LM emptymalei

title: "Event title" slug: event-title date: "2020-03-02T19:30:00+01:00" summary: "the standard says this should be less than 75 characters!" end: "2020-03-02T22:00:00+01:00" location: "Event location if known" organizer: name: "Your name" email: "[email protected]"

Permanent WSL DNS Fix (WSL 2.2.1+)

If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.

This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.

DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.

To upgrade WSL, follow these steps,

This gist and its comments contains some topics for technology section of data weekly

Comparison of ZSH frameworks and plugin managers

Changelog

update 1: add a FAQ section
update 2: benchmark chart and feature comparison table
update 3:
- improve the table with missing features for antigen
- new zplg times result

TLDR

I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.

But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.

Svelte is a language.

Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?

A few projects that have answered this question:

Python `@property` inheritance the right way

Given a Parent class with value property, Child can inherit and overload the property while accessing Parent property getter and setter.

Although we could just reimplement the Child.value property logic completely without using Parent.value whatsover, this would violate the DRY principle and, more important, it wouldn't allow for proper multiple inheritance (as show in the example property_inheritance.py bellow).

Two options:

Child redefines value property completely, both getter and setter.

	import pyspark.sql.functions as F
	from pyspark.sql import Window

	df = spark.createDataFrame([
	('d1',None),
	('d2',10),
	('d3',None),
	('d4',30),
	('d5',None),
	('d6',None),

	An error occurred while installing nokogiri
	(1.8.0), and Bundler cannot continue.
	Make sure that `gem install nokogiri -v '1.8.0'
	--source 'https://rubygems.org/'` succeeds before
	bundling.

	import numpy as np
	import plotly.offline as pyo
	import plotly.graph_objs as go

	# Generate a random signal
	np.random.seed(42)
	random_signal = np.random.normal(size=100)

	# Offset the line length by the marker size to avoid overlapping
	marker_offset = 0.04

	// [START apps_script_bigquery_update_sheet]
	/**
	* Runs a BigQuery query and replace the existing sheet
	*/

	/**
	* Add a custom menu to the spreadsheet when it is opened.
	*/
	function onOpen() {
	var spreadsheet = SpreadsheetApp.getActive();