cmathew

// Define Joda-Time stub
val JODA_STUB = TestFiles.kotlin(
 """
 package org.joda.time

 class DateTime(
   private val moment: Int,
   private val zone: String
 ) {
   companion object {

cmathew

class WarnLocalDateConversion : Detector(), SourceCodeScanner {
 override fun getApplicableMethodNames(): List<String> = listOf("toLocalDateTime", "toLocalDate")

 override fun visitMethodCall(context: JavaContext, node: UCallExpression, method: PsiMethod) {
   val receiverClassName = (node.receiverType as PsiClassReferenceType).reference.qualifiedName
   if (receiverClassName == "org.joda.time.DateTime") {
     context.report(
       WARN_LOCAL_DATE_CONVERSION,
       node,
       context.getLocation(node),

u0705666

@Inject lateinit var suspendApi: SuspendApi


shownScope.launch {
view.showSearchLoading()
val result = suspendApi.getCategorizedAssetsSearch(searchStr, assetCategory?.categoryIdentifier)
view.hideSearchLoading()
when (result) {
     is ApiResult.Success -> {
   view.replaceListItems(getAssetListItem(result.data.categorizedAssets))

u0705666

private fun fetchAccounts() {
    val externalAccountLinkStatusObservable = linkCoordinator.linkStatusObservable
    val wealthFrontAccountObservable = accountRepository.wealthfrontAccountObservable
    val wealthFrontAccountRequestsObservable = accountRequestsRepository.wealthfrontAccountRequestObservable
    val calloutObservable = calloutsRepository.getCalloutsObservable(AccountListSection::class.java)
    
    autoDisposer.autoDispose(
        combineLatest(
            externalAccountLinkStatusObservable,
            wealthFrontAccountObservable,

u0705666

autoDispose(
 api.getCategorizedAssetsSearch(searchStr, assetCategory?.categoryIdentifier)
   .observeOn(mainThread())
   .doOnSubscribe { view.showSearchLoading() }
   .doOnTerminate { view.hideSearchLoading() }
   .subscribe(
     {
         view.replaceListItems(getAssetListItem(it.categorizedAssets))
     },
     {

xanathar

{
    // The following are sample configurations for common case scenarios of debugging
    // Rust in Visual Studio Code
    //
    // For syntax, visit: https://go.microsoft.com/fwlink/?linkid=830387
    //
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch an application",

danieldogeanu

To rename your Git master branch to main, you must do the following steps:

1. Navigate to your repository in the command line and issue the following commands: - git branch -m master main - git push -u origin main

2. Change your default branch on GitHub by going to your GitHub repository in your browser, and navigate to Settings > Branches and click on the dropdown and switch from master to main and click Update (this will only show if you have two or more branches). The main branch is now your default branch.

3. Update the tracking of the branch from your command line with the following command: - git branch -u origin/main main

xorxornop

{
    // Launch configuration for debugging Rust code inside VS Code with LLDB
    // This configuration is used by the extension 'LLDB Debugger'
    // 
    // The necessary extension may be downloaded at: https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb
    // Alternatively, the repository for it may be found at: https://github.com/vadimcn/vscode-lldb.git
    
    "version": "0.1.0",
    "configurations": [
        {

Pulimet

Hi All!

I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future.
Feel free to request any features you'd like to see, and I'll prioritize them accordingly.
One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it.

Here's the link to the repository:  https://github.com/Pulimet/ADBugger

App Description:
ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups.

Jim-Bar

About YUV formats

First of all: YUV pixel formats and Recommended 8-Bit YUV Formats for Video Rendering. Chromium's source code contains good documentation about those formats too: chromium/src/media/base/video_types.h and chromium/src/media/base/video_frame.cc (search for RequiresEvenSizeAllocation(), NumPlanes() and those kinds of functions).

YUV?

You can think of an image as a superposition of several planes (or layers in a more natural language). YUV formats have three planes: Y, U, and V.

Y is the luma plane, and can be seen as the image as grayscale. U and V are reffered to as the chroma planes, which are basically the colours. All the YUV formats have these three planes, and differ by the different orderings of them.