Hacktoberfest

Here I would to talk about some problems with RTL Languages and their solutions.
I will explain all the points here, and we can have a discussion about it.
and maybe add a section that talking about these problems & solution in Guidelines in CONTRIBUTING

**The base discussion on this issue starts o

Many systems don't link python to python3. Debian even maintains it's wrong for their packages to expect python to work:

NOTE: Debian testing (bullseye) has removed the "python" package and the '/usr/bin/python' symlink due to the deprecation of Python 2. No packaged scripts should depend on the existence of '/usr/bin/python': if they do, that is a bu

We have a lot of is_prime (or similar) functions: https://github.com/TheAlgorithms/Python/search?p=4&q=is_prime, https://github.com/TheAlgorithms/Python/search?q=isPrime, data_structures/hashing/number_theory/prime_numbers, etc. Shall we use one common function for that exactly identical

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

I'm implementing async load with pagination with the Autocomplete.
When the listbox is open and the user scroll to the bottom, we load the next page and add the new options.
After adding, the position of the scroll on the listbox is reseted and

Related to #5142, AlbertTokenizer (which uses SentencePiece) doesn't decode special tokens (like [CLS], [MASK]) properly. This issue was discovered when adding the Nystromformer model (#14659), which uses this tokenizer.

To reproduce (Transformers v4.15 or below):

!pip install -q transformers sentencepiece

from transformers import AlbertTokenizer

tokenizer = AlbertTokenizer.from

Proof read transcribed code of UPDATE_PROGRAM against scans

Lines: 548
Page: 1386—1396 (10)

Reduced quality scans can be found here

The following tests are outputting errant logs and warnings to the console during unit tests. Some of these are pointing out genuine errors and things that should be looked at, while others might be a bit more benign but should be cleaned up to make testing more pleasant.

In the future we may consider making console logs to be a failure condition in tests, so it would be good to sort these out

Describe the bug
At the time of registration, email has not been validated correctly http://localhost:1337/admin/auth/register

Expected behavior
An email should be valid in all aspect like

• should check valid domain, well-formed and valid mailbox

Screenshots
invalid email1:

I'm on a 14" macbook M1 pro and get the following error when trying to run a freshly downloaded/installed meteor 2.5.3:

Error: Only 64-bit Intel and M1 processors are supported on OS X

From the blogpost announcing meteor 2.5.1 I would expect meteor to work on my machine.
Given that I'm on an M1, the er

Summary

The Mail settings don't have an option to choose a TLS version. Only to enforce upgrading connections to use SSL/TLS.
Mail servers like smtp.office365.com dropped support for TLS1.0 and TLS1.1 and now require TLS1.2: https://techcommunity.microsoft.com/t5/exchange-team-blog/new-opt-in-endpoint-available-for

Issue Summary

When setting up a dev env on windows, yarn setup fails

[2021-12-21 15:45:01] INFO Relation: User to Role                                                                              
[2021-12-21 15:45:01] INFO Finished database init!                                                                             
Running "symlink:githooks" (symlink) task