till
Repos
204
Followers
165
Following
37

Prometheus compatible exporter to query DNSBLs/RBLs.

13
2

A GitHub action to deploy to runway!

2
0

Events

Created at 9 hours ago
issue comment
*.release.flatcar-linux.net doesn't deliver whole certificate chain anymore

There is a Prometheus setup, it needs some fixes for the alert sending…

Like a blackbox exporter? Happy to send a PR too or help.

Created at 14 hours ago
issue comment
*.release.flatcar-linux.net doesn't deliver whole certificate chain anymore

@pothos Is it possible to get some alerting setup? Like a http check could serve as a monitor and a cheap test.

Created at 15 hours ago
issue comment
Use CRLF for header separation, except sendmail, fixes #23

@schengawegga Yeah, as I said I am more surprised it took this long for someone to file a bug.

Created at 15 hours ago
started
Created at 1 day ago
issue comment
DeleteCollection on Fake client doesn't work

@liggitt a question: Wouldn't e.g. a panic("unsupported") make more sense? As in, to highlight when something is not supported. This just seems like a bug or very obscure behaviour otherwise.

Created at 6 days ago
Created at 1 week ago
Created at 1 week ago
Created at 1 week ago
started
Created at 1 week ago
started
Created at 1 week ago
Created at 1 week ago
client.debug

Hey,

just trying out your code and noticed that client.debug doesn't work as it's not exported (capitalized). Generally, maybe an option pattern would work nicer to setup the client?

lexoffice.NewClient(apiKey,
  lexoffice.WithDebug(true),
  lexoffice.WithHttpClient(myOwnClient),
)

func NewClient(apiKey, ...opts) (*lexoffice.Client, error) {
    // ...
    // probably range over the opts
}

Thoughts?

Created at 1 week ago
Created at 2 weeks ago
client.debug

@wolfgang-werner 👋 Sorry I closed this. Had no expected a response.

I started working on/fixing up another lib called golexoffice as it seemed to support more calls originally.

When I asked its author, they archived it and told me I could maintain it going forward as they are no longer using it.

Generally, we need contact management and invoices so far. I am also happy to collaborate on it going forward.

What I did so far is here: https://github.com/hostwithquantum/golexoffice

Mostly added error handling, and a basic test suite. The library was also really procedural.

Created at 2 weeks ago
till delete branch handle-errors
Created at 2 weeks ago

Fix: person/contact creation

  • make fields optional (to fix encoding of the struct)
  • make more fields optional when they can be

Fix: handle errors from the API

  • check if response is successful (before decoding)
  • parse error response(s)
  • add basic test coverage for legacy and new error responses
  • upgrade go to 1.20

Merge pull request #2 from hostwithquantum/handle-errors

handle errors

Created at 2 weeks ago
pull request closed
handle errors
  • Fix: person/contact creation
  • Fix: handle errors from the API
Created at 2 weeks ago
client.debug

Hey,

just trying out your code and noticed that client.debug doesn't work as it's not exported (capitalized). Generally, maybe an option pattern would work nicer to setup the client?

lexoffice.NewClient(apiKey,
  lexoffice.WithDebug(true),
  lexoffice.WithHttpClient(myOwnClient),
)

func NewClient(apiKey, ...opts) (*lexoffice.Client, error) {
    // ...
    // probably range over the opts
}

Thoughts?

Created at 2 weeks ago
till create tag v0.2.1-alpha.1
Created at 2 weeks ago

Chore: create a GH release

Fix: person/contact creation

  • make fields optional (to fix encoding of the struct)
  • make more fields optional when they can be

Fix: handle errors from the API

  • check if response is successful (before decoding)
  • parse error response(s)
  • add basic test coverage for legacy and new error responses
  • upgrade go to 1.20
Created at 2 weeks ago

Chore: create a GH release

Created at 2 weeks ago

Fix: handle errors from the API

  • check if response is successful (before decoding)
  • parse error response(s)
  • add basic test coverage for legacy and new error responses
  • upgrade go to 1.20
Created at 2 weeks ago
pull request opened
handle errors
  • Fix: person/contact creation
  • Fix: handle errors from the API
Created at 2 weeks ago

Fix: handle errors from the API

  • check if response is successful (before decoding)
  • parse error response(s)
  • add basic test coverage for legacy and new error responses
  • upgrade go to 1.20
Created at 2 weeks ago

Fix: person/contact creation

  • make fields optional (to fix encoding of the struct)
  • make more fields optional when they can be
Created at 2 weeks ago

Fix: person/contact creation

  • make fields optional (to fix encoding of the struct)
  • make more fields optional when they can be
Created at 2 weeks ago

Fix: person/contact creation

  • make fields optional (to fix encoding of the struct)
  • make more fields optional when they can be
Created at 2 weeks ago
till create branch handle-errors
Created at 2 weeks ago
set errors when using helpers

I am building a form similar to this (using the helper components): https://svelte-forms-lib-sapper-docs.vercel.app/helpers

My validation works pre submit, however, when I make my request to save my data and encounter an error, I am not sure how to write to the $errors store. Or how to even subscribe to it when I don't use createForm(). Would anyone have an example of how that is done?

Created at 2 weeks ago