Recherche avancée

Sur d’autres sites (7437)

• 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.

  


• Anomalie #2910 : Erreur 404 après redirection après message forum ds un site avec URLs arbo.

  8 janvier 2013, par Joachim SENE

  Nan, pareil ailleurs. est-ce que le .htaccess par défaut n’a pas été modifié sur http://grml.eu pr que ça marche ? J

• How to allow other site via nginx to use my content ?

  3 septembre 2020, par GG GG

  i use nginx - rtmp technique to restream the m3u8 stream via ffmpeg and then play it on the website. I have following restream m3u8 from my server, which is playable perfetly in vlc player https://hls.tvoti.com/rtl2/playlist.m3u8
But i can not play it on the website see demo. I use following code to allow website use the stream, and is it not correct ? :

  


  server {
    listen   80; 

    #root /var/www/html/; 
    #index index.php index.html index.htm;

    server_name tvoti.com; 

    location / {
    proxy_redirect off; 
        proxy_set_header X-Real-IP  $remote_addr;
        proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Host $host;
        proxy_pass http://127.0.0.1:8080;
    }

    location ~ /\.ht {
        deny all;
    }
}

server {
    listen       80;
    server_name  hls.tvoti.com;

    location / {
        add_header Cache-Control no-cache;

    set $cors_origin "https://rtllivestreamkostenlos.com";

    if ($http_origin ~* (^https?://([^/]+\.)*(tvoti|rtllivestreamkostenlos.com)\.com$)) {
            set $cors_origin "$http_origin";
        }

    add_header "X-Dbg" "$cors_origin" always;

        # Simple requests
        if ($request_method ~* "(GET|POST)") {
            add_header "Access-Control-Allow-Origin"  "$cors_origin";
        }

        # Preflighted requests
        if ($request_method = OPTIONS ) {
            add_header "Access-Control-Allow-Origin"  "$cors_origin";
            add_header "Access-Control-Allow-Methods" "GET, POST, OPTIONS, HEAD";
            add_header "Access-Control-Allow-Headers" "Authorization, Origin, X-Requested-With, Content-Type, Accept";
            return 200;
        }
        root   /etc/nginx/hls;
    }

    location /supervisor {
        proxy_pass http://127.0.0.1:9999/;
    }

    #error_page  404              /404.html;

    # redirect server error pages to the static page /50x.html
    #
    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   html;
    }

}