nz

# http://wiki.apache.org/solr/FAQ#How_can_I_delete_all_documents_from_my_index.3F
# http://wiki.apache.org/solr/UpdateXmlMessages#Updating_a_Data_Record_via_curl

curl "http://index.websolr.com/solr/a0b1c2d3/update?commit=true" -H "Content-Type: text/xml" --data-binary '<delete><query>*:*</query></delete>'

I'm amused at the traction this little gist is getting on Google! I would be remiss not to point out that six+ years later I'm still helping thousands of companies on a daily basis with their search index management, by providing managed Solr as a service over at Websolr, and hosted Elasticsearch at Bonsai. Check us out if you'd like an expert helping hand at Solr and Elasticsearch hosting, ops and support!

gist:1167900

diff --git a/commands/core/sitealias.drush.inc b/commands/core/sitealias.drush.inc
index 5352fd5..4f1ae22 100644
--- a/commands/core/sitealias.drush.inc
+++ b/commands/core/sitealias.drush.inc
@@ -39,6 +39,21 @@ function sitealias_drush_command() {
     ),
     'topics' => array('docs-aliases'),
   );
+  $items['site-set'] = array(
+    'description' => '',

Jach

'''
Steps:
  1. Create any milestones
  2. Create any labels
  3. Create each issue, linking them to milestones and labels
  3.1: Update status for new issue if closed
  4: Create all the comments for each issue
'''
import getpass
import json

weitzman

<?php

/**
 * @file
 *
 * Generates a command XML file for PHPStorm/WebStorm/IntelliJ IDEs
 * that provides integration with Drush
 */

/**

shadowhand

#!/bin/bash

usage() {
	echo "usage: git switchbranch"
}

version() {
    echo "switchbranch v0.0.2"
}

jaymcgavren

I run a diff of my current branch versus a different one that has some stuff I want:

$ git diff HEAD subscribers_decorator | cat
diff --git a/app/controllers/posts_controller.rb b/app/controllers/posts_controller.rb
index 245393c..6a1639a 100644
...

Big 'ol list of stuff I don't want...

Followed by a portion that I do want... Which I manually copy.

magickatt

<?php

/**
 * @AfterStep
 */
public function takeScreenshotAfterFailedStep($event)
{
  if ($event->getTestResult()->getResultCode() === \Behat\Testwork\Tester\Result\TestResult::FAILED) {
    $driver = $this->getSession()->getDriver();
    if ($driver instanceof \Behat\Mink\Driver\Selenium2Driver) {

weaverryan

From a user on KnpUniversity.com:

How do you manage testing form validation situations?

For form validation situations, I typically only write 2 scenarios (or sometimes just 1): one that checks that if I submit invalid data, that I see a validation error (I don’t, however assert that all of the validation errors are there – just that the form has some validation errors). Second, I write a scenario that checks a successful form submit.

For me, creating many scenarios to submit a form and check for the different validation errors is over-kill. 99% of the time, adding validation – in Symfony for example – is just one line of code. If we write a scenario for each, we now have one scenario just to test whether or not one line of code is present. For this, I check the validation errors manually – just to make sure I didn’t forget them. I’m not worried about a regression, because it’s highly unlikely that we’ll accidentally remove a line of validation and introduce a bug.

However

helfer

# Autogenerated input type of AddComment
input AddCommentInput {
  # A unique identifier for the client performing the mutation.
  clientMutationId: String

  # The Node ID of the subject to modify.
  subjectId: ID!

  # The contents of the comment.
  body: String!

Berdir

# How to force disable interface translation by overriding the locale lookup service to not be added to the translation manager

# settings.local.php:
$settings['container_yamls'][] = DRUPAL_ROOT . '/sites/default/services.local.yml';


# services.local.yml (add this file to .gitignore):
services:
  string_translator.locale.lookup:
    class: Drupal\locale\LocaleTranslation