Tag: 上海品茶夜网

Moody’s downgrades Contura Energy, says outlook remains negative

first_img FacebookTwitterLinkedInEmailPrint分享S&P Global Market Intelligence ($):Moody’s downgraded Contura Energy Inc.’s corporate family rating to B3 from B2 and revised its outlook on the company to negative from stable, saying it expects Contura will experience significant margin compression in 2020 as a result of decreased metallurgical coal prices and higher cash burn.The rating agency also lowered the NYSE-listed coal miner’s senior secured term loan rating to Caa1 from B3, and its speculative grade liquidity rating to SGL-3 from SGL-2, in a Feb. 27 note.Moody’s estimated Contura Energy’s “management-defined” EBITDA would fall to a range of about $125 million to $175 million in 2020, compared to $335 million in 2018 and $264 million for the first nine months of 2019.Contura Energy’s thermal coal platform will likely generate modest losses in 2020 as the company also faces potential headwinds due to variations in metallurgical coal prices, while the negative outlook also reflects expectations for cash consumption in 2020, Moody’s said.“An increasing portion of the global investment community is reducing or eliminating exposure to the coal industry with greater emphasis on moving away from thermal coal,” Moody’s said.Moody’s said it expects 2020 to be very challenging for the coal industry due to lower domestic demand for thermal coal and substantive reductions in export prices, amid increasing difficulty in accessing capital early in the year as investors increase focus on the industry’s environmental, social and governance profile.[Robert Vergara]More ($): Moody’s revises outlook on Contura Energy to negative from stable Moody’s downgrades Contura Energy, says outlook remains negativelast_img read more

‘FishMS’ service a hit in SA

first_img10 July 2007The Southern African Sustainable Seafood Initiative (SASSI) has successfully turned to technology to help preserve the country’s many fish species, with its FishMS service informing users of which species are in plentiful supply, endangered or illegal to buy.“The instant access to accurate information and an informed choice has struck a chord with South Africa’s seafood lovers and cellphone users,” SASSI spokesperson Timony Siebert told the South African Press Agency (Sapa) this week.He told the agency that more than 3 000 people had made more than 11 000 enquiries since the service was introduced last December.Users can SMS the name of the fish in question to 079 499 8795 and a reply by the service will confirm if the fish is in plentiful supply, endangered or illegal to buy.Siebert told SAinfo that the service was funded and developed from “home-grown” technology by iVeri Payment Technologies, who also manage the system, as part of their contribution to the SASSI.“They thought it would be a novel and fun way to help champion the SASSI cause,” Siebert said.Siebert said that it took about 8 weeks to develop and another month of “fine tuning and beta testing” before the service went live, and was promoted “mostly through print media and then spin-offs from radio interviews, internet, word of mouth and SASSI networking partners”.The SASSI has already released a downloadable pocket guide and booklet as well as online database for seafood lovers, which separates fish species into three lists:Green – These species have well-managed populations that can sustain current fishing pressure, and are recommended as the most sustainable choices available. Orange – Though registered commercial fishers and retailers may legally sell these species, an increase in demand could compromise a sustainable supply. Red – These are species that are illegal to buy or sell in South Africa according to the Marine Living Resources Act. Some of these are recreational species that can be caught for ones own enjoyment, subject to the possession of a valid recreational fishing permit as well as other restrictions.Sapa reported that the highest number of queries for a single species was for the Kingklip, which is on the orange list, with 744 enquiries, while the most queries for a fish on the red list was for the Galjoen with 333 enquiries.“SMSs to the FishMS service are charged at normal cellphone rates,” Siebert told SAinfo.SouthAfrica.info reporter Want to use this article in your publication or on your website?See: Using SAinfo materiallast_img read more

Putting the stamp on the World Cup

first_imgThe green-haired leopard Zakumi. The round set of stamps depicting the trophy, the match ball and the 2010 Fifa World Cup logo. A colourful commemorative cover..(Images: South African Post Office) MEDIA CONTACTS • Johan van WykSenior manager, Philatelic Services, Sapo+27 12 845 2901 or +27 82 557 4242RELATED ARTICLES • Coining it for Madiba’s 90th • SA items in World Digital Library • Exciting start to World Cup • Meet Zakumi: the 2010 mascotJanine ErasmusThe South African Post Office (Sapo) has released a series of colourful commemorative stamps and covers to mark the 2010 Fifa World Cup. The stamps were issued on 11 June, the opening day of the football extravaganza.Football lovers and philatelists will be able to buy the two sheets and two envelopes until 31 December – or as long as stocks last.Sapo’s senior manager of Philatelic Services Johan van Wyk said that the new releases are not related to the World Cup stamp set issued jointly by nine of the 14 member countries of the South African Development Community in April.“As far as we know, we are the only country in the region to issue its own World Cup stamps,” he said.The release comes after negotiations with Fifa, and subsequent approval by the world football governing body.Both stamp sheets were designed by Philatelic Services’ inhouse graphic designer Thea Clemons, who is responsible for the blind-friendly taxi signal stamps launched in March, among other notable releases,The smallest ambassadorsAn initial quantity of 500 000 of each stamp sheet has been printed. The first sheet carries six self-adhesive stamps, while the second features 10.The first set is round in shape, with a football as background. The stamps depict the 18-carat gold Fifa World Cup trophy, the official logo, and the Jabulani, the official match ball.The second series depicts Zakumi, the green-haired official mascot of the World Cup, in five activities such as flying the flag, playing football, and cheering – for the home team Bafana Bafana, naturally.The colourful envelopes contain an information card which gives the background to the stamp series and World Cup logo, and more. The envelopes are franked with a special football stamp bearing the date of issue.Orders from post offices around the country are flying in, according to Van Wyk. “We are only just managing to keep up. Even on [the public holiday] 16 June the guys worked overtime to handle the demand.”Although South Africans have anticipated the World Cup for six years, the volume of national sales has surprised even the Post Office staff, said Van Wyk.“We’re also focusing on tourism offices and post offices in major tourist drawcards such as the V&A Waterfront in Cape Town, and Skukuza in the Kruger National Park, to ensure they always have stock available.”The new releases are an inexpensive souvenir of the long-awaited sporting event. “We think of stamps as the smallest ambassadors of our country,” said Van Wyk.Stamping its presenceSouth Africa’s profile amongst the global philatelic community is to receive a boost later in 2010 when Johannesburg hosts the Joburg 2010 International Stamp Show.The event takes place at the Sandton Convention Centre between 27 and 31 October, under the auspices of the Federation of Inter-Asian Philately, to which South Africa is affiliated.  It is sponsored by Sapo and the Philatelic Foundation of South Africa.The date coincides with the printing of the first stamp by the Union of South Africa in 1910. The death of King Edward VII prevented the release of the original stamp, but his successor, King George V, was portrayed on a stamp later in the year, released to commemorate the opening of the new Parliament.With recognition from world philately governing body Fédération Internationale de Philatélie, the Joburg event is the first internationally-recognised stamp show to take place in South Africa since Ilsapex 98, held 12 years ago at Gallagher Estate in Midrand.To date 39 countries have confirmed their attendance, said Van Wyk, and more are expected. Local and international philatelists and dealers are said to be looking forward to the event, which will cover around 5 800 square metres of space.Besides the competitive exhibition and many contemporary designs on show, a selection from Queen Elizabeth II’s own collection will also be on view. Her Majesty has personally approved the appearance of the stamps, which will be brought to South Africa by the Keeper of the Royal Collection. Stamps from the royal collection were also exhibited at Ilsapex 98.Sapo will issue its eighth definitive stamp series at the event.last_img read more

Learn the The Art of Hollywood Storytelling

first_imgPolish your script and learn the secrets of Hollywood storytelling from three professional story consultants.I recently stumbled onto this vast archive of interviews with filmmakers who work in positions that you don’t often get access to. There are interviews (broken up into handily titled sections) with storyboard artists, script consultants, production managers, focus pullers, compositors, and many more. Unfortunately for me, as a non-Swedish speaker, most of the interviews are in the participants native language, which I believe is Swedish!That said, I’ve pulled out this trio of interviews with three professional story consultants and script doctors, all speaking in English, who have great insight to share on improving your storytelling and filmmaking abilities.Script and Story ConsultantsChris Soth, Michael Hauge and Linda Seger are all story consultants. This means they’ve been called in to help filmmakers like Will Smith on I Am Legend, Hancock, and The Karate Kid, or Ron Howard on (apparently) every one of his movies since Apollo 13, to help restructure the film and ensure the character arcs and motivations are working as well as they can.“Story is the most important thing, everything comes after. and if you’re serious about being a filmmaker, and that means being serious about being a storyteller you have to understand structure.” – Chris SothLinda Segar’s bestselling book How to Make a Good Script Great, is personally endorsed by Ron Howard, and after working on over 2000 scripts and a 30+ year career, she certainly knows her stuff. In this video, Linda shares her thoughts on the best way to make it as a writer, which sadly, involves no short cuts.Writers write. you need to get writing and you need to get a number of scripts written. Rarely do you sell your first script. Sometimes in the US people say you need to write at least five scripts, and spend at least five years learning the craft. And then maybe, you’ll sell it, or get an agent or have something happen with it… it’s learning the art in yourself and bringing that out and learning the craft.Michael Hauge, who can be found on Story Mastery.com, shares some elementary advice for the things writers need to do to write their first script well.One of the things I recommend that writers do, that sometimes are either too obvious, or writers don’t think of it. Number one, you gotta read screenplays. I encouter a lot of people who hire me to consultant on their screenplay and pay a lot of money to do that, and I’ll say ‘Well how many scripts have you read.’ and they’ll say ‘Well, I’ve read three.’ And it’s like, you can’t possibly master a craft when you’ve only seen three examples of it being done.A fantastic resource for script writers (that gives you over four hundred examples of different ways of approaching screenwriting elements) is the Mentorless series of script breakdowns, How Did They Write That. Essentially you can see how the writer achieved various things from introducing a character, or writing an action scene, or a phone call, or a description of a character and much more.It’s a brilliant way to quickly see how numerous professional screenwriters approach the task in their own style.The Art of the StoryboardAs an added bonus, there is also this extended interview with storyboard artist Giuseppe Cristiano on how he approaches his storyboard art work and craft. In this first video you get a tour of the tools Cristiano likes to work with and pick up this handy tip…You’ll notice that I use a red pencil [for the initial sketch], and that’s something that you use in animation, so that you can do your clean up in pen, and scan them in you can remove the red pencil [digitally].You can check out more of Cristiano’s storyboards on his site.What resources do you use for pre-production? Share in the comments below.last_img read more

Bursars Urged to Uphold Professional Standards

first_imgMONTEGO BAY – Newly installed President of the Caribbean Bursars’ Association, Valerie Facey, has charged her membership to always uphold the highest standards of professional integrity. Delivering her address at Thursday’s (Nov.  22)  closing session of the association’s conference held at the Hilton Rose Hall Hotel in St. James, Mrs. Facey told the school financial officers that issues related to compensation should not allow them to lose focus or compromise their professional responsibilities and ethics. “Our delivery should be of the highest standard. It is our obligation to carry out our duties with the utmost transparency, competence and professionalism… not to bring the profession into disrepute, but strive to raise the bar to another level. Let our stakeholders and by extension, the nation, become aware that the job we have been entrusted to carry out is in safe and capable hands,” Miss Facey stated. She told the members that the association will continue to protect their welfare, and to strengthen their skills through training. President of the Principals and Vice Principals Association, Pauline Reid, encouraged the bursars to continue striving for professional development and to encourage team engagement at schools. “Whatever you do ultimately, you are impacting lives, and team members make schools successful. We must aim to create the level of synergy so that together, all persons within the school will support the school’s mission, and seek to achieve ongoing school improvement,” she stated. She noted further that “to ensure an effective system, you must all seek to work in tandem with your school leaders so that together, we can provide opportunities for our students to reach their fullest potential.” The three-day conference, which ended on Friday (Nov. 23)  was held under the theme: ‘School Business Managers Surviving Today’s Challenges-Meeting Tomorrow’s Needs’.last_img read more

NTPC to bring down coal import bill to nil in 5 years

first_imgState-run NTPC is looking at bringing its coal import bill to ‘zero’ in the next five years and will rely on the fossil fuel made available by Coal India and the company’s own mines.The power major is one of the country’s largest consumers of coal. “Our aim is to have zero import of coal, and manage with the coal from Coal India sources or our own mines,” NTPC CMD Arup Roy Choudhury told PTI in an interview.When asked about the timeframe in which the PSU plans to have nil coal imports, Choudhury said, “You can say in the next five years.” NTPC ventured into coal mining as part of its backward integration process for fuel security. The company has been allotted 10 coal blocks including Chatti-Bariatu, Chatti-Bariatu (South) and Kerandari in Jharkhand, Dulanga in Odisha and Talaipalli in Chhattisgarh. Its another block — Pakri-Barwadih — in Jharkhand is likely to commence coal production by the end of this calender year and the remaining mines subsequently. “Pakri-Barwadih will come this year (2015) and others later,” Choudhury said. NTPC imported close to 16 million tonnes (MT) of coal in the just-concluded fiscal compared to 10 MT in 2013-14. Meanwhile, the PSU, which is also the country’s largest power producer, is establishing 4,000 MW imported coal-based thermal power plant at Visakhapatnam district in Andhra Pradesh at an investment of about Rs 20,000 crore. NTPC’s present installed capacity is 44,398 MW comprising 39 generating stations.last_img read more

A literary treat for Delhiites

first_imgCome February, Delhi will once again witness some of the most creative writers of our times, sharing their most interesting experiences. Delhi Literature Festival, which is entering into the seventh edition this year, will be held from February 8 – 10, 1 pm to 8 pm, at Dilli Haat. The festival was started in the year 2013, with the objective of inculcating good old habit of book reading and promoting tourism.In the past years, it has witnessed active participation from popular authors and writers including Ashok Bajpai, Ashok Chakradhar, Ankit Lal, Ashwin Sanghi, Anna Vetticad, Ashish Chaudhary, Blossom Kochhar, Christopher Doyle, Rakhshanda Jalil, Ravinder Singh, Munawwar Rana, Shashi Tharoor, Mani Shankar Aiyar, amongst others. Also Read – Add new books to your shelfProminent publishers including Ajay Mago – Om Books International, Swati Daftuer – Commissioning Editor Harper Collins, Milee Ashwarya, Editor-in-Chief Penguin Random House and Simran Khara, CEO Juggernaut have actively participated at the Delhi Literature Festival. This year, the literary extravaganza will be officially supported by Department of Art, Culture and Language, Government of NCT of Delhi, Hindi Academy and Sahitya Kala Parishad. The organisers have closely worked with all the leading book publishers. Also Read – Over 2 hours screen time daily will make your kids impulsiveThe seventh edition is expected to be bigger and more exciting with leading authors including Amit Lodha, Novoneel Chakraborty, Ravinder Singh, Madhavi Menon, Ruskin Bond, Pallavi Kamakshi Rebbapragada, Jonathan Gil Harris, Dr Shashi Tharoor, Prasoon Joshi, Manoj Muntashir, S Y Quraishi, Rajdeep Sardesai, Vir Sanghvi, Purushottam Agrawal, Malashri Lal,Dr Mridula Tandon, Moein Shadad, Tarkash Pradeep, Taruna Mishra, Meenakshi Jijivisha, Irshad Khan Sikandar, Valay Singh, Victor Kalyan Ghose being lined up.last_img read more

GitHub October 21st outage RCA How prioritizing data integrity launched a series

first_imgYesterday, GitHub posted the root-cause analysis of its outage that took place on 21st October. The outage started at 23:00 UTC on 21st October and left the site broken until 23:00 UTC, 22nd October. Although the backend git services were up and running during the outage, multiple internal systems were affected. Users were unable to log in, submit Gists or bug reports, outdated files were being served, branches went missing, and so forth. Moreover, GitHub couldn’t serve webhook events or build and publish GitHub Pages sites. “At 22:52 UTC on October 21, routine maintenance work to replace failing 100G optical equipment resulted in the loss of connectivity between our US East Coast network hub and our primary US East Coast data center. Connectivity between these locations was restored in 43 seconds, but this brief outage triggered a chain of events that led to 24 hours and 11 minutes of service degradation” mentioned the GitHub team. GitHub uses MySQL to store GitHub metadata. It operates multiple MySQL clusters of different sizes. Each cluster consists of up to dozens of read replicas that help GitHub store non-Git metadata. These clusters are how GitHub’s applications are able to provide pull requests and issues, manage authentication, coordinate background processing, and serve additional functionality beyond raw Git object storage. For improved performance, GitHub applications direct writes to the relevant primary for each cluster, but delegate read requests to a subset of replica servers. Orchestrator is used to managing the GitHub’s MySQL cluster topologies. It also handles automated failover. Orchestrator considers a number of factors during this process and is built on top of Raft for consensus. In some cases, Orchestrator implements topologies that the applications are unable to support, which is why it is very crucial to align Orchestrator configuration with application-level expectations. Here’s a timeline of the events that took place on 21st October leading to the Outage 22:52 UTC, 21st Oct Orchestrator began a process of leadership deselection as per the Raft consensus. After the Orchestrator managed to organize the US West Coast database cluster topologies and the connectivity got restored, write traffic started directing to the new primaries in the West Coast site. The database servers in the US East Coast data center contained writes that had not been replicated to the US West Coast facility. Due to this, the database clusters in both the data centers included writes that were not present in the other data center. This is why the GitHub team was unable to failover (a procedure via which a system automatically transfers control to a duplicate system on detecting failures) the primaries back over to the US East Coast data center safely. 22:54 UTC, 21st Oct GitHub’s internal monitoring systems began to generate alerts indicating that the systems are undergoing numerous faults. By 23:02 UTC, GitHub engineers found out that the topologies for numerous database clusters were in an unexpected state. Later, Orchestrator API displayed a database replication topology including the servers only from the US West Coast data center. 23:07 UTC, 21st Oct The responding team then manually locked the deployment tooling to prevent any additional changes from being introduced. At 23:09 UTC, the site was placed into yellow status. At 23:11 UTC, the incident coordinator changed the site status to red. 23:13 UTC, 21st Oct As the issue had affected multiple clusters, additional engineers from GitHub’s database engineering team started investigating the current state. This was to determine the actions that should be taken to manually configure a US East Coast database as the primary for each cluster and rebuild the replication topology. This was quite tough as the West Coast database cluster had ingested writes from GitHub’s application tier for nearly 40 minutes. To preserve this data, engineers decided that 30+ minutes of data written to the US West Coast data center. This prevented them from considering options other than failing-forward in order to keep the user data safe. So, they further extended the outage to ensure the consistency of the user’s data. 23:19 UTC, 21st Oct After querying the state of the database clusters, GitHub stopped running jobs that write metadata about things such as pushes. This lead to partially degraded site usability as the webhook delivery and GitHub Pages builds had been paused. “Our strategy was to prioritize data integrity over site usability and time to recovery” as per the GitHub team. 00:05 UTC, 22nd Oct Engineers started resolving data inconsistencies and implementing failover procedures for MySQL.Recovery plan included failing forward, synchronization, fall back, then churning through backlogs before returning to green. The time needed to restore multiple terabytes of backup data caused the process to take hours. The process to decompress, checksum, prepare, and load large backup files onto newly provisioned MySQL servers took a lot of time. 00:41 UTC, 22nd Oct A backup process started for all affected MySQL clusters. Multiple teams of engineers started to investigate ways to speed up the transfer and recovery time. 06:51 UTC, 22nd Oct Several clusters completed restoration from backups in the US East Coast data center and started replicating new data from the West Coast. This resulted in slow site load times for pages executing a write operation over a cross-country link. The GitHub team identified the ways to restore directly from the West Coast in order to overcome the throughput restrictions caused by downloading from off-site storage. The status page was further updated to set an expectation of two hours as the estimated recovery time. 07:46 UTC, 22nd Oct GitHub published a blog post for more information. “We apologize for the delay. We intended to send this communication out much sooner and will be ensuring we can publish updates in the future under these constraints”, said the GitHub team. 11:12 UTC, 22nd Oct All database primaries established in US East Coast again. This resulted in the site becoming far more responsive as writes were now directed to a database server located in the same physical data center as GitHub’s application tier. This improved performance substantially but there were dozens of database read replicas that delayed behind the primary. These delayed replicas made users experience inconsistent data on GitHub. 13:15 UTC, 22nd Oct GitHub.com started to experience peak traffic load and the engineers began to provide the additional MySQL read replicas in the US East Coast public cloud earlier in the incident. 16:24 UTC, 22nd Oct Once the replicas got in sync, a failover to the original topology was conducted. This addressed the immediate latency/availability concerns. The service status was kept red while GitHub began processing the backlog of data accumulated. This was done to prioritize data integrity. 16:45 UTC, 22nd Oct At this time, engineers had to balance the increased load represented by the backlog. This potentially overloaded GitHub’s ecosystem partners with notifications. There were over five million hook events along with 80 thousand Pages builds queued. “As we re-enabled processing of this data, we processed ~200,000 webhook payloads that had outlived an internal TTL and were dropped. Upon discovering this, we paused that processing and pushed a change to increase that TTL for the time being”, mentions the GitHub team. To avoid degrading the reliability of their status updates, GitHub remained in degraded status until the entire backlog of data had been processed. 23:03 UTC, 22nd Oct At this point in time, all the pending webhooks and Pages builds had been processed. The integrity and proper operation of all systems had also been confirmed. The site status got updated to green. Apart from this, GitHub has identified a number of technical initiatives and continue to work through an extensive post-incident analysis process internally. “All of us at GitHub would like to sincerely apologize for the impact this caused to each and every one of you. We’re aware of the trust you place in GitHub and take pride in building resilient systems that enable our platform to remain highly available. With this incident, we failed you, and we are deeply sorry”, said the GitHub team. For more information, check out the official GitHub Blog post. Read Next Developers rejoice! Github announces Github Actions, Github connect and much more to improve development workflows GitHub is bringing back Game Off, its sixth annual game building competition, in November GitHub comes to your code Editor; GitHub security alerts now have machine intelligencelast_img read more