Bad error message for assigning empty array to tuple type

Reported in the IRC channel against 1.7.5. Still exists in 1.8.0-dev.20160117
var x: [number] = [];

foo.ts(1,5): error TS2322: Type 'undefined[]' is not assignable to type '[number]'.
  Property '0' is missing in type 'undefined[]'.

I guess undefined comes from the fact that the RHS array is empty, so its element type is left uninitialized. Maybe you want to detect that and have a different error message? "An empty array is not assignable to type [number]." or something.

@sandersn @DanielRosenwasser would this be fixed by the proposed contextual typing changes?

If I understand things correctly, you should get number[] with Nathan's changes.
Even if you didn't, I think I've concluded on several occasions with @JsonFreeman and @CyrusNajmabadi that surfacing the undefined  type in error messages is not a problem.

Even if you didn't, I think I've concluded on several occasions with @JsonFreeman and @CyrusNajmabadi that surfacing the undefined type in error messages is not a problem.

You don't think it gives the impression of being a compiler bug?

That's what I argued at the time because it totally looks like we screwed up somehow. The fact that we're surfacing the undefined type isn't a problem so much as it is that its representation kinda, well, sucks. :smile:

I checked, looks like the error with the change in #6118 is still the same.

Is there such thing as a tuple of length 0? It seems like the error ought to say something like

type [] is not assignable to type [number]

where [] is the tuple of length 0. But I guess a tuple of length 0 is really the same as undefined[] anyway, so maybe there is no point in having that concept.
This is not to say that the type undefined should never be surfaced in an error message. That is a separate discussion. I think the better question is not about undefined, but about how to improve error messages about tuple types. I think that while technically, a tuple type acts as an object with numeric properties, perhaps the error should talk about the "size / length" of the tuple. I think that would be more intuitive for users.

Is this still a bug given that the null and undefined types are going to be representable in 2.0?

foo.ts:
var x = [];

tsc -d -t es5 foo.ts
foo.d.ts:
declare var x: any[];

foo.ts:
var x: [number] = [];

tsc -t es5 foo.ts
foo.ts(1,5): error TS2322: Type 'undefined[]' is not assignable to type '[number]'.
  Property '0' is missing in type 'undefined[]'.

There's no difference with --strictNullChecks

So is an empty array any[] or undefined[] ? Should it be undefined[] even if --strictNullChecks isn't passed in?

For the tuple case, it doesn't really matter what the element type is. The array literal is required to have an element at index 0 because of the contextual type, but it does not.
For the other case, if the array did not get widened to any[], I don't think you would be able to subsequently add elements to it, which would be very limiting.
Both of these ideas are independent of strict null checking. That said, I still think it would be reasonable to have tuples of length 0, and then the message would talk about the type [] as the empty tuple type.

We have empty tuples now, and the new message is
Property '0' is missing in type '[]' but required in type '[number]'.


update makefile for automation of local setup

What this PR does / why we need it:
for smoother working of local setup automation.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Thank you @Mkmittal for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.


Typescript changes

Changed TypeScript declarations to support any component type as argument for the styled function #64. What also includes in this PR is the optional argument for the StyletronClient constructor #59 and a hack to enable autocompletion for CSS properties as object.

Also added a generic styled<TElement, TProps> with base as string for the ability to manually type when you have e.g. base as a variable.
type PropType = {
  bold: boolean;
}

function factory<TElement extends HTMLElement>(base: string, color: string) {
  return styled<TElement, PropType>(base, props => ({
    color,
    fontWeight: props.bold ? 'bold' : 'normal',
  }));
}

const RedDiv = factory<HTMLDivElement>('div', 'red');
const GreenSpan = factory<HTMLSpanElement>('span', 'green');

LGTM, thanks!


Memory Leak Issue

I just want to inform that I am countering with Memory leak issue.
I am not 100% sure that It comes from catalyst. But I am sure that when I use my own code written by myself (without catalyst), there is no leaking issue. I tried to pre-procedure this issue from your examples, but it runs very fast and we could not see the leak.
Following is my leak descriptions:

Image classification task with ~17M images

The memory leak occurs every epoch and it happens at the next epoch again.
EX:
At the beginning of epoch 0, my memory is:

RAM: 13G/16G
Swap: 0/50G

At the end of epoch 0, my memory is:

RAM: 16G/16G
Swap: 25G/50G

When epoch 0 ends, the memories (RAM + Swap) are released, (RAM: 13G/16G, SwapL: 0/50G). The same phenomena occurs at the next epoch 1.

I am debugging to see where the issue comes from. Could you please double check with your bigger data?

Updated:

Train with bigger data by using finetune
I downloaded dogscats dataset from fastai and tried to run finetune from your examples. There is no leak issue during training one epoch
It seems that the leak comes from my code

Debug my code
I am able to figure out where the leak comes from. It occurs at my custom dataset.

    def __getitem__(self, idx):

        # Get token
        token = self.tokens[idx]

        # Get drawing
        drawing = self.drawings[idx]
        stroke = stroke_data(drawing).astype(np.float32)
        # stroke = np.expand_dims(stroke, axis=0)
        stroke = np.transpose(stroke, (1, 0)).astype(np.float32)

        drawing = eval(drawing)
        label = self.labels[idx]

        # Plot the image
        img, img_gray = drawing_to_image(drawing, IMG_SIZE, IMG_SIZE)

        if self.transform:
            img = self.transform(image=img)["image"]
            img = np.transpose(img, (2, 0, 1)).astype(np.float32)
            # img = np.expand_dims(img, 0).astype(np.float32)

            img_gray = self.transform(image=img_gray)["image"]
            img_gray = np.expand_dims(img_gray, 0).astype(np.float32)

        return {
            "image": img,
            "image_gray": img_gray,
            "stroke": stroke,
            "token": token,
            "targets": label
        }

The interesting is, when I change the code from
drawing = self.drawings[idx]

to
drawing = self.drawings[0]

There is no more memory leak. I could not explain why because I still use this function on my own code written by myself and there is no leak.
Do you have any idea?

Hi,
First of all, are you sure it's a leak, not just memory fragmentation
and not too-eager Dataloader piling up a lot of data at the GPU to be
processed later?
A usual advice to distinguish between the two first is to add
gc.collect() + torch.cuda.empty_cache()
and check if it helped.
For the last two, an idea is to reduce the number of worker threads
and see if that helps.
On Sun, Nov 4, 2018 at 6:04 PM Nguyen Xuan Bac<EMAIL_ADDRESS>wrote:

Updated:
Train with bigger data by using finetune
I downloaded dogscats dataset from fastai and tried to run finetune from your examples. There is no leak issue during training one epoch
It seems that the leak comes from my code
Debug my code
I am able to figure out where the leak comes from. It occurs at my custom dataset.
def __getitem__(self, idx):

    # Get token
    token = self.tokens[idx]

    # Get drawing
    drawing = self.drawings[idx]
    stroke = stroke_data(drawing).astype(np.float32)
    # stroke = np.expand_dims(stroke, axis=0)
    stroke = np.transpose(stroke, (1, 0)).astype(np.float32)

    drawing = eval(drawing)
    label = self.labels[idx]

    # Plot the image
    img, img_gray = drawing_to_image(drawing, IMG_SIZE, IMG_SIZE)

    if self.transform:
        img = self.transform(image=img)["image"]
        img = np.transpose(img, (2, 0, 1)).astype(np.float32)
        # img = np.expand_dims(img, 0).astype(np.float32)

        img_gray = self.transform(image=img_gray)["image"]
        img_gray = np.expand_dims(img_gray, 0).astype(np.float32)

    return {
        "image": img,
        "image_gray": img_gray,
        "stroke": stroke,
        "token": token,
        "targets": label
    }

The interesting is, when I change the code from
drawing = self.drawings[idx]
to
drawing = self.drawings[0]
There is no more memory leak. I could not explain why because I still use this function on my own code written by myself and there is no leak.
Do you have any idea?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

--
Best regards, Yuri V. Baburov, Skype: yuri.baburov

Hi,
Thank for your suggestion.

For the last two, an idea is to reduce the number of worker threads
and see if that helps.

You are right. When I reduced the number of worker threads to 0. It helped. What is the problem here?
Is there any better solution? Because running with workers=0 is very slow.

Try decreasing batch size then.

Hi,
Sorry, I was out of time during last week.
I am not sure, but you can try things like:

something like drawing = self.drawings[idx].copy()
stop pinning memory in PyTorch DataLoader
play with n_workers and batch_size parameters
check @buriy idea and add gc.collect() + torch.cuda.empty_cache() after the end of each dataloder.

And it's always better if you can share the code (especially catalyst-based), so we can check out all parts of it.
PS. btw, @ngxbac feel free to PR your additional metrics & losses.

Hi,
Thank for your replies.
None of the sugessions above could help me :D.
I searched in Pytorch forum. There are many people getting the similar issue. I guess, probably it comes from pytorch framework.

PS. btw, @ngxbac feel free to PR your additional metrics & losses.

It is my pleasure to contribute to this awesome library. I will do it in the near future when I can clean my code, I promise.


Add provisioner

Given that we recently removed the previous way that we had to provision nodes, we need a new more secure way to  deploy and update nodes.

Closed as https://github.com/nimona/go-provision/pull/3


Two-Factor Authentication (2FA) Support?

I'm new to homebridge and started with Bryan's plugin before I realized the API issues. So I'm working on porting to this plugin.

No issues uninstalling homebridge-alarm.com and installing homebridge-node-alarm-dot-com.
I updated the config file and deleted the ~/.homebridge/accessories/cachedAccessories file.
When launching Homebridge, it successfully logs me into my alarm.com account.

Then it drops the following error:

UNHANDLED ERROR: Error: GET https://www.alarm.com/web/api/systems/systems/4472096 failed: [object Object]
at fetch.then.then.catch.err (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process.internalTickCallback (internal/process/next_tick.js:77:7)

Every minute thereafter I get the same error.

Error: GET https://www.alarm.com/web/api/systems/systems/4472096 failed: [object Object]
at fetch.then.then.catch.err (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process.internalTickCallback (internal/process/next_tick.js:77:7)

Any help would be appreciated.

I have been traveling quite a bit recently, but plan to do some work in the coming weeks. This seems like a problem with upgraded node packages that I need to rework the implementation.

@danemacmillan, is the GET url the same as @longanecker's?
After upgrading and testing, I'm still not seeing these errors in my log like the both of you are.
Could both of you answer the following questions:
System/OS:
Node Version:
Homebridge Version:
Alarm.com Account Type: (you may have to ask your provider what options you have with your security package)

@mkormendy  I am seeing something similar:
[[37m[7/16/2019, 5:52:18 PM][[39m [[36m[Security System][[39m Error: GET https://www.alarm.com/web/api/systems/systems/7615162 failed: [object Object]
at fetch.then.then.catch.err (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process._tickCallback (internal/process/next_tick.js:68:7)

Can u provide more detail? Maybe answer the previous request that longanecker nor Dane didn’t answer?

How do I grab the node version?

Well I googled “get node version” and the first stack overflow entry came up with this, but your mileage may vary:
https://stackoverflow.com/questions/14888471/node-js-version-on-the-command-line-not-the-repl/14888509#14888509

System/OS: Linux Docker
Node Version: v10.16.0
Homebridge Version: Version 0.4.50
Alarm.com Account Type: Interactive security with video.  Do you need them all listed?
Working on the logs now.

`[7/16/2019, 9:24:11 PM] [Config] Console v4.5.1 is listening on :: port 8080
[7/16/2019, 9:24:12 PM] Loaded config.json with 0 accessories and 2 platforms.
[7/16/2019, 9:24:13 PM] ---
[7/16/2019, 9:24:13 PM] Loaded plugin: homebridge-node-alarm-dot-com
[7/16/2019, 9:24:13 PM] Registering platform 'homebridge-node-alarm-dot-com.Alarmdotcom'
[7/16/2019, 9:24:13 PM] ---
[7/16/2019, 9:24:13 PM] Loaded plugin: homebridge-config-ui-x
[7/16/2019, 9:24:13 PM] Registering platform 'homebridge-config-ui-x.config'
[7/16/2019, 9:24:13 PM] ---
[7/16/2019, 9:24:13 PM] Loading 2 platforms...
[7/16/2019, 9:24:13 PM] [Config] Initializing config platform...
[7/16/2019, 9:24:13 PM] [Config] Running in Standalone Mode.
[7/16/2019, 9:24:13 PM] [Security System] Initializing Alarmdotcom platform...
[7/16/2019, 9:24:13 PM] Loading 0 accessories...
Setup Payload:
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│
└────────────┘

[7/16/2019, 9:24:13 PM] [Security System] Logging into Alarm.com as xxxx
[7/16/2019, 9:24:13 PM] Homebridge is running on port 51826.
[7/16/2019, 9:24:14 PM] [Security System] Logged into Alarm.com as xxxx
[7/16/2019, 9:24:14 PM] [Security System] UNHANDLED ERROR: Error: GET https://www.alarm.com/web/api/systems/systems/7615162 failed: [object Object]
at fetch.then.then.catch.err (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
[7/16/2019, 9:24:51 PM] [Config] Starting terminal session
[7/16/2019, 9:25:13 PM] [Security System] Error: GET https://www.alarm.com/web/api/systems/systems/7615162 failed: [object Object]
at fetch.then.then.catch.err (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
[7/16/2019, 9:25:15 PM] [Config] Terminal session ended.
[7/16/2019, 9:26:13 PM] [Security System] Error: GET https://www.alarm.com/web/api/systems/systems/7615162 failed: [object Object]
at fetch.then.then.catch.err (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
[7/16/2019, 9:27:13 PM] [Security System] Error: GET https://www.alarm.com/web/api/systems/systems/7615162 failed: [object Object]
at fetch.then.then.catch.err (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
[7/16/2019, 9:28:13 PM] [Security System] Error: GET https://www.alarm.com/web/api/systems/systems/7615162 failed: [object Object]
at fetch.then.then.catch.err (/homebridge/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:334:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
`

I started doing a little tinkering in Postman. I suspect the issue may be 2 factor auth. Using Firefox dev tools. I logged into to alarm.com to see successful API calls. I saw there was 2 headers being passed in the request that authenticates the user:
Cookie=twoFactorAuthenticationId=xxxxxxx
ajaxrequestuniquekey
Sending a postman request without both results in a 403.

Can you turn off two-factor auth on your account temporarily and test?
Or if it is a "no-going back" to non-2FA setting, please let me know that too.

Traveling till Saturday. I will give it a shot then.

As I suspected.... Disabling 2FA on the account (I was able to turn it off on alarm.com so not a permanent setting on the account) allows your implementation to discover all sensors and the panel!

Perfect! I have tested this as well, and am seeing what you’re talking about.
I can provide further support for this and have to build in some further action steps to work with 2FA, similar to some other plugins I’ve seen for homebridge.

I attempted to install this plugin and am getting what appears to be a 2FA error, but I have it disabled on my account.
Here's my config.json file:
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
"ports": {
	"start": 52100,
	"end": 52150,
	"comment": "This section is used to control the range of ports that separate accessory (like camera or television) should be bind to."
},
"accessories": [],
"platforms": [{
	"platform": "Alarmdotcom",
	"name": "Security System",
	"username": "<*****>",
	"password": "<*****>",
	"armingModes": {
		"away": {
			"noEntryDelay": false,
			"silentArming": false
		},
		"night": {
			"noEntryDelay": false,
			"silentArming": false
		},
		"stay": {
			"noEntryDelay": false,
			"silentArming": false
		}
	}
}]

}
...and here is the error:
[9/29/2019, 8:25:04 AM] [Security System] Logging into Alarm.com as <*****>
[9/29/2019, 8:25:04 AM] Homebridge is running on port 51826.
[9/29/2019, 8:25:06 AM] [Security System] UNHANDLED ERROR: Error: POST https://www.alarm.com/pda/(S(axpklfdwwb5szixwg3daegpc))/Default.aspx failed: GET https://www.alarm.com/login.aspx?m=unexpectederror failed:
No afg cookie: ASP.NET_SessionId=4ozwh4ty42arfis1tj1idktp; twoFactorAuthenticationId=362F3B9444FE42CF13FF14F0927270BD3BF537942AA8CF162D46C5506DFB04C6; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!lSK/mIIQYr+OP6Xfq1PpycjqXg8oNVYZBUq1I/v8fbgEqDJd7OOpSGy/04zcTc/36yQRfZDYPj85f4E=
at fetch.then.catch.err (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:127:17)
at process._tickCallback (internal/process/next_tick.js:68:7)
Any suggestions on how I can make this work would be greatly appreciated!  Thank you!  :)

Well at a first glance the errors aren't the same as some of the others. but it appears like your account is still attempting to use 2FA regardless of it being disabled.

Agreed. I went into my account and enabled and then disabled 2FA just in case there was a bug, but I can’t seem to get it to work correctly. I get the same error every time.
I’m stumped on how to proceed. Any ideas?

Agreed. I went into my account and enabled and then disabled 2FA just in case there was a bug, but I can’t seem to get it to work correctly. I get the same error every time.
I’m stumped on how to proceed. Any ideas?

Sorry for not seeing this until now. I'm intermittently checking on these issues, and some are more engaging than others! 😉 I have however been looking into resolving this to get 2FA working as well.

Just as a heads up, I started hitting this error on my Frontpoint account despite not changing anything on my account. I've reached out to Frontpoint in hopes that there might be something on their end that they can disable (since I don't seem to have the option of enabling 2FA).

@miltykiss okay, lemme know what they say. My alarm.com account has the expected switch for the 2FA but I haven't attempted a fix for it yet.

Not sure if this is the same issue, but I have 2FA turned off on alarm.com but am getting the following error....
[2019-11-23 11:31:26] [Security System] Error: GET https://www.alarm.com/web/api/devices/locks/? failed: [object Object]
at fetch.then.then.catch.err (/usr/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:482:13)
at
at process._tickCallback (internal/process/next_tick.js:189:7)
[2019-11-23 11:32:26] [Security System] Error: GET https://www.alarm.com/web/api/devices/lights/? failed: [object Object]
at fetch.then.then.catch.err (/usr/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:482:13)
at
at process._tickCallback (internal/process/next_tick.js:189:7)
[2019-11-23 11:33:26] [Security System] Error: GET https://www.alarm.com/web/api/devices/locks/? failed: [object Object]
at fetch.then.then.catch.err (/usr/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:482:13)
at
at process._tickCallback (internal/process/next_tick.js:189:7)

@miltykiss okay, lemme know what they say. My alarm.com account has the expected switch for the 2FA but I haven't attempted a fix for it yet.

Inconclusive right now. They say that I should have an option on my account, but none actually exists. :(

Anyone make any progress on this? This is what I am getting, I don't even have the option for two factor on my frontpoint log in.
[12/15/2019, 4:50:15 PM] [Security System] Logging into Alarm.com as <j****>
[12/15/2019, 4:50:16 PM] [Security System] Error: POST https://www.alarm.com/pda/(S(plhtl5a1yl0p3kj1jnisg1cn))/Default.aspx failed: GET https://www.alarm.com/login.aspx?m=unexpectederror failed:
No afg cookie: ASP.NET_SessionId=ya0u12iqc3ttkyon1gps0pkt; twoFactorAuthenticationId=A190B897F09FC21C44100072FFA6256B72DA945CBDE26C9B20A5B589F2D70C83; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!TTC6dM8Tm6TRr4Dfq1PpycjqXg8oNcQ9LKd8KJ6nZjr3DuaLx7xH2i4jjSA5n1DuZLv7Ga5FxYm/WKI=
at fetch.then.catch.err (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:159:17)
at process._tickCallback (internal/process/next_tick.js:68:7)

@jdugan4859 I don't think that is the same error. Are you still receiving it?

I uninstalled this plugin on 11/23 after Frontpoint was unhelpful in determining where my 2FA option should be located in my preferences (they never got back to me, despite numerous requests).
Today, I did a full reinstall of Homebridge on my RPI since I changed to a bigger SD card and this plugin magically started working again (I'm even using my old config file). I'm not sure if something changed between 11/23 and now on alarm.com 's backend, but I would suggest trying it again.

Thanks for the update @miltykiss,.. @longanecker @danemacmillan @torresdrew @spiffynacho @jdugan4859 @kaganae can you guys update to the latest on your ends and see if things work now?
NOTE: I have provider that works directly with Alarm.com. So in the Alarm.com app and website, I have attempted to turn on two factor auth, but I never receive the text for the passcode to verify my second auth factor (phone). I have reached out to Alarm.com and never heard back which is odd, because this shouldn't have to do with my contracted provider.
Either way, I have no way of testing/developing for 2FA because I can't turn it on in the first place.

From what I can see Alarm[.]com is now forcing 2FA on all logons regardless of settings. Whenever I try to login direct to their site it forces me to enable 2FA. I can disable once I'm in but on the next logon it forces again. This has broken integration between this plugin and their site. Here is the logs from HomeBridge:
[11/19/2020, 6:12:11 PM] [Security System] UNHANDLED ERROR: Error: No afg cookie: ASP.NET_SessionId=at2oa4psiz5jhytggalcatpx; cookieTest=1; twoFactorAuthenticationId=4A5A95C6571CB589838C73897FC6CD64A72F47A645F4DCC859DAF5E5DB114B0E; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; loggedInAsSubscriber=1; twoFactorAuthenticationSkipped-11380094=false; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!l3ldY9MxOZI89yfNzUFX+zqT5KjmGEO8+vGb5CPGJdP/FpL5LNoQlti2GbhLFqkL9sGZ5H6vv+RFUnQ=
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at processTicksAndRejections (internal/process/task_queues.js:97:5)
[11/19/2020, 6:13:10 PM] [Security System] Logging into Alarm.com as
[11/19/2020, 6:13:12 PM] [Security System] Error: No afg cookie: ASP.NET_SessionId=oydnlulowbeaz5mir4sfok5v; cookieTest=1; twoFactorAuthenticationId=3499873BC8C8496A918A2F0830D5D065D4BD827ABE6343944DE368B96ADA2E95; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; loggedInAsSubscriber=1; twoFactorAuthenticationSkipped-11380094=false; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!Icu41SdK2uY2n67NzUFX+zqT5KjmGFLCsWvPT8vY31iI//4HQ4ljGt508AlYEYOUZ5XE+GK9PCOCm0s=
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at processTicksAndRejections (internal/process/task_queues.js:97:5)
Since at logon it is redirecting to a 2FA setup page I am unsure what the technical fix would be. Wish they would get with the times and allow API Key creation as this would be much easier to manage than their current setup.

This is interesting as I’m not seeing 2-FA being forced on me. The alarm.com partner portal also still lists 2-FA as being optional.
That being said, the Amazon Echo skill is able to use 2-FA, so theoretically it’s possible. However, I don’t have an echo to test me this.
Chase Lau
Please excuse any grammatical errors as this was sent from my iPhone.

On Nov 19, 2020, at 12:18 PM, CJ<EMAIL_ADDRESS>wrote:

From what I can see Alarm[.]com is now forcing 2FA on all logons regardless of settings. Whenever I try to login direct to their site it forces me to enable 2FA. I can disable once I'm in but on the next logon it forces again. This has broken integration between this plugin and their site. Here is the logs from HomeBridge:
[11/19/2020, 6:12:11 PM] [Security System] UNHANDLED ERROR: Error: No afg cookie: ASP.NET_SessionId=at2oa4psiz5jhytggalcatpx; cookieTest=1; twoFactorAuthenticationId=4A5A95C6571CB589838C73897FC6CD64A72F47A645F4DCC859DAF5E5DB114B0E; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; loggedInAsSubscriber=1; twoFactorAuthenticationSkipped-11380094=false; BIGipServerAlarmApplicationAlarm_WEBADC_Alarm_HTTPS=!l3ldY9MxOZI89yfNzUFX+zqT5KjmGEO8+vGb5CPGJdP/FpL5LNoQlti2GbhLFqkL9sGZ5H6vv+RFUnQ=
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at processTicksAndRejections (internal/process/task_queues.js:97:5)
[11/19/2020, 6:13:10 PM] [Security System] Logging into Alarm.com as
[11/19/2020, 6:13:12 PM] [Security System] Error: No afg cookie: ASP.NET_SessionId=oydnlulowbeaz5mir4sfok5v; cookieTest=1; twoFactorAuthenticationId=3499873BC8C8496A918A2F0830D5D065D4BD827ABE6343944DE368B96ADA2E95; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; loggedInAsSubscriber=1; twoFactorAuthenticationSkipped-11380094=false; BIGipServerAlarmApplicationAlarm_WEBADC_Alarm_HTTPS=!Icu41SdK2uY2n67NzUFX+zqT5KjmGFLCsWvPT8vY31iI//4HQ4ljGt508AlYEYOUZ5XE+GK9PCOCm0s=
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at processTicksAndRejections (internal/process/task_queues.js:97:5)
Since at logon it is redirecting to a 2FA setup page I am unsure what the technical fix would be. Wish they would get with the times and allow API Key creation as this would be much easier to manage than their current setup.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

No worries; further testing it appears it is being forces due to something at ADT.
When I try to log into alarm.com I enter creds then it redirects to:
https://control.adt.com/system-install/login-setup/two-factor-authentication/overview
Conversely when I login direct to control.adt.com I do not get redirected or forced to setup 2FA.
At this point I don't know if something is broken on the backend between ADT and alarm.com or it is something else.

Try downloading the Alarm.com app. If you try and use your credentials for ADT to login to the Alarm.com app, there should be an option on the Alarm.com app to turn off 2FA. Wait 10 mins, then reload homebridge.

That doesn't appear to be working; I'm starting to wonder if this is something cookie related that isn't being dropped on the homebridge during logon.

@cplmayo
I had the same issue.

Log in to ADT and/or Alarm.com apps (if you have both), ensure you turn off two factor Authentication.
Log out from the app.
Log back into the app, ensure “Keep me logged in” is checked.
Restart HomeBridge.

The problem should be solved. Good Luck.
@mkormendy : it will be nice, if plug-in can support the two factor authentication feature.

I've started seeing the same no afg cookie error. When I log in to Alarm.com and via the Alarm.com app, I noticed that it now prompts me every time to set up 2FA.

That is the same I have been dealing with it still works some of the time
but is not reliable enough to call it good. I now pretty much just use my
ADT app for control and try HomeKit once in a while to see if it works.
On Mon, Dec 7, 2020 at 5:20 PM farmerboy772<EMAIL_ADDRESS>wrote:

I've started seeing the same no afg cookie error. When I log in to
Alarm.com and via the Alarm.com app, I noticed that it now prompts me every
time to set up 2FA.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/node-alarm-dot-com/homebridge-node-alarm-dot-com/issues/11#issuecomment-740240793,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUURT2LACAZRCYXXECHFD3STVPMJANCNFSM4GHXLKAQ
.

--
Charles Johnston
"That government is best which governs the least, because its people
discipline themselves." -Thomas Jefferson

I'm getting the same 2FA error. I never enabled 2FA and "skipped" the option when logging into the website and the app. It seems a bit sporadic as I was able to get alarm.com into homebridge yesterday without changing anything, today, no dice.
Error: No afg cookie: ASP.NET_SessionId=v5vqzerhhjbdbj30dq1o3rqg; cookieTest=1; twoFactorAuthenticationId=9AF5C277B94D030C1A4D83490EB252204F080CB1CB85E921EC1D10090FA67BF0; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; loggedInAsSubscriber=1; twoFactorAuthenticationSkipped-4398430=false; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!mK2CfkWaU1Anr0DNzUFX+zqT5KjmGBEMaa6ViGpQEzVjUHADEQ3gOKPnlRgULG6pmYe/+0utjaFmV5Y=
at /home/hoobs/.hoobs/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Just curious who your provider is? A lot of the issues seem to be with ADT
or the like. I use a much smaller provider and haven’t encountered any 2FA
issues yet.
On Tue, Dec 15, 2020 at 2:45 AM thehumanista<EMAIL_ADDRESS>wrote:

I'm getting the same 2FA error. I never enabled 2FA and "skipped" the
option when logging into the website and the app. It seems a bit sporadic
as I was able to get alarm.com into homebridge yesterday without changing
anything, today, no dice.
Error: No afg cookie: ASP.NET_SessionId=v5vqzerhhjbdbj30dq1o3rqg;
cookieTest=1;
twoFactorAuthenticationId=9AF5C277B94D030C1A4D83490EB252204F080CB1CB85E921EC1D10090FA67BF0;
IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=;
SeamlessLoginEnabled=; loggedInAsSubscriber=1;
twoFactorAuthenticationSkipped-4398430=false; BIGipServerAlarmApplication
Alarm_WEBADC_Alarm_HTTPS=!mK2CfkWaU1Anr0DNzUFX+zqT5KjmGBEMaa6ViGpQEzVjUHADEQ3gOKPnlRgULG6pmYe/+0utjaFmV5Y=
at
/home/hoobs/.hoobs/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at processTicksAndRejections (internal/process/task_queues.js:97:5)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/node-alarm-dot-com/homebridge-node-alarm-dot-com/issues/11#issuecomment-745115284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6JCYWAYXJ54AEZWN56P7DSU4HYRANCNFSM4GHXLKAQ
.

Same issues as others here with Protection1, a smaller company.  Never enabled 2FA, but getting the prompt when logging in via a browser to sign up for it, which I skip.  Plugin seems to be working intermittently, but most often not, starting a week ago or so.

I also have Protection1 which is owned by ADT. I think Protection1 has it set up so that you get the prompt asking to enable 2FA at first login, but since I can't respond using Homebridge, it fails. Even though I said no/skip when I logged in on web, I had to skip again when I logged in on the app.

UPDATE:
Now I'm seeing my alarm.com show up in HomeKit, but it is still not logged in so nothing is responding. I still get the same error message:
12/15/2020, 11:13:30 PM [Protection 1] Logging into Alarm.com as XXX
12/15/2020, 11:13:30 PM [Protection 1] Error: No afg cookie: ASP.NET_SessionId=2h5h1jelgmt2qoyulebtkcwn; cookieTest=1; twoFactorAuthenticationId=CC67D26C3E59E5BAC327F2AD9952FC8FD794EDD7D36ABEFDEBE2CB86A6FAAA0D; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; loggedInAsSubscriber=1; twoFactorAuthenticationSkipped-4398430=false; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!04JrJywAS4GYI7rNzUFX+zqT5KjmGBl0l1GsMh/SZ6nbIblGmtMxIAhPvImkIgza9GR1PoWRggY8dNM=
at /home/hoobs/.hoobs/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Is there a 2FA nag screen or popup that needs to be dismissed when logging
into the alarm.com web interface?  I thought I recall someone mentioning
this previously.  I haven't seen this at all with my provider.
On Tue, Dec 15, 2020 at 11:15 PM thehumanista<EMAIL_ADDRESS>wrote:

UPDATE:
Now I'm seeing my alarm.com show up in HomeKit, but it is still not
logged in so nothing is responding. I still get the same error message:
12/15/2020, 11:13:30 PM [Protection 1] Logging into Alarm.com as XXX
12/15/2020, 11:13:30 PM [Protection 1] Error: No afg cookie:
ASP.NET_SessionId=2h5h1jelgmt2qoyulebtkcwn; cookieTest=1;
twoFactorAuthenticationId=CC67D26C3E59E5BAC327F2AD9952FC8FD794EDD7D36ABEFDEBE2CB86A6FAAA0D;
IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=;
SeamlessLoginEnabled=; loggedInAsSubscriber=1;
twoFactorAuthenticationSkipped-4398430=false; BIGipServerAlarmApplication
Alarm_WEBADC_Alarm_HTTPS=!04JrJywAS4GYI7rNzUFX+zqT5KjmGBl0l1GsMh/SZ6nbIblGmtMxIAhPvImkIgza9GR1PoWRggY8dNM=
at
/home/hoobs/.hoobs/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/node-alarm-dot-com/homebridge-node-alarm-dot-com/issues/11#issuecomment-745752435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6JCYXHTXSOMR7MJJMYC7LSVAX5VANCNFSM4GHXLKAQ
.

It pops up for me on the app and web. On the app I can skip. On the web I have no choice but to enable in order to get into the account but then I disable it once I’m done. I don’t have a skip option for the web. ADT.
On Dec 16, 2020, 11:57 AM -0500, ngori<EMAIL_ADDRESS>wrote:

Is there a 2FA nag screen or popup that needs to be dismissed when logging
into the alarm.com web interface? I thought I recall someone mentioning
this previously. I haven't seen this at all with my provider.
On Tue, Dec 15, 2020 at 11:15 PM thehumanista<EMAIL_ADDRESS>wrote:

UPDATE:
Now I'm seeing my alarm.com show up in HomeKit, but it is still not
logged in so nothing is responding. I still get the same error message:
12/15/2020, 11:13:30 PM [Protection 1] Logging into Alarm.com as XXX
12/15/2020, 11:13:30 PM [Protection 1] Error: No afg cookie:
ASP.NET_SessionId=2h5h1jelgmt2qoyulebtkcwn; cookieTest=1;
twoFactorAuthenticationId=CC67D26C3E59E5BAC327F2AD9952FC8FD794EDD7D36ABEFDEBE2CB86A6FAAA0D;
IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=;
SeamlessLoginEnabled=; loggedInAsSubscriber=1;
twoFactorAuthenticationSkipped-4398430=false; BIGipServerAlarmApplication
Alarm_WEBADC_Alarm_HTTPS=!04JrJywAS4GYI7rNzUFX+zqT5KjmGBl0l1GsMh/SZ6nbIblGmtMxIAhPvImkIgza9GR1PoWRggY8dNM=
at
/home/hoobs/.hoobs/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/node-alarm-dot-com/homebridge-node-alarm-dot-com/issues/11#issuecomment-745752435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6JCYXHTXSOMR7MJJMYC7LSVAX5VANCNFSM4GHXLKAQ
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

The plugin is using the web interface for login and api calls.  My guess is
that there is some sort of counter or time window that is expiring on the
ADC side.  So even after disabling on the web after X logins or Y days or
something it is returning and nagging which is breaking the plugin .   Just
a hunch though.  I've had the plugin running for 2+ years now with no login
related issues.
On Wed, Dec 16, 2020 at 12:08 PM iBanks3<EMAIL_ADDRESS>wrote:

It pops up for me on the app and web. On the app I can skip. On the web I
have no choice but to enable in order to get into the account but then I
disable it once I’m done. I don’t have a skip option for the web. ADT.
On Dec 16, 2020, 11:57 AM -0500, ngori<EMAIL_ADDRESS>wrote:

Is there a 2FA nag screen or popup that needs to be dismissed when
logging
into the alarm.com web interface? I thought I recall someone mentioning
this previously. I haven't seen this at all with my provider.
On Tue, Dec 15, 2020 at 11:15 PM thehumanista<EMAIL_ADDRESS>wrote:

UPDATE:
Now I'm seeing my alarm.com show up in HomeKit, but it is still not
logged in so nothing is responding. I still get the same error message:
12/15/2020, 11:13:30 PM [Protection 1] Logging into Alarm.com as XXX
12/15/2020, 11:13:30 PM [Protection 1] Error: No afg cookie:
ASP.NET_SessionId=2h5h1jelgmt2qoyulebtkcwn; cookieTest=1;

twoFactorAuthenticationId=CC67D26C3E59E5BAC327F2AD9952FC8FD794EDD7D36ABEFDEBE2CB86A6FAAA0D;

IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=;
SeamlessLoginEnabled=; loggedInAsSubscriber=1;
twoFactorAuthenticationSkipped-4398430=false;
BIGipServerAlarmApplication

Alarm_WEBADC_Alarm_HTTPS=!04JrJywAS4GYI7rNzUFX+zqT5KjmGBl0l1GsMh/SZ6nbIblGmtMxIAhPvImkIgza9GR1PoWRggY8dNM=

at

/home/hoobs/.hoobs/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/index.js:149:19

at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/node-alarm-dot-com/homebridge-node-alarm-dot-com/issues/11#issuecomment-745752435
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AG6JCYXHTXSOMR7MJJMYC7LSVAX5VANCNFSM4GHXLKAQ

.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/node-alarm-dot-com/homebridge-node-alarm-dot-com/issues/11#issuecomment-746647715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6JCYSG3CTA4A45TAYKGPTSVDSMNANCNFSM4GHXLKAQ
.

Having the same issue as @iBanks3 with the same setup.  Tried logging in via web and app disabling 2FA and reinstalling/restarting but no luck

I did some testing and on the web, you get the prompt to turn on or skip 2FA every time for "new" browsers. I tested using incognito sessions.
I am with Protection1, but makes sense that ADT Command users have the same experience. Protection 1 is owned by ADT and both platforms are powered by alarm.com.

Just found this repository which seems to solve this issue by having the user out their 2FA code into the config. Perhaps we could replicate this functionality?
https://github.com/uvjustin/alarmdotcom

Hopefully not adding to the noise on this thread. Was able to get my ADT control system back up and running today after being forced to enable 2FA. Found out that after turning it on, I could go under: Settings -> Login Information -> Two Factor Authentication and I had an option to disable.
Tested a quick logout and login and it looks like currently I'm not being pestered to enable 2FA at the moment.

Hopefully not adding to the noise on this thread. Was able to get my ADT control system back up and running today after being forced to enable 2FA. Found out that after turning it on, I could go under: Settings -> Login Information -> Two Factor Authentication and I had an option to disable.
Tested a quick logout and login and it looks like currently I'm not being pestered to enable 2FA at the moment.

I am trying to use this plug-in on hoops to access alarmdotcom.
I seem also to be getting error related to 2FA despite the fact that I have that feature off.  I tried activating and then deactivating 2FA without success.
I have checked out the code and it was verified by JSON Formatter & Validator.  Here is what I am using:
{
"platform": "Alarmdotcom",
"name": "Alarm System",
"username"<EMAIL_ADDRESS>"password": "",
"armingModes": {
"away": {
"noEntryDelay": false,
"silentArming": false
},
"night": {
"noEntryDelay": false,
"silentArming": false
},
"stay": {
"noEntryDelay": false,
"silentArming": false
}
},
"authTimeoutMinutes": 30,
"pollTimeoutSeconds": 180,
"logLevel": 1
}
Here is the error I get repeatedly:
2/13/2021, 6:53:18 PM [Alarm System] Error: No afg cookie: ASP.NET_SessionId=2gt3rajlmlwzdat4b55r4fpr; cookieTest=1; twoFactorAuthenticationId=D601F6C556BA428E3205611C132394D5705ADFBA16485FFF9B9A4771311DBA65; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!6n6i44MGnbrc8hTNzUFX+zqT5KjmGJs4rnpxLbnjSeSgmDLevddWYVrBenLpMQ6zCN+xkGh99Evv8Pw=
at /home/hoobs/.hoobs/node_modules/node-alarm-dot-com/dist/index.js:91:23
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Any ideas on how to remedy?
thanks in advance

The latest beta implements support for a MFA workaround. I haven't had time to write a wiki yet (help appreciated!) but there is a new spot in the config for adding your MFA token. You need to get it from a logged in browser. Here's how:

Open the network tab of the developer tools of your browser
Log into alarm.com
Check any network connection to the site. In the request headers, under the cookie section, there should be your cookie. It'll look something like this: Cookie: twoFactorAuthenticationId=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX;
Paste the part inbetween the = and the ; into your config. People using the UI just need to click the "Use MFA" checkbox and paste it there. Manual users should add "mfaCookie" to their config.json and paste this in.
Restart the plugin/homebridge and requests should start working.

Granted, this is a workaround since Alarm.com doesn't implement anything like app passwords, but hopfully it'll work well enough where ADT users don't have to worry anymore.
Please let me know if you run into any problems!

@chase9
Just install the beta version and config mfaCookie, It works for me as ADT user. No more Error message.
Thank you.

Is 1.7.1 the beta version and if it is not, where do I find the beta version?
I have it installed and I added the mfaCookie to the code.  I couldn't find it in the network section of the developer mode of safari as you mentioned it would be found, rather, I found it under storage, cookies,  where it was listed as "twoFactorAuthenicationId"  once I had signed into alarm.com
I assume I leave both the username and password and add the mfacookie field as I did below?  Again I checked the syntax on the JSON Formatter and all is good.
Here is what I have at this time:
{
"platform": "Alarmdotcom",
"name": "Alarm System",
"username"<EMAIL_ADDRESS>"password": "",
"mfaCookie": "",
"armingModes": {
"away": {
"noEntryDelay": false,
"silentArming": false
},
"night": {
"noEntryDelay": false,
"silentArming": false
},
"stay": {
"noEntryDelay": false,
"silentArming": false
}
},
"authTimeoutMinutes": 30,
"pollTimeoutSeconds": 180,
"logLevel": 1
}
Here is the log file, still getting an error:
2/21/2021, 7:01:02 PM [Alarm System] Error: No afg cookie: ASP.NET_SessionId=qshjwn0iwwr2ocdqyz2byreh; cookieTest=1; twoFactorAuthenticationId=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!6ONT1V/cwHK7UlfNzUFX+zqT5KjmGCdXXj7u5qAznS/MCzn7wmWRvPN2N126Qlr4+J+agcKyqtUoDpU=
at /home/hoobs/.hoobs/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:91:23
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Any help appreciated.
cheers

@Shadwboxer The version you'll need is 1.7.2-4. If you're using the UI you can lookup how to install alternative versions homebridge ui.
I got around to writing a wiki page on 2FA support. You can follow the instructions here to set it up, once you're running the beta plugin.

@Shadwboxer The version you'll need is 1.7.2-4. If you're using the UI you can lookup how to install alternative versions homebridge ui.
I got around to writing a wiki page on 2FA support. You can follow the instructions here to set it up, once you're running the beta plugin.

Installed the beta and added the 2FA token. So far so good! Thank you for this update!

@chase9 How do I go about installing the beta version?

@cplmayo How did you install the beta version?

@CaptainsMast
sudo npm install -g<EMAIL_ADDRESS>

@cplmayo You are a saint, thank you!

@chase9
Thanks for the update.  I have been doing a little more homework on my system and I see that HOOBS, which is the platform I am running, requires a bit of work beyond my skills to get a beta plugin working
( https://github.com/hoobs-org/HOOBS/issues/186).
I will wait till this change makes it to the HOOBS stable plugin page.
cheers

having issues resolving the 2FA login. Followed the 2FA WiKi page and still receiving the following error:

Beta is installed and 2FA key is entered

Error: GET https://www.alarm.com/web/api/systems/systems/6778960 failed: Two factor is enabled on this account but not setup in the plugin. See the wiki for details
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:470:15
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 0)

Could you reply with your config.json attached or a screenshot of your settings? Remember not to include your username/password.
Chase Lau
Please excuse any grammatical errors as this was sent from my iPhone.

On Mar 2, 2021, at 11:30 PM, techfreakdad<EMAIL_ADDRESS>wrote:

having issues resolving the 2FA login. Followed the 2FA WiKi page and still receiving the following error:
Beta is installed and 2FA key is entered
Error: GET https://www.alarm.com/web/api/systems/systems/6778960 failed: Two factor is enabled on this account but not setup in the plugin. See the wiki for details
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:470:15
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 0)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Interestingly enough it started working overnight without any further intervention. The error message is gone and the Alarm.com functions are responding appropriately in HK.

Could you reply with your config.json attached or a screenshot of your settings? Remember not to include your username/password. Chase Lau Please excuse any grammatical errors as this was sent from my iPhone.

So now that's I'm running the beta plugin, it will not recognize "ignored devices". Further if I go into the HB UI and delete them from the cached accessories, they still populate in HK. And with the following error:
TypeError: Cannot read property 'updateCharacteristic' of undefined
at ADCPlatform.statLightState (/usr/local/lib/node_modules/homebridge-node-alarm-dot-com/dist/index.js:633:17)
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:334:20
at Array.forEach ()
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:329:27
at Array.forEach ()
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/src/index.ts:301:22
at processTicksAndRejections (internal/process/task_queues.js:93:5)

I haven't seen another poster with this issue so bringing it here; I'm using HOOBs and have setup and installed the beta of this plugin manually. It was working briefly but am now getting the error seen below. HOOBs seems to properly handle the useMFA and mfaCookie tokens, and I was not initially receiving this error.
I've enabled/disabled MFA on the account and the plugin + restarted homebridge to try to clear any saved states, checked and the mfaCookie token is unchanged (redacted below),  and fully un-and-re-installed the plugin.
3/28/2021, 9:45:15 PM [Security System] Error: GET https://www.alarm.com/web/api/systems/systems/10899645 failed: Two factor is enabled on this account but not setup in the plugin. See the wiki for details
    at /home/hoobs/.hoobs/node_modules/node-alarm-dot-com/dist/index.js:470:15
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Promise.all (index 0)

{     "server": {         "port": 80,         "origin": "*",         "autostart": 0,         "home_setup_id": "*****",         "polling_seconds": 5     },     "client": {         "default_route": "status",         "inactive_logoff": 30,         "theme": "hoobs-dark",         "locale": "en",         "temp_units": "fahrenheit",         "country_code": "US",         "postal_code": "*****"     },     "bridge": {         "name": "*****",         "port": *****,         "pin": "*****",         "username": "*****"     },     "description": "",     "ports": {},     "plugins": [         "homebridge-node-alarm-dot-com"     ],     "accessories": [],     "platforms": [         {             "platform": "Alarmdotcom",             "plugin_map": {                 "plugin-name": "homebridge-node-alarm-dot-com"             },             "name": "Security System",             "logLevel": 3,             "username": "*****",             "password": "*****",             "useMFA": true,             "mfaCookie": "*****",             "authTimeoutMinutes": 15,             "pollTimeoutSeconds": 90         }     ],     "package_manager": "npm",     "system": "hoobs"
One thing I noticed more generally was with the API requests being sent, the token "twoFactorAuthenticationSkipped-*****=false;" was always set to true when being sent by the browser. Not sure if this is something that may need to be updated or added to the requests sent from the plugin.
3/28/2021, 9:57:15 PM [Security System] Error: No afg cookie: ASP.NET_SessionId=; cookieTest=1; twoFactorAuthenticationId=; IsFromNewSite=1; fromASP=; IsFromSeamlessLogin=; login=; ST=; SeamlessLoginEnabled=; loggedInAsSubscriber=1; twoFactorAuthenticationSkipped-=false; BIGipServer~AlarmApplication~Alarm_WEBADC_Alarm_HTTPS=!=
at /home/hoobs/.hoobs/node_modules/node-alarm-dot-com/dist/index.js:93:23
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Thanks for your work on this plugin!

I'm having issues for quite a while, no matter each version I use on the plugin. this is the error message I am getting:
Error: GET https://www.alarm.com/web/api/devices/sensors?ids[]=99843883-14&ids[]=99843883-9&ids[]=99843883-15&ids[]=99843883-4&ids[]=99843883-5257&ids[]=99843883-13&ids[]=99843883-12&ids[]=99843883-8&ids[]=99843883-2&ids[]=99843883-5267&ids[]=99843883-5529&ids[]=99843883-3&ids[]=99843883-10&ids[]=99843883-5&ids[]=99843883-229&ids[]=99843883-16&ids[]=99843883-6&ids[]=99843883-7 failed: request to https://www.alarm.com/web/api/devices/sensors?ids[]=99843883-14&ids[]=99843883-9&ids[]=99843883-15&ids[]=99843883-4&ids[]=99843883-5257&ids[]=99843883-13&ids[]=99843883-12&ids[]=99843883-8&ids[]=99843883-2&ids[]=99843883-5267&ids[]=99843883-5529&ids[]=99843883-3&ids[]=99843883-10&ids[]=99843883-5&ids[]=99843883-229&ids[]=99843883-16&ids[]=99843883-6&ids[]=99843883-7 failed, reason: read ECONNRESET
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:470:15
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 1)
at async Promise.all (index 0)

I'm no longer having major issues, even with 2FA on. I uninstalled everything, manually deleted the cached devices (as to not have to setup my other plugin devices), waited a few days, and reinstalled. I noticed the 2FA cookie changed even though I didn't change the 2FA status in that time. There are still intermittent errors on calls but overall the system seems stable, and arm/disarm and sensor states are correct.
I also created a second, less privileged alarm.com user in the name of least-privilege access but I only did that after it was in the working state above. More leaving this here as a recommendation for others.

I'm having issues for quite a while, no matter each version I use on the plugin. this is the error message I am getting:
Error: GET https://www.alarm.com/web/api/devices/sensors?ids[]=99843883-14&ids[]=99843883-9&ids[]=99843883-15&ids[]=99843883-4&ids[]=99843883-5257&ids[]=99843883-13&ids[]=99843883-12&ids[]=99843883-8&ids[]=99843883-2&ids[]=99843883-5267&ids[]=99843883-5529&ids[]=99843883-3&ids[]=99843883-10&ids[]=99843883-5&ids[]=99843883-229&ids[]=99843883-16&ids[]=99843883-6&ids[]=99843883-7 failed: request to https://www.alarm.com/web/api/devices/sensors?ids[]=99843883-14&ids[]=99843883-9&ids[]=99843883-15&ids[]=99843883-4&ids[]=99843883-5257&ids[]=99843883-13&ids[]=99843883-12&ids[]=99843883-8&ids[]=99843883-2&ids[]=99843883-5267&ids[]=99843883-5529&ids[]=99843883-3&ids[]=99843883-10&ids[]=99843883-5&ids[]=99843883-229&ids[]=99843883-16&ids[]=99843883-6&ids[]=99843883-7 failed, reason: read ECONNRESET
at /usr/local/lib/node_modules/homebridge-node-alarm-dot-com/node_modules/node-alarm-dot-com/dist/index.js:470:15
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 1)
at async Promise.all (index 0)

I am having the same error message.

I'm very pleased to say this has been merged in 1.8.0


Maximum quantity not being enforced

This is regarding this tier: https://opencollective.com/ehf-community/contribute/aroha-koha-for-paula-21141
On the main page you can see it's already reached the max available of 7:

But this isn't being enforced. You can still click koha and go through the checkout process. It should not let you do that.

We actually have an inconsistency here: the contribution (both legacy and new versions) both assume that only PRODUCTs and TICKETs tiers can have a limited quantity. I'll look at that.


feat: integration tests

Implemented a very basic test suite for all Datatypes that can be passed as an argument or returned.
I am not sure what kind of conventions you would like to follow here, so I kept the PHP files very stupid - same with the assertion texts. So we would need to decide on a proper way of how to pass the results from PHP to Rust.
Not a 100% happy how the PHP code is executed using a hardcoded path to the compiled extension. Nontheless, I think that is a good start for the first iteration 👍🏻

@TorstenDittmann how are you feeling about that state of this PR? I may be able to help finish it if you're short on time.

What's the status on this ? I feel like such test would be very helpful when developing this library

What's the status on this ? I feel like such test would be very helpful when developing this library
It's the most critical feature that I want, but this PR is abandoned.
IMHO, I would try to reproduce what php core does with phpt

Yeah, it kinda got abandoned due to many reason.
If there is interest I can spend a weekend to probably create the PR again from scratch 👀

IMHO, I would try to reproduce what php core does with phpt

That would be nice, it could even be used by people creating extension with this lib to test there code.
I think this would be possible if there was a possibility to compile php with code from this library under a new binary, which would also allow to create binary in rust that can execute php code (like a new sapi ?)

That would be nice, it could even be used by people creating extension with this lib to test there code.
I think this would be possible if there was a possibility to compile php with code from this library under a new binary, which would also allow to create binary in rust that can execute php code (like a new sapi ?)

There is this experimental module here https://github.com/php/php-src/tree/master/sapi/embed to produce a single binary with the Zend engine entry point. I did a small PoC with it and Tauri to reproduce what NativePHP does: it works well.
Instead of compiling into a whole extension, we could execute the tested code with it

Can you share your PoC with Tauri, i would be interested in how you did that

I made an example on https://github.com/davidcole1340/ext-php-rs/pull/270
It works great, it even allow to put test directly in the wanted file, i will try to do a wrapper so we can execute code directly in it, thanks for the input @ptondereau about embed this is certainly the best way to go for that


Document how to upload protos of any type

Hey team! Please add your planning poker estimate with Zenhub @paulinechi @sinkingsugar


Merge master to live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Consume-Packages/Dependency-Resolution.md
:white_check_mark:Succeeded

docs/TOC.md
:white_check_mark:Succeeded

docs/What-is-NuGet.md
:white_check_mark:Succeeded

docs/media/dependency-graph.png
:white_check_mark:Succeeded

docs/media/nuget-restore.png
:white_check_mark:Succeeded

docs/media/nuget-roles.png
:white_check_mark:Succeeded

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


Disable fragile test-runner exceptions test

Summary: Disabling this for now so we can get CI green against our rely test suite. After it's green we can work on getting this re-enabled.
Differential Revision: D13495452

Didn't get tracked properly, already merged.

https://github.com/facebookexperimental/reason-native/commit/b0b6932a5679dbc15a005ca4d2907df560ed0dc6


New propties window not easly moveable

Description
I believe because the tab buttons are where the title bar is makes it so it can't be moved.
Steps To Reproduce
No response
Expected behavior
The title bar should be blank so the window can be moved
Files Version
<IP_ADDRESS>
Windows Version
10.0.19043.1387
Relevant Assets/Logs

Can you drag the window from the left of the title bar buttons? We're working on hiding the maximize and minimize buttons to give you more space to grab from.

I can but its very small amount. ill wait to see if the removing of the button make it easer to do

This issue is caused by hidden items in the nav view that are taking up space preventing the drag region from working correctly. The solution for this is to switch to x:Load so that the nav items don't take up any space.

Would it not be possible to make the window wider when opened?

@Josh-65 the drag area would still be covered by the navigation view items.


UI mods

This is cool but I think we should keep the notes in between the frets since that seems to be the standard


Add theme breakpoints to Storybook

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


weex run ios

Makes sure these boxes are checked befor submitting your issue - thank you!

[] Check that your node version is >= 6 and npm version is >=5(Run npm --version and node --version).
node v9.10.1
npm  v5.6.0
[] If you encounter any problems using the tool, please check if there has a new version to update(Run weex update [pluginname]@latest).
[] Check the FAQ, make sure there have not the same issue.

Your development environment

weex-toolkit verison (Run weex -v)
weex -v
v1.2.9

weexpack : v1.2.1

weex-builder : v0.3.14

weex-previewer : v1.4.6

platform (Win/Mac/Ubuntu..)
mac

The key error stack message.
============Build Config============
AppName      : WeexApp
Version      : 0.1
BuildVersion : 0.1.0
AppId        : com.alibaba.weex
WeexBundle   : index.js
Ws           : ws://<IP_ADDRESS>:8080
CodeSign     :
Profile      :
15:13:02 : If you want to change build config.please modify ios.config.json
15:13:02 : pod update
15:13:02 : Hot Reload socket: ws://<IP_ADDRESS>:8080
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.5.0/lib/cocoapods/executable.rb:89: warning: Insecure world writable dir /usr/local/go in PATH, mode 040777
Update all pods
Updating local specs repositories
10% [1] building modules 0/1 modules 1 active .../awesome-app/src/index.vue?entry=true[!] Failed to connect to GitHub to update the CocoaPods/Specs specs repo - Please check if you are offline, or that GitHub is down
15:13:03 : Command run error, please check if there has the same issue here: https://github.com/weexteam/weex-toolkit/issues/337
15:13:03 : Error:Error: Command failed: pod update
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.5.0/lib/cocoapods/executable.rb:89: warning: Insecure world writable dir /usr/local/go in PATH, mode 040777
at ChildProcess.exithandler (child_process.js:273:12)
at ChildProcess.emit (events.js:180:13)
at maybeClose (internal/child_process.js:936:16)
at Socket.stream.socket.on (internal/child_process.js:353:11)
at Socket.emit (events.js:180:13)
at Pipe._handle.close [as _onclose] (net.js:541:12)

Steps to reproduce the problem.(Maybe a dotwe link,)

@sixianfeng Try the solution here https://stackoverflow.com/questions/38993527/cocoapods-failed-to-connect-to-github-to-update-the-cocoapods-specs-specs-repo?answertab=votes#tab-top.

@erha19  升级了 openssl 和ruby   还是不行
F014176:~ tusm$ openssl version
OpenSSL 1.0.2o  27 Mar 2018
TF014176:~ tusm$ pod --version
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.5.0/lib/cocoapods/executable.rb:89: warning: Insecure world writable dir /Users/tusm in PATH, mode 040777
1.5.0
ruby --version
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin15]

问题已经解决了，把 mac 升级了 sierra 版


Jesse: Watch hitechdriver.com

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

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

Approved by Jeff Schaller in Charcoal HQ


NixOS Stage 1 boot broken for build-vm

Issue description
nixos-rebuild build-vm on latest master<PHONE_NUMBER>8b7591d1431beef7fc6c8e7affef0d) yields this:

Basically, the boot hangs with the message /init: line 95: can't open '/dev/null'. I guess I could be brave and try this on a real system (possibly it only affects the VM), but I figured it post this issue anyway :-)
It works like it should just a few days ago: 898edb0fbc3f23b24b7e28bad0cdd3e57ad5dcc7.
Steps to reproduce

Enter latest nixpkgs.git working tree (i.e.<PHONE_NUMBER>8b7591d1431beef7fc6c8e7affef0d)
nixos-rebuild -I nixpkgs=. build-vm
./result/bin/run-*-vm -m 4096

Technical details

System: NixOS 16.09pre 64-bit

CC @abbradar (has touched stage-1 in the affected commit range).

Ouch, I think this is me indeed. Investigating...

This happens because we force-override filesystems for VMs. Because we now set special filesystems in common fileSystems attribute set, they are overriden and no special filesystems are mounted. It's a miracle it goes through stage 1 ~_^.
I guess I'll fix this by adding boot.specialFileSystems and moving them there...

@abbradar: That was quick! Thank you. (I've confirmed the fix works.)

IMHO, if certain filesystems need special treatment, it's nicer to have an option in the filesystem, similar to the neededForBoot flag.
And it's not clear what the semantics of specialFileSystems is. It seems to implicitly be "those filesystems that should be mounted in a QEMU VM anyway".

Although, since the option is marked as internal, I guess it's not a huge problem.

@edolstra First implementation did just what you have described (only the option was named early). I would be glad to return to this, however I have no idea how to do so with this override taking place. Any ideas?


Mop up test won't start if the test is open before candidates are added

It is possible to open a test before candidates are added and then test wont start. Perhaps its best to disable Open Tests button until candidates are added (?)

This is a good spot, thanks @mbrookeswebdev


Feat button component

These are the updated changes @WojuadeAA  for the button

Hello Kelvin can you resolve this conflict?


End to End tests fail for SOPS (HTTP 301)

End to end tests fail for sops tool due to http status 301 redirect
Expected Behaviour

make e2e should pass all tests

Current Behaviour

make e2e generates the following error:
=== CONT  Test_CheckTools/Download_of_sops
url_checker_test.go:41: Error getting url for sops: server returned status: 301

Possible Solution

Modify url_checker_test.go to be permissive for 301 status codes and follow the redirect

Steps to Reproduce (for bugs)

Clone repo (https://github.com/alexellis/arkade)
run make e2e

Context

Issue is preventing successful e2e tests, required for merge requests for additional tooling contributions.

If requesting a CLI for "arkade get"
How many downloads does this tool have? Check at:
https://somsubhra.github.io/github-release-stats/
If approved, are you willing to submit a pull request for this?
Your Environment

AMD64 Linux / bash

What Kubernetes distribution are you using?

kubectl version

N/A

Operating System and version (e.g. Linux, Windows, MacOS):

uname -a
Linux xxxx 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/os-release
NAME="Linux Mint"
VERSION="21.1 (Vera)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 21.1"
VERSION_ID="21.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=vera
UBUNTU_CODENAME=jammy

What arkade version is this?

./arkade version
            _             _
  __ _ _ __| | ____ _  __| | ___
 / _` | '__| |/ / _` |/ _` |/ _ \
| (_| | |  |   < (_| | (_| |  __/
 \__,_|_|  |_|\_\__,_|\__,_|\___|

Open Source Marketplace For Developer Tools

Version: dev
Git Commit: 3a36fb5e13bcb6455e000d3e06bcfd998e9895ef

 🐳 arkade needs your support: https://github.com/sponsors/alexellis

Hi @mkimberley are you happy to send a PR for this?

I've fixed it - the error was due to mozilla moving the project into a "getsops" organisation.
If you find arkade useful and appreciate me maintaining the tool, please check out personal sponsorship options
Cheers :gb:

https://github.com/alexellis/arkade/releases/tag/0.9.24


nb-skeleton does not work in a table

I'm trying this web component in a table as follow , only the circle is rendered , the bar does not, what I'v missed , many thanks!!!

    <meta charset='utf-8' />


Wanted to add Mondrian website project

It consists of Mondrian painting with the help of HTML and CSS. Kindly assign me for this.

Please go through the guideline on steps to contribute before contributing : https://github.com/dev-AshishRanjan/Hacktoberfest-frontend/blob/dev/CONTRIBUTING.md
Happy Contributing!


low version google chrome(my version is 73) is not supported,how can I support it

Description
I can use it correct in new version google chrome,but in low version,the glb suffix file can not show,when I upgrade the low version to new version,it can show again,how can I do in the low version google chrome
Browser Affected

Chrome

OS

Windows

Versions
Chrome:73

@gexingfeiyang we actively support the last two versions of every major browser. If there is a reason why you cannot upgrade, please let us know so that we can consider whether or not we should extend support.
To be honest with you, it is unlikely that we will go out of our way to support a Chrome version that old. However, if you explain your use case a little more and also share an example / demo / model that fails in old Chrome, then I would be happy to consider the issue with you and give you a more clear answer as to whether or not you can use old Chrome.

Something to note is that developers working with the Android emulator tend to have old Chrome versions by default. I was trying to get the model viewer working in a WebView on an Android 10 image, but that didn't work out; as it turned out, that image shipped with Chrome 74:

@cdata Where might one find documented the oldest Chrome version that v1.0.0 supports?

@artob We don't document that anywhere because we don't have enough test coverage to be certain. More than likely it won't stop completely, but simply have more and more bugs the further back you go. As stated above, our test coverage is generally for the most recent two versions.

@elalish The failures I have seen (with the bundled stock Chrome version on Android 10 VMs, as mentioned above) produced just a blank white page with no overt indication of anything wrong other than the content just missing.
Is that the intended failure mode for ancient Chrome versions (Chrome 74 in that case), or might it perhaps be useful to show some failure indication similar to broken image tags?
Also, even if it's not possible to pinpoint the exact version where all this no longer works, would it at least be possible to document a known-good version where it all certainly does work?

@artob Indeed, those things would be helpful. I'd be more than happy to accept a PR, and if that's too heavy a lift, if you want to test some chrome versions and put the results here, I can put them into our docs somewhere. The biggest challenge is it will tend to be a moving target.

is there any way to disable Scale on AR Mode

https://modelviewer.dev/docs/index.html#entrydocs-augmentedreality-attributes-arScale

I have integrated this model viewer plus in android application everything works fine but the ar-scale does not work. I have also make changes in packages but nothing works. your response will be appreciated.

I have a problem with my app. Its working fine in android emulator, but when i deploy it by downloading the apk the model is not loaded,rather than a blue colour loading indicator keeps on loading.


Error when starting Eliza agent: "fs.Stats constructor is deprecated" and "triggerUncaughtException"

Description:
I am encountering an error when trying to start the Eliza agent using the provided instructions. The error appears to be related to deprecated features and experimental warnings in Node.js.
Steps to Reproduce:
Clone the repository and checkout the latest tagged release:
bash
git clone https://github.com/ai16z/eliza.git
cd eliza
git checkout v0.0.10
Install dependencies:
bash
pnpm install -r
Configure environment variables in .env (using placeholder values where appropriate).
Start the agent:
bash
pnpm start --character="characters/trump.character.json"
Observe the error messages.
Expected Behavior:
The agent should start without errors, allowing me to interact with it as per the quickstart guide.
Actual Behavior:
I receive the following error messages:
(node:25002) ExperimentalWarning: --experimental-loader may be removed in the future; instead use register():
--import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));'
at createModuleLoader (node:internal/modules/esm/loader:814:17)
at Object.getOrInitializeCascadedLoader (node:internal/modules/esm/loader:858:22)
at asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:105:65)
at runEntryPointWithESMLoader (node:internal/modules/run_main:138:19)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:175:5)
at node:internal/main/run_main_module:36:49
(node:25002) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
at Object.createResolve (/Users/bensmith/Desktop/Personal/Projects/agents/eliza/node_modules/ts-node/dist-raw/node-internal-modules-esm-resolve.js:146:25)
at /Users/bensmith/Desktop/Personal/Projects/agents/eliza/node_modules/ts-node/src/index.ts:1494:7
at Object.onceFn [as getNodeEsmResolver] (/Users/bensmith/Desktop/Personal/Projects/agents/eliza/node_modules/ts-node/src/util.ts:166:13)
at createEsmHooks (/Users/bensmith/Desktop/Personal/Projects/agents/eliza/node_modules/ts-node/src/esm.ts:125:51)
at Object.registerAndCreateEsmHooks (/Users/bensmith/Desktop/Personal/Projects/agents/eliza/node_modules/ts-node/src/esm.ts:118:10)
at file:///Users/bensmith/Desktop/Personal/Projects/agents/eliza/node_modules/ts-node/esm.mjs:8:7
at ModuleJob.run (node:internal/modules/esm/module_job:268:25)
at async onImport.tracePromise.proto (node:internal/modules/esm/loader:543:26)
at async Hooks.register (node:internal/modules/esm/hooks:152:7)
at async initializeHooks (node:internal/modules/esm/utils:318:5)
node:internal/modules/run_main:122
triggerUncaughtException(
^
[Object: null prototype] {
[Symbol(nodejs.util.inspect.custom)]: [Function: [nodejs.util.inspect.custom]]
}
Thrown at:
at asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:122:5)
Node.js v23.1.0
ELIFECYCLE  Command failed with exit code 1.
ELIFECYCLE  Command failed with exit code 1.
Environment:
OS: macOS Sonoma 14.6.1
Node.js version: v23.1.0
I have tried the following steps to resolve the issue:
Cleaned node_modules and reinstalled dependencies with pnpm install -r.
Updated ts-node, typescript, and @types/node to the latest versions.
Adjusted tsconfig.json settings, including changing moduleResolution to "node" and "nodenext".
Modified the start script in core/package.json to use ts-node directly.
Attempted to rebuild packages with pnpm rebuild.
Despite these efforts, the error persists.
The error messages suggest deprecation warnings and issues with experimental features, possibly related to the Node.js version.
The quickstart guide specifies Node.js v23.1.0, but this version may not be stable or widely supported.
Request:
Could you please help me identify the cause of this issue and provide guidance on how to resolve it? Is there a recommended Node.js version or additional configuration that I should use?

please try the following:
main branch, node v23.1.0,
pnpm clean
pnpm install
pnpm build
pnpm start --character=(file)


Fix OneDimentionalBar graph all filled

I am not familiar with chartXScale's range property, so I can't explain why it is different,
but with range, the graph is not maximized even when the capacity is full, so I changed it to domain.

domain
range

Thank you, confirmed your fix.


With a run flag, exit with code depending on whether a list was exported.

The flag could make it exit with 0 if a list was exported, and a 1 of no list was exported.

May I ask for the use case for something like this?

For easier scripting purposes - I want to be able to know whether or not a list was exported/saved.

I see, please test this branch feat/exit-code


Custom Data Filter Adaptor: buildQuery: The condition with Eq operator's operands positions is not same as other conditions with different operators

I've noticed this when I'm writing my own data filter adaptor. the condition with Eq operator has value in lhs and typeName and fieldName in rhs but that's not same for other conditions with different operators.
Example:
[     [         {             "lhs": {                 "value": 10             },             "cmp": "Eq",             "rhs": {                 "typeName": "Article",                 "fieldName": "col1"             }         }     ],     [         {             "lhs": {                 "typeName": "Article",                 "fieldName": "col2"             },             "cmp": "Gt",             "rhs": {                 "value": 10             }         }     ],     [         {             "lhs": {                 "typeName": "Article",                 "fieldName": "col4"             },             "cmp": "Geq",             "rhs": {                 "value": 10             }         }     ],     [         {             "lhs": {                 "typeName": "Article",                 "fieldName": "col3"             },             "cmp": "Lt",             "rhs": {                 "value": 10             }         }     ],     [         {             "lhs": {                 "typeName": "Article",                 "fieldName": "col5"             },             "cmp": "Leq",             "rhs": {                 "value": 10             }         }     ],     [         {             "lhs": {                 "typeName": "Article",                 "fieldName": "col6"             },             "cmp": "Neq",             "rhs": {                 "value": 10             }         }     ] ]
is this bug or has any purpose for having like that?

Totally agree with you !! but still why this inconsistency, Because, we need to handle this case while creating custom data filter adapter, making this consistent helps to get more predictable conditions json while working with custom adaptors. Just an improvement.


Getting 401, Permission denied error on read data from firebase

Hi, firstly thank you so much for such a great library. But I am getting an error using it.
I am using php PHP 7.2.5 and version * 4.7.1 of the library, and I am getting a 401 , permission denied error. I checked the role with 'Project Editor' and 'Project Owner' both, and the Database rules for read & write are both true.
But when I try to read the data, I get 401 , permission denied error.
The weird thing is that I do get the data from firebase but library returns 401 error.
In the middleware
    {
        return function (callable $handler) {
            return function (RequestInterface $request, array $options = []) use ($handler) {
                $uri = $request->getUri();
                $path = $uri->getPath();

                if ('.json' !== substr($path, -5)) {
                    /** @noinspection ExceptionsAnnotatingAndHandlingInspection */
                    $uri = $uri->withPath($path.'.json');
                    $request = $request->withUri($uri);
                }

                return $handler($request, $options);
            };
        };
}

where there is $request = $request->withUri($uri); I get the data from firebase, and I can print it there. But the next call at the bottom of the function return $handler($request, $options); returns 401 error.
Bellow is the code that cause the issue :

        $firebase = (new Factory)
            ->withServiceAccount($serviceAccount)
            ->withDatabaseUri('Database_URI')
            ->create();

        $database = $firebase->getDatabase();

        $testData = $database
            ->getReference('testData')->getSnapshot();

          var_dump($testData)

Hey @exleedo and thank you for reporting this issue!
The 401 error is still an indication that the used service account doesn't match the project  you are accessing or hasn't the needed permissions, and the exception is thrown by Google's Authentication middleware when processing the server response.
The database rules don't apply when using the Admin SDK, because the Service Account grants unrestricted admin rights.
Could you please try the following:

Look inside the used service account JSON file and check if the field project_id matches your database URI. Usually, if the project id is myproject, the database URI ismyproject.firebaseio.com. If both are the same, you can remove the withDatabaseUri() line - the library will then determine the database URI automatically.
Try creating a new service account JSON file by accessing https://console.firebase.google.com/project/_/settings/serviceaccounts/adminsdk and then clicking "Generate new private key". Then reference this file when bootstrapping the SDK in your script.

Thanks @jeromegamez for prompt reply.
1- By doing this, it doesn't give me the error now, but it also doesn't bring the data.
2- Same thing with the new key as well.

Thanks @jeromegamez for a quick reply. thank you so much. Deleting the old service account, and recreating a new service account with 'Project Editor' permissions worked this time. It works with & without the withDatabaseUri() .
Thank you so much for your help & this amazing library.

Glad it worked out, thank you for the kind words! 🌺


widescreen image format

So I have a widescreen monitor and I'm guessing that Jellyscrub tries to only allow format 16:9, so my images get stretched out like below.
What I get:

What I should get:

Note this only happens when I enter fullscreen, or when the browser is maximized. Work great in windowed mode. Could I fix this somehow?

I think it should be easy to fix by making the max size of the preview no greater than the size of the image. What's your monitor resolution just so I can test?

I think it should be easy to fix by making the max size of the preview no greater than the size of the image. What's your monitor resolution just so I can test?

That's what I thought we could do. My screen res is 3440x1440
Lmk how it goes!

Hey just wanted to check if you found anything?

Hey just wanted to check if you found anything?

Sorry have been pretty busy. I tried checking this out using the Chrome dev tools that let you test different resolutions, so it might not be 100% true to what you're seeing, but it didn't seem as disproportionately scaled like in the example you showed.
I see something else is styling the thumbnail images--if you remove/comment out the custom CSS you have set in the jellyfin settings do you get the same result?


[VIRUS] Can't install!!!

Windows 11 Pro 64 bit, Nim 2.0.8.
When trying to install library with nimble:
Installing https://github.com/yglukhov/wasmrt@any version
Downloading https://github.com/yglukhov/wasmrt using git
Verifying dependencies for<EMAIL_ADDRESS>Info:  Dependency on zippy@any version already satisfied
Verifying dependencies for<EMAIL_ADDRESS>Installing<EMAIL_ADDRESS>Building wasmrt/wasmrt/wasm2html.exe using c backend
Tip: 421 messages have been suppressed, use --verbose to show them.
oserrors.nim(92)         raiseOSError
Error:  Operation did not complete successfully because the file contains a virus or potentially unwanted software.
    ... Additional info: ("C:\\Users\\User\\AppData\\Local\\Temp\\nimble_2632\\githubcom_yglukhovwasmrt\\wasmrt\\wasm2html.exe", "C:\\Users\\User\\.nimble\\pkgs2\\wasmrt-0.1.0-345935a3a160c44acf09ec23a14e2c20eaebc8a0\\wasmrt\\wasm2html.exe")

The Windows defender note is:

Also in the same file:


import-xlf command should output package.nls.[language].json loc files to root, not --output-dir

In @vscode/l10n-dev, the import-xlf command takes a parameter --output-dir, which per the current logic sets the output directory for both bundle.[language].json and package.nls.[language].json.
However, this doesn't accommodate the case from the official l10n-sample, where you can see that the file package.nls.[language].json lives in the root directory, whereas the file bundle.[language].json lives in the ./l10n/ directory. From what I understand, the  package.nls.[language].json files must live in the same directory as package.nls.json and package.json, regardless of the value of the l10n parameter specified inside of package.json, so why does import-xlf move package.nls.[language].json to a folder where it won't be recognized?

Yeah these should just go to wherever the package.json is.


Incorrect information about supported languages in readme

Readme says "Supports multiple languages and frameworks such as Node.js, Java, Ruby, Perl, PHP, and Python." But odo officially supports only Java and NodeJs, the other languages are without any guarantees.
Not sure what the right wording should be.

ping @boczkowska

/assign @pmacko1

/assign @pmacko1

the PR is merged. we can close this issue


[Feature Request] Compatibility with TheRippers System Customizer.

Currently compatibility seems to be pretty good except for the currencies, when the system customizer changes the currencies the character sheet doesn't update to match the new currencies.

It looks like the module requires purchase. I will contact TheRipper to inquire further.

Reference to troubleshooting with TheRipper: https://discord.com/channels/844900867240361984/1197054285679165500
Solution: Use CONFIG.DND5E.currencies.${currency}.abbreviation instead of DND5E.CurrencyAbbr${currency}

This has been released. When able, please give it a test and see if the issue is resolved for you.

Closing as completed.


Consume ssh_proxy_link on ha_proxy config if available

This depends on https://github.com/cloudfoundry/diego-release/pull/273 being merged first.
Now we disable consul templating in favor of bosh links and more advanced HAProxy config.

consider giving it more specific type so that implicit linking connects up components automatically without addiotional manifest configuration.
cc @dsabeti
Sent from my iPhone

On Feb 14, 2017, at 4:25 PM, Luan Santos<EMAIL_ADDRESS>wrote:
This depends on cloudfoundry/diego-release#273 being merged first.
Now we disable consul templating in favor of bosh links and more advanced HAProxy config.
You can view, comment on, or merge this pull request online at:
https://github.com/cloudfoundry/cf-release/pull/1152
Commit Summary
Consume ssh_proxy link on ha_proxy config if available
File Changes
M jobs/haproxy/monit (8)
M jobs/haproxy/spec (5)
M jobs/haproxy/templates/haproxy.conf.erb (16)
Patch Links:
https://github.com/cloudfoundry/cf-release/pull/1152.patch
https://github.com/cloudfoundry/cf-release/pull/1152.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey @luan.
I just realized that there will be two jobs (access_z1 and access_z2) that both provide this link in a standard Diego deployment. I may be wrong, but I'm pretty sure that this PR will fail most deployments because BOSH won't know which of the two links to consume. I think you'll have to nil out the link in cf-release manifest (like we do with consul and nats).
In which case, why have this change, if you have to deploy it such that link cannot be consumed?

@luan Bump.

Hey @luan, I'm going to close this PR if it looks like you don't need it.

Hey @dsabeti. Yeah you're right, but that's only true if you're using a cf-release generated manifest.
I know of consumers of ha_proxy that use the job from cf-release in a cf-deployment type manifest (only one access VM).
We do have to nil out the link in cf-release manifest unfortunately for that to work.

Hey @luan. Thanks for the context. It's good point, so I just prioritized the story to merge this.


pin revive version, and fix some detected problems

merged and v0.3.0 tagged

we are very close to be able to make PEDANTIC the default
$ make PEDANTIC=1 tidy
▶ generating subproject rules
▶ tidy: root
▶ tidy: cblog
▶ tidy: discard
▶ tidy: filter
  ✘  https://revive.run/r#cognitive-complexity  function (*LogEntry).Enabled has cognitive complexity 8 (> max enabled 7)
  entry.go:24:1

  ✘  https://revive.run/r#cognitive-complexity  function (*LogEntry).WithField has cognitive complexity 16 (> max enabled 7)
  entry.go:137:1

  ✘  https://revive.run/r#cognitive-complexity  function (*LogEntry).WithFields has cognitive complexity 31 (> max enabled 7)
  entry.go:158:1

  ✘  https://revive.run/r#cyclomatic  function (*LogEntry).WithFields has cyclomatic complexity 11 (> max enabled 10)
  entry.go:158:1

✘ 4 problems (4 errors, 0 warnings)

Errors:
  3  cognitive-complexity
  1  cyclomatic

make: *** [.tmp/gen.mk:47: tidy-filter] Error 1


add icinga monitoring

to document

[ ] default and how to set icinga password (htpasswd.icinga)
[ ] additional possible monitoring to be added

waiting on answer on how to setup admin handle


Bugfix for pairplot

The changes from marginal_plot had broken the subset argument of pairplot. This fixes it.

Codecov Report

Merging #694 (cddc9b2) into main (7799de5) will increase coverage by 0.00%.
 Consider uploading reports for the commit 74602e9 to get more accurate results

@@           Coverage Diff           @@
##             main     #694   +/-   ##
=======================================
  Coverage   76.68%   76.69%
=======================================
  Files          76       76
  Lines        5868     5869    +1
=======================================
+ Hits         4500     4501    +1
  Misses       1368     1368

Flag
Coverage Δ

unittests
76.69% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sbi/analysis/plot.py
56.32% <100.00%> (+0.10%)
: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 7799de5...74602e9. Read the comment docs.


isolate nginx-ingress deployment

moves nginx-ingress to kubeapps namespace
uses a custom ingress class 'kubeapps-ingress'

The idea here is to not interfere with any other Ingress Controllers
installed in the cluster (typically installed in the kube-system
namespace).

travis is failing because it's still looking in kube-system.  @prydonius I think the fix is https://github.com/prydonius/manifest/pull/1 - although travis doesn't run against a fork-of-a-fork so I haven't actually exercised that fix yet ..


Change position of kiki images on smaller screens - About

The kiki images on About page should be bigger on smaller screens.
_
As images de kiki na página About deveriam ser maiores em telas pequenas.

Fixed by pull request #16 by @pwechs83


Show how to create credentials object

Show how to create credentials object on python sdk

@jonparrott WDYT? Probably worth looking at all of http://google-cloud-python.readthedocs.io/en/latest/google-cloud-auth.html to see how this fits in

This is good in theory, but the sentence preceding this talks about "credentials for your specific environment". @ricardolui how would you feel about just cross-linking to http://google-auth.readthedocs.io/en/latest/user-guide.html#compute-engine-container-engine-and-the-app-engine-flexible-environment

@jonparrott Good, I actually would not mind linking to Service account private key files section from the document you pointed out.  I  think we should also see how to update https://cloud.google.com/docs/authentication to make it more like http://google-auth.readthedocs.io/en/latest/user-guide.html#compute-engine-container-engine-and-the-app-engine-flexible-environment, and give example in our programming languages. What do you think? I thought it was too hard to find the code sample to do a simple thing. My ldap is gricardo@

@ricardolui I'm working with the tech writing team right now to completely re-do cloud.google.com/docs/authentication.

@jonparrott Great!!! :) That will be awesome!! Many customers complaining about it ;) About this specific commit, if you could link the Credentials creation to  http://google-auth.readthedocs.io/en/latest/user-guide.html#compute-engine-container-engine-and-the-app-engine-flexible-environment, it would be great!

@ricardolui it's your PR, feel free to update it (and I'll review and merge).


Error logging for Observe / Override, implicit TweakDBID conversion, minor environment fixes

Added reporting for errors occurred in Observe / Override handlers.
This fails silently before fix:

Observe('gameObject', 'OnGameAttached', function()
    undefined.call()
end)

Added implicit string to TweakDBID conversion.

print(Game.GetTransactionSystem():GetItemInSlot(Game.GetPlayer(), 'AttachmentSlots.WeaponRight'):GetItemID())

Removed redundant environment passing to Lua functions as an argument. This change addresses two issues:
a. Environment passed as an argument doesn't change the environment of the function, but goes straight to the called function as a table.
b. The function inherits environment when defined and the assignment is stored in the Lua state. There is no need to set environment for function before call unless it's intended to change the currently assigned environment to another one. Also it should be taken in account that any environment assignment is permanent and will not be reverted to previous environment in any implicit way.

Looks good! Thanks :)


Add specific tags to speed up common configuration updates

Issue Type

Feature Idea

Summary
I've always been a bit more of a stickler against tagging all the things in Ansible (and still am), but see some value in adding tags to specific roles, includes, etc. which are often helpful in speeding up the deployment of specific config changes.
There are a few of these specific things which I think we could support out of the box in Drupal VM and wouldn't add too much weight to the main playbook:

PHP (options like memory limit changes)
XDebug configuration changes (quite often requested)
Drupal deployment (the new drupal role, basically)
Apache/Nginx ('webserver') changes

I hope some other people may chime in and offer suggestions of other things that could be tagged.
The basic process is:
First, add a tag to a part (or relevant parts) of the playbook like:
    # Build and configure the Drupal site.
    - include_role: name=geerlingguy.drupal
      static: no
      tags: ['drupal']

Then, if you just want to call that tag, you can specify the tags arg with DRUPALVM_ANSIBLE_ARGS like so:
DRUPALVM_ANSIBLE_ARGS="--tags=drupal" vagrant provision

Any other sets of tags people think would be nice to have? Parts of the VM you might frequently change and don't want to wait the full 2-4 minutes for a provision run.

Hmm maybe add DRUPALVM_ANSIBLE_TAGS for convenience? Seems more like a "supported feature" then.
if tags = ENV['DRUPALVM_ANSIBLE_TAGS']
  ansible.tags = tags
end

@oxyc - True, would accept a PR for that—that way you could specify tags through raw args or that env var.


Python code debugging in mixed mode does not work in VS2019 with python 3.6

We are running python code from managed code (C#) using 3.6 CPython dll (Marshaling). I could see the python debugger attached but still could not set break points.
Attached simple project which will be helpful to repro the issue.  Select X64 build and change path of python36.dll in CPython.cs file to run the code. Feel free to let me know if you need more details.

PythonMixedModeDebugging.zip

@santok1980, Thank you for the report.
Can you tell me which VS version you are using? Can you try debugging with Python 3.7 (using the base interpreter, not a virtual environment)

Here are the details
Microsoft Visual Studio Enterprise 2019
Version 16.4.0
Assuming it works for you, Which versions (VS and Python) are you using where debugging from C# to Python works?

Not a common scenario. If this needs to be reopened please do.


Query on how to setup ethernet in Linux using Ti180 board

Hi,
Is the ethernet for Linux ready? If yes, can you provide me information on how to do the setup on Ti180 board. Thanks

I too , am eagerly waiting for its release as it is key for our product
development . I am hoping for an ' early beta release ' by june and check
out the site every morning to see if new code has been uploaded.
Hedley Davidson
On Mon, May 29, 2023 at 9:30 AM rohaya2021 @.***> wrote:

Hi,
Is the ethernet for Linux ready? If yes, can you provide me information on
how to do the setup on Ti180 board. Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/Efinix-Inc/br2-efinix/issues/11, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB244KUXTH7UJUJU6SH4BH3XIRF53ANCNFSM6AAAAAAYSOJ5TU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

duplicate query. See https://github.com/Efinix-Inc/br2-efinix/issues/6.


UserManger.FindID throws an cast exception

I have been trying to get a user by their ID, using UserManager, which is an email address.
For the sake of example<EMAIL_ADDRESS>I also have a  Model.Person , which I store in the same database as the RavenUsers, and the Key is also the same email.
When I create the user I use this code
var user = new Models.ApplicationUser(userName); (UserName is the Email)
I have now eventually got got this working by using
var user2 = UserManager.FindByName("peter@mail.com");
The problem is when I use this
var user3 = UserManager.FindById("peter@mail.com");
I get an exception
Unable to cast object of type 'Models.Person' to type 'Models.ApplicationUser'.
I have been trying to work out what the problem is about 2 days now, on and off, but it seems when I use the FinByID, RavenDB, or Identidy.Raven DB for some reason actually matches up with the Person Key in the database. I couldn't understand why I was getting this exception the whole time since I am just calling a method and not trying to cast any thing.
When I use
var user3 = UserManager.FindByEmail("peter@mail.com");
It reutrns NULL, even though in the database under ApplciationUsers, the Email is the same as UserName and the same as the Key.
Is this a Identity.RavenDB problem?

I think I know why its getting the Person entity instead of ApplicationUser.
The entity that was returned useing FindByName, its ID is<EMAIL_ADDRESS>I am a newb with RavenDB but I don't understand why the FindByID would get a result from the Persons table and then try and cast it to ApplicationUser?