close

在我对prometheus-es-adapter做压测的时候，会因为es繁忙导致panic，
1，one Elasticsearch server  use docker images: docker.elastic.co/elasticsearch/elasticsearch:6.4.2
2, set ES_WORKERS=100
3, Number of requests to run concurrently is 200 /使用200的并发压测
错误如下：
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xa13c19]
goroutine 74 [running]:
github.com/pwillie/prometheus-es-adapter/pkg/elasticsearch.(*WriteService).after(0xc0001c2140, 0x5a32, 0xc000f1c000, 0x13, 0x20, 0x0, 0xc6f360, 0xc000b5a750)
/go/src/github.com/pwillie/prometheus-es-adapter/pkg/elasticsearch/write.go:99 +0x29
github.com/pwillie/prometheus-es-adapter/pkg/elasticsearch.(*WriteService).after-fm(0x5a32, 0xc000f1c000, 0x13, 0x20, 0x0, 0xc6f360, 0xc000b5a750)
/go/src/github.com/pwillie/prometheus-es-adapter/pkg/elasticsearch/write.go:51 +0x73
github.com/pwillie/prometheus-es-adapter/vendor/gopkg.in/olivere/elastic.v6.(*bulkWorker).commit(0xc0002a6ac0, 0xc76300, 0xc0000240a8, 0x1, 0xc0002d7c80)
/go/src/github.com/pwillie/prometheus-es-adapter/vendor/gopkg.in/olivere/elastic.v6/bulk_processor.go:588 +0x37d
github.com/pwillie/prometheus-es-adapter/vendor/gopkg.in/olivere/elastic.v6.(*bulkWorker).work(0xc0002a6ac0, 0xc76300, 0xc0000240a8)
/go/src/github.com/pwillie/prometheus-es-adapter/vendor/gopkg.in/olivere/elastic.v6/bulk_processor.go:487 +0x48a
created by github.com/pwillie/prometheus-es-adapter/vendor/gopkg.in/olivere/elastic.v6.(*BulkProcessor).Start
/go/src/github.com/pwillie/prometheus-es-adapter/vendor/gopkg.in/olivere/elastic.v6/bulk_processor.go:336 +0x1bb
修改代码打印出after函数错误遇到两种情况：
1，Post http://<IP_ADDRESS>:9200/_bulk: dial tcp <IP_ADDRESS>:9200: connect: cannot assign requested address
2，no available connection: no Elasticsearch node available

Hi yjbdsky,
Thanks for the PR.  I have just merged another PR that addresses this issue.  Please let me know if you still experience issues with the latest version.  Note however there are some breaking changes in metrics names and http port for health checks.

Sorry ,the latest code is ok ,i get the latest version  form the docker hup ,but the is not the latest version

and my code is old version

I fork the code yesterday,but is the old version。It's amazing。

i know why ! please close the pr, thks  ^_^


Using a pinned certificate will always incorrectly trust peer on iOS

Description
Due to a condition in didReceiveTrust combined with _checkValidity only being set locally, the trust evaluation will yield false positive results and exit early when using a pinned certificate.
This should potentially be a security risk if providing a certificate using the ca property since the library essentially skips certificate validation.
Steps to reproduce
Steps to reproduce the behavior:

Connect to a server with connectTLS
Use a pinned certificate that doesn't match the server certificate

Current behavior
The code exits early and connects without validating the certificate.
Expected behavior
The certificate should be validated and connection should be dropped.

Bump @Rapsssito


Stop calculating deaths and cases scores

Closes #248.
Only hospital admissions predictions are still active; cases and deaths forecasts are no longer supported by Forecast Hub and the JHU truth data used to evaluate these is no longer being updated. This means that historical error metrics for cases and deaths are fixed, so we no longer need to calculate them.
The pipeline is still able to recalculate cases and deaths scores if we wish -- this only requires updating the signals vector. To make sure that these archived scores are still available for the dashboard, the relevant score RDS files are downloaded from the S3 bucket and then re-uploaded unmodified after the pipeline completes.

Oh, another thought from @dshemetov's work on the old exploration  scripts, as far as saving memory is concerned, we may want to sprinkle gc() around, since it isn't getting called by R as often as we'd like.

On the gc()s, any suggestions on how frequent they should be? We have just a couple in here already, but I suppose there are also some long loop cycles.

iirc it was around get_covidhub_predictions that I OoMed, so it might actually belong in the for loops there. In the cases where Dmitry got a large decrease in memory, there wasn't even explicit rms or anything like that.

Just a very light dusting of gc() added here


Update usage instructions

Reference issue #5

This change looks fine to me. I haven't tried instantiating without the additions introduced here, but I've had a look at our internal usage and it's consistent with what @acca is proposing.

I had a look inside this and seems it is not just a problem of documentation, please see #5 for details. I think this PR is no longer needed for now.


Add shortcut to python conda environment py39_prvi

See environment.yml for more details about this python environment py39_prvi on Windows10.
Note that my setting of pytorch and corresponding libraries might not fit your computer/server.
You need to have Anaconda Prompt to help you with the following instructions. See Anaconda website for more info.

To recreate an environment from the YAML file on the same or another machine, you can use the following command:
conda env create -f /path/to/your/file.yml

This approach is particularly useful for sharing environments with others or for deploying code that depends on specific package versions.

LGTM


Demonstrations metadata updates

Added the metadata for one more of the new demonstrations.

Could you also include here tutorial_qutrits_bernstein_vazirani? It has been added today


Allow renaming and transfering repos programmatically

Fixes #694
On top of implementing transfer repos, I'm refactoring some of the token validation/retrievals which is duplicated. I kept some things for the backward compatibility of some methods, but it will be simplified further once cleaned up.
I added two methods: transfer_repo and rename_repo, with the first being more consistent with the codebase by handling separately the model_repo name and its namespace. rename_repo, on the other hand, follows a bit more intuitive approach by simply using the repo_id, which is what you copy/paste from the Hub.
Example usage
# Examples with rename_repo
rename_repo("osanseviero/test1", "huggingface/test")
rename_repo("osanseviero/test1", "osanseviero/test2")

# Examples with transfer_repo
transfer_repo("test1", new_name="test", new_organization="huggingface")
transfer_repo("test1", new_name="test", organization="osanseviero", new_organization="huggingface")
transfer_repo("test1", new_name="test2")

I don't love having two methods for the same goal though, so we can ax rename_repo, although I feel it's more intuitive for the users and does fewer things on the back.

I'd agree that the rename_repo API looks better/simpler

With the big con it would be inconsistent with the rest of the methods, unfortunately.

Thanks for your PR, very clean. Throwing another idea in the pit: how about move_repo? To me, move covers both rename and transfer, while transfer seems like it's only for cross-organization changes and rename sounds to me like inner-organization changes. No strong opinion though.
And to recap what we have in the library right now:

hf_hub_url/hf_hub_download takes repo_id
model_info takes repo_id
list_repo_files takes repo_id
upload_file takes repo_id
delete_file takes repo_id
Repository takes repo_id

And

create_repo takes name/organization
delete_repo takes name/organization
update_repo_visibility takes name/organization

So all methods that manage the repositories' settings and existence on the hub ask for an explicit organization. However, this is legacy from the very beginning of the library so I think we should feel free to reconsider if having <org>/<id> is simpler than two arguments (which I definitely think it is), especially as setting up a deprecation cycle for this should be very straightforward.
If we don't opt for updating the create/delete/update_repo_visibility methods, I would keep the organization parameters separate.

Thanks for the feedback!

Given the rename_repo was more intuitive by passing repo_id instead of name, I kept that and removed transfer_repo.
I renamed rename_repo to move_repo as per @LysandreJik suggestion, I agree it sounds better.
About the create/delete/update_repo_visibility methods, let's deprecate the organization parameters. I think this will be somewhat easy but we'll need to modify quite a bit of 3rd party integrations in the future (they use pinned versions so not big issue). Let's keep this PR small; are you ok if we do this in a follow up PR? (opened an issue)

Yes, absolutely!

@lvwerra about this comment

Should we add some guidance for the case where a user wants to transfer a model from org2org or user2user?

I don't think providing this guidance should be in the client library (except a link to the docs). What we can do is expose the error message to the user when this happens so it's as confusing. It's then in the backend side to provide better error messages in the response.
Example result with existing implementation

requests.exceptions.HTTPError: 403 Error Message: {"error":"You don't have the rights to move this model to OsanOrg2"}

@osanseviero sure, I don't have a strong opinion where the message comes from. I just thought from a users perspective the current documentation alone might be a bit frustrating: I need to move a repo  org2org > I find a function that could potentially do that > function docstring (or error following message) says just no, this is not possible > what now?
I think rather than just saying it is not supported it would be nice to directly offer a solution or point to instructions.

I agree with all @LysandreJik said, especially the part about deprecating the organization parameter in create/delete/update_repo_visibility for more consistency.
(@LysandreJik I hope you realize that for backward-compatibility reasons, the first positional argument of those methods will need to support both a repo_name and automatically add the namespace of the user, or a full organization/repo_name which is something I've asked for ever and ever)

I'm supportive of deprecating the organization parameters and aligning to "full" repo ids everywhere.
I think third party library usage is still rather small and we can work with them to pin their dependencies and/or support them updating their code.

Answering @lvwerra

@osanseviero sure, I don't have a strong opinion where the message comes from. I just thought from a users perspective the current documentation alone might be a bit frustrating: I need to move a repo org2org > I find a function that could potentially do that > function docstring (or error following message) says just no, this is not possible > what now?
I think rather than just saying it is not supported it would be nice to directly offer a solution or point to instructions.

After thinking about this, I don't think the limits of the server API should be documented in the library. Instead, I added a section under docs with clear documentation for this. The documentation is linked both in the docstring and in case of an error. If we do server changes, then we just need to update the documentation. Here is an example of an error when doing something invalid.
requests.exceptions.HTTPError: 403 Error Message: {"error":"You don't have the rights to move this model to OsanOrg2"}. For additional documentation please see https://hf.co/docs/hub/main#how-can-i-rename-or-transfer-a-repo.

@osanseviero that's great, thanks for adding the link to the docs!


Question about stax batch dimension

Should it be possible to define a network in stax without setting an exact batch dimension?
import jax.numpy as np
from jax import random
from jax.experimental import stax
from jax.experimental.stax import Dense, Relu, Flatten, LogSoftmax

# Use stax to set up network initialization and evaluation functions
net_init, net_apply = stax.serial(Dense(128), Relu, Dense(10), LogSoftmax)

rng = random.PRNGKey(0)
# Initialize parameters, not committing to a batch shape

# works
in_shape = (-1, 1)
out_shape, net_params = net_init(rng, in_shape)

# doesn't work (fails with ValueError: all elements of broadcast shape must be non-negative)
in_shape = (-1,)
out_shape, net_params = net_init(rng, in_shape)

I get that's it's a little odd, but if I want to use the same model to train on with large batches, but also use it for single examples later, it would be nice to have this.
As a workaround, I can of course add a fake 1 dimension on the end, and then remove it later, but I was a little surprised that this doesn't automatically work.

We'd like something like that to be possible, but it isn't right now. (Actually it's because stax predates the existence of vmap, and we haven't really updated it in a while.) I think this might be a duplicate of #381 though.
You'd still need to provide a nonemtpy input shape tuple with positive elements to init_fun to specify the example size (i.e. in_shape won't be just (-1,) because that doesn't provide any shape information, but maybe it'd be e.g. (28 * 28,)), but we'd like it not to be necessary to specify a batch size.

Can you check #381 and see if you think this is a duplicate?

I saw that issue when I filed this one, this could be a duplicate, but I also think I worded this confusingly.
If my inputs is a list of scalars, I could consider that of shape (batchsize,) or (batchsize, 1).  The second one seems to work with stax but not the first.  I could of course, wrap the stax model with jp.expand_dims(input, axis=-1) but wanted to make sure I wasn't missing something.


App crash when set same symmetric key

Describe the bug
When I'm playing with demo app, the app crashed sometimes when connecting with demo dApp.
Is it possible to add try catch or throw here? without 2 force try in the code?
Or we can remove the the same key before we add it ?
SDK Version

Client: [e.g.  Swift]
Version [e.g. 22]

To Reproduce
Steps to reproduce the behavior:

Go to demo wallet
Scan QR code in demo dApp
Click on Approve
App crashed

Expected behavior
The SDK will handle the duplicate SymmetricKey
Screenshots

It's hard to reproduce, I just connect the same wallet with the same dapp multiple times.
The duplicate pairing has been created, somehow, it crashes after scanning the QRCode.


Clean up DeprecatedDefaultIngressClassKey

clusteringress.class was deprecated for a long time ago, we should clean up DeprecatedDefaultIngressClassKey and related code like:
https://github.com/knative/networking/blob/6a77ca6c8f6920f1a480014f215904919ca1f5d3/pkg/network.go#L68-L69
/kind good-first-issue

Fixed by https://github.com/knative/networking/pull/388


docs(README): improve cache documentation

Closes #20

:tada: This PR is included in version 1.0.5-test.1 :tada:
The release is available on:

npm package (@test dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.3-test.1 :tada:
The release is available on:

npm package (@test dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Extension of the Microsoft.AspNetCore.HttpRequest class

This class extends the Microsoft.AspNetCore.HttpRequest class, adding functions to determine whether the HTTP request is AJAX request, and to query the key value of QueryString.

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


Feature - IJ 192 Daily Affirmations

I've added a new resource type called 'Affirmation' which can be used to schedule a daily affirmation (or 'though for the day' but affirmation is a more succinct way of describing them). I've also updated the seed to be able to generaate upcoming affirmations and archived affirmations (same naming convention as goals), Note: You will need to update your config.rb file if you want to run the seed to include values for PAST_AFFIRMATIONS and UPCOMING_AFFIRMATIONS, I've gone with 100 and 30 of each.
The User's will see this affirmation on their dashboard view below the 'Your Journey' header if present.

Team Members have a new button on the dashboard and navbar that takes them to the upcoming affirmations index which will display a table sorted by the scheduled date with today/the next date upcoming at the top.

The archive index contains a reduced table with pagination controls (as this index can get huge whereas you wouldn't expect more than a months worth of upcoming affirmations to be scheduled) which can also be searched according to the affirmation text. (More complex search for the team member and date range could also be added in future if required).

@phil-6 can I get your approval on this? I've created a new ticket IJ-199 to capture any enhancement we feel needs to be made to the index view which means the rest of the work should be good as this is the only outstanding discussion point 👍


Android Studio ERRORS

@osuleymanova @android-dev-lxl
Android Studio is still not working properly, several errors, one being that when you build a new project under most of the APIs for example API 24 that when you then run the project in Preview that it does not run and displays red text. I have provided a screenshot in a previous message.
The only way I can use Android Studio is by using API 34 which is available to 1% of devices.
Also, the Emulator is not allowing me to see work I complete.
Secondly, I have a @Preview although in the Split it displays that there is "No Preview Found"

Android Studio requires urgent work.

Hi @AR102023
Thank you for writing in.
Please provide a screenshot showing all your code including the specific import statements at the top.
I am unable to troubleshoot this issue just based on this limited screenshot.
I look forward to your reply.
Regards.

Hi John,
Thank you for responding to my messages.
Regarding this particular inquiry, it happens on starting a new project on API 24. Now I have to create a new project using API 34.
I believe this to be an issue with Android Studio as it used to work in API 24 without the red writing showing.
The below is running on API 24.

The code in the above screenshots are exactly how it was when I received the message that no @Preview was available.
Currently using API 34 at the moment until I can start using API 24.

@johnshea
Issue now fixed, possibly due to an update to Android Studio


[AVM Module Issue]: avm/ptn/lz/sub-vending default storage account name too short

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
Module Name
avm/ptn/lz/sub-vending
(Optional) Module Version
0.1.5
Description
The vending module fails from time to time due to the storage account created for the Deployment Script already exists.
As there are 4 random characters in the current version, increasing this to a higher number would probably help mitigate these random issues.
(Optional) Correlation Id
No response

This has been resolved


Question : can a package be published to ~/.nuget on local machine?

Is it possible in msbuild to pack NumSharp after build automaticly and move to ~/.nuget?
I come up with this question because if there are other projects like pandas.net or I can image SciSharp and they are in different repos, we can not reference them in csproj. Because everybody of us has a different folder structure.
To avoid bad style or complains I think we have now 2 possible options.
No 1) one repo with one solution and all projects so we can reference them in csproj. And we all have same fder structure
No 2) we reference them as nuget package. Usual nuget search first local so if msbuild copy NumSharp nuget package automatically to local cache we are fine. :)
Maybe we have other options?

Until now i go your option 3.
But we should really consider other solution

Submodule is another option.
https://blog.github.com/2016-02-01-working-with-submodules/

Cool. I was always wondering what this strange folder in ironpython is.
https://github.com/IronLanguages/ironpython3/tree/master/Src
From the blog it's a submodule. Indeed that would be an option.


Update optimize-form-performance.md

Added notes for asynchronous network requests

Looks like this is the equivalent Power Apps doc - https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/optimize-form-performance


Responsive UI package for the Office 365 SP sites

Hi,
I only need to implement the responsive feature for an SharePoint 2013 online site but even though the docs mention that the PnP package doesn't have to be installed to use this, there is no guide on how to actually achieve this.
Can anyone assist with this?
Thanks

Because you are targeting SP2013, please use this project instead: https://github.com/OfficeDev/PnP-Tools/tree/master/Solutions/SharePoint.UI.Responsive .Thanks. I will close this one.


[Sticky / Visibility]  Fixed Isn't Removed Until Top Offset is Surpassed by 1px

Hello,
I have a sticky header, residing above my page content.
It's all set up according to http://semantic-ui.com/modules/sticky.html.
(see Fiddle link below)
Scrolling down the page works fine: The header stays at the top of page, whereas the content scrolls below.
But when scrolling back top, the top of the page content gets stuck just below the header, which overlaps the page content.
I examined this using dev tools and saw that when scrolling down, Semantic UI adds classes "fixed" and "top" to the sticky header, which don't get removed when page is scrolled back to top again.
Meanwhile, as a workaround, I implemented an own handler, which detects the page is scrolled to top again and removes the classes manually.
Here is a JS Fiddle, to demonstrate the issue:
http://jsfiddle.net/Windwalker/vmk41s9j/2/
Can you tell whether this is a bug which will be fixed?
Or is there something I can to to avoid this behaviour beforehand?
Kind regards,
Sascha.

This is an edge condition of sticky. Fixed isnt removed until it surpases its previous position not equals.  Since the content is exactly at 0 px, it will not unstick. You can fix this by adding a 1pixel offset to scroll.
http://jsfiddle.net/9tf8jkfj/
I'll look into seeing whether it messes up anything if we swap <= for <

This fix still doesn't work great... The content appears to jump after 1px is surpassed and vice versa when you reach the top.

Yeah visibility handles placeholder case, sticky does not.

Fix accidentally got added in another commit 09ecab6 #2710


[http1 codec] Allow requests with Transfer-Encoding and Content-Length headers set.

Commit Message: [http1 codec] Allow HTTP/1 requests/responses with Transfer-Encoding and Content-Length headers set.
Additional Description: opt-in for serving requests/responses with Content-Length and Transfer-Encoding: chunked. Per RFC remove Content-Length header before forwarding it to upstream.
Update http-parser version to include fix for https://github.com/nodejs/http-parser/issues/517.
Risk Level: Medium
Testing: unit tests, update integration test
Docs Changes: updated docs/root/version_history/current.rst
Release Notes: http: added allow_chunked_length configuration option for HTTP/1 codec to allow processing requests with both Content-Length and Transfer-Encoding: chunked. If enabled - per RFC Content-Length is removed before sending to upstream.
Fixes #11398

/assign @antoniovicente

/wait

/wait

/wait

Updated PR:

validation logic is in onHeadersCompleteBase() which is shared by Client/Server implementations.
codec_settings_ moved to base class,
reverted integration test change and version history comment note as behavior is not changed now if option is off

Note will also need a main merge.

Found an issue with http-parser for response parsing case, will update PR when issue is fixed.

/wait

When would this PR get into envoyproxy/envoy-wasm so that istio can pick it up? We are actually hitting this edge case. @alyssawilk

Up to folks on that side.
Did @jplevyak 's last merge sort this out for you?  Looks like it landed the same day you pinged here.

@alyssawilk we won't be able to test this until this version of envoyproxy gets into istio and then into our IBM managed istio offering.


typecheck svelte files in tests

Adds svelte-check to the check script in packages/kit, which will hopefully help us catch more type errors early (https://github.com/sveltejs/kit/pull/1316#issuecomment-831491962).
This doesn't actually fix any of the surfaced errors, but it's low-hanging fruit if anyone wants to work on that
Before submitting the PR, please make sure you do the following

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

Made two changes to types:

Added an internal NormalizedLoadOutput that mirrors the public LoadOutput, and changed LoadOutput to allow string | Error for loaded.error. An alternative would be to only allow Error
Referenced Vite/Svelte types inside the Kit types. This means that people only need to reference Kit types in their own apps


Use LinearRgba in bevy_gizmos internals

Objective
This PR arose as part of the migration process for bevy_color: see #12056.
While examining how bevy_gizmos stores color types internally, I found that rather than storing a Color internally, it actually stores a [f32;4] for a linear RGB, type aliased to a ColorItem.
While we don't have to clean this up to complete the migration, now that we have explicit strong typing for linear color types we should use them rather than replicating this idea throughout the codebase.
Solution

Added LinearRgba::NAN, for when you want to do cursed rendering things.
Replaced the internal color representation in bevy_gizmo: this was ColorItem, but is now LinearRgba.
LinearRgba is now Pod, enabling us to use the same fast bytemuck bit twiddling tricks that we were using before. This requires:

Forcing LinearRgba to be repr(C)
Implementing Zeroable, and unsafe trait which defines what the struct looks like when all values are zero.
Implementing Pod, a marker trait with stringent safety requirements that is required for "plain old data".

I'm not sure about the Pod/bytemuck trick. I think LinearRgba should implement ShaderType since it's the color intended for shaders.

I implemented the ShaderType trait for LinearRgba in this PR https://github.com/bevyengine/bevy/pull/12137

[6:30 PM]IceSentry: @Alice 🌹 actually, I misunderstood the gizmo code. You can't really use all the encase goodies for vertex buffers. So I think the bytemuck thing is unavoidable here
[6:30 PM]IceSentry: It's still a good thing to use ShaderType in LinearRgba, but it can't help much in this case
[6:31 PM]IceSentry: we definitely don't want to allocate in prepare_asset like that
[6:31 PM]IceSentry: it will kill perf
[6:32 PM]IceSentry: I think there's probably a safer api that's missing here, but for now I think we should use the bytemuck trick
[6:34 PM]Alice 🌹: Yeah, that was my concern seeing the final diff 😄 I'll revert it and merge then 🙂

Conversation on Discord about the final reverted commit.


Add Excelize

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 250 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Deploy preview for landscape failed.
Built with commit b6fb3657e0adf0c3a6a5684c87bc8a7960a01c25
https://app.netlify.com/sites/landscape/deploys/5d687a6e49e0ed00070ab8cb

This looks like a cool project, but unfortunately the Tools section of the Serverless Landscape is not designed to capture Go libraries. As you could imagine, there are hundreds. Instead, you're welcome to start from https://github.com/cncf/landscapeapp/ and create a landscape of your own.
Also, as an FYI, your PR failed because your SVG embeds a PNG.


how do i build the client can i get like a vidieo how or smthing

lol its private and u rnt gonna get it XD

oh didn't know its private thx for info man

np :D i dont have it either lol a friend is making it


Possible to include hostname in the 404 log

Better support for multi-site solutions. Feature request #25 + #30 .
New configuration setting to turn this feature on/off (off by default).
Not sure I followed the "correct" pattern when reading the config setting in Configuration.cs...

@ErikHen Is this all needed to close #25 and #30?

@marisks Yes. This will include the hostname in the log, so it's possible to see to which site the request are made.


The graphs show 0 cases for the last 15 days

Confirmed, Active, Recovered graphs show 0 value for the last 15 days.

Hi @realkushagrakhare - Could you attach a screenshot? Is this for a particular page/state?

Seems to be fixed


libc: newlib: libc-hooks: Consistently use const void* as arg to write

write() function is not supposed to change buffer passed to it, so
propagate const pointer param to all write-like functions used/defined
in this file.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

Codecov Report

Merging #10731 into master will decrease coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10731      +/-   ##
==========================================
- Coverage   53.26%    53.1%   -0.16%
==========================================
  Files         215      215
  Lines       25829    25829
  Branches     5697     5697
==========================================
- Hits        13758    13717      -41
- Misses       9754     9801      +47
+ Partials     2317     2311       -6

Impacted Files
Coverage Δ

include/posix/posix_sched.h
0% <0%> (-100%)
:arrow_down:

lib/posix/pthread_barrier.c
0% <0%> (-100%)
:arrow_down:

lib/posix/pthread_cond.c
62.5% <0%> (-20.84%)
:arrow_down:

lib/posix/pthread.c
68.03% <0%> (-12.33%)
:arrow_down:

lib/posix/pthread_mutex.c
76.38% <0%> (-1.39%)
:arrow_down:

lib/posix/pthread_sched.c
62.5% <0%> (+20.83%)
:arrow_up:

Continue to review full report at Codecov.

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

I dont see you using const void* as the pr message says.

@nashif : Fixing.

@nashif : Fixing.

thanks, but then, if we are fixing the signature, why not fix it for real:
ssize_t write(int fildes, const void *buf, size_t nbyte);
nbyte is size_t

nbyte is size_t

Now fixed too.

@nashif : Ok, now fixed "for real".


Scale consistency

Hi I m gonna make a test with your nice library, but a quick question about scale, if I would provide 2 images of similar location would I get a consistent  scale in both results? Is there anyway to get into the right scale or just like midas it s an avarage scale ?
Thanks

Our code uses MiDaS, so the output disparity maps have the same scale ambiguity.


Improve PEP conformance of add/remove_reader/writer

According to PEP 3156, Section "I/O Callbacks", calling each of remove_reader/writer and add_reader/writer multiple times in sequence on the same fd without adding/removing a reader/writer inbetween is legal. Logging a warning is thus not neccessary and only produces noise when debugging applications.
In addition, the correct return values for remove_{reader,writer} have been implemented.
Note: this pull request depends on and includes #19 (I probably should have handled this differently).

#19 was release with version 0.4 on pypi, but #20 (this pull request) was not, because I am a spazz ball.

No worries, #19 was more important anyways. Thanks for merging!

I decided to make a 0.4.1 release


"g-recaptcha-response field is required" - Field is empty

Hello, I'm on the newest commit currently of this package. I can see the captcha badge, and my _submitForm/_captchaForm/_captchaSubmit all bind properly. However, every time I submit my form it doesn't also submit the g-recaptcha-response field, causing validation to fail.
I've tried moving the captcha render around within the form, to see if it was an issue with where it loaded, as well as tried to pull the value before submit and I've tried to use a custom submit function as well.

Hi @ColinTravis ,
Can you try to upgrade your package to release v1.8.3 to see if this issue still exists?

Just fully updated, issue still persists. I've read around that with captcha, sometimes it's position within a form can prevent it from functioning, so I moved it around again to see if that fixed it. I think is should be fine where it is now (right before the form ends, and still within the input groups)

Subscribe To Our Newsletter

                            <form method="post" action="{{ route('email.subscribe') }}" class="form-inline" id="newsletter-subscribe-form">
                                {{ csrf_field() }}

                                    <input type="hidden" name="item" value="newsletter" />
                                    <input type="email" class="form-control email-subscribe" placeholder="Email" name="EmailAddress" id="newsletter-email-address" />

                                        <button id="newsletter-subscribe" type="submit" class="btn btn-form btn orange">SUBSCRIBE</button>

                                    @captcha

                            </form>

```

There'a also nothing too crazy going on in my mail controller:

```php
     * @param Request $request
     * @return \Illuminate\Contracts\View\Factory|\Illuminate\Http\JsonResponse|\Illuminate\View\View
     */
    public function subscribe(Request $request)
    {
        $subscribeConfig = config('campaignmonitor.subscribe.' . $request->get('item'));
        $campaignMonitorData = $request->except(['item', 'ResponseMessage']);

        $validateFields = array('g-recaptcha-response' => 'required|captcha');
        $this->validate($request, $validateFields);

        if(!empty($subscribeConfig['customFields'])) {
            if(empty($campaignMonitorData['CustomFields']))
                $campaignMonitorData['CustomFields'] = [];
            foreach($subscribeConfig['customFields'] as $key => $value) {
                $campaignMonitorData['CustomFields'][] = [
                    'Key' => $key,
                    'Value' => $value,
                ];
            }
        }

        $listID = $subscribeConfig['listID'];
        $result = \CampaignMonitor::subscribers($listID)->add($campaignMonitorData);

        if($request->ajax()) {
          return response()->json($result);
        }
        $message = $request->get('ResponseMessage', 'Thank you!');
        return view('emails.thank-you', ['message' => $message]);
    }```

The @captcha directive should be placed within a form element. So does it work now?

No, it still doesn't validate, as the g-captcha field still ends up being blank when it submits.

Can you please try to reproduce your issue on codepen? Like what I did here: https://codepen.io/albertcht/pen/MXraNr, that would be easier to debug. I only need your html redered by your frontend code.


silver-platter: 0.5.12 -> 0.5.20

Diff: https://github.com/jelmer/silver-platter/compare/0.5.12...0.5.20
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hmm, ofborg disagrees with you about this building; looks like this needs openssl and pkg-config?


Added option to exclue node_modules directory by default to help alle…

#55 This pull request adds a default configuration option to exclude the node_modules directory from being watched in order to help alleviate performance issues when running lite-server for use cases like described in the angular2 quickstart documentation.

Good call, @qubithaze. Tested this and verified the performance benefits. Merging now, but may take a few days to publish.

And thank you!


⚠ PrivateHD has degraded performance

In daa23d1, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2217 ms

Resolved: PrivateHD performance has improved in 387c194.


Data from IO Link gateway not sent

What Should Happen
According to the documentation, sensor readings should be automatically sent to the broker when connecting sensors via IO Link.
Current Behaviour
No data in the /ia/raw topic
Possible Solution
Checking the code of the sensor_connect container?
Steps to Reproduce

Install the system following the steps in the documentation
Connect an IO Link gateway to the network
Connect a sensor to the gateway

Context (Environment)

Factory Cube with a fresh installation of k3os.
The container of the image rancher/klipper-lb:v0.2.0 does not execute due to a port conflict presumably with the vernemq/vernemq:1.11.0 container.

I have made sure that the IO Link gateway is in the network. I have restarted the system more than once and nothing solves the problem.
How has this issue affected you? What are you trying to accomplish?
I am trying to create get sensor data over IO Link and to create a dashboard using Grafana.

You need to specify the IP range, where sensorconnect should look for gateways first. @larswitte and @oarne97 are currently rewriting the documentation, so that is easier to understand.
You can do that by accessing the stack via Lens and changing under apps --> releases the configuration under sensorconnect.iprange
See also: https://docs.umh.app/docs/developers/factorycube-edge/sensorconnect/#ip_range
You might struggle with Lens (xxx not found), for which you can find a solution here: https://docs.umh.app/docs/tutorials/united-manufacturing-hub/working-with-helm-and-lens/#troubleshooting
btw: The container of the image rancher/klipper-lb:v0.2.0 does not execute due to a port conflict presumably with the vernemq/vernemq:1.11.0 container. will be solved by #559

@JeremyTheocharis can you provide some screenshots on how to change the ip range to issue #455? This could help @oarne97

Closing this issue as measures have been taken.


nuget new build process

Hi,
your build process is at the moment complex because the old csproj doesn't support multi target builds.
Do you like that I make a PR to change to the new cprojs with  ?
bye

Please do.

Hi, I just wondering about some differences in the build between different .NET / signed releases.
I will now try to merge it in the right way, but maybe we need after that a short session together to clariy the last open points

When would you like to have it?

I'm in Germany so any time between 7:30-16:00CET is fine. Does this fit for you?

It's perfect. Please, send me a meeting link.

@zapadi
09.08. 10:00-10:30
https://go.teamviewer.com/v13/m29470043

Hi,
There is a big refactoring in progress right now, but I'm not sure that will be available by next month.
Any contribution it will speed up the process.
Adrian

On 9 Oct 2019, at 17:25, ekwus<EMAIL_ADDRESS>wrote:
Hi
Has there been any progress on this? I need a .Net Standard version of the library or grow my own. Was thinking of forking and restructuring but would rather contribute directly.
Cheers
Dave
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/zapadi/redmine-net-api/issues/210?email_source=notifications&email_token=ACXVEWPG7QXSOEZL7KDEFNTQNXST7A5CNFSM4FMWCPRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAYCCBA#issuecomment-540025092, or mute the thread https://github.com/notifications/unsubscribe-auth/ACXVEWMBETDV7CO2SJFZHHLQNXST7ANCNFSM4FMWCPRA.

Hey
I found your redmine-netcore-api project and have got that working for now.
If you have specific tasks that can be branched off easily then let me know what they are and I'll take a look at them?
Cheers
Dave


Fixed. Socket was created with a random port.

The fact the port is random is deliberate - it tries to find a free port. However in #4 I've added the ability to specify --port on the command-line in case you want to hard-code this.


Use a list of checkboxes to publish grades

I just discovered the MultiCheckboxField. I'll probably use that instead.

Thanks. I will look at this later tonight.

Would it be useful to have a count of the number of scores that exist for each one?

Probably, but I'd consider that an out-of-scope enhancement


TODO [ENGINE]: Add debug rendering system

make a modular system for rendering gizmos etc.

we have debug gizmos which are all rendered in ER_Sandbox.cpp (just not a dedicated class/system with all debug gizmos); closing this for now as this ticket is misleading and not a priority


Please add ability to complete an LP add

Description
Just today I had an LP add operation (initiated from Asgardex) that got hung up. One of the smart people on the THORChain Telegram figured out that the asset side of the LP add was successful but the RUNE side failed for some reason.
Asgardex gave no indication that I could find that the LP add was stuck. I was however able to load the keystore wallet in THORSwap and that said the LP add was incomplete and gave me a "complete" button to press and then verify to go ahead.
Something like this would be a great addition to Asgardex.

Yes, Asgardex does detect if one side is missing but doesn't help you fix it. I have the same issue on my ledger and wish there was a simple way to fix it or be told "send x asset to this address with the memo abc."
It shouldn't be too hard to work out what is required to fix it up and show the user.

Awesome, thanks. Look forward to the next release.

Just needed to use this and it was trivially easy to fix and incomplete LP add.


add/default-route-table

what

Manages the default route table created alongside aws_vpc resource automatically.

why

If not managed there are no identifying features about this resource which is confusing.
In our case we establish ownership via tags passed into this module, if no tags are present it is difficult to report on ownership

references

Closes #109
aws_default_route_table

/test all

/test all

@nitrocode I just pushed up a fix for that error reported by terratest/bats. Should succeed now if you try again. I wasn't able to get the test runner to work locally (I'm probably doing something incorrectly), was using various make commands to try to get it to work.
When releasing I would recommend placing something release notes indicating the new resource as people who use this may be taken aback by it asking to "add" a resource (that already exists).
Feel free to ping me on slack if you think a tag change is required. Easy enough to implement.

/test all

@nitrocode once more. I was incorrectly pointing at id instead of default_route_table_id. Sorry for the extra runs.
I also confirmed that this output value is available through hashicorp/aws provider 3.0.0 and onward.

Just looking at this do you think it's worthwhile also bringing in these?

aws_default_security_group
aws_default_network_acl

I ended up adding 3 booleans for enabling / disabling the management of these resources. This should retain the existing behaviour for people whom don't want this.
I'll add an extra test for this case.

I updated some of the naming as per your suggestion @nitrocode. I didn't do it exactly as you named it as this test actually covers 3 things:

default security group (already existed in this module)
default network acl (new)
default route table (new)

@cdobbyn did you see this comment https://github.com/cloudposse/terraform-aws-vpc/pull/110#discussion_r971267496

@nitrocode I updated as per https://github.com/cloudposse/terraform-aws-vpc/pull/110#discussion_r971267496.
I removed the standalone test and made the complete one set all values to true.
The "Summary" action on here seems to be a subscription issue and not a code one (it keeps throwing me for a loop).

/test all

@nitrocode anything else you need from me here? This isn't failing on code but misconfiguration of the summary bot?

@aknysh @Gowiem do you mind taking one more look before merging?


Pylint subcategories' codes are confusingly documented

https://docs.astral.sh/ruff/rules/#pylint-pl

This looks like using C, E, R or W should enable/disable Pylint rules, but this is wrong as the codes are actually PLC, PLE, PLR and PLW.
This is especially vicious given that W and E are existing pycodestyle groups https://docs.astral.sh/ruff/rules/#pycodestyle-e-w, so config validations will pass.
Even the URL currently needs to disambiguate between pycodestyle and pylint error/warning groups https://docs.astral.sh/ruff/rules/#error-e_1 and https://docs.astral.sh/ruff/rules/#warning-w_1 (notice the -1)

Using the full error code in parentheses does make sense to me


Add plugin operators

This is a proposal for a new behaviour that allows to change card operators from the final command such that:
load_dataset("card=cards.wikitq,table_serializer=serializers.table.markdown")
will be loading the wikitq with different table serializer, markdown serializer in this case.

If I understand there are two changes here.

The ability to add constant fields to the datasets via the recipe (what happens If it overwrites an existing field?)
An operator PlugIn operators that by defaults apply an operator to the stream, but allows changes the operator.

The Plugin operator is a bit tricky to understand (even the example is).

A naïve question.. : Since the card is a json file, a simpler, and perhaps better understood way (addressing @yoavkatz concern) would be to first load that json file into a json object, then change that json object, and use the edited version as the input to the recipe?
Or the card must be instantiated via fetch_artifact?  can that ad-hoc edited card be added to the catalog via add_card?


Help: expect() macro selects from actual table instead of mocking select query

Hi,
thank you for a truly great and super helpful module!
I am just getting my hands dirty with dbt unit testing, so might be missing or misinterpreting some concepts.
Disclaimer:  using redshift db engine.
My problem is the following:
For some reason dbt_unit_testing.expect() selects from the actual dwh table instead of a mock select query.
Lets say this is my model that i am trying to test (might not make sense to test it, but there is something very confusing about it)
select
    {{ select_star(from=api.Relation.create(database=target.database, schema="staging", identifier="session_status_proposals_v"))}},
    '{{var("tenant_name")}}' as tenant_name
from {{ ref("session_status_proposals_v") }}
{% if get_adapter_type() == 'redshift' %}
union all
select
    {{ select_star(from=api.Relation.create(database=target.database, schema="staging", identifier="session_status_proposals_us_v"))}},
    'us' as tenant_name
from {{ ref("session_status_proposals_us_v") }}
{% endif %}

Rather a simple union of 2 tables.
Here is my test:
-- depends_on: [{{ ref('session_status_proposals_v') }}, {{ ref('session_status_proposals_us_v') }} ]
{{ config(tags=['unit-test']) }}
{% set options = {"include_missing_columns": true} %}

{% call dbt_unit_testing.test('session_status_proposals_union_s', 'should verify that both tenants exist in the final table') %}

  {% call dbt_unit_testing.mock_ref('session_status_proposals_v') %}
        select
        'comment_1' as comment,
        'created_at_1' as created_at,
       <rest of the table columns>
 {% endcall %}

  {% call dbt_unit_testing.mock_ref('session_status_proposals_us_v') %}
    select
        'comment_1' as comment,
        'created_at_1' as created_at,
       <rest of the table columns>
  {% endcall %}

  {% call dbt_unit_testing.expect() %}
    select
       'comment_1' as comment,
        'created_at_1' as created_at,
       <rest of the table columns>

        union all

         'comment_1' as comment,
        'created_at_1' as created_at,
       <rest of the table columns>
  {% endcall %}
{% endcall %}

But instead of comparing 2 rows with 2 rows and outputting a success message, it does something different, so i get an error message
19:55:52.983432 [info ] [Thread-1  ]: ERROR: Number of Rows do not match! (Expected: 2, Actual: 442141)
19:55:52.983848 [info ] [Thread-1  ]: ERROR: Rows mismatch:

due to the fact that it compares 2 mock input rows with expected data which turned out to be the entire dataset of 44K rows.
I thought screenshot would make more sense to demonstrate the issue

In my attempt to debug and understand the problem, i cloned the current repo and tried to reproduce my test using jaffle-shop data:
query (added stg_calls created with identical query as stg_orders)

select
{{ select_star(from=api.Relation.create(database=target.database, schema="s_staging", identifier="stg_orders"))}},
'eu' as tenant_name
from {{ ref('stg_orders') }}
union all
select
{{ select_star(from=api.Relation.create(database=target.database, schema="s_staging", identifier="stg_calls"))}},
'us' as tenant_name
from {{ ref('stg_calls') }}

using the following test:
-- depends_on: {{ ref('stg_calls') }}
-- depends_on: {{ ref('stg_orders') }}

{{ config(tags=['unit-test']) }}
{% set options = {"include_missing_columns": true} %}

{% call dbt_unit_testing.test('orders', 'should verify that both tenants exist in the final table') %}

  {% call dbt_unit_testing.mock_ref('stg_calls') %}
    select
        50 as customer_id,
        '2018-01-05 00:00:00.000' as order_date,
        54 as order_id,
        'completed' as status,
        '1' as rn
  {% endcall %}

  {% call dbt_unit_testing.mock_ref('stg_orders') %}
    select
        54 as customer_id,
        '2018-02-25 00:00:00.000' as order_date,
        52 as order_id,
        'return_pending' as status,
        '2' as rn
  {% endcall %}

  {% call dbt_unit_testing.expect() %}
    select
        50 as customer_id,
        '2018-01-05 00:00:00.000' as order_date,
        54 as order_id,
        'completed' as status,
        '1' as rn
        union all
        select
        54 as customer_id,
        '2018-02-25 00:00:00.000' as order_date,
        52 as order_id,
        'return_pending' as status,
        '2' as rn
  {% endcall %}
{% endcall %}

But doing so works properly, test pass and expect() selects from the mock select query
.
In both case i used same redshift cluster, dbt 1.3.0.
Tried looking into the source code and understand the macros, but that didnt help.
Any idea what it`s not working as expected? Am i missing something?
Any hints which direction i should be looking at are much appreciated.
Thank you!
Best, Mike

Hi @mike-bolshakov, it looks like you are not using "dbt-unit-testing.ref" in your models. If that's the case, you need to redefine the ref macro as explained here in the README.
Please let me know it it helps

@psousa50 thank you for pointing that out, that was indeed the issue. I do not know how i missed that.
Thank you very much!

no worries, glad that you find the module useful 🙂


Plugin Freezes?

Hi,
i now had it two times, that the plugin doesn't refelct changes i make in the original app.
I needed to restart homebridge to get it working again. There was no error in the log.
Any idea?

There maybe a hint to why in the debug logging if you want to try and look at that. It may be that the connection used for the live updates gets closed and is not reconnecting on its own. I can try and reproduce this by dropping the network. I assume this is installed on a system that never sleeps?

Yes. This is a Raspi connected by LAN. Let me know how i can help.

I was able to replicate and resolve this. You can test this yourself by dropping your network connection and watching the logs.

Tested. And you where right. I restarted the router prior to the connection losses due to updates. Now its working also after it was offline. Thank you!


How to change login error message?

when login with wrong password, it always got this error message: Oh snap!
Something went wrong.
Is this message supposed to be? How can i customize the error message? Thanks!

You may take a look at https://akveo.github.io/nebular/docs/auth/configuring-ui#custom-ui-components

Hi @joeyjin , did your issue resolved?

If not, please, reopen issue in the nebular repo.

After a deep search in @nebular/auth files I figure out how to do it, you have to override the getter method of the errors of the used strategy, here is an example:
NbPasswordAuthStrategy.setup({
  name: 'username',
  token: {
    class: NbAuthJWTToken,
    key: 'token',
  },
  baseEndpoint: '/api',
  login: {
    endpoint: '/auth/login',
    method: 'post',
  },
  logout: {
    endpoint: '/auth/logout',
    method: 'get',
  },
  errors: {
    getter: (module, res, options) => {
      return res.error ? res.error.message : options[module].defaultErrors;
    },
  },
})

@bacali95 Do you have any examples of how you did this, I'm facing the same issue.

@bacali95 Do you have any examples of how you did this, I'm facing the same issue.

Here is an example:
NbPasswordAuthStrategy.setup({
  name: 'username',
  token: {
    class: NbAuthJWTToken,
    key: 'token',
  },
  baseEndpoint: '/api',
  login: {
    endpoint: '/auth/login',
    method: 'post',
  },
  logout: {
    endpoint: '/auth/logout',
    method: 'get',
  },
  errors: {
    // Override the getter of errors functions
    // res: is the HttpResponse that you get from your backend
    getter: (module, res, options) => {
      return res.error ? res.error.message : options[module].defaultErrors;
    },
  },
})

Oh! Nice, it works!

After a deep search in @nebular/auth files I figure out how to do it, you have to override the getter method of the errors of the used strategy, here is an example (where res is the HTTP response of the login request):
NbPasswordAuthStrategy.setup({
  name: 'username',
  token: {
    class: NbAuthJWTToken,
    key: 'token',
  },
  baseEndpoint: '/api',
  login: {
    endpoint: '/auth/login',
    method: 'post',
  },
  logout: {
    endpoint: '/auth/logout',
    method: 'get',
  },
  errors: {
    getter: (module, res, options) => {
      return res.error ? res.error.message : options[module].defaultErrors;
    },
  },
})

This is the best answer!


Scatter and Signal plots fail for data containing double.NaN

If data contains even a single double.NaN value, the entire plot fails to render properly. How should double.NaN be handled? Perhaps it could indicate data points which should not be rendered (#202)

[ ] GetLimits() in every Plottable should be modified to ignore double.NaN
[ ] Render() in every Plottable should be modified to not render double.NaN

Problem code:
double[] xs = new double[] { 1, double.NaN, 3, 4, 5, 6 };
double[] ys = new double[] { 1, 4, 9, 16, double.NaN, 36 };
var plt = new ScottPlot.Plot();
plt.PlotScatter(xs, ys);
plt.SaveFig("test.png");

Current output:

I worked with LabVIEW graph control very a lot .
LabVIEW graph controls do ignore NaN while drawing a line/curve.
In case a NaN in the middle of an array, both sides are render while a span left  between them.


Multilevel json objects are not parsed beyond the first.

Here is my test path to reproduce.
=universe_systems_system(31001688, en-us, true)
The planets cell has unparsed data.
[{"planet_id":40438381},{"planet_id":40438382},{"planet_id":40438383},{"planet_id":40438384},{"moons":[40438386],"planet_id":40438385},{"moons":[40438388],"planet_id":40438387},{"moons":[40438390,40438391],"planet_id":40438389},{"moons":[40438393],"planet_id":40438392},{"moons":[40438395,40438396,40438397,40438398,40438399,40438400,40438401,40438402,40438403,40438404,40438405,40438406,40438407,40438408,40438409,40438410,40438411,40438412,40438413],"planet_id":40438394},{"moons":[40438415,40438416,40438417,40438418,40438419,40438420,40438421,40438422,40438423,40438424,40438425,40438426,40438427,40438428,40438429,40438430,40438431,40438432,40438433,40438434,40438435,40438436,40438437,40438438,40438439],"planet_id":40438414},{"moons":[40438441,40438442,40438443,40438444,40438445,40438446],"planet_id":40438440},{"moons":[40438448,40438449,40438450,40438451,40438452,40438453,40438454,40438455,40438456,40438457,40438458,40438459,40438460,40438461,40438462,40438463,40438464,40438465],"planet_id":40438447}]
I'm not sure if I understand it 100% correctly if there should be a planets column and a moons column etc.  But hopefully, this is enough to explain the issue.

This will be fixed in 7.0.0 when the add-on stuff gets released.


[ARM] az policy assignment: Updated policy SDK and support user assigned MSI on policy assignment

Description

Updated azure-mgmt-resource SDK to version 20.0
Updated policy api-version to 2021-06-01 in the shared profile
Updated az policy assignment [identity] to support user assigned MSI
Added corresponding test to verify user assigned MSI support
Fixed remediation test async wait issue
Fixed policy management group level test which shouldn't append compute RP resource to MG scope

Testing Guide

az policy assignment create --assign-identity MyAssignedId will create policy assignment with user assigned identity.
az policy assignment identity assign --identity MyAssignedId will add the user assigned identity to the policy assignment.

History Notes

[ARM] az policy assignment create and az policy assignment identity assign now support adding user assigned identity

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[X] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AzurePolicy

@yonzhan We want to catch Nov 2021 milestone.
We are under the push to support user assigned identity by Jan 2022 by big customers. We want to keep some buffer to catch the Nov 2021 if possible.

Add @zhoxing-ms to review this PR

@zhoxing-ms Thank you for reviewing the PR. I have updated the parameters according to the doc. I didn't change identity remove command because we don't support multiple MSI. I used the flag deprecate_info to hide the old parameter. However, I kept backward compatibility. So, no breaking change.


Fix migrate volume permissions

Description
This PR aims to correct the migrateVolume API permissions for the default users role. While the ACS UI currently only allows users with the roleType admin to perform volume migration, all default non-read-only roles have permission to use the migrateVolume API. However, this permission does not make sense for a common user, not even via API; to properly use migrateVolume it`s necessary to have knowledge about the cloud structure. Therefore, a common user should not be allowed by default to this API method.
We are not saying that somebody cannot create a custom role allowing such a process; however, we should not provide such a scenario by default, as it might lead to some unexpected behaviors and/or misuses of the cloud environment.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[x] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
The sql script was tested in a test db.

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6224 (SL-JID-1460)

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6224 (SL-JID-1695)

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6224 (SL-JID-2087)

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6224 (SL-JID-2321)

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6224 (SL-JID-2339)

Hey @DaanHoogland could you run the tests for this one?

@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_multiplication_x: el8 :heavy_check_mark: debian :heavy_multiplication_x: suse15. SL-JID 4264

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian Build Failed (tid-5004)

@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 4270

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-5012)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 41010 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6224-t5012-kvm-centos7.zip
Smoke tests completed. 102 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_08_upgrade_kubernetes_ha_cluster
Failure
613.28
test_kubernetes_clusters.py


WebDataset

Support WebDataset with --wds e.g. --wds "shard-{00000..00069}.tar".
Outputs to "{sample['__url__']}_{sample['__key__']}" e.g. shard-00000_00000_caption.json.
__url__ is processed for streaming WebDataset e.g. pipe:aws s3 cp s3://data/shard-00000.tar --endpoint-url https://00000000000000000000000000000000.r2.cloudflarestorage.com -, pipe:aws s3 cp s3://data/shard-00000.tar -:

split by  -- in case of endpoint-url
split by /

Testing

[x] Local tar files
[x] Streaming
[x] Linux

Closes #2

WebDataset streaming is working well in tests:

A40
Streaming from Cloudflare R2
<CAPTION> task
batch 14
num workers 4
17 images/s


Fix calling services by HTTP with query params in endpoint url

Given
Given a service definition with a method:
rpc Get(Query) returns (Item) {
    option (semaphore.api.http) = {
        endpoint: "/v2/?query=value"
        method: "GET"
    };
};

Result
The HTTP caller escapes the ? symbol with %3F, the query does not work (leads to a wrong URL).
Expected behavior
The ? symbold should not be escaped, the built URL has to look like http://example.com/v2?query=value

Codecov Report

Merging #124 into master will decrease coverage by 0.02%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #124      +/-   ##
==========================================
- Coverage   84.67%   84.64%   -0.03%
==========================================
  Files         109      109
  Lines        4947     4951       +4
==========================================
+ Hits         4189     4191       +2
- Misses        470      471       +1
- Partials      288      289       +1

Impacted Files
Coverage Δ

pkg/flow/caller.go
68.00% <0.00%> (ø)

pkg/transport/http/caller.go
78.00% <75.00%> (-1.17%)
:arrow_down:


kitty term info copy does not work

Describe the bug
Kitty has a shortcut to copy terminfo to target server
To Reproduce
Steps to reproduce the behavior:

... kitty +kitten ssh<EMAIL_ADDRESS>... error FileNotFoundError: [Errno 2] No such file or directory: 'infocmp': 'infocmp'

Expected behavior
Connected to the server
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Metadata

system: "x86_64-linux"
host os: Linux 5.2.8, NixOS, 19.09pre188690.8746c77a383 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-19.09pre188690.8746c77a383"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: kitty
# a list of nixos modules affected by the problem
module:

@shyim would you mind testing if #66817 fixes the issue for you (I use kitty on a daily basis and it appears to work fine with this patch).

Tested works. Thanks! ❤


Auth Support

I haven't been able to get swarm to work with a registry that requires authentication.  I logged in from each node, and from swarm itself but it keeps telling me image not found.  I can docker pull from each node individually and then launch them via swarm.  It also works fine with public images.
It might just not be implemented yet.  Are there plans to have auth support in the near future?  Thanks.

Hi @ahromis yes, we have plan to do it, currently it's unsupported because, swarm is actually pulling the images instead of letting the client pull.
This should be solved in #349
Cheers.

Same here. I built swarm locally from the latest master. It still fails.

@csabapalfi you'll have to docker pull first to pull your private image on all hosts

Yeah, I ended up with just doing docker pull locally on all swarm hosts via ansible.

I meant that you can do docker pull on swarm, it will pull on all boxes.

I built swarm from master and tried pulling an image from a private registry from the manager.  It looks like it tried the pull on all 3 swarm agents instead of giving a not implemented error, but each node still says authentication required.  I verified the nodes are all logged in and I can pull the image from the private registry on the nodes.  @vieux, it looks like you implied the pull should work so I just wanted to verify.

I can't pull against an a private, authenticated registry either.
It looks like swam isn't passing along the X-Registry-Auth header to the /images/create endpoint.  I think that's all that has to happen to make this work.

@etuttle pull will be fixed in #684

Has this been fixed yet ?
On OSX I would do:
 boot2docker ssh
 echo 'EXTRA_ARGS="--insecure-registry <YOUR INSECURE HOST>"' | sudo tee -a /var/lib/boot2docker/profile
 sudo /etc/init.d/docker restart

but this doesn't get applied to the docker-machine environment.

ping @vieux

I am trying to pull a private image via the remote api, but I get 500, but I have no idea what went wrong, does swarm support it?
[{"id":"swarm-master","status":"500 Internal Server Error: EOF\n","progressDetail"}]

Any news on this? This basically means swarm is quite inconvenient to use with private images on hub.docker.com. I wound up with the same solution mentioned above: pull directly from the hub for each of the nodes in the swarm individually, but that's quite clunky.

@sanga This is implemented by #1384 and will be included in a 1.0.1 most probably, but this depends on another PR in docker.

excellent. Cheers!

Its not 100% clear if this is solved, or when it is solved - the linked PR do not seem to have related information either.

Does anyone have a workaround for this other than disabling authentication on the registry?

@nishanttotla What is the state on this regarding engine-api, can this be closed?

I'm also interested in pulling from private registries on container creation. But it is not consistent with docker behaviour. Because of that systems that uses swarm transparently as it is just docker can't use that behavior.
Also there is no output of pulling because container creation API of docker doesn't provide output. Some system might get connection read timeout since pulling can take a lot of time on systems with high load of network.
So it would be better to add such a feature to engine-api of docker. This would solve all 3 issues:

transparent usage of Swarm as it is just docker
auth on container creation
streaming logs of pulling on container creaition

I do believe we discussed that quite long ago, but looks like it wasn't introduced in docker-engine.
Maintainers, have you discussed that feature with docker-engine maintainers? Are you/they OK with such a changes in docker API? If so community will be able to work on that.

Here is suggestion of that feature by @aluzzardi  https://github.com/docker/swarm/pull/1350#issuecomment-152112163

@garagatyi this looks like an independent discussion. Could you open a separate issue where we can discuss the best solution?
For the present issue, look at #2042 and #2272.

@nishanttotla Yes, sorry, I'll open new issue. And I checked container creation with X-Registry-Auth header and private repo on latest swarm/docker 1.11 - everything works.
So @abronan  +1 for closing that issue.


GUACAMOLE-1980: Update client versions to 1.6.0.

Need to also bump:
https://github.com/apache/guacamole-client/blob/addac2a263190d028501d191fb455d60d71c6a14/guacamole-common-js/src/main/webapp/modules/Version.js#L30

It's done


[Event Hubs Client] Added credential rotation for Shared Access Keys (#6618)

Hello @jsquire
Hope you are well,
Opening a Draft PR with what discussed

Can one of the admins verify this patch?

As a note, please bear with us if we're a bit slow to engage the next week or so; we're coming up against a deadline and the holidays.

No worries. Hit the deadline, I will be cheering for you, and please enjoy your well deserved holiday.

Other than fixing up the conflicts from the churn during my lag, I think we're good to go here. I left one response that you may need to kick me on if I am indeed overlooking something.

I think we should be good to go. Thank you a lot for this opportunity and all your help.

I think we should be good to go. Thank you a lot for this opportunity and all your help.

.... and we're merged.    It is we who should be thanking you.   You continue to be a fantastic member of the extended Event Hubs team and your efforts are very much appreciated.


RSDK-3379 - add modular resource docs

Ticket: RSDK-3379
This PR updates the docs to include directions on how to add a modular resource using the Python SDK.
Please note that there is another ticket RSDK-3836 that aims to make this doc to be more parallel to the one we have in our actual docs.

can you also change the instance of from typing import Self to from typing_extensions import Self

its in examples/module/src/arm/my_arm.py

Apologies for the lack of input - this does look great!


Add Support for Visualizing Dynamic Schema Fields in Attu

Describe the feature:
The proposed feature would involve enhancing the Attu interface to support the visualization of dynamic schema fields in Milvus collections. Currently, collections in Milvus can evolve with dynamic schemas, but these changes are not reflected in the Attu UI. The feature would allow Attu to display all fields of a collection, including those that are dynamically added or altered after the initial schema is set up.
Describe a specific use case for the feature:
In the current scenario, when dynamic fields are added to a Milvus collection, the only way to view and interact with these fields is through the Milvus SDK. Developers and data scientists must write and execute custom code to retrieve and view this information, which can be cumbersome and time-consuming. For example, when a new set of features is added to a collection as part of a data update process, users have to rely on the SDK to access the updated schema and the new data points.
This process lacks the convenience and immediacy of a visual tool. With the addition of this feature to Attu, users would be able to immediately see the updated schema and corresponding data directly within the Attu interface, without the need for additional coding. This would streamline workflows for users who need to manage and explore evolving datasets, making it easier to verify and understand the structure of their data in real-time.

which version of attu are you using?

I apologize for still using version 2.3.1, I didn't notice the update.


physfs: fix-up CONTROL for v3.0.1

Updated [Version] string in CONTROL to match current version in /ports/physfs/portfile.cmake:
Source: physfs
Version: 3.0.1
Description: a library to provide abstract access to various archives
Build-Depends: zlib

Thanks for the fix!

You are most welcome <3 I really love vcpkg and the Microsoft team is doing excellent, its what Windows has needed for so long now <3


Bump pyarrow from 3.0.0 to 6.0.0 (for M1 mac installations; duplicates #740)

⚠ Note

(hopefully) Working duplicate of #740 (thanks to #741)

TL;DR
Updates the pyarrow dependency to 6.0.0 for easier flytekit installation on M1 macs.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

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

Complete description
Previously, installation on M1 macs required pyarrow to be built from source since no prebuilt arm64 wheels were available for the 3.0.0 version. This build, in turn, depended on the 3.0.0 version of the Apache Arrow library (pyarrow's build system had breaking changes between 3.0.0 and 4.0.0). Apache Arrow can be installed via brew, but only the 6.0.0 version is currently available. This meant that users had to also build the Apache Arrow library from source (and remember to set the correct LDFLAGS and CFLAGS, etc.) prior to building pyarrow.
Since pyarrow version 6.0.0 includes prebuilt wheels for the arm64 architecture, simply upgrading the pyarrow dependency version to 6.0.0 elides the above steps, yielding a much more pleasant flytekit installation experience.
Tracking Issue
NA
Follow-up issue
NA

cc @cosmicBboy / @eapolinario

Just kidding, it looks like #741 needs to be in the latest release for compatibility.
Error message (similar to https://github.com/flyteorg/flytekit/pull/740#issuecomment-962260781):
2021-11-09T00:52:36.5537204Z E           #11 16.03 The conflict is caused by:
2021-11-09T00:52:36.5537762Z
2021-11-09T00:52:36.5538445Z E           #11 16.03     The user requested pyarrow==6.0.0
2021-11-09T00:52:36.5539035Z
2021-11-09T00:52:36.5539756Z E           #11 16.03     flytekit 0.23.1 depends on pyarrow<4.0.0 and >=2.0.0

@TeoZosa we're going to cut a release of flytekit v0.24.0 tomorrow.  I just released https://github.com/flyteorg/flytekit/releases/tag/v0.24.0b2 though if you want to play around with it before that happens.

tests are failing because integration tests are failing because there's a version conflict.  but once this pr is merged, which we just did, and cut a release, we can regenerate the mock repo requirements file.

sorry about closing the other one. thanks!

No worries! I think it's awesome that the team is able get to and through these PRs so quickly. Thank you for all your hard work helping me get this PR merged!


sink(ticdc): use  an unbounded chan in conflict detector

What problem does this PR solve?

Issue Number: close #8255
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/merge

/run-all-tests

/run-dm-integration-tests
/run-kafka-integration-tests

/run-verify-tests
/run-engine-integration-tests

/run-kafka-integration-tests