Recherche avancée

Sur d’autres sites (11695)

• AWS lambda SAM deploy error - Template format error : Unresolved resource dependencies

  1er juin 2022, par mozenge

  I have am trying to deploy an aws lambda function using the SAM cli. I have some layers defined in the sam template. Testing locally using sam local start-api works quite well. The but deploying using the sam deploy --guided command throws the following error
Error: Failed to create changeset for the stack: sam-app, ex: Waiter ChangeSetCreateComplete failed: Waiter encountered a terminal failure state: For expression "Status" we matched expected path: "FAILED" Status: FAILED. Reason: Template format error: Unresolved resource dependencies [arn:aws:lambda:us-west-1:338231645678:layer:ffmpeg:1] in the Resources block of the template

  


  The SAM template is as follows

  


  AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >
  video-processor-functions

  Functions to generate gif and thumbnail from uploaded videos
  
# More info about Globals: https://github.com/awslabs/serverless-application-model/blob/master/docs/globals.rst
Globals:
  Function:
    Timeout: 3
    Tracing: Active

Resources:
  VideoProcessorFunctions:
    Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
    Properties:
      CodeUri: src/
      Handler: app.lambdaHandler
      Runtime: nodejs14.x
      # timeout in seconds - 2 minutes
      Timeout: 120
      Layers:
        - !Ref VideoProcessorDepLayer
        - !Ref arn:aws:lambda:us-west-1:338231645678:layer:ffmpeg:1
      Architectures:
        - x86_64
      Events:
        HelloWorld:
          Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
          Properties:
            Path: /hello
            Method: get

  VideoProcessorDepLayer:
    Type: AWS::Serverless::LayerVersion
    Properties:
      LayerName: mh-video-processor-dependencies
      Description: Dependencies for sam app [video-processor-functions]
      ContentUri: dependencies/
      CompatibleRuntimes:
        - nodejs14.17
      LicenseInfo: 'MIT'
      RetentionPolicy: Retain

Outputs:
  # ServerlessRestApi is an implicit API created out of Events key under Serverless::Function
  # Find out more about other implicit resources you can reference within SAM
  # https://github.com/awslabs/serverless-application-model/blob/master/docs/internals/generated_resources.rst#api
  HelloWorldApi:
    Description: "API Gateway endpoint URL for Prod stage for Hello World function"
    Value: !Sub "https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Prod/hello/"
  VideoProcessorFunctions:
    Description: "Generate GIF and Thumnail from Video"
    Value: !GetAtt VideoProcessorFunctions.Arn
  VideoProcessorFunctionsIamRole:
    Description: "Implicit IAM Role created for MH Video Processor function"
    Value: !GetAtt VideoProcessorFunctionsRole.Arn



  


  Any ideas what i'm doing wrong ?

  


• avcodec/pthread_frame : Don't update the first thread ctx before freeing

  18 mai 2022, par Andreas Rheinhardt

  avcodec/pthread_frame : Don't update the first thread ctx before freeing
  Currently, ff_frame_thread_free() uses the last worker thread
  
  to updates the first worker thread via update_context_from_thread()
  
  immediately before freeing all these worker threads. This is
  
  a remnant of the time in which the first worker was special.
  
  (E.g. the first worker shared its AVCodecInternal with the public
  
  AVCodecContext.)
  But these times are over (none of the uses of is_copy matter
  
  for ff_frame_thread_free()) ; nowadays the only thing that
  
  update_context_from_thread() does is referencing a few
  
  buffers/frames and replacing them with other references instead.
  
  These new references will then be freed immediately thereafter
  
  when the first worker thread is freed. Ensuring that the code is
  
  free of double-frees is achieved by using reference-counted structures
  
  (or in case of AVChannelLayouts : by giving each worker its own copy).
  Some archaeology :
  
  a) Updating the first worker thread from the last one used
  
  has been done since frame-threading was added in
  
  37b00b47cbeecd66bb34c5c7c534d016d6e8da24.
  
  b) The precursor to ff_mpv_common_end() checked for is_copy
  
  before freeing pictures (i.e. it only freed them for the first
  
  worker thread).
  
  c) Commits c2dfb1e37cc72bf144545c4410a4621cbff5c4b1 and
  
  e33811bd2686411233cb0eb4a4ee45eb99d7e736 modified the
  
  update_thread_context function of the H.264 decoder
  
  so that it could fail before calling ff_mpeg_update_thread_context().
  
  d) This led to a double free/an assert violation with a H.264
  
  sample for which ff_mpeg_update_thread_context() is not reached
  
  for the final update_context_from_thread(). Commit
  
  a6e4796fbf0aa9b13451a8ef917ecc4e80d1d272 added code to fix this
  
  sample.
  
  e) This issue was fixed (even with the last mentioned commit reverted)
  
  when the H.264 decoder was deMpegEncContextized in commit
  
  b7fe35c9e50e1701274364adf7280bf4a02b092b (merging commit
  
  2c541554076cc8a72e7145d4da30389ca763f32f).
  
  f) mpegvideo.c stopped using is_copy when it was switched to refcounted
  
  frames in 759001c534287a96dc96d1e274665feb7059145d.
  
  g) 1f4cf92cfbd3accbae582ac63126ed5570ddfd37 removed the init_thread_copy
  
  callbacks ; now no FFCodec.close callback checks for is_copy at all
  
  any more.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/pthread_frame.c

• doc : Update to Doxygen 1.7.6.1

  18 novembre 2019, par NotTsunami

  doc : Update to Doxygen 1.7.6.1
  This will bring our doxyfile closer to the modern world and clean up some warnings in the doxygen output during a regular build. I believe it is pretty fair to use 1.7.6.1 given it released in 2011, with the 1.7.x branch a year prior. The current branch is 1.8, which released 2012, but I believe 1.7.6.1 is sufficient.
  Updated by running doxygen -u doc/Doxygen.in with Doxygen 1.7.6.1. The only manual change was adding 'Free Lossless Audio Codec' to PROJECT_BRIEF.
  

  • [DH] doc/Doxyfile.in