Missing links in this article

Hi there,
There is not enough clarity on how the AI Log analytics or Log Analytics work space are linked to the logic flow action? after running the flow I dont see any thing coming up in AI Log Analytics as well as the Log Analytics workspace. even strangely the action "Send Data" is not taking any input like Log Analytics workspace id etc...
on the path of the container in Get Blob Content using blob action. Assuming this flow will be actively monitoring the blob so it should

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

ID: ff6334a4-8a70-0aae-b31b-3027831ff6e3
Version Independent ID: f7b71cad-f09f-adef-ccd6-46efc0be15df
Content: Create a data pipeline with the Azure Monitor Data Collector API
Content Source: articles/azure-monitor/platform/create-pipeline-datacollector-api.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@BhupalPatil Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

@BhupalPatil I believe the document consists of an example that too a hypothetical scenario illustrating the overall functionality of Data Collector API Pipeline.
Assigning content owner @MGoedtel for visibility of your valuable feedback on the document, for review and for document enhancement considerations if any.

@BhupalPatil - The Send Data action when added in the designer should prompt you to provide connection details (Connection Name, Workspace ID, etc.).  If not, when you select Send Data there is an option in the Send Data action - Change connection and you can select an existing connection or create a new connection.  Without being able to reproduce your issue, I would delete the Send Data action and try again and verify it prompts you to provide those configuration settings if it doesn't indicate this was already configured for this Logic App.
Hope that helps. I'll ping the author, who works on my team to review this and recommend the steps are revised to provide more detail regarding behavior/configuration of the Data Collection action.

I've created a work item for the doc and not sure when it will get prioritized.  Being this isn't a common issue raised with the article, I'm suggesting we close it - #please-close.

@MGoedtel Thanks for getting back on this.
I deleted entire flow and recreated and then on send data action I got the prompt to enter the Workspace Id and Workspace Key.
Workspace Id is available on the section overview but Key is not available in any section.. explored all option from left menu bar... Can you help with some pointers here? also it is not clear in which table the blob contents will go? is it going to create new table with the value that we  entered in "Custom Log Name" field on the send data action?


Mouse-Over field-name currently only for admins

Summary
In the "edit-view" when hovering over the labels, as an administrator, you see the field-name popping up, as a not-admin, you don't.
Step to reproduce
Hover over a field-label.
Observed behavior
As an admin you get the name of the available placeholder:

As an editor (another group), you don't.
Expected behavior
As ClientConfig is for the editors/clients, they should definitely get the mouse-over-info, so they can independently use these, without needing to "remember" it.

This was actually intentionally hidden for clients, as it's kind of a technical implementation detail that those users really shouldn't care about. I'm okay with adding a setting that toggles that behaviour though.

By the way, the name of fields with the type "file" and "image" (maybe with other types) are not shown at all.


Refactoring PlatesFormatter

Refactoring PlatesFormatter and corrected his test for this branch.
I also added the method PlatesFormatter::output to remove from the array output template name.
I think that key for a template name needs the suffix @template or something. A value should be formatted like @domain::index. But the difficulty is to do this for any formatter that uses templates. (Unification)

I have a question. if I create a extension for the Plates (Equip specific), in which namespace I define them?
Maybe for the Plates to make a separate repository?

Looks like this PR needs merge conflicts resolved. Overall, though, I like the idea of moving status handling to a separate responder and agree it makes for much cleaner and less coupled code.

@AlexMasterov please open a new PR, the parent #39 has been merged into the dev branch. Thanks!


SQLFile :: Dbms validation check added

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
dbms property for SQLFile change was not being validated, and this was causing an invalid behavior apparently changeset was being successfully deployed (an entry was added into the DBCL table), but since the specified database short name was not valid, nothing was being deployed in the DB.
Fixes #6484

Things to be aware of

Things to worry about

Additional Context

@filipelautert yeap if dmbs specified is not valid, it will throw a validation error saying that.


Cleanup of webhooks as part of the undeploy script

Recently we added undeploy task in the Makefile for removing the metallb operator
from the cluster.
However, the undeploy script does not remove the ValidatingWebhookConfiguration which
leaving the Validation Webhooks hanging in the cluster.
Also, a user who uses the webhook must have applied the cert-manager yamls, adding
the cert-manager namespace with all its resources, that are not being cleaned up as well.
Besides that, MetalLB's ValidatingWebhookConfiguration name is "validating-webhook-configuration"
which is generic and for customers with many ValidatingWebhookConfiguration resources it won't
be clear that the "validating-webhook-configuration" is for MetalLB, so I think it could be helpful
to have a more specific name like "metallb-validation-webhook"

Guess we can close this, as webhooks are now being deployed by metallb itself.


BUG: Signup and Login Pages Not Functioning Properly

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The signup and login pages on the website are currently experiencing issues. After filling out the form and submitting it, there is no response or action taken, leaving the user unable to proceed with the signup or login process. This prevents new users from creating accounts and existing users from accessing their accounts.
Please assign me this issue , I will create a pull request to make signup and login page working and also add appropriate label to my pull request.
Add ScreenShots

What browser are you seeing the problem on?
Microsoft Edge
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

@ratuladhikary21 , I am already working    on this ,please assign me with his

@Mansi168 ,you have written localhost url ,i will deploy your server and replace url of deployed server and login will work ,please assign me this issue,i will create pull request asap


Suppress notifications

I keep getting spammy notifications for Control Concealer.

Hey sorry for the late reply. I located the Button it keeps failing to find: It's Small Time. Unhiding the button seems to have resolved it.

Ok now I get the yellow one I change to any tab. I'm not getting any logs in the chat.

what dows it say?

Enhanced Terrain Layer is Prone to causing the yellow notifications to pop up any time any button is pressed.

This bug also bothered me.
I realized when looking through the code, that showing a blatant red error warning when something could NOT be fixed was a good notification to show to the user.
But I could not see the reason to display a yellow warning every time the module 'fixed' the error and things were just fine.  This seemed more like debug code that wasn't removed for production.  Something like this could be logged to the console instead.
So an easy fix for this, is to simply comment out one line of code.
//ui.notifications.warn(game.i18n.localize("CONTROLCONCEALER.warning.ControlMissmatchFixed"));
This suppressed all the redundant yellow warning labels for random modules that didn't want to behave together.
Enjoy!
if(hasControlMissmatch){
				if(hasUnfixedControlMissmatch){
					ui.notifications.error(game.i18n.localize("CONTROLCONCEALER.error.ControlMissmatch"));
				}else{
					//ui.notifications.warn(game.i18n.localize("CONTROLCONCEALER.warning.ControlMissmatchFixed"));
					await this.saveHiddenElements();
				}
			}

The warning is intentional. I wanted that users to notify me when that pops up so I can take a look and see if my logic is flawed somewhere.
With enough modules adding their buttons in weird ways I'm not sure how to handle I guess I should add a setting to opt out of the warning.

I totally understand.  It seemed more like a bit of debug code than anything.  Very helpful for the developer, not as much for the end user.  But either way, an opt out setting would be pretty nice to have in the future.
Figured I'd offer up a temporary solution to those who love the module (myself included), but didn't want to have the yellow warnings pop up non stop.
Thanks KayelGee!


[Feature Request]  create microservices based framework and loosely coupled and high cohesion for every plugin or module

Is your feature request related to a problem? Please describe.
Looking for community feedback...
Develop all modules in a micro architecture way:
References:
https://www.youtube.com/watch?v=mG9SvxnkKEY
(Im not sure if this is the right thing above but it seems to be.  I kind of have book knowledge of lots of this stuff and not street knowledge :)   )
So let me dig deeper into what I mean.  If we create integrations with cpanel, plesk, cyberpanel, whatever panel.  Or if we create ANY feature we do it loosely coupled with high cohesion and make each thing we create a stand along library able to be used by laravel community or since laravel is already loosely coupled anyone can use the lib.
https://medium.com/clarityhub/low-coupling-high-cohesion-3610e35ac4a6
Maybe micro arch is the wrong statement but above is what I mean.  If anyone can provide a name for it it would be helpful.
We would then shave all of them in composer or npm or github.
Describe the solution you'd like
Use https://laravel.com/docs/9.x/octane
Describe alternatives you've considered
Yes create a monolithic app.
Additional context
If ocatain and micoservices is different then loosely coupled/high cohesion let me know and ill split this.  That being said I think anyone would get my gist and I would be interested in libraries for laravel (or  framework documentation) that deals with this?

It doesn't make sense to publish an "Create" user account module to the public for "outside" use but it makes sense to have a public php api based system that can communicate to Cpanel, Directadmin, Plesk, Hestia or Whatever.
But there is not need to run Fossbilling on multiple smaller instances and we need to add communication layers inbetween. Keep it *** simple

ok so then a standardized api in front of a Cpanel, Directadmin, Plesk, Hestia or Whatever. pluginized library ...am i getting that right?

There is no standaard API for Cpanel, Plek, Directadmin and creating really doesn't make sense because the can always change.

i think thats the point, how do you think the api i mentioned does it, but yeah you dont want it hidden behind a service thats a valid point, but saying you cant do a standard api is imho not 100% true, all it is is a api wrapper with a singular api schema around multiple code modules for each provisioning software.

sorry i mentioned the standarized api for shopping carts elsewhere, but this is what i mean, an example of what i mean:
https://api2cart.com/
See this: https://docs.api2cart.com/post/interactive-docs?version=v1.1

I'm not aware of any kind if standard API for control panels, and expecting us to create and maintain one is effectively another project entirely and restructuring FOSSBilling to work with it.
As it stands, only 4 of the server managers are known to work (CPW, HestiaCP, Plesk, and cPanel).
Of these, the only one I know that's being actively maintained is HestiaCP, possibly Plesk. Most contributors aren't even using FOSSBilling for anything (yet), let alone using it with one of the existing control panels and maintaining the server manager for it.
Such a project would be quite cool, if there were other OSS projects that would benefit from it, but I really don't think there are more than a very small handful.
Potentially paid software like WHM would have a use for them, but again, they would need to update their software to work with it, and potentially cause issues with existing server managers that are written for them.
I'm going to close this as not planned, if someone on the team disagrees with me, feel free to speak up / re-open this issue.


docs: Add test specifications for AccountAllowanceDeleteTransaction

Description:
This PR adds the test specifications for AccountAllowanceDeleteTransaction fields.
Related Issue(s):
Fixes #27
Notes for Reviewer(s):
This PR contains work in #279 so that should be reviewed and merged first.
Checklist

[x] Documented (Code comments, README, etc.)
[x] Tested (unit, integration, etc.)

AccountAllowanceDeleteTransaction has several deprecated methods. Also in a lot of places you are saying approves and not deletes. Overall this flow should be revisited.

I guess I got lazy with my copy-pasting! DeleteAllTokenNftAllowances should be the only function tested as it is the only function provided by this API. I removed the other functions.
There are deprecated methods but these only make modifications to local class variables that don't ever actually get sent to the network. I didn't think these were necessary to test.


FindMatchingInterpreter matching on interpreter path

Noticed this in a semi-related PR here.
https://github.com/microsoft/vscode-jupyter/pull/5644#pullrequestreview-646103184
In FindMatchingInterpreter it's matching based on the path of the interpreter. I believe this might be an issue as "Interpreters" here is actually PythonEnvironments, and for Conda I believe you can have multiple environments with the same interpreter path if you don't specify the python version when creating the env.

We need to rethink how we uniquely identify PythonEnvironments.

We should add telemetry to see how many users fall into this category. Not necessary for June though.

Repro for this.
Create a conda env. Then you can create named conda kernelspec like this:
(dupe1) Ians-MacBook-Pro:~ ianhuff$ python -m ipykernel install --user --name dupeEnvUno --display-name "Dupe Env Uno"
Installed kernelspec dupeEnvUno in /Users/ianhuff/Library/Jupyter/kernels/dupeenvuno
(dupe1) Ians-MacBook-Pro:~ ianhuff$ python -m ipykernel install --user --name dupeEnvDos --display-name "Dupe Env Dos"
Installed kernelspec dupeEnvDos in /Users/ianhuff/Library/Jupyter/kernels/dupeenvdos
These will all get startUsingPythonInterpreter kernelConnectionMetadata and they will all have the same path. Find preferredKernel in helpers.ts matches only on path in a couple of places. If using old webview you run with "Dupe Env Uno" and save the file. The next time you open it you might get your kernel switched to the main conda env (dupe1) or "Dupe Env Dos" it's all ordering dependent.
The interactive window part usually works since the current interpreter is first in the list, so it usually gets matched before the other ones, but that is ordering dependent to some degree as well.

These are just completely skipped now. Seems wrong to me? Kernelspec might have a custom env.

This works fine if the custom kernelspecs are any different than the default kernelspec.


ShardPositionsUpdate event handler timed out

2023-12-11T02:05:21.913Z  WARN quickwit_common::pubsub: quickwit_proto::indexing::ShardPositionsUpdate event handler timed out
Happens regularly when running the
./target/release/quickwit-simian-army "chico(rate=1000000)*20" "chico(rate=100000)*20" "chico(rate=12000000)" "chico(rate=20000000)" --endpoint localhost:7280

Here is what we get when it happens.
ub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:12.520Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:12.629Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:12.892Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:13.040Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:13.225Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:13.322Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:13.646Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:13.924Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:14.225Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:14.231Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:14.281Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:14.321Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:14.391Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:33.562Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:42.615Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:44.286Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:44.346Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:44.387Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:45.285Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:45.395Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:45.395Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:45.468Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
2023-12-11T03:27:45.811Z  WARN quickwit_common::pubsub: `quickwit_proto::indexing::ShardPositionsUpdate` event handler "quickwit_ingest::ingest_v2::ingester::WeakIngesterState" timed out
^C2023-12-11T03:27:51.949Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:51.968Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:51.993Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:51.996Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.019Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.021Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.045Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.045Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.045Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.046Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.046Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.046Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.046Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.046Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.046Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.047Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.047Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.047Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.047Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.047Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.047Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.053Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.054Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.060Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.063Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.069Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.071Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.086Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.097Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.106Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.128Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.129Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.129Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.129Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.129Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.426Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.439Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.439Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.439Z ERROR quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.919Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.919Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available
2023-12-11T03:27:52.920Z  WARN quickwit_ingest::ingest_v2::router: failed to get open shards from control plane: control plane is unavailable: no ingester available

Acquire the lock  in the impl EventSubscriber<ShardPositionsUpdate> for WeakIngesterState { can take 1s.
2023-12-11T04:54:04.768Z  WARN quickwit_ingest::ingest_v2::ingester: elapsed elapsed=978.99875ms

Created a PR to increase the timeout to 20s with a warn log. Assigning to @guilload to investigate if this is normal or if this should be fixed.


Incorrect text for CLI help output for terminal rows and columns

When using --help for several devcontainer commands, the description for rows and columns seems to be mixed up:
  --terminal-columns              Number of rows to render the output for. This is required for some of the subprocesses to correctly render their output.  [number]
  --terminal-rows                 Number of columns to render the output for. This is required for some of the subprocesses to correctly render their output.  [number]

It would seem that --terminal-columns should reference columns instead of rows as shows above. ...and vice versa.

Hi 👋
Thanks for catching this error, it looks like a mixup to me as well.


OpenROAD regressions with boundary checks [-Wp,-D_GLIBCXX_ASSERTIONS]

There are no failing regressions on latest a1cd122fe9bf2e6cb7b2b05be43c50dc5599d8f2 (2022/04/10) unless boundary checks are enabled.
Suggestions:

for the betterment we could try enable -Wp,-D_GLIBCXX_ASSERTIONS compile flags and lets start investigate each failure.

boundary check enabled environment also help daily development process acting as an immediate guard against odd things.

as releng practice, boundary check is mandatory & enforced by default on all packages in distros like RHEL / Fedora.

Observations:

In contrast with OpenROAD, OpenSTA's regressions with boundary checks are fine (as for now).

(x) Enabling boundary checks reveals these:
$ cat openroad-cxx-on.log | grep -e ERROR
pd1 *ERROR*
gcd_mem1_01 *ERROR*
gcd_mem1_02 *ERROR*
gcd_mem1_03 *ERROR*
gcd_mem3_01 *ERROR*
gcd_mem3_02 *ERROR*
gcd_mem3_03 *ERROR*
gcd_mem5_01 *ERROR*
level3_01 *ERROR*
level3_02 *ERROR*
east_west1 *ERROR*
east_west2 *ERROR*
snap_layer1 *ERROR*
repair_slew12 *ERROR*
repair_antennas1 *ERROR*
repair_antennas2 *ERROR*
repair_antennas3 *ERROR*
sw130_random *ERROR*
sw130_random_simple *ERROR*
gcd *ERROR*
45_gcd *ERROR*

(x) All the above fails due to boundary issues, e.g:
$ cat src/rcx/test/results/45_gcd.log  | grep Asser
/usr/include/c++/12/bits/stl_vector.h:1122: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>:
:operator[](size_type) [with _Tp = odb::tmg_rc; _Alloc = std::allocator<odb::tmg_rc>;
reference = odb::tmg_rc&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.

The documentation is way too summary, it covers more than enlisted there.
A little sample (e.g. on a generic std::vector) on how boundary checks works:
$ cat test1.cpp
#include <vector>
#include <cstdio>

int main()
{
    std::vector<int> v = { 7, 5, 16, 8 };
    printf("v[-1] = %i\n", v[-1]);
}

$ cat test2.cpp
#include <vector>
#include <cstdio>

int main()
{
    std::vector<int> v = { 7, 5, 16, 8 };
    printf("v[4] = %i\n", v[4]);
}

It runs, doesn't fail:
$ c++ test1.cpp -o test1; ./test1
v[-1] = 0

$ c++ test2.cpp -o test2; ./test2
v[4] = 0

Now failures are guaranteed:
$ c++ test1.cpp -Wp,-D_GLIBCXX_ASSERTIONS -o test1; ./test1
/usr/include/c++/12/bits/stl_vector.h:1122: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>
::operator[](size_type) [with _Tp = int; _Alloc = std::allocator<int>; reference = int&;
size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Aborted (core dumped)

$ c++ test2.cpp -Wp,-D_GLIBCXX_ASSERTIONS -o test2; ./test2
/usr/include/c++/12/bits/stl_vector.h:1122: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>
::operator[](size_type) [with _Tp = int; _Alloc = std::allocator<int>; reference = int&;
size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Aborted (core dumped)

Cc @maliberty
Thanks,
~cristian.

We should definitely fix the issues this flag catches.  However it will have a runtime performance cost.  Are you saying every release package has this flag on all the time, not just during development?

We should definitely fix the issues this flag catches.

I will try involve and PR some of enumerated regression fixes when time permits.

However it will have a runtime performance cost.

IMHE  for GLIBCXX_ASSERTIONS the cost isn't noticeable, compilers do a great job "hiding it".
There is a discuss on it's performance concerns here: https://www.spinics.net/lists/fedora-devel/msg257877.html

Are you saying every release package has this flag on all the time, not just during development?

YES absolutely all released production .rpm packages in rhel/fedora land contains it (ever since such flags exists).

Using it even in final releases allows catching complete new uncovered bugs from the very users.

Some more (offtopic) details:

In RHEL land these are the mandatory flags (even many more) involved:

$ rpm --eval %{optflags}
-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS  -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64  -mtune=generic
-fasynchronous-unwind-tables  -fstack-clash-protection -fcf-protection

A documentation of them is here .
Beyond  GLIBCXX_ASSERTIONS there are: stack-smash, origin-annotations, lto and some more.
The very GLIBCXX_ASSERTIONS is a built-in type, it's absence cannot be "negociated" with releg team :)

Thanks,
~cristian.

I've fixed a bunch of these (https://github.com/The-OpenROAD-Project/OpenROAD/pull/1765).  The last all seem to come down the tmg* code which is really bad code in odb.  Maybe its time to finally clean it up as fixing anything in there is excruciating.

@cbalint13 do you recommend that we also enable this for https://github.com/hdl/conda-eda/tree/master/pnr/openroad? maybe that could be something enable for CMake for all Release build?

@cbalint13 do you recommend that we also enable this for https://github.com/hdl/conda-eda/tree/master/pnr/openroad? maybe that could be something enable for CMake for all Release build?

@proppy ,
You can for all else but not for openroad ,I suggest not yet, until all regression tests pass.

For RHEL / Fedora opernroad native packages I had to disable it.
See disabling receipt line 81: https://copr-dist-git.fedorainfracloud.org/cgit/rezso/VLSI/openroad.git/tree/openroad.spec#n81

With it, openroad will fail on simple designs (e.g. the spm form openlane) at antenna-checking step.
It's enabled everywhere else (in that repo) except the openroad package.

@cbalint13 cvc issues should be filed at https://github.com/d-m-bailey/cvc

All designs pass but some of the ISPD routing benchmarks have issues that need looking into.

All designs pass but some of the ISPD routing benchmarks have issues that need looking into.

Nice ! That was very fast :)
Maybe offtopic (again), IMHO it't worth watching progress on -fanalyser in GCC Land .


Add a comfortable way to search filenames with regex etc. support

This issue: https://github.com/microsoft/vscode/issues/127723 got closed even though people support it, few more got closed after, so creating a new one.
I don't know how this isn't a feature already - most, even basic editors like Notepad++, can search filenames fairly easily. Searches in VSCode are generally very lacking in comparison to other features, however, this is the worst - searching for names right now:

is uncomfortable and rather hidden
doesn't support basics like regexes

Rejecting adding this to search panel because of complexity is nonsense, you can always hide additional options under some Advanced options dropdown if needed.

https://github.com/microsoft/vscode/issues/127723#issuecomment-881711911
To add to this, we use ripgrep to search through files, which uses globs to filter out files. Something like this would require changes on upstream dependencies, which we do not plan on doing soon for this case.


Ignore files that have a null byte

Cross-linking rollup/rollup-plugin-commonjs#268
rollup-plugin-commonjs generates a file with a null byte called \u0000commonjsHelpers.  This causes fs.stat to fail via the path here (with long paths shortened to ...):
    at nullCheck (fs.js:173:16)
    at Object.fs.stat (fs.js:947:8)
    at FSWatcher.NodeFsHandler._addToNodeFs (.../node_modules/chokidar/lib/nodefs-handler.js:447:20)
    at FSWatcher.<anonymous> (.../node_modules/chokidar/index.js:622:12)
    at .../node_modules/async-each/index.js:16:7
    at Array.forEach (<anonymous>)
    at each (.../node_modules/async-each/index.js:15:11)
    at FSWatcher.add (.../node_modules/chokidar/index.js:621:5)
    at buffer.forEach.m (.../node_modules/karma-rollup-preprocessor/lib/index.js:69:15)

There is probably a better way, but the best I can figure is karma-rollup-preprocessor is the easiest place to fix this, by simply checking for the presence of a null byte before adding a file to the watch list.  If a filename has a null byte, ignore it.
A better solution would to be to not have filenames generated in plugins and injected into the watch list, but I'm sure there's a good reason for that.
The test is just if (m.includes('\u0000')) { return } inside the respective forEach functions at Watch.prototype.start and Watch.prototype.clean.
Generally it's considered a security issue if a filename has a null byte, and disallowed in many languages (e.g. Python), so I expect it's a safe change. See eg https://security.stackexchange.com/a/45958/2914

Interesting, thanks @brianmhunt
So let's see if I understand—null bytes are a security concern for karma-rollup-preprocessor, but the patch would also serve as a downstream fix for an emergent bug in rollup-plugin-commonjs?

So let's see if I understand—null bytes are a security concern for karma-rollup-preprocessor, but the patch would also serve as a downstream fix for an emergent bug in rollup-plugin-commonjs?

Yes, that is my understanding.


The sharding does not work when call gorm.Create method!

GORM Playground Link

https://github.com/go-gorm/playground/pull/1
Description
Recently, I test sharding plugin and try to intergate it in my project. However, it fail the tests when I run the example in https://github.com/go-gorm/sharding/tree/main/examples/order.go.
The only difference is the database driver. I replace postgres to mysql.
enviroment:
OS: WSL1 for Win10
Go: go version go1.17.6 linux/amd64
Package:
	gorm.io/driver/mysql v1.2.3
	gorm.io/gorm v1.22.5
	gorm.io/sharding v0.4.0

The following is the error message:
2022/02/21 09:19:34 ~/main.go:67 Error 1146: Table 'gorm.orders' doesn't exist
[19.048ms] [rows:0] INSERT INTO `orders` (`user_id`,`product_id`) VALUES (2,0)
Error 1146: Table 'gorm.orders' doesn't exist

and the code:
// this record will insert to orders_02
	err = db.Create(&Order{UserID: 2}).Error
	if err != nil {
		fmt.Println(err)
	}
```go

Apparently, the sharding policy does not work. It try to insert new record in `orders` not `orders_2`.

Please upload your main.go file, I need checkout it.

Please upload your main.go file, I need checkout it.

@huanlee, I appreciate your quick response to the issue. And the fowllowing is test code.
Go Mod file
module dbmid

go 1.17

require (
	gorm.io/driver/mysql v1.2.3
	gorm.io/gorm v1.22.5
	gorm.io/sharding v0.4.0
)

require (
	github.com/bwmarrin/snowflake v0.3.0 // indirect
	github.com/go-sql-driver/mysql v1.6.0 // indirect
	github.com/jinzhu/inflection v1.0.0 // indirect
	github.com/jinzhu/now v1.1.4 // indirect
	github.com/longbridgeapp/sqlparser v0.3.1 // indirect
)

main.go :
package main

import (
	"fmt"

	"gorm.io/driver/mysql"
	"gorm.io/gorm"
	"gorm.io/sharding"
)

type Order struct {
	ID        int64 `gorm:"primarykey"`
	UserID    int64
	ProductID int64
}

func main() {
	db, err := gorm.Open(mysql.Open(
		"gorm:gorm@tcp(<IP_ADDRESS>:9911)/gorm?charset=utf8&parseTime=True&loc=Local"),
		&gorm.Config{PrepareStmt: true})
	if err != nil {
		panic(err)
	}

	middleware := sharding.Register(sharding.Config{
		ShardingKey:         "user_id",
		NumberOfShards:      4,
		PrimaryKeyGenerator: sharding.PKSnowflake,
	}, "orders")
	db.Use(middleware)

	// this record will insert to orders_02
	err = db.Create(&Order{UserID: 2}).Error
	if err != nil {
		fmt.Println(err)
	}
}

Remove PrepareStmt option


Improved error message when no spec found.

Very minor flaw I encountered during testing: As target_cls is typically a type. It would print <class 'type'> which is not very informative.

I just realized, I based this PR on the deepcopy branch. Sorry for that.

Merged as part of another PR: https://github.com/anikolaienko/py-automapper/pull/12


[Bug fix]Update docker_compose.rst

Signed-off-by: LF<EMAIL_ADDRESS>

Type of change

Bug fix

Description

Add tabs before every service, fix ERROR: In the file './docker-compose.yaml', service must be a mapping, not a NoneType. after running the docker-compose up ca-tls command.
Additional details

Related issues

@fabric-core-doc-maintainers Hello, could you review this change?thanks~

Thanks!


[HMR] setInterval calls keep stacking when a module is reloaded

Describe the bug
I have a function I would like to call periodically so I initialize a setInterval loop in interval.ts by importing handle in hooks.server.ts. The return value from setInterval is exported as handle. The bug is that whenever the console.log is updated, the output in the console shows there are two setInterval loops running. This output keeps stacking as more changes are made and more HMR updates are triggered. For example, if you update the runAsync(1) call to runAsync(2) you will see the following console output:
tick 1
tick 2
tick 1
tick 2
tick 1
tick 2

I tried using import.meta.hot in interval.ts with a dispose following accept(), as well as others like invalidate and on('vite:beforeUpdate', ...) but this behavior persisted or at best the first loop was the only one that kept running after HMR updates.
This is all running using npm run dev. Am I doing something wrong with import.meta.hot or is there another way to cleanup the previous loop?
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-2xzaqm?file=src%2Flib%2Fserver%2Finterval.ts
Logs
No error logs were produced

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^3.0.0 => 3.2.4
    @sveltejs/kit: ^2.0.0 => 2.5.24
    @sveltejs/vite-plugin-svelte: ^3.0.0 => 3.1.2
    svelte: ^4.2.7 => 4.2.19
    vite: ^5.0.3 => 5.4.2

Severity
serious, but I can work around it
Additional Information
Reproduced using the SvelteKit template on StackBlitz.

Also come up with the same issue. It seems hooks.server.ts is never called with import.meta.hot, therefore one could not do:
let interval = undefined;

if (dev) {
  interval = setInterval(()=>{
    console.log('pong');
  },1000);
}

if (import.meta.hot) {
   import.meta.hot.dispose(()=> {
   if ( interval !== undefined ) {
     clearInterval(interval);
     interval = undefined;
   }
}

Which seems from svelte-hmr the way to go for disposing resource on HMR events.

Definitely related to #11932

Agreed it looks related. That issue has been open for some time now, so is there any ETA when it will be looked at?


CDAP-15627: Added support of clustering in BigQuery Sink plugin.

JIRA: https://issues.cask.co/browse/CDAP-15627
In scope of this PR:

Added support of clustering in BigQuery Sink plugin.

@albertshau could you, please, take a look

@nitinmotgi what do you mean by an ordering list? The csv widget? Users would still have to type the field names though.
I see in https://docs.cdap.io/cdap/6.0.0/en/developer-manual/pipelines/developing-plugins/presentation-plugins.html#H2651 that there's an input-field-selector, but not one for selecting multiple input fields. @ajainarayanan is there a widget for this that isn't documented?

@albertshau @nitinmotgi We don't have a way to allow users to select multiple fields from input schema. Right now we only allow users to select one field (input-field-selector). We would need to build this component if we need it.

@albertshau I addressed all your comments, could you, please, take a look.

My point is we should not have them to type input fields. We should have a
widget that allows them to select and order
On Fri, Jul 12, 2019 at 2:37 PM albertshau<EMAIL_ADDRESS>wrote:

@nitinmotgi https://github.com/nitinmotgi what do you mean by an
ordering list? The csv widget? Users would still have to type the field
names though.
I see in
https://docs.cdap.io/cdap/6.0.0/en/developer-manual/pipelines/developing-plugins/presentation-plugins.html#H2651
that there's an input-field-selector, but not one for selecting multiple
input fields. @ajainarayanan https://github.com/ajainarayanan is there
a widget for this that isn't documented?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/data-integrations/google-cloud/pull/127?email_source=notifications&email_token=AAKNPHZDR6EFTO4ZT3CBNDDP7D2TJA5CNFSM4ICL4MDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ26BLA#issuecomment-511041708,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKNPH2SPIZCXOILHZSML2DP7D2TJANCNFSM4ICL4MDA
.

@nitinmotgi @ajainarayanan https://issues.cask.co/browse/CDAP-15646. It's not possible today, the plugin can change when there is support

@albertshau I made final changes and squashed the commits.


Spacing of Table Headers

I have found when you have many columns > 10 that the headers for the columns overflow the header. I have scrollbarH on as well, expecting it to allow scrolling over to those off the page columns.

Can you make a repo? Thats odd because there is a example of scrollbars in both scenarios like that.

Yea, I am trying to fork the plunker you have for those and seeing if I can make it do the same.

I fixed it on my end, it had nothing to do with code persay but how I was initializing that code. I will have relook up the exact solution.


Adding 2020 Linux Kernel Security Review

Adding 2020 Review of the Linux Kernel’s Vulnerability Reporting and Remediation to Project Security Reviews repo

Thanks @Amir-Montazery ! We're actually using a repo within ossf, I'll merge here and then copy over there. Sorry for the confusion!


streamlink: 1.5.0 -> 2.0.0

https://github.com/streamlink/streamlink/releases/tag/2.0.0
https://github.com/streamlink/streamlink/compare/1.5.0...2.0.0

Motivation for this change
Noticed it was more than 6 months out of date, so I figured I'd update it.
Be aware that 2.0.0 contains many breaking changes. Read the changelog (above) to determine how this affects you.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

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

2 packages built:

streamlink
streamlink-twitch-gui-bin

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

2 packages built:

streamlink
streamlink-twitch-gui-bin

Just a test.
/marvin opt_in
/status needs-merger

Just a test.
/marvin opt_in
/status needs-merger

@cole-h Could you also update streamlink-twitch-gui-bin :thinking: ?
https://github.com/streamlink/streamlink-twitch-gui/releases/tag/v1.11.0

@cole-h Could you also update streamlink-twitch-gui-bin :thinking: ?
https://github.com/streamlink/streamlink-twitch-gui/releases/tag/v1.11.0

I prefer to have my package bumps focused only on the specified package, but I guess I can make an exception this time. Done.

I prefer to have my package bumps focused only on the specified package, but I guess I can make an exception this time. Done.

@cole-h If you want to increase your chances for your PR to be merged, you can use: https://github.com/timokau/marvin-mk2/blob/master/USAGE.md

@cole-h If you want to increase your chances for your PR to be merged, you can use: https://github.com/timokau/marvin-mk2/blob/master/USAGE.md


Validate multiple values for account name in AH API

Definition of Ready

[ ] Does this meet the INVEST criteria?
[ ] Does this have a clearly defined user?
[ ] Does this have an estimate?
[ ] Does this have acceptance criteria?
[ ] Does this have sufficient context (wireframes, business rules, etc.)?
[ ] Is this traceable to a feature, epic, or PI?

User Story
As a CAMPD API user I want to enter valid filter criteria for multiple account names so that I can see results
Acceptance Criteria
Given that a user has entered filter criteria for account name
When the API endpoint is executed
Then the system validates:
Validate that the text matches a valid account name
Given that a user has entered one or more account names in an upper-case or lower case format
When the API endpoint is executed
Then the system displays the records that match the criteria (containing data elements below)
Given that a user has entered one or more account names without white space(s) before or after the delimiter
When the API endpoint is executed
Then the system displays the records that match the criteria (containing data elements below)
Given that a user has entered one or more account names with white space(s) before or after the delimiter
When the API endpoint is executed
Then the system displays the records that match the criteria (containing data elements below)
Given that a user has entered one or more invalid parameters for account name
When the API endpoint is executed
Then the system displays error message: TBD
Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Testing
Test Case:
Tester:
Data Elements
Query results will include:
ACCOUNT_NUMBER
ACCOUNT_NAME
ORISPL_CODE
PRG_CODE
VINTAGE_YEAR
TOTAL_BLOCK
START_BLOCK
END_BLOCK
STATE
EPA_REGION
OWN_DISPLAY
ACCOUNT_TYPE
Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Has the user story been accepted by the Product Owner?
[ ] Is the user story ready to be deployed to the test/staging environments?

During sprint planning on 3/17 the team decided to complete the AH API by creating tickets #972, #973, #974, #975


Change eventhub to accept byte array as input

Change eventhub datawriter to be byte array type as input format


Governance. Multisig operations. There is no default message for Vote / Remove Vote

Description
Expected Behavior
?
Actual Behavior

Environment
https://github.com/novasamatech/nova-spektr/commit/023df867e4ea11596d331f02f572caada4bbeaf6

For the transition period (before we implement Multisig without Matrix) the following default Description may be used: Remove votes for referendum #referendum index


Allow passing additional command line options to pt-online-schema-change

We needed this since in our somewhat complicated slave and replication setup to change the bahaviour of pt-online-schema-change so it works correctly.
This may also be handy for other circumstances.

Have you considered solving this by using configuration files for pt-online-schema-change? Some arguments to pt-online-schema-change require quoting, which I think could get complicated.
You can see an example of a config file in pt-online-schema-change.cnf

As far as I can see using a configuration file also requires specifying this file via command line. Correct me if I am wrong.

Yes, you'll always need some way to manipulate the command line.
I see basically two ways:

provide a environment variable liquibase.percona.configurationFile - which the plugin then passes on as --config xyz
provide a more generic way for additional parameters, like you suggested: liquibase.percona.options.

I'd prefer the second option, as it is more flexible. In order to use this for providing a configuration file, the additional options need to be passed as the first arguments, so that --config is the first argument on the command line. See also Specifying configuration file
Do you think, it would be a problem, if these additional options would be passed first? (E.g. before the --alter argument, see line 60)

@adangel I updated the pull request as you proposed.

Thanks @hseffler!
I've adjusted it a little bit in order to handle specific cases with multiple options and spaces.
Would you mind downloading the latest version liquibase-percona-1.2.1-SNAPSHOT and let me know, if it works?

Am updating our setup right now, will comment once we used it again with using the options. Should be soonish.


Is the m1 version available?

Is monitorcontrol available for m1 macs?

Hello, indeed support for MacBookPro M1 is needed.

See #323

Thanks @JoniVR. It looks all is perfectly tracked. Great.


Added py_test - an entry point for running the cdf code from a jupyter notebook

And fixed two bugs in sampling and resampling a cdf

Looks good, thanks!
Can you please add a few comments in the py_test file to describe what it is & how to use it?


The message file for category 'yii' does not exist

I have many errors in log file:
The message file for category 'yii' does not exist: ...vendor/yiisoft/yii2/messages/en-GB/yii.php Fallback file does not exist as well: ...vendor/yiisoft/yii2/messages/en/yii.php

Yii (2.0.7) $language is en-GB.
I have already seen that @SilverFire has been already fixed (#7964).

do you get this error with yii 2.0.7 ?

Yes.

Well, we do not have translations for en-GB as well as for en:
https://github.com/yiisoft/yii2/tree/master/framework/messages
They are considred as not necessary ones.
If you wish to avoid error messages in logs, you should configure sourceLanguage to be en-GB.

I already set this in config:
``
'language'  => 'en-GB',
'sourceLanguage' => 'en-GB'
but errors happened.

what does your message source config look like, i.e. i18n component config.

'i18n' => [
      'translations' => [
        'app*' => [
          'class' => 'yii\i18n\PhpMessageSource',
          'basePath' => '@app/messages',
          'sourceLanguage' => 'en-GB'
        ]
      ]
    ]

I already tried to comment this config.

Resolved by https://github.com/yiisoft/yii2/commit/c3c0d04f5bc58c5ad08da13797e27d956ebec043


export page data from db

Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check (rat-check) on project commons-csv: Execution rat-check of goal org.apache.rat:apache-rat-plugin:0.13:check failed: Plugin org.apache.rat:apache-rat-plugin:0.13 or one of its dependencies could not be resolved: Could not transfer artifact commons-collections:commons-collections:jar:3.2.2 from/to google-maven-central (https://maven-central.storage-download.googleapis.com/maven2/): GET request of: commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar from google-maven-central failed: Connection reset

Coverage decreased (-4.8%) to 88.385% when pulling 1bf86bfbc7df0098d7360f975069d6516edbf32b on shootercheng:master into e503c568a10ae42364a94695b8505bcb4db28969 on apache:master.

Coverage decreased (-1.3%) to 91.879% when pulling f98dfe2 on shootercheng:master into e503c56 on apache:master.

所有的方法都测试了，这个覆盖率检测有bug

This ticket has no description so I have no idea what the intent is here. The lack of Javadoc does not help either.

今天添加JavaDoc ，实现分页查询导出数据库的数据到 CSV
---Original---
From: "Gary<EMAIL_ADDRESS>Date: Sat, Feb 22, 2020 21:06 PM
To<EMAIL_ADDRESS>Cc: "Comment"<comment@noreply.github.com>;"James<EMAIL_ADDRESS>Subject: Re: [apache/commons-csv] export page data from db (#58)
This ticket has no description so I have no idea what the intent is here. The lack of Javadoc does not help either.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

intent

This ticket has no description so I have no idea what the intent is here. The lack of Javadoc does not help either.

you can see the method DbQueryExportTest.testExport(),  this test method will export querying page data from db

intent

This ticket has no description so I have no idea what the intent is here. The lack of Javadoc does not help either.

you can see the method DbQueryExportTest.testExport(), this test method will export querying page data from db

@shootercheng
I'm sorry so say that you're not helping your PR here :-( You should provide some kind of description for this PR so that people can learn what problem this PR attempts to solve and how. This would then allow reviewers to try to understand if this code belongs here and how it can fit in. I suppose you could fill in the Javadoc at a later phase of your development (but before any merge into Commons CSV.)
If you want to export database rows, you can use org.apache.commons.csv.CSVPrinter.printRecords(ResultSet) which works with Java's own JDBC framework. The printer class also provides other types of services to create CSV files.
More importantly, I see zero reuse of Commons CSV's code for which this PR seems to duplicate features like using your ExportParam instead of CVS's CSVFormat. It seems this PR is complete;y standalone code from Commons CSV since it does not reuse any of Commons CSV's code. Why would it belong within Commons CSV?

intent

This ticket has no description so I have no idea what the intent is here. The lack of Javadoc does not help either.

you can see the method DbQueryExportTest.testExport(), this test method will export querying page data from db

@shootercheng
I'm sorry so say that you're not helping your PR here :-( You should provide some kind of description for this PR so that people can learn what problem this PR attempts to solve and how. This would then allow reviewers to try to understand if this code belongs here and how it can fit in. I suppose you could fill in the Javadoc at a later phase of your development (but before any merge into Commons CSV.)
If you want to export database rows, you can use org.apache.commons.csv.CSVPrinter.printRecords(ResultSet) which works with Java's own JDBC framework. The printer class also provides other types of services to create CSV files.
More importantly, I see zero reuse of Commons CSV's code for which this PR seems to duplicate features like using your ExportParam instead of CVS's CSVFormat. It seems this PR is complete;y standalone code from Commons CSV since it does not reuse any of Commons CSV's code. Why would it belong within Commons CSV?

之前使用过 printRecords(ResultSet) 去导出 csv 数据，但是数据量比较大的时候，导出有问题，所以我就加了这个导出方法，确实好像可以单独出来建一个工程了，不过放在这里也没啥问题呀，增强了原来的导出功能呀

I am so sorry , I have closed it.
---Original---
From: "Gary<EMAIL_ADDRESS>Date: Sun, Feb 23, 2020 11:02 AM
To<EMAIL_ADDRESS>Cc: "Mention"<mention@noreply.github.com>;"James<EMAIL_ADDRESS>Subject: Re: [apache/commons-csv] export page data from db (#58)
intent
This ticket has no description so I have no idea what the intent is here. The lack of Javadoc does not help either.
you can see the method DbQueryExportTest.testExport(), this test method will export querying page data from db
@shootercheng
I'm sorry so say that you're not helping your PR here :-( You should provide some kind of description for this PR so that people can learn what problem this PR attempts to solve and how. This would then allow reviewers to try to understand if this code belongs here and how it can fit in. I suppose you could fill in the Javadoc at a later phase of your development (but before any merge into Commons CSV.)
If you want to export database rows, you can use org.apache.commons.csv.CSVPrinter.printRecords(ResultSet) which works with Java's own JDBC framework. The printer class also provides other types of services to create CSV files.
More importantly, I see zero reuse of Commons CSV's code for which this PR seems to duplicate features like using your ExportParam instead of CVS's CSVFormat. It seems this PR is complete;y standalone code from Commons CSV since it does not reuse any of Commons CSV's code. Why would it belong within Commons CSV?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Google translate says:

I have used printRecords (ResultSet) to export csv data before, but when the amount of data is relatively large, there is a problem with the export, so I added this export method, and it seems that it can be built separately, but there is nothing here Problem, enhanced the original export function

I do not see enhancements in this PR that has anything to do with JDBC. What am I missing?

Google translate says:

I have used printRecords (ResultSet) to export csv data before, but when the amount of data is relatively large, there is a problem with the export, so I added this export method, and it seems that it can be built separately, but there is nothing here Problem, enhanced the original export function

I do not see enhancements in this PR that has anything to do with JDBC. What am I missing?

ResultSet is very primitive, we do not use JDBC in web projects

Google translate says:

I have used printRecords (ResultSet) to export csv data before, but when the amount of data is relatively large, there is a problem with the export, so I added this export method, and it seems that it can be built separately, but there is nothing here Problem, enhanced the original export function

I do not see enhancements in this PR that has anything to do with JDBC. What am I missing?

ResultSet is very primitive, we do not use JDBC in web projects

How do you extract data from your database? Hibernate?

Google translate says:

I have used printRecords (ResultSet) to export csv data before, but when the amount of data is relatively large, there is a problem with the export, so I added this export method, and it seems that it can be built separately, but there is nothing here Problem, enhanced the original export function

I do not see enhancements in this PR that has anything to do with JDBC. What am I missing?
Please see my demo project for export page data from db, it takes less time
https://github.com/shootercheng/batch/tree/export
21:19:59.967 [main] DEBUG com.single.batch.mapper.BatchLabelMapper.selectPage - ==>  Preparing: select concat_ws(',', id, ifnull(parent,''), ifnull(code,''), ifnull(status,''), ifnull(type,''), ifnull(customer_id,''), ifnull(operator_id,''), ifnull(reseller_id,''), ifnull(user_id,''), ifnull(product_id,''), ifnull(batch,''), ifnull(query_times,''), ifnull(first_time,''), ifnull(create_time,''), ifnull(update_time,'') ) from label_1 limit ?,?  21:19:59.968 [main] DEBUG com.single.batch.mapper.BatchLabelMapper.selectPage - ==> Parameters: 990000(Integer), 10000(Integer) 21:20:01.126 [main] DEBUG com.single.batch.mapper.BatchLabelMapper.selectPage - <==      Total: 10000 21:20:01.131 [main] DEBUG org.apache.ibatis.transaction.jdbc.JdbcTransaction - Resetting autocommit to true on JDBC Connection [com.mysql.cj.jdbc.ConnectionImpl@59309333] 21:20:01.131 [main] DEBUG org.apache.ibatis.transaction.jdbc.JdbcTransaction - Closing JDBC Connection [com.mysql.cj.jdbc.ConnectionImpl@59309333] time 64218 ms

time 64218 ms
https://github.com/shootercheng/batch/tree/export
How to use JDBC  in this demo web project? You should add more base code.Show me wasting less time for using commons-csv !

Google translate says:

I have used printRecords (ResultSet) to export csv data before, but when the amount of data is relatively large, there is a problem with the export, so I added this export method, and it seems that it can be built separately, but there is nothing here Problem, enhanced the original export function

I do not see enhancements in this PR that has anything to do with JDBC. What am I missing?

time 64218 ms
https://github.com/shootercheng/batch/tree/export
How to use JDBC in this demo web project? You should add more base code.Show me wasting less time for using commons-csv !

If you are looking for help on how to use JDBC, then start here: https://docs.oracle.com/javase/tutorial/jdbc/basics/index.html
Once you know how to use JDBC to procure a JDBC ResultSet, then using Commons CSV is as simple as calling CSVPrinter.printRecords(ResultSet)


[ci] test azp coverage artifact logging

Signed-off-by: Asra Ali<EMAIL_ADDRESS>Commit Message: Adds a log error message when coverage fails that points to the coverage report produced.

Risk Level: Low
Testing: Manually testing

still wip, will ping when ready

still wip, will ping when ready

Ready for review

Ready for review

friendly ping @lizan ?

friendly ping @lizan ?


[1.39]The spoiler screen was a bit buggy for me

The "choose a hero to leave to rest" screen was buggy for me, overlapped "x coins got" and hero portrait made things hard to see. Should've screenshotd it.

Yes, please share a screenshot.

I will once I get the situation like this again.

In 1.45, this screen has been reworked. The "hero selection" part can be scrolled if it doesn't fit on the screen. This should solve your problem.


Archive the repo using GitHub's "archive repo" functionality?

See https://help.github.com/articles/archiving-repositories/.

Hi @dwijnand thanks for the tip!

(closing before archiving)


CLI extra arg not working for keys with string values

The intention for running a tackle from the cli with an additional argument is that that argument is for running a specific key from a tackle file. This works for map/list values but breaks for strings in the parser around this code block in run_source.
            elif i in context.input_dict:
                context.key_path.append(i)
                walk_sync(context, context.input_dict[i].copy())
                context.key_path.pop()

Running: tackle file.yaml foo
Working example:
foo:
  ->: print bar

Broken example:
foo->: print bar

Same for non-hook keys.

No longer relevant

No longer relevant


Name undefined for nested schema field in array object

Consider the following schemas were we have an schema that contains an array of another schema that contains a nested schema.
NestedSchema = new SimpleSchema({
    field1: {
        type: Number
    }
});

Schema2 = new SimpleSchema({
    NormalField: {
        type: String
    },
    NestedField: {
        type: NestedSchema
    }
});

Schema1 = new SimpleSchema({
    Array: {
        type: [Schema2],
    }
});

Now, in a template, I would expect to be able to render the "Nested" fields inside every array object as follows:
{{# afEachArrayItem name="Array" }}
    {{> afFieldInput name=this.current.NormalField }} <----- This works fine!
    {{> afFieldInput name=this.current.NestedField.field1 }} <----- This does not work!
{{/afEachArrayItem}}

If I  manually hard code the following:
{{> afFieldInput name="Array.0.NestedField.field1" }}

it correctly displays the input box for the first array element, which is evidence of a problem with "this.current" for nested fields.
In general, I can correctly access normal fields of every array element, but I cannot access nested field elements. Is this a bug? or is there another way of doing this? It looks to me that this should be the most natural way and the most obvious way of doing it given that it's the way to do it for normal fields.
Thanks

+1 Have this problem as well.

+1 Same here. Sadly it seems that this package is not maintained anymore so dont know if there will be a official fix.

+1 same  :(

+1:
I also have same problem with schema :
coordsSchema = new SimpleSchema({
XCoordinate: {
label: "X - Coordinate",
type: String,
max: 100
},
YCoordinate: {
label: "Y - Coordinate",
type: String,
max: 100
},
});
And accessing it like :
X - Coordinate: {{ coords.XCoordinate }}
in *.html file


Add test coverage for /notify_tornado.

We now have test coverage for all of our endpoints.

Automated message from Dropbox CLA bot
@showell, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @showell!  I guess we can now lock down requiring URL coverage on all endpoints?


Fix args to cut command in 99-realsense-libusb.rules

Hi,
I've noticed an error in the dmesg:
[30331.222419] udevd[290]: invalid key/value pair in file /gnu/store/qa4qk0l00s2infj73bzzbzlxldkrjqf3-udev-rules/lib/udev/rules.d/99-realsense-libusb.rules on line 81, starting at character 154 ('.')

Seems you try to pass a string separator to a cut command which expects only a character. After reloading the the file with the fix there is no error in the dmesg output.

Hi! Can you post the issue within the CI? It's not public so I can't check what failed.

@phodina , the CI-reported issue is an internal ticket not related to the PR, so it can be disregarded.
We'll review the PR internally and update.
What Linux distro/version do you use in reproduction?
Thanks

@ev-mp Archlinux

Hi, any update on the issue?

Hi @phodina @ev-mp @seebq @wspr @martinus any updates on this issue?

@Shreyas-NR unfortunately not. The CI pipeline is private so I can't investigate and there has been nobody assigned to this issue.
@ev-mp could you please help us?

Hi, has there been any progress?

Hi, has there been any progress?

The last comment was for you.. have you tested it?

Okay, I'll change rule and test it if it works.


Add recipe for TypeScript plugin

Closes #1589
Rendered

Coverage remained the same at 97.06% when pulling c0cf2bf8bc93f62caba19d8e786a59e1d1251d79 on willsoto:docs/plugins-ts into<PHONE_NUMBER>8021eb617b29e047fbf2b35373b3a9 on Vincit:master.

Thank you!


attempt to fix issue #579

please wait before merging this as it breaks the API

@maltitco after thinking about this feature for a while, I came to the conclusion that it breaks the atomic behaviour of the Cart -> Order transaction.
If your PSP absolutely requires an order number before creating the Orderobject, then I would create a unique number and store it within the Cart object. Only if the payment is successful, I would reuse that number and copy it the the Order.number field.
I will therefore discard this pull request. Thanks anyway for pointing me on this problem.

@jrief Order number is essential not only for the current PSP. I checked the documentation of other Polish PSP and it is similar.
In that case, I'm waiting for your change in code to test it.

@maltitco
What about using the PK of the Cart instance when proceeding to the payment of your PSP?
Whenever the payment was successful, you can still assign a new number to the Order instance.

The value I give to PSP as order number must be unique and it's so much essence because it helps to check the current payment status in the PSP panel. However, this should be the order number. The PSP registers the order number and returns a token for further authorization (to check current payment status).
No matter what the payment status is (Declined, Pending, Approved), the order must be created in the store because it will make a product reservation for the customer.

@maltitco just discussed this issue with @rfleschenberg
Good news for you: I will merge this PR into django-SHOP 0.10 or 1.0, since it breaks the current API.
This also means, that I have to fix the third party payment modules.

@jrief Nice to hear it.


[WIP] Tensorflow plasma op

Codecov Report

Merging #2046 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2046      +/-   ##
==========================================
+ Coverage   87.44%   87.47%   +0.03%
==========================================
  Files         189      178      -11
  Lines       29374    28601     -773
==========================================
- Hits        25686    25019     -667
+ Misses       3688     3582     -106

Impacted Files
Coverage Δ

cpp/src/plasma/client.h
100% <ø> (ø)
:arrow_up:

rust/src/memory_pool.rs

rust/src/list.rs

rust/src/datatypes.rs

rust/src/memory.rs

rust/src/bitmap.rs

rust/src/list_builder.rs

rust/src/array.rs

rust/src/buffer.rs

rust/src/lib.rs

... and 2 more

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 e237918...5d0174a. Read the comment docs.

Just a bit curious: this sounds like some translation between TF data and plasma objects, is the purpose of the change to support TensorFlow to use Plasma as store?
And it seems the code mainly uses Plasma client to access the store, functionality wise it doesn't look like to be part of plasma if I understand correctly, would you mind to explain a little bit on the considerations to include this as part of plasma? Thanks!

@zhijunfu This op is supposed to be useful to transfer data between Plasma and TensorFlow. Supporting machine learning workloads seamlessly is very important for us and we want to make the interop between TensorFlow and Plasma as high performance as possible. This op will be fully optional and there will be a flag that is off by default which determines if the op gets built/included or not, so there will be no dependency on TensorFlow for users if they don't want to use the op.
[This is work in progress]
Also cc'ing @concretevitamin, who is the author of the op.

@pcmoritz Got it. Thanks for the explanations.

It'd be nice to ship GPU and CPU versions of the op with pyarrow. Is that feasible?

I don't know if we can build against CUDA in Travis and/or have a GPU machine for building @wesm @xhochy Any thoughts? Moving forward, it will become more important for the project I think.

TF's core may change across versions. For example I've had to rebuild some of my ops and horovod after a TF upgrade.
Some of TF's build flags will affect binary compatibility. For example "GLIBCXX_USE_CXX11_ABI".
Therefore it's probably not feasible to ship the op as a binary like the rest of pyarrow. It'll have to be built during pip install.

replaced by https://github.com/apache/arrow/pull/2104


Error building in mybinder

Bug report
Description

Demo container not building in binder
Removing intermediate container f8f6e2fb55fc
Step 25/27 : USER ${NB_USER}
 ---> Running in cf2a7e8109e6
 ---> 6a0841b27202
Removing intermediate container cf2a7e8109e6
Step 26/27 : RUN conda env update -n root -f "environment.yml" && conda clean -tipsy
 ---> Running in 57ad6dd7cfda
Fetching package metadata .............
Solving package specifications: .

UnsatisfiableError: The following specifications were found to be in conflict:
  - openbabel >=2.3,<2000 -> python 2.7*
  - python 3.6*
Use "conda info <package>" to see the dependencies for each package.

Steps to reproduce

https://mybinder.org/v2/gh/Autodesk/molecular-design-toolkit/master

Thanks for this @psychemedia - Binder has just undergone a major overhaul apparently, so I'm hoping to get this running in the next day or two.

@avirshup I have my own demo running from  here: https://github.com/psychemedia/showntell/tree/chemistry

This still seems to be an issue on this repo? Binder build fails?


When downloading dataset, it suddenly stopped and didn't resume, just stucked.

kaggle competitions download -c airbus-ship-detection -f train_v2.zip
2018-10-29 20:22:23,200 WARNING Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError("bad handshake: SysCallError(104, 'ECONNRESET')",),)'<EMAIL_ADDRESS>......
2018-10-29 20:26:39,692 WARNING Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', OSError("(104, 'ECONNRESET')",))'<EMAIL_ADDRESS>Downloading train_v2.zip to /data/krf/another
0%|                                                                                | 3.00M/26.4G [00:19<5:16:36, 1.49MB/s]
I tried to restart this command many times, but it didn't start or it started but stopped very soon.  I have no idea where the problem is.

I cannot reproduce this.  What client version are you using?  Is this still happening?

Kaggle API <IP_ADDRESS>
It still happening, but there is no problem when I downloading another competitions dataset

It's very weird because I cannot download this dataset on my laptop neither.  But I can download it on another server which I installed kaggle-api just now. They are using the same token.

Typically when I see this, it's due to some server side connectivity issues or it's because I mistakenly left debug settings in the API client (turns out that the client gets very confused when you point it towards a server that doesn't exist).  The latter problem shouldn't exist with <IP_ADDRESS>, and I don't see any related errors server side.
I'll try to investigate this, but being unable to reproduce it is going to make it challenging.

Thank you.
This problem becomes more serious...I cannot download another dataset on another server which was able to download dataset last night.

You can see that it have downloaded a small file and then stucked...
Three different machines have the same problem (Win10, Ubuntu14, Ubuntu16). They are using the same token.
I hope you guys can solve this problem soon since I have to waste much time to download dataset.

Are all of those machines on the same network?  Are you able to download hte problematic files from the Kaggle website?

Two of them are on same network but another one isn't. Even though they all are on different network, they still can't download. Today I got the following traceback,
C:\Users\kwong>kaggle competitions download -c airbus-ship-detection -f train_v2.zip
2018-10-31 09:13:28,054 WARNING Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', OSError("(10060, 'WSAETIMEDOUT')",))'<EMAIL_ADDRESS>2018-10-31 09:14:10,126 WARNING Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x0000027C42FDCBA8>: Failed to establish a new connection: [WinError 10060] 由于连接方在一段时间后没 有正确答复或连接的主机没有反应，连接尝试失败。',)'<EMAIL_ADDRESS>Traceback (most recent call last):
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connection.py", line 141, in _new_conn
    (self.host, self.port), self.timeout, **extra_kw)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\util\connection.py", line 83, in create_connection
    raise err
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\util\connection.py", line 73, in create_connection
    sock.connect(sa)
TimeoutError: [WinError 10060] 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connectionpool.py", line 601, in urlopen
    chunked=chunked)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connectionpool.py", line 346, in _make_request
    self._validate_conn(conn)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connectionpool.py", line 850, in _validate_conn
    conn.connect()
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connection.py", line 284, in connect
    conn = self._new_conn()
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connection.py", line 150, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x0000027C42FDCCF8>: Failed to establish a new connection: [WinError 10060] 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "d:\softwares\anaconda3\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "d:\softwares\anaconda3\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "D:\Softwares\anaconda3\Scripts\kaggle.exe\__main__.py", line 9, in <module>
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\cli.py", line 50, in main
    out = args.func(**command_args)
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\api\kaggle_api_extended.py", line 680, in competition_download_cli
    force, quiet)
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\api\kaggle_api_extended.py", line 617, in competition_download_file
    id=competition, file_name=file_name, _preload_content=False))
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\api\kaggle_api.py", line 325, in competitions_data_download_file_with_http_info
    collection_formats=collection_formats)
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\api_client.py", line 334, in call_api
    _preload_content, _request_timeout)
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\api_client.py", line 165, in __call_api
    _request_timeout=_request_timeout)
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\api_client.py", line 355, in request
    headers=headers)
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\rest.py", line 251, in GET
    query_params=query_params)
  File "d:\softwares\anaconda3\lib\site-packages\kaggle\rest.py", line 224, in request
    headers=headers)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\request.py", line 66, in request
    **urlopen_kw)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\request.py", line 87, in request_encode_url
    return self.urlopen(method, url, **extra_kw)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\poolmanager.py", line 349, in urlopen
    return self.urlopen(method, redirect_location, **kw)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\poolmanager.py", line 321, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connectionpool.py", line 668, in urlopen
    **response_kw)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connectionpool.py", line 668, in urlopen
    **response_kw)
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\connectionpool.py", line 639, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "d:\softwares\anaconda3\lib\site-packages\urllib3\util\retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='storage.googleapis.com', port=443): Max retries exceeded with url<EMAIL_ADDRESS>(Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x0000027C42FDCCF8>: Failed to establish a new connection: [WinError 10060] 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。',))

This Chinese sentence, "由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败", means connection attempt failed because the connecting party did not reply correctly after a period of time or the connected host did not respond.

It seems like I'm able to download the problematic files from the website.  I don't think it's the files' problem since downloading process doesn't stuck at the same moment. Sometimes it can download some files but sometimes it can't download any file.
Sometimes I even can't access the kaggle website,maybe it's the same reason. But when I can't download dataset by kaggle-api, I can access the kaggle website.

楼主解决没有啊 我也有这个问题  broken by 'ProtocolError

我也碰到了这个问题，看日志应该是host='storage.googleapis.com'连接不上，原因大家估计都懂，这个地址我找到了一个中国国内的镜像，地址是clmirror.storage.googleapis.com，先ping一下得到镜像的ip，然后设置一下host文件把storage.googleapis.com映射到镜像的ip上，就可以了。
I got this problem too.As shown in LOG,it may be caused by failed in connection with host='storage.googleapis.com'.The real reason is known to us all.I found a mirror of this host accessible in china which is "clmirror.storage.googleapis.com".You can fix this problem by modifying your host file that linking “storage.googleapis.com“ to "clmirror.storage.googleapis.com"'s ip.

我也碰到了这个问题，看日志应该是host='storage.googleapis.com'连接不上，原因大家估计都懂，这个地址我找到了一个中国国内的镜像，地址是clmirror.storage.googleapis.com，先ping一下得到镜像的ip，然后设置一下host文件把storage.googleapis.com映射到镜像的ip上，就可以了。
I got this problem too.As shown in LOG,it may be caused by failed in connection with host='storage.googleapis.com'.The real reason is known to us all.I found a mirror of this host accessible in china which is "clmirror.storage.googleapis.com".You can fix this problem by modifying your host file that linking “storage.googleapis.com“ to "clmirror.storage.googleapis.com"'s ip.

感谢，解决了


Sign up form errors

Email address is incorrectly spelt

Full name input field has a type="email" rather than type="text"

Hi
Thank you for the feedback!
We've already fixed that issues
Best regards


Clean up conversion tests

Codecov Report

Merging #49 (8fd046c) into main (c0aa8be) will decrease coverage by 37.54%.
The diff coverage is n/a.

:exclamation: Current head 8fd046c differs from pull request most recent head 6a81305. Consider uploading reports for the commit 6a81305 to get more accurate results

@@             Coverage Diff             @@
##             main      #49       +/-   ##
===========================================
- Coverage   89.60%   52.06%   -37.55%
===========================================
  Files          89       89
  Lines        4608     4602        -6
===========================================
- Hits         4129     2396     -1733
- Misses        479     2206     +1727

Impacted Files
Coverage Δ

src/solver/options.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/contacts/linear.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/mechanics/energy.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/mechanics/momentum.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/graph/linear_system.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/simulation/simulate.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/contacts/collisions/string.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/joints/rotational/impulses.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/gradients/finite_difference.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/joints/translational/impulses.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 56 more

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 c0aa8be...6a81305. Read the comment docs.


MemoryError: bad allocation  Training an object detector with 700+ images.

Expected Behavior
Finish object detection training on 732 images (1200x1800) using dlib.train_simple_object_detector without errors. The images were all tagged using imglab.
Current Behavior
After about 5 hours of training (with GPU) I get the following error:
MemoryError: bad allocation
The code works if I  used 100 images however the performance is poor. I tried reducing the sizes of the images to 480x720 and then used imglab again to tag the object.  When I ran the training session on the new images, I received errors that some boxes were too small.  I then returned to trying to figure how to work with the bigger files.
I'm running Windows 10  i7 64bit 12GB RAM and NVIDIA GeForce GT 705 with virtual memory set to 17.868 GB
I have option.ve_verbose = True but it did not return any information while training so I do not know how many images were processed before the error.  I plan to do trial and error by incrementing by 100 images. This will be time-consuming and I was hoping I can get some guidance as to how to estimate the memory requirements a priori.
Steps to Reproduce
Run my python code from the command line (not within Spyder). Spyder does not return option.be_verbose information until the very end.
It was verified that the GPU is being used.

Version: 19.13
Where did you get dlib: GitHub
Platform: Windows 10 64 Bit
Compiler: Visual Studio 14 2015

You just need more RAM.  That's what that error means.  Also, this part of dlib doesn't use the GPU.

Thank you.
I gathered that much. But how much is needed? The max on my machine is 16GB. Will that be enough? Should I expect to be able to compensate by increasing the pagefile size? Is it possible to train in smaller batches and then combined the results into a single detector? Is it possible to get information on the average size of the feature vector for each image. If so, I could use that value to plan ahead.
Also, I'm surprised that the simple object detection does not use the GPU?

No, you either need to use smaller images, fewer images, or get more RAM in
your machine.
This code doesn't use the GPU. It's not a DNN or anything like that.

Leaving this for future visitors of this issue. I had a similar issue even though I had 16G RAM. I compiled the code as 32 bit at first, which limits the memory that can be used to 2G (as the CMakeLists says). After compiling it as 64 bit,  I had no problems any more.

I assume @brankalakic is not using Python.  When using Python the setup.py file will compile in 64bit or 32bit to match the version of pyhton you are using. There isn't anything you do to set this when you build dlib.  But you should certainly be using 64bit Python.  But that isn't anything the dlib installer has control over.
To install dlib, everyone should be following the instructions here: http://dlib.net/compile.html.  If you are doing anything different then you are probably doing it wrong.  In particular, there is a lot of nonsense on the internet about how to install dlib.  Follow the official instructions: http://dlib.net/compile.html
Maybe the issue here was using 32bit python.  Or maybe it was the images were too big.  It is hard to know.  It should be noted that the simple python training API automatically upsamples images when small objects are in the training dataset.  So that can increase RAM usage as well.  In general, you don't want to be training on images that have an obscene number of non-target pixels in them.  Not because it's bad for the algorithm, but if only 0.00000001% of the pixels in your images are the objects you want to train on then you are going to run out of RAM before you get a lot of training objects into memory.

Leaving this for future visitors of this issue. I had a similar issue even though I had 16G RAM. I compiled the code as 32 bit at first, which limits the memory that can be used to 2G (as the CMakeLists says). After compiling it as 64 bit, I had no problems any more.

Ohhh! Many thanks for your advise! I use QtCreator 32 bits and got out of memory allocation during buildin dlib application. When I switched to 64 bit, error is gone


Feature/204 swagger UI page

Related Issues:

EQ-204

Main Changes:

Added Swagger API documentation for the profile /data routes and there corresponding /count routes.

I left the contact email blank for now. Also most parameters still need descriptions, since we're still waiting on glossary/tooltip descriptions from EPA.
The configuration file is stored with the S3 content, so the filepath shown in the UI would be strange if displayed:

If we want this JSON file to be publicly accessible, we may need to move it to the public folder; currently, the link to the file is hidden.
Steps To Test:

Go to the API docs page: http://localhost:3000/api-docs.
Confirm that all routes are properly documented, and that trying queries works as expected.

I am getting those warnings, I'll try checking those repositories to see if anybody else is having those issues.

It looks like the warnings are due to the fact that the Autolinker package is generating source maps when compiling their TypeScript source code, but they aren't including the source code in the NPM package (as raised in https://github.com/gregjacobs/Autolinker.js/issues/396 and discussed generally in https://github.com/facebook/create-react-app/discussions/11767). It doesn't look like there is a way to disable this warning for a particular package, but it would only become a problem when trying to debug Autolinker code.
Both swagger-ui and swagger-ui-react include remarkable as a dependency, which includes autolinker, so I think the only way to avoid the warning would be to keep the bundles in the public folder, like LEW does, but that option is a lot heavier.

Both swagger-ui and swagger-ui-react include remarkable as a dependency, which includes autolinker, so I think the only way to avoid the warning would be to keep the bundles in the public folder, like LEW does, but that option is a lot heavier.

We may need to keep the bundles in the public folder just to cut down on the noise in the console. We can discuss this lader though. I'll go ahead and merge this in as is.


[develop] Evaluate optional gate selectors

This is #13534 against develop. This includes the proof-systems update from https://github.com/o1-labs/proof-systems/pull/1146.
Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

Changeset was approved in https://github.com/MinaProtocol/mina/pull/13534; force-merging.


Parsing rating from title is not a good idea

I just tried to host a coop game with title "all welcome 3-4 players " and on second try "3-4 players all welcome ". It seems like the client tries to parse the title and misinterprets the "3-4 players" as rating range, and subsequently sets the rating range to "3-4". If the parsing of desired rating from title is basically [0-9]*-[0-9]*, it should be removed. This way of parsing rating from title is WAY too pimitive. Or ut should at least require there to be an "r" or "rating" after the number range.
Client version 0.10.5

Oh, btw. the games title was "all welcome 3-4 players " and on second try "3-4 players all welcome ". Damn, looks like the client trys to parse the rating range from the title and fails miserably. If the parsing of desired rating from title is basically [0-9]-[0-9], it should be removed. This way of parsing rating from title is WAY to pimitive.

I just looked at the regex parsing in game.java and i think the best course of action would be to remove it. Since this client is now the official one, most people will be able to use the explicit rating boundary input fields when creating a custom game anyway. This is imo the proper way to set rating bounds.
If you want to me to do that i can make a pull request.

It's not a client issue, it's a lack of server support to create a game with a dedicated rating range.
While you can set it in the create game form, right now it has no effect on the server.

Ok so what you mean is that the rating range feature was built with server support in mind? Ok, but i don't want to remove the feature, i want to remove the automated parsing. Rating range would still work if you use the rating range input fields.

I get the rating feature desires (I'd like the same) - but parsing the game title should not be it (or it should be very specific pattern).  We've had issues where we were saying CPU scores should be under a certain range, and the client would interpret that as a desire to restrict by rank.

Especially since it tells people that want to join a game that their rating is too high or too low (even if they can join anyway) based on this inaccurate title parsing.

removing the parsing could be done but then rating would be handled by java FAF client allone and adding the rating handling would be another uphill climb added to the python client.

What do you mean. Solving this issue by removing title parsing should not have any effect whatsoever on the python client because this changes nothing at all about the server.

well, we could implement this the clean way and have rating range as one of the attributes of the hosted game, that's what I'm saying.

Oh yeah sure. Would put that in a different issue though since it probably affects quite a few things (and i can easily implement this, i cannot implement a server change currently).

Same problem again: https://forums.faforever.com/viewtopic.php?f=3&t=17603
I think i will create pull request that

removes title parsing
disables/greys out rating range input field (for now) on new game form
hides rating range column (for now) in both custom games and coop games list

Well better talk it through with e.g. @micheljung otherwise you might end up doing work for nothing

If you want server support for rating ranges, make a server issue or ping me in slack if one already exists