Test target x encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
We have 3 separate build machines all which run the same code, I am getting this error on the newest mac we just got which has the same specs as another which the builds pass on. All running exact same fastfile etc. I assume something must be up with my build on the computer. All are running xcode 8.1.
Complete output when running fastlane, including the stack trace and command used
Executed 619 tests, with 0 failures (0 unexpected) in 22.376 (22.746) seconds
2016-11-10 09:54:04.256 xcodebuild[40376:613510] Error Domain=IDETestOperationsObserverErrorDomain Code=5 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}

Testing failed:
	Test target x encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
| Gem                 | Version | Update-Status |
| ------------------- | ------- | ------------- |
| credentials_manager | 0.16.2  | ✅ Up-To-Date  |
| fastlane_core       | 0.55.0  | ✅ Up-To-Date  |
| spaceship           | 0.37.0  | ✅ Up-To-Date  |
| deliver             | 1.15.0  | ✅ Up-To-Date  |
| snapshot            | 1.16.3  | ✅ Up-To-Date  |
| frameit             | 3.0.0   | ✅ Up-To-Date  |
| pem                 | 1.4.0   | ✅ Up-To-Date  |
| cert                | 1.4.4   | ✅ Up-To-Date  |
| sigh                | 1.11.2  | ✅ Up-To-Date  |
| produce             | 1.3.0   | ✅ Up-To-Date  |
| gym                 | 1.12.0  | ✅ Up-To-Date  |
| pilot               | 1.12.0  | ✅ Up-To-Date  |
| scan                | 0.14.1  | ✅ Up-To-Date  |
| supply              | 0.7.1   | ✅ Up-To-Date  |
| match               | 0.11.0  | ✅ Up-To-Date  |
| fastlane            | 1.108.0 | ✅ Up-To-Date  |
| screengrab          | 0.5.5   | ✅ Up-To-Date  |

### Loaded fastlane plugins:

**No plugins Loaded**

Loaded gems

| Gem                       | Version      |
| ------------------------- | ------------ |
| executable-hooks          | 1.3.2        |
| bundler-unload            | 1.0.2        |
| rubygems-bundler          | 1.4.4        |
| bundler                   | 1.13.3       |
| highline                  | 1.7.8        |
| commander                 | 4.4.0        |
| terminal-table            | 1.4.5        |
| multipart-post            | 2.0.0        |
| faraday                   | 0.9.2        |
| faraday_middleware        | 0.10.0       |
| dotenv                    | 2.1.1        |
| net-ssh                   | 3.2.0        |
| net-sftp                  | 2.1.2        |
| plist                     | 3.1.0        |
| rubyzip                   | 1.1.7        |
| security                  | 0.1.3        |
| krausefx-shenzhen         | 0.14.11      |
| slack-notifier            | 1.5.1        |
| rouge                     | 1.11.1       |
| xcpretty                  | 0.2.4        |
| addressable               | 2.4.0        |
| claide                    | 1.0.1        |
| xcode-install             | 2.0.7        |
| word_wrap                 | 1.0.0        |
| multi_json                | 1.12.1       |
| colored                   | 1.2          |
| babosa                    | 1.0.2        |
| gh_inspector              | 1.0.2        |
| credentials_manager       | 0.16.2       |
| fastlane_core             | 0.55.0       |
| multi_xml                 | 0.5.5        |
| unf_ext                   | <IP_ADDRESS>      |
| unf                       | 0.1.4        |
| domain_name               | 0.5.20160826 |
| http-cookie               | 1.0.3        |
| faraday-cookie_jar        | 0.0.6        |
| fastimage                 | 1.6.8        |
| mini_magick               | 4.5.1        |
| xcpretty-travis-formatter | 0.0.4        |
| i18n                      | 0.7.0        |
| thread_safe               | 0.3.5        |
| tzinfo                    | 1.2.2        |
| activesupport             | <IP_ADDRESS>      |
| json                      | 1.8.3        |
| excon                     | 0.54.0       |
| xcodeproj                 | 1.3.3        |

*generated on:* **2016-11-11**

@seanscal Can you erase the simulators on the machine in question? That should clear this up in most cases. Thanks!

@TKBurner this has just started happening with one of the other builds on different machines as well.  It happens every time on the one machine with all of our builds that run tests, and then sporadically is happening on the other machines as well now within the last two or three days

also, do you mean reset all the simulators or uninstall then reinstall

@seanscal Is it occurring more on a slower machine? It looks like a timeout of some sort. Thanks!

I had this issue occur, but mine might be a little different. I'll list my issue and solution in case it might help you out.
I had a test bundle with empty test. Whenever scan ran on it, it would just timeout there.

What i did was disable the bundle.
Before running any test, i would boot up the simulator first, then wait to give it time to load.
Then clean out any previously install app on it. Then run scan.

@TKBurner sorry i dont know why I didnt see this, but this is a early 2015 macbook that we run builds on which is faster than one other one and should be about the same speed as our third. I'm not sure why timeouts would happen on this and not the slowest machine, where jenkins builds take like 12 minutes, while on these 2 they take around 4-5
@lam2558 thanks for the help, but I dont think it applies to my situation sadly :(.

Hallo,
i got the same error now on two machines (10.11 and 10.10). First it worked correctly.
I only use snapshot.
Resetting & Deleting of the simulators does not fix the the problem.

Bad news, my only solution was to completely re-install the OSX.  That worked. I'm all set

Hello to all.
I got the same error with fastlane scan. I spent many hours before found the problem. Maybe someone will got the same.
The real bug is not the "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted". Before this message I found in logs the another message, more important:
"Cannot launch simulated executable: no file found at /Users/me/Library/Developer/Xcode/DerivedData/MyApp-gltkodapbbvlitfeuqbhsjilahgz/Build/Intermediates/CodeCoverage/Products/Debug-iphonesimulator/MyApp.app"
Here is a full example:
13:44:14 /Users/me/Library/Developer/Xcode/DerivedData/MyApp-gltkodapbbvlitfeuqbhsjilahgz/Logs/Test/9F2E8733-A6AE-4AD3-8BE6-D4BB5A70D6E8/Session-MyAppTests-2017-03-06_154355-xpXd2q.log

13:44:14 2017-03-06 15:43:55.242 xcodebuild[20233:269415] Error Domain=IDEFoundationErrorDomain Code=1 "Cannot launch simulated executable: no file found at /Users/me/Library/Developer/Xcode/DerivedData/MyApp-gltkodapbbvlitfeuqbhsjilahgz/Build/Intermediates/CodeCoverage/Products/Debug-iphonesimulator/MyApp.app" UserInfo={NSLocalizedDescription=Cannot launch simulated executable: no file found at /Users/me/Library/Developer/Xcode/DerivedData/MyApp-gltkodapbbvlitfeuqbhsjilahgz/Build/Intermediates/CodeCoverage/Products/Debug-iphonesimulator/MyApp.app}

13:44:14 2017-03-06 15:43:55.242 xcodebuild[20233:269415] Error Domain=IDETestOperationsObserverErrorDomain Code=5 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}
13:44:14 ** TEST EXECUTE FAILED **

When I looked into the Session-MyAppTests-2017-03-06_154355-xpXd2q.log I found the launch command, something like this:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace MyApp.xcworkspace -scheme MyApp -destination "platform=iOS Simulator,id=FA7DF862-A049-47C5-93B7-070483AA7B33" -derivedDataPath /Users/me/Library/Developer/Xcode/DerivedData/MyApp-eleawdbfycuswrcieexbehcqpbef clean test-without-building

Then I realized that something strange in the end of string: test-without-building — this is the real problem! But why?
Because my .env config contained incorrect value of the SCAN_TEST_WITHOUT_BUILDING=0 environment variable.
The strangest fix that I could imagine... ta-da-a: ```SCAN_TEST_WITHOUT_BUILDING=false`. Yep, zero value is not equal false

It just started happening to me on my Jenkins build slaves tonight. After I upgraded to fastlane 2.22.0.
On my own dev computer fastlane scan runs my tests just fine.

I got it on a scan step on Travis ... I assume was simulator. But leaving here for info:
2017-03-22 19:29:46.165 xcodebuild[1687:7465] Error Domain=IDETestOperationsObserverErrorDomain Code=5 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}
Testing failed:
Test target <DeletedName> encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **
[19:29:50]: Exit status: 65

Actually this was not at all related to the discussion here. Same symptom - I saw Error Domain=IDETestOperationsObserverErrorDomain but as it turned out, this was from a crash right on launch in the application stack that we were able to get fixed. Unfortunately, I assumed this was fastlane - since I had just upgraded to the new release. Always check the device log!

For us it was caused either by Xcode asking for debugging permission credentials or because we had to deselect code coverage in the scheme, save and select code coverage again. So not exactly sure which one solved it.

I had this and fixed it by deleting an empty test target as mentioned by someone above.

I'm seeing this issue when trying to set up Travis for RxStarscream. No fastlane so it is definitely not fastlane specific. I'm really not sure what it is, I've tried everything and running the command locally works absolutely fine.
https://travis-ci.org/freak4pc/RxStarscream/builds/227625861
https://github.com/freak4pc/RxStarscream/blob/feature/travis-ci/.travis.yml

I've seen this error and tracked it down to different problems each time (none with Fastlane):

A crash when the app initially starts up on the simulator; this is actually a great error to find if you running tests on a PR - will prevent developers from committing this crash.
The app could not be loaded because a library was missing (example: Library not loaded: @rpath/libswiftXCTest.dylib). I had to set Runpath to include @loader_path/Frameworks and then it was able to load this library.
A communication channel error: Connection peer refused channel request for "dtxproxy:XCTestManager_IDEInterface:XCTestManager_DaemonConnectionInterface"; channel canceled. I am not sure what the solution to this one is - however I have seen something like this on my own computer running tests on the simulator - occasionally it cannot connect. Restarting the simulator or even my computer itself will fix it. Would love to know a better way.

This issue just started happening for me, but there are things that puzzle me

The issue started happening on existing project
The project was using fastlane scan for at least a year and this issue was extremely rare
After I removed 1 file from the project and added 1 pod to it, the issue now happens every run
It occurs both on my local machine as well as on CI
We have a handful of CI build agents, and so far it happened on 4 of them at least
The version of fastlane is 2.12.0 and this version as used with this project for a long time, at least 3 months or so

I can see that simulator is launching and then has a spinner like so:

And while it spins and is booting, the tests fail with 65 error code.
2017-05-15 23:41:44.993 xcodebuild[23689:289454] Error Domain=IDETestOperationsObserverErrorDomain Code=5 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}
2017-05-15 23:41:45.008 xcodebuild[23689:289986] Connection peer refused channel request for "dtxproxy:XCTestManager_IDEInterface:XCTestManager_DaemonConnectionInterface"; channel canceled <DTXChannel: 0x7fabacac4510>

Testing failed:
Test target X encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **
[23:41:45]: Exit status: 65

Update, just tried with fastlane 2.30.2 - same issue.
It's as if the project somehow builds super fast and tries to run tests before simulator is ready.
For some reason scan neither waits for simulator to get ready nor does it retry to run the tests at least few more times.

I tend to have the simulator up and running first before any test is run.
Can you try to put this in your fastfile::
ENV["FASTLANE_EXPLICIT_OPEN_SIMULATOR"] = "2"

I recently had the problem where a number of builds failed because the simulator could not be communicated with.
I started running this script before using fastlane scan - to kill the simulator and wipe it clean. It has eliminated much of these errors. It still happens occasionally but much less frequently.
echo "Shutting down the simulator app"
osascript -e 'quit app "Simulator"'

echo "Making sure ALL simulators are shutdown"
xcrun simctl list | grep Booted | grep -e "[0-9A-F\-]\{36\}" -o | xargs xcrun simctl shutdown

echo "Erasing apps from all simulators and resetting back to clean state"
xcrun simctl erase all

echo "Killing com.apple.CoreSimulator.CoreSimulatorService"
killall -9 com.apple.CoreSimulator.CoreSimulatorService

@lam2558 thanks for suggestion, though that didn't make any difference
@RichardGuion
I'm using something similar:
def kill_simulators
  Action.sh("killall -9 Simulator 2>/dev/null || echo No simulators running")
end

and then using FastlaneCore::Simulator to reset things:
    # Reset simulator
    if Env.reset_simulator?
      puts "Reset simulator: iOS #{CIConfig.full_test_device_name}"
      FastlaneCore::Simulator.reset(name: CIConfig.test_device_name, os_version: CIConfig.test_device)
      kill_simulators # Kill simulators again (otherwise builds may get stuck)
    end

Probably the logic to reset simulator is missing some bits...
Anyways, I've tried the steps you have suggested.
The main difference is that now the tests fail with the same error, while simulator is showing progress bar, not a spinner :)

So, maybe it helps to narrow it down.
In my case adding new pod to main target is what's causing the issue.
Some facts:

Mix-n-match dynamic framework project (ObjC + Swift)
No pods for main target until making the change
Added pod is Swift Result pod version 3.2.1
After adding the pod I can't run unit tests in Xcode either and getting this error:

So at least in my case, failing tests from command line seem to be same as in Xcode.

OK, so in the end solution for my trouble was re-integrating cocoapods.
pod deintegrate then pod install.
I've noticed that doing so changes some of the CocoaPods autogenerated files, such as "copy frameworks" shell script and few other xcconfigs.
This may not be the case if you don't use cocoapods though...

@mgrebenets Xcode 8.2.1 wasn't kind to us, are you still seeing issues using the most current fastlane and Xcode 8.3.2?

I also ran into this issue with Xcode 8.3.2 using Cocoapods and the latest fastlane. Following these notes helped solving the issue! All I had to do is add $(FRAMEWORK_SEARCH_PATHS) to the LD_RUNPATH_SEARCH_PATHS of the test targets

Proposed fixed don't seem to work. Is this still a problem for someone?

I too had the same problem when creating xcodebuild  test  from Jenkins.
I Fixed the problem by manually do test from Xcode and then run the xcodebuild trest command/script from Jenkins . I was using Xcode 9 beta version. Try it out comment if this solution works for you guys

Fix doesn't appear to work for me either.

For me the problem was that the test target was not running locally either, because of missing cocoapods framework

My team has been running into this issue quite a bit on our Jenkins builds. We have to constantly restart the simulators, then the builds until they pass.

Hey @ryang1428 what version of Xcode are you using?

This is occurring to me as well, using Xcode 8.3.3 on a mac mini in the cloud. Xcode server consistently fails as a result of this issue.

This seems to have started occurring once we added multiple test sub-targets to the test scheme.

Not sure if this will help, but after some more investigation I'm only ever seeing this on more memory constrained machines (CI, our cloud mac mini). When I run the same scheme (which runs several different test targets) on an iMac, even repeatedly this issue has yet to occur. On CircleCI it's somewhat infrequent, which leads me to believe under load this happens on Circle. Lastly, this happens 100% of the time now on our cloud mac mini, and considering just running Xcode seems to put that machine under load, maybe CPU/memory load has an impact on this?
What else could cause the simulator to fail to restart?

Sorry @ohayon I just saw your reply-- but we are seeing this on Xcode 8.3.3

Not sure if this helps or not, but I was getting a similar error (code 1 instead of 6) and digging down into the system logs provided a lot more context. Whenever the build was running, I checked the device under "Devices" in Console.app on the box. I found out an architecture was missing in the build and it was causing trouble. Updating my build products and scheme solved the issue for me.

Its been happening several times a day this week:
▸ Signing /Users/jenkins/Library/Developer/Xcode/DerivedData/WhiteLabelClient-elfzwalyuregzmcqaqtuwmdvsygb/Build/Intermediates/CodeCoverage/Products/Debug-iphonesimulator/WhiteLabelClient.app/PlugIns/WhiteLabelClientTests.xctest
2017-09-27 16:20:21.421 xcodebuild[41567:1873091] Error Domain=IDETestOperationsObserverErrorDomain Code=6 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}

Testing failed:
Test target WhiteLabelClientTests encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **
ERROR [2017-09-27 16:20:21.81]: Exit status: 65
/Users/jenkins/.gem/gems/fastlane-2.59.0/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `build_failure!': [!] Error building the application - see the log above (FastlaneCore::Interface::FastlaneBuildFailure)
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/fastlane_core/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/error_handler.rb:24:in `handle_build_error'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/runner.rb:42:in `block in test_app'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/fastlane_core/lib/fastlane_core/command_executor.rb:88:in `execute'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/runner.rb:34:in `test_app'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/runner.rb:14:in `run'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/manager.rb:14:in `work'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/commands_generator.rb:40:in `block (2 levels) in run'
	from /Users/jenkins/.gem/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
	from /Users/jenkins/.gem/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in `run'
	from /Users/jenkins/.gem/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:64:in `run!'
	from /Users/jenkins/.gem/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in `run!'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/commands_generator.rb:59:in `run'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/scan/lib/scan/commands_generator.rb:11:in `start'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/fastlane/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
	from /Users/jenkins/.gem/gems/fastlane-2.59.0/bin/fastlane:20:in `<top (required)>'
	from /Users/jenkins/.gem/bin/fastlane:22:in `load'
	from /Users/jenkins/.gem/bin/fastlane:22:in `<main>'

Xcode 8.3.3
This is using scan 2.59.0

This is happening to me as well. It seems to start happening right after I updated to Swift 4 / Xcode 9. Not sure if running multiple simulators affects it or not.
I am using TeamCity on a Mac mini macOS 10.12.
Using fastlane v2.59.0
Here is the output:
[13:36:19]	[Step 1/1] 2017-09-29 13:36:13.378 xcodebuild[50763:4063673] Error Domain=IDETestOperationsObserverErrorDomain Code=6 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}
[13:36:19]	[Step 1/1]
[13:36:19]	[Step 1/1] Testing failed:
[13:36:19]	[Step 1/1] Early unexpected exit, operation never finished bootstrapping - no restart will be attempted
[13:36:19]	[Step 1/1] ** TEST FAILED **
[13:36:19]	[Step 1/1] [13:36:19]: Exit status: 65```

Any suggestions to get this issue fixed? We are receiving the following error on every CI run.
Had Xcode 8.3.3, switched to Xcode 9 and swift4 but then reverted to old xcode is when we started seeing the following issue: any pointers?
xcodebuild[79910:1503189] Error Domain=IDETestOperationsObserverErrorDomain Code=6 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}
Testing failed:
Test target xx encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted)
** TEST FAILED **

In my case, specifying iPhone and iOS version helped. (make sure that simulator with chosen version is installed)
fastlane scan --scheme "integration" --device "iPhone 7 (10.2)" --clean

In my case, specifying iPhone and iOS version helped. (make sure that simulator with chosen version is installed)
fastlane scan --scheme "integration" --device "iPhone 7 (10.2)" --clean

I had this problem when running tests on iOS 9 simulator (Xcode 9, parallel run with iOS 10 simulator). After we decided to drop iOS 9 tests and only run the suite for iOS 10 and iOS 11, the problem was gone.

I had this problem when I had both Xcode 9.0 and 9.1 one installed and the simulator that was chosen is not displayed in the latest Xcode (something weird there) so I ran xcrun simctl delete <UUID> and the issue was resolved.

What's the status on this ongoing issue? Lots of people still seeing this issue I guess (including me).

Also having this issue on Travis after updating osx_image to Xcode 9.1
Everything was working fine on Xcode 8.2 image.

Ok, so creating a naked project with file > new project > include unit tests > cmd + u works just fine.
Started adding source files from my broken project, one at a time, to the new naked project. I also started adding framework dependencies one at a time.
I reproduced the problem the moment I introduced a specific framework.
The framework was built with Carthage. The Carthage documentation states a few steps that I normally skip. Now it seems, these steps are important.
The following solved my issue.

I applied @rob-nash's answer to my project, but I am still having the same problem, no results on success or failure of UI tests.
But now I cut down on a build script that would "thin" my frameworks, so that was helpful. Thanks!

Hey everyone, as you can see this issue was started over a year ago. I am going to close this issue and if anyone sees something similar to this, I think it would be best to open a new issue so that we can make sure that everything is up to date and we aren't conflating some things that might be caused by different problems given how much code has changed in the past 365+ days 😄  🚀  🐙

I was getting the same error while running scan on our CI agent, and also locally on my machine.
Log file only contains an information like:
Error Domain=IDETestOperationsObserverErrorDomain Code=6 "Early unexpected exit, operation never finished bootstrapping - no restart will be attempted" UserInfo={NSLocalizedDescription=Early unexpected exit, operation never finished bootstrapping - no restart will be attempted}
[07:59:58]	[Step 2/2] Testing failed:
[07:59:58]	[Step 2/2] Early unexpected exit, operation never finished bootstrapping - no restart will be attempted

👉  Finally running test target via Xcode 9.2 helped me!
Here are the steps which help me to fix the problem:
👉  1. Run all tests using Xcode. (What is important here, that only Xcode return a detailed error. I also try to run unit test AppCode, but unfortunately, it ended up without meaningful error)
👉 2. In my case it occurs that while Xcode runs the tests I will receive a runtime error:
Main Thread Checker: UI API called on a background thread: -[UIApplication setApplicationIconBadgeNumber:]

Here is my code when I started receiving Early unexpected exit error.
UNUserNotificationCenter.current().getPendingNotificationRequests {
            (v: [UNNotificationRequest]) in
            UIApplication.shared.applicationIconBadgeNumber = 0
}

and code before the error:
UIApplication.shared.applicationIconBadgeNumber = 0 // I called this line on the main thread

So, as Xcode said I called the setter of applicationIconBadgeNumber not on the main thread. After fixing that and calling the UIApplication.shared.applicationIconBadgeNumber = 0 on main thread my scan start working fine and without Early unexpected exit error
Summary:
I guess in your case it could be a different error, but it is worth to run unit tests using Xcode because(in my case) that was only one way to get a detailed error.
Hope it will help you 😉


Use latest protobuf and prune travis config

@stepancheg

right now you're on an ancient 2.2, because that's the latest version provided by travis' old ubuntu. using 2.6 means you can start adding features like anyof, allow_alias, import public, etc. (see https://github.com/google/protobuf/blob/master/CHANGES.txt)

Ubuntu 12.04 used in travis is ancient indeed. protobuf version in Ubuntu 12.04 is 2.4.1. Anyway, 2.4.1 it is still old.
However, rust-protobuf does not need latest protoc to implement features like anyof. Rust-protobuf git repository contains descriptor.proto and generated descriptor.rs. That descriptor is taken from 2.5, and descriptor from 2.6 can be used instead: descriptor.proto from 2.6 doesn't use modern features and can be compiled even with protoc 2.4.
Modern protobuf is actually needed to implement tests for rust-protobuf (tests, which invoke protoc), but I'd rather made tests of modern protobuf features optional, rather than forced travis to download latest protobuf.
I don't like the idea of downloading protobuf from internet in travis for two reasons:

it adds extra load to travis servers
it makes build fragile, as build may produce false positive in case of network errors

Summary: rust-protobuf does not need latest protobuf to implement modern protobuf features.

I'll just leave this here until you decide that testing all functionality is more important that conserving trivial travis-ci resources (the download is < 2MB).
FWIW, this stuff is almost straight out of travis-ci's own guides http://docs.travis-ci.com/user/installing-dependencies/#Installing-Projects-from-Source.

rebased

Applied.


Fixes #292 Display version number

- Summary
Show the version number in the "settings" dropdown - fixes #292. I also combined the settings menu and user avatar together, which haves the benefit of leaving more space for the search bar on mobile. "-dev" is appending to the version when developing.
- Test plan

- Description for the changelog

Inject the version number from package.json with Webpack and display it in the settings menu (this could lead to an about page)
Combine the settings icon and user avatar together

- A picture of a cute animal (not mandatory but encouraged)

What if we put it in the footer?
Having it in the drop down makes me think that's something I can click on a do something with it.

Seems like it's mainly relevant when debugging. Would it be enough to write it in a console log message when the CMS loads?

I agree with @calavera that placing it in the footer is ideal, but we should try to avoid UI related iterations at this point. For that reason I'd go with @biilmann's approach, as this really is just for debugging.

:+1: will change to console log it

Updated to log to the console:

LGTM


No much performance difference between SAMed and SAMed_h on my own dataset

Thanks for your code. However, I found that there existed less performance difference between SAMed and SAMed_h for my own dataset.
May I know how to fine-tune the parameters to improve the performance of SAMed_h? Shall I change the rank of LoRA adaptation?
Best,
Eric

Thanks for your code. However, I found that there existed less performance difference between SAMed and SAMed_h for my own dataset.
May I know how to fine-tune the parameters to improve the performance of SAMed_h? Shall I change the rank of LoRA adaptation?
Best,
Eric

Hello, I noticed that you have trained using your own dataset. Could you please advise me on how to convert my own dataset into training and testing datasets usable for Samed?  Thank you very much!


Unhandled error with category numbering

I got an unhandled error when trying to number all motions in one category. Setup:
Category A:

Motion One, ID: X
Motion Two, ID: A 2
Category B:
Motion Three, ID: A 1

Obviously, the numbering of category A fails, because ID "A 1" is already defined. But it gives a traceback and this html document (you have to rename it back to .html) in the response. There should be some error-checking and validation to give an structured error to display, maybe which motion is blocking the numbering, so the user can fix it by himself.

I'll test it

Tested: After trying to renumbering I get a correct error message:

So I think we can close it. @normanjaeckel ok?


Exception ticking world pawn

OS: Linux (Manjaro)
Game version: 1.2.2753
Current content BuildID: 5527989
Can be recreated: yes
Cause of issue: Unknown
Relevant log attached: yes
Modlist attached: yes
Description: when running a modded game exceptions are thrown for world pawns who cannot be ticked. This throws an error to the in game log. It does not appear to affect gameplay in the shortterm. The same error/exception is thrown for all known world pawns.
Log.txt
Main.txt

Td enhance is currently not compatible. It will require their code to be modified

Closing bug. Many bugs have been fixed since this was reported. Please reopen in new bug report using the new templates if this issue persists.


Errors during .gb libraries loading are quite obscure

When a .gb library is loaded, but there are errors, it's unclear where the problem happens.
If, for example, a large file is created and loaded:
vm.libFiles = append(vm.libFiles, "my_library.gb")

but it misses an end, the only thing appearing during running a test suite, or the interpreter, is:
Unexpected EOF

without showing in which file the problem is.
Printing the file would help debugging (and make obvious that there is an issue).

This has been fixed in #601


[BUG][Functional] Actions on KMS key's created by the SEA

Bug reports which fail to provide the required information will be closed without action.
Required Basic Info

Accelerator Version:  v1.5
Install Type: Upgrade
Upgrade from version: (v1.3.8)

Describe the bug

The SEA Deploys a few KMS keys within the environment with the names PBMMAccel-*, With AdministratorAccess managed Policy users, can disable the KMS keys and delete the associated tags(for example the accelerator tags).
Users can also delete Key aliases in the sandbox accounts

Steps To Reproduce

log in to a workload account console and search for "Key Management Service"
Select a key created by the SEA and click on "Key actions" and click "Disable"
You should see the key being disabled
You can also switch to the "Tags" tab and click on "edit" and click on "Delete tag" to delete the tag
Login into a sandbox account and search for "Key Management Service"
Select a key created by the SEA and switch to the "Aliases" tab and select the alias and click delete

Expected behavior

The Expected behavior is that the KMS Keys created by the SEA are non-editable by users with admin privileges and users trying to update or edit the KMS keys should get an explicit deny in an SCP

Screenshots

Additional context

Users can disable keys but cannot delete them which is a good thing, but we believe that any kind of actions on the KMS keys created by the SEA should result in an Explicit deny

Peculiar - it should actually work the way you want, given we have this SCP in place:

Your actual SCP should look like this:
"Resource": "arn:aws:kms:::alias/PBMMAccel*", in Organizations.
I just re-tested and I get the same result.
Can I request you open an AWS support case to dive into why this SCP is not working as expected? (as it will be more timely and effective than any analysis by myself)  If you report back a fix, happy to get it incorporated.  I'm going to guess that KMS SCP's currently don't support using the ALIAS in the resource field - which may mean I have no easy mechanism to further protect these objects, unless KMS supports using tags within SCPs.  My initial thoughts.

Hey @Brian969, we have raised an AWS support request regarding the issue, and they came back confirming using Alias in the resource field is not supported and suggested using Keyid in the resource field.
{
"Effect": "Deny",
"Action": [
"kms:DeleteAlias",
"kms:UpdateAlias",
"kms:DisableKey",
"kms:ImportKeyMaterial",
"kms:PutKeyPolicy",
"kms:ScheduleKeyDeletion"
],
"Resource": "arn:aws:kms:::key/",
"Condition": {
"ForAnyValue:StringEquals": {
"aws:ResourceTag/Accelerator": "PBMM"
},
"ArnNotLike": {
"aws:PrincipalARN": [
"arn:aws:iam:::role/PBMMAccel-*"
]
}
}
}
But restricting with tags, we also need to make sure who has access to the tags so they don't get around it by simply tagging("kms:TagResource") or untagging(kms:UntagResource) them

SCP in reference-artifacts updated to fix.


Chrome debugging broke in 0.22 (weird breakpoints, no variables shown/console.log'able)

Hi there,
I upgraded from 0.20 to 0.22 and Chrome debugging went completely off the rails. I had no issue before updating to 0.22. I'm attempting to debug in an iOS project on Chrome 49.
Some sample code just to demonstrate what I mean.
function (someVariable) {
  let someOtherVariable = 123
    , somePromise = getSomePromise(someVariable);

  somePromise.then(r => {
    if (r.someCondition) {
      doSomething(r);
    }

    doSomethingElse();
  });

  ...
}

Setting breakpoints acts strangely as it sometimes jumps down a line or two. If I try to add a breakpoint on the if line, it will actually end up adding it to the empty line above doSomethingElse().
Variables don't show correctly. If I set a breakpoint on somePromise.then(r => { (line 4) and I hover over someOtherVariable then Chrome Debugger won't show anything. If I go into the console and type console.log(someOtherVariable) I get an error VM144:1 Uncaught ReferenceError: someOtherVariable is not defined(…). I can view the value of someVariable just fine if I hover over it, this variable was passed into the method.

These issues are sporadic and not very consistent and I haven't noticed any pattern as to when it happens and doesn't happen. Very odd behavior and I'm not sure what I can do about this.

someOtherVariable is no longer lexically referenced from that point on in the program so Chrome / V8 might mark it as eligible for cleanup, hence the non-determinism.

Does it happen with master or 0.23-rc?

That was a sample @ide, in my actual code that variable is still referenced. My apologies.
I just downgraded to 0.21 and can confirm that it's working again. Let me try 0.23-rc real quick.

@satya164 Indeed it appears to be working on 0.23-rc1.
Looks like whatever the issue was will be fixed going forward, but let me know if there is any more information I can provide on this.

@aforty Thank you.

I see this bug with RN 0.53.. I tried with the trick of renaming all function with arrow funtions. Still the same bug


Package doesn't work with Google-Maps-iOS-Utils (~> 3.0.0)

Bug report
Ran into this issue http://<IP_ADDRESS>/66966465/react-native-maps-ios-build-issues-when-using-use-frameworks-linkage-stati when installing https://github.com/prscX/react-native-app-tour.
Found a fix which involves updating to use Google-Maps-iOS-Utils 3.0.0 https://github.com/googlemaps/google-maps-ios-utils/issues/23#issuecomment-579467769, however when I go to utilize as prescribed, I receive this issue running pod install
[!] CocoaPods could not find compatible versions for pod "Google-Maps-iOS-Utils":
In Podfile:
Google-Maps-iOS-Utils (~> 3.0.0)
react-native-google-maps (from `../node_modules/react-native-maps`) was resolved to 0.28.0, which depends on
  Google-Maps-iOS-Utils (= 2.1.0)

Specs satisfying the Google-Maps-iOS-Utils (~> 3.0.0), Google-Maps-iOS-Utils (= 2.1.0) dependency were found, but they required a higher minimum deployment target.
Environment info
<!--
  Please specify the react, react-native, react-native-maps versions, eg:

    "react": "16.11.0",
    "react-native": "0.62.2",
      "react-native-maps": "github:react-native-community/react-native-maps",

    Target Platform: --simulator="iPhone 11 Pro Max (13.7)"

    Using GoogleMaps

We should probably update the podspec file here but will need to test for any breaking changes.

@christopherdro yeah would be GoogleMaps 3.7.0 and iOS-Utils 3.0.0

@n3rd253 can you submit a pull request with those updated?

Any activity on this one @christopherdro? Ran into aa similar problem as OP.

It seems like the only breaking change listed in v<IP_ADDRESS> is update GMUFeature interface to conform to spec #rfc7946. Not sure if that breaks anything in react-native-maps? The rest seems to be bugfixes and new features.


Add defaults to custom fields

This is the most obvious thing that Personal Text / Blurb can do that custom fields currently can't. Besides being shown without title, which I've already got done in my own code.

I thought it was already there, but it not!... heck I know close to nothing about custom fields! xD
Anyway, just to be kind of consistent, take in consideration that in 1.0.6 I did some changes to radio and selects regarding the default value https://github.com/emanuele45/Dialogo/commit/6d010104884895e1121f29a36587353b06ebaa70
It's not yet merged into development, I'll bring it soonish.
It shouldn't conflict with this, but just in case if there is anything that may be re-used. ;)

@emanuele45 you closed this but didn't merge the pr?

Darn github! xD
I forgot development bugs are closed automatically...


Helm Deploy returns 404 when using prefix

Checks

[X] I have checked for existing issues.
[X] This report is about the User-Community Airflow Helm Chart.

Chart Version
1.70
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.0", GitCommit:"a866cbe2e5bbaa01cfd5e969aa3e033f3282a8a2", GitTreeState:"clean", BuildDate:"2022-08-23T17:44:59Z", GoVersion:"go1.19", Compiler:"gc", Platform:"windows/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.13-eks-fb459a0", GitCommit:"55bd5d5cb7d32bc35e4e050f536181196fb8c6f7", GitTreeState:"clean", BuildDate:"2022-10-24T20:35:40Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}

Helm Version
version.BuildInfo{Version:"v3.9.4", GitCommit:"dbc6d8e20fe1d58d50e6ed30f09a04a77e4c68db", GitTreeState:"clean", GoVersion:"go1.17.13"}

Description
I was trying to set prefix for the URL so that I can access Airflow by following URL: http://some_url.com/test.
However the UI returns 404. On the deploy side,  airflow UI can still be accessed by doing portforward from 8080.

Take a look at the FAQ on setting up Ingresses with the chart
Take a look at the ingress.* section of the values for information about what values are possible to set

I recommend against using the airflow.extraEnv values to set configs, instead please use airflow.config.

Take a look at the FAQ about setting airflow configs


Hide Misses

What is your question?
How do I hide the score, misses, and rating?

function onCreatePost()
     setProperty('scoreTxt.visible')
end

thx


[regression in runc v1.0.0] Cannot run a container on fedora 34 since containerd 1.4.8 upgrade (cannot fetch program from id: get program by id: permission denied)

Description
I am not able to run a container on fedora 34 since containerd 1.4.8 upgrade, neither with docker nor with nerdctl. I always get the following error message:
FATA[0000] OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: cannot fetch program from id: get program by id: permission denied: unknown

Steps to reproduce the issue:

Start containerd with systemd
Try to run a container with nerdctl: sudo ./nerdctl run hello-world

Describe the results you received:
Following error message:
FATA[0000] OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: cannot fetch program from id: get program by id: permission denied: unknown

Describe the results you expected:
I expected the container to run
What version of containerd are you using:
$ containerd --version
containerd containerd.io 1.4.8 7eba5930496d9bbe375fdf71603e610ad737d2b2

Any other relevant information (runC version, CRI configuration, OS/Kernel version, etc.):
runc --version
$ runc --version
runc version 1.0.0
commit: v1.0.0-0-g84113ee
spec: 1.0.2-dev
go: go1.15.14
libseccomp: 2.5.0

I noticed that this commit: https://github.com/containerd/containerd/commit/34861f1aa3d6666381e5a9539289598db0b37381 changed the runc version to 1.0.1, while I'm still on 1.0.0. If this is the cause of this issue, please close it, as runc 1.0.1 should be available soon for fedora 34: https://src.fedoraproject.org/rpms/runc
uname -a
$ uname -a
Linux pils 5.12.15-300.fc34.x86_64 #1 SMP Wed Jul 7 19:46:50 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Upgrading containerd to 1.5.3 (package taken from this build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1781152) fixed the issue, both with nerdctl 0.10.0 and docker 20.10.7. An install from fedora 34's default containerd package still fails though

Yes, looks like this was a regression in runc v1.0.0, and fixed by https://github.com/opencontainers/runc/pull/3055, which was back ported in https://github.com/opencontainers/runc/pull/3087 for v1.0.1

https://github.com/containerd/containerd/pull/5753 updates the containerd 1.4 release branch to use runc v1.0.1, but it has not yet been included in a release

As a "workaround", setting SELinux to "permissive" works (but of course removes protection of SELinux for other things);
setenforce 0
docker run --rm alpine echo hello-world
hello-world

setenforce 1
docker run --rm alpine echo hello-world
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: cannot fetch program from id: get program by id: permission denied: unknown.
ERRO[0000] error waiting for container: context canceled

Oh great! I guess this can be closed once 1.4.9 is out then ?

Yes, I asked the maintainers to consider doing v1.4.9 and v1.5.5 releases with runc v1.0.1. I only just asked, so haven't had a reply yet.

This also worked for me on Fedora 34 after the last containerd update:
sudo setenforce 0
Now my projects will start without error.

This also worked for me on Fedora 34 after the last containerd update:
sudo setenforce 0
Now my projects will start without error.

Thanks man, you solution work for me

Great! As mentioned; really consider it a "workaround"; as of course, disabling SELinux is not something to "recommend", makes security people weep, can lead to cute fluffy kittens being tortured, and so on.  I am awaiting the proper fix from upstream.

This also worked for me on Fedora 34 after the last containerd update:
sudo setenforce 0
Now my projects will start without error.

An other solution is to just downgrade the package and wait for 1.4.9
dnf downgrade containerd.io

Same here, I downgrade the containerd.io back to 1.4.6

Same here, but still on Fedora 33. Downgrading is what I do.
Disabling SElinux is not an acceptable workaround. Sailors will drown if we go that route.

I too just downgraded. Thought maybe an update would have come by now. nbd, thanks to the maintainers for all their hard work!

Same issue. See:

containerd v1.4.9 and v1.5.5 have been released, which have runc v1.0.1: https://github.com/containerd/containerd/releases
If you're using docker's containerd.io package from download.docker.com, new packages of v1.4.9 have been published (download.docker.com does not yet have packages for containerd v1.5.x)
A patch release of Docker (20.10.8) will also be available soon (hopefully start of next week) for people that use the static binaries (which bundles docker, the docker cli, containerd and runc in a single tar) or the official docker-in-docker images from https://hub.docker.com/_/docker/)
Let me go ahead and close this ticket


copy database wizard - file table error

i just want to mention, when using copy wizard, if you want to move database with file table it wont work because of same directory name for  "filestream directory name"
if you use attach and detach method, it works but could not reattach original database
so i think an option is needed in the wizard for defining new name
(i will go and report it in SSMS either, just a good idea to mention here)

@stevestein Hi Steve, My guess is that @gmareater has in mind the following articles. Can you take a look.  Thanks.
.
"Use the Copy Database Wizard"
https://docs.microsoft.com/sql/relational-databases/databases/use-the-copy-database-wizard?view=sql-server-2017
.
"Copy Databases to Other Servers"
https://docs.microsoft.com/sql/relational-databases/databases/copy-databases-to-other-servers?view=sql-server-2017
.
(Steve:  GitHub Issues, Process info)
sqlcontentshiproom Notebook  >  sql-docs-pr  >  GitHub-ISSUES-Plan,-Rogue1
.
(GeneMi ,  2018/11/26  10:10am  Monday)

@gmareater can you please include the URL of the specific article you are referring to?  Even better, could you please click the "Edit" button on the topic and suggest an edit and we can review the PR. If you suggest an edit in the actual topic will ensure we are all working on the correct / same thing. @stevestein fyi.

@craigg-msft @stevestein @gmareater This sounds like a feature request and perhaps a request for a doc note saying that the copy wizard doesn't work when a file table in involved. I wonder if it works when the T-SQL equivalent is used.

hi
I tried my best and created PR
this is the artice i mean
"
https://docs.microsoft.com/en-us/sql/relational-databases/databases/use-the-copy-database-wizard?view=sql-server-2017
"
thanx
On Wed, Dec 5, 2018 at 4:26 AM Carl Rabeler<EMAIL_ADDRESS>wrote:

@craigg-msft https://github.com/craigg-msft @stevestein
https://github.com/stevestein @gmareater https://github.com/gmareater
This sounds like a feature request and perhaps a request for a doc note
saying that the copy wizard doesn't work when a file table in involved. I
wonder if it works when the T-SQL equivalent is used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/sql-docs/issues/1331#issuecomment-444316963,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF61OcGfdhMiojPZ3wbtNK4qwXehPl1bks5u1xm2gaJpZM4YxuOI
.

@gmareater - Thanks for creating the PR and adding this info to the article.  I made a minor edit to your addition directly into your PR. The updated article should go live sometime today.
Thanks!


recognize_file() missing 1 required positional argument: 'self'

Hi...
When a i trying to run this code:
try:
api_response = api_instance.recognize_bytes(image_bytes, secret_key, country, recognize_vehicle=recognize_vehicle, state=state, return_image=return_image, topn=topn, prewarp=prewarp)
pprint(api_response)
except ApiException as e:
print "Exception when calling DefaultApi->recognize_bytes: %s\n" % e
I obtain this error: recognize_file() missing 1 required positional argument: 'self'
Can somebody tell me why?

Hi,
Problem it's solved,
Changin this line: api_instance = openalpr_api.DefaultApi
For this: api_instance = openalpr_api.DefaultApi()


ie11 file origin does not match viewer's origin

Hi,
PDF.JS : latest release (v1.9.426)
Tested on IE11 (11.192.16299.0)
Use case : I get pdf js sources and I do a gulp minified.
When I open my viewer, it works on all Browser except Internet explorer.
I got this error : "file origin does not match viewer's origin"
Inside pdf.viewer.js script (yeah, i read minified js =P), the part
if(new URL(e,window.location.href).origin!==t)throw new Error("file origin does not match viewer's")
Throw an error
because
new URL(window.location.href).origin is undefined
I saw on an issue where you explained that you use a polyfill for javaScript URL object (https://github.com/mozilla/pdf.js/issues/9358) but it doesn't seems to work on internet explorer 11.
To help you, I tried this one https://github.com/lifaon74/url-polyfill/blob/master/url-polyfill.js which seems to work great on IE11.
I'll do a temporary work around to avoid this error on my own project (literally skip throw error).

The URL polyfill in src/shared/compatibility.js overrides the URL constructor if origin is not supported.
The default demo viewer works fine for me when I open the viewer in IE 11.1000.17074.0 (and also an older version, IE11.0.9600.17728).
This is therefore not an issue with the default viewer.
I also ran gulp minified from the master branch, and simulated a broken URL API with the following test case:
<script>delete URL.prototype.origin</script>
<script src=pdf.js></script>
<script>document.write(new URL(location.href).origin)</script>

and the test passed (localhost was being printed, instead of undefined).
Did you load pdf.js before pdf.viewer.js?

You're right.
I tested my use case with pdf.js included and it works perfectly.
I wasn't sure about what scripts should be included, because some script are loaded inside library and it worked with other browser.
But.. the online demo https://mozilla.github.io/pdf.js/web/viewer.html include pdf.js and I didn't notice.
Mea culpa.

Still doesn't work on IE11, I have a second problem. Yesterday I tried :
new URL(window.location.href).origin
And this line works fine.
But when a parameter is added inside pdf.viewer.js, it doesn't seems to work.
I added some logs to pdf.viewer.js :
if (new URL(e, window.location.href).origin !== t){
  console.log('new URL(e, window.location.href).origin', new URL(e, window.location.href).origin);
  // result : new URL(e, window.location.href).origin null
  console.log('e', e);
  // result : e blob:E953C0C2-1552-4A49-9A50-54F7753827B2
  console.log('t', t);
  // result : t https://myurl
  console.log("file origin does not match viewer's")
}

new URL(e, window.location.href).origin return null.

That "problem" is not IE-specific.
The code/logic in its current form is introduced by #6916, and was designed to block cross-origin requests.
We could allow blob:-URLs, since they can only be loaded if the blob:-URL is created by the same origin as where the viewer is hosted, e.g. like this:
diff --git a/web/app.js b/web/app.js
index e1891650..fe442c85 100644
--- a/web/app.js
+++ b/web/app.js
@@ -1501,11 +1501,12 @@ if (typeof PDFJSDev === 'undefined' || PDFJSDev.test('GENERIC')) {
         // Hosted or local viewer, allow for any file locations
         return;
       }
-      let fileOrigin = new URL(file, window.location.href).origin;
+      let inputFileUrl = new URL(file, window.location.href);
       // Removing of the following line will not guarantee that the viewer will
       // start accepting URLs from foreign origin -- CORS headers on the remote
       // server must be properly configured.
-      if (fileOrigin !== viewerOrigin) {
+      if (inputFileUrl.origin !== viewerOrigin &&
+          inputFileUrl.protocol !== 'blob:') {
         throw new Error('file origin does not match viewer\'s');
       }
     } catch (ex) {

@yurydelendik Is blob: in file= something that we want to support?
Side note: There are other URLs that can be loaded without CORS, such as data: and filesystem:.
To avoid cross-origin content spoofing, data: should still not be allowed.
Since the filesystem:-URL is only generated for the long-deprecated and Chrome-only Filesystem API, I don't think that we need to check for that either.

Is blob: in file= something that we want to support?

Ideally, yes. Not sure about IE11 though -- its issue with URL.createObjectURL not generating origin. (BTW, can blob's be cross origin?) We moved HTTP transport to the API side, and if there is a need, we can special case such schemas as data:, blob: or file:.

So actually, this problem is IE-specific.
blob:-URLs are specified to include the origin of the creator in the URL: https://www.w3.org/TR/2017/WD-FileAPI-20171026/#unicodeSerializationOfBlobURL
Firefox, Chrome, Safari, Opera, Edge do match the standards.
Internet Explorer does not, it creates URLs that look like blob:UUID instead of blob:origin/UUID.

BTW, can blob's be cross origin?

No, blob:-URLs can only be loaded by same-origin execution contexts (documents, workers).

Thank you for your expertise and the fix ; you are reactive, I really appreciate it :)
Can I close this issue ?

Closing since this is fixed by the PR above.


Custom key bindings don't work depending on selected layer type

🐛 Bug
Hi all,
I noticed that custom key bindings are ignored depending on what layer type is selected, e.g. the "d" key is overwritten when a labels layer is selected.
To Reproduce
After installing napari 0.4.8 run this code:
import napari
import numpy as np

# create a viewer window
viewer = napari.Viewer()
viewer.add_labels(np.asarray([[1,2],[3,0]]))

# bind short cuts to functions
@viewer.bind_key("d")
def right(event):
    print("d")

# Start napari
napari.run()

The custom key-binding on key "d" is ignored. No error or warning shows up.
Expected behavior
I would argue that custom key bindings should have a higher priority than predefined key bindings. It would be nice if
a) custom key bindings are taken into account first, or
b) a warning shows up that custom bindings are ignored or
c) a function exists that allows to deactivate pre-defined key bindings.
Environment

Please copy and paste the information at napari info option in help menubar here:

napari: 0.4.8rc1
Platform: Windows-10-10.0.19041-SP0
Python: 3.8.6 (tags/v3.8.6:db45529, Sep 23 2020, 15:52:53) [MSC v.1927 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.4
NumPy: 1.20.2
SciPy: 1.6.3
Dask: 2021.04.1
VisPy: 0.6.6
OpenGL:

GL version: 4.6.0 - Build <IP_ADDRESS>29
MAX_TEXTURE_SIZE: 16384

Screens:

screen 1: resolution 1920x1080, scale 2.0

Plugins:

clEsperanto: 0.9.0

console: 0.0.3

napari_webcam: 0.1.12

scikit-image: 0.4.8rc1

svg: 0.1.5

Any other relevant information:

Additional context

Running this from ipython (and changing to 1, because d is not longer bound) I do get a warning:
ValueError: key combination 1 already used! specify 'overwrite=True' to bypass this check
But from a script it's silent.
Can we print the warning from script too?

Using the following example code in 0.4.18:
import napari
import numpy as np

# create a viewer window
viewer = napari.Viewer()
viewer.add_labels(np.asarray([[1,2],[3,0]]))

# bind short cuts to functions
@viewer.bind_key("1")
def right(event):
    print("1 pressed")

Only works when the labels layer is not selected and does nothing when the layer is selected and the 1 works to select the eraser tool.
No error is returned.
Adding overwrite=True has no effect.
Same behavior on main 12c371cd656c12c61e0a53b1b92d85670e7efd8f`

For anyone who needs it, I find this works:
`
from app_model.types import KeyCode, KeyMod
from napari.layers.labels.labels import Labels
from napari.layers.image.image import Image
@Image.bind_key(KeyCode.KeyZ, overwrite=True):
def func1()
print(" ")
@Labels.bind_key(KeyCode.KeyZ, overwrite=True):
def func2()
print(" ")
`
Got the hints from here:
https://github.com/napari/napari/blob/main/napari/layers/labels/_labels_key_bindings.py

@XiaopengZzh You're on the right track, but your code snippet doesn't work!
Try something like:
@Image.bind_key(KeyCode.KeyZ, overwrite=True)
def func1(event):
     print("Z pressed")

the import can be simplified to from napari.layers import Image


syncSLErepos: retry sync until repomd is there

There seems to be a race with the OBS repopublisher, which first
syncs the rpms and then repodata. as an imperfect quick hack,
lets repeat sync until repodata is there.

untested

@dirkmueller Still untested?  LGTM


pull request for e2e test at 11/22/2016 00:56:06

: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.


SteamVR Unity Toolkit an Networking VR?

It is possible to add a very important feature: Networking VR??
A superb Network Library like DarkRift (https://www.assetstore.unity3d.com/en/#!/content/16711) is free for 20 users !! The developer is writing the new core that is opens source: https://github.com/DarkRiftNetworking/Hazel-Networking
(for info: http://forum.unity3d.com/threads/darkrift-networking-2-the-next-level-of-networking.380800/page-2)
Please add Networking VR,  I dream the Metaverse!!
Your framework is awesome!!
Also only a tutorial or an example: Is it complex? How to integrate this features?

Quite a few people have been using PhotonPUN with VRTK (and also PhotonBolt) they seem to be having relative success.

Any examples? Tutorial? Thanks...

Multiplayer for VR is just the same as normal multiplayer. You can start learning through Photon tutorials.https://doc.photonengine.com/en/pun/current/tutorials/photon-unity-and-networking-links
The hands and headset position of other network players are synchronized just like any other game object (by sending their transform info).


Convert modals into modal templates

Currently every page (except of Exporting) has a set of 3 modals. This should be replaced by a singular modal template for each of modal types to save space and prevent the neccessity of having to change the code in all of them whenever a small change is required. This is also how Angular does it with Reactive Forms.

Turns out this was a real bad idea XD. Because Redux Store gives access to the state globally a lot of the pointless code has been removed, thus I am closing this.


openstack: avoid NPE when there's only an image attached

It's possible to not create a storage map when only an image is attached to a VM, this will lead to an NPE later on

It's possible to not create a storage map when only an image is attached to a VM, this will lead to an NPE later on

I find the commit message sophisticated

How about:
When we don't have a VM that only has image attached, we need to make sure that a storage map exists. Otherwise, we will result in NPE.

@bennyz please backport


Tips on replacing wkhtmltopdf/KnpSnappyBundle with WeasyPrintBundle

Hello,
for a use case of generating A4 from HTML pages (for email attachments), I have noticed while switching from KnpSnappyBundle to WeasyPrintBundle, the output font text ends up much bigger, while keeping an overall layout coherence:
KnpSnappyBundle:
	return $this->knpSnappy->getOutputFromHtml($html, array(
		'orientation' => 'portrait', // or Landscape
		'page-size' => 'A4',
		'encoding' => 'utf-8',
		'dpi' => 72,
		'enable-local-file-access' => true,
	));

WeasyPrintBundle:
       // for available options
       // @see \Pontedilana\PhpWeasyPrint\Pdf::configure
       return $this->weasyprintPdf->getOutputFromHtml($html, array(
           'encoding' => 'utf-8',
       ));
   }

with the following added to the source HTML <style> tag to "enforce" A4 page size
    @page {
        /* related: https://github.com/Kozea/WeasyPrint/issues/1579#issuecomment-1051689324 */
        size: 210mm 297mm;
    }

Would you have CSS/display/options tips for migrating?

Hi!
WeasyPrintBundle uses PhpWeasyPrint as php library which uses the Command-line API available from WeasyPrint.
In WeasyPrint documentation is stated that

WeasyPrint does not provide support for adjusting page size or document margins via command-line flags. This is best accomplished with the CSS @page at-rule

As you already found out adding @page CSS rule is the only option available.
For orientation option you can add it after size:
@page {
	size: A4 landscape;
}

For dpi option you can experiment with image-resolution (I've never tried it):
img { image-resolution: 300dpi }

I suggest to prepare a dedicated twig template and css for pdf generation, and don't recycle twig/html created for browser use.

Hello @endelwar , thank you for those tips which I have included in our current project; both rules you have stated do work OK.
For people looking into migrating away from wkhtmltopdf / knpsnappybundle, here is a related discussion.


Linear edit variants

Linear reference that backs out graph reference support while maintain a degree of syntactic forwards compatibility

Merging into the properly-prefixed topic branch, as per @benedictpaten 's new rules. This being a topic branch, anything we don't like we can easily change later.


Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3
Also their maintainer says they probably won't ever use it: http://stackoverflow.com/questions/24844901/bowers-bower-json-file-version-property

Good work! Thank you!


Deadlock fixes

We have packaged Orchid as an I2P plugin, enabling I2P users to easily use Orchid as an outproxy for their non-I2P web connections. This is the first patch we are pushing upstream for bugs we have found. The patch is in the current released version of the Orchid plugin.
Ref: https://trac.i2p2.de/ticket/1207

The deadlock fixes from bitcoinj have been merged. This can be closed now - we haven't seen any deadlocks in Orchid for a long time after these fixes.


[W6.4f][T11-B3] David Dalmaso

@daviddalmaso Accepting this PR with minimal review and I found no important issue.


redhat.sap_install.sap_general_preconfigure : Verify that variable sap_domain is set issue

When running following playbook on IBM Cloud RHEL for SAP 8.4
---
- name: Apply SAP Ansible roles to localhost
  gather_facts: true
  hosts: localhost
  become: true
  become_user: root
  roles:
    - redhat.sap_install.sap_general_preconfigure
    - redhat.sap_install.sap_hana_preconfigure
EOF

Faced with following error message
TASK [redhat.sap_install.sap_general_preconfigure : Verify that variable sap_domain is set] *****
fatal: [localhost]: FAILED! => {
    "assertion": "not( (sap_domain is undefined) or (sap_domain is none) or (sap_domain | trim == '') )",
    "changed": false,
    "evaluated_to": false,
    "msg": "Variable 'sap_domain' is undefined or empty. Please define it in defaults/main.yml or via --extra-vars!"
}

Domain is not configured for the host.
[root@hana ~]# hostname -A
hana
[root@hana ~]# hostname -d
[root@hana ~]#

HI Kirill,
this works as designed. The blank system is configured without a proper domain name.
Hence ansible_domain which is the default value is empty and the system cannot be properly configured.
Please add the variable sap_domain to your playbook and set it to the domain you want and the system will be configured accordingly
BR
Markus


The editor is not scrolling when creating a hidden new line

Like the tittle said, the editor (I don't know which class is the html editor is) doesn't get scrolled when user create new line on the bottom of the visible area. The caret just looks like goes below the visible area without any scrolling to make the new position of the caret visible. For better picture, see the attached screenshot.

I got same issue after add image and start to write text very near by image. Can you give proper solution?

@kurotsukikaitou I believe that this has been fixed because I replicated your screenshot and had no issues with it, can you confirm if it has been fixed or not please?
@parthpatel1105 please can you also confirm if your issue is still present or not when using the latest version of the source?

I am going to close this issue for now, but if anyone still has issues with this then comment and I will re-open the issue. @parthpatel1105 @kurotsukikaitou


RetryPolicy for output messages?

What is the default RetryPolicy for messages send by the OpcPublisher used as IotEdge module ?
Can the RetryPolicy be changed (e.g. using commandline parameters) ?

it does use in any case (Edge and non Edge):
ExponentialBackoff exponentialRetryPolicy = new ExponentialBackoff(int.MaxValue, TimeSpan.FromMilliseconds(2), TimeSpan.FromMilliseconds(1024), TimeSpan.FromMilliseconds(3));
makes sense?

@hansgschossmann How long will the publisher retry to send messages, i.e. what is the value of DefaultOperationTimeoutInMilliseconds ?

I have not tried this, but the definition of ExponentialBackoff is:
public ExponentialBackoff(int retryCount, TimeSpan minBackoff, TimeSpan maxBackoff, TimeSpan deltaBackoff);
It will try int.MaxValue times using the given backoff parameters.

@hansgschossmann If DefaultOperationTimeoutInMilliseconds is not set within OpcPublisher, the default should be 4 minutes.

The retry mechanism stops after DefaultOperationTimeoutInMilliseconds, which is currently set at 4 minutes.

(source)
Reading the linked source, it is unclear to me whether the 4 minute limit is always applicable or only for "throttling errors".

i see. i will tag this issue as feature request. adding a command line option to configure it should to the job.

OK - thank you.


Delayed actions processed in wrong order

When actions are delayed for policy concurrency (and concurrency.attr), they appear to be retried in newest to oldest order, rather than oldest to newest.  The file attached is a trimmed down actionrunner log showing delayed actions and their subsequent dispatch.  When multiple actions are delayed, they appear to be dispatched in the opposite order intended.
2600.txt
st2actions/policy/concurrency.py:88 and concurrency_by_attr.py:115 both include order_by['start_timestamp'], but does not indicate ascending or descending.

Thanks for the report.
We don't officially say that we process delayed executions in the FIFO order, but I agree with you that LIFO behavior is confusing and making it FIFO would indeed be better and make more sense.
As far as the actual code / implementation goes - I believe the default mongoengine order (unless explicitly specified) is to sort in ascending order so there must be something else going on and I will dig into the code.

I quickly looked at the code and the concurrency stuff looks correct - we don't explicitly specify ASC order, but that's the default behavior (so doing +start_timestamp is optional).
There might be an issue with the way requested and scheduled are processed, but looking at the code nothing stands out. By default RabbitMQ messages are processes in FIFO order, but there are many edge-cases (in a distributed system) where this doesn't always hold true - if there are multiple consumers (we run multiple action runners by default), if for some reason message is re-queued (timeout, ...), etc.
Do you happen to have a simple workflow / action example which I can use to try to reproduce this issue?
/cc @m4dcoder

Thanks, Kami.  I'll try to see if we can reproduce this issue.  Also, our system is defaulting to a single action runner (I think four cores or less yields a single one) - any known concerns?  Would we be better/safer with two?

No, it should be fine with a single action runner - if anything it should be better with regards to the race conditions (but there shouldn't be any, more runners simply means more actions will be executed in parallel).
And yeah, if you can come up with a simple workflow with reproduces a problem, please gist it here and I will have a look.

@Kami, nope, will have to define one to test this.

I'm working on a simple set of repro steps for this and encountered another issue. I can't disable a policy!  I set 'enabled' to false and reload and the policy is still enforced.  I remove the file, st2ctl stop/start, reboot, and the policy is still being applied!  I feel a little silly asking, but is there extra special policy persistence somewhere?

@bri365 It could be a bug - I will look into it.

@bri365 Yeah - it looks like a bug in the code.
I'm working on a fix as we speak.

@Kami @m4dcoder after developing and verifying repro steps for my issue, I have isolated why items appeared "out of order" to me and in the process found another one or two issues, which I will file separately.
In this case, my clean-up script to delete stuck actions included iterating through the list of 'scheduled', 'delayed', and 'running' actions and canceling them.  The iteration was based on 'st2 execution list -l --status scheduled -n 1' which delivers the most recent action in the requested state, rather than the oldest action of the given state.
I think it is valuable to get the oldest action/workflow in a given state, so either reversing the order of returned items or offering a sort order would be very helpful.

Closing this as not an issue and opening a feature request for execution list sort order.


Race condition in IncrementalIndex's facts

In OnheapIncrementalIndex::addToFacts(...), when we get a new fact, we will first add the mapping from key to fact's index, then we do aggregate. It will cause query saw some unaggregated metrics with initial value, and sometimes may cause some weird situations. Like if we use LongMax for build but use LongSum for query, then the result may add LongMax's initial value which is LONG.MIN_VALUE.
BTW, do we need to deal with this:
      final Integer prev = facts.putIfAbsent(key, rowIndex);
      if (null == prev) {
        numEntries.incrementAndGet();
      } else {
        // We lost a race
        aggs = concurrentGet(prev);
        // Free up the misfire
        concurrentRemove(rowIndex);
        // This is expected to occur ~80% of the time in the worst scenarios
      }

I don't find any multi-thread adds for IncremetalIndex.

Multi-threaded add in IncrementalIndex exists because it is also used for groupBy, which does multi-threaded merging of partial results. In #2987 I'm suggesting no longer using IncrementalIndex for groupBy, which could mean IncrementalIndex might not have to support multi-threaded adds anymore.
Btw, out of curiosity why would you use longMax for building but longSum for querying?

@gianm It's a hack solution for one of our realtime cases. We use druid to consume a streaming job's output to calculate some metrics like PV which is obviously sum(each_pv). But it's difficult to let the streaming job output each record exactly once because failover always exists. So we add a primary key to the event and make it dimension. Now we can use LongMax to dedup the duplicated events, and use LongSum to query.


Bump to v0.3.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.51%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
1681

Relevant Lines:
1878

💛  - Coveralls


Display mode doesn't work for MathML output

Describe the bug:
Display mode does not work for MathML output (it does for HTML output).
To Reproduce:
Render any expression, using the options {displayMode: true, output: 'mathml'}.
See JSFiddle.
Expected behavior:
Expression renders in display mode, i.e. display-style math centred on its own line.
Actual behavior:
Expression appears to render in inline mode.
Screenshot:

Environment:

KaTeX Version: 0.11.1
Browser: any browser which supports MathML

@yawnoc Good catch! The <math> element needs to have attribute display="block".
This should be a pretty easy fix. I can probably turn in a PR later today.


⚠ Bofrost.at has degraded performance

In e9c77c4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1231 ms

Resolved: Bofrost.at performance has improved in 65ce95d after 15 minutes.


My style is out of order

When I press Ctrl + H to open the history:
---------
I can only restore sideberry with one click!
There are also problems with the URL bar

Go to Extensions & Themes, enable light theme then your url bar will display normally.

The sidebar is shared between Sidebery, the History sidebar, Bookmarks sidebar, Synced Tabs sidebar, etc. If you want to leave the Sidebery sidebar visible and bring up the Manage History window (instead of the History sidebar) you can press Ctrl+Shift+H, and I suggest add history to toolbar for quick access


Error when using the pvlib.forecast.ForecastModel.get_processed_data

pvlib usage questions can be asked on Stack Overflow and tagged with the pvlib tag.
The pvlib-python google group is used for discussing various topics of interest to the pvlib-python community. We also make new version announcements on the google group.
Hi, I have been using PVLIB to model a solar array in Hawaii. I just updated my computer to the new catalina software. I reinstalled pvlib on my system and now when I run my code to get the weather data the following error occurs:
TypeError: <class 'cftime._cftime.DatetimeGregorian'> is not convertible to datetime
I have been trying to figure out why this is happening. Below is my code. Thank you for any help!!
`# built-in python modules
import datetime
import inspect
import os
import pytz
scientific python add-ons
import numpy as np
import pandas as pd
plotting
first line makes the plots appear in the notebook
%matplotlib inline
import matplotlib.pyplot as plt
import matplotlib as mpl
#import the pvlib library
from pvlib import solarposition,irradiance,atmosphere,pvsystem
from pvlib.forecast import GFS
from pvlib.modelchain import ModelChain
pd.set_option('display.max_rows', 500)
latitude, longitude, tz = 21.300268, -157.818044, 'Pacific/Honolulu'
# specify time range.
start2 = pd.Timestamp(datetime.date.today(), tz=tz)
pacific = pytz.timezone('Etc/GMT+10')
# print(pacific)
# datetime.datetime(year, month, day, hour, minute, second, microsecond, tzinfo)
start2 = pd.Timestamp(datetime.datetime(2020, 2, 14, 12, 0, 0, 0, pacific))
# print(start)
# print(start2)
# print(datetime.date.today())
end = start2 + pd.Timedelta(days=1.5)
pacific = pytz.timezone('Etc/GMT+10')
# use python datetime and pytz correctly
start2 = pd.Timestamp(pacific.localize(datetime.datetime(2020, 2, 14, 12, 0, 0, 0)))
naive python datetime, let pandas/pytz handle tz
start2 = pd.Timestamp(datetime.datetime(2020, 2, 17, 12, 0, 0, 0), tz=pacific)
# skip pytz and just use pandas
pacificstr = 'Etc/GMT+10'
start2 = pd.Timestamp(2020, 2, 14, 12, 0, 0, 0, tz=pacificstr)
end = start2 + pd.Timedelta(days=1.5)
from datetime import datetime
start2 = datetime.now()
end = start2 + pd.Timedelta(days=1.5)
print(type(start2))
print(type(end))
Define forecast model
fm = GFS()
get data from location specified above
forecast_data = fm.get_processed_data(latitude, longitude, start2, end)
print(forecast_data)
Full stack trace of error
TypeError                                 Traceback (most recent call last)
 in
3
4 # get data from location specified above
----> 5 forecast_data = fm.get_processed_data(latitude, longitude, start2, end)
6 # print(forecast_data)
~/opt/anaconda3/lib/python3.7/site-packages/pvlib/forecast.py in get_processed_data(self, *args, **kwargs)
306             Processed forecast data
307         """
--> 308         return self.process_data(self.get_data(*args, **kwargs), **kwargs)
309
310     def rename(self, data, variables=None):
~/opt/anaconda3/lib/python3.7/site-packages/pvlib/forecast.py in get_data(self, latitude, longitude, start, end, vert_level, query_variables, close_netcdf_data, **kwargs)
264         # higher dimensional data for more advanced applications
265         self.data = self._netcdf2pandas(self.netcdf_data, self.query_variables,
--> 266                                         self.start, self.end)
267
268         if close_netcdf_data:
~/opt/anaconda3/lib/python3.7/site-packages/pvlib/forecast.py in _netcdf2pandas(self, netcdf_data, query_variables, start, end)
349         try:
350             time_var = 'time'
--> 351             self.set_time(netcdf_data.variables[time_var])
352         except KeyError:
353             # which model does this dumb thing?
~/opt/anaconda3/lib/python3.7/site-packages/pvlib/forecast.py in set_time(self, time)
391         '''
392         times = num2date(time[:].squeeze(), time.units)
--> 393         self.time = pd.DatetimeIndex(pd.Series(times), tz=self.location.tz)
394
395     def cloud_cover_to_ghi_linear(self, cloud_cover, ghi_clear, offset=35,
~/opt/anaconda3/lib/python3.7/site-packages/pandas/core/indexes/datetimes.py in new(cls, data, freq, start, end, periods, tz, normalize, closed, ambiguous, dayfirst, yearfirst, dtype, copy, name, verify_integrity)
332             yearfirst=yearfirst,
333             ambiguous=ambiguous,
--> 334             int_as_wall_time=True,
335         )
336
~/opt/anaconda3/lib/python3.7/site-packages/pandas/core/arrays/datetimes.py in _from_sequence(cls, data, dtype, copy, tz, freq, dayfirst, yearfirst, ambiguous, int_as_wall_time)
444             yearfirst=yearfirst,
445             ambiguous=ambiguous,
--> 446             int_as_wall_time=int_as_wall_time,
447         )
448
~/opt/anaconda3/lib/python3.7/site-packages/pandas/core/arrays/datetimes.py in sequence_to_dt64ns(data, dtype, copy, tz, dayfirst, yearfirst, ambiguous, int_as_wall_time)
1864             #  or M8[ns] to denote wall times
1865             data, inferred_tz = objects_to_datetime64ns(
-> 1866                 data, dayfirst=dayfirst, yearfirst=yearfirst
1867             )
1868             tz = maybe_infer_tz(tz, inferred_tz)
~/opt/anaconda3/lib/python3.7/site-packages/pandas/core/arrays/datetimes.py in objects_to_datetime64ns(data, dayfirst, yearfirst, utc, errors, require_iso8601, allow_object)
1973             dayfirst=dayfirst,
1974             yearfirst=yearfirst,
-> 1975             require_iso8601=require_iso8601,
1976         )
1977     except ValueError as e:
pandas/_libs/tslib.pyx in pandas._libs.tslib.array_to_datetime()
pandas/_libs/tslib.pyx in pandas._libs.tslib.array_to_datetime()
pandas/_libs/tslib.pyx in pandas._libs.tslib.array_to_datetime_object()
pandas/_libs/tslib.pyx in pandas._libs.tslib.array_to_datetime()
TypeError: <class 'cftime._cftime.DatetimeGregorian'> is not convertible to datetime`

Very hard to tell with all the repeated lines. But it's clear that it's related to the datetimes and timezone localization.

start2 = pd.Timestamp(2020, 2, 14, 12, 0, 0, 0, tz=pacificstr)

This line will fail with a different error, which tells me that I can't reproduce the error you see. Use named argument names, you are passing positional values to the wrong arguments.

Hi Cliff,
Thanks for the help and suggestions to fix my problem. I tried to run the
example code from
https://pvlib-python.readthedocs.io/en/stable/forecasts.html. I still get
the error "TypeError: <class 'cftime._cftime.DatetimeGregorian'> is not
convertible to datetime", the code I used is below and I attached a jupyter
notebook of the example. Any help in solving this issue would be greatly
appreciated!!
import pandas as pd
import matplotlib.pyplot as plt
import datetime
import pvlib forecast models
from pvlib.forecast import GFS, NAM, NDFD, HRRR, RAP
specify location (Tucson, AZ)
latitude, longitude, tz = 32.2, -110.9, 'US/Arizona'
specify time range.
start = pd.Timestamp(datetime.date.today(), tz=tz)
end = start + pd.Timedelta(days=7)
model = GFS()
retrieve data. returns pandas.DataFrame object
raw_data = model.get_data(latitude, longitude, start, end)
print(raw_data.head())
On Mon, Feb 17, 2020 at 10:01 AM Cliff Hansen<EMAIL_ADDRESS>wrote:

Closed #895 https://github.com/pvlib/pvlib-python/issues/895.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pvlib/pvlib-python/issues/895?email_source=notifications&email_token=AOSUNZTI2KFXXGWEDNHZENLRDLUH7A5CNFSM4KWXMVGKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWV6TJDI#event-3044881549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOSUNZWLT6G4RWHFYDA4ZSTRDLUH7ANCNFSM4KWXMVGA
.

I can't reproduce that error, having firewall issues. I'm guessing that there's a clash among python packages. Which versions of pandas, numpy and datetime are you using?

@dankestship I only get this error when using cftime==1.1.0 (released Feb 13).  Downgrading to the prior release with pip install cftime==<IP_ADDRESS> fixes the issue on my computer.
@wholmgren Looks like this was the relevant change: https://github.com/Unidata/cftime/issues/136 -- possible fix is to specify only_use_cftime_datetimes=False here: https://github.com/pvlib/pvlib-python/blob/master/pvlib/forecast.py#L409

Thank you both for all your help!! Downgrading to a prior release fixed the
issue and the example code now runs without error. Thank you again!
On Tue, Feb 18, 2020 at 6:23 AM Kevin Anderson<EMAIL_ADDRESS>wrote:

@dankestship https://github.com/dankestship I only get this error when
using cftime==1.1.0 (released Feb 13). Downgrading to the prior release
with pip install cftime==<IP_ADDRESS> fixes the issue on my computer.
@wholmgren https://github.com/wholmgren Looks like this was the
relevant change: Unidata/cftime#136
https://github.com/Unidata/cftime/issues/136 -- possible fix is to
specify only_use_cftime_datetimes=False here:
https://github.com/pvlib/pvlib-python/blob/master/pvlib/forecast.py#L409
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pvlib/pvlib-python/issues/895?email_source=notifications&email_token=AOSUNZTV63LGGOSHT2XQJQLRDQDR3A5CNFSM4KWXMVGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMCT7SY#issuecomment-587546571,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOSUNZVTVOI5I2JLVP4C4STRDQDR3ANCNFSM4KWXMVGA
.


Vaccine data global - J&J vaccine

Hello,
First, thanks a lot for compiling this amazing data!
A new vaccine is starting to get approval in various countries, the J&J one.
It requires only 1 dose to be administered.
I just wanted to know how it will be counted in the Global vaccine data here:

Will people go directly to fully vaccinated?
Will they be counted in both?

Regarding the US state timeline, here, will there be a new column for the J&J vaccine?
Thanks a lot for helping me understand that!
Best,
Louis

Hello,
I see that this has been asked in both Issue #351 by @PGuimarais and here.
I know the type of vaccine per US state, are we going to do the same for different countries?
All the more interested in this as J&J will probably be allowed in Europe today ;)
Many thanks!


User is shown confusing technical error message when they refuse/can't do MFA (e.g., in eduID)

When an IdP is configured (in manage) to require a specific ACCR fot a service, and the MFA login fails for some reason, Engineblock shows this generic error message to the user:

While technically correct, it would be nice if we could make this specific error a bit more readable for regular users.  For me it was not entirely clear on first glance that this was an MFA error.  Regular users probably have no idea what is happening here.
To reproduce:

connect an SP to eduID and configure Refeds MFA for this connection
log into the service but in eduID refuse to install the app or login with a token
EB shows this error.

We have this error screen available in Engineblock. This is shown when said setting is configured but the IdP does not report back that the ACCR has been used in authentication. This is what the majority of our IdP's implement:

I understand your request as that when receiving NoAuthnContext from the IdP, it should also display this screen instead of the generic "SAML Error response received" message above, correct?

If this is indeed specific to EduID, I agree that it would be nicer to fix it there (i.e., make eduID shown an error instead of redirecting the user with a SAML errror message).


Need help with my index file

Can you help me find a more efficient way to write this code?
https://github.com/fhdsl/DaSEH/blob/c63f7310da322166a819a65aa29461dba0498e9f/index.Rmd#L50

oh lol I think this was from the class as a demo haha- I was confused :P

HAHA :)


Enable checkpoint_sync by default

Motivation

Before a Zebra stable release, we should enable post-Canopy checkpoints so that Zebra synchronizes the chain more quickly.
This is part of #2368.
Solution

Make checkpoint_sync true by default
Update the documentation to say that setting it to false is useful for debugging

Review

Reviewer Checklist

[x] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work

Finish the rest of #2368 by increasing the checkpoint height.

We're currently merging CI fixes in the high priority queue, so I've set this PR to medium priority.


Code Missing :-(

Ciao Angelalp,
we are starting to implement the same features you mentioned in the watermarking extension pack :-)
To avoid reinventing the wheel, could you please share the code again?
It doesn't matter if it's a bit old; we can adjust it to work with the latest Innovator release and share back the updates with you, of course!
Thank you very much!
Matteo

Hi Matteo,
I haven´t seen you were writing this question. I right now cannot use the PDF Watermark feature by myself anymore. My code from back than is pretty wild. Which feature are you looking for?


Added "Running Add-on tests with code coverage"

https://iqs-jira.zeiss.org/browse/AD-542

[ ] Also, the referenced add-on from "AddOnExamples" repo should be uploaded before merging this documentation.


Replace os.path.join(ROOT, ...) with call to path()

A couple lines were still using os.path.join to join ROOT and a path

Thanks


DB1000N | Add app. auto-restart upon successful update

Over-the-air updates
Lots of maintainers run their needles on a bare metal machines.
As long as this project is so frequently updated, it might be
a good idea to let them update it without the hassle.

[V] Enabled automatic time-based version check
[V] Enabled application self-restart after it downloaded the update

Description
Support for the application self-update by downloading
the latest release from the official repository.
Stay strong, be the first in line!

The version should be embedded in the binary during the build, see the build
target in the Makefile.
Usage
Available flags
  -enable-self-update
        Enable the application automatic updates on the startup
  -restart-on-update
        Allows application to restart upon the successful update (ignored if auto-update is disabled) (default true)
  -self-update-check-frequency duration
        How often to run auto-update checks (default 24h0m0s)
  -skip-update-check-on-start
        Allows to skip the update check at the startup (usually set automatically by the previous version) (default false)

The default behavior if the self-update enabled:

Check for the update
If update is available - download it

If auto-restart is enabled

Notify the user that a newer version is available
Fork-Exec a new process (will have a different PID), add a flag to skip the version check upon startup
Stop the current process

If auto-restart is disabled - notify user that manual restart is required

If update is NOT available - schedule the next check

Examples
To update your needle, start it with a flag -enable-self-update
./db1000n -enable-self-update

Advanced options

Start the needle with the self-update & self-restart

$ ./db1000n -enable-self-update
0000/00/00 00:00:00 main.go:82: DB1000n [Version: v0.6.4][PID=75259]
0000/00/00 00:00:00 main.go:166: Running a check for a newer version...
0000/00/00 00:00:00 main.go:176: Newer version of the application is found [0.7.0]
0000/00/00 00:00:00 main.go:177: What's new:
* Added some great improvements
* Added some spectacular bugs
0000/00/00 00:00:00 main.go:180: Auto restart is enabled, restarting the application to run a new version
0000/00/00 00:00:00 restart.go:45: new process has been started successfully [old_pid=75259,new_pid=75262]

# NOTE: Process 75259 exited, Process 75262 has started with a flag to skip version check on the startup

0000/00/00 00:00:00 main.go:82: DB1000n [Version: v0.7.0][PID=75262]
0000/00/00 00:00:00 main.go:155: Version update on startup is skipped, next update check is scheduled in 24h0m0s

Start the needle with the self-update but do not restart the process upon update (systemd friendly)

$ ./db1000n -enable-self-update -self-update-check-frequency=5m -restart-on-update=false
0000/00/00 00:00:00 main.go:82: DB1000n [Version: v0.6.4][PID=75320]
0000/00/00 00:00:00 main.go:166: Running a check for a newer version...
0000/00/00 00:00:00 main.go:176: Newer version of the application is found [0.7.0]
0000/00/00 00:00:00 main.go:177: What's new:
* Added some great improvements
* Added some spectacular bugs
0000/00/00 00:00:00 main.go:191: Auto restart is disabled, restart the application manually to apply changes!

References

https://github.com/Scalingo/go-graceful-restart-example
https://github.com/rcrowley/goagain
https://grisha.org/blog/2014/06/03/graceful-restart-in-golang

@Arriven, please, add the version embedding to the binary distributed thru release downloads. The example on how to add the version you can find in the Makefile.
Btw, I can't test if the restart works fine for the Windows machines, I don't have one.


fix: Color not applied to diff

Hello!!
I always use mdbook-catppuccin! 🐈⬛
After updating to v1.0.0, I noticed that the color theme is not applied correctly to the diff.
All we are doing in this PR is reverting the parameters related to diffs back to what they were before v1.0.0, but I think this will fix this issue.
Could you please confirm this?
Thanks!! ☕

Ah, I see. I'm beginning to understand!
Is it my understanding that this can be solved by simply rewriting pallete/package.json?
I'm not sure if my understanding is correct, as I can't get the build to work in my local environment...
><EMAIL_ADDRESS>build
> sass -I node_modules --no-charset --no-source-map catppuccin.scss:../src/bin/assets/catppuccin.css catppuccin-admonish.scss:../src/bin/assets/catppuccin-admonish.css

Error: Can't find stylesheet to import.
  ╷
1 │ @use "@catppuccin/palette/scss/catppuccin" as catppuccin;
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  catppuccin.scss 1:1  root stylesheet

Error: Can't find stylesheet to import.
  ╷
3 │ @use "@catppuccin/palette/scss/catppuccin" as catppuccin;
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  catppuccin-admonish.scss 3:1  root stylesheet

Sorry, this was because I did not npm install.
Also, looking closer, maybe the package is supposed to be updated on release.
Sorry for the strange English!
You can also dismiss this PR if it gets in the way!

Hey there :wave:, thanks for the pull request!
The changes with the dependency bump look good, could you just help me understand why https://github.com/catppuccin/mdBook/commit/051a7ff0a01f36e43750417f659328bc2f81e31d was reverted in 1d10d5b (#67)? I specified the files because using . was copying over the node_modules directory into the source directory which wasn't great when it came time to cargo publish.

Sorry for repeating myself...
In the revert, I thought I had only undone the operations I had done, but I may have been wrong.
I'm getting kind of confused....
This is a very selfish question, but what should I do in this case...?

I have tried many things,
The cappuccin.css seems to match the one generated via
npm run build and the current one (which I manually rewrote).
Now all I have to do is fix the mistake in package.json?
...Please squash the messy commit history 😖

Thanks for the kind words!
I was actually in a hurry for nothing as I was doing it in the time before bed....
It was a good experience 😅
Thanks again 🩷


xfail pyarrow tests failing due to upstream bump to 1.0

[x] Tests added / passed
[x] Passes black dask / flake8 dask

temporary xfail to handle changes upstream

As @rjzamora pointed out to me offline, PR ( https://github.com/dask/dask/pull/6346 ) should fix pyarrow 1.0.0 compatibility. Please correct me if I got this wrong Rick 🙂

the 3.8 failure on Windows is that spurious ([nan]) array bug.
@jakirkham -- I'm very happy for a proper fix and happy to shelve this if #6346 is close

I don't have strong feelings here. Would defer to Rick 🙂
My guess is we could still go ahead with this and just revert it in Rick's PR (though please feel free to override me Rick 🙂). Just wanted to relay that a pyarrow fix is in the works 😉

@jakirkham - 6346 is ready to mnerge from my own perspective, but I have no problem at all if this PR gets in first

Closing, since #6346 is in.


BaseNDArray get returning incorrect shape and result order on dl4j test

Issue outlined in Deeplearning4j repo under: testSubSampleLayerAvgBackprop issue in SubsamplingLayerTests #593

This is fixed . Make sure your nd4j is updated.
https://github.com/deeplearning4j/deeplearning4j/commit/a07cc139751cbbcc696cd78a462763a80c61dc66