I hereby claim:
- I am affixalex on github.
- I am affixalex (https://keybase.io/affixalex) on keybase.
- I have a public key ASCRsqQPp_k87K1bjJeU6xoQoPqBtHktmgjuJ6u58WhWpQo
To claim this, I am signing this object:
| This is a strategy intended to be executed at around 8AM ET through the first | |
| hour of trading (10:30AM ET). It's a refinement of my previous approach aimed | |
| at generating automated buy signals at market open. Note that I didn't actually | |
| write the machine learning model for sentiment analysis, it's a black box to me, | |
| but it performed very well on the training dataset. I'm sure there are better | |
| proprietary sentiment models floating around. | |
| 1. Find after hours gappers, big movers from previous close to current open | |
| 2. Only select gappers priced from $10-20 with a float of 1M+ shares | |
| 3. The top 50 gapping symbols form the watch list for this period |
| ssh_authorized_keys: | |
| - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCnxn8cEjl5PM079R5zwzxrRysi1BCtFJSMwi9H7n6SZytBOEYKCDcJ6fpBFmbmmXmFiQLVNKKtIjOMFvyTRoLj1I2lw8Z6RJ7K28jS1guAAO54WmCb4BxCPnhqeOMy3p/HEsPGGC/81GhlxQr4N7x/3F8OAE5qtjP8cjUmefnTEE8gtDVBrN3MoadBmJqLUuFnMcbvxhfMHBYCpsLSxbKxz+6MJz7g02IhPYPTGg1+gOUaA/JJGs6QQ2iA9woP8ZFIWsBAoYOwuGMIjnY78I2A2BSjAouoMEASWazX4aWU3MXMybLdXh9kKbSkyPnK6UZjp+w/ZtUPkO7ZlVed4z6ONfPBnGiGxdxUdX27xqHBQG5AR/KaQH+NxO/yI9E7pqDQfll0O0AAf3lod5exc/lQHwN77iFfcZm4F5A0+L2Vxg26n4ton4N+rk8t9wN9ttce4OTx8NdzQJEw9uXVgCqM2HyzIEOGtKCdxt/W3mch+mR9TzfRIJ1Zjt5kuctZRas= [email protected] | |
| - github:affixalex | |
| hostname: horizon | |
| k3os: | |
| k3s_args: | |
| - server | |
| - "--cluster-cidr=172.1.0.0/23" | |
| - "--service-cidr=172.2.0.0/23" | |
| dns_nameservers: |
I hereby claim:
To claim this, I am signing this object:
| CHART_REPO := http://jenkins-x-chartmuseum:8080 | |
| CURRENT=$(pwd) | |
| NAME := dashboard | |
| OS := $(shell uname) | |
| RELEASE_VERSION := $(shell cat ../../VERSION) | |
| build: clean | |
| rm -rf requirements.lock | |
| helm dependency build | |
| helm lint |
| pipeline { | |
| agent { | |
| label "jenkins-ruby" | |
| } | |
| environment { | |
| ORG = 'jenkinsx' | |
| APP_NAME = 'dashboard' | |
| CHARTMUSEUM_CREDS = credentials('jenkins-x-chartmuseum') | |
| } | |
| stages { |
| alex@amnesiac ~/mininode $ cat ~/test.js [6/1915] | |
| const os = require("os"); | |
| const fs = require("fs"); | |
| console.log("Platform: " + os.platform()); | |
| console.log("Release: " + os.release()); | |
| console.log("Homedir: " + os.homedir()); | |
| console.log("Uptime: " + os.uptime()); | |
| console.log("TotalMem: " + os.totalmem()); | |
| console.log("FreeMem: " + os.freemem()); |
| /* ---------------------------------------------------------------------------- | |
| * This file was automatically generated by SWIG (http://www.swig.org). | |
| * Version 3.0.11 | |
| * | |
| * This file is not intended to be easily readable and contains a number of | |
| * coding conventions designed to improve portability and efficiency. Do not make | |
| * changes to this file unless you know what you are doing--modify the SWIG | |
| * interface file instead. | |
| * ----------------------------------------------------------------------------- */ |
I want to cover a lot of ground in this post.
Let's discuss how clang(1) works and explore what I think would be an ideal
toolchain for Illumos-based systems. Firstly, how does clang work?
Let's eplore that a bit.
alex@meek:/home/alex$ clang -v -target x86_64-pc-hydraos1.0 test.c -o test
clang version 3.8.0 (tags/RELEASE_380/final)
Target: x86_64-pc-hydraos1.0
| #ifndef SYS_DWARF_H | |
| #define SYS_DWARF_H | |
| #include <stdint.h> | |
| /* | |
| * Integer representations - DWARF4 Section 7.26 | |
| */ | |
| typedef int8_t dwarf_sbyte; | |
| typedef uint8_t dwarf_ubyte; | |
| typedef uint16_t dwarf_uhalf; |
| /*- | |
| * Copyright (c) 2013 The NetBSD Foundation, Inc. | |
| * All rights reserved. | |
| * | |
| * This code is derived from software contributed to The NetBSD Foundation | |
| * by Matt Thomas of 3am Software Foundry. | |
| * | |
| * Redistribution and use in source and binary forms, with or without | |
| * modification, are permitted provided that the following conditions | |
| * are met: |