telescope | tracking blogs in orbit around Seneca

I see that the NexmoServiceProvider is trying to use the defined http_client in the config, so can you share what the .env has for NEXMO_HTTP_CLIENT ? I am pretty sure you have something wrong there or even not defined.

And this is what it is defined in the config/nexmo.php related to that config:

If your current data is strictly one sentence per line, then by far the easiest thing to do is to just leave it like that and to give the option -ssplit.eolonly=true.

There unfortunately isn't an option to pass through certain kinds of meta-data or delimiters without attempting to parse or process them. However, you can indicate that they should not be made part of other sentences by means of the ssplit.boundaryTokenRegex or ssplit.boundaryMultiTokenRegex properties. However, your choices are then either to just delete them (see ssplit.tokenPatternsToDiscard) or else to process them as weird sentences, which you'd then need to clean up.

:h isdirectory

isdirectory({directory})

isdirectory() The result is a Number, which is non-zero when a directory with the name {directory} exists. If {directory} doesn't exist, or isn't a directory, the result is FALSE. {directory} is any expression, which is used as a String.

:h FALSE

For boolean operators Numbers are used. Zero is FALSE, non-zero is TRUE. You can also use |v:false| and |v:true|. When TRUE is returned from a function it is the Number one, FALSE is the number zero.

Make sure that FALSE is actually false. It is probably 0 which would be a true value in Lua. In Lua any values but false or nil are true.

So ideally check if vim.fn.isdirectory('.git') ~= 0 then

Telescope allows you to search entries by "tag". Often, tags are Eloquent model class names or authenticated user IDs which Telescope automatically adds to entries. Occasionally, you may want to attach your own custom tags to entries. To accomplish this, you may use the Telescope::tag method. The tag method accepts a closure which should return an array of tags. The tags returned by the closure will be merged with any tags Telescope would automatically attach to the entry. Typically, you should call the tag method within the register method of your App\Providers\TelescopeServiceProvider class:

This issue is resolved in the version 8.29.0. You will either need to upgrade to the version specified, or downgrade the version of pusher-http-php (composer require pusher/pusher-php-server ^4.1)

as @bk2204 helped me to realize my faulty assumption that checkout@v2 sets composer to v2 I was able to resolve my problem by changing the laravel.yml deployment instructions as follows:

1. Remove App\Providers\TelescopeServiceProvider::class from config/app.php because all providers inside config/app.php is automatically loaded. But in your production environment, laravel/telescope isn't installed that means Laravel\Telescope\TelescopeApplicationServiceProvider is undefined and App\Providers\TelescopeServiceProvider can not extend an undefined class.

2. Register App\Providers\TelescopeServiceProvider::class manually inside app/Providers/AppServiceProviders.php

The warning you're getting about page.current_path not available when attempting to screenshot is probably because your RSpec after hooks are installed in the wrong order (session is being reset before the screenshot call is made).

As for the failing test, it's really hard to tell exactly what you're doing but a number of things stand out as potential issues

1. I'm assuming the element ids are named #task_ If it's not and instead it's #task_ then you need to rethink how you're doing the test

2. tbody:nth-child(2) finds the tbody that is a second child, not the second child of the tbody element. I'm guessing you wanted tbody tr:nth-child(2) ...

3. There is no need to find the element before doing within since within will find the element (with retry/waiting)

4. The saving of the new order has to be committed before you call the second visit - hopefully your check for the element being in a different row does indicate the order has been saved.

Applying those 3 I end up with

You need to have the web middleware applied to any routes you need sessions for, which is what the default authentication system is using. When you apply the auth middleware without this it can't possibly resolve a user since there is no session to be authenticated against.

You need to apply the web middleware and then what ever other middleware you want: