alpacahq / alpacahq/alpaca-py

[Bug]: assigning a "client_order_id" does not work on MarketOrderRequest

Offen
#186 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
1.5k
Forks
398
Ø Merge
1 T. 16 Std.
Gemergte PRs (30 T.)
6

Beschreibung

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

When I order a `MarketOrderRequest` with `client_order_id`, it seems to be ignored.
Im using Bracket order with stop loss and take profit
```
order_request = MarketOrderRequest(symbol=ticker,
side=api_action,
type=OrderType.STOP,
qty=stock_quantity,
time_in_force=TimeInForce.DAY,
order_class=OrderClass.BRACKET,
take_profit=take_profit_request,
stop_loss=stop_loss_request,
client_order_id=client_order_id)
```

the client_order_id that is actually assigned to the order is a default one and my client_order_id is ignored.

### Expected Behavior

client_order_id is assigned as the user wishes

### SDK Version I encountered this issue in

0.6.1

### Steps To Reproduce

```markdown
order a MarketOrderRequest with client_order_id.
Im pretty sure its not related to the stops I assigned but whatever.
```

### Filled out the Steps to Reproduce section?

- [X] I have entered valid steps to reproduce my issue or have attached a minimally reproducible case in code that shows my issue happening; and understand that without this my issue will be flagged as invalid and closed after 30 days.

### Anything else?

I'm seeing it does not work in the older api as well. So do whatever you want to do with it.

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.