Floating point color represents each pixel as four floating point values, while truecolor packs the color information into a 32bit integer. See FloatingPointPixel and TrueColorPixel for more information.
Please note that this class is just a simple wrapper around an enumeration. This is done so that you can refer to modes as Mode::TrueColor and Mode::FloatingPoint in your code.
You can assign and compare instances of this class as if they were the enumeration itself.
Here is some example code to demonstrate:
Mode mode = Mode::FloatingPoint; if ( mode != Mode::TrueColor ) { mode = Mode::TrueColor; } switch ( mode ) { case Mode::FloatingPoint: print( "floating point mode" ); break; case Mode::TrueColor: print( "truecolor mode" ); break; } Mode a = Mode::FloatingPoint; Mode b = Mode::TrueColor; assert( a != b ); assert( ! (a == b) ); Display display( "mode example", 320, 240, Output::Windowed, mode ); if ( display.open() ) { assert( mode == display.mode() ); }
Public Types | |
| enum | Enumeration { TrueColor, FloatingPoint } |
| The internal enumeration wrapped by the Mode class. More... | |
Public Member Functions | |
| Mode () | |
| The mode default constuctor sets the enumeration value to FloatingPoint. | |
| Mode (Enumeration enumeration) | |
| This constructor enables automatic conversion from the enumeration type to a mode object. | |
| operator Enumeration () const | |
| Cast from mode object to enumeration. |
| enum Enumeration |
The internal enumeration wrapped by the Mode class.
You should never need to use the enumeration type directly, only the Mode::TrueColor and Mode::FloatingPoint values.
| TrueColor | pixels are represented as packed 32 bit integers. See TrueColorPixel for details. |
| FloatingPoint | pixels are represented by four floating point values for. See FloatingPointPixel for details. |
| Mode | ( | ) | [inline] |
The mode default constuctor sets the enumeration value to FloatingPoint.
Floating point color to considered to be the default throughout the Pixel Toaster API.
| Mode | ( | Enumeration | enumeration | ) | [inline] |
This constructor enables automatic conversion from the enumeration type to a mode object.
For example: Mode mode = Mode::FloatingPoint;
| enumeration | the enumeration value. |
| operator Enumeration | ( | ) | const [inline] |
Cast from mode object to enumeration.
Allows you to treat this class as if it was the enumeration itself. This enables the ==, != operators, and the use of mode objects in a switch statement.


*Starship Troopers* 1997 TriStar, Rated R. Directed by Paul Verhoeven, starring Casper Van Dien, Dina Meyer, Denise Richards, Neil Patrick Harris, Clancy Brown, Michael Ironside. Written by Edward Neumeier, based on the novel by Robert A. Heinlein.
Review by Thor Thomas
The movie _Starship Troopers_ is full of sound and fury and blood and testosterone. A tongue-in-cheek deconstruction of Robert A. Heinlein's novel and war movies as fascist propaganda. So, what's in it? Macho women with guns! Macho men with guns! Phallic spaceships! Guns that shoot 23-skidillion bullets before reloading! Nuclear grenades! Decapitations! Mutilations! Defenestrations! Whipping! And bugs! Bugs!! Bugs!!! It's been a while since I have read the book, but as I recall, it was not much more than a series of battle vignettes framed by flashbacks to the main character's high-school civics class. Inspired in part by Heinlein's experiences during WWII, it is a platform for Heinlein to preach and philosophize about how the military is necessary for the survival of civilians, though as it is an allegory, it does perhaps get taken a bit far. The military rules society, and anyone who is not a member does not have citizen's rights.  The Bugs are an enemy with whom we cannot have peace (because we have nothing in common but a need for the same planets), only victory or defeat. Hence, a war that goes on pretty much forever as the two sides are fairly evenly matched. In this sort of scenario, the society Heinlein presents is perhaps justified, but it is a nasty world I could not like very much while reading the book, and the filmmakers evidently had similar feelings. Personally, I never felt the book was one of Heinlein's stronger works; for a better coming- of-age story in a military setting, I would recommend his _Space Cadets_ much more highly. In the book version of _Starship Troopers_, the Mobile Infantry does its fighting in power battlesuits that inspired the whole "Japanime" mech genre.  Perhaps someone figured they wouldn't need actors anymore if they did the CGI powersuits. The crypto-fascist society of Starship Troopers takes a back seat to the action, but between acts we do get treated to spoofs of interactive government propaganda. In the book, the Bug War had been going on for some time, which explained the militaristic society, but in the movie the war starts during the story, and the junta is already well-established, which is slightly more disturbing. Many of the uniforms and insignia have a definite "Nazi" look about them. I'm not sure Heinlein would have approved of the interpretation, but it's definitely an element of his story, whether he meant it precisely that way or not. Another difference: in the movie, the military is fully integrated, while in the book the infantry was all-male and only women flew the ships. The philosophy is still there, though in smaller proportions than the novel (which is a good thing, we wouldn't want to fall asleep in the theater, would we?), and the brutality is not as sugar-coated. Director Paul Verhoeven seems to be exposing some of the Heinlein's nastier subtext. Verhoeven is also a director who loves to depict death and blood, and this is not a movie for the squeamish. Nothing perhaps as blatant and gratuitous as the transit-station shoot- out in his movie _Total Recall_, but in addition to battlefield casualties shown in full view, we also have violence off the battlefield, including a broken arm, a knife through a hand, someone cut in half by a pressure door, and a death during a training exercise. Ironically, the only violence censored is one scene of a cow being slaughtered and one of cruelty to an alien. Despite the satiric element, the movie comes across as fairly mindless once all is said and done, mainly due to the testosterone-poisoned cornball plot and stock characters lifted from old WWII movies. But it is fun in the mode of _Independence Day_ - cheer the humans squashing those nasty alien bugs. And such pretty bugs, too: the computer graphics really turned out well! See it for the special effects and the bugs, or for the part of the novel that is still there, rather than the intellectual content or a retelling of the book, and be warned of the gore. DISCLAIMER: It has been a while since I read _Starship Troopers_ (I considered re-reading it before seeing the movie, but decided not to), so any misrepresentations of Heinlein's text are my fault entirely.
Review copyright 1997 by Thor Thomas, permission to distribute freely in complete form with copyright notice.
<EMAIL_ADDRESS>http://pobox.com/~thor -- /// Thor Thomas AKA Kerr Avon |<EMAIL_ADDRESS><EMAIL_ADDRESS>/// "http://pobox.com/~thor" |<EMAIL_ADDRESS><EMAIL_ADDRESS>\\\/// \/// BOYCOTT MICROSOFT! <*>
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


[all packages]
[package ]
[class hierarchy]
[index]
java.lang.Object | +----Printer | +----StdOut
public class StdOut extends Printer
Printer
class which sends the
text to the standard output (useful for debugging).public StdOut();
printRawString
public void printRawString(String s);
[all packages]
[package ]
[class hierarchy]
[index]


HOME
ABOUT ME
PORTFOLIO
CONTACT ME
CONTACT-ME
SEND MESSAGE
<EMAIL_ADDRESS>tel.+254746225871
Facebook
Twitter
Designed By Easy BenKaka .com


First Tour: November 20, 2018 | End Date: November 27, 2018
Second Tour: December 1, 2018 | End Date: December 7, 2018
Third Tour: December 20, 2018 | End Date: December 27, 2018
First Session: September 1, 2018 - September 12, 2018
Second Session: October 12, 2018 - October 24, 2018
Third Session: November 1, 2018 - November 12, 2018


FROM THE DESK OF : BJSRI BUDAK, AUDITING AND ACCOUNTING SECTION, BANK OF AFRICAN ( B.O.A ) OUAGADOUGOU BURKINA-FASO,WEST AFRICA. Attention Please, This message might meet you in utmost surprise, however,it's just my urgent need for foreign partner that made me to contact you for this transaction. I am a banker by profession from Burkina faso in west Africa and currently holding the post of Director Auditing and Accounting unit of the bank.I have the opportunity of transfering the left over funds ($15.6million) of one of my bank clients who died along with his entire family on 31 july 2000 in a plane crash.You can confirm the genuiness of the deceased death by clicking on this web site http://news.bbc.co.uk/1/hi/world/europe/859479.stm Hence,i am inviting you for a business deal where this money can be shared between us in the ratio of 60/30 while 10% will be mapped out for expenses.If you agree to my business proposal.further details of the transfer will be forwarded to you as soon as i receive your return mail,have a great day. Make sure you keep this transaction as your top secret and make it confidential till we receives the fund into the account that you will provide to the bank. don¢t disclose it to any body, because the secrecy of this transaction is as well as the success of it. Yours faithfully, Mr Bjsri Budak. Please reply me here:Email<EMAIL_ADDRESS>_________________________________________________________________ MSN Hotmail : créez votre adresse e-mail gratuite & à vie ! http://www.msn.fr/newhotmail/Default.asp?Ath=f


FAQ¶
Q: How does conflict resolution actually work?
A: The game uses reverse topological sorting on a move requests graph at each turn to determine the order in which the units’ move requests are executed. The move requests graph is a directed graph in which vertices represent each point on the board and edges represent move requests by players. A reverse topological sort of the move requests graph orders the vertices such that the ordering respects every directed edge (“move request from point x to point y”) in the graph. Move requests are executed in order of the reverse topological sort.
Q: If one of my units attacks an enemy unit, will it also always lose health points?
A: If the enemy unit also attacks your unit in the same turn, your unit will lose health. But if only you attack, your health point remains the same.
Q: Can a tile return to being neutral after it’s been visited by a firefly unit?
A: No. A tile is neutral only from the start of the game to the time at which it’s first visited by any team. Its colour can change between teams, but it’ll never return back to neutral.
Q: Can you build a nest on a non-neutral tile?
A: No. Only neutral tiles can become nests
Q: My AI exceeds time-out once or twice, but not often. Will it be disqualified?
A: Don’t worry - the game will continue to run even if your AI exceeds time-out. However, any moves you make will be skipped, and all your units will rest for that turn.
Q: When does a unit gain health points
A: A unit gains health points any time it rests, either by choice or forcibly. That is, even if a unit was instructed to move to a neighbouring tile, if the server rejects that move (e.g. because of a wall or a nest), it’ll gain a health point.
Q: If several units merge, and one of the units are at rest, will the merged unit earn a health point? A: Yes. If at least one of the merging units are at rest, then the newly merged unit will earn 1 health point.


| pgpool-II 4.0.3 Documentation | |||
|---|---|---|---|
| Prev | Up | Appendix A. Release Notes | Next |
Release Date: 2016-11-21
Major enhancements in Pgpool-II 3.6 include:
Improve the behavior of failover. In the steaming replication mode, client sessions will not be disconnected when a failover occurs any more if the session does not use the failed standby server. If the primary server goes down, still all sessions will be disconnected. Also it is possible to connect to Pgpool-II even if it is doing health checking retries. Before all attempt of connecting to Pgpool-II failed while doing health checking retries.
New PGPOOL SET command has been introduced. Certain configuration parameters now can be changed on the fly in a session.
Watchdog is significantly enhanced. It becomes more reliable than previous releases.
Handling of extended query protocol (e.g. used by Java applications) in streaming replication mode speeds up if many rows are returned in a result set.
Import parser of PostgreSQL 9.6.
In some cases pg_terminate_backend() now does not trigger a failover.
Change documentation format from raw HTML to SGML.
The above items are explained in more detail in the sections below.
Improve the behavior of failover. (Tatsuo Ishii)
In the steaming replication mode, client sessions will not be disconnected when a failover occurs any more if the session does not use the failed standby server. If the primary server goes down, still all sessions will be disconnected. Health check timeout case will also cause the full session disconnection. Other health check error, including retry over case does not trigger full session disconnection.
For user's convenience, "show pool_nodes" command shows the session local load balance node info since this is important for users in case of failover. If the load balance node is not the failed node, the session will not be affected by failover.
Also now it is possible to connect to Pgpool-II even if it is doing health checking retries. Before all attempt of connecting to Pgpool-II failed while doing health checking retries. Before any attempt to connect to Pgpool-II fails if it is doing a health check against failed node even if failover_on_backend_error is off because Pgpool-II child first tries to connect to all backend including the failed one and exits if it fails to connect to a backend (of course it fails). This is a temporary situation and will be resolved once pgpool executes failover. However if the health check is retrying, the temporary situation keeps longer depending on the setting of health_check_max_retries and health_check_retry_delay. This is not good. Attached patch tries to mitigate the problem:
When an attempt to connect to backend fails, give up connecting to the failed node and skip to other node, rather than exiting the process if operating in streaming replication mode and the node is not primary node.
Mark the local status of the failed node to "down". This will let the primary node be selected as a load balance node and every queries will be sent to the primary node. If there's other healthy standby nodes, one of them will be chosen as the load balance node.
After the session is over, the child process will suicide to not retain the local status.
Add PGPOOL SHOW, PGPOOL SET and PGPOOL RESET commands. (Muhammad Usama)
These are similar to the PostgreSQL's SET and SHOW commands for GUC variables, adding the functionality in Pgpool-II to set and reset the value of config parameters for the current session, and for that it adds a new syntax in Pgpool-II which is similar to PostgreSQL's SET and RESET variable syntax with an addition of PGPOOL keyword at the start.
Currently supported configuration parameters by PGPOOL SHOW/SET/RESET are: log_statement, log_per_node_statement, check_temp_table, check_unlogged_table, allow_sql_comments, client_idle_limit, log_error_verbosity, client_min_messages, log_min_messages, client_idle_limit_in_recovery.
Sync inconsitent status of PostgreSQL nodes in Pgpool-II instances after restart. (bug 218) (Muhammad Usama)
Watchdog does not synchronize status.
Enhance performance of SELECT when lots of rows involved. (Tatsuo Ishii)
Pgpool-II flushes data to network (calling write(2)) every time it sends a row data ("Data Row" message) to frontend. For example, if 10,000 rows needed to be transfer, 10,000 times write()s are issued. This is pretty expensive. Since after repeating to send row data, "Command Complete" message is sent, it's enough to issue a write() with the command complete message. Also there are unnecessary flushing are in handling the command complete message.
Quick testing showed that from 47% to 62% performance enhancements were achieved in some cases.
Unfortunately, performance in workloads where transferring few rows, will not be enhanced since such rows are needed to flush to network anyway.
Import PostgreSQL 9.6's SQL parser. (Bo Peng)
This allows Pgpool-II to fully understand the newly added SQL syntax such as COPY INSERT RETURNING.
In some cases pg_terminate_backend()
now does not trigger a failover. (Muhammad Usama)
Because PostgreSQL returns exactly the same error code as postmaster
down case and pg_terminate_backend()
case, using
pg_terminate_backend()
raises a failover which user might not want. To
fix this, now Pgpool-II finds a pid of backend which is the target of
pg_terminate_backend()
and does not trigger failover if so.
This functions is limited to the case of simple protocol and the pid
is given to pg_terminate_backend()
as a constant. So if you call
pg_terminate_backend()
via extended protocol (e.g. Java) still
pg_terminate_backend()
triggers a failover.
HTML documents are now generated from SGML documents. (Muhammad Usama, Tatsuo Ishii, Bo Peng)
It is intended to have better construction, contents and maintainability. Also man pages are now generated from SGML. However, still there's tremendous room to enhance the SGML documents. Please help us!
Make authentication error message more user friendly. (Tatsuo Ishii)
When attempt to connect to backend (including health checking), emit error messages from backend something like "sorry, too many clients already" instead of "invalid authentication message response type, Expecting 'R' and received '%c'"
Tighten up health check timer expired condition in pool_check_fd(). (Muhammad Usama)
Add new script called "watchdog_setup". (Tatstuo Ishii)
watchdog_setup is a command to create a temporary installation of Pgpool-II clusters with watchdog for mainly testings.
Add "-pg" option to pgpool_setup. (Tatsuo Ishii)
This is useful when you want to assign specific port numbers to PostgreSQL while using pgpool_setup. Also now pgpool_setup is installed in the standard bin directory which is same as pgpool.
Add "replication delay" column to "show pool_nodes". (Tatsuo Ishii)
This column shows the replication delay value in bytes if operated in streaming replication mode.
Do not update status file if all backend nodes are in down status. (Chris Pacejo, Tatsuo Ishii)
This commit tries to remove the data inconsitency in replication mode found in [pgpool-general: 3918] by not recording the status file when all backend nodes are in down status. This surprisingly simple but smart solution was provided by Chris Pacejo.
Allow to use multiple SSL cipher protocols. (Muhammad Usama)
By replacing TLSv1_method() with SSLv23_method() while initializing the SSL session, we can use more protocols than TLSv1 protocol.
Allow to use arbitrary number of items in the black_function_list/white_function_list. (Muhammad Usama)
Previously there were fixed limits for those.
Properly process empty queries (all comments). (Tatsuo Ishii)
Pgpool-II now recognizes an empty query consisted of all comments (for example "/* DBD::Pg ping test v3.5.3 */") (note that no ';') as an empty query.
Before such that query was recognized an error.
Add some warning messages for wd_authkey hash calculation failure. (Yugo Nagata)
Sometimes wd_authkey calculation fails for some reason other than authkey mismatch. The additional messages make these distinguishable for each other.
Fix the broken log_destination = syslog functionality. (Muhammad Usama)
Fixing the logging to the syslog destination, which got broken by the PGPOOL SET/SHOW command commit, and also enhancing the log_destination configuration parameter to be assigned with the comma separated list of multiple destinations for the Pgpool-II log. Now, after this commit log_destination can be set to any combination of 'syslog' and 'stderr' log destinations.
Change the default value of search_primary_node_timeout from 10 to 300. (Tatstuo Ishii)
Prior default value 10 seconds is sometimes too short for a standby to be promoted.
Change the Makefile under directory src/sql/, that is proposed by [pgpool-hackers: 1611]. (Bo Peng)
Change the PID length of pcp_proc_count command output to 6 characters long. (Bo Peng)
If the Pgpool-II process ID are over 5 characters, the 6th character of each process ID will be removed. This commit changes the process ID length of pcp_proc_count command output to 6 characters long.
Redirect all user queries to primary server. (Tatsuo Ishii)
Up to now some user queries are sent to other than the primary server even if load_balance_mode = off. This commit changes the behavior: if load_balance_mode = off in streaming replication mode, now all the user queries are sent to the primary server only.
Fixing a potential crash in pool_stream functions. (Muhammad Usama)
POOL_CONNECTION->con_info should be checked for null value before de-referencing when read or write fails on backend socket.
Fixing the design of failover command propagation on watchdog cluster. (Muhammad Usama)
Overhauling the design of how failover, failback and promote node commands are propagated to the watchdog nodes. Previously the watchdog on pgpool-II node that needs to perform the node command (failover, failback or promote node) used to broadcast the failover command to all attached pgpool-II nodes. And this sometimes makes the synchronization issues, especially when the watchdog cluster contains a large number of nodes and consequently the failover command sometimes gets executed by more than one Pgpool-II.
Now with this commit all the node commands are forwarded to the master/coordinator watchdog, which in turn propagates to all standby nodes. Apart from above the commit also changes the failover command interlocking mechanism and now only the master/coordinator node can become the lock holder so the failover commands will only get executed on the master/coordinator node.
Fix the case when all backends are down then 1 node attached. (Tatsuo Ishii)
When all backends are down, no connection is accepted. Then 1 PostgreSQL becomes up, and attach the node using pcp_attach_node. It successfully finishes. However, when a new connection arrives, still the connection is refused becausePgpool-II child process looks into the cached status, in which the recovered node is still in down status if mode is streaming replication mode (native replication and other modes are fine). Solution is, if all nodes are down, force to restart all pgpool child.
Fix for avoiding downtime when Pgpool-II changes require a restart. (Muhammad Usama)
To fix this, the verification mechanism of configuration parameter values is reversed, previously the standby nodes used to verify their parameter values against the respective values on the master Pgpool-II node and when the inconsistency was found the FATAL error was thrown, now with this commit the verification responsibility is delegated to the master Pgpool-II node. Now the master node will verify the configuration parameter values of each joining standby node against its local values and will produce a WARNING message instead of an error in case of a difference. This way the nodes having the different configurations will also be allowed to join the watchdog cluster and the user has to manually look out for the configuration inconsistency warnings in the master Pgpool-II log to avoid the surprises at the time of Pgpool-II master switch over.
Fix a problem with the watchdog failover_command locking mechanism. (Muhammad Usama)
Add compiler flag "-fno-strict-aliasing" in configure.ac to fix compiler error. (Tatsuo Ishii)
Do not use random()
while generating MD5 salt. (Tatsuo Ishii)
random()
should not be used in security related applications. To
replace random()
, import PostmasterRandom()
from PostgreSQL. Also
store current time at the start up of Pgpool-II main process for later
use.
Don't ignore sync message from frontend when query cache is enabled. (Tatsuo Ishii)
Fix bug that Pgpool-II fails to start if listen_addresses is empty string. (bug 237) (Muhammad Usama)
The socket descriptor array (fds[]) was not getting the array end marker when TCP listen addresses are not used.
Create regression log directory if it does not exist yet. (Tatsuo Ishii)
Fixing the error messages when the socket operation fails. (Muhammad Usama)
Update regression test 003.failover to reflect the changes made to show pool_nodes. (Tatsuo Ishii)
Fix hang when portal suspend received. (bug 230) (Tatsuo Ishii)
Fix pgpool doesn't de-escalate IP in case network restored. (bug 228) (Muhammad Usama)
set_state function is made to de-escalate, when it is changing the local node's state from the coordinator state to some other state.
SIGUSR1 signal handler should be installed before watchdog initialization. (Muhammad Usama)
Since there can be a case where a failover request from other watchdog nodes arrive at the same time when the watchdog has just been initialized, and if we wait any longer to install a SIGUSR1 signal handler, it can result in a potential crash
Fix Pgpool-II doesn't escalate ip in case of another node inavailability. (bug 215) (Muhammad Usama)
The heartbeat receiver fails to identify the heartbeat sender watchdog node when the heartbeat destination is specified in terms of an IP address while wd_hostname is configured as a hostname string or vice versa.
Fixing a coding mistake in watchdog code. (Muhammad Usama)
wd_issue_failover_lock_command()
function is supposed to forward command type
passed in as an argument to the wd_send_failover_sync_command()
function instead
it was passing the NODE_FAILBACK_CMD command type.
The commit also contains some log message enhancements.
Display human readable output for backend node status. (Muhammad Usama)
Changed the output of pcp_node_info utility and show commands display human readable backend status string instead of internal status code.
Replace "MAJOR" macro to prevent occasional failure. (Tatsuo Ishii)
The macro calls pool_virtual_master_db_node_id()
and then access
backend->slots[id]->con using the node id returned. In rare cases, it
could point to 0 (in case when the DB node is not connected), which
gives access to con->major, then it causes a segfault.
Fix "kind mismatch" error message in Pgpool-II. (Muhammad Usama)
Many of "kind mismatch..." errors are caused by notice/warning messages produced by one or more of the DB nodes. In this case now Pgpool-II forwards the messages to frontend, rather than throwing the "kind mismatch..." error. This would reduce the chance of "kind mismatch..." errors.
Fix handling of pcp_listen_addresses config parameter. (Muhammad Usama)
Save and restore errno in each signal handler. (Tatsuo Ishii)
Fix usage of wait(2)
in pgpool main process. (Tatsuo Ishii)
The usage of wait(2)
in Pgpool-II
main could cause infinite wait in the system call. Solution is,
to use waitpid(2)
instead of wait(2)
.
Fix that pool_read()
does not emit error messages when read(2)
returns -1 if
failover_on_backend_error is off. (Tatsuo Ishii)
Fix buffer over run problem in "show pool_nodes". (Tatsuo Ishii)
While processing "show pool_nodes", the buffer for hostname was too short. It should be same size as the buffer used for pgpool.conf. Problem reported by a twitter user who is using pgpool on AWS (which could have very long hostname).
Fix [pgpool-hackers: 1638] pgpool-II does not use default configuration. (Muhammad Usama)
Configuration file not found should just throw a WARNING message instead of ERROR or FATAL.
Fix bug with load balance node id info on shmem. (Tatsuo Ishii)
There are few places where the load balance node was mistakenly put on wrong place. It should be placed on:
ConnectionInfo *con_info[child id, connection pool_id, backend id].load_balancing_node].
In fact it was placed on:
*con_info[child id, connection pool_id, 0].load_balancing_node].
As long as the backend id in question is 0, it is ok. However while testing Pgpool-II 3.6's enhancement regarding failover, if primary node is 1 (which is the load balance node) and standby is 0, a client connecting to node 1 is disconnected when failover happens on node 0. This is unexpected and the bug was revealed.
It seems the bug was there since long time ago but it had not found until today by the reason above.
Fix for bug that pgpool hangs connections to database. (bug 197) (Muhammad Usama)
The client connection was getting stuck when backend node and remote Pgpool-II node becomes unavailable at the same time. The reason was a missing command timeout handling in the function that sends the IPC commands to watchdog.
Fix a posible hang during health checking. (bug 204) (Yugo Nagata)
Helath checking was hang when any data wasn't sent
from backend after connect(2)
succeeded. To fix this,
pool_check_fd()
returns 1 when select(2)
exits with
EINTR due to SIGALRM while health checkking is performed.
Deal with the case when the primary is not node 0 in streaming replication mode. (Tatsuo Ishii)
http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported that if
primary is not node 0, then statement timeout could occur even after
bug194-3.3.diff was applied. After some investigation, it appeared
that MASTER macro could return other than primary or load balance
node, which was not supposed to happen, thus do_query()
sends queries
to wrong node (this is not clear from the report but I confirmed it in
my investigation).
pool_virtual_master_db_node_id()
, which is called in MASTER macro
returns query_context->virtual_master_node_id if query context
exists. This could return wrong node if the variable has not been set
yet. To fix this, the function is modified: if the variable is not
either load balance node or primary node, the primary node id is
returned.
If statement timeout is enabled on backend and do_query()
sends a query to primary node, and all of following user queries are sent to
standby, it is possible that the next command, for example END, could
cause a statement timeout error on the primary, and a kind mismatch
error on pgpool-II is raised. (bug 194) (Tatsuo Ishii)
This fix tries to mitigate the problem by sending sync message instead
of flush message in do_query()
, expecting that the sync message reset
the statement timeout timer if we are in an explicit transaction. We
cannot use this technique for implicit transaction case, because the
sync message removes the unnamed portal if there's any.
Plus, pg_stat_statement will no longer show the query issued by do_query() as "running".
Plus, pg_stat_statement will no longer show the query issued by
do_query()
as "running".
Fix extended protocol handling in raw mode. (Tatsuo Ishii)
Bug152 reveals that extended protocol handling in raw mode (actually
other than in stream mode) was wrong in Describe(
) and Close()
.
Unlike stream mode, they should wait for backend response.
Fix confusing comments in pgpool.conf. (Tatsuo Ishii)
Fix Japanese and Chinese documetation bug about raw mode. (Yugo Nagata, Bo Peng)
Connection pool is avalilable in raw mode.
Fix is_set_transaction_serializable()
when
SET default_transaction_isolation TO 'serializable'. (bug 191) (Bo Peng)
SET default_transaction_isolation TO 'serializable' is sent to not only primary but also to standby server in streaming replication mode, and this causes an error. Fix is, in streaming replication mode, SET default_transaction_isolation TO 'serializable' is sent only to the primary server.
Fix extended protocol hang with empty query. (bug 190) (Tatsuo Ishii)
The fixes related to extended protocol cases in 3.5.1 broke the case of empty query. In this case backend replies with "empty query response" which is same meaning as a command complete message. Problem is, when empty query response is received, pgpool does not reset the query in progress flag thus keeps on waiting for backend. However, backend will not send the ready for query message until it receives a sync message. Fix is, resetting the in progress flag after receiving the empty query response and reads from frontend expecting it sends a sync message.
Fix for [pgpool-general: 4569] segfault during trusted_servers check. (Muhammad Usama)
PostgreSQL's memory and exception manager APIs adopted by the Pgpool-II 3.4 are not thread safe and are causing the segmentation fault in the watchdog lifecheck process, as it uses the threads to ping configured trusted hosts for checking the upstream connections. Fix is to remove threads and use the child process approach instead.
Validating the PCP packet length. (Muhammad Usama)
Without the validation check, a malformed PCP packet can crash the PCP child and/or can run the server out of memory by sending the packet with a very large data size.
Fix pgpool_setup to not confuse log output. (Tatsuo Ishii)
Before it simply redirects the stdout and stderr of pgpool process to a log file. This could cause log contents being garbled or even missed because of race condition caused by multiple process being writing concurrently. I and Usama found this while investigating the regression failure of 004.watchdog. To fix this, pgpool_setup now generates startall script so that pgpool now sends stdout/stderr to cat command and cat writes to the log file (It seems the race condition does not occur when writing to a pipe).
Fix for [pgpool-general: 4519] Worker Processes Exit and Are Not Re-spawned. (Muhammad Usama)
The problem was due to a logical mistake in the code for checking the exiting child process type when the watchdog is enabled. I have also changed the severity of the message from FATAL to LOG, emitted for child exits due to max connection reached.
Fix pgpool hung after receiving error state from backend. (bug #169) (Tatsuo Ishii)
This could happend if we execute an extended protocol query and it fails.
 (Tatsuo Ishii)
After receiving X message from frontend, if Pgpool-II detects EOF on the connection before sending reset query, Pgpool-II could wait for backend which had not received the reset query. To fix this, if EOF received, treat this as FRONTEND_ERROR, rather than ERROR.
Fix for [pgpool-general: 4265] another reset query stuck problem. (Muhammad Usama)
The solution is to report FRONTEND_ERROR instead of simple ERROR when pool_flush on front-end socket fails.
Fixing pgpool-recovery module compilation issue with PostgreSQL 9.6. (Muhammad Usama)
Incorporating the change of function signature for
GetConfigOption()
functions in PostgreSQL 9.6
Fix compile issue on freebsd. (Muhammad Usama)
Add missing include files. The patch is contributed by the bug reporter and enhanced a little by me.
Fix regression test to check timeout of each test. (Yugo Nagata)
Add some warning messages for wd_authkey hash calculation failure. (Yugo Nagata)
Sometimes wd_authkey calculation fails for some reason other than authkey mismatch. The additional messages make these distingushable for each other.


WITNESS LIST Public Health Committee April 30, 2003-8:00A HB 963 Against: Chiodo, Dana (American Electronics Association) Glacken, Shawn (Association of Eletric Companies of Texas) Goleman, Kinnan (Soap & Detergent Association) Miksa, Mary (Texas Association of Business) On: Dillard, Annabelle (Texas Department of Health) HB 2046 For: McGiffert, Lisa (Consumers Union) On: Blass, Casey (Texas Department of Health) HB 2479 For: Appel Jr., Herbert (Self and The Greater Fort Bend Economic Development Council) Conner, Ben (Self) Conner, Gladys (Self) Ferguson, Charles (Self and Texans Supporting State Schools) Garza, J G (Self and Texans Supporting State Schools) Miller, Jim (Self and Texans Supporting State Schools) Snyder, Ruth (Self) Stephens, Mike (Self and PART (Parent Association for the Retarded of Texas)) Against: Anderson, Ed (Self) Borel, Dennis (Coalition of Texas with Disabilities) Cranston, Ron (Self) Eernisse, Virginia (ARC of the Gulf Coast) Gordon, Trisha (Self) Horton, Colleen (Self and Texas Center for Disability Studies) Kafka, Bob (ADAPT) Mizcles, Amy (The Arc of Texas) Murphree, Susan (Advocacy Inc) HB 2495 On: Garanflo, Jaime (Texas State Board of Medical Examiners) HB 2800 For: Nzedu, Jasper (Self) Nzedu, Vivian (Myself) Pickens, Ace (Self) HB 2833 On: Bays, Richard (Tx Dept of Health) HB 2997 For: Lochridge, Patton (1800 Contacts) Magore, Jay (1800 Contacts) McGiffert, Lisa (Consumers Union) Shepard, Janelle (Self) Venable, Peggy (Self and Citizens for a Sound Economy) Against: Avery, BJ (Texas Optometric Asso) Cornett, Dr. John Todd (Texas Optometric Association) Neel, Morris (Self) On: Bays, Richard (Tx Dept of Health) Deloach OD, Joe (Texas Optometry Board) Kloeris, Chris (Texas Optometry Board) HB 3451 For: Burney, Dr. Paul (Tex Psychological Association) Crumley, Marlene (Self) Hopewell PhD, C Alan (Texas Psychological Assocation) Jennings, Peggy (Self) McPherson, Bob (Texas Psychological Association) Yates, Dr. Dee (Texas Psychological Association) Against: Bresnen, Steve (Tex Society of Psychiatric Physicians) Nelson MD, Jefferson (Texas Society of Psychiatric Physicians) Swinney, James (Depression BiPolar Support Allaince of Texas) SB 803 For: Hotze, Steve (Self) SB 939 For: Hotze, Steve (Self) Luedecke, Monica (Self) On: Gonzales, David (Texas Pharmacy Association)


The National tease return of their Homecoming festival for 2020
Who could be heading to Ohio this time around?
The National have teased that their Homecoming festival could be set to return next year – check out the post below.
Matt Berninger and co. launched the event in Cincinnati, Ohio last April, with the band themselves performing two headline sets over the weekend. Their self-curated line-up boasted the likes of Future Islands, Father John Misty, and Feist.
Though the festival didn’t return in 2019, it now appears that a 2020 instalment could be on the cards.
Posting on their official Instagram last night (November 8), The National shared a live shot of themselves featuring the repeated word “Homecoming” in all-capitals. Captioning the black and purple photo, The National wrote the ‘Bloodbuzz Ohio’ lyrics “I was carried to Ohio in a swarm of bees.”
See the post below.
“Looks a lot like I’ll be taking a road trip soon,” wrote one fan in the comments section. Another said: “Yes please let’s do this again.”
This news comes ahead of The National’s UK tour next month, which will see the group take to the stage in Brighton, Leeds, Cardiff, and Nottingham.
Frontman Matt Berninger, meanwhile, has announced his debut solo album ‘Serpentine Prison’. The musician revealed that the upcoming record will be produced and arranged by Booker T. Jones and that we’ll hear “more on it soon”.
Earlier this month, Berninger performed a cover of ‘Not’ by Big Thief during a benefit concert in Toronto.


We are excited to announce that Mask Network builds a partnership with lending protocol WePiggy. The two parties will jointly explore the possibilities of technology integrations, and work together to build a cross-chain DeFi ecosystem.
Mask Network has been trying to create a decentralized applet (DApplet) ecosystem, and we position ourselves to be the bridge that connects internet users from Web 2.0 to Web 3.0. WePiggy focuses on building an open-source, non-custodial crypto-asset lending market protocol that helps users realize asset appreciation and maximize utilization across many blockchain networks. Both parties will work together in fields such as cross-chain DeFi ecosystem building, trying to build a broader on-chain world.
Mask Network and WePiggy have reached an agreement on the cross-chain DeFi ecosystem building. The cooperation will move forward steadily in stages according to the will of both parties.
Starting with cross-chain lending market building: $MASK token has been evaluated and proposed to be listed on WePiggy lending protocol through WIP23 official governance voting.
$MASK will be listed on the BSC mainnet at 15:00 UTC+8 Time on Sep 8th.
$MASK will be listed on the ETH mainnet after Chainlink’s price feeds are ready to ensure the security of the lending and liquidation process.
Mask Network will contribute to the trading liquidity building on DEXs, and the liquidity of MASK token in WePiggy’s lending market, to eliminate systemic risk of WePiggy protocol as much as possible.
More cooperation between WePiggy and MASK Network is on the way, $MASK token holders will be able to use features such as diversified portfolio management, cross-chain asset transfer, and lending on WePiggy in the future.
“Mask Network is the portal that helps traditional internet users transition from Web2.0 to Web3.0. The integration will allow us to take more users into the DeFi world and provide them with secure, powerful and user-friendly cross-chain DeFi applications.”
– Ron, Zheng, Founder and CEO of WePiggy
“Mask wants to bridge the traditional internet and the new, open internet. Mask has always been trying to build an ecosystem that welcomes amazing projects on different blockchains. While WePiggy builds a cross-chain DeFi ecosystem, our vision aligns in connecting different parts of the Web 3.0 world together.”
– Suji Yan, Founder and CEO of Mask Network
About WePiggy
WePiggy is an open-source, non-custodial, crypto-asset lending market protocol. In WePiggy’s market, users can deposit their crypto assets to earn interest or borrow other crypto assets by paying interest. WePiggy aims to spread the benefits of cryptocurrency’s freedom and transparency to the widest possible user community in a more friendly and simple way, as well as be a good partner for them in wealth management.
Github https://github.com/DimensionDev
Twitter https://twitter.com/realMaskNetwork
Facebook https://www.facebook.com/masknetwork
Discord https://discord.com/invite/cKGW45g
Telegram (English) https://t.me/maskbook_group
Telegram （中文） https://t.me/masknetwork_cn


Changing Preferences
Not a good idea to edit the preferences file
Don’t save preferences in it
Settings - user file
Overrides the platform specific file
Different preferences for different files - HTML, CSS, JavaScript
Project specific “settings”
Adding Custom Themes
Soda theme
Download zip file
Rename file: Theme - “Name”
Adding Custom Color Schemes
Preferences - Color Scheme
Kuroir Theme
Rename folder: Color Scheme - “name”
Dark Theme
Creating Custom Key Bindings
Shortcuts
Preferences --> Key bindings default
Edit json file
Write custom commands
Power Editing
Expanding selections of code
Option key - move through one word at a time
Add shift - creates a selection
Select word - cmd+d
Select paragraph - Expand selection to paragraph
Tag structure selection
JavaScript - Bracket - cmd+shift+m
Select by scope - shift+cmd+space
Transposing and Swapping Code
Transpose - swaps letter position or word position
Swap line up or down
Bookmarking a Position In The File
Position or text selection - cmd+F2
Using the Goto Anything Command
cmd+p
switching between files
# fuzzy matching mode
use it in combination with file opening
Jump to line number - : + line number
Symbol list - @ list of ids
Using the Command Palette to Access Seldom-Used Shortcuts
Gives a list of every command available
Using Multiple Selections to Edit Multiple Lines Simultaneously
cmd+drag
Any command will affect all of the cursors at once
Add previous/next line commands
shift+cmd+upArrow/downArrow
Split a normal selection into multiple lines
select lines and split the selection into multiple lines
option + arrow
Creating a Multiple Selection Using Matches
Quick find all - finds all ids
cmd+d after selection adds another selection
Skip - cmd+k
cmd+u = undo
Using Multiple Selections to Edit Large Amounts of Text
select p tags for section of page
Move to text of each paragraph
Copy and paste into a new file
Placing text back into original file
Select all - break selection into lines - paste edited version into original document
Switching Into Vintage Mode To Make Sublime Text Work More Like Vim
Emulates vim’s command mode
Copy from default settings file
Insert Mode
escape to switch to command mode
Hard core vim experience - start newly opened files in vim


Generates a network diagram showing collaborative connections between researchers in CBS and CFANS on a coordinate grid based on degree of cross-college and within-college collaboration
Similar to the network degree visualization, but researchers are clustered according to college affiliation.
Hierarchical Concept Network
Shows connections between researchers based on shared concept terms where researchers are clustered according to college affiliation.
Generates a network diagram showing collaborative connections between researchers in CBS and CFANS in a radial distribution with researchers grouped according to college affiliation
Generates a bar graph depicting how the number of publications involving collaboration between CBS and CFANS has changed over time on a yearly and cumulative basis


Ibidun is an author, artist, poet, and game developer, so here is a list of the games he/she will create.
The Miraculous Kitchen-Piano of Death
List of text-based games.
A Twine story is currently being made based on an existing story.
To see more from Ibidun, visit one of these websites.
Check out this game story that was created in-between--->Clouds in the Sky
And, quickly answer this poll!


Plugin Information |
|---|
View Datadog on the plugin site for more information. |
Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:
This plugin is used to forward metrics, events, and service checks to your account at Datadog, automatically.
Details
Further project details, downloads, and issue tickets are available at https://github.com/DataDog/jenkins-datadog-plugin
Open Issues
We actively use Github's ticketing system to track issues, here. However, some may show up on JIRA. For those situations, here is that list.


--- layout: newsstory title: I SUPPOSE WE DID SCORE THREE match: Yeltz 3 Gresley 4 ---
And it gets worse... this time a 3-4 loss to former champions Gresley, who now done the double over us this season. Yeltz scorers were Birch, Peters and Reed. Hmmm.


Reports on uses of
instanceof
where the expression checked is
this
. Such expressions are indicative of a failure of object-oriented design, and should be replaced by polymorphic constructions.
Powered by InspectionGadgets


| 007:022 Khan | : |
So he misled them with deception. Then when they tasted of the tree, that which was hidden from them of their shame (private parts) became manifest to them and they began to stick together the leaves of Paradise over themselves (in order to cover their shame). And their Lord called out to them (saying): "Did I not forbid you that tree and tell you: Verily, Shaitan (Satan) is an open enemy unto you?" |
| 007:022 Maulana | : |
Thus he caused them to fall by deceit. So when they had tasted of the tree, their shame became manifest to them, and they both began to cover themselves with the leaves of the garden. And their Lord called to them: Did I not forbid you that tree, and say to you that the devil is surely your open enemy? |
| 007:022 Pickthal | : |
Thus did he lead them on with guile. And when they tasted of the tree their shame was manifest to them and they began to hide (by heaping) on themselves some of the leaves of the Garden. And their Lord called them, (saying): Did I not forbid you from that tree and tell you: Lo! Satan is an open enemy to you? |
| 007:022 Rashad | : |
He thus duped them with lies. As soon as they tasted the tree, their bodies became visible to them, and they tried to cover themselves with the leaves of Paradise.  |
| 007:022 Sarwar | : |
Thus, he deceitfully showed them (the tree). When they had tasted (fruits) from the tree, their private parts became revealed to them and they began to cover their private parts with leaves from the garden.  |
| 007:022 Shakir | : |
Then he caused them to fall by deceit; so when they tasted of the tree, their evil inclinations became manifest to them, and they both began to cover themselves with the leaves of the garden; and their Lord called out to them: Did I not forbid you both from that tree and say to you that the Shaitan is your open enemy? |
| 007:022 Sherali | : |
So he caused them to fall into disobedience by deceit. And when they tasted of the tree, their shame became manifest to them and they both began to cover themselves with the leaves of the Gardens. And their Lord called them, saying, 'Did I not forbid you that tree and tell you, verily Satan is to you an open enemy?' |
| 007:022 Yusufali | : |
So by deceit he brought about their fall: when they tasted of the tree, their shame became manifest to them, and they began to sew together the leaves of the garden over their bodies.  |
Concepts/Themes Covered: الإيمان > الغيب > الشيطان > وسوسته Faith> The Unseen World> Satan, the Devil> Satanic Temptations
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


Brilliant, unpredictable, and daring, Ral Zarek was always testing boundaries (and nerves) as a young mage of Ravnica. His bright, fearless skill made him a natural at harnessing the chaotic power of lightning and storms.
The ingenious madness of the Izzet League first drew him in, sparking his obsession with discovery. With defiance and talent, Ral quickly rose through the ranks of the Izzet.
As a Planeswalker, he could travel beyond the bounds of Ravnica, but continued to feel loyalty to the plane and his guild. Then, when the guilds returning to prominence, Ral returned home. He was ready to champion the Izzets that had so shaped him.
Recognizing the beneficial combination of Ral’s talent and loyalty, the dragon guildmaster, Niv-Mizzet, put Ral in charge of researching the Implicit Maze. This puzzle, encoded into Ravnica's streets and alleyways, had long remained a mystery and promised a major advantages to the guild who could decipher it.
Ral and his team of mages diligently tracked down every clue they could discover. But when the time came to solve the Maze, Niv-Mizzet selected a newly created Izzet as the guild's maze-runner.
Ral believes he was the more deserving choice. And his resentment runs deep.
Now Ral is determined to prove his worth, in his defiance of his guildmaster. He will show everyone what a brilliant storm-wielding Planeswalker can do, at any cost—even the guild loyalty he once cherished.


--- layout: post title: 1/28 date: '2015-01-28T20:58:00.001-07:00' author: Jacob . tags: - progress-reports modified_time: '2015-01-28T20:58:25.842-07:00' blogger_id: tag:blogger.com,1999:blog-6400085873105072120.post-8930017423630339652 blogger_orig_url: http://www.svlark.com/2015/01/128.html --- More breaking in the dinghy engine today. Fun to experiment with how much throttle is takes to get on a plane and stay there.


Update May 6, 2022: Now I’m using Todoist for GTD.
Update Oct 21, 2021: I have switched to Nirvana HQ for GTD.
Update Nov 14, 2020: After some experimentation I returned to using Trello for GTD. Roam is well suited for learning and deep work, but not for juggling a lot of small actions. In particular, clarifying/organizing tasks on Roam mobile was painful due to its slow startup and text based input. (Trello on the other hand is fast to start and has dropdowns for moving actions to different lists.) Roam may be better paired with another task management system. Feel free to still read the below as inspiration for your own Roam workflows.
Roam Research is a great note-taking app where each note page tracks its linked and unlinked references. Even without explicitly linking pages Roam will create connections and help you manage your disparate thoughts.
When I was reading through the Welcome to Roam documentation I came across notes on how to set up Getting Things Done in Roam. It was a good starting point, but it doesn't use GTD Contexts to narrow down Next Actions and relies a lot on drag-and-drop to move actions around. Both of these factors limit the total number of tasks that can be managed without getting overloaded and make it harder to do GTD on a phone.
So I’ve come up with a system that uses Roam’s linked references to gather tasks by their context tag, and let me move tasks around without leaving the keyboard.
Capturing
Instead of a specific Bucket page for adding new ideas, I write ideas down wherever I am, along with an #Inbox tag. This has the nice effect of keeping the idea on the page where I first thought of it (and where it’s surrounded by related information). This could be a project page or the Daily Note. Putting new task ideas on the Daily Note page actually makes it possible to track the time between thinking of it and completing it.
Sometimes I save a bit of typing by adding multiple ideas under an #Inbox block. Roam will link the whole thing to the Inbox page.
Clarifying/Organizing
To remind myself of all my non-Roam (a.k.a. satellite) inboxes I have a list of them on the Inbox page. Places like my personal and work emails, my night table, or my desk. I also added orphaned blocks using Roam’s /Find orphan blocks command. (The picture of balloons by ian dooley is there to make processing my Inbox during a Daily Review a bit more fun!)
I start my Daily Review by going to the Inbox page, reviewing each linked reference in order, and asking myself GTD’s clarifying questions:
- What is it?
- What’s the desired outcome?
- What’s the next action(s)?
With the answers to these questions I deal with it in one of the following ways:
- Do It if it takes <2 minutes
- Delegate It if someone else is handling it. In which case I’ll tag their name and #Waiting On
- Defer It if it’s for a later time.
- Either by creating a calendar event (outside of Roam)
- Creating a phone reminder (if it’s something I need to do at a specific time)
- Tagging #Tickler and a future date using /Date Picker if it’s something I want to sort at a later time
- Or tagging it with related topics and #Someday/Maybe
- Tidy It by creating Next Action(s), #Outcomes, or keeping it somewhere as reference
- Trash It if it’s not necessary anymore
Next Actions
To next actions I add a checkbox (using Ctrl + Enter), tags for related topics, and a GTD context tag like:
- #Anywhere
- #[[Someone’s Name]] and #Agenda
- #Calls
- #Errands
- #Home
- #Office
Roam linked references can be filtered (and Roam will even remember filters across browsers and sessions). So for each of these context pages, I’ve set up filters to only show linked references that are TODOs.
I like to complete actions by tagging the current day (using the /Today command) and then checking it off. This adds it to the Daily Note where I journal about what I did during the day.
Roam Shortcuts
Roam’s left sidebar has space for a list of shortcuts. I added the following to make all parts of the GTD workflow easily accessible:
- Inbox
- Next Actions
- Outcomes
- Someday/Maybe
I try to keep this list short because scrolling is limited on mobile. On a desktop computer shortcuts can be added by going to All Pages, finding the context page, clicking … (in the ACTIONS column), and then Add to shortcuts.
On the Next Actions page I have a list of different contexts. If you have only a few contexts, go ahead and add them to the shortcuts on the left sidebar.
Deferring Actions with #Tickler and #Waiting On
The original version of GTD had physical folders for each day of the month, each month of the year, and then future years as needed. When using a digital Tickler like Roam, I prefer to skip the folders for months and years and just tag future dates directly (using the /Date Picker command). It helps that Roam will automatically turn those future dates into a Daily Note when the date comes about.
I used to worry that I might miss a #Tickler or #Waiting On task, if I didn't open Roam every day. But Roam makes it easy to scroll down on the Daily Notes page and see past Daily Notes. To help me remember to do this, I added a reminder to my Daily Review instructions.
If I scroll down I’ll either see blank notes with linked references to #Tickler or #Waiting On tasks that I missed or I’ll see the last Daily Note where I wrote a journal entry. Once I see that last journal entry I’ll know that I won’t need to look any further back.
Projects/Outcomes
“Projects” are what GTD calls any short term goal that takes multiple actions (typically in different contexts). This confused me until I read this article by Laura Earnest. In Roam, I avoid using the term project and instead handle multiple steps by creating an #Outcomes block describing what I want to achieve and listing next actions beneath it.
Plans
I have a page with a copy of the Natural Planning Model that I’ll consult when planning long term projects:
- Define purpose and principles – Why are you doing this? What are the constraints?
- Visualise outcomes – What does success look like? How about wild success?
- Brainstorm – What are all the ideas you can think of?
- Organise – What ideas will you use? Which are the most important? What order will you do them in?
- Identify next actions – What is the very next physical action you can take to progress the project?
I also have a page for GTD Horizons. This is the only GTD list where I keep notes on the page itself, rather than use Roam’s' linked references. This is fine since Horizon planning is very structured and Horizon items change infrequently.
- Horizon 5: Purpose and principles – The purpose, mission and values at the heart of your existence;
- Horizon 4: Vision – A broad overview of what success looks like for you on a 3 – 5 years timeline;
- Horizon 3: Goals – The larger outcomes you’d like to make manifest in the next 1 – 2 years;
- Horizon 2: Areas of Focus and Accountability – The roles and areas of life your committed to focussing on in the next 12 months;
- Horizon 1: Current projects – The list of any outcome you are committed to realising in < 12 months; and
- Ground: Current actions – The comprehensive action list at the core of getting things done.
Reference
This is the easiest part of GTD to handle in Roam. Roam’s reference linking will naturally bring notes back up when they're written about again. When I’m writing I just try to maintain consistent terminology and let Roam do its thing.
Reviews
I start my Daily Reviews on the Inbox page. Clarifying and organizing what Roam has linked, and then looking through my list of satellite inboxes. Then I’ll go to the Daily Notes page (using Alt + D) and scroll down to see if I missed any #Tickler or #Waiting On tasks. I could also go to the Tickler or Waiting On pages directly but these lists can get long (for me at least) and Roam has no way of sorting by date. Plus I use Roam frequently enough that I have yet to need to scroll far. Finally, I’ll plan my day by reading through my Next Actions, and adding block references in the Daily Note I open in the right sidebar.
Once a week, in addition to the usual Daily Review, I’ll also review my Outcomes, Someday/Maybe, and Horizons pages to see if there’s anything that I now want to tackle.
Once a year I’ll also review a summary of GTD, compare it to my GTD page in Roam, and think about where my system can be improved. And that’s how to do GTD with Roam’s linked references and filtering!


olympus
SOCIAL NETWORK
Home
Profile
Profile Page
Newsfeed
Post Versions
Forums
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Profile Page
Terms & Conditions
Events
Privacy Policy
<


Fancy Search
About
close
Fancy Search
Simple search application with Web API.
version @@version
GitHub Repository
Copyright © 2011-2012 Tanjo, Hiroyuki
This application is released under the MIT license.
Thanks to
RequireJS
RequireJS text
Backbone.js
Underscore.js
jQuery
Handlebars.js
jQuery Masonry
tipsy
leanModal
Modernizr
Normalize.css
JavaScript must be enabled for you to use this page.
Your browser is not supported.
Please upgrade to a modern browser.


Call the Marketing Cloud APIs
Username
Secret
Method
Endpoint
San Jose
Dallas
London
Singapore
Params
Method
Params
Method
Params
Method
Params


About Sénégal and Ziguinchor
Senegal
The area is about 200,000 square kilometers which corresponds to barely half the size of Sweden. The population is about 16 million, of which 2 million are living in the capital Dakar.
The average length of life is 67 years and the median age is 18,5 years which means that half the population is under 19 years old. The youth unemployment is high and the average income is low. Half the population is very poor.
The GNP of Senegal is 7 % that of Sweden. The main export products are fish and peanuts.
French is the official language but people mostly speak their own ethnic language like Wolof, Pulaar, Jola, Mandinca and so on. Many speak several of these languages.
Illiteracy is widespread and, in 2015, included more than 40% of the adult population.
Ziguinchor
Ziguinchor is situate in this region of Casamance, south of Gambia. The city in 2013 had a population of about 200.000 inhabitants. It is a typical African city with mostly low buildings, a lot of hustle and bustle, lots of colours and friendly people everywhere. It is a very green city lying by the Casamance River and only one hours drive from the sea.
History
During the 9th and 10th centuries, Islam was introduced to this area and, today, about 94% of the population are Muslims, 5% Christians and the remainder of native religions.
In the 1500´s the Portuguese arrived in West Africa and settled on the island Gorée, close to Dakar, and a bit later the Dutch visited seeking to trade in rubber.
Then in the 1700´s the French founded a commercial town on the island Saint-Louis, it the northern Senegalese river estuary.
During the colonial period, Dakar was the most important port for the transportation of slaves to America.
In 1815 Senegal was recognised as a French Colony but in 1960 it became an independent state and in 1981 the country got full democracy.
Climate
The climate is tropical. During the rainy season, which can last from June until October, there are strong winds from the South-East which can flood the low-lying land areas. The Casamance region in the South is considerably hotter and more damp than the rest of the country.


The picker uses the following enum to represent a breakdown of date/time.
- seconds
- minutes
- hours
- date
- month
- year
Unit Enum
02/05/2022
02/05/2022
A break down of the Unit enum in Tempus Dominus.
datepicker, javascript, open source, tempus dominus, eonasdan


--- layout: about title: About permalink: /about/ ---
Even though programming is becomming paramount in conteporary sceintific work, not everyone has been introduced to the concepts that it involves. We all can write scripts that work, but struggle with doing work that is clear for others. Sometimes we are oblivious to current technologies only because there is nobody around who would introduce us to them.
Aim of this community is to share knowhow of programming. To teach people who are in the position we once were. To teach good habbits so that we can all benefit from each others work. To share knowledge about current approaches and possibilities that arise with software such as Jupyter or new services such cloud computing.
We hold courses on programming topics, either online or in person in Prague.