Shougo/dein.vim 2814
:zap: Dark powered Vim/Neovim plugin manager
machine-drivers/docker-machine-driver-xhyve 878
docker-machine/minikube/minishift driver plugin for xhyve/hyperkit (native macOS hypervisor.framework)
deoplete-plugins/deoplete-jedi 548
deoplete.nvim source for Python
deoplete-plugins/deoplete-go 432
Asynchronous Go completion for Neovim. deoplete source for Go.
neovim/go-client 254
Nvim Go client
(AE|Cloud) Datastore Wrapper
deoplete-plugins/deoplete-clang 186
deoplete.nvim source for C/C++/Obj-C/Obj-C++ with clang-python3
mercari/docker-appengine-go 75
Projects has been moved
micnncim/protocol-buffers-language-server 42
[WIP] Protocol Buffers Language Server
issue closedistio/istio
Need to remove illegal characters from remote secret names
Cluster names on various platforms can contain characters that are not allowed in k8s resource names. We should remove any illegal characters when creating the secret name.
[ ] Docs [x] Installation [ ] Networking [ ] Performance and Scalability [ ] Extensions and Telemetry [ ] Security [ ] Test and Release [ ] User Experience [ ] Developer Infrastructure [ ] Upgrade
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)
closed time in 3 minutes
nmittler
issue commentistio/istio
Need to remove illegal characters from remote secret names
After some discussion, we've decided to retain the existing restrictions on cluster names.
comment created time in 3 minutes
issue commentkubernetes/kubernetes
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
comment created time in 3 minutes
issue commentkubernetes/kubernetes
PVC is not annotated with "volume.kubernetes.io/selected-node" when .spec.nodeName is used
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
comment created time in 3 minutes
issue commentkubernetes/kubernetes
Read-only NFS based PV PVC allowing writes to the filesystem
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
comment created time in 3 minutes
issue commentkubernetes/sig-release
Add mention of WIP tests to Release Blocking Jobs and Criteria
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
comment created time in 3 minutes
issue commentkubernetes/kubernetes
Stateful POD created but not scheduled
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
comment created time in 3 minutes
issue commentkubernetes/kubernetes
Allow updating volumeClaimTemplates labels
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
comment created time in 3 minutes
issue commentkubernetes/kubernetes
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
comment created time in 3 minutes
push eventDataDog/datadog-agent
commit sha 7e7bc4d72eb22ac84e82ef11b7313d56d693771c
set top level to 0
push time in 3 minutes
PR closed istio/istio
Fixes https://github.com/istio/istio/issues/29101
[ ] Configuration Infrastructure [ ] Docs [x] Installation [ ] Networking [ ] Performance and Scalability [ ] Policies and Telemetry [ ] Security [ ] Test and Release [ ] User Experience [ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.
pr closed time in 3 minutes
pull request commentistio/istio
Allow more flexible cluster names.
In a discussion offline, it sounds like there may be cases where cluster names might be used in hostnames. For that reason, it's probably best to keep the current restrictions. Closing this.
comment created time in 3 minutes
push eventrancher/rancher
commit sha 10a71ba72a7651f1f817947872edc3061d197d98
Add ability to set password for rancherd
commit sha 11a4a1c9288f80b527a78282504b44b2c196de15
Merge pull request #30216 from StrongMonkey/backport-rancherd-password-v2.5 [2.5]Backport-Add ability to set password for rancherd
push time in 4 minutes
PR merged rancher/rancher
pr closed time in 4 minutes
push eventrancher/rancher
commit sha 8af52f9e336a0ddf341316d87fce5f39505ff9fb
Update provider detector to include rke.windows
commit sha 8ad21afb4e70b955b5b97c32992da6156133eb95
Merge pull request #30207 from StrongMonkey/backport-windows-provider [2.5] Update provider detector to include rke.windows
push time in 4 minutes
PR merged rancher/rancher
Backport of https://github.com/rancher/rancher/pull/29691
pr closed time in 4 minutes
pull request commentkubernetes-sigs/service-apis
I'm a little hesitant about this one. Especially since our docs include API spec now. This would mean any change to API types or docs (99% of PRs) would conflict with each other. I agree that search would be helpful, but I'm hesitant to add that kind of overhead to the dev workflow.
comment created time in 4 minutes
push eventJetBrains/intellij-sdk-docs
commit sha fec89a27165a92ca316f28eb58f038b68fff3944
api_notable_list_2020.md: TextEditorCustomizer
push time in 4 minutes
pull request commentistio/istio
Move some special injection logic into the templates
@howardjohn: The following tests failed, say /retest to rerun all failed tests:
| Test name | Commit | Details | Rerun command |
|---|---|---|---|
| gencheck_istio | 651bcab7e6fe35e71a4e825135bc258304aca707 | link | /test gencheck_istio |
| unit-tests_istio | 651bcab7e6fe35e71a4e825135bc258304aca707 | link | /test unit-tests_istio |
| lint_istio | 651bcab7e6fe35e71a4e825135bc258304aca707 | link | /test lint_istio |
<details>
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. </details> <!-- test report -->
comment created time in 4 minutes
pull request commentistio/istio
Move some special injection logic into the templates
@howardjohn: The following tests failed, say /retest to rerun all failed tests:
| Test name | Commit | Details | Rerun command |
|---|---|---|---|
| gencheck_istio | 651bcab7e6fe35e71a4e825135bc258304aca707 | link | /test gencheck_istio |
| unit-tests_istio | 651bcab7e6fe35e71a4e825135bc258304aca707 | link | /test unit-tests_istio |
<details>
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. </details> <!-- test report -->
comment created time in 4 minutes
pull request commentgoogle/syzkaller
dashboard/config/linux: update to next-20201124 with KFENCE enabled
Codecov Report
Merging #2272 (d9c336e) into master (878fb17) will not change coverage. The diff coverage is
n/a.
comment created time in 4 minutes
pull request commentistio/istio
Move some special injection logic into the templates
@howardjohn: The following test failed, say /retest to rerun all failed tests:
| Test name | Commit | Details | Rerun command |
|---|---|---|---|
| gencheck_istio | 651bcab7e6fe35e71a4e825135bc258304aca707 | link | /test gencheck_istio |
<details>
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. </details> <!-- test report -->
comment created time in 4 minutes
Pull request review commentistio/api
[WIP] Add initial Telemetry API definition
message MeshConfig { // The default status is "403" (HTTP Forbidden). string status_on_error = 4; }++ // EnvoyTracingOpenCensusProvider defines configuration for an OpenCensus tracer writing to+ // an OpenCensus agent backend. See+ // [Envoy's OpenCensus trace configuration](https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/trace/v3/opencensus.proto)+ // and+ // [OpenCensus trace config](https://github.com/census-instrumentation/opencensus-proto/blob/master/src/opencensus/proto/trace/v1/trace_config.proto)+ // for details.+ // $hide_from_docs+ message EnvoyTracingOpenCensusProvider {+ // REQUIRED. gRPC address for the OpenCensus agent (e.g. dns://authority/host:port or+ // unix:path). See [gRPC naming docs](https://github.com/grpc/grpc/blob/master/doc/naming.md) for+ // details.+ string address = 1;
I was worried about requiring that everything involve a k8s service, as it should be valid to send to a daemon set for some tracing use cases. Is service + port the way forward here for all integrations, or is there another convention that you are suggesting?
comment created time in 5 minutes
pull request commentgoccy/go-json
Clean encode context before putting to pool
Note that the error with -race happens even without GOGC=1. And also using all=-d=checkptr -N -l doesn't fail.
comment created time in 6 minutes
issue openedgolang/go
x/tools/gopls: change "Toggle gc details" to show/hide
It's not always clear which package you've enabled GC details for, so you may not know if it's on or off--it might be easier if the codelens was "Show GC details" and "Hide GC details".
/cc @pjweinb
created time in 6 minutes
push eventkubernetes-sigs/service-apis
commit sha e57f6a552632bece88f19a9f7fca5749e97959bd
remove unnecessary Dockerfile `Dockerfile` is a leftover from the past when the repo had a sample controller code.
commit sha 4455c32ed47a8b47f686d2c5c64aeff9b6798dcd
Merge pull request #478 from hbagdi/remove-dockerfile remove unnecessary Dockerfile
push time in 6 minutes
PR merged kubernetes-sigs/service-apis
Dockerfile is a leftover from the past when the repo had a sample controller
code.
pr closed time in 6 minutes
PR opened juju/juju
Add a strategy for adding adding default application architecture constraint.
This is just an idea and I'm unsure how successful it is, but essentially the idea is to check all instances for their own arch and if it has some the fill it in.
If we have a heterogenous set of machines then use the model to see if that has one, otherwise use the default architecture.
Please provide the following details to expedite review (and delete this heading)
Replace with a description about why this change is needed, along with a description of what changed.
Checklist
- [ ] Requires a pylibjuju change
- [ ] Added integration tests for the PR
- [ ] Added or updated doc.go related to packages changed
- [ ] Comments answer the question of why design decisions were made
QA steps
Please replace with how we can verify that the change works.
QA steps here
Documentation changes
Please replace with any notes about how it affects current user workflow, CLI, or API.
Bug reference
Please add a link to any bugs that this change is related to, e.g., https://bugs.launchpad.net/juju/+bug/9876543
pr created time in 7 minutes
issue commentdocker/for-win
additional debugging steps:
- verified nothing else was listening on port 53
- disabled windows features containers, hyperv, wsl, then re-enabled. (https://github.com/docker/for-win/issues/8204)
comment created time in 7 minutes
pull request commentkubernetes/kubernetes
api: Allow MaxSurge to be set on DaemonSets during update
@smarterclayton: The following tests failed, say /retest to rerun all failed tests:
| Test name | Commit | Details | Rerun command |
|---|---|---|---|
| pull-kubernetes-e2e-gce-ubuntu-containerd | 67a487164e181a3f9780cdd41cf00f3e931e2343 | link | /test pull-kubernetes-e2e-gce-ubuntu-containerd |
| pull-kubernetes-node-e2e | 67a487164e181a3f9780cdd41cf00f3e931e2343 | link | /test pull-kubernetes-node-e2e |
| pull-kubernetes-e2e-gce-100-performance | 67a487164e181a3f9780cdd41cf00f3e931e2343 | link | /test pull-kubernetes-e2e-gce-100-performance |
| pull-kubernetes-e2e-gce-alpha-features | 67a487164e181a3f9780cdd41cf00f3e931e2343 | link | /test pull-kubernetes-e2e-gce-alpha-features |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
<details>
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. </details> <!-- test report -->
comment created time in 7 minutes