PIXI.js v5 / Attempted import error: 'extras' is not exported from 'pixi.js'

Description
Hey :wave:,
I wanted to bump PIXI.js to the v5 and I got this error at compilation:
<EMAIL_ADDRESS>Attempted import error: 'extras' is not exported from 'pixi.js'.

I saw this issue: https://github.com/inlet/react-pixi/issues/98
It seems you fixed the issue and other issues related to PIXI.js v4 in last version: https://github.com/inlet/react-pixi/releases/tag/v0.7.1
But you can see, I still have the issue from #98.
Do you have an idea to get rid of it?
Steps to reproduce

Use CRA: yarn create react-app .
Install PIXI.js v5.0.4: yarn add<EMAIL_ADDRESS>Install @inlet/react-pixi v0.7.1: yarn add<EMAIL_ADDRESS>Paste this code as replacement of App.js:

import React from 'react';
import { Stage, Text } from '@inlet/react-pixi'

const App = () => (
  <Stage>
    <Text text="Hey!" />
  </Stage>
);

export default App;

Start the app: yarn start

Additional info

@inlet/react-pixi version: 0.7.1
React version: 16.8.6
ReactDOM version: 16.8.6
PIXI version: 5.0.4

Hi @fabienjuif,
Thanks! It tries to resolve the pixi.js v4 components which have different namespaces (note the extras error message). To solve this (just a temporary fix though) you can force create-react-app to use the commonjs import:
import { Stage } from '@inlet/react-pixi/index'

However, you won't be able to use the Stage object either as this uses pixi.js v4 PIXI.Application which is not compatible with the new v5 API. However you can easily create your own Stage object.
Even better would be to create a PR and upgrade Stage and components/* to make it compatible with PIXI v5. 🙏

I can do this as well, but haven't got time the coming weeks (working on some projects). If you need it now we can work on it together. Just make a PR and I'll contribute to it.

Hey @inlet I try to take a look then, but without promising anything :)

@fabienjuif This is caused by the old typings for Pixi in your v5 branch. My PR I will send through to you shortly will fix it! Just testing now to make sure it works!

Fixed in #116

Hi, so how do you use it? I'm trying to play around with this https://codepen.io/inlet/pen/5aaed9ddeadb4d7bb5ea435d77df397a but it seems that it is still using v4.


Allow deploy secrets without list  permission for it

Output of helm version:
v3.0.0
Output of kubectl version:
oc v3.11.135
kubectl v1.11.0
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
OpenShift 3.11 on premise
Acccording to company policy it is not allowed to list/describe secrets but it is allowed to create/edit/delete.
In that scenario helm deployments with secrets is failing due to missing list RBAC permission:
helm upgrade --install ...
Error: UPGRADE FAILED: query: failed to query with labels: secrets is forbidden: User "system:serviceaccount:[redacted]-deployer" cannot list secrets in the namespace " -prod": no RBAC policy matched
Please allow helm to handle this exception and process deployment of  secrets.

In order for Helm to determine the next release version, it needs to perform a lookup in its backend for the latest deployed version. This is required to generate the merge patch between the source and the target release.
https://github.com/helm/helm/blob/38670ebe3dfa5e8f61f58a0bd66098b7a0e9da77/pkg/action/upgrade.go#L122-L123
If you don't have the capability to list secrets, then Helm will be unable to function properly. An alternative solution would be to switch to an alternative storage backend using export HELM_DRIVER=configmap.
Hope this helps.


fix(select): style trigger as disabled when select is disabled

This change resolves the issue I just opened https://github.com/cschroeter/park-ui/issues/257. It styles the select trigger to look disabled.
Before:

After:

@wontondon
Thanks mate.


Support spo2 and migrate to v2 API

Hi, I just wanted to let this project's maintainer know that Oura has announced that the V1 version of its API will be discontinued in Jan 2024, and will no longer be available.
So after that time, this project will need to use the v2 API in order to function.

@dvargas92495 The v1 API has been removed and the extension has stopped working.

Yup, we are working on the replacement - we need to stand up an api in our backend in order to support


API: IntervalCollection should implement IComponentLoadable

IntervalCollection slipped through the cracks as we introduced IComponentHandle.
You should be able insert an interval collection into an ISharedMap / ISharedDirectory like this...
const intervals = sequence.createIntevalCollection();
this.root.add("intervals", intervals.handle);

...where the handle references the interval collection via the sequence that created it.

I do not see createIntevalCollection method, but I do not see anything related to handles on IntervalCollection either.
@DLehenbauer, @anthony-murphy - are we still planning to address it?
I'll mark won't fix for bot to close this issue if there is no activity.


SCRUM-3693: roll down MaTI DB between environments

Fix the integration tests failure (SCRUM-3692) imposing ordering and making the GET counters endpoint public
Adds a persistence unit "rolldown" to roll down the DB. For production it is be the beta database, for beta it is the alpha database
Adds the code to roll down the MaTI db for curation, easily extensible for the ABC literature system.

closing for gitguardian check to remove local password from yaml


incorrect branch name on Gsplit

let g:lightline = {
  \ 'active': {
  \ 'left': [['mode', 'paste'],
  \    ['gitbranch', 'readonly', 'filename', 'modified']],
  \ 'right': [['lineinfo'],
  \    ['percent'],
  \    ['fileformat', 'fileencoding']]
  \ },
  \ 'component_function': {
  \   'gitbranch': 'FugitiveHead'
  \ },
  \ }

Open a file in a git repository in branch 1, :Gsplit <branch 2> opens a new tab with same file in branch 2. Bottom left corner branch name is branch 1 (should be branch 2).
Thanks!

The FugitiveHead function returns the current branch, but the Gsplit command does not checkout to the specified branch, so that's understandable behavior.

Do you have a suggestion to get branch 2? Thanks!

Would you ask to fugitive.vim devs? I'm not familiar with fugitive APIs.

Thanks. I have made a ticket with them.


Fix: coalesce typeless colnames

Updates macro that coalesces datatype-named column variants, which is a common behavior in Stitch-loaded tables.
Base case (previous functionality): coalesce field__type1 and field__type2 to string column field
Additional case (this PR): coalesce field and field__type to string column field
This was causing errors in a project, whereby the previous macro behavior included two columns named field (one "clean" and one coalesced) in its output.

@drewbanin I added integration tests + some comments to the macro code, which is admittedly dense. Do you have recommendations around possible areas to refactor?


Deletion of many Messages [Again]

Hello i posted a few month ago, that it would be nice to make a workaround the Discord Limit of 2 weeks deletion.

I have an idea how to fix that issue, you can get the messages from the channel and delete all message seperated and not as bulk. The two weeks rule is only for bulk messages not for deleting messages seperated. I know it will take longer to delete all messages, but i think it would be helpfull.

Also please add a message for the user, which say the cause of the problem.

I hope you can add it, i would add it on my own, but i dont know much about this language and dont want to mess up something.
I hope you read and think about my idea. It would be really nice if you can implement this options.

This is not a bad idea and fine for a smaller thing/private or some self-hosted, but it becomes a pain for the public bot. The BULK_MESSAGE_DELETE endpoint is specific and per-channel, which is unique and allows bot accounts only to delete very fast, and per-channel thereby avoiding ratelimit issues.
There is no special exemption for this for bots, and they would use the same MESSAGE_DELETE endpoint as you or I would, and the ratelimits would be towards the global as well, so it would be very slow - especially in large public bots.
I do this privately - not with Nadeko - but this doesn't seem to be worth it since the public bot wouldn't reasonably be able to do it without API abuse, and timing it is a few extra bit of work (BULK until hits 2 week, then delete slowly) as you would need to keep track of the channel and global ratelimit - if not it will turn messy very fast.

I dont need that it will be deleted fast. Slowly is acceptable. Sure, the public bot cant handle that, but i would like it for private hosted bots like mine, that there is an option to slowly delete a huge amount of messages

You will be able to delete up to 1000 messages, regardless of their send time in 1.43


which pre-train model should we use for fine-tuning

I have pre-trained the IndicBART model on new monolingual data, and in the model path two models are saved  1) IndicBART and 2) IndicBART_puremodel.  Now which should we use during the fine-tuning?

IndicBART size is 2.4 GB and pure_model size is 932.

Either.
Use the pure model with the flag --pretrained_model
Use the larger model with the flag --pretrained_model and an additional flag --no_reload_optimizer_ctr_and_scheduler
The larger checkpoint contains optimizer and scheduler states so you can resume pretraining in case of crash. During fine tuning resetting the optimizer is more common.


CLI: conf get | set | ls

Create a port of pgagroal's
  conf <action>            Manages the configuration (e.g., reloads the configuration
                           The subcommand <action> can be:
                           - 'reload' to issue a configuration reload;
                           - 'get' to obtain information about a runtime configuration value;
                                   conf get <parameter_name>
                           - 'set' to modify a configuration value;
                                   conf set <parameter_name> <parameter_value>;
                           - 'ls'  lists the configuration files used.

functionality.
We have reload already

@MohanadKh03 Can you take this one ?
@Jubilee101 can help with core stuff

Sure!
Regarding the networking part though when writing the commands into pgmoneta's socket should it be the same as pgagroal's way ? I can see some pattern but correct me if im wrong
1.Send the header
2.Send the size of the payload
3.Send the payload itself
4.Read the response as a json
5.Extract whatever needed and then print it out in the console
Is that correct ? assuming no failures/errors in any of the steps

Yes, the pgmoneta way is the new way of doing it, so you need to extract information from the "Response" part of the JSON payload based on the input. That is the easy part - think of conf get as a simple https://jqlang.github.io/jq/ command.
The harder part is the conf set command, but it shouldn't be that hard either - we need to send a request with the key and the new value

Remember to add yourself to the authors info...

Just let me know if you need anything, welcome! @MohanadKh03

Yes, lets get the full solution now because we need a chapter in the advanced manual that describes how to get the configuration, a field and how to set a field.
The manual work can be separate from this

@MohanadKh03 Where are you on this ?

Hey @jesperpedersen My bad I have been pretty busy and haven’t had a chance to continue working on this. It might be better if someone else takes over to keep things going and not block progress. Thanks and apologies for the late progress.

@MohanadKh03 Thanks for the update !

@jesperpedersen I can continue with this issue, kindly assign me this.

@ashu3103 Ok, but this is an important task very soon

@ashu3103 You can see how it works in pgagroal - here we need to get the configuration as a JSON and then filter out the entry wanted, set is a key/value pair and then matched on the server side. conf ls is the easiest one as it just a request, and the strings in the Response part

@ashu3103 Ok, but this is an important task very soon

Sure, I'll keep that in mind and try to wrap it quickly.

@ashu3103 Do conf ls first and post a draft patch


Is this project dead?

Just wanted to ask if this project is dead or are plans for updating this one?

Unfortunately, it is dead :(

Unfortunately, it is dead :(

No plans for coming back? :/


we can re-consider supporting freebsd now

Since these defined packet information structures prevent ipstack from supporting FreeBSD, which is caused by tun, however, ipstack can support FreeBSD together with tun2 since tun2 supports FreeBSD now, we can re-consider supporting the platform by reverting https://github.com/narrowlink/ipstack/commit/04b7ac7c8e1d9e533584c6f817fa24b63258299a.

https://github.com/narrowlink/ipstack/commit/b29ace0b16578d734459ae87b97e5b4e8ab68e19

FreeBSD always does not have packet information, in my test. see https://github.com/ssrlive/rust-tun/blob/v2/src/platform/freebsd/device.rs#L454


[fix] (all) fix ignores

delete tracked files from git's cached (dist and docs)
Reduce size of ./packages from 31M to 2.8M

Tracking build artifacts was intentional. But it was a decision I was on the fence about and I'm more than happy to stop. I think the reasons behind it were

We've always done it that way
It makes it possible to install from git (npm install go-faast/coin-payments)
I don't remember any others, but we should probably stop committing artifacts

We'll also need to modify the postversion scripts in package.json because it'll add these back

Tracking build artifacts was intentional. But it was a decision I was on the fence about and I'm more than happy to stop. I think the reasons behind it were

I agree. I'm all for this change.
Current npm scripts for releasing will need to be adjusted for this change. Each package has a version script that runs npm run build && git add -Af dist docs which is going to add all these files back if not removed. Additionally, lerna run build will need to be added to the "Steps to publish" section of the readme to ensure the artifacts are generated before being published to npm. Consolidating all that into a single script would be a good idea.

Changes addressed in v2.2.1


WIP model: add cascade to all foreign keys

Missing alembic upgrade recipe and tests.

Signed-off-by: David Caro<EMAIL_ADDRESS>

@david-caro If you rebase on top of master the tests should pass now

Merged via #119


Check underlay against DL and VRT

Check underlay

[ ] matches DL
[ ] check VRT passes
[ ] check and update migration guides example

No vrt for underlay

Summary:
Modal & Tray look good.
I confirm that the CSS props are being applied to the underlay in main.
The token   --spectrum-dialog-underlay-background-color: var(--spectrum-alias-background-color-modal-overlay);
got removed and replaced with   --spectrum-dialog-confirm-overlay-background-color: var(--spectrum-alias-background-color-modal-overlay);
The values are identical.
How has this been tested:
Chrome Version 87.0.4260.0 (Official Build) canary (x86_64) on MacOS
Screenshots:


Getting error 'ConnectionError: ('Connection aborted.', error(2, 'No such file or directory'))'

I am getting an error when trying to use dockerpty. Using the example in the
README:
import docker
import dockerpty

client = docker.Client()
container = client.create_container(
    'busybox:latest',
    stdin_open=True,
    tty=True,
    command='/bin/sh')

dockerpty.start(client, container)

When I run this, I get the error:
Traceback (most recent call last):
  File "test_script.py", line 9, in <module>
    command='/bin/sh')
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/docker/api/container.py", line 116, in create_container
    return self.create_container_from_config(config, name)
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/docker/api/container.py", line 126, in create_container_from_config
    res = self._post_json(u, data=config, params=params)
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/docker/client.py", line 166, in _post_json
    return self._post(url, data=json.dumps(data2), **kwargs)
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/docker/client.py", line 107, in _post
    return self.post(url, **self._set_request_timeout(kwargs))
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/requests/sessions.py", line 508, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/requests/sessions.py", line 465, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/Users/michaelbarton/Library/Python/2.7/lib/python/site-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', error(2, 'No such file or directory'))

Here are the details of my docker install, using docker-machine:
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   76d6bc9
 Built:        Tue Nov  3 19:20:09 UTC 2015
 OS/Arch:      darwin/amd64

Server:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   76d6bc9
 Built:        Tue Nov  3 19:20:09 UTC 2015
 OS/Arch:      linux/amd64

And the details of my OS:
Darwin Michaels-MacBook-Air.local 14.5.0 Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64 i386 MacBookAir7,2 Darwin

The following command does however work:
docker run -ti busybox:latest /bin/sh

I have tried the above script on a separate work computer and got a similar error. This was with docker-py-1.5.0 and dockerpty-0.3.4

For anyone else coming across this: you get this error if there are no docker machines running. Try eval ${docker-machine env default} (or swap default for your machine name)

@michaelbarton @mejamiewilson  Did you find any solution ? I understand that eval ${docker-machine env default} works great for command,  but any solution for Client() via script ?
OS info:
Darwin Ravis-MacBook-Pro.local 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64

If you're using Docker Machine, you can point docker-py at it using docker-machine env and the kwargs_from_env() utility method.
from docker import Client
from docker.utils import kwargs_from_env

client = Client(**kwargs_from_env(assert_hostname=False))
...

$ eval "$(docker-machine env default)"
$ python script.py


About the console output during validation.

Thanks for the awesome work!
I have a question about the console output during validation.
What do the numbers in parentheses represent, as shown in the log below (0.7825)  and (0.7502) ?
Averaged stats: val_iou_0: 0.8307 (0.7825)  val_boundary_iou_0: 0.8178 (0.7502)

请问您是用哪个数据集进行训练的呢


Added Switch Animation for Material 3

Part of: https://github.com/flutter/flutter/issues/91605
This PR is to add animation for M3 Switch.
https://user-images.githubusercontent.com/36861262/194502373-2d8c290f-13b1-4258-a373-ba377dc38e6c.mov
Slowed down for reference:
https://user-images.githubusercontent.com/36861262/194502598-7501d83c-d6b9-45be-a589-46d1ff546fa6.mov
Fixes:
#103536
#112026
#111663
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

I just marked the golden change as positive since it is a new test for the Switch thumb in the middle of the track.

Great work!

@QuncCccccc , beautiful animation!
For an enabled switch, when the ball hits the border of the switch, the background color of the switch is repainted to a darker shade, and when the ball returns from the border to its original enabled position, the background is repainted to a lighter shade, and this happens on the last frames of the animation. The same applies to the animation of turning off the switch, as well as the shade of the ball itself.
Is this a unique feature, or is it an unwanted result?


Strange licence error / conditions

In latest healthcheck we noticed:
File: [cocoon.log.2020-09-08] Warnings/Errors: [0/13]
    22629:2020-09-08 05:13:22,135 ERROR cocoon.handled  - Could not read resource cocoon://DRI/8/handle/1135/1042/license/agree
    at <map:serialize type="xml"> - resource://aspects/BrowseArtifacts/sitemap.xmap:104:40
    at <map:transform type="Navigation"> - resource://aspects/BrowseArtifacts/sitemap.xmap:47:47

We do not really understand this error messasge, what does it mean?
Second thing: this item (http://hdl.handle.net/11356/1042) has a standard CC BY-NC licence. Yet, unlike other items with this licence, it requires the user to log-in before allowing download of files. We checked the metadata, but cannot find anything forcing this behaviour. Where is this (wrong) requirement hidden?

We do not really understand this error messasge, what does it mean?

My general (perhaps questionable) understanding from talking to Jozef and Ondrej was that cocoon errors are mostly harmless artifacts which aren't necessarily easy to fix (for instance, see https://github.com/clarinsi/clarin-dspace/issues/10#issuecomment-332584922). So I've tended to pay more attention to other errors. However, please do note if you find that these errors coincide with some kind of visibly problematic behaviour in the application

Second thing: this item (http://hdl.handle.net/11356/1042) has a standard CC BY-NC licence. Yet, unlike other items with this licence, it requires the user to log-in before allowing download of files. We checked the metadata, but cannot find anything forcing this behaviour. Where is this (wrong) requirement hidden?

Indeed, this is mysterious to me too. I've spent some time trying to track this down in the Java code, and have determined that this occurs (for 11356/1042, but not for 11356/1213, which has the same license) if the hibernate query at https://github.com/clarinsi/clarin-dspace/blob/clarin/utilities/src/main/java/cz/cuni/mff/ufal/lindat/utilities/HibernateFunctionalityManager.java#L128 returns any non-null results. However, it's not clear to me what these entities and queries are really about or why 11356/1042 is special, so I'll have to investigate further and/or pester Ondrej (again). Is this issue a priority (best if you use the *-priority github labels we once defined)?


Docs: Not clear how to use "request_attributes"

I am struggling reading the docs. It has no .yaml (or JSON) examples which makes it really hard.
I have successfully added an ext_proc [1] to my envoy proxy, but the the path does not reach the external processor (it does reach the cluster). I had a look at request_attributes, but it is not clear to me if that would solve my issue or even what the correct syntax is.
E.g. is this correct? If yes, what does it do?
http_filters:
          - name: envoy.filters.http.ext_proc
            typed_config:
              "@type": "type.googleapis.com/envoy.extensions.filters.http.ext_proc.v3.ExternalProcessor"
              failure_mode_allow: true
              async_mode: false
              message_timeout:
                seconds: 5
                nanos: 0
              processing_mode:
                request_header_mode: "SEND"
                response_header_mode: "SEND"
                request_body_mode: "NONE"
                response_body_mode: "NONE"
                request_trailer_mode: "SKIP"
                response_trailer_mode: "SKIP"
              request_attributes:
                - "request.path"
              grpc_service:
                google_grpc:
                  target_uri: "<external processor>"
                  stat_prefix: "<metric prefix>"

[1] https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/ext_proc/v3/ext_proc.proto

cc @tyxia @yanavlasov as codeowners

I have successfully added an ext_proc [1] to my envoy proxy, but the the path does not reach the external processor (it does reach the cluster)

request_attributes  is for forwarding Envoy request attributes to external processor when matched. In other words, your client request should already have path field in to be matched.

@jbohanon  who added attributes feature.

To triage this, if you don't use request_attributes feature, just configure  request_header_mode to SEND, does your external processor server receive headers?

To be totally clear, what version of Envoy are you using? The attributes feature merged very recently and will not be available in a released version of Envoy until 1.30.
Assuming you are using a version which accepts this config, the yaml you posted looks correct to me. The attribute should appear in this field in a struct under the key envoy.filters.http.ext_proc

We are running an old version (1.26.4), I should have checked ..
@tyxia I can confirm request_header_mode: SEND works.
Thanks for the quick reply all!


Improve ergonomics of using this library with Salesforce APIs

Hello
I am interested in leveraging this library to implement bayeux protocol as is required for long polling with Salesforce streaming API. I noticed that a recent commit to the extension package mentions fixing subscription to Salesforce, so I am assuming that this is definitely a potential use case of this library.
I am new to Salesforce and was hoping one of this library's contributors had some sample code they could share with me around how to use this library to subscribe to Salesforce streaming APIs. Any tips/references/guidance you could provide would be awesome. Very much appreciated in advance.
Chris

Hi @criswit that contributor would be @zknill if anyone.
To give you a high-level sketch though, you'll want a library that allows you to authenticate with Salesforce and perhaps create a http.Client (or http.Transport) that has that authentication. Then you can do use bayeux.WithHTTPClient or bayeux.WithHTTPTransport and emulate https://github.com/sigmavirus24/gobayeux/blob/8e23f51bba44af3474ddd9b92f6e2cd3265300f0/cmd/testutil/main.go#L57-L90
I'd advise going through the code examples that salesforce documents here.
Cheers,
Ian

Hi @sigmavirus24 @zknill
Thanks for that info. I have done as mentioned, I have an library that authenticates with Salesforce using JWT and returns me with a *http.client containing the Authorization header (supposedly).
I am able to perform a handshake, but when trying to subscribe/connect it throws me a 403 unknown client.
DEBU[0000] got client
DEBU[0000] starting                                      at=handshake
DEBU[0001] finishing                                     at=handshake duration=737.014372ms
DEBU[0001] starting long-polling loop                    at=start
DEBU[0001] in polling loop                               at=poll
DEBU[0001] got subscription requests                     at=poll
DEBU[0001] starting                                      at=subscribe
error in bayeux client: "unable to subscribe to channels: 403::Unknown client"

I have been able to perform a successful handshake and connection (not using this library) when I've made a POST request to with connect parameters and including the "Authorization: OAuth ..." header in that request. To me, it seems like that is what the extensions package is trying to do - however I am yet unable to understand how I am supposed to use that package when creating the Bayeux client.
I've created two gists with my main and sfdc_auth source code, if that is helpful. Mainly I'm unsure how I'm supposed to make use of that "extensions"  package or if it's supposed to be taking care of the putting an Authorization header in the Transport implicitly. Thanks again for the support.

You likely don't need the extension package. I was writing that to use with the test utility command in the repository as I know that I can make a Salesforce developer edition org and test against it provided I can get a token out of sfdx etc. I just never got around to that.
I think I remember something around Salesforce setting cookies as well. I wonder if the cookie jar isn't attaching those to the request correctly, perhaps because Salesforce is specifying a Path attribute that doesn't match the cometd URL. Can you see the Cookie headers/Cookie Jar cookies @criswit ?

Hey @sigmavirus24 thanks, I was reading something similar here
probably didn't do this right, but i modified the "parse response" portion of your bayeux_client to iterate through the cookies in responses after starting client. here's what i'm seeing
DEBU[0000] got client
DEBU[0000] starting                                      at=handshake
DEBU[0001] Cookie Name BrowserId
DEBU[0001] Cookie Value SPmVCz_sEeuxHFGPBLGF3w
DEBU[0001] Cookie Path /
DEBU[0001] Cookie Name t
DEBU[0001] Cookie Value !0vaFlJER5UsrfIGrfKp9YI2pARkJi5YS8O/yCf8GE+6HiX+CvWWacnC3MzF+OXsuC3USJWIP3jamDQ==
DEBU[0001] Cookie Path /cometd/
DEBU[0001] Cookie Name BAYEUX_BROWSER
DEBU[0001] Cookie Value eb4ajzqv8f0j5yiakirz4ui41ah6
DEBU[0001] Cookie Path /cometd/
DEBU[0001] Cookie Name force-stream
DEBU[0001] Cookie Value !u+63QcPFhMWL7Ti5ygfhHl1kwJScsjM7XyMnY4Kg2rV5HBLIAYV52ek1x6NWczMA5Uxjyi6PsMtOBlk=
DEBU[0001] Cookie Path /
DEBU[0001] finishing                                     at=handshake duration=360.963931ms
DEBU[0001] starting long-polling loop                    at=start
DEBU[0001] in polling loop                               at=poll
DEBU[0001] got subscription requests                     at=poll
DEBU[0001] starting                                      at=subscribe
DEBU[0001] Cookie Name BrowserId
DEBU[0001] Cookie Value SQZmtz_sEeu88MlxpRNA4Q
DEBU[0001] Cookie Path /
DEBU[0001] Cookie Name t
DEBU[0001] Cookie Value !0vaFlJER5UsrfIGrfKp9YI2pARkJi5YS8O/yCf8GE+6HiX+CvWWacnC3MzF+OXsuC3USJWIP3jamDQ==
DEBU[0001] Cookie Path /cometd/
DEBU[0001] Cookie Name force-stream
DEBU[0001] Cookie Value !H4zwzZfEmdG6M/W5ygfhHl1kwJScsqFUVf+op6XrBcME/iCyxnymkkfXF6ArBvMz0WjyR05+PNO8QaY=
DEBU[0001] Cookie Path /
error in bayeux client: "unable to subscribe to channels: 403::Unknown client"

looks like the "force-stream" cookie has a different value, and BAYEUX_BROWSER is present in handshake response but not in subscribe/connect response. am i understanding this correctly? will continue to investigate .

i might have got  it...
DEBU[0000] got client
DEBU[0000] starting                                      at=handshake
DEBU[0001] Cookie Name BrowserId
DEBU[0001] Cookie Value gohQhz_uEeu88MlxpRNA4Q
DEBU[0001] Cookie Path /
DEBU[0001] Cookie Name t
DEBU[0001] Cookie Value !0vaFlJER5UsrfIGrfKp9YI2pARkJi5YS8O/yCf8GE+6HiX+CvWWacnC3MzF+OXsuC3USJWIP3jamDQ==
DEBU[0001] Cookie Path /cometd/
DEBU[0001] Cookie Name BAYEUX_BROWSER
DEBU[0001] Cookie Value bbdcf6yxjkcn3dzekirzpbto113w
DEBU[0001] Cookie Path /cometd/
DEBU[0001] Cookie Name force-stream
DEBU[0001] Cookie Value !pdMAjDyuH2x96F0KdVzjdDX+5Mc4L305KNCPIJWoGUR26RPyHnlHmHW0dgLYO6WuVuXR0EvOCaGapzU=
DEBU[0001] Cookie Path /
DEBU[0001] finishing                                     at=handshake duration=280.789206ms
DEBU[0001] starting long-polling loop                    at=start
DEBU[0001] in polling loop                               at=poll
DEBU[0001] got subscription requests                     at=poll
DEBU[0001] starting                                      at=subscribe
DEBU[0001] finishing                                     at=subscribe duration=143.31755ms
DEBU[0001] queued next /meta/connect request             at=enqueueConnectRequest
DEBU[0001] in polling loop                               at=poll
DEBU[0001] checking for new messages                     at=poll
DEBU[0001] starting                                      at=connect
DEBU[0001] finishing                                     at=connect duration=52.961874ms
DEBU[0001] delivering messages                           at=poll
DEBU[0001] in polling loop                               at=poll
DEBU[0001] queued next /meta/connect request             at=enqueueConnectRequest
DEBU[0001] in polling loop                               at=poll
DEBU[0001] checking for new messages                     at=poll
DEBU[0001] starting                                      at=connect

Interesting, what changed?
Also you probably don't want to be putting cookie values in public issues like this as that's a secret leak technically speaking.

Also @criswit if there's anything you think we should add to help better support Salesforce, I'd be very open to reviewing PRs around this.

i'd love to contribute (even if just a little) let me cleanup what i have and circle back to you tomorrow. also - appreciate the security heads up

Looking forward to it @criswit and glad you got things working

hey @sigmavirus24 , sorry for the huge delay on this. i finally got around to putting some of my changes in which make this library connect to salesforce. i forked your repo and added the commit there so you can check it out and let me know any thoughts before i actually go about sending you a PR to review.
also - i want to help get the replay functionality included/working in this repo as well. might need a bit of guidance on how we should do that.
let me know your thoughts on this commit and the effect it might have on your library
https://github.com/criswit/gobayeux/commit/decedc58c8bd8ea8aebbf68295616c593799c9d3

Hi @criswit thanks for pushing that up for us to look at. I've been meaning to comment here and just have been busy. Sorry about that.
So a few things:

I think the auth part of this should be handled via the Transport I think we could improve https://github.com/sigmavirus24/gobayeux/blob/8e23f51bba44af3474ddd9b92f6e2cd3265300f0/extensions/salesforce/salesforce.go#L9-L44 to cover the gaps you've found.
Are you okay with me pulling your commit and updating it to cover what I think needs coverage?

For replay IDs does, https://github.com/sigmavirus24/gobayeux/blob/main/extensions/replay/replay.go not work for you? Technically replay IDs are an extension of the Bayeux protocol that Salesforce added to their servers. So it's an optional extension to the library that you'd need to configure. There's an in memory backend there but there's an interface you can implement if you wanted to store IDs in a data store (Redis, Memcached, etc.)

@sigmavirus24  hey - thanks for getting back , no worries about delay. quickly to respond to your questions (will circle back with more details on item 2)

yes - absolutely ok with this. let me know how i can further help.
I think i was able to get replayIds working , but I had to add some extension methods to the SubscribeRequestBuilder (i think) . i will go back to find where i did that and get back to you
let me know any thoughts

@criswit you've got the logic to add cookies to each request but you don't seem to pull them off from anywhere to store them. How is that code helping?

@criswit I updated some things to fix oversights and add documentation. Hopefully that helps

thanks @sigmavirus24

@criswit anything else to make this easier to use is also welcome feedback

sounds good. will keep in touch @sigmavirus24 . thanks for all your help


helm upgrade fails since 3.7

Output of helm version: 3.7
Output of kubectl version: 1.22.2
Cloud Provider/Platform (AKS, GKE, Minikube etc.): private cloud K8s
version 3.6.3 was working fine, as of 3.7 i'm getting:
Error: UPGRADE FAILED: timed out waiting for the condition
##[error]history.go:56: [debug] getting history for release eventsourcerapi
The pods in k8s don't get created, so I think helm is failing before that, when retrieving the history.
here the complete debug log:
2021-09-16T04:05:12.3518459Z [command]D:\AzureDevOps-agent1_work_tool\helm\3.7.0\x64\windows-amd64\helm.exe upgrade --namespace moo-dev --install --values D:\AzureDevOps-agent1_work\r12\a_eventsourcer\KubernetesAPI\values.yaml --wait --debug eventsourcerapi D:\AzureDevOps-agent1_work\r12\a_Infra.HelmCharts\api
2021-09-16T04:10:13.3558029Z history.go:56: [debug] getting history for release eventsourcerapi
2021-09-16T04:10:13.3559274Z upgrade.go:139: [debug] preparing upgrade for eventsourcerapi
2021-09-16T04:10:13.3559850Z upgrade.go:147: [debug] performing update for eventsourcerapi
2021-09-16T04:10:13.3560532Z upgrade.go:319: [debug] creating upgraded release for eventsourcerapi
2021-09-16T04:10:13.3562119Z client.go:218: [debug] checking 4 resources for changes
2021-09-16T04:10:13.3562740Z client.go:501: [debug] Looks like there are no changes for Secret "eventsourcerapi-cert"
2021-09-16T04:10:13.3563319Z client.go:501: [debug] Looks like there are no changes for Service "eventsourcerapi"
2021-09-16T04:10:13.3564068Z W0916 06:05:13.289172    3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
2021-09-16T04:10:13.3576522Z W0916 06:05:13.295176    3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
2021-09-16T04:10:13.3577636Z W0916 06:05:13.302173    3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
2021-09-16T04:10:13.3578282Z wait.go:48: [debug] beginning wait for 4 resources with timeout of 5m0s
2021-09-16T04:10:13.3578884Z upgrade.go:420: [debug] warning: Upgrade "eventsourcerapi" failed: timed out waiting for the condition
2021-09-16T04:10:13.3579447Z Error: UPGRADE FAILED: timed out waiting for the condition
2021-09-16T04:10:13.3579918Z helm.go:88: [debug] timed out waiting for the condition
2021-09-16T04:10:13.3580334Z UPGRADE FAILED
2021-09-16T04:10:13.3580686Z main.newUpgradeCmd.func2
2021-09-16T04:10:13.3581198Z 	helm.sh/helm/v3/cmd/helm/upgrade.go:200
2021-09-16T04:10:13.3581754Z github.com/spf13/cobra.(*Command).execute
2021-09-16T04:10:13.3582260Z 	github.com/spf13/cobra@v1.2.1/command.go:856
2021-09-16T04:10:13.3582772Z github.com/spf13/cobra.(*Command).ExecuteC
2021-09-16T04:10:13.3583348Z 	github.com/spf13/cobra@v1.2.1/command.go:974
2021-09-16T04:10:13.3583844Z github.com/spf13/cobra.(*Command).Execute
2021-09-16T04:10:13.3584286Z 	github.com/spf13/cobra@v1.2.1/command.go:902
2021-09-16T04:10:13.3584670Z main.main
2021-09-16T04:10:13.3585051Z 	helm.sh/helm/v3/cmd/helm/helm.go:87
2021-09-16T04:10:13.3585447Z runtime.main
2021-09-16T04:10:13.3585803Z 	runtime/proc.go:225
2021-09-16T04:10:13.3586302Z runtime.goexit
2021-09-16T04:10:13.3586788Z 	runtime/asm_amd64.s:1371
2021-09-16T04:10:13.3651817Z ##[error]history.go:56: [debug] getting history for release eventsourcerapi
upgrade.go:139: [debug] preparing upgrade for eventsourcerapi
upgrade.go:147: [debug] performing update for eventsourcerapi
upgrade.go:319: [debug] creating upgraded release for eventsourcerapi
client.go:218: [debug] checking 4 resources for changes
client.go:501: [debug] Looks like there are no changes for Secret "eventsourcerapi-cert"
client.go:501: [debug] Looks like there are no changes for Service "eventsourcerapi"
W0916 06:05:13.289172    3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0916 06:05:13.295176    3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0916 06:05:13.302173    3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
wait.go:48: [debug] beginning wait for 4 resources with timeout of 5m0s
upgrade.go:420: [debug] warning: Upgrade "eventsourcerapi" failed: timed out waiting for the condition
Error: UPGRADE FAILED: timed out waiting for the condition
helm.go:88: [debug] timed out waiting for the condition
UPGRADE FAILED
main.newUpgradeCmd.func2
helm.sh/helm/v3/cmd/helm/upgrade.go:200
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.2.1/command.go:902
main.main
helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
runtime/proc.go:225
runtime.goexit
runtime/asm_amd64.s:1371

I have a feeling this may be relevant…

W0916 06:05:13.289172 3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

Helm 3.7 is compiled against the Kubernetes 1.22 client libraries.

I have a feeling this may be relevant…

W0916 06:05:13.289172 3416 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

Helm 3.7 is compiled against the Kubernetes 1.22 client libraries.

helm 3.6.3 with kubectl 1.22 worked just fine, or are there some internals i'm missing?

I will close this for now; this seems to be the perfect storm: our infrastructure provider (private cloud K8s) has some certificate issues as of the same date as the release of helm 3.7.


Dev: "fatal: ambiguous argument 'master': unknown revision or path not in the working tree

Lots of error on dev:

at least some of the are
  |   | 2022-12-13 17:13:59 | [ ERROR ] analysis error: Shell command failed: |
  |   | 2022-12-13 17:13:59 | command: "git log -n1 --format=format:"%H-%ct" "master"" |
  |   | 2022-12-13 17:13:59 | path:    "/checkouts/github.com-dastrobu-argtree" |
  |   | 2022-12-13 17:13:59 | message: "ShellOut encountered an error |
  |   | 2022-12-13 17:13:59 | Status code: 128 |
  |   | 2022-12-13 17:13:59 | Message: "fatal: ambiguous argument 'master': unknown revision or path not in the working tree. |
  |   | 2022-12-13 17:13:59 | Use '--' to separate paths from revisions, like this: |
  |   | 2022-12-13 17:13:59 | 'git <command> [<revision>...] -- [<file>...]'" |
  |   | 2022-12-13 17:13:59 | Output: """ [component: server, database-id: psql] |
  |   | 2022-12-13 17:13:59 | [ ERROR ] analysis error: Shell command failed: |
  |   | 2022-12-13 17:13:59 | command: "git log -n1 --format=format:"%H-%ct" "master"" |
  |   | 2022-12-13 17:13:59 | path:    "/checkouts/github.com-sventiigi-flyoverkit" |
  |   | 2022-12-13 17:13:59 | message: "ShellOut encountered an error |
  |   | 2022-12-13 17:13:59 | Status code: 128 |
  |   | 2022-12-13 17:13:59 | Message: "fatal: ambiguous argument 'master': unknown revision or path not in the working tree. |
  |   | 2022-12-13 17:13:59 | Use '--' to separate paths from revisions, like this: |
  |   | 2022-12-13 17:13:59 | 'git <command> [<revision>...] -- [<file>...]'" |
  |   | 2022-12-13 17:13:59 | Output: """ [component: server, database-id: psql]

This might be due to a default branch change. Flyoverkit is now on main, and so is argtree. This should sort itself out on its own - although we may want to deal with the flood of errors somehow.

These errors are now gone. We could improve this and reduce noise in the logs but it's not the most important thing in the world to address right now.
Will close for now.


Haskell lsp nightly

Use haskell-lsp-<IP_ADDRESS> from the latest stackage nightly. For the GHC 8.2.1 build

Does this bring GHC 8.2 support for HIE, or is it still blocking on ghc-mod?

It is still blocked on ghc-mod /cabal-helper.
And I fear my next task is to dive into that swamp, as @DanielG does not seem to have the time to do it.

Ah, damn :(
Perhaps there should be more coordination between GHC releases and core tooling such as this, although I understand that the cabal-helper update was quite big, with backpack and all.

Yes, backpack and new-build need to be digested. Both are major changes.


[libadwaita] Update to 1.4.2

Fixes #36328, update libadwaita to 1.4.2.
The following error occurred, so it depends on #36359:
Dependency gtk4 found: NO found 4.10.5 but need: '>= 4.11.3'

[ ] Changes comply with the maintainer guide.
[ ] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[ ] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[ ] Only one version is added to each modified port's versions file.

Reopen to rerun the stuck triplet.

@dg0yt
The expected result is that this issue will be resolved after #37396, but it still exists, can you help me with a suggestion?
The Meson build system
Version: 1.5.2
Source dir: D:\b\libadwaita\src\1.4.2-bc9e91710f.clean
Build dir: D:\b\libadwaita\x64-windows-dbg
Build type: native build
Project name: libadwaita
Project version: 1.4.2
DEPRECATION: None of the values ['gnu11'] are supported by the c compiler.
However, the deprecated gnu11 std currently falls back to c11.
This will be an error in the future.
If the project supports both GNU and MSVC compilers, a value such as
"c_std=gnu11,c11" specifies that GNU is preferred but it can safely fallback to plain c11.
C compiler for the host machine: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.41.34120/bin/Hostx64/x64/cl.exe -DWIN32 -D_WINDOWS -utf-8 -MP -D_DEBUG -MDd -Z7 -Ob0 -Od -RTC1 (msvc 19.41.34120 "Microsoft (R) C/C++ Optimizing Compiler Version 19.41.34120 for x64")
C linker for the host machine: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.41.34120/bin/Hostx64/x64/link.exe link 14.41.34120.0
Host machine cpu family: x86_64
Host machine cpu: x86_64
Check usable header "roapi.h" : YES
Check usable header "Windows.Foundation.h" : YES
Check usable header "Windows.UI.ViewManagement.h" : YES
Compiler for C supports arguments -FImsvc_recommended_pragmas.h: NO
Program sassc found: YES
Found pkg-config: YES (D:/downloads/tools/msys2/1e74ca60daa10104/mingw64/bin/pkg-config.exe) 2.2.0
Configuring adw-version.h using configuration
Program gen-public-types.py found: YES (D:\downloads\tools\python\python-3.11.8-x64\python.exe D:\b\libadwaita\src\1.4.2-bc9e91710f.clean\src\gen-public-types.py)
Run-time dependency gio-2.0 found: YES 2.80.0
Run-time dependency gtk4 found: YES 4.14.0
Found CMake: D:/downloads/tools/cmake-3.30.1-windows/cmake-3.30.1-windows-i386/bin/cmake.exe (3.30.1)
Run-time dependency appstream found: NO (tried pkgconfig and cmake)
Looking for a fallback subproject for the dependency appstream

..\src\1.4.2-bc9e91710f.clean\src\meson.build:274:16: ERROR: Automatic wrap-based subproject downloading is disabled

A full log can be found at D:\b\libadwaita\x64-windows-dbg\meson-logs\meson-log.txt

Run-time dependency appstream found: NO (tried pkgconfig and cmake)

AFAICS libadwaita requires libappstream now.
https://gitlab.gnome.org/GNOME/libadwaita/-/commit/908d8052bac504536642c14ce84b53e525db2d02
There is no port for (lib)appstream yet.
https://github.com/ximion/appstream
And upstream libadwaita is already at 1.6.0.


fix some typos

Pull Request
Related issue
Fixes #<issue_number>
What does this PR do?

fix some typos

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Hello @cuishuang :wave:
thanks for taking the time to fix typos, this is appreciated 😊
Could you edit your PR to git mv index-scheduler/src/snapshots/lib.rs/register/everything_is_succesfully_registered.snap index-scheduler/src/snapshots/lib.rs/register/everything_is_successfully_registered.snap, because currently fixing the typo in the filename makes it so the snapshot is not found anymore, and the tests fail?
Thanks a lot!

Hello @cuishuang 👋
thanks for taking the time to fix typos, this is appreciated 😊
Could you edit your PR to git mv index-scheduler/src/snapshots/lib.rs/register/everything_is_succesfully_registered.snap index-scheduler/src/snapshots/lib.rs/register/everything_is_successfully_registered.snap, because currently fixing the typo in the filename makes it so the snapshot is not found anymore, and the tests fail?
Thanks a lot!

The command has been executed, please check again

Alright, it is passing now, thank you for contributing ❤
bors merge

My pleasure


Authentication pages of Ping, Keycloak, ADFS, Okta, Shibboleth Rancher API Host field should default to Rancher URL

Navigate to each of these Authentication pages in Dashboard
Observe the Rancher API Host text input is empty.
Expected:
This field should default to the current Rancher host according to: https://github.com/rancher/dashboard/issues/2115
(Compare this with Ember UI It should match)
Example defaults for Keycloak

Rancher version v2.5-head (01/21/2021) 23a29c306

Based on what's in Ember, we should pre-fill in Vue too. Then again, should the URL actually be hidden in both views?

Based on what's in Ember, we should pre-fill in Vue too. Then again, should the URL actually be hidden in both views?

Need to figure out if "undefined" means something breaks. Checking with backend.

Need to figure out if "undefined" means something breaks. Checking with backend.

Rancher version master-head (02/11/2021) 98fe72a
I see the Rancher URL getting set by default in the Rancher API Host field.


Ports in domain name no longer allowed

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug

I am using ports in my listening config. This works fine. But now I want to change the certificate, and it gives me this error
Nginx Proxy Manager Version
2.12.1
To Reproduce
Steps to reproduce the behavior:

Go to 'Proxy host with port'
Click on 'change ssl'
Scroll down to 'Hit save'
See error

Expected behavior
Honor ports previous allowed

After some trial and error I made a proxy host with non-port domain name and put following in advanced:
listen 8085 ssl; listen 9097 ssl; location / { if ($server_port = 8085) { proxy_pass http://<IP_ADDRESS>:8096; } if ($server_port = 9097) { proxy_pass http://<IP_ADDRESS>:80; } }
No clue if this is the best solution, but for now it works.


[BUG] midi.exe received(or showed) wrong UMP event

Applies To
midi.exe(or MIDI services?)
Describe the bug
midi.exe received(or showed) wrong UMP event.
This is similar but different issue from #174.
To Reproduce
We are using ProtoZOA with following firmware.
https://github.com/midi-mma/Amenote_Protozoa/blob/main/Releases/V0.4/ProtoZOA_Main.uf2
ZoA_UUT.uf2.zip
(When "5" button on ProtoZOA, it will send UMP message(Note On) with 500usec interval, "3" means 300usec.)
When ProtoZOA sends continuously UMP MIDI 2.0 Note On messages with interval e.g. 500usec, then it seems that some scheduled messages appeared different UMP event, around 100,000 messages as following screen shot.
It shows "###### HR" and shows unexpected UMP events in after "###### HR", probably those are old events which USB MIDI 2.0 Driver received previously.

Thanks.

We've confirmed with Developer Preview 3(Worked Around https://github.com/microsoft/MIDI/issues/182 also related to message scheduling), same issue still occurred in our environment.

@dmiura If you are seeing this on Developer Preview 3, it's unrelated to message scheduling. Scheduling is bypassed in DP3
I can't reproduce this with any of the commercial MIDI devices I have or the loopback endpoints. Can you reproduce this with anything other than the protozoa?

@garydan42 is it possible that the circular buffer (either the one connected to USB or the one connected to the client) is wrapping around here and resulting in this? I know you've taken pains to ensure that doesn't happen, but I can't think of how else this might happen.

@Psychlist1972 @dmiura
This issue could be reproduced on Roland side with DP3.

I also checked USB log and verified that the messages sent from the device were no problem.
As you can see in the attached screen captures, unexpected UMP messages appear to be just 512 messages ago.
As far as I remember, the size of the buffer between MIDIService and API/Driver was 4KB, so it can store 512 MT4 messages.
I'm not sure but the symptoms may change if you change the buffer size.

@garydan42 @AmeNote-Michael  I've never run into this with the loopbacks, however, so either it's not a client (app<->service) xproc buffer issue, or timing is a component. Is it possible this is related to the messages being put into the buffer from the driver and that queue?

I'm running the same firmware on protozoa and haven't had the out of order messages yet, but I do see what I assume are dropped messages (the second word is not incrementing by 0x1 each time). It started off fine, but higher numbers seem to skip.

(Note, I was capturing to file at the same time, so the latency is higher. Just filed a bug on that)
protozoa-2024-01-15.midi2.txt
As I recall, dropped messages are expected if the client can't keep up with the incoming stream, but these aren't coming fast enough for me to think that's the problem here.

Interestingly, I changed the client buffer size in MidiSrv from 4096 bytes to 512 bytes and the messages are now all coming in at around 300us. The larger buffer was 2x slower. I recall Gary mentioning that possibility in the past.
So far, I'm not seeing any skipped messages, and still no out-of-order timestamps.

I do get bursts of faster messages from time to time. I'm guessing that there's a pile-up and wait somewhere and then in the next timeslice they can all be sent?

But nothing out of order

The downside of small buffers is that messages will be more easily lost if the client or device can't keep up, and there isn't code in there that will wait until the queue frees up.

Finally had a message displayed out of order. Given that the text at the bottom says no messages were received out of order (that's checked in the background thread handling incoming messages), and this is strangely at the last message, this may be a display issue. I'll look into it more. Difficult to repro this, though.

I didn't notice in the earlier screen shots that the index was also out of order. The index is generated in midi.exe.
So, been a long way around saying this is a problem in my code :)
The dropped messages are something else, however. I haven't been able to repro that now, which is annoying.

I've made some significant performance changes to the console monitor. However, I cannot repro this specific issue at will to know if it will address it or not.
I can say that if I press "1" on the ProtoZoa, I get messages that are all around 100 microseconds from message to message (there's definite jitter there, but it's in the +/- tens of microseconds) and I haven't had any dropped messages or messages received out of order.

If this fixes the issue, the problems were all in the display, not in the data path between the service and the client. However, again, I can't repro the original problem at will, so I will await your feedback once you try this change.
Can you try this release preview, please?
https://github.com/microsoft/MIDI/releases/tag/dev-preview-4-daily1

@Psychlist1972
I have tried to install DP4 after uninstalling DP3, but I couldn't.
Setup failed with the error below:

Any advice?

@Psychlist1972 I have tried to install DP4 after uninstalling DP3, but I couldn't. Setup failed with the error below:
Any advice?

It's presumably because a component didn't register during install. I've only see this when something stuck around from before. May need to do a manual cleanup. Sorry about that.

Ensure you don't have the console app actively monitoring an endpoing. If you do, exit it.

Uninstall the previous release from Apps > Installed Apps in Settings.

After that, check the Windows Services Console (search->Services) and see if "Microsoft MIDI Service" is still listed. If it is, right-click it and choose "Stop"

Then go into %ProgramFiles%\Windows MIDI Services and if it exists, delete all three subdirectories. (Will require administrator permission)

Those steps should clear up anything that was lingering around.

Re-run the latest installer.

@Psychlist1972
Thank you for your suggestion.
In my case, there is no installed MIDI Service, no running service and no installed files under %ProgramFiles%.
However, the installer still fails.
But it's okay, I will re-install windows.
It may take an hour, but for me it's not a pain. ;-)

@Psychlist1972 Thank you for your suggestion. In my case, there is no installed MIDI Service, no running service and no installed files under %ProgramFiles%. However, the installer still fails. But it's okay, I will re-install windows. It may take an hour, but for me it's not a pain. ;-)

Oh! Sorry. I do hope it works after you reinstall. I'll be up for a couple more hours if you need anything.

@Psychlist1972 Thank you for your suggestion. In my case, there is no installed MIDI Service, no running service and no installed files under %ProgramFiles%. However, the installer still fails. But it's okay, I will re-install windows. It may take an hour, but for me it's not a pain. ;-)

Andrew also mentioned having issues with the install from this one. I'm testing in a VM now, and assuming there's something broken in the installer, I'll put out an update.

@m-komo
It was a bad installer file. I'm so sorry.
Updated installer here
https://github.com/microsoft/MIDI/releases/tag/dev-preview-4-daily1

@Psychlist1972
Thank you for updating the installer.
I successfully installed it on my PC.
Then I checked whether the issue persists and there were no out of order messages.
It seems the issue has been solved.
However, the message displayed by the monitor command is very slow.
The device sends a message every 500 microseconds, so you should have received 10,000 messages after 5 seconds.
But the message displayed on the monitor was about 300 messages.
Is this a limitation due to this fix?

@Psychlist1972
We've installed updated installer and confirming the issue again.
As m-komo commented, monitor command is very slow...

@Psychlist1972
Thank you for updating the installer. I successfully installed it on my PC.
Then I checked whether the issue persists and there were no out of order messages. It seems the issue has been solved.
However, the message displayed by the monitor command is very slow. The device sends a message every 500 microseconds, so you should have received 10,000 messages after 5 seconds. But the message displayed on the monitor was about 300 messages.
Is this a limitation due to this fix?

There's a limit as to how fast messages can be output to the console. It should be much faster than in the past, but I didn't test overall time. I'll look at overall timing next.

@dmiura  @m-komo
I will look at further ways to optimize the console output speed. There's a limit as to how much can be done there, though.
However, because I had separated capture from display, I was able to add to the summary some information that shows me that the actual messages are being received in time, even if the display isn't keeping up.

That is from pressing "5" on the protozoa. This is from pressing "3"

Bit of a breakthrough here. By splitting out some steps to yet another thread, I was able to get the console to be within 5 or so messages being displayed vs captured.

@dmiura  @m-komo
Please let me know if https://github.com/microsoft/MIDI/releases/tag/dev-preview-4-daily2 fixes this for you. I'll hold off on closing it as complete until then.

@Psychlist1972
I checked the DP4 daily2.
I confirmed that the performance of console output is good and no out of order messages are received.
Thank you!

@Psychlist1972
I checked the DP4 daily2. I confirmed that the performance of console output is good and no out of order messages are displayed. Thank you!

Great, thank you!
@dmiura let me know if you also concur, in which case, I will close this bug as fixed.

@Psychlist1972 @m-komo
We checked DP4-daily2, it was succeeded 100,000 messages transmit with 500usec interval, unfortunately, second transmitting was failed.
We tried several sets of 100,000 messages transmitting, result is as below.
1st transmitting: succeeded.

2nd transmitting: not succeeded, 15 messages were lost.

3rd transmitting: about 40% messages were lost, and receive duration became approximately 1000usec.

@Psychlist1972
Do we need to install everything(OS, Developer Preview, etc) from scratch for testing?
We assume that something cache remained in our environment...

@Psychlist1972 @dmiura
I've never seen this phenomenon "missing messages" with the 500usec interval, but it could be reproduced with the 100usec interval on my PC.

@Psychlist1972 Do we need to install everything(OS, Developer Preview, etc) from scratch for testing? We assume that something cache remained in our environment...

Not in my experience, no.

@Psychlist1972 @m-komo
We checked DP4-daily2, it was succeeded 100,000 messages transmit with 500usec interval, unfortunately, second transmitting was failed.
We tried several sets of 100,000 messages transmitting, result is as below. 1st transmitting: succeeded.  2nd transmitting: not succeeded, 15 messages were lost.  3rd transmitting: about 40% messages were lost, and receive duration became approximately 1000usec.
We'll check again tomorrow.

This is all good information. Thank you. I will look into it.
During this test, did you use Control-C to end the console at all, or did you always use Escape? In the former case, the process is killed and the service buffers do not get cleaned up per #221

(Note that you don't need to use --verbose for the tests. The data will fit on your screen better without it :))

Incorrect data is no longer being received, so closing this issue.
I've created a new issue to track the missing message problem. See #227

@Psychlist1972

During this test, did you use Control-C to end the console at all, or did you always use Escape?

We used Control-C after 2nd transmitting before 3rd transmitting.

@Psychlist1972

During this test, did you use Control-C to end the console at all, or did you always use Escape?

We used Control-C after 2nd transmitting before 3rd transmitting.

Thanks. Note that if you control-C or crash a client app, you usually need to restart the service for things to work reliably. That's not the cause of the skipped messages, but it can cause hang-ups. #221


Clarification on "not ready to use" in README

WARNING: totally not ready to use

Could you be more specific on what is not ready?

It would be much easier to describe what is ready ;) The only thing that is completely implemented is reading parquet file metadata. Reading boolean and string fields are somewhat supported.
On a serious note this package in its current state is completely unusable (hence the WARNING in the README). I am not actively working on this package as I have no use for it currently.
If you are planning to work on a Go package for reading/writing parquet format I will be happy to answer any questions.

Our lives could been so much easier if I wouldn't have to convert these parquet files...


Messaging: Teams Trial

We're introducing a free 14 day trial for the Teams plan. People have to manually enable it via the billing page. When they do, we send an event and trigger an email. After 11 days, we trigger another email with another event.
I want to generally avoid negative messaging here. It's generally more urgent and impactful, but positioning this as what you will lose if you cancel just feels 🤮. So, I'm proposing the following emails to keep it positive.
Day 1

Day 11

Day 14

Flagging @zlwaterfield for approval on copy. If this looks good, all I need to know are the names of the events we trigger for each event -- then I configure and roll this out in Customer.io.

These look great- thank you @joethreepwood! The only thing is that for the third email, they will get charged immediately, so "Scenario 2" won't really work. Maybe just say reach out to us?

Gotcha. Changed that line to "No worries, just get in touch and we'll see what we can do. "

These emails should be able to go in the existing billing campaign

Great. That's all set up and live now. Though FYI we'll need a new method if we keep adding emails using this template method. Customer.io's campaign builder limits you to 20 variations on a path, which is what we're at now.
This is only going to be a short-term limitation. Longer term I want to move these to a new transactional API method (and/or the messaging product) but I haven't started scoping that out yet.


how to use rollup search ?

Hey, guys, I can not found any thing about rollup search after I was viewed all godoc, Can anyone tell my how to perform a rollup search request by using olivere/elastic sdk ?
Thank you !
Which version of Elastic are you using?
[x] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)

What do you mean by rollup search?

Ah, Xpack? Sorry, that’s not implemented yet.

What do you mean by rollup search?

Ah, Xpack? Sorry, that’s not implemented yet.

Yes, I mean the rollup search, OK, I need to found other way.

You can always use Client.PerformRequest, but there’s no DSL.

@olivere Querying from a rollup index is a very essential feature, are there any plans to support it?

@saifat29 I'm accepting PRs. Will create a new tracking issue for it: #1262. But in reality it's basically the Search API with a different endpoint, very easy to use with PerformRequest and the existing DSL for Search API.


Image Biome Provider Alignment/Tile Options

Currently all image providers are unaligned. Possible alignment options to include:

CENTER
NONE (Current default)
OFFSET (specify custom offset X and Y)

Currently all image providers tile. Possible tile options:

TILE (Current default)
CONSTANT (Set a constant biome to use after edge of image is reached)

Implemented in 4.1.0 (align)


Remove warning in vpn-shoot by setting the correct file permissions on tls key.

How to categorize this PR?

/area networking
/kind cleanup
What this PR does / why we need it:
Remove warning in vpn-shoot by setting the correct file permissions on tls key.
OpenVPN complains if the private key is group/other accessible, which it should
not be. This change sets the permissions properly and thereby silences the
warning.
Which issue(s) this PR fixes:
None.
Special notes for your reviewer:
A similar change is not possible (easily) on the vpn-seed-server side as the secret is used by openvpn and envoy proxy, but the latter one is not running as root.
Release note:

Removed warning about the private key being group/other accessible in vpn-shoot

/cc @DockToFuture


FAIR-GPT answers questions on GitHub VS GitLab similarly to Vanilla GPT4

FAIR-GPT
https://chat.openai.com/share/7f62c223-7924-4fc9-a22d-b3fab5a9bc3f
Vanilla GPT4
https://chat.openai.com/share/d9a441ec-50c8-4ca9-b758-28f93c3b1e7f

We need to upload files with knowledge on FAIR software to FAIR GPT.


Check LPUART clock source in STOP mode

Check LPUART clock source before enable it in STOP mode, only LSE could be enabled in STOP mode.
Description

It is to fix the extra power consumption in STOP mode, which consumed by HSI clock.
Fix #8264
Pull request type

[ x ] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change

@Eman869 Did you mean to open this against https://github.com/ARMmbed/mbed-os?

@cmonr I want to create a pull request to fix the power consumption in mbed-os issue #8264. Is the procedure wrong?

@Eman869 It's almost correct. The pull request needs to point to the Mbed OS repo owned by ARMmbed.
A quick way to check if it's correct is to see if it shows up in this list: https://github.com/ARMmbed/mbed-os/pulls


Fix Forge maven URL and provide instructions on how to build

Without the Maven change, builds will fail because forgeSrc.jar is unavailable.
I've also added the EnderCore JAR to .gitignore so it doesn't show up as an untracked file.

The Forestry Maven repository came back. I tested this again and fixed one other Maven issue. It does build now without problems. runClient still has issues because of EnderCore being loaded twice.
This will likely be superseded by #5545 anyways.

So you still cant run it? Is there anything that makes it work?


Removal of METIS breaks linking for EveryLB

Original issue: https://charm.cs.illinois.edu/redmine/issues/479

A surprisingly large number of LB strategies rely on METIS.  Removing METIS from the distribution (http://charm.cs.uiuc.edu/gerrit/#/c/100/) created an EveryLB which will fail during link time without METIS.
Bug went undetected because there is no automated test of EveryLB
A fix for this is implemented in http://charm.cs.uiuc.edu/gerrit/#/c/89/
That patch set was originally triggered by https://charm.cs.illinois.edu/redmine/issues/419
This bug could be fixed without that patch set, but then we'd have to do the same thing twice, in two different ways, for no apparent benefit.

Original date: 2014-04-27 23:47:57

Manually tested and confirmed fixed. Can also explicitly build MetisLB and link/run against that.


Error found on step 3 of "Update control table by copy data tool" section

Step 3 currently reads:
"Go throughput the copy data tool, and it will come up with a new SQL script for you. Rerun the SQL script to update your control table."
I believe that "throughput" should be "through".

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

ID: 1a5cbc6d-82ff-3a69-b00c-22ceb99a4318
Version Independent ID: 29bed67a-6c33-dd39-4770-1da65225ebe6
Content: Build large-scale data copy pipelines with metadata-driven approach in copy data tool - Azure Data Factory
Content Source: articles/data-factory/copy-data-tool-metadata-driven.md
Service: data-factory
Sub-service: data-movement
GitHub Login: @dearandyxu
Microsoft Alias: yexu

@spontello - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


next export - more options

next export is an awesome extension to the toolchain, however id love to see some more options added:

Option to set the '_next' folder - would make integration with Cordova easier
Option to force the output to copy when exporting to another folder (rather than the default 'out' folder).

Excellent work so far though!

You can use assetPrefix config (in the next.config.js) to specify the folder in which _next will be searched, e.g. assetPrefix: '/assets/', and manually move the build/_next folder to the build/assets/_next.

Its not the location of the '_next' folder i was keen to configure it was the '_next' folder itself, Cordova for Android ignores folder with a prefix of underscore (see bug here) and while this is relitivly easy to overcome with some hacks its not ideal.

Actually, it's hard to change at this moment.
Basically using _ is not a bad idea at all. We use _ to mention it's something internal for Next.js.
We can't use /next because, it might be a URL where the user want to put an actual page.
Since that's a bug in Cordova/Android you need to go for hacks.


Better handling of tool dicussions

We recently added guidelines on how to deprecate tools in #224 after a longer discussion in #223.
Since then I have learned a few things the hard way:

Discussions can quickly get out of hand. It is not easy (and sometimes impossible) to find a solution that pleases everyone.
The role of a project maintainer is to keep collaboration constructive and make all contributors feel welcome.

In light of that, I propose the following changes for contributing:

⚠ will be replaced with ℹ. We don't want to spread fear, we want to inform.
As far as possible, project maintainers should be involved in the discussion to come to a fair conclusion.
Discussions around tools will be linked in the README.md.
Please remember that we're all human and we all have the same goal of making Open Source a little better.

I understand the need for a civil discussion, but I fear this is an overreaction. If a tool doesn't support the current version of a language, and there is no hope that it soon will, I would consider its use deprecated. Injecting the tool's author into the discussion is risking a highly biased opinion. I think project maintainers should never be highlighted or called to a discussion. Calling them was the problem.

I don't see why asking the maintainer if their tool is still maintained is a problem.
An opinion is always biased but the goal is to reach consensus.
From that perspective, to only way to reach a common ground is to hear all sides.

We saw what happened when opinions from all sides were requested in the prior issue. It didn't help things. This is not a court of law where justice must be served at all costs. I support getting additional less-biased opinions from expert users, however.

Perhaps tagging tools with language version limitations?  Javascript isn't alone.  Several great C++ linters don't support C++17.

Perhaps tagging tools with language version limitations? Javascript isn't alone. Several great C++ linters don't support C++17.

Good point. Maybe there is a better way by providing more objective information on the tools. Here's hope that #194 brings more clarity in the future.


Use curl to download github artifacts during bloat report

This fixes #32656
I am unsure why the ghapi does not work, however that is a 3rd party library so there may be bugs.
I tried to report a bug to github and during that I wanted to describe reproduction steps in terms of what they documented in https://docs.github.com/en/rest/actions/artifacts?apiVersion=2022-11-28#download-an-artifact ... however it turns out curl actually worked.
Since curl works, just started using that instead.

PR #32666: Size comparison from 7f1413364e012fbf03cdba0aabd2fb73624e9311 to 44b08e8df9a2d54bf2142adf5056922e4164a19e

Full report (3 builds for cc32xx, stm32)

platform
target
config
section
7f141336
44b08e8d
change
% change

cc32xx
air-purifier
CC3235SF_LAUNCHXL
(read only)
583402
583402
0
0.0

(read/write)
207992
207992
0
0.0

.bss
201228
201228
0
0.0

.data
1640
1640
0
0.0

.rodata
86610
86610
0
0.0

.text
494668
494668
0
0.0

lock
CC3235SF_LAUNCHXL
(read only)
628674
628674
0
0.0

(read/write)
208336
208336
0
0.0

.bss
201720
201720
0
0.0

.data
1496
1496
0
0.0

.rodata
107066
107066
0
0.0

.text
519484
519484
0
0.0

stm32
light
STM32WB5MM-DK
(read/write)
601241
601241
0
0.0

.bss
128344
128344
0
0.0

.data
668
668
0
0.0

.rodata
79700
79700
0
0.0

.text
382800
382800
0
0.0


Html wrap attribute setting is not working

This setting is not working in vscode insider though working perfectly fine in stable release

Can you paste a small code example that show the issue?

well this is happening with the any html contnent

Cases

    {{appStore.userData.currentOrganizationName()}}

here label attribute on line 3 should go on to the next line but it doesn't

I can't reproduce on the latest insiders:

Make sure the editor is in HTML mode, and that there's no other extension that took over formatting or the HTML mode.

Tested on Version: 1.88.0-insider
Commit: ae59067554575afaba07640320a26435c8e05175
Date: 2024-04-02T12:32:08.997Z
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>


DateTime.now().timeZoneOffset refresh only after app restart

Steps to Reproduce

Open App
Change TimeZone in System (Windows/Linux/MacOS)
Go back to App check Timezone again and still old one
Restart App and Timezone is finaly that i changed

Hot Reload doesn't work either.
Expected results: DateTime.now().timeZoneOffset refresh after changing timezone in system.

I have a similar problem with my application

Hi @Remigiusz-Ruszkiewicz,
I've just tested with simple code using DateTime.now().timeZoneOffset and see it worked properly.

Demo
https://user-images.githubusercontent.com/104349824/170242875-f0f5c9c2-6221-4487-a06e-acb7a53ecd29.mov

After changing timezone, back to app, invoke setState((){}), and see that the data has changed.
Can you try this sample code on your side?

Sample code

import 'dart:typed_data';

import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';
import 'package:flutter/rendering.dart';
import 'dart:ui' as ui;

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

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Test timezone',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {

  final nowTime = DateTime.now();

  @override
  Widget build(BuildContext context) {
    final nowOffset = nowTime.timeZoneOffset;
    print('nowOffset : $nowOffset');
    return Scaffold(
      appBar: AppBar(
        title: const Text('Test timezone'),
      ),
      floatingActionButton: FloatingActionButton(
        child: const Icon(Icons.save),
        onPressed: () async {
          setState((){});
        },
      ),
      body: Center(child: Text(nowOffset.toString()))
    );
  }

}

flutter doctor -v
[✓] Flutter (Channel stable, 3.0.1, on macOS 12.2.1 21D62 darwin-x64, locale en-VN)
    • Flutter version 3.0.1 at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fb57da5f94 (8 hours ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] Android Studio
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/203.7185775/Android Studio
      Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)

[✓] IntelliJ IDEA Community Edition (version 2020.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.67.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.40.0

[✓] Connected device (3 available)
    • iPhone 13 (mobile) • 2526BC1A-435D-4B08-B99C-44B928F2517B • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4 (simulator)
    • macOS (desktop)    • macos                                • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 101.0.4951.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.1.0-0.0.pre.896, on macOS 12.2.1 21D62 darwin-x64, locale en-VN)
    • Flutter version 3.1.0-0.0.pre.896 at /Users/huynq/Documents/GitHub/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 09987dc00a (3 hours ago), 2022-05-24 18:48:10 -0700
    • Engine revision 7274f79325
    • Dart version 2.18.0 (build 2.18.0-149.0.dev)
    • DevTools version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[!] Android Studio
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/203.7185775/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Community Edition (version 2020.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.67.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.40.0

[✓] Connected device (3 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • macOS (desktop)         • macos         • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)            • chrome        • web-javascript • Google Chrome 101.0.4951.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

@huycozy I tried same code as you and doesn't work
https://user-images.githubusercontent.com/47605818/170255830-3faec226-601b-400f-b88f-49ed0f10c641.mp4
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.0.1, on Microsoft Windows [Version 10.0.19044.1706], locale pl-PL)
[√] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.8)
[√] Android Studio (version 2021.1)
[√] Connected device (3 available)
[√] HTTP Host Availability
• No issues found!

Hi, from your demo video, I found the difference between platforms:

Android, iOS: ✅
Web: ✅
MacOS: ✅
Windows: ❌
Linux (Ubuntu): ❌

✅: No Issue
❌: Issue reproduced

Demo

Linux

https://user-images.githubusercontent.com/104349824/170409218-1a37909b-f2cb-4434-b1a0-1bd0d1aa1c8e.mp4

iOS:

https://user-images.githubusercontent.com/104349824/170409177-70dcc34d-ac0d-48e5-8ab8-d9373f74992e.mp4

MacOS:

https://user-images.githubusercontent.com/104349824/170409178-29eaca1b-dfe7-4f05-a1e9-8069903bb76a.mp4

Web:

https://user-images.githubusercontent.com/104349824/170409181-44902cc7-7c20-415d-a886-e8ae815edd20.mp4

Windows:

https://user-images.githubusercontent.com/104349824/170409185-02322bd1-44c9-4283-bb74-59e4e5c5a885.mp4

flutter doctor -v
[✓] Flutter (Channel stable, 3.0.1, on macOS 12.2.1 21D62 darwin-x64, locale en-VN)
    • Flutter version 3.0.1 at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fb57da5f94 (8 hours ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] Android Studio
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/203.7185775/Android Studio
      Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)

[✓] IntelliJ IDEA Community Edition (version 2020.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.67.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.40.0

[✓] Connected device (3 available)
    • iPhone 13 (mobile) • 2526BC1A-435D-4B08-B99C-44B928F2517B • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4 (simulator)
    • macOS (desktop)    • macos                                • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 101.0.4951.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.1.0-0.0.pre.931, on macOS 12.2.1 21D62 darwin-x64, locale en-VN)
    • Flutter version 3.1.0-0.0.pre.931 at /Users/huynq/Documents/GitHub/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 20a9f1d8d7 (2 hours ago), 2022-05-25 18:43:11 -0700
    • Engine revision 480610ca4c
    • Dart version 2.18.0 (build 2.18.0-149.0.dev)
    • DevTools version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7042882/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[!] Android Studio
    • Android Studio at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/203.7185775/Android Studio
      Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] IntelliJ IDEA Community Edition (version 2020.3.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.67.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.40.0

[✓] Connected device (3 available)
    • iPhone (mobile) • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.5 19F77
    • macOS (desktop) • macos                                    • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)    • chrome                                   • web-javascript • Google Chrome 101.0.4951.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

However, there is a similar issue here #12531 that you can follow up on it for further updates.
Closing this issue as duplication. If you disagree, please write in the comments and I will reopen it.


[FIX] Remove form link. Remove edit profile for logistics

FIX
Objective:

remove link to form and replace with a message
remove edit profile for logistics

Merging on to main. Verbal confirmation to merge w/o review from @fw-noel (on vacation)


Feature - Add/Modify/Delete tags for model resource

Issue 1732, if available:
Description of changes:
Currently tags modification is not supported for model resource . Hence added require changes to support tags modification.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/assign @ryansteakley

/retest

/hold

@rkurduka we have plans to start generating Tag handlers for all the ACK controllers. But nothing stops us from implement some manually if there is urgent need for them :) I left few comments in-line

@a-hilaly  - thanks for update . Yes there was customer ask for this . Issue 1732 has details


iOS: Lockscreen controls play/pause events not triggered. Title not updated

Hello,
I followed the documentation to use this plugin but I am unable to get this plugin to work in iOS 14 (version does not matter).
It works in Android but not in iOS.
I did a bit of debugging and seems like
remoteControlReceivedWithEvent method is never triggered. The title also is not updated in the controls.
Please let me know how I should fix this.
Thanks.

I this I am having the same issue. I too am not seeing any events after clicking pause and play on the music controls. I am not seeing remoteControlReceivedwithEvent being called, but I think this is due to an error in the pauseEvent and playEvent methods. I am clueless with working in Object-C, just started working in it yesterday.
Everything is working as it should in Android my only issue at this time is with iOS. I can get the Title, Cover Art and even the Play and Pause buttons to display correctly on the music controls, but when I click play or pause I get the following message in Xcode terminal:
Invalid callback id received by sendPluginResult
I put some console.log()s in MusicControls.js and some NSLog's in the MusicControls.m file to verify everything is being called in the correct order. per this post #https://github.com/ghenry22/cordova-plugin-music-controls2/issues/12 subscribe() and listen() should called before create(). Below is the logs of messages coming from each method to ensure I am calling things in the right order.
2022-05-25 13:45:44.501378-0700 The History of England[9763:405153] is ready?!?
2022-05-25 13:45:44.501482-0700 The History of England[9763:405153] subscribe called
2022-05-25 13:45:44.501583-0700 The History of England[9763:405153] listen called
2022-05-25 13:46:08.496087-0700 The History of England[9763:405153] Will use resource 'https://domain.com/audio.mp3' from the Internet.
2022-05-25 13:46:08.515953-0700 The History of England[9763:405153] create called
2022-05-25 13:46:08.527015-0700 The History of England[9763:405153] currentPodcast is changing...
2022-05-25 13:46:13.520159-0700 The History of England[9763:405323] Playing stream with AVPlayer & default rate
2022-05-25 13:46:13.543021-0700 The History of England[9763:405153] MEDIA_RUNNING
2022-05-25 13:46:17.365420-0700 The History of England[9763:405153] Invalid callback id received by sendPluginResult
2022-05-25 13:46:25.683562-0700 The History of England[9763:405153] Invalid callback id received by sendPluginResult
2022-05-25 13:46:29.396358-0700 The History of England[9763:405153] Paused playing audio sample

Any input or advice as to why event notifications are not being sent to the callback?

What I've noticed here, on iOS 12 fwiw, is that this happens only when destroy was called. Because then, latestCallBackId is set to nil, and never restored (by watch: command).
My workaround, which seems to work for now, is to never destory the MusicControls (which is much less an issue than on Android, I believe).

I reworked my entire app into a simpler demo for sharing and seeking help on a freelance site. When I did I found my app worked as it should.
I believe my issue was in the way I was using Vue and Vuex to achieve my app. I was using the store for all of my functionality. Once I moved that functionality (and reworked my logic) into my component and only used the store to track state and not functionality my issue was resolved.

@stoi2m1 -- interesting, thanks. I solved some issues on the Android side, which might be related, by strictly enforcing the async-ness. I also have a rather complex Vue/Vuex app and this helped for the time being. Got this idea from https://github.com/ghenry22/cordova-plugin-music-controls2/issues/41#issuecomment-786956913

What I've noticed here, on iOS 12 fwiw, is that this happens only when destroy was called. Because then, latestCallBackId is set to nil, and never restored (by watch: command). My workaround, which seems to work for now, is to never destory the MusicControls (which is much less an issue than on Android, I believe).

I'll look into this and see what is happening there, thanks for the info.
At the same time though I use this plugin extensively on iOS and have not seen this issue at all (I do call destroy).  Was this specifically with iOS12 or did it persist for you with later iOS updates?