Build backend: Add --list option

Add the uv build --list, a "subcommand" to list the files that would be included when building a distribution. It does not build the distribution, except when a source dist is required for source dist -> wheel. This is an important debugging tool for the include and exclude options: Did i actually include the files I wanted, or am i shipping a broken distribution? Are there any temporary files I still need to exclude?
Cargo offers this as cargo package --list.
--list is preview-exclusive, since it requires the fast path, which I also put into preview.
Examples:

I'll fix the error handling in a follow-up.
Tagging as enhancement because it changes the stable output slightly (two lines instead of one).
CC @charliermarsh for uv-wide consistency in the stdout/stderr handling.

Although I am not sure I have enough knowledge to understand why --list requires the fast path. Will there be other options that also require the fast path?

Potentially - We may grow more uv build backend only features in the future that don't work through the limited set of PEP 517 hooks. "direct build" is a better term now than fast path. We need to explain to users that uv build can be both the PEP 517 generic source dist and wheel builder (python -m build, pip wheel, etc.) and the CLI command to the uv build system (poetry build, hatch build, maturin build). The latter has more options than the former (maturin build is a good example), while the former is the "official" way, there is some agreement that python -m build is the "official" way to build. By default, uv will be the latter for the uv build backend, but we allow switching to the former with --force-pep517, since this is what your package's users will experience.

I think it's correct for the output to go to stderr in general, and then stdout with --list.

Yeah I like "direct build" a lot better. :-) Otherwise makes sense, thank you for explaining!


Server crash with

Issue Description:
I am running Ender IO in my extremely large modpack called Modsplosion. It is semi private on the ATLauncher and this issue only occurs in servers.
What happens:
When installing Reika's Chromaticraft, I receive this crash report for servers only. Client side, everything works fine and as expected.
What you expected to happen:
Expected result is for the server to start up normally
Steps to reproduce:

Search for "modsplosion" in the ATLauncher and create a server
Open the mods folder and install Reika's ChromatiCraft 1.7.10 V13b (all dependency mods already installed)
Start server and observe crash
...

Affected Versions (Do not use "latest"):

EnderIO: 1.7.10-<IP_ADDRESS>6_beta  &&  1.7.10-<IP_ADDRESS>4_beta
EnderCore: 1.7.10-<IP_ADDRESS>_beta &&   1.7.10-<IP_ADDRESS>_beta
Minecraft: 1.7.10
Forge: 1566

Your most recent log file where the issue was present:
http://pastebin.com/qZcgR3f2

see #3301


Drag and Drop not working in WP 10 emulator

Tried getting this sample to work in the Windows phone 10 emulator and it acts as if it does not know any drag events. it just highlights the text or list items. Should this work on the phone too?

I checked with the feature team. Phone support for drag and drop is not yet as strong as desktop. The functionality is basically the same as on Windows 8.1: You can drag/drop items within a listview, and any UI element can be a drop target, but you don't get dragging to another process or drag customization.

Interesting. Do you know if there will be support for this in the future? It seems like something that would be a great feature add to compete with animations in IPhone and the like. Also, do you know of any examples out there that I can use that demonstrates what drag-ability exists for the phone? None of the ones in your example work at all. Including the list view. I have tried a few in the past that say they work, but don't.

We hope to bring full drag/drop support to Phone eventually, but it's not there yet. I don't know why the Windows 8.1 drag/drop features are not working. Will check with the feature team.

Okay, by experimenting, I found that I can do drag/drop in the listview. You have to press and hold on the item for a while, and then it becomes draggable.

Weird. Ok I'll have try that tomorrow. Is there a timer to it or something? Maybe a different event? This is really something I'm asked about a bit from customers  in regards to my apps and the windows phone in general why drag and drop isn't used more. If it doesn't work well, that is probably why. Hopefully this works because it has been frustrating to get this working. You would think if you can do it on a WP live tile, it should be able to be done in apps as well.

Note that you have to press and hold on WP live tiles too, before you can go into drag/drop mode.

Thank you for your feedback on this issue regarding the drag and drop events on the Windows 10 emulator. As Raymond mentioned at this time we don't support a full-fledged drag and drop feature for Windows 10. However, Windows 10 does continue to support the Windows Phone 8.1 drag and drop feature. Thanks again for your comment, I will now consider this issue closed.

Sam, Thank you. Sorry for the delay, but I was just wondering if there is a future for supporting Phone dragging

We have been actively discussing it for a future release, however we don't have a specific timetable for when it would be added. Your feedback is helpful for us to make prioritization decisions - please keep it coming!

Any update on this? The drag & drop (especially scenario 2) appears to be critical for my project at the moment. However the samples are still not working on Phone device and Phone emulators (though all are working well on desktop).
Could you help us with this functionality on Phone devices at the earliest? Thanks a ton.


npm fail to install packages with dependencies on node 0.12.x

Hi,
The script is not working when you have a dependency on a package that requires node 0.12,
Because of the warning "The iisnode.yml file explicitly sets nodeProcessCommandLine. Automatic node.js version selection is turned off." a really old node.js is selected, and the package cannot install.
you can try with https://github.com/msgpack/msgpack-node version 0.2.6.

Hey, thanks for reporting! You actually won't have to use this repo anymore to use Node 0.12 - you can instead just specify the engine parameter in your package.json. Node 12 is now preinstalled on all Azure Web Apps (formerly known as websites), so this is enough:
{ "engines":
    { "node" : ">=0.12.0" }
}

If you want to use a custom version of Node, this repo is still perfect - if that's the case, I'm happy to look into your problem :)

I am using this repo for specifying --harmony flag, couldn't find other way.
Anyway, the problem is not in this script... it's while building on any node.js version.


Expose session ticket statistics.

Motivation:
We recently added support for session ticket statistics which we can expose now.
Modifications:
Expose the statistics.
Result:
Be able to obtain session ticket statistics.

This depends on https://github.com/netty/netty-tcnative/commit/16f99bf116803037d3c2b354c9e8e34838daebed so needs a new netty-tcnative release first.
@cconroy PTAL as well...
@Scottmitch @nmittler PTAL

LGTM

lgtm

LGTM
Thanks!

Cherry-picked into 4.0 (0a01d85b598c5ea4e9d80f6e1fa6f89c7321d36a) and 4.1 (2546d99864cf75597fe80ae314036d719534a504)


Fix a typo in the readme

not sure, why it shows line 95 as changed... I only changed the typo in line 68

You (or your client) added an empty string

Oh well, that seems to be a feature of the github inline editor then :). Feel free to close this PR and just fix the typo on your side ;-)

I'll just merge #13 instead if that's ok with you @mo-gr, it does the same without the empty string.

Sure! Merge #13 instead :+1:


Azure: enable podvm images nightly build

Could we turn this into a reusable workflow to share the code with the azure e2e test?

We should definitely do that. We don't have to maintain code in two places for the same thing.

Could we turn this into a reusable workflow to share the code with the azure e2e test?

We should definitely do that. We don't have to maintain code in two places for the same thing.

I took the commits from this PR and consolidated it with the e2e test workflow to share the build job.

Merged along with This !!


Text in the navigation bar does not vertically align with the logo

As suggested in the title, we need to add padding to the text such that the navigation links are vertically aligned with respect to the logo in the navigation bar section.

Linked already closed PR by @pritshah9 above, which resolves this issue.


Multiple actions not possible

Hi, in our app, we have a scenario where we need to do something like this in one step:
dispatch(go(-2))
dispatch(replace('/new/url'))

Currently we don't see a way to do that with react-router-redux. If we execute that code, we do not reach /new/url. In redux dev tools I can se that the second LOCATION_CHANGE action is dispatched before the first one.
Is there some way to achieve this, maybe as workaround by manipulating history another way?

Your code is likely being short circuited. Doing a history "transaction" isn't something it supports itself. You would have to do this kind of thing in your own code:
let nextAction

if (something) nextAction = go(-2)
if (somethingElse) nextAction = replace('/new/url')

dispatch(nextAction)


Versionbot doesn't ignore already merged PRs

See https://github.com/resin-io/resin-ui/pull/450#discussion_r102524450, where a comment on the PR after merge triggered an error.

This is down to the procbots/versionbot/ready-to-merge label still being assigned, and because a pull_request event is being fired on comments. Essentially, the label should be automatically removed on a successful merge.

It does now, the unlabeling occurs and further comments do not provoke it.

Do not provoke the VersionBot, lest you feel its wrath.

 :)

Do not provoke the VersionBot, lest it spams multiple identical comments on your PRs :laughing:


Sub/superscript are displayed as plain text characters in the TEI output

First re-flexion, identify piece of text as sub/superscript based on position, fonts, etc.

Hey there, I had a quick question. I just started tinkering with grobid and I was wondering if the superscript/subscript identification can be added through training such as giving the following training data:
β-cell Endoplasmic Reticulum Ca2+
<titleStmt>
  <title level="a" type="main">β-cell Endoplasmic Reticulum Ca2+</title>
</titleStmt>

thanks for the input

subscript and superscript flags are attached to the tokens so we could serialize with  and  elements yes.
Similarly we could add <hi> for bold and italic tokens.

I'm starting to work on implementing this feature.
What should be done when the token contains combinations? Like italic + bold, or italic+bold+superscript?

With the current recognition, the "style" features could support indeed in principle at least italic, bold, superscript/subscript.
The TEI guidelines introduce <hi> to encode "graphically distinct" text and there is no constraint on the values, see here. We often see values space-separated (for example <hi rend="bold italic superscript">).
In TEI, there's also <rendition> element which uses CSS, which might be more predictable and would not required to further customize the XML schema.
I think what's complicated are the relations and the possible clash with other structures/tagging.

when this style information should be ignored: For instance a reference marker is often in bold or a superscript number. But the logical "reference" structure is already captured by the <ref> labeling and there is no point in keeping rendering information here. The <hi> is only relevant to text without any other explicit other logical mark-up. The only exception I think would be superscript/subscript inside a formula.

to maintain hierarchical structures: The <hi> element would be an inline annotation (like <ref>) so it is always under structure tags like
 or <s>. This is indeed complicated for sentence segmentation, because the sentence segments are introduced after the initial serialization, directly on the TEI objects (this was to simplify the serialization! working with a tree structure ensures that we have well-formed XML at the end). The <hi> tags should be manageable as the <ref> tags in segmentIntoSentences - except if the bold/italic/etc covers more than the sentence. If a highlight style to be labeled covers more than the current sentence, we would need to close it with the end of the sentence, and re-open it in the next sentence.

[...]

The TEI guidelines introduce <hi> [...]

I'm using <hi rend="bold italic">... and it seems to work fine by adding several formats.

I think what's complicated are the relations and the possible clash with other structures/tagging.
* when this style information should be ignored: For instance a reference marker is often in bold or a superscript number. But the logical "reference" structure is already captured by the `<ref>` labeling and there is no point in keeping rendering information here. The `<hi>` is only relevant to text without any other explicit other logical mark-up. The only exception I think would be superscript/subscript inside a formula.

Yes, we don't want to decorate references, and that was quite easy as the references are already separated by the text 😄
I've decorated formulas with only superscript/subscript.

* to maintain hierarchical structures: The `<hi>` element would be an inline annotation (like `<ref>`) so it is always under structure tags like `<p>` or `<s>`. This is indeed complicated for sentence segmentation, because the sentence segments are introduced after the initial serialization, directly on the TEI objects (this was to simplify the serialization! working with a tree structure ensures that we have well-formed XML at the end). The `<hi>` tags should be manageable as the `<ref>` tags in `segmentIntoSentences` - except if the bold/italic/etc covers more than the sentence. If a highlight style to be labeled covers more than the current sentence, we would need to close it with the end of the sentence, and re-open it in the next sentence.

Yes, that's the plan, so I've implemented the style for the case where there is not sentence splitting.
The implementation in segmentIntoSentences is more complicated because of the sentence truncation and, generally, because I have to introduce the layoutToken list and keep them in sync with the text.
One question about the spacing when adding the <hi> tag. Usually spaces are removed before attaching them as child so my current strategy is preserve the spaces when I'm attaching the children to the or`.
The method is here for information: https://github.com/kermitt2/grobid/blob/d5ae544febd66739b48a847e1f9c64677467986f/grobid-core/src/main/java/org/grobid/core/document/TEIFormatter.java#L1406
I'm attaching some output examples:

1704.00030.pdf.tei(1).xml.zip (example with formula)
2101.00027.pdf.tei.xml.zip
test.styles.pdf.tei.xml.zip
grobid/files/9176998/2101.00027.pdf.tei.xml.zip) (I've made this example with Ms word, however certain superscript/subscript information are not there at all in the pdfalto output... probably hidden in the font size/position)

I think it's now implemented by injecting <hi rend="bold italic">. The flow of decoration is interrupted by references (that was easy) and sentences (that was a pain).
I've also tried to modularise a bit the code in methods, so that could be unit tested as different components.
I tried not to run the realignment of the code 😅 which usually make a mess...
I'm sending some examples:
Examples.zip


Can't fling customBuilder sheet closed by dragging on header header.

Bug
When using a customBuilder for the sheet, you can't fling the sheet closed by dragging on the header, It snaps back up.
Video
untitlssssssssssed.webm
Sample Code
import 'package:flutter/material.dart';
import 'package:wtf_sliding_sheet/wtf_sliding_sheet.dart';

void main() {
  runApp(const MainApp());
}

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
          appBar: AppBar(
            title: Text('Hello World!'),
          ),
          body: SlidingSheet(
            snapSpec: const SnapSpec(
              snap: true,
              snappings: [0.2, 1.0],
              positioning: SnapPositioning.relativeToAvailableSpace,
            ),
            body: Center(
              child: Text('This widget is below the SlidingSheet'),
            ),
            headerBuilder: (context, state) {
              return Container(
                height: 100,
                color: Colors.black,
                child: Center(
                  child: Text("Header"),
                ),
              );
            },
            customBuilder: (context, controller, state) {
              return SingleChildScrollView(
                controller: controller,
                child: Column(
                  children: [
                    Container(
                      height: 100,
                      color: Colors.red,
                    ),
                    Container(
                      height: 100,
                      color: Colors.blue,
                    ),
                    Container(
                      height: 100,
                      color: Colors.yellow,
                    ),
                    Container(
                      height: 100,
                      color: Colors.red,
                    ),
                    Container(
                      height: 100,
                      color: Colors.blue,
                    ),
                    Container(
                      height: 100,
                      color: Colors.yellow,
                    ),
                  ],
                ),
              );
            },
          )),
    );
  }
}

Hello @dickermoshe!
Did you try to use any of parameters: closeOnBackdropTap, closeOnBackButtonPressed, isBackdropInteractable?
Otherwise you can wrap the SlidingSheet in the Stack or sth similar to close it from the any place.

Did you try to use any of parameters: closeOnBackdropTap, closeOnBackButtonPressed, isBackdropInteractable?

Every variation of these 3 still results in the slider snapping back open

Otherwise you can wrap the SlidingSheet in the Stack or sth similar to close it from the any place.

If anyone comes here with this issue, they should use a CustomScrollView.
Use a SliverPersistentHeader with pinned: true and put the body in a SliverList.


RFC: Make OAuth*Problem extend ProblemException instead of werkzeug

Description
I wonder if these should extend ProblemException instead of the werkzeug exceptions.

connexion.exceptions.OAuthProblem(werkzeug.exceptions.Unauthorized)
connexion.exceptions.OAuthResponseProblem(OAuthProblem)
connexion.exceptions.OAuthScopeProblem(werkzeug.exceptions.Forbidden)

I'm not sure the logic behind not using ProblemException for these. I wonder if it has something to do with making it more secure or to get better handling in Flask.
Ultimately it feels out of place when you consider adding aiohttp (and other frameworks #828 #440) support.
This is related to #955, and could be included in it, but seems slightly orthogonal to that effort.
Expected behaviour
Don't extend a framework specific exception inside Zalando core.
Actual behaviour
Aiohttp ends up using the werkzeug exceptions.
Steps to reproduce
Read the code.

The docs are incorrect. They say that OAuthProblem extends both Unauthorized and ProblemException which would probably be good enough to allow better framework interchangeability without using werkzeug directly in, for example, aiohttp.
https://connexion.readthedocs.io/en/latest/exceptions.html?highlight=ProblemException
https://github.com/zalando/connexion/blob/d8cd116154c957e0a9f0abb321189b29f2b6a10e/docs/exceptions.rst#L9-L10
https://github.com/zalando/connexion/blob/d8cd116154c957e0a9f0abb321189b29f2b6a10e/docs/exceptions.rst#L18-L28
https://github.com/zalando/connexion/blob/fda2b18b38f4f3dc26338195240ffb7a77f5c6db/connexion/exceptions.py#L81-L96

The code changed away from what is listed in the doc in https://github.com/zalando/connexion/commit/bce907f72492a518e60710aba5057a884ae66395
This section of the doc hasn't changed since added in https://github.com/zalando/connexion/commit/7a9329fe6be88fb69b4d1d278ec1265897c0bd9a


Log accordingly to a field, is there possible ?

I would like to log accodingly to field in the log, like this:
log.WithFields(log.Fields{"Field": "logname"}).Info("My log message!")
So all logs that contains that field would go to logname.log, if I have:
log.WithFields(log.Fields{"Field": "logname2"}).Info("My log message!")
It would go to logname2.log
How can I achieve that ?

Hm... An interesting usecase. Not one I'd considered going into this.
Currently, It's not something that can be done. I set it up to be an exact mapping between entry.Level and a file, then later streams were added. If you want to write a PR you could probably do something similar to the introduction of streams.
If you wanted to add support for file routing by Fields you would need the following:

You'd have to add code to the fileWrite method that would allow using something other than entry.Level as the file selector.
You'd have to add a Field-Filename map that would be set in the contructor. Similar to the PathMap, and if you just create a different type like FieldPathMap then it could be supported without too much difficulty.

I don't see it as a super complex change, but you'd have to be really careful to not introduce regressions.


Error IPAM detection in k3s dual stack

Hello,
I am writing to you because I have an error regarding the ipam allocation in my cluster. My infrastructure consists of two master nodes and two worker nodes with a k3s cluster, with calico as cni and metallb as load balancer. It also works with dual stack. When I installed it, I defined two CIDR, one for the cluster and one for the services, as you can see here:
k3sup install \
    --host=x.3.190 \
    --user=root \
    --k3s-version=v1.23.6+k3s1 \
    --local-path=config.demo.yaml \
    --context k3s-dual-stack \
    --cluster \
    --tls-san x.x.3.196 \
    --k3s-extra-args="--disable servicelb --flannel-backend=none --cluster-cidr=<IP_ADDRESS>/16,fd42::/48 --service-cidr=<IP_ADDRESS>/16,fd43::/112 --disable-network-policy --disable=traefik --node-taint node-role.kubernetes.io/master=true:NoSchedule --node-ip=x.x.3.190,2001:x:x:x:1234::10"

When installing calico, in the installation file only let me define a range of ip, in the custom resources file.
apiVersion: operator.tigera.io/v1
kind: Installation
metadata:
  name: default
spec:
  # Configures Calico networking.
  calicoNetwork:
    # Note: The ipPools section cannot be modified post-install.
    ipPools:
    - blockSize: 26
      cidr: <IP_ADDRESS>/15
      encapsulation: VXLANCrossSubnet
      natOutgoing: Enabled
      nodeSelector: all()
    - blockSize: 122
      cidr: fd42::/48
      encapsulation: None
      natOutgoing: Enabled
      nodeSelector: all()

So when I do ./calicoctl ipam check I see how there are ips that are not within the ipam range, which generates that the corresponding routes are not created in the nodes and can not communicate.
../calicoctl ipam check
Checking IPAM for inconsistencies...

Loading all IPAM blocks...
Found 6 IPAM blocks.
 IPAM block <IP_ADDRESS>/26 affinity=host:kube5:
 IPAM block <IP_ADDRESS>/26 affinity=host:kube4:
 IPAM block <IP_ADDRESS>/26 affinity=host:kube2:
 IPAM block <IP_ADDRESS>/26 affinity=host:kube1:

[...]

Looking for top (up to 20) nodes by allocations...
  kube4 has 5 allocations
  kube5 has 3 allocations
  kube2 has 1 allocations
  kube1 has 1 allocations
Node with most allocations has 5; median is 1

Scanning for IPs that are allocated but not actually in use...
Found 0 IPs that are allocated in IPAM but not actually in use.
Scanning for IPs that are in use by a workload or node but not allocated in IPAM...
Found 0 in-use IPs that are not in active IP pools.
Found 18 in-use IPs that are in active IP pools but have no corresponding IPAM allocation.

Check complete; found 18 problems.

So I would appreciate if you could tell me how to configure the cluster so that both ipam are detected and the routing tables are configured correctly so that the pods can reach the services.
Thanks in advance,
Pablo.

Hi,
Thanks for your answer. I finally found the problem. If anyone has encountered this problem, and your are building a K3s dual stack HA cluster with calico as CNI, dont forget to put this lines in the calico.yaml.
"container_settings": {
              "allow_ip_forwarding": true
          }


Aeon Labs Home Energy Meter Gen5 not updating values automatically

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
Opening a new issue as requested here.
The HEM does not send automatic updates even though it is configured to do so. Values get updated with manual refresh.
("I have checked the troubleshooting section and my problem is not described there. *" : Unfortunately I wasn't knowledgeable enough to complete the steps described here)
Device information
Manufacturer: Aeon Labs
Model name: Home Energy Meter Gen5 (ZW095)
Node ID in your network: 8
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
Driver version: 8.0.5
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
Automatic updates are working with the same device and settings on Openhab and its Z-Wave implementation.
Attach Driver Logfile
interview_zw095.txt

Any chance you have access to zwavejs2mqtt? The official HA integration does not seem to include all log messages in the output, although you set it to debug.

Hopefully this works better:
zwavejs_2021-07-29.log

The associations etc. look okay, but for reference could you look up how they are configured in OpenHAB?
I don't see any reports come in after the interview, but this could be due to the configuration. You currently only have Power reporting enabled for the whole device (none of the single clamps) and these settings:

Maybe your power consumption is so stable that this relative change of 50W isn't reached?

A bit of a setback happened. I loaded my Openhab instance just to see if the HEM is still sending automatic updates. It is not, and I'm not sure what caused this change. As far as I can remember, the only things I did were
a) add HEM to HA using its Z-Wave integrations / addons
b) just after your last post, change the Selective Reporting to disabled through zwavejs2mqtt control panel to make sure the thresholds wouldn't be a problem
In Openhab (through the Z-Wave control software Habmin), I also changed the Power Change Thresholds (options 4 and 8) to 1. With these settings the automatic updates for Power (Whole HEM) should happen every 5 seconds OR if the Selective Reporting would be enabled, after 1W or 1% of change.
As this is the case, I'm guessing Openhab isn't much of a reference anymore.
A bit of background from Openhab where things worked for two years prior to this: it was a PITA to get working even in there and judging by this thread, still is. This is my comment of how I got it working. The latest posts link to a tutorial that someone made which correlates with my own experience:

HEM has a problem/is challenging with associations and the tools within Openhab do not set them in such a way that the automatic updates would work
From Aeotec support:

"There is an issue when using Multichannel Association which causes the HEM Gen5 to not report correctly. One way to resolve this issue is to remove the Multichannel Association of Node ID 01 endpoint 1 from Group 1. Then re-associate Node ID 01 to Group 1 using “Group Association”. Alternatively you could use “Multichannel Association” and assign Node ID 01 endpoint 0 to Group 1 which will work as well."

Without understanding much from the above, redoing the association with 3rd party tools (in my case Zensys Tools) fixed the problem

Sorry about the lengthy post. Hopefully this will give some clues for next steps? I know I could probably try to do the magic with Zensys Tools again but would of course prefer a proper fix.

Alternatively you could use “Multichannel Association” and assign Node ID 01 endpoint 0 to Group 1 which will work as well."

Hmm, but that's what zwave-js does:
2021-07-29T12:08:29.473Z DRIVER « [Node 008] [REQ] [ApplicationCommand]
                                  └─[MultiChannelAssociationCCReport]
                                      group id:           1
                                      maximum # of nodes: 5
                                      node ids:
                                      endpoints:          1:0

Group 1 is assigned with a multi channel association to Node 1, endpoint 0.
Not sure about HA, but zwavejs2mqtt lets you configure the associations to the full extent. I'm guessing that shows you a target of node 1 without endpoint now? If that is the case and it works, we can add configuration that forces zwave-js to use a node association instead of a multi channel association.

With lack of better terms, I'm going to call what is presented in the Groups list as '0 Lifeline NodeID_1 None' as "None" and '0 Lifeline NodeID_1 0' (the default one) as "0".
After some testing: when None is added to the Groups in Z-Wave JS Control Panel so that both that and 0 are present, automatic updates start to work. Great!

Log file when both None and 0 are in the Groups list and automatic updates are working:
zwavejs_2021-07-30.log
Not that I needed to do anything else, but after adding None I tried to remove 0 from the Groups and this is when things got weird (this is reproducible):

when 0 is removed automatic updates stop working
-- if a new interview is done at this point 0 is back and None is gone
if after removing 0, None is added again (even though it's still on the Groups list), automatic updates start to work but stop working when a new interview is done; after the interview only 0 is present and automatic updates no longer work

Interviewing when both 0 and None are present on the Groups list doesn't break anything: they both stay on the list and automatic updates still work which is good.
I don't know if this information is of any use but it sure confused me for a good while.

Please don't re-interview after changing the associations manually.
I assume that you just need one of the two, question is which one.

Adding "None" makes things work. Let me know if you need me to test or log anything else.

So to be clear, you now only have one association to node 1, endpoint none?
And this is working?

No, I have both like the screenshot above.
When association to node 1, endpoint 0 is removed automatic updates stop working.
It is possible to achieve a scenario where the updates work and the control panel only shows association to node 1, endpoint none - however this seems fiddly as I have to re-add association to node 1, endpoint none even though it is still on the Groups list after removing association to node 1, endpoint 0.

this seems fiddly as I have to re-add association to node 1, endpoint none even though it is still on the Groups list after removing association to node 1, endpoint 0.

I think that's actually the setup we need. Can you make a logfile of you trying to achieve that status? I'd like to see what exactly is being configured here.
Not that the UI is doing something weird here.

Removed all association groups
Interview
Association groups at this point:
0	Lifeline	NodeID_1	0
Start logging
Add  0	Lifeline	NodeID_1	None (updates start to work)
Remove 0	Lifeline	NodeID_1	0 (updates stop working)
Add  0	Lifeline	NodeID_1	None (updates start to work)
Association groups at this point:
0	Lifeline	NodeID_1	None

zwavejs_2021-07-31.log

Okay, something strange is going on when you remove the association to endpoint 0, but it looks like I was on the right track.


Remove Release Gold configuration

There is little difference between the Release and Release Gold configuration. Mostly just a few optimization settings. Ideally we should only have a single release configuration, with one set of optimization settings. We should perhaps merge the differences, and remove the Release Gold configuration.
Currently I see the following differences in settings:
Release Gold|Win32:
      <Optimization>Full</Optimization>
      <FavorSizeOrSpeed>Speed</FavorSizeOrSpeed>
      <InlineFunctionExpansion>AnySuitable</InlineFunctionExpansion>
      <OmitFramePointers>true</OmitFramePointers>

Release Gold|x64:
      <Optimization>MinSpace</Optimization>
      <FavorSizeOrSpeed>Size</FavorSizeOrSpeed>

Release (Win32 and x64):
      <Optimization>MaxSpeed</Optimization>
      <EnablePREfast>true</EnablePREfast>

As a side note, I once read that due to effects of processor caches, optimizing for size often produced the fastest code. I don't know if that is still true.

I generally have three "Release" builds:

The default Release build: useful for profiling (never profile debug code!)
A FastDebug build: A copy of the default but with optimizations turned off to facilitate step-through debugging.
And a FinalBuild build: All optimizations turned on and all debug pre-processing defines and asserts disabled.

Well, they do allow multiple configurations for cases where you might need them. In our case here, I don't think we really need them. We don't do anything too fancy development wise.
For distribution licensing reasons (on the Microsoft debug runtime), we can only really distribute the Release versions. That's somewhat reflected in the AppVeyor builds, which are only setup to build the Release versions. The other part simply being build time. If you want the Debug versions, that's likely only for local debugging.
I think Leeor was looking into removing the Gold configuration at some point in the past.


Match best practices on different url

https://landscape.cncf.io/selected=git-lab
GitLab has a best practices badge but it's not showing because the badge is registered under a non-GitHub repo:
https://gitlab.com/gitlab-org/gitlab-ce
https://bestpractices.coreinfrastructure.org/en/projects/42
Please add support for a new key called url_for_bestpractices and if it exists, try it instead of repo_url to match against the best practices JSON.

Ok, I'll add this to the allowed keys


Compatibility request.

I provide this because of one reason: I normally use Just Enough Items instead of REI. And well... I'd like to ask if it's possible that you could provide support for JEI on the forge build in particular. Reason being is that JEI and REI do not play nicely with one another and cause the game to instantly crash as soon it even detects the mods. (So while the issue isn't from this mod directly, the requirement of a mod that conflicts with another that i prefer over the required one, is still a form of issue at the least.)
Also this is mostly for 1.18.2 as FYI I should mention.

indeed,pls make a JEI Compatible version (also,Jade is used way more than WTHIT/TOP)

JEI of Forge already does what this mod does for REI though?

I can do JEI and Jade support for Fabric though


Jesse: Watch Alejandro Flores Morales

Jesse requests the watch of the watch_keyword Alejandro Flores Morales. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Alejandro Flores Morales has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Refine code for annotated type handling

Pull Request Checklist

[x] Fixes # this PR follows up on #1160
[x] Tests added
[x] Documentation/examples added : this is refactoring. no need
[x] Good commit messages and/or PR title

Description of PR
Currently, we are checking annotated, parameter/artifact, or other types in different ways.
In this PR, I added hera._utils.type_util module and unified them into one place.
Followings can be expected:

If there's another metadata along with Parameter or Artifact, they should be ignored. (e.g. Annotated[type, metadata1, metadata2, Parameter(...)], this can be happened when Annotateds are nested)
Optional parameter handling should be more precise which is added in #1160.

Suggestions on function names/module names are welcome.

Checked all review comments, feel free to check this PR again :)

@alicederyn can you also review this please.

Thank you all for great reviews! I applied it @elliotgunton @alicederyn

I updated to guard multiple type annotations: https://github.com/argoproj-labs/hera/pull/1168/files/77757b9bef13ee4f749736d57125e06120a54a65..5df6da25630dd50c77022e7fa2d196547b146972
Thank you again @elliotgunton !


Has the behaviour of RVMparser been changed ?

Hy Christopher
We discussed rvmparser on linkedin three years ago.
I don't know if you remember that discussion
I have implemented a module in rvmparser to simplify the PDMS hierarchy. This module regenerates an rvm file by grouping the geometry at a level passed in parameter.
After incorporating this module in the latest version of RVMparser in order to take advantage of the export functionality in gltf format, I notice that the reading of simplified rvm files does not work anymore. Has the import algorithm of the rvm files changed?
Thanks for your answer.

Hi,
Yes, there has been some changes as I have learned more about the RVM format:

len field in chunk header reinterpreted as offset-to-next-chunk
if cntb chunk has a version greater than 2, it has an extra word with transparency info
support for COLR, INSU, and OBST chunks.

In what way does reading of the simplified RVM file fail?

Hi Christopher,
Here is the error I get when I run rvmParser on a streamlined RVM file
Failed to parse E:\CAO\Home\HLF1025Export_Roombat_sbfi_PENE-compact.rvm:
After chunk PRIM, expected offset 0x180, current offset is 0x420c
I think there is a problem with the offset control of the PRIM chunk
After commenting the line 323 of parserRVM.cpp
if (!verifyOffset(ctx, "PRIM", base_ptr, curr_ptr,
expected_next_chunk_offset)) return nullptr;
The glb file seems to be correctly generated
Have you an idea about this problem
Sincerely
Le mar. 25 janv. 2022 à 08:01, Christopher Dyken @.***>
a écrit :

Hi,
Yes, there has been some changes as I have learned more about the RVM
format:

len field in chunk header reinterpreted as offset-to-next-chunk
if cntb chunk has a version greater than 2, it has an extra word
with transparency info
support for COLR, INSU, and OBST chunks.

In what way does reading of the simplified RVM file fail?
—
Reply to this email directly, view it on GitHub
https://github.com/cdyk/rvmparser/issues/34#issuecomment-1020869505, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFMQB7WMMD6TX6LCLN6UA3UXZDFLANCNFSM5MWY262Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi,
The offset field is the offset of the next chunk. The PRIM chunk can vary in size depending on what kind of primitive is contained.
Are you sure you calculate this correctly when generating the file and that the problem is in rvmparser?
This offset is only needed to verify file integrity (and it could be used to skip unknown chunks), so the test is really not essential for rvmparser to work. So it can be skipped as a work-around

I also go this error while trying it on a large file at work.
Tried to produce new RVM file on just that site, but was not able to reproduce error.
So my issue might be something auto coloring they do during the export with PDMS PML script/MAC files.
@anadana Did you find out more btw ?
Looks like commenting out the verify part helped, but ran into memory issues due to file size (4,7 gig RVM 😄 )
Think I need to figure out how to read main 1 site, then generate glb, clear memory, then read/produce next site/main group.
Just need to learn c++ first 😂

The RVM offset fields are 32 bits, so max offset is ~4.2GB, so I guess a 4.7GB file gets a wrap-around.
Might be sufficient to replace line 101 in ParserRVM.cpp with
uint32_t current_offset = uint32_t(curr_ptr - base_ptr);
as the comparison is then done in 32 bits and not 64 bits.

@cdyk
Thx, Ill give it a try, will post back how it goes in a few minutes
Looks like I got a few more errors while parsing
Ended up with this duing the gltf export
Assertion failed: ctx->dataBytes + size <= std::numeric_limits<uint32_t>::max(), file D:\rvmparser\src\ExportGLTF.cpp

Changing line 64 i in ExportGLTF.cpp helped.
Ended up with a 7,9gig gltf 😂
assert(ctx->dataBytes + uint32_t(size) <= std::numeric_limits<uint32_t>::max());

@cdyk
Btw, in ParserRVM I ended up with changing line 102 to
if (uint32_t(current_offset) == expected_next_chunk_offset) {
Else snprintf gave errors, dint know anything about formatting, so was easier for me to do it this way.

The glb container format has a 32-bit length field in the header, i.e. a max size of 4GB, and all references into the binary blob is 32 bits as well, so that file is probably invalid. Handling more than 4GB of geometry requires splitting the gltf-data into multiple files, which rvmparser doesn't do.
I would suggest splitting the rvm-file into layers/zones so that each piece is more manageable.

Trying to use existing files generated by pipline to naviswork I have no control of/can not change. Only access to RVM file.
So will probably need to modify the rvm parser to generate 1 glb file per site, who knows maybe Im very lucky... will just take a very long time to figure out while trying to learn :-)
Or just generate json file/pure buffer file and parse that into more manageable pieces.
@cdyk Btw, thank you for taking the time to respond. 👍 🥇

With no control of the input file, splitting into layers would be the first thing I would try. If you're lucky, the files have a suitable attribute you can use for splitting (use --output-json to create a massive json-file with all metadata) or there is a suitable prefix in the name (use --output-txt to get a text file with all node names).
If you look at DiscardGroups.cpp, that code discards the part of the node hierarchy that doesn't the condition tested on line 47. In this case, it is just a list of groups to discard read from a text file, but an alternative would be to check if the group name starts or does not start with a given prefix.
Another test one could do is to check if the node has a given attribute, and if so, check if it its value matches. If it matches or does not have the attribute, process the node and recurse into the children, otherwise just return from the function.
Another place to attach is in the ExportGLTF.cpp filem, in the processGroup function. This function traverses the hierarchy and sets up the data to write. You could have a test on the start whether or not you want to export this part of the hierarchy (e.g. check prefix of name or attribute). If you wrap the exportGLTF function body into a loop, you can directly export all layers you specify one-by-one.
A really simple predicate is, if the hierarchy "split point" you want is always at a given level in the hierarchy, is to keep track of recursion depth when you call processGroup, and when you are at the given depth, only recurse into the n'th child.

Thank you. 👍

FYI
Got it to do what i needed, modified it a lot to my needs in main/gltf export.
Wanted the buffer as pure buffer file, gltf meta as json I could read with javascript to process the data more/merging etc, that why we have a few edits in the exportgltf..
https://github.com/VegarRingdalAibel/rvmparser/blob/file_per_site/src/main.cpp#L280-L306
When and if I get time to clean up more I will :-)
Yes, some parts might be weird.. but Im pretty new to c++ :-)
Though I could post it here just incase it can help someone else too.
@cdyk Thanks again for taking the time to respond, really helped a lot. 🥇

@cdyk
Hi, have you ever seen something like this ?
Ive kinda limited it down to site of RVM file, but its getting harder to get closer to item atm
Figured I could ask, since I knew what was wrong last time :-)

It is libtess that breaks for some reason. It is used to triangulate polygon faces of facetGroup primitives.
You can try to go up in the stack trace to triangulationFactory::facetGroup and look at the polygon that is triangulated.
Either the polygon is degenerated in some way that libtess doesn't like (eg duplicate or colin ear points or nan's etc) or data points to uninitialized memory (0xcdcdcd..), which might be a bug in rvmparser.

If the input data contains nan, it is just garbage, so IMO one should just discard it (possibly with a warning), ie what you have done.
I think I would have had the check when reading the rvm file, to filter it out as early as possible.
Btw, it looks like your code only checks the first component of the first vertex in each contour. Also, std::isfinite checks both nan and infinity, infinity in vertex positions isn't very useful either.

yes, I prob should move it.
But havent had much time to learn c++, but it is on my todo list.
Would have been nice to have a better understanding of the code.
Just need to make time between all other hobby projects.
Thx for pointing me in the right direction btw. 🥳

@cdyk Love the activity, your a machine lately 🥇 👍


Cannot pull - Cannot stash

Hello,
I was pulling my github clone and I got this:
git pull                                                                                [40/43122]
Updating cd3a1cc..4e1dfc6
error: Your local changes to the following files would be overwritten by merge:
        public/fonts/Inter-Black.woff
        public/fonts/Inter-Black.woff2
        public/fonts/Inter-BlackItalic.woff
        public/fonts/Inter-BlackItalic.woff2
        public/fonts/Inter-Bold.woff
        public/fonts/Inter-Bold.woff2
        public/fonts/Inter-BoldItalic.woff2
        public/fonts/Inter-ExtraBold.woff
        public/fonts/Inter-ExtraBold.woff2
        public/fonts/Inter-ExtraBoldItalic.woff
        public/fonts/Inter-ExtraBoldItalic.woff2
        public/fonts/Inter-ExtraLight.woff2
        public/fonts/Inter-ExtraLightItalic.woff2
        public/fonts/Inter-Italic.woff2
        public/fonts/Inter-Light.woff
        public/fonts/Inter-Light.woff2
        public/fonts/Inter-LightItalic.woff
        public/fonts/Inter-LightItalic.woff2
        public/fonts/Inter-Medium.woff2
        public/fonts/Inter-MediumItalic.woff
        public/fonts/Inter-Regular.woff
        public/fonts/Inter-Regular.woff2
        public/fonts/Inter-SemiBold.woff2
        public/fonts/Inter-SemiBoldItalic.woff
        public/fonts/Inter-ThinItalic.woff
        public/fonts/Inter-ThinItalic.woff2
        public/fonts/Inter-italic.var.woff2
        public/fonts/Inter-roman.var.woff2
        public/fonts/Inter.var.woff2
        public/logo_144x144.png
Please commit your changes or stash them before you merge.
Aborting

I tried to git restore <file> to no avail. Also tried to git stash and this is the output I get:
git stash
warning: in the working copy of 'public/fonts/Inter-Black.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Black.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-BlackItalic.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-BlackItalic.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Bold.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Bold.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-BoldItalic.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ExtraBold.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ExtraBold.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ExtraBoldItalic.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ExtraBoldItalic.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ExtraLight.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ExtraLightItalic.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Italic.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Light.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Light.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-LightItalic.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-LightItalic.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Medium.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-MediumItalic.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Regular.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-Regular.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-SemiBold.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-SemiBoldItalic.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ThinItalic.woff', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-ThinItalic.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-italic.var.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter-roman.var.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/fonts/Inter.var.woff2', CRLF will be replaced by LF the next time Git touches it
warning: in the working copy of 'public/logo_144x144.png', CRLF will be replaced by LF the next time Git touches it
Saved working directory and index state WIP on master: cd3a1cc improve chances of successfully gather a response

On the next pull it still tells me the same thing.
Please commit your changes or stash them before you merge. Aborting
Please advice. Thanks

You can replicate by:
git clone --branch v2.7.1 https://github.com/fr0tt/benotes.git

Then go on with the installation and finally:
git checkout master

Same issue

I changed the line endings of the binary files to align with the rest of the files (that's the "CRLF will be replaced by LF").
Git isn't exactly helpful with auto resolving binary files.
I'm sorry for the inconvenience. I tried a couple of ways to make it smoother but they all failed and I have to change it eventually anyways.
The fix is however rather simple:
rm -R public/fonts && rm public/logo_144x144.png
This removes all conflicting files and simply fetches the newest version of them from GitHub.

Nice, solved.


Length Metrics disappeared

previously

now (after upgrade to OpenLens: 6.5.2)

fixed by adding
@shilazi/openlens-lens-metrics


Removed the requirement that the buttons are actually buttons, they c…

…an now be just views

LGTM on success!


feat: File for settings (like an Ionic.json)

Type: feat
Platform: all
We have many options now to set with $ionicConfigProvider:
http://ionicframework.com/docs/nightly/api/provider/%24ionicConfigProvider/
I thought it would be cool to have this configurations in a specific file and this file be loaded by default..
Like an "IonicConfig.json" or something inside some specific folder or just inside www/ folder.
This json could have an syntax like:
{    views.transition: {      ios: "ios",      android: "none"    },   views.maxCache: {     ios: 30,     android: 20   } }
or something better and organized.

Thanks, I've added it to our feature request Trello board. If it gets enough votes, we'll consider it for the 1.1


Unknown database 'lobsters_development'

After running docker-compose up I get a NoDatabaseError. Both the MariaDB and Lobster's machines are running in the expected ports.
rescue Mysql2::Error => error
  if error.error_number == ER_BAD_DB_ERROR
    raise ActiveRecord::NoDatabaseError
  else
    raise
  end

looks like there were missing bundle exec statements in the docker-entrypointsh file. should be fixed now

looks like there were missing bundle exec statements in the docker-entrypointsh file. should be fixed now


Add FiScript

Project URL
https://github.com/Mortennn/FiScript
Category
Finder
Description
Added FiScript which lets you execute custom scripts from the MacOS context menu (CTRL+click) in Finder.
Why it should be included to Awesome macOS open source applications  (optional)
It is an unique application which i think people will enjoy.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in alphabetical order
[x] Appropriate language icon(s) added if applicable
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

@Mortennn Nice App! Thanks for your contribution! 👍


Maven repository example does not work

Documentation feedback

Page title: Getting started
Page URL: https://crate.io/docs/jdbc/en/latest/getting-started.html
Source: https://github.com/crate/crate-jdbc/blob/master/docs/getting-started.rst

When using this Getting started guide to setup a Maven Project with CrateDB I got an error that some libraries could not be found (JsonProcessingException). The reason is that the repository in the example ha the ID central and is therefor overwriting the default maven repositories called central. Changing the name to e.g. crate would make using the current example a valid option. But I'm not usually a Java/Maven dev and don't know what the usual approach would be. But I think having an example code in the documentation should work without letting the user figure some problems out themselves.

thanks for reporting this, @kamejosh! I have asked one of our core engineers to review your suggestion and will happily fix once I hear back

update: @kovrus gives this a thumbs up! :)

this was fixed but never closed


cluster: New() made async

We have New() blocking because we need to handle the error previously.
Now we will report failed status if error happens.
Meanwhile, cluster shouldn’t block or interfere each, which we have
seen in some issues. This is gonna fix #607, #588.

fixed

lgtm


Re-organizing some of the optimizer code

No actual code changes here. Just thought I would clean it up since I'm getting my hands dirty in the optimizer and the organization is getting confusing

closing. This merged in Master.


(URGENT) Parse failure: Unable to parse "NIST Monograph 125" and "NIST Monograph 125, Supp. 1"

The same goes for when the series name is not an abbreviation.
$ bundle exec nist-pubid convert "NIST Monograph 125"
Calling `DidYouMean::SPELL_CHECKERS.merge!(error_name => spell_checker)' has been deprecated. Please call `DidYouMean.correct_error(error_name, spell_checker)' instead.
bundler: failed to load command: nist-pubid (/Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/bin/nist-pubid)
/Users/me/src/mn/nist-pubid/lib/nist_pubid/document.rb:144:in `parse': failed to parse serie for NIST Monograph 125 (NistPubid::Errors::ParseError)
	from /Users/me/src/mn/nist-pubid/exe/nist-pubid:44:in `convert'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/gems/thor-1.0.1/lib/thor/base.rb:485:in `start'
	from /Users/me/src/mn/nist-pubid/exe/nist-pubid:52:in `<top (required)>'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/bin/nist-pubid:25:in `load'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/bin/nist-pubid:25:in `<top (required)>'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/cli/exec.rb:58:in `load'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/cli/exec.rb:58:in `kernel_load'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/cli/exec.rb:23:in `run'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/cli.rb:484:in `exec'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/cli.rb:31:in `dispatch'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/cli.rb:25:in `start'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/gems/bundler-2.3.3/libexec/bundle:48:in `block in <top (required)>'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/3.1.0/bundler/friendly_errors.rb:103:in `with_friendly_errors'
	from /Users/me/.rbenv/versions/3.1.0/lib/ruby/gems/3.1.0/gems/bundler-2.3.3/libexec/bundle:36:in `<top (required)>'
	from /Users/me/.rbenv/versions/3.1.0/bin/bundle:25:in `load'
	from /Users/me/.rbenv/versions/3.1.0/bin/bundle:25:in `<main>'

Should we parse long document identifiers?
example:
$ bundle exec nist-pubid convert "National Institute of Standards and Technology Special Publication 800-53, Revision 5"
or only long series part?
example:
$ bundle exec nist-pubid convert "NIST Special Publication 800-53r5"

@mico yes that would be great, we wish to parse all 4 styles of document identifiers (legacy ID to PubID)

So we want to parse both:
"NIST Monograph 125" and "National Institute of Standards and Technology Monograph 125", right?

Yes.

Now fully implemented abbreviated and long PubID for publisher, series, edition, revision and update.
Still need to implement:

part
version
addendum
section
appendix
errata
index
insert
supplement
stage
translation

Could be quite a big task, so maybe postpone this for later. Could we do this together with refactoring?

Could be quite a big task, so maybe postpone this for later. Could we do this together with refactoring?

Good idea. Once we have the refactoring done, we can easily implement other PubID schemes.


Allow search in glue webview

Issue #, if available:
#19
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

lgtm, will push with the v0.6.0 release


Update default conversion options instead of overwriting for run conversion

Motivation
Right now, when we run a conversion (with NwbConverter class) and we pass some conversion_options this overrides all of them:
https://github.com/catalystneuro/nwb-conversion-tools/blob/673410a79402b31a919e0e13e2bf7ed84732d15c/src/nwb_conversion_tools/nwbconverter.py#L149-L150
The current PR solves this by using dict_deep_update so the defaults conversion options defined at the interface level are respected at run time.
This PR is a follow up of #465 where we are using the get_conversion_options to hard code how and where the recording extractor data should be written.
Currently, we only define get_conversion_options for spikeglx and in our TutorialRecordingExtractor but if we want to use this option further we will need something like this.

Interestingly, we do have several test functions out there that use conversion_options, but I suppose they are all single-interface unit tests whereas this behavior would require a 2+ interface integration test, right?

@h-mayorquin Also can you look into if https://github.com/catalystneuro/nwb-conversion-tools/blob/main/src/nwb_conversion_tools/nwbconverter.py#L95-L100 and https://github.com/catalystneuro/nwb-conversion-tools/blob/main/src/nwb_conversion_tools/basedatainterface.py#L38-L40 are even needed at all? Seems like a round-about way of double-specifying default kwargs for all run_conversion functions.
Ideally the conversion_options dict would just be the minimal subset of override commands, though maybe it needs to load the rest of the options for the schema validation step?

Interestingly, we do have several test functions out there that use conversion_options, but I suppose they are all single-interface unit tests whereas this behavior would require a 2+ interface integration test, right?

I think the core of why this has been flying under the radar is because no interface relies on the get_conversion_options for anything that we are testing.
That said, you are also right about the two interfaces in the specific instance where this bug surfaced. Due to the new changes in spikeglx data interface (#465) the two of them crash when their get_conversion_options are overwritten at run time. This is because when force into default behavior both of them try to write to acquisition with the same name and the program fails.

That said, you are also right about the two interfaces in the specific instance where this bug surfaced. Due to the new changes in spikeglx data interface (https://github.com/catalystneuro/nwb-conversion-tools/pull/465) the two of them crash when their get_conversion_options are overwritten at run time. This is because when force into default behavior both of them try to write to acquisition with the same name and the program fails.

Nice catch, be sure to assign unique names by default for that interface, then.
Also I'd add it to your new To-Do list on https://github.com/orgs/catalystneuro/projects/3/views/1 to add a battery of tests for conversion_options support.

@h-mayorquin Also can you look into if https://github.com/catalystneuro/nwb-conversion-tools/blob/main/src/nwb_conversion_tools/nwbconverter.py#L95-L100 and https://github.com/catalystneuro/nwb-conversion-tools/blob/main/src/nwb_conversion_tools/basedatainterface.py#L38-L40 are even needed at all? Seems like a round-about way of double-specifying default kwargs for all run_conversion functions.
Ideally the conversion_options dict would just be the minimal subset of override commands, though maybe it needs to load the rest of the options for the schema validation step?

In my view, the second definition in basedatainterface.py is important as it ensures that the method always exist for all interfaces and returns an empty dict as default.
The first method is just a convenience for gathering all the conversion options for each interface in a hierarchical dict. Maybe not needed I agree but I also don't think is too much code.
More importantly, I think that the both the metadata and the conversion options should be passed and validated in the initialization of the class. Also, we should make them both attributes of NWBConverter. Doing this will allow us to build tests for the validation of both the metadata and the conversion options without the need of calling run_conversion and give the latter function a more clear responsibility.


Converter IP Decimal field only allows one period

As reported by T. Jackson Leverette, III:
Using CIDR Caclulator v 1.19.
Tested on both Nexus 7 (2013) with Lollipop 5.0.2 and a Moto X (2013) with Kitkat 4.4.4.
In the Converter mode, I'm unable to enter an address in the IP Decimal field, as the app will only allow one dot (period). After one dot, the only input that will appear are numbers.
However: when I use the IP Binary or IP Hex conversion, the result appears in the IP Decimal field correctly (with three decimals), but if the field is cleared a normal dotted-quad IP Decimal cannot be entered (as noted above).
Even though the app provides its own keyboard, just to test if my keyboard was the problem, I switched my default keyboard (from Swiftkey, to Google) and the bug still occurs.

This was already fixed in 1f0672c62a58028f9cc33115853c063f8c90d64f
Should work on releasing 1.20.


Caps lock on warning display

In the login page, If the Capslock is on when the password is being entered, a warning is displayed about it.
Closing issues
closes #183

Issue fixed in PR #189


chore: release 2.5.1

:robot: I have created a release *beep* *boop*
2.5.1 (2019-08-21)
Bug Fixes

deps: update dependency yargs to v14 (f406898)
docs should not count as feature (#234) (5a2c7d7)

This PR was generated with Release Please.

Release is at https://github.com/googleapis/release-please/releases/tag/v2.5.1

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


Be compatible with --incompatible_load_proto_rules_from_bzl

Checklist

[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[x] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
This PR is required to flip --incompatible_load_proto_rules_from_bzl in a future release of Bazel.
It's purely build-related and not a feature or bug-fix, so I did not open an issue (https://github.com/bazelbuild/intellij/issues/1512 was automatically created to notify about the upcoming breaking change but was closed without comment). I did, however, reach out to @jin (https://bazelbuild.slack.com/archives/CHSV3RSR0/p1580932545028100) to ask whether such a change would be accepted.
Description of this change
This change adds load statements for proto_library to become
compatible with https://github.com/bazelbuild/bazel/issues/8922
Also, Protobuf is updated to v3.11.3 (which also has the necessary load
statements).

FYI @brendandouglas, this is the change I discussed with you about.

The import commit is here: https://github.com/bazelbuild/intellij/pull/1627.
I'm gonna close this one for now.


neon-project-create/delete: print project id to output

Print project_id to stdout from GitHub actions

Funny how we create ${project_id}, BUT DELETE ${PROJECT_ID} :)

They grow so fast! 🤣


Pie Charts with gradients

Would it be possible to handle gradients colors within Pie or Doughnut Charts ?
Something like that?

Hi @willdale! So I managed to get the result I wanted (by duplicating the code) !

Both the fill of the PieChart and the stroke of the DoughnutChart accept a Color or a Gradient.
I wanted to make a PR, but I have the following problems:

How to allow both Color and Gradient in the related datapoints? If I change public var colour: Color in PieChartDataPoint by public var colour: ShapeStyle, I get the error Protocol 'ShapeStyle' can only be used as a generic constraint because it has Self or associated type requirements.
The gradient may actually need the startAngle and amount of the data point itself, if we want to be able to use RadialGradient as in my example:

Here is an example of a modified version of PieChart.
PieSegmentShape(id: chartData.dataSets.dataPoints[data].id,
startAngle: chartData.dataSets.dataPoints[data].startAngle,
amount: chartData.dataSets.dataPoints[data].amount)
.fill(AngularGradient(
    gradient: Gradient(colors: [
        Color(DynamicColor(chartData.dataSets.dataPoints[data].colour).lighter(amount: 0.3)),
        Color(DynamicColor(chartData.dataSets.dataPoints[data].colour).darkened(amount: 0.1))
    ]),
    center: .center,
    startAngle: .radians(chartData.dataSets.dataPoints[data].startAngle),
    endAngle: .radians(chartData.dataSets.dataPoints[data].startAngle+chartData.dataSets.dataPoints[data].amount)
))

Could you help me with this? What would be the preferred way to handle this case?


update README to prepare for archiving

halfway toward resolving #268.
after this is approved/merged, someone with admin 🔑s will need to archive the repo to disable new issues/pull requests.

happy to revisit this anytime...


Add support for diufferent NTS settings

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Sorry about the shitload of commits. Tests are not my hobby

@Heidistein thanks for the PR. can you please rebase and squash the commits into one?

In order to combine your commits, from your working directory:
git rebase -i origin/master # Interactively rewrite history

This will bring your editor listing all commits in your branch.  Keep the first line unchanged, and replace pick with squash for all subsequent lines.  Save and quit, your editor will pop again and allow you to combine all the commit messages in a single one.
Then push your updated branch:
git push -f            # Send the changes (-f is required because we re-wrote history)

Aight. git went heywire on me. It's a burning pile right now. I'll close this and redo it from scratch.


Closes ##3780 High memory usage due to idma import

Fix related to bug: https://github.com/kennethreitz/requests/issues/3780
idma package will now be imported within the function

Thanks for this!
However, this patch does not meaningfully reduce the memory usage. Any use of Requests will encounter this branch immediately and unconditionally, meaning that in practice all that we have done is delay the loading of the module. I think we need a better solution than this one.

How about doing selective import of the needed objects?
Raised another PR: https://github.com/kennethreitz/requests/pull/3783
Thanks,
Moinuddin Q
Website: www.moinq.com http://www.moinq.com/
Blog: www.cloudhack.in http://www.cloudhack.in/
Phone: +91 8790 719 434
On Wed, Dec 21, 2016 at 7:11 PM, Cory Benfield<EMAIL_ADDRESS>wrote:

Closed #3782 https://github.com/kennethreitz/requests/pull/3782.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kennethreitz/requests/pull/3782#event-901602069, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AE_RIPmien3rnNTVgjj6Y4O2yNmqOqr9ks5rKSyVgaJpZM4LS6ge
.


Make GitOps E2E test more robust + minor cleanup

Make GitOps E2E test more robust by using a newer tag that got created after the major force push to master
Minor cleanup of dead code

/test all

@jeff-mccoy Here's the scoped down PR for just the E2E test changes. The other one will get smaller once master gets integrated including this change

I'm a little sad you didn't stay on the dark side 😂 but 👍.

Gotta set a good example for the younglings 😉


Incorrect Provider seen for clusters using Rancher CLI

Rancher Server Setup

Rancher version: rancher version v2.6.5-rc1

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin

Describe the bug
Incorrect Provider seen for clusters using Rancher CLI
To Reproduce

Deploy an RKE2 node driver cluster on a docker install rancher setup
Deploy a few RKE1 clusters also
Login through Rancher CLI
List clusters - RKE2 node driver cluster is seen as Imported and local cluster is seen as Unknown

Result
./rancher clusters ls

CURRENT   ID             STATE     NAME         PROVIDER                    NODES     CPU         RAM             PODS
          c-2m6sp        active    test-36455   Rancher Kubernetes Engine   6         0.33/9.50   0.34/43.39 GB   12/440
          c-b6b7s        active    test-new     Rancher Kubernetes Engine   2         0.82/8      0.34/15.38 GB   15/220
*         c-m-wcpk7gct   active    sowmya-new   Imported                    1         1.22/2      0.23/3.84 GB    18/110
          c-vkggz        active    test-15523   Rancher Kubernetes Engine   6         0.33/9.50   0.34/43.39 GB   11/440
          local          active    local        Unknown                     1         0.10/4      0.07/7.77 GB    8/110

Expected:
RKE2 node driver cluster should be Rancher Kubernetes Engine 2 and local cluster should be Imported

The management cluster object for RKE2 provisioned clusters is an imported cluster. So, in this case, the client would have to detect that the imported cluster is an RKE2 provisioned cluster and change the output based on that.

the fix can be validated in Rancher CLI v2.6.5-rc1 https://github.com/rancher/cli/releases/tag/v2.6.6-rc1

Verified on Rancher CLI v2.6.6-rc1.
ENVIRONMENT DETAILS

Rancher HA: v2.6.5-rc12
Rancher CLI

Reproduced version: v2.6.5
Verified version: v2.6.6-rc1
• Token

Browser: Chrome

TEST RESULT
PAASS
REPRODUCTION STEPS

Setup Rancher and navigate to the UI in a browser.
Created a user token for the default admin and keep note of it; will need it for later.
Created a standard user and login to Rancher as that user.
Created a user token for this standard user and keep note of it.
Navigated to Cluster Management and provisioned the following clusters: AKS, GKE, K3s, RKE, RKE2:

Navigated over to your client machine and make sure the Rancher CLI v2.6.5 is installed.
Run command rancher login -t <admin user token> https://<RANCHER SERVER URL>.
Run command rancher clusters ls:

# rancher cluster ls
CURRENT   ID             STATE     NAME       PROVIDER                    NODES     CPU         RAM                   PODS
*         c-6q479        active    mew-gke    Unknown                     3         1.28/5.79<PHONE_NUMBER>/16.46 GB   25/330
          c-ffjdl        active    mew-aks    Unknown                     3         1.25/5.70   0.96/13.36 GB         24/330
          c-m-gd7c4qh9   active    mew-k3s    Imported                    1         0.20/2      0.14/3.84 GB          8/110
          c-m-kmmcgnp8   active    mew-rke2   Imported                    1         1.22/2      0.23/3.84 GB          18/110
          c-mql7t        active    rketest    Rancher Kubernetes Engine   1         0.47/4      0.27/7.69 GB          10/110

VERIFICATION STEPS

Setup Rancher and navigate to the UI in a browser.
Created a user token for the default admin and keep note of it; will need it for later.
Created a standard user and login to Rancher as that user.
Created a user token for this standard user and keep note of it.
Navigated to Cluster Management and provisioned/imported the following clusters: AKS, EKS, GKE, K3s, RKE, RKE2:

Navigated over to your client machine and make sure the Rancher CLI v2.6.5 is installed.
Run command rancher login -t <admin user token> https://<RANCHER SERVER URL>.
Run command rancher clusters ls:

# rancher cluster ls
CURRENT   ID             STATE     NAME                     PROVIDER                     NODES     CPU          RAM                   PODS
          c-44cxx        waiting   mew-eks                  Elastic Kubernetes Service   0         0/0          0/0 GB                0/0
*         c-4rh5b        active    mew-aks                  Azure Kubernetes Service     1         0.94/1.90    1.50/4.45 GB          16/110
          c-m-blx8glsx   active    mew-rke2                 RKE2                         1         1.47/4       0.23/7.77 GB          13/110
          c-m-k5fsbf6x   active    mew-rke                  Imported                     1         0.47/4       0.27/7.67 GB          8/110
          c-m-rfsbqksn   active    mew-k3s                  K3S                          1         0.20/4       0.14/7.77 GB          7/110
          c-mgrwb        active    mew-gke                  Google Kubernetes Engine     3         1.28/23.73<PHONE_NUMBER>/83.22 GB   25/330
          c-xw787        active    mew-rancher-custom-rke   Rancher Kubernetes Engine    1         0.47/4       0.27/7.67 GB          10/110


Bugfix: missing import of sys

UDP.py was missing "sys" module, meaning components would fail in the exception handler of receive_packet() (line 162)

Thanks!


Update MD file on new branch 2017-11-22_21-29-33

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/content1.md
:white_check_mark:Succeeded

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


Ockam enroll should work without having to specify the node or Ockam Controller URL

Ockam enroll enrolls the identity of a node to the Ockam Orchestrator. It should work without having to specify the node as an argument or the Controller URL.
Current behavior
ockam enroll --auth0 $CONTROLLER -n blue
$CONTROLLER will be hard coded into the Ockam Command binary and the identity of the node will be a global known identity so both of those values can be derived and do not need to be specified by the user.
Desired behavior
ockam enroll --auth0

Shouldn't this be just ockam enroll. Currently, the default enrollment method is email, but AFAIR we wanted to switch the default to auth0.

done


Data: project addition by coderhersh

Add a new project to the list
Hi, there.
I want to add a project called pinax. It is a landing page made in angular and tailwind css.
Kindly, include it under GSSOC 23.
https://github.com/priyankarpal/ProjectsHut/assets/56130865/ef36df7f-1ffc-4db0-94f3-6cf7505f5c7c
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Completed. Thanks for your contributions 🎉 ❤


Updated eslintrc file and latest version of eslint installed

ESLint detected 75 issues on ae772399dc656c6d9307a5fbf7089ca20c360834
Visit https://sideci.com/gh/114989629/pull_requests/7 to review the issues.

ESLint detected 8 issues on 5b0ac2778b2260b4d26f99514a0e454d174d7e64
Visit https://sideci.com/gh/114989629/pull_requests/7 to review the issues.


Regression in complex_layout_scroll_perf_bad_ios__timeline_summary build time on 12/6/2023

The performance dashboard showed a regression in the complex_layout_scroll_perf_bad_ios__timeline_summary benchmark around 12/6/2023.
Build time metrics like average_frame_build_time_millis increased, along with total_ui_gc_time.
See https://flutter-flutter-perf.skia.org/e/?keys=X85d9845ae61164943ad8763287b1ec06&selected=commit%3D38291%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253DiPhone_11%252Cdevice_version%253Dnone%252Chost_type%253Dmac%252Csub_result%253Daverage_frame_build_time_millis%252Ctest%253Dcomplex_layout_scroll_perf_bad_ios__timeline_summary%252C&xbaroffset=38291
The increase does not happen consistently on every run, but there is a clear overall trend.
Tried bisecting, and I noticed a change in this benchmark's behavior starting with https://dart.googlesource.com/sdk/+/85cb56dd205fdc7ca7e8d4eb7c3511075fe1a417

Looking at the generated arm64 code, I can only see improvements - less closure and context object allocations, certain switch expressions are optimized out entirely (such as TooltipState._getDefaultTooltipHeight).
Maybe smaller number of object allocations caused slower heap growth, which increased total number of GCs and results in higher overall GC time and build time. /cc @rmacnak-google

Given that this was a fairly small regression in a single benchmark and we think the change is good overall, lets close this and move on.

This did result in more overall GC times:
https://flutter-flutter-perf.skia.org/e/?begin=1704653803&end=1704740203&queries=sub_result%3Dnew_gen_gc_count%26sub_result%3Dold_gen_gc_count%26sub_result%3Dtotal_ui_gc_time%26test%3Dcomplex_layout_scroll_perf_bad_ios__timeline_summary&selected=commit%3D38528%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253DiPhone_11%252Cdevice_version%253Dnone%252Chost_type%253Dmac%252Csub_result%253Dtotal_ui_gc_time%252Ctest%253Dcomplex_layout_scroll_perf_bad_ios__timeline_summary%252C&xbaroffset=38291


Typo

Under Project level groups, Contributor permissions content says tacking when I believe it should say tracking.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 68686c2b-c69a-d9e4-3e21-a46d231b649c
Version Independent ID: 049659da-1772-3166-f909-4feeb8a97730
Content: Permissions and groups reference - VSTS & TFS
Content Source: docs/organizations/security/permissions.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@corosh Thanks for letting us know, I'm fixing it now and it should be live soon.


Fix a tiny typo

Hi,
thank you for such implementation, I am looking forward to start using it in mine future projects!  This just corrects a simple typo I saw when I was reading through the README.
Take care
krusty

Thank you too for your interest in go-sse! I'll ship this fix together with other README changes I have on the pipeline.
Let me know if you use this library and how I can assist you in that case!


docs: sync changes from v1.1 branch

Signed-off-by: Zach Rhoads<EMAIL_ADDRESS>

@zr-msft the commit title is misleading. You are syncing the changes from openservicemesh/osm main right and not v1.1?


repeated serialization of vcard corrupts organization value

Repeated serialization of a card corrupts the organization value of a vcard as there appears to be a missing line in OrgBehavior.transformToNative
I would have expected
obj.value = splitFields(obj.value)

before
obj.isNative = True
return obj

The difference in results with the line added can be seen below:
BEFORE
one:
BEGIN:VCARD
VERSION:3.0
FN:Bar\, Foo
N:Bar;Foo;;;
ORG:Company X;Division Y;Business Unit Z
END:VCARD

two:
 BEGIN:VCARD
VERSION:3.0
FN:Bar\, Foo
N:Bar;Foo;;;
ORG:C;o;m;p;a;n;y; ;X;\;;D;i;v;i;s;i;o;n; ;Y;\;;B;u;s;i;n;e;s;s; ;U;n;i;t;
 ;Z
END:VCARD

three
BEGIN:VCARD
VERSION:3.0
FN:Bar\, Foo
N:Bar;Foo;;;
ORG:C;\;;o;\;;m;\;;p;\;;a;\;;n;\;;y;\;; ;\;;X;\;;\\;\;;\;;D;\;;i;\;;v;\;;i;
 \;;s;\;;i;\;;o;\;;n;\;; ;\;;Y;\;;\\;\;;\;;B;\;;u;\;;s;\;;i;\;;n;\;;e;\;;s;
 \;;s;\;; ;\;;U;\;;n;\;;i;\;;t;\;; ;\;;Z
END:VCARD

AFTER
one:
BEGIN:VCARD
VERSION:3.0
FN:Bar\, Foo
N:Bar;Foo;;;
ORG:Company X;Division Y;Business Unit Z
END:VCARD

two:
BEGIN:VCARD
VERSION:3.0
FN:Bar\, Foo
N:Bar;Foo;;;
ORG:Company X;Division Y;Business Unit Z
END:VCARD

three
BEGIN:VCARD
VERSION:3.0
FN:Bar\, Foo
N:Bar;Foo;;;
ORG:Company X;Division Y;Business Unit Z
END:VCARD

The fix is already in master (courtesy of #23); I was using 0.9.1


Option to disable progress bar

Fixes #4

Any updates? This pr seems fine and would be very useful

Any updates? This pr seems fine and would be very useful

I would like to know as well if this will be merged soon!

I would like to know as well if this will be merged soon!

Can we get this merged and a new version released please?


FillPath Performance Declines Linearly

What version of CUE are you using (cue version)?
0.3.2
Problem
FillPath performance starts really strong, at 27µs. However, as the number of increases, FillPath takes around 500ms at 1k entries. Sporadically throughout there are 1-2s FillPath calls also.
Video
https://i.rawko.de/jkuLe9l9
Reproduction
package main

import (
	"fmt"
	"os"
	"os/signal"
	"time"

	"cuelang.org/go/cue"
)

func main() {
	var cueRuntime cue.Runtime
	cueInstance, err := cueRuntime.Compile("", "")
	if err != nil {
		panic("No Cue Runtime")
	}
	cueValue := cueInstance.Value()

	c := make(chan os.Signal, 1)
	signal.Notify(c, os.Interrupt)

	go func() {
		for _ = range c {
			fmt.Println(cueValue)
			panic("Done")
		}
	}()

	i := 0
	for {
		start := time.Now()
		cueValue = cueValue.FillPath(cue.ParsePath(fmt.Sprintf("i_%d", i)), i)
		now := time.Now()
		elapsed := now.Sub(start)
		fmt.Printf("FillPath %d took %v\n", i, elapsed)
		i++
	}
}

Relevant #804 ?

FTR: this comment already exists in internal/core/adt/closed.go and is related to exactly this issue:
	// TODO(perf): more aggressively determine whether a struct is open or
	// closed: open structs do not have to be checked, yet they can particularly
	// be the ones with performance issues, for instanced as a result of
	// embedded for comprehensions.

It basically is quadratic slowdown, thought the constant is higher than I expected.

This issue has been migrated to https://github.com/cue-lang/cue/issues/899.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


fix for bug #10868: _backward_softsign activation is incorrect

problem was that softsign was computed using outputs instead of inputs
added inputs to list, and changed what gets passed into softsign calculation
added softsign test to test_activation function
code reviewed by anirudh
Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@nswamy @eric-haibin-lin this fixes #10868 . Please take a look.

Good first blood! @samskalicky


Add OSCALJsonEditor Component

Uses react-split to create a vertically split element into two panes. This only manifests in REST mode and starts off with 50/50 split for the two panes. The end user is then able to adjust the width of the pane up to a certain limit.

The left pane wraps the OSCALJsonEditor component which consists of a configured instance of the @monaco-editor component. The editor is does take up 100% of the vertical height of the HTML page, instead, it adapts to screen height and is positioned relative to the scrollport based on sticky positioning.
The right pane wraps the viewer, which based on the route is one of the specific OSCALLoader components.

TO DOs:

[x] Migrate static CSS to makeStyles used by MUI
[x] Use fetch to complete PUT request
[ ] Write tests
[x] Fix overflow issues with OSCAL components. MUI 4 has significant issues element overflows when generic spacing is used.

References

@monaco-editor/react
Monaco Editor
react-split
split.js
https://github.com/EasyDynamics/easygrc/issues/23

Seems like the content uses ~100% of the display width in non-REST mode now. Is that an intentional change?

Seems like the content uses ~100% of the display width in non-REST mode now. Is that an intentional change?

Intentional, based on the screenshot that @rgauss shared with us on the potential design of including an editor. If we change the display width between rest/non-rest mode, the layout changes pretty dramatically which leads to some cognitive load. Nonetheless, this has been factored by a very small change Change to XL. So if we decide to go smaller we can. 🤞, all other components are dynamically sized.

The dropdown for the document and the toggle for REST mode should be aligned (REST mode toggle is currently higher)

Worked this in already, the changes will be up soon.

The top bar goes away when scrolling -- do we want to keep it? maybe not?

I tried not to modify existing layout/style decisions. Prior to this PR, the header was not static, so no change there. However changing it to be static isn't that hard.

Save/Discard buttons require scrolling to see (on my monitor).

This was intentional, so that when you do scroll past a certain point (i.e. when the top nav and selector are past the scroll port), the editor (including the buttons) fills up the viewport vertical space. Eventually the OSCALLoaderForm will move to a left hand drawer which will pull the editor and the buttons up, and no scroll will be required. We can either reduce the height now, or it can be part of the update when we develop the left hand drawer. It's mostly a matter of testing with different Editor Vertical Height values

@kylelaker, have your concerns been addressed here?

@rgauss I think so for the most part. I had previously approved and I think then dismissed because others had raised concerns. I haven't been following the developments on this branch super closely but I have no objections to merging it.


Data-Binding using LiveData

in Basic Sample, ProductFragment.java
// Observe product data
model.getObservableProduct().observe(this, new Observer<ProductEntity>() {
    @Override
    public void onChanged(@Nullable ProductEntity productEntity) {
        model.setProduct(productEntity);
   }
});

We observe for a change in LiveData<ProductEntity> mObservableProduct. When a change is there we set ObservableField<ProductEntity> product so that the data-binding library updates the UI. It seems like too much work perhaps.
My understanding would be that since LiveData cares about the lifecycle owner and not the view, hence databinding doesn't support LiveData. Is that so? @yigit
If this is the right way of doing it, is there any better way of using Data-Binding with LiveData?

@BindingAdapter will solve your problem. In my case I need to update list on LiveData has changed. Here is how I achieve this by using databinding.
I created a BindingAdapter to update list.
public final class ListBindingAdapter{
    @BindingAdapter(value = "resource")
    public static void setResource(RecyclerView recyclerView, Resource resource){
        RecyclerView.Adapter adapter = recyclerView.getAdapter();
        if(adapter == null)
            return;

        if(resource == null || resource.data == null)
            return;

        if(adapter instanceof BaseAdapter){
            ((BaseAdapter)adapter).setData((List) resource.data);
        }
    }
}

Then I need to add list as variable to my xml.
<layout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto">

    <data>
        <variable
            name="resource"
            type="iammert.com.androidarchitecture.data.Resource"/>
    </data>

    <android.support.v7.widget.RecyclerView
        android:id="@+id/recyclerView"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        app:resource="@{resource}"/>

</layout>

Then, all I need to do is setResource on live data change.
movieListViewModel
                .getPopularMovies()
                .observe(this, listResource -> binding.setResource(listResource));

We are going to make data binding lifecycle aware but for that to happens, lifecycle needs to hit 1.0 stable api.

@iammert  ((BaseAdapter)adapter) how you cast RecyclerView adapter to BaseAdapter?

@iammert how do we test that part :)

@yigit as of 1.0.0 is out now, is it now possible to bind livedata?

@theanh0512 I created BaseAdapter abstract class which has setData(List data).

@yigit @JoseAlcerreca Hey! Thanks for stable version! It is already hit to the stable version. Do you have any update about making databinding lifecycle aware?

@yigit @JoseAlcerreca Hi! I think, its time to reopen this bug as the lifecycle has already hit 1.0 stable api.
Thoughts?

LiveData without data binding kinda makes little sense, because you have to set/listen your way through again or manually throw data between observables and LiveData and that increases amount of vode required to present data, not decreases. @yigit, it definitely needs revising - especially, that you already hit 1.0 stable. Please reopen.

Keen to see this happen also.

The above proposal is interesting and make sense  so I really want this thread to re-open.

It seems like it's possible now with new Canary build: https://androidstudio.googleblog.com/2017/12/android-studio-31-canary-6-is-now.html
"You can now use a LiveData object as an observable field in data binding expressions. The ViewDataBinding class now includes a new setLifecycle method that you need to use to use to observe LiveData objects."

note that it's working for two-way data binding also!