Sur d’autres sites (13543)

• Piwik 2.1 — Massive Performance and Reliability Improvements

  4 mars 2014, par Benaka M. — Community, Development

  We are very excited to announce the immediate availability of Piwik v2.1.0 !

  • Download Link
  • How to update Piwik ?
  • List of all tickets closed : Changelog

  Piwik 2.1 is the first release after our 2.0 release and it reflects the new direction Piwik is moving in : better performance, more reliability and a better overall open platform ! We also released more plugins on the marketplace as well as helped developers build exciting new plugins for Piwik.

  This 2.1.0 release contains several performance and reliability improvements to the archiving process and to the new device detection process introduced in Piwik 2.0. It also includes a new email report format (CSV), a new marketplace plugin and overall more than 80 improvements (source).

  Massive Performance Improvements to Archiving

  The biggest improvement this release brings to Piwik are the various performance improvements made to the Archiving Process. These improvements include the following :

  • The amount of memory used has been reduced in some cases by 80% or more ! What used to require 8GB of memory will now only require 1GB. Piwik engineers analysed Profiler XHProf reports of Piwik under high load and implemented several improvements to archiving.
  • The cron script you can setup to automatically process your reports will now create new processes to perform asynchronous archiving instead issuing CURL http requests. This change results in increases to the performance and reliability of the Archiving Process.

  Bug Fixes and Performance Improvements to Device Detection

  In Piwik 1.12 we introduced a new device detection feature that could detect much more information than what we used before. Piwik 2.1 includes several bug fixes and improvements to this feature (such as detecting dozens of new devices, brands and models for smartphones, tablets and other devices). To use this feature, go to “Settings” then “Plugins” then activate the DevicesDetection plugin.

  New Default MySQL Database Type (InnoDB)

  This change doesn’t affect our existing Piwik users, but it does reflect our commitment to performance and reliability. We’ve changed the default MySQL database type to be InnoDB instead of Myisam. This will allow new users to immediately gain the benefits in reliability offered by InnoDB.

  New Marketplace Plugin – HTTP Authentication

  We’re releasing a new plugin on the marketplace that will allow you to use the HTTP authentication services provided by your webserver. Learn more about this plugin on the marketplace.

  New Email Format for Scheduled Reports

  The last big change in this release is a new email report format. You can now get your email reports as CSV files as well as HTML and PDF reports.

  Other Improvements

  In addition to performance improvements and new plugins, this release contains a few other smaller improvements described below.

  Changing segments in the Embedded Dashboard

  The embedded dashboard is the powerful feature that lets you include the Piwik Dashboard without the top menu and Piwik branding, directly within your application !

  This dashboard will now include the segment selector allowing you to change the current segment and create new segments, just as you would in the normal dashboard view :

  

  Multiple Super Users

  It’s now possible for your Piwik to have more than one Super User and for Super Users to have aliases :

  

  Learn more in the User guide : Managing Super Users in Piwik.

  Smart App Banners for our Mobile Apps

  Finally, in accord with our commitment to providing great User Experience, we’ve added a smart banner to Piwik so users that view Piwik from a mobile device will be informed of our amazing (and free !) mobile apps (for both iOS and Android).

  Participate in Piwik

  Are you a talented developer or an experienced User Interface designer ? If you have some free time and if you want to contribute to one of the most awesome open source projects around, please get in touch with the Piwik team, or read this page to learn more ?

  Summary

  For the full list of changes in Piwik 2.1 check out the Changelog.

  Thank you to the core developers, all the beta testers and users, our official supporters, the translators & everyone who reported bugs or feature requests. Also thank you to the software we use, and the libraries we use.

  Many of the improvements in this release come from the efforts of Piwik PRO experts. If you are looking for help to make the most of your analytics data, contact Piwik PRO. Learn more about us here.

  If you like what you read, please tell your friends and colleagues or write on your website, blog, forums, stackoverflow, etc.

  Enjoy !

• Piwik 2.1 — Massive Performance and Reliability Improvements

  4 mars 2014, par Benaka M. — Community, Development

  We are very excited to announce the immediate availability of Piwik v2.1.0 !

  • Download Link
  • How to update Piwik ?
  • List of all tickets closed : Changelog

  Piwik 2.1 is the first release after our 2.0 release and it reflects the new direction Piwik is moving in : better performance, more reliability and a better overall open platform ! We also released more plugins on the marketplace as well as helped developers build exciting new plugins for Piwik.

  This 2.1.0 release contains several performance and reliability improvements to the archiving process and to the new device detection process introduced in Piwik 2.0. It also includes a new email report format (CSV), a new marketplace plugin and overall more than 80 improvements (source).

  Massive Performance Improvements to Archiving

  The biggest improvement this release brings to Piwik are the various performance improvements made to the Archiving Process. These improvements include the following :

  • The amount of memory used has been reduced in some cases by 80% or more ! What used to require 8GB of memory will now only require 1GB. Piwik engineers analysed Profiler XHProf reports of Piwik under high load and implemented several improvements to archiving.
  • The cron script you can setup to automatically process your reports will now create new processes to perform asynchronous archiving instead issuing CURL http requests. This change results in increases to the performance and reliability of the Archiving Process.

  Bug Fixes and Performance Improvements to Device Detection

  In Piwik 1.12 we introduced a new device detection feature that could detect much more information than what we used before. Piwik 2.1 includes several bug fixes and improvements to this feature (such as detecting dozens of new devices, brands and models for smartphones, tablets and other devices). To use this feature, go to “Settings” then “Plugins” then activate the DevicesDetection plugin.

  New Default MySQL Database Type (InnoDB)

  This change doesn’t affect our existing Piwik users, but it does reflect our commitment to performance and reliability. We’ve changed the default MySQL database type to be InnoDB instead of Myisam. This will allow new users to immediately gain the benefits in reliability offered by InnoDB.

  New Marketplace Plugin – HTTP Authentication

  We’re releasing a new plugin on the marketplace that will allow you to use the HTTP authentication services provided by your webserver. Learn more about this plugin on the marketplace.

  New Email Format for Scheduled Reports

  The last big change in this release is a new email report format. You can now get your email reports as CSV files as well as HTML and PDF reports.

  Other Improvements

  In addition to performance improvements and new plugins, this release contains a few other smaller improvements described below.

  Changing segments in the Embedded Dashboard

  The embedded dashboard is the powerful feature that lets you include the Piwik Dashboard without the top menu and Piwik branding, directly within your application !

  This dashboard will now include the segment selector allowing you to change the current segment and create new segments, just as you would in the normal dashboard view :

  

  Multiple Super Users

  It’s now possible for your Piwik to have more than one Super User and for Super Users to have aliases :

  

  Learn more in the User guide : Managing Super Users in Piwik.

  Smart App Banners for our Mobile Apps

  Finally, in accord with our commitment to providing great User Experience, we’ve added a smart banner to Piwik so users that view Piwik from a mobile device will be informed of our amazing (and free !) mobile apps (for both iOS and Android).

  Participate in Piwik

  Are you a talented developer or an experienced User Interface designer ? If you have some free time and if you want to contribute to one of the most awesome open source projects around, please get in touch with the Piwik team, or read this page to learn more ?

  Summary

  For the full list of changes in Piwik 2.1 check out the Changelog.

  Thank you to the core developers, all the beta testers and users, our official supporters, the translators & everyone who reported bugs or feature requests. Also thank you to the software we use, and the libraries we use.

  Many of the improvements in this release come from the efforts of Piwik PRO experts. If you are looking for help to make the most of your analytics data, contact Piwik PRO. Learn more about us here.

  If you like what you read, please tell your friends and colleagues or write on your website, blog, forums, stackoverflow, etc.

  Enjoy !

• Specifying FFMPEG in the requirements section of 'buildozer.spec' causing [libavformat/network.o] Error 1

  18 juillet 2022, par GJ78

  My question relates to how to mitigate an ffmpeg requirement listed in a buildozer.spec that is causing compile errors using buildozer.

  



  GOAL :

  



  Using buildozer to ensure FFMPEG can be embedded within a small Kivy app so i can utilise youtube_dl functionality on my android phone.

  



  THE ISSUE :
Specifying FFMPEG in the requirements section of 'buildozer.spec' causes the following error message :
  
common.mak:60 : recipe for target 'libavformat/network.o' failed
  
make : [libavformat/network.o] Error 1
  
make : Waiting for unfinished jobs...

  



  What have I done to resolve myself :
  
1. Ensured LOG LEVEL 2 is specified.

  



  


  2. Upgraded cython from Version 21 to 27. Then downgraded to 25, then 21 then 20 to see if this resolved anything. It didn't.

  


  3. In BUILDOZER.SPEC, switched between Android NDK crystax-ndk-10.3.2 and android-ndk-r16b. (Note have reverted back to Crystax 10.3.2) in my NDK PATH.

  


  4. In BUILDOZER.SPEC, changed android.api from 19 to 15 (just to see if this has any positive effects).

  


  5. executed : rm -Rf .buildozer between each compiling attempt.

  


  6. Part extract of Buildozer.log :

     



     In file included from libavformat/dump.c:37:0 :
     
libavformat/avformat.h:893:21 : note : declared here
     
 AVCodecContext codec ;
 ^
     
CC libavformat/format.o
     
CC libavformat/golomb_tab.o
     
CC libavformat/h264dec.o
     
CC libavformat/hevc.o
     
CC libavformat/http.o
     
CC libavformat/httpauth.o
     
CC libavformat/id3v1.o
     
CC libavformat/id3v2.o
     
CC libavformat/img2.o
     
CC libavformat/isom.o
     
CC libavformat/log2_tab.o
     
CC libavformat/m4vdec.o
     
CC libavformat/metadata.o
CC libavformat/mov_chan.o
     
CC libavformat/mov.o
     
CC libavformat/movenc.o
     
CC libavformat/movenccenc.o
     
CC libavformat/movenchint.o
     
CC libavformat/mpegvideodec.o
     
CC libavformat/mux.o
     
CC libavformat/network.o
     
In file included from libavformat/network.h:29:0,
     
 from libavformat/network.c:22 :
     
libavformat/os_support.h:67:32 : error : expected declaration specifiers or '...' before '(' token
     
 # define lseek(f,p,w) lseek64((f), (p), (w))
     
 ^
libavformat/os_support.h:67:37 : error : expected declaration specifiers or '...' before '(' token
     
 # define lseek(f,p,w) lseek64((f), (p), (w))
     
 ^
libavformat/os_support.h:67:42 : error : expected declaration specifiers or '...' before '(' token
     
 # define lseek(f,p,w) lseek64((f), (p), (w))
     
 ^
common.mak:60 : recipe for target 'libavformat/network.o' failed
     
make : [libavformat/network.o] Error 1
     
make : * Waiting for unfinished jobs....

  


  7. Part extract of Buildozer.spec

     



     (str) Title of your application

     



     title = myapplication

     



     (str) Package name

     



     package.name = myapp

     



     (str) Package domain (needed for android/ios packaging)

     



     package.domain = org.test

     



     (str) Source code where the main.py live

     



     source.dir = .

     



     (list) Source files to include (let empty to include all the files)

     



     source.include_exts = py,png,jpg,kv,atlas

     



     (list) List of inclusions using pattern matching

     



     source.include_patterns = assets/,images/.png

     



     (list) Source files to exclude (let empty to not exclude anything)

     



     source.exclude_exts = spec

     



     (list) List of directory to exclude (let empty to not exclude anything)

     



     source.exclude_dirs = tests, bin

     



     (list) List of exclusions using pattern matching

     



     source.exclude_patterns = license,images//.jpg

     



     (str) Application versioning (method 1)

     



     version = 0.1

     



     (str) Application versioning (method 2)

     



     version.regex = version = '"['"]

     



     version.filename = %(source.dir)s/main.py

     



     (list) Application requirements

     



     comma seperated e.g. requirements = sqlite3,kivy

     



     requirements = ffmpeg,python2,hostpython2,kivy,youtube-dl

     



     (str) Custom source folders for requirements

     



     Sets custom source for any requirements with recipes

     



     requirements.source.kivy = ../../kivy

     



     (list) Garden requirements

     



     garden_requirements =

     



     (str) Presplash of the application

     



     presplash.filename = %(source.dir)s/data/presplash.png

     



     (str) Icon of the application

     



     icon.filename = %(source.dir)s/data/icon.png

     



     (str) Supported orientation (one of landscape, portrait or all)

     



     orientation = portrait

     



     (list) List of service to declare

     



     services = NAME:ENTRYPOINT_TO_PY,NAME2:ENTRYPOINT2_TO_PY

     



     OSX Specific

     



     author = © Copyright Info

     



     change the major version of python used by the app

     



     osx.python_version = 3

     



     Kivy version to use

     



     osx.kivy_version = 1.9.1

     



     Android specific

     



     (bool) Indicate if the application should be fullscreen or not

     



     fullscreen = 0

     



     (string) Presplash background color (for new android toolchain)

     



     Supported formats are : #RRGGBB #AARRGGBB or one of the following names :

     



     red, blue, green, black, white, gray, cyan, magenta, yellow, lightgray,

     



     darkgray, grey, lightgrey, darkgrey, aqua, fuchsia, lime, maroon, navy,

     



     olive, purple, silver, teal.

     



     android.presplash_color = #FFFFFF

     



     (list) Permissions

     



     android.permissions = INTERNET

     



     (int) Android API to use

     



     android.api = 19

     



     (int) Minimum API required

     



     android.minapi = 9

     



     (int) Android SDK version to use

     



     android.sdk = 20

     



     (str) Android NDK version to use

     



     android.ndk = 10.3.2

     



     (bool) Use —private data storage (True) or —dir public storage (False)

     



     android.private_storage = True

     



     (str) Android NDK directory (if empty, it will be automatically downloaded.)

     



     android.ndk_path = /home/gjones/Downloads/crystax-ndk-10.3.2

     



     (str) Android SDK directory (if empty, it will be automatically downloaded.)

     



     android.sdk_path =

     



     (str) ANT directory (if empty, it will be automatically downloaded.)

     



     android.ant_path =

  


  8. Lastly, when I remove ffmpeg from requirements in buildozer.spec, the .APK compiles successfully and i can deploy it on to my phone with the KIVY GUI. Obviously, ffmpeg functionality is not present.

  


  



  Current Environment Specs :

  



  

  1. Running Linux Mint 17.2 as a Virtual Box VM

  


  2. Buildozer Version : 0.35dev

  


  3. Cython Version : 0.25

  


  



  Any advice would be greatly appreciated.

  



  Lastly, if there is no obvious solution via buildozer, do i need to compile ffmpeg for Android separately and somehow include this somewhere in the buildozer spec file to prevent this error message ?

  



  Thanks in advance.