Bug Report - Linking 'privatelink.monitor.azure.com' Private DNS Zone Breaks Log Analytics Querying When AMPLS Not Used

Describe the bug
ALZ deployments currently create and link a 'privatelink.monitor.azure.com' Private DNS Zone to the hub VNET. Because of how Azure Monitor implements Private Endpoints (via an AMPLS), this default configuration breaks access to services such as Log Analytics queries from within VNET or clients with DNS queries being forwarded to this zone.
Azure Monitor is designed so DNS queries to Azure Monitor endpoints always return a privatelink CNAME with the response; most other Azure services implement Private Endpoints by returning a privatelink CNAME only when a Private Endpoint has been added to the resource. DNS clients prioritize the CNAME record in the response and attempt to recursively resolve the name (such as 'api.privatelink.monitor.azure.com') via the linked Private DNS Zone. The zone has no records, so it responds that the name does not exist.  See: https://docs.microsoft.com/en-us/azure/azure-monitor/logs/private-link-security
With other services, linking the Private Endpoint Private DNS zones is not an issue, but this zone causes unexpected behavior which is frustrating to customers and difficult to troubleshoot. Unless ALZ also implements an AMPLS, as proposed in #967, this DNS zone should either not be linked to the hub VNET or not created altogether.
Steps to reproduce

Deploy ALZ (Contoso used)
[optional] Configure VNETs to use custom DNS IPs
[optional] On the custom DNS servers, configure a server-level forwarder or conditional forwarder (for zone 'privatelink.monitor.azure.com') to <IP_ADDRESS>
Attempt to access Log Analytics data via the Portal or SDK

   PS C:\&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; Invoke-AzOperationalInsightsQuery -WorkspaceId '...' -Query &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;AzureDiagnostics&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;quot;
   &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt; Invoke-AzOperationalInsightsQuery : An error occurred while sending the request. &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;

Generic Steps:
    1. Create a 'privatelink.monitor.azure.com' Private DNS Zone
    2. Link the DNS zone to a VNET
    3. Attempt to query Log Analytics from a VM within the VNET using Azure-provided DNS/<IP_ADDRESS>
Screenshots
Packet capture of DNS query when Invoke-AzOperationalInsightsQuery is executed:

Error in PowerShell from a client with DNS queries forwarded to the Private DNS Zone:

Error in Portal from a client with DNS queries forwarded to the Private DNS Zone:

Thank you @mbrat2005 for raising awareness on this. I'll look into it and get back to you soonest.

Trigger ADO Sync 1

Trigger ADO Sync 2

Are there any updates? This should be at least mentioned in the docs as are the other Private DNS Zone issues (https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Policies-FAQ#private-dns-zone-issues), ideally with scenarios it breaks.
Documentating scenarios may not be that ovious as I think with the new AMA agent this is even more messy.
For example, in our case enabling Azure Monitor private link zones (it creates zones for monitor.azure.com, ods.opinsights.azure.com and oms.opinsights.azure.com) broken following scenarios:

AKS clusters with Container Insights integration enabled are able to send data to LAW but they cannot access global.handler.control.monitor.azure.com and some of the pods are constantly restarting
Log Querying is completely broken when using DNS forwarder with these privatelink zones linked
Azure Managed Prometheus integration for AKS is completely broken and no metrics are published to Azure Monitor Workspace at all, in the logs we can see this is due to the global.handler.control.monitor.azure.com not being resolved correctly

The main issue from my perspective is that some Azure Monitor/Log Analytics DNS entries always return privatelink zone in the chain while some others are not. So for now entire Azure Monitor/Log Analytics stack is partially working and partially not.

Ah, the "this has been an issue for years" experience.
Finally, stumbled over the solution as well when troubleshooting missing Application Insights logs today.
100% agree that this should be documented at the very least!

@Springstone - can you add this to this page please?
https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Policies-FAQ#private-dns-zone-issues
It may be a good idea to list the zone names in the FAQ also so they come up on google searches.


Add 'git bzr'

This https://github.com/kfish/git-bzr can be used to work on 'git bzr' feature.

Is there an actual issue or feature request here? If so, please expand on it.

Heya,
thanks for raising an issue! Since this issue tracker is dedicated to git-scm.com website you might have more success with your issue if you raise your question in one of community channels listed at https://git-scm.com/community .


Edit Field Mapping?

Is it possible to change which field the Contact's Company Name maps to, for example?

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

ID: 95ffb635-6d9e-ba8d-8b02-fbd8f46d36ce
Version Independent ID: ffcc3f3b-11a2-9bac-08e9-97e47022aee0
Content: Control field synchronization between Dynamics 365 Customer Engagement and Outlook
Content Source: ce/admin/control-field-synchronization-outlook.md
Service: crm-online
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

Sorry. Changing field mapping is not possible.


E2E tests are not using the correct Kind version

If you look at logs in any of the E2E artifacts, you'll notice all Kind cluster are v1.27.1.
This seems to be the default image for the version of Kind installed with the Github Action: https://github.com/kubernetes-sigs/kind/releases/tag/v0.19.0
Issue stems from the fact that the e2e-framework API is misleading. It never takes the Provider image options into account when launching Kind: https://github.com/kubernetes-sigs/e2e-framework/blob/fdcf509f96c96f0055b03f026ea44c62df82c753/support/kind/kind.go#L170

Closing as #676 has been merged


Cannot read property 'toDomXCoord' of undefined

To repro, start with a fresh install, add a telegraf config, push data, open the system dashboard, and change the dashboard to refresh every 5 seconds
Version 2.0.0 (0e5e2a5)

Not able to reproduce this

I actually saw this error. I was configuring a graph and another graph failed with this message


Pro 3554 store registry variables db

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRO-3554
Change description
Changes registry endpoint to select the next registry in the sequence from database values instead if in-memory values.
Does this PR introduce a breaking change? (check one with "x")
Changes involve backend persistence service and submit service updates along with a new registry database table.
[ ] Yes
[x] No

Dev approved, but ticket currently blocked for QA testing by PRO-3800.


[Android] Import via Camera causes the app to crash if photo is taken first thing upon app install

Describe the bug
The app crashes when one tries to import a photo from the camera via

Add new;
Import image;
Take photo.

ATTENTION:  the bug manifests ONLY after a fresh install and BEFORE one has tried to scan a QR Code.
Expected behaviour
No app crash.
Technical details
Galaxy XCover 4, Android 9
Wallet App 1.2.0-acc
https://user-images.githubusercontent.com/76050122/133758109-e754a0cb-76f5-42a8-883e-54fca57e8723.mp4
Possible Fix

Additional context

Confirmed.

Retest was successful, DGCA Wallet 1.2.2-acc (18)


ESP32-WROOM-32 - AT HTTP get block with null char (0x00)

Hello,
I have an ESP32-WROOM-32 with AT firmware of the branch release/v<IP_ADDRESS>_esp32 (last commit 3c9e097ca).
AT version:<IP_ADDRESS>-dev(de4a90c - Jun 14 2019 07:28:10)
SDK version:v3.3-beta1

The problem:
When I get a binary file with the next HTTP command, the transmission of the 512B-block cuts the messages to the first 0x00 and ignores the rest.
Command:
AT+HTTPCLIENT=2,0,"http://test.xx/file.test",,,1
Example return :
+HTTPCLIENT:512,    2B 48 54 54 50 43 4C 49 45 4E 54 3A 35 31 32 2C
CRLF                0D 0A
+HTTPCLIENT:512,    2B 48 54 54 50 43 4C 49 45 4E 54 3A 35 31 32 2C
..CRLF              B5 FA 0D 0A
+HTTPCLIENT:512,    2B 48 54 54 50 43 4C 49 45 4E 54 3A 35 31 32 2C
.1.F..\..K.hO.zq    FF 31 18 46 12 F0 5C F8 14 4B 1B 68 4F F4 7A 71
.F..U..F.+...K.h    18 46 12 F0 55 F8 03 46 01 2B 0F D1 10 4B 1A 68
.K.....             10 4B 07 F1 08 0D 0A 2B 48

I guess it's something related to strings and its termination, but I'm not familiarised with the AT firmware.
Thank you very much in advance !

@AdriPapa Hi, it seems that has already fixed in the lastest version.
I tried AT+HTTPCLIENT=2,0,"http://download.espressif.com/esp_share/customer/test/xaa.bin",,,1, it works well on my side.
Please git pull the latest code and compile again.
please provide the HTTP GET URL if possible when test failed.

The lastets version works, thank you @ustccw  !


Error: Unable to find a set of packages that will work with your constraints.

Subj

More information about what you were trying to do will be needed to do anything here. For example, how does your elm-package.json file look? What command(s) did you issue? Starting in an empty directory?

@jvoigtlaender Sorry for the lack of info.
{
    "version": "1.0.0",
    "summary": "helpful summary of your project, less than 80 characters",
    "repository": "https://github.com/USER/PROJECT.git",
    "license": "BSD3",
    "source-directories": [
        "./src"
    ],
    "exposed-modules": [],
    "dependencies": {
        "elm-lang/core": "3.0.0 <= v < 4.0.0",
        "evancz/elm-html": "4.0.2 <= v < 5.0.0"
    },
    "elm-version": "0.15.1 <= v < 0.16.0"
}

I'm running in this issue while executing elm-package install evancz/elm-http

Okay. As seen here, version 3.0.0 of core depends on at least version 0.16.0 of Elm. So elm-lang/core": "3.0.0 <= v < 4.0.0" is incompatible with "elm-version": "0.15.1 <= v < 0.16.0". You have to change one of these constraints.
Of course, it would be nice if the error message had told you so. There is some issue already open either here or in the elm-make repo which is tracking this. So at some point there will hopefully be a more informative error in such cases.
Does this resolve the present issue?

@jvoigtlaender Yes, big thanks!

Hi. could you please tell me how to solve this problem? I am starting to learn elm and I cannot install the html package on windows


Unable to access API end point url

The Fineract-CN Mobile app currently trying to access the end point base url is pilot.kuelap.io.
Its not accessing while running the app. I dont think so this is the correct end point url.
Please update me on this to run this mobile app with valid end point url.

@seshalh Did you find the correct url?


merge single_quoted_string and double_quoted_string

This will come in handy with my next few commits. :)

Hey Alec! Nice work! :)
Would you like to be added to the list of collaborators? This way you would be able to push changes directly :-)

@OttoRobba Sure. :) I promise to be very careful!


Typed proxy support

Requirements
In order to create a type-safe experience for working with orchestrations and activities, the Java SDK for the Durable Task Framework should support type-safe invocation of orchestration and activities.
For example, when calling an activity, instead of the following:
Object activityInput = "World";
String result = context.callActivity("SayHello", activityInput, String.class).get();

...we should be able to instead write:
MyActivities activities = // get a pointer to an activity proxy
String result = activities.sayHello("World");

We'd want the same experience also for orchestrations (created by a client) and sub-orchestrations.
Ideally this support will also allow developers to easily unit test their code.
Design considerations
Java's Proxy support could be a good starting point for such a feature.

I'll start looking at our options for this


redirects-list.json broken

Probably due to #325.
Also shows up in failing link-checks since 2022-10-17 (cml.dev/chat 404)

It's actually not broken, the 404 page is loading first before being redirected. It should be redirected upon request from the server itself. I hope #347 will fix the problem.


It's not possible to determine the rect_size of children in GridContainer

**Godot version:3.1

OS/device including version:

Issue description:

Since there is a margin between each child in the GridContainer, and the size of margin is unknown, it's impossible to calculate the size of the child to fill the Grid with a fixed size.
For example, the width of my GridContainer is 640, its columns is 4, and I want the children fill the grid, I set the rect_min_size.x of the child to 160, the final size of the Grid will bigger than 640.
Suggestion:
The margin between the children can be set to a determined value.
Steps to reproduce:
Minimal reproduction project:

You can customize the "margin" via separation variables in theme constants.

As pointed out by @KoBeWi , there is a default margin with grid containers which you can override using custom constants.

I have not changed this value ,its value is 0, but there is still a 4 pixel margin between children.

it's OK.

Did it ticking the boxes solve the problem?
I see from my emails you, edited the message saying it wasn't working. If so that's a big.

after check that option on, it works.
The default value is 0 and it is not checked on, but it leaves a 4 pixels margin, it's a little confusion without your reminder.


test(migrate): attempt to get rid of flaky ci macos log

Closing for now

Happened recently again https://github.com/prisma/prisma/runs/4883407768?check_suite_focus=true#step:13:438 reopening 👯


ci(ci/cd): refactor pipelines

:tada: This PR is included in version 2.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add support for YouTube embeds

This PR adds basic support for YouTube embeds, so videos can be played directly. I could think of supporting other video services (e.g. Vimeo, Dailymotion), but I first wanted to see where this is going.
There are some shortcomings I don't want to leave unmentioned:

this does not support YouTube playlist (Twitter itself only has limited support)
the video ratio is fixed, but without accessing the YouTube API, there's no way to determine the correct one (16:9 is probably most common)

I also suggest applying aspect-ratio on the iFrame and maybe change the width/height in your CSS.

I think it would be better for performance to use Paul Irish's lite-youtube-embed component: https://github.com/paulirish/lite-youtube-embed

I think it would be better for performance to use Paul Irish's lite-youtube-embed component

Unfortunately, I have no deeper experience with Eleventy and how to configure it to support custom elements. Simply requiring lite-youtube-embed results in this error:
HTMLElement is not defined (via ReferenceError)

@idleberg Can you drop the version you tried with the embed? I set it up in my own Eleventy site and could probably help get it over the finishline.

@aarongustafson These are my uncommitted changes:
diff --git a/package.json b/package.json
index fc114ae..dafa521 100644
--- a/package.json
+++ b/package.json
@@ -31,6 +31,7 @@
     "twitter-lite": "^1.1.0"
   },
   "dependencies": {
-    "chartist": "^0.11.4"
+    "chartist": "^0.11.4",
+    "lite-youtube-embed": "^0.2.0"
   }
 }
diff --git a/src/twitter.js b/src/twitter.js
index 7ad5a6c..2875beb 100644
--- a/src/twitter.js
+++ b/src/twitter.js
@@ -159,7 +159,8 @@ class Twitter {
                                                searchParams.delete('v');
                                        }

-                                       let displayUrlHtml = `<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/${id}${searchParams.keys().length ? '?' + searchParams.toString() : ''}" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen crossorigin="anonymous" />`
+                                       await import('lite-youtube-embed');
+                                       let displayUrlHtml = `<lite-youtube videoid="${id}" />`
                                        text = text.replace(url.url, displayUrlHtml);
                                } else {
                                        let {targetUrl, className, displayUrl} = this.getUrlObject(url);

How about rebasing to resolve those merge conflicts?


Promote klaus-sap to UAA approver

According to the the Promotion to Reviewer or Approver we need two approvals. It will be good if we could get an approval from different involved parties.

ping @peterhaochen47, @bruce-ricard, @swalchemist, @Tallicia

Thanks and welcome as reviewer @klaus-sap.


Rename Clearing Operations Tools

Rename Clearing Operations tools to a more generic name such as GRG Tools.
Name:

ClearingOperationsTools_pro.tbx --> GRGTools_pro.tbx
ClearingOperationsTools_arcmap.tbx --> GRGTools_arcmap.tbx
Alias: _grg

It was also discussed to rename the tools in the new GRG toolbox to reflect those in the GRG widget:

Canvas Area GRG --> Create GRG from Area
Point Target GRG --> Create GRG from Point

Also need to update tests to reflect new toolbox name.

.\utils\tests\Configuation.py

Current refactor examples:

Got rename working for Create GRG from Area. Compared output from original Canvas Area GRG (CAGRG) and Create GRG from Area (CGRGFA):
Executing: FeatureCompare CAGRG0002 CGRGFA0005 Grid ALL # "0.001 Meters" 0.001 0.001 # # NO_CONTINUE_COMPARE #
Start Time: Thu Sep 07 15:50:09 2017
FeatureClass: Shape types are the same.
FeatureClass: Feature types are the same.
Table: Table row counts are the same.
FeatureClass: Feature class extents are the same.
GeometryDef: GeometryDefs are the same.
Field: Field properties are the same.
Table: Table row counts are the same.
SpatialReference: Spatial references are the same.
Table: Rows are the same.
Succeeded at Thu Sep 07 15:50:09 2017 (Elapsed Time: 0.21 seconds)

PR #587 is in to rename the tools.

Just need one reviewer to verify and close this one out once the PR is merged.

@mfunk not to be difficult, but should we call them:

Create GRG from Area
Create GRG from Point
-or-
Define Grid from an Area
Define Grid from a Point

... based on the widget?

@joebayles
We went with Create GRG from Area and Create GRG from Point based on the GRG widget, and made all the associated changes that went with it. I'm really not looking forward to changing them again, and again in another few weeks. Pick something and stick with it please.

Verified.


Add: SET TV 2 [US/VN]

Channel Name
SET TV 2
Alternative Names (optional)
Saigon Entertainment Television 2
Network (optional)
No response
Owners (optional)
No response
Country
US
Subdivision (optional)
US-CA
City (optional)
Garden Grove
Broadcast Area
c/US, c/VN
Languages
eng;vie
Categories (optional)
entertainment
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://setchannel.tv
Logo
https://setchannel.tv/wp-content/uploads/2019/08/SET-web-logo.png
Notes
No response

Please update your request:

broadcast area codes must be separated by ;

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels


The NuGet Dependency Resolution documentation is very misleading

The documentation of the "Nearest Wins" and "Cousin dependencies" rules in the NuGet "Dependency Resolution" chapter is very misleading.
Let's try to interpret the following sentences:
"When the package graph for an application contains different versions of the same package, NuGet chooses the package that's closest to the application in the graph and ignores all others."
"When different package versions are referred to at the same distance in the graph from the application, NuGet uses the lowest version that satisfies all version requirements"
Based on these I would assume that the "Nearest Wins" rule is a general rule, and hence it is "stronger" than the "Cousin dependencies" rule.
E.g.:

My Project -> PackageE -> Package D (>= 1.1.0)
My Project -> Package D (>= 1.0.0)

Here it's quite obvious that the 1.0.0 version of Package D is selected, since its version was "overwritten" by the user. (And by the way the NU1605 warning is displayed, since the package was downgraded.)
But let's take the following example now:

My Project -> Package A -> PackageE -> Package D (>= 1.1.0)
My Project -> Package A -> Package D (>= 1.0.0)

Based on the documentation I would expect that here again the 1.0.0 version is choosen (although that would be very weird), but in reality the "Cousin dependencies" rule wins, and the 1.1.0 version is selected.
There are many discussion regarding this question (e.g.: #5400, #8020, #9861), but due to the many contradicting statements I had to try it out myself to be sure.
Both Package A 1.0.0 and Package B 1.0.0 references the 1.0.0 version of Package D:

But if I upgrade Package B to 1.1.0, then it will reference Package C 1.1.0, and that will reference Package D 1.1.0.
As you can see - although the Package D 1.1.0 reference is further from my application than the Package D 1.0.0 reference - the 1.1.0 version was choosen globaly:

Therefore it should be made clear in the documentation that the "Nearest wins" rule is applied only on direct dependencies (aka. top level packages), and "Cousin dependencies" is not only applied "at the same distance".

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

ID: 8e8a945e-ee7e-cefa-282a-41da09a951b9
Version Independent ID: c380b1cb-6e17-7777-995f-7c8b48f581de
Content: NuGet Package Dependency Resolution
Content Source: docs/concepts/Dependency-Resolution.md
Product: nuget
GitHub Login: @JonDouglas
Microsoft Alias: jodou

"Nearest wins" rule is applied only on direct dependencies (aka. top level packages)

If this is true, then the example in the docs under "Nearest wins" regarding package C 2.0 should be removed as it is entirely misleading.
In fact, if this is the case then I think the docs should be changed as follows:
(1) Put the "cousin dependencies" section first
(2) Follow that with a section called "Direct dependencies win" that just says: "If the application directly references a package, the directly referenced version will be used even when the "cousin dependencies" rule would select a different version..."

@nkolev92 even if we're not ready to write the formal docs, any chance you could explain how this works here? This ambiguity is impacting our ability to write some internal tooling that works with NuGet.

Hi, I've been looking at this recently as well an I've prepared this diagram. I hope it helps:

Package B v2.0.0 is considered “nearest” because both B v1.0.0 and B v2.0.0 are in the subtree of Lib1 and  B v2.0.0 is a direct dependency of Lib1.
On the contrary package D v1.0.0 is closer to the root project than the D v2.0.0, but it is not considered “nearest”. It is because the D v1.0.0 is a direct dependency of B v2.0.0, but D v2.0.0 is not in the subtree of B v2.0.0.

@marcin-krystianc: I don't really get your point.
Is Lib1 also a NuGet package, or is it a library in your solution? (I.e. what do we consider "top level dependency" in this case, Lib1 or package A & B?
And which versions of package B and D would be choosen by NuGet at the end?

Yeah, I know that this topic is hard to explain 😄

Lib can be a project or a NuGet package, it doesn't really matter for the dependency resolution algorithm
Don't think in terms of  "top level dependency", it is not how the algorithm works - that is what probably confuses you
B v2.0.0 is chosen due to "nearest wins" rule for the reason I explained in previous comment
D v2.0.0 is chosen because it is a cousin with D v1.0.0 and "NuGet uses the lowest version that satisfies all version requirements" (which is `D v2.0.0" in this case).
Documentation claims that distance from the top level project is important but it is not how the algorithm actually works. D v2.0.0 is selected even though it is further from the top level project than D v1.0.0.

@marcin-krystianc thanks for responding here. I feel like I'm still not quite understanding when the "nearest wins" rule gets applied.
In the diagram, for example, you say that B v2 is "nearest" but in this case B v2 is also the "lowest version that satisfies all requirements" (presuming that Lib 1 references B  >= v2).

Can you show/describe an example where "nearest wins" trumps "lowest version that satisfies all requirements"?
Is there a succinct way (like the current docs) that can describe the resolution algorithm accurately?

In the diagram, for example, you say that B v2 is "nearest" but in this case B v2 is also the "lowest version that satisfies all requirements" (presuming that Lib 1 references B >= v2).
Can you show/describe an example where "nearest wins" trumps "lowest version that satisfies all requirements"?

If in the diagram that I posted above you would swap B v1 and B v2 it would be what you ask for. The B that is a direct dependency of Lib1 is "nearest" in the scope of the whole Lib1 subtree, so it always wins with any other "B" that is further down in that subtree.

Is there a succinct way (like the current docs if they weren't inaccurate) that can describe the resolution algorithm accurately?

Nothing I'm aware of.

Documentation claims that distance from the top level project is important but it is not how the algorithm actually works

I wasn't around when the original docs are written, but I have not a single place where actual distance matters.

thanks for responding here. I feel like I'm still not quite understanding when the "nearest wins" rule gets applied.

Let me give a shot.

Nearest wins is probably best summarized as, direct dependencies of ancestors always win in that subgraph.

The first subgraph in which 2 versions of the same package appear determines what version gets selected.

A more practical way of looking at it is that a
downgrade will only happen if someone has explicitly added a top level package that has a lower version, at any point during the graph.

Here's some examples:
Simplest case of a downgrade is the following:

Project X, explicitly wants B 1.0, and because of direct dependencies of ancestors always win, when we look at B 2.0, the first time they are in the same subgraph is the complete graph here, and because B 1.0 is direct, it wins.

Now say, someone packaged X and shipped X 1.0.0.
Say I have a project in which I installed X 1.0.0.

B 2.0.0 and  B 1.0.0 first appear in X's graph. NuGet tries to preserve the user intention, so it selected 1.0.0.

Now what if another subgraph has a B reference of 3.0.0.
Say you have the following:

This is where the whole, cousins don't really look at the distance thing comes in.

For the X subgraph, B 1.0.0 is chosen, but is obv downgraded.
B 3.0.0 appears in a subgraph for the first time in the MyApp subgraph. Given that there's no direct dependency to B, here's where cousin dependency wins and the most compatible version is selected (in this case lowes)

Hope that helps.
My goal is to rewrite the docs and I think we might have to rename the nearest wins rule because it's very confusing.

Thanks @nkolev92 those diagrams and explanations are super helpful.
I'm trying to think about how to express this as a simplified algorithm (for context, my underlying intent behind these questions is partly because I'm trying to replicate NuGet's restore algorithm in a piece of tooling I'm writing). Here's what I'm thinking so far:
(1) Draw out the full dependency graph. Whenever we encounter a package dependency range (e. g. A depends on B >= 1.0), we pick the lowest compatible version in that range. Project dependencies are nodes in the graph just like package dependencies (except they lack versions).

(2) Apply the "direct dependency of ancestor wins" rule the graph by pruning each subgraph which is superceded according to that rule.

(3) For any package with multiple versions remaining in the overall graph (cousin dependencies), select the highest (most compatible) version and prune all other versions.

(4) Detect any errors; basically we need to check whether the globally selected version of each package is compliant with the dependency version ranges for all other selected versions. Step 2 can result in invalid downgrades of packages, while step 3 can result in invalid upgrades of packages if there are version ranges with upper bounds (e. g. in your example if X depended on B [1, 3) then selecting B 3.0 would be an error).

Does this seem right?
One area that feels a bit vague is step 3 because it feels like we could get different outcomes depending on what order we processed packages in. For example, imagine if our graph after step 2 was this:
MyApp -> X 1.0 -> A 1.0 -> B 2.0
             -> Y 1.0 -> A 2.0
             -> Z 1.0 -> B 1.0

If we resolved package A first we'd end up pruning the A 1.0 subgraph and keeping B 1.0. However if we consider B first then we'll pick B 2.0 (unless the algorithm has some way of revisiting the previous resolution?). What is it supposed to do here?

The algorithm is supposed to pick A 2.0 and B 1.0.
Firstly, all packages are detected.
Then direct dependencies of ancestor wins is applied and nothing happens because there's no direct deps.
Finally the graph is walked in a BFS fashion, and we will do multiple passes in order to resolve all conflicts.
X, Y & Z are all selected, and then we come to A, and when checking A 1.0, we already know about 2.0, so A 1.0 will be rejected because it's not the best version.
A 1.0 gets rejected, then we do A 2.0, which will get accepted because it's the best version.
At the end of that the 2nd level pass, B is going to be treated as ambiguous, because we still see a different version of it lower in the graph.
In the next pass, we know A 1.0 was rejected, so B 2.0 gets rejected as well, so B 1.0.0 becomes unambiguous.
You can see the code in https://github.com/NuGet/NuGet.Client/blob/f04b570e65af9f7828f01968c1efdf42e8f317d7/src/NuGet.Core/NuGet.DependencyResolver.Core/GraphModel/GraphOperations.cs#L26-L37.

@nkolev92: Do I see well that your second example is exactly the same scenario that I've tested?
(See above in the issue's description.)
You wrote:

B 2.0.0 and B 1.0.0 first appear in X's graph. NuGet tries to preserve the user intention, so it selected 1.0.0.

For me version 2.0.0 was selected, not 1.0.0.
(The package names and versions were different in my example, but the point was the same.)
I'm confused, is there a difference that I haven't noticed?
Have you tried it in practice, e.g. with a local NuGet feed, like me?

Yes, I used tests to confirm the behavior.
The 3 tests are available here: https://github.com/NuGet/NuGet.Client/blob/ed04716852723771d9ce95ad2ea0c8c6ac31ce54/test/NuGet.Core.Tests/NuGet.DependencyResolver.Core.Tests/RemoteDependencyWalkerTests.cs#L1813-L1912
@madelson Here's an easy way to validate NuGet' behavior through tests.
This is something I cooked up locally:

C:\Code\Temp\NDR\MyApp\MyApp.csproj : error NU1605: Detected package downgrade: B from 2.0.0 to 1.0.0. Reference the package directly from the project to select a different version.
C:\Code\Temp\NDR\MyApp\MyApp.csproj : error NU1605:  MyApp -> X 1.0.0 -> A 1.0.0 -> B (>= 2.0.0)
C:\Code\Temp\NDR\MyApp\MyApp.csproj : error NU1605:  MyApp -> X 1.0.0 -> B (>= 1.0.0)

@nkolev92: Ok, it still gives me headache when I'm trying to understand it, but maybe now I'm closer :)
First of all, I was wrong, your example and my example are different.
This was yours:

And this is mine:

In your case the B 2.0.0 package (greyish) was thrown out becuase of the "nearest wins" rule, while in my case the D 1.0.0 package (greyish) was thrown out because of the "cusine dependencies" rule.
So if I interpret it well, then the "nearest wins" rule is only applied if there is a junction in the tree, and only on the level of the junction.
By "junction" and "level of juction" I mean the following:

Here the "nearest wins" rule was used, because B also appeared on lower levels of the graph.

Here the "nearest wins" rule was not used, because B (and A) only appeared once in the graph.
Pacakage D appeared more times in the graph, but that was not on the "level of the juction", hence it was resolved by the "cousin dependencies" rule.
Is it correct?

Yep, that seems right.

It seems like we're getting close to a concise description of how this works that could replace and clarify the existing docs!


Examples should be verified for two-slashiness on CI

I shipped a bad build of docusaurus

Interesting but docusaurus will fail on purpose today because of #79


Stream isn't returning anything

    def __init__(self, api):
        self.api = api
        self.me = api.me()
        logger.info("StreamListener Inicializado")

    def on_status(self, tweet):
        print (tweet.text)

def main():

    api = create_api()
    tweets_listener = newTT(api)
    stream = tweepy.Stream(auth=api.auth, listener=tweets_listener, tweet_mode="extended")

    stream.filter(track=['python'])

if __name__ == "__main__":
    main()

Tweepy was working fine but suddenly the stream isn't returning anymore.
I've tried with different Authentications but nothing worked.

I ran your code and it seems fine. could you send a screenshot of the error you get?

I'm also unable to reproduce this issue.
In the future, you should use the on_error method of the StreamListener to determine what errors you're encountering.
For code block usage, see https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks.

I am having the same issue. Running python 3.7.5

I maybe the limit reached.
I had error code 420.
Returned when an app is being rate limited for making too many requests.


Documentation for customizing redoc

Describe the feature
There are no example for using redoc with custom options like specific version
Why do you want the feature?
I spent a lot of time to read the code to understand how this plugin works

Available in 2.16.0.
Thank you for your contribution!


fix: support arrays

Fixes #288

Hey @tenjaa Sorry this took so long. If you add a sample to test/fixtures/samples we should be able to merge this. Ideally the sample is a real module from the public registry.

@mrgrain I had a quick look but found nothing with a read-only array property. Do you have a hint where I could find something like that?
In the meantime I added a very simple self written resource and one from datadog to show that for createOnly properties nothing should change.


Fix Snowflake tests - private access error

Pull Request Description
Snowflake tests are still failing on develop branch. This time due to a Private_Access error. Attempting to fix that to make the tests on develop green.
Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[ ] Unit tests have been written where possible.
[x] If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
or the Snowflake database integration, a run of the Extra Tests has been scheduled.

If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

Extra tests run:

🔃 https://github.com/enso-org/enso/actions/runs/12547109452

The Extra tests are passing, so I'm merging :)


docs: Notifications REST API missing member_feature_requested reason

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/rest/activity/notifications?apiVersion=2022-11-28
What part(s) of the article would you like to see updated?
Add the reason member_feature_requested
Additional information

Thanks


Icons NOT showing on Device in either MDNavigationDrawer or MDDropdownMenu

Description of the Bug
while developing on my PC the icons show just fine.  But when I compile with Buildozer to make an APK file, when I run the App on the Tablet none of the icons are showing in either my MDDropdownMenu or MDNavigationDrawer.
This might be a Buildozer or Python-4-Android bug actually...
Code and Logs
from kivy.app import App
from kivy.lang import Builder

kv = """
Screen:
    # KV-Code
"""

class MainApp(App):
    def build(self):
        self.root = Builder.load_string(kv)

if __name__ == '__main__':
    MainApp().run()

Screenshots
Add images to explain us this bug. Paste urls here.
Remove this section if no images here
Versions

OS:
Python:
Kivy:
KivyMD:

@edwit1971 Dublicate - https://github.com/HeaTTheatR/KivyMD/issues/327


Update loader.py

Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Added comments to make loaders more justified.

There are only two comments. Did you miss the rest of your commits?

i think so! let me check.
On Sun, Oct 30, 2016 at 7:15 PM, Fabian Affolter<EMAIL_ADDRESS>wrote:

There are only two comments. Did you miss the rest of your commits?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/4137#issuecomment-257151817,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKAOYfhubUEiJayXBTYSoa-X9n7b5mN8ks5q5J9wgaJpZM4KkYM9
.

--
Regards,
Rishabh Thukral
9466309992

Closing this while you figure it out


Hello!

When implementing a library/app in another language, it's usually called a port, not a clone!

That is why clone is in quotes :)


[Feature] SE View Only

What do you think about having a SE(send-error) View/Presenter only ?
That would be useful on Form Scenarios, like logging in, saving data etc.
I'm already implementing it on my app, if you think that would be cool, I can drop a PR !

Hi,
well I also caught myself implementing this multiple times, but I would like to avoid putting this into this library, for various reasons:

maintaining & testing
you never catch all use cases and users will start to complain about it. See #132 #107 #42 about LCE components
I would prefer to keep this library small and concise. See #143  about adding support for Map Fragments. The problem is if we add SE, then next month we may have to add another XY component too and so on.

I'm open to discuss that, but I think it would be a better approach to write and publish a standalone SE library on top of Mosby. I would be more than happy to share the link to such a extension module library in the README. See https://github.com/Bodo1981/appkit
What do you think?
By the way: In my experience you need 3 states i.e. for login: 1. Show login input form. 2. Show loading (Sending) 3. Show Error ( and optionally 4. Show successful)

Sure, no problem.
I see your point and I agree that people may complain about some tweaks it should have or use cases it wouldn't cover. Nevertheless I think it's a very common use case, and I also get myself implementing this over and over. I'm not sure if it's a good approach to create a lib on top of that just for this feature. If so, LCE should also be a part lib, right ?
About the states, I agree 100%, that' how I do on my side. And I'd give a +1 for the step 4, show successful callback.
Thanks for taking your time and I really appreciate all the work and effort you put on your project dude !

Hey @sockeqwe, how is it going ?
I came up with something like that https://github.com/leonardo2204/mosby/commit/e44e19ff6493576d1142f98aa0f9d0267d31882c
See what your toughts are on that !

Sorry, I am a little bit busy right now, I will take a detailed look during the weekend...
Indeed, there are discussions going on to remove LCE from this project (or at least package it into is own artifacts) #148 and I think if I would rewrite this project from scratch I wouldn't add LCE into this project.
Usually, some other Mosby users give their feedback here on github on some project related decisions. I think we should wait some more days, maybe we get some more opinions about that, and then we make a final decision. I'm open to discuss that with the community and you are part of the community!

I'm not sure if it's a good approach to create a lib on top of Mosby

I'm not really talking about writing a whole big library like appkit, I'm just saying that instead of putting all you code into Mosby directly, we could simple publish those classes as its own artifact (with having a dependency to Mosby).
Does that all makes sense for you?

Sure, no problem !
Ohh I see it, so that would be something like the viewstate separate lib, right ? I misunderstood haha. In that case I think that would be just fine, also we could even extract the LCE part into the same package.. What do you think ?
We'd have something like a MosbyForm, something like that (I'm not good at naming things).
Thanks for your time, I'll wait for some other feedback ;)

We are using mosby in several projects and in each of them we have different requirements for LCE views which happen to differ a bit from each other. And also from Mosby's default implementation of LCE. The concept is there, but I discovered that it is sometimes easier to create my own implementation of LCE stuff than to try to customize mosby's and to apply workarounds for functionality it does a little bit differently. For example mosby has the concept of pullToRefresh (last time I looked) while I might not need it, etc etc.
So I feel that it would be a correct move - to separate this into a different artifact which would provide this functionality for the projects that can use it right away. And other implementations can use that for a reference and inspiration also :)

I also use multiple variations of LCE for different cases and some are the Mosby provided implementation.  To the same end I have two implementations around forms as well.
I'm onboard with moving LCE and adding other things like SE to a separate module, that makes the most sense to me.

I kinda stopped developing this features waiting for a feedback from you guys...
Any thoughts on how to design this new features ?

I think we can add this but in a separate module in Mosby 3.0 . Still not sure about the naming...

@sockeqwe Thanks for the feedback !
Sure, do you have any naming sugestion ?
As soon as I have some more time, I'll keep implementing !

Regarding naming: Content Loading Error Success  (CLES) ? Doesn't sound that nice in my ears but nothing better came into my mind until now ... not sure ...

@sockeqwe Hmm, I'm not sure about that, IMO, it doesn't seem like a "natural" name to refer to Form views. Maybe using send or something else to make it clearer ? Something like Send Loading Error Success (SLER) or Form Loading Error Success (FLES) ??


Reopen #12356 due to being misidentified as a duplicate of #12369

#12356 was misidentified as a duplicate of #12369. Please reopen #12356.

I reopened it


Set default values for schema url fields

My proposals

Add a syntax in Prisma Schema Language for setting a default value if env variable was empty. e.g.

datasource db {
  provider = "postgresql"
  url = env('POSTGRES_URL') || "postgresql://dev@localhost/testdb"
}

As a better option add support for schema definition in JavaScript/Typescript (e.g. schema.prisma.js)

Why I think creating a new schema language isn't a good idea?

Please re read your article on the problems of schema first development.
I worry that in time you reach the same conclusion and you end up with a schema language that tries to solve everything but is not as good as a real programming language.
I think having a real general purpose programming language at your disposal is always a good idea. (take Webpack config or many other tools for example)
I understand that Prisma is a cross language tool (Go driver for example) but it is also written in JS and Generator and Lift need node to run. So I see no harm in having a  schema.prisma.js option.

What are the use cases for these?
I’m struggling to add Prisma 2 to my development workflow.
I have a complex NodeJS server that connects to some DBs and outside services. We try our best to keep initial configuration for new developers as simple as possible (setup everything in the first npm run dev).
We use docker to initialize and run the DBs and external services and setup some default credentials for dev databases.
In the dev server we set the same default credentials for our DB connectors so new developers don’t have to worry about DB config at all.
The current url system for Prima Schema Language only accepts environment variables. It is a good thing for production but not the dev env.
Using .env file is not a good option for us as each new developer should create it and add the default configs to it.

It is good to mention that we are currently using photon's datasources argument to override the database URL like this:
const photon = new Photon({
      datasources: {
          db: {
            url: process.env.POSTGRES_URL || "postgresql://dev@localhost/repository",
          },
      },
});

A note: This might also be solved by adding a second param default (of fallback) to the env() method.

Hi @HosseinAgha! Thanks for bringing this up,
For 1., we're definitely going to add a default env argument, it'll likely look like this
env("POSTGRES_URL", default: "postgresql://dev@localhost/testdb")

For 2., thanks for bringing this up! You've sparked a lively debate internally about this decision.
The reason we went with a declarative format rather than a code-first format is that we're describing the layout of your datasource, we're not providing implementations for this schema (unlike graphql's resolvers). In this sense, we're more like JSON schema or terraform than GraphQL. We also want to be able to migrate your database based on this schema file.
We do understand that you may want to simply generate database clients and bring your own migration engine, so for that we're planning to introduce the Prisma SDK to work with Prisma without generating a schema.

Was the default for the connection url functionality ever added?

@blevine No, we didn't get any more requests for this so this was never pushed again up the priority classification.

That's too bad.  It seems to have been almost completely implemented and would have been a good enhancement.

I would be happy to see an implementation of this as well! :-)

Would love to see this implemented. It would help with zero downtime migrations of database credentials.
Supporting something similar to env("NEW_DATABASE_URL") || env("DATABASE_URL") would let the application handle two database credentials at once.

How would that work @2pmflow, specifically? If it falls back to the second value if the first env var is empty, can you not also just update the only single environment variable to the new value instead?


fine tuned browserSync reload to inject css

Hi,
Instead of a full reload, browserSync now inject the css files.
But when the css ends with .component a full reload is performed, issues with shadow dom I suppose.
Tested with both css and sass
Another way to look at it, is that global css changes in main.css or main.sass get inject, component css get reloaded.
That improve dev experience a little bit.
Another good thing to do, is modify the watch task to not recompile typescript  on each file change, that way the performance is improved.

Thanks for the PR and for the comment! Yeah, it does inject CSS but it is bad practice to have CSS files with global scope (like main.css).
If you include CSS injection, the files associated to the components will not cause refresh of the page and the changed styles won't be applied (they need to be processed by Angular), which is confusing. We already dropped one such change.
I suggest to not merge such feature for now, until we are not able to process the changed component styles with Angular, server-side and be able to inject the emulated-shadow dom CSS

I agree that global css should be avoid, but its not a bad practice.
A global main.css is much less friction for themes. Shadow doom is great to isolate the css for each component, but for the same reason is a headache to use something like boostrap and many others.
The pattern I'm following is to use a main.scss that pick include components from libraries like uikit, or bootstrap and customize its theme. The component has css only for its basic layout, sometimes no css at all. The theme can dynamically change without coupling each component. That way I can customize the css framework, with the advantage to evolve the look and feel for all application, and across applications.
The goal is to let component only with behaviors and structure, and adapt the view to the needs of the application. For that, we need to combine the two technics.
In the case of this pull request, the injection only happens if is not a .component.css, so the behavior is as expected. Maybe a better way to differentiate components css from application css, like filtering by a specific folder, but following the angular conventions, it works :-)
Anyway, I will put on the wiki, or provide a flag to opt for this feature.

Information in the wiki sounds good!


Setup Gorm handler for Password change

Worked on the handler and backend support for password changes
[t:30]

Pulled in new work from main to compare and see if I'm doing this right. Made a few changes and then submitted a pr to confirm with other devs that I'm using correct security protocols for updating the passwords.
[t:20]

Made some changes based on what should be the proper way to do it. I think this will work, will await other dev's opinions on the code in the pr...
[t:25]

Fixed error with gorm handler and dao and added 204 return code
[t:15]

Fixed a possible security issue changed error message to be more specific and tried to debug a future issue that we found in the dao when saving the password. I did some research on prepared statements but I'm not sure if that's gonna work. I have some ideas but I'm not sure if they will work... I started implementing a solution.
[t:45]

Working on the solution, I think we found a good resource here
Having some bugs with it that are tedious to work out...
[t:30]

I think I fixed it!
[t:15]


@types/react-table not working for 7.7.0 and @types/react-table 7.7.3

PROBLEM TLDR:
I am not able to use react-table (getSortByToggleProps method) in typescript project.
CONFIGURATION:
react-table 7.7.0
@types/react-table 7.7.3
typescript: 4.4.2

and also I have files:

tsconfig.json in root dir.
react-table-config.d.ts available on path: './types/react-table-config.d.ts' from root dir.
content of above file is copied from documentation, from here https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-table

and also I added to my tsconfig.json following lines (after several tries without following statements in tsconfig):
    "typeRoots": [
      "./node_modules/@types",
      "./types/react-table-config.ts"
    ]

I imported useSortBy (correclty) and added as option to useTable (correctly).
BUG DETAIL:
I have this bug:
Property 'getSortByToggleProps' does not exist on type 'HeaderGroup<object>'
when using method:
column.getHeaderProps(column.getSortByToggleProps())
and also all interfaces in react-table-config.d.ts has following error:
All declarations of 'Hooks' must have identical type parameters.
and also iwhole import statement in react-table-config.d.ts has this error:
All imports in import declaration are unused
I TRIED ALSO:
I tried also:

renaming react-table-config.d.ts to index.d.ts and changing in tsconfig.json "./types/react-table-config.d.ts" to "./types" (in field typeRoots: [ ... ] in tsconfig
not adding "./types" directory (or react-table-config.d.ts path) to tsconfig.json,
moving react-table-config.d.ts to root directory.

FILE DETAILS:

tsconfig.json:

{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",
    "experimentalDecorators": true,
    "baseUrl": "src",
    "noFallthroughCasesInSwitch": true,
    "typeRoots": [
      "./node_modules/@types",
      "./types"
    ]
// this configuration was tested with and without "typeRoots" field
  },
  "include": [
    "src"
  ]
}

project file:

const ReactTable = () => {
    const {
        getTableProps,
        headerGroups,
        rows,
        prepareRow,
    } = useTable({ columns, data }, useSortBy)

    return (
        <div {...getTableProps()}>

            {headerGroups.map((headerGroup, idx) => {

                const { key, ...headerGroupProps } = headerGroup.getHeaderGroupProps();
                return (
                    <StyledListHeader
                        {...headerGroupProps}
                        key={key}
                    >
                        {headerGroup
                            .headers
                            .map((column, idx) => {
                                return (
                                    <span {...column.getHeaderProps(column.getSortByToggleProps())}>
                                        {column.render("Header")}
                                    </span>
                                )
                                )
                        })}
                    </StyledListHeader>

                )
            })}

{...rest of jsx }
</div>
)}}

I installed react-table yesterday as well and am running into the same issue.
The current documentation around extending declarations provides a generic type signature for various interfaces as similar to the following:
export interface Cell<D extends Record<string, unkown>= Record<string, unkown>, V = any>
  extends UseGroupByCellProps<D>,
    UseRowStateCellProps<D> {}

which conflicts with the actual types in @types/react-table 7.7.3:
export interface Cell<D extends object = {}, V = any>
  extends UseGroupByCellProps<D>,
    UseRowStateCellProps<D> {}

The latter type declaration is warned against by eslint-typescript due to the ambiguous nature of the object type.
While I'm currently unable to use the library, I'm incredibly impressed by the features in the documentation and look forward to being able to try it out. Thanks for all your hard work on this!

Same issue here. I've tried extending the type defs as suggested in some of the other similar issues but I just get compiler errors about conflicting definitions.

having a similar issue with useSortBy
here's a simple reproduction with the latest<EMAIL_ADDRESS>and<EMAIL_ADDRESS>https://codesandbox.io/s/react-table-usesortby-ts-issues-1k7rf


Add Japanese (ja_JP) translation

Hi. Thank you for creating this wonderful plugin!
I just added Japanese (ja_JP) translation regarding to #14
I also fixed some typos that would have been obviously wrong.

Thank you very much!
Both for the typos (specially the missing bracket...) and the new translation :)


(docs) 6.3.3 Release notes

CLA signed by all contributors.

Did you intend for this to remove such a large section of the file?  And if so, and if the intention is to remove older release notes, I'd be inclined to at least keep them for all of the supported branches, which I believe still includes 5.2.x.
Offhand, I might also be inclined to keep them in the repository by just moving them to another file -- i.e. release_notes_1.md or release_notes_upto_5.2.x.md or...  I'm thinking of precedents like Emacs NEWS (https://git.savannah.gnu.org/cgit/emacs.git/tree/etc), libc's Changelog.old/ (https://sourceware.org/git/?p=glibc.git;a=tree), etc. -- so that the older notes are still relatively easy to find, link-to (even if just via git) and read, if/when needed.

Hi @rbrw, yes this change is intentional.
Here is the issue I'm solving by removing the old release notes. Users visiting the release notes page for the latest version of DB have to scroll through a massive TOC to get to the release notes. It's a poor user experience.
The change also aids consistency across the documentation site. If a user is looking for release notes for other supported versions of DB, they can use the product switcher to select the version they're looking for. This is how the release notes work for all Puppet products.
If you'd like to keep a historical log of all the changes made to DB in the repo, then I agree that a Changelog is a good solution.

OK, hmm (speculating) what if we just moved all the release notes to release_notes.X or release_notes_X.Y.md files (depending on what granularity you wanted).  Then (unless we wanted to handle it some other way) we might just symlink release_notes.markdown to the correct version in each branch?  Not sure it's sensible yet, just came to mind...

(And of course my assumption there is that the web pages would just pick up the right changes without any extra effort on that side.)


Pre-Trained Model checkpoints available?

I would like to run the evaluation scrtipt on VCR dataset vcr/val.py, but not sure about the checkpoint files --a-ckpt & --r-ckpt.
Could kindly assist me with this issue.
For the given template:
python vcr/val.py \
  --a-cfg <cfg_of_q2a> --r-cfg <cfg_of_qa2r> \
  --a-ckpt <checkpoint_of_q2a> --r-ckpt <checkpoint_of_qa2r> \
  --gpus <indexes_of_gpus_to_use> \
  --result-path <dir_to_save_result> --result-name <result_file_name>

This is what I am executing:
python3 vcr/val.py \
--a-cfg ./cfgs/vcr/base_q2a_4x16G_fp32.yaml \
--r-cfg ./cfgs/vcr/base_qa2r_4x16G_fp32.yaml \
--gpus 0 1 --result-path ./results/ --result-name eval_vcr \
--a-ckpt ./model/pretrained_model/vl-bert-base-e2e.model

However I am facing the following error:
Traceback (most recent call last):
  File "vcr/val.py", line 218, in <module>
    main()
  File "/home/axe/VirtualEnvs/py3ve/lib/python3.6/site-packages/torch/autograd/grad_mode.py", line 49, in decorate_no_grad
    return func(*args, **kwargs)
  File "vcr/val.py", line 119, in main
    smart_load_model_state_dict(answer_model, a_ckpt['state_dict'])
  File "/home/axe/Projects/VL_BERT/common/utils/load.py", line 16, in smart_load_model_state_dict
    raise ValueError('failed to match key of state dict smartly!')
ValueError: failed to match key of state dict smartly!

This is my ./models directory:
└── pretrained_model
    ├── bert-base-uncased
    │   ├── bert_config.json
    │   ├── pytorch_model.bin
    │   └── vocab.txt
    ├── bert-large-uncased
    │   ├── bert_config.json
    │   ├── pytorch_model.bin
    │   └── vocab.txt
    ├── PREPARE_PRETRAINED_MODELS.md
    ├── resnet101-pt-vgbua-0000.model
    └── vl-bert-base-e2e.model

@Axe-- These pre-trained models mean pre-training on Conceptual-Captions and text-only corpus, not on downstream tasks, like VCR. Please use configs for VCR to fine-tune VL-BERT before you evaluate them on VCR. Thanks!

Oh! Got it. Thank you! :-)

Oh! Got it. Thank you! :-)

Excuse me.What the final checkpoint files are?Are they through training in the Folder“output”?And which should i add following --a-ckpt & --r-ckpt.


[tests-only][full-ci ] use responsexml from HttpRequestHelper instead of featurecontext in test

Description

Previously we got response from featurecontext and inside trait featurecontext couldn't be accessed. The error did not occur since there was a try-catch. So, getting the response from HttpRequestHelper class

Please, elaborate on the cause, effect, and solution in the description.
Also, change the PR title to more suitable one

https://drone.owncloud.com/owncloud/ocis/31247/16/5
runsh: Total unexpected failed scenarios throughout the test run:
apiGraphUserGroup/deleteUser.feature:156

    And as "Alice" folder "Shares/new" should not exist                                       # FeatureContext::asFileOrFolderShouldNotExist()
      Type error: Return value of FeatureContext::asFileOrFolderShouldNotExist() must implement interface Psr\Http\Message\ResponseInterface, none returned (Behat\Testwork\Call\Exception\FatalThrowableError)

This has a test code problem. Please have a look.


Enable automation to add all new org members to the "eveyone" GitHub Team

Background

The AP GitHub org has a team called everyone which is similar to the all-org-members team in the MoJ GitHub Organisation, however adding users to it is a manual process.
Manual process sometimes gets missed so some users can't access some repos which leads to support requests and slows users down.
To address this problem we propose adding similar automation to the AP Org to automatically add users to the everyone GitHub Team.
Approach

Replicate what we have in the MoJ Org, but just with the everyone team.
Acceptance Criteria

[ ] New users to the AP Org are automatically made write members of the everyone team.

Reference
How to write good user stories

Script working now:

https://github.com/moj-analytical-services/operations-engineering/actions/runs/3912270858


Enable Cinternal output.

This should fix master on CI, currently xc7 is broken at HEAD on master.

LGTM.

Waiting for green CI, then will merge


PL and enemy

Updated Player and enemy. Player is now can attack with mouse click

확인했습니다!

확인했습니다!


Fix type conversion in add NS records to panic

Fixes #2

commands based on the v1 API are no longer supported. Will not merge.


Update: Added an expression to get maximum health and an action to change it.

Description
The following were added:

Added an action to change the maximum health of the object.
Added an expression to get the maximum health.

How to use the extension
No response
Checklist

[X] I've followed all of the best practices.
[X] I confirm that this extension can be integrated to this GitHub repository, distributed and MIT licensed.
[X] I am aware that the extension may be updated by anyone, and do not need my explicit consent to do so.

What tier of review do you aim for your extension?
Reviewed
Example file
HealthXyz.zip
Extension file
Health.zip

I have created a PR for this.  Once it is approved it will be merged and active.
https://github.com/GDevelopApp/GDevelop-extensions/pull/523


question about specifications of evaluation

I had an exciting time to travel your codes the last few weeks, and I finally got the below results.

but I have a question about Waymo evaluation code.
How could I check the configuration of these metrics such as "Does it use bev or 3D, does it use @11 or @40 for mAP"
Because in KITTI, there is an option for choosing 'bev' or '3D', but I can't find it in waymo, except "compute_detection_metrics_main" created by binary file.
Summary: How could I check configurations of metrics on Waymo evaluation.

Thanks for your using.
compute_detection_metrics_main calculates 3D IoU@(0.7/0.5/0.5) for Vehicle/Pedestrain/Cyclist.
There is no concepts like R11 or R40 in Waymo. Different from the way in KITTI or COCO, Waymo uses score cutoff to sample data points on the PR curve. Specifically, Waymo samples a data point every 0.01 score from the PR curve (0.99, 0.98, ..., 0.01, 0). So it is more like a "R100" strategy.
BTW, which config did you use to get the results above? The results seem a little strange.

"There is no concepts like R11 or R40 in Waymo. Different from the way in KITTI or COCO, Waymo uses score cutoff to sample data points on the PR curve. Specifically, Waymo samples a data point every 0.01 score from the PR curve (0.99, 0.98, ..., 0.01, 0). So it is more like a "R100" strategy. " --> Thank you for answer.
BTW, which config did you use to get the results above? The results seem a little strange. --> I test "configs>sst>sst_waymoD1_2x_3class_8heads_1f" which little modify your "configs>sst>sst_waymoD1_2x_3class_8heads_3f". And could you tell me what's wrong with the above results? if you are weird about form, it copies from "onenote" which I clean up my results. So It could be a little different from console form.

In your results, the performance of vehicle and pedestrian is a little bit lower (~1AP) while the cyclist has a higher number (~1AP).
I believe your results are basically correctly, but I recommend to use the center version in sst_refactor which is simpler and better.

I want to check your code on the same setting in your paper, so I use the old version. But I agree with your advice. Next time I will use the latest version. Thanks.

In fact, the code we used in our paper is not totally consistent with the code here. The performances are slightly different. For example you may get 1 AP lower in Vehicle and 2 AP higher in Pedestrian. @seonhoon1002

So if you don't mind, could you tell me more detail about the differences between the code and your paper? @Abyssaledge

I am going to update the old config in couple of days.


Add conventions for sorting

FIx type in Filter & Sort Middleware
Extend Middleware Activator by custom paramter
Add Sorting Conventions

Naming of Asc and Desc
Naming of Argument

First half of #1087

@michaelstaib  With the current implementation of MiddlewareActivator we can only inject custom paramater of a type not an abstraction. If we want to inject abtractions like interfaces we cannot longer work with params object[] but rather have to use KeyValuePairs<Type, object> or even a IReadOnlyDictionary<Type, object>


What is the Working Directory During Configure?

Brief Issue Summary
I have a CMake script that sets my project's version using execute_process and a call to Git. My build directory is within the repo (${workspaceFolder}/build$). The script works fine if I run cmake` on the command-line. When I configure via the CMake Tools, the script fails with:
[cmake] fatal: not a git repository (or any of the parent directories): .git
[cmake] CMake Warning at cmake/GitVersion.cmake:6 (message):
[cmake]   Git failed (not a repo, or no tags).

Suggesting that CMake is not being run from either the Workspace directory or the build directory.
Expected:

CMake Tools runs CMake somewhere within my repo

Apparent Behavior:

CMake Tools runs CMake from a different directory

Platform and Versions

Operating System: macOS
CMake Version: 3.19.3
VSCode Version: 1.54.3
CMake Tools Extension Version: 1.6.0
Compiler/Toolchain: Apple Clang

Other Notes/Information
I looked but I couldn't see a setting for the working directory?

It should be the build directory. How do you wire the script? Via "environmentSetupScript" in the definition of your kit? I just inspected the code and I think that for running that script, the cwd is its own path. If that's what you're doing, try to place the script in the build folder as a workaround until provide a solution.
Do you use a different scenario for the script?
Either way, let us know (how you wire the script and if the above workaround helps) and I'll investigate closer.

Apologies for not getting back to you sooner.
I do not use environmentSetupScript. I think I explained poorly by saying "CMake script" - it is a .cmake file that is included in CMakeLists.txt, not something I run separately.
The repo I am trying to configure is here: https://github.com/spinicist/riesling
The included .cmake file is here: https://github.com/spinicist/cmake/blob/2621fa8e2f6bd8f7fc07a6b604b30c3a8180808c/GitVersion.cmake
My build directory is /build. If I run cmake . from a terminal within that directory, it works fine. If I run cmake -B build -S . from within the the top level directory, it runs fine. If I run a Configure within VSCode, it does not work.

Hello - a note that I am still experiencing this problem on Mac. Running a CMake configure from the command-line picks up the version from git perfectly, running within VSCode, it fails.


How does arrow parse its ipc format?

Hi there, I am trying to hack the arrow IPC format, I am confused about how does arrow differentiate between different type in record batch buffers and parse it.

for example, now I store a data frame
name | age | balance
'jack'    | 12.  |  100.23
'Jennie' | 24   | 2000.34

I believe 'jack' and 'jennie' is stored in one buffer
and 12 and 24 are stored in another buffer
100.23 and 2000.34 is stored in another buffer
how does the arrow deserializer know which tools to use to parse the buffer?

the reason why I am hacking the Arrow ipc format is that recently I am implementing a fuse filesystem for vineyard, which is an immutable storage manager that utilize the columnar format as the arrow.
We decided to enable our clients to access vineyard objects by reading from the Arrow ipc format. which means when the client wants to access the objects stored in the vineyard, the fuse file system will searlize the corresponding vienayrd objects on the fly, store it in the fuse process, and provide the serialized Arrow-formatted vineyard objects to clients. However, this approach may lead to heavy memory usage.
We are thinking, is it possible to create a mapping between the Arrow ipc format to the vineyard objects, in terms of the information stored in the vineyard objects' metadata, it's totally possible, especially in terms of the dataframe, we store that in units of column as well.
Theoretically, if a user wants to access the 100 byte to 200 btyes of the Arrow-formatted vineyard objects, conceptually, that's a range of data in the first column, my implementation can realize its conceptual representation from the byte range, and grab the data from vineyard, serialized  data, provide what client wants.
Practically, I haven't found a way to precompute the sizes of each part of the serialized Arrow ipc format for now, given the documentation so far.  After doing some question compression, I raised the question above.

Hey @liusitan, the first message in an Arrow IPC stream should always be a Schema message which describes the actual schema of the following record batch messages. So anything processing an IPC RecordBatch message should already have the expected schema for that record batch.
Then you have the nodes field of the flatbuffer message which is a flattened version of the logical schema. So for example, if you had the following schema:
col1: Struct<a: Int32, b: List<item: Int64>, c: Float64>
col2: Utf8

That Nodes list would be:
FieldNode 0: Struct name='col1'
FieldNode 1: Int32 name='a'
FieldNode 2: List name='b'
FieldNode 3: Int64 name='item'
FieldNode 4: Float64 name='c'
FieldNode 5: Utf8 name='col2'

Each of those FieldNode objects contains the appropriate metadata describing the length of the array and the number of nulls. The recordbatch message also has that buffers list which is a list of the offset and length of the buffers that are sent in the message body. Thus, for the above described example we'd expect the buffers described to correspond to:
buffer 0: field 0 validity bitmap
buffer 1: field 1 validity bitmap
buffer 2: field 1 values buffer (ie: a buffer of int32 values)
buffer 3: field 2 validity bitmap
buffer 4: field 2 offsets (ie: the offsets buffer for the List array, a buffer of int32 values)
buffer 5: field 3 validity bitmap
buffer 6: field 3 values (ie: a buffer of int64 values)
buffer 7: field 4 validity bitmap
buffer 8: field 4 values (ie: a buffer of float64 values)
buffer 9: field 5 validity bitmap
buffer 10: field 5 offsets (ie: the offsets for col2, the utf8 array, a buffer of int32 values)
buffer 11: field 5 data (ie: the data buffer for the utf8 column, all of the string values)

For your provided example:
name | age | balance
'jack'    | 12.  |  100.23
'Jennie' | 24   | 2000.34

The first message in the stream would be the schema:
name: utf8
age: Int32
balance: Float64

the nodes in the RecordBatch message (the second message of the stream) would contain:
FieldNode 0: Utf8 name='name', length=2, nulls=0
FieldNode 1: Int32 name='age', length=2, nulls=0
FieldNode 2: Float64 name='balance', length=2, nulls=0

So now you can parse the buffers because you know the types:
buffer 0: validity bitmap for name column (should be 1 byte)
buffer 1: offsets for name column (should be the int32 values [0, 4, 10])
buffer 2: data buffer for name column (should be 'jackJennie')
buffer 3: validity bitmap for age column (should be 1 byte)
buffer 4: values for age column (should be int32 values [12, 24], ie: 8 bytes)
buffer 5: validity bitmap for balance column
buffer 6: values for balance column (should be the bytes for [100.23, 2000.34], ie: 16 bytes)

Hope that helps

@liusitan the FieldNode's type is coming from the Schema that we already know from the first message (I included the type in my example to help illustrate which node they corresponded to)

Thanks for the lightning response first! got it, I am looking at the schema.fbs now

I guess you are saying that the field in the schema type includes the type info, and according to the Field fbs definition, Field contains

I can use the type underlined above to determine the type of the field node.
I notice it comments that   _ This is the type of the decoded value if the field is dictionary encoded_. what does dictionary encoded mean?  is the example below dictionary encoded
name | age | balance
'jack'    | 12.  |  100.23
'Jennie' | 24   | 2000.34

I can use the type underlined above to determine the type of the field node, right?

Correct!

I notice it comments that _ This is the type of the decoded value if the field is dictionary encoded_. what does dictionary encoded mean? is the example below dictionary encoded...

Dictionary encoding is a specific type of Arrow array that is ideal for large arrays with low cardinality. You can find a full description of dictionary-encoded arrays here in the Arrow docs.

got it thank you!


Ability to define positive/negatives datasets for rules?

It would be super-nice to have ability to define positive and negative datasets within the rule.
Both, self-documentation, testability, regression and quick assurance the rules actually work.
Gitleaks should be validating .toml against dataset_positive/negative before running against codebase.
For example:
[[regexes]]
description = "Cathing xxxx-yyyy strings"
regex = '''"\d{4}-\d{4}"'''
dataset_positive = [
 "1111-1111",
 "2222-2222"
]
dataset_negative = [
 "1111-1111-1",
 "2222-2222-2222"
]

@avishnyakov This could be interesting.
title = "gitleaks config"
verify = true
[[rules]]
id = "gitlab-pat"
description = "GitLab Personal Access Token"
regex = '''glpat-[0-9a-zA-Z\-]{20}'''
example = '''gitlab_token = glpat-00000000000000000000'''

If verify is set then gitleaks would test the rules. verify could be a cli command as well. Something I'll think about

Closing this as there is a feature in the default config generation that accomplishes TP/FP validation. I do not plan on supported the syntax in the issue description


Model predicting attrition rate of employee

kindly confirm my merge request

Must Give a Star to repo for Merging Successfully. Thanks


Optimize the model analysis weekly pipeline

The PR will optimise the model analysis weekly pipeline - #761
The current model_analysis script will generate the unique op tests and running the unique op configuration test model wise instead collect the unique op test configuration from all the models and then extract unique op configuration test across all the models which will avoid running same configuration that are present in multiple models again and again.
For example, if we have add op with operands shape of (1, 32) and (1, 32) in resnet and mobilenet, will run the test only once and populate the test results in both resnet and mobilenet

Great work @chandrasekaranpradeep! I don't see any major issues from code changes. However, I would like to confirm few details before proceeding with further review. That said, can you provide details about achieved results with this change?
Here are a few questions as a guideline:

How long tests are executing now, vs before this change? Please provide details of machine on which you run this.
Summary of workflow changes? E.g. how generation and run work now (generate unique across all models; run only unique and populate details for all variants)
Do we have ability to separate test generation and test runs? E.g. to have a workflow where we generate these tests on weekly, but running them on nightly.
What is the process of including generated op tests as part of the push pipeline?
More detail on how params/constants form model are handled? Do we rely on random tensors now, and can this be swapped easily per need? E.g. debugging PCC issues with original weights instead of ones generated in the runtime.

Other:

@vmilosevic is it possible to have workflow run when the specific part of the code has changed? @chandrasekaranpradeep for example when TVM ref change, to run job to update these generated unique op tests.

@nvukobratTT

How long tests are executing now, vs before this change? Please provide details of machine on which you run this.

I have checked the behaviour of the implementation but haven't noted the execution time before and after the change, will check and let you know here.

Summary of workflow changes? E.g. how generation and run work now (generate unique across all models; run only unique and populate details for all variants)

Summary of previous workflow:

Generate the unique op tests for the models present in the directory path specified by the user(i. e forge/test/models/pytorch):

Collected all the pytest present in the specified directory path
Run the pytest and extract unique op configuration and generate forge module with test functions and additionally export the unique op config test details as excel.

Run the generated unique op config tests and generate markdowns

Run the generated unique op config forge test cases model  wise and generate sub markdown files contains unique operation configurations, pass/fail status for each compiler component, and failure reasons.
After running all the models unique op test, generate root markdown file for summarising the result for all the models.

Summary of the new workflow:

Generate the unique op tests for the models present in the directory path specified by the user(i. e forge/test/models/pytorch):

Collecting and running the pytest and extracting unique op config and generating forge module is similar to the previous workflow but in addition to exporting unique op config test details as excel file, will export the model metadata information which includes module_name, framework name, model params and buffers file path which will be used for extracting unique op configuration across all the models.

Run the generated unique op config tests and generate markdowns.

Instead of running the generated unique op config forge test cases model wise, by utilising the same UniqueOperations class(i.e which is used for extracting unique op config from model), will extract unique op configuration across all the models and run the extracted unique op configuration across all the models and populate the test result to the respective models.
After running extracted unique op config across all the models will generate sub markdown and root markdown files.

Do we have ability to separate test generation and test runs? E.g. to have a workflow where we generate these tests on weekly, but running them on nightly.
What is the process of including generated op tests as part of the push pipeline?
More detail on how params/constants form model are handled? Do we rely on random tensors now, and can this be swapped easily per need? E.g. debugging PCC issues with original weights instead of ones generated in the runtime.

All these question are related to generation of test for nightly from the extracted unique op configuration across all the models, the PR doesn't have implementation for generating test for nightly from extracted unique op configuration across all the models.
The pchandrasekaran/generate_nightly_test branch that I am working has the changes for generating test for nightly which will be later include as part of push pipeline
The idea is to generate nightly test by using the exported unique op config test details excel and models metadata info json files produced from the Generate the unique op tests for the models present in the directory path specified by the user(i. e forge/test/models/pytorch) step in the new workflow
In the model analysis script main function, I have added an option to generate nightly test.
When we enable the option of generating nightly test, after generating unique op test from all the models with xlsx and json files, we are extracting unique op configuration across all the models and then generate nightly test for extracted unique op configuration across models.
Instead of loading actual parameters and constants  from models with process_framework_paremeter method, now the parameters and constants are randomly generated  by  modifying the add_constants method in ForgeModule in forge/forge/module.py and Parameter class in forge/forge/parameter.py and also done some modification in the write_class_defination function in ForgeWritter.
Added recorded_property fixtures in the nightly test function which includes model_name, variant_name, framework_op_name and op_kind
In sum, the model_analysis script will additional generate nightly test with model_analysis_nightly marker and then create a separate PR for the generate nightly test and then we will have some github workflow to run the generated nightly based upon the test results we can remove the failed test cases from the same PR branch and check it and merge it into main.
Whats your thoughts on this nikola?

Genereted nightly test from model analysis script:
nightly.zip

Thanks for the details! Sounds good!

The pchandrasekaran/generate_nightly_test branch that I am working has the changes for generating test for nightly which will be later include as part of push pipeline

Think about how we can include passing ones right away as part of push pipeline, while keeping other part of nightly. Ofc, this is more question for upcoming PR rather then this one. For other details related to futhre PR, let's discuss in our sync tomorrow.


Document RegisterTagNameFunc more

Make sure that you've checked the boxes below before you submit PR:

[x] Tests exist or have been written that cover this particular change.

I noticed a code snippet was often being copy-pasted in the issue tracker, in response to questions about how to get JSON key names to show in error messages rather than Go field names. This PR puts that snippet right into the GoDoc for RegisterTagNameFunc so that it is more discoverable.
@go-playground/admins

Coverage remained the same at 100.0% when pulling 29b73202feec0eed620eb88799c5067ed73229e6 on frou:doc-registertagnamefunc into f8af4b15dbe132b53d3a53e7c3724271040e82e7 on go-playground:v9.


Warning when building go-redis storage

go: warning<EMAIL_ADDRESS>retracted by module author: This version was accidentally released. Please use version 9.6.0 instead.

Nothing too worrisome I imagine just worth bumping the go module soon.

Hey @danielloader this issue will be patched in the #17. Thank you for your patience! 🙏

Hey @danielloader the commit 29b5e6ae4cd7977b4eaf3b04c8a0dc12cf774293 in the PR #17 contains the dep bump. I'll close it once I merged the PR.

Thanks again.


Translations of texts in CDS views (DDLS) do not make it into the git repo

Seems to be missing currently in zcl_abapgit_object_ddls

@mbtools  Could I temporarily set translation_languages (if not already set) with the help of ii_xml->i18n_params( ) and call serialize_lxe_texts() and afterwards empty translation_languages (if it was empty before) and similarily with deserialize?
Upon finish of #4470 we could simply remove the translation_languages calls afterwards.

sounds like a hack ;-). not sure if there are side effects for example in parallel runs.
#4470 are follow-ups but it's already working in general. why not try the LXE logic straight up (maintain the LXE language in settings of course):
* serialize
    serialize_lxe_texts( io_xml ).

* deserialize
    deserialize_lxe_texts( io_xml ).

@mbtools serialize works, but deserialize seems to conflict with the delete and recreate strategy used for DDLS, at the end of the deserialize method in zcl_abapgit_object_ddls the cds view does not exist and thus the texts can't be created.

As a side note: In our EHP8 system the result from SYSTEM_INSTALLED_LANGUAGES and what is shown in SMLT differs (the FM returns approx double the number), in the S/4HANA system this matches.
For testing I used * for "Serialize Translations" in the EHP8 system which lead of cource to a bit more language entries than expected....
What should I use in "Serialize Translations", the SAP two letter codes, ie eg 3f (which is what you meant in https://github.com/abapGit/abapGit/issues/4470#issuecomment-770305929 , or?).

in general we avoid object type specific code outside of the zc_abapgit_object_xxxx classes. maybe you can use the post processing exit until we find something better.
i added a comment to #4470. also sent something via slack.

@mbtools yes, of course, this was just meant as a quick proof of concept that it will work. What do you think of a interface with the deserialize_lxe_texts like call, then we could stay with a loop at this position and test for implementation of the interface and then call the interface method?

@mbtools I want to continue work on this. What do you think instead of IF <ls_obj>-obj IS INSTANCE OF zcl_abapgit_object_ddls. using a marker interface like IF <ls_obj>-obj IS INSTANCE OF zif_abapgit_lxe_texts_postproc.  and having a method deserialize_lxe_texts in the interface and call this method then?

Sorry, I'm a bit short on time currently. Feel free to do a PR. Then we can better see the impact.


Set OIDC manually, just to test if it works

Start Keycloak using the compose file within this repository:

docker-compose -f etc/deploy/compose/compose.yaml up

This PR manually have set the appropriate OIDC parameters manually so you only need to start the server
Start the server

cargo run --bin trustd

Open http://localhost:8080 . You should be redirected to the Keycloak login (username=admin, password=admin123456)

I have tested it and it works without any issues!

This PR was created in response to https://github.com/trustification/trustify-ui/issues/34 and should be closed soon

Closing this PR as it served its original purpose already


Delete plugin auxiliary metadata from files

If found possibility to resolve #18 in minor harm way - just delete auxiliary metadata from files after plugin finishes its work.
So with such fix plugin could be called as many time as needed.
I tried to implement the test for this functionality, but without changing plugins parameter of test function from Object to Array it seems not possible (because this test must use the same plugin .. several times).

With this functionality my current usage looks something like this:
...

metalsmith
  .use($m.jstransformer({
    pattern: '**.html.md',
    layoutPattern: '!**',
  }));

metalsmith
  .use($m.branch('blog/*/**')
    .use($m.wordCount())
    .use($m.betterExcerpts())
  );

metalsmith
  .use($m.jstransformer({
    pattern: '**.html*',
    layoutPattern: 'layouts/**',
  }));

...

Good call, we don't need that cached information. Nicely done! :+1:


[feat] status indicator component

Description
New "status indicator" component that would be injected into the new unified footer for sites looking to report out on site outage.
The current implementation of the indicator shows the operational status across all of status.redhat.com and is not site specific. Notes from early conversations around this as it relates to the unified footer: https://docs.google.com/document/d/1vZ2taPSsG2MnpujdwpXxZvhH7ssnQgfAPVrzTPfaH4A/edit#bookmark=id.vq7rdtmnvsdg
Redhat.com is not currently included on status.redhat.com for reasons:
Per Danielle Smith "However, the complexity around determining what should be displayed on this page is not an XS LoE for our dev and infra teams.  Based on the comments in this thread, and what we learned this morning, it does not make sense to build out the comms and support processes to add it to the status-dot page at this time."
Acceptance Criteria

[X] Design done
[ ] Development done

Image
No response
Link to design doc
https://www.figma.com/file/IoKYfBlrcx2kXIGdC22Gjq/Footer---status-indicators?type=design&node-id=0%3A1&mode=dev
Other resources
some thoughts on development:

if we make the various status texts configurable via slots (with english fallback), then 18n becomes the consumer's responsibility (e.g. the cms)
this being a red hat element, not a pfelement, we can rely on convention and have something like

<rh-site-status site-ids="613,770">   All systems operational </rh-site-status>

Updated issue with Figma link.

@markcaron @hellogreg Can you please check with Kelsey if this is still a priority? Otherwise, proposing to move it to the Chansey release.

@coreyvickery I would say it is still a priority. @kylebuch8 what do you think?

Considering the US holiday calendar, we must delay this important feature to Chansey.

Free to use @zeroedin's CodePen: https://codepen.io/zeroedin/pen/QWoNbzL

@heyMP @zeroedin where are we on this? Are there any blockers?

Closes in PRs aren't closing issues for some reason.