scale
Here are 476 public repositories matching this topic...
-
Updated
Apr 14, 2022 - Go
-
Updated
Mar 30, 2022 - Java
-
Updated
Apr 22, 2022 - C
Initial Revisions (at least) with crash-looping pods take a long time to terminate/clean up Pods
What version of Knative?
v1.0 at least
Expected Behavior
When creating a Revision with a pod which exits immediately, the Revision should (fairly quickly) report that Ready is False and terminate the Pods.
Actual Behavior
The pods stick around
Describe your question
平台:mac m1 arm64
容器平台: docker desktop V4.5.0
docker版本:Server Version: 20.10.12 Storage Driver: overlay2
运行镜像:oceanbase/oceanbase-ce standalone-3.1.3
启动命令:docker run -p 2881:2881 --name obstandalone --platform linux/amd64 -e MINI_MODE=1 -d oceanbase/oceanbase-ce:standalone-3.1.3
启动过程中的问题:
启动执行 docker logs obstandalone 有以下信息
generate boot.yaml ...
/root/boot
-
Updated
Nov 28, 2021 - TypeScript
-
Updated
Mar 26, 2022 - JavaScript
-
Updated
Apr 24, 2022 - Dart
-
Updated
Dec 22, 2018 - Objective-C
-
Updated
Apr 22, 2022 - Java
-
Updated
Apr 6, 2022 - Go
-
Updated
Apr 12, 2022 - TypeScript
Describe the issue
Currently we run the Linter CI for golang repos using the golang-ci-linter binary. But according to the documentation it is faster and better to use the github action.
https://golangci-lint.run/usage/install/
The UX of all the error highlighting is also better.
What if we do not do this?
Finding linter errors is troublesome as users have to parse through the cons
-
Updated
Apr 23, 2022 - Go
-
Updated
Apr 4, 2022 - Swift
Is your feature request related to a problem? Please describe.
I would like to know how Brighter reacts if it receives messages from other systems.
Describe the solution you'd like
Would like to know if you can rely on default behavior or if any additional message headers are needed
-
Updated
Mar 26, 2020 - JavaScript
-
Updated
Sep 9, 2021 - Java
-
Updated
Apr 4, 2022 - PHP
-
Updated
Apr 12, 2022 - Scala
-
Updated
Oct 1, 2018 - Java
-
Updated
Oct 23, 2020 - C#
Is your feature request related to a problem? Please describe.
Updating escalator config currently requires a pod restart. We should update escalator to automatically read new config upon changing on disk.
Describe the solution you'd like
Check for changes in nodegroup config before each run. If safe to do so, run with the new config.
*Describe alternatives you've considered
Improve this page
Add a description, image, and links to the scale topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the scale topic, visit your repo's landing page and select "manage topics."
Enhancement