get rg from vscode pre-builts
commit sha： a44ace885af6cfc62d3528d88554e1f852aacb9cpush time in 1 month ago
gh-r isn't searching for Apple Silicon compatible binaries correctly.
On my new M1 MacBookPro...
The gh-r ice isn't correctly grabbing the right binary packages that are using platform strings like
x86_64-apple-darwin (usually Rust apps in my experience). e.g.
It's usually finding the linux arm binaries instead.
Here are my environment variables from zsh installed via Home-brew which is version
zsh 5.8 (arm-apple-darwin21.1.0):
CPUTYPE=arm64 MACHTYPE=arm OSTYPE=darwin21.1.0
/bin/zsh which is
zsh 5.8 (x86_64-apple-darwin21.0):
CPUTYPE=arm64 MACHTYPE=x86_64 OSTYPE=darwin21.0
# An example command to cause the issue(s) in question. zinit wait lucid for \ from'gh-r' \ as'program' \ mv'lsd* -> lsd' \ pick'lsd/lsd' \ @Peltoche/lsd
I suspect the way to deal with this is to detect that it is an M1 macOS system and do an arm check then an intel type.
I don't think moving the
CPUTYPE up in
.zinit-get-latest-gh-r-url-part would be enough. Plus
MACHTYPE won't check for
amd64 unless it is
/bin/zsh. A native
zsh won't have any indication that it has Rosetta 2 installed and can handle
Yes, I can do experiments for you. :smiley:
commit sha： 3dd2a0764f7c9ab15adc17ae1201aae2c22788f0push time in 1 month ago
commit sha： aca83d9effd7b3176440e8d017a6bd4ca1fae0c7push time in 1 month ago
commit sha： b6e140dd9381d3a5d4bfc1e3809dee38641ecf4dpush time in 1 month ago
commit sha： e238d3cf1e465b371fe761740f80dbae1211cbcepush time in 1 month ago
commit sha： b7db0060854f2478deafd36e92f3365505a9cd04push time in 1 month ago
Bump gopkg.in/DataDog/dd-trace-go.v1 from 1.32.0 to 1.37.0
Bumps gopkg.in/DataDog/dd-trace-go.v1 from 1.32.0 to 1.37.0.
Sourced from gopkg.in/DataDog/dd-trace-go.v1's releases.
This release comes with the new AppSec capability to monitor the parsed HTTP body thanks to a new public
appsecpackage. This package provides a function -
appsec.MonitorParsedHTTPBody()- that should be called from within your http request handlers with the parsed http body payload, such as returned by
proto.Unmarshal()or any other parser. It also introduces support for the web framework gin, as well as the latest AppSec security rules which include the new OGNL & Cassandra injection detections.
Additionally, this update provides a new user monitoring tracing function -
tracer.SetUser()- allowing to associate user attributes to a trace. This allows to add user context to traces which can then be leveraged by Datadog's monitoring, for example by identifying the user of an AppSec attack.
The profiler's code hotspots and endpoints is now enabled by default in order to connect APM traces and profiles.
Note that dd-trace-go's go.mod file has been updated to now include every dependency required by dd-trace-go and its integrations. It now lists the minimum secure versions required, according to the Go module registry of vulnerabilities.
- all: commit full go.mod and go.sum files (#1188)
- contrib/database/sql: fix support for drivers using deprecated interfaces (#1167)
- contrib/database/sql: trace connection time (#1154)
- contrib/gorilla/mux: provide a new function wrapper for gorilla router (#1175)
- contrib/segmentio/kafka-go: add tracing for kafka writer and reader (#1152)
- ddtrace/tracer: overall CPU & memory performance improvements (#1184, #1160, #1186, #1134, #1183)
- ddtrace/tracer: Add B3 flag to PropagatorConfig (#1148)
- ddtrace/tracer: provide a new user monitoring tracing function to associate a user to a trace (#1196)
- ddtrace/tracer: disable Datadog internal tag propagation (#1182)
- ddtrace/tracer: fix a bug with the
x-datadog-tagsheader parser (#1155)
- ddtrace/tracer: fix top_level computation with DD_SERVICE_MAPPING (#1150)
- contrib/gin-gonic: add AppSec monitoring of http requests and responses (#1165)
- contrib/google.golang.org/grpc: monitor grpc metadata headers (#1190)
- contrib/labstack/echo.v4: fix http response monitoring (#1177)
- appsec: provide a new function to monitor the parsed http body (#1178)
- internal/appsec/waf: fix the parsing of AppSec security rules (#1189)
- internal/appsec: update the security rules to v1.2.6, including new OGNL & Cassandra injections and various improvements (#1191)
- profiler, ddtrace/tracer: enable code hotspots & endpoints by default with 100% CPU profiling (#1169)
- profiler: don't upload full profiles if delta profiling is enabled (#1187)
- profiler: Inc DefaultBlockRate from 10µs to 100ms (#1192)
This release contains a small patch that disables service propagation in the Tracer.
ddtrace/tracer: disable Datadog internal tag propagation (#1182)
To view the changes check out the list of commits
This version comes with the Application Security (AppSec) public beta which includes a broader security coverage of HTTP servers, now also extended to gRPC servers. It is powered by new security rules that allow monitoring the OWASP Top 10 attack attempts, such as SQL injections, Log4Shell and Server-Side Request Forgeries.
It also includes many APM tracing improvements, along with a fix for a regression introduced in v1.35.0.
2f579f3appsec: use std context package (#1214)
58fe681FAQ.md: add link to PR about measuring spans (#1113)
0c1b381go.mod: downgrade to sqlx v1.2.0 (#1208)
133f3d9contrib/google.golang.org/grpc: monitor grpc metadata headers (#1190)
9d4a5d1go.mod: update github.com/gin-gonic/gin to v1.7.0 (#1204)
5b43087ddtrace/tracer: don't use UTC() when getting time (#1134)
c47da55ddtrace/tracer.StartSpan: Use setMeta instead of SetTag (#1160)
5b114beddtrace/tracer: Remove log.Debug from hot path (-2 allocs; -5% CPU) (#1186)
7c11ba8contrib/google.golang.org/grpc: Reduce allocs in interceptor (#1183)
7d066c1ddtrace/tracer.Measured(): Cache a global instance (save 1 alloc/call) (#1184)
- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it
@dependabot mergewill merge this PR after your CI passes on it
@dependabot squash and mergewill squash and merge this PR after your CI passes on it
@dependabot cancel mergewill cancel a previously requested merge and block automerging
@dependabot reopenwill reopen this PR if it is closed
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
feat(directory): Directory enhancements
This pull request provides a number of enhancements to the display of directory strings.
Full Disclosure: This pull request depends on the stylish-stringlike crate, of which I am the author.
Directories can be shrunk to fit in an available terminal width. For example, the path
some-random-arbitrarily-long-path/with/segments can be automatically shrunk to
some-ran…ng-path/with/segments. New configuration variables
fit_symbol are introduced to control this behavior.
Style strings in
[directory.substitutions] are expanded.
Regular Expression Substitution
Regular expressions (with back-referencing) are supported through
[directory.substitution_regexes], and style strings in the replacement text are expanded.
Path Delimiter Specification
A new configuration variable
delimiter is provided. This is required in order for the directory fitting to not truncate on path delimiters.
Motivation and Context
Styled substitutions make path delimiters easier to see. Automatic fitting of paths can provide more flexibility if users want as much context as possible without overflowing the terminal, or if they have unfortunately long folder names.
Screenshots (if appropriate):
How Has This Been Tested?
- I have tested using MacOS
- I have tested using Linux
- I have tested using Windows
I have tested this on Linux Mint using the Tilix terminal running zsh. I have also run the test suite on Windows.
I have updated the call signature for the
modules::utils::directory::truncate function to be generic over objects that are
String implements), and to require a
delimiter argument. Corresponding function calls in the
conda module have been updated for this reason.
- I have updated the documentation accordingly.
- I have updated the tests accordingly.
commit sha： c73344b285f1bb649061f3f6a6491262bb82ac8epush time in 2 months ago
commit sha： 4c0ec82a1fd771777475ffd337ef0b2e84d36581push time in 2 months ago