brew install docker kubectl helm
You can do this with docker for mac by enabling kubernetes
Make sure to set docker for mac's resources for this demo. Ideally 8GB CPU, and 12GB of Memory.
function unlikeAndScroll() { | |
Array.from(document.querySelectorAll("div[aria-label$='Liked']")).forEach(button => button.click()); | |
console.log('Unliked all visible tweets. Scrolling down...'); | |
// Scroll to the bottom of the page | |
window.scrollTo(0, document.body.scrollHeight); | |
// Wait for more tweets to load and then run again | |
setTimeout(unlikeAndScroll, 3000); // Adjust the time as needed | |
} |
navigator.registerProtocolHandler("mailto", | |
"https://mail.google.com/mail/u/1/?extsrc=mailto&url=%s", | |
"Gmail"); |
import random | |
# note, run with python 3 for utf 8 chars. | |
adjectives = [ | |
"admiring", | |
"adoring", | |
"affectionate", | |
"agitated", | |
"amazing", |
brew install docker kubectl helm
You can do this with docker for mac by enabling kubernetes
Make sure to set docker for mac's resources for this demo. Ideally 8GB CPU, and 12GB of Memory.
progressTracker.setCurrentStep(FINALISATION); | |
// We notarise the transaction and get it recorded in the vault of | |
// the participants of all the transaction's states. | |
SignedTransaction notarisedTx1 = subFlow(new FinalityFlow(fullySignedTx, singleton(counterpartySession), FINALISATION.childProgressTracker())); | |
// We can also choose to send it to additional parties who aren't one | |
// of the state's participants. | |
List<FlowSession> partySessions = Arrays.asList(counterpartySession, initiateFlow(regulator)); | |
SignedTransaction notarisedTx2 = subFlow(new FinalityFlow(fullySignedTx, partySessions, FINALISATION.childProgressTracker())); |
progressTracker.setCurrentStep(SIGS_GATHERING); | |
// The list of parties who need to sign a transaction is dictated | |
// by the transaction's commands. Once we've signed a transaction | |
// ourselves, we can automatically gather the signatures of the | |
// other required signers using ``CollectSignaturesFlow``. | |
// The responder flow will need to call ``SignTransactionFlow``. | |
SignedTransaction fullySignedTx = subFlow(new CollectSignaturesFlow(twiceSignedTx, emptySet(), SIGS_GATHERING.childProgressTracker())); | |
progressTracker.setCurrentStep(VERIFYING_SIGS); |
progressTracker.setCurrentStep(TX_VERIFICATION); | |
// Verifying a transaction will also verify every transaction in | |
// the transaction's dependency chain, which will require | |
// transaction data access on counterparty's node. The | |
// ``SendTransactionFlow`` can be used to automate the sending and | |
// data vending process. The ``SendTransactionFlow`` will listen | |
// for data request until the transaction is resolved and verified | |
// on the other side: | |
subFlow(new SendTransactionFlow(counterpartySession, twiceSignedTx)); |
progressTracker.setCurrentStep(TX_SIGNING); | |
// We finalise the transaction by signing it, | |
// converting it into a ``SignedTransaction``. | |
SignedTransaction onceSignedTx = getServiceHub().signInitialTransaction(txBuilder); | |
// We can also sign the transaction using a different public key: | |
PartyAndCertificate otherIdentity = getServiceHub().getKeyManagementService().freshKeyAndCert(getOurIdentityAndCert(), false); | |
SignedTransaction onceSignedTx2 = getServiceHub().signInitialTransaction(txBuilder, otherIdentity.getOwningKey()); |
progressTracker.setCurrentStep(TX_BUILDING); | |
// If our transaction has input states or a time-window, we must instantiate it with a | |
// notary. | |
TransactionBuilder txBuilder = new TransactionBuilder(specificNotary); | |
// Otherwise, we can choose to instantiate it without one: | |
TransactionBuilder txBuilderNoNotary = new TransactionBuilder(); | |
// We add items to the transaction builder using ``TransactionBuilder.withItems``: |