Recherche avancée

Sur d’autres sites (11366)

• Heroku build failed & state changed from crashed to down

  5 décembre 2020, par Cal9233

  2020-12-05T08:10:45.000000+00:00 app[api]: Build started by user calvin.m71@hotmail.com
2020-12-05T08:11:38.587758+00:00 app[api]: Deploy 4fca112e by user calvin.m71@hotmail.com
2020-12-05T08:11:38.587758+00:00 app[api]: Release v6 created by user calvin.m71@hotmail.com
2020-12-05T08:11:38.635964+00:00 heroku[web.1]: State changed from crashed to down
2020-12-05T08:11:41.000000+00:00 app[api]: Build succeeded
2020-12-05T08:32:12.000000+00:00 app[api]: Build started by user calvin.m71@hotmail.com
2020-12-05T08:32:50.304709+00:00 app[api]: Release v7 created by user calvin.m71@hotmail.com
2020-12-05T08:32:50.304709+00:00 app[api]: Deploy 4fca112e by user calvin.m71@hotmail.com
2020-12-05T08:32:52.000000+00:00 app[api]: Build succeeded


  


  Before it was that there was no ffmpeg buildpack on heroku, I added it with
https://elements.heroku.com/buildpacks/jonathanong/heroku-buildpack-ffmpeg-latest

  


  But now I just get state changed and see no errors. Any help would be greatly appreciated !

  


• Realtime removal of carriage return in shell

  1er mai 2013, par Seth

  For context, I'm attempting to create a shell script that simplifies the realtime console output of ffmpeg, only displaying the current frame being encoded. My end goal is to use this information in some sort of progress indicator for batch processing.

  For those unfamiliar with ffmpeg's output, it outputs encoded video information to stdout and console information to stderr. Also, when it actually gets to displaying encode information, it uses carriage returns to keep the console screen from filling up. This makes it impossible to simply use grep and awk to capture the appropriate line and frame information.

  The first thing I've tried is replacing the carriage returns using tr :

  $ ffmpeg -i "ScreeningSchedule-1.mov" -y "test.mp4" 2>&1 | tr '\r' '\n'

  This works in that it displays realtime output to the console. However, if I then pipe that information to grep or awk or anything else, tr's output is buffered and is no longer realtime. For example : $ ffmpeg -i "ScreeningSchedule-1.mov" -y "test.mp4" 2>&1 | tr '\r' '\n'>log.txt results in a file that is immediately filled with some information, then 5-10 secs later, more lines get dropped into the log file.

  At first I thought sed would be great for this : $ # ffmpeg -i "ScreeningSchedule-1.mov" -y "test.mp4" 2>&1 | sed 's/\\r/\\n/', but it gets to the line with all the carriage returns and waits until the processing has finished before it attempts to do anything. I assume this is because sed works on a line-by-line basis and needs the whole line to have completed before it does anything else, and then it doesn't replace the carriage returns anyway. I've tried various different regex's for the carriage return and new line, and have yet to find a solution that replaces the carriage return. I'm running OSX 10.6.8, so I am using BSD sed, which might account for that.

  I have also attempted to write the information to a log file and use tail -f to read it back, but I still run into the issue of replacing carriage returns in realtime.

  I have seen that there are solutions for this in python and perl, however, I'm reluctant to go that route immediately. First, I don't know python or perl. Second, I have a completely functional batch processing shell application that I would need to either port or figure out how to integrate with python/perl. Probably not hard, but not what I want to get into unless I absolutely have to. So I'm looking for a shell solution, preferably bash, but any of the OSX shells would be fine.

  And if what I want is simply not doable, well I guess I'll cross that bridge when I get there.

• Révision 22875 : Déplantage de la balise #RANG quand on a déclaré autre chose qu’un simple champ p...

  4 mars 2016, par rastapopoulos@spip.org

  On garde exactement le même fonctionnement qu’avant avec un "AS titre_rang" rajouté. Mais on fait deux tests au lieu d’un seul :
  - d’abord on cherche le titre en se disant que "lang" est défini AVANT
  - et si on ne trouve pas, là on prend depuis le début
  Mais dans les deux cas, vu que c’est séparé en deux, et qu’on cherche "lang" explicitement et pas une virgule toute seule : on peut donc prendre tout caractère pour le titre, y compris les virgules qu’il y aurait dans des fonctions.

  Cela gère donc bien tous les cas, enfin de toute façon plus de cas qu’avant.