-
Notifications
You must be signed in to change notification settings - Fork 278
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
Fix outdated & upgrade commands #312
Conversation
4ff363c
to
b5a8553
Compare
I force pushed some minor changes 14 hours ago, but the Jenkins/pr-merge check hasn't completed. How long does it normally take? Might something have gone wrong? 14 hours seems a long time, but maybe it's normal… |
The most recent Jenkins/pr-merge build failed, but previous builds succeeded. The logs say that the Commandant build failed. The only differences in the most recent force push were in Supposedly, there's more info in the following file, but I don't know how to see the file:
|
Whenever I build, changes are made to spacing in various files that I haven't edited (presumably because the spacing violates various formatting rules). Can I commit those spacing changes in this PR, so people don't keep getting files changed on them? Or should I create a new issue & PR? There's also a bug in the
Which do you prefer? |
The file spacing is no longer changed by the build, presumably because of the change from |
Hi @phatblat, glad you’re recovering. Sorry to bother you, but is there anything that I (or anyone else) must do to get the I pushed commits 2 days ago, and it still hasn’t run… |
@rgoldberg sorry for the delay getting to this PR. The Jenkins server these checks run on is a mac mini I have hosted at MacStadium. It's been offline for a while due to an OS upgrade that failed. The CI just runs several of the scripts checked into the project, so as long as these are working for you and me, we can ignore Jenkins for now. I will take a closer look at these changes and test them out myself tonight, but at a quick glance, I think this is a great idea. This tool has been using a private CommerceKit API to figure out which apps have pending updates but that API stopped returning anything some time back. I've dug around in a debugger several times looking for where this functionality moved to but haven't been successful. Thanks for the PR! I will get back with any suggestions this week. |
Thanks, @phatblat. Glad you're recovering. No problem about delay. Take whatever time you need to stay healthy, and to ensure the PR is good. I haven't looked throughout mas to see whether there are other commands that can be similarly fixed. I tried to write tests, but got cryptic errors, so I decided to wait on tests until I communicated with you. |
Sorry about the changing format. I'd rather have that as a separate script but it was easy to add the --format flag to swiftlint and didn't think about the ramifications. On the "InfoCommandSpec displays app details" test failures, I think a deterministic date format (option 2) would be ideal I'm curious, what locale setting do you have to get that format? That "yyyy-MM-dd" format (ISO-8601 minus the time) is perfect for the new format. You can find this formatter in AppInfoFormatter. |
No problem about formatting. I just didn't want to cause build or git history issues by changing things without asking. I thought that maybe I had missed some setup instructions that would have prevented the file reformatting. I set all 4 date formats in System Preferences > Language & Region > Advanced… > Dates to "yyyy-MM-dd" a long time ago. I'll have to read about the Apple Should I open a new issue & PR for the "InfoCommandSpec displays app details" date format change, or just include it in this PR in a separate commit? |
Yes, please create a separate PR for this date formatting change. That way it will be easier to track to see which version it changed in. |
I'll create a new issue & PR for the date format change after we finish with the current PR, as I don't want to have to manage multiple branches. The second PR will be simple, so easy to finish after this one. |
I managed to get the CI server back online tonight but builds are failing due to some issues I still need to clean up. So ignore the failing check for now. |
Will do. Please let me know whenever I need to do anything to improve / finish the PR. |
Wow, this works better than the App Store's "Updates" section! The App Store app doesn't show any of the 5 pending updates.
Looked into the apps which weren't found:
There might be a way to map apps like Deliveries that release updates as a new app to the one, but these are technically not an upgrade so the only thing we might be able to do is to have a more informative warning message. The macOS installers have a weird versioning scheme which looks like it doesn't match the version reported by the iTunes Search API. This is a very minor issue as these are not usually kept around. |
Weird, both Grammarly and DaisyDisk are newer versions on my system than the app store reports.
I installed them from the app store some time ago. Not sure how this can happen unless installing beta versions direct from the developer (which these aren't). I'll keep digging on the reason for this. |
Running the
Afterwards
Is there a way to exclude the items that generate a warning from the |
Maybe a version was released to the store, but was later retracted… |
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all your great work on this! 💯
@phatblat No problem. Glad to help. Thanks for maintaining / working on mas. All but one issue that I referenced in the commit message are still open, so someone should go through the list and close the applicable issues. Some issues will definitely be fixed by this PR, some other issues might be fixed, but I'm not 100% sure as I didn't have the time to verify each. |
Thanks for reminding me. Once I get #327 completed I'll ask on each issue for confirmation. |
The issues listed after |
Fix outdated & upgrade commands.
Resolves #111 #245 #248 #252 #282 #306
Possibly #76 #92 #247 #249 #290