Branch coverage data is incorrect after upgrading to Angular 13

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[X] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: Angular 12
Description
The coverage produced when running ng test --code-coverage is incorrect, it is missing branches that were previously counted. This applies to if that do not have an else: these used to be counted as two branches, and they are now counted as one. This artificially increases branch coverage.
🔬 Minimal Reproduction
Starting from a minimal reproduction repository (ng new), make the following changes:

Add src/foo.ts. Note that this function contains two branches to cover: the if, and the (non-explicitly written) else.

export function foo(n: number) {
  if (n % 2 === 0) {
    console.log('hello');
  }
}

Add src/foo.spec.ts:

import { foo } from './foo';

describe('test', () => {
  it('test', () => {
    foo(2);
  });
});

Restrict the test suite to run only foo.spec.ts in src/test.ts:

const context = require.context('./', true, /foo\.spec\.ts$/);

Launch the tests with code coverage: npx ng test --code-coverage
The output reports full coverage, of only one branch:

=============================== Coverage summary ===============================
Statements   : 100% ( 2/2 )
Branches     : 100% ( 1/1 )
Functions    : 100% ( 1/1 )
Lines        : 100% ( 2/2 )

For comparison, downgrading to Angular 12 and to Typescript 4.3.5 results in the correct coverage report, which is:
=============================== Coverage summary ===============================
Statements   : 100% ( 5/5 )
Branches     : 50% ( 1/2 )
Functions    : 100% ( 1/1 )
Lines        : 100% ( 5/5 )

🌍 Your Environment
Everything comes from the default app when running ng new

Angular CLI: 13.2.2
Node: 16.13.2
Package Manager: npm 8.1.2
OS: linux x64

Angular: 13.2.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1302.2
@angular-devkit/build-angular   13.2.2
@angular-devkit/core            13.2.2
@angular-devkit/schematics      13.2.2
@angular/cli                    13.2.2
@schematics/angular             13.2.2
rxjs                            7.5.2
typescript                      4.5.5

It turned out to be pretty complex to find the root cause of this. After spending most of yesterday afternoon and today's morning I was able to locate the root cause of the issue. It turns out that this is caused by this change in istanbul-lib-instrument which is causing incorrect branch coverage for implicit else.
I opened an issue in their repo with a minimal reproduction. I suggest that you subscribe to that issue.
I am going to close this issue, as is not actionable from our end since we don't control which version of istanbul-lib-instrument is used because this is a transitive dependency.


DTNN-132 Clean up bp prototype readme

Describe the contribution
Updates the main README with descriptive text and example configure/build/test scripts.
Adds the bp/docs/example-scripts folder with a README and the example scripts.
Testing performed
Tested all example scripts described in the main README and bp/docs/example-scripts/README.
Expected behavior changes
The READMEs and the example scripts they describe will benefit users with tested, reusable configure/build/test scripts.
System(s) tested on

Hardware: AWS Elastic Container
OS: Ubuntu 20.04.6 LTS

Contributor Info - All information REQUIRED for consideration of pull request
Grafton Kennedy, Vantage Systems, Inc<EMAIL_ADDRESS>

These bplib comments apply to bp
https://github.com/nasa/bplib/pull/260#issuecomment-2237684478

/doc/example-scripts/stand-alone/README.md:
"Copy the example scripts to $BPLIB_HOME." This isn't specific enough. It should say "Copy the example scripts in this directory to $BPLIB_HOME".

https://github.com/nasa/bplib/pull/260#issuecomment-2237733555

/doc/example-scripts/README.md:
"Verify that environment variables in $CFS_HOME/cfs-env-vars are set to the correct paths." This should note that most of the paths shouldn't exist yet. As it is, it makes the reader think the paths should already exist and cFS should already be cloned.

Commit f47a7f9b fixes:
Comment: https://github.com/nasa/bp/pull/64#issuecomment-2240083740

Fix environment variable steps in the README.

Found a typo in the BP example-scripts README:
# Clean/onfigure/build/test

Commit https://github.com/nasa/bp/pull/64/commits/78248a53a2abe16a8ece22ed791d21d8e9ac0eec fixes:
Comment: https://github.com/nasa/bp/pull/64#issuecomment-2242838031

Found a typo in the BP example-scripts README: # Clean/onfigure/build/test

Updated, reviewed, tested, and ready to go.


Save offset in local storage

Currently, if you use custom background and you need to provide custom background offset, you'd have to do it for each page refresh. While custom background template is saved to localstorage.
Custom offset also needs to be saved in the local storage.

I could see that being useful, but only:

for custom (or more specifically, "local") imagery sources
if the offset is stored keyed on the source url

I wouldn't want someone running a task from the HOT task manager to accidentally end up with a previous task's offset.

What about saving them under a name? So that a user will need to choose which of stored offsets to load?

See also #1124

What about saving them under a name? So that a user will need to choose which of stored offsets to load?

What would you name it?

What would you name it?

A user would pick a name

A simpler quick fix would be that when an user set up an offset for a custom imagery, the offset is retain if he switches to Bing and then go back to the custom imagery. It could last for instance for the duration of his session.
It regularly happens in some countries that contributors have to navigate between 2 imageries and it really is an hassle to have to set it up every time.

+1
Perhaps a popup asking if the user wants to re-add the previous session offset would be the best way to do it, as then it's not automatically applied which may be confusing.
I'll see if i can make a prototype, although i'm not experienced in JS so no promises.

I think the best solution would be to add a save button and drop-down box with a list of saved named offsets, similar to JOSM. These would be stored in cookies, but not automatically applied.
I'll try and work on a draft, but no guarantees 😄


Remove document.attachEvent code from web/pdf_print_service.js since it's only necessary for old IE versions

This code was originally added to support IE10 (and below), however with those browsers explicitly unsupported since PDF.js version 2.0 this code is now dead.

/botio-linux preview

Nice find, removing old IE-only code!


prism proxy should mock on 404, not (or in addition to) 501

Summary
Change or add 404 to the list of upstream status codes prism proxy re-mocks on.
Tasks

[ ] PR to add 404 to the list - or -
[ ] PR to add a configuration option (as described below)

Additional context
prism proxy "re-mocks" when it receives 501 from upstream. But "501 is the appropriate response when the server does not recognize the request method" (MDN).
prism proxy, however, should re-mock when "the server can't find the requested resource" (MDN). This should be indicated by a 404.
Also, most frameworks today respond with a 404 on a missing route/endpoint (NextJS, Rails) out of the box. Using 501 requires custom code.
I therefore suggest to either

replace 501 with 404 for re-mocking (breaking change)
add 404 to the list of re-mocked status codes
add configuration which port to use, for example -c, --upstream-code [number] [default: 501].

PR
If you would entertain this idea, we'd consider writing a PR.

A simple solution could be for prism to respond with the same code it received from the API if it can't find the endpoint to remock.
For example,

prism proxies a request
downstream api responds with 501 (or 404)
it doesn't find an endpoint to remock
it responds with 501 or 404

Point is, as virtually no API commonly responds with 501 on not-yet-implemented endpoints, we'd have to implement 501 responses temporarily in the API, and replace the, later with the real response. Kinda nuts. 😀

we'd have to implement 501 responses temporarily in the API, and replace the, later with the real response.

I'm not sure if you've ever seen this happen, but before mocking tools like Prism people were coding up the routes and controllers, then returning static objects/arrays of JSON.
Adding res.status(501).send() until you're finished getting feedback on the mock then writing then replacing it with code seems ok. I'd rather ask people to opt in to mocks than have mocks pop up unexpected on fully functional endpoints just because you requested a missing item from a collection. That's just spooky and confusing.
If there is another approach to mixing mock+proxy then let me know, I've been trying to find nice solutions to this for ages and settled on 501 as a partial way there, but I'm not sure auto-mock 404s is the next step. Let's see if we can come up with something else?

Hi @klausbadelt our team decided that this feature is not one that we want to support in Prism. If you have any other ideas around this topic, feel free to re-open, but for now, we're going to close this request. Thank you!

That's too bad. My team was looking for the exact same functionality. Although the proposed solution would potentially open up doors to ambiguities, it would be nice if we could let individual teams decide how they would like to use this tool. This could be an advanced config parameter such as re-mock-on=[404, 501, ...]


diy the dew

diy just leveled up to a template with bare setup like wall or interweb but soaked with dew and npm juice

@jrdnrch dew template here


Moving all the test files to folders

Moving all the test files in each module to a folder to organize the code files
getting this error:

@TomerNewmanPrograms Takes care of this in #105

Moving all the test files in each module to a folder to organize the code files
getting this error:

This happened to me also, I changed test.py to test_posts.py in posts/tests and it works now. #94


Disable the override of default alert

Is there a way to disable the override of the default Javascript alert? I would like to keep the default alert box, but use jAlert for other scenarios.

Depend what you try to do ! I really don't completely understand what you try to do !

If I write the code
alert("Hello World");
I want to see the default Javascript alert box with the "Ok" button to close, and not the jAlert themed popup with only the small "x" in the corner. I just introduced jAlert into a large project for use with the jTimeout plugin. I have hundreds, or thousands, of alerts in the code, and my client doesn't like the new jAlert alert format. I still want to use the standard Javascript alert with old alerts, and just use jAlert with the jTimeout tool.

jAlert will never overide alert("");
The alert is come from jquery. Maybe one of your script rewrite the alert !

From the README for jAlert
  alert('hi'); //override is enabled by default

jAlert overrides the default Javascript alert, and it is enabled by default. I am looking for how to turn it off.

You must remove this from  jAlert-functions.js
This can not be turn off just remove it from the  jAlert-functions.js. This will not affect your jAlert if you remove it

That was it. Thank you. I was looking in the wrong file.

You welcome 😄

Lol I'm a lil late now, but thanks for helping @ChristianGabs!


card-llinks should show more information about the card on hover

Including, primarily, the title

Fixed as of 7d7e440


墙洞托管URL无法获取yml

--2019-06-21 22:58:17--  https://dler.cloud/link/xxx?dns=1&clash=1
Resolving dler.cloud... <IP_ADDRESS>, <IP_ADDRESS>, 2606:4700:30::681f:4d75, ...
Connecting to dler.cloud|<IP_ADDRESS>|:443... connected.
ERROR: cannot verify dler.cloud's certificate, issued by 'CN=CloudFlare Inc ECC CA-2,O=CloudFlare\, Inc.,L=San Francisco,ST=CA,C=US':
Unable to locally verify the issuer's authority.
To connect to dler.cloud insecurely, use --no-check-certificate'. --2019-06-21 23:04:31--  https://dler.cloud/link/xxx?dns=1&clash=1 Resolving dler.cloud... <IP_ADDRESS>, <IP_ADDRESS>, 2606:4700:30::681f:4c75, ... Connecting to dler.cloud|<IP_ADDRESS>|:443... connected. ERROR: cannot verify dler.cloud's certificate, issued by 'CN=CloudFlare Inc ECC CA-2,O=CloudFlare\\, Inc.,L=San Francisco,ST=CA,C=US':   Unable to locally verify the issuer's authority. To connect to dler.cloud insecurely, use --no-check-certificate'.
--2019-06-21 23:04:34--  https://dler.cloud/link/xxx?dns=1&clash=1
Resolving dler.cloud... <IP_ADDRESS>, <IP_ADDRESS>, 2606:4700:30::681f:4d75, ...
Connecting to dler.cloud|<IP_ADDRESS>|:443... connected.
ERROR: cannot verify dler.cloud's certificate, issued by 'CN=CloudFlare Inc ECC CA-2,O=CloudFlare\, Inc.,L=San Francisco,ST=CA,C=US':
Unable to locally verify the issuer's authority.
To connect to dler.cloud insecurely, use `--no-check-certificate'.

看起来好像错误提示是无法验证证书？但我不知道墙洞的clash证书怎么弄
To connect to dler.cloud insecurely, use `--no-check-certificate'这句不知道什么意思

是没装ca-bundle的缘故，已解决


jQuery adpater

This adapter overwrite native jquery animate function, but you can still use it to know.
 It'll make animating with jQuery much easier.

Having considered this path myself, I’d say it’s pretty dangerous territory to override jQuery’s animate method.


[BEAM-1450] Fix NewDoFn handling of window explosion.

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @sb2nov

Coverage decreased (-0.003%) to 69.727% when pulling a7b5fe559e3796c2b31aa55ddb8ff2b4566f6a00 on robertwb:newdofn-windows into 9ec22f17388ef8d15ccd66813b7bb65647714eb4 on apache:master.

Thanks for the fix. LGTM.
This looks really clean as well.

Coverage decreased (-0.003%) to 69.727% when pulling f02843e60b8feac9d94bf15709694aaa15a8847f on robertwb:newdofn-windows into 9ec22f17388ef8d15ccd66813b7bb65647714eb4 on apache:master.


MultiTenantSpringLiquibase only creates procedures in the default schema

Search first

[X] I searched and no similar issues were found

Description
I have a multi-tenant application with a database. The database has separate schemas per tenant and is managed by Liquibase integration with Spring Boot.
By configuring the MultiTenantSpringLiquibase bean I am able to successfully process my Liquibase change sets upon starting my application for the most part - however when using createProcedured changetypes, the procedure is only created in the default schema, and none of the other tenant databases.
Steps To Reproduce
Changelog:
  <changeSet id="999" author="xyz" runOnChange="true">
    <createProcedure
      path="procedures/sp_get_data.sql"
      relativeToChangelogFile="true"
      replaceIfExists="true"
      procedureName="sp_get_data"/>
  </changeSet>

The procedure sp_get_data is only deployed to the default schema, and no other tenant databases.  An entry is made in the databasechangelog table for it in each database.
Expected/Desired Behavior
The procedured sp_get_data should be deployed to each tenant database, not just the default.
Liquibase Version
4.21.0
Database Vendor & Version
Mysql 8
Liquibase Integration
Spring Boot 2.7.3
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
Windows 11
Additional Context
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR (Thank you!)

This is the same issue as reported in https://github.com/liquibase/liquibase/issues/4304. I debugged this issues and wrote my findings in that issue report.

Thanks, @troligsownder! Would you be up for submitting a PR to fix it?

Hello @nealeduncan1 ! As @troligsownder noticed this is the same issue as https://github.com/liquibase/liquibase/issues/4304 and has been fixed on https://github.com/liquibase/liquibase/pull/4427 that is already merged to master for the next release.

Just tried with 4.23.1 - this is still and issue and not fixed.

Hello @nealeduncan1 - just to make sure: the problem only happens with createProcedure change type for you? For other changes like "createTable" it works fine right?

Hi @filipelautert, yes I have only seen this with createProcedure -  createTable works fine.  There is another related issue however, the createView has an issue with defaultSchema in the body of the view #4316

@tati-qalified could you try to reproduce this issue? thanks


Model Builder generate invalid namespace for generated models

System Information (please complete the following information):

Model Builder Version: 16.0.1907.1703
Visual Studio Version: 16.1.6

Describe the bug
The model builder generates invalid namespace if there is space in Project name.
To Reproduce
Steps to reproduce the behavior:

Make a project with the name containing space between words for instance "Semantic Analysis"
Right-Click on project > Add > Machine learning > Semantic Analysis
After every step, the model has been built, Try to build your model.
It shows that your namespace "Semantic Analysis" is not valid because it contains space in names.

Expected behavior
The model builder should generate a namespace without space and space should be replaced by an underscore(_). For instance, if the project name is "Semantic Analysis" the generated model namespace should be "Semantic_Analysis".

It's a bug in Code Generator, I can take a look @JakeRadMSFT

It's a bug in Code Generator, I can take a look @JakeRadMSFT

fixed

Thanks

Thanks


feat: dark mode update #1 (ignore)

Description
Updating dark mode for:

[x] TitleBar
[x] HelpTip
[x] Tags
[x] Switch component
[x] Tari mining
[x] Merged mining

Motivation and Context
#36
How Has This Been Tested?
Screenshots
Initial Home

Ready to Start

Mining Running

Mining Paused

Expert View Open (tab underline is missing in DarkMode, will be in upcoming PR)

Git history messed up, PR closed.


[pipeline] Catch the exception that load yaml failed

Description
Currently, only scannerError and StrickYAMLError are catched when load component yaml failed when fix the diagnostics. Other types of error will block the pipeline operation.
For example:
"""
Comments
"""
from azure.ai.ml.dsl import pipeline

@dsl.pipeline
def func():
    pass

When there is a warning in this pipeline validate result, it will raise ComposerError when generate diagnostic.
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


Update msstats_plfq.R

nf-core/proteomicslfq pull request
Many thanks for contributing to nf-core/proteomicslfq!
Please fill in the appropriate checklist below (delete whatever is not relevant).
These are the most common things requested on pull requests (PRs).
PR checklist

[ ] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/proteomicslfq branch on the nf-core/test-datasets repo
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: CONTRIBUTING.md

Now you can see the error.

This would be cool to have for a release as well.

Can you rebase or something?

k just a sec

hmm can't push on this PR

you can also make a new one

I think a new one is better.


Is IFindByAndroidUIAutomator removed in 5.0.0-beta?

Description
Hello,
I am updating our framework to Selenium 4 and because we share some of the code for the session creation of devices and browsers I noticed that for mobile apps the IFindByAndroidUIAutomator was removed.
We are using it to run some code in order to scroll the view like this:
 var driver = ((AndroidDriver) SeleniumContext.WebDriver);
 var code = BuildJavaCode("textContains", expectedText);
driver.FindElementByAndroidUIAutomator(code);

Is there a replacement I can use or this will no longer be applied?
Thanks

@alexlazarciuc
The underlying code was not removed, but how you interact with it has.
Here is where we made the change:
https://github.com/appium/appium-dotnet-driver/pull/470
Here is an example of the new usage:
https://github.com/appium/appium-dotnet-driver/blob/8acfc1ce90a4fb3d48e2b611023daed30c97583c/test/integration/Android/ElementTest.cs#L92

Thank you, @TroyWalshProf  - I will give it a try.


init

👷 Deploy Preview for hongdeyu processing.

Name
Link

🔨 Latest commit
6bd7a2244d8ee4c18103a79c50a6d25510ea855b

🔍 Latest deploy log
https://app.netlify.com/sites/hongdeyu/deploys/670c45ad52bda60008636bc6


[Menu] Add new context menu demo

Closes #1462

A couple of minor issues from playing with the demo:

Right-clicking elsewhere when the context menu is open doesn't change the menu context.
The menu items would benefit from being a more representative example of a context menu

@SarthakC First pull request ✌

@SarthakC First pull request ✌, thank you, well done

Cheers!


How can I show the process bar on Django HTML?

I have created an admin panel using Django and [python-ffmpeg-video-streaming] everything is good, but I want to show process bar on HTML code.  Can anyone help me on this case?

It is up to you which approach you want to choose. Personally, I prefer to use Django Channels (WebSocket) in this use case to pass data to the front-end.

@sannjayy , any succes with the django channels ?


Javadocs disappeared for v4.1

The API docs for 4.1 show a 404 not found error.
Seems to already have happened in the past:  #9709

will check

Fixed... my bad.


Add more uniform setters to program class

I've added a few more uniform setters to program, this time taking in glm types. In the program header file, I have decide to include the file GLM/fwd.hpp. This header file forward declares all of the classes in glm, but does not implement them. I did this because glm classes are very laborious to forward declare, making copious use of typedef and other commands. SInce this header file does not include implementation, and only forward declaration, it does not come with the drawbacks that including external headers in a header file has. Thus, I think it is appropriate to use here.

I've added matrix uniform setters for the shader class. This concludes my work on the shader class for now, as with this I will now be able to work on the rest of the graphical components.

I've added a first implementation of the line class. I have tested it and it does work as expected, however, I still need to write tests for it and continue to work on it for a bit longer. Mainly, I need to solve the problem with needing to use a third party library header in the header, as I detail in the commit message below:
The line class for now compiles its own shader, which giving no
access or option to change it to outside classes. Nearly all of the
variables are bound to an IDContainer object, a shared pointer of
which more pointers are created when a line object is copied. The only
variable that is unique to the object is the color.
There is a problem right now upon compilation, with the glm forward declaration
header, as it fails upon reaching the unique_ptr in the header
file. As a temporary workaround, the proper glm header is used
instead. This is of course unnaceptable and will be changed as soon as possible.

Several variables did not have the private tag in the Program class as was intended. I have fixed this.

The color field has been made to affect all copied instances of a line
class. This with the intention of removing issues concerning the use
forward declarations of glm classes in the header file. The unproper
use of glm.hpp in the header file was removed, replace with the use of
the proper forward declaration fwd.hpp.
The copy constructor and the copy operator have been removed, as they
are no longer needed, as the default c++ generated ones will now be enough.

Certain documentation has been updated to be current with the current
line implementation. Functions which do not throw exceptions have been
marked appropriately. A function to access the program associated to
the line has been added.

I have begun to define the ellipse class.
The ellipse class will generate a number of points based on the user's
rX, rY and number_of_points input. It will then draw these to the
screen when prompted to, in the future possible with a line mode and a
triangle mode.


Exclusive Audio + Chromecast Backend (also Fix for Seamless Audio)

Huge commit , need review.
P/S : Backend support only. No UI yet.

can't play GC and EA on MVs. I did find the audiocontext from the video element but the thing froze out.


Sticky items in Virtuoso variabelbox

Added value for topItemCount prop in Virtuoso to make search and select all sticky if shown.

Should this PR also have the animations for the sticky items?


Review swarm detection algorithm

The following states needs to be determined by Portainer:

Docker standalone
Docker Swarm primary
Docker Swarm replica
Docker swarm-mode manager
Docker swarm-mode worker

The current way of determining this state is not really clear:
  Config.$promise.then(function (c) {
    $scope.swarm = c.swarm;
    Info.get({}, function(d) {
      if ($scope.swarm && !_.startsWith(d.ServerVersion, 'swarm')) {
        $scope.swarm_mode = true;
        $scope.swarm_manager = false;
        if (d.Swarm.ControlAvailable) {
          $scope.swarm_manager = true;
        }
      }
    });
  });

And the usage in Angular templates is messy:

          Swarm

We need to find a clearer way to determine the connected engine state and a clearer way to represent this state in the Angular templates.
var engineState = {
  "Swarm": {
    "Node": "primary|replica",
  },
  "SwarmMode": {
    "Node": "manager|worker"
  },
  "Standalone": true|false,
};

As an extent of this, a banner should be displayed in the dashboard when a user connected Portainer using the --swarm flag on a Docker standalone host.

Related to #101, this will not be required anymore after multiple endpoint management implementation.


[swift-3.0-preview-2-branch][stdlib] unavailable String APIs: use Swift 2.x APIs without first argument labels

Explanation: correct the signatures of the unavailable advancedBy and distanceTo methods on String indices.
Scope of the issue: migration of code that uses string indices.
Risk: low.
Reviewed by: nobody.
Testing: manual.

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

:shipit:

@swift-ci Please test

@swift-ci test


Issue #171

As i can see  below methods are not present in jedis 2.6.2. Is there any specific reason or there is another to release binary jedis.
public void returnBrokenResource(final BinaryJedis resource) {

  returnBrokenResourceObject(resource);

}

public void returnResource(final BinaryJedis resource) {

  returnResourceObject(resource);

}


do not merge

do not merge
just to test the new spinmint

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: https://i-0400493be296524a2.test.spinmint.com
Test Admin Account: Username: sysadmin | Password: sysadmin
Test User Account: Username: user-1 | Password: user-1
Instance ID: i-0400493be296524a2

Spinmint test server destroyed

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: https://i-0a468845ed4e1bcf7.test.spinmint.com
Test Admin Account: Username: sysadmin | Password: sysadmin
Test User Account: Username: user-1 | Password: user-1
Instance ID: i-0a468845ed4e1bcf7

Spinmint test server destroyed


[lapack-reference] Build failure on x64-linux

Package: lapack-reference[blas-select,core,noblas]:x64-linux -> 3.11.0#1
Host Environment

Host: x64-linux
Compiler: GNU 11.4.0
vcpkg-tool version: 2023-11-16-4c1df40a3c5c5e18de299a99e9accb03c2a82e1e
vcpkg-scripts version: cd5e746ec 2023-11-23 (3 days ago)

To Reproduce
vcpkg install lapack
Failure logs
-- Using cached Reference-LAPACK-lapack-v3.11.0.tar.gz.
-- Cleaning sources at /home/zhiyaot/vcpkg/buildtrees/lapack-reference/src/v3.11.0-5e6de67bfb.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/zhiyaot/vcpkg/downloads/Reference-LAPACK-lapack-v3.11.0.tar.gz
-- Applying patch cmake-config.patch
-- Applying patch lapacke.patch
-- Using source at /home/zhiyaot/vcpkg/buildtrees/lapack-reference/src/v3.11.0-5e6de67bfb.clean
-- The Fortran compiler identification is unknown
CMake Error at scripts/cmake/vcpkg_find_fortran.cmake:130 (message):
  Unable to find a Fortran compiler using 'CMakeDetermineFortranCompiler'.
  Please install one (e.g.  gfortran) and make it available on the PATH!
Call Stack (most recent call first):
  ports/lapack-reference/portfile.cmake:54 (vcpkg_find_fortran)
  scripts/ports.cmake:170 (include)

resolved

I have the same issue. May I ask how you solved it?

Maybe by installing gfortran with the system package manager?

Unable to find a Fortran compiler using 'CMakeDetermineFortranCompiler'.
Please install one (e.g.  gfortran) and make it available on the PATH!


Txn V3 Support?

Right now, we can't sign v3 transactions even if TransactionHashInvoke supports it, the SignInvokeTransaction doesn't support it?

Hi @dhruvkelawala, could you send me a piece of your code and the error message?


login view update

Related Issuse

Info about Issue or bug
To add mandatory field options in login inputs

Closes: #166 [issue number that will be closed through this PR]
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
I have added 'requied' tag in the input forms of the login page to make them as madatory field
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.

Screenshots

Original
Updated

original screenshot
updated screenshot

I have resolved the branch conflicts which were arising previously. Kindly review now sir @khannakshat7

@sreetu Please resolve the conflicts

I have deleted the duplicate code and so, conflict has been resolved.

@sreetu Any update on this?

@sreetu Any update on this?

@khannakshat7 sir, I have resolved the conflicts.

I think there is some mistake in this PR have a look

this PR is removing one of the most important code on that page
@khannakshat7 please look into this

there is a code for error / success msg after the div having id myTabContent but this PR is removing it.
Please allow me to make a PR for this

@khannakshat7 please assign me


How to programmatically set video duration

Hi, I wanted to limit the duration of video recording to 3 seconds. How do I achieve that?

You can pass extra intent params through a bundle, by using the method

setExtras(Bundle);

cameraPicker = new CameraVideoPicker(this);
cameraPicker.shouldGenerateMetadata(true);
cameraPicker.shouldGeneratePreviewImages(true);
Bundle extras = new Bundle();
// For capturing Low quality videos; Default is 1: HIGH
extras.putInt(MediaStore.EXTRA_VIDEO_QUALITY, 0);
// Set the duration of the video
extras.putInt(MediaStore.EXTRA_DURATION_LIMIT, 5);
cameraPicker.setExtras(extras);
cameraPicker.setVideoPickerCallback(this);
pickerPath = cameraPicker.pickVideo();


ERROR: 500: Internal error encountered. - 500

I'm getting this error when trying to amend new Google Classrooms.  I can edit older classrooms but not any that I've created in the last few days.
Error:
ERROR: 500: Internal error encountered. - 500
Can any one help?
Thank you.

What command are you using? Can you edit them in Classroom itself?
On Thu, Jan 28, 2021, 3:09 AM jcs808<EMAIL_ADDRESS>wrote:

I'm getting this error when trying to amend new Google Classrooms. I can
edit older classrooms but not any that I've created in the last few days.
Error:
ERROR: 500: Internal error encountered. - 500
Can any one help?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/1311, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDIZMG6IDHACCE4DBH4MUDS4ELVHANCNFSM4WWSGPHA
.

What command are you using? Can you edit them in Classroom itself?
On Thu, Jan 28, 2021, 3:09 AM jcs808<EMAIL_ADDRESS>wrote:

I'm getting this error when trying to amend new Google Classrooms. I can
edit older classrooms but not any that I've created in the last few days.
Error:
ERROR: 500: Internal error encountered. - 500
Can any one help?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/1311, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDIZMG6IDHACCE4DBH4MUDS4ELVHANCNFSM4WWSGPHA
.

I'm using this command
GAM.exe course  add teacher
GAM.exe course  add student
I've used this many times before and it works on older Google Classrooms.  I can edit the Google Classroom in the web interface but that only invites people and the command adds them, this is preferable when adding students.

I'm using this command
GAM.exe course  add teacher
GAM.exe course  add student
I've used this many times before and it works on older Google Classrooms.  I can edit the Google Classroom in the web interface but that only invites people and the command adds them, this is preferable when adding students.

Same problem here.

Same problem here.

I get the same result here:
https://developers.google.com/classroom/reference/rest/v1/courses.students/create
So it's not a GAM issue.

I get the same result here:
https://developers.google.com/classroom/reference/rest/v1/courses.students/create
So it's not a GAM issue.

I've found this entry on the Google Classroom API issue tracker, but response from Google.
https://issuetracker.google.com/issues/178647877

I've found this entry on the Google Classroom API issue tracker, but response from Google.
https://issuetracker.google.com/issues/178647877


SW-2629 Remove id from on change handlers

This change is needed so html id can be set independently of the data model. We can then change the value of the data model using the necessary id, separately of the html id

oops, i've been merging the other PRs,, i will hold off until this merged

oops, i've been merging the other PRs,, i will hold off until this merged

Merged! Thanks


Adding Ars Magica 5e sheet

Adding a sheet for Ars Magica 5e, based on the one in the back of the core book, with some minor adjustments.
I'm aware another was merged a couple of days ago, but it has some inconsistencies with the rules(mainly spell Range and Target being numbers instead of text/select fields), and I started this one the same day without realizing that one existed.
Edit: Also some small changes to the Deadlands Classic sheet I submitted a while ago, I guess, since I forgot to make a PR when I made those commits originally.

Hey, sorry you did all this work only to have another sheet pop up first. We like to keep it to 1 sheet per game system, except in a few small cases. If there are system inconsistencies with the other sheet, you are more than welcome to fix them there, nobody "owns" their sheet here.
As for the Deadlands changes you made, I'm not able to grab those since you have merge conflicts. If you can add those Deadlands changes by themselves, without the conflicts, I'll be happy to merge them.


I'm getting timeout because is generating more than one ipa.

I found the issue when new XCode version has from iPhone 4 to iPhone Xs like about 12 systems. So is building those .ipa.
Does you have any way to configure or any solution?

Hi @cbedoy
Could you please send us a related build URL so we can see what's happening during the build?


Erroneous behaviour when cancelling a program

What happened?
When running a pulumi program, especially with automation API, sending a single Ctrl+C to the execution hangs the program indefinitely
Expected Behavior
When sending a Ctrl+C to a Pulumi invocation, I'd expect the program to try and gracefully shut down and terminate
Steps to reproduce
Customer sent the following program that exhibits this behaviour
using System;
using System.Collections.Generic;
using System.ComponentModel.DataAnnotations;
using System.Threading;
using System.Threading.Tasks;
using McMaster.Extensions.CommandLineUtils;
using Pulumi;
using Pulumi.Automation;
using Pulumi.Aws;
using Pulumi.Aws.S3;

namespace Snap;

[Command("pulumi", Description = "Deploy Pulumi stack")]
public class DeployPulumiCommand
{
    [Required]
    [Option("--project-name",
        "Pulumi project name",
        CommandOptionType.SingleValue,
        ShowInHelpText = true)]
    private string ProjectName { get; set; }

    public async Task<int> OnExecuteAsync(CancellationToken cancellationToken)
    {
        PulumiFn program = PulumiFn.Create(async () =>
        {
            var region = "us-west-2";
            var provider = new Provider(region, new()
            {
                Region = region,
            });

            var bucket = new Bucket("some-bucket", BucketArgs.Empty, new CustomResourceOptions { Provider = provider });
        });

        return await UpdatePulumiAsync(program, ProjectName, "test-stack", cancellationToken);
    }

    private static async Task<int> UpdatePulumiAsync(PulumiFn program, string projectName, string stackName, CancellationToken cancellationToken)
    {
        var stack = await SetupAsync(projectName, stackName, program, cancellationToken);

        Console.WriteLine("updating stack...");
        var result = await stack.UpAsync(new UpOptions
        {
            OnStandardOutput = Console.WriteLine,
            Parallel = Int32.MaxValue,
            Color = "always",
        }, cancellationToken);

        if (result.Summary.ResourceChanges != null)
        {
            Console.WriteLine("update summary:");
            foreach (var change in result.Summary.ResourceChanges)
                Console.WriteLine($"    {change.Key}: {change.Value}");
        }

        return 0;
    }

    private static async Task<WorkspaceStack> SetupAsync(string projectName, string stackName, PulumiFn program, CancellationToken cancellationToken)
    {
        var stackArgs = new InlineProgramArgs(projectName, stackName, program);
        var plugins = new Dictionary<string, string>
        {
            { "aws", "v4.24.1" },
        };
        var config = new Dictionary<string, ConfigValue>
        {
            { "aws:region", new ConfigValue("us-west-2") },
            { "aws-native:region", new ConfigValue("us-west-2") },
        };

        var stack = await LocalWorkspace.CreateOrSelectStackAsync(stackArgs, cancellationToken);
        Console.WriteLine("successfully initialized stack");

        Console.WriteLine("installing plugins...");
        foreach (var kvp in plugins)
        {
            await stack.Workspace.InstallPluginAsync(kvp.Key, kvp.Value, cancellationToken: cancellationToken);
        }
        Console.WriteLine("plugins installed");

        Console.WriteLine("setting up config...");
        foreach (var kvp in config)
        {
            await stack.SetConfigAsync(kvp.Key, kvp.Value, cancellationToken: cancellationToken);
        }
        Console.WriteLine("config set");

        Console.WriteLine("refreshing stack...");
        await stack.RefreshAsync(new RefreshOptions { OnStandardOutput = Console.WriteLine }, cancellationToken);
        Console.WriteLine("refresh complete");

        return stack;
    }
}

Output of pulumi about
N/A
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Potentially related to #124

Need to actually try it out, but just from looking, it looks like McMaster.Extensions.CommandLineUtils is handling CTRL+C:
https://github.com/natemcmaster/CommandLineUtils/blob/81199c7ec68367ea9612be55719dc1fe08f658da/src/Hosting.CommandLine/Internal/CommandLineLifetime.cs#L83-L88
Is the parent process handling and cancelling the SIGINT, but child processes still being killed?


FutureWarning: resume_download is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use force_download=True.

Not sure what the special token stuff is about, but it seem that a setting in file_download is no longer needed.
(mlx) ➜  llava git:(main) ✗ python mytest.py
/opt/homebrew/Caskroom/miniconda/base/envs/mlx/lib/python3.12/site-packages/huggingface_hub/file_download.py:1132: FutureWarning: `resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.
  warnings.warn(
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
Fetching 15 files: 100%|███████████████████████████████████████████████| 15/15 [00:00<00:00, 140121.51it/s]
A large cathedral with stained glass windows and a high ceiling.

Added fix to #749


Title: Roulette Game

Is your feature request related to a problem? Please describe.
Roulette is a classic casino game of chance that involves a spinning wheel, a small ball, and a betting table. Here’s a brief overview of how it works:
The Wheel
Design: The roulette wheel is divided into numbered pockets ranging from 0 to 36.
Colors: The numbers alternate between red and black, except for 0 , which are green.
The Table
The table displays all the numbers and the different types of bets that can be placed.
Bets can be made on individual numbers, groups of numbers, colors (red or black), odd or even, and high or low numbers.
Gameplay
Placing Bets: Players place their chips on the betting table, choosing their desired bets.
Payouts: The croupier announces the winning number and color, and winning bets are paid out according to a predetermined pay table, while losing bets are collected.
The primary goal is to predict which numbered pocket the ball will land in. Players can make a variety of bets, each offering different odds and payouts.
Roulette is known for its simplicity and excitement, attracting players with its wide range of betting options and the thrill of watching the ball bounce and settle into a pocket.
Describe the solution you'd like.
add the aforementioned game.
Describe alternatives you've considered.
.
Add any other context or screenshots about the feature request here.

@tanyagupta01 Not accepting any new projects.


question / enhancement proposal, continue with previous level of structuring

An example: if someone wants an output like:
* Topic
  some text,
  ** Subtopic 1
    some text,
  ** Subtopic 2
    some text,
  continue with some text to Topic, e.g. conclusion,
* Topic 2
  some text,

I didn't yet find a way to format the indented part   continue with some text to Topic, e.g. conclusion, in AsciidocFX, and in numbered lists keep the counting.
Likely I overlooked something, thanks for any hint, or it could be a good idea to add an option for such???

That is a question related to Asciidoctor syntax. You can ask this to Asciidoctor team https://chat.asciidoctor.org/

thank you, did so, https://asciidoctor.zulipchat.com/#narrow/stream/279642-users/topic/structure.2C.20continuing.20with.20.20previous.20level.2C


add github actions for rspec

adding CI on pull requests

I've had this on my list for a while. Thanks so much for getting this done!


客户端间歇性超时

提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。
除非特殊情况，请完整填写所有问题。不按模板发的 issue 将直接被关闭。
如果你遇到的问题不是 V2Ray 的 bug，比如你不清楚要如何配置，请使用Discussion进行讨论。

你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）

V2Ray 4.22.1

客户端（树莓派）： V2Ray 4.22.1 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.13 linux/arm)
服务器： V2Ray 4.22.1 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.13.5 linux/amd64)

你的使用场景是什么？

比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。

你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）

间歇性超时，贴出的log中是访问twitter的超时。遇到此问题时，用本机客户端替换树莓派客户端后问题消失；或重启树莓派上V2Ray客户端，问题也会消失。

你期待看到的正确表现是怎样的？

twitter正常打开

请附上你的配置（提交 Issue 前请隐藏服务器端IP地址）。

服务器端配置:
{
  "log": {
    "access": "/var/log/v2ray/access.log",
    "error": "/var/log/v2ray/error.log",
    "loglevel": "error"
    // "loglevel": "info"
  },
  "inbounds": [
    {
      "port": 443,
      "protocol": "vmess",
      "settings": {
        "clients": [
          {
            "id": "e443e443-e443-e443-e443-0f04a535846c",
            "level": 1,
            "alterId": 7
          }
        ]
      },
      "streamSettings": {
        "network": "h2",
        "httpSettings": {
          "path": "/ray"
        },
        "security": "tls",
        "tlsSettings": {
          "certificates": [
            {
              "certificateFile": "/root/.acme.sh/my.site_ecc/fullchain.cer",
              "keyFile": "/root/.acme.sh/my.site_ecc/my.site.key"
            }
          ]
        }
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom",
      "settings": {}
    },
    {
      "protocol": "blackhole",
      "settings": {},
      "tag": "blocked"
    }
  ],
  "routing": {
    "rules": [
      {
        "type": "field",
        "ip": [
          "geoip:private"
        ],
        "outboundTag": "blocked"
      }
    ]
  }
}

客户端配置:
{
  "log": {
    "access": "/var/log/v2ray/access.log",
    "error": "/var/log/v2ray/error.log",
    "loglevel": "info"
    // "loglevel": "warning"
  },
  "inbounds": [
    {
      "port": 12345,
      "tag": "transparent",
      "protocol": "dokodemo-door",
      "settings": {
        "network": "tcp,udp",
        "followRedirect": true
      },
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls"
        ]
      },
      "streamSettings": {
        "sockopt": {
          "tproxy": "tproxy"
        }
      }
    },
    {
      "port": 1080,
      "listen": "<IP_ADDRESS>",
      "tag": "socks-proxy",
      "protocol": "socks",
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls"
        ]
      }
    },
    {
      "port": 1086,
      "listen": "<IP_ADDRESS>",
      "tag": "http-proxy",
      "protocol": "http",
      "settings": {
        "timeout": 0
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "vmess",
      "tag": "v2-server",
      "settings": {
        "vnext": [
          {
            "address": "my.site",
            "port": 443,
            "users": [
              {
                "id": "e443e443-e443-e443-e443-0f04a535846c",
                "alterId": 7
              }
            ]
          }
        ]
      },
      "streamSettings": {
        "network": "h2",
        "httpSettings": {
          "path": "/ray"
        },
        "security": "tls",
        "sockopt": {
          "mark": 255
        }
      }
    },
    {
      "tag": "direct",
      "protocol": "freedom",
      "settings": {
        "domainStrategy": "UseIP"
      },
      "streamSettings": {
        "sockopt": {
          "mark": 255
        }
      }
    },
    {
      "tag": "block",
      "protocol": "blackhole",
      "settings": {
        "response": {
          "type": "http"
        }
      }
    },
    {
      "tag": "dns-out",
      "protocol": "dns",
      "streamSettings": {
        "sockopt": {
          "mark": 255
        }
      }
    }
  ],
  "dns": {
    "hosts": {
      "my.site": "<IP_ADDRESS>",
      "<IP_ADDRESS>": "<IP_ADDRESS>",
      "dns.google": "<IP_ADDRESS>"
    },
    "servers": [
      {
        "address": "<IP_ADDRESS>",
        "port": 53,
        "domains": [
          "geosite:cn",
          "ntp.org",
          "my.site"
        ]
      },
      {
        // "address": "https://<IP_ADDRESS>/dns-query",
        "address": "<IP_ADDRESS>",
        "domains": [
          "geosite:geolocation-!cn",
          "geosite:speedtest"
        ]
      },
      "<IP_ADDRESS>"
    ]
  },
  "routing": {
    "domainStrategy": "IPOnDemand",
    "rules": [
      { // 劫持 53 端口 UDP 流量，使用 V2Ray 的 DNS
        "type": "field",
        "inboundTag": [
          "transparent"
        ],
        "port": 53,
        "network": "udp",
        "outboundTag": "dns-out"
      },
      { // 直连 123 端口 UDP 流量（NTP 协议）
        "type": "field",
        "inboundTag": [
          "transparent"
        ],
        "port": 123,
        "network": "udp",
        "outboundTag": "direct"
      },
      { // intranet
        "type": "field",
        "outboundTag": "direct",
        "ip": [
          "<IP_ADDRESS>/16",
          "<IP_ADDRESS>/16"
        ]
      },
      { // DNS within China
        "type": "field",
        "ip": [
          "<IP_ADDRESS>",
          "<IP_ADDRESS>/32",
          "<IP_ADDRESS>/32",
          "<IP_ADDRESS>"
        ],
        "outboundTag": "direct"
      },
      { // BT 流量直连
        "type": "field",
        "protocol": [
          "bittorrent"
        ],
        "outboundTag": "direct"
      },
      { // DNS outside China
        "type": "field",
        "ip": [
          "<IP_ADDRESS>",
          "<IP_ADDRESS>",
          "<IP_ADDRESS>",
          "<IP_ADDRESS>"
        ],
        "outboundTag": "v2-server"
      },
      { // 广告拦截
        "type": "field",
        "domain": [
          "geosite:category-ads-all"
        ],
        "outboundTag": "block"
      },
      { // 直连中国大陆主流网站 ip 和 保留 ip
        "type": "field",
        "ip": [
          "geoip:private",
          "geoip:cn"
        ],
        "outboundTag": "direct"
      },
      { // 直连中国大陆主流网站域名 & vps
        "type": "field",
        "domain": [
          "geosite:cn",
          "domain:my.site"
        ],
        "outboundTag": "direct"
      },
      { // non-china sites
        "type": "field",
        "outboundTag": "v2-server",
        "domain": [
          "geosite:geolocation-!cn",
          "geosite:speedtest",
          "domain:dns.google",
          "domain:<IP_ADDRESS>"
        ]
      },
      { // always route explicit proxy
        "type": "field",
        "inboundTag": [
          "socks-proxy",
          "http-proxy"
        ],
        "outboundTag": "v2-server"
      }
    ]
  }
}

请附上出错时软件输出的错误日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志为空，目前设置的log等级为error。
客户端错误日志:
2020/04/13 14:14:16 [Info] [3463428526] v2ray.com/core/proxy/socks: TCP Connect request to tcp:twitter.com:443
2020/04/13 14:14:16 [Info] [3463428526] v2ray.com/core/app/dispatcher: sniffed domain: twitter.com
2020/04/13 14:14:18 [Info] [1327768356] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:18 [Info] [3618910640] v2ray.com/core/proxy/socks: TCP Connect request to tcp:pbs.twimg.com:443
2020/04/13 14:14:18 [Info] [2023199474] v2ray.com/core/proxy/socks: TCP Connect request to tcp:video.twimg.com:443
2020/04/13 14:14:18 [Info] [1327768356] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:18 [Info] [2684041438] v2ray.com/core/proxy/socks: TCP Connect request to tcp:t.co:443
2020/04/13 14:14:18 [Info] [3618910640] v2ray.com/core/app/dispatcher: sniffed domain: pbs.twimg.com
2020/04/13 14:14:18 [Info] [2023199474] v2ray.com/core/app/dispatcher: sniffed domain: video.twimg.com
2020/04/13 14:14:18 [Info] [2684041438] v2ray.com/core/app/dispatcher: sniffed domain: t.co
2020/04/13 14:14:18 [Info] [3409323823] v2ray.com/core/proxy/socks: TCP Connect request to tcp:twitter.com:443
2020/04/13 14:14:18 [Info] [3409323823] v2ray.com/core/app/dispatcher: sniffed domain: twitter.com
2020/04/13 14:14:18 [Info] [1172962873] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:18 [Info] [1172962873] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:18 [Info] [3729801625] v2ray.com/core/proxy/socks: TCP Connect request to tcp:twitter.com:443
2020/04/13 14:14:18 [Info] [3729801625] v2ray.com/core/app/dispatcher: sniffed domain: twitter.com
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain abs.twimg.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: twitter.com. TypeA -> [<IP_ADDRESS>] 10.195991ms
2020/04/13 14:14:19 [Info] [3206041259] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:twitter.com:443]
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: abs.twimg.com. TypeAAAA -> [] 11.202075ms
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: twitter.com. TypeAAAA -> [] 37.120409ms
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: abs.twimg.com. TypeA -> [<IP_ADDRESS>] 36.798693ms
2020/04/13 14:14:19 [Info] [50168095] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:abs.twimg.com:443]
2020/04/13 14:14:19 [Info] [3625870445] v2ray.com/core/proxy/socks: TCP Connect request to tcp:twitter.com:443
2020/04/13 14:14:19 [Info] [3625870445] v2ray.com/core/app/dispatcher: sniffed domain: twitter.com
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain fonts.gstatic.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:19 [Info] [2829359529] v2ray.com/core/proxy/freedom: dialing to to tcp:<IP_ADDRESS>:443
2020/04/13 14:14:19 [Info] [2829359529] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:<IP_ADDRESS>:443
2020/04/13 14:14:19 [Info] [3214465337] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:19 [Info] [3214465337] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:19 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:19 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:20 [Info] [3592243347] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:20 [Info] [3592243347] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:20 [Info] [2165079177] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:20 [Info] [2165079177] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:20 [Info] [2017191649] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:20 [Info] [2017191649] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:20 [Info] [452349862] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:20 [Info] [452349862] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:20 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:20 [Info] [3463428526] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:twitter.com:443]
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain pbs.twimg.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain t.co at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain video.twimg.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: api.twitter.com. TypeA -> [<IP_ADDRESS>] 10.087503ms
2020/04/13 14:14:22 [Info] [1327768356] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: pbs.twimg.com. TypeA -> [<IP_ADDRESS>] 13.017474ms
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: video.twimg.com. TypeAAAA -> [] 11.428948ms
2020/04/13 14:14:22 [Info] [3618910640] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:pbs.twimg.com:443]
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: t.co. TypeA -> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] 11.466551ms
2020/04/13 14:14:22 [Info] [2684041438] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:t.co:443]
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:22 [Info] [3409323823] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:twitter.com:443]
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: api.twitter.com. TypeAAAA -> [] 182.99905ms
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:22 [Info] [1172962873] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: t.co. TypeAAAA -> [] 261.851541ms
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: video.twimg.com. TypeA -> [<IP_ADDRESS>] 272.586746ms
2020/04/13 14:14:22 [Info] [2023199474] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:video.twimg.com:443]
2020/04/13 14:14:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:22 [Info] [3729801625] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:twitter.com:443]
2020/04/13 14:14:23 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: pbs.twimg.com. TypeAAAA -> [] 631.650333ms
2020/04/13 14:14:23 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:23 [Info] [3625870445] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:twitter.com:443]
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:23 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:23 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:23 [Info] [3214465337] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:24 [Info] [3592243347] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:24 [Info] [2165079177] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:24 [Info] [2017191649] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:24 [Info] [452349862] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:27 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/04/13 14:14:27 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2020/04/13 14:14:37 [Info] [2829359529] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:37 [Info] [2829359529] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/04/13 14:14:38 [Info] [2608078702] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:39 [Info] [419718750] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:39 [Info] [3170822414] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:46 [Info] [3206041259] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:46 [Info] [50168095] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:47 [Info] [1546396869] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:47 [Info] [3463428526] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:48 [Info] [3566410265] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:48 [Info] [3566410265] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:48 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:48 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:49 [Info] [1327768356] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:49 [Info] [3618910640] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:49 [Info] [2023199474] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:49 [Info] [2684041438] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:49 [Info] [3409323823] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:49 [Info] [1172962873] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:49 [Info] [3729801625] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:49 [Info] [2520859371] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:49 [Info] [2520859371] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:50 [Info] [3992761050] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:50 [Info] [3992761050] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:50 [Info] [2579972146] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:50 [Info] [2579972146] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:50 [Info] [3625870445] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:50 [Info] [208629315] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:50 [Info] [208629315] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:50 [Info] [358070411] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:14:50 [Info] [358070411] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:14:50 [Info] [3214465337] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:51 [Info] [3592243347] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:51 [Info] [2165079177] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:51 [Info] [2017191649] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:51 [Info] [452349862] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:52 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:52 [Info] [3566410265] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:52 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:52 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:52 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:14:52 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:14:52 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:14:53 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:53 [Info] [2520859371] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:54 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:54 [Info] [3992761050] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:54 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:54 [Info] [2579972146] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:54 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:54 [Info] [208629315] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:14:54 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:14:54 [Info] [358070411] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:18 [Info] [1904424005] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:18 [Info] [1904424005] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:18 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:18 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:19 [Info] [3566410265] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:19 [Info] [4083833330] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:19 [Info] [4083833330] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:20 [Info] [385154253] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:20 [Info] [385154253] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:20 [Info] [3715229698] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:20 [Info] [3715229698] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:20 [Info] [2445012602] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:20 [Info] [2445012602] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:20 [Info] [3720103643] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:20 [Info] [3720103643] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:20 [Info] [3354253887] v2ray.com/core/proxy/socks: TCP Connect request to tcp:twitter.com:443
2020/04/13 14:15:20 [Info] [3354253887] v2ray.com/core/app/dispatcher: sniffed domain: twitter.com
2020/04/13 14:15:20 [Info] [2520859371] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:21 [Info] [3992761050] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:21 [Info] [2579972146] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:21 [Info] [208629315] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:21 [Info] [358070411] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:22 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:22 [Info] [1904424005] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:22 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:22 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:22 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:22 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:22 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:22 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:22 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:23 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:23 [Info] [4083833330] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:24 [Info] [385154253] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:24 [Info] [3715229698] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:24 [Info] [2445012602] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:24 [Info] [3720103643] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:24 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:24 [Info] v2ray.com/core/proxy/freedom: opening connection to udp:<IP_ADDRESS>:53
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: twitter.com. TypeA -> [<IP_ADDRESS>] 12.406594ms
2020/04/13 14:15:24 [Info] [3354253887] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:twitter.com:443]
2020/04/13 14:15:24 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: twitter.com. TypeAAAA -> [] 21.57369ms
2020/04/13 14:15:32 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/04/13 14:15:32 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2020/04/13 14:15:48 [Info] [1244301580] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:48 [Info] [1244301580] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:48 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:48 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:49 [Info] [1904424005] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:49 [Info] [776412388] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:49 [Info] [776412388] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:50 [Info] [1101534440] v2ray.com/core/proxy/socks: TCP Connect request to tcp:api.twitter.com:443
2020/04/13 14:15:50 [Info] [1101534440] v2ray.com/core/app/dispatcher: sniffed domain: api.twitter.com
2020/04/13 14:15:50 [Info] [4083833330] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:51 [Info] [385154253] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:51 [Info] [3715229698] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:51 [Info] [2445012602] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:51 [Info] [3720103643] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:51 [Info] [3354253887] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/socks: connection ends > context canceled
2020/04/13 14:15:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:52 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:52 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:52 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:52 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:52 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:52 [Info] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:52 [Info] v2ray.com/core/proxy/freedom: opening connection to udp:<IP_ADDRESS>:53
2020/04/13 14:15:52 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:52 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:52 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: api.twitter.com. TypeA -> [<IP_ADDRESS>] 29.725326ms
2020/04/13 14:15:52 [Info] [1244301580] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:52 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: api.twitter.com. TypeAAAA -> [] 66.328501ms
2020/04/13 14:15:53 [Info] [2054180273] v2ray.com/core/proxy/socks: TCP Connect request to tcp:ssl.gstatic.com:443
2020/04/13 14:15:53 [Info] [2054180273] v2ray.com/core/app/dispatcher: sniffed domain: ssl.gstatic.com
2020/04/13 14:15:53 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:53 [Info] [776412388] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:54 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain api.twitter.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:54 [Info] [1101534440] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:api.twitter.com:443]
2020/04/13 14:15:56 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:15:56 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:15:56 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:15:57 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain ssl.gstatic.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:15:57 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: ssl.gstatic.com. TypeA -> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] 10.403802ms
2020/04/13 14:15:57 [Info] [2054180273] v2ray.com/core/app/dispatcher: taking detour [direct] for [tcp:ssl.gstatic.com:443]
2020/04/13 14:15:57 [Info] [2054180273] v2ray.com/core/proxy/freedom: opening connection to tcp:ssl.gstatic.com:443
2020/04/13 14:15:57 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: ssl.gstatic.com. TypeAAAA -> [] 46.551304ms
2020/04/13 14:16:00 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:16:00 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:16:00 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:16:01 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain ssl.gstatic.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:16:01 [Info] [2054180273] v2ray.com/core/proxy/freedom: dialing to to tcp:<IP_ADDRESS>:443
2020/04/13 14:16:01 [Info] [2054180273] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:<IP_ADDRESS>:443
2020/04/13 14:16:04 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/04/13 14:16:04 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2020/04/13 14:16:07 [Info] [113856771] v2ray.com/core/proxy/socks: TCP Connect request to tcp:clients4.google.com:443
2020/04/13 14:16:07 [Info] [113856771] v2ray.com/core/app/dispatcher: sniffed domain: clients4.google.com
2020/04/13 14:16:07 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:16:07 [Info] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:16:11 [Info] v2ray.com/core/transport/internet/udp: failed to write first UDP payload > io: read/write on closed pipe
2020/04/13 14:16:11 [Info] v2ray.com/core/app/dns: failed to lookup ip for domain clients4.google.com at server UDP:<IP_ADDRESS>:53 > context deadline exceeded
2020/04/13 14:16:11 [Info] v2ray.com/core/transport/internet/udp: establishing new connection for udp:<IP_ADDRESS>:53
2020/04/13 14:16:11 [Info] v2ray.com/core/app/dispatcher: taking detour [direct] for [udp:<IP_ADDRESS>:53]
2020/04/13 14:16:11 [Info] v2ray.com/core/proxy/freedom: opening connection to udp:<IP_ADDRESS>:53
2020/04/13 14:16:11 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: clients4.google.com. TypeA -> [<IP_ADDRESS>] 11.474103ms
2020/04/13 14:16:11 [Info] [113856771] v2ray.com/core/app/dispatcher: taking detour [v2-server] for [tcp:clients4.google.com:443]
2020/04/13 14:16:11 [Info] v2ray.com/core/app/dns: UDP:<IP_ADDRESS>:53 got answere: clients4.google.com. TypeAAAA -> [[2404:6800:4008:801::200e]] 12.197586ms

请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。

2020/04/13 14:14:19 tcp:<IP_ADDRESS>:49641 accepted tcp:twitter.com:443 [v2-server]
2020/04/13 14:14:19 tcp:<IP_ADDRESS>:49642 accepted tcp:abs.twimg.com:443 [v2-server]
2020/04/13 14:14:20 tcp:<IP_ADDRESS>:49647 accepted tcp:twitter.com:443 [v2-server]
2020/04/13 14:14:22 tcp:<IP_ADDRESS>:49656 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:22 tcp:<IP_ADDRESS>:49657 accepted tcp:pbs.twimg.com:443 [v2-server]
2020/04/13 14:14:22 tcp:<IP_ADDRESS>:49659 accepted tcp:t.co:443 [v2-server]
2020/04/13 14:14:22 tcp:<IP_ADDRESS>:49660 accepted tcp:twitter.com:443 [v2-server]
2020/04/13 14:14:22 tcp:<IP_ADDRESS>:49661 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:22 tcp:<IP_ADDRESS>:49658 accepted tcp:video.twimg.com:443 [v2-server]
2020/04/13 14:14:22 tcp:<IP_ADDRESS>:49662 accepted tcp:twitter.com:443 [v2-server]
2020/04/13 14:14:23 tcp:<IP_ADDRESS>:49667 accepted tcp:twitter.com:443 [v2-server]
2020/04/13 14:14:23 tcp:<IP_ADDRESS>:49673 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:24 tcp:<IP_ADDRESS>:49668 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:24 tcp:<IP_ADDRESS>:49674 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:24 tcp:<IP_ADDRESS>:49675 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:24 tcp:<IP_ADDRESS>:49676 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:52 tcp:<IP_ADDRESS>:49793 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:53 tcp:<IP_ADDRESS>:49798 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:54 tcp:<IP_ADDRESS>:49803 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:54 tcp:<IP_ADDRESS>:49804 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:54 tcp:<IP_ADDRESS>:49805 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:14:54 tcp:<IP_ADDRESS>:49806 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:22 tcp:<IP_ADDRESS>:49921 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:23 tcp:<IP_ADDRESS>:49926 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:24 tcp:<IP_ADDRESS>:49927 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:24 tcp:<IP_ADDRESS>:49928 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:24 tcp:<IP_ADDRESS>:49933 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:24 tcp:<IP_ADDRESS>:49934 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:24 tcp:<IP_ADDRESS>:49935 accepted tcp:twitter.com:443 [v2-server]
2020/04/13 14:15:52 tcp:<IP_ADDRESS>:50049 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:53 tcp:<IP_ADDRESS>:50054 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:54 tcp:<IP_ADDRESS>:50055 accepted tcp:api.twitter.com:443 [v2-server]
2020/04/13 14:15:57 tcp:<IP_ADDRESS>:50073 accepted tcp:ssl.gstatic.com:443 [direct]
2020/04/13 14:16:11 tcp:<IP_ADDRESS>:50126 accepted tcp:clients4.google.com:443 [v2-server]

仔细看了下log，貌似是因为dns一直失败或者返回错误IP的原因？
但是<IP_ADDRESS>的dns包应该也会转发到v2ray服务器呀，为什么也一直context deadline exceeded失败呢？以及为什么更换或重启客户端之后问题就会消失呢？

我也遇到过一些问题， 结合你的描述
”比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。“
我chrome浏览器安装了HTTP/2 and SPDY indicator
https://chrome.google.com/webstore/detail/http2-and-spdy-indicator/mpbpobfflnpcgagjijhmgnchggcjblin
发现只要是插件检测出网站服务器用的quic协议（HTTP3？），必定间歇性卡顿，具体表现为关闭这个网站（比如google），过一两分钟再打开， 就要卡几十秒。
我估计是不是go的quic库在某些特定场景下会有bug？ 或者v2ray一部分代码本来是处理v2ray传输协议quic的， 结果处理了payload中的quic？
解决：

chrome关闭quic
换safari

@cod1ingcoding 我升级了树莓派上v2ray的版本到4.23.0，（引入了一些DNS优化），又调整了一下DNS的配置，现在基本不再出现这个问题了。
但感觉之前的问题未必是QUIC的原因，因为QUIC与否在浏览器里就决定了，但我的情况换用本地v2ray客户端、或者重启树莓派上客户端，都可以使问题消失。

升级到4.23.4后，问题再次出现。重启V2Ray后问题消失，但不久之后又会重新出现。
怀疑新版的V2Ray进行DNS（我用的<IP_ADDRESS>）解析时，没有严格按照routing规则处理，有时会不通过代理，直接在墙内直接向<IP_ADDRESS>发起DNS请求。


Add upgrade notes in docs

Nice. LGTM, +1

It renders like this now: https://www.evernote.com/shard/s209/sh/b4fd4b22-e8f7-43eb-a0e1-aafdf0111aae/df3612a6b1df6795e3833f2f1215ffc8

LGTM, +1


Non-canonical signature: S value is unnecessarily high)' ,u'code':-26 (#2287)

When I try to make a payment , I receive this error during the "broadcasting"...
I am using:
Version Electrum-DASH 2.4.1

Please advise

Same error for me too. First got this(Link attached) error. Then after the suggested fix, seeing mentioned error. "error: {u'message': u'64: non-mandatory-script-verify-flag (Non-canonical signature: S value is unnecessarily high)', u'code': -26}"
Fix Link: https://support.node40.com/hc/en-us/articles/115002838488-My-Electrum-Dash-wallet-will-not-send-a-transaction-after-the-update-to-12-1

Please advise us on how to upgrade from 2.4.1 to 2.6.2

On พ. 15 มี.ค. 2560 at 20:04 parparanga<EMAIL_ADDRESS>wrote:

Please advise us on how to upgrade from 2.4.1 to 2.6.2
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dashpay/electrum-dash/issues/99#issuecomment-286734866,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKQsq9p5qwxQumz_2j2BKhnOusNF_UyMks5rl-HfgaJpZM4MbA_X
.

please try #91 or #95

Hi, the current Electrum Dash fork is maintained here: https://github.com/akhavr/electrum-dash
Please use that repo and report there if you have any issues.


Redirects, Hashed User Seed & Responsiveness

Layout should be responsive
Redirect UN-authenticated users to /login
Redirect all traffic not matching a specified endpoint (404) to /signup page
Update user seeds to contain PRE-hashed password for "password123"

Integrated prior to: commit e2dad405a122138516fa6c855f090b8a9621aca8 .


hope-ui does not work in Vitest

Describe the bug
When I ran simple vitest with Hope UI, I got the following error message.

SyntaxError: Named export 'addScrollableSelector' not found. The requested module 'scroll-lock' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from 'scroll-lock';
const { addScrollableSelector, disablePageScroll, removeScrollableSelector, clearQueueScrollLocks, enablePageScroll } = pkg;

To Reproduce
here is my component
import type { Component } from 'solid-js';

import {
    HopeProvider,Box
  } from "@hope-ui/solid";

export default function (Tes: Component ) {
    return (<HopeProvider><Box>test</Box></HopeProvider>)
}

and test code
import {describe, it, expect} from 'vitest';
import {render} from 'solid-testing-library';
import Tes from './Tes';

it('render test', () => {
    render(()=><Tes></Tes>);
});

OS: Linux
Version 0.6.7

I got the same error message.  Now I use uvu instead of vitest.

Hi, Not sure I can help since i've never used Vitest.
scroll-lock is an internal dependency which will be removed in 1.0, but I don't know if others internal dependencies will cause the same error.