Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 855 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 13 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 240k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
269,875 | 8,444,061,884 | IssuesEvent | 2018-10-18 17:19:24 | poanetwork/metamask-extension | https://api.github.com/repos/poanetwork/metamask-extension | closed | (Fix) Update integration tests | high priority ready for release | Relates to https://github.com/poanetwork/metamask-extension/pull/135
Integration tests don't work after eliminating of `betaUI` flag from configuration.
They should be updated for the current version of extension in `search-tokens` branch
Integration tests launch with `npm run test:integration`.
PR should be made to [search-tokens](https://github.com/poanetwork/metamask-extension/tree/search-tokens) branch | 1.0 | (Fix) Update integration tests - Relates to https://github.com/poanetwork/metamask-extension/pull/135
Integration tests don't work after eliminating of `betaUI` flag from configuration.
They should be updated for the current version of extension in `search-tokens` branch
Integration tests launch with `npm run test:integration`.
PR should be made to [search-tokens](https://github.com/poanetwork/metamask-extension/tree/search-tokens) branch | priority | fix update integration tests relates to integration tests don t work after eliminating of betaui flag from configuration they should be updated for the current version of extension in search tokens branch integration tests launch with npm run test integration pr should be made to branch | 1 |
115,759 | 4,681,986,091 | IssuesEvent | 2016-10-09 02:19:38 | CS2103AUG2016-W13-C3/main | https://api.github.com/repos/CS2103AUG2016-W13-C3/main | closed | Import user stories into `Issues` | priority.high | Quoting T8A1:
>
- Record each of the user stories you plan to deliver as an issue in the issue tracker.
e.g. Title: As a user I can add a deadline
Description: ... so that I can keep track of my deadlines
- Assign the type.* and priority.* labels to those issues. | 1.0 | Import user stories into `Issues` - Quoting T8A1:
>
- Record each of the user stories you plan to deliver as an issue in the issue tracker.
e.g. Title: As a user I can add a deadline
Description: ... so that I can keep track of my deadlines
- Assign the type.* and priority.* labels to those issues. | priority | import user stories into issues quoting record each of the user stories you plan to deliver as an issue in the issue tracker e g title as a user i can add a deadline description so that i can keep track of my deadlines assign the type and priority labels to those issues | 1 |
600,821 | 18,359,005,251 | IssuesEvent | 2021-10-08 23:51:16 | pycaret/pycaret | https://api.github.com/repos/pycaret/pycaret | closed | [Time Series] Limit models to only those that have a prediction interval | enhancement time_series priority_high | **Describe the solution you'd like**
Many applications need to have a prediction interval available. In compare models, we currently show a mix of models - some that have PI and some that don't. Provide an option in setup (overridden in compare_models) to use only models that have a PI.
| 1.0 | [Time Series] Limit models to only those that have a prediction interval - **Describe the solution you'd like**
Many applications need to have a prediction interval available. In compare models, we currently show a mix of models - some that have PI and some that don't. Provide an option in setup (overridden in compare_models) to use only models that have a PI.
| priority | limit models to only those that have a prediction interval describe the solution you d like many applications need to have a prediction interval available in compare models we currently show a mix of models some that have pi and some that don t provide an option in setup overridden in compare models to use only models that have a pi | 1 |
43,179 | 2,885,926,112 | IssuesEvent | 2015-06-12 02:47:50 | gama-platform/gama | https://api.github.com/repos/gama-platform/gama | closed | Batch not working | > Bug Concerns Batch Priority High | ```
Simulation crashes when using batch, providing the following error log:
java.lang.NullPointerException
at msi.gama.runtime.exceptions.GamaRuntimeException.create(GamaRuntimeException.java:53)
at msi.gama.runtime.AbstractScope.step(AbstractScope.java:442)
at msi.gama.runtime.FrontEndScheduler.step(FrontEndScheduler.java:83)
at msi.gama.runtime.FrontEndScheduler.run(FrontEndScheduler.java:129)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at msi.gama.kernel.experiment.BatchAgent.launchSimulationsWithSolution(BatchAgent.java:152)
at msi.gama.kernel.batch.ExhaustiveSearch.testSolutions(ExhaustiveSearch.java:79)
at msi.gama.kernel.batch.ExhaustiveSearch.testSolutions(ExhaustiveSearch.java:85)
at msi.gama.kernel.batch.ExhaustiveSearch.findBestSolution(ExhaustiveSearch.java:41)
at msi.gama.kernel.batch.ParamSpaceExploAlgorithm.run(ParamSpaceExploAlgorithm.java:91)
at msi.gama.kernel.experiment.BatchAgent.step(BatchAgent.java:132)
at msi.gama.runtime.AbstractScope.step(AbstractScope.java:440)
```
Original issue reported on code.google.com by `tri.nguyen-huu@ird.fr` on 2014-04-17 06:36:24
<hr>
* *Attachment: [essai_batch.gaml](https://storage.googleapis.com/google-code-attachments/gama-platform/issue-996/comment-0/essai_batch.gaml)* | 1.0 | Batch not working - ```
Simulation crashes when using batch, providing the following error log:
java.lang.NullPointerException
at msi.gama.runtime.exceptions.GamaRuntimeException.create(GamaRuntimeException.java:53)
at msi.gama.runtime.AbstractScope.step(AbstractScope.java:442)
at msi.gama.runtime.FrontEndScheduler.step(FrontEndScheduler.java:83)
at msi.gama.runtime.FrontEndScheduler.run(FrontEndScheduler.java:129)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
at msi.gama.kernel.experiment.BatchAgent.launchSimulationsWithSolution(BatchAgent.java:152)
at msi.gama.kernel.batch.ExhaustiveSearch.testSolutions(ExhaustiveSearch.java:79)
at msi.gama.kernel.batch.ExhaustiveSearch.testSolutions(ExhaustiveSearch.java:85)
at msi.gama.kernel.batch.ExhaustiveSearch.findBestSolution(ExhaustiveSearch.java:41)
at msi.gama.kernel.batch.ParamSpaceExploAlgorithm.run(ParamSpaceExploAlgorithm.java:91)
at msi.gama.kernel.experiment.BatchAgent.step(BatchAgent.java:132)
at msi.gama.runtime.AbstractScope.step(AbstractScope.java:440)
```
Original issue reported on code.google.com by `tri.nguyen-huu@ird.fr` on 2014-04-17 06:36:24
<hr>
* *Attachment: [essai_batch.gaml](https://storage.googleapis.com/google-code-attachments/gama-platform/issue-996/comment-0/essai_batch.gaml)* | priority | batch not working simulation crashes when using batch providing the following error log java lang nullpointerexception at msi gama runtime exceptions gamaruntimeexception create gamaruntimeexception java at msi gama runtime abstractscope step abstractscope java at msi gama runtime frontendscheduler step frontendscheduler java at msi gama runtime frontendscheduler run frontendscheduler java at java lang thread run unknown source caused by java lang nullpointerexception at msi gama kernel experiment batchagent launchsimulationswithsolution batchagent java at msi gama kernel batch exhaustivesearch testsolutions exhaustivesearch java at msi gama kernel batch exhaustivesearch testsolutions exhaustivesearch java at msi gama kernel batch exhaustivesearch findbestsolution exhaustivesearch java at msi gama kernel batch paramspaceexploalgorithm run paramspaceexploalgorithm java at msi gama kernel experiment batchagent step batchagent java at msi gama runtime abstractscope step abstractscope java original issue reported on code google com by tri nguyen huu ird fr on attachment | 1 |
451,152 | 13,025,551,056 | IssuesEvent | 2020-07-27 13:42:59 | kubesphere/kubesphere | https://api.github.com/repos/kubesphere/kubesphere | closed | workspace admin can't add a custom app repo because of access problem | area/iam kind/bug kind/need-to-verify priority/high | ## English only!
**注意！GitHub Issue 仅支持英文，中文 Issue 请在 [论坛](https://kubesphere.com.cn/forum/) 提交。**
**General remarks**
> Please delete this section including header before submitting
>
> This form is to report bugs. For general usage questions refer to our Slack channel
> [KubeSphere-users](https://join.slack.com/t/kubesphere/shared_invite/enQtNTE3MDIxNzUxNzQ0LTdkNTc3OTdmNzdiODViZjViNTU5ZDY3M2I2MzY4MTI4OGZlOTJmMDg5ZTFiMDAwYzNlZDY5NjA0NzZlNDU5NmY)
**Describe the Bug**
workspace admin can't add a custom app repo because of access problem
**Versions Used**
KubeSphere: 3.0 alpha 2
**How To Reproduce**
Steps to reproduce the behavior:
1. Create a user with 'Platform Regular' role
2. Create a workspace and assign this user as the workspace admin
3. login as this user and access above workspace
4. Add a custom app repo, and got an access denied msg.
<img width="1323" alt="Xnip2020-07-26_18-26-48" src="https://user-images.githubusercontent.com/28883416/88476824-23ab4300-cf6e-11ea-98a2-7390ea37e51e.png">
<img width="1614" alt="Xnip2020-07-26_18-27-29" src="https://user-images.githubusercontent.com/28883416/88476842-2ad25100-cf6e-11ea-90bb-74ec942f2680.png">
| 1.0 | workspace admin can't add a custom app repo because of access problem - ## English only!
**注意！GitHub Issue 仅支持英文，中文 Issue 请在 [论坛](https://kubesphere.com.cn/forum/) 提交。**
**General remarks**
> Please delete this section including header before submitting
>
> This form is to report bugs. For general usage questions refer to our Slack channel
> [KubeSphere-users](https://join.slack.com/t/kubesphere/shared_invite/enQtNTE3MDIxNzUxNzQ0LTdkNTc3OTdmNzdiODViZjViNTU5ZDY3M2I2MzY4MTI4OGZlOTJmMDg5ZTFiMDAwYzNlZDY5NjA0NzZlNDU5NmY)
**Describe the Bug**
workspace admin can't add a custom app repo because of access problem
**Versions Used**
KubeSphere: 3.0 alpha 2
**How To Reproduce**
Steps to reproduce the behavior:
1. Create a user with 'Platform Regular' role
2. Create a workspace and assign this user as the workspace admin
3. login as this user and access above workspace
4. Add a custom app repo, and got an access denied msg.
<img width="1323" alt="Xnip2020-07-26_18-26-48" src="https://user-images.githubusercontent.com/28883416/88476824-23ab4300-cf6e-11ea-98a2-7390ea37e51e.png">
<img width="1614" alt="Xnip2020-07-26_18-27-29" src="https://user-images.githubusercontent.com/28883416/88476842-2ad25100-cf6e-11ea-90bb-74ec942f2680.png">
| priority | workspace admin can t add a custom app repo because of access problem english only 注意！github issue 仅支持英文，中文 issue 请在 提交。 general remarks please delete this section including header before submitting this form is to report bugs for general usage questions refer to our slack channel describe the bug workspace admin can t add a custom app repo because of access problem versions used kubesphere alpha how to reproduce steps to reproduce the behavior create a user with platform regular role create a workspace and assign this user as the workspace admin login as this user and access above workspace add a custom app repo and got an access denied msg img width alt src img width alt src | 1 |
265,440 | 8,354,366,762 | IssuesEvent | 2018-10-02 13:08:06 | CS2103-AY1819S1-W13-1/main | https://api.github.com/repos/CS2103-AY1819S1-W13-1/main | closed | As a user I can use the tag command to view all persons with a tag that I have specified | priority.High type.Story | so that I can more easily view contacts with the same tag. | 1.0 | As a user I can use the tag command to view all persons with a tag that I have specified - so that I can more easily view contacts with the same tag. | priority | as a user i can use the tag command to view all persons with a tag that i have specified so that i can more easily view contacts with the same tag | 1 |
226,999 | 7,526,008,923 | IssuesEvent | 2018-04-13 12:42:34 | inverse-inc/packetfence | https://api.github.com/repos/inverse-inc/packetfence | opened | Dashboard: most sections are still empty | Priority: High Type: Feature / Enhancement | This is more of a meta issue so we don't mistakenly forget this before the release but only the first tab of the dashboard has graphs now
RADIUS, authentication and endpoints are still empty | 1.0 | Dashboard: most sections are still empty - This is more of a meta issue so we don't mistakenly forget this before the release but only the first tab of the dashboard has graphs now
RADIUS, authentication and endpoints are still empty | priority | dashboard most sections are still empty this is more of a meta issue so we don t mistakenly forget this before the release but only the first tab of the dashboard has graphs now radius authentication and endpoints are still empty | 1 |
549,937 | 16,101,985,812 | IssuesEvent | 2021-04-27 10:27:58 | snowplow/snowplow-android-tracker | https://api.github.com/repos/snowplow/snowplow-android-tracker | closed | Fix StrictMode alerts | priority:high status:completed type:enhancement | StrictMode is a developer tool which detects things you might be doing by accident and brings them to your attention so you can fix them.
The tracker raises "StrictMode$StrictModeDiskReadViolation" when the Session read the SharedPreferences to get some basic information about the previous session. | 1.0 | Fix StrictMode alerts - StrictMode is a developer tool which detects things you might be doing by accident and brings them to your attention so you can fix them.
The tracker raises "StrictMode$StrictModeDiskReadViolation" when the Session read the SharedPreferences to get some basic information about the previous session. | priority | fix strictmode alerts strictmode is a developer tool which detects things you might be doing by accident and brings them to your attention so you can fix them the tracker raises strictmode strictmodediskreadviolation when the session read the sharedpreferences to get some basic information about the previous session | 1 |
173,188 | 6,521,406,910 | IssuesEvent | 2017-08-28 20:27:19 | SemBioProcess/SemGen | https://api.github.com/repos/SemBioProcess/SemGen | closed | Extractions produce empty models | 4.0.0 bug high priority | Sometimes when selecting a set of nodes in a model, then right clicking and selecting "Extract Selected", the resulting model doesn't contain anything. Double clicking it shows an empty model and selecting the different visualizations don't do anything. | 1.0 | Extractions produce empty models - Sometimes when selecting a set of nodes in a model, then right clicking and selecting "Extract Selected", the resulting model doesn't contain anything. Double clicking it shows an empty model and selecting the different visualizations don't do anything. | priority | extractions produce empty models sometimes when selecting a set of nodes in a model then right clicking and selecting extract selected the resulting model doesn t contain anything double clicking it shows an empty model and selecting the different visualizations don t do anything | 1 |
87,361 | 3,750,364,953 | IssuesEvent | 2016-03-11 06:22:20 | YUKAI/konashi-android-sdk | https://api.github.com/repos/YUKAI/konashi-android-sdk | closed | SPI をサポートしない konashi に接続して KonashiManager.spiConfig すると NPE が発生する | bug priority (high) | こちらのコードを実行したところ発生しました。
https://github.com/YUKAI/KonashiInspectorForAndroid/blob/98296bb7aafe7dac6b1292ac5b3f0e38430290fc/app/src/main/java/com/uxxu/konashi/inspector/android/SpiFragment.java#L184
エラーメッセージ
```
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'java.util.UUID android.bluetooth.BluetoothGattCharacteristic.getUuid()' on a null object reference
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at info.izumin.android.bletia.action.CharacteristicAction.<init>(CharacteristicAction.java:16)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at info.izumin.android.bletia.action.WriteCharacteristicAction.<init>(WriteCharacteristicAction.java:15)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.action.KonashiWriteCharacteristicAction.<init>(KonashiWriteCharacteristicAction.java:21)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.action.KonashiWriteCharacteristicAction.<init>(KonashiWriteCharacteristicAction.java:25)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.action.SpiConfigAction.<init>(SpiConfigAction.java:29)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.KonashiManager.spiConfig(KonashiManager.java:614)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.inspector.android.SpiFragment.resetSpi(SpiFragment.java:184)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.inspector.android.SpiFragment.access$000(SpiFragment.java:33)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.inspector.android.SpiFragment$1.onItemSelected(SpiFragment.java:81)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView.fireOnSelected(AdapterView.java:914)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView.dispatchOnItemSelected(AdapterView.java:903)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView.access$300(AdapterView.java:48)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView$SelectionNotifier.run(AdapterView.java:873)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.os.Looper.loop(Looper.java:135)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5254)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
```
https://github.com/YUKAI/konashi-android-sdk/blob/master/konashi-android-sdk/src/main/java/com/uxxu/konashi/lib/action/KonashiWriteCharacteristicAction.java#L24-L26
```
protected KonashiWriteCharacteristicAction(BluetoothGattService service, UUID uuid) {
this(service.getCharacteristic(uuid));
}
```
で `this()` に null が渡ってしまっているのが原因のようです。 | 1.0 | SPI をサポートしない konashi に接続して KonashiManager.spiConfig すると NPE が発生する - こちらのコードを実行したところ発生しました。
https://github.com/YUKAI/KonashiInspectorForAndroid/blob/98296bb7aafe7dac6b1292ac5b3f0e38430290fc/app/src/main/java/com/uxxu/konashi/inspector/android/SpiFragment.java#L184
エラーメッセージ
```
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'java.util.UUID android.bluetooth.BluetoothGattCharacteristic.getUuid()' on a null object reference
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at info.izumin.android.bletia.action.CharacteristicAction.<init>(CharacteristicAction.java:16)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at info.izumin.android.bletia.action.WriteCharacteristicAction.<init>(WriteCharacteristicAction.java:15)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.action.KonashiWriteCharacteristicAction.<init>(KonashiWriteCharacteristicAction.java:21)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.action.KonashiWriteCharacteristicAction.<init>(KonashiWriteCharacteristicAction.java:25)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.action.SpiConfigAction.<init>(SpiConfigAction.java:29)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.lib.KonashiManager.spiConfig(KonashiManager.java:614)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.inspector.android.SpiFragment.resetSpi(SpiFragment.java:184)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.inspector.android.SpiFragment.access$000(SpiFragment.java:33)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.uxxu.konashi.inspector.android.SpiFragment$1.onItemSelected(SpiFragment.java:81)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView.fireOnSelected(AdapterView.java:914)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView.dispatchOnItemSelected(AdapterView.java:903)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView.access$300(AdapterView.java:48)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.widget.AdapterView$SelectionNotifier.run(AdapterView.java:873)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.os.Looper.loop(Looper.java:135)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5254)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
01-12 19:04:43.305 1490-1490/com.uxxu.konashi.inspector.android E/AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
```
https://github.com/YUKAI/konashi-android-sdk/blob/master/konashi-android-sdk/src/main/java/com/uxxu/konashi/lib/action/KonashiWriteCharacteristicAction.java#L24-L26
```
protected KonashiWriteCharacteristicAction(BluetoothGattService service, UUID uuid) {
this(service.getCharacteristic(uuid));
}
```
で `this()` に null が渡ってしまっているのが原因のようです。 | priority | spi をサポートしない konashi に接続して konashimanager spiconfig すると npe が発生する こちらのコードを実行したところ発生しました。 エラーメッセージ com uxxu konashi inspector android e androidruntime java lang nullpointerexception attempt to invoke virtual method java util uuid android bluetooth bluetoothgattcharacteristic getuuid on a null object reference com uxxu konashi inspector android e androidruntime at info izumin android bletia action characteristicaction characteristicaction java com uxxu konashi inspector android e androidruntime at info izumin android bletia action writecharacteristicaction writecharacteristicaction java com uxxu konashi inspector android e androidruntime at com uxxu konashi lib action konashiwritecharacteristicaction konashiwritecharacteristicaction java com uxxu konashi inspector android e androidruntime at com uxxu konashi lib action konashiwritecharacteristicaction konashiwritecharacteristicaction java com uxxu konashi inspector android e androidruntime at com uxxu konashi lib action spiconfigaction spiconfigaction java com uxxu konashi inspector android e androidruntime at com uxxu konashi lib konashimanager spiconfig konashimanager java com uxxu konashi inspector android e androidruntime at com uxxu konashi inspector android spifragment resetspi spifragment java com uxxu konashi inspector android e androidruntime at com uxxu konashi inspector android spifragment access spifragment java com uxxu konashi inspector android e androidruntime at com uxxu konashi inspector android spifragment onitemselected spifragment java com uxxu konashi inspector android e androidruntime at android widget adapterview fireonselected adapterview java com uxxu konashi inspector android e androidruntime at android widget adapterview dispatchonitemselected adapterview java com uxxu konashi inspector android e androidruntime at android widget adapterview access adapterview java com uxxu konashi inspector android e androidruntime at android widget adapterview selectionnotifier run adapterview java com uxxu konashi inspector android e androidruntime at android os handler handlecallback handler java com uxxu konashi inspector android e androidruntime at android os handler dispatchmessage handler java com uxxu konashi inspector android e androidruntime at android os looper loop looper java com uxxu konashi inspector android e androidruntime at android app activitythread main activitythread java com uxxu konashi inspector android e androidruntime at java lang reflect method invoke native method com uxxu konashi inspector android e androidruntime at java lang reflect method invoke method java com uxxu konashi inspector android e androidruntime at com android internal os zygoteinit methodandargscaller run zygoteinit java com uxxu konashi inspector android e androidruntime at com android internal os zygoteinit main zygoteinit java protected konashiwritecharacteristicaction bluetoothgattservice service uuid uuid this service getcharacteristic uuid で this に null が渡ってしまっているのが原因のようです。 | 1 |
524,032 | 15,194,825,946 | IssuesEvent | 2021-02-16 04:49:25 | QuantEcon/lecture-python.myst | https://api.github.com/repos/QuantEcon/lecture-python.myst | closed | [downloadnb-comparison] [14_linear_models] a sentence disappears in MYST | high-priority | Hi @mmcky , I find the following sentence is missing in ``MYST`` notebook of lecture [14_linear_models](https://quantecon.github.io/lecture-python.myst/linear_models.html#conditions-for-stationarity):
- ``This is the *globally stable case* — see <ahref=_static/lecture_specific/linear_models/iteration_notes.pdfdownload>these notes</a> for more a theoretical treatment.``
Please find a screenshot for the corresponding place of lecture ``14_linear_models`` (left: ``RST``, right: ``MYST``):
| 1.0 | [downloadnb-comparison] [14_linear_models] a sentence disappears in MYST - Hi @mmcky , I find the following sentence is missing in ``MYST`` notebook of lecture [14_linear_models](https://quantecon.github.io/lecture-python.myst/linear_models.html#conditions-for-stationarity):
- ``This is the *globally stable case* — see <ahref=_static/lecture_specific/linear_models/iteration_notes.pdfdownload>these notes</a> for more a theoretical treatment.``
Please find a screenshot for the corresponding place of lecture ``14_linear_models`` (left: ``RST``, right: ``MYST``):
| priority | a sentence disappears in myst hi mmcky i find the following sentence is missing in myst notebook of lecture this is the globally stable case — see these notes for more a theoretical treatment please find a screenshot for the corresponding place of lecture linear models left rst right myst | 1 |
310,991 | 9,526,914,750 | IssuesEvent | 2019-04-29 00:11:42 | gw2efficiency/issues | https://api.github.com/repos/gw2efficiency/issues | closed | Add more "Order by" options | 1-Type: Feature 2-Priority: C 3-Complexity: High 4-Impact: Medium 5-Area: Other 9-Status: Ready for Release | Would be great, if the "order by" in the followng pages could be extended:
https://gw2efficiency.com/account/recipes
Order by:
Buy price (asc/desc)
Sell price (asc/desc)
Order by each column (like with https://gw2efficiency.com/crafting/zephyrite-supply-boxes)
https://gw2efficiency.com/crafting/recipe-overview
https://gw2efficiency.com/crafting/legendaries
https://gw2efficiency.com/crafting/ascended | 1.0 | Add more "Order by" options - Would be great, if the "order by" in the followng pages could be extended:
https://gw2efficiency.com/account/recipes
Order by:
Buy price (asc/desc)
Sell price (asc/desc)
Order by each column (like with https://gw2efficiency.com/crafting/zephyrite-supply-boxes)
https://gw2efficiency.com/crafting/recipe-overview
https://gw2efficiency.com/crafting/legendaries
https://gw2efficiency.com/crafting/ascended | priority | add more order by options would be great if the order by in the followng pages could be extended order by buy price asc desc sell price asc desc order by each column like with | 1 |
613,476 | 19,091,492,845 | IssuesEvent | 2021-11-29 12:36:58 | turbot/steampipe-plugin-aws | https://api.github.com/repos/turbot/steampipe-plugin-aws | closed | Add listener details in table aws_ec2_network_load_balancer | enhancement priority:high | **Is your feature request related to a problem? Please describe.**
Add listener details in table aws_ec2_network_load_balancer
https://pkg.go.dev/github.com/aws/aws-sdk-go/service/elbv2#ELBV2.DescribeListeners
This is required for `elbv2-acm-certificate-required` config rule.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
| 1.0 | Add listener details in table aws_ec2_network_load_balancer - **Is your feature request related to a problem? Please describe.**
Add listener details in table aws_ec2_network_load_balancer
https://pkg.go.dev/github.com/aws/aws-sdk-go/service/elbv2#ELBV2.DescribeListeners
This is required for `elbv2-acm-certificate-required` config rule.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
| priority | add listener details in table aws network load balancer is your feature request related to a problem please describe add listener details in table aws network load balancer this is required for acm certificate required config rule describe the solution you d like a clear and concise description of what you want to happen describe alternatives you ve considered a clear and concise description of any alternative solutions or features you ve considered additional context add any other context or screenshots about the feature request here | 1 |
484,649 | 13,943,273,774 | IssuesEvent | 2020-10-22 22:42:27 | ctm/mb2-doc | https://api.github.com/repos/ctm/mb2-doc | closed | stud bring-in should have explicit wording | easy enhancement high priority | ```
GrizzB: the stud messages could be better
GrizzB: your bring in or whatever
``` | 1.0 | stud bring-in should have explicit wording - ```
GrizzB: the stud messages could be better
GrizzB: your bring in or whatever
``` | priority | stud bring in should have explicit wording grizzb the stud messages could be better grizzb your bring in or whatever | 1 |
657,045 | 21,783,587,582 | IssuesEvent | 2022-05-13 22:13:18 | jerboa88/Mergist | https://api.github.com/repos/jerboa88/Mergist | closed | Create CONTRIBUTIONS.md | ⏰ Status: In Progress 🗃 Type: Maintenance 🛡 Priority: High | **Description**
Create CONTRIBUTIONS.md with more details about the project. Move existing info out of the README and link to the new file.
| 1.0 | Create CONTRIBUTIONS.md - **Description**
Create CONTRIBUTIONS.md with more details about the project. Move existing info out of the README and link to the new file.
| priority | create contributions md description create contributions md with more details about the project move existing info out of the readme and link to the new file | 1 |
58,451 | 3,089,485,366 | IssuesEvent | 2015-08-25 21:45:03 | DoSomething/longshot | https://api.github.com/repos/DoSomething/longshot | closed | Redirect to Admin Scholarships list on new scholarship save | @bender priority-high | References #673
After hitting save to create a new scholarship, get a white screen; scholarship is created, but doesn't redirect back to anything... just left staring at a blank page. | 1.0 | Redirect to Admin Scholarships list on new scholarship save - References #673
After hitting save to create a new scholarship, get a white screen; scholarship is created, but doesn't redirect back to anything... just left staring at a blank page. | priority | redirect to admin scholarships list on new scholarship save references after hitting save to create a new scholarship get a white screen scholarship is created but doesn t redirect back to anything just left staring at a blank page | 1 |
448,864 | 12,959,218,941 | IssuesEvent | 2020-07-20 12:40:50 | onaio/reveal-frontend | https://api.github.com/repos/onaio/reveal-frontend | opened | Plan Team Assignment For Expired Plans | Priority: High Size: Small | For all plans whose end date is in the past:
- [ ] The "Assign Teams" button should be disabled
- [ ] Show a tooltip with the words "Cannot assign teams for expired plans" when you hover the "Assign Teams" button | 1.0 | Plan Team Assignment For Expired Plans - For all plans whose end date is in the past:
- [ ] The "Assign Teams" button should be disabled
- [ ] Show a tooltip with the words "Cannot assign teams for expired plans" when you hover the "Assign Teams" button | priority | plan team assignment for expired plans for all plans whose end date is in the past the assign teams button should be disabled show a tooltip with the words cannot assign teams for expired plans when you hover the assign teams button | 1 |
924 | 2,505,179,254 | IssuesEvent | 2015-01-11 05:07:10 | chessmasterhong/WaterEmblem | https://api.github.com/repos/chessmasterhong/WaterEmblem | closed | Clicking enemy during player's turn locks game in menu. | bug high priority | Clicking an enemy unit during the player unit's turn brings up the action menu as if the player unit has moved already when it actually has not moved yet. The major issue is that this menu **cannot** be escaped by pressing the escape key when it actually should. The only workaround if this scenario occurs is to click on a player unit first (no visuals will happen yet) and then press the escape key. | 1.0 | Clicking enemy during player's turn locks game in menu. - Clicking an enemy unit during the player unit's turn brings up the action menu as if the player unit has moved already when it actually has not moved yet. The major issue is that this menu **cannot** be escaped by pressing the escape key when it actually should. The only workaround if this scenario occurs is to click on a player unit first (no visuals will happen yet) and then press the escape key. | priority | clicking enemy during player s turn locks game in menu clicking an enemy unit during the player unit s turn brings up the action menu as if the player unit has moved already when it actually has not moved yet the major issue is that this menu cannot be escaped by pressing the escape key when it actually should the only workaround if this scenario occurs is to click on a player unit first no visuals will happen yet and then press the escape key | 1 |
796,171 | 28,100,910,572 | IssuesEvent | 2023-03-30 19:24:55 | RedHat-UX/red-hat-design-system | https://api.github.com/repos/RedHat-UX/red-hat-design-system | reopened | [feat] Use semantic color tokens wherever possible | high priority | Comb through RHDS repo for use of "crayon colors" or other non-semantic tokens, and replace with semantic tokens.
Referencing: https://github.com/RedHat-UX/red-hat-design-tokens/issues/80 | 1.0 | [feat] Use semantic color tokens wherever possible - Comb through RHDS repo for use of "crayon colors" or other non-semantic tokens, and replace with semantic tokens.
Referencing: https://github.com/RedHat-UX/red-hat-design-tokens/issues/80 | priority | use semantic color tokens wherever possible comb through rhds repo for use of crayon colors or other non semantic tokens and replace with semantic tokens referencing | 1 |
732,396 | 25,258,245,417 | IssuesEvent | 2022-11-15 20:07:53 | SRF-Consulting-Group-Inc/iris | https://api.github.com/repos/SRF-Consulting-Group-Inc/iris | closed | Frequent cycling into "Failed" state for DMS signs | High Priority | For a large number (total unknown, but likely more than 50) of signs, the communication status moves to "Failed". These may return to "Available" or "Deployed" on their own, but will generally respond to a manual poll.
Unclear if there are polling/comm parameters that can be adjusted to compensate for this. | 1.0 | Frequent cycling into "Failed" state for DMS signs - For a large number (total unknown, but likely more than 50) of signs, the communication status moves to "Failed". These may return to "Available" or "Deployed" on their own, but will generally respond to a manual poll.
Unclear if there are polling/comm parameters that can be adjusted to compensate for this. | priority | frequent cycling into failed state for dms signs for a large number total unknown but likely more than of signs the communication status moves to failed these may return to available or deployed on their own but will generally respond to a manual poll unclear if there are polling comm parameters that can be adjusted to compensate for this | 1 |
27,708 | 2,695,305,267 | IssuesEvent | 2015-04-02 03:46:02 | cs2103jan2015-t13-4j/main | https://api.github.com/repos/cs2103jan2015-t13-4j/main | closed | User can do a save command during the program run | priority.high type.story | So... this ensures that the data are not lost if there is an event where the program crash | 1.0 | User can do a save command during the program run - So... this ensures that the data are not lost if there is an event where the program crash | priority | user can do a save command during the program run so this ensures that the data are not lost if there is an event where the program crash | 1 |
100,492 | 4,097,355,347 | IssuesEvent | 2016-06-03 01:02:35 | ampproject/amphtml | https://api.github.com/repos/ampproject/amphtml | closed | amp-font: Chrome bug 347460 breaks amp font | Priority: High Starter Type: Bug | documents.font
We have a web font loader script which has this logic -
```javascript
this.document_.fonts.load(fontString).then(() => {
if (this.document_.fonts.check(fontString)) {
resolve();
} else {
reject(new Error('Font could not be loaded,'
+ ' probably due to incorrect @font-face.'));
}
}).catch(reject);
```
And the check almost always fails. It is due to this chrome bug
https://bugs.chromium.org/p/chromium/issues/detail?id=347460#
Here is the actual code
https://github.com/ampproject/amphtml/blob/master/extensions/amp-font/0.1/fontloader.js#L116
And here is the page to test this out
https://ampskrish.herokuapp.com/examples.build/everything.amp.max.html
(If you see the first paragraph in red - means the check failed.)
Do you have any good advice for us.
======
Response from chrome team is --
Suggested workaround: in comment 2.
Which equates to something like this
```javascript
this.document_.fonts.load(fontString).then(() => {
this.document_.fonts.load(fontString).then(() => {
if (this.document_.fonts.check(fontString)) {
resolve();
} else {
reject(new Error('Font could not be loaded,'
+ ' probably due to incorrect @font-face.'));
}
});
}).catch(reject);
``` | 1.0 | amp-font: Chrome bug 347460 breaks amp font - documents.font
We have a web font loader script which has this logic -
```javascript
this.document_.fonts.load(fontString).then(() => {
if (this.document_.fonts.check(fontString)) {
resolve();
} else {
reject(new Error('Font could not be loaded,'
+ ' probably due to incorrect @font-face.'));
}
}).catch(reject);
```
And the check almost always fails. It is due to this chrome bug
https://bugs.chromium.org/p/chromium/issues/detail?id=347460#
Here is the actual code
https://github.com/ampproject/amphtml/blob/master/extensions/amp-font/0.1/fontloader.js#L116
And here is the page to test this out
https://ampskrish.herokuapp.com/examples.build/everything.amp.max.html
(If you see the first paragraph in red - means the check failed.)
Do you have any good advice for us.
======
Response from chrome team is --
Suggested workaround: in comment 2.
Which equates to something like this
```javascript
this.document_.fonts.load(fontString).then(() => {
this.document_.fonts.load(fontString).then(() => {
if (this.document_.fonts.check(fontString)) {
resolve();
} else {
reject(new Error('Font could not be loaded,'
+ ' probably due to incorrect @font-face.'));
}
});
}).catch(reject);
``` | priority | amp font chrome bug breaks amp font documents font we have a web font loader script which has this logic javascript this document fonts load fontstring then if this document fonts check fontstring resolve else reject new error font could not be loaded probably due to incorrect font face catch reject and the check almost always fails it is due to this chrome bug here is the actual code and here is the page to test this out if you see the first paragraph in red means the check failed do you have any good advice for us response from chrome team is suggested workaround in comment which equates to something like this javascript this document fonts load fontstring then this document fonts load fontstring then if this document fonts check fontstring resolve else reject new error font could not be loaded probably due to incorrect font face catch reject | 1 |
386,379 | 11,437,786,381 | IssuesEvent | 2020-02-05 01:06:48 | ngageoint/hootenanny | https://api.github.com/repos/ngageoint/hootenanny | opened | Rubbersheeting is ridiculously slow on large datasets | Category: Core Priority: High Status: Defined Type: Maintenance | Thought I had an issue for this, as it drove me crazy a few months ago. Its turned on by default for Network. We need to disable above some certain linear feature size threshold. The tiny gains it yields are far outweighed by the extreme amount of time it adds to conflate jobs. I'll post some numbers for the ~5.8 million feature conflate job I'm running now, if it ever gets out of the rubbersheeting. | 1.0 | Rubbersheeting is ridiculously slow on large datasets - Thought I had an issue for this, as it drove me crazy a few months ago. Its turned on by default for Network. We need to disable above some certain linear feature size threshold. The tiny gains it yields are far outweighed by the extreme amount of time it adds to conflate jobs. I'll post some numbers for the ~5.8 million feature conflate job I'm running now, if it ever gets out of the rubbersheeting. | priority | rubbersheeting is ridiculously slow on large datasets thought i had an issue for this as it drove me crazy a few months ago its turned on by default for network we need to disable above some certain linear feature size threshold the tiny gains it yields are far outweighed by the extreme amount of time it adds to conflate jobs i ll post some numbers for the million feature conflate job i m running now if it ever gets out of the rubbersheeting | 1 |
528,015 | 15,358,361,046 | IssuesEvent | 2021-03-01 14:43:45 | ansible/awx | https://api.github.com/repos/ansible/awx | opened | Execution environment details view missing organization | priority:high state:needs_devel type:bug | <!-- Issues are for **concrete, actionable bugs and feature requests** only - if you're just asking for debugging help or technical support, please use:
- http://webchat.freenode.net/?channels=ansible-awx
- https://groups.google.com/forum/#!forum/awx-project
We have to limit this because of limited volunteer time to respond to issues! -->
##### ISSUE TYPE
- Bug Report
##### SUMMARY
The `Organization` information is not present on details view for an Execution Environment
##### STEPS TO REPRODUCE
1. Create an EE with organization
2. Navigate to details view
##### EXPECTED RESULTS
The organization assosiated should be displayed
##### ACTUAL RESULTS
<!-- What actually happened? -->
##### ADDITIONAL INFORMATION
<!-- Include any links to sosreport, database dumps, screenshots or other
information. -->
| 1.0 | Execution environment details view missing organization - <!-- Issues are for **concrete, actionable bugs and feature requests** only - if you're just asking for debugging help or technical support, please use:
- http://webchat.freenode.net/?channels=ansible-awx
- https://groups.google.com/forum/#!forum/awx-project
We have to limit this because of limited volunteer time to respond to issues! -->
##### ISSUE TYPE
- Bug Report
##### SUMMARY
The `Organization` information is not present on details view for an Execution Environment
##### STEPS TO REPRODUCE
1. Create an EE with organization
2. Navigate to details view
##### EXPECTED RESULTS
The organization assosiated should be displayed
##### ACTUAL RESULTS
<!-- What actually happened? -->
##### ADDITIONAL INFORMATION
<!-- Include any links to sosreport, database dumps, screenshots or other
information. -->
| priority | execution environment details view missing organization issues are for concrete actionable bugs and feature requests only if you re just asking for debugging help or technical support please use we have to limit this because of limited volunteer time to respond to issues issue type bug report summary the organization information is not present on details view for an execution environment steps to reproduce create an ee with organization navigate to details view expected results the organization assosiated should be displayed actual results additional information include any links to sosreport database dumps screenshots or other information | 1 |
281,720 | 8,698,627,672 | IssuesEvent | 2018-12-05 00:15:32 | AICrowd/ai-crowd-3 | https://api.github.com/repos/AICrowd/ai-crowd-3 | closed | Memory paging in crowdAI | high priority | _From @seanfcarroll on February 21, 2017 07:43_
```
Feb 19 19:17:24 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:17:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:17:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:18:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:18:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:18:23 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:18:23 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:18:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:18:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:19:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:19:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
```
_Copied from original issue: crowdAI/crowdai#55_ | 1.0 | Memory paging in crowdAI - _From @seanfcarroll on February 21, 2017 07:43_
```
Feb 19 19:17:24 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:17:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:17:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:18:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:18:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:18:23 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:18:23 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:18:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:18:43 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
Feb 19 19:19:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#load_avg_1m=0.00 sample#load_avg_5m=0.00 sample#load_avg_15m=0.00
Feb 19 19:19:03 crowdai-prd heroku/web.2: source=web.2 dyno=heroku.48624194.5ca0da63-a538-4ec4-aa69-2725f19c15da sample#memory_total=597.35MB sample#memory_rss=592.55MB sample#memory_cache=4.04MB sample#memory_swap=0.76MB sample#memory_pgpgin=404239pages sample#memory_pgpgout=251512pages sample#memory_quota=1024.00MB
```
_Copied from original issue: crowdAI/crowdai#55_ | priority | memory paging in crowdai from seanfcarroll on february feb crowdai prd heroku web source web dyno heroku sample memory total sample memory rss sample memory cache sample memory swap sample memory pgpgin sample memory pgpgout sample memory quota feb crowdai prd heroku web source web dyno heroku sample load avg sample load avg sample load avg feb crowdai prd heroku web source web dyno heroku sample memory total sample memory rss sample memory cache sample memory swap sample memory pgpgin sample memory pgpgout sample memory quota feb crowdai prd heroku web source web dyno heroku sample load avg sample load avg sample load avg feb crowdai prd heroku web source web dyno heroku sample memory total sample memory rss sample memory cache sample memory swap sample memory pgpgin sample memory pgpgout sample memory quota feb crowdai prd heroku web source web dyno heroku sample load avg sample load avg sample load avg feb crowdai prd heroku web source web dyno heroku sample memory total sample memory rss sample memory cache sample memory swap sample memory pgpgin sample memory pgpgout sample memory quota feb crowdai prd heroku web source web dyno heroku sample load avg sample load avg sample load avg feb crowdai prd heroku web source web dyno heroku sample memory total sample memory rss sample memory cache sample memory swap sample memory pgpgin sample memory pgpgout sample memory quota feb crowdai prd heroku web source web dyno heroku sample load avg sample load avg sample load avg feb crowdai prd heroku web source web dyno heroku sample memory total sample memory rss sample memory cache sample memory swap sample memory pgpgin sample memory pgpgout sample memory quota copied from original issue crowdai crowdai | 1 |
393,589 | 11,621,982,143 | IssuesEvent | 2020-02-27 04:58:02 | nmstate/nmstate | https://api.github.com/repos/nmstate/nmstate | closed | DHCP timeout will cause software interface deleted in `libnmstate.show()`. | High priority | The NM will delete the device if DHCP timeout on software interface(like bond).
nmstate is using `NM.Client.get_devices()` for the interface list. | 1.0 | DHCP timeout will cause software interface deleted in `libnmstate.show()`. - The NM will delete the device if DHCP timeout on software interface(like bond).
nmstate is using `NM.Client.get_devices()` for the interface list. | priority | dhcp timeout will cause software interface deleted in libnmstate show the nm will delete the device if dhcp timeout on software interface like bond nmstate is using nm client get devices for the interface list | 1 |
616,586 | 19,306,632,239 | IssuesEvent | 2021-12-13 12:15:03 | Dicey-Tech/frontend-app-teacher-dashboard | https://api.github.com/repos/Dicey-Tech/frontend-app-teacher-dashboard | opened | Combine teacher and student dashboard | type:enhancement priority:high | <!--- Provide a general summary of the issue in the Title above -->
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
Depending on a user's role in an enterprise, display the appropriate components.
### Teachers
- Classroom row
- Currently teaching courses
-
### Students
- Currently enrolled courses
| 1.0 | Combine teacher and student dashboard - <!--- Provide a general summary of the issue in the Title above -->
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
Depending on a user's role in an enterprise, display the appropriate components.
### Teachers
- Classroom row
- Currently teaching courses
-
### Students
- Currently enrolled courses
| priority | combine teacher and student dashboard expected behavior depending on a user s role in an enterprise display the appropriate components teachers classroom row currently teaching courses students currently enrolled courses | 1 |
244,239 | 7,872,432,652 | IssuesEvent | 2018-06-25 11:13:08 | assistify/Rocket.Chat | https://api.github.com/repos/assistify/Rocket.Chat | opened | Creating a thread should set a proper topic for Smarti | Cmp: Smarti in RocketChat Priority: High Type: Improvement | ### Description:
When creating a new thread from a message, there is used the channelId as topic.
This should be improved by giving the new channel an appropriate topic.
### Server Setup Information:
* Version of Rocket.Chat Server: `v0.63.3-0.8.1`
* Operating System: `4.9.81-35.56.amzn1.x86_64`
* Deployment Method(snap/docker/tar/etc): `tar.gz`
* Number of Running Instances: `2`
* DB Replicaset Oplog: `enabled`
* Node Version: `v8.9.4`
* mongoDB Version: `3.6`
### Steps to Reproduce:
1. Start a new thread by selecting "Start thread" from the context menu from a single message
<img width="1088" alt="rocket_chat_" src="https://user-images.githubusercontent.com/853776/41847175-5d7e3a9a-7879-11e8-9089-fa44fa490828.png">
### Expected behavior:
The correct topic is sent to Smarti
### Actual behavior:
The channelId is passed.
| 1.0 | Creating a thread should set a proper topic for Smarti - ### Description:
When creating a new thread from a message, there is used the channelId as topic.
This should be improved by giving the new channel an appropriate topic.
### Server Setup Information:
* Version of Rocket.Chat Server: `v0.63.3-0.8.1`
* Operating System: `4.9.81-35.56.amzn1.x86_64`
* Deployment Method(snap/docker/tar/etc): `tar.gz`
* Number of Running Instances: `2`
* DB Replicaset Oplog: `enabled`
* Node Version: `v8.9.4`
* mongoDB Version: `3.6`
### Steps to Reproduce:
1. Start a new thread by selecting "Start thread" from the context menu from a single message
<img width="1088" alt="rocket_chat_" src="https://user-images.githubusercontent.com/853776/41847175-5d7e3a9a-7879-11e8-9089-fa44fa490828.png">
### Expected behavior:
The correct topic is sent to Smarti
### Actual behavior:
The channelId is passed.
| priority | creating a thread should set a proper topic for smarti description when creating a new thread from a message there is used the channelid as topic this should be improved by giving the new channel an appropriate topic server setup information version of rocket chat server operating system deployment method snap docker tar etc tar gz number of running instances db replicaset oplog enabled node version mongodb version steps to reproduce start a new thread by selecting start thread from the context menu from a single message img width alt rocket chat src expected behavior the correct topic is sent to smarti actual behavior the channelid is passed | 1 |
69,993 | 3,316,363,073 | IssuesEvent | 2015-11-06 16:35:33 | TeselaGen/Peony-Issue-Tracking | https://api.github.com/repos/TeselaGen/Peony-Issue-Tracking | opened | AA to DNA back-translation interface/mechanism | Customer: DAS Phase I Priority: High Type: Feature | _From @sampearl on August 20, 2015 20:33_
* Create user-configurable (preloaded plus upload-able, or manually added) Codon translation table interface
* Immediate back-translation upon upload of AA via default codon table
* User-controlled alternate back-translations of AA via new translation interface
_Copied from original issue: TeselaGen/ve#1264_ | 1.0 | AA to DNA back-translation interface/mechanism - _From @sampearl on August 20, 2015 20:33_
* Create user-configurable (preloaded plus upload-able, or manually added) Codon translation table interface
* Immediate back-translation upon upload of AA via default codon table
* User-controlled alternate back-translations of AA via new translation interface
_Copied from original issue: TeselaGen/ve#1264_ | priority | aa to dna back translation interface mechanism from sampearl on august create user configurable preloaded plus upload able or manually added codon translation table interface immediate back translation upon upload of aa via default codon table user controlled alternate back translations of aa via new translation interface copied from original issue teselagen ve | 1 |
50,574 | 3,006,488,760 | IssuesEvent | 2015-07-27 10:44:36 | Itseez/opencv | https://api.github.com/repos/Itseez/opencv | opened | Highgui window is not scaled properly when displaying small images | affected: master auto-transferred bug category: highgui-gui priority: normal | Transferred from http://code.opencv.org/issues/3906
```
|| Khue Le on 2014-09-14 15:48
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: highgui-gui
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: x64 / Linux
```
Highgui window is not scaled properly when displaying small images
-----------
```
In OpenCV 3.0 (I did not try other versions), when displaying small images, even with the `WINDOW_AUTOSIZE` flag, the window is not scaled properly.
<pre>
#include <opencv2/core.hpp>
#include <opencv2/imgcodecs.hpp>
#include <opencv2/highgui.hpp>
#include <iostream>
using namespace cv;
using namespace std;
int main( int argc, char** argv )
{
if( argc != 2)
{
cout <<" Usage: display_image ImageToLoadAndDisplay" << endl;
return -1;
}
Mat image;
image = imread(argv[1], IMREAD_COLOR); // Read the file
if( image.empty() ) // Check for invalid input
{
cout << "Could not open or find the image" << std::endl ;
return -1;
}
namedWindow( "Display window", WINDOW_AUTOSIZE ); // Create a window for display.
imshow( "Display window", image ); // Show our image inside it.
while (waitKey(0) != 27); // Wait for ESC key
return 0;
}
</pre>
Test image (100x100):
!http://i.stack.imgur.com/6XB1v.png!
Results:
!http://i.stack.imgur.com/LZOU7.png!
When moving the mouse to the displayed image, I got this:
!http://i.stack.imgur.com/Fo9kx.png!
```
History
-------
##### Dmitry Retinskiy on 2014-09-16 07:05
```
- Description changed from In OpenCV 3.0 (I did not try other
versions), when displaying small images, e... to In OpenCV 3.0 (I
did not try other versions), when displaying small images, e... More
```
##### Dmitry Retinskiy on 2014-09-16 07:12
```
Alexander, please check the problem.
Thanks.
- Target version set to 3.0
- Assignee set to Alexander Smorkalov
- Status changed from New to Open
- Category set to highgui-gui
```
##### Theodore Tsesmelis on 2015-03-08 18:01
```
I can confirm the above bug. I noticed that it is related to the integration with the Qt library. If I compile opencv v.3.0.0 (master branch from github) with Qt4 I do not get this bug, on the other hand if I compile it with Qt5 then it appears. Moreover, on the command line when I am running a project which has to imshow an image I get the following message: *QSettings::value: Empty key passed* twice
```
##### Steven Puttemans on 2015-03-09 08:25
```
Theodore Tsesmelis wrote:
> I can confirm the above bug. Moreover, I noticed that it is related to the integration with the Qt library. If I compile opencv v.3.0.0 (master branch from github) with Qt4 I do not get this bug, on the other hand if I compile it with Qt5 then it appears. Moreover, on the command line when I am running a project which has to imshow an image I get the following message: *QSettings::value: Empty key passed* twice
I can concur that this indeed only happens with Qt5 installations. Got same problem here. My solution was to ignore Qt supported builds for the moment, not really need that extra functionality.
``` | 1.0 | Highgui window is not scaled properly when displaying small images - Transferred from http://code.opencv.org/issues/3906
```
|| Khue Le on 2014-09-14 15:48
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: highgui-gui
|| Tracker: Bug
|| Difficulty:
|| PR:
|| Platform: x64 / Linux
```
Highgui window is not scaled properly when displaying small images
-----------
```
In OpenCV 3.0 (I did not try other versions), when displaying small images, even with the `WINDOW_AUTOSIZE` flag, the window is not scaled properly.
<pre>
#include <opencv2/core.hpp>
#include <opencv2/imgcodecs.hpp>
#include <opencv2/highgui.hpp>
#include <iostream>
using namespace cv;
using namespace std;
int main( int argc, char** argv )
{
if( argc != 2)
{
cout <<" Usage: display_image ImageToLoadAndDisplay" << endl;
return -1;
}
Mat image;
image = imread(argv[1], IMREAD_COLOR); // Read the file
if( image.empty() ) // Check for invalid input
{
cout << "Could not open or find the image" << std::endl ;
return -1;
}
namedWindow( "Display window", WINDOW_AUTOSIZE ); // Create a window for display.
imshow( "Display window", image ); // Show our image inside it.
while (waitKey(0) != 27); // Wait for ESC key
return 0;
}
</pre>
Test image (100x100):
!http://i.stack.imgur.com/6XB1v.png!
Results:
!http://i.stack.imgur.com/LZOU7.png!
When moving the mouse to the displayed image, I got this:
!http://i.stack.imgur.com/Fo9kx.png!
```
History
-------
##### Dmitry Retinskiy on 2014-09-16 07:05
```
- Description changed from In OpenCV 3.0 (I did not try other
versions), when displaying small images, e... to In OpenCV 3.0 (I
did not try other versions), when displaying small images, e... More
```
##### Dmitry Retinskiy on 2014-09-16 07:12
```
Alexander, please check the problem.
Thanks.
- Target version set to 3.0
- Assignee set to Alexander Smorkalov
- Status changed from New to Open
- Category set to highgui-gui
```
##### Theodore Tsesmelis on 2015-03-08 18:01
```
I can confirm the above bug. I noticed that it is related to the integration with the Qt library. If I compile opencv v.3.0.0 (master branch from github) with Qt4 I do not get this bug, on the other hand if I compile it with Qt5 then it appears. Moreover, on the command line when I am running a project which has to imshow an image I get the following message: *QSettings::value: Empty key passed* twice
```
##### Steven Puttemans on 2015-03-09 08:25
```
Theodore Tsesmelis wrote:
> I can confirm the above bug. Moreover, I noticed that it is related to the integration with the Qt library. If I compile opencv v.3.0.0 (master branch from github) with Qt4 I do not get this bug, on the other hand if I compile it with Qt5 then it appears. Moreover, on the command line when I am running a project which has to imshow an image I get the following message: *QSettings::value: Empty key passed* twice
I can concur that this indeed only happens with Qt5 installations. Got same problem here. My solution was to ignore Qt supported builds for the moment, not really need that extra functionality.
``` | priority | highgui window is not scaled properly when displaying small images transferred from khue le on priority normal affected branch master dev category highgui gui tracker bug difficulty pr platform linux highgui window is not scaled properly when displaying small images in opencv i did not try other versions when displaying small images even with the window autosize flag the window is not scaled properly include include include include using namespace cv using namespace std int main int argc char argv if argc cout usage display image imagetoloadanddisplay endl return mat image image imread argv imread color read the file if image empty check for invalid input cout could not open or find the image std endl return namedwindow display window window autosize create a window for display imshow display window image show our image inside it while waitkey wait for esc key return test image results when moving the mouse to the displayed image i got this history dmitry retinskiy on description changed from in opencv i did not try other versions when displaying small images e to in opencv i did not try other versions when displaying small images e more dmitry retinskiy on alexander please check the problem thanks target version set to assignee set to alexander smorkalov status changed from new to open category set to highgui gui theodore tsesmelis on i can confirm the above bug i noticed that it is related to the integration with the qt library if i compile opencv v master branch from github with i do not get this bug on the other hand if i compile it with then it appears moreover on the command line when i am running a project which has to imshow an image i get the following message qsettings value empty key passed twice steven puttemans on theodore tsesmelis wrote i can confirm the above bug moreover i noticed that it is related to the integration with the qt library if i compile opencv v master branch from github with i do not get this bug on the other hand if i compile it with then it appears moreover on the command line when i am running a project which has to imshow an image i get the following message qsettings value empty key passed twice i can concur that this indeed only happens with installations got same problem here my solution was to ignore qt supported builds for the moment not really need that extra functionality | 1 |
363,200 | 10,739,145,249 | IssuesEvent | 2019-10-29 15:53:05 | ADFC-Hamburg/adfc-t30-paten-frontend | https://api.github.com/repos/ADFC-Hamburg/adfc-t30-paten-frontend | closed | Doppelte Issues aufräumen | Büro high-priority | Es ist total demotivierend wenn es für ein und die selbe sache, zwei oder mehr Tickets gibt. | 1.0 | Doppelte Issues aufräumen - Es ist total demotivierend wenn es für ein und die selbe sache, zwei oder mehr Tickets gibt. | priority | doppelte issues aufräumen es ist total demotivierend wenn es für ein und die selbe sache zwei oder mehr tickets gibt | 1 |
539,821 | 15,795,497,332 | IssuesEvent | 2021-04-02 13:15:29 | oslc-op/oslc-specs | https://api.github.com/repos/oslc-op/oslc-specs | closed | Core/Discovery and Core/resource-shape have 2 odd Core 2.0 refs | Area: Core Core: Main Spec Kind: Normative Priority: High Tag: Has PR | @jamsden here is the snippet from discovery.html:
```js
OSLCSPR: {
title: "OSLC Core 2.0 Service Provider Resources",
href: "http://open-services.net/bin/view/Main/OslcCoreSpecification#Service_Provider_Resources",
authors: ["S. Speicher", "D. Johnson"],
status: "Finalized",
publisher: "http://open-services.net",
},
OSLCSPV: {
title: "OSLC Core 2.0 Selective Property Values",
href: "http://open-services.net/bin/view/Main/OslcCoreSpecification#Selective_Property_Values",
authors: ["S. Speicher", "D. Johnson"],
status: "Finalized",
publisher: "http://open-services.net",
},
```
1. Should we have 2 references to the same spec?
2. Should we reference 2.0 specs from 3.0? | 1.0 | Core/Discovery and Core/resource-shape have 2 odd Core 2.0 refs - @jamsden here is the snippet from discovery.html:
```js
OSLCSPR: {
title: "OSLC Core 2.0 Service Provider Resources",
href: "http://open-services.net/bin/view/Main/OslcCoreSpecification#Service_Provider_Resources",
authors: ["S. Speicher", "D. Johnson"],
status: "Finalized",
publisher: "http://open-services.net",
},
OSLCSPV: {
title: "OSLC Core 2.0 Selective Property Values",
href: "http://open-services.net/bin/view/Main/OslcCoreSpecification#Selective_Property_Values",
authors: ["S. Speicher", "D. Johnson"],
status: "Finalized",
publisher: "http://open-services.net",
},
```
1. Should we have 2 references to the same spec?
2. Should we reference 2.0 specs from 3.0? | priority | core discovery and core resource shape have odd core refs jamsden here is the snippet from discovery html js oslcspr title oslc core service provider resources href authors status finalized publisher oslcspv title oslc core selective property values href authors status finalized publisher should we have references to the same spec should we reference specs from | 1 |
629,362 | 20,030,357,608 | IssuesEvent | 2022-02-02 04:34:01 | way-of-elendil/3.3.5 | https://api.github.com/repos/way-of-elendil/3.3.5 | closed | Sindragosa (et autres dragons) hitbox | bug status-wontfix type-boss type-dungeon priority-high | **Description**
La hitbox des dragons en boss de raids est mal positionnée. Elle touche les joueurs placées sur le flanc (même au centre)
**Étapes de reproduction**
Faites un raid avec sindra
**Comportement attendu**
La hitbox des stuns/bump des dragons doit se passer sur le point d'impact de la queue (avec 20 yard de distance).
**Captures d’écran / Vidéos**
https://www.youtube.com/watch?v=DBRx9magQ0c
**Ressources additionnelles**
https://wowwiki.fandom.com/wiki/Sindragosa_(tactics)
https://github.com/TrinityCore/TrinityCore/issues/12235
Ps : Il me semble que c'est la même pour Halion et autres dragons. | 1.0 | Sindragosa (et autres dragons) hitbox - **Description**
La hitbox des dragons en boss de raids est mal positionnée. Elle touche les joueurs placées sur le flanc (même au centre)
**Étapes de reproduction**
Faites un raid avec sindra
**Comportement attendu**
La hitbox des stuns/bump des dragons doit se passer sur le point d'impact de la queue (avec 20 yard de distance).
**Captures d’écran / Vidéos**
https://www.youtube.com/watch?v=DBRx9magQ0c
**Ressources additionnelles**
https://wowwiki.fandom.com/wiki/Sindragosa_(tactics)
https://github.com/TrinityCore/TrinityCore/issues/12235
Ps : Il me semble que c'est la même pour Halion et autres dragons. | priority | sindragosa et autres dragons hitbox description la hitbox des dragons en boss de raids est mal positionnée elle touche les joueurs placées sur le flanc même au centre étapes de reproduction faites un raid avec sindra comportement attendu la hitbox des stuns bump des dragons doit se passer sur le point d impact de la queue avec yard de distance captures d’écran vidéos ressources additionnelles ps il me semble que c est la même pour halion et autres dragons | 1 |
432,955 | 12,500,474,952 | IssuesEvent | 2020-06-01 22:22:16 | Azure/ARO-RP | https://api.github.com/repos/Azure/ARO-RP | closed | Failing python unit tests for multiple resource group parameters on aro extensions. | priority-high size-small | The unit tests for python started to fail on the following error.
```
FAIL - HIGH severity: parameter_should_not_end_in_resource_group
Parameter: aro create, `cluster_resource_group` - A command should only have '--resource-group' as its resource group parameter. However options '--cluster-resource-group' in command 'aro create' end with 'resource-group' or similar.
Parameter: aro create, `vnet_resource_group_name` - A command should only have '--resource-group' as its resource group parameter. However options '--vnet-resource-group' in command 'aro create' end with 'resource-group' or similar.
```
The failure is at least in the following prs:
* https://github.com/Azure/ARO-RP/pull/763
* https://github.com/Azure/ARO-RP/pull/693
Renaming should be an option. | 1.0 | Failing python unit tests for multiple resource group parameters on aro extensions. - The unit tests for python started to fail on the following error.
```
FAIL - HIGH severity: parameter_should_not_end_in_resource_group
Parameter: aro create, `cluster_resource_group` - A command should only have '--resource-group' as its resource group parameter. However options '--cluster-resource-group' in command 'aro create' end with 'resource-group' or similar.
Parameter: aro create, `vnet_resource_group_name` - A command should only have '--resource-group' as its resource group parameter. However options '--vnet-resource-group' in command 'aro create' end with 'resource-group' or similar.
```
The failure is at least in the following prs:
* https://github.com/Azure/ARO-RP/pull/763
* https://github.com/Azure/ARO-RP/pull/693
Renaming should be an option. | priority | failing python unit tests for multiple resource group parameters on aro extensions the unit tests for python started to fail on the following error fail high severity parameter should not end in resource group parameter aro create cluster resource group a command should only have resource group as its resource group parameter however options cluster resource group in command aro create end with resource group or similar parameter aro create vnet resource group name a command should only have resource group as its resource group parameter however options vnet resource group in command aro create end with resource group or similar the failure is at least in the following prs renaming should be an option | 1 |
343,676 | 10,334,827,002 | IssuesEvent | 2019-09-03 09:12:51 | openmsupply/mobile | https://api.github.com/repos/openmsupply/mobile | opened | Custom hook refreshing top route | DataTable Docs: not needed Effort: small Priority: High Refactor | ## Is your feature request related to a problem? Please describe.
Currently navigating back to a page does not cause a full re-render, causing inconsistencies:
i.e. `CustomerInvoicesPage` -> `CustomerInvoicePage` (non-new, finalise it) -> `CustomerInvoicesPage` -> See invoice still in progress.
## Describe the solution you'd like
A custom hook which would determine if the page is returning to the top of the stack.
An event can be added to the navigator object, which could dispatch `refreshData`. In order to access the navigator object, the redux selector passing `PageContainer` should be modified to pass the navigation object.
## Describe alternatives you've considered
Don't think there's really another/better solution? Determining if a page is *returning* to the top of the stack isn't quite as simple as just checking a variable set?
Potentially hooking into the `BackHandler`, but without the state of a page in redux, it doesn't seem to be too much help
## Additional context
Any other idea's are definitely welcome!
| 1.0 | Custom hook refreshing top route - ## Is your feature request related to a problem? Please describe.
Currently navigating back to a page does not cause a full re-render, causing inconsistencies:
i.e. `CustomerInvoicesPage` -> `CustomerInvoicePage` (non-new, finalise it) -> `CustomerInvoicesPage` -> See invoice still in progress.
## Describe the solution you'd like
A custom hook which would determine if the page is returning to the top of the stack.
An event can be added to the navigator object, which could dispatch `refreshData`. In order to access the navigator object, the redux selector passing `PageContainer` should be modified to pass the navigation object.
## Describe alternatives you've considered
Don't think there's really another/better solution? Determining if a page is *returning* to the top of the stack isn't quite as simple as just checking a variable set?
Potentially hooking into the `BackHandler`, but without the state of a page in redux, it doesn't seem to be too much help
## Additional context
Any other idea's are definitely welcome!
| priority | custom hook refreshing top route is your feature request related to a problem please describe currently navigating back to a page does not cause a full re render causing inconsistencies i e customerinvoicespage customerinvoicepage non new finalise it customerinvoicespage see invoice still in progress describe the solution you d like a custom hook which would determine if the page is returning to the top of the stack an event can be added to the navigator object which could dispatch refreshdata in order to access the navigator object the redux selector passing pagecontainer should be modified to pass the navigation object describe alternatives you ve considered don t think there s really another better solution determining if a page is returning to the top of the stack isn t quite as simple as just checking a variable set potentially hooking into the backhandler but without the state of a page in redux it doesn t seem to be too much help additional context any other idea s are definitely welcome | 1 |
666,729 | 22,365,460,035 | IssuesEvent | 2022-06-16 03:12:53 | tensorchord/envd | https://api.github.com/repos/tensorchord/envd | closed | enhancement(CLI): Update the description of envd | good first issue ❤️ help wanted 🆘 priority/1-high 🔥 type/enhancement 💭 area/cli 🖥️ | The usage here should be updated.
https://github.com/tensorchord/envd/blob/main/pkg/app/app.go#L40
```diff
func New() EnvdApp {
internalApp := cli.NewApp()
internalApp.EnableBashCompletion = true
internalApp.Name = "envd"
- internalApp.Usage = "Build tools for data scientists"
+ internalApp.Usage = "Development environment for data science and AI/ML teams"
``` | 1.0 | enhancement(CLI): Update the description of envd - The usage here should be updated.
https://github.com/tensorchord/envd/blob/main/pkg/app/app.go#L40
```diff
func New() EnvdApp {
internalApp := cli.NewApp()
internalApp.EnableBashCompletion = true
internalApp.Name = "envd"
- internalApp.Usage = "Build tools for data scientists"
+ internalApp.Usage = "Development environment for data science and AI/ML teams"
``` | priority | enhancement cli update the description of envd the usage here should be updated diff func new envdapp internalapp cli newapp internalapp enablebashcompletion true internalapp name envd internalapp usage build tools for data scientists internalapp usage development environment for data science and ai ml teams | 1 |
241,490 | 7,812,511,382 | IssuesEvent | 2018-06-12 13:36:09 | kowala-tech/kcoin | https://api.github.com/repos/kowala-tech/kcoin | opened | Hardware security for token delivery | High priority andromeda-launch | We need either a Ledger app or a secure USB drive solution. Or both. | 1.0 | Hardware security for token delivery - We need either a Ledger app or a secure USB drive solution. Or both. | priority | hardware security for token delivery we need either a ledger app or a secure usb drive solution or both | 1 |
676,128 | 23,117,102,501 | IssuesEvent | 2022-07-27 17:45:32 | hypertrons/hypertrons-crx | https://api.github.com/repos/hypertrons/hypertrons-crx | closed | [Bug] `yarn run build` and `yarn run start` not working on Windows Machine | kind/bug priority/high | ### Description
In the commit [fix: exsiting way to write process.env.XXX does not work](https://github.com/hypertrons/hypertrons-crx/pull/384/commits/791c261fc46b2be03dfd1868c498dfbb9a172fb6), we changed the way to specify environment variables. However, the wary of adding the env variables directly to `yarn run build` and `yarn run start` doesn't work for windows Machine. Catch error:
becuase we are using windows cmd and the commands are different.
How do we solve this? | 1.0 | [Bug] `yarn run build` and `yarn run start` not working on Windows Machine - ### Description
In the commit [fix: exsiting way to write process.env.XXX does not work](https://github.com/hypertrons/hypertrons-crx/pull/384/commits/791c261fc46b2be03dfd1868c498dfbb9a172fb6), we changed the way to specify environment variables. However, the wary of adding the env variables directly to `yarn run build` and `yarn run start` doesn't work for windows Machine. Catch error:
becuase we are using windows cmd and the commands are different.
How do we solve this? | priority | yarn run build and yarn run start not working on windows machine description in the commit we changed the way to specify environment variables however the wary of adding the env variables directly to yarn run build and yarn run start doesn t work for windows machine catch error becuase we are using windows cmd and the commands are different how do we solve this | 1 |
145,028 | 5,557,321,174 | IssuesEvent | 2017-03-24 11:42:05 | nossas/bonde-client | https://api.github.com/repos/nossas/bonde-client | closed | Undefined Editor of wysihtml5 | Category: DevOps Priority: High Status: Blocked Type: Bug | # Introduction
It needs to fix the **wysihtml5** lib import when try to edit the content of content wdget. Follow the error:
```
TypeError: Cannot read property 'Editor' of undefined
at EditorOld.componentDidMount (editor-old.js:66)
at eval (ReactCompositeComponent.js:265)
at measureLifeCyclePerf (ReactCompositeComponent.js:75)
at eval (ReactCompositeComponent.js:264)
at CallbackQueue.notifyAll (CallbackQueue.js:76)
at ReactReconcileTransaction.close (ReactReconcileTransaction.js:80)
at ReactReconcileTransaction.closeAll (Transaction.js:206)
at ReactReconcileTransaction.perform (Transaction.js:153)
at ReactUpdatesFlushTransaction.perform (Transaction.js:140)
at ReactUpdatesFlushTransaction.perform (ReactUpdates.js:89)
``` | 1.0 | Undefined Editor of wysihtml5 - # Introduction
It needs to fix the **wysihtml5** lib import when try to edit the content of content wdget. Follow the error:
```
TypeError: Cannot read property 'Editor' of undefined
at EditorOld.componentDidMount (editor-old.js:66)
at eval (ReactCompositeComponent.js:265)
at measureLifeCyclePerf (ReactCompositeComponent.js:75)
at eval (ReactCompositeComponent.js:264)
at CallbackQueue.notifyAll (CallbackQueue.js:76)
at ReactReconcileTransaction.close (ReactReconcileTransaction.js:80)
at ReactReconcileTransaction.closeAll (Transaction.js:206)
at ReactReconcileTransaction.perform (Transaction.js:153)
at ReactUpdatesFlushTransaction.perform (Transaction.js:140)
at ReactUpdatesFlushTransaction.perform (ReactUpdates.js:89)
``` | priority | undefined editor of introduction it needs to fix the lib import when try to edit the content of content wdget follow the error typeerror cannot read property editor of undefined at editorold componentdidmount editor old js at eval reactcompositecomponent js at measurelifecycleperf reactcompositecomponent js at eval reactcompositecomponent js at callbackqueue notifyall callbackqueue js at reactreconciletransaction close reactreconciletransaction js at reactreconciletransaction closeall transaction js at reactreconciletransaction perform transaction js at reactupdatesflushtransaction perform transaction js at reactupdatesflushtransaction perform reactupdates js | 1 |
625,231 | 19,722,911,827 | IssuesEvent | 2022-01-13 16:59:46 | ut-issl/c2a-core | https://api.github.com/repos/ut-issl/c2a-core | closed | CmdTlmとなってる部分を，TlmCmdにする | priority::high tools WINGS | ## 概要
CmdTlmとなってる部分を，TlmCmdにする
## 詳細
統一したい
- [x] src/直下
- [x] TlmCmdDBのフォルダ
## close条件
統一できたら
## 備考
各種ツール群などの整合をとる必要があるので，注意
- [x] AddSection.pl
- [x] workflowのトリガ
- [ ] WINGS (GitlabからDBをとってくるところ）
- [x] etc
| 1.0 | CmdTlmとなってる部分を，TlmCmdにする - ## 概要
CmdTlmとなってる部分を，TlmCmdにする
## 詳細
統一したい
- [x] src/直下
- [x] TlmCmdDBのフォルダ
## close条件
統一できたら
## 備考
各種ツール群などの整合をとる必要があるので，注意
- [x] AddSection.pl
- [x] workflowのトリガ
- [ ] WINGS (GitlabからDBをとってくるところ）
- [x] etc
| priority | cmdtlmとなってる部分を，tlmcmdにする 概要 cmdtlmとなってる部分を，tlmcmdにする 詳細 統一したい src 直下 tlmcmddbのフォルダ close条件 統一できたら 備考 各種ツール群などの整合をとる必要があるので，注意 addsection pl workflowのトリガ wings gitlabからdbをとってくるところ） etc | 1 |
596,513 | 18,105,141,969 | IssuesEvent | 2021-09-22 18:21:30 | ansible/awx | https://api.github.com/repos/ansible/awx | closed | [ui_next] Allow for resize/popout of extra_vars fields | type:bug state:in_progress priority:high component:ui | ### Please confirm the following
- [X] I agree to follow this project's [code of conduct](http://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
- [X] I have checked the [current issues](https://github.com/ansible/awx/issues) for duplicates.
- [X] I understand that AWX is open source software provided for free and that I am not entitled to status updates or other assurances.
### Summary
`extra_vars` can get really large, thus cumbersome to read.
Inventory host vars have a popout button due to #3209, and (WF) Job Details had it before ui_next (see #1268), but it's gone now.
### AWX version
19.2.0
### Installation method
kubernetes
### Modifications
no
### Ansible version
_No response_
### Operating system
_No response_
### Web browser
Firefox
### Steps to reproduce
Run a job (best with some extra_vars)
### Expected results
The job details page offers more than 4 lines of variables textfield
### Actual results
the variables display is limited to 4 lines
### Additional information
_No response_ | 1.0 | [ui_next] Allow for resize/popout of extra_vars fields - ### Please confirm the following
- [X] I agree to follow this project's [code of conduct](http://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
- [X] I have checked the [current issues](https://github.com/ansible/awx/issues) for duplicates.
- [X] I understand that AWX is open source software provided for free and that I am not entitled to status updates or other assurances.
### Summary
`extra_vars` can get really large, thus cumbersome to read.
Inventory host vars have a popout button due to #3209, and (WF) Job Details had it before ui_next (see #1268), but it's gone now.
### AWX version
19.2.0
### Installation method
kubernetes
### Modifications
no
### Ansible version
_No response_
### Operating system
_No response_
### Web browser
Firefox
### Steps to reproduce
Run a job (best with some extra_vars)
### Expected results
The job details page offers more than 4 lines of variables textfield
### Actual results
the variables display is limited to 4 lines
### Additional information
_No response_ | priority | allow for resize popout of extra vars fields please confirm the following i agree to follow this project s i have checked the for duplicates i understand that awx is open source software provided for free and that i am not entitled to status updates or other assurances summary extra vars can get really large thus cumbersome to read inventory host vars have a popout button due to and wf job details had it before ui next see but it s gone now awx version installation method kubernetes modifications no ansible version no response operating system no response web browser firefox steps to reproduce run a job best with some extra vars expected results the job details page offers more than lines of variables textfield actual results the variables display is limited to lines additional information no response | 1 |
562,728 | 16,668,473,545 | IssuesEvent | 2021-06-07 08:00:17 | ita-social-projects/TeachUA | https://api.github.com/repos/ita-social-projects/TeachUA | closed | [Мій профіль] Page crashes when clicking on 'Мій профіль' button | Priority: High bug | Environment: macOS Catalina 10.15.7, macOS Catalina 10.15.7, Safari 14.0.3 (15610.4.3.1.7, 15610)
Reproducible: always.
Build found: last commit.
Steps to reproduce
1. Go to https://speak-ukrainian.org.ua/dev/
2. Click on 'Увійти' button
3. Fill in admin credentials (email: admin@gmail.com; password: admin)
4. Click on 'Мій профіль' button
Actual result
Page crash.
https://user-images.githubusercontent.com/83167973/120885183-3bbd0b80-c5f0-11eb-8203-43a21956ee9b.mov
Expected result
'Мій профіль' page is opened.
Labels to be added
"Bug", Priority ("pri: High"), Severity ("severity:High"), Type ("Functional").
| 1.0 | [Мій профіль] Page crashes when clicking on 'Мій профіль' button - Environment: macOS Catalina 10.15.7, macOS Catalina 10.15.7, Safari 14.0.3 (15610.4.3.1.7, 15610)
Reproducible: always.
Build found: last commit.
Steps to reproduce
1. Go to https://speak-ukrainian.org.ua/dev/
2. Click on 'Увійти' button
3. Fill in admin credentials (email: admin@gmail.com; password: admin)
4. Click on 'Мій профіль' button
Actual result
Page crash.
https://user-images.githubusercontent.com/83167973/120885183-3bbd0b80-c5f0-11eb-8203-43a21956ee9b.mov
Expected result
'Мій профіль' page is opened.
Labels to be added
"Bug", Priority ("pri: High"), Severity ("severity:High"), Type ("Functional").
| priority | page crashes when clicking on мій профіль button environment macos catalina macos catalina safari reproducible always build found last commit steps to reproduce go to click on увійти button fill in admin credentials email admin gmail com password admin click on мій профіль button actual result page crash expected result мій профіль page is opened labels to be added bug priority pri high severity severity high type functional | 1 |
544,644 | 15,895,412,462 | IssuesEvent | 2021-04-11 13:55:12 | DIT112-V21/group-09 | https://api.github.com/repos/DIT112-V21/group-09 | closed | 1.1 Frontend app setup | CSS JS NodeJS high-priority sprint-1 | As a user, I want to be able to launch a frontend app and access a generic layout.
Acceptance criteria: Frontend app is setup and generic page layout is complete. | 1.0 | 1.1 Frontend app setup - As a user, I want to be able to launch a frontend app and access a generic layout.
Acceptance criteria: Frontend app is setup and generic page layout is complete. | priority | frontend app setup as a user i want to be able to launch a frontend app and access a generic layout acceptance criteria frontend app is setup and generic page layout is complete | 1 |
213,447 | 7,253,906,743 | IssuesEvent | 2018-02-16 08:45:02 | geoladris/apps | https://api.github.com/repos/geoladris/apps | closed | Make context.xml use system variables | Priority: High Status: In Progress Type: Bug | To configure database access, the file allows system variables (see [example](http://nfms4redd.github.io/documentation/install/docker/context.xml)). Thus, we can configure the database access without having to edit/add any file, just by adding system properties:
```
JAVA_OPTS=-DGEOLADRIS_DB_USER=user -DGEOLADRIS_DB_PASS=pass -DGEOLADRIS_DB_URL=jdbc:postgresql://localhost:5432/nfms
```
Document it [here](https://geoladris.github.io/doc/user/config/). | 1.0 | Make context.xml use system variables - To configure database access, the file allows system variables (see [example](http://nfms4redd.github.io/documentation/install/docker/context.xml)). Thus, we can configure the database access without having to edit/add any file, just by adding system properties:
```
JAVA_OPTS=-DGEOLADRIS_DB_USER=user -DGEOLADRIS_DB_PASS=pass -DGEOLADRIS_DB_URL=jdbc:postgresql://localhost:5432/nfms
```
Document it [here](https://geoladris.github.io/doc/user/config/). | priority | make context xml use system variables to configure database access the file allows system variables see thus we can configure the database access without having to edit add any file just by adding system properties java opts dgeoladris db user user dgeoladris db pass pass dgeoladris db url jdbc postgresql localhost nfms document it | 1 |
585,078 | 17,470,731,518 | IssuesEvent | 2021-08-07 04:39:42 | vignette-project/Akihabara | https://api.github.com/repos/vignette-project/Akihabara | closed | Investigate what is ValueOrFormatException() | good first issue help wanted priority:high | This seems very important, so if anyone who's willing to check the Unity code we're basing at, it would be nice
Might be part of #3 | 1.0 | Investigate what is ValueOrFormatException() - This seems very important, so if anyone who's willing to check the Unity code we're basing at, it would be nice
Might be part of #3 | priority | investigate what is valueorformatexception this seems very important so if anyone who s willing to check the unity code we re basing at it would be nice might be part of | 1 |
692,195 | 23,725,945,195 | IssuesEvent | 2022-08-30 19:37:10 | ml4ai/tomcat | https://api.github.com/repos/ml4ai/tomcat | closed | Correct way to extract .metadata files from testbed | Priority: High | Steps followed to extract metadata files:
1. Goto localhost:8082/dashboard, made sure the testbed is running and metadata-app is online
2. Select logstash-2022.06.03.000004
3. Select the latest trail under UUID
4. Once I hit export I get the message saying '0 documents exported' | 1.0 | Correct way to extract .metadata files from testbed - Steps followed to extract metadata files:
1. Goto localhost:8082/dashboard, made sure the testbed is running and metadata-app is online
2. Select logstash-2022.06.03.000004
3. Select the latest trail under UUID
4. Once I hit export I get the message saying '0 documents exported' | priority | correct way to extract metadata files from testbed steps followed to extract metadata files goto localhost dashboard made sure the testbed is running and metadata app is online select logstash select the latest trail under uuid once i hit export i get the message saying documents exported | 1 |
658,818 | 21,903,299,496 | IssuesEvent | 2022-05-20 15:21:30 | huridocs/uwazi | https://api.github.com/repos/huridocs/uwazi | closed | Relationship values cannot be used as filters when user has no permissions | Bug :lady_beetle: Sprint Priority: High Backend | Consider this scenario:
- a collection has entities of the type "country"
- it also has entities of the type "case"
- "case" has a relationship property pointing to "country"
If an entity of the type "case" has as value a "country" for which my user has no permissions, I won't even see the option available in filters. This is wrong since the filter aggregations should be calculated based on the values of "case" not on the access control of "country". | 1.0 | Relationship values cannot be used as filters when user has no permissions - Consider this scenario:
- a collection has entities of the type "country"
- it also has entities of the type "case"
- "case" has a relationship property pointing to "country"
If an entity of the type "case" has as value a "country" for which my user has no permissions, I won't even see the option available in filters. This is wrong since the filter aggregations should be calculated based on the values of "case" not on the access control of "country". | priority | relationship values cannot be used as filters when user has no permissions consider this scenario a collection has entities of the type country it also has entities of the type case case has a relationship property pointing to country if an entity of the type case has as value a country for which my user has no permissions i won t even see the option available in filters this is wrong since the filter aggregations should be calculated based on the values of case not on the access control of country | 1 |
488,960 | 14,099,949,928 | IssuesEvent | 2020-11-06 02:47:20 | AY2021S1-CS2113T-F14-4/tp | https://api.github.com/repos/AY2021S1-CS2113T-F14-4/tp | opened | allow the user to type FOE FOS etc to give possible choices of Buildings/LTs/labs available there | priority.High task | inspired by team3
this only provides a list | 1.0 | allow the user to type FOE FOS etc to give possible choices of Buildings/LTs/labs available there - inspired by team3
this only provides a list | priority | allow the user to type foe fos etc to give possible choices of buildings lts labs available there inspired by this only provides a list | 1 |
123,474 | 4,863,523,332 | IssuesEvent | 2016-11-14 15:40:36 | Metaswitch/sprout | https://api.github.com/repos/Metaswitch/sprout | closed | IPv6 is generally broken for the S-CSCF sproutlet | bug cat:ipv6 high-priority | If the sprout_hostname is an IPv6 address then the S-CSCF plugin fails to load as the BGCF URI is invalid
Debug scscfsproutlet.cpp:99: BGCF URI = sip:bgcf.[::1]:5054;transport=TCP
Error scscfsproutlet.cpp:125: Invalid BGCF URI sip:bgcf.[::1]:5054;transport=TCP
| 1.0 | IPv6 is generally broken for the S-CSCF sproutlet - If the sprout_hostname is an IPv6 address then the S-CSCF plugin fails to load as the BGCF URI is invalid
Debug scscfsproutlet.cpp:99: BGCF URI = sip:bgcf.[::1]:5054;transport=TCP
Error scscfsproutlet.cpp:125: Invalid BGCF URI sip:bgcf.[::1]:5054;transport=TCP
| priority | is generally broken for the s cscf sproutlet if the sprout hostname is an address then the s cscf plugin fails to load as the bgcf uri is invalid debug scscfsproutlet cpp bgcf uri sip bgcf transport tcp error scscfsproutlet cpp invalid bgcf uri sip bgcf transport tcp | 1 |
730,205 | 25,164,094,080 | IssuesEvent | 2022-11-10 19:12:17 | digett-trs/trs | https://api.github.com/repos/digett-trs/trs | opened | "EST. 2001" text in header doesn't fit | priority-high | 
I think we should just tighten it up a bit, reposition... should be fine with a little adjustment. | 1.0 | "EST. 2001" text in header doesn't fit - 
I think we should just tighten it up a bit, reposition... should be fine with a little adjustment. | priority | est text in header doesn t fit i think we should just tighten it up a bit reposition should be fine with a little adjustment | 1 |
320,789 | 9,789,110,529 | IssuesEvent | 2019-06-10 08:56:57 | ballerina-platform/ballerina-lang | https://api.github.com/repos/ballerina-platform/ballerina-lang | opened | Return error instead of panic when stamping value with cyclic reference | Area/Language Component/Compiler Priority/High Type/Bug | **Description:**
```
type Person record {
string name = "";
int age = 0;
Person? parent = ();
};
Person p = { name: "Waruna", age: 25, parent: () };
Person p2 = { name: "Milinda", age: 25, parent:p };
p.parent = p2;
json|error j = json.stamp(p); // Cyclic value will be check with isLikeType method.
```
json.stamp(p) will be panic but it should be return an error. | 1.0 | Return error instead of panic when stamping value with cyclic reference - **Description:**
```
type Person record {
string name = "";
int age = 0;
Person? parent = ();
};
Person p = { name: "Waruna", age: 25, parent: () };
Person p2 = { name: "Milinda", age: 25, parent:p };
p.parent = p2;
json|error j = json.stamp(p); // Cyclic value will be check with isLikeType method.
```
json.stamp(p) will be panic but it should be return an error. | priority | return error instead of panic when stamping value with cyclic reference description type person record string name int age person parent person p name waruna age parent person name milinda age parent p p parent json error j json stamp p cyclic value will be check with isliketype method json stamp p will be panic but it should be return an error | 1 |
780,404 | 27,393,656,507 | IssuesEvent | 2023-02-28 17:57:33 | flowforge/website | https://api.github.com/repos/flowforge/website | closed | Improve home page performance on mobile devices | task priority:high | ### Story
_No response_
### Description
Google Search Console is reporting flowforge.com home page is too slow on mobile devices. Our performance score is 39/100.
For SEO, Google prioritizes mobile friendly pages so it would be nice to address this.
[Link to the report from Google.](https://pagespeed.web.dev/report?url=https%3A%2F%2Fflowforge.com%2F&utm_source=search_console&form_factor=mobile&hl=en) | 1.0 | Improve home page performance on mobile devices - ### Story
_No response_
### Description
Google Search Console is reporting flowforge.com home page is too slow on mobile devices. Our performance score is 39/100.
For SEO, Google prioritizes mobile friendly pages so it would be nice to address this.
[Link to the report from Google.](https://pagespeed.web.dev/report?url=https%3A%2F%2Fflowforge.com%2F&utm_source=search_console&form_factor=mobile&hl=en) | priority | improve home page performance on mobile devices story no response description google search console is reporting flowforge com home page is too slow on mobile devices our performance score is for seo google prioritizes mobile friendly pages so it would be nice to address this | 1 |
537,836 | 15,755,225,378 | IssuesEvent | 2021-03-31 01:24:13 | myConsciousness/zenna-db | https://api.github.com/repos/myConsciousness/zenna-db | closed | コンテンツオブジェクトのフィールドに任意の型を指定したい | Priority: high Type: new feature | # Add New Feature
## 1. Feature details
現状コンテンツ情報を取得するロジックの関係上コンテンツオブジェクトのフィールドの型はStringのみとなっている。
これを改善し任意の型をフィールドに指定できないか検討する。
## 2. Why it is necessary
任意の型を指定できるようにしたい。
## 3. How to implement
コンテンツオブジェクトへの設定からではなくて、
コンテンツの取得方法から調査する必要がある。
## 4. References
| 1.0 | コンテンツオブジェクトのフィールドに任意の型を指定したい - # Add New Feature
## 1. Feature details
現状コンテンツ情報を取得するロジックの関係上コンテンツオブジェクトのフィールドの型はStringのみとなっている。
これを改善し任意の型をフィールドに指定できないか検討する。
## 2. Why it is necessary
任意の型を指定できるようにしたい。
## 3. How to implement
コンテンツオブジェクトへの設定からではなくて、
コンテンツの取得方法から調査する必要がある。
## 4. References
| priority | コンテンツオブジェクトのフィールドに任意の型を指定したい add new feature feature details 現状コンテンツ情報を取得するロジックの関係上コンテンツオブジェクトのフィールドの型はstringのみとなっている。 これを改善し任意の型をフィールドに指定できないか検討する。 why it is necessary 任意の型を指定できるようにしたい。 how to implement コンテンツオブジェクトへの設定からではなくて、 コンテンツの取得方法から調査する必要がある。 references | 1 |
501,999 | 14,538,016,189 | IssuesEvent | 2020-12-15 09:55:18 | flextype/flextype | https://api.github.com/repos/flextype/flextype | closed | Entries API - clean up and reorganize events | priority: high type: feature | We should have clean events background for Entries API to avoid collisions but with still powerful extensibility.
### Events:
**onEntriesFetchSingle** instead of **_onEntryInitialized_**
**onEntriesFetchSingleCacheHasResult** instead of **_onEntryAfterCacheInitialized_**
**onEntriesFetchSingleNoResult**
**onEntriesFetchSingleHasResult** instead of **_onEntryAfterInitialized_**
**onEntriesFetchCollection** instead of **_onEntriesInitialized_**
**onEntriesFetchCollectionHasResult** instead of **_onEntriesAfterInitialized_**
**onEntriesFetchCollectionNoResult**
**onEntriesMove** instead of **_onEntryMove_**
**onEntriesUpdate** instead of **_onEntryUpdate_**
**onEntriesCreate** instead of **_onEntryCreate_**
**onEntriesDelete** instead of **_onEntryDelete_**
**onEntriesCopy** instead of **_onEntryCopy_**
**onEntriesHas** instead of **_onEntryHas_**
related to #491 | 1.0 | Entries API - clean up and reorganize events - We should have clean events background for Entries API to avoid collisions but with still powerful extensibility.
### Events:
**onEntriesFetchSingle** instead of **_onEntryInitialized_**
**onEntriesFetchSingleCacheHasResult** instead of **_onEntryAfterCacheInitialized_**
**onEntriesFetchSingleNoResult**
**onEntriesFetchSingleHasResult** instead of **_onEntryAfterInitialized_**
**onEntriesFetchCollection** instead of **_onEntriesInitialized_**
**onEntriesFetchCollectionHasResult** instead of **_onEntriesAfterInitialized_**
**onEntriesFetchCollectionNoResult**
**onEntriesMove** instead of **_onEntryMove_**
**onEntriesUpdate** instead of **_onEntryUpdate_**
**onEntriesCreate** instead of **_onEntryCreate_**
**onEntriesDelete** instead of **_onEntryDelete_**
**onEntriesCopy** instead of **_onEntryCopy_**
**onEntriesHas** instead of **_onEntryHas_**
related to #491 | priority | entries api clean up and reorganize events we should have clean events background for entries api to avoid collisions but with still powerful extensibility events onentriesfetchsingle instead of onentryinitialized onentriesfetchsinglecachehasresult instead of onentryaftercacheinitialized onentriesfetchsinglenoresult onentriesfetchsinglehasresult instead of onentryafterinitialized onentriesfetchcollection instead of onentriesinitialized onentriesfetchcollectionhasresult instead of onentriesafterinitialized onentriesfetchcollectionnoresult onentriesmove instead of onentrymove onentriesupdate instead of onentryupdate onentriescreate instead of onentrycreate onentriesdelete instead of onentrydelete onentriescopy instead of onentrycopy onentrieshas instead of onentryhas related to | 1 |
608,191 | 18,817,407,954 | IssuesEvent | 2021-11-10 01:56:48 | boostcampwm-2021/web14-salondesrefuses | https://api.github.com/repos/boostcampwm-2021/web14-salondesrefuses | closed | (높음)[FE] 에디터 초안 - Drag까지 | 🚀 Front Priority: High | ## 📃 이슈 내용
에디터 틀을 띄우고 사각형을 넣는다. 드래그가 된다.
## ✅ 체크 리스트
- [x] 에디터 틀
- [x] 사각형 넣기
- [x] 드래그
## 📌 레퍼런스
| 1.0 | (높음)[FE] 에디터 초안 - Drag까지 - ## 📃 이슈 내용
에디터 틀을 띄우고 사각형을 넣는다. 드래그가 된다.
## ✅ 체크 리스트
- [x] 에디터 틀
- [x] 사각형 넣기
- [x] 드래그
## 📌 레퍼런스
| priority | 높음 에디터 초안 drag까지 📃 이슈 내용 에디터 틀을 띄우고 사각형을 넣는다 드래그가 된다 ✅ 체크 리스트 에디터 틀 사각형 넣기 드래그 📌 레퍼런스 | 1 |
396,732 | 11,713,138,076 | IssuesEvent | 2020-03-09 09:45:54 | onaio/reveal-frontend | https://api.github.com/repos/onaio/reveal-frontend | closed | Refactor ActiveFocusInvestigation | Priority: High has pr | In support of #651, we need to refactor the `ActiveFocusInvestigation` component to work with jurisdictions. i.e. this component should take a jurisdiction id and render that jurisdiction's FI activities. | 1.0 | Refactor ActiveFocusInvestigation - In support of #651, we need to refactor the `ActiveFocusInvestigation` component to work with jurisdictions. i.e. this component should take a jurisdiction id and render that jurisdiction's FI activities. | priority | refactor activefocusinvestigation in support of we need to refactor the activefocusinvestigation component to work with jurisdictions i e this component should take a jurisdiction id and render that jurisdiction s fi activities | 1 |
542,061 | 15,838,076,476 | IssuesEvent | 2021-04-06 21:48:33 | Azure/azure-sdk-for-cpp | https://api.github.com/repos/Azure/azure-sdk-for-cpp | closed | Enable an arm64 windows CI leg to make sure the SDK continues to build for the supported platform | EngSys priority:High | See the supported platform matrix:
https://azure.github.io/azure-sdk/cpp_introduction.html#supported-platforms
We have found one linker issue on arm64-windows already, see https://github.com/Azure/azure-sdk-for-cpp/issues/1367.
This will help us uncover any other issues that need to be fixed and also stay green going forward.
cc @danieljurek, @vhvb1989 | 1.0 | Enable an arm64 windows CI leg to make sure the SDK continues to build for the supported platform - See the supported platform matrix:
https://azure.github.io/azure-sdk/cpp_introduction.html#supported-platforms
We have found one linker issue on arm64-windows already, see https://github.com/Azure/azure-sdk-for-cpp/issues/1367.
This will help us uncover any other issues that need to be fixed and also stay green going forward.
cc @danieljurek, @vhvb1989 | priority | enable an windows ci leg to make sure the sdk continues to build for the supported platform see the supported platform matrix we have found one linker issue on windows already see this will help us uncover any other issues that need to be fixed and also stay green going forward cc danieljurek | 1 |
242,079 | 7,837,898,517 | IssuesEvent | 2018-06-18 08:20:55 | schibsted/account-sdk-android | https://api.github.com/repos/schibsted/account-sdk-android | opened | Crash related to loadingDialog fragment at app launch | Priority: High | ### Summary
Briefly describe the issue. What were you trying to do and what actually happened.
### Environment
- SDK Version:
- SDK Module:
- Android Version:
- Device Info:
### Details
Stack trace, screenshots or any other relevant information
### Steps to reproduce
Please let us know how to reproduce this issue
| 1.0 | Crash related to loadingDialog fragment at app launch - ### Summary
Briefly describe the issue. What were you trying to do and what actually happened.
### Environment
- SDK Version:
- SDK Module:
- Android Version:
- Device Info:
### Details
Stack trace, screenshots or any other relevant information
### Steps to reproduce
Please let us know how to reproduce this issue
| priority | crash related to loadingdialog fragment at app launch summary briefly describe the issue what were you trying to do and what actually happened environment sdk version sdk module android version device info details stack trace screenshots or any other relevant information steps to reproduce please let us know how to reproduce this issue | 1 |
666,884 | 22,390,840,275 | IssuesEvent | 2022-06-17 07:31:10 | admiral-team/admiralui-ios | https://api.github.com/repos/admiral-team/admiralui-ios | closed | [FEATURE] - Ресерч Kotlin MultiPlatform | enhancement high priority | **Описание задачи:**
Изучить особенности работы с Kotlin MultiPlatform
**Фреймворк**
Kotlin MultiPlatform
**Ресурсы:**
Ссылка на макеты или ресурсы...
| 1.0 | [FEATURE] - Ресерч Kotlin MultiPlatform - **Описание задачи:**
Изучить особенности работы с Kotlin MultiPlatform
**Фреймворк**
Kotlin MultiPlatform
**Ресурсы:**
Ссылка на макеты или ресурсы...
| priority | ресерч kotlin multiplatform описание задачи изучить особенности работы с kotlin multiplatform фреймворк kotlin multiplatform ресурсы ссылка на макеты или ресурсы | 1 |
337,487 | 10,218,668,001 | IssuesEvent | 2019-08-15 16:31:02 | balena-io/balena-supervisor | https://api.github.com/repos/balena-io/balena-supervisor | opened | Add a download lock in addition to the update lock | High priority type/enhancement | This would control whether the device will start downloading an image, whereas update lock controls whether a device should install an update. | 1.0 | Add a download lock in addition to the update lock - This would control whether the device will start downloading an image, whereas update lock controls whether a device should install an update. | priority | add a download lock in addition to the update lock this would control whether the device will start downloading an image whereas update lock controls whether a device should install an update | 1 |
146,870 | 5,629,753,317 | IssuesEvent | 2017-04-05 10:15:25 | Kademi/kademi-dev | https://api.github.com/repos/Kademi/kademi-dev | closed | Add language selection to menu component | High priority | Extension to
- https://github.com/Kademi/kademi-dev/issues/3073
- https://github.com/Kademi/kademi-dev/issues/3069#issuecomment-290903692
Front end websites need to allow users to select a language, please add a setting to component config to allow display of language selector, and to display languages from TranslationService.getLanguages if selected. When selected should be recorded in a cookie, the same as for the admin.
| 1.0 | Add language selection to menu component - Extension to
- https://github.com/Kademi/kademi-dev/issues/3073
- https://github.com/Kademi/kademi-dev/issues/3069#issuecomment-290903692
Front end websites need to allow users to select a language, please add a setting to component config to allow display of language selector, and to display languages from TranslationService.getLanguages if selected. When selected should be recorded in a cookie, the same as for the admin.
| priority | add language selection to menu component extension to front end websites need to allow users to select a language please add a setting to component config to allow display of language selector and to display languages from translationservice getlanguages if selected when selected should be recorded in a cookie the same as for the admin | 1 |
719,377 | 24,757,789,449 | IssuesEvent | 2022-10-21 19:37:37 | xsuite/xsuite | https://api.github.com/repos/xsuite/xsuite | closed | Warning not showing | bug High priority | This wanrning does nor appear in ipython:
https://github.com/xsuite/xpart/blob/e89c0bec09eb3f6326431e253a2afb54d12b5945/xpart/build_particles.py#L139
You can use this example to test:
https://github.com/xsuite/xpart/blob/main/examples/particles_generation/001c_build_particles_normalized.py
| 1.0 | Warning not showing - This wanrning does nor appear in ipython:
https://github.com/xsuite/xpart/blob/e89c0bec09eb3f6326431e253a2afb54d12b5945/xpart/build_particles.py#L139
You can use this example to test:
https://github.com/xsuite/xpart/blob/main/examples/particles_generation/001c_build_particles_normalized.py
| priority | warning not showing this wanrning does nor appear in ipython you can use this example to test | 1 |
715,774 | 24,609,288,780 | IssuesEvent | 2022-10-14 19:31:20 | cryostatio/cryostat-operator | https://api.github.com/repos/cryostatio/cryostat-operator | closed | Add CR property to disable Cryostat built-in discovery mechanisms | good first issue feat high-priority | The environment variable `CRYOSTAT_DISABLE_BUILTIN_DISCOVERY` can be set to `true` on the Cryostat container to disable the built-in discovery mechanisms. In an Operator context this would mean disabling Cryostat's `Endpoints` querying/watch. This would be used in cases where the end user only intends to have applications discovered via the Discovery Plugin API. | 1.0 | Add CR property to disable Cryostat built-in discovery mechanisms - The environment variable `CRYOSTAT_DISABLE_BUILTIN_DISCOVERY` can be set to `true` on the Cryostat container to disable the built-in discovery mechanisms. In an Operator context this would mean disabling Cryostat's `Endpoints` querying/watch. This would be used in cases where the end user only intends to have applications discovered via the Discovery Plugin API. | priority | add cr property to disable cryostat built in discovery mechanisms the environment variable cryostat disable builtin discovery can be set to true on the cryostat container to disable the built in discovery mechanisms in an operator context this would mean disabling cryostat s endpoints querying watch this would be used in cases where the end user only intends to have applications discovered via the discovery plugin api | 1 |
457,267 | 13,153,933,810 | IssuesEvent | 2020-08-10 05:20:20 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | m.animeflv.net - desktop site instead of mobile site | browser-firefox-mobile engine-gecko ml-needsdiagnosis-false ml-probability-high priority-important | <!-- @browser: Firefox Mobile 79.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:79.0) Gecko/79.0 Firefox/79.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/56356 -->
**URL**: https://m.animeflv.net/ver/log-horizon-2-14
**Browser / Version**: Firefox Mobile 79.0
**Operating System**: Android
**Tested Another Browser**: Yes Edge
**Problem type**: Desktop site instead of mobile site
**Description**: Desktop site instead of mobile site
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200717001501</li><li>channel: beta</li><li>hasTouchScreen: true</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | m.animeflv.net - desktop site instead of mobile site - <!-- @browser: Firefox Mobile 79.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:79.0) Gecko/79.0 Firefox/79.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/56356 -->
**URL**: https://m.animeflv.net/ver/log-horizon-2-14
**Browser / Version**: Firefox Mobile 79.0
**Operating System**: Android
**Tested Another Browser**: Yes Edge
**Problem type**: Desktop site instead of mobile site
**Description**: Desktop site instead of mobile site
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200717001501</li><li>channel: beta</li><li>hasTouchScreen: true</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | m animeflv net desktop site instead of mobile site url browser version firefox mobile operating system android tested another browser yes edge problem type desktop site instead of mobile site description desktop site instead of mobile site steps to reproduce browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true from with ❤️ | 1 |
716,827 | 24,649,612,771 | IssuesEvent | 2022-10-17 17:29:24 | KinsonDigital/Velaptor | https://api.github.com/repos/KinsonDigital/Velaptor | opened | 🔬Multi-OS execution and publishing | high priority 🔬research | ### Complete The Item Below
- [X] I have updated the title without removing the 🔬 emoji.
### What To Research
The application is getting closer and closer to the reality of needing to be executed and tested in other operating systems other then **Windows.** Due to this, there are complexities that need to be dealt with such as builds, executing unit tests, and distributing the correct binaries with each OS.
All of these things need to be figured out.
This issue will do the proper research to handle these areas.
---
### **Scenario 1**
Research into how **Visual Studio Community** and **JetBrains Rider** can be set up to be able to publish, build, execute unit tests, and run the application remotely into **WSL** for running the application.
- **Visual Studio Community**
- This can indeed do remote development, but I have never done this before. Research this to see what is available and also how to do it.
- **JetBrains Rider**
- This has a **Remove Development** capability that could be utilized to do this. It is currently in beta but requires that Linux is setup for SSH for it to work. There are websites and **Rider** documentation about the subject.
### **Scenario 2**
Another way that this could possibly be done is by using **PowerShell**. This is what can be used if the IDEs cannot accomplish what is needed. **PowerShell** is not only cross-platform but can provide much more control over the process.
If none of the IDEs can provide what is needed, then this is the alternative.
**Things To Consider:**
- The scripts should have all of the pathing done relative to the path of the script itself.
- A build will need to be executed
- Restoring packages will have to be performed
- Running the publish will have to be done for each configuration type
- Input parameters to the script will need to be constructed for choosing which type of configuration/publish to perform.
- When dealing with **WSL**, building and copying the build and or project to the **WSL** side is slow and not ideal. Instead, simply use GIT to get the latest code before building.
- This means that work will need to be done to make sure that no staged or unstaged items are in progress
- Authentication to pull down the repo needs to be considered. This means making sure that storing those credentials securely is taken into account.
- The following configurations need to be set up and work
- Debug
- Debug-Console
- Release
- Release-Console
**Purpose:**
This publishing will be required when needing to easily publish different configurations for windows and Linux as things progress into the future. For example, the Linux version of the publish can be performed on windows inside of WSL for testing purposes as well. Remote development can be done with **JetBrains Rider** and probably **Visual Studio**, but having those both setup and working for all environments is not only
### Research Results
_No response_
### Acceptance Criteria
**This issue is finished when:**
- [ ] Research complete and issues created _(if needed)_.
- [ ] If any issues were created, they have been added to the _**Related Work**_ section below.
### ToDo Items
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct. | 1.0 | 🔬Multi-OS execution and publishing - ### Complete The Item Below
- [X] I have updated the title without removing the 🔬 emoji.
### What To Research
The application is getting closer and closer to the reality of needing to be executed and tested in other operating systems other then **Windows.** Due to this, there are complexities that need to be dealt with such as builds, executing unit tests, and distributing the correct binaries with each OS.
All of these things need to be figured out.
This issue will do the proper research to handle these areas.
---
### **Scenario 1**
Research into how **Visual Studio Community** and **JetBrains Rider** can be set up to be able to publish, build, execute unit tests, and run the application remotely into **WSL** for running the application.
- **Visual Studio Community**
- This can indeed do remote development, but I have never done this before. Research this to see what is available and also how to do it.
- **JetBrains Rider**
- This has a **Remove Development** capability that could be utilized to do this. It is currently in beta but requires that Linux is setup for SSH for it to work. There are websites and **Rider** documentation about the subject.
### **Scenario 2**
Another way that this could possibly be done is by using **PowerShell**. This is what can be used if the IDEs cannot accomplish what is needed. **PowerShell** is not only cross-platform but can provide much more control over the process.
If none of the IDEs can provide what is needed, then this is the alternative.
**Things To Consider:**
- The scripts should have all of the pathing done relative to the path of the script itself.
- A build will need to be executed
- Restoring packages will have to be performed
- Running the publish will have to be done for each configuration type
- Input parameters to the script will need to be constructed for choosing which type of configuration/publish to perform.
- When dealing with **WSL**, building and copying the build and or project to the **WSL** side is slow and not ideal. Instead, simply use GIT to get the latest code before building.
- This means that work will need to be done to make sure that no staged or unstaged items are in progress
- Authentication to pull down the repo needs to be considered. This means making sure that storing those credentials securely is taken into account.
- The following configurations need to be set up and work
- Debug
- Debug-Console
- Release
- Release-Console
**Purpose:**
This publishing will be required when needing to easily publish different configurations for windows and Linux as things progress into the future. For example, the Linux version of the publish can be performed on windows inside of WSL for testing purposes as well. Remote development can be done with **JetBrains Rider** and probably **Visual Studio**, but having those both setup and working for all environments is not only
### Research Results
_No response_
### Acceptance Criteria
**This issue is finished when:**
- [ ] Research complete and issues created _(if needed)_.
- [ ] If any issues were created, they have been added to the _**Related Work**_ section below.
### ToDo Items
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct. | priority | 🔬multi os execution and publishing complete the item below i have updated the title without removing the 🔬 emoji what to research the application is getting closer and closer to the reality of needing to be executed and tested in other operating systems other then windows due to this there are complexities that need to be dealt with such as builds executing unit tests and distributing the correct binaries with each os all of these things need to be figured out this issue will do the proper research to handle these areas scenario research into how visual studio community and jetbrains rider can be set up to be able to publish build execute unit tests and run the application remotely into wsl for running the application visual studio community this can indeed do remote development but i have never done this before research this to see what is available and also how to do it jetbrains rider this has a remove development capability that could be utilized to do this it is currently in beta but requires that linux is setup for ssh for it to work there are websites and rider documentation about the subject scenario another way that this could possibly be done is by using powershell this is what can be used if the ides cannot accomplish what is needed powershell is not only cross platform but can provide much more control over the process if none of the ides can provide what is needed then this is the alternative things to consider the scripts should have all of the pathing done relative to the path of the script itself a build will need to be executed restoring packages will have to be performed running the publish will have to be done for each configuration type input parameters to the script will need to be constructed for choosing which type of configuration publish to perform when dealing with wsl building and copying the build and or project to the wsl side is slow and not ideal instead simply use git to get the latest code before building this means that work will need to be done to make sure that no staged or unstaged items are in progress authentication to pull down the repo needs to be considered this means making sure that storing those credentials securely is taken into account the following configurations need to be set up and work debug debug console release release console purpose this publishing will be required when needing to easily publish different configurations for windows and linux as things progress into the future for example the linux version of the publish can be performed on windows inside of wsl for testing purposes as well remote development can be done with jetbrains rider and probably visual studio but having those both setup and working for all environments is not only research results no response acceptance criteria this issue is finished when research complete and issues created if needed if any issues were created they have been added to the related work section below todo items priority label added to this issue refer to the priority type labels section below issue linked to the correct project issue dependencies no response related work no response additional information priority type labels priority type label low priority low priority medium priority medium priority high priority high priority code of conduct i agree to follow this project s code of conduct | 1 |
619,129 | 19,517,151,913 | IssuesEvent | 2021-12-29 12:14:47 | skycocker/chromebrew | https://api.github.com/repos/skycocker/chromebrew | closed | flags now added to make prevent builds from succeeding | bug high priority | Trying to do a new build of ruby I get this:
```
ruby failed to build: `make -j4 DESTDIR=/usr/local/tmp/crew/dest install` exited with 127
/usr/local/lib/crew/lib/package.rb:195:in `system': No such file or directory - make -j4
```
This is happening from an invocation of `system 'make'`
@supechicken Thoughts? | 1.0 | flags now added to make prevent builds from succeeding - Trying to do a new build of ruby I get this:
```
ruby failed to build: `make -j4 DESTDIR=/usr/local/tmp/crew/dest install` exited with 127
/usr/local/lib/crew/lib/package.rb:195:in `system': No such file or directory - make -j4
```
This is happening from an invocation of `system 'make'`
@supechicken Thoughts? | priority | flags now added to make prevent builds from succeeding trying to do a new build of ruby i get this ruby failed to build make destdir usr local tmp crew dest install exited with usr local lib crew lib package rb in system no such file or directory make this is happening from an invocation of system make supechicken thoughts | 1 |
405,444 | 11,873,352,582 | IssuesEvent | 2020-03-26 17:10:18 | dmwm/WMCore | https://api.github.com/repos/dmwm/WMCore | closed | MS: send notification/email on large data transfers (100TB ?) | High Priority New Feature ReqMgr2MS | **Impact of the new feature**
ReqMgr2MS
**Is your feature request related to a problem? Please describe.**
Not related to a current problem, but perhaps a future one.
Once we enable MicroServices for input data placement, it could be that a campaign/workflow missconfigured would trigger unnecessary data transfers. I'm especially concerned about the pileup dataset, which gets replicated as a whole.
**Describe the solution you'd like**
My suggestion is to use the email module Erik has implemented a few months ago and send out a notification (with the phedex transfer ID) every time we have a large data placement made by microservices. In addition, for such cases we might want to not auto-approve such requests, at least for the first month of this service in production.
In more details:
* any data transfer above 100 TB (more? less?). Ideally a configurable parameter.
* do not auto-approve phedex requests
* send an email to ...workflow-team egroup?
* make a special record in the logs
**Describe alternatives you've considered**
none
**Additional context**
none
| 1.0 | MS: send notification/email on large data transfers (100TB ?) - **Impact of the new feature**
ReqMgr2MS
**Is your feature request related to a problem? Please describe.**
Not related to a current problem, but perhaps a future one.
Once we enable MicroServices for input data placement, it could be that a campaign/workflow missconfigured would trigger unnecessary data transfers. I'm especially concerned about the pileup dataset, which gets replicated as a whole.
**Describe the solution you'd like**
My suggestion is to use the email module Erik has implemented a few months ago and send out a notification (with the phedex transfer ID) every time we have a large data placement made by microservices. In addition, for such cases we might want to not auto-approve such requests, at least for the first month of this service in production.
In more details:
* any data transfer above 100 TB (more? less?). Ideally a configurable parameter.
* do not auto-approve phedex requests
* send an email to ...workflow-team egroup?
* make a special record in the logs
**Describe alternatives you've considered**
none
**Additional context**
none
| priority | ms send notification email on large data transfers impact of the new feature is your feature request related to a problem please describe not related to a current problem but perhaps a future one once we enable microservices for input data placement it could be that a campaign workflow missconfigured would trigger unnecessary data transfers i m especially concerned about the pileup dataset which gets replicated as a whole describe the solution you d like my suggestion is to use the email module erik has implemented a few months ago and send out a notification with the phedex transfer id every time we have a large data placement made by microservices in addition for such cases we might want to not auto approve such requests at least for the first month of this service in production in more details any data transfer above tb more less ideally a configurable parameter do not auto approve phedex requests send an email to workflow team egroup make a special record in the logs describe alternatives you ve considered none additional context none | 1 |
67,477 | 3,274,208,018 | IssuesEvent | 2015-10-26 09:38:54 | tgstation/-tg-station | https://api.github.com/repos/tgstation/-tg-station | closed | Some steal objectives are broken | Bug Priority: High | 9d2e1ffafdc8fbcd4b566e5766b758ada702fe25
Steal objectives with additional checks will never run those checks and therefore greentext when they shouldn't. So if you need to steal a full plasma tank, an empty tank would work just as well. Or an empty intelliCard if you need to steal an AI. | 1.0 | Some steal objectives are broken - 9d2e1ffafdc8fbcd4b566e5766b758ada702fe25
Steal objectives with additional checks will never run those checks and therefore greentext when they shouldn't. So if you need to steal a full plasma tank, an empty tank would work just as well. Or an empty intelliCard if you need to steal an AI. | priority | some steal objectives are broken steal objectives with additional checks will never run those checks and therefore greentext when they shouldn t so if you need to steal a full plasma tank an empty tank would work just as well or an empty intellicard if you need to steal an ai | 1 |
490,384 | 14,118,825,277 | IssuesEvent | 2020-11-08 15:14:55 | AY2021S1-CS2113T-F14-2/tp | https://api.github.com/repos/AY2021S1-CS2113T-F14-2/tp | closed | need to adjust spending list output format | priority.High | it's better to sort spending list according to date | 1.0 | need to adjust spending list output format - it's better to sort spending list according to date | priority | need to adjust spending list output format it s better to sort spending list according to date | 1 |
488,038 | 14,073,876,626 | IssuesEvent | 2020-11-04 06:05:21 | tikv/tikv | https://api.github.com/repos/tikv/tikv | closed | raftstore::test_tombstone::test_server_readd_peer response header { error { message: "peer is not leader for region 1, leader may None" not_leader { region_id: 1 } } } has error | priority/high severity/Major sig/raft type/bug | ## Bug Report
### What version of TiKV are you using?
This tikv source 7cbf045bb6bf7255ddedd44e76beba98efedd2e6
### What operating system and CPU are you using?
```
processor : 39
vendor_id : GenuineIntel
cpu family : 6
model : 79
model name : Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
stepping : 1
microcode : 0xb00001f
cpu MHz : 2400.341
cache size : 25600 KB
physical id : 1
siblings : 20
core id : 12
cpu cores : 10
apicid : 57
initial apicid : 57
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts
bogomips : 4399.40
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
```
```
Linux version 3.10.0-862.14.4.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Wed Sep 26 15:12:11 UTC 2018
```
### Steps to reproduce
I run `cargo test --all` in `tikv/` dir(the root dir of tikv project).
And it report this error
```
failures:
---- raftstore::test_tombstone::test_server_readd_peer stdout ----
thread 'raftstore::test_tombstone::test_server_readd_peer' panicked at 'response header { error { message: "peer is not leader for region 1, leader may None" not_leader { region_id: 1 } } } has error', components/test_raftstore/src/cluster.rs:682:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
failures:
raftstore::test_tombstone::test_server_readd_peer
```
However, when I run it one more time, there is no this failure, so I can not get the full backtrace.
| 1.0 | raftstore::test_tombstone::test_server_readd_peer response header { error { message: "peer is not leader for region 1, leader may None" not_leader { region_id: 1 } } } has error - ## Bug Report
### What version of TiKV are you using?
This tikv source 7cbf045bb6bf7255ddedd44e76beba98efedd2e6
### What operating system and CPU are you using?
```
processor : 39
vendor_id : GenuineIntel
cpu family : 6
model : 79
model name : Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
stepping : 1
microcode : 0xb00001f
cpu MHz : 2400.341
cache size : 25600 KB
physical id : 1
siblings : 20
core id : 12
cpu cores : 10
apicid : 57
initial apicid : 57
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts
bogomips : 4399.40
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
```
```
Linux version 3.10.0-862.14.4.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Wed Sep 26 15:12:11 UTC 2018
```
### Steps to reproduce
I run `cargo test --all` in `tikv/` dir(the root dir of tikv project).
And it report this error
```
failures:
---- raftstore::test_tombstone::test_server_readd_peer stdout ----
thread 'raftstore::test_tombstone::test_server_readd_peer' panicked at 'response header { error { message: "peer is not leader for region 1, leader may None" not_leader { region_id: 1 } } } has error', components/test_raftstore/src/cluster.rs:682:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
failures:
raftstore::test_tombstone::test_server_readd_peer
```
However, when I run it one more time, there is no this failure, so I can not get the full backtrace.
| priority | raftstore test tombstone test server readd peer response header error message peer is not leader for region leader may none not leader region id has error bug report what version of tikv are you using this tikv source what operating system and cpu are you using processor vendor id genuineintel cpu family model model name intel r xeon r cpu stepping microcode cpu mhz cache size kb physical id siblings core id cpu cores apicid initial apicid fpu yes fpu exception yes cpuid level wp yes flags fpu vme de pse tsc msr pae mce apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse ss ht tm pbe syscall nx rdtscp lm constant tsc arch perfmon pebs bts rep good nopl xtopology nonstop tsc aperfmperf eagerfpu pni pclmulqdq monitor ds cpl vmx smx est sdbg fma xtpr pdcm pcid dca movbe popcnt aes xsave avx rdrand lahf lm abm epb cat cdp intel pt tpr shadow vnmi flexpriority ept vpid fsgsbase tsc adjust hle smep erms invpcid rtm cqm rdt a rdseed adx smap xsaveopt cqm llc cqm occup llc cqm mbm total cqm mbm local dtherm ida arat pln pts bogomips clflush size cache alignment address sizes bits physical bits virtual power management linux version mockbuild kbuilder bsys centos org gcc version red hat gcc smp wed sep utc steps to reproduce i run cargo test all in tikv dir the root dir of tikv project and it report this error failures raftstore test tombstone test server readd peer stdout thread raftstore test tombstone test server readd peer panicked at response header error message peer is not leader for region leader may none not leader region id has error components test raftstore src cluster rs note run with rust backtrace environment variable to display a backtrace failures raftstore test tombstone test server readd peer however when i run it one more time there is no this failure so i can not get the full backtrace | 1 |
631,589 | 20,155,726,881 | IssuesEvent | 2022-02-09 16:17:24 | ctm/mb2-doc | https://api.github.com/repos/ctm/mb2-doc | closed | rare connection error | bug high priority | Find and fix the `ErrorImpl` error.
Every once in a while I'm seeing an error in the logs that suggests the wrong type of packet is being sent from the lobby.
> 2022-01-27T17:04:24.903014330Z WARN [mb2] NewConnection: ErrorImpl { code: Message("invalid value: integer `12`, expected variant index 0 <= i < 6"), offset: 0 }
2022-01-27T17:04:24.903057561Z WARN [mb2] NewConnection: ErrorImpl { code: Message("invalid value: integer `12`, expected variant index 0 <= i < 6"), offset: 0 }
The first time I noticed this was January 18th and I [mentioned it in a comment](https://github.com/ctm/mb2-doc/issues/812#issuecomment-1015609555) on another issue. It's happened a few times since. The two above are the most recent ones.
Internally we use two different types of messages when the lobby is talking to the server. The first request is done as a `FirstRequest` and everything else is done as a `Lobby` request. The error that I'm seeing suggests that for some reason the client is sending a `Lobby` request where the server expects a `FirstRequest`. So, to track this down, I'll make it so that if we see an error decoding a `FirstRequest`, we'll try to decode it as a `Lobby` request and if that succeeds, we'll record which `Lobby` request it is. Assuming it decodes, that should help me track down what's going on. | 1.0 | rare connection error - Find and fix the `ErrorImpl` error.
Every once in a while I'm seeing an error in the logs that suggests the wrong type of packet is being sent from the lobby.
> 2022-01-27T17:04:24.903014330Z WARN [mb2] NewConnection: ErrorImpl { code: Message("invalid value: integer `12`, expected variant index 0 <= i < 6"), offset: 0 }
2022-01-27T17:04:24.903057561Z WARN [mb2] NewConnection: ErrorImpl { code: Message("invalid value: integer `12`, expected variant index 0 <= i < 6"), offset: 0 }
The first time I noticed this was January 18th and I [mentioned it in a comment](https://github.com/ctm/mb2-doc/issues/812#issuecomment-1015609555) on another issue. It's happened a few times since. The two above are the most recent ones.
Internally we use two different types of messages when the lobby is talking to the server. The first request is done as a `FirstRequest` and everything else is done as a `Lobby` request. The error that I'm seeing suggests that for some reason the client is sending a `Lobby` request where the server expects a `FirstRequest`. So, to track this down, I'll make it so that if we see an error decoding a `FirstRequest`, we'll try to decode it as a `Lobby` request and if that succeeds, we'll record which `Lobby` request it is. Assuming it decodes, that should help me track down what's going on. | priority | rare connection error find and fix the errorimpl error every once in a while i m seeing an error in the logs that suggests the wrong type of packet is being sent from the lobby warn newconnection errorimpl code message invalid value integer expected variant index i offset warn newconnection errorimpl code message invalid value integer expected variant index i offset the first time i noticed this was january and i on another issue it s happened a few times since the two above are the most recent ones internally we use two different types of messages when the lobby is talking to the server the first request is done as a firstrequest and everything else is done as a lobby request the error that i m seeing suggests that for some reason the client is sending a lobby request where the server expects a firstrequest so to track this down i ll make it so that if we see an error decoding a firstrequest we ll try to decode it as a lobby request and if that succeeds we ll record which lobby request it is assuming it decodes that should help me track down what s going on | 1 |
649,069 | 21,217,195,150 | IssuesEvent | 2022-04-11 08:31:09 | microsoftgraph/microsoft-graph-explorer-v4 | https://api.github.com/repos/microsoftgraph/microsoft-graph-explorer-v4 | opened | [Header Area] Add settings icon | Priority: High Header area | As a user,
When I’m on the header area
I would like to see a settings icon
**Acceptance Criteria**
- Responsive design
- Accessibility
- Telemetry: measure clicks on icon to access feature usability
**Design**
Please refer to figma file for design requirements
| 1.0 | [Header Area] Add settings icon - As a user,
When I’m on the header area
I would like to see a settings icon
**Acceptance Criteria**
- Responsive design
- Accessibility
- Telemetry: measure clicks on icon to access feature usability
**Design**
Please refer to figma file for design requirements
| priority | add settings icon as a user when i’m on the header area i would like to see a settings icon acceptance criteria responsive design accessibility telemetry measure clicks on icon to access feature usability design please refer to figma file for design requirements | 1 |
345,237 | 10,354,702,085 | IssuesEvent | 2019-09-05 14:14:50 | vuejs/vuepress | https://api.github.com/repos/vuejs/vuepress | closed | TypeError: Cannot assign to read only property 'exports' of object '#<Object>' | priority: high type: bug | ## Bug report
#### Steps to reproduce
1. vue create some-project
2. yarn add -D vuepress
3. vuepress dev docs
4. open chrome devtool，you can see console:
``` jaavascript
vue.runtime.esm.js?2b0e:619 [Vue warn]: Failed to resolve async component: function Layout() {
return __webpack_require__.e(/*! import() */ 0).then(__webpack_require__.bind(null, /*! ./node_modules/@vuepress/theme-default/layouts/Layout.vue */ "./node_modules/@vuepress/theme-default/layouts/Layout.vue"));
}
Reason: TypeError: Cannot assign to read only property 'exports' of object '#<Object>'
```
5. vuepress build docs，you can see shell:
``` shell
(undefined) ./node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus& (./node_modules/mini-css-extract-plugin/dist/loader.js!./node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--13-oneOf-1-2!./node_modules/stylus-loader??ref--13-oneOf-1-3!./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&)
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
TypeError: Cannot assign to read only property 'exports' of object '#<Object>'
at Module.<anonymous> (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:453:16)
at Module.module.exports.module.exports (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:471:30)
at __webpack_require__ (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:21:30)
at Object.module.exports.module.exports (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:342:17)
at __webpack_require__ (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:21:30)
at /Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:85:18
at Object.<anonymous> (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:88:10)
at Module._compile (internal/modules/cjs/loader.js:688:30)
at exec (/Users/yuistack/Documents/Test/test-press/node_modules/mini-css-extract-plugin/dist/loader.js:58:10)
at childCompiler.runAsChild (/Users/yuistack/Documents/Test/test-press/node_modules/mini-css-extract-plugin/dist/loader.js:151:14)
at compile (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:343:11)
at hooks.afterCompile.callAsync.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:671:15)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)
at AsyncSeriesHook.lazyCompileHook (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:668:31)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
@ ./node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus& 1:0-435 1:451-454 1:456-888 1:456-888
@ ./node_modules/@vuepress/plugin-search/SearchBox.vue
@ ./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--3-0!./node_modules/babel-loader/lib??ref--3-1!./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@vuepress/theme-default/components/Navbar.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/components/Navbar.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/components/Navbar.vue
@ ./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--3-0!./node_modules/babel-loader/lib??ref--3-1!./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@vuepress/theme-default/layouts/Layout.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/layouts/Layout.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/layouts/Layout.vue
@ ./node_modules/@vuepress/core/.temp/internal/layout-components.js
@ ./node_modules/@vuepress/core/lib/client/util.js
@ ./node_modules/@vuepress/core/lib/client/app.js
@ ./node_modules/@vuepress/core/lib/client/clientEntry.js
@ multi ./node_modules/@vuepress/core/lib/client/clientEntry.js
Error: Failed to compile with errors.
at webpack (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/lib/node/build/index.js:186:16)
at finalCallback (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:254:12)
at runWithDependencies.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:277:6)
at done (/Users/yuistack/Documents/Test/test-press/node_modules/neo-async/async.js:2931:13)
at runCompilers (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:181:48)
at err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:188:7)
at compiler.run (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:270:7)
at finalCallback (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:257:39)
at hooks.done.callAsync.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:273:13)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:33:1)
at AsyncSeriesHook.lazyCompileHook (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:271:21)
at hooks.afterCompile.callAsync.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:671:15)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:668:31)
npm ERR! code ELIFECYCLE
```
6. about repo：[vuepress-bug-report](https://github.com/falstack/vuepress-bug-report)
#### What is expected?
vuepress can work with vue-cli
#### What is actually happening?
vuepress can't work with vue-cli
#### Other relevant information
``` shell
Environment Info:
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Binaries:
Node: 10.13.0 - ~/.nvm/versions/node/v10.13.0/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.10.2 - ~/.nvm/versions/node/v10.13.0/bin/npm
Browsers:
Chrome: 75.0.3770.142
Firefox: 67.0.2
Safari: 12.1.1
npmPackages:
@vuepress/core: 1.0.3
@vuepress/theme-default: 1.0.3
vuepress: ^1.0.3 => 1.0.3
npmGlobalPackages:
vuepress: Not Found
```
vue-cli version：`3.1.0`
| 1.0 | TypeError: Cannot assign to read only property 'exports' of object '#<Object>' - ## Bug report
#### Steps to reproduce
1. vue create some-project
2. yarn add -D vuepress
3. vuepress dev docs
4. open chrome devtool，you can see console:
``` jaavascript
vue.runtime.esm.js?2b0e:619 [Vue warn]: Failed to resolve async component: function Layout() {
return __webpack_require__.e(/*! import() */ 0).then(__webpack_require__.bind(null, /*! ./node_modules/@vuepress/theme-default/layouts/Layout.vue */ "./node_modules/@vuepress/theme-default/layouts/Layout.vue"));
}
Reason: TypeError: Cannot assign to read only property 'exports' of object '#<Object>'
```
5. vuepress build docs，you can see shell:
``` shell
(undefined) ./node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus& (./node_modules/mini-css-extract-plugin/dist/loader.js!./node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--13-oneOf-1-2!./node_modules/stylus-loader??ref--13-oneOf-1-3!./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&)
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
TypeError: Cannot assign to read only property 'exports' of object '#<Object>'
at Module.<anonymous> (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:453:16)
at Module.module.exports.module.exports (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:471:30)
at __webpack_require__ (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:21:30)
at Object.module.exports.module.exports (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:342:17)
at __webpack_require__ (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:21:30)
at /Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:85:18
at Object.<anonymous> (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/css-loader/dist/cjs.js??ref--13-oneOf-1-1!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/loaders/stylePostLoader.js!/Users/yuistack/Documents/Test/test-press/node_modules/postcss-loader/src/index.js??ref--13-oneOf-1-2!/Users/yuistack/Documents/Test/test-press/node_modules/stylus-loader/index.js??ref--13-oneOf-1-3!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!/Users/yuistack/Documents/Test/test-press/node_modules/vue-loader/lib/index.js??vue-loader-options!/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus&:88:10)
at Module._compile (internal/modules/cjs/loader.js:688:30)
at exec (/Users/yuistack/Documents/Test/test-press/node_modules/mini-css-extract-plugin/dist/loader.js:58:10)
at childCompiler.runAsChild (/Users/yuistack/Documents/Test/test-press/node_modules/mini-css-extract-plugin/dist/loader.js:151:14)
at compile (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:343:11)
at hooks.afterCompile.callAsync.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:671:15)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)
at AsyncSeriesHook.lazyCompileHook (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:668:31)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
@ ./node_modules/@vuepress/plugin-search/SearchBox.vue?vue&type=style&index=0&lang=stylus& 1:0-435 1:451-454 1:456-888 1:456-888
@ ./node_modules/@vuepress/plugin-search/SearchBox.vue
@ ./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--3-0!./node_modules/babel-loader/lib??ref--3-1!./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@vuepress/theme-default/components/Navbar.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/components/Navbar.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/components/Navbar.vue
@ ./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--3-0!./node_modules/babel-loader/lib??ref--3-1!./node_modules/@vuepress/core/node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@vuepress/theme-default/layouts/Layout.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/layouts/Layout.vue?vue&type=script&lang=js&
@ ./node_modules/@vuepress/theme-default/layouts/Layout.vue
@ ./node_modules/@vuepress/core/.temp/internal/layout-components.js
@ ./node_modules/@vuepress/core/lib/client/util.js
@ ./node_modules/@vuepress/core/lib/client/app.js
@ ./node_modules/@vuepress/core/lib/client/clientEntry.js
@ multi ./node_modules/@vuepress/core/lib/client/clientEntry.js
Error: Failed to compile with errors.
at webpack (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/lib/node/build/index.js:186:16)
at finalCallback (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:254:12)
at runWithDependencies.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:277:6)
at done (/Users/yuistack/Documents/Test/test-press/node_modules/neo-async/async.js:2931:13)
at runCompilers (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:181:48)
at err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:188:7)
at compiler.run (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/MultiCompiler.js:270:7)
at finalCallback (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:257:39)
at hooks.done.callAsync.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:273:13)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:33:1)
at AsyncSeriesHook.lazyCompileHook (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:271:21)
at hooks.afterCompile.callAsync.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:671:15)
at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
at AsyncSeriesHook.lazyCompileHook (/Users/yuistack/Documents/Test/test-press/node_modules/tapable/lib/Hook.js:154:20)
at compilation.seal.err (/Users/yuistack/Documents/Test/test-press/node_modules/@vuepress/core/node_modules/webpack/lib/Compiler.js:668:31)
npm ERR! code ELIFECYCLE
```
6. about repo：[vuepress-bug-report](https://github.com/falstack/vuepress-bug-report)
#### What is expected?
vuepress can work with vue-cli
#### What is actually happening?
vuepress can't work with vue-cli
#### Other relevant information
``` shell
Environment Info:
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Binaries:
Node: 10.13.0 - ~/.nvm/versions/node/v10.13.0/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.10.2 - ~/.nvm/versions/node/v10.13.0/bin/npm
Browsers:
Chrome: 75.0.3770.142
Firefox: 67.0.2
Safari: 12.1.1
npmPackages:
@vuepress/core: 1.0.3
@vuepress/theme-default: 1.0.3
vuepress: ^1.0.3 => 1.0.3
npmGlobalPackages:
vuepress: Not Found
```
vue-cli version：`3.1.0`
| priority | typeerror cannot assign to read only property exports of object bug report steps to reproduce vue create some project yarn add d vuepress vuepress dev docs open chrome devtool，you can see console jaavascript vue runtime esm js failed to resolve async component function layout return webpack require e import then webpack require bind null node modules vuepress theme default layouts layout vue node modules vuepress theme default layouts layout vue reason typeerror cannot assign to read only property exports of object vuepress build docs，you can see shell shell undefined node modules vuepress plugin search searchbox vue vue type style index lang stylus node modules mini css extract plugin dist loader js node modules vuepress core node modules css loader dist cjs js ref oneof node modules vue loader lib loaders stylepostloader js node modules postcss loader src ref oneof node modules stylus loader ref oneof node modules vuepress core node modules cache loader dist cjs js ref node modules vue loader lib vue loader options node modules vuepress plugin search searchbox vue vue type style index lang stylus module build failed from node modules mini css extract plugin dist loader js typeerror cannot assign to read only property exports of object at module users yuistack documents test test press node modules vuepress core node modules css loader dist cjs js ref oneof users yuistack documents test test press node modules vue loader lib loaders stylepostloader js users yuistack documents test test press node modules postcss loader src index js ref oneof users yuistack documents test test press node modules stylus loader index js ref oneof users yuistack documents test test press node modules vuepress core node modules cache loader dist cjs js ref users yuistack documents test test press node modules vue loader lib index js vue loader options users yuistack documents test test press node modules vuepress plugin search searchbox vue vue type style index lang stylus at module module exports module exports users yuistack documents test test press node modules vuepress core node modules css loader dist cjs js ref oneof users yuistack documents test test press node modules vue loader lib loaders stylepostloader js users yuistack documents test test press node modules postcss loader src index js ref oneof users yuistack documents test test press node modules stylus loader index js ref oneof users yuistack documents test test press node modules vuepress core node modules cache loader dist cjs js ref users yuistack documents test test press node modules vue loader lib index js vue loader options users yuistack documents test test press node modules vuepress plugin search searchbox vue vue type style index lang stylus at webpack require users yuistack documents test test press node modules vuepress core node modules css loader dist cjs js ref oneof users yuistack documents test test press node modules vue loader lib loaders stylepostloader js users yuistack documents test test press node modules postcss loader src index js ref oneof users yuistack documents test test press node modules stylus loader index js ref oneof users yuistack documents test test press node modules vuepress core node modules cache loader dist cjs js ref users yuistack documents test test press node modules vue loader lib index js vue loader options users yuistack documents test test press node modules vuepress plugin search searchbox vue vue type style index lang stylus at object module exports module exports users yuistack documents test test press node modules vuepress core node modules css loader dist cjs js ref oneof users yuistack documents test test press node modules vue loader lib loaders stylepostloader js users yuistack documents test test press node modules postcss loader src index js ref oneof users yuistack documents test test press node modules stylus loader index js ref oneof users yuistack documents test test press node modules vuepress core node modules cache loader dist cjs js ref users yuistack documents test test press node modules vue loader lib index js vue loader options users yuistack documents test test press node modules vuepress plugin search searchbox vue vue type style index lang stylus at webpack require users yuistack documents test test press node modules vuepress core node modules css loader dist cjs js ref oneof users yuistack documents test test press node modules vue loader lib loaders stylepostloader js users yuistack documents test test press node modules postcss loader src index js ref oneof users yuistack documents test test press node modules stylus loader index js ref oneof users yuistack documents test test press node modules vuepress core node modules cache loader dist cjs js ref users yuistack documents test test press node modules vue loader lib index js vue loader options users yuistack documents test test press node modules vuepress plugin search searchbox vue vue type style index lang stylus at users yuistack documents test test press node modules vuepress core node modules css loader dist cjs js ref oneof users yuistack documents test test press node modules vue loader lib loaders stylepostloader js users yuistack documents test test press node modules postcss loader src index js ref oneof users yuistack documents test test press node modules stylus loader index js ref oneof users yuistack documents test test press node modules vuepress core node modules cache loader dist cjs js ref users yuistack documents test test press node modules vue loader lib index js vue loader options users yuistack documents test test press node modules vuepress plugin search searchbox vue vue type style index lang stylus at object users yuistack documents test test press node modules vuepress core node modules css loader dist cjs js ref oneof users yuistack documents test test press node modules vue loader lib loaders stylepostloader js users yuistack documents test test press node modules postcss loader src index js ref oneof users yuistack documents test test press node modules stylus loader index js ref oneof users yuistack documents test test press node modules vuepress core node modules cache loader dist cjs js ref users yuistack documents test test press node modules vue loader lib index js vue loader options users yuistack documents test test press node modules vuepress plugin search searchbox vue vue type style index lang stylus at module compile internal modules cjs loader js at exec users yuistack documents test test press node modules mini css extract plugin dist loader js at childcompiler runaschild users yuistack documents test test press node modules mini css extract plugin dist loader js at compile users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js at hooks aftercompile callasync err users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js at asyncserieshook eval eval at create users yuistack documents test test press node modules tapable lib hookcodefactory js at asyncserieshook lazycompilehook users yuistack documents test test press node modules tapable lib hook js at compilation seal err users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js at asyncserieshook eval eval at create users yuistack documents test test press node modules tapable lib hookcodefactory js node modules vuepress plugin search searchbox vue vue type style index lang stylus node modules vuepress plugin search searchbox vue node modules vuepress core node modules cache loader dist cjs js ref node modules babel loader lib ref node modules vuepress core node modules cache loader dist cjs js ref node modules vue loader lib vue loader options node modules vuepress theme default components navbar vue vue type script lang js node modules vuepress theme default components navbar vue vue type script lang js node modules vuepress theme default components navbar vue node modules vuepress core node modules cache loader dist cjs js ref node modules babel loader lib ref node modules vuepress core node modules cache loader dist cjs js ref node modules vue loader lib vue loader options node modules vuepress theme default layouts layout vue vue type script lang js node modules vuepress theme default layouts layout vue vue type script lang js node modules vuepress theme default layouts layout vue node modules vuepress core temp internal layout components js node modules vuepress core lib client util js node modules vuepress core lib client app js node modules vuepress core lib client cliententry js multi node modules vuepress core lib client cliententry js error failed to compile with errors at webpack users yuistack documents test test press node modules vuepress core lib node build index js at finalcallback users yuistack documents test test press node modules vuepress core node modules webpack lib multicompiler js at runwithdependencies err users yuistack documents test test press node modules vuepress core node modules webpack lib multicompiler js at done users yuistack documents test test press node modules neo async async js at runcompilers users yuistack documents test test press node modules vuepress core node modules webpack lib multicompiler js at err users yuistack documents test test press node modules vuepress core node modules webpack lib multicompiler js at compiler run users yuistack documents test test press node modules vuepress core node modules webpack lib multicompiler js at finalcallback users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js at hooks done callasync err users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js at asyncserieshook eval eval at create users yuistack documents test test press node modules tapable lib hookcodefactory js at asyncserieshook lazycompilehook users yuistack documents test test press node modules tapable lib hook js at oncompiled users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js at hooks aftercompile callasync err users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js at asyncserieshook eval eval at create users yuistack documents test test press node modules tapable lib hookcodefactory js at asyncserieshook lazycompilehook users yuistack documents test test press node modules tapable lib hook js at compilation seal err users yuistack documents test test press node modules vuepress core node modules webpack lib compiler js npm err code elifecycle about repo： what is expected vuepress can work with vue cli what is actually happening vuepress can t work with vue cli other relevant information shell environment info system os macos cpu intel r core tm cpu binaries node nvm versions node bin node yarn usr local bin yarn npm nvm versions node bin npm browsers chrome firefox safari npmpackages vuepress core vuepress theme default vuepress npmglobalpackages vuepress not found vue cli version： | 1 |
276,063 | 8,583,787,446 | IssuesEvent | 2018-11-13 20:46:24 | johannbrehmer/madminer | https://api.github.com/repos/johannbrehmer/madminer | closed | Validation with ground truth | enhancement high priority | Without shower and detector effects, we have `x=z` and can evaluate the ground-truth likelihood. We should use this to validate all methods.
This means:
- generating events with MadMiner for some process (we can deactivate Pythia)
- using LHEProcessor to extract a complete set of observables (no unobservable directions in phase space)
- when extracting the test sample, also save the t(x,z) and r(x,z) (have to implement this in SampleAugmenter)
- train methods as usually and compare to ground truth | 1.0 | Validation with ground truth - Without shower and detector effects, we have `x=z` and can evaluate the ground-truth likelihood. We should use this to validate all methods.
This means:
- generating events with MadMiner for some process (we can deactivate Pythia)
- using LHEProcessor to extract a complete set of observables (no unobservable directions in phase space)
- when extracting the test sample, also save the t(x,z) and r(x,z) (have to implement this in SampleAugmenter)
- train methods as usually and compare to ground truth | priority | validation with ground truth without shower and detector effects we have x z and can evaluate the ground truth likelihood we should use this to validate all methods this means generating events with madminer for some process we can deactivate pythia using lheprocessor to extract a complete set of observables no unobservable directions in phase space when extracting the test sample also save the t x z and r x z have to implement this in sampleaugmenter train methods as usually and compare to ground truth | 1 |
587,688 | 17,629,307,133 | IssuesEvent | 2021-08-19 05:12:29 | xmichelo/Beeftext | https://api.github.com/repos/xmichelo/Beeftext | closed | [Bug] Line edits have a grey text instead of black. | bug high priority | Most single line edit now have grey text instead of black. | 1.0 | [Bug] Line edits have a grey text instead of black. - Most single line edit now have grey text instead of black. | priority | line edits have a grey text instead of black most single line edit now have grey text instead of black | 1 |
493,182 | 14,227,565,324 | IssuesEvent | 2020-11-18 01:36:14 | APS-USAXS/ipython-usaxs | https://api.github.com/repos/APS-USAXS/ipython-usaxs | closed | FlyScan Start failed status object | bug high priority | nothing obvious in the logs:
<details>
```
|2020-11-17 14:12:54.992|INFO|27885|bluesky-session|command_list|387|bluesky-run-engine| - Command file: usaxs.mac
====== ======================= ==============================
line # action parameters
====== ======================= ==============================
1 CURRENT_EXPERIMENT_NAME
19 saxsExp 20, 20, 1, AirBlank
20 saxsExp 20, 60, 1, GlassyCarbonSRM3600
23 waxsExp 20, 20, 1, AirBlank
24 waxsExp 20, 60, 1, GlassyCarbonSRM3600
26 preUSAXStune
29 USAXSscan 20, 20, 1, AirBlank
30 USAXSscan 20, 60, 1, GlassyCarbonSRM3600
====== ======================= ==============================
|2020-11-17 14:12:55.255|INFO|27885|bluesky-session|amplifiers|451|bluesky-run-engine| - Measuring background for: PD_USAXS
|2020-11-17 14:12:56.938|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=4 gain=1e12 bkg=10599.4 +/- 434.0975005687086
|2020-11-17 14:12:56.954|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=4 gain=1e9 bkg=266.8 +/- 0.4
|2020-11-17 14:12:56.969|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=4 gain=1e9 bkg=396.4 +/- 0.48989794855663565
|2020-11-17 14:12:56.988|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=4 gain=1e9 bkg=13195.8 +/- 6596.904771178677
|2020-11-17 14:12:58.634|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=3 gain=1e10 bkg=71.8 +/- 40.30583084368811
|2020-11-17 14:12:58.650|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=3 gain=1e8 bkg=261.0 +/- 0.0
|2020-11-17 14:12:58.666|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=3 gain=1e8 bkg=360.8 +/- 0.4
|2020-11-17 14:12:58.690|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=3 gain=1e8 bkg=1646.8 +/- 0.9797958971132713
|2020-11-17 14:13:00.368|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=2 gain=1e8 bkg=1.0 +/- 0.0
|2020-11-17 14:13:00.385|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=2 gain=1e7 bkg=260.0 +/- 0.0
|2020-11-17 14:13:00.390|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=2 gain=1e7 bkg=357.0 +/- 0.0
|2020-11-17 14:13:00.406|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=2 gain=1e7 bkg=137.2 +/- 0.7483314773547883
|2020-11-17 14:13:02.082|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=1 gain=1e6 bkg=1.0 +/- 0.0
|2020-11-17 14:13:02.098|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=1 gain=1e6 bkg=260.6 +/- 0.48989794855663565
|2020-11-17 14:13:02.113|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=1 gain=1e6 bkg=356.8 +/- 0.4
|2020-11-17 14:13:02.135|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=1 gain=1e6 bkg=1.0 +/- 0.0
|2020-11-17 14:13:03.783|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=0 gain=1e4 bkg=1.0 +/- 0.0
|2020-11-17 14:13:03.801|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=0 gain=1e5 bkg=209.0 +/- 104.0
|2020-11-17 14:13:03.816|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=0 gain=1e5 bkg=357.0 +/- 0.0
|2020-11-17 14:13:03.833|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=0 gain=1e5 bkg=1.0 +/- 0.0
|2020-11-17 14:13:03.945|INFO|27885|bluesky-session|command_list|122|bluesky-run-engine| - Runing preUSAXStune as requested at start of measurements
|2020-11-17 14:13:03.992|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:13:04.508|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:13:04.780|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: m_stage_r
|2020-11-17 14:13:04.785|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:13:05.181|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 1000000.0 max: 950000 converged=[True, False]
|2020-11-17 14:13:05.187|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 32060.0 max: 950000 converged=[True, False, False, True]
|2020-11-17 14:13:05.191|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 1580.0 max: 950000 converged=[True, False, False, True, False, True]
|2020-11-17 14:13:05.448|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 549860.0 max: 950000 converged=[False, True]
|2020-11-17 14:13:05.450|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 310620.0 max: 950000 converged=[False, True, True, True]
|2020-11-17 14:13:05.454|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000000.0 rate: 1600.0 max: 950000 converged=[False, True, True, True, False, True]
|2020-11-17 14:13:05.703|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 545180.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:05.705|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 309580.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:05.706|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1620.0 max: 950000 converged=[True, True, True, True, False, True]
|2020-11-17 14:13:05.966|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 550280.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:05.967|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 310200.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:05.969|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1820.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:13:06.007|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:13:06.037|INFO|27885|bluesky-session|axis_tuning|118|bluesky-run-engine| - Tuning axis m_stage_r, current position is 9.059825
|2020-11-17 14:13:19.498|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ =============================================
key result
================ =============================================
x m_stage_r
y I0_USAXS
cen 9.059841344687035
com 9.059806187459237
fwhm 0.0012476952013429354
min [9.059825 1. ]
max [9.059742e+00 3.115500e+04]
crossings [9.0591918 9.0597835 9.05995059 9.06043949]
tune_ok True
center 9.059806187459237
initial_position 9.059825
final_position 9.059806187459237
================ =============================================
|2020-11-17 14:13:19.500|INFO|27885|bluesky-session|axis_tuning|127|bluesky-run-engine| - Tuning axis m_stage_r, final position is 9.059807
|2020-11-17 14:13:19.718|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: m_stage_r
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 9.059825
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (9.059742, 31155.0)
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 9.059841344687035
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 9.059806187459237
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.0012476952013429354
|2020-11-17 14:13:19.720|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 9.059807
|2020-11-17 14:13:20.931|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r
|2020-11-17 14:13:20.934|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:13:21.335|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 506920.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:21.337|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 309380.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:21.337|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1840.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:13:21.384|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:13:21.399|INFO|27885|bluesky-session|axis_tuning|222|bluesky-run-engine| - Tuning axis a_stage_r, current position is 8.746982800000001
|2020-11-17 14:13:36.561|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ===================================================================
key result
================ ===================================================================
x a_stage_r
y PD_USAXS
cen 8.746886818777009
com 8.746875691565497
fwhm 0.0004645681837658344
min [8.7473946 1. ]
max [8.7468652e+00 6.1244000e+04]
crossings [8.74663827 8.74669463 8.74673721 8.7470498 8.74709816 8.74710284]
tune_ok True
center 8.746875691565497
initial_position 8.746982800000001
final_position 8.746875691565497
================ ===================================================================
|2020-11-17 14:13:36.562|INFO|27885|bluesky-session|axis_tuning|231|bluesky-run-engine| - Tuning axis a_stage_r, final position is 8.7468757
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 8.746982800000001
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (8.7468652, 61244.0)
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 8.746886818777009
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 8.746875691565497
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.0004645681837658344
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 8.7468757
|2020-11-17 14:13:38.181|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r2p
|2020-11-17 14:13:38.184|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:13:38.596|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 619480.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:38.597|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 312160.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:38.598|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1800.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:13:38.663|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:13:38.680|INFO|27885|bluesky-session|axis_tuning|289|bluesky-run-engine| - Tuning axis a_stage_r2p, current position is 45.8415
|2020-11-17 14:13:43.280|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ========================================================================
key result
================ ========================================================================
x a_stage_r2p
y PD_USAXS
cen 46.076191262102945
com 46.13022908489644
fwhm 2.291823972187345
min [43.5081 1. ]
max [4.63415e+01 6.36710e+04]
crossings [44.9726227 45.3918372 45.60132712 46.09115043 46.25814607 46.42480262
46.60519729 47.26444667]
tune_ok True
center 46.13022908489644
initial_position 45.8415
final_position 46.13022908489644
================ ========================================================================
|2020-11-17 14:13:43.283|INFO|27885|bluesky-session|axis_tuning|302|bluesky-run-engine| - Tuning axis a_stage_r2p, final position is 46.1302
|2020-11-17 14:13:43.504|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r2p
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 45.8415
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (46.3415, 63671.0)
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 46.076191262102945
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 46.13022908489644
|2020-11-17 14:13:43.506|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 2.291823972187345
|2020-11-17 14:13:43.506|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 46.1302
|2020-11-17 14:13:44.621|INFO|27885|bluesky-session|scans|143|bluesky-run-engine| - USAXS count time: {terms.USAXS.usaxs_time.get()} second(s)
|2020-11-17 14:13:44.689|INFO|27885|bluesky-session|command_list|479|bluesky-run-engine| - Synchronizing detector order numbers to 5
|2020-11-17 14:13:44.735|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 1: CURRENT_EXPERIMENT_NAME ""
|2020-11-17 14:13:44.735|INFO|27885|bluesky-session|command_list|462|bluesky-run-engine| - no handling for line 1: CURRENT_EXPERIMENT_NAME ""
|2020-11-17 14:13:44.736|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 19: saxsExp 20 20 1 "AirBlank"
|2020-11-17 14:13:44.753|INFO|27885|bluesky-session|mode_changes|164|bluesky-run-engine| - Found UsaxsSaxsMode = USAXS in beam
|2020-11-17 14:13:44.753|INFO|27885|bluesky-session|mode_changes|165|bluesky-run-engine| - Moving to proper SAXS mode
|2020-11-17 14:13:44.755|INFO|27885|bluesky-session|move_instrument|59|bluesky-run-engine| - Moving WAXS out of beam
|2020-11-17 14:13:44.766|INFO|27885|bluesky-session|move_instrument|70|bluesky-run-engine| - Removed WAXS from beam position
|2020-11-17 14:13:44.771|INFO|27885|bluesky-session|move_instrument|185|bluesky-run-engine| - Moving USAXS out of beam
|2020-11-17 14:13:55.351|INFO|27885|bluesky-session|move_instrument|203|bluesky-run-engine| - Removed USAXS from beam position
|2020-11-17 14:13:55.358|INFO|27885|bluesky-session|move_instrument|144|bluesky-run-engine| - Moving to Pinhole SAXS mode
|2020-11-17 14:14:02.676|INFO|27885|bluesky-session|move_instrument|174|bluesky-run-engine| - Pinhole SAXS is in position
|2020-11-17 14:14:02.679|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:08.511|INFO|27885|bluesky-session|setup_new_user|274|bluesky-run-engine| - Creating technique directory: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs
|2020-11-17 14:14:08.511|INFO|27885|bluesky-session|scans|688|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/AirBlank_0005.hdf
|2020-11-17 14:14:08.511|INFO|27885|bluesky-session|scans|690|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/AirBlank_0005.hdf
|2020-11-17 14:14:08.679|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:10.143|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:10.537|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000000.0 rate: 30460.0 max: 950000 converged=[False, True]
|2020-11-17 14:14:10.537|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 120360.0 max: 950000 converged=[False, True, True, True]
|2020-11-17 14:14:10.781|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000000.0 rate: 292900.0 max: 950000 converged=[True, True]
|2020-11-17 14:14:10.785|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 120720.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:14:10.810|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:14:16.108|INFO|27885|bluesky-session|sample_transmission|156|bluesky-run-engine| - Measured SAXS transmission values, pinDiode cts =381687.000000 with gain 100000.0 and I0 cts 1472102.0 with gain 100000000.0
|2020-11-17 14:14:17.087|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:17.467|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 850520.0 max: 950000 converged=[False, True]
|2020-11-17 14:14:17.711|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 833333.3333333334 max: 950000 converged=[True, True]
|2020-11-17 14:14:17.729|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True]
|2020-11-17 14:14:18.032|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:14:24.392|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 6.37434983253479 seconds.
|2020-11-17 14:14:24.466|INFO|27885|bluesky-session|scans|789|bluesky-run-engine| - I0 value: 429731.0
|2020-11-17 14:14:24.478|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 20: saxsExp 20 60 1 "GlassyCarbonSRM3600"
|2020-11-17 14:14:24.502|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:30.298|INFO|27885|bluesky-session|scans|688|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:14:30.298|INFO|27885|bluesky-session|scans|690|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:14:30.358|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:31.795|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:32.205|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 30460.0 max: 950000 converged=[True, True]
|2020-11-17 14:14:32.207|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 113840.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:14:32.244|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:14:37.524|INFO|27885|bluesky-session|sample_transmission|156|bluesky-run-engine| - Measured SAXS transmission values, pinDiode cts =381687.000000 with gain 100000.0 and I0 cts 1472102.0 with gain 100000000.0
|2020-11-17 14:14:38.436|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:38.816|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 1310606060.6060605 max: 950000 converged=[True, False]
|2020-11-17 14:14:39.065|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 1882173913.0434783 max: 950000 converged=[True, False]
|2020-11-17 14:14:39.321|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86420.0 max: 950000 converged=[True, True]
|2020-11-17 14:14:39.336|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True]
|2020-11-17 14:14:39.628|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:14:45.131|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 5.519550800323486 seconds.
|2020-11-17 14:14:45.179|INFO|27885|bluesky-session|scans|789|bluesky-run-engine| - I0 value: 429245.0
|2020-11-17 14:14:45.193|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 23: waxsExp 20 20 1 "AirBlank"
|2020-11-17 14:14:45.194|DEBUG|27885|bluesky-session|scans|808|bluesky-run-engine| - waxsx start collection =0.000624999999956799
|2020-11-17 14:14:45.195|DEBUG|27885|bluesky-session|scans|812|bluesky-run-engine| - waxsx after before plan =0.000624999999956799
|2020-11-17 14:14:45.211|INFO|27885|bluesky-session|mode_changes|193|bluesky-run-engine| - Found UsaxsSaxsMode = SAXS in beam
|2020-11-17 14:14:45.211|INFO|27885|bluesky-session|mode_changes|194|bluesky-run-engine| - Moving to proper WAXS mode
|2020-11-17 14:14:45.213|INFO|27885|bluesky-session|move_instrument|113|bluesky-run-engine| - Moving SAXS out of beam
|2020-11-17 14:14:52.447|INFO|27885|bluesky-session|move_instrument|133|bluesky-run-engine| - Removed SAXS from beam position
|2020-11-17 14:14:52.453|INFO|27885|bluesky-session|move_instrument|185|bluesky-run-engine| - Moving USAXS out of beam
|2020-11-17 14:14:52.482|INFO|27885|bluesky-session|move_instrument|203|bluesky-run-engine| - Removed USAXS from beam position
|2020-11-17 14:14:52.495|INFO|27885|bluesky-session|move_instrument|81|bluesky-run-engine| - Moving to WAXS mode
|2020-11-17 14:15:03.012|INFO|27885|bluesky-session|move_instrument|102|bluesky-run-engine| - WAXS is in position
|2020-11-17 14:15:03.015|DEBUG|27885|bluesky-session|mode_changes|202|bluesky-run-engine| - guard slits horizontal difference = 0
|2020-11-17 14:15:03.015|DEBUG|27885|bluesky-session|mode_changes|203|bluesky-run-engine| - guard slits vertical difference = 0
|2020-11-17 14:15:03.016|DEBUG|27885|bluesky-session|mode_changes|218|bluesky-run-engine| - USAXS slits horizontal difference = 8.12e-05
|2020-11-17 14:15:03.016|DEBUG|27885|bluesky-session|mode_changes|219|bluesky-run-engine| - USAXS slits vertical difference = 0.0001625
|2020-11-17 14:15:03.016|INFO|27885|bluesky-session|mode_changes|229|bluesky-run-engine| - Prepared for WAXS mode
|2020-11-17 14:15:03.062|DEBUG|27885|bluesky-session|scans|816|bluesky-run-engine| - waxsx after mode_WAXS =256.50062499999996
|2020-11-17 14:15:08.113|INFO|27885|bluesky-session|setup_new_user|274|bluesky-run-engine| - Creating technique directory: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs
|2020-11-17 14:15:08.114|INFO|27885|bluesky-session|scans|851|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/AirBlank_0005.hdf
|2020-11-17 14:15:08.114|INFO|27885|bluesky-session|scans|853|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/AirBlank_0005.hdf
|2020-11-17 14:15:09.206|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:15:09.599|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86480.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:09.603|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 999980.0 max: 950000 converged=[True, True, True, False]
|2020-11-17 14:15:09.852|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86340.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:09.853|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 539380.0 max: 950000 converged=[True, True, False, True]
|2020-11-17 14:15:10.102|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86240.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:10.105|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 538640.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:15:10.141|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:15:10.416|DEBUG|27885|bluesky-session|scans|928|bluesky-run-engine| - waxsx before Image collection=256.50062499999996
|2020-11-17 14:15:10.429|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:15:15.471|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 25.0s remaining
|2020-11-17 14:15:20.436|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 20.0s remaining
|2020-11-17 14:15:25.453|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 15.0s remaining
|2020-11-17 14:15:30.469|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 10.0s remaining
|2020-11-17 14:15:35.437|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 5.0s remaining
|2020-11-17 14:15:41.833|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 31.417147874832153 seconds.
|2020-11-17 14:15:41.892|INFO|27885|bluesky-session|scans|957|bluesky-run-engine| - I0 value: 2591974.0
|2020-11-17 14:15:41.905|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 24: waxsExp 20 60 1 "GlassyCarbonSRM3600"
|2020-11-17 14:15:41.907|DEBUG|27885|bluesky-session|scans|808|bluesky-run-engine| - waxsx start collection =256.50062499999996
|2020-11-17 14:15:41.907|DEBUG|27885|bluesky-session|scans|812|bluesky-run-engine| - waxsx after before plan =256.50062499999996
|2020-11-17 14:15:41.984|DEBUG|27885|bluesky-session|mode_changes|190|bluesky-run-engine| - WAXS is in beam
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|202|bluesky-run-engine| - guard slits horizontal difference = 0
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|203|bluesky-run-engine| - guard slits vertical difference = 0
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|218|bluesky-run-engine| - USAXS slits horizontal difference = 8.12e-05
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|219|bluesky-run-engine| - USAXS slits vertical difference = 0.0001625
|2020-11-17 14:15:41.986|INFO|27885|bluesky-session|mode_changes|229|bluesky-run-engine| - Prepared for WAXS mode
|2020-11-17 14:15:42.019|DEBUG|27885|bluesky-session|scans|816|bluesky-run-engine| - waxsx after mode_WAXS =256.50062499999996
|2020-11-17 14:15:47.047|INFO|27885|bluesky-session|scans|851|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:15:47.047|INFO|27885|bluesky-session|scans|853|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:15:48.011|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:15:48.403|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86560.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:48.407|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 508180.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:15:48.455|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:15:48.734|DEBUG|27885|bluesky-session|scans|928|bluesky-run-engine| - waxsx before Image collection=256.50062499999996
|2020-11-17 14:15:48.751|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:15:53.793|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 25.0s remaining
|2020-11-17 14:15:58.766|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 20.0s remaining
|2020-11-17 14:16:03.777|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 15.0s remaining
|2020-11-17 14:16:08.803|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 10.0s remaining
|2020-11-17 14:16:13.768|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 5.0s remaining
|2020-11-17 14:16:19.301|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 30.56360387802124 seconds.
|2020-11-17 14:16:19.562|INFO|27885|bluesky-session|scans|957|bluesky-run-engine| - I0 value: 2590638.0
|2020-11-17 14:16:19.579|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 26: preUSAXStune
|2020-11-17 14:16:23.016|INFO|27885|bluesky-session|mode_changes|112|bluesky-run-engine| - Found UsaxsSaxsMode = WAXS in beam
|2020-11-17 14:16:23.016|INFO|27885|bluesky-session|mode_changes|113|bluesky-run-engine| - Moving to proper USAXS mode
|2020-11-17 14:16:23.021|INFO|27885|bluesky-session|move_instrument|59|bluesky-run-engine| - Moving WAXS out of beam
|2020-11-17 14:16:33.503|INFO|27885|bluesky-session|move_instrument|70|bluesky-run-engine| - Removed WAXS from beam position
|2020-11-17 14:16:33.511|INFO|27885|bluesky-session|move_instrument|113|bluesky-run-engine| - Moving SAXS out of beam
|2020-11-17 14:16:33.525|INFO|27885|bluesky-session|move_instrument|133|bluesky-run-engine| - Removed SAXS from beam position
|2020-11-17 14:16:33.545|INFO|27885|bluesky-session|move_instrument|214|bluesky-run-engine| - Moving to USAXS mode
|2020-11-17 14:16:44.147|INFO|27885|bluesky-session|move_instrument|242|bluesky-run-engine| - USAXS is in position
|2020-11-17 14:16:44.149|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:16:44.667|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:16:44.943|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: m_stage_r
|2020-11-17 14:16:44.946|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:16:45.349|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 624180.0 max: 950000 converged=[True, True]
|2020-11-17 14:16:45.351|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 312240.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:16:45.351|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1800.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:16:45.383|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:16:45.403|INFO|27885|bluesky-session|axis_tuning|118|bluesky-run-engine| - Tuning axis m_stage_r, current position is 9.059807
|2020-11-17 14:16:59.016|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ===========================
key result
================ ===========================
x m_stage_r
y I0_USAXS
cen 9.059839376418388
com 9.059838127744769
fwhm 0.0012467757926177825
min [ 9.058557 421. ]
max [9.059974e+00 3.140400e+04]
crossings [9.05921599 9.06046276]
tune_ok True
center 9.059838127744769
initial_position 9.059807
final_position 9.059838127744769
================ ===========================
|2020-11-17 14:16:59.017|INFO|27885|bluesky-session|axis_tuning|127|bluesky-run-engine| - Tuning axis m_stage_r, final position is 9.059838
|2020-11-17 14:16:59.226|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: m_stage_r
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 9.059807
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (9.059973999999999, 31404.0)
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 9.059839376418388
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 9.059838127744769
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.0012467757926177825
|2020-11-17 14:16:59.228|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 9.059838
|2020-11-17 14:17:00.441|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r
|2020-11-17 14:17:00.444|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:17:00.850|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 593380.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:00.852|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 313760.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:00.853|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1820.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:17:00.900|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:17:00.942|INFO|27885|bluesky-session|axis_tuning|222|bluesky-run-engine| - Tuning axis a_stage_r, current position is 8.7468757
|2020-11-17 14:17:16.065|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ===========================
key result
================ ===========================
x a_stage_r
y PD_USAXS
cen 8.746955269003653
com 8.74694818799869
fwhm 0.00051833940621826
min [8.7473169 2. ]
max [8.746964e+00 6.522100e+04]
crossings [8.7466961 8.74721444]
tune_ok True
center 8.74694818799869
initial_position 8.7468757
final_position 8.74694818799869
================ ===========================
|2020-11-17 14:17:16.066|INFO|27885|bluesky-session|axis_tuning|231|bluesky-run-engine| - Tuning axis a_stage_r, final position is 8.7469482
|2020-11-17 14:17:16.587|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r
|2020-11-17 14:17:16.587|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 8.7468757
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (8.746964, 65221.0)
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 8.746955269003653
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 8.74694818799869
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.00051833940621826
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 8.7468757
|2020-11-17 14:17:17.924|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r2p
|2020-11-17 14:17:17.927|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:17:18.333|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 601160.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:18.335|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 314760.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:18.336|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1820.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:17:18.378|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:17:18.396|INFO|27885|bluesky-session|axis_tuning|289|bluesky-run-engine| - Tuning axis a_stage_r2p, current position is 46.1302
|2020-11-17 14:17:23.105|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ =================================================
key result
================ =================================================
x a_stage_r2p
y PD_USAXS
cen 46.21770183843965
com 45.77260666059711
fwhm 2.0894698967413845
min [47.6302 1. ]
max [4.59635e+01 6.17300e+04]
crossings [44.74551552 46.53165177 46.75865465 46.83498542]
tune_ok True
center 45.77260666059711
initial_position 46.1302
final_position 45.77260666059711
================ =================================================
|2020-11-17 14:17:23.107|INFO|27885|bluesky-session|axis_tuning|302|bluesky-run-engine| - Tuning axis a_stage_r2p, final position is 45.772600000000004
|2020-11-17 14:17:23.335|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r2p
|2020-11-17 14:17:23.335|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 46.1302
|2020-11-17 14:17:23.335|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (45.9635, 61730.0)
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 46.21770183843965
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 45.77260666059711
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 2.0894698967413845
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 45.772600000000004
|2020-11-17 14:17:24.451|INFO|27885|bluesky-session|scans|143|bluesky-run-engine| - USAXS count time: {terms.USAXS.usaxs_time.get()} second(s)
|2020-11-17 14:17:24.471|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 29: USAXSscan 20 20 1 "AirBlank"
|2020-11-17 14:17:24.513|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:17:25.021|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:17:30.115|INFO|27885|bluesky-session|setup_new_user|274|bluesky-run-engine| - Creating technique directory: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_usaxs
|2020-11-17 14:17:30.465|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:17:30.977|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:17:34.088|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:17:34.476|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 108800.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:34.477|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 298840.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:34.511|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:17:40.705|INFO|27885|bluesky-session|sample_transmission|91|bluesky-run-engine| - Measured USAXS transmission values:
======== ============= ==========
detector counts gain
======== ============= ==========
pinDiode 897075.000000 100000.0
I0 326459.000000 10000000.0
======== ============= ==========
|2020-11-17 14:17:40.927|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:17:41.336|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 684280.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:41.338|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 313800.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:41.340|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1800.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:17:41.383|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:17:41.939|INFO|27885|bluesky-session|usaxs_fly_scan|143|Thread-3525| - HDF5 config: /share1/AreaDetectorConfig/FlyScan_config/saveFlyData.xml
|2020-11-17 14:17:41.940|INFO|27885|bluesky-session|usaxs_fly_scan|144|Thread-3525| - HDF5 output: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_usaxs/AirBlank_0005.h5
|2020-11-17 14:17:41.941|DEBUG|27885|bluesky-session|usaxs_fly_scan|99|Thread-3527| - progress_reporting has arrived
|2020-11-17 14:17:42.001|INFO|27885|bluesky-session|usaxs_fly_scan|106|Thread-3527| - flying, s ar, deg ay, mm dy, mm channel elapsed, s
|2020-11-17 14:17:46.941|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 5.00 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:17:51.943|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 10.00 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:17:56.943|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 15.00 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:01.948|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 20.01 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:06.953|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 25.01 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:11.959|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 30.02 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:16.963|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 35.02 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:21.971|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 40.03 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:26.973|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 45.03 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:31.975|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 50.04 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:36.978|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 55.04 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:41.978|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 60.04 8.7474221 0.00134 12.89540 43 4.47
|2020-11-17 14:18:46.981|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 65.04 8.7465670 -0.00160 12.88191 77 9.48
|2020-11-17 14:18:51.991|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 70.05 8.7442744 -0.00979 12.84332 158 14.48
|2020-11-17 14:18:57.006|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 75.06 8.7387945 -0.02978 12.75383 324 19.50
|2020-11-17 14:19:02.010|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 80.07 8.7288428 -0.06548 12.58796 578 24.50
|2020-11-17 14:19:07.014|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 85.07 8.7125184 -0.12444 12.32028 916 29.52
|2020-11-17 14:19:12.017|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 90.08 8.6879521 -0.21221 11.91334 1320 34.52
|2020-11-17 14:19:17.025|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 95.09 8.6530330 -0.33540 11.34481 1780 39.52
|2020-11-17 14:19:22.033|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 100.09 8.6065840 -0.49936 10.59277 2284 44.53
|2020-11-17 14:19:27.042|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 105.10 8.5451042 -0.71911 9.60428 2820 49.53
|2020-11-17 14:19:32.043|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 110.10 8.4681207 -0.98864 8.34250 3382 54.53
|2020-11-17 14:19:37.051|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 115.11 8.3700480 -1.33069 6.76414 3967 59.55
|2020-11-17 14:19:42.061|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 120.12 8.2544121 -1.74213 4.87822 4566 64.55
|2020-11-17 14:19:47.071|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 125.13 8.1117977 -2.24406 2.56832 5181 69.57
|2020-11-17 14:19:52.084|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 130.14 7.9420729 -2.82694 -0.17056 5802 74.55
|2020-11-17 14:19:57.082|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 135.14 7.7483276 -3.52310 -3.30210 6436 79.59
|2020-11-17 14:20:02.089|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 140.15 7.5175999 -4.33461 -7.04691 7077 84.59
|2020-11-17 14:20:07.095|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 145.16 7.2594410 -5.24235 -11.22207 7722 89.59
|2020-11-17 14:20:12.101|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 150.16 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:17.106|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 155.17 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:22.108|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 160.17 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:27.118|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 165.18 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:32.120|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 170.18 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:37.128|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 175.19 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:42.135|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 180.20 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:47.141|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 185.20 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:52.148|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 190.21 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:57.151|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 195.21 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:02.156|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 200.22 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:07.159|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 205.22 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:11.951|INFO|27885|bluesky-session|usaxs_fly_scan|115|Thread-3527| - 210.01 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:11.952|ERROR|27885|bluesky-session|usaxs_fly_scan|118|Thread-3527| - 210.01355910301208s - progress_reporting timeout!!
```
</details>
Looking at the recent console output, this helps:
<details>
```
D Tue-14:17:41 - progress_reporting has arrived
I Tue-14:17:42 - flying, s ar, deg ay, mm dy, mm channel elapsed, s
D Tue-14:17:46 - 5.00 8.7487005 0.00612 12.91725 0 0.00
D Tue-14:17:51 - 10.00 8.7487005 0.00612 12.91725 0 0.00
---------------------------------------------------------------------------
FailedStatus Traceback (most recent call last)
<ipython-input-3-04b994fdd9b0> in <module>
----> 1 RE(run_command_file("usaxs.mac"))
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in __call__(self, *args, **metadata_kw)
805 self._task_fut.add_done_callback(set_blocking_event)
806
--> 807 self._resume_task(init_func=_build_task)
808
809 if self._interrupted:
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in _resume_task(self, init_func)
929 if (exc is not None
930 and not isinstance(exc, _RunEnginePanic)):
--> 931 raise exc
932
933 def install_suspender(self, suspender):
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in _run(self)
1498 exit_reason = str(err)
1499 self.log.exception("Run aborted")
-> 1500 raise err
1501 finally:
1502 if not exit_reason:
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in _run(self)
1339 # throw the exception at the current plan
1340 try:
-> 1341 msg = self._plan_stack[-1].throw(
1342 stashed_exception or resp)
1343 except Exception as e:
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in __call__(self, plan)
1305 plan = monitor_during_wrapper(plan, self.monitors)
1306 plan = baseline_wrapper(plan, self.baseline)
-> 1307 return (yield from plan)
1308
1309
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in baseline_wrapper(plan, devices, name)
1160 return (yield from plan)
1161 else:
-> 1162 return (yield from plan_mutator(plan, insert_baseline))
1163
1164
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in monitor_during_wrapper(plan, signals)
801 plan1 = plan_mutator(plan, insert_after_open)
802 plan2 = plan_mutator(plan1, insert_before_close)
--> 803 return (yield from plan2)
804
805
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in fly_during_wrapper(plan, flyers)
859 plan1 = plan_mutator(plan, insert_after_open)
860 plan2 = plan_mutator(plan1, insert_before_close)
--> 861 return (yield from plan2)
862
863
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
~/.ipython/profile_bluesky/startup/instrument/plans/command_list.py in run_command_file(filename, md)
339 """
340 commands = get_command_list(filename)
--> 341 yield from execute_command_list(filename, commands)
342
343
~/.ipython/profile_bluesky/startup/instrument/plans/command_list.py in execute_command_list(filename, commands, md)
417 snm = args[3]
418 _md.update(dict(sx=sx, sy=sy, thickness=sth, title=snm))
--> 419 yield from USAXSscan(sx, sy, sth, snm, md=_md) # either step or fly scan
420
421 elif action in ("saxs", "saxsexp"):
~/.ipython/profile_bluesky/startup/instrument/plans/scans.py in USAXSscan(x, y, thickness_mm, title, md)
234 _md["title"] = title
235 if terms.FlyScan.use_flyscan.get():
--> 236 yield from Flyscan(x, y, thickness_mm, title, md=_md)
237 else:
238 yield from USAXSscanStep(x, y, thickness_mm, title, md=_md)
~/.ipython/profile_bluesky/startup/instrument/plans/scans.py in Flyscan(pos_X, pos_Y, thickness, scan_title, md)
580 yield from record_sample_image_on_demand("usaxs", scan_title_clean, _md)
581
--> 582 yield from usaxs_flyscan.plan(md=_md) # DO THE FLY SCAN
583
584 yield from bps.mv(
~/.ipython/profile_bluesky/startup/instrument/devices/usaxs_fly_scan.py in plan(self, md)
198 yield from bps.abs_set(self.flying, True)
199
--> 200 yield from bps.wait(group=g)
201 yield from bps.abs_set(self.flying, False)
202 elapsed = time.time() - self.t0
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/plan_stubs.py in wait(group)
465 Msg('wait', None, group=group)
466 """
--> 467 return (yield Msg('wait', None, group=group))
468
469
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
FailedStatus: Status(obj=EpicsSignal(read_pv='9idcLAX:USAXSfly:Start', name='usaxs_flyscan_busy', parent='usaxs_flyscan', value=1, timestamp=1605644261.927068, auto_monitor=True, string=True, write_pv='9idcLAX:USAXSfly:Start', limits=False, put_complete=True), done=True, success=False)
```
</details>
It's a FailedStatus on the fly scan start button: `9idcLAX:USAXSfly:Start` (ophyd object: `usaxs_flyscan.busy`)
Could not interrupt the RunEngine with ^C. Used ^\ to stop the ipython session. Command line did not show what was being typed so had to create new terminal sessions to restore normal operations. Ugly. | 1.0 | FlyScan Start failed status object - nothing obvious in the logs:
<details>
```
|2020-11-17 14:12:54.992|INFO|27885|bluesky-session|command_list|387|bluesky-run-engine| - Command file: usaxs.mac
====== ======================= ==============================
line # action parameters
====== ======================= ==============================
1 CURRENT_EXPERIMENT_NAME
19 saxsExp 20, 20, 1, AirBlank
20 saxsExp 20, 60, 1, GlassyCarbonSRM3600
23 waxsExp 20, 20, 1, AirBlank
24 waxsExp 20, 60, 1, GlassyCarbonSRM3600
26 preUSAXStune
29 USAXSscan 20, 20, 1, AirBlank
30 USAXSscan 20, 60, 1, GlassyCarbonSRM3600
====== ======================= ==============================
|2020-11-17 14:12:55.255|INFO|27885|bluesky-session|amplifiers|451|bluesky-run-engine| - Measuring background for: PD_USAXS
|2020-11-17 14:12:56.938|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=4 gain=1e12 bkg=10599.4 +/- 434.0975005687086
|2020-11-17 14:12:56.954|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=4 gain=1e9 bkg=266.8 +/- 0.4
|2020-11-17 14:12:56.969|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=4 gain=1e9 bkg=396.4 +/- 0.48989794855663565
|2020-11-17 14:12:56.988|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=4 gain=1e9 bkg=13195.8 +/- 6596.904771178677
|2020-11-17 14:12:58.634|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=3 gain=1e10 bkg=71.8 +/- 40.30583084368811
|2020-11-17 14:12:58.650|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=3 gain=1e8 bkg=261.0 +/- 0.0
|2020-11-17 14:12:58.666|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=3 gain=1e8 bkg=360.8 +/- 0.4
|2020-11-17 14:12:58.690|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=3 gain=1e8 bkg=1646.8 +/- 0.9797958971132713
|2020-11-17 14:13:00.368|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=2 gain=1e8 bkg=1.0 +/- 0.0
|2020-11-17 14:13:00.385|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=2 gain=1e7 bkg=260.0 +/- 0.0
|2020-11-17 14:13:00.390|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=2 gain=1e7 bkg=357.0 +/- 0.0
|2020-11-17 14:13:00.406|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=2 gain=1e7 bkg=137.2 +/- 0.7483314773547883
|2020-11-17 14:13:02.082|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=1 gain=1e6 bkg=1.0 +/- 0.0
|2020-11-17 14:13:02.098|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=1 gain=1e6 bkg=260.6 +/- 0.48989794855663565
|2020-11-17 14:13:02.113|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=1 gain=1e6 bkg=356.8 +/- 0.4
|2020-11-17 14:13:02.135|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=1 gain=1e6 bkg=1.0 +/- 0.0
|2020-11-17 14:13:03.783|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - PD_USAXS range=0 gain=1e4 bkg=1.0 +/- 0.0
|2020-11-17 14:13:03.801|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I0_USAXS range=0 gain=1e5 bkg=209.0 +/- 104.0
|2020-11-17 14:13:03.816|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - I00_USAXS range=0 gain=1e5 bkg=357.0 +/- 0.0
|2020-11-17 14:13:03.833|INFO|27885|bluesky-session|amplifiers|425|bluesky-run-engine| - TR diode range=0 gain=1e5 bkg=1.0 +/- 0.0
|2020-11-17 14:13:03.945|INFO|27885|bluesky-session|command_list|122|bluesky-run-engine| - Runing preUSAXStune as requested at start of measurements
|2020-11-17 14:13:03.992|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:13:04.508|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:13:04.780|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: m_stage_r
|2020-11-17 14:13:04.785|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:13:05.181|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 1000000.0 max: 950000 converged=[True, False]
|2020-11-17 14:13:05.187|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 32060.0 max: 950000 converged=[True, False, False, True]
|2020-11-17 14:13:05.191|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 1580.0 max: 950000 converged=[True, False, False, True, False, True]
|2020-11-17 14:13:05.448|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 549860.0 max: 950000 converged=[False, True]
|2020-11-17 14:13:05.450|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 310620.0 max: 950000 converged=[False, True, True, True]
|2020-11-17 14:13:05.454|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000000.0 rate: 1600.0 max: 950000 converged=[False, True, True, True, False, True]
|2020-11-17 14:13:05.703|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 545180.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:05.705|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 309580.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:05.706|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1620.0 max: 950000 converged=[True, True, True, True, False, True]
|2020-11-17 14:13:05.966|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 550280.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:05.967|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 310200.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:05.969|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1820.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:13:06.007|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:13:06.037|INFO|27885|bluesky-session|axis_tuning|118|bluesky-run-engine| - Tuning axis m_stage_r, current position is 9.059825
|2020-11-17 14:13:19.498|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ =============================================
key result
================ =============================================
x m_stage_r
y I0_USAXS
cen 9.059841344687035
com 9.059806187459237
fwhm 0.0012476952013429354
min [9.059825 1. ]
max [9.059742e+00 3.115500e+04]
crossings [9.0591918 9.0597835 9.05995059 9.06043949]
tune_ok True
center 9.059806187459237
initial_position 9.059825
final_position 9.059806187459237
================ =============================================
|2020-11-17 14:13:19.500|INFO|27885|bluesky-session|axis_tuning|127|bluesky-run-engine| - Tuning axis m_stage_r, final position is 9.059807
|2020-11-17 14:13:19.718|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: m_stage_r
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 9.059825
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (9.059742, 31155.0)
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 9.059841344687035
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 9.059806187459237
|2020-11-17 14:13:19.719|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.0012476952013429354
|2020-11-17 14:13:19.720|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 9.059807
|2020-11-17 14:13:20.931|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r
|2020-11-17 14:13:20.934|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:13:21.335|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 506920.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:21.337|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 309380.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:21.337|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1840.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:13:21.384|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:13:21.399|INFO|27885|bluesky-session|axis_tuning|222|bluesky-run-engine| - Tuning axis a_stage_r, current position is 8.746982800000001
|2020-11-17 14:13:36.561|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ===================================================================
key result
================ ===================================================================
x a_stage_r
y PD_USAXS
cen 8.746886818777009
com 8.746875691565497
fwhm 0.0004645681837658344
min [8.7473946 1. ]
max [8.7468652e+00 6.1244000e+04]
crossings [8.74663827 8.74669463 8.74673721 8.7470498 8.74709816 8.74710284]
tune_ok True
center 8.746875691565497
initial_position 8.746982800000001
final_position 8.746875691565497
================ ===================================================================
|2020-11-17 14:13:36.562|INFO|27885|bluesky-session|axis_tuning|231|bluesky-run-engine| - Tuning axis a_stage_r, final position is 8.7468757
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 8.746982800000001
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:13:36.844|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (8.7468652, 61244.0)
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 8.746886818777009
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 8.746875691565497
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.0004645681837658344
|2020-11-17 14:13:36.845|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 8.7468757
|2020-11-17 14:13:38.181|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r2p
|2020-11-17 14:13:38.184|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:13:38.596|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 619480.0 max: 950000 converged=[True, True]
|2020-11-17 14:13:38.597|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 312160.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:13:38.598|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1800.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:13:38.663|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:13:38.680|INFO|27885|bluesky-session|axis_tuning|289|bluesky-run-engine| - Tuning axis a_stage_r2p, current position is 45.8415
|2020-11-17 14:13:43.280|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ========================================================================
key result
================ ========================================================================
x a_stage_r2p
y PD_USAXS
cen 46.076191262102945
com 46.13022908489644
fwhm 2.291823972187345
min [43.5081 1. ]
max [4.63415e+01 6.36710e+04]
crossings [44.9726227 45.3918372 45.60132712 46.09115043 46.25814607 46.42480262
46.60519729 47.26444667]
tune_ok True
center 46.13022908489644
initial_position 45.8415
final_position 46.13022908489644
================ ========================================================================
|2020-11-17 14:13:43.283|INFO|27885|bluesky-session|axis_tuning|302|bluesky-run-engine| - Tuning axis a_stage_r2p, final position is 46.1302
|2020-11-17 14:13:43.504|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r2p
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 45.8415
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (46.3415, 63671.0)
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 46.076191262102945
|2020-11-17 14:13:43.505|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 46.13022908489644
|2020-11-17 14:13:43.506|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 2.291823972187345
|2020-11-17 14:13:43.506|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 46.1302
|2020-11-17 14:13:44.621|INFO|27885|bluesky-session|scans|143|bluesky-run-engine| - USAXS count time: {terms.USAXS.usaxs_time.get()} second(s)
|2020-11-17 14:13:44.689|INFO|27885|bluesky-session|command_list|479|bluesky-run-engine| - Synchronizing detector order numbers to 5
|2020-11-17 14:13:44.735|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 1: CURRENT_EXPERIMENT_NAME ""
|2020-11-17 14:13:44.735|INFO|27885|bluesky-session|command_list|462|bluesky-run-engine| - no handling for line 1: CURRENT_EXPERIMENT_NAME ""
|2020-11-17 14:13:44.736|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 19: saxsExp 20 20 1 "AirBlank"
|2020-11-17 14:13:44.753|INFO|27885|bluesky-session|mode_changes|164|bluesky-run-engine| - Found UsaxsSaxsMode = USAXS in beam
|2020-11-17 14:13:44.753|INFO|27885|bluesky-session|mode_changes|165|bluesky-run-engine| - Moving to proper SAXS mode
|2020-11-17 14:13:44.755|INFO|27885|bluesky-session|move_instrument|59|bluesky-run-engine| - Moving WAXS out of beam
|2020-11-17 14:13:44.766|INFO|27885|bluesky-session|move_instrument|70|bluesky-run-engine| - Removed WAXS from beam position
|2020-11-17 14:13:44.771|INFO|27885|bluesky-session|move_instrument|185|bluesky-run-engine| - Moving USAXS out of beam
|2020-11-17 14:13:55.351|INFO|27885|bluesky-session|move_instrument|203|bluesky-run-engine| - Removed USAXS from beam position
|2020-11-17 14:13:55.358|INFO|27885|bluesky-session|move_instrument|144|bluesky-run-engine| - Moving to Pinhole SAXS mode
|2020-11-17 14:14:02.676|INFO|27885|bluesky-session|move_instrument|174|bluesky-run-engine| - Pinhole SAXS is in position
|2020-11-17 14:14:02.679|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:08.511|INFO|27885|bluesky-session|setup_new_user|274|bluesky-run-engine| - Creating technique directory: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs
|2020-11-17 14:14:08.511|INFO|27885|bluesky-session|scans|688|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/AirBlank_0005.hdf
|2020-11-17 14:14:08.511|INFO|27885|bluesky-session|scans|690|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/AirBlank_0005.hdf
|2020-11-17 14:14:08.679|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:10.143|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:10.537|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000000.0 rate: 30460.0 max: 950000 converged=[False, True]
|2020-11-17 14:14:10.537|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 120360.0 max: 950000 converged=[False, True, True, True]
|2020-11-17 14:14:10.781|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000000.0 rate: 292900.0 max: 950000 converged=[True, True]
|2020-11-17 14:14:10.785|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 120720.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:14:10.810|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:14:16.108|INFO|27885|bluesky-session|sample_transmission|156|bluesky-run-engine| - Measured SAXS transmission values, pinDiode cts =381687.000000 with gain 100000.0 and I0 cts 1472102.0 with gain 100000000.0
|2020-11-17 14:14:17.087|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:17.467|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 850520.0 max: 950000 converged=[False, True]
|2020-11-17 14:14:17.711|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 833333.3333333334 max: 950000 converged=[True, True]
|2020-11-17 14:14:17.729|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True]
|2020-11-17 14:14:18.032|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:14:24.392|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 6.37434983253479 seconds.
|2020-11-17 14:14:24.466|INFO|27885|bluesky-session|scans|789|bluesky-run-engine| - I0 value: 429731.0
|2020-11-17 14:14:24.478|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 20: saxsExp 20 60 1 "GlassyCarbonSRM3600"
|2020-11-17 14:14:24.502|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:30.298|INFO|27885|bluesky-session|scans|688|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:14:30.298|INFO|27885|bluesky-session|scans|690|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_saxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:14:30.358|INFO|27885|bluesky-session|mode_changes|170|bluesky-run-engine| - Prepared for SAXS mode
|2020-11-17 14:14:31.795|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:32.205|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 30460.0 max: 950000 converged=[True, True]
|2020-11-17 14:14:32.207|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 113840.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:14:32.244|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:14:37.524|INFO|27885|bluesky-session|sample_transmission|156|bluesky-run-engine| - Measured SAXS transmission values, pinDiode cts =381687.000000 with gain 100000.0 and I0 cts 1472102.0 with gain 100000000.0
|2020-11-17 14:14:38.436|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:14:38.816|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 1310606060.6060605 max: 950000 converged=[True, False]
|2020-11-17 14:14:39.065|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 1882173913.0434783 max: 950000 converged=[True, False]
|2020-11-17 14:14:39.321|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86420.0 max: 950000 converged=[True, True]
|2020-11-17 14:14:39.336|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True]
|2020-11-17 14:14:39.628|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:14:45.131|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 5.519550800323486 seconds.
|2020-11-17 14:14:45.179|INFO|27885|bluesky-session|scans|789|bluesky-run-engine| - I0 value: 429245.0
|2020-11-17 14:14:45.193|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 23: waxsExp 20 20 1 "AirBlank"
|2020-11-17 14:14:45.194|DEBUG|27885|bluesky-session|scans|808|bluesky-run-engine| - waxsx start collection =0.000624999999956799
|2020-11-17 14:14:45.195|DEBUG|27885|bluesky-session|scans|812|bluesky-run-engine| - waxsx after before plan =0.000624999999956799
|2020-11-17 14:14:45.211|INFO|27885|bluesky-session|mode_changes|193|bluesky-run-engine| - Found UsaxsSaxsMode = SAXS in beam
|2020-11-17 14:14:45.211|INFO|27885|bluesky-session|mode_changes|194|bluesky-run-engine| - Moving to proper WAXS mode
|2020-11-17 14:14:45.213|INFO|27885|bluesky-session|move_instrument|113|bluesky-run-engine| - Moving SAXS out of beam
|2020-11-17 14:14:52.447|INFO|27885|bluesky-session|move_instrument|133|bluesky-run-engine| - Removed SAXS from beam position
|2020-11-17 14:14:52.453|INFO|27885|bluesky-session|move_instrument|185|bluesky-run-engine| - Moving USAXS out of beam
|2020-11-17 14:14:52.482|INFO|27885|bluesky-session|move_instrument|203|bluesky-run-engine| - Removed USAXS from beam position
|2020-11-17 14:14:52.495|INFO|27885|bluesky-session|move_instrument|81|bluesky-run-engine| - Moving to WAXS mode
|2020-11-17 14:15:03.012|INFO|27885|bluesky-session|move_instrument|102|bluesky-run-engine| - WAXS is in position
|2020-11-17 14:15:03.015|DEBUG|27885|bluesky-session|mode_changes|202|bluesky-run-engine| - guard slits horizontal difference = 0
|2020-11-17 14:15:03.015|DEBUG|27885|bluesky-session|mode_changes|203|bluesky-run-engine| - guard slits vertical difference = 0
|2020-11-17 14:15:03.016|DEBUG|27885|bluesky-session|mode_changes|218|bluesky-run-engine| - USAXS slits horizontal difference = 8.12e-05
|2020-11-17 14:15:03.016|DEBUG|27885|bluesky-session|mode_changes|219|bluesky-run-engine| - USAXS slits vertical difference = 0.0001625
|2020-11-17 14:15:03.016|INFO|27885|bluesky-session|mode_changes|229|bluesky-run-engine| - Prepared for WAXS mode
|2020-11-17 14:15:03.062|DEBUG|27885|bluesky-session|scans|816|bluesky-run-engine| - waxsx after mode_WAXS =256.50062499999996
|2020-11-17 14:15:08.113|INFO|27885|bluesky-session|setup_new_user|274|bluesky-run-engine| - Creating technique directory: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs
|2020-11-17 14:15:08.114|INFO|27885|bluesky-session|scans|851|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/AirBlank_0005.hdf
|2020-11-17 14:15:08.114|INFO|27885|bluesky-session|scans|853|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/AirBlank_0005.hdf
|2020-11-17 14:15:09.206|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:15:09.599|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86480.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:09.603|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000.0 rate: 999980.0 max: 950000 converged=[True, True, True, False]
|2020-11-17 14:15:09.852|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86340.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:09.853|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 539380.0 max: 950000 converged=[True, True, False, True]
|2020-11-17 14:15:10.102|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86240.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:10.105|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 538640.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:15:10.141|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:15:10.416|DEBUG|27885|bluesky-session|scans|928|bluesky-run-engine| - waxsx before Image collection=256.50062499999996
|2020-11-17 14:15:10.429|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:15:15.471|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 25.0s remaining
|2020-11-17 14:15:20.436|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 20.0s remaining
|2020-11-17 14:15:25.453|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 15.0s remaining
|2020-11-17 14:15:30.469|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 10.0s remaining
|2020-11-17 14:15:35.437|INFO|27885|bluesky-session|reporter|28|Thread-2048| - WAXS: 5.0s remaining
|2020-11-17 14:15:41.833|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 31.417147874832153 seconds.
|2020-11-17 14:15:41.892|INFO|27885|bluesky-session|scans|957|bluesky-run-engine| - I0 value: 2591974.0
|2020-11-17 14:15:41.905|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 24: waxsExp 20 60 1 "GlassyCarbonSRM3600"
|2020-11-17 14:15:41.907|DEBUG|27885|bluesky-session|scans|808|bluesky-run-engine| - waxsx start collection =256.50062499999996
|2020-11-17 14:15:41.907|DEBUG|27885|bluesky-session|scans|812|bluesky-run-engine| - waxsx after before plan =256.50062499999996
|2020-11-17 14:15:41.984|DEBUG|27885|bluesky-session|mode_changes|190|bluesky-run-engine| - WAXS is in beam
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|202|bluesky-run-engine| - guard slits horizontal difference = 0
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|203|bluesky-run-engine| - guard slits vertical difference = 0
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|218|bluesky-run-engine| - USAXS slits horizontal difference = 8.12e-05
|2020-11-17 14:15:41.985|DEBUG|27885|bluesky-session|mode_changes|219|bluesky-run-engine| - USAXS slits vertical difference = 0.0001625
|2020-11-17 14:15:41.986|INFO|27885|bluesky-session|mode_changes|229|bluesky-run-engine| - Prepared for WAXS mode
|2020-11-17 14:15:42.019|DEBUG|27885|bluesky-session|scans|816|bluesky-run-engine| - waxsx after mode_WAXS =256.50062499999996
|2020-11-17 14:15:47.047|INFO|27885|bluesky-session|scans|851|bluesky-run-engine| - Area Detector HDF5 file: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:15:47.047|INFO|27885|bluesky-session|scans|853|bluesky-run-engine| - Pilatus computer Area Detector HDF5 file: /mnt/usaxscontrol/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_waxs/GlassyCarbonSRM3600_0006.hdf
|2020-11-17 14:15:48.011|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:15:48.403|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 86560.0 max: 950000 converged=[True, True]
|2020-11-17 14:15:48.407|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 508180.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:15:48.455|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:15:48.734|DEBUG|27885|bluesky-session|scans|928|bluesky-run-engine| - waxsx before Image collection=256.50062499999996
|2020-11-17 14:15:48.751|DEBUG|27885|bluesky-session|area_detector|34|bluesky-run-engine| - areaDetectorAcquire(): OrderedDict([('enable', 1), ('auto_increment', 'Yes'), ('array_counter', 0), ('auto_save', 'Yes'), ('num_capture', 0), ('file_template', '%s%s_%4.4d.hdf'), ('file_write_mode', 'Single'), ('blocking_callbacks', 'No'), ('parent.cam.array_callbacks', 1)])
|2020-11-17 14:15:53.793|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 25.0s remaining
|2020-11-17 14:15:58.766|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 20.0s remaining
|2020-11-17 14:16:03.777|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 15.0s remaining
|2020-11-17 14:16:08.803|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 10.0s remaining
|2020-11-17 14:16:13.768|INFO|27885|bluesky-session|reporter|28|Thread-2252| - WAXS: 5.0s remaining
|2020-11-17 14:16:19.301|INFO|27885|bluesky-session|area_detector|47|bluesky-run-engine| - Finished SAXS/WAXS data collection in 30.56360387802124 seconds.
|2020-11-17 14:16:19.562|INFO|27885|bluesky-session|scans|957|bluesky-run-engine| - I0 value: 2590638.0
|2020-11-17 14:16:19.579|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 26: preUSAXStune
|2020-11-17 14:16:23.016|INFO|27885|bluesky-session|mode_changes|112|bluesky-run-engine| - Found UsaxsSaxsMode = WAXS in beam
|2020-11-17 14:16:23.016|INFO|27885|bluesky-session|mode_changes|113|bluesky-run-engine| - Moving to proper USAXS mode
|2020-11-17 14:16:23.021|INFO|27885|bluesky-session|move_instrument|59|bluesky-run-engine| - Moving WAXS out of beam
|2020-11-17 14:16:33.503|INFO|27885|bluesky-session|move_instrument|70|bluesky-run-engine| - Removed WAXS from beam position
|2020-11-17 14:16:33.511|INFO|27885|bluesky-session|move_instrument|113|bluesky-run-engine| - Moving SAXS out of beam
|2020-11-17 14:16:33.525|INFO|27885|bluesky-session|move_instrument|133|bluesky-run-engine| - Removed SAXS from beam position
|2020-11-17 14:16:33.545|INFO|27885|bluesky-session|move_instrument|214|bluesky-run-engine| - Moving to USAXS mode
|2020-11-17 14:16:44.147|INFO|27885|bluesky-session|move_instrument|242|bluesky-run-engine| - USAXS is in position
|2020-11-17 14:16:44.149|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:16:44.667|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:16:44.943|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: m_stage_r
|2020-11-17 14:16:44.946|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:16:45.349|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 624180.0 max: 950000 converged=[True, True]
|2020-11-17 14:16:45.351|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 312240.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:16:45.351|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1800.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:16:45.383|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:16:45.403|INFO|27885|bluesky-session|axis_tuning|118|bluesky-run-engine| - Tuning axis m_stage_r, current position is 9.059807
|2020-11-17 14:16:59.016|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ===========================
key result
================ ===========================
x m_stage_r
y I0_USAXS
cen 9.059839376418388
com 9.059838127744769
fwhm 0.0012467757926177825
min [ 9.058557 421. ]
max [9.059974e+00 3.140400e+04]
crossings [9.05921599 9.06046276]
tune_ok True
center 9.059838127744769
initial_position 9.059807
final_position 9.059838127744769
================ ===========================
|2020-11-17 14:16:59.017|INFO|27885|bluesky-session|axis_tuning|127|bluesky-run-engine| - Tuning axis m_stage_r, final position is 9.059838
|2020-11-17 14:16:59.226|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: m_stage_r
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 9.059807
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (9.059973999999999, 31404.0)
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 9.059839376418388
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 9.059838127744769
|2020-11-17 14:16:59.227|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.0012467757926177825
|2020-11-17 14:16:59.228|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 9.059838
|2020-11-17 14:17:00.441|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r
|2020-11-17 14:17:00.444|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:17:00.850|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 593380.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:00.852|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 313760.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:00.853|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1820.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:17:00.900|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:17:00.942|INFO|27885|bluesky-session|axis_tuning|222|bluesky-run-engine| - Tuning axis a_stage_r, current position is 8.7468757
|2020-11-17 14:17:16.065|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ ===========================
key result
================ ===========================
x a_stage_r
y PD_USAXS
cen 8.746955269003653
com 8.74694818799869
fwhm 0.00051833940621826
min [8.7473169 2. ]
max [8.746964e+00 6.522100e+04]
crossings [8.7466961 8.74721444]
tune_ok True
center 8.74694818799869
initial_position 8.7468757
final_position 8.74694818799869
================ ===========================
|2020-11-17 14:17:16.066|INFO|27885|bluesky-session|axis_tuning|231|bluesky-run-engine| - Tuning axis a_stage_r, final position is 8.7469482
|2020-11-17 14:17:16.587|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r
|2020-11-17 14:17:16.587|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 8.7468757
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (8.746964, 65221.0)
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 8.746955269003653
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 8.74694818799869
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 0.00051833940621826
|2020-11-17 14:17:16.588|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 8.7468757
|2020-11-17 14:17:17.924|INFO|27885|bluesky-session|axis_tuning|56|bluesky-run-engine| - tuning axis: a_stage_r2p
|2020-11-17 14:17:17.927|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:17:18.333|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 601160.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:18.335|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 314760.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:18.336|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1820.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:17:18.378|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:17:18.396|INFO|27885|bluesky-session|axis_tuning|289|bluesky-run-engine| - Tuning axis a_stage_r2p, current position is 46.1302
|2020-11-17 14:17:23.105|INFO|27885|bluesky-session|axis_tuning_patches|100|bluesky-run-engine| - PeakStats
================ =================================================
key result
================ =================================================
x a_stage_r2p
y PD_USAXS
cen 46.21770183843965
com 45.77260666059711
fwhm 2.0894698967413845
min [47.6302 1. ]
max [4.59635e+01 6.17300e+04]
crossings [44.74551552 46.53165177 46.75865465 46.83498542]
tune_ok True
center 45.77260666059711
initial_position 46.1302
final_position 45.77260666059711
================ =================================================
|2020-11-17 14:17:23.107|INFO|27885|bluesky-session|axis_tuning|302|bluesky-run-engine| - Tuning axis a_stage_r2p, final position is 45.772600000000004
|2020-11-17 14:17:23.335|INFO|27885|bluesky-session|axis_tuning|70|bluesky-run-engine| - axis: a_stage_r2p
|2020-11-17 14:17:23.335|INFO|27885|bluesky-session|axis_tuning|71|bluesky-run-engine| - starting position: 46.1302
|2020-11-17 14:17:23.335|INFO|27885|bluesky-session|axis_tuning|72|bluesky-run-engine| - peak detected: True
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|74|bluesky-run-engine| - max: (45.9635, 61730.0)
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|75|bluesky-run-engine| - center: 46.21770183843965
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|76|bluesky-run-engine| - centroid: 45.77260666059711
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|77|bluesky-run-engine| - fwhm: 2.0894698967413845
|2020-11-17 14:17:23.336|INFO|27885|bluesky-session|axis_tuning|78|bluesky-run-engine| - final position: 45.772600000000004
|2020-11-17 14:17:24.451|INFO|27885|bluesky-session|scans|143|bluesky-run-engine| - USAXS count time: {terms.USAXS.usaxs_time.get()} second(s)
|2020-11-17 14:17:24.471|INFO|27885|bluesky-session|command_list|397|bluesky-run-engine| - file line 29: USAXSscan 20 20 1 "AirBlank"
|2020-11-17 14:17:24.513|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:17:25.021|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:17:30.115|INFO|27885|bluesky-session|setup_new_user|274|bluesky-run-engine| - Creating technique directory: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_usaxs
|2020-11-17 14:17:30.465|INFO|27885|bluesky-session|mode_changes|119|bluesky-run-engine| - Preparing for USAXS mode ... please wait ...
|2020-11-17 14:17:30.977|INFO|27885|bluesky-session|mode_changes|135|bluesky-run-engine| - Prepared for USAXS mode
|2020-11-17 14:17:34.088|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: I0_USAXS
|2020-11-17 14:17:34.476|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 108800.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:34.477|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=100000.0 rate: 298840.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:34.511|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True]
|2020-11-17 14:17:40.705|INFO|27885|bluesky-session|sample_transmission|91|bluesky-run-engine| - Measured USAXS transmission values:
======== ============= ==========
detector counts gain
======== ============= ==========
pinDiode 897075.000000 100000.0
I0 326459.000000 10000000.0
======== ============= ==========
|2020-11-17 14:17:40.927|INFO|27885|bluesky-session|amplifiers|555|bluesky-run-engine| - Autoscaling amplifier for: PD_USAXS
|2020-11-17 14:17:41.336|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000.0 rate: 684280.0 max: 950000 converged=[True, True]
|2020-11-17 14:17:41.338|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=10000000.0 rate: 313800.0 max: 950000 converged=[True, True, True, True]
|2020-11-17 14:17:41.340|DEBUG|27885|bluesky-session|amplifiers|514|bluesky-run-engine| - gain=1000000000.0 rate: 1800.0 max: 950000 converged=[True, True, True, True, True, True]
|2020-11-17 14:17:41.383|DEBUG|27885|bluesky-session|amplifiers|520|bluesky-run-engine| - converged: [True, True, True, True, True, True]
|2020-11-17 14:17:41.939|INFO|27885|bluesky-session|usaxs_fly_scan|143|Thread-3525| - HDF5 config: /share1/AreaDetectorConfig/FlyScan_config/saveFlyData.xml
|2020-11-17 14:17:41.940|INFO|27885|bluesky-session|usaxs_fly_scan|144|Thread-3525| - HDF5 output: /share1/USAXS_data/2020-11/11_17_ComissBS/11_17_ComissBS_usaxs/AirBlank_0005.h5
|2020-11-17 14:17:41.941|DEBUG|27885|bluesky-session|usaxs_fly_scan|99|Thread-3527| - progress_reporting has arrived
|2020-11-17 14:17:42.001|INFO|27885|bluesky-session|usaxs_fly_scan|106|Thread-3527| - flying, s ar, deg ay, mm dy, mm channel elapsed, s
|2020-11-17 14:17:46.941|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 5.00 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:17:51.943|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 10.00 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:17:56.943|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 15.00 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:01.948|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 20.01 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:06.953|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 25.01 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:11.959|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 30.02 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:16.963|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 35.02 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:21.971|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 40.03 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:26.973|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 45.03 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:31.975|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 50.04 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:36.978|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 55.04 8.7487005 0.00612 12.91725 0 0.00
|2020-11-17 14:18:41.978|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 60.04 8.7474221 0.00134 12.89540 43 4.47
|2020-11-17 14:18:46.981|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 65.04 8.7465670 -0.00160 12.88191 77 9.48
|2020-11-17 14:18:51.991|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 70.05 8.7442744 -0.00979 12.84332 158 14.48
|2020-11-17 14:18:57.006|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 75.06 8.7387945 -0.02978 12.75383 324 19.50
|2020-11-17 14:19:02.010|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 80.07 8.7288428 -0.06548 12.58796 578 24.50
|2020-11-17 14:19:07.014|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 85.07 8.7125184 -0.12444 12.32028 916 29.52
|2020-11-17 14:19:12.017|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 90.08 8.6879521 -0.21221 11.91334 1320 34.52
|2020-11-17 14:19:17.025|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 95.09 8.6530330 -0.33540 11.34481 1780 39.52
|2020-11-17 14:19:22.033|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 100.09 8.6065840 -0.49936 10.59277 2284 44.53
|2020-11-17 14:19:27.042|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 105.10 8.5451042 -0.71911 9.60428 2820 49.53
|2020-11-17 14:19:32.043|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 110.10 8.4681207 -0.98864 8.34250 3382 54.53
|2020-11-17 14:19:37.051|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 115.11 8.3700480 -1.33069 6.76414 3967 59.55
|2020-11-17 14:19:42.061|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 120.12 8.2544121 -1.74213 4.87822 4566 64.55
|2020-11-17 14:19:47.071|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 125.13 8.1117977 -2.24406 2.56832 5181 69.57
|2020-11-17 14:19:52.084|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 130.14 7.9420729 -2.82694 -0.17056 5802 74.55
|2020-11-17 14:19:57.082|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 135.14 7.7483276 -3.52310 -3.30210 6436 79.59
|2020-11-17 14:20:02.089|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 140.15 7.5175999 -4.33461 -7.04691 7077 84.59
|2020-11-17 14:20:07.095|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 145.16 7.2594410 -5.24235 -11.22207 7722 89.59
|2020-11-17 14:20:12.101|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 150.16 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:17.106|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 155.17 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:22.108|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 160.17 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:27.118|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 165.18 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:32.120|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 170.18 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:37.128|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 175.19 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:42.135|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 180.20 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:47.141|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 185.20 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:52.148|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 190.21 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:20:57.151|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 195.21 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:02.156|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 200.22 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:07.159|DEBUG|27885|bluesky-session|usaxs_fly_scan|111|Thread-3527| - 205.22 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:11.951|INFO|27885|bluesky-session|usaxs_fly_scan|115|Thread-3527| - 210.01 7.0901130 -5.78505 -13.72213 7999 93.65
|2020-11-17 14:21:11.952|ERROR|27885|bluesky-session|usaxs_fly_scan|118|Thread-3527| - 210.01355910301208s - progress_reporting timeout!!
```
</details>
Looking at the recent console output, this helps:
<details>
```
D Tue-14:17:41 - progress_reporting has arrived
I Tue-14:17:42 - flying, s ar, deg ay, mm dy, mm channel elapsed, s
D Tue-14:17:46 - 5.00 8.7487005 0.00612 12.91725 0 0.00
D Tue-14:17:51 - 10.00 8.7487005 0.00612 12.91725 0 0.00
---------------------------------------------------------------------------
FailedStatus Traceback (most recent call last)
<ipython-input-3-04b994fdd9b0> in <module>
----> 1 RE(run_command_file("usaxs.mac"))
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in __call__(self, *args, **metadata_kw)
805 self._task_fut.add_done_callback(set_blocking_event)
806
--> 807 self._resume_task(init_func=_build_task)
808
809 if self._interrupted:
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in _resume_task(self, init_func)
929 if (exc is not None
930 and not isinstance(exc, _RunEnginePanic)):
--> 931 raise exc
932
933 def install_suspender(self, suspender):
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in _run(self)
1498 exit_reason = str(err)
1499 self.log.exception("Run aborted")
-> 1500 raise err
1501 finally:
1502 if not exit_reason:
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/run_engine.py in _run(self)
1339 # throw the exception at the current plan
1340 try:
-> 1341 msg = self._plan_stack[-1].throw(
1342 stashed_exception or resp)
1343 except Exception as e:
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in __call__(self, plan)
1305 plan = monitor_during_wrapper(plan, self.monitors)
1306 plan = baseline_wrapper(plan, self.baseline)
-> 1307 return (yield from plan)
1308
1309
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in baseline_wrapper(plan, devices, name)
1160 return (yield from plan)
1161 else:
-> 1162 return (yield from plan_mutator(plan, insert_baseline))
1163
1164
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in monitor_during_wrapper(plan, signals)
801 plan1 = plan_mutator(plan, insert_after_open)
802 plan2 = plan_mutator(plan1, insert_before_close)
--> 803 return (yield from plan2)
804
805
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in fly_during_wrapper(plan, flyers)
859 plan1 = plan_mutator(plan, insert_after_open)
860 plan2 = plan_mutator(plan1, insert_before_close)
--> 861 return (yield from plan2)
862
863
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
76 # if we have a stashed exception, pass it along
77 try:
---> 78 msg = plan_stack[-1].throw(exception)
79 except StopIteration as e:
80 # discard the exhausted generator
~/.ipython/profile_bluesky/startup/instrument/plans/command_list.py in run_command_file(filename, md)
339 """
340 commands = get_command_list(filename)
--> 341 yield from execute_command_list(filename, commands)
342
343
~/.ipython/profile_bluesky/startup/instrument/plans/command_list.py in execute_command_list(filename, commands, md)
417 snm = args[3]
418 _md.update(dict(sx=sx, sy=sy, thickness=sth, title=snm))
--> 419 yield from USAXSscan(sx, sy, sth, snm, md=_md) # either step or fly scan
420
421 elif action in ("saxs", "saxsexp"):
~/.ipython/profile_bluesky/startup/instrument/plans/scans.py in USAXSscan(x, y, thickness_mm, title, md)
234 _md["title"] = title
235 if terms.FlyScan.use_flyscan.get():
--> 236 yield from Flyscan(x, y, thickness_mm, title, md=_md)
237 else:
238 yield from USAXSscanStep(x, y, thickness_mm, title, md=_md)
~/.ipython/profile_bluesky/startup/instrument/plans/scans.py in Flyscan(pos_X, pos_Y, thickness, scan_title, md)
580 yield from record_sample_image_on_demand("usaxs", scan_title_clean, _md)
581
--> 582 yield from usaxs_flyscan.plan(md=_md) # DO THE FLY SCAN
583
584 yield from bps.mv(
~/.ipython/profile_bluesky/startup/instrument/devices/usaxs_fly_scan.py in plan(self, md)
198 yield from bps.abs_set(self.flying, True)
199
--> 200 yield from bps.wait(group=g)
201 yield from bps.abs_set(self.flying, False)
202 elapsed = time.time() - self.t0
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/plan_stubs.py in wait(group)
465 Msg('wait', None, group=group)
466 """
--> 467 return (yield Msg('wait', None, group=group))
468
469
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
/share1/bluesky/conda_envs/bluesky_2020_9/lib/python3.8/site-packages/bluesky/preprocessors.py in plan_mutator(plan, msg_proc)
193 try:
194 # yield out the 'current message' and collect the return
--> 195 inner_ret = yield msg
196 except GeneratorExit:
197 # special case GeneratorExit. We must clean up all of our plans
FailedStatus: Status(obj=EpicsSignal(read_pv='9idcLAX:USAXSfly:Start', name='usaxs_flyscan_busy', parent='usaxs_flyscan', value=1, timestamp=1605644261.927068, auto_monitor=True, string=True, write_pv='9idcLAX:USAXSfly:Start', limits=False, put_complete=True), done=True, success=False)
```
</details>
It's a FailedStatus on the fly scan start button: `9idcLAX:USAXSfly:Start` (ophyd object: `usaxs_flyscan.busy`)
Could not interrupt the RunEngine with ^C. Used ^\ to stop the ipython session. Command line did not show what was being typed so had to create new terminal sessions to restore normal operations. Ugly. | priority | flyscan start failed status object nothing obvious in the logs info bluesky session command list bluesky run engine command file usaxs mac line action parameters current experiment name saxsexp airblank saxsexp waxsexp airblank waxsexp preusaxstune usaxsscan airblank usaxsscan info bluesky session amplifiers bluesky run engine measuring background for pd usaxs info bluesky session amplifiers bluesky run engine pd usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine tr diode range gain bkg info bluesky session amplifiers bluesky run engine pd usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine tr diode range gain bkg info bluesky session amplifiers bluesky run engine pd usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine tr diode range gain bkg info bluesky session amplifiers bluesky run engine pd usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine tr diode range gain bkg info bluesky session amplifiers bluesky run engine pd usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine usaxs range gain bkg info bluesky session amplifiers bluesky run engine tr diode range gain bkg info bluesky session command list bluesky run engine runing preusaxstune as requested at start of measurements info bluesky session mode changes bluesky run engine preparing for usaxs mode please wait info bluesky session mode changes bluesky run engine prepared for usaxs mode info bluesky session axis tuning bluesky run engine tuning axis m stage r info bluesky session amplifiers bluesky run engine autoscaling amplifier for pd usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session axis tuning bluesky run engine tuning axis m stage r current position is info bluesky session axis tuning patches bluesky run engine peakstats key result x m stage r y usaxs cen com fwhm min max crossings tune ok true center initial position final position info bluesky session axis tuning bluesky run engine tuning axis m stage r final position is info bluesky session axis tuning bluesky run engine axis m stage r info bluesky session axis tuning bluesky run engine starting position info bluesky session axis tuning bluesky run engine peak detected true info bluesky session axis tuning bluesky run engine max info bluesky session axis tuning bluesky run engine center info bluesky session axis tuning bluesky run engine centroid info bluesky session axis tuning bluesky run engine fwhm info bluesky session axis tuning bluesky run engine final position info bluesky session axis tuning bluesky run engine tuning axis a stage r info bluesky session amplifiers bluesky run engine autoscaling amplifier for pd usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session axis tuning bluesky run engine tuning axis a stage r current position is info bluesky session axis tuning patches bluesky run engine peakstats key result x a stage r y pd usaxs cen com fwhm min max crossings tune ok true center initial position final position info bluesky session axis tuning bluesky run engine tuning axis a stage r final position is info bluesky session axis tuning bluesky run engine axis a stage r info bluesky session axis tuning bluesky run engine starting position info bluesky session axis tuning bluesky run engine peak detected true info bluesky session axis tuning bluesky run engine max info bluesky session axis tuning bluesky run engine center info bluesky session axis tuning bluesky run engine centroid info bluesky session axis tuning bluesky run engine fwhm info bluesky session axis tuning bluesky run engine final position info bluesky session axis tuning bluesky run engine tuning axis a stage info bluesky session amplifiers bluesky run engine autoscaling amplifier for pd usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session axis tuning bluesky run engine tuning axis a stage current position is info bluesky session axis tuning patches bluesky run engine peakstats key result x a stage y pd usaxs cen com fwhm min max crossings tune ok true center initial position final position info bluesky session axis tuning bluesky run engine tuning axis a stage final position is info bluesky session axis tuning bluesky run engine axis a stage info bluesky session axis tuning bluesky run engine starting position info bluesky session axis tuning bluesky run engine peak detected true info bluesky session axis tuning bluesky run engine max info bluesky session axis tuning bluesky run engine center info bluesky session axis tuning bluesky run engine centroid info bluesky session axis tuning bluesky run engine fwhm info bluesky session axis tuning bluesky run engine final position info bluesky session scans bluesky run engine usaxs count time terms usaxs usaxs time get second s info bluesky session command list bluesky run engine synchronizing detector order numbers to info bluesky session command list bluesky run engine file line current experiment name info bluesky session command list bluesky run engine no handling for line current experiment name info bluesky session command list bluesky run engine file line saxsexp airblank info bluesky session mode changes bluesky run engine found usaxssaxsmode usaxs in beam info bluesky session mode changes bluesky run engine moving to proper saxs mode info bluesky session move instrument bluesky run engine moving waxs out of beam info bluesky session move instrument bluesky run engine removed waxs from beam position info bluesky session move instrument bluesky run engine moving usaxs out of beam info bluesky session move instrument bluesky run engine removed usaxs from beam position info bluesky session move instrument bluesky run engine moving to pinhole saxs mode info bluesky session move instrument bluesky run engine pinhole saxs is in position info bluesky session mode changes bluesky run engine prepared for saxs mode info bluesky session setup new user bluesky run engine creating technique directory usaxs data comissbs comissbs saxs info bluesky session scans bluesky run engine area detector file usaxs data comissbs comissbs saxs airblank hdf info bluesky session scans bluesky run engine pilatus computer area detector file mnt usaxscontrol usaxs data comissbs comissbs saxs airblank hdf info bluesky session mode changes bluesky run engine prepared for saxs mode info bluesky session amplifiers bluesky run engine autoscaling amplifier for usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session sample transmission bluesky run engine measured saxs transmission values pindiode cts with gain and cts with gain info bluesky session amplifiers bluesky run engine autoscaling amplifier for usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged debug bluesky session area detector bluesky run engine areadetectoracquire ordereddict info bluesky session area detector bluesky run engine finished saxs waxs data collection in seconds info bluesky session scans bluesky run engine value info bluesky session command list bluesky run engine file line saxsexp info bluesky session mode changes bluesky run engine prepared for saxs mode info bluesky session scans bluesky run engine area detector file usaxs data comissbs comissbs saxs hdf info bluesky session scans bluesky run engine pilatus computer area detector file mnt usaxscontrol usaxs data comissbs comissbs saxs hdf info bluesky session mode changes bluesky run engine prepared for saxs mode info bluesky session amplifiers bluesky run engine autoscaling amplifier for usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session sample transmission bluesky run engine measured saxs transmission values pindiode cts with gain and cts with gain info bluesky session amplifiers bluesky run engine autoscaling amplifier for usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged debug bluesky session area detector bluesky run engine areadetectoracquire ordereddict info bluesky session area detector bluesky run engine finished saxs waxs data collection in seconds info bluesky session scans bluesky run engine value info bluesky session command list bluesky run engine file line waxsexp airblank debug bluesky session scans bluesky run engine waxsx start collection debug bluesky session scans bluesky run engine waxsx after before plan info bluesky session mode changes bluesky run engine found usaxssaxsmode saxs in beam info bluesky session mode changes bluesky run engine moving to proper waxs mode info bluesky session move instrument bluesky run engine moving saxs out of beam info bluesky session move instrument bluesky run engine removed saxs from beam position info bluesky session move instrument bluesky run engine moving usaxs out of beam info bluesky session move instrument bluesky run engine removed usaxs from beam position info bluesky session move instrument bluesky run engine moving to waxs mode info bluesky session move instrument bluesky run engine waxs is in position debug bluesky session mode changes bluesky run engine guard slits horizontal difference debug bluesky session mode changes bluesky run engine guard slits vertical difference debug bluesky session mode changes bluesky run engine usaxs slits horizontal difference debug bluesky session mode changes bluesky run engine usaxs slits vertical difference info bluesky session mode changes bluesky run engine prepared for waxs mode debug bluesky session scans bluesky run engine waxsx after mode waxs info bluesky session setup new user bluesky run engine creating technique directory usaxs data comissbs comissbs waxs info bluesky session scans bluesky run engine area detector file usaxs data comissbs comissbs waxs airblank hdf info bluesky session scans bluesky run engine pilatus computer area detector file mnt usaxscontrol usaxs data comissbs comissbs waxs airblank hdf info bluesky session amplifiers bluesky run engine autoscaling amplifier for usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged debug bluesky session scans bluesky run engine waxsx before image collection debug bluesky session area detector bluesky run engine areadetectoracquire ordereddict info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session area detector bluesky run engine finished saxs waxs data collection in seconds info bluesky session scans bluesky run engine value info bluesky session command list bluesky run engine file line waxsexp debug bluesky session scans bluesky run engine waxsx start collection debug bluesky session scans bluesky run engine waxsx after before plan debug bluesky session mode changes bluesky run engine waxs is in beam debug bluesky session mode changes bluesky run engine guard slits horizontal difference debug bluesky session mode changes bluesky run engine guard slits vertical difference debug bluesky session mode changes bluesky run engine usaxs slits horizontal difference debug bluesky session mode changes bluesky run engine usaxs slits vertical difference info bluesky session mode changes bluesky run engine prepared for waxs mode debug bluesky session scans bluesky run engine waxsx after mode waxs info bluesky session scans bluesky run engine area detector file usaxs data comissbs comissbs waxs hdf info bluesky session scans bluesky run engine pilatus computer area detector file mnt usaxscontrol usaxs data comissbs comissbs waxs hdf info bluesky session amplifiers bluesky run engine autoscaling amplifier for usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged debug bluesky session scans bluesky run engine waxsx before image collection debug bluesky session area detector bluesky run engine areadetectoracquire ordereddict info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session reporter thread waxs remaining info bluesky session area detector bluesky run engine finished saxs waxs data collection in seconds info bluesky session scans bluesky run engine value info bluesky session command list bluesky run engine file line preusaxstune info bluesky session mode changes bluesky run engine found usaxssaxsmode waxs in beam info bluesky session mode changes bluesky run engine moving to proper usaxs mode info bluesky session move instrument bluesky run engine moving waxs out of beam info bluesky session move instrument bluesky run engine removed waxs from beam position info bluesky session move instrument bluesky run engine moving saxs out of beam info bluesky session move instrument bluesky run engine removed saxs from beam position info bluesky session move instrument bluesky run engine moving to usaxs mode info bluesky session move instrument bluesky run engine usaxs is in position info bluesky session mode changes bluesky run engine preparing for usaxs mode please wait info bluesky session mode changes bluesky run engine prepared for usaxs mode info bluesky session axis tuning bluesky run engine tuning axis m stage r info bluesky session amplifiers bluesky run engine autoscaling amplifier for pd usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session axis tuning bluesky run engine tuning axis m stage r current position is info bluesky session axis tuning patches bluesky run engine peakstats key result x m stage r y usaxs cen com fwhm min max crossings tune ok true center initial position final position info bluesky session axis tuning bluesky run engine tuning axis m stage r final position is info bluesky session axis tuning bluesky run engine axis m stage r info bluesky session axis tuning bluesky run engine starting position info bluesky session axis tuning bluesky run engine peak detected true info bluesky session axis tuning bluesky run engine max info bluesky session axis tuning bluesky run engine center info bluesky session axis tuning bluesky run engine centroid info bluesky session axis tuning bluesky run engine fwhm info bluesky session axis tuning bluesky run engine final position info bluesky session axis tuning bluesky run engine tuning axis a stage r info bluesky session amplifiers bluesky run engine autoscaling amplifier for pd usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session axis tuning bluesky run engine tuning axis a stage r current position is info bluesky session axis tuning patches bluesky run engine peakstats key result x a stage r y pd usaxs cen com fwhm min max crossings tune ok true center initial position final position info bluesky session axis tuning bluesky run engine tuning axis a stage r final position is info bluesky session axis tuning bluesky run engine axis a stage r info bluesky session axis tuning bluesky run engine starting position info bluesky session axis tuning bluesky run engine peak detected true info bluesky session axis tuning bluesky run engine max info bluesky session axis tuning bluesky run engine center info bluesky session axis tuning bluesky run engine centroid info bluesky session axis tuning bluesky run engine fwhm info bluesky session axis tuning bluesky run engine final position info bluesky session axis tuning bluesky run engine tuning axis a stage info bluesky session amplifiers bluesky run engine autoscaling amplifier for pd usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session axis tuning bluesky run engine tuning axis a stage current position is info bluesky session axis tuning patches bluesky run engine peakstats key result x a stage y pd usaxs cen com fwhm min max crossings tune ok true center initial position final position info bluesky session axis tuning bluesky run engine tuning axis a stage final position is info bluesky session axis tuning bluesky run engine axis a stage info bluesky session axis tuning bluesky run engine starting position info bluesky session axis tuning bluesky run engine peak detected true info bluesky session axis tuning bluesky run engine max info bluesky session axis tuning bluesky run engine center info bluesky session axis tuning bluesky run engine centroid info bluesky session axis tuning bluesky run engine fwhm info bluesky session axis tuning bluesky run engine final position info bluesky session scans bluesky run engine usaxs count time terms usaxs usaxs time get second s info bluesky session command list bluesky run engine file line usaxsscan airblank info bluesky session mode changes bluesky run engine preparing for usaxs mode please wait info bluesky session mode changes bluesky run engine prepared for usaxs mode info bluesky session setup new user bluesky run engine creating technique directory usaxs data comissbs comissbs usaxs info bluesky session mode changes bluesky run engine preparing for usaxs mode please wait info bluesky session mode changes bluesky run engine prepared for usaxs mode info bluesky session amplifiers bluesky run engine autoscaling amplifier for usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session sample transmission bluesky run engine measured usaxs transmission values detector counts gain pindiode info bluesky session amplifiers bluesky run engine autoscaling amplifier for pd usaxs debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine gain rate max converged debug bluesky session amplifiers bluesky run engine converged info bluesky session usaxs fly scan thread config areadetectorconfig flyscan config saveflydata xml info bluesky session usaxs fly scan thread output usaxs data comissbs comissbs usaxs airblank debug bluesky session usaxs fly scan thread progress reporting has arrived info bluesky session usaxs fly scan thread flying s ar deg ay mm dy mm channel elapsed s debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread debug bluesky session usaxs fly scan thread info bluesky session usaxs fly scan thread error bluesky session usaxs fly scan thread progress reporting timeout looking at the recent console output this helps d tue progress reporting has arrived i tue flying s ar deg ay mm dy mm channel elapsed s d tue d tue failedstatus traceback most recent call last in re run command file usaxs mac bluesky conda envs bluesky lib site packages bluesky run engine py in call self args metadata kw self task fut add done callback set blocking event self resume task init func build task if self interrupted bluesky conda envs bluesky lib site packages bluesky run engine py in resume task self init func if exc is not none and not isinstance exc runenginepanic raise exc def install suspender self suspender bluesky conda envs bluesky lib site packages bluesky run engine py in run self exit reason str err self log exception run aborted raise err finally if not exit reason bluesky conda envs bluesky lib site packages bluesky run engine py in run self throw the exception at the current plan try msg self plan stack throw stashed exception or resp except exception as e bluesky conda envs bluesky lib site packages bluesky preprocessors py in call self plan plan monitor during wrapper plan self monitors plan baseline wrapper plan self baseline return yield from plan bluesky conda envs bluesky lib site packages bluesky preprocessors py in baseline wrapper plan devices name return yield from plan else return yield from plan mutator plan insert baseline bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc if we have a stashed exception pass it along try msg plan stack throw exception except stopiteration as e discard the exhausted generator bluesky conda envs bluesky lib site packages bluesky preprocessors py in monitor during wrapper plan signals plan mutator plan insert after open plan mutator insert before close return yield from bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc if we have a stashed exception pass it along try msg plan stack throw exception except stopiteration as e discard the exhausted generator bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc if we have a stashed exception pass it along try msg plan stack throw exception except stopiteration as e discard the exhausted generator bluesky conda envs bluesky lib site packages bluesky preprocessors py in fly during wrapper plan flyers plan mutator plan insert after open plan mutator insert before close return yield from bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc if we have a stashed exception pass it along try msg plan stack throw exception except stopiteration as e discard the exhausted generator bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc if we have a stashed exception pass it along try msg plan stack throw exception except stopiteration as e discard the exhausted generator ipython profile bluesky startup instrument plans command list py in run command file filename md commands get command list filename yield from execute command list filename commands ipython profile bluesky startup instrument plans command list py in execute command list filename commands md snm args md update dict sx sx sy sy thickness sth title snm yield from usaxsscan sx sy sth snm md md either step or fly scan elif action in saxs saxsexp ipython profile bluesky startup instrument plans scans py in usaxsscan x y thickness mm title md md title if terms flyscan use flyscan get yield from flyscan x y thickness mm title md md else yield from usaxsscanstep x y thickness mm title md md ipython profile bluesky startup instrument plans scans py in flyscan pos x pos y thickness scan title md yield from record sample image on demand usaxs scan title clean md yield from usaxs flyscan plan md md do the fly scan yield from bps mv ipython profile bluesky startup instrument devices usaxs fly scan py in plan self md yield from bps abs set self flying true yield from bps wait group g yield from bps abs set self flying false elapsed time time self bluesky conda envs bluesky lib site packages bluesky plan stubs py in wait group msg wait none group group return yield msg wait none group group bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc try yield out the current message and collect the return inner ret yield msg except generatorexit special case generatorexit we must clean up all of our plans bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc try yield out the current message and collect the return inner ret yield msg except generatorexit special case generatorexit we must clean up all of our plans bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc try yield out the current message and collect the return inner ret yield msg except generatorexit special case generatorexit we must clean up all of our plans bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc try yield out the current message and collect the return inner ret yield msg except generatorexit special case generatorexit we must clean up all of our plans bluesky conda envs bluesky lib site packages bluesky preprocessors py in plan mutator plan msg proc try yield out the current message and collect the return inner ret yield msg except generatorexit special case generatorexit we must clean up all of our plans failedstatus status obj epicssignal read pv usaxsfly start name usaxs flyscan busy parent usaxs flyscan value timestamp auto monitor true string true write pv usaxsfly start limits false put complete true done true success false it s a failedstatus on the fly scan start button usaxsfly start ophyd object usaxs flyscan busy could not interrupt the runengine with c used to stop the ipython session command line did not show what was being typed so had to create new terminal sessions to restore normal operations ugly | 1 |
542,607 | 15,863,350,640 | IssuesEvent | 2021-04-08 12:43:51 | dmwm/WMCore | https://api.github.com/repos/dmwm/WMCore | closed | [py2py3] make pylint --py3k happy with test/python/WMCore_t/Database_t/DBCore_t.py | High Priority Low effort New Feature Python3 | **Impact of the new feature**
This should involve only the unit test `test/python/WMCore_t/Database_t/DBCore_t.py`.
**Is your feature request related to a problem? Please describe.**
`pylint --py3k` complains with warnming `W1655` about `dict.keys()[0]` bekayse `.keys()` is not used in a for loop.
**Describe the solution you'd like**
Later during the modernization campaign, we decided to use `next(iter(dict))` instead of `dict.keys()[0]`. We should be consistent and do the same here
**Describe alternatives you've considered**
We can be less consistent and live with the pylint warning, however this is super likely to fail in py3 with
```plaintext
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
>>> myd = {"hello":1, "world":2}
>>> myd.keys()[0]
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: 'dict_keys' object is not subscriptable
```
**Additional context**
Fix modernization slice #10262
| 1.0 | [py2py3] make pylint --py3k happy with test/python/WMCore_t/Database_t/DBCore_t.py - **Impact of the new feature**
This should involve only the unit test `test/python/WMCore_t/Database_t/DBCore_t.py`.
**Is your feature request related to a problem? Please describe.**
`pylint --py3k` complains with warnming `W1655` about `dict.keys()[0]` bekayse `.keys()` is not used in a for loop.
**Describe the solution you'd like**
Later during the modernization campaign, we decided to use `next(iter(dict))` instead of `dict.keys()[0]`. We should be consistent and do the same here
**Describe alternatives you've considered**
We can be less consistent and live with the pylint warning, however this is super likely to fail in py3 with
```plaintext
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
>>> myd = {"hello":1, "world":2}
>>> myd.keys()[0]
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: 'dict_keys' object is not subscriptable
```
**Additional context**
Fix modernization slice #10262
| priority | make pylint happy with test python wmcore t database t dbcore t py impact of the new feature this should involve only the unit test test python wmcore t database t dbcore t py is your feature request related to a problem please describe pylint complains with warnming about dict keys bekayse keys is not used in a for loop describe the solution you d like later during the modernization campaign we decided to use next iter dict instead of dict keys we should be consistent and do the same here describe alternatives you ve considered we can be less consistent and live with the pylint warning however this is super likely to fail in with plaintext python default feb myd hello world myd keys traceback most recent call last file line in typeerror dict keys object is not subscriptable additional context fix modernization slice | 1 |
180,581 | 6,651,132,828 | IssuesEvent | 2017-09-28 18:53:14 | Burke-Lauenroth-Lab/rSFSW2 | https://api.github.com/repos/Burke-Lauenroth-Lab/rSFSW2 | opened | rSFSW2 passes carbon data to SOILWAT2 through memory | bug high priority | The current setup with passing an explicit dir argument to sw_exec is hiding a logical error:
- e.g., https://github.com/Burke-Lauenroth-Lab/rSFSW2/pull/115/commits/ef18f0ee5e2e859cfe0c0f551672aca372433e26 is incorrect because `project_paths[["dir_in_sw"]]` only holds the default values and not the run-specific values.
The fix will use the new functionality of rSOILWAT2 to read carbon data and pass it through memory: https://github.com/Burke-Lauenroth-Lab/rSOILWAT2/issues/57 | 1.0 | rSFSW2 passes carbon data to SOILWAT2 through memory - The current setup with passing an explicit dir argument to sw_exec is hiding a logical error:
- e.g., https://github.com/Burke-Lauenroth-Lab/rSFSW2/pull/115/commits/ef18f0ee5e2e859cfe0c0f551672aca372433e26 is incorrect because `project_paths[["dir_in_sw"]]` only holds the default values and not the run-specific values.
The fix will use the new functionality of rSOILWAT2 to read carbon data and pass it through memory: https://github.com/Burke-Lauenroth-Lab/rSOILWAT2/issues/57 | priority | passes carbon data to through memory the current setup with passing an explicit dir argument to sw exec is hiding a logical error e g is incorrect because project paths only holds the default values and not the run specific values the fix will use the new functionality of to read carbon data and pass it through memory | 1 |
235,950 | 7,744,429,146 | IssuesEvent | 2018-05-29 15:22:03 | Gloirin/m2gTest | https://api.github.com/repos/Gloirin/m2gTest | closed | 0004822:
the createNode server response should contain the content type of the created file | Filemanager bug high priority | **Reported by unknown user on 13 Sep 2011 13:37**
**Version:** git master
the createNode server response should contain the content type of the created file
| 1.0 | 0004822:
the createNode server response should contain the content type of the created file - **Reported by unknown user on 13 Sep 2011 13:37**
**Version:** git master
the createNode server response should contain the content type of the created file
| priority | the createnode server response should contain the content type of the created file reported by unknown user on sep version git master the createnode server response should contain the content type of the created file | 1 |
373,202 | 11,035,368,970 | IssuesEvent | 2019-12-07 13:13:26 | ivanhercaz/buruma | https://api.github.com/repos/ivanhercaz/buruma | closed | Links broken when it is in a subpage | bug priority:high | This is similar to #7. It should be solved urgently because it breaks all the navigation of the site. It happens with links to articles and tags. | 1.0 | Links broken when it is in a subpage - This is similar to #7. It should be solved urgently because it breaks all the navigation of the site. It happens with links to articles and tags. | priority | links broken when it is in a subpage this is similar to it should be solved urgently because it breaks all the navigation of the site it happens with links to articles and tags | 1 |
461,369 | 13,229,139,703 | IssuesEvent | 2020-08-18 07:38:36 | onaio/reveal-frontend | https://api.github.com/repos/onaio/reveal-frontend | closed | RVL-157 - CSV import for risk files | Priority: High epic | This document provides details on how to upload the risk and structure count csv and how to use the uploaded information. It includes mock-ups for the risk profile and the number of structure upload alongside the risk evaluation workflow.
Some points to note are:
- The MVP will focus on one risk profile
- The Upload of the risk profile and number of structures document will be manual for this step
Below is the desired workflow:
1. A user will be provided with a template pre-filled with jurisdiction IDs and names and with provision to capture the risk profile and the structure count. See sample template mock-up below:
2. 
3. The user will fill in the risk profile (the MVP will provide one variable) and provide an option to provide the structure count. Where the structure count already exists in the system, the structure count uploaded will override what exists in the system.
4. Ona will facilitate the manual upload of the completed file into the system from the backend.
5. On the WebUI, the user will select the create plan button and create an IRS plan and have an option to move to the risk threshold page.
6. The page will load with a risk threshold slider that automatically calculates the number of structures that meet the set threshold. See mock-up below:
7. 
8. On clicking on the “continue to next step” button, the user is provided with a map with the jurisdictions affected by the risk threshold selection in the earlier step. The map allows the user to drill down the maps until they get to the hierarchy level that is the immediate parent of the individual focus areas. Note, you cannot go back once the process has started, but you can start afresh. Selection of the risk check-box allows one to toggle on and off a risk layer allowing one to see the jurisdictions affected by the risk profile. The step further provides a breakdown of the number of structures in each of the jurisdiction. Each of the pages will also provide the total number of structures in the district. See mock-up below:
9. 
10. On clicking on the “continue to next step” button, the user gets the function allowing editing of the targeted jurisdictions based on the available resources. This is possible through the “change target status” button. It allows one to manually remove areas that may have been automatically selected based on the risk profile but that can not be supported by the available resources. The status change is made from targeted to Not targeted and vice versa. A note is also made on whether the status update was through auto-selection or by a user-change. See sample mock-up below:
11. 
12. Once the jurisdiction selection is complete, the process completes with the user being presented with the option to assign team to the plan.
| 1.0 | RVL-157 - CSV import for risk files - This document provides details on how to upload the risk and structure count csv and how to use the uploaded information. It includes mock-ups for the risk profile and the number of structure upload alongside the risk evaluation workflow.
Some points to note are:
- The MVP will focus on one risk profile
- The Upload of the risk profile and number of structures document will be manual for this step
Below is the desired workflow:
1. A user will be provided with a template pre-filled with jurisdiction IDs and names and with provision to capture the risk profile and the structure count. See sample template mock-up below:
2. 
3. The user will fill in the risk profile (the MVP will provide one variable) and provide an option to provide the structure count. Where the structure count already exists in the system, the structure count uploaded will override what exists in the system.
4. Ona will facilitate the manual upload of the completed file into the system from the backend.
5. On the WebUI, the user will select the create plan button and create an IRS plan and have an option to move to the risk threshold page.
6. The page will load with a risk threshold slider that automatically calculates the number of structures that meet the set threshold. See mock-up below:
7. 
8. On clicking on the “continue to next step” button, the user is provided with a map with the jurisdictions affected by the risk threshold selection in the earlier step. The map allows the user to drill down the maps until they get to the hierarchy level that is the immediate parent of the individual focus areas. Note, you cannot go back once the process has started, but you can start afresh. Selection of the risk check-box allows one to toggle on and off a risk layer allowing one to see the jurisdictions affected by the risk profile. The step further provides a breakdown of the number of structures in each of the jurisdiction. Each of the pages will also provide the total number of structures in the district. See mock-up below:
9. 
10. On clicking on the “continue to next step” button, the user gets the function allowing editing of the targeted jurisdictions based on the available resources. This is possible through the “change target status” button. It allows one to manually remove areas that may have been automatically selected based on the risk profile but that can not be supported by the available resources. The status change is made from targeted to Not targeted and vice versa. A note is also made on whether the status update was through auto-selection or by a user-change. See sample mock-up below:
11. 
12. Once the jurisdiction selection is complete, the process completes with the user being presented with the option to assign team to the plan.
| priority | rvl csv import for risk files this document provides details on how to upload the risk and structure count csv and how to use the uploaded information it includes mock ups for the risk profile and the number of structure upload alongside the risk evaluation workflow some points to note are the mvp will focus on one risk profile the upload of the risk profile and number of structures document will be manual for this step below is the desired workflow a user will be provided with a template pre filled with jurisdiction ids and names and with provision to capture the risk profile and the structure count see sample template mock up below the user will fill in the risk profile the mvp will provide one variable and provide an option to provide the structure count where the structure count already exists in the system the structure count uploaded will override what exists in the system ona will facilitate the manual upload of the completed file into the system from the backend on the webui the user will select the create plan button and create an irs plan and have an option to move to the risk threshold page the page will load with a risk threshold slider that automatically calculates the number of structures that meet the set threshold see mock up below on clicking on the “continue to next step” button the user is provided with a map with the jurisdictions affected by the risk threshold selection in the earlier step the map allows the user to drill down the maps until they get to the hierarchy level that is the immediate parent of the individual focus areas note you cannot go back once the process has started but you can start afresh selection of the risk check box allows one to toggle on and off a risk layer allowing one to see the jurisdictions affected by the risk profile the step further provides a breakdown of the number of structures in each of the jurisdiction each of the pages will also provide the total number of structures in the district see mock up below on clicking on the “continue to next step” button the user gets the function allowing editing of the targeted jurisdictions based on the available resources this is possible through the “change target status” button it allows one to manually remove areas that may have been automatically selected based on the risk profile but that can not be supported by the available resources the status change is made from targeted to not targeted and vice versa a note is also made on whether the status update was through auto selection or by a user change see sample mock up below once the jurisdiction selection is complete the process completes with the user being presented with the option to assign team to the plan | 1 |
196,798 | 6,949,161,103 | IssuesEvent | 2017-12-06 04:37:31 | wso2/product-ei | https://api.github.com/repos/wso2/product-ei | closed | JDBC message processor gives null pointer when the message SOAP body is empty | Component/Integrator Priority/High Severity/Critical | **Description:**
When a message body is empty, JDBC message processor gives following NPE.
`[2017-12-01 14:06:44,127] [EI-Core] INFO - LogMediator To: /services/Aproxy, MessageID: urn:uuid:3547bae4-64dd-4d15-8280-94dec0601bb0, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body/></soapenv:Envelope>
[2017-12-01 14:06:45,076] [EI-Core] ERROR - MessageConverter Cannot create Message Context. Error:null
java.lang.NullPointerException
at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:211)
at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBodyImpl.java:231)
at org.apache.synapse.message.store.impl.commons.MessageConverter.getSoapEnvelope(MessageConverter.java:362)
at org.apache.synapse.message.store.impl.commons.MessageConverter.toMessageContext(MessageConverter.java:98)
at org.apache.synapse.message.store.impl.jms.JmsConsumer.receive(JmsConsumer.java:107)
at org.apache.synapse.message.processor.impl.forwarder.ForwardingService.fetch(ForwardingService.java:406)
at org.apache.synapse.message.processor.impl.forwarder.ForwardingService.execute(ForwardingService.java:196)
at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:98)
at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)`
**Suggested Labels:**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->
**Suggested Assignees:**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->
**Affected Product Version:**
EI 6.1.1
**OS, DB, other environment details and versions:**
**Steps to reproduce:**
**Related Issues:**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. --> | 1.0 | JDBC message processor gives null pointer when the message SOAP body is empty - **Description:**
When a message body is empty, JDBC message processor gives following NPE.
`[2017-12-01 14:06:44,127] [EI-Core] INFO - LogMediator To: /services/Aproxy, MessageID: urn:uuid:3547bae4-64dd-4d15-8280-94dec0601bb0, Direction: request, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body/></soapenv:Envelope>
[2017-12-01 14:06:45,076] [EI-Core] ERROR - MessageConverter Cannot create Message Context. Error:null
java.lang.NullPointerException
at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:211)
at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBodyImpl.java:231)
at org.apache.synapse.message.store.impl.commons.MessageConverter.getSoapEnvelope(MessageConverter.java:362)
at org.apache.synapse.message.store.impl.commons.MessageConverter.toMessageContext(MessageConverter.java:98)
at org.apache.synapse.message.store.impl.jms.JmsConsumer.receive(JmsConsumer.java:107)
at org.apache.synapse.message.processor.impl.forwarder.ForwardingService.fetch(ForwardingService.java:406)
at org.apache.synapse.message.processor.impl.forwarder.ForwardingService.execute(ForwardingService.java:196)
at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAdapter.java:98)
at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute(TaskQuartzJobAdapter.java:67)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)`
**Suggested Labels:**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->
**Suggested Assignees:**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->
**Affected Product Version:**
EI 6.1.1
**OS, DB, other environment details and versions:**
**Steps to reproduce:**
**Related Issues:**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. --> | priority | jdbc message processor gives null pointer when the message soap body is empty description when a message body is empty jdbc message processor gives following npe info logmediator to services aproxy messageid urn uuid direction request envelope soapenv envelope xmlns soapenv error messageconverter cannot create message context error null java lang nullpointerexception at org apache axiom om impl llom omelementimpl addchild omelementimpl java at org apache axiom soap impl llom soapbodyimpl addchild soapbodyimpl java at org apache synapse message store impl commons messageconverter getsoapenvelope messageconverter java at org apache synapse message store impl commons messageconverter tomessagecontext messageconverter java at org apache synapse message store impl jms jmsconsumer receive jmsconsumer java at org apache synapse message processor impl forwarder forwardingservice fetch forwardingservice java at org apache synapse message processor impl forwarder forwardingservice execute forwardingservice java at org carbon mediation ntask ntaskadapter execute ntaskadapter java at org carbon ntask core impl taskquartzjobadapter execute taskquartzjobadapter java at org quartz core jobrunshell run jobrunshell java at java util concurrent executors runnableadapter call executors java at java util concurrent futuretask run futuretask java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java suggested labels suggested assignees affected product version ei os db other environment details and versions steps to reproduce related issues | 1 |
112,163 | 4,512,944,014 | IssuesEvent | 2016-09-04 00:04:52 | jahirfiquitiva/IconShowcase | https://api.github.com/repos/jahirfiquitiva/IconShowcase | opened | Content from Zooper and Kustom sections not appearing | bug help wanted high priority | It was working fine until Butler and Capsule implementation started | 1.0 | Content from Zooper and Kustom sections not appearing - It was working fine until Butler and Capsule implementation started | priority | content from zooper and kustom sections not appearing it was working fine until butler and capsule implementation started | 1 |
90,492 | 3,822,453,390 | IssuesEvent | 2016-03-30 01:14:22 | Esri/solutions-webappbuilder-widgets | https://api.github.com/repos/Esri/solutions-webappbuilder-widgets | closed | Enhanced Editor - Modify existing geometries | High Priority | implement the same logic as the find edit filter app to modify features location and vertices. | 1.0 | Enhanced Editor - Modify existing geometries - implement the same logic as the find edit filter app to modify features location and vertices. | priority | enhanced editor modify existing geometries implement the same logic as the find edit filter app to modify features location and vertices | 1 |
284,204 | 8,736,606,819 | IssuesEvent | 2018-12-11 20:00:31 | RobotLocomotion/drake | https://api.github.com/repos/RobotLocomotion/drake | closed | Multibody plant SDF parsing / sdformat "preserve unknown elements" is broken | priority: high team: dynamics type: bug | When I upgrade Drake's commit of SDFormat to the latest upstream `default` (aka master), the "preserve unknown elements" feature causes things to go haywire. In particular, the new unit test in #9220 fails.
Reverting #9221 will demonstrate this -- 9221 rolls back the SDFormat commit from one that has "preserve unknown", to a month-prior version that doesn't. If we push forward to a new commit, the unit test will break. | 1.0 | Multibody plant SDF parsing / sdformat "preserve unknown elements" is broken - When I upgrade Drake's commit of SDFormat to the latest upstream `default` (aka master), the "preserve unknown elements" feature causes things to go haywire. In particular, the new unit test in #9220 fails.
Reverting #9221 will demonstrate this -- 9221 rolls back the SDFormat commit from one that has "preserve unknown", to a month-prior version that doesn't. If we push forward to a new commit, the unit test will break. | priority | multibody plant sdf parsing sdformat preserve unknown elements is broken when i upgrade drake s commit of sdformat to the latest upstream default aka master the preserve unknown elements feature causes things to go haywire in particular the new unit test in fails reverting will demonstrate this rolls back the sdformat commit from one that has preserve unknown to a month prior version that doesn t if we push forward to a new commit the unit test will break | 1 |
512,738 | 14,908,593,319 | IssuesEvent | 2021-01-22 06:15:45 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | [0.9.2.0 beta staging-1902]Residency window not having a Accept button unless you reconnect | Category: Gameplay Category: UI Priority: High Squad: Mountain Goat | After receiving an invite to a claim or getting permissions on a claim requires a reconnect to get the Accept / become resident button to appear.
While fixing this if possible take a look at this as per the overfixing potential.
#19941 | 1.0 | [0.9.2.0 beta staging-1902]Residency window not having a Accept button unless you reconnect - After receiving an invite to a claim or getting permissions on a claim requires a reconnect to get the Accept / become resident button to appear.
While fixing this if possible take a look at this as per the overfixing potential.
#19941 | priority | residency window not having a accept button unless you reconnect after receiving an invite to a claim or getting permissions on a claim requires a reconnect to get the accept become resident button to appear while fixing this if possible take a look at this as per the overfixing potential | 1 |
80,417 | 3,561,525,596 | IssuesEvent | 2016-01-23 21:14:55 | RobotLocomotion/drake | https://api.github.com/repos/RobotLocomotion/drake | closed | Drake build system compatibility with DRC | priority: high type: installation and distribution | I thought I could add drake/drake to the drc tobuild.txt, but this didn't work because the drake build system cannot find the cmake subdir. I can't add drake to tobuild.txt because that will build dependencies that are already provided by drc. How do you guys think we should make this work? | 1.0 | Drake build system compatibility with DRC - I thought I could add drake/drake to the drc tobuild.txt, but this didn't work because the drake build system cannot find the cmake subdir. I can't add drake to tobuild.txt because that will build dependencies that are already provided by drc. How do you guys think we should make this work? | priority | drake build system compatibility with drc i thought i could add drake drake to the drc tobuild txt but this didn t work because the drake build system cannot find the cmake subdir i can t add drake to tobuild txt because that will build dependencies that are already provided by drc how do you guys think we should make this work | 1 |
64,533 | 3,212,562,954 | IssuesEvent | 2015-10-06 15:59:42 | cs2103aug2015-w13-2j/main | https://api.github.com/repos/cs2103aug2015-w13-2j/main | closed | Data file uses vertical pipe | as delimiter between labels | priority.high status.ongoing type.bug | This means that the user cannot include the pipe symbol in the task name, or else problems will arise when parseTask() is called. | 1.0 | Data file uses vertical pipe | as delimiter between labels - This means that the user cannot include the pipe symbol in the task name, or else problems will arise when parseTask() is called. | priority | data file uses vertical pipe as delimiter between labels this means that the user cannot include the pipe symbol in the task name or else problems will arise when parsetask is called | 1 |
109,415 | 4,387,107,001 | IssuesEvent | 2016-08-08 14:52:49 | ubuntudesign/vanilla-framework | https://api.github.com/repos/ubuntudesign/vanilla-framework | opened | Links should have a :visited state | Priority: High Status: Triaged | Currently, links do not have a :visited state.
For accessibility purposes, we should make clear to users which links they have already visited. This can be achieved with a color variation as long as it is sufficiently high contrast. | 1.0 | Links should have a :visited state - Currently, links do not have a :visited state.
For accessibility purposes, we should make clear to users which links they have already visited. This can be achieved with a color variation as long as it is sufficiently high contrast. | priority | links should have a visited state currently links do not have a visited state for accessibility purposes we should make clear to users which links they have already visited this can be achieved with a color variation as long as it is sufficiently high contrast | 1 |
7,224 | 2,599,205,101 | IssuesEvent | 2015-02-23 04:59:44 | OpenConceptLab/oclapi | https://api.github.com/repos/OpenConceptLab/oclapi | closed | external_id is ignored on concept update | bug high-priority | Create works, but for update, the external_id field is ignored.
This was send to dev and external id remains unchanged (without the "x" at the end):
```
PUT http://api.dev.openconceptlab.com/orgs/CIELTEST/sources/CIELTEST/concepts/5043/
{"datatype": "N/A", "external_id": "5043AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAx", "update_comment": "adding an x to the end of external ID", "concept_class": "Diagnosis"} {'Content-Type': 'application/json', 'Authorization': u'Token 22f6bf9500958d9a49b4a7c16203c17de3b59d45'}
``` | 1.0 | external_id is ignored on concept update - Create works, but for update, the external_id field is ignored.
This was send to dev and external id remains unchanged (without the "x" at the end):
```
PUT http://api.dev.openconceptlab.com/orgs/CIELTEST/sources/CIELTEST/concepts/5043/
{"datatype": "N/A", "external_id": "5043AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAx", "update_comment": "adding an x to the end of external ID", "concept_class": "Diagnosis"} {'Content-Type': 'application/json', 'Authorization': u'Token 22f6bf9500958d9a49b4a7c16203c17de3b59d45'}
``` | priority | external id is ignored on concept update create works but for update the external id field is ignored this was send to dev and external id remains unchanged without the x at the end put datatype n a external id update comment adding an x to the end of external id concept class diagnosis content type application json authorization u token | 1 |
748,866 | 26,141,227,470 | IssuesEvent | 2022-12-29 18:47:13 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Gutenberg 14.8.0+ compat issue with WordPress < 6.1 | [Type] Bug [Priority] High Backwards Compatibility | Gutenberg 14.8.0+ compat issue with WordPress < 6.1
14.8.0 introduced the use of has_same_registered_blocks function call:
https://plugins.trac.wordpress.org/changeset/2837553/gutenberg/trunk/lib/experimental/class-wp-theme-json-resolver-gutenberg.php
This function was only added to WordPress in 6.1.:
https://core.trac.wordpress.org/changeset/54493
However, Gutenberg itself was marked as compatible with 6.0:
https://plugins.trac.wordpress.org/changeset/2837553/gutenberg/trunk/gutenberg.php
Result attempting to install Gutenberg 14.8.0 and up with WordPress 6.0 will cause a fatal error. Example:
https://wordpress.org/support/topic/call-to-undefined-method-wp_theme_json_resolver_gutenberghas_same_registered_b/
Thus, the compatibility needs to be marked at 6.1 in the plugin headers, which will prevent older installs from accidentally breaking the site.
| 1.0 | Gutenberg 14.8.0+ compat issue with WordPress < 6.1 - Gutenberg 14.8.0+ compat issue with WordPress < 6.1
14.8.0 introduced the use of has_same_registered_blocks function call:
https://plugins.trac.wordpress.org/changeset/2837553/gutenberg/trunk/lib/experimental/class-wp-theme-json-resolver-gutenberg.php
This function was only added to WordPress in 6.1.:
https://core.trac.wordpress.org/changeset/54493
However, Gutenberg itself was marked as compatible with 6.0:
https://plugins.trac.wordpress.org/changeset/2837553/gutenberg/trunk/gutenberg.php
Result attempting to install Gutenberg 14.8.0 and up with WordPress 6.0 will cause a fatal error. Example:
https://wordpress.org/support/topic/call-to-undefined-method-wp_theme_json_resolver_gutenberghas_same_registered_b/
Thus, the compatibility needs to be marked at 6.1 in the plugin headers, which will prevent older installs from accidentally breaking the site.
| priority | gutenberg compat issue with wordpress gutenberg compat issue with wordpress introduced the use of has same registered blocks function call this function was only added to wordpress in however gutenberg itself was marked as compatible with result attempting to install gutenberg and up with wordpress will cause a fatal error example thus the compatibility needs to be marked at in the plugin headers which will prevent older installs from accidentally breaking the site | 1 |
397,008 | 11,717,056,131 | IssuesEvent | 2020-03-09 16:37:15 | wc-work/why | https://api.github.com/repos/wc-work/why | closed | Upcoming Section | High Priority | # Upcoming Events
- [x] Add bootstrap card
- [x] Generate loop to bring in more cards
- [x] ACF - Image
- [x] ACF - Name
- [x] ACF - Date/Time
- [x] ACF - Location
- [x] ACF - Description | 1.0 | Upcoming Section - # Upcoming Events
- [x] Add bootstrap card
- [x] Generate loop to bring in more cards
- [x] ACF - Image
- [x] ACF - Name
- [x] ACF - Date/Time
- [x] ACF - Location
- [x] ACF - Description | priority | upcoming section upcoming events add bootstrap card generate loop to bring in more cards acf image acf name acf date time acf location acf description | 1 |
664,825 | 22,289,655,728 | IssuesEvent | 2022-06-12 06:50:50 | UseCrowdWise/crowdwise | https://api.github.com/repos/UseCrowdWise/crowdwise | closed | Allow user to Sort by Points (default?) or Comments or Date | enhancement PRIORITY-HIGH | Should remember this preference (via `sync`?) | 1.0 | Allow user to Sort by Points (default?) or Comments or Date - Should remember this preference (via `sync`?) | priority | allow user to sort by points default or comments or date should remember this preference via sync | 1 |
270,796 | 8,470,182,191 | IssuesEvent | 2018-10-24 02:53:03 | meumobi/IRmobi | https://api.github.com/repos/meumobi/IRmobi | closed | can't install debug app on Android 6.0.1 | bug high priority | ### Actual behaviour
I've tested to install debug app (non-signed) on Android 6.0.1 but raise can't install msg. Works fine on 5.1
### Steps to reproduce
1. build non signed app
2. download apk
3. click on apk to install it => launch install but failed "can't install"
### Expected responses
- Why it happens
- How to fix it
- How to test
| 1.0 | can't install debug app on Android 6.0.1 - ### Actual behaviour
I've tested to install debug app (non-signed) on Android 6.0.1 but raise can't install msg. Works fine on 5.1
### Steps to reproduce
1. build non signed app
2. download apk
3. click on apk to install it => launch install but failed "can't install"
### Expected responses
- Why it happens
- How to fix it
- How to test
| priority | can t install debug app on android actual behaviour i ve tested to install debug app non signed on android but raise can t install msg works fine on steps to reproduce build non signed app download apk click on apk to install it launch install but failed can t install expected responses why it happens how to fix it how to test | 1 |
347,324 | 10,428,552,869 | IssuesEvent | 2019-09-16 23:01:32 | universelabs/universe-core | https://api.github.com/repos/universelabs/universe-core | closed | Login, Auth & Device Pairing | coding high-priority | **Description**
We need to implement a basic notion of logging in and pairing a feather device. User would input their credentials into the web app and Core will talk to its paired feather, which will respond whether login was successful. | 1.0 | Login, Auth & Device Pairing - **Description**
We need to implement a basic notion of logging in and pairing a feather device. User would input their credentials into the web app and Core will talk to its paired feather, which will respond whether login was successful. | priority | login auth device pairing description we need to implement a basic notion of logging in and pairing a feather device user would input their credentials into the web app and core will talk to its paired feather which will respond whether login was successful | 1 |
291,828 | 8,950,108,006 | IssuesEvent | 2019-01-25 09:50:17 | trimstray/htrace.sh | https://api.github.com/repos/trimstray/htrace.sh | opened | Reduce the curl command calls. | Priority: High Status: Review Needed Type: Enhancement | ```bash
fgrep _curl_base * -R [10:49:38]
lib/DomainResolve: _host_ip=$($_curl_base -ks -m "$_timeout" "https://dns.google.com/resolve?name=${_host}&type=A" | \
lib/DomainTrace: _http_output=$($_curl_base -ks -m "$_timeout" \
lib/DomainTrace: local _via_ip=$($_curl_base_remote -ks -m "$_timeout" http://whatismyip.akamai.com/)
lib/DomainTrace: $_curl_base -Iks -m "$_timeout" \
lib/DomainTrace: $_curl_base -Iks -m "$_timeout" \
lib/DomainTrace: $_curl_base -ks -m "$_timeout" \
lib/DomainTrace: $_curl_base -ks -m "$_timeout" \
src/__init__: local _curl_base=""
src/__init__: local _curl_base_remote=""
src/__init__: _curl_base="curl --proxy $proxy_type --request $req_method_type"
src/__init__: _curl_base_remote="curl --proxy $proxy_type"
src/__init__: _curl_base="curl --request $req_method_type"
src/__init__: _curl_base_remote="curl"
``` | 1.0 | Reduce the curl command calls. - ```bash
fgrep _curl_base * -R [10:49:38]
lib/DomainResolve: _host_ip=$($_curl_base -ks -m "$_timeout" "https://dns.google.com/resolve?name=${_host}&type=A" | \
lib/DomainTrace: _http_output=$($_curl_base -ks -m "$_timeout" \
lib/DomainTrace: local _via_ip=$($_curl_base_remote -ks -m "$_timeout" http://whatismyip.akamai.com/)
lib/DomainTrace: $_curl_base -Iks -m "$_timeout" \
lib/DomainTrace: $_curl_base -Iks -m "$_timeout" \
lib/DomainTrace: $_curl_base -ks -m "$_timeout" \
lib/DomainTrace: $_curl_base -ks -m "$_timeout" \
src/__init__: local _curl_base=""
src/__init__: local _curl_base_remote=""
src/__init__: _curl_base="curl --proxy $proxy_type --request $req_method_type"
src/__init__: _curl_base_remote="curl --proxy $proxy_type"
src/__init__: _curl_base="curl --request $req_method_type"
src/__init__: _curl_base_remote="curl"
``` | priority | reduce the curl command calls bash fgrep curl base r lib domainresolve host ip curl base ks m timeout lib domaintrace http output curl base ks m timeout lib domaintrace local via ip curl base remote ks m timeout lib domaintrace curl base iks m timeout lib domaintrace curl base iks m timeout lib domaintrace curl base ks m timeout lib domaintrace curl base ks m timeout src init local curl base src init local curl base remote src init curl base curl proxy proxy type request req method type src init curl base remote curl proxy proxy type src init curl base curl request req method type src init curl base remote curl | 1 |
186,470 | 6,736,432,303 | IssuesEvent | 2017-10-19 03:59:20 | octobercms/october | https://api.github.com/repos/octobercms/october | closed | FileUpload widget faillure with belongsTo relationManager | Priority: High Status: Review Needed Type: Unconfirmed Bug | 
When having the fileupload widget via the relation manager in a belongsTo relation ship, when you click on it, you can't modify the image details from the view page. but the menu gets presented to mondify anyways.
| 1.0 | FileUpload widget faillure with belongsTo relationManager - 
When having the fileupload widget via the relation manager in a belongsTo relation ship, when you click on it, you can't modify the image details from the view page. but the menu gets presented to mondify anyways.
| priority | fileupload widget faillure with belongsto relationmanager when having the fileupload widget via the relation manager in a belongsto relation ship when you click on it you can t modify the image details from the view page but the menu gets presented to mondify anyways | 1 |
734,795 | 25,364,354,934 | IssuesEvent | 2022-11-21 04:10:44 | wso2/api-manager | https://api.github.com/repos/wso2/api-manager | closed | Error in Browser Console Tab when Loading Portal Login Pages | Type/Bug Severity/Critical Priority/Highest Component/APIM | ### Description
The following errors gets logged in the browser console tab when loading the login pages of Publisher, DevPortal and Admin portals. **As a result of these errors, UI tests are failing.**
### Steps to Reproduce
1. Start the APIM server and load the publisher portal
2. Inspect the browser console tab
### Affected Component
APIM
### Version
APIM 4.2.0 M1 Pack
### Environment Details (with versions)
OS: Ubuntu 20.04 LTS
Browser: Google Chrome Version 106.0.5249.103 (Official Build) (64-bit), Firefox 106.0.5 (64-bit)
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | 1.0 | Error in Browser Console Tab when Loading Portal Login Pages - ### Description
The following errors gets logged in the browser console tab when loading the login pages of Publisher, DevPortal and Admin portals. **As a result of these errors, UI tests are failing.**
### Steps to Reproduce
1. Start the APIM server and load the publisher portal
2. Inspect the browser console tab
### Affected Component
APIM
### Version
APIM 4.2.0 M1 Pack
### Environment Details (with versions)
OS: Ubuntu 20.04 LTS
Browser: Google Chrome Version 106.0.5249.103 (Official Build) (64-bit), Firefox 106.0.5 (64-bit)
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | priority | error in browser console tab when loading portal login pages description the following errors gets logged in the browser console tab when loading the login pages of publisher devportal and admin portals as a result of these errors ui tests are failing steps to reproduce start the apim server and load the publisher portal inspect the browser console tab affected component apim version apim pack environment details with versions os ubuntu lts browser google chrome version official build bit firefox bit relevant log output no response related issues no response suggested labels no response | 1 |
686,792 | 23,504,462,097 | IssuesEvent | 2022-08-18 11:22:24 | alephium/explorer-backend | https://api.github.com/repos/alephium/explorer-backend | closed | Explorer reporting balance 0 but transactions add up to much more than 0 | high priority | Check out this address on testnet: https://testnet.alephium.org/addresses/1HRr1oBBSPJqeodrSnpKGiWv9iSpWiND1zZNPdL4tL8Ev
It received 10 ALPH but only sent out 0.002 ALPH. How come the balance is now zero?
I can explain why it's zero, but not why there are missing transactions: I had sent additional transactions to drain this address. So for some reason explorer is just not showing the rest of the transactions.
/cc @tdroxler | 1.0 | Explorer reporting balance 0 but transactions add up to much more than 0 - Check out this address on testnet: https://testnet.alephium.org/addresses/1HRr1oBBSPJqeodrSnpKGiWv9iSpWiND1zZNPdL4tL8Ev
It received 10 ALPH but only sent out 0.002 ALPH. How come the balance is now zero?
I can explain why it's zero, but not why there are missing transactions: I had sent additional transactions to drain this address. So for some reason explorer is just not showing the rest of the transactions.
/cc @tdroxler | priority | explorer reporting balance but transactions add up to much more than check out this address on testnet it received alph but only sent out alph how come the balance is now zero i can explain why it s zero but not why there are missing transactions i had sent additional transactions to drain this address so for some reason explorer is just not showing the rest of the transactions cc tdroxler | 1 |
361,339 | 10,707,399,742 | IssuesEvent | 2019-10-24 17:23:05 | craftercms/craftercms | https://api.github.com/repos/craftercms/craftercms | closed | [search] Make Crafter CMS internal fields non dynamic on elasticsearch | enhancement priority: highest! | All fields like `internal-name`, `expired_dt` & `disabled` should be always added to indexes instead of being added when a document that contains it is indexed | 1.0 | [search] Make Crafter CMS internal fields non dynamic on elasticsearch - All fields like `internal-name`, `expired_dt` & `disabled` should be always added to indexes instead of being added when a document that contains it is indexed | priority | make crafter cms internal fields non dynamic on elasticsearch all fields like internal name expired dt disabled should be always added to indexes instead of being added when a document that contains it is indexed | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.