Hass and Raspberry cannot run the command

pi@raspberrypi:~/sunpower_hass $ python sunpower.py Traceback (most recent call last):   File "sunpower.py", line 3, in <module>     from urllib import request ImportError: cannot import name request pi@raspberrypi:~/sunpower_hass $ python2 sunpower.py Traceback (most recent call last):   File "sunpower.py", line 3, in <module>     from urllib import request ImportError: cannot import name request pi@raspberrypi:~/sunpower_hass $ python3 sunpower.py Traceback (most recent call last):   File "sunpower.py", line 5, in <module>     from config import Config ImportError: No module named 'config' pi@raspberrypi:~/sunpower_hass $
pi@raspberrypi:~/sunpower_hass $ python sunpower.py
Traceback (most recent call last):
File "sunpower.py", line 3, in
from urllib import request
ImportError: cannot import name request
pi@raspberrypi:~/sunpower_hass $ python2 sunpower.py
Traceback (most recent call last):
File "sunpower.py", line 3, in
from urllib import request
ImportError: cannot import name request
pi@raspberrypi:~/sunpower_hass $ python3 sunpower.py
Traceback (most recent call last):
File "sunpower.py", line 5, in
from config import Config
ImportError: No module named 'config'
pi@raspberrypi:~/sunpower_hass $
Appreciate by the component and its attention, thank you

Apologies for not making this a "proper" python module and adding a setup.py.
You'll need to run pip install -r requirements.txt to install the per-requisites.
I'd also recommend running this in a python virtualenv. (See https://www.pythoncentral.io/how-to-install-virtualenv-python/ or just look for "python virtualenv"
This was more a goof around project for me. Eventually, I should finish it up and make it a proper home assistant module.

thanks, is perfect
but
Is there any way the command line works in the Hassio?

Oh, probably. I really should just make it a real HomeAssistant extension, but I've not had a lot of time to do it.
I'm not quite sure I follow what you mean by "command line", though.
In my configuration.yaml file I've got:
# solar:
sensor:
   - platform: command_line
     # Sunpower only updates every 5 minutes. No need to call more often.
     scan_interval: 300
     name: Solar Production
     # This uses the same python that runs HomeAssistant, and calls the script I've copied into
     # a sub directory
     command: $HASS/bin/python $HOME/.homeassistant/scripts/sunpower.py
     unit_of_measurement: "kW"

I know that they recently rolled out the HomeAssistant Command Line, and I have no idea how well this works with that. I do know that it works with the HTTP interface, since  I can call it from another server:
$ curl "http://home:8123/api/states/sensor.solar_production"
{"attributes": {"friendly_name": "Solar Production", "unit_of_measurement": "kW"}, "context": {"id": "c2b53359cfd944c19ac79d9ad7555e93", "user_id": null}, "entity_id": "sensor.solar_production", "last_changed": "2019-02-22T15:44:28.429890+00:00", "last_updated": "2019-02-22T15:44:28.429890+00:00", "state": "0.24"}

and that's good enough for what I need.
Does that help?
(By the way, thanks for these questions. Again, when I get the time to write up proper documentation, they'll be really useful. Sorry for any confusion, but I'm very happy to provide whatever info I can.)


[pg] Add support multi schemas migrations

I take no credit for this PR, I just grabbed the PR #1638 and fixed all conflicts. I needed it for my project and saw a few more people too, so I decided to help with this.

Thanks a lot for your work. I was fixing some issues we had and also resolved all issues with the SQLite Proxy. I didn't have a chance to review this PR before fixing everything
Was released in<EMAIL_ADDRESS>https://github.com/drizzle-team/drizzle-orm/releases/tag/0.29.5


Prototypes - testing purposes

… share it

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

Closing as this has seen no activity for awhile. Please reopen if still relevant. Thanks!


Add flag to make PassThroughInputManager not sync new presses in Sync() except for initial state

Discussed in https://github.com/ppy/osu/issues/9658#issuecomment-2005767323, resolving one part of the issue.

When the game is paused, the game input manager has UseParentInput set to false for input to be frozen. When resuming gameplay in osu!, we ask the user to press a key at the location of the cursor first, then toggle back UseParentInput and resume gameplay accordingly.
If the user had paused without holding down any key, then when toggling back UseParentInput, either at the setter of UseParentInput, or at any subsequent update frames of the input manager, the key that was pressed to resume gameplay will be synchronised with the game input manager, causing gameplay to receive an incorrect press event and pollute the score for the player.
This PR introduces a flag, SyncNewPresses, which can be disabled to prevent the above from happening, by making Sync() not apply press input from parent state, and only look at releasing instead.

I dunno. I threw the flag proposal out as a potential way of avoiding complications. But I look at this diff and see more complications.
I'd like this to be simpler. Isn't it an option to (spitballing) make Sync() virtual and override it to do nothing in the resume overlay case or something?
At the least the flag needs to be named different. Something like TriggerInputEventsOnSync or something. Ideally it should mean that, too.

I think you're misunderstanding the issue. The point of this change is to make the input manager that contains the hit objects not sync new presses using Sync(), so it doesn't catch the press by the resume overlay if we intentionally block it from receiving it by the PassThroughInputManager.Handle(UIEvent) path. In other words, we want the following to happen:

User presses osu! action to resume.
ResumeOverlay receives the action press, but, using some method that I haven't decided on yet, it will not let the DrawableRuleset.KeyBindingInputManager (hit objects input manager) receive the action press via the Handle(UIEvent) path
Then, since I want DrawableRuleset.KeyBindingInputManager to have "sync new presses" disabled, once it's enabled to receive parent input (set UseParentInput to true), it will not apply the user's press of the osu! action.

I suggest we do away with the flag and conform to the new behaviour introduced by this PR, and reassess when something bad happens.

I don't like the increase in complexity here. I'd be tentatively okay with using the same logic as the mouse buttons, but I also have long forgotten why mouse buttons specifically differed.

The mouse button behaviour looks to have just been added as-is since https://github.com/ppy/osu-framework/pull/1682 with no specific reason.

I touched on that already in https://github.com/ppy/osu/issues/9658#issuecomment-2005767323 (see final point in bullet 2, where I linked the issue). But that being said, the diff will not change by much actually:
diff --git a/osu.Framework/Input/PassThroughInputManager.cs b/osu.Framework/Input/PassThroughInputManager.cs
index 40855fa26..e82e66ab6 100644
--- a/osu.Framework/Input/PassThroughInputManager.cs
+++ b/osu.Framework/Input/PassThroughInputManager.cs
@@ -48,15 +48,6 @@ public virtual bool UseParentInput

         private bool useParentInput = true;

-        /// <summary>
-        /// Whether to synchronise newly pressed buttons on <see cref="Sync"/>.
-        /// Pressed buttons are still synchronised at the point of loading the input manager.
-        /// </summary>
-        /// <remarks>
-        /// This does not apply for mouse buttons.
-        /// </remarks>
-        public bool SyncNewPresses { get; init; } = true;
-
         public override bool HandleHoverEvents => UseParentInput ? parentInputManager.HandleHoverEvents : base.HandleHoverEvents;

         internal override bool BuildNonPositionalInputQueue(List<Drawable> queue, bool allowBlocking = true)
@@ -251,7 +242,7 @@ protected virtual void SyncInputState(InputState state, bool applyPresses)
                 }
             }

-            if (SyncNewPresses || applyPresses)
+            if (applyPresses)
             {
                 // since we have a flag for syncing new presses, it is expected that we apply mouse button presses as well.
                 // this wasn't the case before the existence of the flag for another reason that's irrelevant here,

The applyPresses property will have to exist so that the input manager can apply new presses on LoadComplete to satisfy https://github.com/ppy/osu-framework/issues/1672.

Well I dunno what to say at this point if that is the extent of the changes incurred by the flag. You're basically presenting two choices: a schedule hack or increased complexity. At this point I'd be even willing to reconsider the schedule hack because at least it's self-contained to a degree I guess?

Two things need to be clarified:

The proposal of scheduling resume operation to be performed one frame later does not replace this PR, because as soon as UseParentInput is set to true and the ruleset input manager sees the pressed key it will still register it as pressed. The intention of this PR is to make the input manager completely disregard the pressed key regardless of how long it is held.
Disabling synchronisation on ruleset input manager after initial load does not help either, because we still want to synchronise buttons that were previously held but are now released (i.e. a user holding a slider but paused midway then resumed but didn't continue holding).

I've juggled and reordered the class around in hopes it reduces complexity. Take another look at it and see what you think. I have updated test coverage to reflect the new expected behaviour of the class, and tested on osu! to ensure it's working correctly.

I have removed the initial state synchronisation logic. Removing it does not regress the case brought in #1672 because scroll speed actions have been migrated to global key bindings, therefore not reading from the ruleset input manager to trigger the action. Also, if we compare this behavior on a normal Drawable, a drawable does not receive an OnKeyDown if it's added to the hierarchy after a key has been pressed, and when the key is up, it does not receive an OnKeyUp either (see test).
Therefore, for the sake of reducing complexity and matching general behaviour of drawable input handling, I have removed it, and also confirmed all tests both on o!f and osu! are passing, meanwhile the PR still maintains its original intent, which is to resolve https://github.com/ppy/osu/issues/9658 (only partly).


default exclude of node_modules cause issues

Describe the bug
We are trying to switch to vitest and most of our tests are working now,
but we encountered the following issue in some of our tests:
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

Check the render method of `Footer`.
 ❯ createFiberFromTypeAndProps node_modules/react-dom/cjs/react-dom.development.js:25058:21
 ❯ createFiberFromElement node_modules/react-dom/cjs/react-dom.development.js:25086:15
 ❯ createChild node_modules/react-dom/cjs/react-dom.development.js:13446:28
 ❯ reconcileChildrenArray node_modules/react-dom/cjs/react-dom.development.js:13719:25
 ❯ reconcileChildFibers node_modules/react-dom/cjs/react-dom.development.js:14125:14
 ❯ reconcileChildren node_modules/react-dom/cjs/react-dom.development.js:16990:28
 ❯ updateHostComponent node_modules/react-dom/cjs/react-dom.development.js:17632:3
 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:19080:14
 ❯ HTMLUnknownElement.callCallback node_modules/react-dom/cjs/react-dom.development.js:3945:14
 ❯ HTMLUnknownElement.callTheUserObjectsOperation node_modules/jsdom/lib/jsdom/living/generated/EventListener.js:26:30
 ❯ innerInvokeEventListeners node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:350:25
 ❯ invokeEventListeners node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:286:3
 ❯ HTMLUnknownElementImpl._dispatch node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:233:9
 ❯ HTMLUnknownElementImpl.dispatchEvent node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:104:17
 ❯ HTMLUnknownElement.dispatchEvent node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:241:34
 ❯ Object.invokeGuardedCallbackDev node_modules/react-dom/cjs/react-dom.development.js:3994:16
 ❯ invokeGuardedCallback node_modules/react-dom/cjs/react-dom.development.js:4056:31
 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:23964:7
 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:22779:12
 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:22707:5
 ❯ renderRootSync node_modules/react-dom/cjs/react-dom.development.js:22670:7
 ❯ performSyncWorkOnRoot node_modules/react-dom/cjs/react-dom.development.js:22293:18
 ❯ scheduleUpdateOnFiber node_modules/react-dom/cjs/react-dom.development.js:21881:7
 ❯ updateContainer node_modules/react-dom/cjs/react-dom.development.js:25482:3
 ❯ node_modules/react-dom/cjs/react-dom.development.js:26021:7
 ❯ unbatchedUpdates node_modules/react-dom/cjs/react-dom.development.js:22431:12
 ❯ legacyRenderSubtreeIntoContainer node_modules/react-dom/cjs/react-dom.development.js:26020:5
 ❯ Object.render node_modules/react-dom/cjs/react-dom.development.js:26103:10
 ❯ node_modules/@testing-library/react/dist/pure.js:101:25
 ❯ batchedUpdates$1 node_modules/react-dom/cjs/react-dom.development.js:22380:12
 ❯ act node_modules/react-dom/cjs/react-dom-test-utils.development.js:1042:14
 ❯ Proxy.render node_modules/@testing-library/react/dist/pure.js:97:26
 ❯ src/organisms/Footer/Footer.spec.tsx:49:30

Most of time it seems to relate when something is used from node_modules like
import { StaticRouter } from "react-router-dom";
will cause the error from above except of react itself, due to this vitest.config.js:
import path from "path";
import { readdirSync } from "fs";
import { defineConfig } from "vitest/config";
import react from "@vitejs/plugin-react";

const absolutePathAliases = {};
const srcPath = path.resolve("./src/");
const srcRootContent = readdirSync(srcPath, { withFileTypes: true }).map(
    (directoy) => directoy.name.replace(/(\.ts){1}(x?)/, "")
);

srcRootContent.forEach((directory) => {
    absolutePathAliases[directory] = path.join(srcPath, directory);
});

export default defineConfig({
    resolve: {
        alias: {
            ...absolutePathAliases,
        },
    },
    plugins: [
        react({
            babel: {
                parserOpts: {
                    plugins: ["decorators-legacy", "classProperties"],
                },
            },
        }),
    ],
    test: {
        globals: true,
        environment: "jsdom",
        deps: {
            interopDefault: true,
            fallbackCJS: true,
        },
        setupFiles: "./tests/Jest/setup-vitest.js",
        css: {
            modules: {
                classNameStrategy: "non-scoped",
            },
        },
    },
});

Should be caused be the default exclude setting in vitest.config. But i don't want to add everything manually.
So how can we fix this?
Reproduction
Setup vitest & testing-library/react and try to test a component which uses something from node_modules like react-router-dom inside of test or inside of a component like:
import React from "react";
import Footer from "organisms/Footer/Footer";
import { StaticRouter } from "react-router-dom";
import { fireEvent, render } from "@testing-library/react";

describe("Footer", () => {
    it("renders correctly", () => {
        const { container } = render(
            <StaticRouter location={""}>
                <Footer showTermsOfUse={true} />
            </StaticRouter>
        );
        expect(container).toMatchSnapshot();
    });
    ...

System Info
System:
    OS: macOS 12.6
    CPU: (10) arm64 Apple M1 Max
    Memory: 18.64 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.11.0 - /opt/homebrew/bin/node
    npm: 8.19.2 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 107.0.5304.87
    Safari: 16.0
  npmPackages:
    @vitejs/plugin-react: ^2.2.0 => 2.2.0
    vite: ^3.2.2 => 3.2.2
    vitest: ^0.24.5 => 0.24.5

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

exclude option only affects what Vitest considers a test file, it doesn't affect transforming code. From your description I don't understand what the issue is. Please, provide a runnable reproduction (stackblitz or GitHub).

I'm not sure myself what's the issue here. One test fails when using "react-router-dom" / a node_module.
If a add the same to another code, it stills succeeds.
Need to investigate more here obviously.


[DROOLS-1452] fixes after Maven 3.2.5 -> 3.3.9 upgrade

Depends on https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/pull/401

@mswiderski or @sutaakar could you please quickly review the kie-server changes?

looks ok to me, though would be worth trying this on WAS as I remember there were few issues with guide in there but that might have been related to workbench only.

@mswiderski I am afraid I won't be able to try this on WAS.

@psiroky no worries, I just thought about this and soon we need to try this (kie server) out on all containers anyway so we fix anything related at that time

+1


Adding factories to the app instead

I don't know if this is the right solution but it seems like it could be. I tried to test it, but the demo app's index.html has all of it's code commented out. Why is that?

You know that is a great question .. why is that index.html code commented out?  I have no idea?

It looks like you commented it out here https://github.com/danielspaniel/ember-data-factory-guy/commit/3a15f099ba5e8c712f74e95d89c4156d128c7a04

Just forgot what was going on there? I will fix that

please uncomment that if that helps you test it ..

I am testing your idea now

not working ..

wait .. take that back .. it is in the assets.[appname].js file ..
I think the only thing missing now is to require them because they don't get loaded unless they are required .. which is what factory guy manual setup does .. goes through the files and requires them
so .. wow .. awesome dude .. I think you did that in 10 minutes ? .. amazing

:) I'm glad it did the trick. Do you need anything else?

yes, can you explain about the microstates sometime to me .. me want to understand more about that .. I don't quite get it

Let's do a little screenshare and I'll show you how it works.

let me know when you want to do that


[Docs]:  Fix spelling and grammatical error in the README.md file

what's wrong in the documentation?
I'm in GSSOC'23
We need to add the following;

The word "installed" in the phrase "Make sure you have NodeJs installed in your system" should be "install" to match the action time. The sentence should be "Make sure you install Node.js on your system."
In the sentence "As a user, you have the ability to translate the documentation of this project to new languages," the word "to" should be "into." The sentence should be "As a user, you have the ability to translate the documentation of this project into new languages.
In the sentence "Don't spam if you do it your PR/issue will be closed," the word "it" should be "so" or "then."

Add screenshots
Add screenshots
Code of Conduct

[X] I agree to follow this project's Code of Conduct

it seems like this issue has already been raised before. We kindly request you review the existing issues and, if necessary, create a new one accordingly. https://github.com/priyankarpal/ProjectsHut/issues/654


add meta-data for application model

Thank you!

I think it is best to change MetaData to MetaDatas

🤔
It is very good point and very difficult problem...
metadata is an uncountable noun, so "metadatas" is wrong word.
I propose to make decisions as well as the Android API.
The Android API uses "activities" for an array of an activity, and "metadata" for a set of metadata.

PackageInfo.activities https://developer.android.com/reference/android/content/pm/PackageInfo.html#activities
PackageItemInfo.metaData https://developer.android.com/reference/android/content/pm/PackageItemInfo.html#metaData


About

https://gatsby-starter-breeze.netlify.app/about/
关于 Gatsby Starter Breeze，清风朗月的简单介绍
Gitalk_/about/

hey!


proposal: drop GO386=387 support in Go 1.16

I propose dropping 387 floating-point support and requiring SSE2 support for GOARCH=386 in the native gc compiler for Go 1.16. This would raise the minimum GOARCH=386 requirement to the Intel Pentium 4 (released in 2000) or AMD Opteron/Athlon 64 (released in 2003).
We would need to pre-announce this in the 1.15 release notes. (I've put it in the 1.15 milestone for this reason.)
There are several benefits to doing this:

While 387 support isn’t a huge maintenance burden, it does take time away from performance and feature work and represents a fair amount of latent complexity.
387 support has been a regular source of bugs (#36400, #27516, #22429, #17357, #13923, #12970, #4798, just to name a few).
387 bugs often go undetected for a long time because we don’t have builders that support only 387 (so unsupported instructions can slip in unnoticed).
Raising the minimum requirement to SSE2 would allow us to also assume many other useful architectural features, such as proper memory fences and 128 bit registers, which would simplify the compiler and runtime and allow for much more efficient implementations of core functions like memmove on 386.
We’re exploring switching to a register-based calling convention in Go 1.16, which promises significant performance improvements, but retaining 387 support will definitely complicate this and slow our progress.

The gccgo toolchain will continue to support 387 floating-point, so this remains an option for projects that absolutely must use 387 floating-point.
I proposed this on golang-nuts to get feedback on significant uses of GO386=387, particularly for which using gccgo would not be a viable option.

We should wait a little longer for public comment, but I've gone ahead and prepared the pre-announcement for the release notes. (We could also submit the release notes change and roll it back if necessary.)
Nick Craig-Wood pointed out on golang-nuts that we should make sure GO386=387 fails with a useful error message if we do drop it (rather than, say, starting to ignore the GO386 environment variable entirely).

Perhaps a silly question, but would this affect GOARCH=amd64 at all?

@mvdan, no it would not.

I guess I am the only one who still has such an old computer. Emulated coprocessor support is also still useful for certain embedded systems. I would keep the feature around for a few more years.

It is known that systems still exists that do not support SSE2. I have several too. It would be interesting if there are users of them relying on current versions of Go for more than hobbyist use and if they cant use gccgo.

I've gone ahead and submitted the deprecation notice to the 1.15 release notes. However, this issue is still in proposal review. If it does get declined, we can revert the CL. I've asked for this to get reviewed in next week's proposal review meeting.

This went into the proposal minutes last week, and @aclements mailed it to golang-nuts and golang-dev as well. Let's leave this open another week before moving to likely accept, but there doesn't seem to be much pushback here.

Based on the discussion above, this seems like a likely accept.
So long, 387, and thanks for all the floating-point errors.

One data point: just today somebody asked for 387 binaries in https://github.com/tailscale/tailscale/issues/651
We already cross-compile a number of architectures (https://pkgs.tailscale.com/unstable/#static) and it's easy to add 387 to that list. If we had to use gccgo, though, it's a bit harder. Perhaps add some docs linked from the release notes pointing to gccgo instructions for building static 387 binaries?

To build a static executable with gccgo: go build -compiler=gccgo -gccgoflags=-static.
But note that gccgo executables use the C libraries, so static executables on GNU/Linux systems have some limitations, as glibc generally expects to be dynamically linked.  Specifically not all /etc/nsscache.conf values are supported, unless the dynamic C library is also present at run time.

The most feedback to keep support seems to come from users with AMD Geode GX/LX (the kind with MMX but not SSE or SSE2) boards still used in the embedded space/routers.
Im in favor of dropping 387. As an alternative go1.16 could be made to reinterpret GO386=387 to mean use softfloat support instead of 387 or SSE2 instructions. This would make ordinary go programs on 387 hardware still work, but slower. It would make the register based calling conventions still easier as other platforms (e.g. arm and mips) also require softfloat support. We would also have a mainstream platform for builders to test the softfloat code paths frequently. The upside is that e.g. Athlon XP and Pentium III keep on working and distros dont need to switch away from go gc to gogcc for their package builders for 386 distros supporting old hardware.
For verifying no newer instructionsets are used we could potentially use something like:
https://software.intel.com/content/www/us/en/develop/articles/intel-software-development-emulator.html

No change in consensus, so accepted.

Small question here. What to do with GO386?
Since GO386 was only used to select 387, we can drop it. But should we get rid of it completely, or do we want to keep it around, if only to error out if GO386 is still set to 387. Otherwise, we'd silently generate sse2 binaries when 387 was requested.

I would keep it around to generate the error.
(https://golang.org/design/28221-go2-transitions strongly prefers additions and removals over redefinitions, and ignoring GO386=387 would be a redefinition.)

I agree we should keep it and error out if it's set to anything but sse2 (see also previous comment).

We replaced 387 support with softfloat support GO386=softfloat in CLs 260017 and 260137.
If anyone has a machine without SSE support, please try tip and let us know if it works.
@beoran


[Backend Development with PHP]: Error Handling

Description

Add documentation for Error Handling

Domain
Backend Dev (PHP)
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


rebase: update kubernetes to v1.25.0

update kubernetes to the latest v1.25.0 release.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

/retest ci/centos/k8s-e2e-external-storage/1.22

/retest ci/centos/k8s-e2e-external-storage/1.22

Rook deployment failure

@mergifyio rebase

CI passed :tada:


Docs - How to rotate a secret

I wanted a secret to be regenerated, its dependent templates to be regenerated, and the instance groups updated.
I assumed that I should just delete the secret, and cf-operator would recreate it, and proceed with the steps above. I didn't observe this happening. Then I tried deleting extendedsecret too (once I remembered it existed)
Next I tried re-running helm upgrade but that didn't trigger the process of cf-operator recreating the now missing secret, etc.
What are the steps to replace a missing secret/rotate + regenerate secrets?
Relates to https://cloudfoundry.slack.com/archives/C1BQKKNP4/p1570164123144700?thread_ts=1570095847.136700&cid=C1BQKKNP4 / @viovanov

@andreas-kupries @drnic I was able to rotate the secrets by adding the namespace when running the apply command, which is missing on @drnic article...
steps:
❯ kubectl get secret my-internal-secret -n kubecf -ojsonpath='{.data.password}' | base64 --decode
jILD8xRkbazaf7qQNccvKtNfP5aOHdArMIi1r10NdIKQNoR7Qk7dlhWXNfrbAdQC

❯ kubectl apply -f rotate-my-internal-secret.yaml -n kubecf
configmap/rotate-my-internal-secret created

❯ kubectl get secret my-internal-secret -n kubecf -ojsonpath='{.data.password}' | base64 --decode
1Bzic0BLnYEu4ahffEV7JPMeBpOsPs1bWcWTaLoJZTlLdQybBGtGyaSMa2tNajc6

Oh :bulb: Will verify here and then update the PR. Thanks for your testing and time.

Verified. Adding the -n kubecf to the rotation request makes it trigger properly. Update to docs to come ASAP.


Stack overflow in trap handlers

Why do we need a call to orig_trapHandler here https://github.com/async-profiler/async-profiler/blob/a237cad1150b6b2477d82359c91cc1f1b3486793/src/profiler.cpp#L838?
As I can see trapHandler method is only called from AllocTracer::trapHandler which is installed as orig_trapHandler. I think that it leads to a crash:
crash2050223224811971188.txt.
We use a patched version of the async-profiler built from master https://github.com/async-profiler/async-profiler/commit/d29cb86bd0d663ffe65010c412ee360c67fbb274 (I can share dylib in DM)

Can you reproduce the issue with unmodified async-profiler?
setupSignalHandlers() sets SIGTRAP handler to AllocTracer::trapHandler while storing the previous value in orig_trapHandler. The stack trace from the crash log suggests that setupSignalHandlers() has been called twice. I don't see how this may happen in the original async-profiler code.
An obvious workaround is to check that orig_trapHandler is not equal to (void*)AllocTracer::trapHandler. But I don't want to apply it without knowing the root cause of the issue (why setupSignalHandlers() was called twice).

We don't call setupSignalHandlers() more than async-profiler does. Can it be possibly called from Hooks::init?

We don't call setupSignalHandlers() more than async-profiler does

The problem might be related to anything - even to the way how the libary is compiled/linked. So I kindly ask you to see if the issue occurs with the genuine async-profiler or provide more evidence that it's a bug in the original code.

Can it be possibly called from Hooks::init?

Hooks::init is intended for native applications; it is not normally called in a JVM process.

I see setupSignalHandlers  method is called twice with my dylib. Once from VM init, and once from  Hooks::init. Can I comment out DLLEXPORT methods from hooks.cpp if I'm not interested in native applications profiling?

Thank you for the update. DLLEXPORT functions from hooks.cpp should not be called, unless libasyncProfiler is preloaded using LD_PRELOAD on Linux or DYLD_INSERT_LIBRARIES on macOS.
It's OK to comment them out in your branch, but I'm still wondering why they are called in your case.

Thank you for your help!
The crash happened only a cople of times on some anonymous user machine, so I can't check whether it is reproducible with the original agent

I refactored hooks and setupSignalHandlers in recent commits.
The mentioned issue should not occur anymore.


Add support in parser for YIELD ... WHERE

see:
https://pbs.twimg.com/media/DpOKSJyXcAA1l8g.jpg

Fixed and delivered in plugin v2.5.5.
Should be available for updating soon.


Add Kubernetes Recommended Labels to Istio Helm Charts

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
Kubernetes has a list of recommended labels to be added to resources https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/. It would be great if we can add these labels to all resources in istio helm chart as an improvement on standardization.
The current istio helm charts does not introduce the said labels:

I am happy to submit a PR for this.
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

can be done by helm as well https://preliminary.istio.io/latest/docs/setup/additional-setup/customize-installation-helm/


Windows version built on Mac OS couldn't run properly on windows

nw.js version : 0.30.3
nwjs-builder-phoenix version: 1.46.6
While trying to build a cross platform application, it seems windows version built on Mac OS couln't run  properly on windows. But windwos version built by windows itself was able to run as expected. Is there any special configuration needed to build a working windows version on Mac OS?

you'll want to run it in wine

Thanks you very much for the advice. @conceptualspace


Feature/better layout

Remove a lot of the fluff and make the UI filled with useful information without forcing the user to scroll to get the core information they need to iterate with immersion.

Get ready for demo day


Gzip Error when callig https://store.ui.com/...

Think I got this all setup but running via docker compose and I got a gzip error.
Ubuntu 22.04
Package: docker
Version: 1.5-2

Package: docker-compose-plugin
Version: 2.6.0~ubuntu-jammy

docker images
REPOSITORY           TAG       IMAGE ID       CREATED        SIZE
jakewharton/ui-spy   latest<PHONE_NUMBER>af   3 months ago   45MB

# The product handles (and their optional variant ID) to monitor for availability (required).
#  Value: Array of strings.
products = [
  "camera-g4-instant", "unifi-protect-g3-instant-camera",
]

# URL of IFTTT webhook to trigger for product availability changes (optional). If not specified, the
# tool will only log product availability changes to the console.
#  Value: Valid URL as string.
#  Default: none
ifttt = "https://maker.ifttt.com/trigger/ui-spy/with/key/<snip>"

# Duration between each check (optional).
#  Value: ISO 8601 duration string representing a positive value.
#    See https://en.wikipedia.org/wiki/ISO_8601#Durations.
#  Default: "PT1M" (1 minute)
#checkInterval = "PT5M"

# Base URL of the store (optional). Useful for targeting stores in other geographical markets.
#  Value: Valid URL as string.
#  Default: "https://store.ui.com"
#store = "https://ca.store.ui.com"

# Whether to also notify when a new product is added (optional).
#  Value: boolean
#  Default: false
productAddNotifications = true

docker compose up
[+] Running 1/0
 ⠿ Container ui-spy-ui-spy-1  Created                                                                              0.0s
Attaching to ui-spy-ui-spy-1
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:15 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0x14df6f8b != expected 0x2b650b4b
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:15 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0xb9738743 != expected 0xd4b9039a
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:15 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0xb434ddb9 != expected 0xac56394d
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:15 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0x9a1bf762 != expected 0x5a14547f
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:15 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0x0aaedd04 != expected 0xf9aef994
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:15 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0xd1fd8674 != expected 0xeafd0f47
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:16 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0xe38ec27a != expected 0x97115732
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:16 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0x037f5379 != expected 0x71dcec9a
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |
ui-spy-ui-spy-1  | Aug 10, 2022 1:12:16 AM okhttp3.internal.platform.Platform log
ui-spy-ui-spy-1  | INFO: Callback failure for call to https://store.ui.com/...
ui-spy-ui-spy-1  | java.io.IOException: CRC: actual 0x74675810 != expected 0x50fed5f2
ui-spy-ui-spy-1  | 	at okio.GzipSource.checkEqual(GzipSource.kt:197)
ui-spy-ui-spy-1  | 	at okio.GzipSource.consumeTrailer(GzipSource.kt:164)
ui-spy-ui-spy-1  | 	at okio.GzipSource.read(GzipSource.kt:81)
ui-spy-ui-spy-1  | 	at okio.Buffer.writeAll(Buffer.kt:1642)
ui-spy-ui-spy-1  | 	at okio.RealBufferedSource.readString(RealBufferedSource.kt:95)
ui-spy-ui-spy-1  | 	at okhttp3.ResponseBody.string(ResponseBody.kt:187)
ui-spy-ui-spy-1  | 	at com.jakewharton.uispy.UtilKt$await$2$1.onResponse(util.kt:21)
ui-spy-ui-spy-1  | 	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
ui-spy-ui-spy-1  | 	at java.base/java.lang.Thread.run(Unknown Source)
ui-spy-ui-spy-1  |

Hello! Sorry you're having troubles.
On July 22nd the UI store seems to have switched from using Shopify to something else and they broke this tool. For now you can try one of the following alternative sources of getting notified of product availability:

https://www.reddit.com/r/UbiquitiInStock/
https://discord.gg/ubiquitiinstock
https://uinotify.net/

I haven't decided what I'm going to do with this tool quite yet. I need to figure out the mechanism by which those three alternatives are getting their data and then I could conceivably switch to it. But I just haven't had the time to look.
I'll put a warning on the README for now.

Appreciate the reply!  This all makes sense and if I find some time I'll poke around as well.

Wow that's most unfortunate.  Thank you for the tool though, I just snagged what I needed because of it a few days ago.


Flag a session as "expired" once the edits are applied

If a user applies their edits on the server and tries to use the same editor session to change more perms, it will likely delete perms from their first session.
I think there should be some way to flag an editor session as "expired" or "used" or something, so server admins don't use the same session again, or continue to use the same session to further harm there permission setup.
Possibly attaching a new JSON entry to the stored session data on Bytebin which records the time which the edits were applied (either when the code is generated on the web editor, or when the command is run in game).

Expiring the session will be hard. Only maybe warning that session has been opened a while back.
Though what I think would be better than just expiring sessions is updating the session (ID) so that after saving the changes persist.

I agree to this.
Instead of having the session just "timing out" after the changes where applied, just use the newly generated id and redirect the user to the new editor session, so that they keep their changes.
Does the editor use the same syntax as LP does when posting data to bytebin? This would make it easier since the only thing to do would be to save the changes, let the user copy the changes (or somehow keep it over the reload of the page) and then forward them to the new link.

It's nearly the same. It certainly can be modified so it's the same.


fix(wireless): fix delete button alignment and empty search result ui

Closes AB#2950, AB#2953

Codecov Report

Merging #356 (33c5a53) into master (3047e7a) will decrease coverage by 0.05%.
The diff coverage is 33.33%.

:exclamation: Current head 33c5a53 differs from pull request most recent head 3309114. Consider uploading reports for the commit 3309114 to get more accurate results

@@            Coverage Diff             @@
##           master     #356      +/-   ##
==========================================
- Coverage   55.72%   55.67%   -0.06%
==========================================
  Files          39       39
  Lines         969      970       +1
  Branches       88       89       +1
==========================================
  Hits          540      540
+ Misses        396      395       -1
- Partials       33       35       +2

Impacted Files
Coverage Δ

...rofiles/profile-detail/profile-detail.component.ts
79.84% <33.33%> (-1.41%)
:arrow_down:

src/app/shared/add-device/add-device.component.ts
88.63% <0.00%> (+2.27%)
:arrow_up:

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 3047e7a...3309114. Read the comment docs.


Bloated JavaScript bundler when copying files with file-loader

I use file-loader to copy HTML files generated with an external static generator into my build directory using require.context. This works fine. However when I look at the JavaScript bundle, it contains a lot of bloat. For each copied file it contains a module function like this one:
/* 14 */
/***/ function(module, exports, __webpack_require__) {

    module.exports = __webpack_require__.p + "2014/01/01/dummy-article-01/index.html";

/***/ },

and then another module function with a map containing the URLs of all imported files.
I do not use this code anywhere since file-loader is just the tool to pull the files into the buld directory. Is there a way to prevent webpack from creating these module functions and reduce the bloat in the JavaScript bundle?

I do not use this code anywhere since file-loader is just the tool to pull the files into the buld directory.

In that case, why are you using webpack for that? Why not use cp or some copy tool? webpack is not made for copying files that are not getting referenced in your bundle.

@mdotasia please use solution https://github.com/webpack-contrib/file-loader/issues/85#issuecomment-261513248 to solve this problem, example your can use any copy library or use CopyWebpackPlugin for copying files.
Closing due to inactivity. Feel free to reopen if solution above not suitable as a solution (provide more information or create minimum reproducible test repo). Thanks!


No TPI session - and doesn't seem to reconnect

I'm running version 2.0.1.
It will work fine most of the time, but every now and then I notice it is non-responsive in the Home app. When I look at homebridge logs I see the following when I try to arm/disarm:
[Envisalink-Ademco] Envisakit Module: Command not successful, no TPI session established.
I understand that the connection with my Envisalink system may have been dropped. But I also have it set up to try to reconnect every 30 seconds (heartbeatinterval), so I wouldn't expect it to remain disconnected like this.
Any thoughts on how I can troubleshoot and/or assist with a fix? The network connection to my Envisalink system is wireless but pretty stable (~50ms and < 2% dropped packets).
Thanks in advance!

Hi,
Few questions:

Upon startup does the plug indicate heart beat monitoring has started?
Does your log have any messages indicating missing heartbeats? and successful or unsuccessful reconnect?

If these messages are missing then the plug is not attempting to reconnect.  Make sure the following items are set
"heartbeatInterval": 30,
"autoReconnect": true,
"sessionWatcher": true,

If all of these are set and you still don't see the start message. Put homebridge in debug mode and post the output when the plug-in startup. Be mindfully to remove sensitive data such as your PIN and password.

I have confirmed that the settings you listed are correct.
I also confirmed that the plug-in logs that heartbeat monitoring has started when I restart it:
[24/09/2022, 16:19:59] [Envisalink-Ademco] Starting connection to envisalink module at: <IP_ADDRESS>, port: 4025
[24/09/2022, 16:19:59] [Envisalink-Ademco] Successful TPI session established.
[24/09/2022, 16:19:59] [Envisalink-Ademco] Checking for disconnected session every: 30 seconds.
I then tried unplugging the Envisalink module and I saw this in the logs:
[24/09/2022, 16:24:29] [Envisalink-Ademco] Missing Heartbeat - Time drift:  34.484 . Trying to re-connect session...
[24/09/2022, 16:24:34] [Envisalink-Ademco] Starting connection to envisalink module at: <IP_ADDRESS>, port: 4025
It failed with a connection error but kept trying until I plugged in the Envisalink, and then it re-connected successfully:
[24/09/2022, 16:25:26] [Envisalink-Ademco] Successful TPI session established.
[24/09/2022, 16:25:26] [Envisalink-Ademco] Checking for disconnected session every: 30 seconds.
So the heartbeat and reconnection seems to be working perfectly. However, I checked old logs and there were no indications of a 'missing heartbeat' before the "[Envisalink-Ademco] Envisakit Module: Command not successful, no TPI session established" message.
Does the plugin log when a heartbeat is sent successfully? Perhaps in debug mode? I can wait until this happens again, and then check to see that it was performing the heartbeat every 30 seconds.

Hi,
Interesting.. its seem the logic is working as expected. As far as heartbeat its actually works by monitoring the stream from the Envisalink module.  The alarm panel is continuously sending messages to Envisalink module, in turn the plug-in is continuous listening and processing the events. If it doesn't see anything for during the heartbeat interval it determine something is wrong. With debug on you will see the time drift of check.

I understand. So in my case when I perform a command and it logs this:
[Envisalink-Ademco] Envisakit Module: Command not successful, no TPI session established.
It somehow hasn't noticed that the connection was dropped (i.e. there were no missing heartbeats). I'm guessing this situation is not supposed to happen. Is there anything I can do to help troubleshoot and identify root cause?
I will poke around the source code and see if I can figure it out too.

Correct, it is odd that you're getting this error since the stream should have already timed out and logic to re-connect started. Everything related to connection is in the envisalink.js file. It uses javascript net library for communication.
On another note: I did review the code and found a use case where Homekit was not updating quickly due to a missing connection. I am posting the new code in repo, but will not release until I have more time to make sure nothing broke as result of the fix. It does however fix the hang/long wait when you are trying to arm/disarm in HomeKit when TPI is disconnect  The updates are changes in Envisalink.js and partitionAccessory.js in accessory file. This don't fix root of your issue however as why you have these random disconnect and auto re-connect doesn't work. Report back if you find anything...

I've been running 2.0.2 for a while and this problem has not re-occurred. Thanks!

Great...

This has started happening again. I have all the settings enabled as described here. Periodically, the plugin stops working and I see this log message:
[18/04/2024, 20:48:10] [Envisalink-Ademco] Command not successful. No TPI session establish.
But there is no attempt to re-establish the TPI connection.
If I could make a suggestion (I can also look at the code and see if I can put together a pull request). It seems that if for some reason the session watcher doesn't notice that the connection has been terminated, then the plugin should try to re-establish the TPI connection after it logs this error message.

Hi
The "Command not successful. No TPI session establish" comes from when the plug-in tries executing a command.  The command is being executed?
The error is generic. So,  I posted a new envisalink.js it extends the message to know if the net connection is destroyed or the login isn't completed.
As far as reconnecting during the send command, the easy part is requesting the plug-in to reconnect (if indeed that is an issue) the hard part is retrying logic for the command and not causing homekit to become unresponsive due to trying to reconnect and replay of command.
Monitoring code handles issues of this nature, the fact you do not see any message from that piece of code indicates some unique error case is not handled. Let me know what extend the message returns.

Thanks for the additional details and for posting an update to Envisalink.js. I’ve applied that update, and if/when this condition occurs again I’ll let you know what it says.

On Apr 19, 2024, at 12:10 AM, haywirecoder @.***> wrote:
Hi
The "Command not successful. No TPI session establish" comes from when the plug-in tries executing a command. The command is being executed?
The error is generic. So, I posted a new envisalink.js it extends the message to know if the net connection is destroyed or the login isn't completed.
As far as reconnecting during the send command, the easy part is requesting the plug-in to reconnect (if indeed that is an issue) the hard part is retrying logic for the command and not causing homekit to become unresponsive due to trying to reconnect and replay of command.
Monitoring code handles issues of this nature, the fact you do not see any message from that piece of code indicates some unique error case is not handled. Let me know what extend the message returns.
—
Reply to this email directly, view it on GitHub https://github.com/haywirecoder/homebridge-envisalink-ademco/issues/29#issuecomment-2065717351, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZAELIVBLDUHIYPWI7EJFATY6CKMNAVCNFSM6AAAAAAQUWHJZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRVG4YTOMZVGE.
You are receiving this because you authored the thread.

Hi @haywirecoder - this just occurred again, and I was able to grab the additional logging:
Command not successful. TPI connection status: ${actual.destroyed} and login session connected is: ${this.isConnected}.
Not sure if those variables were supposed to be populated?

Hi,
No that shouldn't have been the output :(  ...  I have uploaded a new version, which will be deployed as part of an upcoming release. The new version is better-tuned re-connect logic now syncing with the send command. I have also reviewed the error message and tested it, so it should tell you that the stream got dropped (network) or that the object associated with Steam is been unallocated (e.g. undefined).  What exactly is the command that is being requested when this appear?

Awesome, thanks!
I patched my install with the updated envisalink.js file. I will let you know if I can reproduce the issue again.
To answer your question - the command is always either disarming or arming the system.

On May 7, 2024, at 12:30 AM, haywirecoder @.***> wrote:
Hi,
No that shouldn't have been the output :( ... I have uploaded a new version, which will be deployed as part of an upcoming release. The new version is better-tuned re-connect logic now syncing with the send command. I have also reviewed the error message and tested it, so it should tell you that the stream got dropped (network) or that the object associated with Steam is been unallocated (e.g. undefined). What exactly is the command that is being requested when this appear?
—
Reply to this email directly, view it on GitHub https://github.com/haywirecoder/homebridge-envisalink-ademco/issues/29#issuecomment-2097424008, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZAELIQWKSVCSPAFTOFQETDZBBKGJAVCNFSM6AAAAAAQUWHJZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXGQZDIMBQHA.
You are receiving this because you authored the thread.

After several months of no issues, the connection stopped working with the following error:
[23/08/2024, 07:02:171 [Envisalink-Ademco] Disarming the alarm system with PIN, [Par tition 1].
[23/08/2024, 07:02:171 [Envisalink-Ademco] Command not successful, connection login session connected is: false and data stream object is defined: true

Hi,
The enhanced error log paid off, knowing now that the connection handler is becoming false.  I made the update Envisalink.js. You are welcome to update your installation with this new Envisalink.js file.  If I am correct, you will receive the following error message. "EnvisaLink server connect closed due to a transmission error" In about 30 sec, you should see the plug-in attempt to reconnect.

Thanks! I copied over the latest envisalink.js, and will let you know if I run into this issue again.

On Aug 24, 2024, at 6:58 PM, haywirecoder @.***> wrote:
Hi,
The enhanced error log paid off, knowing now that the connection handler is becoming false. I made the update Envisalink.js. You are welcome to update your installation with this new Envisalink.js file. If I am correct, you will receive the following error message. "EnvisaLink server connect closed due to a transmission error" In about 30 sec, you should see the plug-in attempt to reconnect.
—
Reply to this email directly, view it on GitHub https://github.com/haywirecoder/homebridge-envisalink-ademco/issues/29#issuecomment-2308565701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZAELIRKBYG7WLWUOZSFRB3ZTEF3FAVCNFSM6AAAAAAQUWHJZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGU3DKNZQGE.
You are receiving this because you authored the thread.

Publish a new release with these updates. Please re-open if you encounter that same issue.


Propagate error messages from API calls to frontend in OAI

References this: https://github.com/grafana/grafana/issues/75501
For streaming responses from OAI, we need to propagate errors to the frontend so that API requests don't fail silently.

From a bit of playing around the only way to do this is to avoid returning an error from RunStream and instead call sender.SendJSON() with an error-like payload, which we'll then need to handle in @grafana/experimental.


Menu not show on mobile

Whats is happening?
Serve
Mobile

I'll close this issue; feel free to re-open it if you need any help. Thanks :)


Rust stable

Hi!
I'm not very familiar with Rust, but very excited by your library. Only my problem is I decided to keep on latest stable Rust.
Is it very difficult to support stable Rust at least lexer part?

Hi! It should be possible, but I'm not currently working on it. I'm not very happy with the current options for stable, so I'm going to wait a little at least.

Hi, what's the status on this issue again?
Also, what rust version are you building on? I just encountered a significant number of errors on cargo build's compilation of plex. I'm on Gentoo's nightly branch of rust.

Hi! I'm pretty busy at the moment, so I haven't been actively keeping up to
date with Rust master. I'd accept a pull request that works against nightly
though ;)
As for stable support... I'd prefer to wait until procedural macros are
properly supported in stable, rather than porting it to the syntex/build
script approach, which I'm not a fan of.
On Jan 26, 2017 11:44, "Saksham Sharma"<EMAIL_ADDRESS>wrote:

Hi, what's the status on this issue again?
Also, what rust version are you building on? I just encountered a
significant number of errors on cargo build's compilation of plex. I'm on
Gentoo's nightly branch of rust.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/goffrie/plex/issues/13#issuecomment-275439970, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABLtTipKPcbN4PkQle3-dGCrHADIcNDoks5rWM17gaJpZM4Kkakb
.

Thanks for the quick reply!
I'm just starting with rust right now, so perhaps this may be beyond me. But I can try.

I'm having a look at this now, too. Mostly it just seems to be renaming and some minor reworks of syntax.

I tried it too. Isn't straightforward, since one function/enum now requires
u128 type, which is unstable, and doesn't compile. At another point, a
function now requires a new argument (Span), which I did not understand. Do
let me know if you can make this work. I need this urgently myself. Thanks
:smile:
On 27-Jan-2017 3:47 pm, "Yuki Izumi"<EMAIL_ADDRESS>wrote:

I'm having a look at this now, too. Mostly it just seems to be renaming
and some minor reworks of syntax.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/goffrie/plex/issues/13#issuecomment-275632604, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJ75pKDInkxgwURfJmD5P1CfbYsAFee-ks5rWcQ5gaJpZM4Kkakb
.

Down to 5 compile errors (from ~50), so I'll let you know if I get there! 😸

Oh, damn. I wasn't working on the latest master. -_- I'll be a little bit more.

Turns out I redid a lot of work. PR incoming.

Great! I'll test it out soon. Although, are you informed enough to be able to port it to stable? (In case you would prefer that as well). There's this library rustlex which works on both. Perhaps something like that can be made for this, if possible? I'm quite new to rust, and low on time, so cannot make that work right now. No hurry though :smile:

Unfortunately not; I'm very advanced at Rust either, and I do think it would be a biiiig effort to port this; better waiting for the features to come to stable (or ideally, target nightly yourself).

I wouldn't target a nightly build I'm afraid. But is it safe to assume (from, for instance, here ) that macros 1.1 should be in stable within a week or two? That's what is holding back plex from building on stable, right?

Has anybody built successfully with a stable version compiler?

Has anybody built successfully with a stable version compiler?

As long as the procedural macros aren't stabilized yet, I don't think you can build this crate with stable (or even beta).
See this issue for more info: https://github.com/rust-lang/rust/issues/54725

I see that rust-lang/rust#54725 is still in nightly and under active development to this day. Since the last activity in this repository was in 2020, I wanted to ask if the maintainers are still looking to update this crate once this feature is on rust stable?

I ported the crate to use syn 2.0.0 and compile_error!-style error reporting (using syn::Error) in fafa4dcdbd51dd4f0c7fba58109842a0481fd05d. With that, the crate now compiles on stable.

Thank you! 😊

Would it be possible to make a new release with this feature? Would be great if I can build my project with the latest version of the crate without needing to compile from source. Thank you :)

@maxrdz v0.3 was just released!

Sweet, thanks for letting me know!On Oct 28, 2023, at 4:57 AM, Erik Bjäreholt @.***> wrote:
@maxrdz v0.3 was just released!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Does this works for Xamarin.iOS and Xamarin.Android

Hi,
I have a requirement of making Xamarin.Android and Xamarin.iOS projects. (No Xamarin Forms). Does this library works with them as well?
Asking this question because other MVVM libraries do kind of work with them. I don't know the internals so thought of asking.
PS: Please feel free to close this issue. As this is kind of out of scope as per read me. But still if Gjallarhorn binding works it would be great. I will end up with some better MVVM library.

Dunno, I'm not aware how Xamarin.iOS/Xamarin.Android works. Maybe easiest way to find out is try to port demo from sample folder and see what happens?


[release-1.18] Wildcard Disambiguration

Please provide a description of this PR:
Backporting #48071, #48330, and #48361 to 1.18. Fixes #48558

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test lint

gencheck_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test lint

gencheck_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test gencheck

unit-tests-arm64_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test lint

gencheck_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test gencheck

unit-tests-arm64_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test unit-tests-arm64

unit-tests_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test lint

gencheck_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test gencheck

unit-tests_istio_release-1.18
479bfb4e83914592778d61722429ec86422f9b5a
link
true
/test unit-tests

unit-tests-arm64_istio_release-1.18
e6ae50b64a5bfcb6d24c4a544264a084f89622ad
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.18
e6ae50b64a5bfcb6d24c4a544264a084f89622ad
link
true
/test unit-tests-arm64

unit-tests_istio_release-1.18
e6ae50b64a5bfcb6d24c4a544264a084f89622ad
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Looks like I also needed to cherry-pick #45715 and #45740 to fix the race detector

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.18
e6ae50b64a5bfcb6d24c4a544264a084f89622ad
link
true
/test unit-tests-arm64

unit-tests_istio_release-1.18
e6ae50b64a5bfcb6d24c4a544264a084f89622ad
link
true
/test unit-tests

lint_istio_release-1.18
0bcf3d5eb41184245048d9fa960d34aaa43767f0
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


add translation for terraform ydb doc

add translation for terraform ydb doc
...

Documentation
...

incorrectly merged :(
will re-open a new one

superseded by #4062


Port from rs-wnfs

Licensing test is failing — will look at it in the morning

Licensing test is failing — will look at it in the morning

just needs BSD-2-Clause and BSL-1.0 added to the list of licenses. I didn't want to make all the opines in the template.

Ah, clippy is unhappy about some stuff in the test utils. I'll look tomorrow; I have a flight so I have to get up relatively early

Licensing test is failing — will look at it in the morning

just needs BSD-2-Clause and BSL-1.0 added to the list of licenses. I didn't want to make all the opines in the template.

oh, derp, and CC0-1.0 :).

Oh also I wasn't really sure what to wrap for Wasm. I can serialize the filter, but that seems wasteful in the normal case 🤷♀ I think I want to do some stuff with WasmRefCells, but that seems like a "not this instant" thing.

Oh also I wasn't really sure what to wrap for Wasm. I can serialize the filter, but that seems wasteful in the normal case woman_shrugging I think I want to do some stuff with WasmRefCells, but that seems like a "not this instant" thing. Thoughts?

I'm thinking the most efficient way will be to expose it as Rc<BloomFilter<...>> and in some way make it so that it's available as a Uint8Array on the JS side. This would allow the Uint8Array to not be copied into the JS side, but instead the JS side would just have something that points into Wasm memory.
The Rc + something like wasm-bindgen's --weak-refs feature is how I imagine figuring out when repurposing the memory on the rust side is safe. I'm not 100% sure how that'd work.

do you think we'll want more in-between variations for wasm?

We'll probably want a runtime-dynamic version for Wasm, honestly.
The const-based version is good for doing benchmarks & WNFS, but it's not good for e.g. CAR mirror.

@walkah no reason besides it's missing a review :man_shrugging:

@walkah It's like I'm reviewing my own code haha
I'll just go ahead and merge


[ui-bootstrap] upgrade to v1.0.0

Since UI Bootstrap 1.0 and higher requires Angular 1.4.x, this is dependent on #567

Fixed by #947

nice :)


Move to pcre2

coda was removed from Debian testing because it depends on the end-of-life PCRE library.
The newer PCRE2 library (the official successor to PCRE) was first released in 2015.
Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/
Please consider updating to PCRE2.

Sounds like a good idea. We will investigate.

This was implemented in CODA V2.25.


Error in startRGB

I had the following error after running the launch file:
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::math::rounding_error> >'
   what():  Error in function boost::math::round<d>(d): Value -inf can not be represented in the target integer type.
[head/kinect2/startRGB-1] process has died [pid 31638, exit code -6, cmd /home/spelle/ros_ws/devel/lib/k2_client/startRGB __name:=startRGB __log:=/home/spelle/.ros/log/7ee2fe14-8308-11e5-9fa5-782bcb9a79bf/head-kinect2-startRGB-1.log].

Hmm, could you see if any of the bugfixes from here:
https://github.com/personalrobotics/k2_client/pull/4/files#diff-e013eb24c00c2d58a8603f1477f73c96R62
are helpful?

Yes! They worked out. Thanks

Excellent! Can you make another PR with the changes you needed to make it work when you get a chance?  Thanks very much.

No changes. startRGB is working as it is now in:
https://github.com/personalrobotics/k2_client/pull/4/files#diff-e013eb24c00c2d58a8603f1477f73c96R62.
I guess the first time I probably used a code you had partially changed respect to final version (I compiled but the code was partially different). Thanks

Hi! I'm having the same error as @stepelle mentioned at the beginning of this thread. I'm using the latest files in repository.

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorboost::math::rounding_error >' what():  Error in function boost::math::round(d): Value -inf can not be represented in the target integer type.
[head/kinect2/startRGB-1] process has died [pid 25939, exit code -6, cmd /home/vdl/catkin_ws/devel/lib/k2_client/startRGB __name:=startRGB __log:=/home/vdl/.ros/log/b26a505a-8e59-11e5-912c-002314598558/head-kinect2-startRGB-1.log].
log file: /home/vdl/.ros/log/b26a505a-8e59-11e5-912c-002314598558/head-kinect2-startRGB-1*.log

Any ideas why the error happens?


bump the azblob from 0.3.0 to 0.4.0

Pull Request Description
[Add a description of your pull request here]

Future Release Comment
[Add description of your change, to include in the next release]
[Delete any or all irrelevant sections, e.g. if your change does not warrant a release comment at all]
Breaking Changes:

None

Features:

None

Fixes:

None

@AsafMah could you please help take a look? thanks.

Closing - obsolete with 0.10.0


Question about scrollIntoView()

Why don't you use the native Element.scrollIntoView()
https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView

Optiscroll scrollIntoView implementation adds behaviours that are missing in the native implementation. For instance, the native  scrollIntoView does not allow you to animate the scrolling (same limitation applies for the native scrollTo).
As you are pointing out, now finally something has started to change. There is a working draft specification for scrollIntoViewOptions argument and it has been implemented in Firefox 36.
It is a good starting point and, eventually, we will align scrollIntoView method with the new specification (and using the native implementation if feature detection will be possible).

Okay, thank you for pointing this out.


Prom-Migrator - prometheus migration from centos to Ubuntu

prometheus migration from centos to Ubuntu
1.prometheus version :2.29.1
2.alertmanger 0.23.0
3. we are using prometheus-postgres-adapter and timescale DB.
how can migrate TSDB old promethues to new prometheus TSDB

Hello, if you want to migrate to new prometheus instance in Ubuntu, just point the write-url to prometheus/api/v1/write and keep the max-read-duration low, maybe 1 minute. This is because I recall that when I was testing migrating to Prometheus, anything larger than 1 minute block makes Prometheus error out, because Prometheus wasn't meant to be written into.
However, if you want to migrate data to Promscale, then you don't need any limit on max-read-duration.
BTW, can you share why you are using prometheus-postgres-adapter. The project is no longer maintained and instead, we recommend to use Promscale.

@prashantnitt07 Does the above info answer your question? If yes, can you please close this issue?


New transformer: concat(<item1>, <item2>, ...)

Motivation
Please look at this comment for context.
The concat(<item1>, <item2>, ...) transformer concatenates items (either a field or a literal string) given as arguments and returns a new string.
Its output can be utilized in two primary ways:

In conditions for filtering.
In the output: field of Falco's rule.

One significant use case is concat(fd.rip, ":", fd.rport]) in ("<IP_ADDRESS>:53","<IP_ADDRESS>:53") as reported by https://github.com/falcosecurity/libs/issues/1981
Feature
Implement the concat(<item1>, <item2>, ...) as described above.
The transformer should return a concatenated string.
Note: Implementing this transformer requires extending the current syntax to allow a variable number of arguments to be accepted by a transformer.
Alternatives
Please look at https://github.com/falcosecurity/libs/issues/1981 for more context on the evaluated alternatives.

/assign


Eq. for EulerianPT calculator

This implements comparison between PT calculators beyond id.
The tracers seem to me to be complicated enough that the only practical and safe comparison is via id equality.

OK, done (although it seems a bit silly, since this is effectively a slower way of just checking ids atm)


Colors are sticky

When scrolling down the page the background colors are sticky.  They do not scroll with the content, they hover the page.

Hi @cbstodd, this package have been replaced by pigments. It's the same features (and more) but with better performances and integrated with project-palette-finder.


fix: prevent unexpected spy callback removal on multiple unmount calls

Problem:
Multiple scrollSpy.unmount() calls may occur on same Link due to component tree rebuild. Subsequent calls will try to remove already non-existing spyHandler. In this case .indexOf(spyHandler) will return -1 and .splice(-1, 1) will cause unwanted removal of last spyHandler in list.
Solution
Add extra check to make sure spyHandler is in list

Let's do this!

Thanks for the PR, merged :)


Trying again

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


[STRMCMP-860] Fix thread cancelation timeout problems

This attempts to fix the hanging task thread. Two possible scenarios:
(1) cancelTask() can be called from multiple locations. At least one of the
locations does not perform proper exception handling. Once a task is in the
CANCELING state and the cancelation timeout thread has not been started, the
task will linger forever.
(2) taskCancellationTimeout was non-volatile and is non-final which
theoretically could lead to a thread calling cancelTask() to read an outdated
value. It is first initialized with 0 which would disable the cancelation. The
value is written in the constructor which makes it unlikely but not impossible
to read the initial value:
https://stackoverflow.com/questions/33485625/non-volatile-fields-first-object-access-from-another-thread-java
We bring up the thread as soon as possible to avoid any problems running
it. Also we exit in case the thread fails to start.

CC @tweise I'm deploying a new Flink 1.8 version with this.


Throw the book at em! The space law book now does 1 blunt projectile damage

About the PR
added one projectile damage to the space law book, so you can literally throw the book at someone in addition to just hitting people with it.
Why / Balance
Funny, and it already does one blunt, just not as a projectile, so I felt like it was a missed opportunity
Media
Requirements

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

tweak: The Space Law book now does one blunt damage when thrown as a projectile, allowing you to throw the book at inmates.

I did not mean to submit this as a draft lmao

This is amazing. Can projectiles that don't embed hit multiple people? Lining up 5 security officers to prepare them for the shift with this book would be amazing.

just make all books do this?

This is amazing. Can projectiles that don't embed hit multiple people? Lining up 5 security officers to prepare them for the shift with this book would be amazing.

yea, you can infact line up targets and hit them, I saw this while testing.

just make all books do this?

Well not all books have blunt damage, just the law book. I don't think it would make sense to make all books have projectile damage when this was already the only one to do damage in the first place

just make all books do this?

Brought this up for maintainer discussion and this is preferred for consistency reasons.

law book does... 2 damage (heavy) :godo:

it does 1 damage, it's just that now it also does damage when thrown and not just when punched with.


Create standalone cython runtime module package

https://github.com/cython/cython/issues/1981
Package is named Cython_shadow. That can probably be changed.
It doesn't attempt to deal with any versioning issues.
It also doesn't do any testing. That'd probably be a case of adding a ci run that makes and installs the wheel and then imports a few example pure-Python modules.
Not sure what else I'm missing.

I'm created this as a draft because 1) I'm not completely sure this is a good idea, and 2) it's missing any kind of testing

it's missing any kind of testing

Shadow file is already tested in: Cython/Tests/TestShadow.py. Do we need additional tests since this PR is adding just symbolic links?

Do we need additional tests since this PR is adding just symbolic links?

Probably just that the wheel does provide the imports that I think it does. So not a huge amount of testing, but a little bit


Begin Focus vs Mouse mode

Add a setSelectionMode with an enum for current FOLLOWS_MOUSE or FOLLOWS_FOCUS
Unregister / register appropriate focus listener, structure for other options
Add the listener to update state

With this plus inspectr->setFocusMode called explicitly on launch melatonin is equivalent to the surge focus debugger. Awesome.
The primary thing not done yet is a toggle button in teh UI to swap modes. You can only swap programatically.
Addresses #97

The reason I didn't do a button is I couldn't figure out how to make assets etc... so I figured add a function and then perhaps if you decide to merge this, you could help with that part?

Woo!
Yeah, adding assets is described here, but it's a brittle pain in the butt.
Also I care about the icon / will need a minute to cook one up...

Great. We can also merge as a two step. Have this function version (and I can add a menu I surge in the interim) and a button once you have time. If the function looks correct of course

Thanks for the patience! I have a policy to check things out locally and make sure I understand them before merging (otherwise I tend to get into trouble post-merge being like "wait, how did that get here!"). I had to add a bit more rudimentary accessibility in my own app to check this one out. Also, I tried yesterday but changing the default to FOLLOW_FOCUS didn't work (as the function needs to be called somewhere).
Merging now and will follow up with toggle and icon.
This is maybe also worth storing in settings->props so that while iterating on an app the mode persists.


Blank js files throw "Invalid Source" Error

Blank js files throw "Invalid Source" Error
Running "complexity:src" (complexity) task

Warning: Invalid source Use --force to continue.
Error: Invalid source
    . . .

Aborted due to warnings.

I think it would probably be better to either omit/ignore the error created by empty files and just skip over them in the source array (As I think it would be better not to halt the process because of this), or provide a better error message saying "Empty files cannot be analysed". Invalid source is a bit misleading in this regard, in my opinion.
Thanks in advance!

I agree.

Merged a fix to make the error message better. Seems like the next step would be to ignore empty files. What do you think?
In the mean time, https://github.com/vigetlabs/grunt-complexity/pull/37/commits/91dc55fa05eea28e78acac2882867c79cc21abc5 should eliminate the confusion.
https://github.com/vigetlabs/grunt-complexity/releases/tag/v0.4.0


fixed errors in module-02

What does this PR do? and how can I test it?

Rodrigo from SmartPy team mentioned that there were issues with module-02. This PR fixes them.
To test it, you can go through module-02.


fix eslint warnings

would be nice to fix or eslint-ignore the linting warnings that appear when you yarn start

will take a stab at this

edit this looks like this is actually a semiotic issue https://github.com/emeeks/semiotic/issues/210


str_replace('.','_',$str) crashes metric

In my case the metric is named "icinga2.max.services.PSU-Load.snmp.perfdata.FSC-SERVERCONTROL2-MIB.sc2psPowerSupplyLoad.1.1.value".
But the function "escapeMetric" converts it to "icinga2.max.services.PSU-Load.snmp.perfdata.FSC-SERVERCONTROL2-MIB.sc2psPowerSupplyLoad_1_1.value" which results in an "NoData"-Graph.
Is it my fault or can you fix it?

Ah it looks like the graphite writer escapes dots (.) in the prefix part of the target name but not the metric part. Of course this module needs to follow suit.

fixed with c4082b09a2aa00f1de74ea04f763c3e5334d223f

Well done. Thank you!


Fixes bug when pausing in fullscreen (iOS)

Similar to #153, attempts to pause in fullscreen mode will be negated by the playbackLikelyToKeepUp event.
This PR adds a check for _fullscreenPlayerPresented, in addition to _controls, before calling setPaused for playbackLikelytoKeepUp.
This update is likely preferrable to #258, as it doesn't lose the empty buffer check.

@mattapperson

@mcrumm Sorry I was sick for a few days so I missed this... reviewing now...

Thanks for merging - I hope you're feeling better!


Create "My Profile" page for people who are logged in

"My Profile" only shows up for people who are logged in

For faculty and students, this could house their profile or option to create a profile. For students, this could additionally include a "toolkit" for signing up to mentor other students and what that would mean.


Implement loading of settings from database

Get settings loaded from database and filling in to HomeController.cs
Ensure this is the only place these settings get into a view/HTML (from HomeController)
Depends on tasks #25 and #26

Is this related to the DI work we did on PR #35 with settings passed through to the controller as a service?

@JamesEarle Yea, it's related. This one will be DB implementation specific so we may change in the future how we do this (consider DI or not DI). The current implementation is config file driven and uses the DI and IOptions so its setup for us, this task will need to load from db, possibly just from repository or cache. We'll investigate if we'll use DI or not at that time.

Will this be ready to close with the merging of #145 ?

I know this is dependent on the DB work, but the DI work setting up IOptions in Startup.cs has been done for a while. We can leave this open as a reminder to discuss the alternate options (from db, etc) next week. @adamtuliper

Find out if DB stores any application settings or if it's all config based.

The DB stores application settings in a table, looks like they are configured in ISettingsManager and SettingsManager in legacy code and then injected in the startup class

We need to decide if we want to use this setup or not. Currently all settings are config based, but this could just be the setup for app settings and then user settings could be stored in the DB.

Moving to backlog because of time left for 0.6. Can be revisited after. We should ideally have app settings from a database and app configuration in the json file though if we eventually have a UI to change these (from an admin standpoint) then we can have all DB changes.


cardano-wallet-shelley-linux64

I am using cardano-wallet-shelley-latest-release on Linux for a wallet service. when I start with './cardano-wallet serve'
it hits "Missing: --node-socket FILE --testnet FILE", where could I find these two files of mainnet? ; is it impossible to connect the mainet yet??

i get a mainnet file from "https://hydra.iohk.io/build/3175192/download/1/mainnet-genesis.json";
and the log shows this file is not JSON valid ??????/
what should I do to run Cardano-wallet on mainnet

For current mainnet, you'll need cardano-wallet-byron unfortunately. The transition to Shelley will happen soon but hasn't happened yet. The genesis file looks indeed correct for the current Mainnet chain.
For further details, please follow the instructions in the command-line manual: https://github.com/input-output-hk/cardano-wallet/wiki/Wallet-command-line-interface-cardano-node#serve

when I run with file "https://hydra.iohk.io/build/3175192/download/1/mainnet-genesis.json";
the log shows 'You may want to check the filepath given via --genesis and make sure it points to a valid JSON genesis file. Here's (perhaps) some helpful hint: Error in $: key "maxMajorPV" not found'
and indeed for key "maxMajorPV" is not exist in the "mainnet-genesis.json"

maxMajorPV is a parameter required by the Shelley node. Please re-read my previous answer, you need cardano-wallet-byron, not cardano-wallet-shelley.


OSError: [Errno 30] Read-only file system: '/workspace/single_stage_detector/ssd.log'

Hi, Am running MLperf. While using docker directly, entire set up runs with the same container. When I use enroot+pyxis, the content inside the container becomes Readonly. I tried to change permission of the folder inside the container and following issue occurs. Can you please help me sort this out?
srun --nodes=1 --ntasks=1 --container-name=single_stage_detector --container-remap-root bash -c ' chmod 0777          /workspace/single_stage_detector/*'
chmod: changing permissions of '/workspace/single_stage_detector/Dockerfile': Read-only file system
chmod: changing permissions of '/workspace/single_stage_detector/README.md': Read-only file system
chmod: changing permissions of '/workspace/single_stage_detector/async_evaluator.py': Read-only file system
chmod: changing permissions of '/workspace/single_stage_detector/bind.sh': Read-only file system
chmod: changing permissions of '/workspace/single_stage_detector/bind_launch.py': Read-only file system
chmod: changing permissions of '/workspace/single_stage_detector/box_coder.py': Read-only file system
chmod: changing permissions of '/workspace/single_stage_detector/config_DGX1.sh': Read-only file system
chmod: changing permissions of '/workspace/single_stage_detector/config_DGX2.sh': Read-only file system

What do you have in your /etc/enroot/enroot.conf? You need to set ENROOT_ROOTFS_WRITABLE y as the default is no (read-only container filesystem).
You might also want to take a look at the pyxis wiki:
https://github.com/NVIDIA/pyxis/wiki/Setup#enroot-configuration-example

I faced a similar issue, I assume you installed something inside the container using '--root'.
When using a standard user, could you try '--rw' ?


Put concept (Arguments / ArgumentsMatcher) into words and ask for help

Requirements:

Must work with references to generics (See #123).
More?

Upon further research and bodging around, I think we should be able to implement #123 with GATs (Generic Associated Types) however this is not yet implemented in the compiler 😞


Fix the array out of bounds while getting offsets

We meet this problem while running with gluten, and we found that the array was out of bounds while getting the last offset. The length of the offsets is length+1, thus the last index should be length instead of length+1. As for the unit tests, they are running normally because it use offset to read data and won't check whether has too many data in stringViewBuffers.

cc @zhztheplayer @zhouyuan

Thanks @jackylee-ch for raising the issue.
As you mentioned

The length of the offsets is length+1, thus the last index should be length instead of length+1

IIUC offsets[length + 1] was treated as "the last index" to pass to WrapInBufferViewFunc, is that correct?
However when I looked into the definition of WrapInBufferViewFunc
using WrapInBufferViewFunc =
    std::function<BufferPtr(const void* buffer, size_t length)>;

The second parameter is supposed to be "length" rather than "last index". Am I missing something here?

@jackylee-ch can you please do a rebase?
-yuan

@jackylee-ch can you please do a rebase?

@zhouyuan done


Link or URL is not visible and accessible when added to website project page

On website's project pages, when you add a link to a website, it shows up as this inscrutable purple button with a Win95 mouse pointer, any way we can change that to something more noticeable, like the actual link?
Example: https://www.opentech.fund/results/supported-projects/seaglass-imsi-catcher-detection-latin-america/

@fourthletter The Purple arrow icon is not that clear to me either. I would suggest a purple button that say "Homepage", "WWW" or something like that.
What do  @ei8fdb and @bumbleblue think?

I think nothing should be there since a link/url is already provided below the description. Another option is if the user can select the icon or image they prefer.

@fourthletter If you don't want a link to show up then just delete it. But the point of having the contact details in a separate field is that they will show up the same for all projects, consistency.
My suggestion is to delete the link at the end of the body and then we make the url look a way that you like in the contact details section.
https://apply.opentech.fund/admin/pages/802/edit/

The purple arrow is misleading and the heading title "Get the word out" does not indicate that the purple arrow will take you the project's website. The public is consistently confuse by this UI.

@fourthletter Then let the designers redesign it so it becomes good.


Obsolete GO:0000903 regulation of cell shape during vegetative growth phase (was: "phase" branch term has an "annotatable" descendant.)

I notice that a "phase" branch term has a  "annotatable" descendant.
GO:0000903    regulation of cell shape during vegetative growth phase
This branch was supposed to be disjoint  from the rest of the ontology (confusingly it is a separate aspect describing when things occur).
This is  also odd because it has a
part_of relation to the phase. This is not correct, the relationship to "vegetative growth phase" is "happens_during"
Maybe logical defs need fixing?
I'm not really sure why the term is required. The parent with a happens_during extension would be correct would'nt it?
Annotations
PomBase 1
SGD 2

Hi @ValWood
I changed the logical definition to have "happens_during" rather than "part_of". Let me know if this addresses the issue or if you want to propose obsoletion.

Please reopen if needed. Thanks, Pascale

I would rather obsolete to be consistent and always do phases with extensions...
@cmungall ?
It might be helpful to maintain this disjointly in case it is ever  decided to move the branch out of GO... but more it just seems like a natural place to always post compost to me...

Another reason, that I just thought of, since we already have a lot of phase specific data, we are implementing "phase" filtering over all of our GO data. This is much easier to do if the phases are neatly in extensions.
https://github.com/pombase/website/issues/877

Dear all,
The proposal has been made to obsolete GO:0000903 regulation of cell shape during vegetative growth phase. The reason for obsoletion is that the
There are 3 experimental annotations to this term by SGD (2 EXP) and PomBase (1 EXP).
There are no InterPro2GO mappings to this term and the term is not in any subsets.
Any comments can be added to the issue: https://github.com/geneontology/go-ontology/issues/16285
We are opening a comment period for this proposed obsoletion. We’d like to proceed and obsolete this term on September 4th, 2018. Unless objections are received by September 4th, 2018, we will assume that you agree to this change.
Thanks, Pascale

@srengel

i have changed the SGD annotations to regulation of cell shape GO:0008360 w/col16 happens_during(GO:0072690) single-celled organism vegetative growth phase