Resolved Latest Update to Git Extension is Broken

[VizyDiego]

Server operating system version

Ubuntu 18.04 x86_64

Plesk version and microupdate number

Plesk Obsidian 18.0.49.2

Hi, I noticed that Yesterday (March 27th) Plesk released a new version of the Git Extension. This release has made it so I'm unable to change the settings of an existing repo, and is also not allowing me to create new ones either. Does anyone know what I can do to revert to an old version, or if they can update this?

Here is the error I get:
Server error: Argument 7 passed to Symfony\Component\Validator\Constraints\Choice::__construct() must be of the type int or null, string given, called in /opt/psa/admin/plib/modules/git/library/DTO/API/AbstractRepositoryRequest.php on line 68

Git Extension Version: 2.4.5-442

 

[Ryan Soeder]

Same issue, same error, same Git Extension Version. Screenshot attached of error message whenever I try to apply git changes.

 

[Crim]

Same error here.

 

[babanooki]

Same error here, too. Same version.

 

[developer044]

Same Issue with me.

 

[Peter Debik]

A product issue has been confirmed that can be tracked under ID [EXTGIT-315] and will be fixed in a future update. No ETA yet.

 

[landrei]

I can confirm that after update git extension is hidden from all domains.
I managed to reset git extension db but icon didn't show in domain dashboard (service plan allow git management), and using command line I could setup a remote git for a domain and after that icon is back in domain dashboard but just for that domain only.
Anyway, now I can't pull updates from that repo.

Plesk Obsidian
Version 18.0.51

[2023-03-29 09:33:38.499] 505018:6423dbc279d96 ERR [extension/git] Symfony\Component\Validator\Constraints\Choice::__construct(): Argument #7 ($max) must be of type ?int, string given, called in /opt/psa/admin/plib/modules/git/library/DTO/API/AbstractRepositoryRequest.php on line 68

 

[landrei]

Also, probably related to git issues, "Deployment" options from Laravel Toolkit extension are hidden and every time when I open Laravel Toolkit I get this error in panel.log

ERR [panel] Table is not detected

 

[Peter Debik]

@landrei Could you please open a separate thread for the separate issue?

 

[Peter Debik]

Regarding the initially reported issue of this thread a fix has already been prepared and will be published shortly.

 

[landrei]

I can confirm, that for domains that had a git repo setup before, things seems to work after today extension update.
But, I just created a new domain, new subscription, I selected Blank website type. Then I decided to setup git after domain was added to Plesk and Git extension icon is not available in domain dashboard (service plan allow git management)

 

[landrei]

After more tests you can set remote git repo with Laravel Toolkit and then Git extension will be active in domain dashboard.
Still you can't use Git Extension directly for some unknown reason.

Also if you try to setup git repo with Plesk commands that works but Laravel Toolkit won't see this and deployment tab will not be available.

Error when git repo was set with Git Extension not with Laravel Toolkit
[2023-03-29 11:40:19.408] 526676:6423f9725d299 ERR [panel] Table is not detected

 

[jasonw]

I can confirm after update its still coming up with same error ( i have 3 servers, all the same

 

[Maarten]

An update of the GIT extension was released today:

2.4.6 (29 March 2023)​

• [-] Fixed deployment of a new private repository. (EXTGIT-315

 

[landrei]

Git
Version 2.4.6-445

My last two comments are after this update. #11 #12

 

[Peter Debik]

@landrei Could you please open a separate thread for the separate issue? Your description on Laravel Toolkit "ERR [panel] Table is not detected" does not match the case described in this thread "Git Extension".

 

[Peter Debik]

@jasonw Did you update to 2.4.6 and was the issue solved by that?

 

[landrei]

@landrei Could you please open a separate thread for the separate issue? Your description on Laravel Toolkit "ERR [panel] Table is not detected" does not match the case described in this thread "Git Extension".

I will, thanks -- please see post #11

 

[babanooki]

Updating to 2.4.6 worked for me. Thank you for the quick response, Peter.

 

[developer044]

Updating to 2.4.6 worked for me. Thank you for the quick response, Peter.