Adding parameterized config option to the donet publish commands

JIRA link (if applicable)
VIH-8168
Change description
parameterizing dot net config options for Debug
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

too old


Add provisioning key expiry date to generateDeviceProvisioningKey

Change-Type: patch
Signed-off-by: Nitish Agarwal<EMAIL_ADDRESS>See: https://jel.ly.fish/product-improvement-provisioning-api-key-management-4c86a2c3-8899-4764-9019-8c9b932e57f5

@balena-ci retest

@balena-ci retest

@nitishagar @balena-ci retest doesn't work here, since appveyor is not part of balena-ci.
You need to open appveyor, login & issue a restart from there. Let me do that for you,

@nitishagar @balena-ci retest doesn't work here, since appveyor is not part of balena-ci. You need to open appveyor, login & issue a restart from there. Let me do that for you,

Thanks @thgreasi. I didn't see any re-run option on appveyor maybe permission issue - checking with @ops.
From the re-run the TEST_ONLY_ON_ENVIRONMENT=browser one passed but the node one failed. Seems intermittent again; but will confirm once permission issue sorted.


Clean up logging

use Err method instead of format strings
use Msg if no format string is used

Can we use constituent upper/lowercases for log messages? Some log messages start with upper, some with lowercase.

Ok 3 people agreed to normalize upper/lower cases, but the PR was merged without fixing it :smile: Should I create an issue to track it?

the "linter explosin" pull do have a linter for that if i remember, ... so this part just has to be picket out and it should lint & you also have the fixes there


refactor: return service_id if present

The code was checking wether the service Id contains a /. If it contained a / it was not returning the service id. Was it intentional? Could you explain me why?

Never mind, I found the test.    is to avoid @Client using a path or url . e.g. @Client("/client")


Oversampling Mitigation

Issue #, if available: N/A
Description of changes: Implemented oversampling mitigation to support creating subsegments without sampling (control sampling decisions at the subsegment level) and an SQS message helper class.
Note: Since it is possible to modify the sampled flag of a subsegment without the need to create a new API, this is the design implemented in the changes below. For instance, to create a new unsampled subsegment and add it to a Lambda facade segment:
    segment = FacadeSegment('facade_segment', 'id', 'id', True)
    subsegment = Subsegment('sampled_subsegment', 'local', segment)
    subsegment.sampled = False
    segment.add_subsegment(subsegment)

Similarly, the begin_subsegment API has been modified to include a default sampling parameter which defaults to True, and can be set to False when creating a new unsampled subsegment.
    segment = xray_recorder.begin_segment('segment')
    subsegment = xray_recorder.begin_subsegment('unsampled_subsegment', sampling=False)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This change has been tested in a Lambda environment using the following Lambda function:
from aws_xray_sdk.core import xray_recorder
from aws_xray_sdk.core.models.subsegment import Subsegment
from aws_xray_sdk.core.utils.sqs_message_helper import SqsMessageHelper
import logging

def lambda_handler(event, context):

    for message in event['Records']:
        if SqsMessageHelper.isSampled(message):
            print('sampled - doing batch work')
            subsegment = xray_recorder.begin_subsegment('sampled_subsegment', sampling=True)

        else:
            print('unsampled - doing batch work')
            subsegment = xray_recorder.begin_subsegment('unsampled_subsegment', sampling=False)

    xray_recorder.end_subsegment()

X-Ray service map when Sampled=1 in AWSTraceHeader:

X-Ray service map when Sampled=0 in AWSTraceHeader:

Can we use the same paradigm of a separate without sampled function instead of passing in a parameter? We want the SDKs to be consistant.

Can we also get a unit test for the emitter?

@carolabadeer I know we decided on this approach in our conversation. But now when I think of it again, I agree with @atshaw43 that we should keep the SDKs consistent. There could be confusion among customers why the a begin_subsegment_without_sampling API exists in other SDKs but not in this.

@carolabadeer I know we decided on this approach in our conversation. But now when I think of it again, I agree with @atshaw43 that we should keep the SDKs consistent. There could be confusion among customers why the a begin_subsegment_without_sampling API exists in other SDKs but not in this.

Updated lambda handler function with the new begin_subsegment_without_sampling API:
def lambda_handler(event, context):

    for message in event['Records']:
        if SqsMessageHelper.isSampled(message):
            print('sampled - doing batch work')
            subsegment = xray_recorder.begin_subsegment('sampled_subsegment')

        else:
            print('unsampled - doing batch work')
            subsegment = xray_recorder.begin_subsegment_without_sampling('unsampled_subsegment')

    xray_recorder.end_subsegment()


gwt-user 2.6 via Gradle

Hello,
Using gradle, gwt-user (v2.6) gets pulled into my classpath, I believe this is from the Universal Analytics dependency. I can exclude it manually, but it creates a nasty conflict when running. It takes a minute to track down.
I was wondering if we could decouple this in the next build? Especially with 2.8 so close!
Thanks,
E

Hi, thanks for your report.
I can force the project to avoid importing gwt-user itself, but the Universal Analytics I can't remove (unless I repackage it inside the project - practice that I don't like).
I'll take a look with Gradle to see what can be done (till today I only used Maven).

Hey Gilberto,
Here's how I have it:
compile ("com.github.gilberto-torrezan:gwt-views:1.3.0"){
exclude group:'com.google.gwt', module: 'gwt-user'
}

That's how I have it in my build file and it works as expected.

Fixed on v.1.3.1.


docs: Adding a couple links to contributing page

SUMMARY

Just adding a few links.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Should be pretty straighforward from the markdown mods, but I can spin up the server and take screenshots if warranted.
TESTING INSTRUCTIONS

Make sure it looks right when merged (it sure should!) but we can roll back if I goofed something up.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@sfirke for review/comments/additions


Uncaught TypeError: Cannot read property 'toLowerCase' of undefined

I have someone that is getting a strange error. I haven't had anyone else run into this issue. Does anyone know what is causing it? Im storing files in localdb with dexie and then upload them with this. Im using Ruby on Rails 6.1 with webpacker.
One other thing is they said they are getting these. Maybe its some setting with their Chrome browser?

VM21:294 Uncaught TypeError: Cannot read property 'toLowerCase' of undefined
    at HTMLDocument.document.createElement (<anonymous>:294:15)
    at HTMLDocument.document.createElement (<anonymous>:292:44)
    at HTMLDocument.document.createElement (<anonymous>:292:44)
    at $.<computed>.<computed>._initTemplates (eval at e.exports (addScript.js:20), <anonymous>:617:53)
    at $.<computed>.<computed>.eval [as _initTemplates] (eval at e.exports (addScript.js:20), <anonymous>:151:31)
    at $.<computed>.<computed>._initSpecialOptions (eval at e.exports (addScript.js:20), <anonymous>:643:12)
    at $.<computed>.<computed>.eval [as _initSpecialOptions] (eval at e.exports (addScript.js:20), <anonymous>:151:31)
    at $.<computed>.<computed>._create (eval at e.exports (addScript.js:20), <anonymous>:1413:12)
    at $.<computed>.<computed>.eval [as _create] (eval at e.exports (addScript.js:20), <anonymous>:151:31)
    at $.<computed>.<computed>._super (eval at e.exports (addScript.js:20), <anonymous>:138:39)
rollbar.min.js:1 jQuery.Deferred exception: Cannot read property 'then' of undefined TypeError: Cannot read property 'then' of undefined
    at File.eval (eval at e.exports (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:5763), <anonymous>:144:56)
    at Function.each (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:3391)
    at $.<computed>.<computed>.process (eval at e.exports (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:5763), <anonymous>:131:11)
    at $.<computed>.<computed>.eval [as process] (eval at e.exports (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:5763), <anonymous>:151:31)
    at HTMLInputElement.eval (eval at e.exports (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:5763), <anonymous>:248:45)
    at Function.each (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:3391)
    at e.fn.init.each (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:1865)
    at e.fn.init.$.fn.<computed> [as fileupload] (eval at e.exports (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:5763), <anonymous>:231:16)
    at $.<computed>.<computed>.eval (eval at e.exports (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:5763), <anonymous>:92:24)
    at f (https://app.iris.fm/packs/js/application-afe787b75da0b5eb5dec.js:2:17738) undefined
e.<computed> @ rollbar.min.js:1

Please see #2190


Guidelines for Using the Simulation Code

Could you provide a detailed guideline or instructions on how to use the simulation code to generate the results mentioned in the paper?
Thank you for your assistance in advance!

Close with commit c1ab9f632369bba789a21c2c1f274384033c20eb


Adding javadoc.

So we can incorporate your pull request, please share the following:

What issue are you addressing with this pull request?
Are you modifying the correct branch? (See CONTRIBUTING.md)
Have you run unit tests? (See CONTRIBUTING.md)
Version of MarkLogic Java Client API (see Readme.txt)
Version of MarkLogic Server (see admin gui on port 8001)
Java version (java -version)
OS and version
What Changed: What happened before this change? What happens without this change?

Please let me know if any file was missed.

Added the missing javadoc in JacksonCSVSplitter and Splitter.


Add regional staging artifact move file

Add regional staging artifact move file and update some tags.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Update history_date to be tz aware

This eliminates the warning about history_date being set to naive timestamp.

@nielsvanoch since you took a look at pr #3; any thoughts on this one?

This requires a migration, no?

That's a great question.  After making this change I ran python manage.py makemigrations in my own project and the hisorical fields were updated.  However, I didn't think a migration was necessary in this branch.
If this is not the case, please let me know.

Ah, of course, these models aren't ever instantiated directly. This does mean it's a non-trivial change to upgrade, because all models using this will need to get a migration. I'll merge it with a minor version bump.

Added in https://github.com/vikingco/django-historicalrecords/releases/tag/1.3.0

And thanks a lot for your contribution of course!


customize CursorLineNr's color

good morning.
I am a first day user of the neovim hence apologies for a very basic question.
the context: I am trying to change the current line number's color to orange.
the problem: changing the value of the CursorLineNr does not have any visual effect. I can successfully change other colors, but not this one.
...
  on_highlights = function(highlights, colors)
    hightlights.CursorLineNr = colors.orange
  end,
...

It should be
highlights.CursorLineNr = { fg = colors.orange, bold = true }

Did you run setup BEFORE doing colorscheme?

Did you run setup BEFORE doing colorscheme?

yer sir. tokyonight.setup is on line 72 and colorscheme tokyonight is on line 138.

For me the CursorLineNr also works as expected. Really weird. Maybe some other plugin is overriding the highlight?

ah... do you know where to search for such a plugin?

PS: I am using https://github.com/nvim-lua/kickstart.nvim as the basic...

I have EXACTLY the same issue and I also use packer. Weird thing is that in netrw it works as expected.
Any solution to this?

~/.config/nvim/lua/default.lua
-- This file can be loaded by calling `lua require('plugins')` from your init.vim

-- Only required if you have packer configured as `opt`
vim.cmd [[packadd packer.nvim]]

return require('packer').startup(function(use)
  -- Packer can manage itself
  use 'wbthomason/packer.nvim'
  use 'folke/tokyonight.nvim'
end)

~/.config/nvim/after/plugin/color.lua
require("tokyonight").setup({
  --style = "night",
  transparent = true,
  styles = {
    sidebars = "transparent",
    floats = "transparent"
  },
  on_highlights = function(hl, colors)
    hl.CursorLineNr = {
      fg = colors.yellow
    }
  end
})

vim.cmd("colorscheme tokyonight")

@patrykk21 that's all really odd. Does setting LineNr work for you?
I still believe there's another plugin doing something weird.

You are both using the latest version right?

@folke

Does setting LineNr work for you?
Yes

You are both using the latest version right?
Well, at least I'm

I would love to help solve this issue but I don't even know where to begin -

Maybe this might help https://github.com/neovim/neovim/issues/19607
Can you try in kitty or alacrtitty?? And make sure you dont set the TERM env variable anywhere.

Also relevant https://github.com/neovim/neovim/issues/17885

And https://github.com/neovim/neovim/issues/17617

It seems there was effectively a bug that was fixed on March 7. So maybe you have an older version?

I forgot to mention I'm using Kitty.
Running this
:set cursorline cursorlineopt=number

Correctly sets the color on the CursorLineNr

Version
NVIM v0.7.2

@patrykk21 so it works now for you?

After adding the following config to a .lua file for neovim
vim.opt.cursorline = true
vim.opt.cursorlineopt = "number"

The issue seems solved

@folke Thank you for the help!

vim.opt.cursorline = true

issue is resolved. thank you :)


Remove kubernetes sandbox

Remove Kubernetes sandbox since this product has been deprecated by Bitnami.
Signed-off-by: mauraza<EMAIL_ADDRESS>

Learn Build status updates of commit 10b803e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-stack/operator/azure-stack-marketplace-azure-items.md
:white_check_mark:Succeeded

azure-stack/operator/media/azure-stack-marketplace-azure-items/sandbox.png
:white_check_mark:Succeeded
n/a (file deleted or renamed)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@sethmanheim,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Mauraza Thank you for the contribution -- #sign-off


Some classes being skipped when contain only @media

Hi and thank you for such a useful plugin!
Recently I noticed that some .d.ts files are missing few classes, particulary those which are consists only of @media query:
.input {
  @media (min-width: 768px) {
    max-width: 370px;
  }
}

I can open PR with fix if you like

@Nodman
Thanks contact!
It certainly seems that the type is not output in the case of @media query.
Please PR.

@Nodman
Thanks for the PR.
I've merged and published the latest version to npm.

@activeguild Thank you. Closing this.


lanelet2 examples

Hi, I successfully built the working space without docker but my local computer.
After I source devel/setup.bash, I try to execute the examples with rosrun lanelet2_examples 01_dealing_with_lanelet_primitives but nothing happen. No errors, no windows show up.
Is there anything I missed?

You didn't miss anything. It just means you successfully executed the example. It is not supposed to do or show anything. The interesting thing is the source code, not the output.

01 Dealing with lanelet primitives

02 Regulatory elements

03 Lanelet map

04 Reading and writing

05 Traffic rules

06 Routing


Unexpected success in commonmark-android-test with android-10

In commit 4cfc2e03f49dc0ce2d11695462357fe54afa799f, I changed
diff --git a/commonmark-android-test/app/build.gradle b/commonmark-android-test/app/build.gradle
index 3ca56fb..5d940d1 100644
--- a/commonmark-android-test/app/build.gradle
+++ b/commonmark-android-test/app/build.gradle
@@ -10,13 +10,13 @@ if (testPropertiesFile.canRead()) {
 }

 android {
-    compileSdkVersion 16
-    buildToolsVersion "21.1.1"
+    compileSdkVersion 10
+    buildToolsVersion "21.1.2"

     defaultConfig {
         applicationId "com.atlassian.commonmark.android.test"
-        minSdkVersion 16
-        targetSdkVersion 16
+        minSdkVersion 10
+        targetSdkVersion 10
         versionCode 1
         versionName "1.0"

Even though I would expect it to fail, gradle reports

...
:app:packageSnapshotDebugAndroidTest
:app:assembleSnapshotDebugAndroidTest
:app:connectedSnapshotDebugAndroidTest
BUILD SUCCESSFUL
Total time: 1 mins 12.542 secs

and the report contains
<?xml version='1.0' encoding='UTF-8' ?>
<testsuite name="com.atlassian.commonmark.android.test.AndroidSupportTest" tests="8" failures="0" errors="0" skipped="0" time="50.773" timestamp="2017-03-02T17:26:42" hostname="localhost">
  <properties>
    <property name="device" value="android-10(AVD) - 2.3.3" />
    <property name="flavor" value="SNAPSHOT" />
    <property name="project" value="app" />
  </properties>
  <testcase name="parseTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="6.03" />
  <testcase name="headingAnchorExtensionTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="7.379" />
  <testcase name="insExtensionTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="6.549" />
  <testcase name="strikethroughExtensionTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="6.069" />
  <testcase name="autolinkExtensionTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="6.423" />
  <testcase name="tablesExtensionTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="6.019" />
  <testcase name="yamlFrontMatterExtensionTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="6.07" />
  <testcase name="htmlRendererTest" classname="com.atlassian.commonmark.android.test.AndroidSupportTest" time="6.059" />
</testsuite>

When I copy commonmark-core into a test project (android-10) and build it as part of this project, the build fails as expected.

I'm not up to speed with how Android builds work. Can you explain what the issue is in more details? Is the way we test on Android not testing the right things?
Maybe @JinneeJ would be able to help with this.

Actually, I don't know either, at least when it comes to gradle and commonmark.
I slightly modified commonmark, so it works with a small project for Android 2.3.6 (android-10). I can build it within my project with ant, and it works fine so far.
In order to return my changes, I wanted to verify with the existing tests, and stumbled upon the unexpected result. I get a success with or without my changes, even though the emulator is running android-10.
This is why I reported this issue. To dig deeper and understand how the tests work will take some time however.

Hm, ok. So what's the failure when you build it as part of your project?

Initially there were changes in commonmark to support Android sdk 15 at least. There is sdk version 16 in tests because CI doesn't have emulator with sdk 15 (afaik).
It's likely that commonmark might work on android sdk 10 now. As far as I remember Java in Android SDK didn't change in span of SDK 10-15.
+1 to question what exactly failed on Android sdk 10 after copying commonmark core.

It does work on android-10, with a very small change. In commonmark/src/main/java/org/commonmark/internal/util/Html5Entities.java, I replaced "try with resources" with "try finally"
--- a/commonmark/src/main/java/org/commonmark/internal/util/Html5Entities.java
+++ b/commonmark/src/main/java/org/commonmark/internal/util/Html5Entities.java
@@ -45,20 +45,29 @@ public class Html5Entities {
         Map<String, String> entities = new HashMap<>();
         InputStream stream = Html5Entities.class.getResourceAsStream(ENTITY_PATH);
         Charset charset = Charset.forName("UTF-8");
-        try (BufferedReader bufferedReader = new BufferedReader(new InputStreamReader(stream, charset))) {
+        try {
+            BufferedReader bufferedReader = null;
+            try {
+                bufferedReader = new BufferedReader(new InputStreamReader(stream, charset));
                 String line;
                 while ((line = bufferedReader.readLine()) != null) {
                     if (line.length() == 0) {
                         continue;
                     }
+
                     int equal = line.indexOf("=");
                     String key = line.substring(0, equal);
                     String value = line.substring(equal + 1);
                     entities.put(key, value);
                 }
+            } finally {
+                if (bufferedReader != null)
+                    bufferedReader.close();
+            }

This is needed, because AutoCloseable was introduced at API level 19, and according to this Issue 73483 is also available at level 15.
I didn't find the time yet, to investigate further into the android test and find out what is tested and how. One reason why it works - I might have done this wrong - could be that the jar is built upfront, independent of the test. When I build the unmodified commonmark-java (core) as part of my project, it is built together with the rest of the source with android-10 of course, and then it fails with

[javac] /path/to/src/org/commonmark/internal/util/Html5Entities.java:48: error: incompatible types: try-with-resources not applicable to variable type
[javac]         try (BufferedReader bufferedReader = new BufferedReader(new InputStreamReader(stream, charset))) {
[javac]                             ^
[javac]     (BufferedReader cannot be converted to AutoCloseable)

One reason why it works - I might have done this wrong - could be that the jar is built upfront, independent of the test

That might be the reason, yeah. That would be good to fix in the Android test.
As for changing the code, I'd prefer not to do changes for an Android version that was released 6 years ago and only has 1% market share, according to this: https://developer.android.com/about/dashboards/index.html#Platform
(I'm already a bit sad about not being able to use Java 8 because of Android.)

I don't see an easy way to fix android tests. I agree the problem is that commonmark-android-test use compiled commonmark core that contain valid java byte code (that can work also on android 10). I see 2 ways how we can test compilation of commonmark core in android tests to avoid compilation fails:

We can convert commonmark-android-test to maven (but I'm not familiar with maven enough for that)
We can make "hacky" source set for gradle project (but it's an ugly hack and I would avoid it)

In general I'm not sure that it's needed to change android tests since commonmark is supposed to be used as already compiled dependency (and that is what android tests check here). Probably it would be nice to mention in readme something like that: "it's only guaranteed that compiled commonmark work on sdk > 15"

Well, if it were easy and obvious, I would have fixed it right away. :-)
@robinst

... for an Android version that was released 6 years ago and only has 1% market share

I am biased of course, because my phone belongs to these 1% market share. And even when 1% doesn't sound too much, if there are 1 bln Android phones out there, this would still make 10 mln, which isn't too shabby. :-)
Anyway, I will maintain this in a separate branch nevertheless.
@JinneeJ

We can convert commonmark-android-test to maven (but I'm not familiar with maven enough for that)

What would we gain by using maven? I don't object, just curious.

used as already compiled dependency (and that is what android tests check here).

This sounds like the test checks, if the jar file can be copied to the emulator. If this is the case, I would consider the test's name at least misleading. In my case it is even useless, because I cannot verify, if I introduced a bug or not. Which is why I started the test in the first place.

What would we gain by using maven?

Since commonmark core uses maven build system, having maven system in android tests will allow to build commonmark core with android sdk. So it will be possible to verify that building commonmark core doesn’t fail with android sdk.
I agree that probably naming is misleading. In general I’m not sure what should be tested on Android if all java tests are successful in commonmark-core. The only thing that commonmark-android-tests does - verifying that changes in commonmark-core won’t lead to something like ClassNotFound exception and etc on Android 😊

verifying that changes in commonmark-core won’t lead to something like ClassNotFound exception and etc on Android 😊

Yeah, and I think that's useful.
As I said before, I'm not up-to-date with Android development, but wouldn't you also just pull in an already compiled jar as a dependency. If so, and that works on Android, then I'm not sure we need to change anything. @olafdietsche does consuming commonmark via a jar not work for you?


Personal Finance Tracker

Project title
Personal Finance Tracker
Project Description
It's a web app that helps the user to keep track of their daily expenses.
Doc Domain

[] Solidity , Html, Css , JavaScript , Web3.js / Ether.js
[] Solidity , ReactJs /NextJs , Web3.js /Ether.js
[] Solidity , Python3 , Web3.py
[] Other , feel free to mention below

Are you contributing under any open-source program ?
Yes
Please Assign me this project @Vikash-8090-Yadav

Great, start working on this