Allow use of integer variables in tasks.json

I'm trying to call revealLine from a task input as that allows variable substitution (unlike keybindings):
    "inputs": [
        {
            "id": "RevealLine",
            "type": "command",
            "command": "revealLine",
            "args":{
                "lineNumber": "${lineNumber}",
                "at": "center"
            },
        }
    ]

Obviously this fails because the command revealLine expects an integer as the first command. It works fine if I substitute "${lineNumber}" with any old integer.
Of course, this is a valid JSON file with no pre-process and I anticipate you want to keep this concept. But it occurs to me that the type matching between strings an integers could be loosened a bit, allowing this conversion. I may be useful elsewhere.
Thanks again for this great tool.

This would require that the variable substitution know something about where the variable substitution is happening. Instead, you could very easily write your own command that takes a string lineNumber and converts it to a number before calling the revealLine command.

Sorry, I'm unsure what this means: doesn't the variable substitution already happen in tasks.json? So as far as I'm aware the above piece of code ends up being presented to the command as:
"args":{
                "lineNumber": "123",
                "at": "center"
            },

The problem is that the command itself wants a number type, not a string type:
https://github.com/microsoft/vscode/blob/7c17748db7b43d11a5cd20563888da0519d1360d/src/vs/editor/browser/widget/codeEditorWidget.ts#L579-L590
I'm totally aware there are command extensions out there that can service my needs but I don't trust extensions as a rule and prefer to keep those installed to a minimum.
In this case a very simple addition would be to convert from string to integer but that may seem too specific. I've not dug any deeper into the code than this but I hand-wave assumed there'd be some higher level point (e.g. https://github.com/microsoft/vscode/blob/a109b2561de478e23c29c139d2cc4ecc0776eb65/src/vs/editor/browser/controller/coreCommands.ts#L1482) that allowed you to be relaxed about the type of inputs you expect.

@rebornix would you consider changing the reveal line command to handle a string for the lineNumber?

@alexr00 we can support both number | string.

Verifier, please test that you are not seeing warnings in keybindings editor when adding below
{
    "key": "cmd+i",
    "command": "revealLine",
    "args": {
      "lineNumber": "70",
      "at": "center"
    }

and also it works as expected

The title of this feature request no longer matches what was actually implemented to close the issue.
The feature "Allow use of integer variables in tasks.json" is still not supported.
But the command "revealLine" now supports a string and a number for the line number argument.
I've verified that "revealLine" now accepts a string argument.


chore(deps): lock file maintenance

This PR contains the following updates:

Update
Change

lockFileMaintenance
All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[x] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Frontend available
Backend available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@material-ui/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR!


feat: add btc payer wrapper class

this is not up to date and not yet using your new library, can you update it?


How do i check NSG connected to subnet or NIC using azure CLI ?

az network nic list-effective-nsg [--ids]
[--name]
[--resource-group]
[--subscription]
Get Outlook for Androidhttps://aka.ms/ghei36

From: azyp<EMAIL_ADDRESS>Sent: Sunday, December 16, 2018 7:17:55 PM
To: QT-DevOps/DevOpsIssues
Cc: Subscribed
Subject: [QT-DevOps/DevOpsIssues] How do i check NSG connected to subnet or NIC using azure CLI ? (#313)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/QT-DevOps/DevOpsIssues/issues/313, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACU0rWYTcJK4MtfMvrpPJRtqXgfg42y3ks5u5k8LgaJpZM4ZVOvW.


  Can't get mushrooms now :(

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

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions:

Mod: x.x.x
Game: 1.4.2

Additional context
Add any other context about the problem here.

Checking this out now, thanks for the report

Fixed in c72fabab1a03271f480adc6a78c4e9127813c133


Feature request for docker --filter : ability to search by PORT number, exposed or published and all published

Just wanted to voice an idea to implement a couple of new --filter's in docker cli tool
Often, I find myself looking for containers that run or publish certain ports, or sometime find all containers that publish ports and filter out all containers that don't publish and don't expose ports.
Does anyone think that they could also benefit from something like that?
It should allow matches by complete number and/or support wildcard or regex in the search mask.
Proposed syntax:
docker ps --filter publishes=27017
docker ps --filter exposes=27017
docker ps --filter publishes=270*
docker ps --filter exposes=270*
docker ps --filter publishes=*
docker ps --filter exposes=*

One issue with the wildcard is that we also need to take into consideration the protocols, i.e., tcp or udp.
I created a PR #27557 with filter expose|publish=<port>[/<protocol>]|<from>-<to>[/<protocol>]. This is an attempt with the hope to have more discussions.  Open to any suggestions or feedbacks.


Creating more interactive nav bar

Hey @bruno-keiko The design of the navbar can be made more better of the UI. This will make the first impression after entering the site better.

Could you please wait until our design is ready?


HBASE-25191 -JVMMetrics tag.processName regression between hbase-1.3 …

…and hbase-2.x+ versions

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 36s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  8s
master passed

+1 :green_heart:
compile
1m 17s
master passed

+1 :green_heart:
shadedjars
7m  8s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 54s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 50s
the patch passed

+1 :green_heart:
compile
1m 17s
the patch passed

+1 :green_heart:
javac
1m 17s
the patch passed

+1 :green_heart:
shadedjars
7m  9s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 36s
hbase-hadoop-compat in the patch passed.

-1 :x:
unit
9m 11s
hbase-server in the patch failed.

40m  3s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2573

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9ac6dadff33d 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2cd5f914af

Default Java
1.8.0_232

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/testReport/

Max. process+thread count
719 (vs. ulimit of 30000)

modules
C: hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 44s
master passed

+1 :green_heart:
compile
1m 30s
master passed

+1 :green_heart:
shadedjars
7m 20s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  1s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 39s
the patch passed

+1 :green_heart:
compile
1m 35s
the patch passed

+1 :green_heart:
javac
1m 35s
the patch passed

+1 :green_heart:
shadedjars
7m 58s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 22s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 50s
hbase-hadoop-compat in the patch passed.

-1 :x:
unit
12m  6s
hbase-server in the patch failed.

46m 15s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2573

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux af1a2f6be5ed 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1b58af1841

Default Java
2020-01-14

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/testReport/

Max. process+thread count
598 (vs. ulimit of 30000)

modules
C: hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 50s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 22s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 52s
master passed

+1 :green_heart:
checkstyle
1m 43s
master passed

+1 :green_heart:
spotbugs
3m 17s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 32s
the patch passed

-0 :warning:
checkstyle
0m 13s
hbase-hadoop-compat: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

-0 :warning:
checkstyle
1m 22s
hbase-server: The patch generated 2 new + 141 unchanged - 0 fixed = 143 total (was 141)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
21m 38s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

-1 :x:
spotbugs
2m 27s
hbase-server generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

+1 :green_heart:
asflicense
0m 23s
The patch does not generate ASF License warnings.

52m 38s

Reason
Tests

FindBugs
module:hbase-server

Write to static field org.apache.hadoop.hbase.master.HMaster.metricsIO from instance method new org.apache.hadoop.hbase.master.HMaster(Configuration)  At HMaster.java:from instance method new org.apache.hadoop.hbase.master.HMaster(Configuration)  At HMaster.java:[line 555]

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2573

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 0102e94af1dd 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2cd5f914af

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-hadoop-compat.txt

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

spotbugs
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/artifact/yetus-general-check/output/new-spotbugs-hbase-server.html

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2573/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


[subset] Wish: Flatten OpenType features

Hi everyone,
pyftsubset is one of the most useful tools I’ve come around in my current stream of work.
Yet a key feature may be missing: Flattening OpenType features, as in: applying all single substitutions from a certain feature before removing it.
So that one could choose a certain hard-wired figure set, for instance, or Small Caps or some Stylistic Set baked as the default into the fonts.
It feels like such a natural part of pyftsubset, especially for reducing file sizes for web fonts.
Is there such a thing already that I’ve missed or shall I attempt to make it and push?

By the way, the FontFont Subsetter has that feature, so one could ask Eigi if he wants to contribute the code, assuming that it was written around fontTools.

Check out this script by @twardoch
https://github.com/twardoch/fonttools-utils/tree/master/pyftfeatfreeze
Maybe it's what you are looking for?

Thanks, I checked it out.
As Adam writes, it seems to only remap the ´cmap´ table, leaving the rest of the font as it is and my findings seems to confirm it. The entire glyph body and features are still in the font afterwards, whereas I would expect the lowercase glyphs to disappear when I freeze the smcp feature. So his approach doesn’t actually optimize anything, just changes the functionality of the font.
That's not what I had in mind.

I see. What about running pyftfeatfreeze and subset afterwards?

This looks very promising. I used pyftsubset using  --unicodes="*" --layout-features='*' --layout-features-='smcp' on the frozen font. Please correct me as I’m just learning how to use the tools properly. I was afraid that it would then remove the .sc glyph as per the features, but I guess that the cmap-remapping really did the trick. The glyphs in the final font are still called .sc but have the respective standard Unicodes. Also the kerning seems to be correct for the .sc. The font lost 42% file size.
Will do some more testing. If I find anything, I’ll let you know. Thank you.

I've been using pyftfeatfreeze and pyftsubset myself. pyftfeatfreeze even has an option to output the new glyphnames, which can then be fed into pyftsubset to create a small font that only includes the remapped glyphs (which can then be included in a CSS font-family call as the first font, followed by the regular font). This is now a bit obsolete for new browsers but may be useful for those that don't support font-feature-settings.
Though for IE, I'd just run pyftfeatfreeze and produce only the EOT (without WOFF/WOFF2) and specify that webfont as the first one, followed by WOFF/WOFF2 with font-feature-settings applied from the regular font.
Generally, pyftfeatfreeze and pyftsubset are meant to work together. My tool does its own analysis of lookups because I wrote it before pyftsubset existed. Today, it'd make sense to use the internal of subset.py i.e. out would be very possible to slightly extend subset.py to do the freezing but I never got around to doing it.

Thanks for the explanation.
I’m closing this issue. You guys will remember to include a freezer into pyftsubset when the time has come.


grid triggers change detection in angular2

Hi got the following markup,

                {{widget.name}}

                <dynamic-component [model]="widget.component"></dynamic-component>

ngOnInit() : void {
        this.gridConfig = {
            'draggable': this.dashboardEditMode,
            'resizable': this.dashboardEditMode,
            'cascade': 'up',
        };

        this.widgets = [];
        for (let component of this.model.components) {
            this.widgets.push({
                name: component.config.displayName,
                config: {
                    sizex: component.config.sizeX,
                    sizey: component.config.sizeY,
                    col: component.config.col,
                    row: component.config.row
                },
                component: component,
                components: component.components
            });
        }
    }

Whenever i move the mouse on the screen i see all interpolutions of {{something()}} going bananas. (I've added console.log() events in there to see it happening). When i disable the grid it doesn't behave like that. Tried with the latest 2.0.1 with angular 2.4.4

BTW i tried to do a plunker, but i failed :(
https://plnkr.co/edit/KxPusbL9IJLCDIpxZhxf?p=catalogue

I've created a root plunker here: https://plnkr.co/edit/3m8ost Give that a try and see if you can replicate the issue :)

Hi BTMorton,
funny you should update it yesterday. I've been away for this in a month and just got back to it. I've done a fork here:
https://plnkr.co/edit/yPGKbkx9lTKwmvJcG21e?p=preview
I have added a single function in app.ts that will do a console.log and calling that function in my template. It goes crazy whenever i move the mouse. Any way to avoid that?

No update on this BTMorton?

I don't know. Best guess is that it's causing the angular change detection routine to run because it's bound the mouse move events. I don't know what would cause it otherwise. I can try to investigate further, but my knowledge of the Angular 2+ change detection algorithms is limited at best.

I guess it should only bind the move events when there's actually something that should move. Usually the configuration properties are set to false which means that i cant move or resize anything. So it should subscribe/unsubscribe on request.


Fix for issue 1916: Consumes / Produces media-types on the document level aren't copied and merged anymore with the operation level consumes / produces media-types.

This is a possible fix for issue 1916. It removes the merging of the document level and operation level consumes and produces media types on the in the OperationContext. This results in a "more" valid swagger specification because now the document level media types are only defined on the document level and only when these media-types are overwritten on the operation level, they will be set on the operation level. This behaviour is according to the Swagger v2 specification and it also works just fine within the Swagger UI.
However we do want to provide some default values when no media-types are defined on the document and operation level. Thus I changed the MediaTypeReader to reflect this.
I also fixed the contract tests, because many of these didn't produce the correct specification anymore. TBH: I didn't check every specification by hand because many many failed due to this change. For most of them I just made sure that the expected specification matched the produces specification.

Could you perhaps add some tests for this change?

No problem, I can add some additional tests.

@dilipkrish I updated the MediaTypeReaderSpec with additional tests and added two contract tests that test the behaviour for this change. I hope this suffices.

:metal: Will pull it in over the weekend. Thanks for being diligent! 🙇


Add a battery type node

Please could a device type of battery be added to allow me to pass by house battery charge % from NR to google home

I have a sample battery device, I'll try and find some time to add the relevant parts to Web interface.


Ceiling Fan: No Response and Log Errors

I'm seeing a Ceiling Fan issue with the status of "No Response" on the tile in HomeKit. How do I fix this?
I'm seeing the following error in the homebridge logs:
[8/28/2024, 1:59:38 PM] [@xenuiswatching/homebridge-hubspace] This plugin threw an error from the characteristic 'Active': Unhandled error thrown inside read handler for characteristic: Failed to get function definition for 'fan-power'. Each function requires to set a definition.. See https://homebridge.io/w/JtMGR for more info.
[8/28/2024, 1:59:38 PM] [@xenuiswatching/homebridge-hubspace] Error: Failed to get function definition for 'fan-power'. Each function requires to set a definition.
    at getDeviceFunctionDef (/usr/local/lib/node_modules/@xenuiswatching/homebridge-hubspace/src/models/device-functions.ts:110:15)
    at FanAccessory.getActive (/usr/local/lib/node_modules/@xenuiswatching/homebridge-hubspace/src/accessories/fan-accessory.ts:50:42)
[8/28/2024, 1:59:38 PM] [@xenuiswatching/homebridge-hubspace] This plugin threw an error from the characteristic 'Color Temperature': Unhandled error thrown inside read handler for characteristic: Failed to get function definition for 'color-mode'. Each function requires to set a definition.. See https://homebridge.io/w/JtMGR for more info.
[8/28/2024, 1:59:38 PM] [@xenuiswatching/homebridge-hubspace] Error: Failed to get function definition for 'color-mode'. Each function requires to set a definition.
    at getDeviceFunctionDef (/usr/local/lib/node_modules/@xenuiswatching/homebridge-hubspace/src/models/device-functions.ts:110:15)
    at LightAccessory.getTemperature (/usr/local/lib/node_modules/@xenuiswatching/homebridge-hubspace/src/accessories/light-accessory.ts:138:42)
    at ColorTemperature.getHandler (/usr/local/lib/node_modules/@xenuiswatching/homebridge-hubspace/src/accessories/light-accessory.ts:62:31)

Hubspace Plugin Version: 2.1.2
Homebridge Version: 1.8.4
Homebridge UI Config X Version: 4.57.1
Node JS Version: 20.11.1

I'm getting the same error.
Also I'm not sure if it matters, but my fan model only has 3 speeds vs 6 like the one mentioned as a supported device.
Light temperature options: 2700K,3000K,3500K,4000K,5000K,6500K
https://www.homedepot.com/p/Hampton-Bay-Nevali-52-in-White-Changing-LED-Indoor-Smart-Hubspace-Ceiling-Fan-with-Light-and-Remote-Control-Included-92394/322700723

@XenuIsWatching Are you able to help with this plugin still?


[Prototype] expose outsideBorder parameter in Buttons.

See XAML Border API

See layer-compare branch.

In the previous layer implementation. If we set outsideBorder to false, Layer will use content's size. If set to true, the Layer will expand by the size of paddings. Generally, the first one should be the correct behavior. I had seen that problem previously, but I haven't solved it instantly.
A:
This parameter only affects on background in Layer, we don't add padding to the content. So we will get the same effect as Box. That is the most convenient implementation.
B:
If the content has maxConstraints, we propagate the constraints - padding, so the 32.dp in Box(Modifier.size(32.dp)) will contain padding. If the content does not have maxConstraints, we just measure and put it.
I haven't tried Plan B yet. Maybe there are some undetectable problems.
The correct implementation of SplitButton should use a different border on four sides, which is not supported by compose.

Maybe we can provide a basic api Modifier.fluentBorder and FluentBorderStroke，that can provide a BackgroundSizing configuration .

Maybe we can provide a basic api Modifier.fluentBorder and FluentBorderStroke，that can provide a BackgroundSizing configuration .

I think there's no need to do that. If we add more tricky codes, it could potentially lead to more issues when the compose API changes.

Maybe we can provide a basic api Modifier.fluentBorder and FluentBorderStroke，that can provide a BackgroundSizing configuration .

I think there's no need to do that. If we add more tricky codes, it could potentially lead to more issues when the compose API changes.
I found a better way to implement background padding.

@Composable
private fun Modifier.newLayer(shape: Shape = FluentRoundedCornerShape(4.dp), backgroundSizing: BackgroundSizing = BackgroundSizing.OuterBorderEdge): Modifier {
    val paddingShape = remember {
        object : Shape {
            override fun createOutline(size: Size, layoutDirection: LayoutDirection, density: Density): Outline {
                return when {
                    shape is FluentRoundedCornerShape && backgroundSizing == BackgroundSizing.OuterBorderEdge -> {
                        with(density) {
                            val padding = 1.dp.toPx()
                            val innerSize = Size(size.width - 2*padding, size.height - 2* padding)
                            when(val oldOutline = shape.createOutline(innerSize, layoutDirection, density)) {
                                is Outline.Rectangle -> {
                                    Outline.Rectangle(oldOutline.rect.translate(Offset(padding, padding)))
                                }
                                is Outline.Rounded -> {
                                    Outline.Rounded(oldOutline.roundRect.translate(Offset(padding, padding)))
                                }
                                is Outline.Generic -> {
                                    Outline.Generic(oldOutline.path.apply {
                                        translate(Offset(padding, padding))
                                    })
                                }
                            }
                        }
                    }
                    else -> shape.createOutline(size, layoutDirection, density)
                }
            }
        }
    }
    return then(Modifier.border(1.dp, FluentTheme.colors.stroke.control.default, shape = shape)
        .background(FluentTheme.colors.fillAccent.default, shape = paddingShape)
    )
}

        NewLayer {
            Box(Modifier.size(32.dp))
        }

        NewLayer(backgroundSizing = BackgroundSizing.InnerBorderEdge) {
            Box(Modifier.size(32.dp))
        }

Screenshot

See layer-compare branch.

In the previous layer implementation. If we set outsideBorder to false, Layer will use content's size. If set to true, the Layer will expand by the size of paddings. Generally, the first one should be the correct behavior. I had seen that problem previously, but I haven't solved it instantly.
A: This parameter only affects on background in Layer, we don't add padding to the content. So we will get the same effect as Box. That is the most convenient implementation.
B: If the content has maxConstraints, we propagate the constraints - padding, so the 32.dp in Box(Modifier.size(32.dp)) will contain padding. If the content does not have maxConstraints, we just measure and put it.
I haven't tried Plan B yet. Maybe there are some undetectable problems.
The correct implementation of SplitButton should use a different border on four sides, which is not supported by compose.

new layer implementation, see layer-compare-2 branch

Looks well! We can use this method.

Looks well! We can use this method.

So we can remove the FluentCornerShape also?

Looks well! We can use this method.

So we can remove the FluentCornerShape also?

Yes

Looks well! We can use this method.

So we can remove the FluentCornerShape also?

See Commit [fluent] Deprecate FluentRoundedCorner and FluentCornerSize
#37


[Question] How to Pre-populate Items with Aliases Correctly in Custom Dictionary

Hi Tadashi,
I am populating my custom dictionary file from the outside complete with aliases. In order to know how to do that, I first tried creating items through Obsidian/VC and seeing in my dictionary file what pattern is used to store the main entry and its aliases.
What I found is that the first alias follows the main entry by two tabs and the others are separated by one tab.
My question:
Am I counting the tabs/spaces correctly (it is difficult to see properly)?
Is this how it is intended and taken to be a rule and can I take this for granted it will be future-proof in later releases?
Are there other ways to do it or would you consider a more easily followed rule? E.g.
Item\nAlias1\nAlias2\nAlias3\nAlias99
Thanks in advance
Cheers,
Z.

Hi, @zanodor :)

What I found is that the first alias follows the main entry by two tabs and the others are separated by one tab.

Please see the "Custom dictionary formats". The second column is not an alias but a description.
https://tadashi-aikawa.github.io/docs-obsidian-various-complements-plugin/5. Terms/📚 Custom dictionary formats/

Are there other ways to do it or would you consider a more easily followed rule?

You could set "Column delimiter".
https://tadashi-aikawa.github.io/docs-obsidian-various-complements-plugin/4. Options/4.6. Custom dictionary complement/⚙ Column delimiter/

I think I have waited enough to let the index refresh itself...?

Yes. Please see "When does it update tokens?".

I showcased your plugin (again) on the Obs forum:

Thanks! 😍

Works fine on my sandbox environment 🤔


Update uninstall-az-ps.md

Updating the doc to reflect the feedback shared by the customer.

Docs Build status updates of commit 7438337:
:clock10: Full build: the average full build time is 22 min(s) 27 sec(s), this is based on the last 246 build(s) for this repository.

Docs Build status updates of commit 7438337:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-3.0.0/uninstall-az-ps.md
:white_check_mark:Succeeded
View (azps-3.0.0)

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


Allow changing Settings in Calc by assigning values to "info.settings.blah"

We could then actually remove the relevant directives because this is simpler and more direct....

Changed "info.settings" to "settings".


Fix brush transforms

This fixes an incorrect application of the inverse transform for radial gradients in fine.
Also fixes an edge case in SceneBuilder where supplying a brush transform that is identical to the path transform generates a corrupt encoding.
Discovery of both done by @DJMcNab on this zulip thread.
Should fix #281

Thank you for the back and forth!


Adopt flutter_plugin_tools podspecs linter

lint_darwin_plugins.sh now lives in flutter_plugin_tools and has more linting features.
Already done in Flutter plugins with https://github.com/flutter/plugins/pull/2346.

lint_darwin_plugins.sh no longer exists and the podspec linting has moved from .cirrus.yml to  https://github.com/FirebaseExtended/flutterfire/blob/584d0d340bae7ed3f32c09fe68aab7ddf32a4229/melos.yaml#L75

Hi @Salakar
Couldn't find a relevant label for this. Should this be kept as-is ?
Thanks.

I'm closing this for the following reasons:

We do not publish the podspecs so the warning are not relevant (missing author or license are included in the dart package)
the underlying command pod lib lint does not support importing variables from ruby files which we use for defining a global firebase_sdk_version

Anybody feel free to reopen if you feel it's important


Fix onShouldStartLoadWithResquest.

Resolve
https://github.com/react-native-community/react-native-webview/issues/185
Summary
onShouldStartLoadWithRequest does not work on Android, when the first url is loaded.
Test Plan
Just test, if onShouldStartLoadWithRequest is called after first url load.
Checklist

[x] I have tested this on a device and a simulator

OnShouldStartLoadWithRequest isn't just an event you listen to, you need to be able to stop the current request from starting. This is why it was trickier to implement on android.

Close, because it does not solve the problem.

Hey folks,
I am also stuck in this is an issue from webview and finally am fix this issue by getting a fork from react-native-community/react-native-webview by doing some android native code.
You guys check out my git package.
https://github.com/kulbhushan-ucreate/react-native-web-view.


Distance - Error displayed when creating distance expense in workspace that not opened yet

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:  9.0.10-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/45000
Action Performed:

Go to https://staging.new.expensify.com/
and log in with an existing account than has a workspace (make sure to open any chat other that workspace chat when logging out)
Click on FAB > Distance expense
Enter the start and finish waypoints
On the next screen select the workspace you have not opened yet after logging in
Finish creating a distance expense

Expected Result:
The distance expense is created
Actual Result:
The error "The selected rate has been deletedUnexpected error submitting this expense. Please try again later." is displayed
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/93385ba8-bdee-4ce0-9aa3-49dfccd1f2c9
View all open jobs on GitHub

@puneetlath  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-collect - Release 1

Since I was tagged in, here are my thoughts. The p2p distance beta is a bit tricky because it's designed to hide some features, like selecting a workspace rate, that are also related to regular distance requests. Do we need to access the rate for the distance request if you are not on the p2p distance beta? I would guess probably yes since it's used to calculate various optimistic data and display elements. When not on the beta we should only use the default rate on the workspace. If we're on the beta, then we should try to get the last selected distance rate or the default rate for workspacse, or the defaultP2PRate for P2P requests.

@allgandalf have you had a chance to review?

@allgandalf can you complete the checklist?

Regression test: https://github.com/Expensify/Expensify/issues/425941
All paid. Thanks everyone!


nvim-lsp: add sumneko_lua language server

Doesn't this server require some special configuration to work properly? At least that's what I encountered the last time I looked into it. Will check it out later today.

Indeed...
Here is how I currently have it configured:
require 'lspconfig'.sumneko_lua.setup {
    capabilities = capabilities,
    settings = {
        Lua = {
            runtime = {
                -- Tell the language server which version of Lua you're using
                -- (most likely LuaJIT in the case of Neovim)
                version = 'LuaJIT',
            },
            diagnostics = {
                -- Get the language server to recognize the `vim` global
                globals = {'vim'}
            },
            workspace = {
                -- Make the server aware of Neovim runtime files
                library = vim.api.nvim_get_runtime_file("", true),

                -- https://github.com/sumneko/lua-language-server/discussions/1688#discussioncomment-4185003
                checkThirdParty = false,
            },
            -- Do not send telemetry data containing a randomized but unique identifier
            telemetry = {
                enable = false,
            }
        }
    }
}

Here is the documentation from the nvim-lspconfig plugin:
https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.txt#sumneko_lua


Add Option to Disable System Keychain on macOS

Is your feature request related to a problem? Please describe.
See also https://github.com/apple/cups/issues/6037, this continues to be an issue on recent versions of macOS. It would help to be able to prevent CUPS-based targets from choosing inappropriate TLS credentials, as they will be unable to start TLS connections. Many Macs acting as print servers also host other services, and therefore are likely to have candidate identities in the System keychain, which aren't intended for CUPS.
The current mechanism in tls-darwin.c doesn't respect identity preferences (which are one solution), enumerate multiple matches as candidates, nor attempt to preflight the credential selected. Extracting the relevant code and running it repeatedly shows a different credential may be selected each time if many are available, which is also undesirable.
Describe the solution you'd like
A global option (like -o system-keychain=no) to cause http_cdsa_open_system_keychain to always return NULL/nil.
Describe alternatives you've considered
Custom builds, removing certificates, granting access conditionally, interposing.
Additional context
When running CUPS-based targets as Launch Daemons on macOS, the System keychain is always available, whereas user substitution in a graphical session doesn't produce the same result.

Not using the keychain is, unfortunately, not an option since macOS depends on it when generating self-signed certificates (the iOS target can generate and use an in-memory certificate since it lacks the same keychain APIs). I'm not sure what state your keychain is in that a query will result in multiple certificates matching the query, but this is the same code shipped by Apple and I'm not keen on changing it here when the code will never get used on macOS... :/
If you can provide additional context we might be able to come up with a short-term solution. Longer term CDSA/Security.framework support has been removed from CUPS 3.0 (replaced by a requirement for OpenSSL/LibreSSL or GNU TLS) since Securty.framework's TLS API was never updated to support TLS/1.3 (!) and the suggested Apple replacement (Network.framework) requires adoption of GCD and doesn't support TLS upgrade, both of which are a non-starter...

Closing as not to be fixed - CUPS 2.5 and later will no longer support Security.framework or the system keychain (opting to use OpenSSL/GNU TLS instead with standard PEM-encoded certs/keys).


gRPC on Endpoints Quickstart sample.

Code is mostly from: https://github.com/grpc/grpc/tree/master/examples/cpp/helloworld Client is modified to take an api_key and insert it into the request. Endpoints configs and README added. Will eventually replace https://cloud.google.com/endpoints/docs/quickstart-grpc-container-engine and https://cloud.google.com/endpoints/docs/quickstart-grpc-compute-engine-docker bookstore sample with a tabbed helloworld for each language.

@SurferJeffAtGoogle Do you think this is a reasonable requirement?

You either need Docker installed or the ability to compile Linux
+64-bit static C++ binaries.

It allows us to make a "from scratch" Docker image


Bug Fixes for autotuner and flops profiler

This PR makes the following change:

fix the autotuner timing bug when backward is not called
change autotuner default to not tune zero stage if "zero_optimization" is not defined
fix flops profiler bug when computing flops for torch.nn.functional.interpolate

Can one of the admins verify this patch?


form_with resulting in undefined local variable in link_to_add_association

I am attempting to implement cocoon inside of a form_with form, and running into:
"undefined local variable or method `form' for <Class:0x000000000430b8e0>:0x00000000040ea250>

Showing app/views/job_step_options/_job_step_option_fields.erb where line #3 raised:

My form definition starts with:
<%= form_with(model: job_definition_step, local: true) do |form| %>
And I am attempting to setup the link_to as such:
<%= link_to_add_association 'add option', form, :job_step_options, partial:'job_step_options/job_step_option_fields' %>
And my partial is very basic right now (which appears to be where the error is thrown, line 3 in this file which is calling form.label):

<%= form.label :option_type %>

  <%= link_to_remove_association "remove option", form %>

In my debug console poking at the form variable:
>> form.present?
=> true
>> form.class
=> ActionView::Helpers::FormBuilder
>> form.form
NoMethodError: undefined method `form' for #<ActionView::Helpers::FormBuilder:0x00007f2734e83ea8>

This is running with cocoon 1.2.14, ontop ruby 2.5.3 and rails <IP_ADDRESS>.
I'm not sure what all to attach for additional data, but glad to provide whatever is necessary/dumps of variables/etc as requested.

Tracked it down with other google searches that lead to other Cocoon errors; End answer: specify "form_name: 'form'" in the link_to_add;
Hopefully my including "form_with" in the issue name will help lead others here as well :)
https://github.com/nathanvda/cocoon/issues/504


[BEAM-4297] Streaming executable stage translation and operator for portable Flink runner.

Executable stage translation for streaming mode based on the generic Flink streaming operator. Stage execution and tests adopted from batch translation.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

R: @lukecwik @bsidhom

@bsidhom @lukecwik PTAL


Can we have a add template for "created" and "author"

Hi team,
On https://raw.githubusercontent.com/SSWConsulting/SSW.Rules.Content/main/template/rule.md
...can we have a default timestamp (until we automate it)  + a default author?
Example:
---
type: rule
archivedreason:
title: {title}
guid: {guid}
uri: {uri}
created: 2021-01-01T00:01:00.0000000Z
authors:
- title: Adam Cogan
  url: https://ssw.com.au/people/adam-cogan
related:

---

<!--endintro-->

...so it's easier to create new rules ;)
AB#60490
AB#60654

Hi team,
the template is also missing the field for "redirect"


Client responds to CertificateRequest incorrectly, potentially causing interoperability problems

Your environment.

Version: 2.0.9
Browser: N/A
Other Information - OS: Ubuntu 20

What did you do?
Test how the PionDTLS client behaves when asked to authenticate with a certificate of a type it does not own.
The RFC mandates in this case that the client responds with an empty certificate as per:

This message is only sent if the server requests a certificate. If no suitable certificate is available, the client MUST send a certificate message containing no certificates. That is, the certificate_list structure has a length of zero.

What did you expect?
An empty certificate from the client.
What happened?
The client responded with the certificate under its possession, despite it being of the wrong type. This is seen in the bellow capture taken on my machine. The capture is included in the reproduction files provided at the end.

Notice the CertificateRequest sent by the server. If we look at this records we see that the server asks for a Certificate of type RSA Sign (containing an RSA public key).

The client, whose certificate contains an EC public key, wrongly provides its certificate despite it being the wrong type (by not containing an RSA public key).

We found the problem to also affect MbedTLS clients and posted an issue. There we also explain how this can lead to interoperability problems between clients and servers who request but not require client certificates for handshake completion. The client providing a wrong certificate may cause the server to terminate the handshake, which would not happen if the client had provided an empty certificate.
Steps to Reproduce
I attached files necessary for reproduction on the server (see reproduction.tar.gz) using DTLS-Fuzzer and a PionDTLS client/server program we use for testing. Also included in the archive is the capture shown earlier. DTLS-Fuzzer requires  the JDK for Java 8. On Ubuntu, this can be installed  by running:
sudo apt-get install openjdk-8-jdk
Unpack the archive, cd to resulting folder and run bash reproduce.sh, while running an instance of Wireshark on the side. The reproduction script will:

setup PionDTLS and DTLS-Fuzzer;
launch DTLS-Fuzzer in server mode in order to  execute input sequence found in 'test_sequence' exposing this problem;
launch the PionDTLS client.

Let me know if you can confirm this behavior.
Thanks.
reproduce.tar.gz

Thanks so much for raising this with us and all the detail provided in the bug report!
As an aside, I hadn't seen DTLS fuzzer before, seems great. @Sean-Der @at-wat does either of you have an idea on how we could integrate that in CI? It feels like this could help us close the long-standing #4.

I would love to do that @daenney! I am a few weeks out from having free time, but sounds like a great weekend project :)
Sounds like getting TLS-Attacker setup today in the best first step? I hadn't heard of these tools before, but I am sure we will find some good bugs/additional work :)


Web directories don't open unless called from within the main site

https://testnet-wallet.kyber.network/transactions  does not work (404) when being called directly as a url, only when  being requested while in the https://testnet-wallet.kyber.network page.
Same for all /dirs under the main page

@tranvictor Please check configuration in server, the localhost work well

Sure i will check later


Could you recommend some papers related to positioning with esp32s3?

I want to learn to use esp32s3 for positioning, but I don't know the relevant principles very well. Can you recommend some literatures?

see: https://github.com/espressif/esp-idf/tree/master/examples/wifi/ftm

see: https://github.com/espressif/esp-idf/tree/master/examples/wifi/ftm

Thank you very much!!! But if I only know the distance without direction, how can I know the specific location?

Hello, @xiaokangkang6
Closing this issue, feel free to reopen with more updates. Thanks.


Allow custom GAV for application creation

Allow custom GAV for application creation
Fixes https://github.com/quarkus-qe/quarkus-test-framework/issues/486
Summary
(Summarize the problem solved by this PR, and how to verify it manually)
Please check the relevant options

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[ ] Refactoring
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update

Checklist:

[x] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

CI is green, can be merged @fedinskiy


Consultation for Source Code

Amazing and intriguing work! Congratulations on the publication of your paper ! Do you have any plans for opening source code ?

Thank you. The code will be released this year.


Replaces animated pending halo with static pending halo

This also modifies the legend so that "pending" and "started" are at
the bottom

Resolves concourse/concourse#987
Signed-off-by: Jesse Zhang<EMAIL_ADDRESS>Signed-off-by: Lindsay Auchinachie<EMAIL_ADDRESS>

This pull request significantly reduces the CPU load for visualizing a concourse pipeline with paused jobs. We've been having issues with our build monitors rendering concourse pipelines.

Sounds like a step towards addressing https://github.com/concourse/concourse/issues/991. Thank you so much!

+1 to anything which let's the fan in my laptop not spinning at full speed!

:shipit: pls

@d, can I ask for two things?

An example of the high CPU usage with the animation.
And a screenshot showing that it decreased.

Here is the hack day demo explaining the change:
https://drive.google.com/a/pivotal.io/file/d/0B9ljoEuCdXaxd0JkVUF0elA5WjQ/view?usp=sharing
@jtarchie
before the change:
Tab: 75%, GPU Process: 27%
after the change:
Tab: 18%, GPU Process: 10%
(Note that it is difficult for me to apply the change to our production pipeline, so the 'after' number is an estimate based on the change. When we made the Hack Day demo we saw a clear reduction in CPU utilization, but we didn't write down the exact numbers.)

This looks good. Thanks for the PR!

Awesome!


Add team sync issue template

Blarhhh...  Will redo from my computer and send PR from a fork.

see #116


Add andja3's file

create a branch, create a file, make a commit, open a pull request

Merge pull request


MLDB-1058: restored in-house implementation of "trim"

Restored ML::trim, that was disabled without a bug report.

Still brisé.

Le test qui échoue n'est pas influencé par l'une ou l'autre des implémentations. C'est un hasard.

The reason it was disabled without a bug report was that it broke the SQL parsing (which needs the behavior to include stripping all characters including newlines), and so was reverted.  Until we understand what's going on there, we shouldn't change it back.
Also, in the case that there is no space at the beginning or end of a string, we should simply return a copy of the input string.  In the shared string implementation of our compiler, this is a significant performance gain.

@wsourdeau I created the JIRA to avoid any additional back-and-forth.  See https://datacratic.atlassian.net/browse/MLDB-1221.

-1
I will create a test case to catch the regressions which caused this revert.

@nicolaskruchten thanks!

test case created and issue assigned

@guyd all characters reported as spaces by "isspace" are now handled.

@nicolaskruchten  all test cases pass now. The demos needs to be tested yet.

+1

The demos can be tested by building a docker container, booting it, and then executing the notebooks through Jupyter. If the tests pass it should be fine though, so please merge when ready.

(tests run 3 times, best result kept)
With fix: 80kqps
Without this fix: 75kqps
Gain: 5kqps

you already have a +1, please merge :)
On Wed, Jan 13, 2016 at 3:05 PM, Wolfgang Sourdeau<EMAIL_ADDRESS>
wrote:

(tests run 3 times, best result kept)
With fix: 80kqps
Without this fix: 75kqps
Gain: 5kqps
—
Reply to this email directly or view it on GitHub
https://github.com/mldbai/mldb/pull/41#issuecomment-171417111.

--
Nicolas Kruchten, Eng  |  Staff Software Engineer at Datacratic  |
http://datacratic.com/

Squash merged


[backport] Fixed choice function for 0 samples from 0 candidates

Backport of #4830

@toslunar This pull-request is marked as st:test-and-merge, but there were no activities for the last 3 days. Could you check?

Jenkins, test this please.

Jenkins CI test (for commit abb6c432b4742f01f729ec2a9d81af338d03e0bd, target branch v8) succeeded!


Cleaner Documentation Comments with ///

🔍 Search Terms
"comment", "jsdoc", "documentation", "doc"
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
The JSDoc format is both hard to write, and hard to read. More than that it is very messy and designed for a world where there is no compiler present. In the other worlds, languages like Go and Dart have such powerful, and at the same time more beautiful documentation comments that after working with them revisiting TypeScript has become a nightmare of mine. So my suggestion is to employ a better documentation comment, the ///.
📃 Motivating Example
While to some people TypeScript is an improvement to existing JavaScript projects, for some (which I believe is the most) it was the initial language and there was types from the ground up. And thus all the @param parts of the documentation tool are somewhat redundant and a bit ugly to be honest when compared to languages like go where simplicity is the rule. There you simply write a comment above a function and that becomes the function's documentation, that easy. Or in dart, there is a /// comment that has the same semantics, but it also provides a [ClassName] grammar which links to the name of another class. Markdown like and very basic.
Why shouldn't TypeScript have such elegant documentations? You could say:
/// Returns the sum of `a` and `b`
function add(a: number, b: number): number {
   return a + b;
}

Instead of
/**
 * Returns the sum of two numbers
 * @param {number} a the first number
 * @param {number} b the second number
 */
function add(a, b) {
   return a + b
}

There are somethings here worth noticing:

JSDoc has redundancies such as the @param. Usually, all we want to know from @param is the type. When the language has the type, then this becomes redundant. It is much more pleasant that we define something in the comment like:

/// Gets the `n`th root of the number `x`
function root(x: number, n: number): number {

/** feels old! Sorry but it matters, and I hope that you agree, TypeScript is a modern language, it has the most advanced type system in the world, it works on cutting-edge compiler architecture and design, and then it has the comment look of the dark ages. Why should it be such? Why can't we have the beautiful ones that are really easy to write and easy to edit (you can enable multiple coursers in vscode and make a normal comment a documentation comment, or the other way, but good luck doing that with JSDoc)

It's called JSDoc! It itself says I'm not the TypeScript doc! TypeScript deserves much more!

Because editing /// is easier, making tools for it is also easier. I have made an extension for justifying comments so that they are easy to read, uniform, and easy to write. It was so easy to make that for the /// / // comments, but for JSDoc, it was really hard. (I still haven't figured out what should I do) and if TypeScript joins this party, I can make tools like this for my workflow way more easier. And I believe others will too. It is important to enable the community in making tools for what they do. This is an example of a comment justified in Go. I hope that you find it beautiful, and then I can ask: Don't you like to write a comment this clean in TypeScript?

// Compare  compares  equality  of two values
// and returns  a  numeric  value  describing
// their  equality  or  greater  less or less
// than states. -1 if the left is lesser than
// right,  0 if they are equals and 1 for the
// other purpose.
func Compare(a, b computable.Value) computable.Value {

💻 Use Cases

Way easier for users to write
Way easier for developers to make extensions and tools for
Way nicer code to read and navigate
Denser in size and therefore more screen real estate + less documentation reading
Made for TypeScript and not redundant
Easier to maintain in the big projects

FWIW unless you have tooling that needs to see the @param tags, this gets you most of the way there.
/** Returns the sum of two numbers */
function add(a: number, b: number) {
   return a + b
}

Personally, I'd prefer a simpler syntax that allows params without tags if you like, but in general supports tags the same as the current design. Something like this.
/// Returns the sum of two numbers
/// a - the first number
/// b - the second number
/// @deprecated
function add(a: number, b: number) {
   return a + b
}

@snarbies yes I know that, but my reasoning was to show the nature of it. That it is because of this, and if we move to a more elegant system is better because exactly we don't need proms anymore.

You don't need them now, was my point.

I can remove that part from my point, but it still remains that /// are nicer to write and read.

It's called JSDoc! It itself says I'm not the TypeScript doc! TypeScript deserves much more!

It's called JSDoc because it predates Typescript.  This is important more more than just historical reasons; it means that many tools other than Typescript also support JSDoc.  Even if those other tools can't understand the type annotations, they can still parse the rest of the comments.  Switching to /// would greatly decrease compatibility and interoperability with other tooling.

@nmain I'm not saying this is a replacement, I'm saying that this can be another flavor. If anything, JavaScript can simply be defined in letting the developer have options. It has most features most languages have because it is the only common place where everyone comes and write code. So why should it force only one comment style for documentation? I think it would be great to have this alternative because I don't like /**, and then you can keep using /** so that your tooling won't break. It's the essence of web, you get to do it how you wish to do.

To be honest I'm a little surprised by the reactions. What I'm trying to say is to just "recognize" an alternative (and preferred) comment style that is "already" implemented and supported, to be a documentation comment as well as the /** for the JSDoc.
For all the years I have seen code, the /* ... */ was so rare to actually spot in code. Most people prefer the ergonomics of // codes. I only see the /* ... */ pattern where people want to disable a portion of a code, or for the copyright templates that they have copied from licenses written in many decades ago. And writing documentation comment is one of those things that at least I do like 20% of my time. I think for what I do 20%-30% during my day, a bit more ergonomics is a huge difference, given the fact that the implementation of it is probably of the easiest features to the language.
So I'm a little confused why so much rejection is happening here. What would break if this gets implemented? Nothing. Will it have any effect on anyone who don't like it? No! You'll still be able to use what you like. So why so much rejection? I mean I'm not harming anyone, not breaking anything, I'm just asking for a very inexpensive feature that will make my life a lot better.

/// is already used for triple-slash directives plus I don't see the point in adding an alternative when the existing already suffices. All it's going to do is cause confusion and deviate from the standard; not to mention the amount of tools that are now going to have to add support for this when everyone is already using /** */.

Please don't take people disagreeing with you personally. People are meant to examine issues here. If somebody has a hard time understanding the benefit, it's natural for them to say so and it's incumbent upon you to articulate why the investment is worthwhile. Plus, any feature, even a teensy tiny little feature, takes non-trivial time and effort to develop, almost always more than it seems at first blush. And any feature can have non-obvious consequences.
Most people use an IDE, and the formatting of /** */ documentation mostly just takes care of itself. I'm just not seeing a meaningful ergonomic issue and I genuinely can not see value in taking development time away from something else to implement a feature with a benefit that is somewhere between dubious and non-existent.
Adding a second syntax means everyone has to choose one. It creates the opportunities for style/convention wars, adds additional work for people creating documentation tooling, or creates a situation where somebody chooses one style and then finds out after writing several thousand lines of code that a tool in their chain doesn't like that comment style. There is quite a lot of software out there that only understands what we currently have. Fractures in the ecosystem, even small ones, come with a real cost.
All other things being equal, I'd have preferred /// style comments from the get. But in the present, it might seem trivial for you in your situation, but that doesn't mean that it won't create problems for others that are potentially greater than what it solves for you.
Not trying to rain on your parade. Just trying to convey to you that what you're asking for is not as trivial as it might seem.

Related: https://github.com/microsoft/tsdoc/issues/160

Closing since it is a duplicate of #160


Allow the WebServer component to be restarted

Dissoc-ing one of the defined fields of a record returns a regular Clojure map instead of a record instance. Due to this the WebServer cannot be started again once it is stopped. Setting the field to nil preserves the type.

For me, (stop) and (start) work with the current code. How can I reproduce this?

I can reproduce it like this:

Start dev system: boot dev
Start REPL in other shell: boot repl
Test that the server is running (in 3rd shell):

$curl http://localhost:3000/hello
Hello World!

Check WebServer component in REPL:

user=> (type (:web-server system))
edge.web_server.WebServer

Stop system:

user=> (stop)
:stopped

Confirm that system is stopped:

$ curl http://localhost:3000/hello
curl: (7) Failed to connect to localhost port 3000: Connection refused

Check WebServer component in REPL:

user=> (type (:web-server system))
clojure.lang.PersistentArrayMap

The :web-server entry is a PersistentArrayMap now, which doesn't implement the Lifecycle protocol.

Start the system again, :web-server is still a map:

user=> (start)
:started
user=> (type (:web-server system))
clojure.lang.PersistentArrayMap

Confirm that server was not started:

$ curl http://localhost:3000/hello
curl: (7) Failed to connect to localhost port 3000: Connection refused

Ah, I see now. What a horrible silent error! https://github.com/stuartsierra/component#creating-components it is noted here in the comments.
Good catch!


Update README.md

Cleaned up requirements and formatting.
added link to console

Regardless if you accept this PR or not youtube-dl has a duplicate "brew install" in the readme.

Thanks a lot!


Throw exception on duplicate database names within a document

Q
A

Type
bug

BC Break
yes

Fixed issues
Fixes #924

Summary
As described in #924, this adds check to the metadata drivers to ensure that database names are not reused within a document. This check is done in the metadata drivers to ensure that it's still possible to re-declare a field from a parent class to change its mapping.

I was able to move the check to the metadata class, so we don't need to implement it in every driver 🎉
With this change, we're now throwing an exception if there are two properties with different names mapped to the same field in the database and both are not marked as notSaved. If they share the same property name we assume the original mapping is overwritten, while if either of them is marked as notSaved we also don't throw a mapping error since we won't have any conflicts due to the mapping. The sorted group relationships in the user document in our tests shows where this can be useful.
To allow a mapping references and embedded relationships as notSaved, I had to drop the NotSaved annotation and move it to the AbstractField annotation to allow references and embedded documents being marked as readonly. I'll need to come up with some more tests to ensure this works consistently, so I might extract that change to a separate pull request.


Tracking: embedded connector node

Phase1: Embedded connector node coexists with the original connector
In this phase, we will migrate connector RPC to the Embedded one step by step, so that we can review it easier and don't need to migrate it in one version.

[x] Extract java_binding common codes into jni_core. https://github.com/risingwavelabs/risingwave/pull/12108
[x] Start a JVM in Rust and register native methods. https://github.com/risingwavelabs/risingwave/pull/12122
[x] Set up necessary environment variables for embedded connector node. https://github.com/risingwavelabs/risingwave/pull/12122
[x] Replace Source CDC RPC with JNI. https://github.com/risingwavelabs/risingwave/pull/12122
[x] Replace Source validation RPC with JNI. https://github.com/risingwavelabs/risingwave/pull/12270
[x] Replace Sink validation RPC with JNI. https://github.com/risingwavelabs/risingwave/pull/12312
[x] Replace Sink coordinator RPC with JNI. https://github.com/risingwavelabs/risingwave/pull/12724
[x] Replace Sink writer RPC with JNI. https://github.com/risingwavelabs/risingwave/pull/12480
[x] Migrate connector metrics from Java to Rust. https://github.com/risingwavelabs/risingwave/pull/12283 https://github.com/risingwavelabs/risingwave/pull/12584

Phase2: Embedded connector node only

[ ] Remove java_binding crate
[x] Disable the connector node and clean up existing codes related to it. https://github.com/risingwavelabs/risingwave/pull/12807 https://github.com/risingwavelabs/risingwave/pull/12804
[ ] https://github.com/risingwavelabs/risingwave/issues/13089

@chenzl25 I've just manually created an all-in-one package that combines connector libs and the risingwave binary. We should automate the workflow in future: https://github.com/risingwavelabs/risingwave/releases/download/v1.3.0/risingwave-v1.3.0-x86_64-linux-all-in-one.tar.gz

Yes. I will take a look. cc @huangjw806


Front End proofreading

Includes:
Studio Pro 9 Refguide > Mobile
Studio Pro 9 How To > Front End
Studio Pro 9 How To > Mobile
Studio Pro 9 How To > Extensibility

Approved via slack, merging


Added v6.0 workaround for upgrade error

Updated: Deploy Mattermost > Upgrade Mattermost > Upgrading Mattermost Server > Upgrading from Releases Older than v5.35 to:

add a note that details a workaround for a specific error that can be encountered during the upgrade

@streamer45 @wiersgallak - I've applied all technical review updates and this PR should now be ready for final review and approval.


Remove out-of-date doc line about supported versions

Coverage remained the same at 72.12% when pulling 481b36c40c7a1f272db41b21606c5dfdc87af37e on Flimm:patch-1 into 02c2fbf1b393782adfeececc0719e4e155ea6208 on django-extensions:master.

Thanks


Bad error message on .await + ?

Code:
#![feature(async_await, stmt_expr_attributes, proc_macro_hygiene)]
use futures::{future, stream};
use futures_async_stream::for_await;

async fn foo() {
    #[for_await]
    for _i in stream::iter(1..2) {
        async {}.await?;
    }
}

Error message:
error[E0277]: the `?` operator can only be applied to values that implement `std::ops::Try`
 --> tests\async_stream.rs:5:5
  |
5 |     #[for_await]
  |     ^^^^^^^^^^^^ the `?` operator cannot be applied to type `()`
  |
  = help: the trait `std::ops::Try` is not implemented for `()`
  = note: required by `std::ops::Try::into_result`

This error message can be very confusing to the user if more than one ? operator is used.

Another case (.await? in #[async_stream]):
Code:
#[async_stream(item = i32)]
async fn async_stream_fn() {
    for _i in 1..2 {
        async {}.await?;
    }
}

Error message:
error[E0277]: the `?` operator can only be applied to values that implement `std::ops::Try`
  --> tests\async_stream.rs:13:1
   |
13 | #[async_stream(item = i32)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ the `?` operator cannot be applied to type `()`
   |
   = help: the trait `std::ops::Try` is not implemented for `()`
   = note: required by `std::ops::Try::into_result`

This fixed in #7.

Unfortunately, this is a compiler bug and probably the fix will require https://github.com/rust-lang/rust/issues/43081.


Cleanup: Force field

What does this implement/fix? Explain your changes.
Some minor changes to modernize Code/ForceField.

Thanks for another nice set of cleanups @AnnaBruenisholz !

Sorry for intruding, I was curious about the changes, so I had a look, and I have a couple comments :)

If only you'd been 2 hours quicker! ;-)
Thanks for catching the problems. I'll fix them in a separate PR


Add devise

This PR containes Following updates:
✅Remove current_user method in ApplicationController, devise will provide us with one.
✅Install and setup devise.
✅Can register a new user.
✅User logs in with a combination of email and password.
✅Hashed password should be stored in the database.
✅Ask for confirmation of email.
✅Can reset password.

As per instruction of last reviwer.
I have Clone the repo, installed the node modules and then installed the gem. After that I run the rails server and everything is working perfectly. I have recorded video for your reference, Please check the below link.
https://drive.google.com/file/d/1BxXZGIpIS3VylgU0a3FF5XaU1CIcyX1g/view?usp=sharing


Stream | sliding window: add storing of slice index into sample

In the call of sliding window operation we add support of storing index of the slice into new key in the sample to be able to reconstruct the order of the slices later. The use-case is e.g. audio segments in data processing.

@andresy since I added some changes it requires someone else to approve.


Fix Avenger backlog email generation

Following the fix in #1031, it is now broken. See linked PR's description for details on rationale and proposed fix.

Part of #1032 (but kept as separate issue due to high priority (feature broken, as opposed to a memo to fix).

I have confirmed that PR #1065 has resolved this issue.

I have confirmed that PR #1065 has resolved this issue.

Ok, will close this issue.


refactor: Change input method for private_key field

Change private key input method to survey.Editor
Signed-off-by: Darren Murray<EMAIL_ADDRESS>

Does the input message needs to change? Have we run this command to test and see if the message feels intuitive enough?

Does the input message needs to change? Have we run this command to test and see if the message feels intuitive enough?


Change Point Interactive

Before submitting (must do checklist)

[ ] Did you read the contribution guide?
[ ] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Proposed Changes

Closing issues

Codecov Report

Merging #988 (ce0a535) into master (926982a) will decrease coverage by 0.56%.
The diff coverage is 8.19%.

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

@@            Coverage Diff             @@
##           master     #988      +/-   ##
==========================================
- Coverage   85.43%   84.86%   -0.57%
==========================================
  Files         148      148
  Lines        7962     8023      +61
==========================================
+ Hits         6802     6809       +7
- Misses       1160     1214      +54

Impacted Files
Coverage Δ

etna/analysis/plotters.py
24.17% <6.66%> (-1.50%)
:arrow_down:

etna/analysis/__init__.py
100.00% <100.00%> (ø)

etna/auto/runner/utils.py
100.00% <0.00%> (+50.00%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Also update the table of contents here


[BUG] fatal error C1001: Internal compiler error.

Not sure what is happening, but since the new versions i'm now getting
[build] D:\<folder name>\.cache\cpm\glaze\27bbdd96fd3142512b169ac3a4ce5040c94972cb\include\glaze/json/write.hpp(1308): fatal error C1001: Internal compiler error.
[build] (compiler file 'D:\a\_work\1\s\src\vctools\Compiler\CxxFE\sl\p1\c\symbols.c', line 32907)
[build]  To work around this problem, try simplifying or changing the program near the locations listed above.
[build] If possible please provide a repro here: https://developercommunity.visualstudio.com
[build] Please choose the Technical Support command on the Visual C++

When trying to use glz::write with a struct
struct WorkshopModConfig {
		uint32_t type;

		std::string title;
		std::string version;
		std::string author;
	};

std::string buffer;
auto ec = glz::write<glz::opts{.comments = true, .error_on_unknown_keys = true, .skip_null_members = true, .prettify = false}>(settings, buffer);
if (ec) throw _logger->error("Failed to serialize mod settings");

If i comment out these lines, the compiler works fine.
I'm using c++23 and Vistual Studio Build Tools 2022

For me, since I defined a constructor for the struct I was writing from I needed to add explicit metadeta to handle the serialization. See https://github.com/stephenberry/glaze?tab=readme-ov-file#explicit-metadata.

Thanks for reporting this. I'll aim to fix this soon. Typically these MSVC internal compiler errors aren't too hard to fix. I just keep adding unit tests to catch more of them.

This issue turns out to be a missing guard for reflected structs when .comments = true, because reflection doesn't support built in comments. Will be merging a fix soon (#1124). If you set .comments = false your code should also run.


Cannot find module 'jquery', map frozen and always showing 'Loading...' on account info

Expected Behavior
Account info and map updated must be updated.

![captura de tela 2016-08-11 as 11 37 32](https://cloud.githubusercontent.com/assets/954889/17592439/b27ce9b4-5fb8-11e6-820e-e896af071915.png)

Actual Behavior
Account info is always showing 'Loading...'
Map is frozen.
Steps to Reproduce
Install normally, npm start and log in.
Information

macOS
PikaBot 0.0.1-alpha

Fixed in https://github.com/PokemonGoF/PokemonGo-Bot-Desktop/pull/135


Fix long line issue in partitioner client

The default requests code can be quadratic in the data size if it finds a single long line without a newline because it is doing the standard append to a string trick.  Switch over to chunking based on raw data and explicitly handle splitting by lines for the early status output.

Update the MockResponses in test_aryn_partitioner.py to include an iter_content
FAILED sycamore/tests/unit/transforms/test_aryn_partitioner.py::TestArynPDFPartitioner::test_partition - AttributeError: 'MockResponseNoTables' object has no attribute 'iter_content'
FAILED sycamore/tests/unit/transforms/test_aryn_partitioner.py::TestArynPDFPartitioner::test_partition_extract_table_structure - AttributeError: 'MockResponseTables' object has no attribute 'iter_content'


Whoops I still have access to this :)

I just noticed I still have access to this, someone likely just needs to remove my individual github account from the repo.

actually i see other FHIR things if I go to icanbwell's org page.. I might still be a member of some helix/fhir group

@imranq2 ☝ just a heads-up

These are open source projects :-)


Allow parameter evaluation on-the-fly with valueFrom.evaluate field

Summary
Add a field valueFrom.evaluate that will run the expression through our evaluator after parameter substitution.
Motivation
Seeing the example in #2801, a Python image is booted up just to add one to a counter on each iteration. This is obviously a waste of resources as it would be easily done by the controller's evaluator.
Proposal
I'll implement this by running the field through the evaluator after parameter substitution.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

I believe this was implemented in #4987 with valueFrom.expression.


Add support for directory overrides

This adds an override command to juliaup:

juliaup override set lts: Sets an override for the current directory to the lts channel.
juliaup override unset: Removes an override for the current directory.
juliaup override status: Shows all overrides.

There are some more options, see the command line help for those.

How does this work? Does it store a file in the given directory? If so, can we document the name of that filev


Foreground color of selected word - Visibility issue

With the latest sublime changes to color schemes and how the default coloring works, you can see in the image the word selected using something like cmd+d or a plain selection, uses black foreground text by default which makes it really hard to see the selected word.
I've made a tiny patch in word_highlight.py to sort this out. I'm not sure it'll be a good solution for everyone, but it essentially fixes the issue to behave like it did before the recent sublime update.
The fix simply drops any selections from the list of regions found by find_regions().
word_highlight.py:237, replace return regions with:
return [region for region in regions if not view.sel().contains(region)]

The result:

I can make a PR if this is an acceptable solution.

Good. It settle my problem. Hope author will follow up this issue.


Update needed for Sphinx 8.0

Describe the bug
The CI build of the SciPy docs is failing with the recently updated Sphinx 8.0.2.  Initially the problem was coming from jupyterlite_sphinx (see https://github.com/jupyterlite/jupyterlite-sphinx/issues/197).  A current pull request there fixes the error that occurs in jupyterlite_sphinx, but the build of the SciPy docs fails again in myst_nb code:
[...snip...]
reading sources... [ 96%] tutorial/interpolate/interp_transition_guide
Traceback (most recent call last):
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/cmd/build.py", line 337, in build_main
    app.build(args.force_all, args.filenames)
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/application.py", line 378, in build
    self.builder.build_update()
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 296, in build_update
    self.build(to_build,
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 317, in build
    updated_docnames = set(self.read())
                           ^^^^^^^^^^^
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 424, in read
    self._read_serial(docnames)
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 476, in _read_serial
    self.read_doc(docname)
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 535, in read_doc
    publisher.publish()
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/docutils/core.py", line 234, in publish
    self.document = self.reader.read(self.source, self.parser,
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/io.py", line 106, in read
    self.parse()
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/docutils/readers/__init__.py", line 76, in parse
    self.parser.parse(self.input, document)
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/myst_nb/sphinx_.py", line 85, in parse
    nb_reader = create_nb_reader(document_path, md_config, nb_config, inputstring)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/myst_nb/core/read.py", line 71, in create_nb_reader
    if path.endswith(suffix):
       ^^^^^^^^^^^^^
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/util/_pathlib.py", line 96, in __getattr__
    warnings.warn(_MSG, RemovedInSphinx90Warning, stacklevel=2)
sphinx.deprecation.RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.

Exception occurred:
  File "/home/warren/py3.12.4/lib/python3.12/site-packages/sphinx/util/_pathlib.py", line 96, in __getattr__
    warnings.warn(_MSG, RemovedInSphinx90Warning, stacklevel=2)
sphinx.deprecation.RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
The full traceback has been saved in /tmp/sphinx-err-1o84nyhg.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
make: *** [Makefile:114: html-build] Error 2

The error occurs in 'core/read.py' at line 71:
https://github.com/executablebooks/MyST-NB/blob/6ce30cd41fa82543e0f315ac8bbee82669b0cc82/myst_nb/core/read.py#L71
If I follow the example of the jupyterlite_sphinx pull request, and change that line to:
         if path.suffix == suffix:

the build of the SciPy docs completes successfully.
Reproduce the bug
See above.
List your environment
No response

Thanks for this report. Will try and get a fix out today (we have been slow to test Sphinx 8).

Thanks @agoose77.  For now, we are sticking with Sphinx 7.4.7 in CI, so we're not blocked.

I've run into this issue, too for some tutorial CIs.
Naively went ahead and opened the PR as it looked all good locally.

Hey, any updates on this one? Just noticed the warning after updating to sphinx v8...


adaptor proteins

are there are any outstanding issues with things
described as 'adaptors' ?
I wanted a term for clathrin-binding adaptors
'select protein cargo to be included in the
internalizing vesicles and recruit endocytic machinery'
to describe the function of adaptins such as AP-3 & 2
adaptor complex
i expect this would go under
protein binding, bridging GO:0030674
synonym protein-protein adaptor
I noticed
cytoskeletal adaptor activity GO:0008093,
this could have additional parent GO:0030674
Reported by: ValWood
Original Ticket: "geneontology/ontology-requests/1435":https://sourceforge.net/p/geneontology/ontology-requests/1435

thanks www.movied.org


Synchronousness of Akka.JVM

Some parts of Akka.JVM are designed to be run synchronously, but unfortunately we cannot block in JS.
For instance, some points that come to mind

Initialization of logging
TestKit

TestKit is the toughest one because it really is 100% blocking. So far I've been able to make it work by using a custom event loop which is able to block, but I wouldn't call it a reliable solution. Ideally the test suite should be refactored to use futures.
I do understand however this is a huge undertaking
@rkuhn @andreaTP @andreaferretti

Yes, rewriting the test suite would be a huge undertaking, and a risky one as well: the test suite is the only thing that keeps us from falling into the abyss—thus is the nature of writing a concurrency toolkit. How does node.js do this? I hear they have “synchronous” APIs that will just stop executing a certain piece of code when it its I/O and resume it when the bytes are ready.

yea, crazy enough there is 'blocking' available through the use of 'fibers' which is supported in V8, and in various forms in node.js. basically this still enforces strict limitations on concurrent access to the JS VM, but it does allow you to run multiple JS stacks in 'fibers' that basically run on a global lock around the VM, and can release the lock inside a function thats executing something outside of the VM (think Thread.sleep())

this is referred into separate issues, testkit is reworked and now much more stable, extensions must be fixed but do not cause bugs now


Trouble to connect for the first time

Hi,
i'm using version v.0.3.2 of the integration
HA is version 0.112.4
To have more logs i set this options in my configuration.yaml:
logger:
  default: info
  logs:
    custom_components.sia: debug

Entities state:
alarm_control_panel.8124_aaa_1_alarm | unavailable | friendly_name: 8124 - AAA - zone 1 - alarm

sensor.8124_aaa_last_heartbeat | 2020-07-15T10:58:57.401882+00:00 (last HA restart was at 14h28)

Ha logs:
Logger: pysiaalarm.base_sia_server
Source: __main__.py:356
First occurred: 2:28:41 PM (43 occurrences)
Last logged: 2:36:23 PM

CRC mismatch, ignoring message.

And Ajax apps says "Not connected" for the Sia server
I don't know what to do... I try with or without encryption...

and what do you have set for the ping interval, and you have dubbelchecked that the exact same settings (account, port, key) are used in both?

1 min for both. Yes, all settings are the same.

in the Heartbeat sensor attribute, i have this:
account: AAA ping_interval: 0:01:00 zone: 0 unit_of_measurement: ISO8601 friendly_name: 8124 - AAA - Last Heartbeat icon: mdi:alarm-light-outline device_class: timestamp
Zone:0 ? Is it normal?
Thanks a lot for your help @eavanvalkenburg !

yeah Zone 0 is correct, the last_heartbeat is unrelated to the number of zones, but is at account level. The thing is that a CRC mismatch means the message that was sent is not the same as the received message, which is strange. Could you add
  - pysiaalarm: debug to your log and then post some rows from your homeassistant.log (so the full thing not just a screen of the toplevel errors (can be found in your config folder or by clicking Load Full HA log on the log page?

Sure:
2020-07-15 15:03:22 DEBUG (MainThread) [pysiaalarm.aio.sia_client] Starting SIA.
2020-07-15 15:05:04 DEBUG (MainThread) [pysiaalarm.aio.sia_server] Incoming line: 43580023"SIA-DCS"0084L0#AAA[#AAA|Nri1/XC12]
2020-07-15 15:05:04 WARNING (MainThread) [pysiaalarm.base_sia_server] CRC mismatch, ignoring message.

There is about 10 occurence of the same debug message "Incoming line: 43580023"SIA-DCS"0084L0#AAA[#AAA|Nri1/XC12"

I'm not sure why this isn't working but I have been working on updates to the underlying package, could you test that one out? Please change the manifest in your HA (in the custom components folder), to this: ["pysiaalarm==2.0.4b0"], and then reboot it should pull in this version. Let me know how it goes! I'm currently testing it, if it proves good for this and some other people's issues, I will release it later this week.

ok, let's go :-)
2020-07-15 15:30:41 INFO (SyncWorker_36) [homeassistant.util.package] Attempting install of pysiaalarm==2.0.4b0
2020-07-15 15:30:54 INFO (MainThread) [homeassistant.setup] Setting up sia
2020-07-15 15:30:54 DEBUG (MainThread) [pysiaalarm.aio.sia_client] Starting SIA.
2020-07-15 15:31:04 DEBUG (MainThread) [pysiaalarm.aio.sia_server] Incoming line: 43580023"SIA-DCS"0084L0#AAA[#AAA|Nri1/XC12]
2020-07-15 15:31:04 DEBUG (MainThread) [pysiaalarm.base_sia_server] Parsed event: Content: #AAA|Nri1/XC12], Zone: 1, Code: XC, Message: 12, Concerns: None, Type: None, Description: None, Account: AAA, Receiver: None, Prefix: L0, Timestamp: None, Length: 0023, Sequence: 0084, CRC: 4358, Calc CRC: 4358, Message type: None, Encrypted Content: None, Full Message: "SIA-DCS"0084L0#AAA[#AAA|Nri1/XC12]..
2020-07-15 15:31:04 WARNING (MainThread) [pysiaalarm.base_sia_server] Code not found, replying with DUH to account: AAA
...
2020-07-15 15:37:23 DEBUG (MainThread) [pysiaalarm.aio.sia_server] Incoming line: 43580023"SIA-DCS"0084L0#AAA[#AAA|Nri1/XC12]
2020-07-15 15:37:23 DEBUG (MainThread) [pysiaalarm.base_sia_server] Parsed event: Content: #AAA|Nri1/XC12], Zone: 1, Code: XC, Message: 12, Concerns: None, Type: None, Description: None, Account: AAA, Receiver: None, Prefix: L0, Timestamp: None, Length: 0023, Sequence: 0084, CRC: 4358, Calc CRC: 4358, Message type: None, Encrypted Content: None, Full Message: "SIA-DCS"0084L0#AAA[#AAA|Nri1/XC12]..
2020-07-15 15:37:23 WARNING (MainThread) [pysiaalarm.base_sia_server] Code not found, replying with DUH to account: AAA

cool, the XC code is a bit of a strange one, so I think you need to set your alarm to just one IP and port, because that might cause some doubling, and the XC code means either: Malfunction Restore | connection restored, [device] in   [room] or Alarm Restore | connection restored, roller   shutter [device] in [room].  So not really sure what that means but at least the connection is now established!

Ajax apps still shows "Not connected" and HA still show "8124 - AAA - zone 1 - alarm" unavailable   :(

It is supposed to start sending RP messages, and YG when you change a setting, please add this to REACTIONS in const.py:
    "XC": {"type": "timestamp", "attr": "last_message"},

and a next beta is coming for the package, because it turns out XC is a code that AJAX added that is not in the base SIA protocol!

ok great.  Many thanks @eavanvalkenburg you're the best.
But Sensor alarm seems to stay at "Triggered" even if i am armed or disarmed.

the fact you keep getting the XC code is strange, seems like there is something wrong in your system that doesn't have anything to do with this component, but I can't judge that, I will close this issue.

Sorry to use this thread but I'm having a similar problem after a system restart:
2021-03-25 09:05:09 DEBUG (MainThread) [custom_components.sia.alarm_control_panel] Loading last state: unavailable
2021-03-25 09:05:09 DEBUG (MainThread) [custom_components.sia.alarm_control_panel] Loading last state: unavailable
2021-03-25 09:05:11 DEBUG (MainThread) [pysiaalarm.aio.sia_server] Incoming line: 8BCA00A2"*SIA-DCS"0411L0#42617263656C6F6E[39ECACC2A75FBD98C06C34FEC43618E880C4E42933D99C262713339C9CF7DD19434BD318033E72F7F862026C42785C38EBDF6C5B071D35034A64AB53B1172F1F
2021-03-25 09:05:11 DEBUG (MainThread) [pysiaalarm.base_sia_server] Parsed event: Content: BhyC.+>|#42617263656C6F6E|Nri0/RP0000]_08:05:28,03-25-2021, Zone (ri): 0, Code: RP, Message: 0000, Concerns: Unused, Type: Automatic Test, Description: Automatic communication test report, Account: XXXXX, Receiver: None, Prefix: L0, Timestamp: 2021-03-25 08:05:28, Length: 00A2, Sequence: 0411, CRC: 8BCA, Calc CRC: 8BCA, Message type: Automatic Test, Encrypted Content: 39ECACC2A75FBD98C06C34FEC43618E880C4E42933D99C262713339C9CF7DD19434BD318033E72F7F862026C42785C38EBDF6C5B071D35034A64AB53B1172F1F, Full Message: "*SIA-DCS"0411L0#42617263656C6F6E[39ECACC2A75FBD98C06C34FEC43618E880C4E42933D99C262713339C9CF7DD19434BD318033E72F7F862026C42785C38EBDF6C5B071D35034A64AB53B1172F1F..

I have two zones, and both are not changing, they remain to Unknown.
 The unavailable state can be because of a mistiming between the last RP message and the expected interval from your setup (if you have it set to 1 min in HA, it will wait for 1 min 30 sec to set the sensors (alarm, moisture and smoke) to unavailable), off course if you're alarm waits 10 minutes between RP messages that causes issues, but that doesn't seem to be the problem.


NL: Implement reranking support

After this change if reranker=cross-encoder-mxbai-rerank-base-v1 is added to the URL param on autopush, we'll perform reranking.
The reranking results will show up in debug-info UI in two ways.
1. Counters of SV lists pre_reranking and post_reranking:

2. Reranking scores in Sentence table:

What is a general range for rerank score and how to interpret them?

I see that each model has its own range, but generally, the higher the relative value the closer the match.  Maybe if we find a model works best, then we can look at its range for further heuristics?

Thanks for the reviews!


Fix about template css

Fix about template css

I wasn't sure of the reasoning behind adding the css class, so I figured I would get you to review rather than directly committing.

It looks like the 2_0_opted.html page has change because of the requested change above. There may need to be another commit to fix the formatting on 2_0_opted.html and 2_0.html

I was lazy and wanted to pick up a background. I'll fix it in another PR.


No journey details are captured if running in new context

Sometimes there is need to start browser with context that is different from default defined in synthetics.config.ts. Like this:
import { step, monitor, journey, Page, ChromiumBrowserContext } from "@elastic/synthetics";

journey("My journey", ({ browser }) => {
  monitor.use({
    ...myMonitorConfiguration,
  });

  let page: Page;
  let context: ChromiumBrowserContext;

  step("Open new context", async () => {
    context = await browser.newContext({
      ...myBrowserConfiguration,
    });
    page = await context.newPage();
  });

  step("Open page", async () => {
    await page.goto("https://example.com/");
  });
});

Pushing this to Kibana works fine and journey is executed, steps are listed properly. But there are no network requests or screenshots recorded for this new context, all you get step with blank page. It would be great if you could either specify custom context in journey options or if all contexts would get recorded.
Screenshot attached.

Hello @kazagz all you need is , we may have a known issue that playwright options you pass via below statement may not work locally but they will once you push to kibana and at execution time
monitor.use({
    ...myMonitorConfiguration,
  });

playwright options you pass via above statement will be passed to the context being used by journey. We don't support creating a new context within journey. Like you rightly pointed out , network data etc will not be captured.

there is some more context provided here by @vigneshshanmugam
https://discuss.elastic.co/t/use-environment-variables-from-kubernetes-pod-in-elastic-synthetics/345396/8?u=shahzad31

@shahzad31 thanks, somehow I had missed this parameter. That's fine if locally it has no effect on monitor.


EDM-297: Publish helm charts under quay.io/flightctl/charts

This makes the charts compatible with ArgoCD usage, since ArgoCD expects a base OCI repo like this.
Also makes the helm charts publishing depending on the publishing of the containers. (Otherwise we would render helm charts that point to a container version that has not been published)

wait do not merge yet
I noticed this will publish quay.io/flightctl/charts/flightctl-helm
while it should be
quay.io/flightctl/charts/flightct


Add _has_memory_hooks to avoid thread local dictionary operation

jenkins, test this please.

Jenkins CI test (for commit e6dba576f4c93ef84c91cc6b888644b6b369700d, target branch master) succeeded!

What is the motivation for this change? Do you mean querying PyThread_get_key_value is faster than accessing an attribute of threading.local object?

Yes

OK. LGTM!


可以设置展示多少层级的地图吗？右侧内容太多了。

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

完成.
v0.5.1: 现在支持设置最大深度

感谢！


npm module relative path conflict

Due to npm relative path conflict, gitconvex is failing to run as a global command line module.

Fixed with commits to the server module
https://github.com/neel1996/gitconvex-server/commit/0fef97587df3a76c10c222db40dd298ef132b68d
https://github.com/neel1996/gitconvex-server/commit/e510ff742e3b361f13db0b9c34ba39eb39f9935a