interaction design – Combining single- and multi- select drop-down in one form. How to dismiss the drop-down?

enter image description here

How to dismiss the drop-down in single-select and multi-select cases?

For single-select, the obvious option is to dismiss the drop-down on selection.

For multi-select, drop-down should stay open on selection, and can be dismissed with a button, or clicking outside.

Question: Will it be confusing for people to have two models of interaction side-by-side? What is the best strategy here?

Mind that cost of error ((wrong selection) is small. Nothing is saved, or processed, or launched into the space when option is selected.

Examples from the web are welcome in the comments section.

multi signature – Is there any statistical evidence that 2 of 3 wallets are indeed the most common one?

I read the following statement:

2 of 3 wallets are the most common multi-signature wallets created. In
this case, the wallet requires three signatures, but only two are
needed to authorize a transaction.

Is there any statistical evidence that 2 of 3 wallets are indeed the most common one? Like some graph etc. Any kind of statistical evidence would be good. I want to use this fact in a research paper I am writing. I need some reference to cite.

Thanks.

architecture – Multi Tenancy and container support in Spring Webflow application

I have an application which is quite old (7 years back-2014) but well built using JSF, Spring Webflow and Hibernate. This application is critical as being deployed for 50 separate clients each with different box (with tomcat as web server).

Now I want to change the architecture and move to multi tenancy in web module (JSF, Spring Webflow) i.e. Same web application mutualized for multiple clients with Super Admin module. But in backend will keep one database per client. For this I have decided to choose any one the the below approaches :

Approach 1 : Modify the web module and implement dynamic database routing to load application with multiple datasources and in which client will be able to switch to specific datasource dynamically through web interface.
Challenge – Technical feasibility without impacting the functional part.

Approach 2 : Keep the web module as it is and move to containers with container per datasource and user another super admin interface for client to connect to specific datasource.
Challenge – Orchestration and Will need to maintain authentication and access different apps using SSO or something better.

I want to go for second approach as it would be the one with least functional impact. Need some insight on what would the better approach or if someone have any suggestions w.r.t to Design, JSF or Spring Webflow compatibility with dynamic datasource.

Cannot access Ubuntu in multi boot on laptop with Windows 10 after installing Ubuntu

Before installing Ubuntu on a laptop with Windows 10 I first attempted to install the Raspberry Pi OS. It failed and left this error:

g2ldr.mbr

0xc000007b

file missing or contains errors

I tried repairing the Raspberry Pi OS installation but this made no difference.

Started again by installing Ubuntu. Completed installation, restarted, removed install USB, laptop started and same error as before. Ubuntu was not added to the multi boot menu.

How can I fix the multi boot to run Ubuntu and then fix the Raspberry Pi OS installation from there?

Thank-you.

multi selection – should dual list orientation follow the language direction?

I got this question while working on a “Persian” app. As you may know, dual lists are consisted of 2 lists, where normally in a LTR language, the list on the left includes all the available options and the one on the right includes the ones that the user has selected from the left one. Now here’s my question: If the app’s language is a RTL one, should the order of the lists be reversed, meaning that the list with the available options be placed on the right, and the one with user’s selection on the left?

multi tenant – Unable to create pluggable database on 19c using response file

I am trying to create Pluggable database using response file but it is giving me below error indicating that one of the mandatory parameters is/are missing. Although I have checked it multiple times and don’t see that any mandatory parameter is missing. Below is my response file which I am using.

 dbca -silent -createPluggableDatabase -responseFile /f01/app/oracle/dbca_pdb_creation.rsp
(INS-04008) Invalid combination of arguments passed from command line. One or more mandatory dependent arguments are not passed for the argument: -createPluggableDatabase

I am able to create the database when passing the required parameters directly in command line as below:

dbca -silent -createPluggableDatabase -sourceDB testcdb  -pdbName testpdb2 -createPDBFrom default  -pdbAdminUserName PDBADMIN  -pdbAdminPassword abcd1234

Response file

##############################################################################
##                                                                          ##
##                            DBCA response file                            ##
##                            ------------------                            ##
## Copyright(c) Oracle Corporation 1998,2019. All rights reserved.         ##
##                                                                          ##
## Specify values for the variables listed below to customize               ##
## your installation.                                                       ##
##                                                                          ##
## Each variable is associated with a comment. The comment                  ##
## can help to populate the variables with the appropriate                  ##
## values.                                                                  ##
##                                                                          ##
## IMPORTANT NOTE: This file contains plain text passwords and              ##
## should be secured to have read permission only by oracle user            ##
## or db administrator who owns this installation.                          ##
##############################################################################
#-------------------------------------------------------------------------------
# Do not change the following system generated value. 
#-------------------------------------------------------------------------------

#-----------------------------------------------------------------------------
# GENERAL section is required for all types of database creations.
#-----------------------------------------------------------------------------
(GENERAL)

#-----------------------------------------------------------------------------
# Name          : RESPONSEFILE_VERSION
# Datatype      : String
# Description   : Version of the database to create
# Valid values  : "12.1.0"
# Default value : None
# Mandatory     : Yes
#-----------------------------------------------------------------------------
responseFileVersion=/oracle/assistants/rspfmt_dbca_response_schema_v19.0.0

#-----------------------------------------------------------------------------
# Name          : OPERATION_TYPE
# Datatype      : String
# Description   : Type of operation
# Valid values  : "createDatabase"  "createTemplateFromDB"  "createCloneTemplate"  "deleteDatabase"  "configureDatabase"  "addInstance" (RAC-only)  "deleteInstance" (RAC-only)  "createPluggableDatabase"  "unplugDatabase"  "deletePluggableDatabase"  "configurePluggableDatabase"
# Default value : None
# Mandatory     : Yes
#-----------------------------------------------------------------------------
OPERATION_TYPE = "createPluggableDatabase"

#-----------------------*** End of GENERAL section ***------------------------

#----------------------------------------------------------------------------------
# CREATEPLUGGABLEDATABASE section is used when OPERATION_TYPE is defined as "createPluggableDatabase". 
#----------------------------------------------------------------------------------
(CREATEPLUGGABLEDATABASE)
#----------------------------------------------------------------------------------
# Name          : SOURCEDB
# Datatype      : String
# Description   : The source database is the SID 
#     This database must be local and on the same ORACLE_HOME.
# Default value : none
# Mandatory     : YES
#-----------------------------------------------------------------------------
SOURCEDB = "testcdb"

#----------------------------------------------------------------------------------
# Name          : PDBNAME
# Datatype      : String
# Description   : The name of new pluggable database 
#     This pdb name must not be same as sourcedb name.
# Default value : none
# Mandatory     : YES
#-----------------------------------------------------------------------------
PDBNAME = "testpdb2"

#----------------------------------------------------------------------------------
# Name          : CREATEASCLONE
# Datatype      : Boolean
# Description   : specify true or false for PDB to be create as Clone.
#               : When "true" is passed a new PDB GUID is generated for the plugged in PDB
# Default value : true
# Mandatory     : NO
#-----------------------------------------------------------------------------
CREATEASCLONE = "TRUE"

#----------------------------------------------------------------------------------
# Name          : CREATEPDBFROM
# Datatype      : String
# Description   : specify the source of pdb to be plugged
# Valid values  : DEFAULT | FILEARCHIVE | RMANBACKUP | USINGXML
# Default value : DEFAULT
# Mandatory     : NO
#-----------------------------------------------------------------------------
CREATEPDBFROM = "DEFAULT"
 
 
#----------------------------------------------------------------------------------
# Name          : PDBADMINUSERNAME
# Datatype      : String
# Description   : PDB Administrator user name
# Default value : None
# Mandatory     : Mandatory only when creating new DEFAULT PDB
#-----------------------------------------------------------------------------
PDBADMINUSERNAME = "PDBADMIN"

#----------------------------------------------------------------------------------
# Name          : PDBADMINPASSWORD
# Datatype      : String
# Description   : PDB Administrator user password
# Default value : None
# Mandatory     : Mandatory only when creating new DEFAULT PDB
#-----------------------------------------------------------------------------
PDBADMINPASSWORD = "abcd1234"

#-----------------------*** End of createPluggableDatabase section ***------------------------

Please help.

multi signature – Output Descriptor for an Arbitrary Script

Can output descriptors be used to describe an arbitrary script?

Say I had a script something like the following:

OP_IF
  1737417600 OP_CHECKLOCKTIMEVERIFY OP_DROP OP_DUP OP_HASH160 <pubKeyHashD> OP_EQUALVERIFY OP_CHECKSIG
OP_ELSE
  2 <PubKeyA> <PubKeyB> <PubKeyC> 3 OP_CHECKMULTISIG
OP_ENDIF

That’s a two-branch script that either allows a 2-of-3 multisig or a single-address retrieval after a set amount of time. Is there a way to convert that into descriptor that I could then use to derive addresses?

wsh seems focused on set types of scripts, while trying raw on a 32-bit hash of a script gives me Descriptor does not have a corresponding address.