Turkey's Erdogan says U.S. still holding patrols with Kurdish YPG in Syria
ISTANBUL (Reuters) - Turkish President Tayyip Erdogan said on Tuesday that U.S. forces were still conducting joint patrols with the Kurdish YPG militia in Syria in a border region that Ankara and Washington had agreed to clear of the militant group.
Erdogan also told reporters in parliament that he would decide whether to meet President Donald Trump in Washington as planned this month after holding a phone call with him.


Fall Trimester
Planning block
Advanced Algebra
Software
Advanced Algebra
Planning block
Planning block
Planning block


Police outline security measures for JLP annual conference Sunday
The police are advising persons who will be attending the Jamaica Labour Party’s (JLP) Annual Conference at the National Arena on Sunday that no offensive weapons will be allowed inside the venue.
Long umbrellas, glass bottles or any other items that can be used to cause serious harm or injury have also been restricted.
All persons entering the venue will be subjected to a search.
The police are further advising that no vending will be allowed outside of the designated areas and that no provision will be made for the storage of prohibited or restricted items at the venue.
Warning to motorists
Motorists are reminded that all provisions of the Road Traffic Act will be strictly enforced. In particular, drivers are warned not to allow passengers to hang from the doors of motor buses, sit on top of motor vehicles, or have any part of the body protruding from the motor vehicles. This is a dangerous practice, which has resulted in the loss of lives in previous years. Drivers are to ensure that they obey the speed limit and desist from dangerous and careless driving on the nation’s roads.
Traffic changes
Traffic changes will be implemented beginning at 8:00 a.m. on Sunday, November 24 to facilitate the smooth staging of the event.
They are:
BEFORE THE EVENT
At 8:00 a.m., Arthur Wint Drive will be one way easterly towards the National Stadium. Motorists travelling from this direction will turn left onto Roosevelt Avenue, right on to Stanton Terrace, right on Mountain View Avenue, right on to Arthur Wint Drive and into the car park.
Only vehicles with VIP passes will be allowed to enter Roosevelt Avenue towards the National Stadium.
Only persons attending the event will be allowed to enter Arthur Wint Drive from Mountain View Avenue.
There will be no through way along Arthur Wint Drive between gates E4 to the Bob Marley Statue at the intersection of Roosevelt Avenue. The area will be sterile and available only to pedestrian traffic.
Residents from Stadium Gardens will be able to leave and enter the community by using Arthur Wint Drive as a one way easterly only.
Parking
VIPs will enter through gate E1, E10 and Indoor Access and park in that general area. Regular attendees will park in the general parking area, which will be accessed via gates E4- E8 and the KSAC Car Park across from the Stadium Car Park.
No parking will be allowed on the following roads:
Roosevelt Avenue
Arthur Wint Drive
Latham Avenue
Stanton Terrace
Mountain View Avenue
Vehicles found in contravention will be towed. Motorists will be asked to position their vehicles facing the directions where the traffic will flow after the event to assist with traffic flow after the event.
AFTER THE EVENT
Arthur Wint Drive will be one way westerly from gate E4 towards Tom Redcam Avenue.
Roosevelt Avenue will be one way northerly towards Stanton Terrace.
Arthur Wint Drive from E5 will be one way easterly towards Mountain View Avenue.
Latham Avenue will be one way north-westerly towards Old Hope Road.
Motorists travelling on North and Central Avenue towards Arthur Wint Drive will only be allowed to turn right on to Arthur Wint Drive.
For about 45 minutes after the event, residents of Stadium Gardens will be able to exit the community by turning left on to Arthur Wint Drive but will not be able to enter or re-enter the community.


This is some text in the div.
This is a paragraph in the div.
This is another paragraph in the div.
Empty the div element


Toggle navigation
butterfly paws
Home
(current)
About
Contact
Sign Up
Log In
butterfly paws
find your forever friend
get started


Receives the next message from the mailbox of the current actor
self
Receives the next message from the mailbox of the current actor
self
.
This is a factory method for creating actors
This is a factory method for creating actors.
The following example demonstrates its usage:
import scala.actors.Actor._ ... val a = actor { ... }
the code block to be executed by the newly created actor
the newly created actor. Note that it is automatically started.
Removes any reference to an Actor
instance
currently stored in thread-local storage
Removes any reference to an Actor
instance
currently stored in thread-local storage.
This allows to release references from threads that are potentially long-running or being re-used (e.g. inside a thread pool). Permanent references in thread-local storage are a potential memory leak.
This method is used to compare the receiver object (this
)
with the argument object (arg0
) for equivalence
This method is used to compare the receiver object (this
)
with the argument object (arg0
) for equivalence.
The default implementations of this method is an equivalence relation:
x
of type Any
,
x.equals(x)
should return true
.x
and y
of type
Any
, x.equals(y)
should return true
if and only
if y.equals(x)
returns true
.x
, y
, and z
of type AnyRef
if x.equals(y)
returns true
and
y.equals(z)
returns
true
, then x.equals(z)
should return true
.
If you override this method, you should verify that
your implementation remains an equivalence relation.
Additionally, when overriding this method it is often necessary to
override hashCode
to ensure that objects that are
"equal" (o1.equals(o2)
returns true
)
hash to the same Int
(o1.hashCode.equals(o2.hashCode)
).
the object to compare against this object for equality.
true
if the receiver object is equivalent to the argument; false
otherwise.
Terminates execution of self
with the following
effect on linked actors:
Terminates execution of self
with the following
effect on linked actors:
For each linked actor a
with
trapExit
set to true
, send message
Exit(self, 'normal)
to a
.
Terminates execution of self
with the following
effect on linked actors:
Terminates execution of self
with the following
effect on linked actors:
For each linked actor a
with
trapExit
set to true
, send message
Exit(self, reason)
to a
.
For each linked actor a
with
trapExit
set to false
(default),
call a.exit(reason)
if
reason != 'normal
.
Returns a hash code value for the object
Returns a hash code value for the object.
The default hashing algorithm is platform dependent.
Note that it is allowed for two objects to have identical hash
codes (o1.hashCode.equals(o2.hashCode)
) yet not be
equal (o1.equals(o2)
returns false
). A
degenerate implementation could always return 0
.
However, it is required that if two objects are equal
(o1.equals(o2)
returns true
) that they
have identical hash codes
(o1.hashCode.equals(o2.hashCode)
). Therefore, when
overriding this method, be sure to verify that the behavior is
consistent with the equals
method.
Links self
to the actor defined by body
Links self
to the actor defined by body
.
the body of the actor to link to
the parameter actor
Links self
to actor to
Links self
to actor to
.
the actor to link to
the parameter actor
Causes self
to repeatedly execute
body
Causes self
to repeatedly execute
body
.
the code block to be executed
Causes self
to repeatedly execute
body
while the condition
cond
is true
Causes self
to repeatedly execute
body
while the condition
cond
is true
.
the condition to test
the code block to be executed
Returns the number of messages in self
's mailbox
Returns the number of messages in self
's mailbox
Lightweight variant of receive
Lightweight variant of receive
.
Actions in f
have to contain the rest of the
computation of self
, as this method will never
return.
a partial function specifying patterns and actions
this function never returns
Lightweight variant of receiveWithin
Lightweight variant of receiveWithin
.
Actions in f
have to contain the rest of the
computation of self
, as this method will never
return.
the time span before timeout
a partial function specifying patterns and actions
this function never returns
This is a factory method for creating actors whose
body is defined using a Responder
This is a factory method for creating actors whose
body is defined using a Responder
.
The following example demonstrates its usage:
import scala.actors.Actor._ import Responder.exec ... val a = reactor { for { res <- b !! MyRequest; if exec(println("result: "+res)) } yield {} }
the Responder
to be executed by the newly created actor
the newly created actor. Note that it is automatically started.
Receives a message from the mailbox of
self
Receives a message from the mailbox of
self
. Blocks if no message matching any of the
cases of f
can be received.
a partial function specifying patterns and actions
the result of processing the received message
Receives a message from the mailbox of
self
Receives a message from the mailbox of
self
. Blocks at most msec
milliseconds if no message matching any of the cases of
f
can be received. If no message could be
received the TIMEOUT
action is executed if
specified.
the time span before timeout
a partial function specifying patterns and actions
the result of processing the received message
Send ()
to the actor waiting in a call to
!?
Send ()
to the actor waiting in a call to
!?
.
Send msg
to the actor waiting in a call to
!?
Send msg
to the actor waiting in a call to
!?
.
Resets an actor proxy associated with the current thread
Resets an actor proxy associated with the current thread.
It replaces the implicit ActorProxy
instance
of the current thread (if any) with a new instance.
This permits to re-use the current thread as an actor
even if its ActorProxy
has died for some reason.
Converts a synchronous event-based operation into
an asynchronous Responder
Converts a synchronous event-based operation into
an asynchronous Responder
.
The following example demonstrates its usage:
val adder = reactor { for { _ <- respondOn(react) { case Add(a, b) => reply(a+b) } } yield {} }
Returns the currently executing actor
Returns the currently executing actor. Should be used instead
of this
in all blocks of code executed by
actors.
Returns the actor which sent the last received message
Returns the actor which sent the last received message.
Returns a string representation of the object
Returns a string representation of the object.
The default representation is platform dependent.
Unlinks self
from actor from
Unlinks self
from actor from
.
the actor to unlink from
The
Actor
object provides functions for the definition of actors, as well as actor operations, such asreceive
,react
,reply
, etc.


Welcome to TwitOff!
Add User
{% for user in users %} {{ user.name }} {% endfor %}
Mouse Over Me
An API that takes two Twitter users and
compares which is more probable to have that 'Tweet'... Cool, Right?! ✊ 😍 😄 🤟 💗


Using AngularJS
Project Structure
The JHipster client code can be found under src/main/webapp
, and follows closely the John Papa AngularJS 1 style guide. Please read this guide first if you have any question on our application structure, file names, JavaScript conventions…
This style guide is endorsed by the AngularJS team, and gives the guarantee to have a clear upgrade path to AngularJS 2.
For AngularJS routes we follow a dash cased naming convention so that the URLs are clean and consistent.
When you generate an entity the route names, route URLs and REST API endpoint URLs are generated according to this convention, also entity names are automatically pluralized where required.
Here is the main project structure:
webapp
├── app - Your application
│ ├── account - User account management UI
│ ├── admin - Administration UI
│ ├── blocks - Common building blocks like configuration and interceptors
│ ├── components - Common components like alerting and form validation
│ ├── entities - Generated entities (more information below)
│ ├── home - Home page
│ ├── layouts - Common page layouts like navigation bar and error pages
│ ├── services - Common services like authentication and user management
│ ├── app.constants.js - Application constants
│ ├── app.module.js - Application modules configuration
│ ├── app.state.js - Main application router
├── bower_components - Dependencies installed by Bower
├── content - Static content
│ ├── images - Images
│ ├── styles - CSS stylesheets
│ ├── fonts - Font files will be copied here
├── i18n - Translation files
├── scss - Sass style sheet files will be here if you choose the option
├── swagger-ui - Swagger UI front-end
├── 404.html - 404 page
├── favicon.ico - Fav icon
├── index.html - Index page
├── robots.txt - Configuration for bots and Web crawlers
Using the entity sub-generator to create a new entity called Foo
generates the following front-end files under src/main/webapp
:
webapp
├── app
│ ├── entities
│ ├── foo - CRUD front-end for the Foo entity
│ ├── foo.controller.js - Controller for the list page
│ ├── foo.service.js - Service which access the Foo REST resource
│ ├── foo.state.js - AngularUI router, which manages routes for this entity
│ ├── foo-delete-dialog.controller.js - Controller for the delete dialog pop-up
│ ├── foo-delete-dialog.html - View for the delete dialog pop-up
│ ├── foo-detail.controller.js - Controller for the entity details page
│ ├── foo-detail.html - View for the entity details page
│ ├── foo-dialog.controller.js - Controller for the create/update dialog pop-up
│ ├── foo-dialog.html - View for the create/update dialog pop-up
│ ├── foos.html - View for the list page
├── i18n - Translation files
│ ├── en - English translations
│ │ ├── foo.json - English translation of Foo name, fields, ...
│ ├── fr - French translations
│ │ ├── foo.json - French translation of Foo name, fields, ...
Please note that the default language translations would be based on what you have choosen during app generation. ‘en’ and ‘fr’ are shown here only for demonstration.
Authorizations
JHipster uses angular-ui-router to organize the different parts of your client application.
For each state, the required authorities are listed in the state’s data, and when the authority list is empty it means that the state can be accessed anonymously.
The authority names are defined in server’s class AuthoritiesConstants.java
.
In the example below, the ‘sessions’ state can be accessed only by authenticated users who have ROLE_USER
authority:
(function() {
'use strict';
angular
.module('tmpApp')
.config(stateConfig);
stateConfig.$inject = ['$stateProvider'];
function stateConfig($stateProvider) {
$stateProvider.state('sessions', {
parent: 'account',
url: '/sessions',
data: {
authorities: ['ROLE_USER'],
pageTitle: 'global.menu.account.sessions'
},
views: {
'content@': {
templateUrl: 'app/account/sessions/sessions.html',
controller: 'SessionsController',
controllerAs: 'vm'
}
},
resolve: {
translatePartialLoader: ['$translate', '$translatePartialLoader', function ($translate, $translatePartialLoader) {
$translatePartialLoader.addPart('sessions');
return $translate.refresh();
}]
}
});
}
})();
Notification System
JHipster uses ui-bootstrap alerts for the notification system, and has an i18n-capable AlertService
which can be used throughout the generated applications.
By default JHipster will show success notifications whenever an entity is created/updated/deleted and error notifications when there is an error caught from the response.
To show a custom notification or alert, use the below methods after injecting the AlertService
to your controller, directive or service.
The shorthand methods success
, info
, warning
and error
will have a timeout of 5 seconds, for other configurations use the add
method:
(function() {
'use strict';
angular
.module('tmpApp')
.controller('FooController', FooController);
FooController.$inject = ['$scope', '$state', 'Foo', 'AlertService'];
function FooController ($scope, $state, Foo, AlertService) {
AlertService.success("This is a success message, it is green");
AlertService.info("This is an info message, it is blue");
AlertService.warning("This is a warning message, it is amber");
AlertService.error("This is an error message, it is red");
AlertService.success("i.will.be.translated");
// where key i.will.be.translated needs to be in global.json
AlertService.success("i.will.be.translated", {param: someParam});
// where key i.will.be.translated needs to be in global.json and can have a { param } which will be replaced by `someParam`
AlertService.add({
type: "success", // can be success, info, warning and error
msg: msg,
params: params, // parameters to pass for translation
timeout: timeout // how long to show the alert in milliseconds
});
AlertService.clear(); // clear all alerts
AlertService.get(); // get all open alerts
}
})();
If you would like the notifications to look like toasts you can enable that by setting AlertServiceProvider.showAsToast(true)
in src/main/webapp/app/blocks/config/alert.config.js
. By default this will be set to false AlertServiceProvider.showAsToast(false)
.


Ecclesiastes 2:9
So I was great, and increased more than all that were before me in Jerusalem: also my wisdom remained with me.


Futures provide a nice way to reason about performing many operations in parallel– in an efficient and non-blocking way. The idea is simple, a Future is a sort of a placeholder object that you can create for a result that does not yet exist. Generally, the result of the Future is computed concurrently and can be later collected. Composing concurrent tasks in this way tends to result in faster, asynchronous, non-blocking parallel code.
** Source : http://docs.scala-lang.org/overviews/core/futures.html
require "./src/futures"
include Futures
# Create a new future
a = Future.new do
someTimeConsumingOperation()
end
# Register a callback on successful operation
a.on_success do |val|
doSomethingWithResult val
end
a.on_failure do |err|
raise err
end
# Or handle both cases in one callback
a.on_complete do |result|
try = result.get
case try
when Success
puts try.get
when Failure
raise try.error
end
end
# Or block untill future completes
val = a.get
# compose new Futures from existing ones
b = a.map do |val|
"String : " + val
end
b.get


A not-for-profit organization founded in 2017 and licensed by Scrum Alliance® to produce Regional Scrum Gathering® Canada in Toronto, March 2018.
Starting December 2016, these generous individuals worked to produce Regional Scrum Gathering® Canada 2018.


| Top |
GObject ╰── GInitiallyUnowned ╰── GtkWidget ╰── GtkContainer ╰── GtkBin ╰── GtkButton ╰── GtkScaleButton ╰── GtkVolumeButton
GtkVolumeButton implements AtkImplementorIface, GtkBuildable, GtkActionable, GtkActivatable and GtkOrientable.
GtkVolumeButton is a subclass of GtkScaleButton that has been tailored for use as a volume control widget with suitable icons, tooltips and accessible labels.
GtkWidget *
gtk_volume_button_new (void
);
Creates a GtkVolumeButton, with a range between 0.0 and 1.0, with a stepping of 0.02. Volume values can be obtained and modified using the functions from GtkScaleButton.
Since: 2.12


Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's
Hi
Hey Maria
Talk
Catchu later
There are many variations of passages of Lorem Ipsum available,
but the majority have suffered
Ipsum is simply dummy text of the printing and typesetting industry.
Ipsum is simply dummy text of the printing and typesetting industry.
Ipsum is simply dummy text of the printing and typesetting industry.
Ipsum is simply dummy text of the printing and typesetting industry.
Ipsum is simply dummy text of the printing and typesetting industry.
Ipsum is simply dummy text of the printing and typesetting industry.
Ipsum is simply dummy text of the printing and typesetting industry.
Ipsum is simply dummy text of the printing and typesetting industry.


Home
Posts
Users
Clubs
Reference
In The Book Club Your New Name Will be: {{result.adjective}} {{result.noun}}
Find Books
Search Word


{% block head_extra %} {% endblock %}
This website uses cookies to improve your experience and collect anonymized usage statistics. Accept Opt Out Learn More


Cirque de Zack
Home
Shows
Feedback
Performance Feedback
Please provide your feedback below:
Please enter the location and date of the show you would like to provide feedback on below.
City:
How do you rate your overall experience?
Bad
Average
Good
Comments:
Your Name (Optional):
Email (Optional):
Submit
Posted your feedback successfully!
Error
Sorry there was an error sending your form.


Prototype change log
This summarises the main changes we’ve made in response to feedback.
Skeleton Version 1
Skeleton Version 1 A specific skeleton version created to provide assets for dev
|
Summary of Skeleton |
Reason/source |
|---|---|
|
A specific skeleton version created to provide assets for dev |
Based on Version 1.4 Chemicals, this version is not an end-to-end journey but consists of individual pages for the development team to use as templates Skeleton Version 1 includes only releases challenge, releases table, releases detail, error validation and add new substance journey |
Version 2.0
Version 2.0 updates the Intensive farmer user journey with waste transfer code lists filtered by recommendation
|
Summary of Version 2.0 |
Reason/source |
|---|---|
|
Waste transfer codes are filtered based on all PIEDC user history |
User feedback often cited too many codes as a pain point. Filtering is one suggestion to meet the need for simplicity. |
Version 1.3
Version 1.3 was a copy of version 1.2 with the data updated for a Waste transfer business and was the first all-sector version to be tested with users.
|
Summary of Version 1.3 |
Reason/source |
|---|---|
|
Added "select new NOSE-P code" journey Moved "Share your data" to before "Check your data" |
Version 1.2
Version 1.2 was a copy of version 1.1 with the data updated for a Waste transfer business and was the first all-sector version to be tested with users.
|
Summary of Version 1.2 |
Reason/source |
|---|---|
|
This user had few no substances released to air Numeric style to waste codes New pattern: Add new waste transfer. Step-by-step pick lists |
Version 1.1
Version 1.1 was our first version prototype for all-sectors.
A hypothesis based on user needs gathered from interviews with users who submit PI data and business requirements.
|
Summary of Version 1.1 |
Reason/source |
|---|---|
|
Version 1.1 was a copy of version 1.0 with the data updated for a Paper and Pulp manufacturer. We hypothesised we could make the service simple by presenting the fewest data input points for most users. The data entry user interface is a summary page with the previous year’s submission data preloaded (substance and value) and the current threshold. Input options allow for value and unit only. In the event the values to be inputted are exceptional, users can follow links to add more detail. Any QA issues are highlighted in the UI when the user continues. Following “more detail” will reveal more messaging about the issue and allow users to correct or explain the data. Common issues are shown plus an ‘other’ where users can add their own comments. |
Users tend to be specialists and are likely to transpose data that they have stored in their own spreadsheet. Users need to see historical data. They often input the same data each year and they tend to forget what they submitted the previous year. Users have a preference for handling data manually. |
Version 1
Version 1 was our first version prototype using the gov.uk prototype kit. It is a high-fidelity mock-up with which users can interact. It is based on a user journey built in sketch
An initial hypothesis based on user needs gathered from interviews with users who submit PI data and business requirements.
|
Summary of Version 1 |
Reason/source |
|---|---|
|
Version 1 demonstrated the user journey for an intensive farmer. We hypothesised it would be simpler for an intensive farmer if, rather than asking the user to determine their site's emissions using the formula given in the guidance, users could count livestock and how they are housed and the service could do the calculations to determine site emissions. This differs from all other sectors which requests the substances and amounts to be measured, calculated estimated by the user. Until we can draw business requirements from the internal needs research we assumed all the data being requested on the Pollution Inventory reporting form is required so company details, sharing information is collected. We did not include user authentication |
The intensive farming sector has specific user needs that differ from all other sectors and has the most sites and users of all sectors - they were also the first user the prototype was tested on. An initial hypothesis based on user needs gathered from interviews with users who submit PI data. This version is delivered through a content methodology from user needs based on user research: High level user needs included in this version:
|


Package Request Type
Create Schedule
Generate Now
Adhoc Schedule
Partial Export
Start Date
Start Time
Effective Date
Model: {{ model | json }}
Package Window Date
Model: {{ model | json }}
Package Instruction
Regular
Special
Package Content
Messages and File Output
Generate
Export Package
Cancle
Save


Class: Ram::Packager
- Inherits:
-
Object
- Object
- Ram::Packager
- Defined in:
- lib/jammit/packager.rb
Overview
The Ram::Packager resolves the configuration file into lists of real assets that get merged into individual asset packages. Given the compiled contents of an asset package, the Packager knows how to cache that package with the correct timestamps.
Instance Attribute Summary (collapse)
-
- (Object) force
Set force to false to allow packages to only be rebuilt when their source files have changed since the last time their package was built.
-
- (Object) package_names
Set force to false to allow packages to only be rebuilt when their source files have changed since the last time their package was built.
Instance Method Summary (collapse)
-
- (Object) cache(package, extension, contents, output_dir, suffix = nil, mtime = nil)
Caches a single prebuilt asset package and gzips it at the highest compression level.
-
- (Object) cacheable(extension, output_dir)
private
Return a list of all of the packages that should be cached.
-
- (Object) create_packages(config)
private
Compiles the list of assets that goes into each package.
-
- (Object) glob_files(glob)
private
Absolute globs are absolute — relative globs are relative to ASSET_ROOT.
-
- (Object) individual_urls(package, extension)
Get the list of individual assets for a package.
-
- (Packager) initialize
constructor
Creating a new Packager will rebuild the list of assets from the Ram.configuration.
-
- (Object) latest_mtime(paths)
private
Get the latest mtime of a list of files (plus the config path).
-
- (Object) not_found(package, extension)
private
Raise a PackageNotFound exception for missing packages…
-
- (Object) pack_javascripts(package)
Return the compressed contents of a javascript package.
-
- (Object) pack_stylesheets(package, variant = nil, asset_url = nil)
Return the compressed contents of a stylesheet package.
-
- (Object) pack_templates(package)
Return the compiled contents of a JST package.
-
- (Object) package_for(package, extension)
private
Look up a package asset list by name, raising an exception if the package has gone missing.
-
- (Object) precache_all(output_dir = nil, base_url = nil)
Ask the packager to precache all defined assets, along with their gzip’d versions.
Constructor Details
- (Packager) initialize
Creating a new Packager will rebuild the list of assets from the Ram.configuration. When assets.yml is being changed on the fly, create a new Packager.
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 |
# File 'lib/jammit/packager.rb', line 17 def initialize # In Rails, the difference between a path and an asset URL is "public". @path_diff = Ram.public_root.sub(ASSET_ROOT, '') @path_to_url = /\A#{Regexp.escape(ASSET_ROOT)}(\/?#{Regexp.escape(@path_diff)})?/ @compressor = Compressor.new @force = false @package_names = nil @config = { :css => (Ram.configuration[:stylesheets] || {}), :js => (Ram.configuration[:javascripts] || {}) } @packages = { :css => create_packages(@config[:css]), :js => create_packages(@config[:js]) } end |
Instance Attribute Details
- (Object) force
Set force to false to allow packages to only be rebuilt when their source files have changed since the last time their package was built.
12 13 14 |
# File 'lib/jammit/packager.rb', line 12 def force @force end |
- (Object) package_names
Set force to false to allow packages to only be rebuilt when their source files have changed since the last time their package was built.
12 13 14 |
# File 'lib/jammit/packager.rb', line 12 def package_names @package_names end |
Instance Method Details
- (Object) cache(package, extension, contents, output_dir, suffix = nil, mtime = nil)
Caches a single prebuilt asset package and gzips it at the highest compression level. Ensures that the modification time of both both variants is identical, for web server caching modules, as well as MHTML.
60 61 62 63 64 65 66 67 68 69 70 71 72 |
# File 'lib/jammit/packager.rb', line 60 def cache(package, extension, contents, output_dir, suffix=nil, mtime=nil) FileUtils.mkdir_p(output_dir) unless File.exists?(output_dir) raise OutputNotWritable, "Ram doesn't have permission to write to \"#{output_dir}\"" unless File.writable?(output_dir) mtime ||= latest_mtime package_for(package, extension.to_sym)[:paths] files = [] files << file_name = File.join(output_dir, Ram.filename(package, extension, suffix)) File.open(file_name, 'wb+') {|f| f.write(contents) } if Ram.gzip_assets files << zip_name = "#{file_name}.gz" Zlib::GzipWriter.open(zip_name, Zlib::BEST_COMPRESSION) {|f| f.write(contents) } end File.utime(mtime, mtime, *files) end |
- (Object) cacheable(extension, output_dir) (private)
Return a list of all of the packages that should be cached. If “force” is true, this is all of them — otherwise only the packages that are missing or whose source files have changed since the last package build.
121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 |
# File 'lib/jammit/packager.rb', line 121 def cacheable(extension, output_dir) names = @packages[extension].keys names = names.select {|n| @package_names.include? n } if @package_names config_mtime = File.mtime(Ram.config_path) return names if @force return names.select do |name| pack = package_for(name, extension) cached = [Ram.filename(name, extension)] cached.push Ram.filename(name, extension, :datauri) if Ram. cached.push Ram.filename(name, extension, :mhtml) if Ram.mhtml_enabled cached.map! {|file| File.join(output_dir, file) } if cached.any? {|file| !File.exists?(file) } true else since = cached.map {|file| File.mtime(file) }.min config_mtime > since || pack[:paths].any? {|src| File.mtime(src) > since } end end end |
- (Object) create_packages(config) (private)
Compiles the list of assets that goes into each package. Runs an ordered list of Dir.globs, taking the merged unique result. If there are JST files in this package we need to add an extra path for when package_assets is off (e.g. in a dev environment). This package (e.g. /assets/package-name.jst) will never exist as an actual file but will be dynamically generated by Ram on every request.
148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 |
# File 'lib/jammit/packager.rb', line 148 def create_packages(config) packages = {} return packages if !config config.each do |name, globs| globs ||= [] packages[name] = {} paths = globs.flatten.uniq.map {|glob| glob_files(glob) }.flatten.uniq packages[name][:paths] = paths if !paths.grep(Ram.template_extension_matcher).empty? packages[name][:urls] = paths.grep(JS_EXTENSION).map {|path| path.sub(@path_to_url, '') } packages[name][:urls] += [Ram.asset_url(name, Ram.template_extension)] else packages[name][:urls] = paths.map {|path| path.sub(@path_to_url, '') } end end packages end |
- (Object) glob_files(glob) (private)
Absolute globs are absolute — relative globs are relative to ASSET_ROOT. Print a warning if no files were found that match the glob.
105 106 107 108 109 110 |
# File 'lib/jammit/packager.rb', line 105 def glob_files(glob) absolute = Pathname.new(glob).absolute? paths = Dir[absolute ? glob : File.join(ASSET_ROOT, glob)].sort Ram.warn("No assets match '#{glob}'") if paths.empty? paths end |
- (Object) individual_urls(package, extension)
Get the list of individual assets for a package.
75 76 77 |
# File 'lib/jammit/packager.rb', line 75 def individual_urls(package, extension) package_for(package, extension)[:urls] end |
- (Object) latest_mtime(paths) (private)
Get the latest mtime of a list of files (plus the config path).
113 114 115 116 |
# File 'lib/jammit/packager.rb', line 113 def latest_mtime(paths) paths += [Ram.config_path] paths.map {|p| File.mtime(p) }.max || Time.now end |
- (Object) not_found(package, extension) (private)
Raise a PackageNotFound exception for missing packages…
167 168 169 |
# File 'lib/jammit/packager.rb', line 167 def not_found(package, extension) raise PackageNotFound, "assets.yml does not contain a \"#{package}\" #{extension.to_s.upcase} package" end |
- (Object) pack_javascripts(package)
Return the compressed contents of a javascript package.
85 86 87 |
# File 'lib/jammit/packager.rb', line 85 def pack_javascripts(package) @compressor.compress_js(package_for(package, :js)[:paths]) end |
- (Object) pack_stylesheets(package, variant = nil, asset_url = nil)
Return the compressed contents of a stylesheet package.
80 81 82 |
# File 'lib/jammit/packager.rb', line 80 def pack_stylesheets(package, variant=nil, asset_url=nil) @compressor.compress_css(package_for(package, :css)[:paths], variant, asset_url) end |
- (Object) pack_templates(package)
Return the compiled contents of a JST package.
90 91 92 |
# File 'lib/jammit/packager.rb', line 90 def pack_templates(package) @compressor.compile_jst(package_for(package, :js)[:paths]) end |
- (Object) package_for(package, extension) (private)
Look up a package asset list by name, raising an exception if the package has gone missing.
98 99 100 101 |
# File 'lib/jammit/packager.rb', line 98 def package_for(package, extension) pack = @packages[extension] && @packages[extension][package] pack || not_found(package, extension) end |
- (Object) precache_all(output_dir = nil, base_url = nil)
Ask the packager to precache all defined assets, along with their gzip’d versions. In order to prebuild the MHTML stylesheets, we need to know the base_url, because IE only supports MHTML with absolute references. Unless forced, will only rebuild assets whose source files have been changed since their last package build.
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 |
# File 'lib/jammit/packager.rb', line 40 def precache_all(output_dir=nil, base_url=nil) output_dir ||= File.join(Ram.public_root, Ram.package_path) cacheable(:js, output_dir).each {|p| cache(p, 'js', pack_javascripts(p), output_dir) } cacheable(:css, output_dir).each do |p| cache(p, 'css', pack_stylesheets(p), output_dir) if Ram. cache(p, 'css', pack_stylesheets(p, :datauri), output_dir, :datauri) if Ram.mhtml_enabled raise MissingConfiguration, "A --base-url option is required in order to generate MHTML." unless base_url mtime = latest_mtime package_for(p, :css)[:paths] asset_url = "#{base_url}#{Ram.asset_url(p, :css, :mhtml, mtime)}" cache(p, 'css', pack_stylesheets(p, :mhtml, asset_url), output_dir, :mhtml, mtime) end end end end |


Code Quiz
Getting started
This quiz is a ten question quiz on basic Javascript functions and syntax. You will have 5 mintues to complete the quiz. Click start to test your knowledge.
Start


Designed to support an introductory programming course, Introduction to Java Programming and Data Structures teaches you concepts of problem-solving and object-orientated programming using a fundamentals-first approach. Beginner programmers learn critical problem-solving techniques then move on to grasp the key concepts of object-oriented, GUI programming, data structures, and Web programming. This course approaches Java GUI programming using JavaFX, which has replaced Swing as the new GUI tool for developing cross-platform-rich Internet applications and is simpler to learn and use. This edition has been completely revised to enhance clarity and presentation, and includes new and expanded content, examples, and exercises.


Admin page 1 (action=adminpage1)
Admin page 2 (action=adminpage2)
User page 1 (action=userpage1)
User page 2 (action=userpage2)
Logout


The Assignment relationship links active elements (e.g., Business Roles or Application Components) with units of behaviour that are performed by them, or Business Actors with Business Roles that are fulfilled by them.
Structural.
A Business Actor assigned to a Business Role. A Business Role assigned to a Business Process or Function. An Application Component assigned to an Application Function.


{% extends 'base.html' %} {% block main %} HTTP 404 It seems you are looking for something that I don't have. {{ macros:: social_links( social_config=config.extra.social) }} Home {% endblock %}
{{ macros:: social_links( social_config=config.extra.social) }}
Home


Equivalent to clicking the Alignment tab in the Format Cells dialog box, which is displayed when you click the Cells command on the Format menu. Aligns the contents of the selected cells.
Syntax
ALIGNMENT(horiz_align, wrap, vert_align, orientation, add_indent, shrink_to_fit, merge_cells)
ALIGNMENT?(horiz_align, wrap, vert_align, orientation, add_indent, shrink_to_fit, merge_cells)
Horiz_align is a number from 1 to 7 specifying the type of horizontal alignment, as shown in the following table. If horiz_align is omitted, horizontal alignment does not change.
| Horiz_align | Horizontal alignment |
| 1 | General |
| 2 | Left |
| 3 | Center |
| 4 | Right |
| 5 | Fill |
| 6 | Justify |
| 7 | Center across selection |
Wrap is a logical value corresponding to the Wrap Text check box in the Alignment tab. If wrap is TRUE, Microsoft Excel selects the check box and wraps text in cells; if FALSE, Microsoft Excel clears the check box and does not wrap text. If wrap is omitted, wrapping does not change.
Vert_align is a number from 1 to 4 specifying the vertical alignment of the text. If vert_align is omitted, vertical alignment does not change.
| Vert_align | Vertical alignment |
| 1 | Top |
| 2 | Center |
| 3 | Bottom |
| 4 | Justify |
Orientation is a number from 0 to 4 specifying the orientation of the text. If orientation is omitted, text orientation does not change.
| Orientation | Text orientation |
| 0 | Horizontal |
| 1 | Vertical |
| 2 | Upward |
| 3 | Downward |
| 4 | Automatic (applies to only chart tick labels) |
Add_indent This argument is for only Far East versions of Microsoft Excel.
Shrink_to_fit is a logical value corresponding to the Shrink To Fit check box in the Alignment tab.
Merge_cells is a logical value corresponding to the Merge Cells check box in the Alignment tab. If merge_cells is TRUE, Microsoft Excel selects the check box and merges the selected cells; the merged cell contains the value of the left-most cell that was merged. If FALSE, Microsoft Excel clears the check box and unmerges the selected cells; the left-most cell takes the formula or value of the cell that was unmerged. If merge_cells is omitted, cell mergers do not change.
Related Function
FORMAT.TEXT Formats a worksheet text box or a chart text item
Return to index


{% with diff_result.diff_me_transcript as diff_me_tr %}
Diff Me
Region {{ diff_me_tr.loc_region }}
Start {{ diff_me_tr.loc_start }}
Stop {{ diff_me_tr.loc_end }}
Strand {{ diff_me_tr.loc_strand }}
Checksums
Location {{ diff_me_tr.loc_checksum }}
{% endwith %}
Match
{% include "checksum_match.html" with has_var_checksum=diff_result.result.has_location_changed %}
{% with diff_result|compare_transcript:"loc_start" as has_loc_start_changed %}
{% include "checksum_match.html" with has_var_checksum=has_loc_start_changed %}
{% endwith %}
{% with diff_result|compare_transcript:"loc_end" as has_loc_end_changed %}
{% include "checksum_match.html" with has_var_checksum=has_loc_end_changed %}
{% endwith %}
{% with diff_result|compare_transcript:"loc_strand" as has_loc_strand_changed %}
{% include "checksum_match.html" with has_var_checksum=has_loc_strand_changed %}
{% endwith %}
Checksums
{% with diff_result|compare_transcript:"loc_checksum" as has_transcript_checksum %}
{% include "checksum_match.html" with has_var_checksum=has_transcript_checksum %}
{% endwith %}
{% with diff_result.diff_with_transcript as diff_with_tr %}


WATCH: Year of Return: The African Americans moving to Ghana
by BBC1619 marks the year of the first documented arrival of enslaved Africans in what’s today the United States of America. The West African country of Ghana – which was a major hub during the transatlantic slave trade - declared 2019 the year of return and is encouraging the African diaspora to visit the country. According to the country’s tourism board from January to June this year, there was a 20 per cent increase in the number of Americans visiting the country and an 11 per cent increase in visitors from the UK. But some young African Americans have decided to return for good.


Answer a series of questions to reveal a hand picked selection of socks that we think you will really dig. The sock Sleuth will help determine your sock personality and introduce you to some unexpected options!
Let's Get Sleuthing! >Answer a series of questions to reveal a hand picked selection of socks that we think you will really dig. The sock Sleuth will help determine your sock personality and introduce you to some unexpected options!
Let's Get Sleuthing! >


| TIMINGS | MONDAY | TUESDAY | WEDNESDAY | THURSDAY | FRIDAY | SATURDAY | SUNDAY |
| 6.30A.M - 7.30A.M | YOGA | YOGA | YOGA | YOGA | MEDITATE | MEDITATE | MEDITATE |
| 7.30A.M - 8.00A.M | MEDITATE | MEDITATE | MEDITATE | MEDITATE | EXERCISE | EXERCISE | EXERCISE |
| 8.00A.M - 9.30A.M | PRAY(BE GRATEFUL) | PRAY(BE GRATEFUL) | PRAY(BE GRATEFUL) | PRAY(BE GRATEFUL) | PRAY(BE GRATEFUL) | PRAY(BE GRATEFUL) | PRAY(BE GRATEFUL) |
| 9.30A.M - 10.00A.M | BREAKFAST | BREAKFAST | BREAKFAST | BREAKFAST | BREAKFAST | BREAKFAST | BREAKFAST |
| 11.00A.M - 12.30P.M | READ POSITIVE ARTICLES | READ POSITIVE ARTICLES | READ POSITIVE ARTICLES | READ POSITIVE ARTICLES | TRY FAVOURITE HOBBIE | TRY FAVOURITE HOBBIE | TRY FAVOURITE HOBBIE |
| 2.00P.M - 3.00P.M | LUNCH | LUNCH | LUNCH | LUNCH | LUNCH | LUNCH | LUNCH |
| 3.00P.M - 4.30P.M | TAKE REST/NAP | TAKE REST/NAP | TAKE REST/NAP | TAKE REST/NAP | TAKE REST/NAP | TAKE REST/NAP | TAKE REST/NAP |
| 4.30P.M - 6.00P.MTRY FAVOURITE HOBBIE | TRY FAVOURITE HOBBIE | TRY FAVOURITE HOBBIE | TRY FAVOURITE HOBBIE | READ POSITIVE ARTICLES | READ POSITIVE ARTICLES | READ POSITIVE ARTICLES | |
| 6.00P.M - 7.30P.M | WALK IN NATURE | WALK IN NATURE | WALK IN NATURE | WALK IN NATURE | WALK IN NATURE | WALK IN NATURE | WALK IN NATURE |
| 8.30P.M - 9.30P.M | HAVE DINNER WITH FAMILY | HAVE DINNER WITH FAMILY | HAVE DINNER WITH FAMILY | HAVE DINNER WITH FAMILY | HAVE DINNER WITH FAMILY | HAVE DINNER WITH FAMILY | HAVE DINNER WITH FAMILY |
| 9.30P.M - 10.00P.M | SLEEP | SLEEP | SLEEP | SLEEP | SLEEP | SLEEP | SLEEP |


{Dev_loper}
Home
About
Contact
Hi, Im ________
bring your ideas to life with me
Multidisciplinary developer who makes and occasionally breaks things.
Skills
PROJECTS
About Project
Link
About Project
Link
About Project
Link
About Project
Link
About Project
Link
About Project
Link
In case of any query contact me at
Send Email


Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
IN THE COURT OF SH. DEVENDRA KUMAR SHARMA ADDL CHIEF METROPOLITAN MAGISTRATE (Spl. Acts) CENTRAL TIS HAZARI COURTS: DELHI Delhi Pollution Control Committee vs M/s AOne Automobile U/s 24/25/26/33A r.w.s. 41/43/44/49 of Water Act, 1974 CC No.76/06 JUDGMENT
(a) Serial no. of the case : 02401R0283622001 (b) Date of commission of offence: 19.04.2000 th (c) Name of complainant : DPCC, 4 Floor ISBT, Delhi54 through Sh. Ramesh Chandra, Junior Environmental Engineer (d) Name, parentage, residence: 1)M/s AOne Automobile A1, Jyoti Colony, Loni Road, Shahdara, Delhi
(e) Offence complained of/ proved : U/s 24/25/26/33A r/w sec.41/43/44/49 of Water Act, 1974
(f) Plea of accused : Pleaded not guilty.
(g) Final order : Acquitted
(h) Date of such order : 09.09.13 Date of Institution : 08.08.2000 Arguments heard/order reserved: 06.09.13 Date of Judgment: 09.09.13 Brief statement of the reasons for the decision:
1. The Complainant i.e. Delhi Pollution Control Committee (for short 'DPCC') filed the present complaint u/s 24/25/26/33A read with section 41/43/44 & 49 of the Water (Prevention & Control of Pollution) Act, 1974 (hereinafter to be referred as 'Act') against the accused. Present complaint was filed through Sh. Ramesh Chandra, the then Junior Environmental Engineer in DPCC.
DPCC vs M/s A-One Automobiles 1 of 9 The short facts of the case for filing of the present complaint for prosecution of the accused are that on 19.04.2000, the industrial unit of the accused M/s AOne Automobile was inspected by Vigilance Squad consisting of SDM (Seemapuri), DPCC Engineer and Sector Officer. During inspection, the required facility for washing the automobiles was found in the premises and oil mixed effluent was also observed in the drains and therefore, the unit closure directions were issued by the SDM. It is also alleged that the accused was operating its unit without obtaining requisite consent from DPCC. Hence, present complaint.
2. On filing of the complaint, accused was summoned and thereafter the prosecution examined the complainant Sh. Ramesh Chandra, Assistant Environmental Engineer as CW1 in precharge evidence. Thereafter, a charge u/s 24/25 & 26 of the Act, punishable u/s 41/43 & 44 of the Act was framed against the accused to which he pleaded not guilty and claimed trial.
3. In post charge evidence, the prosecution examined the complainant Sh. Ramesh Chandra, Environmental Engineer, as CW1, Sh. Dalbir Singh, Executive Engineer as CW2 and Sh. Mohd. Ahsan Abid, Additional Development Commissioner as CW3.
4. CW1 Sh. Ramesh Chandra, the complainant, deposed that he was duly authorized to file the present complaint by virtue of order dated 05.05.2000 Ex.CW1/2 passed by Dr. Chandra Prakash, Incharge (Legal Cell). CW1 DPCC vs M/s A-One Automobiles 2 of 9 reiterated the facts mentioned in the complaint and stated that an inspection of industrial unit of accused was carried out on 19.04.2000 and required facility for washing the automobiles was found in the premises and oil mixed effluent was also observed in the drains. The accused was operating its unit without obtaining requisite consent from DPCC and discharged untreated trade effluent. An inspection was prepared and the unit closure directions were issued by the SDM. He has proved on record inspection report Ex. CW1/8 and closure order Ex.CW1/9.
5. CW2 Sh. Dalbir Singh, the then Sector Officer, deposed that he alongwith SDM and DPCC Engineer, inspected the unit of the accused and found water mixed with oil and lubricants. Pump and compressor being used for washing vehicles were also found. The witness also deposed that an inspection report was prepared and premises was sealed. He also identified his signature appearing on inspection report Ex.CW1/8.
CW3 Mohd. Ahsan Abid, the then SDM who passed the sealing order, corroborated the testimony of other witnesses and deposed more or less on the lines of CW1 and CW2. All three witnesses were cross examined at length on behalf of the accused.
6. Statement of accused was recorded u/s 313 read with section 281 Cr.P.C. In his statement accused denied all the allegations and stated that he has been falsely implicated in this case. However, accused opted not to lead any defence evidence.
DPCC vs M/s A-One Automobiles 3 of 9
7. I have given my thoughtful consideration to the submissions advanced on behalf of the parties and have gone through the relevant records. I have also gone through the written arguments filed on behalf of complainant as well as relevant provisions of Water (Prevention & Control of Pollution) Act, 1974. A) The relevant provisions of section 24/25 & 26 of the Water (Prevention & Control of Pollution) Act, 1974 are reproduced for ready reference:
24. Prohibition on use of stream or well for disposal of polluting matter, etc. (1) Subject to the provisions of this section,
(a) no person shall knowingly cause or permit any poisonous, noxious or polluting matter determined in accordance with such standards as may be laid down by the State Board to enter (whether directly or indirectly) into any [stream or well or sewer or on land], or
(b) no person shall knowingly cause or permit to enter into any stream any other matter which may tend, either directly or in combination with similar matters, to impede the proper flow of the water of the stream in a manner leading or likely to lead to a substantial aggravation of pollution due to other causes or of its consequences.
25. Restrictions on new outlets and new discharge - [(1) Subject to this provisions of this section, no person shall, without the previous consent of the State Board,
8. establish or take any steps to establish any industry, operation or process, or any treatment and disposal system or any extension or addition thereto, which is likely to discharge sewage or trade effluent into a stream or well or sewer or on land (such discharge being hereafter in this section referred to as discharge of sewage); or
9. begin to make any new discharge of sewage
26. Provision regarding existing discharge of sewage or trade effluent. Where immediately before the commencement of this Act any person was discharging any sewage or trade effluent into a [stream or well or sewer or on land], the provisions of section 25 shall, so far as may be, apply in relation to such person as they apply in relation to the person referred to in that section subject to the notification that the application for consent to be made under sub section (2) of that section [shall be made on or before such date as may be specified by the State Govt. by notification in this behalf in the Official Gazette]. B) Learned counsel for complainant argued that the case of the prosecution has DPCC vs M/s A-One Automobiles 4 of 9 been proved beyond reasonable doubt in view of the testimony of the witnesses. Hence, accused may be convicted for the alleged offences.
On the other hand, learned defence counsel argued that accused is innocent he has been falsely implicated in this case just to harass him. It is further argued that no documentary evidence or photographs are filed on record to show that the unit was in existence at the time of inspection and moreover, no sample was taken and sent to lab for expert opinion to determine the existence of effluent. However, this plea of the accused does not hold much water. CW1, CW2 and CW3 were the member of Vigilance Squad, who inspected the unit of the accused on 19.04.2000. The original inspection report and closure order mentioning the irregularities and violation of the Hon'nble Supreme Court order and the Water Act by the accused, have been proved on record as Ex.CW1/8 and mark A. Accused did not deny his signature appearing upon inspection report Ex.CW1/8 as well as sealing order mark A. It is evident from the inspection report as well as sealing order that, the unit of the accused was inspected on 19.04.2000 and these documents were prepared at the spot which were signed by the accused also. C) Next contention raised is that no sample was taken, therefore, in absence of any expert opinion, it can not be said that the unit of the accused was discharging untreated effluent. However, perusal of section 21 of the Water (Prevention & Control Pollution) Act, 1974, makes it clear that collection of sample is not sine qua non. From the statement of witnesses, it is clear that no Effluent Treatment Plant (ETP) was installed by the accused and required DPCC vs M/s A-One Automobiles 5 of 9 facilities of servicing and washing of automobiles were existing at the site. Mixed oil effluent was also observed in the drain of unit and discharge of trade effluent without any treatment by putting any ETP. CW1 also stated that accused was operating his unit without obtaining requisite consent from DPCC. Accused has not denied this fact. Even the perusal of inspection report relied upon by the complainant makes it clear that no ETP was provided for the treatment of trade effluent and the entire untreated effluent was being discharged without any kind of treatment into the public sewer/drain. It is not the case of the accused that any ETP was installed and therefore, expert opinion is must to determine the prescribed parameter of trade effluent. In such circumstances, it is not necessary to collect the sample and send the same to lab test for expert opinion.
D) It is further argued that testimony of prosecution witnesses is not reliable as there is material contradiction in the testimony of prosecution witnesses and no independent public witness was joined in this case. This arguments of the learned defence counsel does not carry much weight. Inspection and closure of the unit is evident from the document Ex.CW1/8 and mark A. Perusal of the records reveals that the raid was conducted at the unit being closely run by the accused. Thus, in the circumstances joining of public witness can not be said to be necessary as it was not a public place. Even there is no law which mandates joining of public witness in each case. In any case, if independent persons are not willing to be a witness, the prosecution cannot be blamed and evidence of other witness cannot be discarded. In support of claim and DPCC vs M/s A-One Automobiles 6 of 9 contention, reliance may be placed upon the judgment reported in "AIR 1988 SC 1998". Though, some minor contradictions appears in the testimony of prosecution witnesses regarding the time of reaching the spot, location, distance and direction of shop. In this matter, inspection was carried out on 19.04.2000 and CW1 and CW2 was examined/cross examined in the year 2011 and CW3 was examined in the year 2012. Thus, it can not be aspected from a witness to tell each and everty thing minutely after passing of such a long period. Such type of minor contradictions may obviously occur due to lapses of a decade.
E) However, before coming to the conclusion of the case, it would be necessary to one important and legal issue raised by the learned defence counsel as the decision of this issue affect the case of the complainant. Learned counsel for the accused has vehemently argued that this complaint is not filed by the duly authorized and competent person and approval for filing the present complaint is not proved on record. On the other hand, learned counsel for complainant argued that not filing of approval on record is not fatal to the prosecution and this objection has been raised for the first time at the stage of fag end of the case. Per contra, learned defence counsel argued that except bald statement nothing is on record to show that complainant obtained any approval prior to filing of the present complaint. It is further argued that prosecution witnesses have kept mum that whether any approval was obtained or not. Even, this fact has not been mentioned in the complaint. Therefore, this legal issue was not raised earlier and complainant can not be allowed to advantage of this very DPCC vs M/s A-One Automobiles 7 of 9 lacuna on the part of the complainant.
F) As observed this complaint was filed on behalf of complainant by CW1 Sh. Ramesh Chandra the then serving Junior Environment Engineer in DPCC. CW1 deposed that he is authorized to file the present complaint through the document Ex.CW1/2. Bare perusal of document Ex.CW1/2 shows that Assistant/Junior Environmental Engineer was authorized to file complaint with prior approval of the Chairman of DPCC. It is argued on behalf of complainant that approval was obtained. However, no such approval is filed or proved on record. No approval as mentioned in document Ex.CW1/2 is filed on record. Further, there is no copy of minutes of meeting dated 30.03.2000 as stated in Ex.CW1/2 is on record to show that any resolution was passed to authorize area AEE/JEE to maintain prosecution as contemplated u/s 49 of Water Act. Present complaint is filed by CW1 who can not be delegated the power to adopt pick and choose policy. The statutory power of giving approval is given to the Board. In this case, complainant was authorized to file the present complaint through office order Ex.CW1/2 passed by Dr. Chandra Prakash, Incharge (Legal Cell) and not by the board. Thus, present complaint is not sustainable in absence of valid sanction/approval accorded by the competent person. In this regard, reliance may be placed upon the judgment report in "Criminal Appl. No.1284 of 1989, titled as S.M. Dubash and Ors vs. V.V.M. Bhosale and Ors".
G) In this case, it is reiterated that CW1 has even failed to show the valid DPCC vs M/s A-One Automobiles 8 of 9 sanction/approval to depose on behalf of the complainant. In fact, in this case, it appears that there is no approval accorded for filing of the complaint or for deposing before the court. In view of the aforesaid facts and circumstances, the court is of the considered view that the complainant has failed prove the competency to file this complaint on behalf of the complainant or deposing before this court by CW1. In this regard further reliance may be placed uon the judgment reported in "V (2008) SLT 246". In view of the findings regarding the competency of the witness to depose before this court as well as regarding filing of the present complaint, the court is of the considered opinion that the complainant has failed to prove the allegations against the accused made in the complaint in accordance with the provisions of law. Complaint is, therefore, dismissed. Accused is acquitted of charges leveled against him. However, bail bonds of accused already on record is extended in terms of section 437A for a period of six months. Case property, if any, be confiscated to the state and file be consigned to record room.
Judgment be sent to the server www.delhidistrictcourt.nic.in.
(DEVENDRA KUMAR SHARA) ACMM(SPECIAL ACTS) CENTRAL TIS HAZARI COURTS DELHI Announced in open court on 09.09.13 (Total number of page 9) (One spare copy attached) DPCC vs M/s A-One Automobiles 9 of 9


Ahmed Mohamed
abdulmoha
Java
Ping pong will count up to your number from 1 with the following excptions:


We have some very exciting news to announce today!
Elixir School and ElixirConf are partnering up to offer two days of in-person workshops! What could make this exciting announce even better? LiveView, obviously! Join us for two days of hands-on training with Phoenix, Channels, LiveView, and property-based testing. We’ll look at the role these technologies play in today’s real-time web and how we can build bulletproof features in our applications.
But wait — there’s even more! In continued dedication to our mission of making Elixir learning accessible to everyone, we’ll be offering our workshops at a discount! The specific discount and details will be announced in a follow-up post along with instructions on how you can register.
Join Sean Callan (@doomspork), Sophie DeBenedetto (@SophieDeBenedetto), and Michael Stalker (@michaelstalker) for two awesome days of training in beautiful Denver, CO. Come for Day 1 or Day 2, or both, and level up your Elixir in a truly first-of-its-kind workshop.
After Day 1’s workshop, Harnessing the Real-Time Web with Phoenix, Channels, and Presence, you’ll come away with the experience to confidently create Phoenix applications from scratch and implement basic real-time features. Along the way, learn not only Elixir and Phoenix how-tos, but also testing and application design best practices while we work together on our applications.
On Day 2, we’ll explore the advanced features of Phoenix, the real-time web, and testing with Building Bulletproof Real-Time Applications with Phoenix, LiveView, and StreamData. Expanding on the applications used in Day 1 (attendance is not required but encouraged), we’ll incorporate features into our application that leverage the new LiveView library and we’ll ensure our features are well tested with property-based testing and StreamData.
What is ElixirConf?
ElixirConf is the premier US-based conference for the Elixir programming language. Created to advance the Elixir programming language and community by bringing together people from around the globe to collaborate and learn, we here at Elixir School are proud to be working together this year. We’re excited to be a part of a mission that aligns so closely with our own goal of making Elixir learning accessible to people around the world.
Head on over to the official ElixirConf site to keep up to date on the latest news and be sure to stay tuned for more from us: https://Elixirconf.com
Caught a mistake or want to contribute to the article? Edit this page on GitHub!


--- layout: post title: "Day 10 - Bar Brothers Workout" subtitle: "Day 10 was come and with him my new weight, I am not happy about that but this is what I have so far, so I don't going to quit!" date: 2019-10-31 background: '/img/posts/intro-barbrothers.png' ---
My body weight has been increasing since yesterday, I've gained about a pound, I'm not really happy but that's what it is, which I'm sure I'm not going to retire at this point. In the evening a massive workout awaits me and tomorrow I will do cardio training.
Most important is not to forget to eat during the day, I have two fruits and today I will eat at a place close to my work, a salad with chicken breast and tahini (Sesame sauce).
At the evening I went to walk and after I was back home I run into Bar Brothers workout which to day is abs on bar, I must be honest with you, I was really hard to do this traning on the bar and not becouse, of my abs, my shuldress was really hurt and although I done four set for every type of workout.
After I finish my workout I cleaning the house and I arranged everything to be ready for the weekend, after that I showered up and wen for bad, tomorrow I will for workout and right after that, I'll check my weight, good night.
Cheers!


This is testing a github image that has been loaded onto github using the browser. that works but is not local. Lets try


func SelectEndpoints(k int, peerPool []discovery.NetworkMember) []*comm.RemotePeer
SelectEndpoints select k peers from peerPool and returns them.
Config defines the configuration of the pull mediator
type Config struct { ID string PullInterval time.Duration // Duration between pull invocations Channel common.ChainID PeerCountToSelect int // Number of peers to initiate pull with Tag proto.GossipMessage_Tag MsgType proto.PullMsgType PullEngineConfig algo.PullEngineConfig }
EgressDigestFilter filters digests to be sent to a remote peer, that sent a hello with the following message
type EgressDigestFilter func(helloMsg proto.ReceivedMessage) func(digestItem string) bool
IngressDigestFilter filters out entities in digests that are received from remote peers
type IngressDigestFilter func(digestMsg *proto.DataDigest) *proto.DataDigest
Mediator is a component wrap a PullEngine and provides the methods it needs to perform pull synchronization. The specialization of a pull mediator to a certain type of message is done by the configuration, a IdentifierExtractor, IdentifierExtractor given at construction, and also hooks that can be registered for each type of pullMsgType (hello, digest, req, res).
type Mediator interface { // Stop stop the Mediator Stop() // RegisterMsgHook registers a message hook to a specific type of pull message RegisterMsgHook(MsgType, MessageHook) // Add adds a GossipMessage to the Mediator Add(*proto.SignedGossipMessage) // Remove removes a GossipMessage from the Mediator with a matching digest, // if such a message exits Remove(digest string) // HandleMessage handles a message from some remote peer HandleMessage(msg proto.ReceivedMessage) }
func NewPullMediator(config Config, adapter *PullAdapter) Mediator
NewPullMediator returns a new Mediator
MembershipService obtains membership information of alive peers
type MembershipService interface { // GetMembership returns the membership of GetMembership() []discovery.NetworkMember }
MessageHook defines a function that will run after a certain pull message is received
type MessageHook func(itemIDs []string, items []*proto.SignedGossipMessage, msg proto.ReceivedMessage)
MsgType defines the type of a message that is sent to the PullStore
type MsgType int
Constants go here.
const ( HelloMsgType MsgType = iota DigestMsgType RequestMsgType ResponseMsgType )
PullAdapter defines methods of the pullStore to interact with various modules of gossip
type PullAdapter struct { Sndr Sender MemSvc MembershipService IdExtractor proto.IdentifierExtractor MsgCons proto.MsgConsumer EgressDigFilter EgressDigestFilter IngressDigFilter IngressDigestFilter }
Sender sends messages to remote peers
type Sender interface { // Send sends a message to a list of remote peers Send(msg *proto.SignedGossipMessage, peers ...*comm.RemotePeer) }


--- layout: project title: "Service Mesh Performance Specification" description: "Measuring and indexing the performance, overhead, and value of the world's service mesh deployments." author: twitter: layer5 image: path: /assets/images/buttons/smps.png width: 1200 thumbnail: /assets/images/buttons/smps_white.svg lang: en link: /performance permalink: /performance redirect_from: performance/ ---
The Service Mesh Performance Specification (SMPS) is a vendor-neutral specification for capturing details of:
SMPS is a collaborative effort of Layer5, UT Austin, Google, and The Linux Foundation.


Porting subversion To git
12 April 2017
Before leaving my current role, I was tasked to migrate existing SVN repositories into git. It is exciting since I never did such thing in the past. Funny enough, I was challenged to install git-all
on one of our unregistered Red Hat box. I'm failing to run this command to make base repository accessible. I can raise a ticket to register the box but I'm worried waiting for resolution would take longer than doing the migration on a different machine.
rhn-channel --add --channel=rhel-x86_64-server-optional-6
Anyways, I have to install git-svn
to my personal laptop and do the migration.
$ sudo yum install git-svn
...
Running transaction
Installing : git-svn-<IP_ADDRESS>-6.el7_2.1.x86_64 1/1
Verifying : git-svn-<IP_ADDRESS>-6.el7_2.1.x86_64 1/1
Installed:
git-svn.x86_64 0:<IP_ADDRESS>-6.el7_2.1
Backup and load svn repository
Since I'm going to do the migration on a my personal laptop, I need to dump all the repositories and load them.
$ svnadmin dump /var/svn/ami > airmenzies.dump
$ svnadmin create /home/drmanalo/svn/airmenzies
$ svnadmin load /home/drmanalo/svn/airmenzies < airmenzies.dump
Create committers.txt
Google seach results will give you a one liner to get all the committers.
$ svn log -q | awk -F '|' '/^r/ {sub("^ ", "", $2); sub(" $", "", $2); print $2" = "$2" <"$2">"}' | sort -u > committers.txt
We only have half a dozen svn users, so I decided to get it from conf/passwd
file of one of the repositories. Format should be like this.
root = root<EMAIL_ADDRESS>Clone subversion using git-svn
Here, I'm going to clone an existing svn repository into my home drive folder called temp
.
$ git svn clone file:///home/drmanalo/svn/airmenzies --no-metadata --authors-file=/home/drmanalo/Documents/committers.txt --stdlayout ~/temp
...
r1152 = 8ba77ef334b586dc7560e0bf5be0427f1b255fb8 (refs/remotes/trunk)
Checked out HEAD:
file:///home/drmanalo/svn/airmenzies/trunk r1152
Convert svn:ignore properties into .gitignore
$ cd ~/temp
$ git svn show-ignore -i trunk > .gitignore
$ git add .gitignore
$ git commit -m 'Convert svn:ignore properties to .gitignore.'

Delta compression using up to 4 threads.
Compressing objects: 100% (11853/11853), done.
Writing objects: 100% (32238/32238), 37.48 MiB | 53.16 MiB/s, done.
Total 32238 (delta 16197), reused 28310 (delta 14223)
To /home/drmanalo/projects/airmenzies.git
* [new branch] master -> master
You can safely delete the ~/temp
folder.
Push the bare repository
In this instance, I'm pushing the converted svn to my local gitlab
.
$ cd ~/projects/airmenzies.git
$ git remote add origin<EMAIL_ADDRESS>$ git push -u origin --all
Password for 'http://root@localhost':
Counting objects: 32238, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9879/9879), done.
Writing objects: 100% (32238/32238), 37.48 MiB | 0 bytes/s, done.
Total 32238 (delta 16197), reused 32238 (delta 16197)
remote: Resolving deltas: 100% (16197/16197), done.
To<EMAIL_ADDRESS>* [new branch] master -> master
Branch master set up to track remote branch master from origin.


"There is no one who loves pain itself, who seeks after it and wants to have it, simply because it is pain..."
the act, process, or result of developing the development of new ideas an interesting development in the case.
Learn moreGraphic designers/artists design graphics for use in media products such as magazines, labels, advertising and signage.
Learn moreIn the advertising, digital or marketing sectors, the creative team is responsible for generating attention-grabbing ideas that will entice the consumer or target audience.
Learn moreMy work<
My work<
My work<
My work
My work
All Pregress !!!!!!!!!!!!!!
Here!!!
Stay Connected


The 4MOST Galactic Pipeline – Delivering a brighter future for your spectra
{% block content %}{% endblock %}


--- layout: default ---
This workshop will teach developers how to build apps that run on kubernetes.
It can be thought of as:
- a container platform
- a microservices platform
- a portable cloud platform and a lot more.
Kubernetes provides a container-centric management environment.
It orchestrates computing, networking, and storage infrastructure on behalf of user workloads.
This provides much of the simplicity of Platform as a Service (PaaS) with the flexibility of Infrastructure as a Service (IaaS), and enables portability across infrastructure providers.


List of Students
Register a New Student
Search
#
Student Number
First Name
Middle Name
Last Name
CGPA
Enrollment Date
International
#
Edit
Delete


Da Vinci Payer Data exchange - Local Development build (v0.3.7). See the Directory of published versions
This section of the implementation guide defines the specific conformance requirements for systems wishing to conform to this Payer Data Exchange (PDex) Implementation Guide. The bulk of it focuses on the implementation of the CDS Hooks Specification to meet PDex use-cases. It also describes the use of SMART on FHIR and provides guidance on privacy, security and other implementation requirements.
This IG uses a combination of CDS-Hooks and SMART-on-FHIR to enable Providers to issue a query to a Health Plan and to retrieve information about their patient (the Health Plan member) that they MAY review and choose to commit to the patient record in their EMR.
CDS Hooks enables the Health Plan to be queried either via an on-demand transaction triggered from a SMRT-on-FHIR app, or from a workflow event in the EMR that triggers the hook, such as when an apppointment is booked for a patient.
The bulk of the functionality of this specification is implemented using CDS Hooks. The Hooks specification is small. Implementers should read and be familiar with all of it.
CDS Hooks is a relatively new technology. It is considered a Standard for Trial Use, meaning that it will continue to evolve based on implementer feedback and may change in ways that are not compatible with the current draft. As well, the initial version of the specification has focused on the core architecture and a relatively simple set of capabilities. Additional capabilities will be introduced in future versions.
To meet requirements identified by Da Vinci project participants, it is necessary to introduce some additional capabilities above and beyond what is currently found in the CDS Hooks specification. This section of the PDex implementation guide describes those additional capabilities and the mechanism the implementation guide proposes to implement them. The purpose of these customizations is to enable testing at connectathons and to support feedback into the CDS Hooks design process.
When interacting with EMR systems that support FHIR R4 the SMART App SHALL evaluate the EMR System’s CapabilityStatement that the implementation has determined relevant to this SMART-on-FHIR application to determine which of the records selected by the Provider can be written to the EMR via the FHIR API.
Where the EMR’s FHIR API does not enable the SMART App to write a resource via the API the SMART App SHOULD write the records that it is permitted to write to the API. The remaining selected records SHOULD be retained in the EMR in the most appropriate form to allow the provider access to the information when needed. Each capability listed here has been proposed to the CDS Hooks community and may well become part of the official specification, either in the initial release, or in some future release. However, there is a significant likelihood that the manner in which the requirements are met may vary somewhat from a syntax or even an architectural approach. Future versions of this implementation guide will be updated to align with how these requirements are addressed in future versions of the CDS Hook specification. This implementation guide will not be able to be Normative (locked into backward compatibility mode) until the underlying CDS Hooks content is also normative.
This implementation guide extends/customizes CDS Hooks in 4 ways:
Each are described in the following sections.
The hooks published in the CDS Hooks specification provide a list of context resources for the DSTU2 and STU3 versions of FHIR. The CDS Hook specification won’t be updated to include R4 resources until after R4 is finalized. Because this implementation guide is being written to support FHIR R4 as well as STU3 and Argonaut (DSTU2), it provides guidance on what R4 resources are relevant for each hook (both pre-existing hooks as well as newly proposed hooks).
It is possible that the actual list of R4 resources provided for the hooks will differ from that proposed in this IG. Future versions of the implementation guide will adjust accordingly.
The CDS Hooks payload received from an EMR can include DSTU2, STU3 or R4 resources. The Payer’s CDS Hooks service SHALL handle the content in the JSON hooks payload, regardless of version of FHIR used for incorporated resources.
The health plan’s CDS Hooks service SHALL provide access to FHIR R4 resources based on Profiles identified in the US Core, Da Vinci PDex and HRex IGs.
The SMART-on-FHIR App that MAY be called from the returned CDS Hooks card will not translate R4 profiles to earlier versions of FHIR.
When interacting with EMR systems that support FHIR R4 the SMART App SHALL evaluate the EMR System’s CapabilityStatement to determine which of the records selected by the Provider can be written to the EMR via the FHIR API. Where the EMR’s FHIR API does not enable the SMART App to write a resource via the API the SMART App shall write the records that it is permitted to write to the API. The remaining selected records SHALL be compiled into a FHIR bundle, a PDF SHALL be created to provide a human-readable version of the bundle and both documents SHALL be attached as a DocumentReference and commited to the patient’s record.
Where an EMR providing an R4 API prevents the attaching of a FHIR bundle to a DocumentReference the SMART APP SHALL attempt to write the selected records based upon the options listed below for graceful write degradation.
When interacting with EMR systems that support FHIR versions prior to FHIR R4 the SMART App SHALL , where permitted by the target EMR, create a DocumentReference and encapsulate a PDF, human readable version of the records being committed, together with a document bundle that encapsulates the FHIR resources from the health plan that the provider has selected to commit to the patient’s record.
Where the EMR does not support the attachment of FHIR Bundles to a DocumentReference record the SMART App SHALL create a human readable PDF version of the selected resources and attach this document to the DocumentReference and commit to the patient’s record.
Where the EMR does not support the attachment of PDF Documents to a DocumentRefernece record the SMART App SHALL create an HTML or XHTML document that contains the selected resources and attach this document to the DocumentReference and commit to the patient’s record.
Where the EMR does not support the attachment of HTML/XHTML documents to a DocumentRefernece record the SMART App SHALL create a human readable ASCII text version of the selected resources and attach this to the DocumentReference and commit to the patient’s record.
To summarize this graceful degradation in functionality the priority for writing information to a target EMR should be:
The base CDS hooks 1.0 specification defines the following hooks:
The expectation is that new hooks will be defined by and eventually formally approved by the community. The formal process for this proposal and maturity development process is still evolving. Individuals interested in this process can provide feedback here.
Defining new hooks is an expected part of the CDS Hooks specification and there is no need for hooks to be officially registered with the community for them to be used. However, using registered hooks increases the likelihood of broad adoption by the community - which increases the likelihood of broad uptake of this implementation guide. The project is proposing hooks that build on proposals made in the Da Vinci CRD IG.
This IG uses a modified appointment-book hook. Subscriber Id is declared as an OPTIONAL context field.
Subscriber Id or Member Id, if available, SHOULD be taken from the Patient’s Coverage record, or be manually entered by the Provider via the SMART-on-FHIR App.
If the Member Id is not available the Subscriber ID and the patient information from the Coverage.beneficiary element SHOULD be used to uniquely identify the member.
Sharing of Member health information via PDex SHALL use the CDS Hooks specification. Connection to health plan systems SHALL be supported via the following hook:
The overall flow of the SMART-on-FHIR and CDS-Hooks interaction is summarized in the diagram below:
| |
It is possible that this hook will change over the course of the review/approval process, including changes to the names of the hooks, their context parameters or other information. Future versions of this implementation guide will be updated to align with such changes. Additional hooks may also be added.
This IG defines an extension to the appointment-book hook. The additional optional context fields are:
NOTE: Even pre-existing hooks are not yet locked down as normative and similar changes are possible, though perhaps less likely.
A sample of the CDS Hook for appointment-book is included below:
{ "hookInstance": "d1577c69-dfbe-44ad-ba6d-3e05e953b2ea", "fhirServer": "http://fhir.example.com", "fhirAuthorization" : { "access_token" : "some-opaque-fhir-access-token", "token_type" : "Bearer", "expires_in" : 300, "scope" : "patient/Patient.read patient/Observation.read", "subject" : "cds-service4" }, "hook": "appointment-book", "user": "Practitioner/example", "context": { "userId" : "Practitioner/A12365498", "patientId" : "EMR1239876", "encounterId" : "654", "appointments" : [], } "extension" : { "memberId" : "HP567123489", "coverage" : "Coverage/ } }
If a Health Plan does not provide a Member Id on a coverage card the extension can reference a Coverage resource that contains the Subscriber Id and plan details and the beneficiary information (ie. the member demographic information).
Any identifiers associated with the coverage for the patient (which may include patient demographics) SHOULD be obtained from the FHIR Coverage record for the patient, or MAY be entered manually by the provider via the SMART-on-FHIR App.
PDex supports three common scenarios where CDS Hooks SHOULD be used:
The hook interaction for these scenarios is:
When a Card is returned from the CDS Hooks appointment-book service by a Health Plan it will provide the following elements:
The SMART-on-FHIR App MAY be configured with default FHIR search queries that can be set by the Clinician, or their organization.
Examples of preset search queries parameters MAY include, but are not limited to:
The later three items are used to enable the Provider to exclude information that they may already have in their system. These query parameters are examples of FHIR API queries. Any valid FHIR search query for a Patient MAY be constructed by the Provider. The potentially valid search query parameters will be limited by the options provided in the Health Plan’s FHIR API CapabilityStatement.
As a minimum the Health Plan’s FHIR API SHALL limit returned results to the records that are related to the Patient/Member that is the subject of the Provider query.
As a minimum searches of FHIR Resources SHOULD support the following query parameters where appropriate for a Resource Type:
An example CDS Hooks Response Card is shown below:
{ "cards": [ { "summary": "Provider Member History Request", "indicator": "success", "detail": "Response from Payer Appointment-Book Hook", "source": { "label": "Static Member History Response", "url": "https://example.com/fhir/" }, "links": [ { "label": "SMART Example App", "url": "https://smart.example.com/fhir/Patient/123456789", "type": "smart" } ] } ] }
This implementation guide sets expectations for two types of systems:
Client systems are electronic medical records, pharmacy systems and other clinical and administrative systems responsible for the ordering and execution of patient-related services. These are systems whose users have a need for discovery of patient information from health plans who have provided coverage to the patient.
Payer systems are systems run by health plans/insurers that provide insurance coverage to the patient and can provide claims history clinical information and benefits information about the patient.
The requirements and expectations described here are not intended to be exhaustive. Health plans and clients MAY support additional hooks, additional card patterns, additional resources, additional extensions, etc. The purpose of this implementation guide is to establish a baseline of expected behavior that communication partners can rely on and then build from. Future versions of this specification will evolve based on implementer feedback.


--- layout: page title: Lean Prover Zulip Chat Archive permalink: archive/113488general/49112vscodefreezesmymachine.html ---
I just pushed an update to the syntax highlighting in the vscode extension (we can now highlight def /- comment -/ foo /- comment -/ := ...
correctly). Last time I did this, it caused all windows machines to freeze. I would be grateful if any windows user would upgrade to the latest version of the vscode extension and confirm that it doesn't kill their machine.
My windows box seems fine so far with the latest version.
Tried it and it's fine.
{% endraw %}


We are a small Bitcoin mining company oerating just South of the town of Stonehaven in the north east of Scotland. We have a Raspberry Pi
mining stup which mines at about 5-25 Gh/s.
We are a small Bitcoin mining company oerating just South of the town of Stonehaven in the north east of Scotland. We have a Raspberry Pi
mining stup which mines at about 5-25 Gh/s.


|
lwIP
2.1.3
Lightweight IP stack
|
Functions | |
| void | snmp_mib2_set_sysdescr (const u8_t *str, const u16_t *len) |
| void | snmp_mib2_set_syscontact (u8_t *ocstr, u16_t *ocstrlen, u16_t bufsize) |
| void | snmp_mib2_set_syscontact_readonly (const u8_t *ocstr, const u16_t *ocstrlen) |
| void | snmp_mib2_set_sysname (u8_t *ocstr, u16_t *ocstrlen, u16_t bufsize) |
| void | snmp_mib2_set_sysname_readonly (const u8_t *ocstr, const u16_t *ocstrlen) |
| void | snmp_mib2_set_syslocation (u8_t *ocstr, u16_t *ocstrlen, u16_t bufsize) |
| void | snmp_mib2_set_syslocation_readonly (const u8_t *ocstr, const u16_t *ocstrlen) |
| void snmp_mib2_set_syscontact | ( | u8_t * | ocstr, |
| u16_t * | ocstrlen, | ||
| u16_t | bufsize | ||
| ) |
Initializes sysContact pointers
| ocstr | if non-NULL then copy str pointer |
| ocstrlen | points to string length, excluding zero terminator. if set to NULL it is assumed that ocstr is NULL-terminated. |
| bufsize | size of the buffer in bytes. (this is required because the buffer can be overwritten by snmp-set) if ocstrlen is NULL buffer needs space for terminating 0 byte. otherwise complete buffer is used for string. if bufsize is set to 0, the value is regarded as read-only. |
| void snmp_mib2_set_syscontact_readonly | ( | const u8_t * | ocstr, |
| const u16_t * | ocstrlen | ||
| ) |
see snmp_mib2_set_syscontact but set pointer to readonly memory
| void snmp_mib2_set_sysdescr | ( | const u8_t * | str, |
| const u16_t * | len | ||
| ) |
Initializes sysDescr pointers.
| str | if non-NULL then copy str pointer |
| len | points to string length, excluding zero terminator |
| void snmp_mib2_set_syslocation | ( | u8_t * | ocstr, |
| u16_t * | ocstrlen, | ||
| u16_t | bufsize | ||
| ) |
Initializes sysLocation pointers
| ocstr | if non-NULL then copy str pointer |
| ocstrlen | points to string length, excluding zero terminator. if set to NULL it is assumed that ocstr is NULL-terminated. |
| bufsize | size of the buffer in bytes. (this is required because the buffer can be overwritten by snmp-set) if ocstrlen is NULL buffer needs space for terminating 0 byte. otherwise complete buffer is used for string. if bufsize is set to 0, the value is regarded as read-only. |
| void snmp_mib2_set_syslocation_readonly | ( | const u8_t * | ocstr, |
| const u16_t * | ocstrlen | ||
| ) |
see snmp_mib2_set_syslocation but set pointer to readonly memory
| void snmp_mib2_set_sysname | ( | u8_t * | ocstr, |
| u16_t * | ocstrlen, | ||
| u16_t | bufsize | ||
| ) |
Initializes sysName pointers
| ocstr | if non-NULL then copy str pointer |
| ocstrlen | points to string length, excluding zero terminator. if set to NULL it is assumed that ocstr is NULL-terminated. |
| bufsize | size of the buffer in bytes. (this is required because the buffer can be overwritten by snmp-set) if ocstrlen is NULL buffer needs space for terminating 0 byte. otherwise complete buffer is used for string. if bufsize is set to 0, the value is regarded as read-only. |
| void snmp_mib2_set_sysname_readonly | ( | const u8_t * | ocstr, |
| const u16_t * | ocstrlen | ||
| ) |
see snmp_mib2_set_sysname but set pointer to readonly memory


--- layout: default ---
Intercooler allows you add AJAX to your web-application with as little (or as much) javascript as you would like. Bindings and dependencies are managed via REST-ful URLs specified using custom attributes.
<-- This button posts to the /example/click URL when it is clicked --> <button ic-post-to="/example/click">Click Me!</button> <-- This span is bound to a URL that returns an updated version of the span when the button is clicked --> You have not yet clicked the button
You can use Intercooler.JS for as much or as little of your application as you like. It mixes in cleanly with either traditional web-app methodology or fancy-pants single-page-app libraries.
Keeping the simple stuff simple, you can use easy to understand REST-ful urls to specify a server-side UI model for your HTML elements. Of course, Intercooler is pluggable, so you can drop into javascript whenever you'd like.
Intercooler uses pattern matching in your REST-ful URLs to detect and refresh dependencies between independent elements. Typically it will do the right thing without any additional work on your part. Of course, if you need to add or ignore dependencies, Intercooler allows you to do that as well.
Although it was inspired by Partials in Rails, IntercoolerJS can work equally well with any back end platform. Additionally, it is designed to play well with other Javascript frameworks, so you can use AngularJS or EmberJS in places your UI call for it.
IntercoolerJS works fine with any HTML/CSS framework, but it was designed with Bootstrap in mind, making it easy to create dynamic UIs using standard, simple Bootstrap techniques.
IntercoolerJS was designed from the ground up to be pluggable so, when push comes to shove, you can customise pretty much any part of the it you need to. On the other hand, Intercooler provides sensible, attractive defaults so you won't need to do much if you don't want to.


Ways To Improve Your Pitch Content For Melodies
August 31, 2018 | Nick Mazuk
There are so many different aspects of melody that it can be difficult to work on all of them at once.
That’s why it is useful to break down melody writing into it’s basic components and then practice each of them individually. Then, when you combine everything together, you can start to sculpt a melody with all these tools in your toolbox.
So today, I’m going to give you two basic yet effective ways to isolate pitch in your melody writing. This will let you develop melodies that have solid pitch content without needing to worry about structure, rhythm, dynamics, or anything else.
Way 1: Write a Pitch Line
The first way you should always practice when improving pitch is writing pitch lines. Don’t worry about rhythm. Only write notes.
Here’s an example of a pitch line.
As you do this, tweak, add, or delete notes to make the pitch content stronger. Use different techniques that we’ve talked about, including the magic moving note, new scales, unexpected notes, using new modes, beginning on dissonances, internal resolutions, delayed resolutions, and leading tones.
As you do this, start by focusing on one technique of improving your pitch. Let’s say magic moving note. Then, modify your pitch line only to have better internal resolutions. For instance, you might change the pitch line from above into this.
Repeat this several times with several pitch lines. Then, focus on a new technique, like using leading tones. Write several new pitch lines focusing on improving your use of leading tones. Then focus on new technique. Repeat.
So overall, the process is:
- Choose a technique of pitch to improve
- Write a pitch line
- Improve the pitch line with that one technique only
- Write several more pitch lines, improving each one using the technique
- Repeat 2-4 with a new technique
Then, when you are writing complete melodies, you already have the skills to figure out what is bad and to improve it.
Way 2: Write to a Rhythm
Writing a pitch line is great and works wonders. But it can be difficult at first to use those skills in a melody. Because you might feel like you need to add or delete notes, only to leave your melody sounding incoherent.
That is why it’s useful to also practice pitch with a rhythm. Here’s the process.
- Write a rhythmic melody with a good structure
- Write pitches to each note without changing the rhythm at all
- Improve the pitches with the skills you learned writing pitch lines
This is each step of a sample that I wrote, trying to begin on a dissonance for the improved melody.
Pitch Added:
Starting on Dissonance:
Getting Started
That is the basic process for improving your pitch content in melodies. And like all compositional elements, melody is a skill. That means you actually need to practice and get started practicing. I can give you the tools and methods to practice, but it is your job to take action.
Luckily, I’ve made the process of getting started easier for you. If you would like help getting clear instruction to practice pitch in melodies, download the free worksheet below. It will walk you step by step through the process I’ve laid out above. If you are already a subscriber, the worksheet is in your inbox.
Happy writing!


'Jiivi' actor Vetri’s next to star KGF villain
The latest actor to join the cast of the yet-to-be-titled film is Ramachandra Raju, who played the villain in last year’s hit film KGF.
by Gopinath RajendranVetri, who made his debut with the critically acclaimed 8 Thottakkal and was recently seen in Jiivi, will next work on a thriller, directed by debutant Guru Ramanujam.
The latest actor to join the cast of the yet-to-be-titled film is Ramachandra Raju, who played the villain in last year’s hit film KGF. He will play the antagonist in the film, which went on floors on Friday.
 But it will also have an underlying message. We have spoken about something that has not been addressed yet in Tamil cinema,” says director Guru, an erstwhile associate of Kazhugu director Sathyasiva.
The makers are planning to wrap up the film in a single schedule. The film, bankrolled by J Parthasarrathy also stars Diyaa Mayurikha, Marimuthu and Kabali-fame Vishvanth. The project will be shot in and around Chennai.


PLAY PIG-DICE
DONT KNOW HOW TO PLAY THE GAME
CLICK HERE!
PRESS THE "PLAY" TO START!


Has your book been in the news? Has your news been in a book? With this REVOLUTIONARY app, for the first time EWAr (do you see what we did there?), you can find out! No need to thank us.


测试，由html控制器生成 hsz
$117.99
Namira is a very slick and clean e-commerce template with endless possibilities.
Creating an awesome clothes store with this Theme is easy than you can imagine.
| Size: | EU 41 (US 8), EU 42 (US 9), EU 43 (US 10), EU 45 (US 12) |
|---|---|
| Colors: | Violet, Black, Blue |
| Fabric: | Cotton (100%) |
-
This template is so awesome. I didn’t expect so many features inside. E-commerce pages are very useful, you can launch your online store in few seconds. I will rate 5 stars.
-
This template is so awesome. I didn’t expect so many features inside. E-commerce pages are very useful, you can launch your online store in few seconds. I will rate 5 stars.


SITE_NAME is perfectly suited for monitoring cron jobs. All you have to do is update your cron job command to send an HTTP request to SITE_NAME after completing the job.
Let's look at an example:
$ crontab -l
# m h dom mon dow command
8 6 * * * /home/user/backup.sh
The above job runs /home/user/backup.sh
every day at 6:08. The backup
script is presumably a headless, background process. Even if it works
correctly currently, it can start silently failing in the future without
anyone noticing.
You can set up SITE_NAME to notify you whenever the backup script does not run on time, or it does not complete successfully. Here are the steps to do that.
If you have not already, sign up for a free SITE_NAME account.
In your SITE_NAME account, add a new check.
Give the check a meaningful name. Good naming will become increasingly important as you add more checks to your account.
Edit the check's schedule:
8 6 * * *
in the cron expression fieldTake note of your check's unique ping URL.
Finally, edit your cron job definition and append a curl or wget call after the command:
$ crontab -e
# m h dom mon dow command
8 6 * * * /home/user/backup.sh && curl -fsS --retry 5 -o /dev/null PING_URL
Now, each time your cron job runs, it will send an HTTP request to the ping URL. Since SITE_NAME knows your cron job's schedule, it can calculate the dates and times when the job should run.
This monitoring technique takes care of various failure scenarios that could potentially go unnoticed otherwise:
The extra options in the above example tell curl to retry failed HTTP requests, and silence output unless there is an error. Feel free to adjust the curl options to suit your needs.
/home/user/backup.sh
exits with an exit code 0.If your cron job consistently pings SITE_NAME an hour early or an hour late, the likely cause is a timezone mismatch: your machine may be using a timezone different from what you have configured on SITE_NAME.
On modern GNU/Linux systems, you can look up the time zone using the
timedatectl status
command and looking for "Time zone" in its output:
$ timedatectl status
Local time: C 2020-01-23 12:35:50 EET
Universal time: C 2020-01-23 10:35:50 UTC
RTC time: C 2020-01-23 10:35:50
Time zone: Europe/Riga (EET, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
journalctl
On a systemd-based system, you can use the journalctl
utility to see system logs,
including logs from the cron daemon.
To see live logs:
journalctl -f
To see the logs from e.g. the last hour, and only from the cron daemon:
journalctl --since "1 hour ago" -t CRON


I have a weird issue on my locally hosted Emoncms (latest version).
I have a Node (Node 1) with all of my weather data. I had setup feeds for all of the inputs to log to MySQL. This worked great until it just stopped. When I look at my inputs, there are no feeds associated with them, but when I go to my feeds, I still see all the feeds that I created and the data is still there up to the point where the input and feeds for just that node somehow got separated.
When I look in the MySQL database, all the data for the feeds is still there, just the input is no longer configured to go to those feeds.
I created a new feed (thinking it would link it to the old feed data) but it just created a new feed named exactly what the old feed was named.
Has anyone seen this before and is there anyway to relink the inputs with the feeds so I do not lose the data?
EmonCMS Inputs disconnected from Feeds
Submitted by rjsears on Tue, 19/04/2016 - 06:42I have a weird issue on my locally hosted Emoncms (latest version).
I have a Node (Node 1) with all of my weather data. I had setup feeds for all of the inputs to log to MySQL. This worked great until it just stopped. When I look at my inputs, there are no feeds associated with them, but when I go to my feeds, I still see all the feeds that I created and the data is still there up to the point where the input and feeds for just that node somehow got separated.
When I look in the MySQL database, all the data for the feeds is still there, just the input is no longer configured to go to those feeds.
I created a new feed (thinking it would link it to the old feed data) but it just created a new feed named exactly what the old feed was named.
Has anyone seen this before and is there anyway to relink the inputs with the feeds so I do not lose the data?
Thanks