Files
org/notes.org
Thomas Ruoff efa1c405ef more
2019-10-18 12:33:18 +02:00

5.1 KiB
Raw Blame History

My Notes

Work

Reoccuring Tasks

TODO Schedule Day

SCHEDULED: <2019-10-08 Tue 08:30-08:45>

TODO Catch-Up (Emails/Slack)

SCHEDULED: <2019-10-09 Wed 09:00-09:15 .+1d>

  • State "DONE" from "WAIT" [2019-10-08 Tue 09:24]

TODO Code Reviews

SCHEDULED: <2019-10-08 Tue 09:15 .+1d>

  • State "DONE" from "WAIT" [2019-10-08 Tue 09:24]

CLOCK: [2019-10-08 Tue 08:24][2019-10-08 Tue 09:24] => 1:00

Sprint Work

Sprint Ceremonies

Other meetings

fb token service

DONE investigate access_token null

CLOSED: [2019-10-14 Mon 10:31] INVITE SECRET iPh5foo2ief4uv,i mit line break

Seems weird, getting quite some errors in the live logs. Not too many but still.

Added some more logging to the error in this PR.

DONE check fb token service logs

CLOSED: [2019-10-14 Mon 10:31] SCHEDULED: <2019-10-08 Tue>

TODO iventigate page token count

page tokens stored 187 on here another 187 on here

funnily on different nodes

DONE Update graph API version

CLOSED: [2019-10-09 Wed 10:51]

Howtos

setup mitmproxy

  1. write a script to modify the response

      from mitmproxy import http
    
      def request(flow):
          if flow.request.pretty_url.find("/classifiers/trainings") >=0 and flow.request.method == 'PUT':
              flow.response = http.HTTPResponse.make(
                  500,
                  "<html><body>failed with mitmproxy</body></html>",
                  {"content-type":"text/html"},
              )
  2. mitmproxy --mode reverse:https://bwjsonapi.stage.brandwatch.net -p 9999 -s <scriptName>
  3. ./runInDevelopment --apiUrl=http://localhost:9999

mitmproxy scripts

throttle all request in random order
from threading import Timer
from random import random
from mitmproxy import http

def request(flow):
    resumeLater = Timer(random() * 2, flow.resume)
    flow.intercept()
    resumeLater.start();

jq usage

Get ids from a json response { results: [{id: 4}, ...] }

curl URL | jq '.results[] | .id'

Things to pass on

TODO kitchen duty calendar

SCHEDULED: <2019-10-10 Thu> DEADLINE: <2019-10-15 Tue>

TODO remove Kamil from kitchen duty calendar

SCHEDULED: <2019-10-10 Thu>

TODO slack calendar integrations

DEADLINE: <2019-10-15 Tue> SCHEDULED: <2019-10-10 Thu>

TODO dependabot assignment

SCHEDULED: <2019-10-10 Thu>

Other

TODO separate randomly failing unit tests

There are some randomly failing unit tests in the frontend. We currently retry ALL backbone frontend unit tests when they fail.

This slows down CI and does not really help in identifying these.

As a intermedate solution we want to separate these randomly failing unit tests in an own directory to be able to separate them from unit tests that work fine.

This enables us to get rid of retrying all of them when some test fails.

Failing tests

Axiom WG

arbeitszeugnis

sonstige services

Private