Null/empty/absent data¶
One of Miller's key features is its support for heterogeneous data. For example, take mlr sort
: if you try to sort on field hostname
when not all records in the data stream have a field named hostname
, it is not an error (although you could pre-filter the data stream using mlr having-fields --at-least hostname then sort ...
). Rather, records lacking one or more sort keys are simply output contiguously by mlr sort
.
The three types¶
Miller has three kinds of null data:
-
Empty (key present, value empty): a field name is present in a record (or in an out-of-stream variable) with empty value: e.g.
x=,y=2
in the data input stream, or assignment$x=""
or@x=""
inmlr put
. -
Absent (key not present): a field name is not present, e.g. input record is
x=1,y=2
and aput
orfilter
expression refers to$z
. Or, reading an out-of-stream variable which hasn't been assigned a value yet, e.g.mlr put -q '@sum += $x; end{emit @sum}'
ormlr put -q '@sum[$a][$b] += $x; end{emit @sum, "a", "b"}'
. -
JSON null: The main purpose of this is to support reading the
null
type in JSON files. The Miller programming language has anull
keyword as well, so you can also write the null type using$x = null
. Additionally, though, when you write past the end of an array, leaving gaps -- e.g. writinga[12]
when the arraya
has length 10 -- JSON-null is used to fill the gaps. See also the arrays page.
You can test these programmatically using the functions is_empty
/is_not_empty
, is_absent
/is_present
, and is_null
/is_not_null
. For the last pair, note that null means either empty or absent. Here is a full list of such functions:
mlr -f | grep is_
is_absent is_array is_bool is_boolean is_empty is_empty_map is_error is_float is_int is_map is_nan is_nonempty_map is_not_array is_not_empty is_not_map is_not_null is_null is_numeric is_present is_string
Rules for null-handling¶
- Records with one or more empty sort-field values sort after records with all sort-field values present:
mlr cat data/sort-null.dat
a=3,b=2 a=1,b=8 a=,b=4 x=9,b=10 a=5,b=7
mlr sort -n a data/sort-null.dat
a=1,b=8 a=3,b=2 a=5,b=7 a=,b=4 x=9,b=10
mlr sort -nr a data/sort-null.dat
a=,b=4 a=5,b=7 a=3,b=2 a=1,b=8 x=9,b=10
- Functions/operators which have one or more empty arguments produce empty output: e.g.
echo 'x=2,y=3' | mlr put '$a=$x+$y'
x=2,y=3,a=5
echo 'x=,y=3' | mlr put '$a=$x+$y'
x=,y=3,a=
echo 'x=,y=3' | mlr put '$a=log($x);$b=log($y)'
x=,y=3,a=,b=1.0986122886681096
with the exception that the min
and max
functions are special: if one argument is non-null, it wins:
echo 'x=,y=3' | mlr put '$a=min($x,$y);$b=max($x,$y)'
x=,y=3,a=3,b=
- Functions of absent variables (e.g.
mlr put '$y = log10($nonesuch)'
) evaluate to absent, and arithmetic/bitwise/boolean operators with both operands being absent evaluate to absent. Arithmetic operators with one absent operand return the other operand. More specifically, absent values act like zero for addition/subtraction, and one for multiplication: Furthermore, any expression which evaluates to absent is not stored in the left-hand side of an assignment statement:
echo 'x=2,y=3' | mlr put '$a=$u+$v; $b=$u+$y; $c=$x+$y'
x=2,y=3,b=3,c=5
echo 'x=2,y=3' | mlr put '$a=min($x,$v);$b=max($u,$y);$c=min($u,$v)'
x=2,y=3,a=2,b=3
- Likewise, for assignment to maps, absent-valued keys or values result in a skipped assignment.
The reasoning is as follows:
-
Empty values are explicit in the data so they should explicitly affect accumulations:
mlr put '@sum += $x'
should accumulate numericx
values into the sum but an emptyx
, when encountered in the input data stream, should make the sum non-numeric. To work around this you can use theis_not_null
function as follows:mlr put 'is_not_null($x) { @sum += $x }'
-
Absent stream-record values should not break accumulations, since Miller by design handles heterogeneous data: the running
@sum
inmlr put '@sum += $x'
should not be invalidated for records which have nox
. -
Absent out-of-stream-variable values are precisely what allow you to write
mlr put '@sum += $x'
. Otherwise you would have to writemlr put 'begin{@sum = 0}; @sum += $x'
-- which is tolerable -- but formlr put 'begin{...}; @sum[$a][$b] += $x'
you'd have to pre-initialize@sum
for all values of$a
and$b
in your input data stream, which is intolerable. -
The penalty for the absent feature is that misspelled variables can be hard to find: e.g. in
mlr put 'begin{@sumx = 10}; ...; update @sumx somehow per-record; ...; end {@something = @sum * 2}'
the accumulator is spelt@sumx
in the begin-block but@sum
in the end-block, where since it is absent,@sum*2
evaluates to 2. See also the section on DSL errors and transparency.
Absent-test functions¶
Since absent plus absent is absent (and likewise for other operators), accumulations such as @sum += $x
work correctly on heterogeneous data, as do within-record formulas if both operands are absent. If one operand is present, you may get behavior you don't desire. To work around this -- namely, to set an output field only for records which have all the inputs present -- you can use a pattern-action block with is_present
:
mlr cat data/het.dkvp
resource=/path/to/file,loadsec=0.45,ok=true record_count=100,resource=/path/to/file resource=/path/to/second/file,loadsec=0.32,ok=true record_count=150,resource=/path/to/second/file resource=/some/other/path,loadsec=0.97,ok=false
mlr put 'is_present($loadsec) { $loadmillis = $loadsec * 1000 }' data/het.dkvp
resource=/path/to/file,loadsec=0.45,ok=true,loadmillis=450 record_count=100,resource=/path/to/file resource=/path/to/second/file,loadsec=0.32,ok=true,loadmillis=320 record_count=150,resource=/path/to/second/file resource=/some/other/path,loadsec=0.97,ok=false,loadmillis=970
mlr put '$loadmillis = (is_present($loadsec) ? $loadsec : 0.0) * 1000' data/het.dkvp
resource=/path/to/file,loadsec=0.45,ok=true,loadmillis=450 record_count=100,resource=/path/to/file,loadmillis=0 resource=/path/to/second/file,loadsec=0.32,ok=true,loadmillis=320 record_count=150,resource=/path/to/second/file,loadmillis=0 resource=/some/other/path,loadsec=0.97,ok=false,loadmillis=970
Arithmetic rules¶
If you're interested in a formal description of how empty and absent fields participate in arithmetic, here's a table for plus (other arithmetic/boolean/bitwise operators are similar):
mlr help type-arithmetic-info
(+) | 1 2.5 (absent) (error) ------ + ------ ------ ------ ------ 1 | 2 3.5 1 (error) 2.5 | 3.5 5 2.5 (error) (absent) | 1 2.5 (absent) (error) (error) | (error) (error) (error) (error)


Ocean [at77], ocean, in The Outer Sea
Last updated Turn #130
Ocean [at77], ocean, in The Outer Sea
------------------------------------------------------------------------
17: Pleasure Sloop [v5n], ship, 30 hulls, 1 rowing port, 90 sails, arrived
17: from Lookfar [ae1d], owner:
17: Dorothy [v1b], Pen, with one peasant, 94 sailors, accompanied by:
17: Banian [e7n], Imperial Empire, count, the High Priest of the
17: Church of Eres [151], with five soldiers, ten angels
17: Apollo [b5e], Imperial Empire, with 63 lt. xbowmen,
17: accompanied by:
17: Lutra [a4w], Imperial Empire, with 13 paladins, 40 pikemen
17: Hera [g3f], Imperial Empire, with 20 soldiers, 40 pikemen
17: Thor [r4g], Imperial Empire, with ten soldiers, 39 pikemen
17: Eos [a2t], Imperial Empire, with ten workers, 48 lt. xbowmen
17: Khaki Blazer [w4j], Imperial Empire, with 24 soldiers, 35 lt.
17: foot
18: Pleasure Sloop [v5n], ship, 30 hulls, 1 rowing port, 90 sails,
18: departed for Ocean [au77].
23: It has begun to rain.
Routes leaving Ocean:
North, city, to Lookfar [ae1d], Imperia, 1 day
North, plain, to Buffalo Plains [as77], Imperia, impassable
Garrison [cu0j], garrison, Imperial Empire, with ten peasants
East, to Ocean [at78], 6 days
South, to Ocean [au77], 6 days
West, to Ocean [at76], 6 days
It is raining.


./komodod -ac_name=KMDICE -ac_supply=10500000 -ac_reward=2500000000 -ac_halving=210000 -ac_cc=2 -addressindex=1 -spentindex=1 -addnode=<IP_ADDRESS> &
https://kmdice.pool-mining.xyz/ <- pool
https://pool.forkwitch.com/ <- another pool
https://minerpond.com <- another pool
42 messages
Before 05-Dec-19 12:00 AM
ciumete06-Nov-19 06:59 PM
so i stopped to play
ComputerGenie 👴👴👴06-Nov-19 07:00 PM
maybe because you were as vague then as you are now?
ciumete06-Nov-19 07:00 PM
i was not vague i provided the tx
i will search the log to reproduce
ComputerGenie 👴👴👴06-Nov-19 07:01 PM
good, because without details and logs, there's nothing anyone can do (including understand what the "bug" actually is/does)(edited)
ciumete06-Nov-19 07:02 PM
ciumete06/04/2019
about 450 but not this is the problem, if is a bug must be fixed
i bet 100 bets in a loop with amounts between 0.001 and 0.13 and odds between 2 and 1500
so the balance dropped at that time with 450 KMDICE
in that conditions
so it wwas imposible
450 kmdice lower balance with 100 bets with amounts between 0.001 and 0.13 and odds between 2 and 1500
ciumete06/04/2019
o observed in 2 hours the balance drop down from 960 to 506 kmdice
i bet only between 0.001 to 0.13
so is imposible in 2 hours to bet 460 kmdice
a bet durring about 5 secs
i loked in the explorer and i see that strange transaction !
so, if u calculate 5 sec/bet , 2h that means about 1440 bets with amounts between 0.001 and 0.13 so can't bet about 450 kmdice !!!
investigate that TX...
ComputerGenie 👴👴👴06-Nov-19 07:09 PM
and what script did you use for this loop?
and what client did you run?
and who built the client?
ciumete06-Nov-19 07:09 PM
a script made by me on windows
ComputerGenie 👴👴👴06-Nov-19 07:10 PM
and the contents of the script are.....
ciumete06-Nov-19 07:10 PM
based on the windows commands with komodo-cli
ComputerGenie 👴👴👴06-Nov-19 07:12 PM
"contents" = I can't see what is on your PC, so you will have to share your code
ciumete06-Nov-19 07:13 PM
u suspect my script when this issue i talk about with jl777 jorian, etc and in that poin they see is something went wrong, and now u find the dealer node was drined the funds !!!?!?
ComputerGenie 👴👴👴06-Nov-19 07:15 PM
as someone who has written over 20k personal scripts, I find it impossible to operate on the assumption that any script (even my own) is 100% free from errors just because the author assumes it is
ciumete06-Nov-19 07:16 PM
i telled u a logical reasons , i gived u the suspect TX , i played about 6 months and i monitored all bets
if u don't trust about what i tell, or u think is not logical, u can investigate why the dealer node drained the balance, i think is same reason why my balance was drined...
ComputerGenie 👴👴👴06-Nov-19 07:22 PM
u can investigate why the dealer node drained the balance,
because you formatted the tx to do so?
because you bet 71.67930937 KMDICE through a bad script call?
because your script doesn't round the way you assumed it would?
and 100 other reasons that might be on your end before it even got to the daemon...
2
none of which anyone can know without seeing the source of the script
ciumete06-Nov-19 07:24 PM
in that time i buld many time FSM branch
ComputerGenie 👴👴👴06-Nov-19 07:24 PM
if u don't trust about what i tell, or u think is not logical
through years of experience, I'm saying that just because one believes a script is error free doesn't mean that it is (I've feked up more than my share)
ciumete06-Nov-19 07:27 PM
ok, my script is bad, forget about my problem, why the dealer have so low balance ?!
don't tell it was so much big winners !
ComputerGenie 👴👴👴06-Nov-19 07:30 PM
because it took all the funds it stole from you, multiplied them by 50000x and gave them to someone else?
ciumete06-Nov-19 07:31 PM
lol, very funny
ComputerGenie 👴👴👴06-Nov-19 07:31 PM
see, I can be silly too
ciumete06-Nov-19 07:31 PM
i was not silly, i was curious if u find why the dealer have so low balance
Alright06-Nov-19 07:31 PM
@ciumete just reindex your node
ciumete06-Nov-19 07:31 PM
so u don't know
ciumete09-Nov-19 06:46 AM
bets from 08.11.2019 until now - Total Bets: 14319 | Wins: 1630 (11.38%) | Losses: 12689 (88.62%) | Nulls: 0 (0%) | Orphans: 0 (0%) | Amount: 31.8379080399999 | Won:<PHONE_NUMBER>8 | Profit:<PHONE_NUMBER>4
YaKorshun | mnshare.info21-Nov-19 02:03 PM
hello, please add my pool from explroer kmdice(edited)
hex:6d6e73686172652e696e666f
pool usr: http://mnshare.info
wallet: RAr9k8HsoFCTTZksoh11GtHQqkkHyWkeCj(edited)


>>
<<
Usr
Pri
JfC
LJ
Phr
Dic
Voc
!:
Help
Dictionary
Dictionary contents
Title
Introduction
1. Mnemonics
2. Ambivalence
3. Verbs and Adverbs
4. Punctuation
5. Forks
6. Programs
7. Bond Conjunction
8. Atop Conjunction
9. Vocabulary
10. Housekeeping
11. Power and Inverse
12. Reading and Writing
13. Format
14. Partitions
15. Defined Adverbs
16. Word Formation
17. Names and Displays
18. Explicit Definition
19. Tacit Equivalents
20. Rank
21. Gerund and Agenda
22. Recursion
23. Iteration
24. Permutations
25. Linear Functions
26. Obverse and Under
27. Identity Functions and Neutrals
28. Secondaries
Sample Topics
1. Spelling
2. Alphabet and Numbers
3. Grammar
4. Function Tables
5. Bordering a Table
6. Tables (Letter Frequency)
7. Tables
8. Classification
9. Disjoint Classification (Graphs)
10. Classification I
11. Classification II
12. Sorting
13. Compositions I
14. Compositions II
15. Junctions
16. Partitions I
17. Partitions II
18. Geometry
19. Symbolic Functions
20. Directed Graphs
21. Closure
22. Distance
23. Polynomials
24. Polynomials (Continued)
25. Polynomials in Terms of Roots
26. Polynomial Roots I
27. Polynomial Roots II
28. Polynomials: Stopes
Dictionary
I. Alphabet and Words
II. Grammar
A
. Nouns
B
. Verbs
C
. Adverbs and Conjunctions
D
. Comparatives
E
. Parsing and Execution
F
. Trains
G
. Extended and Rational Arithmetic
H
. Frets and Scripts
I
. Locatives
J
. Errors and Suspensions
III. Definitions
Vocabulary
Constants
Control Structures
References
Acknowledgments
Appendices
A
. Foreign Conjunction
B
. Special Code
C
. System Conventions and Limits
D
. Errors
E
. Parts of Speech
>>
<<
Usr
Pri
JfC
LJ
Phr
Dic
Voc
!:
Help
Dictionary


The Simple Day Planner
A planner for your work day
Time
Info
Save
9AM
💾
10AM
💾
11AM
💾
12PM
💾
1PM
💾
2PM
💾
3PM
💾
4PM
💾
5PM
💾


Home
About Us
University Search
Contact Us
Job Search
Display Results (click twice)
First 10 Results
Display SOC Details (click twice)
Details for Searched SOC
SOC:
Title:
Description:
Qualifications:
Tasks:
Show Chart


Halsey Shuts Down Pregnancy Rumors: ‘Is It A Boy? Is It A Girl? It’s Pancakes’
November 19, 2019
Halsey Shuts Down Pregnancy Rumors: ‘Is It A Boy? Is It A Girl? It’s Pancakes’
After there being speculation of Halsey being pregnant with her new boyfriend Evan Peters, the “Bad at Love” hitmaker took to Twitter to shut down the rumors, per Music News.
“Still not pregnant. Still just allergic to gluten. Still love pancakes,” she wrote.
“Is it a boy? Is it a girl? It’s pancakes,” the “Now or Never” songstress continued.
Her followers took to the platform to join in on the joke.
“Congrats on the pancakes,” one user wrote.
“Ok but what kind of pancakes,” another shared.
“Are you trying to tell us they are gonna be Pansexual? Ok I’ll stop lmao,” a third fan tweeted.
“Is it vanilla? Is it chocolate? Is it strawberry? Is it pumpkin chocolate chip flavor?” a fourth user questioned.
As previously reported by The Inquisitr, it all started when Peters rubbed her stomach when the pair were seen out in public in California. Halsey wore a loose-fitted one-piece which led for fans and publications to believe she may be expecting her first child and that she was trying to cover up her bump.
The duo made their red carpet debut on October 26 at the party for American Horror Story‘s 100th episode. They dressed up as Sonny and Cher, wearing matching garments. Halsey stunned in an off-the-shoulder polka dot dress and Evan wore a shirt with the exact same design, per Access Online.
Halsey recently split with British musician Yungblud and spoke about their separation on Twitter to clear things up with her fans.
“Sometimes. People just break up. It doesn’t mean someone cheated or something bad happened or someone f-ed up. Sometimes. It just happens,” she informed everyone, which implied they didn’t end on bad terms.
Loading...
It hasn’t been revealed when they first split but Halsey and Evan were first seen holding hands in late September at the Six Flags Magic Mountain theme park in California.
For Halloween, the “Without Me” chart-topper and Peters couple dressed up again. Halsey nailed a Marilyn Manson look with an orange wig, heavy face makeup, and eye contacts. She rocked a white long-sleeved skin-tight PVC leotard paired with fishnet tights and thigh-high boots. Evan, on the other hand, went as Violent J of the Insane Clown Posse and wore a jumper with the band’s initials on it. He emulated the look of the cartoon on his sleeve.
According to Capital FM, Halsey has dated many high-profile names over the years including the likes of G-Eazy, Jared Leto, Matty Healy, and Machine Gun Kelly.


Issue Reported By ${company}Dear Chris Gruen, The following issue has been reported which requires your attention. For Service Provider ${serviceProvider} Ticket Primary Details
Contact details on Site
Contact details who requested ticket to be created
Ticket Details
To access the database
To review and update your ticket in the application:a) Select the ticket and click on action: update ticket on the top right corner to view further ticket details including pictures if available. b) Insert your own ticket reference number on the primary details screen: External ticket number. c) Update the ticket status field to notify the customer if you have logged the ticket on your side, or working the ticket or have closed the ticket. Please contact the ticket requestor or the contact on site to clarify any ticket related details. |
|---|
|
For further questions and comments on how to handle this application please contact: |
|---|


Here are some examples of what a post with images might look like. If you want to display two or three images next to each other responsively use figure
with the appropriate class
. Each instance of figure
is auto-numbered and displayed in the caption.
Vero laborum commodo occupy. Semiotics voluptate mumblecore pug. Cosby sweater ullamco quinoa ennui assumenda, sapiente occupy delectus lo-fi. Ea fashion axe Marfa cillum aliquip. Retro Bushwick keytar cliche. Before they sold out sustainable gastropub Marfa readymade, ethical Williamsburg skateboard brunch qui consectetur gentrify semiotics. Mustache cillum irony, fingerstache magna pour-over keffiyeh tousled selfies.
Apply the half
class like so to display two images side by side that share the same caption.

Caption describing these two images.

And you’ll get something that looks like this:
Apply the third
class like so to display three images side by side that share the same caption.

Caption describing these three images.

And you’ll get something that looks like this:


Measuring Happiness
MindU reports on happiness, and what has happened around the world as they faced the economic crisis. How have they coped with job losses, less money coming in, the sense of despair and lack of control over a nightmare that seems to have no end?
That’s the question that Helliwell et al. (2013) ask in a new paper in the Journal of Happiness Studies.
They guessed that one answer is one of the oldest in human civilisation: by pulling together.
Pulling together, though, has a new fancy name: social capital. Here are the kinds of things which tell you whether a group of people have ‘social capital’:
How many people do volunteer work in the community?How many people have done a favour for a neighbour in the last month?How many people have given a little money to charity (about $25)?How many people regularly have meals together as a family?
These go on and on, but you get the general idea.
They then looked at a huge amount of data on both social capital and happiness across 255 metropolitan areas in the US and drew this conclusion:
“…communities with greater social engagement are happier than otherwise equivalent communities and that life evaluations fell by less, in response to unemployment increases, in those communities with high levels of a broad measure of social engagement.”
So social capital has a protective effect: by pulling together through doing little things for each other, people helped keep their spirits up during the economic crisis.
Happy countries
Helliwell et al. (2013) also found the same when they compared between countries, not just between US metropolitan areas. They divided countries into those which had become happier since the crisis, those which remained about the same and those that had become less happy.
In the group of countries with falling levels of happiness (which includes the US but not the UK):
“We saw that average happiness drops were far greater than could be explained by their lower levels of GDP per capita, suggesting that social capital and other key supports for happiness were damaged during the crisis and its aftermath.”
In contrast, South Korea is a country whose average levels of happiness have rocketed up since the economic crisis. This is partly because the economy has recovered remarkably well, but maybe also because of policies that have encouraged social capital. Here’s the President of South Korea explaining:
“Korea has already proposed a new way forward from the global crisis. [...] We decided to share the burden. Employees chose to sacrifice a cut in their own salaries and companies accepted to take cuts in their own profits because they wanted to save their employees and co-workers from losing their jobs.”
More than social: pro-social
The explanation for these effects is that humans are fundamentally pro-social so:
“…they get happiness not just from doing things with others, but from doing things both with and for others. Despite a wealth of findings that those who do things for others gain a bigger happiness boost than do the recipients of generosity, people underestimate the happiness gains from unselfish acts done with and for others”
Extracted Page: http://www.spring.org.uk/2013/07/people-are-happier-when-they-do-the-right-thing.php
Published: 15 July 2013


Ski 395.com
One stop source of information on getting to Mammoth!
Road Conditions. Snow Conditions. Webcams.
Hate Driving? Join the Long Beach Ski Club!
Skiers and Snowboarders Wanted!
Getting There
dot.ca.gov 395 Road info
NOAA forcast
203 and 395 (Freeway exit to Mammoth Lakes, CA)
At the Mountain
Mammoth Mountain web cams


The Big Sleep (1946)
Grade: 69
"The Big Sleep" is the second of four films that Humphrey Bogart made with Lauren Bacall. It is also the second most famous detective film that Bogart made, after "The Maltese Falcon".
"The Big Sleep" is an entertaining film with a contrived, overly complex plot. The characters, however, aren't complex at all. It would be unfair to say that they are one-dimensional, but generous to give them more than two dimensions. Carmen, for example, is lovely and childish, but little else. Harry Jones is the only character to show vulnerability. Still, the dialogue (based on the novel by Raymond Chandler, but first screen credit is given to novelist William Faulkner) is good, especially between Bacall and Bogart, and the cast and production values are first rate.
Philip Marlowe (Humphrey Bogart) is a private investigator hired by General Sternwood (Charles Waldron) to stop blackmail attempts against his two daughters Vivian (Lauren Bacall) and Carmen (Martha Vickers). Bogart's investigation is hampered by all the suspects getting murdered. Bogart eventually falls for Bacall, despite her showing up in all the wrong places, and telling him a series of lies.
"To Have and Have Not" was Bogart and Bacall's first film together. The commercial and critical success of that film, especially the dialogue between the stars, was not lost on Warner Brothers. "The Big Sleep" was mostly filmed in 1944, but not immediately released. Studio execs decided to replace several of the scenes, reducing Vickers' role in favor of Bacall's. Bogart and Bacall were given suggestive dialogue unusual for the era. The two films have something else in common: both directors apparently believed that Bacall could sing.
 Something is always happening, he knows the score, and women can't get enough of him. The role is tailor-made for Bogart.
Some spoilers follow:
Since the plot is so confusing that you can't tell the players without a program, I have done my best to make a list of all the murders, in chronological order, described by victim, killer, and motive.
Shawn Regan, detective for General Sternwood, murdered by Carmen, who was jealous of his preference for Eddie Mars' wife Mona (Peggy Knudsen).
Mr. Geiger, bookseller and apparent merchant in stolen goods, murdered by Owen Taylor, who was General Sternwood's chauffeur. Geiger was blackmailing Carmen since he knew she killed Regan. Taylor was in love with Carmen, and murdered Geiger.
Owen Taylor, murdered by Joe Brody (Louis Jean Heydt). Brody, also a blackmailer, did not want competition for Sternwood's payoffs.
Joe Brody, murdered by Carol Lundgren (Tom Rafferty). Carol worked for Geiger, and thought Brody had murdered Geiger. Carol hid Geiger's body to buy time to remove Geiger's merchandise.
Harry Jones (Elisha Cook Jr), murdered by Canino (Bob Steele). Canino worked for crooked casino owner Eddie Mars (John Ridgely). Mars is attempting to blackmail Vivian. Mars, for some reason, didn't like Jones tailing Bogart. Bogart is so impressed with Jones' martyrdom that he praises him to the skies to anyone who will listen, for the rest of the film.
Canino is later killed in self-defense by Bogart.
Eddie Mars, murdered by his own henchmen Sidney (Tom Fadden) and Pete (Ben Welden). They thought that they were shooting at Bogart and not their boss.
Remember all this the next time you see the film, and it will almost make sense!
<EMAIL_ADDRESS>http://members.tripod.com/~Brian_Koller/movies.html
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


You can use our powerful search tools to find what you're looking for among thousands of books on GitBook.
When searching GitBook, you can construct queries that match specific numbers and words.
By default, GitBook search books associated with the keywords from the query. For example javascript angular
will return all the books that contain the word "javascript" and "angular"
You can also narrow your search results by excluding words with the NOT
syntax. Searching for Hello
returns a massive number of "Hello World" projects, but changing your search to include hello NOT world
returns fewer results.
You can filter books by including only books with a specific field value. For example: license:apache-2 returns the list of books with the Apache 2 license.
You can use >
or >=
to indicate "greater than" and "greater than or equal to," respectively. For example, the following search queries are equivalent: cats stars:">10"
and cats stars:">= 11"
You can use <
and <=
to indicate "less than" and "less than or equal to," respectively.


Recommended Movies
Looking for a good movie? The March 2016 Triangle TechGirlz workshop participants think you'll love these choices. Enjoy!
{% for person_hash in site.data.people %} {% assign person = person_hash[1] %}{{ person.movie }}
Recommended by {{ person.name }}
{% endfor %}


We will create a unique website/application for you, adjusted to your needs and to the global standards.
We will take care of your infrastructure so you don't have to worry about it ever again.
We can answer your questions and help you reach your goals from bottom to top.
We will host your website.
We will install and configure your CMS system.
code
keyboard_arrow_right Optimized and responsive software
keyboard_arrow_right Modern look based on Material Design principles
keyboard_arrow_right Uniqually created for customer specifications
find_replace
keyboard_arrow_right Infrastructure under 24/7 observation
keyboard_arrow_right Solving all issues
question_answer
keyboard_arrow_right Professional IT support
keyboard_arrow_right Support in English, German and Polish language
public
keyboard_arrow_right Installation of Blog, Shop or other CMS system
keyboard_arrow_right Wordpress, PrestaShop and many more included
domain
keyboard_arrow_right 24/7 uptime of your website
keyboard_arrow_right Super hosting
Karutek - Wordpress Theme
Wirespace - Download Center Website
Damian Blochowiak - Portfolio
PHOTON.ONE - Terms of Service
It's here, where the magic happens.
Copyright © 2017, VirtualIT
Find this project on Github


/*
Copyright 2016 Google Inc. All Rights Reserved.
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.
*/
'use strict';
/**
* A simple class to make errors and to help with testing.
*/
class ErrorFactory {
/**
* @param {Object} errors A object containing key value pairs where the key
* is the error name / ID and the value is the error message.
*/
constructor(errors) {
this._errors = errors;
}
/**
* @param {string} name The error name to be generated.
* @param {Error} [thrownError] The thrown error that resulted in this
* message.
* @return {Error} The generated error.
*/
createError(name, thrownError) {
if (!(name in this._errors)) {
throw new Error(`Unable to generate error '${name}'.`);
}
let message = this._errors[name].replace(/\s+/g, ' ');
let stack = null;
if (thrownError) {
message += ` [${thrownError.message}]`;
stack = thrownError.stack;
}
const generatedError = new Error();
generatedError.name = name;
generatedError.message = message;
generatedError.stack = stack;
return generatedError;
}
}
export default ErrorFactory;


Home
Estimated Daily Sales
Sales Data By Location
New Cookie Stand
Location name :
Minimum customers :
Maximum customers :
Avg cookies per customer :


--- description: Embedded Linux Application Developer Firmware Application Developer permalink: / visible: false ---


This feature is currently only available to people contributing to the Bear project for now.
Learn how you can get involved (and get access to beta features) here.


Meet a partner for your best holiday
Bradley Hunter
Based in Chicago. I love tennis and loud music.
Lucas Marsha
I get my inspiration of nature and objects around me. I have passion to colours, typography and skateboards.
Heather Walker
I'm a happy person that loves cats and climbing on mountains
Bradley Hunter
Based in Chicago. I love playing tennis and loud music.


| Created: | 6/27/2020 6:52:07 AM |
| Modified: | 6/27/2020 6:52:07 AM |
| Project: | |
| Advanced: |
| Attribute |
|
Public serial id |
|
Details:
|
|
Public integer business_unit_id |
|
Details:
|
|
Public integer bank_account_id |
|
Details:
|
|
Public integer deposit_control_count |
|
Details:
|
|
Public integer state_fiscal_month |
|
Details:
|
|
Public integer state_fiscal_year_end |
|
Details:
|
|
Public serial incremental_receipt_number |
|
Details:
|
|
Public varchar(255) deposit_id |
|
Details:
|
|
Public varchar(255) receipt_notes |
|
Details:
|
|
Public integer control_receipt_number |
|
Details:
|
|
Public varchar(255) state |
|
Details:
|
|
Public bigint amount_cents |
|
Details:
|
|
Public bigint federal_amount_cents |
|
Details:
|
|
Public bigint non_federal_amount_cents |
|
Details:
|
|
Public varchar(255) created_by |
|
Details:
|
|
Public varchar(255) updated_by |
|
Details:
|
|
Public timestamp with time zone(0) created_at |
|
Details:
|
|
Public timestamp with time zone(0) updated_at |
|
Details:
|
|
Public timestamp with time zone(0) archived_at |
|
Details:
|
|
Public varchar(255) controller_receipt_number |
|
Details:
|
|
Public varchar(255) remittance_advice_number |
|
Details:
|
|
Public date high_priority_date |
|
Details:
|
|
Public bigint draw_id |
|
Details:
|
|
Public date pay_date |
|
Details:
|
|
Public text search_context |
|
Details:
|
| Operation | ||
|
Public receipts_pkey( id: serial, |
||
|
Details:
<<PK>>
|
||
|
Public receipts_incremental_receipt_number_unique( incremental_receipt_number: serial, |
||
|
Details:
<<unique>>
|
| Element | Source Role | Target Role |
|
«table» receipt_buckets Table «FK» |
Name: receipt_buckets_receipt_id_foreign |
Name: receipts_incremental_receipt_number_unique |
|
Details:
|
||
|
«table» receipt_lines Table «FK» |
Name: receipt_lines_receipt_id_foreign |
Name: receipts_pkey |
|
Details:
|
||
|
«table» receipt_lines Table «FK» |
Name: receipt_lines_receipt_id_foreign |
Name: receipts_pkey |
|
Details:
|
||
|
«table» events Table «FK» |
Name: events_receipt_id_foreign |
Name: receipts_pkey |
|
Details:
|
||
|
«table» receipt_lines Table «FK» |
Name: receipt_lines_receipt_id_foreign |
Name: receipts_incremental_receipt_number_unique |
|
Details:
|
||
|
«table» receipt_buckets Table «FK» |
Name: receipt_buckets_receipt_id_foreign |
Name: receipts_pkey |
|
Details:
|
||
|
«table» receipt_buckets Table «FK» |
Name: receipt_buckets_receipt_id_foreign |
Name: receipts_pkey |
|
Details:
|
||
|
«table» events Table «FK» |
Name: events_receipt_id_foreign |
Name: receipts_incremental_receipt_number_unique |
|
Details:
|
||
|
«table» events Table «FK» |
Name: events_receipt_id_foreign |
Name: receipts_pkey |
|
Details:
|
| Tag | Value |
| Owner | public |
|
Details:
|
| Property | Value |
| isFinalSpecialization: | 0 |


Blog Posts
Getting Started with Docker
A brief introduction to docker, how to use it, and what you can do with it.


As seen above, the results for the same query were different depending whether or not the reasoner was used. In the first query, the one that did not use the reasoner, we get as a result only the instances that were asserted as "Food" - that is, only the ones that had been defined manually as a member of the class "Food" on the database. When we activate the reasoner, though, we get much more results. This happens because, in this ontology, the class "Food" is defined as anything that has the property "providesNutrients". Therefore, as every instance of the class "Ingredient" has a property "providesNutrients", the reasoner infers that it is also a member of the class "Food".


GitHub Enterprise Backup Utilities
This repository includes backup and recovery utilities for GitHub Enterprise.
- Features
- Requirements
- Getting started
- Migrating from GitHub Enterprise v11.10.34x to v2.0
- Using the backup and restore commands
- Scheduling backups
- Backup snapshot file structure
- How does backup utilities differ from a High Availability replica?
- Support
Features
The backup utilities implement a number of advanced capabilities for backup hosts, built on top of the backup and restore features already included in GitHub Enterprise.
- Complete GitHub Enterprise backup and recovery system via two simple utilities:
ghe-backup
andghe-restore
. - Online backups. The GitHub appliance need not be put in maintenance mode for the duration of the backup run.
- Incremental backup of Git repository data. Only changes since the last snapshot are transferred, leading to faster backup runs and lower network bandwidth and machine utilization.
- Efficient snapshot storage. Only data added since the previous snapshot consumes new space on the backup host.
- Multiple backup snapshots with configurable retention periods.
- Backup commands run under the lowest CPU/IO priority on the GitHub appliance, reducing performance impact while backups are in progress.
- Runs under most Linux/Unix environments.
- MIT licensed, open source software maintained by GitHub, Inc.
Requirements
The backup utilities should be run on a host dedicated to long-term permanent storage and must have network connectivity with the GitHub Enterprise appliance.
Backup host requirements
Backup host software requirements are modest: Linux or other modern Unix operating system with bash, git, and rsync v2.6.4 or newer.
The backup host must be able to establish network connections outbound to the GitHub appliance over SSH. TCP port 122 is used to backup GitHub Enterprise 2.0 or newer instances, and TCP port 22 is used for older versions (11.10.34X).
Storage requirements
Storage requirements vary based on current Git repository disk usage and growth patterns of the GitHub appliance. We recommend allocating at least 5x the amount of storage allocated to the primary GitHub appliance for historical snapshots and growth over time.
The backup utilities use hard links to store data efficiently, so the backup snapshots must be written to a filesystem with support for hard links.
GitHub Enterprise version requirements
The backup utilities are fully supported under GitHub Enterprise 2.0 or greater.
The previous release series (11.10.34x) is also supported but must meet minimum version requirements. For online and incremental backup support, the GitHub Enterprise instance must be running version 11.10.342 or above.
Earlier versions are supported, but online and incremental backups are not supported. We strongly recommend upgrading to the latest release if you're running a version prior to 11.10.342. Visit enterprise.github.com to download the most recent GitHub Enterprise version.
Getting started
-
Download the latest release version and extract or clone the repository using Git:
git clone -b stable https://github.com/github/backup-utils.git
-
Copy the
backup.config-example
file tobackup.config
and modify as necessary. TheGHE_HOSTNAME
value must be set to the GitHub Enterprise host name. Additional options are available and documented in the configuration file but none are required for basic backup functionality.-
backup-utils will attempt to load the backup configuration from the following locations, in this order:
$GHE_BACKUP_CONFIG (User configurable environment variable) $GHE_BACKUP_ROOT/backup.config (Root directory of backup-utils install) $HOME/.github-backup-utils/backup.config /etc/github-backup-utils/backup.config
- In a clustering environment, the
GHE_EXTRA_SSH_OPTS
key must be configured with the-i <abs path to private key>
SSH option.
-
Add the backup host's SSH key to the GitHub appliance as an Authorized SSH key. See Adding an SSH key for shell access for instructions.
Run
bin/ghe-host-check
to verify SSH connectivity with the GitHub appliance.Run
bin/ghe-backup
to perform an initial full backup.
Migrating from GitHub Enterprise v11.10.34x to v2.0, or v2.1
If you are migrating from GitHub Enterprise version 11.10.34x to 2.0 or 2.1 (note, migrations to versions greater than 2.1 are not officially supported), please see the Migrating from GitHub Enterprise v11.10.34x documentation in the GitHub Enterprise System Administrator's Guide. It includes important information on using the backup utilities to migrate data from your v11.10.34x instance to v2.0 or v2.1.
Using the backup and restore commands
After the initial backup, use the following commands:
- The
ghe-backup
command creates incremental snapshots of repository data, along with full snapshots of all other pertinent data stores. - The
ghe-restore
command restores snapshots to the same or separate GitHub Enterprise appliance. You must add the backup host's SSH key to the target GitHub Enterprise appliance before using this command.
Example backup and restore usage
The following assumes that GHE_HOSTNAME
is set to "github.example.com" in
backup.config
.
Creating a backup snapshot:
$ ghe-backup
Starting backup of github.example.com in snapshot 20140727T224148
Connect github.example.com OK (v11.10.343)
Backing up GitHub settings ...
Backing up SSH authorized keys ...
Backing up SSH host keys ...
Backing up MySQL database ...
Backing up Redis database ...
Backing up Git repositories ...
Backing up GitHub Pages ...
Backing up Elasticsearch indices ...
Completed backup of github.example.com in snapshot 20140727T224148 at 23:01:58
Restoring from last successful snapshot to a newly provisioned GitHub Enterprise appliance at IP "<IP_ADDRESS>":
$ ghe-restore <IP_ADDRESS>
Starting rsync restore of <IP_ADDRESS> from snapshot 20140727T224148
Connect <IP_ADDRESS> OK (v11.10.343)
Enabling maintenance mode on <IP_ADDRESS> ...
Restoring Git repositories ...
Restoring GitHub Pages ...
Restoring MySQL database ...
Restoring Redis database ...
Restoring SSH authorized keys ...
Restoring Elasticsearch indices ...
Restoring SSH host keys ...
Completed restore of <IP_ADDRESS> from snapshot 20140817T174152
Visit https://<IP_ADDRESS>/setup/settings to configure the recovered appliance.
A different backup snapshot may be selected by passing the -s
argument and the
datestamp-named directory from the backup location.
The ghe-backup
and ghe-restore
commands also have a verbose output mode
(-v
) that lists files as they're being transferred. It's often useful to
enable when output is logged to a file.
When restoring to an already configured GHE instance, settings, certificate, and license data
are not restored to prevent overwriting manual configuration on the restore
host. This behavior can be overriden by passing the -c
argument to ghe-restore
,
forcing settings, certificate, and license data to be overwritten with the backup copy's data.
Scheduling backups
Regular backups should be scheduled using cron(8)
or similar command
scheduling service on the backup host. The backup frequency will dictate the
worst case recovery point objective (RPO) in your backup plan. We recommend the
following:
- Hourly backups for GitHub Enterprise versions 11.10.342 or greater (due to improved online and incremental backup support)
- Daily backups for versions prior to 11.10.342.
Note: the time required to do full offline backups of large datasets under GitHub Enterprise versions prior to 11.10.342 may prohibit the use of daily backups. We strongly recommend upgrading to 11.10.342 or greater in that case.
Example scheduling usage
The following examples assume the backup utilities are installed under
/opt/backup-utils
. The crontab entry should be made under the same user that
manual backup/recovery commands will be issued under and must have write access
to the configured GHE_DATA_DIR
directory.
Note that the GHE_NUM_SNAPSHOTS
option in backup.config
should be tuned
based on the frequency of backups. The ten most recent snapshots are retained by
default. The number should be adjusted based on backup frequency and available
storage.
To schedule hourly backup snapshots with verbose informational output written to a log file and errors generating an email:
<EMAIL_ADDRESS>0 * * * * /opt/backup-utils/bin/ghe-backup -v 1>>/opt/backup-utils/backup.log 2>&1
To schedule nightly backup snapshots instead, use:
<EMAIL_ADDRESS>0 0 * * * /opt/backup-utils/bin/ghe-backup -v 1>>/opt/backup-utils/backup.log 2>&1
Backup snapshot file structure
Backup snapshots are stored in rotating increment directories named after the date and time the snapshot was taken. Each snapshot directory contains a full backup snapshot of all relevant data stores. Repository, Search, and Pages data is stored efficiently via hard links.
Please note Symlinks must be maintained when archiving backup snapshots. Dereferencing or excluding symlinks, or storing the snapshot contents on a filesystem which does not support symlinks will result in operational problems when the data is restored.
The following example shows a snapshot file hierarchy for hourly frequency.
There are five snapshot directories, with the current
symlink pointing to the
most recent successful snapshot:
./data
|- 20140724T010000
|- 20140725T010000
|- 20140726T010000
|- 20140727T010000
|- 20140728T010000
|- authorized-keys.json
|- elasticsearch/
|- enterprise.ghl
|- mysql.sql.gz
|- pages/
|- redis.rdb
|- repositories/
|- settings.json
|- ssh-host-keys.tar
|- strategy
|- version
|- current -> 20140728T010000
Note: the GHE_DATA_DIR
variable set in backup.config
can be used to change
the disk location where snapshots are written.
How does backup utilities differ from a High Availability replica?
It is recommended that both backup utilities and an High Availability replica are used as part of a GitHub Enterprise deployment but they serve different roles.
The purpose of the High Availability replica
The High Availability replica is a fully redundant secondary GitHub Enterprise instance, kept in sync with the primary instance via replication of all major datastores. This active/passive cluster configuration is designed to minimize service disruption in the event of hardware failure or major network outage affecting the primary instance. Because some forms of data corruption or loss may be replicated immediately from primary to replica, it is not a replacement for the backup utilities as part of your disaster recovery plan.
The purpose of the backup utilities
Backup utilities are a disaster recovery tool. This tool takes date-stamped snapshots of all major datastores. These snapshots are used to restore an instance to a prior state or set up a new instance without having another always-on GitHub Enterprise instance (like the High Availability replica).
Support
If you find a bug or would like to request a feature in backup-utils, please open an issue or pull request on this repository. If you have a question related to your specific GitHub Enterprise setup or would like assistance with backup site setup or recovery, please contact our Enterprise support team instead.


Your virtual environment must be active to use thunder.py:
source ../env-tctf/bin/activate
python3 thunder.py create thunder/a1openbucket
For each level of this ctf, you will be tasked with exploiting various vulnerable cloud infrastructure in order to find the "secret" of each level, which is a large integer stored somewhere in the infrastructure
The secret for this level is in a file in a Google Cloud Storage bucket. On level creation, you are given the bucket name, and it is written to start/a1openbucket.txt
Each level of this ctf has a set of detailed hints that can guide you through the level, but we strongly encourage you to try as hard as you can to figure out the challenges using the least number of hints possible, as this is how you will learn the most. The hints can be accessed by clicking the "next" button next to "Intro"
---List the bucket's contents
---The command to do so is:
gsutil ls gs://[bucket-name]---
Download the secret file
---The command to do so is:
gsutil cp gs://[bucket-name]/secret.txt---
Level writeup will be available soon


--- layout: archive title: Zulip Chat Archive permalink: /stream/116395-maths/topic/Future.20projects.20as.20Wiki.3F.html ---
Chris has written a roadmap for algebraic closure. I am wondering whether this could be in the mathlib wiki? @Reid Barton also described to me a small mathlib-appropriate project which he didn't have time to do but which he had turned into a coherent roadmap (in particular he felt that he had found the correct way of setting up the theory, and was concerned that if someone else tried it without having put the same amount of thought into planning then there was a risk that they would set things up in a worse way). Would the wiki pages be appropriate for roadmaps?
{% endraw %}Last updated: Apr 24 2020 at 19:02 UTC


JSON Editor multiple file upload (base64)
Upload multiple files simultaneously. Add multiple files in the upload dialog and new rows in the picture array will automatically be added. Description will not be overwritten for the current selected element.
Submit (console.log)


While working on the automated build system for the R client at Sage, I discovered how to pass parameters between Jenkins jobs. In this post, I will talk about why I was interested in this topic, and what I learned from setting up my builds.
Why passing parameters between Jenkins jobs?
The automated build system I worked on is supposed to do the following:
1. One each platform (Linux, Window & Mac):
* Clone and checkout a release candidate branch of a Github repository
* Run R CMD build
& R CMD install
to create artifacts
2. Zip the artifacts
3. Generate documentation and update the release candidate branch
4. Push artifacts to our RAN
5. Check that the artifacts can be installed on 3 platforms Linux, Window, and Mac
I have the following Jenkins jobs:
synapser_staging
* Runs on 3 slaves (Linux, Window & Mac)
* Executes task #1
synapser_artifacts
* Runs on a Mac machine
* Executes task #2 & #3
synapser_deploy
* Runs on a slave machine
* Executes #4
synapser_check
* Runs on 3 slaves (Linux, Window & Mac)
* Executes #5
synapser_staging
uses the branch name and the Jenkins job number to determine to version that it's going to build. For example, when the building branch is v0.1-rc
and the job number is 27, the version that is going to build is 0.1.27
This algorithm allows us to automatically increase the version number without making human mistakes.
This version number will be used:
* to generate the artifacts (in synapser_staging
),
* update Version
in DESCRIPTION
file, then this change is push back to the building branch (in synapser_artifacts
),
* and look for which version to check after deployment (in synapser_check
)
Ideally, I would want to pass the version number from one job to another.
How to pass parameters from one Jenkins job to another?
Preconditions
To pass parameters from synapser_staging
to synapser_artifacts
, I need the following Jenkins plugins:
* Parameterized Build
* Parameterized Build Trigger
Configurations
synapser_staging
- the giver - is set up with Parameterized Build Trigger in Post Actions section. synapser_artifacts
- the receiver - is set up with Parameterized Build in the General section.
What variables can you pass?
The types of variable that can be passed includes: * Jenkins environment variables (BUILD_ID, BUILD_NUMBER, ...) * Params that trigger the giver job (entered from users or passed from another job) * Github params (BRANCH_NAME) * Constants (I will talk more about why you need constants).
What I learned
Now, those types above do not include user defined variable. If you are familiar with bash, you would laugh at me for trying to pass variables that I exposed in the running script. The biggest lesson that I learned from this is when you expose a "global variable" in your script, it will effect the current running script and it's child processes, but not its parents. Passing params happen at the "parent" level, at the process that manages the job. So any values you calculate within the job, stays inside the job.
With that said, I cannot calculate version number with my algorithm and pass it along to a downstream job. Instead, I passed the infomation that requires to calculate the version number from the starting job to the last job.
Now, you may say, that's a lot of dupplicated code to execute the algorithm over and over again. When I need to make changes to that code, I will forget to change all the places. Here is the solution for that: use git raw file. You can write your code once, push it to Github. Then you can use curl to get that code. I do this for big chunk of code, but not small and simple code. It's not about being lazy, it's about efficiency. Reading/ downloading data over the network is always the bottle neck. If the code was one line of bash script, I would just copy and past it from one job to another job.
Notes about constants
Constants are useful when you have 2 upstream jobs calling the same downstream job with different variables. For example, my synapser_check
can be used to check any package version on any RAN. The upstream job would pass it the version number and the RAN URI. In this case, the RAN URI can be a constant defined while configure the giver job with Parameterized Build Trigger.
I hope these information are useful. If you try it, please leave a comment letting me know how it works out for you.


This page demonstrates
rollup-plugin-commonjs issue #77
.
Check your browser console for the results.


{{searchSubject?.name}}
S{{searchSubject?.semester}} Elective
Code: {{searchSubject?.cource_code}}
Credit: {{searchSubject?.credit}}
Subject Difficulty: {{searchSubject?.difficulty}}
Pass percentage
Performance of last 5 batches
Showing results of:
Batch {{ batchShow?.year}} - {{semester[0].name}}
No students found with the grade {{grade}}
Students with grade: {{grade}} show all
| id | Name | Grade |
|---|---|---|
| {{student.id}} | {{student.name}} | {{student.grade}} |
Grade Map
Cleared: {{data.length}}
Failed: {{data.length}}
Total: {{data.length}}


Kognito is a 30 minute online interactive program that teaches students to recognize signs of depression and suicide in their peers, how to approach them and converse with them about it, and how to point them to relevant campus resources. For more information, see Kognito.
Our mission is to convince 1,500 UC Berkeley students to take online Kognito training and fill out response survey by May, 2018. We will do this in order to test the efficacy of the thirty three thousand dollar program, with grant funds coming from the student Wellness Fee Committee. If the program has demonstrated that it will make an impact on mental health stigma and referral rates at the Cal campus, then we will seek to mandate the program.


-> Why should I use medCabinet?
-> How do I start using medCabinet?
-> How can medCabinet help me?
medCabinet creates an easy way for people new to the MedicalMarijuana community to better understand which strains help best with your ailment.
Simply create an account or login and you will have access to a world of information regarding MedicalMarijuana.
We specialize In helping people switching to medical cannabis find the right strains, dosing, intake method and intake schedule!


Firstday Experiences&feelings
Today
今天先是看了下node.js的一个教程，发现里面的编辑器不错，代码补全能力很强大，于是对Atom兴趣大增，搞了好半天还是没学会怎么做一个插件（过了一会，我发现教程里用的其实不是Atom）。
Angularjs的相关插件在Mac下要用“Control”+“Space”才能补全代码，感觉好麻烦，感觉理想情况下应该是自动补全，或Tab键补全，但我修改Lanuage-Javascript这个插件也没成功，就先放下了。
想起来，昨天装jekyllbootsrtap还有个问题没解决，“The submodule _theme_packages/hooligan
was not properly initialized with a .gitmodules
file.”
今天又重装了下，可还是报这个错，解决方法中的这句不会“Commit and push your changes to trigger another build on our servers.”
最后我把“_theme_packages”这个目录删除了，于是不报错了。目前也没发现有什么影响，于是用Atom写了今天这个。
### What is Tomorrow?
再看看Atom，确实不错；还有。。。much to think.
Examples
This website is created with Jekyll. Other Jekyll websites.
What does Jekyll Do?
Jekyll is a ruby gem you install on your local system.
Once there you can call jekyll --server
on a directory and provided that directory
is setup in a way jekyll expects, it will do magic stuff like parse markdown/textile files,
compute categories, tags, permalinks, and construct your pages from layout templates and partials.
Once parsed, Jekyll stores the result in a self-contained static _site
folder.
The intention here is that you can serve all contents in this folder statically from a plain static web-server.
You can think of Jekyll as a normalish dynamic blog but rather than parsing content, templates, and tags on each request, Jekyll does this once beforehand and caches the entire website in a folder for serving statically.
Content in Jekyll
Content in Jekyll is either a post or a page. These content “objects” get inserted into one or more templates to build the final output for its respective static-page.
Posts and Pages
Both posts and pages should be written in markdown, textile, or HTML and may also contain Liquid templating syntax. Both posts and pages can have meta-data assigned on a per-page basis such as title, url path, as well as arbitrary custom meta-data.
blog comments powered by Disqus


Package com.qoretechnologies.qorus
Class QorusSystemRestHelper
- java.lang.Object
-
- org.qore.jni.QoreObjectWrapper
-
- org.qore.lang.HTTPClient
-
- com.qoretechnologies.qorus.QorusSystemRestHelper
-
public class QorusSystemRestHelper extends org.qore.lang.HTTPClient
Java wrapper for the OMQ::QorusSystemRestHelper class in Qore
-
-
Constructor Summary
Constructors Constructor Description QorusSystemRestHelper()
Creates the object pointing to the first local listener for the current instanceQorusSystemRestHelper(java.lang.String name)
Creates the object with the configuration given by the name of the remoteconn "remote instance"QorusSystemRestHelper(java.lang.String username, java.lang.String password)
Creates the object pointing to the first local listener for the current instance using the given user and password for connectingQorusSystemRestHelper(java.util.HashMap<java.lang.String,java.lang.Object> info)
Creates the object with the configuration givenQorusSystemRestHelper(org.qore.jni.QoreObject obj)
Creates the object as a wrapper for the Qore object
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description java.lang.Object
delRest(java.lang.String path)
Executes a "DELETE" call on the remote REST service and returns the responsejava.lang.Object
delRest(java.lang.String path, java.lang.Object args)
Executes a "DELETE" call on the remote REST service and returns the responsejava.lang.Object
delRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "DELETE" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
delRestWithInfo(java.lang.String path)
Executes a "DELETE" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
delRestWithInfo(java.lang.String path, java.lang.Object args)
Executes a "DELETE" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
delRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "DELETE" call on the remote REST service and returns the responsejava.lang.Object
getRest(java.lang.String path)
Executes a "GET" call on the remote REST service and returns the responsejava.lang.Object
getRest(java.lang.String path, java.lang.Object args)
Executes a "GET" call on the remote REST service and returns the responsejava.lang.Object
getRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "GET" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
getRestWithInfo(java.lang.String path)
Executes a "GET" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
getRestWithInfo(java.lang.String path, java.lang.Object args)
Executes a "GET" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
getRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "GET" call on the remote REST service and returns the responsejava.lang.Object
postRest(java.lang.String path)
Executes a "POST" call on the remote REST service and returns the responsejava.lang.Object
postRest(java.lang.String path, java.lang.Object args)
Executes a "POST" call on the remote REST service and returns the responsejava.lang.Object
postRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "POST" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
postRestWithInfo(java.lang.String path)
Executes a "POST" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
postRestWithInfo(java.lang.String path, java.lang.Object args)
Executes a "POST" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
postRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "POST" call on the remote REST service and returns the responsejava.lang.Object
putRest(java.lang.String path)
Executes a "PUT" call on the remote REST service and returns the responsejava.lang.Object
putRest(java.lang.String path, java.lang.Object args)
Executes a "PUT" call on the remote REST service and returns the responsejava.lang.Object
putRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "PUT" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
putRestithInfo(java.lang.String path)
Executes a "PUT" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
putRestWithInfo(java.lang.String path, java.lang.Object args)
Executes a "PUT" call on the remote REST service and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
putRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes a "PUT" call on the remote REST service and returns the responsejava.lang.Object
restDo(java.lang.String m, java.lang.String path)
Executes the remote REST call and returns the responsejava.lang.Object
restDo(java.lang.String m, java.lang.String path, java.lang.Object args)
Executes the remote REST call and returns the responsejava.lang.Object
restDo(java.lang.String m, java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes the remote REST call and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
restDoWithInfo(java.lang.String m, java.lang.String path)
Executes the remote REST call and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
restDoWithInfo(java.lang.String m, java.lang.String path, java.lang.Object args)
Executes the remote REST call and returns the responsejava.util.HashMap<java.lang.String,java.lang.Object>
restDoWithInfo(java.lang.String m, java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr)
Executes the remote REST call and returns the response-
Methods inherited from class org.qore.lang.HTTPClient
clearProxyURL, clearProxyUserPassword, clearStats, clearUserPassword, connect, disconnect, get, get, getConnectionPath, getConnectTimeout, getDefaultPath, getEncoding, getEncodingPassthru, getErrorPassthru, getHostHeaderValue, getHTTPVersion, getMaxRedirects, getNoDelay, getProxyURL, getRedirectPassthru, getTimeout, getURL, getUsageInfo, head, head, isConnected, isProxySecure, isSecure, post, post, post, post, post, send, send, send, send, send, send, send, send, setConnectionPath, setConnectionPath, setConnectTimeout, setDefaultPath, setEncoding, setEncodingPassthru, setEncodingPassthru, setErrorPassthru, setErrorPassthru, setHTTPVersion, setMaxRedirects, setNoDelay, setPersistent, setProxySecure, setProxyURL, setProxyURL, setProxyUserPassword, setProxyUserPassword, setRedirectPassthru, setRedirectPassthru, setSecure, setTimeout, setURL, setUserPassword, setUserPassword
-
-
-
-
Constructor Detail
-
QorusSystemRestHelper
public QorusSystemRestHelper(org.qore.jni.QoreObject obj)
Creates the object as a wrapper for the Qore object
-
QorusSystemRestHelper
public QorusSystemRestHelper() throws java.lang.Throwable
Creates the object pointing to the first local listener for the current instance- Throws:
java.lang.Throwable
- Since:
- Qorus 3.0.2
-
QorusSystemRestHelper
public QorusSystemRestHelper(java.lang.String name) throws java.lang.Throwable
Creates the object with the configuration given by the name of the remoteconn "remote instance"- Throws:
java.lang.Throwable
-
QorusSystemRestHelper
public QorusSystemRestHelper(java.lang.String username, java.lang.String password) throws java.lang.Throwable
Creates the object pointing to the first local listener for the current instance using the given user and password for connecting- Parameters:
username
- the username for the connectionpassword
- the password for the connection- Throws:
java.lang.Throwable
- Since:
- Qorus 3.0.2
-
QorusSystemRestHelper
public QorusSystemRestHelper(java.util.HashMap<java.lang.String,java.lang.Object> info) throws java.lang.Throwable
Creates the object with the configuration given- Throws:
java.lang.Throwable
-
-
Method Detail
-
getRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> getRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "GET" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "GET /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
getRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> getRestWithInfo(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "GET" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "GET /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
getRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> getRestWithInfo(java.lang.String path) throws java.lang.Throwable
Executes a "GET" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "GET /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
getRest
public java.lang.Object getRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "GET" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
getRest
public java.lang.Object getRest(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "GET" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
getRest
public java.lang.Object getRest(java.lang.String path) throws java.lang.Throwable
Executes a "GET" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
putRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> putRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "PUT" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "PUT /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
putRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> putRestWithInfo(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "PUT" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "PUT /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
putRestithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> putRestithInfo(java.lang.String path) throws java.lang.Throwable
Executes a "PUT" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "PUT /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
putRest
public java.lang.Object putRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "PUT" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
putRest
public java.lang.Object putRest(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "PUT" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
putRest
public java.lang.Object putRest(java.lang.String path) throws java.lang.Throwable
Executes a "PUT" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
postRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> postRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "POST" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "POST /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
postRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> postRestWithInfo(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "POST" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "POST /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
postRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> postRestWithInfo(java.lang.String path) throws java.lang.Throwable
Executes a "POST" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "POST /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
postRest
public java.lang.Object postRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "POST" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
postRest
public java.lang.Object postRest(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "POST" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
postRest
public java.lang.Object postRest(java.lang.String path) throws java.lang.Throwable
Executes a "POST" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
delRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> delRestWithInfo(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "DELETE" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "DELETE /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
delRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> delRestWithInfo(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "DELETE" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "DELETE /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
delRestWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> delRestWithInfo(java.lang.String path) throws java.lang.Throwable
Executes a "DELETE" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "DELETE /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
delRest
public java.lang.Object delRest(java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes a "DELETE" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
delRest
public java.lang.Object delRest(java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes a "DELETE" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
delRest
public java.lang.Object delRest(java.lang.String path) throws java.lang.Throwable
Executes a "DELETE" call on the remote REST service and returns the response- Parameters:
path
- the URI path for the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
restDoWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> restDoWithInfo(java.lang.String m, java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes the remote REST call and returns the response- Parameters:
m
- the HTTP method for the request (ex: "GET")path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "DELETE /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
restDoWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> restDoWithInfo(java.lang.String m, java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes the remote REST call and returns the response- Parameters:
m
- the HTTP method for the request (ex: "GET")path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "DELETE /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
restDoWithInfo
public java.util.HashMap<java.lang.String,java.lang.Object> restDoWithInfo(java.lang.String m, java.lang.String path) throws java.lang.Throwable
Executes the remote REST call and returns the response- Parameters:
m
- the HTTP method for the request (ex: "GET")path
- the URI path for the request- Returns:
- a hash with the following keys:
- rv: the deserialized response body
- info: a hash of request headers and other information about the HTTP request; if present the hash will contain the following keys:
- headers: a hash of outgoing HTTP request headers
- request-uri: the request URI string sent (ex: "DELETE /services/async/38.0/job HTTP/1.1")
- body-content-type: the outgoing message body Mime "Content-Type" value
- response-headers: a hash of incoming HTTP headers in the response
- chunked: set to Qore::True "True" if the response was received with chunked transfer encoding
- response-code: the HTTP response code
- response-body: the raw message body in the response (after any content decoding)
- response-serialization: the type of message serialization in the response; see RestClient::RestClient::DataSerializationOptions for possible values
- request-body: the raw message body in the request (before any content encoding)
- request-serialization: the type of message serialization in the request; see RestClient::RestClient::DataSerializationOptions for possible values
- Throws:
java.lang.Throwable
-
restDo
public java.lang.Object restDo(java.lang.String m, java.lang.String path, java.lang.Object args, java.util.HashMap<java.lang.String,java.lang.Object> hdr) throws java.lang.Throwable
Executes the remote REST call and returns the response- Parameters:
m
- the HTTP method for the request (ex: "GET")path
- the URI path for the requestargs
- any arguments to the REST requesthdr
- a hash of optional HTTP header info to add to the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
restDo
public java.lang.Object restDo(java.lang.String m, java.lang.String path, java.lang.Object args) throws java.lang.Throwable
Executes the remote REST call and returns the response- Parameters:
m
- the HTTP method for the request (ex: "GET")path
- the URI path for the requestargs
- any arguments to the REST request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
restDo
public java.lang.Object restDo(java.lang.String m, java.lang.String path) throws java.lang.Throwable
Executes the remote REST call and returns the response- Parameters:
m
- the HTTP method for the request (ex: "GET")path
- the URI path for the request- Returns:
- the deserialized response body
- Throws:
java.lang.Throwable
-
-


HTML Forms
First name:
Last name:
Gender:
Please Select
Laki-Laki
Perempuan
Company name:
Contact Phone:
Email Address:
Language:
Please Select
Indonesia
English
Company Site:


You can add query string parameters to the URL to filter the syllabi that are displayed in the list below. The options are:
semester
e.g. "Spring 2017"order
which is one of "modified", "relevance", or "name"q
for a free text querySo, for instance, appending ?semester=Spring+2017&q=history+of+art to this URL will retrieve Spring 2017 syllabi matching the search "history of art".


Maps internal statuses to FontAwesome icons. Examples of their usage are available on the rxStatusColumn demo page.


If you're looking for free coding exercises to prepare for your next job interview, we've got you covered.
An array is a programming structure that is a collection of several data values of the same type. In terms of memory, an array is a group of contiguous memory locations storing data of the same type.
Any artificial language usable for expressing information or knowledge or systems in an arrangement determined by a reliable set of rules is called a modeling language.
The same set of rules is also used for interpreting the meaning of the components of a modeling language structure. Following are some examples of modeling languages:
During the testing of a computer program, a number of issues are discovered. These are called errors and bugs. Debugging is the process of correcting them. In other words, debugging is the process of correcting the failures discovered in the implemented code.
DRY stands for Don’t Repeat Yourself. It is a software development principle that aims at reducing the repetition of software patterns. For achieving this, either the repetitive software patterns need to be replaced with abstractions or data normalization must be used.
A data structure is a particular way of organizing and manipulating
data. It allows efficient access as well as modification of data.
A data structure can also be defined as a collection of data, the
functions applicable to them, and the relationships among them.
Arrays, linked lists, heaps, graphs, and stacks are some examples of
data structures.
You’ll already know the basics from your research ahead of submitting your application, but now is the time to delve a bit deeper. What are their current projects? Have they been in the news? Who are their clients? Who will be interviewing you? Check out the organisation’s website, newspapers, or social media for this information. Showing you know what the organisation is up to will look good to your interviewers. If you have been told or can find out who will be interviewing you a bit of research about them (a quick look over their LinkedIn page will do) could potentially help reduce your nerves.
Looking at the job description and the skills required for the role should give you a steer on what kind of questions could be asked about your abilities and experience. List the possible questions and make a note of what your answers would be, but don’t worry about fitting in to an exact box. The interview is a chance to show your knowledge and skills but also your personality, so personal projects you’ve developed, or examples from hobbies or interests that are relevant might be of interest to the interviewer. It’s all of these things combined that will help to demonstrate why you are a good match for the job.
You’ll already know the basics from your research ahead of submitting your application, but now is the time to delve a bit deeper. What are their current projects? Have they been in the news? Who are their clients? Who will be interviewing you? Check out the organisation’s website, newspapers, or social media for this information. Showing you know what the organisation is up to will look good to your interviewers. If you have been told or can find out who will be interviewing you a bit of research about them (a quick look over their LinkedIn page will do) could potentially help reduce your nerves.
If you need special access or additional materials to be arranged for your interview, make sure you get in touch with the organisation and let them know.
Make sure you know where you are going and how long it takes to get there. If you can, go online and work out the easiest way to get there, then be sure to add on extra time so you’re totally covered. The last thing you want is to arrive flustered or late.
The last thing you need is a frantic panic on the morning of the interview as you hunt for a suitable outfit. Planning what to wear a few days beforehand will let you focus on the important things. Check out this module for tips on what to wear for your interview.
During your research there will most likely have been things cropping up that you’d like to know more about. Write them out as clear questions for the interviewer. This will help you avoid an awkward silence when you’re asked if you have any questions. Check out our Top 5 questions to ask in your interview for more tips.
Imagining what it feels like to be in the interview can help make it feel less daunting. Rehearsing questions and answers with friends, family or a mentor will be a huge help on the day.
Re-familiarise yourself with the questions and answers you’ve prepared but don’t stress about trying to remember every single detail. A decent grasp of the main points will stop you ‘script-reading’ your answers, but if it helps, create a list of key skills, qualities and experience from your CV that you want to cover.
You’ll undermine your preparations if you’re stifling yawns in the interview. Feeling refreshed and alert will also help you cope with any unforeseen situations that might get the nerves buzzing; like questions you maybe hadn’t thought of.


Property Types are for adding addiotional information to the product your selling that is not definted by Option Types. For exmaple, you can add the dimensions, color or materal of the product for better organization and search filters.
You can set up Property Types for your store so all your products can have access to them, then adjust their values in the Edit page for a specific product or variant.
Add Property Types to the Store by clicking the link in the Products Menu and create them in a master list.