- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 181 for fix (0.06 sec)
-
CHANGELOG/CHANGELOG-1.2.md
## Changelog since v1.2.5 ### Other notable changes * Fix watch cache filtering ([#28967](https://github.com/kubernetes/kubernetes/pull/28967), [@liggitt](https://github.com/liggitt)) * Fix problems with container restarts and flocker ([#25874](https://github.com/kubernetes/kubernetes/pull/25874), [@simonswine](https://github.com/simonswine))
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Fri Dec 04 06:36:19 UTC 2020 - 41.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.13.md
* fix azure disk naming matching issue due to case sensitive comparison ([#81720](https://github.com/kubernetes/kubernetes/pull/81720), [@andyzhangx](https://github.com/andyzhangx)) * fix: detach azure disk issue using dangling error ([#81266](https://github.com/kubernetes/kubernetes/pull/81266), [@andyzhangx](https://github.com/andyzhangx))
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu May 05 13:44:43 UTC 2022 - 273.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.15.md
- Fix: add remediation in azure disk attach/detach ([#88444](https://github.com/kubernetes/kubernetes/pull/88444), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: azure file mount timeout issue ([#88610](https://github.com/kubernetes/kubernetes/pull/88610), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu May 05 13:44:43 UTC 2022 - 278.9K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.22.md
- Fix a bug that `--disabled-metrics` doesn't function well. (#105793, @Huang-Wei) [SIG API Machinery, Cluster Lifecycle and Instrumentation] - Fix a panic in kubectl when creating secrets with an improper output type (#106356, @lauchokyip) [SIG CLI] - Fix concurrent map access causing panics when logging timed-out API calls. (#106112, @marseel) [SIG API Machinery]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Tue Dec 13 12:43:45 UTC 2022 - 454.1K bytes - Viewed (0) -
.github/release-drafter.yml
name-template: 'v Release $NEXT_PATCH_VERSION π' tag-template: 'v$NEXT_PATCH_VERSION' categories: - title: 'π Features' labels: - 'feature' - 'enhancement' - title: 'π Bug Fixes' labels: - 'fix' - 'bugfix' - 'bug' - title: 'π§° Maintenance' label: 'chore' change-template: '- $TITLE @$AUTHOR (#$NUMBER)' change-title-escapes: '\<*_&' template: | ## Changes
Registered: Sun Nov 03 09:35:10 UTC 2024 - Last Modified: Wed Oct 09 11:31:04 UTC 2024 - 428 bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.21.md
- Fix a bug that `--disabled-metrics` doesn't function well. (#106391, @Huang-Wei) [SIG API Machinery, Cluster Lifecycle and Instrumentation] - Fix a panic in kubectl when creating secrets with an improper output type (#106354, @lauchokyip) [SIG CLI] - Fix concurrent map access causing panics when logging timed-out API calls. (#106113, @marseel) [SIG API Machinery]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Fri Oct 14 07:03:14 UTC 2022 - 367.3K bytes - Viewed (0) -
cni/pkg/config/config.go
// The node name that the CNI DaemonSet runs on NodeName string // Key and value for broken pod label LabelKey string LabelValue string // Whether to fix race condition by repairing them RepairPods bool // Whether to fix race condition by delete broken pods DeletePods bool // Whether to label broken pods LabelPods bool
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Aug 16 15:33:47 UTC 2024 - 5.7K bytes - Viewed (0) -
.pre-commit-config.yaml
- --unsafe - id: end-of-file-fixer - id: trailing-whitespace - repo: https://github.com/astral-sh/ruff-pre-commit rev: v0.7.1 hooks: - id: ruff args: - --fix - id: ruff-format ci: autofix_commit_msg: π¨ [pre-commit.ci] Auto format from pre-commit.com hooks
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Mon Oct 28 20:31:44 UTC 2024 - 733 bytes - Viewed (0) -
CONTRIBUTING.md
[issue]: https://github.com/google/guava/issues Pull requests ------------- Unless the change is a trivial fix such as for a typo, it's generally best to start by opening a new issue describing the bug or feature you're intending to fix. Even if you think it's relatively minor, it's helpful to know what people are working on. And as mentioned above, API changes should be discussed
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Nov 17 18:47:47 UTC 2023 - 3.7K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/bug_report.md
--- name: Bug report about: A reproducible problem title: '' labels: bug assignees: '' --- Good bug reports include a failing test! Writing a test helps you to isolate and describe the problem, and it helps us to fix it fast. Bug reports without a failing test or reproduction steps are likely to be closed. Hereβs an example test to get you started.
Registered: Fri Nov 01 11:42:11 UTC 2024 - Last Modified: Sun Dec 30 22:44:40 UTC 2018 - 412 bytes - Viewed (0)