add integresql-client-python to libraries

I've created python version of library for IntegreSQL, and as requested, added link in README :)
BTW, great tool! Thanks!

Hello,
is your repository at https://github.com/msztolcman/integresql-client-python private? I get a 404 when trying to open it.

Ech, not anymore... forgot to switch, sorry :)

Thank you!


Use X-Forwarded-Proto to determine Scheme

I've recently come across an interesting problem with running Kestrel behind a SSL offloading HAProxy where the ASP.Net app is generating redirect URLs that use HTTP instead of HTTPS.
Obviously ASP.Net doesn't know about the actual URL the client uses (over HTTPS) so it thinks it's doing the correct thing as it uses the HttpRequest.Scheme to generate it.
As most (reverse) proxies include the X-Fowarded-Proto header it would be nice to have Kestrel recognise this header and set the Scheme accordingly.
I've prepared a change to implement this behaviour but before I submit a PR I would like to get some feedback if this is a correct approach.
A bit of background:
My first approach was to include a bit of middleware in the ASP.Net pipeline to detect the header and set the scheme accordingly however that has the drawback that every app needs to include that middleware so having the hosting server (Kestrel or IIS) supply it makes life easier for the devs building the app.

A bit more effort on the googling would have helped. I now tracked down that there is already middleware included by default in the IISIntegration package (specifically here: https://github.com/aspnet/IISIntegration/blob/dev/src/Microsoft.AspNetCore.Server.IISIntegration/WebHostBuilderIISExtensions.cs#L56) that makes this work.

@sandermvanvliet In case you didn't see it, the code you linked to is configuring the UseForwardedHeaders middleware which you can get from the Microsoft.AspNetCore.HttpOverrides NuGet package.

@halter73 yep found it, thanks for the link.


Fonts not loading

Describe the bug
On this computer, the fonts aren't being requested. The entire site is in Serif (it looks horrible.)
To Reproduce
Steps to reproduce the behavior:

Go to matrix.to
"My eyes, my eyes!"

Screenshots

Desktop (please complete the following information):

OS: Apologetically, it's Windows 10 (not mine.)
Browser: Firefox
Version: 72.0.2 (32-bit)

Additional context
I've checked the Developer Tools, and no font files are being loaded.

Duplicate of https://github.com/matrix-org/matrix.to/issues/121. Fixed but not deployed yet

not deployed yet

Why?


proposal: cmd/go: refine the default language version based on context

Background
In https://groups.google.com/g/golang-dev/c/j3d8zuauJoY/m/gPOgpq_5DgAJ, @griesemer noted (emphasis mine):

Not everybody has switched to modules yet. We do know from surveys that the vast majority has (we estimate some 70-80%), but it is not the default mechanism. And even if everybody was using modules, introducing these changes would require .mod files to be adjusted to avoid breakages.

I agree with that assessment. However, I think there is a better default we could use in order to move forward with less churn: rather than having the Go language version used for dependencies track the maximum version supported by the Go toolchain (as it has in the past), we should have it default to a version that is likely to be compatible with existing code that was written for use in GOPATH mode.
Proposal
I propose that cmd/go should:

If in module mode and the main module lacks an explicit language version, set it to the maximum supported language version (as cmd/go already does today).

When compiling a package from a list of .go source files specified on the command line:

If in module mode and the working directory is inside of a module, use the main module's language version.
If in module mode but not inside of a module, use the maximum supported language version.
If in GOPATH mode, use the maximum supported language version.

When compiling a package, either as a direct argument to the go command or loaded as a dependency of some other package:

If in module mode and the module containing the package has a go.mod file with a go directive, use the version indicated by that module's go.mod file.
If in module mode and the module containing the package does not specify an explicit language version (perhaps because it lacks a go.mod file), use Go 1.14 (or another version that has not removed support for any features introduced up to that point).
If in GOPATH mode, use the maximum supported language version.

Note that in all cases users can explicitly override the default by passing -gcflags=-lang=… either as an explicit argument or via GOFLAGS.
Rationale
Defaulting to Go 1.14 for packages outside of the main module in module mode maintains compatibility for packages written prior to the introduction of modules, even when they are loaded in module mode.
Defaulting to the maximum supported language version for file lists in module mode encourages users of standalone “script” files to either keep them up to date with language changes, or explicitly record the intended version in a corresponding go.mod file.
Defaulting to the maximum supported language version in GOPATH mode avoids the need to (imprecisely) scan the GOPATH tree (including vendor directories) looking for go.mod files, and seems the most likely to maintain compatibility for users “working at head” (which is generally what GOPATH assumes regardless). It is also consistent with the general non-reproducibility of GOPATH mode: if users want a reproducible build, they are encouraged to switch to module mode, and even if they do not they still have the option to set -gcflags=-lang=… explicitly or vendor in older versions of their dependencies.
See also #30791.
(CC @ianlancetaylor @matloob @jayconrod @dmitshur)

I suggest we put this on hold until we are ready to make a backwards-incompatible language change. We'll know more then.

We discussed part of this in an email. It seems we agree upon using the containing main module's go version:
Current behavior
The Go version for a file passed in via command-line uses the local version.
e.g. $ go vet -x main.go
will set the Go Version to be the local version.
This happens in 3 places (maybe more):

vet
compiler
init.go

This ignores whether or not the file has a containing module.
e.g. current go version running is 1.23
-> main.go
-> go.mod (1.21)
$ go vet -x main.go
will set the Go Version to be 1.23
New behavior
As discussed in the email and in https://go-review.googlesource.com/c/go/+/567435 we have come to the decision to set the Go version to use the containing go.mod's version.
In the above example, $ go vet -x main.go
will set the Go Version to be 1.21

We ended up doing most of this proposal over the past few years as part of the toolchain work. The only part that's not done is the version for command-line .go files matching the containing module. That's clearly correct and important to do. No proposal needed for that.


Unavailable release tarballs

Hello.
There are no tags in repo. Ok...
README says that tarballs are here: https://www.eventd.org/download/wayland-wall/. HTTP 404...
Please either add tags or provide tarballs by other means.

There are currently no releases, as you noticed with the empty tag list.
What do you need a tarball for?

I was planning to introduce the next release of eventd into the Gentoo main repo. Wayland support in eventd as you know requires wayland-wall. I need smth non-live per Gentoo rules.

Wayland support in eventd needs weston-wall plugin and only works in Weston and my unreleased WayHouse.
It’s probably not worth the effort to include this support right now. I’ll start releases once the preliminary work on libweston is done to kind of support shared plugins.

Ok, that's fine with me. Thank you for the info!
P.S. If you say eventd actually wants weston-wall, then this is probably a typo: https://github.com/sardemff7/eventd/blob/977ba0ea808cb6239b35fb296e12ede909a8b69d/configure.ac#L280

I say that eventd-nd/wayland will only work with a server-side implementation, and the only one available is in weston-wall (and orbment-wall), nothing like the coverage the nd/xcb backend has.

Ah, I see. Thanks for the clarification.


Fix response handling in HTTPClient

Closes the stream upon a response if not keepalive (this was the bug)
Adds a few comments
Cleanup

Current coverage is 80.42% (diff: 0.00%)

Merging #174 into master will decrease coverage by 0.11%

@@             master       #174   diff @@
==========================================
  Files           176        176
  Lines         13059      13078    +19
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits          10518      10518
- Misses         2541       2560    +19
  Partials          0          0

Powered by Codecov. Last update aca83a2...dc92239

👍 looks good to me


Feature/readme update

Moved documentation to wiki keeping simple Readme.md

I hereby agree to the terms of the Knot.x Contributor License Agreement.

Approved.


feature; Dynamic container loading support & Error collection

TL;DR

storage package config accepts an init container. It only allows reading and writing data from the init container. This PR expands the capability of optional loading arbitrary containers during the runtime. This is controlled using a bool flag, which is default disabled, to maintain backwards compatibility.

We also add error collection to a common errors package

Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[x] Code documentation added
[x] Any pending items have an associated Issue

Tracking Issue
https://github.com/lyft/flyte/issues/297
&
https://github.com/lyft/flyte/issues/321
Follow-up issue
NA

Codecov Report

Merging #64 into master will increase coverage by 1.00%.
The diff coverage is 81.25%.

@@            Coverage Diff             @@
##           master      #64      +/-   ##
==========================================
+ Coverage   70.91%   71.91%   +1.00%
==========================================
  Files          57       56       -1
  Lines        2352     2361       +9
==========================================
+ Hits         1668     1698      +30
+ Misses        544      526      -18
+ Partials      140      137       -3

Impacted Files
Coverage Δ

config/utils.go
16.66% <0.00%> (ø)

errors/errors.go
100.00% <ø> (ø)

storage/config.go
60.00% <ø> (ø)

storage/rawstores.go
82.85% <ø> (ø)

storage/stow_store.go
73.10% <80.00%> (+10.31%)
:arrow_up:

storage/config_flags.go
53.33% <100.00%> (+1.60%)
:arrow_up:

storage/stowstore.go
48.38% <100.00%> (+9.58%)
:arrow_up:

cache/auto_refresh.go
83.92% <0.00%> (+6.25%)
:arrow_up:

Continue to review full report at Codecov.

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


Command service API is stuck at first run

🐞 Bug Report
Affected Services

 The issue is located in: core-command
Is this a regression?

 yes, only happen in master branch
Description and Minimal Reproduction
When the command service starts, the first time of executing http://localhost:48082/api/v1/device will be stuck.

download the nightly-build docker-compose file
https://github.com/edgexfoundry/developer-scripts/blob/master/releases/nightly-build/compose-files/docker-compose-nexus-redis-no-secty.yml
use docker-compose up
docker-compose -f docker-compose-nexus-redis-no-secty.yml up -d
use curl to send request to http://localhost:48082/api/v1/device
curl http://localhost:48082/api/v1/device
the request is stuck

🔥 Exception or Error
There is no error log in edgex-core-command container.
🌍  Your Environment
Deployment Environment:
EdgeX Version:
Master
Anything else relevant?
Cancel the curl request, and send it again, the request works properly.
Also, this issue could be reproduced by simply restarting command service.

docker-compose -f docker-compose-nexus-redis-no-secty.yml restart command
send curl request again

This issue currently causes failure in blackbox-testing.

This might be a regression introduced by #2370 somewhere in the URLClient code. I don't have any insight or theories beyond that.

This looks to me like a variation of the original issue that led us down the refactoring path.
Possibly newly introduced retry is not working as expected?
Assigned to @brandonforster for investigation/solution.

It looks like logging is throwing an error retrieving its configuration from Consul. I'd say there's two issues here:

Why is logging not able to retrieve its configuration?
Why is logging not starting making command stop, shutdown, and then restart over and over and over?

I believe I have identified the issue in contracts. Submitting a PR now, I'll use this issue number to update the core-contracts version.

Closed by https://github.com/edgexfoundry/go-mod-core-contracts/issues/220

Reopening, adding a PR to incorporate those changes into the codebase and fix the BB tests.


HW Backend 14.10.16

https://github.com/vladik1609/Backend/tree/master

Next time post commit instead of link to the repository.


Remove usage of the deprecated getIdentityId() in APIPlugin, Storage, etc

are there a lot of internal usages of the now deprecated API? I know storage plugin internally uses .getIdentityId() . perhaps we can make a list in this PR, then reference the list in an issue for us to track updating internal usages of the deprecated API.

https://github.com/aws-amplify/amplify-ios/search?q=getIdentityId
follow up to remove usage of the deprecated API in APIPlugin, Storage, etc
Originally posted by @lawmicha in https://github.com/aws-amplify/amplify-ios/issues/1502#issuecomment-962103221

This should be fixed in Amplify v2.0.0

Fixed in v2.0.0


added troubleshooting section to readme

Was having some issues. Added this to help out anyone having issues running the example.

@cla-bot check

Thanks for contributing @natemcintosh.


Add ctags about symbols

This PR is adding ctags to generate a text file about symbols used in addons.

This should be a user-specific plugin, so I am going to close this PR. I'd suggest you could load it in your vscode workspace config or .vimrc etc.

Thanks @WindQAQ, but I think it will be good to have it as well, here is from PyTorch.

Yes, but it's still not a prerequisite of a GitHub repository or a Python package. I mean it's a feature that the repository could still work without it, and users could easily setup it on their own workspace without any extra effort. Thank you.


Testing Guide

Fixes #3254.
@slchow can you please copyedit?  As we did before, make a branch off of the testing-guide branch in your repo, and then open a pull request into this repo's testing-guide branch.
As I clean everything up, the Contributor Guides on the wiki will move here.

Copyedits in #3291

Thanks, copyedits are merged into this branch.


Example in Readme throwing an error

Operating System: Arch Linux
Python version: 3.10.6
summit version used: 0.8.7

Description
I installed the latest version of Summit and run the example listing taken from the Readme file.
I got the error message reported below.
It is not clear at all which threshold I should increase.
What I Did
´´´
$ python -m venv .venv
$ ~ source .venv/bin/activate
$ ~ pip install -U summit
python
Python 3.10.6 (main, Aug  3 2022, 17:39:45) [GCC 12.1.1 20220730] on linux
Type "help", "copyright", "credits" or "license" for more information.

from summit.benchmarks import SnarBenchmark
from summit.strategies import NelderMead, MultitoSingleObjective
from summit.run import Runner
exp = SnarBenchmark()
transform = MultitoSingleObjective(
...     exp.domain, expression="-sty/1e4+e_factor/100", maximize=False
... )
nm = NelderMead(exp.domain, transform=transform)
r = Runner(
...     strategy=nm, experiment=exp,max_iterations=50
... )
r.run()

/home/ilario/.venv/lib/python3.10/site-packages/summit/strategies/neldermead.py:195: FutureWarning: In a future version of pandas all arguments of DataFrame.drop except for the argument 'labels' will be keyword-only.
next_experiments = next_experiments.drop(("constraint", "DATA"), 1)
/home/ilario/.venv/lib/python3.10/site-packages/summit/experiment.py:92: FutureWarning: The frame.append method is deprecated and will be removed from pandas in a future version. Use pandas.concat instead.
self._data = self._data.append(res)
/home/ilario/.venv/lib/python3.10/site-packages/summit/strategies/neldermead.py:146: FutureWarning: In a future version of pandas all arguments of DataFrame.drop except for the argument 'labels' will be keyword-only.
invalid_res = self.prev_param[1].drop(("constraint", "DATA"), 1)
[... many many more FutureWarning messages ...]
Traceback (most recent call last):
File "", line 1, in
File "/home/ilario/.venv/lib/python3.10/site-packages/summit/run.py", line 164, in run
next_experiments = self.strategy.suggest_experiments(
File "/home/ilario/.venv/lib/python3.10/site-packages/summit/strategies/neldermead.py", line 159, in suggest_experiments
next_experiments, xbest, fbest, param = self._inner_suggest_experiments(
File "/home/ilario/.venv/lib/python3.10/site-packages/summit/strategies/neldermead.py", line 457, in _inner_suggest_experiments
overfull_simplex, _, _, _, _, _ = self.check_overfull(
File "/home/ilario/.venv/lib/python3.10/site-packages/summit/strategies/neldermead.py", line 910, in check_overfull
raise ValueError(
ValueError: Simplex is overfull in one dimension. Please increase threshold for stopping.
´´´

Thanks for the new example in #202!
Now the code runs, but the plotting complains about this:

>>> r.experiment.pareto_plot(ax=ax)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'ax' is not defined. Did you mean: 'max'?

I suppose this has been fixed in e0b011198b2da3b135505c045c0599d9294e6068 (but I did not check), closing.


Fix PDF417 infinite loop

Backstepping should not violate startRow.
Fixes #316

In the image above, red & blue polygons are the detected PDF417 regions. The green line is the 171st row. This change restricts the backstepping so that it can find the two regions below the green line. Before this fix, the program would find the previous 2 regions again and thus end up in an infinite loop.

Thanks a lot for reporting and fixing this :).
Interestingly, this code has not been touched since it has been directly ported from the upstream Java code base. So I would assume they have the same issue in their code base as well (https://github.com/zxing/zxing/blob/8265242784be6f5493f1ede4b1fd1432b1666a54/core/src/main/java/com/google/zxing/pdf417/detector/Detector.java#L199) zxing.org does not hang, though, with that input image, so maybe we have some change upward in the callstack that caused this loop.


The selectAnnotation stops firing after an exception is thrown

Hello! Sorry for filing several GitHub issues recently, our team is using this library a lot and has been bumping into edge cases.
We've found that if the selectAnnotation event handler ever throws an exception, it breaks all future invocations of the event handler. This even persists after anno.destroy()!
Here's a minimal example to reproduce this bug: https://codepen.io/helloksong/pen/eYjMgvP
Steps to reproduce:

Click on an annotation once, and the event handler fires
Click on it again, and the event handler won't fire
Run anno.destroy() and initAnnotorious() in the console
Click on an annotation again, and the event handler won't fire

Hi,
hm - I'm not convinced that Annotorious should be responsible for isolating errors caused in the host application. Exceptions will generally break JS execution by design. If you know there's code that might raise an exception, then IMO the proper way is to handle it right there, inside the event handler. Otherwise, the app should crash rather than hide the error with a generic catch-call catch. So my personal take on this is: works as designed, TBH.

Thanks for the quick reply!
Understood. It was surprising to us that an exception in an event handler seemed to break the internal state of Annotorious (unlike other libraries which can be more forgiving). This is something we can work around though, if exceptions are not allowed by design.
The additional surprising thing is that anno.destroy() doesn't fully reset/fix the state. We call anno.destroy() frequently to swap images+annotations in a single global anno instance. Is this okay or should we be resetting the object in a different way?

Ok, yes I can reproduce. I'll need to dig deeper to understand what's going on. Which means it will take a while until I actually find the time. As a workaround: best avoid exceptions for now ;-)

No problem, we will avoid exceptions in event handlers then. Thank you!

Closing as won't fix (in v2)


Write a simple bot that can be used to run a load-test

This would be useful for a few specific things:

Did we fix localstorage issues?
If we have multiple window support, we may see as many as 2x connected clients. How does our system behave as we approach 1k concurrents?

Fairly low priority, I think, unless this is necessary to debug localstorage.


add optional parameters to Jenkins file

This will fix issues in nightly tests that doesn't need to configure SELINUX_MODE parameter
Signed-off-by: Mohamed Eldafrawi<EMAIL_ADDRESS>Ref: https://github.com/longhorn/longhorn/issues/3076

failed nightly tests: https://ci.longhorn.io/job/public/job/master/job/ubuntu/job/amd64/job/longhorn-tests-ubuntu-amd64/


Combine QR screens

Combine multi QR screen type into one or use fewer QR screen

Scan QR screen when click on Scan QR button on header to sign message/sign transaction with QR-signer account
Scan QR screen when attach QR-signer account
Scan QR screen when import account by QR code
Scan QR screen when attach read-only account

Separate action by data type:

Account address: => User need to choose next action

Send Fund or XCM Transfer
Attach Read-only Account

Scan Attach QR-Singer Data
Scan Import Account By QR
Scan signature payload

Same as https://github.com/Koniverse/SubWallet-Mobile/issues/1162


General Question, feel free to close.

How did you generate the 'autogen' directory? I've been dissecting the game memory manually and it's a huge pain(Particularily with tasks). It seems like you have a tool that provided at least some of the work for you, which would be amazing for me to use as well.

Honestly, the name autogen doesn't mean automatic code generation. It's just a directory with sources that I've obtained from game binary manually and/or partially automatically. Name autogen is used only by historical reasons.
On the question of automation, I use Il2CppDumper tool to extract functions (name, address, signature) and classes (name, layout, methods etc) from GameAssembly.dll + Among Us_Data/il2cpp_data/Metadata/global-metadata.dat.
Unfortunately, the developers have been using an obfuscator since Among Us v2020.9.22s, i.e. instead of PlayerTask class (2020.6.9) we have FKAPFNAKPBG (2020.11.4) or PILBGHDHJLH (2020.12.9). However, some structure members remain non-obfuscated so I use them as markers. Check out this repo for comments // [marker] (example).
P.S. il2cpp.h, dump.cs - output of Il2CppDumper for non-obfuscated version 2020.6.9, hope it helps.

Awesome, thanks a bunch. Very helpful!

Awesome, thanks a bunch. Very helpful!


Convert dag.tasks list to dict to avoid slowdown

After discussion with @mistercrunch, looks like #1213 introduced some slowdowns. I believe it's related to increased use of dag.get_task() which iterates over all tasks in dag.tasks. For example: https://github.com/airbnb/airflow/pull/1213/files#diff-a32a363fa616685db3bfefba947535b2R1767
The solution is to replace the list of tasks with a {task_id: task} dict. Adding a tasks property that returns a list of the dict's values means all other uses of dag.tasks should work.

Nice, I'm glad to find this, I'll just take it on from here

+1


Porting of basic medical items

About the PR
Resolves:

fix #522
fix #183
fix #642

This has turned into a way bigger project.

[x] Gauze
[x] First Aid Kits
[ ] First Aid Kit Fills
[x] Surgical Line
[x] Skin graft
[x] trauma kit
[x] burn kit
[x] pill bottles
[ ] health analyzer
[x] autoinjectors
[ ] autoinjector sounds
[ ]  autoinjectors for first aid fills

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

add: Ported some of the medical items from CMSS13.

If this satisfies the requirements for #183 let me know and I will add it to the description of the pr.

Fixing errors

Hey I forgot to mention this but it'll make your life easier, you don't need to port every different colour of chem. Just put one in, as the game can dynamically change the chem colour within the pen automatically!

thank you whisper

Anything I can help with

Anything I can help with

Health analyzer sprites would help

are the chemical heal and OD stats the same as CM13? if not ill PR that

are the chemical heal and OD stats the same as CM13? if not ill PR that

not yet, that also requires making Prototypes/_CM14/Reagents/Medical
Other than that, bringing over the colours description etc would be cool

are the chemical heal and OD stats the same as CM13? if not ill PR that

not yet, that also requires making Prototypes/_CM14/Reagents/Medical
Other than that, bringing over the colours description etc would be cool

ill try my hand at that tomorrow, but i gotta harvest the values first

yep I found the values, just gotta translate PROPERTY_ANTICORROSIVE = 3 into ss14 language, ill make an issue on this and provide progress

#813

this PR is alive?

CM had the surgical line and synth-graft sprites updated, they look better and are colourblind-friendly, please port those


How do I translate smth like list of services?

So, traditionally I would create an object smth like this
const obj = [
  {
    id: 1,
    title: 'Massage',
    description:
      'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut tincidunt non sem vel lacinia. Duis suscipit, nibh ut malesuada aliquet, velit est consectetur leo, quis consectetur ante mauris rutrum orci.',
  },
  {
    id: 2,
    title: 'Massage',
    description:
      'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut tincidunt non sem vel lacinia. Duis suscipit, nibh ut malesuada aliquet, velit est consectetur leo, quis consectetur ante mauris rutrum orci.',
  },
  {
    id: 3,
    title: 'Massage',
    description:
      'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut tincidunt non sem vel lacinia. Duis suscipit, nibh ut malesuada aliquet, velit est consectetur leo, quis consectetur ante mauris rutrum orci.',
  },
];

and then run my loop
const ServicesList = ({ className }) =>
  obj.map(({ title, description, id }) => (

      <ContentHeader>{title}</ContentHeader>
      <Content>{description}</Content>

  ));

Problem, however, with translations is that I have no idea how with default methods (without resorting to creating custom data) to pass multiple translations without manually adding them as props
<Services {...translate(['ServicesList.Massage.title ...... '])}  />
The bigger the list, the more manual work I have to do, plus I have to keep in mind if I delete smth to remove it from here as well, which is far from ideal.
Is there any way to do smth like this
<Services {...translate(['ServicesList'])}  />
And then run my .map function on the object to properly loop through translations, without restoring to custom data implementation?

So far, the only suitable way I found was to replicate the names in the list as an object and loop through em
const services = [
  { key: 1, value: 'Massage' },
  { key: 2, value: 'Face' },
  { key: 3, value: 'Therapy' },
];

const ServicesList = ({ className, translate }) =>
  services.map(({ key, value }) => (

      <ContentHeader>{translate(`ServicesList.${value}.title`)}</ContentHeader>
      <Content>{translate(`ServicesList.${value}.description`)}</Content>

  ));

Sorry I don't understand the use case from what you've provided. If you're able to provide a link to the full source that may help.

Thanks for the update, but the context I needed is still not included in this explanation. If you want my help I will need a working example to look at that shows the entire react-localize-redux implementation, with real translation data.

I'm going to close this for now as I haven't heard anything further. Feel free to reopen if you're able to provide the requested info.


Ask if venv should be created when initiating an existing Python project

Users are currently asked if a virtual environment (venv) should be created when creating a new Python project, this also triggers creation of tasks for manage builds within the venv. However, when importing/initiating an existing project (e.g. when git cloned), the user is not prompted in the same manner if a venv is to be created. This makes it harder to import an existing project.
I have copied the logic from the create flow to the init flow to provide the user with the same options.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: NVolcz sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Translate contribute guide to docs to spanish

Signed-off-by: jesuslerma<EMAIL_ADDRESS>Description
This PR fixes #1608
Notes for Reviewers
This is a proposal and it will be accessed over direct link /docs/es/project/contributing
Signed commits

[x] Yes, I signed my commits.

Muy bien Senor 🥳


Documentation: SplitConfigStore

Suggestion
Document the SplitConfigStore integration with all the necessary details that explain what the store is and how to use it.
Motivation

Introduces users to the ConfigStore.
Improves usability of the store by providing usage examples.
Improves the completeness of the integration package.

Context

Integration docs: https://help.split.io/hc/en-us
Example PR of a store doc contribution: #575

Got a hang of it . Kindly assign me this as well.

All yours @Ritesh-Udgata


support multiple sasl_passwd entries

with tests
Description
allows for multiple sasl_passwd entries
Issues Resolved
[List any existing issues this PR resolves]
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

this pr re-opens https://github.com/chef-cookbooks/postfix/pull/89 with updates to reflect master.

poke @tas50

@gnowxilef Any chance you've had a chance to look at @iennae's feedback?

ah, yes, let me update the readme.

@tas50 @iennae pr updated. :)

Sorry for the delay. Thanks for putting this together

Shouldn't this be flagged as a breaking change / have caused a major version bump?
Unless I'm missing something the attribute structure on existing projects no longer works - my deployment is now provisioning a /etc/postfix/sasl_passwd file with the content:
# Auto-generated by Chef.
# Local modifications will be overwritten.

smtp_sasl_passwd :
smtp_sasl_user_name :

which is of course completely broken. The readme implies both the old and new attribute format should work with this version but I can't see that's the case.


When will the toolchain be ready for installation

How to install the compiler on my Mac. The toolchain link is currently empty.

if you'd like to build from source and have an apple-darwin you can follow the instructions on the readme x86_linux probably works with some tweaks, unsure as I haven't tested myself on linux. If this is a general question about the project status, quite a lot of work has gone into the compiler and at the moment the runtime is being fleshed out (https://github.com/GetFirefly/firefly/commits/develop). A pre-compiled toolchain is likely to be ready for target architectures soon.

@mdshamoon I haven't had a chance to put together a precompiled toolchain package for macOS yet, but it is fairly straightforward to compile from source as mentioned by @hailelagi.
I've been holding off on a precompiled toolchain until some further runtime functionality is implemented, since at this point in time Firefly is not ready for any kind of production use, and the primary users at this point are people interested in contributing to the development of the project, so they'll be compiling from source anyway. I expect later this year we'll have enough runtime functionality implemented to make a proper prebuilt package worth publishing though.


fix: #46 do not use build-args in the dockerfiles, else we risk corrupt images

WHAT
Backport of solution https://github.com/eclipse-tractusx/knowledge-agents-edc/pull/47 to #46
Remove all references to catenax-ng in the .github folder
WHY
see #46
Catenax-Ng forks are abundant.
FURTHER NOTES
Closes #46

Same issues as in #47, please do not manage forks in upstream workflows.

I removed all catenax-ng fork references.


Theme import documentation

import { theme } from '@trendmicro/styled-ui-theme';
This doesn't work as per the documentation on getting started page.
import { theme } from "@trendmicro/react-styled-ui";
This works. So maybe we need to update the documentation.

This is fixed and should be closed.


postgresql: Move socket dir to /run/postgresql

The default, which is /tmp, has a few issues associated with it:
One being that it makes it easy for users on the system to spoof a PostgreSQL server if it's not running, causing applications to connect to their provided sockets instead of just failing to connect.
Another one is that it makes sandboxing of PostgreSQL and other services unnecessarily difficult. This is already the case if only PrivateTmp is used in a systemd service, so in order for such a service to be able to connect to PostgreSQL, a bind mount needs to be done from /tmp to some other path, so the service can access it. This pretty much defeats the whole purpose of PrivateTmp.
We regularly run into issues with this in the past already (one example would be https://github.com/NixOS/nixpkgs/pull/24317) and with the new systemd-confinement mode upcoming in https://github.com/NixOS/nixpkgs/pull/57519, it makes it even more tedious to sandbox services.
I've tested this change against all the postgresql NixOS VM tests and they still succeed and I also grepped through the source tree to replace other occasions where we might have /tmp hardcoded. Luckily there were very few occasions.

:+1: would be awesome if it was changed to /var/run/postgresql, as Debian/Ubuntu use that path by default. See https://sources.debian.org/src/postgresql-11/11.2-2/debian/patches/51-default-sockets-in-var.patch/ , but I guess /run and /var/run are mounted to each other in every distribution, so not a big deal.
Also, add release notes, because it can make old psql not to connect to new postgresql via UNIX socket.

Also, add release notes, because it can make old psql not to connect to new postgresql via UNIX socket.

Yep, that's why I added that label, just wanted to see first whether there is any opposition.

@thoughtpolice, @danbst: Done.

BTW, this should be only for Linux system, right? Does darwin platform have /run? cc @basvandijk

@danbst: Hm, good catch, but even if OSX would have /run, it probably won't have /run/postgresql. So I'm going to make this Linux-only.

@aszlig what's the socket path that PHP defaults to when connecting to a local postgresql?
Is there a way to tweak this one, similar to how I did for mysql in 5bb85cd45ce96a8c48e089711eead4129c36baf8?

@flokli: I haven't checked PHP in particular but I'd assume that it's using the default one in libpq like most other software.

@aszlig if that's the case, shouldn't overriding DEFAULT_PGSOCKET_DIR in this PR also make PHP find the proper socket path automatically?

@flokli: Exactly that is the idea. Just checked the PHP source and they rely fully on libpq and there is no NIH implementation. So this also covers PHP unless of course someone uses /tmp as the hostname in PDO/pg_connect, but see the changelog entry.

This PR seems to have broken the build of hydra, since it doesn't use the systemd service to launch postgresql and as such, it doesn't have a /run/postgresql to put the socket into...

can we tweak the hydra module to simply enable the postgresql module through services.postgresql?

wait, I don't get it - the hydra module already uses the postgresql module, and this one should set up /run/postgresql through RuntimeDirectory = "postgresql"…

no, that part's fine. It's during doCheck that it fails: https://hydra.nixos.org/build/91221682

@puckipedia we also can't just mkdir -p /run/postgresql in hydra's preCheck, as the sandbox doesn't allow to write to /run.
We however might be able to tweak hydra's tests/ to pass -k /tmp when instructing postgresql commands, didn't check.

Very unfortunate situation. I tend to revert this, and reapply when Nix does allow creating /run/postgresql. It can even be a build setup hook for postgresql, but Nix doesn't allow /run directory....
@aszlig what do you think?

@danbst: Nix doesn't need to allow this, because you can simply set PGHOST during preCheck to use a different socket path.

eg, similar to: https://github.com/nixcloud/nixcloud-webservices/blob/d8b966f8d25c08e9445fa9a28ba850afc2ffcc2d/modules/web/database/postgresql-hook.sh#L1

I just see it as regression - previously it was possible to do pg_ctl -D ... start and psql, but now you have specify socket directory both for server and client. It was useful...
Probably the best approach would be to patch postgres server to create socket in unix_socket_dir, and if it is not set, then create in /run/user/$(id -u), and if it doesn't exist, then use /run/postgresql. And implement same search logic for psql - first search in host argument/PGHOST, and if not specified, then in /run/user/$(id -u), if not found then search in /run/postgresql. This would still require Nix to allow /run directory and require setup hook for postgresql, to make things flawless.

Added a discussion topic here https://www.postgresql.org/message-id/CANZg%2Byd2OdqxM%3DHwnrkT-QecNMqLKNp%2BbGO_2SirJGznGK6h_w%40mail.gmail.com
Meanwhile, we just have to mention in release notes that pg_ctl should use custom socket dir (XDG_RUNTIME_DIR for users, /tmp for nix build environment) both for client and server.

@danbst can we either revert this PR, or add a fetchpatch https://github.com/NixOS/hydra/pull/648/commits/4171ab4c4fd576c516dc03ba64d1c7945f769af0.patch to get Hydra to build again?

I believe this might also fix a race condition between systemd-tmpfiles (caused by boot.cleanTmpDir) and postgres, that causes the socket to be deleted on boot.

@tilpner another reason to run systemd-tmpfiles as part of sysinit.target, before every other "regular" service ;-)
see https://github.com/NixOS/nixpkgs/pull/56265#issuecomment-487936452 and following.
cc @aanderse @erikarvstedt

This breaks postgres outside of NixOS, this shouldn't be patched but handled in the nixos modules instead IMHO.

@LnL7 true, but outside NixOS it is easy fixable with -h /tmp in client CLI arg, and -k /tmp server CLI arg. I agree this is less convenient, but sharing sockets through /tmp isn't generally safe in multiuser setup.

That doesn't matter, the default usage is broken because of non-standard behaviour. If this was a change in postgresql it would be another story.

While I think getting rid of sockets in /tmp is great (including /tmp/.X11-unix and /tmp/.ICE-unix while we're at it), it would be better if this were done upstream rather than in NixOS-specific patches.

So revert this PR and pass -k /run/... from the module?

Is anyone in favor of a socket option (potentially readOnly) so we can stop using so many magic strings all over NixOS modules every time we want to refer to a socket? Other modules like mysql would benefit from this as well. If so, let me know and I can whip something up.

@LnL7 unfortunately, it was already "non-standard", depending on what is "standard". Ubuntu (and Debian afaik) uses /var/run/postgresql as a de-factor standard socket path (same as we do now).
@edolstra Upstream doesn't work to improve this. https://www.postgresql.org/message-id/25758.1553906401%40sss.pgh.pa.us
@tilpner no, because PG consists of "server" and "client". And PG wants both to have same config parameter. So either both use same location, or they don't communicate each other.

@danbst Well, Tom Lane isn't wrong about "a Babel of servers and clients that can't talk to each other", as this issue shows...
Having said that, the fact that Ubuntu/Debian already use /run/postgresql is probably more relevant to us than what upstream does.

Unlike the apt packages, nix won't ensure these defaults are functional however.


Enhanced repository override

I propose aditions to ~/.sbt/repositories. Adding repository type by appending  # to url.
[repositories]
local: https://ponto.com:8081/content/repositories/snapshots/#maven
ivy-releases: https://ponto.com:8081/content/groups/sbt/#sbt
nexus: https://ponto.com:8081/content/groups/public/#maven
ivy: https://ponto.com:8081/content/groups/public/#ivy
tags: #maven - maven repository. No ivy specific files will be published
#sbt - ivy repo with #sbt layout
#ivy - maven repo with additional ivy files

Closing this since we won't likely implement it.


FFM-7642: adds tutorial at top of get started/landing page

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


issue due kCALineJoinBevel being renamed

Using SwiftChart 1.0.1 from cocoapods.
When building with xcode 10.2.1 and Swift language set to 5.0
I get this error:

'kCALineJoinBevel' has been renamed to 'CAShapeLayerLineJoin.bevel'

Is it possible to fix it,  and update cocoapod?
Should be small change.

Looks like the pod version wasn't updated, but the fix is already in the repo https://github.com/gpbl/SwiftChart/pull/105

I did pod "SwiftChart", :git => 'https://github.com/gpbl/SwiftChart', :branch => 'master' in the meantime

Is there going to be a new release for Swift 5?


⚠ Samsung has degraded performance

In 73242b8, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2278 ms

Resolved: Samsung performance has improved in cb59584.


handle get forms in addition to links

would be nice to have a standardized solution for get forms ... atm using this to make all get forms use turbolinks
// https://github.com/turbolinks/turbolinks/issues/272
// support remote get forms ... since turbolinks fails to do this properly
$(document).on('submit', 'form[method=get][data-remote=false]', function(e) {
  e.preventDefault();
  var form = $(this);
  Turbolinks.visit(form.attr("action") + form.serialize());
});

hmm yeah ... ujs issue ...
remote forms are supposed to return js ... and I'm just rendering a page ... so that cannot possibly work ...
so would be nice if turbolinks could optionally hook into get forms ... should be relatively straight forward ... and should be opt-in ...

my solution in es6
for(let i = 0; i < document.forms.length; i++) {
    const form = document.forms[i]
    if (form.method == "get" && form.dataset['remote'] == "true") {
      form.addEventListener("submit", (e) => {
        e.preventDefault();
        const entries = [...new FormData(e.target).entries()]
        const params = "?" + entries.map(e => e.map(encodeURIComponent).join('=')).join('&')
        Turbolinks.visit(form.action + params);
      });
    };
  };

I tried stefan694's solution but it hits the server twice.
But this works.
e.preventDefault()
e.stopImmediatePropagation()

Yet simply
e.stopImmediatePropagation()

alone causes a page reload (bypasses turbolinks)
It really would be nice to have the framework take care of this. It's a pretty standard way to handle a search form I think.

Any better workarounds for this in the core yet?

Right, for anyone who comes across this and needs to achieve the same with the latest Rails UJS (vanilla js version), I ended up with quite a clean solution after some digging:
import Turbolinks from 'turbolinks';
document.addEventListener('turbolinks:load', function(event) {
  for (let form of document.querySelectorAll('form[method=get][remote=true]')) {
    form.addEventListener('ajax:beforeSend', function (event) {
      const detail = event.detail,
            xhr = detail[0], options = detail[1];

      Turbolinks.visit(options.url);
      event.preventDefault();
    });
  }
});

@thelucid actually, you will want to grab forms with the data-remote attribute. took me 3 minutes to spot ;)
 import Turbolinks from 'turbolinks';

 document.addEventListener('turbolinks:load', function(event) {
-  for (let form of document.querySelectorAll('form[method=get][remote=true]')) {
+  for (let form of document.querySelectorAll('form[method=get][data-remote=true]')) {
     form.addEventListener('ajax:beforeSend', function (event) {
       const detail = event.detail,
             xhr = detail[0], options = detail[1];

@glaszig Good spot!

Right, for anyone who comes across this and needs to achieve the same with the latest Rails UJS (vanilla js version), I ended up with quite a clean solution after some digging:
import Turbolinks from 'turbolinks';

document.addEventListener('turbolinks:load', function(event) {
  for (let form of document.querySelectorAll('form[method=get][remote=true]')) {
    form.addEventListener('ajax:beforeSend', function (event) {
      const detail = event.detail,
            xhr = detail[0], options = detail[1];

      Turbolinks.visit(options.url);
      event.preventDefault();
    });
  }
});

See blog post: Handling GET remote forms with Turbolinks in Rails 6.

Thanks, mate, it worked! Will there be a fix any time soon?

@Freika I believe there are some significant changes coming to Turbolinks that will address this in a different way. I’ll post again if I hear more.

I'm not good at English, so I'm using DeepL to convert Japanese into English. I'm sorry if my grammar is wrong.
I think the selector data-remote=true is wrong, the setting data-remote=true was originally used to rewrite part of the screen using Ajax. Therefore, we don't think it's something to use in Turbolinks.visit.
As @grosser writes, data-remote=false is probably correct. However, if you set local=true in the form_with method, the attribute data-remote=false is not added.
So, I think we should try to exclude data-remote=true.
In my environment, this code works as expected.
import Turbolinks from 'turbolinks';

document.addEventListener('turbolinks:load', function(event) {
    for (let form of document.querySelectorAll('form[method=get]:not([data-remote=true])')) {
        form.addEventListener('submit', function (event) {
            event.preventDefault();
            const entries = [...new FormData(event.target).entries()];
            const actionUrl = new URL(event.target.action);
            const currentUrl = new URL(location.href);
            // if pathname not changed, hand over per parameter to next page.
            if (actionUrl.pathname === currentUrl.pathname && currentUrl.searchParams.has('per')) {
                actionUrl.searchParams.set('per', currentUrl.searchParams.get('per'))
            }
            entries.forEach(entry => actionUrl.searchParams.set(...entry));
            Turbolinks.visit(actionUrl.toString());
        });
    }
});

@patorash has a point. data-remote=true is somewhat exclusive to ujs...

Tiny modification to @patorash solution if we have this UI:

We get the following:

Thus the same key is set. Instead of entries.forEach(entry => actionUrl.searchParams.set(...entry)); => entries.forEach(entry => actionUrl.searchParams.append(...entry));. Append will do the trick well.
So here we have:
import Turbolinks from 'turbolinks';

document.addEventListener('turbolinks:load', function(event) {
    for (let form of document.querySelectorAll('form[method=get]:not([data-remote=true])')) {
        form.addEventListener('submit', function (event) {
            event.preventDefault();
            const entries = [...new FormData(event.target).entries()];
            const actionUrl = new URL(event.target.action);
            const currentUrl = new URL(location.href);
            // if pathname not changed, hand over per parameter to next page.
            if (actionUrl.pathname === currentUrl.pathname && currentUrl.searchParams.has('per')) {
                actionUrl.searchParams.set('per', currentUrl.searchParams.get('per'))
            }
            entries.forEach(entry => actionUrl.searchParams.append(...entry));
            Turbolinks.visit(actionUrl.toString());
        });
    }
});


move datashader logic from map.py to io/raster.py

add_datashader_gdf at the moment generates a raster using datashader and creates an ImageOverlay layer
The first half of that should be moved into io/raster.py and the map function should just be add_bitmap or similar

Closed with #178


Update Logstash filter to create fields for app/space/org

What
Update Logstash filter to create fields for app/space/org
We found syslog_host contained these fields but it caused some confusion as it
isn't the most obvious place to find the app name.
Creating separate fields for these will hopefully be more intuitive and make it
easier to produce queries when dealing with multiple apps shipping logs to a
single ELK stack.
How to review
Describe the steps required to test the changes.

Apply this configuration to an ELK stack
Ship logs to that ELK stack from CloudFoundry
Look in Kibana for the app / space / org fields

Who can review
Anyone familiar with logstash configuration.

Thanks to @philandstuff for helping me group the fields into a cf document.

👍 Have tested on Registers and works as expected.

Thanks! Someone from our team will review this soon.


Support for AMDGCN/ROCm.

This patch adds support targetting AMD discrete GPUs as a compute
device. The work in the patch was carried out in relay by @sklam
and @stuartarchibald.

Codecov Report

Merging #3023 into master will decrease coverage by 0.14%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #3023      +/-   ##
==========================================
- Coverage   85.68%   85.53%   -0.15%
==========================================
  Files         327      328       +1
  Lines       68842    69206     +364
  Branches     7807     7865      +58
==========================================
+ Hits        58984    59197     +213
- Misses       8611     8744     +133
- Partials     1247     1265      +18

how did numba/caching.py got in the diff with no change?

RE: https://github.com/numba/numba/pull/3023#issuecomment-403856241 its file mode is wrong. Moved 0x755->0x644

@sklam thanks for the review. I've made some changes based on things you noted and also things I picked up on self review. Am running this through the build farm now.

This is passing on the buildfarm on real AMDGCN hardware... merging.


Fixed word family import and added admin interface for word families

Coverage increased (+0.1%) to 42.81% when pulling d0b9108442c834e0eb498cc3f9978991a15d0d2f on feature/word-family-import into f35969c5bd2af30fba9430915e8d76cf636f8fd7 on feature/presenters.


🚀 Backward compatible with Map<dynamic, dynamic> encodes

Partially reverts #1704.
New Pull Request Checklist

[x] I have read the Documentation
[x] I have searched for a similar pull request in the project and found none
[x] I have updated this branch with the latest main branch to avoid conflicts (via merge from master or rebase)
[x] I have added the required tests to prove the fix/feature I'm adding
[x] I have updated the documentation (if necessary)
[x] I have run the tests without failures
[x] I have updated the CHANGELOG.md in the corresponding package

Additional context and info (if any)
When constructing the data like {key: value}, it can be easy that the type is inferred to a dynamic map, rather than Map<String, dynamic>. So #1704 breaks part of previous usages and those usages become invalid after upgraded.

I don't think we should allow this. I surely didn't think of that cases when I fixed the encoding problems :)
Other than that, it looks ok.

I don't think we should allow this.

Any intentions or reasons about this?

I don't think we should allow this.

Any intentions or reasons about this?

It will just lead to problems and hard to trace issues with people having weirdly encoded keys.


Fixing the README.md

I was testing with the library using the readme.md as guide but notice some issues in the example code.
import numpy as np
from gym.spaces import Box
from rc_gym.Entities import Ball, Frame, Robot
from rc_gym.ssl.ssl_gym_base import SSLBaseEnv

"""
rc_gym doesn`t work, this works:
"""
from rsoccer_gym.Entities import Ball, Frame, Robot
from rsoccer_gym.ssl.ssl_gym_base import SSLBaseEnv

def _frame_to_observations(self):
    ball, robot = self.frame.ball, self.frame.robots_blue[0]
    return np.array([ball.x, ball.y, rbt.x, rbt.y]) # , robot.x, robot.y])

I created a PR to solve this issues:
https://github.com/robocin/rSoccer/pull/47

Thank you for the contribution, sorry for the error! We will work on improving our documentation


pull request for e2e test at 01/25/2017 00:45:07

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


Site down & no HTTPS

It looks like the site is down https://dfuse.io/ and HTTPS certificate is not present.

Try dfuse.eosnation.io


Preview: Catch-all page at root level catches requests for NextJS static assets

I have the following (minimal) example:
// pages/api/preview.js
export default async (req, res) => {
  return res.status(404).json({ message: 'Not found' })
}

////////////////////

// pages/index.js
import Link from 'next/link'

function IndexPage() {
  return <Link href='/mypage'>My page</Link>
}

export async function getStaticProps() {
  return {
    props: {}
  }
}

export default IndexPage

////////////////////

// pages/[...slug].js
const SlugPage = () => {
  return null
}

export async function getStaticProps({params: {slug}}) {
  console.log(`slug = ${slug}`)

  return {
    props: {}
  }
}

export async function getStaticPaths() {
  return {
    paths: [],
    fallback: true
  };
}

export default SlugPage

When I run this example using netlify dev I get an invalid getStaticProps parameter value for slug: _next,static,chunks,pages,[...slug]-0ab994ad29aa8a4f0aaa.js.
The full output is:
◈ Rewrote URL to /.netlify/functions/next_slug
Request from ::1: GET /.netlify/functions/next_slug
info  - Loaded env from .env
[request] /_next/static/chunks/pages/%5B...slug%5D-0ab994ad29aa8a4f0aaa.js
slug = _next,static,chunks,pages,[...slug]-0ab994ad29aa8a4f0aaa.js
Response with status 200 in 225 ms.
Request from ::1: GET /.netlify/functions/next_slug
[request] /_next/data/vAFu7puWIo_lpacbTliex/mypage.json
slug = mypage
Response with status 200 in 54 ms.

Is this a bug?
NB. the <Link> element is necessary to trigger the behaviour.

Interesting scenario!
You have a catch-all route at root-level — it catches all paths: /whatever/path/...
The request at [request] /_next/static/chunks/pages/%5B...slug%5D-0ab994ad29aa8a4f0aaa.js is where NextJS is trying to load the page's code. If you look under out_publish/_next/..., you should find this JS file. But rather than loading the code file, the request is being re-routed to the catch-all page instead. That's why you get all the path segments when you console.log the slug.
Because of shadowing, your request for /_next/static/... should not be rewritten to the [...slug].js page. So there's definitely an issue here and I'm happy to get to the bottom of it.
If you have time, the following would be extremely helpful:

What version of netlify-cli are you on (netlify --version)? If it's not v2.63.2 (latest), can you upgrade?
Do you have time to create a mini repo with these three pages for me to clone?
Does the code work on netlify.com?

I am using the following netlify-cli version: netlify-cli/2.63.2 darwin-x64 node-v13.7.0 and created this https://github.com/joostmeijles/next-on-netlify-catchall-bug mini repo.
The site is deployed here: https://friendly-babbage-dcd353.netlify.app/, but I don't know how to see the same logging.

That's a bug in netlify dev! reqUrl.pathname should be wrapped in decodeURIComponent() in:
https://github.com/netlify/cli/blob/c4ce6bba298ab3c7deb0d5b409e9c36ff21fd3da/src/utils/proxy.js#L149
You can create an issue or PR in netlify dev, if you want. A quick workaround in the meantime is to add a custom redirect to your NextJS app by adding a _redirects file to your project root:
/_next/* /_next/:splat 200

This redirect will become the first redirect in your list of Netlify redirects and catch all the requests for NextJS static assets.

I'll make a PR for this @FinnWoelm, thanks for finding that!!

Awesome! :raised_hands: :blush: I already have a sample repo https://github.com/FinnWoelm/netlify-uri-bug, in case it's helpful.

The CLI fix is released in the latest CLI version - v2.63.3, thanks @cassidoo and @FinnWoelm. Please let me know if you're experiencing other issues.

Tested, works as a charm!
Thanks for the prompt fix over the weekend 🚀


why TheD435i becomes d430i

Hi，hello everyone，
After updating my d435i to the latest firmware version with realsensor viewer, it becomes d430i. No matter which version of firmware is updated, it will not be displayed as d435i in realsensor viewer. Under Linux, windows displays d430i, and its serial number is<PHONE_NUMBER>72.
thank you very much

The model that the camera is detected as depends on the sensor components that are detected by the firmware driver.  If a D435's RGB sensor cannot be detected then the firmware identifies the camera as a D430, as the D430 Depth Module (the camera circuit board inside the D435) does not have an integrated RGB sensor.  In the D435, the RGB sensor is attached separately to the D430 camera board via a cable.
https://github.com/IntelRealSense/librealsense/issues/3124#issuecomment-500233636
There have been a couple of extremely rare cases where the internal cable has become disconnected, so that the D435 is recognised as D430.  It is not something that you could check without opening the camera's casing and invalidating any remaining warranty on it though.
The most common fix is to downgrade the firmware and then re-upgrade to the latest firmware (i.e do not downgrade to an old one and then an older one).
If a firmware downgrade-upgrade does not fix the problem and you do not want to check inside the casing, you should have the option of returning the camera for a replacement if you purchased it less than 30 days ago.

Hi @bjthemost   Do you still require assistance with this case, please?   Thanks!

It's been a long time since the warranty
And in China
so。。。
I'm going to throw him back,
thank you @MartyG-RealSense

Thanks very much for the update.  I appreciate it.


Update values.yaml

Hi, shouldnt it be alerts-kapacitor instead of kap-kapacitor to match the kapacitor helm chart?

to match whats in ./create.sh

@jackzampolin -- can you take a quick look?

@naseemkullah You would be correct here. Good catch.


Lots of compilation errors when invoking "pio run" for the [env:esp32dev_wifi] pio environment

Issue template
Several compilation errors when compiling for the [env:esp32dev_wifi] environment.
How do I resolve these?

Hardware description: esp32
RTOS: arduino
Installation type: micro_ros_platformio
Version or commit hash: master

Steps to reproduce the issue

$ git clone git@github.com:safdark/micro_ros_platformio_ci.git ./ci
(This is a copy of the ci/ folder from the original repository, with only the esp32dev_wifi environment present in the platformio.ini file, for simplicity)

$ cd ci

$ pio lib install

Library Storage: /home/safdar/code/repositories/myproject_firmware/entrypoints/ci/.pio/libdeps/esp32dev_wifi
Library Manager: Installing git+https://github.com/micro-ROS/micro_ros_platformio
git version 2.25.1
Cloning into '/home/safdar/.platformio/.cache/tmp/pkg-installing-fvshhh20'...
remote: Enumerating objects: 64, done.
remote: Counting objects: 100% (64/64), done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 64 (delta 10), reused 42 (delta 5), pack-reused 0
Unpacking objects: 100% (64/64), 123.23 KiB | 882.00 KiB/s, done.
Library Manager: micro_ros_platformio @ 0.0.1+sha.c20916a has been installed!

$ pio run

Expected behavior
Should compile succesfully since I haven't changed anything in the original ci/ folder.
Actual behavior
Output:
$ pio run

Processing esp32dev_wifi (platform: espressif32; board: esp32dev; framework: arduino)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32dev.html
PLATFORM: Espressif 32 (3.5.0) > Espressif ESP32 Dev Module
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (esp-prog) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
 - framework-arduinoespressif32 3.10006.210326 (1.0.6)
 - tool-esptoolpy 1.30100.210531 (3.1.0)
 - toolchain-xtensa32 2.50200.97 (5.2.0)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Installing pyyaml with pip at PlatformIO environment
/home/safdar/.platformio/penv/bin/python -m pip install pyyaml
Requirement already satisfied: pyyaml in /home/safdar/.platformio/penv/lib/python3.8/site-packages (6.0)
WARNING: You are using pip version 21.3.1; however, version 22.0.4 is available.
You should consider upgrading via the '/home/safdar/.platformio/penv/bin/python -m pip install --upgrade pip' command.
Installing markupsafe==2.0.1 with pip at PlatformIO environment
/home/safdar/.platformio/penv/bin/python -m pip install markupsafe==2.0.1
Requirement already satisfied: markupsafe==2.0.1 in /home/safdar/.platformio/penv/lib/python3.8/site-packages (2.0.1)
WARNING: You are using pip version 21.3.1; however, version 22.0.4 is available.
You should consider upgrading via the '/home/safdar/.platformio/penv/bin/python -m pip install --upgrade pip' command.
Configuring esp32dev with transport wifi
Downloading micro-ROS dev dependencies
	 - Downloaded ament_cmake
	 - Downloaded ament_lint
	 - Downloaded ament_package
	 - Downloaded googletest
	 - Downloaded ament_cmake_ros
	 - Downloaded ament_index
Building micro-ROS dev dependencies
Downloading micro-ROS library
	 - Downloaded microcdr
	 - Downloaded microxrcedds_client
	 - Downloaded rcl_yaml_param_parser (ignored)
	 - Downloaded rcl_lifecycle
	 - Downloaded rcl_action
	 - Downloaded rcl
	 - Downloaded rclc
	 - Downloaded rclc_examples (ignored)
	 - Downloaded rclc_parameter
	 - Downloaded rclc_lifecycle
	 - Downloaded micro_ros_utilities
	 - Downloaded rcutils
	 - Downloaded micro_ros_msgs
	 - Downloaded rmw_microxrcedds
	 - Downloaded rosidl_typesupport_c
	 - Downloaded rosidl_typesupport_cpp (ignored)
	 - Downloaded rosidl_typesupport_microxrcedds_c
	 - Downloaded rosidl_typesupport_microxrcedds_cpp (ignored)
	 - Downloaded rosidl_typesupport_microxrcedds_cpp_tests
	 - Downloaded rosidl_typesupport_microxrcedds_test_msg
	 - Downloaded rosidl_typesupport_microxrcedds_c_tests
	 - Downloaded rosidl_typesupport_introspection_c
	 - Downloaded rosidl_generator_c
	 - Downloaded rosidl_runtime_cpp (ignored)
	 - Downloaded rosidl_cmake
	 - Downloaded rosidl_runtime_c
	 - Downloaded rosidl_parser
	 - Downloaded rosidl_typesupport_introspection_cpp (ignored)
	 - Downloaded rosidl_adapter
	 - Downloaded rosidl_cli
	 - Downloaded rosidl_typesupport_interface
	 - Downloaded rosidl_generator_cpp (ignored)
	 - Downloaded rmw
	 - Downloaded rmw_implementation_cmake
	 - Downloaded statistics_msgs
	 - Downloaded composition_interfaces
	 - Downloaded rcl_interfaces
	 - Downloaded rosgraph_msgs
	 - Downloaded action_msgs
	 - Downloaded builtin_interfaces
	 - Downloaded test_msgs
	 - Downloaded lifecycle_msgs
	 - Downloaded rosidl_default_generators
	 - Downloaded rosidl_default_runtime
	 - Downloaded unique_identifier_msgs
	 - Downloaded actionlib_msgs
	 - Downloaded stereo_msgs
	 - Downloaded diagnostic_msgs
	 - Downloaded sensor_msgs
	 - Downloaded std_msgs
	 - Downloaded visualization_msgs
	 - Downloaded shape_msgs
	 - Downloaded sensor_msgs_py
	 - Downloaded std_srvs
	 - Downloaded trajectory_msgs
	 - Downloaded nav_msgs
	 - Downloaded common_interfaces
	 - Downloaded geometry_msgs
	 - Downloaded test_interface_files
	 - Downloaded test_rmw_implementation
	 - Downloaded rmw_implementation
	 - Downloaded rcl_logging_spdlog (ignored)
	 - Downloaded rcl_logging_interface
	 - Downloaded rcl_logging_log4cxx (ignored)
	 - Downloaded rcl_logging_noop
	 - Downloaded tracetools_read
	 - Downloaded tracetools
	 - Downloaded tracetools_trace
	 - Downloaded tracetools_test
	 - Downloaded tracetools_launch
	 - Downloaded ros2trace
Checking extra packages
	 - Downloaded control_msgs
	 - Adding my_custom_message
Building micro-ROS library
Build mcu micro-ROS environment failed:

...
...
...   <<<<<< Several CMake Warning messages >>>>>>
...
...

CMake Error at /opt/ros/galactic/share/rosidl_typesupport_fastrtps_c/cmake/rosidl_typesupport_fastrtps_c-extras.cmake:5 (find_package):
  Could not find a configuration file for package "fastcdr" that is
  compatible with requested version "".

  The following configuration files were considered but not accepted:

    /opt/ros/galactic/lib/cmake/fastcdr/fastcdr-config.cmake, version: 1.0.20 (64bit)
    /usr/local/lib/cmake/fastcdr/fastcdr-config.cmake, version: 1.0.23 (64bit)

Call Stack (most recent call first):
  /opt/ros/galactic/share/rosidl_typesupport_fastrtps_c/cmake/rosidl_typesupport_fastrtps_cConfig.cmake:41 (include)
  /home/safdar/code/repositories/myproject_firmware/entrypoints/ci/.pio/libdeps/esp32dev_wifi/micro_ros_platformio/build/mcu/install/share/rosidl_typesupport_c/cmake/rosidl_typesupport_c-extras.cmake:13 (find_package)
  /home/safdar/code/repositories/myproject_firmware/entrypoints/ci/.pio/libdeps/esp32dev_wifi/micro_ros_platformio/build/mcu/install/share/rosidl_typesupport_c/cmake/rosidl_typesupport_cConfig.cmake:41 (include)
  /home/safdar/code/repositories/myproject_firmware/entrypoints/ci/.pio/libdeps/esp32dev_wifi/micro_ros_platformio/build/mcu/install/share/rosidl_default_generators/cmake/rosidl_default_generators-extras.cmake:21 (find_package)
  /home/safdar/code/repositories/myproject_firmware/entrypoints/ci/.pio/libdeps/esp32dev_wifi/micro_ros_platformio/build/mcu/install/share/rosidl_default_generators/cmake/rosidl_default_generatorsConfig.cmake:41 (include)
  CMakeLists.txt:14 (find_package)

---
Failed   <<< lifecycle_msgs [0.61s, exited with code 1]

============================================================================================================================== [FAILED] Took 59.21 seconds ==============================================================================================================================

Additional information

I have tried this both with and without sourcing the environment for ROS2.
I upgraded colcon to version 0.8.2.

$ colcon version-check
colcon-argcomplete 0.3.3: up-to-date
colcon-bash 0.4.2: up-to-date
colcon-cd 0.1.1: up-to-date
colcon-cmake 0.2.26: up-to-date
colcon-core 0.7.1: newer version available (0.8.2)
colcon-defaults 0.2.6: up-to-date
colcon-devtools 0.2.3: up-to-date
colcon-library-path 0.2.1: up-to-date
colcon-metadata 0.2.5: up-to-date
colcon-notification 0.2.13: up-to-date
colcon-output 0.2.12: up-to-date
colcon-package-information 0.3.3: up-to-date
colcon-package-selection 0.2.10: up-to-date
colcon-parallel-executor 0.2.4: up-to-date
colcon-pkg-config 0.1.0: up-to-date
colcon-powershell 0.3.7: up-to-date
colcon-python-setup-py 0.2.7: up-to-date
colcon-recursive-crawl 0.2.1: up-to-date
colcon-ros 0.3.22: newer version available (0.3.23)
colcon-test-result 0.3.8: up-to-date
colcon-zsh 0.4.0: up-to-date

Environment:
$ env | grep ROS
ROS_VERSION=2
ROS_PYTHON_VERSION=3
ROS_LOCALHOST_ONLY=0
ROS_DISTRO=galactic

PIO version:
$ pio --version
PlatformIO Core, version 5.2.5

@Acuadros95 , my previous output was:
$ env | grep RMW
RMW_IMPLEMENTATION=rmw_fastrtps_cpp

...because I read somewhere that only FastRTPS is guaranteed to work with MicroROS.
In any case, I changed it to RMW_IMPLEMENTATION=rmw_microxrcedds, as per your recommendation, and did a clean build, but I still get the same errors as above.

I think you have ROS2 sourced by default on your terminal, at least its sourced on the environment you provided:
AMENT_PREFIX_PATH=/opt/ros/galactic
Please try with this PR, which removes ROS2 sourced references out of the micro-ROS build process: https://github.com/micro-ROS/micro_ros_platformio/pull/25

Thanks @Acuadros95 !!
I incorporated that PR (i,e the fix/ros_source branch) and that worked!

Btw, regarding the RMW_IMPLEMENTATION setting, as you mentioned, this package requires that that be set to rmw_microxrcedds. However, I had read elsewhere that only rmw_fastrtps_cpp is guaranteed to work with MicroROS. Is that not a constraint any more?

Yes, only rmw_fastrtps_cpp is compatible on ROS2 side.
This means that you need to use FastRTPS as your ROS2 middleware when using ros2 console commands or running a rclcpp node, but micro-ROS uses rmw_microxrcedds internally.
So when generating the micro-ROS binary, rmw_microxrcedds shall be used.

Thanks @Acuadros95 !! I incorporated that PR (i,e the fix/ros_source branch) and that worked!

Could someone explain how to do this, I have the same problem, but im a bit of a git noob.

@1larity Could you explain your problem? The fix for this issue is already on the latest main branch.


No routes folder

There's no routes folder on any version

Not a bug. It's in the route service provider.


get full datasource/database/schema/table/column information of field

For each fields used in a worksheet, we would like to know where does this field come from, basically datasource connection, database/schema/table/column name.
Is there any API support this requirement?

Currently, the Extensions API will not give you insight at that level. If you are interested in seeing this information on Server, there is an API that is being worked on that will let you query data source information, but it will likely not be released until later this year.


Add ENA driver

ENA is a network driver supported on newer EC2 instance types and has full DPDK support. It does not have hardware timestamping support but software timestamping works as expected.

thanks!


Add the bill of materials for dependencies.

Yes, you can re-run the license-bill-of-materials tool: https://github.com/coreos/license-bill-of-materials


Empty SG card in private SG

The issue happens if VM is created with errors (card with only one option Delete) and this VM is destroyed. Private SG for this vm isn't updated.
Steps:

Create VM with error - (here such vm can be created with exceeded cpu limit http://cs-ui-ci.z1.netpoint-dc.com:8080/qqcky/860-service-offering-limitations)
Destroy this vm
Go to Private SG

Expected result: filled correct data list/card private sg appear
Actual result: empty card for private sg

Unable to reproduce error, please provide more detailed info @Nadya913 .
After step 1 I get Error and there is no vm to delete for step 2.
In Private SG I did not found any empty card

I created wrong VM (vm-develop-1059), would you please try to reproduce with this vm?
Updated Steps:

Create new VM with custom wrong characteritics: 2x10015 MHz | 518.00 MB
Got error, refresh the page and see this vm, destroy it
Go to Private SG

Thanks, I was able to reproduce the problem with your specifications.
This problem only appears if you did not wait for the removal (expulsion) of your virtual machine to complete and moved to the SG private tab.
But, I think that the problem should not be with an empty SG, but with the fact that when an error occurs during the creation process, the machine was created and it must be manually deleted.

Update to my comment.
PO explained that creating VM with error and not delete it automatically is the default behavior for Cloudstack. So we need to fix the issue as it is explained by Nadya.

Test on:
tamazlykar:989-empty-sg

Tested on:
tamazlykar:989-empty-sg


bump 3.0.7

moving on up to Cassandra 3.0.7 first attempt

👍

👍

rebuild this please

rebuild this please


Llvm fixes

Misc fixes to the LLVM front-end.
It would be nice to get a review before I push it to trunk. Thanks!
Marek

(rebased on the current trunk)

Thanks for the fixes and the explanations - feel free to merge this to our SVN trunk :-)

Merged.


The tests for latest master work on 0.4, except for the method overwrite warnings

Doing git checkout master on 0.4 gives passing tests (but, of course, with the method overwrite warnings).

Coverage remained the same at 100.0% when pulling 190eaee6e02e94551abb11211856458c8d92222c on dpsanders:retag_0.4 into 3c08c9af9ebeaa54589e939c0cf2e652ef4ca6a0 on JuliaLang:master.

Ironically, the tests now fail on 0.5.


Change graph based on overlay data

This PR makes it possible to feed external speed or access changes via GeoJSON. For now it is not yet integrated in e.g. GraphHopper core or web. But you can easily add it via:
GraphHopper myHopper = new GraphHopperOSM() {

    public void postProcessing()
    {
        super.postProcessing();
        FeedOverlayData instance = new FeedOverlayData(getGraphHopperStorage(),
                getEncodingManager(), getLocationIndex(), new GHsonBuilder().create());
        long updates = instance.applyChanges(fileOrFolderAsString);
    }
}

pom.xml:
        <dependency>
            <groupId>com.graphhopper</groupId>
            <artifactId>graphhopper-reader-overlay-data</artifactId>
            <version>0.8-SNAPSHOT</version>
        </dependency>

E.g. see FeedOverlayDataTest or an example json file
Keep in mind that the order of any coordinate array is lon,lat and e.g. the bbox is min_lon,min_lat,max_lon,max_lat like specified in the Geojson spec. Also currently only three cases for a Feature are implemented:

type=Point,
type=MultiPoint and
no type and no properties.coordinates entry but with a bounding box entry bbox

It furthermore introduces a Json reader wrapper as discussed in #773 backed by Gson.
The overlay change functionality will stay in separate module reader-overlay-data. It goes even further and as we need map matching functionality in this reader module, we potentially have to move the currently separate map matching component into this repository here. Keeping it necessary and still depend on it would not work well.
Keep in mind: the feeding mechanism is not thread safe, so you should not use this for real time updates without some locking. And it would work only for non-CH, but this method here is before the preparation and works with CH as applied only once.

Currently the default is to pick the first vehicle if non is specified in the file, maybe we should apply the change to all vehicles instead.

Will merge soon

Attached is a real world example (berlin area) to block access (car) and lower speed (foot)
overlaydata1.json.zip
for foot => http://localhost:8989/?point=52.51006%2C13.375436&point=52.510655%2C13.373221&vehicle=foot
for car => http://localhost:8989/?point=52.51055%2C13.375779&point=52.510955%2C13.375688&vehicle=car

Is now merged to master: https://github.com/graphhopper/graphhopper/commit/9a9f34ad67ec661568d35a1b4ebf43012d21fec6

Using serialization classes e.g. 'ConfigurationPojo' in the core will avoid using this 'heavier' dependency into the core. We can deserialize the json in the web module into such a 'serialization object' and forward this.


Class stories

Class stories are stories which are bound to the class object.
Their main purpose is to enable using stories with inheritance:
from stories import class_story, Success

class Example:
  @class_story
  def x(cls, I):
    I.one

  def one(self, ctx):
    return Success()

class ExtendedExample(Example):
  @class_story
  def x(cls, I):
    super(ExtendedExample, cls).x(I)
    I.two

  def two(self, ctx):
    return Success()

As demonstrated by the tests and documentation, this also works with multiple inheritance with one exception (which we can resolve later).
This feature opens up more possibilities for the user
such as dynamically generating stories based on class attributes
or conditionally including a step based on a class attribute.
Implementing this feature took some refactoring
to resolve the circular references caused by importing
wrap_story() and MountedStory.
I moved wrap_story() to ClassMountedStory since it's the only place that uses it,
it has all the required state to wrap a story and it makes sense to have
a direct mapping between ClassMountedStory and MountedStory.
In addition, we don't collect strings anymore but CallMethod objects.
These objects allow us to customize the way we collect our steps.

If you have an idea how to fix the doctest, I'd appreciate it.
They should be working...

With a heavy heart, I will mark it as a won't fix.
I see how much effort you put into it. And I understand that you need this feature for other projects of yours.
I would admit that dependencies, stories, mappers, and (in future) predicates libraries have a ton of my opinion in the design of the API.
The feature set you've implemented in this PR is kinda opposite to the direction I want this project to evolve.
Given that we have the same disagreement on the ABC stories, I concluded that you and I want two different libraries in the end.
It's totally fine of course for people to have different opinions. And I respect the approach you take.
If you need such kind of API for your libraries, maybe it would be easier for you to fork the project and create an alternative library from it. I would be happy to put a link to it in the documentation.
With all respect, I'll close the PR.
Best regards,
Artem.


Render Audio Player if Tool Result resource mime type is audio.

Show the browser audio player if resource mime type is audio.
Motivation and Context
Makes testing audio tool results integration simpler.
How Has This Been Tested?
This has been tested with an MCP Server calling Parler/TTS.
...
      const audioBase64 = await generateSpeech(text);
      return {
        content: [{
          type: "resource",
          resource: {
            uri: "audio:///" + crypto.randomUUID(),
            mimeType: "audio/wav",
            blob: audioBase64
          }
        }]
      };
    }
...

async function generateSpeech(text: string): Promise<string> {
  const client = await Client.connect("parler-tts/parler_tts");
  const result = await client.predict("/gen_tts", {
    text,
    description: "Laura's voice is monotone yet slightly fast in delivery, with a very close recording that almost has no background noise.",
    use_large: false
  });

  // Fetch the audio file
  const response = await fetch(result.data[0].url);
  const arrayBuffer = await response.arrayBuffer();

  // Convert to base64
  const base64 = Buffer.from(arrayBuffer).toString('base64');

  return base64;
}

Breaking Changes
No - but the Client Reference Implementation (Claude Desktop does not support Audio content).
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update

Checklist

[X] I have read the MCP Documentation
[X] My code follows the repository's style guidelines
[X] New and existing tests pass locally
[X] I have added appropriate error handling
[X] I have added or updated documentation as needed

Hey @evalstate, apologies for the delay here. After some consideration, we'd like to avoid having the inspector showcase any features that aren't in the official spec. So this particular PR will need to wait until the spec discussion you started gets to a resolution.

Hi Ashwin -
This PR renders the audio component if the mime type of the Resource is audio (so in-spec). It's very convenient for testing.
The reverted commit handled the change to the Schema - and was accidentally committed to the branch. Ideally changes to the spec could be coordinated with updates to SDK and Inspector for testing. I fat-fingered this one - hence the delete of that commit .
Best.