Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BOX info command is not always able to read the Requirement Checker section #1235

Closed
llaville opened this issue Nov 30, 2023 · 3 comments
Closed

Comments

@llaville
Copy link
Contributor

Bug report

Question Answer
Box version 4.5.1@1e10a1e
PHP version 8.3.0
Platform with version Ubuntu 22.04 LTS on WSL2 with Docker
Github Repo - none

Trying to get info on some phar artifacts raise following ErrorException Undefined array key "source"

For example, with :

Composer Unused 0.8.11

Output
$ box info composer-unused.phar
> output
API Version: 1.1.0

Built with Box: 3.16.0@adb282a

Archive Compression: None
Files Compression: None

Signature: SHA-1
Signature Hash: E11A7EE8E6670D53D3948E12BAE8392BE019BFC5

Metadata: None

Timestamp: 1701355209 (2023-11-30T14:40:09+00:00)

RequirementChecker:

In Requirement.php line 26:

 Undefined array key "source"


info [-l|--list] [-m|--mode MODE] [-d|--depth DEPTH] [--] [<phar>]

UmlWriter 3.4.0

Output
$ box info umlwriter.phar
> output
API Version: 1.1.0

Built with Box: 4.3.8@5534406

Archive Compression: None
Files Compression:
 - GZ (99.93%)
 - None (0.07%)

Signature: SHA-1
Signature Hash: B91733EBC7A4323262AD0191BD426C7833D1AA70

Metadata: None

Timestamp: 1681205957 (2023-04-11T09:39:17+00:00)

RequirementChecker:

In Requirement.php line 26:

 Undefined array key "source"


info [-l|--list] [-m|--mode MODE] [-d|--depth DEPTH] [--] [<phar>]

PS: I've noticed that box info command works when there are no Requirement Checker defined in project with box.json config file (like Phive or Composer)

Given on BOX info output

RequirementChecker: Not found.
@theofidry
Copy link
Member

This should be fixed in #1157. Unfortunately I'm on the phone so I can't confirm if it's not released or not enough of a fix.

@llaville
Copy link
Contributor Author

llaville commented Dec 2, 2023

This should be fixed in #1157.

👍

@theofidry
Copy link
Member

Should be part of 4.6.0 that has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants