acroos edited a comment on issue #6380: [AIRFLOW-3632] Allow replace_microseconds in trigger_dag REST reqeust URL: https://github.com/apache/airflow/pull/6380#issuecomment-549362931 @ashb can I clarify the exact behavior that you're expecting? As far as I can tell there are 6 scenarios: ### microseconds not replaced 1. User gives `execution_date`, does not give `replace_microseconds` => given execution date with microseconds **not** replaced 2. User gives `execution_date`, gives `replace_microseconds=False` => given execution date with microseconds **not** replaced 3. User does not give `execution_date`, gives `replace_microseconds=False` => `timezone.utcnow()` with microseconds **not** replaced --- ### microseconds replaced 4. User gives `execution_date`, gives `replace_microseconds=True` => given execution date with microseconds replaced 5. User does not give `execution_date`, does not give `replace_microseconds` => `timezone.utcnow()` with microseconds replaced 6. User does not give `execution_date`, gives `replace_microseconds=True` => `timezone.utcnow()` with microseconds replaced Are all of these scenarios correct? The only non-obvious situation I guess is that not passing any value for `replace_microseconds` results in different outputs depending on if the `execution_date` was given or not
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
