Was curious about the mathematical justification for the uniform random rotations so I looked at the justification/reference here: But that reference only tells me how to sample uniformly from the sphere; nothing about rotations. According to Our implementation is actually wrong. The angle of axis angle should not be uniformly distributed. Proposal: UniformlyRandomQuaternion should just sample from the unit sphere (4D), via four Gaussian random variables normalized. UniformlyRandomAxisAngle (and others) should use the UniformlyRandomQuaternion. Cc @hongkai-dai. I added a simple ops file to update the manifest by using xenial stemcell and sounds it works as well.
Explains what Mandatory Access Control (MAC) is and how this mechanism can be used to secure a FreeBSD system. Chapter 17, Security Event Auditing Describes what FreeBSD Event Auditing is, how it can be installed, configured, and how audit trails can be inspected or monitored.
$ cat stemcell.yml. Observed behavior Device info is not listed on the nodes after peer detach. And when tried to add the device it is throwing below error. root@gluster-kube2-0 /# glustercli device add e0275243-b512-4df0-8588-075ebd65e3a5 /dev/vdc Device add failed Response headers: X-Gluster-Cluster-Id: f1291712-add8-4741-936e-b3234d54cd5c X-Gluster-Peer-Id: e0275243-b512-4df0-8588-075ebd65e3a5 X-Request-Id: 58a0c57e-cc13-4f3b-bac1-e3ddc0dad45e Response body: transaction to prepare device failed time=“2018-12-27 09:85” level=error msg=“Failed to create physical volume” device=/dev/vdc error=“exit status 5; Can’t initialize physical volume ”/dev/vdc “ of volume group 'gluster-dev-vdc ” without -ff n /dev/vdc: physical volume not initialized. N' reqid=58a0c57e-cc13-4f3b-bac1-e3ddc0dad45e source=“transaction.go:29:device.txnPrepareDevice” txnid=72ceb68c-2e8b-43e2-a8f0-1346a290083f time=“2018-12-27 09:20” level=error msg=“Step failed on node.” error=“exit status 5; Can’t initialize physical volume ”/dev/vdc “ of volume group 'gluster-dev-vdc ” without -ff n /dev/vdc: physical volume not initialized. The “Keyword Interactions” section of the core spec currently reads as: Keyword behavior MAY be defined in terms of the annotation results of subschemas (Section 4.3.3) and/or adjacent keywords. Such keywords MUST NOT result in a circular dependency.
Keywords MAY modify their behavior based on the presence or absence of another keyword in the same schema object (Section 4.3). It seems to me that the meaning of this paragraph is that:. Keyword behavior can only be recursively defined in terms of:. The annotation results of subschemas. The annotation results of other keywords that share the same parent schema object. The presence or absence of another keyword in the same schema object.
This definition seems to have a number of problems, on my reading:. It leaves unclear whether this section is laying out all a keyword may do, or if it is merely stating what a keyword may not do.
Keywords may be defined in terms of the validation results of subschemas and adjacent keywords. The current definition makes no references to validation at all. $ref and $recursiveRef are not supported on this definition. The referent of these keywords may not be in the same schema object, but their outcomes are entirely defined in terms of their referents. Furthermore, $recursiveAnchor affects the behavior of referring schema objects. As an aside, I don’t think the exclusion of circular dependency is required. A circular definition is no definition at all.
I’m happy to open a PR to fix this section! But I would like clarification on the following questions:.
Are we, in “Keyword Interactions”, trying to explicitly lay out everything a keyword may do, or are we merely just enumerating what a keyword shouldn’t do?. Is the omission of any reference to validation intentional?. What does “the same schema object” mean?
How does it relate to external references? Happy to help! But I don’t want to make assumptions about the three preceding questions. When you go to Shops Market or Shops Seasonal Shop to buy an equipment piece that you have not previously owned, the purchase is successful (the item appears in your Inventory immediately) but the bought item does not disappear from the Shop until you sync. I.e., it looks as if you haven’t been able to buy the item, which will be confusing and frustrating to anyone attempting to use the Shop for the current Grand Gala gear. Note that if you are buying an item because you previously owned it and lost it due to death, then it DOES disappear from the Market as soon as you buy it, so this bug only happens if the item was not already stored in your account with a false value. The bug does not occur if you buy a new item from your Rewards column.
Thanks to cTheDragons for reporting this. Do you want to request a feature or report a bug? Feature What is the current behavior? With old key generation, algorithm user can just construct key by concatenating orgid and username, and what most importantly dashboard was able to make such an assumption when querying by username. With new hashing algorithms, dashboard can’t query by username anymore.
What is the expected behavior? We need to modify Key API to allow querying by username, which will ensure that the right hashing algorithm is used.
Which versions of Tyk affected by this issue? Did this work in previous versions of Tyk? I’m getting following crash sometimes, The scenario is that when image or video is captured then user is taken to next screen and in onStop method i stop the camera. Sometimes if i perform capturing or recording too frequently by goind back and forth from between camera and next screen. Then app crashes and gives following logs: Fatal Exception: java.lang.RuntimeException: Camera is being used after Camera.release was called at android.hardware.Camera.nativegetParameters(Camera.java) at android.hardware.Camera.getParameters(Camera.java:1952) at com.wonderkiln.camerakit.Camera1$6.onPreviewFrame(Camera1.java:449) at android.hardware.Camera$EventHandler.handleMessage(Camera.java:1133) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:154) at android.os.HandlerThread.run(HandlerThread.java:61). Description of Problem, Request, or Question I’m currently using conan-boost with boostpython to generate bindings for a C project using cmake. System-wide, I have Python 3.7 installed.
However, I would like to use a pyenv version of Python, namely 3.6.7. Short of forking the repo and customizing the jamfile manually, is there any other way to set the Python path through e.g. Environment/cmake variables? I’m not opposed to this, but it would be nice not to have to do so. This is issue can be linked with #99 The following code will lead to not compilable transformed code after FFront and FBack processings. Describe the bug The script crafter.sh provides status and statustomcat options.
However, these options are internally supported only by Studio, and not by delivery. This is inconsistent with the start/stop tomcat options which will start/stop the webserver for either studio or delivery. To Reproduce Steps to reproduce the behavior: 1.
Start a crafter delivery instance 2. Execute crafter.sh status, observe there is incomplete success output for uptime, status, and version 3. Execute crafter.sh statustomcat, observe there is incomplete success output for uptime, status, and version Expected behavior When status or statustomcat is run for delivery, the webserver status is titled as “Studio” and it has no output for uptime, status, and version.
When the webserver is not running, output states that Crafter Studio is not running. Screenshots Taken from a running delivery instance: $ /opt/crafter/bin/crafter.sh statustomcat -———————————————————– Crafter Studio status -———————————————————– PID 23123 uptime: Status: Version: Specs Version Crafter 3.0.x OS Linux & MacOS.