mlncn

Running bash [-c /tmp/test_ddev.sh] 
======= Existing project config =========
These config files were loaded for project refer-laaha: [/home/mlncn/Projects/github/unicef/refer-laaha/.ddev/config.yaml]
name: refer-laaha
type: drupal9
docroot: docroot
php_version: 8.1
webserver_type: apache-fpm
webimage: drud/ddev-webserver:v1.21.4
router_http_port: 80

mlncn

# This file contains your BLT configuration. For a list of all available
# properties with current values run `blt config:dump`. Default values come
# from vendor/acquia/blt/config/build.yml.
#
# These values can be overridden at the command line using `--define`, i.e.:
# blt setup --define project.profile.name=minimal
#
# However, when tokens in this file are expanded, they will not use any such
# command-line overrides. For instance, `blt sync --define drush.aliases.local`
# will not modify `drush.default_alias`, even though `drush.default_alias` is

mlncn

$ blt artifact:deploy --commit-msg "Deploy to build" --branch "build"
Commit message is set to Deploy to build.
Branch is set to build.
Preparing artifact directory...
Global .gitignore file is being disabled for this repository to prevent unexpected behavior.
Merging upstream changes into local artifact...
Generating build artifact...
For more detailed output, use the -v flag.
> source:build:frontend
> source:build:frontend-reqs

mlncn

Keybase proof

I hereby claim:

• I am mlncn on github.
• I am mlncn (https://keybase.io/mlncn) on keybase.
• I have a public key ASCvmtF9wx5F7P6roj1Q4agS5VARB1FmHP5iE9Fwj_fTNAo

To claim this, I am signing this object:

mlncn

 (1/1) SchemaException

There is no column with name 'attachment' on table 'bill_payments'.
in SchemaException.php line 86
at SchemaException::columnDoesNotExist('attachment', 'bill_payments')in Table.php line 671
at Table->getColumn('attachment')in Connection.php line 844
at Connection->getDoctrineColumn('bill_payments', 'attachment')in SQLiteGrammar.php line 225
at SQLiteGrammar->compileDropColumn(object(Blueprint), object(Fluent), object(SQLiteConnection))in Blueprint.php line 110
at Blueprint->toSql(object(SQLiteConnection), object(SQLiteGrammar))in Blueprint.php line 85
at Blueprint->build(object(SQLiteConnection), object(SQLiteGrammar))in Builder.php line 239

mlncn

// ==UserScript==
// @name        Toggle fonts-loaded
// @namespace   agaric
// @description Toggle fonts loaded
// @include     *.local
// @version     1
// @grant       none
// ==/UserScript==

(function(){

mlncn

# -*- coding: utf-8 -*-
from __future__ import unicode_literals

from django.db import migrations


def dedupe_codes(apps, schema_editor):
    codes = []
    count = 0
    measures = apps.get_model('measures', 'Measure')

mlncn

Security

History

In Drupal 7 and prior versions we relied on manual escaping variables by our developers and themers. Every variable was either run through check_plain(), filter_xss() or another filter function manually or it was assumed to be safe. You can see where this assumption can easily be overlooked/forgotten and we end up with a security vulnerability usually in the form of an XSS attack.

One of the major decisions for choosing Twig in Drupal 8 was due to its autoescape security feature which all variables can be escaped automatically while they are printed. This alleviates a bunch of concerns and burden on the Security Team as well as protect Drupal Sites by default. This is equivalent to Drupal 7 writing <?php print check_plain($variable); ?> on each variable printed.

Flipping our security on its head aka Security Thought Process

mlncn

class Thumb extends Backbone.Model
  
  defaults:
    uri: ''
    state: ''

  select: (state) ->
    st = ''
    st = 'selected' if state
    @set('state' : st)

mlncn

#!/bin/sh
# Pre-commit hook for git which removes trailing whitespace, converts tabs to spaces, and enforces a max line length.

if git-rev-parse --verify HEAD >/dev/null 2>&1 ; then
   against=HEAD
else
   # Initial commit: diff against an empty tree object
   against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
fi