Recherche avancée
Autres articles (45)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Les tâches Cron régulières de la ferme
1er décembre 2010, parLa gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
Le super Cron (gestion_mutu_super_cron)
Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...) -
Soumettre améliorations et plugins supplémentaires
10 avril 2011Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)
Sur d’autres sites (7625)
-
Anomalie #3663 (Fermé) : Anomalie espace privé
22 mai 2016Je ferme donc le ticket. Si le plugin Albums pose un problème, merci de le signaler sur le forum du plugin.
-
The 7 GDPR Principles : A Guide to Compliance
11 août 2023, par Erin — Analytics Tips, GDPRWe all knew it was coming. It’s all anyone could talk about — the General Data Protection Regulation (GDPR) took effect on 25 May 2018.
You might think five years would have been plenty of time for organisations to achieve compliance, yet many have failed to do so. As of 2022, 81% of French businesses and 95% of American companies were still not compliant.
If you’re one of these organisations still working on compliance, this blog will provide valuable information about the seven GDPR principles and guide you on your way to compliance. It will also explore how web analytics tools can help organisations improve transparency, ensure data security and achieve GDPR compliance.
What is GDPR ?
The European Union (EU) created the General Data Protection Regulation (GDPR) to grant individuals greater control over their data and promote transparency in data processing.
Known by many other names across Europe (e.g., RGPD, DSGVO, etc.), the GDPR created a set of rules surrounding the handling of personal data of EU citizens and residents, to make sure organisations aren’t being irresponsible with user names, locations, IP addresses, information gleaned from cookies, and so on.
Organisations must assume several responsibilities to achieve GDPR compliance, regardless of their physical location. These obligations include :
- Respecting user rights
- Implementing documentation and document retention policies
- Ensuring data security
Why is GDPR compliance important ?
Data has become a valuable asset for businesses worldwide. The collection and use of data is a feature of almost every sector. However, with increased data usage comes a greater responsibility to protect individuals’ privacy and rights.
A YouGov study conducted in 17 key markets found that two in three adults worldwide believe tech corporations across all markets have too much control over their data.
GDPR is the most extensive government framework aiming to tackle the increasing concern over data collection and handling. GDPR safeguards personal data from misuse, unauthorised access and data breaches. It ensures that businesses handle information responsibly and with respect for individual privacy. It also provided a foundation for similar laws to be created in other countries, including China, which is among the least concerned regions (56%), along with Sweden (54%) and Indonesia (56%).
GDPR has been pivotal in safeguarding personal data and empowering individuals with more control over their information. Compliance with GDPR builds trust between businesses and their customers. Currently, 71% of the countries in the world are covered by data protection and privacy legislation.
What are the risks of non-compliance ?
We’ve established the siginficance of GDPR, but what about the implications — what does it mean for your business ? The consequences of non-compliance can be severe and are not worth being lax about.
According to Article 83 of the GDPR, you can be penalised up to 4% of your annual global revenue or €20 million, whichever is higher, for violations. For smaller businesses, such substantial fines could be devastating. Non-compliance could even result in legal action from individuals or data protection authorities, leading to further financial losses.
Potential outcomes are not just legal and financial. GDPR violations can significantly damage your reputation as a company. Non-compliance could also cost you business opportunities if your policies and processes do not comply and, therefore, do not align with potential partners. Customers trust businesses that take data protection seriously over those that do not.
Finally, and perhaps the most timid outcome on the surface, individuals have the right to complain to data protection authorities if they believe you violate their data rights. These complaints can trigger an investigation, and if your business is found to be breaking the rules, you could face all of the consequences mentioned above.
You may think it couldn’t happen to you, but GDPR fines have collectively reached over €4 billion and are growing at a notable rate. Fines grew 92% from H1 2021 compared with H1 2022. A record-breaking €1.2 billion fine to Meta in 2023 is the biggest we’ve seen, so far. But smaller businesses can be fined, too. A bank in Hungary was fined €1,560 for not erasing and correcting data when the subject requested it. (Individuals can also be fined in flagrant cases, like a police officer fined €1,400 for using police info for private purposes.)
The 7 GDPR principles and how to comply
You should now have a good understanding of GDPR, why it’s important and the consequences of not being compliant.
Your first step to compliance is to identify the personal data your organisation processes and determine the legal basis for processing each type. You then need to review your data processing activities to ensure they align with the GDPR’s purpose and principles.
There are seven key principles in Article 5 of the GDPR that govern the lawful processing of personal data :
Lawfulness, fairness and transparency
This principle ensures you collect and use data in a legal and transparent way. It must be collected with consent, and you must tell your customers why you need their data. Data processing must be conducted fairly and transparently.
How to comply
- Review your data practices and identify if and why you collect personal data from customers.
- Learn what personally identifiable information (PII) is.
- Update your website and forms to include a clear and easy-to-understand explanation of why you need their data and what you’ll use it for.
- Obtain explicit consent from individuals when processing their sensitive data.
- Add a cookie consent banner to your website, informing users about the cookies you use and why.
- Website analytics tools like Google Analytics and Matomo offer the ability to create cookie consent banners and integrate with Consent Management Platforms (CMPs) to manage user consent and privacy settings.
- Matomo also offers a setting without tracking cookies, in which case you would not need to add the cookie consent banner.
- Privacy notices must be accessible at all times.
- To ensure your cookies are GDPR compliant, you must :
- Get consent before using any cookies (except strictly necessary cookies).
- Clearly explain what each cookie tracks and its purpose.
- Document and store user consent.
- Don’t refuse access to services if users do not consent to the use of certain cookies.
- Make the consent withdrawal process simple.
Use tools like Matomo that can be configured to automatically anonymise data so you don’t process any personal data.
Purpose limitation
You can only use data for the specific, legitimate purposes you told your visitors, prospects or customers about at the time of collection. You can’t use it for anything else without asking again.
How to comply
- Define the specific purposes for collecting personal data (e.g., processing orders, sending newsletters).
- Ensure you don’t use the data for any other purposes without getting explicit consent from the individuals.
Data minimisation
Data minimisation means you should only collect the data you need, aligned with the stated purpose. You shouldn’t gather or store more data than necessary. Implementing data minimisation practices ensures compliance and protects against data breaches.
How to comply
- Identify the minimum data required for each purpose.
- Conduct a data audit to identify and eliminate unnecessary data collection points.
- Don’t ask for unnecessary information or store data that’s not essential for your business operations.
- Implement data retention policies to delete data when it is no longer required.
Accuracy
You are responsible for keeping data accurate and up-to-date at all times. You should have processes to promptly erase or correct any data if you have incorrect information for your customers.
How to comply
- Implement a process to regularly review and update customer data.
- Provide an easy way for customers to request corrections to their data if they find any errors.
Storage limitation
Data should not be kept longer than necessary. You should only hold onto it for as long as you have a valid reason, which should be the purpose stated and consented to. Securely dispose of data when it is no longer needed. There is no upper time limit on data storage.
How to comply
- Set clear retention periods for the different types of data you collect.
- Develop data retention policies and adhere to them consistently.
- Delete data when it’s no longer needed for the purposes you specified.
Integrity and confidentiality
You must take measures to protect data from unauthorised or unlawful access, like keeping it locked away and secure.
How to comply
- Securely store personal data with encryption and access controls, and keep it either within the EU or somewhere with similar privacy protections.
- Train your staff on data protection and restrict access to data only to those who need it for their work.
- Conduct regular security assessments and address vulnerabilities promptly.
Accountability
Accountability means that you are responsible for complying with the other principles. You must demonstrate that you are following the rules and taking data protection seriously.
How to comply
- Appoint a Data Protection Officer (DPO) or someone responsible for data privacy in your company.
- Maintain detailed records of data processing activities and any data breaches.
- Data breaches must be reported within 72 hours.
Compliance with GDPR is an ongoing process, and it’s vital to review and update your practices regularly.
What are GDPR rights ?
Individuals are granted various rights under the GDPR. These rights give them more control over their personal data.
The right to be informed : People can ask why their data is required.
What to do : Explain why personal data is required and how it will be used.
The right to access : People can request and access the personal data you hold about them.
What to do : Provide a copy of the data upon request, free of charge and within one month.The right to rectification : If data errors or inaccuracies are found, your customers can ask you to correct them.
What to do : Promptly update any incorrect information to ensure it is accurate and up-to-date.The right to object to processing : Your customers have the right to object to processing their data for certain purposes, like direct marketing.
What to do : Respect this objection unless you have legitimate reasons for processing the data.Rights in relation to automated decision-making and profiling : GDPR gives individuals the right not to be subject to decisions based solely on automated processing, including profiling, if it significantly impacts them.
What to do : Offer individuals the right to human intervention and express their point of view in such cases.The right to be forgotten : Individuals can request the deletion of their data under certain circumstances, such as when the data is no longer necessary or when they withdraw consent.
What to do : Comply with such requests unless you have a legal obligation to keep the data.The right to data portability : People can request their personal data in a commonly used and machine-readable format.
What to do : Provide the data to the individual if they want to transfer it to another service provider.The right to restrict processing : Customers can ask you to temporarily stop processing their data, for example, while they verify its accuracy or when they object to its usage.
What to do : Store the data during this period but do not process it further.Are all website analytics tools GDPR compliant ?
Unfortunately, not all web analytics tools are built the same. No matter where you are located in the world, if you are processing the personal data of European citizens or residents, you need to fulfil GDPR obligations.
While your web analytics tool helps you gain valuable insights from your user base and web traffic, they don’t all comply with GDPR. No matter how hard you work to adhere to the seven principles and GDPR rights, using a non-compliant tool means that you’ll never be fully GDPR compliant.
When using website analytics tools and handling data, you should consider the following :
Collection of data
Aligned with the lawfulness, fairness and transparency principle, you must collect consent from visitors for tracking if you are using website analytics tools to collect visitor behavioural data — unless you anonymise data entirely with Matomo.
To provide transparency, you should also clarify the types of data you collect, such as IP addresses, device information and browsing behaviour. Note that data collection aims to improve your website’s performance and understand your audience better.
Storage of data
Assure your visitors that you securely store their data and only keep it for as long as necessary, following GDPR’s storage limitation principle. Clearly state the retention periods for different data types and specify when you’ll delete or anonymise it.
Usage of data
Make it clear that to comply with the purpose limitation principle, the data you collect will not be used for other purposes beyond website analytics. You should also promise not to share data with third parties for marketing or unrelated activities without their explicit consent.
Anonymisation and pseudonymisation
Features like IP anonymisation to protect users’ privacy are available with GA4 (Google Analytics) and Matomo. Describe how you use these tools and mention that you may use pseudonyms or unique identifiers instead of real names to safeguard personal data further.
Cookies and consent
Inform visitors that your website uses cookies and other tracking technologies for analytics purposes. Matomo offers customisable cookie banners and opt-out options that allow users to choose their preferences regarding cookies and tracking, along with cookieless options that don’t require consent banners.
Right to access and correct data
Inform visitors of their rights and provide instructions on requesting information. Describe how to correct inaccuracies in their data and update their preferences.
Security measures
Assure visitors that you take data security seriously and have implemented measures to protect their data from unauthorised access or breaches. You can also use this opportunity to highlight any encryption or access controls you use to safeguard data.
Contact information
Provide contact details for your company’s Data Protection Officer (DPO) and encourage users to reach out if they have any questions or concerns about their data and privacy.
When selecting web analytics tools, consider how well they align with GDPR principles. Look for features like anonymisation, consent management options, data retention controls, security measures and data storage within the EU or a similarly privacy-protecting jurisdiction.
Matomo offers an advanced GDPR Manager. This is to make sure websites are fully GDPR compliant by giving users the ability to access, withdraw consent, object or erase their data, in addition to the anonymizing features.
And finally, when you use Matomo, you have 100% data ownership — stored with us in the EU if you’re using Matomo Cloud or on your own servers with Matomo On-Premise — so you can be data-driven and still be compliant with worldwide privacy laws. We are also trusted across industries as we provide accurate data (no trying to fill in the gaps with AI), a robust API that lets you connect your data to your other tools and cookieless tracking options so you don’t need a cookie consent banner. What’s more, our open-source nature allows you to explore the inner workings, offering the assurance of security firsthand.
Ready to become GDPR compliant ?
Whether you’re an established business or just starting out, if you work with data from EU citizens or residents, then achieving GDPR compliance is essential. It doesn’t need to cost you a fortune or five years to get to compliant status. With the right tools and processes, you can be on top of the privacy requirements in no time at all, avoiding any of those hefty penalties or the resulting damage to your reputation.
You don’t need to sacrifice powerful data insights to be GDPR compliant. While Google Analytics uses data for its ‘own purposes’, Matomo is an ethical alternative. Using our all-in-one web analytics platform means you own 100% of your data 100% of the time.
Start a 21-day free trial of Matomo — no credit card required.
Disclaimer
We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to GDPR. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns.
-
Stage-Whisper is not working because of missing files
24 novembre 2023, par TingtongI tried to install this here : https://github.com/Stage-Whisper/Stage-Whisper


Once i put the audio file in it, it is still loading and loading but not transcribing it.


So after that i checked the requirements and packages, if there is something missing and there is. I installed those here :


Node (required for Electron)
Yarn (required for Electron)
Python 3.x (required for backend)
Rust (required for backend)
ffmpeg (required for backend)
Poetry (required for backend)


I installed them with homebrew. There are some errors showing up, once i launch the electron programm with "yarn dev" : ERROR : "could not locate binding files"


I also tried "poetry run python stagewhisper —input /path/to/audio/file.mp3", but got following message. Poetry could not find a pyproject.toml file in /Users/Administrator/Desktop/Stage-Whisper or its parents.


Where do i have to put the file pyproject.toml and what do i have to write in it ?


So i checked with brew info all tools which i need for Stage-Whisper. Screenshots :enter image description here
[enter image description here](https://i.stack.imgur.com/sirb3.png)


What i tried was to update those packages/requirements which where missing, with "sudo port install requirementPackageName ". But after checking with brew info again, those parts are still missing. So does that actually work or do i have to install those missing stuff with homebrew ? I have Mac Mojave 10.14.6 and Homebrew 4.1.18 Version.


I also got an error, while i installed those tools with homebrew :


ERROR : You are using macOS 10.14.
We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version... etc


Thank you for your help guys.


Edit :




yarn install v1.22.19 warning ../../../package.json : No license field
[1/4] 🔍 Resolving packages... [2/4] 🚚 Fetching packages... [3/4]
🔗 Linking dependencies... warning "@emotion/react >
@emotion/babel-plugin@11.10.2" has unmet peer dependency
"@babel/core@^7.0.0". warning "@emotion/react > @emotion/babel-plugin




@babel/plugin-syntax-jsx@7.18.6" has unmet peer dependency "@babel/core@^7.0.0-0". warning " > autoprefixer@10.4.4" has unmet
peer dependency "postcss@^8.1.0". warning " >
eslint-config-airbnb@19.0.4" has unmet peer dependency
"eslint-plugin-react-hooks@^4.3.0".
[----------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 0/890^[4/4] 🔨 Building fresh packages... [1/7] ⠁ better-sqlite3
[-/7] ⠁ waiting... [3/7] ⠁ sqlite3 [4/7] ⠁ esbuild error
/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3 :
Command failed. Exit code : 1 Command : prebuild-install || npm run
build-release Arguments : Directory :
/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3
Output : prebuild-install warn install No prebuilt binaries found
(target=20.9.0 runtime=node arch=x64 libc= platform=darwin)






better-sqlite3@7.6.2 build-release
node-gyp rebuild —release




gyp info it worked if it ends with ok gyp info using node-gyp@9.3.0
gyp info using node@20.9.0 | darwin | x64 gyp info find Python using
Python version 3.9.14 found at "/usr/local/bin/python3" gyp info spawn
/usr/local/bin/python3 gyp info spawn args [ gyp info spawn args

'/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp', gyp info spawn args '-f', gyp
info spawn args 'make', gyp info spawn args '-I', gyp info spawn
args

'/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3/build/config.gypi',
gyp info spawn args '-I', gyp info spawn args

'/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I', gyp info spawn args

'/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library', gyp info spawn args
'-Dvisibility=default', gyp info spawn args

'-Dnode_root_dir=/Users/administrator/Library/Caches/node-gyp/20.9.0',
gyp info spawn args

'-Dnode_gyp_dir=/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp',
gyp info spawn args

'-Dnode_lib_file=/Users/administrator/Library/Caches/node-gyp/20.9.0/<(target_arch)/node.lib',
gyp info spawn args

'-Dmodule_root_dir=/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3',
gyp info spawn args '-Dnode_engine=v8', gyp info spawn args

'—depth=.', gyp info spawn args '—no-parallel', gyp info spawn
args '—generator-output', gyp info spawn args 'build', gyp info
spawn args '-Goutput_dir=.' gyp info spawn args ] gyp info spawn
make gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]

TOUCH ba23eeee118cd63e16015df367567cb043fed872.intermediate ACTION
deps_sqlite3_gyp_locate_sqlite3_target_copy_builtin_sqlite3
ba23eeee118cd63e16015df367567cb043fed872.intermediate TOUCH
Release/obj.target/deps/locate_sqlite3.stamp CC(target)
Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o LIBTOOL-STATIC
Release/sqlite3.a CXX(target)
Release/obj.target/better_sqlite3/src/better_sqlite3.o In file
included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:12 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-local-handle.h:12 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
SHARED_EXTERNAL_POINTER_TAGS(CHECK_SHARED_EXTERNAL_POINTER_TAGS)
^ /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:465:30 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
PER_ISOLATE_EXTERNAL_POINTER_TAGS(CHECK_NON_SHARED_EXTERNAL_POINTER_TAGS)
^ /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:466:35 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:693:61 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
static_assert(kJSObjectType + 1 == kFirstJSApiObjectType) ;
^
, "" /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:694:55 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
static_assert(kJSObjectType < kLastJSApiObjectType) ;
^
, "" /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-internal.h:695:63 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
static_assert(kFirstJSApiObjectType < kLastJSApiObjectType) ;
^
, "" In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:13 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-object.h:9 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:106:45 :
error : no template named 'is_lvalue_reference_v' in namespace 'std' ;
did you mean 'is_lvalue_reference' ? template>
 ^ 
is_lvalue_reference /Library/Developer/CommandLineTools/usr/include/c++/v1/type_traits:780:50 :
note : 'is_lvalue_reference' declared here template struct
_LIBCPP_TEMPLATE_VIS is_lvalue_reference : public false_type {} ;
^ In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:13 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-object.h:9 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:106:69 :
error : expected '(' for function-style cast or type construction

template>
 ^ /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:123:43 :
error : no template named 'is_lvalue_reference_v' in namespace 'std' ;
did you mean 'is_lvalue_reference' ? template * = nullptr>
 ^ 
is_lvalue_reference /Library/Developer/CommandLineTools/usr/include/c++/v1/type_traits:780:50 :
note : 'is_lvalue_reference' declared here template struct
_LIBCPP_TEMPLATE_VIS is_lvalue_reference : public false_type {} ;
^ In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:24 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-array-buffer.h:13 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-object.h:9 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-maybe.h:123:67 :
error : expected '(' for function-style cast or type construction
template * =
nullptr>
 ^ In file included from ../src/better_sqlite3.cpp:4 : In file included from
./src/better_sqlite3.lzz:11 : In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/node.h:73 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8.h:33 :
In file included from
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-function.h:11 :
/Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-function-callback.h:151:66 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
kReturnValueDefaultValueIndex - kReturnValueIndex) ;
^
, "" /Users/administrator/Library/Caches/node-gyp/20.9.0/include/node/v8-function-callback.h:153:50 :
warning : static_assert with no message is a C++17 extension
[-Wc++17-extensions]
kIsolateIndex - kReturnValueIndex) ;
^
, "" ./src/util/macros.lzz:157:21 : error : no member named
'AccessorSignature' in namespace 'v8'
v8::AccessorSignature::New(isolate, recv)
 ^ ./src/util/binder.lzz:37:51 : error : no member named 'CreationContext' in 'v8::Object'
v8::Local ctx = obj->CreationContext() ;
 ^ 22 warnings and 6 errors generated. make : ***
[Release/obj.target/better_sqlite3/src/better_sqlite3.o] Error 1 rm
ba23eeee118cd63e16015df367567cb043fed872.intermediate gyp ERR ! build
error gyp ERR ! stack Error : makefailed with exit code : 2 gyp ERR !
stack at ChildProcess.onExit
(/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/electron-rebuild/node_modules/node-gyp/lib/build.js:203:23)
gyp ERR ! stack at ChildProcess.emit (node:events:514:28) gyp ERR !
stack at ChildProcess._handle.onexit
(node:internal/child_process:294:12) gyp ERR ! System Darwin 18.7.0 gyp
ERR ! command "/usr/local/bin/node"
"/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/.bin/node-gyp"
"rebuild" "—release" gyp ERR ! cwd
/Users/administrator/Desktop/Stage-Whisper/electron/node_modules/better-sqlite3



Same goes for the the "poetry install" command in the backend folder :


8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/onig_sys-3a9a2f947b5ad744/out
warning: variable does not need to be mutable --> tokenizers-lib/src/models/unigram/model.rs:265:21 | 265 | let mut target_node = &mut best_path_ends_at[key_pos]; | ----^^^^^^^^^^^ | | | help: remove thismut| = note:#[warn(unused_mut)]` on by default

warning : variable does not need to be mutable
—> tokenizers-lib/src/models/unigram/model.rs:282:21
|
282 | let mut target_node = &mut best_path_ends_at[starts_at + mblen] ;
| ----^^^^^^^^^^^
| |
| help : remove this
mut

warning : variable does not need to be mutable
—> tokenizers-lib/src/pre_tokenizers/byte_level.rs:200:59
|
200 | encoding.process_tokens_with_offsets_mut(|(i, (token, mut offsets))| 
| ----^^^^^^^
| |
| help : remove this
mut

error : casting
&Tto&mut Tis undefined behavior, even if the reference is unused, consider instead using anUnsafeCell
—> tokenizers-lib/src/models/bpe/trainer.rs:526:47
|
522 | let w = &words[*i] as *const _ as *mut _ ;
| -------------------------------- casting happend here
...
526 | let word : &mut Word = &mut (*w) ;
| ^^^^^^^^^
|
= note :#[deny(invalid_reference_casting)]on by default

warning :
tokenizers(lib) generated 3 warnings
error : could not compiletokenizers(lib) due to previous error ; 3 warnings emitted

Caused by :
process didn't exit successfully :
/Users/administrator/.rustup/toolchains/stable-x86_64-apple-darwin/bin/rustc --crate-name tokenizers --edition=2018 tokenizers-lib/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="cached-path"' --cfg 'feature="clap"' --cfg 'feature="cli"' --cfg 'feature="default"' --cfg 'feature="http"' --cfg 'feature="indicatif"' --cfg 'feature="progressbar"' --cfg 'feature="reqwest"' -C metadata=cb36f9861d265e60 -C extra-filename=-cb36f9861d265e60 --out-dir /private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps -L dependency=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps --extern aho_corasick=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libaho_corasick-021885281f13d108.rmeta --extern cached_path=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libcached_path-767095c4d4a77107.rmeta --extern clap=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libclap-c92d2593d8a75e62.rmeta --extern derive_builder=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libderive_builder-833217c2af636976.dylib --extern dirs=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libdirs-f12e99ecd3a76eae.rmeta --extern esaxx_rs=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libesaxx_rs-b694f04df571686b.rmeta --extern indicatif=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libindicatif-39491a3282a24810.rmeta --extern itertools=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libitertools-b322e49e83853c17.rmeta --extern lazy_static=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/liblazy_static-28a96417d88df3c9.rmeta --extern log=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/liblog-937f94f366843d8a.rmeta --extern macro_rules_attribute=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libmacro_rules_attribute-d4d77bee9330e675.rmeta --extern onig=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libonig-7f9dab4334743bdf.rmeta --extern paste=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libpaste-a36a4a0dbc2ac63f.dylib --extern rand=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/librand-4b1adc86e35ea892.rmeta --extern rayon=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/librayon-d134e48f83d52e6e.rmeta --extern rayon_cond=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/librayon_cond-5715a923c66c54a9.rmeta --extern regex=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libregex-a5c54f2d0034ab98.rmeta --extern regex_syntax=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libregex_syntax-58c405f62323b6ed.rmeta --extern reqwest=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libreqwest-1551c89d20e17f58.rmeta --extern serde=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libserde-f4748cc953dd1338.rmeta --extern serde_json=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libserde_json-5fba404e8440399e.rmeta --extern spm_precompiled=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libspm_precompiled-6bd24072bd3c9d31.rmeta --extern thiserror=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libthiserror-bcbb2769006ee534.rmeta --extern unicode_normalization_alignments=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libunicode_normalization_alignments-658520cf6a5461dc.rmeta --extern unicode_segmentation=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libunicode_segmentation-fffd829ab6256bb0.rmeta --extern unicode_categories=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/deps/libunicode_categories-e3815c3d18c1086b.rmeta -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/bzip2-sys-d2cb72d65b178690/out/lib -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/zstd-sys-ddff0154a55a136c/out -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/esaxx-rs-69d9e34a40d41449/out -L native=/private/var/folders/zc/c2qvlcjd5cgcg5l84484t8vh0000gt/T/tmp2yohvwu_/tokenizers-0.12.1/target/release/build/onig_sys-3a9a2f947b5ad744/out(exit status : 1)
error :cargo rustc --lib --message-format=json-render-diagnostics --manifest-path Cargo.toml --release -v --features pyo3/extension-module --crate-type cdylib -- -C 'link-args=-undefined dynamic_lookup -Wl,-install_name,@rpath/tokenizers.cpython-311-darwin.so'failed with code 101

at /usr/local/lib/python3.11/site-packages/poetry/installation/chef.py:166 in _prepare
162│
163│ error = ChefBuildError("\n\n".join(message_parts))
164│
165│ if error is not None :
→ 166│ raise error from None
167│
168│ return path
169│
170│ def _prepare_sdist(self, archive : Path, destination : Path | None = None) -> Path :


Note : This error originates from the build backend, and is likely not a problem with poetry but with tokenizers (0.12.1) not supporting PEP 517 builds. You can verify this by running 'pip wheel —no-cache-dir —use-pep517 "tokenizers (==0.12.1)"'.


UPDATE (SOLVED) :


- 

- i found a solution and this worked for me :




"I had the same problem and nothing mentioned here worked for me. Here is what worked for me :


**("Didnt do this Part")"Require all dependencies you need in the main.js file that is run by electron."** 


What i did was :
Run npm i -D electron-rebuild to add the electron-rebuild package
Remove the node-modules folder, as well as the packages-lock.json file.
Run npm i to install all modules.
Run ./node_modules/.bin/electron-rebuild (.\node_modules.bin\electron-rebuild.cmd for Windows) to rebuild everything


It is very important to run ./node_modules/.bin/electron-rebuild directly after npm i otherwise it did not work on my mac."


But now i get following Error, when i upload and transcribe the file :


> [ELECTRON] NewEntry: Creating new entry with UUID: XY...
[ELECTRON] NewEntry: Copying audio file to store...
[ELECTRON] NewEntry: Audio file copied to store.
[ELECTRON] NewEntry: Entry added to database!
[ELECTRON] RunWhisper: Running model with args [
[ELECTRON] '--verbose',
[ELECTRON] 'true',
[ELECTRON] '--output_dir',
[ELECTRON] '/Users/administrator/Library/Application Support/stagewhisper/store/whisper/2a07203b-ad88-438c-babf-b600cb76aa1d',
[ELECTRON] '--task',
[ELECTRON] 'translate',
[ELECTRON] '--model',
[ELECTRON] 'base',
[ELECTRON] '--device',
[ELECTRON] 'cpu',
[ELECTRON] '--input',
[ELECTRON] '/Users/administrator/Library/Application Support/stagewhisper/store/audio/harvard.mp3'
[ELECTRON] ]
[ELECTRON] RunWhisper: Child process closed with code 1
[ELECTRON] RunWhisper: Error running whisper script!
[ELECTRON] Error occurred in handler for 'run-whisper': Error: Error running whisper script!
[ELECTRON] at ChildProcess.<anonymous> (/Users/administrator/Desktop/Stage-Whisper/electron/main/handlers/runWhisper/runWhisper.js:234:31)
[ELECTRON] at ChildProcess.emit (node:events:390:28)
[ELECTRON] at maybeClose (node:internal/child_process:1064:16)
[ELECTRON] at Socket.<anonymous> (node:internal/child_process:450:11)
[ELECTRON] at Socket.emit (node:events:390:28)
[ELECTRON] at Pipe.<anonymous> (node:net:687:12)

 
</anonymous></anonymous></anonymous>

Syndiquer tout le site
