swalkinshaw

Moved to Shopify/graphql-design-tutorial

greypants

UPDATE: It's a gem!

This helper has finally been moved into a gem called nav_lynx!

https://github.com/vigetlabs/nav_lynx

http://rubygems.org/gems/nav_lynx

Thanks to @brianjlandau and @reagent for getting that set up and tested!

Behold, the nav_link:

krasnoukhov

My largest Sidekiq application had a memory leak and I was able to find and fix it in just few hours spent on analyzing Ruby's heap. In this post I'll show my profiling setup.

As you might know Ruby 2.1 introduced a few great changes to ObjectSpace, so now it's much easier to find a line of code that is allocating too many objects. Here is great post explaining how it's working.

I was too lazy to set up some seeding and run it locally, so I checked that test suite passes when profiling is enabled and pushed debugging to production. Production environment also suited me better since my jobs data can't be fully random generated.

So, in order to profile your worker, add this to your Sidekiq configuration:

if ENV["PROFILE"]

github0013

class FileUploadComponent extends Component{
  upload(){
    this.props.mutate({
      variables: {
        id,
        avatar: this.inputFile.files[0] //this is how you send file
      }
    }).
    then(({data}) => {
      console.log(data)

nfarina

#import <UIKit/UIKit.h>

@interface UIView (SMFrameAdditions)

@property (nonatomic, assign) CGPoint $origin;
@property (nonatomic, assign) CGSize $size;
@property (nonatomic, assign) CGFloat $x, $y, $width, $height; // normal rect properties
@property (nonatomic, assign) CGFloat $left, $top, $right, $bottom; // these will stretch the rect

@end

justinko

Dear Rubyists,

I just lost a contract because of my code in a Rails project.

The specific code in question is related to a "posting a comment" feature. Here are the details:

In this project, "posting a comment" does not simply entail inserting a row into the database. It involves a procedure to yes, insert a row, but also detect its language, check for spam, send emails, and "share" it to Twitter and Facebook. I believe this algorithm should be encapsulated. I do not believe it belongs in a controller or a model. I do not believe Active Record callbacks should be used.

The "senior developer", whom is the stake holder's right hand man, said this:

maccman

$ = jQuery

TRANSFORM_TYPES = ['PUT', 'POST', 'DELETE']

$.activeTransforms = 0

$(document).ajaxSend (e, xhr, settings) ->
  return unless settings.type in TRANSFORM_TYPES
  $.activeTransforms += 1

tanguyantoine

Types::FoosType = GraphQL::ObjectType.define do
  field :foos, !types[Types::FooType] do
    timed true # enable New Relic trace_execution_scoped
    description "Returns foos"
    argument :per, types.Int, default_value: 20
    argument :page, types.Int, default_value: 1
    # Moving to cursor pagination would be better
    resolve(...)
  end
end

nmerouze

package main

import (
	"encoding/json"
	"log"
	"net/http"
	"reflect"
	"time"

	"github.com/gorilla/context"

dhh

# Bulk API design
#
# resources :posts
class PostsController < ActiveController::Base
  # GET /posts/1,4,50,90
  # post_url([ @post, @post ])
  def show_many
    @posts = Post.find(params[:ids])
  end