performance: added schema reused based on content

for usage patterns where the same instance is registered regularly, the
increase in memory pressure is measurable and can cause Karapace to be
OOM'ed. This commits improves the situation by reusing existing schemas
based on their content, instead of having multiple copies of the same
schema in memory.

@tvainika unfortunately yes, we had an issue for this https://github.com/aiven/karapace/issues/283 ,  which I tried to fix with https://github.com/aiven/karapace/pull/284 , but it was reverted with some other modifications by https://github.com/aiven/karapace/pull/295 due to issues with duplicated global IDs.
This PR doesn't try to fix the memory leak, just optimize the memory usage.


Turned off autocomplete on search input

Can you add the label "hacktoberfest-accepted" to my PR please?


Events part 1: events section under community page

Part of #541
This is supposed to show the first three events in the community page under the "Events" section, but the API is broken so can't see it for real at the moment. The best alternative is to check Storybook for now.
Desktop

Mobile

Frontend checklist

[x] Formatted my code with yarn format && yarn lint --fix
[x] There are no warnings from yarn lint
[x] There are no console warnings when running the app
[x] Added any new components to storybook
[x] Added tests where relevant
[x] All tests pass
[ ] Clicked around my changes running locally and it works
[x] Checked Desktop, Mobile and Tablet screen sizes

Had to fix a merge conflict 😢


[Editor] Allow the user to add and save an alt-text for images (bug 1844952)

/botio-linux preview

/botio-linux preview

Possibly better suited for a follow-up: Looking at the specification it appears that the text-color of the textarea should become "greyed out" when Mark as decorative active, and that doesn't seem to happen currently.

There's potentially one (small) problem with positioning the dialog absolutely in the way that we're doing here, which is that if the browser window is resized to become smaller after the dialog has been opened (I happened to trigger this by opening the devtools) then part of the altText dialog will be invisible/inaccessible.
One possible, simple way, around that might be to pass in the eventBus to the AltTextManager and add a listen for "resize" on it and reset the dialog left/top values to auto if a resize event occurs while the dialog is open?

There seem to be some problem with the dialog position in RTL-mode, since its right side is always aligned with the right edge of the browser window:

It's strange: nothing happens if I change left in devtools but if use right instead it's ok.
I tried to write a basic test case but everything works fine.


Fix IsoDatastore using OvirtServices::Strategies

OvirtServices::Strategies::[V3, V4] was removed and now there is only
OvirtStrategies::V4.
Caused By: https://github.com/ManageIQ/manageiq-providers-ovirt/pull/423

Also, shouldn't this be in the providers-ovirt repo @borod108 ?


Use ReadLine to be able to work with long lines

Similar to PR #502, this commit switches from using bufio.Scanner to
bufio.Reader. See #502 for more information.
I hope you don't mind that I changed the massive if else chain to a switch-statement - if you do, I'll revert it 🙂
Signed-off-by: Ramon Rüttimann<EMAIL_ADDRESS>

Looks like a few of the parser unit tests failed due to whitespace differences in the fixtures. E.g., TestBasicExample

Ah yes, forgot about the newline 🙂
Should be working now.

Thanks for the update! Just kicked off another build.

The build failed, but for an unrelated known flaky test so will go ahead and merge this in. Thanks for the contribution!


improvement Composite predicate supports range predicate when rewritting by materialzied view

Proposed changes
It supports predicate composite as following:
materialized view define

   select l_shipdate, o_orderdate, l_partkey, l_suppkey
   from lineitem_1
   left join orders_1
   on lineitem_1.l_orderkey = orders_1.o_orderkey
   where l_shipdate > '2023-10-19'

the query as following can be rewritten by the materialized view above

   select l_shipdate, o_orderdate, l_partkey, l_suppkey
   from lineitem_1
   left join orders_1
   on lineitem_1.l_orderkey = orders_1.o_orderkey
   where l_shipdate > '2023-10-25'

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall


Turn beluga_ros into a Python package

Proposed changes
Precisely what the title says. A small addition to #332.
Type of change

[ ] 🐛 Bugfix (change which fixes an issue)
[x] 🚀 Feature (change which adds functionality)
[ ] 📚 Documentation (change which fixes or extends documentation)

Checklist

[x] Lint and unit tests (if any) pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] All commits have been signed for DCO

Can we address the merge conflict so we can merge this?

Ready to go @serraramiro1.


[Exploit?/Intended?] Possible to attach a fourth functional Venting Port to a Smelter

Under "normal" circumstances, it is only possible to attach up to three Auxilliary Venting Ports to a Smelter, which together remove approximately 70% of the Flux generated by smelting Essentia. Attempting to attach a fourth Venting Port to the front face of a Smelter simply fails to place the Port.
By using a tool which can rotate blocks, commonly found in other tech mods (e.g. Wand of the Forest from Botania, Wrenches from assorted mechanical/technical mods, etc), it is possible to place a fourth Venting Port by rotating a Smelter to face a direction which already had a Port, then placing the fourth Port on the newly exposed "side". All four Venting Ports are then functional, reducing the Flux generated by the Smelter by another third, resulting in just over 80% of Flux removed.
This is not necessarily a bad thing - the additional Flux reduction is small, and even at the minimum Essentia cost of 10 Essentia per unit of condensed Flux, Flux Condensers still require a large fraction of all Essentia smelted to go right back into Flux Condensers just to run at a Flux-neutral level, even with three (or four) Venting Ports. (For example, with a Thaumium Smelter with three Ports, for every 100 units of Essentia input, 4.44 units of Flux will be released, consuming 44.4 units of Essentia in a Condenser, resulting in almost 60% Essentia loss. A fourth Port reduces this to 45% Essentia loss.) However, it does appear to be unintended behavior.

Definitely an exploit

You don't need another mod's wrench to do this - you can break and replace the smelter in a different rotation without detaching the port.

@Ulysses2  I had assumed that breaking the Smelter would also break any Venting Ports attached to it. Clearly, that is not true - post updated to include this even-easier-to-use exploit.


The electron platform is deprecated

Hi!
I have an Ionic app and now I was deploying to Windows using Electron.
When I ran the command npx cap add electron I received the warning The electron platform is deprecated!
What is the reason for this warning? Is there a better alternative?

Hi @JoaoEdu93,
npx cap add electron is deprecated. Instead please refer to the documentation of the community version of the electron platform.
See: https://capacitor-community-electron-docs-site.vercel.app/getting-started

Anyone looking for a solution for "deprecation warning of electron" and switching to the community version see the steps here


NPE when persistPositionToLedger

Search before asking

[X] I searched in the issues and found nothing similar.

Version
Master branch
Minimal reproduce step
ReplicatorTest#testReplicatorWithFailedAck
What did you expect to see?
No NEP.
What did you see instead?
org.apache.bookkeeper.mledger.ManagedLedgerException: java.lang.NullPointerException
Caused by: java.lang.NullPointerException
	at java.util.Objects.requireNonNull(Objects.java:208) ~[?:?]
	at org.apache.bookkeeper.mledger.impl.ManagedCursorImpl.persistPositionToLedger(ManagedCursorImpl.java:2814) ~[classes/:?]
	at org.apache.bookkeeper.mledger.impl.ManagedCursorImpl.internalMarkDelete(ManagedCursorImpl.java:1968) ~[classes/:?]
	at org.apache.bookkeeper.mledger.impl.ManagedCursorImpl.internalAsyncMarkDelete(ManagedCursorImpl.java:1911) ~[classes/:?]
	at org.apache.bookkeeper.mledger.impl.ManagedCursorImpl.asyncDelete(ManagedCursorImpl.java:2226) ~[classes/:?]
	at org.apache.bookkeeper.mledger.impl.ManagedCursorImpl.asyncDelete(ManagedCursorImpl.java:2030) ~[classes/:?]
	at org.apache.pulsar.broker.service.persistent.PersistentReplicator.lambda$deleteFailed$4(PersistentReplicator.java:645) ~[classes/:?]

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

It seems to be a flask test, I will fix it.

Closed.
See https://github.com/apache/pulsar/pull/20096 and https://github.com/apache/pulsar/pull/20096#discussion_r1169428743.


Break out novels from short stories on wanted list

As requested in the Fritz Leiber Short Stories email chain, this moves any "short fiction" entries from "first production" section to "moderate". It also adds an entry for each specific novel (40K words or longer) that is available on Project Gutenberg for those authors.
Note that Fritz Leiber doesn't have any novels on PG, only short stories and novellas.

Excellent, thanks!


[DONT MERGE] v0.1.18-2

Upgrade to latest polkadot-v0.9.29 https://github.com/paritytech/substrate/commit/cc370aa61e15c18d23a2f686b812fd576a630afe

https://github.com/Phala-Network/khala-parachain/commit/e980c45ad31e63523eae2809c3d9ab94bb25636d

Port https://github.com/Phala-Network/phala-blockchain/pull/991

https://github.com/Phala-Network/khala-parachain/commit/14bb03f77ad916acccc7db9f50a4f2045e5fab86

Change version to v0.1.18-2 as a maintaince version

This PR only for CI, when green, tag latest https://github.com/Phala-Network/khala-parachain/tree/v0.1.18-maintaince commit as v0.1.18-2 then make new release

Ah this shouldn't merge to main...

CI passed


[SU-213] Refactor leave workspace modal, allow leaving groups

Heads up to reviewers- it looks like Identiteam rolled back Sam by a few commits (including the one that added support for this), so you won't actually be able to test this right now...
Deleting managed groups is now supported: https://github.com/broadinstitute/sam/pull/807
Switched the trash icon into a three dot menu that now displays Leave and Delete options.
Also refactored the LeaveWorkspaceModal into a generic LeaveResourceModal.
Before:

After:

<!--
Hello, friend!
Remember to mention what sort of testing/verification you performed in the course of building this PR, i.e. checking functionality in the browser locally.
Also, so if a screen recording [1] and/or screenshots would be a helpful way to communicate context, please consider including some in your PR description.
Thanks!

[1] https://support.apple.com/guide/quicktime-player/record-your-screen-qtp97b08e666/mac
--!>

@MatthewBemis Are things working in Sam now?

@cahrens yeah it looks like the required Sam changes are back on dev now so this should be good to test/review

@cahrens unfortunately we can't know ahead of time if it's possible to leave a group or not. This is the same UX as leaving workspaces. We could implement a new Sam endpoint to do that check in the future

heads up that this is gonna sit around until monday or tuesday, depending on when the monolith is released


Added a proof-of-concept for async loaded images from the web

using https://github.com/AvaloniaUtils/AsyncImageLoader.Avalonia
If you want this as an extension to Fabulous.Avalonia, I can try to encapsulate it into a separate project similar to the existing Fabulous.Avalonia.ItemsRepeater

@edgarfgp I prefer the second option - easier to find for everyone and less work for me :)
I'd also love your help getting the implementation right and the API consistent with that of Fabulous Avalonia. I don't understand the difference between Fabulous' different Attributes.define* helpers yet. Or how to decide which options to expose in a builder vs. in extension methods - because not all existing ones are intuitive to me.
Let me know how you'd like to proceed. If you set up a GitHub repo, I'm happy to convert this into a library with a sample project, and either create a PR or push to it.
I'd also like your feedback on the naming. Is AsyncImage a good widget name? Does it conflict with a part of the ecosystem I don't know about? I derived it from the name of AsyncImageLoader.Avalonia, but didn't to put the -Loader suffix in the name - because the widget effectively renders an image, not a loader.
And what would be a good name and default namespace for the project? Note that the library also features the AdvancedImage control and the ImageBrushLoader attached property, both of which I haven't wrapped in my sample.

I think we ca use the AsynImage from Avalonia.Labs https://github.com/AvaloniaUI/Avalonia.Labs
The Idea is to have a dedicated nuget Fabulous.Avalonia.Labs where we can wrap this controls to our DSL and use these.
Note that this controls are experimental in Avalonia itself where some of these might make it to Avalonia.Controls itself.

@edgarfgp Yes, the AsyncImage from Avalonia Labs seems to offer similar functionality. I just investigated how to configure the cache folder and updated your example to use caching.

Thanks @h0lg moved the caching logic to init function and run it using Cmd.ofEffect

I think if you are happy with this we can merge it as it is and I will work on adding the rest of control wrappers in separate PRs.

@edgarfgp Comparing the branch to the master, I've just reverted some left-over changes in the Playground.
I also notice the branch adds many new .json files, presumably Lottie animations, without actually wrapping the Lottie control.
Are you sure you want to include all, if any of them in this merge?

@edgarfgp Comparing the branch to the master, I've just reverted some left-over changes in the Playground. I also notice the branch adds many new .json files, presumably Lottie animations, without actually wrapping the Lottie control. Are you sure you want to include all, if any of them in this merge? Otherwise I could rebase the branch on the master and strip out the unnecessary bits.

It is ok to leave the extra files. I’m using these https://github.com/fabulous-dev/Fabulous.Avalonia/pull/272


Clean up application

Since the prototype was written in a rush, we need to move out components and clean them up.
This means creating smaller components of some of the bigger ones as well as moving logic outside of components to be re-used.

This has mostly been done as our application is plenty clean. A few things left do are adding stronger typings (tracked in #1). I will track model creation etc. on that. Closing.


[spi_devce] Fix Intercept assertion

Addressing #13934
Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

@eunchan I made a quick fix as I proposed in the issue. PTAL


charm++/delegation/multicast test fails with randomized queues due to a bug in support for anytime migration

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

See parent task for full details.

Original date: 2015-10-26 20:00:50

The multicast itself is working fine with randomized queues.
The bug here is in the interplay of section multicast and anytime migration.  This test makes an array section and then multicasts.  In the multicast target entry method it then does contribute, contribute, contribute, migrate. It deliberately creates the pathological case of every element migrating during a multicast/reduction.
Cutting the number of reductions down to 1 per multicast does not fix the problem.  This is not as reported in the comments for (#120), the bug is not due to consecutive reductions without an intervening multicast.  The subject line has been amended accordingly.
If you comment out the migration, there is no bug.  Consecutive reductions work just fine in the absence of migration.


Systemd-boot loader takes very long to start

Describe the bug
When updating my system about 2 weeks ago, systemd-boot suddenly started up very slow.
I'm not quite sure yet which commit is to blame, but here are the results of systemd-analyze time:
Startup finished in 11.716s (firmware) + 22.115s (loader) + 7.347s (kernel) + 7.766s (userspace) = 48.945s
graphical.target reached after 7.766s in userspace.

22 seconds for loader... I have a powerful system booting from an NVME drive, with a Ryzen 9 5950X CPU and 4000MHz RAM, so these results are quite unexpected.
My thinkpad T470, which is significantly slower, still takes 7 seconds to start loader, but in my experience that's also slower than it used to be.
My bootloader config is simply
boot.loader = {
      systemd-boot.enable = true;
      systemd-boot.configurationLimit = 5;
      efi.canTouchEfiVariables = true;
    };
};

Steps To Reproduce
Unsure yet. I have done a full wipe of my drive, cleared BIOS CMOS and then reinstalled my system, yet same result.
Expected behavior
I expect the systemd-boot bootloader to start within like 3 seconds.
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.0.13, NixOS, 23.05 (Stoat), 23.05.20221218.04f574a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.12.0`
 - nixpkgs: `/nix/store/v3h6hhxf4f5l5ix3p70jap046zl2plm1-source`

cc @flokli @Kloenk @Mic92

Can you check what version of sd-boot you have installed?

Can you check what version of sd-boot you have installed?

version 252.1

Hm, this could be https://github.com/systemd/systemd-stable/commit/1c9e7fc8f28347e7151baa7163f0d5bb2cdb9611, which is included in 252.3 and upwards.
252.3 should be in staging, and 252.4 comes with https://github.com/NixOS/nixpkgs/pull/207119. Can you check with one of these versions? You should be able to just invoke bootctl install from one of these builds, without having to rebuild the world.

Can you force merge staging into master?
252.1 is still preventing Macbooks from booting.

This should be part of the next staging-next cycle. cc @vcunat

Solved with the systemd 252.4 update. Loader start time is now 2.233 seconds.


Look at review comments for approval

Currently fourth wall only turns a PR green if a normal comment has a thumbs up. Github now has review comments, which are different.
In a review you can mark the PR as approved. This PR adds a new backbone model which checks review comments for the APPROVED state. If found the thumbsup class is added to the pull-view, in the same way that is done for a normal comment with a thumbup.

Thanks Chris! Will take a look at those comments. I've added a couple more commits, as we realised there was an issue with if someone requested changes then later thumbsed up; it wouldn't reflect on the wall.
I did look for an API endpoint I could hit for the PR's status rather than doing the logic I've done on the reviews response, but couldn't find one. If you don't mind taking a look, that'd be awesome.

Also, if you want to use this stuff before it's merged to this repo, I've forked it and have my version hosted here: https://wynndow.github.io

I’m happy with the changes in 762f69c and d5985a0. Let me know if you need help finding someone to merge this.

I may well need that help I think...do you know who looks after this repo?


3 machine learning research papers added

Closing this because now we are tracking this as part of https://github.com/vicky002/AlgoWiki/pull/339 after resolving all merge conflicts.


Error :Could not import _ext module.

Dear @zeliu98
Thank you for your code.Here I meet a problem:(Could not import _ext module. )while training. (shown as below)
Traceback (most recent call last):   File "function/train_s3dis_dist.py", line 24, in <module>     from models import build_scene_segmentation   File "/home/yeminglang/project/CloserLook3D/pytorch/models/__init__.py", line 1, in <module>     from .build import build_classification, build_multi_part_segmentation, build_scene_segmentation   File "/home/yeminglang/project/CloserLook3D/pytorch/models/build.py", line 4, in <module>     from .backbones import ResNet   File "/home/yeminglang/project/CloserLook3D/pytorch/models/backbones/__init__.py", line 1, in <module>     from .resnet import ResNet   File "/home/yeminglang/project/CloserLook3D/pytorch/models/backbones/resnet.py", line 3, in <module>     from ..local_aggregation_operators import LocalAggregation   File "/home/yeminglang/project/CloserLook3D/pytorch/models/local_aggregation_operators.py", line 13, in <module>     from pt_utils import MaskedQueryAndGroup   File "/home/yeminglang/project/CloserLook3D/pytorch/ops/pt_custom_ops/pt_utils.py", line 10, in <module>     "Could not import _ext module.\n" ImportError: Could not import _ext module. Please see the setup instructions in the README: https://github.com/erikwijmans/Pointnet2_PyTorch/blob/master/README.rst
Can this problem be solved by
pip install "git+git://github.com/erikwijmans/Pointnet2_PyTorch.git#egg=pointnet2_ops&subdirectory=pointnet2_ops_lib" ?
I have no idea because I can't download this package properly :( ...
Or there is another things going wrong?
python=3.6
pytorch=1.5
cuda=10.1
pillow=6.2.1
Your prompt reply is looking forward!
Best wish!
Your sincere : yeminglang

I have the same problem, have you solved it？


Wrong default INTERFACE

Summary
The README says that the default for INTERFACE is notebookbar but install/assets/defaults/10-coolwsd set it to classic on its line 42.
Steps to reproduce
Don’t set INTERFACE env var.
What is the expected correct behavior?
README and install/assets/defaults/10-coolwsd should have the same default value.

Thanks for the feedback - this has been resolved with https://github.com/tiredofit/docker-collabora-online/commit/99d2163aae6c5f4c1aae4b8ffc77d47e451ac775 - It really should be notebookbar.


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 5659878, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 8238 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in a66b6b9.


[e2e]: container tag main registry-username-secret

Repo: https://github.com/slsa-framework/example-package/tree/v31.0.518
Run: https://github.com/slsa-framework/example-package/actions/runs/10650514747
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.main.registry-username-secret.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.main.registry-username-secret.yml
Trigger: push
Branch: v31.0.518
Date: Sun Sep  1 03:12:40 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v31.0.519
Run: https://github.com/slsa-framework/example-package/actions/runs/10660024005
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.main.registry-username-secret.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.main.registry-username-secret.yml
Trigger: push
Branch: v31.0.519
Date: Mon Sep  2 03:09:40 UTC 2024
Tests are passing now. Closing this issue.


The client doesn't return correct value when used with unleash-edge

Describe the bug
We have a toggle in three environments (dev, test, prod). The toggle is turned on (100%) in dev, and off (0%) in test and prod.
We use a token with access to the dev environment. When we configure the client to use unleash directly it works as expected and the toggle evaluates as true, but if we change the url to our unleash-edge instance, it evaluates as false.
I have recreated it with the "Synchronous startup" example. I thinks this is an issue with the dotnet client, as when i test the golang package with the same token and url using the SimpleUsage example here, it works as expected.
I have also tried calling /api/client/features on the unleash-edge instance directly with the same token, and it returns the flag with "enabled": true.
To Reproduce
Steps to reproduce the behavior:

Create a toggle in three environments
Enable the toggle in one environment
Create a token for that environment
Deploy an unleash-edge instance
Configure the client to use the token and unleash-edge, check if the feature is enabled using unleash.IsEnabled
Change the url to use unleash without unleash-edge and try again

Expected behavior
I expect the client to return the same value as configured upstream and as returned by other clients.
Screenshots
Additional context
This is using version 3.3.3 of the client and v13.0.0 of unleash-edge.
The unleash-edge deployment basically looks like this:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: unleash-edge
  namespace: unleash
spec:
  selector:
    matchLabels:
      app: unleash-edge
  template:
    metadata:
      labels:
        app: unleash-edge
    spec:
      containers:
      - name: unleash-edge
        image: docker.io/unleashorg/unleash-edge:v13.0.0
        args:
        - edge
        env:
        - name: UPSTREAM_URL
          value: "https://eu.app.unleash-hosted.com/OUR_UPSTREAM_URL"
        ports:
        - containerPort: 3063
          name: http

This is tested both with and without setting a SERVICE_ACCOUNT_TOKEN environment variable.

Hi @JonasBak , thanks for bringing this to our attention.  I will try to reproduce, investigate and get back to you

Hello @JonasBak, thank you for bringing this up.
I had a look at your repro steps and failed to reproduce this locally. I've also had a conversation with one of the edge devs.
From what I can tell edge works as it should. I also took a look at your update with the diff in the returned JSON, but there's nothing there that stands out. I think a good next step is to validate any constraints that may have been put on your strategy, appname for instance, against what is being defined in your apps.
Also:

I have also tried calling /api/client/features on the unleash-edge instance directly with the same token, and it returns the flag with "enabled": true.

The "enabled" property here does not reflect the result of feature flag evaluation, which happens inside the Unleash .NET Client SDK based on the defined parameters, constraints, strategies, and provided context from host application

Thank you @JonasBak, that's interesting. If you can, please keep us posted on your findings!

I've been able to reproduce the issue locally using caddy and edge.
docker run --rm -d -p 3063:3063 -e "UPSTREAM_URL=https://eu.app.unleash-hosted.com/OUR_URL" -e RUST_LOG=DEBUG docker.io/unleashorg/unleash-edge:v13.0.0 edge
caddy reverse-proxy --from http://localhost:8080 --to http://localhost:3063

When using http://localhost:3063/api/ (edge directly) it works, but http://localhost:8080/api/ (through caddy) it doesn't. (both work with golang)
My best guess atm would be that it's somehow related to the headers UNLEASH-APPNAME and UNLEASH-INSTANCEID. It seems like the dotnet client uses the headers in all caps, but caddy and nginx rewrites them to Unleash-Appname and Unleash-Instanceid.

Hello @JonasBak, thank you for these repro steps. We were able to reproduce and found that edge does not send back etag when content is gzipped. We have a PR on the way that should fix the issue

Thanks @daveleek  🙌
I've not been able to test v13.1.0 as when i start the container it exits with the following message:
/unleash-edge: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

Thank you @JonasBak - we're looking into it and will get back to you when we have a fix

Hey @JonasBak, we had an issue in our build which produced a broken docker image. We've uploaded a new 13.1.0 image over the broken one, which should fix this. Apologies for the trouble here!

Nice, I've checked that the new version works in our setup, so I'll close the issue 🎉


Replace 'out of capacity' by 'node allocation failure'

This might lead to some temporary glitches during infrastructure upgrade, but I don't think it's worth doing something more complicated.

Users of OutOfCapacityException in internal repo also need to be updated (build is broken now)


Add support for tc actions

This work has been on my fork a couple month now, and I had a conversation with @alessandrod about this when he said he would like to add support for tc programs, that is also almost a month ago now... Forgive my laziness but anyway here I am ready to kick off this effort.
You can see in this PR that I've moved the SkBuff out of the socket_filter module, since tc programs use it for input as well, and (I believe) I followed existing example for other shared data structures for probes. I also plan to add a few more utility functions in SkBuff for example to test for specific protocol, and jump to packet data start - since IP and TCP header has some peculiar header length calculation that I spent quite a while to figure out.
I picked the macro name tc_action because as I understand, there're also "classifiers" for tc, although I haven't really figure it out what they do or whether they're really different than "action" programs. As far as I remember, they have different return codes, so I believe it makes sense to separate them based on that.
Note with only this PR, the output ELF still cannot be loaded by tc. At least two problems that I've found workarounds:

Strip .text section
Rename maps section

As a complete working example, you can see this project, and the workarounds are codified here.
I think it's possible that we integrate these extra LLVM tools, but I'd like to see your opinion first. Also I'd really like to understand what's in the .text section anyway...
Another potential issue is how to use multiple maps if tc only expects a single section, though it might not be an issue but I don't think I've tried it.
On a sidenote, I submitted a lightning talk on exactly this work for the eBPF summit, and it got accepted, I'd really appreciate it if you would like to see my draft (I need to prepare a recorded video before Friday).

Hey, it's great to see this, thanks!
I'd be happy to review the talk draft, if you message me here or on Twitter, my DMs are open.

I think both issues can be fixed without incompatible changes to the current toolchain.
The .text section has to do with https://github.com/alessandrod/redbpf/blob/685c51862f58d89b399958e1cb126fa325fb4059/cargo-bpf/src/llvm.rs#L182. Since we have no way to provide the library info, and since we ask rustc to do the first step of the compilation for the host target triple, llvm ends up thinking that the target provides bcmp when it doesn't. So to make things work we inject our own bcmp (and other builtins), that end up in .text. I'm working on a workaround for this right now.
The map thing we just need to decide the API. Currently #[map("foo")] outputs an ELF section named "maps/foo". we could have #[map(name="")] or something to output just "maps".

Just remembered, I believe tc also supports attaching already loaded programs - which means it doesn't need to interpret the ELF file by itself - so maybe we can also just provide/extend our loader to load the program and maps and don't necessarily need to "fix" the ELF file?

Let's move this loader discussion to #56 . I'm merging this. Thanks both!


Fix Path Separator in Service Workers

The path separator generated by path.relative varies depending on the operating system. Such generation can cause created service workers to have a back-slash in keys of RESOURCES instead of a forward-slash, which can cause strings to become improper, thus making the JavaScript file error creating.
This fix converts the generated path to URI again to create a string that is consistent across operating systems.

@googlebot I signed it!

This is great! But it needs a test - there should be something under targets/web_test that is related

@jonahwilliams Would modifying test('WebServiceWorker generates a service_worker for a web resource folder', ...) to create a.txt as a/a.txt suffice? Currently it creates at execution level instead of a subdirectory.

Yeah, that sounds like a reasonable addition

@jonahwilliams Done


Implement source subcommand

Relates to #60

I'm wondering about the best way to interact with the Knative plugin in the e2e tests 🤔
Shall I invoke the binary with exec, execute the cobra.Command or something else?

LGTM
The only thing I have feedback for is to  check what the client can already do with any source object, they had some plans to make it "easy" to make sources and they do some dynamic lookup stuff from the CRDs labeled source. So this might introduce a second way with the same client...


DownloadBuildArtifactsV0 does not download the latest successful build

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: DownloadBuildArtifacts
Environment

Agent - Hosted or Private: Hosted

If using Hosted agent, provide agent queue name: windows-2019

Issue Description
We have a multi stage pipeline that has a pipeline resource defined. We have manually kicked off this pipeline and after it has deployed to the first stage, we have noticed that the DownloadBuildArtifacts that is being injected into the pipeline has not downloaded the most recent successful build for the pipeline resource.
We have noticed that if when we run the pipeline, click on "Resources" in the panel, and click on the pipeline resource, the correct build is being selected by default. This does not seem to be the case when we run the pipeline but do not click on "Resources".
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]

@romil07 are you taking a look at this? Wasn't sure if this is an artifact issue we need to look at

@leantk I and harshini from my team looked at it but we couldn't repro this or find anything that could cause this issue.
This is pretty simple flow. We call the builds API from pipeline provider and just rely on what API returns. We tried finding the logs to see in the execution flow of that API but didn't find anything.
This issue is not a task issue is what I am saying. We can discuss if you feel the need.

This issue has been resolved. Thank for your help!


🥼 Add gh actions to perform CI tests, verify builds, etc

https://github.com/axi0m/ratatoskr/pull/40


Add p2p listener port options for reth node

Describe the feature
Currently NetworkArgs does not include any option for changing the p2p or discovery port:
https://github.com/paradigmxyz/reth/blob/a0f195590c5b0bc5d7b32a9f449db80aac7018e7/bin/reth/src/args/network_args.rs#L12-L48
The inner DiscoveryArgs does not have this option either:
https://github.com/paradigmxyz/reth/blob/a0f195590c5b0bc5d7b32a9f449db80aac7018e7/bin/reth/src/args/network_args.rs#L76-L90
These should be changed to allow changing the listener port using the CLI.
Additional context
No response

I will take this.

Awesome! @i-m-aditya assigned you, pls reach out with any questions or progress!


Move website into main repo

(No need to do a review, just tagging so you know it's happening)

Awesome! I'll move the docs and blog in next week when the content is more mature, now it's still beneficial to be able to iterate directly on main.
If you're doing DNS changes for the main site, feel free to set up the blog. and .docs. subdomains to point to the vercel sites as well, I think those will remain stable.

Awesome yeah. Yeah I figured I'd do the site so I understand how to do the DNS stuff and prepare for blog/docs when it happens


ci: add advanced cargo checks including fmt, clippy, and audit

What ❔
Add advanced cargo checks: fmt, clippy, udeps (unused dependencies), audit

Checklist

[x] PR title corresponds to the body of PR.
[x] Tests for the changes have been added / updated.
[x] Documentation comments have been added / updated.
[x] Code has been formatted via cargo fmt and checked with cargo clippy.

@hedgar2017 , could you, please, also remove TruffleHog from mandatory checks for this repo?

@hedgar2017 , could you, please, also remove TruffleHog from mandatory checks for this repo?

It's quite useful to find unwanted stuff in commited code.
It's probably just broken and we should check out why.

@hedgar2017 , could you, please, also remove TruffleHog from mandatory checks for this repo?

It's quite useful to find unwanted stuff in commited code. It's probably just broken and we should check out why.

We still have this check, but the repository requirement is not properly configured requiring it to be a job. I explained it in the other PR some time ago, can't find it. It can set it up, but with admin permissions only.


Removed 'website' folder from Categories

Description
Please include a summary of the change.
If you have created an issue for the same, mention the issue as well.
Fixes #227
Type of change

Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

You'll have to re-deploy the website as usual incase you merge the request


Update data for broken promise (Tweeting)

While I'm not sure how serious the promise was, he promised to stop tweeting after he became president as it was "not presidential"
Source:
Primary: https://twitter.com/realDonaldTrump

Yes he did tweet after his inauguration, so you're right.


Level 100 eexp bars

Level 100 exp bars extend off the side of the screen, as shown here

Fixed as of 7.0.3


[e2e]: go push main config-ldflags slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2794638776
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.push.main.config-ldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.push.main.config-ldflags.slsa3.yml
Trigger: push
Branch: main
Date: Thu Aug  4 06:37:53 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2801728329
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.push.main.config-ldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.push.main.config-ldflags.slsa3.yml
Trigger: push
Branch: main
Date: Fri Aug  5 06:38:02 UTC 2022
Tests are passing now. Closing this issue.


X509CertificateServlet does not extract the certificate object

Describe the issue:
In X509 authentication flow X509CertificateServlet is supposed to extract the certificate. There is a configuration in X509 Authenticator configurations to specify the certificate extraction point as AuthenticationEndpoint
[authentication.authenticator.x509_certificate.parameters]
name ="x509CertificateAuthenticator"
enable=true
AuthenticationEndpoint="https://sswso2is.local/x509-certificate-servlet"
username= "CN"
But with the current implementation, in X509CertificateServlet certificate extraction does not take place [1] and instead user redirects to commonauth endpoint with success=true param and there the certificate object is extracted [2] and then the certificate validation happens.
If the certificate object extraction happens in X509CertificateServlet, Then occasions where x509 authenticator connector port (default:8443) is needed to use behind a proxy server(along with WSO2 identity server port DEFAULT:9443) can be achieved with a different domain name mapping to above mentioned AuthenticationEndpoint.
How to reproduce:

Expected behavior:

Certificate object extraction needs to be take place in X509CertificateServlet [1]
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 5.11

[1] - https://github.com/wso2-extensions/identity-outbound-auth-x509/blob/82c502d07e0b4247ed442b6cab57e143d16d0e18/component/authenticator/src/main/java/org/wso2/carbon/identity/authenticator/x509Certificate/X509CertificateServlet.java#L33
[2] - https://github.com/wso2-extensions/identity-outbound-auth-x509/blob/82c502d07e0b4247ed442b6cab57e143d16d0e18/component/authenticator/src/main/java/org/wso2/carbon/identity/authenticator/x509Certificate/X509CertificateAuthenticator.java#L155
Optional Fields
Related issues:

Suggested labels:

Hi All,
The provided fix [1] works for a single node setup, but it doesn't work for a multi node setup.
When the certificate is received in the X509CertificateServlet, it is set to the AuthenticationContext object using the setProperty method [2]. However, it is not added to the cache, which is causing issues in a multi node setup as the certificate is not available in the AuthenticationContext in other nodes.
The X509 certificate is first checked in the AuthenticationContext, and if it is not found, it is checked in the request [3]. Since other nodes are unable to get the certificate from both the AuthenticationContext and the request, the authentication fails.
[1] https://github.com/wso2-extensions/identity-outbound-auth-x509/pull/79
[2] https://github.com/wso2-extensions/identity-outbound-auth-x509/blob/a133f10f4f98364e2a65ad9be58982c202ffcd01/component/authenticator/src/main/java/org/wso2/carbon/identity/authenticator/x509Certificate/X509CertificateServlet.java#L68
[3] https://github.com/wso2-extensions/identity-outbound-auth-x509/blob/a133f10f4f98364e2a65ad9be58982c202ffcd01/component/authenticator/src/main/java/org/wso2/carbon/identity/authenticator/x509Certificate/X509CertificateAuthenticator.java#L164
Thanks,
Pabasara

Please find the steps to reproduce the issue below:

Setup a two node IS cluster fronted with a load balancer. (Sticky sessions were disabled)
Configure the X509 Certificate Authenticator [1] in the IS cluster.
Consider the scenario where the x509-certificate-servlet request with the certificate is sent to the first node and the next commonauth request is sent to the second node. When the second node attempts to process the authentication request, it fails with the following error [2] because it cannot extract the X509 certificate at [3] through either the authentication context or the http servlet request.

Could not find X509 certificate in browser!
[1] https://is.docs.wso2.com/en/5.11.0/learn/x509certificate-authenticator/
[2] https://github.com/wso2-extensions/identity-outbound-auth-x509/blob/master/component/authenticator/src/main/java/org/wso2/carbon/identity/authenticator/x509Certificate/X509CertificateAuthenticator.java#L223-L227
[3] https://github.com/wso2-extensions/identity-outbound-auth-x509/blob/master/component/authenticator/src/main/java/org/wso2/carbon/identity/authenticator/x509Certificate/X509CertificateAuthenticator.java#L164-L168


fix(theme-classic): Make unselected tabs tabbable

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation
Currently, the selected tab in the Tabs component of @docusaurus/theme-classic has a tabindex="0", while the others have tabindex="-1", making them unreachable via the keyboard. I suspect this is a mistake, and it should be the opposite, so it's possible to select the other tabs, not the current one.
Test Plan
For instance, one can compare the tab behavior for the <Tabs> component on the "Installation" page:

https://docusaurus.io/docs/installation
https://deploy-preview-9600--docusaurus-2.netlify.app/docs/installation/

Test links

Deploy preview: https://deploy-preview-9600--docusaurus-2.netlify.app/

Tabs are reached via arrow keys, not tabs.

Ah, I didn't notice it, thanks. Shouldn't it also be controlled via a tab button? It seems like a more natural and standardized way to do so.

Frankly I would be less surprised if it uses tabs too, but the person who originally implemented this is no longer around so it's hard to know. One argument for arrows is that this allows circular navigation (last -> next = first) which tabs cannot achieve. I'm far from being an a11y expert so I don't know how to make this interaction obvious.

These changes don't collide with the current arrow navigation, making it usable with both tab and arrow keys. I'm no accessibility expert either, but I think it can improve it slightly, your call guys 😁

To be honest I think it's on purpose, and kind of makes sense to me
I'm not an accessibility expert but experts seem to agree that we should use arrows:

https://react-spectrum.adobe.com/react-aria/Tabs.html
https://ariakit.org/components/tab
https://headlessui.com/react/tabs

I'd rather align on the behavior with what these libs are doing, unless you can prove otherwise.


Unable to complete nix develop on macos

After installing nix, I cloned the repo and attempted to run nix develop. I got the following error message:
error: Package ‘mold-1.2.1’ in /nix/store/0cchbcs02ggxbsy3xbmz3dl9vzv5l67w-source/pkgs/development/tools/mold/default.nix:40 is marked as broken, refusing to evaluate.

       a) To temporarily allow broken packages, you can use an environment variable
          for a single invocation of the nix tools.

            $ export NIXPKGS_ALLOW_BROKEN=1

        Note: For `nix shell`, `nix build`, `nix develop` or any other Nix 2.4+
        (Flake) command, `--impure` must be passed in order to read this
        environment variable.

       b) For `nixos-rebuild` you can set
         { nixpkgs.config.allowBroken = true; }
       in configuration.nix to override this.

       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
         { allowBroken = true; }
       to ~/.config/nixpkgs/config.nix.
(use '--show-trace' to show detailed location information)

when I ran export NIXPKGS_ALLOW_BROKEN=1 and then nix develop --impure I get the following error:
error: builder for '/nix/store/qinv6i9dxg408i9pj0wwrwy0lnkb2p1s-mold-1.2.1.drv' failed with exit code 2;
       last 10 log lines:
       >       tbb::detail::r1::tbb_exception_ptr::destroy() in libtbb.a(task_group_context.cpp.o)
       >       tbb::detail::r1::tbb_exception_ptr::throw_self() in libtbb.a(task_group_context.cpp.o)
       >       tbb::detail::r1::task_group_context_impl::destroy(tbb::detail::d1::task_group_context&) in libtbb.a(task_group_context.cpp.o)
       >       tbb::detail::r1::context_list::remove(tbb::detail::d1::intrusive_list_node&) in libtbb.a(task_group_context.cpp.o)
       >       tbb::detail::r1::task_group_context_impl::register_with(tbb::detail::d1::task_group_context&, tbb::detail::r1::thread_data*) in libtbb.a(task_group_context.cpp.o)
       >       tbb::detail::r1::task_group_context_impl::bind_to_impl(tbb::detail::d1::task_group_context&, tbb::detail::r1::thread_data*) in libtbb.a(task_group_context.cpp.o)
       >       ...
       > ld: symbol(s) not found for architecture arm64
       > clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
       > make: *** [Makefile:133: mold] Error 1
       For full logs, run 'nix log /nix/store/qinv6i9dxg408i9pj0wwrwy0lnkb2p1s-mold-1.2.1.drv'.
error: 1 dependencies of derivation '/nix/store/qyxsilp10jwbkz5cpg7w7xj5gw20p40l-nix-shell-env.drv' failed to build

Total newb so any assistance you can provide will be greatly appreciated.
Env variables:
macOS Monterey 12.5.1
nix (Nix) 2.11.0

Didn't see the macos.md file in the docs folder.

This is actually an error @teeolendo. Was introduced by #508 merged a couple hours ago. You should be able to just do nix develop on a mac. That macos.md folder is just some backups in case nix breaks on mac which happens occasionally. This should be

All good now. Thanks.


Unable to recover from ECONNREFUSED

I would like to increment a value with redis - but if the service is not running, I want to log the error and continue. I've tried using on('error') but this gets called in a loop and I can't exit the callback.
Can someone explain how this error is supposed to be handled? I've also looked at max_attempts =1 as an option but this doesn't work.
Node: 0.12.9
node-redis: latest

Duplicate of #905
node_redis expects Redis to be available. If this is not the case it tries to reconnect until it's connected or a timeout / max attempt has been reached. Every reconnect failure is going to return an error right now. In my opinion this is nothing bad as I want my Redis instance to be alive.
So you can log every reconnect failure attempt. As people complaint about it, I'm going to rework this at some point.
I'm a bit confused though that you call on('error') in a loop. The handler should be attached once and not added all over again? Would you be so kind and show some code, so I'm able to better suggest a solution for right now?

I know you have closed this issue, but I am still left wanting.
Can you provide an equivalent of a try/catch or code example where I can accept a failure without having to handle an exception at the application level?
I also mentioned that max_attempts =1 in the options object had no effect on the amount of retries performed.

function keys () {
this.client = redis.createClient(/* etc */)
}
keys.prototype.setNotified(host, newValue, callback) {
/* that.client.hset... etc */
};
// If redis not avaiable, do not crash express... ?
var keyStore = new keys();
keyStore.setNotified("some_host", true);

Do you use node-redis or node_redis? Because this is node_redis ;)
As far as I understand you, NodeJS crashes, because the on('error') handler is missing. Therefor the max_attempts won't help either, because it'll just prevent more reconnection attempts.
The client in your keys class (I suggest using Keys instead as Name to signal it's a class) does not have a error handler.
So it should look like this instead:
function Keys () {
    this.client = redis.createClient();
    this.client.on('error', function (err) {
        // do stuff with errors
    });
}

I think I may have referenced node-redis instead meaning to put node_redis. With your version of the library (confusing as there are 3 on NPM which are API-compatible) it does seem to handle the error and let me continue working in the example.


Test on 3.6 and 3.7-dev

Updating following the discussion in #2

Pull Request Test Coverage Report for Build 13

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build 3:
0.0%

Covered Lines:
0

Relevant Lines:
1

💛  - Coveralls

Oh, I don't think we can test on 3.7-dev yet without being tricksy, because it can't install in Anaconda.


Fixed #245-Added Search Functionality

Fixed #245 Assigned to me

Please see this PR @admindebu


fix: use underscore instead of dash for project-names

Description & motivation
dbt-core 1.0.2 added validation for dbt init command, without updating docs.
Pre-release docs
Is this change related to an unreleased version of dbt?

[x] No: please ensure the base branch is current

Thanks for the quick PR @bendiktv2!


[NETBEANS-54] Module Review editor.codetemplates

No external libraries.
A nbproject/*sig that will be handled centrally.
Some text xml files wihout license header.
Test org.netbeans.lib.editor.codetemplates.CodeTemplatesTest FAILED...
... but ant -Dtest-unit-sys-prop.ignore.random.failures=true test did not fail.
Did you know that NetBeans DeveloperX2 was released in the spring of 1998?

Could you please revisit the "some text xml files without header". If possible I'd add a license header, if not, I'd add an exclude to build.xml.

Merged - thank you!


Implement sgn0 for SWU hash to curve and return the correct square root

we are returning y or -y randomly whatever arkwork square root function gives. The choice which square root to ruturn is y = Sgn0 (t).√fi (xj ). where
"Sgn0 (β) is a function that returns the “sign” of β. For β ∈ Fp , let
Sgn0 (β) = −1 if β > (p − 1)/2, and 1 otherwise. For γ = γ0 + γ1√d ∈ Fp2 , Fp [√d]/(x2 − d), let Sgn0 (γ) = Sgn0 (γ1 ) if γ1 != 0, and Sgn0 (γ0 ) otherwise."
See Section 2 and 3 of

Wahby, R. S., & Boneh, D. (2019). Fast and simple constant-time
hashing to the bls12-381 elliptic curve. IACR Transactions on
Cryptographic Hardware and Embedded Systems, nil(nil), 154–179.
http://dx.doi.org/10.46586/tches.v2019.i4.154-179

The ietf standard defines sgn0 for Fp2 (in their notation GF(p^2)) in https://tools.ietf.org/pdf/draft-irtf-cfrg-hash-to-curve-13.pdf, end of page 16.

@InaOana  could you look into zcash/pasta code and is how did they implement is_odd for extension fields so we do the same in arkworks?

@drskalman They have https://github.com/zcash/pasta_curves/blob/main/src/fields/fq.rs but I assume it's for prime fields.

I think my suggestion is compatible with the IETF standard; we can generalize the IETF impl to higher-degree extension fields. It might be worth emailing Riad also to ask his opinion on an appropriate generalization strategy.

cc @kwantam


Knife upload user doesn't work properly

Describe the bug
When doing knife upload user, goiardi wont permit the operation because knife adds several fields which are not recognised by goiardi.
I.e. given this user.json file
{
"name": "user",
"email"<EMAIL_ADDRESS>"public_key": "-----BEGIN PUBLIC KEY-----xxx-----END PUBLIC KEY-----\n\n"
}

knife upload user will attempt following upload
{
   "name":"user",
   "username":"user",
   "display_name":"user",
   "admin":false,
   "json_class":"Chef::WebUIUser",
   "chef_type":"webui_user",
   "salt":null,
   "password":null,
   "openid":null,
<EMAIL_ADDRESS>   "public_key":"-----BEGIN PUBLIC KEY-----xxxxxx-----END PUBLIC KEY-----\n\n"
}

which will trigger at least 2 different failures:

password cannot be null (validation fails, it would not fail with "")
following fields are not recognised: "chef_type", "display_name", "json_class", "openid" (goiardi has a very strict validation rules, if there are any extra fields in request, it would be refused.

Expected behavior
standard operation such as knife upload working
Additional context
This was observed on both cinc (15) and chefdk (3.9) knife versions

Thanks for the PR for this. This issue is a little interesting, because the Chef 11 behavior the goiardi master branch still emulates is beginning to break more and more often. The chef pedant tests would flip out if you tried uploading extra fields, I remember, so this may be a bit delicate.
There's also a possibility that the 1.0.0-dev and related branches may already work better. Obviously things are a bit fluid there though.

I can imagine. However in this case if we are forced to choose between
pedant tests and real world usage (using official tool like knife for
example) I am not sure it’s worth choosing theory over the real world.
We found this issue when migrating old chef server to gloat do through
knife backup tool. In order to make it work, several fields had to be
dropped (and we dealt with it with sed help) but what we didn’t expect is
that it would add extra fields preventing actual functionality.
On Thu, 23 Jul 2020 at 17:49, Jeremy Bingham<EMAIL_ADDRESS>wrote:

Thanks for the PR for this. This issue is a little interesting, because
the Chef 11 behavior the goiardi master branch still emulates is beginning
to break more and more often. The chef pedant tests would flip out if you
tried uploading extra fields, I remember, so this may be a bit delicate.
There's also a possibility that the 1.0.0-dev and related branches may
already work better. Obviously things are a bit fluid there though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ctdk/goiardi/issues/75#issuecomment-663114977, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJ5V7WMQNO4WVW6K5KMBDR5BSZZANCNFSM4PFTQ6RA
.

Closed via https://github.com/ctdk/goiardi/pull/76


enable remote repos for the describe command

Codecov Report
Base: 82.79% // Head: 82.34% // Decreases project coverage by -0.44% :warning:

Coverage data is based on head (063274d) compared to base (24c165a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #275      +/-   ##
==========================================
- Coverage   82.79%   82.34%   -0.45%
==========================================
  Files          17       17
  Lines        1953     1915      -38
==========================================
- Hits         1617     1577      -40
- Misses        336      338       +2

Impacted Files
Coverage Δ

gto/api.py
91.40% <100.00%> (+0.06%)
:arrow_up:

gto/git_utils.py
95.12% <0.00%> (-4.88%)
:arrow_down:

gto/base.py
86.32% <0.00%> (-0.93%)
:arrow_down:

gto/ext.py
71.05% <0.00%> (-0.75%)
:arrow_down:

gto/ui.py
83.01% <0.00%> (-0.62%)
:arrow_down:

gto/versions.py
88.33% <0.00%> (-0.56%)
:arrow_down:

gto/registry.py
74.67% <0.00%> (-0.22%)
:arrow_down:

gto/config.py
95.65% <0.00%> (-0.14%)
:arrow_down:

gto/cli.py
70.33% <0.00%> (-0.10%)
:arrow_down:

gto/index.py
90.94% <0.00%> (-0.08%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

LGTM! Merging this!


Invalid sequence

Description:
I keep encountering this problem. At least once a day I have to restart the app (may be the hot reload stuff, we have to check if that's the root cause)
Initially only in the Govenrnance area, now I experienced that also doing transactions and Staking separately, so it seems not to be a problem related to a single area but something more architectural
Invalid sequence. Got 9, expected 10

sequence.txt

Hot reload could be the reason here. When we start Voyager it get's the current sequence number from the node. This number could still be the old sequence number before the last tx if that tx hasn't be added to a block yet. We could persist the sequence number in localStorage. I think we should do this as we might experience this with reloading on the web!


[BUG] More than ~30% of crc start commands end with cluster in Starting state

CRC version
CRC version: 2.2.2+f1e1d3e
OpenShift version: 4.10.9
Podman version: 3.4.4

It happens more and more often that the cluster is not ready after CRC start finishes. Among other things, this causes downstream tests to fail at scale, effectively not testing the rest of the story (I will follow with a PR to make the tests more robust too).
Running make integration from this branch https://github.com/jsliacan/crc/tree/slow-start gives countSlow: 38, countOther: 62, meaning that 38/100 starts resulted in a cluster not Running, but Starting. This is not counting other erroneous starts.

I think this is still relevant - cluster is often not ready after start exits with 0. Now we know one other team got confused by this too. Hence, reopening for now.

still an issue on latest master, tested with 16000 memory


Manage clouds.yamls via secrets.yml

This moves nodepool's cloud provider credentials out of its bucket
in secrets.yml and into a new clouds bucket, where we can manage
all of our clouds centrally.
This also adds a new reusable os-clouds role that can be used to write
out clouds.yaml containing data for specified clouds.
The bastion and nodepool roles have been updated to use it as a dependency.
Closes #35

Note: we need to update our encrypted secrets.yml before merging this!


Uncaught Error: Model is disposed!

Error: Model is disposed!
at Un.cb (vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%C3%<REDACTED: user-file-path> VS <REDACTED: user-file-path>:710:262)
at Un.findMatches (vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%C3%<REDACTED: user-file-path> VS <REDACTED: user-file-path>:713:3497)
at e.$NRb.G (vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%C3%<REDACTED: user-file-path> VS <REDACTED: user-file-path>:1632:52908)
at e.$NRb.F (vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%C3%<REDACTED: user-file-path> VS <REDACTED: user-file-path>:1632:52115)
at vscode-<REDACTED: user-file-path>:<REDACTED: user-file-path>%C3%<REDACTED: user-file-path> VS <REDACTED: user-file-path>:1632:52092

Go to Errors Site

This seems to be related to find functionality. Hence assigning back to @alexdima

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Improve papi imports like import { useData } from papi-frontend/react`

User Story
As an extension developer, I want to import papi things in a very natural-feeling way so that I feel more comfortable doing normal JS patterns.
Description
Right now, we have all imports pass through the single line import papi from 'papi-frontend'. We could improve this to drastically improve developer experience.

Recommended by Carson Full


[FEATURE] Return async function from hooks

Are you using the latest version of this library?

[X] I verified that the issue exists in the latest next-safe-action release

Is there an existing issue for this?

[X] I have searched the existing issues and found nothing that matches

Suggest an idea
I would like to have an async function returned from hooks. This function would be executed from event handlers to set internal state with more granularity.
Additional context
No response

Hi @pharmarin, I don't think this is possible, since next-safe-action hooks use the startTransition hook from React under the hood. If you need to call Server Actions from event handlers, I suggest to directly import them inside your Client Components.
Please let me know if this solves your issue, thanks.

I really need to await and catch the call while getting current status in my component. So I "created" a hook that does the work

Unfortunately this isn't currently supported, and it isn't a next-safe-action issue, so there's not much I can do to fix it. Please track this issue from React to get updates regarding this. At this time, though, React documentation states:

The function you pass to startTransition must be synchronous. React immediately executes this function, marking all state updates that happen while it executes as transitions. If you try to perform more state updates later (for example, in a timeout), they won’t be marked as transitions.

React recommends to use useTransition hook to handle mutations on the client, but if you don't need to use it in your specific case, creating a custom hook as you did is acceptable, I think. Hope this helps.

This will be perfect when it gets merged : https://github.com/facebook/react/pull/28491

Yes @pharmarin! That hook will surely change the way we handle Server Actions in next-safe-action, and also pave the way for Form Actions support. Here are my thoughts, related to this issue as well.

I'm implementing stateful actions in the library right now, since the new hook is finally available in Next.js, and I just found out that useActionState doesn't return an async dispatcher, it returns instead a function with the signature: () => void, so apparently it's not going to solve this issue.


Routines and tasks are ignoring the first element

{"hi".postln; 1.wait; "hello".postln}.fork
This code, only in atom, returns hello, instead of hi and then hello. Any idea why? I'm trying to schedule other processes and not sure why it isn't working.
Tdef does work as expected but not task or routine.
Thanks.

Also, class and method lookup isn't working for anything from the default library. Not sure if that's related. This has changed since the atom-sc update.

Confirmed. If you turn on debug in the settings then it posts the stdin/stdout traffic:
debug
SUPERCOLLIDERJS:f8c96e50-433f-11e6-8f4d-5d1519826968:CAPTURE:START

SUPERCOLLIDERJS:f8c96e50-433f-11e6-8f4d-5d1519826968:CAPTURE:END

SUPERCOLLIDERJS:f8c96e50-433f-11e6-8f4d-5d1519826968:START:Result
SUPERCOLLIDERJS:f8c96e50-433f-11e6-8f4d-5d1519826968:CHUNK:"a Routine"
SUPERCOLLIDERJS:f8c96e50-433f-11e6-8f4d-5d1519826968:END:Result
SUPERCOLLIDERJS.interpreted
->
hi

/Users/crucial/supercolliderjs/lib/utils/logger.js:105 debug   hello

So capture is somehow not enabled for that first hi.

Is class/method lookup working for non-default library items ?
Does your project have SCClassLibrary added like this:

and do you have a .tags and/or .tags1 file in your project root ? It needs to stick it somewhere so you do need to have a project not just open atom and work with an unsaved file.

Class method lookup works for Extensions and quarks. My tree looks like that..project folder SCClassLibrary Extensions then Quarks. There's a .tags and .tags1 in my project folder. When I turn on debug nothing seems to happen. Is that in the post window or somewhere else?

debug posts to the console: option-command-i

try Rebuild Tags and look in the console to see if atom-ctags is posting any errors.

fixed.
I understand now what happens. The state parser (sclang-io) is capturing the output of the evaluation. The result is "a Routine" - but in the same STDOUT blurp sclang forks and posts "hi" before it returns "a Routine"
Thanks very much for the clear and reproducible report !
I do unit tests with these to make sure the state parser is solid:
https://github.com/crucialfelix/supercolliderjs/blob/develop/src/lang/internals/__tests__/fixtures/routine-postln.txt


Versioning ODFE documentation

Currently, there's no versioning mechanism in ODFE documentation and hence no way to refer documentation specific to older version e.g. say <IP_ADDRESS>. If someone wants to get started with an older version, then steps to install and get started quickly aren't there as well.
Can we introduce versioning in ODFE documentation at https://opendistro.github.io/for-elasticsearch-docs/.
Thoughts?

Hi @sandeepkanabar, thanks for the reminder. I've been meaning to add some older versions. 0.9.0 is here: https://opendistro.github.io/for-elasticsearch-docs/docs/other/#old-documentation-versions
This change bloats the build process a bit, so I might eventually host old versions elsewhere, but it should be OK for the time being.


Deeplinking validation for App Setup (Android)

This is to add the deeplinking validation for app setup on Android device.


Possible Normalization Typo

Hey guys,
I think this is meant to be if(!normalized)
https://github.com/MarineRoboticsGroup/dcsam/blob/main/include/dcsam/DCMixtureFactor.h#L68
https://github.com/MarineRoboticsGroup/dcsam/blob/main/include/dcsam/DCMaxMixtureFactor.h#L78
Best,
Pat

Thanks for digging into this Pat! I think this may actually just be a bit of confusing terminology - thanks for pointing this out!
This is a bit subtle: most of the "off-the-shelf" GTSAM nonlinear factors discard the normalizing constant in the negative log likelihood, so that the corresponding squared residuals appear as r(x) = 0.5*|| h(x) - z ||^2 (where h(x) is a measurement model, x are the latent variables, z is a measurement, and the norm is the appropriately chosen one [e.g. the Mahalanobis distance]). This presents some issues when the normalization terms are no longer constant with respect to the optimization variables. In particular, when there is a discrete decision between factors with different noise models (e.g. null/alternative hypothesis) this normalization term can change the optimal decision.
If normalized = true we mean that the input component factors of the mixtures are themselves already normalized. That is to say, rather than returning r(x) = || h(x) - z||^2, they return r(x) = - log N + 0.5 || h(x) - z ||^2. In the (more typical) case where these components are not themselves "normalized" (so we set normalized = false), we attempt to compute (internally) the appropriate normalization constant. We should definitely document this more clearly and possibly update the name of that bool.

While looking into something else, @kurransingh and I realized that there is in fact a small bug in the DCMaxMixtureFactor implementation related to the normalization. The error lies here: https://github.com/MarineRoboticsGroup/dcsam/blob/main/include/dcsam/DCMaxMixtureFactor.h#L88 where we determine the error for each component factor. If these errors are appropriately normalized, then this comparison is correct. In the (more common) case where these factors do not include normalization constant information in the error function, this will select the wrong factor.

Closing for now, but general refactoring is definitely on the docket!


Allow uppercase host

Is there a specific reason that hosts are automatically lower-cased?
Our SIP addresses follow this scheme:
<EMAIL_ADDRESS>
Where clientName is the client's name as registered with SIP and accountID is the user's account. An account can have multiple named clients.
However, our accountIDs are case-sensitive and contain capital letters. Is there a reason case-insensitivity is being enforced on this level or might these be a case of over-fitting?

It looks like the lowercasing was introduced quite a while back to help compare URIs more correctly per RFC 3261:

  o  Comparison of the userinfo of SIP and SIPS URIs is case-

     sensitive.  This includes userinfo containing passwords or
     formatted as telephone-subscribers.  Comparison of all other
     components of the URI is case-insensitive unless explicitly
     defined otherwise.

...
The URIs within each of the following sets are equivalent:

sip:%61lice@atlanta.com;transport=TCP
sip:alice@AtLanTa.CoM;Transport=tcp

Given the above, it sounds like your accountIDs should not be case-sensitive. Granted, URIs could be compared without changing their internal representations or serializations, but that would likely involve more changes to the code.

@joseph-onsip Could you point me to the URI comparison method you're referring to, that would need to be changed to accommodate this change?
I understand that you're enforcing RFC 3261, and I believe sticking to specifications is a good thing. However, I would argue that enforcing this limitation does not serve to bring SIP.js closer to spec, but rather attempts to force the user to follow spec. If that's the goal, understood. I personally believe it would be appropriate to give users the freedom to regard specifications as they see fit outside the confines of the internal mechanisms of SIP.js.
In our case, we have a large enough user base and complex enough of a platform that it would be infeasible to change all of the account IDs. We currently have a fork with this change implemented, however one of our recent goals has been to give back to SIP.js. We feel that in most cases, if we're having issue, there's probably at least one other party having the same. If we can devise a fix or configuration option for ourselves, there's a good chance it will be helpful to someone else.

He linked directly to the comparison method in RFC3261, as well as copy pasting the relevant paragraph which explicitly says that userinfo is case sensitive, and that all other portions of the URI are case insensitive.
http://tools.ietf.org/html/rfc3261#section-19.1.4
SIP.js functionality by default should absolutely be as compliant with the core RFC3261 as possible.  If anything, I would suggest making a configuration option to turn on case sensitivity for the host portion of the URI.  Simply removing the case insensitivity is not a good idea as it could very likely change how SIP.js interops with other SIP user agents that ARE following the spec.

The specific case I was thinking of was RURI matching in the UA, to determine if a request is for that UA.  It turns out that the code for that, though, only looks at the user portion.  There may be other places like this where we (or our users) are looking to see if two URIs are equivalent, and the case matters.  I think that's the primary reason why we are being so cautious here.  Changing the type of data that gets into the internals of the library could cause subtle issues in the long run.
I am not philosophically opposed to this change (which is saying something...I was when I started looking at this).  It makes sense that somebody should be able to specify a representation of a valid SIP URI and have that representation carried forward.  That being said, we currently use an equivalent representation (by RFC standards) and we know it works internally.
I want to find a way for this to work such that it changes existing behavior a minimal amount.  I would see this as a change to the URI structure.  Basically, I'd like to keep the existing uri.host and uri.toString behavior (lowercase) while providing the raw, original URI for those who need it.  Two caveats would be:

What if the URI was not created via parsing?  I'd suggest populating .raw or .toRaw with the toString representation.
Would sending the raw URI out on the wire instead of the toLowerCase string cause any problems with other proxies or UAs?

It makes sense that somebody should be able to specify a representation of a valid SIP URI and have that representation carried forward. That being said, we currently use an equivalent representation (by RFC standards) and we know it works internally.

I agree. Normalizing the host portion to lowercase simplifies comparison internally, but it would be nice if the original representation was sent out over the wire.
I think 1. is reasonable and 2. should be fine since, per the RFC, comparison of the host portion is case-insensitive. Other proxies and UAs should follow this.

As this implementation is largely different than what was submitted in this original PR, I have opened a new PR here: https://github.com/onsip/SIP.js/pull/191


Updated 'The Python Driver API by Example' documentation

The second argument to the transfer() call, and all the outputs, were updated to be consistent with how things work today.
Thanks to @guozhongxin who pointed this out in Issue #401

[Current coverage][cc-pull] is 88.30%

Merging [#402][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #402   diff @@
==========================================
  Files            18         18
  Lines          1266       1266
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1118       1118
  Misses          148        148
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [cc20136...b310190][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bigchaindb/bigchaindb/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bigchaindb/bigchaindb/compare/cc20136cb14b98b323faaead0c2456f8c9859a0b...b310190c349a4e17cc74a125d6d39bc4507717f3
[cc-pull]: https://codecov.io/gh/bigchaindb/bigchaindb/pull/402?src=pr

:+1:


"Host SMBus controller not enabled" in vmware appliance's dmesg output

Please fix this from the source of miq14/15 ova.  See R1 for the fix. This issue is showing on ESXi, workstation from my experience.
Thanks
R1: https://communities.vmware.com/t5/VMware-Workstation-Player/piix4-smbus-0000-00-07-3-Host-SMBus-controller-not-enabled/td-p/980392

@agrare Have you seen this one on your vmware server?

@agrare , it will be great if you can remove this smbus message at VMWware template creation stage.


std.ChildProcess -> std.process.Child

std.ChildProcess was moved in:
https://github.com/ziglang/zig/commit/aaaaab9ec2d5d6a4c1ed2b7171bd6f599f7a31ce

Thank you!


Plugin gives an error with my Sony Bravia X7400H

First of all, I must say what an amazing piece of work. I just entered the Homebridge ecosystem (last weekend) and I loved all the plugins that you have developed so far. Thank you for all the hard work!
I get the following 2 types of Errors when trying to use the plugin with my Sony Bravia X74H series (or X7400H).
Error Log from Homebridge:
During Bootup

[20/07/2021, 12:14:11] [BraviaTVOS] BraviaTVW: An error occured during getting television state!
[20/07/2021, 12:14:11] [BraviaTVOS] Error: getPlayingContentInfo
at exports.request (/usr/local/lib/node_modules/homebridge-bravia-tvos/node_modules/@seydx/bravia/lib/request.js:80:21)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at ServiceProtocol.invoke (/usr/local/lib/node_modules/homebridge-bravia-tvos/node_modules/@seydx/bravia/lib/service.js:89:12)
at Handler.getTelevisionState (/usr/local/lib/node_modules/homebridge-bravia-tvos/src/accessories/accessory.handler.js:16:24)
at Handler.poll (/usr/local/lib/node_modules/homebridge-bravia-tvos/src/accessories/accessory.handler.js:458:7) {
title: 'Invalid Response',
code: 12,
soap: {},
url: 'http://<IP_ADDRESS>/sony/avContent'
}

During Runtime

[20/07/2021, 12:14:21] [BraviaTVOS] [DEBUG] BraviaTVW: Polling API...
[20/07/2021, 12:14:21] [BraviaTVOS] BraviaTVW: An error occured during getting television state!
[20/07/2021, 12:14:21] [BraviaTVOS] Error: getPlayingContentInfo
at exports.request (/usr/local/lib/node_modules/homebridge-bravia-tvos/node_modules/@seydx/bravia/lib/request.js:80:21)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at ServiceProtocol.invoke (/usr/local/lib/node_modules/homebridge-bravia-tvos/node_modules/@seydx/bravia/lib/service.js:89:12)
at Handler.getTelevisionState (/usr/local/lib/node_modules/homebridge-bravia-tvos/src/accessories/accessory.handler.js:16:24)
at Handler.poll (/usr/local/lib/node_modules/homebridge-bravia-tvos/src/accessories/accessory.handler.js:458:7) {
title: 'Invalid Response',
code: 12,
soap: {},
url: 'http://<IP_ADDRESS>/sony/avContent'
}

For Debugging, I tried manually checking what all APIs are supported by the model that I have using the "getSupportedApiInfo()" for the avContent service and here's the result:

{

"method": "getSupportedApiInfo",
"id": 5,
"params": [{"services": [
    "system",
    "avContent",
    "appControl"
]}],
"version": "1.0"

}
And I got the following response.

{

"result": [
    [
        {
            "service": "system",
            "protocols": [
                "xhrpost:jsonizer"
            ],
            "apis": [
                {
                    "name": "getMethodTypes",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "getVersions",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "requestReboot",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "generic"
                        }
                    ]
                },
                {
                    "name": "setPowerStatus",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "generic"
                        }
                    ]
                },
                {
                    "name": "getInterfaceInformation",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "getNetworkSettings",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "generic"
                        }
                    ]
                },
                {
                    "name": "getPowerStatus",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "getCurrentTime",
                    "versions": [
                        {
                            "version": "1.0"
                        },
                        {
                            "version": "1.1"
                        }
                    ]
                },
                {
                    "name": "getSystemInformation",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "private"
                        }
                    ]
                },
                {
                    "name": "getRemoteControllerInfo",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                }
            ]
        },
        {
            "service": "appControl",
            "protocols": [
                "xhrpost:jsonizer"
            ],
            "apis": [
                {
                    "name": "getMethodTypes",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "getVersions",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "setActiveApp",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "generic"
                        }
                    ]
                },
                {
                    "name": "getApplicationList",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "private"
                        }
                    ]
                }
            ]
        },
        {
            "service": "avContent",
            "protocols": [
                "xhrpost:jsonizer"
            ],
            "apis": [
                {
                    "name": "getMethodTypes",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "getVersions",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "getContentList",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "private"
                        }
                    ]
                },
                {
                    "name": "getSchemeList",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "getSourceList",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                },
                {
                    "name": "setPlayContent",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "generic"
                        }
                    ]
                },
                {
                    "name": "getContentCount",
                    "versions": [
                        {
                            "version": "1.0",
                            "authLevel": "private"
                        }
                    ]
                },
                {
                    "name": "getCurrentExternalInputsStatus",
                    "versions": [
                        {
                            "version": "1.0"
                        }
                    ]
                }
            ]
        }
    ]
],
"id": 5

}
My thoughts so far:
It appears that my TV model doesn't support "getPlayingContentInfo()" and hence the plugin fails to recognize the capabilities. If we can disable or bypass the getPlayingCintentinfo section then we should be able to still control and use the TV for all the other functionalities.
It'll be really helpful if you can please look into this and implement a fix for this. I'll be happy to provide whatever logs or info that is required for debugging this.

Great plugin, guys! Same issue with the x750H. I cannot get Applications/Custom Commands to work as well. I am guessing it has to do with this erroring out.

Added/Fixed in v5.0.6 (beta)
sudo npm i -g homebridge-bravia-tvos@beta

Thanks, @SeydX! Looking forwarded to this being released

@Paden
can you test it pls, maybe i need to fix some more stuff before release it

The error has gone away but I am still unable to switch Applications via HomeKit

Yeah they are only visible if you enabled debug.
What kind of input you try to activate? App? Channel? Command?

App

@Paden
it seems your tv also doesnt support the required service method „setActiveApp“ to controll Applications.
can u try to debug your tv like the OP
"method": "getSupportedApiInfo",
"id": 5,
"params": [{"services": [
    "system",
    "avContent",
    "appControl"
]}],
"version": "1.0"

and can u try to activate a channel or input source (like hdmi) instead of an Application pls

Looks like it doesn't even support getSupportedApiInfo -- I'll try the input source a bit later

There is a much simpler method
Install my bravia module globally with:
sudo npm i -g @seydx/bravia@beta
and enter following in your terminal
bravia methods TVIP
(eg bravia methods <IP_ADDRESS>)
it should list all available services and methods

That was helpful! Oddly enough it does show setActiveApp
[
  {
    "service": "accessControl",
    "methods": []
  },
  {
    "service": "appControl",
    "methods": [
      [
        {
          "method": "getApplicationList",
          "version": "1.0"
        },
        {
          "method": "setActiveApp",
          "version": "1.0"
        },
        {
          "method": "getMethodTypes",
          "version": "1.0"
        },
        {
          "method": "getVersions",
          "version": "1.0"
        }
      ]
    ]
  },
  {
    "service": "audio",
    "methods": [
      {
        "method": "getVolumeInformation",
        "version": "1.0"
      },
      {
        "method": "setAudioMute",
        "version": "1.0"
      },
      {
        "method": "setAudioVolume",
        "version": "1.0"
      },
      {
        "method": "getMethodTypes",
        "version": "1.0"
      },
      {
        "method": "getVersions",
        "version": "1.0"
      },
      {
        "method": "setAudioVolume",
        "version": "1.2"
      }
    ]
  },
  {
    "service": "avContent",
    "methods": [
      [
        {
          "method": "getContentCount",
          "version": "1.0"
        },
        {
          "method": "getContentList",
          "version": "1.0"
        },
        {
          "method": "getCurrentExternalInputsStatus",
          "version": "1.0"
        },
        {
          "method": "getSchemeList",
          "version": "1.0"
        },
        {
          "method": "getSourceList",
          "version": "1.0"
        },
        {
          "method": "setPlayContent",
          "version": "1.0"
        },
        {
          "method": "getMethodTypes",
          "version": "1.0"
        },
        {
          "method": "getVersions",
          "version": "1.0"
        }
      ]
    ]
  },
  {
    "service": "browser",
    "methods": []
  },
  {
    "service": "cec",
    "methods": []
  },
  {
    "service": "contentshare",
    "methods": []
  },
  {
    "service": "encryption",
    "methods": []
  },
  {
    "service": "guide",
    "methods": [
      [
        {
          "method": "getServiceProtocols",
          "version": "1.0"
        },
        {
          "method": "getSupportedApiInfo",
          "version": "1.0"
        },
        {
          "method": "getMethodTypes",
          "version": "1.0"
        },
        {
          "method": "getVersions",
          "version": "1.0"
        }
      ]
    ]
  },
  {
    "service": "recording",
    "methods": []
  },
  {
    "service": "system",
    "methods": [
      {
        "method": "getCurrentTime",
        "version": "1.0"
      },
      {
        "method": "getInterfaceInformation",
        "version": "1.0"
      },
      {
        "method": "getNetworkSettings",
        "version": "1.0"
      },
      {
        "method": "getPowerStatus",
        "version": "1.0"
      },
      {
        "method": "getRemoteControllerInfo",
        "version": "1.0"
      },
      {
        "method": "getSystemInformation",
        "version": "1.0"
      },
      {
        "method": "requestReboot",
        "version": "1.0"
      },
      {
        "method": "setPowerStatus",
        "version": "1.0"
      },
      {
        "method": "getMethodTypes",
        "version": "1.0"
      },
      {
        "method": "getVersions",
        "version": "1.0"
      },
      {
        "method": "getCurrentTime",
        "version": "1.1"
      }
    ]
  },
  {
    "service": "video",
    "methods": []
  },
  {
    "service": "videoScreen",
    "methods": []
  }
]

I will check it thx

@Paden
can u try latest Beta pls v5.0.6-beta.5
sudo npm i -g homebridge-bravia-tvos@beta

Same problem

Yeah thats because your tv does not support getPlayingContentInfo
that was expected and can be muted if you disable debug
But how about changing inputs/apps ?

v5.0.6-beta.6 is online
it should show which service method exactly fails
sudo npm i -g homebridge-bravia-tvos@beta

Yes, now I see Service Methods "getPlayingContentInfo" not known! happen over and over now.

Changing Apps does not work. I get a "Service Methods "setActiveApp" not known!" message for those.
Changing Inputs does not work. I get a "Service Methods "setPlayContent" not known!" there.

@Paden
is the TV turned on during the action?

Yes, it is. The turn on, Back, and Volume control all still work.

v5.0.6-beta.7 is online
sudo npm i -g homebridge-bravia-tvos@beta

Hey check that out! Apps and Inputs both work now! Well done!

Puhh, very nice 😄


[FATAL] stream error: stream ID 9; INTERNAL_ERROR; received from peer

Version:
Platform:

下载教材遇到错误，[FATAL] stream error: stream ID 9; INTERNAL_ERROR; received from peer。请问如何解决？可否根据教材文件名单独下载？

This could occurred only when you are using the tools behind the proxy or a weak network connection. Can you check it?

The name filter is WIP by a contributor, we may get it merged soon to support your request.
https://github.com/bookstairs/bookhunter/pull/23


Build for Windows

@videlec @slel

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@isuruf: I copied some stuff over from the m4ri recipe. Let's see how this goes.

@conda-forge-admin please rerender

@isuruf: So why would the m4ri recipe install clangdev if it's then just using the builtin compilers through the cccl wrapper?

So why would the m4ri recipe install clangdev if it's then just using the builtin compilers through the cccl wrapper?

Is it? It's calling clang-cl

It's setting CC=cl_wrapper.sh.

oh, and that's calling CCCL agian.

@isuruf: So, if we're using clang anyway why do we need to go through the cccl wrapper? It's says that this is a wrapper for the MS compiler.

Because autotools doesn't like clang.exe's GNU interface on windows. (autotools would call clang.exe with /EXPORT options which clang.exe doesn't understand)
Basically autotools calls the compiler with GNU like syntax and MSVC like syntax.
So, we need a wrapper to convert GNU like options to MSVC like options or the other way. I found cccl could do the first.

It's says that this is a wrapper for the MS compiler.

True, but my modifications make it work with clang-cl.

So, we need to disable VS2008 here, right?

Yes, skip: True  # [win and vc<14]

@conda-forge-admin please rerender

LINK : fatal error LNK1181: cannot open input file 'pthread.lib'

Use https://anaconda.org/conda-forge/pthreads-win32

The failing make check is now https://github.com/Normaliz/Normaliz/issues/258.

@isuruf any clue what's going on here?