The "type" argument in fs.symlink

This argument seems to be only respected on Windows, but it is currently not set correctly - it should be 'dir'. So is there any reason for the current behavior?
I suggest the type argument is removed from forceSymlink altogether and replaced with 'dir' where it is used.

Actually I think you need to use 'junction' to avoid the permissions issue on windows. but to do so the paths must be absolute.

I've just tested this in cmd and it worked without problem, will read about this a bit more.
This should also solve #35. Also the absolute paths should not a problem in this case so everything should work out.

Ok, there's a serious problem with that: even changing the main project directory name will invalidate all of the junctions.
I think that's too big of a trade-off, because there won't be a way to warn Windows users when such a thing happens, whereas in the worst case of the symbolic link scenario they will be able to get an informative message.
Also, a new command would have to be made that regenerates all of the junctions, and it would only be useful for Windows users.
What do you think @alexanderGugel?

I spent a long time today playing with this.  I could not get ide to run without admin.  You might have better luck.  Take a look at  this: https://github.com/npm/npm/blob/master/lib/utils/link.js

It seems that they also use junctions. Anyway, I'm looking into utilizing powershell for creating symlinks painlessly.

:+1:

Yeah, from what I see ied (nom?) is much more symlink heavy.  junction links my be a bad idea.  Do you think using power shell will get around the need for admin?

I'm closing this, as it has been inactive for quite some time. I'm really sorry I didn't help with this as I promised.

@fatfisz have you tried pnpm. It uses a symlinked node_modules as ied and supports Windows fine (uses junctions on Windows)


chore: add exponential rebate tldr

https://github.com/graphprotocol/docs/pull/454#issuecomment-1672359973
@howard-the-graph please confirm if this looks good to go.

Separately, the phrase "by the gateway and" should be removed from the first sentence of the paragraph.

@alex-pakalniskis – Uhhh yeah that's weird:

I can't imagine the change in this PR introducing any sort of failure, so I would just ignore it yes.

cc @saihaj @B2o5T ☝


Update crazyflie_tools, disabling safelink

Resolves #185
add updated crazyflie_tools with updated crazyflie_cpp (disabling safelink)

I am fine with merging this, but technically I am not sure why this solves #185. In Crazyflie_ros, crazyflie_cpp is already a submodule (which seems to have the latest version) and if you build using catkin_make it should use the crazyflie_cpp that is directly a submodule in this repository, not the one that is a submodule in crazyflie_tools.

Yeah I found it a bit odd as well. The build itself works fine, but somewhere in the logic the crazyflie_cpp in crazyflie_tools gets run and that is causing the error I face.

Thanks for the real fast responses @whoenig!


Create a status update deck for GCDevEx

Deck will be used at the next meeting with Martin, Julie and Mathieu.
To include details on the work with CFOB, mental MVP, resources required, costs.

DG Comm presentation..
https://sara-sabr.github.io/ITStrategy/presentation.html?markdown=en/2020-GCDevEx-DG-Comm.md

Status update deck for Mathieu not needed for now


Rename Repository?

Should I rename this to "night" with a lowercase "n"? @firefish111

Nah, Night is fine, for me at least

it is grammatically correct... so no

no need to, but, you could


Update the Github Action "Test Simple Example with Poorly Formatted Code Change" to use bazel_integration_test with a custom runner.

Related to #30.

Duplicate of #30.


Debug jumps in etendue for spectrometer concave crystals

Main changes:
Two minor bugs identified in the routines used to project an aperture (slit) on a concave crystal.
Concavity comes with numerical instability when the root-finding process comes close to the singular point that is the center of curvature.
Tofu implements a robust root-finding routine + interpolates reflected polygons to take out singular points.
Bug 1: the interpolation process was missing some corners of the polygons in some particular cases.
Bug 2: the root-finding algo wasn't robust enough for some particular pixels / configurations
Both bugs have been addressed in this PR, see issue #747 for examples
Several plotting / debugging sections have been added to the code to facilitate any later debugging in case another problem arises. They are commented out and left as such for later use.
Issues:

Fixes, in devel, issue #747

Just flipping plotting data through diag.plot_diagnostic() things look good except for dlamb and res. This is more so related to what's stated in Issue #748 than what's addressed here. Attached is a plot of dlamb from diag.plot_diagnostic(). Also attached is repeating the comparison plot given in Issue #748 to illustrate that the factor is still about off the same amount, but the shape changed from what you did here

Well spotted (dlamb), as you mention, it's more related to issue #748 , will try to address that tomorrow morning

Definitely changed some things up with the magnitude of dlamb. The prefactor to rescale it to just being the spacing in the wavelength mesh is now ~3.5 (previously ~4.3).
Much less noisy though. The relative difference between the two meshes shown is now 1e-6%. So any difference in the first attached plot is really the subtraction I did for visualization.
The additional computational time isn't terrible. Might have slowed down "build diagnostic" section in tofu_sparc by say 50%-ish so not the end of the world.


Token refresh refires requests in Angular

I implemented this package in Angular but every time the token refreshes it refires previous HTTP calls. Does somebody have an idea how this can happen?

Using angular 9

That's probably your code on the redirect_iri or silent_redirect_uri page.

this is my silent-renew.html

and this is my signin-callback.html

I need to have the config for the metadata

this is my console with oidc client in debug, ng-oidc-client package but i had the same problem when i used my own NGRX auth package

I also noticed the blocked requests are using the old Bearer token.

So the problem was with my intercepter in Angular and getting the token from the store via an observable, I had to terminate the observable using take(1). So it isn't a bug from this package, closing it now.


Can't draw or flag on the minimap unless "Lock Size" is ticked

Removed lock size option for minimap


Update nokogiri to 1.10.4 to fix CVE

LGTM ;)

"Affected versions of this package are vulnerable to Command Injection via the undocumented method  Nokogiri::CSS::Tokenizer#load_file. This allows commands to be executed in a subprocess."


BigQuery Service Account Support

The TSC library doesn't yet support the BigQuery Service Account Authentication feature:
https://community.tableau.com/s/idea/0874T000000HBbWQAW/detail
I haven't found a way to do it with the Native API:
https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_data_sources.htm#publish_data_source
So this seems to be an undocumented feature and the community cannot make the change themself.
Please add this feature to this official library so we can use it!

Any news on that issue? I have the same problem.

The internal team working on this tells me it has not been a priority for them yet, sorry.


Coalesce sum queries

Task/Issue URL: https://app.asana.com/0/488551667048375/1203268720887505/f
Description
Coalesce the SUM db queries to avoid null return values
Steps to test this PR
Fresh install

[x] Fresh install the app
[x] Enable AppTP (going through onboarding)
[x] Verify onboarding flow succeeds
[x] Open any app that tracks and verify trackers are being blocked

Current dependencies on/for this PR:

develop

PR #2472   👈

This comment was auto-generated by Graphite.


feature: add JavaScript codegen

Summary

closes #39
Adds functionality to check the output file type to enable JS codegen. When .js or .mjs, will output JS ESM code, when .cjs, will output CommonJS code.
Both JS format types will output fully typed code using JSDocs.
Additionally, can override the file type with --output-type, which accepts TS, CJS, or ESM and defaults to TS. Will not change the extension used. This was added so you can generate a .js as CommonJS and a way to output CommonJS to stdout.
Why bother
I use JSDocs + the typebox check compiler to get fast runtime checks for external inputs.

@xddq let me know if you want me to squash early, figured you could squash what you want on merge

@xddq im so used to not be able to run formatters x.x mb. ran it / checked wfs on the fork now


Mock dynamic url's

Hi. I'm developing weather forecast app. Front-end of my app makes different get queries to server like this:
localhost:3000/api/weather/22.30935/113.921988888889/1447970462561
localhost:3000/api/weather/49.13234/22.679924588889/1447938462456
Is there any way to mock this dynamic routes by your module?
For example: can I use something like this:
mock([{
request: {
path: 'localhost:3000/api/weather///*',
method: 'GET'
},
response: {
status: 200,
data: {}
}
}]);
???
Thanks.

@alexandrmatsyuk92 are you expecting to mock different responses for each dynamic route?
You could define an expectation with simply "api/weather", but I doubt that will be sufficient for you. Perhaps a better approach could be to be able to define a function that returns the response data as opposed to a static JSON definition. That's not currently an option at the moment.


Deepspeed zero optimizer, error converting model checkpoints

Describe the bug
Unable to convert a custom gpt-neox model (with zero stage 3) checkpoints using zero_to_fp32.py script.
To Reproduce
Train a model with zero stage 3, pp=0, mp=1 (haven't attempted other combinations). Save checkpoint.
Run the zero_to_fp32.py script, attached to the saved checkpoint.
Environment (please complete the following information):

GPUs: training on 4x A100, convert attempted on: same as training, 4x 2080ti, 1x 2080ti, cpu
Configs: 12 layer gpt, zero stage 3, pp=0, mp=1

Attempted so far
Run as is:
Detected checkpoint of type zero stage 3, world_size: 4
Traceback (most recent call last):
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 151, in <module>
    convert_zero_chkpt_to_fp32_consolid_state_dict(args.checkpoint_dir, args.output_file)
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 121, in convert_zero_chkpt_to_fp32_consolid_state_dict
    state_dict[name] = torch.cat(
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cuda:1! (when checking argument for argument tensors in method wrapper___cat)

Limit env to 1 GPU:
Traceback (most recent call last):
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 151, in <module>
    convert_zero_chkpt_to_fp32_consolid_state_dict(args.checkpoint_dir, args.output_file)
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 83, in convert_zero_chkpt_to_fp32_consolid_state_dict
    zero_stage, world_size, param_shapes, fp32_flat_groups = parse_optim_states(optim_files)
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 39, in parse_optim_states
    state_dicts.append(torch.load(f))
  File "/home/mulcar/.conda/envs/gptneox/lib/python3.9/site-packages/torch/serialization.py", line 607, in load
    return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
  File "/home/mulcar/.conda/envs/gptneox/lib/python3.9/site-packages/torch/serialization.py", line 882, in _load
    result = unpickler.load()
  File "/home/mulcar/.conda/envs/gptneox/lib/python3.9/site-packages/torch/serialization.py", line 857, in persistent_load
    load_tensor(data_type, size, key, _maybe_decode_ascii(location))
  File "/home/mulcar/.conda/envs/gptneox/lib/python3.9/site-packages/torch/serialization.py", line 846, in load_tensor
    loaded_storages[key] = restore_location(storage, location)
  File "/home/mulcar/.conda/envs/gptneox/lib/python3.9/site-packages/torch/serialization.py", line 175, in default_restore_location
    result = fn(storage, location)
  File "/home/mulcar/.conda/envs/gptneox/lib/python3.9/site-packages/torch/serialization.py", line 151, in _cuda_deserialize
    device = validate_cuda_device(location)
  File "/home/mulcar/.conda/envs/gptneox/lib/python3.9/site-packages/torch/serialization.py", line 142, in validate_cuda_device
    raise RuntimeError('Attempting to deserialize object on CUDA device '
RuntimeError: Attempting to deserialize object on CUDA device 1 but torch.cuda.device_count() is 1. Please use torch.load with map_location to map your storages to an existing device.

Adding map_location argument to torch.load as per above error
Detected checkpoint of type zero stage 3, world_size: 4
Traceback (most recent call last):
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 151, in <module>
    convert_zero_chkpt_to_fp32_consolid_state_dict(args.checkpoint_dir, args.output_file)
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 122, in convert_zero_chkpt_to_fp32_consolid_state_dict
    tuple(fp32_flat_groups[i].narrow(0,
  File "/home/mulcar/gpt-neox/checkpoints-sl-small/./zero_to_fp32.py", line 122, in <genexpr>
    tuple(fp32_flat_groups[i].narrow(0,
RuntimeError: start (27432576) + length (6168576) exceeds dimension size (33570816).

I have also attempted to convert with deepspeed's latest script, but I got an error that it's not a model state checkpoint, so I figure the differences between current deeperspeed and latest deepspeed are too great to be of any use. Please advice on how I could salvage, ie. actually use the model for inference/evaluation other than training again from scratch.

Hmmm. We haven’t really been using ZeRO 3, as our testing indicates that it’s a big step up in complexity for a minimal increase in performance. It’s possible we broke something without realizing it.
I’ll have to train a model and play with it a bit. Hopefully we can get this resolved.

I've figured it's less bother to train from scratch without ZeRO 3, seeing how GPUs were under-utilized in the original run. Either way, I can share the trained model https://drive.google.com/drive/folders/13Z4g4eGFd33yhI2HWj4EM4G6lGw2W24D?usp=sharing The config files included in the archive, the model config here:
{
   # parallelism settings ( you will want to change these based on your cluster setup, ideally scheduling pipeline stages
   # across the node boundaries )
   "pipe-parallel-size": 0,
   "model-parallel-size": 1,

   # model settings
   "num-layers": 12,
   "hidden-size": 768,
   "num-attention-heads": 12,
   "seq-length": 2048,
   "max-position-embeddings": 2048,
   "norm": "layernorm",
   "pos-emb": "rotary",
   "no-weight-tying": true,
    # this should provide some speedup but takes a while to build, set to true if desired
   "scaled-upper-triang-masked-softmax-fusion": false,
   "train-iters": 80000,

   # optimizer settings
   "optimizer": {
     "type": "Adam",
     "params": {
       "lr": 1.0e-5,
       #"freeze_step": 5000,
       "betas": [0.9, 0.999],
       #"cuda_aware": false,
       #"comm_backend_name": "nccl"
     }
   },

   "zero_optimization": {
    "stage": 3,
    "allgather_partitions": True,
    "allgather_bucket_size": 100000000,
    "overlap_comm": True,
    "reduce_scatter": True,
    "reduce_bucket_size": 100000000,
    "contiguous_gradients": True,
    "cpu_offload": False
  },
  "zero_allow_untested_optimizer": true,

   # batch / data settings
   "train_micro_batch_size_per_gpu": 8,
   "gradient_accumulation_steps": 4,
   "data-impl": "mmap",
   "split": "949,50,1",

   # activation checkpointing
   "checkpoint-activations": true,
   "checkpoint-num-layers": 1,
   "partition-activations": true,
   "synchronize-each-layer": true,

   # regularization
   "gradient_clipping": 1.0,
   "weight-decay": 0.05,
   "hidden-dropout": 0.1,
   "attention-dropout": 0.1,

   # precision settings
   "fp16": {
     "enabled": true,
     "loss_scale": 0,
     "loss_scale_window": 500,
     "hysteresis": 2,
     "min_loss_scale": 1,
   },

   # lr decay settings
   "lr-decay-iters": 80000,
   "lr-decay-style": "cosine",
   "warmup": 0.01,

   # misc. training settings
   "distributed-backend": "nccl",
   #"save-interval": 10000,
   #"eval-interval": 1000,
   "save-interval": 500,
   "eval-interval": 100,
   "eval-iters": 10,

   # logging
   #"log-interval": 100,
   "log-interval": 10,
   "steps_per_print": 10,
   "keep-last-n-checkpoints": 4,
   "wall_clock_breakdown": true,

  # sparse attention
  #"attention_config": [[["local", "global"], "all"]],
}

We do not currently support ZeRO 3, which seems to be the core source of your issue. Closing for now.


renaming multiclusterhub-repo to multiclusterhub repo; updating githu…

…b actions for chart pushing

@jlpadilla looks like it didn't merge by itself :-/


[Bug]: Windows path - Invalid Parameter

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
Expected to run the "dev" command to start development,
Actual behavior
Testing Shopify app development, I ran the command "yarn dev" and I got an error of "exit code 1". I also tried npm. I exported the logs, and the path name seems to be an issue.
Stack trace
yarn run v1.22.10
$ shopify logs
Invalid parameter - /Users
Done in 1.85s.

Reproduction steps

Install @shopify/cli to latest version (3.12.0 for bug)
Create app using "yarn create @shopify/app"
Run "yarn dev"an

Operating System
Windows 11
Shopify CLI version (check your project's package.json if you're not sure)
3.12.0
Shell
Powershell
Node version (run node -v if you're not sure)
v16.15.0
What language and version are you using in your application?
Node 16

Hi! I'm not able to reproduce it. Could you please run yarn dev --verbose and share the output?


Use itertools to process the min_value and max_value in statistics

Hello!
Currently, when processing the statistics, the array is scanned twice to get the min and max value.
The Itertools::minmax_by can do the same and faster, needing to go through 1.5 * n elements, rather than 2 * n elements, for an array of n elements.

Thanks for your PR @GrandChaman.
I think we could do this optimization without the need of adding a new dependency. We could write a function that tracks both in a single pass for instance.

Also, are you sure it's faster or has a big impact?
As we are using primitive arrays, wouldn't it make sense here to use the optimized compute kernels here instead?
This has further optimizations / vectorization compared to using array.iter().flatten() etc.

@ritchie46 The dependencies was already in arrow2, although not with the feature io_parquet. I agree it'd be best not to add new dependencies, I just wanted to test quickly without re-implementing what itertools had to offer.
@Dandandan  From my testing, it is faster. But I agree maybe the compute kernel are better suited for this task.

Thanks a lot for this! This is a good point.
@Dandandan , exactly: I did not want to drag that dependency just to read/write parquet. I like @ritchie46 's idea: if we have the kernel already in the features, use it; else, use a simple iteration / our own implementation of minmax.
An alternative that would also be fine is to see if itertools offers features that we can pick via default-features = false, features = [...] to reduce the dependency to its minimum (itertools is pretty large).


Adding new pipeline without gridsearch

new pipeline for use in ihc-image-analysis.

Ben, I already changed this in the last commit along with cleaning up a lot of code from previous experimentation that we were no longer using. Probably shouldn't have bundled these changes together but I was having trouble re-installing the library (I think due to some Python 2 / 3 switching at some point). I've also made the update to the web app to use the updated version.


T07: Fix fingerprint generator error

Description
Fixed fingerprint generator function to give a vector as an output #360
convert fpg.GetCountFingerprint(mol) to  fpg.GetFingerprint(mol) in smiles_to_fp function
Status

[ ] Ready to go

@hamzaibrahim21, could you please

add this PR to the PR description of the dev base branch so that we can keep track? (I think at the minute the issue is linked instead)
add a more descriptive title* and description

*"T007:" as prefix (see the other PR titles) also helps for a quick overview of which notebooks are worked on at the moment, thank you!

Do you know why there are conflicts with dev? Because of the direct pushs regarding T007 on dev(I see you reverted some things, so do I misunderstand)

@dominiquesydow Thanks for the notes, Done :+1:
I pushed the changes directly into dev branch, but it was requested to do it in a PR so I reverted it and pushed it again  in a different branch to be able to do a PR. Sorry for the confusion.

@dominiquesydow I will deal with the merge. It's usually straight-forward. Just some changed memory addresses in the output etc.


How to upload a file on s3  using vb6

How to upload a file on s3  using vb6 or vbscript
Is fine upload support vb6 or vbscript?

A Fine Uploader S3 signing server can be implemented in almost any language you wish. However only PHP, Java, and Node.js example servers are actively maintained by the FU team (though a few other examples are included). To leverage this functionality within VB6 or VBScript you will need to write you own server, which is a fairly simple endeavor and is heavily documented.
If you have any further questions that are not actual issues or feature requests, please ask within StackOverflow.

Is it possible you will send me the response formats that we use in fine uploader so that I can write my own code for it?

Everything you will need to know in order to create your own server can be found in our documentation as well as an in-depth, step-by-step blog post.

I am using below Policy format and creating a application/json format with policy base 64 and signature sha base 64 but getting "Error attempting to parse signature response: SyntaxError: Unexpected token s" error. Can you suggest where I am wrong:
strToPolicy =  "{""expiration"": ""2015-01-01T12:00:00.000Z"", ""conditions"": [ {""bucket"": manishtests3.s3-website-ap-southeast-1.amazonaws.com }, {""acl"": ""public-read"" },{""key"": my access key id},{""x-amz-meta-qqfilename"": Search.png}, ]}"

This issue tracker is not for general troubleshooting. Please leverage StackOverflow.


Undefined variable: "$spacer-1".

We are seeing this error when using<EMAIL_ADDRESS>Pinning to 1.0.2 resolved it for us.
[sass]  error: Undefined variable: "$spacer-1".

in /Users/z/git/electron/electron.atom.io/node_modules/primer-breadcrumb/lib/breadcrumb.scss:3:17
Error: Undefined variable: "$spacer-1".
    at options.error (/Users/z/git/electron/electron.atom.io/node_modules/node-sass/lib/index.js:291:26)
[sass]  error: Undefined variable: "$spacer-1".

in /Users/z/git/electron/electron.atom.io/node_modules/primer-breadcrumb/lib/breadcrumb.scss:3:17
Error: Undefined variable: "$spacer-1".
    at options.error (/Users/z/git/electron/electron.atom.io/node_modules/node-sass/lib/index.js:291:26)
^C

~/git/electron/electron.atom.io neo* 4m 17s
$ npm ls primer-breadcrumb
<EMAIL_ADDRESS>/Users/z/git/electron/electron.atom.io
└──<EMAIL_ADDRESS>
🍐 @vanessayuenn

@zeke You probably need to update the version of primer-support you're on. primer-support is a dependency for the breadcrumbs module and has had the spacer variables in it for a while, but we only recently updated primer-breadcrumb to use those variables. Updating support should fix this though.

I think we're still on the pinned version. Should I try latest?

We're still seeing the same error with<EMAIL_ADDRESS>😿
=> npm ls primer-support
<EMAIL_ADDRESS>/Users/vanessayuenn/Projects/electronjs.org
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

@zeke @vanessayuenn Have you tried updating to the latest version of primer-support as suggested above?

@broccolini we have<EMAIL_ADDRESS>which seems to be the latest version already?

This seems to have been resolved in<EMAIL_ADDRESS>Thanks!
https://github.com/electron/electronjs.org/pull/968

Yay for code that fixes itself


特定网络无法连接到服务器，retry: all retry attempts failed

用了cloudfare，移动网络没问题，但是有些wifi下连接不上。附带客户端日志：
Last login: Thu Jan 20 18:52:27 on ttys000
/Users/%%%%%/Downloads/APP/macos-64/v2ray ; exit;
%%%%%@bogon ~ % /Users/%%%%%/Downloads/APP/macos-64/v2ray ; exit;
V2Ray 4.44.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.17.3 darwin/amd64)
A unified platform for anti-censorship.
2022/01/21 09:41:16 Using config from env:  /Users/%%%%%/Downloads/APP/macos-64/config.json
2022/01/21 09:41:16 [Info] main/jsonem: Reading config: /Users/%%%%%/Downloads/APP/macos-64/config.json
2022/01/21 09:41:16 [Warning] V2Ray 4.44.0 started
2022/01/21 09:41:30 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:34 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:36 tcp:<IP_ADDRESS>:57803 accepted tcp:www.google.com:443
2022/01/21 09:41:36 tcp:<IP_ADDRESS>:57804 accepted tcp:www.google.com:443
2022/01/21 09:41:36 tcp:<IP_ADDRESS>:57808 accepted tcp:www.google.com:443
2022/01/21 09:41:38 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:46 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:50 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:52 tcp:<IP_ADDRESS>:57826 accepted tcp:www.google.com:443
2022/01/21 09:41:54 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:57 [Warning] [3887581697] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:57 [Warning] [3549885513] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:41:57 [Warning] [1202936345] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:01 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:05 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:07 tcp:<IP_ADDRESS>:57857 accepted tcp:www.google.com:443
2022/01/21 09:42:09 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:13 [Warning] [1208641022] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:28 [Warning] [2979637715] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:36 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:40 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:42 tcp:<IP_ADDRESS>:57884 accepted tcp:www.google.com:443
2022/01/21 09:42:42 tcp:<IP_ADDRESS>:57886 accepted tcp:clients4.google.com:443
2022/01/21 09:42:44 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:46 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:50 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:42:52 tcp:<IP_ADDRESS>:57899 accepted tcp:www.google.com:443
2022/01/21 09:42:54 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:03 [Warning] [4268773911] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:03 [Warning] [4213785335] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:13 [Warning] [1858500987] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:36 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:40 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:42 tcp:<IP_ADDRESS>:57944 accepted tcp:www.google.com:443
2022/01/21 09:43:44 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:46 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:50 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:43:52 tcp:<IP_ADDRESS>:57954 accepted tcp:www.google.com:443
2022/01/21 09:43:54 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:44:03 [Warning] [3411733163] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:44:13 [Warning] [3317133765] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:44:46 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:44:50 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:44:52 tcp:<IP_ADDRESS>:57993 accepted tcp:www.google.com:443
2022/01/21 09:44:52 tcp:<IP_ADDRESS>:57992 accepted tcp:www.google.com:443
2022/01/21 09:44:54 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:45:13 [Warning] [1482199794] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:45:13 [Warning] [826903653] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:45:57 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:55277->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:65127->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:56341->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:62209->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:50809->[::1]:53: read: connection refused] > common/retry: all retry attempts failed
2022/01/21 09:46:01 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:57340->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:64955->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:60124->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:55367->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:50384->[::1]:53: read: connection refused] > common/retry: all retry attempts failed
2022/01/21 09:46:05 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:59272->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:52346->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:61198->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:58633->[::1]:53: read: connection refused transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: lookup .com on [::1]:53: read udp [::1]:58121->[::1]:53: read: connection refused] > common/retry: all retry attempts failed
2022/01/21 09:46:07 tcp:<IP_ADDRESS>:58057 accepted tcp:mtalk.google.com:443
2022/01/21 09:46:28 [Warning] [3131147391] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:46:31 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:46:35 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:46:37 tcp:<IP_ADDRESS>:58094 accepted tcp:<IP_ADDRESS>:443
2022/01/21 09:46:39 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:46:55 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:46:58 [Warning] [1816821724] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:46:59 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:01 tcp:<IP_ADDRESS>:58116 accepted tcp:www.google.com:443
2022/01/21 09:47:01 tcp:<IP_ADDRESS>:58118 accepted tcp:www.google.com:443
2022/01/21 09:47:03 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:04 tcp:<IP_ADDRESS>:58121 accepted tcp:www.google.com:443
2022/01/21 09:47:22 [Warning] [4212140618] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:22 [Warning] [4092084348] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:25 [Warning] [90637086] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:32 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:36 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:38 tcp:<IP_ADDRESS>:58173 accepted tcp:clients4.google.com:443
2022/01/21 09:47:40 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:46 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:50 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:52 tcp:<IP_ADDRESS>:58197 accepted tcp:www.google.com:443
2022/01/21 09:47:52 tcp:<IP_ADDRESS>:58196 accepted tcp:www.google.com:443
2022/01/21 09:47:54 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:47:59 [Warning] [2675733680] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:48:13 [Warning] [2099953976] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:48:13 [Warning] [2767303155] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:54:46 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:54:50 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:54:52 tcp:<IP_ADDRESS>:58345 accepted tcp:www.google.com:443
2022/01/21 09:54:52 tcp:<IP_ADDRESS>:58344 accepted tcp:www.google.com:443
2022/01/21 09:54:54 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:55:13 [Warning] [1323918074] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:55:13 [Warning] [692047762] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:01 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:05 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:07 tcp:<IP_ADDRESS>:58399 accepted tcp:mtalk.google.com:5228
2022/01/21 09:57:09 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:28 [Warning] [1931763929] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:31 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:35 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:37 tcp:<IP_ADDRESS>:58426 accepted tcp:<IP_ADDRESS>:5228
2022/01/21 09:57:39 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:57:58 [Warning] [1513849320] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:19 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:23 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:25 tcp:<IP_ADDRESS>:58460 accepted tcp:www.google.com:443
2022/01/21 09:58:26 tcp:<IP_ADDRESS>:58464 accepted tcp:www.google.com:443
2022/01/21 09:58:26 tcp:<IP_ADDRESS>:58465 accepted tcp:www.google.com:443
2022/01/21 09:58:27 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:46 [Warning] [2273104661] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:46 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:47 [Warning] [100521058] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:47 [Warning] [3446423236] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:50 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:58:52 tcp:<IP_ADDRESS>:58493 accepted tcp:www.google.com:443
2022/01/21 09:58:54 [Warning] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 09:59:13 [Warning] [492049088] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 172.67..:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://.com/ray):  > dial tcp 104.21..:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://******.com/ray):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed

同样的问题：
2022/01/21 22:40:56 [Warning] [4192999151] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://domain.com/s5s55771a0/):  > dial tcp <IP_ADDRESS>:443: operation was canceled transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://domain.com/s5s55771a0/):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed
2022/01/21 22:40:56 [Warning] [3501525843] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: failed to find an available destination > common/retry: [transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://domain.com/s5s55771a0/):  > read tcp <IP_ADDRESS>:59773-><IP_ADDRESS>:443: i/o timeout transport/internet/websocket: failed to dial WebSocket > transport/internet/websocket: failed to dial to (wss://domain.com/s5s55771a0/):  > dial tcp: operation was canceled] > common/retry: all retry attempts failed

服务端来自：https://github.com/wulabing/V2Ray_ws-tls_bash_onekey
客户端v2rayn

应该是你网络环境的问题，请自行检查网络是否通畅。

how resolve it!!!

same issue here

same issue here

same issue here

did you resolve it?

did you fix it?


ocsp: reject ocsp responses where version is not v1

See #20079. In the event that updates to the OCSP specification are released and the OCSP response version is incremented, Envoy would currently accept the new data but might not correctly parse or interpret it. Envoy should explicitly reject versions other than v1 (a value of 0).

I think #20406 fixed this.


Why compiled function of module code return development source file path?

Nuitka Version: 0.6.7

In [3]: some_method
Out[3]: <compiled_function some_method at 0x0000000004DB2862>
In [4]: some_method.code
Out[4]: <code object some_method at 0x0000000004DB2862, file "E:\proj\win32\cmn.py", line 10>

The path file "E:\proj\win32\cmn.py"  ,how can i remove or strip it ?

This is described in the help output. Also the user manual will reveal information to you. You need to pick appriopiate modes to influence these things.


Remove window.__NUXT__

Describe the feature
Apparently it only exists for backwards-compat according to code comments:
https://github.com/nuxt/nuxt/blob/648ef069931336b8ee0c0e48fef3ee700ebc3dbe/packages/nuxt/src/app/plugins/revive-payload.client.ts#L52-L53
Nuxt v4 might be a good point to remove it if that's the case.
PR: #19205
Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

I'm not familiar with internal Nuxt codebase but as a user of Nuxt, I kind of enjoy using window.__NUXT__ to access data when Vue devtools are not available. I often look at pinia store through window.__NUXT__.pinia. And even cooler is that it is also available on prod which makes debugging really pleasant.

@martinszeltins you can use window.useNuxtApp in Nuxt 3 for that 😋
Here is a link to the PR introducing it and to a video about it I made

@martinszeltins you can use window.useNuxtApp in Nuxt 3 for that 😋 Here is a link to the PR introducing it and to a video about it I made

Ah, I wasn't aware of window.useNuxtApp, I guess in that case window.__NUXT__ is indeed not needed anymore.

In the case of closed SSR, currently window. Write too much unnecessary code, SPA application is not very friendly, there is no way to remove

Is there a way to use a micro front-end?


Does it work in hololens?

I want to use ffmpeg in hololens, so I need the dll which can be used in hololens. How could I build it with this repo?

Hi @ZhengzhongSun,
Yes, this would work on Hololens as it builds a Universal Windows Platform compatible binaries.

@khouzam hololens should use BuildFFmpeg.bat win10?

Yes, that will build all architectures for Windows 10. You can specify run BuildFFmpeg.bat win10 win32 to only build the binary for x86 which is what HoloLens should run.

@khouzam Thanks. It works. But I used it to decode a 2048*2048 h264 video, it seems a little slow.

@khouzam Does ffmepg support hardware decode in hololens?

From our implementation, using ffmpeg will not do hardware decoding, only software as we are using memory buffers to pass the information around. Depending on the type of media that you're trying to play, you can combine using FFmpeg and MediaFoundation to achieve much better media support while keeping great performance (this was one of the goals of this project). A lot of the decisions on how to proceed and what to use depends on the media format that you are trying to play. If you're looking to playback an h.264 video, that is usually able to be decoded in hardware by most Windows platforms. You can still leverage ffmpeg to parse the container and playback formats that are not natively supported by Windows (xvid, divx, rtsp for example), while still levaraging the hardware capabilities of the device.
If you have the video playing, have you tried to set the ForceDecode parameter to false for the video stream and see if that works? With details about the videos and protocols that you're trying to play, we can help guide on the best way to achieve a great experience.

@ZhengzhongSun You can try out the better optimized fork, where you can actually get some more support
https://github.com/lukasf/FFmpegInterop

@khouzam I didn't find the ForceDecode parameter

@khouzam @mcosmin222 Thank you very much! Since my demand is simple, I decide to use the hardware decoder for h264 directly. I find the ICodecAPI interface which can enable the hardware acceleration. https://msdn.microsoft.com/en-us/library/windows/desktop/dd742712(v=vs.85).aspx
But I'm not familiar about the decode part and there are no sample code about it. Any suggestion would be appreciated!

You do not need that interface. In the context of MediaStreamSource, you need
VideoEncodingProperties::CreateH264()
Then you read packages from the stream and send them to the OS for hardware acceleration.
In FFmpegInterop, if you set "videoDecode" to false, it will automatically pass through all the video packages undecoded. This will use directx APIs to do the decoding on the GPU.

Hi,
I have issues with building dll for Unity for Hololens. Could you please provide this file? Thanks in advance.

Hi,
I have issues with building dll for Unity for Hololens. Could you please provide this file? Thanks in advance.

Hi,
Is your problem solved? I have encountered such a problem.


Make the URL of Testing Farm results more visible

Closes #107

@nikromen could you please add release note to the description? Format should be something like:
‹text that will be included in blog›

---

Closes #107


about pretrained

作者你好，我认为你的工作非常令人振奋，麻烦请问一下，我看代码里面并没有加载mamba的预训练，如果使用的话，结果会不会更好呢

Hi, we did not use mamba pre-training in VM-UNet, LightM-UNet and UltraLight VM-UNet at that time in order to ensure fairness of comparison. But based on past experience, if mamba adopts pre-training, the performance will be slightly improved.

Hello author! Regarding your code, I'd like to know how to use mamba or vmamba's pretraining to adapt it to other different image tasks, rather than building it from scratch.


[vicuna.py] Allow to pass extra arguments to iree-compile

Add a new flag --Xiree_compile to forward extra compiler arguments to iree-compile. This flag can be set multiple times to pass more than one extra argument.

Ping.


Fix running tests in template builds

From suggestion here https://github.com/godotengine/godot/issues/88439#issuecomment-1950255250
Ran into this unexpectedly previously which led to finding errors in the no-3D build, but decided to change this to avoid unexpected defaults, still allows tests to be run if desired

I did some testing and it doesn't really make sense to have tests enabled with export, will look at disabling it completely for this as well

I did some testing and it doesn't really make sense to have tests enabled with export, will look at disabling it completely for this as well

What are the issues? In theory it seems useful to me that we can run unit tests on non-tools builds (especially the release template), to validate that the API behaves as intended even in release builds.
It's not something we would enable for official export templates of course, but ideally we would run such tests on CI. If some tests depend on editor-only functionality, they should be #ifdef TOOLS_ENABLED away.

Indeed, will look deeper into the specific issues, but there are some tests that simply won't work without even being in the correct directory, but will leave this for later digging and not add it here
Note that we couldn't use it in CI unless we do an export completely as the template binary can't be run then

That's strange it popped up the dialog for me first, you're right it works fine in that case, then no worries here, then I'll just leave it as such for now :)

Well actually in second thought, since dev_mode is for engine developers, I do think we should have tests enabled by default in dev builds even for templates. We just need to fix the bugs with running tests, by disabling the tests which can't work.

I'll take a look :)

Identified the first issue, the file modules/gdscript/tests/scripts/analyzer/errors/cyclic_ref_override.gd crashes on release builds, unsure how to fix that, will see if I can get better output details

For now I'm disabling some of the offending GDScript tests, to be fixed later, and fixing some other tests and improving them, will push soon

There, some temporary fixes in there but this makes it possible to generally run tests, with some improvements
There are still some test cases that fail on disable_3d builds but will look into those specifically in a separate PR as they're a bit trickier

Thanks!

Thank you!


Bump Dependencies #9782026025

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/9782026025

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


”document“ should not appear in the Worker.

Describe the bug
I use Comlink to work with Worker.
It's seems like:

And to use:
  const worker = new Worker(new URL("./Decoder", import.meta.url), { type: "module" });
  const decode = Comlink.wrap<typeof AVIFDecode>(worker);

Then, everything is fine with dev, but after building:

Reproduction
https://github.com/Aloento/ErrorRepo
Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Possible original code for this:

It seems like optimizer remove the if statement.

Yes, when I set build.minify: false, then, it works well.

For a workaround use worker.format.
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  worker: {
    format: 'es' // here
  }
})

Opening as this is a bug

can you give me the idea to replicate this @sapphi-red @Aloento


Adds an installation guide for Cilium on clusters built with RKE

Adds an installation guide for Cilium on clusters built with Rancher Kubernetes Engine
Fixes: #11380
Signed-off-by: Sean Winn<EMAIL_ADDRESS>

Coverage decreased (-0.03%) to 42.542% when pulling fdd8e4a5d73bbd64658866b172aed5934b38883c on seanmwinn:cilium-11380 into 3c25373901605acb9d8615ae2f0ba68e5a78ac18 on cilium:master.

@seanmwinn when you get a chance, could you go back through each point in the above feedback and mark the bits that you've fixed up as "resolved" and/or respond to the comments to discuss whether further action is necessary / clarify what further action?

I'll defer to @seanmwinn , so don't treat any of my comments above as blocking this commit.


secondary index

Does etcd support a secondary index?
If yes, which kind of index according to this table:
https://raw.githubusercontent.com/cockroachdb/cockroach/c3bc53a463f0a7036dcea06ac6d109d3ef2aa4fe/resources/doc/scan-efficiency.png

no. it does not support.

Will we ever?

@jayunit100 it's not currently on the roadmap. Do you have a specific use case in mind?