Bed State is always Unknown

As of 1.0.15, I've noticed my Bed State, and all its attributes, are always unknown. This means I have no way to read the target heating level of the bed, though I'm still able to set it. Not seeing any error messages, but I haven't had time to go enable debug logging.

Bed State is still updating for me. @andrew-kennedy, I'm curious if your account is being served a different version of the API

Hmm, can you remind me which endpoints are in use for that state so I can audit them? I'll take another traffic capture.

@andrew-kennedy
It's pulling from the heating_level:
@property     def heating_level(self) -> int | None:         """Return heating/cooling level."""         level = self.device.device_data.get(f"{self.side}HeatingLevel")         # Update observed low         if level is not None and level < self.observed_low:             self.observed_low = level         return level
This boils down to being the first value in the list returned from the url f"{CLIENT_API_URL}/devices/{self.device_id}"

{
  "result": {
    "deviceId": "redacted",
    "ownerId": "<redacted>",
    "leftUserId": "<redacted>",
    "leftHeatingLevel": -33,
    "leftTargetHeatingLevel": 0,
    "leftNowHeating": false,
    "leftHeatingDuration": 0,
    "leftSchedule": {
      "daysUTC": {
        "sunday": false,
        "monday": false,
        "tuesday": false,
        "wednesday": false,
        "thursday": false,
        "friday": false,
        "saturday": false
      },
      "enabled": false
    },
    "rightUserId": "redacted",
    "rightHeatingLevel": -33,
    "rightTargetHeatingLevel": 0,
    "rightNowHeating": false,
    "rightHeatingDuration": 0,
    "rightSchedule": {
      "daysUTC": {
        "sunday": false,
        "monday": false,
        "tuesday": false,
        "wednesday": false,
        "thursday": false,
        "friday": false,
        "saturday": false
      },
      "enabled": false
    },
    "priming": false,
    "lastLowWater": "2024-07-26T20:38:51.800Z",
    "needsPriming": false,
    "hasWater": true,
    "ledBrightnessLevel": 15,
    "sensorInfo": {
      "label": "20600-0003-F00-00012C1D",
      "partNumber": "20600",
      "sku": "0003",
      "hwRevision": "F00",
      "serialNumber": "redacted",
      "lastConnected": "2024-09-17T08:04:02.423Z",
      "skuName": "caking",
      "connected": true
    },
    "timezone": "America/Los_Angeles",
    "mattressInfo": {
      "firstUsedDate": null,
      "eightMattress": null,
      "brand": null
    },
    "firmwareCommit": "026334eb083095a6450edbf3d7c046b802b4280b",
    "firmwareVersion": "026334e",
    "firmwareUpdated": true,
    "firmwareUpdating": false,
    "lastFirmwareUpdateStart": "1970-01-01T00:00:00.000+00:00",
    "lastHeard": "2024-09-17T08:05:45.244Z",
    "online": true,
    "encasementType": null,
    "leftKelvin": {
      "targetLevels": [
        -21,
        -21,
        -21
      ],
      "alarms": [],
      "scheduleProfiles": [],
      "phases": [],
      "level": 0,
      "currentTargetLevel": 0,
      "active": false,
      "currentActivity": "off"
    },
    "rightKelvin": {
      "targetLevels": [
        -21,
        -21,
        -21
      ],
      "alarms": [],
      "scheduleProfiles": [],
      "phases": [],
      "level": 0,
      "currentTargetLevel": 0,
      "active": false,
      "currentActivity": "off"
    },
    "features": [
      "warming",
      "cooling",
      "vibration",
      "alarms"
    ],
    "leftUserInvitationPending": false,
    "rightUserInvitationPending": false,
    "modelString": "Pod 3",
    "lastPrime": "2024-04-24T21:03:33.000Z",
    "isTemperatureAvailable": true,
    "deactivated": {}
  }
}

This is what I see returned from that API when I do a traffic capture.

I'm wondering if the side names are somehow wrong and being interpolated into incorrect keys or something...

So looking at the code, if you setup the integration while your bed was in away mode the self.side key wouldn't ever update when you assigned yourself to a bed side. This could cause the key for the json data to be misformatted. Creating a release to fix this, which I'm guessing may be your issue.

Closing this, since I believe the latest releases fixed the issue.


Unable to Remove Text Background

Steps to reproduce:

I am also experiencing the same issue with text color and highlighting not being able to reset to default, using the latest on next branch.


EVP: don't call memset for evp_pkey_downgrade

This commit tries to address a locking issue in evp_pkey_reset_unlocked
which can occur when it is called from evp_pkey_downgrade.
evp_pkey_downgrade will acquire a lock for pk->lock and if successful
then call evp_pkey_reset_unlocked. evp_pkey_reset_unlocked will call
memset on pk, and then create a new lock and set pk->lock to point to
that new lock. I believe there are two problems with this.
The first is that after the call to memset, another thread would try to
acquire a lock for NULL as that is what the value of pk->lock would be
at that point.
The second issue is that after the new lock has been assigned to
pk->lock, that lock is different from the one currently locked so
another thread trying to acquire the lock will succeed which can lead to
strange behaviour. More details and a reproducer can be found in the
Refs link below.
This commit introduces a new function that is only called by
evp_pkey_downgrade which does not use memset but instead
"manually" sets the EVP_PKEY values to their default values, but does
not modify pk->lock. This could perhaps be updated to go back to only
having one function that is called for both evp_pkey_downgrade and
EVP_PKEY_new and only create a new lock if one does not already exist.
Refs:
https://github.com/danbev/learning-libcrypto/blob/master/notes/issues.md#openssl-investigationtroubleshooting
https://github.com/nodejs/node/issues/29817

I'm wondering why we have a lock at all? In line with most OpenSSL objects, an EVP_PKEY is not thread safe.
Ping @levitte.

Would it rather make sense to do the downgrade the other way around?
I.e. do the copy_downgraded to a temporary copy and then just copy back the contents if the downgrade succeeds (excluding the lock).

Access to most of the fields in an EVP_PKEY is not controlled by the lock anyway. The lock seems to be primarily related to the reference counting.

Reference counts are always associated with a lock.
This code plays with the locks, so it isn't a surprise.

I'm having some apprehensions about the new reset code...  addressing each field individually is a maintenance issue waiting to happen, as we will be prone forget to update the new reset function any time a new field is added in EVP_PKEY.  That is the single reason for the memset() method.
I do understand why a memset() isn't a best idea when a lock pointer is involved...  I wonder if a re-organization of EVP_PKEY could be a good idea, for example an internal structure to separate payload stuff from lock and count managerial stuff.
NOTE: This is food for thought, not something that I expect to happen in this PR!

What about copying the EVP_PKEY to a temporary.  Using memset(2) to clear everything, setting the lock in the copy and them copying back to the original?  It requires the lock pointer to be moved atomically which might be a bad assumption.
Something like this should work:
struct {
    ...
    CRYPTO_RWLOCK *lock;
    ...
} *p;

const size_t offset = (unsigned char *)&p->lock - (unsigned char *)p;    /* strictly it's a ptrdiff_t not size_t */

memset(p, 0, offset);
memset(&p->lock + sizeof(p->lock), 0, sizeof(*p) - offset - sizeof(p->lock));

@paulidale I'll take a closer look at your suggestion, but it might not be until tomorrow. Thanks

It's only a suggestion, but I've reservations like @levitte.

What about copying the EVP_PKEY to a temporary.  Using memset(2) to clear everything, setting the lock in the copy and them copying back to the original?

Doesn't that exactly reproduce the issue that this PR is trying to solve?

Doesn't that exactly reproduce the issue that this PR is trying to solve?

The problem is that the original PKEY structure is being zeroed including the lock and then the lock is restored.  What I suggested doesn't do this.  That doesn't make it any less of a hack.
Selective memset(2) is better -- I think it will need to preserve the reference count and lock though.

Oh, now I see...

@paulidale I've added a commit with the changes you suggested (hope I did not misunderstand). One thing though was the second memset call which I had to change to be 1 instead of sizeof(pk->lock). My reasoning for this can be found below.

memset reasoning
After the first call to memset, which will set all the values up to pk->lock to zero:
(lldb) expr *pk
(EVP_PKEY) $7 = {
  type = 0
  save_type = 0
  ameth = 0x0000000000000000
  engine = 0x0000000000000000
  pmeth_engine = 0x0000000000000000
  pkey = {
    ptr = 0x0000000000000000
    rsa = 0x0000000000000000
    dsa = 0x0000000000000000
    dh = 0x0000000000000000
    ec = 0x0000000000000000
    ecx = 0x0000000000000000
  }
  references = 0
  lock = 0x00000000004520b0
  attributes = 0x0000000000000000
  save_parameters = 1
  ex_data = {
    ctx = 0x0000000000000000
    sk = 0x0000000000000000
  }
  keymgmt = 0x000000000044fbb0
  keydata = 0x000000000045aea0

And just take note of the address of pk->lock:
(lldb) expr pk->lock
(CRYPTO_RWLOCK *) $3 = 0x00000000004520b0
(lldb) memory read -c 1 -f x -s 8 &pk->lock
0x00450a90: 0x00000000004520b0

Next we are going to use memset once again with the address of the lock
plus the size of the pointer (which is 8)
(lldb) expr &pk->lock + sizeof(pk->lock)
(CRYPTO_RWLOCK **) $8 = 0x0000000000450ad0  ------------+
(lldb) expr sizeof(pk->lock)                            |
(unsigned long) $9 = 8                                  |
(lldb) memory read -c 20 -s 8 -f x pk                   |
0x00450a60: 0x0000000000000000 0x0000000000000000       |
0x00450a70: 0x0000000000000000 0x0000000000000000       |
0x00450a80: 0x0000000000000000 0x0000000000000000       |
0x00450a90: 0x00000000004520b0 0x0000000000000000       |
0x00450aa0: 0x0000000000000001 0x0000000000000000       |
0x00450ab0: 0x0000000000000000 0x000000000044fbb0       |
0x00450ac0: 0x000000000045aea0 0x0000000000000000       |
    +---------------------------------------------------+
    ↓
0x00450ad0: 0x0000000000000000 0x0000000000000000
0x00450ae0: 0x0000000000000000 0x0000000000000000
0x00450af0: 0x0000000000000000 0x0000000000000000

Notice that this skipped a bit further than expected. In the code we are adding
8 to the address of pk->lock, but pk-lock is a pointer and perhaps it should
only be adding 1?:
(lldb) memory read -c 1 -s 8 -f x '&pk->lock + 1'
0x00450a98: 0x0000000000000000
  ↑
  +-------------------------------------------------+
0x00450a60: 0x0000000000000000 0x0000000000000000   |
0x00450a70: 0x0000000000000000 0x0000000000000000   |
0x00450a80: 0x0000000000000000 0x0000000000000000   |
                                      +-------------+
                                      ↓
0x00450a90: 0x00000000004520b0 0x0000000000000000
0x00450aa0: 0x0000000000000001 0x0000000000000000
0x00450ab0: 0x0000000000000000 0x000000000044fbb0
0x00450ac0: 0x000000000045aea0 0x0000000000000000
0x00450ad0: 0x0000000000000000 0x0000000000000000
0x00450ae0: 0x0000000000000000 0x0000000000000000
0x00450af0: 0x0000000000000000 0x0000000000000000

The Travis CI build failed with the following error:
An error occurred while generating the build script.

Would someone with permissions be able to re-run that job?

Would someone with permissions be able to re-run that job?

It looks like someone did.
However, you will have to wait until #13450 is merged, and rebase then.  It fixes the other Travis failures we currently see.

However, you will have to wait until #13450 is merged, and rebase then. It fixes the other Travis failures we currently see.

Thanks for the info and I'll rebase when that PRs has been merged.

@levitte Just a friendly ping that I've rebased this PR now that #13450 has landed.

This pull request is ready to merge

Merged to master with amendment of the commit message to reflect the real change after all the squashed commits.

Thank you for the contribution.


Directly include SVG logo in the page.

Use HTML  element to include Prometheus logo in the navbar.

:+1:


NJsonSchema breaks VS2015 Web Performance Test UI

When I am using NJsonSchema in a project with Web Performance Testing, I cannot set Context Variables using Visual Studio's GUI. I can edit the XML of the WPT by hand, or I could uninstall NJsonSchema, appoint the context parameters, reinstall NJsonSchema to build and run successfully the WPTs.
I am using NJsonSchema for custom validation rules (a WhatEverClassName extending Microsoft.VisualStudio.TestTools.WebTestingValidationRule).

I have no idea how a simple .NET library could cause this... do you?

... or is it run as part of the Visual Studio tooling?

Frankly, I have no idea. I could explain what I am doing in more details:

I would create a ValidationRule or ExtractionRule derived class, as shown here https://msdn.microsoft.com/en-us/library/ms182556.aspx I am doing this in a separate project, but the issue is observed if the class was in the same project with the web performance test.
I would install with NuGet Newtonsoft.Json and NJsonSchema. I use a general rule and JSON Path to query REST result for specific values and I use NJsonSchema to generate schema from the DTO class and validate the Rest result with it.
I create a Web Performance Test in a separate project, which references the project with the validation rules, add some requests to it.
Then I add the custom validation rules. All goes well, until I would press F4 to open the Properties of the element; I see no properties.
I uninstall NJsonSchema from the project with webtest files (I installed it because I need the dll to build, or I need to embed it into the project with validation and extraction rules, but this does not work either).
I clean and rebuild everything; as the project with webtests will need NJsonSchema only at runtime, I have no issues assigning properties on webtest requests.
However, I cannot run, nor debug, nor transform to code, because I lack NJsonSchema. Thus, I install it over NuGet and run/debug, and transform to code. I could try regestering globally assemblies (just for fun), but would not be acceptable :/

The library servers its purpose (great work :) ) and this issue is not a blocker. The webtest itself is XML. I guess it is translated to C# and build with MSTest. Having all the dll, MSTest does what it needs to do, so there is no issue with mainstream CI build servers.

Can you provide a sample project which reproduces this issue?

I can make one, I would the time to do it :)

The solution contains an example WebAPI2 project, there is a single controller. Rebuild the solution and in project ~.Test, select the applied validation rule and press F4 for the UI to show up. You should not be seeing the applied criteria. Uninstall package njsonschema from the project and do the same again; now you should be seeing the applied criteria, which is {$.[0].id}. This is a very minimalistic example.
NJsonSchemaWithWPT.zip


[Issue]: install latest not handled and leaks unnecessary info

What happened?
 nvm install latest
panic: runtime error: index out of range [3] with length 3

goroutine 1 [running]:
main.checkVersionExceedsLatest({0x1149e0c0, 0x6})
        C:/Users/corey/OneDrive/Documents/workspace/oss/coreybutler/nvm-windows/src/nvm.go:790 +0x220
main.install({0x1140a0e0, 0x6}, {0x29fa65, 0x2})
        C:/Users/corey/OneDrive/Documents/workspace/oss/coreybutler/nvm-windows/src/nvm.go:302 +0x35d
main.main()
        C:/Users/corey/OneDrive/Documents/workspace/oss/coreybutler/nvm-windows/src/nvm.go:87 +0xa69

``

### What did you expect to happen?

Have this case handled

### Version

1.1.9

### Which version of Windows?

Windows 11+

### Which locale?

English (Default)

### Which shell are you running NVM4W in?

PowerShell

### User Permissions?

Administrative Privileges, Non-Elevated

### Is Developer Mode enabled?

No (Default)

### Relevant log/console output

```Shell
nvm install latest
panic: runtime error: index out of range [3] with length 3

goroutine 1 [running]:
main.checkVersionExceedsLatest({0x1149e0c0, 0x6})
        C:/Users/corey/OneDrive/Documents/workspace/oss/coreybutler/nvm-windows/src/nvm.go:790 +0x220
main.install({0x1140a0e0, 0x6}, {0x29fa65, 0x2})
        C:/Users/corey/OneDrive/Documents/workspace/oss/coreybutler/nvm-windows/src/nvm.go:302 +0x35d
main.main()
        C:/Users/corey/OneDrive/Documents/workspace/oss/coreybutler/nvm-windows/src/nvm.go:87 +0xa69

Debug Output
not supported for this version

Anything else?
No response

This is already resolved in newer versions. We don't re-release older patched versions of NVM4W because we don't have the manpower to maintain every prior version as an independent workflow. This type of development model is not sustainable with NVM4W, but will be part of the Runtime business model.

ok then it that case we just can take off the version support in the github bug template then?

The purpose of having the version listed in the github bug template is to identify when users need to update their installation, or to provide specific workarounds in the event they cannot update, so it's still relevant.


ToTestTests.cs:309-310: Make SingletonAsArgument test to...

The puzzle 60m-de6b1700 from #60m has to be resolved:
https://github.com/DenisZhukovski/ObjectToTest/blob/54d178636b7a952527d7d3dfe024db2788827fb6/tests/ObjectToTest.UnitTests/ToTestTests.cs#L309-L310
The puzzle was created by @DenisZhukovski on 07-Sep-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 60m-de6b1700 has disappeared from the source code, that's why I closed this issue.


Animate 1 transform from a multi-transform CSS statement

I'm trying to make a circular preloader animation such as:

Each element I want to animate has multiple transforms applied to align it to the curve of the circle via a SCSS mixin.
eg: a loop
&:nth-of-type(#{$i}) {
    transform:
    rotate($rot * 1deg)
    translate($circle-size / 2)
    rotate($rot * -1deg);
}

which produces something like:
:nth-of-type(3) {
    transform: rotate(90deg) translate(16px) rotate(-90deg);
}

How would I affect only the translate(16px) to set it to 0 (so it collapses to the center as shown in the gif), but keep the rotate statements intact?
Something like this:
var circles = anime ({
  targets: ['.circle'],
  easing: 'linear',
  duration: 1000,
  translateX: 0,
  translateY: 0
});

Doesn't work, as it blows away all transforms. What are some approaches to this type of animation?

Here is an approach
https://codepen.io/gaougalos/pen/xYGMdj

I know i'm super late to this, but @gaou-piou approach is good.
But since it's not directly related to a bug in the library, please consider using stackoverflow instead in the future.
Thanks!


Created 'Thoroughly check database' button

Closes #1566
Needs OpenSlides/openslides-backend#1421 to work

still missing: warning log state


[CoinbaseEx] Digest fix

Previous code would crash if no secretKey was specified.

Is this a duplicate for #969 ? Thanks

Yes it is
On Jun 6, 2015 8:26 PM, "Jonathan Heusser"<EMAIL_ADDRESS>wrote:

Is this a duplicate for #969
https://github.com/timmolter/XChange/pull/969 ? Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/timmolter/XChange/pull/975#issuecomment-109660976.

closed because of duplicate already merged


support CSV import from original vanguard mutual fund accounts

https://www.bogleheads.org/forum/viewtopic.php?p=7131683#p7131683

Somebody reached out via email saying that they could get one Custodian import to work, but their Vanguard CSV file wasn't working.
One possibility, they said, is that they still have the Original Vanguard Mutal Fund Account...so I will work with them to see if we can figure out the difference in that CSV file format, so the importing logic can be made to work with it also.

Details so far about the older account type's CSV file:

Fund Account Number,Fund Name,Price,Shares,Total Value
0585-xxxxxxxxxx,Vanguard Total Stock Market Index Fund Admiral Shares,97.73,(shares with 3 decimals),(dollars with 2 decimals)
Fund Account Number is two items: The first four numbers in the Fund Account Number tells you the fund, as given on the fund’s page:
Fund Number 0585
https://investor.vanguard.com/investment-products/mutual-funds/profile/vtsax#overview
Fund Number tells you both the name and symbol, so the symbol is not required (for that matter, name is not required either if you have the fund number), so  you may want to strip it leaving just the account number with name in the next field.

Should be solved with this commit: https://github.com/bogle-tools/site/commit/8a9c4a2ae68f54f31b58107cbae9ae0925f3b33c
Sample file: https://github.com/bogle-tools/financial-variables/blob/main/data/custodians/vanguard-orig.csv


feat(ws): allows for optional use of @nestjs/websocket

Adds the ability to not use @nestjs/websockets but still have the module work in general.
@kkoomen can you verify that this is doing what I think it is. Tests pass, and a local check passed, but having another dev look it over would be really nice.

Looks fine. To be honest, I didn't even knew that optional requires were supported through Nest.
If you publish a new version then I'll test it immediately. If there are any problems we can open up a new issue/PR.

Published 0.2.3


Npcs first-class component

Moves https://github.com/webaverse/npc into this repo under the npc component, so npcs get a full standard support in the engine.
This makes NPCs a configured subtype of VRM, rather than a ghost app which puppets a VRM. That should make more sense for the typical art creation process (first you make the avatar and then you add details to it, rather than deciding on some details and then making an avatar for them as an afterthought).
Also updates the local npc definitions to the new component style. The old app will still work for backwards compatibility but they are likely to diverge significantly from here.

Depends on https://github.com/webaverse/totum/pull/94


fps drop when using 3dmigoto

I am using fps unlock to get higher fps( >20). But, I have a question, it looks like when you using fps unlock + 3dmigo, it will drop 20-80 fps compare with using fps unlock alone. In addition,the fps is unstable when using 3dmigo+fps unlock

Third Party isnt supported so it will not rin great i guess

I have no plans to investigate compatibility issues with other software


[Azure.Developer.DevCenter] Enable live tests for the test pipeline

Library name and version
Azure.Developer.DevCenter 1.0.0
Query/Question
Currently we .NET SDK tests in playback mode against pre-recorded sessions. While it works well for running quick validation on PRs it has a few drawbacks. This ticket is to track work related to enabling live tests on the test pipeline for the SDK.
Related work: https://github.com/Azure/azure-sdk-for-net/pull/36245

https://github.com/Azure/azure-sdk-for-net/pull/36245#issuecomment-1732145134


BUG: Titles have no length limit

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to my little test site, 'go.dev'
Open your eyes

Expected behavior
The window isn't three times the size of the screen
Screenshots

(one normal and one ultrawide monitor, mind you)
Desktop (please complete the following information):

OS: Windows
Version 1.3.1

Additional context
The windows shouldn't expand indefinitely

Lnfao


minicdn

@codeskyblue<EMAIL_ADDRESS>

已经停止维护了
                        命令行

<EMAIL_ADDRESS>
签名由 网易邮箱大师 定制
在2018年07月14日 16:44，Works 写道：<EMAIL_ADDRESS>—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/codeskyblue/gosuv","title":"codeskyblue/gosuv","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/codeskyblue/gosuv"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"minicdn (#67)"}],"action":{"name":"View Issue","url":"https://github.com/codeskyblue/gosuv/issues/67"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/codeskyblue/gosuv/issues/67",
"url": "https://github.com/codeskyblue/gosuv/issues/67",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "minicdn (#67)",
"sections": [
{
"text": "",
"activityTitle": "Works",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@wjzhangcsu",
"facts": [
{
"name": "Repository: ",
"value": "codeskyblue/gosuv"
},
{
"name": "Issue #: ",
"value": 67
}
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "codeskyblue/gosuv",\n"issueId": 67,\n"IssueComment": "{{IssueComment.value}}"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueClose",\n"repositoryFullName": "codeskyblue/gosuv",\n"issueId": 67\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/codeskyblue/gosuv/issues/67"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 356459021\n}"
}
],
"themeColor": "26292E"
}
]

可以发一份代码给我吗？
| |
电气信息1112班张文杰
<EMAIL_ADDRESS>|
签名由 网易邮箱大师 定制
On 07/14/2018 17:47, shengxiang wrote:
已经停止维护了
命令行
<EMAIL_ADDRESS>签名由 网易邮箱大师 定制
在2018年07月14日 16:44，Works 写道：<EMAIL_ADDRESS>—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/codeskyblue/gosuv","title":"codeskyblue/gosuv","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/codeskyblue/gosuv"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"minicdn (#67)"}],"action":{"name":"View Issue","url":"https://github.com/codeskyblue/gosuv/issues/67"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/codeskyblue/gosuv/issues/67",
"url": "https://github.com/codeskyblue/gosuv/issues/67",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "minicdn (#67)",
"sections": [
{
"text": "",
"activityTitle": "Works",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@wjzhangcsu",
"facts": [
{
"name": "Repository: ",
"value": "codeskyblue/gosuv"
},
{
"name": "Issue #: ",
"value": 67
}
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "codeskyblue/gosuv",\n"issueId": 67,\n"IssueComment": "{{IssueComment.value}}"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueClose",\n"repositoryFullName": "codeskyblue/gosuv",\n"issueId": 67\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/codeskyblue/gosuv/issues/67"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 356459021\n}"
}
],
"themeColor": "26292E"
}
]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

代码太乱了，不想开源出去，请不要再要了


Issues with Bower dist

main target is dist/funcunit.js, which is missing the browser folder within dist. CJS & AMD version are also missing this folder.

main should be pointing to the global, is it not?

It does actually, I'm tracking down the actual cause. Just putting a bug note here before I forget.

Here's the browser folder in the commonjs build: https://github.com/bitovi/funcunit/tree/v3.0.0/dist/cjs
It does have browser, same for the amd. But it's not showing up in bower?

Just tried it and you are right... very bizarre, should be there, it's in the tag.

we ignore "browser" instead of "/browser" in the bower.json, however I haven't debugged why the main dist isn't working.

Note: jQuery shouldn't be a dependency. Maybe we shouldn't distribute the non-global version via bower at all(which would remove the syn dep as well). Reason is: bower doesn't handle nested dependencies, so the version of jQuery will most likely always conflict with the version the app being tested needs.

jQuery is definitely a dependency, FuncUnit doesn't work without it.  The user can override our version using resolutions: http://jaketrent.com/post/bower-resolutions/

We should probably provide a way for the user to pass in their own jQuery and we create a "new funcunit" based off of that.

Correct, however jQuery 1.11.x should be built into the dist/funcunit.js in noConflict mode. This would allow you to test an app that uses jQuery or any $ lib of any version, independent of the testing framework.

It's not built into the global.  It expects you to put jquery in a

Just noting for this issue: FuncUnit does build jQuery 1.11.x into the global: https://github.com/bitovi/funcunit/blob/master/dist/funcunit.js#L2430
We only expected jQuery to be added separately in v2.0, which was actually my personal mistake. In v2.1.0-pre, this was corrected.


bump token-cli to 2.2 and token-client to 0.3

i removed the patch version locking since really we shouldnt need it internal to the repo

oh note that due to a previous release attempt, monorepo version 1.10 and 1.13 are locked on cli 2.0.17, so this doesnt affect them. test built successfully on 1.14.7 and 1.15.0


[FEATURE] Add drop measuremennt

Description

Summary: Add drop measurement functionality
Contacts: @dshen109 @shakefu
Priority: Medium

Feature
Add drop measurement call to the API, which will speed up tests over drop database calls.
Use cases

User should be able to drop a measurement from the Influx client API.

Solutions and alternatives
Add a drop measurement method to the Influx client API.
Links

https://axiomexergy.atlassian.net/browse/CIRRUS-363

/cc @AxiomExergy/triage

Fixed in 1.8.0.


add resolution field to SingleTimeSeries

Adds resolution field to SingleTimeSeries and avoids making the calculation on the fly. closes #236

cc. @andrewrosemberg this resolves the issue in IS with problems horizon = 1

LGTM


Requesting ability to export Unity Terrain as meshes (FTV-658)

Hi, We are trying to export our scene as USD but we are not able to get the terrain from the scene. When I asked at Unite the speaker said it was possible to export Terrain but when we export we do not get anything. Is there something we are doing wrong? Is it maybe because we are working in HDRP?

You can export terrain as RAW using Unity or as png/tiff/exr using the TerrainToolbox package.
How would you like terrain (a set of dense values/textures) to manifest in USD?

I'm closing this for now, when you get around to providing additional details, feel free to reopen!

I am sorry for the late replay.
So when we are exporting our scenes from Unity with USD we get everything from the scene except the Terrain. We want the terrain as a mesh. It does not need textures or anything. It is just to get the correct lineup of the terrain for the animations.
We are right now using https://wiki.unity3d.com/index.php/TerrainObjExporter <-- this. But the problem there is that it does not line up with the objects from the USD file so we have to manually line it up. Which leaves room for errors.

I see, exporting as a mesh seems reasonable. I guess we would do this:

Use the terrain's world extents to specify vertex positions
Use the texture density to tessellate the mesh

But you should know that there is no guarantee that this will exactly match the Unity mesh, since it is dynamically tessellated.
Also, do you care about the splatmaps, details (grass, etc), trees, physics colliders, wind system, or any other details?

Sounds like its worth a try. and if it does not help in exactness it would at least help us line up the obj!
we don't need any splatmaps or such. Trees would be nice though.

we found a work around for now so no need to rush this.
posting workaround for others: Export terrain with objexporter. then import into unity again and line it up with the terrain. Now export with usd and it will come with you into maya.

Hey! We've moved this feature request to our Roadmap for better internal visibility. If you head over to the Roadmap you can add more detail about your use case (on the 'USD Import ticket') for this feature to help us prioritize as we hope to be able to work on this in the future :)


[ feature ] option to disable UE? links for nodes inside the same group

Normally, I use regular links inside groups, and UE? nodes to make connections between groups.
It would be easier to prevent loops, if there was an option to disable EU? links, for nodes inside the same group.
In this example, I have a ControlNet group.
Since it uses UE? nodes it has priority over the [ Prompts Everywhere ] node ( image 1 ).
So, to disable ControlNet, I just need to mute the group ( image 2 ).
This works very well !
But to send conditioning to all other groups in the workflow, and prevent a loop, I need to use multiple UE? nodes ( image 1 ).
I'd like for this to work, with the same UE? node sendind to all groups, without creating a loop ( image 3 )
This would also be useful, if I want to save the ControlNet group as a template.
This way the template would be compatible with more workflows, without modifications.

Image 1 - to prevent a loop, I need to use a set of UE? nodes ( positive and negative ) for each set of groups in the workflow,
( e.g. all groups with the prefix/name "Sampler"and "Upscalers" )

Image 2 - I just need to mute the group to disable ControlNet ( the priorities are great ! )

Image 3 - If I use a single set of UE? nodes to send to all groups in the workflow, I also create a loop.

I just noticed you already have a setting to do the opposite thing : Send only within my group(s)
Can you add this other setting to the right click menu, for each node ?
I was thinking about a global setting, but this would be even better !

And the restriction stays on, even if I load the nodes as a template ! That's great !
I also have the [ aegisflow_utility_nodes ] which creates a group for the template, when it's loaded.
https://github.com/aegis72/aegisflow_utility_nodes
So I just need to load the template and it will be connected automatically.
( I Just need another UE in the workflow to connect the image ).

Take a look at the latest update - has options for group and color to

send to all
send only to matching
send only to not matching

See if that's what you need!


support absolute URL redirects

https://github.com/quintype/page-builder/issues/2757

Closing PR because mongoDb document is limited to 16MB, the 40K redirects alone are coming to >18MB
Instead, working on https://github.com/quintype/page-builder/issues/2807


PANIC while creating storage container policy

Hi,
I'm using azurite version: 2.6.5 in a docker container on Windows 10 and docker-ce in WSL bash.
When I try to create a storage container policy with:
export AZURE_STORAGE_CONNECTION_STRING=BlobEndpoint=http://<IP_ADDRESS>:10000/devstoreaccount1;QueueEndpoint=http://<IP_ADDRESS>:10001/devstoreaccount1;TableEndpoint=http://<IP_ADDRESS>:10002/devstoreaccount1;DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;
docker run --rm -d -p 10000:10000 arafato/azurite:2.6.5
az storage container create --name test
az storage container policy create --name read --permission rl --container-name test
I'm getting the following error:
PUT /devstoreaccount1/test?restype=container&timeout=30 201 9.546 ms - 0
GET /devstoreaccount1/test?comp=acl&restype=container 200 6.874 ms - 59
PANIC Something unexpected happened! Blob Storage Emulator may be in an inconsistent state!
TypeError: Cannot read property '0' of undefined
at parseStringAsync.then (/opt/azurite/lib/xml/Serializers.js:19:81)
at tryCatcher (/opt/azurite/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/opt/azurite/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/opt/azurite/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromiseCtx (/opt/azurite/node_modules/bluebird/js/release/promise.js:606:10)
at Async._drainQueue (/opt/azurite/node_modules/bluebird/js/release/async.js:138:12)
at Async._drainQueues (/opt/azurite/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
PANIC Something unexpected happened! Blob Storage Emulator may be in an inconsistent state!
TypeError: Cannot read property '0' of undefined
at parseStringAsync.then (/opt/azurite/lib/xml/Serializers.js:19:81)
at tryCatcher (/opt/azurite/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/opt/azurite/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/opt/azurite/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromiseCtx (/opt/azurite/node_modules/bluebird/js/release/promise.js:606:10)
at Async._drainQueue (/opt/azurite/node_modules/bluebird/js/release/async.js:138:12)
at Async._drainQueues (/opt/azurite/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
PANIC Something unexpected happened! Blob Storage Emulator may be in an inconsistent state!
TypeError: Cannot read property '0' of undefined
at parseStringAsync.then (/opt/azurite/lib/xml/Serializers.js:19:81)
at tryCatcher (/opt/azurite/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/opt/azurite/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/opt/azurite/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromiseCtx (/opt/azurite/node_modules/bluebird/js/release/promise.js:606:10)
at Async._drainQueue (/opt/azurite/node_modules/bluebird/js/release/async.js:138:12)
at Async._drainQueues (/opt/azurite/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async.js:17:14)js:17:1
4)
at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async
.js:17
:14)
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async
.UT /devstoreaccount1/test?comp=acl&restype=container - - ms - -
js:17:14)
at runCallback (timers.js:763:18)                                                                    )    at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
PUT /devstoreaccount1/test?comp=acl&restype=container - - ms - -                                                  )
PANIC Something unexpected happened! Blob Storage Emulator may be in an inconsistent state!           js:17:14TypeError: Cannot read property '0' of undefined                                                         .
at parseStringAsync.then (/opt/azurite/lib/xml/Serializers.js:19:81)
at tryCatcher (/opt/azurite/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/opt/azurite/node_modules/bluebird/js/release/promise.js:512:31
)   at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async
at Promise._settlePromise (/opt/azurite/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromiseFromHandler (/opt/azurite/node_modules/bluebird/js/release/promise.js:512:31)    at Promise._settlePromise (/opt/azurite/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromiseCtx (/opt/azurite/node_modules/bluebird/js/release/promise.js:606:10)
at Async._drainQueue (/opt/azurite/node_modules/bluebird/js/release/async.js:138:12)    at Async._drainQueues (/opt/azurite/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:763:18)    at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
PANIC Something unexpected happened! Blob Storage Emulator may be in an inconsistent state!
TypeError: Cannot read property '0' of undefined
at parseStringAsync.then (/opt/azurite/lib/xml/Serializers.js:19:81)
at tryCatcher (/opt/azurite/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/opt/azurite/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/opt/azurite/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromiseCtx (/opt/azurite/node_modules/bluebird/js/release/promise.js:606:10)    at Async._drainQueue (/opt/azurite/node_modules/bluebird/js/release/async.js:138:12)
at Async._drainQueues (/opt/azurite/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues [as _onImmediate] (/opt/azurite/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)PUT /devstoreaccount1/test?comp=acl&restype=container - - ms - -
PUT /devstoreaccount1/test?comp=acl&restype=container - - ms - -
PUT /devstoreaccount1/test?comp=acl&restype=container - - ms - -
PUT /devstoreaccount1/test?comp=acl&restype=container - - ms - -

@nobiehl thanks for reporting this and the detailed repro steps.
I'm picking up where @arafato left off, and I'll add this to the list that we are working on addressing.
We're currently reviewing all the security issues raised in the projects dependencies, and deciding on how to address those, once that is complete, I hope to catch up on the outstanding issues.

Issue is resolved, but we want to ensure that we have behavioral parity with Azure storage for the case of malformed XML.
Creating a new issue for that.


Update moment, pin bootstrap-table to local

what a pain. Had regressions with bootstrap-table here. Closing in favor of #279  and a new PR to deal with SRI still to come.


Clarify imports

Worth clarifying what the imports should be for these code examples?
Unless you deliberately decided not to add these import statements because of the difference between using the PyPI package vs. locally saving and importing aws_error_utils.py, of course.

Is this confusing, though? A boto3 user knows they need import boto3, and the other functions obviously (I think) come from this package, or at least that's my thinking. It just seems needlessly verbose to put it in all the snippets, and I haven't really seen the docs for other packages do it that way (for snippets, longer examples definitely should have them for completeness).

Hi Ben, it's your call, obviously. I'd personally prefer to see 'complete' examples.
The reason I raised this was because when I looked at the first example, it included except errors.NoSuchBucket as error: without any indication what errors was. There's no import of that name and there's no file in the repo called errors. I then had to read the source of aws_error_utils.py to see that it defined errors. Anyhow, just sharing how it wasn't obvious first time reading the example code.

I can see that with the new errors object it's a lot less obvious.


Feat/require quantity in the add-to-cart route

And other improvements about cart

:tada: This PR is included in version 9.0.0 :tada:
The release is available on:

9.0.0
GitHub release

Your semantic-release bot :package::rocket:


Public Cloud Product Owner Website Design

Describe the Issue
The team needs to build a new Public Cloud Website with the product owners being the primary persona/ target user
Additional Context
The Content Audit and Information Architecture for the website is currently in progress.
Acceptance Criteria

Upon completion of the information architecture, we will need to work on the wireframes as per the new IA.

Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

Closing this ticket since we will directly be populating content into WordPress.. no wireframes required


Unclear documentation

https://github.com/tudo-aqua/bgw-core/blob/0dd6dd9c8943e992cfa65fd7aaf5204d485d6b7f/src/main/kotlin/tools/aqua/bgw/core/BoardGameApplication.kt#L47
The description, on when the background visual is shown, should be more clear.

Check improved doc and close the issue if its sufficient now.


Add code completion for modules

YARA's module system should have some kind of completion system for helping a user figure out what attributes are available
Examples of available attributes
pe.entry_point == 0x1000
cuckoo.http_request(/someregexp/)

Documentation:
https://code.visualstudio.com/docs/extensionAPI/language-support#_show-code-completion-proposals

^^ closer to providing this. Most of the enum values like pe.DLL, pe.SYSTEM, etc. are difficult to differentiate between, but the subclasses will only show the methods and properties available to them

Pushed in v1.3.0


Split tests into matrix suites

What is the context of this PR?
Describe what you have changed and why, link to other PRs or Issues as appropriate.
How to review
Describe the steps required to test the changes (include screenshots if appropriate).
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

It looks like the virtual environment is being recreated for each of the matrix, I would test to see if you can use the cache from the initial python dependencies and node dependences install. That would save over a minute for each matrix.

 Speed up runner GitHub Actions (3 SP)


Wrong IP Address being used for queryDevice_Direct

[11/3/2021, 5:02:53 PM] [homebridge-kumo] queryDevice_Direct error: FetchError: request to http://<IP_ADDRESS>/api?m=24f1068d5ae939f69281368e4f9cb0320bc0e720e4a5ab9111a0ab6a292ae9d7 failed, reason: connect ECONNREFUSED <IP_ADDRESS>:80

The actual Kumo device is located at <IP_ADDRESS>. I'm not sure where the plugin is getting the 205 address from.

It must have changed from an original setting of 205. Are you by any chance using DHCP in your wifi router?
I strongly recommend if you want to use direct access that the devices are kept on static IPs. If not, whenever the router decides to give out a different IP address you will get this error for a period of time. Unfortunately, I have not found out a way to override the Kumo derived IP address and it can take minutes/hours or longer to update.
I had this problem once and moved to static IPs and its been good since. If you are unable to change to static IP addresses for your Kumo devices then I suggest unchecking the direct access button and just using the cloud based API.

I already have the IP reservation (static IP) set to 200 for this device. And it has been connected to the 200 address for over a week. So is this a kumo cloud issue that they do not update their own cached IP address associated with the device?

I moved the reservation to 205 and now it's working. Still seems like a bug in that it never updates the IP address if it changes.

Yeah it's not ideal. The plugin gets the IP address reported from the Kumo cloud. So if the two are out of sync, you get the error. I could mask the error and just have the plugin revert to an indirect connection but this is also suboptimal as the user is expecting a 'direct' connection to be used if you check that box in the config. I think documentation is the better approach and making it clear that the direct connection should be used with static IPs.

@fjs21 is there a log line which shows the directAccess IP being attempted?

If you turn on debug in the homebridge UI. You should be able to tell.
For now hold off as I think I found a bug in my new code that means that it won't wait until you get authenticated before proceeding. I need to add an "await".

Ok. I have added additional logging so you can tell if directAccess (via local IP) was successful and additional log entries to demonstrate that a connection was successfully completed. These should appear shortly after homebridge is restarted.

@esetnik just curious, what app that?

@esetnik just curious, what app that?

Eero iOS


MaxListenersExceededWarning

Version
3.9.3
Environment info
  System:
    OS: macOS 10.14.5
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 11.9.0 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.5.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 75.0.3770.142
    Firefox: 68.0
    Safari: 12.1.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

run vue ui from terminal
switch projects a few times with dropdown (not always, but frequently)
check terminal

What is expected?
No errors
What is actually happening?
$ vue ui
🚀  Starting GUI...
🌠  Ready on http://localhost:8000
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 exit listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGABRT listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGALRM listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGHUP listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGTERM listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGVTALRM listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGXCPU listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGXFSZ listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGUSR2 listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGTRAP listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGSYS listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGQUIT listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGIOT listeners added.  I suggest checking if there's not folder with large number of files that can be move elsewhere (e.g. to node_modules) or change node max listeners limit.

Seems like you have large number of files in your repository

Thanks for the tip, I’ll check this

同样的问题，找不到解决方案，但不影响构建，且只有本地开发的时候出现。
将 const rawArgv = ['serve']; 换成 const rawArgv = ['build']; 就没有了
`
const Service = require('@vue/cli-service/lib/Service');
const minimist = require('minimist');
const { error } = require('@vue/cli-shared-utils');
const service = new Service(process.env.VUE_CLI_CONTEXT || process.cwd())
const getCommandArgs = function (rawArgv) {
return minimist(rawArgv, {
boolean: [
// build
'modern',
'report',
'report-json',
'inline-vue',
'watch',
// serve
'open',
'copy',
'https',
// inspect
'verbose'
]
})
}
const rawArgv = ['serve'];
const args = getCommandArgs(rawArgv);
const command = args._[0]
// 中间省略一大段业务代码
service.run(command, args, rawArgv).catch(err => {
error(err)
process.exit(1)
})
`
控制台就会输出
Starting development server...
10% building 2/2 modules 0 active(node:27476) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 upgrade listeners added to [Server]. Use emitter.setMaxListeners() to increase limit

For anyone who's looking for a temporary fix which can ignore this warning, simply add require('events').EventEmitter.defaultMaxListeners = 50; to vue.config.js (source).
Again, this is just to ignore this warning and it is essentially not fixing the real issue.

somehow this does increase my listeners.


why keras.layers.MultiHeadAttention q-dim don't / heads?

Hi @zhanlie2008, thanks for reaching out. The issue backlog is not the best place for support requests. Can you repost this to one of the forums below? That way your question will have more visibility.

TensorFlow forum
Keras mailing list

Thanks!


[nix] Filtering sources using a whitelist approach

The Haskell build is quite expensive, we aggressively filter its src input to make sure we that the editor artifacts and other mutable state files don't end up triggering a rebuild.
We take advantage of this filtering rework to move back the haskell sources filtering to the edge: we clean the derivation src before sending it to cabal2nix projects list. Doing this allow us to apply a package-specific filter instead of a generic one.
After applying this PR, altering the state.json file does not lead to a curiosity rebuild anymore.

This seems really great, thanks !


Fix IPv6 Error on Win10 machine with trunk serve

With a brand new app and this template, I got an error running trunk serve. This seems to be due to the use of an IPv6 address which my version of Win10 doesn't seem to support.
ERROR error opening browser error=Custom { kind: Other, error: "Launcher "cmd" "/c" "start" "" "http://::1:8080/\" failed with ExitStatus(ExitStatus(1))" }

Adding the IPv4 address first in the Trunk.toml fixed this.
I'm not sure what impact this would have on other platforms?

Its possible as well this is fixed in a later version of trunk? https://github.com/trunk-rs/trunk/issues/824

Sounds good. We will swap Trunk anyways for bevy run web by @TimJentzsch, but fixing this until then is good


RFC 7233 (range requests)

Hey @dominictarr , I implemented HTTP1.1 range requests (RFC 7233) for blobs.
I needed this to better support video playback. Browsers tend to refuse to loop videos otherwise and seeking in videos requires range requests. It's also great for extracting embedded thumbnails from JPEGs etc.
I added tests including for the old functionality (there were none)

This is awesome!!!
I love your PRs there are always tests!
Merged into 1.0.0, and also released<EMAIL_ADDRESS>to use this.

oh I also added a little bit of docs, so that there is a link to the rfc.

It's also great for extracting embedded thumbnails from JPEGs etc.

I did not know you could embed a thumbnail in a jpg!

:) Thank you, @dominictarr , I love your code too!

I did not know you could embed a thumbnail in a jpg!

Cameras do that. Probably to reduce their own processing time when displaying a super high-res image on their low res display. EXIF data gives you offset, length and type of the embedded thumbnail.

@dominictarr how do you feel about publishing this as 0.5.0? The way you did it now (1.0.0) prevents it from being picked up by older versions of ssb-ws (which is a bummer, because I am using an older version of ssb-ws, I am on sbot 11.3.x). After all, it's not a breaking change but a feature addition.
0.5.0 and 1.0.0 being identical would be a bit weird, but should cause no harm, I guess?


Set unavailable property when issue retrieving August information

Description:
Sets the unavailable property for the entity if there is an issue when trying to retrieve the status for the August lock, sensor, and/or doorbells.
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass

Nice 👍


ImportError: cannot import name 'ChaliceIntegration' from 'sentry_chalice'

Hi! Thanks for this module.
I installed it using pip install sentry_chalice (or with Poetry using poetry add sentry_chalice).
But then I got ImportError: cannot import name 'ChaliceIntegration' from 'sentry_chalice' when importing it. Did I miss something, or is it too early to use the module?

@bolinocroustibat can you upgrade your version (pip install -U sentry-chalice)? We just released 0.1.0 to PyPi

Thank you, it works now.


Devstack cancellations

When exiting devstack, there are often errors logged that are unnecessary, or in some cases delay when the process actuall exits.
This commit checks some obvious context cancellation errors and gives the code a chance to exit without logging and continuing.
Should also fix https://github.com/bacalhau-project/bacalhau/issues/3484

Summary by CodeRabbit

Refactor

Improved error handling in IPFS client and node operations.
Enhanced logging clarity by removing unused statements and adjusting error logging conditions.

Bug Fixes

Ensured appropriate error messages are returned when no swarm addresses are found in IPFS operations.

Chores

Added a comment regarding using a single address for libp2p due to concurrency issues.
Introduced handling for the context being canceled during peer connection attempts.

@coderabbitai pause


Update setup.py

Add rest of used packages to install_requires. So pip can install all together.
Heading toward #95.
(does not resolve numpy and cython) being required before hand.

Thanks!


having followed get started and added swagger

I am getting
ArgumentException: An item with the same key has already been added. Key: BearerAuth
upon running the api solution

what was the issue? registered swagger or something?


Broken references, no longer able to load any projects from platforms folder in gamestatemanagement

Unfortunately this set of samples is no longer usable, the references are not packaged with the solution even if you download all the folders referenced manually and rebuild it seems that MonoGame\v3.0\MonoGame.Content.Builder.targets prevents loading all projects within the solution beyond the core making it unusable to learn from.

Updated the checkout for the GSM sample to the latest 3.8 branch, which is fully working


Add support for vscode via the browser

it would be really useful to switch between vscode and mage.ai UI, when developing a pipeline, with code server you get all the best parts of vscode , like plugins but it's via the browser so you can have a standard env for developers.
https://github.com/coder/code-server

cc: @johnson-mage @tommydangerous


Both SAS Launched Jobs (node and user) do not show activity

Hi,
I just installed the latest version of the Viya 4 monitoring project, and both the SAS Launched Jobs - Node Activity and SAS Launched Jobs - User Activity, show no data, although I clearly have sas-launcher- pods running n my namespace.
Is there anything I need to configure to make sure these 2 reports work ?
The rest (CAS, Rabbitmq, postgres, ...) all show correct data)
Bye,
Wouter.

Hi Wouter,
I believe in our recent efforts to support Workload Orchestrator and update the SAS Jobs dashboards, we may have affected the display of non-SWO jobs. I believe it comes down to differences in the labels on the job pods, but I haven't investigated this fully yet.
Could you provide me with a list of the labels on a few of the jobs you are running?

Hi @BryanEllington ,
Here's one :
Labels:       controller-uid=9f32e28a-d6f6-462d-bbcd-8231335d998b
job-name=sas-launcher-c2ca0a56-37a0-4a3c-81d8-ec4f36e7bc93
launcher.sas.com/job-type=compute-server
launcher.sas.com/requested-by-client=sas.studio
launcher.sas.com/username=snljro
sas.com/created-by=sas-launcher
And this was indeed a job launched in SAS Studio, without Workload Orchestrator !
When I do the same on a system WITH Workload Orchestrator these are the labels I see :
Labels:       app=sas-workload-orchestrator
launcher.sas.com/job-type=compute-server
launcher.sas.com/requested-by-client=sas.studio
launcher.sas.com/username=sbxwvw
sas.com/created-by=sas-launcher
swo.sas.com/containerName=sas-programming-environment
swo.sas.com/jobID=235
swo.sas.com/jobName=sas-launcher-default
swo.sas.com/queueName=default
swo.sas.com/realm=viya401
So I guess the labels in common are :
launcher.sas.com/job-type=compute-server
launcher.sas.com/requested-by-client=sas.studio
launcher.sas.com/username=
sas.com/created-by=sas-launcher
Could this help ?
Bye,
Wouter.

Are you seeing dashboard data for jobs launched with SWO, but not without?

Hey Brian,
I had not yet deployed the viya4-monitoring framework in that cluster, but yes, I can confirm I can see the user activity jobs in a cluster with Workload Orchestrator :
@.***
@.***
Bye,
Wouter.
From: Bryan Ellington @.>
Sent: Friday, December 17, 2021 1:55 PM
To: sassoftware/viya4-monitoring-kubernetes @.>
Cc: Wouter Van de Weghe @.>; Author @.>
Subject: Re: [sassoftware/viya4-monitoring-kubernetes] Both SAS Launched Jobs (node and user) do not show activity (Issue #246)
EXTERNAL
Are you seeing dashboard data for jobs launched with SWO, but not without?

Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-monitoring-kubernetes%2Fissues%2F246%23issuecomment-996700557&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767953751|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=o%2BJ%2FJlIoVggpvLdxgDxaCg%2BQaisUgut9GQezOZjOIso%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGNOZLIGVOMT7Q7BUOVZA3LURMXITANCNFSM5JR2EVVQ&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767963708|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=VwfrXS%2BvF18t%2BXt5NJpDxLBILfm9fEtRQVQ3RCIiFS8%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767963708|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=i03W%2FvB76Qwhm5wUQ%2FOH5X7ELol1UF8Er%2FiW4lrs6%2Bk%3D&reserved=0 or Androidhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767973666|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=iSXFT87%2BSifu8mTJfLcgzEnnNOLA3o%2BPg%2FFItuz77lU%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

And by the way  :
These 2 dashboard items are also the only ones that are not "tagged" :
@.***
Thanks,
Wouter.
From: Wouter Van de Weghe
Sent: Friday, December 17, 2021 2:09 PM
To: sassoftware/viya4-monitoring-kubernetes @.>; sassoftware/viya4-monitoring-kubernetes @.>
Cc: Author @.***>
Subject: RE: [sassoftware/viya4-monitoring-kubernetes] Both SAS Launched Jobs (node and user) do not show activity (Issue #246)
Hey Brian,
I had not yet deployed the viya4-monitoring framework in that cluster, but yes, I can confirm I can see the user activity jobs in a cluster with Workload Orchestrator :
@.***
@.***
Bye,
Wouter.
From: Bryan Ellington<EMAIL_ADDRESS>Sent: Friday, December 17, 2021 1:55 PM
To: sassoftware/viya4-monitoring-kubernetes<EMAIL_ADDRESS>Cc: Wouter Van de Weghe<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [sassoftware/viya4-monitoring-kubernetes] Both SAS Launched Jobs (node and user) do not show activity (Issue #246)
EXTERNAL
Are you seeing dashboard data for jobs launched with SWO, but not without?

Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-monitoring-kubernetes%2Fissues%2F246%23issuecomment-996700557&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767953751|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=o%2BJ%2FJlIoVggpvLdxgDxaCg%2BQaisUgut9GQezOZjOIso%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGNOZLIGVOMT7Q7BUOVZA3LURMXITANCNFSM5JR2EVVQ&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767963708|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=VwfrXS%2BvF18t%2BXt5NJpDxLBILfm9fEtRQVQ3RCIiFS8%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767963708|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=i03W%2FvB76Qwhm5wUQ%2FOH5X7ELol1UF8Er%2FiW4lrs6%2Bk%3D&reserved=0 or Androidhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|wouter.van.de.weghe%40sas.com|439c0e0a22c94a94b64308d9c15c600f|b1c14d5c362545b3a4309552373a0c2f|0|0|637753424767973666|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=iSXFT87%2BSifu8mTJfLcgzEnnNOLA3o%2BPg%2FFItuz77lU%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Hi Bryan, any update to this issue?
We're seeing the same issue in our deployment (both SAS dashboards showing job activities are empty). Our order is not using Workload Orchestrater. My suspicion is that one of the Prometheus rules is not working correctly (sas_launcher_pod_info)?
Any hint how to fix this would be highly appreciated!

I took a closer look at the issue and hopefully found a solution.
The issue is caused by the expression used to calculate the sas_launcher_pod_info rule/variable. This variable assumes that a specific metric called sas_job_info is available in the pushgateway to provide information about SAS jobs. However, this information will not be available if the SAS deployment does not contain the SAS Workload Orchestrator component.
A simple "solution" would be to remove this particular metric from the expression. Can you confirm that this is a suitable approach for sites without SWO? The next command patches the existing rule (it assumes that a recent version of the yq utility is installed):
kubectl get prometheusrule sas-launcher-job-rules -n monitoring -o yaml | yq eval 'del(.metadata.resourceVersion, .metadata.uid, .metadata.annotations, .metadata.creationTimestamp, .metadata.selfLink, .metadata.managedFields, .status)' - | yq eval '.spec.groups[0].rules[0].expr = "sum without(container, endpoint, instance, job, service) ((label_replace(kube_pod_labels{pod=~\"sas-launcher-.+-.+-.+-.+\"}, \"job_pod\", \"$1\", \"pod\", \"(.+)\")) * on(pod) group_left(node) kube_pod_info{pod=~\"sas-launcher-.+-.+-.+-.+\"})"' - | kubectl apply -f -

sas_job_info is provided by SWO. It looks like:
# HELP sas_job_info Information on pending and running SAS jobs
# TYPE sas_job_info gauge
sas_job_info{job_name="my-job",queue_name="default",job_pod="sas-launcher-wxyz-abcd-abcd-6789"} 1

The dashboards have job name and queue filters. I'm not sure they will display jobs without those fields. Having "friendly" job and queue names helps users filter the jobs. Using labels directly from kube_pod_labels had issues because of the tight character restrictions for Kubernetes label values.  The other purpose of sas_job_info was to reduce inaccuracies in the jobs dashboards from "joining" too many other metrics collected from different sources causing some panel values to out of sync with others.
We know we have an issue here but just haven't settled on the right fix to handle both SWO and non-SWO jobs consistently while still supporting the requirement job and queue names and the special characters they can contain.
We've also avoiding imposing additional dependencies on the user environment like yq. We're going to be moving to a containerization model that will address this and give the scripts access to whatever utilities or programs (like Python scripts) might be needed.
I wish I had a better answer, but it is something we're looking at and hope to address soon.

Hi @BryanEllington , we are having the same problem and I would like to confirm that at the moment if we want to use the two dashboards, is it assumed that this requires the purchase of a SAS Workload Orchestrater license? Thank you!

@DoritozX @wweghe These dashboards only report on SAS Workload Orchestrator jobs, so a SWO license is required.  Support for non-SWO jobs is on our list of future enhancements but we don't have a timeline for when we will deliver it.  We have updated the Grafana dashboards to include tags indicating these dashboards are SAS Viya related and also to indicate they are related to SWO.  I think that covers the open questions so I'm going to close this issue.  Regards.


Remove redundant String extension

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

This is a slight extension of https://github.com/Homebrew/brew/pull/14452
Library/Homebrew/extend/string.rb is just a wrapper of active_support/core_ext/object/blank, which is already required in global.rb.
It's also required in a few files in Library/Homebrew/rubocops, but none of them appear to use blank?.

Thanks again @dduugg!


[zh-cn]Resync job.md

A min change about zh-cn
Preview:https://github.com/kubernetes/website/pull/35290/files?short_path=9e76853#diff-9e7685352516243d51fb7e00e4c6ec0b45dbe060e85e535891ea2413da30b273

A more impressive internet-image of you might come from your daily traces and efforts except for frequent trival changes. 😺

/lgtm

A more impressive internet-image of you might come from your daily traces and efforts except for frequent trival changes. 😺

You are my role model and strength, hats off to the big guy

/approve


Implement threadlocks on CLI functions.

This is a continuation of https://github.com/mitsuhiko/click/issues/292. It has also been discussed with @mitsuhiko in IRC.
The problems:

If you use threads in your CLI app, and they all use click.echo, you get garbage on stdout (written data is mixed up).
If one thread uses click.prompt, and some other thread uses click.echo, you get garbage.
The list goes on...

The solution: Implement a global UI lock that prevents multiple threads from simultaneously writing to stdout.
See IRC log: https://botbot.me/freenode/pocoo/2015-01-24/?msg=30379697&page=6

I'm not sure if we should implement the fast path for click.echo as mentioned in IRC.
Basically I'd like the locking support to be non-transparent, i.e. make the user provide a lock rather than having automatic support for threading. The primary reason is that the user might use multiprocessing (or anything else) instead, which would require a different lock.
This could happen in combination with https://github.com/mitsuhiko/click/issues/292: The UI lock could live on the context in the form of an attribute ctx.ui_lock, with a default value of None, which equates to the current behavior (no locking at all). If the user then uses threading, they could set this value to their custom lock.
The user has to explicitly "initiate" locking, but as a consequence, the lock is exposed to the user as well. This is useful if one thread is launching e.g. a "configuration wizard" (a series of prompts) and not only wants to avoid overlapping prompts, but also wants to prevent other threads from writing between the wizard's prompts. This problem is easily solved by setting Click's lock to an RLock instance and holding that lock while the wizard is running.
We could still have simple thread locking with a fast path as default, but I don't the special casing is worth it. For anything nontrivial, the user almost certainly wants to override it.

What we also could do is to provide an interface for making the acquiring function known to the lock. This would allow for a custom threadlock wrapper that decides on a per-function basis whether to use an eventual fast path or not.

And I just realized that providing the same ctx in each subprocess of multiprocessing-based systems is impossible :( So I suppose the object can't live on the context if we want to support multiprocessing.

Closing this because it's a bad idea: click.echo blocking on prompts is a bad idea performance-wise. I'm not sure how else to solve this problem, but any effort should probably happen in a contrib package.


feat(Backend): Add Expenses table

Codecov Report

Merging #41 (2c6ef55) into main (cdfab5f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #41   +/-   ##
=========================================
  Coverage     44.66%   44.66%
  Complexity       47       47
=========================================
  Files            25       25
  Lines           206      206
  Branches          8        8
=========================================
  Hits             92       92
  Misses          111      111
  Partials          3        3

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 cdfab5f...2c6ef55. Read the comment docs.

Codecov Report

Merging #41 (2c6ef55) into main (cdfab5f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #41   +/-   ##
=========================================
  Coverage     44.66%   44.66%
  Complexity       47       47
=========================================
  Files            25       25
  Lines           206      206
  Branches          8        8
=========================================
  Hits             92       92
  Misses          111      111
  Partials          3        3

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 cdfab5f...2c6ef55. Read the comment docs.


Run cargo-fmt

Depends on #75. Splitting this up to as this is pretty noisy.

Travis build is broken for Unrecognized option: 'write-mode' in the format command line. This was the cargo +nightly fmt -- --write-mode=diff bit added to ensure the code was correctly formatted or to cause a build break otherwise.


_pywrapfst. FstOpError: Operation failed

Why there is such problem?

Could you provide your input text for us to repro this issue

Could you provide your input text and running cmd for us to repro this issue

Hi I think I couldn't reproduce the error. I will close this issue for now until I encounter the same issue again. Thanks a lot for your reply.

您好，我也遇到了此问题：
(wenetITN) liuhangchen@G08:~/WeNetITN/WeTextProcessing-master/itn/chinese$ weitn --text "二点五平方电线"
Traceback (most recent call last):
File "/storage1/liuhangchen/anaconda3/envs/wenetITN/bin/weitn", line 8, in
sys.exit(main())
File "/storage1/liuhangchen/anaconda3/envs/wenetITN/lib/python3.8/site-packages/itn/main.py", line 43, in main
normalizer = InverseNormalizer(
File "/storage1/liuhangchen/anaconda3/envs/wenetITN/lib/python3.8/site-packages/itn/chinese/inverse_normalizer.py", line 41, in init
self.build_fst('zh_itn', cache_dir, overwrite_cache)
File "/storage1/liuhangchen/anaconda3/envs/wenetITN/lib/python3.8/site-packages/tn/processor.py", line 74, in build_fst
self.build_tagger()
File "/storage1/liuhangchen/anaconda3/envs/wenetITN/lib/python3.8/site-packages/itn/chinese/inverse_normalizer.py", line 44, in build_tagger
tagger = (add_weight(Date().tagger, 1.02)
File "/storage1/liuhangchen/anaconda3/envs/wenetITN/lib/python3.8/site-packages/itn/chinese/rules/date.py", line 25, in init
self.build_tagger()
File "/storage1/liuhangchen/anaconda3/envs/wenetITN/lib/python3.8/site-packages/itn/chinese/rules/date.py", line 29, in build_tagger
digit = string_file('itn/chinese/data/number/digit.tsv')  # 1 ~ 9
File "extensions/_pynini.pyx", line 1033, in _pynini.string_file
File "extensions/_pynini.pyx", line 1109, in _pynini.string_file
_pywrapfst.FstIOError: Read failed


Can not change plugin version when plugin changelog page opened.

VSCode Version: 1.44.2
OS Version: Win10

Steps to Reproduce:

Install the latest version of intelliCode or other java pack plugin
Install another version on the plugin changelog page

Result:
Install another version button doesn't work.

I can repro in 1.44.2 but not in 1.45.0-insider
Probably fixed by https://github.com/microsoft/vscode/issues/88284#issuecomment-615496315

@EricZhangzf Could you check if this is fixed in 1.45? Download: https://code.visualstudio.com/insiders/

@chrmarti  can not repro in 1.45, Fixed

Thanks, closing as duplicate of https://github.com/microsoft/vscode/issues/88284.


Optionalize nb_tests for bayesian

We should not force tests on the Bayesian example NB because we do not require PyMC 3.
I'm not sure if there is a better way to check if the test can be run.
Closes #149.

Well, looks like this serendipitously fixed the travis issue. I don't think this is the desirable way to fix this, though. What do you think @twiecki?

Wow, that is odd but we'll take it!

Actually might also be randomly fixed irrespective of the change.

Originally I was thinking that when we try to import PyMC 3, numpy.core.multiarray fails to import, and with this new change it skips over that test. But I think your latter idea might be the case.

I just restarted a separate branch https://travis-ci.org/quantopian/pyfolio/builds/88759661 that now shows the same error, seems like conda fixed it.

Ah, great


Log view enhancements

[ ] Button to close current file.
[ ] Button to open tail of file

Filtering to today doesn't work on onebit.


feat: Japanese, Chinese, Spanish and Galician translations for SwapProgress

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove no-mir bots.

Needed to merge rust-lang/rust#35764.

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

We'll pick this up on the next buildbot restart, but that may be awhile


Refactor Drag & Drop events

This is a work item for #685.
Pages:

[ ] https://developer.mozilla.org/en-US/docs/Web/Events/drag
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/dragend
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/dragenter
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/dragexit
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/dragleave
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/dragover
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/dragstart
[ ] https://developer.mozilla.org/en-US/docs/Web/Events/drop

Here the targets are difficult, see https://html.spec.whatwg.org/multipage/dnd.html#dndevents
The pages itself mention Document and Element, which I think sound like reasonable targets.

So, here I'm hitting the same case as Will had with pointer events. The event handler properties are documented on a mixin page called GlobalEventHandlers:
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondrag
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondragend
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondragenter
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondragexit
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondragleave
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondragover
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondragstart
https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/ondrop
The actual targets are Document and Element, so that's where web devs actually interact with them, but for spec authoring convenience the authors came up with GlobalEventHandlers to not duplicate the handlers in their texts. MDN followed this convenience and documented this non-observable mix-in as well. I'm unclear if web devs actually understand non-observable interfaces. It is explained on the GlobalEventHandlers page, but is it practical when looking things up?
See also my previous comment about GlobalEventHandlers here https://github.com/mdn/sprints/issues/949#issuecomment-464733445. I think we will hit this with many event pages and we should make a call on how we want to proceed.
@chrisdavidmills @wbamberg, do you have thoughts on this and https://github.com/mdn/sprints/issues/949#issuecomment-464733445? I'm afraid this is sort of opening the grand debate around "do we document mixins or not?" :-/

Part of me thinks that the event pages should be together with their "on" event handler pages.
Another part of me thinks that all this mix-in business is confusing and we should rather duplicate pages than to follow the specs.
I'm really torn here. Also no idea what to do now vs. what to do ideally when we have the time.

Annoying as it is, I think the only thing we can do now is to leave the on... pages where they are, put the event pages below the interfaces they are fired on, and link both from the interface landing page as agreed.
If we try to start moving on... pages around now and deleting mixin landing pages, etc., that makes things inconsistent and opens up a rabbit hole below this work that we don't have time for.
We need to have agreement and a definite plan of what to do about mixin pages and then execute it, probably as part of the maintenance work we are doing this year. I'd be more than happy to duplicate pages and get rid of mixin pages, but we need to plan and get agreement first.
Florian, do you fancy taking that planning work on? ;-)

OK, so basically leave on... pages as is, but have event pages documented on both Element and Document now?
Generally, I think this whole situation boils down to us deeply understanding WebIDL, then derive and agree on structures for MDN docs that are useful for web developers.
That is, I can imagine to write a tool that accepts WebIDL and then spits out MDN URLs and BCD paths to create after we have looked into all sorts of types that WebIDL can have and formulated structure for them (observable interfaces, mixins, dictionaries, etc). Only then our API docs aren't of random structure anymore I suppose.
One rule we agreed on (I think) was to not have subpages for dictionaries, for example, but that decision alone wasn't straight forward to come to ;-)
So, yes, I can maybe take on planning some of this, but this is quite gigantic due to the WebIDL complexity, decision making, (user) research, and amount of API pages (5000+?).

the only thing we can do now is to leave the on... pages where they are, put the event pages below the interfaces they are fired on, and link both from the interface landing page as agreed.

This is what I've done in https://github.com/mdn/sprints/issues/949 and I agree, it's the best plan at the moment.
In the bigger picture: it might be worth some research to see whether people see things in terms of these mixins rather than just in terms of the actual objects they work with (e.g. Document, Element). I would be very surprised if they did though.
Assuming they don't, then I think abolishing the mixins and duplicating the event properties across the objects that implement then is a better approach.
About duplicating information when/if we do this: that's just like the conversation we have had about duplicating event pages that have multiple targets. Yes, there is duplication, but also differences: at least the examples and BCD can be different in the different pages.

I think this all makes total sense.

About duplicating information when/if we do this: that's just like the conversation we have had about duplicating event pages that have multiple targets. Yes, there is duplication, but also differences: at least the examples and BCD can be different in the different pages.

I think this is a core finding (which we had before, but we now see ourselves thanks to the event work). I want to stress that I see this as a major argument against documenting mixins.

I have a question regarding the targets here. The MDN pages say the targets are Document and Element (the pages for pointer events said the same), but when you look at the specs or the Firefox webidl files, Element doesn't actually implement the GlobalEventHandlers mixin. See https://dxr.mozilla.org/mozilla-central/search?q=GlobalEventHandlers+ext%3Awebidl&redirect=false
So, my understanding would be that the targets here are:

Window
Document
HTMLElement
SVGElement
(XULElement but we don't document this one)

If you type in devtools "Element.prototype.on" there is actually only "onfullscreenchange" and "onfullscreenerror" and no other event handler properties whereas when typing "HTMLElement.prototype.ond" you actually see all the drag and drop events (and pointer events, etc).
So, what do you think about this? @chrisdavidmills @wbamberg

Good, if depressing, catch, @Elchi3 . I suppose the correct thing to do then is to have these events live off HTMLElement (and SVGElement). And that's also probably the least disruptive thing to do in terms of getting this project completed without opening too many worm-cans.
But I worry whether the correct thing to do is actually the most helpful thing to do. This feels like another version of the 'mixin debate'. Do most web developers care about the distinction between HTMLElement and Element, or know (or want to know) which methods and properties and events are on one versus the other?

Good, if depressing, catch, @Elchi3 . I suppose the correct thing to do then is to have these events live off HTMLElement (and SVGElement). And that's also probably the least disruptive thing to do in terms of getting this project completed without opening too many worm-cans.

That is my thinking as well.

But I worry whether the correct thing to do is actually the most helpful thing to do. This feels like another version of the 'mixin debate'. Do most web developers care about the distinction between HTMLElement and Element, or know (or want to know) which methods and properties and events are on one versus the other?

I don't know tbh. Seems like speculation what is helpful and what not. Part of me also wants to understand and then teach the differences of these interfaces and event installations on different targets. At the moment it isn't very clear to me how these things differ when you install a drag event on say window or document or HTMLElement.
Also, it feels like we need to be more conscious where we put docs and how we arrange them if our content aims to be machine-readable and highly structured and at the same time useful (for some definition of "useful"/"helpful").

The general rule should be to have multiple pages hanging off of all the different interfaces the event is fired on. So we can then have different BCD, and examples if the sensible examples would be different in different contexts. Sucks, but it is still less confusing than having them on weird mixins or made up constructs.
If you are not currently sure what the differences are between the different contexts they fire on, then for the moment I'd say just keep the pages generic for now, and then make a note to research these differences and follow up on them in a future sprint. For each one, it'd probably make sense to chat to a relevant engineer about what their feelings are, and get them to help with the explanations.

Do you think then that we should reopen https://github.com/mdn/sprints/issues/949 to move them under HTMLElement? (and redo the BCD?) I think we should although I'm reluctant to...

It sounds like we should bite the bullet and re-open.

Agreed.

Back to Drag & Drop. I've moved the pages and added them to the Document listing:
https://developer.mozilla.org/en-US/docs/Web/API/Document#Drag_drop_events
https://developer.mozilla.org/en-US/docs/Web/API/Document/drag_event
https://developer.mozilla.org/en-US/docs/Web/API/Document/dragstart_event
https://developer.mozilla.org/en-US/docs/Web/API/Document/dragend_event
https://developer.mozilla.org/en-US/docs/Web/API/Document/dragover_event
https://developer.mozilla.org/en-US/docs/Web/API/Document/dragenter_event
https://developer.mozilla.org/en-US/docs/Web/API/Document/dragleave_event
https://developer.mozilla.org/en-US/docs/Web/API/Document/dragexit_event
https://developer.mozilla.org/en-US/docs/Web/API/Document/drop_event
Can you review this before I copy this and make pages for other targets (Window, HTMLElement, SVGElement).
The example is longer and the same throughout as it shows all drag and drop events in context. Do you think this is OK or should it be split up and only show the relevant code for the given event?

The example is longer and the same throughout as it shows all drag and drop events in context. Do you think this is OK or should it be split up and only show the relevant code for the given event?

I think it's OK to have a longer example, but I think if possible longer examples should be "live" (this is really the point of having a longer example, and long examples that you can't run are so much more likely to not work properly). Not to mention that examples that are one big blob of HTML with embedded JS and CSS are harder to read. Note that the copy in at least one of these page (https://developer.mozilla.org/en-US/docs/Web/API/Document/dragstart_event#Examples) has been converted to a live example, so perhaps that could be copied? It's a bit sad to duplicate the example across like 20 pages, but hey ho.

https://developer.mozilla.org/en-US/docs/Web/API/Document#Drag_drop_events

This should use code style for the <dt> elements, and alphabetize them.

https://developer.mozilla.org/en-US/docs/Web/API/Document/drag_event

These comments apply to more than one page:

This includes "Default action" in the blue box, which most of the others don't. Is this optional?
I think H2 "Example" should be "Examples" even when there's just one of them.
the Demo link in See also is redundant, doubly so if the example is converted to live.

https://developer.mozilla.org/en-US/docs/Web/API/Document/dragstart_event

The blue box should use th for the cells in column 1

https://developer.mozilla.org/en-US/docs/Web/API/Document/dragend_event

The blue box has a different order here

https://developer.mozilla.org/en-US/docs/Web/API/Document/dragenter_event

The blue box includes "Target objects" as well here. Or did you keep this in intentionally, because it's weird? If so I think it would be better to note that outside the table.

I think it's OK to have a longer example, but I think if possible longer examples should be "live" (this is really the point of having a longer example, and long examples that you can't run are so much more likely to not work properly). Not to mention that examples that are one big blob of HTML with embedded JS and CSS are harder to read. Note that the copy in at least one of these page (https://developer.mozilla.org/en-US/docs/Web/API/Document/dragstart_event#Examples) has been converted to a live example, so perhaps that could be copied? It's a bit sad to duplicate the example across like 20 pages, but hey ho.

How about this: I've added the example to the drag event with code blocks and live demo and jsfiddle link: https://developer.mozilla.org/en-US/docs/Web/API/Document/drag_event
On other event pages I have referred this to the drag event page but also still to jsfiddle and showed the demo. https://developer.mozilla.org/en-US/docs/Web/API/Document/dragstart_event

https://developer.mozilla.org/en-US/docs/Web/API/Document#Drag_drop_events
This should use code style for the <dt> elements, and alphabetize them.

Done.

This includes "Default action" in the blue box, which most of the others don't. Is this optional?

I'm not sure. I guess the page author copied or modeled this blue box after the table in the spec https://html.spec.whatwg.org/multipage/dnd.html#dndevents
Do you think it is okay to leave it in?

I think H2 "Example" should be "Examples" even when there's just one of them.

I agree and I've changed it to be "Examples" throughout.

the Demo link in See also is redundant, doubly so if the example is converted to live.

I agree. Removed.

The blue box should use th for the cells in column 1

Oversight, sorry. Fixed now.

The blue box has a different order here

I've now made them all alphabetically.

The blue box includes "Target objects" as well here. Or did you keep this in intentionally, because it's an unusual value? If so I think it would be better to note that outside the table.

Yeah, I guess I left that there as it is special. I've now moved it after the summary sentence. Is that a better place?

The BCD is in https://github.com/mdn/browser-compat-data/pull/3542

Thanks @Elchi3 , these changes look good.