kickstart | Decentralized kickstarter.com using Ethereum | Cryptocurrency library

What is the pythonic, one way of sleeping forever on the asyncio event loop?

asyncio.run is a higher level API and is typically the preferred way of running an event loop. There's nothing wrong with using the lower level run_forever, though.

The problem here is this will fail with an error of the sorts RuntimeError: no running event loop when I call asyncio.create_task()

This doesn't work since create_task can't get the running event loop. Fortunately there is also a create_task method on loops. You'll need to update create_tasks_and_register_callbacks to accept the loop as an argument

Most likely openjdk:8 base Docker image that you used doesn't support TLS version required by AWS Aurora. You have to review which TLS version is allowed by your AWS Aurora and then make sure that Java installed in your Docker image supports it. You can take a look at this answer or this answer.

Please note that recently, in April 2021, Java™ SE Development Kit 8, Update 291 (JDK 8u291) changed allowed TLS versions:

➜ Disable TLS 1.0 and 1.1

TLS 1.0 and 1.1 are versions of the TLS protocol that are no longer considered secure and have been superseded by more secure and modern versions (TLS 1.2 and 1.3).

These versions have now been disabled by default. If you encounter issues, you can, at your own risk, re-enable the versions by removing "TLSv1" and/or "TLSv1.1" from the jdk.tls.disabledAlgorithms security property in the java.security configuration file.

To create a theme you want to use createMuiTheme (https://material-ui.com/customization/theming/)

Bytecode of a smart contract is published in a transaction (that is mined in a block), and then stored in a storage of the network (usually Ethereum or Binance Smart Chain) associated with an address.

So each time when you're interacting with a smart contract, you're interacting with an address that is associated with a storage chunk containing the bytecode. Plus the bytecode points to other storage slots where the values of its variables are stored.

All state changes (including changes of the storage values) are part of the ledger database. The raw blockchain data only contain the state changes (not the current state), but most higher layers return the current state by default (you can still chose to fetch an older state, e.g. the "defaultBlock" param here). And some layers even disallow accessing previous states (e.g. Solidity and Vyper languages for writing smart contracts - you can compile this code to the bytecode).

But how does the the smart contract know when to pay the project team?

A smart contract can access current balance of any address, including its own. It can also have a variable containing the funding goal. Comparing these two values tells you whether the goal has been reached and whether the smart contract should pay the project team.

However, smart contracts currently don't have any native timers (such as cronjobs) or event handlers - and functions are executed after a transaction is sent to the address of the smart contract (data field of the transaction states what function you want to execute and what arguments you're passing).

So you need to either send the transaction (executing the withdraw() function) manually or using some offchain tool (that can watch the current balance and then send the transaction executing the function for you).

If your target is only to remove spaces from words, am not sure if you really need regex.

You can use simple replace() function like this:

Generics support it's on the works. Currently the only missing piece is adding support of it in the VS debugger library. We plan to tackle that soon.

xgboost library is currently under updating to fix this bug, so the current solution is to downgrade the library to older versions, for me I have solved this problem by downgrading to xgboost v0.90

Try to check your xgboost version by cmd:

you need to add an embedding layer at the top of your NN to kind of vectorize words. something like this:

The merging logic is incorrect. The code only tries to merge the entire ranges. In a simple failing case