Hi, Is this the full stack trace? How do you start this pipeline?
Med Vänlig Hälsning / Best Regards <https://lunar.app/> *Matyas Manninger* *Data Engineer Consultant* +46 76 050 6326 m...@lunar.app, lunar.app CVR: DK36982837 On Wed, 7 Dec 2022 at 19:40, Sofia’s World <mmistr...@gmail.com> wrote: > Hello all > i have been writing pipelines with beam , and suddenly my unit tests with > a weird exception > This is a sample pipeline i have that basically does nothing > > key = os.environ['FMPREPKEY'] > > > with TestPipeline() as p: > (p | 'start run_mm' >> beam.Create(['20210101']) > | 'prnt' >> beam.Map(print) > ) > > > and still i am getting the exception below > have i somehow messed up my imports? > > Kind regards > Marco > > > elf = <argparse._ArgumentGroup object at 0x0000014024923A60> > action = _StoreAction(option_strings=['--key'], dest='key', nargs=None, > const=None, default=None, type=None, choices=None, help=None, metavar=None) > conflicting_actions = [('--key', _StoreAction(option_strings=['--key'], > dest='key', nargs=None, const=None, default=None, type=None, choices=None, > help=None, metavar=None))] > > def _handle_conflict_error(self, action, conflicting_actions): > message = ngettext('conflicting option string: %s', > 'conflicting option strings: %s', > len(conflicting_actions)) > conflict_string = ', '.join([option_string > for option_string, action > in conflicting_actions]) > > raise ArgumentError(action, message % conflict_string) > E argparse.ArgumentError: argument --key: conflicting option string: > --key >
