is this a demo or sim? how to use the sim?

so im super confused and all of the docs apparently assume professional programmer, which im not. i was able to get it to load some random demo, but im trying to simulate my smartwatch forked from https://github.com/sharandac/My-TTGO-Watch. platformIO and vscode are already good, what else do i need? sim should be an extension for vscode or pIO or something...

This is demo how to use lvgl with pio, building multiple targets - bare metal & sim. But you are expected to know how to use pio.

thats not helpful... i know how to use pio, that doesnt tell me what to do with this, or how to simulate my project instead of the included demo

Sorry, but generic programming questions are out of this project scope.

how is "how to use THIS software" outside the scope of this software? this is not generic, this is "which files need to go where? to make the simulation of another thing that isnt the demo," which seems pretty specific to me. the readme reads like it assumes platformio is new, including instructions for installing vscode and pio... yay... then explains up to how to run the demo: "To build/execute, on PlafomIO tab expand desired env and click target:" great, still not trying to run the demo, trying to simulate my thing. the last thing listed in the readme is "Note, for emulator env upload also executes compiled binary." does that mean that i can use the compiled binary from wherever it gets compiled and drop it here to simulate it, or just that it has the same function as the execute button?

I think there may be a misunderstanding here. LVGL simulators are evaluation/development environments for LVGL itself. They do not simulate specific hardware.

I think there may be a misunderstanding here.

this is definitely true. is this for the development of LVGL or for developing things with LVGL? all im trying to do, is simulate what will be displayed on my watch, without having to actually upload it to the watch.

You can use this to develop things with LVGL, but it will not simulate your watch directly.
This is a generic simulator for designing LVGL user interfaces, but it does not include any specific APIs that you would find in your watch's firmware.

This is a generic simulator for designing LVGL user interfaces, but it does not include any specific APIs that you would find in your watch's firmware.

ok but is there some part of this that i could include somewhere else that, when clicking execute, would simulate that page, probably with a custom build env in the target project? i dont expect it to be able to actually trigger the buttons for the applications/ watchface, im just trying to save myself the headache of having to make another update because im 5 pixels too big or buttons overlap etc. my apologies for being completely clueless still, i was linked to this project from this page and this was the first one i got working(and also the first i tried). maybe, can you tell me: does there exist something that will let me "preview" the output of an active project? this LOOKS like it could, but i admit im not an expert with pio yet and have no idea what would need to go where to make it do

does there exist something that will let me "preview" the output of an active project?

With embedded development, it is difficult to preview the output of a project easily, unless the project already has some type of emulation/simulation environment set up.
This is where the difference between a simulator and emulator really comes into play. Simulators only aim to replicate some of a device's behavior. In LVGL's case our simulator can only replicate the user interface. You can change the screen size, etc., but it's not a replacement for development on the actual target.
An emulator would replicate the hardware's behavior very closely to the point of being indistinguishable.
I think what you are really looking for is an emulator for your watch, but I'm not sure if such a thing exists. You would probably need to ask in that community.
There are two solutions which are commonly used to solve this problem:

Structure your GUI code in such a way that it can be copied back and forth between the LVGL simulator project and the target project easily. If you set the screen size of the simulator to match the watch, you can get a feel for how things would look without having to download the code to the watch each time. The downside here is that your entire GUI has to be architected in such a way that it runs in two different environments.
Make iterating on the real hardware faster, so that you can quickly deploy updates and see how things would look. For example, on my personal STM32 build environment, I can see the effects of a change within about 10-15 seconds.

mad thanks for this. the documentation lists key features as "Hardware independent to use with any microcontroller or display," i think i interpreted that to mean that gui code would be portable between environments, which it sounds like it can be, but isnt inherently...

Correct. The LVGL APIs themselves are the same regardless of what environment you use them in, but if your GUI code is interacting with hardware or relying on a certain screen size, you have to mock those things yourself. By "hardware independent" we mean that the library itself doesn't depend on a specific display type or processor.


update incremental-sim branch with develop

Checked for duplicates
Yes - I've already checked
Alternatives considered
No - I haven't considered
Related problems
the incremental-sim branch is based on a much earlier version of develop, and continues to get further behind. this makes it hard to correspond with the latest bug fixes of other issues already in develop but missing in the branch.
Describe the feature request
we should update the incremental-sim branch so that it is based on the latest develop.
this is also a great opportunity to go through all the diffs for the incremental-sim branch and learn about all the changes
Brad provided these hints about managing the changes:
... (to be copied from slack)

notes from merging process and go-backs marked with (**) for mandatory vs () for optional nice to do and (x, xxx) done
mergenotes.txt

in progress branch here: https://github.com/NASA-AMMOS/aerie/tree/incremental-sim-merge-2160

briefed @bradNASA on current status in case he has time to bite off any testing while I am out

Incremental sim used the SimulationFacade to cache past engines (actually SimulationDrivers), to reuse.  SimulationFacade is now an interface, implemented by CheckpointSimulationFacade.  I expect we should create a separate facade class for incremental sim.  Should we just use the old SimulationFacade code for that or rewrite it to look more like CheckpointSimulationFacade?

The "old" SimulationFacade was adapted to how the scheduler was working before checkpoint sim was introduced. With checkpoint sim, SimulationFacade has been rewritten. I think you can add a specific implementation of that interface for incremental sim. I realize there are no comments in that interface file, we can discuss what each method means. The simulation facade object is managed by the scheduler and I doubt you would have to change anything on the scheduler's side besides spawning the incremental simulation facade instead of the checkpoint sim facade.


Enhance keyboard navigation

Would like to support:

Left/Right: move a small amount
Shift+Left/Right: move a larger amount

The above keyboard shortcuts work, though they need to be documented (#53), and they also need to be made to behave the same way regardless of the number of datum points in a series (e.g. always move 1/10th or 1/5th through the chart).
Also, the chart shouldn't stop playing if the user arrows to the end.
Also there is the separate issue of where the keyboard handling should be attached (#48).


doc: development_process: document that CI style checks can fail

The CI style checking solution can produce false positives when it's
given code that it mis-parses, or that follows conventions it doesn't
allow.  Document a couple examples, and explicitly note that
maintainers should override the -1 vote if they're encountered.
For those following along in the commit history:
static uint8_t __aligned(PAGE_SIZE) page_pool[PAGE_SIZE * POOL_PAGES];

checkpatch sees "uint8_t __aligned(PAGE_SIZE)" and infers a prototype
for a function "__aligned" that takes an unnamed parameter of type
"PAGE_SIZE".  So it adds "PAGE_SIZE" as a known type name.
IOPCTL_Type *base = config->base;

This is common in driver code where the vendor HAL allows typedefs for
structure types.  checkpatch was designed for an environment with
limited use of typedefs; "struct IPCTL_Type" would have been handled
properly.
Closes #27002

The compliance check failure related to the sample code line being too long should be ignored.  It's not an issue when the code is displayed in documentation.
Run if [ -s Nits.txt ]; then
71
##[error]See https://docs.zephyrproject.org/latest/contribute/#commit-guidelines for more details
72

73
10: UC4 Line exceeds max length (73>72): "   static uint8_t __aligned(PAGE_SIZE) page_pool[PAGE_SIZE * POOL_PAGES];"
74
##[error]Process completed with exit code 1.

(Amusing it showed up in a PR that identifies cases where compliance check failures may be overridden.)


Facing crash issue while loading Map and while getting focus on markers

I'm facing issue while I am loading Markers to map and it's crashing on any pages and it will be like on specified devices like Samsung, Oppo, Xiaomi . On some device it's working fine but on other devices it is crashing continuously. also I'm attaching screen shot which is from firebase crash analytics, Please have a look.
Thank you in advance for checking my issue and please do needful.

Hi @maulik0webomindapps, please provide the output of flutter doctor -v that was used to build the app that is crashing.
Please also provide the crash log in txt form instead of screenshots. Screenshots are not searchable and they make it difficult for us to find similar issues if we do not have all the logs.
Also, are you able to reproduce this locally? If you are, kindly provide a complete minimal sample along with the steps to reproduce.
Thank you

Hello @danagbemava-nc ,
Thank you for reaching out to my issue.
Here is Output of flutter doctor -v
`[√] Flutter (Channel stable, 3.0.5, on Microsoft Windows [Version 10.0.22000.795], locale en-IN)
• Flutter version 3.0.5 at C:\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision f1875d570e (8 days ago), 2022-07-13 11:24:16 -0700
• Engine revision e85ea0e79c
• Dart version 2.17.6
• DevTools version 2.12.2
[√] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
• Android SDK at C:\Users\mauli\AppData\Local\Android\sdk
• Platform android-33, build-tools 32.1.0-rc1
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2021.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
[√] VS Code (version 1.68.1)
• VS Code at C:\Users\mauli\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.29.0
[√] Connected device (4 available)
• sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
• Windows (desktop)       • windows       • windows-x64    • Microsoft Windows [Version 10.0.22000.795]
• Chrome (web)            • chrome        • web-javascript • Google Chrome 103.0.5060.134
• Edge (web)              • edge          • web-javascript • Microsoft Edge 103.0.1264.62
[√] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 1 category.
`
This is log of issue
Fatal Exception: java.lang.NullPointerException
Attempt to get length of null array
Fatal Exception: java.lang.NullPointerException: Attempt to get length of null array
at java.nio.ByteBufferAsIntBuffer.put(ByteBufferAsIntBuffer.java:122)
at com.google.maps.api.android.lib6.gmm6.vector.gl.buffer.n.i(n.java:2)
at com.google.maps.api.android.lib6.gmm6.vector.gl.buffer.n.d(n.java:3)
at com.google.maps.api.android.lib6.gmm6.vector.gl.drawable.d.s(d.java:2)
at com.google.maps.api.android.lib6.gmm6.vector.gl.drawable.ao.s(ao.java:12)
at com.google.maps.api.android.lib6.gmm6.vector.bz.s(bz.java:29)
at com.google.maps.api.android.lib6.gmm6.vector.bs.b(bs.java:151)
at com.google.maps.api.android.lib6.gmm6.vector.av.run(av.java:48)
also i can't able to reproduce at locally that's why i can't able to resolve

same here

Hi @maulik0webomindapps, the crash logs are exactly the same as the error in https://github.com/flutter/flutter/issues/105965.
As such, I'll be closing this issue as a duplicate of the linked issue.
Kindly follow up there for updates.
Closing from here as duplicate.
Thank you


Create cookies_policy.html

Create a Cookies Policy file with the option for disabling cookies.

The option to disable cookies is now on the develop branch.


Shared context seems to be leaking mocked info

Subject of the issue
RSpec mocks leaking cross "shared context"
Your environment

Ruby version: 2.4
rspec-mocks version: 3.9

Steps to reproduce
See github SHA for failing rspec test here: https://github.com/site-prism/site_prism/runs/872888494
Expected behavior
I'm not sure why this context is leaking. Inside my context I stub and require a certain input/output. These should be completely isolated right? Maybe I'm doing something wrong?
Actual behavior
The Xpath shared context is leaking info to the css shared context

Can you link directly to the file and part of the build you'd like us to look at? We don't have time to dig through your codebase and build output.

Sorry mybad.
Commit SHA where I add references inside the shared contexts - https://github.com/site-prism/site_prism/pull/68/commits/874cf517ed7e57d9f415cae1e3c2c3ede9b95266#diff-420eec461dcee2d4bebde4204d2be9c0R88
Sample failing build, tests that are problematic start here: https://travis-ci.com/github/site-prism/site_prism/jobs/361220368#L882
It says the XPath page expected a css element and vice versa. Maybe it's something wrong with my setup, I'm not sure. I actually only wanted to write a test for a warning being thrown to increase code coverage.

I may get it wrong, but:
context 'with a Page defined using CSS locators' do
  let(:page) { CSSPage.new }
  it ...
    allow(page).to receive(:element).with(:no_way_should_this_be_written, '//a[@class="c"]//b[@class="d"]').and_call_original

it seems to me you're passing an XPath selector to a CSSPage and the other way around.

I've switched those round and I get different errors now. So I think..... maybe you are right @pirj
Given this feels like it's something that can't be globally broken. I'll close this Issue for now and investigate further. Sorry for wasting everyones time.
I'm not sure what's broken, but fairly sure it's not rspec.

Feel free to reopen @luke-hill if you see an issue in RSpec itself.

No worries, @luke-hill.
Sometimes we have bugs, and if it's not so obvious, please feel free to open a ticket.
You're always welcome.


fix global keyboard and window listeners are not removed after the map is destroyed

Hi,
I noticed the global listeners bound in the keyboard mixin were not unbound after the map was destroyed, which makes the listener always exist and makes the code throw errors even if the component is destroyed in those single-page applications.
So I think we should unbind the listeners somewhere after destroying the map. I currently put this logic into the _initKeyListener function of the Keyboard mixin. Also, to keep the isolation of the mixin, I changed the singleton Keyboard mixin object to a function that returns a new object at each call to make it work for multiple map instances, or the entire listener will be removed as long as one map is destroyed, which causes the event listener for other maps to not work.
To reproduce,

https://codepen.io/plainheart/pen/bGZVxgv
Or just open demo/index.html in this project and call map.remove()

@Falke-Design Just added a simple test case but I'm not sure if it's enough.

And do you think we have with some other Mixins problems when there are multiple maps?

It looks other mixins are not binding events on the global objects like window and document. There might be no problem with them. One suggestion is to provide an API to allow users to unmount (or destroy/remove/dispose) the PM plugin and clean up the relative resources like listeners and mounted objects.


Datashare issue for users belongs to two or more teams

Describe the bug
We have noticed that a user is  a part of 2 teams (eg producer , consumer) 2) producer team has a dataset-test. 3) you request permissions for consumer team for dataset-test 4) you won't see the submit button .
How to Reproduce
*P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.*

Expected behavior
When a user belongs to 2 teams and requests permissions for a dataset for a team that does not own the dataset they should be able to request access.
Your project
No response
Screenshots
No response
OS
All
Python version
3.1
AWS data.all version
all
Additional context
No response

Hi @manjulaK, thanks for raising an issue. We will look into it, but you are more than welcome to start working on it. The implementation of a mechanism that adapts the sharing so that a user can be approver and requester at the same time is not a complicated implementation but our bandwidth is limited at the moment

Merged and released with v2.1.0 🚀


Remove the remaining reference to the text painter rounding migration flag.

The default value of disableRoundingHack is now true, the migration flag is no longer needed and will be removed soon.

@LongCatIsLooong is this change on stable too? Or only on master?

It was removed in 3.15.0-1.0.pre so yeah the default should be the same (no rounding) for both branches.

@angelosilvestre can you cherry pick this?


Miscellaneous project improvements

Main goal of this PR is to simplify import process of this project into qwertycoin-gui and qwertycoin-zero.

@qwertycoin-org This PR can be merge once you see that all CI scripts are "green" 🙂

@qwertycoin-org Could you please push new tag (5.2.0 or 5.1.4) to master branch after merging this PR? I need this to configure qwertycoin imports in qwertycoin-gui and qwertycoin-zero repositories.

@speqtr yes sure we can bump the version.
And btw there is a little issue with version code or isn't it?
Old: <IP_ADDRESS>00 (6db7f2b-g6db7f2b)
After your last PR: <IP_ADDRESS>00 (5.1.3) Was that intended?

@qwertycoin-org This change was not intended. Please, open an issue and assign it to me. I'll fix it in a separate PR after this one is merged.


Adding node pool to existing cluster fails

When trying to add a nodepool to an existing cluster, you get an error message like:
Error: failed to create cluster: PUT https://management.azure.com/subscriptions/<REDACTED>/resourceGroups/<REDACTED>/providers/Microsoft.ContainerService/managedClusters/<REDACTED>
--------------------------------------------------------------------------------
RESPONSE 400: 400 Bad Request
ERROR CODE: BadRequest
--------------------------------------------------------------------------------
{
  "code": "BadRequest",
  "details": null,
  "message": "A new agent pool was introduced. Adding agent pools to an existing cluster is not allowed through managed cluster operations. For agent pool specific change, please use per agent pool operations: https://aka.ms/agent-pool-rest-api",
  "subcode": ""
}
--------------------------------------------------------------------------------

Facing same issue with bicep template based deployment.
API version used: Microsoft.ContainerService/managedClusters@2023-07-02-preview
Error message:
"Preflight validation check for resource(s) for container service xxxxxx in resource group  xxxxxx failed. Message: A new agent pool was introduced. Adding agent pools to an existing cluster is not allowed through managed cluster operations. For agent pool specific change, please use per agent pool operations: https://aka.ms/agent-pool-rest-api. Details:  (Code: BadRequest)"

@krishkalai I am assuming this is not in context of deploying Tyger? This issue should actually be closed since we have implemented a fix here.

@hansenms  his is not related to tyger. We got this issue today when we tried to add a new agent pool addition to an existing AKS managedcluster using "Microsoft.ContainerService/managedClusters@2023-07-02-preview" api version. Does this fix applies to all Api versions of managed clusters?

This was not a fix to the AKS API. It was a fix to Tyger, which deploys and uses AKS.

@johnstairs Thanks for the clarity.


getting OpenSSL.SSL.ZeroReturnError in failure set env variable

I'm trying to set an env var deis config:set FOO=bar -a production and am getting  OpenSSL.SSL.ZeroReturnError
Creating config... Traceback (most recent call last):
  File "<string>", line 2540, in <module>
  File "<string>", line 2536, in main
  File "<string>", line 2469, in _dispatch_cmd
  File "<string>", line 1290, in config_set
  File "<string>", line 1302, in _config_set
  File "<string>", line 450, in _dispatch
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.sessions", line 504, in post
  File "<string>", line 170, in request
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.sessions", line 461, in request
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.sessions", line 610, in send
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.models", line 730, in content
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.models", line 655, in generate
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.packages.urllib3.response", line 256, in stream
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.packages.urllib3.response", line 186, in read
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/httplib", line 567, in read
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/socket", line 380, in read
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/requests.packages.urllib3.contrib.pyopenssl", line 188, in recv
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/OpenSSL.SSL", line 1320, in recv
  File "/Users/jenkins/workspace/build-deis-cli-installer-darwin/src/github.com/deis/deis/client/build/deis/out00-PYZ.pyz/OpenSSL.SSL", line 1167, in _raise_ssl_error
OpenSSL.SSL.ZeroReturnError

This is on a new deis 1.9.0 cluster that I already been set up (i.e. the command has worked before on my machine)
I've included some of the fixes since the v1.9.0 tag in the platform build: git log v1.9.0-v1.9.0-b90c2fbb --oneline https://www.irccloud.com/pastebin/z6eiyQOI/
I asked in #deis and mboersma wrote:

I haven't seen that error either, although there have been a couple similar issues due to something about how the Deis CLI is packaged by PyInstaller.
If you can run "deis.py" locally or install it with "pip install deis", I doubt you'll see that problem.
but if you could enter a GitHub issue, maybe someone actually knows of a fix...

I agree to the DCO
Output of ssh "core@$DEISCTL_TUNNEL" /bin/bash -l -c '/opt/bin/deis-debug-logs' (slightly amended)
--- VERSIONS ---
CoreOS 723.3.0
Deis v1.9.0
etcd version 0.4.9
fleetd version 0.10.2

--- SYSTEM STATUS ---
-- Logs begin at Wed 2015-08-19 10:34:41 UTC, end at Wed 2015-08-19 16:39:24 UTC. --
Aug 19 16:39:11 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:11 etcdserver: failed to reach the peerURL(http://10.x.x.x:7001) of member klm987 (Get http://10.x.x.x:7001/version: dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:11 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:11 etcdserver: cannot get the version of member klm987 (Get http://10.x.x.x:7001/version: dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:11 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:11 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:11 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:11 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:12 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:12 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:12 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:12 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:12 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:12 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:13 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:13 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:13 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:13 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:13 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:13 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:14 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:14 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:2380: no route to host)
Aug 19 16:39:14 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:14 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:2380: no route to host)
Aug 19 16:39:14 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:14 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: no route to host)
Aug 19 16:39:15 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:15 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:15 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:15 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:15 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:15 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:16 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:16 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:16 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:16 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:16 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:16 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:17 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:17 etcdserver: failed to reach the peerURL(http://10.x.x.x:2380) of member klm987 (Get http://10.x.x.x:2380/version: net/http: request canceled while waiting for connection)
Aug 19 16:39:17 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:17 etcdserver: failed to reach the peerURL(http://10.x.x.x:7001) of member klm987 (Get http://10.x.x.x:7001/version: dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:17 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:17 etcdserver: cannot get the version of member klm987 (Get http://10.x.x.x:7001/version: dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:17 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:17 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:17 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:17 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:17 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:17 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:18 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:18 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:18 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:18 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:18 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:18 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:19 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:19 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:19 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:19 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:19 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:19 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:20 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:20 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:20 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:20 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:2380: no route to host)
Aug 19 16:39:20 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:20 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:2380: no route to host)
Aug 19 16:39:20 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:20 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: no route to host)
Aug 19 16:39:21 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:21 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:21 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:21 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:21 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:21 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:7001: i/o timeout)
Aug 19 16:39:22 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:22 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:22 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:22 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:22 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:22 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:23 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:23 etcdserver: failed to reach the peerURL(http://10.x.x.x:2380) of member klm987 (Get http://10.x.x.x:2380/version: net/http: request canceled while waiting for connection)
Aug 19 16:39:23 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:23 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:23 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:23 etcdserver: failed to reach the peerURL(http://10.x.x.x:7001) of member klm987 (Get http://10.x.x.x:7001/version: dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:23 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:23 etcdserver: cannot get the version of member klm987 (Get http://10.x.x.x:7001/version: dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:23 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:23 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:23 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:23 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:7001: no route to host)
Aug 19 16:39:24 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:24 rafthttp: failed to write klm987 on pipeline (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:24 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:24 rafthttp: failed to dial klm987 on stream Message (dial tcp 10.x.x.x:2380: i/o timeout)
Aug 19 16:39:24 deis-v1.9.0-b90c2fbb-1 docker[675]: 2015/08/19 16:39:24 rafthttp: failed to dial klm987 on stream MsgApp v2 (dial tcp 10.x.x.x:2380: i/o timeout)
-- Logs begin at Wed 2015-08-19 10:34:41 UTC, end at Wed 2015-08-19 16:39:24 UTC. --
Aug 19 16:35:37 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO engine.go:79: Engine leader is hij78966d740379e6d8a0414fae730
Aug 19 16:36:52 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:52 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:52 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:53 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:54 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:54 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:55 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:56 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:56 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:56 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:57 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:57 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:36:58 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:37 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:37 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:38 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:40 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled
Aug 19 16:37:40 deis-v1.9.0-b90c2fbb-1 fleetd[913]: INFO client.go:292: Failed getting response from http://localhost:4001/: cancelled

--- DEIS STATUS ---
UNIT				MACHINE				LOAD	ACTIVE		SUB
deis-builder.service		abc123.../10.0.0.z	loaded	active		running
deis-controller.service		abc123.../10.0.0.z	loaded	active		running
deis-database.service		abc123.../10.0.0.z	loaded	active		running
deis-logger.service		efg456.../10.0.0.y	loaded	active		running
deis-logspout.service		efg456.../10.0.0.y	loaded	active		running
deis-logspout.service		abc123.../10.0.0.z	loaded	active		running
deis-logspout.service		hij789.../10.0.0._	loaded	active		running
deis-publisher.service		efg456.../10.0.0.y	loaded	active		running
deis-publisher.service		abc123.../10.0.0.z	loaded	active		running
deis-publisher.service		hij789.../10.0.0._	loaded	active		running
<EMAIL_ADDRESS>efg456.../10.0.0.y	loaded	active		running
<EMAIL_ADDRESS>hij789.../10.0.0._	loaded	active		running
<EMAIL_ADDRESS>efg456.../10.0.0.y	loaded	active		running
<EMAIL_ADDRESS>abc123.../10.0.0.z	loaded	active		running
deis-store-daemon.service	efg456.../10.0.0.y	loaded	active		running
deis-store-daemon.service	abc123.../10.0.0.z	loaded	active		running
deis-store-daemon.service	hij789.../10.0.0._	loaded	active		running
<EMAIL_ADDRESS>efg456.../10.0.0.y	loaded	active		running
deis-store-metadata.service	efg456.../10.0.0.y	loaded	inactive	dead
deis-store-metadata.service	abc123.../10.0.0.z	loaded	active		running
deis-store-metadata.service	hij789.../10.0.0._	loaded	active		running
deis-store-monitor.service	efg456.../10.0.0.y	loaded	active		running
deis-store-monitor.service	abc123.../10.0.0.z	loaded	active		running
deis-store-monitor.service	hij789.../10.0.0._	loaded	active		running
deis-store-volume.service	efg456.../10.0.0.y	loaded	active		running
deis-store-volume.service	abc123.../10.0.0.z	loaded	active		running
deis-store-volume.service	hij789.../10.0.0._	loaded	active		running
/deis/migrations
/deis/migrations/data
/deis/migrations/data/0001
/deis/migrations/data/0002
/deis/registry
/deis/registry/bucketName
/deis/registry/masterLock
/deis/registry/host
/deis/registry/port
/deis/registry/hosts
/deis/registry/hosts/10.0.0.y
/deis/registry/hosts/10.0.0.y/host
/deis/registry/hosts/10.0.0.y/port
/deis/registry/hosts/10.0.0.z
/deis/registry/hosts/10.0.0._
/deis/registry/protocol
/deis/config
/deis/config/production
/deis/config/production/redis_url
/deis/config/production/mailer_host
/deis/config/production/secret_token
/deis/config/production/asset_host
/deis/config/production/database_url
/deis/config/production/thread_pool
/deis/config/production/rails_env
/deis/config/production/s3_secret_access_key
/deis/config/production/s3_access_key_id
/deis/config/production/s3_bucket
/deis/config/production/new_relic_license_key
/deis/config/production/new_relic_app_name
/deis/config/production/workers
/deis/config/production/rack_env
/deis/config/production/buildpack_url
/deis/config/production/api_subdomain
/deis/config/production/frontend_subdomain
/deis/database
/deis/database/adminPass
/deis/database/user
/deis/database/initId
/deis/database/host
/deis/database/engine
/deis/database/adminUser
/deis/database/password
/deis/database/name
/deis/database/bucketName
/deis/database/port
/deis/router
/deis/router/hsts
/deis/router/gzip
/deis/router/proxyProtocol
/deis/router/hosts
/deis/router/hosts/10.0.0.z
/deis/router/hosts/10.0.0.y
/deis/router/hosts/10.0.0._
/deis/platform
/deis/platform/domain
/deis/platform/sshPrivateKey
/deis/platform/version
/deis/logs
/deis/logs/port
/deis/logs/drain
/deis/logs/host
/deis/cache
/deis/controller
/deis/controller/registrationMode
/deis/controller/port
/deis/controller/host
/deis/controller/protocol
/deis/controller/builderKey
/deis/controller/unitHostname
/deis/controller/subdomain
/deis/controller/secretKey
/deis/controller/webEnabled
/deis/services
/deis/services/production
/deis/domains
/deis/domains/new.mydomain.com
/deis/domains/new-api.mydomain.com
/deis/domains/www.mydomain.com
/deis/domains/api.mydomain.com
/deis/certs
/deis/store
/deis/store/fsid
/deis/store/monKeyring
/deis/store/gatewayKeyring
/deis/store/gateway
/deis/store/gateway/secretKey
/deis/store/gateway/masterLock
/deis/store/gateway/host
/deis/store/gateway/port
/deis/store/gateway/hosts
/deis/store/gateway/hosts/10.0.0.y
/deis/store/gateway/hosts/10.0.0.y/host
/deis/store/gateway/hosts/10.0.0.y/port
/deis/store/gateway/hosts/10.0.0.z
/deis/store/gateway/hosts/10.0.0.z/host
/deis/store/gateway/hosts/10.0.0.z/port
/deis/store/gateway/hosts/10.0.0._
/deis/store/gateway/hosts/10.0.0._/host
/deis/store/gateway/hosts/10.0.0._/port
/deis/store/gateway/accessKey
/deis/store/size
/deis/store/minSize
/deis/store/monSetupLock
/deis/store/delayStart
/deis/store/adminKeyring
/deis/store/osds
/deis/store/osds/10.0.0.y
/deis/store/osds/10.0.0._
/deis/store/osds/10.0.0.z
/deis/store/filesystemSetupLock
/deis/store/hosts
/deis/store/hosts/10.0.0._
/deis/store/hosts/10.0.0.y
/deis/store/hosts/10.0.0.z
/deis/store/pgNum
/deis/store/maxPGsPerOSDWarning
/deis/store/monSetupComplete
/deis/store/filesystemSetupComplete
/deis/builder
/deis/builder/users
/deis/builder/users/admin
/deis/builder/users/admin/b0:......
/deis/builder/sshHostecdsaKey
/deis/builder/sshHosted25519Key
/deis/builder/sshHosted25519PubKey
/deis/builder/sshHostKey
/deis/builder/sshHostdsaKey
/deis/builder/sshHostdsaPubKey
/deis/builder/sshHostecdsaPubKey
/deis/builder/sshHostrsaKey
/deis/builder/sshHostrsaPubKey
/deis/builder/sshHostPubKey
/deis/builder/host
/deis/builder/port
/deis/scheduler

huh, that's an interesting error. Would you be willing to try the new Go client? We're looking to cut over this release and it might unblock you. Let me know and I can build you a v1.9.0 client :)

@bacongobbler I can build it, I think. Looks like I need to install the docker client, which I think mean brew install docker? but not boot2docker?

CGO_ENABLED=0 godep go build -a -installsuffix cgo -ldflags '-s' -o deis .
deis.go:10:2: cannot find package "github.com/deis/deis/client-go/parser" in any of:
        /usr/local/Cellar/go/1.4.2/libexec/src/github.com/deis/deis/client-go/parser (from $GOROOT)
        /Users/bfleischer/projects/deis/Godeps/_workspace/src/github.com/deis/deis/client-go/parser (from $GOPATH)
        /Users/bfleischer/gocode/src/github.com/deis/deis/client-go/parser
deis.go:11:2: cannot find package "github.com/deis/deis/version" in any of:
        /usr/local/Cellar/go/1.4.2/libexec/src/github.com/deis/deis/version (from $GOROOT)
        /Users/bfleischer/projects/deis/Godeps/_workspace/src/github.com/deis/deis/version (from $GOPATH)
        /Users/bfleischer/gocode/src/github.com/deis/deis/version
godep: go exit status 1
make: *** [build] Error 1

make on its own says
~/projects/deis/client-go
$ make
Missing `docker` client which is required for development
make: *** [check-docker] Error 2

You'll have to move deis/deis to $GOPATH/src/github.com/deis/deis or else godep wont be able to find anything under the "github.com/deis/deis" package.

Ok, got it to build but haven't played with it yet.  In the meantime, pip version is working fine.
Here's my steps from start to finish :)
unset GOROOT
export GOPATH="$HOME/gocode"
echo $GOPATH
go env

go get github.com/tools/godep

mkdir -p  $GOPATH/src/github.com/deis
cd $GOPATH/src/github.com/deis
git clone deis/deis
export DEIS=$GOPATH/src/github.com/deis/deis

cd $DEIS
git remote add upstream https://github.com/deis/deis.git

cd $DEIS/deisctl
  make build
 # Running make install will install the deisctl command in $GOPATH/bin/deisctl
 ./deisctl -h

cd $DEIS/client-go/
  make build
  # Running make install will install the deis command in $GOPATH/bin/deis
 ./deis -h
 ./deis --version

The python client is deprecated and will be removed with the v1.10.0 release. If you see similar issues with the new go CLI, please open a new issue.


Adding Doubtnut app clone

Doubtnut app clone
Doubtnut is an app for competitive exams like JEE and NEET.

[x] Html
[x] CSS

/assign

/assign


Drop support for EOL Python 3.6 and test CI on Windows and macOS

Follow on from https://github.com/python-twitter-tools/twitter/pull/451#issuecomment-1246747905.
Drop support for Python 3.6, end-of-life on 2021-12-23.
On the CI, test Ubuntu with:

Python 2.7 (CPython and PyPy)
the lowest and highest 3.x versions
Any dev versions

And also test Windows on 3.8 and macOS 3.9.

Not sure to understand why coveralls fails
https://github.com/python-twitter-tools/twitter/actions/runs/3058141268/jobs/4935255053

I wonder if it's because the action isn't running on macOS and Windows? I added if: matrix.is == 'ubuntu-latest' because it said it was Linux only.
I've split out the 3.6 drop into https://github.com/python-twitter-tools/twitter/pull/454 to see what happens.

https://github.com/python-twitter-tools/twitter/pull/454 passed.
I've split this PR to add just Windows and macOS and it still fails.
I've reported this upstream to the action to ask for advice: https://github.com/AndreMiras/coveralls-python-action/issues/23

I merged 454, and let's wait for their answer before moving on with windows/mac then, thanks!


Failed Travis-CI test for ruby 1.9.3

Since weppos/publicsuffix-ruby only supports ruby > v2.0.0 and ruby v1.9.3 support ended, Support for Ruby 1.9.3 has ended.
ruby v1.9.3 Travis-CI support should be drop to fix failing of test or allow to fail?
What do you think @leereilly?

^ @tmcw @afeld

I'm fine with dropping Ruby < 2 support, though we should jump a major version. I'm AFK but can submit a PR tomorrow if someone else doesn't get a chance.

If it's okay with you @afeld, I can submit a PR now.

Go for it!

Oh! I'm late.


checkpoint condition should be modified

Thanks for your clear implementation of KD. There is a little mistake about the condition that a new epoch should be saved as checkpoint. You should assign current value of "acc" to "max_accuracy", after each checkpoint.

Surprisingly missed that!! Feel free to send a PR. Or I will see when I can get a chance to fix it


added android for getting started in Launcher

Added Android setup instructions for using Launcher in Launcher.md

@dotnet-policy-service agree


Aladin - SHMU Slovensko

I would like to ask you to create Aladin - SHMU Slovakia?
Or you can recommend me another source.
Thank you.

@vawaver do you have some API source for slovak Aladin?

@vawaver do you have some API source for slovak Aladin?

I am very sorry, I do not know anything about programming. So API neither.

It’s not possible without API with Slovak Aladin.

Understand. Thank you.


move channel logic into it's own class

Currently using Aup.open does return the instance of Aup itself.  Which makes it impossible to work with to channels at the same time.
Having open return a file-like object that is the project instance itself is somewhat unexpected.
This patch creates a separate instance when running open making it possible to run more than one open.

The diff looks a lot bigger than it is.  There is no change to the actual code at all. Just moving things around :]

Thanks for the work!


Suggestions

Can we be allowed to enable all snap options, i would rather have vertices and edge points and face centre always on to and from only turing them off if i need to.
Align to normal of the snap point would be nice as someone suggested before
Rotations?
Can we rotate from one point to another from the snapping selections
Say a get a vertex point from the selected object it becomes the rotation centre, i then select another vertex on the selected object which sets the rotation axis we then can snap to another object based on the snap options available. I guess theres some complications with the axis modes but it would be good just just have available working in global axis so you set the two points and use x,y,z to set rotation direction
Could do scale to to complete the set, which would be as simple as grab two points on a object and scale in that lines direction to another snap point on another object
This is an amazing addon and should be defaults behaviour, blenders snapping has always been a pain
Thankyou for this addon!!!

Love this addon!
I piggyback on this issue since I want to suggest something similar. Snap edge of ObjectA to edge of Object B - however also rotate A, so the edges of both objects have the same "orientation".
Same with faces. Rotate A so its selected face has same orientation as a face of Object B.
I know this would make the addon a little bit more complex but I think you can hide the functionality, so beginners don't even know it exists.

Is it possible to add snap 3d cursor function to the addon ?


PARQUET-598: Test writing all primitive data types

Minor comments, but this is great, thanks.

Addressed comments, Travis failed due to apt-Problems (can someone retrigge it?)

You will have to push an empty commit. AFAIK there is no other way.

@xhochy what I usually do in these cases is git commit --amend to bump the git hash without committing anything new

Successfully rebased.

+1, thank you


Migrate out of react-responsive to @mantine/hooks

Description

Closes #2967.
TODO:

[ ] Migrate/remove MediaQuery HOC
[ ] Remove react-responsive from package.json

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test

Checklist

[ ] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 2 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 33.067%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/mobileWorkspace/MobileWorkspace.tsx
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5299

Relevant Lines:
14891

💛  - Coveralls


Test: Do some manual testing of the watch/live reload

I have some nagging feeling that there is still are some glitches with the live reload / watch / rebuild. I have some weird encounters when it doesn't work, but when I restart the server ... it starts to work.
I will keep this as a placeholder for some testing that needs to be done before 0.16.
I'm on OS X. Would be great if others could chime in with their experiences.
A test scenario I think would cover most bases would be:
Start hugo serveron a site:

[ ] Edit an image or CSS in /static and verify that it's loaded OK.
[ ] Edit a md file in /content and ...
[ ] Add a new image to /static
[ ] Add a new md file to /content
[ ] Remove an image from /static
[ ] Remove a md file from /content
[ ] Edit a layout file
[ ] Edit a shortcode and verify that pages gets updated

Start hugo server --renderToDisk on a site:

[ ] Edit an image or CSS in /static and verify that it's loaded OK.
[ ] Edit a md file in /content and ...
[ ] Add a new image to /static
[ ] Add a new md file to /content
[ ] Remove an image from /static
[ ] Remove a md file from /content
[ ] Edit a layout file
[ ] Edit a shortcode and verify that pages gets updated

If you perform the test above, please make sure you test with a Hugo built from the latest source and report back what OS/platform you tested on.

Operating system: Ubuntu 15.10
Start hugo server on a site:

[ ] Edit an image or CSS in /static and verify that it's loaded OK.
[ ] Edit a md file in /content and ...
[ ] Add a new image to /static
[ ] Add a new md file to /content
[ ] Remove an image from /static
[ ] Remove a md file from /content
[ ] Edit a layout file
[ ] Edit a shortcode and verify that pages gets updated

Start hugo server --renderToDisk on a site:

[ ] Edit an image or CSS in /static and verify that it's loaded OK.
[ ] Edit a md file in /content and ...
[ ] Add a new image to /static
[ ] Add a new md file to /content
[ ] Remove an image from /static
[ ] Remove a md file from /content
[ ] Edit a layout file
[ ] Edit a shortcode and verify that pages gets updated

FWIW, I find about half the time I run Hugo server, the livereload doesn't work when I update my SASS files.
I should note that this is not just a matter of the watch on the static folder, since my gulp assets actually write the minified CSS to an HTML partial I include in my  for the sake of critical render path in addition to writing to a style.min.css file I keep in the static folder.
Sent from my iPhone

On Apr 24, 2016, at 6:19 AM, digitalcraftsman<EMAIL_ADDRESS>wrote:
Operating system: Ubuntu 15.10
Start hugo server on a site:
Edit an image or CSS in /static and verify that it's loaded OK.
Edit a md file in /content and ...
Add a new image to /static
Add a new md file to /content
Remove an image from /static
Remove a md file from /content
Edit a layout file
Edit a shortcode and verify that pages gets updated
Start hugo server --renderToDisk on a site:
Edit an image or CSS in /static and verify that it's loaded OK.
Edit a md file in /content and ...
Add a new image to /static
Add a new md file to /content
Remove an image from /static
Remove a md file from /content
Edit a layout file
Edit a shortcode and verify that pages gets updated
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

Operating system: Windows 8.1
Start hugo serveron a site:

[ ] Edit an image or CSS in /static and verify that it's loaded OK.
[ ] Edit a md file in /content and ...
[ ] Add a new image to /static
[ ] Add a new md file to /content
[ ] Remove an image from /static
[ ] Remove a md file from /content
[ ] Edit a layout file
[ ] Edit a shortcode and verify that pages gets updated

Start hugo server --renderToDisk on a site:

[ ] Edit an image or CSS in /static and verify that it's loaded OK.
[ ] Edit a md file in /content and ...
[ ] Add a new image to /static
[ ] Add a new md file to /content
[ ] Remove an image from /static
[ ] Remove a md file from /content
[ ] Edit a layout file
[ ] Edit a shortcode and verify that pages gets updated

On my OS X with Byword as Markdown editor:
Start hugo serveron a site:

[x] Edit an image or CSS in /static and verify that it's loaded OK.
[ ] Edit a md file in /content and ... FAILED
[x] Add a new image to /static
[x] Add a new md file to /content
[x] Remove an image from /static
[x] Remove a md file from /content
[x] Edit a layout file
[x] Edit a shortcode and verify that pages gets updated

Start hugo server --renderToDisk on a site:

[x] Edit an image or CSS in /static and verify that it's loaded OK.
[] Edit a md file in /content and ... FAILED
[x] Add a new image to /static
[x] Add a new md file to /content
[x] Remove an image from /static
[x] Remove a md file from /content
[x] Edit a layout file
[x] Edit a shortcode and verify that pages gets updated

The content file issue is editor specific, it seems. I'll create an issue for that.


Add additional database compatibility

Add compatibility for MS SQL Server
Default SQL keepalive statement to a more compatible "SELECT 1"
Prevent one broken keepalive from disabling entire functionality

I've used a version of 1.3.1 but obviously change to whatever you see fit.  If it doesn't recognise the database type, it'll try to use "SELECT 1" which works on most databases other than Oracle.  It'll also print out the database product name so it can be explicitly added if needed.

@bertbert72 I'm really sorry that I haven't been able to merge yet. Will do my best to merge by the end of Nov.

:) No worries. There's obviously no rush. We've all got real lives too. If anybody is really "desperate", they can grab the fork. If you need me to make any changes, just let me know.


Separate training script into main part and data submodule to avoid an error related to NVIDIA DALI.

This PR fixes an issue #8063. Would you please review and merge this PR if it's ok!

Absolutely, thanks a lot for the PR. The changes LGTM so let me just verify it with the CI.

Jenkins, test this please.

Jenkins CI test (for commit ac3bbe04cdf4feaffdd741caf64714603d043e1d, target branch master) succeeded!


Use go modules and simplify build

This patch introduces the new and shiny go modules to the build system. Third party libraries are now handled out of the box by go. I added a GO variable to the Makefile such that the name of the go tool can be overwritten via, for instance, an environmental variable.
Since it is not needed any more, I removed glide.
$ make GO=go1.11
GOARCH=amd64 go1.11 build -a -ldflags "-X main.revision=ef195d6 -w -extldflags=" -tags "" -o target/fzf-linux_amd64
go: finding github.com/codegangsta/cli v0.0.0-20171128035504-c6af8847eb2b
go: finding github.com/mattn/go-runewidth v0.0.0-20170201023540-14207d285c6c
go: finding github.com/gdamore/encoding v0.0.0-20151215212835-b23993cbb635
go: finding github.com/mattn/go-shellwords v1.0.3
go: finding github.com/mitchellh/go-homedir v0.0.0-20161203194507-b8bc1bf76747
go: finding github.com/lucasb-eyer/go-colorful v0.0.0-20170223221042-c900de9dbbc7
go: finding github.com/gdamore/tcell v0.0.0-20170915061752-0a0db94084df
go: finding golang.org/x/sys v0.0.0-20170529185110-b90f89a1e7a9
go: finding golang.org/x/text v0.0.0-20170530162606-4ee4af566555
go: finding gopkg.in/yaml.v2 v2.0.0-20171116090243-287cf08546ab
go: finding github.com/mattn/go-isatty v0.0.0-20160806122752-66b8e73f3f5c
go: finding github.com/Masterminds/vcs v1.12.0
go: finding golang.org/x/crypto v0.0.0-20170728183002-558b6879de74
go: finding github.com/Masterminds/semver v1.4.0
go: downloading github.com/mattn/go-shellwords v1.0.3
go: downloading github.com/mattn/go-isatty v0.0.0-20160806122752-66b8e73f3f5c
go: downloading golang.org/x/crypto v0.0.0-20170728183002-558b6879de74
go: downloading github.com/mattn/go-runewidth v0.0.0-20170201023540-14207d285c6c
go: downloading golang.org/x/sys v0.0.0-20170529185110-b90f89a1e7a9

I also updated the travis config to actually use a go test environment rather than a ruby one.

I must think of a way how to include the remaining tests. So, this is not ready to merge yet.

This pull request is ready to go.

AFAIK go mod init migrates dependencies from glide, govendor, ... automatically. I updated the dependencies with make update after initializing the module and only committed the updated version.

Merged, thanks!

Nice, thanks!


ternary consortium does not have a dinitrogen flux

Hi @mcnaughtonadm
The flux for EX_n2_e is zero in azotobacter for the ternary consortia.
Instead, it appears to be using $NO_3$ as the nitrogen source

Image thanks to @ShantMahserejian

Okay, looks like n2 isn't in the medium. Will rerun with it included.

N2 is expensive to consume.  Might want to consider removing n03 from the media, too.

Also just noticed that the medium appears to contain glc__D and leu__L  and does not appear to need sucr__D
What changes to the consortia are needed to get it to grow using co2 and n2 as the only carbon and nitrogen sources?

Hey @mcnaughtonadm thanks for pushing this task through to completion.  When @ShantMahserejian  has generated the new ternary alluvial diagram, we can close this issue

I ran the ternary under 2 new conditions:

With CO2 and N2 as the sole carbon and nitrogen sources provided in the combined media.
Same as 1. but with the photons reduced to only the 530 and 690 wavelengths. These are the only ""metabolites"" being used in FBA so this should clear some visual clutter of the alluvial.

ternary_model_co2_n2_growth_reduced_photons.csv
ternary_model_co2_n2_growth.csv

This growth condition can help center some of the model curation that needs to be done as this provides incomplete community growth as is.

Here's the alluvial diagram for the updated model and fluxes.

Note 1: The flux values have been log-log transformed to aid visualization
Note 2: that Andrew passed me two flux files, one with reduced photon fluxes, though both produced the same diagram results

This is fabulous!
At first I was a bit surprised, because it appeared as if Rhodo was fixing CO2 (which would be bad), but then I saw that what it actually appears to be doing is converting CO2 to HCO3 (which isn't perfect, but is not nearly as bad).  Furthermore, it is clear that more CO2 is being consumed by Syn than is produced by Azo (which is good).   Ideally, we would separate out CO2 so that there is the flux of CO2 that is coming from the media, and then there is the CO2 that is exchanged, but if you don't have time for that, I can always explain why what appears counterintuitive still makes sense during the poster session if there is time.

[ ] For @mcnaughtonadm  create a source metabolite for co2 and h2o and o2
[ ] For @ShantMahserejian create new source metabolites on the left-hand side of the alluvial diagram
[ ] For @mcnaughtonadm remove the reaction that converts co2 to hco3 in rhodo and see if we can remove a confusing flux
[ ] What happened to the excreted metabolites?  Is this because there is no-growth?
[ ] Should we have a flux for biomass (even though it isn't technically an exchange metabolite. It seems to be a good sink metabolite


However, I only tested on Pepper, I'm not sure yet what happens when I tried it on Nao.
rosservice call /get_move_config "move_config_name:
  data: 0"
move_config:
  max_vel_xy: 0.550000011921
  max_vel_theta: 2.0
  max_acc_xy: 0.550000011921
  max_acc_theta: 3.0
  max_jerk_xy: 5.0
  max_jerk_theta: 50.0
  torso_wy: 0.174532920122

 rosservice call /get_move_config "move_config_name:
  data: 1"
move_config:
  max_vel_xy: 0.10000000149
  max_vel_theta: 0.20000000298
  max_acc_xy: 0.10000000149
  max_acc_theta: 0.10000000149
  max_jerk_xy: 0.20000000298
  max_jerk_theta: 0.20000000298
  torso_wy: -0.174532920122

 rosservice call /get_move_config "move_config_name:
  data: 2"
move_config:
  max_vel_xy: 0.34999999404
  max_vel_theta: 1.0
  max_acc_xy: 0.300000011921
  max_acc_theta: 0.75
  max_jerk_xy: 1.0
  max_jerk_theta: 2.0
  torso_wy: 0.0

@suryaambrose can you verify this?

See my comment here : https://github.com/ros-naoqi/naoqi_bridge_msgs/pull/20#issuecomment-258619746

This is an old pull-request.
This may cause unexpected trouble when it is merged.
I close this and improve this in my local.
I'm sorry to leave this for a long time.


Fix bug in complex grammar

Summary
Closes #258. Implement fix suggested by @aspcompiler.
Details and comments

@jakelishman, I think your argument has merits, however, I'll leave this to the grammar WG to decide on how to proceed.

For sure - definitely not something that needed addressing here.

+1 to discuss the refactoring of this part of grammar in grammar WG.


feat(Degeneration): Added the inspection of degenerated polygons in S…

…urfaceMeshes and polyhedra in SolidMeshes.

:tada: This PR is included in version 2.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


transfer not done

Good evening, please request to ensure that the transaction is confirmed because it is not appear , attached link of hash
https://insight.bitpay.com/tx/0d38126439304d53483c467b7b953ba5bb814fe78e47400fb175ac2921345ee9

Dear
I have a digibyte account on google. Transaction on 1,060,360 dgb account on 5/5/2017. But I do move to another account not. And it's display is locked waiting for confirmation. Thanks admin for help
https://digiexplorer.info/tx/b2a4612fddd0604dff7857b9624755e01f654b4f818d98c60f08e87761910701


Template didn't rerender when 2 routes render the same template

I have 2 route / and /sell linked to the same Template, but when I switch from one to the other, the template isn't reloaded (so ReactiveVar aren't updated).
This is my router:
FlowRouter.route('/', {
  name: "dashboard",
  action() {
    console.log('go to buy');
    BlazeLayout.render("layout", {nav: "publicNav", main: "dashboard"});
  }
});
FlowRouter.route('/sell', {
  name: "dashboard-sell",
  action() {
    console.log('go to sell');
    BlazeLayout.render("layout", {nav: "publicNav", main: "dashboard"});
  }
});

And the basic template onCreated function:
Template.dashboard.onCreated(function () {
  console.log('Route name: ', FlowRouter.current().route.name)
})

So whem I call / and I try to switch multiple times, I got:
go to buy
Route name:  dashboard
go to sell
go to buy
go to sell

And When I start with /sell (hard refresh) I got:
go to sell
Route name:  dashboard-sell
go to buy
go to sell

How can I avoid that ? Or at least bind a function on this update event ?

This issue is a duplicate of https://github.com/kadirahq/blaze-layout/issues/65.
Would be great to see this resolved. :)

+1

+1
Has anyone come up with a workaround? This has become a show-stopper for me in my little project. :-(

Another way to do it, use the FlowRouter.watchPathChange() function:
Template.testPage.onCreated(function() {
  Tracker.autorun(function() {
    FlowRouter.watchPathChange();
    /* .. some update here .. */
  });
})

This is what I did to get around the issue. I reset BlazeLayout with a global trigger that fires for every route and clean out the DOM. Put this on top of your routes.js file.
function resetBlazeLayout() {
  BlazeLayout.reset();
}

FlowRouter.triggers.enter([resetBlazeLayout]);

I can't find the documentation for BlazeLayout.reset() so it is unlikely to be part of the supported API for BlazeLayout
You'll need to hunt down bits like onhover-tooltips that are inserted by your UI framework. Not the prettiest solution, but everything about routing is in the same file, which is nice.


Funky font rendering when rendering multiple different PDFs

Description
PDF.js renders font inconsistently and incorrectly when rendering multiple PDFs. Issue does not always appear, and never seems to appear when only one PDF document is being rendered. Issue does not appear to be tied to any specific browser or operating system (see browsers tested below).
Screenshots (Expected and Actual)

PDF.js Version
Both stable (v1.1.114) and beta (1.1.125) from https://mozilla.github.io/pdf.js/getting_started/#download
Browsers Tested

Firefox 35.0.1 on Ubuntu 14.04 LTS
Firefox Dev Ed 41.0a2 (2015-07-12) on Ubuntu 14.04 LTS
Chrome 43.0.2357.81 (64-bit) on Ubuntu 14.04 LTS
IE 11.0.9600.17843 on Windows 7 Build 7601

Code Used
<body>
<script src="pdf.js"></script>
<script>

  function tryPDF(filename) {
    return PDFJS.getDocument(filename)
      .then(function(pdf) { return pdf.getPage(1); })
      .then(function(page) {
        var c = document.createElement('canvas');
        var v = page.getViewport(1.2);
        c.width = v.width;
        c.height = v.height;
        document.body.appendChild(c);
        return page.render({
          canvasContext: c.getContext('2d'),
          viewport: v,
        });
      });
  }

  Promise.all([
    tryPDF('compressed.tracemonkey-pldi-09.pdf'),
    tryPDF('pdf.pdf'),
    tryPDF('random.pdf'),
  ])
    .then(function() { console.log('done'); })
    .catch(console.error.bind(console));

</script>
</body>

PDFs used
http://mozilla.github.io/pdf.js/web/compressed.tracemonkey-pldi-09.pdf
http://www.pdf995.com/samples/pdf.pdf
https://www.mathworks.com/moler/random.pdf

Thanks for the detailed report. I've reproduced the issue and created a unit test. I'll follow up later with a fix.

Is this issue perhaps related to e.g. #5148, #5984, and #5992?

Ah yes, it does seem to be the same bug as #5148. Applying the fix (using random numbers) does indeed solve the issue, although not ideal. I hope a better fix could be integrated in future versions. Thank you.


Add contribution guidelines

Geode Version
v2.0.0
Related Problem
No response
Your Solution
Add a CONTRIBUTING.md file to the main repo, it's a little weird to only have it in the discord server (and I can't even find it there)
Additional Information
No response

we only have this page https://docs.geode-sdk.org/source/styling

Can you just link it to "contribution guidelines"... don't feel like making a pr for this


Unable to sign messages on Ledger for particular actions.

Hi! And thank you for reading!
Having some issues with signing into some sites on my Ledger using Hiro. Some actions seem to work, others don't.
Am able to sign into gamma.io, can purchase items,

however -
I cannot edit my profile or sign the message hash with many sites. These include Console and many other web3 sites. A hot wallet version works but using my Ledger sadly leaves me in the cold to call it functioning.

This is the main error I get and it replicates when I use my Nano S as well as my Nano S+. Both updated to the latest firmware and software versions from ledger live.

Awesome you also made a ticket here. We expect this to get resolved with the resolution to this issue here: https://github.com/hirosystems/stacks-wallet-web/issues/2725
The fix is built but it takes some more time for Ledger to accept. The fix is for the Stacks app for Ledger Live, as soon as you get version 0.23.4 we expect this to be resolved. We'd love to hear from users after they get the new release.
You already know this but I thought this could be good to know for anyone else finding this.

Closing because it is a duplicate of #2725


Config variable to disable the package

You should be able to disable the package using a config variable (for use in pipelines etc.)

@danielwierden I added documentation for Local only installation.


sentinel rule Template issue

In the sentinel analytics we can find this rule called : Azure DevOps - Retention to Zero
with the following query logic:
AzureDevOpsAuditing
| where OperationName =~ "Pipelines.PipelineRetentionSettingChanged"
| where Data.SettingName in ("PurgeArtifacts", "PurgeRuns")
| where Data.NewValue == 0
| project-reorder TimeGenerated, OperationName, ActorUPN, IpAddress, UserAgent, Data
| extend timestamp = TimeGenerated, AccountCustomEntity = ActorUPN, IPCustomEntity = IpAddress
However, in the Azure DevOps Portal, it prevents the user from setting the retention value to zero
basically there is NO WAY to set the value to zero. so what is the purpose of this rule template given that it is impossible to trigger.

The query has been modified now to address the issue.
https://github.com/Azure/Azure-Sentinel/blob/master/Detections/AzureDevOpsAuditing/ADORetentionReduced.yaml


skrooge: 2.10.5 -> 2.11.0

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/a0n4s1xpwchl3d7d3pk50bd1pf2acldp-skrooge-2.11.0/bin/skroogeconvert -h got 0 exit code
ran /nix/store/a0n4s1xpwchl3d7d3pk50bd1pf2acldp-skrooge-2.11.0/bin/skroogeconvert --help got 0 exit code
ran /nix/store/a0n4s1xpwchl3d7d3pk50bd1pf2acldp-skrooge-2.11.0/bin/skroogeconvert -v and found version 2.11.0
ran /nix/store/a0n4s1xpwchl3d7d3pk50bd1pf2acldp-skrooge-2.11.0/bin/skroogeconvert --version and found version 2.11.0
ran /nix/store/a0n4s1xpwchl3d7d3pk50bd1pf2acldp-skrooge-2.11.0/bin/skroogeconvert -h and found version 2.11.0
ran /nix/store/a0n4s1xpwchl3d7d3pk50bd1pf2acldp-skrooge-2.11.0/bin/skroogeconvert --help and found version 2.11.0
found 2.11.0 with grep in /nix/store/a0n4s1xpwchl3d7d3pk50bd1pf2acldp-skrooge-2.11.0

cc "@joko"

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘kxmlgui-5.43.0’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/development/libraries/kde-frameworks/default.nix:94 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0/lib/libskgbankgui.so.2.11.0
shrinking /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0/lib/libskgbasegui.so.2.11.0
shrinking /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0/lib/libskgbankmodeler.so.2.11.0
shrinking /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0/lib/libskgbasemodeler.so.2.11.0
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0/lib  /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0/bin
patching script interpreter paths in /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0
checking for references to /tmp/nix-build-skrooge-2.11.0.drv-0 in /nix/store/fyr0pcs63da1b0bl8qfq0pgjj01s8xh9-skrooge-2.11.0...
postPatchMkspecs
postPatchMkspecs

Failure on aarch64-linux (full log)
Partial log (click to expand)
cannot build derivation '/nix/store/kvkw13f2kr40m6wsn6mlpfhvisvyxbqk-kactivities-5.43.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/28hmbhdqxagq4fdrh7pdv4x2ax4g3w19-kdeclarative-5.43.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/5p00cag7k0awygqvc8asi8rfxmmd8w7r-kdesignerplugin-5.43.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/lhjv5a7mjnnwp4p8n9crgi1raj1vfz0i-knewstuff-5.43.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/15c423sjhn7rg97h7z9mn6pa7sg527dp-knotifyconfig-5.43.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/i9vgb8c7sd0mfsmqs6lz1i6y5klp4crk-kparts-5.43.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/w5hb3di4a6cdi1r66a2i8rqlzwd4d33h-plasma-framework-5.43.0.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/bw0qsisyilzjgvprgiv2xdzrhzdrwaia-krunner-5.43.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/qmggv08iwz0agpr1idi8jygla25drxvi-skrooge-2.11.0.drv': 6 dependencies couldn't be built
error: build of '/nix/store/qmggv08iwz0agpr1idi8jygla25drxvi-skrooge-2.11.0.drv' failed


Notification when the endpoint of a datasourse is down

add an error message to all the functions to reflect if the endpoint of the datasource is down.

added to all the annotator stuff


Add NVIDIA config for Dell XPS 15 7590

Description of changes
Add hardware configuration for the Dell XPS 15 7590 with NVIDIA graphics.
Things done
Import the Intel-based config, the common NVIDIA config and add the necessary bus IDs.
Not sure whether we are supposed to add hardware.nvidia.powerManagement.enable = true; here or leave it to the user to decide to enable it or not (I did personally).

[x] Tested the changes in your own NixOS Configuration
[ ] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

bors merge


Document supervision tree and worker concurrency limits/config

Is there a max worker concurrency? Can I configure it?

I have documented this here https://hexdocs.pm/rihanna/Rihanna.Config.html#content but admittedly it's not obvious.
Do you think there should be a new documentation page outlining an overview of Rihanna in general, aside from the README and moduledocs?


Add missing initialization of the Http11AbsolutePathWithPort test

Add missing initialization of the Http1ServerConnectionImplTest.Http11AbsolutePathWithPort test
Risk Level: Low
Testing: Unit Test
Docs Changes: N/A
Release Notes: N/A
Signed-off-by: Yan Avlasov<EMAIL_ADDRESS>

How does this pass in our CI out of curiosity?

It failed (internal google) msan build which we do run in CI. I suspect it is flaky, just has not been ran enough times.


inferno-fela: Uncaught TypeError: Cannot read property 'bind' of undefined

Version: 5.0.2
Environment: DOM
Type: Bug
Description
I'm getting the error while trying to reproduce  Composition example  with the latest inferno and fela versions
index.js:347 Uncaught TypeError: Cannot read property 'bind' of undefined
    at createReactCompositeComponent (index.js:347)
    at updateReactComponent (index.js:250)
    at createReactCompositeComponent (index.js:341)
    at updateReactComponent (index.js:250)
    at Object.componentAdded (index.js:163)
    at inferno.options.afterMount (index.js:468)
    at eval (index.js:2171)
    at Lifecycle.trigger (index.js:84)
    at Object.render (index.js:1128)
    at render (index.js:75)

component.js
import { createComponent } from 'inferno-fela'

const a = () => ({ backgroundColor: 'black' })

const b = () => ({ color: 'white' })

const A = createComponent(a)
const B = createComponent(b, A)

const MODULE = () => <B>{'test'}</B>

export default MODULE

index.js
const render = (container) => {
  Inferno.render(
    <Redux store={store}>
      <Fela renderer={styler}>
        <PageHome/>
      </Fela>
    </Redux>,
    document.getElementById('app')
  )
}

@tajo

My original reason for the fork was to prevent createComponent(createComponent(...)) since I believe it's an anti-pattern (there are much better ways how to combine styles if necessary)

Can that be the reason? Then what is the better way to combine styles?

^ Looks like a bug to me. I'll look into it later.

Can that be the reason?

I don't think that's the reason.

Then what is the better way to combine styles?

http://fela.js.org/docs/api/fela/combineRules.html

Probably relative to this issue. I get this error on HMR
index.js:16 Uncaught (in promise) TypeError: Cannot read property 'prototype' of undefined
    at isStatefulComponent (index.js:16)
    at createVNode (index.js:2410)
    at eval (index.js:93)
    at eval (index.js:94)
    at Object.hotApply [as apply] (index.js:567)
    at cb (process-update.js:52)
    at eval (process-update.js:68)
    at <anonymous>

I've started to get it after migrating from styled-components to fela

Hmm. I am sadly not really familiar with Inferno's internal Component structure. Thought it'd mimic the React way and therefore just work as expected. Not sure where this issue comes from. Any help/suggestions are really appreciated.

@oleksiibilous Does this only happen if you use createComponent with another "createComponent"-component?

Could you provide a simple debugable example somehow? I basically got no time to set one up, but would like to hack it a bit.

Sure, will do later today

You know what? I cannot reproduce it anymore. It was a kind of blocker for me, so I switched to inferno-compat & react-fela. There where several inferno releases after. Probably one of them fixed the problem. However, I reproduced the issue with the HMR. It is rather annoying than critical. Maybe you can suggest what is wrong
Here is the code: https://github.com/oleksiibilous/example-fela-hmr

After running yarn && yarn serve open localhost:8000 in your browser
Open console logs and you will see no errors
Go to src/components/home.js and change any rule
Go to the browser and wait before the page will be automatically updated
Then you should see the error

Let me know if you couldn't reproduce it. I'll make a screencast for you

Hmm. I tried to reproduce that last one as well, but I can't. Seems to work just fine for me?


cannot pass verification - stopping bot now

cannot pass verification - stopping bot now
0.0.1-Beta
LDPLAYER 9

I apologize for the late reply

Delete the devices_config.json file in the main directory and the files in the save folder
Restart the bot
Check if your device is online with the adb devices command.

maybe the error is because lilith has updated the new captcha


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/eventing-kafka 63ae784...723ad05:
  > 723ad05 upgrade to latest dependencies (# 1157)
bumping knative.dev/eventing-redis bed308b...e727201:
  > e727201 upgrade to latest dependencies (# 323)
bumping knative.dev/reconciler-test f0e3dfa...f14902d:
  > f14902d upgrade to latest dependencies (# 331)
bumping knative.dev/eventing 3abb436...2219e14:
  > 2219e14 Fix performance tests setup (# 6340)
bumping knative.dev/pkg 1f681e1...2d552be:
  > 2d552be Add genreconcile for core/v1 Node (# 2503)
  > fd05bf1 upgrade to latest dependencies (# 2500)

/lgtm
/approve


CE pipeline migration

Tested in my personal account: https://travis-ci.com/xabxx/health-metrics-collector-ros1/builds/101353262

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-v1@fe342d0). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             release-v1       #8   +/-   ##
=============================================
  Coverage              ?   87.21%
=============================================
  Files                 ?       13
  Lines                 ?      133
  Branches              ?        0
=============================================
  Hits                  ?      116
  Misses                ?       17
  Partials              ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fe342d0...362d4a1. Read the comment docs.


Bug: SingleFile was not able to archive the page

Describe the bug
Using the latest stable docker image for arm64, no matter what site I try to archive, SingleFile always gives me the same error: SingleFile was not able to archive the page. All the other options seem to work fine.
Steps to reproduce

Add+
Choose Auto-detect parser, depth=0, SingleFile for Archive methods
Submit.

Screenshots or log output
Log after submission

Log
[+] [2022-11-28 06:38:05] Adding 1 links to index (crawl depth=0)... > Saved verbatim input to sources/1669617485-import.txt > Parsed 1 URLs from input (Generic TXT) > Found 1 new URLs not already in index [*] [2022-11-28 06:38:05] Writing 1 links to main index... √ ./index.sqlite3 [▶] [2022-11-28 06:38:05] Starting archiving of 1 snapshots in index... [+] [2022-11-28 06:38:05] "www.betanews.com" https://www.betanews.com > ./archive/1669617485.841526 > singlefile Extractor failed: SingleFile was not able to archive the page Got single-file response code: 0. TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md Run to see full output: cd /data/archive/1669617485.841526; /node/node_modules/single-file/cli/single-file --browser-executable-path=chromium "--browser-args=[\"--headless\", \"--no-sandbox\", \"--disable-gpu\", \"--disable-dev-shm-usage\", \"--disable-software-rasterizer\", \"--run-all-compositor-stages-before-draw\", \"--hide-scrollbars\", \"--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.61 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)\", \"--window-size=1440,2000\"]" https://www.betanews.com singlefile.html 2 files (238.3 KB) in 0:00:00s [√] [2022-11-28 06:38:06] Update of 1 pages complete (0.23 sec) - 0 links skipped - 1 links updated - 1 links had errors Hint: To manage your archive in a Web UI, run: archivebox server <IP_ADDRESS>:8000 [+] [2022-11-28 06:38:05] Adding 1 links to index (crawl depth=0)... > Saved verbatim input to sources/1669617485-import.txt > Parsed 1 URLs from input (Generic TXT) > Found 1 new URLs not already in index [*] [2022-11-28 06:38:05] Writing 1 links to main index... √ ./index.sqlite3 [▶] [2022-11-28 06:38:05] Starting archiving of 1 snapshots in index... [+] [2022-11-28 06:38:05] "www.betanews.com" https://www.betanews.com > ./archive/1669617485.841526 > singlefile Extractor failed: SingleFile was not able to archive the page Got single-file response code: 0. TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md Run to see full output: cd /data/archive/1669617485.841526; /node/node_modules/single-file/cli/single-file --browser-executable-path=chromium "--browser-args=[\"--headless\", \"--no-sandbox\", \"--disable-gpu\", \"--disable-dev-shm-usage\", \"--disable-software-rasterizer\", \"--run-all-compositor-stages-before-draw\", \"--hide-scrollbars\", \"--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.61 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)\", \"--window-size=1440,2000\"]" https://www.betanews.com singlefile.html 2 files (238.3 KB) in 0:00:00s [√] [2022-11-28 06:38:06] Update of 1 pages complete (0.23 sec) - 0 links skipped - 1 links updated - 1 links had errors Hint: To manage your archive in a Web UI, run: archivebox server <IP_ADDRESS>:8000

This is probably easier to read:

In the logs, in the CMD STR, I see this:
CMD STR

Log
/node/node_modules/single-file/cli/single-file --browser-executable-path=chromium --browser-args=[\"--headless\", \"--no-sandbox\", \"--disable-gpu\", \"--disable-dev-shm-usage\", \"--disable-software-rasterizer\", \"--run-all-compositor-stages-before-draw\", \"--hide-scrollbars\", \"--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.61 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)\", \"--window-size=1440,2000\"] https://www.betanews.com singlefile.html

Again, if easier to read

If I pull up a shell in the docker instance and run the above command, I get:
bash: syntax error near unexpected token `('

If I remove the user-agent from that command, I get 'Unexpected end of JSON.'
I tried setting the CHROME_USER_AGENT to
- CHROME_USER_AGENT="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

under archivebox -> environment in docker-compose.yml, I get the same 'Unexpected end of JSON" error.

Running Ubuntu 22.04.1
Docker version: Docker version 20.10.21, build baeda1f

Can you try running the most basic case outside of docker to confirm singlefile works on that URL:
npm install single-file

single-file https://www.betanews.com singlefile.html

# open singlefile.html

The /data/archive directory has the json file and the index.html with the archive types, but no HTML file with contents of the website.
I should have been more clear, the betanews site is not the only one causing issues, but any site I tried.
I installed single-file outside of docker using npm and tried the following:
single-file https://betanews.com --back-end=puppeteer --browser-executable-path $(which chromium) betanews.html

The betanews.html contained the html as expected.


Using Format to genarate form widget

I have been taking a look at json-schema and liform-react. I know it is possible to specify a format for a field. The current implementation of liform-react utilises the type property of every schema-property to determine the widget to make use of. However the use the format property together with the type property will make the choosing of appropriate widget more effective. For example,
"properties": {
                    "contents": {
                        "description": "content (plain-text only)",
                        "format": "textarea",
                        "propertyOrder": 3,
                        "type": "string"
                    },
                    "mode": {
                        "default": "0644",
                        "description": "filesystem permissions",
                        "maxLength": 4,
                        "minLength": 3,
                        "pattern": "^[0-7]*$",
                        "propertyOrder": 2,
                        "type": "string"
                    },
                    "path": {
                        "description": "filesystem path",
                        "propertyOrder": 1,
                        "type": "string"
                    }
                }

from the above schema,  we can see that using the type property of content, path and mode will give us an appropriate widget, however what if we did have a textarea widget and we made us of the format property of content to choose the widget. That'd more efficient.
My proposal is that we check for the format property and return if a valid widget is found for it, else we fallback to using the type property. This double checking will help increase our widget choice efficiency.

We can already do this. If you have a property
 'color': { 'type':'string', 'widget': 'color', 'title': 'In which color' },

It will look for the widget color. If it was
 'color': { 'type':'string', 'title': 'In which color' },

It would use the widget string instead.

I was following the json-schema standards following this docs, and i believe it's going to be more standards to enable the format property too for this check given that most people may already have followed those standards and setup their schema with the format property.

Ok, it may be good idea:
If widget is present, use widget.
Otherwise: If format is present, then use format.
Otherwise: use type.
Would that be ok?

Yes, that will be okay, I will clean up the code I have written for this and submit a PR by the end of the week.


How to sort tabarray like array elements (via drag-drop)?

Hi,
For simple arrays I see it's pretty simple to sort them via drag-drop. But last I checked, this doesn't seem to work for tabarrays.
Are there any plans to implement this? How difficult it is to do it.
I'm going to dig in the ui-sortable code to see how the array sorting is implemented but if anyone can give me a few pointers how to go about it wrt tabarray, that would be really awesome!
thanks,
san

I think it can be as easy as slapping on the ui-sortable directive here https://github.com/Textalk/angular-schema-form/blob/development/src/directives/decorators/bootstrap/tabarray.html#L8
Try it out! :)

Closing


[Sival, spi_dev] Tpm mode

This PR port the spi_device_tpm_tx_rx_test for Sival.
Note: This does not work on the current Cw310 + Hyperdebug for reasons explained here.

I rebased the PR. Regarding the changes needed on the FPGAs, I marked this test as broken and we can merge it. This way It can be used with Silicon and manual runs on FPGAs with the MOD.

I have an unrelated question: is the code in atomic_wait_for_interrupt really correct?
static void atomic_wait_for_interrupt(void) {
  irq_global_ctrl(false);
  if (!header_interrupt_received) {
    wait_for_interrupt();
  }
  irq_global_ctrl(true);
}

Since interrupts are globally enabled, an interrupt will wake up for code at wait_for_interrupt but it won't be serviced I believed? Therefore it seems to me that if the code actually enters the loop, it will get stuck. It should probably re-enabled and then re-disabled the interrupts immediately after wait_for_interrupt?

I have an unrelated question: is the code in atomic_wait_for_interrupt really correct?
static void atomic_wait_for_interrupt(void) {
  irq_global_ctrl(false);
  if (!header_interrupt_received) {
    wait_for_interrupt();
  }
  irq_global_ctrl(true);
}

Since interrupts are globally disabled, an interrupt will wake up the core at wait_for_interrupt but I believe that it won't be serviced. Therefore it seems to me that if the code actually enters the loop, it will get stuck. It should probably re-enabled and then re-disabled the interrupts immediately after wait_for_interrupt?

I think it is correct, the wfi only runs if no IRQ has fired. When it fires, the core wakes up, enables the global IRQ which allows it to be serviced and update the variable header_interrupt_received. Does that make sense?
Here's another place with an approach similar with what you suggested, but in this case undesirable IRQs can fire, but the test should not fail because of it:
https://github.com/lowRISC/opentitan/blob/c8de39a70f38a46c9546ae918798efeb49e03d67/sw/device/tests/aon_timer_irq_test.c#L132-L145

I have an unrelated question: is the code in atomic_wait_for_interrupt really correct?
static void atomic_wait_for_interrupt(void) {
  irq_global_ctrl(false);
  if (!header_interrupt_received) {
    wait_for_interrupt();
  }
  irq_global_ctrl(true);
}

Since interrupts are globally disabled, an interrupt will wake up the core at wait_for_interrupt but I believe that it won't be serviced. Therefore it seems to me that if the code actually enters the loop, it will get stuck. It should probably re-enabled and then re-disabled the interrupts immediately after wait_for_interrupt?

Some clarification here: You're correct that the interrupt won't be serviced while interrupts are "globally" disabled, but this is a misnomer. The only thing that is disabled is Ibex's jump to an ISR. The PLIC has still latched the pending interrupt and is maintaining the level signaling to Ibex (irq_global_ctrl() does nothing to the PLIC's handling of interrupts).
So, if an interrupt broke us out of WFI, we will immediately jump to its ISR once irq_global_ctrl(true) happens. However, this handling isn't quite right, as it forgets to check the condition again...

I have an unrelated question: is the code in atomic_wait_for_interrupt really correct?
static void atomic_wait_for_interrupt(void) {
  irq_global_ctrl(false);
  if (!header_interrupt_received) {
    wait_for_interrupt();
  }
  irq_global_ctrl(true);
}

Since interrupts are globally disabled, an interrupt will wake up the core at wait_for_interrupt but I believe that it won't be serviced. Therefore it seems to me that if the code actually enters the loop, it will get stuck. It should probably re-enabled and then re-disabled the interrupts immediately after wait_for_interrupt?

I think it is correct, the wfi only runs if no IRQ has fired. When it fires, the core wakes up, enables the global IRQ which allows it to be serviced and update the variable header_interrupt_received. Does that make sense? Here's another place with an approach similar with what you suggested, but in this case undesirable IRQs can fire, but the test should not fail because of it:
https://github.com/lowRISC/opentitan/blob/c8de39a70f38a46c9546ae918798efeb49e03d67/sw/device/tests/aon_timer_irq_test.c#L132-L145

It's not quite right. The condition must always be checked before proceeding. We cannot assume that exiting WFI means we got the event we were waiting for.
This test is also able to get interrupts that break out of WFI but don't touch header_interrupt_received. For example, a debugger issuing a halt will cause an ebreak, which wakes up Ibex to execute instructions in debug mode. If we don't check header_interrupt_received and loop back, the test can continue before the proper time and fail. This would make debugging issues really annoying. ;)
So, instead, it should probably look something like this:
static void atomic_wait_for_interrupt(void) {
  do {
    // Because this next check's result is to determine whether to go to WFI,
    // the check and WFI instruction must be atomic.
    irq_global_ctrl(false);
    if (!header_interrupt_received) {
      wait_for_interrupt();
    }
    irq_global_ctrl(true);
  // But don't proceed unless we actually have received a command!
  } while (!header_interrupt_received);
}