Skip to content

Conversation

andreasohlund
Copy link
Member

As discovered in https://github.com/Particular/ServiceControl/pull/4943/files#diff-b318f9c690fb6d2daac8156a8c023e2cb1fcb7d10caf0d4535c27aa25357f11dR62 there are scenarios where the receiving endpoint can't be detected. This change handles that edge case

@andreasohlund andreasohlund self-assigned this Apr 24, 2025
@andreasohlund
Copy link
Member Author

@johnsimons I'm a vue noob so adding you for review to confirm that ? is the way to go?

Is there a good way I can add a test for this?

@andreasohlund andreasohlund added this to the vNext milestone Apr 26, 2025
@cquirosj cquirosj self-requested a review April 27, 2025 19:23
@cquirosj
Copy link
Contributor

@andreasohlund, there is a new MessageView.Vue component under a folder named Messages2. This will eventually replace the original MessageView. In the new version, these values are already conditionally rendered:

<template v-if="state.data.receiving_endpoint">

@johnsimons
Copy link
Member

@andreasohlund this is interesting, becasue there are a few places in the UI where we use this value, and I am wondering if we need to handle this scenario more explicitly.

So we have things like the flow diagram that displays the addresses
image

We also have other diagrams that I am not 100% sure what happens there!

It may be worth doing a code search everywhere to see how this data is used and what are the ramifications if there is no data.

@andreasohlund
Copy link
Member Author

I'll take a look.

Side note:

If we merge Particular/ServiceControl#4945 the result will be that we'll always have an endpoint name (since its deducted from the FailedQ headers which is mandatory) and it will only be the host that can be missing

@andreasohlund
Copy link
Member Author

andreasohlund commented Apr 29, 2025

Discussed with @johnsimons and since this is already handled I'm closing this.

Raised the following to track renaming "Machine" to something more accurate:

@andreasohlund andreasohlund deleted the handle-missing-endpoint branch April 29, 2025 07:16
@johnsimons johnsimons removed this from the 2.0.0 milestone May 12, 2025
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

Successfully merging this pull request may close these issues.

3 participants