| # Don't use this. | |
| import zmq | |
| import os | |
| class Worker: | |
| def __init__(self): | |
| print "parent: %d, pid: %d" % (os.getppid(), os.getpid()) | |
| self.pid = os.getppid() | |
| self.context = zmq.Context() | |
| self.sub = self.context.socket(zmq.SUB) |
| #!/usr/bin/env ruby | |
| rss = '.+?Rss:\s+(\d+)' | |
| share = '.+?Shared_Clean:\s+(\d+)' | |
| share << '.+?Shared_Dirty:\s+(\d+)' | |
| priv = '.+?Private_Clean:\s+(\d+)' | |
| priv << '.+?Private_Dirty:\s+(\d+)' | |
| MEM_REGEXP = /\[heap\]#{rss}#{share}#{priv}/m | |
| def mem_usage() |
For a while, I have felt that the following is the correct way to improve the mass assignment problem without increasing the burden on new users. Now that the problem with the Rails default has been brought up again, it's a good time to revisit it.
When creating a form with form_for, include a signed token including all of the fields that were created at form creation time. Only these fields are allowed.
To allow new known fields to be added via JS, we could add:
| diff --git a/Changelog.backport_gc b/Changelog.backport_gc | |
| new file mode 100644 | |
| index 0000000..b617fc8 | |
| --- /dev/null | |
| +++ b/Changelog.backport_gc | |
| @@ -0,0 +1,128 @@ | |
| +Tue Jan 17 12:32:46 2012 Nobuyoshi Nakada <nobu@ruby-lang.org> | |
| + | |
| + * gc.c (aligned_malloc, aligned_free): covered missing defined | |
| + operators and fixes for cygwin. |
| diff -rupN openssl-1.0.0g/apps/apps.c openssl-1.0.0g-npn//apps/apps.c | |
| --- openssl-1.0.0g/apps/apps.c 2011-03-19 02:44:25.000000000 -0700 | |
| +++ openssl-1.0.0g-npn//apps/apps.c 2012-02-08 11:07:50.667074885 -0800 | |
| @@ -2693,6 +2693,48 @@ void jpake_server_auth(BIO *out, BIO *co | |
| #endif | |
| +/* next_protos_parse parses a comma separated list of strings into a string | |
| + * in a format suitable for passing to SSL_CTX_set_next_protos_advertised. | |
| + * outlen: (output) set to the length of the resulting buffer on success. |
| git clone git://github.com/RailsApps/rails3-devise-rspec-cucumber.git rails3app | |
| cd rails3app | |
| #lets increase working set | |
| sed -i 's/, :group.*//' Gemfile | |
| sed -i '/^\(group\|end\)/ d' Gemfile | |
| rm Gemfile.lock | |
| bundle install | |
| RAILS_ENV=production bundle exec rake db:migrate | |
| RAILS_ENV=production bundle exec rails runner '(1..20).each{|i| User.create(email: "as#{i}@df.gh", name: "asdf#{i}", password: "asdfghjk")}' | |
| bundle exec rake assets:precompile |
| def screenshot | |
| require 'capybara/util/save_and_open_page' | |
| now = Time.now | |
| p = "/#{now.strftime('%Y-%m-%d-%H-%M-%S')}-#{rand}" | |
| Capybara.save_page body, "#{p}.html" | |
| path = Rails.root.join("#{Capybara.save_and_open_page_path}" "#{p}.png").to_s | |
| page.driver.render path | |
| Launchy.open path | |
| end |
This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.
You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and brew install autoconf using homebrew.
| (defadvice ruby-indent-line (after unindent-closing-paren activate) | |
| (let ((column (current-column)) | |
| indent offset) | |
| (save-excursion | |
| (back-to-indentation) | |
| (let ((state (syntax-ppss))) | |
| (setq offset (- column (current-column))) | |
| (when (and (eq (char-after) ?\)) | |
| (not (zerop (car state)))) | |
| (goto-char (cadr state)) |
#Lessons From A JavaScript Code Review
I was recently asked to review some code for a new JavaScript application and thought I might share some of the feedback I provided as it includes a mention of JavaScript fundamentals that are always useful to bear in mind. Code reviews are possibly the single biggest thing you can do to improve the overall quality of your solutions and if you're not actively taking advantage of them, you're possibly missing out on bugs you haven't noticed being found or suggestions for improvements that could make your code better.
##Challenges & Solutions
Code reviews go hand-in-hand with maintaining strong coding standards. That said, standards don't usually prevent logical errors or misunderstandings about the quirks of a programming language. Even the most experienced developers can make these kinds of mistakes and code reviews can greatly assist with catching them.
Often the most challenging part of code reviews is actually finding an experienced developer you trust to complete