Recherche avancée

Sur d’autres sites (9590)

• Why ffmpeg launched on a google cloud function can throw "Error : Output stream error : Maximum call stack size exceeded" ?

  15 décembre 2020, par Stepan Shilin

  I'm trying to process video files with ffmpeg running on google cloud functions. Video files are downloaded from a google file storage, processed in stream by fluent-ffmpeg and streamed to a new google storage file. It works on smaller files but throws an "Output stream error : Maximum call stack size exceeded" on larger files.

  



  I tried running the code on a normal pc, and I haven't encountered this error, even with larger files.

  



  These are the parameters I deploy the function with

  



  gcloud functions deploy $FUNCTION_NAME --runtime nodejs8 --trigger-http --timeout=180 --memory 256


  



  This is the code that processes video

  



  function cutVideo({videoUrl, startTime, duration, dist}) {
    return ffmpeg(videoUrl)
    .outputOptions('-movflags frag_keyframe+empty_moov')
    .videoCodec('copy')
    .audioCodec('copy')
    .format('mp4')
    .setStartTime(startTime)
    .setDuration(duration);
}

const sectionStream = cutVideo({
    videoUrl,
    startTime,
    duration,
    dist: tempFilePath,
});

const outputStream = bucket.file(sectionPath)
.createWriteStream({
    metadata: {
        contentType: config.contentType,
    },
    public: true,
});


  



  Actual error stack looks like this

  



    Error: Output stream error: Maximum call stack size exceeded&#xA;                                                                  at Pumpify.<anonymous> (/srv/node_modules/fluent-ffmpeg/lib/processor.js:498:34)&#xA;                                                                  at emitOne (events.js:121:20)&#xA;                                                                  at Pumpify.emit (events.js:211:7)&#xA;                                                                  at Pumpify.Duplexify._destroy (/srv/node_modules/duplexify/index.js:191:15)&#xA;                                                                  at /srv/node_modules/duplexify/index.js:182:10&#xA;                                                                  at _combinedTickCallback (internal/process/next_tick.js:132:7)&#xA;                                                                  at process._tickDomainCallback (internal/process/next_tick.js:219:9)&#xA;  RangeError: Maximum call stack size exceeded&#xA;                                                                  at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:28:31)&#xA;                                                                  at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)&#xA;                                                                  at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)&#xA;                                                                  at value.map.v (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:32)&#xA;                                                                  at Array.map (<anonymous>)&#xA;                                                                  at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:23)&#xA;                                                                  at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)&#xA;                                                                  at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)&#xA;                                                                  at value.map.v (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:32)&#xA;                                                                  at Array.map (<anonymous>)&#xA;</anonymous></anonymous></anonymous>

  



  What could cause this error on a google cloud function ?

  


• Anomalie #3592 (En cours) : Robots.txt.html et tests de compatibilité mobile de Google

  25 novembre 2019, par Ben .

  Je rouvre pour (re)discuter du sujet je viens d’ajouter 2 captures d’écrans avec l’état actuel de contrib .

  Faut il ajouter 2 lignes au robots.txt actuel ?

  Allow :    /local/cache-gd2/
  Allow :    /local/cache-vignettes/
  

  https://git.spip.net/SPIP/dist/src/branch/master/robots.txt.html

• Leading Google Analytics alternative, Matomo, parodies Christopher Nolan blockbuster ahead of the UA sunset

  4 juillet 2023, par Erin — Press Releases

  Wellington, New Zealand, 4 July 2023 : In the world of online data, Google Analytics has long reigned supreme. Its dominance has been unquestioned, leaving website owners with little choice but to rely on the tech giant for their data insights. However, a new dawn in web analytics is upon us, and Matomo, the leading alternative to Google Analytics, is seizing a unique opportunity to position itself as the go-to provider. In a bold move, Matomo has launched a parody trailer, “Googleheimer,” humorously taking a satirical swipe at Google in the style of the upcoming Oppenheimer biopic by Christopher Nolan.

  Capitalising on a time-bound decision

  With an important decision looming for marketers and web specialists who need to switch analytics providers by July 1st, Matomo has found the perfect window to capture their attention.

  The urgency of the situation, combined with the high intent to switch providers, sets the stage for Matomo to establish itself as the leading alternative analytics platform of choice.

  Matomo’s parody trailer addresses the frustrations of GA4 head-on by highlighting the issues and the uncertainties caused by the sunset of Universal Analytics in humorous satire with lines such as :

  “But we’re keeping everyone’s data, right ? Right ?? …RIGHT ?!”

  Riding on the coat tails of this summer’s anticipated blockbuster from Christopher Nolan, Matomo openly points at the downsides of GA4, and reflects many frustrated marketers pain points in an entertaining way. Beneath the comedic and satirical tone lies the message that users have choices, and no longer need to surrender to the behemoth incumbent.

  Matomo was founded to challenge the status quo and provide a solution for those who believe in privacy and in ethical analytics, and who prefer that their customer data not be concentrated in the hands of just a few corporations.

  Watch the full trailer here. 


  About Matomo
  

  Matomo is a world-leading open-source privacy-friendly ethical web analytics platform, trusted by over 1.4 million websites in 190 countries and translated into over 50 languages. Matomo helps businesses and organisations track and optimise their online presence allowing users to easily collect, analyse, and act on their website and marketing data to gain a deeper understanding of their visitors and drive conversions and revenue. Matomo’s vision is to create, as a community, the leading open digital analytics platform that gives every user complete control of their data.

  Visit matomo.org for more information.




  More on Google Analytics changes



  A new dawn in web analytics is upon us, and Matomo – the leading alternative to Google Analytics – is here for it. After 20 years, Google is blowing up Universal Analytics (or GA3) – and taking your data with it. Inspired by Christopher Nolan’s upcoming biopic about physicist J. Robert Oppenheimer and the making of his atomic bomb (also known as “The Manhattan Project”), this parody trailer openly points to Google and draws the comparison in humorous satire. GA4 comes with a new set of metrics, setups and reports that change how you analyse your data.