--rev-version flag is broken
See original GitHub issueI am using version 0.8.3 of tfx. When using the command tfx extension create --rev-version
, I get the following error message:
error: TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received an instance of Inplace
It looks like it is an error with the json parsing and writing.
I’m happy to take a look and find a fix.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Failed Bear Flag: What Is It & How to Trade Them - YouTube
Key moments. View all · Reversal from a Broken Bear Flag · Reversal from a Broken Bear Flag · Reversal from a Broken...
Read more >How to Properly Dispose of Worn-Out US Flags
According to the resolution, "The approved method of disposing of unserviceable flags has long been that they be destroyed by burning." The U.S ......
Read more >Bull Flag Chart Pattern & Trading Strategies
A Bull Flag chart pattern happens when a stock is in a strong uptrend but then has a slight consolidation period before continuing...
Read more >Bug#469770: python2.5: Old shelve files broken by DB4.6 reversion
Bug#469770: python2.5: Old shelve files broken by DB4.6 reversion. 18 views ... return DbfilenameShelf(filename, flag, protocol, writeback, binary)
Read more >squashed migration broke django-reversion upgrade. #559
Issue: Django version: 1.9.7 django-reversion version: 2.0.5 I was using ... We run migrations on each database with the --database flag.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in 0.9.0, thanks for the PR, @xinyi-joffre
This error only occurs in node v14.x or above