subcommands lack one-line description

Running rdfsx --help provides a list of subcommands, but they are not self-explanatory.
Ideally, next to each subcommand would be a one-line description introducing it, and when running rdfsx SUBCOMMAND --help at least that same introduction, but preferrably an additional elaboration in few paragraphs, would be at the top of the output, before listing arguments.
I have tried, with the help of the wiki pages, to construct the one-line descriptions (which also hints at where to expand with additional paragraphs):
Description: add initial descriptive sentence for each subcommand
Author: Jonas Smedegaard<EMAIL_ADDRESS>Forwarded: not-needed
Last-Update: 2024-07-14
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/rdfsx_cli/src/cli.rs
+++ b/rdfsx_cli/src/cli.rs
@@ -24,6 +24,7 @@

 #[derive(Subcommand, Debug)]
 pub enum Command {
+    /// Process a ShapeMap
     Shapemap {
         #[arg(short = 'm', long = "shapemap", value_name = "ShapeMap file name")]
         shapemap: PathBuf,
@@ -50,6 +51,7 @@
         output: Option<PathBuf>,
     },

+    /// Show info about a ShEx schema
     Schema {
         #[arg(short = 's', long = "schema", value_name = "Schema file name")]
         schema: PathBuf,
@@ -84,6 +86,7 @@
         output: Option<PathBuf>,
     },

+    /// Validate a specific node with a shape in ShEx
     Validate {
         #[arg(short = 's', long = "schema", value_name = "Schema file name")]
         schema: PathBuf,
@@ -146,6 +149,7 @@
         output: Option<PathBuf>,
     },

+    /// Process RDF data
     Data {
         #[arg(short = 'd', long = "data", value_name = "RDF data path")]
         data: PathBuf,
@@ -166,6 +170,7 @@
         output: Option<PathBuf>,
     },

+    /// Show information about a node in an RDF file or a SPARQL endpoint
     Node {
         #[arg(short = 'n', long = "node")]
         node: String,
@@ -206,6 +211,7 @@
         output: Option<PathBuf>,
     },

+    /// Show information about a SHACL shapes graph
     Shacl {
         #[arg(short = 's', long = "shapes", value_name = "Shapes file name")]
         shapes: PathBuf,
@@ -234,6 +240,7 @@
         output: Option<PathBuf>,
     },

+    /// Convert from DCTap to JSON
     #[command(name = "dctap")]
     DCTap {
         #[arg(short = 'd', long = "DCTap file", value_name = "DCTap file name")]
@@ -263,6 +270,7 @@
         output: Option<PathBuf>,
     },

+    /// Convert from DCTap or ShEx to SPARQL, ShEx, UML or HTML
     #[command(name = "convert")]
     Convert {
         #[arg(short = 'm', long = "input-mode", value_name = "Input mode")]

Please note the places saying "Processing" which is purely made up, and probably needs rewording.

Also, please note that the initial line is not a full sentence, so should not contain a trailing full stop (ideally it should also not have initial letter capitalized, but apparently that's how clap styles such one-liners itself, judging from the automatic "Print this message or the help of the given subcommand(s)".

Thank...I really appreciate those suggestions to improve usebility of the tool.
I added those description lines and published a latest version yesterday (0.1.2), could you check if they are what you expected so we could close this issue?

The proposed changes are maintained (and just now synced with v0.1.10) as a patch here.
I do not push code to Github as a political principle, but perhaps I can persuade you to try out the decentralized git exchange Radicle - it integrates seemlessly with git (at least on my Debian system) and should only involve you (or anyone permitted, after the initial push) changing your git push to git push && git push rad, and I am then more than happy to share my change proposals there, wheren you can accept them by doing git pull rad && git push

Tnanks a lot for the suggestion on the description of the commands, it makes a lot of sense for me.
About using radicle, I was looking at it and it seems nice. I started this discussion in case more people want to express their opinion. As I understand, it would require me to run:
rad init

in the root of the project and after that, try to keep the remote rad up-to-date, right?
I think you are only suggesting to keep rad as another remote, not to replace github by rad, is that also right? At this moment, I would prefer that option, I mean, to keep github and to add support for radicle so other contributors who don't want to use github, can also contribute...

Looks good to me. Thanks!


Annoying cryptography deprecation warning via paramiko, via smart_open

When using snakemake with cryptography >=43.0.0 one gets 2 deprecation warnings:
$ snakemake
Using workflow specific profile profiles/default for setting default command line arguments.
/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/paramiko/pkey.py:100: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from this module in 48.0.0.
  "cipher": algorithms.TripleDES,
/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/paramiko/transport.py:259: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from this module in 48.0.0.
  "class": algorithms.TripleDES,
...

See paramiko issue https://github.com/paramiko/paramiko/issues/2419
By adding an exception in the relevant paramiko file, I found out that the import happens through smart_open.
I wonder if it would be possible to add a (temporary) workaround for the deprecation warning until upstream (paramiko and/or smart_open have a fix).
Traceback (most recent call last):

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/cli.py", line 2022, in args_to_api
    dag_api = workflow_api.dag(
              ^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/api.py", line 328, in dag
    return DAGApi(
           ^^^^^^^

  File "<string>", line 6, in __init__

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/api.py", line 438, in __post_init__
    self.workflow_api._workflow.dag_settings = self.dag_settings
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/api.py", line 386, in _workflow
    workflow.include(

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/workflow.py", line 1368, in include
    snakefile = infer_source_file(snakefile, basedir)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/sourcecache.py", line 320, in infer_source_file
    if is_local_file(path_or_uri):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/common/__init__.py", line 122, in is_local_file
    return parse_uri(path_or_uri).scheme == "file"
           ^^^^^^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/snakemake/common/__init__.py", line 126, in parse_uri
    from smart_open import parse_uri

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/smart_open/__init__.py", line 34, in <module>
    from .smart_open_lib import open, parse_uri, smart_open, register_compressor  # noqa: E402
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/smart_open/smart_open_lib.py", line 35, in <module>
    from smart_open import doctools

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/smart_open/doctools.py", line 21, in <module>
    from . import transport

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/smart_open/transport.py", line 105, in <module>
    register_transport("smart_open.ssh")

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/smart_open/transport.py", line 49, in register_transport
    submodule = importlib.import_module(submodule)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/smart_open/ssh.py", line 37, in <module>
    import paramiko

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/paramiko/__init__.py", line 22, in <module>
    from paramiko.transport import (

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/paramiko/transport.py", line 93, in <module>
    from paramiko.dsskey import DSSKey

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/paramiko/dsskey.py", line 37, in <module>
    from paramiko.pkey import PKey

  File "/opt/homebrew/Caskroom/miniforge/base/envs/py11/lib/python3.11/site-packages/paramiko/pkey.py", line 23, in <module>
    raise Exception("import of paramiko")

Exception: import of paramiko

Shall we really silence deprecation warnings, or rather wait for the decency to be fixed? I understand the intention, but fear that this code change will hit Snakemake eventually. It might just be forgotten, that this change has been introduced and then something else will be deprecated and after a while vanish entirely, only to be noticed when the code breaks.


Please provide tracking-free version

With the latest version, you introduced Firebase Analytics. Some folks decided to use Zimbra as an alternative to being tracked by Google when using GMail – so it would be unfortunate to bring that tracking back.
Could you at least have a Firebase-free .apk attached to releases/? And by "free" I do not simply mean "disabled", but "removed" (i.e. "contains no Firebase code"). Thanks in advance!

Alrighty! I'm willing to do so. Can you please submit a PR that removes Firebase from the source code completely?

If I could, I'd done that instead of opening an issue :wink: Sorry, but I'm no Android dev.

Briefly went through your github profile - doesn't look like DAIICT is your alma mater - the university this app was originally made for.

Are you using this app for Zimbra's webmail service elsewhere? I'd love to list it down on the readme if that's the case.
or, do you have a tracker that looks at github repos and checks to see if anything Google, ie, Firebase in this case, is added to well-off open source repos. Asking because you seem to be linked to FDroid.

No, I'm not affiliated either with the map nor with DAIICT. But yes, I'm affiliated with F-Droid and also run my own F-Droid repo.

I'm not using Zimbra nor its web services (as for DAIICT: from the readme it didn't sound like your app is bound to that – but rather could be used with any Zimbra Email Service?)
I have a personal tracker (me, skimming manually for interesting open-source Android apps from time to time) – which is how I found your project. Checking the releases/ page I saw your announcement "Added firebase analytics".

Firebase is a show-stopper at F-Droid. And I personally would not want to use an app having that integrated – especially not if the app deals with sensitive content (like mails do from time to time). As I know others feel the same, I thought to bring it up. I'm a "privacy advocate", so I try to help the privacy-aware community :wink:

Thanks a lot! I'm already providing your app via my repo. Once the Firebase-free version was fetched, I'll remove the Tracking AntiFeature. Guess you'll want to keep GMS for cloud messages (which makes it not fitting on F-Droid's main repo, but is OK for mine). If you consider replacing that as well (to make your app fully FOSS) but still want those messages, there are ways to achieve this (e.g. Tutanota has implemented a FOSS alternative called SSE (Server Sent Events)).

Any news here ... ? Would love to give it a try


When scroll icon displayed, adding new message doesn't scroll screen to the bottom.

Describe the bug
When I have a lot of messages and scroll up, the scroll icon is appear. After that I add new message and send. In this moment my screen doesn't scroll to the bottom, it stay in the same place. On the other hand, if I scroll down till the scroll icon disappear, and add new message after that, than screen automatically scroll to the bottom (expected behaviour).
Steps to reproduce

Load a lot of messages.
Scroll up untill scroll icon is appear.
Add new message and send.
If the scroll icon not shown, all works fine.

Expected behavior
After adding a new message screen scroll down to this message automatically.
Device (please complete the following information)
MacBook Pro 15"

I cannot reproduce. Which version of the chat are you using?
Can you send a GIF of the issue so I can try to reproduce?

I cannot reproduce. Which version of the chat are you using?
Can you send a GIF of the issue so I can try to reproduce?

Version 0.7.8

I cannot reproduce. Which version of the chat are you using?
Can you send a GIF of the issue so I can try to reproduce?

Have you change the height of the textarea? Maybe it's breaking the scrolling behaviour.
If you did, could you revert it to default and see if it fixes the issue?

No, I haven't change the height of the textarea and didn't use :height prop.
But if I try to use this prop and pass any value, scrolling behaviour still incorrect.
Below you can see an example of my Chat component:

I still cannot reproduce. The textarea doesn't have the same height as on the demo, maybe you are overriding it in your css.
If not, could you please share your project or a minimal reproducible example so I can debug it?

Try to do it on the clear project. Just follow the next steps:

Use code snippet below.
yarn add vue-advanced-chat
yarn run watch

<template>
    <div>
        <chat-window
            :current-user-id="currentUserId"
            :rooms="rooms"
            :messages="messages"
            @send-message="sendMessage"
            @fetch-messages="fetchMessages"
        />
    </div>
</template>

<script>
import ChatWindow from 'vue-advanced-chat'
import 'vue-advanced-chat/dist/vue-advanced-chat.css'

export default {
    name: 'Chat',

    components: {
        ChatWindow
    },

    data() {
        return {
            messages: [],
            rooms: [
                {
                    roomId: 1,
                    roomName: 'Room 1',
                    avatar: 'https://upload.wikimedia.org/wikipedia/en/thumb/a/a1/NafSadh_Profile.jpg/768px-NafSadh_Profile.jpg',
                    index: 3,
                    users: [
                        {
                            _id: 1234,
                            username: 'John Doe',
                            avatar: 'https://upload.wikimedia.org/wikipedia/en/thumb/a/a1/NafSadh_Profile.jpg/768px-NafSadh_Profile.jpg',
                            status: {
                                state: 'online',
                                lastChanged: 'today, 14:30'
                            }
                        },
                        {
                            _id: 4321,
                            username: 'John Snow',
                            avatar: 'https://lh3.googleusercontent.com/-G1d4-a7d_TY/AAAAAAAAAAI/AAAAAAAAAAA/AAKWJJPez_wX5UCJztzEUeCxOd7HBK7-jA.CMID/s83-c/photo.jpg',
                            status: {
                                state: 'offline',
                                lastChanged: '14 July, 20:00'
                            }
                        }
                    ],
                    typingUsers: [ 4321 ]
                }
            ],
            currentUserId: 1234,
        }
    },

    methods: {
        fetchMessages() {
            setTimeout(() => {
                let messages = [];

                for (let i=0; i<30; i++) {
                    messages.push({
                        _id: i,
                        content: 'message 1',
                        senderId: 1234,
                        username: 'John Doe',
                        date: '13 November',
                        timestamp: '10:20',
                        system: false,
                        saved: false,
                        distributed: false,
                        seen: false,
                        disableActions: true,
                        disableReactions: true,
                    })
                }

                this.messages = messages;
            }, 2000);
        },
        sendMessage(message) {
            const m = {
                _id: this.messages.length,
                content: message.content,
                senderId: this.currentUserId,
                timestamp: new Date()
            }

            this.$set(this.messages, this.messages.length, m)
        },
    },
}
</script>

I can reproduce thanks. Will try to fix this ASAP

In the meantime, you can do:
this.messages = [...this.messages, m]

Instead of:
 this.$set(this.messages, this.messages.length, m)

Also, I'm curious about the height of your textarea.
When you get the time, could you send me a screenshot using this repo: https://github.com/antoine92190/vue-advanced-chat-sandbox

hope this help

Thanks. Which browser are you using?

Google Chrome
Version 88.0.4324.192 (Official Build) (x86_64)

Scroll behaviour is fixed in https://github.com/antoine92190/vue-advanced-chat/commit/70cfa0026744829865b7ab6cb65db8be7b47e45f

I've found the new issue. With the same code for fetch messages on the first page load, if the last message belongs to the current user, then already is fine. If the last message belongs to another user, then scroll works incorrectly. See screenshots below.


No module named emailprotectionslib.dmarc

When running
sudo ./spoofcheck.py example.com
Got error:
Traceback (most recent call last):
  File "./spoofcheck.py", line 7, in <module>
    import emailprotectionslib.dmarc as dmarclib
ImportError: No module named emailprotectionslib.dmarc

did
sudo pip3 -r requirements.txt
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2

Hi,
Sorry, the version of spoofcheck in this repository has been deprecated and removed. The current home for spoofcheck is https://github.com/bishopfox/spoofcheck.
Additionally, it is my understanding that pip3 installs the Python 3 version of libraries. This would not be compatible with the Python 2.7 version that you are running.


Don't show consumption plans when the user selects "App Service Plan"

"Y" is for consumption

Merging to get a build, but feel free to review tomorrow


pull request for e2e test at 01/09/2017 07:26:10

:white_check_mark: Validation status: passed
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.


docs: Remove storage bucket requirement in PREINSTALL for palm extensions

are we sure the extension will install and work if storage isn't enabled?


ISPN-5903 Spring split

Hey!
Please take a look at proposed solution for https://issues.jboss.org/browse/ISPN-5903
This PR is very similar to CDI split implemented a week ago: https://github.com/infinispan/infinispan/pull/3775
Thanks
Sebastian

@tristantarrant done

@tristantarrant done

Can you squash the commits please ?

Yeah sure, any further comments or squashing and are good to go?

Looks good

Pushed, thanks


docs: Create Administrator only feature macro.

Automated message from Dropbox CLA bot
@synicalsyntax, it looks like you've already signed the Dropbox CLA. Thanks!

Thanks for the review @timabbott ! I've fixed the changes you've requested :)

BTW the first lines of the commit messages are too long.
Check out the Zulip commit message guidelines for more details: https://zulip.readthedocs.io/en/latest/version-control.html#commit-messages
I think the non-macro changes are sufficiently simple that I'm happy with squashing a bunch of the macro commits; will do that and merge.

Squashed the "use macro" commits and merged, thanks @synicalsyntax!

This macro was definitely a good choice since we had so many copies of that text :).


HTTP API enhancement

Pivotal story
There will be a subsequent PR addressing corresponding changes in protocol

Modified wiki page HTTP Client API: get account balance for consistency

@e-user This might be of interest for you.

Force pushed changes to RELEASE-NOTES-0.14.0.md

Rebased on top of master and resolved conflict


os: prevent formatting from happening twice

Fixes https://github.com/coreos/docs/issues/843
cc: @wintamute

I attempted to rewrite this with the following cloud-config, just can't get the all-on-one-line syntax correct in the ExecStartPre. Any pointers @crawford? systemctl status output below.
The tricky part is I want to invert the exit codes, such that finding a fs exits 1, but no fs exits 0, so the unit will continue to run/format.
#cloud-config
coreos:
  units:
    - name: format-ephemeral.service
      command: start
      content: |
        [Unit]
        Description=Formats the ephemeral drive if the desired filesystem does not exist
        After=dev-xvdb.device
        Requires=dev-xvdb.device
        [Service]
        Type=oneshot
        RemainAfterExit=yes
        ExecStartPre=/bin/bash -c "case "$(/usr/bin/lsblk -no FSTYPE /dev/xvdb)" in ext4) exit 1;; *) exit 0;; esac"
        ExecStart=/usr/sbin/wipefs -f /dev/xvdb
        ExecStart=/usr/sbin/mkfs.ext4 -F /dev/xvdb
    - name: var-lib-docker.mount
      command: start
      content: |
        [Unit]
        Description=Mount ephemeral to /var/lib/docker
        Wants=format-ephemeral.service
        After=format-ephemeral.service
        [Mount]
        What=/dev/xvdb
        Where=/var/lib/docker
        Type=ext4
    - name: docker.service
      drop-ins:
        - name: 10-wait-docker.conf
          content: |
            [Unit]
            After=var-lib-docker.mount
            Requires=var-lib-docker.mount

al bash[812]: -no: -c: line 0: unexpected EOF while looking for matching `)'
al bash[812]: -no: -c: line 1: syntax error: unexpected end of file
al systemd[1]: format-ephemeral.service: Control process exited, code=exited status=1
al systemd[1]: Failed to start Formats the ephemeral drive if the desired filesystem does not exist.
al systemd[1]: format-ephemeral.service: Unit entered failed state.
al systemd[1]: format-ephemeral.service: Failed with result 'exit-code'.
al systemd[1]: Starting Formats the ephemeral drive if the desired filesystem does not exist...
al bash[816]: -no: -c: line 0: unexpected EOF while looking for matching `)'
al bash[816]: -no: -c: line 1: syntax error: unexpected end of file
al systemd[1]: format-ephemeral.service: Control process exited, code=exited status=1
al systemd[1]: Failed to start Formats the ephemeral drive if the desired filesystem does not exist.

You had some extra quotes in there.
/bin/bash -c "case $(lsblk -no FSTYPE /dev/xvdb) in ext4) exit 1;; *) exit 0;; esac"

Had a few more seconds to look into this.
Here's what I ended up with:
#cloud-config
coreos:
  units:
    - name: format-ephemeral.service
      command: start
      content: |
        [Unit]
        Description=Formats the ephemeral drive if the desired filesystem does not exist
        After=dev-xvdb.device
        Requires=dev-xvdb.device
        [Service]
        Type=oneshot
        RemainAfterExit=yes
        ExecStartPre=/bin/bash -c 'case "$(lsblk -no FSTYPE /dev/xvdb)" in ext4) exit 1;; *) exit 0;; esac'
        ExecStart=/usr/sbin/wipefs -f /dev/xvdb
        ExecStart=/usr/sbin/mkfs.ext4 -F /dev/xvdb
    - name: var-lib-docker.mount
      command: start
      content: |
        [Unit]
        Description=Mount ephemeral to /var/lib/docker
        Wants=format-ephemeral.service
        After=format-ephemeral.service
        [Mount]
        What=/dev/xvdb
        Where=/var/lib/docker
        Type=ext4
    - name: docker.service
      drop-ins:
        - name: 10-wait-docker.conf
          content: |
            [Unit]
            After=var-lib-docker.mount
            Requires=var-lib-docker.mount

It works well and doesn't double format, and the unit does fail. It's not ideal that you'll see this every time you login though...
l systemd[1]: Starting Formats the ephemeral drive if the desired filesystem does not exist...
l systemd[1]: format-ephemeral.service: Control process exited, code=exited status=1
l systemd[1]: Failed to start Formats the ephemeral drive if the desired filesystem does not exist.
l systemd[1]: format-ephemeral.service: Unit entered failed state.
l systemd[1]: format-ephemeral.service: Failed with result 'exit-code'.
l systemd[1]: Starting Formats the ephemeral drive if the desired filesystem does not exist...
l systemd[1]: format-ephemeral.service: Control process exited, code=exited status=1
l systemd[1]: Failed to start Formats the ephemeral drive if the desired filesystem does not exist.
l systemd[1]: format-ephemeral.service: Unit entered failed state.
l systemd[1]: format-ephemeral.service: Failed with result 'exit-code'.
l systemd[1]: Starting Formats the ephemeral drive if the desired filesystem does not exist...
l systemd[1]: format-ephemeral.service: Control process exited, code=exited status=1
l systemd[1]: Failed to start Formats the ephemeral drive if the desired filesystem does not exist.
l systemd[1]: format-ephemeral.service: Unit entered failed state.
l systemd[1]: format-ephemeral.service: Failed with result 'exit-code'.

@robszumski you could put everything in the ExecStart and then just no-op if it's already formatted. This is getting pretty gross.

@robszumski @crawford What's that status of this document?

The proper solution is to let Ignition format the filesystem instead. We can probably just yank this example entirely.


The search tool's width is real-time change, It's shake and customer can not sometimes input correct word.

VSCode Version: Code 1.3.1 (e6b4afa53e9c0f54edef1673de9001e9f0f547ae, 2016-07-12T13:35:06.227Z)
OS Version: Windows_NT ia32 6.1.7601

Steps to Reproduce:

Press hotkey "CTRL + F", Open search tool,
Search tool's width is: 411px
Screenshot:

Input 's',
Search tool's width is: 447px
Screehshot:

Input 'm',
Search tool's width is: 427px
Screenshot:

Delete 'm',
Search tool's width is: 447px
Screenshot:

Actual Result:
Search tool's width is real-time change, It's shake and customer can not sometimes input correct word.
Expect Result:
Search tool's width is fixed, customer can accurately locate char and input correct word

Hi guys, submitted a PR for this issue.
Fix increases the width of find widget for all locale.
Is that fine, do we have any other better approach?

Hi
Nagaraj,
Sorry,
I was busy with interview in Microsoft.SuZhou, yestoday.
About
this issue, I think your solution is fine, And I do not find a better solution
for it, now.
We
can change the issue state to ‘Resolved’ or ‘Close’, And I will continue focus
the issue in new build.
Best
Regards,
Jimmy.LiDate: Fri, 19 Aug 2016 11:43:47 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] The search tool's width is real-time change, It's shake and customer can not sometimes input correct word. (#10650)
Hi guys, submitted a PR for this issue.
Fix increases the width of find widget for all locale.
Is that fine, do we have any other better approach?
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

About this issue, I think your solution is fine,
And I do not find a better solution for it, now.
We can change the issue state to ‘Resolved’ or ‘Close’,
And I will continue focus the issue in new build.

It's the first time I use github.
Need I close the issue when we resolve it?

Hi @JimmyLonely,
Usually one of the admins/core_committers of vscode will review & test whether the fix is fine or not. Only when it passes the review criteria, they will merge my pull request into the master branch and resolve/close the issue.
As a reporter of the issue, you don't have to do anything :)


prune list of plugins

Description (cross posted from #325): pip install ModelBench also installs with all plugins by default, which is probably unnecessary


FreeType generated font misses some characters with certain parameters

Issue details
When using the font provided below and one of the affected sizes some characters are not rendered.
Reproduction steps/code

Generate new project with FreeType feature enabled
Replace the body of your generated ApplicationAdapter class (MyGdxGame by default) with this:

    private SpriteBatch batch;
    private BitmapFont font;

    @Override
    public void create() {
        batch = new SpriteBatch();

        FreeTypeFontGenerator fontGenerator =
                new FreeTypeFontGenerator(Gdx.files.internal("Carlito-Regular.ttf"));

        FreeTypeFontGenerator.FreeTypeFontParameter parameter =
                new FreeTypeFontGenerator.FreeTypeFontParameter();

        // Rendered text depending on font size:

        // 211:       "abcde" as expected
        // 212:       "something strange bcde"
        // 214 - 215: " b de"
        // 216 - 262: " b d "
        // 263:       " bcde"
        // 264 - 266: " b de"
        // 267 - 268: " b d "
        // 269:       "abcde" as expected

        parameter.size = 216;

        font = fontGenerator.generateFont(parameter);
    }

    @Override
    public void render() {
        Gdx.gl.glClearColor(0, 0, 0, 1);
        Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);

        batch.begin();
        font.draw(batch, "abcde", 5, 300);
        batch.end();
    }

    @Override
    public void dispose() {
        batch.dispose();
        font.dispose();
    }

Download Carlito font from https://fontlibrary.org/en/font/carlito and copy Carlito-Regular.ttf to your assets folder
Set parameter.size to one of the values from the comments above
Run and see a certain kind of unexpected render

Version of LibGDX and/or relevant dependencies
• LibGdx 1.9.8
• Windows and Android, other platforms not tested
• Carlito-Regular.ttf font, other fonts not tested.
Please select the affected platforms

[+] Android
[?] iOS (robovm)
[?] iOS (MOE)
[?] HTML/GWT
[+] Windows
[?] Linux
[?] MacOS

Does setting useIntegerPositions to false changes anything?
font.setUseIntegerPositions(false);

Does setting useIntegerPositions to false changes anything?
font.setUseIntegerPositions(false);

Thank you for suggestion.
Just checked, unfortunately it stays the same way.

You are rendering at a huge size. What do the font textures look like? What if you increase the PixmapPacker page size by setting parameter.packer?

You are rendering at a huge size. What do the font textures look like? What if you increase the PixmapPacker page size by setting parameter.packer?

That really worked. Thank you :)
My use case for such a font size is a diagram editor. It supports zooming and needs to render a smooth text. As far as I remember, this font problem also occurred on smaller text sizes. Instead of absence of characters, some quite unusual ones were generated.
Probably it would be helpful to add some notice about large font size and packer on this page:
https://github.com/libgdx/libgdx/wiki/Gdx-freetype
Currently the only mention of packers on that page is /** The optional PixmapPacker to use */ comment. And it doesn't tell when it's reasonable to set that parameter.

Found a much more simple solution:

FreeTypeFontGenerator.setMaxTextureSize(4096);

Then I guess it's even better to mention this method on https://github.com/libgdx/libgdx/wiki/Gdx-freetype

Cool, glad you got it sorted. Sorry it took so long to reply. I've updated the wiki. Feel free to make wiki contributions! I believe anyone can edit the wiki, that is what it is there for.
BTW, you might look at DistanceFieldFont:
https://github.com/libgdx/libgdx/wiki/Distance-field-fonts
That wiki page looks outdated though, since it doesn't even mention that you should use the shader created by DistanceFieldFont.createDistanceFieldShader.


stop caching ring-finding results

Currently the ring-finding code caches its results, which leads to delightful confusion like this:
In [5]: m = Chem.MolFromSmiles('C1C2CC1CCC2')

In [6]: m.GetRingInfo().NumRings()
Out[6]: 3

In [7]: Chem.GetSSSR(m)
Out[7]: <rdkit.rdBase._vectclass std::vector<int,class std::allocator<int> > at 0x20583b62fc0>

In [8]: m.GetRingInfo().NumRings()
Out[8]: 3

In [9]: m = Chem.MolFromSmiles('C1C2CC1CCC2',sanitize=False)

In [10]: m.UpdatePropertyCache()

In [11]: Chem.GetSSSR(m)
Out[11]: <rdkit.rdBase._vectclass std::vector<int,class std::allocator<int> > at 0x20583ca1840>

In [12]: m.GetRingInfo().NumRings()
Out[12]: 2

That mess is by design, but it seems like a bug.
This removes the caching so that things are a bit less surprising.
We could add something to be more specific about what we cache, but there's really no reason for people to be calling the ring finding code multiple times on the same molecule, so this seems like wasted effort to me.
Thanks to @fwaibl for pointing out the problem

We should probably search for findSSSR in the code (or fastFindRings) and move the isInitialized to the caller.
Example:  Wrap/MolOps.cpp line 309
VECT_INT_VECT getSSSR(ROMol &mol) {
  VECT_INT_VECT rings;
  MolOps::findSSSR(mol, rings);
  return rings;
}

will always call the ring finding code now regardless of whether it exists or not.

I think there are only a few of these.
Mol2FileParser
ReactionWriter
are two that I've found in a brief search.

ExtendedMurckoScaffold always calls fastFindRings as well.

As does regioIsomer

I think you have everything except the Wrapper, Mol2FileParser and ReactionWriter

We should probably search for findSSSR in the code (or fastFindRings) and move the isInitialized to the caller.
Example: Wrap/MolOps.cpp line 309
VECT_INT_VECT getSSSR(ROMol &mol) {
  VECT_INT_VECT rings;
  MolOps::findSSSR(mol, rings);
  return rings;
}

will always call the ring finding code now regardless of whether it exists or not.

Correct - that's exactly what this bug fix is doing: when the user/client calls the ring finding code, it will always be run

I think you have everything except the Wrapper, Mol2FileParser and ReactionWriter

The Wrapper doesn't need a change (see my earlier comment). In the Mol2FileParser the work is being done during molecule construction, so we know we don't need to do the test. I've updated the ReactionWriter

Yep, the Wrapper was a brain fart.

LGTM

Nice, I think this will help with a lot of confusion.

Now, if we delete a ring bond or atom, do we or should we invalidate the ring info?

Now, if we delete a ring bond or atom, do we or should we invalidate the ring info?

We do: https://github.com/rdkit/rdkit/blob/master/Code/GraphMol/RWMol.cpp#L315


Fixed back-to-back span merging when adding new span (Resolves #598)

Fixed back-to-back span merging when adding new span (Resolves #598)
This PR should be rebased after #599 merges.

I can test this once https://github.com/superlistapp/super_editor/pull/599 lands.

@knopp I rebased against main so the PR should now be up to date.


Error trying to format ngClass attribute with optional chaining followed by property access via variable

What version of prettier-plugin-tailwindcss are you using?
For example: v0.1.13
What version of Tailwind CSS are you using?
For example: v3.1.8
What version of Node.js are you using?
For example: v16.16.0
What package manager are you using?
yarn 2 (pnp disabled)
What operating system are you using?
Windows 11
Reproduction URL
https://github.com/TomTomB/tailwind-ng-prettier-issue
Describe your issue
The repo is a bare nrwl nx setup.
After clone, the following commands needs to get executed:

npm i
npm run prettier .\apps\issue-app\src\app\app.component.html

This will result in the following error.
apps\issue-app\src\app\app.component.html[error] apps\issue-app\src\app\app.component.html: Error: Unexpected node undefined

Hey thanks for the report — this was a confusing bug for sure. I've come up with a fixed and merged it in. We're likely gonna do some extra bits of work before we tag our next release though. I'm hoping by the end of this week if we can swing it but not 100% certain.

Any chance you can cut a release to include the fixes from #93 ? We're being bitten by this exact issue :(


Neuvector images built for Apple aarm64

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
linux/arm64 images would allow local development / testing of Neuvector on Apple Mac M1 line of laptops and servers (i.e. Studio offers plenty of capacity)
Describe the solution you'd like
A clear and concise description of what you want to happen.
Publish an image for arm64 to Docker Hub or expose build system so others can build locally
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I have put in a support ticket for our commercial license and this is being considered by Product Team. Opens-sourcing of build tools might allow this happen faster.
Additional context
Add any other context or screenshots about the feature request here.
Not expecting this to be a production support configuration but local K8s development (KinD on Podman) offers reasonable local configuration for setup and testing.

ARM CPU is not supported yet. We will add it to the roadmap based on the customer requests.


Reorganize web-sys items into modules?

Should items in web-sys crate be reorganized into modules like this:
pub mod html_elements {
    pub use HTMLAnchorElement;
    pub use HTMLAreaElement;
    ....
}
pub mod element_events {
    pub use MouseEvent;
    pub use InputEvent;
    ....
}

Most of them can be classified automatically, for example, in HTMLDivElement.webidl:
[HTMLConstructor]
interface HTMLDivElement : HTMLElement {};

then, HTMLDivElement will be grouped into Rust's module html_elements?

I think that the idea is that web_sys is like libc, in that it just exposes everything with minimal overhead. That means that abstractions can be tested as crates. If this crate chose a particular abstraction it would become the de-facto standard and would stifle any innovation.
I'm not a decision maker though so I may be wrong.

I'm personally also a fan of dumping it all into one namespace. That's the way it is on the web and as the *-sys bindings to the web it makes sense to me to mirror that! I'll mark this as blocking the web-sys release though.

I agree with @derekdreery and @alexcrichton that we should keep the existing, flat namespace.
It seems we have rough consensus, so I'm going to go ahead and close this issue. Thanks for bringing up the idea, @limira!

@limira another reason for not doing it is that it would make the parsing/ast code more complicated - and it's already very complicated IMO! :P

@derekdreery  Thanks for trying to... er... explain (I do not know what is the right word here!). And don't worry, I know it's very complicated, I personally just understand a little on the surface of the whole wasm-bindgen project!


Question about pypi/matplotlib-inline pointing to a fork of this project.

Hello,
I was taking a look at https://pypi.org/project/matplotlib-inline/ .
Is there any reason why as a source/homepage it points to a fork of @martinRenou instead of this repo? Isn't this the "official" repo? As of my understanding, Martin currently works for your organization so it is possible there was a mistake when publishing to Pypi?
To me it feels strange to have the official package source to be here (ipython/matplotlib-inline) but deployed/owned by Martin on Pypi (via martinRenou/matplotlib-inline, which clearly is shown by GitHub as a fork) .
Thanks for the clarification,
Cristian

Hello,
Thanks for reporting. This is indeed unintended, the matplotlib-inline repo started under my account and was moved there. There was a fix of the url https://github.com/ipython/matplotlib-inline/pull/3 but this was never released and published to PyPi.
We should fix that.

This should be fixed now. Thanks :)

Perfect! Thanks for the quick turnaround


use proxies instead of model extensions

problems:
direct access to targetmodels circumvent proxies (see openapi-builder)
const targetModel = model.associations[associationName].target;


fix attribute handler bugs, re-deploy contracts, simplify makefile

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Provide IPv6 mask for IPv6 virtual servers.

The VIP netmask was always given as <IP_ADDRESS> which caused errors
when placing a Neutron LB on an IPv6 subnet. This passes the proper /128
mask for IPv6 virtual server IP addresses.
@richbrowne
What issues does this address?
Fixes #1294
...
What's this change do?
This change causes the agent to pass "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff" as the netmask for IPv6 VIPs rather than the previous value of <IP_ADDRESS>. I did not do testing with IPv6 pool members.
Where should the reviewer start?
service_adapter.py
Any background context?
This resolves a failure to provision a Neutron LB on an IPv6 subnet. In the test scenario, the LB is placed on a shared IPv6 subnet while the backends are on an IPv4 tenant network.

Can somebody re-run the CI for this commit? I don't see any failures related to the changed code.

Bump.

Closing this PR as it is 3 years old now


Default grouping blocks the Group title override

Describe the bug
When forcing default grouping by using defaultGroupOrder in the column definition, the method for overriding the Group title doesn't work.
To Reproduce
https://codesandbox.io/s/brave-flower-onz9d5?file=/src/App.tsx
Expected behavior
The override method to work when either using the drag and drop columns or by default in the column definition.
Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 6.1.1

Well... it looks like it's working in CodeSandbox now...

yes, my fault.  I was on 6.0.2, and it looks to be fixed in the newest.


Hero: Improve pattern quality

By specifying 'full background image' for a hero, one can request a loss-less rendition.
fix: 'full background image' will force the image to be rendered in loss-less quality (webpll)
Fix #321
Test URLs (hero will change its quality):

Before: https://main--hlx-test--urfuwo.hlx.live/draft/hupe/321-pattern-quality
After: https://321-hero-improve-pattern-quality--hlx-test--urfuwo.hlx.live/draft/hupe/321-pattern-quality

@karlpauls : Integrated your requested change


No module named '_pywrap_tensorflow' error even after installing Visual C++ and MSVCP140.dll.

I'm trying to run the simple speech recognition network example of Tensorflow:
python tensorflow/examples/speech_commands/train.py
But I keep getting:

Traceback (most recent call last):
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 18, in swig_import_helper
fp, pathname, description = imp.find_module('_pywrap_tensorflow', [dirname(file)])
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\imp.py", line 296, in find_module
raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_pywrap_tensorflow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python_init_.py", line 66, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 28, in
_pywrap_tensorflow = swig_import_helper()
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 20, in swig_import_helper
import _pywrap_tensorflow
ModuleNotFoundError: No module named '_pywrap_tensorflow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "tensorflow/examples/speech_commands/train.py", line 79, in
import tensorflow as tf
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow_init_.py", line 24, in
from tensorflow.python import *
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python_init_.py", line 72, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 18, in swig_import_helper
fp, pathname, description = imp.find_module('_pywrap_tensorflow', [dirname(file)])
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\imp.py", line 296, in find_module
raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_pywrap_tensorflow'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python_init_.py", line 66, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 28, in
_pywrap_tensorflow = swig_import_helper()
File "C:\Users\DELL 7000\AppData\Local\Programs\Python\Python37-32\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 20, in swig_import_helper
import _pywrap_tensorflow
ModuleNotFoundError: No module named '_pywrap_tensorflow'

Failed to load the native TensorFlow runtime.

See https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/get_started/os_setup.md#import_error

for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

Most of the solutions I found told me to reinstall visual c++ or to manually add MSVCP140.dll to the path. But neither of these solve my problem.
The github page it tells me to refer returns a 404.
I'm on python 3.7.2 and tensorflow 1.0.0.
Kindly help if possible.

@SharawatChirag Does your CPU support AVX instruction set? Thanks!


reusable vs. reuseable

The sync connection manager spells "make-reusable" differently than the async version:
make-reusable-conn-manager
make-reuseable-async-conn-manager
This is a minor annoyance, but "gotcha'd" me when switching between them, for testing purposes.
If this is worth addressing, perhaps a wrapping function make-reusable-async-conn-manager?
Thank you for this terrific library, and thanks for your consideration!

Whoops that's a really good catch, I totally missed that I named them incorrectly.
I think a wrapping function would be useful, would you be interested in opening a PR for it?


fix: Removed net6.0-windows10.0.17763.0 target from Uno.WinUI project.

net6.0 is prioritized over .Net Standard, because of this, .Net Standard Uno projects do not work

What kind of change does this PR introduce?

Bug fix
What is the current behavior?

What is the new behavior?

What might this PR break?
Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

Try the net6.0-windows10.0.19041 please on your targets where you have net6.0-windows before opening issues. I managed to get your project working with it.


Use syntax redirection in place of ERRORLEVEL

This should solve https://github.com/bmrf/tron/issues/61

I made these changes knowing how the relation between ERRORLEVEL and redirection work, but I have not tested this code. I have multiple other projects where I have done the same thing with no issues.

Another point of discussion is that using syntax redirection might make the code look less human readable in some cases. Personally I don't think ERRORLEVEL is very human readable either, but that's probably just me.

I'll leave things the way they are in the majority of the code, but I'm OK with slowly moving things to the syntax redirection method over time.

No worries, this one was more of a personal vendetta because I just don't trust ERRORLEVEL :smile:

@nemchik it's like the friend that's reliable 80% of the time. Just enough unreliability to cause you concern


Use Cases that only run a single wrapper

Most use case examples in the parm/use_cases area run multiple wrappers in PROCESS_LIST. This is good, but some wrappers don't have a clear example that uses ONLY that wrapper. For example, the mode use case parm/use_cases/mode/examples/hrefmean-vs-mrm-qpe.conf runs PcpCombine first, so that use case file has a lot of confs specific to pcp_combine in addition to the mode confs.
I think we should create a parm/use_cases/wrappers directory that has subdirectories for each wrapper we have implemented. Each subdir will contain a conf file to run each way to run that wrapper only, i.e. pcp_combine will have examples to run all of the modes - add, sum, subtract, derive. This will give users an example of all of the configurations needed to add a specific wrapped MET tool.

Here is a list of wrappers that I don't think have a use case that runs only that wrapper:
CyclonePlotter
EnsembleStat
ExtractTiles
MakePlots
MODE
MTD
PB2NC
PointStat
RegridDataPlane
SeriesByInit
SeriesByLead
StatAnalysis (?)
TcPairs
TcStat
TCMPRPlotter

I can create use cases that only run the following wrappers. If you are familiar with any others, please volunteer to create a use case that only runs and uses configuration variables needed for that use case.
MODE
MTD
RegridDataPlane
PB2NC
PointStat

Mallory has StatAnalysis - save GridStat use case output to use as input for StatAnalysis
Jim will do EnsembleStat and TcPairs - if time create SeriesAnalysis use case based on MET unit tests
Minna will do CyclonePlotter and TCMPRPlotter
Hank will do TcStats
Don't need ExtractTiles or MakePlots

These use cases should be put under parm/use_cases/met_tool_wrapper inside a subdirectory named after the tool. The need appropriate rst and py files for documentation. They also need a sym link for README.txt. See grid_stat directory for an example. These directories should likely be named with the wrapper notation GridStat instead of grid_stat.

See subtask #315 Single wrapper use cases for:
EnsembleStat,
TCPairs,
SeriesByInit,
SeriesByLead

In the meeting today we discussed trying to set up use cases that run one wrapper using data in met_test if possible. If there is insufficient data in there to run a case (for example the TC apps), then we should add new data to met_test so we can move towards making the MET tests more complete in regards to coverage.

Is this data in met_test included in the MET source code? I'm looking at the 8.1 install on Hera. There are various datasets in /contrib/met/8.1/met-8.1/data. There is also tutorial data on Hera in /contrib/met/tutorial_data, but there is no data for 8.1. Anyone know if either of these is the equivalent to met_test? Or if met_test exists on Hera? Maybe @JohnHalleyGotway @jprestop ?

I'm not sure if I fully understand what is meant by "met_test", but I think I do. The data used when running "make_test" for met is on hera at /contrib/met/8.1/met-8.1/data and /contrib/met/8.1/met-8.1/out.  You can see the tools that were tested in running "make_test" and the commands that were run for those tools in /contrib/met/8.1/met-8.1/make_test.log.  If that does not answer your question, please let me know.

@jprestop I think the data in this "met_test" directory is the data used in the nightly build and testing of MET?

I thought that at first too, but then I remembered the data that we discussed at the meeting was a small amount of data.
The data used in make_test is small:
[Julie.Prestopnik@hfe10 met-8.1]$ du -sh data
181M	data
[Julie.Prestopnik@hfe10 met-8.1]$ du -sh out
82M	out
But, the data used in the nightly build and testing of MET is large and is not on hera:
dakota:jpresto:~% du -sh /d3/projects/MET/MET_test_data/unit_test
49G	/d3/projects/MET/MET_test_data/unit_test
It is entirely possible that I am confused and misunderstanding something.

met_test is on eyewall under /d1/METplus_Data and in one of the sample data
tarballs attached to the METplus releases. It was taken from the data
directory in the MET build area that are used to run the
unit_met_test_scripts.xml unit tests. It may be a subset of the data in the
met-8.1/data directory. Here is what the directory listing looks like:
ls /d1/METplus_Data/met_test/*
/d1/METplus_Data/met_test/atcf_data:
aal052012.dat  aal092012.dat  aal182012.dat  bal092011.dat  bal182011.dat
aal092011.dat  aal182011.dat  bal052012.dat  bal092012.dat  bal182012.dat
/d1/METplus_Data/met_test/data:
colortables  copyright_notice.txt  Makefile.am  map   ps      sample_fcst
table_files  version.txt
config       Makefile              Makefile.in  poly  python  sample_obs
tc_data
/d1/METplus_Data/met_test/out:
ascii2nc       gen_vx_mask  lidar2nc  mode           pb2nc
plot_data_plane  point_stat     wavelet_stat
ensemble_stat  grid_stat    madis2nc  mode_analysis  pcp_combine
plot_point_obs   stat_analysis
/d1/METplus_Data/met_test/scripts:
ascii2nc       gen_vx_mask  madis2nc  mode_analysis     plot_data_plane
regrid_data_plane  stat_analysis
config         gis_utils    Makefile  mode_time_domain  plot_point_obs
Rscripts           tc_utils
ensemble_stat  grid_stat    mk        pb2nc             point_stat
series_analysis    wavelet_stat
examples       gsi_tools    mode      pcp_combine       python
shift_data_plane   wwmca
On Fri, Nov 15, 2019 at 10:40 AM jprestop<EMAIL_ADDRESS>wrote:

I thought that at first too, but then I remembered the data that we
discussed at the meeting was a small amount of data.
The data used in make_test is small:
[Julie.Prestopnik@hfe10 met-8.1]$ du -sh data
181M data
[Julie.Prestopnik@hfe10 met-8.1]$ du -sh out
82M out
But, the data used in the nightly build and testing of MET is large and is
not on hera:
dakota:jpresto:~% du -sh /d3/projects/MET/MET_test_data/unit_test
49G /d3/projects/MET/MET_test_data/unit_test
It is entirely possible that I am confused and misunderstanding something.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZN5VH23MMDKB757YTF3QT3NKDA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEGFSTQ#issuecomment-554457422,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFSSZN4FPHWTTPJMOSPIQ5LQT3NKDANCNFSM4HMRYG7Q
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.

Thank you, George.  In that case, no, the met_test data is not on hera because the METplus-2.2 sample data is not yet present on hera.  Only the sample data for 2.0, 2.0.4, and 2.1 is on hera.  I will put the met_test data on hera.  It will be located at /scratch1/BMC/dtc/Julie.Prestopnik/METplus.  I will update the webpage as well: https://dtcenter.org/community-code/model-evaluation-tools-met/metv8-1-existing-builds-metplus-2-1-installations

What is in /contrib/met/8.1/met-8.1/data? This likely contains the same
data.
On Fri, Nov 15, 2019 at 10:54 AM jprestop<EMAIL_ADDRESS>wrote:

Thank you, George. In that case, no, the met_test data is not on hera
because the METplus-2.2 sample data is not yet present on hera. Only the
sample data for 2.0, 2.0.4, and 2.1 is on hera. I will put the met_test
data on hera. It will be located at
/scratch1/BMC/dtc/Julie.Prestopnik/METplus. I will update the webpage as
well:
https://dtcenter.org/community-code/model-evaluation-tools-met/metv8-1-existing-builds-metplus-2-1-installations
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZNYA5PV5KWYLA2RMXRLQT3O4ZA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEGG3CA#issuecomment-554462600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFSSZN2RC464LHYP2YYY4RTQT3O4ZANCNFSM4HMRYG7Q
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.

Yes, the data is /contrib/met/8.1/met-8.1/data appears to be the same data as what is in met_test/data.  However, there is also atcf_data in the met_test directory at the same level as "data", which I do not believe is anywhere in the MET area on hera.
I needed to put the METplus-2.2 data on hera anyway, and I did go ahead and grab the met_test data anyway.   So, all of the METplus-2.2 sample data is on hera now at /scratch1/BMC/dtc/Julie.Prestopnik/METplus/METplus-2.2_sample_data.

Thank you!!

TCStat has a single use case wrapper committed to develop

Hey Hank, I tried to run this use case to test the bugfix that Mallory
pointed out and it failed. It looks like the input data is relative to
{OUTPUT_BASE}. It should be using data in the {INPUT_BASE} area (ideally
from met_test if possible). Could you add this input data to the met_test
area and update the config to use that path? The use case should run
successfully using an empty output directory.
On Mon, Dec 2, 2019 at 4:30 PM Hank Fisher<EMAIL_ADDRESS>wrote:

TCStat has a single use case wrapper committed to develop
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZN3R6XNLIDOH5MYG7I3QWWLC7A5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFXJ7JI#issuecomment-560897957,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFSSZN4BNKLDYY5O5LZCL5DQWWLC7ANCNFSM4HMRYG7Q
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.

I can give it a shot. I initially tried to do that but TCStat depends on
TCPairs and wanted the data in OUTPUT_BASE. I will override that.
I also only did a use case for one of the stats. Let me know if I should
add another. I don't have Mallory's bug in front of me but will look it up
shortly
Hank
On Tue, Dec 3, 2019, 9:02 AM George McCabe<EMAIL_ADDRESS>wrote:

Hey Hank, I tried to run this use case to test the bugfix that Mallory
pointed out and it failed. It looks like the input data is relative to
{OUTPUT_BASE}. It should be using data in the {INPUT_BASE} area (ideally
from met_test if possible). Could you add this input data to the met_test
area and update the config to use that path? The use case should run
successfully using an empty output directory.
On Mon, Dec 2, 2019 at 4:30 PM Hank Fisher<EMAIL_ADDRESS>wrote:

TCStat has a single use case wrapper committed to develop
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZN3R6XNLIDOH5MYG7I3QWWLC7A5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFXJ7JI#issuecomment-560897957
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AFSSZN4BNKLDYY5O5LZCL5DQWWLC7ANCNFSM4HMRYG7Q
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AHAUIKCFKEGEWE3GGZIRTQTQWZ7JDA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZ4FOI#issuecomment-561234617,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAUIKEDFUGMFBQP4D3V5BTQWZ7JDANCNFSM4HMRYG7Q
.

I fixed the bug Mallory mentioned in the develop branch. I think you will
need to take the output from TCPairs and put it in the met_test area so it
can be run without relying on TCPairs running first. It should probably go
in the met_test/out directory in a new tc_stat subdirectory.
On Tue, Dec 3, 2019 at 10:44 AM Hank Fisher<EMAIL_ADDRESS>wrote:

I can give it a shot. I initially tried to do that but TCStat depends on
TCPairs and wanted the data in OUTPUT_BASE. I will override that.
I also only did a use case for one of the stats. Let me know if I should
add another. I don't have Mallory's bug in front of me but will look it up
shortly
Hank
On Tue, Dec 3, 2019, 9:02 AM George McCabe<EMAIL_ADDRESS>wrote:

Hey Hank, I tried to run this use case to test the bugfix that Mallory
pointed out and it failed. It looks like the input data is relative to
{OUTPUT_BASE}. It should be using data in the {INPUT_BASE} area (ideally
from met_test if possible). Could you add this input data to the met_test
area and update the config to use that path? The use case should run
successfully using an empty output directory.
On Mon, Dec 2, 2019 at 4:30 PM Hank Fisher<EMAIL_ADDRESS>wrote:

TCStat has a single use case wrapper committed to develop
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<

https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZN3R6XNLIDOH5MYG7I3QWWLC7A5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFXJ7JI#issuecomment-560897957

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AFSSZN4BNKLDYY5O5LZCL5DQWWLC7ANCNFSM4HMRYG7Q

.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AHAUIKCFKEGEWE3GGZIRTQTQWZ7JDA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZ4FOI#issuecomment-561234617
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AHAUIKEDFUGMFBQP4D3V5BTQWZ7JDANCNFSM4HMRYG7Q
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZN2EKRJNMBMDCMWW4WTQW2LGHA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2G6TY#issuecomment-561278799,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFSSZN4FTEZX5J6QV3AYLCTQW2LGHANCNFSM4HMRYG7Q
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.

I am using some TCPairs data that is already there but I had to copy that
data to the output directory to have it found. Still working on pointing
TCStat to a different input location.
Hank
On Tue, Dec 3, 2019, 1:11 PM George McCabe<EMAIL_ADDRESS>wrote:

I fixed the bug Mallory mentioned in the develop branch. I think you will
need to take the output from TCPairs and put it in the met_test area so it
can be run without relying on TCPairs running first. It should probably go
in the met_test/out directory in a new tc_stat subdirectory.
On Tue, Dec 3, 2019 at 10:44 AM Hank Fisher<EMAIL_ADDRESS>wrote:

I can give it a shot. I initially tried to do that but TCStat depends on
TCPairs and wanted the data in OUTPUT_BASE. I will override that.
I also only did a use case for one of the stats. Let me know if I should
add another. I don't have Mallory's bug in front of me but will look it
up
shortly
Hank
On Tue, Dec 3, 2019, 9:02 AM George McCabe<EMAIL_ADDRESS>wrote:

Hey Hank, I tried to run this use case to test the bugfix that Mallory
pointed out and it failed. It looks like the input data is relative to
{OUTPUT_BASE}. It should be using data in the {INPUT_BASE} area
(ideally
from met_test if possible). Could you add this input data to the
met_test
area and update the config to use that path? The use case should run
successfully using an empty output directory.
On Mon, Dec 2, 2019 at 4:30 PM Hank Fisher<EMAIL_ADDRESS>wrote:

TCStat has a single use case wrapper committed to develop
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<

https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZN3R6XNLIDOH5MYG7I3QWWLC7A5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFXJ7JI#issuecomment-560897957

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AFSSZN4BNKLDYY5O5LZCL5DQWWLC7ANCNFSM4HMRYG7Q

.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<

https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AHAUIKCFKEGEWE3GGZIRTQTQWZ7JDA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZ4FOI#issuecomment-561234617

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AHAUIKEDFUGMFBQP4D3V5BTQWZ7JDANCNFSM4HMRYG7Q

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AFSSZN2EKRJNMBMDCMWW4WTQW2LGHA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2G6TY#issuecomment-561278799
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AFSSZN4FTEZX5J6QV3AYLCTQW2LGHANCNFSM4HMRYG7Q
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/issues/231?email_source=notifications&email_token=AHAUIKE4T72Y2YU2DE6SDQ3QW24QDA5CNFSM4HMRYG72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2VCPY#issuecomment-561336639,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAUIKDZXSZM3655MMDT2R3QW24QDANCNFSM4HMRYG7Q
.


Cant add sensor

Just get this error:
Configuration validation
Validate your configuration if you recently made some changes to it and want to make sure that it is all valid.
Configuration invalid!
Platform error sensor.nordpool_planner - No module named 'custom_components.nordpool_planner.sensor'
Iv added it via hacs

Sorry for that, forgot to update documentation. Shall be under "binary_sensor".
Will fix dokumentation asap

The documentation is updated in release 0.1.2 but you don't have to update, just change the setting in your configuration.yaml
Version 0.1.2 also has new a feature which I haven't had time to test that much so safe option is to stay on v0.1.1 and just update config, but are happy to receive feedback on new feature if you want to test it

I would like to test yes :) Ill do an upgrade.
BTW on 0.1.1 i get this error:
Invalid config for [binary_sensor.nordpool_planner]: [accept_level] is an invalid option for [binary_sensor.nordpool_planner]. Check: binary_sensor.nordpool_planner->accept_level. (See ?, line ?).


Connecting iOS device keeps files and fodlers empty

Abstract
The synchronisation hung up immediately after connecting.
Out of a sudden my sync between 2 devices stopped working. I've chosen my Laptop to have the better status for a recovery and ditched the mobile iOS app. Every attempt to re-create, delete or even use a new couch DB didn't solve my problem that the mobile device shows a lot of replication logs (-> Applied filnema.md).
Expected behaviour

A freshly installed iOS app is syncing the whole content from the couch DB

Actually happened

Laptop seems to be up to date with the couch DB
iOS device is not

Reproducing procedure
Unfortunately I have no clue how I ended up in this situation. Sync was working like a charm for months now.
Report materials
I will provide all logs you might need. Right now I don't know where to start. So please let me know wich log might be useful for you.
Report from the LiveSync
Thats the report from the mobile device.

The app is doing stuff for a long time but in the end, the mobile app shows always 0 folders and 0 files.

Okay, I only resolved this by completely uninstalling the Live Sync plugin on both devices and deleting the CouchDB database. Afterwards, I started from scratch, and now it's working again.

Thank you for opening the issue and helpful information! And, sorry for being late for reply!
Self-hosted LiveSync stores the content of the vault to the local database which is inside Obsidian. This database would not be deleted automatically even if we have deleted the vault against our intuition. Therefore, if we create a data vault with the same name and install LiveSync, the contents of the local database that were not deleted will be restored.
To avoid this behaviour, we can discard the local database before deleting the vault. It could be performed by using before Discard local database to reset or uninstall Self-hosted LiveSync in the Maintain Databases pane.
Or, we can put redflag2.md on top of the vault before installing LiveSync. This file tells to the LiveSync to Rebuild local database from the content of this vault.
I think that I should make documents about this and decide on a suitable name for command files.
I hope that this information will answer some of your confusion.

Thanks for the explanation.


type 'set' is not supported for sql wrangle

sqlLite does not support set data types, returning this error when ran:
sqlite3.ProgrammingError: Error binding parameter 1: type 'set' is not supported

See test_to_dict_where in test_merge.py on the "Where-Wrangles" branch to replicate.

Fixed in Where-Wrangles


mgmt+tsp, brownfield for vmware/avs

vmware/avs already GAed with Swagger
service moved to TypeSpec on 2023-09-01
https://github.com/Azure/azure-rest-api-specs/pull/28023
(at the time of the PR, the breaking changes CI having problem and not picking up the breaks)

REST API breaks

removal of OperationProperties properties from Operation

Partly REST API breaks

extensible enum WorkloadNetworkName changed to default in URL

SDK

x-ms-client-flatten
mismatch on model names / property names

Mostly addressable in client.tsp
https://github.com/Azure/azure-rest-api-specs/pull/29308

SDK operation groups

Lots of @operationId, which is not supported in SDK emitter

WIP on whether we need to modify the interface structure in route.tsp

Java: seems missed Addon$Update.withProperties

service should name the folder as suffix ".Management", see https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/typespec-structure-guidelines.md#service-folder-structure

I thought it was the RP name. Yes, you can change it to align with the guidance.

removal of OperationProperties properties from Operation

We do not actually want the operation API in our spec or SDKs. I've never understood why it is required. Anyhow, in TypeSpec we are using the standard typespec-azure-core definition.
https://github.com/Azure/azure-rest-api-specs/blob/32f566eb38af9593cfc1ed183362471c50d67fb2/specification/vmware/Microsoft.AVS/routes.tsp#L15

leaseTime changed from int64 to int32

This was unintentional. It should be changed back to int64.

extensible enum WorkloadNetworkName changed to default in URL

This was an approved breaking change. model WorkloadNetwork is a @singleton and this is how it is modeled in TypeSpec.

SDK operation groups

Lots of @operationId, which is not supported in SDK emitter (they are only for typespec-autorest emitter)

WIP on whether we need to modify the interface structure in "route.tsp" e.g. Azure/azure-rest-api-specs@7105e2d
(alternative is write all the APIs explicitly in client.tsp, which likely be hard to maintain)

I did a lot of work to make the operationIds match in the generated OpenAPI. Are there operationIds that do not match? Are you generating the SDK from the OpenAPI spec or directly from TypeSpec?

@operationId is from typespec-openapi lib
<EMAIL_ADDRESS>SDK would generate directly from TypeSpec (and hence won't use the openapi lib or any decorator within).
The @operationId is required anyway, since mslearn still generate REST API doc from Swagger.
Just emitter need a different way to solve the operation group.

removal of OperationProperties properties from Operation

We do not actually want the operation API in our spec or SDKs. I've never understood why it is required. Anyhow, in TypeSpec we are using the standard typespec-azure-core definition.
https://github.com/Azure/azure-rest-api-specs/blob/32f566eb38af9593cfc1ed183362471c50d67fb2/specification/vmware/Microsoft.AVS/routes.tsp#L15

But, unfortunately, it is already in Swagger for a very long time, and lots of SDK is shipped with that.
We will discuss the break within SDK devs first, see if we accept it, or try to keep backward-compatible. Do you mind, if we modify the operation to make it same as your older Swagger, if we decide to keep backward-compatible?

leaseTime changed from int64 to int32

This was unintentional. It should be changed back to int64.

PR to fix https://github.com/Azure/azure-rest-api-specs/pull/29351
Please approve the PR if you are OK with it.

removal of OperationProperties properties from Operation

We do not actually want the operation API in our spec or SDKs. I've never understood why it is required. Anyhow, in TypeSpec we are using the standard typespec-azure-core definition.
https://github.com/Azure/azure-rest-api-specs/blob/32f566eb38af9593cfc1ed183362471c50d67fb2/specification/vmware/Microsoft.AVS/routes.tsp#L15

But, unfortunately, it is already in Swagger for a very long time, and lots of SDK have been shipped with that.
We will discuss the break within SDK devs first, see if we accept it, or try to keep backward-compatible. Do you mind, if we modify the operation to make it same as your older Swagger, if we decide to keep backward-compatible?

We are using the standard Azure.ResourceManager.Operations. We never wanted the API in our SDKs. We do not want to maintain a non-standard version of it.

Hi @weidongxu-microsoft , a engineer working on the Azure CLI noticed that ManagementCluster used to require clusterSize, but no longer does. That was non intentional and should be changed back. Do you see the impact in this generated Java SDK?
https://github.com/Azure/azure-rest-api-specs/blob/1418642cf8a57954c781c26c759fd4aef39a1287/specification/vmware/resource-manager/Microsoft.AVS/stable/2023-03-01/vmware.json#L6106-L6110

Hi @weidongxu-microsoft , an engineer working on the Azure CLI noticed that ManagementCluster used to require clusterSize, but no longer does. That was non intentional and should be changed back. Do you see the impact in this generated Java SDK?
https://github.com/Azure/azure-rest-api-specs/blob/1418642cf8a57954c781c26c759fd4aef39a1287/specification/vmware/resource-manager/Microsoft.AVS/stable/2023-03-01/vmware.json#L6106-L6110
    "ManagementCluster": {
      "type": "object",
      "description": "The properties of a management cluster",
      "required": [
        "clusterSize"
      ],

As mentioned in the discription of this issue, the BreakingChanges CI is broken when your prepare/merge that migration PR. It really not able to report anything useful. (tooling team already got notified and fixing/fixed the problem)
This part of Swagger is pretty tricky. You can see that the clusterSize is defined in CommonClusterProperties, but the required=["clusterSize"] is defined in ManagementCluster. SDK codegen/emitter may not able to handle this case as what you expect (as most model this allOf as superclass/subclass relationship).
I've look at existing .NET code, seems not a required as well. (it is int? with a default value)
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/avs/Microsoft.Azure.Management.Avs/src/Generated/Models/ManagementCluster.cs#L39

And we are still in the progress of trying to get all the potential breaks.
Here is another one, please let us know if we want to revert this int32 back to int64

dnsServices changed from int64 to int32

And we are still in the progress of trying to get all the potential breaks.
Here is another one, please let us know if we want to revert this int32 back to int64

dnsServices changed from int64 to int32

Yes, also unintentional and should be changed back.

This part of Swagger is pretty tricky. You can see that the clusterSize is defined in CommonClusterProperties, but the required=["clusterSize"] is defined in ManagementCluster. SDK codegen/emitter may not able to handle this case as what you expect (as most langugages model this allOf as superclass/subclass relationship, and subclass usually won't touch property/variable from its superclass).
I've looked at existing .NET code (2021-06-01? form the last commit), appears not a required as well. (it is int? with a default value) https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/avs/Microsoft.Azure.Management.Avs/src/Generated/Models/ManagementCluster.cs#L39

You are right. Same with JavaScript here, it is clusterSize?: number;. I think it is best to leave it the way it is.

Yes, also unintentional and should be changed back.

PR to fix https://github.com/Azure/azure-rest-api-specs/pull/29395

I was told by Go that there was multiple places in PATCH, that previously request body is e.g. WorkloadNetworkSegment (same model as in PUT) being changed to WorkloadNetworkSegmentUpdate
This would cause some breaks to Go (and probably other languages as well).
Please let us know if this is intended. If yes, any reason?

SDK models

x-ms-client-flatten
mismatch on model names / property names

Mostly addressable in "client.tsp" Azure/azure-rest-api-specs#29308
Important: AddonProperties cannot be x-ms-client-flatten as it is polymorphic Should TCGC handle this (i.e., set flatten=false, whatever the @flattenProperty)?

@weidongxu-microsoft , the following two properties need to be renamed back to current name in client.tsp.
`PrivateCloud.Identity`
`PrivateCloudUpdate.Identity`

SDK models

x-ms-client-flatten
mismatch on model names / property names

Mostly addressable in "client.tsp" Azure/azure-rest-api-specs#29308
Important: AddonProperties cannot be x-ms-client-flatten as it is polymorphic Should TCGC handle this (i.e., set flatten=false, whatever the @flattenProperty)?

@weidongxu-microsoft , the following two properties need to be renamed back to current name in client.tsp.
`PrivateCloud.Identity`
`PrivateCloudUpdate.Identity`

In TypeSpec, it can be renamed in client.tsp
https://github.com/Azure/azure-rest-api-specs/blob/1418642cf8a57954c781c26c759fd4aef39a1287/specification/vmware/Microsoft.AVS/client.tsp#L59-L64
For Swagger, it may had to be done via directive.

rename of List responses from ##List to ##ListResult

This can be handled by using a customized ResourceList template, e.g. https://github.com/Azure/azure-rest-api-specs/pull/29408/files

There is also some changes to "x-ms-mutability", e.g. properties in Addon changed to "read", "create" -- meaning this proxy resource cannot be updated
The x-ms-mutability comes from ProxyResource in lib
Is it intended?

There is certain change to "x-ms-mutability", e.g. properties in Addon changed to "read", "create" -- meaning this proxy resource cannot be updated
The x-ms-mutability comes from ProxyResource in lib
Is it intended?

It is not intended.

rename of List responses from ##List to ##ListResult

This can be handled by using a customized ResourceList template, e.g. https://github.com/Azure/azure-rest-api-specs/pull/29408/files

I approved that draft. That looks like a good way to restore name compatibility.

@weidongxu-microsoft , the following two properties need to be renamed back to current name in client.tsp.
`PrivateCloud.Identity`
`PrivateCloudUpdate.Identity`

In TypeSpec, it can be renamed in client.tsp https://github.com/Azure/azure-rest-api-specs/blob/1418642cf8a57954c781c26c759fd4aef39a1287/specification/vmware/Microsoft.AVS/client.tsp#L59-L64
For Swagger, it may had to be done via directive. Azure/azure-rest-api-specs#29413

We do wish that the generated SDKs use the standard identity types. We support system identity now, but will support user managed identity in the future.

I was told by Go that there was multiple places in PATCH, that previously request body is e.g. WorkloadNetworkSegment (same model as in PUT) being changed to WorkloadNetworkSegmentUpdate
This would cause some breaks to Go (and probably other languages as well).
Please let us know if this is intended. If yes, any reason?

No, not intended.

There is certain change to "x-ms-mutability", e.g. properties in Addon changed to "read", "create" -- meaning this proxy resource cannot be updated
The x-ms-mutability comes from ProxyResource in lib
Is it intended?

It is not intended.

The unreleased typespec-azure-resource-manager appears have removed this @visibility
https://github.com/Azure/typespec-azure/blob/main/packages/typespec-azure-resource-manager/lib/models.tsp#L62-L66

I was told by Go that there was multiple places in PATCH, that previously request body is e.g. WorkloadNetworkSegment (same model as in PUT) being changed to WorkloadNetworkSegmentUpdate
This would cause some breaks to Go (and probably other languages as well).
Please let us know if this is intended. If yes, any reason?

No, not intended.

PR to move it back https://github.com/Azure/azure-rest-api-specs/pull/29392

Thanks @weidongxu-microsoft for the spec PRs. Here is a summary:

https://github.com/Azure/azure-rest-api-specs/pull/29351
https://github.com/Azure/azure-rest-api-specs/pull/29395
https://github.com/Azure/azure-rest-api-specs/pull/29408
https://github.com/Azure/azure-rest-api-specs/pull/29392
x-ms-mutability fix in next Azure TypeSpec version

The TypeSpec fix was merged two days ago.

https://github.com/Azure/typespec-azure/pull/979

All Swagger related PR should have been merged.
Allen upgraded spec repo to 0.57 as well (it could include the Swagger change via typespec-azure-resource-manager).
Swagger should be completed.
Remain issue to TypeSpec (on SDK emitter) is the operation group that is still in discussion https://gist.github.com/weidongxu-microsoft/fa420c35cf0611a62a8d155771dd3425


Ensure the pristine checksums are not recomputed

When switching between the pristine and PR checkouts we must
ensure the pristine checksums are not recomputed.
Also ignore errors (such as trying to remove a label that
is not set) when setting or removing labels.

Merged. Thank you again for the swift review.


State might choose one of the many. Mainstream is Provider or Bloc.

State might choose one of the many. I think Mainstream is Provider or Bloc
Maybe people ended up dropping Triple because they had a "provider". Although it's not perfect.
Or, people encapsulate on "triple" on Mainstream.

some code from common_bloc

BlocBuilder<RequestBloc, RequestState>(
            bloc: _requestBloc,
            builder: (context, state) => state.map(
                uninitialized: (s) => Center(child: Text('Uninitialized')),
                error: (s) =>
                    Center(child: Text('I\'m an error :( | ${s.message}')),
                loading: (s) => Center(child: CircularProgressIndicator()),
                loaded: (s) => Center(
                    child: Text(_generateRequestResult(s),
                        textAlign: TextAlign.center)))));

class RequestCubit extends Cubit<RequestState> {
  ///Main Constructor
  RequestCubit() : super(RequestState.uninitialized());

  ///Perfoms an action that be dispatched by RequestCubit
  ///
  ///requestAction needs to return the data you will need later.
  void perform(Function requestAction, String requestName,
      {bool withLoading = true}) async {
    if (withLoading) emit(RequestState.loading());
    try {
      final result = await requestAction();
      emit(RequestState.loaded(
          data: result,
          lastRequest: requestName,
          timestamp: DateTime.now().toIso8601String()));
    } on Exception catch (e) {
      emit(RequestState.error(message: e.toString()));
    }
  }
}

Just don't care about this lib

Sorry. i don't understand this message.


Search is not working

https://semantic-ui-vue.github.io/#/modules/search#Types-Search
[Vue warn]: Error in render: "TypeError: Cannot read property 'toLowerCase' of undefined"
found in
--->

Where exactly is this happening?


[SPARK-7676] Bug fix and cleanup of stage timeline view

cc @pwendell @sarutak
This commit cleans up some unnecessary code, eliminates the feature where when you mouse-over a box in the timeline, the corresponding task is highlighted in the table (because that feature is only useful in the rare case when you have a very small number of tasks, in which case it's easy to figure out the mapping anyway), and fixes a bug where nothing shows up if you try to visualize a stage with only 1 task.

Merged build triggered.

Merged build started.

Test build #32857 has started for   PR 6202 at commit dfd29d4.

Thanks for the bug fix and cleanup @kayousterhout !
I inspected the change and checked the appearance. In terms of removing the highlighting, I agree with you and how about adding a feature in order to jump to the corresponding row  instead?
@pwendell , what do you think about the removal because you suggested this highlighting feature.
Once the highlighting thing is resolved, LGTM.

I think @kayousterhout is right - we can remove the feature since it's only
useful in a small number of cases.
On Fri, May 15, 2015 at 3:54 PM, Kousuke Saruta<EMAIL_ADDRESS>wrote:

Thanks for the bug fix and cleanup @kayousterhout
https://github.com/kayousterhout !
I inspected the change and checked the appearance. In terms of removing
the highlighting, I agree with you and how about adding a feature in order
to jump to the corresponding row instead?
@pwendell https://github.com/pwendell , what do you think about the
removal because you suggested this highlighting feature.
Once the highlighting thing is resolved, LGTM.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/6202#issuecomment-102542906.

Test build #32857 has finished for   PR 6202 at commit dfd29d4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32857/
Test PASSed.

@sarutak Let's do that as a separate PR (the feature so you can click on a link to jump to the correct row), just so we can get this cleanup in!


BCML not installing (downloaded miniconda 3.7)

I installed miniconda 3.7 from https://docs.conda.io/en/latest/miniconda.html#linux-installers, launched the install BCML script and got this back;
#!/bin/bash
if test -f ~/miniconda3/condabin/conda &> /dev/null
then
echo "BCML will now be installed. This might take a bit."
zenity --info --text "BCML will now be installed. This might take a bit." --title "BCML Installer" --width=300 &> /dev/null
~/miniconda3/condabin/conda init
~/miniconda3/condabin/conda install -c conda-forge gcc -y
~/miniconda3/condabin/conda install pip -y
~/miniconda3/bin/python -m pip install bcml
mkdir ~/.icons
wget https://github.com/sks316/bcml-steamdeck/raw/main/bcml.png -O ~/.icons/bcml.png
wget https://github.com/sks316/bcml-steamdeck/raw/main/BCML.desktop -O ~/Desktop/BCML.desktop
chmod +x ~/Desktop/BCML.desktop
cp ~/Desktop/BCML.desktop ~/.local/share/applications/BCML.desktop
echo "BCML is now installed. You can access it with the icon on your desktop, or through your application launcher."
zenity --info --text "BCML is now installed. You can access it with the icon on your desktop, or through your application launcher." --title "BCML Installer" --width=300 &> /dev/null
else
echo "Miniconda is missing. Please install Miniconda with Python 3.7, then run this script again."
zenity --error --text "Miniconda is missing. Please install Miniconda with Python 3.7, then run this script again." --title "BCML Installer" --width=300 &> /dev/null
fi
exit
not sure what to do, tried reinstalling(miniconda and BCML installer), installing a different miniconda version(3.8)

That's just the text for the installer script. What exactly did you do, did you download the .desktop file from the releases page or did you download the bash script from the repository?

under the releleases section i clicked the link and downloaded the .desktop file

I got it to work! I believe I copied the text that showed when I clicked the application into Konsole, and it downloaded, no problems


bumping frameworks version to 5.1.3

This time to pull in the renaming of region to location in the manifests.

👍 when tests green


set EndSilenceTimeoutAmbiguous and BabbleTimeout from Python

There is a number of speech properties not exposed in the Python SDK - e.g. EndSilenceTimeoutAmbiguous and BabbleTimeout.
How can I set these properties from a Python script?

Those two properties are not applicable when using the Cognitive Services Speech SDK since it uses newer and more robust speech recognition models.
You can find more information about the timeouts that can be set for the new speech recognition service here:
https://learn.microsoft.com/azure/cognitive-services/speech-service/how-to-recognize-speech?pivots=programming-language-csharp#change-how-silence-is-handled.

Awesome. Thanks a lot!


Support for Pandoc line_blocks extension

Pandoc allows for a special kind of block quote marked with a | in which

The division into lines will be preserved in the output, as will any leading spaces; otherwise, the lines will be formatted as Markdown. This is useful for verse and addresses.

From pandoc
I use this environment all the time since I'm a scholar who writes about poetry. I'm happy to give it a go myself if someone would be willing to point me in the right direction.

Sorry, this should be in the pandoc project. I'll move it over there.


Provide better issue templates for vuestic-admin and vuestic-ui

What do we need:
3 issue types:

[ ] Bug report
[ ] Feature request
[ ] Empty (for contributors)

[ ] Implement is also for vuestic-ui (maybe with some specifics for ui project).
[ ] We should also include discord link in the issue as that's recommended approach if user is looking for discussion instead of report.
[ ] For bonus points - also sync labels between repos. :)

You would have to look up what any of these issue types need. Generally we want to keep templates not annoying as vuestic is not popular enough to get swarmed yet :D.

Probably also relevant for UI.


Use pebble templating for index

This changes the config slightly: faq and info locations no longer specify if they are a resource or a file and require no such prefixes.
This change was made because using templating for html files is a pre-requisite to automated localization, which seems to be a topic of interest right now.

Merging #475 instead.


chore(resources): cleanup v1beta1 resources

Welcome to Cryostat! 👋
Before contributing, make sure you have:

[x] Read the contributing guidelines
[x] Linked a relevant issue which this PR resolves
[x] Linked any other relevant issues, PR's, or documentation, if any
[x] Resolved all conflicts, if any
[x] Rebased your branch PR on top of the latest upstream main branch
[x] Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
[x] Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

Fixes: #846

/build_test

/build_test


Added Typescript defs; need to integrate w/NPM publish.

Hey Guys --
I'd like to add Typescript support. I've added a tsconfig.json file and added the compile step to the package.json. The d.ts definitions are now published with the .js files in the ./dist folder. Still need to include them with the NPM package, but not sure how you'd like to handle that, (bundled/publish to @types).
Let me know your thoughts...
Scott --

Hi Scott,
Thanks a lot for this initiative. It is much appreciated.
I'll look into it in the coming days.  I've also added an example in the appropriate folder. That would be great if you can have a look into the PR: https://github.com/vagabondrev/epcis2.js/pull/1
Thanks a lot,
Clement

Hey Clement -
I've merged your changes into my fork of the repo, and added some comments to the tsconfig.json to help decide which approach you prefer for publication of the module.
I'll close this PR and open another with those updates.
Scott -


Customizing Support for Different Image Formats

Hi,
Is there any information we should be made aware of, outside of the custom libvips and minor tweaks to the standalone CF template, that can help in achieving the goal of supporting JPEG 2000 formatted images?

Not that I know of. The only thing blocking support is being able to build a JPEG 2000-enabled libvips and linking sharp against it. I've taken a run at it a few times, but since we don't use JP2 in house, I didn't put a lot of time into it. I might take another shot in a few weeks.

we are interested in this too and do have a libvips build script for another lambda. I'll see if I can start a PR for this.

@orangewolf - Thank you for tackling this. After multiple attempts to resolve, the following error is the current blocker.
{
  "errorType": "Error",
    "errorMessage": "\nSomething went wrong installing the \"sharp\" module\n\nlibvips-cpp.so.42: cannot open shared object file: No such file or directory\n\nPossible solutions:\n- Install with verbose logging and look for errors: \"npm install --ignore-scripts=false --foreground-scripts --verbose sharp\"\n- Install for the current linux-x64 runtime: \"npm install --platform=linux --arch=x64 sharp\"\n- Consult the installation documentation: https://sharp.pixelplumbing.com/install"
}

I am thinking this can be resolved by building and running this process in a Docker container and using Lambda to run the container. I have not yet attempted this approach, but more interested in your thoughts on this being a viable solution.
Thanks,
Brian

@codeclout in the draft PR above, we build a layer to handle the updated Sharp. You don't really want to run docker in your lambda because spin up time becomes killer. There are instructions here: https://github.com/samvera-labs/serverless-iiif/pull/86/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L106 for trying it out. Michael is planning to publish the layer, which will negate the need to build it locally.

@orangewolf  - thank you

@orangewolf - Thanks again for the new layer... I just had time allocated to spin it up this sprint. I'm getting the following error.
"errorMessage": "\nSomething went wrong installing the \"sharp\" module\n\nCannot find module '../build/Release/sharp-linux-x64.node'\nRequire stack:\n- /var/task/node_modules/sharp/lib/sharp.js\n- /var/task/node_modules/sharp/lib/constructor.js\n- /var/task/node_modules/sharp/lib/index.js\n- /var/task/node_modules/iiif-processor/lib/transform.js\n- /var/task/node_modules/iiif-processor/index.js\n- /var/task/index.js\n- /var/runtime/index.mjs\n\nPossible solutions:\n- Install with verbose logging and look for errors: \"npm install --ignore-scripts=false --foreground-scripts --verbose sharp\"\n- Install for the current linux-x64 runtime: \"npm install --platform=linux --arch=x64 sharp\"\n- Consult the installation documentation: https://sharp.pixelplumbing.com/install"

Any thoughts as to what we're doing incorrectly?
Thanks in advance


Upgraded the Web3Auth version from 3.0.4 to 5.2.0 [PRO-1396]

Description
Social Logins Fix for Safari. Upgraded the Web3Auth version from 3.0.4 to 5.2.0
Reference
https://linear.app/pillarproject/issue/PRO-1396/buidler-social-logins-fix-for-safari
Demo

LGTM. @parag-chauhan did the web3auth guys remove the /core package from their new version?

@MayukhSamadder2000 Yes. They have renamed to nomodal


most items are no longer goo

some weirdness has happened with goo values, several items have been declared not goo when it seems like they should be, it's also not just hidden, the gooifier will refuse to melt them
versions:
minecraft: 1.16.3
forge: 34.1.19
aequivaleo: 0.0.105-ALPHA-universal
patchouli: 1.16.2-44
goo: 1.16.3-<IP_ADDRESS>

Probably an Aequivaleo issue; there has been a lot of backend work very recently to correct a variety of problems. Orion may have some answers, but it's possible that newer Aequivaleo builds have already addressed them. I'll keep an eye on it so we can check again in a later build.

A PR needs to be merged into Aequivaleo: ldtteam/Aequivaleo#7 needs to be merged to gain improvements on this front.

Transfered to ldtteam/Aequivaleo#8