owo-lib does not install automatically and the game won't start without it

In the release notes it is stated that "owo-lib is now a required dependency, installed automatically through sentinel" but when I installed isometric-renders from Modrinth using PolyMC the game wouldn't start and will be stuck at listing the installed mods Loading 181 mods: ....
After I installed owo-lib manually, everything worked again.

You don't happen to be running macOS?

@gliscowo I do, macOS Ventura on an M2 machine, why?

We are already aware of this issue, see https://github.com/wisp-forest/owo-lib/issues/51

@Noaaan oh, sorry, I missed that one. Can I somehow help with the testing or is this the same old "no macos in GitHub actions" problem?

The problem here is quite simply that AWT, which sentinel uses, does not work in an MC environment on macOS - something we didn't initially anticipate when developing sentinel. There's a mitigation underway, but for the time being there's nothing you can do to help - we very much appreciate the offer however.
Cheers

This is now no longer an issue with owo 0.8.3


Add configuration ordering tests.

Refactor host building to better support unit testing.
Add extension methods for replacing environment configuration sources.
cc @kkeirstead

/backport to release/6.0

/backport to release/6.x


Warnings: deprecated tensorflow features

Hi,
I've just started using this library in a project and I'm getting these warnings:
When importing the library:
WARNING:tensorflow:From C:\Users\<>\py39\lib\site-packages\keras\src\losses.py:2976: The name tf.losses.sparse_softmax_cross_entropy is deprecated. Please use tf.compat.v1.losses.sparse_softmax_cross_entropy instead.

WARNING:tensorflow:From C:\Users\<>\py39\lib\site-packages\tensorflow_probability\python\internal\backend\numpy\_utils.py:48: The name tf.logging.TaskLevelStatusMessage is deprecated. Please use tf.compat.v1.logging.TaskLevelStatusMessage instead.

WARNING:tensorflow:From C:\Users\<>\py39\lib\site-packages\tensorflow_probability\python\internal\backend\numpy\_utils.py:48: The name tf.control_flow_v2_enabled is deprecated. Please use tf.compat.v1.control_flow_v2_enabled instead.

When I instantiate a CI instance:
WARNING:tensorflow:From C:\Users\jharris\py39\lib\site-packages\tensorflow\python\autograph\impl\api.py:459: StructuralTimeSeries.joint_log_prob (from tensorflow_probability.python.sts.structural_time_series) is deprecated and will be removed after 2022-03-01.
Instructions for updating:
Please use `StructuralTimeSeries.joint_distribution(observed_time_series).log_prob`

WARNING:tensorflow:From C:\Users\jharris\py39\lib\site-packages\tensorflow\python\autograph\impl\api.py:459: StructuralTimeSeries.joint_log_prob (from tensorflow_probability.python.sts.structural_time_series) is deprecated and will be removed after 2022-03-01.
Instructions for updating:
Please use `StructuralTimeSeries.joint_distribution(observed_time_series).log_prob`

WARNING:tensorflow:From C:\Users\jharris\py39\lib\site-packages\causalimpact\model.py:408: calling one_step_predictive (from tensorflow_probability.python.sts.forecast) with timesteps_are_event_shape=True is deprecated and will be removed after 2021-12-31.
Instructions for updating:
`Predictive distributions returned by`tfp.sts.one_step_predictive` will soon compute per-timestep probabilities (treating timesteps as part of the batch shape) instead of a single probability for an entire series (the current approach, in which timesteps are treated as event shape). Please update your code to pass `timesteps_are_event_shape=False` (this will soon be the default) and to explicitly sum over the per-timestep log probabilities if this is required.

WARNING:tensorflow:From C:\Users\jharris\py39\lib\site-packages\causalimpact\model.py:408: calling one_step_predictive (from tensorflow_probability.python.sts.forecast) with timesteps_are_event_shape=True is deprecated and will be removed after 2021-12-31.
Instructions for updating:
`Predictive distributions returned by`tfp.sts.one_step_predictive` will soon compute per-timestep probabilities (treating timesteps as part of the batch shape) instead of a single probability for an entire series (the current approach, in which timesteps are treated as event shape). Please update your code to pass `timesteps_are_event_shape=False` (this will soon be the default) and to explicitly sum over the per-timestep log probabilities if this is required.

I still get output but I think these will need to be updated?

Hi @TravelsandBooks ,
Those warnings are indeed annoying but unfortunately everything that I've tried to remove those failed. If someone figures it out we can implement how it's done but so far nothing worked.
For now you can safely ignore them, they are part tensorflow itself.


mdx: implement MDX generation from generated JSON

This PR implements MDX generation from the generated doc.json. To work with this:

In the root folder, do make gen (if not generated previously)
Then, still in the root folder, do make -C mdx build. This will transform all .ts files to .js files in the mdx/dist folder.
Then, do make -C mdx gen-mdx. This will emit the required .mdx files to website/docs and .json dictionary to website/plugins/proto-messages.
In website, install deps using yarn (if not installed previously)
yarn start, then go to http://localhost:3000/docs/booking-v1

Things that are still in doubt/tentative

How to present the "category" name? At the moment we are using the "directory to the package", but all slashes are replaced with dashes. For example, /booking/v1 are transformed to booking-v1.
Ideas regarding the TODOs, most importantly these ones (the proto messages plugin):

// TODO(imballinst): this plugin has 2 known weaknesses:
// 1. if there is a message with the same name with another "local message",
// then it will link to a wrong link.
// 2. there is no way yet to recognize common know messages (e.g. from Google protobuf).

Demo video
https://user-images.githubusercontent.com/7077157/151301603-58442091-3749-4ebf-b5dc-afa3c759885a.mov
Signed-off-by: Try Ajitiono<EMAIL_ADDRESS>

@dio should I also add the commands to generate the MDX to the GitHub actions in this PR?

How to present the "category" name? At the moment we are using the "directory to the package", but all slashes are replaced with dashes. For example, /booking/v1 are transformed to booking-v1.

This should follow the package name,
package booking.v1;

How to present the "category" name? At the moment we are using the "directory to the package", but all slashes are replaced with dashes. For example, /booking/v1 are transformed to booking-v1.

This should follow the package name,
package booking.v1;

Ah s

@dio should I also add the commands to generate the MDX to the GitHub actions in this PR?

Sure. Let me check on my PR first.

How to present the "category" name? At the moment we are using the "directory to the package", but all slashes are replaced with dashes. For example, /booking/v1 are transformed to booking-v1.

This should follow the package name,
package booking.v1;

OK! Let me see if that works (not sure if periods are allowed for .mdx files in Docusaurus). I think it should.

Yep, that booking.v1 works! I have updated the PR.

re: there is no way yet to recognize common know messages (e.g. from Google protobuf).
I think we need to recursively generate the deps.

re: there is no way yet to recognize common know messages (e.g. from Google protobuf).
I think we need to recursively generate the deps.

Right. I assume they are going to be generated in the .proto to .json pipeline? Or is it after the JSON is generated?

https://github.com/imballinst/protosaurus/pull/5


[Proposal] Update API template

As I've closing the additional API content gaps, there are a few scenarios I've encountered that the current API template does not account for, such as multiple examples or when additional complex descriptions are required such as the Rollover API. Therefore, I would like to propose the following changes to the API template:

Move the "Required permissions" section after Path and HTTP methods.
Simplify the default table settings by removing "data" from "data type". This is also more accurate since the type technically isn't "data" every time. Instead, the "type" can indicate a style or tweak to an operation, such as a Boolean.
Change "Request fields" to "Request body options". Request body options is more in line with the OpenAPI standard and further distinguishes these options from path and query parameters. For more information, see Describing Request Body.
Change "Response fields" to "Response body options".
Change "Example requests" and "Example responses" from H4 to H2 headers. This makes the examples more accessible and even with the rest of the template sections, and allows for the addition of subheadings in cases where an API contains multiple examples.
Add a note that accounts for examples which might require additional explanation.

Version
All.
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Overall, I don't see much value in doing this. This will require changing many files and is clear as is.

* Move the "Required permissions" section after Path and HTTP methods.

Don't particularly have an opinion on this one but I think it breaks the flow when this is in the middle.

* Simplify the default table settings by removing "data" from "data type". This is also more accurate since the type technically isn't "data" every time. Instead, the "type" can indicate a style or tweak to an operation, such as a Boolean.

Data type is a standard CS concept. Boolean is a data type https://learn.microsoft.com/en-us/office/vba/language/reference/user-interface-help/boolean-data-type.

* Change "Request fields" to "Request body options". Request body options is more in line with the OpenAPI standard and further distinguishes these options from path and query parameters. For more information, see [Describing Request Body](https://swagger.io/docs/specification/describing-request-body/).

"Options" is not standard language. Maybe, to clarify further, we can name this "Request body fields".

* Change "Response fields" to "Response body options".

Options imply the ability to change. There are no options that users can change in the response. The response contains the fields that come from the server.

* Change "Example requests" and "Example responses" from H4 to H2 headers. This makes the examples more accessible and even with the rest of the template sections, and allows for the addition of subheadings in cases where an API contains multiple examples.

* Add a note that accounts for examples which might require additional explanation.

We already have some pages that have multiple examples. For example, https://opensearch.org/docs/latest/api-reference/index-apis/force-merge/. We normally clarify the example type in the heading like "Example request: Force merge multiple indexes". These are self-explanatory, I think. Changing from H4 to H2 will make them visible in the right navigation, which is not ideal, given that if you clarify the example type within the header, the header becomes long.

@kolchfa-aws:
As a general note, most of the APIs on our site do not use the template. Here are some examples:

https://opensearch.org/docs/latest/api-reference/cluster-api/cluster-awareness/
https://opensearch.org/docs/latest/api-reference/cluster-api/cluster-settings/
https://opensearch.org/docs/latest/api-reference/search/
https://opensearch.org/docs/latest/api-reference/security-apis/
https://opensearch.org/docs/latest/api-reference/tasks/

Discussing this while the majority of the API content gaps I'm closing are still in review makes sense to me. Whether we change the template or not, we'll still have to go through and standardize to the template across the board.
Responding to your other comments:

"Options" is not standard language. There is no mention of the word "options" at the provided link. Maybe, to clarify further, we can name this "Request body fields".
That's fine by me.

Options imply the ability to change. There are no options that users can change in the response. The response contains the fields that come from the server.
Noted, does "Response body fields?" work for you?

Changing from H4 to H2 will make them visible in the right navigation, which is not ideal, given that if you clarify the example type within the header, the header becomes long.
This is the change I feel most passionately about. Its a bad user experience to bury the examples/example responses under a header that's inaccessible from the right nav. For an example of this, see the Force Merge page. Not only does a header for the example requests not exist, but I have to scroll all the way down to see a copyable example.
Having the examples directly accessible in the right navigation allows me to use the reference how I see fit. Instead of scrolling, I can click on the example that most pertains to me from the right nav and copy it immediately, like on the https://opensearch.org/docs/latest/api-reference/render-template/ page.
Furthermore, the example request and example response should have a clearer delineation between the two. Using Force Merge again, the response blends in with the examples, so it's not immediately clear that I'm looking at a Response Body visually.
As far as the header length is concerned, we shouldn't be making headers that are sentence-length anyways, even as H4-level headers. Giving both the Example request and Example response an H2 Header removes the need to prepend the H4 header with "Example response:" greatly reducing the length of the header to begin with.
There are multiple ways I'm okay changing this though:

The currently proposed method. See Render template
Have ##Examples be an H2 Header with "Requests" and "Responses" as H3s. If a request has multiple examples, you could use the H4 Headers, which would make them inaccesbile from the right nav. See the Multi-search API.

Thoughts? Both of those solutions solve the usability issue I described.

@Naarcha-AWS "Response body fields" works for me and matches "Request body fields". I'm also fine with the example you gave in the Render Template API. Less of a fan of the Multi-search API. I like "Example request" (singular) and "Example response" and the various types within the "Example request". This separates them a little more. Note that implementing this for all API pages is not a simple find/replace and is best done with a regex and a script.

BTW, this probably should have been an issue and not a PR 😄

@kolchfa-aws: I implemented the changes we agreed on. Let me know if there's anything else you would like to adjust or discuss.

Also, I see you switched the "Example response" and "Response fields" sections. I think this is worse than the current order because when users see an example request, they expect that the example response is right after. Then they can explore the response fields in the "Response fields" section.

Also, I see you switched the "Example response" and "Response fields" sections. I think this is worse than the current order because when users see an example request, they expect that the example response is right after. Then they can explore the response fields in the "Response fields" section.

I don't personally think it makes much of a difference, although I find it a little odd to see the response fields after as opposed to before. That being said, ok switching this back.

@kolchfa-aws: Fixed the order and added back Data Type, per your request. Once you sign off, I can go ahead and make sure the pages follow the template.

If there are multiple example requests, there should be an intro sentence before the first h3 to avoid stacked headings. Do you want to provide that intro sentence so it's standardized? I think we should change all API files to follow the new template in this PR to ensure consistency.

If there are multiple example requests, there should be an intro sentence before the first h3 to avoid stacked headings. Do you want to provide that intro sentence so it's standardized? I think we should change all API files to follow the new template in this PR to ensure consistency.

Is it worth doing now, or should we wait until after we have full coverage? I'm in favor of waiting until we have full coverage, unless the changes are minimal.

I would just change the heading level 4 in Example request/Example response headings to heading level 2. The other changes provide minimal value and require more work. Just changing a heading level is trivial.

If there are multiple example requests, there should be an intro sentence before the first h3 to avoid stacked headings. Do you want to provide that intro sentence so it's standardized? I think we should change all API files to follow the new template in this PR to ensure consistency.

Something along the lines, "The following example request shows _____"?


Better CLI for Executioner

The executioner is designed to accept many useful options which can change how the executioner operates. Currently, calling npm start will only use the  default values for many options like executing one submission at a time and setting the tmp submission directory to tmp inside the executioner directory.
Having a means for which the executioner can be called with different command line arguments to set different options would allow for users to customise their executioner experience to their needs. Additionally, different 'presets' could also be defined in the package run scripts to run the executioner with different sets of predefined arguments.

Is this really needed? Presets might be useful but for further customisation they can always just modify the source code.

True, but at the very least, allowing for specifying options like how many submissions to execute simultaneously (e.g how many cpu cores someone has) is useful.


Feature | Signup/Login Page

Implement the Sign up and Login page which will live under /.

[ ] Port Button Component
[x] Implement Signup Form
[x] Implement Signup Form with Submit Alert

@dararod I've implemented the Login with the same styles that we used for https://github.com/dararod/matefeed on Input component.

I leave the Signup to you, you must use the same component with a "toggle" button to switch from Login form to Signup form.

Please, also consider porting the Button component from ReactJS to Svelte as well. https://github.com/dararod/matefeed/tree/main/src/client/components/Button.
If you find yourself in trouble with Tailwind feel free to use a <style> tag to define the classes and then we can migrate them together to TailwindCSS.

I will close this and open issues for login and signup separately.


Can you release a version of CPU-only?

Hi, I'm trying to do something on my mac and it doesn't have any GPUs.
Could you please release a version that only to use the CPU?
Thank you so much!

The cpu version is not optimized at all and thus very slow.
You don't need pynvrtc and cupy when you run on cpu.

Thank you!


yq-go: 4.4.1 -> 4.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mikefarah/yq/releases.
meta.description for yq-go is: "Portable command-line YAML processor"
meta.homepage for yq-go is: "https://mikefarah.gitbook.io/yq/"
meta.changelog for yq-go is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 4.5.0 with grep in /nix/store/6iy8bjbicja9x2hwfsm71dza5ccva8v9-yq-go-4.5.0

directory tree listing: https://gist.github.com/2e50a0dd110c4ff045a00cafe19143cb

du listing: https://gist.github.com/5ac003d529133aaa55dad033c4ef0de6

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
yq-go

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6iy8bjbicja9x2hwfsm71dza5ccva8v9-yq-go-4.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A yq-go https://github.com/r-ryantm/nixpkgs/archive/2e430e09193380fb676a50f19492e7e97420da59.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6iy8bjbicja9x2hwfsm71dza5ccva8v9-yq-go-4.5.0
ls -la /nix/store/6iy8bjbicja9x2hwfsm71dza5ccva8v9-yq-go-4.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

yq-go

Maintainer pings
cc @nlewo @kalbasit for testing.

Result of nixpkgs-review pr 112566 run on x86_64-linux 1

1 package built:

yq-go


Explanation, why the keys @/# and </> are sometimes inverted on Mac.

Explanation, why the keys @/# and </> are sometimes inverted on Mac.

There are exists at least two physical keyboard types, US style ANSI without extra key between left Shift and Z and ISO with such extra key.

Long time ago Apple assigned different scancodes to some keys for ANSI and ISO Apple Desktop Bus (ADB) keyboards, effectively moving key with ADB scancode 32 from the location below Esc on ANSI keyboards to the location near left Shift on ISO keyboards, and assigning new scancode 0A to the key below Esc on ISO keyboard. It was done in hardware, by physically rerouting wires, so for example symbol "~" was always assigned by US keyboard layout to scancode 32, and was located below Esc for ANSI and near the Shift for ISO ADB keyboards. Other languages assigned other symbols to the key with scancode 32, physical location of those symbols moved between ANSI and ISO ADB keyboards the same way.

For the backward compatibility purposes ADB scancodes are used even on modern versions of macOS, with PS/2, USB or Bluetooth keyboard drivers translating native scancodes to ADB scancodes very early. Behavior of "moving" key with ADB scancode 32 is emulated inside driver if macOS autodetects or if user specified that ISO style keyboard is in use.

Most of VM software were written by US programmers that are not aware about this "jumping" key 32, but Parallels Desktop developers were aware, and compensated "jumping" key 32 so that key under the Esc has stable IBM Set2 scancode inside VM no matter was it ANSI or ISO keyboard from macOS host point of view.

Therefore, having "alternative" keyboard layout with swapped keys with ADB scancodes 32 and 0F or equivalently IBM scancodes 29 and 56 is useful not only on VmWare, but even on Parallels Desktop, especially for situations when Windows keyboard layout created from European macOS keyboard layout is used on Mac with ANSI keyboard.

Right now I have a problem with macOS PL keyboard layout assigning "~" to ADB key 32 that should have been near the Shift as Polish language usually uses ISO style keyboards. Parallels Desktop "mirror" keyboard layout assigned "~" to VK_OEM_102 that is assigned to IBM scancode 56 physically absent on my MacBook with ANSI style keyboard.

Thanks @eugenegff for the explanations.
I directly jumped from my Apple II in the early 80's to an iMac in 2015. I the meantime, I only used various Unix workstations and Windows PC. This is why I missed all the intermediate story.

@eugenegff, I have added a reference to your explanation in the README file.


devbuild_ofp_odp_dpdk takes wrong version of odp-dpdk

I took odp-dpdk as devbuild_ofp_odp_dpdk.sh suggests:
git clone https://git.linaro.org/lng/odp-dpdk.git
pushd odp-dpdk
git checkout v<IP_ADDRESS>_DPDK_17.02

, then built libodp-dpdk.so.115.0.2
Later, when I attempt to build ofp, ./configure complains
Requested 'libodp-dpdk >= <IP_ADDRESS>' but version of libodp-dpdk is <IP_ADDRESS>

I therefore suggest that git checkout above should be changed to something different, like
git checkout 3f2f63a3430c932cf65795b8e15a1c4ba72a199c

I've recently posted a patch, which should fix this.
https://list.openfastpath.org/pipermail/openfastpath/2018-October/003348.html

Thanks for help. ofp compiled. I had to put ODP_CFLAGS= and ODP_LIBS= before ofp configure.
I think that in your version of devbuild_ofp_odp_dpdk.sh line
export CONFIGURE_FLAGS="--enable-shared=yes --enable-helper-linux"

does nothing and must be deleted.


Creating a web based editor specifically for 'Taipy'

Description
This is a feature request for creating a web based editor specifically designed for Taipy. As of now, if we want to use Taipy, then we've to install it and then do our work. But, by creating a web based editor, a user can create some projects(just for testing) very easily without having the need to install it.
For example:

If I'm a new user and want to try Taipy for the first time, then I've to install Taipy as a pip file and start learning about it. But, with the web editor, I can straight away start editing some basic files like creating buttons, dialogs etc.
If, suppose a user is creating a project in Taipy and the user gets stuck somewhere, and wants to check if by adding a particular piece of code, will the project work or not, but the user wants to do this on a different file/dir, then the user has to create a new file/dir and then do the same. But, by the web editor, the user can easily test the code and after closing the browser, the previously created file by the user will be lost i.e. in the web based editor, it'll be like a temporary file, just for testing, by the user.

Solution Proposed
A web editor for Taipy can be created for users so that, they can try their piece of code easily, like a temporary file.
Impact of Solution
No response
Additional Context
I just found a web based editor kind of thing. The Kotlin language has a web editor and the same can be implemented for Taipy as well.

Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%.
[ ] Create related issue in taipy-doc for documentation and Release Notes.
[ ] Check if a new demo could be provided based on this, or if legacy demos could be benefit from it.
[ ] Ensure any change is well documented.

Code of Conduct

[X] I have checked the existing issues.
[X] I am willing to work on this issue (optional)

Hi! I'd love to take this up for hacktoberfest :)

@jrobinAV I have been trying out a number of approaches for this. What is the current stack of the taipy website?
I believe running a docker container that has taipy installed by default would be the best apporach.

@aazam-gh , here's the link for the taipy website's repo. The website is build in next-js.
On this page, maybe before the Optimized for Insights section, we can have a 'Why Taipy?' Section as in Kotlin's website and then a basic run command?
What do you think @jrobinAV @FabienLelaquais @FredLL-Avaiga ?

@aazam-gh , I believe your approach makes sense technically. Of course, we need more insights and deeper details to understand all the technical and architectural questions.
I am adding @RymMichaut and @nevo-david to this issue since they oversee the website development.

Wait wait...
This issue, that @yaten2302 has created, has a lot of value.
We've had this in mind for years. And really, the hosting part of that is not the difficult part.
What we want to do is an equivalent of Codepen, tuned for Taipy.
So you would have a Python coding area (with edition facilities including code highlight), a 'page definition' area (not so clear since Taipy supports Markdown, raw HTML, and Python simultaneously), a rendering area (what the page looks like), and potentially a styling page to apply CSS rules for tuning.
Several problems show up immediately.
Hosting is certainly one of them since we need to provide a hosting environment with a Python interpreter up and running, ready to process concurrent environments (every running app).
But this edition section is a real problem as well.
Furthermore, this kind of online service will soon enough be very related to the Taipy Designer offering, which provides a WYSIWYG approach that is more than relevant for this proposal.
Short answer: we're on it. Hosting will definitively be an issue, but just not right now.

@FabienLelaquais , it's good to know that this issue useful for Taipy :)
BTW, I've a doubt, that are you folks working on this issue or like it needs to be started from scratch?
I was just asking this because, if there's some work required from my side in creating the playground or the web editor, then I would definitely like to work 👍

I have been looking into the website repo.
Since it's pure js, I tried to test with Monaco.
However the same issue drawback tends to occur because we'd want an isolated environment for installing pip.
I'd love to hear any suggestions too!

How about hosting taipy console/interpreter in taipy.github.io like linking the console in the website will that work ?

Isn't it possible to get taipy included in pyodide?
Coz, if it is; it would be a piece of cake to get this up and running
Otherwise, can't we compile the basic functionality in a javascript environment and upload it on a cdn; (ik the language isn't technically accurate, bear with me please 😢) just like streamlit did with their stlite.js thing
This accounts for the execution of the code
As for rendering it on the display, I guess the best bet would be to use an iframe

Some of the approach I'm thinking that could go along are:

Cloud-based Execution: To create separate Python environments for every user session, utilize a cloud platform such as AWS Lambda or Google Cloud Functions. Although it could necessitate a substantial infrastructure build, this could solve the hosting issue.
Investigate compiling a portion of Taipy's essential features for WebAssembly (WASM) and executing them straight in the browser. Although this method eliminates the need for a server-side Python interpreter, it may restrict the functionality that are accessible. One possible tool for this strategy is Pyodide, which was discussed in the comments.
Combining a limited server-side component for particular Taipy functions that are not transferable to WASM with a Monaco editor for Python code is known as a hybrid approach. This might provide a harmony between performance and usefulness.
Editor with Limited Functionality: Make a simple editor that concentrates on fundamental Taipy

On top of that if we want to use some additional libraries we can use Monaco as mentioned by @aazam-gh  as well in one of the conversations.
Kindly let me know what approach is aligning or there is some other proposed solution that you guys have in mind .

@preeti13456 These points are really nice!! I was also researching pyodide.

As for the first point, in which you suggested using cloud services like AWS, etc... this approach ig might not work for us? Because this has to be implemented by the Taipy team themselves and also ig these cloud services are not free? Some subscriptions need to be taken, ig, we're thinking of some solutions that are easily accessible.

I think the second point, which you told, should research that. According to me this I found the most promising solution!! Wdyk?

Actually, I wasn't able to understand the third point. Could you please elaborate on it a bit more?

@FabienLelaquais @FredLL-Avaiga

Hey I'm also looking more on the second solution but I needed to understand if the above plausible solutions we can use for certain functionalities

@FabienLelaquais @FredLL-Avaiga , could you also provide your thoughts regarding this 👀?


Add missing source line to 2 QuickStart samples

In 1 of the Quickstarts for Cognitive Services > Computer Vision, the final line of code:
plt.show()
appears to have been inadvertently omitted from both provided Python code samples.
The Quickstart is "Quickstart: Use a domain model using the REST API and Python in Computer Vision" at https://docs.microsoft.com/en-us/azure/cognitive-services/computer-vision/quickstarts/python-domain
This PR just adds this missing line of code to both code samples.

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


exec with a error message

It will be helpful if we can pass an argument to the exec "helper" for executing commands with a custom error message to be used in case of failure.

Hmm, maybe but this is easily done as try { exec {...} } catch { throw "My custom message" } }.
New features should add some more significant values, ideally.

Sure we can do that, but because exec doesn't have the error message param there is no benefit for us in using it when we want a custom error message and we just go with the basics:
& cmd
if() { throw "blah"}

which is simpler and more readable than try/exec/catch

which is simpler and more readable than try/exec/catch

Yes, this is also a good way and again a reason that the suggested feature is not that "must have".

In fact, one of the main purposes of exec (IMHO) is to make the error messages uniform. So custom messages reduce necessity of exec even further.

Then, what is custom message exactly? Literal text on errors? Or should it include the exit code or the command or both?
How do you see this?
What if others would see this differently?
(I am just thinking out loud)

Maybe I wasn't clear but I was not suggesting to replace existing default message; just to be able to add additional information - no matter what is that: just a string sounds fine to me.

Can you give an example command and the result, how see this?

Plenty of times we are just using exec, but also plenty of times we want to add additional informative messages in case of failure to be easier to identify what failed. At that moment it is just easier/nicer to move back to if()  which is annoying: some code is using exec, other code if().
I would think that an additional custom error message complements very naturally the current exec making it more useful.
exec {
&cmd ...
} -ErrorMessage 'Failed to execute blah ..... whatever string"
Result;
: Failed to execute blah ..... whatever string

@dsbenghe I work on this, do not worry. This week is busy (work on inherited custom headers and footers in IB).
Then I plan something like this:
function Invoke-BuildExec([Parameter(Mandatory=1)][scriptblock]$Command, [int[]]$ExitCode=0, [string]$ErrorMessage, [switch]$Echo) {
	${private:*c} = $Command
	${private:*x} = $ExitCode
	${private:*m} = $ErrorMessage
	${private:*e} = $Echo
	Remove-Variable Command, ExitCode, ErrorMessage, Echo
	if (${*e}) {
		Write-Build 3 (Show-BuildExec ${*c})
	}
	& ${*c}
	if (${*x} -notcontains $global:LastExitCode) {
		*Die "$(if (${*m}) {"${*m} "})Command exited with code $global:LastExitCode : ${*c}" 8
	}
}

Invoke-Build 5.7.2 - new parameter exec -ErrorMessage ...

thanks.


Refactor logging in parallel-install lib

Description
Changes proposed in this pull request:

remove old log function
introduce zap logger dependency
create logger factory function that should be used across the library
remove one global logger passed in Config to let every struct has it's own logger
add Verbose flag to Config to easy logger toggling
replace all Go SDK log calls with zap logger calls

Related issue(s)

Implements #169

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm not a big fan of such direct dependency to zap logger (imagine zap replaced with another logger), I would expect a tiny interface in logger.go and this interface used around our stuff

@strekm : Maybe worth to bring this topic up in the quality sig-group to come up with one logging abstractoin-layer used globally in Kyma which uses internally ZAP. Otherwise we have a decouple logging layer in Hydroform, another one in CLI etc. etc.

I'm not a big fan of such direct dependency to zap logger (imagine zap replaced with another logger), I would expect a tiny interface in logger.go and this interface used around our stuff

@strekm : Maybe worth to bring this topic up in the quality sig-group to come up with one logging abstractoin-layer used globally in Kyma which uses internally ZAP. Otherwise we have a decouple logging layer in Hydroform, another one in CLI etc. etc.

/test pre-master-hydroform


Prevent activation of hidden terminals

For #9053

Codecov Report

Merging #10048 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master   #10048      +/-   ##
==========================================
- Coverage   61.23%   61.21%   -0.02%
==========================================
  Files         564      564
  Lines       30192    30195       +3
  Branches     4567     4569       +2
==========================================
- Hits        18487    18485       -2
- Misses      10672    10676       +4
- Partials     1033     1034       +1

Impacted Files
Coverage Δ

src/client/common/constants.ts
100% <ø> (ø)
:arrow_up:

src/client/terminals/activation.ts
84.21% <100%> (ø)
:arrow_up:

...activation/terminalEnvironmentActivationService.ts
100% <100%> (ø)
:arrow_up:

src/client/common/utils/platform.ts
64.7% <0%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0%> (-0.73%)
:arrow_down:

...science-ui/interactive-common/latexManipulation.ts
92.59% <0%> (+0.59%)
: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 9bda1a9...eeafb65. Read the comment docs.


Doesn't work with .NETFramework 4.7.2

Anyway you can add support for .NETFramework 4.7.2

Agreed.  Puppeteer Sharp is Net Standard 2.0 compatible, this is only NetCoreApp V3.1.

You right, I will change the target framework to Net Standard 2.0 this week.

Migrated to net standard 2.0 in version 1.2.0.

Migrated to net standard 2.0 in version 1.2.0.


Typo in class name

https://github.com/ntegral/nestjs-sentry/blob/a90b33d416254b1a1d5d5d4dfb18f03d90683b0d/lib/graphql.interceptor.ts#L19

This was corrected in the latest version update


Board Review: Azure Communication Services (SPOOL) - Auth Custom Teams Endpoint (Java, .NET, JS & Python)

Service team responsible for the client library: ACS Auth
Link to documentation describing the service:

Build a custom Teams endpoint

Quickstart: Set up and manage Teams access tokens (currently Private Preview) + PR for Public Preview

Contact emails:

PM: Tomas Chladek
EM: Sofia Rico Sanchez
Dev Lead: Jiri Sofka
SDKs main point of contact: Petr Svihlik

Name of the client library: Azure.Communication.Identity
Languages for this review: C#, JS/TS, Java
Link to the service REST APIs: Swagger (related PR)
API view artifacts

.NET

Private Preview API + Public Preview diff, rename to ExchangeTeamsUserAadToken, remove private preview version

JS/TS

Private Preview API + Public Preview diff, rename to exchangeTeamsUserAadToken

Java

rename to exchangeTeamsUserAadToken

Python

Champion scenarios:

The main goal of this feature is to allow developers who use ACS (directly or via SDKs) to build and integrate a custom user interface for calling functionality with Microsoft 365 Teams identities.
A typical scenario is building an attendant console (e.g. for receptionists to be able to accept incoming calls and redirect them to the right person). All scenarios are described in the business specification
Developers will use the new API to exchange AAD Access tokens (of AAD users with a Teams license) for Skypetokens. These Skypetokens can then be used to call ACS APIs directly or via SDKs. An example for TS:

The changes we’re making for Public Preview are mostly driven by the need of enabling consumption-based billing for scenarios that originate in apps built on top of ACS SDKs. Public preview doc

Timeline:

We are targeting the 31st of October with the SDKs
We are targeting December 2021 with the Public Preview of the feature as a whole

All four API Views were approved
we also had a follow-up discussion on the overall architecture of the feature and there are no unanswered questions left

--> closing


Rename methods and tweak API

Renames answer -> step_through
Renames Agent().invoke -> respond
Improve typing (messages: list)
Use only step.stream in step_through, and interface.stream in respond
Wrap output from step_through in AgentStepResults parameterized
Migrate agent chain tuples into AgentChainLink parameterized
Make LLM generate a short title for steps (I was confused why the LLM was doing consecutive SQLAgent calls) and widen the default min_width
Prevent plan step from flashing (due to empty string replace=True)

Looking good, but thinking about it again I'm not sure I love step_through and I'm also wondering if we actually need both methods or should simplify it to one method with an argument like render_output/render_final.

AgentStepResults did seem superfluous besides making the return type the same so I like that idea of merging those two methods

Maybe render_output can be controlled by the LLM too, e.g. prompt
Show me the table and the plot of the data

Okay, having the LLM decide on whether to render intermediate output works.

Table + Chat example


Add Thrift example

Motivation:
A Thrift example with armeria-thrift* is not offered officially.
Modifications:

Add Thrift example

Result:
Close #2978

.gitkeep could be removed? Or is it intentional?

Other examples have .gitkeep for empty resources folder. So I added it intentionally.


Script workflow issue

The process described in the Powershell script requires that I create a new resource group and then select an existing key vault within that group. That makes little sense - this script should instead either create the key vault within the new resource group or retrieve an existing resource group and the existing key vault within it, but the current approach doesn't make sense.

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

ID: dc8f7af4-e186-8d96-588d-5019de461b04
Version Independent ID: 1bd04124-6eac-c027-d1bf-f2c4907a7456
Content: Roll over an Azure Service Fabric cluster certificate
Content Source: articles/service-fabric/service-fabric-cluster-rollover-cert-cn.md
Service: service-fabric
GitHub Login: @athinanthny
Microsoft Alias: atsenthi

We had similar feedback before
#22605
And you can use the same keyvault if you like. There is nothing stopping you and I have confirmed this works. That being said, I will assign this to the content authors to review and see if they want to update this sample to work in the manner you are describing.

We have discussed this item and since the script is mainly used for non-production clusters and to help new users test rolling over certs we have decided to keep the doc as is.
However your comment will remain on this doc so if others feel the same way we can always come back and revisit or work on an additional doc.


Token contract is empty

Token contract source code is empty: https://github.com/oraclesorg/treasury/blob/master/contracts/TestToken.sol.
Let's create extension of mintable token with tokenDepositEvent  at transfer method.

Why mintable? Mintable or not does not affect on transfer method. I suggest just StandardToken.

@vbaranov we will create all tokens (252,460,800) on the right side before the token sale start. After crowd sale ends we will send exact amount of sold tokens in coins from multisig to the treasury. Buyers will exchange tokens to coins. Unsold tokens will be on the contract of the right side of the bridge.
I don't understand either why do we need mintable token here.

Maybe, it's my misunderstanding. Let me explain.
I make tests for bridge this way:

I create mintable token
mint hardcap of crowdsale to master of ceremony address
join mintable token to the right side of the bridge
tokens are transfered to user address from master of ceremony during buying

How to fill master of ceremony balance without minting?

why do we need to mint token? we can specify the number of tokens and owner (master of ceremony) as a const in StandardToken, right?

How to fill master of ceremony balance without minting?

Just put desired number of tokens into balances[msg.sender] in the Token constructor. Like that done in TestToken: https://github.com/oraclesorg/treasury/blob/master/contracts/TestToken.sol#L12

Ok, I see. Thanks.


Add Sqlite to PHP base images

why? I'm not trying to block it, but I asked why you temporarily added it elsewhere when I didn't run into issues

In the context of Symfony, what some user do is to run tests with the sqlite database backend for Doctrine, so they don't need to deploy the actual database. I think it's a nice idea and this wasn't supported because of the missing driver

If they use migrations for data or fixtures that are using mysql features, that'll break, but ok as it it wont hurt if not


Add kubernetes audit log labels

Towards https://github.com/giantswarm/giantswarm/issues/28841
This PR adds the following labels to the kubernetes audit logs:

resource: Type of resource concenred by the audit log
namespace: Namespace of the resource being touched


Bot is inactive and won't respond

yes I have read the readme, and the issues already posted, followed them exactly, my bot will come online, but it won't respond to anything and gives me no errors.

Hey @Radix-Comet,
Thank you for letting me know. I haven't been quite working on this project and Discord bots for a while. I found the issue and it's due to Discord's regulations a.k.a. intents for bots. You have to enable the following setting in your bot's page in Developer Portal. Then, it might work. If not, I am going to release an update with bunch of fixes, upgrades and improvements which means you can clone the repo again for a fixed version. Stay tuned!

Closing this issue as it seems to be working fine.


[BUG] ClusterManager operations are not called with "task" param

Describe the bug
Recent changes on main (and backport of these changes on v2.2 branch) has a bug where corresponding method of clusterManagerOperation with task param is not called.
** Issue/Fix **
clusterManagerOperations with task param needs to call corresponding previous method with task param
protected void clusterManagerOperation(Task task, Request request, ClusterState state, ActionListener<Response> listener)
        throws Exception {
        masterOperation(task, request, state, listener);
    }

Ref: https://github.com/opensearch-project/OpenSearch/blob/2.x/server/src/main/java/org/opensearch/action/support/clustermanager/TransportClusterManagerNodeAction.java#L141-L144

@Rishikesh1159 - Could you take a look ?

Hi @saikaranam-amazon , I'm afraid this is not a bug caused by the inclusive terminology renaming.
This is the code in version 2.1 before the renaming.
https://github.com/opensearch-project/OpenSearch/blob/388c80ad94529b1d9aad0a735c4740dce2932a32/server/src/main/java/org/opensearch/action/support/clustermanager/TransportClusterManagerNodeAction.java#L122-L127
(https://github.com/opensearch-project/OpenSearch/blob/2.1.0/server/src/main/java/org/opensearch/action/support/clustermanager/TransportClusterManagerNodeAction.java#L122-L127)
The task parameter in method masterOperation(...) was not called by default, and the comment told to override the method if accessing task parameter is needed.

@tlfeng
CCR is using the TransportMasterNodeAction (and there are no other changes apart from the version bump to 2.2) and masterOperation (with task param) method is overriden to get the relevant task details.
Problem is, this method is never called evident from the below relevant stack trace as eventually all methods under  TransportClusterManagerNodeAction are wired to call masterOperation (without task params)
at org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction.clusterManagerOperation(TransportClusterManagerNodeAction.java:129)
        at org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction.clusterManagerOperation(TransportClusterManagerNodeAction.java:143)
        at org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction$AsyncSingleAction.lambda$doStart$3(TransportClusterManagerNodeAction.java:221)
        at org.opensearch.action.ActionRunnable$2.doRun(ActionRunnable.java:88)
        at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52)
        at org.opensearch.common.util.concurrent.OpenSearchExecutors$DirectExecutorService.execute(OpenSearchExecutors.java:301)
        at org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction$AsyncSingleAction.doStart(TransportClusterManagerNodeAction.java:221)
        at org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction.doExecute(TransportClusterManagerNodeAction.java:159)
        at org.opensearch.action.support.clustermanager.TransportClusterManagerNodeAction.doExecute(TransportClusterManagerNodeAction.java:74)
        at org.opensearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:204)
        at org.opensearch.action.support.TransportAction.execute(TransportAction.java:174)
        at org.opensearch.action.support.TransportAction.execute(TransportAction.java:102)
        at org.opensearch.client.node.NodeClient.executeLocally(NodeClient.java:110)
        at org.opensearch.client.node.NodeClient.doExecute(NodeClient.java:97)
        at org.opensearch.client.support.AbstractClient.execute(AbstractClient.java:423)
        at org.opensearch.replication.util.CoroutinesKt$suspendExecute$2.invokeSuspend(Coroutines.kt:80)
        at org.opensearch.replication.util.CoroutinesKt$suspendExecute$2.invoke(Coroutines.kt)
        at org.opensearch.replication.util.CoroutinesKt$suspendExecute$2.invoke(Coroutines.kt)
        at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:89)
        at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:165)
        at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
        at org.opensearch.replication.util.CoroutinesKt.suspendExecute(Coroutines.kt:79)
        at org.opensearch.replication.util.CoroutinesKt.suspendExecute$default(Coroutines.kt:75)

Thanks for pointing out this problem! 👍
I found that the cause is the method masterOperation(Task task, Request request, ClusterState state, ActionListener<Response> listener) is totally bypassed.
https://github.com/opensearch-project/OpenSearch/blob/01123f8fdadc2e953e5a92d7d0fb55bab939a28c/server/src/main/java/org/opensearch/action/support/clustermanager/TransportClusterManagerNodeAction.java#L221
The above line should be reverted to using masterOperation (with task param). I will make the code change for it.

Created PR https://github.com/opensearch-project/OpenSearch/pull/4103 to solve the problem. Thank you for reporting this problem.

Thanks @tlfeng

The fix is backported to 2.x and 2.2 branch by PR https://github.com/opensearch-project/OpenSearch/pull/4114 and https://github.com/opensearch-project/OpenSearch/pull/4115.


restart replaced with reload in service_spec.rb file

@jfryman related with pull request 702 comment from me. review ad confirm please.
https://github.com/jfryman/puppet-nginx/pull/702

@pallavjosh this PR is only updating the tests, you would also need to update the Puppet manifests themselves.
Also please be careful with your spelling, the command would be reload not relaod

@3flex Sorry for the typo, corrected. Though in this case manifest is already changed with pull request #702 #712 , test was unchanged. So changing test file only with this PR
If In case upstream was wrong still shooting error as execution of "/etc/init.d/nginx restart" command failed. That pointed out issue.

@jfryman Please review, merge and confirm on reload part. Thanks

@pallavjosh Thanks so much for the contribution! 🎩🙇🏽


[FR] - Webhook Notification Support On Completed Run

Provide an option to configure a webhook to post end of job summary results to

@Drazzilb08 any ideas on what content?
@austinwbest - any thoughts (content/format/python libraries?), if added will naturally request it for Notifiarr ;)

Similar to PMM finished notifications. It shows what all was added, removed, how long it ran, etc..
I can add support for this, no biggie. Whatever hooks are sent I can make a way to handle them

I like this idea. Can do much the same thing as PMM. Torrents removed. NoHL torrents set. Ect.

Would be nice if the payload follows the Apprise payload https://github.com/caronc/apprise-api#stateless-solution. Makes it easier for anyone using Apprise and docker.

 Can apprise even handle a full json payload of data or is it just a simple text & body thing like bazarr uses

According to the docs:
Payload Parameters
📌 urls: One or more URLs identifying where the notification should be sent to. If this field isn't specified then it automatically assumes the settings.APPRISE_STATELESS_URLS value or APPRISE_STATELESS_URLS environment variable.
📌 body: Your message body. This is a required field.
📌 title: Optionally define a title to go along with the body.
📌 type: Defines the message type you want to send as. The valid options are info, success, warning, and failure. If no type is specified then info is the default value used.
📌 format: Optionally identify the text format of the data you're feeding Apprise. The valid options are text, markdown, html. The default value if nothing is specified is text.

Guess quantity over quality wins that one. I would offer 2 options then, one for shit text services and json payloads for those who want notifications that look nice

Sure, I'll try to leave options open for the user to decide.

Sure, I'll try to leave options open for the user to decide.

Quit taking about it and get on it! I'm over here waiting on you to send a payload 🤣

I've been busy with work 😅 maybe I'll have more time next week to start on it. I want to revamp the current code to use classes as well, I'm not too experienced in OOP so I want to use this opportunity to learn as well

@afraazali can you please test the apprise integration in the develop branch?

@afraazali can you please test the apprise integration in the develop branch? Instructions can be found on the wiki or checking out the new config.yml.sample

Will do it later tonight. I didn’t realize you were doing an apprise integration. I setup a custom fastapi app to handle webhooks in the mean time.

You will still need to set up Apprise-API separately in order to use this integration.

Yup! I have it all set up. I was using it with cross seed. It was working. I’ve disabled it now since this project does notifications as well. I’ll report my findings after a few runs.

@bobokun run_start and run_end are working as expected. I'll need to test for a little longer to see if the function webhooks work.
Thank you again for integrating with the apprise API.

@bobokun,
I'm getting an error with latest develop, https://0bin.net/paste/IOuiCQYb#JrcwKx0G7lT1W2wajUH3tRJCVNs0Ihi+K6lIwmTxfsl

Fixed in latest develop. Sorry I screwed up the config check, you'll need to redo your config for the webhooks section since that got erased.

Great! I'll continue to test. Will let you know if I come across any other issues. Thank you.

@bobokun
getting the same error in the “checking paused torrents” routine

hm I can't seem to replicate...it works fine for me. Can you paste your webhooks part in your config?

Working now. Thank you!


busywork: Performance timer overflows

Description

Sam Ding reported an issue showing that on longs runs, the busywork timer would overflow, and busywork would report negative throughput. This makes sense because the current timer is a microsecond timer, which will overflow (at 32 bits) after a couple thousand seconds. The timing methodology needs to be improved.

@bcbrock Thanks for submitting this issue. However, we have transitioned issue tracking to Jira https://jira.hyperledger.org/ Please transfer this issue there and then close this one. Thanks!

Transferred to Jira (as link)


Fixed bug in setting buildpack at end of list

/cc @freeformz

@jkutner Since these tests are stubbing put are these output assertions even testing anything?

@freeformz yea, the tests are missing a decent chunk of the flow. But in this case the test actually does capture the bug.

hunh. Well then :+1: then.


Support of sessions

What steps will reproduce the problem?
1. Open otroslogviewer
2. Select some log-files to view or tail
3. Close otroslogviewer
4. Re-Open otroslogviewer
5. I have to open all log-files again

What is the expected output? What do you see instead?
Either the logviewer shall save a "session-state" and try to re-open all
logfiles on re-opening the application or there should be a possibility
to explicit save the "session-state" (all open files, parsers etc).

What version of the product are you using? On what operating system?
2013-01-24 on Windows

Please provide any additional information below.
For example "LogExpert" re-opens all files from a previous session.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 17 Jul 2013 at 1:33

It would be great to have that option. Unfortunately currently after computer restart I have to spend some time to load all sessions and change the session names because the names of tabs have names likes 'Multiple logs' not the session name.

Issue is already implemented in 1.4.6

@otrebski are you sure that was implemented? Every time when I open the tool I have to manually load the sessions (the previous sessions/files are not opened automatically). Version which I'm using 1.4.6 on Windows 10.


Human bytes not displaying size correctly

Seems to be fixed when changing bytesToHuman() s variable from 0 to 1.
Tested with 2gb data. Displayed that 2MiB was cleaned, while it should be 2GiB.

As always.. Feel free to open a PR :)

See: https://github.com/fwartner/mac-cleanup/pull/78
:)

Merged. :)


ixa2.si.ehu.es is down

The webpage that hosts the different models is not reachable anymore.
Can you please upload the resources to a different site?

Wrong repository. Closing down and posting it in the proper one.


Support building w/o Ninja for cross-compile targets

I need to build a Python Extension for an OS that requires compilation with Xcode (cross compile, build on MacOS).
cmake-build-extension hard-codes the use of Ninja.
No issue having Ninja installed but it can't be used to build the project.
w/o the patch, cmake is called with 2 -G flags, one for Ninja and one for XCode.
I suggest the patch below. Check if the user (in setup.py) has asked for build system.
File modified is build_extension.py, line 149.
Maybe it can be improved because it behaves differently if Ninja is explicitly requested.
        ext_dir = Path(self.get_ext_fullpath(ext.name)).parent.absolute()
        cmake_install_prefix = ext_dir / ext.install_prefix

        ##### patch start here
        # CMake configure arguments
        configure_args = [
            f"-DCMAKE_BUILD_TYPE={ext.cmake_build_type}",
            f"-DCMAKE_INSTALL_PREFIX:PATH={cmake_install_prefix}",
        ]

        # check the user has opted-in for a build system
        build_system_specified = bool([option for option in ext.cmake_configure_options if option.startswith('**-DCMAKE_GENERATOR=**')])

        # Default to Ninja if the user didn't explicitly request a build system
        if not build_system_specified:
            configure_args +=  [
            "-GNinja",
            # Fix #26: https://github.com/diegoferigo/cmake-build-extension/issues/26
            f"-DCMAKE_MAKE_PROGRAM={shutil.which('ninja')}",
        ]

Added patch file based on master/HEAD.
issue#52.patch


The struture of generator of ImageNet benchmark

Nice work! But i have some little question.
(1)Could you provide the structure details of generators on ImageNet and TinyImageNet benchmarks? i.e., F_\phi in Eq(7).
(2)Could you publish the code of ImageNet and TinyImageNet benchmarks?

@MasterLX I have cleaned this code up and am currently verifying it. As soon as verification is complete, I will push it.


Test project templates with release workflow

The release workflow test the packages by building the examples, but this doesn't cover the template packages.
We should test the project templates too with this workflow.

Closed by #3971


ARROW-528: [Python] Utilize improved Parquet writer C++ API, add write_metadata function, test _metadata files

+1 -- some other Parquet patches will be incoming


s/Cannont/Cannot/

I don't know if this is safe to change. I will leave that decision up to the reviewer.

Or maybe this wording change is better: https://github.com/samuelvanderwaal/metaboss/pull/235

Sugar does need an error refresh but will merge this fix, thanks!


Installation Issue #2

An error occurred while attempting to install niftyPET on an HPC. I've extracted what I think is the important part of the error message out. I don't understand what this means.
Is it attempting to prompt? Because a prompt did not appear at any point.
    i> conda environment found: nipet
    i> using this CUDA architecture(s): -gencode=arch=compute_35,code=compute_35;
    i> conda environment found: nipet
    Folder for hardware mu-mapsTraceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-Dedvau/nipet/setup.py", line 128, in <module>
        Cnt['HMUDIR'] = askdirectory(**prompt)
      File "/tmp/pip-install-Dedvau/nipet/setup.py", line 27, in askdirectory
        path = raw_input(title)
    EOFError: EOF when reading a line
    Cleaning up...

Any help will be greatly appreciated, thanks.

Hi Rory
Sorry for the late reply.  Which Python version are you using?  2 or 3?
Cheers,
Pawel

Not to worry, I actually sorted this issue by instead downloading the source code for NIPET and NIMPA seperately and running the relevant setup.py scripts.
However, this particular issue with the recommended installation method still exists. I was using Python 2.7 if that helps.

Also some other information that may be relevant.
Python 2.7 installed in an anaconda environment.
Attempting to install on an HPC running CentOS Linux release 7.6.1810

I have it working under Centos 7 and 8, so no problems there.
With the remote installation (no gui) it may be better to use Python 3.  If you can, try cloning it from github and then checking out branch dev2, which is version 2.0, and which soon will become the master branch for Python 3.
Let me know how it goes and if you can do it.
Cheers,
Pawel

I think the error (hanging during install) may be due to waiting for user input regarding where to find hardware mumaps etc. Probably a duplicate of #1. Also probably best to use the latest Python3 version which has this fixed.
Let us know if Python 3 (e.g. https://github.com/NiftyPET/NIPET#quick-install) doesn't work.


Compiler crashes when running on https://api.hackerone.com/v1/api-docs/v1/swagger.json

tried to run RESTler on https://api.hackerone.com/v1/api-docs/v1/swagger.json
RESTler compiler crashed with :
Unhandled exception. System.AggregateException: One or more errors occurred. (Could not resolve the path '#/components/schemas/automated_remediation_guidance'.)
---> System.InvalidOperationException: Could not resolve the path '#/components/schemas/automated_remediation_guidance'.

@stishkin This looks like a bug in the specification.  That path is not present in the specification, which causes the parsing exception.

@stishkin This looks like a bug in the specification.  That path is not present in the specification, which causes the parsing exception.


pass working folder into invoke-batchscript.

Approved with comments. These changes need to be tested. We don't want to ship broken tasks.


translations PR 20200608

Ideally this PR should be review by community members for each language.
If you as a core committer are requested a review, please confirm there are no changes that would cause build or unit test failures, and merge the PR.
Notes:

Further changes to translations should be made to the [Mattermost Translation Server(https://translate.mattermost.com/projects/mattermost). These will be included in next week's PR.
If you see an English translation instead of the desired language, then this PR was submitted before the translation was made on the [Mattermost Translation Server(https://translate.mattermost.com/projects/mattermost). New translations will be included in next week's PR.

@metanerd Tests are failing for this PR

/update-branch

Looks like the tests check the order of search results in ES and since the translations have changed for ES the order of the search results has changed... @enahum
Could you just modify lines 52-60 of admin_console_index.test.jsx to
        expect(idx.search('ldap')).toEqual([
            'environment/session_lengths',
            'authentication/mfa',
            'authentication/ldap',
            'authentication/saml',
            'experimental/features',
            'authentication/email',
            'authentication/discover-ldap',
            'authentication/guest_access',
        ]);

That should fix the build...

@fmunshi I can modify it yes, but are other languages going to be affected? why is this causing an issue ?

@enahum looks like the spanish translations for session length changed to include the text LDAP
"admin.service.webSessionDaysDesc.extendLength": "El número de días desde la última vez que un usuario tuvo actividad en Mattermost para que la sesión del usuario creada por autenticación de correo electrónico y AD/LDAP expire. Luego de cambiar esta configuración, la nueva duración de la sesión tendrá efecto luego de la próxima vez que el usuario ingrese sus credenciales.",
So the test which checks search results for LDAP in spanish now returns session lengths as one of the first results - I opened a PR that ignores the order of languages other than english so we could merge that in or we could make the changes here, but then this test could still have the potential to fail again in the future if the spanish translations for any of these changes again.

@fmunshi I think the code should be fixed and it should be completely agnostic of the translation and this PR should be about translations only

@enahum @fmunshi If it's only related to the order of the strings, this shouldn't impact the user as it's just a stylistic error affecting code? If so, could we merge this to 5.24 and fix the ordering on master?

@jasonblais I think is only making the test to fail, so I do not see why it can’t be merged.. but if we can fix the tests that would be a good win.

/update-branch


[SMALLFIX]Change the Unit test method name follows the standard

This one is different, because there was a private method in DataNettyBufferTest.java named releaseBuffer(), so I first changed the private method name into releaseBufferHelper, then changes all fields which called this method, finally, I changed releaseBufferTest() to releaseBuffer().

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14108/
Test PASSed.


Building f5totec cannot link against libtacs

Attempting to build f5totec (e.g. cd extern/f5totec; make), the build seems to not be set up correctly to link the tacs library as shown by the following link error:
mpicxx f5totec.o /home/minion/local/tecio/install/libtecio*.a  -L/lib/ -Wl,-rpath,/lib -ltacs  /home/minion/local/metis/lib/libmetis.a -L/opt/intel/oneapi/mkl/2023.0.0/lib/intel64 -L/opt/intel/oneapi/mkl/2023.0.0/../../compiler/latest/linux/compiler/lib/intel64_lin -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -liomp5 -o f5totec
/usr/bin/ld: cannot find -ltacs
collect2: error: ld returned 1 exit status
make: *** [Makefile:9: f5totec] Error 1

I was able to fix by amending extern/f5totec/Makefile to include -L../../lib so that the linker would have visibility to the tacs library. I don't know if that is the preferred approach or if one should be building it differently.

This linking should be handled automatically (see here and here). Did you properly set the TACS_DIR variable in your Makefile.in?

Yes, I was creating Makefile.in programmatically and TACS_DIR was errantly getting evaluated to an empty string. Fixed the process and all is well. Thanks for the recommendation.


Subgraph with private state doesn't have a proper state at the last node

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangGraph/LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangGraph/LangChain rather than my code.
[X] I am sure this is better as an issue rather than a GitHub discussion, since this is a LangGraph bug and not a design question.

Example Code
class CodeFeedbackAgentPrivateState(BaseModel):
    interview_question: str = Field(default="")
    interview_solution: str = Field(default="")
    code_editor_state: str = Field(default="")

    debugging_result: str = Field(default="")
    assessment_result: str = Field(default="")

class DebuggingAgentPrivateState(BaseModel):
    interview_question: str = Field(default="")
    interview_solution: str = Field(default="")
    code_editor_state: str = Field(default="")

    debugging_record: list[str] = Field(default=[])

def initiate_private_state(state):
    print("initiate_private_state: \n", state.__annotations__)
    print("type: ", type(state))
    return {
        "interview_question": state.interview_question,
        "interview_solution": state.interview_solution,
        "code_editor_state": state.code_editor_state,
    }

def placeholder_node(state: DebuggingAgentPrivateState):
    return {
        "debugging_record": ["debugging_record testing"],
    }

def placeholder_node2(state: DebuggingAgentPrivateState):
    return {
        "debugging_result": "debugging_result testing",
    }

def last_node(state: CodeFeedbackAgentPrivateState):

    print("last_node CodeFeedbackAgentPrivateState debugging_result: \n", state.debugging_result)
    return {
        "debugging_result": state.debugging_result, #? BUG: this return is applied to OverallState instead of CodeFeedbackAgentPrivateState
    }

g = StateGraph(CodeFeedbackAgentPrivateState)
g.add_edge(START, n(initiate_private_state))

g.add_node(initiate_private_state)
g.add_edge(n(initiate_private_state), n(placeholder_node))

g.add_node(placeholder_node)
g.add_edge(n(placeholder_node), n(placeholder_node2))

g.add_node(placeholder_node2)
g.add_edge(n(placeholder_node2), n(last_node))

g.add_node(last_node)
g.add_edge(n(last_node), END)

debugging_agent_graph = g.compile()

Error Message and Stack Trace (if applicable)
No response
Description
I have double nested subgraphs.
Level 0: main_graph

uses OverAllState as StateGraph schema
no private states
includes a node of code_feedback_agent_graph

Level 1: code_feedback_agent_graph

uses OverAllState as StateGraph schema
uses CodeFeedbackAgentPrivateState as a private state
includes a node debugging_agent_graph
the private state is used when the debugging_agent_graph is triggered

level 2: debugging_agent_graph

uses CodeFeedbackAgentPrivateState as StateGraph schema
uses DebuggingAgentPrivateState as private state

At the last node of level 2 graph, I'm returning a dictionary that includes state variable of level 1 graph's private state because that is the state that is used when level 2 graph is triggered.
However, I'm getting an error saying the return should include OverAllState variable. Since level 2 graph is using CodeFeedbackAgentPrivateState as its StateGraph schema, the last node's return dict should update that instead of OverAllState. Shouldn't it be?
System Info
Version: 0.2.28

@minki-j the update from last_node is in fact applied to the state of the Level 1 graph, but since Level 1 graph is invoked inside the Level 0 graph, Level 1 graph as a whole still needs to respect the state of the parent (Level 0) graph. if you want to keep the state schemas independent, i.e. have no overlapping keys, you can just add input/output transformations before/after you invoke level 1 graph
see more here: https://langchain-ai.github.io/langgraph/concepts/low_level/#as-a-function
hope this helps!

@vbarda Thank you so much for your answer!! It makes sense. I'll follow your recommendation.
Again, I really really appreciate you guys work on LangGraph! Thank you so much!

Glad it helped! Will close this issue for now, but let me know if you run into any problems w/ subgraphs/state management


aa-kbc-params is not customized in agent-config.toml for libvirt provider in fedora

When creating libvirt PeerPod based on the fedora image on a s390x machine, which is built from mkosi.
The field "aa-kbc-params" in agent-config.toml under /run/peerpod was not customized correctly.
Which should be caused by the process-user-data. Logs looks like:
#journalctl -t process-user-data
Jun 06 00:11:23 podvm-busybox-b4e79cb5 process-user-data[676]: failed to send request: Get "http://<IP_ADDRESS>/metadata/instance/compute?api-version=2021-01-01": dial tcp <IP_ADDRESS>:80: connect: network
is unreachable
Jun 06 00:11:23 podvm-busybox-b4e79cb5 process-user-data[676]: failed to send request: Get "http://<IP_ADDRESS>/latest/dynamic/instance-identity/document": dial tcp <IP_ADDRESS>:80: connect: network is unre
achable
Jun 06 00:11:23 podvm-busybox-b4e79cb5 process-user-data[676]: Error: failed to create UserData provider: unsupported user data provider

After disable the "ExecStartPre" https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/podvm/files/etc/systemd/system/process-user-data.service#L12
Error like this:
# journalctl -t process-user-data
Jun 06 03:03:14 podvm-busybox-66cded21 process-user-data[675]: 2024/06/06 03:03:14 [agent/update] failed to read daemon config file: open /run/peerpod/daemon.json: no such file or directory
Jun 06 03:03:14 podvm-busybox-66cded21 process-user-data[675]: Error: failed to get daemon config from local file

The problem is on fedora, the failure in ExecStartPre in process-user-data causes ExecStart skipped because libvirt provider does not implement the provision API.
Option 1
I tried and broken it into 2 services. process-user-data-provision and process-user-data-update while process-user-data-update depends on cloud-final.service because libvirt and other providers like ibmcloud uses cloud-init to provision user-data.
It works for libvirt provider on ubuntu because:

ExecStartPre in process-user-data won't cause ExecStart skip on ubuntu
Which is /etc/agent-config.toml rather than /run/peerpod/ agent-config.toml on ubuntu

Fedora https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/podvm-mkosi/mkosi.skeleton/usr/lib/systemd/system/kata-agent.service.d/10-override.conf
Ubuntu https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/podvm/files/etc/systemd/system/kata-agent.service#L10

Option 2:
We can handle agent-config.toml just like cdh.toml here https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/pkg/adaptor/cloud/cloud.go#L258-L282 via cloudConfig rather than update it in process-user-data

Hey @huoqifeng - for the cdh configuration we also need aa_kbc_params set in /run/confidential-containers/cdh.toml (see https://github.com/confidential-containers/cloud-api-adaptor/pull/1748), do you know if that is working okay for libvirt in fedora too?

Hey @huoqifeng - for the cdh configuration we also need aa_kbc_params set in /run/confidential-containers/cdh.toml (see #1748), do you know if that is working okay for libvirt in fedora too?

CDH configure is OK on Fedora.

Right, maybe we should handle agent-config.toml similar as cdh.toml and remove the algorithm for its update in process-user-data.

@stevenhorsman @mkulke @bpradipt @liudalibj We can handle agent-config.toml just like cdh.toml here https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/pkg/adaptor/cloud/cloud.go#L258-L282 via cloudConfig rather than update it in process-user-data. wdyt?

@stevenhorsman @mkulke @bpradipt @liudalibj We can handle agent-config.toml just like cdh.toml here https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/pkg/adaptor/cloud/cloud.go#L258-L282 via cloudConfig rather than update it in process-user-data. wdyt?

in principle yes, if we assume the agent-config will be static and the same for all cases, we can generate it in code and don't attempt to update the file, that would be the cleaner approach.

it will also be useful if we want to provision a registry auth file via user-data, we could set the required kata-agent config option in the same file.


Appcenter --debug seems to write debug output to stdout

We're using appcenter to upload Proguard mappings after an APK file, and to make sure we have the right information we parse the json response that comes back from appcenter distribute command.
We hit some issues a while ago and added the --debug flag, however this seems to output the debug information to stdout, rather than to stderr, which makes it very difficult to use from a script.
Our script looks something like:
release_response=$(appcenter distribute release \
      --app ${application_id} \
      --file ${app_file} \
      --group ${deployment_group} \
      --silent \
      --output json
version_code=$(echo $release_response | jq -r '.version')
version_name=$(echo $release_response | jq -r '.shortVersion')

and when we run the above with --debug, the "release_response" variable gets setup with something like
Using appcenter-cli version: 2.7.3
logFilter, request: {
	  "rawResponse": false,
	  "queryString": {},
	  "url": "https://api.appcenter.ms/v0.1/......

Is there a workaround that allows us to get debugging information and the JSON response separately?

--app says it requires USER/APP_NAME does it also accept the App ID (Secret)?

--app says it requires USER/APP_NAME does it also accept the App ID (Secret)?

Closing as stale.


Laryngitis { points: 3 }
Lamb { points: 1 }
Log { points: 9 }
a log?????

funny one that isnt it-- I am trying to work myway through the logic of the code to figure out how it gets to this decision so i can possibly submit a correction.
be useful to have  some verbose output log file option to see how it arrives at a score


PRAGMA journal_mode=WAL;

Should we add PRAGMA journal_mode=WAL; to the database schema

Only needed for parallel read+write, see this article:
https://www.skoumal.com/en/parallel-read-and-write-in-sqlite/
Does not hurt other features though, so can be enabled by default.


Unable to select video on Android

Explain what you did, what you expected to happen, and what actually happens.
How to repeat issue and example
Your explanation here and source code or link
Unable to select video on Android
Solution
What needs to be done to address this issue? Ideally, provide a pull request with a fix.
ImagePicker.launchImageLibrary({
mediaType: 'video'
},()=>{}
})
Additional Information

React Native version: 0.55.4
Platform: Android
Development Operating System: MacOS
Dev tools: Android5.1 魅族M3

"react-native-image-picker": "0.28.1",


Added ability to get clean phrase from time->humanize()

Description
Added parameter to humanize($rawPhrase = false) to get clean phrase.
rawPhrase = false : 20 hours ago | in 20 hours
rawPhrase = true  : 20 hours
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

This is an enhancement, and should go to 4.3 branch, not develop.
See https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/workflow.md#if-you-sent-to-the-wrong-branch

This is how Carbon does it. Chronos doesn't seem to have a "raw value" option. Normally I'd prefer a new method rather than a flag that changes behavior, like humanInterval() but I could go either way on this. If we do stick with the parameter I'd prefer to see it as an additive description:

rawPhrase = false = takes away content

Versus:

useQualifier = true = adds content

There is no test code. Please write test code.
See https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/pull_request.md#unit-testing
And please add to changelog:
https://github.com/codeigniter4/CodeIgniter4/blob/4.3/user_guide_src/source/changelogs/v4.3.0.rst#libraries

I also prefer a new method rather than a flag that changes behavior.

No feedback. Closing.
If you still find this change useful, please submit another PR following the guidelines.
https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/pull_request.md
Thank you.


Change Default Year

Closes #438

@MattHJensen @talumbau is there a need to change the tests to use 2017 as the start year?

confirmed that this works locally with START_YEAR environment variable. Also I like the addition of /apps/constants.py. Merging and then will update ospc.org.


antd-admin示例的登录账号和密码是多少，求告知!

Username:guest Password: guest

Username:admin Password: admin
Username:guest Password: guest

Why not add it to the readme file?

@ramen-curator done


Python 3.6: [WinError 10054] OR sslv3 alert bad record mac

Hello,
I'm using python 3.6 and I'm trying to connect to 2.x socket. The lib is socketIO-client-nexus 0.7.5. Here's the code:
def on_response(*args):
    print('response: ', args)

with SocketIO('https://streamer.cryptocompare.com', 443, LoggingNamespace) as socket:
    socket.on('on_response', on_response)
    socket.send("['0~Poloniex~BTC~USD']")
    socket.wait(seconds=10)

I managed to connect to this websocket on only one occassion and I got the expected response.
As soon as I quit the program and tried reconnecting later on - I encounter one of the following two scenarios:
First  - WinError 10054
> Traceback (most recent call last):
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\transports.py", line 164, in send_packet
    self._connection.send(packet)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_core.py", line 234, in send
    return self.send_frame(frame)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_core.py", line 259, in send_frame
    l = self._send(data)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_core.py", line 423, in _send
    return send(self.sock, data)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_socket.py", line 116, in send
    return sock.send(data)
  File "C:\Program Files\Python36\lib\ssl.py", line 935, in send
    return self._sslobj.write(data)
  File "C:\Program Files\Python36\lib\ssl.py", line 636, in write
    return self._sslobj.write(data)
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\__init__.py", line 28, in wrap
    return f(*args, **kw)
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\__init__.py", line 225, in _message
    transport.send_packet(engineIO_packet_type, engineIO_packet_data)
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\transports.py", line 168, in send_packet
    raise ConnectionError('send disconnected (%s)' % e)
socketIO_client_nexus.exceptions.ConnectionError: send disconnected ([WinError 10054] An existing connection was forcibly closed by the remote host)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\transports.py", line 164, in send_packet
    self._connection.send(packet)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_core.py", line 234, in send
    return self.send_frame(frame)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_core.py", line 259, in send_frame
    l = self._send(data)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_core.py", line 423, in _send
    return send(self.sock, data)
  File "C:\Program Files\Python36\lib\site-packages\websocket\_socket.py", line 116, in send
    return sock.send(data)
  File "C:\Program Files\Python36\lib\ssl.py", line 935, in send
    return self._sslobj.write(data)
  File "C:\Program Files\Python36\lib\ssl.py", line 636, in write
    return self._sslobj.write(data)
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:/Users/[User]/PycharmProjects/[Project]/WebsocketConnection.py", line 26, in <module>
    socket.send("['0~Poloniex~BTC~USD']")
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\__init__.py", line 440, in send
    self.emit('message', *args, path=path)
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\__init__.py", line 433, in emit
    self._message(str(socketIO_packet_type) + socketIO_packet_data)
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\__init__.py", line 31, in wrap
    return f(*args, **kw)
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\__init__.py", line 225, in _message
    transport.send_packet(engineIO_packet_type, engineIO_packet_data)
  File "C:\Program Files\Python36\lib\site-packages\socketIO_client_nexus\transports.py", line 168, in send_packet
    raise ConnectionError('send disconnected (%s)' % e)
socketIO_client_nexus.exceptions.ConnectionError: send disconnected ([WinError 10054] An existing connection was forcibly closed by the remote host)

If I try relaunching the program however, it appears that I manage to connect, following warning pops up only before the connection is closed:

WARNING:socketIO-client:streamer.cryptocompare.com:443/socket.io [connection error] recv disconnected by SSL ([SSL: SSLV3_ALERT_BAD_RECORD_MAC] sslv3 alert bad record mac (_ssl.c:2171))

Am I doing something wrong?

Hey guys, any updates on this issue? My colleague experiences similar problem.

@rassokhin-s I don't think they made some progress about it otherwise I guess the issue would have been updated. I abandonded the python library and ended up creating a small program in node.js to exploit the API...

@kotvrt thanks for reply!


API tests further improvements.

Follow up on https://github.com/aws-amplify/amplify-backend/issues/655 where initial version was developed.
TODO:

Further expansion to cover:

inheritance
exported consts
See TODOs in https://github.com/aws-amplify/amplify-backend/blob/main/scripts/components/api-changes-validator/api_usage_statements_generators.ts

Integration with semver diffs/changeset. This check can be accompanied by semver diff check. I.e. a version bump coming from changeset can be validated against API diff detected (e.g. no API change - patch, non-breaking API change - minor, breaking API change - major, detection of no API change or intentional major version increment should skip this change for given package).
Mechanism to suppress the check for intentional breaks (for now check will be optional).
Consider publishing api-changes-validator as npm package.

Class inheritance https://github.com/aws-amplify/amplify-backend/pull/876


Map.getStreetView does not return StreetViewPanorama

``The Map.getStreetView function does not return a StreetViewPanorama mock.
dist/index.js#310
        this.getStreetView = jest
            .fn()
            .mockImplementation(() => jest.fn());

This should be changed to return a StreetViewPanorama instead:
        this.getStreetView = jest
            .fn()
            .mockImplementation(() => new StreetViewPanorama());

Good catch. I think when the method was mocked initially, the mocked class for StreetViewPanorama did not exist yet, hence the wrong return value.