We are a leading Fintech Development Services company. We provide services to clients for Enterprise Cloud Solutions, Fintech Services, De-fi Development, Money Management Solutions, Blockchain Solutions, Trading Bots, Decentralised Applications, Financial Analytics, Design, Motion Animation, Web and Mobile Solutions, APIs, bots, software solutions, and more.

Stackera

Setup, Run and Debug Cypress Tests: A Quick Guide To Get You Started

HackerNoon COO and CEO Discuss Entrepreneurship, Working With Your Spouse, and More

Introduction is a foundational class in UIKit and . Everything we see on the screen is constructed from `s and their subclasses. UIView iOS development UIView One topic often considered basic is the geometry of . It's easy to grasp initially, but complete understanding is often elusive, even for very experienced iOS engineers. In this article, we will dive deeply into the world of geometry. We will explain the main concepts, such as , , , , , how they relate to each other, and answer more advanced questions about computing the and Autolayout specifics. UIView UIView frame bounds center anchorPoint transform frame Playground To better understand the geometry, I've also developed a small iOS app: . https://github.com/psharanda/UIViewGeometry In the app, you can experiment with different properties in real time by adjusting sliders. Such an interactive approach is really helpful for grasping the nuances. UIView frame The definition of in Apple documentation is: UIView.frame The frame rectangle, which describes the view’s location and size in its superview’s coordinate system. Most of the time, we operate just with frames, either during manual layout or when printing the view's debug description. The designated initializer for also uses the frame as the only param. UIView This seems simple and straightforward. However, the reality is more complex. The frame is actually a computed property of . It is not the definitive source of the view's geometry. So, what is it exactly? UIView bounds Apparently, has many more properties related to geometry, and we’re now going to check the real, non-computed ones. Let’s examine the first of them: . UIView bounds The definition of is: UIView.bounds The bounds rectangle, which describes the view’s location and size in its own coordinate system. Usually, both and are simply equal to , and is the same as (however, it is not always true). bounds.origin.x bounds.origin.y 0.0 bounds.size frame.size What happens if is not equal to ? In that case, bounds basically act as a viewport, defining which part of the view coordinate system is visible to the outside world (superview). can also be seen as an additional translation (with a minus sign) for all subviews and view’s content rendered using . bounds.origin .zero bounds.origin drawRect This might remind you of . It is for a reason: the property of a is directly linked to its . UIScrollView contentOffset UIScrollView bounds.origin It's important to note that border, background, and shadow are rendered without considering . bounds.origin Previously, we mentioned that sometimes cannot be equal to . It may happen if transform is not equal to . frame.size bounds.size .identity According to the documentation, setting to any value when is not is considered undefined behavior (getting is still fine). However, setting when is not is valid.  In that case, describes the rectangle that fits the view after all transformations in its superview’s coordinate system. frame transform .identity bounds transform .identity frame center The definition of : UIView.center The center point of the view's frame rectangle in its superview’s coordinate system. However, the term "center" can be a bit misleading. It only represents the actual center of the view if the (more on this in the next section) is positioned at the center, specifically at ( , ). A more accurate definition for would be: view.anchorPoint 0.5 0.5 center The coordinates of the view’s anchor point in its superview’s coordinate system. UIView’s is exactly the same as . center CALayer.position The combination of and can fully replace the use of bounds center frame transform The transform property in iOS development is a fundamental concept that enables developers to apply geometric transformations to views. UIView The transform property of is of the type , which represents a matrix used for affine transformations. Affine transformations include: UIView CGAffineTransform Translation To move a view, you set the transform property with . For instance, moves the view 50 points to the right and 75 points down. CGAffineTransform(translationX:y:) view.transform = CGAffineTransform(translationX: 50, y: 75) Scaling To scale a view, use . For example, halves the size of the view in both width and height. CGAffineTransform(scaleX:y:) view.transform = CGAffineTransform(scaleX: 0.5, y: 0.5) Rotation To rotate a view, apply . The angle is in radians, so to rotate 30 degrees, you would use . CGAffineTransform(rotationAngle:) view.transform = CGAffineTransform(rotationAngle: .pi / 6) Combining Transforms One of the powerful aspects of the transform property is the ability to combine transformations. You can combine scaling, rotation, and translation into a single transform using concatenation, for example: var t = CGAffineTransform.identity // 0
t = t.concatenating(CGAffineTransform(scaleX: 0.5, y: 0.5)) //1
t = t.concatenating(CGAffineTransform(rotationAngle: .pi / 6)) //2
t = t.concatenating(CGAffineTransform(translationX: 50, y: 150)) //3
view.transform = t To reset a transformation, set the property to , which is also the default for a newly created . transform CGAffineTransform.identity UIView Perspective ’s transform is baked by which has the type and can be used for even more advanced transformations like changing the perspective UIView CALayer.transform CATransform3D var transform = CATransform3DIdentity;
transform.m34 = 1.0 / 500.0;
view.layer.transform = CATransform3DRotate(transform, .pi / 4, 0, 1, 0) anchorPoint The anchor point defines how a view behaves during transformations. It's specified using the unit coordinate space, where ( , ) is the top-left corner of the view's bounds rectangle, and ( , ) is the bottom-right corner. By default, the anchor point of a is set to ( , ), which is the center of the view’s bounds rectangle. 0 0 1 1 UIView 0.5 0.5 Interestingly, the property was only added to in iOS 16, but it has always been accessible through . anchorPoint UIView view.layer.anchorPoint Geometric manipulations, like rotation or scaling, occur around the anchor point. For example, if you apply a rotation transform to a view with the default anchor point, the view will rotate around its center. If you change the anchor point to a different location, the view will rotate around this new point. How to calculate the frame? We mentioned in the beginning that is a computed property. Now, with enough knowledge, let’s compile all the observations into actual code that computes the frame. frame First, let’s follow the positioning logic that is used during the render process. We start with a rectangle, with set to and set to . is not involved in calculations since it only affects subviews and the output. origin .zero size bounds.size bounds.origin drawRect Before applying the transform, we must translate the view according to its . We apply the transform only when the view, with its , is aligned with the starting point coordinates ( , ). anchorPoint anchorPoint 0 0 Now, we can apply the transform. The last step is to translate the view by its value, positioning it correctly. center These transformations can be concatenated into a single transform (i.e., absolute one), which is then applied to zero-origin bounds by using function. CGRectApplyAffineTransform Here is the final function which computes the frame: func computeFrame(bounds: CGRect,
                  center: CGPoint,
                  anchorPoint: CGPoint,
                  tranform: CGAffineTransform) -> CGRect {

    // set the initial rectangle to bounds with origin set to (0, 0)
    let zeroOriginBounds = CGRect(origin: .zero, size: bounds.size) // 1

    // combine transformations
    let absoluteTransform = CGAffineTransform(
            translationX: -anchorPoint.x * bounds.width,
            y: -anchorPoint.y * bounds.height
        ) // 2
        .concatenating(tranform) // 3
        .concatenating(CGAffineTransform(translationX: center.x, y: center.y)) // 4

    // apply transform to the initial rectangle
    return CGRectApplyAffineTransform(zeroOriginBounds, absoluteTransform)
} How can this knowledge be useful for us? Apart from just satisfying curiosity and gaining a better understanding of the internals, this algorithm has some real-world applications. A classic example is an image editor. Imagine you are building an application that creates custom stories. You want to place stickers on top of a photo, move, scale, and rotate them with your finger. For the editing mode, you use the actual and layout it by modifying its properties like center, bounds, and transform. Eventually, you’d like to render your story project into a bitmap and share it in high resolution, and that’s where understanding how geometry works becomes really useful. The image rendering code can look like the following: UIImageView UIView let renderer = UIGraphicsImageRenderer(size: imageSize)
let image = renderer.image { context in
    let cgContext = context.cgContext
    // render photo…
    // render other things…
    
    // render our sticker
    let absoluteTransform = CGAffineTransform(
        translationX: -sticker.anchorPoint.x * sticker.bounds.width,
        y: -sticker.anchorPoint.y * sticker.bounds.height
    )
        .concatenating(sticker.transform)
        .concatenating(
            CGAffineTransform(translationX: sticker.center.x, y: sticker.center.y)
        )
    
    cgContext.saveGState()
    cgContext.concatenate(absoluteTransform)
    sticker.image.draw(in: CGRect(origin: .zero, size: sticker.bounds.size))
    cgContext.restoreGState()
} What about Autolayout? Autolayout doesn't work with . It also ignores the and properties during its calculations. For each view, Autolayout calculates and sets only the and . The and are still used, but only for the final render on screen, and are applied afterward. frame transform anchorPoint bounds center transform anchorPoint To reiterate, in the Autolayout world, , , and don't exist. The Autolayout process is: constraints in, and out. frame transform anchorPoint bounds center Additional Resources UIView Documentation – https://developer.apple.com/documentation/uikit/uiview View Programming Guide – https://developer.apple.com/library/archive/documentation/WindowsViews/Conceptual/ViewPG_iPhoneOS/WindowsandViews/WindowsandViews.html#//apple_ref/doc/uid/TP40009503-CH2-SW5 Core Animation Basics – https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/CoreAnimation_guide/CoreAnimationBasics/CoreAnimationBasics.html#//apple_ref/doc/uid/TP40004514-CH2-SW3 Understanding UIKit Rendering – https://www.wwdcnotes.com/notes/wwdc11/121/ Understanding UIKit: CALayer Anchor Point – https://ikyle.me/blog/2022/understanding-uikit-calayer-anchor-point Understanding UIScrollView – https://oleb.net/blog/2014/04/understanding-uiscrollview/

Mastering UIView Geometry: A Dive into UIKit's Foundational Class and Geometry Concepts for iOS

Crypto’s largest exchange just got hit with $4 billion in fines. Its CEO resigned. Rumors are swirling that the largest stablecoin, a crypto version of the US dollar, will collapse under US regulatory scrutiny. Every major US crypto entity is getting sued by investors, users, or the US government. Bitcoin’s price is up 126% this year. The bear market warriors claim validation. The OGs chant “victory!” The bull market champions call for new all-time highs. They all expect crypto will go on an amazing run, they just can’t agree whether that means bitcoin’s price will hit $60,000 before the halving, deliver diminishing returns through the end of 2025, peak sooner than expected in a “left-translated cycle,” or reach some other number on a timeframe that fits within the cycle theories, trading charts, and data models. Torn between two lovers Nobody else seems to believe them. Mainstream commentators seem doubtful. Jim Cramer said crypto’s done. YouTube traders say this is the “B” wave of an A-B-C correction to $6,000 (whatever that means). Your favorite regulators say it’s a fraud. Munger and Buffett say its going to zero. Macro guys tell you the wheels are about to fall off the world’s economy but 2022’s Recessionistas tell you that the recession’s been called off. On-chain gurus say prices have to go up because 75% of bitcoin’s supply sits in the hands of people who either don't care enough to sell or care so much they won’t sell. Data guys say that can’t happen, “the maths” don’t work out. One side of YouTube says the bull market’s confirmed. The other side says prices have to go down because “there is no liquidity,” “interest rates are too high,” and “we need capitulation first.” You're torn between two lovers, a bull and a bear. They both want what’s best for you, but only one is right! Just go along with it Some people simply can’t accept the reality: if bitcoin’s price stays above $15,600, crypto’s been in a bull market for over a year. If that’s you, no worries! What you’re feeling is normal during the disbelief stage of the market cycle, just before hope returns. This is a psychological phenomenon best illustrated by the Wall Street Cheat Sheet, an image that captures the emotions you will feel as you ride the crypto rollercoaster. Take a look: Can you apply that to bitcoin’s price chart? Here it is: You don’t have to believe what you see. You may, however, want to suspend your disbelief. Excuses, excuses Since the start of the year, every upswing has ended with a downswing. You get your hopes up, only to be let down. Priya in the Park insists the end is near, and she’s called every crypto bear market—sometimes more than three years in advance! She’s always right! Billy the Neighbor just bought back the Tesla stock he sold at the 2022 bottom but he’s not hitting you up for altcoin recommendations anymore crypto because “it’s dead” and “I don’t see why it’s valuable.” Your family thinks you lost all of your money. Conspiracy theorists tell you Tether, HTX, and [fill-in-the-blank crypto entity] will collapse from regulators, insolvency, central banks, law enforcement, quantum computers, and whatever else the social media algorithms slip into their feeds. Insolvent exchanges are dumping their customers’ cryptos to raise money. Think of all the excuses you’ve had to keep money out of crypto this year. Curve.Fi gets hacked and seems on the verge of imploding DeFi, so you keep your money out of the market. Death crosses and bull market support bands say you can't buy yet. You haven’t found a narrative that will bring new money into crypto, let alone a narrative that fits what you’re looking for, so you sit on your hands waiting for the altcoin capitulation or some news to get you hyped up again. China has an economic crisis. Supposedly, Europe’s in the middle of one (they don’t know it yet). Canada’s about to collapse. As a result, your mind simply can’t convince you that this market could ever recover. Yet, crypto goes up. Embrace uncertainty You think crypto should collapse, but nothing’s collapsing. Regulators seem to lose or settle every anti-crypto case. Wall Street’s preparing to take over the space. Crypto is not going away. Circumstantial evidence and on-chain behavior suggest stackers and HODLers have settled in for the long haul, and they control the largest portion of the market since 2016. Key sentiment indicators remain in a healthy equilibrium. Key metrics show strong market conditions. China’s stimulus has started to enter the market. Other Asian countries have taken back market share from the US. I could give you a dozen charts that make the future seem hopeless. https://twitter.com/MarkHelfman/status/1705780363040010437?embedable=true Despite all the gloom, the crypto market has turned a corner on every conceivable metric I look at. Bitcoin’s returns beat almost every asset that people like you and me can buy. Hard to believe, I know. Don’t try to believe it. Just try to suspend your disbelief. If you do that, maybe you’ll see a reality you never knew about. This post is also available as a collectible NFT at . https://mirror.xyz https://mirror.xyz/0x9a6600c7B40801dda9A0Fa4E8DE7b1B99FE524a7/ZPqrswR2QxFUPqP0Rng6Gl226NQDpG0nrYNFqx9-gfk?embedable=true Mark Helfman publishes the newsletter. He is also the author of three books and a top Bitcoin writer on and . Learn more about him in his and connect with him on or . Crypto is Easy Medium Hacker Noon bio Superpeer Tealfeed

The Crypto Market Demands You Suspend Your Disbelief

a SWOT analysis is an evaluation of the fundamental, operational, technical, social, economic, and even, to some degree, administrative elements of a project. This is not a model to be used for trading purposes. (NFA, DYOR) *Note: Composed of four elements, Strengths, Weaknesses, Opportunities, and Threats, a SWOT analysis framework provides excellent insight for establishing a high-level understanding of the state of a project's well-being through the lens of a birds-eye view. It can help formulate decisions around which areas require more attention, set performance goals, and organize a foundational understanding of where a project is headed. Rarely (if ever) used in crypto, it is time to apply this timeless method of evaluation to the digital asset space. Today, Stacks (STX), the layer 2 solution that is bringing smart contract capabilities to the Bitcoin network, will get a . SWOT 💪 Strengths (Internal) (Helpful) 1. PoX Consensus Model This is a very novel, creative solution for tithing the operational logic of the Stacks network to Bitcoin. Proof-of-transfer is a mechanism that utilizes transactional entropy as the underlying modality to mint new tokens. Credit must be given to Stacks for creating this system (which never existed prior), and it acts as a very abstract social pegging. Based on the use of assets from Proof-Of-Work-based chains, miners on the Bitcoin Network transfer their assets to Validators on Stacks (called Stackers) in return for the chance to stream the next batch of blocks and receive the newly minted STX tokens. 2. On-Chain TVL increasing The trendline of how much value is locked on Stacks in USD terms has been showing directionally improving. While it is possible that the trend benefits alongside a greater market recovery from the beginning of 2023, the fact there are already DEFI and NFT initiatives taking place on-chain signals a blue ocean of opportunity. 3. sBTC Attempting to bring TVL into its ecosystem in the form of Bitcoin and replicate the massive success of WBTC, sBTC promises to be the most trustless method of bridging BTC. Utilizing a two-way pegging system where users would deposit BTC into a nominated address that would then, in turn, be minted on Stacks at a 1:1 ratio and de-peg or move their assets back off of Stacks onto Bitcoin. What sets sBTC apart from all other pegging systems in the industry today is the architecture of capital flows. Bridging a BTC from Bitcoin to Stacks is permissionless and maximally frictionless; withdrawing requires some form of authority attestation. Stacks has devised a model for establishing the withdrawal authority in a maximally decentralized way. 4. Bridges to EVM chain Connecting the most prominent networks in terms of unlocks a new degree of capital, a new grade of developers, and a greater surface area for potentially marketing Stack's network in the smorgasbord of applications that live around the EVM ecosystem. At this time, Stacks is only bridged to Ethereum and Binance Smart Chain; however, introducing each new network should provide the project with some exciting technical roadmap developments over the next months/years. 5. Uses Bitcoin as Data Availability Layer In the new modular landscape where technologies are constantly introducing more complexity and more diversity in an attempt to cater to a still extremely young market, Stack’s focus on the Bitcoin ecosystem for data availability brings a novel level of decentralization and security to the dApp space. Data availability is arguably the most important part of any decentralized information system; given that Bitcoin is the most resilient (by raw computational power) and the most ridging, the data that Bitcoin's network governs can be thought of as being the most secure. This anchoring to Bitcoin allows STX to inherit some of its most desirable properties. 6. STX token was sold as an Approved Security Stacks token was the first to receive the regulatory green light to be sold to the public as a compliant digital asset. This makes STX an extremely interesting asset for potential Tradfi market participants. The sale took place in 2019, setting a precedent for any other projects in the space to follow in their footsteps. 7. STX Validator Incentives STX has one of the few, possibly only, models for the network participants (validators) to earn real yield through their involvement. Given that Stackers actually receive BTC that is used within its consensus model, there can be a real-world demand vector attributed to the STX token (even if only through second or third-degree relationships). 😞 Weaknesses (Internal) (Harmful) 1. BNS Abandoned Twice Stacks released BNS (Bitcoin Name Services) sometime in July of 2022. With over a year of observation, it seems that BNS does not really have that much of an important place in the digital asset market. Surely, it was released in the mother of all crypto bear markets, where approximately 300,000 BNS domains were sold. However, it has drawn a pattern of hype followed by absolute disregard. If the hype cooled down to a low of -95%, it would be feasible, but as the charts show us, the hype is followed by a fall to actual 0 in some cases. Moreover, all on-chain activity is to some degree faked by either project founders or supporters, or at the very least not Sybil conscious (a single entity can easily just own multiple BNS domains), likely arriving at a true number some odd 10x lower than the total amount sold. *This is by no means an existential crisis of any kind for Stacks, just some worthwhile food for thought in gauging ecosystemic resilience. 2. Bitcoin MEV Sharing a security model is known to be an obvious risk factor for MEV. Stacks was (and at this time still is) subject to the economic vulnerability present in the current version of PoX, where Bitcoin Miners can technically conduct fraudulent transactions without there being any risk to them; Stacks Network cannot punish Bitcoin Miners. Savvy miners came in and began only to include the actions related to their own nodes, pushing assets through a bottleneck that totally eliminated competition from other STX miners. 🧐 Opportunities (External) (Helpful) 1. Ultra Low Network DAU/DAA Both an opportunity and a threat. At the painfully modest level of roughly 3,000 Daily active users (not knowing how many of these are Sybils or bots), in the event the network gains a tiny portion of the interest that will flood the markets at some point, the potential external economic impact easily qualifies as enough to break previous ATH's. Moreover, considering how much quality infrastructure has actually been developed in the process, is STX attracts the developer community, then orders of magnitude growth await in terms of useability, adoption, and access. 2. No Real Competition Stacks has carved out a decently strong reputation for itself as THE project that is approaching Bitcoin programmability, scalability, and interoperability in the most crypto-pure way "decentralized." Positioned very uniquely against the few other participants (Liquid, Lighting Network, Rootstock), Stacks is the only one to provide the spectrum of benefits with minimal negative externalities. 3. Appealing to TradFi Stacks has carved out a niche that ticks the boxes for many traditional financial entities to be interested in participating in its ecosystem. The real yield of Bitcoin, the security of Bitcoin, a digital asset that was brought to market under regulatory supervision, scalable smart contract environment, and reputable findings with tremendous backing from prominent VCs. STX is easily crypto that likely every major enterprise will, at the very least, consider in their Web3 journies. 😳 Threats (External) (Harmful) 1. Graveyard of Bitcoin-based Solutions Rootstock, colored coins, Ordinals, and a handful of other attempts have been made to introduce more functionality on Bitcoin. Nearly all of them have failed to pick up steam, existing only within tiny niche communities until eventually dying off and becoming relics. If attempting to evaluate the long-term survivability of Stacks based on the niche it is operating in, the odds are stacked against them (pun intended). 2. Ultra Low Network DAU/DAA Both an opportunity and a threat. Ultra-low levels of adoption could be a direct indicator of the relative unimportance of the project or perhaps just a failure in marketing to users. Considering that at the absolute peak hype, the Stacks networks showed just about 9,000 daily active addresses. More likely than not, a decent portion of this can be attributed to bot activity, which dampens the interest levels even further. This extremely low level of engagement shows one of two things: either honesty from the network operators in showing activity or total disregard for the network, and the first inadvertently points to the second. Takeaway: Positive, unorthodox overall feeling about the project. Technology is there. Unique market position and produce offering is there. Marketing and social presence are definitely lagging, but out of all things, it is easiest to sort out. I'm not saying building communities is easy; I'm saying that building quality products is much more noble. Conclusion: Stacks is to Bitcoin what Polygon is to Ethereum. To be totally honest, I was an extreme skeptic of stacks. I actually considered it trash for a long while. But, after a thorough digging, I am humbled to admit that I was wrong; it's legit. While I now see the value proposition and understand why institutions might find this attractive, I would still NOT deposit my Bitcoin into sBTC and will most likely never use the smart contract network itself. Would I invest in the token itself (STX)? Yes. Small, controlled DCA with a better chance for higher returns than just holding Bitcoin. Under a different set of circumstances (where I had far more wealth), I would definitely explore becoming a validator on their network, but from my calculations, anything less than ~$500,000 is not worth the time. If you know something that I don't or feel as though I might have missed anything worth noting, please do share. I would tremendously appreciate some feedback. Thank you so much for reading, I hope this serves you well on your journey. Live long and prosper 🥂

The Stacks (STX) SWOT Analysis

Nowadays, an essential part of the development process is to track the performance of an application. Analyzing the processes in the system allows you to better understand which part of the project is working well, and where urgent fixes are needed. Among the many tools that allow you to monitor and debug, there is one that is very easy to customize in the Laravel framework, because it is made by the creators of the framework themselves. Its name is Telescope. Laravel Telescope is a debugging panel, with a user-friendly and modern design. Inside the panel you can find logs and statuses of all elements of the system. Features Laravel Telescope is a customized debugging panel with different aspects of the application, where each aspect is highlighted in a separate menu item. Telescope allows you to see all parts of the system, such as database accesses, cache accesses, how to work with built-in events, how to work with custom events. Also there is realized the display of requests to the system or errors. We will talk more about the features a little later, but for now let's set up the application. Local and production installation The main convenience of working with Telescope is that it can be configured literally in a couple of clicks. After installing the package you need to load the assets with the command telescope:install , and then run migrations. When installing only locally we need, after adding the package to dev dependencies and loading the assets, to remove the TelescopeServiceProvider connection from config/app.php, but set the provider connection depending on the environment in AppServiceProvider, for example as follows if ($this->app->environment('local')) {
   $this->app->register(\Laravel\Telescope\TelescopeServiceProvider::class);
   $this->app->register(TelescopeServiceProvider::class);
} After that you need to remove the Telescope package from discover in composer.json.
As for the production solution, there can't be one opinion. On the one hand - when installing and on production environment there is no need to finalize the connection, because in this case it will be available everywhere. It is also a plus, as it gives you the opportunity to quickly see what is happening with the state of production.
However, such a solution has a disadvantage and quite a big one.
Due to the fact that the data that is shown in Telescope is extremely sensitive, it is necessary to correctly configure the routing and disable it from being available without access to the corporate network.
In my opinion, the ideal connection would be to access a local Laravel Telescope that accesses all data sources within the corporate network.
The last step in setting up this tool is to set up the configuration in config/telescope.php Let's see how it works By default Telescope runs at /telescope. With a fresh installation, you probably won't see any requests or other data. But what we can say with certainty is that there is a lot of possibilities for this tool, if you look even just at the list of menus. As for the settings for connecting different services, we will talk about it below. In the meantime, it is still necessary to understand how to set up the panel for yourself. Prune command The first problem in our application is the problem with data deletion. Since Telescope collects all the data it sees, the database often quickly reaches its limit without deleting old records. Because of this, we need to update the database by force. Every application has a different frequency of data refresh, but if we're talking about a small project, we can do it on a daily basis. This can be achieved by running the artisan command telescope:prune, or by setting it automatically in Console\Kernel. Accessing the Telescope panel By default, working with the panel is only allowed locally. To fix this, you need to add some modified logic to the Gate check in TelescopeServiceProvider and specify there, for example, your email address. protected function gate(): void
{
   Gate::define('viewTelescope', function ($user) {
       return in_array($user->email, [
           'example@gmail.com'
       ]);
   });
} As you can see in the listing - adding a rule for validation is not a difficult task. Filters From time to time, when working with Telescope, especially in production, there is a problem with disk space. In order to avoid this and not to disable all logs so often, Laravel Telescope provides filters. They allow us to record only important parts, such as errors or dropped jobs. To change this we need to add or remove necessary/unnecessary parts in TelescopeServiceProvider, for example like this: Telescope::filter(function (IncomingEntry $entry) {
   if ($this->app->environment('local')) {
       return true;
   }


   return $entry->isReportableException() ||
          $entry->isFailedRequest() ||
          $entry->isFailedJob() ||
          $entry->hasMonitoredTag();
}); So the filters helped to limit the set of logs when working on production. Tags If you look at the previous listing, there is a method hasMonitoredTag(). It allows you to show all records that have a tag set, regardless of which watcher it belongs to. In order to set a tag on, for example, a query, you will need to add the following to the TelescopeServiceProvider: Telescope::tag(function (IncomingEntry $entry) {
   return $entry->type === 'request'
       ? ['status:'.$entry->content['response_status']]
       : [];
}); All tracked tags can be viewed by clicking on the button in the top right corner of the admin panel interface. Available watchers Finally, we have observed all the formalities and come to the most interesting part. Laravel Telescope contains a huge number of integrations with different services. Let's take a look at the most popular watchers. Adding a watcher to the system is done in the config/telescope configuration file. If you need to add login data to a new watcher, the new data is written directly to the 'watchers' key. The full list is quite large and while some work with obvious entities like CacheWatcher, CommandWatcher, RequestWatcher, others need a bit more detail. BatchWatcher - this watcher keeps track of sending jobs in batches. Read more about this method here EventWatcher and ModelWatcher - it's worth noting that EventWatcher does not track changes to models that use standard model events, unlike ModelWatcher GateWatcher - records all checks of gates and policies and their results. Below, for information, are examples of how some of the pages work. CacheWatcher Tracks cache hits, including unsuccessful ones. You can also see the passed arguments and options DumpWatcher Shows all calls to dump() function It is worth noting that this watcher does not work when using as a cache driver. array EventWatcher Shows all custom events that have occurred recently. You can also track the listener that worked on a particular event. ExceptionWatcher One of the most useful watchers, as it allows you to see errors, including the code where the error is thrown, as well as stacktrace Upgrade Telescope version It cannot be ignored that upgrading the Telescope version can cause some difficulties. To solve them, you need to follow all the steps of the guide on the official website, and make a couple of points. Due to the fact that the published assets may change during the upgrade, you need to upload them again during the upgrade, either manually or by setting post-update-cmd in composer.json Conclusion There are a huge number of all sorts of options on the market right now for debugging and tracking the state of a project. Laravel Telescope may not be very suitable for Production solutions, but for local development the tool is almost indispensable. It is worth noting that Laravel Telescope is updated quite often, which gives hope for long term support.

Companion for working with Laravel — Telescope

Hi all! My name is Taras Egorov; I'm an engineer at inDrive. I'll show you how we set up an infrastructure capable of running more than 5,000 tests per day on iOS and Android devices combined. The secret is simple: we used Selenoid. Preface Last year, our colleagues conducted a study of auto testing, and we took part in a survey as part of the study. We were pleased with the survey's findings, so we decided to write an article to share our experience with you and get some advice in return. We thought it a good idea to divide the material into two parts: the first one focusing on Android and the second on iOS. Let's begin with Android. Running the tests on Android Selenoid is a tool for running and managing browsers and Android emulators in a Docker container. You can read more about this . popular in the documentation To write Appium tests, we use: Kotlin; JUnit 5; Maven. The first run. Setting up Selenoid Create a config file: browsers.json {

  "android": {

    "default": "10.0",

    "versions": {

      "10.0": {

        "image": "browsers/android:10.0",

        "port": "4444",

        "path": "/wd/hub"

      }

    }

  }

} The emulator image is specified in . The guys from have prepared ready-made images of Android emulators. You can check them out or . The images don't differ from each other in any way. image aerokube here here Let’s take the image as an example. The image must be downloaded beforehand: , otherwise the tests will not run: browsers/android:10.0 docker pull browsers/android:10.0 Original error: create container: Error response from daemon: No such image: browsers/android:10.0 The next step is to run Selenoid. We do that directly via , or there’s the option of using . docker Configuration Manager docker run -d \

           -v /var/run/docker.sock:/var/run/docker.sock \

           -v "$(pwd)/selenoid/config/":/etc/selenoid/:ro \

           -p 4444:4444 \

           --name selenoid \

           aerokube/selenoid:1.10.7 You can check to see if Selenoid is working properly by following the link in your browser: http://localhost:4444 You are using Selenoid 1.10.7! Specify the Selenoid address in the Appium tests in the driver: ...
val driver = AndroidDriver(URL("http://localhost:4444/wd/hub"), capabilities)
... Next, specify the link to the build in capabilities: ... 
capabilities.setCapability("appium:app", "https://storage.example.com/builds/app.apk")
... If unable to provide a link, you can specify the path to the build:** ...
capabilities.setCapability("appium:app", "/builds/app.apk")
... Where is the path inside the container where the emulator is being run. For this option to work properly, be sure to specify the in : /builds/app.apk volumes browsers.json {

  "android": {

    "default": "10.0",

    "versions": {

      "10.0": {

        ...

        "volumes": [

          "/home/username/app.apk:/builds/app.apk:ro"

        ]

        ...

      }

    }

  }

} Where is the path to the build on the host platform. /home/username/app.apk That's it, we've almost set up Selenoid, and now we can try running the tests: ./mvnw test But, unfortunately, the tests will not be able to run. Let's look into this and see what's wrong. The second run. Taking a look at the logs and video The first thing to do after a failed startup is to check out the Selenoid logs: docker logs selenoid [INIT] [Loading configuration files...]
[INIT] [Loaded configuration from /etc/selenoid/browsers.json]
[INIT] [Video Dir: /opt/selenoid/video]
[INIT] [Your Docker API version is 1.41]
[INIT] [Timezone: UTC]
[INIT] [Listening on :4444]
[NEW_REQUEST] [unknown] [172.17.0.1]
[NEW_REQUEST_ACCEPTED] [unknown] [172.17.0.1]
[LOCATING_SERVICE] [android] [10.0]
[USING_DOCKER] [android] [10.0]
[CREATING_CONTAINER] [selenoid/android:10.0]
[STARTING_CONTAINER] [selenoid/android:10.0] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa]
[CONTAINER_STARTED] [selenoid/android:10.0] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa] [0.40s]
[0] [REMOVING_CONTAINER] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa]
[0] [CONTAINER_REMOVED] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa]
[0] [SERVICE_STARTUP_FAILED] [http://172.17.0.3:4444/wd/hub does not respond in 30s] We see that the status is SERVICE_STARTUP_FAILED. Go to the and look at the status value: documentation SERVICE_STARTUP_FAILED - Failed to start Docker container or driver binary The error doesn’t tell you much, and more information is required. It would be good to take a look at the container logs. Let's do that by enabling logging: docker run -d \

           -p 4444:4444 \

           -v /var/run/docker.sock:/var/run/docker.sock \

           -v "$(pwd)/selenoid/config/":/etc/selenoid/:ro \

           -v  "$(pwd)/selenoid/logs/":/opt/selenoid/logs/ \

           aerokube/selenoid:1.10.7 \

           -log-output-dir /opt/selenoid/logs We also enable logs in the Capabilities section: ...
capabilities.setCapability("enableLog", true)
... Run the tests and review the logs using the browser : http://localhost:4444/logs/ 2023-04-16T13:44:43.909768530Z Waiting X server...
2023-04-16T13:44:44.009494775Z Logging to: /tmp/fluxbox.log
2023-04-16T13:44:44.047587277Z Waiting X server...
2023-04-16T13:44:44.151933325Z Waiting X server...
2023-04-16T13:44:44.262850410Z * daemon not running; starting now at tcp:5037
2023-04-16T13:44:44.457972956Z * daemon started successfully
2023-04-16T13:44:44.458249266Z adb: no devices/emulators found
2023-04-16T13:44:45.463480812Z adb: no devices/emulators found
2023-04-16T13:44:46.471547723Z adb: no devices/emulators found
2023-04-16T13:44:47.476093515Z adb: no devices/emulators found
2023-04-16T13:44:48.481987351Z adb: no devices/emulators found
2023-04-16T13:44:49.486503149Z adb: no devices/emulators found
2023-04-16T13:44:50.492757801Z adb: no devices/emulators found
2023-04-16T13:44:51.499094108Z adb: no devices/emulators found
2023-04-16T13:44:52.505862428Z adb: no devices/emulators found
2023-04-16T13:44:53.513276412Z adb: no devices/emulators found
2023-04-16T13:44:54.520642210Z adb: no devices/emulators found
2023-04-16T13:44:55.527420189Z adb: no devices/emulators found
2023-04-16T13:44:56.534631013Z adb: no devices/emulators found
2023-04-16T13:44:57.316094939Z WARNING. Using fallback path for the emulator registration directory.
2023-04-16T13:44:57.335415397Z checkValid: hw configs not eq
2023-04-16T13:44:57.541959741Z adb: device offline
2023-04-16T13:44:58.547907700Z adb: device offline
2023-04-16T13:44:58.565504866Z emulator: WARNING: System image is writable
2023-04-16T13:44:58.565528396Z emulator: Cold boot: different AVD configuration
2023-04-16T13:44:58.565532576Z Your emulator is out of date, please update by launching Android Studio:
2023-04-16T13:44:58.565536346Z  - Start Android Studio
2023-04-16T13:44:58.565539506Z  - Select menu "Tools > Android > SDK Manager"
2023-04-16T13:44:58.565543076Z  - Click "SDK Tools" tab
2023-04-16T13:44:58.565546216Z  - Check "Android Emulator" checkbox
2023-04-16T13:44:58.565549216Z  - Click "OK"
2023-04-16T13:44:58.565552146Z 
2023-04-16T13:44:59.554451514Z adb: device offline
2023-04-16T13:45:00.560926060Z adb: device offline
2023-04-16T13:45:01.568777440Z adb: device offline
2023-04-16T13:45:12.124226047Z emulator: INFO: boot completed
2023-04-16T13:45:12.124251007Z emulator: INFO: boot time 27848 ms
2023-04-16T13:45:12.124255077Z emulator: Increasing screen off timeout, logcat buffer size to 2M.
2023-04-16T13:45:12.152557294Z emulator: Revoking microphone permissions for Google App. The container logs are not much help here either, because you can't see the Appium logs. Now let's try to enable them. To do this, let's look at the script : entry point.sh ...
if [ -z "$VERBOSE" ]; then
    APPIUM_ARGS="$APPIUM_ARGS --log-level error"
else
    EMULATOR_ARGS="$EMULATOR_ARGS -verbose"
fi
... To enable Appium logs, the parameters and : must be passed to the container: VERBOSE=true APPIUM_ARGS=--log-level debug {

  "android": {

    "default": "10.0",

    "versions": {

      "10.0": {

        ...

        "env": [

          "VERBOSE=true",

          "APPIUM_ARGS=--log-level debug"

        ]

        ...

      }

    }

  }

} To enable Appium to debug logs, you need to pass VERBOSE; in this case, the emulator logs turn on and start filling the "ether"” But we fixed that for future images =) Now it is enough to pass to . APPIUM_ARGS=-log-level debug ...
[HTTP] --> POST /wd/hub/session/c89fa9c2-ca2b-49cd-ab31-590eeccf77d1/element
[HTTP] {"using":"id","value":"authorization_edittext_phone"}
[debug] [W3C (c89fa9c2)] Calling AppiumDriver.findElement() with args: ["id","authorization_edittext_phone","
c89fa9c2-ca2b-49cd-ab31-590eeccf77d1"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, -and
roid uiautomator
[debug] [BaseDriver] Waiting up to 0 ms for condition
[debug] [WD Proxy] Matched '/element' to command name 'findElement'
[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/65943f03-3b35-4d3eb221-d6dc7988f935/element] with body: {"strategy":"id","selector":
"authorization_edittext_phone","context":"","multiple":false}
[WD Proxy] Got response with status 404: {"sessionId":"65943f03-3b35-4d3e-b221-d6dc7988f935","value":{"error"
:"no such element","message":"An element could not be located on the page using the given search parameters","stacktrace":"io.appium.uiautomator2.common.exceptions.El
ementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(Find
Element.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.
handleRequest(AppiumServlet.java:253)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.Se
rverHandler.channelRead(ServerHandler.java:68)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io
.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann...
[debug] [W3C] Matched W3C error code 'no such element' to NoSuchElementError
[debug] [W3C (c89fa9c2)] Encountered internal error running command: NoSuchElementError: An element could not
be located on the page using the given search parameters.
[debug] [W3C (c89fa9c2)]     at AndroidUiautomator2Driver.findElOrEls (/opt/node_modules/appium/node_modules/appium-android-driver/lib/commands/find.js:75:11)
[debug] [W3C (c89fa9c2)]     at process._tickCallback (internal/process/next_tick.js:68:7)
[HTTP] <-- POST /wd/hub/session/c89fa9c2-ca2b-49cd-ab31-590eeccf77d1/element 404 23 ms - 444
... As seen from the logs, Appium cannot find our element. Let's see what is happening on the emulator screen. To do this, we have to run the Selenoid UI: docker run -d \

           --name selenoid-ui \

           -p 8080:8080 \

           --link selenoid:selenoid \

           aerokube/selenoid-ui:1.10.4 \

           --selenoid-uri "http://selenoid:4444" Go to and open the Selenoid UI: http://0.0.0.0:8080 Be sure to enable VNC and video recording in the tests: ...

capabilities.setCapability("enableVNC", true)

capabilities.setCapability("enableVideo", true)

... The Selenoid startup command ends up looking like this: docker run -d \

-v /var/run/docker.sock:/var/run/docker.sock \

-v "(pwd)/selenoid/logs/":/opt/selenoid/logs/ \

-v /opt/selenoid/video/:/opt/selenoid/video/ \

-e OVERRIDE_VIDEO_OUTPUT_DIR="/opt/selenoid/video/" \

-p 4444:4444 \

-name selenoid \

aerokube/selenoid:1.10.7 \

-log-output-dir /opt/selenoid/logs Open the Selenoid UI once the tests are up and running: And here's . a video of it https://www.youtube.com/watch?v=Hm7s5ZjnVYQ&embedable=true We found the cause of the startup error. Great! Let’s move on. The third run. Building an emulator image As it turns out, the images of Selenoid emulators won’t work without Google Play services. To remedy this situation, you must build an emulator image yourself. The guys from aerokube have assembled everything you need for this: and . a repository with photos documentation the repository. Downloading Go to the folder. selenium Run the script and answer the questions. This is what it looks like in our case: ./automate_android.sh Specify Appium version: [1.18.1]

>> 1.18.1

Specify Android image type (possible values: "default", "google_apis", "google_apis_playstore", "android-tv", "android-wear"): [default]

>> google_apis

Specify Application Binary Interface (possible values: "armeabi-v7a", "arm64-v8a", "x86", "x86_64"): [x86]

>> x86

Specify Android version: [8.1]

>> 10.0

Specify device preset name if needed (e.g. "Nexus 4"):

>>

Specify SD card size, Mb: [500]

>>

Specify userdata.img size, Mb: [500]

>>

Are you building a Chrome Mobile image (for mobile web testing): [n]

>> y

Specify Chromedriver version if needed (required for Chrome Mobile):

>> 74.0.3729.6

Specify image tag: [selenoid/chrome-mobile:74.0]

>> android-emulator:10.0

Add Android quick boot snapshot? [y]

>> n When I saw the question Add Android quick boot snapshot?, I thought it was an emulator . But if you look at the , it calls a , which is needed to install APK applications. Basically, it doesn't give us any gain. snapshot code script We already use snapshot emulators , but we'll talk about that in other articles. to speed up container launches Once the image is built, we will be prompted to push it into the registry. Since we don't need that yet, we will kindly decline the offer: Push?  >> n We have put together a build with Google Play services. Remember to change the image parameter in browsers.json, and restart Selenoid. Now let's try rerunning the tests: [INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------ And of the test run. here’s a video https://www.youtube.com/watch?v=w-uzB7hg7g8&t=1s&embedable=true To sum up What we have done: Configured Selenoid to run Android tests. Learned how to check out the logs and videos to troubleshoot. Built our own emulator image with Google Play services. Something else I would like to tell you about: Selenoid timeouts. If your app is large, you might run into problems with timeouts. How we tried making the container run faster. The video shows that the run takes about a minute or so. How we tried running native Android tests written in Espresso on Selenoid. Spoiler alert: this works! Meanwhile, in the next part, we'll tell you how we scaled up the infrastructure and ran tests on iOS.

Stackera

stackera.io

11-50 employees

Since 2021

COMPANY RANKING

STACKERA

EVERGREEN INDEX #9929

Stackera WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

Stackera

stackera.io

11-50 employees

Since 2021

COMPANY RANKING

STACKERA

EVERGREEN INDEX #9929

RELATED COMPANIESRANK

STORIES ABOUT STACKERA

Stackera WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!