266 karma · joined October 30, 2012
I wouldn’t be surprised if all bank stocks are halted with the market open, to contain the contagion.
https://twitter.com/rywalker/status/1634614103586078721?s=46...
All banks are going to see large depositors pull funds, to diversify risks. They will have incoming deposit activity too, but the weaker ones may have a cash crunch that causes a widespread run, as dominos begin to fall.
Hopefully govt takes quick actions like this one, to minimize effect - but we are definitely getting more pain before relief :(
I've never used either framework; would you agree with that assessment from other signals you've seen?
Looks like Actix dropped off a lot since Nikolay Kim stepped away from the project (no commits for past year https://ossrank.com/p/1906-actix)
I added it for you though @ https://ossrank.com/p/2037 (1000 isn't the real rank, will take a few hours to get ranked, we rescore projects every 3 hours)
#MVP
We've added Gladys Assistant @ https://ossrank.com/p/2035
Combining commits + contributors is my favorite (obviously!), especially when considered over a long time range.
Yes, some (usually smaller) teams make small incremental commits, others have more ceremony and commits tend to be less frequent and bigger. And you could easily game the system theoretically, but not easily in a project of important and substance.
We've added a voting system, where we give every dev 20 votes, and we'd give more notable OSS contributors a higher weighting, but it's very early days for that — but we'd mix that data into the score if we had it.
How would you do it? We're open to suggestions :)
"Environments with CREATING status must complete previous operation before initiating a new operation."
can't email support for help (i only have basic plan)
any AWSMWAA ppl on this thread and can help? the instance name is `airflow-ry-test`.
disclosure: co-founder of astronomer
We're working on making the scheduler HA and more performant, reach out to me if you'd like to collaborate on your use case (ry at astronomer dot io)
2) Yes the UI is outdated, and not responsive. We're going to kick off a process to build a new modern UI in Q3 (a full-featured Swagger API is being built now, which the new UI will rely upon.)
3) I personally think catchup true is a fine default, but whatever. Generally when I launch a new DAG I want to generate some historical data using the DAG.
4) Airflow has tags now since 1.10.8 https://airflow.readthedocs.io/en/latest/howto/add-dag-tags.... - we decided not to do folders.
5) That's true, but it also provides a low bar to entry. There are some guides written on unit testing DAGs, but I agree we should be a test-first community. On my roadmap.
6) Celery w/ KEDA is pretty nice - check out https://www.astronomer.io/blog/the-keda-autoscaler/
7) I personally love the PythonOperator for simple DAGs. Agree that DockerOperator (KubernetesPodOperator if you're running Airflow in K8s)
8) Yes, logging UI will be improved in the UI rewrite. What's your favorite UI for this?
9) That feature is in the queue https://github.com/apache/airflow/issues/7911
We fell in love with Airflow's capability to allow us to write one small python program that generated hundreds of tailored dags by iterating over the configuration of each of our customers. This dynamism is very powerful for similar use cases.
re: idempotency - yes, make your workflow tasks idempotent.
re: latency - this is being worked on very actively. Ash (PMC member) has committed to working on task latency almost exclusively until it's resolved
re: sensors, there is some great work from Airbnb to improve: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-17+A...