jhonasn

#!/usr/bin/env python3

# from pdb import set_trace as bkp
from sys import argv, exit
from os import listdir, path, mkdir, utime
from json import loads as to_dict
from datetime import datetime as date

if '-h' in argv or '--help' in argv:
  print('''

newswim

import { Link } from 'react-router-dom'
import { Badge, Col, Menu } from 'antd'

const StyledBadge = styled(Badge)`
    .ant-badge-count {
        background-color: #7ECBBF;
        color: white;
        box-shadow: 0 0 0 1px #d9d9d9 inset;
    }
`

zcaceres

'Include' in Sequelize: The One Confusing Query That You Should Memorize

When querying your database in Sequelize, you'll often want data associated with a particular model which isn't in the model's table directly. This data is usually typically associated through join tables (e.g. a 'hasMany' or 'belongsToMany' association), or a foreign key (e.g. a 'hasOne' or 'belongsTo' association).

When you query, you'll receive just the rows you've looked for. With eager loading, you'll also get any associated data. For some reason, I can never remember the proper way to do eager loading when writing my Sequelize queries. I've seen others struggle with the same thing.

Eager loading is confusing because the 'include' that is uses has unfamiliar fields is set in an array rather than just an object.

So let's go through the one query that's worth memorizing to handle your eager loading.

The Basic Query

DaniilBabanin

// ==UserScript==
// @name         Hide issues by tags
// @namespace    http://babanin.de/
// @version      0.2
// @description  try to take over the world! and hide gitlab issues by tags
// @author       Daniil Babanin & Robin Würfel
// @match        http*://hpm.agency/*
// @grant        none
// ==/UserScript==

spalladino

# Backup
docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql

# Restore
cat backup.sql | docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE

watzon

{
    // JSHint Default Configuration File (as on JSHint website)
    // See http://jshint.com/docs/ for more details

    "maxerr"        : 50,       // {int} Maximum error before stopping

    // Enforcing
    "bitwise"       : true,     // true: Prohibit bitwise operators (&, |, ^, etc.)
    "camelcase"     : false,    // true: Identifiers must be in camelCase
    "curly"         : true,     // true: Require {} for every new block or scope

zeroseis

• Close Android File Transfer
• Open Activity Monitor and kill “Android File Transfer Agent”
• Go to where you installed “Android File Transfer.app” (I have it under /Applications)
• Ctrl+click –> “Show package contents”
• Go to Contents/Resources
• Rename “Android File Transfer Agent” to e.g. “Android File Transfer Agent_DISABLED”
• Then go to “/Users/username/Library/Application Support/Google/Android File Transfer” and again rename the Agent app.

MotiurRahman

var picker = Ti.UI.createPicker({
	type : Ti.UI.PICKER_TYPE_DATE,
	top : 50
});

$.txt.addEventListener('click', function(e) {
	picker.showDatePickerDialog({
		callback : function(e) {
			if (e.cancel) {
				Ti.API.info('User canceled dialog');

phynet

##Generate and Install IPA's file in device through Command Line

###Thanks to Mattt and phonegap's scripts

Take a note: all this steps can be automatized in a single script, if you know how to write it. (Bash or Ruby will be fine)

1.- Install your Provisioning Profile and Developer Certificate

2.- Install Shenzhen and ios-deploy: the firstone will generate the IPA file and the secondone will install it onto your device

DanHerbert

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.