Sweet Free Stuff
///////////////////////////////////////////
Two Free Bass Barn Stickers
Posted: 29 Jul 2013 11:39 AM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/ymEQJM_Rhwk/?utm_source=feedburner&utm_medium=email
Complete the form and enter striped bass for the answer to the security
question to get your free stickers. Get it for Free!
///////////////////////////////////////////
Free Dozen Eggs at Meijer
Posted: 29 Jul 2013 11:34 AM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/UC5yK2U8wRc/?utm_source=feedburner&utm_medium=email
Were giving away a free dozen eggs to mPerks users who enter the offer code
FreeEggs and clip the coupon! Get it for Free!
///////////////////////////////////////////
Free Book: The Greatest Story Ever Told
Posted: 29 Jul 2013 03:49 AM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/YXN8HKrEHzk/?utm_source=feedburner&utm_medium=email
From Genesis to Revelation, a story unfolds that begins and ends in
paradise—the greatest story ever told from the timeless pages of the Bible.
With fresh perspective and imagination, Mart De Haan takes you on a journey
through the Old and New Testaments to retell the story of God’s vision for
mankind. Get it for […]
///////////////////////////////////////////
Free Bronx Zoo Dinosaur Safari Stickers
Posted: 29 Jul 2013 03:43 AM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/DujBJ0Kg9ac/?utm_source=feedburner&utm_medium=email
Get it for Free!
///////////////////////////////////////////
Free Subscription to Click Magazine
Posted: 29 Jul 2013 03:40 AM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/7wAhRcnygGk/?utm_source=feedburner&utm_medium=email
Get it for Free!
///////////////////////////////////////////
Earn Cash and Prizes for Scanning Purchases - NCP
Posted: 29 Jul 2013 01:00 AM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/qos-M-mPM7c/?utm_source=feedburner&utm_medium=email
As a panel member, the National Consumer Panel will provide you with a
hand-held scanner. Every time you or members of your household shop, youll
use the scanner to scan the barcodes on all of your purchases. Then, once a
week, youll send us your purchase information. Its as easy as that! Youll
earn gift […]
///////////////////////////////////////////
Free Sample of Nature Made Vitamelts
Posted: 28 Jul 2013 11:00 PM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/dZm19s7_nz8/?utm_source=feedburner&utm_medium=email
Get it for Free!
///////////////////////////////////////////
Free Sample of Minties Dog Treats (Sams Club Members)
Posted: 28 Jul 2013 10:00 PM PDT
http://feedproxy.google.com/&;r/SweetFreeStuff/&;3/v6h0UdaARzQ/?utm_source=feedburner&utm_medium=email
Watch the video, then sample link will appear. It is for one medium sized
bone. Requires a Sams Club membership number. Get it for Free!


Telemed electronic stethoscope 3rd generation
Upgrade your license
Standard
-
On demand technical support
-
First time installation byour experts
-
Device software updates
-
Repairing malfunctioned parts
-
Device replacement
-
Priority support
-
Device monthly checkup
Already covered
Exxemtial
-
On demand technical support
-
First time installation byour experts
-
Device software updates
-
Repairing malfunctioned parts
-
Device replacement
-
Priority support
-
Device monthly checkup
Already covered
Premium
-
On demand technical support
-
First time installation byour experts
-
Device software updates
-
Repairing malfunctioned parts
-
Device replacement
-
Priority support
-
Device monthly checkup
12,000 EGP / Year


Desc. {{desc}}
This beer has an abv. of: {{beers.abv}}
This beer has an ibu. of: {{beers.ibu}}
This beer is Organic? (Y/N): {{beers.isOrganic}}
Beer name is required.


1 Some of the Egyptians consider crocodiles sacred; others do not, but treat them as enemies. Those who live near Thebes and lake Moeris consider them very sacred.
2 Every household raises one crocodile, trained to be tame; they put ornaments of glass and gold on its ears and bracelets on its forefeet, provide special food and offerings for it, and give the creatures the best of treatment while they live; after death, the crocodiles are embalmed and buried in sacred coffins.
3 But around Elephantine they are not held sacred, and are even eaten. The Egyptians do not call them crocodiles, but khampsae. The Ionians named them crocodiles, from their resemblance to the lizards which they have in their walls.


PART I. HOME LOANS FOR LOW INCOME
HOME BUYERS ON STATE LAND
Note
Part heading amended by L 1971, c 192, §2.
§207-1 Authorization for loans. The director of finance may grant loans as provided for in this part to persons leasing or purchasing state lands for their personal residential needs. Loans may be granted only to eligible persons as provided for in this part who occupy state land by virtue of leases or agreements of sale executed after July13, 1961. [L 1961, c 194, §2; am L 1963, c 114, §1; Supp, §98L-2; HRS §207-1]
Cross References
Disaster relief commercial loans, see chapter 209, part III.
Public lands for natural disaster victims, see chapter 171, part IIIC.
Residential development by State, see chapter 206.


CSE 555: Computational Geometry
Project: Finding Minimum weight optimal triangulation of simple polygons using Dynamic Programming
Draw a simple closed polygon using mouse click (as vertices) and close the polygon


Pair experience
Learning from others
March 29, 2015
Pair sessions are definitely being one of the most interesting parts of Phase 0. It's been a very rewarding experience to me. First of all reasons, it's a cultural experience. Since I'm not American, I've been having the chance to experience a little of american's culture through these interactions. And, so far, it seems to me that this group that I'm interacting with is very darting. And this attitude (I honestly don't know why) seems to be undervalued around here. That all said, whenever I'm pairing, I always feel that I have so much to learn from my pair (and sometimes, that makes me feel that I can't contribute to my pair as much as he/she does).
And then, there's feedback. I'm not that used to feedback so much, and it's been challenging. Feedback dashboard has helped me a lot on that. I had very different evaluations for the first 3 feedbacks I gave, and having the chance to see what others evaluated as being good and bad feedback, I've drawn a strategy to all feedbacks I give: I always highlight things that my pair did that he/she should keep doing and things that he/she could improve for future sessions. This is how I managed to give specific and actionable feedback: even when I don't have anything contructive to say, I try to specifically highlight what pleased me about my pair.
There's also the feedback that I get. I have this constant seek for perfectionism, so I always want to read that all and desperately think of how I can improve and go beyond. And I'm not only perfectionist, but I'm also the kind of person who seeks for approval. So, whenever there's new feedback for me, I just wish I didn't disappoint my partner. I think that's my biggest vulnerability when it comes to those pair interactions and feedbacks. At least so far, I think it all worked very well and I've been having wonderful experiences. I hope it keeps being this delightful!


My Thinking Style
Sunday, October 5th, 2014
In this blog entry I've been tasked with researching my Gregorc thinking style. The quiz groups everyone into one of 4 thinking styles such as Concrete Sequential, Abstract Sequential, Abstract Random or Concrete Random. After taking the quiz a few times, I found that I am equally Abstract Sequential as Concrete Random. Now if you're asking how can one have equal traits in all 4 of the options, well I'm with you. After doing some research, I realized that they are both similar and describe me pretty accurately.
The following is the summary of Gregorc's findings. In the thinking styles there are two perceptual qualities, Concrete and Abstract. Concrete is something you can sense and is tangible. Abstract is something thought up and visualized. Gregorc also groups everyone into two ordering abilities, Sequential and Random. Sequential allows one to order everything in a linear fashion through step by step while random allows your mind to organize information into chunks where tackling the information is in no particular linear order.
Not only is it important to understand other people's thinking styles but understanding one's own thinking style is also very important. This will help you work with teams, understand how you learn and how you don't so you can maximize your learning.
After researching my thinking style I learned that Abstract Sequential thinkers are described by Gregorc as the following:
Abstract Sequential learners like:
- his/her point to be heard
- analyzing situations before making a decision or acting
- applying logic in solving or finding solutions to problems
They learn best when:
- they have access to experts or references
- placed in stimulating environments
- able to work alone
What's hard for them?
- Being forced to work with those of differing views
- Too little time to deal with a subject thoroughly
- Repeating the same tasks over and over
- Lots of specific rules and regulations
- "sentimental" thinking
- Expressing their emotions
- Being diplomatic when convincing others
- Not monopolizing a conversation
Concrete Random learners like:
- experimenting to find answers
- take risks
- use their intuition
- solving problems independently
They learn best when:
- they are able to use trial-and-error approaches
- able to compete with others
- given the opportunity to work through the problems by themselves.
What's hard for them?
- Restrictions and limitations
- Formal reports
- Routines
- Re-doing anything once it’s done
- Keeping detailed records
- Showing how they got an answer
- Choosing only one answer
- Having no options
While my thinking style is described as the above I also think I can learn from what I am not.
Concrete Sequential learners like:
- order
- logical sequence
- following directions, predictability
- getting facts
They learn best when:
- they have a structured environment
- they can rely on others to complete this task
- are faced with predictable situations
- can apply ideas in pragmatic ways
What's hard for them?
- Working in groups
- Discussions that seem to have no specific point
- Working in an unorganized environment
- Following incomplete or unclear directions
- Working with unpredictable people
- Dealing with abstract ideas
- Demands to "use your imagination"
- Questions with no right or wrong answers
Abstract Random learners like:
- to listen to others
- bringing harmony to group situations
- establishing healthy relationships with others
- focusing on the issues at hand
They learn best when:
- in a personalized environment
- given broad or general guidelines
- able to maintain friendly relationships
- able to participate in group activities
What's hard for them?
- Having to explain or justify feelings
- Competition
- Working with dictatorial/authoritarian personalities
- Working in a restrictive environment
- Working with people who don’t seem friendly
- Concentrating on one thing at a time
- Giving exact details
- Accepting even positive criticism
How do you think? Take the quiz yourself here.


UKCloud Limited (“UKC”) and Virtual Infrastructure Group Limited (“VIG”) (together “the Companies”) – in Compulsory Liquidation
On 25 October 2022, the Companies were placed into Liquidation with the Official Receiver appointed as Liquidator and J Robinson and A M Hudson simultaneously appointed as Special Managers to manage the liquidation process on behalf of the Official Receiver.
Further information regarding the Liquidations can be found here: https://www.gov.uk/government/news/virtual-infrastructure-group-limited-and-ukcloud-limited-information-for-creditors-and-interested-parties
Contact details:
For any general queries relating to the Liquidations please email<EMAIL_ADDRESS>For customer related queries please email<EMAIL_ADDRESS>For supplier related queries please email<EMAIL_ADDRESS>How to view your VMs in the UKCloud Portal
Overview
The My VMs page in the UKCloud Portal enables you to see, at a glance, the services currently operational within your environment, including virtual machines (VMs) and vApps.
Accessing the My VMs page
To go to the My VMs page:
If necessary, switch to the account that you want to work in.
In the Portal navigation panel, expand VMware Cloud and then select the compute service with which you want to work.
Select the My VMs tab.
From the Currently viewing for VDC list, select the virtual data centre (VDC) you want to work with to see its settings.
Viewing information about vApps
The vApps tab shows a list of the vApps within the selected VDC. The information displayed includes the number of VMs within the vApp.
On the My VMs page, select the vApps tab.
Click a vApp name to view additional information about that vApp in the Info tab.
Select the VMs tab to see a list of the VMs within the selected vApp and their properties.
One useful property that you can see is the backup status.
In the example above, there is no backup policy for this VM so the backup icon is greyed out. If backups are successful there will be a green icon, if backups have failed there will be a red icon.
If you need to manage your backups for a VM, click the Manage button. For more information, see How to manage Snapshot Protection for your VMs.
Click a VM name to see additional information about it, including backup logs.
Viewing information about VMs
The VMs tab displays a list of all VMs within the selected VDC.
On the My VMs tab, select the VMs tab.
Click a VM to view its additional properties, including backup logs.
Viewing Snapshot Protection information
The Snapshot Protection tab enables you to specify a snapshot retention policy to apply to all the VMs in a VDC. You can apply the policy to all new VMs or to all new and existing VMs.
For more information about Snapshot Protection, see How to manage Snapshot Protection for your VMs.
Feedback
If you find a problem with this article, click Improve this Doc to make the change yourself or raise an issue in GitHub. If you have an idea for how we could improve any of our services, send an email to feedback@ukcloud.com.


The following is an example of how FileInputFlash act's with the same APIs as FileInputOverlay, so you can build your own file input. For the file to actually upload, you'll need to have PHP enabled.


Name:
{{profile.firstName + " " + profile.lastName}}
Email:
{{profile.Email}}
Mobile:
{{profile.Mobile}}
Address:
{{profile.address.street_address}}
{{profile.address.city + ", " + profile.address.state + " " + profile.address.pincode}}
{{profile.address.country}}


{% extends "layout.html" %} {% block body %}
Please upload the .fasta or .txt file you would like to analyze and your email address to get an email after run completion (if not immediate).


File
Load model
Clear models
Setup screens...
VR viewer setup...
Edit
Add cut plane
WASD + Mouse movement
View
Fullscreen
Zoom all
Visual quality show low
Background...
Framerate show
Exit fullscreen
×
Setup Screen Sizes
Unintentionaly left blank
×
VR Viewer Cardboard Setup
Background Color


--- title: Photo Highlights from Namibia date: 2012-06-30 comments: true layout: post categories: - namibia ref_url: http://www.flickr.com/photos/bonelake/sets/72157630353231870/ ---
Well, its really hard to pick out the photo highlights from this trip, but I decided to take a quick stab at it during my hour at the internet cafe today. So, here's a link to the flickr photoset. Hope you like it.


|
|||||||||||
| PREV NEXT | FRAMES NO FRAMES |
| Packages that use Lease | |
| com.sun.jini.landlord | This is a utility for services implementing leases. |
| com.sun.jini.lease | Some basic utility classes for helping with client-side lease renewal operations. |
| net.jini.core.event | The RemoteEventListener interface and related standard classes. |
| net.jini.core.lease | These are distributed leasing interfaces and classes. |
| net.jini.core.lookup | These are the lookup service interfaces and classes. |
| net.jini.core.transaction | These are the transaction abstraction's interfaces and classes. |
| net.jini.core.transaction.server | These are the default transaction semantics for participant/manager interaction. |
| net.jini.discovery | These are utility classes and interfaces that conform to the discovery and join protocol defined in the Jini(TM) Discovery and Join Specification. |
| net.jini.event | |
| net.jini.lease | Standard service and utility classes for managing leases. |
| net.jini.space | JavaSpaces(TM) servers provide a place on the network, a space, for clients to store and exchange objects. |
| Uses of Lease in com.sun.jini.landlord |
| Classes in com.sun.jini.landlord that implement Lease | |
class |
ConstrainableLandlordLease
Constrainable sub-class of LandlordLease .
|
class |
LandlordLease
Basic implementation of net.jini.core.lease.Lease that works
with the the Landlord protocol. |
| Methods in com.sun.jini.landlord with parameters of type Lease | |
boolean |
LandlordLease.canBatch(Lease lease)
|
boolean |
ConstrainableLandlordLease.canBatch(Lease lease)
|
| Uses of Lease in com.sun.jini.lease |
| Classes in com.sun.jini.lease that implement Lease | |
class |
AbstractLease
A base class for implementing lease objects. |
| Methods in com.sun.jini.lease that return Lease | |
Lease |
BasicRenewalFailureEvent.getLease()
Returns the lease that could not be renewed. |
| Constructors in com.sun.jini.lease with parameters of type Lease | |
AbstractLeaseMap(Lease lease,
long duration)
Default to using a small HashMap. |
|
AbstractLeaseMap(Map map,
Lease lease,
long duration)
Provide a map of your choice. |
| Uses of Lease in net.jini.core.event |
| Fields in net.jini.core.event declared as Lease | |
protected Lease |
EventRegistration.lease
The registration lease. |
| Methods in net.jini.core.event that return Lease | |
Lease |
EventRegistration.getLease()
Returns the Lease object for this registration. |
| Constructors in net.jini.core.event with parameters of type Lease | |
EventRegistration(long eventID,
Object source,
Lease lease,
long seqNum)
Constructs an EventRegistration object. |
| Uses of Lease in net.jini.core.lease |
| Methods in net.jini.core.lease with parameters of type Lease | |
boolean |
Lease.canBatch(Lease lease)
Returns a boolean indicating whether or not the lease given as a parameter can be batched (placed in the same LeaseMap) with the current lease. |
| Uses of Lease in net.jini.core.lookup |
| Methods in net.jini.core.lookup that return Lease | |
Lease |
ServiceRegistration.getLease()
Returns the lease that controls the service registration, allowing the lease to be renewed or cancelled. |
| Uses of Lease in net.jini.core.transaction |
| Fields in net.jini.core.transaction declared as Lease | |
Lease |
NestableTransaction.Created.lease
The lease. |
Lease |
Transaction.Created.lease
The lease. |
| Constructors in net.jini.core.transaction with parameters of type Lease | |
NestableTransaction.Created(NestableTransaction transaction,
Lease lease)
Simple constructor. |
|
Transaction.Created(Transaction transaction,
Lease lease)
Simple constructor. |
| Uses of Lease in net.jini.core.transaction.server |
| Fields in net.jini.core.transaction.server declared as Lease | |
Lease |
TransactionManager.Created.lease
The lease. |
| Constructors in net.jini.core.transaction.server with parameters of type Lease | |
TransactionManager.Created(long id,
Lease lease)
Simple constructor. |
| Uses of Lease in net.jini.discovery |
| Methods in net.jini.discovery that return Lease | |
Lease |
LookupDiscoveryRegistration.getLease()
Returns the Lease object that controls a client's registration with the lookup discovery service. |
| Uses of Lease in net.jini.event |
| Methods in net.jini.event that return Lease | |
Lease |
MailboxRegistration.getLease()
Returns the Lease object associated
with this registration. |
| Uses of Lease in net.jini.lease |
| Methods in net.jini.lease that return Lease | |
Lease |
ExpirationWarningEvent.getRenewalSetLease()
Convenience method to retrieve the Lease associated
with the source of this event. |
Lease[] |
LeaseUnmarshalException.getLeases()
Accessor method that returns an array consisting of instances of Lease , where each element of the array corresponds
to a successfully unmarshalled object. |
Lease |
LeaseRenewalSet.remove(Lease leaseToRemove)
Removes the specified lease from set. |
Lease[] |
LeaseRenewalSet.getLeases()
Returns all the leases currently in the set. |
Lease |
LeaseRenewalSet.getRenewalSetLease()
Returns the lease that controls the lifetime of this set. |
abstract Lease |
RenewalFailureEvent.getLease()
Returns the lease that could not be renewed. |
Lease |
LeaseRenewalEvent.getLease()
Returns a reference to the lease to which the event pertains. |
| Methods in net.jini.lease with parameters of type Lease | |
void |
LeaseRenewalSet.renewFor(Lease leaseToRenew,
long desiredDuration,
long renewDuration)
Include a client lease in the set for a specified duration and with a specified renewal duration. |
void |
LeaseRenewalSet.renewFor(Lease leaseToRenew,
long desiredDuration)
Include a client lease in the set for a specified duration. |
Lease |
LeaseRenewalSet.remove(Lease leaseToRemove)
Removes the specified lease from set. |
void |
LeaseRenewalManager.renewUntil(Lease lease,
long desiredExpiration,
LeaseListener listener)
Include a lease in the managed set until a specified time. |
void |
LeaseRenewalManager.renewUntil(Lease lease,
long desiredExpiration,
long renewDuration,
LeaseListener listener)
Include a lease in the managed set until a specified time and with a specified renewal duration. |
void |
LeaseRenewalManager.renewFor(Lease lease,
long desiredDuration,
LeaseListener listener)
Include a lease in the managed set for a specified duration. |
void |
LeaseRenewalManager.renewFor(Lease lease,
long desiredDuration,
long renewDuration,
LeaseListener listener)
Include a lease in the managed set for a specified duration and with specified renewal duration. |
long |
LeaseRenewalManager.getExpiration(Lease lease)
Returns the current desired expiration time associated with a particular lease, (not the actual expiration that was granted when the lease was created or last renewed). |
void |
LeaseRenewalManager.setExpiration(Lease lease,
long expiration)
Replaces the current desired expiration of a given lease from the managed set with a new desired expiration time. |
void |
LeaseRenewalManager.cancel(Lease lease)
Removes a given lease from the managed set, and cancels it. |
void |
LeaseRenewalManager.remove(Lease lease)
Removes a given lease from the managed set of leases; but does not cancel the given lease. |
| Constructors in net.jini.lease with parameters of type Lease | |
LeaseUnmarshalException(String message,
Lease[] leases,
MarshalledObject[] marshalledLeases,
Throwable[] exceptions)
Constructs a new instance of LeaseUnmarshalException
with a specified message. |
|
LeaseUnmarshalException(Lease[] leases,
MarshalledObject[] marshalledLeases,
Throwable[] exceptions)
Constructs a new instance of LeaseUnmarshalException . |
|
LeaseRenewalEvent(LeaseRenewalManager source,
Lease lease,
long expiration,
Throwable ex)
Constructs an instance of this class with the specified state. |
|
LeaseRenewalManager(Lease lease,
long desiredExpiration,
LeaseListener listener)
Constructs an instance of this class that will initially manage a single lease. |
| Uses of Lease in net.jini.space |
| Methods in net.jini.space that return Lease | |
Lease |
MatchSet.getLease()
Returns a proxy to the Lease associated with this
match set, or null if this match set is not
leased. |
Lease |
JavaSpace.write(Entry entry,
Transaction txn,
long lease)
Write a new entry into the space. |
|
|||||||||||
| PREV NEXT | FRAMES NO FRAMES |


TABLE OF INTERACTIONS WITH
MIDAZOLAM
See also: benzodiazepines and related
See also: sedative medications
See also: substrates at risk of CYP3A4
From the French ANSM drug interactions document of
September 2016, pp. 155-156
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
ANTICONVULSANT ENZYMATIC INDUCERS CLASS CODE: N03A-001 |
Risk of decrease of the plasma concentrations of the midazolam by the anticonvulsant |
Take into account |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
DILTIAZEM RxNorm: 3443 ATC: C08DB01 |
Increase of the plasma concentrations of midazolam due to decrease of its hepatic metabolism, with increase of sedation |
Precaution for use Clinical monitoring and reduction of the dosage during the treatment with the diltiazem |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
FLUCONAZOLE RxNorm: 4450 ATC: D01AC15 J02AC01 |
Increase of the plasma concentrations of midazolam due to reduction of its hepatic metabolism, with increase of sedation |
Not recommended --with the midazolam by mouth Precaution for use --with the midazolam via IV and sublingual Clinical monitoring and reduction of the dosage of midazolam in case of treatment with the fluconazole |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
STRONG INHIBITORS OF CYP3A4 CLASS CODE: J02-J05 |
Increase of the plasma concentrations of midazolam due to decrease of its hepatic metabolism, with increase of sedation |
Not recommended: --with the midazolam by mouth Precaution for use: --with the midazolam via IV and sublingual Clinical monitoring and reduction of the dosage of the midazolam in the case of treatment with the inhibitor |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
ST JOHNS WORT Hypericum perforatum RxNorm: 258326 ATC: not found |
Risk of decrease of the plasma concentrations of midazolam by the St Johns wort |
Take into account |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
OMBITASVIR + PARITAPREVIR CLASS CODE: OMPA |
Increase of the plasma concentrations of the midazolam due to decrease of its hepatic metabolism by the ombitasvir+ paritaprevir |
CONTRAINDICATION |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
RIFAMPICIN RxNorm: 9384 ATC: J04AB02 |
Risk of absence of effect of the midazolam, with very large decrease of its plasma concentrations, due to increase of its hepatic metabolism |
Not recommended |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
ROXITHROMYCIN RxNorm: 9478 ATC: J01FA06 |
Slight increase of sedation |
Take into account |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
STIRIPENTOL RxNorm: 37119 ATC: N03AX17 |
Increase of the plasma concentrations of the midazolam due to decrease of its hepatic metabolism with increase of sedation |
Precaution for use Clinical monitoring and reduction of the dosage during the treatment with the stiripentol. |
MIDAZOLAM RxNorm: 6960 ATC: N05CD08 |
VERAPAMIL RxNorm: 11170 ATC: C08DA01 |
Increase of the plasma concentrations of midazolam (decrease of its hepatic metabolism with increase of sedation) |
Precaution for use Clinical monitoring and reduction of the dosage of midazolam during the treatment with the verapamil. |


'You ought to be ashamed of yourself for asking such a simple question,' added the Gryphon; and then they both sat silent and looked at poor Alice, who felt ready to sink into the earth. At last the Gryphon said to the Mock Turtle, 'Drive on, old fellow! Don't be all day about it!' and he went on in these words: 'Yes, we went to school in the sea, though you mayn't believe it—' 'I never said I didn't!' interrupted Alice. 'You did,' said the Mock Turtle.
Lorem Ipsum is simply dummy text of the pr make but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.
15 Minutes Ago
- Copyright @AskMe 2019 -


X-Road: System Parameters User Guide
Version: 2.20
Doc. ID: UG-SYSPAR
| Date | Version | Description | Author |
|---|---|---|---|
| 29.05.2015 | 1.0 | First draft | Siim Annuk |
| 01.06.2015 | 1.1 | Some corrections done, typos fixed | Siim Annuk |
| 30.06.2015 | 1.2 | Minor corrections done | Vello Hansen, Imbi Nõgisto |
| 26.08.2015 | 1.3 | Corrections regarding SQL done | Marju Ignatjeva |
| 09.09.2015 | 2.0 | Editorial changes made | Imbi Nõgisto |
| 11.09.2015 | 2.1 | Global configuration generation interval added | Martin Lind |
| 20.09.2015 | 2.2 | Editorial changes made | Imbi Nõgisto |
| 23.09.2015 | 2.3 | Warning added about changing system parameters | Siim Annuk |
| 24.09.2015 | 2.4 | Note added about setting the timeStampingIntervalSeconds system parameter | Siim Annuk |
| 07.10.2015 | 2.5 | Default value of the parameter acceptable-timestamp-failure-period set to 14400 | Kristo Heero |
| 08.12.2015 | 2.6 | New parameters for configuring signature algorithms and key length, proxy client-side TLS protocols, and software token pin policy | Jarkko Hyöty |
| 08.12.2015 | 2.7 | Added parameters for toggling SOAP body logging on/off | Janne Mattila |
| 17.12.2015 | 2.8 | Added monitoring parameters | Ilkka Seppälä |
| 28.1.2016 | 2.9 | Added configuration client admin port | Ilkka Seppälä |
| 04.10.2016 | 2.10 | Converted to markdown format | Sami Kallio |
| 05.10.2016 | 2.11 | Added options for proxy client and server connections. Clarified client-timeout option. | Olli Lindgren |
| 02.11.2016 | 2.12 | Fix ocspFreshnessSeconds description in system parameters document | Ilkka Seppälä |
| 01.12.2017 | 2.13 | Added documentation for minimum global conf version | Sami Kallio |
| 20.01.2017 | 2.14 | Added license text and version history | Sami Kallio |
| 08.02.2017 | 2.15 | Updated documentation with new environmental monitoring parameters describing sensor intervals | Sami Kallio |
| 23.02.2017 | 2.16 | Added documentation for OCSP-response retrieval deactivation parameter | Tatu Repo |
| 03.03.2017 | 2.17 | Added new parameter jetty-ocsp-responder-configuration-file | Kristo Heero |
| 07.03.2017 | 2.18 | Added new parameters ocsp-responder-client-connect-timeout and ocsp-responder-client-read-timeout | Kristo Heero |
| 11.04.2017 | 2.19 | Changed default values of the proxy parameter client-timeout to 30000, client-use-fastest-connecting-ssl-socket-autoclose and client-use-idle-connection-monitor to true. Added new messagelog parameters timestamper-client-connect-timeout and timestamper-client-read-timeout. Changed default value of the proxy parameter pool-validate-connections-after-inactivity-of-millis to 2000. | Kristo Heero |
| 06.06.2017 | 2.20 | Removed parameter default-signature-algorithm, replaced parameters csr-signature-algorithm with csr-signature-digest-algorithm, signature-algorithm-id with signature-digest-algorithm-id, and confSignAlgoId with confSignDigestAlgoId. Added new proxy-ui parameter auth-cert-reg-signature-digest-algorithm-id. | Kristo Heero |
Table of Contents
- Introduction
- Changing the System Parameter Values
- Security Server System Parameters
- Central Server System Parameters
- Configuration Proxy System Parameters
License
This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.
Introduction
This document describes the system parameters of the X-Road components – of the security server, the central server and the configuration proxy. Additionally, changing the default values of the system parameters are explained.
References
-
[INI] INI file, http://en.wikipedia.org/wiki/INI_file
-
[CRON] Quartz Scheduler CRON expression, http://www.quartz-scheduler.org/documentation/quartz-2.1.x/tutorials/crontrigger.html
Changing the System Parameter Values
The system parameters specify various characteristics of the system, such as port numbers, timeouts and paths to files on disk. The system parameters of the X-Road components are mainly stored in configuration files. Additionally, X-Road central server stores some system parameters in the database.
Changing the values of the system parameters is strongly discouraged, since it may cause unexpected system behaviour.
Changing the System Parameter Values in Configuration Files
The configuration files are INI files [INI], where each section contains parameters for a particular server component.
In order to override the default values of system parameters, create or edit the file
/etc/xroad/conf.d/local.ini
Each system parameter affects a specific server component. To change the value of a system parameter, a section for the affected component must be created in the INI file. The name-value pairs of the system parameters for that component are written under the section, one pair per line.
The following format is used for the sections:
[ServerComponent]
SystemParameterName1=Value1
SystemParameterName2=Value2
For example, to configure the parameter client-http-port for the proxy component, the following lines must be added to the configuration file:
[proxy]
client-http-port=1234
Multiple parameters can be configured under the same section:
[proxy]
client-http-port=1234
server-listen-port=20000
NB! Changing the parameter values in the configuration files requires restarting of the server.
WARNING! The value of the parameter is not validated, thus care must be taken when changing the value. For example, setting the port number to a non-numeric value in the configuration will cause the system to crash.
Changing the System Parameter Values in the Central Server Database
The central server database can be accessed with the psql utility using the following command (password: centerui):
psql -U centerui -h localhost centerui_production
The default value of a system parameter can be overridden by adding the parameter name and value to the system_parameters table:
INSERT INTO system_parameters (key, value, created_at, updated_at) VALUES ('parameter_name', 'parameter_value', (now() at time zone 'utc'), (now() at time zone 'utc'));
To edit the value of a system parameter already inserted into the system_parameters table:
UPDATE system_parameters SET value = '*parameter_value*', updated_at = (now() at time zone 'utc') WHERE key = 'parameter_name';
To restore the default value of a system parameter, delete the parameter from the system_parameters table:
DELETE FROM system_parameters WHERE key = 'parameter_name';
NB! Modifying or deleting system parameters other than the ones listed in section System Parameters in the Database will cause the system to crash.
Changing the Global Configuration Generation Interval in the Central Server
In order to override the default value of the global configuration generation interval, edit the cron expression[1] in the file
/etc/cron.d/xroad-center
The default contents of the file are the following:
#!/bin/sh
* * * * * xroad curl http://<IP_ADDRESS>:8084/managementservice/gen_conf 2>&1 > /dev/null;
NB! Global configuration generation interval must be modified with extreme care. Misuse of the global configuration generation interval may hinder the operation of the whole X-Road instance.
The configuration generation interval must be shorter than the value of global configuration expiration interval (confExpireIntervalSeconds, see section 4.2 ), or else the configuration downloaded by the configuration clients (security servers or configuration proxies) will always expire before valid configuration becomes available. It is highly recommended that the global configuration generation interval is multiple times smaller than the global configuration expiration interval.
Security Server System Parameters
This chapter describes the system parameters used by the components of the X-Road security server. For instructions on how to change the parameter values, see section Changing the System Parameter Values in Configuration Files.
| Server component | Parameter | Default value | Explanation |
|---|---|---|---|
| common | configuration-path | /etc/xroad/globalconf/ | Absolute path to the directory where global configuration is stored. |
| common | temp-files-path | /var/tmp/xroad/ | Absolute path to the directory where temporary files are stored. |
| proxy | client-http-port | 80 8080 (RHEL) |
TCP port on which the service client's security server listens for HTTP requests from client applications. |
| proxy | client-https-port | 443 8443 (RHEL) |
TCP port on which the service client's security server listens for HTTPS requests from client applications. |
| proxy | client-timeout | 30000 | Defines the time period (in milliseconds), for which the service client's security server tries to connect to the service provider's security server. When the timeout is reached, the service client's security server informs the service client's information system that a service timeout has occurred. |
| proxy | configuration-anchor-file | /etc/xroad/configuration-anchor.xml | Absolute file name of the configuration anchor that is used to download global configuration. |
| proxy | connector-host | <IP_ADDRESS> | IP address on which the service client's security server listens for connections from client applications. The value <IP_ADDRESS> allows listening on all IPv4 interfaces. |
| proxy | database-properties | /etc/xroad/db.properties | Absolute file name of the properties file for the configuration of the security server database. |
| proxy | enforce-token-pin-policy | false | Controls enforcing the token pin policy. When set to true, software token pin is required to be at least 10 ASCII characters from at least tree character classes (lowercase letters, uppercase letters, digits, special characters). (since version 6.7.7) |
| proxy | ocsp-cache-path | /var/cache/xroad | Absolute path to the directory where the cached OCSP responses are stored. |
| proxy | ocsp-responder-listen-address | <IP_ADDRESS> | IP address on which the service provider's security server listens for requests for OCSP responses from the service client's security server. The service client's security server downloads OCSP responses from the service provider's security server while establishing a secure connection between the security servers. The value <IP_ADDRESS> allows listening on all IPv4 interfaces. Must match the value of proxy.server-listen-address. |
| proxy | ocsp-responder-port | 5577 | TCP port on which the service provider's security server listens for requests for OCSP responses from the service client's security server. The service client's security server downloads OCSP responses from the service provider's security server while establishing a secure connection between the security servers. |
| proxy | ocsp-responder-client-connect-timeout | 20000 | Connect timeout (in milliseconds) of the OCSP responder client. The service client's security server downloads OCSP responses from the service provider's security server while establishing a secure connection between the security servers. |
| proxy | ocsp-responder-client-read-timeout | 30000 | Read timeout (in milliseconds) of the OCSP responder client. The service client's security server downloads OCSP responses from the service provider's security server while establishing a secure connection between the security servers. |
| proxy | server-listen-address | <IP_ADDRESS> | IP address on which the service provider's security server listens for connections from the service client's security servers. The value <IP_ADDRESS> allows listening on all IPv4 interfaces. |
| proxy | server-listen-port | 5500 | TCP port on which the service provider's security server listens for connections from the service client's security server. |
| proxy | server-port | 5500 | Destination TCP port for outgoing queries in the service client's security server. |
| proxy | jetty-clientproxy-configuration-file | /etc/xroad/jetty/clientproxy.xml | Absolute filename of the Jetty configuration file for the service client's security server. For more information about configuring Jetty server, see https://wiki.eclipse.org/Jetty/Reference/jetty.xml\_usage. |
| proxy | jetty-serverproxy-configuration-file | /etc/xroad/jetty/serverproxy.xml | Absolute filename of the Jetty configuration file for the service provider's security server. For more information about configuring Jetty server, see https://wiki.eclipse.org/Jetty/Reference/jetty.xml\_usage. |
| proxy | jetty-ocsp-responder-configuration-file | /etc/xroad/jetty/ocsp-responder.xml | Absolute filename of the Jetty configuration file for the OCSP responder of the service provider's security server. For more information about configuring Jetty server, see https://wiki.eclipse.org/Jetty/Reference/jetty.xml\_usage. |
| proxy | ssl-enabled | true | If true, TLS is used for connections between the service client's and service provider's security servers. |
| proxy | client-tls-ciphers | See [2] | TLS ciphers enabled on the client-side interfaces (for both incoming and outgoing requests). (since version 6.7) |
| proxy | client-tls-protocols | TLSv1.2,TLSv1.1 | TLS protocols enabled on the client-side interfaces (for both incoming and outgoing requests) (since version 6.7) |
| proxy | server-connector-max-idle-time | 0 (overridden to 120000 in Finnish installation) | The maximum time (in milliseconds) that connections from a service consuming security server to a service providing security server are allowed to be idle before the provider security server starts closing them. Value of 0 means that an infinite idle time is allowed. A non-zero value should allow some time for a pooled connection to be idle, if pooled connections are to be supported. |
| proxy | server-connector-so-linger | 0 | The SO_LINGER time (in seconds) at the service providing security server end for connections between security servers. A value larger than 0 means that upon closing a connection, the system will allow SO_LINGER seconds for the transmission and acknowledgement of all data written to the peer, at which point the socket is closed gracefully. Upon reaching the linger timeout, the socket is closed forcefully, with a TCP RST. Enabling the option with a timeout of zero does a forceful close immediately. Value of -1 disables the forceful close. |
| proxy | server-support-clients-pooled-connections | false (overridden to true in Finnish installation) | Whether this service providing security server supports pooled connections from the service consumer side. If set to false, connections are to be closed immediately after each message. This may be a wanted approached for security servers behind load balancers. |
| proxy | client-connector-max-idle-time | 0 | The maximum time (in milliseconds) that connections from a service consumer to the service consumer's security server are allowed to be idle before the security server starts closing them. Value of 0 means that an infinite idle time is allowed. |
| proxy | client-connector-so-linger | 0 | The SO_LINGER time (in seconds) at the service consuming security server end for connections between a consumer and a security server. A value larger than 0 means that upon closing a connection, the system will allow SO_LINGER seconds for the transmission and acknowledgement of all data written to the peer, at which point the socket is closed gracefully. Upon reaching the linger timeout, the socket is closed forcefully, with a TCP RST. Enabling the option with a timeout of zero does a forceful close immediately. Value of -1 disables the forceful close. |
| proxy | client-httpclient-timeout | 0 | The maximum time (SO_TIMEOUT, in milliseconds) that connections from a service consuming security server to a service providing security server are allowed to wait for a response before the consumer end httpclient gives up. Value of 0 means that an infinite wait time is allowed. This does not affect idle connections. |
| proxy | client-httpclient-so-linger | -1 | The SO_LINGER time (in seconds) at the service consuming security server end for connections between security servers. A value larger than 0 means that upon closing a connection, the system will allow SO_LINGER seconds for the transmission and acknowledgement of all data written to the peer, at which point the socket is closed gracefully. Upon reaching the linger timeout, the socket is closed forcefully, with a TCP RST. Enabling the option with a timeout of zero does a forceful close immediately. Value of -1 disables the forceful close. |
| proxy | client-use-idle-connection-monitor | true | Should the idle connection monitor be used to clean up idle and expired connections from the connection pool. |
| proxy | client-idle-connection-monitor-interval | 30000 | How often (in milliseconds) should the connection monitor go through the pooled connections to see if it can clean up any idle or expired connections. This option requires the connection monitor to be enabled to have any effect. |
| proxy | client-idle-connection-monitor-timeout | 60000 | The minimum time (in milliseconds) that a pooled connection must be unused (idle) before it can be removed from the pool. Note that removal from the pool also depends on how often the connection monitor runs. This option requires the connection monitor to be enabled to have any effect. |
| proxy | pool-total-max-connections | 10000 | The total maximum number of connections that are allowed in the pool. |
| proxy | pool-total-default-max-connections-per-route | 2500 | The default route specific connection maximum that is set unless a route specific connection limit is set. Due to the current implementation, this is actually the total maximum limit of connections, indepedent of what the above setting is. |
| proxy | pool-validate-connections-after-inactivity-of-millis | 2000 | When reusing a pooled connection to a service providing security server, check that the connection (the socket) is not half-closed if it has been idle for at least this many milliseconds. This method cannot detect half-open connections. Value of -1 disables the check. |
| proxy | pool-enable-connection-reuse | false (overridden to true in Finnish installation) | Allow pooled connections between security servers to be used more than once on the client side. The service provider end of the connections has to have the setting server-support-clients-pooled-connections=true for the pooling to work between a provider and consumer security servers. |
| proxy | client-use-fastest-connecting-ssl-socket-autoclose | true | On TLS connections between security servers, should the underlying TCP-layer connection (socket) be closed on the service consumer end when the TLS layer connection is terminated. |
| proxy | client-fastest-connecting-ssl-use-uri-cache | true | When a service consumer's security server finds the fastest responding service providing security server, should the result be saved in the TLS session cache? |
| proxy | health-check-port | 0 (disabled) | The TCP port where the health check service listens to requests. Setting the port to 0 disables the health check service completely. |
| proxy | health-check-interface | <IP_ADDRESS> | The network interface where the health check service listens to requests. Default is all available interfaces. |
| proxy | actorsystem-port | 5567 | The (localhost) port where the proxy actorsystem binds to. Used for communicating with xroad-signer and xroad-monitor. |
| proxy-ui | wsdl-validator-command | The command to validate the given X-Road service WSDL. The command script must: a) read the WSDL from the standard input (stdin), b) return exit code 0 on success, c) return exit code 0 and write warnings to the standard error (stderr), if warnings occurs, d) return exit code other then 0 and write error messages to the standard error (stderr), if errors occurs. Defaults to no operation. |
|
| proxy-ui | auth-cert-reg-signature-digest-algorithm-id | SHA-512 | Signature digest algorithm used for generating authentication certificate registration request. Possible values are - SHA-256, - SHA-384, - SHA-512. |
| signer | client-timeout | 15000 | Signing timeout in milliseconds. |
| signer | device-configuration-file | /etc/xroad/signer/devices.ini | Absolute filename of the configuration file of the signature creation devices. |
| signer | key-configuration-file | /etc/xroad/signer/keyconf.xml | Absolute filename of the configuration file containing signature and authentication keys and certificates. |
| signer | port | 5556 | TCP port on which the signer process listens. |
| signer | key-length | 2048 | Key length for generating authentication and signing keys (since version 6.7) |
| signer | csr-signature-digest-algorithm | SHA-256 | Certificate Signing Request signature digest algorithm. Possible values are - SHA-256, - SHA-384, - SHA-512. |
| anti-dos | enabled | true | Flag for enabling or disabling the AntiDOS system. |
| anti-dos | max-cpu-load | 1.1 | Maximum allowed CPU load for accepting new connections. If set to > 1.0, then CPU load is not checked. |
| anti-dos | max-heap-usage | 1.1 | Specifies the maximum allowed Java heap usage when accepting new connections. If set to > 1.0, then heap usage is not checked. |
| anti-dos | max-parallel-connections | 5000 | Maximum number of parallel connections for AntiDOS. |
| anti-dos | min-free-file-handles | 100 | Minimum amount of free file handles in the system for accepting new connections. At least one free file handle must be available to accept a new connection. |
| configuration-client | port | 5665 | TCP port on which the configuration client process listens. |
| configuration-client | update-interval | 60 | Global configuration download interval in seconds. |
| configuration-client | admin-port | 5675 | TCP port on which the configuration client process listens for admin commands. |
| message-log | soap-body-logging | true (overridden to false in Finnish installation) | Whether SOAP body of the messages should be logged or not. If true, SOAP messages are logged in original form. If false, SOAP body is cleared of its contents and only has an empty child element inside it. As a side effect, details such as formatting and namespace labels of the xml message can be changed and new elements may be introduced for default values in SOAP header. Removal of SOAP body is usually done for confidentiality reasons (body contains data that we do not want to have in the logs). Note that changing the message this way prevents verifying its signature with the asicverifier tool. |
| message-log | enabled-body-logging-local-producer-subsystems | Subsystem-specific overrides for SOAP body logging when soap-body-logging = false. This parameter defines logging for local producer subsystems, that is, our subsystems that produce some service which external clients use. Comma-separated list of client identifiers for which SOAP body logging is enabled. For example FI/ORG/1710128-9/SUBSYSTEM_A1, FI/ORG/1710128-9/SUBSYSTEM_A2 where - FI = x-road instance - ORG = member class - 1710128-9 = member code - SUBSYSTEM_A1 = subsystem code This parameter can only be used on subsystem-level, it is not possible to configure SOAP body logging per member. If a subsystem has forward slashes “/” in for example subsystem code, those subsystems can’t be configured with this parameter. |
|
| message-log | enabled-body-logging-remote-producer-subsystems | Subsystem-specific overrides for remote producer subsystems, that is, remote subsystems that produce services which we use. Parameter is used when soap-body-logging = false. |
|
| message-log | disabled-body-logging-local-producer-subsystems | Same as enabled-body-logging-local-producer-subsystems, but this parameter is used when soap-body-logging = true. | |
| message-log | disabled-body-logging-remote-producer-subsystems | Same as enabled-body-logging-remote-producer-subsystems, but this parameter is used when soap-body-logging = true. | |
| message-log | acceptable-timestamp-failure-period | 14400 | Defines the time period (in seconds) for how long is time-stamping allowed to fail (for whatever reasons) before the message log stops accepting any more messages (and consequently the security server stops accepting requests). Set to 0 to disable this check. The value of this parameter should not be lower than the value of the central server system parameter timeStampingIntervalSeconds. Default for Finnish installation is 18 000 seconds |
| message-log | archive-interval | 0 0 0/6 1/1 * ? * | CRON expression [CRON] defining the interval of archiving the time-stamped messages. |
| message-log | archive-max-filesize | 33554432 | Maximum size for archived files in bytes. Reaching the maximum value triggers file rotation. |
| message-log | archive-path | /var/lib/xroad | Absolute path to the directory where time-stamped log records are archived. |
| message-log | clean-interval | 0 0 0/12 1/1 * ? * | CRON expression [CRON] for deleting any time-stamped and archived records that are older than message-log.keep-records-for from the database. |
| message-log | hash-algo-id | SHA-512 | The algorithm identifier used for hashing in the message log. Possible values are - SHA-224, - SHA-256, - SHA-384, - SHA-512. |
| message-log | keep-records-for | 30 | Number of days to keep time-stamped and archived records in the database of the security server. If a time-stamped and archived message record is older than this value, the record is deleted from the database. |
| message-log | timestamp-immediately | false | If true, the time-stamp is created synchronously for each request message. This is a security policy requirement to guarantee the time-stamp at the time of logging the message. |
| message-log | timestamp-records-limit | 10000 | Maximum number of message records to time-stamp in one batch. |
| message-log | timestamper-client-connect-timeout | 20000 | The timestamper client connect timeout in milliseconds. A timeout of zero is interpreted as an infinite timeout. |
| message-log | timestamper-client-read-timeout | 60000 | The timestamper client read timeout in milliseconds. A timeout of zero is interpreted as an infinite timeout. |
| message-log | archive-transaction-batch | 10000 | Size of transaction batch for archiving messagelog. This size is not exact because it will always make sure that last archived batch includes timestamp also (this might mean that it will go over transaction size). |
| env-monitor | port | 2552 | TCP port number used in communications with xroad-proxy and xroad-monitor components. |
| env-monitor | system-metrics-sensor-interval | 5 | Interval of systems metrics sensor in seconds. How often system metrics data is collected. |
| env-monitor | disk-space-sensor-interval | 60 | Interval of disk space sensor in seconds. How often disk space data is collected. |
| env-monitor | exec-listing-sensor-interval | 60 | Interval of exec listing sensor in seconds. How often sensor data using external command are collected. |
Central Server System Parameters
The system parameters described in this chapter are used by the X-Road central server, except for the parameters ocspFreshnessSeconds and timeStampingIntervalSeconds.
The values of ocspFreshnessSeconds and timeStampingIntervalSeconds are distributed to the security servers via the global configuration. These parameters determine the interval of calling OCSP responder services and time-stamping services (respectively) by the security servers.
System Parameters in the Configuration File
For instructions on how to change the parameter values, see section Changing the System Parameter Values in Configuration Files.
| Server component | Name | Default value | Description |
|---|---|---|---|
| common | temp-files-path | /var/tmp/xroad/ | Absolute path to the directory where temporary files are stored. |
| center | conf-backup-path | /var/lib/xroad/backup/ | Absolute path to the directory where configuration backups are stored. |
| center | database-properties | /etc/xroad/db.properties | Absolute path to file where the properties of the database of the central server are stored. |
| center | external-directory | externalconf | Name of the signed external configuration directory that is distributed to the configuration clients (security servers and/or configuration proxies) of this and federated X-Road instances. |
| center | generated-conf-dir | /var/lib/xroad/public | Absolute path to the directory where both the private and shared parameter files are created for distribution. |
| center | internal-directory | internalconf | Name of the signed internal configuration directory that is distributed to the configuration clients (security servers and/or configuration proxies) of this X-Road instance. |
| center | trusted-anchors-allowed | false | True if federation is allowed for this X-Road instance. |
| center | minimum-global-configuration-version | 2 | Minimum supported global configuration version on central server. Change this if old global configuration versions need to be supported. |
| signer | ocsp-response-retrieval-active | false (see Description for more information) |
This property is used as an override to deactivate periodic OCSP-response retrieval for components that don't need that functionality, but still use signer. Values: false - OCSP-response retrieval jobs are never scheduled true - periodic OCSP-response retrieval is active based on ocspFetchInterval. Note that if the entire property is missing, it is interpreted as true. This property is delivered as an override and only for the components where the OCSP-response retrieval jobs need to be deactivated. The property is missing for components that require OCSP-response retrieval to be activated. |
System Parameters in the Database
This section describes the system parameters used by the X-Road central server. For instructions on how to change the parameter values, see section Changing the System Parameter Values in the Central Server Database.
| Name | Value type | Default value | Description |
|---|---|---|---|
| confExpireIntervalSeconds | integer | 600 | Time in seconds of the validity of the configuration after creation. |
| confHashAlgoUri | string | http://www.w3.org/2001/04/xmlenc#sha512 | URI of the algorithm used for calculating the hash values of the global configuration files. Possible values are http://www.w3.org/2001/04/xmlenc#sha256, http://www.w3.org/2001/04/xmlenc#sha512. |
| confSignDigestAlgoId | string | SHA-512 | Identifier of the digest algorithm used for signing the global configuration. Possible values are - SHA-256, - SHA-384, - SHA-512. |
| confSignCertHashAlgoUri | string | http://www.w3.org/2001/04/xmlenc#sha512 | URI of the algorithm used for calculating the hash value of the certificate used to sign the global configuration. Possible values are http://www.w3.org/2001/04/xmlenc\#sha256, http://www.w3.org/2001/04/xmlenc\#sha512. |
| ocspFreshnessSeconds | integer | 3600 | Defines the validity period (in seconds) for the OCSP responses retrieved from the OCSP responders. OCSP responses older than the validity period are considered expired and cannot be used for certificate verification. |
| timeStampingIntervalSeconds | integer | 60 | Defines the interval of time-stamping service calls. Interval in seconds after which message log records must be timestamped. The interval must be between 60 and 86400 seconds. Note: this value must be less than ocspFreshnessSeconds. |
Global Configuration Generation Interval Parameter
The global configuration generation interval parameter regulates the timing for global configuration generation. Global configuration generation is invoked by the Cron daemon[3]. The parameter is located at following file:
/etc/cron.d/xroad-center
The file is deployed during X-Road installation and by default has following content[4]:
#!/bin/sh
* * * * * xroad curl http://<IP_ADDRESS>:8084/managementservice/gen_conf 2>1 >/dev/null;
The parameter regulating the timing of global configuration generation is the cron expression at the start of the last line (* * * * *), which means that global configuration generation is invoked every minute by default.
Configuration Proxy System Parameters
This chapter describes the system parameters used by the X-Road configuration proxy.
| Server component | Name | Default value | Description |
|---|---|---|---|
| configuration-proxy | address | <IP_ADDRESS> | The public IP or NAT address which is accessed for downloading the distributed global configuration. |
| configuration-proxy | configuration-path | /etc/xroad/configurationproxy/ | Absolute path to the directory containing the configuration files of the configuration proxy instance. |
| configuration-proxy | generated-conf-path | /var/lib/xroad/public | Absolute path to the public web server directory where the global configuration files that this configuration proxy generates are be placed for distribution. |
| configuration-proxy | signature-digest-algorithm-id | SHA-512 | ID of the digest algorithm the configuration proxy uses when computing global configuration signatures. The possible values are - SHA-256, - SHA-384, - SHA-512. |
| configuration-proxy | hash-algorithm-uri | http://www.w3.org/2001/04/xmlenc#sha512 | URI that identifies the algorithm the configuration proxy uses when calculating hash values for the global configuration files. The possible values are http://www.w3.org/2001/04/xmlenc#sha256, http://www.w3.org/2001/04/xmlenc#sha512 |
| configuration-proxy | download-script | /usr/share/xroad/scripts/download_instance_configuration.sh | Absolute path to the location of the script that initializes the global configuration download procedure. |
| configuration-proxy | minimum-global-configuration-version | 2 | Minimum supported global configuration version on configuration proxy. Change this if old global configuration versions need to be supported. |
| signer | ocsp-response-retrieval-active | false (see Description for more information) |
This property is used as an override to deactivate periodic OCSP-response retrieval for components that don't need that functionality, but still use signer. Values: false - OCSP-response retrieval jobs are never scheduled true - periodic OCSP-response retrieval is active based on ocspFetchInterval. Note that if the entire property is missing, it is interpreted as true. This property is delivered as an override and only for the components where the OCSP-response retrieval jobs need to be deactivated. The property is missing for components that require OCSP-response retrieval to be activated. |
[1] See also http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger.
[2] Default value for proxy.client-tls-ciphers.
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA
(see https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SunJSSEProvider for possible values)
Note. OpenJDK 8 on RHEL 7 does not support ECDHE key agreement protocol, only DHE cipher suites are supported.
[3] See also http://linux.die.net/man/8/cron.
[4] For exact format specification see also https://help.ubuntu.com/community/CronHowto.


| 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 | 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 2x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 2x 355x 2x 341x 2x 339x 6154x 6154x 6154x 6154x 6154x 2x 440x 2x 216x 216x 216x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 360x 6154x 6154x 6154x 6154x 6154x 2x 360x 360x 360x 360x 360x 360x 360x 2x 360x 360x 360x 360x 360x 360x 2x 360x 360x 360x 2x 2x 2x 2x 360x 2x | /** * Copyright 2017 Google Inc. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ import { User } from '../auth/user'; import { DatabaseInfo } from '../core/database_info'; import { JsonProtoSerializer } from '../remote/serializer'; import { assert } from '../util/assert'; import { Code, FirestoreError } from '../util/error'; import * as log from '../util/log'; import { AutoId } from '../util/misc'; import { IndexedDbMutationQueue } from './indexeddb_mutation_queue'; import { IndexedDbQueryCache } from './indexeddb_query_cache'; import { IndexedDbRemoteDocumentCache } from './indexeddb_remote_document_cache'; import { ALL_STORES, createOrUpgradeDb, DbOwner, DbOwnerKey, SCHEMA_VERSION } from './indexeddb_schema'; import { LocalSerializer } from './local_serializer'; import { MutationQueue } from './mutation_queue'; import { Persistence } from './persistence'; import { PersistencePromise } from './persistence_promise'; import { QueryCache } from './query_cache'; import { RemoteDocumentCache } from './remote_document_cache'; import { SimpleDb, SimpleDbTransaction } from './simple_db'; const LOG_TAG = 'IndexedDbPersistence'; /** If the owner lease is older than 5 seconds, try to take ownership. */ const OWNER_LEASE_MAX_AGE_MS = 5000; /** Refresh the owner lease every 4 seconds while owner. */ const OWNER_LEASE_REFRESH_INTERVAL_MS = 4000; /** LocalStorage location to indicate a zombied ownerId (see class comment). */ const ZOMBIE_OWNER_LOCALSTORAGE_SUFFIX = 'zombiedOwnerId'; /** Error when the owner lease cannot be acquired or is lost. */ const EXISTING_OWNER_ERROR_MSG = 'There is another tab open with offline' + ' persistence enabled. Only one such tab is allowed at a time. The' + ' other tab must be closed or persistence must be disabled.'; const UNSUPPORTED_PLATFORM_ERROR_MSG = 'This platform is either missing' + ' IndexedDB or is known to have an incomplete implementation. Offline' + ' persistence has been disabled.'; /** * An IndexedDB-backed instance of Persistence. Data is stored persistently * across sessions. * * Currently the Firestore SDK only supports a single consumer of the database, * but browsers obviously support multiple tabs. IndexedDbPersistence ensures a * single consumer of the database via an "owner lease" stored in the database. * * On startup, IndexedDbPersistence assigns itself a random "ownerId" and writes * it to a special "owner" object in the database (if no entry exists already or * the current entry is expired). This owner lease is then verified inside every * transaction to ensure the lease has not been lost. * * If a tab opts not to acquire the owner lease (because there's an existing * non-expired owner) or loses the owner lease, IndexedDbPersistence enters a * failed state and all subsequent operations will automatically fail. * * The current owner regularly refreshes the owner lease with new timestamps to * prevent newly-opened tabs from taking over ownership. * * Additionally there is an optimization so that when a tab is closed, the owner * lease is released immediately (this is especially important to make sure that * a refreshed tab is able to immediately re-acquire the owner lease). * Unfortunately, IndexedDB cannot be reliably used in window.unload since it is * an asynchronous API. So in addition to attempting to give up the lease, * the owner writes its ownerId to a "zombiedOwnerId" entry in LocalStorage * which acts as an indicator that another tab should go ahead and take the * owner lease immediately regardless of the current lease timestamp. */ export class IndexedDbPersistence implements Persistence { /** * The name of the main (and currently only) IndexedDB database. this name is * appended to the prefix provided to the IndexedDbPersistence constructor. */ static MAIN_DATABASE = 'main'; private simpleDb: SimpleDb; private started: boolean; private dbName: string; private localStoragePrefix: string; private ownerId: string = this.generateOwnerId(); /** * Set to an Error object if we encounter an unrecoverable error. All further * transactions will be failed with this error. */ private persistenceError: Error | null; /** The setInterval() handle tied to refreshing the owner lease. */ // tslint:disable-next-line:no-any setTimeout() type differs on browser / node private ownerLeaseRefreshHandle: any; /** Our window.unload handler, if registered. */ private windowUnloadHandler: (() => void) | null; private serializer: LocalSerializer; constructor(prefix: string, serializer: JsonProtoSerializer) { this.dbName = prefix + IndexedDbPersistence.MAIN_DATABASE; this.serializer = new LocalSerializer(serializer); this.localStoragePrefix = prefix; } start(): Promise<void> { Iif (!IndexedDbPersistence.isAvailable()) { this.persistenceError = new FirestoreError( Code.UNIMPLEMENTED, UNSUPPORTED_PLATFORM_ERROR_MSG ); return Promise.reject(this.persistenceError); } assert(!this.started, 'IndexedDbPersistence double-started!'); this.started = true; return SimpleDb.openOrCreate(this.dbName, SCHEMA_VERSION, createOrUpgradeDb) .then(db => { this.simpleDb = db; }) .then(() => this.tryAcquireOwnerLease()) .then(() => { this.scheduleOwnerLeaseRefreshes(); this.attachWindowUnloadHook(); }); } shutdown(): Promise<void> { assert(this.started, 'IndexedDbPersistence shutdown without start!'); this.started = false; this.detachWindowUnloadHook(); this.stopOwnerLeaseRefreshes(); return this.releaseOwnerLease().then(() => { this.simpleDb.close(); }); } getMutationQueue(user: User): MutationQueue { return IndexedDbMutationQueue.forUser(user, this.serializer); } getQueryCache(): QueryCache { return new IndexedDbQueryCache(this.serializer); } getRemoteDocumentCache(): RemoteDocumentCache { return new IndexedDbRemoteDocumentCache(this.serializer); } runTransaction<T>( action: string, operation: (transaction: SimpleDbTransaction) => PersistencePromise<T> ): Promise<T> { Iif (this.persistenceError) { return Promise.reject(this.persistenceError); } log.debug(LOG_TAG, 'Starting transaction:', action); // Do all transactions as readwrite against all object stores, since we // are the only reader/writer. return this.simpleDb.runTransaction('readwrite', ALL_STORES, txn => { // Verify that we still have the owner lease as part of every transaction. return this.ensureOwnerLease(txn).next(() => operation(txn)); }); } static isAvailable(): boolean { return SimpleDb.isAvailable(); } /** * Generates a string used as a prefix when storing data in IndexedDB and * LocalStorage. */ static buildStoragePrefix(databaseInfo: DatabaseInfo): string { // Use two different prefix formats: // // * firestore / persistenceKey / projectID . databaseID / ... // * firestore / persistenceKey / projectID / ... // // projectIDs are DNS-compatible names and cannot contain dots // so there's no danger of collisions. let database = databaseInfo.databaseId.projectId; Iif (!databaseInfo.databaseId.isDefaultDatabase) { database += '.' + databaseInfo.databaseId.database; } return 'firestore/' + databaseInfo.persistenceKey + '/' + database + '/'; } /** * Acquires the owner lease if there's no valid owner. Else returns a rejected * promise. */ private tryAcquireOwnerLease(): Promise<void> { // NOTE: Don't use this.runTransaction, since it requires us to already // have the lease. return this.simpleDb.runTransaction('readwrite', [DbOwner.store], txn => { const store = txn.store<DbOwnerKey, DbOwner>(DbOwner.store); return store.get('owner').next(dbOwner => { Eif (!this.validOwner(dbOwner)) { const newDbOwner = new DbOwner(this.ownerId, Date.now()); log.debug( LOG_TAG, 'No valid owner. Acquiring owner lease. Current owner:', dbOwner, 'New owner:', newDbOwner ); return store.put('owner', newDbOwner); } else { log.debug( LOG_TAG, 'Valid owner already. Failing. Current owner:', dbOwner ); this.persistenceError = new FirestoreError( Code.FAILED_PRECONDITION, EXISTING_OWNER_ERROR_MSG ); return PersistencePromise.reject<void>(this.persistenceError); } }); }); } /** Checks the owner lease and deletes it if we are the current owner. */ private releaseOwnerLease(): Promise<void> { // NOTE: Don't use this.runTransaction, since it requires us to already // have the lease. return this.simpleDb.runTransaction('readwrite', [DbOwner.store], txn => { const store = txn.store<DbOwnerKey, DbOwner>(DbOwner.store); return store.get('owner').next(dbOwner => { Eif (dbOwner !== null && dbOwner.ownerId === this.ownerId) { log.debug(LOG_TAG, 'Releasing owner lease.'); return store.delete('owner'); } else { return PersistencePromise.resolve(); } }); }); } /** * Checks the owner lease and returns a rejected promise if we are not the * current owner. This should be included in every transaction to guard * against losing the owner lease. */ private ensureOwnerLease(txn: SimpleDbTransaction): PersistencePromise<void> { const store = txn.store<DbOwnerKey, DbOwner>(DbOwner.store); return store.get('owner').next(dbOwner => { Iif (dbOwner === null || dbOwner.ownerId !== this.ownerId) { this.persistenceError = new FirestoreError( Code.FAILED_PRECONDITION, EXISTING_OWNER_ERROR_MSG ); return PersistencePromise.reject<void>(this.persistenceError); } else { return PersistencePromise.resolve(); } }); } /** * Returns true if the provided owner exists, has a recent timestamp, and * isn't zombied. * * NOTE: To determine if the owner is zombied, this method reads from * LocalStorage which could be mildly expensive. */ private validOwner(dbOwner: DbOwner | null): boolean { const now = Date.now(); const minAcceptable = now - OWNER_LEASE_MAX_AGE_MS; const maxAcceptable = now; Eif (dbOwner === null) { return false; // no owner. } else if (dbOwner.leaseTimestampMs < minAcceptable) { return false; // owner lease has expired. } else if (dbOwner.leaseTimestampMs > maxAcceptable) { log.error( 'Persistence owner-lease is in the future. Discarding.', dbOwner ); return false; } else if (dbOwner.ownerId === this.getZombiedOwnerId()) { return false; // owner's tab closed. } else { return true; } } /** * Schedules a recurring timer to update the owner lease timestamp to prevent * other tabs from taking the lease. */ private scheduleOwnerLeaseRefreshes(): void { // NOTE: This doesn't need to be scheduled on the async queue and doing so // would increase the chances of us not refreshing on time if the queue is // backed up for some reason. this.ownerLeaseRefreshHandle = setInterval(() => { const txResult = this.runTransaction('Refresh owner timestamp', txn => { // NOTE: We don't need to validate the current owner contents, since // runTransaction does that automatically. const store = txn.store<DbOwnerKey, DbOwner>(DbOwner.store); return store.put('owner', new DbOwner(this.ownerId, Date.now())); }); txResult.catch(reason => { // Probably means we lost the lease. Report the error and stop trying to // refresh the lease. log.error(reason); this.stopOwnerLeaseRefreshes(); }); }, OWNER_LEASE_REFRESH_INTERVAL_MS); } private stopOwnerLeaseRefreshes(): void { Eif (this.ownerLeaseRefreshHandle) { clearInterval(this.ownerLeaseRefreshHandle); this.ownerLeaseRefreshHandle = null; } } /** * Attaches a window.unload handler that will synchronously write our * ownerId to a "zombie owner id" location in localstorage. This can be used * by tabs trying to acquire the lease to determine that the lease should be * acquired immediately even if the timestamp is recent. This is particularly * important for the refresh case (so the tab correctly re-acquires the owner * lease). LocalStorage is used for this rather than IndexedDb because it is * a synchronous API and so can be used reliably from an unload handler. */ private attachWindowUnloadHook(): void { this.windowUnloadHandler = () => { // Record that we're zombied. this.setZombiedOwnerId(this.ownerId); // Attempt graceful shutdown (including releasing our owner lease), but // there's no guarantee it will complete. this.shutdown(); }; window.addEventListener('unload', this.windowUnloadHandler); } private detachWindowUnloadHook(): void { Eif (this.windowUnloadHandler) { window.removeEventListener('unload', this.windowUnloadHandler); this.windowUnloadHandler = null; } } /** * Returns any recorded "zombied owner" (i.e. a previous owner that became * zombied due to their tab closing) from LocalStorage, or null if no such * record exists. */ private getZombiedOwnerId(): string | null { try { const zombiedOwnerId = window.localStorage.getItem( this.zombiedOwnerLocalStorageKey() ); log.debug(LOG_TAG, 'Zombied ownerID from LocalStorage:', zombiedOwnerId); return zombiedOwnerId; } catch (e) { // Gracefully handle if LocalStorage isn't available / working. log.error('Failed to get zombie owner id.', e); return null; } } /** * Records a zombied owner (an owner that had its tab closed) in LocalStorage * or, if passed null, deletes any recorded zombied owner. */ private setZombiedOwnerId(zombieOwnerId: string | null) { try { if (zombieOwnerId === null) { window.localStorage.removeItem(this.zombiedOwnerLocalStorageKey()); } else { window.localStorage.setItem( this.zombiedOwnerLocalStorageKey(), zombieOwnerId ); } } catch (e) { // Gracefully handle if LocalStorage isn't available / working. log.error('Failed to set zombie owner id.', e); } } private zombiedOwnerLocalStorageKey(): string { return this.localStoragePrefix + ZOMBIE_OWNER_LOCALSTORAGE_SUFFIX; } private generateOwnerId(): string { // For convenience, just use an AutoId. return AutoId.newId(); } } |


The very important meeting ends nothing happened in the meeting execpt FOR EVERYTHING.  For example:
There was a lot of flash backs.Turns out Gladia doent like Dr.Amarido. Then the agurment between when she meet a Dr.fastlofe. (just under 6 months of her being pregnant with her son.
Really this entire chapeter is a debate on this and that dis-agrement and robots.


Standard Library
Jump to Section
The Python Standard Library By Example
PyMOTW-3 is a series of articles written by Doug Hellmann to demonstrate how to use the modules of the Python 3 standard library. It is based on the original PyMOTW series, which covered Python 2.7. See About Python Module of the Week for details including the version of Python and tools used.
- Text
- Data Structures
- enum – Enumeration Type
- collections — Container Data Types
- array — Sequence of Fixed-type Data
- heapq – Heap Sort Algorithm
- bisect — Maintain Lists in Sorted Order
- queue — Thread-Safe FIFO Implementation
- struct — Binary Data Structures
- weakref — Impermanent References to Objects
- copy — Duplicate Objects
- pprint — Pretty-Print Data Structures
- Algorithms
- Dates and Times
- Mathematics
- The File System
- os.path — Platform-independent Manipulation of Filenames
- pathlib — Filesystem Paths as Objects
- glob — Filename Pattern Matching
- fnmatch — Unix-style Glob Pattern Matching
- linecache — Read Text Files Efficiently
- tempfile — Temporary File System Objects
- shutil — High-level File Operations
- filecmp — Compare Files
- mmap — Memory-map Files
- codecs — String Encoding and Decoding
- io — Text, Binary, and Raw Stream I/O Tools
- Data Persistence and Exchange
- Data Compression and Archiving
- Cryptography
- Concurrency with Processes, Threads, and Coroutines
- subprocess — Spawning Additional Processes
- signal — Asynchronous System Events
- threading — Manage Concurrent Operations Within a Process
- multiprocessing — Manage Processes Like Threads
- asyncio — Asynchronous I/O, event loop, and concurrency tools
- concurrent.futures — Manage Pools of Concurrent Tasks
- Networking
- The Internet
- urllib.parse — Split URLs into Components
- urllib.request — Network Resource Access
- urllib.robotparser — Internet Spider Access Control
- base64 — Encode Binary Data with ASCII
- http.server — Base Classes for Implementing Web Servers
- http.cookies — HTTP Cookies
- webbrowser — Displays web pages
- uuid — Universally Unique Identifiers
- json — JavaScript Object Notation
- xmlrpc.client — Client Library for XML-RPC
- xmlrpc.server — An XML-RPC server
- Application Building Blocks
- argparse — Command-Line Option and Argument Parsing
- getopt — Command Line Option Parsing
- readline — The GNU readline Library
- getpass — Secure Password Prompt
- cmd — Line-oriented Command Processors
- shlex — Parse Shell-style Syntaxes
- configparser — Work with Configuration Files
- logging — Report Status, Error, and Informational Messages
- fileinput — Command-Line Filter Framework
- atexit — Program Shutdown Callbacks
- sched — Timed Event Scheduler
- Internationalization and Localization
- Developer Tools
- pydoc — Online Help for Modules
- doctest — Testing Through Documentation
- unittest — Automated Testing Framework
- trace — Follow Program Flow
- traceback — Exceptions and Stack Traces
- cgitb — Detailed Traceback Reports
- pdb — Interactive Debugger
- profile and pstats — Performance Analysis
- timeit — Time the execution of small bits of Python code.
- tabnanny — Indentation validator
- compileall — Byte-compile Source Files
- pyclbr — Class Browser
- venv — Create Virtual Environments
- ensurepip — Install the Python Package Installer
- Runtime Features
- Language Tools
- Modules and Packages
- Unix-specific Services
- Porting Notes
- Outside of the Standard Library
- About Python Module of the Week
Source : https://pymotw.com/3/index.html
source code : https://github.com/dhellmann/pymotw-3


Rate the following factors on a scale of 1 to 3 where 3 being Good and 1 being Poor or a scale of 5 to 1 (5-Strongly Agree, 4-Agree, 3-Neutral, 2-Disagree and 1-Strongly Disagree), which indicates the level of your agreement.
To provide inputs to management about the extent to which SUN core values and instilled in our employees.
Determine employee’s understanding and belief in SUN vision, mission, organizational goals and objectives.
To gauge the perception of employee towards organization and commitment level towards the development of organization
Measure the level of engagement and satisfaction of employee.
To identify the problem areas at ground level and opportunities of improvement
To enable us serve you better through your responses from this feedback
We would appreciate your precious feedback in responding to the following questions pertaining to services offered by various Department in the school. We believe that this survey would certainly help us to serve you better in the future. Rate the following factors in a scale of 1 to 3 where 3 being Good and 1 being Poor or a scale of 5 to 1 (5-Strongly Agree, 4-Agree, 3-Neutral, 2-Disagree and 1-Strongly Disagree), which indicates the level of your agreement.
To enable us serve you better through your responses from this feedback
We would appreciate your precious feedback in responding to the following questions
pertaining to services offered by Academic Support Department .
We believe that this survey would certainly help us to serve you better in the future.
Rate the following factors in a scale of 1 to 3 where 3 being Good and 1 being Poor.


ResNet-50 conversion WebDNN example
You have to convert ResNet-50 with python script before running this webpage.
Image URL:
Load image
Using canvas's image slightly changes the output due to interpolation.
Run
Backend:
auto
webgpu
webassembly
fallback (slow; debug only)
Framework for model:
Keras
Chainer


The other day I came across a small issue, while using the Android port of GPUImage. On some devices (mainly Samsung), an image captured in portrait by the camera intent and then fed to GPUImageView would be rotated by 90 degrees. On other devices, this would work perfectly. Also, selecting an already captured image from the gallery worked just fine.
Despite being captured in portrait mode, the resulting image will be rotated when loaded in GPUImageView
I first noticed that the problematic devices were all setting the device orientation to landscape when opening up the camera mode. There were a few noticeable rotations during the process of capturing and reviewing an image. I thought they would somehow write wrong Exif data into the image, but I soon was proved wrong.
The real issue lied within my way of loading the image to GPUImageView:
I grabbed the Uri, once the user supplied a picture via camera, gallery or share with my app function in my onActivityResult
method:
[…] case R.string.choose_photo: case R.string.take_photo: case R.string.share: if (resultCode == RESULT_OK) { final Uri uri; switch (requestCode) { case R.string.take_photo: // same as I configured via intent.putExtra(MediaStore.EXTRA_OUTPUT, mTempFileUri); in the photo intent uri = mTempFileUri; break; case R.string.share: uri = data.getParcelableExtra(Intent.EXTRA_STREAM); break; default: // some fixes for url-encoded paths like DropBox returns; and paths without “file://” scheme uri = Utils.extractProperFileUri(data.getData()); break; } // now feed the image to GPUImageView mGPUImageView.setImage(uri); } […]
Setting the image by passing an Uri object, leads to this internal flow in GPUImage:
- delegate loading to GPUImage, which will start a
LoadImageUriTask
- the above task will either load the image from web (uri starts with http or https) or using a ContentResolver
- then, it will determine a proper size and rotation for the image, using a media query to
MediaStore.Images.ImageColumns.ORIENTATION
- .. and finally return the image resized and rotated to be displayed within the GPUImageView (involves calls to setRenderer and so forth)
The problem lies within step 3, if the given Uri’s scheme is not content
but file
. Media queries work on proper content Uris, so Android can look into the meta data associated with the image from a media collection. On the other side, when passing an Uri with a file
-scheme, the ContentResolver will find no additional meta data for a „generic file“ which resides on a given path. To get ahold of any additional image information, one should use the ExifInterface and read the ExifInterface.TAG_ORIENTATION
from the file.
Fortunately, after a quick digging into the GPUImage code, I found that the method mGPUImageView.setImage();
actually supports various types of parameters and then uses slightly different ways to load and interpret them:
// load the image directly from bitmap data setImage(Bitmap bmp);
// load a file from the file system, interpreting exif data for proper rotation setImage(File file);
// load a file from the internet or media store, using media query for proper rotation setImage(Uri uri);
Since I also passed an Uri object when I referenced a file, GPUImage could not determine the proper rotation in the -non existing- media store data. Eventually, fixing this was as easy as that:
[…] // now feed the image to GPUImageView // either by File or other ContentResolver // important for correct usage of detecting image rotation (File: ExifInterface; ContentResolver: MediaStore > ImageColumns) if (“file”.equals(uri.getScheme())) { mGPUImageView.setImage(new File(uri.getPath())); } else { mGPUImageView.setImage(uri); }
Providing GPUImageView with the proper parameters in setImage() leads to correct rotation
I hope it helps someone facing the same issues. It is not specifically related to GPUImage, but to capturing an photo with Android and processing it in general, as you can see at stackoverflow. GPUImage employs best practices to load an image properly, if provided with the correct parameters.
Big thanks to CyberAgent and pboos for proding us with that port of the original GPUImage library for iOS.


We are Zefo, an early stage eCommerce startup committed to giving buyers and sellers an absolutely hassle free used goods shopping experience. Quite counter-intuitively, we decided to take all of that pain and load it all on ourselves, to ensure that each of you get the most convenient and Zero Effort experience while trying to buy and sell.
Keep Connected
Like us on Facebook Follow us on Twitter Add us on Google Plus
Contact Us
3154 Glenwood Avenue, Warrensville Heights, Ohio-44128.


... All of your HTML content is here ...
See the HTML code and comments regarding how to load external JavaScript files (from a sub-folder) directly before the </body> end tag.
</body>


--- layout: post title: DDD eXchange 2010 date: 2010-07-18 17:08:43.000000000 -06:00 type: post published: true status: publish categories: - Community Event - Library - News tags: [] meta: _gcid: '205' _edit_last: '3' _wp_page_template: default _bitly_trim: http://dddcommunity.org/?p=92 _dependencies: s:6:"a:0:{}"; custom_permalink: events/dddx2010/ _custom_background: a:5:{s:3:"url";s:0:"";s:16:"background-color";s:0:"";s:17:"background-repeat";s:6:"repeat";s:21:"background-attachment";s:6:"scroll";s:19:"background-position";s:8:"left top";} _intro_text: default _intro_custom_banner: a:1:{s:3:"url";s:0:"";} author: login: Vladimir Gitlevich email<EMAIL_ADDRESS>display_name: Vladimir Gitlevich first_name: Vladimir Gitlevich last_name: '' ---
The second annual DDD eXchange in London is done. Wow! It turned out even better than last year.
The idea had been to make this a real conference, where experts convened to confer on the issues and questions of the moment in DDD. And that is what happened!
Rather than cram the day with talks which, while potentially informative, put attendees in a passive position, the conference focused on two broad themes: Architectural Innovation (especially Event Sourcing and CQRS) and Process Integration (combining DDD with Agile, TDD, BDD, etc.). It also included a lot of opportunities for interaction between everyone present. The whole was greater than the sum of the parts.
In 2010 the community's attention is turned toward two areas of innovative energy: A family of architectural approaches that promise to scale DDD more effectively and more clearly mark context boundaries; and a new look at fitting DDD and Agile processes together along with a handful of other key best practices.
The conference featured 7 expert talks, including those by Eric Evans, Udi Dahan and Greg Young, and two Parkbench sessions. All the talks were recorded and you can watch them online.
Eric Evans wrote up his impressions of the conference in the Domain Language newsletter here.


Toggle navigation
GovEx Operations Dashboard
City Dashboard
Mesa
Louisville
Charts
Assignment Map
Applicant Cities Map
Tables
Mesa Dashboard


Angular Dispersion function
This function implements Planck Collaboration 2016 method to calculates the angular dispersion of the region
- AngularDispersion.AngularDispersion(stokesQ, stokesU, PolAngerr, lag=0.5)
StructureFunctionAnalysis
This function implements Planck Collaboration 2016 method to calculates the angular dispersion of the region The input needs to be an astropy.io.fits.PrimaryHDU
- Parameters
stokesQ (astropy.io.fits.PrimaryHDU) – The Stokes Q file in astropy.io.fits.PrimaryHDU.
stokesU (astropy.io.fits.PrimaryHDU) – The Stokes U file in astropy.io.fits.PrimaryHDU.
PolAngerr (astropy.io.fits.PrimaryHDU) – The error in Polarization angles in astropy.io.fits.PrimaryHDU format.
lag (float) – The lag also referred to as delta is specifies the area under which the angular dispersion is calculated, For more information please refer to the paper mentioned above.
- Returns
returns the debiased angular dispersion map of the region.
- Return type
S_map_deb (2D numpy array)


StackMachine currently only supports games written using the LÖVE game engine, but we'll be adding support for more engines soon. Sign up below to get updates when support for your engine of choice is available.


This is inside the basic view!
Name:
The name was set with from the 'code behind' (i.e. View.ts) using a value provided from the view model.


Label
Status
hide
s1
start
ctrl-c
ctrl-z
resume
terminate
show
s2
start
ctrl-c
ctrl-z
resume
terminate
show
s3
start
ctrl-c
ctrl-z
resume
terminate
show
s4
start
ctrl-c
ctrl-z
resume
terminate
show
Nothing sent yet!


Home
Your Library
GO
Sign Up
Login
Cookie Policy
|
Privacy
TRENDING
PODCAST
MOODS AND GENRES
NEW RELEASES
DISCOVER
Search Results
Rock Classics
Pop Artists
HipHop Top


MathUtil
画圆
判断是否为空字符
打乱数组
判断输入框是否为空字符
判断表单项
判断是否是pc端
获取终端类型
存储cookie
获取cookie
删除cookie
复制对象
时间差
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf
dfadfasdf


- Select 'ia15. meta_ii with loops, use with ca05' from the first list on the left
- Select 'ca05 added STORE AND LOAD VARIABLES' from the center list
- click the ⤺ arrow to copy the output to the center text area
- Select 'ia16. sql to eosio' which will output the compiler
- click the ⤺ arrow to copy the output to the center text area
- Select 'ia17. create table example' to see the sql2eos compiler in action!
⤺


--- layout: archive title: Zulip Chat Archive permalink: /stream/144837-PR-reviews/topic/.23988.20norm_cast.html ---
Currently there is a very long list of attributes being added starting at https://github.com/leanprover-community/mathlib/pull/988/files#diff-836b1338043521d5628c0a4b8832505dR357
Does it make sense to move these to the respective files real.lean
and complex.lean
(or whatever they are). Of course some of these lemmas are in core, so then it's fine to keep them here. Do we want this tactic to depend on the complex numbers?
Is it possible to have a syntax
attributes [norm_cast] [nat.cast_add, int.coe_nat_add, int.cast_add]
?
you already have it
remove the s and the second series of []
Great! I think I would rather keep the attributes with the tactic, unless we want to start using the tactic earlier, i.e., before all the lemmas with the attributes are even defined.
I just used it for the first time!
Bad news is importing this kills all my other proofs
I get deterministic timeout in proofs not using norm_cast
that used to type check instantaneously
@Sebastien Gouezel What is your reason for keeping the attributes in this file?
I don't really care either way... To me it just feels more natural to have them close the the lemma's if possible.
I don't really mind either. Maybe the current setup is easier to modify, and helps to understand the role of the different attributes.
Actually, I didn't even look at the imports. I don't think tactic.norm_cast
should import any more than is necessary to define the tactic. Most of the attributes should be added when the lemmas are proved.
It would be silly if you needed to import data.complex
in order to simplify nat
-to-int
casts.
@Paul-Nicolas Madelaine
Patrick, that must be caused by a transitive import. Do you get the same problem importing data.complex.basic
instead of norm_cast
?
After all, data.complex
is very ... complex :upside_down: :grinning_face_with_smiling_eyes:
I removed all the unnecessary imports from norm_cast.lean
@Patrick Massot could you check if that solved the problem?
They are two reasons why I had left these attributes in the norm_cast.lean file :
- compile time, now any modification in the file requires recompiling a lot of things
- clarity, you could see the general shape of the lemmas, and their different versions for different data types
There's nothing much that can be done about the first point,
but about the second, I could add a comment with a list of "typical" norm_cast and simp_cast lemmas
I should say that I didn't pull the branch. I copied the content of the tactic file into a new file in a project depending on an old version of mathlib. I have a real workflow issue here, and it was the same with omega
and cooper
. It's very hard to test a tactic until it actually is in mathlib (or can be dumped in a completely autonomous file)
Right now I registered lemmas like complex.of_real_im
as elimination lemmas,
and lemmas like rat.cast_mk_of_ne_zero
as compositionnal lemmas.
But the fact is that, unlike more simple lemmas like nat.cast_add
, these don't just move casts around, they also simplify things (for instance complex.of_real_im
removes the projection).
Do you think that these lemmas should be applied by norm_cast, or should they be left to the simplifier?
More generally, where do we draw the line between what is a norm_cast lemma and what should be left to simp?
Ooh, I think norm_cast
should do as much as possible. Because it's still a very small thing that it tries to do. But it tries to do it really well.
Simp tries to do a lot, and for that reason it's not popular to call simp half-way a proof.
We were just discussing whether it would make sense to introduce a cast_mode
or mod_cast
tactic combinator. It would accept a list of tactics and normalize all casts between the steps.
@Johan Commelin told me he's running into proofs in which rw
and norm_cast
lines alternate repeatedly.
I have to say I do not have any idea how the cast tactics are implemented ;)
Last updated: Apr 24 2020 at 19:02 UTC