profile
viewpoint
TJ Miller sixlive @sixlabs @internationalbancard Metro Detroit https://www.tjmiller.me Full stack capable, backend developer. 💚 Laravel, Vue, React, Docker, Node

push eventsixlive/honeybadger-php

sixlive

commit sha fc36ac0716f41334dbb5ce2fd486bb9efdf1cc0a

Adds tests

view details

sixlive

commit sha 0b7f1d4aeeea30930327b0cbcbaaa4681bd8bab1

Changelog

view details

push time in 3 days

PR opened honeybadger-io/honeybadger-php

Add method arguments to backtrace

Description

Adds method arguments to backtrace where available. Resolves #84

The following code creates the following report in HB.

<?php

function foo($foo, $bar)
{
    throw new \Exception('Test argument exception');
}

Route::get('/', function () {
    foo('asdfasdf', 'th293475239748at');
});

Screen Shot 2019-07-15 at 6 51 26 AM

Todos

  • [ ] Tests
  • [ ] Documentation
  • [ ] Changelog Entry (unreleased)

Steps to Test or Reproduce

> git pull --prune
> git checkout <branch>
> vendor/bin/phpunit
+1 -0

0 comment

1 changed file

pr created time in 3 days

create barnchsixlive/honeybadger-php

branch : add-method-arguments-to-backtrace

created branch time in 3 days

delete branch sixlive/honeybadger-php

delete branch : add-fingerprint-and-tags

delete time in 3 days

push eventhoneybadger-io/honeybadger-php

TJ Miller

commit sha e4af88b8394c2a340b9cdb149162ff82e897edeb

Add fingerprint and tags (#76)

view details

push time in 3 days

PR merged honeybadger-io/honeybadger-php

Add fingerprint and tags enhancement

Description

Now that we have a way of passing additional params for exceptions we should add the ability to pass fingerprints and tags.

Related PRs

  • depends on #75

Todos

  • [ ] Tests
  • [ ] Documentation
  • [ ] Changelog Entry (unreleased)

Steps to Test or Reproduce

> git pull --prune
> git checkout <branch>
> vendor/bin/phpunit
+22 -0

0 comment

4 changed files

sixlive

pr closed time in 3 days

push eventsixlive/honeybadger-php

sixlive

commit sha 0b01f8f7f846e6611d2dffc19f388814396e78e0

changelog

view details

push time in 3 days

push eventsixlive/honeybadger-php

TJ Miller

commit sha 1b8cd79a7ebf60e08be58938e06225b022c456c8

Updates to PHPUnit 8 (#79) - Updates PHPUnit version - Resoves `assertArraySubset` warning

view details

Jess Archer

commit sha 14264e1aff47c0df382bb9626d620051144ad8b4

Handle empty API key (#80) The existing approach would only prevent reporting if the configured API key was explicitly of type `null`. If the key was an empty string, the API call would be made, and fail. It is common for API keys to be defined in a `.env` file, and also common for a values to be defined empty, especially in development environments when they are copied from a `.env.example` file and not being used for local development. When a value is left empty, it is parsed as an empty string rather than a null.

view details

TJ Miller

commit sha fa8820fe45ccd18becd9a526a4c5ed7a3477b102

Version (#81)

view details

TJ Miller

commit sha 1447b4ea48faf45bb3f08a2e83faea342ac858ad

Add an option to not send data (#82)

view details

sixlive

commit sha 677e556287067fdf16efdb1863975cbbc2a59800

Version

view details

TJ Miller

commit sha 300eaa7cb57a89125796dc66ed409bd14e3b1e4c

Adds a check to error settings in the error handler (#83)

view details

sixlive

commit sha 92da2600c452e8f7730d1d255df1091d3a973171

Version

view details

TJ Miller

commit sha 0aebbe6071ec23a721cf4d0fa6e86d226e9699e6

Accept grouping options for notification (fixed conflicts) (#85)

view details

sixlive

commit sha 2daa9cc4b5744fb94b59916940d5960eb6ff9db1

Merge remote-tracking branch 'upstream/master' into add-fingerprint-and-tags

view details

sixlive

commit sha 4817ae0d07b7d1d6dba062e6e66fa09ccd2da82b

Add tests for fingerprint and tags

view details

push time in 3 days

issue closedhoneybadger-io/honeybadger-php

Accept notification options for grouping

Honeybadger is accepting grouping options for easier error tracing. https://docs.honeybadger.io/lib/javascript/guides/customizing-error-grouping.html#grouping-by-component

I think that would be nicer if we can pass such options via honeybadger-php also.

closed time in 3 days

Kaname87

issue commenthoneybadger-io/honeybadger-php

Accept notification options for grouping

This will land in 1.6

Kaname87

comment created time in 3 days

push eventhoneybadger-io/honeybadger-php

TJ Miller

commit sha 0aebbe6071ec23a721cf4d0fa6e86d226e9699e6

Accept grouping options for notification (fixed conflicts) (#85)

view details

push time in 3 days

push eventsixlive/honeybadger-php

sixlive

commit sha b607d86d33f0182d08dd60bdbd7dc7c96e2c5a3a

wip

view details

push time in 3 days

push eventsixlive/honeybadger-php

sixlive

commit sha 1e397e70c4dacdcfdcaaeff05eea4a722be1dfb5

Working on CI errors

view details

push time in 3 days

PR closed honeybadger-io/honeybadger-php

Accept grouping options for notification

Status

READY

Description

Partially resolves 74

In this PR just only making component and action acceptable among the notification options. fingerprint is also grouping options but that is not a part of request but a part of error so not included in this change.

Related PRs

na

Todos

  • [x] Tests
  • [x] Documentation
  • [ ] Changelog Entry (unreleased)

Steps to Test or Reproduce

> git pull --prune
> git checkout <branch>
> vendor/bin/phpunit
+119 -4

5 comments

7 changed files

Kaname87

pr closed time in 3 days

pull request commenthoneybadger-io/honeybadger-php

Accept grouping options for notification

Closing in favor of #85

Kaname87

comment created time in 3 days

push eventsixlive/honeybadger-php

sixlive

commit sha 8a15e1cc71fa23ad541acf6373cfaf1fd5539c9c

Changelog

view details

push time in 3 days

PR opened honeybadger-io/honeybadger-php

fixed conflicts

Duplicate of #75 with fixed conflicts

+119 -8

0 comment

7 changed files

pr created time in 3 days

push eventspatie/laravel-uptime-monitor

Freek Van der Herten

commit sha b0f92d23dc807ed01068a9cd9cf7555121975274

Apply fixes from StyleCI (#185)

view details

push time in 5 days

PR merged spatie/laravel-uptime-monitor

Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.


For more information, click here.

+1 -1

0 comment

1 changed file

freekmurze

pr closed time in 5 days

push eventsixlive/json-schema-to-openapi-schema

TJ Miller

commit sha 441c1174420cd67e40b0e2e527e962e257f2089d

Update index.js

view details

push time in 6 days

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

The patch was part of honeybader-php

riyuk

comment created time in 21 days

issue commenthoneybadger-io/honeybadger-laravel

[Enhancement] Make a artisan deploy command

@riyuk Deployed with v1.6.0

riyuk

comment created time in 21 days

created taghoneybadger-io/honeybadger-laravel

tagv1.6.0

PHP/Laravel library for reporting errors to Honeybadger.io :elephant: :zap:

created time in 21 days

release honeybadger-io/honeybadger-laravel

v1.6.0

released time in 21 days

push eventhoneybadger-io/honeybadger-laravel

sixlive

commit sha 40480a582bd6d50269d47438e4865f6a5363a55d

Version

view details

push time in 21 days

delete branch honeybadger-io/honeybadger-laravel

delete branch : analysis-qMm0YM

delete time in 21 days

push eventhoneybadger-io/honeybadger-laravel

TJ Miller

commit sha 6a98903936b7bd17930a232587aac184b162ebf9

Apply fixes from StyleCI (#30)

view details

push time in 21 days

PR merged honeybadger-io/honeybadger-laravel

Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.


For more information, click here.

+2 -2

0 comment

2 changed files

sixlive

pr closed time in 21 days

PR opened honeybadger-io/honeybadger-laravel

Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.


For more information, click here.

+2 -2

0 comment

2 changed files

pr created time in 21 days

delete branch sixlive/honeybadger-laravel

delete branch : add-deploy-command

delete time in 21 days

push eventhoneybadger-io/honeybadger-laravel

TJ Miller

commit sha 830727e03a670ff21893fb400c2dd34560a3d490

Add deploy command (#26)

view details

push time in 21 days

PR merged honeybadger-io/honeybadger-laravel

Add deploy command

Status

<!--- READY/WIP/HOLD ---> WIP

Description

Adds a deploy command honeybadger:deploy. Unless the options are passed to the command it will resolve params from the Laravel/Honeybadger config (config/honeybadger.php) and system calls to get the git hash and local username. The command will merge options together if mixed options are passed.

Options: honeybadger:deploy --apiKey="" --environment="" --revision="" --repository= --username=""

Resolves #25

I STILL NEED TO DO FINAL TESTING TO HONEYADGER IN PRODUCTION

Related PRs

n/a

Todos

  • [x] Tests
  • [ ] Documentation
  • [ ] Changelog Entry (unreleased)

Steps to Test or Reproduce

> git pull --prune
> git checkout <branch>
> vendor/bin/phpunit
+252 -1

2 comments

4 changed files

sixlive

pr closed time in 21 days

issue closedhoneybadger-io/honeybadger-laravel

[Enhancement] Make a artisan deploy command

<!-- Thanks for reporting an issue! Please fill out the blanks below. -->

I just wondered why there is no php artisan honeybadger:deploy command which runs on the server after a deployment. (like in Forge, deployment-scripts)

Is there a easy way to integrate this using the env-variables?

closed time in 21 days

riyuk

push eventsixlive/honeybadger-laravel

sixlive

commit sha 2a108d43da56d5c7323ca67ba1db5bf1703d6bbe

Fixed some issues when doing production testing

view details

push time in 21 days

issue commenthoneybadger-io/honeybadger-php

Method call arguments on the stacktrace/backtrace

The team over at Homeybadger is working on the server side API to support this and then I can wrap up the implementation. We’re looking somewhere around a week to get this sorted and tagged.

abishekrsrikaanth

comment created time in 22 days

issue commenthoneybadger-io/honeybadger-php

Method call arguments on the stacktrace/backtrace

Still looking into it and working out an implementation. I agree that this is a must-have feature.

abishekrsrikaanth

comment created time in 22 days

issue commenthoneybadger-io/honeybadger-php

Method call arguments on the stacktrace/backtrace

I’ll look at it this weekend!

abishekrsrikaanth

comment created time in 25 days

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

@riyuk I just verified that it’s now published to packagist.

riyuk

comment created time in a month

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

@riyuk There seems to be an issue getting it over to packagist, I dont have admin access to that account but I'm working with the team to get that fixed.

riyuk

comment created time in a month

pull request commenthoneybadger-io/honeybadger-php

Update error handler with additional checks

Honestly, I went back and forth on this several times. Almost all examples that I've reviewed just exited early if it shouldn't be reported.

sixlive

comment created time in a month

issue closedhoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

What are the steps to reproduce this issue?

Tinker: Auth::loginUsingId(1)

What happens?

I get tons of Errors like unlink(/home/forge/abc/storage/framework/sessions/NfkuYxmlk3ZjVy0wirhi2uqsZsIYajEyLJlI61Yk): No such file or directory

What were you expecting to happen?

No errors - since errors get suppresed with @! See: https://github.com/laravel/framework/blob/5.8/src/Illuminate/Filesystem/Filesystem.php#L207

Any other comments?

See: https://github.com/laravel/framework/issues/22514

What versions are you using?

Operating System: PHP 7.2 fpm Package Version: 1.5.0

closed time in a month

riyuk

created taghoneybadger-io/honeybadger-php

tagv1.5.1

PHP library for reporting errors to Honeybadger.io :elephant: :zap:

created time in a month

release honeybadger-io/honeybadger-php

v1.5.1

released time in a month

push eventhoneybadger-io/honeybadger-php

sixlive

commit sha 92da2600c452e8f7730d1d255df1091d3a973171

Version

view details

push time in a month

delete branch sixlive/honeybadger-php

delete branch : update-error-handler-with-additional-checks

delete time in a month

push eventhoneybadger-io/honeybadger-php

TJ Miller

commit sha 300eaa7cb57a89125796dc66ed409bd14e3b1e4c

Adds a check to error settings in the error handler (#83)

view details

push time in a month

PR merged honeybadger-io/honeybadger-php

Update error handler with additional checks

Description

Adds a check to ensure error reporting is enabled for that particular error. Fixes an issue where error suppression does not prevent the error from being reported.

Related Issues

  • https://github.com/honeybadger-io/honeybadger-laravel/issues/27

Tasks

  • [x] Tests
  • [x] Changelog
+8 -2

0 comment

2 changed files

sixlive

pr closed time in a month

push eventsixlive/honeybadger-php

sixlive

commit sha 6a023d9c401e590159888cfe9854f3fa642db9bc

Adds a check to error settings in the error handler

view details

push time in a month

push eventsixlive/honeybadger-php

sixlive

commit sha 1212740b1e1556d04be96bb53005fc02645c450e

Changelog updates [ci skip]

view details

push time in a month

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

I've opened https://github.com/honeybadger-io/honeybadger-php/pull/83 to address this.

riyuk

comment created time in a month

push eventsixlive/honeybadger-php

sixlive

commit sha d43b0f59223d26fe155b1ecb3600ca01e0d58397

Adds a check to error settings in the error handler

view details

push time in a month

push eventsixlive/honeybadger-php

sixlive

commit sha 9be29bcff9f05157b16c281bf33ea8bcbdca9ad7

Styles

view details

push time in a month

PR opened honeybadger-io/honeybadger-php

Update error handler with additional checks

Description

Adds a check to ensure error reporting is enabled and that the error should be reported based on error reporting settings inside the PHP Engine

Tasks

  • [x] Tests
  • [x] Changelog
+11 -5

0 comment

3 changed files

pr created time in a month

push eventsixlive/honeybadger-php

sixlive

commit sha 19a091d27c4c2ea1d6e9faa9f3c264e7417e0c1c

Updates changelog

view details

push time in a month

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

100% what I’m thinking too. I have something worked up just need to finish testing

riyuk

comment created time in a month

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

Is there any way you can get me your current php settings so I can ensure we are testing the same thing?

riyuk

comment created time in a month

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

I might have an idea, I’ll try and write a test for it today

riyuk

comment created time in a month

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

I don’t think this has anything to do with the library we simply register an optional global error handler. I believe this needs to be resolved through your PHP engine error settings.

riyuk

comment created time in a month

issue closedspatie/laravel-uptime-monitor

Bug: Status Code wrong

I wrote a custom class to check the status code, but the status code returned to your class is always 200.. The Guzzle code is correct, but doesn't appear to be the same code passed to the interfaces.

class ExampleChecker implements UptimeResponseChecker { public function isValidResponse(ResponseInterface $response, Monitor $monitor) : bool { dd($response->getStatusCode()); // Always returns 200. }

Brand new install of Laravel 5.8, and your extension.

    "require": {
        "php": "^7.1.3",
        "fideloper/proxy": "^4.0",
        "laravel/framework": "5.8.*",
        "laravel/tinker": "^1.0",
        "spatie/laravel-uptime-monitor": "^3.5"
    },

closed time in a month

adam-devapp

issue commentspatie/laravel-uptime-monitor

Bug: Status Code wrong

The status code sent to the checker will only be 200-300 level codes, 400 and 500 throw an exception and will fail the checker.

adam-devapp

comment created time in a month

issue commentspatie/laravel-uptime-monitor

certificate_check_failure reason truncated

@atymic that would be great!

dabonzo

comment created time in a month

Pull request review commentspatie/laravel-uptime-monitor

feat: allow configuration of guzzle client options

  $factory->define(Monitor::class, function (Faker\Generator $faker) {     return [-        'url' => 'http://localhost:9000',+        'url' => sprintf('http://localhost:%d', getenv('TEST_SERVER_PORT')),

Can we set 9000 as the default somewhere?

atymic

comment created time in a month

push eventsixlive/honeybadger-laravel

TJ Miller

commit sha 34d9e22c15cc25a4e593f6288a7abef58ce51200

Update composer.json

view details

push time in 2 months

Pull request review commenthoneybadger-io/honeybadger-laravel

Adds support for `report_data`

     ],     "require": {         "php": "^7.1",-        "honeybadger-io/honeybadger-php": "^1.2",+        "honeybadger-io/honeybadger-php": "^1.3",
        "honeybadger-io/honeybadger-php": "^1.5",
sixlive

comment created time in 2 months

created taghoneybadger-io/honeybadger-php

tagv1.5.0

PHP library for reporting errors to Honeybadger.io :elephant: :zap:

created time in 2 months

release honeybadger-io/honeybadger-php

v1.5.0

released time in 2 months

push eventhoneybadger-io/honeybadger-php

sixlive

commit sha 677e556287067fdf16efdb1863975cbbc2a59800

Version

view details

push time in 2 months

PR opened honeybadger-io/honeybadger-laravel

Adds support for `report_data`

Description

Add the new report_data option to the default config initially excluding the testing env which is set for phpunit by default with Laravel.

Notes

Requires https://github.com/honeybadger-io/honeybadger-php/pull/82 to be released, updated composer requirements for the perspective version.

+3 -2

0 comment

3 changed files

pr created time in 2 months

create barnchsixlive/honeybadger-laravel

branch : add-report-data-option-to-config

created branch time in 2 months

delete branch sixlive/honeybadger-php

delete branch : add-option-to-not-send-data

delete time in 2 months

push eventhoneybadger-io/honeybadger-php

TJ Miller

commit sha 1447b4ea48faf45bb3f08a2e83faea342ac858ad

Add an option to not send data (#82)

view details

push time in 2 months

PR merged honeybadger-io/honeybadger-php

Add an option to not send data

Description

Adds an option for whether the library should send data back to the API, this is useful in testing or staging environments.

new Honeybadger([
    'report_data' => false,
])
+40 -6

0 comment

6 changed files

sixlive

pr closed time in 2 months

push eventsixlive/honeybadger-php

sixlive

commit sha ef17a38bb4887afd00eac8f181ea24d02d66a0c1

wip

view details

push time in 2 months

PR opened honeybadger-io/honeybadger-php

Add an option to not send data

Description

Adds an option for whether the library should send data back to the API, this is useful in testing or staging environments.

new Honeybadger([
    'report_data' => false,
])
+39 -5

0 comment

6 changed files

pr created time in 2 months

create barnchsixlive/honeybadger-php

branch : add-option-to-not-send-data

created branch time in 2 months

push eventsixlive/jigsaw-starter

Bryan Monzon

commit sha ab4366e417237e00852453072d56425a209030a5

updated tailwind and dependencies to match Jigsaw's default (#1) * remove old tailwind config and add new * update tailwind to 1.0.1 and all of the npm dependencies * update webpack.mix file with new config * update build.js file with the newest stuff * update php packages to the latest

view details

push time in 2 months

PR merged sixlive/jigsaw-starter

updated tailwind and dependencies to match Jigsaw's default

Brought Tailwind up to 1.0.1, updated the npm dependencies and the tasks/build.js file to match Jigsaw's default. Figured I'd send a PR with it in case you wanted it.

+11352 -1157

1 comment

7 changed files

bryanmonzon

pr closed time in 2 months

pull request commentsixlive/jigsaw-starter

updated tailwind and dependencies to match Jigsaw's default

Whoa! Awesome!

bryanmonzon

comment created time in 2 months

issue commentspatie/laravel-uptime-monitor

SSL problem reports site offline (but is up!)

Maybe the certificate check cannot be performed because the site is unreachable for the monitor?

This is correct.

goyne

comment created time in 2 months

issue commentspatie/laravel-uptime-monitor

SSL problem reports site offline (but is up!)

Lets get some clarity, maybe we aren't on the same page.

The site is reported up (since it is reachable)

Most important of all: the very site is up. Reachable for any user.

In the browser, its up but it's not according to the monitor. If it can't negotiate SSL then it is effectively unreachable.

The certificate is reported unhealthy (there's no certificate report given)

The package is promised to be able to monitor uptime (again: the site is up) AND certificate health.

Are you running certificate checks as well as uptime checks? Is the uptime failing due to the cert but the cert check is passing? (this would absolutely be a problem)

goyne

comment created time in 2 months

issue closedspatie/laravel-uptime-monitor

SSL problem reports site offline (but is up!)

I'm not sure if this is how it should be. I'm testing around with the package and one of my sites is reported offline (which is certainly not the case!).

The reason given by the package (see screen dump):

cURL error 60: SSL certificate problem: unable to get local issuer certificate (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Schermafbeelding 2019-05-20 om 21 21 41

Ok, the certificate needs a little work (I guess), but it seems to me that this is no reason to report the site down? Even Google believes the certificate is valid.

Schermafbeelding 2019-05-20 om 21 49 10

Have used the default configuration (as shipped with the package, latest version) on a clean Laravel installation (also the latest version).

Any clue on this? I'm pulling my hair out since the site is very very up...

closed time in 2 months

goyne

issue commentspatie/laravel-uptime-monitor

SSL problem reports site offline (but is up!)

I agree with @dabonzo that this is a server error. I feel like this might be a false positive if it is a server issue but if there was legitimately an issue with the certificate your site would be unreachable and therefore "down" to any users or other services.

goyne

comment created time in 2 months

issue closedspatie/laravel-uptime-monitor

Get SSL status for IP address.

Some IP addresses are served over a valid SSL but the SSL check with the uptime monitor fails. For example 1.1.1.1 is CloufFlare's IP address for DNS and that serves a valid SSL.

closed time in 2 months

rehmatworks

issue commentspatie/laravel-uptime-monitor

Get SSL status for IP address.

This makes sense as my test worked fine. I’m going to chalk this up to a server issue and close. Thanks @dabonzo!

If you feel I closed this without solving your problem I’m willing to continue the discussion.

rehmatworks

comment created time in 2 months

CommitCommentEvent

startedblastcloud/guzzler

started time in 2 months

issue commentspatie/laravel-uptime-monitor

SSL problem reports site offline (but is up!)

Hmm I’ll take a closer look, this is a CURL error so I’ll have to look at the Guzzle configuration.

goyne

comment created time in 2 months

issue commentspatie/laravel-uptime-monitor

Should CURL error be pushed to slack?

Can you decern if the curl error is happening during the monitor check or is the curl error happening when trying to hit the slack webhook?

albertStaalburger

comment created time in 2 months

issue commentspatie/laravel-uptime-monitor

certificate_check_failure reason truncated

I'll consider changing it to TEXT. In the meantime, you could publish the migration and make the update yourself.

dabonzo

comment created time in 2 months

issue commentspatie/laravel-uptime-monitor

Get SSL status for IP address.

I'm going to look into this further. I'm a bit short on time today but I'll get to it this week. If you want to open a PR in the meantime I'd be happy to review!

rehmatworks

comment created time in 2 months

issue closedspatie/laravel-uptime-monitor

Cannot use database driver

When trying to use database driver in an extended notification class, the following error is raised:

Call to undefined method Spatie\UptimeMonitor\Notifications\Notifiable::morphMany()

closed time in 2 months

rehmatworks

issue commentspatie/laravel-uptime-monitor

Cannot use database driver

Using a user model is the appropriate solution. After all inheritance, it ultimately ends up extending Illuminate\Notifications\Notification::class and never actually has a connection to the database. You would need to use a notifiable that is attached to a model.

I'm still familiarizing myself to the intricacies of this package but this is how I understand it at the moment. I'm going to go ahead and close this as I feel you made the correct adjustment and this isn't an issue with the package itself.

rehmatworks

comment created time in 2 months

issue commentspatie/laravel-uptime-monitor

Cannot use database driver

Can you post more of the extended notification class so I can get more context?

rehmatworks

comment created time in 2 months

issue commenthoneybadger-io/honeybadger-laravel

Error suppresion with @ doesn't seem to work

I believe this is caught and reported by the global error handler. I'll take a look at this over the weekend.

riyuk

comment created time in 2 months

startedspatie/laravel-uptime-monitor

started time in 2 months

issue commentspatie/laravel-uptime-monitor

How to json_encode the eloquent reponse

Tagged in https://github.com/spatie/laravel-uptime-monitor/releases/tag/3.5.0

dabonzo

comment created time in 2 months

more