Language server fails with exception when ansible.ansibleLint.arguments is not set

Summary
I'm using ansiblels installed via https://github.com/williamboman/nvim-lsp-installer with https://github.com/neovim/nvim-lspconfig/ in neovim 0.6 (HEAD / nightly).
When I'm opening an ansible file, linting with ansible-lint is not working. The log file (see log output below) pointed me to this code: https://github.com/ansible/ansible-language-server/blob/30a3a89/src/services/ansibleLint.ts#L64-L69
The default configuration of nvim-lspconfig does not set ansible.ansibleLint.arguments which results in this code calling match on undefined in line 67. When I set ansible.ansibleLint.arguments to an empty string, everything works as expected.
coc-ansible seems to default this to an empty string. I'm not sure if this is a bug in ansible-language-server or the default configuration in nvim-lspconfig. If it is the latter I'll gladly open a PR there to fix this.
Extension version
latest nvim-lspconfig
VS Code version
using nvim-lspconfig with neovim 0.6 HEAD
Ansible Version
ansible [core 2.11.6]
  config file = /Users/strayer/dev/valheim-dedicated-server/ansible.cfg
  configured module search path = ['/Users/strayer/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/4.8.0/libexec/lib/python3.10/site-packages/ansible
  ansible collection location = /Users/strayer/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.10.0 (default, Oct 13 2021, 06:45:00) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
  jinja version = 3.0.2
  libyaml = True

OS / Environment
macOS Monterey 12.1 Beta (21C5039b), ansible-lint 5.2.1
Relevant log output
[START][2021-11-23 12:47:01] LSP logging initiated
[WARN][2021-11-23 12:47:01] ...lsp/handlers.lua:108	"The language server ansiblels triggers a registerCapability handler despite dynamicRegistration set to false. Report upstream, this warning is harmless"
[WARN][2021-11-23 12:47:01] ...lsp/handlers.lua:108	"The language server ansiblels triggers a registerCapability handler despite dynamicRegistration set to false. Report upstream, this warning is harmless"
[WARN][2021-11-23 12:47:01] ...lsp/handlers.lua:108	"The language server ansiblels triggers a registerCapability handler despite dynamicRegistration set to false. Report upstream, this warning is harmless"
[ERROR][2021-11-23 12:47:01] ...lsp/handlers.lua:403	"An error occurred in 'onDidOpen' handler: [TypeError] Cannot read properties of undefined (reading 'match')\nTypeError: Cannot read properties of undefined (reading 'match')\n    at AnsibleLint.<anonymous> (/Users/strayer/.local/share/nvim/lsp_servers/ansiblels/out/server/src/services/ansibleLint.js:59:73)\n    at Generator.next (<anonymous>)\n    at fulfilled (/Users/strayer/.local/share/nvim/lsp_servers/ansiblels/out/server/src/services/ansibleLint.js:5:58)"

I think it would be up to @yaegassy to review this one.

@strayer Adjust the settings on the nvim-lspconfig side. https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/ansiblels.lua#L8-L24

@strayer I made a PR that should address your problem but it would be really useful if you can describe exactly how can someone use our ALS with neovim, maybe we can add one additional GHA for testing integration with it?

@ssbarnea Thank you! I planned on doing exactly the same change later this evening, but you beat me to it :)
In which way should I describe the setup? It is rather complicated, as pretty much every customized neovim setup, but the basics are relatively simple. This problem should happen as soon as one is using the current neovim stable release with https://github.com/neovim/nvim-lspconfig.
With ansible-language-server and nvim-lspconfig installed the init.vim should really only need to have this to get the integration running:
lua << EOF
require'lspconfig'.ansiblels.setup{}
EOF

I'm not sure how to automate this using a Github action though. My knowledge about neovim internals is rather limited. As far as my experience with neovim goes there should be some way to test the language server with lua code.

You don't need GHA knowledge, we can help he. As long you can come-up with a script or step by step guide  with few test steps, we can take care of the rest. Stuff like `install editor, install plugin, execute this command".
Yep defaults should work better but I am sure that w/o some testing we will soon find something else breaking. The only way to ensure we keep it working is to have a level of tests on our CI.

Github Actions wouldn't be an issue. I'm really not competent enough with lua internals of neovim to get something like this going, sorry :( As far as I can see some kind of lua script would need to launch neovim with an example ansible playbook and expect specific linter messages via internal lua LSP APIs (at least to cover this issue). In case I find the time to get into the thick of this I'll gladly contribute, but I'd rather make clear that I probably won't be able to help with this.


MB-2438 Office app authorization

Description
This PR adds functionality to restrict components and redirect users in the office app based on their user role. For instance, if I log in as a TOO, I'm taken to the TOO queue and will not be able to access the PPM office queue.
Reviewer Notes
None of our existing office users have an explicit user role, so that presents us with the problem of not knowing where to redirect people in the system. This PR adds a migration to address that by assuming all existing office users in the system are "PPM office" users, and creates a corresponding users_roles association record for each user. We can manually add the TOO or TIO role to users in the admin app. Slack context.
Setup

make db_dev_e2e_populate
make server_run
make client_run
Try logging into the office app as each user type. You should be taken to the correct screen for each role and shouldn't be able to access the screens of another role. For example, if you log in as a new TOO user and attempt to visit officelocal:3000/queues/new, you'll be redirected back to the TOO app.
For users with multiple roles (most likely Truss folks), you'll see a "Change user role" link at the top left of your screen. From there, you can select the other roles that you have access to.

Code Review Verification Steps

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Warnings

:warning:

Please include the Jira ID at the start of the title with the format MB-123 or [MB-123]

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 82583d473be8f851fa3fac8254aecd33ad12ec8f

I was expecting the home page for each user role to still be “/“, redirecting on the home page has some weird impacts. That is, I was expecting the landing page to use authorization to render the appropriate controls, not redirect you to the appropriate page.

@tinyels I went with the redirect approach since I found myself trying to reconstruct the whole tree of components represented in Office/index.jsx inside PrivateRoute. I had a good pairing session with @suzubara and we discussed the trade-offs of each approach. The redirect approach was easier for me to wrap my head around, but the HOC that renders a component based on your role separate from the route may be doable. As I transition from TTV to A-team, Suz and I are going to pair on this work so that she can take over and hopefully introduce some better patterns.

There have been some substantive changes to how we're handling this under the hood, so I am re-requesting PR reviews! 🙏  Primary changes are showing each user role's "home" content at the root URL, and storing the currently selected role in Redux (for users with multiple roles).


Fix badges to match new org structure

I didn't update the references to the badges after the org changes which caused them to be stale. This fixes that.
Please note the AppVeyor URL didn't change because those aren't associated with the org but with the user owning the build.

:+1:


Netty should always provide a terminal event for WebSocket Handshake

I have a client implementation which uses SSL Handler with WebSocketClientProtocolHandshakeHandler. If SSL handshake fails for some reason, it leads to channel close which deactivates/deregisters the WebSocket handler. The client implementation has a WebSocket connection initialization logic that is performing a sync wait for either ClientHandshakeStateEvent.HANDSHAKE_TIMEOUT or ClientHandshakeStateEvent.HANDSHAKE_COMPLETE.
Expected behavior
After handshake has been started i.e. ClientHandshakeStateEvent.HANDSHAKE_ISSUED has been triggered, one of either ClientHandshakeStateEvent.HANDSHAKE_TIMEOUT or ClientHandshakeStateEvent.HANDSHAKE_COMPLETE must always be triggered.
Actual behavior
In certain cases when the Channel is closed before the callback could be invoked neither of the above events are triggered. In such cases the sync wait on the application defined above waits indefinitely.
I can fix this situation on my application my interrupting the sync wait on channel closure, but I think it would be cleaner if my application could rely on Netty to always provide a terminal event for a handshake.
Steps to reproduce
Similar to the unit test added in https://github.com/netty/netty/pull/10510

Add a handler in the chain that waits on a terminal ClientHandshakeStateEvents to proceed ahead with the business logic. Currently, the two terminal events are: HANDSHAKE_COMPLETE and HANDSHAKE_TIMEOUT.
Start WebSocket handshake.
Assert HANDSHAKE_ISSUED is received.
Close the channel before the handshake can complete.
Observe that no terminal event reaches the client handler introduced in step 1.

Minimal yet complete reproducer code (or URL to code)
The test case would be similar to the one added in https://github.com/netty/netty/pull/10510
Netty version
4.1
Suggested improvement
Either of the two options below would work:
Option 1: Add a new event ClientHandshakeStateEvent.HANDSHAKE_FAILED which would be triggered if anything (including channel closure) goes wrong during the handshake.
Option 2: Provide public access to the handshakePromise in WebSocketClientProtocolHandshakeHandler.java which should be completed on ChannelInactive

This was fixed by #10510

@normanmaurer #10510 does not address the scenario described in the issue. That PR simply ensures that the resources (executor threads) and the scheduled timer is cleared if channel is closed.
This issue discusses a very different problem i.e. the handshake process does not provide a terminal event. I have provided two suggestions at the end of the description. I would be happy to implement once we could arrive at a conclusion about the preferred approach.
Please re-open this issue.


Error in recent react-native version

I recently updated to new react-native 0.46.1 and following bugs appear in this library.
It appears when I set isVisible state to true.

please fix this issue in npm module. Thank you.

Related to this react-native-modal issue.
I'll try to investigare asap.
Help on this would be apreciated.

Can you change your modal import to 'react-native-modalbox'? (link https://github.com/maxs15/react-native-modalbox)
I've been using react-native-modal but changed to this one and error is gone.
Also you can close modal touching the background which is useful.
I feel much comfortable using this and it also fixes the bug.
Hope you can change your library to this one!

@hyochan35 sorry but I won't change the modal component used for this module.
You can still contribute to the issue of react-native-modal though or, in the meanwhile, you can stay on the previous RN version :)
Also, are you on Expo?

Yes I am on Expo.
Sad to hear from you that you won't change the modal component.
Can I pull your source and fix your library to my own taste and use it for my project?
What I want from your library it to close the modal when tab on back without clicking on cancel button.

It's an Expo issue then, I'll investigate it soon (I never used Expo).
Yep, you can fork it as much as you want, of course!

Thanks. Glad to hear that. I will update your library to react-native-modalbox for my project.
Also checkout my starter project for React-Native if you don't like expo.
https://github.com/hyochan35/starter-rn.git

Hey @hyochan35, from my testing the issue seems to be related to the last Expo release.
Also, I opened an issue on the official Expo repo.

The issue has been fixed in the last Expo release (19.0.1)


Update xamarin.md

We're proposing this change to the docs because we recently had a hard time configuring the Xamarin.iOS build task to produce an .ipa package for CI/CD in Azure Pipelines. We had to troubleshoot a lot and we even had to perform the build using a regular bash task to finally find out that we were passing a wrong apple certificate. The Xamarin.iOS task never through an error but we noticed no .ipa file was being generated at all by carefully reviewing the folders of the agent, somehow a regular bash MSBuild command provided more information pointing we were missing signing identities for the app bundle id.
After understanding the issue we guessed it'd be a good idea to share this with Microsoft customers through this docs.
Hopefully, you'll find our contribution useful. Proposing this with @ManuelGalindo we're both Azure DevOps support engineers. Pending for corrections if needed we can provide a visual guide with screenshots for the classic pipeline tab.

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

@steved0x @madhurig could you take a look at this? :)


Missing feedback on invalid email input in the "Add Team Member" form.

The form currently lacks visual or error messages when the user inputs an invalid email address. While the email field is marked as required, it doesn't provide feedback for invalid inputs, like incorrect email format or missing fields.
Steps to Reproduce:

Open the form.
Leave the email field empty or enter an invalid email address.
Submit the form.

Expected Behavior: The form should display error messages indicating the email field is required or that the email format is invalid.
Suggested Fix: Implement form validation feedback for email input to improve the user experience. This can include showing error messages like "Please enter a valid email address" or "Email field cannot be empty

@Iyeba-Kallon kindly give directions on where the function lives, can't seem to find the addTeamMember function anywhere


Add support for lights and fix up wrong button action

In this PR:

Fix wrong button action for yeelink.switch.ylsw7 (BUTTON_2_DOUBLE -> BUTTON_3_DOUBLE)
Add support for mvs.light.wy0a01
Add support for lemesh.light.w00a02

Thanks!

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.6


Requesting: Alternative designs for items table

Problem to solve
Based on the level of data now available for items and after a discussion at design review (24 June), the current table design no longer feels fit for purpose, especially on mobile where a lot of scrolling is needed to find the 'request item' button, and for works that have a large number of items (e.g. The Lancet).
Objective:
Consider alternatives to the table design that can:

Make the data easy to scan and digest across different work types on desktop and mobile
Visually work well for the varying levels of data available across items

Zeplin links below for alternative design options.
Desktop:

Full-width table: https://zpl.io/VqzMPJ4
List style: https://zpl.io/VOL3qGr
Open shelves list: https://zpl.io/bLq3mAY
List style on archives: https://zpl.io/aMw38g3

Mobile designs

Version 1 (card style): https://zpl.io/VOL3qll
Alternative for the above: https://zpl.io/bLq3mZ6
Card style (no data labels): https://zpl.io/aBv39XQ
List style v1: https://zpl.io/bWG3Wl7
List style (no data labels): https://zpl.io/blOnvQe

The first bit of feedback from Gareth O, Alice and Jonathan - the list style feels like the right approach to move away from the table design.
Need to consider the pros and cons of showing or hiding the labels (location, status, access etc), but to start with they should be included.

@gestchild @davidpmccormick Zeplin links are on this ticket as well :)

Design review:

add item note under title
add access note
take out structured 'to' field and append to terms where appropriate


Simplify behavior of FieldResponse#getError to only return the first field error

While getErrors in FieldResponse simply returns all field errors, by contrast getError does a more exhaustive search that also includes global, request errors too, but only if the field is "failed" (i.e. has no value). So if the field has both a value and nested field errors, then getError would return null while getErrors would be non-empty.
We should align the two by making getError return the first field error. Separately, one still has the option to check if the field has a value or not, if the GraphQlResponse has global, request errors.

On second thought, the more logical thing is to deprecate getError() altogether.


Error: Not Found indicates that some expected artifacts are missing?

   Compiling state v0.5.3
    Finished release [optimized] target(s) in 7m 22s
    Bundling bibi-gpt_2.12.0_amd64.deb (/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/deb/bibi-gpt_2.12.0_amd64.deb)
    Bundling bibi-gpt_2.12.0_amd64.AppImage (/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage)
    Finished 2 bundles at:
        /home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/deb/bibi-gpt_2.12.0_amd64.deb
        /home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage

Expected artifacts paths:
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/deb/bibi-gpt_2.12.0_amd64.deb
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage.tar.gz
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage.tar.gz.sig
Found artifacts:
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/deb/bibi-gpt_2.12.0_amd64.deb
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage
Error: Not Found

According to the output, these two expected artifacts are not found:
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage.tar.gz
/home/runner/work/BibiGPT/BibiGPT/src-tauri/target/release/bundle/appimage/bibi-gpt_2.12.0_amd64.AppImage.tar.gz.sig

Is there any way to not handle these additional artifacts paths? I remember that the previous version of tauri-apps/tauri-action@dev still built successfully?

I think I should change the wording from "Expected" to "possible"?
What it means is that the action looks at these paths for files (so that you can compare it with the files you would expect).
Above the "Expected paths" line is the actual Tauri output which also only lists 2 bundles which means that it was correct that the action detected 2 out of the 4 possible(expected) paths.
By the way the 2 "missing" artifacts will only be created if you enabled and configured Tauri's updater.
In other words, the action is running fine and your app was built correctly :)

cool, I see. thanks a lot, so my build is successful, only because I configured TAURI_PRIVATE_KEY & TAURI_KEY_PASSWORD, thus the 2 "missing" artifacts path, is my understanding right?

The action always checks for the updater artifacts, it doesn't actually check if you configured the updater or not.

cool, thanks!


VirtualArray has correct record parameter

I don't understand the windows errors, is it using a different c++ standard?

The first error is
https://github.com/scikit-hep/awkward-1.0/blob/e4186d058e55f0b2bd5747eb1546e694e4258d21/src/libawkward/array/VirtualArray.cpp#L545
I would say that a not operator doesn't exist in C++, but maybe it does in some recent standard. (I don't know how the non-Windows builds passed.) Anyway, the standard is C++11. Negation is !.

It did, but what do you know, I found another case where the lack of a proper form for purely field slices in SliceGenerator is causing usability issues: passing a subarray to a numba function.
Given that this implementation is most of the way to a proper implementation of virtual getitem_field, maybe we should just finish it.

Okay, I'll leave this open. It won't be hard to merge with any upcoming changes.

I think this is done


Fix signature of using core.getIDToken

⬇

@kachick nice catch, thanks again!

Thank you for merging! 🙏


Break point is not work when query statement inside the partition

Description:
Break point can not put to the query when the query statment inside the partition.
1 @App:name("firstrule")
2 @App:description("Description of the plan")
3 @source(type='http',receiver.url = 'http://localhost:8080/exchange',@map(type='json'))
4 define stream exchangeStream(id string, age int);
5 @sink(type='log',@map(type='json'))
6 define stream outputStream(id string, age long);
7 partition with (id of exchangeStream)
8    begin
9          from exchangeStream
10        select id, sum(age) as age
11        insert into inner_outputStream
12  end;

As the code shows,I want to put a breakpoint in line 9 but it is not success.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
V1.1.0
OS, DB, other environment details and versions:
IDEA 2017.3.3
Steps to reproduce:
Just write a siddhi app with the partition statment and try to put a break point
Related Issues:
Similar issue

@yourgentlesmile  This  is actually not a issue in siddhi-idea-plugin. Currently, Siddhi doesn't has the support to add breakpoints in queries which are inside the partitions. So in both siddhi-idea-plugin and Stream Processor we don't have this feature yet.

@RAVEENSR Thank you~(＾ω＾)


OpenJDK 10

Feature Request
Desired behaviour
We should start replacing Oracle JDK 8 with OpenJDK 10.
This will affect local builds and Travis-CI.
Partial dependency on Cromwell , how well does this work with 10?)
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Issue Number: DOCK-169

Didn't really look into it much, but tooltester/jenkins didn't seem to work with OpenJDK 10 without changes

I definitely expect changes for these open-ended tasks :)

duplicate of ga4gh/dockstore#2320


⚠ Bofrost.be has degraded performance

In 6afd75e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1988 ms

Resolved: Bofrost.be performance has improved in aa2f740 after 6 minutes.


install failed opencv

pi@raspberrypi:~ $ brew install opencv
Updating Homebrew...
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- dbm (LoadError)
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/cache_store.rb:1:in `<top (required)>'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1:in `<top (required)>'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/readall.rb:1:in `<top (required)>'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/tap.rb:2:in `<top (required)>'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/global.rb:145:in `<top (required)>'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:15:in `require_relative'
	from /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:15:in

> `<main>'``

This bug will be fixed in Linuxbrew 1.7.7. In the mean time, try running…
HOMEBREW_DEVELOPER=1 brew update-reset


Add initialize with partial Table or Column Schema

creation of init_with_partial_schema, init_with_full_schema, and init
Closes #965

I'm wondering if there's a short-hand for the third "solution". Having us do it manually in all our components could lead to bugs and it's possible my "solution" does not carry over all of the relevant schema information, (like the origin field?)
@freddyaboulton we could add a force_infer_logical_types argument

@tuethan1999 I think that would work! Would the api be force_infer_logical_types=["Integer", "Boolean"] or would it infer all logical types again

@freddyaboulton I think the api would be more along the lines force_infer_logical_types=['b', 'c'] where the iterables arguments are column names

@tuethan1999 Sounds good!

@tamargrey now that we've already crossed the breaking change boundary, does it still make sense that we ignore arguments along with a full schema? It actually seems like the EvalML use case wants to pass in a full schema and specify which columns to reinfer. Tbh,init_with_full_schema seems more of an internal call to me.

@tuethan1999 @tamargrey I am okay with the breaking change.

I installed this branch locally and calling to_frame() on any ww series throws an error:

@freddyaboulton @tuethan1999 Interestingly, there is one way where to_frame doesn't error for me locally: when the Series is from a DataFrame.
y = sample_df.ww['id']
y.ww.to_frame()

However test_series_methods_returning_frame also doesn't error.

@tamargrey @freddyaboulton thanks for bringing this bug up. Turns out it breaks when the series doesn't have a name! working on a fix

lgtm! Idk if anyone else wants to take a last look before merging, though


feat: Loading builder for Route

Description

This change is mainly to make it easier for specifying loading screen along when routing between component using the RouterComponent. Currently the change is only made on Route, that now have optional loadingBuilder to Route constructor which would expect a Component, which would be added as the loading page/screen while  onLoad of the builder (the main routing component) to be completed.

Checklist

[x] I have followed the Contributor Guide when preparing my PR.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[x] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples or docs.

Breaking Change?

[ ] Yes, this PR is a breaking change.
[x] No, this PR is not a breaking change.

wait ya , dont merge yet, adding test for this

Don't merge yet.
hi @spydon , sorry I was away for awhile. Just pushed new one with test. Anyways, I just have problem it making a full test to check if the loading component was mounted before it was removed. I was only able to check for loading component was removed and the builder component ( page component) was mounted right after it was removed.
If you look at the file route_test.dart , I added test and also did add few comments , to explain the situation for the test coverage. Sorry I am not that good at coming with test, but I did manually check it by linking my version of flame repo to one of my old flame game, I mean my flame in pubspec refer to my git repo instead of pub.dev and test this feature I added, according to my observation it did work to what I expected.

I mean does checking the loading component was removed technically means it also verifies that it was mounted before right . So if that is the case then the test I added already suffice ?

@PistonShot1 have you made any progress on this? :)

@spydon . I have fixed it, sorry took so long for such a small feature addition, I gave up after the test keep on fail, but as you suspected it was the way I wrote the test, now it works fine and should be working and passed the expected tests


feat: add AWS Lambda detector

Which problem is this PR solving?

Support resource detection on AWS Lambda

Short description of the changes

Reads environment variables to fill resource on AWS Lambda as per Java and pending spec

I think it would be good to list the available detectors in readme of the package.
Once there is such a section in readme we should also mention that the spec required attribute faas.id is currently not detected.

@Flarna Sounds good, added the detectors to the README

It's not directly related to this PR. But I wonder why AWS (and GCP) detectors are in this repo instead in opentelemtry-js-contrib.

It's not directly related to this PR. But I wonder why AWS (and GCP) detectors are in this repo instead in opentelemtry-js-contrib.

I believe they are required by the spec at some point, but it make sense to move them back in the contrib now

It's not directly related to this PR. But I wonder why AWS (and GCP) detectors are in this repo instead in opentelemtry-js-contrib.

I believe they are required by the spec at some point, but it make sense to move them back in the contrib now

Agree they should move to contrib. I think the resource detectors actually predate the contrib repo and have just not been moved.

Thanks all, moving to contrib seems to make sense to me. Hopefully it's independent from this PR :)


Invalid OAuth2 redict_url

So I have problems with the Invalid OAuth2 redict_url. I configured all Redirects & it's still coming with this error.

Here is my config for this dashboard:
module.exports = {
"verification": "",
"description": "hi",
"domain": "REMOVED FOR SECURITY REASONS",
"google_analitics": "",
"token": process.env.TOKEN,
"https":"https://",
"port":"8080",
"client_id":"REMOVED FOR SECURITY REASONS",
"secret":"REMOVED FOR SECURITY REASONS"
}

Maybe I added wrong Redirects?

1- Make sure your domain is correct in the config.js file. Example http://localhost:5000
2- Make sure the domain doesn't have a / at the end, it affects. (http://google.com instead of  http://google.com/)
If it still doesn't work open a ticket in Pogy's support server and we will help you from there.

Alr, I will make a ticket as it doesn't works.


/client/src/components/Map/index.js

GitHub's got a new UX for task lists. One misclick opens an issue :(


SR-7154: swiftpm tests fail if --debug-foundation option is used.

Add a --swift-lib-dir so that tests can find libswiftSwiftOnone.so
which is required by libFoundation.so

The path to the libraries in the swift build directory are passed
to the test programs via the environment using LD_LIBRARY_PATH.

When testing using ./utils/build-script -R -T --llbuild --swiftpm --xctest --debug-foundation -- --reconfigure --lit-args=-v to build a debug version of Foundation, the libFoundation.so in the Foundation build directory is linked to libswiftSwiftOnone.so in the swift build directory. However libFoundation.so cannot find libswiftSwiftOnone.so  in its default RUNPATH. This adds an LD_LIBRARY_PATH to the environment so that libswiftSwiftOnone.so can be found ok.
This PR works in conjunction with https://github.com/apple/swift/pull/15498 for swift's main build script so it can pass the directory.

So swiftpm runs two binaries as part of its testing, build/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-build-stage1 and build/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-test.
The first one, swift-build-stage-1 runs without issue.  So when swift-build-stage1 is run, it dynamically loads libswiftSwiftOnoneSupport.so which it can find in /home/spse/src/swift/build/Ninja-ReleaseAssert/swift-linux-x86_64/lib/swift/linux. Later when libFoundation.so is needed, it is loaded from the second path $ORIGIN/../lib/swift/linux. $ORIGIN refers to the directory of the loading ELF file, in this case the directory containing ../build/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-build-stage1 which gives a resultant path of ../build/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/../lib/swift/linux, the contents of which are:
$ ls -l ../build/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/../lib/swift/linux
total 8
lrwxr-xr-x 1 501 dialout 96 Mar 27 22:32 libdispatch.so -> /home/spse/src/swift/build/Ninja-ReleaseAssert/libdispatch-linux-x86_64/src/.libs/libdispatch.so
lrwxr-xr-x 1 501 dialout 98 Mar 27 22:32 libFoundation.so -> /home/spse/src/swift/build/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation/libFoundation.so

So it finds libFoundation.so here. When libFoundation.so later needs libswiftSwiftOnone.so, it is already loaded and there is no issue.
The second binary that is run is build/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-test which has the following runpath and dependancies:
$ readelf -aW ../build/Ninja-ReleaseAssert/swiftpm-linux-x86_64/x86_64-unknown-linux/release/swift-test|egrep 'Library runpath|Shared library'
 0x0000000000000001 (NEEDED)             Shared library: [libswiftCore.so]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libutil.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libdl.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [libdispatch.so]
 0x0000000000000001 (NEEDED)             Shared library: [libswiftGlibc.so]
 0x0000000000000001 (NEEDED)             Shared library: [libFoundation.so]
 0x0000000000000001 (NEEDED)             Shared library: [libstdc++.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x000000000000001d (RUNPATH)            Library runpath: [/home/spse/src/swift/build/Ninja-ReleaseAssert/swift-linux-x86_64/lib/swift/linux:$ORIGIN:/../lib/swift/linux:/home/spse/src/swift/build/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation:/home/spse/src/swift/build/Ninja-ReleaseAssert/xctest-linux-x86_64]

This time swift-test loads libFoundation.so first which it finds via the /home/spse/src/swift/build/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation entry in the runpath.  This directory does not contain libswiftSwiftOnone so this is where the loading fails and the error message swift-test: error while loading shared libraries: libswiftSwiftOnoneSupport.so: cannot open shared object file: No such file or directory appears.
The addition of the LD_LIBRARY_PATH environment variable, which is considered after the RPATH, is added to point to /home/spse/src/swift/build/Ninja-ReleaseAssert/swift-linux-x86_64/lib/swift/linux/x86_64 which contains libswiftSwiftOnoneSupport.so and thus resolves the issue.
The following could be achieved through the use of extra symlinks and this is actually the case for the loading of libdispatch.so which is loaded via a symlink made by swift-corelibs-xctest's build-script.py adding a symlink into swift-corelibs-foundation's build directory however there are a couple of issues with this.

If swift-corelib-foundation's build directory is deleted, it wont know to add the symlink back.
Adding symlinks in multiple places in the build scripts is more inconvienent than providing a simple LD_LIBRARY_PATH environment variable (which is also the method used when invoking TestFoundation from build-script-impl)
If swift ever vends more libraries as part of its runtime / stdlib, extra symlinks would need to be created for those as well.

Extra information about ELF library loading that may be useful: How to write shared libraries

More options:

When libFoundation.so is built with -Onone it gets a runpath to the current location of the stdlib it was built against. It's not like we're going to distribute a debug Foundation anyway.
We all actually build into a common toolchain location somehow, instead of just putting products in each project's build directory. Unfortunate CMake changes, most likely.

Thus far, all development on Linux that I've done has required setting a correct LD_LIBRARY_PATH. Is it something that we don't want to have to occur?

@spevans Thanks for the detailed analysis. I like @jrose-apple's first suggestion about Foundation getting rpath to swift stdlibs when its built with -Onone. This currently happens automatically in swift-test because we use Swift compiler as the linker and it always embeds the stdlib's rpath. We manually remove the embedded rpath during the install step.

@millenomi If I remember correctly, LD_LIBRARY_PATH is usually considered anti-pattern and should be avoided but I don't really remember the reasons.

I reworked this by simply passing an LD_LIBRARY_PATH when running the tests:
call env LD_LIBRARY_PATH="${SWIFT_BUILD_PATH}/lib/swift/${SWIFT_HOST_VARIANT}/${SWIFT_HOST_VARIANT_ARCH}" "${swiftpm_bootstrap_command[@]}" test --test-parallel

This also means that this PR is not now required as it can all be done in utils/build-script-impl. I will update https://github.com/apple/swift/pull/15498 to use this method.
I think the issue with adding in runpaths into the libraries is that it makes the build process more complicated and will cause issues if not properly removed. Debugging is also made more complicated as this is now a non-obvious path added into the linking, as opposed to an explicit LD_LIBRARY_PATH on the command line.
@millenomi  I do have one question with the @testable import which is that if debugging needs to be enabled for the tests to run, how are the tests run on the snapshot builds which are built in release mode?

I still don't think we should use LD_LIBRARY_PATH. It will make things difficult when using SwiftPM's bootstrap command independently of the Swift's build-script. You can pass the runpath to foundation from the build-script. I am not sure why debugging becomes complicated. Is that some know issue?

Note that we don't want to provide an rpath for release builds, because we might make toolchains out of those and ship them to people.

Ive done an RPATH version for swift-corelibs-foundation in https://github.com/apple/swift-corelibs-foundation/pull/1495


local network communication

Hello. I am trying to make a local network communication between my two computers. I tried with python socket, but I saw in documentation that dora-rs supports TCP. After some time searching I didn't find any examples/issues/discussions on how to do it. Where can I check it?
Additionally, could you please update Discord invitation link. Thank you

Hi! There is a multiple-daemon example, and you can see the release note about multiple machines: https://github.com/dora-rs/dora/releases/tag/v0.3.5

Thank you very much. I followed the example with minimal example, reading frames from camera on raspberry pi and plotting it on my computer. I have the following error
2024-08-15T08:48:46.065534Z  WARN dora_coordinator::listener: failed to deserialize node message

Caused by:
    missing field `inner` at line 1 column 853

on Machine A I do as in example
dora coordinator
dora coordinator

on Machine B I do slightly differently
dora daemon --machine-id B --coordinator-addr <IP_ADDRESS>:53290
dora start dataflow_small.yml --coordinator-addr <IP_ADDRESS> --coordinator-port 53290

Thank you very much. I followed the minimal example, reading frames from camera on raspberry pi and plotting it on my computer. I have the following error

2024-08-15T08:48:46.065534Z  WARN dora_coordinator::listener: failed to deserialize node message

Caused by:

    missing field `inner` at line 1 column 853

on Machine A I do as in example

dora coordinator

dora daemon --machine-id A

on Machine B I do slightly differently

dora daemon --machine-id B --coordinator-addr <IP_ADDRESS>:53290

dora start dataflow_small.yml --coordinator-addr <IP_ADDRESS> --coordinator-port 53290

Hi, sorry for the error. Can you show me the dataflow YAML file, and your source code ?

yaml file
nodes:
  - id: webcam
    _unstable_deploy:
      machine: A
    operator:
      python: ../car/operators/webcam.py
      inputs:
        tick:
          source: dora/timer/millis/50
      outputs:
        - image

  - id: plot
    _unstable_deploy:
      machine: B
    operator:
      python: ../computer/operators/plot.py
      inputs:
        image: webcam/image

'webcam.py'
import os
import time

import cv2
import numpy as np
import pyarrow as pa

from dora import DoraStatus

class Operator:
    """
    Sending image from webcam to the dataflow
    """

    def __init__(self):
        self.CI = os.environ.get("CI")# TODO
        self.CAMERA_WIDTH = 960 # TODO
        self.CAMERA_HEIGHT = 540# TODO
        self.CAMERA_INDEX = int(os.getenv("CAMERA_INDEX", 0))

        self.video_capture = cv2.VideoCapture(self.CAMERA_INDEX)
        self.start_time = time.time()
        self.video_capture.set(cv2.CAP_PROP_FRAME_WIDTH, self.CAMERA_WIDTH)
        self.video_capture.set(cv2.CAP_PROP_FRAME_HEIGHT, self.CAMERA_HEIGHT)

    def on_event(self, dora_event, send_output) -> DoraStatus:
        if  dora_event["type"] == "INPUT":
            ret, frame = self.video_capture.read()
            if ret:
                frame = cv2.resize(frame, (self.CAMERA_WIDTH, self.CAMERA_HEIGHT))
            else:
                frame = np.zeros((self.CAMERA_HEIGHT, self.CAMERA_WIDTH, 3), dtype=np.uint8)
                cv2.putText(frame,
                    "No Webcam was found at index %d" % (self.CAMERA_INDEX),
                    (int(30), int(30)), cv2.FONT_HERSHEY_SIMPLEX, 0.75,
                    (255, 255, 255), 2, 1)
                if self.CI != "true":
                    return DoraStatus.CONTINUE
            send_output("image", pa.array(frame.ravel()), dora_event["metadata"])
        elif  dora_event["type"] == "STOP":
            print("received stop")
        else:
            print("received unexpected event:",  dora_event["type"])

        if time.time() - self.start_time < 10000:
            return DoraStatus.CONTINUE
        else:
            return DoraStatus.STOP

    def __del__(self):
        self.video_capture.release()

plot.py
import os
import cv2
from dora import DoraStatus

CI = os.environ.get("CI")

CAMERA_WIDTH = 960
CAMERA_HEIGHT = 540

FONT = cv2.FONT_HERSHEY_SIMPLEX

class Operator:
    """
    Plot image and bounding box
    """

    def on_event(self, dora_event, send_output):
        if dora_event["type"] == "INPUT":
            if dora_event['id'] == "image":

                image = dora_event['value'].to_numpy().reshape(
                    (CAMERA_HEIGHT, CAMERA_WIDTH, 3)).copy()

                if CI != "true":
                    cv2.imshow("frame", image)
                    if cv2.waitKey(1) & 0xFF == ord("q"):
                        return DoraStatus.STOP

        return DoraStatus.CONTINUE

Thanks. The code doesn't seem incorrect. However you're using operators and it's deprecated.
Could you try with standard nodes ? You can just use our pre-conceived nodes inside the node-hub directory.

Here is my updated yaml
nodes:
  - id: webcam
    _unstable_deploy:
      machine: A
    build: pip install ../dora-main/node-hub/opencv-video-capture
    path: opencv-video-capture
    inputs:
      tick: dora/timer/millis/16 # try to capture at 60fps
    outputs:
      - image # the captured image
    env:
      PATH: 0 # optional, default is 0
      IMAGE_WIDTH: 640 # optional, default is video capture width
      IMAGE_HEIGHT: 480 # optional, default is video capture height

  - id: plot
    _unstable_deploy:
      machine: B
    build: pip install ../dora-main/node-hub/opencv-plot
    path: opencv-plot
    inputs:
      image: webcam/image # image: Arrow array of size 1 containing the base image
    env:
      PLOT_WIDTH: 640 # optional, default is image input width
      PLOT_HEIGHT: 480 # optional, default is image input height

And I have the following error
Dataflow could not be validated.: paths of remote nodes must be absolute (node `webcam`)

Ok, so for remote machines you must specify absolute path to a source file. So you should remove the build procedure for the two nodes and pass the absolute path path/to/dora/node-hub/opencv-video-capture/opencv_video_capture/main.py

With the removed build and full path for path I have the same error as initially
WARN dora_coordinator::listener: failed to deserialize node message

Caused by:
    missing field `inner` at line 1 column 853

With the removed build and full path for path I have the same error as initially

WARN dora_coordinator::listener: failed to deserialize node message

Caused by:

    missing field `inner` at line 1 column 853

So it must be a bug with Dora. Could you tell us the exact version you're using for Dora ? (Lastest release, main branch ?)
I will try to solve it soon. But I can't until end of August because I'm on vacation

I am using dora-cli 0.3.5, installed from dora-v0.3.5-x86_64-macOS.zip. On my third machine where I experience the same problem, I used the same version but installed with cargo (armv7)


Is it planned to implement a module autocompletion?

Symbols autocompletion works pretty properly in VSCode with its extension (for my super-tiny projects at least) but there is no module autocompletion at all.
Don't you think it would be useful if we could type import str, press Ctrl+Space and see all modules which names start with "str": strutils, strformat, strscans etc. ?

There are many features that would be very neat. I saw in Java IDE automatic imports, so you had basically completion for functions that weren't even imported at all. But for me personally, before features are added stability should be improved. It is just a matter of priorities.

This works just fine now, e.g. if you type "import str" in the vscode nim extension you automatically get autocompletion.

Ignore my last comment, it seems like vscode-nim has that feature but it's not from nimsuggest - https://github.com/pragmagic/vscode-nim/blob/master/src/nimImports.ts

Also this seems to be a duplicate of https://github.com/nim-lang/nimsuggest/issues/47

Can be closed?


Fix native racetests

Fixes https://github.com/istio/istio/issues/15312
This should fix the racetest failures we are seeing. There are 3 fixes in this PR:

Fix reachability to not have the test case overwritten by .Parallel
Fix conformance test to copy the MCP response
Fix docker.newInstance to track resources serially. Alternatively we could do some mutexs but I think this is easier

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: howardjohn
To complete the pull request process, please assign nmittler
You can assign the PR to them by writing /assign @nmittler in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

pkg/OWNERS
tests/integration/conformance/OWNERS [howardjohn]
tests/integration/security/OWNERS [howardjohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test all

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
93049205ca5da9c0b3712c890739f69cef4554bd
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
93049205ca5da9c0b3712c890739f69cef4554bd
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
93049205ca5da9c0b3712c890739f69cef4554bd
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler]
tests/integration/conformance/OWNERS [howardjohn,nmittler]
tests/integration/security/OWNERS [howardjohn,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
93049205ca5da9c0b3712c890739f69cef4554bd
link
/test integ-mixer-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
1c1bc9af366db17a9d02ef471fbe766321ac355e
link
/test integ-new-install-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
1c1bc9af366db17a9d02ef471fbe766321ac355e
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
1c1bc9af366db17a9d02ef471fbe766321ac355e
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add "Mover.io"

Should be good to go.

Hello @SebJansen ,
This repo is not being maintained anymore, but we are trying to keep it alive on a detached fork here, would you kindly submit your PR there and close this one here? :)


support push info to hook

/lgtm
/approve

relate: https://github.com/milvus-io/milvus-proto/issues/370


Fix guidFor import

its fixes #298
// this works
import { guidFor } from '../utils/computed';
guidFor(whatever);

// and this works
import * as customComputed from '../utils/computed';
customComputed.guidFor(whatever);

// but this does not work.
import customComputed from '../utils/computed';
customComputed.guidFor(whatever);

This is a case where ember-cli historically allows a non-spec-compliant behavior.
cc: @Dhaulagiri

Thanks! Will release soon-ish.

thanks @Dhaulagiri

Released in 1.7.2

@Dhaulagiri you forget of publish this on npm

@villander sorry about that, it should be actually publish now 😸


Sync channel

Updated based on https://www.notion.so/elfour/Channel-syncing-224c505e440c4056b5e4f072f0bab631


can not delete json feild by PUT router

// Copies properties from an object to another
__update: function(dest, src) {
this.each(src, function(value, key) {
dest[key] = value;
});
},
just can update value， but can not delete it

@chuanY Good point, thank you for raising this issue. I'll have a look.

Should be good now :) v0.8.1


Vscode Debugger takes time to kick in

VSCode Version: 1.31.1
OS Version: 10.14.3 (18D109)

Does this issue occur when all extensions are disabled?: YES
Issue:
Breakpoints are taking a lot of time to start working.
Info: (My configuration uses docker with typescript.
Steps to Reproduce:

Setup breakpoint
Press F5 to run the debugger.

Expected:

When the code on the selected line gets execute, the breakpoint should work and stop execution.

Actual
Breakpoints don't get hit. To get it to work I have to do EITHER of these 2 things:

Wait about 65 seconds for the breakpoints to work.  (Seems like vscode is taking its time to get attached to the port than node exposes? my guess tough I am not familiar with the way it works).
Open chrome browser, click on the icon 'node debugger in chrome', set a breakpoint on the same line I selected before and give the code another run. This will stop on both chrome browser and vscode.

Relative Info:

Folder Structure

.vscode
package.json
src

routes
services
...

Launch.json:

{
	// Use IntelliSense to learn about possible attributes.
	// Hover to view descriptions of existing attributes.
	// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
	"version": "0.2.0",
	"configurations": [
		{
      "type": "node",
      "request": "launch",
      "name": "Launch in Docker",
      "preLaunchTask": "tsc-watch",
      "protocol": "auto",
      "runtimeExecutable": "npm",
      "runtimeArgs": [ "run", "docker-debug" ],
      "port": 9229,
      "restart": true,
      "timeout": 60000,
      "localRoot": "${workspaceFolder}",
      "remoteRoot": "/usr/src/app",
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen"
    },
	]
}

Tasks.json:

{
 "version": "2.0.0",
 "tasks": [
   {
     "label": "tsc-watch",
     "command": "npm",
     "args": [ "run", "watch" ],
     "type": "shell",
     "isBackground": true,
     "group": "build",
     "problemMatcher": "$tsc-watch",
   }
 ]
}

Package.json:

{
   "debug": "nodemon --watch ./dist --inspect=<IP_ADDRESS>:9229 --nolazy ./dist/bin.js",
    "docker-debug": "docker-compose up",
    "watch": "tsc -w",
    "start": "node dist/bin.js",
}

DockerFile:

FROM node:10-alpine

RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app

# Install app dependencies
COPY package.json /usr/src/app
RUN npm install

docker-compose.yml

version: '2'
...
services:
foo-service:
volumes:
      - ./public:/usr/src/app/public
      - ./dist:/usr/src/app/dist
    ports:
      - 80
      - "9229:9229"
environment:
      NODE_ENV: development
      HOST_PORT: 80
    command: npm run debug
    restart: always

What OS are you on? Could you set "trace": true in your launch config, run it again, and upload the log from the path that it writes to the debug console? That should help me figure out why it's slow. A similar issue was reported in #69118 but I don't know why it's happening yet.

Thanks for the reply @roblourens. Yes, that is exactly the same behaviour I am experiencing.
My OS is: MacOS Mojave 10.14.3 (18D109) and here are the logs:
debugadapter.txt
Let me know if there is anything I could help.

Thanks! This is different than the other issue. Since you have a "launch" config, we run your runtimeExecutable then we wait for node to start and pause on start. We wait for "timeout" ms which in your case is 60s. The log shows that this is what the debugger is waiting for. However in your case the launch task just takes the container up. So I'm guessing at some point the container is already up and your node process is already running and so node will not "pause on start".
I think the best way to fix it is to use an "attach" task instead of a "launch" task. This will just try to attach to an already running node instance. But you could probably still get it to also start the container when it's not running by specifying a preLaunchTask and writing a task that takes the container up.
Alternately you could just decrease the "timeout" but then risk it timing out when the container is not actually running before you start debugging.

@roblourens Ha! Nice.
I like your idea of bringing the container up with a preLaunchTask, it makes the launch more robust. I also tried reducing the timeout to 1s and it worked too. My server is very small and I only send the dist folder to the container so it doesn't need that much time but I will def try the preLaunchTask. Thanks.
I will close the issue now.


Bug Fixes

Change from copying Roso fields twice to copy Pofo and Roso
Remove 1 that was added to template

LGTM


Maintaining and accessing session and user identity at Apache

Hi,
In continuation of the conversation in https://github.com/pingidentity/mod_auth_openidc/issues/252.
Thanks for the information.
Our use case is typical web application with authentication and session management features - as depicted in the attached flow diagram.
In this context, user session and identity to be managed at Apache HTTPD and sent to Tomcat application server to process the request. This may mean, Apache is acting as both Relying Party and Resource Server.
In this flow, we need access of ID_TOKEN and request object at Apache layer and pass this information to Tomcat application. Please guide how can we achieve this?
thanks
ganga

You can pass the ID token and/or the individual claims from the ID token as headers to Tomcat, see: https://github.com/pingidentity/mod_auth_openidc/blob/master/auth_openidc.conf#L611

Please note: the issues list is meant for bug/feature requests; general questions about how the module works should go to the mailing list<EMAIL_ADDRESS>


APIDigester: Break cycle between swiftFrontend and swiftAPIDigester

Also refactor to remove SIL dependency from APIDigester.

@swift-ci please smoke test

@swift-ci please smoke test


Getting more done in GitHub with ZenHub

Hola! @DawidCh has created a ZenHub account for the servicecatalog organization. ZenHub is the only project management tool integrated natively in GitHub – created specifically for fast-moving, software-driven teams.

How do I use ZenHub?
To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.
What can ZenHub do?
ZenHub adds a series of enhancements directly inside the GitHub UI:

Real-time, customizable task boards for GitHub issues;
Multi-Repository burndown charts, estimates, and velocity tracking based on GitHub Milestones;
Personal to-do lists and task prioritization;
Time-saving shortcuts – like a quick repo switcher, a “Move issue” button, and much more.

Add ZenHub to GitHub
Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @DawidCh.

Shall we try?


"no-response" v2 - Close issues after 10 days of inactivity

actions/stale is a bot that helps in closing isues after being marked as stale
an issue gets marked as so when it becomes inactive for 5 days, this can be changed in the file
after being marked as stale, it waits 5 more days, then closes the issue if the label remains there
this workflow will ignore issues labelled as "enhancement", "need more information" and "special"

damn thanks github (reopening shortly)


How to using more than 1 wallet to single defi wallet

I am using more than 1 wallet on my defi wallet app and for change wallet I change manually defi.conf files
Each defi.conf file contain the information to login to a single wallet
Example defi.conf (1)
rpcauth=AAAAA
rpcuser=AAAAA
rpcpassword=123
wallet=Wallet1
walletdir=/home/angelo/wallet1
Example defi.conf (2)
rpcauth=BBBBB
rpcuser=BBBBB
rpcpassword=456
wallet=Wallet2
walletdir=/home/angelo/wallet2
For sent and receive dfi i dont have any issue, also I am using dex and liquidity without issue, but when I using pre-fun txns function automatically sent 0.01 to all my wallet (wallet 1 + wallet 2 + wallet 3 + wallet 4 etc etc) not only the current wallet that i am using. I dont know where defi wallet save my own address that I have used.
There are better solution for admin more than 1 wallet separately ? If is possible I dont want to run more virtual machine
Thanks for suggestion

Hi @angelocastiglione , here's how you can run more than 1 wallet on the same app. For example, you're on wallet 1, and want to go to wallet 2:

Click Exit Wallet icon

You should be prompted to Backup Wallet 1, kindly backup then exit

After backing up, Restore wallet via backup > Select wallet 2's wallet.dat

Continue using wallet 2 from there. Thank you.
You may turn to DeFiChain’s telegram for how-to related issues:
DeFiChain Telegram (EN)


fix: broken MIB translation unit tests

config.yaml wasn't properly loaded (need to look to the parent's folder)

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@975c556). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage        ?   96.69%
=======================================
  Files           ?       25
  Lines           ?     4545
  Branches        ?        0
=======================================
  Hits            ?     4395
  Misses          ?      150
  Partials        ?        0

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 975c556...45d1b73. Read the comment docs.


Full screen Back button

Hi. Is it possible to customize or remove back button in full screen mode? It seems too small and it's difficult to tap on it

Extends JCVideoPlayerStandard Override setUiWitStateAndScreen(), invisible back button.


postTaskDebugger does not wait debugger under windows with node-lambda

Hi all, I usually works on backend project with AWS and node-lambda tech. These weeks i have a temporary computer under windows because my first one that run under linux was in repair. So I have to rewrite some preLaunchTask and postDebugTask scripts but i can't make it works as in my Linux computer.
Here comes a piece of my config:
launch.json
        {
            "type": "node",
            "request": "launch",
            "name": "Debug Node Lambda for Linux",
            "program": "/usr/local/bin/node-lambda",
            "args": [
                "run"
            ],
            "preLaunchTask": "debug",
            "postDebugTask": "clean"
        },
        {
            "type": "node",
            "request": "launch",
            "name": "Debug Node Lambda for Windows",
            "program": "${workspaceFolder}\\node_modules\\node-lambda\\bin\\node-lambda",
            "args": [
                "run"
            ],
            "preLaunchTask": "debugForWindows",
            "postDebugTask": "cleanForWindows",
        },

tasks.json:
               {
			"label": "clean",
			"type": "shell",
			"command": "./.debug/clean.sh"
		},
		{
			"label": "debugForWindows",
			"type": "shell",
			"command": ".\\.debug\\launch.windows.sh",
			"args": [
				"${file}"
			]
		},
		{
			"label": "cleanForWindows",
			"type": "shell",
			"command": ".\\.debug\\clean.windows.ps1"
		},
		{
			"label": "cleanTestForWindows",
			"type": "shell",
			"command": ".\\.debug\\clean.sh"
		}

launch.windows.sh:
#!/bin/bash
fileName=`basename ${1}`;
fullPath=`dirname ${1}`;
module=$(basename $fullPath);
functionName="${fileName%.js}";

node-lambda setup

echo "AWS_ENVIRONMENT=development" >  .env
echo "AWS_ROLE_ARN=your_amazon_role" >>  .env
echo "AWS_REGION=eu-west-1" >>  .env
echo "AWS_FUNCTION_NAME=" >>  .env
echo "AWS_HANDLER=$module/$functionName.handler_$functionName" >>  .env
echo "AWS_MODE=event" >>  .env
echo "AWS_MEMORY_SIZE=128" >>  .env
echo "AWS_TIMEOUT=3" >>  .env
echo "AWS_DESCRIPTION=" >>  .env
echo "AWS_RUNTIME=nodejs8.10" >>  .env
echo "AWS_XRAY_CONTEXT_MISSING=LOG_ERROR" >> .env
echo "AWS_TRACING_CONFIG=true" >> .env
rm event.json
cp "$fullPath/"test_$functionName.json event.json

clean.sh:
#!/bin/bash
rm event.json .env deploy.env context.json

as you can see my preLaunchTask creates and inits conf files for my node-lambda program, debugger launch it and postLaunchTask erases them to clean the project. This works like a charm under linux but under windows it seems that postLaunchTask  does not wait after debugger return and launch it directly, before the debugger can reach the first breakpoint. So node-lambda can not be launch because conf file has already been erased by postLaunchTask. It could be due to parallelism and async side of my lambda code. Debugger works fine if I dont use my postLaunchTask but it is not a good solution.

probably the same problem at the first debug session, debugger launch before files have been creating by my node-lambda setup command so debugger don't work at the first try but after itis good.
so i think that debugger don't wait the end of preLaunchTask before starting...


Parse Timex property hourAmount, minuteAmount + secondAmount as decimal

This should support valid Timex strings like "PT0.5H" in the .NET package.

@microsoft-github-policy-service agree [company="we-do.ai GmbH"]

@microsoft-github-policy-service agree [company="{your company}"]


Fix for laravel versions without reflection api support (resolves tighten/ziggy#437)

This PR resolves the issue originally raised in #358. I appreciate the root cause is not with Ziggy, but I've created a solution that allows backwards compatibility for those using Laravel <6.18.17 with barryvdh/laravel-debugbar.
Context
The root issue was resolved in Laravel 6.18.17:

Support PHP 8's reflection API (#33039)

For those using earlier versions, I've resolved the error by bringing forward the point at which any excluded route names are filtered out. This means that excluding debugbar via the config...
// config/ziggy.php

return [
    'except' => ['debugbar.*'],
];

...now resolves the error, as previously the error was encountered before the filtering took place.
And now I can successfully generate a ziggy file 😄
File generated!

New Unit Tests
 ✔ IsExcluded can identify excluded route via except
 ✔ IsExcluded can identify excluded route via only
 ✔ IsExcluded can identify included route via only
 ✔ IsExcluded can identify included route via groups
 ✔ IsExcluded can identify included route via groups when only is also set
 ✔ IsExcluded can identify route in both excluded and groups as included
 ✔ IsExcluded can ignore excluded route when both except and only are set
 ✔ IsExcluded can ignore route when no config set

Thanks a lot for this PR and for including tests! My preference would be for this to be fixed upstream, ideally in the laravel-debugbar package, so I've submitted a PR there (barryvdh/laravel-debugbar#1203) to avoid registering the Telescope-related route causing this issue unless Telescope is actually installed.
Either way though, I really like your idea of not touching excluded routes at all.

Thanks @bakerkretzmar ! That's certainly a lot simpler 😄


Toggle task done command should add the global task filter text

Discussed in https://github.com/obsidian-tasks-group/obsidian-tasks/discussions/1319

Originally posted by axelson November 13, 2022
Currently if you've set your Global task filter setting (i.e. to #task) then if you use the Toggle task done command you won't actually be creating a task unless you also manually type in #task. It would be nice if the Toggle task done command automatically added your Global task filter text.

Thanks for the suggestion.
I can't find any earlier requests for it.
At first I read this as if you were completing a task, but I think that you mean that if you have a line typed already, and then run Toggle task done it gains a checkbox but not a global filter, which means it will not show up in any task queries.
Good point, I agree.

Yes that's basically it, although usually I start from an empty line and run Toggle task done twice to create a task and I'd like that task to have the Global task filler task already inserted. Thanks!


import error

Describe the bug
1: imported the image into the generator and exported the MKCD file.
2: opened the MKCD file with MakecodeArcade.
3: deleted the test.ts file.
4: Downloaded the project in png format.
5: Opened the png file with MakecodeArcade.
6: An error message was displayed.
"Oops, something went wrong when importiong your project."
7: When I try to open the same project again, it doesn't open.

Here’s the png file with the error
https://aws1.discourse-cdn.com/standard14/uploads/makecode/original/2X/c/cfbcb34458db180623b0f45c1ca2c89b7e233759.png

Awesome, thank you so much for filing, and for providing the PNG! We'll look into fixing this ASAP


[RFE] Drop ct support from Mantle

Current situation
While ct is deprecated and not used anymore (even LTS can support Ignition 3 now) - we might be interested to drop ct from Mantle to only use Butane.
Impact
Scaleway test suite can't be implemented without hacks as Mantle flight relies on ct platform -> we can use a ctplatform.Custom but we need then to implement some logic to convert the Scaleway metadata to the expected "custom" format.
Ideal future situation
No more ct configuration inside Mantle, everything relies on Butane or raw Ignition.
Implementation options

Remove ctplatform dependency from ctplatform
Rewrite ct configuration to butane configuration (git grep ContainerLinuxConfig)

See also: https://github.com/coreos/coreos-assembler/commit/f0e49857931dec827992903c7b335fa9830fb0b9

Scaleway test suite can't be implemented without hacks as Mantle flight relies on ct platform -> we can use a ctplatform.Custom but we need then to implement some logic to convert the Scaleway metadata to the expected "custom" format.

Can you link to some code? I don't understand what ctplatform and why it would require hacks to support scaleway.
If we remove ct from mantle we can't be sure that we won't break users who still have old ignition configs. I'm sure they haven't migrated.


PEP 8 formatting

I tend to set my IDE to flag up violations of PEP 8 style guidelines. Having a set of agreed formatting rules prevents reformatting battles breaking out in commits to shared repositories. I note that some of the code written recently fails the line length checks in particular. Do we need to define a set of rules that can be enforced at commit time to make sure that we're all working with a consistent pattern?

I like Black and have that as standard in my IDE. I agree would be good to have a standard.

Black is fine if you don't work with other people, or if you all work with it. In this case, I don't think it will be a high-maintenance, multiple commits kind of project so the precise details are less important.
I tend to use the PEP 8 defaults in PyCharm because it doesn't require me to install another dependency. I don't know if they play nicely, or fight with BlackCodeStyle

The ideal technical choice respects explicit # @formatter-off / # @formatter-on directives

I'm happy to use whatever formatter is felt by the team to be the best. I'm using VSCode so ideally something that can be installed as a VSCode extension.

Addressed by Pull Request #17


backport: kytos/.*.uni_available_tags to update UNI tags in interfaces

Closes #165
Summary
The base branch is base/2023.1.0, It is what we have on releases.
Added kytos/.*.uni_available_tags so Interface.available_tags is updated in the DB when a UNI tag is allocated
Local Tests
Added uni tests
Created EVCs and see allocated vlan from interfaces.
End-To-End Tests
Results in mef_eline PR

Nicely done @Alopalao. Also, appreciated you making the DB script safer.
Feel free to merge this into base/2023.1.1 and then create a GitHub release targeting base/2023.1.1 (also creating the git tag accordingly), if you need help let me know (also feel free to do the same for kytos-ng/mef_eline#381).  Since you're at it, it might be worth to take the opportunity to also run vlan_pool.py DB script in that prod copied data, even though it's not related to this PR. Thanks, Aldo.

@Alopalao I realize your progressing with vlan range and other PRs, but following up here, did you have the chance to also run the script with copied prod data? If positive and it's passing feel free to merge and bump the version. If you need my help to also merge or tag upstream let me know. Thanks.

I have not received the copied data, but I tested with one created by following e2e tests examples. The updated script worked with failover_path and current_path.

I have not received the copied data, but I tested with one created by following e2e tests examples. The updated script worked with failover_path and current_path.

OK. Good to know @Alopalao. I'll go ahead and merge this PR. Regarding the prod data, it won't be a blocker, since it looks good and you locally tested it with other data, but please map a task for trying out all scripts with prod data, it'd be helpful for @italovalcy to also have this feedback. In the future, we do plan to have e2e tests with equivalent prod data in terms of scalability, but until then for certain cases core developers still need to also explore them. Thanks.


'BotSettings' issue

After the upgrade, I'm getting this error message:
AttributeError: 'BotSettings' object has no attribute 'model_copy'

Interesting, I am not seeing this error. The class definition is:
class BotSettings(BaseModel):
...

and BaseModel has the model_copy attribute: https://docs.pydantic.dev/2.5/concepts/serialization/#model_copy
In previous versions of pydantic this function had a different name, so I am wondering: is there a chance you are using a version of pydantic earlier than the one specified in requirements.txt (2.5.3 currently)?


Add support for pure integration tests

Description
This PR embeds the mint_url in the HttpClient itself, since every of its methods was anyway always with the wallet's mint_url as arg.
This has a few other benefits:

it will make it easier to encapsulate logic for mints with multiple URLs inside HttpClient ("if URL A fails, try URL B")
it makes "pure integration tests" possible, which can call and test mint methods without the extra HTTP layer

Notes to the reviewers

Suggested CHANGELOG Updates

CHANGED
Add support for pure integration tests

Checklist

[x] I followed the code style guidelines
[x] I ran just final-check before committing

I rebased to include the recent Uuid change.
I also had to add an explicit conversion between the String and Uuid types for the DirectMintConnection used in the pure integration tests : 6f0b2de99b1d896b2020dd424f3b8d5457e0d805


Titles for forms

Can the forms have titles at the top? I get lost on what is happening without that. I know the sidebar indicates which form it is via the green dot, but having it written at the top above where you are entering seems to be what my brain needs. (like right above required fields or next to the add/edit/delete symbol)

I would like to see what the rest of the team feels about this as it is largely an aesthetic choice.

I am ambivalent. I didn't get lost in forms, but also didn't put in the massive session that Dori did where I entered lots of different things. This might be a good specific question to ask at the Hack-a-Thon and then move forward accordingly.

Sounds good - it could just be a matter of getting used to it/training oneself. (I'm doing better with it now). Let's put on discussion/feedback list for the hackathon. I'll make a working doc for that now.

No one brought this up at Hack-a-Thon, and I think we have more important issues to finish us out. I'm closing this one.


Add Mac CI build for aarch64 (Mac M1)

We do test building for aarch64 for Android which gives some coverage, but would be good to have Mac aarch64 CI target as that is a primary platform for us, and PhysX codebase can fail specifically on it as showin in #133.
Not sure if the would nicely cross-compile from the existing Mac x86 agents, or if we should wait until GitHub has Mac aarch64 native agents (could take a long time).

Oops, closed in #183
https://github.com/EmbarkStudios/physx-rs/blob/49176ebed029614e8e5072ce18c4440b99e82f08/.github/workflows/ci.yaml#L76-L94


Backup and restore on RTF

Is there a way to verify a backup (checking for specific contents, etc.), or do we assume success if no error code is returned?


Rate limit 0 reached :: provider.terraform-provider-github when using TF CLI

Hi Team,
I need your help.
I am using the TF CLI and during the TF plan, I am unable to set the github token. I have set this variable on the machine level, but the task doesn't get the token and the call the GitHub API as anonymous.

https://registry.terraform.io/providers/integrations/github/latest/docs
Here is my part of yaml pipeline
      - task: TerraformCLI@2
        inputs:
          command: plan
          workingDirectory: '$(System.DefaultWorkingDirectory)/${{parameters.env}}'
          environmentServiceName: 'APP-SP-CORP-TF-${{parameters.env}}'
          providerAzureRmSubscriptionId: '$(subscription_id)'
          commandOptions: '-no-color -out=tfplan.json'
          allowTelemetryCollection: false
          publishPlanResults: '${{parameters.env}}'`

And when the API call anonymous, I got the rate limit issue in my pipeline. Can anyone face the similar issue and know the workaround for it.

I am using the GitHub service connection and tried both Azure Pipeline GitHub OAuth / Personal Access Token in the Azure Pipeline. Also set the export variable during the pipeline but none of them solve the issue mentioned above..

This does not appear to be a TerraformCli issue, but an Azure Devops issue.  If the GITHUB_TOKEN variable is in your environment then Azure Devops is probably not injecting it because it knows it is a secret (as decribed here).


Instragram posts no longer working

Facebook changed the API, it requires authentication now
https://embedsocial.com/blog/instagram-api-changes-2020/#oembed

Fixed in version 1.1.0


Customized macro

Hello, is it possible to make a macro that runs cmake.build command first and start debugging right after cmake.build finished? Thanks.

Have you checked available params in docs https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes ?
Looks like preLaunchTask is what you are looking for (when you add that script to tasks).

In your launch configuration (in launch.json) you can add the "cmake.build command" as a preLaunchTask.
Search for preLaunchTask in this section of VS Code's debugger documentation: https://code.visualstudio.com/docs/editor/debugging#_launchjson-attributes

@IllusionMH @weinand Thanks for your answers.
But what I need is another customized command which able to lunch from F1 key dropdown list, just like cmake.build.
I don't need to run cmake.build every time I debug the program, so need to separate this customize command from debugging command.

you can use a macro extension, e.g.  https://marketplace.visualstudio.com/items?itemName=jeff-hykin.macro-commander


[translation] Discussion To Remove Preprocessing (Sharding+Tokenization) From Timing

Moving rules question from https://github.com/mlperf/reference/issues/109:
The preprocessing stage requires a non-negligible fraction of the overall execution time, especially as models are optimized. It seems like timing this portion may not be representative of real-world use cases since the cost of preprocessing in this situation is not amortized over multiple training sessions. I would vote to remove the timing around preprocessing, but I would like to see if there is a good reason for keeping it.

We should record this information, as it's quite useful. More information is better.

If we don't count pre-processing, then this will incentivize everyone to do maximal pre-processing to keep actual training short and simple. Do we believe this is representative? Is this good?

It seems to me that if we want to truly measure end-to-end latency, we need pre-processing.

Your point about pre-processing is that in 'real world' scenarios, pre-processing is a smaller proportion of the overall problem than in the MLPerf tests because 'real world' you train multiple times on the same data set.  MLPerf is a first attempt to get things right, we don't need to be perfect initially.

Why is translation different from, say, image classification?

This issue is complicated and we will revisit this issue next week.

See issue 30 for v0.5 policy.

Closed as covered by issue #30.


[MERGE] Merge branch-1.7

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/18636/
Test PASSed.


[Q] matching image tag patterns

Hey folks, thanks for this neat service! I'm currently playing around with the upgrade feature and was wondering if it is possible to match not only exact tags, but also against a certain pattern, eg:
matcher: release-*
dockerhub tag: release-v1.1.2
Many thanks in advance!

No, at this time, it's only exact tags, but I've created this issue in Rancher as an enhancement request:
https://github.com/rancher/rancher/issues/8446


B12.1 Deploy Node Registries

💡 Description
Work related to finalizing the deployment of node registries.

[ ] ATM
[ ] RMS
[ ] GEO
[ ] IMG
[ ] NAIF
[ ] SBN-UMD
[ ] SBN-PSI
[ ] PPI
[ ] PSA

📆 December status: Delayed due to ElasticSearch versioning and personnel issues. Slack built into remainder of schedule so no impact on B12.1 foreseen.

📆 January status: delayed again to wrap up documentation. no impact foresee yet on build, but will be monitoring closely to ensure https://github.com/nasa-pds/pds-registry-app/issues/226 is completed

Complete. Will revisit PSA registry deployment at a later time.


new solution Path Sum added to leetcode

Why have you added .vs folder?

It got added by default ,as I was editing the file in vs(visual studio)
If you want I can delete that file

It got added by default ,as I was editing the file in vs(visual studio)
If you want I can delete that file

Sure.

Hey, I have deleted .vs folder

you can take a look, if you want

If you want I can add more solutions of leetcode???

If you want I can add more solutions of leetcode???

sure, go for it.

If you want I can add more solutions of leetcode???

Sure you can, but you may open new pull request for those.

ok

Thank You @sakshi-1604
Keep Contributing :-)


Project Updated

Hello Chaaya.
Thanks for the directive. This pull request just merge the new commits from upstream "https://github.com/Narzerus/angular-permission" and some README documentation update.
Thanks man.
Cheers.

Thanks @paulorbpacheco!
Hope you find it useful!


Unable to download artifacts when using insecure: true

Checklist:

[X ] I've included the version.
[X ] I've included reproduction steps.
[ ] I've included the workflow YAML.
[ ] I've included the logs.

What happened:
When trying to download artifacts through the UI, when setting insecure: true under the s3: configuration, was presented with http: named cookie not present
What you expected to happen:
Artifacts should be downloaded.
How to reproduce it (as minimally and precisely as possible):
Set insecure: true and try to download an artifact.
Anything else we need to know?:
Environment:

Argo version: 2.5.0-rc7
Kubernetes version : 1.16.4

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Discussed more in https://github.com/argoproj/argo/issues/2129, however that ticket is tracking the missing CA certificates for insecure: false.  This seems to be unrelated.

this seems to happen whether you set insecure to true or false.

thanks @haghabozorgi! i'll update the description.  i don't currently have a good way to test with inscure: false.

@ddseapy  https://github.com/argoproj/argo/pull/2129 was closed based on https://github.com/argoproj/argo/pull/2147 being merged. Using install.yaml from master branch and adding the volume and volume mounts from tcolgate's comment (til https://github.com/argoproj/argo/pull/2143 is merged)  still leads to http named cookie not present. Not sure if that is expected, given your last comment in https://github.com/argoproj/argo/pull/2129?

Fixed by https://github.com/argoproj/argo/pull/2147

Please re-open if not :)


Additional (CNPJBR and CPFBR): Fix not to fail when field is not required

Additional: CNPJBR and CPFBR
Fix not to fail when field is not required

Thanks for your contribution :)


Lidar Revolutions

Something weird is going on with the origin point of the raycast needs investigating and fixing.

See Environments/LidarTestScene_with_robot.gd for a testing level confirming.


UI Tweaks

Just a few tweaks to make the UI feel a bit more polished.

Suh-weet! :D I love it.


That one weird transparent format

Um yeah that thing...
[2017-04-30 10:46:42] <Runer112> speaking of convpng
[2017-04-30 10:47:00] <Runer112> did you ever create the fast transparent sprite conversion
[2017-04-30 10:48:24] <MateoC> oops
[2017-04-30 10:48:26] <MateoC> No :P
[2017-04-30 10:48:46] <Runer112> I recently rediscovered my attempts to create that routine
[2017-04-30 10:48:52] <Runer112> I think the unclipped version is actually done
[2017-04-30 10:49:02] <Runer112> would be nice to test i
[2017-04-30 10:49:10] <MateoC> Okay :)
[2017-04-30 10:49:18] — MateoC gets out the logs to find the format
[2017-04-30 10:49:55] <Runer112> each row is just an alternating sequence
[2017-04-30 10:50:03] <Runer112> trans run length, opaque run length + data
[2017-04-30 10:50:15] <Runer112> always starts with trans
[2017-04-30 10:50:39] <Runer112> (so if the row actually starts opaque, just emit a 0 for the first trans run length)
[2017-04-30 10:50:58] <MateoC> Okay :)
[2017-04-30 10:51:05] <MateoC> Just normal rle?
[2017-04-30 10:51:16] <Runer112> not normal RLE, no
[2017-04-30 10:51:22] <Runer112> but similar
[2017-04-30 10:51:34] <MateoC> Got it
[2017-04-30 10:51:51] <Runer112> basically, the "run" has no value associated with it
[2017-04-30 10:52:00] <Runer112> it's a meta transparent run

I think this is pretty good now so I'm going to close it :P


Flutter: API Calls are so slow in flutter, taking more than 20s to load with WiFi and less than a sec with Mobile Data

I have a weird issue with Flutter (Android app only) for the past few days. I make 3 API calls, which usually takes less than 2 sec to load, but for the past few days it's taking more than 20s to load with WiFi and less than 2 sec with mobile data. I tried with multiple WiFi networks but the result is same. The problem exists with Android app only and works fine with iOS. Wifi connection speeds were more than 100Mbps.
With postman, the same calls can be made in 0.7s.
I use Dio for api calls.
Has anyone faced this issue? I'm not able to understand the reason. Help would be highly appreciated.
Thank you
**UPDATE - The same api calls works normally (loads fast) in android phones running Android 9 or less with WiFi.
This is flutter doctor -v
`[✓] Flutter (Channel stable, 3.3.2, on macOS 12.5.1 21G83 darwin-arm, locale en-IN)
• Flutter version 3.3.2 on channel stable at /Users/davin/Documents/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision e3c29ec00c (9 days ago), 2022-09-14 08:46:55 -0500
• Engine revision a4ff2c53d8
• Dart version 2.18.1
• DevTools version 2.15.0

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

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

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

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

[✓] VS Code (version 1.71.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • SM N975F (mobile)          • RF8M749NZ7J                          • android-arm64  • Android 12 (API 31)
    • iPhone 13 Pro Max (mobile) • 6B4691F0-AFA4-44E6-82BD-4E946DC60D45 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS 12.5.1 21G83 darwin-arm
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 105.0.5195.125

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

• No issues found!`

I use Dio for api calls.

@jerrypaulsam Can you try using http package and see using it, you get same behavior ?
See this for your reference and check if it helps in your case.

I was able to solve this issue, it is related to ipv4 and ipv6 requests.
Somehow flutter android apps  with android version greater than 10 is trying to connect to ipv6 address automatically and only after failing, reverting to ipv4, so there is a huge delay in getting response whereas in Android 9 and less, this isn't a problem. In flutter, there should be an option to manually choose ipv4 or ipv6 addresses.

Good to know that issue is resolved. Closing.


Terminate the target process, restart it, PI shows (terminated) multiple times

Dev Home version
0.503
Windows build number
10.0.22631.3672
Other software
No response
Steps to reproduce the bug

Run PI, and associate with some app.
Go to Expanded mode
Terminate the target process.
See we append (terminated).
Restart the target app, and associate PI with it (via process list or hotkey)
Terminate the target process again.
See we append (terminated) (terminated)

Expected result
No response
Actual result
(terminated) is repeated.

Included System Information
No response
Included Extensions Information
No response

No repro