nymous

Logging setup for FastAPI

This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.

Then, you can use Structlog loggers or standard logging loggers, and they both will be processed by the Structlog pipeline (see the hello() endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!

Requests are assigned a correlation ID with the asgi-correlation-id middleware (either captured from incoming request or generated on the fly). All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented. This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog. You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom

ThirVondukr

import base64
import enum
from typing import Any, Optional, Annotated

from sqlalchemy import select
from sqlalchemy.ext.asyncio import AsyncSession
from sqlalchemy.orm import InstrumentedAttribute, DeclarativeMeta
from sqlalchemy.sql import Select

from gql.modules.users._fields import UserOrder

samuelcolvin

const log_el = document.getElementById('log')

function log(...messages) {
  console.log(...messages)
  log_el.innerText += '\n' + messages.map(m => JSON.stringify(m, null, 2)).join(' ')
}

function error(message) {
  console.error(message)
  log_el.innerText += '\n' + message

donaldpipowitch

Whenever the server returns validation errors and we would set them with setFieldError they would be lost if any field would get a change or blur event. But we want to keep these kind of errors until the specific field changes. Additional we want to handle generic server errors (which are not specific to a field, but the whole form).

With these hooks field specific server side errors should be added like this:

const { setStatus } = useFormikContext();

const errors = {};
// adjust serverErrors to your own responses
// in this case they look like this: Array<{ name: string, error: string }>

ferndot

from django.conf import settings

from templated_mail.mail import BaseEmailMessage


class VerificationEmail(BaseEmailMessage):
    template_name = 'email/email_verification.html'

    def get_context_data(self):
        # Get context and user

whoisryosuke

import React, {Component} from 'react'
import Router from 'next/router'
import TokenContext from '../context/TokenContext'
import { getCookie } from '../utils/Cookies'
import ServerRedirect from 'utils/ServerRedirect'

export default function withAuth(AuthComponent) {
    return class Authenticated extends Component {

      static async getInitialProps(ctx) {

iMerica

urlpatterns = [
  url(r'^rest-auth/registration/account-confirm-email/(?P<key>[-:\w]+)/$', ConfirmEmailView.as_view(), name='account_confirm_email'),
]

pgjones

from flask import Flask, request
from werkzeug.http import dump_cookie

def test_cookie(app: Flask) -> None:
    header = dump_cookie('Name', 'value')
    with app.test_request_context(environ_base={'HTTP_COOKIE': header}):
        assert request.cookies['Name'] == 'value'

Tyrdall

"""
- Add some settings -
Log in to your sandbox account and get your API keys plus your merchant ID.

"""
BRAINTREE_PRODUCTION = False  # We'll need this later to switch between the sandbox and live account
BRAINTREE_MERCHANT_ID = “your_merchant_id”
BRAINTREE_PUBLIC_KEY = “your_public_key”
BRAINTREE_PRIVATE_KEY = “your_private_key”

dmpayton

#!/usr/bin/env python

import tornado.httpserver
import tornado.ioloop
import tornado.web
import tornado.websocket
import tornado.wsgi
from myapp.wsgi import application as myapp_wsgi

# Javascript Usage: