[BUG] Passwordless feature does't set the cloud-type correctly

Describe the bug
Passwordless feature support set cloud-type with spring.datasource.azure.profile.cloud-type, but we don't support spring.cloud.azure.profile.cloud-type. If user set spring.cloud.azure.profile.cloud-type, the feature will fail to get the right cloud-type.
Exception or Stack Trace
Add the exception log and stack trace if available
To Reproduce
Steps to reproduce the behavior:
Code Snippet
Add the code snippet that causes the issue.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):

OS: [e.g. iOS]
IDE: [e.g. IntelliJ]
Library/Libraries: [e.g. com.azure:azure-core:1.16.0 (groupId:artifactId:version)]
Java version: [e.g. 8]
App Server/Environment: [e.g. Tomcat, WildFly, Azure Function, Apache Spark, Databricks, IDE plugin or anything special]
Frameworks: [e.g. Spring Boot, Micronaut, Quarkus, etc]

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

verbose dependency tree (mvn dependency:tree -Dverbose)
exception message, full stack trace, and any available logs

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Bug Description Added
[ ] Repro Steps Added
[ ] Setup information Added

This bug is fixed in this PR https://github.com/Azure/azure-sdk-for-java/pull/31600.

The issue has been addressed in this PR https://github.com/Azure/azure-sdk-for-java/pull/31600.


Roadmap & Todo

There are a couple things that still need to be done and places I want to take this tool:

Validate serialization and deserialization works across the bridge
add logging across the board, both during gen and runtime
improve error DX

improve host error type
structured serialization for results
handle errors even when return type is not result optionally disabled through unchecked

reduce reliance on extern crates in rust runtime code (wasm_bindgen and serde). Move wasm_bindgen macro use into guest-rust and only use exported async fn send<T: Serialize>(T) function
improve integration with Tauri (possibly through a WIP impl of the new IPC routing system?)
switch tauri-sys and try implementing the Tauri API
add optional tracing to gen-host
fork wit-parser and remove worlds & exports
publish to crates.io
explore binary serialization of types instead of JSON
explore adding the stream type defined by wit
explore adding back exports (functions exposed from JS to Rust)
explore platform specific codegen

Moved to TODO.md


Loading Angular-Gannt with Requirejs

Hi,
I am using angular gantt for one of my project. The project uses requireJS for loading all the libraries. I tried loading angular gantt using the requireJS config but it fails to do so.
Does angular-gantt supports requireJS loading mechanism ?
From my preliminary check, I see that the library does not have provision to load it as requirejs module (no AMD check found in source). The thing is, I can load angular-gantt JS (as requireJS will load the non-AMD files using shim) but I would also like to load angular-gantt-plugins using requireJS, but it fails to do so.
Below is my shim configuration for RequireJS,
'angulargantt': {                 deps: ['angular'],                 exports: 'gantt'             },             'angularganttplugins': {                 deps: ['angular','angulargantt'],                 exports: 'angularganttplugins'             }
But I see the following error in console,

Error: [$injector:modulerr] Failed to instantiate module gantt due to:
Error: [$injector:modulerr] Failed to instantiate module gantt.sortable due to:
Error: [$injector:nomod] Module 'gantt.sortable' is not available! You either misspelled the module name or forgot to load it.

I guess the error is valid, because I am trying to load gantt with all the other module dependencies such as (gantt.bounds, gantt.sortable, etc) but it seems angular-gantt-plugins JS is never loaded by requireJS.
Any idea on how to fix this issue ??

I don't know requireJS, sorry but I can't help for this one.

@Toilal
I was able to do a kind of hack to achieve the same.  I made it work by enclosing the lib code in
define([]{
})

Require JS expects each JS file to be a module so I wrapped it as one.
Thanks for your reply thought !


Allow chunk encoded HTTP requests Fixes #1094

PEP3333 only requires a limited stream if CONTENT_LENGTH is present.

Closing in favor of #1126 which still uses safe_fallback if no max_content_length is configured. Thanks for getting this started.


[BUG] ASP.NET 4.7, ServiceBusProcessor.StartProcessingAsync() crashes website (The process was terminated due to an internal error in the .NET Runtime)

Library name and version
Azure.Messaging.ServiceBus 7.12.0
Describe the bug
We want to integrate ServiceBus into our old ASP.NET 4.7 MVC application. We do not consider upgrading to the newest .NET because of effort considerations.
The most straightforward integration crashes our application. The same code works for a console application. We get The process was terminated due to an internal error in the .NET Runtime.
link to a repository where you can test it.
Here's a sample code:
            var fullyQualifiedNamespace = "qcash-concert2-test.servicebus.windows.net";
            var queueName = "TestQueue";
            var credentials = new DefaultAzureCredential(new DefaultAzureCredentialOptions()
            {
                ExcludeAzureCliCredential = false,
                ExcludeEnvironmentCredential = false,
                ExcludeManagedIdentityCredential = false,
                ExcludeSharedTokenCacheCredential = false,
                ExcludeInteractiveBrowserCredential = true,
                ExcludeVisualStudioCodeCredential = false,
                ExcludeVisualStudioCredential = false,
            });

            var serviceBusClient = new ServiceBusClient(fullyQualifiedNamespace, credentials, new ServiceBusClientOptions
            {
                RetryOptions = new ServiceBusRetryOptions
                {
                    MaxRetries = 5,    //The maximum number of retry attempts before giving up
                    Mode = ServiceBusRetryMode.Exponential,        //The approach to use for calculating retry delays
                    MaxDelay = TimeSpan.FromMilliseconds(90000)
                }
            });

            var administartionClient = new ServiceBusAdministrationClient(fullyQualifiedNamespace, credentials);

            if (await administartionClient.QueueExistsAsync(queueName, CancellationToken.None) == false)
            {
                var queueOptions = new CreateQueueOptions(queueName)
                {
                    DeadLetteringOnMessageExpiration = true,
                    EnableBatchedOperations = true,
                    EnablePartitioning = false,
                    MaxSizeInMegabytes = 1024,
                    RequiresDuplicateDetection = false,
                    RequiresSession = false,
                };

                queueOptions.AutoDeleteOnIdle = TimeSpan.FromMinutes(60);

                _ = await administartionClient.CreateQueueAsync(queueOptions, CancellationToken.None);
            }

            var processor = serviceBusClient.CreateProcessor(queueName, new ServiceBusProcessorOptions()
            {
                AutoCompleteMessages = true,
                MaxConcurrentCalls = Environment.ProcessorCount,
                PrefetchCount = Environment.ProcessorCount * 100,
                ReceiveMode = ServiceBusReceiveMode.ReceiveAndDelete
            });

            processor.ProcessMessageAsync += (args) =>
            {
                return Task.Run(() =>
                {
                    Thread.Sleep(1000);
                });
            };

            processor.ProcessErrorAsync += OnMessageProcessingException;
            await processor.StartProcessingAsync(CancellationToken.None);

            await Task.Run(() =>
            {
                Thread.Sleep(5 * 1000);
            });

Logs from Event Viewer
Application: iisexpress.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFC367F3D99 (00007FFC367F0000) with exit code 80131506.

Faulting application name: iisexpress.exe, version: 10.0.25095.1000, time stamp: 0x7d00e3ab
Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e
Exception code: 0xc0000005
Fault offset: 0x0000000000003d99
Faulting process id: 0xc584
Faulting application start time: 0x01d929d2fecf87d7
Faulting application path: C:\Program Files\IIS Express\iisexpress.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 137ef970-d27f-4f0b-b506-0f4879426b6d
Faulting package full name:
Faulting package-relative application ID:

Expected behavior
The website doesn't crash
Actual behavior
The website crashes
Reproduction Steps

Clone repository
Start web application. It's an asp.net MVC template application.
Open the Contact tab

Environment
.NET SDK (reflecting any global.json):
Version:   6.0.401
Commit:    0906eae6f8
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19044
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\6.0.401\
global.json file:
Not found
Host:
Version:      6.0.13
Architecture: x64
Commit:       1af80ba017
.NET SDKs installed:
5.0.301 [C:\Program Files\dotnet\sdk]
5.0.408 [C:\Program Files\dotnet\sdk]
6.0.101 [C:\Program Files\dotnet\sdk]
6.0.113 [C:\Program Files\dotnet\sdk]
6.0.308 [C:\Program Files\dotnet\sdk]
6.0.401 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.16 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
VS 2022 Version 17.3.5

We tried to run the same code with the latest .NET and it works (doesn't crash). So, it's a .NET framework related issue.

Hi @mykhailopylyp.   Thank you for reaching out and we regret that you're experiencing difficulties.   Would you please share the exact version stamp from your .NET Framework environment on the host so that we can    If you are able to capture and share a dump, that would also be very helpful.
I'd also appreciate your perspective on what the application is intended to do.   In your home controller, you're creating and starting a processor and then returning.  After you return your view, the processor and client will go out of scope without being stopped nor the connection closed gracefully.   Depending on the host and its state, the callback to the error handler may cause a fault since the instance of the class itself is out of scope.

Hi @jsquire,
Environment.Version = {4.0.30319.42000}.
Dump file.
iisexpress.exe.3444.zip
We need service bus to integrated with third party service (sending and receiving messages). I tried to make the example as simple as possible to demonstrate the issue (we use service bus instances correctly in our application).
Have you tried to run the repository I've created? It is reproducible at least on two machines.

Hi @mykhailopylyp.   I've had a chance to dig into the memory dump and the sample code that you provided.  The root cause of your crash is how the application is using the processor.   In short, the application code is a race condition which is likely to intermittently reproduce the crash and may manifest more frequently on some hosts than others.
This isn't something that the SDK can guard against or mitigate, it requires adjustments in the application.  I've provided some mitigation suggestions below.
Root Cause Details
When the crash manifests, the sequence of events is:

IIS creates an instance of HomeController to service a specific request and routes that request to the Contact method.

The Contact method creates an instance of the processor  and configures it to use  instance methods in the controller class as event handler callbacks.

The Contact method then starts the processor, which spins up a set of background tasks responsible for reading messages and invoking the event handlers.

The Contact method  then returns a view without stopping the processor, so those background tasks are still running.

The executing instance of HomeController goes out of scope, taking the processor it created and the methods assigned to use for handling events with it.

When the background task reading Service Bus messages attempts to raise the event, the .NET runtime isn't able to resolve the address of the callback that was registered, which causes an access violation and crashes the process.

The crash manifesting depends on the connection to Service Bus being established and background tasks starting before the controller instance goes out of scope as well as the availability of messages to be read.
Crash Dump Details
The inability for the runtime to resolve the methods registered as event handlers is represented in the dump when analyzing the exception and the CLR stack.
Root message:  Failed to request MethodData, not in JIT code range
EXCEPTION_RECORD:  (.exr -1)ExceptionAddress: 00007ffcfb9c3d99 (clr!JIT_IsInstanceOfInterface+0x0000000000000009)
  ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000001
NumberParameters: 2
   Parameter[0]:<PHONE_NUMBER>000000
   Parameter[1]:<PHONE_NUMBER>000001
Attempt to read from address<PHONE_NUMBER>000001

PROCESS_NAME:  iisexpress.exe
READ_ADDRESS:<PHONE_NUMBER>000001
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

Mitigation Strategies
The ServiceBusProcessor is not a good fit for the pattern in which the application is attempting to use it.  If you need to have a set of messages read as part of the Contact call, ServiceBusReceiver would be a better fit, the key difference is that it uses a pull-based pattern rather than push.  This allows the application full control over when reads happen and the ability to ensure that processing and clean-up are complete before the view is returned.
If you're looking to have messages being processed continually, I'd suggest looking into using an implementation of BackgroundService from the hosting extension package.  Though most articles discuss using it in the context of ASP.NET Core, the extensions package supports net462 as a target and would work with your .NET 4.7.2 environment.

/unresolve
Hi @jsquire,
Thank you for your help! I believe I encountered a different issue that is specified in the root cause.
I've updated an example to demonstrate it. Made ServiceBusClient and ServiceBusProcessor as static members as well as delegates for processing messages and moved initialization to Application_Start. So, now all objects that are potentially needed for message processing have a lifetime of the application.
    public class MvcApplication : System.Web.HttpApplication
    {
        public static ServiceBusClient ServiceBusClient { get; set; }
        public static ServiceBusProcessor Processor { get; set; }

        protected void Application_Start()
        {
            AreaRegistration.RegisterAllAreas();
            FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
            RouteConfig.RegisterRoutes(RouteTable.Routes);
            BundleConfig.RegisterBundles(BundleTable.Bundles);

            var fullyQualifiedNamespace = "qcash-concert2-test.servicebus.windows.net";
            var queueName = "TestQueue";
            var credentials = new DefaultAzureCredential(new DefaultAzureCredentialOptions()
            {
                ExcludeAzureCliCredential = false,
                ExcludeEnvironmentCredential = false,
                ExcludeManagedIdentityCredential = false,
                ExcludeSharedTokenCacheCredential = false,
                ExcludeInteractiveBrowserCredential = true,
                ExcludeVisualStudioCodeCredential = false,
                ExcludeVisualStudioCredential = false,
            });

            ServiceBusClient = new ServiceBusClient(fullyQualifiedNamespace, credentials, new ServiceBusClientOptions
            {
                RetryOptions = new ServiceBusRetryOptions
                {
                    MaxRetries = 5,    //The maximum number of retry attempts before giving up
                    Mode = ServiceBusRetryMode.Exponential,        //The approach to use for calculating retry delays
                    MaxDelay = TimeSpan.FromMilliseconds(90000)
                }
            });

            var administartionClient = new ServiceBusAdministrationClient(fullyQualifiedNamespace, credentials);

            if (administartionClient.QueueExistsAsync(queueName, CancellationToken.None).Result == false)
            {
                var queueOptions = new CreateQueueOptions(queueName)
                {
                    DeadLetteringOnMessageExpiration = true,
                    EnableBatchedOperations = true,
                    EnablePartitioning = false,
                    MaxSizeInMegabytes = 1024,
                    RequiresDuplicateDetection = false,
                    RequiresSession = false,
                };

                queueOptions.AutoDeleteOnIdle = TimeSpan.FromMinutes(60);

                var _ = administartionClient.CreateQueueAsync(queueOptions, CancellationToken.None).Result;
            }

            Processor = ServiceBusClient.CreateProcessor(queueName, new ServiceBusProcessorOptions()
            {
                AutoCompleteMessages = true,
                MaxConcurrentCalls = Environment.ProcessorCount,
                PrefetchCount = Environment.ProcessorCount * 100,
                ReceiveMode = ServiceBusReceiveMode.ReceiveAndDelete
            });

            Processor.ProcessMessageAsync += OnMessageProcessingAsync;

            Processor.ProcessErrorAsync += OnMessageProcessingException;
        }

        private static Task OnMessageProcessingAsync(ProcessMessageEventArgs args)
        {
            return Task.Run(() =>
            {
                Thread.Sleep(1000);
            });
        }

        private static async Task OnMessageProcessingException(ProcessErrorEventArgs args)
        {
            if (args == null || args.CancellationToken.IsCancellationRequested)
                return;

            if (args.Exception is ServiceBusException serviceBusException
                && serviceBusException.Reason == ServiceBusFailureReason.MessagingEntityNotFound)
            {
                // await ServiceBusFactory.CreateQueueAsync(_processor.FullyQualifiedNamespace, args.EntityPath, _queueTimeToLive, CancellationToken.None).ConfigureAwait(false);
            }
        }
    }

        public async Task<ActionResult> Contact()
        {
            await MvcApplication.Processor.StartProcessingAsync(CancellationToken.None);

            await Task.Run(() =>
            {
                Thread.Sleep(5 * 1000);
            });

            ViewBag.Message = "Your contact page.";

            return View();
        }

Updated example.
New dump file
iisexpress.exe.26172.zip

@mykhailopylyp.   Can you please detail the exception that you're seeing with your new example?   At a glance with the sample code, you'll throw every time you call your Contact method except the first.   You cannot call StartProcessingAsync on the processor when it's already running.
I'd suggest that you consider adding some try/catch block around the application code and inspect the exceptions rather than allowing the process to crash.  The error details will help you better understand the pattern of exceptions that you're seeing.

@mykhailopylyp I'm a community member and regular contributor to the Azure .NET SDK. Maybe I can help you with some more guidance around using Azure Service Bus within MVC applications as well as in general setting up messaging infrastructure on top of Azure Service Bus for your PoC.
Since I could not find your contact details on Github I'm reaching out here. Feel free to send me an email at "daniel dot marbach at particular dot net" or reach out to me over twitter or linkedin.

Hi @mykhailopylyp.   At this point, I'm confident that this is an application issue and not something with the SDK itself.   The patterns that you're using aren't recommended and are susceptible to the types of issues that you're running into.  There's not much more that we can offer outside of my previous suggestions to mitigate and explore the exception:

It seems from your scenario like the processor is not the best type for what you're looking to do.  I'd suggest looking into a shared instance of the [ServiceBusReceiverClient](hhttps://learn.microsoft.com/dotnet/api/azure.messaging.servicebus.servicebusreceiver?view=azure-dotnet) that will allow you to pull messages on-demand when your Contact method runs.

If you're set on having messages being processed continually in the background, I'd suggest looking into using an implementation of BackgroundService from the hosting extension package.  Though most articles discuss using it in the context of ASP.NET Core, the extensions package supports net462 as a target and would work with your .NET 4.7.2 environment.  That is the recommended way to host long-running services.

I'd strongly suggest following the guidance from Processing Unhandled Exceptions and implementing the [Application_Error](https://learn.microsoft.com/aspnet/web-forms/overview/older-versions-getting-started/deploying-web-site-projects/processing-unhandled-exceptions-cs#retrieving-information-about-the-unhandled-exception) handler to help capture and understand the pattern of exceptions that you're seeing.

I'd also suggest that you consider adding some try/catch block around the application code to allow you to inspect and understand exceptions rather than allowing the process to crash.

Since I've already looked over the dump and sample, I'll offer analysis one last time.  The latest implementation still attempts to call StartProcessingAsync multiple times, as the StartedProcessing variable is never set to true - I believe that L42 was meant to do so, but has a typo.  (see below)
Unfortunately, even if L42 is fixed, the application is still likely to crash as the implementation is not thread-safe and the Contact method may be called concurrently.  This would result in intermittent attempts to start the processor twice.  As mentioned in the mitigations, persistent background processing should be performed in a hosted service, and the processor should be managed from there rather than the controller.


Found and fix a mount issue with find

Found and fix a mount issue with find when using a named component e.g. find('Foo')
Added test case to highlight the issue
fixed someone else's lint issues too

Thanks - could you squash these two commits?

@ljharb Ok squashed

@CurtisHumphrey thanks for finding this bug!  I'm not sure we should be using the ShallowTraversal helpers with mount, though.  Can you pull in MountedTraversal instead and use the instHasType helper function and see if that works?

@lelandrichardson The instHasType helper in MountedTraversal is where the problem was. The same logic from ShallowTraversal's nodeHasType solved the problem and I was trying to keep it dry.  I did not find anything in MountedTraversal that did the same check

@CurtisHumphrey we should be adding code to the instHasType helper, then. We should try not to mix the logic between MountedTraversal and ShallowTraversal.

@lelandrichardson So you would prefer copy any paste? If so I can do that. Or I guess we could move the function into the utils file

@lelandrichardson ok, I move the function into util, rebased and squashed

@CurtisHumphrey it looks like you might have added some Sublime project files to your commit.

@aweary, remove them oops.

Looks legit. Thanks!


Refactor SOCI index builder code into a separate module.

Issue #, if available: #128
Description of changes:
Refactor SOCI index builder code into a separate module.
Motivation: to allow reusing the index builder code in other projects (issue #128).
This PR contains minimal change to existing soci_index.go. If this PR is accepted, we'll have another follow up PR that replaces existing index builder code with the newly created module.
Testing performed:
Testing by writing an example code and use the module locally to build soci index for a pulled image
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you run make add-ltag to add headers to new files?


docker-compose up/down does not pick up changes to pipeline/controller code

After I pulled the latest changes to fix a bug in the pipeline controller logging, the docker version did not work until I used docker image rm to delete the old docker image, which is not a step I remember seeing in other projects. Is it possible to streamline this?

Thanks for reporting. My reading of the documentation is that this is probably as easy as dropping the image attribute here (I have not tried it yet). I'll send a PR to fix both this and #487.
As a side note: If we want to create and release a docker image for pipelines+controller at some point, we should provide a compose file (for single machine deployment) where it only has the image attribute and no build.


Tooltip (5/14)

We'll need to figure out the best approach doing building a tooltip that works at various positions in the viewport. For example, if we have it positioned for "top", we need to be smart enough to switch to "bottom" if you're scrolled up to the very top of the viewport.
Popper is used by BS for this (I think) and probably other solutions exist. I'm pretty sure we don't want to have this JavaScript in AgnosticUI core (since our whole philosophy is to only support primitives).

[ ] CSS
[ ] React
[ ] React Examples
[ ] Vue 3
[ ] Vue Examples
[ ] Svelte
[ ] Svelte Examples
[ ] Angular
[ ] Angular Examples
[ ] Site Docs
[] Publish frameworks

Look at https://github.com/chinchang/hint.css
Does it do viewport calculations? Seems not. Maybe it's enough to show how a 3rd party solution could be added if viewport position based "flipping" is needed?

The whole viewport calculations side of this is leading me to believe that this is either an "addon" or we just shouldn't handle tooltips in AgnosticUI (and doesn't belong in core).
This is a tough one because most web apps will need a tooltip solution so it would "be nice" to handle here. But, it would seem better to perhaps link out from docs in a "Why no Tooltips?" part of an FAQ.
For posterity, here are some popper implementations we can link to:

https://valgeirb.github.io/vue3-popper/
https://popper.js.org/react-popper/
https://svelte.dev/repl/6ef53f4882324d21a14f49ec68cf60f7?version=3.47.0 (svelte repl with example use:popper action to use popper core

Removing per my last comment. Added the reason for no Tooltip to the FAQ


Fixed #32144 -- Made makemessages remove temporary files when locale path doesn't exist.

The error case "Unable to find a locale path to store translations..." didn't clean up its files.
https://code.djangoproject.com/ticket/32144#ticket

I thought of just adding it in the one missing place. But that's what previous developers have done, and they missed one place which is why this PR exists. The try-finally block ensures that anyone who adds a new raise won't have to step on this mine. That's the entire reason try-finally exists...

Tests are required

Are you serious right now? There are no tests for the old code, and this is an improvement. Are you saying I need to make a test that sets up a filesystem, some files, runs this entire code path, and then checks for the non-existence of temporary files? This seems like a huge waste of CI resources as this will slow down the test suite for all eternity.

That's the entire reason try-finally exists...

Yes, but it make code less readable to wrap 150+ lines where an error can appear in the last 20, IMO.

Are you serious right now?

Yes, it looks feasible. We need a test if we don't want to introduce a regression in the future.

Are you saying I need to make a test that sets up a filesystem, some files, runs this entire code path, and then checks for the non-existence of temporary files? This seems like a huge waste of CI resources as this will slow down the test suite for all eternity.

Not really, you don't need to do most of these things. Please check i18n/test_extraction.py for an inspiration.

Yes, but it make code less readable to wrap 150+ lines where an error can appear in the last 20, IMO.

Maybe. This is what the code is actually doing though. If the indent is really a big problem, we can make a private _process_locale_dir that doesn't do the cleanup, and the public process_locale_dir has the try/finally and calls _process_locale_dir.
And you're wrong btw, the error can come as early as the very first line inside the for loop. Think of it like this: what if we create a temporary file, add it to the list, and then we start over with the for loop. Now there's an error at the very beginning, like maybe self.stdout.write raises an exception? Now you have temporary files on disk.

Not really, you don't need to do most of these things. Please check i18n/test_extraction.py for an inspiration.

Seems like that test does literally this :(
Yea ok, I guess it's not a big extra cost to check the non-existance of a file here. Seems rather iffy though, as really that check should be on all the different code paths that are possible through makemessages, including future code paths not dreamt of yet... Are you satisfied with a check for just the code path I am fixing?

Yes, but it make code less readable to wrap 150+ lines where an error can appear in the last 20, IMO.

Maybe. This is what the code is actually doing though. If the indent is really a big problem, we can make a private _process_locale_dir that doesn't do the cleanup, and the public process_locale_dir has the try/finally and calls _process_locale_dir.

It's not about indentation. try ... finally should be small and contain only code that can actually raise an exception, IMO. We don't need to consider theoretical and unsupported paths.

And you're wrong btw, the error can come as early as the very first line inside the for loop. Think of it like this: what if we create a temporary file, add it to the list, and then we start over with the for loop. Now there's an error at the very beginning, like maybe self.stdout.write raises an exception? Now you have temporary files on disk.

Not really, you don't need to do most of these things. Please check i18n/test_extraction.py for an inspiration.

Seems like that test does literally this :(
Yea ok, I guess it's not a big extra cost to check the non-existance of a file here. Seems rather iffy though, as really that check should be on all the different code paths that are possible through makemessages, including future code paths not dreamt of yet... Are you satisfied with a check for just the code path I am fixing?

Yes, should be fine, but I also would be happy to review tests for "...future code paths not dreamt of yet." :moon:  if you believe they will make new tests more bulletproof. Thanks for you understanding.
I have a gut feeling that you don't like code reviews. We're all here to make Django better.

It's not about indentation. try ... finally should be small and contain only code that can actually raise an exception, IMO.

You mean self.stdout.write can't raise? And all those string formatting operations can't raise? build_file_class can't raise? I think I can go on, but I stopped at this point.
I also disagree with your statement in its entirety. try/except I would accept that it should be used for small isolated blocks, but this is try/finally, a totally different construct made for exactly the purpose I am using it for.

We don't need to consider theoretical and unsupported paths.

Sure. Except those aren't covered by the existing code, or the the suggestion you made. Not to mention the dry violation, or the risk of the clean up being modified and then not being updated in all the places. Which is why we have try/finally in python.

Yes, should be fine

Ok.

but I also would be happy to review tests for "...future code paths not dreamt of yet." 🌔 if you believe they will make new tests more bulletproof.

I can do that. With the try/finally block. Again, that's why it exists.

I have a gut feeling that you don't like code reviews. We're all here to make Django better.

Code reviews are fine. It's just that I'm fixing the problem and you're suggesting I make all the same mistakes that caused the problem in the first place.

This fat block is about 1/3 of the function. And yes, with else: return it could leave temp files on disk theoretically:
https://github.com/django/django/blob/edd3c82df4a30a6c1c4dbe1d905dd89d65fbf1c6/django/core/management/commands/makemessages.py#L525-L556
but only if there's a poor refactoring in the future, since this would have raised before the temp files were created:
https://github.com/django/django/blob/edd3c82df4a30a6c1c4dbe1d905dd89d65fbf1c6/django/core/management/commands/makemessages.py#L323-L325
I hear @boxed wants to make future development completely safe, but I also hear @felixxm that wrapping the whole thing just to make future development safer brings readability downsides. My instinct was going to be to suggest a sweet spot in the middle, but as a practical matter that fat block in the middle of the function is so easy to skim I don't know that I would bother having separate try blocks above and below.

@jacobtylerwalls notice that I suggested the middle ground of introducing a private method without the try/finally and the public function just calls that

Ah. And also note that my proposed change isn't just safe against future refactoring. It's also safe against the myriad of other reason the code can exit without cleaning up the temp files. Like I already mentioned above.

TBH I agree with @felixxm. We have to maintain this code, and from experience I'd say that it's read more often than theoretical issues actually appear. Can we make the try smaller as per the initial review please. Thanks both.

What do you mean make the try smaller? How small? The entire reason this bug existed in the first place was because the code didn't use any of the two python methods you should be using for clean up: try/finally or with. You can't make the try smaller without also re-introducing this bug.

If you think the diff is hard to read look at this: https://github.com/django/django/pull/13609/files?w=1

https://github.com/django/django/pull/13609#pullrequestreview-516561055

@carltongibson I already said why that fix isn't sufficient. For example we know that build_file.preprocess() can raise. How do we know? Because there's already a try/except around it! So we KNOW that there's a temporary file leak there too. So the try/finally has to cover that too, which means it has to cover the entire for loop. Which is what my PR is doing.

Oh, and https://github.com/django/django/pull/13609/files#diff-f6dcf84eeecbbfbad63c316715f09e3eaf55784c75295e97a7fa57f424a52205R564 for example. The more you look, the more you find.

For example we know that build_file.preprocess() can raise. How do we know? Because there's already a try/except around it!

I'm sorry, but it's hard to take this argument seriously. The code you are referring to is the following:
https://github.com/django/django/blob/edd3c82df4a30a6c1c4dbe1d905dd89d65fbf1c6/django/core/management/commands/makemessages.py#L514-L522
In this case, a specific exception is being raised and suppressed. You cannot conflate that to assume that all manner of other exceptions are going to be raised. It makes more sense to reason about the function itself:
https://github.com/django/django/blob/edd3c82df4a30a6c1c4dbe1d905dd89d65fbf1c6/django/core/management/commands/makemessages.py#L98-L115
In there, yes, I can see two potential problems. We can either fail to read or fail to write. On quick inspection I would imagine that failing to write would happen on the first file being built as the directory in the work path is the same. So then there would be nothing to clean up... As for reading I could imagine a problem maybe with permissions, but then you arguably have bigger problems than some left over temporary files and this is an external problem.
Please can we calm this down a little bit - the tone comes across a bit too aggressive. The fellows work hard to try and accommodate all of our improvements but they are also responsible for maintaining the project long after we've had our pull requests merged. We contributors may sometimes disagree - @carltongibson and I often have different points of view :wink:  -  but we need sometimes need to compromise or know when it's not worth fighting a battle over something.
If you can come up with a concrete, not contrived, examples where you can make this fail through other paths in the form of one or more unit tests, then you may be able to make your case stronger. @felixxm has said he would review such test cases.
Thank you for taking the time to work on this improvement to Django.

In this case, a specific exception is being raised and suppressed.

And we know this is a totally exhaustive list of all exceptions that can be raised how? This is a rhetorical question obviously.

If you can come up with a concrete, not contrived, examples where you can make this fail through other paths in the form of one or more unit tests

You mean in addition to the case I already identified? I am submitting this PR because I got these temporary files on disk multiple times already and it took me a while to figure out where they came from. This is not a "contrived" example. This happened to me multiple times. There is a python construct to do cleanup, in fact there are two: try/finally and with. We can use try/finally here or a with block with for example an ExitStack.

the tone comes across a bit too aggressive.

Yes I realize this. I am having to explain what try/finally is to django core developers it seems. This is an absurd situation.

but they are also responsible for maintaining the project long after we've had our pull requests merged

This is my point though. I am arguing for using the python feature specifically designed to do cleanup, to do clean up. It will work now, and it will work in the future. It will work for the cases we can foresee, and it will work for the cases we haven't thought about.
So far there's one and only one argument against the try/finally:

try ... finally should be small and contain only code that can actually raise an exception, IMO.

But that's not at all reasonable. That's now what try/finally is for. try/finally is very different from try/except.
In addition I have also suggested that if you won't budge on this issue, we can change the method do just contain:
build_files = []
try:
    self._process_locale_dir(self, locale_dir, files, build_file)
finally:
   for....

This would satisfy the "small and contain only code that can actually raise", and it would remove the extra indent (even though it is claimed that this is irrelevant). It would also minimize the git blame, if you are concerned about that.
You have to be concerned with more than just the big try/finally block since you obviously are more bothered by that than by the fact that the current code has cleanup copy pasted into two places, still has cleanup holes (one of which I got bitten by, and more that I have not yet been bitten by), and is vulnerably to introducing even more bugs in the future.
Like popen_wrapper can raise CommandError too (https://github.com/django/django/blob/9386586f31b8a0bccf59a1bff647cd829d4e79aa/django/core/management/utils.py#L13) which was pointed out to me by someone. I have already pointed this out above.
I am trying to fix the code with a simple change, using a standard python feature specifically made for this use case.

You opened ticket-32144 about files not being cleaned up when hitting the exception raised in this branch:
https://github.com/django/django/blob/4ac2d4fa42e1659f328c35b6b8d4761b3419c11a/django/core/management/commands/makemessages.py#L578-L583
The suggested fix is to perform the same cleanup as raised in this branch prior to the exception being raised:
https://github.com/django/django/blob/4ac2d4fa42e1659f328c35b6b8d4761b3419c11a/django/core/management/commands/makemessages.py#L566-L572
Making that fix will solve the problem.

And we know this is a totally exhaustive list of all exceptions that can be raised how? This is a rhetorical question obviously. Look at what it calls! You have to now audit all of...

Did I say that it was an exhaustive list? Not that I recall.

You mean in addition to the case I already identified? I am submitting this PR because I got these temporary files on disk multiple times already and it took me a while to figure out where they came from. This is not a "contrived" example. This happened to me multiple times.

Nobody is doubting your original issue as described. It has even been pointed out where to fix that case. The issue is that you are proposing umpteen other hypothetical points of failure without a concrete example that they could actually happen.

Yes I realize this. I am having to explain what try/finally is to django core developers it seems. This is an absurd situation.

And this is now just patronising. I'm going to take a step back here as I've said my bit, but I suggest that you engage with the reviewers rather than attack them with vitriol. Please may I also refer you to the code of conduct for your consideration.

Making that fix will solve the problem.

Sure. It won't make the code good though. It will make the code longer, harder to read, and have all the maintainability problems we've already covered, plus the basic fact that it doesn't clearly fix the bug that files are sometimes not cleaned up.

The issue is that you are proposing umpteen other hypothetical points of failure without a concrete example that they could actually happen.

Well this the point of try/finally: that you don't need to even consider any other cases. It makes it super easy to just read the code and then know it does the right thing without reading the code of every function called in the function. The fact is that I don't know if any other exceptions can happen, and it's quite unfeasible to audit the code to find out. Just look at templatize, it's huge and calls lots of functions itself. Cleaning up files is simple: just use try/finally. Auditing hundreds or thousands of lines of code to see if they raise an exception is hard.
In fact, I just found such a case by reading templatize: https://github.com/django/django/blob/d6aff369ad33457ae2355b5b210faf1c4890ff35/django/utils/translation/template.py#L126 I an also reproduce it quite trivially and indeed when I did it created tons of temporary files on my disk that it didn't clean up:
? iommi/templates/iommi/base.html.py
? iommi/templates/iommi/form/actions.html.py
? iommi/templates/iommi/form/bootstrap/row_checkbox.html.py
? iommi/templates/iommi/form/bulma/field.html.py
? iommi/templates/iommi/form/choice.html.py
? iommi/templates/iommi/form/choice_select2.html.py
? iommi/templates/iommi/form/form.html.py
? iommi/templates/iommi/form/heading.html.py
? iommi/templates/iommi/form/image_row.html.py
? iommi/templates/iommi/form/radio.html.py
? iommi/templates/iommi/form/row_checkbox.html.py
? iommi/templates/iommi/form/semantic_ui/radio.html.py
? iommi/templates/iommi/form/semantic_ui/row_checkbox.html.py
? iommi/templates/iommi/query/form.html.py
? iommi/templates/iommi/query/form_toggle_script.html.py
? iommi/templates/iommi/table/bootstrap/paginator.html.py
? iommi/templates/iommi/table/bulma/paginator.html.py
? iommi/templates/iommi/table/header.html.py
? iommi/templates/iommi/table/js_select_all.html.py
? iommi/templates/iommi/table/paginator.html.py
? iommi/templates/iommi/table/semantic_ui/paginator.html.py
? iommi/templates/iommi/table/table.html.py
? iommi/templates/iommi/table/table_container.html.py
? iommi/templates/iommi/table/table_header_rows.html.py

Reproduction is to put {% blocktrans %}{% if foo %}{% endif %}{% endblocktrans %} in a .html file, but not the first one since crashes on the first file will not lead to any temporary files being created prior to the crash.

So, let's summarize:

The entire code block DOES need to be wrapped because it can fail.
If you don't like big try/finally blocks we can make a small such block and call another (private) function in the body of the try.
We can also do the same private function with a with ExitStack(...) construct if you prefer. Personally I think try/finally is simpler.

I will gladly change this PR to any of these suggested changes, and add a test. Is this acceptable?

Strolled by because I got a notification as a watcher. I simply suggest opening a new ticket for the issue raised in https://github.com/django/django/pull/13609#issuecomment-718713695 and describing the motivation for wrapping the entire function there. The fellows stay right on top of ticket triage, which should unclog this a bit. Then this patch's scope will be clearer: it will either be for solving one accepted ticket or two accepted tickets depending on how the new ticket is received--simple as that. Cheers, Jacob

@jacobtylerwalls sorry I didn't understand that. Should I just change this PR to do the wrap of the private function? It's really only one problem here with one solution so I don't see the point of a new issue?

Sure, that would get this moving, at the very least. I understand your view of the root cause here, I'm just suggesting that since the original ticket was accepted before (i.e. without) any discussion of there being a deeper root cause, that temp files are being created without a finally block to catch every scenario, what got this bogged down was that not every thread participant had a clear view of whether there were, as one participant put it, non-contrived examples of additional problems. I think you demonstrated that, but well after the thread went quiet, so I was suggesting a second ticket as a faster way to get a view from the community/mergers before investing more time into this. No harm in having two issues representing different steps to reproduce that happen to be solvable with one code change, but all the same, no harm in running with your idea of updating this patch with your preferred approach and getting another review.

@jacobtylerwalls I've updated this PR to do the private method thing. I looked at the tests but it really feels contrived and silly to make a test for the failure case. It just seems like it's a waste of CO2.

Thanks for the updates. I doubt you'll find support for the view that this doesn't need tests; in fact, that will almost certainly keep this PR stalled (given that community/fellows use the ticket flags Needs Improvement and Needs Tests to determine what's ripe for review).
Continuing this discussion also has a carbon cost. @smithdc1 did some great work minimizing unnecessary runs of the entire test suite by implementing pre-commit hooks.

Yea ok... I noticed there's already a test for a similar scenario, but it's a bit broken. I've improved that test case to be more robust so it covers at least some of the failure cases I've uncovered in this discussion.

Hmm... and the JS tests failed now. I don't seem to have permission to retry it though, but it's quite clearly a flaky test :(

@jacobtylerwalls Fixed the spelling error, and the tests now pass (again there seems to be a flaky js tests).

Could someone take a look at this again? It's a trivial thing and all points above have been dealt with as far as I understand.

Will give it a spin against the patch review checklist soon, meantime--first thing needed is to squash the commits and reword to use the same message as the PR title. Thanks.

Done.


Dimensionality Reduction

Completed dimensionality reduction task.

@sravanth99 Thanks for opening this pull request. Please add MLproject to your contribution

Sure

Added MLproject

@sravanth99 Please add a python file (aka convert your notebook into a script), which will be triggered using MLproject

Done.

Added .py file and modified ML project


Forget password and reset password

Description
Want to work on the functionality of forget password and reset password
Use Case
will improve the user interface and functionalities.
Proposed Solution
No response
Additional Information
No response
Attachments
No response

i would like to fix this issue

@Sooraj002 @tusharyadav11   Kindly find the code-of-conduct of the project Code-of-conduct.
And if you feel this issue is not following the code-of-conduct. Kindly close the issue.
Looking forward to have you as a contributor in the project :) We have a long way to go
p.s: Feel free to join our discord server: https://discord.gg/FEKasAdCrG and assign roles for yourself in the group, The likely-hood of contributing in the project will be really high :)

Hello Sir,
My name is Shivam Kanchole, and I am a fourth-year student at IIT Roorkee. I find this issue both interesting and challenging. Additionally, I have worked on similar projects in the past. Could you please assign this issue to me?
Thank you.
Best regards,
Shivam Kanchole

Hi @tusharyadav11 ,
I would like to work on this issue. Could you please assign it to me?
Thanks!


Not working in app terminated state.

I want to show push notification using pusher. but it is not working when app is terminated.

This is an implementation of pusher channels, it's not intended to work with push notifications. The purpose is to give real time updates in the app. Pusher Channels close connection once the app is terminated thus it cannot be used to send notifications in the background.


feat(fetch): add fetch monitor

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: MaximBalaganskiy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@MaximBalaganskiy  - thanks for contributing to the SDK. can you please add some unit tests for the monitor?

Can do. Looked at the custom test framework and couldn't figure out in a
timeframe I had. Can you point me to an example on how to use addTestAsync?
On Mon., 23 Jul. 2018, 10:52 pm Piyali Jana (MS<EMAIL_ADDRESS>wrote:

@MaximBalaganskiy https://github.com/MaximBalaganskiy - thanks for
contributing to the SDK. can you please add some unit tests for the monitor?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/ApplicationInsights-JS/pull/636#issuecomment-407047267,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADimvEOi-PxFhaTuh-9sX-PXBJsHN85Lks5uJccKgaJpZM4VaSND
.

Check out TestCaseAsync usage in AppInsightsModule.tests.ts. Option is minimal but would it work for you?
For the unused variable, possibly remove it since its not being used currently.
Thanks!

I've updated the monitor to check the disable flag. As for the tests, I couldn't make it work - this project's test harness is a bit hard to get around. Promise stub is missing and to add it I would have to include another package source code into the project, plus typings. Sorry, I'm just not that committed to this PR.
Feel free to close it. I'll be using my monitor for now.

ok, i figured it out for the async in browser useFakeTimers sould be false.... but the question still stands for tests not working in CLI

Ok, all done

Done. I also fixed an issue when an async test could not be run with the setTimeout being overwritten by a stub.

What was causing the issue in IE10? Could that be fixed instead of reverting the PR?

I've just tried the ai.1.0.19.js script in IE10 without a Promise polyfill and had no errors at all.

@MaximBalaganskiy  - issue is in IE8 and below. We could have tried a promise polyfill, but that would have increased the size of the SDK needlessly.

we'll make the implementation as an extension in the SDK 2.0.0. We'll be releasing beta at end of the month.

IE10 does not have Promise either


Trouble Sending BTC - getting Insufficient balance

Issue description

Your Environment

ASGARDEX desktop version:

 win.exe

Operating system and version:

 Win 10  64

Transaction hash(es):

Wallet address(es):  BTC  -  bc1qpeqyxmv99aulxgrx86w7c4ypzleu4z4jxmscha

You can't send anything if the balance of your bc1qpeqyxmv99aulxgrx86w7c4ypzleu4z4jxmscha address is 0 BTC.


fix(index): make wallets from settings.json optional

#1

this should fix #1
@dklombardo can you confirm?


Missing XML Namespace?

Shouldn't templates/form.html have the XML namespace defined to properly use th?
Presently, line 0 has just the html tag
<html xmlns:th="http://www.thymeleaf.org">

Sounds like a great idea. Have time for a PR?

PR #20 implements the fix.


Add some comments

Hi @ImranVirani,
Thank you for the PR!
I don't think the comments you have added to the code are necessary. I have named the functions so that it is clear to the reader what the function does.
Let me know what your thoughts are on that 😊

Hi @ImranVirani,
Thank you for the PR!
I don't think the comments you have added to the code are necessary. I have named the functions so that it is clear to the reader what the function does.
Let me know what your thoughts are on that 😊

Hi @sdushantha,
Makes sense that's fine.

Hi @sdushantha,
Makes sense that's fine.


Add github.com/jedisct1/piknik

https://github.com/jedisct1/piknik

Thank you.

https://github.com/aquaproj/aqua-registry/pull/28720


Removing docker container causing lock up

Note: This has only occurred once but I thought I'd report it in case others experience the same issue.
I tried to run docker kill against a container and it wouldn't stop so I tried docker stop but that didn't work either. Finally, I tried running docker rm which reported that it couldn't remove a running container and then soon after it caused the whole SSH session to freeze. At that point the box was inaccessible via any new SSH connections.
Here's a log from the box:
https://gist.github.com/snormore/20c261a4166d8049e238
And the docker version and info:
$ docker version
Client version: 0.7.5
Go version (client): go1.2
Git commit (client): c348c04

$ docker info
Containers: 5
Images: 27
Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 37

/cc: @snormore

@unclejack I'm getting this on CentOS 7:
[root@server-test ~]# docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock:ro jwilder/nginx-proxy
65641cb2e0f2365eb139df9d11a6d558521c304bfad1520a408cac240ae8db12
[root@server-test ~]# docker ps -a
CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS              PORTS                         NAMES
65641cb2e0f2        jwilder/nginx-proxy   "/app/docker-entrypoi"   4 seconds ago       Up 3 seconds        <IP_ADDRESS>:80->80/tcp, 443/tcp   prickly_yonath
[root@server-test ~]# docker halt 656
docker: 'halt' is not a docker command.
See 'docker --help'.
[root@server-test ~]# docker stop 656
656
[root@docka-test ~]# docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
[root@docka-test ~]# docker ps -a
CONTAINER ID        IMAGE                 COMMAND                  CREATED              STATUS                     PORTS               NAMES
65641cb2e0f2        jwilder/nginx-proxy   "/app/docker-entrypoi"   About a minute ago   Exited (2) 4 seconds ago                       prickly_yonath
[root@docka-test ~]# docker rm 656

After this the box is crashed and I have to restart it. This is running Docker version 1.9.0, build 76d6bc9

I got the same issue but it seems to have something to do with the way the storage is being handled automatically on RHEL boxes:
If you don't have enough LVM or unpartitioned space, docker-storage-setup (which seems to run automatically if /var/lib/docker does not exist) will create some weird setup (I'm guessing some files in /var/lib/docker that get mounted as loop devices and stuck into the device mapper, or something like this).
Once I added a secondary disk to the VM, added DEVS="/dev/sdb" to /etc/sysconfig/docker-storage-setup, stopped docker, run docker-storage-setup and then start the docker service again, everything is peachy because it uses the thin LVM allocation method.

@FlorinAsavoaie Hmm, that's very interesting. I'll be interested to say what some of the Docker team says. This is a pretty big issue for me in a cloud environment where I'm spinning systems up and down. I don't really want to have to add disks to the system.

You don't have to add disks, just make sure you have enough space in the LVM Volume Groups so that Docker can use its default and production ready storage setup for RHEL, which is thin allocated LVM.

The default device mapper configuration uses loopback devices, and is not intended for production usage. We recently added more documentation about picking and setting up storage drivers, see: http://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/ and this page describes device mapper; http://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/


use LocalDateTime and LocalDate for dates?

according to the swagger spec these are formatted without a timezone, but there is an implicit assumption that it is UTC.
so - should a "date-time" field be an Instant, a LocalDateTime or a ZonedDateTime using UTC?

small problem with LocalDateTime: its toString() of course lacks a Zcharacter at the end, which is required by the swagger spec


gfx_window_sdl is not available on crates.io

It's published now! https://crates.io/crates/gfx_window_sdl

thanks @csherratt !


rename wachFlags for Flags

Description of the change:

rename wachFlags for Flags

Motivation for the change:
Was decide not to do this change in the same pr where the lint was introduced. Even though watch.WatchFlags is an internal type, it is embedded in exported types, which means that changing it to watch.Flags is a breaking change which will not affect users since it is not used/exported to them.

@camilamacedo86 This is a breaking change.
Here's an example program that breaks between v0.15.1 and master
package main

import (
	"fmt"
	"github.com/operator-framework/operator-sdk/pkg/helm/flags"
)

func main() {
	hflags := flags.HelmOperatorFlags{}
	fmt.Println(hflags.WatchFlags)
}

Based on our discussion here (https://github.com/operator-framework/operator-sdk/pull/2549#issuecomment-584701697), I think we should revert this.

Hi @joelanford
Regards

Here's an example program that breaks between v0.15.1 and master
package main
import (
"fmt"
"github.com/operator-framework/operator-sdk/pkg/helm/flags"
)
func main() {
hflags := flags.HelmOperatorFlags{}
fmt.Println(hflags.WatchFlags)
}
Based on our discussion here (#2549 (comment)), I think we should revert this.

It is true, technically it is a breaking changing besides I do not see a practical use case of this usage. In this way, the PR is addressing this change with your suggestion.


d_a_player_npc

Matched the regalloc by fixing the inline dComIfGs_setRestartOption(cXyz* i_pos, s16 i_angle, s8 i_roomNo, s8 i_option), to call dSv_player_priest_c::set inside of it, rather than calling that separately afterwards.


pull request for e2e test at 12/12/2016 21:56:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[macOS] just to confirm it works!

Tried with my macOS builds of zcashd v2.0.1 (https://github.com/kozyilmaz/zcash-apple/releases) and Qt 5.11.1. Confirm it works, great job!
$ /Users/loki/Qt5.11.1/5.11.1/clang_64/bin/qmake -v
QMake version 3.1
Using Qt version 5.11.1 in /Users/loki/Qt5.11.1/5.11.1/clang_64/lib
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.13.6
BuildVersion:	17G65
$ clang -v
Apple LLVM version 10.0.0 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
Found CUDA installation: /usr/local/cuda, version unknown

Awesome! Thanks a ton.
I currently don't have access to a Mac, so I haven't been able to test it. Thanks for trying it out.
Was it also able to auto-discover zcashd and connect to it? The code here tries to auto-detect zcashd. Did it work correctly for your builds of zcashd?
Thanks for trying it out.

Also managed to build this on a Mac and works nicely 👍
No, it doesn't get the config file correctly (I set the config manually). On macOS it's in ~/Library/Application Support/Zcash/zcash.conf

Yes, sent a PR https://github.com/adityapk00/zec-qt-wallet/pull/15

Thanks @kozyilmaz. Merged!


ldap traffic is unencrypted between haproxy and container host

Currently the ldap container exposes a plain text port 389 to the outside.  This means that all traffic between the haproxy and ldap container is plain text, which we don't want.
There are two solutions:

(preferrred) loop the ldap traffic also through Traefik; according to @quartje it is also able to handle plain TCP traffic and should be able to do TLS termination.  This is the preferred solution, because it allows us to treat all containers and traffic (HTTP and TCP) identical, and we don't have to expose the ldap container port on the Docker host at all.
let slapd handle the TLS termination and expose an ldaps-port on the container host.  In that case, make sure we expose a non-standard port (e.g., 1636 instead of 636).

No, LDAP traffic flow through traefik and traefik connects to 389 on the container host. Let's discuss when I'm back.

SURFConext test docker host needs extra config:
entryPoints:
  ldaps:
    address: ":636"

Enige uitstaande actie is de LDAP ACL configuratie op de loadbalancer (?) vanuit de SBS config.

Needful config has been completed, needs another set of eyes to look at seeing if it works. Can the dirs on test2 be accessed via LDAP-S.

merged and deployed.  Waiting for acl change in https://jira.ia.surf.nl/servicedesk/customer/portal/1/ISSD-28458

ACL change ticket marked as Done


Queries with params don't seem to work

Example query syntax:
'SELECT "Beach name" FROM beaches WHERE Region = ?, params=("SydneyOceanBeaches", )'
[ISSUE reporting in progress - add environment details & error message]

Hello 👋
It's hard to be sure from your example, but it looks a bit like params=("SydneyOceanBeaches", ) is passed inside the SQL string itself, rather than as a separate argument to the query function.
So it looks like you're trying:
from sqlite_s3_query import sqlite_s3_query

with sqlite_s3_query(url='https://my-bucket.s3.eu-west-2.amazonaws.com/my-db.sqlite') as query:
    with query('SELECT "Beach name" FROM beaches WHERE Region = ?, params=("SydneyOceanBeaches", )') as (columns, rows):
        for row in rows:
            print(row)

when it should be something like:
from sqlite_s3_query import sqlite_s3_query

with sqlite_s3_query(url='https://my-bucket.s3.eu-west-2.amazonaws.com/my-db.sqlite') as query:
    with query('SELECT "Beach name" FROM beaches WHERE Region = ?', params=("SydneyOceanBeaches", )) as (columns, rows):
        for row in rows:
            print(row)

G'day Michal
Thanks for you prompt reply -- yes I was mistakenly passing the params within the SQL query string. It is working well now.
Any thoughts on returning the (columns, rows) as a pandas dataframe? :)

Any thoughts on returning the (columns, rows) as a pandas dataframe? :)

Like this?
import pandas as pd

# ...

with query('SELECT "Beach name" FROM beaches WHERE Region = ?', params=("SydneyOceanBeaches", )) as (columns, rows):
    df = pd.DataFrame(rows, columns=columns)

Oh just realised - were you asking about changing the API of sqlite-s3-query to return a pandas DataFrame? If so: I'm fairly anti:

Right now the dependencies are as minimal as I can make them. I wouldn't want to add to them if I can at all help it (and I've been pondering even if I can remove the http client somehow...)

The API is also a "streaming first" API. By returning an iterable of rows, it means streaming processing, i.e. processing rows while data is still being fetched from S3, and avoiding loading all the results in memory at once, is possible. This doesn't happen for all queries, admittedly, but it's a property I would like to preserve, since I personally use it in another project.

And as above, if someone wants a pandas dataframe and all data in memory at once, it's a 1-liner: df = pd.DataFrame(rows, columns=columns), so even for fairly novice Pandas people, not too tricky.

And if the creation of the dataframe is in client code, the client can pass as many other options to the constructor as they like. There isn't any sort of "hiding" of Pandas features, or making assumptions about what sort of dataframe is needed, since it doesn't use any pandas at all, or then having to copy the data into another dataframe that is more suitable.

Anyway, suspect in any case this is beyond the scope of this particular issue. Closing, but feel free to open another.


Seasocks now compiles in Windows with c++17 and VS2019

I have been as careful as I can about the changes so as to hopefully not break the Linux compile. At least on WSL2 Linux, this code compiles and all tests pass.
Build process is exactly the same for Windows (mkdir build && cdbuild followed by cmake ../) as it is in Linux; except in the resulting build directory there will be Visual Studio solution files that will enable seasocks to be built and debugged in visual studio. Please note I only tried the static library builds.
Steve

Add this to .github/workflows/ci.yml to get CI working:
  build_msvc:
    runs-on: windows-latest
    strategy:
      matrix:
        build_config:
          - {args: "-DDEFLATE_SUPPORT=OFF", config: "Debug"}
    steps:
      - uses: actions/checkout@main
      - uses: actions/setup-python@v2
        with:
          python-version: '3.x'
      - name: Build
        run: |
            cmake . -Bbuild ${{ matrix.build_config.args }}
            cmake --build build --parallel --config ${{ matrix.build_config.config }}
      - name: Test
        run: |
            cd build
            cmake --build . --target test --config ${{ matrix.build_config.config }}
            ctest -D ExperimentalBuild -C ${{ matrix.build_config.config }}
            ctest -D ExperimentalMemCheck -C ${{ matrix.build_config.config }}
            # FIXME: use github actions for coverage: https://github.com/marketplace/actions/codecov

Add this to .github/workflows/ci.yml to get CI working:
  build_msvc:
    runs-on: windows-latest
    strategy:
      matrix:
        build_config:
          - {args: "-DDEFLATE_SUPPORT=OFF", config: "Debug"}
    steps:
      - uses: actions/checkout@main
      - uses: actions/setup-python@v2
        with:
          python-version: '3.x'
      - name: Build
        run: |
            cmake . -Bbuild ${{ matrix.build_config.args }}
            cmake --build build --parallel --config ${{ matrix.build_config.config }}
      - name: Test
        run: |
            cd build
            cmake --build . --target test --config ${{ matrix.build_config.config }}
            ctest -D ExperimentalBuild -C ${{ matrix.build_config.config }}
            ctest -D ExperimentalMemCheck -C ${{ matrix.build_config.config }}
            # FIXME: use github actions for coverage: https://github.com/marketplace/actions/codecov

ci now complains with:
Invalid workflow file : .github/workflows/ci.yml#L51 You have an error in your yaml syntax on line 51
right where I pasted the new job :-(

Thanks! Glad to be of service!
On Fri, Oct 29, 2021 at 5:42 PM offa @.***> wrote:

Looks good, all main issues are addressed and the rest can be cleaned-up
later. 👍
Awesome work @sjk7 https://github.com/sjk7 !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mattgodbolt/seasocks/pull/159#issuecomment-954890447,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZJ7FPX7RZPBGOLV2OGM6TUJLFJBANCNFSM5GNF6LWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Sorry I hadn't merged this earlier! Yay!


Did GOOS and GOARCH get removed from env variables?

My build relied on those two variables being set
https://github.com/conda-forge/zaber-motion-feedstock/pull/7
Did they go away for a good reason?

Yes, you can get them using go env goarch, go env goos.
It was redundant to set them and it would override the users defaults unnecessarily.

@hmaarrfk, if you are looking to use them in your recipes then my suggestion is to use the variants target_gobin, target_goos, target_goarch. They are defined in conda-forge-pinning.

Got it. Thanks!


Chart and graph in popups or tool tips

It would be great if the lonboard library could support plots anad interractive charts

Plots and charts are outside the scope of lonboard. Lonboard is concerned solely with geospatial maps on top of deck.gl.
With jupyter widgets, you can link together multiple widgets, so you can combine existing plotting libraries like plotly or the like with lonboard.


NPE during xml models and mappers generation

During generation xml models and mappers from file:
errorWsdl.txt
NullPointerException was thrown.
Supposedly, the problem is in this piece of code and:

type definition failed to define type and returned null.
In debug this command helped to define type:
type  = element.getSchema().getType(new QName(getNamespaceByPrefix(element, "ns1"), getTypeByElement(element)))
where "ns1" is an element prefix.

fixed by #154


Bug with this module takes us to 403 and forbidden images in BO

As discussed in the forum here:
https://forum.thirtybees.com/topic/5862-403-error-when-attempting-to-save-seo-urls-page/#comment-44562
and here:
https://forum.thirtybees.com/topic/5854-cant-see-enlarged-product-picteres-in-backoffice/#comment-44556
if the following code is present in .htaccess the website have 2 issues:
# start ~ module watermark section
<IfModule mod_rewrite.c>
Options +FollowSymLinks
RewriteEngine On
RewriteCond expr "! %{HTTP_REFERER} -strmatch '*://%{HTTP_HOST}*/admin******/*'"
RewriteRule [0-9/]+/[0-9]+\.jpg$ - [F]
</IfModule>
# end ~ module watermark section

Product images in Product can not be enlarged
When saving in SEO section BO gives 403

@getdatakick said it's not an app issue in one of the threads but maybe it's worth a second look?!

A 403 error is almost 100% of the time generated from mod_security on the server. What you need to do, is set it off again, look at your mod_security logs, find the exception along with your IP address and either disable that rule or whitelist your IP address. I honestly have never seen a 403 error that was not generated by anything other than mod_security, although I am sure it happens.

The .htaccess rule basically says that if watermark module is enabled then nobody can access original images (unless they the request originates from administration page).
This is exactly what watermark module is supposed to do, right? To block access to original (non watermarked) images.
I suspect that your theme (or module) constructs path to original image manually to facilitate zoom effect. But that's wrong. The theme should use $link object to receive url for higher resolution images (use different image type).
Not sure why SEO saving should cause any issues.  Maybe Options +FollowSymLinks ??? I'm not sure why that's in there

Uninstalling the module does not remove the .htaccess code relating to the module.
Removing the .htaccess code above upon uninstall of the module would have solved the problem I had with 403 errors after I uninstalled the module.

It does:
https://github.com/thirtybees/watermark/blob/b01df1bbcceafdb008d92a2d02f6d148635fbf13/watermark.php#L85-L89
If this didn't happen for you, then there must be other reasons, for example:

permissions or ownership of the .htaccess file has changed sometimes in between the module installation and uninstallation
module wasn't uninstalled properly, but simply deleted
somebody modified .htaccess file and removed or modified delimiters that watermark module uses to detect borders of the section.

No Petr. Never assume others are to blame. I neer touch code ever, now I've had to.

No Petr. Never assume others are to blame. I never touch code ever, now I've had to because this was not removed

I don't blame others. I look a the code and try to reason about why it wasn't executed. =
Code to remove .htaccess section exists in the module. This code works properly, I just tested it. If the section was not removed, then that means that this code was either not executed at all (module uninstall was not performed), or was executed but failed. If you indeed uninstalled the module properly, then something must have gone really bad. Either the write to the disk failed (permissions, etc.), or the section delimiters were not found in file. Is there some other explanation?
This is not blaming anyone, this is just explanation what must have happened.

I tested again. Maybe #3 is the root cause of your issue. I managed to reproduce by following steps:

install watermark module
uninstall watermark module
check that .htaccess does not contains watermark section (OK)
install watermark module
go to Preferences > SEO & URL, and hit Save
uninstall watermark module
check that .htaccess does not contains watermark section (FAILED)

The step 5 - saving in SEO & URL - removes leading empty line in .htaccess file. This empty line is part of section delimiter (see issue #3)

Ok thanks for testing further...sounds like youve sussed out the root cause...  The issue for me was fixed by deleting (actually commenting out) the code. So for me I was happy, just a case of ensuring that for others the problem is fixed also as the problem can be significant. Thank for getting it sorted and double testing.


bot not starting

hey i was working on this bot with your script changed token to the bots owner to me and checked everything to be set but i was searching in the dark as there is no help anywhere on the internet,  the bot doesn't want to start up after "node index.js" which i think is how you launch it but i know nothing about java, no error messages just

thanks for the help!

this is the only "code" i've changed

owner too but i wont share my discord ID

That doesn't look like a Discord bot token.

how would one look like?

Found it, changed it to the actual token still doesn't seem to work

Rename .env.example to .env


FZF doesn't exclude hidden directories

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[ ] Linux
[x] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
Lines in my .zshrc
export FZF_DEFAULT_COMMAND="fd -i -p -L -d 4 --type f -E '*Applications*' -E '*Library*'"
export FZF_DEFAULT_OP="--cycle --no-sort"

Here's the directory structure from which I am running cd **<tab> (that intern calls fzf), and fd (the FZF_DEFAULT_COMMAND flavor):
reportaman@reportaman's-Mac-mini temp % tree -a
.
├── .foo
│   └── foo.txt
├── .foo.txt
├── foo
│   └── foo.txt
└── foo.txt

Output of cd **<tab> (isn't .foo in the listing a bug?):

Output of fd -i -p -L -d 4 --type f -E '*Applications*' -E '*Library*:
foo/foo.txt
foo.txt

System information
OS: macOS 11.2 20D64 arm64
Host: Macmini9,1
Kernel: 20.3.0
Shell: zsh 5.8
CPU: Apple M1 (ARM64)

For fuzzy directory completion, you need to implement _fzf_compgen_dir. It doesn't run FZF_DEFAULT_COMMAND. I'll update the README page hopefully to lessen the confusion.

See

https://github.com/junegunn/fzf#environment-variables
https://github.com/junegunn/fzf#settings


Challenges in Finding Consistent Encouragement and Motivational Support

Describe the real-life Issue
Description
1. What is the Issue:
Tech professionals often encounter challenges in finding consistent encouragement and motivational support, leading to feelings of isolation and demotivation.
2. Affected Parties:

Individuals in the tech community seeking ongoing inspiration and support.
Those facing hurdles in their professional journey, such as setbacks or imposter syndrome.
Tech organizations aiming to foster a positive and motivating work environment.

3. Repetitive Nature:
The struggle to find consistent encouragement is recurrent among tech professionals, impacting their morale and productivity over time.
4. Impact:

Decreased Morale and Productivity: The absence of consistent encouragement can lead to decreased motivation and reduced productivity among tech professionals.
Negative Mental Health Effects: Persistent lack of support may contribute to feelings of burnout, stress, and disengagement.
Hindered Innovation: Without a supportive environment, individuals may be less inclined to take risks and explore innovative ideas, impacting overall innovation within the tech industry.

5. What Counts as Contribution:

Creating platforms or initiatives that provide ongoing encouragement and motivation to tech professionals.
Advocating for organizational policies that prioritize employee well-being and motivation.
Cultivating a culture of recognition and appreciation within tech communities.
Establishing regular forums or events dedicated to sharing success stories and motivational content.
Encouraging peer-to-peer support networks to facilitate ongoing encouragement and motivation.
and much more

Who has faced this issue?
Group of people
I have read the CONTRIBUTING.md file

[X] Yes
[ ] No

Contribution Acknowledgement:

Contributor: Mark Techson @MarkTechson

Contributions:  #GoodMorningWithMark and #GoodQuestionWithMark

How does it help:
Mark's consistent daily videos spread positivity and encouragement throughout the tech community, uplifting individuals and imbuing them with a sense of optimism and belief in better possibilities. His messages inspire tech professionals to start their day on a positive note and infuse them with the confidence that they can overcome challenges.
Links:
Mark Techson's YouTube Channel
Mark Techson's Twitter

Thank you, Mark Techson, for your valuable contribution.
This marks a significant step in our efforts towards enhancing better state of mind and career growth!


Possibility of KeyError exception if 'tenant_id' is missing

Without any check directly the keys are accessed, if the keys are not present in context.current it can raise KeyError exception , here we can catch the exception KeyError and pass to neutron,
deal_port , setPortinfo, setNetWorkInfo . check for other applicable functions also if any
log also can be recorded if any KeyError occur, key details can be recorded
line details : https://github.com/libuparayil/networking-huawei/blob/master/networking_huawei/plugins/ml2/ac/driver.py#L408

In bind_port, there is no check for segments, before accessing the segments we can check whether its a valid segment based on the below method
def check_segment(self, segment):
    """Check whether segment is valid"""

    return segment[api.NETWORK_TYPE] in [constants.TYPE_LOCAL,
                                         constants.TYPE_GRE,
                                         constants.TYPE_VXLAN,
                                         constants.TYPE_VLAN]

and access it like below
    for segment in context.segments_to_bind:
       ** if self.check_segment(segment):**
            context.set_binding(segment[api.ID],
                                self.vif_type,
                                self.vif_details,
                                status=n_const.PORT_STATUS_ACTIVE)

line details : https://github.com/libuparayil/networking-huawei/blob/master/networking_huawei/plugins/ml2/ac/driver.py#L551

https://github.com/libuparayil/networking-huawei/commit/a02facb6d6d9a9ca79919ff328d40e43a3e0f563

ok


Brisk parcel simple project setup

Please go through the P2B-simple-setup.md file for a detailed description on how to setup brisk

Was just thinking about this and we should list what stress points this hits for running with parcel, and what it doesn't:
This will make us run in to

Loading markdown (see package with readme)
Inline loaders (fetching changelog raw)
loading mdx (in file packages/mock-package3/docs/extended-info.md )
routing (nav)
routing (external links)

This will not make us run into

Loading with extract-react-types (we are not using the props component anywhere)
Loading our webpack-injected components ( <Props /> and <Example /> that we make globally available
routing (internal links)

Looks good! One question... The PR is asking to be merged into master, but do we plan to incrementally add Parcel to Brisk or should we have a long running branch where we do our Parcel work and merge that into master once it's all done? If we do have a long running branch then we probably don't need separate commands for Parcel, we would probably just use dev and build right?

Looks good! One question... The PR is asking to be merged into master, but do we plan to incrementally add Parcel to Brisk or should we have a long running branch where we do our Parcel work and merge that into master once it's all done? If we do have a long running branch then we probably don't need separate commands for Parcel, we would probably just use dev and build right?

Yes, I think you are right..we will be having the long running parcel-brisk branch for integration and then merge to master once all done. PR was raised for review of my changes in the new branch

Yes, I think you are right..we will be having the long running parcel-brisk branch for integration and then merge to master once all done. PR was raised for review of my changes in the new branch

If we're going to have a longer lived branch (e.g. parcel), this could be branched from parcel and PRs could be targeted against parcel as well. That would allow for review without landing these changes in master.


DOC: signal: minor clarification to docstring of TransferFunction.

In response to a question from @matthew-brett on gh-5418.

LGTM.


Introduce technology diagram

It is useful to filter a system according to a particular discipline so that certain teams can review all the modules together, even if they are divided across different logical boundaries.
For example, electronics engineers will be interested in all electronic blocks in order to consider deployment to different PCBs. All electronic element should be rendered even if some are associated within one logical block (e.g. amplification) vs another (e.g. connectivity)

It is unclear how much resolution is desired. Is this just a context diagram filtered based on a tag?
Or could it be performing a search of the model tree, returning the first child that is tagged with the technology? That sounds good. Not sure about the relationships...

The technology view should probably place all the primary elements within a technology psudo-element. This obviously separates these elements of interest from those that are included simply because they exist.
This psudo-element probably ruins the whole assumption that every view is really just a model, because now a new unexpected element is introduced. However we might get away with it if the NewTechnologyView function does some sort of insertion of a new element. Sounds messy 😨


Also support CrunchyData postgres-operator

Describe the solution you'd like
Since I already use the CrunchyData postgres-operator to support postgres deployments in other workloads, I would like to use it to support my harbor postgres instance as well.

@ron1
Now, calling the PostgreSQL operator to create psql instance for Harbor using has become a framework. It's easy to support another kind once the CRD is upgraded later.
The simple work is just providing a new handler that implements the Apply() function.
@ron1  Do you have any interest to do such contributions?


ORDER BY break in UNIQUE queries

https://github.com/codewithkyle/jsql/blob/2aed441abf9e4b9718d020b6cbd5d36c0f0c11be/src/jsql.worker.ts#L679

Current workaround is to perform the query without ORDER BY then .sort() the response yourself.


Support for monitoring

Hey, great job on this library!
Any idea on when support for monitoring will be available?
I'd love to switch to this library instead of react-native-beacons-android. But monitoring beacons is kinda key for my use-case

Never mind. There seems to be a bug with Android 7. The beacons become undetected for a few-seconds, then coming back and then getting undetected again. Can someone else confirm that this issue is related to Android 7. Monitoring seems to be working fine on Android 6

Thanks @felixaa
I tested it with a Nexus 5X and Android 7 a few days ago and it worked for me. Beacon signals always jump around a bit (You surely know that). Stuff we experimented with is https://github.com/juanderful11/kalmanjs or to accumulate signals in a certain time range etc.
Concerning monitoring: When creating the module, I tested monitoring and had trouble getting it working with a native Android implementation, so I did not include it in the module. I hope I'll soon find time to update the SDK as outlined in another issue with which monitoring might work then. That being sad, pull requests are always welcome.

Monitoring now included in version 1.0.0.


[stable/mongodb-replicaset] Openssl: unable to write 'random state'

Is this a request for help?: No

Bug Report
Version of Helm and Kubernetes:
Kubernetes: 1.12.5-gke.10
Helm

server: v2.13.0
client:  v.2.13.1

Which chart:
stable/mongodb-replicaset
What happened:
When creating the client certificate for the replica set member Openssl throws: unable to write 'random state'
What you expected to happen:
Expected the cert to be created w/o issue
How to reproduce it:
replicas: 1
image:
  tag: 3.6
init:
  resources: {}
  timeout: 30

auth:
  enabled: true
  key: "MySuperSecretKeyFile"
  adminUser: username
  adminPassword: password

tls:
  # Enable or disable MongoDB TLS support
  enabled: true
  # Please generate your own TLS CA by generating it via:
  # $ openssl genrsa -out ca.key 2048
  # $ openssl req -x509 -new -nodes -key ca.key -days 10000 -out ca.crt -subj "/CN=mydomain.com"
  # After that you can base64 encode it and paste it here:
  # $ cat ca.key | base64 -w0
  cacert: `Genertate and add your own from above`
  cakey: `Genertate and add your own from above`

configmap: #Doesn't matter b/c it never gets this far
  storage:
    dbPath: /data/db
  net:
    port: 27017
    ssl:
      mode: requireSSL
      CAFile: /data/configdb/tls.crt
      PEMKeyFile: /work-dir/mongo.pem
      # Set to false to require mutual TLS encryption
      allowConnectionsWithoutCertificates: false
  replication:
    replSetName: rs0
  security:
    authorization: enabled
    # # Uncomment to enable mutual TLS encryption
    #clusterAuthMode: x509
    keyFile: /keydir/key.txt

Anything else we need to know:
I solved this issue by setting the RANDFILE environment variable in the 'on-start.sh' script when using ssl like below.
cat >openssl.cnf <<EOL                  ### Line 123 -> on-start.sh
[req]
req_extensions = v3_req
distinguished_name = req_distinguished_name
[req_distinguished_name]
[ v3_req ]
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
subjectAltName = @alt_names
[alt_names]
DNS.1 = $(echo -n "$my_hostname" | sed s/-[0-9]*$//)
DNS.2 = $my_hostname
DNS.3 = $service_name
DNS.4 = localhost
DNS.5 = <IP_ADDRESS>
EOL
    export RANDFILE=/work-dir/.rnd

    # Generate the certs
    openssl genrsa -out mongo.key 2048
    openssl req -new -key mongo.key -out mongo.csr -subj "/OU=MongoDB/CN=$my_hostname" -config openssl.cnf
    openssl x509 -req -in mongo.csr \
        -CA "$ca_crt" -CAkey "$ca_key" -CAcreateserial \
        -out mongo.crt -days 3650 -extensions v3_req -extfile openssl.cnf

    rm mongo.csr
    cat mongo.crt mongo.key > $pem
    rm mongo.key mongo.crt
fi

same error, still present, fixed here but never answered or merged
https://github.com/helm/charts/pull/16655


codebert-base.jackson-databind.mid-2930.idx-41854.1.buggy

Formatting bindItem(..)

Closing due to conclifts. Sorry if we accepted some PR before yours.


[Android] Add typing callback

This adds the missing typing callback for having typing notifications in the Android app.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8e127b3) 87.39% compared to head (240f5ed) 89.39%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #900      +/-   ##
============================================
+ Coverage     87.39%   89.39%   +2.00%
============================================
  Files           166       86      -80
  Lines         18987    15324    -3663
  Branches       1049        0    -1049
============================================
- Hits          16593    13699    -2894
+ Misses         2093     1625     -468
+ Partials        301        0     -301

Flag
Coverage Δ

uitests
?

uitests-android
?

uitests-ios
?

unittests
89.39% <ø> (+3.97%)
:arrow_up:

unittests-android
?

unittests-ios
?

unittests-rust
89.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Generate client certificate with proper extended usage info

Should resolve #2447

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

jenkins: test this please

I am not quite happy with the call like shared.FindOrGenCert(certf, keyf, true) - it doesn't explain what's going on. In Python I would do it like shared.FindOrGenCert(certf, keyf, client=True), but go doesn't seem to support default params.


tools: prevent use of 'throw new'

Description: throw new should be avoided, as the type being thrown is a pointer to the exception and not the exception itself. This can mess with catch statements. See https://stackoverflow.com/a/10964457 for more info.
Risk Level: low
Testing: added
Docs Changes: n/a
Release Notes: n/a
Signed-off-by: Derek Argueta<EMAIL_ADDRESS>

misc-throw-by-value-catch-by-reference actually looks like it should do the job
https://github.com/llvm/llvm-project/blob/master/clang-tools-extra/clang-tidy/misc/ThrowByValueCatchByReferenceCheck.cpp#L86
Should I remove the check_format.py change or leave a TODO?

I would probably just remove the format check and add it when you fix clang-tidy, but up to you.

@mattklein123 SGTM, removed format check


Some operations fail after multiple EXPIREs

SET foo1 bar
SET foo2 bar
EXPIRE foo1 0
EXPIRE foo2 0
DBSIZE

fails with "null". Some other commands like KEYS * also fail

nevermind


New nvim disable/enable approach

Maybe you can think about this realization?
https://github.com/neovim/neovim/issues/14825#issuecomment-1196644699
https://github.com/neovim/neovim/pull/15134/files#diff-2c5241b87ba4cc10dd6d1822a2cfa718b1ea523bb9781da4f92585aff7f6b01fR1299

Sorry for the very late reply. While I continue to use this plugin I don't need to change it unless it breaks.  enable/disable only work on the current buffer. The approach I've taken for Neovim 0.7+ is to use config since it works across buffers (which is how this plugin works for 0.5 -> 0.6.1). This seems to work just fine. As long as this plugin works I don't see much need to change it. It does precisely what it was meant to do. I'll continue to fix bugs as they are reported, but I don't see a need to change how it works, for now.


[ClangImporter] Adjust for LLVM changes

https://github.com/llvm/llvm-project/commit/9721fbf85b83 refactors the
enum; adjust Swift accordingly.

CC @plotfi @epilk

Wonder if master-next is in any kind of state to support this
@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - b59ffe0edf8c89892faed8ce728b37b8a433f628

Build failed
Swift Test OS X Platform
Git Sha - b59ffe0edf8c89892faed8ce728b37b8a433f628

sigh
⛵


[BUG] Beta 1 BC issues

Describe the bug
Issues identified on a clean install to TBC

Some missing Textures still in BC And Classic

Still cant save macro in beta4


fix(app): getPatientUrl when patient num over 100

Fixes

Fixes #28 by @elsiehoffet-94

did you test locally ?

yep


Disable SSL Verification based on ENV

@tareksamni This disables SSL Verification for all Checks and that's not the 'nice-to-have' from the Feature request.

It would be nice to have a checkbox that disables certificate verification per endpoint. (#28)

You are right. will open another one once It's ready


This control scheme is not the same as the Reverb G2 (also WMR).

[Enter feedback here]

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

ID: f2095ad7-420a-8852-5f36-0c4fa60150d7
Version Independent ID: a73a63b2-1276-b9b2-a459-c1c86b3ccc97
Content: Windows Mixed Reality controls - AltspaceVR
Content Source: altspace-vr/getting-started/wmr-controls.md
Product: mixed-reality
GitHub Login: @vryunji
Microsoft Alias: v-hferrone

This should now be fixed.


vm-import: fix diskoffering checks for root disk

Description
Use disk offering linked with the service offering while checking for root disk during import
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@shwstppr , this is needed because of the de-coupling of service offering and disk offerings?
can you add soem test spec?
code lgtm

@shwstppr , this is needed because of the de-coupling of service offering and disk offerings? can you add soem test spec? code lgtm

@DaanHoogland yes, it could be decoupling or maybe this has been ignored since the addition of VM import.
I've not tested this yet. Will add more details soon

@shwstppr is this still relevant/needed?

@shwstppr is this still relevant/needed?


Support for bicepparam files

bicepparam files are now the preffered over json parameter files for bicep deployments.
Docs
Can support for this file type be added to tree-sitter?

Resolved using the autocmd here:
https://github.com/neovim/nvim-lspconfig/issues/2745#issuecomment-1676506505

Just saw this, this should be PRed to vim and then backported to neovim

Thanks for the pointer. PR has been opened:
https://github.com/vim/vim/pull/12784


New MorphoSourceImport Module

This is still showing some trailing white space, but in the HiResScreenCapture file, which is not part o this commit. @smrolfe @oothomas can you work together?


[REF] cfdilib: Compatibiity with all lxml versions

Based on base_ubl module used in Germany localization
Fix https://github.com/Vauxoo/cfdilib/issues/43

@nhomar
I found a way most compatible with other lxml version to validate the schema
Could you review it?