- We found a Node.js bug. When
Object.defineProperty
was monkeypatched, in certain situations other things would break. For example, usingconsole.log
after the monkeypatch but not before (ifconsole.log
also appeared before the monkeypatch, it would work).- which was triggered by that kind of monkeypatch mistakenly being attached due to a syntax error in the Ruby uglifier gem’s
es5.js
shim (v2.7.1 - fixed by https://github.com/lautis/uglifier/commit/31a53a92da537af3776711471d6e9582d96dc49d, released in uglifier v3.0.0) - which was used as the js compressor for our static jekyll blog - luckily a direct dependency, and upgrading had no dependency conflicts - easy fix.
- which was triggered by that kind of monkeypatch mistakenly being attached due to a syntax error in the Ruby uglifier gem’s
- Introduced in Node 11.12.0 by: https://github.com/nodejs/node/commit/c14aa07b94d684de8e2a23a54d0e6a3c25a2e460
- Fixed in Node 12.0.0 by: https://github.com/nodejs/node/commit/908292cf1f551c614a733d858528ffb13fb3a524
- [I was running Node 11.14.0.]
package main | |
import ( | |
"fmt" | |
"runtime" | |
"sync" | |
) | |
type UpgradableLock struct { | |
uglMutex sync.RWMutex |
TL;DR: what was the bug? (spoilers!): https://gist.github.com/trptcolin/6039cd454acfe6e820d13cbdce5e4064
- Minor text change for the company blog; let’s get it done!
JEKYLL_ENV=production bundle exec jekyll upload -e staging
Liquid Exception: ExecJS::ProgramError in /_layouts/default.html
- execjs, hmm, do i have node installed?
node --version
- yes, v11.14.0
bundle open jekyll-s3-upload
to read code & see this command is doing- looks like it builds before uploading (
Jekyll::Commands::Build.build(site, jekyll_config)
) - https://github.com/8thlight/jekyll-s3-upload/blob/60dd52f937db21d1265cb9a7fdcdf438730e32d2/lib/jekyll/commands/s3_upload.rb#L51
- looks like it builds before uploading (
bundle exec jekyll build
#include <iostream> | |
#include <iomanip> | |
#include <dlfcn.h> | |
using std::cout; | |
using std::cerr; | |
using std::endl; | |
void* h = []() { |
While installing a Node.js application isn't difficult in principle, it may still be confusing if you're not used to how the Node.js ecosystem works. This post will tell you how to get the application going, what to expect, and what to do if it doesn't work.
Occasionally an application may have custom installation steps, such as installing special system-wide dependencies; in those cases, you'll want to have a look at the install documentation of the application itself as well. However, most of the time it's safe to assume that the instructions below will work fine.
If the application you want to install is available in your distribution's repositories, then install it through there instead and skip this entire guide; your distribution's package manager will take care of all the dependencies.
.global main | |
.func main | |
main: | |
LDR R0, =random_seed | |
LDR R0, [R0] | |
MOV R1, #num_elements | |
BL _rng_loop | |
LDR R0, =unordered_msg | |
BL printf |
""" | |
Dynamic Routing Between Capsules | |
https://arxiv.org/abs/1710.09829 | |
""" | |
import torch | |
import torch.nn as nn | |
import torch.optim as optim | |
import torch.nn.functional as F | |
import torchvision.transforms as transforms |
brew update | |
brew cask install java | |
brew cask install jce-unlimited-strength-policy | |
export JAVA_HOME=`/usr/libexec/java_home -v 1.8` |