Add machinery for printing major deprecations

First step towards handling all of #4695
\c @RochesterinNYC @indirect

@indirect r?

@homu r+

:pushpin: Commit 53737e0 has been approved by indirect

:hourglass: Testing commit 53737e0 with merge 81f96b9...

:broken_heart: Test failed - status

@homu r=indirect

:pushpin: Commit 2cc7c46 has been approved by indirect

@homu r=indirect

:pushpin: Commit 2cc7c46 has been approved by indirect

:bulb: This pull request was already approved, no need to approve it again.

:bulb: This pull request was already approved, no need to approve it again.

:zap: Test exempted - status

Please reconsider removing clean_env ... it's not a nice api and has known drawbacks, but forcing others to re-implement it is not helping either.
There is no clean way of removing bundler from them ENV, but it is needed for some usecases like restarting an app with exec like puma does or shelling out with a clean environment from inside a bundle exec call ...
@indirect

@grosser why would you not use original_env instead?

because it still includes BUNDLE_GEMFILE / RUBYLIB etc

bundle exec ruby -e 'puts Bundler::ORIGINAL_ENV'

the more common case would be bundle exec rake / bundle exec puma ... bundle exec ruby could be re-written to ruby -rbundler/setup -e 'puts Bundler::ORIGINAL_ENV' and would work ... but the others don't

Ugh, that seems like a bug. :/ I agree that we should either fix original_env to provide access to the pre-bundler env or keep clean_env, though.

agreed!

... stupid idea to fix the bug: serialize ORIGINAL_ENV into ENV['BUNDLE_ORIGINAL_ENV'] when calling bundle exec ...

@grosser please open a new issue to discuss this! This PR was merged a year ago and was simply porting things that were implemented on the 1-99-dev branch before


Add Xbox Wireless Controller (Daystrike Camo Special Edition)

I got this sweet new red camo Xbox controller and was surprised to find it was not mapped correctly for SDL2 games, specifically testing on RetroPie.

Xbox Wireless Controller, Daystrike Camo Special Edition, M1139678-001
I used SDL2's controllermap application to create a mapping and found it working perfectly thereafter.

Thanks !


优酷（youku）drm加密的视频无法下载，使用YouTube Downloader

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a new site support request
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that none of provided URLs violate any copyrights or contain any DRM to the best of my knowledge
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and am willing to share it if required

Region
中国
Example URLs
https://v.youku.com/v_show/id_XNjM3Nzc2ODA2MA==.html?spm=a2h0c.8166622.PhoneSokuProgram_1.dselectbutton_1&showid=bcafecf27d504fbc8788
Provide a description that is worded well enough to be understood
https://v.youku.com/v_show/id_XNjM3Nzc2ODA2MA==.html?spm=a2h0c.8166622.PhoneSokuProgram_1.dselectbutton_1&showid=bcafecf27d504fbc8788
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
https://v.youku.com/v_show/id_XNjM3Nzc2ODA2MA==.html?spm=a2h0c.8166622.PhoneSokuProgram_1.dselectbutton_1&showid=bcafecf27d504fbc8788

Sadly, yt-dlp does not support DRM encrypted files.


chore: add NOTES.txt for fullstack-deployment helm chart

Description
This pull request changes the following:

Add NOTES.txt for fullstack-deployment helm chart

Related Issues

Closes #321

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add support for parsing integer types

Draft for feedback please, and also because on top of #67.
Add support to the library for parsing standard integer types u8, u16, u32, and u64.
Note we allow but do not enforce 0x prefix.
If this gets a concept ack we could then do from_maybe_prefixed_hex, from_prefixed_hex, and from_no_prefix_hex` for explicit handling if wanted.

There is no appetite for this at the moment.


Reintroduce Openshift SCC to the logging-operator chart

Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.

A user noticed that the OpenShift SCC resources disappeared and would like to still have it: https://github.com/kube-logging/logging-operator/pull/1167

I just realized, that this is something to be added to the actual logging operator code, it doesn't have a good place in the chart as it belongs to the aggregator instead of the logging operator deployment itself. I have to defer this to the next release.


Add maintenance mode to faucet

#420  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jvmi7 and the rest of your teammates on  Graphite


Number of bits to be flipped to interconvert two numbers.

💥 Proposal
Number of bits to be flipped to interconvert two numbers.
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign


Compound nodes positioned off grid

With default options, a compound node's children will all nicely align with the grid and the compound node margins will also be modified to nicely align with the grid. See here:

And when you drag child nodes of the compound, they keep nicely aligning with the grid. However, when you drag the compound, sometimes, the compound gets positioned off the grid (resulting in children not properly aligning with the grid). See below:

It seems more stable now. May you confirm?

Looks fine!


Getting error: "Error (1): No results to format" when trying to get the entity data

https://confluence.internal.salesforce.com/display/PLATFORMDX/Adding+2GP+Managed+Packaging+metadata+channel+support
I'm following this doc to have my entity be supported for packaging, and I have registered the entity (AffinityScoreDefinition) to the CLI in this repo, but I'm still getting that error when I run these commands:
sfdx force:mdapi:convert -r  -d force-app/
which I believe should have resolved once my metadatype was registered (https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json).
Can't find any information on slack about this, can anyone help?

{
"architecture": "linux-x64",
"cliVersion"<EMAIL_ADDRESS>"nodeVersion": "node-v20.11.1",
"osVersion": "Linux 5.14.0-362.18.1.el9_3.x86_64",
"rootPath": "/nix/store/5vxg9jzr8phqayd1rrl124mnc7xrpggp-sfdx-7.209.6",
"shell": "bash",
"pluginVersions": [
"@oclif/plugin-autocomplete 3.0.13 (core)",
"@oclif/plugin-commands 3.2.0 (core)",
"@oclif/plugin-help 6.0.18 (core)",
"@oclif/plugin-not-found 3.0.14 (core)",
"@oclif/plugin-plugins 4.3.8 (core)",
"@oclif/plugin-search 1.0.20 (core)",
"@oclif/plugin-update 4.2.0 (core)",
"@oclif/plugin-version 2.0.14 (core)",
"@oclif/plugin-warn-if-update-available 3.0.14 (core)",
"@oclif/plugin-which 3.1.5 (core)",
"@salesforce/cli 2.34.7 (core)",
"apex 3.0.31 (core)",
"auth 3.3.27 (core)",
"data 3.1.11 (core)",
"deploy-retrieve 3.2.35 (core)",
"info 3.0.33 (core)",
"limits 3.1.14 (core)",
"marketplace 1.0.29 (core)",
"org 3.5.0 (core)",
"packaging 2.1.12 (core)",
"schema 3.1.9 (core)",
"settings 2.0.31 (core)",
"sobject 1.1.20 (core)",
"source 3.1.22 (core)",
"telemetry 3.1.17 (core)",
"templates 56.0.23 (core)",
"trust 3.3.17 (core)",
"user 3.3.4 (core)"
]
}

your type was included in SDR v10.7.0 (and a small fix about the suffix included in 10.7.1):
https://github.com/forcedotcom/source-deploy-retrieve/blob/main/CHANGELOG.md#1071-2024-04-01
The CLI needs to use that SDR version (or higher) to recognize the type in your project.

"deploy-retrieve 3.2.35 (core)",

the force:mdapi:convert command is part of the deploy-retrieve plugin, v3.2.35 is using SDR 10.5.3 so that explains why it doesn't work.
The available nightly has SDR v10.7.0 but it may not work because of the suffix fix, maybe wait for tomorrow to get the new nightly and try again?:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli_rc.htm

Updating the nightly worked for me -- thank you!


Update bulk upload guide PDF

Updated file reflecting sex assigned at birth requirement here: https://app.zenhub.com/files/302387839/76e0afbe-3a02-46b1-8f14-5ccbd60fa7fd/download

@nickclyde Any chance we can get this up today?

sure thing!

@LGFranklin PR is up: https://github.com/CDCgov/prime-simplereport-site/pull/262


feat!: Add support for multiple options in Select

Adds support for selecting multiple options in the Select component using closable tags.
This should close https://github.com/thaw-ui/thaw/issues/101
https://github.com/thaw-ui/thaw/assets/16362377/a9e98c60-31a9-4c7c-8281-ec6dd6548b67
Issues:

Since this changes the type of value in the Select component, it means this PR is a breaking change.
The popup menu doesn't update it's position when the multiselect gets too long and goes onto two lines. (Fixed with https://github.com/thaw-ui/thaw/pull/166/commits/d0e96ebe7f8318861d4177134ac6be6c7dffbe60)

I was considering that, it would also mean it's no longer a breaking change. Though I'm not sure how this could be done without duplicating so much of the code?

like  https://www.naiveui.com/en-US/os-theme/components/select#max-tag-count.vue ?

Hmm not really limiting, I mean more like custom render function for the label itself.
https://ant.design/components/select#select-demo-custom-label-render
For users who want to render anything they want. In my personal use case, I want a filter called "Bookmakers", and I don't want to render all the bookmakers selected, instead I only want to show the number of bookmakers selected.
[ Bookmakers (3) ]
- [x] Betfair
- [x] Sportsbet
- [x] Tab
- [ ] Pinnacle

This could be done with something like:
view! {
    <MultiSelect
        label=|values| view! { {format!("Bookmakers ({})", values.len()) }
        values
        options
    />
}

We can do this by adding a label slot.
view! {
    <Multiselect
        values
        options
    >
         <MultiselectLabel slot>
              {format!("Bookmakers ({})", values.len())
        <MultiselectLabel>
   </Multiselect>
}

@luoxiaozero I've separated them into separate components. I also renamed it from MultiSelect into SelectMulti so it would be found in the docs beside Select (alphabetical).
I also implemented the SelectLabel slot for the selects.
We should also probably include a dropdown arrow in the select component. But maybe that can be a separate PR?

Great I've pushed another commit with these changes

Actually I've just gone ahead and added the dropdown arrow to the select component. Was quite a simple task so thought I'd add it here.

I'm just trying to debug why it's looking a little different in my personal project when using this fork. The alignment isn't correct.

I've been digging through the styles but not sure what's different.

I'd also like to share this screenshot of what I've implemented in my project where I'm using this fork and the <SelectLabel slot> slot to customize the label.

It's an alternative version of the multi select, where it has a label, and shows a <Tag> beside it with the number of items selected. Perhaps something like this might be of interest to people in the future?


Upgrade cadvisor to v0.44.0 and fix metrics collection under cgroups v2.

Description of the issue
Upstream Cloudwatch Agent uses cadvisor v0.36.0 and is unable to retrieve metrics on hosts running cgroups v2. See https://github.com/aws/amazon-cloudwatch-agent/issues/430.  cadvisor v0.44.0 fixes the metrics collection but is not a stable release and the upstream project will not release an upgrade until v0.44.0 moves out of pre-release.
Description of changes
This upgrades cadvisor to v0.44.0 and handles a small breaking change.
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Deployed to our production fleet.

This seems to be fixed in the latest release 0.0.13 which uses cadvisor 0.44.0

We have updated to version 0.13 of the image and this appears to be fixed.


Teach the library to automatically handle cursors

Now that the search endpoint handles cursorMark, we should be able to introduce a cursor=true parameter, and then have the library automatically create a .next() function that continues to traverse the stack.
This would be preferred over the dirty way I threw together at https://gist.github.com/ecaron/1e4851492d58db66ef4c1ef53010234a

I think this is halfway covered by the newasStream functions, but its not quite.
Having something like result.next() would allow the next page of results to be called manually and could be useful for certain applications.
Leaving this open for now.


[BUG] EventReceiveError: 'At least one receiver for the endpoint is created with epoch of '0''

Library name and version
Azure.Messaging.EventHubs 5.9.2
Describe the bug
In the last couple of months, this error has started showing up in the logs:
'At least one receiver for the endpoint is created with epoch of '0', and so non-epoch receiver is not allowed. Either reconnect with a higher epoch, or make sure all epoch receivers are closed or disconnected.'
It first started on May 31 which exactly coincides with an update of the azurefunctions SDK from version <IP_ADDRESS>14 to version <IP_ADDRESS>99.
We get around 5000 of these error messages every day in the log. As a reference, we have around 100 million outgoing messages per day from the event hub.
We have a function app with several functions that use EventHubTrigger to consume events. In addition, we are explicitly using EventProcessorClient in one function. For that latter case, we create and reuse one EventProcessorClient throughout the app's lifetime.
We have 18 consumer groups in the event hub, not counting the default one which we don't use. Each consumer group is only used in one place in the code.
The event hub has 6 partitions, but I noticed that the message is only reported on partition ID 0.
The error indicates we are trying to register a non-epoch receiver, but I have scanned the code and haven't found anything like that.
The function app is allowed to scale out to 10 instances.
Expected behavior
No exceptions of this type in the log
Actual behavior
Around 5000 of these errors in the log every day.
Reproduction Steps
Haven't been able to reproduce this locally.
Environment
Azure functions v4 in-process
.NET 6

Hi @ben-hamida.  The message that you're seeing indicates that there are multiple readers asserting exclusive access to a partition for a consumer group.  This is normal and expected when instances are scaling up/down for 1-3 minutes after the scaling activity triggers.
In your scenario, if the EventProcessorClient that you're using uses the same consumer group and Event Hub that you've asked the trigger to use, you have very likely created contention for ownership.  Unless you're explicitly using the same exact Blob Storage container that the trigger is, your processor would not see the ones used by the trigger instances and would start claiming ownership and would be fighting with the trigger for exclusive access.
Generally, there's no good pattern for hosting EventProcessorClient directly in Functions and we would strongly recommend not doing so.   If you're looking to receive and process events in a Function, we would recommend using the trigger, which manages an event processor on your behalf and ensure.  Even if you create it as static, the instance of the Function that hosts it is ephemeral and will go idle or change hosts unless you're using a dedicated plan with "Always on" enabled.   You will either see either contention with fighting over ownership or delays in processing in other configurations or plans.
Can you please let us know:

Are you seeing these messages constantly or only as the Function is scaling?
Are all of the Functions using a trigger and configured for the same Event Hub / consumer group pairing also pointed at the same storage account?
Is the EventProcessorClient that you are managing directly using the same Event Hub / consumer group pairing as the triggers?
Is your Function application that manages an EventProcessorClient running on a dedicated plan with "Always On" enabled?

Hi @jsquire, That's what I would expect if the message was indicating that a receiver with an epoch smaller or equal to the current reader was created. In fact, we have filters in place to remove such messages from our logs. But this message, specifically the 'non-epoch receiver is not allowed' part, indicates that a non-epoch receiver is being created. How is this possible? Don't both EventHubTrigger and EventProcessorClient use epoch-receivers?
The reason we are usingEvenProcesserClient: We have a function that is timer triggered that reads events from the event hub and writes to a Cosmos database based on those events. The reason for a timer trigger rather than the EventHubTrigger is that the latter scales out unpredictably, and we want to be able to control the write speed to Cosmos to avoid rate limiting where possible.
Answers to your questions:

We are getting these messages constantly and I don't see a correlation to when the function is scaling.
All of the functions are using different consumer groups. There is one function app with the majority of the functions, and there is one other function app with a single function. The two function apps point to different storage accounts, but as mentioned, none of the functions share consumer groups for their triggers.
The EvenProcessorClient uses a different consumer group.
No, "Always On" is not enabled.

@ben-hamida:  The processor uses non-epoch readers to validate connectivity and permissions when first starting up (as part of the StartProcessingAsync call chain), they expect to be denied if something is already reading the partition - the error is handled internally and considered a successful validation.  This stage of validation is a single read operation, performed once, and generally takes between 125-250ms to complete.
If you're seeing these repeatedly and you're not scaling or having instances fight over partitions, then either a processor instance is being started as frequently as you're seeing the messages or there's another reader (which is not an event processor) attempting to use the consumer group.   Assuming you're inquiring about logs captured for your specific Functions application, the latter case seems unlikely.   That may be your static processor being started/stopped by the timer (or a new instance of the timer Function being created)  or may be the Functions runtime moving instances around or auto-scaling.
Are you seeing the names of the receiver in those error messages?   The processor itself can be assigned an identity and uses a GUID if none is provided.   The startup validation uses a reader with the pattern "SV-<< Processor Identifier >>".   If you assign your static processor a unique name that you can identify with a random component, that should help to identify whether its the startup spammer.

@jsquire I did some deeper investigation and it seems that the error message occurrence is correlated with the function app scaling after all. I found a stretch of one hour where the function app wasn't scaling and there were no error messages logged during that time.
My outstanding questions are:

Why did this start to happen on 31 May when the functionapp SDK version <IP_ADDRESS>99 was deployed? Was this log message added then or was there some other behavioral change?
Why is the log only reported on partition ID 0? (there is not a single instance with prop__partitionId != 0)
Is it ok to just completely ignore these messages in the future?
It seems like a bug that this message is logged at all since it's part of a valid workflow and not an error. Is it something that will be fixed?

If there are instances where this message represents a real error, it will be hard to detect with all the noise. It would be nice if the sdk stopped logging the messages when it's part of a valid workflow, or alternatively, if we had a way to distinguish them from real errors so that we don't accidentally filter out error messages that represent real issues.

@jsquire Thank you for your support, this was very informative. We will go ahead and filter out those messages from our logs.
Looking forward to when that filtering infrastructure is in place. We've had several instances of unwanted/false positive logs from the core libraries.


Confusion

What is a meme?

Memetics is the study of information and culture based on an analogy with Darwinian evolution. Proponents describe memetics as an approach to evolutionary models of cultural information transfer. Critics regard memetics as a pseudoscience. Memetics describes how an idea can propogate successfully, but doesn't necessarily imply a concept is factual.
from https://en.wikipedia.org/wiki/Memetics

oh, I think this rep should be downright removed from GitHub. This rep is part of a larger hierarchal structure that promotes white supremacy/culture by spreading "memes" around the entire world portraying the white colonialist era.  You destroy the culture and dignity minorites such as African Americas, for example, by marking blackness as an ultimate downfall since most memes refer to a darker tone in a negative context. Please delete this rep !

no me

taking one for the team


adding functionality for a events parameter

Issue #26
Adding functionality for an event parameter to be used

@mrsnippy Thank you. Do you know when that is being released?


To Index or Not to Index

Indexes creation and data population in the Neo4j v5 have been time-consuming and causing startup issues. Evaluate and find out if we really need the indexes for search performance needs and when to use indexes, and try to avoid over-indexing.

Two containers on DEV, one with indexes (the current instance from May 8th) and one without (ubkg-neo4j-hmsn-no-indexes09MAY2024.zip)
Choose a set of frequently used queries and some less frequent ones
Profile the above queries against the graph in each container and compare the execution time
Determine which type of index is necessary for improving the performance and which type is not

Primary goals:

Reduce the indexing effort (total 1865 indexes) that @AlanSimmons has to put into
Minimize the deployment failure rate caused by failed indexes
Find a cost-effective solution without sacrificing significant search performance

Whether 'tis nobler in the dev
to suffer the slings and arrows of outrageous Java exceptions
Or to take arms against a sea of indexes
And, optimizing, shrink them. To think--to guess,
No more; and by a guess to say we end
The heart-ache and the thousand error messages
That Docker's heir to: 'tis a consummation
Devoutly to be wished.


dts: Rename DT_HAS_NODE macro to DT_HAS_NODE_STATUS_OKAY

Rename DT_HAS_NODE to DT_HAS_NODE_STATUS_OKAY so the semantics are
clear.  As going forward DT_HAS_NODE will report if a NODE exists
regardless of its status.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Going to merge as this is timing out in CI, but seems to be passing all tests.


After submitting a proposal the form was still in Editing mode for a while until suddenly turning to View mode

Affected Portal:
Select one: Events ( maybe all )
Description:
I submitted the proposal https://events-committee.near.page/proposal/97, which I confirmed via my-near-wallet. After being redirected back to the portal, the proposal was still in editing mode for maybe 10 seconds before it suddenly switched to draft mode. That made me unsure if it was really submitted, and it was also confusing that it suddenly changed mode without any indication. There were no loading spinner or indication that submission was in progress.
User Type:
Specify: Regular User
Reproduction Steps

Create a proposal
Submit and approve it via web wallet ( my-near-wallet )
When redirected back to the page, observe that the proposal is still in edit mode
Observe that after some seconds it switches to view mode

Expected behavior
When redirected back from the wallet, the proposal should not be in edit mode, and it should be a progress indicator ( a spinner ) indicating that submission is still ongoing.
Priority
Select One: (P2) – Major inconvenience
Environment Details

Device: Desktop
OS: Mac
Browser Chrome
Version [e.g. 22]

Additional context
The reproduction of this issue should be possible in a playwright-test, where it would also be possible to create a video of it.
It also seems to happen something similar after marking the proposal ready for review, which when I did that, I was redirected back to this URL from the wallet: https://near.social/events-committee.near/widget/app?page=create-proposal&transactionHashes=4YWEHo5CSdKajEm43e9MJ1HjT8QJsxtg7BscoDxwpM2z It essentially brought me back to the create proposal form.

@ori-near please consider this for one of the coming iterations, I can look into the issue if you want to.


Net45 implementation of Settings

I use the .Net 45 MsTest for my unit testing framework.  This allows us to run CI in the cloud.
When I wrote a unit test that relied on Settings then it failed as there was only the portable implementation.
This pull request includes code for .Net45 project for the concrete implementation and additional msunit tests.
I have not changed any version information

Thanks for this!  It allowed me to add unit testing.

Is this PR in production, I am unable to launch unit test in my MsTest 4.5 project... having SystemNotImplementedException ??

This is not in production, but I will look into it. Take a look into testing: http://www.michaelridland.com/xamarin/best-practices-using-xamarin-plugins/ with plugins

Now integrated into latest version


Make sleep requirement clearer for rake tasks in one-off containers

Make the sleep requirement more clear/better visible for rake tasks in one-off containers

Thank you @johannesluedke


TestActor behaves unpredictably - looks like a static variable coupled with thread-race issue

This issue has a bit of a history in discord: https://discord.com/channels/974500337396375553/974500337954222133/1245403250841096325
Here is a copy of the discussion:
brah.mcdude — Yesterday at 6:47 PM
hi all.
i am running tests using Akka.Hosting.TestKit. I have a test that mostly passes. But randomly fails. I don't know why.
Here is the code:
public class Spec(ITestOutputHelper output) : TestKit(output, LogLevel.Debug)
{
    private IActorRef? myActor;

    [Theory]
    [InlineData(1)]
    [InlineData(2)]
    [InlineData(3)]
    [InlineData(4)]
    [InlineData(5)]
    [InlineData(6)]
    [InlineData(7)]
    public async Task Spec1(int _)
    {
        myActor.Tell(new { });
        await ExpectMsgAsync<object>();
    }

    protected override void ConfigureAkka(AkkaConfigurationBuilder builder, IServiceProvider provider)
    {
        builder.WithActors((system, registry, resolver) =>
        {
            var props = resolver.Props<MyActor>();
            myActor = system.ActorOf(props, nameof(MyActor));
            registry.Register<MyActor>(myActor);
        });
    }

    public class MyActor : UntypedActor
    {
        protected override void OnReceive(object message)
        {
            Sender.Tell(new { });
        }
    }
}

Here is the log of the failure:
Failed: Timeout 00:00:03 while waiting for a message of type System.Object
brah.mcdude — Yesterday at 7:51 PM
ok. found out the cause of the issue. for some reason, we need a probe:
        var probe = CreateTestProbe();
        myActor.Tell(new { }, probe);
        await probe.ExpectMsgAsync<object>();

Should i report it as a bug?
Aaronontheweb — Yesterday at 7:53 PM
I think I know what your issue is
https://github.com/akkadotnet/Akka.Hosting/issues/237
GitHub
Akka.Hosting.TestKit: TestActor is no longer the implicit sender ...
Version Information Version of Akka.NET? 1.0.3 Which Akka.NET Modules? Akka.Hosting.TestKit Describe the bug foreach (var i in Enumerable.Range(0, 2)) { var update1 = Dsl.Update(CounterKey, GCounte...
Akka.Hosting.TestKit: TestActor is no longer the implicit sender ...
a very annoying bug with the TestKit
in Akka.Hosting
brah.mcdude — Today at 1:08 AM
unlikely. my tests mostly pass. 80% of the time. it can't be something like "wrong sender". as that would always fail.
brah.mcdude — Today at 1:58 PM
my intuition is that there are static variables. maybe the test-actor is static. and that only multiple tests running asynchronously are causing the issue.
brah.mcdude — Today at 3:18 PM
i'll open a bug to discuss this.
Aaronontheweb — Today at 4:40 PM
that actor context bug is a thread static variable
and the conditions under which you can lose that context can be racy
so I suspect that's what it is - have run into it myself using the Akka.Hosting.TestKit before

here is another example of an implicit use of the test-actor that gives unpredictable results:
/// this code gives unpredictable results:
        var status = await actor.Ask<Status>(GetStatus.Instance);

/// until this issue is resolved, the code above should be replaced with this code:
        probe = CreateTestProbe();
        actor.Tell(GetStatus.Instance, probe);
        var status = await probe.ExpectMsgAsync<Status>();

I'm attempting to reproduce this today and it looks like I no longer can - everything seems to be working ok even with "run until failure" using v<IP_ADDRESS>

This makes me wonder if this was an xUnit issue possibly

Yes, it looks like this was an issue that was fixed in xUnit 2.8.0, which we upgraded to in June as part of https://github.com/akkadotnet/Akka.Hosting/pull/463

Welp, I take that back - was able to reproduce the failure with
   [Fact]
    public async Task ShouldAllowDuplicatePauseCommands()
    {
        // arrange
        var cohortId = TestCohortId;
        var cohortActor = await ActorRegistry.GetAsync<SubscriptionsActorRegistryKeys.CohortActorKey>();
        var pauseCmd = new CohortSendingCommands.PauseCohortSends(cohortId, DateTime.UtcNow);

        // act
        cohortActor.Tell(pauseCmd);

        // assert
        var resp1 = await ExpectMsgAsync<CommandResponse>();

        cohortActor.Tell(pauseCmd);
        var resp2 = await ExpectMsgAsync<CommandResponse>();

        Assert.Equal(CommandResponseCode.Success, resp1.Code);
        Assert.Equal(CommandResponseCode.NoOp, resp2.Code);
    }

The second Tell dead letters - implicit TestActor ref is lost here


Buffer size too short

Hi,
after loading patches from my ML, the buffer size did not support it:
OperationFailure: database error: Runner error: Overflow sort stage buffered data usage of 33560568 bytes exceeds internal limit of 33554432 bytes
I saw that we can change it by adding:
http://askubuntu.com/questions/501937/how-to-increase-buffered-data-limit

Can you figure out which operation is this in patchew? Is there a backtrace?

Yeah:
[root@happy libpatchew]# patchew server
None
server.conf
/etc/patchew/server.conf
Bottle v0.12.6 server starting up (using CherryPyServer())...
Listening on http://<IP_ADDRESS>:8383/
Hit Ctrl-C to quit.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/bottle.py", line 861, in _handle
return route.call(**args)
File "/usr/lib/python2.7/site-packages/bottle.py", line 1727, in wrapper
rv = callback(*a, **ka)
File "/usr/lib/python2.7/site-packages/libpatchew/server.py", line 267,
in view_index
totalpages = (db.find_series_count(query=query) - 1) / pagesize + 1
File "/usr/lib/python2.7/site-packages/libpatchew/db.py", line 275, in
find_series_count
for i in self._find_series_iter(query=query):
File "/usr/lib/python2.7/site-packages/libpatchew/db.py", line 260, in
_find_series_iter
for i in self._messages.find(q, sort=sort):
File "/usr/lib64/python2.7/site-packages/pymongo/cursor.py", line 814, in
next
if len(self.__data) or self._refresh():
File "/usr/lib64/python2.7/site-packages/pymongo/cursor.py", line 763, in
_refresh
self.__uuid_subtype))
File "/usr/lib64/python2.7/site-packages/pymongo/cursor.py", line 720, in
__send_message
self.__uuid_subtype)
File "/usr/lib64/python2.7/site-packages/pymongo/helpers.py", line 100,
in _unpack_response
error_object["$err"])
OperationFailure: database error: Runner error: Overflow sort stage
buffered data usage of 33560568 bytes exceeds internal limit of 33554432
bytes
On Wed, Apr 13, 2016 at 11:13 PM, Fam Zheng<EMAIL_ADDRESS>wrote:

Can you figure out which operation is this in patchew? Is there a
backtrace?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/famz/patchew/issues/2#issuecomment-209723903

--
Ramon Nunes Medeiros
GitHub: https://github.com/ramonmedeiros
Linkedin: http://www.linkedin.com/pub/ramon-medeiros/22/8aa/245

We can try to make the find_series_count release the object earlier and hopefully the database can also free the buffer.

I'm not a mongodb guru and don't really understand why the created index on the 'date' key is insufficient. What is the size of your "messages" collection? It would be great if you could provide a way to reproduce so I can find a fix.

@ramonmedeiros could you try again with current master? (https://github.com/famz/patchew/commit/9c717b69385e2febe4919dd3da900e29deef0331)

@famz working perfectly. Thanks


[master] Bump Mesos to nightly 1.8.x a6df0e2

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/0c503b01d3a9428ec9db35d09da5e237d737c570...a6df0e2d8dd666cdda9ae4905a43a1850ff466bf

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review


Add Universidad Nacional de Colombia

Add Universidad Nacional de Colombia to domains for granting access to educational packs

@johnconnor77 I am sorry, the domain unal.edu.co is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Cleaning up duplication of groups in Resource Details

Current Resource object contains a group attribute, with no specific definition.
If the intention behind having this attribute is to express resource owner's groups the owner object already covers it. Leaving both in leads to a duplicate definition of the group object.
If there's another reason to have group object in the resource object, please comment on this PR along with the desired description of that object so that it can be updated. If not, then group can be removed from resource as is the intention of this PR.
After the change -

Hm, this brings up an interesting point and has me thinking about resources and how groups relate to them. Can a resource be an account? If so, isn't it then possible for the resource to be part of multiple groups? For instance, a Linux account often has a primary group and multiple secondary groups.

I would not consider an account to be a resource.  Again, trying to conform to D3FEND definitions as we evolve, their definition of Resource:
In computing, a system resource, or simply resource, is any physical or virtual component of limited availability within a computer system. Every device connected to a computer system is a resource. Every internal system component is a resource. Virtual system resources include files (concretely file handles), network connections (concretely network sockets), and memory areas. Managing resources is referred to as resource management, and includes both preventing resource leaks (releasing a resource when a process has finished using it) and dealing with resource contention (when multiple processes wish to access a limited resource).

Re: Rajas' intent however, I was assuming that the Group within Resource was different than the owner's groups, which are often related to their privileges, roles, organizational roles, etc.
I assume that group within Resource is a resource group - e.g. a set of EC2 instances that are part of Autoscale, or a group of containers in K8S etc.

Re: Rajas' intent however, I was assuming that the Group within Resource was different than the owner's groups, which are often related to their privileges, roles, organizational roles, etc.
I assume that group within Resource is a resource group - e.g. a set of EC2 instances that are part of Autoscale, or a group of containers in K8S etc.

Right, if that's the intention then we'll need to update the description to clarify that, because if you check the current description in the resource object it reads The group object associated with an entity such as user, policy, or rule.
I haven't come across such data in logs that I have seen so far, but seems alright to add such an attribute. If we want it in, I can revert that commit and add in object specific the description.

Thanks Rajas - my vote would be to update the description to make clear it is a group of the resource, rather than a group the owner belongs to.


StatusCode 500. device  not found

First of all, I apologize for writing here. I've been struggling with this for weeks, and I couldn't get information from anywhere, so I wrote it.
I followed the guide provided here, but there is an error return from the curl command as follows.
curl -X PUT -d '{
"StartStreaming": {
"InputImageSize": "640x480",
"OutputVideoQuality": "5"
}
}' http://localhost:59882/api/v2/device/name/Ca/StartStreaming | jq '.'
{
"apiVersion": "v2",
"message": "request failed, status code: 500, err: {"apiVersion":"v2","message":"error writing DeviceResourece StartStreaming for Ca -\u003e device Ca not found","statusCode":500}",
"statusCode": 500
}
Other commands available via device profile or http://localhost:59882/api/v2/device/all have the same error return.
(http://localhost:59882/api/v2/device/all?offset=0&limit=20 works strangely)
What should be done to solve this?
Thank you.

(http://localhost:59882/api/v2/device/all?offset=0&limit=20 works strangely)

Do you see your expected device in the results in this case?

Same device Ca not found error message? or same error code 500?
=> return the same status code 500 and error message.

Do you see your expected device in the results in this case?
=> I'm sorry. I wrote it wrong. That works properly. My intention was to convey 'that works strangely well'.

Since I use a translator, I think I might not be able to communicate well, so I'll explain it with an image.

I used Logitec C270 camera and laptop built-in camera.

I wanted to check it accurately, so I checked it in redis DB.

I think everything is going well.
However, when i command the device, the following error is returned: 'status code 500, device Ca not found'

The commands that i can obtain in http://localhost:59882/api/v2/device/all?offset=0&limit=20 return the same error and the same message.

Thank you so much for your interest.

@zambranohally @Biiigstone It looks like you have both potentially encountered a bug/limitation of the device service.
Your devices do infact exist in the redis database, which is why api/v2/devices/all works for you. This is automatic and would work even when the device service is offline, as this is just telling you the info in the database.
The problem is the device service is sending a misleading error message here:
https://github.com/edgexfoundry/device-usb-camera/blob/e07d484d1f5eb205c2c6f6ecd02e5a0c78a6dd12/internal/driver/driver.go#L617-L627
Which is called by this code during the handling of your REST call:
https://github.com/edgexfoundry/device-usb-camera/blob/e07d484d1f5eb205c2c6f6ecd02e5a0c78a6dd12/internal/driver/driver.go#L160-L163
Essentially the issue boils down to the fact that even though your devices are registered to EdgeX, the device service was unable to (or refused to) connect with that camera and thus it does not add the camera to the known list of "activeDevices". Because of this, all commands will return the same 500 error as you observed.
When a device is added to EdgeX, a callback occurs for the AddDevice function. If anything in there returns an error it will end up in that state. A major one is the inability to query the serial number. If you observe the below code snippets, any error generated during this call will cause the system to act in the way you both are experiencing it.
https://github.com/edgexfoundry/device-usb-camera/blob/e07d484d1f5eb205c2c6f6ecd02e5a0c78a6dd12/internal/driver/driver.go#L310-L338
https://github.com/edgexfoundry/device-usb-camera/blob/e07d484d1f5eb205c2c6f6ecd02e5a0c78a6dd12/internal/driver/driver.go#L518-L615

@Biiigstone I do not see you mounting /dev or /dev/videoX into the container via the docker-compose file. Are you missing this?

I certainly haven't done that process.
Can I get a proper example?
I'm using Ubuntu 20.04 version and I was running it as no-secty.
I'm so happy to think about what will be solved.
Thank you.

@Biiigstone I think the documentation here is a bit out of date. Here is what I would recommend:
# clone a fresh copy of the latest edgex-compose
git clone --recursive https://github.com/edgexfoundry/edgex-compose.git
cd edgex-compose
# checkout latest stable release
git checkout kamakura
# run the edgex stack in no-secty mode with the usb-camera device service
make run ds-usb-camera no-secty

You can use docker ps to ensure the device-usb-service is up.
At this point, you can now add your device as you did before:

You can use the following command to view the logs for the device service:
docker logs -f $(docker ps -qf Name="device-usb-camera")

Unfortunately, the method you told me did not work well.
However, I think I got good information from docker logs -f $(docker ps -qf Name="device-usb-camera").
The following is part of my log.

Thank you.

Maybe they solved it!!
I was surprised by the small difference.
Soon, I'll try to recreate it on another computer and if it succeeds, I'll write a note for those who have similar errors as me!

Hi @Biiigstone, glad to see it is working for you now! What is the thing that ended up fixing it?
As for the volume mounts, that is handled for you if using the edgex-compose kamakura or newer built-in ds-usb-service option to make run. Here are the lines for reference:
https://github.com/edgexfoundry/edgex-compose/blob/fa68b85c230c234b7a416225ddaea77d93bf0a4d/compose-builder/add-device-usb-camera.yml#L43-L47

I don't know the exact reason, but I was able to solve it by running the docker in the root area!! It worked well on other computers, too!
It wasn't the edgeX and usb-device-camera's own problem. I am very sorry about this.
Thank you very much for your interest and time in my problem.
Thank you.
I'll simply write down what I did for someone who's going to have a similar problem with me

Get the Device USB Camera Source Code

 $ mkdir ~/edgex
 $ cd ~/edgex
 $ git clone --recursive https://github.com/edgexfoundry/device-usb-camera.git

Download EdgeX Compose Repository (if not already downloaded)

 $ cd ~/edgex
 $ git clone --recursive https://github.com/edgexfoundry/edgex-compose.git
 $ git checkout kamakura

Deploy EdgeX and USB Device Camera Microservice(sudo!)

 $ cd ~/edgex/device-usb-camera
 $ sudo make docker
 $ cd ~/edgex/edgex-compose/compose-builder`
 $ sudo make run no-secty ds-usb-camera

Verify Service and Device Profiles

 $ sudo docker ps
 $ curl -s http://localhost:59881/api/v2/deviceservice/name/device-usb-camera | jq .

Status code 200 must be returned.

Adding Devices using REST API

If you use an auto-scanned device with provision watcher, you can skip this step.
If you want to register your camera yourself, you must delete the auto-registered dv using localhost:4000 or edgex-cli.
Because one serial code seems to allow only one dv.

 $ v4l2-ctl --list-devices
 $ curl -X POST -H 'Content-Type: application/json'  \
http://localhost:59881/api/v2/device \
-d '[
         {
            "apiVersion": "v2",
            "device": {
               "name":"Ca",
               "serviceName": "device-usb-camera",
               "profileName": "USB-Camera-General",
               "description": "My test camera",
               "adminState": "UNLOCKED",
               "operatingState": "UP",
               "protocols": {
                  "USB": {
                        "CardName": "NexiGo N930AF FHD Webcam: NexiG",
                        "Path": "/dev/video0",
                                "AutoStreaming": "false"
                  }
               }
            }
         }
]'

Status code 201 must be returned.
You should use your name and path.
You can use the following command to view the logs for the device service:
$ sudo docker logs -f $(sudo docker ps -qf Name="device-usb-camera")

Start Video Streaming

$ curl -X PUT -d '{
   "StartStreaming": {
     "InputImageSize": "640x480",
     "OutputVideoQuality": "5"
   }
}' http://localhost:59882/api/v2/device/name/<device name>/StartStreaming

Status code 200 must be returned.

 $ curl -s http://localhost:59882/api/v2/device/name/<device name>/StreamURI | jq '.'

Similarly, under the assumption that status code 200 has been returned, check the value of "value" at the bottom.

For example :
$ curl -s http://localhost:59882/api/v2/device/name/Ca/StreamURI | jq '.'
{
 "apiVersion": "v2",
 "statusCode": 200,
 "event": {
   "apiVersion": "v2",
   "id": "ee57873d-ef89-46f8-b6fd-5529962cfeb8",
   "deviceName": "Ca",
   "profileName": "USB-Camera-General",
   "sourceName": "StreamURI",
   "origin":<PHONE_NUMBER>480039700,
   "readings": [
     {
       "id": "84863745-ea2e-4086-8d65-61510860430e",
       "origin":<PHONE_NUMBER>480039700,
       "deviceName": "Ca",
       "resourceName": "StreamURI",
       "profileName": "USB-Camera-General",
       "valueType": "String",
       "value": "rtsp://localhost:8554/stream/Ca"
     }
   ]
 }
}

7, Stream the RTSP stream.
 $ ffplay -rtsp_transport tcp <value>
For example
$ ffplay -rtsp_transport tcp rtsp://localhost:8554/stream/Ca

@Biiigstone , I am closing this issue as answered. Thank you for the details above.

Hi @ajcasagrande the issue is back again. I don't know what happened.
It is functioning some days ago. Can you help me on this? Did you push and new image for device usb?


GrandMA toggle issue

Working on setting up my Stream Deck to trigger GrandMA2.  I can set a button on the GUI to perform the action "toggle exec 2.101". When I test the button via the GUI it responds as expected, toggling the executor on with a press and then off with a press.  However when I push the actual button on my Stream Deck unit, the button works only as a Go or On.  It does not toggle on and then off.
I am new to the unit so guessing I am just missing something obvious but not seeing anything at this point, and odd that it does work via the GUI.
Thoughts?

Put the same cmd on the release of the button. What companion is do it pushing the button. If companion never sends a release command the button is still being pushed. If you look on gma it will appear that you are still holding the button. Both programs are acting as the should be

Oh disregard that I miss read it. What’s the exact command your typing in companion?
If it is “toggle off exec x.x” that won’t work


adds shipping option list api

Background
Adds a new api ShippingOptionListApi to the purchase.checkout.shipping-option-list.render-before/after extension points.
Adds id?: string to the deliveryGroups api.
Both ids have a potentially undefined type as this is the graphql type we are receiving in checkout-web.
It seems like all the examples are auto-generated. Should we be adding new examples for this?
Checklist

[ ] I have :tophat:'d these changes
[x] I have updated relevant documentation

It looks like these changes have not shipped in checkout-web yet. You should open a PR to change the private package there prior to including it in a public release.

Yes, there's a PR open for that already. https://github.com/Shopify/checkout-web/pull/28099

Since this is adding a new API and changes the APIs for multiple targets there are a few doc related changes required.

Define a new Doc API specification (eg.SHIPPING_OPTION_LIST_API), similar to CART_LINE_ITEM_API
Modify the existing, relevant target pages to use this SHIPPING_OPTION_LIST_API

If you have any questions about this, let me know and i'd be happy to walk you through it.

I'll look at adding those to my existing PR. Thanks for the info.


updated to react16 + packages

updated packages and react to latest
updated test libraries.
updated webpack libraries.
possibility to update semantic-ui but will change some styles.

Build fails

Coverage increased (+1.6%) to 77.557% when pulling ee8195849d24aa780e95aa01c0437c52b909ef06 on update_packages into 1bf774a81f120ae38fbfa53e25dca25273c4fe10 on master.


feat(Probability/Kernel): build a kernel from a kernel CDF

Let κ : kernel α (β × ℝ) and ν : kernel α β be two finite kernels. A function f : α × β → StieltjesFunction is called a conditional kernel CDF of κ with respect to ν if it is measurable, tends to to 0 at -∞ and to 1 at +∞ for all p : α × β, if fun b ↦ f (a, b) x is (ν a)-integrable for all a : α and x : ℝ and for all measurable sets s : Set β, ∫ b in s, f (a, b) x ∂(ν a) = (κ a (s ×ˢ Iic x)).toReal.
From such a function with property hf : IsCondKernelCDF f κ ν, we build a kernel (α × β) ℝ denoted by hf.toKernel f such that κ = ν ⊗ₖ hf.toKernel f.
The new file has substantial overlap with the contents of Probability.Kernel.Disintegration and Probability.Kernel.CondCdf: these two files will later be refactored to use the code in this PR.

[x] depends on: #11167

Thanks for the review!
I added a note about future refactors to the PR description.

bors r+
Thanks!


How do we use sessions to prevent request for every typed character?

How can we use sessions with this library to prevent getting billed a request for every character typed? I tried testing a random sessiontoken in the query but I am still seeing requests for every typed character in google cloud console. Here is my query:
query={{
        // available options: https://developers.google.com/places/web-service/autocomplete
        key: "MYKEY",
        language: "en",
        region: "US",
        location: "34.043,-118.267",
        radius: 10000,
        sessiontoken: "thisisarandomtest1234567"
}}

Make a console.log(url) in _request method inside GooglePlacesAutocomplete - it should print the valid url with the parameter sessionToken?

Make a console.log(url) in _request method inside GooglePlacesAutocomplete - it should print the valid url with the parameter sessionToken? It has to make a request for every new input. It could be googles problem?

How do you do that? can you please give some snippet.. thanks.

@Skullcan Any updates?

Feel free to put on a PR.

Just found a problem with uuid, it used crypto-js wich https://stackoverflow.com/a/29836505

From some other reading I've done, I believe there are uuid packages that work fine on React Native.  I would really like to try and avoid adding another dependency, especially if it I only there to support a single library feature.  React Native doesn't support optional imports (yet -it just landed in metro, but it won't be available until RN 0.63 at a minimum).

I totally agree. Just for test purposes, for now, im just generating the token with a simple function.
  const generateToken = (length) => {
    let result = ''
    const characters = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789'
    const charactersLength = characters.length
    for (let i = 0; i < length; i++) {
      result += characters.charAt(Math.floor(Math.random() * charactersLength))
    }
    return result
  }

@Skullcan Any updates?
I guess just using Uuid as recommended by Google is pretty simple. Like this:
        import { v4 as uuidv4 } from 'uuid'
        const sessiontoken = uuidv4()

[...]
        query={{
          key: 'GOOGLE_API_KEY',
          language: 'pt-BR',
          components: 'country:br',
          types: 'address',
          rankby: 'distance',
          sessiontoken
        }}
[...]

Hi, Sorry for the delay in the response.
I ended up following the Docs in the Google Places API and doing exactly what you said.
I have a function to generate a token per component render and stored it in the state:
In the component, I used the same prop you have in your example.. passing this sessionToken

query={{
         key: 'YOUR KEY HERE,
         language: Strings.getLanguage(),
         origin: myLocation,
         location: myLocation,
         sessiontoken: sessionToken,
         radius: '200000',
         components: 'country: br',
         strictbounds: true,
       }}```

Worked like a charm form me.

@Skullcan can you put in a PR? I'll get this merged right away.

@Skullcan can you put in a PR? I'll get this merged right away.

Sure, I'll get to this when I'm done with work later.

What do you all think about how this should be implemented?
There are a couple of ways to go about this, but basically its

Add instructions to the readme about how use sessions tokens (it doesn't seems like there are too many steps). This technically does not need to be in the library, because you should be able to do it already in the query prop.
Add a sessionToken prop to the library, where, if set to true, would automatically set a session token.

The session begins when the user starts typing a query, and concludes when they select a place and a call to Place Details is made.

Handling for this in the library seems a little more logical to me, but I can hear both sides of the argument.

I was thinking of doing the option number two.
Is the way easier for the end user. But also the more invasive and have to be implemented carefully to not break earlier versions.

Have a prop in the library, if true, automatically set a session token.

I was going to do following option two.
But both ways works I guess.
I'd say handling in the library is the easier way for the end user.

Add a prop to the library, if true, automatically set the session using a default function.
Default the prop to false, so it's not a breaking change.
Have a prop so people can use their custom function to generate the sessionToken?

The function I posted in the other comment is working fine, and it generates something very close to UUID, but I've not tested in a large scale project so I cannot guarantee it works 100%.

Sample result for de sessionToken using my function: 6a79849f-24c5-45d9-acb8-3203b6a67bf4

I prefer option two.
I am extremely weary of adding more props to the library, as there are already almost 50 props available (I am trying to document them all, see my effort here).
In terms of API design, I like numbers 1 and 2 from above.  As I said, I don't want to add another prop, especially one that passes in a function, it's a little bit of a blackhole. In addition, passing in a function still limits your using a UUID generating library from NPM directly in the package.
How about a session token that has value of either true, false (default), or a string. That was anyone can generate their own UUID however they feel like.
I wouldn't be terribly worried about the accuracy of the UUID generated.  The likelihood of a collision is so miniscule....

Sure, sounds great to me!
Hope others interested give some feedback and I'll gladly try to implement this.

@Skullcan I wouldn't wait around too long for a response. I would tell you to just go for it 😃

Sure. Already started something, but didn't had the time to finish yet. Crazy Week.


Navigation bar in a different div

I managed to achieve changing the position of navigation bar within the same div as "steps" by editing the wizard html and css.
But how do I add the navigation bar to a different div. Not the same div as steps?

The module is designed to have the steps in the same DIV, to change this you will have to edit the source code in your project.


Coverage should be setup to cover multiprocessing and forks

Per measuring sub-processes PyB needs to bootstrap coverage to cover subprocesses.
Windows coverage not a goal here since quite a few other things broken, but will attempt to make sure Windows doesn't get more broken than it is.

Final solution reflects API method of ensuring coverage is transferred to the spawned subprocess.
No solution for forkserver.
Windows, which uses "spawn" method of multiprocessing should operate normally.
Base coverage version updated to ~=4.2.
Filed nedbat/coveragepy#14 to ensure API-initiated coverage operates normally in >4.2.


add 'use strict'; to examples and test

I am not sure what else non-module scripts should be addressed. If any, let me know to add them in another commit.

Hopefully done in the second commit.


Following the Accelerate documentation, but only one GPU is used

I started with the LoRA example from the list of Transformers examples (I replaced the model with flan-t5-small for testing on my machine). Next I followed the examples and documentation provided in the Accelerate library to ensure both of my CUDA GPUs were utilized. I checked nvidia-smi, and I can confirm that the model is still training on a single GPU. Is there something in the documentation missing?
I've attached my code here:
LoRA-multi-gpu.zip

What command are you using to launch your job? What is the output of accelerate env

I'm executing a jupyter notebook with the same code.

Accelerate version: 0.15.0
Platform: Linux-6.2.0-37-generic-x86_64-with-glibc2.35
Python version: 3.10.12
Numpy version: 1.24.2
PyTorch version (GPU?): 1.13.1+cu117 (True)
Accelerate default config:
Not found

You’re not using the notebook launcher, this is expected. https://huggingface.co/docs/accelerate/basic_tutorials/notebook

Thank you, I missed this entirely.


Angular 12.2.2 css minimizer build error - Invalid version: "TP"

🐞 Bug report

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
Worked in 12.2.1 and broken in >=12.2.2
Description
Build error during css minification.
🔬 Minimal Reproduction
ng build
optimization.styles.minify must be true in the angular.json
May require scss styles
🔥 Exception or Error
This error shows for every component in the build

some-path/some-component.component.scss from Css Minimizer
Error: Transform failed with 1 error:
error: Invalid version: "TP"
    at failureErrorWithLog (/home/geoff/code/iverticle/web-apps/admin/node_modules/esbuild/lib/main.js:1449:15)
    at /home/geoff/code/iverticle/web-apps/admin/node_modules/esbuild/lib/main.js:1260:29
    at /home/geoff/code/iverticle/web-apps/admin/node_modules/esbuild/lib/main.js:609:9
    at handleIncomingPacket (/home/geoff/code/iverticle/web-apps/admin/node_modules/esbuild/lib/main.js:706:9)
    at Socket.readFromStdout (/home/geoff/code/iverticle/web-apps/admin/node_modules/esbuild/lib/main.js:576:7)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)

🌍 Your Environment

Angular CLI: 12.2.2
Node: 14.16.1
Package Manager: npm 6.14.12
OS: linux x64

Angular: 12.2.2
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1202.2
@angular-devkit/build-angular   12.2.2
@angular-devkit/core            12.2.2
@angular-devkit/schematics      12.2.2
@angular/cdk                    12.2.4
@angular/flex-layout            12.0.0-beta.34
@schematics/angular             12.2.2
rxjs                            6.6.7
typescript                      4.2.4

Anything else relevant?
N/A

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Can you provide the browserslist configuration file?

@alan-agius4 this is the entire file...

# This file is used by the build system to adjust CSS and JS output to support the specified browsers below.
# For additional information regarding the format and rule options, please see:
# https://github.com/browserslist/browserslist#queries

# You can see what browsers were selected by your queries by running:
#   npx browserslist

supports es6-module

The above query will yield a large set of browsers which most of them are unsupported by the Angular framework
and_chr 92
and_ff 90
and_qq 10.4
android 92
chrome 95
chrome 94
chrome 93
chrome 92
chrome 91
chrome 90
chrome 89
chrome 88
chrome 87
chrome 86
chrome 85
chrome 84
chrome 83
chrome 81
chrome 80
chrome 79
chrome 78
chrome 77
chrome 76
chrome 75
chrome 74
chrome 73
chrome 72
chrome 71
chrome 70
chrome 69
chrome 68
chrome 67
chrome 66
chrome 65
chrome 64
chrome 63
chrome 62
chrome 61
edge 92
edge 91
edge 90
edge 89
edge 88
edge 87
edge 86
edge 85
edge 84
edge 83
edge 81
edge 80
edge 79
edge 18
edge 17
edge 16
firefox 93
firefox 92
firefox 91
firefox 90
firefox 89
firefox 88
firefox 87
firefox 86
firefox 85
firefox 84
firefox 83
firefox 82
firefox 81
firefox 80
firefox 79
firefox 78
firefox 77
firefox 76
firefox 75
firefox 74
firefox 73
firefox 72
firefox 71
firefox 70
firefox 69
firefox 68
firefox 67
firefox 66
firefox 65
firefox 64
firefox 63
firefox 62
firefox 61
firefox 60
ios_saf 14.5-14.7
ios_saf 14.0-14.4
ios_saf 13.4-13.7
ios_saf 13.3
ios_saf 13.2
ios_saf 13.0-13.1
ios_saf 12.2-12.4
ios_saf 12.0-12.1
ios_saf 11.3-11.4
ios_saf 11.0-11.2
ios_saf 10.3
op_mob 64
opera 78
opera 77
opera 76
opera 75
opera 74
opera 73
opera 72
opera 71
opera 70
opera 69
opera 68
opera 67
opera 66
opera 65
opera 64
opera 63
opera 62
opera 60
opera 58
opera 57
opera 56
opera 55
opera 54
opera 53
opera 52
opera 51
opera 50
opera 49
opera 48
safari 15
safari 14.1
safari 14
safari 13.1
safari 13
safari 12.1
safari 12
safari 11.1
safari 11
safari 10.1
safari TP
samsung 14.0
samsung 13.0
samsung 12.0
samsung 11.1-11.2
samsung 10.1
samsung 9.2
samsung 8.2

I suggest that you update the browserslist to include only the browsers that are supported.
# This file is used by the build system to adjust CSS and JS output to support the specified browsers below.
# For additional information regarding the format and rule options, please see:
# https://github.com/browserslist/browserslist#queries

# For the full list of supported browsers by the Angular framework, please see:
# https://angular.io/guide/browser-support

# You can see what browsers were selected by your queries by running:
#   npx browserslist

last 1 Chrome version
last 1 Firefox version
last 2 Edge major versions
last 2 Safari major versions
last 2 iOS major versions
Firefox ESR

Which yields the following
hrome 92
edge 92
edge 91
firefox 91
firefox 78
ios_saf 14.5-14.7
ios_saf 14.0-14.4
ios_saf 13.4-13.7
ios_saf 13.3
ios_saf 13.2
ios_saf 13.0-13.1
safari 14.1
safari 14
safari 13.1
safari 13

For a full list of supported browsers please see https://angular.io/guide/browser-support

Thank you for that @alan-agius4
Without changing the browserslist file, I have been doing a lot of testing by changing the node and npm versions and removing the node_modules folder and the package-lock and reinstalling the dependencies and re-running the build. This is how I narrowed it down to 12.2.1 to 12.2.2. However, since putting in the issue, I have continued to to do this and at some point the problem has just miraculously disappeared and I can't reproduce it anymore.
I don't think this had anything to do with the browserslist, but rather something to do with my environment which seems impossible to replicate now. So, thank you for your help, but I am closing the issue.


Safeguard publishing

only allow publishing from travis, check for identifying information.

make person testing the code to forcibly jump through some hoops, like setting env vars

only publish on pattern matched tags (n.n.n)

@abesto I think your work on the publishing/releasing resolved this.

I feel the same way. Thanks for cleaning up!


How to visualize an attention mechanism in a classification task?

I've managed to finish experiments using attention mechanism adopted from @cbaziotis implementation and now i'm confused with the visualization. I don't really understand the heatmap as well. If you guys can explain these to me, it means a lot :

What is heatmap? how to read them?
What to visualize in an attention mechanism? The weight?
The code to visualize an attention mechanism, in conjunction to @cbaziotis' implementation

Thanks in advance!

@aryopg Any updates?


I can't able to disable hours and minutes

Timepoint[] disabledTimes = {
new Timepoint(11)
};
    timePickerDialog.setDisabledTimes(disabledTimes);

And also how to set timerange ??


CBMC proofs for s2n_safety functions

Description of changes:
This PR adds two proofs for constant time safety functions in S2N along with s2n_align_to. The file s2n_safety.c has been modified for both functions to disable CBMC checks in specific places when the intended behavior is to underflow an integer. The proof for s2n_align_to is also included because it required a change to s2n_safety.c as well.
Call outs:
The proof of s2n_align_to, much like the existing proof of s2n_mul_overflow, cannot currently perform full testing due to CBMC performance issues. The multiplication and division required cause it to run hours at a minimum. As a result, the offending lines have been commented out but left in for future use. Once the CBMC team has improved the performance of CBMC, these lines can be enabled again.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2178 into master will decrease coverage by 0.26%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #2178      +/-   ##
==========================================
- Coverage   81.07%   80.80%   -0.27%
==========================================
  Files         248      248
  Lines       18521    18545      +24
==========================================
- Hits        15015    14986      -29
- Misses       3506     3559      +53


Throw error when write fails

Related to #61, this PR addresses cases where we're writing to a stream and not a file, so it's not possible to check if it is writable before starting. Instead, make sure that the callback is called with the correct error

Also needs a CHANGES entry.


Two sv_indicator in SpeedView

Hey Anas!
Thanks for this awesome library. This is one of the best library I had seen so far. Really appreciate your efforts.
I am trying to use SpeedView and have few questions regarding it. It would be great if you can help me with those.

Let's suppose i've have fragmentA and fragmentB. So, i just integrated speedview in fragmentA in a cardView then i've another view in fragmentB(let's suppose, it's a details view fragmentA) where i'm also using speedview same as before. FragmentA view is working fine but my problem in fragmentB. So, In fragmentB speedview it's showing me two sv_indicator in the view(i don't know why!) one for deafult 0.0 value and other one is the value that i assigned. I think it's a bug. So, Is there any way resolve this? or am i doing something wrong? Let me know.
Thank you!

I using this meter view
<com.github.anastr.speedviewlib.SpeedView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:id="@+id/meterFair"
android:layout_gravity="center_horizontal"
app:sv_startDegree="180"
app:sv_endDegree="360"
app:sv_withTremble="false"
app:sv_indicator="NormalIndicator"
app:sv_withIndicatorLight="false"
android:layout_marginTop="@dimen/_10sdp"
app:sv_indicatorColor="@color/green"
app:sv_centerCircleColor="@color/green"/>
here's the screenshot:

Sorry it's a not bug. Just after debugging my views for hours, I realized i was doing some mistakes in my code but anyways! Thank you for this awesome library!

Hi @abdulrahim46
SpeedView doesn't support multiple indicators #134, so the second indicator in your case clearly doesn't belong to SpeedView that exists in fragmentB.
it maybe from fragmentA, change the color of indicator in fragmentA, to make sure.

Yeah I have checked your code it doesn't support two indicators. It was a duplication error on fragmentB.
Thanks for the reply! Keep up the goodwork.


Fix icon alignment in Banner

:rocket: Issue was released in<EMAIL_ADDRESS>:rocket:

:rocket: Issue was released in<EMAIL_ADDRESS>:rocket:

:rocket: Issue was released in<EMAIL_ADDRESS>:rocket:


improve logging

have at least info and above level log messages

Hi @sanketplus  I'll love to work on this as part of hackoctoberfest, I've been recently reading a lot about file systems and just getting started with distributed systems. can you provide me with some more info on how do you plan for this to be implemented. I'll clone and look into the repository in a while.

it is fairly simple architecture to follow. You can read some background on https://superuser.blog/distributed-file-system-python/
as this is an improvement, the problem is open ended. The goal is to have logging for both master and minions to get insights into what is going on.
Let me know if you need further help @geekodour

thankyou, working on it.

Hey @geekodour if you are still interested in adding logging check out #6. You can add logging to the file https://github.com/sanketplus/PyDFS/blob/master/pydfs/minion.py the same way and it is pretty easy. Let me know if you want any advice/help!

@nloadholtes thanks! I'll do it today or tomorrow.


add another port for pytorch master sync

currently using 6006 which overlaps with tensorboard

Can 6016 instead which is already opened


Bug opening documents from TreeView

When switching between clicking and using the search facility, the "current" document gets lost resulting in the incorrect documents opening.

The state of the current document was not being kept properly. Fixed now.

Fixed with:
https://github.com/curvedspace/Permastead/commit/7ce58286cf5dc70bbb87e929c73774f3c9b3a2c3


Update to latest open release

Test and update to support Aras 11 SP12.

Updated TESTSTATUS.md for Aras 11SP12. Package is compatible with Aras11SP12


Adds Essentials Devices Common to the references

Adds Essentials Devices Common to the references
Adds reflection to the EssentialsPluginTemplateBridgeJoinMap OffsetJoinNumbers method

Already added in main branch


support to expand structured lg

Support to expand structured lg in expand function

Pull Request Test Coverage Report for Build 85517

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 76.901%

Totals

Change from base Build 85509:
-0.8%

Covered Lines:
7111

Relevant Lines:
9247

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


Property 'getProcessedText' is missing in type 'SurveyPropertyEditorBase'

Are you requesting a feature, reporting a bug or ask a question? Reporting a bug, maybe.
What is the current behavior? Unable to build application.  Error is "node_modules/surveyjs-editor/surveyeditor.d.ts (71,22): Class 'SurveyPropertyEditorBase' incorrectly implements interface 'ILocalizableOwner'.
Property 'getProcessedText' is missing in type 'SurveyPropertyEditorBase'. "
What is the expected behavior? ng build to finish without error
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
your_code_here

Specify your

browser:
browser version:
surveyjs platform (angular or react or jquery or knockout or vue):
surveyjs version:

We have an Angular+SurveyJS boilerplate repo - https://github.com/surveyjs/surveyjs_angular_cli
I've just cloned it, installed latest npm packages (1.0.25) and run ng serve
It works ok for me.
Could you provide any additional info to reproduce the issue on our side.
Or could you get the surveyjs_angular_cli repo and try to reproduce the issue with this repo?


Add content trust attribute to project, and support it in API.

This applies only to Harbor standalone.

For 1.2.0 timeframe in standalone Harbor we may just use environment variable to control the content trust and vulnerable policy.

Done.


RHMAP-14876 - Missing steps to configure WFM Demo into RHMAP

JIRA : https://issues.jboss.org/browse/RHMAP-14876

@nialldonnellyfh could you check and merge it for me please ?

@finp Could you check and merge it?  Missed step identified into a case.
JIRA: https://issues.jboss.org/browse/RHMAP-14876

@finp changes made. I don't have the access to merge in this repo. Do you have? Could you do it for me?

Reviewed and verified.


Fixes #147 : Changed hard code module groupId and version dependency

Signed-off-by: Kai Chu<EMAIL_ADDRESS>

Codecov Report

Merging #149 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #149   +/-   ##
=========================================
  Coverage     70.71%   70.71%
  Complexity      267      267
=========================================
  Files            67       67
  Lines          1144     1144
  Branches        128      128
=========================================
  Hits            809      809
  Misses          276      276
  Partials         59       59

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 a1bc154...71bfdce. Read the comment docs.


Why is Audio not an option?

When I choose Audio instead of this (shitty) image click challenge which takes forever to be finished I get flagged as bot and can't even do an Image Captcha without a page reload. What is this Madness? What if I'm a blind user?

It is Whereat1app Assistance for Google Assistance

In my case I use uMatrix, VPN and all the privacy goodness which makes Recaptcha hate me. This leads to me hating Recaptcha too. Result is me uses a sort of hack which solves the captcha for me by solving the audio challenge.

Repo is just for PHP client issues. This is about the reCAPTCHA service.


Add Webex webhook integration

Hello,
I had the necessity to use a webex integration for notifications. Since it was not available I created it (and documented), a simple webhook using github.com/jbogarin/go-cisco-webex-teams/sdk.
I hope it should be useful also for the community.
BR
Giuseppe Prenni
Tests performed

tested in local cluster

Hi @prennig86
Thanks for the PR. We appreciate your effort and time in submitting it.
Unfortunately, due to security considerations, we're not merging dependencies to 3rd parties, into the main branch.
This helps us maintain a more controlled environment and minimize potential vulnerabilities.
Thanks again for your contribution!


Thorntail-runner: ClassNotFoundException in multi-module package

Description is provided on an isue:  https://github.com/thorntail/thorntail/issues/1276

ok to test

ok to test

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Bump @michalszynkiewicz


Mhsm doc changes

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Rather than merge in a bunch of unrelated changes, please rebase your changes atop main:
Assuming you're in your topic branch:
git fetch upstream main
git rebase FETCH_HEAD
# resolve conflicts, if any
git rebase --continue
git push --force

Merging all these unrelated changes not only brings in other errors as you see from the checks, but makes it difficult to properly review in a monorepo.

Followed these steps, but lint error still persists

Because there's still a bunch of unrelated commits from other branches. Let's try this instead:
git reset --hard 3cd5c93bed8d96a811f71168a02d2dbc112d4aad # this was your first commit
# make any edits you wanted to originally, if any - I think you need to fix the description per Joel's comment
git fetch upstream main
git rebase FETCH_HEAD
git push --force

This should result in only 1 or 2 commits in the PR depending if you made any edits per Joel's comment.

@jhendrixMSFT I think this is ready now, given the typical issues we see from KV changes due to consistent validation issues.


Remove public site from management commands

This PR will remove the public site from management commands and fix the IDs that are used when the apply site is used to reflect that of production.

@frjo @theskumar what are the thoughts on this? anything else need to happen to get it over the line?

This was closed by #3738


tests:test_txn_store_gc2_9 panicked  with  stale_command

Hi,all,
test_txn_store_gc2_9 some times failed caused by gc failed with stale_command  on raftstore. Here is the details:
thread 'storage::test_storage::test_txn_store_gc2_9' panicked at 'called `Result::unwrap()` on an `Err` value: Txn(Engine(Request(message: "stale command" stale_command {})))', src/libcore/result.rs:859
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: tikv::util::panic_hook::track_hook::{{closure}}
   1: <std::thread::local::LocalKey<T>>::with
   2: tikv::util::panic_hook::track_hook
   3: core::ops::Fn::call
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: std::panicking::begin_panic_fmt
   7: rust_begin_unwind
   8: core::panicking::panic_fmt
   9: core::result::unwrap_failed
  10: <core::result::Result<T, E>>::unwrap
  11: tests::storage::assert_storage::AssertionStorage::gc_ok
  12: tests::storage::test_storage::test_txn_store_gc_multiple_keys_cluster_storage
  13: tests::storage::test_storage::test_txn_store_gc_multiple_keys
  14: tests::storage::test_storage::test_txn_store_gc2_9
  15: <F as test::FnBox<T>>::call_box
  16: std::panicking::try::do_call
  17: __rust_maybe_catch_panic
  18: std::panicking::try::do_call
  19: __rust_maybe_catch_panic
  20: <F as alloc::boxed::FnBox<A>>::call_box
  21: std::sys::imp::thread::Thread::new::thread_start
  22: _pthread_body
  23: _pthread_start
test storage::test_storage::test_txn_store_gc2_9 ... FAILED

do we fix it now? @AndreMouche

not yet. It's hard to  reappear, while the cause of failure is clear. I'd like to fix it in the feature since it's a little troublesome. @siddontang


Opensds external provisioner design

In this update, we launched a proposal about OpenSDS external provisioner, to provide a unified provisioner for different backend storage types.

Closed


Add banner image on About page

Maybe a crop of this: https://www.vancouverarchives.ca/wp-content/uploads/MAP359.jpg. Would be good if we had the item information.

To replace the existing banner image, search for j-https-cdil in the project files. This will link a background-image referencing the current image at U Idaho. You can replace this url with a relative path to a image in this project's files.
Something like:
background-image: url(/path/to/image.jpg);


Fails to run Jekyll 1.0.3 (conflicting versions of safe_yaml) on Mac OSX 10.8.3

Trying to run jekyll serve and getting errors about not being able to activate crack because of conflicting versions of dependency, safe_yaml. Jekyll requires ~>0.7.0 and crack ~>0.9.0.
 Feel free to reopen it if you think otherwise


PR: Add a way to bypass errors in QtAwesome

Fixes #3843

Is important to know that for this to actually work this PR has to get a merge in the qtawesome project because of the FontError import.

A preview of the message dialog:

@dalthviz, I added a commit to your branch to fix some Travis errors. Please don't forget to pick it up locally.
Still this is a bit tricky to merge because it depends on a new version of QtAwesome. I'm going to release QtAwesome 0.4 with your FontError fix, so @dalthviz you need to bump here too our package requirements to that version in all places we define them. And for that, please check how @rlaverde did it for Chardet in PR #3640.

@ccordoba12 regarding

...you need to bump here too our package requirements to that version in all places we define them.

I suggest we use a requirements.txt file (or more as needed) as a single entry point for modifying dependencies (we can rely on this file for all CI services and scripts). This will make the updating of dependencies less error prone. I implemented this for fusion and eases the pain :0)

I suggest we use a requirements.txt file

Three reasons i think this is not a good idea:

We need fine grained control for our dependencies. For example, in CircleCI we need to install qtconsole along with the right PyQt version separately from the rest of our deps.
We're still testing that our conda and pip packages pull the right dependencies on Travis and AppVeyor. And for that, we don't need a requirements file, just let the packages to pull the dependencies.
People still wants to know (in README and our docs) what our dependencies are. Again, we can't use a simple requirements file for that.

I know this process is still cumbersome, but that's why CI services are for: to test if we did things right :-)

Regarding the reasons
1.) That is the exception and not the rule
2.) So?
3.) Sure we can, we put a link to the file and comment out the dependencies we have to handle "manually" on CI, which is basically for now just PyQt

... reasons i think this is not a good idea:

If I had nickel for every time...

@dalthviz, please add the QtAwesome version we need now in README.md and docs/installation.rst as 0.4+.
@goanpeca, sometimes you're right and sometimes not. But you're prone to give me the task of finishing what you start, and I really (really) don't have time for that now. So I think we're going to continue with our awkward (but proven ;-) procedure. As I said before, it's not something we do everyday so I'm fine with it.

@dalthviz, please change QtAwesome version to 0.4.1. I had to do some changes in 0.4 to better detect this error.

Ok, this is ready now. Thanks a lot @dalthviz for your work on this one. It's very important for 3.1 :-)


Issue #1480: c8y-config-plugin to fail cloud operation on execution failure

Proposed changes
The c8y-config-plugin to fail cloud operation when the execution of that operation on the child device fails, for cases like:

If the plugin fails to download the config file for a child device, on a c8y_DownloadConfigFile request, fail that operation, before even passing that request to the child device
On receipt of a c8y_UploadConfigFile request, if the child device sends successful status without uploading the file, the plugin should fail that operation ignoring the successful status from the child.

Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

If there is a download request for an unknown file type, this error is not reported to the cloud.

Isn't it better to just ignore requests for an unknown type so that some other component that can handle that type may pick it up and respond to that request? The current logic of logging it as an ERROR is probably wrong too. A WARNING log might be better.

If there is a download request for an unknown file type, this error is not reported to the cloud.

Isn't it better to just ignore requests for an unknown type so that some other component that can handle that type may pick it up and respond to that request? Marking that operation as failed, eliminates that possibility. The current logic of logging it as an ERROR is probably wrong too. A WARNING log might be better.

You are correct, responding with an error would prevent another extension to take ownership of the request.


Build FSM runner

Look at smach - http://wiki.ros.org/smach for this.

This seems really perfect for us. Someone should write a python file for our architecture. @ManashRaja Can some software guy be assigned to this?

@ash-anand @amitpathak09 check the link here for help regarding implementation of FSM

@ash-anand Copy paste all the discuss and the wiki and diagram here.

Snippets from conversation on Slack.
@sam17 :

Why is identifying the bot to attack a different state? Why cant we do it in parallel all the time?

I think your states are too broad. Each state can have multiple states within it. Though, that depends on other modules.

Find/Scan state may need to have multiple states depending on localisation success or failure.

We might need an additional state for increasing K. Coz, it is not necessary that just while scanning K will increase. Some action might be needed to increase K

You claim to have a state with K high for multiple bots. That is really really rare.

1.Identifying bot is different state as there are currently 2 ways we are going to it 1. Simple Circle detection 2. YOLO learning based. We don't have enough computational power to run YOLO all the time so that state will also decide which one to use based on fps or some other criteria.
2.States describe what that state should do, how that will be done is decided by the modules.
3. Find/Scan state will have more modes under it. Will think it through.
4.K will decrease/increase using Kalman filter. Longer the bot is out of view lesser it's probability will get with a Gaussian distribution.
5. We can put a threshold where say if 10/20 bots have prob greater than K instead of all bots.

@sam17 :

Doesnt YOLO/circle detection need to run all the time anyway? So why is it a state with transition? What is YOLO? Is there a description of it? I recently read pi can detect DL things in <1s.
True
Yes but we need something to actively increase K no? Who handles that?
10/20 bots? Very very improbable.

I misunderstood. YOLO can't be run all the time, it's very computationally heavy. Pi cams detecting things don't work on ML. They do some template matching , bots won't be detected if the angles or size change.
K will increase when quad sees the bot. Location will be stored as Normal distribution with increasing variance ( 1/K ), if the quad sees it again we will reduce the variance of the distribution as the harmonic mean thus increasing K.
We can have some other probable criteria then

Why not? Pi does not need to do IP. It only needs to stream images and get results back but yea network needs to be fast for it.
But what about following one bot? Shouldn't we have the provision to shift to greedy mechanism in this?

We can do that but last year off board computation didn't go very well I guess. I was thinking of getting nVidia Jetson development board which hopefully should support YOLO running every time.

That again comes down to specifications of handling the event. Also in case the bot has high probability and is feasible to attack, quad will follow it anyways. We can add greedy algo as well but greedy algos have their down sides of not converging to the optimal always.

@ash-anand I did not understand that why identifying the bot state will decide if YOLO is to be used or not? That state is just supposed to point out which bot has to be attacked based on MAV's and ground bot's pose and twist right?

@gauravgardi to know anything about the groundbots and point out the bots to take action on, first we need to detect them and get details about it's pose twist etc as you said.
For that we need code ( Circle detection like we have now or YOLO ). Since YOLO is computationally very expensive we can't just let it run in a separate thread and continuously publish data to a node.
This can be handled in two ways

Get a more powerful development board which supports CUDA with multi core processor.
Run YOLO only at times when there is no visible bots using circle detection code.
Assuming we go with the 2nd option , it should be the job of Find State to do the switching when required.

@ash-anand so it should be the job of find/scan state or if required a separate state and not the job of identify bot state. So identify bot state is only identifying which bot to attack based on MAV's and ground bots' pose and twist. So why is it a separate state and not a part of strategy state?

@gauravgardi identifying bots shouldn't be done when quad is going to attack. It should be done before. Identify bot is not a state. Identifying bots comes under Find/ Scan state only.
Bot prediction is totally different state which is responsible for choosing the best bot to attack.
I made it separate from strategy because of the discontinuity between these two tasks.
Bot prediction can be very expensive on the processor if done in depth. Also if you consider the interrupts received by the Object Detection , you can see the advantage of keeping the Bot prediction state separate from the Strategy. Strategy is already a very complicated state with a lot of physical activity in Quad.
As written in Wiki, states are "re-run" once an interrupt is received.

I was referring to this state

As I wrote in later reply I misunderstood. Also running bot prediction all the time with YOLO on it won't be very good on Pi.

Ok and odroid?

YOLO + bot detection upto 20+ layers together is capable of making my laptop crash.
It has happened once or twice before so I don't see any chance of even odroid standing.

That would happen while training right? can't we use the parameters after training on any other machine and then run YOLO on odroid?

Not during training, it happened during running the code for detection.
We won't be running it for 20 layers but minimum 2 layers is required for accurate predictions.
Assuming my laptop to be atleast 10 times faster than odroid because of CUDA cores, I don't see any chance of it running.

Can I get link to YOLO code and its plan?
Also, we should never ever shift detection strategy mid-flight. Things need to be completed deterministic in-flight.

@sam17 pjreddie.com/darknet/yolo/
Then we will need to figure out a way to make it less expensive to run smoothly

@ash-anand we don't necessarily need to re-run the states once the interrupt is received. we can just publish commands on a topic to stop a state's output while it keep running in the background. also, let me know whether we can run the bot detection and tracking state at all times in any case and if we can keep detecting the obstacles at all times as sharp doesn't seem to be much useful.
btw, we can run a script in smach to view the designed state machine directly...so you don't need to draw the diagrams and everything, I'll be pushing the code shortly after the exams.
@gauravgardi I seem to be unable to assign the issue to myself. Do it please.

@amanchandra333 Which code are you talking about?

@sam17 the python script for the state machine.

@amanchandra333 the state machine diagram ash has drawn is just for reference for proceeding with the implementation. You can check whether your implementation is correct or not by matching the diagram generated by smach(which will be according to your implementation) with the diagram @ash-anand  has drawn.

@gauravgardi will be pushing it shortly after the endsems