Gets this machine’s public-facing hostname.
| Return type: | string |
|---|---|
| Returns: | the machine’s public-facing hostname. |
Gets this machine’s private loopback address.
| Return type: | string |
|---|---|
| Returns: | the machine’s private loopback address |
Gets the database engine.
| Return type: | an SQLAlchemy Engine instance. |
|---|
Gets the database’s metadata.
| Return type: | an SQLAlchemy MetaData instance. |
|---|
Gets the global DB lock.
| Return type: | Lock |
|---|---|
| Returns: | the global database lock, although doesn’t acquire it |
Gets the database Session class.
| Return type: | an SQLAlchemy Session class. |
|---|
Gets the location of the ZDStack configuration file.
| Return type: | string |
|---|---|
| Returns: | the full resolved path to the ZDStack configuration file |
Sets the location of the ZDStack configuration file.
| Parameter: | config_file (string) – the new configuration file |
|---|
‘config_file’ will be run through ‘resolve_file()’
Loads the ZDStack configuration file into a ConfigParser.
| Return type: | ZDSConfigParser |
|---|
Gets ZDStack’s ConfigParser.
| Parameters: |
|
|---|---|
| Return type: |
Gets the contents of the ZDaemon master banlist.
| Returns: | the contents of the ZDaemon master banlist. |
|---|---|
| Return type: | string |
Gets the full resolved path to the ZDaemon banlist file.
| Returns: | the full resolved path to the ZDaemon master banlist file, properly parsed into ZDStack’s banlist format |
|---|---|
| Return type: | string |
Gets a ZDStack server proxy.
| Return type: | an instance of either XMLProxy or JSONProxy |
|---|
Gets the installed plugins.
| Parameter: | plugins (list of strings or string) – the names of the plugins to get, if ‘all’, returns all plugins. |
|---|---|
| Return type: | a list of modules |
Turns debugging on or off.
| Parameter: | debugging (boolean) – whether or not debugging is enabled |
|---|
Gets the ZDStack logger.
| Parameter: | reload (boolean) – whether or not to reload the logger |
|---|---|
| Return type: | Logger |
Gets whether debugging is set or not.
| Return type: | boolean. |
|---|
LogEvent represents an event occurring in a log file.
Extract the functions from a plugin module.
| Parameter: | module – a plugin module. get_modules returns a list of these. |
|---|---|
| Return type: | a list of function objects |
Get compiled plugin modules.
| Parameter: | plugin_path – a string representing the full path to the plugin folder |
|---|---|
| Return type: | list of compiled plugin module objects |
Get all plugin functions.
| Parameter: | plugin_path – a string representing the full path to the plugin folder. |
|---|---|
| Return type: | a list of functions |
Test if something is a plugin.
| Parameter: | p – a string representing the filename of a potential plugin file |
|---|---|
| Return type: | Boolean |
Adds authentication to RPC dispatching.
Registers a function to respond to RPC requests.
| Parameters: |
|
|---|
BaseRPCRequestHandler allows a configurable transport MIME-Type.
Handles the HTTP POST request.
Attempts to interpret all HTTP POST requests as RPC calls, which are forwarded to the server’s _dispatch method for handling.
Logs a message
| Parameters: |
|
|---|
Converts a datetime instance into seconds since the epoch.
| Parameter: | dt (datetime) – the datetime instance |
|---|
Converts an exception into a serializable dict.
| Parameters: |
|
|---|
Generates a JSON response.
| Parameters: |
|
|---|
Sets this server’s address.
| Parameter: | address (string) – the address to set |
|---|
Sets this server’s help URL.
| Parameter: | help_url (string) – the help URL |
|---|
Sets this server’s summary.
| Parameter: | summary (string) – the summary to set |
|---|
Handles an HTTPS transaction to an XML-RPC server.
Server represents a daemonized process serving network requests.
Gets the contents of this server’s logfile.
| Returns: | the contents of ZDStack’s logfile. |
|---|---|
| Return type: | string |
This logfile can be really large if debugging is enabled, fair warning.
Gets the current status of the server.
| Returns: | ZDStack’s current status as a server |
|---|---|
| Return type: | string |
Initializes the server configuration:
| Parameter: | reload (boolean) – whether or not the config is being reloaded |
|---|
Loads the config.
| Parameters: |
|
|---|
Shuts the server down.
| Parameters: |
|
|---|
Stack is the main ZDStack class.
Stack does the following things:
- Checks that all server log links and FIFOs exist every 30 min.
- Checks that all ZServs are running every 500 milliseconds
- Polls all ZServs for output
- Parses ZServ output lines into events
- Passes events to the EventHandler and the ZServ’s plugins
- Handles incoming RPC requests
Adds an address to the global banlist.
| Parameters: |
|
|---|
Adds an address to the global whitelist.
| Parameter: | ip_address (string) – the IP address to whitelist |
|---|
Adds an address to a ZServ’s whitelist.”
| Parameters: |
|
|---|
Adds an address to a ZServ’s banlist.
| Parameters: |
|
|---|
Adds a bot.
| Parameters: |
|
|---|
Adds a map to the maplist.
| Parameters: |
|
|---|
Ensures that all ZServ configuration sections are correct.
| Parameter: | configparser (ZDSConfigParser) – the configuration to check |
|---|
If a configuration error is found, an Exception is raised.
Clears the maplist.
| Parameter: | zserv_name (string) – the name of the ZServ |
|---|
Gets the value of a variable.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the value of the variable as a string |
Returns a list of zserv info dicts.
| Parameter: | names (list of strings) – an optional list of zserv_names for which to return information - used as a limit. |
|---|
See get_zserv_info() for more information.
Returns a ZServ instance.
| Parameter: | zserv_name (string) – the name of the ZServ to start |
|---|
Returns a ZServ’s configuration as a string.
| Parameter: | zserv_name (string) – the zserv’s name |
|---|
Returns a dict of zserv info.
| Parameter: | zserv_name (string) – the name of the ZServ to get info for |
|---|---|
| Return type: | dict |
| Returns: | {‘name’: <string: internal name of ZServ>, ‘hostname’: <string: hostname of ZServ>, ‘mode’: <string: Game mode of ZServ>, ‘wads’: <strings: list of ZServ’s WADs>, ‘optional_wads’: <strings: list of ZServ’s optional WADs>, ‘ip’: <string: the ZServ’s IP address>, ‘port’: <int: ZServ’s port>, ‘players’: <int: number of connected players>, ‘max_players’: <int: maximum number of connected players>, ‘map_name’: <string: name of the current map>, ‘map_number’: <int: number of the current map>, ‘round_id’: <int: ID of the current round>, ‘is_running’: <boolean: whether ZServ is currently running>} |
Handles events.
| Parameters: |
|---|
Kicks a player from the zserv.
| Parameters: |
|
|---|
Removes an address from a ZServ’s banlist.
| Parameters: |
|
|---|
Returns a list of ZServ names.
| Parameter: | names (list of strings) – an optional list of zserv_names which are to be returned - used as a limit |
|---|
Loads the configuration.
| Parameters: |
|
|---|
Changes the current map.
| Parameters: |
|
|---|
Returns the maplist.
| Parameter: | zserv_name (string) – the name of the ZServ |
|---|
Returns a list of strings representing the numbers of the maps in the maplist.
Parses ZServ output into events, places them in the event queue.
| Parameters: |
|---|
Returns a list of players and their info.
| Parameter: | zserv_name (string) – the name of the ZServ |
|---|---|
| Return type: | list of LogEvent instances |
| Returns: | Each LogEvent instance represents one line of the of the zserv’s response. The dict looks like: {‘player_num’: 0, ‘player_name’: ‘superman’,
|
Removes an address from the global banlist.
| Parameter: | ip_address (string) – the IP address to ban |
|---|
Removes an address from the global whitelist.
| Parameter: | ip_address (string) – the IP address to whitelist |
|---|
Adds an address to a ZServ’s whitelist.”
| Parameters: |
|
|---|
Removes all bots.
| Parameter: | zserv_name (string) – the name of the ZServ |
|---|
Resets all scores.
| Parameter: | zserv_name (string) – the name of the ZServ |
|---|
Restarts all ZServs.
| Parameter: | names (list of strings) – an optional list of zserv_names which are to be stopped - used as a limit |
|---|
Restarts a ZServ.
| Parameter: | zserv_name (string) – the name of the ZServ to start |
|---|
Sends a message from “] CONSOLE [“.
| Parameters: |
|
|---|
Sends a command to a running zserv process.
| Parameters: |
|
|---|
Sets the value of a variable
| Parameters: |
|
|---|
Sets a ZServ’s config.
| Parameters: |
|
|---|
Starts all ZServs.
| Parameter: | names (list of strings) – an optional list of zserv_names which are to be started - used as a limit |
|---|
Starts a ZServ.
| Parameter: | zserv_name (string) – the name of the ZServ to start |
|---|
Stops all ZServs.
| Parameter: | names (list of strings) – an optional list of zserv_names which are to be stopped - used as a limit |
|---|
Stops a ZServ.
| Parameter: | zserv_name (string) – the name of the ZServ to start |
|---|
Toggles a boolean option.
| Parameters: |
|
|---|
Unsets a variable (removes it).
| Parameters: |
|
|---|
Returns a list of the used WADs.
| Parameter: | zserv_name (string) – the name of the ZServ |
|---|---|
| Return type: | list of strings |
| Returns: | Each list member is the name of a used WAD. |
Checks that a string is a properly formed IP address.
| Parameter: | ip (string) – the string to check |
|---|
Raises an Exception if the IP address is malformed. This method also raises an Exception if the address is either a broadcast or private address.
Creates a file with proper permissions.
| Parameter: | filepath (string) – the full path to the file to create |
|---|
Gets a LogEvent from a line.
| Parameters: |
|
|---|---|
| Returns: | a LogEvent parsed from the given line or None |
| Return type: |
Homogenizes a string.
| Parameter: | s (string) – a string to homogenize |
|---|---|
| Return type: | string |
| Returns: | a homogenized string, with spaces, newlines, and tabs removed |
Escapes HTML.
| Parameter: | s (string) – a string to escape |
|---|---|
| Return type: | string |
| Returns: | an escaped string |
This function is basically ripped from web.py; with any luck, the MIT and BSD licenses are compatible... :) I don’t think Mr. Swartz would have a cow, tho.
Converts a properly formatted string into a Ban
| Parameter: | line (string) – a line to convert |
|---|---|
| Return type: | Ban |
Parses a player’s name into a tag and a base player name.
| Parameter: | name (string) – the raw name to parse |
|---|---|
| Return type: | a 2-Tuple of strings |
| Returns: | (‘tag’, ‘name’) |
Like requires_lock, but it acquires its parent’s instance lock.
This function decorator works on instance methods, acquiring their parent instance’s lock before executing.
A function decorator that acquires a lock before executing.
| Parameter: | lck (Lock) – the Lock that the function requires |
|---|
Resolves a path.
| Parameter: | f (string) – a path to resolve |
|---|---|
| Return type: | string |
| Returns: | The expanded, absolute path of a given file/folder. |
Sends an RPC request, returning the result or printing an error.
| Parameters: |
|
|---|
If an error occurs, it will be printed to STDERR. This is because this method is primarily for use by scripts trying to interact with a running ZDStack.
Converts a timedelta into seconds.
| Parameter: | td (timedelta) – a timedelta to convert |
|---|---|
| Return type: | int |
Adds an address to a ZServ’s list.
| Parameters: |
|---|
Adds an address to the global list.
| Parameters: |
|
|---|
Gets an address from a ZServ’s list.
| Parameters: | |
|---|---|
| Returns: | a matching IP address; searches both the ZServ’s address list and the global address list; if no matching addresses are found, returns None |
| Return type: | IPAddress or None |
Gets all addresses from a ZServ’s list.
| Parameter: | zserv (ZServ) – a ZServ from which to get the addresses |
|---|---|
| Return type: | a sequence of addresses |
Gets all addresses from a ZServ’s list, excluding globals.
| Parameter: | zserv (ZServ) – a ZServ from which to get the addresses |
|---|---|
| Return type: | a sequence of addresses |
Gets all global addresses.
| Return type: | a sequence of addresses |
|---|
Gets an address from a ZServ’s list.
| Parameters: | |
|---|---|
| Returns: | a matching IP address; searches only the ZServ’s address list |
| Return type: |
Gets a global address.
| Parameter: | address (string) – an address to match up and return |
|---|---|
| Returns: | a matching IP address or None if not found |
| Return type: | IPAddress |
Removes an address from a ZServ’s list.
| Parameters: | |
|---|---|
| Returns: | whether or not the address existed |
| Return type: | boolean |
Removes an address from the global list.
| Parameter: | address (string) – an address to remove from the list |
|---|---|
| Returns: | whether or not the address existed |
| Return type: | boolean |
Searches for an address.
| Parameters: | |
|---|---|
| Returns: | False if the address is not found, True or the reason listed with the address if found. |
| Return type: | boolean or string |
This method will search for IP addresses in a ZServ’s address list that either match or contain the given address, using the wildcard expansions supported by IPAddress.
Searches for an address.
| Parameters: | |
|---|---|
| Returns: | False if the address is not found, True or the reason listed with the address if found. |
| Return type: | boolean or string |
This method will search for IP addresses in a ZServ’s address list that either match or contain the given address, using the wildcard expansions supported by IPAddress. This method does not consider matching addresses found only in the global list as matches.
Searches for an address.
| Parameter: | address (string) – an address to search for |
|---|---|
| Returns: | False if the address is not found, True or the reason listed with the address if found. |
| Return type: | boolean or string |
This method will search for IP addresses in the global address list that either match or contain the given address, using the wildcard expansions supported by IPAddress.
Renders this Ban.
| Return type: | string |
|---|---|
| Returns: | a string representation of the ban in ZDaemon banlist format. Unless saving into a zserv’s banlist file, you probably just want to use the str() method on Ban instances instead. |
IPAddress represents an IP address or IP addresses.
IPAddress supports 2 types of range expansions:
- 192.168.2.*: Matches anything for ‘*’
- <IP_ADDRESS>-34: Matches address from 17-34 inclusive
IPAddresses representing IP ranges can also be tested for membership, for example:
>>> IPAddress('<IP_ADDRESS>') in IPAddress('<IP_ADDRESS>-5')
True
Creates an object of the same type as this instance.
| Parameter: | address (either string or int/long) – an IP address |
|---|---|
| Returns: | An object of the same type as this instance, with a separate address. This is most useful for subclasses. |
Renders this IPAddress.
| Return type: | string |
|---|---|
| Returns: | a nicely formatted string representing this IPAddress, suitable for re-parsing or saving to a file |
RawZDSConfigParser improves on ConfigParser.RawConfigParser.
The following improvements are made:
- All operations are threadsafe.
- the internal dict of defaults is never returned
- get() and get*() methods can handle default arguments.
- getdecimal(), getlist() and getpath() methods were added
- section order is preserved
- read/readfp were replaced by load and loadfp
- reload/reloadfp/save methods were also added
Regarding get*() methods and defaults, passing ‘None’ (or nothing) as the ‘default’ argument causes the ‘NoOptionError’ to be raised if an option is not found. This is also the default behavior.
Adds a section.
| Parameter: | section (string) – the name of the new section |
|---|
Gets a dict of options & values from the DEFAULT section.
| Returns: | a dict of options & values from the DEFAULT section |
|---|---|
| Return type: | dict |
Gets an option’s value.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. This method also excludes the DEFAULT section. |
Gets an option’s value if it is defined and True.
| Parameters: |
|
|---|---|
| Returns: | the option’s value if it is defined and True. Otherwise returns None. |
Gets an option’s value if it is defined and non-False.
| Parameters: |
|
|---|---|
| Returns: | the option’s value if it is defined and non-False. Otherwise returns None. |
Gets an option’s value as a boolean.
| Parameters: |
|
|---|---|
| Return type: | boolean |
| Returns: | the boolean value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a Decimal.
| Parameters: |
|
|---|---|
| Return type: | Decimal |
| Returns: | the Decimal value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a float.
| Parameters: |
|
|---|---|
| Return type: | float |
| Returns: | the float value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as an int.
| Parameters: |
|
|---|---|
| Return type: | int |
| Returns: | the int value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a list.
| Parameters: |
|
|---|---|
| Return type: | list |
| Returns: | the parsed list value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a resolved path.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. The value will be passed through os.path.abspath(os.path.expanduser(v)). |
Checks if a section contains a specified option.
| Parameters: |
|
|---|---|
| Return type: | boolean |
Tests if a section exists or not.
| Parameter: | section (string) – the name of the section to test for |
|---|---|
| Return type: | boolean |
| Returns: | a boolean whether the section exists or not |
Gets a section’s items.
| Parameter: | section (string) – the name of the section whose items are to be returned |
|---|---|
| Return type: | list of 2-Tuples |
| Returns: | a list of a section’s options and values, i.e. [(‘option’, ‘value1’), (‘option2’, ‘value2’)] |
Returns a section’s options.
| Parameter: | section (string) – the name of the section whose options are to be returned |
|---|---|
| Return type: | list of strings |
| Returns: | a list of strings representing the names of the options |
Old ‘read’ method from ConfigParser.
| Parameter: | filenames (list of strings) – the names of the files to parse |
|---|
This method will raise an Exception if used, the ZDSConfigParsers are designed to be used with one file only. Typically the “read a bunch of files for data” method was only useful when checking a prioritized list of possible config files, but ZDStack already does this in __init__, so this method has become useless.
Old ‘readfp’ method from ConfigParser.
| Parameter: | fp (file) – a file object whose contents are to be parsed |
|---|
For the same reasons ‘read’ is useless, this method is also useless and will also raise an Exception if used.
Removes an option from a section.
| Parameters: |
|
|---|---|
| Return type: | boolean |
| Returns: | True if the option existed |
Removes a section.
| Parameter: | section (string) – the section to be removed |
|---|---|
| Return type: | boolean |
| Returns: | True if the section existed |
Gets a list of section names.
| Returns: | a list of section names |
|---|---|
| Return type: | a list of strings |
Sets a section’s option to ‘value’.
| Parameters: |
|
|---|
ZDSConfigParser is RawZDSConfigParser with magic interpolation.
All interpolation is done with SafeConfigParser’s methods, so interpolation shouldn’t get out of control.
Gets an option’s value without interpolation.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value without interpolation.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Returns a section’s items.
| Parameters: |
|
|---|---|
| Return type: | list of 2-Tuples |
| Returns: | a list of a section’s options and values, i.e. [(‘option’, ‘value1’), (‘option2’, ‘value2’)] |
Sets a section’s option to ‘value’.
| Parameters: |
|
|---|
Gets the global Session instance.
| Returns: | the global Session instance |
|---|---|
| Return type: | Session |
This is a contextmanager that opens a transaction, committing or rolling back as necessary.
Creates a new Session instance.
| Returns: | a new Session instance |
|---|---|
| Return type: | Session |
This is a contextmanager that opens a transaction, committing or rolling back as necessary.
A function decorator executing the function inside a session.
If no session is given with the keyword argument ‘session’, the global session is used.
The base EventHandler class.
An EventHandler maps event categories to handler functions. These functions use the signature ‘handler(event, zserv)’.
Don’t use _event_categories_to_handlers directly, instead use get_handler() and set_handler()
Returns a handler method for a given event_category.
| Parameter: | event_category (string) – the category of an event for which to return a handler. |
|---|---|
| Return type: | function |
Handles an error event.
| Parameters: |
|---|
Handles an unhandled event.
| Parameters: |
|---|
Sets the handler method for a certain event_category.
| Parameters: |
|
|---|
Handles a connection event.
| Parameters: |
|---|
Handles a flag_touch event.
| Parameters: |
|---|
Handles a frag event.
| Parameters: |
|---|
Handles a game_join event.
| Parameters: |
|---|
Handles a map_change event.
| Parameters: |
|---|
SynchronizedFile is a threadsafe interface to an on-disk file.
Loads data from a file object.
| Parameter: | fobj (file) – the file containing data |
|---|
This SynchronizedFile’s filename will also be set to the resolved value of the file object’s .name attribute, so the passed file object must have a .name attribute.
Reloads data from a file object.
| Parameter: | fobj (file) – the file containing data |
|---|
This SynchronizedFile’s filename will also be set to the resolved value of the file object’s .name attribute, so the passed file object must have a .name attribute.
Writes this SynchronizedFile to disk.
The data that is written is the output of str(self), so subclasses can override __str__.
Sets the location of the on-disk file.
| Parameter: | filename (string) – the new location of the on-disk file |
|---|
Alias represents a player’s alias.
There is no way for ZDStack to determine player identity completely on its own; an administrator must setup mappings between StoredPlayers and Aliases. However, player names and addresses must be stored, so we assume that everything is an Alias and store it as such.
Represents a flag return.
Represents a flag touch.
Represents a frag.
GameMode represents a game’s mode, i.e. TeamDM, CTF, etc.
Map represents a map in a WAD.
The shortname of a map.
| Return type: | unicode |
|---|---|
| Returns: | the short-hand name of a map. Maps have a history of shorthand names, i.e. D5M1, E2M1, ZDCTF04, ODA02, etc. This method attempts to figure these out for the given map. |
Port represents a Doom source port.
Represents an RCON access.
Represents an RCON action.
Represents an RCON denial.
A Round represents a single round of play.
Represents a player.
TeamColor represents a team’s color.
Teams can be much more than just colors, for instance, it’s possible for an IDL ‘team’ to play different rounds as different using different ‘team colors’. So we simply store the team’s color and require the administrator to create their own mapping between whatever they think a ‘team’ is, and that team’s color in the round.
Wad represents a WAD file.
The prefix of this WAD.
| Return type: | unicode |
|---|---|
| Returns: | the short name of the WAD. WADs have history of prefixes assigned to them, i.e. ZDCTF, this method attempts to figure these prefixes out for the given WAD. |
The short name of this WAD.
| Return type: | unicode |
|---|---|
| Returns: | the short name of the WAD. WADs have history of having their names shortened, i.e. ZDCTF or EpicCTF, this method attempts to figure these short-hand names out for the given WAD. |
PlayersList is a threadsafe list of players.
It is possible that many threads will try and modify the players list at the same time, with unpredictible results. PlayersList synchronizes access to its internal list of players so that any addition or removal of players is done atomically, and so that the internal list doesn’t change during these operations.
Kicks banned players.
| Parameter: | session (SQLAlchemy Session) – a database session |
|---|
Returns an Alias instance.
| Parameters: |
|
|---|---|
| Return type: | Alias |
Either name or ip_address_and_port is optional, but at least one must be given. Note that only giving name can potentially return the wrong player, as multiple players can have the same name.
Returns the player whose name matches a list of names.
| Parameters: |
|
|---|---|
| Return type: | Player |
| Returns: | the player whose name matches the earliest name in ‘possible_player_names’ |
Syncs the internal players list with the running zserv.
| Parameters: |
|
|---|
A Regexp is a wrapper around a raw regular expression string.
Regexp is useful because it allows prefixes, and the ability to create an Event from a line.
Gets an event.
| Parameters: |
|
|---|---|
| Return type: | LogEvent |
Tests whether a string matches this Regexp.
| Parameter: | s (string) – a string to match |
|---|---|
| Return type: | boolean or dict |
| Returns: | A dict of group names and values if the string matches, False otherwise |
This method actually uses ‘.search()’, so be wary.
ServerRegexp matches lines from a zserv’s log output.
Parses a message, extracting potential names of the sender.
| Parameter: | s (string) – the message to parse |
|---|---|
| Return type: | tuple |
| Returns: | ([‘potential’, ‘names’, ‘of’, ‘the’, ‘sender’, ‘message without prefix’) |
Represents a Task to be performed.
Performs this Task.
| Parameters: |
|
|---|---|
| Returns: | the output of self.func |
Creates a thread.
| Parameters: |
|
|---|---|
| Return type: | threading.Thread |
| Returns: | the newly created Thread |
Creates a thread that processes tasks in a Queue.
| Parameters: |
|
|---|---|
| Return type: | threading.Thread |
| Returns: | the newly created Thread |
ZServAccessList represents a ZServ’s access list.
If a single IP ban conflicts with a whitelisted address, an exception is raised. If a ban using wildcards conflicts with one or more whitelisted addresses, the ban is sliced into pieces, omitting the conflicting whitelisted addresses.
Adds an access control.
| Parameter: | access_control (either Ban or WhiteListedAddress) – a ban or whitelist to add |
|---|
Removes an access control.
| Parameter: | access_control (either Ban or WhiteListedAddress) – a ban or whitelist to add |
|---|
Searches this ZServ’s ban list for the address.
| Parameter: | address (string) – an address to test |
|---|---|
| Returns: | whether or not the address is banned. |
| Return type: | boolean, string, or None |
Even if an address is present on the ban list, if it is also on the white list, False is returned. If it is not on the white list, the reason for the ban is returned as a string. If the address is not found at all, None is returned.
ZServConfigParser parses a config for a ZServ.
ZServConfigParser contains special methods for obtaining ZServ configuration values.
Gets an option’s value.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets configuration data.
| Return type: | string |
|---|---|
| Returns: | configuration data as a string in zserv configuration format |
Gets an option’s value without interpolation.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
The ‘section’ parameter is ignored, replaced by self.zserv.name. The signature is as it is because it’s called by other methods that aren’t overridden here.
Gets an option’s value as a boolean.
| Parameters: |
|
|---|---|
| Return type: | boolean |
| Returns: | the boolean value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a Decimal.
| Parameters: |
|
|---|---|
| Return type: | Decimal |
| Returns: | the Decimal value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a float.
| Parameters: |
|
|---|---|
| Return type: | float |
| Returns: | the float value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as an int.
| Parameters: |
|
|---|---|
| Return type: | int |
| Returns: | the int value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a list.
| Parameters: |
|
|---|---|
| Return type: | list |
| Returns: | the parsed list value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
Gets an option’s value as a resolved path.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. The value will be passed through os.path.abspath(os.path.expanduser(v)). |
Gets an option’s value as a percentage.
| Parameters: |
|
|---|---|
| Return type: | string |
| Returns: | the string value of the option (as a percentage) if found. If the option is not found, but ‘default’ is not None, the value of the ‘default’ argument will be returned. Otherwise a NoOptionError is raised. |
The returned percentage will never be higher than 100%, use ‘getdecimal()’ for that.
Checks if this ZServ’s config contains a specific option.
| Parameter: | option (string) – the option to check for |
|---|---|
| Return type: | boolean |
Gets this ZServ’s config’s items.
| Return type: | list of 2-Tuples |
|---|---|
| Returns: | a list of a section’s options and values, i.e. [(‘option’, ‘value1’), (‘option2’, ‘value2’)] |
Gets this ZServ’s config’s options.
| Return type: | list of strings |
|---|---|
| Returns: | a list of strings representing the names of the options |
Process a config.
| Parameter: | reload (boolean) – whether or not to reload the configuration |
|---|
After the config has been successfully processed, this ZServConfig updates its ZServ’s instance variables
Removes an option from this ZServ’s config.
| Parameter: | option (string) – the option to be removed |
|---|---|
| Return type: | boolean |
| Returns: | True if the option existed |
Emit a record.
If a formatter is specified, it is used to format the record. The record is then written to the stream with a trailing newline [N.B. this may be removed depending on feedback]. If exception information is present, it is formatted using traceback.print_exception and appended to the stream.
ZServ provides an interface to a zserv process.
ZServ does the following:
- Handles configuration of the zserv process
- Provides control over the zserv process
- Provides a method to communicate with the zserv process
- Exports server configuration information
Handles a map change event.
| Parameters: |
|
|---|
Cleans up after a round.
| Parameter: | session (SQLAlchemy Session) – a database session |
|---|
Gets this ZServ’s current GameMode.
| Parameter: | session (SQLAlchemy Session) – a database session |
|---|---|
| Return type: | GameMode |
| Returns: | the current GameMode |
Gets this ZServ’s current Map.
| Parameter: | session (SQLAlchemy Session) – a database session |
|---|---|
| Return type: | Map |
| Returns: | the current Map or None |
Gets this ZServ’s current Round.
| Parameter: | session (SQLAlchemy Session) – a database session |
|---|---|
| Return type: | Round |
| Returns: | the current Round or None |
Gets this ZServ’s current (source) Port.
| Parameter: | session (SQLAlchemy Session) – a database session |
|---|---|
| Return type: | Port |
| Returns: | the current (source) Port |
Tests whether or not the internal zserv process is running.
| Returns: | whether or not the internal zserv process is running |
|---|---|
| Return type: | boolean |
Loads this ZServ’s config.
| Parameter: | reload (boolean) – whether or not the configuration is being reloaded; if this is the first load, there are some things (like creating FIFOs, etc.) we need to do that we don’t want to do if the internal zserv is still running |
|---|
Removes a temporary ban.
| Parameters: |
|
|---|
Restarts the zserv process, restarting it if it crashes.
| Parameter: | signum (int) – the signal to send to the internal zserv, SIGTERM by default |
|---|
Sends a message to the running zserv process.
| Parameters: |
|
|---|---|
| Return type: | list of LogEvent instances |
| Returns: | a list of response events, if event_response_type is None, the list will be empty |
Starts the zserv process.
This keeps a reference to the running zserv process in self.zserv.
Stops the zserv process.
| Parameters: |
|
|---|---|
| Return type: | boolean or string |
| Returns: | if an error occurred while stopping the internal zserv, it is returned as a string - otherwise False is returned |
Adds a ban.
| Parameters: |
|
|---|
Adds a bot.
| Parameter: | bot_name (string) – the name of the bot to add |
|---|
Adds a map to the maplist.
| Parameter: | map_number (int) – the number of the map to add |
|---|
Adds a ban with an expiration.
| Parameters: |
|
|---|
Gets a variable.
| Parameter: | variable_name (string) – the name of the variable whose value is to be returned |
|---|---|
| Return type: | list of LogEvent instances |
Kicks a player.
| Parameters: |
|
|---|
Removes a ban.
| Parameter: | ip_address (string) – the IP address to unban |
|---|
Changes the current map.
| Parameter: | map_number (int) – the number of the map to change to |
|---|
Gets the maplist.
| Return type: | list of LogEvent instances |
|---|
Returns information about a player.
| Parameter: | player_number (string) – the number of the player for which to return player information. |
|---|---|
| Return type: | list of LogEvent instances |
Returns a list of players in the server.
| Return type: | list of LogEvent instances |
|---|
Sends a message as ‘] CONSOLE [‘.
| Parameter: | message (string) – the message to send |
|---|
Sets a variable.
| Parameters: |
|
|---|
Toggles a boolean variable.
| Parameter: | boolean_variable (string) – the name of the variable whose value is to be toggled |
|---|
Un-sets a variable.
| Parameter: | variable_name (string) – the name of the variable whose value is to be un-set |
|---|
Gets the currently used WADs.
| Return type: | list of LogEvent instances |
|---|


This blog post is hosted on GitHub here. Feel free to file a ticket or send a PR.
October 25, 2019
October 24, 2019


[72]
Environmental Protection Agency. Inventory of U.S. Greenhouse Gas Emissions and Sinks
https://www.epa.gov/ghgemissions/inventory-us-greenhouse-gas-emissions-and-sinks


--- layout: default group: "navigation" title: "Portfolio" heading: "CONSULTING" tagline: "Portfolio" description: --- {% include JB/setup %}
Condense has extensive experience using the .NET Framework to deliver business applications and fronting sophisticated business and integration systems.
We have recently delivered:
A whole-of-university data-publishing application, integrating with national research-data-storage infrastructure and international identifier standards, and publishing records to the national research repository.
A business system to support whole-of-university building condition and functionality audits allowing reporting and modelling based on the data gathered.
Sub-contracting .NET and Azure expertise to large enterprise development projects.
Condense is known for the quality of the user experiences it delivers.
We have recently delivered:
A mobile app (iOS and Android) complementing the Asset Management Information System supporting on-the go access and workflow by maintenance contractors and staff.
A web application to allow researchers to gather and prepare information for upload to the metadata repository. Now used by four clients.
Mobile apps for “citizen science” initatives: Kelp tracker and Redmap.
We have recently undertaken:
A comprehensive review of data sources, processing and reporting standards of the wild-capture commercial fisheries sector as they transition to digital platforms as part of the $5 million Fisheries Digital Transition project.
A detailed requirement gathering exercise including workshops with key project stakeholders to develop a comprehensive scope of works to increase up-take and expand capabilities of a University research data management solution.
We have recently undertaken:
Tracking and reporting on the Universities built environment, energy and emissions.
Interactive analytics and reporting necessary for staff to develop the forward works program for the University's property portfolio.
Condense has a breadth of experience across the research data management working with tertiary institutions and government clients.
After going to the eResearch conference we decided it was time to pull together a portfolio of the work we've done in the Research data space. We've been working in the space for over 7 years now.
Our experience includes engagements to develop strategies, designing solutions, developing data capture applications, managing data publishing services, business process and data analysis work.
Here's our Research Data Portfolio.
Condense has deep experience in the asset management space.
We have delivered numerous applications covering a wide range of facilities management functions, including the Work Requests system and contractor login, Project Management Register, the Asset Register, Planned Maintenance, Security Incident Management, and emissions data reporting.
We have integrated with other systems including the Tech 1 for project budget management and Purchase Now for enterprise procure-to-pay workflow.
On-the-go field access, already a major use case through responsive web applications, has just been significantly improved with the launch of a native mobile application.
A core factor of this transformation has been careful analysis and designing applications with the web in mind.
The success of these projects has led to significantly improved data capture and workflow compliance across all areas of the business.


IMC operator LDAP / SSL authentication
9 May 2014 · Filed in NetworkingIMC administrator / operators can be externally authenticated via LDAP or Radius. Combine LDAP authentication and a Active Directory and you get and easy way to authenticate your IMC administrators.
LDAP is relatively easy to setup if you´re using the basic configuration without encryption (SSL). While an easy and quick setup is nice now and then I will also go through the setup of LDAP over SSL authentication. In my opinion using encryption is crucial because passwords and usernames in cleartext over the wire isn´t exactly best practice.
In this post I will go through the following steps:
- Setup basic operator LDAP authentication.
- Enable SSL authentication.
Part 1: Setup basic operator LDAP authentication.
First we need to define an LDAP operator account in AD. IMC will use this account to do LDAP lookups. Grab hold of your favorite AD administrator or do it yourself. The user only needs to be member of the "domain user" group and nothing more. In this example I will use the account name "imc-operator-ldap".
Next we need to find the full DN of the user where we will use the command "dsquery":
[php]:\Users\imc-operator-ldap>dsquery user -name imc*
"CN=imc-operator-ldap,CN=Users,DC=hp-lab,DC=local"[/php]
We can now use this information to configure the LDAP server in IMC:
- Server type : Microsoft Active Directory.
- Server Address: The IP adress of your AD server.
- Server Port: 389 for basic authentication and 636 for SSL.
- Base DN: This is the base search level for your operator user. In this case we take the following from our dsquery "DC=hp-lab,DC=local".
- Admin DN: This is the full DN of your IMC operator. In this case we take the following from our dsquery "CN=imc-operator-ldap,CN=Users,DC=hp-lab,DC=local"
- Admin password: The password of the IMC operator AD user.
- Username attribute: Leave this at standard.
Define IMC user operator
With the LDAP server configured we now need to configure the actual administrative user which we will log on to IMC with.
First configure the AD user. This is a trivial task which I will not cover in this post.
Next we will configure the user in IMC:
- Login name: The same as the AD account login name.
- Full name: The same as the Login name.
- Authentication type: LDAP.
You can leave the rest as per standard.
Now you can verify the configuration by loggin in with your new operator login!
Step 2: Configure LDAP over SSL
For this step we need the following things:
- CA server certificate in base64 format.
- Configure SSL over LDAP in IMC.
The easiest way of grabbing the CA certificate is pointing your favorite webbrowser to the following: "http://ip-address-of-your-ca/certsrv". Next choose "Download a CA certificate, certificate chain, or CRL" and click on "Base64". Download the certificate file by choosing "Download CA certificate".
To finalize the configuration go to the LDAP config under IMC again:
- Server port: 636.
- Select "Requires Security Connection (SSL).
- Click on "Authentication File Configure" and upload the Base64 CA certificate.
And that´s it! Verify by logging in with your AD credential.


Are you sure you want to delete this blog.
{{single_blog.Blog.title}}
{{single_blog.Blog.description}}
{{single_blog.Blog.date_uploaded}}
{{single_blog.Blog.name}}{{single_blog.Blog.body}}
{% if allow_edit %}
{% endif %}
{{single_blog.Users.first_name}} {{single_blog.Users.last_name}}
{{single_blog.Users.about}}


Rank higher than others. Google likes a secure website. Increase your website’s SEO rankings on Google and other search engines with our free SSL certificate you get with Business web hosting.
Generate secure card payments. Protect transactions through your website with SSL certificate you get with Business hosting, boost your sales with a variety of secure payment choices for your clients.
Let your clients trust you.
Easy setup & 24/7 customer support. Cheap and secure web hosting has never been easier, go live and secure instantly with our dedicated live support who will answer all your questions.
Most powerful encryption. No hacker will be able to access your valuable information with free SSL Certificate as it encrypts the path through which data between your customer and you travel.
Protect your WordPress hosting. With our Business cheap web hosting plan, SSL comes free and it also protects your WordPress website, blog or business. Make use of this advantage!
All websites running on our Business web hosting plans with free SSL certificate creates a secure path for data to be passed over safely. Don’t pay any extra for the security of your website, use our free SSL and secure your website and your client's trust. This is a simple way to increase your revenue as a secure connection will allow secure payment transactions.
As soon as any sensitive information is entered on your website, SSL security you get with Business cheap web hosting plan instantly encrypts it. SSL encryption with protected data then travels to the server website is ran from, and decrypts it only when it’s safe and only for the website owner to see. Free SSL protects your client's data from message forgeries, theft, and unnecessary eavesdrop.
Free SSL certificate provided by Hostinger with every Business web hosting plan, will ensure your data is safe. Hostinger’s SSL for WordPress will also protect your blog or e-commerce shop, no need to worry about safe transactions anymore! The encryption, which protects your client’s data from theft and unnecessary eyes is the strongest in the current market and based on SSL protocol.
Our cheap web hosting plan now offers a free SSL certificate to provide a safe connection between you and your client!
Google cares about safe links between a customer and your website’s server. Pages with SSL certificates will have a higher SEO ranking in Google & other search engines. There's no doubt that websites with https rank better than those without. Make sure you’re among them by getting our free SSL certificate with Business web hosting plan and don’t worry about your website SEO rankings in any search engine anymore!
It is no secret that a green lock next to your website's address and Https prefix mean a safe website. You know it and your customers know it! According to the latest research, people buy on websites with SSL certificates 10 times more that on websites without it. Gain the trust of your customers by acquiring SSL certificate with Business web hosting and stop losing potential buyers. Make your website reputable!
Your competitor websites already have SSL certificate and yours still doesn't have it? SSL is a must in today's market. Get it for free with our cheap Business web hosting plan and be the leader of today's market. Steal clients from your competition by getting SSL protection now. SSL protected website is the main reason why people choose your website over the one of a competitor’s and else where you can be found.
With our Business cheap web hosting plan, SSL costs nothing but benefits the business hugely. Increase your revenue with FREE SSL security in no time! This is the cheapest way to boost your sales and establish a secure bond between you and your client. No real investment is required if you want to improve your trades when you get our Business web hosting plan.
With time, your brand will become credible if using SSL security. You will have one more advantage against your competitors – a product that people trust. A service that matters to it’s owners is the service that people trust and want to purchase. Improve your websites reputation instantly by getting our free SSL protection with every Business plan.
With SSL Certificate you will be able to put all your efforts into your product. Stop wasting time on law suits and unnecessary cyber incidents with your clients. It is important to put a stop to hackers who unlawfully steal your client’s data and sensitive information by securing your website with SSL encryption when buying cheap Business hosting plan. Focus only on your product.
Free SSL Certificate with Hostinger's Business plan, establishes a secure connection for sensitive data to travel safely with Hostinger’s SSL encryption. Free SSL will let you work safely without breaking your bank. It will even increase your revenue as you will get a higher Google ranking, more unique visitors, and more sales! How does SSL work? Here’s how.


{% extends "base.html" %} {% block title %}{{ Full_Name }}'s Account - ToolShare{% endblock %} {% block content %} {% include "navigation.html" %}
{{ Full_Name }}'s Account
Tools Data


TL;DR: developer. visionary. philomath. A dedicated software developer, hungry to change the way the world works by means of leadership, entrepreneurship, and mentorship. His biggest project is a website, a database for school documents with over 500k views. After winning a hackathon, he was selected to be a finalist at the Next 36, the top entrepreneurship program in Canada. He has successfully advocated for hackathons to become part of curriculum. He hosts weekly code meetups where he helps people start on their own projects or suggests ideas to build. He is motivated by his passion for the environment and was part of a group urging his school to divest from Fossil Fuels.
An engineer at heart, a lover of technology, who still understands when it's not necessary. Tries to solve problems with code, but prefers to use existing programs and code when possible.
Extremely passionate, thirsty for positive change, great for consulting of validity and expansion of ideas. Has a vision for the future of things. A starter of movements.
A lover of learning. Detail-oriented. Amazing at finding existing solutions to problems online. Wide range of practical knowledge, but not a fan of trivia. Frequent DIYer.


Choose a quiz from the list to see the students authentication results.
There are no quizzes associated to this course.


{{ errorText }}
Unfortunately, there was an error while attempting to recover your secret using your social shares.
Please ensure that you have entered the correct number and combination of related social shares when attempting to recover your secret again


Top
menu
Hello! Project
Community
Community
Morning Musume
ANGERME
Juice=Juice
Country Girls
Kobushi Factory
Tsubaki Factory
BEYOOOOONDS
Hello Pro Trainee
Welcome to the Hello! Project Fandom!
A place where all of the information can be easily found for your convenience.
Community
Wikipedia (Hello! Project)
Wikia (Hello! Project)
Hello! Online
Hello! News Service
Morning Musume. '19
Official Page
YouTube
Facebook
Twitter
Instagram
9th Gen Blog
10th/11th Gen Blog
12th Gen Blog
13th/14th Gen Blog
ANGERME
Official Page
YouTube
Facebook
Twitter
Instagram
Wada Ayaka's Blog
2nd Gen Blog
3rd/4th/5th/6th Gen Blog
7th Gen Blog
Juice=Juice
Official Page
YouTube
Facebook
Twitter
Instagram
Blog
Country Girls
Official Page
YouTube
Facebook
Twitter
Instagram
Blog
Kobushi Factory
Official Page
YouTube
Facebook
Twitter
Instagram
Blog
Tsubaki Factory
Official Page
YouTube
Facebook
Twitter
Instagram
Blog
BEYOOOOONDS
Official Page
Twitter
Instagram
CHICA#TETSU Blog
Ame no Mori Kawa Umi Blog
General Blog
Hello Pro Trainee
Official Page (Hello Pro Trainee)
YouTube
Official Page (Hello Pro Trainee in Hokkaido)


Source on Github
Output depends on URL query. Here are some examples:
Complete
Missing genome
Missing UUIDs


Generic Mets/Alto importer¶
A back-bone for any Mets/Alto importer.
Abstract classes¶
-
class
text_importer.importers.mets_alto.classes.
MetsAltoNewPaperIssue
(issue_dir: impresso_commons.path.path_fs.IssueDirectory)¶ Generic class representing a newspaper issue in Mets/Alto format.
Note
New Mets/Alto importers should sub-class this class and implement its abstract methods (i.e.
_find_pages()
,_parse_mets()
).- Parameters
issue_dir (IssueDir) – Description of parameter issue_dir.
-
property
xml
¶ Returns a BeautifulSoup object with Mets XML file of the issue.
Note
By default the issue Mets file is the only file containing mets.xml in its file name and located in the directory self.path. Individual importers can overwrite this behavior if necessary.
-
class
text_importer.importers.mets_alto.classes.
MetsAltoNewspaperPage
(_id: str, n: int, filename: str, basedir: str)¶ Generic class representing a newspaper page in Alto format.
Note
New Mets/Alto importers should sub-classes this class and implement its abstract methods (i.e.
add_issue()
).- Parameters
_id (str) – Canonical page ID.
n (int) – Page number.
filename (str) – Name of the page Alto XML file.
basedir (str) – Base directory where Alto files are located.
-
abstract
add_issue
(issue)¶ Add to a page object its parent, i.e. the newspaper issue.
This allows each page to preserve contextual information coming from the newspaper issue.
- Parameters
issue (NewspaperIssue) – Newspaper issue contaning this page.
-
parse
()¶ Process the page file and transform into canonical format.
Note
This lazy behavior means that the page contents are not processed upon creation of the page object, but only once the
parse()
method is called.
-
property
xml
¶ Returns a BeautifulSoup object with Alto XML of the page.
Mets parsing¶
-
text_importer.importers.mets_alto.mets.
parse_mets_amdsec
(mets_doc, x_res: str, y_res: str, x_res_default=300, y_res_default=300) → Dict¶ - Parameters
mets_doc – BeautifulSoup document of METS.xml
x_res – Field representing the X resolution
y_res – Field representing the Y resolution
x_res_default – Default X_res (300)
y_res_default – Default Y res (300)
- Returns
dict, containing the resolution for each image
Alto parsing¶
Utility functions to parse Alto XML files.
-
text_importer.importers.mets_alto.alto.
distill_coordinates
(element: bs4.element.Tag) → List[int]¶ Extract image coordinates from any XML tag.
Note
This function assumes the following attributes to be present in the input XML element:
HPOS
,VPOS
.WIDTH
,HEIGHT
.- Parameters
element (Tag) – Input XML tag.
- Returns
An ordered list of coordinates (
x
,y
,width
,height
).- Return type
List[int]
-
text_importer.importers.mets_alto.alto.
parse_printspace
(element: bs4.element.Tag, mappings: Dict[str, str]) → List[dict]¶ Parse the
<PrintSpace>
element of an ALTO XML document.- Parameters
element (Tag) – Input XML element (
<PrintSpace>
).mappings (Dict[str,str]) – Description of parameter mappings.
- Returns
Description of returned object.
- Return type
List[dict]


Let's setup the feature-toggle.
That's how it will look like.
This is text from feature1
This is text from feature2


Eric D. Torres
Day Planner
Day Planner
Task List
Task List
Search NY Times
Search NY Times
Password Generator
Password Generator
JS Code Quiz
JS Code Quiz
Responsive Portfolio:
Home Page
About Me
Portfolio
Contact
Loan Calculator
$
%
Output
Monthly Payment
Total Payment
Total Interest


404
Page not found.
We're sorry, but the page you were looking for doesn't exist.
We Are Fixing The Error At This Moment


🔒 {{ c.client.body.name }}, from {{ c.client.body.company }}, can access your data
This application can access the following data:
This data is used for the following reasons:
This application can access the following data:
This data is used for the following reasons:
This application can access some legitimate data for the following reason:
{{ c.base.legitimate.reason }}
This application can access the following data:
This data is used for the following reasons:
Your data:
Your data will be stored for a duration of {{c.legal.storage_duration}}.
Privacy policy - Contact the DPO office
You have the right to access, modify, transfer or delete the data you have collected on them, as per the law.
Request date: {{c.client.date}}


UIColor
class UIColor : NSObject, NSSecureCoding, NSCopying
Extensions for UIColor class.
-
Initialiser color from hex representable.
Declaration
Swift
public convenience init(hex: String)
-
Changing the color by making it more lighter and returns it. Optional parameter, representing by percentage.
Declaration
Swift
public func lighter(by percentage: CGFloat = 0.1) -> UIColor
-
Changing the color by making it more darker and returns it. Optional parameter, representing by percentage.
Declaration
Swift
public func darker(by percentage: CGFloat = 0.1) -> UIColor
-
String hex representable of color.
Declaration
Swift
public var hex: String { get }


Cultural Blog
According the the Grecorc Thinking Style test, I am skewed toward being a 'Concrete Random thinking style'. An experimenter!. I guess on reflection I feel this is pretty accurate.
I'm hoping this will lend itself to the EDA style of learning, as much of the work in the challenges so far involve experimentation. Having said that, I need to make sure I temper the natural desire to experiment with the need to stay on focus with tasks that may not be as much fun but still need to be completed. To achieve this I create daily task-list of achievable task's and tick them off as I go along, which then makes me feel I'm allowed to experiment
This is reinforced with my enjoyment of phase 0 where the challenges introduce content new or otherwise and then encourage playing and experimenting with what what delivered to cement the concepts, at least at a conscious competence level.


GET https://apis.wso2.com/api/am/publisher/v1/mediation-policies
This operation provides you a list of available all global level mediation policies.
apim:api_view
apim:mediation_policy_view
GET https://localhost:9443/api/am/publisher/v1/mediation-policies HTTP 1/1
Authorization: Bearer ae4eae22-3f65-387b-a171-d37eaa366fa8
HTTP 1/1 200 OK
Content-Type: application/json
{
"count" : 2,
"list" : [ {
"name" : "header_sequence1",
"id" : "c34c35c9-cea9-44fc-8b9f-c61ff50f9aa3",
"type" : "IN"
}, {
"name" : "ample_eader_sequence1",
"id" : "7bdcb31c-5381-447e-8daa-e98a31002885",
"type" : "IN"
} ]
}
curl -k -v -X GET 'https://localhost:9443/api/am/publisher/v1/mediation-policies' -H 'Authorization: Bearer ae4eae22-3f65-387b-a171-d37eaa366fa8'
GET https://localhost:9443/api/am/publisher/v1/mediation-policies HTTP/1.1
Authorization: Bearer ae4eae22-3f65-387b-a171-d37eaa366fa8
HTTP/1.1 200 OK
Content-Type: application/json
{
"count":2,
"list":[
{
"name":"header_sequence1",
"id":"c34c35c9-cea9-44fc-8b9f-c61ff50f9aa3",
"type":"IN"
},
{
"name":"ample_eader_sequence1",.MediationPoliciesApiService
"id":"7bdcb31c-5381-447e-8daa-e98a31002885",
"type":"IN"
}
],
"pagination":null
}
curl -k -H "Authorization: Bearer ae4eae22-3f65-387b-a171-d37eaa366fa8" https://localhost:9443/api/am/publisher/v1/mediation-policies
| Type | Name | Description | Schema | Default |
|---|---|---|---|---|
| Query |
limit optional |
Maximum size of resource array to return. |
Integer |
25 |
| Query |
offset optional |
Starting point within the complete list of items qualified. |
Integer |
0 |
| Query |
query optional |
-Not supported yet- |
String | |
| Header |
If-None-Match optional |
Validator for conditional requests; based on the ETag of the formerly retrieved variant of the resource. |
String |
| HTTP Code | Description | Schema |
|---|---|---|
200 |
OK. List of mediation policies is returned. |
MediationList |
304 |
Not Modified. Empty body because the client has already the latest version of the requested resource (Will be supported in future). |
|
406 |
Not Acceptable. The requested media type is not supported |
Error |


{% extends "starlette_admin/base.html" %} {% block header %}{% endblock %} {% block sidebar %}{% endblock %} {% block content %}
Your password has been changed you can now login.


Connect With Liquidreach:
Let's work together for your brand. If you would like to learn more, request a project quote, or simply say hi,
feel free to drop us a line here<EMAIL_ADDRESS>Let's work together for your brand. If you would like to learn more, request a project quote, or simply say hi,
feel free to drop us a line here info@liquidreach.com


if __name__ == "__main__":
limit = int(input("How many terms to include in Lucas series:"))
print("Lucas series:")
for i in range(limit):
print(recur_luc(i))
from doctest import testmod
testmod()
n = int(input("Enter the number of terms in lucas series:\n").strip())
n = int(input("Enter the number of terms in lucas series:\n").strip())
print("Using recursive function to calculate lucas series:")
print(" ".join(str(recursive_lucas_number(i)) for i in range(n)))


Hi, welcome to my page! I am currently a senior at UC Berkeley studying Electrical Engineering and Computer Science. My interests in the field are constantly changing, but right now I am most excited to be learning about machine learning, computational rationality, and the Internet of Things.
Outside of school, I am an avid sports enthusiast; I can probably (and eagerly) engage with you on just about any prominent sports story. When I have free time, I like to discover hidden restaurants and dessert places around Berkeley and San Francisco. In addition, I have recently started studying rudimentary chess strategy, and if you listen to Serial, I would love to discuss the case.
| March Mathness - A Neural Network | A neural net that predicts win probabilities between any two college basketball teams for annual March Madness tournament challenges. The model has one hidden layer, built using PyBrain and data supplied from Kaggle's March Machine Learning Mania 2016 competition. |
|---|---|
| Twitter Sentiment Analyzer | A Naïve Bayesian classifier that collects tweets related to a search query and categorizes each as positive or negative, plotting the results over a 7-day period. |
| Fantasy Basketball Drafter | A fantasy basketball drafter that uses a heuristic algorithm based on teams' offensive & defensive ratings combined with gambling odds to predict individual player production. It then uses an integer linear programming solver to optimize a daily lineup for the popular fantasy sports website DraftKings. |
| Wikipedia Pathfinder | An app that discovers paths between two Wikipedia articles. It uses a best-first search algorithm to prioritize more likely successful articles in its traversal to maximize time efficiency. |
| Spam Filter | A spam-detection script that uses random forests to classify as spam or not. |
| ebertWrites | An twitter bot that generates and tweets random text using a Markov chain. The algorithm uses a large movie movie dataset as a training input to continually append suffixes, eventually forming a hopefully coherent sentence. |
For more of my projects and ongoing work, check out my GitHub.


NBL.js is a tiny script that will make your HTML pages load faster by loading all your JavaScript files asynchronously (in parallel) with the rest of your page. Normally if you include two or three scripts in your page, the browser will wait for them to be executed before your page is shown.
By using NBL.js the browser can start showing the HTML while loading and executing the scripts, resulting in a faster, more responsive website. All in less than 1kb! Check out some examples.
Include NBL.js in your pages and let it dynamically load all your JavaScript files by simply including the following tag:
<script src="nbl.js" data-nbl="[ [ 'http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js', 'jquery.lightbox.min.js', 'jquery.carousel.min.js' ], function(e){ jquery_loaded(e) }, 'http://www.google-analytics.com/urchin.js', function(){ urchin_loaded() } ]"></script>
This will do the following:
jquery_loaded()
function.urchin_loaded()
function.
After NBL.js has done its job you can verify a few things through the global nbl
object. Every
script will be placed in the nbl.q
object, referred to by the filename of the script minus the
".js" or .min.js" extension or any non-word characters.
In the above example "jquery.lightbox.min.js" will become "jquerylightbox". If it has loaded successfully,
nbl.q.jquerylightbox
will return true, otherwise you'll get the script element of the script you queried.
When a script fails to load, NBL will fire the first defined function it encounters after a default timeout of 2500ms.
In the above example that function is jquery_loaded()
. If jQuery loads fine, but one of the plugins doesn't,
the timeout will expire and call jquery_loaded()
once again, only this time it will provide the nbl.q
object as its only argument e
.
That way you can distinguish between a normal call and a timed out call, check out the examples for more information on this feature.
NBL.js is rather flexible in its options, so let's dissect a few examples.
[ 'script1.js', 'script2.js', 'script3.js' ]
This will simply load all three scripts in parallel.
[ [ 'script1.js', 'plugin1.js', 'plugin2.js' ], 'script2.js' ]
This will load script1.js
and script2.js
in parallel. After script1.js
has loaded, plugin1.js
and plugin2.js
will load in parallel.
When NBL.js encounters an array of scripts, it will immediately load the first script (script1.js
in this case) and load the remaining scripts (plugin1.js
and plugin2.js
) after
completion. The plugin1.js
and plugin2.js
scripts have a lower priority than the
script1.js
and script2.js
scripts and will be loaded after script1.js
completes.
[ [ 'script1.js', [ 'script2.js', [ 'script3.js, 'script4.js ] ] ] ]
It's a bit crazy, but nesting the arrays like this will allow you to load all scripts sequentially. After
the first array with script1.js
, NBL.js encounters a second array starting with script2.js
,
which it will load after script1.js
has completed.
After script2.js
completes, NBL.js will continue the iteration with the third array that starts with
script3.js
, finally ending with loading script4.js
after script3.js
has
completed.
[ 'script1.js', function(e){ script1_callback(e) }, 'script2.js', function(){ script2_callback() }, 'script3.js', function(){ script3_callback() } ]
The basic rule of callbacks is: declare the callback function directly after the script.
In this example, the three scripts will load in parallel and upon completion of each script, the
corresponding callback will be called. In case of a timeout, the first defined function
(script1_callback(e)
) will be called with nbl.q
as argument e
(as explained above).
[ [ 'script1.js', 'plugin1.js', function(){ plugin1_callback() } ], function(e){ script1_callback(e) }, 'script2.js', function(){ script2_callback() } ]
Following the basic rule of callbacks as mentioned above, we place the callback function for script1.js
outside the array that contains script1.js
and plugin1.js
, since to NBL.js
script1.js
and script2.js
are on equal footing, the callbacks for both must be placed in the main array.
[ 3200, function(e){ global_timeout(e) }, 'script1.js', function(){ script1_callback() }, 'script2.js', function(){ script2_callback() } ]
First off, by specifying a number anywhere in the options, NBL.js will assume you want to change the timeout from the default 2500ms to the provided number. Second, by putting a function before any scripts, it will define it as the global timeout function.
In this case script1_callback()
and script2_callback()
will be called when script1.js
and script2.js
are finished loading. And in case of an error, global_timeout()
will be called after
approximately 3500ms.
If you prefer you can choose to simply include NBL.js in a single line in your HTML pages. This way you can
save a HTTP-call from the browser, and it will only add 882 bytes to your HTML page. Simply include the code
in nbl.single.js
into a <script>
tag at the end of your page, and replace
['your', 'scripts', 'here']
with your own options.
You can't use the data-nbl
attribute of the script tag if you use this method.
All options are case-sensitive, if you include a file called urCHin.js
, the corresponding
nbl.q
object will be nbl.q.urCHin
. I advise you to simply use lowercase for all options.
If you do not specify any options in the script tag, NBL.js will instantiate the default nbl
object
and will do nothing. You will have to do a manual nbl.l( [ 'your', 'options', 'here' ] )
.
You can find more examples in the included examples.
I hope you find NBL.js useful, thanks for reading this!
Berklee
GitHub user Knowlecules mailed me with modifications to preload CSS and images using NBL.js. I've incorporated that code into @nbl.plus.js@ (and @nbl.plus.min.js@). Thanks to some additional bug squashing by Richard Lopes, the latest version of NBL Plus is now better than ever! Clocking in at 1119 bytes for the minified version and 681 bytes for the gzipped one, there's no reason not to use NBL Plus for your asynchronous media loading needs.
Copyright (c) 2009-2010 Berklee Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Account |
Represents account model in blockchain class Account : GrapheneObject, GrapheneSerializable |
AccountOptions |
Contains user account additional information class AccountOptions : GrapheneSerializable |
Address |
Represents EcDSA address model in blockchain class Address |
Asset |
Class used to represent a specific asset on the Graphene platform class Asset : GrapheneObject, ByteSerializable |
AssetAmount |
Class used to represent a specific amount of a certain asset class AssetAmount : GrapheneSerializable |
AssetOptions |
Contains options available on all assets in the network AssetOptions details class AssetOptions : JsonSerializable, ByteSerializable |
Balance |
Represents balance model in Graphene blockchain data class Balance |
BaseOperation |
Represents base operation model in Graphene blockchain abstract class BaseOperation : ByteSerializable, JsonSerializable |
BitassetOptions |
Options only available for BitAssets https://dev-doc.myecho.app/asset__ops_8hpp_source.html class BitassetOptions : GrapheneSerializable |
Block |
Represents block model in blockchain class Block |
BlockData |
This class encapsulates all block-related information needed in order to build a valid transaction. class BlockData : ByteSerializable |
BtcAddress |
Describes account's botcoin address model data class BtcAddress |
ByteSerializable |
Describes functionality of entities for which it is required to have specific byte-array representation interface ByteSerializable |
CurrentFees |
Describes fees that exist in current blockchain version class CurrentFees |
Deposit |
Echo sidechain base deposit model sealed class Deposit : GrapheneObject |
DepositAddress |
Describes deposit bitcoin address data class DepositAddress |
DepositDeserializer |
Deserializer for Deposit model class DepositDeserializer : JsonDeserializer<Deposit> |
DepositMapper |
Json mapper for Withdraw model class DepositMapper : ObjectMapper<Deposit> |
DynamicGlobalProperties |
Represents account model in Graphene blockchain Dynamic global properties details (https://dev-doc.myecho.app/classgraphene_1_1chain_1_1dynamic__global__property__object.html) class DynamicGlobalProperties : GrapheneObject, Serializable |
EchorandConfig |
Describes all echorand's configs class EchorandConfig |
ERC20Deposit |
Echo erc20 sidechain deposit model class ERC20Deposit : GrapheneObject |
Erc20DepositMapper |
Json mapper for Deposit model class Erc20DepositMapper : ObjectMapper<ERC20Deposit> |
ERC20Token |
Descibes model of ERC20 token in ECHO network class ERC20Token : GrapheneObject, GrapheneSerializable |
Erc20TokenDeserializer |
Json deserializer for ERC20Token class Erc20TokenDeserializer : JsonDeserializer<ERC20Token> |
Erc20TokenMapper |
Json mapper for ERC20Token model class Erc20TokenMapper : ObjectMapper<ERC20Token> |
ERC20Withdrawal |
Echo sidechain withdrawal model class ERC20Withdrawal : GrapheneObject |
Erc20WithdrawalMapper |
Json mapper for ERC20Withdrawal model class Erc20WithdrawalMapper : ObjectMapper<ERC20Withdrawal> |
Error |
Represents error from blockchain response data class Error |
ErrorData |
Represents error data from blockchain response data class ErrorData |
EthAddress |
Describes account'sethereum address model data class EthAddress |
Extensions |
Represents additional payload of models class Extensions : GrapheneSerializable |
FeeParameter |
Blockchain single fee item class FeeParameter |
FeeParameters |
List fo all blockchain fees class FeeParameters |
FullAccount |
Represents full information about user account class FullAccount |
GasPrice |
Describes blockchain gas price class GasPrice |
GlobalProperties |
Contains all global blockchain properties class GlobalProperties |
GrapheneObject |
Represents base graphene object model open class GrapheneObject : ByteSerializable |
GrapheneSerializable |
Represents functionality of entities that fot which it is required to have both json and byte-array representation interface GrapheneSerializable : ByteSerializable, JsonSerializable |
HistoricalTransfer |
Represents account history History object details data class HistoricalTransfer |
HistoryResponse |
This class encapsulates batch of history data class HistoryResponse |
HistoryResult |
Represents account model in Graphene blockchain class HistoryResult |
JsonDeserializable |
Describes functionality of entities for which it is required to have specific representation from json string interface JsonDeserializable<T> : Serializable |
JsonSerializable |
Describes functionality of entities for which it is required to have specific json string representation interface JsonSerializable : Serializable |
Method |
Describes sidechain method informationstructure class Method |
ObjectType |
Enum type used to list all possible object types in Graphene blockchain enum class ObjectType |
Optional |
Container template class used whenever we have an optional field. class Optional<T : GrapheneSerializable> : GrapheneSerializable |
Parameters |
Blockchain global properties parameters list class Parameters |
PrevSignature |
Describes previous signature model class PrevSignature |
Price |
The price struct stores asset prices in the Graphene system. class Price : JsonSerializable, ByteSerializable |
PublicKey |
Encapsulates logic of working with account key/address by EcDSA algorithm class PublicKey : Serializable, ByteSerializable |
RegistrationResult |
Represents result of account registration. Example: {block_num:114642,tx_id:30b2716a2f563b2cfe29442f410681bdae8b6347} class RegistrationResult |
RegistrationTask |
Describes task required to solv for account registration data class RegistrationTask |
SidechainConfig |
Describes all sidechain's configs class SidechainConfig |
SidechainType |
Contains possible sidechain types enum class SidechainType |
SocketResponse |
Represents response from blockchain open class SocketResponse |
SocketResponseResult |
Represents typed response with result from blockchain class SocketResponseResult<T> : SocketResponse |
Transaction |
Class used to represent a generic Graphene transaction. Transaction details class Transaction : ByteSerializable, JsonSerializable |
TransactionOperationsResult |
Represents Graphene object with operation results of broadcasted transaction data class TransactionOperationsResult |
TransactionResult |
Represents Graphene notice object for broadcasted transaction data class TransactionResult |
Vote |
Represents vote model in graphene blockchain class Vote : ByteSerializable |
Withdraw |
Echo sidechain base withdraw model sealed class Withdraw : GrapheneObject |
WithdrawDeserializer |
Deserializer for Deposit model class WithdrawDeserializer : JsonDeserializer<Withdraw> |
WithdrawMapper |
Json mapper for Withdraw model class WithdrawMapper : ObjectMapper<Withdraw> |
isEqualsByKey |
Check account equals by key from role authorityType fun Account.isEqualsByKey(key: String): Boolean |


Defines out-of-box classes for usage with COM servers supporting automation. Please see http://msdn.microsoft.com/en-us/library/aa912424.aspx
for more details on how to use COM Automation.
Disclaimer and copyright notice: Parts of documentation in this package has been referenced as it is from MSDN online help and is Microsoft(c) copyrighted.


Please see GitHub issue #1913 for more information.
If you have a model running on CPU, GPU, or Google Cloud TPU, you may be able to use the above button to capture a profile.
If you're a CPU or GPU user, please use the IP address option. You may want to check out the tutorial on how to start a TensorFlow profiler server and profile a Keras model on a GPU.
If you're a TPU user, please use the TPU name option and you may want to check out the tutorial on how to interpreting the profiling results.
If you think profiling is done properly, please see the page of Google Cloud TPU Troubleshooting and FAQ and consider filing an issue on GitHub.


Speed
Pause
GO
STOP
JOIN
Repeat
Controlled
Calculate
Total Length: {{tl | number:0}} (m) Total Time: {{tt | number:0}} (sec)


Table of Contents
- Lab Introduction
- Section 1 - Lab Setup
- Section 2 - Python Programming
- Section 3 - Install Python Oracle module and connect
- Section 4 - Querying the Oracle database
Lab Introduction
This lab guide shows how to program a very simple Python script, connect to a database and retrieve information from the database.
Lab Assumptions
- Each participant has been provided a username and password to the tenancy c4u03
- Each participant has completed the Environment Setup lab.
Section 1 - Lab Setup
Python comes preinstalled on most Linux distributions, and it is available as a package on others. The Python packages can be obtained from the software repository of your Linux distribution using the package manager. There are two Python versions available, 2.X and 3.X, the VM used for this lab comes preinstalled with Python 2.7 but since this version will reach the end of support on January 1st, 2020, we will use Python3 for this excercise.
-
Open up a terminal and ssh into your compute instance as the opc user
ssh -i optionskey opc@<your ip address>
-
Check if python3 has been installed by running the command
sudo yum -y install python3 python3-tools
The system will either install packages or let you know they are already installed.
Section 2 - Python Programming
There are several ways to execute Python code. In this section we start with two examples on how to execute Python code from the command line. The first example executing code from the command prompt i.e. executing commands directly in the interpreter. The second example to save your code in a .py file and invoke the interpreter to execute the file.
-
To execute code from command line open the Python command line editor and type the following commands, one by one (each line is one command):
$ python3 >>> var1 = "hello world" >>> var1 'hello world'
-
To create a simple script, open up a text editor (like vi) and enter the following script.
var1 = "hello world" print(var1)
Save the file as test.py in the /home/oracle directory.
$ python3 /home/oracle/test.py hello world
Section 3 - Install Python Oracle module and connect
cx_Oracle is a python module that enables access to Oracle databases. This module is supported by Oracle 11.2 and higher and works for both Python 2.X and 3.X. There are various ways in which cx_Oracle can be installed. In this example we will use pip (installed by default for python 3.4 and up). For more ways to install cx_Oracle (like yum) check the documentation on https://yum.oracle.com/oracle-linux-python.html#Aboutcx_Oracle.
-
Become the Oracle user
Since our client libraries are installed in our VM under the oracle user, we will now ‘sudo’ into the oracle user. (If you have an environment that does not have client libraries accessible to the user running the python3 script, install the Oracle instant client as described in the documentation)
sudo su - oracle
-
Install cx_Oracle using pip
Install the module using python3 and pip for the oracle user:
python3 -m pip install --user cx_Oracle
-
Test your install by launching the python console and list the available modules
$. oraenv ORACLE_SID = [ORCL] ? ORCL The Oracle base remains unchanged with value /u01/app/oracle $ python3 >>> help('modules')
This command will show you a list of installed modules which should include the cx_Oracle module we installed in the previous step.
-
Connect to the Oracle database and print the version of the database via python.
(This confirms you are connected to an Oracle instance and returns the database version)>>> import cx_Oracle >>> con = cx_Oracle.connect('system/Ora_DB4U@localhost:1521/orclpdb') >>> print(con.version) <IP_ADDRESS>.0 (example output) >>> quit()
Section 4 - Querying the Oracle database
Retrieving records from Oracle database using cursors is a simple as embedding the SQL statement within the cursor().execute statement. For this example we will use an existing table that was imported for the In-Memory lab.
-
Create a script called /home/oracle/db_connect.py witht he following contents:
import cx_Oracle con = cx_Oracle.connect('ssb/Ora_DB4U@localhost:1521/orclpdb') cur = con.cursor() cur.execute('select c_name,c_address,c_city from customer where rownum < 100') for row in cur: print (row) cur.close() con.close()
-
Execute the script and check the result:
python3 /home/oracle/db_connect.py
The result should be a list of customers.
Congratulations! You’ve created a basic python application connecting to the oracle database.


My name is John paul, a member of Independent Committee of Eminent Persons (ICEP), Switzerland. ICEP is charged with the responsibility of finding bank accounts in Switzerland belonging to non-Swiss indigenes, which have remained dormant since World War II. It may interest you to know that in July of 1997, the Swiss Banker's Association published a list of dormant accounts originally opened by non-Swiss citizens. These accounts had been dormant since the end of World War II (May 9, 1945). Most belonged to Holocaust victims. The continuing efforts of the Independent Committee of Eminent Persons (ICEP) have since resulted in the discovery of additional dormant accounts - 54,000 in December, 1999. The published lists contain all types of dormant accounts, including interest-bearing savings accounts, securities accounts, safe deposit boxes, custody accounts, and non-interest-bearing transaction accounts. Numbered accounts are also included. Interest is paid on accounts that were interest bearing when established. The Claims Resolution Tribunal (CRT) handles processing of all claims on accounts due non-Swiss citizens. A dormant account of ORDNER ADELE with a credit balance of 35,000,000 US dollar plus accumulated interest was discovered by me. The beneficiary was murdered during the holocaust era, leaving no WILL and no possible records for trace of heirs. The Claims Resolution Tribunal has been mandated to report all unclaimed funds for permanent closure of accounts and transfer of existing credit balance into the treasury of Switzerland government as provided by the law for management of assets of deceased beneficiaries who died interstate (living no wills). Being a top executive at ICEP, I have all secret details and necessary contacts for claim of the funds without any hitch. The funds will be banked in the Cayman Island, being a tax free, safe haven for funds and we can share the funds and use in investment of our choice. Due to the sensitive nature of my job, I need a foreigner to HELP claim the funds. All that is required is for you to provide me with your details for processing of the necessary legal and administrative claim documents for transfer of the funds to you. Kindly provide me with your full name, address, and telephone/fax. I will pay all required fees to ensure that the fund is transferred to a secure, numbered account in your name in the Cayman Island, of which you will be capable of accessing the funds gradually and transferring to your country and other banks of choice in the world. My share will be 60 percent and your share is 40 per cent of the total amount. THERE IS NO RISK INVOLVED. You can find additional information about unclaimed funds through the internet at the following websites: www.swissbankclaims.com http://www.cnn.com/WORLD/europe/9902/09/germany.holocaust/ www.avotaynu.com www.icheic.org www.livingheirs.com www.wiesenthal.com The Holocaust Claims Processing Office has put funds in Escrow awaiting submission of valid claims for necessary disbursement. I find myself priviledged to have this information and this may be a great opportunity for a life time of success without risks. Due to security reasons, reply to my via email only. You may reply to me securely on the following email<EMAIL_ADDRESS>Thank you for your prompt response. John


{% extends "views/base.html" %} {% block breadcrumb %}
{% if id - 1 > 0 %} ← Prev {% endif %} Next →
Received on {{ mail.date }}
Attachments : {{ mail.attachments|length }}


0
Use
Add a balloon
Start the travel
Store the balloons
Add saved balloons
Send all to a blackhole
The Hot Air Balloon Station


THE UNTOUCHABLES A film review by Mark R. Leeper Copyright 1987 Mark R. Leeper
Capsule review: Big mythic cops-and-robbers film is long on excitement, short on accuracy, brash and colorful. It is solid entertainment with a lot of fun in the first half and a second half nearly as good. One of the big films of the summer.
There are lots of ways to make a gangster film. You can make it as realistic as THE GODFATHER or as romanticized as A POCKET FULL OF MIRACLES. You can do a BONNIE AND CLYDE where the crooks are giants and the cops are midgets, or you can make the crooks vermin and the cops squeaky-clean personifications of purity and virtue as was done in THE FBI STORY and the TV show THE UNTOUCHABLES. Brian DePalma did one gangster already with tiny cops and giant hoods, his violent but engrossing remake of SCARFACE. He has returned to the gangster film with a movie based on the UNTOUCHABLES TV series and the book by Elliot Ness and Oscar Fraley that the TV series was based on. His approach is romanticized to the point of being mythic. The hoods are big and the cops are giants. Even a mousy accountant for the Treasury Department who is impressed into service turns out to be a giant. And a film adaptation of a TV show surprisingly turns out to be giant too.
The story should come as no surprise to anyone. An ambitious Treasury agent,Elliot Ness (played by Kevin Costner), comes to Chicago to bring down an oily Al Capone (played by Robert DeNiro). When he realizes he is still wet behind the ears, he calls for the assistance of one good Irish cop (played by Sean Connery) and, with the help of a few friends, they set about hewing down the biggest tree in the underworld jungle. When the film works best, mostly in the first half of the film, it is a positive joy. Toward the second half, I started to realize what I was enjoying is a story about the groovy side of the Secret Police and that Connery's honest and pure philosophy of law enforcement was actually a pretty scary thing.
But David Mamet's screenplay captures the fun of the TV series. When Ness drives a huge snowplow through warehouse doors to smash up shipments of illegal booze, you know you're watching the real thing eight times bigger than life. Though, admittedly, the film's most exciting sequence harks back more to Westerns than to gangster films. And the whole package is done to a score by Ennio Morricone, sometimes tense, sometimes flamboyant, sometimes arrogant.
Now, as for the film's accuracy, yes, there really was an Elliot Ness and he was a Treasury agent. There really was an Al Capone and a Frank Nitti and they were crooks. And Al Capone really was indicted for income tax evasion. Of course, most people knew all that already, and Mamet and DePalma are counting on most people knowing no more than that, because just about everything else is wrong. Ness's accomplishments were exaggerated by newspaper accounts of the day and much more so by his autobiography and by the TV show. Nobody has ever portrayed Frank Nitti accurately in anything. Nitti was one of Capone's lieutenants whom the newspapers thought ran Capone's gang when Capone went to jail. That squares with neither the TV nor the film version. Capone's representation is neither accurate nor inaccurate. We just don't see much of his strategy in the film.
But with all its faults, THE UNTOUCHABLES is a big film, an exciting film, and it will likely be the big film of the summer. Rate it a +2 on the -4 to +4 scale.
Mark R. Leeper ihnp4!mtgzz!leeper<EMAIL_ADDRESS>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


Syrian troops begin deploying along border with Turkey
by By Press AssociationSyrian government forces have started deploying in areas close to the Turkish border in the north-east of the country, state media has reported.
The troops are deploying between the towns of Jawadiyeh and Malkiyeh, also known as Derik, according to news agency Sana.
The deployment is part of a deal reached between Russia and Turkey last month along much of the north-eastern border that seeks to ensure Kurdish fighters leave the area.
Since the agreement was reached, Russia and Turkey began joint patrols along a narrower strip directly on the Turkish-Syrian border.
Turkey began a major military offensive against Kurdish fighters in northern Syria last month, capturing dozens of towns and villages.


{{- /* Comments area start */ -}} {{- /* to add comments read => https://gohugo.io/content-management/comments/ */ -}} {{- /* Comments area end */ -}}


II NORDSTRÖM & THULIN AND THE STOCKHOLM-TALLINN SERVICE
CHAPTER 5
THE HISTORICAL DEVELOPMENT
Nordström & Thulin AB is a Stockholm-based public company, established in 1850, with extensive experience in the worldwide operation of large modern tankers and bulk carriers. Also passenger ferry operations between the Swedish mainland and the island of Gotland in the Baltic Sea belonged to the business and shipbroking is another important company activity.
In the light of the changes in the Soviet Union in 1988 the Board of Nordström & Thulin (N&T) decided to investigate the possibilities for a car/ passenger service between Stockholm and Tallinn and in early spring 1989 Hans Laidwa, a born Estonian, took up his work.
Laidwa's business was to investigate the possibilities of opening a ferry traffic between Stockholm and Tallinn. N&T's plans had a positive response in Stockholm and Tallinn, but the decisions - as far as Estonia was concerned - at that time were still being made in Moscow. The Soviet authorities would among other things have to tolerate that passengers on short cruises to Tallinn would not need visas, which was finally accepted.
N&T received the exclusive right for the passenger traffic between Tallinn and Stockholm from the Estonian side for a guaranteed period of 10 years. This was necessary for the long-term planning of investments, because N&T had to take care of all investments in vessels, in terminals and project preparations and also to conduct the ferry line with own personnel.
For the new activities N&T formed the company N&T Estline AB, and appointed Hans Laidwa its managing director. The Danish passenger ferry MV DANA REGINA, which for many years had been employed in the traffic between Copenhagen and Oslo, was purchased, renamed NORD ESTONIA and put under Swedish flag. The ferry left Stockholm on 16 June 1990 on her historical first tour and a very euphoric summer was commenced. The picture of the city of Tallinn was changing and many of the Soviet restrictions were breaking down through the influence of the numerous tourists visiting the city. The first song festival after 50 years took place without approval from Moscow and it was the first time in 50 years that people from all over Estonia could meet friends and relatives from other parts of the country.
After the summer of 1990 a difficult time began, and with the darkness and cold of winter came harder political signals which culminated in the bloody events in Vilnius and Riga in January 1991 and also the Estonians were prepared to build barricades and to fight for their independence.
To this dark picture also contributed the murder of two Swedish union leaders in Tallinn. MV NORD ESTONIA was more or less sailing empty during the winter and spring of 1991, a situation which only gradually changed in the less than 2 years that the NORD ESTONIA would remain in this service.
5.1
Company Structure and ActivitiesN&T is one of the oldest shipping companies in Sweden and is noted on the Stockholm Exchange. The office is located at Skeppsbron in the old City of Stockholm, where ca. 50 people were working.
The main activities in1994 were
Shipping
Sales & Purchase
Broking and Charteringwith the main activities being concentrated on broking and sales & purchases.
The management in 1994 consisted of
| Ronald Bergmann, | the senior manager and simultaneously majority shareholder |
| Anders Berg, | the number 2 |
| Sten-Christer Forsberg, | the technician within the management and director of the Shipping Department |
| Lennart Ökvist, | Finance |
Details can be taken from the company structure attached as Enclosure 5.1.107.
5.2
The Relevant Staff and AB HornetThe Director of the Shipping Department - Rederi Afdeling - was, and still is, Sten-Christer Forsberg, born in 1945. His CV is attached as Enclosure 5.2.108.
He was practically the Fleet Manager directly responsible to the Managing Director Ronald Bergmann. Forsberg had worked together with Börje Stenström ( 2/1997), then the head of the Technical Group of the JAIC, and Kaj Janérus, then the General Director of Sjöfartsverket, some years ago for the Salén Group.
In relation to the NORD ESTONIA and the ESTONIA the next one in the line of responsibility was Ulf Hobro, born in 1948 (CV see Enclosure 5.2.109), employed by N&T as marine superintendent since mid 1990, i.e. after the NORD ESTONIA had taken up her service to Tallinn. Hobro had been employed as safety inspector with Sjöfartsverket before he had joined this organisation after having sailed as 1st engineer and chief engineer with Rederi AB Gotland on the large car/passenger ferriesGotland - 1973-1978
Gute - 1978-1979
Visby - 1980-1987trading between Visby on Gotland and Nynåshamn south of Stockholm.
On 12 November 1973 - when Hobro was sailing as 1st engineer on the GOTLAND for the same owners and in the same trade - the VISBY suffered serious failure of the locking devices of her bow door on way from Nynåshamn to Visby and returned to Nynåshamn due to water on the car deck.
Rederi AB Gotland was taken over by N&T in 1988 and Hans Laidwa, who later built up the Stockholm-Tallinn service, became managing director. Several years ago the VISBY was sold to the Larvik Line and has been sailing ever since between Larvik and Frederikshamn as the PETER WESSEL.
When the name DANA REGINA was changed to NORD ESTONIA and the flag from Danish to Swedish, Ulf Hobro was still employed with Sjöfartsverket and was the responsible safety inspector controlling all the many new requirements following the change from Danish to Swedish flag.Note:
Although also DANA REGINA respectively NORD ESTONIA had no upper extension of the collision bulkhead above bulkhead deck at the location required by SOLAS and, although, she proceeded more than 20 nm off the nearest land in the course of her route between Stockholm and Tallinn, Sjöfartsverket issued and annually renewed an unrestricted PSSC, thereby confirming that she did comply with SOLAS 1974, the same as B.V. had done for the ESTONIA on behalf of the Estonian National Maritime Board (E.N.M.B.).
S.-C.Forsberg explained his organisation in a letter to the criminal police Stockholm dated 01.11.1994 as follows:
»Internal Organisation
The shipping department deals with the following functions:
- operation
- seagoing personnel
- technical inspection
- insurance.In the shipping department we also deal with such external management contracts as the one which referred to the ESTONIA. We also have similar contracts with OK Petroleum and Neste Oy. Ulf Hobro, technical superintendent, and Lennart Klevberg, in charge of the purchase of spare parts, are employed with the shipping department Operation & Technique. The shipping department of N&T has also engaged personnel from the independent entity Rederi AB Hornet, e.g. for technical follow-up work on board. This situation is not unusual. In the shipping business it is more the rule than the exception that part of owners' employees are engaged from ship management companies. The idea is that certain entities become specialised with vast experience and knowledge and take over the activities which otherwise the shipping company employees themselves would have carried out.«
The full wording of the letter together with a translation is attached as Enclosure 5.2.110.
This was the situation within N&T when in the early summer of 1992 the decision was made to replace the Swedish flag/Swedish crew NORD ESTONIA by a larger but cheaper ferry. Some time later the WASA KING was picked out to be the successor, however, under Estonian flag with Estonian crew.


This domain is used by our
web analytics system to collect statistical data
I want to know more! Visit voluum.com to learn more about the system.
I want to report an abuse :( If you believe that one of our customers has been using Voluum for malicious purposes, please contact us at<EMAIL_ADDRESS>Please include a sample URL, this will allow us to identify the account responsible.