Recherche avancée

Sur d’autres sites (4534)

• How to debug GitHub Action failure

  9 décembre 2022, par Meltemi

  Just yesterday a stable GitHub Action (CI) started failing rather cryptically and I've run out of tools to debug it.

  


  All I can think of is our BUNDLE_ACCESS_TOKEN went bad somehow but I didn't set that up. It's an Action secret under Repository Secrets that are not visible in GitHub UI. How can I test to see if it's valid ?

  


  Or maybe it's something else ?!? "Bad credentials" is vague...

  


  Here's the meat of the action we're trying to run :

  


  #my_tests.yml
jobs:
  my-test:
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:13.4
        env:
          POSTGRES_USERNAME: postgres
          POSTGRES_PASSWORD: postgres
          POSTGRES_DB: myapp_test
        ports:
          - 5432:5432
        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
    env:
      RAILS_ENV: test
      POSTGRES_HOST: localhost
      POSTGRES_USERNAME: pg
      POSTGRES_PASSWORD: pg
      GITHUB_TOKEN: ${{ secrets.BUNDLE_ACCESS_TOKEN }}
      BUNDLE_GITHUB__COM: x-access-token:${{ secrets.BUNDLE_ACCESS_TOKEN }}
      CUCUMBER_FORMAT: progress
    steps:
      - uses: actions/checkout@v2
      - uses: FedericoCarboni/setup-ffmpeg@v1
      ...


  


  And with debug turned on here's the Failure (line 20) from GitHub Actions :

  


  Run FedericoCarboni/setup-ffmpeg@v1

1 ------- ##[debug]Evaluating condition for step: 'Run FedericoCarboni/setup-ffmpeg@v1'
2 ##[debug]Evaluating: success()
3 ##[debug]Evaluating success:
4 ##[debug]=> true
5 ##[debug]Result: true
6 ##[debug]Starting: Run FedericoCarboni/setup-ffmpeg@v1
7 ##[debug]Loading inputs
8 ##[debug]Loading env
9 Run FedericoCarboni/setup-ffmpeg@v1
10   with:
11   env:
12     RAILS_ENV: test
13     POSTGRES_HOST: localhost
14     POSTGRES_USERNAME: pg
15     POSTGRES_PASSWORD: pg
16     GITHUB_TOKEN: ***
17     BUNDLE_GITHUB__COM: x-access-token:***
19     CUCUMBER_FORMAT: progress
20 Error: Bad credentials
21 ##[debug]Node Action run completed with exit code 1
22 ##[debug]Finishing: Run FedericoCarboni/setup-ffmpeg@v1


  


  Thanks for any help.

  


• Revision 6919 : Gros changement... On change le pipeline diogene_champs_sup en ...

  22 août 2012, par kent1 — Log

  Gros changement...
  On change le pipeline diogene_champs_sup en diogene_objets
  Les champs_sup antérieurs $fluxarticle ?truc ? deviennent maintenant $fluxarticle ?champs_sup ?truc ?
  On fait cela pour gérer d’autres propriétés spécifiques par objet comme :
   $fluxpage ?type_orig ? = ’article’ ; => indique que le type d’origine est article ;
   $fluxpage ?diogene_max ? = 1 ; => indique que l’on ne peut avoir qu’un seul diogène de ce type ;
   $fluxpage ?ss_rubrique ? = true ; => indique que ce type de diogène est sans rubrique, ne peut correspondre à 1 secteur ;
  Passage en version 1.2.0

• ios play HLS - only lowest bitrate available

  15 janvier 2016, par user2928842

  i’m trying to play HLS streamed by IIS in different bitrates on ipad (ios 6), encoded with ffmpeg.
  i can see that only the lowest bitrate (600k) is being played by the native player : to play it i’m just opening the main index file (.m3u8) on Safari.

  is there a way to get some logs from the player to understand why this happens ?
  tried with the Safari Developer tools but didn’t get to much info from it

  thanks