Wrap the text in the button of QnAmaker hero card

Is your feature request related to a problem? Please describe.
When active learning is triggered, the QnAmaker hero card can not wrap the text in the buttons with (...). This behavior don't allow us to completely see the question returned.
Describe the solution you'd like
We would like to able wrap the text in the button. We also want some options to control the behavior of this hero card. Actually all is done automatically.
Describe alternatives you've considered
Something which could be better is to have manual control of this bahavior.
Additional context

ActiveLearning functionality
QnAmaker hero card

Hi, is there a way to override the card sent by the QnA maker component? I don't think Hero cards supprot "text wrap" on buttons which mean that the workaround is to use an Adaptive Card instead - Here is an example to do that:
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.3",
"body": [
{
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": "Please select an option"
}
]
},
{
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": "Option 1 - Click on this text to submit your action - This text will be wrapped to the next line automatically ",
"selectAction": {
"type": "Action.Submit",
"data": {
"response": 1
}
}
}
]
},
{
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": "Option 2 - Click on this text to submit your action - This text will be wrapped to the next line automatically ",
"selectAction": {
"type": "Action.Submit",
"data": {
"response": 2
}
}
}
]
}
]
}

Hi @timoleo23 , thanks for your answer. But in composer, we have to use the type "imback" to continue de qna dialog (otherwise we have to change too much codes in module package), do you know how to add "imback" in adaptive card ? Because we have this error with your example + imback:

We would like to have another example of adaptive card with "imback", thanks for your help!
PS: With idea of this issue: https://github.com/microsoft/BotFramework-WebChat/issues/616 , we use actually  a carousel for those suggestion cards(because imback is automatically in hero card):

it's better than before but the UI is not friendly to the users, so we still want to find a solution with adaptive card.

Hi @tingting0118 , you can use this specific format that only works with Adaptive Cards for Microsoft Teams.
Here, you can control the message back displayed to the user and the value returned to the bot.
Documentation is here - https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-actions?tabs=json#adaptive-cards-with-messageback-action
{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "1.4",
    "body": [
        {
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "Please select an option"
                }
            ]
        },
        {
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "Option 1 - Click on this text to submit your action - This text will be wrapped to the next line automatically ",
                    "selectAction": {
                        "type": "Action.Submit",
                        "data": {
                            "response": 1
                        }
                    }
                }
            ]
        },
        {
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "Option 2 - Click on this text to submit your action - This text will be wrapped to the next line automatically ",
                    "selectAction": {
                        "type": "Action.Submit",
                        "title": "Click me for messageBack",
                        "data": {
                            "msteams": {
                                "type": "messageBack",
                                "displayText": "I clicked this button",
                                "text": "text to bots",
                                "value": { "response" : 2 }
                            }
                        }
                    }
                }
            ]
        }
    ]
}

Hi @timoleo23, thanks for this response.
But the problem there is Bot Composer Interface. Your suggestion requiert for us to update the internal code of Microsoft libraries (npm packages). We have implemented your suggestion,  but this type messageBack requiert a value or imBack type doesn't requiert a value. imBack type respond to this problem.  How can we update the library to implement your solution ?

Do you have a zip example of your projet that we can test with ? Please consider the fact that we work with Bot Framework Composer sofware (Ubuntu version) not with Bot services (with native typescript code).

Here is the Adaptive Card format with imBack
However, I don't know if we can supercharge the built-in QnA maker component in Bot Composer and I'd differ this question to the Microsoft support team.
{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "1.4",
    "body": [
        {
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "Please select an option"
                }
            ]
        },
        {
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "Option 1 - Click on this text to submit your action - This text will be wrapped to the next line automatically ",
                    "selectAction": {
                        "type": "Action.Submit",
                        "data": {
                            "response": 1
                        }
                    }
                }
            ]
        },
        {
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "Option 2 - Click on this text to submit your action - This text will be wrapped to the next line automatically ",
                    "selectAction": {
                        "type": "Action.Submit",
                        "title": "Click me for messageBack",
                        "data": {
                            "msteams": {
                                "type": "imBack",
                                "title": "More",
                                "value": "Show me more"
                            }
                        }
                    }
                }
            ]
        }
    ]
}

@timoleo23, thanks for your idea, that helps a lot!  Here is the codes for the developper who has the same question in Bot Composer :

open the script in path YourProject/node_modules/botbuilder-ai/lib/qnaCardBuilder.js"

Just modify the function getSuggestionsCard(suggestionsList, cardTitle, cardNoMatchText)
-> option 1.1 - Adaptive Card for Teams
/!\ That will not work in Composer when you test, but it will work with Teams

Here is the code to change:
`static getSuggestionsCard(suggestionsList, cardTitle, cardNoMatchText) {
if (!Array.isArray(suggestionsList)) {
throw new Error('Missing suggestionsList');
}
if (!cardTitle) {
throw new Error('Missing cardTitle');
}
if (!cardNoMatchText) {
throw new Error('Missing cardNoMatchText');
}
const cardls=[ {
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": cardTitle,
"weight": "Bolder"
}
]
}];
suggestionsList.forEach((suggestion) => {
cardls.push({
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": "👉 " + suggestion,
"selectAction": {
"type": "Action.Submit",
"title": suggestion,
"data": {
"msteams": {
"type": "imBack",
"title": suggestion,
"value": suggestion
}
}
}
}
         ]
     });
 });
 cardls.push({
     "type": "RichTextBlock",
     "inlines": [
         {
             "type": "TextRun",
             "text": "❗ " + cardNoMatchText,
             "selectAction": {
                 "type": "Action.Submit",
                 "title": cardNoMatchText,
                 "data":  {
                     "msteams": {
                         "type": "imBack",
                         "title": cardNoMatchText,
                         "value": cardNoMatchText
                     }
                 }
                 }
             }

     ]
 });

 const card=botbuilder_core_1.CardFactory.adaptiveCard({
       "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
       "type": "AdaptiveCard",
      "version": "1.2",
      "body": cardls});
 const message = botbuilder_core_1.MessageFactory.attachment(card);
return message;

}`
-> option 1.2 - Adaptive Card for WebChat

Here is the code to change:
`static getSuggestionsCard(suggestionsList, cardTitle, cardNoMatchText) {
if (!Array.isArray(suggestionsList)) {
throw new Error('Missing suggestionsList');
}
if (!cardTitle) {
throw new Error('Missing cardTitle');
}
if (!cardNoMatchText) {
throw new Error('Missing cardNoMatchText');
}
const cardls=[ {
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": cardTitle,
"weight": "Bolder"
}
]
}];
suggestionsList.forEach((suggestion) => {
cardls.push({
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": "👉 " + suggestion,
"selectAction": {
"type": "Action.Submit",
"title": suggestion,
"data": suggestion
}
}
]
});
});
cardls.push({
"type": "RichTextBlock",
"inlines": [
{
"type": "TextRun",
"text": "❗ " + cardNoMatchText,
"selectAction": {
"type": "Action.Submit",
"title": cardNoMatchText,
"data":  cardNoMatchText
}
}
     ]
 });

 const card=botbuilder_core_1.CardFactory.adaptiveCard({
       "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
       "type": "AdaptiveCard",
      "version": "1.2",
      "body": cardls});
 const message = botbuilder_core_1.MessageFactory.attachment(card);
return message;

}`
-> option 2 - Carousel

codes to modify:
const cardlist=[];      suggestionsList.forEach((suggestion) => {          cardlist.push(botbuilder_core_1.CardFactory.heroCard(undefined, suggestion,undefined, [{              value: suggestion,              type: 'imBack',              title: "Ask it",          }]));      });      cardlist.push(botbuilder_core_1.CardFactory.heroCard(undefined,undefined,[{          value: cardNoMatchText,          type: 'imBack',          title: cardNoMatchText,      }]));      const message = botbuilder_core_1.MessageFactory.carousel(cardlist,cardTitle)

Save the script and restart the bot in composer.

To display wrapped QnA prompts text in .Net Composer Project, can consider updating Language Generation (bot response) to display proper adaptive card for WebChat & Teams, and then modify the response action in QnA Maker dialog canvas.
I can make it work with below are detailed steps:

In Bot Composer, click Bot Responses
Click Common
Click the main dialog (suppose your QnA is in the dialog)
Click Show Code
Paste below three section LG code into the Editor

# getResponseWithPrompts(answer, prompts)
-```
{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.2",
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "TextBlock",
            "text": "${answer}",
            "wrap": true
        }
    ,
       ${getButtonList(prompts)}
    ]
}```

# getButtonList(prompts)
- ${join(foreach(prompts, u, if(turn.Activity.channelId == 'msteams' ,getButtonWrapTextItemTeams(u.displayText, u.id) ,getButtonWrapTextItemWeb(u.displayText, u.id))), ',')}

# getButtonWrapTextItemWeb(value, id)
-```
{
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "${value}",
                    "selectAction": {
                        "id": "${id}",
                        "type": "Action.Submit",
                        "data": "${value}"
                    }
                }
            ]
}```

# getButtonWrapTextItemTeams(value, id)
-```
{
            "type": "RichTextBlock",
            "inlines": [
                {
                    "type": "TextRun",
                    "text": "${value}",
                    "selectAction": {
                        "type": "Action.Submit",
                        "title": "Click me for messageBack",
                        "data": {
                            "msteams": {
                                "type": "imBack",
                                "title": "More",
                                "value": "${value}"
                            }
                        }
                    }
                }
            ]
        }```

A UI sample in my composer when I update the common LG (bot responses):

Click Create in the left navigation panel

Click QnA Intent Recognized trigger

In the Dialog canvas, select the **Prompt for Text" action (currently it uses SuggestedAction)

In the Properties pane, in the Bot Response part, click Show code

Replace the code with below content

[Activity

    Attachments = ${json(getResponseWithPrompts(@answer, turn.recognized.answers[0].context.prompts))}

]

The UI sample in my composer:

With above steps, you will see Composer and Teams can proper wrapped text with imback type
In Composer Web Chat

In Teams

When I work on this method, also referred one previous discussion https://github.com/microsoft/botbuilder-dotnet/issues/5149, after some modification, its main part can work well in current composer version QnA.


Add d.ts to publish build to use in TS projects

Also I have to add export { TypedData } to src/examples to prevent compile error. Should we move examples from src to separate dir?

@doochik Hi! I've refactored repository structure a bit:

main library, ydb-sdk package, and examples are compiled separately
examples require functions from ydb-sdk explicitly, as if they are not in the same repo
moved all ydb-sdk exports which are meant to be used by client code to index.ts - not an exhaustive list yet.

Please check, if requiring<EMAIL_ADDRESS>solves your issues (after you adjust your imports).

It works. Thanks!


Fix: email form sender

What does this PR do?
Fixes behaviour of SMTP sender in HTML contact form
Test Plan

[x] Manual on QA server

Related PRs and Issues
x
Have you read the Contributing Guidelines on issues?
Yes

Sending form as contact emailer is fairly common.
Maybe at least we should add reply to

During QA I noticed it always went to spam as unauthorized.
We should either use smtp username, or make sender name & email configurable.
Considering it should be simple starter template, I think it's fine to take smtp username as default, and they can change it in the code if needed.


Reminder - #6069 [Event Request] Table 38 "Purchase Header" – UpdatePurchAmountLines

Regarding #6069 from March 2020, there is nothing to see in Insider Build 17.0.14964.0-W1.
Status is "ships-in-future-update".
Will you still integrate it?

It was the result of incorrect closing of the request. The automatic answer has made you think it had been implemented.
Sorry for that.
You can see a comment there that suggests using the existing event:
"There is existing event with all required parameters OnBeforeUpdatePurchLineAmounts(Rec, xRec, CurrFieldNo, IsHandled); in this function."
Do you have a problem using it?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Since I need to set something in context, the publisher would be fine. With the Handled Pattern at the beginning I have to copy your code and then skip the standard and I have a place to check regularly for changes in the standard.


Secure contributions api

Currently, contributions API is open. Make it secure, only accessible by the superuser

@prakashchoudhary07 I want to work on this issue, and guessing it will be done something like this:
router.get("/:username", authorizeRoles([SUPERUSER]), contributions.getUserContributions)


Refactor for easier deploys of new versions. Adds jemalloc 5.0.1

This PR rewrites a large chunk of the build system and how the buildpack is installed and configured. The goals with this PR are to make using jemalloc easier for folks and to reduce the time and work required to release new versions.
The build system has been changed to build specific versions for multiple Heroku stacks against the official Heroku docker images. This means building a new version is a single command make VERSION=5.0.1 followed by uploading the build artifacts to a release on GitHub.
There has been some confusion lately around setting LD_PRELOAD especially since the revision changed with 5.0.0. This introduces JEMALLOC_ENABLED which can configure LD_PRELOAD automatically. This has the added benefit of being opt-in rather than opt-out. People have the option to either set this or use jemalloc.sh on a per-dyno basis.
Versions can now be switched by setting JEMALLOC_VERSION and pushing a new code change / recompiling the slug. The previous incarnation of versions required there to be a specific tag on GitHub with the version string. Now, anyone using the buildpack will always have the most up to date installer script and can switch between versions as long as there is a build available. This also means no longer needing to make code changes to release a new version of jemalloc.
There is some configuration that needs to happen if or when this PR is merged. It uses a different organization for releases where there is a tag based on name of the Heroku stack (heroku-16 and cedar-14). I'm not aware of a way to create a release on GitHub that only contains uploaded binaries (i.e. doesn't include any source) so I created a release-master that is an orphaned commit with no code on it. See the releases on my fork for a reference. I'm happy to configure the releases here to match it or be responsible for updating new builds on my fork going forward.
Finally, this work was sponsored by Dead Man's Snitch (a cron monitoring service), where we deployed 5.0.1 and have seen some really great results on both Puma and Sidekiq.
Fixes #2
Fixes #7
Fixes #13
Closes #11
Closes #14

Having support for heroku-16 would be great as we had to remove the buildpack when upgrading to heroku-16 recently.

@jonekdahl take a look at my fork which is the basis for this PR. It's usable today and support heroku-16

OK, I'm back in the open-source world.
@gaffneyc Anything that needs to be changed/updated here before I sit down and take a look?

@nateberkopec No, this is good to go. It depends on a specific setup for the releases tab before being merged (which I mention in the description).
I'm planning to keep my fork maintained, if you or mojodna don't have capacity then I'm happy to take on ownership of this.

@gaffneyc I don't have capacity, so thanks for volunteering! @nateberkopec has admin rights on this repo (pretty sure), so I'll defer to him on how to continue supporting this.

I think this should be merged - worked great for us! Thank you sir!

For anyone following this, jemalloc 5.1.0 was released yesterday. I've added it as well as builds for the upcoming Heroku-18 stack to my fork. It looks like 5.1.0 is a recommended upgrade by the jemalloc developers and we've just deployed it to our staging environment. Hopefully if all goes well I'll make 5.1.0 the default in a month or so.

LGTM, suggest adding @gaffneyc as maintainer and let him merge/release this.

@gaffneyc I've just invited you as a collaborator. Thanks!!!

Awesome, thanks. I've done a bit of work on my fork since this PR. I'll see about getting this merged, releases put together, and other changes added in here.

@gaffneyc @nateberkopec I can't tell what's blocking this PR from being merged. Does it need to be broken up into smaller PRs? I'm happy to help, just don't want to get started without checking in.

@bf4 This is blocked by me having time to do it. It's based off of my fork but it's both lagged behind master on my fork and was a modified rebase to keep the downloads coming from this repo. To get the PR up to date I would need to go through that process again from my master branch and add the releases. It's been hard to prioritize the time since my fork is working for what we need.
If you need what's in this PR today then I would say just use my fork. If you have time to help get it merged, going through the rebase process and opening a new PR would help a bunch.

@gaffneyc I took your master minus the sponsorship commit, since I figure that's a separate discussion, and merged this repos master into it. Was a clean merge. https://github.com/mojodna/heroku-buildpack-jemalloc/pull/19

how do i verify if jemalloc is running on heroku/dokku (im running RoR)

@wongy91

how do i verify if jemalloc is running on heroku/dokku (im running RoR)

That's really off topic.  I'm pretty sure that the right way to get help for this buildpack, assuming you're using it, is to 1) look for an existing issue 2) create a new one showing what you've tried, what you see, and what you expected

tldr; Migrate to gaffneyc/heroku-buildpack-jemalloc if you want newer versions of jemalloc. Or stick with this buildpack if things are stable for you.
Since opening this PR almost 11 months ago I haven't had much time to revisit it. Even with #19 there is still work to be done to finish the migration and an inherent risk to anyone depending on this buildpack that a major change like this could break their applications on the next deploy.
I'm committed to maintaining my fork since we depend on it for Dead Man's Snitch and several client projects at Collective Idea. With limited time the idea of maintaining two branches of the same code isn't very enticing and it's shown over the last year as I've been more responsive on my fork to issues.
Given the risk to people using this buildpack and the reality of the time I have available, I'm closing this PR (sorry :/) and recommending that people migrate to my fork as they're able to. This means stability for anyone who's happy with the current buildpack but it also means the migration will be opt-in, giving teams the ability to choose when and how they handle it.


Fix the logger

It looks like the original project has an issue with logger not being set correctly: https://github.com/snowdrop/java-buildpack-client/pull/51
But, even if they fix it, it is nice to be able to use the Slf4j one.

thanks @bsideup!


ci: ensure we build and test with Python 3.12

Inspecting this run: https://github.com/apache/arrow-adbc/actions/runs/6724294719
I see 3.12 wheels for linux, macos, and windows


Jumping between directories and aliases not working.

I love the work you guys have put into this terminal. Unfortunately I'm receiving some issues which are sort of a deal breaker when considering adoption of the application. I use zsh, not bash, so maybe this is an issue with zsh specifically?
First off, I commonly use a package called z, that allows me to jump between commonly used directories, located here:
https://github.com/rupa/z/
When I attempt to use it I get the following error:

Black Screen: command "_z" not found.

I have "z" aliased to "j", but I get the same exact error, no matter whether or not I use the alias.
I also use an alias "cd .." to simply ".."
When I type ".." and hit enter, I get the following:

zsh:1: permission denied: ..

Honestly these issues are causing me to not choose to explore the terminal further, and I really want to like this terminal. It's slick design really appeals to me and I love the attention to detail that you guys have put into it.

Some of those issue might be unfixable, as black-screen launches a new instance of bash for each command, so any changing of directories inside that instance of bash can't affect black-screen. The alias should work, though, I can look into that one.

From your comment, I immediately thought that the alias problem may have been because the alias wasn't included in ~/.bashrc, but I have the alias there as well, so I would think the alias should still work. If a fix can be done, that would be great! Maybe there is some sort of z alternative, or a plugin can be written by me; however, my knowledge in this area is rather limited, but it doesn't hurt to push oneself :) Thank you for your timely reply.

I haven't been able to reproduce the issue with the alias, I created a ".." alias and it worked fine for me.

It appears the issue I was having with the alias was because the alias was only located in my .bashrc and not my .zshrc.  I am using oh-my-zsh and I believe the alias is located there. I moved the alias to .zshrc and it works now.


Less ambiguous rule

Interpretations of "long" will vary - an unambiguous rule here is easier to apply.

:+1:


[communication] SMS - re-enable error code check in live test

This re-enables the error code check now that the error code is returning the correct value

type CertificatesGenerateVerificationCodeResponse = CertificateWithNonceDescription & { _response: Object }

I'm sorry, what is it you're asking for?

/azp run js - communication - ci


Kafka pod in pending state -  pod has unbound immediate PersistentVolumeClaims

Version of Helm and Kubernetes:
Client: &version.Version{SemVer:"v2.12.1", GitCommit:"02a47c7249b1fc6d8fd3b94e6b4babf9d818144e", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.1", GitCommit:"02a47c7249b1fc6d8fd3b94e6b4babf9d818144e", GitTreeState:"clean"}
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:39:04Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-10T23:28:14Z", GoVersion:"go1.11.4", Compiler:"gc", Platform:"linux/amd64"}
Which chart: Kafka
What happened: Followed the steps in the below link to install Kafka.
https://github.com/helm/charts/tree/master/incubator/kafka
my-kafka-0 pod is in pending state.
kubectl describe pod my-kafka-0 -n kafka
gives
Events:
Type     Reason            Age                From               Message

Warning  FailedScheduling  42m (x2 over 42m)  default-scheduler  pod has unbound immediate PersistentVolumeClaims
kubectl describe pvc datadir-my-kafka-0 -n kafka
Name:          datadir-my-kafka-0
Namespace:     kafka
StorageClass:
Status:        Pending
Volume:
Labels:        app=kafka
release=my-kafka
Annotations:
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Events:
Type       Reason         Age                      From                         Message

Normal     FailedBinding  2m45s (x743 over 4h52m)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set
What you expected to happen:
Expected the kafka pod to be in running state
How to reproduce it (as minimally and precisely as possible):
helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator
kubectl create ns kafka
helm install --name my-kafka --namespace kafka incubator/kafka
Anything else we need to know:

Hi all, make sure you have "storage" addon enabled. You should have a "hostpath" pod running on system


add EverypipeTimeoutSecond to ForEach-Object-Parallel

Summary of the new feature / enhancement
Context:
Q:how to limit time for everypipe on ForEach-Object-Parallel?
Apparently, -timeoutsecond can't do that.
It can be understood like this:
If there is no "-ThrottleLimit" parameter, -TimeoutSeconds is basically as expected.
But now there is the "-ThrottleLimit" parameter, which makes -TimeoutSeconds unable to limit the runtime of each parallel.
**“-ThrottleLimit” and “-timeoutsecond” cause subsequent pipes to time out without starting execution  **
So,we need -EverypipeTimeoutSecond.
time begin: from every parallel start
@PaulHigin

-timeoutsecond can't do that.

-timeoutsecond can limit total time for all pipes.
If there are many pipes and the execution time of each pipe is inconsistent, then limit total time does not look so good.
Both in the manual and in actual tests it is demonstrated that:
1..10 | ForEach-Object -ThrottleLimit 1 -TimeoutSeconds 2 -Parallel {
	Start-Sleep -Seconds 1
	$_
}

Proposed technical implementation details (optional)
No response

I don't quite get this. If you have 10 jobs taking 1 second each and -ThrottleLimit 4, so that each thread takes 2.5s on average, which do you want to limit? Single job or single thread?

I don't know if there is a one-to-one correspondence between each pipe and thread, so the name "thread" is not used here.
ForEach-Object-Parallel usage scenarios:
1Invoke-WebRequest You can't expect every pipe site to have the same return time.
When the number of pipes is large,
1 “total time” is not as easy to use as “average time”.
I don't know if there is a one-to-one correspondence between each pipe and thread, so the name "thread" is not used here.
ForEach-Object-Parallel usage scenarios:
1Invoke-WebRequest You can't expect every pipe site to have the same return time.
When the number of pipes is large,
1total time is not as easy to use as average time.
2 When a pipe hangs in front of the pipes, or the time is crowded for a long time, the subsequent pipes have not started, and “the total time” is up.

@dkaszews  I can see a wish for both.
100 items to process, average time 1 second, 10 threads. > 10 cores to run them on. Whole process should run in 10 seconds.
We might want to stop a single item that is still running after 10 seconds.
Or we might also want to stop the whole set if has not completed within 2 minutes
The second seems like a terminating error "We stopped without processing everything".
The first would be a way to fail sooner but re-using the thread to process another item (maybe with a warning) strikes me as wrong - my instinct says something should process everything or throw an error, it should not silently drop items. But  I can see  someone saying "My output tells me what has been processed, the commands I'm running in parallel can't change their timeouts so let me set one in the 'command-runner'"

think:
The farmer has 10 sheep (pipes) and a trough (ThrottleLimit).
The farmer wants to average the sheep's food, not that the first sheep eat too much and the remaining 9 sheep starve to death.

think: The farmer has 10 sheep (pipes) and a trough (ThrottleLimit). The farmer wants to average the sheep's food, not that the first sheep eat too much and the remaining 9 sheep starve to death.

The job is successfully done when no sheep are hungry. If the first sheep is removed from the trough while still hungry, do we say the job has failed ?
Ideally the scriptblock run for each item should limit how long it can run, and raise the right exception.
However Testing this I've found that throw (or  break  or exit) will not stop later items from running,  So removing the "hungry sheep" is no worse than what happens already.
For reasons I don't understand foreach-object doesn't allow -parallel and ErrorAction/WarningAction/InformationAction or pipelinevariable   -  but  setting $ErrorActionPreference  will cause it to stop for either  throw and Write-Error  - writing an error for "hungry sheep" would allow the other "sheep" to get their turns, but could also be transformed into a stop

The farmer said: "Don't worry about the sheep, the sick sheep will write-host or log themselves"   ;)

news：asp.net8 pr3 add timeout for per request
https://devblogs.microsoft.com/dotnet/asp-net-core-updates-in-dotnet-8-preview-3/
You can set request timeouts for individual endpoints, controllers, or dynamically per request.
To apply request timeouts, first add the request timeout services:
builder.Services.AddRequestTimeouts();
You can then apply request timeouts using middleware by calling :UseRequestTimeouts()

In my company we have hundreds of scripts that do parallel processing against many machines every day.
Prior to moving to PowerShell 7 we had to manage the jobs manual and it made the scripts about an order of magnitude more complicated than they should be.  For us, ForEach-Object is perfect and enjoy it very much.
Only caveat is randomly we will have sweeps that never return.  They go through their whole process using about 500 threads and each process finishes and shows their output, but the pipeline for ForEach-Object never returns.
I'm not clear on why this happens, but if we had a timeout per each process it would be fantastic.  It's hard to predict the full time a sweep for us will take (typically 10 to 60 minutes), however, it is very easy to determine the maximum amount a single process should take, normally no more than 10 to 30 seconds depending on the script.  Anything beyond that, it's stuck somehow and we need to stop it and free up the pool.
Some suggest ForEach-Object is not suited well for such long running processes, however I don't think that should be a scapegoat for not addressing the issues around ForEach-Object, which I think is one of the best features of PowerShell.  I understand if at a certain load it is not performant enough, however it shouldn't just crash or get stuck because you are using too many threads and memory.  If the demand is more than it can handle it should have a graceful way of reporting it.
If we can make it so each thread has a timeout limit and we can improve the termination of the processes running it would be a tremendous win for PowerShell.  I do realize processes getting stuck on IO that can't be terminated is a Windows thing, but I'm hoping the PowerShell team can help bridge the gap with the Windows team and help resolve this.  Otherwise who can?

Indeed, @kasini3000, I accidentally created a duplicate of your request in:

#20197

The initial post there contains a summary that may be helpful, as well as sample code that demonstrates the desired functionality.


Automatic-Scroll Margin Is Too Large

It's a good addition that the screen in iD scrolls automatically when one gets close to the edge. However, I feel the scroll margin is too large. When I get to about an inch from the edge it starts scrolling. That means that I have to avoid a large area of the screen when I'm editing to avoid scrolling that I don't want. The margin around the edge of the screen when scrolling starts should be much smaller, about 1/4 inch I feel.

I agree, thanks for the suggestion 👍


tsc instance reuse in composite project causes out of memory crash

TypeScript Version:  3.4.5
Search Terms: Composite, project references, out of memory
Expected behavior:
Building a large composite project where each component builds successfully should not run out of memory.
Actual behavior:
It looks like the same tsc instance is being used to compile each phase, and the memory grows until it trips the node memory limit. Would it instead make sense to fork off a new tsc process for each phase, or force some sort of garbage collection?

@RyanCavanaugh what info do you want me to provide?
I assume you have a composite project that you test with, you should be able to see that memory usage grows non-stop as each component project is compiled. The project I'm working on at the moment has nearly 50 components projects which each depend on a single large shared project. When the codebase has no compiler errors it will OOM the node process after 5 or 6 projects. I then restart with tsc -b --verbose --incremental again and this time it will build the project it crashed on, but then crash again 5 or 6 projects later. Rinse and repeat until all projects are compiled successfully.
With such a large project it's important that I can run the watch mode with --incremental, but if the node process is going to OOM every handful of file saves because of this issue then I'm not going to have a good experience.

@RyanCavanaugh @DanielRosenwasser We are seeing the OOM but with tsc --build --watch. Also on a really big project. Not right away but after a few recompiles it dies. We can repro on 3.5 and 3.4 but not on 3.3.

Some more information:

1mm lines of typescript across 100 referenced projects.
Deleting tsbuildinfo seems to prevent it the problem. This ties with doing a full --build (sans watch), deleting an output directory, and running again causing the issue.
Most devs see the failure after around 45 minutes of activity
There are some reports of zero activity (as in pull in master, run tsc --build --watch, go get coffee, return to OOM, no local changes)
We are on node 8.11.4
Most of our devs are configured to 4gb of old-space and we are going to start trying with 6gb to see if that changes anything

If there are theories about certain code patterns or usage patterns or whatever, we would be more happy to run some bespoke builds / nightlies to provide more information. I might be able to get a source code release to ya'll with an NDA.
I'll send you my cell phone number over twitter @DanielRosenwasser, in case @sheetalkamat wants to contact us directly.

Can you please verify if #33145 helps with this issue. Thanks.

It seems to do the job! Thanks!


Version 0.2.0 does not work with bg-space 0.3.0

I don't know exactly what is the minimum version of bg-space so I set it to above 0.5.0.
This is important for people who upgrade.

Thanks for catching this! Yes, it is actually 0.5.0


Sample frequency changed after time warp

Hey Alex,
I have a simple question when I read the paper Discovering Precise Temporal Patterns in Large Scale Neural Recordings through Robust and Interpretable Time Warping. Since linear warping functions will compress or stretch the signal, the time length of the neural activity will change. In discrete time series, the total data points remain the same. That means the sample frequency which is points divided by time length will changed too. Thus, the frequencies of neural activities will change. I wonder if this frequency change exists and how you deal with it. Thank you!
Best,
Dongming

Hi Dongming,
For shift-only warping, there is no change in the sampling frequency but you are correct that for linear / piecewise linear warping the effective sampling frequency changes when you apply the inverse warping functions to the data.
Note that we apply the inverse warping functions only for visualization purposes. If you read the methods section carefully, you'll see we optimize the model we always apply the warping to the "template" and never to the data itself. This is a subtle, but important point. It means that the sampling frequency of the data isn't messed with while we fit the model.
Let me know if that answers your question.

Hi Alex.
Thanks for your answer. It is very useful!
May I comprehend it as that you segment the data to many activities and warp the same activities to a "template", so you get templates for different activities. Although the warping function may change sampling frequencies, the "template" has fix time length and points thus sets the same sampling frequencies. If so. you do interpolation or remove some points while warping to the "template". Since "template" will not be inverse warpped to the data, the data sampling frequency remains unchanged.

Yes that's correct, the sampling frequency of the data is not changed for the purposes of model fitting. One could say that the "sampling frequency" of the template is changed via linear interpolation. Note that the template isn't really sampled at all -- it is a parameter of the model that is learned during optimization. So in a sense we can upsample/downsample the template without loss of precision because it is an idealized function.

Thank you very much, Alex!


Added console messages indicating to the user that npm installed successfully

Addresses #766

Thank you for this. I ended up using it, but I had to add it manually due to several other changes that moved code around. I added a mention/thank you in the release notes.


networkd: do not use DHCP for bridge devices

WIP: needs to be tested
How to use
Testing done

[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)

Would this change mean that #55 is not necessary and other network files excluding specific bridge devices could also be dropped?

Maybe yes but this is also something that could be reverted if it makes problems, I would keep the specific rules we have for the mean time.

Looks good. I suppose it will be release-notes-worthy change.

Right, added it in the coreos-overlay PR and can make it even more verbose if wanted


[backport v1.14] Bluetooth: controller: legacy: Backport v2.2 to v1.14-branch

Commits in this PR are manual cherry-pick of commits based on differences in ctrl.c file.
Fixes #25314

@cvinayak please move this out of draft in order to get it in a 1.14 dot release

@kruithofa  CC

Please remove the stale label, the changes in this PR is need to be in a 1.14 release branch.

This covers all security issues up to the removal of the legacy controller.

@thoh-ot @kruithofa could you review and approve please?

@thoh-ot @kruithofa could you review and approve please?

ping

@cvinayak will you please rebase?

Closing to re-open, so as to retrigger CI.

@MaureenHelm I get unrelated build failure, maybe the v1.14-branch is borken? need help from maintainers/implementors of the following:
qemu_x86_64               tests/crypto/rand32/crypto.rand32
qemu_x86_64               tests/drivers/ipm/peripheral.mailbox
qemu_x86_64               tests/kernel/sched/schedule_api/kernel.sched
qemu_x86_64               tests/kernel/timer/timer_api/kernel.timer
qemu_x86_64               tests/lib/crc/misc.crc

@MaureenHelm I get unrelated build failure, maybe the v1.14-branch is broken? need help from maintainers/implementors of the following:

@nashif can you take a look?


Crashing with MCA(Minecraft Comes Alive) 1.19.2

Hello! I am creating a rather large modpack and was getting a crash when traveling around the world. I narrowed it down to these mods:

I reported to MCA and they said it is not on their end what is happening according to them
"For context: the mca villager updates it's inventory, and it has an item in it with a custom update method. That update method (which is not part of vanilla or mca) assumed the holder is a PlayerEntity (or at least I think class_1657 is a PlayerEntity based on a quick google, and it kinda makes sense).
That means, you have to find the mod implementing that broken item. But it gets more complicated: Your crashlog luckily contains the inventory. And it only contains wheat and seeds. So that means someone tinkered with inbuild methods. Maybe some farming or food related mod?"
Here is the log and crashlog. I have also uploaded them to the MCA github. Thank you!
crash-2022-12-16_16.22.10-server.txt
latest.log

Received word from the mod author of MCA. He took a look at things and found the area causing issues. Are you able to fix?
"I took a look into the source and it is indeed this mixin here performing an unsafe cast: https://github.com/ZuzAser80/EldritchArcaneWorkings/blob/1.19/src/main/java/net/fabricmc/eaw/mixin/rune_support/ItemInject.java"


Patch iacm dev cert

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[x] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://672d2a639d11d3504314415c--harness-developer.netlify.app


incorporate cloud.gov IT troubleshooting guidance

Probably makes sense for the Equipment page, or being split out to a more general one.
https://docs.google.com/document/d/195V9ss3yRheU2j5x3_N5kCt4YNQCW7LsJd-ZJTAEQkI/edit

@eddietejeda this is more of cloud.gov docs team call on next steps.

The documentation has been archived and practice is in place for reaching out to #infrastructure so closing this issue.


json: add support for #[nserde(default = "fn")]

This is supported by serde and currently not possible without hacky wrapper structs in nanoserde. I did run cargo fmt on the code after so some of this is just changes by rustfmt. Test has been adjusted.

I am totally OK with this PR and am not sure about what I am asking about :)
But maybe we can skip the function and go for [nserde(default = "3.0")] right away? Is it really helpful to have a function for a default value?

Oh, I guess it would make us do something like #[nserde(default = "MyString".to_string())], and this doesn't look right

but maybe it is worth it to introduce a special case for a string?
If the field is a String and the default token is "whatever" - add .to_string()?

I am totally OK with this PR and am not sure about what I am asking about :)
But maybe we can skip the function and go for [nserde(default = "3.0")] right away? Is it really helpful to have a function for a default value?

I do like this and would implement it like this if you want me to! serde does not currently support this and I wanted to be somewhat compatible - but if you prefer this way I can change it. The only reason to actually use functions is defaults based on the enviroment, which might be wanted, so probably supporting both ways would be better?

oh, and defaults for structs would be a problem
but maybe we can leave current behavior as default_with(fn) for structs?
and maybe sometimes its ok to do something like #[nserde(default="Foo{bar: 5}")]?

I am totally OK with this PR and am not sure about what I am asking about :)
But maybe we can skip the function and go for [nserde(default = "3.0")] right away? Is it really helpful to have a function for a default value?

I do like this and would implement it like this if you want me to! serde does not currently support this and I wanted to be somewhat compatible - but if you prefer this way I can change it. The only reason to actually use functions is defaults based on the enviroment, which might be wanted, so probably supporting both ways would be better?

serde compatibility is not really a problem - nanoserde given up on this from the day 1 :D
I was thinking about default attribute before, sometimes I would really really love to have a struct that looks like this:
struct Foo {
  #[nserde(default = 5)]
  x: i32,
  #[nserde(default = 6)]
  y: i32
}

I think it is so much more readable than
struct Foo {
  #[nserde(default = "default_x")]
  x: i32,
  #[nserde(default = "default_y")]
  y: i32
}

But there are lots of problems with defaults in attribute, so I really am not sure. Maybe try it out and see how it will looks and how complicated implementation would be and make a decision later?

I got this working:
        #[nserde(default = "4.0")]
        b: f32,
        #[nserde(default_with = "some_fn")]
        c: f32,

however currently the attribute parsing relies on assuming that the value is quoted, which makes this very tough to change. I will push what I have right now and see what can be done about reworking the parser

Should be done. The following test works now:
    #[derive(DeJson)]
    struct Foo {
        x: i32,
    }
    impl Default for Foo {
        fn default() -> Foo {
            Foo { x: 23 }
        }
    }

    #[derive(DeJson)]
    struct Bar {
        x: i32,
    }

    #[derive(DeJson)]
    pub struct Test {
        a: i32,
        #[nserde(default)]
        foo: Foo,
        foo2: Foo,
        #[nserde(default = 4.0)]
        b: f32,
        #[nserde(default_with = "some_value")]
        c: f32,
        #[nserde(default = 1)]
        d: i32,
        #[nserde(default = "hello")]
        e: String,
        #[nserde(default = "Bar{x:3}")]
        f: Bar,
    }

    fn some_value() -> f32 {
        3.0
    }

    let json = r#"{
        "a": 1,
        "foo2": { "x": 3 }
    }"#;

    let test: Test = DeJson::deserialize_json(json).unwrap();
    assert_eq!(test.a, 1);
    assert_eq!(test.b, 4.0);
    assert_eq!(test.c, 3.0);
    assert_eq!(test.d, 1);
    assert_eq!(test.e, "hello");
    assert_eq!(test.f.x, 3);
    assert_eq!(test.foo.x, 23);
    assert_eq!(test.foo2.x, 3);

Should be done. The following test works now:
    #[derive(DeJson)]
    struct Foo {
        x: i32,
    }
    impl Default for Foo {
        fn default() -> Foo {
            Foo { x: 23 }
        }
    }

    #[derive(DeJson)]
    struct Bar {
        x: i32,
    }

    #[derive(DeJson)]
    pub struct Test {
        a: i32,
        #[nserde(default)]
        foo: Foo,
        foo2: Foo,
        #[nserde(default = 4.0)]
        b: f32,
        #[nserde(default_with = "some_value")]
        c: f32,
        #[nserde(default = 1)]
        d: i32,
        #[nserde(default = "hello")]
        e: String,
        #[nserde(default = "Bar{x:3}")]
        f: Bar,
    }

    fn some_value() -> f32 {
        3.0
    }

    let json = r#"{
        "a": 1,
        "foo2": { "x": 3 }
    }"#;

    let test: Test = DeJson::deserialize_json(json).unwrap();
    assert_eq!(test.a, 1);
    assert_eq!(test.b, 4.0);
    assert_eq!(test.c, 3.0);
    assert_eq!(test.d, 1);
    assert_eq!(test.e, "hello");
    assert_eq!(test.f.x, 3);
    assert_eq!(test.foo.x, 23);
    assert_eq!(test.foo2.x, 3);

Gotta admit though, the parser changes are a bit ugly

I love how Test struct looks, I believe it is worth a struggle with a parser. I looked over the implementation and the implementation LGTM!

Turns out the parser changes were not needed. I've added tests for Option<T> and implemented that. PR should be ready!

Great job, I love how nice the Test struct looks now.
The implementation looks very clean, it's amazing that you avoided parsers changes!

Published 0.1.27 to crates
Thanks again! :+1:


Apply key masking to flattened objects (schema shortcut flow)

There should be a way to check if key changes and append this info to schema.


LNK2019 error using VisualizationManager class on Windows

I have a class "QtDemo" that has a rviz_common::VisualizationManager* as a private member "manager_". I have a function QtDemo::InitRviz() that initializes the rviz members of the QtDemo class.

When I try to compile this function against either the pre-compiled foxy binaries, or an rviz2 source build, I get the following linker errors:

I am linking against

rviz_common::rviz_common
rviz_rendering::rviz_rendering
rviz_ogre_vendor::OgreMain
rviz_orgre_vendor::OgreOverlay
Qt5::Core
Qt5::Widgets

My full CMakeLists.txt for reference. For the source build I verified that visualization_manager.cpp was being compiled and that it had the same function definitions. It seems like this is the only file affected, but I can't figure out why. Has anyone seen this before, or have any idea what could be causing it? I am using ROS2 foxy on Windows 10, and doing the source build from the "foxy" development branch.

My best guess here is that VisualizationManager is missing RVIZ_COMMON_PUBLIC here.  It would be worthwhile to try adding it to the class and seeing if that makes a difference.  If you can't get that to work, you may instead have to add RVIZ_COMMON_PUBLIC to every method inside of the class.

My best guess here is that VisualizationManager is missing RVIZ_COMMON_PUBLIC here. It would be worthwhile to try adding it to the class and seeing if that makes a difference. If you can't get that to work, you may instead have to add RVIZ_COMMON_PUBLIC to every method inside of the class.

That was it, thank you. The VisualizationManager class just needed the RVIZ_COMMON_PUBLIC macro before it.

That was it, thank you. The VisualizationManager class just needed the RVIZ_COMMON_PUBLIC macro before it.

If you'd like to open a pull request to add that for future users, we'd be happy to review it.


fix(northlight-ui): fix weeks in date picker

This commit resolves the issue where the weeks in the date picker were incorrect. The previous solution did not follow the ISO week numbering rules, resulting in inaccurate week numbers. We are now taking into account the actual calendar days instead of simply counting and dividing by 7.
https://github.com/user-attachments/assets/ffeb469f-4498-4237-acdc-5ce02a2e6a19
closes: #DEV-17786

Something weird seems to be up with the weeknumbers from DEC 2026 - JAN 2027, it seems to miss week 53.


Race-sensitive language

Hi - this should have the bias free comms disclaimer on it until the product is updated.

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

ID: 17f663ca-635a-10ab-d78a-f60424a5484c
Version Independent ID: cd178cad-c4c4-16a0-ca02-ac336165cad7
Content: Configure the Azure MFA NPS extension - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-nps-extension-advanced.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@GossiTheDog Thank you for your feedback . Could you please point to the section which needs to be improved and we can engage the content authors for the same ?

@GossiTheDog Thank you providing explanations offline on the same. We have filed an internal request for authors to review the change and how best we can fix this in the documentation. We will close this issue now . Once the authors review the same and approve the change it will be merged within the next 24-48 hours.
Thank you.


Mldb 1581 bound parameters inception

New pipeline element to execute sub queries inside the pipeline executor instead of branching to the batch executor.

The taken and unique thing bothers me.  If we need to take twice, we should be calling restart().  I don't see how we should need it.
This code is complex.  It's worth adding quite a lot more comments and explanation to what you've added.

Thanks for the review, I'll document better. The 'unique' is for subqueries without dataset. Because there is no FromElement to limit the number of 'take', we need something to tell the pipeline to only take a single result. It seemed more efficient to tell the select to only take 1 result than to create a dummy FromElement (complete with Bound and Executor) down the pipeline which only purpose is to limit to 1 take.

I would create a one-row dataset and use that for the "from" for a from-less query.  To me it's much clearer as to what the semantics of a no-table query are.

@jeremybarnes ok, done!


Unable to run new versions ( > 0.23.0) on Vagrant

Hi,
I have been using Rancher 0.23.0 on Vagrant to play around with it without any issues so far. Today I wanted to try out the new version and haven't been able to get the agent up on Vagrant. I have tried 0.26.0-RC1 as well as 0.25.0. The agent installation seems to go into a loop. I have pasted it below. My setup is one Vagrant VM running the main rancher server (<IP_ADDRESS>) and another Vagrant VM (<IP_ADDRESS>) running the agent. Both VMs can ping each other without any trouble.  I just ran them using the docker run commands.

@willowandcreek did you try and upgrade from v0.23.0 or did you do a full teardown/rebuild? The upgrades from pre-beta releases  <v0.24.0 are not supported. Also, do you know which version of CoreOS is running? Docker Version?

It was a full tear down. Docker version is 1.7.0, build 0baf609. I am not using CoreOS. I am using Vagrant with a base image of Ubuntu like I did for 0.23.0.
Here is my Vagrant file:
$mgmtScript = <<SCRIPT
#!/usr/bin/env bash

wget -qO- https://get.docker.com/ | sh
docker run -d --restart=always -p 8080:8080 rancher/server:v0.25.0
SCRIPT

$nodeScript = <<SCRIPT
#!/usr/bin/env bash

wget -qO- https://get.docker.com/ | sh

#Replace below with tokens from mgmt node after setup
docker run -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.7.9 http://<IP_ADDRESS>:8080/v1/scripts/5E7CE889490B9FD336C9:1436169600000:ETz3yCx0mR701E23r6K7NYwGdg
SCRIPT

Vagrant.configure(2) do |config|
  config.vm.define "mgmt" do |node|
    node.vm.hostname = "mgmt.vagrant.dev"
    node.vm.box = "ubuntu-trusty-64bit"
    node.vm.network "private_network", ip: "<IP_ADDRESS>"
    node.vm.provision "shell", inline: $mgmtScript
  end

  #<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>
  (1..3).each do |i|
    config.vm.define "box#{i}" do |box|
      box.vm.hostname = "box#{i}.vagrant.dev"
      box.vm.box = "ubuntu-trusty-64bit"
      box.vm.network "private_network", ip: "<IP_ADDRESS>#{i}"
      box.vm.provision "shell", inline: $nodeScript
    end
  end
end


Zero valued time.Time being omitted

Sorry if I'm wrong about this, but it looks like time.Time values that are "zero" values are being omitted from marshaling. I question if this should this be the desired behavior. Zero values are still useful, especially if you're trying to avoid passing around nils/nulls. Let me know what you think, and thank you for maintaining this.
https://github.com/google/jsonapi/blob/d0428f63eb511f08685bda2d0a6af1d7532fb1c0/response.go#L306-L308

Hey, I think the omitempty configuration should help you in the model description.

The same problem.
type Request struct {     BlockedUntil time.Time ``jsonapi:"attr,blocked_until,iso8601"`` }
If BlockedUntil had zero value, after marshaling field BlockedUntil  is omit. Expected behavior: BlockedUntil will remain after marshaling

I think we've all moved on with life.


Please make ipfs.files API more ergonomic

I find ipfs.files API somewhat painful to use here is why:

There are multiple version of cat (catReadableStream, catPullStream) which is fine, except error handling is painful. If ipfs.files.catReadableStream(path) returns a stream, but there is no simple way to know if path is incorrect (for example I was using following /QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme which was failing silently  before end up realizing that / in front was causing an issue). One could listen to error events on a stream but that's not ideal in pipelines where you'd prefer actual stream errors to be passe through.

As things stand detection of the content type is pretty complicated as it involves pass through stream etc...

I would propose alternative API to make dealing with this more convenient. I'll write up interface in flow / ts just for clarity. Also even though both defnine Promise<a> I'll use Promise<x, a> where x represents error type.
interface files {
   // ...
  readEntry(EntryPath):Promise<EntryReadError, Entry>
  readFile(EntryPath):Promise<FileReadError, FileEntry>
  readDirectory(EntryPath):Promise<DirectoryReadError, DirectoryEntry>
}

// including the ipfs handler, a cid and a path to traverse to, ie:
//  '/ipfs/QmXEmhrMpbVvTh61FNAxP9nU7ygVtyvZA8HZDUaqQCAb66'
//  '/ipfs/QmXEmhrMpbVvTh61FNAxP9nU7ygVtyvZA8HZDUaqQCAb66/a.txt'
//  'QmXEmhrMpbVvTh61FNAxP9nU7ygVtyvZA8HZDUaqQCAb66/a.txt'
type IPFSPath = string

type EntryPath =
  | CID
  | Buffer // the raw Buffer of the cid
  | string // the base58 encoded version of the cid
  | IPFSPath

type Entry =
  | FileEntry
  | DirectoryEntry

type EntryReadError =
   | InvalidCIDBuffer // incorrectly encoded cid
   | InvalidCIDString // incorecctly encocec cid string
   | EntryNotFound // incorrect / unavailable path

type FileReadError =
  | EntryReadError
  | NotAFileEntry

type DirectoryReadError =
  | EntryReadError
  | NotADirectoryEntry

interface File {
  entryType: "file",
  size: number,
  path: IPFSPath,
  cid(): CID,
  contentType():Promise<IOError, string>, // fetches just enough to detect content type
  buffer():Promise<IOErrror, Buffer>, // Equivalent of cat
  string():Promise<IOError, string>, // await this.toBuffer().toString()
  readableStream():ReadableStream<IOError, Buffer>,
  pullStream():PullStream<IOError, Buffer>
}

interface DirectoryEntry {
  entryType: "directory",
  cid(): CID,
  path: IPFSPath,
  size: number, // number of entries it contains
  array():Promise<IOError, Entry[]>,
  readableStream():ReadableStream<IOError, Entry>,
  pullStream():PullStream<IOError, Entry>
}

Also are there any plans on support standard streams https://streams.spec.whatwg.org/ ? They support asyc iteration https://streams.spec.whatwg.org/ allowing one even nicer way to do IO:
const entry = ipfs.fils.readFile(path)
for await (const chunk of entry.content()) {
  console.log(chunk);
}

FYSA (quoting https://github.com/ipfs/interface-ipfs-core/issues/284#issuecomment-440569314), we are upgrading the Files API in 3 milestones:

M1 - Move add, get, cat to top level and distinguish them from the Files(MFS) commands.
M2 - Move to async await everywhere (this is half of what ipfsx is about)
M3 - Revisit how the all the commands that touch files are designed. This milestone is original intention of this issue and the other half of what ipfsx is about.


A suggestion about releasing multiple-versions.

WinRAR has a feature called "Save identical files as references". It means that if two or more versions have a lot of identical files, you can just pack them in a same .rar package, and will not make the file size increase rapidly.

why am i suggest this? because i wanted to try both of <IP_ADDRESS> beta2 versions, sadly i had to download excess contents.

200 Megs is tiny, There are a few files that are different even if you don't notice them.


Add query condition for "Project: Last Logged Event"

Is it possible to add a query condition for "Project: Last Logged Event"?
Example query:
SELECT project_id, project_name, last_logged_event FROM redcap_projects;

It would be helpful to notify users of inactive projects.

@shichikoromo Thanks for the feedback. I will try to get that added soon.

@shichikoromo a new version (1.5.9) was just added to the external module repository that has the new "Project Last Logged Event" query condition variable.


Can I download only srt file from torrent?

https://webtor.io/#/show?file=All.The.Old.Knives.2022.720p.WEBRip.x264.AAC-[YTS.MX].mp4&pwd=%2FAll The Old Knives (2022) [720p] [WEBRip] [YTS.MX]&magnet=magnet%3A%3Fxt%3Durn%3Abtih%3A98e61c4f4e54027cbf76dca09a3e1f5fc40e3d12%26dn%3DAll%2BThe%2BOld%2BKnives%2B(2022)%2B%255B720p%255D%2B%255BWEBRip%255D%2B%255BYTS.MX%255D
Is it possible to get direct link to first .srt file that is in main directory with SDK?

@kovacevica00 Hi! Can you provide full use case? What functionality do you want?

I am going to implement simple API that may cover all your needs. It was already discussed here #65.

believe it or not, I am about to talk about the same thing.
@vintikzzz  Is the API will post the content to our Translation SDK URL and get the translated Content?

You would have to download file from Webtor API, then push it to Translation API and finally get translated content.
Just to avoid possible future confusion, API will be available for:

Patreon backers (starting from Silver tier).
RapidApi subscribers.
For self-hosted Webtor instances.


Add note on diff's n differing from pandas

This surprised me so I thought worth calling out. I need to add to Dataset's docstring too.

I created this branch online, and seem to have created the branch on the xarray repo. Closing and will reopen on my own fork.


Websocket client and asyncio.async

Hi,
I was reading the doc about websocket client :
session = aiohttp.ClientSession()
async with session.ws_connect('http://example.org/websocket') as ws:

    async for msg in ws:
        if msg.tp == aiohttp.MsgType.text:
            if msg.data == 'close cmd':
                await ws.close()
                break
            else:
                ws.send_str(msg.data + '/answer')
        elif msg.tp == aiohttp.MsgType.closed:
            break
        elif msg.tp == aiohttp.MsgType.error:
            break

But it seems that async is deprecated now. How to make this code working with python 3.5 ?

The snippet is 100% correct and works on Python 3.5+
asyncio.async coroutine is deprecated for sake of async def, async with and async for keywords.


Version?

What version of unreal engine is this for? And is it in a basic working state? This is the only ue4 GOAP plugin I have found and I would like to implement it in my project.

It's currently on 4.18. It is working in the sense that I've had it running with 3 or 4 actions. I wouldn't advise trying to use it unless you're comfortable working in code and can debug/fix problems yourself.


[ja] Translate content/en/docs/tasks/administer-cluster/cluster-upgrade.md into Japanese

This is a Feature Request
What would you like to be added
Translate content/en/docs/tasks/administer-cluster/cluster-upgrade.md into Japanese
Why is this needed
There is no Japanese translation for this page
Comments

File to translate:

https://github.com/kubernetes/website/blob/main/content/en/docs/tasks/administer-cluster/cluster-upgrade.md

Original:

https://kubernetes.io/docs/tasks/administer-cluster/cluster-upgrade/

日本語に翻訳する際は、以下のドキュメントを参考にしてください。

Japanese Localization document: https://kubernetes.io/ja/docs/contribute/localization/

/area localization
/language ja
/help
/triage accepted

/assign

/unassign @Kei-Ta

/assign


James Todd add html file with images

Thanks. I will get those updated tonight and pushed up
On Thu, Sep 3, 2020, 15:14 Raven<EMAIL_ADDRESS>wrote:

@ravens-eye requested changes on this pull request.
Just issues with your css and image paths now
In client/assets/css/james.css
https://github.com/Raven-s-Eye-Solutions/class-introduction-template/pull/8#discussion_r483197128
:

@@ -0,0 +1,26 @@
+h2 {

font-family: 'Oswald', sans-serif;
font-size: 3rem;
padding-top: 3rem;
padding-bottom: 3rem;
+}

+body {

color: cornsilk;
text-align: left;
background: url(../images/Edited\ beach\ milky\ way.jpg) no-repeat center center fixed;

Still some issues with your pathing of images. None of the image paths are
relative to the frontend files, so you won't have the ../ anymore. Just /
In client/index.html
https://github.com/Raven-s-Eye-Solutions/class-introduction-template/pull/8#discussion_r483197410
:

@@ -30,6 +30,12 @@ Meet your instructors and teammates
Jon Jackson - Support Manager

Capital 'H' Headshot.jpg
In client/james.html
https://github.com/Raven-s-Eye-Solutions/class-introduction-template/pull/8#discussion_r483198099
:

Im currently an automotive technician. During my time in the Tech talent south code bootcamp, I was

       introduced to code and started from the ground up with HTML. My course evolved from html with css into Ruby on rails. The bootcamp left me

       with hundreds of questions and other then the projects performed in class, no real direction was decided. I have

       since been able to mentor with Karsten and add React to my arsenal of code. I am currently working on building a PC to handle android app building while teaching myself Java.

       In my spare time I rock climb, weld, and photography.

James Todd Copyright 2020


Need provision to pass Body as parameter while presigning requests using sign_v4_query_params

Team,
Java SDK has two classes for signing requests  with AWS4 signing protocol
AWS4UnsignedPayloadSigner.java - https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/java/com/amazonaws/auth/AWS4UnsignedPayloadSigner.java
AWS4Signer.java - https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/java/com/amazonaws/auth/AWS4Signer.java
AWS4UnsignedPayloadSigner adds "UNSIGNED-PAYLOAD" as body if the request is sent over HTTPS whereas AWS4Signer doesn't add "UNSIGNED-PAYLOAD" as request body for pre-signing
Background:
I'm trying to authenticate with AWS MSK via AWS_MSK_IAM SASL mechanism in Elixir and it needs me to presign the request without adding "UNSIGNED-PAYLOAD" as part of its canonical request. I see that aws_signature adds "UNSIGNED-PAYLOAD" as part of pre-signing here
https://github.com/aws-beam/aws_signature/blob/9dff1ba66fc9a9e7243fec8f301120b47719df26/src/aws_signature.erl#L170.
This causes issues when I try to pre-sign requests to authenticate with services like Amazon MSK via IAM. Rather than always sending "UNSIGNED-PAYLOAD" as body, is it possible to have a provision to send "UNSIGNED-PAYLOAD" only when Body parameter is nil, otherwise use what is sent as Body? This needs modifying the api's definition to add Body as an additional parameter. Let me know if there are better alternatives to tackle this.
https://hexdocs.pm/aws_signature/aws_signature.html#sign_v4_query_params/8

Hey @aravindanck, the sign_v4_query_params function is used when sending the signature over query params, in that case the payload is always UNSIGNED-PAYLOAD as in the specification. So you most likely want to use the sign_v4 function and send the signature in the headers. sign_v4 calculates the payload hash. Also, this corresponds to the Java code you referenced, where the sign method modifies the request headers. Let me know if that helps :)

@aravindanck thanks for the details, I see it now. The code you referenced in 3. uses presignRequest, which corresponds to sign_v4_query_params. Also, the spec I mentioned is a part of S3 docs, so it adds this assumption about unsigned payload, which may not be the case for other services. The Ruby implementation supports body and body_digest options to control this, I think we need to mirror that, I'll send a PR.

Great, thanks @jonatanklosko

@aravindanck I've just released 0.3.0 and you should be good to go, if you run into any issues let us know :)

Works as expected for me. Thanks @jonatanklosko

Hi @jonatanklosko,
I've had this code with version-0.2.0:
    opts = [ttl: 86_400]
    signed_url =
      :aws_signature.sign_v4_query_params(
        access_key,
        secret_key,
        region,
        service,
        datetime,
        method,
        url,
        opts
      )

This breaks for pre-signed urls.  Do we need to change something to be compatible with 0.3.0 ?
The error we get is:
<Error>

SignatureDoesNotMatch
<Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message>
<AWSAccessKeyId>AKIA4KVFMDO6VN564QOG</AWSAccessKeyId>
<StringToSign>AWS4-HMAC-SHA256 20220530T070125Z 20220530/us-east-2/s3/aws4_request<PHONE_NUMBER>e19ccaa5ef4f610fb6b0355db55c1d45fcb975a1d52511f79395fb</StringToSign>
<SignatureProvided>2a032f4c484eafa403388764758a6d72fa6421564444fbf58d384c9e5a1d8154</SignatureProvided>
<StringToSignBytes>41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 0a 32 30 32 32 30 35 33 30 54 30 37 30 31 32 35 5a 0a 32 30 32 32 30 35 33 30 2f 75 73 2d 65 61 73 74 2d 32 2f 73 33 2f 61 77 73 34 5f 72 65 71 75 65 73 74 0a 30 39 35 36 39 39 30 37 37 30 65 31 39 63 63 61 61 35 65 66 34 66 36 31 30 66 62 36 62 30 33 35 35 64 62 35 35 63 31 64 34 35 66 63 62 39 37 35 61 31 64 35 32 35 31 31 66 37 39 33 39 35 66 62</StringToSignBytes>
<CanonicalRequest>GET /public/9660a06a-59d8-482d-821c-1dd9718ec6d8/534e8b21-7188-49ed-b020-65e137091bbb.jpeg X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA4KVFMDO6VN564QOG%2F20220530%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20220530T070125Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host host:cookstro.s3.us-east-2.amazonaws.com host UNSIGNED-PAYLOAD</CanonicalRequest>
<CanonicalRequestBytes>47 45 54 0a 2f 70 75 62 6c 69 63 2f 39 36 36 30 61 30 36 61 2d 35 39 64 38 2d 34 38 32 64 2d 38 32 31 63 2d 31 64 64 39 37 31 38 65 63 36 64 38 2f 35 33 34 65 38 62 32 31 2d 37 31 38 38 2d 34 39 65 64 2d 62 30 32 30 2d 36 35 65 31 33 37 30 39 31 62 62 62 2e 6a 70 65 67 0a 58 2d 41 6d 7a 2d 41 6c 67 6f 72 69 74 68 6d 3d 41 57 53 34 2d 48 4d 41 43 2d 53 48 41 32 35 36 26 58 2d 41 6d 7a 2d 43 72 65 64 65 6e 74 69 61 6c 3d 41 4b 49 41 34 4b 56 46 4d 44 4f 36 56 4e 35 36 34 51 4f 47 25 32 46 32 30 32 32 30 35 33 30 25 32 46 75 73 2d 65 61 73 74 2d 32 25 32 46 73 33 25 32 46 61 77 73 34 5f 72 65 71 75 65 73 74 26 58 2d 41 6d 7a 2d 44 61 74 65 3d 32 30 32 32 30 35 33 30 54 30 37 30 31 32 35 5a 26 58 2d 41 6d 7a 2d 45 78 70 69 72 65 73 3d 38 36 34 30 30 26 58 2d 41 6d 7a 2d 53 69 67 6e 65 64 48 65 61 64 65 72 73 3d 68 6f 73 74 0a 68 6f 73 74 3a 63 6f 6f 6b 73 74 72 6f 2e 73 33 2e 75 73 2d 65 61 73 74 2d 32 2e 61 6d 61 7a 6f 6e 61 77 73 2e 63 6f 6d 0a 0a 68 6f 73 74 0a 55 4e 53 49 47 4e 45 44 2d 50 41 59 4c 4f 41 44</CanonicalRequestBytes>
<RequestId>W8BFFQJPX6KFA8VQ</RequestId>
<HostId>ic//EUI+wtcZaWw5LP99znf08uuicOBqsjvbLRb5jvIAyWRqXLq+Ysl2yRcdW1lY/I/ZXa6y9JU=</HostId>
</Error>

Hey @collegeimprovements, you most likely need body_digest: "UNSIGNED-PAYLOAD", please see v0.3.0 release notes :)

That was it. Thanks a lot @jonatanklosko :)


Puzzle Piece U+1f9e9

This glyph does not appear to be in noto-emoji yet. It's a puzzle piece glyph.
When it is added, I would like to specifically request that it NOT be blue. Here's why.
A blue puzzle piece is the icon of a group called "Autism Speaks" - they chose blue because at one point, it was thought that autism only affected males.
The organization does not have any autistic people on its board, and is widely disliked by people in the autistic community because they present autism as a tragedy and promote many "treatments" that are very harmful to those of us who are autistic, often likely causing PTSD.

Other videos present autism as something from a horror film that destroys families.
People who are not autistic and do not know the trauma that organization has caused and promotes will often donate to that organization, not realizing that almost none of the money actually goes to anything related to autism - and are likely to use the puzzle piece emoji as a way of suggesting that they "support autism" when in reality they are triggering actual autistic people who have had horrible experiences as a direct result of the "Autism Speaks" organization.
I like puzzles and obviously do not have a problem with a puzzle piece emoji, but please PLEASE do not make it blue. Red or Rainbow or Patterned would be better. Actual puzzle pieces rarely are a single color anyway.
Otherwise many autistic people will be forced to figure out how to use an alternate emoji font to avoid the trigger.
Please see https://learnfromautistics.com/the-problem-with-the-autism-puzzle-piece/
Thank you for your time.

If by chance you did want an emoji we would enjoy - u1f9e0 is actually close, a rainbow version of that is what we already often use to express neuro-diversity. But that would have to be standardized unless there's already a unicode modifier to rainbow something.

Our proposed jigsaw puzzle piece design is mixed blue and green and has two pieces at angles to each other.  It seems sufficiently different from the logo of the group you mention.  People might make metaphoric use of this emoji for whatever they want, though.  The page you link to objects to the use of any puzzle piece, however colored, to represent autism, so there's still potential for people to dislike it on these grounds.  Hopefully the fact that our image uses two jigsaw pieces will help avoid this.
There's no standard sequence for a rainbow brain image, but you can propose such a sequence to Unicode.  See https://unicode.org/emoji/proposals.html

Thank you.


add other contributor

@all-contributors add @LBF38 for code and documentation as well

@all-contributors


[AFTER Section][Lighter Blue Background Needs to be a Bit Higher for Every Page]

AFTER Section
Lighter Blue Background Needs to be a Bit Higher for Every Page
What We Should Do to Fix it

[ ] Make it higher
[ ] For like all the scenes in this section

yeh


Tuning/stop search %

10+0.1 - pretty much inconclusive (run was aborted)
Rank Name                          Elo     +/-   Games   Score    Draw
   0 Lynx 971 - 0.7                 30      25     572   54.4%   20.6%
   1 Lynx 971 - 0.6                 50      26     576   57.2%   16.1%
   2 Lynx 971 - 0.4                 28      26     576   54.0%   16.0%
   3 Lynx 971 - 0.3                 42      26     576   56.1%   17.7%
   4 Rustic 2                       97      37     288   63.5%   18.8%
   5 Walleye 1.6.0                  64      38     287   59.1%   14.3%
   6 Celestial 1.0                  30      37     288   54.3%   17.0%
   7 TSCP 1.8.1                     15      37     286   52.1%   15.4%
   8 Rustic 1.1                     -5      36     288   49.3%   18.1%
   9 Vapor 0.01-r12                -33      32     287   45.3%   36.2%
  10 Lynx 0.14.1                  -201      42     288   24.0%   15.3%
  11 Piranha 0.5                  -398      65     288    9.2%    5.9%

60+1 - pretty much inconclusive as well
Rank Name                          Elo     +/-   Games   Score    Draw
   0 Lynx 971 - 0.7                 57      23     736   58.1%   19.7%
   1 Lynx 971 - 0.6                 56      22     736   58.0%   21.7%
   2 Lynx 971 - 0.4                 66      22     746   59.4%   22.5%
   3 Lynx 971 - 0.3                 66      22     752   59.4%   20.5%
   4 Rustic 2                       85      32     372   62.0%   20.2%
   5 Walleye 1.6.0                  11      32     371   51.6%   18.6%
   6 Lynx 0.14.1                   -17      31     372   47.6%   24.7%
   7 Celestial 1.0                 -62      32     370   41.2%   18.1%
   8 TSCP 1.8.1                    -64      32     370   40.9%   22.4%
   9 Vapor 0.01-r12               -100      29     371   36.0%   36.9%
  10 Rustic 1.1                   -103      33     372   35.6%   19.6%
  11 Piranha 0.5                  -299      46     372   15.2%    8.3%

10+0.1
sprt failed for 0.6 vs 0.4

60+1 (wip)
Score of Lynx 971 - 0.6 vs Lynx 971 - 0.4: 358 - 382 - 258  [0.488] 998
...      Lynx 971 - 0.6 playing White: 194 - 181 - 125  [0.513] 500
...      Lynx 971 - 0.6 playing Black: 164 - 201 - 133  [0.463] 498
...      White vs Black: 395 - 345 - 258  [0.525] 998
Elo difference: -8.4 +/- 18.6, LOS: 18.9 %, DrawRatio: 25.9 %
SPRT: llr -1.49 (-50.6%), lbound -2.94, ubound 2.94

120+1 vs engines mixed (wip)
Rank Name                          Elo     +/-   Games   Score    Draw
   0 Lynx 993 - 0.7                -11      24     612   48.4%   22.9%
   1 Lynx 992 - 0.6                -29      25     618   45.9%   19.9%
   2 Lynx 991 - 0.5                 -9      24     630   48.7%   24.0%
   3 Lynx 990 - 0.4                 17      24     630   52.5%   22.4%
   4 Lynx 989 - 0.3                 -2      24     630   49.8%   21.7%
   5 Cadabra 2.0.0                 224      38     348   78.4%   19.0%
   6 Zeta Dva 0310                 136      33     348   68.7%   25.3%
   7 AdaChess 3.6                  103      33     348   64.4%   24.1%
   8 BBC 1.0                        85      31     346   62.0%   30.3%
   9 Rustic 2                       38      33     346   55.5%   19.7%
  10 TSCP 1.8.1                   -107      33     346   35.1%   22.3%
  11 Celestial 1.0                -119      35     346   33.5%   17.3%
  12 Rustic 1.1                   -144      36     346   30.3%   17.3%
  13 Lynx 0.14.1                  -144      34     346   30.3%   24.3%

10+0.1 self gauntlet - gives higher and lower values to the extremes
Rank Name                          Elo     +/-   Games   Score    Draw
   0 Lynx 992 - 0.6                  5      27     500   50.7%   21.8%
   1 Lynx 991 - 0.5                 13      27     500   51.8%   19.2%
   2 Lynx 990 - 0.4                  4      27     500   50.6%   22.0%
   3 Lynx 989 - 0.3                 15      27     500   52.2%   23.6%
   4 Lynx 993 - 0.7                 -9      13    2000   48.7%   21.6%

10+0.1 vs engines mixed (wip)
Rank Name                          Elo     +/-   Games   Score    Draw
   0 Lynx 993 - 0.7                -35       9    4500   44.9%   15.4%
   1 Lynx 992 - 0.6                -20       9    4500   47.1%   15.6%
   2 Lynx 991 - 0.5                -25       9    4500   46.4%   15.5%
   3 Lynx 990 - 0.4                -19       9    4500   47.2%   15.4%
   4 Lynx 989 - 0.3                -32       9    4500   45.4%   14.1%
   5 Cadabra 2.0.0                 342      18    2500   87.7%   10.2%
   6 Zeta Dva 0310                 124      13    2500   67.2%   14.6%
   7 AdaChess 3.6                  105      13    2500   64.7%   15.7%
   8 BBC 1.0                        85      13    2500   62.1%   18.6%
   9 Rustic 2                       64      13    2500   59.1%   15.5%
  10 Celestial 1.0                 -43      13    2500   43.9%   15.7%
  11 TSCP 1.8.1                    -44      12    2500   43.7%   16.9%
  12 Rustic 1.1                    -80      13    2500   38.6%   15.6%
  13 Lynx 0.14.1                  -274      16    2500   17.1%   13.8%

I'll just leave at 0.4, seems to be the value where all the non-significative results kinda agree


import nebullvm is slow

As shown in the figure below, import nebullvm takes 6.8 seconds but loading the model only takes 1.5 seconds. Why is import so slow?

Hi @shiyu22, the import is a bit slow because internally it imports all the required libraries (pytorch, tensorflow etc.), so I'm not surprised that loading the model is faster. Of course on a jupyter notebook you don't have to import again nebullvm each time you load or optimize a model, you can import it only once.

@valeriosofi Thanks for your answer, I tried import tensorflow and import tvm will take 2-3s, but my program is only related to tensor, is it possible not to import tensorflow and tvm, what do you think?
What I want to say is that because import nebullvm is too slow, is it possible to customize the use of torch or tensorflow according to user environment?

We can consider to add this feature in future, but for now it's not possible. If you want to contribute you can make a PR, we would be more than happy for your contribution ;)


[HOTFIX] Code convention

Fixed style guide.
Followed by #20

@anthonycorbacho I made it. Review this PR, please.

looks better but every variable expansion must follow this variation: ""$conf_dir"" became  ""${conf_dir}"" for example

I hope this would be a final fix. :)

look good now.
thanks
On Thu, Apr 2, 2015, 11:55 PM Jongyoul Lee<EMAIL_ADDRESS>wrote:

I hope this would be a final fix. :)
—
Reply to this email directly or view it on GitHub
https://github.com/apache/incubator-zeppelin/pull/25#issuecomment-88935530
.


Kibana 4 support

As per https://github.com/CiscoCloud/microservices-infrastructure/issues/55, @keithchambers has requested support for the Kibana framework on Mantl.

We're adding this via https://github.com/CiscoCloud/mantl-universe/pull/22.

mesos framework version: https://github.com/CiscoCloud/mantl-universe/tree/version-0.7/repo/packages/K/kibana-mesos/0
non-framework version: https://github.com/CiscoCloud/mantl-universe/tree/version-0.7/repo/packages/K/kibana/0


Add initial_pose in start_trajectory_main.cc Fixes #579

Fixes #579
Related to googlecartographer/cartographer#606
@damienrg @cschuet I followed most of the comments in googlecartographer/cartographer#642 except timestamp. Receiving timestamp sounds weird to me because trajectory should not start in past timestamp or future timestamp.

Ok. updated. ready for review.

Looks good to me.
Maybe edit the first comment as it will be in the git history?

Ok. I have added in the title. It will be the actual commit message I think.

@jihoonl Thanks for the PR! Ship it!

@wally-the-cartographer merge

Merge requested by authorized user cschuet. Merge queue now has a length of 1.


If the zoom is very far away there is no visible map if IGN is selected

When I come back to the site from time to time I have my maps selected but the zoom is on the world and with IGN selected I just have a blank page that can be confusing for some. Maybe put a default map for zoom 0?

It might not be  a problem of IGN, but the size of the last or total maps you have imported. If the size if > 10 Mb, then GPXStudio does not keep them in cache and causes to display the world map next time you com back. Just try with French TET F.gpx

I misspoke, it's just that with the IGN map there is no lower zoom and so the screen is white. Maybe put a default map?

This is what I have when I come back on gpxstudio with my browser.
The zoom is very far from France and therefore does not display a background map

It works for me with last version of Chrome on Windows 10

ok, I'll test on windows then.

I tested and I have the concern, I think we misunderstood each other.
In zoom 0, IGN SCAN 25 doesn't find any image and the screen remains white, is it possible to put a default one if the minimum zoom doesn't exist?

Is it really that important? If you activate your location, the map will be centered around it when you refresh the page.
And even if you don't, you can load a file to center the map there or go to a specific place with the search bar.

It's just weird to arrive on the site and have a white screen but yes for the moment I'm switching back to another background while I zoom in.
But if it shocks me no problem, I can use the site very well.


Add config file instructions and reorganize a bit

Closes #112
This PR adds more detail about config files and profiles to the external user documentation.
⚠ As I was writing, I made some organizational changes to that section and the section about AWS, so this PR should be evaluated before we get too far into revisions, so that those organizational changes don't cause too many conflicts! ⚠
(I retargeted #120 to this branch, as I think it makes sense to finish this one first.)
The organizational changes are mostly about hierarchy: I moved most everything up a level, but nested the "profile" discussion within the more general configuration discussion. It seemed like talking about workflow parameters in a config file was the easiest transition in, so I did that first, then moved on to the discussion of profiles.
I also moved the two required parameters up to the very top of the "Configuring scpca-nf" section, as I want to make sure that people don't miss those. (I had some thoughts about how to make it more clear that those are required at the command line, but I think that will be part of #105, and I will put those thoughts there.)
I didn't include too much detail about profiles as it seems like there were a number of ways one could go on that front, and most would not apply to most people. If you think there are places that I should expand a bit more though, I would be happy to do so!

@allyhawkins I think I addrssed most of your comments, and now link to the Singularity instructions in two places. (I also removed the direct docker link, instead linking to the nextflow instructions there as well, for consistency. I was originally going to link directly to singularity, but their docs are terrible for initial users.)
I also updated the template file a bit, trying to format it to make the organization a bit more clear, and removing the params{} block in favor of params.variable.
I hope this addresses the suggestions you had made, but let me know if I missed anything!


[Issue-3850]Fix the loop of wrapper consumer poll

Fixes 3850
Motivation
When we call the function named "poll(timeoutMillis)" to get records, the conditional judgment ++numberOfRecords < MAX_RECORDS_IN_SINGLE_POLL is always true from beginning, which will  break the loop right now. So we only can get one record from the poll() each time.
Modifications
Change the conditional judgment to ++numberOfRecords >= MAX_RECORDS_IN_SINGLE_POLL,
which can cache more than one record in a signal poll.

run integration tests

Merged in 2.3.1 at
95b4414


Display Episodes

Value Proposition
As a user, I want to see an episode list so that I can get an overview about what's there.
Description

Acceptance Criteria

[ ] A list of episodes (at least three) must be visible on the screen.
[ ] For each episode, the title of the podcast and the title of the episode are shown.
[ ] Length and publishing date of each episode is visible.

Tasks

[ ] Create an array of objects for the podcast episodes.
[ ] Each episode object contains a unique ID (nanoid), its length, its publishing date, a title, and the podcast name.
[ ] Create a component for episodes list.
[ ] Map through the episodes to display them in the list.
[ ] Add the episodes list to stylebook.
[ ] Test whether the episode title, podcast name, and podcast name, episode length and publishing date are displayed.

Complexity
M

Hey Andreas,
Nicely done! I have a few suggestions:
I would recommend to stick to the format of the value proposition:
As a user
I want to see an episode list
so that I can get an overview about what's there.

Your scribble should contain real content and no placeholder text (e.g. Episode One Title).
In your acceptance criteria you could be a bit more specific: A list of episodes (at least three) must be visible on the screen. "At least three" is not so specific. As well, it would be good to mention if your page is going to be scrollable.
All the things which are visible in your scribble do not need to be described in your acceptance criteria e.g. For each episode, the title of the podcast and the title of the episode are shown.

Hi Andrea,
thanks a lot for your feedback! I changed the user story accordingly.


Adding IconFont

Changes

Adding iconfont repo to npm
Adding to bootstrap main less file
New grunt copy process for fonts
ATENTION: This PR don't include the new build intentionally

IconFont Repo
https://github.com/transferwise/iconfont
IconFont Demo Page
http://transferwise.github.io/iconfont/

@StevePole updated in 9e66bb921c8faea2c912a7ecf494a2e2ee28ac9f

@StevePole @coolxeo Why are we including iconfont inside version control? Why do we install it through npm? Can we just configure bower and import the vendor .less files and font assets?

@keyvanakbary we're including all the build inside version control to simplify the distribution. I think is not a bad system for now

@coolxeo simplify it in which way? I actually think there is no simpler way that getting the code out of the repo xD. People will think that the files inside iconfont less folder could be editable (because they are inside of the repo). You could include bower in NPM, add the script "bower install" inside the "install" script section and finally import those less files inside bootstrap ones. Compile will be fine, easy and simple. This something that could be added later too.
In addition, you could squash both commits so this PR will have a clean history ;)


Publish toolchain binaries

Currently, people need to download BP and their first experience is compiling riscv-gnu-toolchain which takes hours and causes problems. Instead, we should break out our toolchain into a separate repo and then publish binaries using the github release mechanism. This whole process can be automated for minimal effort

Should be done in: https://github.com/black-parrot-sdk/black-parrot-sdk

This would be great in terms of usability.
I created a quick prototype which is not fully tested yet.
Let me know if you have some good ideas on how to integrate the binaries in the existing Makefile.
Currently I'm just extracting the binaries to the places where the make process would put them.
This is the prototype Makefile I came up with:
https://github.com/black-parrot-sdk/black-parrot-sdk/pull/7/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R14-R37

Fixed in sdk repo


[Syntax lookup] Add doc for char literal syntax

Proposal for https://github.com/rescript-association/rescript-lang.org/issues/162

' ' (single quote = char)

Looking good, thanks!


Make tokenizer_name configurable in llm_serving

System information

Alpa version: v0.2.1
Are you willing to contribute it (Yes/No): Yes

Describe the new feature and the current behavior/state
tokenizer_name should be configurable. Currently, it defaults to facebook/opt-30b
Will this change the current API? How?
The script launch_model_worker.py will have one more optional argument --tokenizer
Describe alternatives you've considered
Additional context

Hi Sean! Thanks for helping out on this. Let us know if you met any issues.


Implement "subset" queries

Currently, CRoaring supports "is a subset" queries:
https://github.com/RoaringBitmap/CRoaring/blob/master/include/roaring/roaring.h#L329
This should be added to RoaringBitmap.

Resolved thanks to @openkappa


Workshop tickets status from ti.to API

We'll have a status for each workshop loaded from ti.to API and stored in our database + simple page to reload it which can be called by cron.

Deployed to beta. You can test it there with URL /2019/programme/workshops/refresh_tickets


Is there ability to unbind events?

I am using CamanJS in an Angular environment, and work with new images after closing off a previous one. It would be great to be able to unbind events from firing such as "renderFinished" which share the same canvas on completion.
Thanks, and great library.

I am using it in react and I'm getting multiple versions of the listener, because I can't find a way to "unlisten" eg on unmount etc
thanks