text:
An execption during lock renew

We are reading messages from a Service Bus topic with a variant of the
following code block:
client = SubscriptionClient.from_connection_string(
    connection_string, subscription, loop=loop)
receiver = client.get_receiver()
batch = receiver.fetch_next(max_batch_size=1, timeout=30)
...

but during message renew done in an async loop with
message.renew_lock we are getting the following exception:
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/azure/servicebus/aio/async_base_handler.py", line 90, in _mgmt_request_response
    callback=callback)
  File "/usr/lib/python3.6/site-packages/uamqp/async_ops/client_async.py", line 333, in mgmt_request_async
    **kwargs))
  File "/usr/lib/python3.6/site-packages/uamqp/async_ops/session_async.py", line 114, in mgmt_request_async
    return parse_response(status, response, description)
  File "/usr/lib/python3.6/site-packages/azure/servicebus/common/mgmt_handlers.py", line 28, in lock_renew_op
    status_code, description, message.get_data()))
azure.servicebus.common.errors.ServiceBusError: Management request returned status code: 500. Description: b'Unsupported type 0x40 for array. TrackingId:de1b2df6-7cf4-4c7b-a741-ff6d9e310f71_G24, SystemTracker:NoSystemTracker, Timestamp:2019-09-18T11:41:00', Data: None

@Indy2222 thanks for letting us know, we will take a look at it

I had the same error:
`Failed to complete mgmt operation.
Status code: 500
Message: b'Unsupported type 0x40 for array. TrackingId:7bdddf69-a511-4246-8413-4094e9994a0c_G25, SystemTracker:NoSystemTracker, Timestamp:2019-09-18T16:12:44'
2019-09-18 16:12:44,138 MainThread   captura  ERROR: Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/azure/servicebus/base_handler.py", line 91, in _mgmt_request_response
callback=callback)
File "/usr/local/lib64/python3.6/site-packages/uamqp/client.py", line 328, in mgmt_request
**kwargs)
File "/usr/local/lib64/python3.6/site-packages/uamqp/session.py", line 126, in mgmt_request
return parse_response(status, response, description)
File "/usr/local/lib/python3.6/site-packages/azure/servicebus/common/mgmt_handlers.py", line 28, in lock_renew_op
status_code, description, message.get_data()))
azure.servicebus.common.errors.ServiceBusError: Management request returned status code: 500. Description: b'Unsupported type 0x40 for array. TrackingId:7bdddf69-a511-4246-8413-4094e9994a0c_G25, SystemTracker:NoSystemTracker, Timestamp:2019-09-18T16:12:44', Data: None
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/primarecaptura/primare_orchestrator/tools/captura_roudtrip/captura-roundtrip.py", line 212, in main
primareMessage.startManaging()
File "/home/primarecaptura/primare_orchestrator/tools/captura_roudtrip/primare_message.py", line 101, in startManaging
self.renewLock()
File "/home/primarecaptura/primare_orchestrator/tools/captura_roudtrip/primare_message.py", line 106, in renewLock
self.queueManager.renewLockMessage(message=self.message)
File "/home/primarecaptura/primare_orchestrator/azure_queue_manager.py", line 246, in renewLockMessage
message.renew_lock()
File "/usr/local/lib/python3.6/site-packages/azure/servicebus/common/message.py", line 303, in renew_lock
expiry = self._receiver._renew_locks(self.lock_token)  # pylint: disable=protected-access
File "/usr/local/lib/python3.6/site-packages/azure/servicebus/receive_handler.py", line 141, in _renew_locks
mgmt_handlers.lock_renew_op)
File "/usr/local/lib/python3.6/site-packages/azure/servicebus/base_handler.py", line 93, in _mgmt_request_response
raise ServiceBusError("Management request failed: {}".format(exp), exp)
azure.servicebus.common.errors.ServiceBusError: Management request failed: Management request returned status code: 500. Description: b'Unsupported type 0x40 for array. TrackingId:7bdddf69-a511-4246-8413-4094e9994a0c_G25, SystemTracker:NoSystemTracker, Timestamp:2019-09-18T16:12:44', Data: None`

this is almost new... the same code worked correctly yesterday. No idea is something changed server side

Hi @nemakam - can you confirm whether any service updates/changes have been rolled out recently?

In my case the parameter arrived here:
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/servicebus/azure-servicebus/azure/servicebus/receive_handler.py#L138
are, in order:
b'com.microsoft:renew-lock'
b'entity-mgmt'
{b'lock-tokens': [None]}       <<<<--- is it this the problem. would [ ] or none (json encoding) ?
5000

Thanks @luipir  - yeah it looks like an empty array is being sent (0x40 indicates a NULL value).
If we work back up the strack trace you posted above (thank you!) we can see that the messages lock_token attribute appears to be empty...
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/servicebus/azure-servicebus/azure/servicebus/common/message.py#L237
This would indicate that it's not being returned in the annotation.
My understanding is that there's more than one way to collect a lock token for a message - so maybe we need to investigate the alternative if the delivery annotations are unreliable.
Thoughts @nemakam ?

setting None as token instead of [None] override the Array error, but obviously can't lock the token returning:
Message: b'The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 Reference:***********, TrackingId:****************, SystemTracker:primare-desa-service-bus:Topic:primare_desa_topic_initplanification|proyestegal_initplanification_suscriber, Timestamp:2019-09-19T14:06:29'

My understanding is that there's more than one way to collect a lock token for a message - so maybe we need to investigate the alternative if the delivery annotations are unreliable.

how to set the lock token of the message again? I'll check if it's empty before to call renew_lock!

BTW is token is None, the raised error is not a correct message to understand it. Should be managed

I think that this ticket is related to https://github.com/Azure/azure-sdk-for-python/issues/4598
Note that the docs say:

Lock tokens are the DeliveryTag property on received messages. See the following example in the .NET SDK which retrieves these. The token may also appear in the 'DeliveryAnnotations' as 'x-opt-lock-token' however, this is not guaranteed and the DeliveryTag should be preferred.

in my case None of token property return None only in these case:
@property
def lock_token(self):
    if self.settled:
        return None
    delivery_annotations = self.message.delivery_annotations
    if delivery_annotations:
        return delivery_annotations.get(self._x_OPT_LOCK_TOKEN)
    return None

sorry my mistake, It's not a DeferredMessage but a base class Message => lock_token property is:
@property
def lock_token(self):
if hasattr(self._receiver, 'locked_until') or self.settled:
return None
delivery_annotations = self.message.delivery_annotations
if delivery_annotations:
return delivery_annotations.get(self._x_OPT_LOCK_TOKEN)
return None

In this:
if hasattr(self._receiver, 'locked_until') or self.settled:
I can understand self.settled for a message in sending stat (for my undestand of communication) but I can't figure out the reason of hasattr(self._receiver, 'locked_until') check

Absolutely it should be a reasonable error - however the Service has never sent us empty values before - so we didn't know this was something that needed an appropriate error message ;)
Unfortunately the alternative means of getting a lock token is not yet exposed in the underlying library. I have opened a PR for that here - so hopefully we can get the update out pretty quick:
https://github.com/Azure/azure-uamqp-python/pull/94
The reason for the receiver.locked_until check is for Session-ful messages. In this scenario (i.e. when you receive from a Session), an individual message does not have a lock - rather the entire link has the lock and therefore the link lock must be renewed in order to keep the messages active.

The reason for the receiver.locked_until check is for Session-ful messages. In this scenario (i.e. when you receive from a Session), an individual message does not have a lock - rather the entire link has the lock and therefore the link lock must be renewed in order to keep the messages active.

clear, tnx
BTW I can confirm that bypassing "if hasattr(self._receiver, 'locked_until') or self.settled:" still retunr None

and delivery_annotations is None!

@Indy2222

I think that the bug is related to #4598.

I do not think so, because delivery_annotations are empty in my message (or I didn't well understand you suggestion)

Actually that is correct - or it lease, partially correct.
On the one hand it's strange that deliver_annotations is None - this implies that something has changed in the service. However it would be less of an issue if #4598 was supported.

On the one hand it's strange that deliver_annotations is None - this implies that something has changed in the service.

Note that we are using Service Bus topics extensively and we experience this issue only on one topic but not the others. However, it seems that the lock token is not present on any message on the affected topic.

However it would be less of an issue if #4598 was supported.

Yes. IMHO it is dangerous to depend on a header which is explicitly documented as not being guaranteed. But I don't see under the hood, i.e. how you coordinate between the server side and client side development.

Note that we are using Service Bus topics extensively and we experience this issue only on one topic but not the others. However, it seems that the lock token is not present on any message on the affected topic.

I did tests on different queue on a different computer (not the same point release version of Azure sdk)  and worked fine. I'll check on the same message.
BTW with ServiceBusExplorer I can see a lock token in the metadata of the message where metadata are not transmitted.

confirmed, it happens only on a specific queue (from a testing code that workd on a different queue)
this is the uamqp debug log:
https://gist.github.com/luipir/01775bef48732af9b2a6e1e7a71645ce

I checked queue parameters with a working queue and there is no difference. I test also creating a new subscriber in the broken queue, and the error is still present.

Hi,
got the same error running a small piece of code:
from azure.servicebus import AutoLockRenew, ServiceBusClient, Message
import os
from time import sleep, time
import logging
import datetime

logging.basicConfig(level=logging.DEBUG)

sbs = ServiceBusClient(os.environ['AZURE_BUS_NAMESPACE'],
                        shared_access_key_name=os.environ['AZURE_BUS_KEY_NAME'],
                        shared_access_key_value=os.environ['AZURE_BUS_KEY_VALUE'])
queue = sbs.get_queue(os.environ['AZURE_BUS_QUEUE'])

lock_time = 60
lock_renewal = AutoLockRenew(max_workers=4)
while True:
    with queue.get_receiver(idle_timeout=3) as queue_receiver:
        for message in queue_receiver:
            print(f'Got message: {message}')
            lock_renewal.register(message, timeout=lock_time)
            print(f'Sleeping {lock_time * 0.9} seconds...')
            sleep(lock_time * 0.9)
            print(f'Wake up!')
            message.complete()

Posting a message to a queue, I got the following:
Got message: 5d86a0a5ff09a39ab244655e
DEBUG:azure.servicebus.common.utils:Running lock auto-renew thread for 60 seconds
Sleeping 54.0 seconds...
DEBUG:azure.servicebus.common.utils:10 seconds or less until lock expires - auto renewing.
DEBUG:uamqp.c_uamqp:Deallocating 'AMQPValue'
DEBUG:uamqp.c_uamqp:Destroying 'AMQPValue'
DEBUG:uamqp.c_uamqp:Deallocating 'StringValue'
DEBUG:uamqp.c_uamqp:Destroying 'StringValue'
DEBUG:uamqp.c_uamqp:Deallocating 'DictValue'
DEBUG:uamqp.c_uamqp:Destroying 'DictValue'
DEBUG:uamqp.message:Parsing received message 2.
DEBUG:uamqp.c_uamqp:Destroying cProperties
DEBUG:uamqp.message:Parsing received message properties 2.
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.StringValue: 16>
DEBUG:uamqp.c_uamqp:Destroying cHeader
DEBUG:uamqp.message:Parsing received message header 2.
DEBUG:uamqp.message:Parsing received message application properties 2.
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.DictValue: 19>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.StringValue: 16>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.StringValue: 16>
DEBUG:uamqp.c_uamqp:Deallocating 'StringValue'
DEBUG:uamqp.c_uamqp:Destroying 'StringValue'
DEBUG:uamqp.c_uamqp:Deallocating 'StringValue'
DEBUG:uamqp.c_uamqp:Destroying 'StringValue'
DEBUG:uamqp.c_uamqp:Deallocating 'DictValue'
DEBUG:uamqp.c_uamqp:Destroying 'DictValue'
DEBUG:uamqp.message:Parsing received message annotations 2.
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.DictValue: 19>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.TimestampValue: 13>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.LongValue: 9>
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'TimestampValue'
DEBUG:uamqp.c_uamqp:Destroying 'TimestampValue'
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.LongValue: 9>
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'LongValue'
DEBUG:uamqp.c_uamqp:Destroying 'LongValue'
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.TimestampValue: 13>
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'LongValue'
DEBUG:uamqp.c_uamqp:Destroying 'LongValue'
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'TimestampValue'
DEBUG:uamqp.c_uamqp:Destroying 'TimestampValue'
DEBUG:uamqp.c_uamqp:Deallocating 'DictValue'
DEBUG:uamqp.c_uamqp:Destroying 'DictValue'
DEBUG:uamqp.c_uamqp:Deallocating cProperties
DEBUG:uamqp.c_uamqp:Destroying cProperties
DEBUG:uamqp.c_uamqp:Deallocating cHeader
DEBUG:uamqp.c_uamqp:Destroying cHeader
DEBUG:uamqp.c_uamqp:Deallocating 'cApplicationProperties'
DEBUG:uamqp.c_uamqp:Destroying 'cApplicationProperties'
DEBUG:uamqp.c_uamqp:Deallocating 'cMessageAnnotations'
DEBUG:uamqp.c_uamqp:Destroying 'cMessageAnnotations'
DEBUG:uamqp.c_uamqp:Destroying cSource
DEBUG:uamqp.c_uamqp:Destroying cTarget
DEBUG:uamqp.c_uamqp:Deallocating cSource
DEBUG:uamqp.c_uamqp:Destroying cSource
DEBUG:uamqp.c_uamqp:Deallocating cTarget
DEBUG:uamqp.c_uamqp:Destroying cTarget
DEBUG:uamqp.c_uamqp:Destroying cSource
DEBUG:uamqp.c_uamqp:Destroying cTarget
DEBUG:uamqp.c_uamqp:Deallocating cSource
DEBUG:uamqp.c_uamqp:Destroying cSource
DEBUG:uamqp.c_uamqp:Deallocating cTarget
DEBUG:uamqp.c_uamqp:Destroying cTarget
DEBUG:uamqp.c_uamqp:Management link open: 0
DEBUG:uamqp.message:Parsing received message 3.
DEBUG:uamqp.c_uamqp:Destroying cProperties
DEBUG:uamqp.message:Parsing received message properties 3.
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.StringValue: 16>
DEBUG:uamqp.c_uamqp:Destroying cHeader
DEBUG:uamqp.message:Parsing received message header 3.
DEBUG:uamqp.message:Parsing received message application properties 3.
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.DictValue: 19>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.StringValue: 16>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.StringValue: 16>
DEBUG:uamqp.c_uamqp:Deallocating 'StringValue'
DEBUG:uamqp.c_uamqp:Destroying 'StringValue'
DEBUG:uamqp.c_uamqp:Deallocating 'StringValue'
DEBUG:uamqp.c_uamqp:Destroying 'StringValue'
DEBUG:uamqp.c_uamqp:Deallocating 'DictValue'
DEBUG:uamqp.c_uamqp:Destroying 'DictValue'
DEBUG:uamqp.message:Parsing received message annotations 3.
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.DictValue: 19>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.TimestampValue: 13>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.LongValue: 9>
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'TimestampValue'
DEBUG:uamqp.c_uamqp:Destroying 'TimestampValue'
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.LongValue: 9>
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'LongValue'
DEBUG:uamqp.c_uamqp:Destroying 'LongValue'
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.SymbolValue: 17>
DEBUG:uamqp.c_uamqp:Wrapping value type: <AMQPType.TimestampValue: 13>
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'LongValue'
DEBUG:uamqp.c_uamqp:Destroying 'LongValue'
DEBUG:uamqp.c_uamqp:Deallocating 'SymbolValue'
DEBUG:uamqp.c_uamqp:Destroying 'SymbolValue'
DEBUG:uamqp.c_uamqp:Deallocating 'TimestampValue'
DEBUG:uamqp.c_uamqp:Destroying 'TimestampValue'
DEBUG:uamqp.c_uamqp:Deallocating 'DictValue'
DEBUG:uamqp.c_uamqp:Destroying 'DictValue'
DEBUG:uamqp.c_uamqp:Deallocating cProperties
DEBUG:uamqp.c_uamqp:Destroying cProperties
DEBUG:uamqp.c_uamqp:Deallocating cHeader
DEBUG:uamqp.c_uamqp:Destroying cHeader
DEBUG:uamqp.c_uamqp:Deallocating 'cApplicationProperties'
DEBUG:uamqp.c_uamqp:Destroying 'cApplicationProperties'
DEBUG:uamqp.c_uamqp:Deallocating 'cMessageAnnotations'
DEBUG:uamqp.c_uamqp:Destroying 'cMessageAnnotations'
DEBUG:uamqp.c_uamqp:Deallocating cProperties
DEBUG:uamqp.c_uamqp:Destroying cProperties
DEBUG:uamqp.c_uamqp:Management op complete: 2, status code: 500, description: b'Unsupported type 0x40 for array. TrackingId:0c3a2fd3-d846-4de7-aecc-29cf420726dd_G21, SystemTracker:NoSystemTracker, Timestamp:2019-09-21T22:26:12'
ERROR:uamqp.mgmt_operation:Failed to complete mgmt operation.
Status code: 500
Message: b'Unsupported type 0x40 for array. TrackingId:0c3a2fd3-d846-4de7-aecc-29cf420726dd_G21, SystemTracker:NoSystemTracker, Timestamp:2019-09-21T22:26:12'
DEBUG:uamqp.message:Parsing received message None.

@andreacassioli  @Indy2222  @annatisch I've discovered the origin of the problem... it is how ServiceBusExplorer send messages to the queue! at least in my case!
If a message is sent via ServiceBusexplorer => no lock_token info and/or some mentadata are missing.
If I send the same message to the same queue via a normal client this error is not present.
BTW the issue still remain for at least two aspects:

the error message is totally unuseful to understand the origin of the problem
there is no recovery action. e.g. setup a lock token if not available for a specific session or user.

I'll notify this effect to ServiceBusExplorer tracker

Thanks @luipir - that's a very interesting observation!
I'm still hoping this can be resolved through supporting of the delivery tag - however if we can also get a temporary fix in place in SBExplorer that would be great :)

Edit: I guess you discovered that this wasn't the case and closed the issue?

no, they closed the issue assuming it's not "their" responsability... I't not my way to manage a OS project, but I assume the decision especially because none of the other in this thread have mentioned if they have serviceBusExplorer involved in the message generation.
Their assumption is that ServiceBusExplorer is creating the message correctly and the python SDK is missing reading some metadata (in my case no metadata at all, not only lock).

Ug... okay - well I'll try to get the other patch through as quick as I can.
If I were to get a test build of an updated uAMQP release - would you be open to testing it out?

If I were to get a test build of an updated uAMQP release - would you be open to testing it out?

@annatisch  for a OS project I'm always open to contribute :) do you need a specific platform or a linux is enough? I do not know uAMQP and project details but would make sense to have a unit test about this fix? eg here https://github.com/Azure/azure-uamqp-python/tree/master/tests

Update - the changes are now ready for testing:
The uAMQP wheels with the changes can be download here:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=118233
The updates to the service bus SDK are in PR here:
https://github.com/Azure/azure-sdk-for-python/pull/7453
The PR also includes a better error message for the case where no lock token is present.

@luipir

I've discovered the origin of the problem... it is how ServiceBusExplorer send messages to the queue! at least in my case!
If a message is sent via ServiceBusexplorer => no lock_token info and/or some mentadata are missing.
If I send the same message to the same queue via a normal client this error is not present.

Could you check if ServiceBusExplorer is connecting using NetMessaging transport or Amqp? Could you try with the other protocol and see if you observe anything differently?
FYI: The default for SBExplorer is NetMessaging and the python and .net OS clients are written using AMQP protocol. Other than the protocol differences, I do not generally expect any special handling done by SBExplorer.

i'm late testing because I've to fix other stuff in OpenSFM, sorry... any suggestion to know how SBExplorer is using .net or AMPQ? SBExplorer guys seem sure they use .net.

@luipir, my bad. I meant, when you use SBExplorer, what settings do you use? On the screen when you provide your connection details in the tool, there is an option to choose your transport type. The default value there is NetMessaging.
The .net SDK that SBExplorer uses supports both the transport types, whereas the python library supports only one transport type, i.e., AMQP,
So what I am intrigued with is whether the problem lies in cross-protocol support. i.e, sending messages using NetMessaging protocol and receiving with AMQP protocol, wherein the service is responsible for converting the message format from one protocol to another.

When can we expect the fix to be released in a new version?

https://github.com/Azure/azure-sdk-for-python/pull/7453 seems already merged in track2 branch.. no idea what is the release roadmap of the package. You were able to test the wheels as suggested by https://github.com/Azure/azure-sdk-for-python/issues/7336#issuecomment-535618145 ? I hadn't time (mainly because I found the workaround so I do not have it as an emergency and I'm focused on complementary deadlines)

Hey folks,
Resurrecting this discussion as it seems to be the root for #9010 and #8707 as well, to throw a wider net echoing if individuals are still seeing issues in this path. (Given UAMQP 1.2.6 / SB 0.50.2 releases made in December)
Don't hesitate to shout if there's another repro, in testing the code from AndreaCassioli I was not able to reproduce the failure with latest versions, so "cautiously optimistic."

authors: Indy2222 KieranBrantnerMagee andreacassioli annatisch kaerm luipir nemakam


text:
DefaultAzureCredential error message is displayed twice

Remove all credential related env vars, not managed identity, and not signed into VS 2019.
With this code:
from azure.identity import DefaultAzureCredential
credential = DefaultAzureCredential()
credential.get_token()

The following is outputted:
Traceback (most recent call last):
  File "c:\users\jong\onedrive - microsoft\code\azure-sdk-for-python\sdk\identity\azure-identity\azure\identity\_credentials\default.py", line 50, in get_token
    return super(DefaultAzureCredential, self).get_token(*scopes, **kwargs)
  File "c:\users\jong\onedrive - microsoft\code\azure-sdk-for-python\sdk\identity\azure-identity\azure\identity\_credentials\chained.py", line 52, in get_token
    raise ClientAuthenticationError(message=error_message)
azure.core.exceptions.ClientAuthenticationError: No credential in this chain provided a token.
Attempted credentials:
        EnvironmentCredential: Incomplete environment configuration
        ImdsCredential: IMDS endpoint unavailable
        SharedTokenCacheCredential: No cached token found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "../../../../azure-identity/index2.py", line 4, in <module>
    credential.get_token()
  File "c:\users\jong\onedrive - microsoft\code\azure-sdk-for-python\sdk\identity\azure-identity\azure\identity\_credentials\default.py", line 56, in get_token
    .format(e.message))
azure.core.exceptions.ClientAuthenticationError:
No credential in this chain provided a token.
Attempted credentials:
        EnvironmentCredential: Incomplete environment configuration
        ImdsCredential: IMDS endpoint unavailable
        SharedTokenCacheCredential: No cached token found

Please visit the Azure identity Python SDK docs at
https://aka.ms/python-sdk-identity#defaultazurecredential
to learn what options DefaultAzureCredential supports

We should only be rendering the same error message once per get_token call.

thanks @jongio // cc: @chlowell

source: gharchive/issue

authors: jongio kaerm

repo: Azure/azure-sdk-for-python

license: MIT

license_type: permissive

license_source: github-api


text:
azure-appconfiguration wheel should contain only the "azure" folder

As of today, contains "tests" too. There is several ways to fix that, the best approach is too remove any __init__.py at any levels in the "tests" folder.

Fixed in #8663


text:
[Event Hubs] Add comment to checkpointstore sample that uses old version of storage

Add "Azure Stack" in the sample comment

Can one of the admins verify this patch?

Thanks @YijunXieMS
Looks good to me!

source: gharchive/pull-request

authors: YijunXieMS adxsdk6 spelluru


text:
[KV-keys]Name change in SKR

Literally updated names as specified in this issue: https://github.com/Azure/azure-sdk-for-python/issues/21380

API changes have been detected in azure-keyvault-keys. You can review API changes here
API changes
-             target: str,
+             target_attestation_token: str,
-             target: str,
+             target_attestation_token: str,

API changes have been detected in azure-keyvault-keys. You can review API changes here
API changes
-             target: str,
+             target_attestation_token: str,
-             target: str,
+             target_attestation_token: str,


text:
CODEOWNERS: Adding automation section

Adding automation owners

/check-enforcer override


text:
adding delete_vhd option to delete_deployment

See issue #268

Sorry, I haven't gotten this to work. The blob for the .vhd still exists after deleting the deployment.
Here's the test I'm adding for this:
    def test_delete_deployment_with_vhd(self):
        # Arrange
        service_name = self.hosted_service_name
        deployment_name = self.hosted_service_name
        role_name = self.hosted_service_name

        self._create_vm_linux(service_name, deployment_name, role_name)
        self.assertTrue(
            self._blob_exists(self.container_name, role_name + '.vhd'))

        # Act
        result = self.sms.delete_deployment(
            self.hosted_service_name, deployment_name, delete_vhd=True)
        self._wait_for_async(result.request_id)

        # Assert
        self.assertFalse(
            self._blob_exists(self.container_name, role_name + '.vhd'))
        self.assertFalse(
            self._deployment_exists(self.hosted_service_name, deployment_name))

I'm curious if you it's been working for you?

authors: huguesv okaram


text:
[Corehttp] Misc fixes + cleanup

Fixed a parameter mismatch in the connection config
Added the aiohttp fix that was added to azure-core (Ref: https://github.com/Azure/azure-sdk-for-python/pull/32540)
Cleaned up tests a bit to remove constructs that were used for backcompat testing.

/azp run python - core

/check-enforcer override


text:
Azure Monitor OpenTelemetry Distro Release 1.4.2

Description
Distro release with sdk backoff related diagnostics
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

authors: azure-sdk jeremydvoss


text:
[AutoPR network/resource-manager] Update for Get Application Gateway Server Variables APIs

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5113

Codecov Report

Merging #4282 into restapi_auto_network-january-release will decrease coverage by 0.03%.
The diff coverage is 1.42%.

@@                           Coverage Diff                            @@
##           restapi_auto_network-january-release    #4282      +/-   ##
========================================================================
- Coverage                                 54.35%   54.32%   -0.04%
========================================================================
  Files                                      9772     9772
  Lines                                    206380   206520     +140
========================================================================
+ Hits                                     112181   112183       +2
- Misses                                    94199    94337     +138

Impacted Files
Coverage Δ

...rk/azure/mgmt/network/network_management_client.py
25.87% <1.42%> (-2.03%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7f996cb...36d16c6. Read the comment docs.

authors: AutorestCI codecov-io


text:
[AutoPR datafactory/resource-manager] [Data Factory]Add property blockSizeInMB for AzureBlobStorageWriteSettings and AzureBlobFSWriteSettings

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6954

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/6814


text:
[AutoPR recoveryservicesbackup/resource-manager] Azure Backup Version 2019-05-13  addition

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7345

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/7690


text:
support mutliple Scopes in client credential flow

Following both the existing rust DeviceCode model, as well as MSAL for Python and MSAL for Net, allow requesting multiple scopes at once from confidential clients.
Both in documentation and in practice, scopes are space-separated list of permissions.
ref: https://docs.microsoft.com/en-us/dotnet/api/microsoft.identity.client.iconfidentialclientapplication.acquiretokenbyauthorizationcode?view=azure-dotnet#parameters
ref: https://github.com/AzureAD/microsoft-authentication-library-for-python/blob/dev/sample/confidential_client_secret_sample.py#L7
ref: https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent#requesting-individual-user-consent
ref: https://github.com/AzureAD/microsoft-authentication-library-for-python/blob/45499ff5a4ba1afbb71ed95aa5491f924f39dbba/msal/oauth2cli/oauth2.py#L180
ref: https://github.com/AzureAD/microsoft-authentication-library-for-python/blob/45499ff5a4ba1afbb71ed95aa5491f924f39dbba/msal/oauth2cli/oauth2.py#L265-L268

Note, this doesn't fix #61.  The Token Credential stuff still takes a resource.  This is only the client credentials flow.

repo: Azure/azure-sdk-for-rust


text:
Error when get the dates

Hi
I get this error when I navigate through the calendar.

This has been fixed and SDK review meeting shows available dates on scheduler tool now.

repo: Azure/azure-sdk-tools


text:
Update build pipelines to consistently publish test results

Most of the build pipelines are already publishing test results but not all of them are publishing them in a consistent way.
We should be sure to always include a testRunTitle which includes whatever parameters that are changing in the matrix strategy, such as OS and tool versions in the testRunTitle.

[ ] java

Update the maven task and publish the OSName as well as the java version to the Maven task that is running and publishing tests.

[X] js
[ ] net

dotnet task doesn't support a testRunTitle (see https://github.com/Microsoft/azure-pipelines-tasks/issues/9637) so we will have to disable the test result publishing (likely via running a custom task and passing the logger options explicitly), then explicitly call PublishTestResults tasks with the OSName.

[ ] python

Need to produce test results and then call PublishTestResults explicitly and pass OSName and python version.

As part of this work we need to ensure that PublisTestResults task always runs even if the previous test fails otherwise we will not get test results whenever any single test fails. See https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5217&view=logs as an example where a test failed but we didn't get the test results published because the step was skipped.

repo: Azure/azure-sdk


text:
Board Review: Storage Blob Go SDK

Thank you for submitting this review request. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.
Please reference our review process guidelines to understand what is being asked for in the issue template.
To ensure consistency, all Tier-1 languages (C#, TypeScript, Java, Python) will generally be reviewed together.  In expansive libraries, we will pair dynamic languages (Python, TypeScript) together, and strongly typed languages (C#, Java) together in separate meetings.
For Tier-2 languages (C, C++, Go, Android, iOS), the review will be on an as-needed basis.
Before submitting, ensure you adjust the title of the issue appropriately.
Note that the required material must be included before a meeting can be scheduled.
Contacts and Timeline

Responsible service team: Storage
Main contacts: zezha
Expected code complete date: 04/30
Expected release date: 05/14

About the Service

Link to documentation introducing/describing the service: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction
Link to the service REST APIs: https://docs.microsoft.com/en-us/rest/api/storageservices/operations-on-blobs
Link to GitHub issue for previous review sessions, if applicable:

About the client library

Name of the client library: azblob
Languages for this review: Golang

Artifacts required (per language)
Please read through “API Review” section here to understand how these artifacts are generated. It is critical that these artifacts are present and are in the right format. If not, the language architects cannot review them with the SDK Team’s API review tool.
Golang

APIView Link: https://apiview.dev/Assemblies/Review/42d4c83ec51242129d9808b39e99732f
Link to Champion Scenarios/Quickstart samples: https://github.com/Azure/azure-sdk-for-go/blob/track2-storage/sdk/storage/azblob/zt_examples_test.go

For all other languages, send a request to the Architecture Board to discuss the best format on individual basis.
Thank you!

scheduled for 4/7

rescheduled to 4/14

Recording[MS INTERNAL ONLY]

authors: lilyjma zezha-msft


text:
App Service Graceful Shutdown / Migrate Connections help

Framework: .net5.0
Microsoft.Azure.SignalR: v1.8.0
I have an Azure App Service which I am using as the "Hub Server" in "Default Mode" and I deploy to a staging slot on the service to then swap in the new version.
I have found the documentation on Graceful Shutdown and also read the settings documentation around GracefulShutdown.Mode.
My deployment Pipeline deploys the new version to the staging slot then swaps it in to the production.   At this point my clients may be "connected" (proxied through the Azure SignalR service) to the old version in the staging slot.
I've configured, as per the documentation, the Graceful Shutdown to Migrate the connections over:
options.GracefulShutdown.Mode = GracefulShutdownMode.MigrateClients;
options.GracefulShutdown.Timeout = TimeSpan.FromSeconds(90);
options.GracefulShutdown.Add<Hubs.NotificationHub>(c =>
{
    Trace.WriteLine("GRACEFUL SHUTDOWN");
    return c.Clients.All.SendAsync("GracefulShutdown");
});

And after the swap my Pipeline stops the staging slot.
But from what I can see - there is no migration, or even graceful shutdown - the client connections get disconnected immediately and reconnect (sometimes the Disconnect is actually logged after the Reconnect, but this is a side issue).
Is there something I am doing wrong?  Is this the correct approach?
If I don't shut down the staging slot then clients remain connected to the old version in the staging slot and new clients can even connect to it.   In the documentation it talks about "Set the Server Offline" - but it isn't clear about the approach for this.  Should I be adding a sticky slot setting to do this - something like removing the Azure SignalR connection string?  But as I understand on the swap, this would cause a settings change and an application reload therefore terminating the connections anyway?
Could someone give me some guidance on this?  Firstly why I see no appearance of the Graceful Shutdown, and then any advice on the recommended way to do this?

I'll see if it works well, sorry for any inconvenience.

I should have mentioned that I added the checks for the migration feature into the Hub OnConnectedAsync/DisconnectedAsync:
var httpContext = Context.GetHttpContext();
var migration = httpContext.Features.Get<IConnectionMigrationFeature>();
if (migration != null)
       _logger.LogWarning($"OnConnectedAsync: [{migration.MigrateTo}] {Context.ConnectionId} is migrated from {migration.MigrateFrom}.");

But nothing gets logged.

@terencefan Did you validate that this is working.
In the last couple of days I've started to see Connections with the same ConnectionID as previous connections come into the OnConnectedAsync.  These are possibly related to server events, but I can't be sure.  But still, the IConnectionMigrationFeature is returning null so I can't tell whether this is related to migration or not....

Example of same Connection ID being used - see highlighted

I've upgraded to Microsoft.Azure.SignalR: v1.8.2 but still seeing issues:

IConnectionMigrationFeature is always null so never informs me of anything being migrated.
On shutting down my staging environment it now triggers a Disconnect and Connect (not always in that order, mind you) - presumably with the same connection ID by design BUT, the client is then additionally disconnected and has to reconnect (i.e. another Disconnect and Connect presumably caused by the connection still being interrupted between the Server and Azure SignalR?)

Is there any chance of an update on this?
I've had to turn off the Migration stuff because it doesn't seem reliable or to be working correctly.
I'm now fighting with an issue with OnDisconnectAsync not appearing to be called, possibly during a deployment of a new version of my server - which may or may not be due to me shutting down the staging environment?

authors: andrew-tevent terencefan

repo: Azure/azure-signalr


text:
Performance issue when use azcopy sync on huge file count (from 10.5.0)

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
AzCopy 10.5.0
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy sync 'https://ocrdatasetprodwu2.blob.core.windows.net/ocr-dataset/dataset/CDIP-IMAGES/20200611T022412/' 'https://ocrdatasetprod.blob.core.windows.net/ocr-dataset/dataset/CDIP-IMAGES/20200611T022412/' --recursive --delete-destination true
What problem was encountered?
azcopy sync will scan files both in target and source, but it is very slow. In my case, I have 20M files in both source and target. It took 14 hours but still not finish the scanning in target folder. And what's more, the CPU usage always 90+ percent.
I did the same actions with 10.4.3, it only took 2 hours.
How can we reproduce the problem in the simplest way?

Prepare a folder with 20M files in it.
Use azcopy copy to copy them to another container
Use azcopy sync '***' '***' --recursive --delete-destination true  to sync them again
In the third step, expect it can finish the scanning in 2 hours, but in my case it took 14 hours but still not finish scanning target folder.

OR
Ping me on Microsoft Teams, my alias is lchao
Have you found a mitigation/solution?
Roll back to 10.4.3

Hello,
I also have this issue: azcopy sync --recursive --delete-destination true is very slow on file share in my case.
This is the command i used for troubleshooting:
./azcopy_10.13.0 sync "https://<storage_source>.file.core.windows.net/asshared/?se=2021-11-04T17%3A11Z&sp=rl&spr=https&sv=2018-03-28&ss=f&srt=sco&sig=<sig>" "https://<storage_dest>.file.core.windows.net/asshared/?se=2021-11-04T17%3A11Z&sp=rwdl&spr=https&sv=2018-03-28&ss=f&srt=sco&sig=<sig>" --log-level ERROR --recursive=true --delete-destination=true
I made my tests on a Standard_A2m_v2 linux VM (2 vCPUs, 16GB RAM).
The destination storage does not get other traffic than my test.
Here are the number of files scanned at destination in 60s:

azcopy version
Nb files scanned

10.4.3
69185

10.5.0
17964

10.5.1
24966

10.6.0
26160

10.8.0
17365

10.9.0
2710

10.10.0
2265

10.13.0
3462

I made several tests and numbers change a little but stay in the same order of magnitude.
10.5.0 : "Improved scanning performance for most cases by adding support for parallel local and Blob enumeration."
1.9.0 : "Added scanning logs"
We can see a huge drop in scan performance!
I'm available to make more tests.

authors: TiTi mslichao

repo: Azure/azure-storage-azcopy


text:
Azcopy Sync command not detecting changes to existing files within source directory "File Share"

Which version of the AzCopy was used?
10.3.2
Which platform are you using? (ex: Windows, Mac, Linux)
Windows (Within Server 2016 Azure DevOps Self Hosted build agent)
What command did you run?
azcopy.exe sync $source $dest --delete-destination true
What problem was encountered?
Copying from Az Storage Acc "File Share" to Az Storage Acc "File Share", on first sync it will copy the entire directory successfully.
Added dummy text file for 2nd sync to source folder and ran subsequent sync and detected changes and copied file to destination
Made changes to dummy text file and re uploaded to source file share. Performed another sync and job didn't detect this as a change. Both source and destination showed identical file quantities.
Not sure if this is the intended outcome of this command.
How can we reproduce the problem in the simplest way?
As above
Have you found a mitigation/solution?
Revert back to old commands with older azcopy, however over time our source folder will be cleared of files that are no longer required and using standard copy doesn't delete at destination.

Right now, we check against your Last Modified Time registered on objects (to see if the src is more recent) before we schedule the transfer-- Could you confirm that the source LMT is ahead of the destination LMT?

Hi going to close this issue, the source LMT wasn't ahead of the destination LMT.

authors: adreed-msft djradium


text:
Customize pool_maxsize of requests, urllib3 connection pool

This is a similar feature request like https://github.com/boto/botocore/issues/766
This feature would be useful since I am always getting

WARNING:requests.packages.urllib3.connectionpool:Connection pool is full, discarding connection: ****.blob.core.windows.net

Thanks.

Permalink to the request_session parameter in the constructor of any service.

For the new https://github.com/Azure/azure-sdk-for-python/ maybe this helps? https://stackoverflow.com/a/22253656/

authors: MaxTranced carsonip

repo: Azure/azure-storage-python

license: mit

license_source: bigquery


text:
Clarify which Service Account Labels and Annotations are required

Is your feature request related to a problem? Please describe.
Kinda. With the recent v1.0.0 breaking change of making azure.workload.identity/use required in a Pod but optional in a Service Account, the documentation was modified by adding a Required column in some tables, but I think, to make things clear/consistent, that it needs to be added in all the other tables too.
Describe the solution you'd like
All the Service Account Labels and Annotations tables should have a "Required" column to make it clear which labels and annotations are required.
That would make all the tables consistent with each others.
Describe alternatives you've considered
Additional context

Closed with https://github.com/Azure/azure-workload-identity/pull/860

authors: aramase rgl

repo: Azure/azure-workload-identity


text:
Create objects with loop expression

Is your feature request related to a problem? Please describe.
Currently a loop expression returns an array. The idea is to be able to create an object.
Describe the solution you'd like
Proposed example:
var arr = [
  'one'
  'two'
]
var myObj = {for foo in arr: {
  '${foo}': '${foo}-value'
}}

Duplicate #4152

authors: miqm stan-sz

repo: Azure/bicep


text:
There is a problem with the documentation for bicep and using app service and a vnet

Bicep version
run bicep --version via the Bicep CLI, az bicep version via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep
Describe the bug
If you following the sample here:
https://github.com/Azure/bicep/blob/main/docs/examples/101/app-service-regional-vnet-integration/main.bicep
You will see the following:
Warning BCP037: The property "delegations" is not allowed on objects of type "VirtualNetworkPropertiesFormat". Permissible properties include "bgpCommunities", "ddosProtectionPlan", "dhcpOptions", "enableDdosProtection", "enableVmProtection", "ipAllocations", "virtualNetworkPeerings". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
To Reproduce
Steps to reproduce the behavior:
Run the bicep template found at this link:
https://github.com/Azure/bicep/blob/main/docs/examples/101/app-service-regional-vnet-integration/main.bicep
Additional context
Add any other context about the problem here.

What bicep version are you using? Can you confirm that you are running the latest version?

Currently am running Bicep CLI version 0.4.1008 (223b8d227a)

I'm assuming the template works as expected? If so, this is a REST API spec issue.

authors: KevinDMack StefanIvemo alex-frankel


text:
Bicep deploy - remember the defaults for a deployment keyed by the bicep file being deployed

Remember the defaults for a deployment (including param path) based on the .bicep file that is being deployed.
See https://github.com/Azure/bicep/pull/6129#discussion_r827413071 for more details.

My suggestion here would be:

If the user has already gone through the Deploy dialog one time for BicepfileA, then if they were to right click deploy BicepfileA again, all of the recently used defaults will be declared as the first choice (this is the default behavior of VS Code)
If the user has already gone through the Deploy dialog one time for BicepfileB, then we should display all of the recently used defaults of BicepfileA for their FIRST TIME going through the dialog, but afterwards, we should remember the uniquely selected choices of BicepfileB.
If the user THEN right clicks on BicepfileC, we will use the recently used defaults of BicepfileB, and so one. This means that we establish unique defaults for a file once it has been deployed for the first time, but on the very first time through the deploy command for a specific bicep file, we will use the recently used defaults of the previous Bicep file

From an offline discussion, we've walked back a bit of the logic.
We still want to remember the defaults of a Bicep file that has been deployed AT LEAST ONCE, but (unless it is very easy) we do not need to carry those defaults into a Bicep file that is getting deployed for the first time.

Pushing this out, we can discuss it and reprioritized

authors: bhsubra ucheNkadiCode


text:
MAINT: Run tests in parallel to speed up CI by 0.5x

Description
Run tests in parallel to speed up test execution by 50%
Before

After

The below tasks are set for branch protection and should be removed and replaced by the new test jobs prior to merging, @anthony-c-martin & @majastrz please advise:

This is a good speedup!

authors: asilverman majastrz


text:
[autogenerated] update dependencies

Propagating dependency updates

/AzurePipelines run

repo: Azure/c-util


text:
fix mockapi of getting datetime

For fixing below problem:
Currently, the result of get operation on datetime in packages property-optional and property-types varies depending on the sequence of the executing of testcases:

If the put datetime is executed before get datetime, then the result of the get is "2022-08-26T18:38:00.000Z";
If the get datetime invoked ahead of put datetime, then the result of the get is "2022-08-26T18:38:00Z".

Fix
This PR make the result of the get solid to be "2022-08-26T18:38:00.000Z".
Cadl Ranch Contribution Checklist:

[ ] I have written a scenario spec
[ ] I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
[ ] I have written a mock API
[ ] I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

Thanks changlong for the fix we also met the issue.

authors: MaryGao changlong-liu

repo: Azure/cadl-ranch


text:
Surface more chat errors to ErrorBar

What
Show errors in UI when:

Incorrect credentials are used
Incorrect ACS endpoint is provided
Incorrect thread ID is used / user is not in the thread.
Sending message when user is not in a thread.

How Tested
ChatComposite in local storybook
Process & policy checklist

[x] I have updated the project documentation to reflect my changes if necessary.
[x] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[n] This change causes current functionality to break.

Oops. Wrong base.

repo: Azure/communication-ui-library


text:
Check response body for nil before reading it

Thank you for your contribution to Go-AutoRest! We will triage and review it as soon as we can.
As part of submitting, please make sure you can make the following assertions:

[ ] I've tested my changes, adding unit tests if applicable.
[ ] I've added Apache 2.0 Headers to the top of any new source files.
[ ] I'm submitting this PR to the dev branch, except in the case of urgent bug fixes warranting their own release.
[ ] If I'm targeting master, I've updated CHANGELOG.md to address the changes I'm making.

Hmm, I read the docs for resp.Body and it will never be nil so I don't think this is the correct fix.

Related issue: https://github.com/terraform-providers/terraform-provider-azurerm/issues/6773

Fixes https://github.com/Azure/go-autorest/issues/547

authors: ArcturusZhang jhendrixMSFT

repo: Azure/go-autorest


text:
add linux support

Add support for homebrew on linux. This enables users to install kubelogin on linux or WSL instances via brew install Azure/kubelogin/kubelogin. Without this change the installation finishes and the executable could not be executed due to architecture mismatch.

Pinging @weinong.
By the look of it you're the right person to ask for an review.

repo: Azure/homebrew-kubelogin


text:
Update README.md

Corrected spelling and grammar syntax.

The original README was a placeholder. The first draft of the completed README is now pushed. Feel free to contribute to the current version, thanks!

authors: DCMattyG lukemurraynz

repo: Azure/ipam


text:
x-nullable value from $ref schema reference is not propageted

 "/array/complex/itemnull": {
      "get": {
        "operationId": "array_getComplexItemNull",
        "description": "Get array of complex type with null item [{'integer': 1 'string': '2'}, null, {'integer': 5, 'string': '6'}]",
        "tags": [
          "Array Operations"
        ],
        "responses": {
          "200": {
            "description": "Array of complex type with null item [{'integer': 1 'string': '2'}, null, {'integer': 5, 'string': '6'}]",
            "schema": {
              "description": "Array of complex type with null item [{'integer': 1 'string': '2'}, null, {'integer': 5, 'string': '6'}]",
              "type": "array",
              "items":
                {
                  "$ref": "#/definitions/Product",
                  "x-nullable": true
                }
            }
          },
          "default": {
            "description": "Unexpected error",
            "schema": {
              "$ref": "#/definitions/Error"
            }
          }
        }
      }
    },

    - !<!ArraySchema> &ref_109
      type: array
      apiVersions:
        - !<!ApiVersion>
          version: 1.0.0
      elementType: *ref_24
      language: !<!Languages>
        default:
          name: ArrayOfProduct
          description: 'Array of complex type with null item [{''integer'': 1 ''string'': ''2''}, null, {''integer'': 5, ''string'': ''6''}]'

@pakrym as of the following two PRs I believe this issue is fixed:

https://github.com/Azure/perks/pull/115
https://github.com/Azure/autorest.modelerfour/pull/312

Could you try the test build here and let me know if the remaining x-nullable issues are resolved for you?
https://github.com/Azure/autorest.modelerfour/pull/312#issuecomment-654510326

I think it didn't work with array items:
   "/array/complex/itemnull": {
      "get": {
        "operationId": "array_getComplexItemNull",
        "description": "Get array of complex type with null item [{'integer': 1 'string': '2'}, null, {'integer': 5, 'string': '6'}]",
        "tags": [
          "Array Operations"
        ],
        "responses": {
          "200": {
            "description": "Array of complex type with null item [{'integer': 1 'string': '2'}, null, {'integer': 5, 'string': '6'}]",
            "schema": {
              "description": "Array of complex type with null item [{'integer': 1 'string': '2'}, null, {'integer': 5, 'string': '6'}]",
              "type": "array",
              "items":
                {
                  "$ref": "#/definitions/Product",
                  "x-nullable": true
                }
            }
          },
          "default": {
            "description": "Unexpected error",
            "schema": {
              "$ref": "#/definitions/Error"
            }
          }
        }
      }
    },

 - !<!ArraySchema> &ref_109
      type: array
      apiVersions:
        - !<!ApiVersion>
          version: 1.0.0
      elementType: *ref_24
      language: !<!Languages>
        default:
          name: ArrayOfProduct
          description: 'Array of complex type with null item [{''integer'': 1 ''string'': ''2''}, null, {''integer'': 5, ''string'': ''6''}]'
      protocol: !<!Protocols> {}

Seems to work on latest.

authors: daviwil pakrym

repo: Azure/perks


text:
bump k8s version for example since 1.26 has been deprecated

Describe your changes
Issue number
#000
Checklist before requesting a review

[ ] The pr title can be used to describe what this pr did in CHANGELOG.md file
[ ] I have executed pre-commit on my machine
[ ] I have passed pr-check on my machine

Thanks for your cooperation!

I'm merging this pr whilst e2e test failed, it was failed to pass version upgrade test since 1.26 has been deprecated, the latest tag version's example cannot be applied.

repo: Azure/terraform-azurerm-aks


text:
chore: repository governance

Repository governance update
This PR was automatically created by the AVM Team hive-mind using the grept governance tool.
We have detected that some files need updating to meet the AVM governance standards.
Please review and merge with alacrity.
Grept config source: git::https://github.com/Azure/Azure-Verified-Modules-Grept.git//terraform
Thanks! The AVM team :heart:

Supersceeded by #47


text:
chore: repository governance

Repository governance update
This PR was automatically created by the AVM Team hive-mind using the grept governance tool.
We have detected that some files need updating to meet the AVM governance standards.
Please review and merge with alacrity.
Grept config source: git::https://github.com/Azure/Azure-Verified-Modules-Grept.git//terraform
Thanks! The AVM team :heart:

Supersceeded by #54


text:
chore: repository governance

Repository governance update
This PR was automatically created by the AVM Team hive-mind using the grept governance tool.
We have detected that some files need updating to meet the AVM governance standards.
Please review and merge with alacrity.
Grept config source: git::https://github.com/Azure/Azure-Verified-Modules-Grept.git//terraform
Thanks! The AVM team :heart:

Supersceeded by #22


text:
chore: repository governance

Repository governance update
This PR was automatically created by the AVM Team hive-mind using the grept governance tool.
We have detected that some files need updating to meet the AVM governance standards.
Please review and merge with alacrity.
Grept config source: git::https://github.com/Azure/Azure-Verified-Modules-Grept.git//terraform
Thanks! The AVM team :heart:

Supersceeded by #36


text:
kubeconfig handling

KUBECONFIG is set to a list of config files in powershell profile so that it is defined in powershell external to vscode as well as vscode Integrated Powershell Console and vscode regular powershell terminal. kubectl config get-contexts in all of those three powershell contexts show the clusters from all of the config files. This is expected behavior.
The plugin sidebar shows only the clusters defined in ~/.kube/config.

create cluster1.config and cluster2.config in ~/.kube
set KUBECONFIG in powershell profile:
%USERPROFILE%\WindowsPowerShell\profile.ps1 :
$Env:KUBECONFIG=(get-childitem $env:USERPROFILE/.kube/*config) -join ";"
observe both clusters in kubectl config get-contexts in powershell outside of vscode and vscode Powershell Integrated Console
observe clusters do not appear in plugin sidebar

Hi Tim - thanks for reporting this.  The extension just launches kubectl, so it should pick up KUBECONFIG from its parent environment and the spawned kubectl should inherit that.  You describe that you're setting KUBECONFIG in your PowerShell profile: are you launching VS Code from a PowerShell session where that environment variable is set, or are you launching it from Explorer?  If the latter, could you try running code from the PowerShell command line?
If launching Code from the PS session doesn't help, could you try dumping the value of KUBECONFIG in the VS Code integrated terminal and let us know if it's what you expect?  Thanks!

Ok I see, that makes sense, the environment of code where the extension
runs won't have it set if it is launched from start menu, but the
powershells that code spawns will have it set because they will run the
profile.
I'll check it out.
On Thu, May 24, 2018, 2:39 PM itowlson notifications@github.com wrote:

Hi Tim - thanks for reporting this. The extension just launches kubectl,
so it should pick up KUBECONFIG from its parent environment and the spawned
kubectl should inherit that. You describe that you're setting KUBECONFIG
in your PowerShell profile: are you launching VS Code from a PowerShell
session where that environment variable is set, or are you launching it
from Explorer? If the latter, could you try running code from the
PowerShell command line?
If launching Code from the PS session doesn't help, could you try dumping
the value of KUBECONFIG in the VS Code integrated terminal and let us know
if it's what you expect? Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Azure/vscode-kubernetes-tools/issues/221#issuecomment-391871904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlxKgOcnuXyYCciTcGS9-cA3g11jqWOSks5t1yiqgaJpZM4UNBWV
.

authors: itowlson tlynchpin

repo: Azure/vscode-kubernetes-tools


text:
Validate size of signature against algorithm considering JWE

SymmetricSignatures are now ensuring the size of the signature matches the algorithm.
Authenticated Encryption needed special processing as only the first half of the signature is considered for Aes128CbcHmacSha256, Aes128CbcHmacSha384 and Aes128CbcHmacSha512.

Seems like this also addresses #1743, is that correct?

@TimHannMSFT had not considered #1743

My mistake, I think I got the key size check and the signature size check confused.

In reply to: 1407145465

authors: TimHannMSFT brentschmaltz


text:
[Bug] Instance discovery cache is not thread safe

Where is the issue?

Other (please describe)

AadInstanceDiscovery uses a private global for it's cache but does not synchronize read and writes.
Expected behavior
Instance discovery cache is thread safe
Actual behavior
Instance discovery cache is not thread safe
**Other
sync.Once isn't really needed here either as the only thing it does is init a var, which can be done in it's declaration.

The re-write removed these globals.  We are not seeing anything with the race detector.  Closing this out.

The re-write removed these globals.  We are not seeing anything with the race detector.  Closing this out.

authors: element-of-surprise keegan-caruso


text:
Remove user hint requirement on ssoSilent API

This PR removes the restriction on the ssoSilent API to require an account, login_hint or sid to initiate a request in a hidden iframe and receive a new authorization code. The API will no longer throw an error, but log a warning that there may not be enough information.

Codecov Report

Merging #4123 (14bc8f2) into dev (327931b) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

Flag
Coverage Δ

*Carryforward flag

msal-angular
96.31% <ø> (ø)

msal-browser
88.38% <0.00%> (-0.10%)
:arrow_down:

msal-common
85.11% <ø> (ø)

Carriedforward from fa811dd

msal-core
76.90% <ø> (ø)

Carriedforward from fa811dd

msal-node
81.45% <ø> (ø)

Carriedforward from fa811dd

msal-react
94.17% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files
Coverage Δ

lib/msal-browser/src/error/BrowserAuthError.ts
94.93% <ø> (-0.13%)
:arrow_down:

...owser/src/interaction_client/SilentIframeClient.ts
91.42% <0.00%> (-5.72%)
:arrow_down:

There are a couple of docs that should be updated to reflect that we no longer have this restriction:

https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/926f1c2ba0598575e23dfd8cdd8b79fa3a3d19ff/lib/msal-angular/docs/v2-docs/ssosilent.md
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/06351f0cc63f389d9fbb6b973d9f2417c74fd41f/lib/msal-browser/docs/iframe-usage.md
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/b091029c3a406342d26a9c99729146c116743676/lib/msal-react/docs/hooks.md#usemsalauthentication-hook


text:
chore: update lerna to 6.4.0

Resolution to https://github.com/AzureAD/microsoft-authentication-library-for-js/pull/5517

@microsoft-github-policy-service agree [company="Nrwl"]

@tnorling my pleasure, if you run into any issues or have any feedback on lerna please feel free to ping me. You may or may not know that we (Nrwl) took over stewardship of the project midway through last year and we want to make it the best it can be!


text:
Add one item to readme

From the comment in the PlayerMovement.cs :

make sure whatever you want to be the ground in your game has the tag "Ground"

This will be good to have in the readme.md (which by the way is an awesome readme already!).

Along with this I'm back porting some stuff from an upcoming update to this version. Check out the dev branch for more (Currently broken and under dev atm, will push it soon).

That sounds real good. I've stumbled on some issues with isJumping and isGrounded (even after tagging the floor as Ground). I've been trying to debug it, but if the new version is coming soon I'll use the new version for sure.
I'm on unity 2021 LTS with a 3D Core URP default template. My hunch is that the issue is related to fixedupdate VS update.

The new update should fix a lot of those issues but I know what you are talking about.
The old movement ran solely on the OnCollisionEnter, which in specific edge cases (Rubbing up against a wall while midair then landing) wouldn't fire, so a raycast along with the collision detection was added as a soft patch while I'm working on the main update. Slope support, dynamic crouching to the height of the ceiling, a super stripped back version, etc, etc, etc
The old system only used OnCollisionEnter, this neither a fixedUpdate or update instead it uses "physics steps". Its just the frame rate that the physics run at. It isn't called every frame, but on "physics steps" when collision conditions are met. I could change it too OnCollisionStay to get it to run every frame but it would be pretty wasteful most of the time (Could do checks with use input to only check when necessary).
If you have any code that you wanna change cause, just send in pull request 👌


text:
Wrong Button Used for Hyperlink

Describe the bug
The button used here is the undo button but flipped, for some reason

This does not fit with GD's design language, as the gradient is on the wrong side.
There is a redo button that exists in the game that would make much more sense

I checked that I have the latest version of this mod
Yes

You're right.

Also sorry for taking so long to respond, I'm extremely busy with my university projects so GDDL Int has to wait for now :/


text:
Caching issue with getSchema function

Issue workflow progress

Progress of the issue based on the Contributor Workflow

[ ] 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

Please make sure the graphql-eslint version under package.json matches yours.

[ ] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug
Hi 👋
I've had some issues with tests using eslint's nodejs API and I realized it is because the parser uses a cached schema. This also seems to be the reason why the eslint service needs to be restarted in IDEs when there is a schema change and some rules, e.g no-unreachable-types, don't pick up the change.
I appreciate that caching the schema has performance implications, but without being able to reset the cache it can lead to unexpected behavior.
To Reproduce
Steps to reproduce the behavior:
Valid schema:
type Foo {
  bar: String!
}

type Query {
  foo: Foo!
}

Invalid schema:
type Foo {
  bar: String!
}

type Query {
  hello: String!
}

const pathToValidSchema = '...'
const pathToInvalidSchema = '...'

let eslint = new ESLint({
    useEslintrc: false,
    baseConfig: {
        parser: "@graphql-eslint/eslint-plugin",
        plugins: ["@graphql-eslint"],
        parserOptions: {
            schema: pathToValidSchema,
        },
        rules: {
           "@graphql-eslint/no-unreachable-types": "error"
        }
    },
})

let results = await eslint.lintFiles(pathToValidSchema)

expect(results[0].messages).toHaveLength(0) // ✅

eslint = new ESLint({
    useEslintrc: false,
    baseConfig: {
        parser: "@graphql-eslint/eslint-plugin",
        plugins: ["@graphql-eslint"],
        parserOptions: {
            schema: pathToInvalidSchema,
        },
        rules: {
           "@graphql-eslint/no-unreachable-types": "error"
        }
    },
})

results = await eslint.lintFiles(pathToInvalidSchema).

expect(results[0].messages).toHaveLength(1) // 🟥  <--- This will return 0 errors because it is still using the previous schema

Expected behavior
It should use the new paserOptions.schema and therefore return the correct number of errors.
Environment:

OS: MacOS
@graphql-eslint/eslint-plugin: 3.12.0
Node.js: 16.16

Resolution

As many of the rules have a test guard for caching, getSchema function could have one too.

if (process.env.NODE_ENV !== 'test' && schemaCache.has(schemaKey)) {
    return schemaCache.get(schemaKey);
  }

Caching could be based on content and not filename(s)

While option 1) is quicker to do, option 2) would also make sure that this plugin is working to its fullest in IDEs.

Hi ! Future release with cache invalidation could be tested in the following alpha version 3.13.0-alpha-20221024000319-1089aa0

released in @graphql-eslint/eslint-plugin@3.13.0


text:
Error if path-string contains keyword path

The path is not recognized if the path-sting contains path as in homeopathy.
paths:
  url1: '/homeopathy'

Workaround:
paths:
  url1:
    path: '/homeopathy'

Reporting a problem? Please describe the issue above, and complete the following checklist so that we can help you more quickly.
Issue checklist:

[x] I have validated my config file against YAML Validator to make sure it is valid YAML.
[x] I have run the command in verbose mode (by adding verbose: true to my config) and pasted the output below:

DEBUG: #################################################
DEBUG:   Command run:        capture configs/xxxxxx-wraith-config.yaml
DEBUG:   Wraith version:     3.2.1
DEBUG:   Ruby version:       ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]

DEBUG:   ImageMagick:        Version: ImageMagick 6.8.9-9 Q16 x86_64 2016-06-01 http://www.imagemagick.org

DEBUG:   PhantomJS version:  2.1.1

DEBUG:   CasperJS version:   1.1.1

DEBUG: #################################################
DEBUG:
Config validated. No serious issues found.
Creating Folders
SAVING IMAGES
DEBUG: phantomjs  '/usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/javascript/phantom.js' 'http://test.example.compath' '320x8000' 'xxxxxx/url1/MULTI_phantomjs_test.png' 'body' 'false' 'false'
DEBUG: phantomjs  '/usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/javascript/phantom.js' 'http://example.compath' '320x8000' 'xxxxxx/url1/MULTI_phantomjs_live.png' 'body' 'false' 'false'
/usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:124:in `block in sort_by_diffs': undefined method `[]' for nil:NilClass (NoMethodError)
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:122:in `each'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:122:in `sort_by'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:122:in `sort_by_diffs'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:114:in `sorting_dirs'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:45:in `match'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:31:in `parse_directories'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/gallery.rb:142:in `generate_gallery'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/cli.rb:125:in `block in generate_gallery'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/cli.rb:28:in `within_acceptable_limits'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/cli.rb:122:in `generate_gallery'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/cli.rb:140:in `block in capture'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/cli.rb:28:in `within_acceptable_limits'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/lib/wraith/cli.rb:131:in `capture'
  from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
  from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
  from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
  from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
  from /usr/local/lib/ruby/gems/2.1.0/gems/wraith-3.2.1/bin/wraith:5:in `<top (required)>'
  from /usr/local/bin/wraith:23:in `load'
  from /usr/local/bin/wraith:23:in `<main>'
Loading http://test.example.compath at dimensions: 320x8000

Loading http://example.compath at dimensions: 320x8000

Error with page http://example.compath

Error with page http://test.example.compath

CROPPING IMAGES
COMPARING IMAGES
GENERATING THUMBNAILS
GENERATING GALLERY

[x] I have pasted the contents of my config file below:

browser: "phantomjs"
directory: "xxxxxx"
domains:
  live: "http://example.com"
  test: "http://test.example.com"
...
paths:
  url1: '/homeopathy'
...

I can confirm that bug.

Is there any update on this, I am also facing the same issue.

authors: EXPEsatgupta catchergeese osopolar

repo: BBC-News/wraith


text:
For login purposes, how about a before_capture equivalent that runs just once

Title says it all, the docs aren't super clear on what js files are executed when but it seems like most of the browser automation is made to be run just before certain paths are executed, I just want one that is executed at the beginning of the run. So if I run the spider, it runs the before and logs in to site i've automated out. And if I run capture, it does the same.
Reporting a problem? Please describe the issue above, and complete the following checklist so that we can help you more quickly.
Issue checklist:

[ ] I have validated my config file against YAML Validator to make sure it is valid YAML.

[ ] I have run the wraith info command and pasted the output below:

paste results here

[ ] I have run the command in verbose mode (by adding verbose: true to my config) and pasted the output below:

paste results here

[ ] I have pasted the contents of my config file below:

paste config here

Does this not give you what you need?
http://bbc-news.github.io/wraith/#before_capturehooks
(The before_capture: "javascript/config-level.js" bit, which is run at the beginning of every path).

authors: ChrisBAshton natethinks


text:
Synthseg+ training

Hi,
Firstly, thank you for all the work you've done! Really interesting stuff
I'm trying to create my own model of Synthseg+ by following the tutorial 7 steps. I'm having a bit of difficulty with creating a dataset to train the denoiser, specifically with the sample_segmentation_pairs_d.py script. Do you have any further documentation or examples as to how you obtain the input/target segmentations for the denoiser?
Thank you

Hi,
you will have to be a little bit more specific if you want me to help you ;)
About the documentation: pretty much all the info is either in the code/tutorials or in the paper. You can also have a look at the following issues, where I had a fair bit of re-explaining to do because someone was trying to make the tutorial 7 work but was not using the right inputs.
#45 ValueError: axes don't match array" in sample_segmentation_pairs_d.py
#46 ValueError: axes don't match array in prediction of S1 unit at 7-synthseg+.py

Thanks for the quick reply. I'm getting when I attempt to create an instance of the RandomSpatialDeformation layer, please see the screenshot attached
my inputs to the sample_segmentation_pairs_d function are:
image_dir = './path_to_images_folder'
labels_dir = ['./path_to_labels_folder']
results_dir = './path_to_results_folder'
n_examples = 5
path_model = "./dice_100.h5" (trained s1 model)
segmentation_labels =  "segmentation_labels.npy"
n_neutral_labels = None
please let me know if I can provide more info! Thanks

Thank you for the response, I did manage to get there myself!
I have another issue with the outputs of the sample_segmentation_pairs_d function if you could please provide some more assistance.
I am using the same parameters as outlined above, but I'll repost here:
image_dir = './path_to_image.nii.gz'
labels_dir = './path_to_corresponding_label.nii.gz'
results_dir = './path_to_results_folder'
n_examples = 5
path_model = "./dice_100.h5" (trained s1 model)
segmentation_labels =  "./segmentation_labels_s1.npy" (used to train s1 model)
n_neutral_labels = None
When used to generate results, I get some paired outputs that look appropriate to train the denoiser, and other outputs that are pure noise (see below). I'm thinking that there is some parameter used to build the augmentation model that, when randomly sampled outside of a particular range, is causing the noisy output. However I'm not sure what this may be and I've tried playing around with the upper/lower bounds of the augmentation parameters without any luck so far to try and produce consistently appropriate outputs.
Would you have any potential view on what may be causing the noisy output? Any help would be great thanks!
Appropriate output

Noisy output

again, sorry for the late answer.
I also got some pretty messed up segmentations with the default parameters, but never like that. The worst ones are often almost empty, but I never observed those patterns. But then I guess it depends on the trained and fixed network that you used to obtain those segmentations. Different trainings lead to different networks that respond diffrently to extremely augmented images.
But then is it really a bad thing ? the denoiser might need to see some of those very bad examples during training,  because even if they're hopeless to "denoise" (ie reconstruct), that could still help the denoiser learning what's a good or bad segmentations. So I suggest keeping those guys in for now, and see how removing them affects the training of the denoiser (accuracy, stability, etc.).
Let me know how it goes
Best
Benjamin

repo: BBillot/SynthSeg


text:
Changes to Overlay

Made confirmation box no longer use hookstate and now work on a per-component basis.
Also changed some modal CSS and property names.

New confirmation box:

Old confirmation box:

Same reason as above

repo: BCTCio/components


text:
Feature/css edits

File Browser paging updated
Sorting by headers of File Browser added
Clever Canary files added

Great work @emikoifish !

authors: caaespin emikoifish


text:
Loading Previous X Months Encounters

On the /encounters page Users can Load previous months encounters. This currently has to be done one month at a time.
Investigate a way to improve this functionality, possibly to be able to load more months, possibly X months at a time.

This may be reprioritised after https://github.com/BMMRO-tech/BMMRO/issues/230 is played.

repo: BMMRO-tech/BMMRO


text:
Change default binning threshold to match assembly app

We should have a standard config mechanism to set these defaults rather than have them embedded in the templates.

We should have a standard config mechanism to set these defaults rather than have them embedded in the templates.

That should be doable. I think the original dojo toolkit that we're using was meant to make easy modifications in the html on a per widget basis. But we could come up with a standard config that gets applied and can be extended if needed.
We have AppBase.js for instance that each individual apps .js functionality initially inherits from. Might be able to work off that or something in a similar vein.

authors: chris-c-thomas olsonanl

repo: BV-BRC/BV-BRC-Web


text:
iOS 10's video tags are in BGR instead of RGB

This solves it with a flag in the background material (and a small change in the background shader).
See - http://www.html5gamedevs.com/topic/27723-ios-video-texture-display-issues/?tab=comments#comment-205081 for a discussion about it.
It is the developer's responsibility to set this flag (as I am not sure if it is all iOS 10, or only specific versions).
Note that this is just a suggestion for a solution, if there is a cleaner/better way please comment :smile:

IOS...

authors: RaananW deltakosh


text:
백엔드 객체 설계 - 인터페이스 생성

인터페이스 생성

[x] user
[x] trip
[x] location
[x] photo
[ ] comment

comment phase 2에서 작업 예정

repo: Back-to-Beginner/capstone


text:
load_function seems to fail for a django app

Decorator:
@task(executor=TaskExecutor.SPOOLER)
Error:
ImportError: Failed to import "channel.helpers.update_redis_channels" - No module named helpers
raise ImportError('Failed to import "{}" - {}'.format(dotted_path, ex))
The same function called directly from code without the decorator works fine...
example.ini looks like this:
gid = root
chdir = /app_home_dir
socket = 127.0.0.1:3000
wsgi-file = app/wsgi.py
processes = 8
threads = 4
env = DJANGO_SETTINGS_MODULE=app.settings
logto = /var/log/uwsgi/%n.log
#module = app.wsgi:application
harakiri = 20
buffer-size = 65535
vacuum = True
#thunder-lock = True
pcre = True
max-requests = 5000
py-auto-reload = 3
#Spooling
spooler-import = /spooler_task_file.py
spooler-processes = 4
spooler = /spooler_task_dir
Tracked it down to this call:
uwsgi_tasks.tasks.load_function
def load_function(func_name):
func = getattr(saved_tasks, func_name, None)
if func:
return func
return import_by_path(func_name)
import_by_path doesn't seem to find anything. Any reason this might be? Any way to debug this?
Thanks.

Hi! Is it reproducible with the 0.6 version of uwsgi_tasks?
Please see my comment here: https://github.com/Bahus/uwsgi_tasks/issues/3#issuecomment-124918552

authors: Bahus chokosabe


text:
better visualisation of prefixed routes

something like that would be nice
#        PREFIX "/media"
#        PREFIX       +---"/video"
#        GET          |         +---"/dvds"
#        GET          |         +---"/VHS"
#        PREFIX       +---"/music"
#        GET                    +---"/cds"
#        GET                    +---"/mp3"

output is currently broken:
looks like an io race condition.
> cd /examples/prefix
> bailador -t routes prefix.pl6
Attempting to boot up the app
#     Simple        GET /plain
#     Prefix        ANY /books
    Simple        GET      ┣━━/fiction
    Simple        GET      ┣━━/nonfiction
    P# refix        ANY      ┣━━/childrens
    Simple        GET      ┃           ┣━━/alpha
    Simple        GET      ┃           ┣━━/beta
    Simple        GET      ┃           ┣━━/gamma
  AutoHead       HEAD      ┃           # ┣━━/gamma
  AutoHead       HEAD      ┃           ┣━━/beta
  AutoHead       HEAD      ┃           ┗━━/alpha
    Simple        GET      ┣━━/fantasy
    Simple       POST      ┣━━/fantasy
  AutoHead       HEAD      ┣━━/fantasy
  AutoHead       HEAD      ┣━━/fiction
  AutoHead       HEAD      ┗━━/nonfiction
    Prefix        ANY /alpha
    Prefix        ANY      ┗━━/beta
    Prefix        ANY             ┗━━/gamma
    Simple        GET                #      ┣━━/delta
  AutoHead       HEAD                     ┗━━/delta
  AutoHead       HEAD /plain

repo: Bailador/Bailador


text:
chore(main): release 1.2.3

:robot: I have created a release beep boop
1.2.3 (2024-10-18)
Bug Fixes

define validating workflow (4615f90)
whitespacing (ea82703)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.2.3
:sunflower:

repo: Bane-NOR/azure-pipelines-agent


text:
Typescript TypeCheck errors with this package

node_modules/nuxt-authorization/dist/runtime/components/Can.vue:10:48 - error TS2345: Argument of type 'Ability extends { original: (user: any, ...args: infer Args) => import("D:/Trabajo/NFC/website-public-nuxt/node_modules/nuxt-authorization/dist/utils/index").AuthorizerResponse; } ? Args : never' is not assignable to parameter of type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.
  Type 'unknown[]' is not assignable to type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.

const can = await allows(props.bouncerAbility, ...props.args)
                                                ~~~~~~~~~~~~~

node_modules/nuxt-authorization/dist/runtime/components/Cannot.vue:10:51 - error TS2345: Argument of type 'Ability extends { original: (user: any, ...args: infer Args) => import("D:/Trabajo/NFC/website-public-nuxt/node_modules/nuxt-authorization/dist/utils/index").AuthorizerResponse; } ? Args : never' is not assignable to parameter of type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.
  Type 'unknown[]' is not assignable to type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.

const cannot = await denies(props.bouncerAbility, ...props.args)
                                                   ~~~~~~~~~~~~~

Enabling typescript: {typeCheck: true} in nuxt.config.ts comes up with this error.

The cause of the issue might be because both the server and client utilities export the same functions: allows, denies and authorize but have different signatures.
It seems that during build Nuxt is confused on which one it should be using.
The server version takes an event parameter, while the client version doesn't.
It could be a Nuxt bug. (or maybe vue-tsc?)
Tagging @Barbapapazes
Adding @danielroe for visibility

I can confirm that this is an issue:
For more context:
transforming (6) ../node_modules/nuxt/dist/app/entry.jsnode_modules/nuxt-authorization/dist/runtime/components/Can.vue:12:48 - error TS2345: Argument of type 'PropsArgs' is not assignable to parameter of type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.
  Type 'unknown[]' is not assignable to type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.

12 const can = await allows(props.bouncerAbility, ...(props.args ?? [] as unknown as PropsArgs))
                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/nuxt-authorization/dist/runtime/components/Cannot.vue:12:51 - error TS2345: Argument of type 'PropsArgs' is not assignable to parameter of type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.
  Type 'unknown[]' is not assignable to type 'Ability extends { original: (user: any, ...args: infer Args) => AuthorizerResponse; } ? Args : never'.

12 const cannot = await denies(props.bouncerAbility, ...(props.args ?? [] as unknown as PropsArgs))
                                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 2 errors in 2 files.

Errors  Files
     1  node_modules/nuxt-authorization/dist/runtime/components/Can.vue:12
     1  node_modules/nuxt-authorization/dist/runtime/components/Cannot.vue:12

@Barbapapazes  I also notice that running test and test:types throw errors.
i'm not sure if its related to the release of Nuxt 3.13.2 or vue 3.5

authors: geferon genu

repo: Barbapapazes/nuxt-authorization


text:
🛑 Finance is down

In 99b99fd, Finance (https://www.fin.gov.nt.ca) was down:

HTTP code: 504
Response time: 298 ms

Resolved: Finance is back up in 1e90f29 after 10 minutes.

repo: Barctic/gnwt-monitor


text:
🛑 NWT Housing Corporation is down

In 27d277a, NWT Housing Corporation (https://www.nwthc.gov.nt.ca) was down:

HTTP code: 403
Response time: 449 ms

Resolved: NWT Housing Corporation is back up in 8e41bbe.


text:
🛑 Health and Social Services Authority is down

In 3a6f9d7, Health and Social Services Authority (https://www.nthssa.ca) was down:

HTTP code: 500
Response time: 609 ms

Resolved: Health and Social Services Authority is back up in fa76d56.


text:
🛑 Environment and Natural Resources is down

In 591cdc5, Environment and Natural Resources (https://www.enr.gov.nt.ca) was down:

HTTP code: 504
Response time: 279 ms

Resolved: Environment and Natural Resources is back up in 7c86090 after 50 minutes.


text:
🛑 Legislative Assembly is down

In f1096a5, Legislative Assembly (https://www.ntassembly.ca) was down:

HTTP code: 504
Response time: 337 ms

Resolved: Legislative Assembly is back up in 9457276 after 13 minutes.


text:
🛑 QBitTorrent webUI is down

In a3ecafe, QBitTorrent webUI (https://qbittorrent.local.jonthan.xyz) was down:

HTTP code: 404
Response time: 509 ms

Resolved: QBitTorrent webUI is back up in b8c6329 after 6 minutes.

repo: Baronhez/upptime


text:
flutter_colorpicker too old

I have just installed flutter 2.5, and I am getting the following message:
../../.pub-cache/hosted/pub.dartlang.org/flutter_colorpicker-0.4.0/lib/src/hsv_picker.dart:731:29: Error: The argument type 'PointerEvent' can't be assigned to the parameter type 'PointerDownEvent'.

'PointerEvent' is from 'package:flutter/src/gestures/events.dart' ('../../snap/flutter/common/flutter/packages/flutter/lib/src/gestures/events.dart').
'PointerDownEvent' is from 'package:flutter/src/gestures/events.dart' ('../../snap/flutter/common/flutter/packages/flutter/lib/src/gestures/events.dart').
super.addAllowedPointer(event);
^

From what I can see, the reason is that 'shared_preferences_settings' v. 2.1.0 uses 'flutter_colorpicker' v. 0.4.0, not the latest.

Hi there, thank you for reporting; could you please send a PR with the new version?

shared_preferences: ^2.0.7
rxdart: ^0.27.2
flutter_colorpicker: ^0.6.0

authors: BarthaBRW polaksta


text:
Or inject collapse! Not resolved yet!

Or inject collapse! Not resolved yet! boomboom

And how can anyone help you with such information?

Again, same thing. You provide zero debug, zero information. Either learn how to use your environment or resolve your missing files problem.


text:
big fan

on larry

woa

me too bro 🎩

authors: FloppyDolphin57 Imrglop ZeroMemes

repo: BasedInc/libhat


text:
Support Minecraft Java?

Could you possibly make this support minecraft java?

Thanks for the suggestion!
It is on the TODO list now.

repo: BattlefieldDuck/WindowsGSM


text:
PYMC3 has been renamed to PyMC

Hi,
PyMC3 has been renamed PyMC. If this affects you and you have questions, or you want someone to direct your rage at I'm available! Do let me know how i, or any of the PyMC devs can help.
Ravin

Hi @canyon289 and @twiecki
Thank you for getting in touch. Good to be aware of this. The last time I tried there was no support for GPU training with Variational Inference - https://discourse.pymc.io/t/with-all-the-changes-what-are-the-options-for-advi-training-on-gpus/7918. Do you have an idea of when this will be addressed?
@twiecki citing your response below, I am wondering what kind of parametrization changes you have in mind. This file defines the model. My understanding is that the GPU is needed because of data size.

Usually slow models can be sped up a lot by better parameterization.


text:
Fix safari rendering issues

Fixing issue #72 by setting global font smoothing/antialiasing to antialiased

oh, sorry...

Safari is OK
Chrome is not good

Characters will blur. 👀  ref #40

I've looked into this some more and it seems that Chrome handles antialiasing of text that is Bold or a font size that's not a multiple of 0.5rem differently and thus it shows up fuzzy. This property overall seems pretty finicky. I will keep looking into it to see if there's a way to set it on particular elements instead of the overall body that allows it to work better across the board. There may not be a complete solution however as this property is still experimental and not standard

It is also worth noting that according to caniuse the font-smoothing property only applies on OSX platforms so won't change anything on other platforms. I dont know if this is till the case with latest browser versions but I generally trust caniuse

Hey @jjspace, make sure to merge the latest version of the develop branch so that our CI will run the required checks for this PR. 😉

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: BcRikko jjspace trezy


text:
The "Date created" field is empty on the auto-migration screen

checked on master 5.3.10074.3552

checked on mainnet

authors: Denis-Asipenko Roberrtt

repo: BeamMW/beam-ui


text:
Errors are getting swallowed

Errors are appeared to be getting swallowed when using orchestra.
I've forced an error where the 'el' for a Mn view is not within the DOM,  once I compile and run the code in the browser no error is thrown, making it appear no error has happened.
It is only when I step through my code within the Inspector from the render function where it will go into the catch of this function:
function lib$es6$promise$$internal$$tryCatch(callback, detail) {
    try {
       return callback(detail);
    } catch(e) {
       lib$es6$promise$$internal$$TRY_CATCH_ERROR.error = e;
       return lib$es6$promise$$internal$$TRY_CATCH_ERROR;
    }
}

e consoled out is then the actual message:
message: "An "el" .js-tabled-data-content must exist in DOM"
name: "Error"

This appears to be an issue with es6-promise plugin
https://github.com/jakearchibald/es6-promise/issues/70

This fails when testing this with the plugins directly and no orchestra,  it appears to be a babel/es6 promise issue rather than orchestra

repo: BedeGaming/orchestra


text:
DirectMentions are never detected

When using the starter-go-bot, it creates a subrouter with bot.Messages(slackbot.DirectMessage, slackbot.DirectMention).Subrouter(). Direct messages work fine, but direct mentions do not. At the point when Hear is called on this router, the botID of the bot is not set, and so neither is the botID of the route or the router. However, when the bot is run, the botID of the routers still never gets set. So when Utils.IsDirectMention is called, it's always checking for the regex ^<@>.*.
This can be fixed if you add the line b.SimpleRouter.SetBotID(ID) to Bot.setBotID, then when the bot is run and initialized, it sets the ID for all the existing routers and routes.

+1
Simple fix, it works for me! Thanks @EmmaSimon

This doesn't work for me

@CelinaWard Did you try merging the pull request into your repo? There's also a fork mentioned in the comments of it that should include this fix and a few others.

I didn’t, I just added the line directly in bot.go. When I type git log I don’t see your specific commit.

On May 24, 2017, at 8:08 PM, Emma Simon notifications@github.com wrote:
@CelinaWard https://github.com/celinaward Did you try merging the pull request into your repo? There's also a fork mentioned in the comments of it that should include this fix and a few others.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/BeepBoopHQ/go-slackbot/issues/3#issuecomment-303886812, or mute the thread https://github.com/notifications/unsubscribe-auth/Aa9KHn-iupxGK8PYt1ThGt0Owqff4JNsks5r9MaWgaJpZM4Imgea.

@CelinaWard Double check that it's the same as this: https://github.com/BeepBoopHQ/go-slackbot/pull/4/files
Alternately just clone https://github.com/adampointer/go-slackbot instead of this repo.

Hi Emma,
Thanks for the info! I forgot that my project was using vendoring so I had to update my gvt.
Celina

On May 25, 2017, at 1:42 PM, Emma Simon notifications@github.com wrote:
@CelinaWard https://github.com/celinaward Double check that it's the same as this: https://github.com/BeepBoopHQ/go-slackbot/pull/4/files https://github.com/BeepBoopHQ/go-slackbot/pull/4/files
Alternately just clone https://github.com/adampointer/go-slackbot https://github.com/adampointer/go-slackbot instead of this repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/BeepBoopHQ/go-slackbot/issues/3#issuecomment-304074424, or mute the thread https://github.com/notifications/unsubscribe-auth/Aa9KHvvXqHPOyzQDewhuin0FE9J-dE2eks5r9b2agaJpZM4Imgea.

authors: CelinaWard EmmaSimon jaimemartinez88

repo: BeepBoopHQ/go-slackbot


text:
Need case-insensitive assertions

We are using Behat+Mink+Sahi to test a website that uses CSS text-transform:uppercase extensively. As noted at https://github.com/Behat/Mink/issues/186, the case of text returned by Sahi's getText() varies by browser. This issue has been reported to Sahi at http://sahi.co.in/forums/viewtopic.php?pid=13307 with no real response (as of the time of this writing).
It seems to me that the best solution to this issue is to do case-insensitive matching in the assertions in BaseMinkContext. Even if the Sahi bug did not exist, tests which depend on capitalization are too fragile. Rarely, if ever, do we care about whether the text is capitalized a certain way.
Perhaps this could be activated in the configuration, or it could be specified somehow in the step?
For us the choice is either to override the step definitions in BaseMinkContext, or stop running tests in Firefox.

If BaseMinkContext called $this->assertContains() rather than the global assertContains() function, it would be much easier to override this behavior....

repo: Behat/Mink


text:
question about training

What does this mean, from the README?

Look at your tensorflow eval images to gauge when to stop.

Where do i find tensorflow eval images?

Hello,
While you are running train.py you should also run the tensorboard command. It will print out something like
TensorBoard 0.4.0rc3 at http://Alexs-MacBook-Air-5.local:6006 (Press CTRL+C to quit)
If you then go to that url in your browser you will tensorboards graphs of your total loss, etc. You can also see test images and the annotations of the vehicles. Those eval images are a good indicator of when to stop training.

authors: Bellspringsteen aaronbauman

repo: Bellspringsteen/OurCamera


text:
RandomTileInfo

Add a TileInfo resource that holds different TileInfos with different weights, and randomly chooses one of them, getting replaced with it.

Would probably require #49

repo: BenjaTK/Gaea