Skip to content

Conversation

@Pijukatel
Copy link
Contributor

@Pijukatel Pijukatel commented Dec 8, 2025

  • Bump the apify-client dependency to enable log redirection.
  • Add docs.

@github-actions github-actions bot added this to the 129th sprint - Tooling team milestone Dec 8, 2025
@github-actions github-actions bot added t-tooling Issues with this label are in the ownership of the tooling team. tested Temporary label used only programatically for some analytics. labels Dec 8, 2025
@Pijukatel Pijukatel force-pushed the expose-log-redirection-and-add-docs branch from 4fa4535 to a01f980 Compare December 8, 2025 15:38
@Pijukatel Pijukatel force-pushed the expose-log-redirection-and-add-docs branch from a01f980 to 1cffc5e Compare December 8, 2025 16:02
@Pijukatel Pijukatel requested review from barjin and janbuchar December 9, 2025 13:49
@Pijukatel Pijukatel marked this pull request as ready for review December 9, 2025 13:49
Copy link
Member

@barjin barjin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @Pijukatel! I have just a few points to discuss:

await Actor.exit();
```
Each default redirect log entry will have a specific format. After the timestamp, it will contain cyan colored text that will contain the redirect information - the other Actor's name and the run ID. The rest of the log message will be printed in the same manner as the parent Actor's log is configured.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After the timestamp

The timestamp is only added by the Platform, so locally, this message will start with the colored redirect information, right?

But even if so, I don't really see a reason to change this, this is IMO too minuscule to confuse anybody too much.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rephrased

actorId: string,
input?: unknown,
options: CallOptions = {},
options: StartOptions = {},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is curious, nice catch 👀

I see that StartOptions is not larger than CallOptions, so this change might cause some type errors though. If the user was e.g. using the waitSecs parameter with start method - even though it would be likely ignored, it might start failing (on type level) now.

Idk, this is probably a fix (so not a breaking change), but IMO still something to consider

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I edited PR description to explicitly mention this change. But would you prefer to do this as separate PR with fix or is it ok to be included in this one?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, that's a good point - we probably should do it in a separate PR, so it shows in the changelog (and is easier to revert if needed).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Pijukatel Pijukatel requested a review from barjin December 10, 2025 14:47
Copy link
Member

@barjin barjin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thank you for the quick fixes 🚀

please address the type change in a different PR and feel free to merge 👍

@Pijukatel Pijukatel merged commit 244c277 into master Dec 11, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-tooling Issues with this label are in the ownership of the tooling team. tested Temporary label used only programatically for some analytics.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants