The commented-out code works, but the code shown (the same as hacker_news prod job) does not):

load_uniswap_trades_local_job = <http://load_uniswap_trades.to|load_uniswap_trades.to>_job(

resource_defs={ 'partition_bounds': partition_bounds, 'moonstream_client': live_moonstream_client.configured({'api_key': os.getenv('MOONSTREAM_API_KEY')}) }, config=hourly_download_config, # config={ # 'resources': { # 'partition_bounds': { # 'config': { # 'start': '2021-11-13 00:00:00', # 'end': '2021-11-13 01:00:00', # } # }, # } # } )

@hourly_partitioned_config(start_date=datetime(2021, 11, 16))

def hourly_download_config(start: datetime, end: datetime):

return {

'resources': {

'partition_bounds': {

'config': {

'start': start.strftime(PARTITION_BOUND_DATE_FMT),

'end': end.strftime(PARTITION_BOUND_DATE_FMT),

}

},

}

}

Possible hint: this happens when I run the job with "dagster job execute" but with dagit it seems fine. I am prompted to select the hourly partition and then it creates a config similar to the one above with start/end date and runs it.

Pretty sure this is just a confusing error message resulting from a problem my end. I created a partitioned job in the repo similar to the HN example and instead of running it with "job execute" in dagster I ran with "job backfill" -- this prompted me with a list of partitions not yet backfilled and then ran fine.

Filed an issue for this: https://github.com/dagster-io/dagster/issues/5687