- This topic is empty.
- The topic ‘Extra Topic Rules – READ FIRST!’ is closed to new replies.
Forums / XNL Future Technologies / Bug Reports / Extra Topic Rules – READ FIRST!
In this forum you can post (report) bugs/issues with projects you might have.
Do however make sure that you are DETAILED about the issue and include the following details when making a bug report:
Include IN DETAIL about what project or ‘product’ you are reporting a bug (including the (board) version!), what the exact issue is that you are having. When it happened, what you have tried to fix it. If you can cause it to happen multiple times doing the same (for example software crashing when you click a couple of buttons in a certain order).
If you for example are having issues using one of my boards, then explain what the exact problem is, what parts you’ve used. Make sure that it’s not a problem with your parts but actually the board itself!
Just be as detailed as possible when reporting a bug. In case of reporting a software bug, then for example also include the operating system you’re using etc.
A simple “bug report” like: “Program ….. crashing” is NOT a valid and accepted bug report! This does not provide me with ANY information on where to look how to reproduce the issue etc.
Same goes with something like: “LABUNO not connecting to USB”…. Well euhm.. “cool”🤷🏽♀️ You didn’t provided any information about what chip(s) you’ve used, if you tried different USB cables, tested your circuit on correct solder joints, if you have installed the latest (chip) drivers etc.
So PLEASE do us all a favor, and make sure that you provide as much detailed information as possible when reporting bugs and/or issues in or with any of the projects.
NOTE: Spelling/grammar issues in documentation are not considered as bugs and will not be accepted! (Unless there obviously is an error in pin names for example).
No products in the download basket.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
cookielawinfo-checkbox-videocontent | 11 months | This cookie is set by GDPR Cookie Consent system. This cookie is used to store the user's consent for cookies in the category "Embedded Video Content" and allows (or disallows) showing embedded video content on our platform. |
CookieLawInfoConsent | 11 months | The cookie is set by GDPR cookie consent system and it Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
store_notice[notice id] | session | Allows users to dismiss the store notices which might be shown at the top of the page during special announcements, events or during maintenance for example. It does not store any personal data. |
viewed_cookie_policy | 11 months | This cookie is set by the GDPR Cookie Consent system and is used to store whether or not the user has consented to the use of cookies. It does not store any personal data. |
woocommerce_cart_hash | session | This cookie helps our project and product 'store' determine when cart contents/data changes. It does not store any personal data. |
woocommerce_items_in_cart | session | This cookie helps our projects and products 'store' determine when cart contents/data changes. |
wordpress_logged_in_[hash] | session | The cookie is used to remember that you are logged in, and who you are. Without this cookie the website would not be able to recognize you as being logged-in. The [hash] part represents the value which is generated by applying a specific mathematical formula to the username and password. This is to ensure that the input values are safe and no one can access this data using the cookies. |
wordpress_test_cookie | session | This cookie is set by the website to test if it can actually set (any) cookies, this is necessary to ensure all other functionality like logging-in, storing whether you allow certain cookies or not etc. This cookie does not store any personal information. |
wp_lang | session | This cookie is set by the website's framework by default so that it knows which language it should use. This cookie does not store any personal information |
wp_woocommerce_session_ | 2 days | This cookie contains a unique code for each user so that it knows where to find the cart data in the database for each user. |
Cookie | Duration | Description |
---|---|---|
_twitter_sess | session | This cookie allows the use of Twitter features without having to log in, and contains some tracking information that Twitter uses to improve their services. (However IF Twitter indeed does what it says, the tracking part should be disabled due to the DNT (do not track) setting). |
# IMPORTANT PLEASE READ! | various | This is additional information, not a cookie! The cookies listed here are just a few of the cookies which will be set by the Twitter Timeline, there are (quite a lot of) other cookies which are also set by the Embedded Twitter Timeline when it's enabled. We do have enabled the enhanced privacy options ("do not track") features of Twitter for this Timeline, we however (of course) do not have control over possible cookies set and/or created by externally embedded content. This is also the reason why we disable the content altogether when you don't allow their cookies. You can view which cookies exactly are being placed by websites using the developer console of your browser, where and how to find this depends on your browser, but for most browsers this can be opened using F12 on your keyboard. Please make sure that you understand that externally embedded content (like the Twitter Timeline) does place additional cookies which we are not able to all list here! |
ct0 | 11 months | This cookie is set due to Twitter integration and sharing capabilities for the social media. |
dnt | 12 Months | This seem to be the Do-Not-Track / Do-Not-Taylor cookie, telling the widget not to track/taylor your content depending on our website/widget. Considering this cookie only appeared when we enabled the Privacy feature of the Twitter Widget. |
guest_id | 11 months | Unspecified |
personalization_id | 13 months | This cookie is set due to Twitter integration and sharing capabilities for the social media. |
Cookie | Duration | Description |
---|---|---|
_gads | 13 months | This cookie is associated with the DoubleClick for Publishers service from Google. Its purpose is to do with the showing of adverts on the site, for which the owner may earn some revenue. |
# IMPORTANT PLEASE READ! | various | This is additional information, not a cookie! The cookies listed here are just a few of the cookies which will be set by our advertisement provider, there are (quite a lot of) other cookies which are also set by the advertisement provider (Google/AdSense/Doubleclick) when it's enabled. We do have enabled the enhanced privacy options ("do not track") features for these advertisements, meaning they should only show completely unrelated and non personalized advertisements. We however (of course) do not have control over possible cookies set and/or created by externally embedded content. This is also the reason why we disable the content altogether when you don't allow their cookies. You can view which cookies exactly are being placed by websites using the developer console of your browser, where and how to find this depends on your browser, but for most browsers this can be opened using F12 on your keyboard. Please make sure that you understand that externally embedded content (like the advertisements) does place additional cookies which we are not able to all list here! |
Cookie | Duration | Description |
---|---|---|
# IMPORTANT PLEASE READ! | various | This is additional information, not a cookie! The cookie listed here are just a few of the cookies which can be set by the embedded video player(s), During multiple tests did not encounter any other cookies being placed by the embedded player accept about 4 ("randomly named") cookies once or twice during some extensive testing while using Chrome (other browsers did not seemed to do this). We however (of course) do not have control over possible cookies set and/or created by externally embedded content. This is also the reason why we disable the content altogether when you don't allow their cookies. You can view which cookies exactly are being placed by websites using the developer console of your browser, where and how to find this depends on your browser, but for most browsers this can be opened using F12 on your keyboard. Please make sure that you understand that externally embedded content (like the Embedded Video Content) can or does place additional cookies which we are not able to all list here! |
CONSENT | 11 months | This cookie is placed by the youtube-nocookie.com domain, we suspect that it is used to tell the player that 'consent for cookies or user-tracking' is pending (and thus should not happen) because the data within this cookie says: "PENDING+162". However we unfortunately can't confirm this because there is almost no other website or information available about this cookie. And despite the fact that almost ANY website with "GDPR Compliance Tips" tells you to "just use the YouTube-nocookie feature" to be GDRP Compliant without having to ask user consent, we do not agree! Due to the simple fact that it does still place this cookie. And due to the fact that when enabling the "YouTube Privacy Enhanced feature" it gives a popup saying: "When you turn on privacy-enhanced mode, YouTube won't store information about visitors unless they play the video.", we just don't like this kind of 'sketchy behavior' and thus require you to allow such cookies and content before we will actually display it. |