This document discusses exception handling in Ruby. It begins by explaining why exception handling is needed by describing errors, error codes, and their shortcomings. It then discusses Ruby's exception handling mechanisms - the Exception class hierarchy, user-defined exceptions, and how to handle, raise, and catch exceptions using rescue, ensure, raise, catch, and throw clauses. Specific examples are provided to illustrate typical usage of these exception handling techniques in Ruby.
Exceptions are a powerful mechanism for centralized processing of errors and exceptional situations. This mechanism replaces the procedure-oriented method of error handling in which each function returns a code indicating an error or a successful execution.
Exceptions are a powerful mechanism for centralized processing of errors and exceptional situations. This mechanism replaces the procedure-oriented method of error handling in which each function returns a code indicating an error or a successful execution.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Essentials of Automations: Optimizing FME Workflows with Parameters
Ruby Exceptions
1. ‘Exception Handling in RUBY’
‘Exception Handling in RUBY’
Joy Menon
Department of Computer Science and Engineering, IIT Mumbai.
24 November 2004
2. ‘Exception Handling in RUBY’
A Brief Outline
Exception Handling: WHY?
Errors and Error Codes
The Need for Exception Handling
Exception Handling in Ruby:
The Exception Class
Exception Class Heirarchy
Handling Exceptions
Raising Exceptions
Catch/Throw Clauses
Conclusions
3. ‘Exception Handling in RUBY’
Exception Handling: WHY?
Errors and Error Codes
Errors and Error Codes
In any programming, occurance of errors is a distinct reality.
Errors need to be handled gracefully to avoid abrupt failures.
Code that detects error may not have context to handle it.
For example, attempting to open a file that doesn’t exist is
acceptable in some circumstances and is a fatal error at other
times. What does the file-handling module do?
Conventionally it was done using error-checking and
return-codes mechanism.
Functions were checked for return values, and if the return
code indicated failure, this code was interpreted and passed
up the call stack.
4. ‘Exception Handling in RUBY’
Exception Handling: WHY?
The Need for Exception Handling
The Need for Exception Handling
However Error-codes mechanism has following shortcomings:
Handling all errors through error codes is simply not possible.
Moving error codes up the function call stack is complicated.
Managing all the error-codes and associated code is tedious.
The Exception Handling mechanism addresses these
shortcomings.
Exceptions allow packaging info about error in an object.
Exception handling helps propagate object up the call stack.
Runtime system locates code that knows to handle the error.
Exception handling is essential for achieving well-designed object
oriented code, and therefore Ruby provides a mechanism for same.
5. ‘Exception Handling in RUBY’
Exception Handling in Ruby
The Exception Class
The Exception Class
As in other object oriented languages, Ruby offers a
mechanism for exception handling.
When an exception occurs..
Object of class Exception, or one of it’s children, created.
Exception is associated to message string & a stack backtrace.
All information about the exception is packaged in this object.
IOError, ZeroDivisionError, TypeError, SystemCallError, etc
are examples of exceptions derived from class Exception.
Ruby predefines a hierarchy of exceptions: see next slide.
7. ‘Exception Handling in RUBY’
User Defined Exceptions
User Defined Exceptions
User-Defined Exception
Users can create exception classes of their own.
These must inherit from class StandardError or its children.
If they dont, such exceptions will not be detected by default.
They may include more specific information about the
exception.
8. ‘Exception Handling in RUBY’
User Defined Exceptions
Handling Exceptions
Handling Exceptions
The basic approach to exception handling involves the use of:
Enclose candidate code in begin/end block.
Use rescue block to handle specific class of exceptions,
where:
Report the error,
Code to handle detected error,
Raise the exception using raise.
Use ensure block to ensure execution of some essential code
after handling, like deallocation of resources such as DB
connections, etc.
We can draw analogies to C++/Java exception handling:
begin/end block for candidate code. (like try block)
rescue blocks for handling code. (like catch blocks)
raise command for raising the exception. (like throw)
ensure command for necessary handling. (like final)
9. ‘Exception Handling in RUBY’
User Defined Exceptions
Handling Exceptions
Example: Using rescue, raise and ensure
10. ‘Exception Handling in RUBY’
User Defined Exceptions
Handling Exceptions
Handling Exceptions (continued..)
Variables
$ refers to the default global variable that stores the exception
object for the exception.
stderrobj is an example of user-defined variable storing the
reference to the exception object.
Matching exceptions to correct rescue block is like the case
statement mechanism,
object.kindof? result compared to exception types in
rescue statements.
11. ‘Exception Handling in RUBY’
User Defined Exceptions
Raising Exceptions
Raising Exceptions
Raising exceptions deliberately in code help to trigger alerts
where errors are expected and need to be handled.
The raise statement can take the following forms:
raise
Raises current exception again, or RuntimeError if none.
raise <message>
Creates new RuntimeError exception, associates it with
mentioned string, and raises the exception up the call stack.
raise <exception class>, <message>, <call stack>
Creates exception with arg-1 used as required exception type,
arg-2 as message string, and arg-3 as stack trace.
12. ‘Exception Handling in RUBY’
User Defined Exceptions
Raising Exceptions
Example: Typical Usage of raise
13. ‘Exception Handling in RUBY’
User Defined Exceptions
The Catch/Throw Clauses
The catch/throw Clauses
The rescue and raise mechanism is thus used for
abandoning execution when unwanted errors occur.
The catch and throw mechanism is used to continue
execution at some point up the call stack.
Working of catch/throw:
catch defines a block with a specific label.
The block is exeuted, typically accross nested functions, till a
throw followed by the label is encountered.
The call stack is then scoured for a catch block with a
matching label.
On a match, Ruby rolls back execution to the point and
terminates the block.
If the throw had an optional 2nd argument, it is returned as
value of the catch block.
14. ‘Exception Handling in RUBY’
User Defined Exceptions
The Catch/Throw Clauses
Example: Typical usage of catch/throw
15. ‘Exception Handling in RUBY’
Conclusions
Conclusions
Exception Handling is essential for managing errors in
object-oriented code.
The Ruby Exception Handling mechanism includes:
rescue and final clauses - for handling unwanted errors and
exit gracefully.
raise - for deliberately creating and raising exceptions in
code.
catch and throw clause - for continuing execution at some
point up the function call stack.
16. ‘Exception Handling in RUBY’
Conclusions
References
http://www.insula.cz/dali/material/rbycl/.
http://www.ruby-lang.org/.
Dave Thomas and Chad Fowler and Andy Hunt.
Programming Ruby: The Pragmatic Programmers’ Guide.
Pragmatic Bookshelf, Oct 2004.