kennwhite

Setting up VS Code and Golang with debug & build flag (-tags foo) support

This is the setup that worked for me after half a day of hacking around and chasing rabbit holes down old forum posts and open & closed Github issues.

Problem: While Go integration with VS Code is pretty slick in general, I needed to pass compile-time build flags, e.g., -tags foo[^1] to go build and go run directives, and I wanted to be able to properly debug with breakpoints etc. While there are some promising tutorials out there like this on Digital Ocean and on Log Rocket it turned out that one of the first things they both say to do is add the Delve extension to VS Code,

reytech-dev

Steps to fix "error file '/boot/vmlinux-x.x-x86_64' not found (Manjaro)

Great help: https://forum.manjaro.org/t/boot-error-vmlinuz-5-6/2896/3

https://forum.manjaro.org/t/boot-error-vmlinuz-5-6/2896/2

1. Create Live Stick with Manjaro

• Download: https://manjaro.org/downloads/official/gnome/
• Create bootstick: https://manjaro.org/support/firststeps/#making-a-live-system

2. Change UEFI Settings on your broken system: Boot > Secure Boot > Other OS (You can also disable UEFI, but make sure to re-enable it after you are done here!!)
3. Boot broken system with the live-system

narath

require 'faraday'
require 'uri'

data = {
  :your_data => "YOUR DATA"
}

url = "some url"

response = Faraday.post(url) do |req|

conormm

R to python data wrangling snippets

The dplyr package in R makes data wrangling significantly easier. The beauty of dplyr is that, by design, the options available are limited. Specifically, a set of key verbs form the core of the package. Using these verbs you can solve a wide range of data problems effectively in a shorter timeframe. Whilse transitioning to Python I have greatly missed the ease with which I can think through and solve problems using dplyr in R. The purpose of this document is to demonstrate how to execute the key dplyr verbs when manipulating data using Python (with the pandas package).

dplyr is organised around six key verbs:

jagregory

So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

* Off the top of my head *

1. Fork their repo on Github
2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

    git remote add my-fork [email protected]