BIP: ??? Layer: Applications Title: Payjoin Version 2: Serverless Payjoin Author: Dan Gould <[email protected]> Status: Draft Replaces: 78 Type: Standards Track Created: 2023-08-08 License: BSD-2-Clause
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
--- a/src/script/interpreter.cpp | |
+++ b/src/script/interpreter.cpp | |
@@ -504,6 +504,14 @@ bool EvalScript(std::vector<std::vector<unsigned char> >& stack, const CScript& | |
return set_error(serror, SCRIPT_ERR_MINIMALDATA); | |
} | |
stack.push_back(vchPushValue); | |
+ if ((flags & SCRIPT_VERIFY_DISCOURAGE_UPGRADABLE_NOPS) && opcode == OP_FALSE) { | |
+ auto pc_tmp = pc; | |
+ opcodetype next_opcode; | |
+ valtype dummy_data; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
""" | |
dependency: pip install embit | |
""" | |
from embit import compact | |
from embit.psbt import PSBT, OutputScope | |
from embit.script import Script | |
class OPCODES: | |
OP_RETURN = 106 | |
OP_PUSHDATA1 = 76 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#cloud-config | |
# This is the user-data configuration file for cloud-init. By default this sets | |
# up an initial user called "ubuntu" with password "ubuntu", which must be | |
# changed at first login. However, many additional actions can be initiated on | |
# first boot from this file. The cloud-init documentation has more details: | |
# | |
# https://cloudinit.readthedocs.io/ | |
# | |
# Some additional examples are provided in comments below the default |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# | |
# This is the ultimate HAProxy 2.0 "Getting Started" config | |
# It demonstrates many of the features available which are now available | |
# While you may not need all of these things, this can serve | |
# as a reference for your own configurations. | |
# | |
# Have questions? Check out our community Slack: | |
# https://slack.haproxy.org/ | |
# |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Generated from the ABNF at <https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#collected.abnf> | |
# using <https://github.com/katef/kgt> | |
Accept: | |
,---------------------------------------------------------------------------------------------------------------------------. | |
| | | |
||--^--v----------------- "," ------------------>--v------------------------------------------------------------------------->-->--|| | |
| | | | | |
| ,-------------------. | | ,-----------------------------------------------. | | |
| | | | | | | | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CREATE TABLE states_raw( | |
d date, | |
uid UInt64, | |
first_name String, | |
last_name String, | |
modification_timestamp_mcs DateTime64(3) default now64(3) | |
) ENGINE = Null; | |
CREATE TABLE final_states_by_month( | |
d date, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DROP TABLE IF EXISTS states_raw; | |
DROP TABLE IF EXISTS final_states_by_day; | |
DROP TABLE IF EXISTS final_states_by_day_mv; | |
CREATE TABLE states_raw | |
( | |
process String, | |
state String, | |
stateint Int64, | |
statevalue Float64, |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
:80 { | |
root /serve | |
} |
This is a slightly stripped down version from our internal bug tracker. The point of posting this publicly is part FYI, part peer review. I'm hoping someone can look at this, disagree, and tell me all the downsides of using the C
locale or point out things I've misunderstood. The Recommendations
section in particular is contextualized by our database serving a SaaS product for users from many different locales, thus making locale a render level concern. YMMV, caveat emptor, etc.
Collation defines the character ordering for textual data. For Postgres, https://www.postgresql.org/docs/current/static/locale.html:
The locale settings influence the following SQL features:
- Sort order in queries using ORDER BY or the standard comparison operators on textual data
- The
upper
,lower
, andinitcap
functions
NewerOlder