Vigilans
Vigilans
> in 5.29.1 this issue still exist > > ``` > 025/02/23 17:16:57.574 [I] [io.go:431] panic: crypto/cipher: invalid buffer overlap > .... > 2025/02/23 17:16:57.574 [I] [io.go:431] github.com/v2fly/v2ray-core/v5/common/task/task.go:28 +0x28 >...
@xiaokangwang For reference: https://stackoverflow.com/questions/41471236/data-passed-by-reference-to-defer So `cryptoData` is just copy-by value on deferring...that also means https://github.com/v2fly/v2ray-core/pull/3320 does not help in terms of buffer release issue because `cache` is properly released actually....
@lucaslorentz @francislavoie Ping for a review, I've used it for months and it proves to work usefully. Use cases: ```yaml services: cs2-ingress: image: .../caddy:latest # with caddy-docker-proxy built environment: CADDY_DOCKER_LABEL_PREFIX:...
This PR will be unnecessary once https://github.com/Vigilans/compose-go/pull/3 is accepted, since `workingDir` is ensured to be absolute directory there. (loader's `workingDir` has to be absolute, or `loader.Load(ctx, f) + loader.Dir(f)` will...
Hi, @zhilyaev Can you elaborate a little more about how it is covered by `post_build: command || true`? I am expecting the skipped release are removed from the plan during...
Based on https://github.com/hey-api/openapi-ts/issues/1069#issuecomment-2879231945, a refined version: `mocks/openapi-msw.ts` (supports both flat SDK and class SDK now) ```typescript /* eslint-disable @typescript-eslint/no-explicit-any */ import type { Client, RequestOptions, RequestResult } from '@/api/client/types' import...
我在调整prompt的时候发现沉浸式翻译会拆包\ tag里面的内容，使用里面的yaml。你可以试试这个tag会不会让沉浸式翻译忽略外部解释？
# Currently supported varibles (Global/Common information) ## Project ### `${project[name]}` Name of the project. Will change within included configs. ### `${project[working-dir]}` The project's directory. Will change within included configs. ##...
# Currently supported varibles (Service/Resource scope information) ## Service ### `${service[name]}` The name of the service. ### `${service[scale]}` The number of replicas of the service. ### `${service[containers][...][...]}` Referencing containers of...
# Currently supported varibles (Cross-scope referencing) ## Services ### `${services[service-name][...]}` Referencing another service, can be used like `${services[service-name][containers][0][name]}`. ## Containers ### `${containers[container-name][...]}` Referencing another container, can be used like `${containers[container-name][env][VAR_NAME]}`....