Skip to content

Problem: send function has a deprecation warning in the driver#2547

Merged
ttmc merged 1 commit intobigchaindb:masterfrom
codegeschrei:send-deprecated
Sep 20, 2018
Merged

Problem: send function has a deprecation warning in the driver#2547
ttmc merged 1 commit intobigchaindb:masterfrom
codegeschrei:send-deprecated

Conversation

@codegeschrei
Copy link
Copy Markdown
Contributor

Solution: replace send with the matching new functions

As you might have noticed when running the test, the driver has a deprecation warning for the send() function to send a transaction. We use it in the acceptance tests. Since we want to remove the send() in the next driver release, I'm preparing the server for the changes.

Solution: replace send with the matching new functions
@ttmc
Copy link
Copy Markdown
Contributor

ttmc commented Sep 17, 2018

@codegeschrei I guess you did a search for all "send(" strings, or something like that?

@codegeschrei
Copy link
Copy Markdown
Contributor Author

@ttmc I went through the files of the acceptance tests and searched for send
Did I miss one?

@codecov-io
Copy link
Copy Markdown

Codecov Report

Merging #2547 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2547   +/-   ##
=======================================
  Coverage   93.67%   93.67%           
=======================================
  Files          44       44           
  Lines        2593     2593           
=======================================
  Hits         2429     2429           
  Misses        164      164


# Now she is ready to send it to the BigchainDB Network.
sent_transfer_tx = bdb.transactions.send(fulfilled_creation_tx)
sent_transfer_tx = bdb.transactions.send_commit(fulfilled_creation_tx)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When this acceptance test was created, what was the default mode for send()? Was it commit or async?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't look it up. We always upgraded the driver version for the acceptance tests when a new one was available, so they were run with commit as default most of the time, if not all the time. But I think we had the tests after we switched the default in the driver from async to commit.
Since it is a simple test case it also makes sense to use commit

@ttmc ttmc requested a review from z-bowen September 17, 2018 10:40
Copy link
Copy Markdown
Contributor

@muawiakh muawiakh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ttmc ttmc merged commit 407571d into bigchaindb:master Sep 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants