Plugin Does Not Work Following Reboot

I have my Mac reboot automatically every night. However, it seems that this plugin breaks when my Mac powers on until I restart Homebridge again after. This is the excerpt from the log. Hope someone can help with this!
[5/31/2020, 6:10:49 AM] Homebridge is running on port 51745. (node:467) UnhandledPromiseRejectionWarning: Error: send ENETUNREACH <IP_ADDRESS>:987     at doSend (dgram.js:697:16)     at defaultTriggerAsyncIdScope (internal/async_hooks.js:296:12)     at afterDns (dgram.js:643:5)     at processTicksAndRejections (internal/process/task_queues.js:85:21) (node:467) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:467) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:467) UnhandledPromiseRejectionWarning: Error: Failed to initialize the Noble object: unknown     at Noble.<anonymous> (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot.js:172:23)     at Object.onceWrapper (events.js:417:26)     at Noble.emit (events.js:322:22)     at Noble.onStateChange (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/@abandonware/noble/lib/noble.js:87:8)     at NobleMac.emit (events.js:310:20) (node:467) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:467) UnhandledPromiseRejectionWarning: Error: Failed to initialize the Noble object: unknown     at Noble.<anonymous> (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot.js:172:23)     at Object.onceWrapper (events.js:417:26)     at Noble.emit (events.js:322:22)     at Noble.onStateChange (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/@abandonware/noble/lib/noble.js:87:8)     at NobleMac.emit (events.js:310:20) (node:467) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) [5/31/2020, 6:10:49 AM] [Config] Homebridge Config UI X v4.21.0 is listening on :: port 8581 (node:467) UnhandledPromiseRejectionWarning: Error: send ENETUNREACH <IP_ADDRESS>:987     at doSend (dgram.js:697:16)     at defaultTriggerAsyncIdScope (internal/async_hooks.js:296:12)     at afterDns (dgram.js:643:5)     at processTicksAndRejections (internal/process/task_queues.js:85:21) (node:467) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4) [5/31/2020, 6:10:51 AM] [Spidey PS4] Found device [Spidey PS4] [5/31/2020, 6:10:51 AM] [Spidey PS4] Finish searching accessories [5/31/2020, 7:56:07 PM] [Blinds] Turning on... [5/31/2020, 7:56:07 PM] [Blinds] WoHand (cf:a4:99:de:b5:88) was failed turning on

Do you happen to know of any way I can modify that? Or is this out of our hands

[5/31/2020, 6:10:49 AM] Homebridge is running on port 51745. (node:467)
  UnhandledPromiseRejectionWarning: Error: send ENETUNREACH <IP_ADDRESS>:987
    at doSend (dgram.js:697:16)
    at defaultTriggerAsyncIdScope (internal/async_hooks.js:296:12)
    at afterDns (dgram.js:643:5)
    at processTicksAndRejections (internal/process/task_queues.js:85:21) (node:467)

  UnhandledPromiseRejectionWarning: Unhandled promise rejection.
                                    This error originated either by throwing inside of an async function without a catch block,
                                    or by rejecting a promise which was not handled with .catch().
                                    To terminate the node process on unhandled promise rejection,
                                    use the CLI flag --unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode).
                                    (rejection id: 1) (node:467)

  [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated.
                                In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:467)

  UnhandledPromiseRejectionWarning: Error: Failed to initialize the Noble object: unknown at Noble.<anonymous> (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot.js:172:23)
    at Object.onceWrapper (events.js:417:26)
    at Noble.emit (events.js:322:22)
    at Noble.onStateChange (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/@abandonware/noble/lib/noble.js:87:8)
    at NobleMac.emit (events.js:310:20) (node:467)

  UnhandledPromiseRejectionWarning: Unhandled promise rejection.
                                    This error originated either by throwing inside of an async function without a catch block,
                                    or by rejecting a promise which was not handled with .catch().
                                    To terminate the node process on unhandled promise rejection,
                                    use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode).
                                    (rejection id: 2) (node:467)
  UnhandledPromiseRejectionWarning: Error: Failed to initialize the Noble object: unknown at Noble.<anonymous> (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/node-switchbot/lib/switchbot.js:172:23)
    at Object.onceWrapper (events.js:417:26) at Noble.emit (events.js:322:22)
    at Noble.onStateChange (/usr/local/lib/node_modules/homebridge-switchbot-for-mac/node_modules/@abandonware/noble/lib/noble.js:87:8)
    at NobleMac.emit (events.js:310:20) (node:467)

  UnhandledPromiseRejectionWarning: Unhandled promise rejection.
                                    This error originated either by throwing inside of an async function without a catch block,
                                    or by rejecting a promise which was not handled with .catch().
                                    To terminate the node process on unhandled promise rejection,
                                    use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode).
                                    (rejection id: 3)

[5/31/2020, 6:10:49 AM] [Config]Homebridge Config UI X v4.21.0 is listening on :: port 8581 (node:467)

  UnhandledPromiseRejectionWarning: Error: send ENETUNREACH <IP_ADDRESS>:987
    at doSend (dgram.js:697:16)
    at defaultTriggerAsyncIdScope (internal/async_hooks.js:296:12)
    at afterDns (dgram.js:643:5)
    at processTicksAndRejections (internal/process/task_queues.js:85:21) (node:467)

  UnhandledPromiseRejectionWarning: Unhandled promise rejection.
                                    This error originated either by throwing inside of an async function without a catch block,
                                    or by rejecting a promise which was not handled with .catch().
                                    To terminate the node process on unhandled promise rejection,
                                    use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

[5/31/2020, 6:10:51 AM] [Spidey PS4] Found device [Spidey PS4]
[5/31/2020, 6:10:51 AM] [Spidey PS4] Finish searching accessories
[5/31/2020, 7:56:07 PM] [Blinds] Turning on...
[5/31/2020, 7:56:07 PM] [Blinds] WoHand (cf:a4:99:de:b5:88) was failed turning on

Error: Failed to initialize the Noble object

This error is the same error as the following Issue, so it seems to be caused by the fact that it is still running before Bluetooth initialization.
https://github.com/futomi/node-beacon-scanner/issues/1
For this reason, I'm looking into how to wait out the Bluetooth initialization process.

Thanks for looking into this! Hope a resolution can be found eventually!

@SSutherland94
I added a delay option to wait for Bluetooth initialization.
Can you check if this can be worked around?
https://github.com/zizi4n5/homebridge-switchbot-for-mac#how-to-use

Didn’t want to leave you hanging, but I’ll gladly test this out once I’m home. Should hear back from me around 8 hours from now

Using version 0.0.12, delay is set to a value between 0 and 30,000 milliseconds. Please try.
It is possible to specify more than 30000ms, but in my tests of operation, it was not possible to start up correctly.

If this doesn't improve the situation, I'm going to try the Bluetooth connection again when operating the Switch.

Worked like a charm! Used delay: 5000. I can go back to nightly reboots and easy-open shades now. Thanks!

I'm glad it worked properly!
Then this Issue is closed.


live patching in patch.py should be moved to the respective projects

So far we had to live-patch a couple of things in python-ptrace. In future we should fix python-ptrace instead and get rid of the live patching code.

This has already been done.


feat(SDK): allow for dynamic SDK discovery

This is a part of #842.

The list of supported SDKs in VRTK is fixed because they are hard coded
into the SDK manager (and its editor). This change modifies the SDK
manager so it looks up the available SDKs by checking the code base for
classes that inherit from one of the base SDK classes. This allows to
create and use additional SDKs without touching the existing VRTK
codebase at all.
Sharing of SDK implementations in a private group of people (e.g. where
everyone signed an NDA) is now possible without needing to share patches
to the VRTK codebase. There is no reason anymore to keep up with changes
to the parts of VRTK one changed to use their own SDK implementations.
To allow for easy specifying of SDK implementations a new "SDK
description" attribute is added. Another "predicate" attribute allows to
mark a static method as a predicate for SDK purposes. The method signals
whether to add or remove the scripting define symbol that is specified
by the attribute by returning true or false respectively. Marking the
same method with multiple predicate attributes is allowed.
The existing SDK implementations have been updated to make use of both
attributes. Usage of the SteamVR plugin in VRTK is now simplified by
using the predicate attribute to add a scripting define symbol that
defines what version of the plugin is currently used in addition to
defining the generic SteamVR SDK symbol.
If a set SDK doesn't exist anymore (e.g. the SDK class was removed) the
SDK manager will use the corresponding fallback SDK instead and log an
error so the problem is known about. The editor shows that error, too,
but won't remove the set SDK from its list of selectable SDKs until the
user overrides it with another SDK. It shows the name of the missing
class in that case instead.
The SDK manager's editor is updated to allow selecting one of the
discovered SDKs. Logic that previously handled the scripting define
symbols is now moved to the SDK manager class itself in form of public
methods. This allows to build scripts that handle automatic building for
different stores as Oculus Home doesn't allow to include SteamVR/OpenVR
libraries, for example. The automatic populating of the SDK object
references like the Linked Objects and Alias Objects is moved from the
editor to a new setting on the SDK manager itself. This has a public
method to trigger manually, too.
Additionally the editor was changed to support undo/redo for all the
possible changes. Proper error messages and hints are now shown in the
editor if needed, too.
The existing auto-managing of the scripting define symbols is now done
whenever needed. This means loading a scene with an active SDK manager
in it will make sure to manage the symbols if the SDK managers setting
says to do so. The behavior for the auto-populating of the SDK object
references is the same with this change. The idea is to always make sure
the current setup is correct for a used SDK manager.

SDKs themselves:

Now inherit from the new public abstract class SDK_Base : ScriptableObject { } to give some type safety for the various kinds of SDKs (system, boundaries, headset, controller).
SDKs specify their "description" by adding a C# attribute called SDK_DescriptionAttribute to their class. The existing SDKs are updated to have this attribute. Each SDK has their own attribute because VRTK allows to implement an SDK without implementing all the other SDK kinds with it (e.g. it's possible to provide a controller SDK without a System, Boundaries or Headset SDK).

VRTK_SDKManager:

doesn't need to run in the editor anymore now:
PopulateAvailableAndInstalledSDKInfos is added and is called in the editor and on build startup to make sure the public static fields available*SDKInfos and installed*SDKInfos are always up to date.
now is able to be used in the build pipeline easily with the new method ManageScriptingDefineSymbols. This will make sure the current scripting define symbols are set for the current SDKs. This method is also used whenever something is changed using the inspector on the SDK manager.
The SDKs to use are adjustable using new *SDKInfo properties like systemSDKInfo. They are of a new type called SDKInfo<BaseType>. You create one by providing the type of an SDK using SDKInfo<BaseType>.FromType<ActualType>. An example would be SDKInfo.FromType<SDK_SteamVRController>.
SDKInfo<BaseType> is serialized using the ActualType's FullName. That allows to uniquely identify the SDK that is set. That's what AvailableSDKInfo<BaseType>.FromTypeName<FallbackType> is for.
SDK_DescriptionAttribute.Fallback represents a fallback SDK (for all kinds of SDK endpoints).
If a set SDK isn't available anymore the fallback SDK is automatically used and an error is logged. Additional errors are only logged when the fallback SDK is actually used (by the instantiation of the current set SDK via the Get*SDK methods). The set SDK that was serialized isn't changed to the fallback SDK and left as is in that case to allow for fixing stuff without changing the setup.
All the SDK infos and SDKs themselves are now cached. The cache is invalidated whenever needed of course.

VRTK_SDKManagerEditor:

is updated to allow to set SDKs by providing a list of the available ones.
allows proper usage of undo/redo for all the features now (it even automatically switches the scripting define symbols according to the undo/redo!).
explains why only a subset of all the SDKs is available in the Quick Select dropdown. It only shows this explanation when it's actually needed, i.e. there are some SDKs not available for all the endpoints/kinds (System, Boundaries, Headset, Controller).
explains when a set SDK is not available and therefore tells you that it's falling back to the fallback SDK instead. It leaves the setting for that missing SDK alone, though. So the missing SDK can actually be seen by type name and is only removed from the SDK list after setting another SDK in its place.

Updated for SteamVR plugin version 1.2.1 and the Daydream SDK that got merged on master.

Too risky to go into 3.1.0 :(

shakes fist
I'm OK with that. 😀


Move "internal use" sentence attached to the wrong function

The sentence was placed in the wrong function's documentation in 27ff120a6121528de9f9a726dfd80a209ee05a1a.
A similar edit was made in sha256.c but the sentence was placed correctly there.
Needs 2.16 backport: https://github.com/ARMmbed/mbedtls/pull/3908

I can see the same error on 2.7, does this not need backports to that branch?

Oh, right, the sentence is misplaced in 2.7 too. Fix incoming.


Browser version dates, please

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[x] New documentation
[x] Correction or update

Details

I really get a lot out of MDN and appreciate all the documentation. It's a tremendous help to me, and to the whole web-developing community.
I was wondering if in the "Browser compatibility" section you could include the date (month+year? year?) of each browser version (even just as a tooltip). Such an addition would make it much easier to judge how widely adopted a given feature is for those of us who don't keep browser version dates in our heads.

This request applies to all pages with a "Browser compatibility" section.
I appreciate your help. Thanks so much for this great site!

Thanks for your request. I'm marking this as a duplicate of https://github.com/mdn/kumascript/issues/1119


modify posterior get_latent to be more consistent

model.sample_from_posterior_z can already handle returning the posterior mean or a sample, so it doesn't make sense to handle this twice (once in the model, once in posterior)
resolves: #331

Codecov Report

Merging #332 into master will increase coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #332      +/-   ##
=========================================
+ Coverage   89.51%   89.6%   +0.09%
=========================================
  Files          32      32
  Lines        2948    2945       -3
=========================================
  Hits         2639    2639
+ Misses        309     306       -3

Impacted Files
Coverage Δ

scvi/inference/posterior.py
92.59% <100%> (-0.05%)
:arrow_down:

scvi/inference/autotune.py
74.44% <0%> (+0.55%)
:arrow_up:

scvi/models/vae.py
88.65% <0%> (+1.03%)
:arrow_up:

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 ebd36c1...a69a723. Read the comment docs.

Nice! Thanks Adam.


Clean up CS8602 warnings (Nullable)

related to https://github.com/dendrodocs/dotnet-tool/issues/1 I need to pick this up to solve both


Demo: image scaling provides incorrect values

Since the demo page forces images into a square, the SSIM values end up being way different than if the images were evaluated on their original aspect ratio and size.
This PR...

Uses canvas of the image's size and compares that.
It adjusts CSS so the new canvas fits nicely in the block.
And as two images with different sizes can no longer be tested against eachother, we alert the user to that error. :)

cc @patrickhulce
Before and after:

@patrickhulce in the meantime https://paulirish.github.io/image-ssim-js/test/browser_test.html has these changes live

ping?


Bump libc to 0.2.142

libc 0.2.141 cannot build successfully on AIX. (CI on AIX is not available yet)
Upgrade libc to 0.2.142 to make cargo build on AIX.

Thanks for being interested in contributing to this project! However, it's difficult to make progress on a pull request lacking for a clear context. Contributors are encouraged to follow the process of submitting a PR in Cargo Contributor Guide, as well as the guideline in the pull request template.
A clear description also helps us to trace back in the future why this change was made, even when the change is quite simple as this one. Thank you!
@rustbot label +S-waiting-on-author

Ooops I should just use @rustbot author.

Hi, libc 0.2.141 cannot build successfully on AIX. (CI on AIX is not available yet)
error[E0308]: mismatched types
   --> src/unix/aix/powerpc64.rs:202:9
    |
201 |     pub unsafe fn si_value(&self) -> ::sigval {
    |                                      -------- expected `unix::sigval` because of return type
202 |         self.si_value
    |         ^^^^^^^^^^^^^ expected `unix::sigval`, found `aix::powerpc64::sigval`
    |
    = note: `aix::powerpc64::sigval` and `unix::sigval` have similar names, but are actually distinct types
note: `aix::powerpc64::sigval` is defined in module `crate::unix::aix::powerpc64` of the current crate

This was fixed after 0.2.141 release. (https://github.com/rust-lang/libc/commit/7a1d2c6f9daa45f88810b93d6e28ed612a001397 )

@bors r+

:pushpin: Commit b1290767ac4917a7e1c3dfdc03dc85903879b43a has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit b1290767ac4917a7e1c3dfdc03dc85903879b43a with merge c5bee5d90221db04db3bad8aa3deaf0f390dfa8b...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing c5bee5d90221db04db3bad8aa3deaf0f390dfa8b to master...

Thanks!


On window resize update size!

This is working for some resizing currently :
https://github.com/grebtsew/dcDeployControl/commit/67dcbe16ee0be2e48c4975227553f23f90b32461


creating database and container for gremlin db

Describe the bug
I am trying to create a database and container for a gremlin db, all the documentation says i should be using the Microsoft.Azure.Cosmos, however I am getting the error:
This is while testing locally
Microsoft.Azure.Cosmos.CosmosException : Response status code does not indicate success: Forbidden (403); Substatus: 0; ActivityId: 8d14c9cc-2a28-438a-8145-93d4c5af75cc; Reason: ("Operation 'POST' on resource 'dbs' is not allowed through Azure Cosmos DB endpoint. Please switch on such operations for your account, or perform this operation through Azure Resource Manager, Azure Portal, Azure CLI or Azure Powershell"
Looking up the error, none of the options have anything to do with my case, I have no network policies, I am within my credit limit
var client = new Cosmos.CosmosClient(CosmosConnectionString);
//Create Database
var createResponse = await client.CreateDatabaseIfNotExistsAsync(DatabaseName);
var db = createResponse.Database;
//Create Container
await db.CreateContainerIfNotExistsAsync(GraphName, PartitionKeyPath);
Expected behavior
it to create a database and container
Actual behavior
error as above
Environment summary
c# sdk, gremlin db in azure cosmos db, visual studio code
Additional context
the db is in the azure postal, but I am running the azure function locally

Hello @EnenDaveyBoy thanks for contacting us. What you need is the Gremlin.net API. I advise you to checkout the following.
https://docs.microsoft.com/en-us/azure/cosmos-db/graph/create-graph-dotnet
There is also a sample here
https://github.com/Azure-Samples/azure-cosmos-db-graph-gremlindotnet-getting-started.git

@EnenDaveyBoy Have you taken a look at the following:
https://docs.microsoft.com/en-us/azure/cosmos-db/sql/troubleshoot-forbidden#non-data-operations-are-not-allowed

The issue is Cosmos DB offers support for multiple different APIs like Cassandra, Mongo, Gremlin, SQL, etc.. The Microsoft.Azure.Cosmos nuget works with the SQL API. Since it is meant to work with SQL API it is blocked on the service because your account is gremlin. You need to use Azure CLI, Azure Powershell, Portal, ARM. You should be able to use the following nuget to create databases through ARM.  https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/cosmosdb/Azure.ResourceManager.CosmosDB/README.md

thanks i have it working with Azure.ResourceManager.CosmosDB, bit of a pain it can't use the normal sdk


How we can retrain KNN for 1000 of faces and keep the performance-optimized.

face_recognition version:1.2.3
Python version: 3.6.7
Operating System: windows-10

Description
@ageitgey
How we can retrain KNN for 1000 of faces and keep the performance-optimized for cpu.
What I Did
I tried to retrain the KNN model on  500 images but when I add new face images the training process start from the beginning.
Is there any way to start the training process only for new images (faces) instead of all.

KNN is not very suitable for face recognition. If you change the jitter parameter, it will confuse the network.

KNN is not very suitable for face recognition. If you change the jitter parameter, it will confuse the network.

Thanks @alessiosavi  for sharing your knowledge. will surly check it.

Due to the nature of the KNN, it's quite impossible to find the K parameter that is suitable for different faces.
If your dataset contains only a few dozen of different people, maybe you can find it with a exhaustive hyperparameter tuning.
You can rely on the Multi Layer Perceptron architecture in order to create a neural network capable of recognize different faces with higher accuracy.
I've made a little project that use this library (face_recognition), linked with a Neural Network. It's awesome see that, starting from 4/5 photos of a person, the network is able to recognize the person using different photos.
You can have a look at my repository:
https://github.com/alessiosavi/PyRecognizer/

KNN is not very suitable for face recognition. If you change the jitter parameter, it will confuse the network.

How to use MPL

You can use my PyRecognizer in order to have a plug-and-play face-recognition tool, without deal with coding. The repository have a video for understand how to train the neural network and how to predict an image (the model provided is tuned for some celebrities). Or you can view the code that i have used here: https://github.com/alessiosavi/PyRecognizer/blob/master/datastructure/Classifier.py#L332
Link to the project: https://github.com/alessiosavi/PyRecognizer

@alessiosavi , While predicting it is taking almost 58 seconds. It too late response,  @ageitgey face_recognition took approximate 2.5 seconds using Flask REST API.
Can I make it faster?

Please open an issue on the repo. Have you a GPU? The problems seems related to the encoding_faces phase. You can see that the most of the time is spent


Allow editing shortcuts that include mouse buttons

There's a particularly annoying limitation in Ubuntu where the "alt+LMB" combination is already reserved by the system which impedes the placing of multiple cursors in the program with said shortcut. Might you consider changing the shortcut or allowing users to change it themselves?

Allowing customization of mouse actions is part of https://github.com/Microsoft/vscode/issues/3130
As for alt+click, that's captured in https://github.com/Microsoft/vscode/issues/3091


Error when attempting to apply the schema

I get an error when attempting to apply the schema:
DEBUG:procrastinate.cli:Log level set to DEBUG
DEBUG:procrastinate.app:Registering queue builtin
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:procrastinate.cli:Exception details:
Traceback (most recent call last):
  File "/usr/lib/python3.9/asyncio/tasks.py", line 492, in wait_for
    fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/elemoine/.cache/pypoetry/virtualenvs/procrastinate--j00n7Xq-py3.9/lib/python3.9/site-packages/aiopg/connection.py", line 183, in _poll
    await asyncio.wait_for(self._waiter, timeout)
  File "/usr/lib/python3.9/asyncio/tasks.py", line 494, in wait_for
    raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/elemoine/src/procrastinate/procrastinate/cli.py", line 46, in handle_errors
    yield
  File "/usr/lib/python3.9/contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "/home/elemoine/src/procrastinate/procrastinate/cli.py", line 118, in cli
    app_obj = procrastinate.App.from_path(dotted_path=app)
  File "/home/elemoine/src/procrastinate/procrastinate/app.py", line 49, in from_path
    return utils.load_from_path(dotted_path, cls)
  File "/home/elemoine/src/procrastinate/procrastinate/utils.py", line 30, in load_from_path
    module = importlib.import_module(module_path)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/home/elemoine/src/procrastinate/procrastinate_demo/app.py", line 17, in <module>
    app.open()
  File "/home/elemoine/src/procrastinate/procrastinate/app.py", line 330, in open
    self.connector.open(pool)
  File "/home/elemoine/src/procrastinate/procrastinate/utils.py", line 118, in wrapper
    return sync_await(awaitable=awaitable)
  File "/home/elemoine/src/procrastinate/procrastinate/utils.py", line 168, in sync_await
    return loop.run_until_complete(awaitable)
  File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/home/elemoine/src/procrastinate/procrastinate/aiopg_connector.py", line 186, in open_async
    self._pool = await self._create_pool(self._pool_args)
  File "/home/elemoine/src/procrastinate/procrastinate/aiopg_connector.py", line 31, in wrapped
    return await coro(*args, **kwargs)
  File "/home/elemoine/src/procrastinate/procrastinate/aiopg_connector.py", line 191, in _create_pool
    return await aiopg.create_pool(**pool_args)
  File "/home/elemoine/.cache/pypoetry/virtualenvs/procrastinate--j00n7Xq-py3.9/lib/python3.9/site-packages/aiopg/pool.py", line 155, in from_pool_fill
    await self._fill_free_pool(False)
  File "/home/elemoine/.cache/pypoetry/virtualenvs/procrastinate--j00n7Xq-py3.9/lib/python3.9/site-packages/aiopg/pool.py", line 191, in _fill_free_pool
    conn = await connect(
  File "/home/elemoine/.cache/pypoetry/virtualenvs/procrastinate--j00n7Xq-py3.9/lib/python3.9/site-packages/aiopg/connection.py", line 483, in _connect
    await self._poll(self._waiter, self._timeout)
  File "/home/elemoine/.cache/pypoetry/virtualenvs/procrastinate--j00n7Xq-py3.9/lib/python3.9/site-packages/aiopg/connection.py", line 185, in _poll
    await asyncio.shield(self.close())
  File "/home/elemoine/.cache/pypoetry/virtualenvs/procrastinate--j00n7Xq-py3.9/lib/python3.9/site-packages/aiopg/connection.py", line 263, in close
    self._close()
  File "/home/elemoine/.cache/pypoetry/virtualenvs/procrastinate--j00n7Xq-py3.9/lib/python3.9/site-packages/aiopg/connection.py", line 251, in _close
    self._loop.remove_reader(self._fileno)
  File "/usr/lib/python3.9/asyncio/selector_events.py", line 341, in remove_reader
    return self._remove_reader(fd)
  File "/usr/lib/python3.9/asyncio/selector_events.py", line 286, in _remove_reader
    self._selector.modify(fd, mask, (None, writer))
  File "/usr/lib/python3.9/selectors.py", line 390, in modify
    self._selector.modify(key.fd, selector_events)
FileNotFoundError: [Errno 2] No such file or directory
Error: [Errno 2] No such file or directory

My issue is related to IPv6. I need to use PGHOST=<IP_ADDRESS> rather than PGHOST=localhost. I'll create a PR that changes dev-env for that.


Aeic mangled names 5.7

Cherry-pick of https://github.com/apple/swift/pull/59797 to the 5.7 branch.
Some mangled names for non-abi functions included $ by mistake.
This PR also improves the explanation for compatibility entry points that use the mangled names of newer, non-abi functions.
No related issue.

@swift-ci please test


Update README.md

Thank you for visiting my repository.
I added my favorite singer at the last.
I hope I'm on the right track. Thanks.

Thanks. I will surely check it out.
Have a nice week.


Network protocol error for subscriptions is raised (after publishing)

Describe the bug
A network protocol error for ongoing subscriptions is raised after publishing a message to the server. The error cancels the subscriptions.
Platform:

Windows 10
Version: 21H2
Build: 19044.1348

Client:

Download: https://mosquitto.org/download/
Version: 2.0.14

Server:

Download: https://github.com/chkr1011/MQTTnet/tree/master/Tests/MQTTnet.TestApp.AspNetCore2
Version: 5e5818d7df78de6a0a1342c9dca692346f70ad97 (latest master)

Important: This issue is not only related to the test app. We also experience it in our server app.
Which project is your bug related to?

MQTTnet.Server standalone

To Reproduce
Steps to reproduce the behavior:

Navigate to the MQTTnet.TestApp.AspNetCore2 project directory
Remove the lines 88-92 in Program.cs (to make the app build and run)
Run the app via dotnet run --framework net5.0
Subscribe via ./mosquitto_sub -h localhost -p 1883 -t '#' -q 1
Publish via ./mosquitto_pub -h localhost -p 1883 -t "test/foo" -m "message"

Expected behavior
We expect no network protocol error to occur (which cancels the subscription).
Screenshots
Subscription:

Publish:

Additional context / logging
We found a couple of workarounds for this problem. The following commands avoid a network protocol error:

./mosquitto_sub -h localhost -p 1883 -t '#' -q 1 -i "client id" or
./mosquitto_sub -h localhost -p 1883 -t '#' -q 1 -V 31 or
./mosquitto_pub -h localhost -p 1883 -t "test/foo" -m "message" -V 31

So specifying a client id or the protocol version 31 helps. The protocol versions 311 (default) and 5 are faulty.
Using the MQTTnet client does also work btw.
Greetings!

Please test with latest version 4.0 and reopen the ticket if the issue persists.


Adonis can't handle more than 9 request per sec

I use https://github.com/Utwo/adonis-realworld-example-app
Package version
"@adonisjs/framework": "^5.0.13"
Node.js and npm version
node v12.13.1
npm 6.12
Issue
Adonis can't handle login request
I tested with hey load generator
hey -z 30s -c 5 -m POST  -d<EMAIL_ADDRESS>"password":"ykkqwe"}}' -H "Content-Type: application/json" http://SERVER:8080/users/login

When I test the CPU, it's 100 %

Local test

No idea what exactly you are testing. Try it on a fresh app with hello world to see if it's really related to AdonisJS or your own code

Also, since you are saving a new user in POST /users/login, the password hashing takes place and Bcrypt is intentionally a slow algorithm.
Read this https://stackoverflow.com/questions/15763086/bcrypt-for-password-hashing-because-it-is-slow and https://auth0.com/blog/hashing-in-action-understanding-bcrypt/

https://github.com/Utwo/adonis-realworld-example-app/blob/master/app/Controllers/Http/AuthController.js
i try only login

Already shared the reason. Please read how Bcrypt works

Is it normal only 10 logins per second?

Read the links. Don't expect me to read them out for you and share the summary with you.


Nukes JSONStorage on logout

Details

Drops several JSONStorage properties
Implements deleteAllObjectsForBucketName

cc @eshurakov

Thanks for reviewing this one sir!!

Thanks for reviewing this one sir!!


Monitoring performance regressions and system call expectations

I am working on functionality to monitor performance regressions and get expectation tests on system calls from our test suites. Feedback is welcome. Here is a rough overview of features I would like to have. Feedback welcome.

/usr/bin/time -v (-l on OS X) on the GNU integration test suite. I haven't figured out how to shim this in our unit tests
strace/dtrace to log system calls so we can write expectation tests
Linux perf and OS X Instruments - here are the ARM hardware performance counters available on M1 https://twitter.com/dendibakh/status/1452360400343748609
Comparing these results with GNU/BSD coreutil binary baselines - on OS X I planned using homebrew to grab the prebuilt GNU with an option to build from source.
Compiling with LLVM instrumentation for performance guided optimization
Run LLVM IR through https://github.com/google/souper to flag peephole optimizations that LLVM is missing
Monitor performance of various https://github.com/facebookincubator/BOLT binary reordering strategies
An AFL++ (fuzzing) and KLEE (execution path search) harness for each utility. Ideally we could generate both from rust-clap.
QEMU functionality to test multiple operating systems and architectures on the same machine - I am doing this manually using https://github.com/utmapp/UTM - but I would like it fully automated for a Linux host so it plays well with Github's Ubuntu runner - the CI could detect which utilities have modified lines and only run the QEMU tests for those.
Optionally log dependencies as part of the build to a compressed tarfile - it would speed rebuilds and give binary reproducibility.

@chadbrewbaker are you still working on it?
thanks

I would keep it open and keep pestering me for updates :)
Last weekend I figured out pinning rust-nightly with the 1-january-2022 release has a LLVM backend that still works with KLEE. Should be drop in replacement with the KLEE rig for GNU coreutils. I also had some conversations with fuzzer devs so we can put KLEE/fuzz seeds in a regression suite.
/usr/bin/time -v I have working for both Linux and OSX, can fork and push when I get a chance. Might add in some optional download Python/R so the data is meaningful - histogram plots, resource scaling plots, and x/y/t/z plots of worst case runtimes.
perf  I'm still blocked on my M1 because of an upstream QEMU issue with Docker. Will circle back when I have a chance on my linux x86 boxen.
uftrace/GraalVM - just starting. Effectively this will be a linter that warns variables are too large or default function paths should be explicitly specialized.  Haven't looked at pahole style struct analysis for rust.
Souper - I abandoned what I had and I am now going off of the upstream rust CI script to also bring in profile guided optimization and BOLT reordering. https://github.com/rust-lang/rust/blob/master/src/ci/pgo.sh  As a deeper dive I am looking into Debian and Fedora downstream packaging so distro users actually see the performance gains.
MIRI/Valgrind/sanitizers - I think I have enough testing to make a PR.
Hyperparameter tuning (compiler options, cache sizes) - Google open sourced Vizer. I think I can drive it with a JSON list of clang/gcc optimization parameters and some hooks into cache sizes.  Only rust side work is uniformly specifying cache sizes across the coreutils so they can be tuned.

Here I want to share my results about evaluating PGO effects on different software - link. Here you can find multiple results (with numbers), how PGO is integrated into multiple projects, etc.
Not sure how much of these projects are related to uutils (I guess one of the good examples would be this one - hck). I think we can try to rebuild all uutils (via cargo-pgo it should be pretty easy to do), run on a "usual" workload, recompile and benchmark it again.


Automate the refresh_token question

So.. recently I developing some pixiv application,
the thing is there is no documentation except from community forum upbit/pixivpy and this module.
My question is:
How to automate the token refresh?
My thought is making this module into schedule or cron in every hour, then store it to somewhere like memcache or storage,
so i could make it simple with pixivpy3 and call every endpoints with
api = AppPixivAPI()
api.auth(refresh_token=#GET_FROM_MY_STORAGE)

but i think it's a bit overkill tho..
Is there a simplicity the automated token refresh apart from this? thanks in advance

Once obtained, the refresh_token can probably be used semi-permanently. If you need to refresh it, just run api.auth when it is no longer available and Pixivpy terminates the exception.
See also: https://github.com/upbit/pixivpy/issues/182#issuecomment-912705349


Performance on Chinese Text

Has this framework been tested in Chinese? It is reported that LLaMA performed not well on corpus of Chinese.

We have not conducted extensive testing on Chinese, but we have tested some Chinese language questions and found that our trained model has some Chinese language conversation abilities. We put the results online for your review. Please scroll down to the bottom of the page to see the Chinese examples.
There are good and bad examples. Here are some good examples.

We welcome you to use our code for larger-scale training and more testing, thank you.

The performance seems to be unsatisfactory. It is expected to see a foundation model pretrained (or finetuned) for Chinese specially. Of course I will try to finetune on my own dataset. Thanks for your efforts~

Hi,
Thanks for your feedback.
The initial goal of our open source toolkit is to provide a pipeline to help everyone finetune LLM rather than to get particularly good specific performance. It will be good if we can pre-train a large Chinese model from scratch, but the advantage of finetuning is faster training with fewer resources.
I am very much looking forward to your trial of fine-tuning your own dataset and welcome to report new results. We also plan to do Chinese finetuning in the near future. The trained model and results will be open sourced soon.
Thanks


Linter overhaul and update

Signed-off-by: Carson Farmer<EMAIL_ADDRESS>Description
See https://github.com/textileio/js-threads/pull/400 for details

close?


Fix async-tungstenite vulnerability

Versions of tungstenite up to 0.20 contain a DoS vulnerability described in RUSTSEC-2023-0065.
Fix: updated async-tungstenite in utils-aio from 0.16 to 0.25.1

thanks, we will take a look at this. we need to first make sure that the new async-tungstenite works properly in our wasm build.


Transaction Page - Multiple Page - Beyond Paging

Settlement Process requires-
Selection of transaction beyond Paging
event though Company Filter is applied sometimes transaction count becomes more than 50 to settle
So beyond page selection required
Initiated by @vinpahilwani
Verified by @mitulpanch

This will be different from Company Page - Beyond Paging
Settlement Process requires Company / Contact selection first, and Changing filter disables Settlement Process
So this should not break,
Changing Filter will reset selected Transaction, changing Page will hold selected Transactions


migrate bisect to rust dissect

Improving on the old script:

Detecting minor changes in diagnostics (warnings/errors) between versions.
Group version ranges by similarity.

Additionally, refactored the crate into a proper CLI with commands, to add the new command along:
infra run --bin "solidity_testing_solc" -- dissect "target/test.sol"

// SPDX-License-Identifier: UNLICENSED
pragma solidity '*';

contract Test {
    string value = 'Fireworks 🎆';
}

@Xanewok comments addressed. Please let me know if you have any other suggestions.


Add API description

Unless I'm mistaken, there's no API published. It makes exploring the package difficult. For example, it was not obvious to me where to find the fitted distribution's parameters. I had to look at your code to find out :-) (fortunately, it's very well written so it wasn't hard :-) )

i get the following error by calling some functions
if name == 'main':
freeze_support()
...


Updated change log

Please review master. I will tag 1.5.0 after this PR is merged.

What about https://github.com/php-http/HttplugBundle/pull/142 for HttpAsyncClient?

We have to remove https://github.com/php-http/HttplugBundle/blob/master/DependencyInjection/HttplugExtension.php#L437-L438 because it's no longer required since #135.

There is already mention of #142.

Support for autowring in Symfony 3.3

I just created some PRs for 1.5.0. Just smaller things. Im fine with releasing 1.5.0 after they are accepted.

@dbu Are you fine with releasing 1.5.0?

sorry, at a workshop yesterday and today. if you are confident for the
release i trust you guys. but if you want me to have a look i can take a
bit of time tomorrow.

Im confident. But there is no rush. I will release this on Monday if not before.

I'm confident too :)

Thank you.
Yeah #166 is a blocker


fix: weblate badges to better fit repo guidelines [Weblate]

Reduce the total badges and use the (...|...) syntax. (as mentioned above)

Replace /license with /l.

License: /l

Default to https://hosted.weblate.org (it seems I can make server optional based on the docs)

The parameter is for an uncommon optional attribute, like an alternate registry URL.

Review badge paths

/SERVICE/NOUN/PARAMETERS?QUERYSTRING e.g: /github/issues/:user/:repo

- https://github.com/badges/shields/pull/6677#issuecomment-873433265

Just let me know if there're any other problems!

Related Issues

Relates to: https://github.com/badges/shields/pull/6677

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @SethFalco!

  Generated by :no_entry_sign: dangerJS against d42d11dd4bfb7a857644c102963c0497146523b9

Hoping I fixed everything up now.
Sorry again for the pain! ^-^'
Let me know if there're any other problems, and I'll address them up.
Weblate entity count

Changed title/file/class from Weblate entity count -> Weblate entities
Changed path from /weblate/count/{entities} -> /weblate/{entities}

Weblate user statistic

Changed file from weblate-user-statistics to weblate-user-statistic to match class/title. (whoops)
Changed path from /weblate/statistic/{user}/{entities} -> /weblate/{entities}/{user}
Request/badge now uses the appropriate verb everywhere, and uses a switch to translate it to select the correct property from the API response

Sorry for the delay, will look at this one later today. Could you rebase/address the merge conflicts when you get a chance?

Edit: Unfortunately, I'm unable to see why ci/dockercloud-stage failed. thinking (404)

Don't worry about this one, it's not a required check and has a history of being a bit of a flake. Docker also claim to be shutting this service down (refs #6634) thought they apparently either forgot or are running behind, and this could possibly be a symptom that they've finally done it

Excuse the mess, I messed up while rebasing and did a forced push which changed 20,000 lines. 😆 (https://github.com/badges/shields/commit/cfb70fcc5373e5a9579efeb3f27189335956f38c)
I fixed it now, just spammed the PR activity a little. ^-^'


Incorrect Image references on wiki page

Q
A

content fix?
yes

New article?
no

Related issues?
n/a

What's in this Pull Request?
This article incorrectly references 3 images within it.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

thx Matt, that's not visible in the actual publishing location at https://dev.office.com/sharepoint/docs/spfx/toolchain/integrate-gulp-tasks-in-build-pipeline, but we can absolutely get this fixed also in the GitHub side.


Add note about issues with PSModulePath to windows-agent.md

Related agent PR: https://github.com/microsoft/azure-pipelines-agent/pull/4778

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

#sign-off


WorkloadSelector in DestinationRule resulting in route error

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
My configuration below.
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: vs-0
spec:
  hosts:
  - '*.example.com'
  http:
  - route:
    - destination:
        host: productpage.default.svc.cluster.local
        subset: v1
        port:
          number: 9080
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: dr-0
spec:
  host: productpage.default.svc.cluster.local
  subsets:
  - name: v1
    labels:
      version: v1
  workloadSelector:
    matchLabels:
      app: productpage
---
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: se-0
spec:
  hosts:
  - www.example.com
  ports:
  - number: 8080
    protocol: HTTP
    name: port-1
    targetPort: 9080
  resolution: DNS
---
apiVersion: v1
kind: Service
metadata:
  name: productpage
spec:
  selector:
    app: productpage
  ports:
  - port: 9080
    targetPort: 9080
    name: http-0

I tried curl -H"Host:www.example.com" http://<IP_ADDRESS>:8080/ and received 503. After I removed the workloadSelector in the DestinationRule, I tried again and received 200.
In my configuration, the workloadSelector in DestinationRule shouldn't affect the route correctness of curl -H"Host:www.example.com" http://<IP_ADDRESS>:8080/. So the behavior above is really confusing for me.
Version
$ istioctl version
client version: 1.20.0
control plane version: 1.20.0
data plane version: 1.20.0 (5 proxies)
$ kubectl version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.3

Additional Information
No response

The workload selector in DestinationRule governs where the DestinationRule is applied (in your case it would be limited to only the sidecars for the productpage app) so its likely the traffic is going through a proxy that has no DestinationRule applied and your VirtualService consequently relies on a subset that isn't defined. When you remove the selector in your DestinationRule the subset can then be defined on all proxies and traffic flows as expected.

https://istio.io/latest/docs/reference/config/networking/destination-rule/#DestinationRule
According to the documentation, the DestinationRule applies on the pods with label app: productpage, which means that the subset is defined on these pods instead of that only these pods can see the subset.
Besides, the workloadSelector in ServiceEntry doesn't cause other pods can't see the service. Why the workloadSelectors in DestinationRule and ServiceEntry make different effects?

"Criteria used to select the specific set of pods/VMs on which this DestinationRule configuration should be applied." (emphasis my own) ref
This is the specific verbiage on the field in DestinationRule. It's stating that the field is used to set where the DestinationRules configuration (in your case, the subset) should be applied. It goes on to explain one intended use case which I think helps to explain things:
"For example, if specific sidecars need to have egress TLS settings for services outside of the mesh, instead of every sidecar in the mesh needing to have the configuration (which is the default behaviour), a workload selector can be specified."  ref
I can't speak to exactly why the same field name in different resources has a different effect/behavior but I see how this can be confusing and frustrating. I'd be happy to work with you to improve the clarity of the documentation if you'd like to get some commits in the Istio project or if you just want to leave some suggestions here I can see about updating the documentation myself..

Thank you @ilrudie. According to your description, WorkloadSelector in DestinationRule is to specify which pods (request sender) to apply the DR rule. But in ServiceEntry, it is used to specify the endpoints of service. That is to say, WorkloadSelector defines source in DR but destination in SE. It seems very interesting. Is there some special design inside?

Hi @NaturezzZ, I'm not sure I understand your question. You can look at the envoy config generated by Istio on any of the proxies to confirm whether or not the subset is being configured if that's what you're getting at but I suspect it's not.

Hi @ilrudie, I add some supplementary explanations in https://github.com/istio/istio.io/pull/14617. Would you mind take a look? Thank you.

Thanks for adding this @NaturezzZ, I left a few comments/suggestions on the wording of the note but it looks like it'll be a helpful clarification.

Thanks for polishing @ilrudie 🎉


[IC3 ACS Management GW ] API Review

New API Review meeting has been requested.
Service Name: IC3 ACS Management GW
Review Created By: Daniel Ortega
Review Date: 11/29/2023 08:00 AM PT
Onboarding Record:
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Update the Phone Numbers API with new methods that will enable customers to acquire phone numbers via a shopping cart-like experience. This includes a new browse API that can return multiple available phone numbers synchronously, instead of using LROs to search for a single phone number to be acquired by the customer. The numbers returned by the browse method are not reserved, thus we also provide the ability to create and manage reservations, which lock phone numbers for a limited time. Then, when the customer is ready to acquire all numbers in the reservation, they can start a purchase operation that will apply to all the reserved numbers.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Daniel Ortega
Service Name: IC3 ACS Management GW
Review Created By: Daniel Ortega
Review Date: 11/29/2023 09:00 AM PT
Onboarding Record:
PR: https://github.com/Azure/azure-rest-api-specs/pull/26040
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Update the Phone Numbers API with new methods that will enable customers to acquire phone numbers via a shopping cart-like experience. This includes a new browse API that can return multiple available phone numbers synchronously, instead of using LROs to search for a single phone number to be acquired by the customer. The numbers returned by the browse method are not reserved, thus we also provide the ability to create and manage reservations, which lock phone numbers for a limited time. Then, when the customer is ready to acquire all numbers in the reservation, they can start a purchase operation that will apply to all the reserved numbers.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Notes:

DELETE /availablePhoneNumbers/reservations/{reservationId} must delete the reservation so that a GET on reservations won't include it. Alternatively, change to a POST /availablePhoneNumbers/reservations/{reservationId}/:cancel to only set the state to cancel. Consider whether a cancel or delete (or both) is best from a customer scenario perspective. Validate that when going with DELETE that a following PUT won't fail on a reservation with an id that was previously deleted.
PUT /availablePhoneNumbers/reservations/{reservationId}/phoneNumbers/{phoneNumber} should return the phoneNumber resource, not the reservation. DELETE /availablePhoneNumbers/reservations/{reservationId}/phoneNumbers/{phoneNumber} should return 204 No Content. Alternatively, consider supporting bulk operations with json+merge+patch (needs more design on specifics). POST actions for add/remove are another option but aren't very desirable if they can be avoided.

New API Review meeting has been requested.
Service Name: IC3 ACS Management GW
Review Created By: Daniel Ortega
Review Date: 01/24/2024 09:00 AM PT
Onboarding Record:
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description:
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Daniel Ortega
Service Name: IC3 ACS Management GW
Review Created By: Daniel Ortega
Review Date: 01/24/2024 09:00 AM PT
Onboarding Record:
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description:
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here


Soft Launch Clearinghouse

This issue will be dedicated to any problems encountered in our soft launch.

Before we even can ask for feedback, we're dealing with some CSS difficulties.  Our embedded CSS in the SVG files do not appear to work, and we're still haunted by invisible avatars.
Avatar issue appears to be a be a processing issue (Hugo will not generate 'unused' images that don't have their permalink accessed from the resources.get command.  At the moment, we manipulate the string of the PNG image for all images, in order to order the formats in the most efficient manner.  There does not appear to be an option to force resources to be generated, so I'll have to look at this a little further.
Embedded CSS is a little silly, as I forgot to point the CSS reference towards the published site domain.

Feedback
After politely asking for some input, and providing a little bit of prodding to say something other than "It's really neat", we have a few issues we can explore before moving onto the refactors and final touch issues.
Issues

Background SVG not appearing in landscape mode on iPhone 12 mini safari browser

1 report of this issue, several other Safari viewers support landscape
Aberration?

Radio buttons not rending correctly on Safari

Cactus emoji top-left centered in very small radio bubble

Project/Repo links need better spacing
SVG fonts not loading in some banners

Maybe a Inkscape pulls from local sources in its text editor?
Need to find generally available fonts.

Firefox browsers kinda chug while animated.

Comments

'Good', 'neat', 'awesome', 'fancy', 'great' all used to describe.

Fairly biased pool of people, but I'll take it.

Animations should sync with the direction the user is browsing

This is slightly tricky, as our background elements don't loop.

Is possible though

'Tool' Icons could link to tool home pages for more clarity

Difficult.  We inject these images based on the class name used in DevIcon CSS.

Would need to curate a dictionary of tool websites, accessible in both the Javascript and HTML

Highlights could be better

Very much agree

Font?

One respondent said it could be more professional

Night image

Mixed reaction, either need better image or axe this feature entirely

I will add to these lists as I receive more input.
Actions

Need to research the safari specific display bugs, as well as Inkscape fonts.
CSS changes to URLs area
vanquish the Nightman :( (should help animation chugginess somewhat)

Possible if easier than anticipated

Tool links

We'll implement these changes, begin the CSS refactor and then create a final touches issue, which will enumerate the various loose threads I need to tie up to call this portfolio a wrap.


ESLint : Some things can't be ignored

Hello,
I open this new issue which follows this other issue. I discovered that ESLint is powerful, but this time a little too much. Syntax rules are applied to “props” component and can't be ignored. This is unpleasant because if you ignore something and if you pass it as props, props warn or error will not ignore and you couldn't ignore it.
A short example :
import React from 'react';

export default function MyComponent(): JSX.Element {

    // eslint-disable-next-line @typescript-eslint/naming-convention
    const [openMenu, setOpenMenu] = React.useState(false);

   // ESLint error and warn isn't ignore on open that must be IS_OPEN
    return(
    <MySubComponent
         open={openMenu}
    />
    )
}

Kind regards,
Kilian GOËTZ.

That's more a bug from the typescript pluggin of eslint than a bug of eslint itself. That's annoying but clearly nothing that we can change here. You may want to report this to the pluggin maintainers.

I've just noted that open should for sure be warned has it has not been defined earlier. open is a property of your jsx element that typescript inferred as a constant Boolean. You can add an eslint ignore to ignore that particular issue on that time. That's by no mean a bug ...

That's more a bug from the typescript pluggin of eslint than a bug of eslint itself. That's annoying but clearly nothing that we can change here. You may want to report this to the pluggin maintainers.

Thanks for quick answer, I will contact plugin maintainers or find a solution.

I've just noted that open should for sure be warned has it has not been defined earlier. open is a property of your jsx element that typescript inferred as a constant Boolean. You can add an eslint ignore to ignore that particular issue on that time. That's by no mean a bug ...

You can't declare it before JSX, it's a “props”, his type is declared in child component (example below). I already tried to add an ESLint ignore, but it doesn't work.
import React from 'react';
import MySubComponent from './MySubComponent.tsx';

export default function MyComponent(): JSX.Element {

    const [openMenu, setOpenMenu] = React.useState(false);

    return(
    <MySubComponent
         open={openMenu}
    />
    )
}

import React from 'react';
import {Drawer} from '@mui-materials';

interface MySubComponentProps{
    open : boolean
}

export default function MySubComponent(props:MySubComponent): JSX.Element {

    return(
    <Drawer
        open={props.open}
    />
    )
}

I've just tried your first example and I don't have the problem. ESLint does not tell me anything about the props.

Hi,
I have no longer the issue. I think the issue came from my IDE cache 😕.


tf.compat.v1.keras.backend.get_session gives erroneous deprecation warning

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.0.0
Python version: 3.6.8
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
Accessing tf.compat.v1.keras.backend.get_session gives a deprecation warning telling you to use tf.compat.v1.keras.backend.get_session.
Describe the expected behavior
Accessing tf.compat.v1.keras.backend.get_session should not give a deprecation warning (since we're explicitly accessing the compat.v1 namespace). Or it should direct the user to the correct function, if tf.compat.v1.keras.backend.get_session is not the right access point, rather than telling the user to use the namespace they're already using.
Code to reproduce the issue
import tensorflow as tf

tf.compat.v1.keras.backend.get_session

This results in the warning
The name tf.keras.backend.get_session is deprecated. Please use tf.compat.v1.keras.backend.get_session instead.

(note that we're accessing tf.compat.v1.keras.backend.get_session, not tf.keras.backend.get_session).

@drasmuss ,
When tried running the given code, i didn't receive any warning for TF-2.0 and 2.0rc2. Please find the gist of colab.
Can you please provide gist if the issue is replicating from your end?Thanks!

For some reason the warning doesn't show up when executing through colab, you need to run it as an external command. See gist here.

I have the same issue.

@drasmuss @fperrotta I ran it in my local (Mac Os) as well as in Colab. I don't see any warnings. Later today I will check it on Windows10. Thanks!

I wonder if this is happening because i am loading a trained model file (hdf5) with tensor 1.15 and now i am importing it to apply with K.session and loader updates to tensor 2.x.

Have tried it in my local(ubuntu 18.02) and also on colab with tensorflow 2.2.0-rc2 and I didn't run into any issue. I am closing this issue right now. Please add additional comments for us to open this issue again. Thanks!

When I run the same gist from above (https://github.com/tensorflow/tensorflow/issues/33182#issuecomment-540553089), switching to TF2.2rc2, I still see exactly the same error.

@drasmuss Can you please share the test.py file. Thanks!

The file is created within the gist, see this code
with open("test.py", "w") as f:
  f.write("import tensorflow as tf\ntf.compat.v1.keras.backend.get_session")

I'm also getting this problem. It doesn't happen if I paste the lines directly into an ipython console, but it does if I put them in a separate module and import that (or if I run that module directly from the command line)

As mentioned above, the warning doesn't show up when executing within colab, you have to run it as an external command. I have updated the gist to use 2.5.0, and it shows the same warning message as before.

was able to replicate and resolve the issue in TF 2.5 by adding these lines.
import logging, os
logging.disable(logging.WARNING)
os.environ["TF_CPP_MIN_LOG_LEVEL"] = '3'

please find the gist here

That doesn't fix the problem, it just hides the erroneous warning.

I could reproduce the issue with TF 2.6 .Please, find the gist here.Thanks!

Hi There,
This is a stale issue. As you are using an older version of tensorflow, we are checking to see if you still need help on this issue. Please test the issue with the latest TensorFlow (TF2.7 and tf-nightly). If the issue still persists with the newer versions of TF, please feel free to open it in keras-team/keras repository by providing details about the issue and a standalone code to reproduce the issue. Thanks!
Please note that Keras development has moved to a separate Keras-team/keras repository to focus entirely on only Keras. Thanks!

The issue still persists in TF 2.7, I created a new issue in the Keras repo here https://github.com/keras-team/keras/issues/15792


Dashboard GraphQL endpoint for product attributes

We'll need an endpoint listing all existing product attributes along with their defined values.

In PR #1945 we've added the following query:
attributes {
    edges {
      node {
        id
        slug
        name
        values {
          id
          name
          slug
        }
      }
    }
  }

In order to fetch attributes of a specific product you can use:
{
  product(id: $productId) {
    name
    attributes {
      name
      value
    }
  }
}


Fix clikt upgrade

This PR fixes deprecated usages of a package that powers our CLI.
Test Steps:

Run tests
Double-check a few CLI commands and ensure they run okay

Changes

Updated deprecated usages for confirmation dialogues and error PrintMessages

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[x] Added tests?

Linked Issues

Fixes #12337
Fixes #13055

LGTM! Tested the cli and it works still :) Good job!


NPC shooting other projectiles than arrows without bow (sentinel event or sth)

[01:55]	Goma_Terzu: mcmonkey : could it be possible for you to add NPC with "Weapons" that shoot stuff you decide for sentinel? The only reason I make this script is that my npc hold weapons like an ak-47 and shoot magma_cream (looks like a bullet with texture pack on).
[01:57]	mcmonkey: Goma_Terzu: there's two standing sentinel requests for that on the issues page
[01:58]	mcmonkey: Goma_Terzu: One is to fire arrows regardless of held item, the other is to support Crackshot plugin
[01:59]	Goma_Terzu: mcmonkey : so I would like to see the option to even use item_projectile stuff instead of arrows at all
[01:59]	mcmonkey: Goma_Terzu: That's a bit more difficult to do 0.o
[01:59]	Goma_Terzu: kind of like a shoot command you can configure with sentinel :D
[01:59]	mcmonkey: Goma_Terzu: item_proj is pure Denizen, and Sentinel doesn't link Denizen too strongly
[01:59]	mcmonkey: I could maybe add an event for it
[02:00]	mcmonkey: like "on sentinel attacks:"
[02:00]	mcmonkey: or something
[02:00]	mcmonkey: and then you do - shoot
[02:00]	mcmonkey: and mark the event completed
[02:00]	mcmonkey: or something like that
[02:01]	mcmonkey: Goma_Terzu: If you want the event thingy  isaid, open a Sentinel issue for it
[02:01]	mcmonkey: feel free to just copy/paste  what I said lol

oh, I added an attack event a while back.
it's supported in Denizen via Depenizen!


Add filter-prefix option to update config.

There is not currently a way to include only matching versions from the release update service
This adds filter-prefix entry to Update section of melange.yaml. Specific use case for filter-prefix is a streamed package (ruby).
After the corresponding change to make use of this filter lands in wolfi, then we can update ruby-3.2 to enable the release monitor like with:

update:
enabled: true
manual: true
filter-prefix: "3.2."
release-monitor:
identifier: 4223

Melange Pull Request Template

Functional Changes

[ ] This change can build all of Wolfi without errors (describe results in notes)

Notes:
SCA Changes

[ ] Examining several representative APKs show no regression / the desired effect (details in notes)

Notes:
Linter

[ ] The new check is clean across Wolfi
[ ] The new check is opt-in or a warning

Notes:

I was just going through my open PRs. It feels like this is still useful.  @rawlingsj I'm fine to close it or update it.  let me know what you think is right.

note to self, if this lands, need update to wolfctl also (as seen  https://github.com/wolfi-dev/wolfictl/pull/692)


Demo Page

Vue-Medium Editor needs a demo site.
I build one already but it needs some polishing. Currently not public.
A site that shares design with the medium-editor demo page would be great. RawGit may be used to get the original CSS to extend it with few styles inside style tags.

How about an git checkout --orphan gh-pages branch? Push there and people can jump in.

Good point. Hope you like it.
Closed by #78c9d12


repo maintained

Hello,
is this still maintained / active?
there are some useful PRs that could be merged :)
thanks!

Hey @nonotest,
Yes this repo is still being maintained / is active. I've been traveling / working a lot recently and have fallen behind in addressing issues and PRs.
I'll do my best to get those PRs merged in and a new release out in the next couple days. And take a look at issues as well.
If anyone's interested in being a maintainer shoot me an email (jesse [dot] sessler [at] gmail)
Thanks! :)

thank you! I am happy to help where I can, let me know if you need help reviewing things etc.

Going to close this issue now. I have a lot more time on my hands and will be much more active.
Apologies for the long absence. I've addressed / merged all open PRs and have gone through over half the open issues. Will be addressing the other half and trying to solve as many as possible going forward.


Uploading zero files

In version 2.1.3, Droplet attempts to upload zero files if uploadAllFiles is triggered when there are no valid files to upload.
Version 0.10.0 of Droplet had the following check to prevent that:
if ($ember.get(this, 'validFiles').length === 0) {
    // Determine if there are even files to upload.
    return false;
}

Is there a reason why this was removed? Can the check be restored?

Fixed by 95b98e3.


Show access rights in the lookup handle window

Description of the feature, modification, idea or suggestion

it will be clearer
Proposed implementation details (optional)
No response

Added to latest nightly build 👍


Fixes to missing or duplicate html tag IDs

@AparnaKarve : please, review

@martinpovolny @dclarizio This looks good, although not fully complete because I still see duplicate ID warning in the browser console for userid, password and verify fields.
There are certain instances in the haml where we use ng-show. When ng-show is false, the elements are hidden but still rendered and that's the reason why those dup IDs still exist.
The solution for this case would be to use ng-if, which will ensure that the elements do not get rendered at all.
Long story short, it's just a matter of don't render vs. hide, and we should choose don't render
For now we could merge this PR and I can tackle the rest of the dup IDs in a separate PR.


Update to sjs-dom 2.0.0

Supersedes #30.

@sjrd I'm assuming this means we need to bump to 2.0.0 here?

No, this is only a test dependency :)

Oh, whew!

If it hadn't just been a test dependency, I wouldn't have let you introduce that dependency at all when I first reviewed. 😉


[RESTEASY-1628]

Changed treatment of text media types without charset parameter to add
"charset=UTF-8" by default.

Replaced by https://github.com/resteasy/Resteasy/pull/1111.


Feedback for “Installation”

Hi there,
Noticed a small mix-up: @kuma-ui/core uses npm for its install command, but @kuma-ui/next-plugin goes with pnpm. It's a bit confusing 😅. Could we stick to one for both? Would make things smoother.
Cheers!

Thanks for the feedback! Actually, this just indicates that Kuma UI can be installed with any package manager, thus we provide npm, yarn, pnpm sections so you can stick to any preferable package manager you like!


dualstacklinuxpipeline

Reason for Change:

This PR does include dualstack linux control plane and dataplane pipeline test cases
This PR also includes dualstack windows control plane APIs, verified locally and does not impact on current pipeline, waiting for Vipul's dropgz windows to commit and then use windows dropgz images later one for windows test cases
This also includes dualstack linux conformance test
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

can you fix the title please?

too many conflicts, use #2098 instead


Image doesn't implement RN static functions (ie. Image.prefetch())

** Before reporting this bug, please...**

Check the latest documentation: https://docs.nativebase.io/
Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
For discussion purpose make use of NativeBase discord: https://discord.gg/TSgCw2UPmb

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behaviour:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behaviour
A clear and concise description of what you expected to happen.
CodeSandBox/Snack link
It would be easier for us to debug if you can reproduce the error in a codesandbox link or a snack link. You can use the codesandbox template/snack template.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform

NativeBase version [e.g. 3.0.1]
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Browser version [e.g. 22]
React Native version [e.g. 0.64]
Expo sdk version [e.g. 41]
node [e.g. 14.16.1]
yarn or npm [e.g. 6.1]

Additional information

Add any other context about the problem here.
Is the bug present in both iOS and Android or in any one of them?
If you want your issue to be looked at quicker, please attach a snack reproducible with your issue. Makes it easier for us!

Hi @garrett-gottlieb, Thanks for reporting a bug can you please provide small snack or codeSandbox example.

Sure: https://codesandbox.io/s/gallant-wind-uox23

Hi @garrett-gottlieb, This is issue has been resolved in V3.3.4 of NativeBase.


Add a unit test to verify new register process in broker with controller mode

Add a unit test to verify new register process in broker with controller mode.
related issue: https://github.com/apache/rocketmq/issues/5989
The issue tracker is used for bug reporting purposes ONLY whereas feature request needs to follow the RIP process. To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
It is recommended to start a discussion thread in the mailing lists in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
Generally, fixing an issue goes through the following steps:

Understand the issue reported;
Reproduce the unexpected behavior locally;
Perform root cause analysis to identify the underlying problem;
Create test cases to cover the identified problem;
Work out a solution to rectify the behavior and make the newly created test cases pass;
Make a pull request and go through peer review;

As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
BUG REPORT

Please describe the issue you observed:

What did you do (The steps to reproduce)?

What is expected to see?

What did you see instead?

Please tell us about your environment:

Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

FEATURE REQUEST

Please describe the feature you are requesting.

Provide any additional detail on your proposed use case for this feature.

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

If there are some sub-tasks involved, use -[] for each sub-task and create a corresponding issue to map to the sub-task:

sub-task1-issue-number: sub-task1 description here,
sub-task2-issue-number: sub-task2 description here,
...

merged


[Bug]: Queue toggle button is covered when queue is shown on vertical monitor

🔍 Have you checked that you are using an auto updating method or latest version of the extension?

[X] I have checked that I am on the latest version.

🔍 Is there already an issue for your problem?

[X] I have checked older issues, open and closed

Choose the extension for bug report.
Full Screen Mode
ℹ Environment / Computer Info
Spotify for macOS (Apple Silicon)
<IP_ADDRESS>4.g39a25e2c
Spicetify v2.36.14
Theme: Better-Bloom / darkgreen
Extensions: fullScreenWrapper.js, oldCoverClick.js, theme.js
Custom apps: marketplace, better-local-files, ncs-visualizer, lyrics-plus

📝 Description
I've seen a lovely new queue button (at least it seems new because I haven't noticed it before) to the right hand side of the play controls buttons, which allows the queue to be shown while in fullscreen mode. However, when being used on a vertical monitor, the queue actually covers that button, so there isn't any way to minimise the queue again without exiting fullscreen mode. This can be seen in the attached screenshot.
I was wondering if there might be a way to either shift the play information to the left so that it is still visible next to the queue, or if another queue minimisation button could be added at the top right of the queue window itself or something?
Thank you!
📸 Screenshots

Ahh lol didn’t test it out on vertical mode, it's a rough draft, will take a while to polish the UI though.
Thanks for pointing it out.
Meanwhile, there is the keyboard shortcut Q, which you can use to toggle it.

Ah wonderful, thank you!

Would be neat if it'd hide when you leftclick anywhere outside the queue.

Should not be an issue anymore, reduced the width of queue panel in vertical mode.


[Match] git clone: could not read Password for 'https://': terminal prompts disabled

Issue Description
INFO [2017-01-10 16:47:53.52]: Cloning remote git repo...
INFO [2017-01-10 16:47:53.52]: $ GIT_TERMINAL_PROMPT=0 git clone 'https://' '/var/folders/rv/mc9j2bm521d1qr8wp4k8vlth0000gr/T/d20170110-62498-yv52cn'
INFO [2017-01-10 16:47:53.53]: ▸ Cloning into '/var/folders/rv/mc9j2bm521d1qr8wp4k8vlth0000gr/T/d20170110-62498-yv52cn'...
INFO [2017-01-10 16:47:53.69]: ▸ fatal: could not read Password for 'https://': terminal prompts disabled
Cloning into '/var/folders/rv/mc9j2bm521d1qr8wp4k8vlth0000gr/T/d20170110-62498-yv52cn'...
fatal: could not read Password for 'https:/': terminal prompts disabled
ERROR [2017-01-10 16:47:53.69]: Exit status: 128
"ERROR [2017-01-10 16:47:53.98]: Error cloning certificates git repo, please make sure you have access to the repository - see instructions above"
When running match via Jenkins it fails with the above error message.
Running it via ssh it fails the same way.
Running it locally (with a logged in user) it works.
My guess it can not access the keychain to retrieve local network passwords.
The user itself can do this.
Environment
Jenkins 2 with Pipeline
Slave with OS X 10.11.6
Xcode 8.2

Hi @olbrichj - have you taken a look through our Jenkins Integration documentation?
As you probably know, since you can't type in a password during your CI builds, match & Git will have trouble using the https authentication method unless your build machine has its keychain set up with the right credentials for your repository.
The error message you provided is letting you know that match could not determine the right password to use. It needed to prompt you, but on CI, it is not allowed to prompt because that would cause the build to hang.
Our suggestion would be to investigate the Keychains and Provisioning Profiles Plugin mentioned here.
Please let us know how that works out for you 👍

I'll close this issue for now


Issues training the ytvis_2019 model

Hi Bowen,
Thanks for your excellent work and code! I am retraining the video instance segmentation model on the Youtube VIS 2019 dataset. I managed to train the model, but the quantitative result on the CodaLab turns to be very low (of only about 40).
The command I used for training is:
python3 train_net_video.py \
    --config-file configs/youtubevis_2019/swin/video_maskformer2_swin_base_IN21k_384_bs16_8ep.yaml \
    --num-gpus 8 \
    MODEL.WEIGHTS swin_base_patch4_window12_384_22k.pkl

The backbone weight is got from:
wget https://github.com/SwinTransformer/storage/releases/download/v1.0.0/swin_base_patch4_window12_384_22k.pth
python tools/convert-pretrained-swin-model-to-d2.py swin_base_patch4_window12_384_22k.pth swin_base_patch4_window12_384_22k.pkl

Then I submitted the output/inference/results.json after the training to CodaLab, but only got 40 accuracy. I also tried to rerun the evaluation using output/model_final.pth, and the results are almost the same.
The config files are untouched. I am able to reproduce the correct result using the pretrain model, so I assume that my environment and dataset setups are ok. I also checked the tensorboard output and the loss curve looks good. Could you help to check if there is anything wrong with my training process? Thanks!

Please use Mask2Former COCO instance segmentation pre-trained checkpoints.

Got it. Thanks for your reply!

Hi @bowenc0221 ,
I have used the pretrained coco model to initialize the video model on ytvis_2019. However, the mAP is about 50 using swin-base, still much slower than the results in the paper.
However, when loading the pretrained model, I do see the following warning. Do you have any suggestions where the issues may come from?

Thanks!


Call the quickfixtextfunc function for multiple entries

To reduce the cost of calling a VimScript function for every quickfix list entry,
call the function for multiple entries.

I can confirm that it makes the feature much quicker when dealing with big quickfix lists.

After the PR, I rewrote the QuickFixTextFunc like this:
fu QuickFixTextFunc(info) abort
    if a:info.quickfix
        let qfl = getqflist({'id': a:info.id, 'items': 1}).items
    else
        let qfl = getloclist(a:info.winid, {'id': a:info.id, 'items': 1}).items
    endif
    let l = []
    for idx in range(a:info.start_idx - 1, a:info.end_idx - 1)
        let e = qfl[idx]
        let fname = fnamemodify(bufname(e.bufnr), ':t')
        if strchars(fname, 1) <= 8
            let fname = printf('%8s', fname)
        else
            let fname = printf('%.7s', fname)..'…'
        endif
        let lnum = printf('%5d', e.lnum)
        let col = printf('%3d', e.col)
        call add(l, fname..'|'..lnum..' col '..col..'| '..e.text)
    endfor
    return l
endfu

./src/vim -Nu NONE -S <(curl -Ls https://gist.githubusercontent.com/lacygoill/57d3cd8b5313159f42af43704ebfa7a8/raw/08926a728e7ee97dee6a426aa6eba11a5869bc2f/profile_quickfixtextfunc.vim)
:QfTf 8

Results:
   1000 entries:   0.002 seconds to run :copen
                   0.037 seconds to run :copen with 'qftf'  18 times slower
   2000 entries:   0.002 seconds to run :copen
                   0.073 seconds to run :copen with 'qftf'  36 times slower
   4000 entries:   0.004 seconds to run :copen
                   0.147 seconds to run :copen with 'qftf'  36 times slower
   8000 entries:   0.011 seconds to run :copen
                   0.300 seconds to run :copen with 'qftf'  27 times slower
  16000 entries:   0.026 seconds to run :copen
                   0.596 seconds to run :copen with 'qftf'  22 times slower
  32000 entries:   0.034 seconds to run :copen
                   1.224 seconds to run :copen with 'qftf'  36 times slower
  64000 entries:   0.077 seconds to run :copen
                   2.605 seconds to run :copen with 'qftf'  33 times slower
 128000 entries:   0.136 seconds to run :copen
                   5.448 seconds to run :copen with 'qftf'  40 times slower

This time, the "slowness" is constant.
Thank you very much @yegappan.


Configure ODBC drivers / libraries in the ingestion container

Mssql & Azuresql uses pyodbc package, but it needs odbc drivers to be configured or else it returns failure

from slack:
We tried to add dependency of Oracle and SQL Server to Ingestion docker image. However, this cannot be done due to a primary reason that both [Oracle](https://stackoverflow.com/questions/71040681/qemu-x86-64-could-not-open-lib64-ld-linux-x86-64-so-2-no-such-file-or-direc) and [MS SQL Server Drivers](https://github.com/MicrosoftDocs/sql-docs/issues/6494#issuecomment-905434817) don't support Mac M1 Chip.

Oracle has been fixed already

In this same piece of work we should also make sure that we can ship the db2 plugin that right now has issues building on M1 https://github.com/ibmdb/python-ibmdb#pre-requisites

@akash-jain-10 what is remaining here?

@harshach just tried to run the db2 plugin installation with their latest version 0.3.8 and still getting an arch error on M1. Same error as discussed here https://github.com/ibmdb/python-ibmdb/issues/708
What we're currently doing is not adding db2 by default when installing all. We can update this after the lib has updated their builds.
@akash-jain-10 not sure if there's any way to ship this package on our images without getting into this issue. Otherwise users might need to install db2 inside the containers if needed

@akash-jain-10 any reason we want to make this M1 dependent only? At worst, we can have multiple archs right. This really affects the users right now. I have seen this question pop up multiple times. Anyone who is doing a POC is doing it on Linux and not M1. We are essentially handicapping ourselves by trying to go for single arch images

Hello @harshach . Closing this ticket as we have covered Oracle and MSSQL Database drivers within the Ingestion container. Will be creating a new one for ibmdb and track it there as we would be waiting for ibm community to provide drivers for arm-64 architecture.


Lint proposal: Avoid passing BuildContext to providers

@riverpod
int fn(FnRef ref, BuildContext context) {} // KO

@riverpod
class MyNotifier extends _$MyNotifier {
  int build() => 0;

  void event(BuildContext context) {} // KO
}

I can work on it. I am working on my first contribution

I should create a new file in riverpod_lint/lib/src/lints and create a DartLintRule right?

Yes

I have made a PR and there is a problem. The flutter format command is deprecated can you pls check.

You can either change the CI to use dart format or ignore the error for now.

I didn't know I should not do that. Is there any resources, discussion or discord message about this?

There are no docs except pub.dev page on custom_lint. You need to find everything yourself.

This was implemented in a previous PR


[Bug]: Memory Leak Issue

Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS, Android
@rnmapbox/maps version
#main
Standalone component to reproduce
import React from 'react';
import {
  MapView,
  ShapeSource,
  LineLayer,
  Camera,
} from '@rnmapbox/maps';

const aLine = {
  type: 'LineString',
  coordinates: [
    [-74.00597, 40.71427],
    [-74.00697, 40.71527],
  ],
};

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView style={{flex: 1}}>
        <Camera centerCoordinate={[-74.00597, 40.71427]} zoomLevel={14} />
        <ShapeSource id="idStreetLayer" shape={aLine}>
          <LineLayer id="idStreetLayer" />
        </ShapeSource>
      </MapView>
    );
  }
}

Observed behavior and steps to reproduce
When navigating to a screen with a map and then navigating back or to another screen, the map does not unload properly. Every time we're loading a screen with a map in it, the memory adds up until it causes a memory exhaustion crash. This occurs both on iOS and on Android.

Expected behavior
No response
Notes / preliminary analysis
No response
Additional links and references
No response

Same issue on my project

I also have this issue.

@KristofferEriksson I've tried on current master, one with 10.11 as mapbox dependency. And It was working me just fine. I've replace BugReportExample.js with the code you've pasted bellow and then opened closed the BugReportTemplate example.

I'm closing this as cannot reproduce.

@bradstiff added a fix for that - #2707

Beautiful. Looking forward to the release!
On Thu, Mar 16, 2023, 12:22 AM Miklós Fazekas @.***>
wrote:

@bradstiff https://github.com/bradstiff added a fix for that - #2707
https://github.com/rnmapbox/maps/pull/2707
—
Reply to this email directly, view it on GitHub
https://github.com/rnmapbox/maps/issues/2591#issuecomment-1471387855,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDU6IMCJ32XCO3JPPNDK3DW4KWS7ANCNFSM6AAAAAAUVBHQI4
.
You are receiving this because you were mentioned.Message ID:
@.***>


[For Test] Upgrade 'spring-boot-starter-parent' to 2.5.0-M3.

This PR is used to test whether there is dependency problem if upgrade to spring-boot-2.5.0-M3.

Upgrade 'spring-boot-starter-parent' to 2.5.0-M3.
Upgrade 'spring-boot-dependencies' to 2.5.0-M3.
Upgrade 'spring-cloud-dependencies' to 2020.0.2.
Update pom.py to fit Spring milestone repo.

Hi, @kushagraThapar
Could you please fix the pipeline failure by supporting deleteAllById?
Refs:

https://dev.azure.com/azure-sdk/public/_build/results?buildId=797609&view=logs&j=b56a6aa9-cec1-5a24-2cb2-6d10acd51237&t=f662e9e9-bb13-592c-8f2c-ec0d01338260&l=23
https://github.com/spring-projects/spring-data-commons/blob/2.5.0-M5/src/main/java/org/springframework/data/repository/CrudRepository.java#L120
https://github.com/Azure/azure-sdk-for-java/blob/azure-spring-data-cosmos_3.5.0/sdk/cosmos/azure-spring-data-cosmos/src/main/java/com/azure/spring/data/cosmos/repository/CosmosRepository.java#L37

You can add commits to this branch directly.

Hi, @kushagraThapar
Could you please fix the pipeline failure by supporting deleteAllById?
Refs:

https://dev.azure.com/azure-sdk/public/_build/results?buildId=797609&view=logs&j=b56a6aa9-cec1-5a24-2cb2-6d10acd51237&t=f662e9e9-bb13-592c-8f2c-ec0d01338260&l=23
https://github.com/spring-projects/spring-data-commons/blob/2.5.0-M5/src/main/java/org/springframework/data/repository/CrudRepository.java#L120
https://github.com/Azure/azure-sdk-for-java/blob/azure-spring-data-cosmos_3.5.0/sdk/cosmos/azure-spring-data-cosmos/src/main/java/com/azure/spring/data/cosmos/repository/CosmosRepository.java#L37

You can add commits to this branch directly.

Done.

Hi, @kushagraThapar .
Could you please help to investigate the pipeline failure (java - cosmos - ci)?

Hi, @kushagraThapar .
Could you please help to investigate the pipeline failure (java - cosmos - ci)?

@chenrujun - all of the spring data cosmos tests are failing to load application context. This could be related to the new spring boot version.
Regarding encryption test failures, that also seems to be related to reactor issue -
java.lang.ClassCastException: reactor.core.publisher.MonoSingle$SingleSubscriber cannot be cast to reactor.core.Fuseable$QueueSubscription

I am on-call this week, won't be able to get time to look at these failures, can you please investigate the spring data cosmos tests failures and this above exception?

@kushagraThapar

I am on-call this week, won't be able to get time to look at these failures, can you please investigate the spring data cosmos tests failures and this above exception?

 All tests passed. 😄


Add anchor tag options to buttons

Currently, IconButtons take an href property that creates an  tag in the page. I am working on a project where I'd like to use an IconButton to trigger a file download. HTML5 allows for  to cause an immediate download of the file. Also  achieves similar behavior. This feature could be implemented with an anchor property for buttons where the programmer defines the whole  tag or by a target property that would be included in the generated  tag.

If you pass those props to the IconButton they should be applied to the a root element that's created when you pass the href prop.

  <IconButton
    href="someplace.com"
    download
  />

@lourd Thank you. Is there a way to include this in for the docs?

It's at the bottom of http://www.material-ui.com/#/components/icon-button

Other properties (not documented) are applied to the root element.

This question is not about anchor tags. Is there a way to add anchor links the button like #someAnchor ?


New ResellerClub constructor argument: source IP address

Source IP address for Guzzle connections (CURLOPT_INTERFACE and socket context option bindto).
Default is '0' which means let the system choose the IP.

Thank you.


Feature Request : Is posible to add the "AllowFiltering" parameter to HxSelect?

The behavior is the same as the "AllowFiltering" parameter in the HxMultiSelect .

HxSelect is a native browser input where such a modification is impossible.

(However you can start typing on keyboard when you open the select and most browsers will jump to the corresponding item.)


Animation doesn't trigger based on "container" key in "scroll" mode

No matter what I set the container to for the id, it's always the same result when I target different ids on my page. Please advise! :)

Hi @tenthyoung ,
Could i have a look at your implementation. Would be good if you could show the code on a platform such as codesandbox and link it here.
Thank you


Custom head tag

 Issue by joaosoares
Thursday Jan 19, 2017 at 01:21 GMT
Originally opened as https://github.com/storybooks/getstorybook/issues/25

Since get-storybook hides the config folder when building a create-react-app project, is there another way to include custom tags in the head of the iframe?

See head.html docs at: https://storybooks.js.org/docs/react-storybook/configurations/add-custom-head-tags/
I hope this answers your question. Please re-open if not!