Henrik Feldt

Dependency on Microsoft's OWIN?

1

Hi, We have a user at https://gitter.im/SuaveIO/suave who'd like to use this library, but it would seem this library is not OWIN compatible? Would it be possible to make it...

**Is your feature request related to a problem? Please describe.** It would be great if Mage supported Hudi incremental SQL queries, running on e.g. Spark or Flink. It should support...

Startup failure: current transaction is aborted, commands ignored until end of transaction block

7

## Bug report When adding new models (in a bad manner by not making migrations for them; just declaring them) Medusa doesn't start, because for the get currency query, a...

Hard to get started

2

Hi, So far I've spent about six hours trying to get started with a single sample. I'm trying to run a sample and integrate Textile with my p2p outdoor app,...

Transitive editable deps fail

1

If you have `svc/A`, `libs/a`, `libs/b` and `A` depends on both `a` and `b`, and `b` depends on `a`, installing `b` via the dockerfiles in this repo (the wheel output...

Hi, I was wondering how this would compose with e.g. a javascript library like ReactJS? ReactJS has a virtual DOM and takes care of rendering itself; would an adapter for...

'Dot' object has no attribute 'encode'

1

I'm trying to make one of your extensions work (completely new to IPython, first notebook, first code I'm writing in python)... It's going well, trying to plot strings, like one...

subdir breaks `librarian-puppet update`

1

Repro: 1. create a new Puppetfile, with a git ref with a subdir 2. run `librarian-puppet update` ``` error: pathspec 'origin/master' did not match any file(s) known to git. /Users/henfel/.rvm/gems/ruby-1.9.3-p374@logibit-receipts/gems/librarian-puppet-simple.haf-0.1.1/lib/librarian/puppet/simple/util.rb:40:in...

**Describe the bug** According to the docs, I can feed `intl_translation:extract_to_arb` a wildcard path: > This supports wildcards. For example, to extract messages from a series of files in path...

Deploying this

6

What's the recommended way of deploying this? `medusa-vendor build` generates `build-vendor` in the `./api` folder; but I don't want to deploy the dev server in prod... Is there an equivalent...