question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Annotations from composite actions are not correctly created

See original GitHub issue

Describe the bug Only a single annotation gets created in composite actions. Every single annotation (error, warning, notice) with the exception of the last one gets ignored

To Reproduce

Steps to reproduce the behavior:

  1. Create a simple composite actions that generates annotations
name: 'Annotation example'
description: Test annotations
runs:
  using: "composite"
  steps:
    - run: echo Hello there once!
      shell: bash
    - name: Testing the Error Workflow Command
      run: echo "::error::Testing error"
      shell: bash
    - run: echo Hello there
      shell: bash
    - name: Testing the Error Workflow Command
      run: echo "::error::Testing error"
      shell: bash
    - name: Testing the Error Workflow Command
      run: echo "::warning::Testing warning"
      shell: bash
    - name: Testing the Error Workflow Command
      run: echo "::notice::Testing notice"
      shell: bash
  1. Run the workflow from another repository (or locally)

Expected behavior Every single annotation gets created.

Runner Version and Platform

Version of your runner? 2.288.1

Tested using Linux but probably busted for everything

What’s not working?

Here is an example run: https://github.com/konradpabjan/Testing2/actions/runs/1958916121

Currently at most only one gets created and it’s always the last one

image

Job Log Output

☝️ Only the notice annotations is created while the other annotations do not show up. In the logs though the behavior is expected

image

Runner and Worker’s Diagnostic Logs

Not provided since I used hosted for testing, but it should be easy to get with the repro

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:4
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
thboopcommented, Sep 9, 2022
0reactions
jww3commented, Jun 26, 2023

All PRs have been merged. I’ve verified the original bug as reported is now fixed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to use default github actions env vars for composite ...
I just did a quick test with a composite action and it did output all the expected env vars (with run: env )....
Read more >
GitHub Actions: Reusability, DRY Principle, Debugging ...
Composite actions are useful for combining together common tasks or logic that can be reused in different workflows. To create an action, you ......
Read more >
Composite Actions vs Reusable Workflows
With GitHub offering both Composite Actions and Reusable ... Composite Actions cannot use secrets, not from the workflow nor as parameter.
Read more >
Advanced PDF print settings, Adobe Acrobat
Select any of the panels on the left side of the Advanced Print Setup dialog box, and set options for either composite or...
Read more >
714-Amendments, Applicant's Action
(1) A marked-up copy of any amended drawing figure, including annotations indicating the changes made, may be included. The marked-up copy must be...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found