All Issues
24,993 verified issues
Test {e2e.go}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/16117/ Failed: Test {e2e.go} [code block]
Sub document refs undefined, when not populating in 4.0.2
I am having a strange issue [code block] Any properties that are refs never get added to the document, if I remove the 'ref' statement, the objects load just fine. I am NOT trying to populate the sub-document in this instance, I just want the sub-document id.
Failure To Reconnect After A Socket Closed Error
I am having a issue were the database connection does not seem to be recovering after socket close errors: [code block] My configuration options look like below: [code block] And the mongoose dependency tree looks like below: [code block]
ci-kubernetes-e2e-gci-gke-multizone: broken test run
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gke-multizone/978/ Run so broken it didn't make JUnit output!
Stack overflow when testing with jest
I created a new project where I install the last version 4.8.1. I got the error about promise and use custom one. [code block] The error don't stop but if I go back to version 4.7.7 all work fine.
ci-kubernetes-e2e-gci-gce-reboot-release-1.5: broken test run
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-reboot-release-1.5/684/ Multiple broken tests: Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by dropping all inbound packets for a while and ensure they function afterwards {Kubernetes e2e suite} [code block] Issues about this test specifically: #33405 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by dropping all outbound packets for a while and ensure they function afterwards {Kubernetes e2e suite} [code block] Issues about this test specifically: #33703 #36230 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by ordering unclean reboot and ensure they function upon restart {Kubernetes e2e suite} [code block] Issues about this test specifically: #33882 #35316 Failed: [k8s.io] Reboot [Disruptive] [Feature:Reboot] each node by triggering kernel panic and ensure they function upon restart {Kubernetes e2e suite} [code block] Issues about this test specifically: #34123 #35398
Browser ignoring .border
I've come across an issue where the browser is ignoring the `.border` class: <img width="344" alt="image" src="https://user-images.githubusercontent.com/24975058/37904566-1f4914f6-30f4-11e8-9903-7160a23791ad.png"> This happens in both Chrome & Firefox.
ci-kubernetes-e2e-gce-examples: broken test run
https://storage.googleapis.com/k8s-gubernator/triage/index.html#451144a9be5d4451ad3c https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-examples/4198/ Multiple broken tests: Failed: [k8s.io] [Feature:Example] [k8s.io] Hazelcast should create and scale hazelcast {Kubernetes e2e suite} [code block] Issues about this test specifically: #27850 #30672 #33271 Failed: [k8s.io] [Feature:Example] [k8s.io] CassandraStatefulSet should create statefulset {Kubernetes e2e suite} [code block] Issues about this test specifically: #36323 #36469 #38222 Failed: [k8s.io] [Feature:Example] [k8s.io] Cassandra should create and scale cassandra {Kubernetes e2e suite} [code block] Issues about this test specifically: #27978 #28817 #39574 Failed: Test {e2e.go} [code block] Issues about this test specifically: #33361 #38663 #39788 #39877 #40371 #40469 #40478 #40483 #40668 #41048 #43025 Previous issues for this suite: #36930 #37437 #38393 #38578 #39379 #40341 #43015
send email on same thread.
I have received a successful response of a email using gmail.users.messages.send() which is like `{ "id": "1231212312", "labelIds": ["UNREAD", "SENT", "INBOX"], "threadId": "23123123" }` I need to send an email again to the same email address but on the same thread not as a new email i.e using thread id to send email. Need Help!
ci-kubernetes-e2e-gke-serial: broken test run
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-serial/140/ Run so broken it didn't make JUnit output!
ci-kubernetes-e2e-gce-federation: broken test run
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-federation/18/ Multiple broken tests: Failed: ListResources Before {e2e.go} [code block] Issues about this test specifically: #34755 Failed: ListResources After {e2e.go} [code block] Failed: [k8s.io] Federation deployments [Feature:Federation] Federated Deployment should create and update matching deployments in underling clusters {Kubernetes e2e suite} [code block] Failed: [k8s.io] Federated ingresses [Feature:Federation] Federated Ingresses Ingress connectivity and DNS should be able to connect to a federated ingress via its load balancer {Kubernetes e2e suite} [code block] Issues about this test specifically: #32732 #35392 #36074 Previous issues for this suite: #36927 #37043
UnhandledPromiseRejectionWarning: Error: error:0906D06C:PEM routines:PEM_read_bio:no start line
I get the above error when I try initializing the drive with the jwt token. Below's my implementation. the keys are valid and I downloaded the file from the google developer console. [code block] `workDir` is a variable holding a reference to a string with the name of a working directory. The weird thing is that this was working last week but then it stopped working for some reason.
add more database drivers
Need to add database drivers for at least these databases: - [x] PostgreSQL - [x] SQLite - [x] Microsoft SQL Server - [x] MariaDB - [x] Mongodb - [ ] Cassandra? - [ ] Redis? - [ ] Oracle - [ ] DB2 ? - [ ] mixed databases like indexeddb
ci-kubernetes-e2e-gci-gce-examples: broken test run
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-examples/3599/ Multiple broken tests: Failed: [k8s.io] [Feature:Example] [k8s.io] Hazelcast should create and scale hazelcast {Kubernetes e2e suite} [code block] Issues about this test specifically: #27850 #30672 #33271 Failed: [k8s.io] [Feature:Example] [k8s.io] CassandraStatefulSet should create statefulset {Kubernetes e2e suite} [code block] Issues about this test specifically: #36323 #36469 #38222 Failed: Test {e2e.go} [code block] Issues about this test specifically: #33361 #38663 #39788 #39877 #40371 #40469 #40478 #40483 #40668 #41048 #43025 Failed: [k8s.io] [Feature:Example] [k8s.io] Cassandra should create and scale cassandra {Kubernetes e2e suite} [code block] Issues about this test specifically: #27978 #28817 #39574 Previous issues for this suite: #36939 #39382 #39874 #42107 #43019
Future wish list
We are almost ready to release 2.0.0, and as such, it's time to start thinking about 3.0.0. As usual, the goal of this issue is to gather feedback on important changes that would be breaking or ambitious. (Other suggestions can just be filed as an issue.) We are already looking at dropping support for Node < 4 in 3.0.0. One thing I'd like to hear is ideas for how can ESLint better support TypeScript and Flow. Note: keep the suggestions as high-level descriptions. This is a brainstorming exercise, we don't want to get into implementation details or plausibility discussions. Let's just see what ideas people have. The best will be explored further. <bountysource-plugin> Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
All of a sudden, I'm receiving this error
[code block] I have a 6 nodes setup, I saw this in the log of a node: [code block] I think ioredis is not recovering well alongside the redis cluster(3.2)
ci-kubernetes-e2e-kops-aws-serial: broken test run
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-kops-aws-serial/1/ Multiple broken tests: Failed: [k8s.io] Network Partition [Disruptive] [Slow] [k8s.io] [Job] should create new pods when node is partitioned {Kubernetes e2e suite} [code block] Issues about this test specifically: #36950 Failed: [k8s.io] Daemon set [Serial] Should update pod when spec was updated and update strategy is RollingUpdate {Kubernetes e2e suite} [code block] Failed: [k8s.io] Network Partition [Disruptive] [Slow] [k8s.io] [ReplicationController] should eagerly create replacement pod during network partition when termination grace is non-zero {Kubernetes e2e suite} [code block] Issues about this test specifically: #37479 Failed: [k8s.io] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted. {Kubernetes e2e suite} [code block] Failed: [k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} [code block] Issues about this test specifically: #26784 #28384 #31935 #33023 #39880 Failed: [k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} [code block] Issues about this test specifically: #26982 #32214 #33994 #34035 #35399 #38209 Failed: [k8s.io] Daemon set [Serial] Should not update pod when spec was updated and update strategy is on delete {Kubernetes e2e suite} [co
DiffResources {e2e.go}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-prod-smoke/551/ Failed: DiffResources {e2e.go} [code block] Previous issues for this test: #33373 #33416
DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated with 4.8.0 and 4.8.1
With mongoose versions 4.8.0 and 4.8.1 (node version is 6.9.5 and MongoDB version is 3.2.11) the following warning is generated the first time the save of a document occurs after starting the application (the warning does not appear when the same code is executed subsequent times after the first time while the application is still running, however, if the application is closed and restarted, then the first time a document save occurs after the application has been started the warning is generated): > DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html This issue does not appear when using the exact same application code with mongoose versions 4.7.9 and earlier. The code that sets up the mongoose connection is as follows: `// Set up mongoose and DB connection var mongoose = require('mongoose'); mongoose.Promise = require('bluebird'); mongoose.connect('mongodb://localhost:27017/basedir', {server: { poolSize: 5 }});`
DeprecationWarning: useNewUrlParser: true
warning in debug DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect. Does anyone know how to fix this alert?