Fix issue with displaying Tasks that no longer have a Droplet#4469
Merged
Fix issue with displaying Tasks that no longer have a Droplet#4469
Conversation
- Although a Task must have a Droplet associated with it when it is created, these Droplets will be eventually cleaned up as the app is pushed with newer code over time. This change updates the presenter to return null when a Task's user can no longer be looked up because its droplet has been deleted. - Fixes #4467
ari-wg-gitbot
added a commit
to cloudfoundry/capi-release
that referenced
this pull request
Jul 23, 2025
Changes in cloud_controller_ng:
- Fix issue with displaying Tasks that no longer have a Droplet
PR: cloudfoundry/cloud_controller_ng#4469
Author: Tim Downey <tcdowney@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GET /v3/tasks?app_guids=<guid>fails withAn unknown error occurred#4467I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests