radixdev

class Queue(object):
    def __init__(self):
        self.stack1 = Stack()
        self.stack2 = Stack()
        
    def enqueue(self,p):
        self.stack1.push(p)
        
    def dequeue(self):
        #pop off all in 1 onto 2

radixdev

#!/usr/bin/env ruby

def show_user_prompt(msg)
  puts msg
  # flush our message to display
  STDOUT.flush
  return STDIN.gets.chomp
end

def get_user_input

radixdev

#!/usr/bin/env ruby

# take some text, make it into a big block of warning text

# like this:
# ***********************************************************************************************
# **                                       !! WARNING !!                                       **
# **             InAppMessageEvent was published, but no subscribers were found.               **
# **  This is likely an integration error. Please ensure that the AppboyInAppMessageManager is **
# **               registered as early as possible. Additionally, be sure to call              **

radixdev

.

radixdev

#!/usr/bin/env ruby

def pbpaste
  `pbpaste`
end

# get the raw text
papertrail_text = pbpaste()

# match for the error types

radixdev

<resources>
    <string name="app_name">Thinker</string>

    <!-- Slides for the intro -->
    <string name="welcome_slide_title">Welcome to your Trivia Assistant!</string>
    <string name="welcome_slide_description">I provide answers to trivia questions in the background while you play</string>

    <string name="what_is_trivia_slide_title">What does a trivia game look like?</string>
    <string name="what_is_trivia_slide_description">It\'s a question, followed by 3 answers.</string>

radixdev

{"lastUpload":"2019-08-20T19:07:01.697Z","extensionVersion":"v3.4.1"}

radixdev

openapi: 3.0.3

info:
  version: '3.0'
  title: 'V3'
  description: |
    Request Timing
    When methods on the SDK are called, it should generally enqueue data locally into offline storage, and make batched flushes to the above endpoints on a timed basis, or when explicitly requested by the user. In general, the default flush interval should be in the 10s of seconds (reasonable default may depend on the nature of the platform), and should be configurable.

    In the case of request failure (any non-20x response), the SDK should re-enqueue any failed events or attributes into local offline storage, and should begin an exponential slowdown of the flush interval, until a successful response is received. The backoff function should follow the decorrelated jitter algorithm below:

radixdev

Building solution Android (Debug)
Build started 8/18/2021 7:14:48 PM.
Environment at start of build:
COMMAND_MODE                   = unix2003
XPC_SERVICE_NAME               = com.microsoft.visual-studio.6216
ServiceHubUniqueLogDir         = vsmac
LANGUAGE                       = en
DOTNET_MSBUILD_SDK_RESOLVER_CLI_DIR = /usr/local/share/dotnet
PATH                           = /Library/Frameworks/Mono.framework/Commands:/Applications/Visual Studio.app/Contents/Resources:/Applications/Visual Studio.app/Contents/MacOS:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:~/.dotnet/tools:/usr/local/share/dotnet

radixdev

package com.radix.triviaassistant.models.util;

import android.os.Build;
import android.os.Bundle;

import com.radix.triviaassistant.BuildConfig;
import com.radix.triviaassistant.models.events.AnalyticsSingleton;


public class EmulatorDetector {