dokimyj

https://github.com/bazelbuild/continuous-integration/issues/1431

I found an interesting issue for Xcode 14.2 CI installation on Bazel Org.

I can't advise because I really have no idea what exactly they suffer from and I'm too noob... 
But as a CI maintainer, hope this gist can help whoever is facing the same problem as I did.

※ Really useful article written by English speaker would be: https://macops.ca/xcode-14-new-platforms-packaging-format/
Thanks a lot for the information, macops.ca!

sindresorhus

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.

cmfsotelo

#!/bin/bash
# This script creates a user account under Mac OS X
usage() {
  echo "  Synopsis"
  echo '    create-user userName userFullName userPassword groupId'
  echo ""
  echo ""
  echo "  Description"
  echo "   Creates a new user with the given params and attributes to the desired group"
}

cecilemuller

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Example",
      "type": "node",
      "request": "launch",
      "runtimeExecutable": "node",
      "runtimeArgs": ["--nolazy", "-r", "ts-node/register/transpile-only"],

BretFisher

2021 Update: Easiest option is Justin's repo and image

Just run this from your Mac terminal and it'll drop you in a container with full permissions on the Docker VM. This also works for Docker for Windows for getting in Moby Linux VM (doesn't work for Windows Containers).

docker run -it --rm --privileged --pid=host justincormack/nsenter1

more info: https://github.com/justincormack/nsenter1

---

nstarke

How to make a Release Android App debuggable

Let's say you want to access the application shared preferences in /data/data/com.mypackage.
You could try to run adb shell and then run-as com.mypackage ( or adb shell run-as com.mypackge ls /data/data/com.mypackage/shared_prefs), but on a production release app downloaded from an app store you're most likely to see:

run-as: Package 'com.mypackage' is not debuggable

p3t3r67x0

openssl

Install

Install the OpenSSL on Debian based systems

sudo apt-get install openssl

swizzlevixen

#!/usr/local/bin/python
# coding: utf-8

import cv2
import sys
import numpy
from matplotlib import pyplot as plt
from scipy.spatial import distance

"""

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

devunwired

/**
 * An example of adding these transitions to a Fragment.  This simple
 * version just applies opposite transitions to any Fragment whether it is
 * entering or exiting view.  You can also inspect the transit mode parameter
 * (i.e. TRANSIT_FRAGMENT_OPEN, TRANSIT_FRAGMENT_CLOSE) in combination to do
 * different animations for, say, adding a fragment versus popping the back stack.
 * 
 * Transactions without an explicit transit mode set, in this example, will not
 * animate.  Allowing the initial fragment add, for example, to simply appear.
 */