profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/cheerfulstoic/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Brian Underwood cheerfulstoic Fishbrain Stockholm, Sweden http://www.brian-underwood.codes/ Lover of #elixirlang

cheerfulstoic/devise-neo4j 6

Devise ORM for Neo4j

cheerfulstoic/ancestry 1

Organise ActiveRecord model into a tree structure

cheerfulstoic/ascii_press 1

Tools for publishing a set of ASCIIdoc files to WordPress

cheerfulstoic/absinthe 0

The GraphQL toolkit for Elixir

cheerfulstoic/activerecord-import 0

Extraction of the ActiveRecord::Base#import functionality from ar-extensions for Rails 3 and beyon

cheerfulstoic/active_touch 0

A more robust touch for ActiveRecord associations

cheerfulstoic/advent_of_code_2019 0

My solutions for some of advent of code 2019

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha a7ae1f72db7fc66abe032ff70c7669fe7f473fb7

CHANGELOG

view details

push time in 18 hours

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha f362e05210932db2a15f567593fcadd39604205a

Support specifying package versions in todo_or_die comments

view details

push time in 18 hours

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha f4b9ae1cdd1d8e96c0a591954f2a9f1f9ac8586e

Lower requirement for elixir version and bump version

view details

push time in 2 days

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha 177f2629b9183114041dd3b28b1660d89b7b3976

Notes about matching on dependency versions

view details

push time in 2 days

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha 941c6e087163a0020d426e63ab66f262381f4dbc

Future improvement notes

view details

push time in 3 days

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha 5c7a9197252e4c92d8ed01deb0c401047ffd6473

Version bump

view details

push time in 3 days

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha d07f734fe054e926cc44e9873e90896e3b432bf2

More fixes * Support notes without expressions (so that the built-in TODO/FIXME checks can be disabled) * Documentation * Fix typespecs

view details

push time in 3 days

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha 766f655c3aacb7b13e91a0da73d69a4303cc8bf0

Fixes * Timezone lookup issue * Custom tag name in params

view details

push time in 3 days

create barnchcheerfulstoic/todo_or_die_test

branch : main

created branch time in 4 days

created repositorycheerfulstoic/todo_or_die_test

created time in 4 days

push eventcheerfulstoic/credo_todo_or_die

Brian Underwood

commit sha c311c41d3384ef14a1e3ffd292b5234c2ace7043

Metadata and ex_doc for publishing

view details

push time in 4 days

create barnchcheerfulstoic/credo_todo_or_die

branch : main

created branch time in 4 days

created repositorycheerfulstoic/credo_todo_or_die

created time in 4 days

issue commentrrrene/credo

GenServer.call Credo.Service.SourceFileAST :put timeout

I just ran into the same issue as @nicklayb. I stated writing a whole comment until I saw his edits at the bottom, so in case somebody else skips them like me, make sure to check if you need runtime: false in your mix.exs 😆

tielur

comment created time in 4 days

push eventcheerfulstoic/json-db

Brian Underwood

commit sha 8583d89353072222d15a7d0124d395e3b96f0ccc

Tighten up UI even more

view details

push time in 7 days

issue openedtimescale/timescaledb

`ts_insert_blocker` trigger goes missing after a `ts-dump` / `ts-restore`

Relevant system information:

  • OS: timescale/timescaledb:2.2.0-pg13 Docker image. Output of uname -a: Linux timescaledb-0 5.4.0-67-generic #75-Ubuntu SMP Fri Feb 19 18:03:38 UTC 2021 x86_64 Linux
  • PostgreSQL version (output of postgres --version): postgres (PostgreSQL) 13.2
  • TimescaleDB version (output of \dx in psql): 2.2.0
  • Installation method: using Docker

Describe the bug

I ran a ts-dump and ts-restore of my database and noticed that afterward I was missing the following line when doing \d table_name:

Triggers:
    ts_insert_blocker BEFORE INSERT ON water_switch FOR EACH ROW EXECUTE FUNCTION _timescaledb_internal.insert_blocker()

I asked about it in this Slack thread and there wasn't a clear answer as to why. It seems like it's not a huge problem for the moment, though.

Since I hadn't saved the logs at the time I couldn't see if there were errors. David suggested that the next time I tried it I should save the logs and if the same thing happened and there were no errors that I should open an issue. It did and I've made this gist of the log output.

I've noticed this when doing a dump / restore on five different databases in five different namespaces in our kubernetes clusters.

To Reproduce

Steps to reproduce the behavior:

1.) Check \d table_name in a hypetable to see that the trigger is there 2.) Connect to PostgreSQL / TimescaleDB in docker container in kubernetes via port mapping: kubectl port-forward -n namespace timescaledb-0 5432:5432 3.) ts-dump --db-URI=postgresql://postgres:<password>@localhost/<database> --dump-dir=<local_path> 4.) ts-restore --db-URI=postgresql://postgres:<password>@localhost/<database> --dump-dir=<local_path> 5.) Check \d table_name and see that trigger is missing

Expected behavior Trigger is restored

Actual behavior Trigger is missing

created time in 7 days

push eventcheerfulstoic/json-db

Brian Underwood

commit sha 8cb8ad418e6a7f0128220b8a579e325a3be0ef79

Style changes and changes to compact UI

view details

push time in 10 days

push eventcheerfulstoic/json-db

Brian Underwood

commit sha 1967c96d531151d5b97bafd8564fa63c4fd1c395

More work on the README

view details

push time in 11 days

push eventcheerfulstoic/json-db

Brian Underwood

commit sha 15260a565154c2d18eaa22f298cfef2b4c9327e4

More work on the README

view details

push time in 11 days

push eventcheerfulstoic/json-db

Brian Underwood

commit sha 466b2a92000d87356ec7439ac3d888701908cc6e

More work on the README

view details

push time in 11 days

PublicEvent

issue commentphoenixframework/phoenix_live_view

Connection issues on Firefox

🤔 Weird, I don't have HTTPS-only mode on in Firefox...

Currently my live_view app is working in Firefox, but it definitely gets stuck sometimes, still. Sometimes creating a new table and opening it there helps, but sometimes not

Nicd

comment created time in 22 days

issue commenttimescale/timescaledb

duplicate key value violates unique constraint after restore when create index

I just ran into this and found that if I tweaked the index name (like adding a _ at the end) it created fine...

alx696

comment created time in 22 days

push eventcheerfulstoic/emoji_game

Brian Underwood

commit sha 1952b2d5fba9e455f5183efb474d32fda3aa18b7

Differentiating actor and player icons

view details

push time in a month

push eventcheerfulstoic/cheerfulstoic.github.io

Brian Underwood

commit sha 810aee5596ed68f73d4653db67770ea2fe1dbd0f

When deploying, commit _posts

view details

push time in 2 months

push eventcheerfulstoic/cheerfulstoic.github.io

Brian Underwood

commit sha 06a1b8ec198db46f57de7d80b20c9c20c85a3680

Deploy

view details

push time in 2 months

issue closedrevelrylabs/elixir-nodejs

Can Node.js keep state?

So this library keeps a set of workers in a pool to interface with Node.js. If I want to execute some Node.js code, is it possible to have an ongoing session or state? That is, if I make the same function call more than once I might get a different result back the second or third time? And, if so, would I need to have a "sticky session" with the user to make sure I get the same ongoing state?

I could write some JS code to store things or disk or in a DB and I might just do that, but I wanted to check first what this library is capable of. Thanks! 😊

closed time in 2 months

cheerfulstoic

issue commentrevelrylabs/elixir-nodejs

Can Node.js keep state?

Ah ha! I found this comment which mentions setting NODE_ENV=production, and that has suddenly given me state! If I start up different iex -S mix sessions I get different state, which is interesting, and I'd love to understand that, but it's working how I'd like, so I'm happy for now! 😁 Thanks!

cheerfulstoic

comment created time in 2 months

issue openedrevelrylabs/elixir-nodejs

Can Node.js keep state?

So this library keeps a set of workers in a pool to interface with Node.js. If I want to execute some Node.js code, is it possible to have an ongoing session or state? That is, if I make the same function call more than once I might get a different result back the second or third time? And, if so, would I need to have a "sticky session" with the user to make sure I get the same ongoing state?

I could write some JS code to store things or disk or in a DB and I might just do that, but I wanted to check first what this library is capable of. Thanks! 😊

created time in 2 months

push eventcheerfulstoic/cheerfulstoic.github.io

Brian Underwood

commit sha 5273c9a17ef21ffa91a72a88a272333e2c476d4b

Update feed.xml

view details

Brian Underwood

commit sha ec4f40a13bb9ee303eecfc90af169ab5bf6c6c91

Build with production environment

view details

push time in 2 months