labofsahil/github-event-dataset-2012 huggingface dataset:
You've got several magic strings in here, both for scriptType and projectType. Considering that you're checking for exact string equality *and* these strings are passed in from your caller, these magic strings should be declared as variables that are exported from the module so that callers can use the symbols instead, and you can compare against the symbols as well and everything stays in sync a lot easier.
Or maybe just `scope` as an easy way to access the scope.
this feature is solved, managed to implement get_or_create() method, 
it will now only create AnswerSet if the object doesnt exist
Remplacer par un ".".
since everything in the notification's constructor is almost similar in the two blocks above, can we initialize after the block? If a new parameter is introduced, a similar change will have to be made in two places. Should ideally be in one place.
+1 for `DONT_INTERCEPT`

otherwise
`MIND_YOUR_OWN_BUSINESS` expresses the concept as well :D
I'm just keeping with the same style as previous tests.

We could do a test-wide replacement later, but people with ASCII-only keyboard layouts would have trouble maintaining the test.
Do we need an entire controller for one action? Why not just create another method in Puzzles::SubmissionsController called `rating` which updates a given submission's rating. I'd expect the route to work like:

```
resources :puzzles do
  resources :submissions, :controller => "Puzzles::Submissions" do
    member do
      post :rating
    end
  end
end
```

And with @submission.rating the method is very simple and can just be:


```ruby
def rating
  @rating = @submission.rating

  # This is probably overkill, since we only need to update Rating#rate
  if rating.update_attributes(params[:rating])
    # Same as your method ....
  end
end
```
The fact that as you say, this happens randomly, hints at a bug IMO. 

Also, in JDG, services like HR and Memcached options shouldn't be loaded lazily, should they? They're the core part of JDG.

Did you check this with Tristan?
Tested and works fine. Have not requested a pull request for it.
Was removing this period really necessary
My bad, the occurrences of bloginfo('template_url') should be replaced with 

echo $template_url

I'm emailing you a "header.php" that I made the change.
Oops, right you are!
+1 in regards to the name of this file / the existance of the factory create method

I would expect to be able to use this module like:

     var Webview = require('webview');
     var foo = new Webview();

All the effort in this file is going towards making a classical style Webview object that supports construction with the new operator.  It seems weird to hide all of this behind another "factory"

The best compromise would be to refactor into (since I have a pet peeve with things named Factory / Manager / Helper/ etc):

      var webview = require('webview');
      var foo = webview.create();