Any docs on how to get gem set up for local development?

Steps to reproduce:

clone repo + cd into dir
bundle install
bundle exec rake =>

ActiveRecord::ConnectionNotEstablished:
  No connection pool with 'primary' found.

bundle exec rake appraisal =>

Runs SOME specs but then fails with:
>> BUNDLE_GEMFILE=/Users/joel/Development/sinatra-activerecord/gemfiles/activerecord_4.0.gemfile bundle exec rake                                                                                [7/557]
/Users/joel/.rbenv/versions/2.4.0/bin/ruby -I/Users/joel/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/rspec-core-3.6.0/lib:/Users/joel/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/rspec-support-3.6.0/lib /Users/joel/.rbenv/versions/2.4.0/lib/ruby/gem
s/2.4.0/gems/rspec-core-3.6.0/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
db/migrate/20170705042613_create_users.rb
-- initialize_schema_migrations_table()
   -> 0.0026s
..F

Failures:

  1) the sinatra extension establishes the connection with a database url
     Failure/Error: ActiveRecord::Base.configurations[environment.to_s] = ActiveRecord::ConnectionAdapters::ConnectionSpecification::ConnectionUrlResolver.new(spec).to_hash

     NameError:
       uninitialized constant ActiveRecord::ConnectionAdapters::ConnectionSpecification::ConnectionUrlResolver
     # ./lib/sinatra/activerecord.rb:55:in `database='
     # ./spec/sinatra/activerecord_spec.rb:34:in `block (2 levels) in <top (required)>'

Finished in 0.1212 seconds (files took 0.76077 seconds to load)
3 examples, 1 failure

Is there a series of steps to get the specs to run reliably?

Heya @jayroh , the issue arise because the gem code actually relies on some method that is implemented on ActiveRecord 4.1.  I have since removed support for AR below 4.1, it should work fine now if you clone and run it again, please open another issue if you found another problem, thanks!


typescript definition file?

Please include a typescript definition file.

Hi, is this something you might be able to contribute?

Yes, I think so. I created the definition files over the weekend. I just need to figure out how to publish it to the @types organization on npm. This will be a first for me. I could also try to include it directly in your source code. What do you suggest?
Joe
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Matt Walker<EMAIL_ADDRESS>Date: 8/17/20 5:27 AM (GMT-05:00)
To: walkermatt/ol-popup<EMAIL_ADDRESS>Cc: jwr3408<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [walkermatt/ol-popup] typescript definition file? (#231)
Hi, is this something you might be able to contribute?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/walkermatt/ol-popup/issues/231#issuecomment-674769299, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADNO7OIJAYXFMJWGISTSLVDSBDZWJANCNFSM4P7ZJPMA.

I'm wondering if it might be possible to create a definition directly from the JSDoc comments which are currently used to create the API docs in the readme.
Something like:
npx typescript src/*.js --declaration --allowJs --emitDeclarationOnly --outDir ./src

TypeScript: Handbook - Creating .d.ts Files from .js files.
I think adding the .d.ts file to this repo is probably best as it keeps the JS and types together.
I guess the other option is to switch to TypeScript; it's a very small project so it might not be too onerous...


error while creating account

Hello,
I try to install the ha google photo plugin,
I followed the github procedure, I created a client with id and secret code, activated api, ...
all was fine until the oauth screen :  when I click on my google account and accept the conditions, I receive this screen :
[https://www.googleapis.com/auth/userinfo.email&authuser=0&prompt=consent]
**

You are receiving this error either because your input OAuth2 scope name is invalid or it refers to a newer scope that is outside the domain of this legacy API.
This API was built at a time when the scope name format was not yet standardized. This is no longer the case and all valid scope names (both old and new) are catalogued at https://developers.google.com/identity/protocols/oauth2/scopes.

**
Version of the custom_component
latest
Can someone tell me what I did wrong?
Thanks in advance,
-->Michaël

It can be a bit tricky to debug these, could you verify that your setup looks like:
OAuth consent screen setup

OAuth consent screen edit, step1

OAuth consent screen edit, step2

OAuth consent screen edit, step3

OAuth consent screen edit, step4

Credentials


UI Tests no longer run after Firebase/Core pod install

Describe your environment

Xcode version: 10.1
Firebase SDK version: 5.13.0
Firebase Component: Core
Component version: 5.13.0
CocoaPods: 1.5.3

Describe the problem
When I installed the Firebase Core pod and try and run my test target it runs my unit tests correctly buy fails to launch my UI tests giving the following error:
BrokenFirebaseCoreUITests-Runner.app (80714) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying error: The test runner failed to load the test bundle. Executable cannot be loaded for some other reason, such as a problem with a library it depends on or a code signature/entitlements mismatch.))
I've noticed a few similar issue on here but none specifically mention just the UI Test target failing.
Steps to reproduce:
I've attached a test project that replicates the issue. Simply run the test target (CMD+U) to see the error.
BrokenFirebaseCore.zip
Relevant Code:
I found one workaround solutions which is to add $(FRAMEWORK_SEARCH_PATHS) to the UI Test target's Runpath search paths.
Is this workaround recommended?

Thanks for the report, and producing a repro! We can take a look today to see if this is expected or not.
Also, thanks for adding the workaround! It doesn't sound unreasonable that it could be expected to include that, but it looks like the inherit! :search_paths is added appropriately in the Podfile.
Will update this issue when we figure things out.

Hi, this might be related to the issue I found:
https://github.com/firebase/firebase-ios-sdk/issues/2151

@MrAPolk Thanks for the report and great minimal, reproducible example.
This issue seems to be a CocoaPods bug and discussed at https://stackoverflow.com/questions/34990175/test-target-x-encountered-an-error-early-unexpected-exit-operation-never-finis.
Your workaround is the most popular answer.  I also verified that hujunfeng's answer of un-nesting the test target also works.
@code-surf - Thanks but doesn't seem related to #2151 since the pod version mismatch doesn't occur here.
I'm going to close the issue here since there are workarounds and this is likely a CocoaPods issue. The next step would be creating an issue on the CocoaPods repo.

No difference with the latest CocoaPods 1.6.0.


__dirname is /

The title is clear enough. I have tried to set node.__dirname: false in webpack configs. But got this error: ReferenceError: __dirname is not defined.
I expect __dirname to be the absolute path to the file.

We don't support customizing the webpack configuration. If you've ejected we're unable to help you.


detox test fails because of app crash when Detox Instruments is installed

Describe the bug
When Detox Instruments is installed, demo-react-native and any other apps crash just after starting detox test -c ios.sim.debug. Tests fails after 120s (timeout). If Detox Instruments is uninstalled, app no longer crashes and detox test works as expected.
To Reproduce

[x] I have tested this issue on the latest Detox release and it still reproduces

Provide the steps necessary to reproduce the issue. If you are seeing a regression, try to provide the last known version where the issue did not reproduce.

brew tap wix/brew
brew cask install detox-instruments
git clone https://github.com/wix/Detox.git
cd Detox/examples/demo-react-native
yarn install
yarn start
detox build --configuration ios.sim.debug
detox test --configuration ios.sim.debug -l "trace"

If possible, please provide a small demo project that reproduces the issue, or attach a video with the reproduction - this would be very appreciated.
Expected behavior
detox test should succeed for examples/demo-react-native instead of failing after timeout.
Environment (please complete the following information):

Detox: 13.0.0
React Native: 0.59.8
Node: 10.16.0 (also tested on 10.14.2)
Device: iPhone X Simulator
Xcode: 10.2.1 (10E1001)
iOS: 12.2
macOS: 10.14.5

Device and Verbose Detox Logs
Provide the device and "trace" Detox logs so we can understand what happened.  To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn DC8FA5C9-9679-4E67-AFCE-94A48415A0FD log stream --level debug --style compact --predicate 'processImagePath beginsWith "/Users/joaobertacchi/Library/Developer/CoreSimulator/Devices/DC8FA5C9-9679-4E67-AFCE-94A48415A0FD/data/Containers/Bundle/Application/BB853784-36C9-4A45-8E5F-A52F0EDFC9B1/example.app"'
detox[39345] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onLaunchApp({ bundleId: 'com.wix.demo.react.native',
  deviceId: 'DC8FA5C9-9679-4E67-AFCE-94A48415A0FD',
  launchArgs:
   { detoxServer: 'ws://localhost:62436',
     detoxSessionId: '8f5f5992-2601-bc00-d073-0ac20b29fada' },
  pid: 39345 })
detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"isReady","params":{},"messageId":-1000}
detox[39314] TRACE: [DetoxServer.js/MESSAGE] role=tester action=isReady (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=testee not connected, cannot fw action (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] DEBUG: [DetoxServer.js/LOGIN] role=testee, sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada
detox[39314] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=testee, sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada
detox[39314] TRACE: [DetoxServer.js/MESSAGE] role=testee action=ready (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"ready","messageId":-1000,"params":{}}

detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"waitForActive","params":{},"messageId":1}
detox[39314] TRACE: [DetoxServer.js/MESSAGE] role=tester action=waitForActive (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] TRACE: [DetoxServer.js/MESSAGE] role=testee action=waitForActiveDone (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"waitForActiveDone","messageId":1,"params":{}}

detox[39314] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeAll()
  Example
detox[39314] TRACE: [Detox.js/DETOX_BEFORE_EACH] running test: "Example should have welcome screen"
detox[39314] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeEach({ title: 'should have welcome screen',
  fullName: 'Example should have welcome screen',
  status: 'running' })
detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"reactNativeReload","params":{},"messageId":-1000}
detox[39314] TRACE: [DetoxServer.js/MESSAGE] role=tester action=reactNativeReload (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] TRACE: [DetoxServer.js/MESSAGE] role=testee action=AppWillTerminateWithError (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] TRACE: [DetoxServer.js/MESSAGE] role=testee action=AppWillTerminateWithError (sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada)
detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"AppWillTerminateWithError","messageId":-10000,"params":{"threadNumber":1,"errorDetails":"[<RCTCxxBridge 0x7faed7c03880> valueForUndefinedKey:]: this class is not key value coding-compliant for the key viewRegistry.\n(\n\t0   CoreFoundation                      0x000000010fe3e6fb __exceptionPreprocess + 331\n\t1   libobjc.A.dylib                     0x000000010e5a5ac5 objc_exception_throw + 48\n\t2   CoreFoundation                      0x000000010fe3e269 -[NSException raise] + 9\n\t3   Foundation                          0x000000010e01b45a -[NSObject(NSKeyValueCoding) valueForUndefinedKey:] + 226\n\t4   Foundation                          0x000000010e01a29f -[NSObject(NSKeyValueCoding) valueForKey:] + 281\n\t5   DTXProfiler                         0x0000000127b09df1 ____dtxinst_RCTBridge_setUp_block_invoke + 176\n\t6   libdispatch.dylib                   0x000000011236ad02 _dispatch_client_callout + 8\n\t7   libdispatch.dylib                   0x00000001123775fd _dispatch_lane_barrier_sync_invoke_and_complete + 94\n\t8   EarlGrey                            0x0000000122056a3e grey_dispatch_sync + 238\n\t9   DTXProfiler                         0x0000000127b09a11 __dtxinst_RCTBridge_setUp + 119\n\t10  example                             0x000000010c55392e __19-[RCTBridge reload]_block_invoke + 94\n\t11  EarlGrey                            0x0000000122057fa2 __60-[GREYDispatchQueueTracker grey_dispatchAsyncCallWithBlock:]_block_invoke + 50\n\t12  libdispatch.dylib                   0x0000000112369ccf _dispatch_call_block_and_release + 12\n\t13  libdispatch.dylib                   0x000000011236ad02 _dispatch_client_callout + 8\n\t14  libdispatch.dylib                   0x0000000112376a50 _dispatch_main_queue_callback_4CF + 1276\n\t15  CoreFoundation                      0x000000010fda58a9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9\n\t16  CoreFoundation                      0x000000010fd9ff56 __CFRunLoopRun + 2310\n\t17  CoreFoundation                      0x000000010fd9f302 CFRunLoopRunSpecific + 626\n\t18  EarlGrey                            0x00000001220798fd -[GREYRunLoopSpinner grey_checkConditionInActiveMode:] + 381\n\t19  EarlGrey                            0x0000000122078582 -[GREYRunLoopSpinner spinWithStopConditionBlock:] + 466\n\t20  EarlGrey                            0x00000001220cda7c -[GREYUIThreadExecutor executeSyncWithTimeout:block:error:] + 1500\n\t21  EarlGrey                            0x00000001220cd455 -[GREYUIThreadExecutor executeSync:error:] + 309\n\t22  Detox                               0x000000010d09a6e5 __45-[EarlGreyImpl(Detox) detox_safeExecuteSync:]_block_invoke + 137\n\t23  CoreFoundation                      0x000000010fda5aec __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12\n\t24  CoreFoundation                      0x000000010fda52b0 __CFRunLoopDoBlocks + 336\n\t25  CoreFoundation                      0x000000010fda010b __CFRunLoopRun + 2747\n\t26  CoreFoundation                      0x000000010fd9f302 CFRunLoopRunSpecific + 626\n\t27  GraphicsServices                    0x00000001154cd2fe GSEventRunModal + 65\n\t28  DTXProfiler                         0x0000000127b1cba1 __dtxinst_UIApplication_run + 176\n\t29  Detox                               0x000000010d09dd34 __detox_UIApplication_run + 365\n\t30  UIKitCore                           0x000000011a6c4ba2 UIApplicationMain + 140\n\t31  example                             0x000000010c44d360 main + 112\n\t32  libdyld.dylib                       0x00000001123d8541 start + 1\n\t33  ???                                 0x0000000000000006 0x0 + 6\n)","queueName":"com.wix.activeProfilersQueue"}}

detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"AppWillTerminateWithError","messageId":-10000,"params":{"threadNumber":1,"errorDetails":"Signal 4 was raised\n(\n\t0   Detox                               0x000000010d0a7b56 _ZL16__DTXHandleCrashP11NSExceptionP8NSNumberP8NSString + 497\n\t1   Detox                               0x000000010d0a78db _ZL17__DTXHandleSignali + 61\n\t2   libsystem_platform.dylib            0x000000011273cb5d _sigtramp + 29\n\t3   ???                                 0x3e91082200000001 0x0 +<PHONE_NUMBER>096487425\n\t4   Detox                               0x000000010d0a6606 -[DetoxManager notifyOnCrashWithDetails:] + 293\n\t5   Detox                               0x000000010d0a7c1b _ZL16__DTXHandleCrashP11NSExceptionP8NSNumberP8NSString + 694\n\t6   Detox                               0x000000010d0a7686 _ZL15__dtx_terminatev + 117\n\t7   libc++abi.dylib                     0x0000000112260a2e _ZSt11__terminatePFvvE + 8\n\t8   libc++abi.dylib                     0x0000000112260aa3 _ZSt9terminatev + 51\n\t9   libdispatch.dylib                   0x000000011236ad16 _dispatch_client_callout + 28\n\t10  libdispatch.dylib                   0x00000001123775fd _dispatch_lane_barrier_sync_invoke_and_complete + 94\n\t11  EarlGrey                            0x0000000122056a3e grey_dispatch_sync + 238\n\t12  DTXProfiler                         0x0000000127b09a11 __dtxinst_RCTBridge_setUp + 119\n\t13  example                             0x000000010c55392e __19-[RCTBridge reload]_block_invoke + 94\n\t14  EarlGrey                            0x0000000122057fa2 __60-[GREYDispatchQueueTracker grey_dispatchAsyncCallWithBlock:]_block_invoke + 50\n\t15  libdispatch.dylib                   0x0000000112369ccf _dispatch_call_block_and_release + 12\n\t16  libdispatch.dylib                   0x000000011236ad02 _dispatch_client_callout + 8\n\t17  libdispatch.dylib                   0x0000000112376a50 _dispatch_main_queue_callback_4CF + 1276\n\t18  CoreFoundation                      0x000000010fda58a9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9\n\t19  CoreFoundation                      0x000000010fd9ff56 __CFRunLoopRun + 2310\n\t20  CoreFoundation                      0x000000010fd9f302 CFRunLoopRunSpecific + 626\n\t21  EarlGrey                            0x00000001220798fd -[GREYRunLoopSpinner grey_checkConditionInActiveMode:] + 381\n\t22  EarlGrey                            0x0000000122078582 -[GREYRunLoopSpinner spinWithStopConditionBlock:] + 466\n\t23  EarlGrey                            0x00000001220cda7c -[GREYUIThreadExecutor executeSyncWithTimeout:block:error:] + 1500\n\t24  EarlGrey                            0x00000001220cd455 -[GREYUIThreadExecutor executeSync:error:] + 309\n\t25  Detox                               0x000000010d09a6e5 __45-[EarlGreyImpl(Detox) detox_safeExecuteSync:]_block_invoke + 137\n\t26  CoreFoundation                      0x000000010fda5aec __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12\n\t27  CoreFoundation                      0x000000010fda52b0 __CFRunLoopDoBlocks + 336\n\t28  CoreFoundation                      0x000000010fda010b __CFRunLoopRun + 2747\n\t29  CoreFoundation                      0x000000010fd9f302 CFRunLoopRunSpecific + 626\n\t30  GraphicsServices                    0x00000001154cd2fe GSEventRunModal + 65\n\t31  DTXProfiler                         0x0000000127b1cba1 __dtxinst_UIApplication_run + 176\n\t32  Detox                               0x000000010d09dd34 __detox_UIApplication_run + 365\n\t33  UIKitCore                           0x000000011a6c4ba2 UIApplicationMain + 140\n\t34  example                             0x000000010c44d360 main + 112\n\t35  libdyld.dylib                       0x00000001123d8541 start + 1\n\t36  ???                                 0x0000000000000006 0x0 + 6\n)","queueName":"com.wix.activeProfilersQueue"}}

    1) "before each" hook for "should have welcome screen"
detox[39314] TRACE: [Detox.js/DETOX_AFTER_EACH] failed test: "Example should have welcome screen"
detox[39314] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onAfterEach({ title: 'should have welcome screen',
  fullName: 'Example should have welcome screen',
  status: 'failed',
  timedOut: false })
detox[39314] ERROR: [Detox.js/APP_CRASH] App crashed in test 'Example should have welcome screen', here's the native stack trace:
Signal 4 was raised
(
	0   Detox                               0x000000010d0a7b56 _ZL16__DTXHandleCrashP11NSExceptionP8NSNumberP8NSString + 497
	1   Detox                               0x000000010d0a78db _ZL17__DTXHandleSignali + 61
	2   libsystem_platform.dylib            0x000000011273cb5d _sigtramp + 29
	3   ???                                 0x3e91082200000001 0x0 +<PHONE_NUMBER>096487425
	4   Detox                               0x000000010d0a6606 -[DetoxManager notifyOnCrashWithDetails:] + 293
	5   Detox                               0x000000010d0a7c1b _ZL16__DTXHandleCrashP11NSExceptionP8NSNumberP8NSString + 694
	6   Detox                               0x000000010d0a7686 _ZL15__dtx_terminatev + 117
	7   libc++abi.dylib                     0x0000000112260a2e _ZSt11__terminatePFvvE + 8
	8   libc++abi.dylib                     0x0000000112260aa3 _ZSt9terminatev + 51
	9   libdispatch.dylib                   0x000000011236ad16 _dispatch_client_callout + 28
	10  libdispatch.dylib                   0x00000001123775fd _dispatch_lane_barrier_sync_invoke_and_complete + 94
	11  EarlGrey                            0x0000000122056a3e grey_dispatch_sync + 238
	12  DTXProfiler                         0x0000000127b09a11 __dtxinst_RCTBridge_setUp + 119
	13  example                             0x000000010c55392e __19-[RCTBridge reload]_block_invoke + 94
	14  EarlGrey                            0x0000000122057fa2 __60-[GREYDispatchQueueTracker grey_dispatchAsyncCallWithBlock:]_block_invoke + 50
	15  libdispatch.dylib                   0x0000000112369ccf _dispatch_call_block_and_release + 12
	16  libdispatch.dylib                   0x000000011236ad02 _dispatch_client_callout + 8
	17  libdispatch.dylib                   0x0000000112376a50 _dispatch_main_queue_callback_4CF + 1276
	18  CoreFoundation                      0x000000010fda58a9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
	19  CoreFoundation                      0x000000010fd9ff56 __CFRunLoopRun + 2310
	20  CoreFoundation                      0x000000010fd9f302 CFRunLoopRunSpecific + 626
	21  EarlGrey                            0x00000001220798fd -[GREYRunLoopSpinner grey_checkConditionInActiveMode:] + 381
	22  EarlGrey                            0x0000000122078582 -[GREYRunLoopSpinner spinWithStopConditionBlock:] + 466
	23  EarlGrey                            0x00000001220cda7c -[GREYUIThreadExecutor executeSyncWithTimeout:block:error:] + 1500
	24  EarlGrey                            0x00000001220cd455 -[GREYUIThreadExecutor executeSync:error:] + 309
	25  Detox                               0x000000010d09a6e5 __45-[EarlGreyImpl(Detox) detox_safeExecuteSync:]_block_invoke + 137
	26  CoreFoundation                      0x000000010fda5aec __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
	27  CoreFoundation                      0x000000010fda52b0 __CFRunLoopDoBlocks + 336
	28  CoreFoundation                      0x000000010fda010b __CFRunLoopRun + 2747
	29  CoreFoundation                      0x000000010fd9f302 CFRunLoopRunSpecific + 626
	30  GraphicsServices                    0x00000001154cd2fe GSEventRunModal + 65
	31  DTXProfiler                         0x0000000127b1cba1 __dtxinst_UIApplication_run + 176
	32  Detox                               0x000000010d09dd34 __detox_UIApplication_run + 365
	33  UIKitCore                           0x000000011a6c4ba2 UIApplicationMain + 140
	34  example                             0x000000010c44d360 main + 112
	35  libdyld.dylib                       0x00000001123d8541 start + 1
	36  ???                                 0x0000000000000006 0x0 + 6
)
detox[39314] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeTerminateApp({ deviceId: 'DC8FA5C9-9679-4E67-AFCE-94A48415A0FD',
  bundleId: 'com.wix.demo.react.native' })
detox[39314] DEBUG: [exec.js/EXEC_CMD, #8] /usr/bin/xcrun simctl terminate DC8FA5C9-9679-4E67-AFCE-94A48415A0FD com.wix.demo.react.native
detox[39314] DEBUG: [exec.js/EXEC_TRY, #8] Terminating com.wix.demo.react.native...
detox[39314] TRACE: [exec.js/EXEC_SUCCESS, #8]
detox[39314] DEBUG: [exec.js/EXEC_SUCCESS, #8] com.wix.demo.react.native terminated
detox[39314] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeLaunchApp({ bundleId: 'com.wix.demo.react.native',
  deviceId: 'DC8FA5C9-9679-4E67-AFCE-94A48415A0FD',
  launchArgs:
   { detoxServer: 'ws://localhost:62436',
     detoxSessionId: '8f5f5992-2601-bc00-d073-0ac20b29fada' } })
detox[39314] DEBUG: [exec.js/EXEC_CMD, #9] SIMCTL_CHILD_DYLD_INSERT_LIBRARIES="/Users/joaobertacchi/Library/Detox/ios/d77b206c357df311fadf7da8273e4bce8157091f/Detox.framework/Detox" /usr/bin/xcrun simctl launch DC8FA5C9-9679-4E67-AFCE-94A48415A0FD com.wix.demo.react.native --args -detoxServer "ws://localhost:62436" -detoxSessionId "8f5f5992-2601-bc00-d073-0ac20b29fada"
detox[39314] DEBUG: [exec.js/EXEC_TRY, #9] Launching com.wix.demo.react.native...
detox[39314] DEBUG: [DetoxServer.js/DISCONNECT] role=testee, sessionId=8f5f5992-2601-bc00-d073-0ac20b29fada
detox[39314] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"testeeDisconnected","messageId":-49642}

We test this scenario in CI and it succeeds.
https://jenkins-oss.wixpress.com/view/Detox/job/detox-demo-projects-ios-59-master/
I see you are building in debug. What happens if you build in release?

Also, just to make sure, which version of Detox Instruments do you have installed?

I found the issue. Moving the issue to Detox Instruments.


Add Gitlab integration

Thanks a lot @sagikazarmark, this is great!

Please take a look at the README changes I did. Some links are missing IMO, and the stable link for gitlab also points to the master, those must be updated once you release a new version.


[type:feat] Modify shenyu sdk and add shenyu.instance.clientEnable

shenyu.instance.enabled is true to register itself as a gateway to the center
So add shenyu.instance.clientEnable for shenyu-sdk

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #4060 (bdc09c2) into master (c986aad) will decrease coverage by 0.31%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #4060      +/-   ##
============================================
- Coverage     70.01%   69.69%   -0.32%
+ Complexity     6749     6710      -39
============================================
  Files           935      935
  Lines         25443    25438       -5
  Branches       2290     2287       -3
============================================
- Hits          17814    17730      -84
- Misses         6232     6307      +75
- Partials       1397     1401       +4

Impacted Files
Coverage Δ

.../org/apache/shenyu/common/config/ShenyuConfig.java
72.56% <0.00%> (-0.67%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
68.75% <0.00%> (-31.25%)
:arrow_down:

.../client/server/consul/ShenyuConsulConfigWatch.java
60.41% <0.00%> (-25.00%)
:arrow_down:

...controller/ShenyuClientHttpRegistryController.java
77.77% <0.00%> (-22.23%)
:arrow_down:

...yu/sync/data/http/refresh/AbstractDataRefresh.java
68.96% <0.00%> (-13.80%)
:arrow_down:

...ruptor/RegisterClientServerDisruptorPublisher.java
52.94% <0.00%> (-11.77%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
54.25% <0.00%> (-9.58%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
81.63% <0.00%> (-8.17%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

... and 36 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


mineral counting app

This app might be mobile app or web app.
features

import thin section image. then, click to count the mineral composition on 10x10 grid
plot to QAP chart

working on granite this repo


The ByConity Server connection failed

Question
According to the document: ByConity集群搭建与TPC-DS Benchmark实践, Error thrown when connecting ByConity Server during verification deployment after docker setup:
run ./clickhouse client  then
' error while loading shared libraries: libfdb_c.so: cannot open shared object file:  No such file or directory'  ; who can give me more advice

The simplest way to solve it is download fdb client binary from here https://github.com/apple/foundationdb/releases and install foundationdb-clients_7.1.27-1_xx. There is one example in this doc https://github.com/ByConity/ByConity/tree/master/packages


RootSchema: pass interface{} as schema and validate interface{}

To set schema from interface{} (in addition to UnmarshalJSON)
To validate data from interface{} (in addition to ValidateBytes)
Is it ok to add these APIs? Not sure what would be the best names for the methods, happy to make PR

What's the advantage over just converting to JSON or bytes and then calling the functions?

To avoid extra serialisation and deserialisation when schema and data already deserialised. Available functions deserialise under the hood, I have to serialise the schema and data to pass them in - I am just using Schema for validation (which is a bit ugly) and there is no equivalent API to initialise the schema.

In my case schema is deserialised because it is generated with code. Data is deserialised to avoid extra deserialisation after validation.

I see.
For extra context this is how I use this package:
I have a list of schemas which are JSON files which get loaded with the app. At the same time I use those JSON schema files to generate go structures. Then incoming data is being validated against the schema and on success unmarshalled.
It does seem like those extra functions could be useful.

Related to #53 which also asks to extended the input source.

Isn't Schema.Validate what you want?

I might be getting this wrong, but assuming my understanding is correct, you want to be able to validate arbitrary go structures against the schema. While definitely interesting, it's an interesting bit of work as some of the internals rely on some json specific conversions and behavior. As such the bridge would be to have those structures implement the json marshaller interfaces but then that would mean you can simply pass them in without having to do anything against the current implementation.
Agree that a bit extra efficiency could be squeezed in the ideal case as we avoid unnecessary serialization/deserialization however that opens jsonschema to a much wider surface for "unplanned" usage of the lib which would be a bit harder to support long term.
Also, this applies more to the older version and the current iteration might be closer to what you expect.
I'll close for now, if this is still an issue, happy to reopen.


More mysql metrics

This PR adds additional MySQL metrics to the mysql plugin. These additional measurements can be filtered out using the pass/drop filters in case there is a concern around storing more data.
I updated mysql_test.go with the new mappings and "make test" passes for me.

awesome, thanks for your contribution @nickscript0!
two things before I can merge:

sign the CLA: https://influxdb.com/community/cla.html
add your change under "features" in the CHANGELOG.md

thanks much!

I did sign the CLA previously so should be on the list (let me know if I need to sign again) and CHANGELOG.md is updated with this change now.

you're right, I didn't see your name because our internal list hasn't been sorted :sweat_smile:, I'll merge this, thanks again! :+1:


Not prepend "[MISSING]" in debug mod if Current Language set as "en"

In my application source code and default language - Russian. In any other language, if the string is not translated, it is added to the beginning "[MISSING]".

However, if the load interface in English, it does not happen.

Resolve:
		gettextCatalog.debug = true;
		gettextCatalog.baseLanguage = 'ru_RU';
		gettextCatalog.currentLanguage = 'ru_RU';


[esphome] adding a option for git init container

Signed-off-by: nolte<EMAIL_ADDRESS>Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [radarr])

closes #17

Thanks for contributing!


Specify center of a circle

I want to specify the center point of a circle. but unable to. Here is a the code. I want to include another circle with radius=1.25 and center at [0.75,-0.5,0].
How can I do this?
Or if I can draw a circle with three non-linear points?
Thanks in advance :)
   from big_ol_pile_of_manim_imports import *
   class Shapes(Scene):
   def construct(self):
    circle = Circle(
        radius = 2.5,
    )

    triangle = Polygon(
        np.array([1.5, 2, 0]),
        np.array([-2, -1.5, 0]),
        np.array([2, -1.5, 0]),
    )

    altitutea = Line(
        np.array([1.5, 2, 0]),
        np.array([1.5, -1.5, 0]),
    )

    altituteb = Line(
        np.array([2, -1.5, 0]),
        np.array([0, 0.5, 0]),
    )
    altitutec = Line(
        np.array([-2, -1.5, 0]),
        np.array([1.92, -0.94, 0]),
    )
    pointa = Dot(
        [1.5, 2, 0],
    )
    pointb = Dot(
        [-2, -1.5, 0],
    )
    pointc = Dot(
        [2, -1.5, 0],
    )
    self.play(ShowCreation(triangle))
    self.play(FadeIn(circle))
    self.play(ShowCreation(altitutea), ShowCreation(altituteb), ShowCreation(altitutec))
    self.play(FadeIn(pointa),FadeIn(pointb),FadeIn(pointc))

`

You can call circle.move_to(point) to put it at a given place.
Or, on initialization, you could add a parameter "arc_center"

You can call circle.move_to(point) to put it at a given place.
Or, on initialization, you could add a parameter "arc_center"

You can call circle.move_to(point) to put it at a given place.
Or, on initialization, you could add a parameter "arc_center"

Thank you very much:)

How can I draw circumcircle of a triangle ? Is there any dedicated command?

No such command exists right now.  You could implement it yourself, doing the math to write the inradius and the center

Thanks for the help & manim is really awesome! <3


Pass IncidentState to notifications for richer templating

This series adds useFullContext notification setting. If it's set to true, instead of the template subject/body, the notification template gets passed the whole IncidentState. This allows for richer notifications, e.g.:
template common {
    subject = {{.Alert.Vars.title}} on {{.Group.host}}
    body = `<h1><a href="{{.Incident}}">[{{.Last.Status}}] {{.Alert.Vars.title}} on {{.Group.host}}</a></h1>`
}

notification some_webservice {
    post = http://localhost:8000/some_webservice
    useFullContext = true
    body = `{
        "author": "Bosun",
        "thread_id": "{{.AlertKey}}",
        "status": "{{.CurrentStatus}}",
        "subject": "{{.Subject}}",
        "body": {{.Body|json}}
    }`
    contentType = application/json
}

Not sure I understand what actually failed in the Travis build :(

Oh, it was gofmt, should be fixed now.

gofmt is happy but Travis is not :/

I believe we want to solve this problem a slightly different way, by allowing an template to define an arbitrary set of subtemplates, and the notification then just needs to pick which one, or maybe something like that. It is hard to do in a way that decouples notifications from alerts. Planning to address this for the next release.

will be fixed with https://github.com/bosun-monitor/bosun/pull/2135


feat (ICSAAS-452): implement custom events for a couple of actions

enhance frontend to implement Custom Events
new file serviceEvents.ts where all Custom Events are created

@ana-zdravkovikj there is a conflict in your commits, please update your branch.
Also please add the data as discussed in the ticket

PR looks good, just few comments and the one from Kevin in regards of the callback.
Thanks @ana-zdravkovikj


run bisecting bugs for sqlright_sqlite TLP failed

when i run the shell "run_sqltie_bisecting.sh" in sqlright/sqlite/scripts, i got an error like this:

how to fix it?

Thank you for the error information. The bug is fixed in commit: 0eca86543c.
To patch the code, you need to

pull the latest code changes from this github repo.
rerun the setup_sqlite.sh script in SQLite/scripts.
rerun the command bash run_sqlite_bisecting.sh SQLRight  -O TLP to bisect the detected bugs.

Please let us know if you have more questions.

thank you bery much


fix: status code for versions that already have a build queued

I also want to add some tests for this case, though I'm not sure how to trigger the correct conditions for this error to pop in the current integration test suite.

I'm not sure how to trigger the correct conditions for this error to pop in the current integration test suite

Manually create a build in the database like seen here: https://github.com/denoland/deno_registry2/blob/main/api/async/publish_test.ts#L17-L26. Then trigger the build for that version, and you should get the error.


Applied fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Created by the friendly StyleCI robot.

@cpatrick PTAL.


Full set of changes to ISSUE_TEMPLATE.md

A few changes got missed in https://github.com/tensorflow/tensorflow/pull/9385, so I'm adding them back here.

Thanks!


retry aborted operation on bucket creation in unit-tests

S3 tests working under the same bucket in parallel (still under different prefixes so they don't clobber each other) are often hit by their create-bucket operations getting aborted. We are not deleting the bucket itself anywhere to be hitting an eventual-consistency race with the create-bucket operation, so not sure which other operation it is conflicting with though. I can find out if needed.

@Shrekster See #340 for an alternate approach.

Closing in favor of the look-before-you-leap solution for this problem. Thank Julio!


fix(pkg/kube): make internal cache miss not an error

This fixes #1193 by not making an internal cache miss an error, and instead making it a warning. It will default to the original object, if one exists, instead. This should fix at least one scenario of when helm loses track of the real state of the a config.
This could have issues since it uses the existing object in place of the cached one. Let me know if there are better ways of handling this, since my comment on the issue didn't have anything I decided to propose my fix but am open to any better way of fixing this!
Thanks! :sparkles:

@bacongobbler, or anyone else. We've hit #1193 multiple times in our great kubernetes migration journey so far, patching the deployment to use my code fix has solved every single one! Would be awesome if we had some insight on this!

hey @jaredallard, could you please write up a unit test to cover this failure scenario? That way we can prevent this from occurring in the future. We have been putting more focus on unit tests to allow us to catch regressions earlier in the release process. Thanks so much for taking a shot at fixing this!

cc @adamreese, does this look like something we should port to dev-v3?

@bacongobbler sure, but it might be a bit until I can get around to it

No problem @jaredallard. Because of my findings I don't think we're going to accept this PR as it currently stands, but thank you so much for looking into this!

I agree this is a big issue. Part of the helm (and k8s) promise is that we declare what we want and we get it. helm upgrade --install (+ --force ! ) not working because of apparently minor runtime issues really reduces the confidence here. Especially when the fix is to delete the release....
Ive been following this issue for several months. Thanks to @bacongobbler and @jaredallard for working on it, I just wanted to emphasise how important these issues are. I know its not easy. Will continue to watch with anticipation...

How can we use this build so we can avoid #1193 ?
Any ideas or schedule that will make this eventually get accepted?


Mixing Scatter and Lines series breaks chart

Bug report
Codepen
Codepen
When mixes Scatter series with Line series it only works when there's only one Scatter serie. If you add another one the Line breaks showing its values and also the tooltip stop working for the extra Scatter plot series (in the case of my CodePen the one named Points 2). If you click quickly to hide/show the legends of that serie the points appear in chart for less than a second
Explanation

What is the behavior you expect? Show all the Scatter series correctly with the Line one
What is happening instead? Showing only one scatter and breaking the tooltip of the extra Scatter series
What error message are you getting? In my own console (but not in CodePen, I don't know why) it's throwing:

Uncaught TypeError: n[e] is undefined

On apexcharts.common.js:6:245715

It was not a bug, it was a misunderstanding on my part about the markers.size option: I was setting a fixed value of [6, 0] so it hid some scatter values and shows the dots of the Line chart.
I fixed it generating a marker size array dinamically from the number of series I had, setting the Line chart size to 0 always

In my case, by setting marker size to 0 was creating an odd behaviour of shared tooltip (when hovering on line tooltip was appearing in the corner). The solution/hack was to set shared: false intersect: true and in my "marker size adding function" setting line marker size to 0.00001.


[QA] activate sentry link at test_and_release

Activate automatic release creation for sentry

fixed wazt v2.4.1


tests: drivers: spi: Add nordic,clock-enable to SCK in spi12x

Fast SPI instances (spi12x) also requires clock pin property to be enabled for SCK pin.

Closing this one as we found a solution that does not require nordic,clock-enable in overlays (#76847).


HDDS-7490. fix metaTable error

What changes were proposed in this pull request?
fix metaTable error
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-7490
How was this patch tested?
current ut

Thanks @JacksonYao287 for the fix.

How was this patch tested?
current ut

Since the patch is fixing a bug and tests have been passing without it, I don't think current UT catches the bug, hence it does not validate the fix.
Also, https://github.com/JacksonYao287/ozone/commit/2663f9c31b5578354ccbb25974068e61df24f05c has no CI run, so I don't know which "current UT" was run.
I'm fine committing this without any tests, since it's a trivial fix.  Just please don't say it was tested with existing tests.

Thanks @JacksonYao287 for the fix.

How was this patch tested?
current ut

Since the patch is fixing a bug and tests have been passing without it, I don't think current UT catches the bug, hence it does not validate the fix.
Also, JacksonYao287@2663f9c has no CI run, so I don't know which "current UT" was run.
I'm fine committing this without any tests, since it's a trivial fix. Just please don't say it was tested with existing tests.

thanks @adoroszlai  for pointing out this , i have changed the description and will be careful later。

thanks @adoroszlai and @errose28 for the review!


New VQT

Add and test a VQT method for new style QHBMs.  Need to test cases where: energy and circuit have variables in common; variables in a given component are of different shapes, for example when energy is an MLP; and graph versus non-graph modes.

All that's left is addressing all the test cases above.


Notification issue on iOS13.3.1

We have recently received a significant amount of reports about notification issues. As we have not released the app for a while (:/), we need to check if some changes are requested due to last iOS version.
We also need to dig into Sygnal logs.

Reopened because there have been 2 cases (Steve and Dave) where notifications were not delivered while the setup client side looks good.

Updates for iOS 13:
https://developer.apple.com/videos/play/wwdc2019/707/

Need to reportIncomingCall to Callkit
payload: apps-expiration to 0, need to be updated in Signal.

Reopened because there have been 2 cases (Steve and Dave) where notifications were not delivered while the setup client side looks good.

These cases of failure is a server issue: https://github.com/matrix-org/synapse/issues/7075


Make azure driver create_node use kwargs

Make AzureNodeDriver create_node use only **kwargs. That should
allow the use of the debloy_node from the base class to work.
Motivation
Prior that change, one cannot use a deploy_node as deploy_node (defined on the libcloud.compute.base.NodeDriver) call the create_node of the driver with only keyword arguments.

Hi @lkoenig this goes against one of the projects code standards : https://libcloud.readthedocs.org/en/latest/development.html#don-t-abuse-kwargs
the drivers explicitly use named arguments to allow people to see from the docs what the arguments are, which are required, which are optional. etc.
create_node is intended to be used directly for all drivers.
please can you explain your use case with a bit more context so we might be able to help?

Thanks @tonybaloney for that feedback. I had read that documentation prior submitting the pull request. My issue is I didn't see that working with the implentation of libcloud.compute.base.deploy_node as that methode, line 902 of the file base.py call
        node = self.create_node(**kwargs)

Which, in the case of the azure driver, will throw an exception (as create_node in the azure driver expects some positional argument)
Have you a way you can recommand to fix that ?
I saw 2 ways:

Make the create_node of the azure driver use only kwargs (like the one in openstack and other) even if that breaks the policy yo mentionned
Change how the deploy_node takes and passes argument. To me that require a bigger change (maybe compltely worthed, but as I am new to the project, I prefer to ask).

Thanks again for your help,
Lionel
PS: I'll check also the UT failure ;)

@lkoenig everything in base.NodeDriver is meant to be overridden, if you don't override it, normally there is a NotImplementedError to catch you.
In the case of the Azure driver it looks like it doesn't match up the arguments correctly, so you want to override deploy_node with your own implementation.
Here's an example creating a node with Azure https://github.com/mistio/mist.io/blob/master/src/mist/io/methods.py#L2315
Is it deploy_node you want to use or create_node?

I would like to leverage the deploy_node method of the drive.
According to the documentation of deploy_node, one should not overwrite that method
As stated line 829 of libcloud/compute/base.py:
       Deploy node is typically not overridden in subclasses.  The
        existing implementation should be able to handle most such.

Thus, to make then the create_node of the azure driver be able to work with the deploy_node, I did the change proposed.
Another alternatives would have been to change the deploy_node to be something like:
def deploy_node(self, *args, **kwargs):
    # (...)
    self.create_nodes(*args, **kwargs)
    # (...)

Let me know if you prefer another way to solve that issue.

@Kami  I'll refer this one to you.

Sorry for the delay and thanks for the PR!
@tonybaloney is right - we should always explicitly declare arguments when possible. Sadly some of the old / legacy code doesn't do that, but we should avoid adding more debt in the future when possible.
There are two things we could do:

Leave create_node signature as it is and also add **kwargs to the end
Update / fix deploy_node so it doesn't pass deploy_node specific arguments to create_node. We could probably do something simple like this:

create_node_kwargs = copy.deepcopy(kwargs)
# remove all the deploy_node specific arguments from create_node_kwargs
node = create_node(**create_node_kwargs)

I think second option is the way to go. First one makes it work, but it doesn't really solve the "kwargs abuse" problem - method will just silently take in all the additional arguments and ignore them (that makes for a very bad, confusing and unfriendly API).

Thanks for the inputs. I totally agree that explicit argument is way better that kwargs. I am totally for not building up technical debt.
I'll try to implement the second solution as it seems elegant and doing the work. I'll get back as soon as I have something working.

Thinking, might be better to close that PR and start a new one (as the title could be misleading).

Great - thanks!
I'm fine with opening a new PR.


Error Importing C# dll in ironPython

Dear, I wrote the basic library showed below, then, create the dll and import in IronPython with clr, but I recieve the problem showed in the attached file. Why is this error.

using System;
namespace ClassLibrary1
{
public class Class1
{
public void Connect(int x, int y)
{
Console.WriteLine(x + y);
}
}
}

You need to instantiate your class (same as you would need to do in C#):
cpp.Class1().Connect(4,5)

Thanks a lot for your help...


[Cleanup] Rewrite interface{} to any

Objective
Replace all interface{} with any. See https://github.com/golang/go/issues/49884:

Origin Document
The suggestion was brought up here: https://github.com/pokt-network/pocket/pull/139#discussion_r940182627

Goals / Deliverables

[ ] Rewrite interface{} to any

Non-goals

Add / modify existing business logic

Testing Methodology`

All tests: make test_all
LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
Remove

Creator: @Olshansk
Co-Owners: @deblasis

This can be done with find ./ \( -type d -name .git -prune \) -o -type f -name '*.go' -print0 | xargs -0 sed -i 's/interface{}/any/g' will make PR now

That is some bash foo 🥋


Add Free C/C++ Resources

What does this PR do?
Add resource(s)
For resources
Description

Fixes #3556
Replaces a YouTube watch link with a playlist link.
Corrects naming of DayNhauHoc to Dạy Nhau Học

Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists  in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Followup

Check the output of Travis-CI for linter errors!

Ended up doing more than just fixing that pull request. ^-^'
Hope it's alright, I just took the other /watch URLs and made them playlists instead, updating the title/author if appropriate.


Severed bug: Consistently failed to pull image: 1/1 Pending:ImagePullBackOff on legion

We ran into issues where Azure Container Apps constantly failed to pull images in us west 2 region. it has been a couple days now. 1/1 Pending:ImagePullBackOff on legion
This issue happen sporadically in a Consumption Workload profiles. For ACA with at least a sidecar, this happens around 70% of the time. For ACA with a single container, this happens around 20% of the time.
Container registry setup: we are using admin login. weird thing is if we use a public registry like in docker hub, this still happens.
We tried to create a new vnet and container app environment but issue still persists.
Is this known and when can we expect a fix? Please let me know how I could get more info

Possible fix https://github.com/microsoft/azure-container-apps/issues/960#issuecomment-1907375438

@ericxl can you please send us an email to acasupport at microsoft dot com with your containerapp, env info so we could follow up with you?

We are seeing the same issue. Should I contact you at acasupport as well @chinadragon0515 ?

Hi - we have identified a race condition as the root cause of the issue and are in the process of producing and rolling out a fix.
Details:
The root cause of the issue with users experiencing ImagePullBackoff errors is specifically a race condition within the platform impacting specifically apps running in the Consumption workload profile. This condition occurs when the system inaccurately updates the in-memory token, intended for image pulls, to an empty value for some replicas during the replica creation.
Will update this issue once the rollout with the fix is completed.

The issue has been fixed and rolled out everywhere. close the issue.

@chinadragon0515 I am having this exact issue at the moment. No matter what I do, the container instance fails to pull the image. What do I need to do to resolve it?

I am currently facing the same issue

Has there been an update?

The issue has been fixed and rolled out everywhere. close the issue.

The issue hasn't been fixed yet

I'm facing a similar issue in central-us region, when I was using the consumption plan, the container app was no problem, but since I need more memory(>4G), I switched to the dedicated plan with Consumption workload profile, then it was always failed in pull image.

Same issue since I rotated the keys in a container registry

@aurelien-boubennec   Please open a new case if you are still having an issue, referring back to this one.


App crashed on iOS - Lost connection to device

Hi, I've been encountering this issue where the app crashes on iOS simulator and leaves Lost connection to device error message. I haven't tested it on a real iOS device yet.
Podfile
# Using a CDN with CocoaPods 1.7.2 or later can save a lot of time on pod installation, but it's experimental rather than the default.
# source 'https://cdn.cocoapods.org/'

# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def parse_KV_file(file, separator='=')
  file_abs_path = File.expand_path(file)
  if !File.exists? file_abs_path
    return [];
  end
  pods_ary = []
  skip_line_start_symbols = ["#", "/"]
  File.foreach(file_abs_path) { |line|
      next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
      plugin = line.split(pattern=separator)
      if plugin.length == 2
        podname = plugin[0].strip()
        path = plugin[1].strip()
        podpath = File.expand_path("#{path}", file_abs_path)
        pods_ary.push({:name => podname, :path => podpath});
      else
        puts "Invalid plugin specification: #{line}"
      end
  }
  return pods_ary
end

target 'Runner' do
  use_frameworks!

  # Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
  # referring to absolute paths on developers' machines.
  system('rm -rf .symlinks')
  system('mkdir -p .symlinks/plugins')

  # Flutter Pods
  generated_xcode_build_settings = parse_KV_file('./Flutter/Generated.xcconfig')
  if generated_xcode_build_settings.empty?
    puts "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first."
  end
  generated_xcode_build_settings.map { |p|
    if p[:name] == 'FLUTTER_FRAMEWORK_DIR'
      symlink = File.join('.symlinks', 'flutter')
      File.symlink(File.dirname(p[:path]), symlink)
      pod 'Flutter', :path => File.join(symlink, File.basename(p[:path]))
    end
  }

  # Plugin Pods
  plugin_pods = parse_KV_file('../.flutter-plugins')
  plugin_pods.map { |p|
    symlink = File.join('.symlinks', 'plugins', p[:name])
    File.symlink(p[:path], symlink)
    pod p[:name], :path => File.join(symlink, 'ios')
  }
end

# Prevent Cocoapods from embedding a second Flutter framework and causing an error with the new Xcode build system.
install! 'cocoapods', :disable_input_output_paths => true

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
      config.build_settings['SWIFT_VERSION'] = '4.0'
    end
  end
end

pubspec.yaml
environment:
  sdk: ">=2.3.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  carousel_slider: ^1.3.0
  cached_network_image: ^1.1.1
  flutter_money_formatter: ^0.8.3
  graphql_flutter: ^2.1.0
  rxdart: ^0.22.2
  get_it: ^3.0.1
  rx_widgets: ^2.2.0+1
  rx_command: ^4.3.2+1
  flushbar: ^1.9.0
  flutter_inappbrowser: ^1.2.1
  cupertino_icons: ^0.1.2

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true
  assets:
    - assets/images/

Flutter Doctor result:
[✓] Flutter (Channel dev, v1.10.14, on Mac OS X 10.13.6 17G65, locale en-PH)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.1)
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.39.1)
[✓] Connected device (1 available)
This project was not created via  flutter create -i swift, hope someone could help me on this. This is the only webview plugin that works really great on our app on Android.

I'm encountering the same issue. When compiled using xcode i get these errors:
Error on iPhone 6 (real device) - ios 12.4.2
Error on iPhone 8 (simulator) - ios 13.1
Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/user/development/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_inappbrowser-1.2.1/ios/Classes/FlutterWebViewFactory.swift, line 25
2019-10-22 17:44:48.289006+0700 Runner[360:13751] Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/user/development/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_inappbrowser-1.2.1/ios/Classes/FlutterWebViewFactory.swift, line 25

i found the main problem in my project.
In my case,
flutter_inappbrowser (this plugin) is in conflict with flutter_downloader when calling await FlutterDownloader.initialize(); before runApp(MyApp()); on main.dart
this might be unique to my project though, and I haven't found the solution.

In my case,
flutter_inappbrowser (this plugin) is in conflict with flutter_downloader when calling await FlutterDownloader.initialize(); before runApp(MyApp()); on main.dart

@TimothyY how did you know that there is a conflict?

When I take out the inappbrowser plugin the flutter_downloader runs normal.
Same is true when I take out the flutter_downloader and let the other plugin runs.
I also open an issue on the flutter_downloader github, because their older version works. and this bug appears when I'm using their 1.3.x

I'm not using flutter_downloader.
I'm new to flutter that's why I'm not familiar with xcode compiling. Would you please guide me or send me some links on how to do it?

Open your project with android studio
On your project structure, search for ios folder
Inside the ios folder, search for runner folder
Search for appdelegate.swift /appdelegate.c /appdelegate.h and open it.
When the file is opened in android studio, look at the upper right section of your android studio, there should be something like "open in xcode". Click it.
Your xcode will open the ios module of your project and you can run it from your xcode.
Sometimes your xcode will ask for sign certificate, make sure you have it configured on xcode > your project structure > runner > sign and capabilities

Thanks @TimothyY, I will try this later and will post the progress here.

Try the latest version of the plugin. However, this plugin changed its name to flutter_inappwebview. The current latest version now is 2.1.0+1. So, you can change your dependency influtter_inappwebview: ^2.1.0+1.
Also, change config.build_settings['SWIFT_VERSION'] = '4.0' to config.build_settings['SWIFT_VERSION'] = '5.0'

@pichillilorenzo Should i create new issue, or, just post post messages here? I have same issue, on last ( ^2.1.0+1 ) version.

@koteezy could you explain your use case for which this happens?? Post all useful information such as Xcode version and iOS version. Also, post the Xcode error logs you get. Thanks!

@koteezy could you explain your use case for which this happens?? Post all useful information such as Xcode version and iOS version. Also, post the Xcode error logs you get. Thanks!

Alright, i found scenario when i got this error.
If i call flutter_inappwebview.callHandler to fast, like that:
flutter_inappwebview.callHandler('tracks', '[]');

I got crash, with these errors

Log
2019-12-17 22:45:12.185530+0300 Runner[31568:3738796] flutter: ok. go!
2019-12-17 22:45:12.409090+0300 Runner[31568:3738796] flutter:

Browser Created!
2019-12-17 22:45:15.438394+0300 Runner[31568:3738796] flutter:

Stopped!!
2019-12-17 22:45:15.506786+0300 Runner[31568:3738796] flutter: We got args.
Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/uebanchik/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-2.1.0+1/ios/Classes/InAppWebView.swift, line 1242
2019-12-17 22:45:15.508742+0300 Runner[31568:3738044] Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Users/uebanchik/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-2.1.0+1/ios/Classes/InAppWebView.swift, line 1242
2019-12-17 22:46:06.339925+0300 Runner[31568:3738796] flutter: [{"tracks": []}]
(lldb)

But, if i will use something like this:
setTimeout(() => {
        flutter_inappwebview.callHandler('tracks', '[]');
 }, 1000);

I will got result, and everything will works fine.
Yea, i know what You say what we need use something like this, and i know that is right:
window.addEventListener("flutterInAppWebViewPlatformReady", function (event) {
   flutter_inappwebview.callHandler('tracks',  '[]');
});

But, how i say here, that listener just not called. ( i use injectJavascriptFileFromAsset )

Flutter doctor
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.1 19B88, locale ru-RU)
    • Flutter version 1.12.13+hotfix.5 at /Users/uebanchik/development/flutter
    • Framework revision 27321ebbad (7 days ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/uebanchik/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 42.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.41.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.7.1

[✓] Connected device (1 available)
    • iPhone 11 Pro Max • 92CEB5FD-320B-4EF6-B8C3-84C45803D21A • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-2 (simulator)

• No issues found!

Plugin version: ^2.1.0+1

@koteezy if you use injectJavascriptFileFromAsset on onLoadStop then it should be ok without using window.addEventListener("flutterInAppWebViewPlatformReady") because that event is already called before you load the javascript file. So, you can use directly flutter_inappwebview.callHandler('tracks',  '[]'); in your javascript code.
About the crash, it has been fixed in the next major release.
I tested this code and it works as expected without errors:
import 'dart:async';

import 'package:flutter/material.dart';

import 'package:flutter_inappwebview/flutter_inappwebview.dart';

Future main() async {
  runApp(new MyApp());
}

class MyApp extends StatefulWidget {
  @override
  _MyAppState createState() => new _MyAppState();
}

class _MyAppState extends State<MyApp> {

  @override
  void initState() {
    super.initState();
  }

  @override
  void dispose() {
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        home: InAppWebViewPage()
    );
  }
}

class InAppWebViewPage extends StatefulWidget {
  @override
  _InAppWebViewPageState createState() => new _InAppWebViewPageState();
}

class _InAppWebViewPageState extends State<InAppWebViewPage> {
  InAppWebViewController webView;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
            title: Text("InAppWebView")
        ),
        body: Container(
            child: Column(children: <Widget>[
              Expanded(
                child: Container(
                  child: InAppWebView(
                    initialFile: "assets/index.html",
                    initialHeaders: {},
                    initialOptions: InAppWebViewWidgetOptions(
                      inAppWebViewOptions: InAppWebViewOptions(
                        debuggingEnabled: true,
                      ),
                    ),
                    onWebViewCreated: (InAppWebViewController controller) {
                      webView = controller;

                      controller.addJavaScriptHandler(handlerName: "tracks", callback: (args) {
                        print(args);
                      });
                    },
                    onLoadStart: (InAppWebViewController controller, String url) {

                    },
                    onLoadStop: (InAppWebViewController controller, String url) {
                      controller.injectJavascriptFileFromAsset(assetFilePath: "assets/js/script.js");
                    },
                  ),
                ),
              ),
            ]))
    );
  }
}

where assets/index.html contains this simple HTML code:
<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0">
    <meta http-equiv="X-UA-Compatible" content="ie=edge">
    <title>Flutter InAppWebView</title>

Hi

and assets/js/script.js contains only:
var tracks = [1,2,3,4];
flutter_inappwebview.callHandler('tracks', tracks);

Xcode logs:
flutter: [[1, 2, 3, 4]]

@pichillilorenzo I will wait, thanks!

@koteezy my code example is working for you?

@koteezy my code example is working for you?

No.. On android, everything okay, except, specific models like that one, on ios have same issue as i show above, if it help, here my browser:
class MyInAppBrowser extends InAppBrowser {
  Service service;
  Function callback;

  MyInAppBrowser(this.service, this.callback) {
    final options =
        InAppBrowserClassOptions(
          inAppBrowserOptions: InAppBrowserOptions(),
          inAppWebViewWidgetOptions: InAppWebViewWidgetOptions(
            inAppWebViewOptions: InAppWebViewOptions(
              debuggingEnabled: true
            )
          )
      );

    this.open(
      url: this.service.url,
      options: options,
    );
  }

  @override
  Future onBrowserCreated() {
    print("\n\nBrowser Created!\n\n");

    this.webViewController.addJavaScriptHandler(
        handlerName: "tracks",
        callback: (args) async {
          print("We got args.");
          print(args);
          this.callback(BrowserParsingCallback(service, json.decode(args[0])));

          this.close();
        });
  }

  @override
  Future onLoadStart(String url) async {
    // print("\n\nStarted $url\n\n");
  }

  @override
  Future onLoadStop(String url) async {
    print("\n\nStopped!! $url\n\n");

    this
        .webViewController
        .injectJavascriptFileFromAsset(assetFilePath: service.parserPath());
  }

  @override
  void onLoadError(String url, int code, String message) {
    print("Can't load $url.. Error: $message");
  }

  @override
  void onProgressChanged(int progress) {
    //
  }

  @override
  void onExit() {
   //
  }

  @override
  void onLoadResource(LoadedResource response) {
   //
  }

  @override
  void onConsoleMessage(ConsoleMessage consoleMessage) {
    //
  }
}

It works fine only if i use callHandler with delay, like:
setTimeout(() => {
        flutter_inappwebview.callHandler('tracks', '[]');
 }, 1000);

@pichillilorenzo still shows lost connection to device like @koteezy said or else its added a setttimeout(). I got this errors when i run via xcode
2019-12-19 05:35:04.895948+0100 Runner[14278:77343] flutter: Observatory listening on http://<IP_ADDRESS>:53075/gpsJXD8j4xw=/ Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Library/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-2.1.0+1/ios/Classes/InAppWebView.swift, line 1242 2019-12-19 05:35:07.142995+0100 Runner[14278:76915] Fatal error: Unexpectedly found nil while unwrapping an Optional value: file /Library/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-2.1.0+1/ios/Classes/InAppWebView.swift, line 1242 (lldb)


CoinGecko API for crypto market data | free & reliable

https://www.coingecko.com/api/docs/v3

I don't think this is relevant to this repo as this is for CoinMarketCap API. You could make another API wrapper for CoinGecko API if you want.


PYIC-1523 - use onSubmit to disable submit input and to prevent subse…

What changed
Use onSubmit to disable submit input and to prevent subsequent form submissions
Why did it change
Previously used the click event of the button to disable the button to prevent multiple clicks but this did not account for edge cases where user is not using a mouse.

PYIC-1523

as you're using govuk-frontend, you can utilise the built-in data-prevent-double-click button attribute as described on https://design-system.service.gov.uk/components/button/#:~:text=Stop users from accidentally sending information more than once

The data-prevent-double-click only debounces for one second in our use case we need to disable the button/form completely.


identify should not allow already identified users

Description
Relates to https://github.com/PostHog/posthog-js/pull/524
const isKnownAnonymous = this.persistence.get_user_state() === 'anonymous' is the check where we know if calling identify again is allowed or not.
If the user is already identified, calling identify again isn't allowed, if that's intentional, you should call alias instead.
If you want to identify another user again, you have to call reset first.
https://posthog.com/docs/product-analytics/identify#3-reset-after-logout
There are more restrictions described here.
By not doing this, we might be merging users wrongly and we'll likely get a support request to split persons.
This has to be done on the other SDKs as well such as:

[ ] iOS
[ ] RN (js-lite)
[ ] ...

Description
Relates to PostHog/posthog-js#524
const isKnownAnonymous = this.persistence.get_user_state() === 'anonymous' is the check where we know if calling identify again is allowed or not. If the user is already identified, calling identify again isn't allowed, if that's intentional, you should call alias instead.
If you want to identify another user again, you have to call reset first. https://posthog.com/docs/product-analytics/identify#3-reset-after-logout
There are more restrictions described here.
By not doing this, we might be merging users wrongly and we'll likely get a support request to split persons.
This has to be done on the other SDKs as well such as:

[ ]  iOS
[ ]  RN (js-lite)
[ ]  ...


Conan Exiles Stops Reporting to Server Browser

Operating System
Windows/Linux
AMP Version and Build Date
2.6
AMP Release Stream
Mainline
I confirm that

[X] I have searched for an existing bug report for this issue.
[X] I am using the latest available version of AMP.
[X] my operating system is up-to-date.

Intended Action
N/A
Expected Behaviour
N/A
Actual Behaviour
N/A
Reproduction
https://discord.com/channels/266012086423912458/1283105587709870181

This has been resolved through a change to the template.


Document req.login for refreshing req.user

I hit a use case where I needed to refresh req.user with new information without logging in and out. Somebody on Stack Overflow pointed me to calling req.login() with the updated values. However nowhere is this in the documentation--would love to see it there!

me too! this use case might warrant a new function or feck me pls!

:+1:

I am also trying to update req.user with new information and i am updating it using following code
 req.login(userObj, function(err) {
    if (err) return next(err)

    console.log("After relogin: ");
    console.info(req.user);
  });

where userObj contains new updated user info. in the console i can see req.user has new data, but when i access it again on the route as req.user it shows old data, i am confused, what is wrong here..? can some expert throw some light..?
Thanks!
Regards
Naren

@narendra-agashe Have you figure out that? I have the same problem  thank you cc @Zugwalt

These are my biggest difficulties in understanding passport:

The login flow of passport
How to access passport data on client-side (view engine)

The Login Flow of Passport
Login from the Passport Strategy

You run your passport authentication in your passport strategy code and if it passes, user is authenticated. Right after the code where user passes the authentication tests, you got to keep track of this user who is logged into your system. Why? Because session and cookies don't keep track, they only help to persist the user. In fact, you need to keep track of all other users who are currently logged into your system.
You can keep track of it on a database or in Node memory. Let's say we keep track of logged in users in Node memory, that means it will be in an array such as: var users = [].  So, once user is authenticated, your passport strategy should be adding that user into the users array such as: users.push(user)
Only now will passport finally run serializeUser, which adds user into session req.user and saves the user's ID into the client-side cookie.

On every request authenticated user makes to the system

Passport will run deserializeUser, which gets the ID from the cookie, and looks up and retrieves this user object in the 'users' array based on the ID.
Once the user object is retrieved, it gets copied into req.user. This is done each time on every request the user makes to the system. Why? Because we don't have a way to find out when the user info has changed so we just got to do it every time to make sure our session contains the most updated user info. In other words, deserializeUser will be run for every request, regardless of whether the user info has changed or not.

When User Info has Changed

I don't think passport's req.login will help you update the user info because it doesn't update Node memory, it only updates to session. But session gets its values from Node memory. Please note Node memory is not the same as session memory
So first thing you must do is, you got to update the user info in the users array, which is the Node memory. So, you search for that User object in the users array and then you update the User  object in the user array with the new values.
Only now is deserializeUser() called, which will get the ID from the cookie, look up and retrieve the User object in the users array. Then copy this User object into session req.user.

Note: When user info changes from the client side and you want it to be updated on the server side,  make sure you DON'T use a GET request method. Use something like a POST request method because you're changing stuff.
How to Access Passport Data on Client Side (View Engine)

passport stores user data in the request user object. you can access it with req.user.
in fact, you can check if a user is logged in with this: if (typeof req.user === 'undefined'), because passport creates this request user object req.user when user logs in and deletes req.user when user logs out. yes, it's the same as req.isAuthenticated.
the view engine can only read from the response object. you can access passport data with res.locals.user. please note, the view engine can't access or read from the request object.
to access your passport data in the view engine (e.g. express-handlebars), you need to copy your passport data over to the view engine: res.locals.user = req.user, which copies your request user object over to the response user object. i like to call this step 'session management'
let's say for 'Bill', passport will store it at req.user.name, with value of 'Bill'. If you've done your 'session management' correctly, you can access the username in the view engine, which is in the html code, with {{user.name}}, which comes from res.locals.user.name
i normally do this 'session management' stuff in a middleware and i always put this as the last middleware because order is important. you don't want changes to the passport data to not make it to the view engine because you forgot to copy it over from the request object to the response object.

Example of 'session management' middleware:
module.exports = function() {

     return function(req, res, next) {
        res.locals.session = req.session || {}; // session data
        res.locals.user = req.user || {}; // passport data
        next();
    }
};

@zhiyelee, please look at my above post, my part on "When User Info has Changed" should give you some hints. I also included some background information so you get the complete picture.
If you want to update user info, you got to update the value in your database first or your Node memory first, depending on what you're using to keep track of logged in users. Do that first, and deserializeUser() will automatically update the new value in req.user. Because deserializeUser()  actually searches for the user in your database or Node memory and copies that user info into session.
So you don't have to change any code in deserializeUser(), you just got to replace your req.login() code with something that updates the user in the database or memory. I don't think you need to call req.login() if you're just updating the user info. Plus "login" is not what you're doing so your code would be kind of misleading to use the word "login".
Here's my deserializeUser code inside the Passport Strategy:
passport.deserializeUser(function(id, done) {
    User.findByIdInMemory(id, function(err, user) {
        done(err, user);
    });
});

Here's my code where I update the user info in Node memory, I call this in my routes:
User.updateUserInMemory = function(user) {

    // Find the user in the 'users' array by token ID
    for (var i=0; i<users.length; i++) {
        if (users[i].IDToken == user.IDToken) {

            // update this user's fields in the 'users' array, except for the token ID
            users[i].username = user.username;
            users[i].email = user.email;
        }
    };
};

Awesome Post, thank you @samhuntsocial !!!  That helps a lot.

@samhuntsocial Great description of Passport's flow. It really needs spelling out, since it's pretty complicated. However, it looks like you're saying you should keep the whole of a user's data in the session cookie, and then reload it from the database on every request (done in deserializeUser()). Surely that's a waste of database resources. I would either...

Keep the user in the session cookie, loading the user from the database only once when the user logs in.
Keep just basic, frequently used user-data in the session cookie. Only load a user's complete userdata from the database when you need more information about them (e.g. a user-edit page). If a user's basic data is normally enough for you (e.g. id, name, language, profilePicId), I would go with this option.

In both cases, when a user changes their data, you'd save the user to the database then update the user in the session by calling req.login().
That's how I do it and it works for me. If you've got it working with another method then it's probably best to ignore me and optimise only when you really need to! +Sorry if this makes people more confused!

@chicilatte Thanks. I agree with you. Store only the user's ID in the cookie and store only pertinent info of the user in the session req.user.
In my production system, my logic actually more closely follows what you say. I load the user from the database only once when the user logs in (due to the performance issue). The rest of the time, it's persisted in-memory in Node, in an array. I do have my doubts of the robustness of this in-memory approach (i keep thinking there will be bugs later), but so far the web application is holding up.
The way I explain it above is, that's the way it is in Passport example codes, such as this one: https://github.com/fabiobozzo/expressjs-multiauth

Yeh, the Passport example does seem to be the simplest to get your head around. As for using an array to store your user sessions, there are three reasons why that could be slightly crappy:

The main reason: when you deploy a new version of your app all your users are logged out. Totally annoying. Also happens when your app throws an error or you reset the server's operating system.
The number of logged-in users is limited by your server's memory.
It stops you from using more than one application server if you want to scale to a larger audience.  But node is so quick you'll be doing fabulously well if you have to start using more than one app server :)

In my experience, it's best to use the "connect-redis" module to store your user sessions. Pretty easy to set up, and then you can have as many app servers as you like, all grabbing their user sessions from an independent, lighting quick Redis server. If you can't be arsed with that, storing your sessions on disk seems like the best option (I think this is built into Express, right?).

@chichilatte many thanks, very helpful. i think this "connect-redis" module is what i've been looking for to replace my "array". very good reasons, all three. i'm fully convinced.  if it's a production environment, we must use caching like "connect-redis". if you're just testing out code in your development environment, it's OK to use arrays...but just don't forget to switch over to something like "connect-redis" as soon as you can.

@samhuntsocial @chichilatte Thanks for the clarification but as you said, Passport fires the deserializeUser function for every request which keeps the req.user up to date. If we are to use chichilatte method of only loading the user one time at the login stage then calling req.login just after we make updates in our database, how do we stop the deserializeUser function firing for every request?

@samhuntsocial The approach you presented would only work when immutable information about the user is stored in the session right such as user id? Because in the case where a modifiable field such as username is stored in the session, when the user updates said modifiable field the session data becomes outdated which results in the user being logged out. Just making sure I understand why your approach works, thanks.

I think that since the commit 42630cbd1ffd44d146ff96f0a4be6f3c12f81d75 introduced in version 0.6.0, because of the line https://github.com/jaredhanson/passport/blob/cfdbd4a762b51e339ebfea931d65bccbbde53282/lib/sessionmanager.js#L28 , this strategy (doing req.login) does not work (without some changes) anymore since it regenerates a new session ID.

Well spotted @ctaschereau. That's a real breaking change for people using this technique. Maybe the maintainers have no idea people use the module in this way?

Anybody figured out how to update the existing req.user object?


AS: add parsed claims for TDX/SGX and documents

Partially resolve #246 and #228
This PR will change the token format in https://github.com/confidential-containers/kbs/pull/240

LGTM


pull request for e2e test at 11/09/2016 11:26:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix GitHub workflow warning

https://github.com/philj56/gbcc-android/actions/runs/3337454331
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout, actions/checkout

:+1: Cheers, I've updated the workflow.


Make master green again

Fix tests, reckoning that setuptools.parse does not
preserve ordering of specs and extras anymore.
fixes #26

Changes Unknown when pulling 5c8f85d50d986b36392ec14a17bee53c8f12ab5f on sbidoul:greenify-sbi into ** on davidfischer:master**.

Oops, just noticed #28 fixes this too.

I suppose this isn't necessary now that #28 is merged. Thanks though and thanks for prodding me!


[pidnet_netspresso.py] Load PIDNet and convert torch.fx

Convert PIDNet to torch.fx and compress it through PyNetsPresso into a single .py file.

Load PIDNet
Convert the loaded PIDNet to torch.fx
Compress PIDNet converted to torch.fx via PyNetsPresso
Put the compressed PIDNet into the original PIDNet structure

-> Through this method, the process of convert -> compress -> restore, which was previously divided, can be performed at once, making it convenient for users.

In the case of PIDNet, a model structure is created according to model types s, m, l, and then checkpoints are called. Since the structure changes after netspresso compression, let's declare another model type so that we can load the model right away.

In the case of PIDNet, the structure used for training and the structure used for inference are different. Basically, the purpose is to increase inference speed, so let's blow the model based on inference when loading the model.

It is okay to compress in the form of inference, but if the model itself is extracted in the form of inference, the train cannot be performed. Set the model structure as train, proceed with compression as inference, and finally restore the model in train form.


Dockerise ManagementPortal and integrate with docker-compose at RADAR-Docker

To integrate with usual packaging of the platform, MP should be dockorized with available, configuration options and integrated with docker-compose with relevant security measures taken into account.

Management portal can work with dockerized postgres sql in a docker-compose. Still need to be integrated to the radar-dockerś docker-compose stack

Will be solved by PR


Xbox Joystic does not transmit input when connected with bluetooth

This is not a harware problem as the input is actual recorded by autopylot. this is a probably an issue with a state that disable the recording.
In joystic.py line 131 the fvalue is updated correctly but the car doesn't turn for a weird reason

is this still an issue ? I guess you did select the wrong actuator


Menu bar is not show correctly

New Issue Checklist

I have read the guidelines for contributing and I understand:

[x] My issue is happening in the latest version of SideMenu.
[x] My issue was not solved in the README.
[x] My issue can not be answered on stackoverflow.com.
[x] My issue is not a request for new functionality that I am unwilling to build and contribute with a pull request.
[x] My issue is reproducible in the demo project.

Issue Description

I having a problem with my project. I followed code-less strotyboard implementation. My menubar isn't show correctly as you can see my pictures below.  I also read a example of yours but I could not find solution. Thank you. Sorry for your inconvenience.

You’re adding your navigation bar manually which is atypical. This is a question for stackoverflow.com.

May I ask you how to solve the problem. I have posted this problem on the stackoverflow and I am waiting for the answer but If you can help. It will much more easier. Thank you


CRD to package a software

Describe the problem/challenge you have
Package authors do not have a consistent way to package their software which then can be distributed for consumption.
Describe the solution you'd like
Package authors should be able to create a new Package CR to package their software that can then be distributed for consumption by others. They should be able to define the following in this CR:

Reference to a Package Contents Bundle (containing all the files, OCI images)
Name and version of the package
Authors and description
Describe how to install the package

The Package CR can be deployed on a cluster directly or bundled in a package repository.
Anything else you would like to add:

In progress on the dev-packaging branch.

This is available in release v0.17.0-alpha.1+.
Installation instructions for the latest alpha versions containing this can be found here
Release yaml can be found here
For tracking when this is available in a major release, please follow the epic issue


Issue #93 allow versioning of containers

This builds on @bchecketts ' code from https://github.com/garethr/garethr-docker/pull/209, changing the init script and adding a param, clean_restart.
This allows one to change the image tag in docker::run from say redis:2.6 to redis:2.8.14 and have the old container destroyed and a new one running the new image put in its place.

Thanks both @br0ch0n and @bchecketts for this change. I'm going to merge this now, but it's also worth following https://github.com/garethr/garethr-docker/pull/216 too which might change the need for this in the future.


Migrating to Transformer v2 fails (logs show "Throttling: Rate exceeded")

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.6.5
What operating system are you using?
Windows
Amplify Categories
api
Amplify Commands
push
Describe the bug
I've spend a few hours today trying to mirgrate to v2 of the transformer for GraphQL.
My schema appears to be updated and valid. I've followed the migration doc so have done everything I should. The only feedback or warnings I got when I did the migration where:

I'm not sure if these are statements, warnings, errors? Seems I can ignore them from what little I've found online. However when I try to push it up via amplify push it fails and causes a roll back.
In the console I only have this to go on:

And in the logs (which thanks to previous debugging with the Amplify Team I know to live at c:/users//.amplify/logs) I searched for "error" and I'm seeing lots and lots of them for "Throttling: Rate exceeded":

That error though might be a total red herring...but if so I'd query why its included in the logs.
This push took a good 20 minutes to run and roll back. I ate many chocolates in this time.
Expected behavior
The migration does the migration. The push does the push. If it errors it lets me know why and some pointers of what went wrong. Seems this is two issues, whatever is causing the error and a lack of built in DX help to allow me to fix it myself (if possible).
It would be nice to not feel like I'm in a constant punching match with Amplify. If it fails give me an error I can work with, give me some pointers of where to look, something I can try. I'm once again completely stuck and in the dark, what you know.
Luckily this one for once isn't a total blocker, I can just revert via git (or dare I try the built in revert to the migration?). But I know in the new year you want to drop V1 support so now seemed like a good time to do it 🤷♂
Reproduction steps
I've send over my whole project just before Christmas with the issues I was having then. I'm happy to resend it if required. Its a year old so ancient in Amplify time so its hard to unpick what might be causing it to error this time as usual.
GraphQL schema(s)

# Put schemas below this line

Log output

2021-12-29T18:01:15.759Z|error : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]st-[***]19:stack/[***]ify-[***]manager-[***]ldev-[***]134-[***]emanager-[***]52YPH-[***]ethod-[***]QDK2ZC/[***]8f40-[***]cb-[***]eb-[***]ae-[***]df8eb"}])
Throttling: Rate exceeded
2021-12-29T18:01:15.766Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]st-[***]19:stack/[***]ify-[***]manager-[***]ldev-[***]134-[***]emanager-[***]F6-[***]cription-[***]EHV5E/[***]7860-[***]cb-[***]eb-[***]7b-[***]4271f"}])
2021-12-29T18:01:15.819Z|error : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]st-[***]19:stack/[***]ify-[***]manager-[***]ldev-[***]134-[***]emanager-[***]T52YP-[***]Method-[***]XN8E38/[***]9cd0-[***]cb-[***]eb-[***]0f-[***]eb9d5"}])
Throttling: Rate exceeded
2021-12-29T18:01:15.873Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]st-[***]19:stack/[***]ify-[***]manager-[***]ldev-[***]134-[***]emanager-[***]P-[***]tiveStack-[***]49WDX/[***]0080-[***]79-[***]ec-[***]8d-[***]62abd"}])
2021-12-29T18:01:15.972Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]manager-[***]ldev-[***]134"}])
2021-12-29T18:01:16.075Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]st-[***]19:stack/[***]ify-[***]manager-[***]ldev-[***]134-[***]emanager-[***]52YPHS-[***]ob-[***]KKMY1/[***]ef90-[***]cb-[***]eb-[***]c4-[***]b30f3"}])
2021-12-29T18:01:16.113Z|error : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]rmation:eu-[***]st-[***]19:stack/[***]ify-[***]manager-[***]ldev-[***]134-[***]emanager-[***]52YPHS-[***]omer-[***]FSG5EO/[***]f890-[***]cb-[***]eb-[***]5f-[***]9a86f"}])
T

Additional information
No response

Has this one slipped through the net?
I'm wanting to use the new @searchable total field but being unable to migrate means I'm sort of stuck.

Hey @PeteDuncanson  :wave: apologies for the delay! I'm taking a look at this now

Hey @PeteDuncanson may you send us a copy of your v1 schema to<EMAIL_ADDRESS>And do you see a more descriptive error as to why those resolvers failed to create in the CloudFormation console?

@josefaidt Sent one last night you :)

Hey @josefaidt
I really appreciate you looking into  this and once again I'm sorry its not easier to reproduce, a classic of my whole setup it seems!
From memory I tried running it a few times (multiple pushes) and got roughly the same sort of errors but I can't say if it was on the same model, I suspect it was but can't say for sure. I can give it another push and happy to recreate on my own machine with you zooming in (its not efficient I know). Its all in another branch at the minute and I'm in the middle of go live prep and final testing so time might be short.
Cheers
Pete

Hey @PeteDuncanson that would be great! I can send over a calendar item, do you have a preferred time for meeting?

I'm around now or tomorrow night or friday night. I'm on GMT but I know you guys are around until 9pm my time.

That sounds great @PeteDuncanson I just sent over a calendar item for tomorrow 🙂

Closing issue after a successful call

Trying to warm this one up as I'm going to have some time to try to run this again soon and finally get us up on V2. Might be a case I should just rerun it and see if it works I guess. You might have fixed whatever the issue was since I opened this!


Introduce Succeeded condition

When the remediator sets the Processing condition to False because it is done, there might be a more or less longer delay until the node actually gets healthy (slow reboots or node reprovisionings e.g.). If that delay exceeds the internal 30s timeout, NHC will set the timeout annotation and trigger the next remediator even though the node potentially was remediated successfully, but just didn't get ready fast enough.
Solution is to not use the Processing condition (which still is informative for users), but a Succeeded condtion, wich remediators can set to false in case of issues, which will make NHC set the timeout annotations and trigger the next remdiator immediately.
ECOPROJECT-1246

/lgtm

/retest

/lgtm
Just leaving space to get other feedback, feel free to unhold
/hold

/hold cancel


Output CSV file

It would be nice to also have an option to output the data into a csv file directly.
Excel is nice for double-click and viewing, but not to incorporate it into a workflow.

you can load the xlsx file using pandas and then make your magic.

Is csv export required for command-line usage?
After code refactoring I plan to add numpy array getter, so one could use data without saving to file. Maybe this would be enough.


Fix proposal for pos_file issue in /var/log

This should allow for configurable pos_file directory based on FLUENT_POS_DIR ENV variable

Does this work on your environment?
This patch changes pos_file directory at image building time, not fluentd runtime.
If you want to change configuration parameter at runtime, need to use this feature: https://docs.fluentd.org/v1.0/articles/config-file#embedded-ruby-code

BTW, please add your sign to commits: https://github.com/apps/dco

I'm using configmap to change fluentd's config file so I've changed the pos location and it seems to run but the thing is a regular user (fluent with UID 1000) cannot access files from /var/log/containers which ends up with error, so I guess it's not a proper direction as it still needs root-level access to those files :(
Second thing being the config file itself where we'd have to validate the ENV variable within each pos_file on runtime if I understand correctly?
so it would be like this:
pos_file "#{ENV['FLUENT_POS_DIR'] != nil ? ENV['FLUENT_POS_DIR'] : '/var/log'}/fluentd-kube-controller-manager.log.pos"

It works when added to the configmap, but the access issue remains

Second thing being the config file itself where we'd have to validate the ENV variable within each pos_file on runtime if I understand correctly?

Yes. Your patch approach doesn't work because erb is evaluated at docker image building phase.
So fluentd uses fixed value, in this case /var/log, in user environment.
pos_file "#{ENV['FLUENT_POS_DIR'] != nil ? ENV['FLUENT_POS_DIR'] : '/var/log'}/fluentd-kube-controller-manager.log.pos"
This approach works because this line is evaluated at fluentd startup phase.


React to application part changes

Will make changes in a follow up.

@pranavkm Can you confirm that you are changing this as we discussed?


Sampler cleanup

Clean up some issues in the sampler and other classes

Codecov Report

Merging #547 (0afff1f) into dev (6a834f3) will increase coverage by 0.08%.
The diff coverage is 100.00%.

:exclamation: Current head 0afff1f differs from pull request most recent head dc30e11. Consider uploading reports for the commit dc30e11 to get more accurate results

@@            Coverage Diff             @@
##              dev     #547      +/-   ##
==========================================
+ Coverage   71.87%   71.96%   +0.08%
==========================================
  Files         121      121
  Lines       15647    15607      -40
==========================================
- Hits        11246    11231      -15
+ Misses       4401     4376      -25