Replace DCHECK_NE to avoid errors with gcc 5.3

DCHECK_NE() introduces a dependency to libcef.so. That is a problem with
gcc version 5.3 because of ABI changes. By replacing DCHECK_NE() with an
exception, this can be avoided.

@DarkDeepBlue Since it's already merged, I suggest you leave the PR for now. But please, next time ask for a final review before merging.

@koraa Since the pull request was around for some time I assumed that everyone has already seen it and had no objections. As I already mentioned, it’s mandatory for me to have this changes in master in order to compile inexor using gcc 5.3.
Also, I wouldn’t leave things being the second best solution. What file should I move the exception definition to?

@DarkDeepBlue Well, you pushed a new version this morning ^^
I suppose we could move the exception into engine/engine.hpp. This header is a bit problematic, but I think in this case this would be best.
Btw, I should also mention that I am very glad that we now support the most recent GCC. I am very glad GCC 5.3 is supported now and I just started my package manager.

As a talerted programmer noted a few days ago, the branch was actually updated and I myself witnessed that this very version full of awesomeness and joy was on Github since then.
13-12-2015 20:26:17	+DeepBlue	Good, I updated my gcc 5.3 fix branch. :)

It’s a nice thing that you can upgrade your system now. :)


Expose StyedList contents

This still won't allow direct construction because of the PhnatomData member.

Just to let you know @davidkna: this was included in release 3.5.0 (just published)


@zkwentz

@zkwentz
thank you very much
Originally posted by @piotr-s-brainhub in https://github.com/brainhubeu/react-carousel/issues/549#issuecomment-647193228
I have the same issue; localhost is running, release is wrong;

@codeWebZhang
I close this issue, please write a comment in https://github.com/brainhubeu/react-carousel/issues/549 instead.


Do not create directory if not found

Use type: Directory instead of type: DirectoryOrCreate allows to block running workload on provisioned directories, to avoid the situations when initial storage is unmounted or broken.
docker image containing the fix:
kvaps/local-path-provisioner:v0.0.17-fix-137

fixes https://github.com/rancher/local-path-provisioner/issues/137

Additionally I also added the check for filesystem type:
configmap:

  setup: |
    #!/bin/sh
    path=$1
    dir=$(dirname "${path}")
    fslist='^(ext4|zfs|xfs)$'

    if [ -z "$(awk "\$2 == \"${dir}\" && \$3 ~ \"${fslist}\" {print \"ok\"; exit}" /proc/mounts)" ]; then
      echo "filesystem for "${dir}" is not match ${fslist}:" >&2
      awk "\$2 == \"${dir}\"" /proc/mounts >&2
      exit 1
    fi
    mkdir -m 0777 -p "${path}"

  teardown: |
    #!/bin/sh
    path=$1
    if [ ! -d "${path}" ]; then
      echo "directory "${path}" is not exists" >&2
      exit 1
    fi
    rm -rf "${path}"

The PR itself looks good, but I am not sure why we want to check the fs type?

I am not sure why we want to check the fs type?

This is exactly my case, because I have nodes booted via PXE with ephimeral overlayfs root.
See https://github.com/kvaps/kubefarm
There is a risk that volume might be created directly in the RAM partition and will be lost in the next reboot.
Filesystem type check guarantees that volume will be created on the normal "physical" filesystem.

@kvaps Local path provisioner does offer the ability to set up customized locations for the persistent disk, so built on top of the ram disk should be preventable? Also, even if it's an ext4 filesystem, there is no guarantee it will be persistent since for some OS, certain directories will be cleaned up after reboot.

Setting the different location will not help if whole / (root filesystem) is ephimeral

What's the expected behavior if the whole / is ephemeral? I don't get why checking fs type can help in this case. If there is a mixed deployment, trying to use RAM disk to create volume will result in volume creation failure and there won't be a retry on another node.

Just imagane you have:
/ - ephemeral overlayfs root (backed by tmpfs)
/opt/local-path-provisioner - is not mounted so located on the same ephemeral overlayfs root

let's assume the local-path-provisioner created the directory:
/opt/local-path-provisioner/pvc-xxxxx - still created on the same ephemeral overlayfs root

However pod is started some database and storing some data there.
During the restart we're having completely new root, /opt/local-path-provisioner/pvc-xxxxx - is not existing anymore, all data lost.
type: DirectoryOrCreate is creating new directory under the same path, pod is starting again with no errors. we're having new empty database.

I want to avoid this case. By adding two checks:

replace type: DirectoryOrCreate to type: Directory which will avoid to start pod if desired directory is not found (exactly this PR)

add additional check for the provisioning new volumes, to avoid provisioning volumes on top of ephemeral overlayfs and tmpfs filesystems. (this is not so important if you're having normal root, but it is important if you're having ephemeral rootfs)

type: Directory is a good change (don't understand why it doesn't though). But it's not going to solve the problem that you lost your data in this case.
In this case, that node should be excluded from the config map (https://github.com/rancher/local-path-provisioner#customize-the-configmap) to avoid losing data. Since even the check failed, the provisioner is not going to retry on a different node because the pod is already scheduled.

But it's not going to solve the problem that you lost your data in this case.

At least it will return reilable error, instead of continue to work as if nothing had happened.

In this case, that node should be excluded from the config map

I have all nodes like this

even the check failed, the provisioner is not going to retry on a different node because the pod is already scheduled.

Sure, this is expected behavior. WaitForFirstConsumer allows to create PV on exact node where pod was scheduled.
My check allows to avoid situations when pod was scheduled to the wrong node by human error or if node has unmounted persistent storage for some reason.
This enhance is exact for my case, when nodes has ephimeral root. Unlike type: Directory it doesn't pretend to be merged into upstream.


ScriptTerminated error not returned

After disabling runtime execution the script completes successfully with no error, although I expect ScriptTerminated to be returned. This seems to be happening only when the script has no other commands to execute after runtime execution is disabled. For example, when I try this script, the error is printed as expected (here 'sleep' is a custom callback function that simply does Thread.Sleep, and another thread disables runtime execution after 1 second):
string script = "(()=>{sleep(2000); return new Date();})()";
Output:
Error code: ScriptTerminated
Return value:

But if the script returns a simple string, it completes successfully and no error is returned:
string script = "(()=>{sleep(2000); return \'Hello world!\';})()";
Output:
Error code: NoError
Return value: Hello world!

Is there a way to get a ScriptTerminated error from the script executed in the second example?

If runtime execution is disabled after the script has already finished ("has no other commands to execute", as you say), why would you expect an error?  It indeed completed successfully.  I wouldn't want to be the person that has to debug time-traveling errors... 😝

I guess that depends on whether "return" statement should be considered as a separate command?
In the second example I would expect all execution to stop and "return 'Hello world!'" to never be executed, and an error to be returned instead (similarly to the first example, which has no return value, but has an error).

Stopping runtime execution does depend on hitting designated breakpoints in the bytecode; I don’t remember where this is documented but I know it’s documented somewhere.  It’s probably just that new Date() causes such a breakpoint to be injected while the bare return doesn’t.

Found it:
https://github.com/Microsoft/ChakraCore/wiki/JavaScript-Runtime-(JSRT)-Overview#runtime-resource-usage

Because script termination depends on reaching guard points inserted into the code, a script may not terminate at the exact moment, but will do so very shortly afterwards.

“Shortly afterwards” in your second case just happens to be “after it’s already completed”.

Thanks! Yeah I've seen this page before and I actually pass JsRuntimeAttributeAllowScriptInterrupt, but looks like it's not enough to cover this scenario. I guess this behavior does align with the documentation... Maybe there is really no reason for the runtime to treat a return specially. In the worst case I could probably add some meaningless operation right before the return, which would guarantee a breakpoint :)

AllowScriptInterrupt from what I understand just adds a few extra guards in loops so that you don’t get stuck in an infinite loop.  You wouldn’t want one after every instruction or your code would run insanely slowly.

@dennis-yemelyanov curious is there any reason you want termination to happen at a specific line? The common use case for resource management that the host shuts things down once a certain CPU/time threshold is crossed, in which case you don't really care which specific line of code termination happens.

Thanks @liminzhu. In my case termination can be user-initiated, so if some command takes longer than expected and the user decides to cancel, I thought it would be nice to stop right after that command. But now I understand why it might not be possible without slowing the script down, and I think it makes sense.

Thanks for sharing!

Seems like the issue is resolved so I'm closing it, but feel free to re-open if you have any other issue with this.


Add needs formula

Add NEEDS and NEEDS_ALL formula for evaluating mergeability
Change-type: minor
Signed-off-by: Stathis Moraitidis<EMAIL_ADDRESS>

[ ] after closing update the tutorial accordingly

@Hades32 I pushed a commit with a new filter callback. There is something I might have misunderstood though or we didn't specify. Is the new optional function parameter, supposed to work as a filter function or should it be part of the validation? (or do we need two separate ones).
Let me elaborate. When we  say, for instance NEEDS(contract, "node-module", c => c.data.architecture === "x86_64"), do we mean:
a) Check if a non-error contract has been produced for a node-module type that has an architecture of x86_64. If no, it means it's still processing, so it's pending.
b) Find a non-error backflow contract with a node-module, and check whether that has an architecture of x86_64. If no, it means it failed, therefore it's never.
We had talked about the architecture/platform case, where users will have to put multiple NEEDS to meet different platforms. So I implemented this as a) above. But I can also see the case for a usage like NEEDS(contract, "test-run", c => c.data.success === true), where the user wants to validate a specific key.

@Hades32 on a separate issue, I've noticed that the static-eval library we use to evaluate formulas, might have a small bug. It took me ages to figure out what's happening, but I raised is here. I doubt it will get a response soon, but let's see. Basically, even in existing code, I see that a test does:
FILTER(
    contract.links["has attached element"],
    function (c) { return c && (c.type ===<EMAIL_ADDRESS>|| c.type === "whisper@1.0.0"); }
),

(Depending on the case) I don't think the c && should be needed, and probably it's there because of the bug. This might lead to users writing NEEDS formulas that fail without it, and have to debug. When I switched to another lib, safe-eval, it was evaluating correctly without the need of c &&.

@stathismor about static-eval, yeah that one really sucks, it doesn't even have arrow functions...
I did look at safe-eval before and thought it would require an additional node process and discarded it, but that doesn't seem to be the case (anymore?), so I'd highly advocate for a PR to replace our eval library!
About the semantics of the callback:
You definitely made the right choice. The only reason I could come up with to want option (2) is the success check that you outlined. But I'd argue that is something is success == false then it should be an error contract.
Maybe someone will come up with another use-case, but then we'll implement it as needed

@Hades32 I've resolved some conflicts, had to move the enum to index.ts and restructured tests under their own function (in retrospect, I should probably have done a separate commit). Opening this as officially ready to review.
While I'm at it, I will look at the safe-eval alternative and make a PR if it works.


Update deploy-on-aks.md

Add the az region command: az account list-locations -o table

@suresh-kandoth : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ShannonLeavitt : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@suresh-kandoth Thanks for this suggestion!


Blackout button doesn't blackout anymore

Don't know when this happened, but clicking on the blackout button, doesn't produce an actual blackout.
Instead, channels are "frozen" on the current state (e.g. dimmer channels, RGB channels)
You can make changes to channels (e.g. changing scene, simple desk, etc) and no change is sent on the output.
When the blackout button is unpressed, the updated channel values are sent to the output.
This is quite a big regression and needs to be fixed on 4.10.0
[EDIT] Luckily it's just a monitor issue. The actual blackout works on real fixtures.
This has been caused by my changes to reduce the number of universeWritten notifications.
I'm on it...

Fixed by 9560420e0c9b56e917c549de34b8546f6432dd1e


Customize to enable/disable the warnings

What do you mean exactly?

Some times it throws errors when I save the file and it has some syntax errors and tries to format it, there are some formatters that has an option to show warnings to avoid this


Add feature to undelegate from stake pool

It seems that there’s not yet a feature available to undelegate from a stake pool. Please add or if feature exists add documentation.

The feature have been added and merged. It will be part of the next release.


Increased iDRAC is-ready retries to 96

Increased iDRAC is-ready retries to 96, which is required for the latest firmware.

Looks good.  this is what I manually tested.


⚠ ClamAV has degraded performance

In ca9c7b0, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 435 ms

Resolved: ClamAV performance has improved in af3dc83.


NullPointerException on UI thread when an empty LazyColumn is displayed

Reproduce:
Click on the disabled OutlinedTextField created with the below code
OS: MacOS
Version:
    kotlin("jvm") version "1.5.30"
    id("org.jetbrains.compose") version "1.0.0-alpha4-build344"

My code:
@Composable
fun platformUrlInput(viewModel: ManagePageViewModel) {
    val platformUrlEnabled by viewModel.platformUrlEnabled.collectAsState()
    val url by viewModel.meetingUrl.collectAsState()
    Row {
        Switch(checked = platformUrlEnabled, onCheckedChange = { }, enabled = false)
        Text("URL:")
        OutlinedTextField(
            shape = RoundedCornerShape(50),
            colors = TextFieldDefaults.outlinedTextFieldColors(
                focusedBorderColor = R.color.primary,
                unfocusedBorderColor = R.color.grey
            ),
            value = url,
            onValueChange = viewModel::onUrlChange,
            keyboardOptions = KeyboardOptions(keyboardType = KeyboardType.Ascii),
            modifier = Modifier.fillMaxWidth(),
            enabled = platformUrlEnabled
        )
    }
}

Stack trace:
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
	at androidx.compose.ui.platform.SkiaLayer.isInLayer-k-4lQ0M(SkiaLayer.desktop.kt:128)
	at androidx.compose.ui.node.LayoutNodeWrapper.withinLayerBounds-3MmeM6k(LayoutNodeWrapper.kt:639)
	at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.hitTest-9KIMszo(DelegatingLayoutNodeWrapper.kt:77)
	at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.hitTest-9KIMszo(DelegatingLayoutNodeWrapper.kt:79)
	at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.hitTest-9KIMszo(DelegatingLayoutNodeWrapper.kt:79)
	at androidx.compose.ui.node.LayoutNode.hitTest-9KIMszo$ui(LayoutNode.kt:846)
	at androidx.compose.ui.node.InnerPlaceable.hitTest-9KIMszo(InnerPlaceable.kt:146)
	at androidx.compose.ui.node.LayoutNode.hitTest-9KIMszo$ui(LayoutNode.kt:846)
	at androidx.compose.ui.node.InnerPlaceable.hitTest-9KIMszo(InnerPlaceable.kt:146)
	at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.hitTest-9KIMszo(DelegatingLayoutNodeWrapper.kt:79)
	at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.hitTest-9KIMszo(DelegatingLayoutNodeWrapper.kt:79)
	at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.hitTest-9KIMszo(DelegatingLayoutNodeWrapper.kt:79)
	at androidx.compose.ui.node.DelegatingLayoutNodeWrapper.hitTest-9KIMszo(DelegatingLayoutNodeWrapper.kt:79)
	at androidx.compose.ui.node.LayoutNode.hitTest-9KIMszo$ui(LayoutNode.kt:846)
	at androidx.compose.ui.input.pointer.PointerInputEventProcessor.process-BIzXfog(PointerInputEventProcessor.kt:66)
	at androidx.compose.ui.input.pointer.PointerInputEventProcessor.process-BIzXfog$default(PointerInputEventProcessor.kt:50)
	at androidx.compose.ui.platform.DesktopOwner.processPointerInput-8iAsVTc$ui(DesktopOwner.desktop.kt:326)
	at androidx.compose.ui.platform.DesktopOwners.onMouseMoved(DesktopOwners.desktop.kt:193)
	at androidx.compose.ui.awt.ComposeLayer$initCanvas$3$mouseMoved$1.invoke(ComposeLayer.desktop.kt:211)
	at androidx.compose.ui.awt.ComposeLayer$initCanvas$3$mouseMoved$1.invoke(ComposeLayer.desktop.kt:210)
	at androidx.compose.ui.awt.AWTDebounceEventQueue$job$1.invokeSuspend(AWTDebounceEventQueue.desktop.kt:59)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:316)
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:391)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
	at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

I think outlineCache.outline!! is the problem.
https://github.com/androidx/androidx/blob/a1d3a68c23eb2c1e48543ee6ef4b21dccc5f3eb2/compose/ui/ui/src/desktopMain/kotlin/androidx/compose/ui/platform/SkiaLayer.desktop.kt#L128

Could you try to see if you have the same issue on build348? Build344 behaves weird and on 348 I don't have any issues in similar code.

Hi, thank you for your suggesiton. However, I am facing the same issue on build348.
Also, I found that it was not "clicking" that caused the crash, but it crashed as soon as I moved mouse pointer while the view is being displayed.

I just found that the OutlinedTextField was not the cause. I commented it out but still crashes

I found that LazyColumn was the cause of the crash.
Maybe because the mydata.value's length is 0?
@Composable
fun blockListTab(viewModel: ManagePageViewModel) {
    val myData = viewModel.blockList.collectAsState()
//    val myData = listOf("Hello,", "world!", "Youtube", "Facebook", "줌", "인스타", "으악")
    LazyColumn {
        items(myData.value) { item ->
            // BlockRow(item, viewModel)
        }
    }
}

I am pretty sure that empty myData.value caused the problem!
When I changed
private val _blockList = MutableStateFlow(listOf<BlockItem>())

to
private val _blockList = MutableStateFlow(listOf<BlockItem>(BlockItem(0, 0, "youtube", true)))

In my viewmodel,
The program did not crash anymore~
Should this phenomenon be considered as a bug or user(programmer)'s fault?

could you share a whole reproducer, please?

@akurasov I created a repo for PoC!
https://github.com/KYHSGeekCode/JB-Bug-Poc/

New build 362, facing the same issue. Minimal reproducer
As soon as I move my mouse into the window, the app crashes with
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
	at androidx.compose.ui.platform.SkiaLayer.isInLayer-k-4lQ0M

This does not happen up until build 331.

I'm seeing this issue in 366.

Should this phenomenon be considered as a bug or user(programmer)'s fault?

I'd definitely call this a bug. We should be able to have an empty LazyColumn.

I believe workaround exists here. So shouldn't be critical.

This crash should be fixed in 1.0.0-beta5. Let us know, if it is still exist on your side.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


[Docs] Add health check URL to API docs

Add the health check endpoint to the API reference and maybe the README.md.
The URL is /_ah/health, it takes no parameters and will respond with HTTP 200 and the text "OK", if the Rendertron server is healthy.

Hi @AVGP, I am new to open source, and am looking to learn and contribute. This issue seems a good opportunity for me to do that. If you can guide me, maybe I can solve it.

Hi @AVGP, I am new to open source, and am looking to learn and contribute. This issue seems a good opportunity for me to do that. If you can guide me, maybe I can solve it.

That's awesome news, @ShrillShrestha!
I'm very happy to help :) A first good step is to check out this guide on how to contribute on Github.
You can actually do most of the necessary steps right from your browser:

Click "Fork" on the top right corner to get your own fork of this project.
In your own fork in your browser, navigate to the docs/api-reference.md file and click on the edit button (pen symbol).
Make the edits (add a new section, like the other existing sections).
Save the change and make sure it says "Create new branch".
Go to the main repository (this one here), click "Pull requests" and it should suggest to open a pull request from the new branch you created when saving the edit.

Let me know if you have further questions!

That's awesome news, @ShrillShrestha!
I'm very happy to help :) A first good step is to check out this guide on how to contribute on Github.
You can actually do most of the necessary steps right from your browser:

Click "Fork" on the top right corner to get your own fork of this project.
In your own fork in your browser, navigate to the docs/api-reference.md file and click on the edit button (pen symbol).
Make the edits (add a new section, like the other existing sections).
Save the change and make sure it says "Create new branch".
Go to the main repository (this one here), click "Pull requests" and it should suggest to open a pull request from the new branch you created when saving the edit.

Let me know if you have further questions!

Sure @AVGP, I will try to work on it. If I have any questions, I will let you know.

Sure @AVGP, I will try to work on it. If I have any questions, I will let you know.

@AVGP, so the files that to be changed is only api-reference.md?

@AVGP, so the files that to be changed is only api-reference.md?

Thank you, @ShrillShrestha - your change has now been merged and you're now a Rendertron contributor! 🎉

Thank you, @ShrillShrestha - your change has now been merged and you're now a Rendertron contributor! 🎉

Thanks, @AVGP for helping me out. I am happy to contribute. :)

Thanks, @AVGP for helping me out. I am happy to contribute. :)


Removed the team from the General Signing and update the project to support iOS 9.0

Description

Motivation and Context

How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Without the CLA, I'm unable to accept changes.  Sorry.


New package: 3Dflowsrl.3DFZephyrFree version 7.529

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?
Resolve #156098

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

Verify:

https://github.com/microsoft/winget-pkgs/issues/107639


Question regarding VPC and EFS

As far as I understand the architecture, it's only necessary to have a VPC with private subnet and S3 Gateway Endpoint because the solution is using EFS to support larger files that would exceed the Lambda runtime /tmp storage of 512MB?
I could also directly copy the files from S3 to the Lambda /tmp folder as long as my use case doesn't need more than 512MB of temp storage that the Lambda runtime provides, correct?
Thank you!

Lambda recently added support for up to 10GB ephemeral storage!
That being the case there are some limitations to consider regarding Lambda execution environments. Lambda's in the same execution environment share the /tmp folder. In this case that could mean that several Lambda's running at the same/similar time could fill up the /tmp space and cause new Lambda functions to fail to execute.
With that in mind even with the new announcement this solution will continue using EFS for file storage.


shareProcessNamespace hot patch

Hot fix from
https://github.com/runatlantis/helm-charts/pull/209
the value fromshareProcessNamespace was pulling from the wrong location. This is a hot patch for it.

Hi @nitrocode we missed the location of the process namespace. It pulled from the root of the values when it should have been under stateful set. since it was making the change in that template. Sorry for the miss.


Handle remoting exceptions, and allow empty array results in vfr

Resolves #32 and #34 (see those issues for detailed descriptions):
Summary:

When an empty array is returned intentionally by a remote action, resolve, instead of rejecting.
When a remote action throws an exception, reject with useful information, instead of resolving

Couple of other points, I haven't rebuilt this using grunt min (which I think is your build process?), as https://github.com/noeticpenguin/ngForce/commit/e2bcc141d8ec086c1a0257f3a3b01bee3fd700ee broke the build (standardOpts is declared inside an object literal, as a var, which explodes ngAnnotate). Can do another PR to fix that as well if you like? But there were a few approaches to fix that which i could see, and I didn't want to presume to take either - you could either:

go back to declaring var standardOpts in the provider, and instead of returning an object with $get and setStandardOptions, put the methods on this (following the pattern described here: https://docs.angularjs.org/guide/providers#provider-recipe)
change it to be a property of the the returned object literal, and update the standardOpts references in $get and setStandardOptions to be this.standardOpts

James,
Regarding your other points,
I would love a PR to fix this. I apologize for breaking the build. I would love if you would submit a PR that followed the pattern you linked to in the provider recipe.

James, I would still love the other PR to fix the provider.

Hey Kevin, good to hear from you too!
Looks like you landed on my issue with the explanation of nullOk handling, but to confirm, yep, should be 100% backwards compatible :+1:
Will try and get a PR in for the provider fix today-ish


Python 3.4.7 not available

Hey, I know this is kind of a small thing, but I need 3.4.7 specifically.  I've loved using asdf for python and I'd like to keep using it.  It looks like 3.4.7 is available in pyenv: https://github.com/pyenv/pyenv/releases/tag/v1.1.4  I've tried running asdf plugin-update --all but that didn't help.  Is there something else I should do to get new Python versions?
And is there some way to automatically get new versions as they become available?
Eric

Hi @ELind77, thank you for reporting.
I am aware of this issue and have been too lazy to fix it :sweat:
The issue is that I am not automatically updating pyenv, so only
versions available when first using asdf-python are available.
A temporary workaround is simply to run
cd ~/.asdf/plugins/python/pyenv/ && git pul

The fix is to update pyenv if it was not updated for a while.
If you would like to send a PR for it I would be very pleased to merge it.
Thank you.

I've opened a small PR that will do a pull on list-all: https://github.com/tuvistavie/asdf-python/pull/34


gobi_loader fails on compressed firmwares

Describe the bug
Even with CONFIG_FW_LOADER_COMPRESS=y some firmwares cannot be loaded when compressed.
Steps To Reproduce
{
services.udev.packages = [ pkgs.gobi_loader ];
hardware.firmware = [
  (pkgs.runCommandNoCC "firmware-gobi-Orange" {} ''
    mkdir -p $out/lib/firmware
    # Copy a firmware obtained from a Windows installation
    # See https://www.thinkwiki.org/wiki/Qualcomm_Gobi_2000
    cp -r ${firmware/gobi} $out/lib/firmware/gobi
  '')
];
}

$ ls /run/current-system/firmware/gobi/
amss.mbn.xz  apps.mbn.xz  UQCN.mbn.xz

$ sudo /nix/store/7jv86lpdgi1n625q3sdfvnw8qpqx4wnd-gobi_loader-0.7/lib/udev/gobi_loader -2000 /dev/ttyUSB0 /run/current-system/firmware/gobi
Failed to open firmware: : No such file or directory
usage: /nix/store/7jv86lpdgi1n625q3sdfvnw8qpqx4wnd-gobi_loader-0.7/lib/udev/gobi_loader [-2000] serial_device firmware_dir

Expected behavior
gobi_loader should work as well as when /run/current-system/firmware/gobi is replaced with a directory containing uncompressed firmwares.
Notify maintainers

@alyssais as author of https://github.com/NixOS/nixpkgs/pull/172820
@0x4A6F as author of c97f57ef9623
@flokli as author of c7bf1e2a01ae

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.61, NixOS, 22.11 (Raccoon), 22.11-patch-de4e3b3`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.10.3`
 - nixpkgs: `/nix/store/gxyn8m9xsbl6w1904ig697x2d7w0hhgz-source`

Workaround by abusing compressFirmwareXz's logic with symbolic links:
{
services.udev.packages = [ pkgs.gobi_loader ];
hardware.firmware = [
  (pkgs.runCommandNoCC "firmware-gobi-Orange" {} ''
    mkdir -p $out/lib/firmware
    ln -s ${../../nixos/firmware/gobi} $out/gobi.xz
    ln -s $out/gobi $out/lib/firmware/gobi
  '')
];
}


Add new konnect cta to docs

Description
What did you change and why?
Related Jira ticket
Add a new CTA for driving people to Konnect, checking whether customers dismiss it or follow it.
This is only rendered in:

app/_src/gateway/index.md
app/_src/gateway/install/docker/index.md

It sets a cookie (konnect-cta-card) to keep track of whether the overlay was dismissed or clicked, so we don't show it to customers again
Testing instructions
Netlify link:
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

@fabianrbz thanks for preview to see how this behaves. Do we have another option to locate besides the left menu?
On both pages, when I scroll to the bottom of the page, the CTA is still obscured because the left menus are very long.

@acgoldsmith we can, I was following the example.
we could place it at the top of the menu, do you think that would work?

@fabianrbz thanks for suggestions, as we discussed, let's try to add as overlay in the bottom left of the screen... I think that location is good for distance from CTA button in top nav, and preferable to the other options you've outlined.

@acgoldsmith I added the overlay but had to center the modal, otherwise it looked too weird. Is that ok?

@acgoldsmith I added the overlay but had to center the modal, otherwise it looked too weird. Is that ok?

Let's move the overlay to bottom right corner so it's not obscuring the page content, please and thanks

@fabianrbz , let's make some additional tweaks, please:
remove the grey from page behind overlay
narrow down the size of the overlay window so it's about the same width as the left nav
when I click the close X there's a second step I have to click for "skip to content" - is it possible to remove this?

remove the grey from page behind overlay

Checking the preview today I think what we had yesterday with the wider CTA + grey background was more inline with what's expected (very obvious, but easy to dismiss)

Okay, @fabianrbz let's go back to the more obvious version as Michael suggests and call it good. Thanks


Home - A Unique Horror Adventure [PCSE00533]

Game summary

Game name: Home - A Unique Horror Adventure
Game serial: PCSE00533
Game version: 01.00

Vita3K summary

Version: v0.1
Build number: 1016-52a6cd3
Commit hash: https://github.com/vita3k/vita3k/commit/52a6cd3

Test environment summary

Tested by: HorrorTroll
OS: Windows 10
CPU: Intel Core i5-4200H
GPU: Nvidia Geforce GTX 950M
RAM: 6 GB DDR3

Issues
Crashes because unhandled relocation code on PSNExt.suprx
Screenshots

Log
vita3k.log

Vita3K summary

Version: v0.1
Build number: 1063
Commit hash: https://github.com/vita3k/vita3k/commit/050c22b3

Test environment summary

Tested by: Zangetsu38
OS: Windows 10
CPU: AMD Ryzen 2700X
GPU: NVIDIA GTX 1080 Ti
RAM: 16 GB DDR4 3600 mhz

Issues

Crash on load module PSNExt.suprx inside game folder wiith lot "Unhandled relocation code"

Log
vita3k.log

Vita3K v0.1.5 2703-6929311d
as soon as you go down the tunnel nothing but a red screen
vita3k.log

ingame+ now ??

as of https://github.com/Vita3K/Vita3K/commit/22595c5060298e246bbef02eb70d32752259ee09, the game is playable with no audio issues.
Screenshots

Log
vita3k.log
Recommended labels
Playable


Captured image quality was too bad. how to capture the same quality as we capture from camera application.

I got the picture but it was yellowish. how to capture the same quality as we capture from camera application.
I used the following code.
function success(imgurl) {
  console.log("Imgurl = " + imgurl);
  //here I added my function to upload the saved pictures
  //on my internet server using file-tranfer plugin
}

function onFail(message) {
    alert('Failed because: ' + message);
}

function CaptureBCK() {
    var options = {
    name: "Image", //image suffix
    dirName: "CameraPictureBackground", //foldername
    orientation: "portrait", //or landscape
    type: "back" //or front
    };

    window.plugins.CameraPictureBackground.takePicture(success, onFail, options);
}

    <button onclick="CaptureBCK();">Capture Photo</button> <br>

I am also facing the same issue. Very poor quality and low resolution image.

I recommend entering native plugin code and doing our work, not waiting for the developer to do everything for us


Pylint not working in virtual Environment in VS code.

Environment data

VS Code version: 1.38.1
Extension version (available under the Extensions sidebar):Python 3.7.4 64 bit
OS and version:Windows 10 Pro
Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.4 64 bit
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Relevant/affected Python packages and their versions: Python Extension
-Pylint Version: 2.4.1

Expected behavior
In my global environment pylint works seamlessly and displays all kind of error (indentation,syntax etc)
Actual behavior
It wont even detect syntax errors or any errors which generally show up in the problems tab in VS code.
Steps to reproduce:

Create a venv
2.Install pylint in the venv using pip
3.Create a workspace for that venv in vs code

My Settings

When running in a venv

Running in global environment

Hi @IamCristiano7.  Thanks for letting us know about this.  We're looking into it.

Hi @IamCristiano7. Thanks for letting us know about this. We're looking into it.

Hi any updates ?

Sorry for the delay, @IamCristiano7.  What happens if you remove the "python.venvPath" and "python.linting.pylintPath" from your settings?  What about "python.linting.pylintUseMinimalCheckers"?

Sorry for the delay, @IamCristiano7. What happens if you remove the "python.venvPath" and "python.linting.pylintPath" from your settings? What about "python.linting.pylintUseMinimalCheckers"?

It doesn't make any difference but sometimes pylint runs fine on its own and some times it doesn't. Does pylint have full compatibility issues with Python 3.7+ ?
Also i have another workspace file(VS Code) on my Desktop with separate venv and running python 3.6.8 and pylint runs fine there with the same settings. What could be the issue here?

It could be the version of pylint you are using.  Compare the version used in the two venvs.  If the semi-broken one is older then use pip (under that venv) to update it and see if that sorts it out.
Also, what is in your "Python" output panel?  You should see the command the extension executes to run pylint, as well as the output.
Finally, make sure you have "python.linting.enabled": true, in your settings.json.

It could be the version of pylint you are using. Compare the version used in the two venvs. If the semi-broken one is older then use pip (under that venv) to update it and see if that sorts it out.
Also, what is in your "Python" output panel? You should see the command the extension executes to run pylint, as well as the output.
Finally, make sure you have "python.linting.enabled": true, in your settings.json.

The pylint version is same for both and "python.linting.enabled": true is already there in my settings. Not sure about the output window ... it doesn't display anything

@IamCristiano7, I'm guessing this is still a problem.

@IamCristiano7, I'm guessing this is still a problem.

No worries I fixed it. Things run into issue when the the path is too long.

Ah, thanks for letting us know.  I'm a little surprised about that.  Your paths didn't seem too bad.  How long is "too long"?  It may still be worth looking into.

Ah, thanks for letting us know. I'm a little surprised about that. Your paths didn't seem too bad. How long is "too long"? It may still be worth looking into.

Hi Sorry for taking this long to reply
As you can see my python installation (Venv) directory is inside multiple folders and my guess is sometimes vscode failed to Pylint in that directory.

No worries.  The only place that we run into problems with long paths is when the commandline we try to run in the terminal is too long for the terminal.  This is a known issue in VS Code itself (and sometimes just in the relevant shell itself).  I mostly wanted to see how long the command was that was causing the problem.  The extension prints the command out in the "Python" output panel.
I'm going to close this issue, as it sounds like the known problem.  However, if you think it is something else then we can investigate further.  Thanks!


Release schedule and other questions

When do you plan to release to pypi next (or at least make a release tag)?
Will django-bmemcached officially support Django 1.9 soon?
Are there any known problems or bugs that I can help with right now (I see issue #1 is 4 years old)?

@orokusaki Hey, I just released a new version of it with #8 I am not using django this much these days so I barely touch this, maybe you could create a tox to test with a django and python matrix to check all versions. Maybe 1.9 is already supported and I don't know :D

For now have created https://github.com/jaysonsantos/django-bmemcached/tree/django1.9 to check how it will behave with django 1.9

By just running the tests it works, can you check with your django 1.9 project?


Conversation knowledge and puzzles

PR for #220

Coverage decreased (-6.3%) to 76.245% when pulling 7e9e381781bde0d6f60cd1162d31b1b878b1dd73 on 220 into 37c721404cd458342da4d79e9cc8a69d59e81a6b on master.


Implement collection of spells

All spells should be refactored into a JavaScript object which contains properties such as:

spell casting time : How long does this spell take to cast?
Technical Points Consumption : How much of the Character's TP does this attack consume?
Damage dealt: How much damage will this attack do?

Implemented by commit 80587dd6910067566d032236a2b097c6010f7b77.


Finalize repo QA compliance

As part of the TM issue https://github.com/api3dao/tasks/issues/849 for QA, some requirements need to be addressed:
Repo setup requirements as per new_repo_creation_checklist.md:

[x] Write a short description for the repository in the description field
[x] Link to some relevant page if applicable (e.g. api3 docs, npm package link, ...)
[ ] Add standard configuration files (e.g. in this case eslint?) as per standard requirements and other repositories.
[ ] Enhance the README as needed to accurately describe the specific role of this repo
[ ] Install Renovate in the repository, following the guidelines outlined in dependencyManagementStrategy.md.
[ ] Create a renovate.json configuration file in the root of the repository to manage dependencies effectively, as per our dependency management strategy.
[ ] Set up Renovate for automated security vulnerability scanning to detect vulnerabilities in the codebase.

Package setup requirements as per new_package_creation_checklist.md:

[x] Edit the README.md as needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.

@andreogle - I don't have sufficient permissions- would you be able to install the Renovate app by going to Settings, then GitHub Apps at the bottom under Integrations?

Done 👍🏻

Thank you!


Quick fix

Updates workflows so that solution links to this repo and not template one.

@all-contributors please add @glibesyck for code


Fix json file.

Description
Prod json file was incorrect making the backend crash when reading it and preventing the tasks from updating the flutter dashboard.
Related Issues
https://github.com/flutter/flutter/issues/69818
Tests
N/A tests are already in place
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I signed the CLA.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I read the Tree Hygiene wiki page, which explains my responsibilities.
[X] I updated/added relevant documentation (doc comments with ///).
[X] All existing and new tests are passing.
[X] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[X] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

It has been fixed by: https://github.com/flutter/flutter/pull/69828


Clang format.

Any idea why the tests didn't fail?

I'm going to investigate that too, yes. It's bugging me.
On Tue, Dec 1, 2015 at 1:49 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

Any idea why the tests didn't fail?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/4225#issuecomment-161106376.


Inputs do not zero out when used with New Input System

Environment

Code source: VRTK Github
Code version: July 23, 2021 (a1b6108df1233816bece20cd759e66c7210a73f2)
Platform version: Windows 10 x64, Unity 2020.3.18. Valve Index
3rd party dependencies:  SteamVR plugin 2.7.3 (sdk 1.14.15)

Steps to reproduce

Set up Tilia with Unity's New Input system as per this issue.
Add Tilia.SDK.SteamVR.Unity and SteamVR package from Unity Asset Store
Setup SteamVR default inputs per package instructions
Replace UnityXRPluginFramework with CameraRigs.SteamVR in the farm scene
Update Left/right controller references under Generic Actions and Locomotors to use SteamVR default input mappings accordingly
Set locomotion to any teleport, teleport pointers to axis control
Teleport around with both controllers

Expected behavior
Teleport pointer appears when thumbstick is off center, disappears when thumbstick is released to neutral.
Current behavior
Teleport pointer appears, but very often will fail to disappear as if the axis 2D coordinates were not zero. This is also true to other 1D axis actions like grabbing (index controller) and trigger axis.
I believe this is related to providing a deadzone value for float as per this fix in Tilia.Input.UnityInputSystem.
Not sure if it belongs there since it only occurs when using Tilia.SDK.SteamVR.Unity

Also, the existing float deadzone fix needs updating too i think
https://github.com/ExtendRealityLtd/Tilia.Input.UnityInputSystem/blob/6e7c7de31c7669c4c4b9df9ea2070d33e9d491f7/Runtime/SharedResources/Scripts/Transformation/Conversion/CallbackContextToFloat.cs#L35
return value >= DeadZoneValue ? value : 0f; only matters if the float value is a positive value.
If the value is negative but not 0, then it will fail to return any value at all.
the DeadZoneValue for now can be a positive and negative bound instead of having a separate deadzone for positive and negative approaches to zero.
so:
return Math.Abs(value) >= Math.Abs(DeadZoneValue) ? value : 0f;
This should assure the value is always checked against the positive version of the value against the positive version of the deadzone, but the actual value even if negative will still be returned.

I can recreate in the editor with the Quest acting as an Oculus Rift PC

It seems that in fact the Unity Input System has its own built in mechanism for handling axis deadzones using the Processors.

I'll look to just use that instead of adding any custom stuff, that makes more sense I think

I can recreate in the editor with the Quest acting as an Oculus Rift PC

I cannot recreate at all in the unity editor, works fine every time for me. but built for quest i can recreate it.

Ok I think I know the issue.
The Vector2 Context callback (and the float one as well) have the context to process set to Performed
This should mean that when the input context is performed then the value is passed to the zinnia action.
But it seems that the input context doesn't register as performed on the quest when you quickly let go of the control (e.g. release the thumbstick for it to snap back to the center)
in this instance it does register a Canceled context though.
So my proposal for the fix is to just make sure that on axis values (vector and float) the Callback Context -> Context To Process is just set to Everything
This will mean the value is registered upon it first being touched, then registered for every subsequent performed and will also register on the final Canceled.
It may mean that the Value Changed event on the zinnia action could report the same value 3 times for the same frame. I think I'll just chance that and see if anyone finds that to be an issue first.

This PR https://github.com/ExtendRealityLtd/Tilia.Input.UnityInputSystem/pull/20 should fix the issue, it will need to be updated in the farm scene too

:tada: This issue has been resolved in version 1.1.11 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.1.11
GitHub release

Your semantic-release bot :package::rocket:


Self signed certificate

I get the following error once I run the script.
"Error sending mail: Error: self signed certificate in certificate chain"
Any idea how to resolve this issue?
Thanks!

Hi!
Have you tried changing Google less secure apps settings?
Anyways, I'm preparing new version with updated scraper for both pages and Google OAuth2 authentication with instruction on how to do it. I will push it in a week or two.
Regards

Hi!
Yea i turned that on.
No prob :) will wait for the newer version then.
Thanks for getting back!

Hi!
just pushed the new version. Enjoy!


Netscan Detected - Server Locked

Hello,
Just wanted to let you guys know that I received an abuse email from my server provider and they locked my server. Looking at the logs they sent, it's obviously coming from the hyprspace instance / interface I had setup.
> ##########################################################################
> #               Netscan detected from host   <IP_ADDRESS>               #
> ##########################################################################
>
> time                protocol src_ip src_port          dest_ip dest_port
> ---------------------------------------------------------------------------
> Mon Oct 17 20:44:14 2022 TCP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 31752
> Mon Oct 17 20:44:14 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 31752
> Mon Oct 17 20:44:14 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 31752
> Mon Oct 17 20:44:18 2022 TCP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 9401
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14584
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14584
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14584
> Mon Oct 17 20:43:45 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14584
> Mon Oct 17 20:43:45 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14584
> Mon Oct 17 20:43:08 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30003
> Mon Oct 17 20:43:56 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30003
> Mon Oct 17 20:43:56 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30003
> Mon Oct 17 20:42:05 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30003
> Mon Oct 17 20:42:05 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30003
> Mon Oct 17 20:42:05 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30003
> Mon Oct 17 20:44:19 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30003
> Mon Oct 17 20:44:19 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30003
> Mon Oct 17 20:44:12 2022 TCP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30003
> Mon Oct 17 20:44:12 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30003
> Mon Oct 17 20:44:12 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30003
> Mon Oct 17 20:44:17 2022 TCP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 34567
> Mon Oct 17 20:43:37 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:37 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:37 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:40 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:40 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14591
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14596
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14596
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14596
> Mon Oct 17 20:43:45 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14596
> Mon Oct 17 20:43:45 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14596
> Mon Oct 17 20:42:54 2022 TCP   <IP_ADDRESS> 8001  => <IP_ADDRESS> 32962
> Mon Oct 17 20:42:55 2022 TCP   <IP_ADDRESS> 8001  => <IP_ADDRESS> 32962
> Mon Oct 17 20:42:57 2022 TCP   <IP_ADDRESS> 8001  => <IP_ADDRESS> 32962
> Mon Oct 17 20:42:39 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:41:45 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:41:45 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:41:45 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:41 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:41 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:41 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:41 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:41 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:41 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:41:46 2022 TCP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:41:46 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:42:32 2022 TCP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:42:32 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:42:32 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:42:32 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:42:32 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:43:50 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30013
> Mon Oct 17 20:44:18 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:44:18 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:44:18 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:42:31 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:42:31 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:42:31 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:18 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:18 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:19 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:28 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:43:28 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30013
> Mon Oct 17 20:44:25 2022 TCP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30013
> Mon Oct 17 20:44:25 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30013
> Mon Oct 17 20:44:25 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30013
> Mon Oct 17 20:42:54 2022 TCP   <IP_ADDRESS> 8001  => <IP_ADDRESS> 57091
> Mon Oct 17 20:42:55 2022 TCP   <IP_ADDRESS> 8001  => <IP_ADDRESS> 57091
> Mon Oct 17 20:44:22 2022 TCP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 51197
> Mon Oct 17 20:43:45 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:45 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:46 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:44:20 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:44:20 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:44:20 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:50 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:50 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:51 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:51 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:52 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:30 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:30 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:30 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:51 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30009
> Mon Oct 17 20:43:51 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30009
> Mon Oct 17 20:43:30 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:30 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:43:30 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30009
> Mon Oct 17 20:42:39 2022 TCP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30009
> Mon Oct 17 20:44:14 2022 TCP   <IP_ADDRESS> 8001  =>  <IP_ADDRESS> 40883
> Mon Oct 17 20:43:37 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:37 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:37 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:38 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:40 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:40 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:43:42 2022 UDP   <IP_ADDRESS> 8001  =>        <IP_ADDRESS> 14589
> Mon Oct 17 20:42:09 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:42:10 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:42:12 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:43:09 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:43:09 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:43:10 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:43:12 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:44:24 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:44:25 2022 TCP   <IP_ADDRESS> 8001  =>      <IP_ADDRESS> 33513
> Mon Oct 17 20:44:19 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30002
> Mon Oct 17 20:44:19 2022 UDP   <IP_ADDRESS> 8001  =>     <IP_ADDRESS> 30002
> Mon Oct 17 20:43:18 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30002
> Mon Oct 17 20:43:54 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:54 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:54 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:54 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:55 2022 TCP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:55 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:55 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:56 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:53 2022 TCP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:53 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:43:53 2022 UDP   <IP_ADDRESS> 8001  =>   <IP_ADDRESS> 30002
> Mon Oct 17 20:42:44 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30014
> Mon Oct 17 20:42:44 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30014
> Mon Oct 17 20:42:45 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30014
> Mon Oct 17 20:43:18 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30014
> Mon Oct 17 20:43:18 2022 UDP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30014
> Mon Oct 17 20:44:17 2022 TCP   <IP_ADDRESS> 8001  =>    <IP_ADDRESS> 30014

Thanks for reporting @digitalnomad91! If you don't mind me asking what cloud provider you were using and have you run IPFS with that company before?

Hetzner, and yes indeed I have run IPFS with them before. I have had this issue in the past when running IPFS. Apparently I needed to be running IPFS with the server profile flag. I see that hyprspace is built on top of IPFS, could it be because when I ran the default setup for hyprspace it installed a docker image of IPFS that wasn't configured properly for a server accessible from the outside? I would really like to get hyprspace going again so I can run agentdvr and run CodeProject.AI.Server / PortraitFilter on my dedi instead of my local machine, and I'd rather have to avoid settng up port forwarding and whatnot in order to do so. Any suggestions on how I can achieve that without setting up my machine to become part of some nefarious network activity. I do have a ufw firewall running, but when I was playing around with hyprspace I lazily just added a rule to allow all traffic on its required ports, so perhaps there is a ufw rule (or iptables) that I can configure to prevent my servers network from being abused. Thanks!

I just finished testing using Hyprspace to connect Digital Ocean Server to
Hetzner Server.
OS:  ubuntu 22.04
I use LXD containers so I created one LXD container on both the Digital
Ocean and Hezner servers.
The LXD containers were both Ubuntu but they could have been any other
Distro that LXD supports
such as Fedora, Centos, Debian, Alpine, Suse, RHEL, etc etc
I installed Hyprspace in each Server's LXD container that I created.
Configured the Hyprspace for peering in each
On the Digital Ocean container I pinged the "vpn" ip of the Hetzner
container
Didn't appear to work???
Yesterday, * I too was mystified because I thought it didn't work and I too
had this before.*
Today I decided to try it again but this time I just let the PING run.
I was happily surprised that after about 5 minutes ... the pings started
succeeding !
I do NOT know why it took so long for the 2 TEP's to "find" each other.
Here are my IPERF3 results:
iperf3 commands to use:

on "server/destination:   iperf3 -s
*on "server/client"  iperf3 -c <IP_ADDRESS> *
By default, the benchmark will run for 20 seconds. Then, it will present
the average throughput for the run.

Yesterday when I thought it wasn't working.... I just didn't wait long
enough so I thought it was broken 😎
Brian
On Thu, Oct 20, 2022 at 10:28 AM Andrew Corbin @.***>
wrote:

Hetzner, and yes indeed I have run IPFS with them before. I have had this
issue in the past when running IPFS. Apparently I needed to be running IPFS
with the server profile flag. I see that hyprspace is built on top of IPFS,
could it be because when I ran the default setup for hyprspace it installed
a docker image of IPFS that wasn't configured properly for a server
accessible from the outside? I would really like to get hyprspace going
again so I can run agentdvr and run CodeProject.AI.Server / PortraitFilter
on my dedi instead of my local machine, and I'd rather have to avoid settng
up port forwarding and whatnot in order to do so. Any suggestions on how I
can achieve that without setting up my machine to become part of some
nefarious network activity. I do have a ufw firewall running, but when I
was playing around with hyprspace I lazily just added a rule to allow all
traffic on its required ports, so perhaps there is a ufw rule (or iptables)
that I can configure to prevent my servers network from being abused.
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/hyprspace/hyprspace/issues/99#issuecomment-1285645983,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM23J3IKEBHT2O4EU3WZ63WEFJHTANCNFSM6AAAAAARJPCXQU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

https://github.com/hyprspace/hyprspace/issues/28 is probably relevant here, or in general just having a way to disable LAN connections


Add support for ghc-bignum

GHC 9 moved bignum (Integer and Natural) implementations to a new library,
which exposes new operations. Previously, instances were derived. These new
operations need explicit Categorifier support.
Fixes #99.

For now, this requires adding the following GHC flags:
-fplugin-opt Categorifier:lookup:Categorifier.GhcBignum.Integration.symbolLookup
-fplugin-opt Categorifier:maker-map:Categorifier.GhcBignum.Integration.makerMapFun

but since this library is depended-on by base and these operations can be encountered by using types exposed by base, these should be part of the “core” plugin flags (conditional on GHC 9 being used).
I’m waffling on the best way to do that. Of course, my inclination is always more packages – e.g., split categorifier-plugin into three packages like

categorifier-integration(a library for writing integrations),
categorifier-base-integration (the existing base support), and
categorifier-plugin (the actual plugin).

graph BT
  bignum(categorifier-ghc-bignum-integration) --> integration(categorifier-integration)
  base(categorifier-base-integration) --> integration
  base --> bignum
  plugin(categorifier-plugin) --> base

Then users should still only need to depend on categorifier-plugin to get base (and ghc-bignum) support, but we can still partition everything by library. And extracting base (by far the biggest “integration”) might help solidify the API for other integrations.


AdminPanel: Improve character creation and editing

Is your feature request related to a problem? Please describe.
When creating or editing a character, a lot of additional objects need to be created to make it functional. The user interface is a bit hard if you don't know about the internal data structures.
For example, editing stat values requires to know that there is an stat attributes collection.
Describe the solution you'd like
A more intiutive UI and automatic initialization of the required objects.
It should initialize the same data as the game logic when creating a character in-game.

To add to this, when I edit and save a character using the admin panel editor, then update it in the game client and exit game, going back to the edit character still shows the old state (before doing anything in game), and not the state after exiting the game.
For example, I added remaining 1000 level up points in Admin Panel, then consume that 1000 points in game, going back to admin panel, the 1000 points still show up. Same for items.


role manager does not always notify listeners of changes

The change event is not reliably sent (or received) so we keep outdated role manager data.

Fixed. However, it seems that the change event gets missed sometimes.


Dont use spread here

Originally posted by @lts20050703 in https://github.com/discordeno/discordeno/pull/1927#discussion_r792489877

Waiting for #1927 to merged...


can't open '/var/log/letsencrypt/letsencrypt.log': No such file or directory

Upon starting services with cli.sh up, I see in logs:
letsencrypt-docker-compose-certbot-1  | tail: can't open '/var/log/letsencrypt/letsencrypt.log': No such file or directory

Doesn't seem to be fatal, but doesn't look too healthy either. Did I skip a step somewhere?

Please share the certbot service logs.
docker compose logs -f certbot

The file /var/log/letsencrypt/letsencrypt.log can be absent if certbot certonly has never run since the service (re)start. It is expected in --dry-run mode. And maybe in some other cases, e.g., when you restarted the service and all certificates are not yet due to renewal, so certbot certonly is not executed.
Probably, less confusing will be preserving logs from the previous executions. Certbot files can be mounted to a separate volume to survive the restarts.

The output you asked for:
$ docker compose logs -f certbot
letsencrypt-docker-compose-certbot-1  | Obtaining the certificate for domain abc.xyz.com
letsencrypt-docker-compose-certbot-1  | Let's Encrypt certificate for abc.xyz.com already exists
letsencrypt-docker-compose-certbot-1  | tail: can't open '/var/log/letsencrypt/letsencrypt.log': No such file or directory

And nothing else. Stops there.

@tka85, I changed Certbot Docker entrypoint to remove confusing log message. There is no real error.
You can pull the latest changes.


feat(dependabot): :sparkles: add dependabot for updating Python dependencies

Description

This PR adds dependabot and configures it to update Python dependencies (managed by Poetry) in this repository.
The PRs will look something like:

See also Issue https://github.com/seedcase-project/.github/issues/24
Testing

[ ] Yes
[x] No, not needed (give a reason below)
[ ] No, I need help writing them

I tested it in a minimal repo and it seemed to behave as expected.

Reviewer Focus

This PR only needs a quick review.

Checklist

For all PRs that are not general documentation

[x] Tests accompany or reflect changes to the code
[x] Tests ran and passed locally
[x] Ran the linter and formatter
[x] Build has passed locally
[x] Relevant documentation has been updated

I read around a bit about what some sensible default settings might be, but it's still pretty bare bones, so feel free to ignore or change.


Fix #570

@afred?

(It's going to change because the mock transcript on S3 has changed.)

@mccalluc rebasing.. stand by.


Update microsoft365-maturity-model--communication.md

fixed links, removed en-us specific

Docs Build status updates of commit 7e848e0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/microsoft365-maturity-model--communication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Collection number herbarium record api

This is failing on my vm:
$ git branch -v
  blast-links     1226d40 [ahead 1] Assorted CodeClimate/Rubocop fixes
* master          ca04207 Merge pull request #369 from pellaea/collection-number-herbarium-record-api
  sequence-anyone 126efd4 Conform API POST Sequence to UI
VM:mushroom-observer
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working directory clean
VM:mushroom-observer
$ rake
Started with run options --seed 2552

 FAIL["test_api_error_translations", LocalizationFilesTest, 89.52804940099304]
 test_api_error_translations#LocalizationFilesTest (89.53s)
        Missing API error translations:
        :api_cant_add_herbarium_record
        :api_herbarium_record_already_exists
        .
        Expected [:api_cant_add_herbarium_record, :api_herbarium_record_already_exists] to be empty.
        test/models/localization_files_test.rb:8:in `assert_no_missing_translations'
        test/models/localization_files_test.rb:162:in `test_api_error_translations'

  1651/1651: [=============================================================] 100% Time: 00:03:36, Time: 00:03:36

Finished in 216.50116s
1651 tests, 22459 assertions, 1 failures, 0 errors, 0 skips
Coverage report generated for MiniTest to /vagrant/mushroom-observer/coverage. 41318 / 43649 LOC (94.66%) covered.
[Coveralls] Outside the CI environment, not sending data.

Just need to run rake lang:update
On Mon, Dec 25, 2017 at 10:04 AM, Joseph D. Cohen<EMAIL_ADDRESS>wrote:

This is failing on my vm:
$ git branch -v
blast-links     1226d40 [ahead 1] Assorted CodeClimate/Rubocop fixes

master          ca04207 Merge pull request #369 from pellaea/collection-number-herbarium-record-api
sequence-anyone 126efd4 Conform API POST Sequence to UI
VM:mushroom-observer
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working directory clean
VM:mushroom-observer
$ rake
Started with run options --seed 2552
FAIL["test_api_error_translations", LocalizationFilesTest, 89.52804940099304]
test_api_error_translations#LocalizationFilesTest (89.53s)
Missing API error translations:
:api_cant_add_herbarium_record
:api_herbarium_record_already_exists
.
Expected [:api_cant_add_herbarium_record, :api_herbarium_record_already_exists] to be empty.
test/models/localization_files_test.rb:8:in assert_no_missing_translations'         test/models/localization_files_test.rb:162:in test_api_error_translations'
1651/1651: [=============================================================] 100% Time: 00:03:36, Time: 00:03:36
Finished in 216.50116s
1651 tests, 22459 assertions, 1 failures, 0 errors, 0 skips
Coverage report generated for MiniTest to /vagrant/mushroom-observer/coverage. 41318 / 43649 LOC (94.66%) covered.
[Coveralls] Outside the CI environment, not sending data.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/369#issuecomment-353883077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADE2tYOLw1sAzqssv3qk4OlbyylKiKG5ks5tD-OvgaJpZM4RMLKI
.

Sorry.  I realized that about 1 microsecond after adding my comment (now
deleted).
On Mon, Dec 25, 2017 at 10:59 AM Jason Hollinger<EMAIL_ADDRESS>wrote:

Just need to run rake lang:update
On Mon, Dec 25, 2017 at 10:04 AM, Joseph D. Cohen <
<EMAIL_ADDRESS>wrote:

This is failing on my vm:
$ git branch -v
blast-links 1226d40 [ahead 1] Assorted CodeClimate/Rubocop fixes

master ca04207 Merge pull request #369 from
pellaea/collection-number-herbarium-record-api
sequence-anyone 126efd4 Conform API POST Sequence to UI
VM:mushroom-observer
$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working directory clean
VM:mushroom-observer
$ rake
Started with run options --seed 2552
FAIL["test_api_error_translations", LocalizationFilesTest,
89.52804940099304]
test_api_error_translations#LocalizationFilesTest (89.53s)
Missing API error translations:
:api_cant_add_herbarium_record
:api_herbarium_record_already_exists
.
Expected [:api_cant_add_herbarium_record,
:api_herbarium_record_already_exists] to be empty.
test/models/localization_files_test.rb:8:in
assert_no_missing_translations' test/models/localization_files_test.rb:162:in test_api_error_translations'
1651/1651:
[=============================================================] 100% Time:
00:03:36, Time: 00:03:36
Finished in 216.50116s
1651 tests, 22459 assertions, 1 failures, 0 errors, 0 skips
Coverage report generated for MiniTest to
/vagrant/mushroom-observer/coverage. 41318 / 43649 LOC (94.66%) covered.
[Coveralls] Outside the CI environment, not sending data.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/MushroomObserver/mushroom-observer/pull/369#issuecomment-353883077
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ADE2tYOLw1sAzqssv3qk4OlbyylKiKG5ks5tD-OvgaJpZM4RMLKI
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/369#issuecomment-353885208,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACxlEcnfHss_CAxrgzU6A1b_S4WAyv9ks5tD_CBgaJpZM4RMLKI
.


I hope to find supplementary materials related to the paper.

Hello,
Thank you very much for making part of the DMT code available. The DMT method you've proposed has been quite inspiring for our research. We noticed that your paper (https://ieeexplore.ieee.org/document/10614866) frequently references supplementary materials, but unfortunately, we were unable to locate them within the paper. We look forward to your response.
Best regards.

Hi, the IEEE url you mentioned has already been attached to the supplementary materials. They are addressed at the bottom at the page (https://ieeexplore.ieee.org/document/10614866/media#media), instead of within the paper.

Thank you for your sincere response.


Lightning cant find visible gpu when using pytorch 1.5.0

🐛 Bug
When using the latest pytorch version 1.5.0 with multi-gpu's (backend ddp), lightning says there are no visible gpu's.
The same code runs without issues when using pytorch 1.4.0

  File "/opt/conda/lib/python3.7/site-packages/pytorch_lightning/trainer/trainer.py", line 464, in __init__
    self.data_parallel_device_ids = parse_gpu_ids(self.gpus)
  File "/opt/conda/lib/python3.7/site-packages/pytorch_lightning/trainer/distrib_parts.py", line 730, in parse_gpu_ids
    gpus = sanitize_gpu_ids(gpus)
  File "/opt/conda/lib/python3.7/site-packages/pytorch_lightning/trainer/distrib_parts.py", line 696, in sanitize_gpu_ids
    """)
pytorch_lightning.utilities.exceptions.MisconfigurationException:
                You requested GPUs: [0, 1, 2, 3, 4, 5, 6, 7]
                But your machine only has: []

PyTorch Version (e.g., 1.0): 1.5.0
OS (e.g., Linux): Linux
How you installed PyTorch (conda, pip, source): pip
Python version: 3.7
CUDA/cuDNN version: 10.1
GPU models and configuration: Nvidia - V100 - 8 gpu's
Lightning - 0.7.6

mind posting a script to recreate?

also make sure you have the gpu version of pytorch

i'm kind of sensing that you stopped your aws instance and resumed it. I encountered this exact same "bug" when I did that. For some unknown reasons, when you stop a gpu instance on aws and resume it, the nvidia driver goes away.. Try nvidia-smi to see if you still see your GPUs.

I was using cuda 10.1 and upgraded pytorch (which by default expects cuda 10.2). Installed pytorch 1.5.0 in the right way and it fixed the issue

torch==1.8.0 solved my same problem.

This code saved my life.
conda install pytorch==1.8.0 torchvision==0.9.0 torchaudio==0.8.0 cudatoolkit=10.2 -c pytorch


Add support for RFC 4476

Add module and test for RFC 4476

Codecov Report

Merging #128 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #128      +/-   ##
==========================================
+ Coverage   99.44%   99.44%   +<.01%
==========================================
  Files         118      119       +1
  Lines        6831     6861      +30
==========================================
+ Hits         6793     6823      +30
  Misses         38       38

Impacted Files
Coverage Δ

pyasn1_modules/rfc4476.py
100% <100%> (ø)

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 a599c15...bae3375. Read the comment docs.

Thank you!
I am wondering, can it be said that pyasn1-modules is about to have all ASN.1 structures that ever appeared in RFCs?

No.  I have made no attempt to do all the MIB modules, LDAP-related modules, or Kerberos-related modules.  That is just not my area.

Understood. I am thinking how to express the work you've done in package description...? ASN.1 modules from which area are mostly covered?


doc: adapt README to crates.io

At this moment bmap-rs and bmap-parser share the same README. This is problematic because in crates.io, once published, bmap-parser contains references to bmap-rs while if should be independent from it.
Fix the original README file.
Add a new README file for bmap-parser.
Signed-off-by: Rafael Garcia Ruiz<EMAIL_ADDRESS>

Just in case we want to quick fix the README problem, I've committed a bump to versions.

can you drop the bors commit and the version bump commit ?
We are gonna drop bors at some point, and I think we should handle the release separately.


Unable to capute HD image.

Hi,
I am trying to capture HD image "HD720" but it shows.
Code:
webcam.setViewSize(WebcamResolution.HD720.getSize());
Error:
Exception in thread "main" java.lang.IllegalArgumentException: Incorrect dimension [1280x720] possible ones are [176x144] [320x240] [640x480]
at com.github.sarxos.webcam.Webcam.setViewSize(Webcam.java:588)
at WebcamAPI.main(WebcamAPI.java:14)

Hi @goodrahstar,
This example should shed some more light on your problem. Please follow the code and use setCustomViewSizes(..) method prior the setViewSize(..) is called.
https://github.com/sarxos/webcam-capture/blob/master/webcam-capture/src/example/java/CustomResolutionExample.java
The "standard" resolutions (in opposite to "custom") are QQVGA, QVGA and VGA, which means that all of them are supported by all manufactured UVC devices (with 99.9% probability). The HD720 is not among them - there is many devices which does not support it.
To cut the story short, to resolve your issue just do:
Dimension[] nonStandardResolutions = new Dimension[] {
	WebcamResolution.HD720.getSize(),
};
Webcam webcam = Webcam.getDefault();
webcam.setCustomViewSizes(nonStandardResolutions);
webcam.setViewSize(WebcamResolution.HD720.getSize());

Hi @sarxos
Thanks man for your quick response.
It works :)

Great :) Take care!


Jan 26/scrutinizer fixes

Issue
Scrutinizer flagged a number of documentation and commenting issues in the current 2.x branch. This resolves a number of them.
Most significantly though, I discovered that in deprecating a bunch of Twig functions in lib/Twig.php functionality was removed. In 2.0 Twig code like:
{{ TimberPost(maybe_post).title }}

should now be written as:
{{ Post(maybe_post).title }}

However, these methods (TimberPost, TimberTerm, etc.) had not been properly deprecated until now. Thus, I think we should send the deprecation notice (which 2.x currently does) though still maintain present 1.x functionality (for now)
Solution
Restore functionality for these deprecated methods and update tests accordingly
Usage Changes
None
Considerations
We should totally kill these functions in 3.x now that they've been properly deprecated
Testing
Tests are updated

This is ready for your formal review @gchtr

I did some research and it seems that while phpdoc says either is fine, in PHP apparently "bool" and "int" are the official names and "boolean" and "integer" are aliases: https://stackoverflow.com/questions/44009037/php-bool-vs-boolean-type-hinting
I made a card in the 2.0 project to go through and make everything int and bool as part of the Final Pass


Update ALM API docs - Add O365 CLI, update REST API headers & typos

Q
A

content fix?
yes

New article?
no

Related issues?
n/a

What's in this Pull Request?

Added a new section for the Office 365 CLI usage
Added item to list of API capabilities to include "list & get"
Fixed typos
Updated some verbiage to be more correct / clear

Thx AC. Sorry for the delay.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/apis/alm-api-for-spfx-add-ins.md
:white_check_mark:Succeeded

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


Fixed progress showing incorrectly for Quick Starts.

Fixes issue where quick start is not completed and doesn't show in progress and where it completed with failed steps.

lgtm, just as we discussed.


Added ability to create reverse lookup zone.

Hi @corydwood, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@corydwood Thanks for your contribution! However, I'm not entirely sure you needed to add all these additions.. It's always been possible to create reverse lookup zones with this resource, but that has obviously not been well documented.
There are really two changes here:

Creating reverse lookup zones
Adding AD integrated zone support

The AD integrated zones were earmarked for a separate resource due to all the other parameters available that would clutter this resource unnecessarily - see #5. I'm positive we can integrate your AD zone changes in some fashion. Now, whether these all get bundled into one resource is up for discussion! @TravisEz13 @PlagueHO thoughts?

I didn't realize you could create a reverse zone with the -Name parameter instead of -NetworkID, but I just tried it and it works, so I agree that most of these changes aren't needed if you want to keep AD integrated zone creation in a separate resources.
The fixes that still need to be made are the ordering of the values after the -f in the verbose messages and replacing the invalid $dnsServerZone.Name with $dnsServerZone.ZoneName.

@corydwood @iainbrighton Can one of you file an issue to document how to create a reverse lookup zone with the existing resource if it's not well documented currently with a small sample of how to do it?

@TravisEz13 @iainbrighton I just did: #18.

@corydwood Do we need to leave this PR open?  I thank based on the comments it would be best to open a new one just fixing the issues you mentioned

@corydwood we still need an AD-integrated zone resource so all is not lost! Fancy taking a shot at that? If so, log an issue with proposed implementation and we'll go from there..
A friendly bit of advise: in future, log an issue first - before starting any work! I've found this out to my cost in the past as well :(


New term request non_allelic_homologous_recombination_region

From Clara Amid:
I’d like to suggest to add the following term:
non_allelic_homologous_recombination_region
Definition: A genomic region at a non-allelic position where exchange of genetic material happens as a result of homologous recombination.
Note: NAHR is a very distinct type of recombination event that is described in the literature and has been shown to result in mutations found in a variety of genomic disorders, disease susceptibilities and cancers.

From Karen:
Hi Clara,
I am working on your term.
I just need to get the concept straight in my head before I can figure out the right parent.
You have a region of sequence that is in a repetitive region of the genome, but not genic, that is susceptible to cause rearrangement and therefore cause CNV like changes?
NAHRR itself is not an alteration, but a marker of a region in the genome where rearrangements happen.
Do you think it would be better to place it as a child of recombination_feature, or recombination_hotspot?

I added this term SO:0002094 non_allelic_homologous_recombination_region as a child of recombination_hotspot. The definition is the one that Clara provided.


Save sourceMap if returned from scss

This change allows saving source map near compiled .css file.
To make it work, the compiler should return not empty map (by default it is empty).
To make it not empty, we should pass sourceMap and outFile options to sass.renderSync method.
The outFile is added automatically in this PR, and sourceMap  should be given by a user, like:
scss({
  sourceMap: true,
})

Done

When does this go online/released?


lyxal: Watch pkinstitutecourses.com

lyxal requests the watch of the watch_keyword pkinstitutecourses\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

pkinstitutecourses\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


test: fix composer fetch schema test

I've included a better fix for this in https://github.com/platformatic/platformatic/pull/1088/files#diff-ad47987fc994c65f659c4ee8687466b3411373d1ded7ede89beba76c2ef55ae2R15-R19.


NTR for contractile vacuole processes

I would like to add some terms involving the processes of contractile vacuoles, which occur in Dicty and many other microorganisms as well as in algae.
PMID:22323285 looks at what they call the ‘kiss and run’ discharge, and that seems the difference to some other vesicle processes, the membranes do not completely merge in the discharge process. They dissect what tethers and detethers the CV to the PM.
GO:NEW: contractile vacuole tethering involved in discharge
EXACT synonym: contractile vacuole tethering to plasma membrane
DEF: The initial, indirect interaction between a contractile vacuole membrane and a site of discharge in the plasma membrane. This interaction is mediated by tethering factors (or complexes), which interact with both membranes. Interaction can occur via direct binding to membrane phospholipids or membrane proteins, or via binding to vesicle coat proteins. This process is distinct from and prior to docking and fusion.
is_a
— GO:0090522: vesicle tethering vesicle tethering involved in exocytosis
However, I also need a term for the detethering, or dissociation of the emptied vacuole after discharge.
GO:NEW: contractile vacuole detethering from plasma membrane
DEF: The dissociation of the contractile vacuole after discharge, from the plasma membrane.  This interaction is mediated by detethering factors that initiate the process of tubulation and fragmentation of the empty CV bladder, which is then reincorporated into the CV network.
What structure? Maybe a direct child of GO:0051650: establishment of vesicle localization?
Also,should both terms above be children of GO:003329: contractile vacuole organization? This term has currently no children.
Comments:

Detethering was used in the paper but dissociation would do if preferred, otherwise could be added as synonym
CV is a ubiquitous acronym for contractile vacuole, used it in def but spell out if desired.

Finally, looking at another paper (PMID:19687255), They identified a class V myosin (myoJ) responsible for the transport of the CV to the cortex (near PM) and back. To annotate that, I would like to add another child to GO:0051650 establishment of vesicle localization
GO:NEW: contractile vacuole localization OR establishment of contractile vacuole localization
The directed movement of the contractile vacuole to a specific location.
Thanks,
Petra

Hi Petra,
For GO:NEW: contractile vacuole tethering involved in discharge, I put the proposed synonym "contractile vacuole tethering to plasma membrane" as NARROW, since it's missing the discharge aspect; ok?

Here are the 3 new terms:
[Term]
+id: GO:0140025
+name: contractile vacuole tethering involved in discharge
+namespace: biological_process
+def: "The initial, indirect interaction between a contractile vacuole membrane and a site of discharge in the plasma membrane. This interaction is mediated by tethering factors (or complexes), which interact with both membranes. Interaction can occur via direct binding to membrane phospholipids or membrane proteins, or via binding to vesicle coat proteins. This process is distinct from and prior to docking and fusion." [PMID:22323285]
+synonym: "contractile vacuole tethering to plasma membrane" NARROW []
+is_a: GO:0090522 ! vesicle tethering involved in exocytosis
+intersection_of: GO:0006903 ! vesicle targeting
+intersection_of: part_of GO:0070177 ! contractile vacuole discharge
+created_by: pg
+creation_date: 2017-05-02T09:50:10Z
+
+[Term]
+id: GO:0140026
+name: contractile vacuole dissociation from plasma membrane
+namespace: biological_process
+def: "The dissociation of the contractile vacuole after discharge, from the plasma membrane. This interaction is mediated by detethering factors that initiate the process of tubulation and fragmentation of the empty contractile vacuole bladder, which is then reincorporated into the CV network." [PMID:22323285]
+synonym: "contractile vacuole detethering from plasma membrane" EXACT []
+is_a: GO:0016192 ! vesicle-mediated transport
+created_by: pg
+creation_date: 2017-05-02T10:16:12Z
+
+[Term]
+id: GO:0140027
+name: establishment of contractile vacuole localization
+namespace: biological_process
+def: "The directed movement of the contractile vacuole to a specific location." [PMID:19687255]
+is_a: GO:0051656 ! establishment of organelle localization
+created_by: pg
+creation_date: 2017-05-02T10:23:26Z
Thanks, Pascale

Hello Pascale, I finally looked more into your questions that you seemed to have answered yourself. Here my (late) comments:

GO:0090522: vesicle tethering vesicle tethering involved in exocytosis has the EXACT synonym: vesicle tethering to plasma membrane. Maybe you should make this a NARROW synonym too? I kind of did it in analogy to this.

Yes! I think the CV discharge is_a exocytosis

Many thanks,
Petra

Thanks Petra for the feedback. I fixed the synonym scope of 'GO:0090522: vesicle tethering involved in exocytosis'.
Cheers, Pascale


modern-restaurant-website

Restaurant website with Animation 1986
Close #1986
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@pranjay-poddar can you check committed files , is there any problem with my pushing code.