object as tag

Hi, my ajax source responses is in the form:
[{
	"_id": "56b351e01680a9c815efbaa8",
	"name": "John",
	"age": 20,
	"__v": 0
}, {
	"_id": "56b352551680a9c815efbaa9",
	"name": "James",
	"age": 20,
	"__v": 0
}]

I would keep those infos. I'm searching for a method for getting the tags from tokenize in this form (in this case I selected from the dropdown "John" and I added a new tag  "Mary"):
[{
	"_id": "56b351e01680a9c815efbaa8",
	"name": "John",
	"age": 20,
	"__v": 0
}, {
"name":"Mary",
"value":"Mary"
}

the method

$('#tokenize').tokenize().toArray();

returns just an array of strings...

Not possible with this version, maybe in version 2

I've just replaced my tokenize 2.5 (from bower) with your 2.6 (form this repository), but
    console.log($('#tokenize').tokenize().toArray());

prints still an array of strings.
this is my init, maybe there is something wrong here
$('#tokenize').tokenize({
        datas: "/api/community/users",
        displayDropdownOnFocus:true,
        searchMinLength:0,
        searchParam:'q',
        valueField:'_id',
        textField:'name',
        onAddToken:function(v, t, e){
            if(v==t)
                $('#tokenize').tokenize().tokenRemove(v);

        }
    });

side question:
I set searchMinLength:0 and displayDropdownOnFocus:true:, I want to see the first results onFocus, but it doesn't works neither.
very thanks!

displayDropdownOnFocus on focus doesn't work with ajax
https://github.com/zellerda/Tokenize/issues/62

so there is no way to see the first results using ajax in tokenize?

In the very begining of the plugin this behavior was implemented but retired next, I got some issues with that. I will probably thinking of it for Tokenize2.
If you really need to display the dropdown on click, just change the data option and fill the select with all your values, personally I don't use ajax because with the search it can be a lot of load on the server for a simple value.

I really need this features, other tokenizer plugins have this, but I want to use tokenize.
There is an onFocus event? I can't see in docs

No but you can catch the focus event of the input with jQuery

    $('#tokenize').focus(function() {
        $('#tokenize').tokenize().tokenAdd('test','test1');

    });

it doesn't work, anyway I don't think it's a safe solution..
so I should switch on a dead tokenize plugin project like bootstrap tagsinput or tokenfield?  :(


Feat: replace detect_ids with detect

Changes:

Replace detect_ids with detect so as to be more user-friendly

Instead of detect_ids: ["dog"], it is now detect: ["dog"]
Replace detect_ids in object detection models (efficientdet, yolo, yolox) configs
Update tests to use detect in place of detect_ids
Update docs and use cases yaml files

Add deprecation warning notice for detect_ids.

Technotes:

The changes stop at peekingduck/pipeline/nodes/model level, within the __init__ of EfficientDet, Yolo and YoloX, relevant code shown below:

        self.detect_ids = config["detect"]  # change "detect_ids" to "detect"

Internally, each object detection model still uses self.detect_ids.
detect is used at the user-interface level.

Also updated yolo_face to use detect instead of detect_ids.
Didn't modify yolo_face initially as it only takes in [0, 1] and does not have any class names (no no_mask or masked labels).
After thinking about it, decided to update as you pointed out to keep everything consistent.


Force undo manager to stop capture when pasting

This was raised in https://github.com/jupyterlab/jupyterlab/issues/10928
The capture seems to be stopped before capturing the paste event. But the second stop capture statement is not working because I succeed to do undo's that removed characters typed after the paste change.

Hi, what is the state of this PR? Looking forward to have undo as a separate undoable event, but not quite sure if more work is required of this solves it for JupyterLab.

Thank you for the fix @fcollonval!
Sorry for the late merge. This is perfect. I'm going to publish a new release in a bit and open a PR to JupyterLab.


[GIT] Rename "Clean" to "Discard changes"

When I want to undo changes I've made to a file in VS code, it's possible to use the embedded git tools, right click a file with pending changes and choose "Clean". This option keeps confusing me, so I wondered if it might be an idea to give this option an easier to understand name.

I love it! I was never a big fan of Clean anyway.

0428dd5dc332d453e40f4e471cf75386b869d41e

Agree, git "clean" wipes out files. Revert might be a better word than discard as revert is used by other vcs (svn, hg) to undo changes.

@joaomoreno It now read Discard File which is bogus because it only operates on the changes/delta to the original file.


Move qa scripts to qa dir

Codecov Report

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

@@           Coverage Diff           @@
##           master      #52   +/-   ##
=======================================
  Coverage   99.64%   99.64%
=======================================
  Files           4        4
  Lines         280      280
=======================================
  Hits          279      279
  Misses          1        1

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 bb5ba45...5f5bdf8. Read the comment docs.

@tisnik Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-52


Rosettacode grayscale implementation

An implementation of Rosettacode's grayscale task (http://rosettacode.org/wiki/Grayscale_image) with additional features, including creating a Bitmap from scratch and manipulating its individual pixels.

Jenkins: ok to test
Jenkins: add to whitelist

Nice proposal since it highlight the need of #1267 .
There is some issues in the code, especially missing documentation on classes and methods, but the documentation on the module is good.

Sure, I'll add documentation to the class and methods.
Thanks,
budi
On Tue, Apr 21, 2015 at 12:52 AM, Jean Privat<EMAIL_ADDRESS>wrote:

Nice proposal since it highlight the need of #1267
https://github.com/privat/nit/issues/1267 .
There is some issues in the code, especially missing documentation on
classes and methods, but the documentation on the module is good.
—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1282#issuecomment-94638278.

I added comments to my code and committed and pushed it to GitHub.
What is the procedure here, do I need to create another Pull Request? Or,
how do I add the latest commit to the previous Pull Request?
Thanks,
budi
On Tue, Apr 21, 2015 at 12:52 AM, Jean Privat<EMAIL_ADDRESS>wrote:

Nice proposal since it highlight the need of #1267
https://github.com/privat/nit/issues/1267 .
There is some issues in the code, especially missing documentation on
classes and methods, but the documentation on the module is good.
—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1282#issuecomment-94638278.

Nop, as you can see here, if you push on the same branch it automatically update your PR.
However, you should rebase your branch to merge the two commits. More information about this can be found on the nitlanguage.org website: http://nitlanguage.org/internal/workflow/

Not sure if I did it correctly.
I did "git rebase -i HEAD~1" on my local
Then I did "git push" but this was rejected, so I did a pull, performed
another rebase and pushed again.
Now the PR page looks like this:
https://github.com/privat/nit/pull/1282/commits
On Tue, Apr 21, 2015 at 5:53 PM, Alexandre Terrasa<EMAIL_ADDRESS>
wrote:

Nop, as you can see here https://github.com/privat/nit/pull/1282/commits,
if you push on the same branch it automatically update your PR.
However, you should rebase your branch to merge the two commits. More
information about this can be found on the nitlanguage.org website:
http://nitlanguage.org/internal/workflow/
—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1282#issuecomment-94954317.

When you was on the interactive rebase, did you merge the commits with the fixup or squash command?
Also, GitHub always reject fast-forward modification. When rebasing a branch, use the -f option to force the fast forward push.

These were the steps:

git rebase -i HEAD~2
It then opens a text editor that shows two commits, like this:

pick 01d1124 Rosetta 1
pick 6340aaa Rosetta 2
I then changed the second pick to squash and save the file.

git push

rejected.
What's the best way to fix this? Should I just delete the PR and start over?

If you just want to fix a commit, you can use fixup instead of squash. It does the same things but discard the second commit message. This is what you want to do in this case.
To avoid the rejected problem use git push <repo> <branch> -f

good.
For the missing bits, check the list on http://nitlanguage.org/internal/patches/

license header
signed-off by
whitespaces

@budi-kurniawan can you reroll the commits and make them nice an tidy?

Done. Only one nice commit now.
Thanks to Alexandre who's given me a pointer
On Thu, Apr 23, 2015 at 11:28 AM, Jean Privat<EMAIL_ADDRESS>wrote:

@budi-kurniawan https://github.com/budi-kurniawan can you reroll the
commits and make them nice an tidy?
—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1282#issuecomment-95625287.

jenkins: OK to test

jenkins test this please

still issues with:

the signed-off-by that does not match the author
whitespace errors

I've removed the whitespaces. They were not removed previously probably
because I was using the --online option, which was not recognized.
I've also made sure the commit has only one sign-off-by tag.
On Wed, May 6, 2015 at 11:15 AM, Jean Privat<EMAIL_ADDRESS>wrote:

still issues with:

the signed-off-by that does not match the author
whitespace errors

—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1282#issuecomment-99507643.

The author field is bad. it is budi2020 <budi2020@ubuntu14> but something like Budi Kurniawan<EMAIL_ADDRESS>would have been better.
I suspect that you did not configure your git correctly.

sorry, still learning git.
I just modified the author field of my last commit.
On Thu, May 7, 2015 at 8:51 PM, Jean Privat<EMAIL_ADDRESS>wrote:

The author field is bad. it is budi2020 budi2020@ubuntu14 but something
like Budi Kurniawan<EMAIL_ADDRESS>would have been better.
I suspect that you did not configure your git correctly.
—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1282#issuecomment-100056852.

ok to test

This library should be moved to lib/bitmap. image is too generic for a limited library in my opinion.

agree. bitmap is a better name than image for such a module.

I moved the classes to lib/bitmap. The thinking was that it could be part
of a larger image library, but I guess if that really happens we can always
move them to a lib/image.
In addition, I added the missing # between two comment lines.
I also liked the idea of making set_pixel more nit-ty as per Alexis's
suggestion, but then I thought a bitmap might have a color table and in
such an event, instead of setting a pixel, you would edit the color table.
In this case, set_pixel and edit_color_table would be equally important and
changing set_pixel to a default attribute would leave the impression that
set_pixel is more important.
On Fri, May 8, 2015 at 4:04 PM, Jean Privat<EMAIL_ADDRESS>wrote:

agree. bitmap is a better name than image for such a module.
—
Reply to this email directly or view it on GitHub
https://github.com/privat/nit/pull/1282#issuecomment-100343764.

I've implemented all the required changes


Numpy is not import

Issue Type: Feature Request
I've installed Numpy for python3, but when i import the package in Visual Studio Code i got this message error :
Import Error: No module named numpy.
I used pip3 install numpy to install it, the installation went very smoothly. and i try it in the terminal, it works very well but when i opend the file in Visual Studio Code and i executed it, i got the message error above.
Is there someone who has any idea about the problem?
VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:13:12.822Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

/extPython


Compile fail with cs (and probably java)

When I compile Data.hx, the error "No suitable overload for the super call arguments was found" happened on TmxImageLayer, TmxTileLayer and TmxObjectGroup class.
I guess this commit for [java/cs] isn't compatible with @structInit.
I hotfix by adding constructor and assign members manually as following:
@:structInit
class TmxImageLayer extends TmxBaseLayer
{
	@:optional public var image:TmxImage;

	public function new() {
		super();
	}
}

private function resolveImageLayer(input:Fast):TmxImageLayer
{
	var layer:TmxImageLayer = new TmxImageLayer();
	layer.name = input.att.name;
	layer.x = input.has.x ? Std.parseFloat(input.att.x) : 0;
	layer.y = input.has.y ? Std.parseFloat(input.att.y) : 0;
	layer.offsetX = input.has.offsetx ? Std.parseInt(input.att.offsetx) : 0;
	layer.offsetY = input.has.offsety ? Std.parseInt(input.att.offsety) : 0;
	layer.width = input.has.width ? Std.parseInt(input.att.width) : width;
	layer.height = input.has.height ? Std.parseInt(input.att.height) : height;
	layer.opacity = input.has.opacity ? Std.parseFloat(input.att.opacity) : 1;
	layer.visible = input.has.visible ? input.att.visible == "1" : true;
	layer.properties = resolveProperties(input);
	layer.image = input.hasNode.image ? resolveImage(input.node.image) : null;
	return layer;
}

// repeat 3 times for each class, fortunately each constructor is used only 1 times ...

However, it may lose meaning about adding @:structInit.
Maybe there is some more elegant solution for this problem?
If not, I could close this issue and living with hotfix :)

If you aren't afraid of performance punch which typedefs would bring, you can replace almost all @:structInit class to typedef (and the >BaseClass, inheritance method). I decided to go with classes for better performance, but typedefs is still a solution.
I never tested library with anything other than JS, CPP, HashLink and Neko. But given @:structInit is in the Haxe core, it's a bug in Java/C# part and I'd suggest making an issue on their side. :)

sure ! Many thanks~~~


feat: implemented pad, pad_end and truncate methods for strings

closes rodgeraraujo/reddish#5
I took some liberty with the pad methods, let me know if you want them implemented differently, or want any other changes for that matter :)

@gybrish Thank u for contributing, I will review asap.


[AVS V1.6] The AVS device didn't response any more after an hour.

Hi,
We have integrated avs sdk v1.6 on our Embedded board. It works well. But current we met a problem, It didn’t response any more after one hour. When this case happened, I said “alexa, what’s the time”, AVS Status changed to LISTENING,  and no longer change to other status. We checked website https://alexa.amazon.com/spa/index.html#player/history , and found the device was not connected.  If i restart the device, it works again, but the same problem will occur after an hour again. what caused this issue? Account permissions? Would you please check this problem?
Provide the steps to reproduce the issue, if applicable:
Place the device an hour.
Tell us about your environment:

What version of the AVS Device SDK are you using?
AVS 1.6
Tell us what hardware you're using:

[ ] Other - tell us more: Embedded device

Tell us about your OS (Type & version):

[ ] Yocto

Here is the detail log:
(180726_10:03:34.985)onKeyWordDetected keyword: alexa, beginIndex: 63007199, endIndex:63015120
(180726_10:03:34.987)info: (set_current_cloud_state) state=1, recognition_delay_slots=1
(180726_10:03:34.987)2018-07-26 02:03:34.189 [  d] 0 AudioInputProcessor:setState:from=IDLE,to=RECOGNIZING
(180726_10:03:34.987)2018-07-26 02:03:34.190 [  3] 0 DialogUXStateAggregator:setState:from=IDLE,to=LISTENING
(180726_10:03:34.987)2018-07-26 02:03:34.190 [  3] 5 TemplateRuntime:onDialogUXStateChanged:state=LISTENING
(180726_10:03:34.987)2018-07-26 02:03:34.190 [  8] 5 VisualActivityTracker:provideState
(180726_10:03:35.063)ityAgent:provideState:stateRequestToken=18
(180726_10:03:35.068)2018-07-26 02:03:34.190 [  8] 5 AudioActivityTracker:provideState
(180726_10:03:35.068)############################
(180726_10:03:35.068)#       Listening...       #
(180726_10:03:35.068)############################
(180726_10:03:35.068)2018-07-26 02:03:34.190 [  b] 5 VisualActivityTracker:executeProvideState
(180726_10:03:35.068)2018-07-26 02:03:34.190 [  b] 0 ContextManager:updateStateLocked:action=updatedState,namespace=VisualActivityTracker,name=ActivityState
(180726_10:03:35.068)2018-07-26 02:03:34.190 [  9] 0 ExternalMediaPlayer:executeProvideState:sendToken=true,stateRequestToken=18
(180726_10:03:35.068)2018-07-26 02:03:34.191 [  9] 0 ContextManager:updateStateLocked:action=updatedState,namespace=Alexa.PlaybackStateReporter,name=playbackState
(180726_10:03:35.068)2018-07-26 02:03:34.191 [  9] 0 ExternalMediaPlayer:executeProvideState:sendToken=true,stateRequestToken=18
(180726_10:03:35.068)2018-07-26 02:03:34.191 [  9] 0 ContextManager:updateStateLocked:action=updatedState,namespace=ExternalMediaPlayer,name=ExternalMediaPlayerState
(180726_10:03:35.068)2018-07-26 02:03:34.191 [  6] 5 NotificationsCapabilityAgent:executeProvideState:sendToken=true,stateRequestToken=18
(180726_10:03:35.068)2018-07-26 02:03:34.191 [  6] 0 ContextManager:updateStateLocked:action=updatedState,namespace=Notifications,name=IndicatorState
(180726_10:03:35.068)2018-07-26 02:03:34.191 [  e] 5 AudioActivityTracker:executeProvideState
(180726_10:03:35.068)2018-07-26 02:03:34.191 [  e] 0 ContextManager:updateStateLocked:action=updatedState,namespace=AudioActivityTracker,name=ActivityState
(180726_10:03:35.069)2018-07-26 02:03:34.191 [  8] 9 ContextManager:buildContextIgnored:namespace=VisualActivityTracker,name=ActivityState
(180726_10:03:35.069)2018-07-26 02:03:34.192 [  8] 0 ContextManager:buildContextSuccessful
(180726_10:03:35.069)2018-07-26 02:03:34.192 [  d] 0 AudioInputProcessor:executeOnContextAvailable
(180726_10:03:35.069)2018-07-26 02:03:34.192 [  d] 1 FocusManager:acquireChannel:channelName=Dialog,interface=SpeechRecognizer
(180726_10:03:35.069)2018-07-26 02:03:34.192 [  d] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=04181fa1-0f87-4573-8994-188526ab6a26,newValue=15f7f093-3fab-4e21-bf29-1f3e1ec35ebc
(180726_10:03:35.069)2018-07-26 02:03:34.192 [  d] 0 DirectiveProcessor:scrubDialogRequestIdLocked:dialogRequestId=04181fa1-0f87-4573-8994-188526ab6a26
(180726_10:03:35.069)2018-07-26 02:03:34.192 [  d] 0 EventBuilder:buildJsonEventString:messageId=eb7e6b1b-338f-4598-b38f-fa5a96075d26,namespace=SpeechRecognizer,name=Recognize
(180726_10:03:35.069)2018-07-26 02:03:34.192 [ 11] 9 AudioInputProcessor:onFocusChanged:newFocus=FOREGROUND
(180726_10:03:35.069)2018-07-26 02:03:34.192 [ 11] 5 AudioActivityTracker:notifyOfActivityUpdates
(180726_10:03:35.069)2018-07-26 02:03:34.192 [  e] 5 AudioActivityTracker:executeNotifyOfActivityUpdates
(180726_10:03:35.069)2018-07-26 02:03:34.193 [  d] 0 AudioInputProcessor:executeOnFocusChanged:newFocus=FOREGROUND
(180726_10:03:35.069)2018-07-26 02:03:34.193 [  d] 9 HTTP2Transport:enqueueRequest
(180726_10:03:36.810)[ 3972.912262] <0>.(0)[73:hps_main]CPU1: shutdown
(180726_10:03:36.821)[ 3972.912865] <0>.(0)[73:hps_main]CPU1 killed.
(180726_10:03:37.200)[ 3973.312030] <1>-(1)[0:swapper/1]CPU1: update cpu_capacity 1024
(180726_10:03:37.203)[ 3973.312775] <1>-(1)[0:swapper/1]CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
(180726_10:03:42.053)[ 3978.148833] <0>-(0)[1055:AlexaApp]android_usb gadget: [ratelimit]non-core control req21.00 v0000 i0000 l12
(180726_10:03:42.056)[ 3978.150588] <0>-(0)[1055:AlexaApp]android_usb gadget: [ratelimit]non-core control reqa1.01 v0000 i0000 l4096

Hi @MTKYZ,
This issue looks pretty similar to #727 which is a known bug. Can you please provide full logs for your issue?
Thanks,
Celina

Thank you for your reply, If not play music, just place there one hour, we also can reproduce the same issue.
alexa not response after one hour_log.txt

HI,
Thank you very much for your help, I can’t reproduce this issue when I set different device serial number for each devices in different area.
thanks

I am closing this issue due to inactivity. Please feel free to re-open it if it has been closed in error.


buff.lua logger crash

Was troubleshooting some buffing and uncommented a logger statement but it caused a crash.

In buff.lua #156

tried uncommenting this log and it seemed fine, not sure what happened there.

Hmm maybe was a buff I added to a class somewhere..will check with a fresh pull and add my class files one by one. Afk for a couple weeks so will try this mid may


Unrelated permissions for GET /users (Find-MgGraphCommand -Command Get-MgUser lists unrelated permissions)

The documentation for GET /users does not list any of the DeviceManagement* permissions that are included in the response to Find-MgGraphCommand -Command Get-MgUser:
PS C:\> $a = Find-MgGraphCommand -Command Get-MgUser
PS C:\> $a[0].Permissions

Name                                         IsAdmin Description                                   FullDescription
----                                         ------- -----------                                   ---------------
DeviceManagementApps.Read.All                True    Read Microsoft Intune apps                    Allows the app to...
DeviceManagementApps.ReadWrite.All           True    Read and write Microsoft Intune apps          Allows the app to...
DeviceManagementManagedDevices.Read.All      True    Read devices Microsoft Intune devices         Allows the app to...
DeviceManagementManagedDevices.ReadWrite.All True    Read and write Microsoft Intune devices       Allows the app to...
DeviceManagementServiceConfig.Read.All       True    Read Microsoft Intune configuration           Allows the app to...
DeviceManagementServiceConfig.ReadWrite.All  True    Read and write Microsoft Intune configuration Allows the app to...
Directory.Read.All                           True    Read directory data                           Allows the app to...
Directory.ReadWrite.All                      True    Read and write directory data                 Allows the app to...
User.Read.All                                True    Read all users' full profiles                 Allows the app to...
User.ReadBasic.All                           False   Read all users' basic profiles                Allows the app to...
User.ReadWrite.All                           True    Read and write all users' full profiles       Allows the app to...

@peombwa were you able to transfer this issue? please share the link

@njaci1, the issue was already transferred to DevX API repo - https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/1217.

DevX API merges permissions for Intune in the response. See Intune doc for getting users here. The description of the permissions could help you identify which one's to use.


[ SUGGESTION] Being able to see CPU and GPU usage

I love this mod but I feel that it lacks a basic feature: seeing the CPU and GPU usage

I think you can by downloading fpsdisplay

I agree. This is even present in the vanilla F3 menu so idk why this mod doesn't have it


please suggest a method or library statistics of traffic usage of chat bots

Hi Nazim, please suggest a method or library, framework format or library on git that can be used to implement in the personal profile of the service dalogbase user statistics of chat bots, statistics of traffic usage of chat bots, and the ability to accept payments for a given traffic. Thank you very much in advance!

Hey, sorry about it. I haven't had time to look into Dialoqbase currently, which is why there are so many pending feature implementations.
If you are looking for a BI tool, I suggest going for Metabase. It is open source and can be self-hosted (https://www.metabase.com/), allowing you to generate reports and statistics.

Nazim, good evening! I have connected the statistics meta database. please tell me in which tables to look for data for graphing statistics of the use of AI models token volume by bots ? thank you for the answer!

loaded as a service into docker, all tables appeared ! ) , but the question of where to find data for statistics chat bots has become even wider!) Nazim, please tell me where to look?


[licence-gather-plugin] Upon failure to find license, indicate the dependency

When running the license gather plugin, it may happen that LICENSE-like files are missing, but
the plugin does ot report which one, which is really tedious to identify if there are a lot of them.
> Task :modules:core:gatherLicense FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':modules:core:gatherLicense'.
> LICENSE-like files are missing
  ==============================

  BSD-3-Clause
  * org.pushing-pixels:radiance-animation:6.0.1
...

org.pushing-pixels:radiance-animation:6.0.1 does look like a dependency to me.
Could you please suggest which message would be better in that case?
The failure you have is that radiance-animation does list its license as BSD-3-Clause (I bet it is specified in pom.xml), however, the license text is not included into radiance-animation.jar.
If you shade (or include such radiance-animation.jar into your application) it would violate the terms of BSD-3-Clause because BSD-3-Clause requires including  copyright notice which is a part of the license.

Ahhh OK, I read this output wrong, I thought this dependency was correctly resolved. And didn't look at the jar.
Thank you very much for your clarification. Maybe the message might be improved to hint like you just did here.
Since I cannot fix the third party, maybe this can be fixed with something like (pseudo code as I'm on mobile now) :
ignoreMissingLicenseFor.add(SpdxLicense.BSD_3_Clause.asExpression())

Since I cannot fix the third party

Well, you can put the license file under your source control under licenses folder: https://github.com/apache/jmeter/tree/master/src/licenses/licenses/hamcrest
By default, it would check licenses/$artifactId folder, and you can override it via licenseFiles
        overrideLicense("org.hamcrest:$lib:2.2") {
            // https://github.com/hamcrest/JavaHamcrest/issues/264
            // pom.xml lists "New BSD License", however it is BSD_3
            expectedLicense = SpdxLicense.BSD_3_Clause
            licenseFiles = "hamcrest"
        }

OK, great thanks a lot !

I guess the ticket can be closed !


ignore local ip for ipv6

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Yes

@lwllvyb your change looks good. but please note, ceph-deploy is not maintained anymore. and we're not likely to cut a new release in future.

ok to test


proxy

Problem description

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

commit error


CI: semantic version. CMake DRY refactor

CI: avoid nuisance warnings about outdated libraries by using semantic versions in *.yml
CMake: DRY (don't repeat yourself) by refactoring to inspect target sources and set CXX property in one place.
CMake: avoid nuisance extra CTest targets and use consistent variable name NINJA_BUILD_TESTING by using enable_testing()

Hm ... isn't BUILD_TESTING supposed to be the clean solution to disable one's tests? Introducing our own variable sounds like a bad idea and not like the clean CMake way (not that there is one).


Add support for quota summary

This patch adds support for quota summary and an example that shows how
to use it.

@nimrodshn @tzvatot @ethernetdan please review.


Assigned ipBlocks are not released

Assigned blocks of IP addresses (etcd location /calico/ipam/v2/assignment/ipv4/block/<ip-block>) are not released even if those are not assigned to nodes.
Expected Behavior
When there are no blocks, assigned to nodes (block is not assigned to any node at /calico/ipam/v2/host/<host>/<block>), I expect them to be released from /calico/ipam/v2/assignment/ipv4/block/<ip-block>.

Possible Solution
When the block is not assigned to the host - release it from assignments.
Steps to Reproduce (for bugs)

Create Kubernetes cluster with calico as cni plugin.
Create a bunch of deployments/replicasets/jobs, which will then create enough number of pods to have as many blocks assigned to hosts as possible. For this, we can set up small ipam size (e.g. /27) with small subnet size (e.g. /29).

Context
In the old cluster with ipam network size /18 and subnet block size /26 (default) we got into a situation, where there were 16 subnets, assigned to hosts(/calico/ipam/v2/host/<host>/<block>), but ~240 subnets in assignments (/calico/ipam/v2/assignment/). That lead is into the issue like
  Warning  FailedCreatePodSandBox  11m (x815 over 44h)    kubelet, worker-x53vn-7f9964b764-2rlb6  (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "495cffc4ae7e0e717a62ca01f8249a42928997e9d37e604e2bf2440d108ff0f4" network for pod "test-report-service-7c7f8486bd-qkbl8": NetworkPlugin cni failed to set up pod "test-report-service-7c7f8486bd-qkbl8_default" network: failed to request 1 IPv4 addresses. IPAM allocated only 0

After manual cleaning etcd of all the subnets, which were not assigned to hosts, issues were resolved. E.g.
# get ipblocks, marked as assigned
etcdctl get /calico/ipam/v2/assignment/ipv4/block --prefix --keys-only | grep block | awk -F "/" '{print $NF}' > assigned-by-blocks
# get ipblocks, actually used by nodes
etcdctl get /calico/ipam/v2/host/ --prefix --keys-only | grep block | awk -F "/" '{print $NF}' > assigned-by-nodes
# delete intersection from lists above
for block in `grep -Fvf assigned-by-hosts assigned-by-blocks`; do etcdctl del /calico/ipam/v2/assignment/ipv4/block/${block}; done

Your Environment

Calico version: 3.7.2
Orchestrator version (e.g. kubernetes, mesos, rkt): Kubernetes 1.14.3
Operating System and version: CoreOS 2191.0.0
Link to your project (optional):

Are you running calico-kube-controllers?  That's supposed to clean up blocks when the node is deleted.

@fasaxc yes, we are running kube-controller. And it didn't cleanup ipBlocks

Hmm, maybe we're missing that logic for etcd mode.  Looks like it might have been added to Kubernetes datastore mode only.

We clean up IPAM blocks in etcd mode as well, but through the standard node deletion process.
Do you see non-existent nodes hanging around? calicoctl get nodes should only show real nodes that haven't been torn down.

IP blocks won't get deleted unless:

The no longer have affinity to a node, AND
There are no IPs assigned within the block.

Can you check to see if the unexpected blocks meet those criteria?

What I've tried - draining node and restarting it. So, all the pods where unscheduled from that node. After that node was completely deleted from Kubernetes, it also wasn't visible in list of calico peers. Therefore it was deleted from /calico/ipam/v2/host/<host>/<block>. But all the released block were not cleaned up from assignments.

@corest could you paste in the contents of one of the blocks that you think should be deleted?
When a node is deleted, we free any pod IP addresses that we think should be removed here: https://github.com/projectcalico/libcalico-go/blob/master/lib/clientv3/node.go#L118
Then, we remove that host's tree here: https://github.com/projectcalico/libcalico-go/blob/master/lib/ipam/ipam.go#L1053-L1110
If the /calico/ipam/v2/host entry is gone for that node, we're likely getting that far.
So long as all the IP addresses are successfully released, then I would expect executing this line to also delete the blocks: https://github.com/projectcalico/libcalico-go/blob/master/lib/ipam/ipam.go#L1065
So, my suspicion is that there is still an address remaining in the block which is preventing it from being deleted. My (further) suspicion is that it is the IPIP tunnel address that is being left around, since I don't see that it gets released in that code snippet above!

Thanks @corest for raising this.
In our production cluster running on k8s v1.10.11 and Calico v3.2.3, we managed to hit the limit for IP blocks.
spec:
    blockSize: 26
    cidr: <IP_ADDRESS>/11

/11 gives us a total of 2097150 addresses
block size of /26 is 64 addresses
We do cluster autoscaling - so nodes keep downscaling very often multiple times in a day. And in the past few weeks we are encountering - https://github.com/projectcalico/libcalico-go/blob/master/lib/ipam/ipam.go#L445
because of which whenever a new node is spun up by autoscaler, the calico-node keeps retrying and goes into a crashloop mode.
Our /calico/ipam/v2/assignment/ipv4/block has 32671 blocks that were not used by current hosts.
Looking at one particular node that does not exist in the cluster today as an example to trace the IPAM activities, I see
ipam.go 910: Releasing IPAM affinities for host host=\"ip-xx-xx-xx-xx\
ipam.go 917: Querying IPAM host tree in data store host=\"ip-xx-xx-xx-xx\
ipam.go 921: Failed to get IPAM host error=resource does not exist: IPAMHostKey(host=ip-xx-xx-xx-xx) with error: <nil> host=\"ip-xx-xx-xx-xx\"

We never reach to https://github.com/projectcalico/libcalico-go/blob/release-v3.2/lib/ipam/ipam.go#L926

Here is the content from the unreleased block (there is no even information about the node)
https://gist.github.com/corest/5863287f36f59ac80a36f57aad42b62a

@corest thanks for that. It definitely looks like there are still addresses assigned within the block.
Have you checked to see if those addresses are actually in-use within the cluster?
It would be useful to know, for example, if any workload has some of these addresses (which appear to be allocated in the output you showed)

<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

Just checked - there are no pods with those IP addresses from handles subnets

Ok, this definitely sounds like a bug. I'm not sure how we got into this state though. We might be able to add a backstop to kube-controllers to reconcile these away when it spots unused IP addresses, but I'd like to understand the root cause of this anyway.
I think it would be good to see the full kube-controllers log (probably set to debug level logging) and if possible, the full CNI plugin logs (from the container runtime) on a node that has been removed from the cluster.
kube-controllers is responsible for identifying when nodes are removed and cleaning this up, so that's the more important of the two.

We having the same issue. We are using calico 3.3 on kubernetes 1.11.
The container even stuck at creation phase because these unrelease affinity.
Our case it is because can not get IPAM host when calico-kube-controllers try to delete the node.  https://github.com/projectcalico/libcalico-go/blob/4346117ce592eedcc83269c09fbc4a1e652d0b76/lib/ipam/ipam.go#L1081
After a while our etcd if full with this kind of data
{"cidr":"<IP_ADDRESS>/26","affinity":null,"strictAffinity":false,"allocations":[0,null,null,null,null,0,0,null,null,0,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"unallocated":[18,20,19,24,21,12,26,23,28,27,30,31,34,32,33,4,36,39,62,35,37,38,41,42,40,44,47,45,46,49,48,51,50,52,55,53,54,2,56,58,57,60,43,22,63,1,3,61,7,11,13,10,14,16,15,17,59,8,29],"attributes":[{"handle_id":null,"secondary":null}]}

We are using calico 3.3 on kubernetes 1.11.

We've made a number of improvements to Calico's IPAM since that release, including several bug fixes in this area. I recommend trying on a cluster using the latest Calico release to see if you are still affected.
That said, it does seem like there is at least one issue that still exists in v3.7+ - it's just that it might not be the same issue you are encountering on v3.3

I've spent a fair bit of time trying to break a Calico v3.8 cluster in the way you guys seem to be experiencing it above, unfortunately with no luck.
Do you happen to have the kube-controllers logs from a cluster that is in this state? And perhaps the logs from one of the nodes?

{"cidr":"<IP_ADDRESS>/26","affinity":null,"strictAffinity":false,"allocations":[0,null,null,null,null,0,0,null,null,0,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null],"unallocated":[18,20,19,24,21,12,26,23,28,27,30,31,34,32,33,4,36,39,62,35,37,38,41,42,40,44,47,45,46,49,48,51,50,52,55,53,54,2,56,58,57,60,43,22,63,1,3,61,7,11,13,10,14,16,15,17,59,8,29],"attributes":[{"handle_id":null,"secondary":null}]}

@cvs77 I think this block indicates it's a different issue than the one @corest is experiencing. You can see they are all using the same index - 0- which I think means other nodes are borrowing tunnel address from this block.
I suspect that you're encountering the issue that was fixed by this PR in Calico v3.9: https://github.com/projectcalico/libcalico-go/pull/1111
Upgrading to v3.9 will be part of the fix, but you'll also need to delete those blocks which aren't being used so they can become available again.

network: failed to request 1 IPv4 addresses. IPAM allocated only 0

For completeness, it would also be useful if you could download the latest calicoctl tool and run calicoctl ipam show --show-blocks

I don't think I am experiencing the exact issue that is here, but the solution provided in original description saved our bacon in our production cluster so I wanted to note that thanks here as well as the details for any future person who may benefit from it as we have.
We are on k8s 1.10 and Calico 2.6.7, however we upgraded to Calico 2.6.12 and still saw this issue, although we are still using 1.03 of the kube-controller which may be where the bug still is.
Our cluster had been running fine for more than a year and then all of the sudden when new nodes would come up the Calico pod and kube-proxy pod would come up, but any pod that required ip assignment would fail after some time with the error:
network is not ready: [runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized]Failed create pod sandbox: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Effectively the Node would come up and claim it was healthy, but no pods could actually run on it. This first started appearing and after like 20 minutes the node would "fix" itself so it was just a nuisance which slowed down our scaling ability speed, but it didn't kill us. But as time went on, slowly that time went from 20 minutes to hours to the point where only 20% of our nodes would ever come up. In retrospect it appears that some IP blocks were getting released while others weren't so we were slowly choking ourselves out to the point to where we wouldn't be able to bring up anything.
Luckily after many nights of digging into this we were able to piece it together and through this bug report and the remedy provided by @corest we were able to determine that clearing the allocated blocks that were not actually allocated to a node immediately fixed the problem. Once we did that everything started working again and we are in a good state now. It does appear this is likely fixed in newer versions, but for anyone still stuck on older versions like we are this may be something you run into as well.
Another item of note, as we got in a worse state in addition to the pods not coming up with that error we also saw our Master nodes getting hit incredibly hard with high CPU and constant network and IO traffic. Before we knew what was going on we thought our etcd or Master nodes were the problem and scaled those up but to no avail. Of course now that we know what the issue is it ended up being that Calico was pounding the heck out of etcd trying to find an available block to hand out. Once we cleared the blocks the CPU and load on etcd went back to normal and we were able to scale back down on our Master nodes.
I know this likely doesn't help in triaging the current issue since we are so far behind on our version, but thanks community! If by some way this does help, please let me know if there is any more info I can provide to help diagnose the issue.

Wanted to check up on this one - has anyone had any breakthroughs or been able to gather any additional information?

I've been looking at this a bit more recently. We have this existing controller function that handles cleaning up orphaned IPAM blocks (and any addresses within) when using the Kubernetes API / CRD backed data store: https://github.com/projectcalico/kube-controllers/blob/master/pkg/controllers/node/kdd.go#L36
However, it's not run when in etcd mode. I think this is because we had an existing solution for etcd mode. However, the main difference between these two is that the etcd implementation looks at workload endpoints in the data store to determine which addresses need to be cleaned up, whereas the kubernetes variant looks at addresses assigned within blocks and compares them to pods that exist in the k8s API. (When we implemented the k8s version, we also tagged IP allocations with new metadata that previously didn't exist and so wouldn't have been possible for etcd).
This means that in etcd mode, its possible a workload endpoint could be deleted without the IP allocation being freed, and then we'd effectively leak that address.
Doing a code read, I'm not sure there's any reason we can't now enable this IPAM cleanup logic for etcd mode as well, which I believe will help catch issues like this one. Unless we also make other changes, it will only do it when a node is removed from the cluster, but we could also consider adding a periodic sync.
The thing to note about the existing implementation is that it will only clean up an IPAM block when:

The node is no longer present in the k8s API
All the allocations within that block are no longer in use by any pod in the k8s API.

That means it won't, without modification, catch cases where a single IP has been leaked on a node that is still around. I think this is probably OK, because:

We want to be extra safe here anyway. Accidentally cleaning up an IP address that is still in use would be bad.
All the reported instances of this seem to do with node auto-scaling, which leads me to believe the leaked addresses have to do with nodes being deleted anyway.

So, my proposal would be to start by enabling the existing cleanup logic on etcd, and see if that resolves the issues listed here.

I'm going to close this since we've fixed a number of IP address leaking issues in the last couple of releases.
I think if users still encounter issues with the latest release we should open new issues for further investigation. Thanks all.

Are you running calico-kube-controllers? That's supposed to clean up blocks when the node is deleted.

Can you please let me know if you are talking about the calico-kube-controller pod?


fix(helm): sort release list with flags --reverse and --date

What this PR does / why we need it:
Bug fix and closes #5499
Special notes for your reviewer:
Apart from fixing the bug for --date and --reverse flags in helm list command, this PR also makes sure the behavior is as expected if both --date and --reverse flags are enabled
Precisely:
helm list (Default case - sort by name Asc)
helm list -r sorts by name Desc
helm list -d sorts by date Asc (recent updated release last)
helm list -d -r sorts by date Desc (recently updated release first)
If applicable:

[ ] this PR contains documentation
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Would you mind fixing up the failing test case?
--- FAIL: TestList_Sort (0.00s)
    list_test.go:97:
        	Error Trace:	list_test.go:97
        	Error:      	Not equal:
        	            	expected: "two"
        	            	actual  : "one"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-two
        	            	+one
        	Test:       	TestList_Sort
    list_test.go:99:
        	Error Trace:	list_test.go:99
        	Error:      	Not equal:
        	            	expected: "one"
        	            	actual  : "two"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-one
        	            	+two
        	Test:       	TestList_Sort
FAIL

@hickeyma Hi, Thanks for the review!
Sorry, I couldn't understand the snippet in your comment. Shouldn't it be as below?
$ helm list -d
NAME                       	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART
martychrt-1554198221       	default  	2       	2019-04-02 11:14:12.297504181 +0100 IST	deployed	martychrt-0.1.0
fooxxxxxxxxxxxxx           	default  	1       	2019-04-02 14:08:03.560578811 +0100 IST	deployed	foo-0.1.0
foo-0.1.0-beta.1-1554210628	default  	1       	2019-04-02 14:10:28.122494225 +0100 IST	failed  	foo-0.1.0-beta.1-0.1.0
fooxxxxxxxxxxxxx-1554210671	default  	1       	2019-04-02 14:11:11.871312236 +0100 IST	deployed	fooxxxxxxxxxxxxx-0.1.0

$ helm list -d -r
NAME                       	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART
fooxxxxxxxxxxxxx-1554210671	default  	1       	2019-04-02 14:11:11.871312236 +0100 IST	deployed	fooxxxxxxxxxxxxx-0.1.0
foo-0.1.0-beta.1-1554210628	default  	1       	2019-04-02 14:10:28.122494225 +0100 IST	failed  	foo-0.1.0-beta.1-0.1.0
fooxxxxxxxxxxxxx           	default  	1       	2019-04-02 14:08:03.560578811 +0100 IST	deployed	foo-0.1.0
martychrt-1554198221       	default  	2       	2019-04-02 11:14:12.297504181 +0100 IST	deployed	martychrt-0.1.0

Also, didn't quite understand your question. I believe we have one row per release, right? unlike helm history

@jan25's output is correct. The date sort should only work against the displayed release versions. When the user inputs helm list --date, the intent is to sort the releases by the time each release was last updated.

@adamreese would you mind taking a look?

The date sort should only work against the displayed release versions. When the user inputs helm list --date, the intent is to sort the releases by the time each release was last updated.

@bacongobbler @jan25 Sorry if I didn't clarify the comment above correctly. I agree with your definition on how it work. However when I test from the CLI with releases previously deployed, this is the output I am getting which seems incorrect to me:
$ helm list -d
NAME                       	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART
fooxxxxxxxxxxxxx           	default  	1       	2019-04-02 14:08:03.560578811 +0100 IST	deployed	foo-0.1.0
fooxxxxxxxxxxxxx-1554210671	default  	1       	2019-04-02 14:11:11.871312236 +0100 IST	deployed	fooxxxxxxxxxxxxx-0.1.0
martychrt-1554198221       	default  	2       	2019-04-02 11:14:12.297504181 +0100 IST	deployed	martychrt-0.1.0
foo-0.1.0-beta.1-1554210628	default  	1       	2019-04-02 14:10:28.122494225 +0100 IST	failed  	foo-0.1.0-beta.1-0.1.0

$ helm list -d -r
NAME                       	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART
foo-0.1.0-beta.1-1554210628	default  	1       	2019-04-02 14:10:28.122494225 +0100 IST	failed  	foo-0.1.0-beta.1-0.1.0
martychrt-1554198221       	default  	2       	2019-04-02 11:14:12.297504181 +0100 IST	deployed	martychrt-0.1.0
fooxxxxxxxxxxxxx-1554210671	default  	1       	2019-04-02 14:11:11.871312236 +0100 IST	deployed	fooxxxxxxxxxxxxx-0.1.0
fooxxxxxxxxxxxxx           	default  	1       	2019-04-02 14:08:03.560578811 +0100 IST	deployed	foo-0.1.0

@hickeyma are you using helm cli which is built with this PR? I tested it on my local machine, it looked ok for than 2 releases. Although, the test cases have just 2 releases. From your example, I suspect you might be running helm v3 missing changes from this PR, could you confirm?

@jan25 I have picked up your changes. The reverse works for alphanumeric:
$ helm list
NAME                       	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART
foo-0.1.0-beta.1-1554210628	default  	1       	2019-04-02 14:10:28.122494225 +0100 IST	failed  	foo-0.1.0-beta.1-0.1.0
fooxxxxxxxxxxxxx           	default  	1       	2019-04-02 14:08:03.560578811 +0100 IST	deployed	foo-0.1.0
fooxxxxxxxxxxxxx-1554210671	default  	1       	2019-04-02 14:11:11.871312236 +0100 IST	deployed	fooxxxxxxxxxxxxx-0.1.0
martychrt-1554198221       	default  	2       	2019-04-02 11:14:12.297504181 +0100 IST	deployed	martychrt-0.1.0
usr1@helm-v3:~/test/helm-charts$ helm list -r
NAME                       	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART
martychrt-1554198221       	default  	2       	2019-04-02 11:14:12.297504181 +0100 IST	deployed	martychrt-0.1.0
fooxxxxxxxxxxxxx-1554210671	default  	1       	2019-04-02 14:11:11.871312236 +0100 IST	deployed	fooxxxxxxxxxxxxx-0.1.0
fooxxxxxxxxxxxxx           	default  	1       	2019-04-02 14:08:03.560578811 +0100 IST	deployed	foo-0.1.0
foo-0.1.0-beta.1-1554210628	default  	1       	2019-04-02 14:10:28.122494225 +0100 IST	failed  	foo-0.1.0-beta.1-0.1.0

@jan25 As further testing, could you try and add a few more releases to your current list with different update times?

@hickeyma I'll improve the test cases to have more releases

@hickeyma I added two more releases to test cases and updated the expected output files for tests. Meanwhile i found issues in list.go such as --all and -- superseded weren't working as expected, so i fixed them too in recent commits. It was a good idea to improve and have robust test cases.
@bacongobbler Could you guys please do a review once again considering the recent changes i have made?

@hickeyma I couldn't reproduce on my machine at first, but using the output you provided i could spot a bug in ByDate sorter. Thanks for checking!

Is it a good idea to add v3 tag to this PR? How can i do that? Perhaps it can be done by maintainers only?

@adamreese Do you mind taking a look when you get a chance?


Feature: Add OTP Verification for User Phone Number

Description
Currently, the phone number field in the user profile allows users to input any number without any validation or verification. This could lead to users entering invalid or incorrect phone numbers, potentially causing issues in case we need to contact them or send important notifications.
Proposed Solution:

Implement an OTP (One-Time Password) based phone number verification system.
Once a user adds or updates their phone number, send a verification OTP to the provided number.
The user will need to enter the OTP to successfully verify their phone number.
Only after verification should the phone number be considered valid and saved to the user profile.

Please assign this issue to me and add the necessary tags.

thanks for raising this issue, but this is not required at the moment, ;)


Space for Name is too short, no minimize and no button for friendlist intended?

Hello there,
see attached. My profile name seems to be too long, so it gets cut. Is there a solution?
Futhermore, there doesn't seem to be a mini- or maximize button, is that intended? On top, there is no button for the friendlist, I have to use rightclick - friendlist from my steam-taskbar-button.
I am using Fedora 36, Steam package is from rpmfusion.

My profile name seems to be too long, so it gets cut. Is there a solution?

Not really:

All buttons are 120px wide like in GNOME ViewSwitcher.
You'd probably have the same issue if a native libadwaita app did the same thing and tried to display a long string as a ViewSwitcher tab.
You can increse width of the buttons here, then you will need to adjust the positions of icons.
You can completely remove width=120 from uinavigatorpanel.layout to let the buttons wrap their text, but then the icons won't line up and it won't look like Adw.ViewSwitcher.

there doesn't seem to be a mini- or maximize button, is that intended?

Yes, because that's how GNOME looks by default. There is an installer script that has a few window controls presets, see the Installation section of the readme or #13.

On top, there is no button for the friendlist

It was removed because there were too many buttons there for smaller window sizes.
You can add it back by editing steamrootdialog.layout. Move view_friends control from line 18 to line 11, for example
place { control="InboxButton,SupportAlert,ParentalLockButton,view_friends,MenuBar"


Remove: Unity.Unity.6000.WindowsIL2CPP version 6000.0.12f1

Microsoft Reviewers: Open in CodeFlow

URL: https://download.unity3d.com/download_unity/7defd84cdab8/TargetSupportInstaller/UnitySetup-Windows-IL2CPP-Support-for-Editor-6000.0.12f1.exe
OK
(Automated message - build 923)

https://github.com/microsoft/winget-pkgs/pull/186121#issuecomment-2445759087

[Policy] Needs-Manual-Merge


Failed validation: #/definitions/SearchResult

Validation Error
Minimal Reproduction

y2.search("AMZN").then(d=> d.quotes);

Symbol(s) that it happened for

AMZN

Error Message

> The following result did not validate with schema: #/definitions/SearchResult
[
  {
    instancePath: '',
    schemaPath: '#/additionalProperties',
    keyword: 'additionalProperties',
    params: { additionalProperty: 'screenerFieldResults' },
    message: 'must NOT have additional properties'
  },
  {
    instancePath: '',
    schemaPath: '#/additionalProperties',
    keyword: 'additionalProperties',
    params: { additionalProperty: 'timeTakenForScreenerField' },
    message: 'must NOT have additional properties'
  }
]

This may happen intermittently and you should catch errors appropriately.
However:  1) if this recently started happening on every request for a symbol
that used to work, Yahoo may have changed their API.  2) If this happens on
every request for a symbol you've never used before, but not for other
symbols, you've found an edge-case.  Please see if anyone has reported
this previously:

  https://github.com/gadicc/node-yahoo-finance2/issues?q=is%3Aissue+Failed%20validation%3A%20%23%2Fdefinitions%2FSearchResult

or open a new issue (and mention the symbol):

  https://github.com/gadicc/node-yahoo-finance2/issues/new?labels=bug%2C+validation&template=validation.md&title=Failed%20validation%3A%20%23%2Fdefinitions%2FSearchResult

For information on how to turn off the above logging or skip these errors,
see https://github.com/gadicc/node-yahoo-finance2/tree/devel/docs/validation.md.

Uncaught FailedYahooValidationError: Failed Yahoo Schema validation
    at Object.validate [as default] (/Users/aronrodrigues/workspace/tribie-app/functions/node_modules/yahoo-finance2/dist/cjs/src/lib/validateAndCoerceTypes.js:194:15) {
  result: {
    explains: [],
    count: 10,
    quotes: [ [Object], [Object], [Object], [Object], [Object], [Object] ],
    news: [ [Object], [Object], [Object], [Object] ],
    nav: [],
    lists: [],
    researchReports: [],
    screenerFieldResults: [],
    totalTime: 83,
    timeTakenForQuotes: 478,
    timeTakenForNews: 700,
    timeTakenForAlgowatchlist: 400,
    timeTakenForPredefinedScreener: 400,
    timeTakenForCrunchbase: 400,
    timeTakenForNav: 400,
    timeTakenForResearchReports: 0,
    timeTakenForScreenerField: 0
  },
  errors: [
    {
      instancePath: '',
      schemaPath: '#/additionalProperties',
      keyword: 'additionalProperties',
      params: [Object],
      message: 'must NOT have additional properties'
    },
    {
      instancePath: '',
      schemaPath: '#/additionalProperties',
      keyword: 'additionalProperties',
      params: [Object],
      message: 'must NOT have additional properties'
    }
  ]
}

// Returned quotes:
[
    {
      exchange: 'NMS',
      shortname: 'Amazon.com, Inc.',
      quoteType: 'EQUITY',
      symbol: 'AMZN',
      index: 'quotes',
      score: 31857500,
      typeDisp: 'Equity',
      longname: 'Amazon.com, Inc.',
      isYahooFinance: true
    },
    {
      exchange: 'MEX',
      shortname: 'AMAZON COM INC',
      quoteType: 'EQUITY',
      symbol: 'AMZN.MX',
      index: 'quotes',
      score: 20328,
      typeDisp: 'Equity',
      longname: 'Amazon.com, Inc.',
      isYahooFinance: true
    },
    {
      exchange: 'NEO',
      shortname: 'AMAZON.COM CDR (CAD HEDGED)',
      quoteType: 'EQUITY',
      symbol: 'AMZN.NE',
      index: 'quotes',
      score: 20152,
      typeDisp: 'Equity',
      isYahooFinance: true
    },
    {
      exchange: 'BUE',
      shortname: 'AMAZON COM INC',
      quoteType: 'EQUITY',
      symbol: 'AMZN.BA',
      index: 'quotes',
      score: 20064,
      typeDisp: 'Equity',
      longname: 'Amazon.com, Inc.',
      isYahooFinance: true
    },
    {
      exchange: 'OPR',
      shortname: 'AMZN Aug 2021 3300.000 put',
      quoteType: 'OPTION',
      symbol: 'AMZN210813P03300000',
      index: 'quotes',
      score: 20026,
      typeDisp: 'Option',
      isYahooFinance: true
    },
    {
      exchange: 'OPR',
      shortname: 'AMZN Aug 2021 3400.000 call',
      quoteType: 'OPTION',
      symbol: 'AMZN210813C03400000',
      index: 'quotes',
      score: 20025,
      typeDisp: 'Option',
      isYahooFinance: true
    }
  ]

Environment
Node
Node version 16.5.0
Npm version: 6.14.13
Library version 1.14.3
Additional Context

Hey @aronrodrigues, thanks for reporting.  Looks like Yahoo just added this field.  This is fixed in our devel branch, but since it's very new, I'm not releasing yet until we've had a little more experience with it.

In particular, we're accepting { screenerFieldResults?: Array<any>; } since we have no data yet on what this new field is meant to contain.

Hey @aronrodrigues, v1.14.4 partially fixes this, so that it no longer throws an error, but we still don't actually know what this data looks like.  Will track further developments in #259, but closing at least this validation error for now.  Thanks again for reporting!


[REQUEST] How to update custom formats with changes on GitHub

For which application would like to see this Guide ?
Radarr
Describe what you would like to see in the Tutorial/Guide
At the moment I'm having to delete a custom format and re-add it, which involves resetting a custom format score in the profiles. Although I guess this isn't something that Radarr supports? Editing the custom formats should allow you to paste in the new text and it should override the previous value without losing the scores.
Actually was thinking of raising an issue in the Radarr repo about this configuration approach. To my mind it should just be a directory that Radar reads with a bunch of text files in it with all my configuration changes, it's then trivial to update/backup/store in a git repo etc.
It seems that at the moment we have a binary SQL database which needs zipping up and backing up somewhere.

Well I got good news for you then.
That already exist

It's possible with Notifiarr
It's possible with trash-updater

Any other questions about it you can ask in our Discord Support Channel
And your other question seems to have been merged in to Radarr nightly.
#440

Done with #445 in a own guide (This includes also links to the automation applications)


Catalina upgrade -- node/terminal full disk access

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
Catalina issue with env pull/push
Amplify CLI Version
4.11.0
To Reproduce
Upgrade to Catalina, and Upgrade from Amplify 3.x to 4.x
Expected behavior
Amplify push work normally
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Mac OS Catalina
Node Version. 10, 12

Additional context
This is more informational than a bug report just in case others run into this issue. If you upgrade to catalina, and are also mid-upgrade of an amplify version that uses different configuration files, weird things start happening on amplify env pull --restore / amplify pull. I found others having similar issues with watchman
Basically, if you're having issues where amplify pull or amplify env pull --restore create duplicate files with a space " " and a number after, it's because you need to allow terminal/node to have full disk access. I encountered issues because it created additional CustomResources files on a colleague's machine, and amplify would create CloudFormation Definitions for those resources with a space in them which is not allowed.
TLDR; if you're upgrading to Catalina, give terminal full disk access.

@stefangomez Thanks for the information. This would be useful for anyone else trying to update to Catalina.

Same situation occurred to me when I ran amplify env pull --restore, duplicated files with exactly the same situation like this popped out from nowhere. But my OS is mac Mojave, any ideas why this could happen? Thanks!

I wonder why does it register the entire user directory as a Watchman root in the first place?


Standardize the payload names

payload "username" need to be changed to "email" for /v1/auth

Done

@Joel-C-Johnson Thanks, I'm merging it now


v1.6.4: Pause is not working

tested v1.6.4 on SITL, Pause commend seem to be not responding at all

Checking.

Works just checked.

It does not work when you are in a mission. I fixed that in dbc7d805f2. If you flash the current developer version it should be fine again.

Thanks, works just fine now.
I think its should be included in the stable release as well, that’s a serious safety issue right now


🧠 Specify Dataspace smart contract

Description
Provide the first specification elements about a dataspace smart contract that'll be in charge of performing all the possible actions in a dataspace.
The smart contract specification shall meet the following responsibilities:

Condition any actions against governance rules
Provide changing governance rules mechanism
Sync the ontology by reflecting any mutations in it

Finally, we shall find a name for it.

Closing this one in favour of #328


add vendor to this project

some package need to download ,please add vendor

In general this repository is a library and not a full application. A command line tool exists but in a very early state. In general, libraries should not have vendor/ directories in Go.

Closing this as won't fix. As said above, this is a lib and its highly unlikely we will add a vendor folder. But if you have good reasons for a vendor folder, please feel free to re-open.


Error code 200 -  while getting Bid/ask for multiple coins

Describe your environment

Operating system: Win 10
Python Version: _____ 3.8.3

Your question
Get error code 200, while running a loop for 10 coins
import pandas as pd
import http.client
import json
import requests
from bitbnspy import bitbns

# BNS Private Keys
key = ''
secretKey = ''
bitbnsObj = bitbns(key, secretKey)

#Get Tickers
tickerdf = pd.read_excel (r'C:\Documents\Crptos\StaticData.xlsx', sheet_name= 'BNS')

for index,row in tickerdf.iterrows():

    ticker1 = row['BNSTicker']
     # -------------------------------------------get the order book for specific pair

    #get sell/ask orderbook
    data = bitbnsObj.getSellOrderBook(ticker1)
    CoinBuy = pd.json_normalize(data, "data", meta=["status", "error","code"])

    #get Buy/bid orderbook
    data = bitbnsObj.getBuyOrderBook(ticker1)
    CoinSell = pd.json_normalize(data, "data", meta=["status", "error","code"])

    time.sleep(10)

Please advise solution, as i dont want to use time.sleep function and sometimes, it still gives error in fetching data
Ticker list is here:
BTCUSDT
ETHUSDT
XRPUSDT
ADAUSDT
TRXUSDT
LTCUSDT
BCHUSDT

hi, response code - 200 means the requested action has been performed without any problems.
could you please specify what issue you are facing ?
also the time.sleep(10), you can reduce the time between requests (to around 1s or so),
you can check the number of requests remaining using bitbnsObj.getApiUsageStatus()

the error i get is " KeyError: "Try running with errors='ignore' as key 'code' is not always present"
Also the JSON output stored in data - dataframe is" Some error in get req"
this usually happens when i run for 30 coins and i have double checked in UI that the bid /ask is present for those 30 coins.
If i make time.sleep(10) to 1s, then it gives the above error more frequently.

What is the limit for no of requests? and can this be increased?

API limit is per month or per day?

API limit is per month or per day?

per minute.

Thanks Sanket for the above.
Please advise on the error while requesting for 20 coins together. checked the ApiUsageStatus and its in abundance.


Polkadot: Implement caller_is_root runtime API

Recent versions of the contracts pallet expose a runtime API for contracts to check whether their caller is of root origin. The PR exposes this API as a builtin.

Moved the clippy driveby changes into #1261


Wr/delete custom labels

What does this PR do?
when a single CL is specified for delete, only delete that label from the CLs file
What issues does this PR fix or reference?
@W-13167950@
https://github.com/forcedotcom/cli/issues/2118

QA: turned Willie's STL PR into 3.2.0-beta.1 for local testing
using the sfdx-delete-customlabel repo, sf project deploy start
source delete
✅  can delete one label via sf project delete source --metadata CustomLabel:KeepMe2 --track-source
👎🏻  I don't think this is true now for Labels.  I don't expect you to delete the file.
This operation will delete the following files on your computer and in your org:
/Users/shane.mclaughlin/eng/repros/sfdx-delete-customlabel/force-app/main/default/labels/CustomLabels.labels-meta.xml

✅👎🏻 error when deleting something fictitious.  Expected our usual red Error: blah stuff, and something about why, maybe?

👎🏻 and did you really update source tracking?
2 labels remain in the file, and I say to delete one of them, and then make up something else to delete.
✅ nothing is deleted.
✅ when I delete both remaining labels, the file disappears

project deploy/retrieve stuff
I put the labels back in the org.
✅ delete label in org, looks fine locally after retrieve (pull-like)
✅ when I delete all the labels from the org, the file deletes.
I put the labels back in the local project and the org.
remove 1 label from the local file
❌ project deploy start (like a push)
It gives the output that seems correct, but the label is still in the org
| State     Name         Type         Path
| ───────── ──────────── ──────────── ──────────────────────────────────────────────────────────
| Unchanged KeepMe1      CustomLabel  force-app/main/default/labels/CustomLabels.labels-meta.xml
| Unchanged KeepMe2      CustomLabel  force-app/main/default/labels/CustomLabels.labels-meta.xml
| Unchanged CustomLabels CustomLabels force-app/main/default/labels/CustomLabels.labels-meta.xml

If you restore the label locally and deploy again, it notices the change correctly and the re-added label is in the output.
📓  Not tested: multiple directory scenarios


Selector cannot find "div" elements

This problem suddenly occured and I have no idea why. When I try to find select a "div" element, I get the following error:

Function that specifies a selector can only return a DOM node, an array of nodes, NodeList, HTMLCollection, null or undefined. Use
ClientFunction to return other values.

It works for other elements though.
This works fine:
await t.click(Selector("span").withAttribute('id', 'foo'));
await t.click(Selector("p").withAttribute('id', 'foo'));
await t.click(Selector("button").withAttribute('id', 'foo'));
await t.click(Selector("input").withAttribute('id', 'foo'));

This throws an error:
await t.click(Selector("div").withAttribute('id', 'foo'));
I'm using testcafe 1.10.1
Update: Apparently testcafe still works on other sites. It is just that one website where I cannot access "div" elements. Any ideas why that could be?

This issue can occur if you pass a function with an incorrect return value as a Selector argument:
test('Return non-DOM node', async () => {
    await Selector(() => 'hey')();
});

However, the error should not occur if you use string as a parameter to specify your selector. Please check that you do not pass a function to your Selector object.
If your Selector is defined correctly and the issue still appears, please share the example (html page or public url to your site) and your full test code to demonstrate the issue.

This issue can occur if you pass a function with an incorrect return value as a Selector argument:
test('Return non-DOM node', async () => {
    await Selector(() => 'hey')();
});

However, the error should not occur if you use string as a parameter to specify your selector. Please check that you do not pass a function to your Selector object.
If your Selector is defined correctly and the issue still appears, please share the example (html page or public url to your site) and your full test code to demonstrate the issue.

I'm not passing a function, I'm using the basic annotation displayed above. Unluckily the page is still confidential so I cannot show it to you. Do you have any other guesses what the issue could be? It must have something to do with the code that is used on that specific project.

I'm not passing a function, I'm using the basic annotation displayed above. Unluckily the page is still confidential so I cannot show it to you. Do you have any other guesses what the issue could be? It must have something to do with the code that is used on that specific project.

@CassenH
I need to review a reproducible example to determine the cause of the issue. If you cannot share your example/project here, you can send it at<EMAIL_ADDRESS>It will help us research the issue quickly.
The basic usage in your case should not lead to such an error. Basic TestCafe Selectors use the document.querySelectorAll method internally, so you can try the following:

Execute the document.querySelectorAll('div') without TestCafe inside the Chrome DevTools Console. Please share the results with us.
Simplify your Selector in the test as follows: await t.click(Selector("div"). Does the error still occur? Does the error only occur when you add withAttribute call?

I want to add that if you are able to send your project via email, our policy prevents us from accessing internal resources without prior written approval from a site owner. If we need to access non-public parts of your website or pass through authorization pages, please ask the website owner to send us<EMAIL_ADDRESS>a written confirmation. It must permit DevExpress personnel to access the website and its internal resources remotely for research, testing, and debugging purposes.

@CassenH
I need to review a reproducible example to determine the cause of the issue. If you cannot share your example/project here, you can send it at<EMAIL_ADDRESS>It will help us research the issue quickly.
The basic usage in your case should not lead to such an error. Basic TestCafe Selectors use the document.querySelectorAll method internally, so you can try the following:

Execute the document.querySelectorAll('div') without TestCafe inside the Chrome DevTools Console. Please share the results with us.
Simplify your Selector in the test as follows: await t.click(Selector("div"). Does the error still occur? Does the error only occur when you add withAttribute call?

I want to add that if you are able to send your project via email, our policy prevents us from accessing internal resources without prior written approval from a site owner. If we need to access non-public parts of your website or pass through authorization pages, please ask the website owner to send us<EMAIL_ADDRESS>a written confirmation. It must permit DevExpress personnel to access the website and its internal resources remotely for research, testing, and debugging purposes.

I won't be able to send you any project content right now but I did follow your steps.

Using document.querySelectorAll('div') all 'div' elements are found as usual.
await t.click(Selector("div")) leads to the same error.

For some reason the testcafe selector is not able to work with "div" elements in this project. I guess I'll try to use a workaround for this project.

I won't be able to send you any project content right now but I did follow your steps.

Using document.querySelectorAll('div') all 'div' elements are found as usual.
await t.click(Selector("div")) leads to the same error.

For some reason the testcafe selector is not able to work with "div" elements in this project. I guess I'll try to use a workaround for this project.

@CassenH, It is impossible to determine the cause of the issue without an example. Could you create a synthetic one? It may be helpful if you share some details about the technologies you're using.

@CassenH, It is impossible to determine the cause of the issue without an example. Could you create a synthetic one? It may be helpful if you share some details about the technologies you're using.


Add chunking functionality to dom-if

In the same way that dom-repeat provides chunking up rendering work by setting initial-count, dom-if should provide a mechanism to chunk up work when rendering content. This is important when large chunks of dom are stamped via dom-if.

/sub


Adaptations to the recent updates in usdb

ad 3cf52fb : From my point of view the vscode folder was quite useful, as it introduced the chars-per-line-limit for python files, which is helpful for preventing linting errors.

ad 3cf52fb : From my point of view the vscode folder was quite useful, as it introduced the chars-per-line-limit for python files, which is helpful for preventing linting errors.

There is a [.vscode-dist](https://github.com/bohning/usdb_syncer/tree/main/.vscode-dist) folder that you can simply rename and use.

Open issues/topics:

USDB string translations
login via Firefox browser cookies not working (but working for Chrome, Edge, maybe others)
login via user/pass


special version for effective network

Thanks for contributing a pull request! Please make sure you have read the
contribution guidelines
before submitting.
Please be aware that we are a loose team of volunteers so patience is
necessary. Assistance handling other issues is very welcome. We value
all user contributions, no matter how minor they are. If we are slow to
review, either the pull request needs some benchmarking, tinkering,
convincing, etc. or more likely the reviewers are simply busy. In either
case, we ask for your understanding during the review process.
Again, thanks for contributing!
Reference issue
Example: Fixes #1234.
What does this implement/fix?
Explain your changes.
Additional information
Any additional information you think is important.

@qdong17 you are adding arrows so directions in the circle plots?

Yes, I made one version to plot directional connections. It works for my
research (as the attached figure). I am not sure if it is robust enough.
I thought I made a push request to my private repository. If you think it
is not necessary, please ignore it😂.
On Tue, Jun 23, 2020 at 1:15 AM Alexandre Gramfort<EMAIL_ADDRESS>wrote:

@qdong17 https://github.com/qdong17 you are adding arrows so directions
in the circle plots?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/7918#issuecomment-647986092,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK37UOKFMONRACZO5MX3QOLRYBQCDANCNFSM4OFGQGDQ
.

--
Best Regards,
Qunxi Dong
Geometry Systems Laboratory,
Brickyard Engineering,
699 S Mill Ave, Tempe, AZ, 85281.
Ph:<PHONE_NUMBER>

@qdong17 I don't see any "attached figure". I'm going to close because it sounds like you opened this PR accidentally (?) and the code violates our coding conventions in several ways.  If you think this is the wrong decision, please open a new PR that adheres to our conventions, and includes a clear description of what you're changing and why.


readme on github has dead links

the readme backend links are dead in this section  : https://github.com/containous/traefik#supported-backends
for example this link leads to a 404 : https://docs.traefik.io/configuration/backends/kubernetes

Closed by #5411.


Issue: Sign File Path longer than 260 characters

Problem with a longer path with 260 characters in SignBinary.
Suggested solution:

Ignore and warn the user.
Move the file to a temporary folder to Sign

Make sign to fail

https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry


Add new devices

Pull Request Test Coverage Report for Build 1324

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1321:
0.0%

Covered Lines:
996

Relevant Lines:
996

💛  - Coveralls


Use localized labels for skill variants in NPC Sheets

In GitLab by @dwim on Apr 29, 2022, 07:13
At this point of time, skill variants in NPC sheets are still displayed in English using the skill variant label. If we click on the variant, we can see in the chat that the label is already translated in the base system though.

If we try to translate the label (using Babele and targeting the Sheet item), the button to roll the skill variant does not work anymore unfortunately.
Suggestion : use the localized label (which already exists) in the NPC Sheet for Skill variants (as it's already done in the chat).

This has changed and is now doable, it can be close @cswendrowski