rpkamp
Repos
17
Followers
18
Following
7

A Mailhog API Client for PHP

24
10

A behat extension that allows interaction with Mailhog in your behat features

12
4

Behat context for mailhog/mink integration

4
1

The Minimal Bookmarks Tree extension for Google Chrome

31
5

Display customizable information about visited websites in a small popup

Events

issue comment
GoogleCloudLoggingFormatter timestamp does not work with Google Cloud Run

@lcobucci Please also check if it works when logging in UTC time. Cloud Run doesn't like our default timezone (CEST).

(see my first post for how we're doing it now)

Created at 1 month ago
issue comment
Sub-step logging

As an alternative, how about a separate interface, like LoggingContext, something like

interface LoggingContext
{
    public function setLogger(Some\Behat\Logger $logger): void;
}

Then when the context is created we can detect if it implements LoggingContext and if so call setLogger with our logger. During execution we can look at this logger to see what is logged there.

If the Behat logger implements the PSR interface we can even do nice things like take the logger we get from Behat and wire it up into our application so we can get application logs in Behat.

At least this way seems more versatile than method injection to me.

What do you think?

Created at 1 month ago
Max height/width shouldn't exist. Let us make it take up the whole screen if we want

There's no reason why the max height should be 600px. That is absurd.

I agree, but it's a limitation on Chrome's end, not on mine 🙁 I'll see if it's changed since I last looked, but I wouldn't get my hopes up...

I'll look into your other suggestions, but please note I do not have loads of time to work on this, so it might not happen soon, or indeed at all.

I do really like the default dark/light OS settings and the font size suggestions. I'll certainly look into those.

Created at 1 month ago
opened issue
GoogleCloudLoggingFormatter timestamp does not work with Google Cloud Run

Monolog version 2 and 3.

In our application we have a fingers crossed handler that passes to a stream handler that writes to php://stderr using the Google Cloud Logging Formatter. This mostly works fine, except that Google Cloud Run does not use the timestamp sent from monolog as the timestamp of the message. It seems to be taking the time it received the message instead. Most notably when we logged several messages, sleeping for 1 second between those messages, they all more or less the same timestamp in Google Cloud Logging, they certainly weren't a second apart.

Diving into it, it turns out sending messages through php://stderr is different than sending them through the logging API. Instead of timestamp the field time must be used, and the time must be in UTC.

We found that the following works for us when writing to php://stderr on Google Cloud Run (in Monolog 2):

$record['time'] = $record['datetime']->setTimezone(new DateTimeZone('UTC'))->format('Y-m-d\TH:i:s.u\Z');

I do wonder whether this should be changed in Monolog, because I don't know if the current implementation has a use case that I'm unaware off that uses the format that is now in the code (something else than Cloud Run and/or writing to php://stderr).

@lcobucci since you wrote the formatter in Monolog, do you have ideas on this?

Created at 1 month ago

Use gnome-extensions command to deploy when available

This command was introduced in Gnome 3.34

Use composition instead of inheritence for PopupMenuItem in CollectionItem

Extending PopupMenuItem in CollectionItem under gnome 3.34 breaks the reference to this inside the class.

Creating a new PopupMenuItem inside CollectionItem resolves this problem.

Add gnome 3.34 as supported version for this extension

Fix reference to boyscout rule in README

Fix links in README

Merge pull request #11 from rpkamp/fix-boyscout-reference

Fix reference to boyscout rule in README

fixed deploy script

fixed adding of collection menu item

Merge branch 'gnome-3.34'

version++

cleanup

installed prettier + eslint

Bump lodash from 4.17.15 to 4.17.19

Bumps lodash from 4.17.15 to 4.17.19.

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #12 from dpoetzsch/dependabot/npm_and_yarn/lodash-4.17.19

Bump lodash from 4.17.15 to 4.17.19

updates in preparation for gnome-shell 40 support

towards new gtk4 prefs widget

finished new prefs widget

Merge branch 'master' of github.com:dpoetzsch/keyman

final touches

fixed warning

Created at 2 months ago
Support Chrome Manifest v3

Turns out this can't be done yet as Manifest v3 doesn't have proper support for fetching favicons yet. That would be a big miss in this extension.

Related issue: https://bugs.chromium.org/p/chromium/issues/detail?id=104102

Created at 2 months ago
issue comment
Initial stab at creating scoped PHARs

I'm not particularly aware of any other projects using PHARs and also symphony's extension mechanism :/

Yes, that is the main issue for sure. The easiest way around this would be to create a custom interface inside Behat for extensions. Internally that could still use Symfony, but it shouldn't be exposed to the client at all.

Created at 2 months ago
delete branch
rpkamp delete branch scoped-phar
Created at 2 months ago