Skip to content

Instantly share code, notes, and snippets.

View willismonroe's full-sized avatar

M. Willis Monroe willismonroe

View GitHub Profile
@aparrish
aparrish / index.md
Last active April 7, 2021 14:37
aparrish workshop for machine literacy at sfpc

Introduction to Natural Language Processing and Word Vectors

Nothing is more essentially human than linguistic communication. But when programmers, data scientists, and computational linguists work with language, the abstractions they work with sometimes don't line up with your intuitive understanding of spelling and grammar. In this workshop, we'll investigate the state of the art of natural language processing, including: a whirlwind tour of spaCy for parsing English into syntactic constituents; a discussion of techniques for classifying and summarizing documents; and an explanation and demonstration of "word vectors" (like Google's word2vec), an innovative language technology that allows computers to process written language less as discrete units and more like a continuous signal. Workshop participants will develop a number of small projects in text analysis and poetics using a public domain text of their choice. In becoming familiar with contemporary techniques for computational language analysis, cri

@AtulKsol
AtulKsol / psql-error-fix.md
Last active April 10, 2024 07:41
Solution of psql: FATAL: Peer authentication failed for user “postgres” (or any user)

psql: FATAL: Peer authentication failed for user “postgres” (or any user)

The connection failed because by default psql connects over UNIX sockets using peer authentication, that requires the current UNIX user to have the same user name as psql. So you will have to create the UNIX user postgres and then login as postgres or use sudo -u postgres psql database-name for accessing the database (and psql should not ask for a password).

If you cannot or do not want to create the UNIX user, like if you just want to connect to your database for ad hoc queries, forcing a socket connection using psql --host=localhost --dbname=database-name --username=postgres (as pointed out by @meyerson answer) will solve your immediate problem.

But if you intend to force password authentication over Unix sockets instead of the peer method, try changing the following pg_hba.conf* line:

from