All Issues
24,993 verified issues
insertAll using mongodb bulk API
batch inserts would be good for perf (with in the model.create method). obstacles in 2.x: 1) dependence on triggering each inserted documents 'save' hooks. the hook system isn't flexible enough for us to trigger them without actually calling doc.save. 2) doc.save() is tightly coupled to its persistence method to the db (e.g. collection.insert, collection.update). we don't actually want to .insert() it. we want to trigger hooks without calling doc.save(), then use insertAll.
Error: Cannot find module 'mongodb/node_modules/bson'
I have this error since starting to develop with Mongoose 1,5 years ago. The error never vanished completely, it comes back after each and every `npm update` This error has been a friend and annoyance alongside the road developing with MEANB. Are there any plans to finally get rid of this error or will it continue to annoy the developer community until the end of all time :)?
npm ERR! Failed to parse package.json data.
[code block]
[k8s.io] Kubelet Container Manager [Serial] Validate OOM score adjustments once the node is setup pod infra containers oom-score-adj should be -998 and best effort container's should be 1000 {E2eNode Suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-serial-gce-e2e-ci/782/ Failed: [k8s.io] Kubelet Container Manager [Serial] Validate OOM score adjustments once the node is setup pod infra containers oom-score-adj should be -998 and best effort container's should be 1000 {E2eNode Suite} [code block]
[k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/7676/ Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} [code block]
[k8s.io] Density [Feature:Performance] should allow starting 30 pods per node {Kubernetes e2e suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-kubemark-500-gce/4685/ Failed: [k8s.io] Density [Feature:Performance] should allow starting 30 pods per node {Kubernetes e2e suite} [code block] Previous issues for this test: #26185 #27142
How to ignore SSL issues
Is it possible to configure Axios (running in node.js) to ignore specific SSL errors (like expired certificates)? I'd like to know that the SSL certificate has a problem, but I want the transaction to complete anyway (by default, it fails).
Cannot stop watching a channel
googleapi version: 12.4.0 api version: 3 Steps to reproduce 1. Start watching a drive file [code block] It works good, I get info about channel and start receiving notfnications about changes. 2. Try to stop channel [code block] Expected result Some message about successful operation Actual result [code block] and if I try to watch again, it says "Channel id is not unique"
[k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-soak-continuous-e2e-gce/6512/ Failed: [k8s.io] Kubelet [Serial] [Slow] [k8s.io] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} [code block] Previous issues for this test: #26982
No primary server available
I have an issue that is rather difficult to debug, and was wondering if anyone sees anything wrong with my configuration. [code block] Nodejs version `4.2.1` and mongoDB version `3.0.7` with mongoose `4.2.8`. This seems to happen randomly and will open many connection until I finally restart the node process. The cluster is healthy at all times during this error. This error happens hundreds of times per hour. There does not seem to be any consistency as to when the error will begin. For example, it occurs when the cluster is operating normally and no changes to the primary have been made. This is what the db stats look like. As you can see the number of connections will steadily increase. If I kill the node process and start a new one everything is fine. <img width="1145" alt="screen shot 2015-11-30 at 5 21 01 pm" src="https://cloud.githubusercontent.com/assets/2230570/11489777/36443d10-9787-11e5-98fe-44abe0e49cb8.png"> Config [code block] Connection String [code block] Stack trace [code block]
Help Wanted: Proxy testing
Hi! If you were pinged to this thread, it's because VS Code needs your help! Users behind proxies have had a tough time lately, and we want to make sure we fix this. We've created a small app which will test your machine, network and environment to figure out which network stack works best for you. <details> <summary>App Screenshot</summary> </details> How can I help? We ask you to: 1. Download and extract the appropriate ZIP for your platform 2. Run it 3. Type your proxy URL in the input box 4. Click `Run Tests` 5. Be patient, it should eventually be done 6. Copy the test results to your clipboard 7. Finally, reply to this thread with: - Details about your machine (platform, OS) - Details about your network (proxy type, is it a corporate environment) - A list of the network-related features that don't work for you in VSCode - The results of the test Example reply: > I'm running Windows 10, I am in a corporate environment and I know my proxy address. I can browse VS Code extensions but I can't install them. > > [PASTE TABLE] We thank you in advance! --- @liaoya, @dfroze, @akcorp2003, @ruslanch, @bruceauyeung, @raphabi, @eric-brunel, @fazouane-marouane, @Msira10, @onybo, @ywmail, @foisonocean, @xuewang, @distums, @NeWbY100, @abargstaedt
BeforeSuite {Kubernetes e2e suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-scalability/10992/ Failed: BeforeSuite {Kubernetes e2e suite} [code block] Previous issues for this test: #26135 #26236 #27920 #28492 #29970 #30075 #32980 #33313
Invalid module name in augmentation
Hi, In visual studio, i got this error in every d.ts file under node_modules\rxjs\add\observable\ : Invalid module name in augmentation, module '../../Observable' cannot be found. example code: declare module '../../Observable' { how to fix that please?
Error when building for WebPack
A while ago, I had realized that there is an error when trying to use `socket.io-client` within a WebPack module. It turns out, that "dist/debug.js" can not be located. I did a little bit of unixy research: [code block] [code block] [code block] Conclusion: The `dist` folder must be a virtual folder that is used during the Browserify process... Now, how exactly do I get rid of that? It's really heavy-lifting to `require("socket.io-client/socket.io")` although there already IS a system that knows commonJS. With heavy-lifting, I mean that adding the SIO client is ~350KB... A fix would be pretty awesome.
[k8s.io] [Feature:Example] [k8s.io] Downward API should create a pod that prints his name and namespace {Kubernetes e2e suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-examples/14289/ Failed: [k8s.io] [Feature:Example] [k8s.io] Downward API should create a pod that prints his name and namespace {Kubernetes e2e suite} [code block]
Move packaging process into own plugin
The packaging process should be moved into an own plugin. Status: Done --> See https://github.com/serverless/serverless/pull/1494 This includes: - [x] Zipping up a whole service - [x] One service equals one zip file which includes all the necessary code (all functions) - [x] Magic handler support will be dropped (as it's not necessary anymore) - [x] There will be no checksum to check if something has changed - The zipped up service will be redeployed every time (this ensure that the build "will always work" as no brittle steps as e.g. checksum support will be implemented) - [x] Possibility to set a path to an own artefact (.zip file) via a definition in the `serverless.yaml` file (e.g. `artefact_path`). This way the deployment plugin will use the user specified artefact and won't zip up everything on it's own Questions: - Do we need an own lifecycle in the `deploy` plugin? Or should we use `before:deploy:deploy`? Current implementation: The current implementation can be found in the `awsDeploy` plugin. Open issues: - DRYrun support should be implemented (The user should be able to specify if he wants to save the Resource template (such as `CloudFormation`) and the .zip file to the file system without deploying it) (moved into own issue: https://github.com/serverless/serverless/issues/1496) - Automatic excludes based on the used programming language (moved into own issue: https://github.com/serverless/serverless/issues/1495) - e.g. exclude `src`, `pom` and `traget`
[k8s.io] [Feature:Example] [k8s.io] Spark should start spark master, driver and workers {Kubernetes e2e suite}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-examples/17028 Failed: [k8s.io] [Feature:Example] [k8s.io] Spark should start spark master, driver and workers 6.17s [code block] This test has been consistently failing for a long time https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-examples/17027 https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-examples/17026 https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-examples/17024 https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-examples/17028
beautiful mongodb native errors (unique - code 11000)
I really miss a mechanism that would create validator-like `unique index` error message. Setting the index of an attribute to `unique: true` will tell mongodb to return ugly error message like this: [code block] This message should be treated as validator error message thus we could easily display error messages on a REST service. [code block]
incorrect benchmark ?
Hi, I have ran the benchmarks in my local machine with nodejs 0.12.2, node_redis 0.12.1 and the master branch of ioredis and I have got the following results: [code block] I have ran the benchmark with and without hiredis having similar performance. Those results show better or equal performance between node_redis and ioredis. However, in the documentation, the performance of ioredis is quite better than node_redis. Any idea?
DumpClusterLogs {e2e.go}
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-ingress/225/ Failed: DumpClusterLogs {e2e.go} [code block]