PRL-4033: Urgent case creation by CourtAdmin

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the keep-helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Create a new one hence closing it


User unsubscribe() method not working as expected

Description
Calling unsubscribe method on a subscribed user prevents that the same user can be subscribed again.
The next time the member.getAndSubscribeUser(callback) method is called the CallbackListener callback is never going to be triggered neither with the onError(erroInfo).
The same flow was working instead on v3.1.1 version.
The same issue is present also on iOS Chat SDK.
Steps to Reproduce

call member.getAndSubscribeUser(callback) or client.users.getAndSubscribeUser(identity, callback) and wait for the onSuccess(user) callback has been called.
call user.unsubscribe() when the user's updates are no longer needed.
go thru step 1 again but callback will no longer be triggered

Code
This use case has been tested on the demo app and can be easily reproduced adding the following code to MessageActivity.kt:
    override fun onDestroy() {
        channel?.removeListener(this@MessageActivity)
        TwilioApplication.instance.basicClient.chatClient?.users?.subscribedUsers?.forEach {
            it.unsubscribe()
        }
        super.onDestroy()
    }

Expected Behavior
We expect to be able to subscribe to the same user again after some time.
Chat Android SDK
v4.2.3
Android API
Tested on api 26, 28 and 29

fixed in v4.2.5


Update cruft

Update cruft with trusted publisher.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.57%. Comparing base (1b1339d) to head (e44363d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #982   +/-   ##
=======================================
  Coverage   92.57%   92.57%
=======================================
  Files          19       19
  Lines        1818     1818
=======================================
  Hits         1683     1683
  Misses        135      135

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Clarify that USE_POD_CIDR is required when using host-local IPAM

fixes

documents

[ ] Tests
[ ] Documentation
[ ] Release note

None required

Deploy preview for calico ready!
Built with commit 964bfc15e9782b7726a3c2f26438ff18c43e2fc4
https://deploy-preview-2701--calico.netlify.com


tutorial typo

From Step 20:

Functions like map take other functions as parameters.
Functions like (+1), (>5) and square can be passed to other functions.
Defining functions is just a case of writing what to do with the parameters.

Those are arguments not parameters.

Stack Overflow post explaining the difference between the two, I see your point.
Also, the feature section of the home page consistently refers to the same thing as an "argument", so yeah, it would seem to be a typo. A typo people can still alias in their heads to the intended meaning, but still a typo regardless.

Source of the typo has been fixed.

👍


[build] Enable memory leak detection for Tungsten.

This was turned off accidentally in #7591.

cc @JoshRosen

Merged build triggered.

Merged build started.

Test build #38324 has started for   PR 7637 at commit 34bc3ef.

Test build #38324 has finished for   PR 7637 at commit 34bc3ef.

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

Merged build finished. Test PASSed.


Bower does not include leaflet js files in dist folder

[ x] I've looked at the documentation to make sure the behavior is documented and expected
[ x] I'm sure this is a Leaflet code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[ x] I've searched through the issues to make sure it's not yet reported

Steps to reproduce
Steps to reproduce the behavior:

step 1
Include "leaflet": "1.8.0" in the bower.json dependencies
step 2
run bower update

Expected behavior
The files leaflet-src.js and leaflet.js are included
Current behavior
The leaflet project is downloaded into bower_components folder, but the leaflet-src.js and leaflet.js files are missing in the leaflet/dist folder.
Environment

Leaflet version: 1.8.0
Browser (with version): n/a
OS/Platform (with version): Windows 10

Additional context
Minimal example reproducing the issue
Please create an example using https://leafletjs.com/edit.html or any other jsfiddle-like site.
N/A

[ ] this example is as simple as possible
[ ] this example does not rely on any third party code

Please look into https://github.com/Leaflet/Leaflet/discussions/8149#discussioncomment-2601603

It would of been nice to see this listed in the breaking changes. It did break our build.


Consider using drizzle or prisma

So I like the developer experience of these two orm and very easy to be familiar. Do you have any plans to rewrite the source code using one of these two? or you will still use node-posgres going forward?

For the foreseeable future, we will stick with node-postgres.
The FHIR search implementation has very particular requirements at the SQL layer.  We tried Prisma in early prototypes (early 2021), but quickly ran into ORM object–relational impedance mismatch issues.  We tried Knex.js for a while as well, but ran into limitations with TypeScript type definitions.  We have been quite content with our current data access layer for a while now.
We have long term aspirations for a plugin model so that users could bring their own implementation of the data layer.  For example, you could write an implementation of FhirRepository using DynamoDB or CosmosDB or BigTable.  I think that would be an appropriate time to explore ORM alternates.  Here is that discussion: https://github.com/medplum/medplum/discussions/1424


docs: add information about the build dockerfiles

Split out from https://github.com/AdoptOpenJDK/openjdk-infrastructure/pull/1974
Signed-off-by: Stewart X Addison<EMAIL_ADDRESS>
Checklist

[ ] commit message has one of the standard prefixes
[ ] FAQ.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

All comments addressed


Codemirror Themes possible?

Is it possible to use codemirror themes?

Not currently, but you can add styling to SimpleMDE using CSS.

Hi, I've built a theme system for SimpleMDE, it's easy to create your own theme. Hope this would help you!

SimpleMDE Theme Base
SimpleMDE Theme Dark
List of themes

Related issue: #498


Caret jumps backwards after deleting space after inline tex

In the demo page, if you write some inline tex at the very end of a block, and then delete (with backspace) the last space character that is added, the caret will jump backwards a fixed number of spaces.
Then, any attempt to move the caret to the position just after the inline tex element at the end of the block will cause the caret to jump back the same number of spaces.

I have this issue too.

Does anyone have a solution to this problem? In the demo, the mathjax doesn't have this problem. @efloti would you be able to post the code that made the demo?

You can solve the jumping by setting the contenteditable to false on the child prop.
However, if you do that and then delete that last space, your text cursor can disappear into the hidden span. It's better than the jumping, but still not a great user experience.


YAML as a simple task creator?

Hello,
Today I discover doit, and working with it, (a basical configuration) I was thinking that maybe it can be saved on a yaml file, because my configuration is really simple.
My file is this
In a future, I will put some logic for "uptodate" and other things, maybe some check step. Did you think about that?

you can easily load any time of configuration from dodo.py


Version 0.12.1

Once winit 0.10.1 has been published (https://github.com/tomaka/winit/pull/397)

Can you merge and update crates.io?


Functions updated

Now the logic will follow the original version using multivaraite guassian distribution and matrix form.

looks correct to me after a rough read. Merging it for now -- you might fix smaller stuff down the road as you use it.


clarify which guide should we follow for delegated admin feature

Since we are already  "delegating admin on the member account" should we follow the "Management account guide?". Keep in mind, that the links for steps #4 and #5 are broken.
Thanks

Updated the docs and fixed the links noted above.


mvn doesn't read user's custom -Dname and -Durl fields in Carina archetype

Describe the bug
On setup Carina Carina archetype all user's custom fields are changed in  pom.xml file except
-Dname and -Durl fields.
for these two fields xml shows: ${text}
Logs/Links
here are logs after executing mvn clean eclipse:eclipse  fro importing the project to eclipse:
ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] The expression ${name} is deprecated. Please use ${project.name} instead. @
[ERROR] Resolving expression: ‘${name}’: Detected the following recursive expression cycle in ‘name’: [name] @
[WARNING] The expression ${url} is deprecated. Please use ${project.url} instead. @
[ERROR] Resolving expression: ‘${url}’: Detected the following recursive expression cycle in ‘url’: [url] @
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.ydaroshka:ad-test:1.0 (/Users/ydaroshka/ad-test/pom.xml) has 2 errors
[ERROR]     Resolving expression: ‘${name}’: Detected the following recursive expression cycle in ‘name’: [name] -> [Help 2]
[ERROR]     Resolving expression: ‘${url}’: Detected the following recursive expression cycle in ‘url’: [url] -> [Help 2]

fixed with 6.3.30 archetype. Both name and url are correctly detected and deployed to recently created project


Mobile menu is not usable

The current mobile menu is broken, with white text on white background and a missing close icon.
AC

[ ] Link text is readable
[ ] A clickable close icon is present

The icon should have { instead of <.


added Simple HTML Exporter plugin

Types of changes

[ ] Enhancement (project structure, spelling, grammar, formatting)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

A description of the changes proposed in the Pull Request

@pazbardanl does this still work post-refactor?

@jmcook1186 sorry just catching up on this now. It will need to be converted to an exhaust plugin. I can do it today based on the infra established in if-exhaust-plugins but that one also needs to be reviewed

Blocked on IF team making a decision about how exhaust/export should work.

closing as obseleted by our new exhaust script plan. Feel free to refactor and reopen later


Handle uncompletable tasks

Uncompletable tasks are tasks that cannot be completed. See https://todoist.com/help/articles/how-to-create-an-uncompletable-task. They appear in the Todoist interface without a checkbox.
The plugin should not produce a checkmark for these tasks

Agreed this is suboptimal, however the checkbox is disabled so the task cannot be completed.
If your theme supports it or if you are familiar with CSS, this can be rendered differently:
input[type="checkbox"].task-list-item-checkbox:disabled {
	display: none;
}

for example will hide the checkbox.


DNS resolution succeeds on host but fails in containers

Home Assistant release with the issue:

0.97.2
Operating environment (HassOS/Generic):

hassio > os info
board: ova
version: "2.12"
version_cli: "12"
version_cli_latest: "12"
version_latest: "2.12"
Running in x86_64 openbox vm
Supervisor logs:

19-10-18 06:42:46 INFO (MainThread) [__main__] Initialize Hass.io setup
19-10-18 06:42:46 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/amd64-hassio-supervisor with version 179
19-10-18 06:42:46 INFO (MainThread) [__main__] Setup HassIO
19-10-18 06:42:46 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/amd64-hassio-dns with version 1
19-10-18 06:42:46 INFO (MainThread) [hassio.dns] Update resolv from Supervisor
19-10-18 06:42:46 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to <IP_ADDRESS>
19-10-18 06:42:46 INFO (MainThread) [hassio.dns] Start CoreDNS plugin
19-10-18 06:42:46 INFO (SyncWorker_1) [hassio.docker.interface] Clean hassio_dns application
19-10-18 06:42:46 INFO (SyncWorker_1) [hassio.docker.dns] Start DNS homeassistant/amd64-hassio-dns with version 1
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Introspect de.pengutronix.rauc on /
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: de.pengutronix.rauc - /
19-10-18 06:42:46 INFO (MainThread) [hassio.host.info] Update local host information
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-10-18 06:42:46 INFO (MainThread) [hassio.host.services] Update service information
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-10-18 06:42:46 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
19-10-18 06:42:46 INFO (MainThread) [hassio.host.services] Reload local service hassos-apparmor.service
19-10-18 06:42:46 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
19-10-18 06:42:46 INFO (SyncWorker_0) [hassio.docker.interface] Attach to homeassistant/qemux86-64-homeassistant with version 0.97.2
19-10-18 06:42:46 INFO (MainThread) [hassio.hassos] Detect HassOS 2.12 on host system
19-10-18 06:42:46 INFO (SyncWorker_4) [hassio.docker.hassos_cli] Found HassOS CLI homeassistant/amd64-hassio-cli with version 12
19-10-18 06:42:47 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository
19-10-18 06:42:47 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/cebe7a76 repository
19-10-18 06:42:47 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/15ef4d2f repository
19-10-18 06:42:47 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository
19-10-18 06:42:47 INFO (MainThread) [hassio.store] Load add-ons from store: 63 all - 63 new - 0 remove
19-10-18 06:42:47 INFO (MainThread) [hassio.addons] Found 12 installed add-ons
19-10-18 06:42:47 INFO (SyncWorker_8) [hassio.docker.interface] Attach to homeassistant/amd64-addon-configurator with version 3.4
19-10-18 06:42:47 INFO (SyncWorker_6) [hassio.docker.interface] Attach to homeassistant/amd64-addon-letsencrypt with version 3.0
19-10-18 06:42:47 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/amd64-addon-ssh with version 6.2
19-10-18 06:42:47 INFO (SyncWorker_7) [hassio.docker.interface] Attach to hassioaddons/sonweb-amd64 with version v0.8.1
19-10-18 06:42:47 INFO (SyncWorker_5) [hassio.docker.interface] Attach to hassioaddons/ftp-amd64 with version v3.0.2
19-10-18 06:42:47 INFO (SyncWorker_1) [hassio.docker.interface] Attach to sabeechen/hassio-google-drive-backup-amd64 with version 0.98.2
19-10-18 06:42:47 INFO (SyncWorker_3) [hassio.docker.interface] Attach to homeassistant/amd64-addon-mosquitto with version 5.0
19-10-18 06:42:47 INFO (SyncWorker_4) [hassio.docker.interface] Attach to esphome/esphome-hassio-amd64 with version 1.13.6
19-10-18 06:42:47 INFO (SyncWorker_0) [hassio.docker.interface] Attach to hassioaddons/traccar-amd64 with version v0.5.2
19-10-18 06:42:47 INFO (SyncWorker_9) [hassio.docker.interface] Attach to hassioaddons/unifi-amd64 with version v0.11.0
19-10-18 06:42:47 INFO (SyncWorker_6) [hassio.docker.interface] Attach to hassioaddons/motioneye with version v0.5.3
19-10-18 06:42:47 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-10-18 06:42:47 INFO (MainThread) [hassio.snapshots] Found 7 snapshot files
19-10-18 06:42:47 INFO (MainThread) [hassio.discovery] Load 1 messages
19-10-18 06:42:47 INFO (MainThread) [hassio.ingress] Load 0 ingress session
19-10-18 06:42:47 INFO (MainThread) [__main__] Run Hass.io
19-10-18 06:42:47 INFO (MainThread) [hassio.api] Start API on <IP_ADDRESS>
19-10-18 06:42:47 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
19-10-18 06:42:47 INFO (MainThread) [hassio.addons] Phase 'system' start 2 add-ons
19-10-18 06:42:47 WARNING (MainThread) [hassio.addons.validate] Unknown options ipv6
19-10-18 06:42:47 INFO (SyncWorker_0) [hassio.docker.addon] Start Docker add-on hassioaddons/sonweb-amd64 with version v0.8.1
19-10-18 06:42:47 INFO (SyncWorker_1) [hassio.docker.addon] Start Docker add-on homeassistant/amd64-addon-mosquitto with version 5.0
19-10-18 06:42:48 INFO (MainThread) [hassio.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
19-10-18 06:42:48 INFO (MainThread) [hassio.discovery] Send discovery to Home Assistant mqtt from core_mosquitto
19-10-18 06:42:48 ERROR (MainThread) [hassio.homeassistant] Error on call https://<IP_ADDRESS>:8123/api/: Cannot connect to host <IP_ADDRESS>:8123 ssl:None [Connection refused]
19-10-18 06:42:48 INFO (MainThread) [hassio.discovery] Discovery 537d5227471d45a3b963d070823436e9 mesage ignore
19-10-18 06:42:49 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_sonweb
19-10-18 06:42:52 INFO (MainThread) [hassio.addons] Phase 'services' start 6 add-ons
19-10-18 06:42:53 WARNING (MainThread) [hassio.addons.validate] Unknown options name
19-10-18 06:42:53 WARNING (MainThread) [hassio.addons.validate] Unknown options guest
19-10-18 06:42:53 WARNING (MainThread) [hassio.addons.validate] Unknown options map
19-10-18 06:42:53 ERROR (SyncWorker_8) [hassio.docker] Can't create container from addon_core_samba: 404 Client Error: Not Found ("No such image: homeassistant/amd64-addon-samba:8.1")
19-10-18 06:42:53 INFO (SyncWorker_6) [hassio.docker.addon] Start Docker add-on hassioaddons/traccar-amd64 with version v0.5.2
19-10-18 06:42:53 INFO (SyncWorker_0) [hassio.docker.addon] Start Docker add-on hassioaddons/ftp-amd64 with version v3.0.2
19-08-17 12:47:22 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token

Description of problem:
Name resolution of all my localdomain ".horvath" machines is failing. If I login to hassio with ssh -p 22222 nslookup succeeds just fine and /etc/resolv.conf is correct. Running docker exec on my homeassistant container and running nslookup fails and my homeassistant logs are full of name resolution errors.

See discussion in https://github.com/home-assistant/hassio/issues/1231

@frenck I know you are working on it but I wanted to provide this observation:
After using hassio dns options --servers dns://<IP_ADDRESS> and rebooting my hassio dns info looks like this:
core-ssh:~# hassio dns info
host: <IP_ADDRESS>
latest_version: "1"
servers:
- dns://<IP_ADDRESS>
version: "1"

corefile still has all 3
# docker exec -it hassio_dns /bin/bash
bash-5.0# cat corefile
.:53 {
    log
    hosts /config/hosts {
        fallthrough
    }
    forward . dns://<IP_ADDRESS> dns://<IP_ADDRESS> dns://<IP_ADDRESS> {
        health_check 10s
    }
}

and dns appears to use them in a round-robin fashion
core-ssh:~# ping htpc.horvath
ping: bad address 'htpc.horvath'
core-ssh:~# ping htpc.horvath
PING htpc.horvath (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=63 time=0.466 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=63 time=0.232 ms
64 bytes from <IP_ADDRESS>: seq=2 ttl=63 time=0.149 ms
^C
--- htpc.horvath ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.149/0.282/0.466 ms
core-ssh:~# ping htpc.horvath
ping: bad address 'htpc.horvath'
core-ssh:~# ping htpc.horvath
PING htpc.horvath (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=63 time=0.704 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=63 time=0.450 ms
^C
--- htpc.horvath ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.450/0.577/0.704 ms

I know, @nhorvath, see #1238 ;)

Closing this as a duplicate of #1231


Add new kernel launching API for hip-clang

this is the same as https://github.com/ROCm-Developer-Tools/HIP/pull/1457
I created this one because CI seems to have issue with that one

the old one has passed. so close this one


Direct URL to presenter view

It would be convenient when developing one's presentation to have a direct URL to visit an explicit "slide number" and do so, automatically, in presenter mode.
This would allow for discrete URI's and the ability to develop slides, and specifically presentation notes, in more of a real-time paradigm including separate windows autorefreshing.

This has been relased in version 0.10.0.


add freebsd data

@ekohl seems to work well, also flipped to actually "generate" the entries too, as they are all identical


Add Support for thunderbrid 91.0

AttachFromClipboard options are not showing in Thunderbrid 91.0.
Pls add support for thunderbrid 91.0

Update for Thunderbird 91 is under review at Mozilla, should be released today.

Version 1.91.2 is now available.


feat: support multi-engine

Changes

...

Checklist

[x] Read the contribution guide and accept the code of conduct
[ ] Readme (updated or not needed)
[ ] Tests (added, updated or not needed)

Codecov Report

Merging #23 (3af60f4) into main (02152ee) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #23   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            5         5
=========================================
  Hits             5         5


Flakey test TestResourceTemplateStopAndTerminate/ResourceTemplateStop

Flakey, not as often as other examples.
https://github.com/argoproj/argo/pull/4470/checks?check_run_id=1422010222
        --- FAIL: TestCLIWithServerOverHTTP1Suite/TestResourceTemplateStopAndTerminate/ResourceTemplateStop (0.21s)
            cli_test.go:1291:
                	Error Trace:	cli_test.go:1291
                	            				when.go:288
                	            				when.go:297
                	            				cli_test.go:1290
                	            				suite.go:77
                	Error:      	"Name:                resource-tmpl-wf\nNamespace:           argo\nServiceAccount:      default\nStatus:              Pending\nCreated:             Thu Nov 19 03:28:12 +0000 (now)\nProgress:            \n" does not contain "Running"
                	Test:

@sarabala1979 owns this test

Still flakey.

I will take a look tomorrow


Update Tutorial prerequisites

Update Tutorial Prerequisites and add Graphviz to Installation.
@piiswrong @madjam

Please mark graphviz as optional and only needed for mx.viz package.
Otherwise LGTM


Can we use dynamic import with storybook?

Support request summary
Is it possible to use dynamic imports with storybook?
I have tried to create an minimalistic repo to check if I was able to get this do work, and for me it seems like 99% of this is working. It's just to show the component on the page. Hopefully this is just a silly mistake from me, but I was a bit surprised not to find any examples on this when I searched around in the issues and on github  So not sure this should work either.
I get an error message that I have not render the react component correct!
But when logging the component I want to render I get this:
    ƒ () {
      return __WEBPACK_IMPORTED_MODULE_0_react___default.a.createElement(
        'p',
        null,
        'b'
      );
    }

and I assume this is a transpiled react element that is valid. But not sure...
I try to render it by doing <DynamicImportedComponent />
If you simple can not have an async function in as the second argument to .add is there any know workaround for this?
Steps to reproduce
git clone https://github.com/SindreSvendby/storybook-dynamic-import-example
yarn install
yarn storybook
open http://localhost:6006
go to the dynamic story.
``
The master branch is using latest stable version (3.4,7), I have also done the same with v4-alpha.9 (latest version as of now)

### Screenshots / Screencast / Code Snippets (Optional)

![image](https://user-images.githubusercontent.com/1047421/41308625-c1af8728-6e7c-11e8-8c51-f87e65e5a2e2.png)

The add method is not accepting async functions.
You can try to invert this by doing something like this:

const myStories = storiesOf('Modules loading', module)
  .add('static A', () => <A />)
  .add('static B', () => <B />);

getAsyncThings().then((things) => {
  myStories.add(/* .... */);
});


CTI: PM/Org Meeting Agenda

Overview
This issue tracks the agenda for the Civic Tech Index PM meetings with stakeholders(Bonnie).
Action Items
PMs should consider the following points when creating a meeting agenda with stakeholders.

Objective
Project updates
Roadblock and risks
Deadlines and major milestones
Current or anticipated issues (e.g., changes, resource issues, etc.)
Next steps

Meeting times:

It's a weekly meeting every Sunday from 9 am to 9.55 am

Links:
Sep 26th, 2021
Template:
## [Date ]  Meeting Agenda

### Prework to prep for meeting
- [ ] #1126

### Recurring items: Happens on the PM  Saturday meeting
 - [ ] review any issues that are in the [new issue approval column](https://github.com/civictechindex/CTI-website-frontend/projects/1#column-17543324)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each PM
       - [ ] [Bonnie](https://github.com/civictechindex/CTI-website-frontend/issues/assigned/ExperimentsInHonesty)
       - [ ] [Kevin](https://github.com/civictechindex/CTI-website-frontend/issues/assigned/kevindphan)
       - [ ] [Sean](https://github.com/civictechindex/CTI-website-frontend/issues/assigned/smsada)
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] ~review issues with [epic label]() and define how to break down further~ - Currently there are none

### New Items
- [ ]
- [ ] Carry over Items to next meeting that don't get addressed

### FYIs
-

### Notes from Meeting

### Task Items

Resources/Instructions
CTI site
CTI google drive

Miro - UAT

Agenda for Sep 26th, 2021 meeting.

[ ]  #879
[ ]

@ladissi please add the google drive folder link you want me to put the recording files in

@ladissi I put the recording and transcript into this folder

@ladissi I have uploaded the 3 sets of recordings/transcripts from today in this folder
For the last recording which I made by myself for the FAQ, there is a link I reference, here it is
http://civictechindex.org/join-index?tagsToAdd=civictechindex&value=yes
Here is the subheading text for Radical Collaboration:
We must connect with people from different backgrounds, skills, abilities and thinking modalities to learn and share approaches to societal challenges in order to fulfil the potential of open source.

Agenda for Nov 21st, 2021 meeting
Agenda:

PM's will be unavailable 11/28

Notes:
Action Items:

Agenda for Dec 5th, 2021 meeting
Agenda:

Discuss creation of backend issues
Priority of issues recently created
@kevindphan Input
Review Tag Generator Excel Sheet

Notes:
Action Items:

Agenda for Dec 12th, 2021 meeting
Agenda:
Notes:

Google Drive link: https://docs.google.com/document/d/1GkV4wncpcKCedaYltytzMD_BBQOzRuW8zzOP9KGveYg/edit
Action Items:

add to next agenda

Make agenda template using hfla best practice
setup prework template for all team members, use hfla website team as example

2022-01-23 Meeting Agenda
Prework to prep for meeting

[ ]

Recurring items: Happens on the PM  Saturday meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.

[ ] Review assignments for each PM

[ ] Bonnie
[ ] Kevin
[ ] Sean

[ ] finish adding labels to the issue that are still missing them (see audit links above)
[ ] ~review issues with epic label and define how to break down further~ - Currently there are none

New Items

[ ] Make Label Issue
[ ] Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting
Task Items

Add to agenda

Figure out what happened with the instructions I gave to Chali's team about annotating the tag generator with the new screen info

we need to revise on top of the above the guidance for users around recommend vs required affiliation tags.  See https://github.com/civictechindex/CTI-website-frontend/issues/1113#issuecomment-1020600347 for more details

I added this to the team agenda but it does not seem to have been used since November.  https://github.com/civictechindex/CTI-website-frontend/issues/880#issuecomment-1021822612

Add to next agenda https://github.com/civictechindex/CTI-website-frontend/issues/253

[ ] 2FA set up

[ ] Sean needs access to Zoom spreadsheet
[ ] Add text to Radical Collaboration page

Include something to the effect of: we can't be successful without you, we need you to help in the following ways

[ ] Add Bruce to the 1password
[ ] Confirm the copy quality on Radical Collaboration
[ ] Discuss "Quieting notifications for MVP": People have a hard time managing the project with too many notifications regarding issues
[ ] Discuss with VRMS and David about how we want to work with Democracy Lab and how to handle splitting up into different log-ins / managing messages

On-boarding issue created #1180

[ ] Added new wiki page https://github.com/civictechindex/CTI-website-frontend/wiki/Add-new-FB-admin

add t o next meeting https://github.com/civictechindex/CTI-website-frontend/issues/879

#818

We need to talk about this at next meeting https://github.com/civictechindex/CTI-website-frontend/issues/879

#875 Is this no longer relevant

Need a Marketing Manager #1212

[ ] Need a Marketing Manager #1212
[ ] What are our launch requirements?

Organizations page needs to be finalized
Do we need to do calls with all of the big organizations and if so should we start scheduling them soon while we have Bonnie available?
Are other pages "launch-ready"
Going over the site currently

[ ] #818

Besides adding GitHub IDs what else needs to be done

[ ] Levi's notes are on our drive and can be found in the folder '09 Team Transition'

Confirm if these are the notes we needed so we could be ready for launch or if Bonnie was thinking of another document

[ ] Implementation of active inactive states and changes that need to be made #1076

We do not save data about organizations and individual repos being active meaning that displaying active or inactive states on the Civic Tech Organizations page requires a new database and a new script that scrapes our site by
Store Repo Activity as Active vs Inactive and date updated

We are okay with the information not being up to date to the day, as long as it is active within our definition (6 months)

Develop a scheduler to make API calls and check if organizations and/or repos are active
Our definition of 'Active Org' is at least 1 repo active meaning there is redundancy

[ ] Active and Inactive states are tightly defined making an In-active org but active repo unlikely

Define when is an organization an inactive organization but active repo (assumption is when their organization no longer exists but there are individual contributors adding to repos)
Discuss how much complexity we want to introduce with scraping sites to know if an organization is active

Can this be a post-MVP issue?


Added isolatedElement as parameter to scroll functions / event handlers to prevent multiple scroll elements from firing

With multiple scroll elements on same page, broadcasting scroll events will cause all scrolls to change

Thanks. Can you please make a short working example so I understand the requirement better. I wonder if it's cleaner to use the already existing id feature here. At configuration time you would set the scrollable's id and you would use the same id when sending events. Each scrollable would filter events and only process those events directed to it's own id.


New PE for Synapse workspace

@raunakjhawar : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Command usage does not display sub command arguments

Command arguments for sub-commands do not display at all in the help message when a user types in a sub-command without the required arguments. A detailed explanation can be found below.
Command /main has a sub-command set. The sub-command set has a required argument, called arg1. Running /main set, without submitting the required argument, displays an unhelpful usage message: Usage: /main set. It fails to display the required argument, arg1 in the usage message.
The command was created by implementing the CommandExecutor and registering a `CommandSpec.

Can you show your code for the relevant CommandSpecs?

I think this is actually an API issue, so should be filed there.
To explain: the issue isn't anything to do with the specific CommandSpec @Flibio wrote, so it would be unnecessary to see his code. I see it too with the child commands I've been writing. It's to do with what happens when parsing arguments on child commands built up by a CommandSpec throw an exception. Specifically, if this line throws an exception when parsing the child arguemnts, it bubbles up to here on the base command, and the command calling method only sees an exception that could have come from anywhere in the command path, not that it came from the specific subcommand, so it just shows the usage of the parent command.
Not sure what the best solution is, unfortunately (I had a look a little while ago) - but I figured I'd at least explain the problem... never thought to report it though!

Moved to https://github.com/SpongePowered/SpongeCommon/issues/622


feat: support custom response headers on images served via IPX

Summary
Adds support for custom response headers to be added to images served with IPX
Test plan

Visit this page
Inspect the requests for images in the developer tools console (network tab, look for the ones that begin with ?url)
should see 'x-test: foobar' in the response headers

Relevant links (GitHub issues, Notion docs, etc.) or a picture of cute animal
https://github.com/netlify/netlify-ipx/pull/51
https://github.com/netlify/pod-ecosystem-frameworks/issues/148

Standard checks:

[ ] Check the Deploy Preview's Demo site for your PR's functionality
[ ] Add docs when necessary

🧪 Once merged, make sure to update the version if needed and that it was published correctly.

I'm looking at the request of e.g. https://deploy-preview-1515--netlify-plugin-nextjs-demo.netlify.app/_next/image/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fnetlify%2Fnetlify-plugin-nextjs%2Fmain%2Fnext-on-netlify.png&w=640&q=75, but there is no x-test: foobar header.
General
Request URL: https://deploy-preview-1515--netlify-plugin-nextjs-demo.netlify.app/_next/image/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fnetlify%2Fnetlify-plugin-nextjs%2Fmain%2Fnext-on-netlify.png&w=640&q=75
Request Method: GET
Status Code: 304
Remote Address: <IP_ADDRESS>:443
Referrer Policy: strict-origin-when-cross-origin

Response Headers
cache-control: public, max-age=0, must-revalidate
date: Thu, 11 Aug 2022 21:41:19 GMT
etag: "5e-dKUfCdzmICNqFxWPc06PHLoeigM"
server: Netlify
strict-transport-security: max-age=31536000; includeSubDomains; preload
vary: Accept-Encoding
x-nf-request-id: 01GA7DNJ67R10AR7AYFP7YHCFD

Request Headers
:authority: deploy-preview-1515--netlify-plugin-nextjs-demo.netlify.app
:method: GET
:path: /_next/image/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fnetlify%2Fnetlify-plugin-nextjs%2Fmain%2Fnext-on-netlify.png&w=640&q=75
:scheme: https
accept: image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9
dnt: 1
if-none-match: "5e-dKUfCdzmICNqFxWPc06PHLoeigM"
referer: https://deploy-preview-1515--netlify-plugin-nextjs-demo.netlify.app/old/image/
sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="104"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "macOS"
sec-fetch-dest: image
sec-fetch-mode: no-cors
sec-fetch-site: same-origin
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.81 Safari/537.36

@nickytonline That's a 304 Not Modified response though, so you wouldn't expect it to have all the same headers. Try the request without the cache and check the headers for a 200 response. It looks good to me:

@nickytonline That's a 304 Not Modified response though, so you wouldn't expect it to have all the same headers. Try the request without the cache and check the headers for a 200 response. It looks good to me:

Argh. I switched to Arc browser the other day and forgot to change my dev tool settings to disable cache. Thanks @ascorbic!

I think Kodiak should be able to resolve these conflicts if you set automerge.


[Fix] fix "exports" for node 13.0-13.6 take 2

Followup to #41.
Sorry about the churn!

Thanks!

unassert 2.0.2 is out. Thanks again!
https://github.com/unassert-js/unassert/blob/master/CHANGELOG.md#202-2023-04-20

Thank you!!


laravel 5 support?

Plans?

I definitely plan to - last time I tried to get the workspace working properly it wasn't working.  I'll see if I can work on the upgrade in the next week or so.

Hey awjudd, any progress on this?
If i had a spare hour or two, I'd try to make it L5-ready. Sadly that time hasn't presented itself yet

Sadly I've run into a similar lack of time.  I will try to do this within the next week.

On Mar 12, 2015, at 1:20 PM, Luke Edwards<EMAIL_ADDRESS>wrote:
Hey awjudd, any progress on this?
If i had a spare hour or two, I'd try to make it L5-ready. Sadly that time hasn't presented itself yet
—
Reply to this email directly or view it on GitHub.

No rush on my end

Thanks, good work!

Awesome Thanks :)


No Teams camera filters for Document, Whiteboard, etc

When taking a picture from within the Teams Android App, the camera used is the default application on my LG G2 and does not provide the typical filters/modes.  In the Outlook app I am given options for Document and Whiteboard.  In the OneNote app I am given options for Document, Whiteboard, and Business Card.
I have tried uninstalling/reinstalling as well as manually removing/adding phone permissions with no luck.
I am submitting this issue based on what I saw of the Teams camera function at Ignite 2018.  It's possible that these features are still rolling out and not yet in GA (but I couldn't find anything for it in the roadmap)  Please advise if this is expected behavior at this time or in fact a bug.
Thanks!
Andrew

This is not the place for such questions -- this is the place to ask questions about the developer documentation - but I checked for you anyway.
Office Lens integration for Android hasn't yet been released but it should appear in the next few weeks. It's already in iOS - not sure what was demo'ed at Ignite, but since that's further along perhaps that's what you saw.


Suggest what to do when dependency isn't found?

When a new user gets this error, it's not clear what to do. I wonder if we can help the new user recover from this error. For example, we don't mention pubspec.yaml in this error, so they user can't jump from this error to a way to solve the problem, unless they already understand there is a pubspec.yaml and what it does for the project. Which new users won't know that :)
One idea: add some text that points the user to the pubspec.yaml for this project, and ask them to review the paths.
For example, if we detect "error code 69", we can say:
"Try opening pubspec.yaml and verify the paths to your dependencies."

As for me it would be better to have a single option (eg. help for beginners) which can turn on/off all the educable helpers (messages, hints, helper dialogs etc).


Minor fixes in infos-list with alias display (touchable area, icon, tune)

Description
The goal of this PR is to fix minor issues in infos-list with alias display:

whole row as touchable area
chevron icon
tune when coming back from info list

Changes include

[x] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 35.76%. Comparing base (afadb33) to head (f21ade2).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #813   +/-   ##
=======================================
  Coverage   35.76%   35.76%
=======================================
  Files          13       13
  Lines        1591     1591
=======================================
  Hits          569      569
  Misses       1022     1022

Flag
Coverage Δ

unittests
35.76% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

tested --> on speculos & Flex --> 🟢


proto2 required support

The required syntax of proto2 is now optional in the generated type, is there any way to make it required?
syntax = "proto2";

message Foo {
  required string a = 1;
  required string b = 2;
}

// @generated by protoc-gen-es v1.0.0 with parameter "target=ts"
// @generated from file foo.proto (syntax proto2)
/* eslint-disable */
// @ts-nocheck

import type { BinaryReadOptions, FieldList, JsonReadOptions, JsonValue, PartialMessage, PlainMessage } from "@bufbuild/protobuf";
import { Message, proto2 } from "@bufbuild/protobuf";

/**
 * @generated from message Foo
 */
export class Foo extends Message<Foo> {
  /**
   * @generated from field: required string a = 1;
   */
  a?: string;

  /**
   * @generated from field: required string b = 2;
   */
  b?: string;

  constructor(data?: PartialMessage<Foo>) {
    super();
    proto2.util.initPartial(data, this);
  }

  static readonly runtime = proto2;
  static readonly typeName = "Foo";
  static readonly fields: FieldList = proto2.util.newFieldList(() => [
    { no: 1, name: "a", kind: "scalar", T: 9 /* ScalarType.STRING */ },
    { no: 2, name: "b", kind: "scalar", T: 9 /* ScalarType.STRING */ },
  ]);

  static fromBinary(bytes: Uint8Array, options?: Partial<BinaryReadOptions>): Foo {
    return new Foo().fromBinary(bytes, options);
  }

  static fromJson(jsonValue: JsonValue, options?: Partial<JsonReadOptions>): Foo {
    return new Foo().fromJson(jsonValue, options);
  }

  static fromJsonString(jsonString: string, options?: Partial<JsonReadOptions>): Foo {
    return new Foo().fromJsonString(jsonString, options);
  }

  static equals(a: Foo | PlainMessage<Foo> | undefined, b: Foo | PlainMessage<Foo> | undefined): boolean {
    return proto2.util.equals(Foo, a, b);
  }
}

We agree that this would be nice for type-safety, but it means we have to make properties mandatory in the constructor, something we would prefer to avoid. We haven't found the best way forward yet for this conundrum, so for the time being, proto2 required properties are typed as optional, but will raise an error at runtime when serializing, following the pattern of other implementations.
Thank you for raising this issue though. It is very possible that we'll be making some changes for better support in of proto2 required in the not-so-distant future, so we're happy to keep this open.

What are the cons of mandatory properties in the constructor or using a builder pattern?
On the other hand, there are clear benefits of not having to check fields for "undefined" that are supposed to be required in the schema.

It appears that the behavior has changed since this issue was filed.  The generated classes for proto2 message seem to reflect the required/optional fields.  See below.
That being said, some imported messages (e.g. Timestamp is required in the message but optional in the class) do not seem to generate correctly.
Proto Message (sample)
syntax = "proto2";

package event_logs.v1;

import "google/protobuf/timestamp.proto";

enum FlowStateChange {
  FLOW_STATE_CHANGE_UNSPECIFIED = 0;
  FLOW_STATE_CHANGE_STARTED = 1;
  FLOW_STATE_CHANGE_STOPPED = 2;
  FLOW_STATE_CHANGE_FINISHED = 3;
  FLOW_STATE_CHANGE_RESET = 4;
}

message FlowStateChangeEvent {
  required uint32 workspace = 1;
  required uint32 environment = 2;
  optional uint32 group = 3;
  required uint32 user = 4;
  required uint32 flow = 5;
  required uint32 version = 6;
  required FlowStateChange state = 7;
  required bool value = 8;
  required google.protobuf.Timestamp timestamp = 9;
}

Generated Class
/**
 * @generated from message event_logs.v1.FlowStateChangeEvent
 */
export declare class FlowStateChangeEvent extends Message<FlowStateChangeEvent> {
  /**
   * @generated from field: required uint32 workspace = 1;
   */
  workspace: number;

  /**
   * @generated from field: required uint32 environment = 2;
   */
  environment: number;

  /**
   * @generated from field: optional uint32 group = 3;
   */
  group?: number;

  /**
   * @generated from field: required uint32 user = 4;
   */
  user: number;

  /**
   * @generated from field: required uint32 flow = 5;
   */
  flow: number;

  /**
   * @generated from field: required uint32 version = 6;
   */
  version: number;

  /**
   * @generated from field: required event_logs.v1.FlowStateChange state = 7;
   */
  state: FlowStateChange;

  /**
   * @generated from field: required bool value = 8;
   */
  value: boolean;

  /**
   * @generated from field: required google.protobuf.Timestamp timestamp = 9;
   */
  timestamp?: Timestamp;

  constructor(data?: PartialMessage<FlowStateChangeEvent>);

  static readonly runtime: typeof proto2;
  static readonly typeName = "event_logs.v1.FlowStateChangeEvent";
  static readonly fields: FieldList;

  static fromBinary(bytes: Uint8Array, options?: Partial<BinaryReadOptions>): FlowStateChangeEvent;

  static fromJson(jsonValue: JsonValue, options?: Partial<JsonReadOptions>): FlowStateChangeEvent;

  static fromJsonString(jsonString: string, options?: Partial<JsonReadOptions>): FlowStateChangeEvent;

  static equals(a: FlowStateChangeEvent | PlainMessage<FlowStateChangeEvent> | undefined, b: FlowStateChangeEvent | PlainMessage<FlowStateChangeEvent> | undefined): boolean;
}

The behavior has changed since this issue was filed. The generated classes for proto2 messages seem to reflect the required/optional fields. See below.

@joemckenney, this was actually a bug :scream:, fixed in v1.7.2.
To support editions, we're working on better support for field presence, and plan to update the logic for proto2 first. I'll keep this issue updated.

@timostamm @joemckenney I cannot reproduce the generated class FlowStateChangeEvent with "@bufbuild/protoc-gen-es": "^1.7.2".
Here are the commands I use :
SED := `which gsed 2>/dev/null || which sed`
TS_SRC_DIR := "src"
TS_DIST_DIR := "dist"

default:
    just --list

build: _init_dist _build-es-pb _build-es-connect
    tsc -b

clean:
    rm -rf dist

_init_dist:
    mkdir -p "{{TS_DIST_DIR}}"

_build-es-pb target="showhost.proto":
    protoc -I . \
        --es_out "{{TS_DIST_DIR}}" \
        --es_opt target=js+dts \
        --es_opt import_extension=none \
        "{{target}}"

_build-es-connect target="showhost.proto":
    protoc -I . \
        --connect-es_out "{{TS_DIST_DIR}}" \
        --connect-es_opt target=js+dts \
        --connect-es_opt import_extension=none \
        "{{target}}"

Here is my package.json :
{
    "private": true,
    "name": "@showhost/transport",
    "main": "src/index.ts",
    "types": "src/index.ts",
    "version": "0.1.0",
    "scripts": {
        "build": "just build",
        "clean": "just clean"
    },
    "files": [
        "dist"
    ],
    "exports": {
        ".": "./dist/index.js",
        "./*": "./dist/*.js"
    },
    "devDependencies": {
        "@bufbuild/protoc-gen-es": "^1.7.2",
        "@connectrpc/protoc-gen-connect-es": "^1.3.0"
    },
    "dependencies": {
        "@bufbuild/protobuf": "^1.7.2",
        "@connectrpc/connect": "^1.3.0",
        "@connectrpc/connect-web": "^1.3.0"
    }
}

And here is the (partial) output I get :
/**
 * @generated from message xyz.volgar1x.showhost.FlowStateChangeEvent
 */
export declare class FlowStateChangeEvent extends Message<FlowStateChangeEvent> {
  /**
   * @generated from field: required uint32 workspace = 1;
   */
  workspace?: number;

  /**
   * @generated from field: required uint32 environment = 2;
   */
  environment?: number;

  /**
   * @generated from field: optional uint32 group = 3;
   */
  group?: number;

  /**
   * @generated from field: required uint32 user = 4;
   */
  user?: number;

  /**
   * @generated from field: required uint32 flow = 5;
   */
  flow?: number;

  /**
   * @generated from field: required uint32 version = 6;
   */
  version?: number;

  /**
   * @generated from field: required xyz.volgar1x.showhost.FlowStateChange state = 7;
   */
  state?: FlowStateChange;

  /**
   * @generated from field: required bool value = 8;
   */
  value?: boolean;

  /**
   * @generated from field: required google.protobuf.Timestamp timestamp = 9;
   */
  timestamp?: Timestamp;

  constructor(data?: PartialMessage<FlowStateChangeEvent>);

  static readonly runtime: typeof proto2;
  static readonly typeName = "xyz.volgar1x.showhost.FlowStateChangeEvent";
  static readonly fields: FieldList;

  static fromBinary(bytes: Uint8Array, options?: Partial<BinaryReadOptions>): FlowStateChangeEvent;

  static fromJson(jsonValue: JsonValue, options?: Partial<JsonReadOptions>): FlowStateChangeEvent;

  static fromJsonString(jsonString: string, options?: Partial<JsonReadOptions>): FlowStateChangeEvent;

  static equals(a: FlowStateChangeEvent | PlainMessage<FlowStateChangeEvent> | undefined, b: FlowStateChangeEvent | PlainMessage<FlowStateChangeEvent> | undefined): boolean;
}

Do you have the right command invocation notation?

Hello,
We would like to generate types from protobuf definition that would look like this:
export type RequiredObject = {
  absolutelyRequired: string;
};

export type Request = {
  obj: RequiredObject;
  something?: [],
};

We have tried this:
syntax = "proto2";
package some_package;

message RequiredObject {
    required string absolutely_required = 1;
}
message OptionalArray {
    repeated string values = 1;
}

message Request {
    required RequiredObject obj = 1;
    optional OptionalArray something = 2;
}

and based on description of v2 alpha release https://github.com/bufbuild/protobuf-es/pull/801 expected to get something like
export type RequiredObject = {
  absolutelyRequired: string;
};

export type OptionalArray = {
  values: string[];
};

export type Request = {
  obj: RequiredObject;
  something?: OptionalArray,
};

but in generated type RequiredObject obj is still optional.
Is this in the works?

Apologies for the confusion. I've updated the v2 release notes to clarify that it's an improvement over v1. Required scalar and enum fields are no longer optional in generated code, but this does not apply to message fields. This would need changes that impact the entire API, see https://github.com/bufbuild/protobuf-es/issues/532#issuecomment-2214372913.
I've been working with JSON and TypeScript for a long time, and I understand the desire to have non-optional properties. Realistically though, the required keyword is not the right solution. It's a legacy feature, and the official language guide states: Do not use. It's also not available in proto3, and while it's available in edition 2023, it's likely to be removed in a future edition.
From my understanding, the important bit is avoiding the nullish-coalescing operator and checking for undefined for cases where the API guarantees that a message is present (also see #532). This can potentially be solved by an implementation of protovalidate for TypeScript that ties into the type system. We can't make promises yet, but it looks promising.

The Google's recomendation is relevant for cases where the developer doesn't fully control both sides the use the same proto message, for example, one side is a phone app that can't be forcibly updated.
However, there are plenty of other use-cases where the developer has full control, for example, when using web workers, Electron processes, etc. For these cases a fast, built-in, fitting into the Typescript semantics "required" validation could be better than using a "protovalidate" or other post-processing solution, that would add complexity and latency.

Certainly. But would you want to be stuck with a no longer maintained proto2 down the road? Do you think that switching to getters or immutable is the right call for general use?
Protobuf-ES v2 is just descriptors and functions. For specific use cases like private IPC, you can easily wrap fromBinary and return a custom generated or even just a mapped type, based on a simple custom option.

I imagine for the private IPC use-case people (who like protobufs) are evaluting different libraries for various criteria, including the amount of extra work and maintenance they have to do. From this perspective having to do a separate codegen themselves seems to be a big drawback, it would be simpler to pick another library.
on the proto2 vs. proto3 topic: In my understanding various Typescript proto2 libraries are still well maintained, including protobuf-es. The proto2 spec has been battle-tested for years, not sure if it requires any maintenance. I personally think that proto2 schema is better than proto3, in particular around "required" and "has" semantics.
For https://github.com/bufbuild/protobuf-es/issues/532#issuecomment-2214372913, I don't have enough data to have a strong opinion. Naively I'd say that enforcing immutability would be too much of a burden for the JS/TS users and they would switch to a different library. As a data point, in the official Java codegen, if I remember correctly, (for builders, which are essentially mutable messages) they create an mutable object and cache it inside. This mostly worked but created unpredictable memory and performance patterns, which were noticeable in some rare cases.

would love to see better required support as well.

But would you want to be stuck with a no longer maintained proto2 down the road

Google opted to support proto2 "pretty much forever" due to their own dependency internally on proto2 specific features.

And yet, Google also has plans to "deprecate/remove required field presence": https://github.com/protocolbuffers/protobuf/commit/0b6e768f07c4cde376783b964022ec7e1ff3e772

sure, in editions, right?
This doesn't contradict proto2 syntax being supported for the foreseeable future though.

I'm not sure.  We plan to add *Valid types, similar to JSON types, which will honor protovalidate standard constraints such as (buf.validate.field).required = true. Tracked in https://github.com/bufbuild/protobuf-es/issues/966. This implements required semantics at a different level, as suggested here in the language guide.
It should be possible to use these types for construction and RPC in a flexible way, maybe also with a no-op validator if you trust the source. And I don't see why we couldn't also honor proto2 required and the LEGACY_REQUIRED feature.


PDF.js throws error in Visual Studio 2013 Asp.Net MVC Project

I receive the following error when I run my project:
Unhandled exception at line 9529, column 5 in http://localhost/SSQV4/SSQV5/Scripts/pdf.js
0x800a138f - JavaScript runtime error: Unable to get property 'src' of undefined or null reference
and it stops at the following line in the pdf.js file:
var pdfJsSrc = document.currentScript.src;
Nuget would not add pdf.js in VS 2013 so I had to add pdf.js and the worker files manually.

For IE, add web/compatibility.js or use new version. Closing as dup of #7216

I have compatibility.js, but I still get that error.  Am I missing something else?

You did not provide enough information to reproduce the issue on the computer other than yours. Please provide all information requested by https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md . See also https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md .

Browers: IE 11
Operating System: Windows 7 Ultimate
Pdf,js version 1.3.31
Steps to Reproduce:
I add pdf.js.. pdf.worker.js and compatability.js to my project.  I added script tags to pdf.js and compatability.js to my layout page.  I ran the project in debug mode, and the error happens.  It does NOT happened in Chrome, only IE.

Could you provide a link to your project (e.g., on JSBin or a custom server for example) so we can try to reproduce the issue?

I copied the source file that you have on Git Hub now as I noticed it was different from the one that downloads in your zip file.  The error is no longer occurring.  Thank you for your help!

I copied the source file that you have on Git Hub now as I noticed it was different from the one that downloads in your zip file.

Please explain: which zip and js files you are referring too?

I clicked Download.Zip on the Code page and I received an older version of pdf.js.  I received version 1.3.91.  It is not the same as what shows in the src folder here.

I see. You cannot use non-built source code of PDF.js in the production. As a user, you shall only download code listed in the released.


Add dodsrc and urs cookies files when creating netrc

This PR includes code that will also create a .urs_cookies and .dodsrc files when users persist their credentials to a .netrc file, and will copy the .dodsrc file based on the user operating system. It is based on code from this how-to, but adapted here to use pathlib: https://disc.gsfc.nasa.gov/information/howto?keywords=prerequisite&title=How to Generate Earthdata Prerequisite Files
I have tested this with poetry on both Linux/Windows, and it works great!

📚 Documentation preview 📚: https://earthaccess--492.org.readthedocs.build/en/492/

Thank you for the reviewing and the suggestions @jhkennedy ! I added the suggested commits here. In terms of overwriting the existing dodsrc file, for Windows environments, you need to have additional copies of the dodsrc file in each working directory even if it exists in the root user folder. I'm not sure how long the information in the urs_cookies file is valid for, but I have not had any issues when overwriting it repeatedly, and this file is necessary for those who want to use wget/curl, so I have included it here for convenience.

Woops! bad indent in my suggestion

Woops! bad indent in my suggestion

No worries! Fixed them.


Documentation question

@martinghunt , the README mentions both dl_and_run and --run_accession - do both exist still?
Z

Yes. --run_accession is for processing one run.
dl_and_run is for processing a batch of runs.


Support GPU on SLES

Fixes #349
[LISAv2 Test Results Summary]
Test Run On           : 07/01/2019 07:37:02
ARM Image Under Test  : SUSE : SLES : 15 : Latest
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:12

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 GPU                  NVIDIA-CUDA-DRIVER-VALIDATION                                                     PASS                 7.59
	Using nVidia driver : CUDA
	lsvmbus: Expected "PCI Express pass-through" count: 1, count inside the VM: 1 : PASS
	lspci: Expected "3D controller: NVIDIA Corporation" count: 1, found inside the VM: 1 : PASS
	lshw: Expected Display adapters: 1, total adapters found in VM: 1 : PASS
	nvidia-smi: Expected GPU count: 1, found inside the VM: 0 : FAIL

@LiliDeng  @v-sijliu have you confirmed that SLES is indeed supported in Azure? And that the Azure documentation has to be update to also include SLES?

@chvalean Ava made a mistake here, need further investigation.
nvidia-smi: Expected GPU count: 1, found inside the VM: 0 : FAIL

Close this one, will submit new one once get further progress.

@chvalean Ava made a mistake here, need further investigation.
nvidia-smi: Expected GPU count: 1, found inside the VM: 0 : FAIL

This is what I see today and request to skip SLES 15. @v-sijliu @LiliDeng ok with it?


I have a problem. The generated file is incomplete

When I use node to run 'CRX = > CRX. Pack(); fs. WriteFile ("xpd",crxBuffer)', the content of the CRX file is not complete, but it is complete when I use the CMD command 'CRX pack - O xxx'. . I want to know how to solve it. I look forward to your reply.Thanks.

I solved the problem through your reply, sincere thanks


run specific tests via command line

Makes this work:
testling test/foo.js

If all the files provided do not end in .js, then it just uses the old way...
This is very handy for when attempting to diagnose specific failures in a large test suite.

@dominictarr would you mind checking "allow edits" on the RHS of this PR?


Wave in Footer

I had added this wave in footer and i would like to make a PR for this

Yeah @arpit456jain

ok making the PR


Add support for bitlbee-discord. Use docker layers to speed up building.

I was using bitlbee-discord and wanted to have a docker which supported it, looks like this is the closest to it I could come, so I added support for it.
Created a PR in your direction just in case you thought it might be useful for this repo as well.
I got rid of the build.sh because it made sure none of the steps could be cached while building and testing.

I may have deviated too far from your original repo (with telegram and libpurple), feel free to just close this PR if this is not interesting.


Upgraded Gradle wrapper from 2.11 to 2.12

I agree with this change, but it'll probably need to be tested with SpongeGradle, ForgeGradle and MixinGradle

@me4502 is a successful build (currently running) not sufficient? How do you test it with SpongeGradle, ForgeGradle and MixinGradle?

Closing for the same reason as https://github.com/SpongePowered/SpongeVanilla/pull/232


FEATURE_PROD_DEVTOOLS is not defined - when Vue is externalized

Version
4.0.4
Reproduction link
https://github.com/vuejs/vue-router-next
The result of the steps below for reference
Steps to reproduce

Add externals: { vue: 'Vue' }, to the webpack.config.js in this repo
Run the build:playground script
Add the vue.runtime.global.prod.js build to the index.html in the playground_dist folder [0], before the bundle.js script
Serve the playground_dist folder
Observe the reported error

[0] - e.g.       <script<EMAIL_ADDRESS>Optional: Fix the broken npm scripts by putting a space instead of a . in env.prod?
What is expected?
__FEATURE_PROD_DEVTOOLS__ should have a typeof guard or be shaken out
or
For this to be documented as a flag that should be defined in one's build tool. :)
What is actually happening?
An undefined variable error

The steps to reproduce seem unrealistic to me. The build is working with existing configs because the variable is required by Vue itself and therefore configured. If you were bundling Vue as well (instead of using it as an external), you will need the same configuration.
There is a warning in vue's featureFlags.ts that points you to https://github.com/vuejs/vue-next/tree/master/packages/vue#bundler-build-feature-flags. I think this is worth adding to Vue docs somewhere to mention feature flags. Can you open an issue in docs-next?
In practice, it doesn't make sense to bundle vue-router but not vue so I don't think that warning is worth duplicating.

Optional: Fix the broken npm scripts by putting a space instead of a . in env.prod?

I don't understand, there is no such file.

@posva - the "Optional" refers to package.json scripts:
    "build:playground": "webpack --env.prod",
    "build:e2e": "webpack --env.prod --config e2e/webpack.config.js",

Those commands fail
[webpack-cli] Error: Unknown option '--env.prod'

Could you clarify, you don't think it's realistic to externalize Vue but not Vue Router?
If one is always externalizing Vue, this variable would never need to be set, and introducing Vue Router would then suddenly require defining this string.


Hide scrollbar

Is there any props that I can set to disable both vertical and horizontal scroll indicator?, I could not find it in the doc

Solved by add this to ThemeData
scrollbarTheme: const ScrollbarThemeData().copyWith(
      thumbColor: MaterialStateProperty.all(Colors.transparent),
      thickness: const MaterialStatePropertyAll(0),
    ),


typo: Double word "the"

@nschonni : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.

Verified editorial correction.


Can other conditions be used as control signals?

Thank you for such excellent work. I am very interested in your work.
Can other control conditions (semantic segmentation maps, sketches, etc.) be used as control images?
I am a little confused. Most of the research work claiming to be controllable focuses more on edge/canny maps and depth maps, and few studies focus on semantic segmentation maps and sketches (in the generative models of sdxl and Flux versions). Is it because the result is not good or there is little demand?

This is a good question. While we haven't trained the model on other control conditions such as segmentation maps and sketches, we believe OmniControl could potentially handle these tasks.
Regarding why most research works (including our OminiControl) focus on canny edge-to-image tasks -- we think it's primarily because canny edges provide a straightforward way to demonstrate a method's capability for condition controlling. Since it's relatively easy to extract canny edges from target images, this makes it convenient for implementation and experimental validation.

Thanks for your reply.
I am currently concentrating on achieving precise alignment in image generation using sparse guidance conditions, such as semantic segmentation maps and sketches.
Your work has provided me with new inspiration. I look forward to exploring more of your research and hope for the opportunity to engage in further discussions with you😊

Thank you for your interest! Feel free to reach out anytime for discussion.


Are there any plans to replace the deprecated MKPinAnnotationView for a new AnnotationView on iOS?

Summary
Currently the pins displayed on the map don't match the typical native pins normally displayed on an iOS app. Since MKPinAnnotationView was deprecated, the typical pin used is MKMarkerAnnotationView. I know that it's working fine now, but it will have to be updated at some point.
Reproducible sample code
import { StyleSheet, Text, View } from 'react-native';
import MapView, { Marker } from 'react-native-maps'
import * as Location from 'expo-location'
import React from 'react'
import { useState, useEffect, useCallback, useRef } from 'react';

export default function App() {
  const mapView = useRef<MapView | null>(null);
  const markers = [{lat: 29, lng: -95, name: 'test'}]

  return (
    <View style={styles.container}>
      <MapView style={styles.map} ref={mapView}>
        {markers.map((marker, index) => (
          <Marker
          key={index}
          coordinate={{latitude: marker.lat, longitude: marker.lng}}
          title={marker.name}
          description='This is a test'
          />
        ))}
      </MapView>
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    backgroundColor: '#fff',
    alignItems: 'center',
    justifyContent: 'center',
  },
  map: {
    width: '100%',
    height: '100%'
  }
});

Steps to reproduce

Run the code above
Zoom out until you can see the pin
The pin will be the old style MKPinAnnotationView

Expected result
The library should be updated to not include the old deprecated class
Actual result
The library uses the deprecated class MKPinAnnotationView
React Native Maps Version
1.10.3
What platforms are you seeing the problem on?
iOS (Apple Maps)
React Native Version
0.73.4
What version of Expo are you using?
SDK 48
Device(s)
iPhone Simulator
Additional information
Using expo SDK v50.0.8

Hi, thanks for letting us know. If you can please add a comment on the https://github.com/react-native-maps/react-native-maps/discussions/4975 discussion then we'll plan accordingly. I'm closing the issue as it's not a bug report


Pin ffmpeg 4.4 for the right package

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@h-vetinari
This should be merge after https://github.com/conda-forge/ffmpeg-feedstock/pull/214 is merge
This will allow the HPP stack to be build properly with the dependence on OSG and ffmpeg 4.4 allowing more recent assimp and libbost:

https://github.com/conda-forge/gepetto-viewer-feedstock/pull/38

After we need to migrate regarding assimp and liboost the packages:

https://github.com/conda-forge/openscenegraph-osgqt-feedstock
https://github.com/conda-forge/gepetto-viewer-feedstock
https://github.com/conda-forge/gepetto-viewer-corba-feedstock
https://github.com/conda-forge/hpp-gepetto-viewer-feedstock
https://github.com/conda-forge/hpp-gui-feedstock

And then we can merge the last HPP stack packages without pinning : https://github.com/conda-forge/staged-recipes/pull/24134

I see that this is the package that has the CDTs.
can you please make one attempt here to remove the dependency on CDTs?

@conda-forge-admin, please rerender

Thanks @ymontmarin ! I think that if you like you can also add yourself as a maintainer of the recipe.

Thanks @ymontmarin ! I think that if you like you can also add yourself as a maintainer of the recipe.

Sorry, you already did this, I missed it.

Please leave no CDTs other than the ones that you see in the latest recipe of qt-main.
https://github.com/conda-forge/qt-main-feedstock/blob/main/recipe/meta.yaml

@conda-forge-admin, please rerender

ok. let's hope this works

@hmaarrfk Just to let you know that this recipe works :) I am going to continue the cdt change on the downstream package, and then we will be able to merge the end of the hpp stack

glad to hear it


3D Color Wave

Can't see anything.
http://scratch.mit.edu/projects/104579798/
http://phosphorus.github.io/#104579798
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36

block set pen shade to is the problem here...


Contributing test-cases for NSOperation/NSOperationQueue.

The test is correct and exposed a real bug in the underlying concurrency code that is fixed by #621.
This PR is not needed now and can be closed.


Run on arbitary video

Hi, I want to run SmoothNet on an arbitary video, but it seems like a ground truth for that video is required even for the inference phase, right?

Hi @LeKiet258 ! Thank you for your focus.
Ground truth is not needed for inference, however, you might need to process your own data following instructions here. You can directly leave gt value as 0 if you don't have them. If you want to run inference with visualization, you can also refer to mmhuman3d, which support smoothnet.

Thanks for your fast reply! MMHuman3d currently doesn't support my model of choice yet, which is HybrIK, so I have to respectively clone HybrIK to produce the output and then run SmoothNet on this output, hence my question. As for the gt value set to 0, did you mean by setting the pose and shape parameters ? (in my case, I use SMPL body representation)

Thanks for your fast reply! MMHuman3d currently doesn't support my model of choice, which is HybrIK yet, so I have to clone HybrIK to produce the output and then run SmoothNet on this output respectively, hence my question. As for the gt value set to 0, did you mean

In this repo, we have not provide inference pipeline. So you can use the evaluation pipeline for testing. Due to the evaluation process need ground truth to calculate metrics, we recommend to add groundtruth in data processing. However, for the reason that you only need the inference part, you can set the ground truth value to any random value (e.g., 0). But you may still need to modify the code to obtain the smoothed output pose from the whole pipeline.

Hi @nick008a ,
Thanks for the kind suggestion! We will add it in March.

@nick008a I haven't successfully combined HybrIK with SmoothNet yet, so I changed HybrIK with another model in order to run. Sorry :(

@LeKiet258 @nick008a @ailingzengzzz  I have a simillar question, from the code provided on 2d, the dataset preparing for evaluation actually used a middle postiion data as normalization reference: https://github.com/cure-lab/SmoothNet/blob/be3f9ce43399aa7c6c3c5400f2d5fdcfd958cfc4/lib/dataset/h36m_dataset.py#L164
how to do that in realtime situation say I have 16 length only? And noticed it normalized with a Magic number H36M_IMageshape which is 1000, but when keypoints detected on arbitary videos, the image shapes can be various, does it matter or not?

Hi @lucasjinreal ,
I'm sorry for the late reply. I check this version and find I did not present the general normalization. Here you can use the following functions to normalize with arbitrary videos and input the normalized keypoint positions into SmoothNet, and then denormalize the smoothed keypoints into the image coordinate.
def normalize_screen_coordinates(X, w, h):
    # Normalize so that [0, w] is mapped to [-1, 1], while preserving the aspect ratio
    if X.shape[-1] == 3: #input 3d pose
        X_norm = X[..., :2]
        X_norm = X_norm / w * 2 - [1, h / w]
        X_out = np.concatenate((X_norm, X[..., 2:3] / 1000), -1)
    else:
        assert X.shape[-1] == 2
        X_out = X / w * 2 - [1, h / w]
    return X_out

def image_coordinates(X, w, h):
    # Reverse camera frame normalization
    if X.shape[-1] == 3: #input 3d pose
        X_norm = X[..., :2]
        X_norm[..., :1] = (X_norm[..., :1] + 1) * w / 2
        X_norm[..., 1:2] = (X_norm[..., 1:2] + h / w) * w / 2
        X_out = torch.cat([X_norm, X[..., 2:3] * 1000], -1)
    else:
        assert X.shape[-1] == 2
        X_out = (X + [1, h / w]) * w / 2
    return X_out


when I tried to add a host to rancher, I got an excption

Describe your issue here
that is the excption's details:
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8080): Max retries exceeded with url: /v1 (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7fe41df8a810>: Failed to establish a new connection: [Errno 111] Connection refused',))
any suggestions?
best wishes

Useful
Info

Versions
Rancher v1.6.2 Cattle: v0.181.4 UI: v1.6.5

Access
localauth admin

Orchestration
Cattle

Route
hosts.new.index

You can't use localhost as the registration URL.  Localhost is always the thing it's being resolved in, i.e. the agent containeritself in this case, not the server container.

yeah, I got it! thank you very much!


staking: only disable slashed validators and keep them disabled for whole era

This PR changes the logic for disabling validators and trigger a new era. Whenever a validator commits an offence it is now tracked in the staking pallet and whenever a threshold is reached a new era is started. Only offences that led to a slash lead to the validator being disabled (e.g. if the validator is offline just by itself it is not disabled). Additionally the staking pallet makes sure that disabled validators stay disabled for the whole era.
The reason to not disable validators when there's no slash is https://github.com/paritytech/substrate/pull/9414 which will make sure that disabled validators can't author new blocks. If a validator is not slashed we can assume that the offence was not critical enough to block the validator from participating in consensus (it will be kicked from the set whenever the next era starts).
Fixes https://github.com/paritytech/polkadot/issues/2088.
polkadot companion: https://github.com/paritytech/polkadot/pull/3527

I think I've addressed all issues except bounding the disabled validators vec which I'm not sure how to do since there's no static bound right now.

@andresilva what's the plan for this?

@kianenigma Sorry, I was out for the past 2 weeks 😊 I've updated the PR with current master and added comments regarding the sorted vecs. I think I've addressed all comments from review except the usage of BoundedVec, I created https://github.com/paritytech/substrate/issues/9724 for this.

After merging this we need to make sure the polkadot companion isn't merged right away. I needed to point to a temporary beefy branch.

After talking to @kianenigma we decided to upgrade this to needsaudit since it's touching both session and staking. We'll wait until it's audited before merging.


Publish main to live, Tuesday 12/27, 10:30 AM

Learn Build status updates of commit 06eaa23:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineDialOutPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsDialoutPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


cell_motion_detection and motion_alarm are not found (Tapo C110)

Description
As the headline says.
The two (important) sensors are unknown and HA says something like "This entity is no longer provided by the Tapo Control integration. If the entity is no longer in use, delete it in the settings."
Strange thing is: It already worked... Then it went off, back again and not it's off for several days.
The sensors ARE working in the Tapo App.
Solutions? Thx!
Reproduction Steps
Constant error
Expected behavior
cell_motion_detection and motion_alarm are not found
If applicable, add error logs.
none
Device Firmware
1.0.13
Integration Version
newest
Using stream component
No
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
HASS OS
Search for similar issues
Yes
Additional information
none

Read faq in readme.

Hello, this is how it worked for me.

I did and checked everything. Webhooks is disabled in my case...
Only thing I did not really get is this point:
Make sure you have correct IP set for Home Assistant. Turn on Advanced Mode under /profile. Go to /config/network and under Network Adapter verify correct IP is shown for the device. If it is not correct, under Home Assistant URL uncheck Automatic next to Local Network and set it to http://:8123. DO NOT USE HTTPS.
Where are those options? /profile and stuff?

If it worked before and you haven't updated the camera firmware yes. Some cameras have pull point broken and you will need to get webhooks working for motion detection or wait until they fix it.

Yeah, worked and did not update.
Strange.
Thank you for your quick responses. It's frustrating because I wanna use the motion trigger for recording commands.

(Now it's working again. I don't get it.)

Same problem here with C325WB Camera
Was working before last HA Update and this integration error message see from above come up.
Deleted all cameras and re-installed and then Entity is gone.
Moved Kameras in same vlan but still no help.


adding code to dqm loading program to generate a loading report and send it to slack

@azurebrd Good catch! This section is not part of the report (the story is to report any loading errors for PubMed papers) so I commented out this section during testing, I forgot to turn it on before pulling the PR. Will do it now..
Sorry for the confusion!


[#3835] kafka plugin

Avoid creating corrupted stacks if Trace is already active.

Codecov Report

Merging #4535 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #4535      +/-   ##
==========================================
- Coverage   40.45%   40.42%   -0.03%
==========================================
  Files        2509     2509
  Lines       76356    76410      +54
  Branches    10373    10391      +18
==========================================
+ Hits        30890    30892       +2
- Misses      42629    42683      +54
+ Partials     2837     2835       -2

Impacted Files
Coverage Δ

...terceptor/ConsumerRecordEntryPointInterceptor.java
0% <0%> (ø)
:arrow_up:

...pc/server/LoggingServerMessageListenerFactory.java
90% <0%> (-10%)
:arrow_down:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
19.76% <0%> (+1.16%)
:arrow_up:

...pinpoint/profiler/instrument/AccessorAnalyzer.java
65.71% <0%> (+8.57%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5fa7e4d...48cc9e6. Read the comment docs.


V5X Ethernet Startup needs to be done on separate thread ot time out

No connection pauses init thread by ~10 Sec during Auto negotiation. ~2 Seconds when connected.

Completed in Nuttx and up streamed  Prior to 8.2 https://github.com/PX4/NuttX/commit/786d3453a2f3140ceb1d24a51dbd67b3f0ad4396#diff-4cca7e21c436329c40fd5b1313e71193
Config changed to use back ground init. https://github.com/PX4/Firmware/commit/c9cb59fdd8903847c1ad8d7f70cfad4f3444115e#diff-fde570f7a5e4027436cce1f052ed721b


String no longer works as an area code

[2] pry(main)> BandwidthIris::AvailableNumber.list({ area_code: "984", quantity: 3 })
BandwidthIris::Errors::GenericError: Http code 401
from /Users/jschroeder/.rvm/gems/ruby-2.7.1/gems/ruby-bandwidth-iris-2.6.0/lib/bandwidth-iris/client.rb:141:in `check_response'

[3] pry(main)> BandwidthIris::AvailableNumber.list({ area_code: 984, quantity: 3 })
=> ["9842010293", "9842010570", "9842010668"]

This seems to be a recent change as a string was working previously in our tests.  Examples in doc use strings.

Hey @jbschrades,
I'm looking into this, but I haven't been able to replicate it both with your gem version and the latest gem version. I do know we have situations on our APIs with some http clients not following redirects properly, which could explain the 401 response, but I'm not sure if that is happening here.
Are you setting your api_endpoint in initialization?

Yes. Setting api_endpoint to https://dashboard.bandwidth.com/api.

Hmm still unable to replicate the issue, even on docker with a fresh install. This is the code I was running in my app.rb file
require 'ruby-bandwidth-iris'

BandwidthIris::Client.global_options = {
    :account_id => "<redacted>",
    :username => "<redacted>",
    :password => "<redacted>",
    :api_endpoint => "https://dashboard.bandwidth.com/api"
}

puts BandwidthIris::AvailableNumber.list({ area_code: "984", quantity: 3 })

puts BandwidthIris::AvailableNumber.list({ area_code: 984, quantity: 3 })

Output
9842010689
9842011061
9842011068
9842290508
9842086639
9842086824

Dockerfile
FROM ruby:2.7.1

COPY app.rb /app.rb

RUN ruby -v

RUN gem install ruby-bandwidth-iris -v 2.6.0

RUN ruby /app.rb

We may need to look through our logs to see if something weird is going on. Could you open up a support ticket at https://support.bandwidth.com so we can chat in private?

@jmulford-bw
I just tested this again in the console with the exact same commands from my original post and it's working now.  I'll open the support ticket if you want to investigate further.

Awesome! I'll talk to our support team to see if they want to investigate further


P109: Monotonically normal

Two new properties:

P108: Hereditarily collectionwise normal
P109: Monotonically normal

together with related theorems.  This covers most theorems proposed in #927.
I have assumed T1 as part of the property, as it is needed for the equivalence of definitions (1) and (2) of monotonic normality, and it seems to be always assumed in papers.

I've also mentioned this before in #927, where I listed some additional theorems not covered by #1005 and provided references for those theorems.

Sorry @david20000813 I didn't see that you have raised the same issue. I've closed mine.

For https://topology.pi-base.org/properties/P000109 I have added at the end a section "Meta-properties".
Mainly because I needed to state somewhere that P109 was hereditary, for some of the proofs of the theorems.
But it's an example of something easy that could be done more generally.  (We had discussed possible web development doing something more fancy at some point, with the help of not-Abram?, but that was probably too much.)
Would be curious to see what you think.
@StevenClontz and others

Would "monotonically T 4 " be appropriate as an alias for T109, to emphasize the assumption of T 1 ?

No, please.  Everybody in the literature uses "monotonically normal" with the current meaning, i.e., with the T1 assumption (same as T4 in this case).  This is not a property meant to be appreciated by topology beginners, so no need for this alias.
It's similar to the notion of $\aleph_0$ space or $\aleph$ space, etc, where everybody assume T3.

FWIW, I lightly disagree (authors get away with bad names in papers where we should not, since they aren't trying to catalogue everything in the same database), but not enough to push the point further.

I don't think "monotonically $T_4$" would be appropriate for the following reason.
When we say "monotonically normal" we mean that the property of normality is monotone. But being $T_4$ is both property of normality and of being $T_1$. Saying that something is monotonically $T_4$ would seem to imply we are trying to encapsulate both of those properties in a monotone way, and not just normality.

To expand a little more on this, everybody in the literature that studies "monotonically normal" includes the T1 assumption. If we do the same, that means we will also restrict ourselves to spaces that are T1 (actually T4 and even T5) when studying this concept.  But that's already a rich theory with many beautiful theorems.
It is possible that one could relax this and out of curiosity study what happens without the T1 assumption.  But nobody has bothered to do so in the literature it seems, maybe because some of the important theorems are not true anymore?  I have not thought about it, so I don't know.
In any case, if suddenly the literature has a few papers without the T1 assumption, we can change things/(add an alias) at that time.  In the mean time, I think there is already plenty of interesting things as is.
And it's a little similar to $\aleph_0$ space = T3 + countable $k$-network.  The T3 condition is assumed because it makes things nicer and there are plenty of interesting results already in this case.  So everybody studying these spaces goes along with this assumption.

Sorry @david20000813 I didn't see that you have raised the same issue. I've closed mine.

@Moniker1998 No worries, it did get buried quite deep in the list of issues. Yours also listed $T_5$ and collectionwise normal as consequences of monotonically normal, which I didn't list in my issue.

I think we can add the final theorem suggested in my issue in this PR, namely, Monotonically normal => not Dowker (or equivalently, Monotonically normal => Countably paracompact, as Dowker is equivalent to $T_4$ + not Countably paracompact). It's just a direct citation: Theorem 2.3 of Chapter 17 of DOI: 10.1016/C2009-0-12309-7.

Otherwise, I just have one concern: For hereditarily collectionwise normal, Problem 5.5.1(a) of Engelking only proves the characterizations are equivalent when the space in question is $T_1$. Is the equivalence clear without the $T_1$ assumption? I can easily see how the corresponding equivalence works for completely normal, but I don't see how this is proved for hereditarily collectionwise normal.

Otherwise, I just have one concern: For hereditarily collectionwise normal, Problem 5.5.1(a) of Engelking only proves the characterizations are equivalent when the space in question is T 1 . Is the equivalence clear without the T 1 assumption? I can easily see how the corresponding equivalence works for completely normal, but I don't see how this is proved for hereditarily collectionwise normal.

The equivalence between the characterizations for hered. coll. normal is not hard to prove directly.  That does not need T1 in any way.  The only reason T1 is assumed is because Engelking assume T1 as part of the definition of collectionwise normal.
(That's one of the annoying things about Engelking.  He makes definitions with overly restrictive separation axioms, like normal spaces are T2, compact spaces are Hausdorff, Lindelof spaces are regular, etc.  And then when he states theorems, he makes these extra assumptions, but it's never clear if it's really needed in the argument or if it's just to satisfy the definitions.)
Anyway, we can add a mention that T1 is not needed for this equivalence.  I can see what the original article of McAuley says.  If needed, we could do a mathse post for the equivalence?

@david20000813 Regarding Dowker, we should add the version [monotonically normal => countably paracompact].
I purposefully did not add the theorem as I would like to take the opportunity to understand the theorem myself. I started reading the proof that [LOTS => countably paracompact] but haven't finished it.  The proof for monotonically normal seems even more involved.  Do you have any high level insight about it?
What we can do for now it to release this PR without it, which will already be useful.

Hereditarily collectionwise normal: McAuley (https://zbmath.org/0109.15301) only says "It is not difficult to show that ...".

https://math.stackexchange.com/questions/4737011/definition-of-hereditarily-collectionwise-normal-spaces-using-separated-families
May need a fleshed out answer there.

@david20000813 Regarding Dowker, we should add the version [monotonically normal => countably paracompact].
I purposefully did not add the theorem as I would like to take the opportunity to understand the theorem myself. I started reading the proof that [LOTS => countably paracompact] but haven't finished it. The proof for monotonically normal seems even more involved. Do you have any high level insight about it?
What we can do for now it to release this PR without it, which will already be useful.

@prabau I haven't fully read the proof myself. I suppose in that case we can wait until we get a better understanding of how the proof works before adding that then.

Hereditarily collectionwise normal: McAuley (https://zbmath.org/0109.15301) only says

"It is not difficult to show that complete collectionwise normality is equivalent to hereditary collectionwise normality in a topological space."

Basically it's the same type of arguments to show the equivalence between "hereditarily normal" and "completely normal" (= def. via separated sets).

Oh, I see. I chose the wrong open set for the proof. When I was thinking of proving the equivalence between hereditarily normal and completely normal, I was using the open set given by the space minus the intersection of the closures of the two separated sets. This approach cannot generalize to hereditarily collectionwise normal, since then you would need to subtract infinitely many closed sets. But yeah, the general outline in the MSE question works.

https://math.stackexchange.com/questions/4737011/definition-of-hereditarily-collectionwise-normal-spaces-using-separated-families
May need a fleshed out answer there.

That would be the best, yeah. Now that I see what the open set is supposed to be, I agree that the proof is relatively easy, but it would be good to have an explicitly written down proof for citation.

https://math.stackexchange.com/questions/4737011/definition-of-hereditarily-collectionwise-normal-spaces-using-separated-families
May need a fleshed out answer there.

That would be the best, yeah. Now that I see what the open set is supposed to be, I agree that the proof is relatively easy, but it would be good to have an explicitly written down proof for citation.

I'll write up something as an answer to the mathse post later today.

I have posted an answer to https://math.stackexchange.com/questions/4737011 and will update the reference for pi-base.

@Moniker1998 Definition (2) is equally important as Definition (1).  In fact, many of the later paper only give Def (2) or a variant for monotonically normal.  It also provides a nearly obvious proof that metrizable spaces are monot. normal. (I added one sentence to T669 to make that clear.)  So I think it's important to keep the proof of T669 as is, to show the simplicity of the Def (2) approach.
See also http://at.yorku.ca/b/ask-a-topologist/2003/0383.htm that I did not mention for T669.  I did mention it though as an additional link for T629 (proving that LOTS are monotonically normal).  It uses Def (2) to prove the result. And it's really very close to Heath-Lutzer-Zenor's approach, who also do not use Def (1) for that.
https://topology.pi-base.org/properties/P000109: The section at the end about "Equivalence between the two definitions" gives references and shows why it's equivalent.  If you have any questions about that part, please ask.

Definition (2) is equally important as Definition (1). In fact, many of the later paper only give Def (2) or a variant for monotonically normal. It also provides a nearly obvious proof that metrizable spaces are monot. normal. (I added one sentence to T669 to make that clear.) So I think it's important to keep the proof of T669 as is, to show the simplicity of the Def (2) approach.

I understand that the approach might be simple, but I don't understand why not to mention the alternative.

Do you still have a doubt about the equivalence between the two definitions?

I don't understand what you mean? I never had doubts about the definition.

So there is no problem then in using the simplest and easiest proof available then.
It's similar to #1030.  There was no need to use fancy notions there, as there was a simple direct proof of the result.

I discover that there are too few sufficient conditions for Hereditarily CWN and that'll end up lots of spaces (even finite ones)  are ?Hereditarily CWN, maybe we should do a cleanup or add some sufficient conditions.

There are finite spaces which aren't normal: https://topology.pi-base.org/spaces/S000007

@yhx-12243 Your observation is correct, but this will not happen in this PR.  Better release what we have now and continue with additional PRs.

Suggestion: If people are satisfied with what is here so far, one of you could approve.  And then we can write more PRs involving monotonically normal spaces.
And the first person who manages to read and understand the proof of [monotonically normal => countably paracompact] can write a PR for it.

I think I've now more or less understood the proof of "Monotonically normal => Countably paracompact". The proof in the source I cited has some minor typos, as well as some weird over-complications. I'll present a rewrite of the proof and a high-level outline when I write the PR for the theorem.


Ability to specify which interface to use for the cloud provider

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
I couldn't specify which interface endpoints to use for the Openstack cloud provider. It defaults to the public interface from the gophercloud SDK.
What you expected to happen:
A way to specify which interface to use in the cloud provider config:
e.g.
interface=internal or interface=admin
keep public by default if not specified.
How to reproduce it (as minimally and precisely as possible):
Start any cluster with the openstack cloud provider and turn on verbose logging to see the requests going to the public endpoint.
Anything else we need to know?:
Environment:

openstack-cloud-controller-manager version: all
OS (e.g. from /etc/os-release): all
Kernel (e.g. uname -a):
Install tools:
Others:

I would like to work on this, can someone please assign it to me?

Hi @asomya, thanks for raising this issue, could you please add more information for this feature request, e.g. what's the problem with the current implementation, maybe add some logs you've seen? It will help us to know better about what we are going to enhance. Thanks!

@lingxiankong it looks like @asomya is referring to the https://docs.openstack.org/security-guide/api-endpoints/api-endpoint-configuration-recommendations.html
User can specify the endpoint_type (e.g. OS_ENDPOINT_TYPE) and it can be used to determine the endpoint (https://github.com/gophercloud/gophercloud/blob/13466e32a4a33946a48a259784a7f1f470d78513/endpoint_search.go). I can take a look on this request.