The present invention relates to an apparatus for focusing electromagnetic, preferably pulsed laser, radiation, onto a sample with the aid of an optical component for focusing the radiation and a mirror for reflecting the radiation.
It is known to use laser radiation, in the microanalysis of materials, to evaporate the sample material and to produce plasma. In such procedures, it is desirable to focus the radiation to extremely small areas of the order of magnitude of a few microns, in order to make it possible to obtain not only information about the chemical composition of the sample material but also about its structure. The sample is generally accommodated in a vacuum chamber in which the devices for analyzing the evaporated sample material, e.g. a time of flight mass spectrometer among others, are disposed. If the sample is very thin, e.g. 0.1-0.5.mu., focusing of the laser beam on the side of the sample facing the mass spectrometer may be effected through the sample. If the sample is thicker and not transparent to the laser radiation the radiation must be introduced into the vacuum chamber, for example via a window, and must there be deflected onto the sample with the aid of a mirror.
The present invention relates to such an apparatus for focusing the reflected beam of electromagnetic radiation onto a sample.
A paper by J. F. Eloy and J. L. Dumas in "Methodes Physiques d'Analyse (GAMS)", July through September 1966, at pages 251 et seq., discloses the introduction of laser radiation into a vacuum chamber through a window, the provision of a lens in the vacuum chamber for focusing a beam of the laser radiation and the deflection of this focused laser beam in the direction of the sample with the aid of a planar mirror. This arrangement has the drawback that the lens must have a long focal length since it is arranged relatively far away from the sample. This makes it impossible to produce focal spots of less than 20.mu. diameter.
It is further known, as disclosed in a paper by R. A. Bingham and P. L. Salter in "International Journal of Mass Spectroscopy and Ion Physics", 21 (1976), page 133, to initially deflect the laser beam in the direction of the sample with the aid of a planar mirror and to arrange a lens system between this planar mirror and the sample. This prior art arrangement has the advantage that it can operate with lenses having short focal lengths, but it also has the drawback that relatively large optical components must be arranged in the immediate vicinity of the sample, which complicates the structure of the device as a whole. Moreover, when operating with various laser light wavelengths, the lens system must be achromatic, i.e. it must be independent of the wavelength of the laser radiation. Such an achromatic system, however, is very expensive.


Note:Pictures show the shape of chain. For actual size, please see the measurement. Listing price is for one item.

Write your own review

Review title:

Review text:

Rating:

Bad

Excellent

Your name

Your email

Enquiry

Contact

1-888-500-1586

(905) 554-5298

sales[at]BeadUnion.com

Bead Union

About us

Bead Union is a small unit of individuals who believe that top quality can coincide with value. We provide jewelers, crafters and artists with components to create elegant, unique and sterling jewelry. Our goal is to always supply our customers with the best product, customized to their needs and build connections with those individuals.


Greg Gates

Gregory Crozier "Greg" Gates (born April 28, 1926) is an American rower who competed in the 1948 Summer Olympics. He was born in Montclair, New Jersey. In 1948 he was a crew member of the American boat which won the bronze medal in the coxless fours event.

References

Category:1926 births
Category:Living people
Category:Olympic rowers of the United States
Category:Rowers at the 1948 Summer Olympics
Category:Olympic bronze medalists for the United States in rowing
Category:People from Montclair, New Jersey
Category:American male rowers
Category:Medalists at the 1948 Summer Olympics


Q:

Checking if process is completed (python)

How do I check if a process has stopped running in python? I don't care if it is a zombie process, just if it has stopped running (syscall exit) This only has to work on linux. I have checked out psutil, but the STATE_STOPPED and STATE_DEAD don't seem to work

A:

pidof -- find the process ID of a running program.

pidof will have his exit code to zero if at least one process by that name is running, else it will be one.
You can do a little bash script like this:
if pidof python > /dev/null;
then
    echo 'At least one is running'
else
    echo 'No process is running'
fi

I am pipe-ing the output to /dev/null just to avoid having the PID of the found process being printed, but this is optional.
EDIT: If you want to be able to do it from python, just do the same thing:
import os

if os.system("pidof man > /dev/null") == 0:
    print('At least one is running')
else:
    print('No process is running')


JENNY YOO LENA SATIN

JENNY YOO LENA SATIN

from 435.00

The Lena dress features a one shoulder neckline with wrapped pleating on the strap for an eye catching detail. The slim bias cut skirt highlights the body’s natural shape and femininity while the shine of the material adds glamour to the look. This dress is fully lined with a center back seam.

Shown in Emerald, Petal, Black, Hibiscus and Latte.

THIS ITEM IS MADE TO ORDER AND IS DELIVERED APPROXIMATELY 12 -16 WEEKS FROM ORDER DATE.

Satin backed crepe is available in petal, latte, hibiscus, emerald, and black.

*Due to the many variations in monitors and browsers, colour swatches and images may vary on different monitors. Computer monitors are not all calibrated equally and colour reproduction on the Internet is not precise.


Expression of p53 protein product in triple negative breast cancers and relation with clinical and histopathological parameters.
"Triple" negative breast cancer is a subgroup of so-called basal-like breast cancer. They are represented with 15% of all breast cancers, characterized with lack of hormone receptor as well as with negative expression of HER2 test. These tumors are more frequent in Afro-Americans and Latin-Americans, in patients with BRCA1 mutations and in patients with recent delivery. The aim of this study is to present the immunohistochemical and clinico-pathological characteristics of the triple negative breast cancer and their correlation with expression of the protein product of the tumor suppressor gene p53. A retrospective analyses of 24 patients with triple negative breast cancer was performed. All of the patients were evaluated in the Histopathological Laboratory of the Clinical Hospital Sistina, during the period from June 2009, until June 2011. The standard immunohistochemical procedures, including the hormone receptor status, HER2 status, proliferative index - Ki67 and p53 gene protein product were performed, as well as additional immunohistochemical staining for so-called basal keratins (Cytokeratin 5/6 and high molecular weight cytokeratin 34BE12). The age of the patients ranged from 29-77 years. Positive lymph nodes were found in 14 (59%) patients. The tumor was poorly differentiated in 19 patients (79%). Overexpression of the p53 protein product was evaluated in 19 (79%) of the cases. All p53 negative patients (5/5) had poorly differentiated tumors (G3), associated with positive regional lymph nodes. The p53 positive group expressed quite opposite correlation, only 9/19 (47%) were with positive lymph nodes (p = 0.03). The expression of p53 protein product was also associated with the nuclear grade (p = 0.005), the mitotic index (p = 0.001), lymph-vascular invasion (p = 0.005) and with the proliferation index Ki67 (p = 0.003). There was a trend for association with the tumor size - pT (p = 0.05). According to the results, the triple negative breast cancers are subgroup of the poorly differentiated neoplasms frequently associated in the younger age groups. The majority of these have overexpression of the p53 protein product, which in other hand, are inversely correlated with lymph nodes metastases. Hence, the necessity of enriching the immunohistochemical protocol of these patients with new antibodies, in order to evaluate their expression, which would be helpful for prediction the outcome of different therapeutical modalities.


Seeking to increase the availability of cost-competitive renewable energy to run their businesses, 12 companies have signed the Renewable Energy Buyers' Principles to better communicate their purchasing needs and expectations to the marketplace.

The companies - Bloomberg, Facebook, General Motors, Hewlett-Packard, Intel, Johnson & Johnson, Mars, Novelis, Procter and Gamble, REI, Sprint, and Walmart - hope the principles will open up new opportunities for collaboration with utilities and energy suppliers to increase their ability to buy renewable energy.

With a combined renewable energy target of 8.4 million MWh per year through 2020, the 12 participating companies are seeking a market shift to achieve their sustainable energy goals. Large-scale buyers often have to work around traditional utilities to purchase renewables at competitive prices at the scale they need, increasing complexity and transaction costs.

The Buyers’ Principles outline six criteria that would significantly help companies meet their ambitious purchasing goals:

Greater choice in procurement options;

More access to cost-competitive options;

Longer- and variable-term contracts;

Access to new projects that reduce emissions beyond business as usual;

Streamlined third-party financing; and

Increased purchasing options with utilities.

The principles address several major obstacles large companies face in procuring and installing renewable energy. For example, large buyers find current renewable energy markets are complicated to navigate and don’t deliver the products corporate customers are looking for. The sheer volume of renewable energy needed to meet their goals demonstrates both a clear demand and a market opportunity for any provider that can deliver what they need.

"We know cost-competitive renewable energy exists, but the problem is that it is way too difficult for most companies to buy," says Amy Hargroves, director of corporate responsibility and sustainability for Sprint. "Very few companies have the knowledge and resources to purchase renewable energy, given today’s very limited and complex options. Our hope is that by identifying the commonalities among large buyers, the principles will catalyze market changes that will help make renewables more affordable and accessible for all companies."

The Buyers’ Group is an informal consortium of companies interested in overcoming the obstacles to buying renewable energy and sharing best practices - not a power purchase group.

The principles evolved from a collaboration between World Wildlife Fund (WWF) and the Rocky Mountain Institute (RMI) to identify barriers to corporate achievement of renewable energy targets. The groups convened a Corporate Renewable Energy Buyers’ Day in 2013 to prioritize possible solutions - resulting in RMI’s creating the Renewables Resource Center and WWF’s partnering with the World Resources Institute to develop the new Buyers’ Principles.


{-# LANGUAGE DataKinds          #-}
{-# LANGUAGE DeriveDataTypeable #-}
{-# LANGUAGE DeriveGeneric      #-}
{-# LANGUAGE FlexibleInstances  #-}
{-# LANGUAGE NoImplicitPrelude  #-}
{-# LANGUAGE OverloadedStrings  #-}
{-# LANGUAGE RecordWildCards    #-}
{-# LANGUAGE TypeFamilies       #-}
{-# LANGUAGE TypeOperators      #-}

{-# OPTIONS_GHC -fno-warn-duplicate-exports #-}
{-# OPTIONS_GHC -fno-warn-unused-binds      #-}
{-# OPTIONS_GHC -fno-warn-unused-imports    #-}

-- |
-- Module      : Network.Google.Resource.FireStore.Projects.Databases.Documents.BatchGet
-- Copyright   : (c) 2015-2016 Brendan Hay
-- License     : Mozilla Public License, v. 2.0.
-- Maintainer  : Brendan Hay <brendan.g.hay@gmail.com>
-- Stability   : auto-generated
-- Portability : non-portable (GHC extensions)
--
-- Gets multiple documents. Documents returned by this method are not
-- guaranteed to be returned in the same order that they were requested.
--
-- /See:/ <https://cloud.google.com/firestore Cloud Firestore API Reference> for @firestore.projects.databases.documents.batchGet@.
module Network.Google.Resource.FireStore.Projects.Databases.Documents.BatchGet
    (
    -- * REST Resource
      ProjectsDatabasesDocumentsBatchGetResource

    -- * Creating a Request
    , projectsDatabasesDocumentsBatchGet
    , ProjectsDatabasesDocumentsBatchGet

    -- * Request Lenses
    , pddbgXgafv
    , pddbgUploadProtocol
    , pddbgDatabase
    , pddbgAccessToken
    , pddbgUploadType
    , pddbgPayload
    , pddbgCallback
    ) where

import           Network.Google.FireStore.Types
import           Network.Google.Prelude

-- | A resource alias for @firestore.projects.databases.documents.batchGet@ method which the
-- 'ProjectsDatabasesDocumentsBatchGet' request conforms to.
type ProjectsDatabasesDocumentsBatchGetResource =
     "v1" :>
       Capture "database" Text :>
         "documents:batchGet" :>
           QueryParam "$.xgafv" Xgafv :>
             QueryParam "upload_protocol" Text :>
               QueryParam "access_token" Text :>
                 QueryParam "uploadType" Text :>
                   QueryParam "callback" Text :>
                     QueryParam "alt" AltJSON :>
                       ReqBody '[JSON] BatchGetDocumentsRequest :>
                         Post '[JSON] BatchGetDocumentsResponse

-- | Gets multiple documents. Documents returned by this method are not
-- guaranteed to be returned in the same order that they were requested.
--
-- /See:/ 'projectsDatabasesDocumentsBatchGet' smart constructor.
data ProjectsDatabasesDocumentsBatchGet =
  ProjectsDatabasesDocumentsBatchGet'
    { _pddbgXgafv          :: !(Maybe Xgafv)
    , _pddbgUploadProtocol :: !(Maybe Text)
    , _pddbgDatabase       :: !Text
    , _pddbgAccessToken    :: !(Maybe Text)
    , _pddbgUploadType     :: !(Maybe Text)
    , _pddbgPayload        :: !BatchGetDocumentsRequest
    , _pddbgCallback       :: !(Maybe Text)
    }
  deriving (Eq, Show, Data, Typeable, Generic)

-- | Creates a value of 'ProjectsDatabasesDocumentsBatchGet' with the minimum fields required to make a request.
--
-- Use one of the following lenses to modify other fields as desired:
--
-- * 'pddbgXgafv'
--
-- * 'pddbgUploadProtocol'
--
-- * 'pddbgDatabase'
--
-- * 'pddbgAccessToken'
--
-- * 'pddbgUploadType'
--
-- * 'pddbgPayload'
--
-- * 'pddbgCallback'
projectsDatabasesDocumentsBatchGet
    :: Text -- ^ 'pddbgDatabase'
    -> BatchGetDocumentsRequest -- ^ 'pddbgPayload'
    -> ProjectsDatabasesDocumentsBatchGet
projectsDatabasesDocumentsBatchGet pPddbgDatabase_ pPddbgPayload_ =
  ProjectsDatabasesDocumentsBatchGet'
    { _pddbgXgafv = Nothing
    , _pddbgUploadProtocol = Nothing
    , _pddbgDatabase = pPddbgDatabase_
    , _pddbgAccessToken = Nothing
    , _pddbgUploadType = Nothing
    , _pddbgPayload = pPddbgPayload_
    , _pddbgCallback = Nothing
    }

-- | V1 error format.
pddbgXgafv :: Lens' ProjectsDatabasesDocumentsBatchGet (Maybe Xgafv)
pddbgXgafv
  = lens _pddbgXgafv (\ s a -> s{_pddbgXgafv = a})

-- | Upload protocol for media (e.g. \"raw\", \"multipart\").
pddbgUploadProtocol :: Lens' ProjectsDatabasesDocumentsBatchGet (Maybe Text)
pddbgUploadProtocol
  = lens _pddbgUploadProtocol
      (\ s a -> s{_pddbgUploadProtocol = a})

-- | The database name. In the format:
-- \`projects\/{project_id}\/databases\/{database_id}\`.
pddbgDatabase :: Lens' ProjectsDatabasesDocumentsBatchGet Text
pddbgDatabase
  = lens _pddbgDatabase
      (\ s a -> s{_pddbgDatabase = a})

-- | OAuth access token.
pddbgAccessToken :: Lens' ProjectsDatabasesDocumentsBatchGet (Maybe Text)
pddbgAccessToken
  = lens _pddbgAccessToken
      (\ s a -> s{_pddbgAccessToken = a})

-- | Legacy upload protocol for media (e.g. \"media\", \"multipart\").
pddbgUploadType :: Lens' ProjectsDatabasesDocumentsBatchGet (Maybe Text)
pddbgUploadType
  = lens _pddbgUploadType
      (\ s a -> s{_pddbgUploadType = a})

-- | Multipart request metadata.
pddbgPayload :: Lens' ProjectsDatabasesDocumentsBatchGet BatchGetDocumentsRequest
pddbgPayload
  = lens _pddbgPayload (\ s a -> s{_pddbgPayload = a})

-- | JSONP
pddbgCallback :: Lens' ProjectsDatabasesDocumentsBatchGet (Maybe Text)
pddbgCallback
  = lens _pddbgCallback
      (\ s a -> s{_pddbgCallback = a})

instance GoogleRequest
           ProjectsDatabasesDocumentsBatchGet
         where
        type Rs ProjectsDatabasesDocumentsBatchGet =
             BatchGetDocumentsResponse
        type Scopes ProjectsDatabasesDocumentsBatchGet =
             '["https://www.googleapis.com/auth/cloud-platform",
               "https://www.googleapis.com/auth/datastore"]
        requestClient ProjectsDatabasesDocumentsBatchGet'{..}
          = go _pddbgDatabase _pddbgXgafv _pddbgUploadProtocol
              _pddbgAccessToken
              _pddbgUploadType
              _pddbgCallback
              (Just AltJSON)
              _pddbgPayload
              fireStoreService
          where go
                  = buildClient
                      (Proxy ::
                         Proxy ProjectsDatabasesDocumentsBatchGetResource)
                      mempty


//------------------------------------------------------------------------------
// <copyright file="IWebPartParameters.cs" company="Microsoft">
//     Copyright (c) Microsoft Corporation.  All rights reserved.
// </copyright>
//------------------------------------------------------------------------------

namespace System.Web.UI.WebControls.WebParts {

    using System;
    using System.Collections;
    using System.ComponentModel;

    // Because of the SetConsumerSchema method, this interface only supports 1 consumer
    // at a time.  As a result, it is most useful when an IWebPartParameters consumer connects
    // to a provider via a transformer, like RowToParametersTransformer.  Alternatively, the
    // provider WebPart could specify AllowsMultipleConnections=false for the ConnectionPoint.
    public interface IWebPartParameters {
        PropertyDescriptorCollection Schema { get; }
        void GetParametersData(ParametersCallback callback);
        void SetConsumerSchema(PropertyDescriptorCollection schema);
    }
}


Metabolism and genetics of chlamydias and rickettsias.
Chlamydial and rickettsial diseases pose a hazard to man and to domesticated and wild animals. The virulence mechanisms which aid the establishment of these obligate intracellular parasites in the eukaryotic host are still not within our grasp. Recent knowledge of the biochemical stratagem, the metabolic capabilities and the genetic diversity of these microbes illustrate fundamental differences in ecology and evolutionary divergence. The preferred site of intracellular residence determines the strategy for uptake, for nutrient assimilation and also for evasion of the host's immunological defenses. The Chlamydia, Rickettsia, and Coxiella are the most extensively studied of the genera. Whereas the Ehrlichia and Cowdria are poorly understood, they are also the most intriguing of the Rickettsiae. A number of antigenically and genetically distinct species are identified for the genera Chlamydia, Rickettsia, and Ehrlichia, whereas the Coxiella and Cowdria may not represent such a wide diversity. Recent information on the genetic heterogeneity of the chromosomal and plasmid DNAs of the strains of Coxiella suggest the diversity is greater than was originally envisioned. New information regarding the antigenic structure of Cowdria and their cellular tropisms suggests that they are closely related to the Ehrlichia. In this review we compare the metabolic capabilities and the genetic diversity of these different intracellular bacteria.


453 B.R. 699 (2011)
In re LEGAL XTRANET, INC., Debtor.
Legal Xtranet, Inc. d/b/a/ Elumicor, Plaintiff,
v.
AT & T Management Services, L.P. f/k/a SBC Management Services, L.P., Defendant.
Bankruptcy No. 11-51042. Adversary No. 11-05042.
United States Bankruptcy Court, W.D. Texas, San Antonio Division.
May 24, 2011.
*702 Randall A. Pulman, Pulman, Cappuccio & Pullern LLP, William R. Davis, Jr., Langley & Banack, Inc., San Antonio, TX, for Plaintiff.
Michael M. Parker, Steve A. Peirce, Fulbright & Jaworski, LLP, Ricardo G. Cedillo, Troy A. Glander, Davis, Cedillo & Mendoza, Inc., San Antonio, TX, for Defendant.

DECISION AND ORDER ON DEFENDANT'S MOTION TO REMAND
LEIF M. CLARK, Bankruptcy Judge.
This decision and order resolves a motion to remand a matter removed to this court the same day the bankruptcy petition was filed. Almost immediately, the Defendant ("AT & T") requested remand, based upon the theories of mandatory abstention or, alternatively, permissive abstention/equitable remand. AT & T essentially argued that LXI's suit raised only state law claims and was at best "related to" LXI's bankruptcy case. AT & T further argued that mandatory abstention applied because this court only had jurisdiction, if at all, under the "related to" prong of 28 U.S.C. § 1334 and because AT & T's evidence showed that the case could be timely adjudicated in state court. Finally, AT & T argued that permissive abstention or equitable remand would also be appropriate.
LXI, the Plaintiff in the suit, and the Debtor in this bankruptcy case, naturally, objected to AT & T's motion to remand. First, LXI argued that mandatory abstention did not apply because LXI's claims against AT & T were core proceedings under various subsections of section 157(b)(2) of the Code. LXI asserted that its claims against AT & T were "in the nature of offsets against or attempts to limit the claims of what may well be one of Debtor's largest creditors" (Resp., p. 5.) and thus, as analogous to a response to a proof of claim, the claims against AT & T constituted core proceedings. LXI also argued that its suit fell within this court's core jurisdiction because it included a request for a determination that AT & T is responsible for all sales taxes assessed by the comptroller. LXI maintained that this claim arose under the Bankruptcy Code because it involved the determination of tax liability, liquidation of the assets of the estate and administration of the estate. Lastly, LXI argued that AT & T was also not entitled to equitable remand because consideration of the relevant factors actually favored keeping the case in the bankruptcy court.

Discussion
LXI's state court suit against AT & T seeks a declaratory judgment regarding a *703 contract that had governed the parties' relationship for many years. In December 2010, AT & T gave notice of its intention to terminate that contract pursuant to a provision of that contract. The ensuing dispute arose over the extent (if any) to which LXI might be entitled to certain protections for its claims of proprietary interest in certain software, and for its claims to trade secret protection. The dispute also centered around the extent (if any) to which LXI might be entitled to compensation for work associated with data transfer back to AT & T and/or its new contracting entity, and if so, at what rate. The declaratory judgment action seeks a determination that: 1) LXI is not required to turn over to AT & T its documents in LXI's proprietary and trade secret software format; 2) the Fourth Rate Amendment whereby AT & T pays an annual [redacted] repository management fee and thereafter only [redacted] cents per page for all other services is an effective amendment of the Master Agreement and was the rate for Electronic Data Discovery in effect at the time of the termination of the Master Agreement; 3) the applicable rate for the export and migration of AT & T's documents is: (a) [redacted] cents per page in accordance with the fourth Amendment of the Master Agreement, plus (b) depending on the length of time of such an export, an equal and proportional share of the [redacted] repository management annual fee; and 4) AT & T is responsible for any and all sales taxes assessed by the Texas Comptroller of Public Accountants for the audit period from July 1, 2006, through December 31, 2009, and any other subsequent periods. In short, LXI's suit requires that the court interpret the parties' contract and determine whether AT & T is liable for sales taxes assessed in connection with LXI's provision of services to AT & T. AT & T filed counterclaims against LXI for conversion and breach of contract and sought injunctive relief. AT & T's counterclaims have since been withdrawn. Its request for injunctive relief was essentially resolved after the matter had been removed to this court. Thus, all that remains to be tried are the various declaratory matters described above. Whether that trial should remain in the federal system or should instead be remanded to the state court is the subject of this decision and order.
As an initial matter, the court must address whether the remand request should be evaluated based on the pleadings as they stood as of the removal, or as they stood when they were later amended post-motion but prior to the hearing on the motion for remand. The issue arises because, shortly before the hearing, AT & T amended its answer and counterclaim by dropping its counterclaims (but asserting a defensive claim for recoupment). The case law offers a clear answer: the court must determine its jurisdiction based on the pleadings as of the time LXI filed its notice of removal. See Bissonnet Invs. LLC v. Quinlan (In Re Bissonnet Invs. LLC), 320 F.3d 520, 525 (5th Cir.2003) ("The existence of subject matter jurisdiction is determined at the time of removal.") (citing Arnold v. Garlock, 278 F.3d 426, 434 (5th Cir.2001)); Manguno v. Prudential Prop. & Cas. Ins. Co., 276 F.3d 720, 723 (5th Cir.2002) ("[T]o determine whether jurisdiction is present for removal, we consider the claims in the state court petition as they existed at the time of removal."); Enron Corp. Secs. v. Enron Corp. (In re Enron Corp. Secs.), 2005 WL 6220721, at *3-4, 2005 U.S. Dist. LEXIS 34029, at *15-16 (S.D.Tex. July 25, 2005) ("Jurisdiction is determined at the time of removal and the right to remove depends on the plaintiff's pleading at the time of petition for removal ... The same is true for removals under the much broader *704 grant of `related to' bankruptcy jurisdiction pursuant to 28 U.S.C. §§ 1334(b) and 1452(a).") (internal citations omitted). We thus consider the pleadings as they stood as of the date of filing of the motion for remand.
Looking at the parties' pleadings as they existed at the time of removal, the first issue to be addressed is whether the court has jurisdiction over the parties' state court proceeding and, if so, whether each cause of action asserted within that proceeding is core or non-core. See CBI Eastchase, L.P., et. al. v. Farris, et. al. (In re e2 Communications, Inc.), 2005 Bankr.LEXIS 3250, at *8 (Bankr.N.D.Tex. Mar. 24, 2005) (noting that before addressing the issues of abstention and equitable remand, "the first question is whether this Court has jurisdiction over the claims asserted in the State Court Action under section 1334"). Additionally, "`any doubts concerning removal must be resolved against removal and in favor of remanding the case back to state court ... [and, the removing party] bear[s] the burden of establishing federal jurisdiction under section 1334.'" Id. (citations omitted).
Section 1334 provides in relevant part:
(a) Except as provided in subsection (b) of this section, the district courts shall have original and exclusive jurisdiction of all cases under title 11.
(b) Except as provided in subsection (e)(2), and notwithstanding any Act of Congress that confers exclusive jurisdiction on a court or courts other than the district courts, the district courts shall have original but not exclusive jurisdiction of all civil proceedings arising under title 11, or arising in or related to cases under title 11.
28 U.S.C. § 1334(a)-(b). The term `cases under title 11' refers to the bankruptcy petition itself, which is not applicable here. See In re e2 Communications, 2005 Bankr.LEXIS 3250, at *9 n. 5. Thus, only subsection (b) is relevant to this dispute. A matter falls within the court's subject matter jurisdiction if the matter arises under a provision of title 11, or if the matter arises in or is related to the bankruptcy case. See id. Civil proceedings that arise under title 11 or arise in cases under title 11 are deemed "core" matters; while civil proceedings that are related to a title 11 case are deemed "non-core" matters. See id.; see also Morrison v. Western Builders of Amarillo, Inc. (In re Morrison), 555 F.3d 473, 479 (5th Cir.2009). As succinctly explained by the bankruptcy court for the Northern District of Texas,
`Arising under' jurisdiction involves causes of action created or determined by a statutory provision of title 11. `Arising in' jurisdiction is not based on a right expressly created by title 11, but is based on claims that have no existence outside of bankruptcy. Prior to confirmation of a plan of reorganization, `related to' jurisdiction exists if `the outcome of that proceeding could conceivably have any effect on the estate being administered in bankruptcy.
In re e2 Communications, 2005 Bankr. LEXIS 3250, at *9-10 n.5 (emphasis original) (citations omitted); see also In re Morrison, 555 F.3d at 479. A civil proceeding need not "necessarily be against the debtor or against the debtor's property. An action is related to bankruptcy if the outcome could alter the debtor's rights, options, or freedom of action (either positively or negatively) and which in any way impacts upon the handling and administration of the bankrupt estate." In re e2 Communications, 2005 Bankr. LEXIS 3250, at *10 n.5; Equity Broad. Corp. v. Shubert (In re Winstar Communs. Inc.), 284 B.R. 40, 50 (Bankr.D.Del.2002) (citing *705 Pacor v. Higgins, 743 F.2d 984 (3d Cir. 1984)).
The Fifth Circuit has said that,
For the purpose of determining whether a particular matter falls within bankruptcy jurisdiction, it is not necessary to distinguish between proceedings `arising under,' `arising in a case under,' or `related to a case under,' title 11. These references operate conjunctively to define the scope of jurisdiction....
In re Wood, 825 F.2d 90, 93 (5th Cir.1987). Wood presumed that "related to" jurisdiction represented the farthest reaches of bankruptcy subject matter jurisdiction, and so concluded that a court could cease looking further so long as it could find that a matter was at least related to the administration of the case. See id.[1] If this lawsuit is at least related to the case, then the court's subject matter jurisdiction will have been found. If it is not, then the court will have to look to whether it might in some sense be said to have arisen under a provision of title 11 or to have arisen in the case. As the case was removed to this court on the same day as the bankruptcy petition was filed, however, it is unlikely that the latter two reservoirs of jurisdiction could apply here. If there is subject matter jurisdiction, the court will then discuss whether these claims are core or non-core, a consideration particularly relevant to the claim for mandatory abstention.[2]
LXI argued that this court has jurisdiction over its state court suit under 28 U.S.C. § 1334 because its claims against AT & T constitute core proceedings under 28 U.S.C. § 157(b)(2)(A), (B), (C) and (O) (which means that there is necessarily subject matter jurisdiction, see Matter of Seven Elves,). LXI also maintained that its claim for a declaration that AT & T is responsible for all sales taxes constitutes a core proceeding based on the court's authority to determine tax liability issues under section 505(a)(1) of the Code. AT & *706 T concedes that all the claims and counterclaims in the suit (except for LXI's tax liability claim) fall within the court's "related to" jurisdiction (though it also maintains that these claims and counterclaims are non-core).
The court agrees with AT & T that both LXI's contract-related claims against AT & T and AT & T's counterclaims against LXI are at least "related to" LXI's chapter 11 case. The resolution of LXI's contract claim will have an impact on what is available to pay LXI's creditors as part of LXI's bankruptcy. See Regal Row Fina, Inc. v. Washington Mutual Bank, FA, 2004 WL 2826817, at *3-4, 2004 U.S. Dist. LEXIS 26704, at *11-12 (N.D.Tex. Dec. 9, 2004) (concluding that the court had at least "related to" jurisdiction over debtor's state law claims because "the outcome of this case would have an effect on [debtor's] estate since any recovery of monetary damages would necessarily accrue to the estate"); Maintainco, Inc. v. Mitsubishi Caterpillar Forklift Am., Inc. (In re Mid-Atlantic Handling Sys., LLC), 304 B.R. 111, 120 (Bankr.D.N.J. 2003) (finding that "pre-petition state law tortious interference and breach of contract claims" asserted against the debtor were "related to" debtor's chapter 11 case "since the outcome of the underlying lawsuit could alter the Debtor's rights concerning a significant asset of the estate"). As the Fifth Circuit observed in In re Zale Corp.:
[Section 1334's] reference to cases related to bankruptcy cases is primarily intended to encompass tort, contract, and other legal claims by and against the debtor, claims that, were it not for bankruptcy, would be ordinary stand-alone lawsuits between the debtor and others but that section 1334(b) allows to be forced into bankruptcy court so that all claims by and against the debtor can be determined in the same forum. A secondary purpose is to force into the bankruptcy court suits to which the debtor need not be a party but which may affect the amount of property in the bankrupt estate.
In re Zale Corp., 62 F.3d 746, 752 (5th Cir.1995) (citations and emphasis in original omitted). Although it is not limitless, `related-to' jurisdiction is broadly conferred so as to `avoid the inefficiencies of piecemeal adjudication and promote judicial economy by aiding in the efficient and expeditious resolution of all matters connected to the debtor's estate." Id., (quoting Miller v. Kemira, Inc. (In re Lemco Gypsum, Inc.), 910 F.2d 784, 787 (11th Cir.1990)). The claims and counterclaims relating to the contractual relationship fall within the subject matter jurisdiction of the federal courts under section 1334(b)'s "related to" prong.
LXI's request for a declaration that AT & T is responsible for all accrued sales taxes, however, is likely not the subject matter jurisdiction of the federal courts. LXI's complaint seeks a determination that "AT & T is responsible for any and all sales tax assessed by the Texas Comptroller of Public Accounts for the audit period from July 1, 2006, through December 31, 2009, and any other subsequent period." (Resp. to Motion to Remand, p. 5.) LXI argued that section 505(a)(1) of the Code confers bankruptcy jurisdiction over this claim. While the court would clearly have jurisdiction to decide matters involving the tax liabilities of LXI or the estate under section 505(a)(1), see In re Prescription Home Health Care, Inc., 316 F.3d 542, 547 (5th Cir.2002), LXI's claim seeks only a determination of AT&T's tax liability. In In re Prescription Home Health Care, Inc., the Fifth Circuit held that section 505(a)(1) of the Code does not confer jurisdiction on *707 bankruptcy courts to decide tax liability issues of non-debtors. Id. at 548. In that case, the debtor argued that the bankruptcy court had "related to" jurisdiction to decide the tax liability of a non-debtor officer of the debtor corporation because any assessment of federal tax liability against the non-debtor would jeopardize the success of the debtor's plan of reorganization. Id. The court rejected this argument, stating that
[u]nder [the debtor's] reading of `related to' jurisdiction, all tax matters could be adjudicated by the bankruptcy court if they could conceivably affect the debtor's estate. Such a reading would render superfluous § 505's grant of jurisdiction to determine the tax liabilities of the debtor or the estate.
Id. The court then noted that "[s]ister circuits that have addressed directly whether bankruptcy courts have jurisdiction over the tax liabilities of non-debtors have held that they do not." Id. Ultimately, the Fifth Circuit agreed with these sister circuits, concluding that "[t]he bankruptcy court lacked jurisdiction over [the non-debtor's] tax liability." Id. at 549.
While the Fifth Circuit's decision in In re Prescription Home Health Care, Inc. seems to foreclose the possibility that bankruptcy courts could ever have `related to' jurisdiction over the tax liabilities of non-debtors,[3] one of the circuit court decisions upon which the Fifth Circuit relied actually does not support this conclusion. In Quattrone Accountants, Inc. v. IRS, the Third Circuit specifically held that "Section 505 . . . neither limits nor grants jurisdiction" to determine the tax liability of a non-debtor. 895 F.2d 921, 924 (3d Cir.1990). As explained by one court,
[a]lthough it was clear to the Third Circuit that some restriction on the application of section 505(a) was contemplated by CongressCongress did not intend for bankruptcy courts to become another Tax Court, empowered to determine all tax disputes regardless of the partiesif the debtor requests a determination of the tax liability of a non-debtor under section 505, a bankruptcy court has subject matter jurisdiction to do so if permitted by 28 U.S.C. § 1334, the bankruptcy jurisdictional statute. In other words, the constraint on the broad application of section 505(a) is provided by section 1334. Thus, a bankruptcy court will possess subject matter jurisdiction over a tax dispute under section 505(a) only if the outcome of the dispute is related to the debtor's pending bankruptcy case.
In re Plymouth House Health Care Ctr., Inc., 2004 Bankr.LEXIS 2616, at *13 (Bankr.E.D.Pa. Sept. 10, 2004).
Even were we to apply the standard in Quattrone, however, the court does not believe that subject matter jurisdiction over the tax dispute can be found. The state comptroller has filed a proof of claim in the debtor's bankruptcy case, but AT & T is currently disputing in state court the amount of sales tax the Comptroller has claimed is due. This court has previously held that both vendors and purchasers are liable to the state for uncollected sales taxes. See Szostek v. Tex. State Comptroller of Pub. Accounts, 429 B.R. 552, 566 (Bankr.W.D.Tex.2010) (citing Bullock v. Foley Bros. Dry Goods Corp., 802 S.W.2d *708 835, 838 (Tex.App.Austin-1990)). In Quattrone, the Third Circuit stated that the "responsible person" liability of the corporation's principal officer was "entirely separate and distinct from the debtor's liability to the IRS," and ultimately concluded that the officer's liability was not "related to" the corporation's bankruptcy case under section 1334(b). 895 F.2d at 926-27. While the Third Circuit recognized that if the non-debtor officer were assessed and actually paid his "responsible person" tax liability, the amount the debtor owed to the IRS would decrease, the court nonetheless concluded that this did not amount to a "conceivable effect" on the estate in light of the contingent nature of the payment and the joint and several nature of the debt. Id. See also Newland v. United States, 150 B.R. 160-163 (Bankr.S.D.Miss. 1993) (concluding that the bankruptcy court did not have jurisdiction to decide the tax liability of a non-debtor where both the non-debtor and the debtor were liable for the tax at issue, and stating that "`simply because the debtor corporation is also liable for the taxes is no reason for the bankruptcy court to assume jurisdiction over the liability of the non-debtor' . . . Because [the debtor] remains liable for the taxes whether or not [the non-debtor] is also liable, there was no reason, even if there had been jurisdiction, for the bankruptcy court to adjudicate [the non-debtor's] tax liability.") (internal citation omitted). Here, similarly, both the debtor and AT & T could be held separately liable for the uncollected sales taxes. While AT & T's payment of the tax assessment would reduce or eliminate the debtor's sales tax debt, such a contingency does not confer related to jurisdiction, pursuant to section 505(a)(1), over AT & T's tax liability. See Quattrone, 895 F.2d at 927. Lacking jurisdiction over the tax-related claims, the court is constrained to remand that portion of the lawsuit. See 28 U.S.C. § 1452(a).[4]
Having found subject matter jurisdiction over LXI's contract-related claims and AT & T's counterclaims, the next question is whether LXI's claims and AT & T's counterclaims are core or non-core. Initially, it is important to note that "the `core proceeding' analysis is properly applied not to the case as a whole, but as to each cause of action within a case." Davis v. Life Investors Ins. Co. of Am., 282 B.R. 186, 193 n. 4 (S.D.Miss.2002); see also In re Exide Techs., 544 F.3d 196, 206 (3d Cir.2008) ("A single cause of action may include both core and non-core claims. The mere fact that a non-core claim is filed with a core claim will not mean the second claim becomes `core.'"). In determining whether a particular claim is core or non-core, courts first look to the language of 28 U.S.C. § 157, which sets forth a non-exclusive list of proceedings that are core. Section 157 provides:
(2) Core proceedings include, but are not limited to(A) matters concerning the administration of the estate; (B) allowance or disallowance of claims against the estate or exemptions from property of the estate, and estimation of claims or interests for the purposes of confirming a plan under chapter 11, 12, or 13 of title 11 [11 USCS §§ 1101 et seq., 1201 et seq. or 1301 et seq.] but not the liquidation or estimation of contingent or unliquidated personal injury tort *709 or wrongful death claims against the estate for purposes of distribution in a case under title 11; (C) counterclaims by the estate against persons filing claims against the estate; (D) orders in respect to obtaining credit; (E) orders to turn over property of the estate; (F) proceedings to determine, avoid, or recover preferences; (G) motions to terminate, annul, or modify the automatic stay; (H) proceedings to determine, avoid, or recover fraudulent conveyances; (I) determinations as to the dischargeability of particular debts; (J) objections to discharges; (K) determinations of the validity, extent, or priority of liens; (L) confirmations of plans; (M) orders approving the use or lease of property, including the use of cash collateral; (N) orders approving the sale of property other than property resulting from claims brought by the estate against persons who have not filed claims against the estate; (O) other proceedings affecting the liquidation of the assets of the estate or the adjustment of the debtor-creditor or the equity security holder relationship, except personal injury tort or wrongful death claims; and (P) recognition of foreign proceedings and other matters under chapter 15 of title 11 [11 USCS §§ 1501 et seq.].
28 U.S.C. § 157(b)(2). Next, courts engage in a two-step inquiry whereby a claim will be core "`if (1) it invokes a substantive right provided by title 11 or (2) if it is a proceeding, that by its nature, could arise only in the context of a bankruptcy case.'" In re Exide Techs., 544 F.3d 196, 207 (3d Cir.2008) (citations omitted.).
LXI's contract claims against AT & T are non-core. First, the claims neither arise under nor arise in a case under title 11. "`Arising under' jurisdiction involves causes of action created or determined by a statutory provision of title 11." In re e2 Communications, 2005 Bankr. LEXIS 3250, at *9-10 n.5 (citations omitted). See also, In re Wood, 825 F.2d 90, 97 (5th Cir.1987) (noting that a proceeding does not "arise under" Title 11 if it does not invoke a substantive right, created by federal bankruptcy law, that could not exist outside of bankruptcy); Kovalchick v. Dolbin (In re Kovalchick), 2006 U.S. Dist. LEXIS 66968, 2006 WL 2707428, at *4 (M.D.Pa. Sept. 19, 2006) (state law claims do not fall within bankruptcy court's "arising under" jurisdiction because they do not invoke substantive rights provided by Title 11); Wachovia Bank, N.A. v. Carroll, 2009 WL 330019, at *1-2, 2009 U.S. Dist. LEXIS 10175, at *4 ("As these questions initially arose in a state-court proceeding, long before Carroll filed for bankruptcy, this case did not `arise under' or `arise in' a title 11 proceeding."). Neither do LXI's state law claims against AT & T `arise in' LXI's bankruptcy case as they could (and in fact did) exist absent LXI's bankruptcy filing. "Claims that `arise in' a bankruptcy case are claims that by their nature, not their particular factual circumstance, could only arise in the context of a bankruptcy case." In re Seven Fields, 505 F.3d at 260 (citation omitted); see also Stoe v. Flaherty, 436 F.3d 209, 216 (3d Cir.2006) (noting that matters "arise in" bankruptcy only "if they have no existence outside of the bankruptcy"). Here, LXI commenced the state court lawsuit, involving purely state law issues, before it filed for bankruptcy. LXI's claims against AT & T are non-core. See Coho Oil & Gas, Inc. v. Finley Res., Inc. (In re Coho Energy, Inc.), 309 B.R. 217, 222 (Bankr.N.D.Tex.2004) (finding that "an action seeking damages for pre-petition breaches of pre-petition contracts and for pre-petition tortious conduct," was "a non-core proceeding which neither arises in nor under title 11").
Although LXI's breach of contract claim against AT & T is non-core, at least one *710 court within the Fifth Circuit has found state law claims to be core where they are "inextricably intertwined with the bankruptcy proceeding." Regal Row Fina, Inc. v. Washington Mutual Bank, 2004 WL 2826817, at *7, 2004 U.S. Dist. LEXIS 26704, at *25 (N.D.Tex. Dec. 9, 2004). In Regal Row, the debtor filed a suit alleging, inter alia, fraud in a real estate contract against the debtor's largest creditor three days before the debtor filed its chapter 11 petition. The creditor then filed a notice of removal, to which the debtor objected. The court concluded that the debtor's state court suit was a core proceeding under several of the subsections of section 157(b)(2) because the suit "directly affect[ed] the administration of the estate." Id. at *6, 2004 U.S. Dist. LEXIS 26704 at *20. The court stated,
[the creditor] is the largest creditor of [the debtor]; it was [the creditor's] collection activity that eventually brought on the filing of the bankruptcy case. [The creditor] has filed a proof of claim in the bankruptcy case and has actively participated in hearing in which [the debtor] sought authority from the bankruptcy court to use [the creditor's] cash collateral . . . As a result, any recovery that [the debtor] receives from this case would naturally be applied against the indebtedness evidenced by the promissory note executed by [the debtor] in favor of [the creditor].
Id. at *6-7, 2004 U.S. Dist. LEXIS 26704 at *20-22. The court went on to state,
Another significant factor is that this case is a proceeding involving the allowance or disallowance of claims or counterclaims or exemptions from property of [the debtor's] estate. 28 U.S.C. § 157(b)(2)(B). [The creditor] contendsand the court agreesthat because [the creditor] has filed a proof of claim in [the debtor's] bankruptcy case and because this case is intertwined with its proof of claim, the case necessarily affects the allowance or disallowance of claims against [the debtor's] bankruptcy estate. Thus, before [the debtor] can confirm a reorganization plan in the bankruptcy court, the extent of [the debtor's] net obligation to [the creditor] must be established.
Additionally, the court concludes that this proceeding, if not originally a core proceeding, has been converted into one by [the creditor's] filing of a proof of claim. See 28 U.S.C. § 157(b)(2)(C). Even though [the creditor's] proof of claim was filed after the plaintiffs filed their state court petition, [the creditor]by filing its proof of claimconverted the plaintiffs' adversary proceeding involving state tort law claims `related to' [the debtor's] bankruptcy to a proceeding to adjudicate a counterclaim `arising under' title 11. Numerous courts have found claims asserted by the debtor against a person who has filed proof of claims against the estate to be counterclaims within the meaning of § 157(b)(2)(C), and therefore core proceedings, notwithstanding the fact that the claims were asserted by procedures other than counterclaiming against the proof of claim itself . . .
Finally, this case is properly considered a core proceeding by virtue of the `catch-all' provision because the plaintiffs' claims against [the creditor] would likely 'affect[] the liquidation of the assets of the estate or the adjustment of the debtor-creditor. . . relationship.' 28 U.S.C. § 157(b)(2)(O).
Id. at *6-7, 2004 U.S. Dist. LEXIS 26704 at at *22-25 (internal citations omitted).
The present case can be distinguished from Regal Row, however. Most notably, here, AT & T has not filed a proof of claim. Moreover, it is clear that AT & T does not *711 plan to file a proof a claim. AT & T has withdrawn its counterclaims against LXI, asserting only the defense of recoupment. Additionally, AT & T demanded a jury trial and refused to consent to a jury trial in this court. It is clear that AT & T is doing everything in its power to avoid being subject to this court's jurisdiction.
Finally, the court disagrees with Regal Row's over-reliance on the catch-all provision of section 157(b)(2)(O) in determining that the debtor's state court suit, filed before the debtor filed for bankruptcy, can constitute a core proceeding. The court does not support the attempt to incorporate "pre-petition causes of action, premised on state law, into the catchall provisions of 28 U.S.C. § 157(b)(2)." Peterson v. 610 West Owners Corp. (In re 610 West Owners Corp.), 219 B.R. 363, 372 (Bankr.S.D.N.Y.1998) (citation omitted). To do so, "would allow the `amorphous' catch-all provision to `emasculate' the Supreme Court's decision in Marathon." Id.; see also In re Wood, 825 F.2d at 95.[5] "Every proceeding [could] be characterized as a core proceeding, because every recovery can change the size of the bankruptcy estate." Id. The argument also runs counter to Congress' intent in distinguishing core and non-core claims. See In re 610 West Owners Corp., 219 B.R. at 372. "A proceeding is not `core' simply because it `arguably fits within the literal wording' of one of the listed proceedings under § 157(b)(2)." Hoffmeyer v. Loewen Group Int'l, Inc. (In re Loewen Group Int'l, Inc.), 279 B.R. 471, 475 (Bankr.D.Del.2002). Plaintiff's contract claims in this case are non-core matters.
Finally, AT & T's counterclaims are also non-core. LXI argued that AT & T's counter-claims were core under section 157(b)(2)(B) because they constituted claims against the debtor. This argument would certainly be correct if AT & T filed a proof of claim. See Steinman v. Spencer (In re Argus Group 1700, Inc.), 206 B.R. 737, 747-48 (Bankr.E.D.Pa.1996) (filing of a proof of claim which asserts the same claims raised against the debtor in a prepetition state court action transforms the state court action into a core proceeding); see also Davis v. Life Investors Ins. Co. of Am., 282 B.R. 186, 193 (S.D.Miss.2002) (noting that had defendant actually filed any pleadings in state court asserting the same claim as that asserted in its proof of claim, the court would have considered the state court claim core); In re Best Reception Sys., Inc., 220 B.R. 932, 944 (Bankr. E.D.Tenn.1998) ("Where a party has filed a proof of claim in a debtor's case, any action asserted by that party against the debtor that raises the same issues as those encompassed by the proof of claim is a core proceeding under . . . § 157(b)(2)(B)"); Maintainco, Inc. v. Mitsubishi Caterpillar Forklift Am., Inc. (In re Mid-Atlantic Handling Sys., LLC), 304 B.R. 111, 123 (Bankr.D.N.J.2003) ("Because the proof of claim filed by Maintainco encompasses the same issues as those raised by the removed state law proceeding (in fact, the state court complaint was attached to the proof of claim), the filing, without more, converted the underlying action into a core proceeding under § 157(b)(2)(B)."); Shubert v. Lucent Techs. *712 Inc. (In re Winstar Communs., Inc.), 348 B.R. 234, 247 (Bankr.D.Del.2005) (finding that "[w]hether [defendant] may have breached the Subcontract . . . has a direct bearing upon whether [defendant] may recover under its Proof of Claim and if so, in what amount. Therefore the breach of the Subcontract claim falls within the core jurisdiction of the Court.").
AT & T has not filed a proof of claim, however. What is more, the counterclaims were filed before there was a bankruptcy case pending, so they cannot of themselves be a conscious decision to participate in the distributional process of bankruptcy. Yes, they are claims against the debtor, stayed by the automatic stay. That is not enough to render them the equivalent of proofs of claim. Despite LXI's assertion that AT & T would have to eventually file a proof of claim to preserve its rights in the bankruptcy court, that eventuality is insufficient to deem AT & T's counterclaims core at this time. See Lennar Corp. v. Briarwood Capital LLC, 430 B.R. 253, 265 (Bankr.S.D.Fla.2010) ("In looking at the core versus non-core nature of the removed case, the Court must look solely to the present record, not what may or may not happen in the Bankruptcy Cases."); In re Asousa Partnership, 264 B.R. 376, 387 (Bankr.E.D.Pa.2001) (holding that "when no proof of claim is filed, claims (or counterclaims) asserted against the debtor prepetition are not transformed into core proceedings simply because the debtor files for bankruptcy and removes them") (citing several cases so holding, including Bevilacqua v. Bevilacqua, 208 B.R. 11, 16-17 (E.D.N.Y.1997) and Beneficial National Bank USA v. Best Receptions Systems, Inc. (In re Best Reception Systems, Inc.), 220 B.R. 932, 949-50 (Bankr.E.D.Tenn.1998)).
In Lennar Corp. v. Briarwood Capital, LLC, the Defendant/debtors argued that the pre-petition state court action against them should be considered core because it "asserts claims against the Debtor Defendants and the allowance of claims is expressly within the court's core jurisdiction under 28 U.S.C. § 157(b)(2)(B)." 430 B.R. 253, 264 (Bankr.S.D.Fla.2010). The court noted that "[i]f [the state court plaintiff] had filed a proof of claim, this argument has some support in the case law." Id. (citing cases). The court ultimately concluded that "[i]n the absence of a claim, the case law and clear language of the statute compel a finding that the Florida Action was removed and is pending here solely based on `related to' jurisdiction." Id. Similarly, in In re Asousa, the debtor/landlord had initiated a state court suit against a tenant for ejectment and payment of rent. The tenant filed counterclaims against the debtor-landlord based on the debtor-landlord's alleged failure to deliver the premises in a usable condition and failure to make improvements and repairs. The court concluded that the state court action could not be removed to bankruptcy court and treated as a core "objection to claim" proceeding under § 157(b)(2)(B) because the tenant had not filed a proof of claim. 264 B.R. 376, 387.
The Fifth Circuit intimated that the rule is the same in this circuit in Matter of Wood:
The filing of the proof invokes the special rules of bankruptcy concerning objections to the claim, estimation of the claim for allowance purposes, and the rights of the claimant to vote on the proposed distribution. Understood in this sense, a claim filed against the estate is a core proceeding because it could arise only in the context of bankruptcy. Of course, the state-law right underlying the claim could be enforced in a state court proceeding absent the bankruptcy, but the nature of the state *713 proceeding would be different from the nature of the proceeding following the filing of a proof of claim.

Wood v. Wood (In re Wood), 825 F.2d 90, 97 (5th Cir.1987) (emphasis added). Other circuits agree, most notably the Second Circuit. See S.G. Phillips Constructors, Inc. v. City of Burlington (In re S.G. Phillips Constructors, Inc.), 45 F.3d 702, 705 (2d Cir.1995) (stating that "[t]he sole fact that the City's state law claim was filed before [the debtor's] petition has no bearing on whether the claim is characterized as core or non-core when a proof of claim has been filed[,]" and further stating that "we believe that the determinative factor as to the bankruptcy court's jurisdiction in this case is that the City filed a proof of claim resulting in an adversary proceeding that involved the `allowance or disallowance of claims against the estate.' 28 U.S.C. § 157(b)(2)(B). In so doing, the City necessarily became a party under the court's core jurisdiction").
Ultimately, the determination of whether AT & T's counterclaims are core or non-core may be purely an intellectual endeavor. Even if the court concluded that AT & T's counterclaims were core, thus precluding application of mandatory abstention to those counterclaims, retaining the counterclaims in this court would be a pointless exercise, as they have been withdrawn. The court cannot "make" AT & T assert claims against the estate if it chooses not to do so. Nonetheless, for the sake of completeness, the court concludes that AT & T's counterclaims are non-core. With this predicate established, the court can turn to AT & T's request for mandatory abstention.
Mandatory abstention is governed by 28 U.S.C. § 1334(c)(2), which reads:
Upon timely motion of a party in a proceeding based upon a State law claim or State law cause of action, related to a case under title 11 but not arising under title 11 or arising in a case under title 11, with respect to which an action could not have been commenced in a court of the United States absent jurisdiction under this section, the district court shall abstain from hearing such proceeding if an action is commenced, and can be timely adjudicated, in a State forum of appropriate jurisdiction.
28 U.S.C. § 1334(c)(2). Mandatory abstention applies to non-core proceedings. Technomedia Int'l, Inc. v. Twl Skill Ventures, LLC, 2009 WL 7799491, at *1-2, 2009 U.S. Dist. LEXIS 126495, at *3-4 (S.D.Tex.2009). Courts in the Fifth Circuit have interpreted section 1334(c)(2) as involving a five-part test:
Under 28 U.S.C. § 1334(c)(2), a district court must abstain from hearing a proceeding if the following requirements are met: (1) a motion has been timely filed requesting abstention; (2) the cause of action is essentially one that is premised on state law; (3) the proceeding is non-core or related to the bankruptcy case; (4) the proceeding could not otherwise have been commenced in federal court absent the existence of the bankruptcy case; and (5) the proceeding has already been commenced and can be timely adjudicated in a state court forum.
First Bank v. Arafat, 2006 WL 2612746, at *2-3, 2006 U.S. Dist. LEXIS 64562, at *9 (S.D.Tex. Sept. 11, 2006).
Neither party disputed that the first two elements of mandatory abstention have been satisfied: AT & T filed a timely motion requesting mandatory remand/abstention[6] and the underlying suit is entirely *714 premised on state law. LXI argued that mandatory abstention did not apply because its claims against AT & T constituted core proceedings. The court has already found otherwise. LXI also argued (in its pleadings) that mandatory abstention did not apply because the proceeding could have otherwise been commenced in federal court based on federal question jurisdiction. This argument was not addressed at the hearing and the court will not devote a great deal of time to it here save to say that federal question jurisdiction clearly does not exist here. See Budget Prepay, Inc. v. AT&T Corp., 605 F.3d 273, 280 (5th Cir.2010) ("A complaint creates federal question jurisdiction "when it states a cause of action created by state law and (1) a federal right is an essential element of the state claim, (2) interpretation of the federal right is necessary to resolve the case, and (3) the question of federal law is substantial.""). The state court suit could not have been otherwise commenced in federal court absent the bankruptcy case.
The remaining mandatory abstention element to be examined concerns whether the proceeding can be timely adjudicated in the state court. "The party moving for mandatory abstention need not show that the action can be more timely adjudicated in state court, but only that the matter can be timely adjudicated in state court." J.T. Thorpe Co. v. Am. Motorists, 2003 WL 23323005, at *2-3, 2003 U.S. Dist. LEXIS 26016, at *12 (S.D.Tex. 2003). Regarding the burden of proof on the issue of whether a case can be timely adjudicated in state court, the District Court for the Southern District of Texas has stated:
US Fire [the party opposing abstention] correctly cites WRT [Creditors Liquidation Trust, 75 F.Supp.2d 596, 605 (S.D.Tex.1999)], for the proposition that a naked assertion that the matter can be timely adjudicated in the state court, without more is insufficient to satisfy the requirement of mandatory abstention. Id. at 605-606. However, the very next sentence in WRT also points out that `when faced with a motion to remand, it is the defendant's burden to establish the existence of federal jurisdiction over the controversy.' Id. 606. Arguably, the burden may be different where the issue is whether Congress has mandated that the Court not exercise its jurisdiction rather than whether federal jurisdiction exists in the first place. Regardless, the courts that have noted that naked allegations are not sufficient to establish that the matter can be timely adjudicated in a state court have not required much in the way of proof to establish this element when the non-movant failed to present any counter evidence.
*715 J.T. Thorpe Co. v. Am. Motorists, 2003 WL 23323005, at *3, 2003 U.S. Dist. LEXIS 26016, at *13-14 (S.D.Tex.2003) (citations omitted); see also WRT Creditors Liquidation Trust, 75 F.Supp.2d at 606 (finding that movant's evidence that state trial docket was not congested and that trial would likely occur within the next year sufficient to establish timely adjudication where non-movant had failed to provide any evidence negating the likelihood of a timely adjudication in state court). At the hearing AT & T introduced a letter from the state court judge asserting that the parties' dispute could be timely adjudicated in state court.[7] LXI did not present any evidence to the contrary. This court is satisfied that the "timely adjudication" element of mandatory remand/abstention has been satisfied.
In sum, because LXI's state court suit (including AT & T's counterclaims) involves only state law claims that are non-core, because no other basis for federal jurisdiction (other than bankruptcy jurisdiction) exists, and because AT & T has shown that the case can be timely adjudicated in state court, mandatory abstention/remand applies.
The court is reluctant to reward AT & T's blatant forum shopping in this case. AT & T filed a jury demand and refused to consent to a jury trial in this court in an effort to bolster its argument that the parties' dispute could be timely adjudicated in state court: AT & T's refusal to consent to a jury trial here meant that even if the court retained jurisdiction over the parties' dispute, the case would have to be tried in the federal district court, assuring AT & T that it would have a different judge to hear the case. That would also almost certainly mean that the case would not likely be heard for quite some time. Furthermore, it is not entirely clear that the parties' dispute, as it currently stands, involves any factual issues for a jury to decide the request of declaratory relief will not go beyond the terms of the contract itself unless there is ambiguity in the agreement (or unless the contract itself is found to point outside itself for the determination or application of its terms). Thus, AT & T's jury demand machinations appear to be nothing more than an effort to forum shop. Nonetheless, as noted above, the question is not whether the case can be more timely adjudicated in state court than in the bankruptcy or district court; the question is simply whether it *716 can be timely adjudicated in state court. AT & T established that it could be timely adjudicated in state court, and the court's determination to that effect did not depend upon a finding that the case could not be timely adjudicated in the district court. And there is nothing in section 1334(c)(2) that permits a court to deny relief on grounds that the effort is motivated by a desire to forum shop. Indeed, the sad truth is that the structure of bankruptcy jurisdiction actually encourages and rewards forum shopping strategies. There is little this court can about that, other than to encourage Congress to consider the consequences that seem to flow from the current structure.

Conclusion and Order
The court concludes that mandatory abstention applies in this case, and that remand is thus necessary. Accordingly, this adversary proceeding is remanded to state court for ultimate determination of the parties' dispute.
NOTES
[1]  It bears noting that Wood has been grossly misinterpreted over the years as courts have fallen into one of the more elementary of logical fallacies in applying Wood's holding. If "related to" jurisdiction is found, then of course one need look no further for a basis for subject matter jurisdiction. The converse, however, is not true. That is, if "related to" jurisdiction is not found, that does not mean that there can be no bankruptcy subject matter jurisdiction. See In re Simmons, 205 B.R. 834, 841 n. 3 (Bankr.W.D.Tex.1997). A matter might, for example, not be "related to" the bankruptcy case (in the sense of having a conceivable effect on the administration of the estate, the formulation adopted by Wood for "related to" jurisdiction), yet clearly fall within the bankruptcy subject matter jurisdiction of the federal courts, by virtue of either arising under a provision of title 11 (dischargeability actions are an example) or arising in the bankruptcy case (an action to interpret or enforce a sale order post-bankruptcy is an example). See In re Ames Dept. Stores, Inc., 2005 WL 1000263, at *3, 2005 Bankr.LEXIS 786, at *11-13 (Bankr.S.D.N.Y. 2005). To put the fallacy bluntly, to state that all frogs are green does not mean that all green things are frogs.
[2]  The court here is following the route laid out for it by the Fifth Circuit in Wood. There is another approach that could be taken however, one offered up by the Third Circuit in Matter of Seven Fields Development Corp., 505 F.3d 237, 257 n. 18 (3rd Cir.2007). There, the Third Circuit suggested (in the context of evaluating post-confirmation jurisdiction) that a court could first consider whether a matter were core or non-core. See id. ("a finding that the case "aris[es] in" the bankruptcy would "kill two birds with one stone" inasmuch as such a finding conclusively would establish both subject matter jurisdiction and the bankruptcy court's authority to enter final orders. In that situation, there simply would be no reason to engage in the two-step inquiry [used in Resorts International]"). If the matter were found to be core, then the court's inquiry would necessarily be concluded, as all core matters necessarily fall within the court's subject matter jurisdiction. The same inquiry would also answer the mandatory abstention issue presented here.
[3]  Indeed, the bankruptcy court for the Eastern District of Pennsylvania interpreted the Fifth Circuit's decision in In re Prescription Health Care, Inc., as holding that "section 505(a) [] must be restricted solely to those contested matters involving the tax liability of the debtor." In re Plymouth House Health Care Ctr., Inc., 2004 Bankr.LEXIS 2616, at *12 (Bankr.E.D.Pa. Sept. 10, 2004).
[4]  Of course, should LXI wish to seek a determination from this court regarding its own tax liability, LXI remains free to file a separate proceeding under section 505(a)(1) of the Code. Such a proceeding would clearly be core as it would involve a claim "arising under" Title 11. LXI's request for a declaration regarding only AT & T's tax liability, however, should not be decided by this court outside of the context of determining LXI's own liability.
[5]  The Fifth Circuit said that although the language of § 157(b)(2)(O), "`proceedings affecting. . . the estate' is similar in scope to the test of jurisdiction: proceedings having a `conceivable effect on the estate'. We decline, however, to give such a broad reading to subsection 157(b)(2)(O); otherwise, the entire range of proceedings under bankruptcy jurisdiction would fall within the scope of core proceedings, a result contrary to the ostensible purpose of the 1984 Act. That purpose is to conform the bankruptcy statute to the dictates of Marathon." Wood, 825 F.2d at 95.
[6]  In truth, AT & T did not file a pleading entitled "motion to abstain." It filed a motion for remand. Technically, the two forms of relief are differentat least Congress apparently thought they were different, as each has its own separate statute. Abstention is governed by section 1334(c) of title 28, while removal and remand is governed by section 1452 of title 28. It could be argued that AT & T is not entitled to relief under section 1334(c) on grounds that its pleadings do not support that form of relief. However, as this court has observed on other occasions, the courts have chosen to elide abstention and remand, permitting the abstention remedy to be invoked in the context of removal, and essentially ignoring Congress' design as expressed in the statute. See Lozano v. Swift Energy Co. (In re Wright), 231 B.R. 597, 603-04 (Bankr. W.D.Tex. 1999) (renaming the judicially created remedy "mandatory remand"). The court chooses not to try to continue to sweep the waves back into the sea. Accordingly, the court entertains the remedy here as appropriately invoked in the context of a motion to remand, though the court suggests that the better (and fairer) practice is to expressly plead the relief one intends to seek.
[7]  The letter was admitted over the objection of LXI, which claimed the letter was hearsay. AT & T countered that the letter fell within an exception to the hearsay rule, permitting records of governmental activities. See Fed. R.Evid. 803(8). The court agreed, noting that the exception was broadly drafted to include ". . . statements . . . in any form, of public offices . . . setting forth (A) the activities of the office . . ." See id. The letter was authored by the judge presiding over the administration of the jury docket in Bexar County, and set out the dates, as of the date of the letter, that are next available for jury trials in the district courts of Bexar County. While the dates are prospective, they are dates that, as of the date of the letter, remain available for litigants planning their own trial schedules. Thus, the letter is in fact a statement of a public office delineating the docket activity of the state district court for this county. The rule acknowledges the presumed reliability of such statements, coupled with a recognition that the alternative would be to call the officer to testify live at the hearing, imposing an unnecessary cost on the governmental agency. When the agency is a court, there is the added indignity of requiring a sitting judge to testify under oath in another tribunal about routine matters, and to be cross-examined thereon. Such an exercise is disrespectful of the dignity that ought to be accorded fellow members of the judiciary. The court deems such letters a proper means of establishing the "timely adjudicate" element of mandatory abstention, and believes them to be properly admissible under Rule 803(8) of the Federal Rules of Evidence.


Police in D.C. have arrested 26 men in a park for seeking sex with other men in the past year as federal police started what may be an undercover anti-gay sex sting operation.

Sergeant Eduardo Delgado of the U.S. Park Police told the Washington Blade that the arrests started on August 7, 2018, and resulted in charges of Disorderly Conduct, Lewd Acts, Unlawful Entry, and Simple Assault (Sexual).

While Delgado said he didn’t know whether the arresting officers were in plainclothes or uniformed, one defense attorney said that the entire operation is “reminiscent of the Stonewall days.”

John Albanes is a lawyer who knows several of the attorneys representing some of the men who were arrested in the park.

Related: Judge dismisses charges in a gay sex sting because a private room isn’t a ‘public place’

“I am on a D.C. Superior Court trial lawyers association listserv and recently several criminal defense attorneys on the email list have mentioned that they have had criminal cases involving essentially the same set of facts,” he said.

“Undercover plain-clothes Park Police officers entice men in Meridian Hill Park for purportedly consensual sexual activity and then proceed to arrest their targets for a crime (often misdemeanor sexual abuse).”

Misdemeanor sexual abuse in D.C. law requires that a sexual act be performed on another person “without that other person’s permission.”

“The officers are posing as willing participants in a consensual encounter between adults,” Albanes said. “The target is deceived into thinking that what he is about to do is wanted. This raises serious doubts about whether the government can prove criminal intent.”

Delgado said that the police are responding to complaints about lewd activity, and that plain clothes officers are a legitimate way of enforcing the law. He did not say whether those officers are saying they consent to sexual acts with gay and bi men and then arresting them for sexual assault.

Lou Chibbaro Jr. at the Washington Blade wrote that Meridian Hill Park has been known as a cruising area for the past 50 years for mostly Black men.

In the past decade, many municipalities have abandoned their anti-gay sex sting operations in favor of uniformed officers and better lighting. That, coupled with the popularity of cruising apps like Grindr, have made these sorts of stings seem like things of the past.


Eccentric muscle damage transiently decreases rat skeletal muscle GLUT-4 protein.
The effects of concentric and muscle-damaging eccentric contractions on muscle glucose transporter GLUT-4 content were studied in rat muscles. Rats were anesthetized, the calf muscles on one side were stimulated electrically for concentric or eccentric contractions, and bilateral calf muscles were obtained in the postexercise period. Inflammatory and phagocytic cells accumulated in the eccentric white and red gastrocnemius muscles, whereas there were only discrete changes in the eccentric soleus. Glycogen was depleted to the same extent in the white and red gastrocnemius muscles after both types of stimulation, and it remained decreased > 2 days in eccentric muscles. The total GLUT-4 protein content was decreased in the eccentric white and red gastrocnemius muscles 1 and 2 days after the eccentric stimulation, whereas the maximal activity of glycogen synthase was unaffected at these time points. In conclusion, our one-legged stimulation model caused eccentric muscle damage in the white and red gastrocnemius, whereas only minor damage was observed in the soleus muscle. In damaged muscle, muscle glycogen and GLUT-4 protein content were decreased for > 2 days. These findings may suggest (but do not prove) that decreased muscle GLUT-4 protein is involved in the delayed glycogen resynthesis after eccentric exercise.


Q:

MongoDB replica set in Azure, where do I point the firewall?

I have a mongoDB replica set in azure
I have:
server1 Primary
server2 secondary
server3 Arbiter
I have a dev environment on my local machine that I want to point to this mongoDB instance
What do I open on my Azure Firewall to make sure this configuration is setup with best practices.
Do I create a load balanced endpoint to the Primary and Secondary or do I create a single endpoint to the arbiter, or perhaps even something else?
thanks!

A:

MongoDB will not play well with a load-balanced endpoint (as you might end up sending traffic to a secondary, and you'd have no control over this unless you implemented a custom probe for each VM, and then you'd need to update the probe's status based on the replicaset node's health, for each node). The MongoDB client-side driver is designed to work with a replicaset's topology to make the correct decision on which node to communicate with. Each replicaset node should have a discrete addressable ip:port. If you have all your instances in a single cloud service (e.g. myservice.cloudapp.net) then you'll need one port per instance (since they'd all share a single ip address). If each instance is in a different cloud service, then you can have the same port for each, with different dns name / ip address for each.


Sildenafil for treatment of erectile dysfunction in men with diabetes: a randomized controlled trial. Sildenafil Diabetes Study Group.
Erectile dysfunction is common in men with diabetes. To assess the efficacy and safety of oral sildenafil citrate in the treatment of erectile dysfunction in men with diabetes. A multicenter, randomized, double-blind, placebo-controlled, flexible dose-escalation study conducted May through November 1996. Patients' homes and 19 clinical practice centers in the United States. A total of 268 men (mean age, 57 years) with erectile dysfunction (mean duration, 5.6 years) and diabetes (mean duration, 12 years). Patients were randomized to receive sildenafil (n = 136) or placebo (n = 132) as needed, but not more than once daily, for 12 weeks. Patients took the study drug or placebo 1 hour before anticipated sexual activity. The starting dose of sildenafil citrate was 50 mg, with the option to adjust the dose to 100 mg or 25 mg based on efficacy and tolerability, to be taken as needed. Self-reported ability to achieve and maintain an erection for sexual intercourse according to the International Index of Erectile Function and adverse events. Two hundred fifty-two patients (94%) completed the study (131/136 in the sildenafil group, 121/132 in the placebo group). By intention-to-treat analysis, at 12 weeks, 74 (56%) of 131 patients in the sildenafil group reported improved erections compared with 13 (10%) of 127 patients in the placebo group (P<.001). The proportion of men with at least 1 successful attempt at sexual intercourse was 61 % (71/ 117) for the sildenafil group vs 22% (25/114) for the placebo group (P<.001). Adverse events related to treatment were reported for 22 (16%) of 136 patients taking sildenafil and 1 (1%) of 132 patients receiving placebo. The most common adverse events were headache (11% sildenafil, 2% placebo), dyspepsia (9% sildenafil, 0% placebo), and respiratory tract disorder (6% sildenafil, 2% placebo), predominantly sinus congestion or drainage. The incidence of cardiovascular adverse events was comparable for both groups (3% sildenafil, 5% placebo). Oral sildenafil is an effective and well-tolerated treatment for erectile dysfunction in men with diabetes.


The rapid accumulation of genome sequences and protein structures during the last decade has been paralleled by major advances in sequence database search methods. The powerful Position-Specific Iterating BLAST (PSI-BLAST) method developed at the NCBI formed the basis of our work on protein motif analysis. In addition, Hidden Markov Models (HMM) and protein structure comparison methods were applied. During the last year, we made further progress in detailed analysis of the classification, evolution, and functions of several classes of proteins. In particular, we studied in detail the protein domains that are involved in prokaryotic toxin-antitoxin cassettes and in systems of defense against selfish elements. We proposed previously that the group of so-called Cas proteins comprise a novel DNA repair system. The association of the cas genes with CRISPR and, especially, the presence, in CRISPR units, of unique inserts homologous to phage and plasmid genes made to modify this hypothesis. It appears most likely that CASS is a prokaryotic system of defense against phages and plasmids that functions via the RNAi mechanism. The functioning of this system seems to involve integration of fragments of foreign genes into archaeal and bacterial chromosomes yielding heritable immunity to the respective agents. However, it appears that this inheritance is extremely unstable on the evolutionary scale such that the repertoires of unique psiRNAs are completely replaced even in closely related prokaryotes, presumably, in response to rapidly changing repertoires of dominant phages and plasmids. Our work on the cas system has stimulated exprimental research, and the proposed mechanism has already received partial experimental validation. We also used computational methods to identify a novel toxin-antitoxin system that is predicted to function via RNA binding or cleavage. In addition, we explored mechanisms of protein innovation in eukaryotes, in particular, the patterns of evolution of vairous classes of multidomain proteins.


Q:

how to print lines in a txt which fulfills certain condition with python?

def palindrome_filter(file_name):
    file=open('text_1.txt','r')
    for line in file:
        line=line.rstrip()
        if (is_palindrome(line)):
            print(line)
    file.close()
palindrome_filter('text_1.txt')

Above are the codes that I wrote. I actually want python to print the certain line which is a palindrome, but it keeps printing true or false instead. I wonder what's wrong with my code. (function to determine whether a line is palindrome is texted, it is correct.)

A:

Your solution might be:
def palindrome_filter(file_name):
    file=open('text_1.txt','r')
    for line in file:
        line = line.rstrip()
        if line == line[::-1]:
            print(line)
    file.close()


[Transpalpebral measurement of axial eye length. Use of contact B-scan sonography].
In ophthalmology, it is very often necessary to determine the axial eye length. When standard measuring techniques fail, B-scan sonography may be used. However, coupling problems inhibit exact measurement. The aim of this study was to counter these problems. Correction values were created for the ultrasonic devices (1) Master-Vu (Sonomed), (2) CineScan (Quantel Medical), and (3) System-ABD (Innovative Imaging), including the position of the coupling layer of the hand pieces and the lid thickness. For evaluation of the method, the axial eye lengths of 35 eyes were measured transpalpebrally. These data were compared to those from the (4) IOL Master (Carl Zeiss Meditec). The usefulness of the developed method was shown by two patients. The correction values were (1) 3.0 mm, (2) 1.5 mm, and (3) 1.5 mm. The medial aberrations to (4) were (1) 0.4+/-0.5 mm, (2) 0.9+/-0.7 mm, and (3) 0.2+/-0.7 mm. The introduced method enables transpalpebral eye length measurement and is also applicable in cases of missing compliance or in eyes with an obfuscated optical medium.


Q:

Error creating bean with name 'transactionManager': Cannot resolve reference to bean ''sessionFactory'' while setting bean property 'sessionFactory'

i'm with this error and i can't find the solution
I'm using postgres with Grails
Here's the error that keeps occurring
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManagerPostProcessor': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is org.hibernate.MappingException: Could not instantiate id generator [entity-name=beans.AbsPessoa]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
    at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:207)
    at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:687)
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:523)
    at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118)
    at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:766)
    at org.springframework.boot.SpringApplication.createAndRefreshContext(SpringApplication.java:361)
    at org.springframework.boot.SpringApplication.run(SpringApplication.java:307)
    at grails.boot.GrailsApp.run(GrailsApp.groovy:55)
    at grails.boot.GrailsApp.run(GrailsApp.groovy:374)
    at grails.boot.GrailsApp.run(GrailsApp.groovy:363)
    at grails.boot.GrailsApp$run.call(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133)
    at trabalhoestagio.Application.main(Application.groovy:8)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is org.hibernate.MappingException: Could not instantiate id generator [entity-name=beans.AbsPessoa]
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:359)
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:108)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1481)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1226)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:543)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
    at org.grails.transaction.TransactionManagerPostProcessor.initialize(TransactionManagerPostProcessor.java:75)
    at org.grails.transaction.TransactionManagerPostProcessor.setBeanFactory(TransactionManagerPostProcessor.java:53)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeAwareMethods(AbstractAutowireCapableBeanFactory.java:1597)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1565)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
    ... 20 common frames omitted
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Invocation of init method failed; nested exception is org.hibernate.MappingException: Could not instantiate id generator [entity-name=beans.AbsPessoa]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
    at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:351)
    ... 34 common frames omitted
Caused by: org.hibernate.MappingException: Could not instantiate id generator [entity-name=beans.AbsPessoa]
    at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.createIdentifierGenerator(DefaultIdentifierGeneratorFactory.java:123)
    at org.hibernate.mapping.SimpleValue.createIdentifierGenerator(SimpleValue.java:225)
    at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:323)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1859)
    at org.grails.orm.hibernate.cfg.HibernateMappingContextConfiguration.buildSessionFactory(HibernateMappingContextConfiguration.java:196)
    at org.grails.orm.hibernate.HibernateMappingContextSessionFactoryBean.doBuildSessionFactory(HibernateMappingContextSessionFactoryBean.java:476)
    at org.grails.orm.hibernate.HibernateMappingContextSessionFactoryBean.buildSessionFactory(HibernateMappingContextSessionFactoryBean.java:470)
    at org.grails.orm.hibernate.HibernateMappingContextSessionFactoryBean.afterPropertiesSet(HibernateMappingContextSessionFactoryBean.java:93)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
    ... 41 common frames omitted
Caused by: java.lang.ClassCastException: org.grails.config.NavigableMap$NullSafeNavigator cannot be cast to java.lang.Boolean
    at net.kaleidos.hibernate.PostgresqlExtensionsDialect$TableNameSequenceGenerator.configure(PostgresqlExtensionsDialect.java:60)
    at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.createIdentifierGenerator(DefaultIdentifierGeneratorFactory.java:117)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':bootRun'.
> Process 'command 'C:\Program Files\Java\jdk1.8.0_91\bin\java.exe'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
    ... 50 common frames omitted
Error |
Failed to start server (Use --stacktrace to see the full trace)

Here's my build.gladle
buildscript {
    ext {
        grailsVersion = project.grailsVersion
    }
    repositories {
        mavenLocal()
        maven { url "https://repo.grails.org/grails/core" }
    }
    dependencies {
        classpath "org.grails:grails-gradle-plugin:$grailsVersion"
        classpath "com.bertramlabs.plugins:asset-pipeline-gradle:2.8.2"
        classpath "org.grails.plugins:hibernate4:5.0.5"
    }
}

version "0.1"
group "trabalhoestagio"

apply plugin:"eclipse"
apply plugin:"idea"
apply plugin:"war"
apply plugin:"org.grails.grails-web"
apply plugin:"org.grails.grails-gsp"
apply plugin:"asset-pipeline"

ext {
    grailsVersion = project.grailsVersion
    gradleWrapperVersion = project.gradleWrapperVersion
}

repositories {
    jcenter()
    mavenLocal()
    maven { url "https://repo.grails.org/grails/core" }
}

dependencyManagement {
    imports {
        mavenBom "org.grails:grails-bom:$grailsVersion"
    }
    applyMavenExclusions false
}

dependencies {
    compile "org.springframework.boot:spring-boot-starter-logging"
    compile "org.springframework.boot:spring-boot-autoconfigure"
    compile "org.grails:grails-core"
    compile "org.springframework.boot:spring-boot-starter-actuator"
    compile "org.springframework.boot:spring-boot-starter-tomcat"
    compile "org.grails:grails-dependencies"
    compile "org.grails:grails-web-boot"
    compile "org.grails.plugins:cache"
    compile "org.grails.plugins:scaffolding"
    compile "org.grails.plugins:hibernate4"
    compile "org.hibernate:hibernate-ehcache"
    console "org.grails:grails-console"
    profile "org.grails.profiles:web:3.1.6"
    runtime "com.bertramlabs.plugins:asset-pipeline-grails:2.8.2"
    runtime "com.h2database:h2"
    testCompile "org.grails:grails-plugin-testing"
    testCompile "org.grails.plugins:geb"
    testRuntime "org.seleniumhq.selenium:selenium-htmlunit-driver:2.47.1"
    testRuntime "net.sourceforge.htmlunit:htmlunit:2.18"
    compile 'org.grails.plugins:postgresql-extensions:4.6.1'
    provided 'org.postgresql:postgresql:9.4-1203-jdbc4'
}

task wrapper(type: Wrapper) {
    gradleVersion = gradleWrapperVersion
}

assets {
    minifyJs = true
    minifyCss = true
}

And this is my Application.yml
 hibernate:
        dialect: net.kaleidos.hibernate.PostgresqlExtensionsDialect
        cache:
            queries: false
            use_second_level_cache: true
            use_query_cache: false
            region.factory_class: 'org.hibernate.cache.ehcache.EhCacheRegionFactory'

    dataSource:
        pooled: true
        jmxExport: true
        driverClassName: org.postgresql.Driver
        username: postgres
        password: password
        url: jdbc:postgresql://localhost:5432/trabalho
        dbCreate: update

    environments:
        development:
            dataSource:
                dbCreate: create-drop
                url: jdbc:postgresql://localhost:5432/trabalho
        test:
            dataSource:
                dbCreate: update
                url: jdbc:postgresql://localhost:5432/trabalho
        production:
            dataSource:
                dbCreate: update
                url: jdbc:postgresql://localhost:5432/trabalho
                properties:
                    jmxEnabled: true
                    initialSize: 5
                    maxActive: 50
                    minIdle: 5
                    maxIdle: 25
                    maxWait: 10000
                    maxAge: 600000
                    timeBetweenEvictionRunsMillis: 5000
                    minEvictableIdleTimeMillis: 60000
                    validationQuery: SELECT 1
                    validationQueryTimeout: 3
                    validationInterval: 15000
                    testOnBorrow: true
                    testWhileIdle: true
                    testOnReturn: false
                    jdbcInterceptors: ConnectionState
                    defaultTransactionIsolation: 2 # TRANSACTION_READ_COMMITTED

    ---
    ---
    grails:
        profile: web
        codegen:
            defaultPackage: trabalhoestagio
        spring:
            transactionManagement:
                proxies: false
    info:
        app:
            name: '@info.app.name@'
            version: '@info.app.version@'
            grailsVersion: '@info.app.grailsVersion@'
    spring:

        groovy:
            template:
                check-template-location: false

    ---
    grails:
        mime:
            disable:
                accept:
                    header:
                        userAgents:
                            - Gecko
                            - WebKit
                            - Presto
                            - Trident
            types:
                all: '*/*'
                atom: application/atom+xml
                css: text/css
                csv: text/csv
                form: application/x-www-form-urlencoded
                html:
                  - text/html
                  - application/xhtml+xml
                js: text/javascript
                json:
                  - application/json
                  - text/json
                multipartForm: multipart/form-data
                pdf: application/pdf
                rss: application/rss+xml
                text: text/plain
                hal:
                  - application/hal+json
                  - application/hal+xml
                xml:
                  - text/xml
                  - application/xml
        urlmapping:
            cache:
                maxsize: 1000
        controllers:
            defaultScope: singleton
        converters:
            encoding: UTF-8
        views:
            default:
                codec: html
            gsp:
                encoding: UTF-8
                htmlcodec: xml
                codecs:
                    expression: html
                    scriptlets: html
                    taglib: none
                    staticparts: none
    endpoints:
        jmx:
            unique-names: true

A:

From your log:
Caused by: java.lang.ClassCastException: org.grails.config.NavigableMap$NullSafeNavigator.....

seems related to: grails-postgresql-extensions plugin
According to:
https://github.com/kaleidos/grails-postgresql-extensions/issues/84
problem was fixed in version: 4.6.5 and you are using: 4.6.1
Hope it helps