Add option to get last modified time from header

Checklist

[X] I'm reporting a feature request
[X] I've verified that I'm running youtube-dl version 2021.04.07
[X] I've searched the bugtracker for similar feature requests including closed ones

Description
I would like to request the Last-modified header of the video I am about to download before downloading it.
Currently, the only options are:
   -g, --get-url                        Simulate, quiet but print URL
    -e, --get-title                      Simulate, quiet but print title
    --get-id                             Simulate, quiet but print id
    --get-thumbnail                      Simulate, quiet but print thumbnail URL
    --get-description                    Simulate, quiet but print video description
    --get-duration                       Simulate, quiet but print video length
    --get-filename                       Simulate, quiet but print output filename
    --get-format                         Simulate, quiet but print output format

e.g .
youtube-dl --get-mtime ...

For the moment you can extract the metadata as JSON (-j) and extract whichever of release_date``, timestamp, or upload_date` is supported by the extractor from the JSON output, eg, using a program like jq.

I tried that but I don't see any release_date or upload_date key/value.
I posted the output of the command:
youtube-dl -o /tmp/oneminute.m4a -f mf_akamai-audio_eng=96000-0  -j https://www.bbc.com/news/av/10462520

here
However, I know that such a date is being honoured because the resultant file has a Last Modified date of hours before I actually downloaded it.

As discussed under issue #28746, a modification time may only become available once the download is being started, and so a --get-mtime option couldn't behave like the other --get-xxx options and could be confusing.


Is there a way to declare some plugins as dependent on some others?

Instead of multiple use, if I have a plugin "foo/bar_1" that depends on `"foo/bar" would be nice a syntax like this:
use({
    "foo/bar"
    required = {
        "foo/bar_1",
        "foo/bar_2",
    }
})

Is this possible?

I found it's sort of possible like this:
user.use({
    "plugin",
    init = function ()
        user.use({"requires plugin"})
    end,
    config = function ()
        require("configs/plugin")
    end
})

I like this approach and I would like to know if I'll stumble upon some sort of limitations by doing this.


Version 1.4.1

A minor release addressing a number of issues noted below. Also see the 1.4.1 milestone.
Target May release.

[x] Unable to install via npm due to preinstall requiring root access #235
[x] Add Bower support #237
[x] appContent is undefined for pre-loaded apps #211
[x] Semver devDependency ReDoS alert #240
[x] Update Slack team invite form on Docs (Slackin') and add badge to readme
[x] Update devDependencies in package.json with local modules for generating docs
[x] Post-release: Add F2.js packages to cdnjs repo #250

👍 Nice!


Learn OpenCV interaction modes with mouse and keyboard (cpp)

This will help specifying then developing GUI controls.

Done.


Update homepage and fix eslint errors and warnings

Update homepage to be the GitHub page. Previously set to mongodb-js GitHub pages link that was invalid.
When running eslint checks, the following errors would occur:
1:1  error  Rule 'space-after-keywords' was removed and replaced by: keyword-spacing  space-after-keywords

This was fixed in version 2.1.0 of eslint-mongodb-js package. Just needed updated.
Remove unused module.
Clean up no-console warnings with single-line eslint disables. The console seems appropiate here.

Thanks!


Proposal: Please start using Semantic Versioning

I found that this project already supports Go modules. But sadly, the tags doesn't follow Semantic Versioning, which means that all tags of this project will be ignored by Go modules and replaced by pseudo-versions, go get acts weirdly when tags are not in that form. It would be great to have the tagged release be named in the format vX.X.X format so that go mod can read it.
	github.com/senseyeio/roger v0.0.0-20191009211040-43e330bee47f

Else the mod file shows something like github.com/senseyeio/roger v0.0.0-20191009211040-43e330bee47f which is not very readable and difficult to upgrade. It’s hard to verify which version is in use. This is not conducive to version control.
So, I propose this project to follow Semantic Versioning in future versions. For example, v1.0.1, v2.0.0, v3.1.0-alpha, v3.1.0-beta.2etc.

@dareid  Could you help me review this issue? Thx :p


Inconsistent dynamic array-length rendering behavior between iOS and Android.

Is this a bug report?
Yes.
Have you read the Bugs section of the Contributing to React Native Guide?
Yes. If there is any open issue(s) related to this behavior, I must have missed it.
Environment

react-native -v:

react-native-cli: 2.0.1
react-native: 0.45.0

node -v: v7.10.0
npm -v: 4.2.0
yarn --version (if you use Yarn): 0.24.5

Target Platform: iOS, Android

Development Operating System: macOS 10.12.5

Build tools: Standard.

(NOTE: Although the above is reflective of my actual environment, I also just reproduced on a fresh react-native init using RN v0.46.3).
Steps to Reproduce

react-native init MyNewApp

Embed the minimal code snippet:

  <View>
    <StatusBar hidden />
    {Array.from(Array(5).keys()).map(idx => (
      <Text key={idx}>{idx}</Text>
    ))}
  </View>

Run on iOS and Android separately, observe the below behavior (screenshots):

Expected Behavior
I'd expect the rendered output to be identical on both iOS and Android. Either:

... it works on both iOS and Android.

... it works on works on neither iOS nor Android.

Currently, it works as expected on iOS. On Android, nothing is rendered.
Although I do realize this is a relatively new language feature that may require transpilation, as I mentioned above, if it weren't to work, I'd expect it to not work on either platform rather than the inconsistent results I'm seeing presently.
Actual Behavior
See above screenshot.
Reproducible Demo
See above code snippet.

Specifically, the pertinent line: Array.from(Array(5).keys()).

I'd also originally tried: [...Array(5).keys()]

Additional Context
Although I used a static (literal) numeric value in the minimal reproducible snippet above, in my actual app code, the actual value (quantity) is dynamic (depending on props).
For example, imagine the "pegs" of a paging indicator for a swipeable view, where the number of elements shown is dynamic based on some resultant API call to populate the view with data.
This ended up throwing me for a quick loop because I'd been iterating on the core business logic, visual appearance, and user interaction using the iOS simulator. Once I fired up an Android emulator (and additionally sanity-checked with an actual device), some of my dynamically-rendered screen elements (based on quantity) using the above technique weren't showing up on Android as they were on iOS.
Just to reiterate, the reason I'm filing this bug is because the resultant behavior isn't consistent between both platforms. If it wouldn't have worked for either, I would've spent less time tracing down the issue.

https://snack.expo.io/rkbkRmtHb Here is a quick snack of this issue.

Is it any different in iOS 8? Maybe JSC version has something to do with this.

According to ES6 support table, after checking "Show obsolete platforms" (so iOS 8 column shows up) and looking at "Array static methods" > "Array.from, array-like objects", the support for Array.from method starts at iOS 9.
So this makes me think your test would also fail at iOS 8 simulator and kind of explain the issue.

Is it any different in iOS 8? Maybe JSC version has something to do with this.

Based on my understanding from this page of the docs:

"On iOS simulators and devices, Android emulators and devices React Native uses JavaScriptCore which is the JavaScript engine that powers Safari. On iOS JSC doesn't use JIT due to the absence of writable executable memory in iOS apps."

... it sounds like iOS and Android both use JSC. I was aware of the fact that iOS did, but I hadn't yet done any diligence in terms of Android implementation details.
If that's indeed the case, the only situation in which we'd see the behavior described by this issue is if/when iOS and Android are using different versions of JSC, right? Because AFAIK, all else should be equal as far as Javascript goes (eg. transpilation, polyfills) between platforms.

Yes, all else is equal but here's the thing. On different iOS versions (iOS 8, 9, 10) JSC version is tied to the operating system. On Android, JSC is not part of the device, its binary is shipped with your app.
In the JavaScript environment that does not have Array.from, react-native polyfills it.
Since Android's JSC version is closer to iOS 8's (this is not documented anywhere except mentioned in few GitHub issues in this repo), I expect your bug report to behave the same on both Android and iOS 8, since these would be the platforms to use the Array.from polyfill. Does that make sense?

And it's still a valid bug report btw, I am just trying to help isolating the issue.

On Android, JSC is not part of the device, its binary is shipped with your app.
...
Since Android's JSC version is closer to iOS 8's (this is not documented anywhere except mentioned in few GitHub issues in this repo)...

Ah! This was the part that I was missing 😄

... I expect your bug report to behave the same on both Android and iOS 8, since these would be the platforms to use the Array.from polyfill. Does that make sense?

Totally! 👍
As a somewhat related aside, if iOS is the lowest common denominator (in that the JSC version is pegged), wouldn't it make sense to keep Android's shipped JSC version in lock-step (or at least very close) in order to avoid inconsistencies?
Of course, I realize there's probably a very good explanation as to why this isn't the case (especially considering I'm unaware of the degree of effort involved in shipping updated JSC versions) 😄
Independently, like you said, the pertinent/appropriate polyfills should largely make the above a moot point.

See https://github.com/facebook/react-native/issues/15382#issuecomment-320754495 if you want updated JSC on Android , but I don't think this library is tested by Facebook , so use it at your own risk.


Fix compile error when building folly

remove compile flag -masm=intel when building folly
fix #1869

Hi @stdpain, Can you please update the title / description as suggested ?

Hi @stdpain, Can you please update the title / description as suggested ?

@kgpai OK

This same change was landed as part of PR1883


Improve error handling

Right now the plugin does "only" trigger an error when there is a problem during the commit process. This errors seem to be ignored by Kirby:

A hook is not expected to return anything. You cannot control the user flow with hooks at this state. They are silently triggered.

I honestly have no idea how to improve this, but for now I always have to create my own debugging function to log it into a separate file.
One way might be to allow a commit to be performed through the cron routes. This would at least trigger the same error as the plugin itself when a hook is called. I'd be ok with not exposing the functionality in the interface, but have it available as a huffed feature.
Any thought?
Thanks! :)

I did not realise there is already #38. Looks like a possible solution for me. Only problem I see is that they would be committed once it's working again.


Fix INCLUDE usage in docs

We need to investigate and evaluate all uses of INCLUDES in our docs and remove those that shouldn't be includes, and potentially add those that should in includes.
List of all includes (not including applies-to-v4-current.md):
Unique files: 40

[ ] bot-builder-deploy-az-cli.md	25	[!INCLUDE [deploy prerequisite](~/includes/deploy/snippet-prerequisite.md)]
[ ] bot-builder-deploy-az-cli.md	29	[!INCLUDE [deploy prepare intro](~/includes/deploy/snippet-prepare-deploy-intro.md)]
[ ] bot-builder-deploy-az-cli.md	33	[!INCLUDE [deploy az login](~/includes/deploy/snippet-az-login.md)]
[ ] bot-builder-deploy-az-cli.md	37	[!INCLUDE [deploy az subscription](~/includes/deploy/snippet-az-set-subscription.md)]
[ ] bot-builder-deploy-az-cli.md	41	[!INCLUDE [deploy create app registration](~/includes/deploy/snippet-create-app-registration.md)]
[ ] bot-builder-deploy-az-cli.md	56	[!INCLUDE [ARM with new resource group](~/includes/deploy/snippet-ARM-new-resource-group.md)]
[ ] bot-builder-deploy-az-cli.md	61	[!INCLUDE [ARM with existing resource group](~/includes/deploy/snippet-ARM-existing-resource-group.md)]
[ ] bot-builder-deploy-az-cli.md	68	[!INCLUDE [retrieve or create IIS/Kudu files](~/includes/deploy/snippet-IIS-Kudu-files.md)]
[ ] bot-builder-deploy-az-cli.md	72	[!INCLUDE [zip up code](~/includes/deploy/snippet-zip-code.md)]
[ ] bot-builder-deploy-az-cli.md	76	[!INCLUDE [deploy code to Azure](~/includes/deploy/snippet-deploy-code-to-az.md)]
[ ] bot-builder-deploy-az-cli.md	80	[!INCLUDE [test in web chat](~/includes/deploy/snippet-test-in-web-chat.md)]
[ ] bot-builder-deploy-az-cli.md	93	[!INCLUDE [deploy csharp bot to Azure](~/includes/deploy/snippet-deploy-simple-csharp-echo-bot.md)] -->
[ ] bot-service-activities-entities.md	19		[!include[Entity boilerplate](includes/snippet-entity-boilerplate.md)]
[ ] bot-service-channel-connect-email.md	44	[!INCLUDE [email channelData json](~/includes/snippet-channelData-email.md)]
[ ] bot-service-channel-connect-groupme.md	19	[!INCLUDE [Channel Inspector intro](~/includes/snippet-channel-inspector.md)]
[ ] bot-service-channel-connect-telegram.md	19	[!INCLUDE [Channel Inspector intro](~/includes/snippet-channel-inspector.md)]
[ ] bot-service-debug-bot.md	44	[!INCLUDE [csharp vscode](~/includes/bot-service-debug-bot/csharp-vscode.md)]
[ ] bot-service-debug-bot.md	46	[!INCLUDE [csharp visual studio](~/includes/bot-service-debug-bot/csharp-vs.md)]
[ ] bot-service-debug-bot.md	50	[!INCLUDE [javascript vscode](~/includes/bot-service-debug-bot/js-vscode.md)]
[ ] bot-service-debug-bot.md	54	[!INCLUDE [python vscode](~/includes/bot-service-debug-bot/python-vscode.md)]
[ ] bot-service-design-pattern-embed-web-site.md	61	[!INCLUDE [Introduction to backchannel mechanism](~/includes/snippet-backchannel.md)]
[ ] bot-service-manage-channels.md	69	[!INCLUDE [publishing](./includes/snippet-publish-to-channel.md)]
[ ] dotnet\bot-builder-dotnet-sdk-quickstart.md	20	[!INCLUDE [Azure vs local development](../includes/snippet-quickstart-paths.md)]
[ ] dotnet\bot-builder-dotnet-sdk-quickstart.md	22		<!-- Delete this include file [!INCLUDE [dotnet quickstart](../includes/quickstart-dotnet.md)] -->
[ ] dotnet\bot-builder-dotnet-sdk-quickstart.md	26	[!INCLUDE [dotnet prerequisites](../includes/quickstart/dotnet/quickstart-dotnet-prerequisites.md)]
[ ] dotnet\bot-builder-dotnet-sdk-quickstart.md	30	[!INCLUDE [dotnet quickstart create bot](../includes/quickstart/dotnet/quickstart-dotnet-create-bot.md)]
[ ] dotnet\bot-builder-dotnet-sdk-quickstart.md	34	[!INCLUDE [dotnet quickstart start bot](../includes/quickstart/dotnet/quickstart-dotnet-start-bot.md)]
[ ] dotnet\bot-builder-dotnet-sdk-quickstart.md	38	[!INCLUDE [dotnet quickstart start Emulator](../includes/quickstart/common/quickstart-start-emulator.md)]
[ ] includes\deploy\snippet-prepare-deploy-intro.md	13	[!INCLUDE [about .NET Core versions in the templates](../vsix-templates-versions.md)]
[ ] includes\quickstart\dotnet\quickstart-dotnet-prerequisites.md	17	[!INCLUDE [.NET VSIX templates info](../../../includes/vsix-templates-versions.md)]
[ ] includes\snippet-channeldata.md	35	[!INCLUDE [email channelData json](~/includes/snippet-channelData-email.md)]
[ ] includes\snippet-deploy-considerations.md	10	[!INCLUDE [Application configuration settings](~/includes/snippet-tip-bot-config-settings.md)]
[ ] javascript\bot-builder-javascript-quickstart.md	20	[!INCLUDE [Azure vs local development](../includes/snippet-quickstart-paths.md)]
[ ] javascript\bot-builder-javascript-quickstart.md	22		<!-- Delete this include file [!INCLUDE [javascript quickstart](../includes/quickstart-javascript.md)] -->
[ ] javascript\bot-builder-javascript-quickstart.md	26	[!INCLUDE [dotnet prerequisites](~/includes/quickstart/javascript/quickstart-javascript-prerequisites.md)]
[ ] javascript\bot-builder-javascript-quickstart.md	30	[!INCLUDE [dotnet quickstart create bot](~/includes/quickstart/javascript/quickstart-javascript-create-bot.md)]
[ ] javascript\bot-builder-javascript-quickstart.md	34	[!INCLUDE [dotnet quickstart start bot](~/includes/quickstart/javascript/quickstart-javascript-start-bot.md)]
[ ] javascript\bot-builder-javascript-quickstart.md	38	[!INCLUDE [dotnet quickstart start Emulator](~/includes/quickstart/common/quickstart-start-emulator.md)]
[ ] python\bot-builder-python-quickstart.md	21		<!-- Delete this include file [!INCLUDE [python quickstart](../includes/quickstart-python.md)] -->
[ ] python\bot-builder-python-quickstart.md	25	[!INCLUDE [dotnet prerequisites](~/includes/quickstart/python/quickstart-python-prerequisites.md)]
[ ] python\bot-builder-python-quickstart.md	29	[!INCLUDE [dotnet quickstart create bot](~/includes/quickstart/python/quickstart-python-create-bot.md)]
[ ] python\bot-builder-python-quickstart.md	33	[!INCLUDE [dotnet quickstart start bot](~/includes/quickstart/python/quickstart-python-start-bot.md)]
[ ] python\bot-builder-python-quickstart.md	37	[!INCLUDE [dotnet quickstart start Emulator](~/includes/quickstart/common/quickstart-start-emulator.md)]
[ ] rest-api\bot-framework-rest-connector-add-media-attachments.md	16	[!INCLUDE [Channel Inspector intro](~/includes/snippet-channel-inspector.md)]
[ ] rest-api\bot-framework-rest-connector-add-rich-cards.md	36	[!INCLUDE [Channel Inspector intro](~/includes/snippet-channel-inspector.md)]
[ ] rest-api\bot-framework-rest-connector-add-rich-cards.md	58	[!INCLUDE [Table of card action types](../includes/snippet-card-action-types.md)]
[ ] rest-api\bot-framework-rest-connector-add-suggested-actions.md	14	[!INCLUDE [Introduction to suggested actions](../includes/snippet-suggested-actions-intro.md)]
[ ] rest-api\bot-framework-rest-connector-channeldata.md	34	[!INCLUDE [Email channelData table](~/includes/snippet-channelData-email.md)]
[ ] rest-api\bot-framework-rest-connector-create-messages.md	20	[!INCLUDE [Channel Inspector intro](~/includes/snippet-channel-inspector.md)]
[ ] v4sdk\abs-quickstart.md	25	[!INCLUDE [Azure vs local development](~/includes/snippet-quickstart-paths.md)]
[ ] v4sdk\abs-quickstart.md	91	[!INCLUDE [download keys snippet](../includes/snippet-abs-key-download.md)]
[ ] v4sdk\bot-builder-basics.md	170	[!INCLUDE [alert-await-send-activity](../includes/alert-await-send-activity.md)]
[ ] v4sdk\bot-builder-channeldata.md	18	[!INCLUDE [Channel Data Content](../includes/snippet-channeldata.md)]
[ ] v4sdk\bot-builder-concept-adaptive-dialog-declarative.md	433	[!INCLUDE [Install the Bot Framework CLI](../includes/install-bf-cli.md)]
[ ] v4sdk\bot-builder-concept-identity-providers.md	55	[!INCLUDE [azure-ad-v1-settings](~/includes/authentication/auth-aad-v1-settings.md)]
[ ] v4sdk\bot-builder-concept-identity-providers.md	66	[!INCLUDE [azure-ad-v2-settings](~/includes/authentication/auth-aad-v2-settings.md)]
[ ] v4sdk\bot-builder-concept-identity-providers.md	105	[!INCLUDE [generic-oauth2-settings](~/includes/authentication/auth-generic-oauth2-settings.md)]
[ ] v4sdk\bot-builder-concept-identity-providers.md	114	[!INCLUDE [generic-provider-oauth2-settings](~/includes/authentication/auth-generic-provider-oauth2-settings.md)]
[ ] v4sdk\bot-builder-create-a-bot-project.md	48	[!INCLUDE [VSIX templates](../includes/vsix-templates-versions.md)]
[ ] v4sdk\bot-builder-howto-add-media-attachments.md	177	[!INCLUDE [Table of card action types](../includes/snippet-card-action-types.md)]
[ ] v4sdk\bot-builder-howto-bf-cli-alterations-qna.md	43	[!INCLUDE [applies-to-v4](../includes/install-bf-cli.md)]
[ ] v4sdk\bot-builder-howto-bf-cli-deploy-luis.md	81	[!INCLUDE [applies-to-v4](../includes/install-bf-cli.md)]
[ ] v4sdk\bot-builder-howto-bf-cli-deploy-luis.md	164	[!INCLUDE [applies-to-v4](../includes/generate-source-code-luis-cli.md)]
[ ] v4sdk\bot-builder-howto-bf-cli-deploy-qna.md	75	[!INCLUDE [applies-to-v4](../includes/install-bf-cli.md)]
[ ] v4sdk\bot-builder-howto-bf-cli-update-luis.md	47	[!INCLUDE [applies-to-v4](../includes/install-bf-cli.md)]
[ ] v4sdk\bot-builder-howto-bf-cli-update-luis.md	163	[!INCLUDE [applies-to-v4](../includes/generate-source-code-luis-cli.md)]
[ ] v4sdk\bot-builder-howto-cross-train.md	100	[!INCLUDE [applies-to-v4](../includes/install-bf-cli.md)]
[ ] v4sdk\bot-builder-howto-v4-storage.md	26	[!INCLUDE [VSIX templates](~/includes/vsix-templates-versions.md)]
[ ] v4sdk\bot-builder-telemetry.md	82	[!INCLUDE [dotnet telemetry section](../includes/telemetry-dotnet-main.md)]
[ ] v4sdk\bot-builder-telemetry.md	86	[!INCLUDE [javascript telemetry section](../includes/telemetry-javascript-main.md)]
[ ] v4sdk\bot-builder-telemetry.md	90	[!INCLUDE [python telemetry section](../includes/telemetry-python.md)]
[ ] v4sdk\bot-builder-telemetry.md	99	[!INCLUDE [dotnet telemetry-Enabling disabling activity section](../includes/telemetry-dotnet-enabling-disabling-activity-event-personal-information-logging.md)]
[ ] v4sdk\bot-builder-telemetry.md	103	[!INCLUDE [javascript telemetry section](../includes/telemetry-javascript-enabling-disabling-activity-event-personal-information-logging.md)]
[ ] v4sdk\bot-builder-telemetry.md	108	[!INCLUDE [python telemetry section](../includes/telemetry-python-enabling-disabling-activity-event-personal-information-logging.md)]
[ ] v4sdk\bot-builder-telemetry.md	117	[!INCLUDE [dotnet telemetry-luis section](../includes/telemetry-dotnet-luis.md)]
[ ] v4sdk\bot-builder-telemetry.md	121	[!INCLUDE [javascript telemetry-luis section](../includes/telemetry-javascript-luis.md)]
[ ] v4sdk\bot-builder-telemetry.md	126	[!INCLUDE [python telemetry-luis section](../includes/telemetry-python-luis.md)]
[ ] v4sdk\bot-builder-tutorial-add-qna.md	391	[!INCLUDE [zip up code](~/includes/deploy/snippet-zip-code.md)]
[ ] v4sdk\bot-builder-tutorial-add-qna.md	405	[!INCLUDE [deploy code to Azure](~/includes/deploy/snippet-deploy-code-to-az.md)]
[ ] v4sdk\bot-builder-tutorial-add-qna.md	414	[!INCLUDE [publish snippet](~/includes/deploy/snippet-publish-js.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	29	[!INCLUDE [dotnet prerequisites](~/includes/quickstart/dotnet/quickstart-dotnet-prerequisites.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	33	[!INCLUDE [javascript prerequisites](~/includes/quickstart/javascript/quickstart-javascript-prerequisites.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	37	[!INCLUDE [python prerequisites](~/includes/quickstart/python/quickstart-python-prerequisites.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	45	[!INCLUDE [dotnet quickstart create bot](~/includes/quickstart/dotnet/quickstart-dotnet-create-bot.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	49	[!INCLUDE [javascript quickstart create bot](~/includes/quickstart/javascript/quickstart-javascript-create-bot.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	53	[!INCLUDE [python quickstart create bot](~/includes/quickstart/python/quickstart-python-create-bot.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	61	[!INCLUDE [dotnet quickstart start bot](~/includes/quickstart/dotnet/quickstart-dotnet-start-bot.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	65	[!INCLUDE [javascript quickstart start bot](~/includes/quickstart/javascript/quickstart-javascript-start-bot.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	69	[!INCLUDE [python quickstart start bot](~/includes/quickstart/python/quickstart-python-start-bot.md)]
[ ] v4sdk\bot-builder-tutorial-create-basic-bot.md	75	[!INCLUDE [dotnet quickstart start Emulator](~/includes/quickstart/common/quickstart-start-emulator.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	34	[!INCLUDE [deploy prerequisites](../includes/deploy/snippet-prerequisite.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	40	[!INCLUDE [deploy prepare intro](../includes/deploy/snippet-prepare-deploy-intro.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	44	[!INCLUDE [deploy az login](../includes/deploy/snippet-az-login.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	48	[!INCLUDE [deploy az subscription](../includes/deploy/snippet-az-set-subscription.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	52	[!INCLUDE [deploy create app registration](../includes/deploy/snippet-create-app-registration.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	66	[!INCLUDE [ARM with new resource group](../includes/deploy/snippet-ARM-new-resource-group.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	70	[!INCLUDE [ARM with existing resource group](../includes/deploy/snippet-ARM-existing-resource-group.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	76	[!INCLUDE [retrieve or create IIS/Kudu files](../includes/deploy/snippet-IIS-Kudu-files.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	80	[!INCLUDE [zip up code](../includes/deploy/snippet-zip-code.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	84	[!INCLUDE [deploy code to Azure](../includes/deploy/snippet-deploy-code-to-az.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	88	[!INCLUDE [test in web chat](../includes/deploy/snippet-test-in-web-chat.md)]
[ ] v4sdk\bot-builder-tutorial-deploy-basic-bot.md	92	[!INCLUDE [additional resources snippet](../includes/deploy/snippet-additional-resources.md)]
[ ] v4sdk\migration\conversion-core.md	42	[!INCLUDE [VSIX templates](~/includes/vsix-templates-versions.md)]
[ ] v4sdk\migration\migration-overview.md	155	[!INCLUDE [VSIX templates](~/includes/vsix-templates-versions.md)]

The rules (from the docs)
Included Markdown files
Where markdown files need to be repeated in multiple articles, you can use an include file. The includes feature instructs Docs to replace the reference with the contents of the include file at build time. You can use includes in the following ways:

Inline: Reuse a common text snippet inline with within a sentence.
Block: Reuse an entire Markdown file as a block, nested within a section of an article.

An inline or block include file is a Markdown (.md) file. It can contain any valid Markdown. Include files are typically located in a common includes subdirectory, in the root of the repository. When the article is published, the included file is seamlessly integrated into it.
Includes syntax
Block include is on its own line:

[!INCLUDE ]

Inline include is within a line:

Text before [!INCLUDE ] and after.

Where <title> is the name of the file and <filepath> is the relative path to the file. INCLUDE must be capitalized and there must be a space before the <title> .
Here are requirements and considerations for include files:

Use block includes for significant amounts of content--a paragraph or two, a shared procedure, or a shared section. Do not use them for anything smaller than a sentence.
Includes won't be rendered in the GitHub rendered view of your article, because they rely on Docs extensions. They'll be rendered only after publication.
Ensure that all the text in an include file is written in complete sentences or phrases that do not depend on preceding text or following text in the article that references the include. Ignoring this guidance creates an untranslatable string in the article.
Don't embed include files within other include files.
Place media files in a media folder that's specific to the include subdirectory--for instance, the  /includes/media folder. The media directory should not contain any images in its root. If the include does not have images, a corresponding media directory is not required.
As with regular articles, don't share media between include files. Use a separate file with a unique name for each include and article. Store the media file in the media folder that's associated with the include.
Don't use an include as the only content of an article. Includes are meant to be supplemental to the content in the rest of the article.

Also see the section Include reusable content in articles in the contributor guide.

When working on this issue, check off the files you've edited.

When working on this issue, check off the files you've edited.

Move this to DevOps, then close.


How to set a max number for selecting photos?

As you can see the title,
I'd like to set a limit(maximum) number for selecting photos.
Thanks,

You can do it implementing the GMImagePickerControllerDelegate protocol method shouldSelectAsset . This method will be triggered each time user tryes to select and asset, so when they reach your limit, you can return NO to prevent the selection and display your custom alert message or w/e you want.
/**
 *  Asks the delegate if the specified asset should be selected.
 *
 *  @param picker The controller object managing the assets picker interface.
 *  @param asset  The asset to be selected.
 *
 *  @return `YES` if the asset should be selected or `NO` if it should not.
 *
 */
- (BOOL)assetsPickerController:(GMImagePickerController *)picker shouldSelectAsset:(PHAsset *)asset;

You can get the current number of selected assets from NSMutableArray *selectedAssets, or you can count them yourself using didSelectAsset and didDeselectAsset protocol methods.

By the way, i know these optional protocol methods are not documented and it is not trivial. If you want to improve documentatio


Threshold Parameter Added

Threshold Argument Added
I appreciate the awesome deep face package! 🚀 While using it for my project, I found that the hardcoded threshold values in distances.py didn't suit my needs. For my contribution, I've added a parameter to make the threshold customizable. This marks my first-ever open-source contribution.

DeepFace.py

verify function
find function

Thanks,
Rohit Ingole (DataRohit)

Verify returns distance to make threshold customizable. If smo needs his/her own threshold, he/she should use distance in the response instead of verified key.


[Bug] UWP PopUp Disappears upon changing window and Returning again

Description
Popups will disapear if you bring another window infront of your app and then return to your app.
No Events will be triggered.
Link to Reproduction Sample
You can reproduce this with the Samples provided with xct
Steps to Reproduce

Open a Popup Sample
Switch to another Window
Switch back to the sample window

Expected Behavior
Popup will still be there.
Actual Behavior
Popup will disappear.
Basic Information

Version with issue: 1.3.1
Last known good version: -
IDE: Visual Studio 2019
Platform Target Frameworks:

UWP:  19041

Affected Devices: Windows Desktop

Workaround
None.

The underlying Flyout from UWP has an event Closed. By connecting it to dismiss with some result it's at least detectable that the popup disappeared.
Otherwise there is currently no way to detect if the Popup is still there or if it has disappeared.


Blank screen when using with the Ionic 2/3 Tabs Component

The plugin seems incompatible with the Ionic 2/3 tabs component. The map is only rendered the first time the relevant tab is pressed. When navigating away and then back to the map page is it no longer displayed - just a blank screen is rendered.
Are there any work arounds for this? I have heard using Events to inform the tab component would be a solution?
Thanks

You need to remove before opening another tab using map.remove()

@wf9a5m75 I have tried this in both the below contexts on the maps page, however the issue still persists?
  ionViewDidLeave() {
    this.map.remove()
  }

  ionViewWillLeave() {
    this.map.remove()
  }

I have also this issue. How to proper remove map before switch tab ?

@boskiv I still have this issue, and haven't found anyone who has successfully used the maps plugin with Ionic tabs. @wf9a5m75 I don't believe it is possible to use this with tabs?

Could you give me more enough information?
Such as example code that reproduce your issue 100%

@wf9a5m75 This is an issue with using Ionic. It's due (apparently) to multiple maps not being supported by the plugin. The this.map.remove() method doesn't seem to address the issue.
The issue can only be seen on an actual device. I can provide an APK to test if you wish?

If the issue is ionic problem, I can not help. Because I'm NOT familiar with ionic.
You should ask at the ionic forum.
Anyway please make an apk that is very simple features (for example, only map and tab),  and put it with full code to a github repository, then tell me the repository URL.
**Don't share with your full app code. Please make a simple example code that reproduces your issue 100%.  **

@boskiv Do you have a simple example that I can also test?

Do you guys still face the same issue?

@wf9a5m75 What versions I need to check ?

At least this plugon works on  ionic2.
If you don't face any problem now, you don't need to check

I had no problem with this, Ionic 2.x + map plugin 1.4. I used Ionic Native wrapper in a little bit different way:
this.map = new GoogleMaps(...);
Or you can follow this tutorial: https://www.joshmorony.com/ionic-2-how-to-use-google-maps-geolocation-video-tutorial/

Installing the v2 for the ionic framework, please check out this page.
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/For-ionic2-users/README.md
If you have any problems, please file another issue. Thanks.


Fix exporter_lag off-by-one bug

Fixes #32

I think this suggestion is very sensible. Happy to make the patch once I get the chance.

@braedon This has been implemented. Please review.

Looks good to me - thanks!

Released in 0.5.3


feat(frontend): DappsCarousel usage (all screen sizes)

Motivation
In this PR, DappsCarousel have been added to NavigationMenu (displayed on xl screens) and Tokens page layout (displayed on >= lg screens). For now, the carousel should be rendered only on the Tokens page. All the aspects (breakpoints, where to render) were agreed with Artem.
Desktop:

Tablet:

Mobile:

After we merge https://github.com/dfinity/oisy-wallet/pull/3111, the inactive carousel will be just a "div", so memory-wise we should be fine.


Home no cloud accounts

Coverage decreased (-0.4%) to 46.308% when pulling 1a73f43f3d0af2fbc9349d900c5487a435357ecf on josephkane:home-no-cloud-accounts into f3b85a291d9f67a2745fed518c7e909be05d9a69 on supergiant:master.


CIV-14751 Manage Stay Changes

PR for https://tools.hmcts.net/jira/browse/CIV-14751

Closed as change was merged as part of another PR.


Highlighter prints things when regex highlighting is triggered for the 1st time after login:

This is my addition to zsh-syntax-highlighting/highlighters/regexp/regexp-highlighter.zsh imediately after the line typeset -gA ZSH_HIGHLIGHT_REGEXP:
# Highlight 'ls' and 'cd'
ZSH_HIGHLIGHT_REGEXP+=('(^| )(ls|cd)($| )' 'fg=green')

Everytime the regex is triggered for the 1st time after login, the terminal prints things. The 2nd time and beyond, it works fine
Last login: Mon Jan 22 19:28:18 on ttys000
▸ ~ ls
_zsh_highlight_regexp_highlighter_loop:6: array parameter match created globally in function _zsh_highlight_regexp_highlighter_loop
_zsh_highlight_regexp_highlighter_loop:6: array parameter mbegin created globally in function _zsh_highlight_regexp_highlighter_loop
_zsh_highlight_regexp_highlighter_loop:6: array parameter mend created globally in function _zsh_highlight_regexp_highlighter_loop
▸ ~ ls
Applications   Downloads      Movies         Public         pymel.log      vscode
Desktop        GoogleDrive    Music          VirtualBox VMs safe-rm.sh     vscode.zip
Documents      Library        Pictures       anaconda2      settings.json  xgen
▸ ~

This behavior repeats if your logout and login again.

Whoops, sorry I must have missed the message at that time! It was definitely not my intention to be rude by not responding. I stumbled across this today when I was googling and was surprised this was me who filed this bug..

Thanks for letting us know it works for you now! :-)


Rewrites elasticsearch-http as an OkHttp client

more detail later

most of the additional lines (~750) here are from resurrecting the dependency link and span moshi adapters and tests.

@openzipkin/elasticsearch I need to backfill some unit tests, but I've tested this manually against local and AWS elasticsearch and 👍
Note: some of the new code here is self-tracing, which we never had before.

didn't get much progress on this today. maybe tomorrow

ok ready to go now. once this is in, we can start doing more unwinding, such as ES 5 interop.


it would be cute to have a winter video

use this one instead https://www.youtube.com/watch?v=-C091PSN3lg


Bug: no animation on checkbox and switch

for the preferences that natively have an animation when being toggled, the library doesn't show their animation.

Are there any plans to "fix" this? I can live without it, but the animations would be nice to have.

@zacharee I was told to use what the support library has to offer:
https://issuetracker.google.com/issues/37103112
But it still doesn't work.
So I created a new report about this here:
https://issuetracker.google.com/issues/63456897
Please star it and optionally comment there.


Differentiate between network errors and no dns or mx record.

Thanks for this @rzeigler, would you be able to also add the tests for this, then I can merge it.

Due to a refactor of how this lib works, I'll have to close this.


pyhtml tot being served in lopy

I have installed the server on lopy But the files apart from index.html are not being served, I get a 404, even the png image is not being loaded (404 from the network tab of chrome dev tools. Is it a file format issue with lopy, is there a fix for this?

Hello,
MicroWebSrv2 works on Pycom LoPy.
Could you publish the debug-logs please?
Do you have checked your files system by FTP on your LoPy?

This is what I get  when I click the pdf link
[image: image.png]
this is the files I see when using ftp
[image: image.png]
I have only cloned the repo and  added boot.py and wifi connection code in
the main.py file
On Fri, Feb 7, 2020 at 2:21 AM J-Christophe Bos<EMAIL_ADDRESS>wrote:

Hello,
MicroWebSrv2 works on Pycom LoPy.
Could you publish the debug-logs please?
Do you have checked your files system by FTP on your LoPy?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jczic/MicroWebSrv2/issues/25?email_source=notifications&email_token=AEFPX6H66R3CMJZDFZFAA4LRBSLOVA5CNFSM4KQH6TDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELBE4AQ#issuecomment-583159298,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFPX6AGMWUXRK4Y3YTVTGTRBSLOVANCNFSM4KQH6TDA
.

This is my project file
On Mon, Feb 10, 2020 at 7:04 AM Note 3<EMAIL_ADDRESS>wrote:

This is what I get  when I click the pdf link
[image: image.png]
this is the files I see when using ftp
[image: image.png]
I have only cloned the repo and  added boot.py and wifi connection code in
the main.py file
On Fri, Feb 7, 2020 at 2:21 AM J-Christophe Bos<EMAIL_ADDRESS>wrote:

Hello,
MicroWebSrv2 works on Pycom LoPy.
Could you publish the debug-logs please?
Do you have checked your files system by FTP on your LoPy?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jczic/MicroWebSrv2/issues/25?email_source=notifications&email_token=AEFPX6H66R3CMJZDFZFAA4LRBSLOVA5CNFSM4KQH6TDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELBE4AQ#issuecomment-583159298,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFPX6AGMWUXRK4Y3YTVTGTRBSLOVANCNFSM4KQH6TDA
.

Hello @note5 and sorry for the late.
Your messages are not visible on github :
https://github.com/jczic/MicroWebSrv2/issues/25
(Don't forget to publish the term/repl logs).

Hey,
I had this same issue on a WiPy if you are using pymakr to upload your files, you will need to go to Pymakr Global Settings and add ico and pyhtml files to "Upload File Types"

@theBASTI0N 👍

thank you it, has really saved me


Added AdminRouter and DC-OS Diagnostics service to Windows agent

The changes in this PR have been tested with
1. A private SCRIPTS_REPO_URL, a fork from "https://github.com/dcos/dcos-windows", with changes in
this PR
2.  A private dcosWindowsBootstrapURL that has updated DCOSWindowsAgentSetup.ps1 and a
manually zipped diagnostics file, which contains all the files needed for the DCOS diagnostics
3.  Custom deployment json files that specify above private dcosWindowsBootstrapURL as
dcosWindowsBootstrapURL in its   "dcosConfig" section
Note:
The build script, for the the mesos-jenkins repo,  for producing the diagnostics.zip is still in the work.
Once this PR is reviewed and approved, please wait until the build script is completed before any merging

Merging this since I finished setting up the CI to publish updated diagnostics.zip package to the Windows bootstrap endpoints from: http://dcos-win.westus.cloudapp.azure.com/dcos-windows/.


Metadata is lost when converting to WAV

When downloading mp3, everything works great. But when i download WAV, it loses all metadata. Its basically a empty File with only audio and title.
As i dont really have that much of programming experience, i dont feel qualified to fix that myself.
I found this: https://trac.ffmpeg.org/ticket/7579
(Im not really shure if you even use ffmpeg)

I also found this: https://stackoverflow.com/questions/8081676/how-to-download-a-youtube-video-using-the-youtubes-api
(im not shure if that helps)

Hi, sorry for the delay, I will try to check it out next week. I'm very busy currently :(

Coming back to this, wav just does not support some of the metadata. I use FLAC now


No dart file

Please add translations.g.dart in the project.

Those files are generated by the compiler, you must run the following commands in the root of the project:
dart run slang build
dart run build_runner build

Then you can run the project with no errors


return a value from an event listener

is there any way i can return a value from the listener?
My listener:
Listener.method = async () => {  // code return true }
let e = Event.emit('new::listener')
console.log(e) // undefined

Hey @metronetwork! 👋
This is more a question than an issue with the framework itself.
Please use the forum or the Discord Server for this kind of request.


assigning different containers to the same backend through marathon

According to the docs it states (in the marathon backend) that you can add labels to override the default behaviour -
traefik.backend=foo: assign the application to foo backend

from reading this it reads to me if I add a label to an app that specifies another services backend it would get added there. This would allow you to do a kind of A/B testing while you add an app to another backend temporarily (which would take a % of traffic)
I've tried this using the following marathon.json snippets
start app 1 with  id:nginx
start app 2 with id:nginx-v2
in nginx-v2 JSON file add the following label -
  "labels": {
     "traefik.backend": "backend-nginx"
  },

Instead of adding to the first nginx app backend, it goes and creates a whole new frontend and backend for it. Which means I have 2 apps on 2 different URLs (nginx.domain and nginx-v2.domain)
This looks like because here https://github.com/emilevauge/traefik/blob/master/templates/marathon.tmpl it interpolates the ID to form the template.
Question is then, are the docs wrong or out of date? Or should this be actually working?
If we look in the docker template, it actually looks up the backend via getBackend -
https://github.com/emilevauge/traefik/blob/master/templates/docker.tmpl
but getBackend is not implemented in the marathon plugin.

I'll have a crack at providing a fix for the marathon plugin to use getBackend

Hi @tayzlor, the doc was wrong on that point (copy/paste from Docker provider I think).
This behavior was intended as I thought it would not be required in Marathon.
But if you need it, I have no problem to add it :)

PR for this in #171


hc-159 mma to ama migration task for the test vms under xwc sub

https://dsdmoj.atlassian.net/browse/HC-1159
Code is to create new dcr called dcr-changetracking,
configure change tracking and inventory on following three vms to use newly created dcr dcr-changetracking with AMA.
vmxwctestca01
vmxwctestca02
vmxwctestdm01

Environment: dev. Security Scan of Stage: dev has failed a IaC security scan, Please look at https://dev.azure.com/MoJ-OFFICIAL/Velocity-Landing-Zone/_build/results?buildId=66426&view=ms.vss-test-web.build-test-results-tab

Environment: dev. Security Scan of Stage: dev has failed a IaC security scan, Please look at https://dev.azure.com/MoJ-OFFICIAL/Velocity-Landing-Zone/_build/results?buildId=66431&view=ms.vss-test-web.build-test-results-tab


Public key bin file

What's https://github.com/KhushrajRathod/repl.deploy/blob/main/daemon/src/static/public_key.bin for?

Every request sent out from the hosted version of the repl.deploy server is signed with a private key, which the daemon then verifies before pulling from github and relaunching the app. This is to prevent random people from pinging your endpoint and effectively getting your repl to restart over and over without any code changes.
If you want to self host the repl.deploy server, there are instructions to make your own public key bin file from an ssh keypair here

But why is that file in the tree here on github?

Its included as part of the build process & bundled with the daemon


Infinite sell forex loop 'fix'

fixed 'infinity' loop of selling forex by increasing time before triggering next attempt

/lgtm

/test

/test pull-banka-1-backend-fetching-service-test
/test pull-banka-1-backend-market-service-test
/test pull-banka-1-backend-user-service-test

/test pull-banka-1-backend-fetching-service-test
/test pull-banka-1-backend-market-service-test
/test pull-banka-1-backend-user-service-test

/test pull-banka-1-backend-market-service-test


TinaMarkdown doesn't use alt tags from markdown.

When using TinaMarkdown alt text isn't inserted into the image tag even if it is included:
Example
![example image](/img/example.jpg)
returns
<a src="/img/example.jpg")
We should include the alt text for images when supplied.

Not passing alt text to  elements when using TinaMarkdown is still a bug and in my opinion shouldn't have been marked as wontfix.
I believe I've tracked down at least half of the cause - line 269 in packages/tinacms/src/rich-text/index.tsx is:
return

It's attempting to put the caption field as alt text, rather than the alt text field.
I've been able to get around this locally in two ways, either:
a) Use a markdown image title, which gets pulled through as the caption and then is set as alt text:
![Alt that doesn't work](/path/to/img.jpg "image title that's set as alt text")

I don't like this solution, because it's generally not how alt text is done in markdown, as far as I've seen isn't documented anywhere on the Tina Docs, and feels fragile if/when this alt text issue is "fixed". It is simple though.
b) By changing that (via line 153 in /node_modules/tinacms/dist/rich-text/index.js) to:
return

My thought here is that if either of those are set, it will use them for the alt text of the image. Still slightly confusing, but as far as I can tell it's doesn't really break anything in my Tina projects, and wouldn't in any others either.
Unfortunately with that "fix", I see what I believe is a related console error in the admin view, because of the alt text in my markdown confusing Tinacms' inner workings somehow:
Warning: Extra attributes from the server: alt
img
[...]

Hopefully at least one of these suggestions helps out anyone who stumbles across this issue after having the same problem themselves!

Almost 3 months on and this seems to still be a major accessibility / TinaCMS UX issue.
As a bit of extra info, it's not just an issue when editing markdown files, but when using the editor as well, the image Alt field doesn't do anything, and the Caption field sets the alt attribute of the  element.

I patched the code so that alt tags work.
You can use
{
  "dependencies": {
    "@tinacms/datalayer": <EMAIL_ADDRESS>    "next-tinacms-s3": "https://github.com/EthanShoeDev/tinacms/raw/patched-version/packages/next-tinacms-s3/next-tinacms-s3-4.0.0.tgz",
    "tinacms": "https://github.com/EthanShoeDev/tinacms/raw/patched-version/packages/tinacms/tinacms-2.1.0.tgz",
    "tinacms-authjs": "https://github.com/EthanShoeDev/tinacms/raw/patched-version/packages/tinacms-authjs/tinacms-authjs-4.0.0.tgz",
    "tinacms-gitprovider-github": "https://github.com/EthanShoeDev/tinacms/raw/patched-version/packages/tinacms-gitprovider-github/tinacms-gitprovider-github-1.0.10.tgz",
    "@tinacms/cli": <EMAIL_ADDRESS>  }
}

To use the patched versions.
You may have to use npm i --legacy-peer-deps


builtins.AttributeError: 'NoneType' object has no attribute 'timestep_limit'？？

I encountered the same issue. Have you solved it yet?

This looks like a problem with Gym. Can you give me more details about the command you are running and your version of Gym?

Thx your reply. I have solved this problem,it is surely because of the gym version
------------------ 原始邮件 ------------------
发件人: "Tristan<EMAIL_ADDRESS>发送时间: 2019年11月6日(星期三) 晚上9:08
收件人<EMAIL_ADDRESS>抄送: "461791315"<461791315<EMAIL_ADDRESS>主题: Re: [tristandeleu/pytorch-maml-rl] builtins.AttributeError: 'NoneType' object has no attribute 'timestep_limit'？？ (#37)
This looks like a problem with Gym. Can you give me more details about the command you are running and your version of Gym?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Fix Table overflowing List bug

Jira
https://pegadigitalit.atlassian.net/browse/ACD-17
Summary
Fixes bug where Table inside a List is not properly responsive.
Details
Bug is caused by the List being set to display flex. This allows the Table to overflow the container and the horizontal scroll bar on the Table never kicks in.
After setting List to block, I noticed the negative margin used on list was collapsing the margin around the List. For example, if you put a List inside a Stack, the space provided by the Stack collapses. This I fixed with a pseudo element clearfix.
How to test

Review files changed.
Review List demos, especially "display" and "spacing", and check for any regressions.
Copy this demo code into PL and verify:

Table is responsive inside the List
There is proper space between each Stack

Test 1: Table in List is responsive

{% set table %}
  {% include<EMAIL_ADDRESS>with {
    rows: [
      {
        cells: [
          content,
          content,
          content,
        ]
      },
      {
        cells: [
          content,
          content,
          content,
        ]
      },
      {
        cells: [
          content,
          content,
          content,
        ]
      }
    ],
  } only %}
{% endset %}

{% include<EMAIL_ADDRESS>with {
  items: [
    table,
    table,
    table,
  ],
  spacing: "large"
} only %}

Test 2: There is space between Stack components

{% set content = "Lorem ipsum dolor, long link: https://www.pega.com/insights/resources/royal-bank-scotland-delivering-personalization-scale" %}

{% set list %}
  {% include<EMAIL_ADDRESS>with {
    items: [
      content,
      content,
      content,
    ],
    spacing: "large"
  } only %}
{% endset %}

{% include<EMAIL_ADDRESS>with {
  content: list,
  spacing: "medium"
} only %}
{% include<EMAIL_ADDRESS>with {
  content: list,
  spacing: "medium"
} only %}
{% include<EMAIL_ADDRESS>with {
  content: list,
  spacing: "medium"
} only %}

@remydenton this is the commit you want for v2.22.2: https://github.com/boltdesignsystem/bolt/commit/1f3be35dea215da5f35f44b6617ac38f4fad4511


Disable keyboard input while configuration menu is open.

It's possible to type into the ofxDatGui slider values, but when doing so, keys presses also trigger recording of training data, etc.

Related to #347.

This is fixed per #347.
Note: you can still exit the GUI by pressing ESC. I am not sure if the intended behavior of ESC here should be "close the configuration panel".

ESC should close the configuration panel, not the application.


First draft of creating advanced tables w tanstack

Highlighted the benefits of using Tanstack table
Included a section on prerequisites
Added code snippets on how to set up a table with included markdown table example.

@vyknight I've made some changes just like you've requested, please take another look when you have the time

Looks pretty good, I'll merge this in.


plutus-tx: deal with unpackCStringFoldr#

There are so many ways to make string literals!
This one I think is something of an artifact of the way we use INLINABLE, but this at least deals with it a bit better than having to turn off rewrite rules...
Few minor refactorings and a fix too.

Just going to merge this, I don't think it's worth anyone reviewing this particular hack.


ENH: Enabling (subset) of notebook execution for testing and rendering purposes

We should run notebooks with the exception of the slow ones, rather than not running any of them.

@connolly - for classroom usage, would you rather have empty notebooks, or executed ones?
(for the website rendering we should have the executed versions, but in the repo we could have empty ones that we run through CI to generate the website (and to test that they still run)).
(With the exception of the chapter9 DL example, I expect all the notebooks to run reasonably fast for CI purposes if needed)


Potential bug in the value of i_stuck?

https://github.com/autonomousvision/transfuser/blob/22b3ccdb7e806b42c9be2aa476b71546e8ec3620/team_code_autopilot/autopilot.py#L726-L745
Should this line i_stuck = i be put in the following for-loop? like:
for id, traffic_participant in nearby_vehicles.items():
    i_stuck = i
    if self.render_bev==False and self.junction==False and i > number_of_future_frames_no_junction:
            break
    if id in tmp_stucked_vehicle_id:
        i_stuck = 0

If not, can someone please explain the reason to change the number of future time frame being checked to 0 for all remaining vehicles once any vehicle is found stuck?

Seems like a bug yes.
You can check if it makes a difference to the DS of the expert.

Came around to test it. Didn't seem to have a significant impact on performance. I uploaded the fix.


Add Open Source Jobs

https://github.com/t9tio/open-source-jobs#readme
It is a list of open source projects offering jobs, might be helpful for people who want to find a job contribute to open source
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

[x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
[ ] You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
[x] You have read and understood the instructions for creating a list.
[x] This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

[x] Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

[x] Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

[x] Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
[x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
[x] Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
[x] Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

[x] It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
[x] The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

[ ] The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

[x] Non-generated Markdown file in a GitHub repo.
[x] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
[x] Not a duplicate. Please search for existing submissions.
[x] Only has awesome items. Awesome lists are curations of the best, not everything.
[x] Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

[x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
[x] Includes the Awesome badge.

[x] Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

[x] Should link back to this list.

[x] Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

[x] Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.
To verify that you've read all the guidelines, please add comment with just the word unicorn.

[x] Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

[x] Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

[x] Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
[x] Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

About the name, I don't put an "awesome" in the beginning as the repo has been there for a while, I am afraid changing the name makes it harder for people to find it.  Also, I find some repos in the list did not begin with "awesome" too. So I guess it might be fine.

About awesome-lint

I resolved most of the problems, expect these two, but these two URLs are actually accessible. Not sure it is the network issue on my computer

Title should be title capital letters beginning each word that is not a preposition with spaces not dashes.
The majority of the README.md does not appear to be a list. I think having the documentation of the service somewhere other than the awesome list seems more in line with the mission.

@eselkin thanks for your review,

the title has been updated: https://github.com/t9tio/open-source-jobs/commit/e78f7c5fbbc4836bc80131d9477d97f8c4369cac
The README.md is a list, but in a table format. That is because it looks better in that style

I agree about the table, I meant the sections after the table.

This is a great idea for a list! I have a few things to suggest:

Add "awesome" to the beginning of the repo name. I understand you worry it could make your repo harder to find, but GitHub actually does a great job of preventing this problem. If you rename your repo, then when users attempt to go to the old URL, it will immediately redirect them to the updated URL. Here's GitHub's article on renaming a repository for more information.
The first two sentences in the readme are: "A list of Open Source projects offering jobs. For who want to work on open source and get paid." I think the second sentence could be rephrased a little. Maybe something like "This is useful for anyone who wants to get paid to work on open source projects." Up to you though. If you do keep it the way it is, "For who want" should be "For whoever wants".
Consider adding more GitHub topics if you can think of some other relevant ones. Maybe "open source" or "jobs" etc.
Maybe add a section in the contents on your readme for contributing and link to the contributing file
Above the contents section, you have "Filter the orgs, suggest a new org, post a new job" in a list. I think it would make more sense to move that list underneath the Repos section but above the table of repos.

Let me know if you have any questions about what I suggested. Nice work finding all those open source jobs!

I think the awesome list itself should be a different repo without the entire code and released under some license like CC0 if possible.
While the table format may look good, it doesn't fit the requirements.
You haven't read the guidelines fully as it's missing a requirement in your PR and I can't point it out as it's a requirement to make sure you've gone through everything properly.

@timqian Bump

Make sure to add a comment to this pull request with the word unicorn as indicated by the guidelines to let us know you've read everything


Remove redundancies in utils.BRMatrix

Inspecting the BRMatrix struct present in types.go, we find a lot of redundancies in the form of route's URI string used multiple times in a nested fashion, we instead could work on a more compact and precise data structure for the same. This can be solved as and when we migrate to a new TSDB.

I want to work on this issue @aquibbaig . Brief explaination of the possible approach for this issue will be helpfull. @Harkishen-Singh

@Tushar3099 if you see the types.go, there are several structs that use repeated fields. The main aim here is to make them smaller and have a base struct which will be implemented in other structs and hence reducing redundancy.
Example: Ping and PingResp both have min, mean, max, mdev. So, PingResp can be rewritten as:
type PingResp struct {
        Ping
    	NormalizedTime int64   `json:"NormalizedTime"`
	Timestamp      string  `json:"Timestamp"`
	Relative       int     `json:"relative"`
}

But do make sure that base structs (which are being used to extend) have json implementations (like the current Ping does not have).

@Harkishen-Singh Thanks for the detailed explanation. I will try my best to refactor all the structs.

@Harkishen-Singh, I have solved the simpler redundancies like in Ping and PingResp, FloodPing and FloodPingResp, Response and ResponseResp.
But as @aquibbaig said the redundancy of routes URI in BRMatrix is nested, BRMatrix has a structure as :
type BRMatrix struct {
	FullURL                  string
	Route                    parser.Route
	PingChain, JitterChain   *tsdb.Chain
	FPingChain, MonitorChain *tsdb.Chain
	Metrics                  *EndpointMetrics
}

Here FullURL has the route's URI, also the Route struct has the URL field :
type Route struct {
	Method string    `yaml:"method"`
	URL    string    `yaml:"url"`
	Header []Headers `yaml:"headers"`
	Params []Params  `yaml:"params"`
	Body   []Body    `yaml:"body"`
	Labels []string  `yaml:"labels"`
}

and Chain struct also has a Route field
type Chain struct {
	Path               string
	Name               string
	Route              string
	Chain              []Block
	LengthElements     int
	containsNewBlocks  bool
	inActiveIterations uint32
	mux                sync.Mutex
}

To remove this type of redundancy(if possible) the whole data structure has to be changed because all the redundant route data structs have their own implementation.
What should be the right approach?

@Tushar3099 Not sure if it is the right approach but if it trims down redundancies by any means, it will surely be helpful to the project. If entirely changing the type of the structs helps, please go ahead.

@aquibbaig @Harkishen-Singh, as I see, the structs Chain, Route, BRMatrix are widely used all over the code, and changing those data structs will then affect all the code and logic, and this will take some time. Shall I make a PR up to I have refactored other structs till then?

@Harkishen-Singh Please give your views on this:

@Harkishen-Singh, I have solved the simpler redundancies like in Ping and PingResp, FloodPing and FloodPingResp, Response and ResponseResp.
But as @aquibbaig said the redundancy of routes URI in BRMatrix is nested, BRMatrix has a structure as :
type BRMatrix struct {
	FullURL                  string
	Route                    parser.Route
	PingChain, JitterChain   *tsdb.Chain
	FPingChain, MonitorChain *tsdb.Chain
	Metrics                  *EndpointMetrics
}

Here FullURL has the route's URI, also the Route struct has the URL field :
type Route struct {
	Method string    `yaml:"method"`
	URL    string    `yaml:"url"`
	Header []Headers `yaml:"headers"`
	Params []Params  `yaml:"params"`
	Body   []Body    `yaml:"body"`
	Labels []string  `yaml:"labels"`
}

and Chain struct also has a Route field
type Chain struct {
	Path               string
	Name               string
	Route              string
	Chain              []Block
	LengthElements     int
	containsNewBlocks  bool
	inActiveIterations uint32
	mux                sync.Mutex
}

To remove this type of redundancy(if possible) the whole data structure has to be changed because all the redundant route data structs have their own implementation.
What should be the right approach?

Is the value on fullurl and route struct's url, the same?

@Harkishen-Singh, In this snippet from main.go line 141, we are assigning the route's URL to fullURL, so I assumed that routes URL field and BRMatrix fullURL field have the same value. Please correct me if I misunderstood.
	matrix[hash] = &utils.BRMatrix{
		FullURL:      r.URL,
		Route:        r,
		PingChain:    targetMachineCalc[uHash].Ping,
		JitterChain:  targetMachineCalc[uHash].Jitter,
		FPingChain:   targetMachineCalc[uHash].FPing,
		MonitorChain: tsdb.NewChain(pathMonitor).Init(),
		Metrics:      endpointMetrics,
	}

Then that should be workable without the full url field. You can remove the full url field then and that should be good to go.

Thanks, I will then make the prescribed changes and make a PR ASAP.

@Harkishen-Singh @aquibbaig I think the issue is resolved so that we can close this issue.


epilepsy classifications by genetic/chromosomal abnormalities

These diseases are classified by genetic/chromosomal abnormalities, but these are diseases that have epilepsy as a feature, as far as I can tell.
@cmungall - any advice on how to handle these?
I may not be interpreting this correctly- in the coggle diagram, there are classifications of genetic epilepsies, and the subclasses are chromosomal abnormalities and gene abnormalities. In this website, the diseases listed below are chromosomal abnormalities, and there is a huge list of genes. I'm not sure I understand how this should be modeled.

Label
MONDO ID

15q13.3 MICRODELETION SYNDROME
MONDO_0012774

18q- SYNDROME
MONDO_0011147

INV-DUP (15) OR IDIC (15)
MONDO_0012081

DEL 1p36
MONDO_0011929

ANGELMAN SYNDROME
MONDO_0007113

DOWN SYNDROME (TRISOMY 21)
MONDO_0008608

KLEINFELTERS SYNDROME (XXY)
MONDO_0006823

MILLER DIEKER SYNDROME (DEL 17p)
MONDO_0009532

PALLISTER KILLIAN SYNDROME (TETRASOMY 12p)
MONDO_0011146

RING 14 (r14) SYNDROME
MONDO_0014708

RING 20 (r20) SYNDROME
MONDO_0015436

TRISOMY 12p
MONDO_0015723

WOLF-HIRSCHHORN SYNDROME (DEL 4p)
MONDO_0008684

classify under MONDO_0015652
add source on the subclassOf axiom


Assigned region

What determines "closest to you" for the assignment of a Cloud Shell region? I have a customer in Japan reporting that their storage account was created in West US.
Is it possible to change the assignment to another of the supported regions?

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

ID: ecd5d368-8d1c-f984-4922-ab4c7ae14db5
Version Independent ID: dbb6bc4c-87f4-18a0-f6e9-f9f48be1f289
Content: Persist files for Bash in Azure Cloud Shell
Content Source: articles/cloud-shell/persisting-shell-storage.md
Service: azure
GitHub Login: @jluk
Microsoft Alias: juluk

@dcbrown16 the automatic SA region is determined by Azure Traffic Manager, sometimes it may select the region not geographically closest but at the moment of request was the fastest option.
They can attach a storage account of their choosing by using the "Advanced" onboarding flow which lets you mount existing SA in any supported CS region. Hope this helps!

@dcbrown16 We will now close this issue. If there are further questions regarding this matter, please reply to @femsulu and we will gladly continue the discussion.

@dcbrown16 simply run clouddrive dismount which will remove the SA association. On next launch you should be prompted with the onboarding dialogs again.

Run that cmd from the bash prompt

Great, thanks @jluk!


Monix support

I suppose this is also supported via #7 :)
(though anyone is welcome to making a monix specific module)

I don't think https://github.com/kitlangton/parallel-for/pull/7 solves this in it's current state -- I made it concretely for IO and not using the type classes. I can make another PR using the type classes to allow this to be used with e.g. Monix :) but I think this should be revived.

Sounds good! Tis opened :)

I did some experimenting, and the macro fails in various ways when you are coding against the typeclass. I was unable to figure this out, unfortunately.
It seems to me, that the macro relies on having the concrete type somewhere, somehow.


Should free jNode when not needed

This fixes the JNI table overflow issue for models which have large hierarchy of nodes. Models exported as FBX from DAZ studio has very large hierarchy, so they can be used to review this pull request.
GearVRf-DCO-1.0-Signed-off-by:
Deepak Rawat<EMAIL_ADDRESS>

Looks good. Will merge in the afternoon if there are no comments.
@deepakrawat22 Do you think this fixes https://github.com/Samsung/GearVRf/issues/734 or are there other issues with DAZ-exported models?

@liaxim The model file I am using still has issue with bone index out of bound problem. I am looking separately into that. So for now we can keep #734 open.

@roshanch told me the bone index out of bound is a known problem and for now the limit is 60. I tried another fbx file from DAZ studio which does not have any bones and it worked. I exported to FBX 2012 ASCII with texture in a folder.


Update typedoc

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

v2.7.2
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat/add render cmd and update build cmd to save collection to build cache

Depends on PR #37
Closes #32

[X] Docs updated
[X] Requires an update to the Getting Started guide
[X] Test done

What this change does?
Adds the render command to replace the functionality of what was the build command was
Replace the build command to provide a workflow similar to the container builder

Build the artifact ( It is saved to a build cache)
Push the artifact to a remote location
Optionally, pull the artifact (unpacks the files to an output directory but also pulls the artifact into the cache)

What does this PR not do?
Provide a way to prune the cache. It currently must be deleted by the user.

Works great. The only issues that I experienced were the oras bug and I would prefer the content to only be pulled to the cache by default. Then the content could be optionally output to the target directory with the --directory flag.
wdyt @jpower432 ?

@afflom Perhaps we can work that into a subsequent PR. If we pull into the cache only, the user has no way to retrieve the artifact from the cache with the client. If we could create a subcommand that allows the user to interact with the cache (e.g inspect or export), I would be more inclined to have this functionality on this PR.
ORAS bug fix is in PR #48

@sabre1041, This worked for me, over to you for final review and merge.

@afflom Can you please do a quick test post-rebase and confirm the oras bug is resolved?

Works with the oras version bump.


CSS Timeline

Project title
Timeline
Project Description
Responsive timeline using html and css
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS

/assign


[draft][network] simple on-chain discovery via state-sync reconfig

Motivation
Draft work on  https://github.com/libra/libra/issues/3925
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

@davidiw This is very much a draft PR trying to work out the structure for funneling updates from statesync into the network.   This reflects my current mental model and mappings.
Key pieces at the moment:

Very basic NetworkConfigListener added
removing the deprecated code from epoch_manager
sketching out the new subscription registration patterns

Blocking/Unresolved issues

Is this structurally along the lines of what you are thinking or have I jumped the rails already?
StateSync currently does not expose FullNodeNetworks as far as I can tell
StateSync currently does not expose NodeAddress changes as far as I can tell
There are probably a number of race conditions around registration, process starting, etc. that need to be plumed through
Are there tensions around StateSync using the same network ConnectivityManager which we are attempting to update based on StateSync provided information?
Are there timing concerns for consensus relative to the network and the LivenessStorage updates?

Coming along nicely!

the ValidatorInfo code is pretty rough and needs some TLC.

+10000.  there are a couple of pieces that are confusing me here:

Why is the full node configuration a part of ValidatorInfo?  My understanding is that a node does not need to be a part of a validator network (or to be a validator) in order to be a member of a full node network?

How are different full node networks differentiated?  My understanding is that there are an unbounded number of full node networks, each with their own NetworkBuilder and ConnectionManager, which are configured independently.

Are all full node networks maintained in the on chain config database?  Some?  Exactly 1 consisting only of validators?

The sensible way to proceed (and amount of technical debt to incur) seems to depend heavily on the answer to the last question.

the ValidatorInfo code is pretty rough and needs some TLC.

+10000. there are a couple of pieces that are confusing me here:

Why is the full node configuration a part of ValidatorInfo?  My understanding is that a node does not need to be a part of a validator network (or to be a validator) in order to be a member of a full node network?
We had planned to have two different data sets, but it added a lot of complexity to code when we only intended to ever host a single fullnode network and in the our initial release would be 1:1 with the validator network.
How are different full node networks differentiated?  My understanding is that there are an unbounded number of full node networks, each with their own NetworkBuilder and ConnectionManager, which are configured independently.
That's possible. In reality, there are likely to be 3 networks:

Validator all-to-all
(Validator)-fullnode-to-validator
(Public)-fullnode-to-(validator)-fullnode
At some point in time I should write up a brief proposal that describes what I envision as one potential long term vision of producing a self-organizing Libra PFN, but not today...

Are all full node networks maintained in the on chain config database?  Some?  Exactly 1 consisting only of validators?
No, probably alluded to this many times. Onchain is a trusted set of fullnodes, they somehow have been trusted enough by the validators to be added to the blockchain. More specifically, they are the validators' fullnodes.

The sensible way to proceed (and amount of technical debt to incur) seems to depend heavily on the answer to the last question.

No tech debt, just not the problem we can reasonably hope to solve in the short term.

How are different full node networks differentiated?  My understanding is that there are an unbounded number of full node networks, each with their own NetworkBuilder and ConnectionManager, which are configured independently.
That's possible. In reality, there are likely to be 3 networks:

Validator all-to-all
(Validator)-fullnode-to-validator
(Public)-fullnode-to-(validator)-fullnode
At some point in time I should write up a brief proposal that describes what I envision as one potential long term vision of producing a self-organizing Libra PFN, but not today...

3 networks or 3 types of networks?    I don't understand the descriptions above and I was actually asking a slightly simpler question.
Looking at main_node.rs, there are potentially multiple full_node networks instantiated each with its own NetworkBuilder and each NetworkBuilder has its own [ConnectivityManager] (https://github.com/libra/libra/blob/9bae2e911c653935a23862f31586f756b58ff675/libra-node/src/main_node.rs#L142).   My question is how theses different networks are differentiated?  When a config change is registered, which of the networks changes?

Validator all-to-all
(Validator)-fullnode-to-validator
(Public)-fullnode-to-(validator)-fullnode
At some point in time I should write up a brief proposal that describes what I envision as one potential long term vision of producing a self-organizing Libra PFN, but not today...

Pushing on the three types of networks here and their use cases,

validator all-to-all is the network that supports consensus and the mempool?
for the other two network types, what does it mean for the network to be directional from the fullnode to the validator (or validator to fullnode)?

From experience with the config-builder and associated documentation, my expectation  was that there would be three types of networks:

the validator-to-validator network for consensus
a public facing full node network which mirrors the database for public consumption (and buffers the core network from most interactions)
a collection of privately run full node networks which "hang" off of members of one of the first two networks.

That understanding is driven partially by explicit documentation---points 1 and 3 are mostly implied by Full Node Basics---and my own intuitions---point 2.

How are different full node networks differentiated?  My understanding is that there are an unbounded number of full node networks, each with their own NetworkBuilder and ConnectionManager, which are configured independently.
That's possible. In reality, there are likely to be 3 networks:

Validator all-to-all
(Validator)-fullnode-to-validator
(Public)-fullnode-to-(validator)-fullnode
At some point in time I should write up a brief proposal that describes what I envision as one potential long term vision of producing a self-organizing Libra PFN, but not today...

3 networks or 3 types of networks? I don't understand the descriptions above and I was actually asking a slightly simpler question.
Looking at main_node.rs, there are potentially multiple full_node networks instantiated each with its own NetworkBuilder and each NetworkBuilder has its own ConnectivityManager. My question is how theses different networks are differentiated? When a config change is registered, which of the networks changes?

This really doesn't answer the question directly but here's a direction we're going to help disambiguate networks: https://github.com/libra/libra/issues/4012
In general, the only two networks that would be affected by config changes are:

validator to validator (or validator in the issue)
public to validator full node (or public in the issue)

Personally, I would focus on nailing down the validator network first and foremost and not care about the others in this PR. That way we can get this landed and clean up the rest as things come together.

In general, the only two networks that would be affected by config changes are:

validator to validator (or validator in the issue)
public to validator full node (or public in the issue)

I would expect every network to be impacted by config changes, though only those two would be impacted by StateSync triggered config changes.


[Extensibility-Enhancement] table 55 "Invoice Posting Buffer"

Please make function PadField global
procedure PadField(TextField: Text; MaxLength: Integer): Text

It was already requested: #14122


Fix memory leak in waitDevice

📑 Description

Closes #
✅ Checks

[X] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[X] All the tests have passed

ℹ Additional Information

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 11 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.6%) to 96.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.6%

Covered Lines:
265

Relevant Lines:
269

💛  - Coveralls

@gmacario waiting for your review!

Thanks @Raffone17 for your contribution.
I am not an expert on Node.js but I believe this PR could be proposed upstream.
Have you already had a chance of discussing it with @chrvadala?

Have you already had a chance of discussing it with @chrvadala?

Ping @Raffone17

@Raffone17 as agreed during today meeting with @chrvadala please submit the Pull Request upstream to https://github.com/arolgroup/node-ble


UncaughtThrowError: uncaught throw {:recursive_key=>true, 19667120=>true} from visitors/reduce.rb:13

I am getting above error from visitors/reduce.rb:13, below I have attached full backtrace of the error. The issue is occurring so randomly that, the working query in production suddenly starts breaking and starts throwing error and in the next moment it starts working fine. On tracking origin of the error, every error tracks down to line number 13 of visitors/reduce.rb file inside the gem. The UncaughtThrowError is thrown only when an exception is thrown without catch block. I tried to find whether there is any throw statement in arel gem but I could not get any.
I was also able to get parameters of the visit method at the time the error is being raised. I have also pasted them below. By looking at the arguments it seems like query was also not built completely. The error was raised while building the query itself. That partly built query is one of the query for which I am getting error. I am getting this error for any random query in the application.

Is there a way to reproduce this?
You said, you pasted the params for the query, I don't see them. Can you share more about the query itself.

@vipulnsward Thank you for responding.
I have updated the description and added the value of collector and dispatch[object.class] at the time of error. They are not exactly the parameters of visit method but they are the arguments of method call at line number 13 in which I am getting the error. The query is being fired using ActiveRecord as below:
For example: User.where(id: id, type: user_type)

@bhaskarshankarling https://stackoverflow.com/questions/37693847/rails-app-crashed-with-argumenterror-uncaught-throw-recursive-key-true Is this related ?

Per #523, Arel development is moving to rails/rails.
If this issue is still relevant, please consider reopening it over there. (Note that the Rails repository does not accept feature request issues, and requires reproduction steps that rely on Active Record's documented API.)


add an option to plot network in other shapes [a new pull request ]

start from a clean fork and create a pull request again.

updated of PR #669, from issue #663


Bootstrap call error

I do not think that this is causing any major problems, it just bangs up the style for source code (Prism). I found this issue that seems to be related:
https://github.com/gatsbyjs/gatsby/issues/1043

This error is not happening anymore. I would suspect it was a bug relating to GatsbyJS that has since been fixed.


I have added sleep in line 72

It will retain the text on terminal for 3 secs so as to let the user read the echoed text before clearig :)

@imabhi1906 Thank you for supporting!


libxml2: don't propagate Python bindings

Motivation for this change
Extracted from #77149. Quoting myself there:

I suspect there will be packages that relied on the libxml2 Python
bindings being propagated, but don't know how I'd identify them.  The
libxml2 change is too big for nix-review to handle.  Any ideas?

Things done

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

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

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

This has existed since about 2015, 38313d5d877fc421d1381971051107e4b03dc40d, which was when multiple outputs was introduced (https://github.com/NixOS/nixpkgs/pull/7701).
Nowadays the Python bindings are in python-packages.nix and packages should use those. Not all of them work that way though.

Okay then. Here we go!
I guess the staging process would pick up if this did cause catastrophic breakage anyway.


Update the Government association for Document during publish

The associated Government should be based on the first_public_at date,
which can be edited as part of edition metadata, so the associated
Government needs to be updated when the edition is.
This is done after the Edition itself has been saved, in case the
edition update fails.
This also removes the old implementation/tests, which set the
Government once (and only once) during the first publish

:+1: LGTM


Suggestion: implement "implements" operator

Hello,
I would like to ask if it would be possible to implement the "implements" operator for run-time returning true or false based on evaluation if object implements an interface.
I can imagine there will be a lot of edge cases but for simple class - implements  statements it would be simply doable.
Lets take a look on the following example:
interface ICredentials {
   username: string;
   password: string;
}

class A implements ICredentials {
   username: string;
   password: string;
   ...
}

class B {
   ...
}

let a: A = new A();
let b: B = new B();

# true
console.log(A implements ICredentials);
console.log(a implements ICredentials);

# false
console.log(B implements ICredentials);
console.log(b implements ICredentials);

for such cases we need to write something like:
   function implementsICredentials(obj: any): boolean {
      return
         obj.hasOwnProperty("username") &&
         obj.hasOwnProperty("password");
   }

It is quiet a lot of code to be written manually if we want to test multiple interfaces. I can imagine the compiler could generate such functions for us.
Thanks for response.
Regards,
Franta

Duplicate #5896, #1549, etc.
You might want to try https://www.npmjs.com/package/dtsgenerator or similar tools

Yep, but... you know... implements would be nicer. I get you don't want to add so much additional code.

This also just isn't doable.
interface I {
	m(x: number): number;
}

function f(x: {}): x is I {
	...
}

There's no way we can fill in the body of that function for you automatically.
Suppose we try typeof f.m(0) === "number".
If it does return a number: how do we know it always does?
If it throws an exception: How do we know it isn't just a problem with the number 0?
Also, we would be doing an arbitrary amount of work.

I am sorry, but i don't understand what you mean by this.
Where do you say that x implements something?
in my case, i just wanted to know if members defined by the interface exists on the object.

Just because an object has all the same keys doesn't mean that it actually implements the interface.

Thats true :) But there is no another option, how to check it right? If we will not take reflection into account.

Why do you want this feature though? If you don't trust an object, no amount of checking will suffice. If you do trust an object, you should give it an O(1) way of identifying itself as a member of an interface, as in:
interface Foo {
    __fooBrand: true;
}

class C implements Foo {
    get __fooBrand(): true { return true; }
}

function isFoo(obj: {}): obj is Foo {
    return !!(obj as Foo).__fooBrand;
}

Its complicated. I am using it together with generics so I am good at compile time but I wanted to make sure the same at runtime.
Nice workaround, thanks for recommendation! I'll try to implement it like that.

@novakf
I really think @andy-ms cuts right to the heart of the matter when he asks

Why would you want that, though? If you don't trust an object, no amount of checking will suffice. If you do trust an object, you should give it an O(1) way of identifying itself as a member of the interface, as in:

This is so true that even cases like
class Credentials) { }

class A extends Credentials { } // prototype chain will preserve basic heritage.

const a = new A();

console.log(a instanceof Credentials); // true

It does guarantee anything at all at runtime
class Credentials { }

class A extends Credentials { } // prototype chain will preserve basic heritage.

const credentials = {
  __proto__: Credentials.prototype
};

console.log(credentials instanceof Credentials); // true


Update A Tour of Cybersec notebook features.ipynb

Update nbwidgets.QueryTime Arg from "unit" to "units"

/azpipelines run


List Comprehension example of syntax extension.

Many thanks to Kyle Miller who first posted this solution on Zulip, this sample then tests all the list comprehension features of Python now work in Lean.

There is a bit of inconsistent capitalization of "Lean" and "Python"

fixed, thanks.


Nix os dependency

Want to try deadalus, but in the shell script there is nix OS dependency. In the readme I find "NixOS is a GNU/Linux distribution that aims to improve the state of the art in system configuration management. " Why does installer point to a linux distro? This requires more explanation.

@benjyz: Testnet version of Daedalus can be downloaded from https://test.daedaluswallet.io/. Keys for importing wallet with Ada are available here: https://tada.iohk.io/.

Thanks, will try. Still don't understand where the nixOS dependency comes from. Is this for virtualization?

Daedalus is currently shipping with Ada cryptocurrency and full Cardano node. CI builds the installers and bundles the Cardano node with Daedalus. nix is a dependency needed for the Cardano node integration.
Here is a link to Cardano SL repo: https://github.com/input-output-hk/cardano-sl and Cardano documentation: https://cardanodocs.com.


Add initial integration tests

Right now we have some JS unit tests, but no integration tests at all. We should start adding integration tests using @testing-library/react and perhaps packages like @testing-library/user-event

Here's the documentation for React Testing Library:
https://testing-library.com/docs/react-testing-library/intro
https://testing-library.com/docs/react-testing-library/setup
https://testing-library.com/docs/react-testing-library/api
https://testing-library.com/docs/react-testing-library/faq
https://testing-library.com/docs/react-testing-library/cheatsheet
Relevant companion libraries / packages:
https://github.com/testing-library/user-event
https://github.com/testing-library/jest-dom
https://testing-library.com/docs/ecosystem-eslint-plugin-testing-library
https://testing-library.com/docs/ecosystem-eslint-plugin-jest-dom

We should probably change code coverage analysis to

run coverage also for PRs
add back code coverage PR comments

@swissspidy, I tried to construct a simple test that looked like this:
import { renderHook, act } from '@testing-library/react-hooks';

import FrameElement from '../../components/canvas/frameElement';

describe.only('test', () => {
  it('should render a frame element', () => {
    const element = {
      id: '1',
      type: 'text',
    };
    renderHook(() => (<FrameElement element={element} />));
  });
});

And I'm seeing the parse error on one of the icons.

SyntaxError: Unexpected token <
 ● Test suite failed to run
Jest encountered an unexpected token

This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

Here's what you can do:
 • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
 • If you need a custom transformation specify a "transform" option in your config.
 • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/en/configuration.html

Details:

/Users/dvoytenko/DNI/web-stories-wp/assets/src/edit-story/elements/background/icon.svg:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 29 29"><path fill="currentColor" fill-rule="evenodd" d="M18.179 11.0613L19.0124 11.0599C19.929 11.0583 20.6803 11.8071 20.6818 12.7237L20.6958 21.0571C20.6973 21.9737 19.9486 22.725 19.0319 22.7265L9.03192 22.7433C8.11526 22.7448 7.364 21.9961 7.36247 21.0794L7.3485 12.7461C7.34697 11.8294 8.09571 11.0782 9.01238 11.0766L9.84571 11.0752L9.84291 9.40857C9.83906 7.10857 11.7026 5.23878 14.0026 5.23492C16.3026 5.23107 18.1724 7.09461 18.1762 9.3946L18.179 11.0613ZM14.0054 6.90157C12.6221 6.90389 11.5073 8.02242 11.5096 9.40575L11.5124 11.0724L16.5124 11.064L16.5096 9.39737C16.5073 8.01404 15.3888 6.89925 14.0054 6.90157ZM9.02917 21.0766L9.01521 12.7433L19.0152 12.7265L19.0292 21.0599L9.02917 21.0766ZM15.6888 16.8988C15.6903 17.8154 14.9416 18.5667 14.0249 18.5682C13.1083

SyntaxError: Unexpected token <

  23 |  * Internal dependencies
  24 |  */
> 25 | import { ReactComponent as Icon } from './icon.svg';
     | ^
  26 |
  27 | function BackgroundIcon() {
  28 |   const alt = __('Background element', 'web-stories');

  at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:537:17)
  at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:579:25)
  at Object.<anonymous> (assets/src/edit-story/elements/background/icon.js:25:1)

@dvoytenko check out how @barklund fixed this in #383


Update sqlite to latest version 3.41.0

There is a vulnerability reported in versions below sqlite 3.40-
CVE-2022-46908
Please update to latest version sqlite  3.41.0

The linked CVE does not affect this library.  Only the CLI is affected (see https://sqlite.org/src/info/cefc032473ac5ad2 for the CVE fix).

Closing because the latest release (v1.14.22) is bundling SQLite 3.45.1.


Update README for version 1.0.0-beta8

The current version in master is 1.1.0-beta1, not 1.0.0-beta8, so updating the documentation to the current version would probably make the most sense. The filters were changed in 1.1.0-beta1 to support more filter phases, and the documentation was updated to reflect this. Perhaps you could add a note for 1.0.0-beta8 users that the filter names have changed, and link to a previous revision of the readme that explains how to use them.

Not sure if my updates make sense as the 1.1.0-beta1 is not yet present on mvnRespository. Maybe it is better that you refuse my pull request and update the README yourself just with the version number once it is deployed. What do you think?


Fix deprecated setExpiration method

The setExpiration method uses a $ttl param but $expiration was used instead.

Changes Unknown when pulling 9cc4a4334cffac49c9cdaf619ce8f6f3f9420499 on damianopetrungaro:master into ** on frqnck:master**.


name added

Definitely. I am sorry for this mistake will fix it asap!
On Mon, 20 Sep 2021 at 2:46 PM, Tom Schmelzer @.***>
wrote:

@.**** requested changes on this pull request.
please order yourself in alphabetical order
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EddieHubCommunity/hacktoberfest-practice/pull/578#pullrequestreview-758408835,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AROLRHFB3TOKHRPMMB3HFTDUC33WVANCNFSM5ELN54LQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

duplicate with #580