Had the following:
/1-1-1/Screen16/screen.html
/1-1-2/Screen14/screen.html
/1-1-3/Screen12/screen.html
/1-1-3/Screen14/screen.html
/1-3-12/Screen15/screen.html
/1-3-8/Screen10/screen.html
| // Type in a mongoshell | |
| // Credits: http://stackoverflow.com/questions/3788256/mongodb-updating-documents-using-data-from-the-same-document/3792958#3792958 | |
| db.currencies.find({symbol: "$"}).snapshot().forEach( | |
| function (e) { | |
| e.customSymbol = e.code.substr(0, 2) + e.customSymbol; | |
| db.currencies.save(e); | |
| } | |
| ); |
This is what appear:
Java has discovered application components that could indicate a security concern. Contact the application vendor to ensure that it has not been tampered with.
Block potentially unsafe components from being run?
According to [Java][1] its because an Applet or a Java Web Start application contains mixed code (signed and unsigned).
How to know when an element is visible to the user.
Here're some solutions to this:
| { | |
| "dependencies": { | |
| "heapdump": "^0.2.10" | |
| } | |
| } |
It's not hard to write thread-safe code in a Rails application. Simple rules will save any app:
Don't share mutable state If you must share mutable state, mutex around all accesses to it
| var heapdump = require("heapdump"); | |
| function handleCallback(err) { | |
| callback(err); | |
| gc(); | |
| process.nextTick(function () { | |
| heapdump.writeSnapshot('/var/local/' + Date.now() + '.heapsnapshot', function() { | |
| console.log('dump complete'); | |
| }); | |
| }); |
| Math.floor(number * 100) / 100; |
| $ mongodump -d some_database -c some_collection | |
| $ mongorestore -d some_other_db -c some_or_other_collection dump/some_collection.bson |
| $ cat ~/.ssh/id_rsa.pub | ssh [email protected] 'cat >> .ssh/authorized_keys' |