GuillaumeFalourd

The "INFINITE_LOOP_DETECTED" error you're encountering typically happens when there is a repetitive request pattern that the system detects as a loop. Given the context of your GitHub Actions workflow and the information provided, here are a few potential reasons and solutions for this issue:

Potential Causes and Solutions

Multiple Parallel Runs

Since the workflow can be triggered in parallel by multiple events, and each run uses the same VERCEL_TOKEN, it’s possible that these concurrent requests are causing Vercel to detect an infinite loop.

Solution: Add a delay or rate limiting to the Get deployment details step to prevent too many simultaneous requests. You can introduce a short sleep before making the API call:

GuillaumeFalourd

The issue seems indeed related to the system Keychain being locked on the GitHub Action runner, which is preventing the [CP] Embed Pods Frameworks step from completing. The setup_ci command is used to configure the CI environment, including setting up the necessary Keychain settings, but it needs to be combined with Fastlane's match to properly manage code signing certificates and provisioning profiles.

Understanding setup_ci and match

1. setup_ci:

• This command is designed to perform various CI-specific setup tasks. It includes unlocking the Keychain and setting up other CI-related configurations.

2. match:

GuillaumeFalourd

Problem

I have two Github accounts: oanhnn (personal) and superman (for work). I want to use both accounts on same computer (without typing password everytime, when doing git push or pull).

Solution

Use ssh keys and define host aliases in ssh config file (each alias for an account).

How to?

1. Generate ssh key pairs for accounts and add them to GitHub accounts.

GuillaumeFalourd

Kubernetes: confira os comandos mais usados

Fonte: https://medium.com/programming-to-live/kubernetes-confira-os-comandos-mais-usados-abdc17f50364

Ser desenvolvedor não é uma tarefa fácil. Lidamos, muitas vezes, com projetos gigantescos. São várias linhas de código difíceis de alterar. Basta um único erro para que a equipe se debruce sobre o teclado e comece a chorar.

Como era uma dificuldade enfrentada frequentemente, a solução foi a de colocar blocos de código em “contêineres”. Dessa forma, as modificações em determinada parte do código não afetaria a outra, o que representa mais facilidade e agilidade aos devs.

Existem diversas aplicações de implantação em contêineres, mas hoje decidi falar sobre o Kubernetes.

GuillaumeFalourd

name: Initiator

on:
  schedule:
    - cron: '0 1 * * MON-FRI' # Runs at 1:00 UTC
  repository_dispatch:

jobs:
  producer:
    if: github.event.action != 'Workflow Response'

GuillaumeFalourd

name: Create release

on:
  pull_request:
    types:
      - closed

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

GuillaumeFalourd

name: Deploy (PROD)

on:
  release:
    types:
      - published

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

GuillaumeFalourd

name: Deploy (QA)

on:
  push:
    branches:
      - qa

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

GuillaumeFalourd

name: Deploy (SANDBOX)

on:
  push:
    branches:
      - release-*

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

GuillaumeFalourd

from pytube import Youtube
link = input("Enter video URL: ")
video = Youtube(link)
stream = video.streams.get_highest_resolution()
stream.download()