Unsubscribing WS channel not removing from the collection

Hi,
This is awesome thanks. I was coding something similar myself not long ago, but no need now. How do I donate?
I am having one issue with ws. When I subscribe to a ticker, then unsubscribe then subscribe to another ticker, it doesn't seem to forget the one I unsubscribed from and resubscribes it again with the second one.
Screenshot attached. Where it says SUBBING pair I am only sending one subscribe command, but the old unsubscribed one is still in the collection. Any ideas? Thanks.

Interesting find! Thanks for reporting this, caught two bugs while investigating - can you try the beta release with a fix?
npm install<EMAIL_ADDRESS>
Details here if you're curious: https://github.com/tiagosiebler/ftx-api/pull/9
Regarding donations - always appreciated on my ETH (ERC20) address, unless you have a preferred alternative: 0xd773d8e6a50758e1ada699bb6c4f98bb4abf82da
Let me know once you've given the beta some testing. If all is well I'll publish it to release properly. Thanks!

Great, thanks! A real quick look shows things to be working as expected. I’ll carry on developing around this version for a little bit and let you know if I spot anything.
Dropped a small donation to your address.
Cheers,
Simon
From: Tiago @.>
Reply to: tiagosiebler/ftx-api @.>
Date: Friday, 30 April 2021 at 23:10
To: tiagosiebler/ftx-api @.>
Cc: slpn1 @.>, Author @.***>
Subject: Re: [tiagosiebler/ftx-api] Unsubscribing WS channel not removing from the collection (#8)
Interesting find! Thanks for reporting this, caught two bugs while investigating - can you try the beta release with a fix?
npm install @.***
Details here if you're curious: #9https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftiagosiebler%2Fftx-api%2Fpull%2F9&data=04|01||b11fa03f24624d98a88108d90c24b8c4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637554174128052290|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=KpOOQ25fnNjdSX48gTHu9dsk184fKUSHJqkmuvt2JVY%3D&reserved=0
Regarding donations - always appreciated on my ETH (ERC20) address, unless you have a preferred alternative: 0xd773d8e6a50758e1ada699bb6c4f98bb4abf82da
Let me know once you've given the beta some testing. If all is well I'll publish it to release properly. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftiagosiebler%2Fftx-api%2Fissues%2F8%23issuecomment-830426727&data=04|01||b11fa03f24624d98a88108d90c24b8c4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637554174128052290|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Tx8uGD6PXIDQ%2FsyABo%2FiMdaUdnLCDWDv%2Faqwl6isPRk%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFY273NDVZQ4QTJTIBHULOLTLMTEFANCNFSM434H32GQ&data=04|01||b11fa03f24624d98a88108d90c24b8c4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637554174128052290|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=vDtAQ9eFGhrIEmyMsJljJbTa%2FkgKIFepIy9kyvBxw7Y%3D&reserved=0.

Moved from beta to the latest release. Thanks!


Add a parallelism problem

Nice!
On Wed, May 16, 2018 at 11:23 PM, Christopher Rackauckas <
<EMAIL_ADDRESS>wrote:

I worked parallelism into @rsulli55 https://github.com/rsulli55 's
stock problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/UCIDataScienceInitiative/IntroToJulia/issues/25#issuecomment-389758020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVXkD2Phzi6w0F1L8W6iuOm8zS4bUvbvks5tzRdJgaJpZM4T8o6q
.


remove deprecated import path

https://github.com/emberjs/ember.js/pull/17926#issuecomment-484987305

thank you @rwjblue, accepted all those changes

@bekzod - I've pushed a few changes:

added a failing test that attempts to confirm the babel-plugin-ember-modules-api-polyfill doesn't transpile import { deprecate } from '@ember/application/deprecations' to globals (e.g. Ember.deprecate)
fix that failing test (by ensuring that deprecate from @ember/application/deprecations is not transformed by the modules polyfill
added a test confirming that import { deprecate } from '@ember/application/deprecations is transpiled properly in debug builds

Should be good to land once CI is finished...


HP manufacturer grayed out and not checked, Microsoft grayed out and checked.

This seems to happen every few days. When we open the tool, usually the Dell manufacturer selection is unchecked and grayed out. This is a bigger issue for us since we generally use Dell computers. Today, the Dell box was checked, but the HP was unchecked and grayed out. Of course today we started ordering some HPs!
In the past I've fixed it by backing up the settings and re-installing. Today, that doesn't work. No matter what I try, HP is grayed out and unselected. Are there other things I can try to get it to work?

Try changing the Windows OS selection. I believe that some of the options for manufacturer change depending on what OS is selected for windows 10 vs a windows 10 build number.

That was it... I should have tried that first. I was able to get around it by editing the settings file and changing the HP option from false to true, but this makes more sense!


Styled Desktop view

Desktop view successfully styled.
Individual svgs replaced with combined png set as background image.
This branch made use of :

Media Query
Flex styling
To restyle the mobile version into the complete desktop view

Hello @i-max-xi  I can see that the readme was not updated

STATUS: CHANGES REQUIRED 🟡
Hi @i-max-xi  :computer:,
:thumbsup: This is good to make it this far, your project is really nice, congratulations on the good work you have done so far.
Keep on coding, good job so far! :clap:
Sadly, there are some issues that you still need to work on to go to the next project

Required Changes  :recycle:

[ ] As stated by the previous two reviewers, I strongly suggest you to use this Microverse template in your readme.md and customize it with the information pertaining to your project. Because currently, readme in your repository has plain text without headings and  screenshots. Here is an example of a readme file https://github.com/yersel500/portfolio.

If you do  not know how to customise the readme file, please click on the link, then on readme.md file, then row and copy all the content for customization:

Step 1
Step 2

!

Optional suggestions

[ ] OPTIONAL : Did you know that on Figma you are provided with buttons design 😉? I kindly suggest you to add hover effect as provided in Figma:

_Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.

Cheers and Happy coding! :clap: :clap: :clap:
Code review by Shoira
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Add first version of SimulateBlock

SimulateBlock is CLaSH-specific block that is a counterpart to the simulate
function in Clash. Expects a function that turns a Signal of monotonically
increasing numbers into a Signal of representable result values.
While signals are infinite, SimulateBlock only shows the first N
iterations/steps.

It's basically a poor man's (stepping) debugger.

Code looks fine except for some trivial things.
However I do not understand the choice for an integerproperty with a listener, while recalculation could also be done in a setter for the iteration count.

You're right, we don't need a property there.
Comments should be fixed now.


Loftsman reacting incorrectly to certain remote chart index urls

What happened?
With a manifest like
...
spec:
  sources:
    charts:
    - type: repo
      name: chartmuseum
      location: https://chartmuseum.github.io/charts
...
charts:
- name: chartmuseum
  source: chartmuseum
  version: 3.1.0
...

Loftsman ends up constructing the incorrectly url for the chart:
Error: failed to download "https://chartmuseum.github.io/charts/https:/github.com/chartmuseum/charts/releases/download/chartmuseum-3.1.0/chartmuseum-3.1.0.tgz"

We detect whether or not the root helm repo url is included in the chart index record and respond correctly, but in the case of it being a pointer to a totally different place, this is what happens.
What did you expect to happen?
For the correct URL to be found for pulling the chart
How to reproduce the issue (as minimally and precisely as possible):
Using a manifest like the above and running a ship
Anything else worth sharing:
N/A

fix deployed with 1.1.1


Request

Please add Koldunic Sorcery.

Should now be (un)live on the site. Changes are included in #159


The given key was not present in the dictionary.

Hello,
I'm trying to train my custom model with the local Object detection scenario. everything go fine until Channel finished that crash with the following exception
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary2.get_Item(TKey key)    at Microsoft.ML.TorchSharp.AutoFormerV2.ObjectDetectionMetrics.ImageIoU(List1 objectLabel, List1 annotation, Dictionary2 iouDic, Dictionary2 groundTruthBoxes)    at Microsoft.ML.TorchSharp.AutoFormerV2.ObjectDetectionMetrics.GenerateIOUDic(List1 annotations, List1 objectLabelList, Dictionary2 iouDic, Dictionary`2 groundTruthBoxes)
at Microsoft.ML.TorchSharp.AutoFormerV2.ObjectDetectionMetrics.MeasureMetrics(IDataView dataView, Column labelCol, Column actualBoundingBoxColumn, Column predictedLabelCol, Column predictedBoundingBoxColumn, Column scoreCol)
at Microsoft.ML.ModelBuilder.AutoMLService.LocalObjectDetectionMetricManager.Evaluate(MLContext context, IDataView eval) in //src/Microsoft.ML.ModelBuilder.AutoMLService/MetricManagers/LocalObjectDetectionMetricManager.cs:line 24
at Microsoft.ML.AutoML.SweepablePipelineRunner.Run(TrialSettings settings)
at Microsoft.ML.AutoML.SweepablePipelineRunner.RunAsync(TrialSettings settings, CancellationToken ct)
at Microsoft.ML.AutoML.AutoMLExperiment.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ML.ModelBuilder.AutoMLService.LocalObjectDetectionExperiment.d__13.MoveNext() in //src/Microsoft.ML.ModelBuilder.AutoMLService/Experiments/LocalObjectDetectionExperiment.cs:line 133
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ML.ModelBuilder.AutoMLEngine.d__21.MoveNext() in /_/src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 169

@aboudoux Would you mind sharing your .mbconfig with us.

I have the same problem, my mbconfig
LordsMobile.zip

I have the same problem, my mbconfig
{
  "Scenario": "ObjectDetection",
  "DataSource": {
    "Version": 0,
    "Type": "Coco",
    "FilePath": "C:\\Users\\Nekiplay\\Desktop\\CocoAnatator\\coco-annotator\\datasets\\LordsMobile\\.exports\\coco-1689492909.3708026.json"
  },
  "Environment": {
    "Type": "LocalCPU",
    "Version": 1
  },
  "Type": "TrainingConfig",
  "Version": 4,
  "TrainingOption": {
    "Version": 0,
    "Type": "ObjectDetectionTrainingOption",
    "TrainingTime":<PHONE_NUMBER>,
    "Epoch": 5,
    "ScoreThreshold": 0.35,
    "IOUThreshold": 0.5,
    "ValidationOption": {
      "Version": 0,
      "Type": "TrainValidateSplitValidationOption",
      "SplitRatio": 0.2
    },
    "ResizeOption": {
      "Version": 0,
      "Type": "Resize",
      "Width": 800,
      "Height": 600
    }
  }
}

Hello, I'm trying to train my custom model with the local Object detection scenario. everything go fine until Channel finished that crash with the following exception
at System.ThrowHelper.ThrowKeyNotFoundException() at System.Collections.Generic.Dictionary2.get_Item(TKey key) at Microsoft.ML.TorchSharp.AutoFormerV2.ObjectDetectionMetrics.ImageIoU(List1 objectLabel, List1 annotation, Dictionary2 iouDic, Dictionary2 groundTruthBoxes) at Microsoft.ML.TorchSharp.AutoFormerV2.ObjectDetectionMetrics.GenerateIOUDic(List1 annotations, List1 objectLabelList, Dictionary2 iouDic, Dictionary`2 groundTruthBoxes) at Microsoft.ML.TorchSharp.AutoFormerV2.ObjectDetectionMetrics.MeasureMetrics(IDataView dataView, Column labelCol, Column actualBoundingBoxColumn, Column predictedLabelCol, Column predictedBoundingBoxColumn, Column scoreCol) at Microsoft.ML.ModelBuilder.AutoMLService.LocalObjectDetectionMetricManager.Evaluate(MLContext context, IDataView eval) in //src/Microsoft.ML.ModelBuilder.AutoMLService/MetricManagers/LocalObjectDetectionMetricManager.cs:line 24 at Microsoft.ML.AutoML.SweepablePipelineRunner.Run(TrialSettings settings) at Microsoft.ML.AutoML.SweepablePipelineRunner.RunAsync(TrialSettings settings, CancellationToken ct) at Microsoft.ML.AutoML.AutoMLExperiment.d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ML.ModelBuilder.AutoMLService.LocalObjectDetectionExperiment.d__13.MoveNext() in //src/Microsoft.ML.ModelBuilder.AutoMLService/Experiments/LocalObjectDetectionExperiment.cs:line 133 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ML.ModelBuilder.AutoMLEngine.d__21.MoveNext() in /_/src/Microsoft.ML.ModelBuilder.AutoMLService/AutoMLEngineService/AutoMLEngine.cs:line 169

I found the cause of the problem, don't export a model with unlabeled categories

@aboudoux @Nekiplay May I ask how many different kind of labels does your dataset have? I'm suspecting that this issue is causes because some labels are classified into test dataset and not in train dataset during train-validation split.

@aboudoux @Nekiplay May I ask how many different kind of labels does your dataset have? I'm suspecting that this issue is causes because some labels are classified into test dataset and not in train dataset during train-validation split.
I also have trouble in reproducing this issue on all testing dataset I have. Would be appreciated if anyone can guide me through how to reproducing this bug.

There was one label for 1 category and 0 for the other after I removed their exports model training went fine


[Question]How to purge cache obejects by a url pattern?

The answer of ChatGPT:
traffic_ctl cacheurl flush http://example.com/abc/*
traffic_ctl cacheurl flush  ^https?://([^:/?])(:[0-9])?(/[0-9a-zA-Z]{32}
[myhost@localhost ~]$ traffic_ctl cacheurl flush http://example.com/abc/*
Error: No subcommand found for traffic_ctl
It does not work.

If you want to delete single object (not pattern):
https://docs.trafficserver.apache.org/en/latest/admin-guide/storage/index.en.html#removing-an-object-from-the-cache
If you want to use regex:
https://docs.trafficserver.apache.org/en/latest/admin-guide/storage/index.en.html#inspecting-the-cache


To get proxy host domain set in the mobile devices

Problem Description
I am trying to build a forward proxy server through which traffic from mobile devices can be captured and modified. My proxy server lies in an EC2 instance which is pointed by a wildcard domain, let's say *.myproxy.com.
I am setting different proxy hosts  such as abc.myproxy.com, xyz.myproxy.com, etc in different mobile devices in their wifi configurations.  I am getting network traffic of the devices on my forward proxy but am unable to distinguish the requests according to the proxy host (abc.myproxy.com or xyz.myproxy.com).
If a mobile device is hitting example.com from the browser then the request header's host contains example.com and their is no special parameter in the request object through which I can get the proxy host address set in that mobile device.
Proposal
I want to distinguish the network traffic of different devices according to the proxy host (abc.myproxy.com or xyz.myproxy.com) set in those devices. Is it possible to get the proxy host address set in the devices at my proxy server using MITM proxy?

For explicit HTTP proxying (https://docs.mitmproxy.org/stable/concepts-howmitmproxyworks/#explicit-http) this is not really possible. For explicit HTTPS you may be lucky and the client may be sending a Host header in the initial CONNECT? Those are available in the http_connect hook, see https://github.com/mitmproxy/mitmproxy/blob/10.1.1/mitmproxy/addons/proxyauth.py#L69-L72 for an example of how you can persist state.
Alternatively, can you just equip your clients with unique proxy authentication credentials?


Expose AuthMetadataProcessor to Python?

What version of gRPC and what language are you using?
gRPC 1.18.0, Python
What operating system (Linux, Windows,...) and version?
Linux
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.6
What did you do?
We'd like to implement a custom authentication method in Python. While we can implement AuthMetadataPlugin on the client side, there is not a convenient API on the server side. gRPC C++/Core have AuthMetadataProcessor, but this is not exposed to gRPC.
Also see https://github.com/grpc/proposal/pull/101.
What did you expect to see?
Either a well-supported way to pass data from an interceptor to an RPC method handler, or a way to hook into ServicerContext.peer_identities such as via AuthMetadataProcessor (presumably).
What did you see instead?
We instead created an interceptor, but there is not an obvious way to pass data from an interceptor to the RPC handler. It could be done in a decorator instead, but then it is easy to forget to annotate methods (which should be secure-by-default). Alternatively, the interceptor can wrap the RpcMethodHandler and then wrap ServicerContext, but this is a lot of boilerplate.
Anything else we should know about your project / environment?

This use case is currently difficult out of the box. It has been called out in the past as a potential application of full-featured server-side interceptors, which are unfortunately not yet available in gRPC Python.
As you mentioned, decorators can be used to supply data to the application handlers. In order to solve the secure-by-default problem, you could try a metaclass to decorate the methods automatically.

Thanks for the follow up! I do see the difficulties in the full-featured server interceptor API, and I have wished for the same level of control as in Java. For us, wrapping ServicerContext is an OK solution, as then it doesn't require modifying servicer code (whether with decorators or with a metaclass).
Is there a reason why the processor API won't or can't be supported, though? To me, it feels odd to treat in-tree auth implementations (using ServerCredentials) differently than out-of-tree ones (using a hypothetical interceptor). I suppose Java has the same asymmetry, but it seems C-core and C++ don't.
If it's mostly an implementation effort issue, we have been interested in contributing upstream to unblock these use cases for us.

PRs are always welcome! Thank you for volunteering. :smile:
After a little more thought, barring your concern about different auth configurations for different handler methods, is there any reason that the ServerCredentials interface doesn't meet your needs? It seems like if you implement that and subclass grpc_server_credentials, you should have a full python implementation.
Am I missing some of the complexity here?

Yes, ServerCredentials is exactly the interface we'd like to use! But there's no way to implement it within Python, as it's an opaque wrapper for a C struct. If we bind auth_metadata_processor, that would give an extension point that automatically exposes the right data in ServicerContext. I think the main complexity is in calling back into Python from the C callback.

I think this is possible using the ServerCredentials interface. Here's an implementation sketch.

Implement GSSAPI Support in Core

Subclass grpc_server_credentials just like ALTS and SSL have done.
Write a factory function for your new type returning grpc_server_credentials*
Add the factory function to include/grpc/grpc_security.h like grpc_ssl_server_create_with_options. This will add GSSAPI support to the core surface API, making it available to all wrapped languages, including Python.

Implement GSSAPI Support in Cython

Pull the new core functions into the cython layer by adding their signatures to src/python/grpcio/grpc/_cython/_cygrpc/grpc.pxi
Wrap the new core functions with Cython, resulting in a Python interface.

Implement GSSAPI Support in Python

Add a GSSAPI factory function returning an instance of ServerCredentials to the grpcio public API

I'm still not clear on what exactly you need access to from inside of the service handler. Could you provide a code snippet of what you think a service handler integrating with GSSAPI might look like? If the issue is just calling back into python from core, you can probably solve that with a thread hop.

Sorry, I think I'm mixing up two things here!
For GSSAPI specifically, I'm waiting on the proposal…I'm glad to hear that implementation should be relatively straightforward, though.
However, that proposal has been waiting for a few months now, so I'm exploring an alternate mechanism - namely, the AuthMetadataProcessor API, which would allow us to implement GSSAPI (or any other auth mechanism) without explicit gRPC support for it. This would also let us implement something that exposes the ServerCredentials interface in pure Python. The corresponding client side API, AuthMetadataPlugin, is already exposed in gRPC/Python. So I'm wondering if there's interest in also exposing AuthMetadataProcessor to gRPC/Python.
The reason why I'd like to do this over using ServerInterceptor is to expose a uniform API to servicer implementations - namely, that in Python, they should still be able to access the authenticated user identity via the ServicerContext. This is possible with ServerInterceptor, but requires some boilerplate, plus I'm not sure if it will remain compatible with future versions of gRPC. (Namely: the interceptor creates its own call handler that wraps the given ServicerContext in another object, overriding the peer_identity method and others, then calls the original handler.)

Hi @gnossen, just to follow up; does my previous comment make sense? Essentially, I'd like to bind auth_metadata_processor to Python so that we can implement auth mechanisms in Python, rather than in Core, but still have it look and feel like the other mechanisms in Core (which hook into peer_identities())


chore(windows): use rimraf instead of rm -Rf

This ensures npm run clean and npm run deploy runs on Windows

I sometimes forget about you Windows users ;). Thank you, will merge shortly.


First Travis integration

Problem
We need to link the current project to Travis, a tool for continuous integration
Solution
The file .travis.yml contains all the informations read by Travis. Some lines need to be deleted.
The file 'requirements.txt" contains all the needed packages that Travis need to download in order to make the application work.
Some minor tests were added

Awesome thank you!


Sample/Instructions to install NetService (NDIS Filter Driver) on Windows IoT Core

I know that there is a simple driver example to install a device driver on IoT Core. I cannot find any information about how to install a NetService type NDIS filter driver on IoT Core. I have trouble installing a NDIS Filter Driver on IoT Core, which is quite different from a general device driver.
My NDIS filter driver is basically from VS2015 NDIS filter driver sample. I already successfully put it on a target Win 10 Enterprise PC and can see its trace messages via VS2015 Kernel debugger window from Development computer.
I was also trying to put it on Windows IoT Core, and my hardware is Minnowboard Max. My steps are:

Follow https://ms-iot.github.io/content/en-US/win10/samples/DriverLab4.htm to just set up the provisioning on the target IoT Core from VS2015 on dev computer.
Follow https://channel9.msdn.com/Blogs/WinHEC/Creating-Universal-Drivers-with-WDK-10 to prepare for the mobile package (.cab file). Need to enter the required info in Package.pkg.xml file.
Build the x86 debug version.
Follow https://channel9.msdn.com/Blogs/WinHEC/Creating-Universal-Drivers-with-WDK-10 to deploy the .cab (online .cab package installation/update) on IoT Core from VS2015.

However, after connected via Kernel Debugger and set Kd_DEFAULT_MASK = 0xF,
cannot see any filter driver’s trace messages.
“devcon listclass NetService” returns empty.
Can anyone give me any instructions or hint? (This issue
is only for IoT Core. I successfully made it work on Windows 10 Enterprise already.)

NDIS filter drivers are not supported on IoT Core since there is no facility to register the filter with the network driver binding engine. The work to bring this scenario online is being evaluated but there are no definite plans yet.

ok. Thanks.


lib/container_server: Deprecate implicit hook directories

The previous approach was breaking when the default hook directory was missing:
crio[15828]: level=debug msg="reading hooks from /usr/share/containers/oci/hooks.d"
crio[15828]: level=debug msg="added hook /usr/share/containers/oci/hooks.d/test.json"
crio[15828]: level=debug msg="reading hooks from /etc/containers/oci/hooks.d"
crio[15828]: level=warning msg="failed to load hooks: open /etc/containers/oci/hooks.d: no such file or directory"

With this commit, I've deprecated the implicit defaults in favor of having users explicitly configure their hook directories (either via --hooks-dir on the command line or hooks_dir in their config file).  This is similar to the recent containers/libpod@a4b483c8 (containers/libpod#1920).
Different from the libpod implementation is that CRI-O is only loading the hook manager at this point, so we don't know if the hook directories actually have hooks that will apply to future container (or even if they have hooks at all).  I've just warned about their existence if the directories exist, to help poke folks into migration to explicitly-configured directories.
Another difference is that we get a single manager, so we need to ensure the default directories will work before feeding them in.  I'm now stat'ing them to check, which will address #1942.  But that's racy, since the directory could exist at stat time but be gone by the time the manager tries to load it.  I'm ok with the race, because that entire code path is deprecated anyway.
There's no race for the "user explicitly asked me to load /whatever and now it's gone" case.  Now that the default case is pre-checking, I've tightened 50d49939 (#1517)'s load-failure warning down to a fatal error.
I've dropped the trailing path from the old, hidden --hooks-dir-path, because I think dir(ectory) is already enough context for "we expect a path argument".  I consider this name change non-breaking because the old form was undocumented.  I've also changed hooks_dir_path to hooks_dir and changed it from a string to a []string.  That is potentially a breaking change because hooks_dir_path became publicly documented in 50539c31 (#1749).  But it's only been a few months since it landed, and making that setting public was only one of a few changes it had made.  So I'm reasonably optimistic that there aren't (m)any users explicitly setting hooks_dir_path yet, and haven't gone through the trouble of continuing to support the old setting.
Fixes #1942

All green :)

/test all

LGTM

/approve

/lgtm


Remove pyvista dependency

PyVista should not be a required dependency. Moving it to optional.

Superseded by #17.


Tooling for ES6 modules, clean up

Cleaned up and deleted files scripts from bin, package.json, Gruntfile.js, and docs/source.
Then I got a UMD bundle compiled that uses ES6. I'm doing this via Grunt with rollup. Rollup is actually pretty cool. It basically does both the "take the ES6 imports and put them in the file" and the "make my lib a universal module so anybody can use it in whatever system" parts of this process. It also has a babel plugin that lets you do ES6 things other than just imports.
So then I had to change a couple things so it would actually compile, but it is working now.

/cc @nikolaswise

Killer!


Correctly detect Raspberry Pi 3 on Kernel 4.9

Kernel 4.9 now correctly identifies the hardware for the Raspberry Pi 3 as "BCM2835", /proc/cpuinfo contains:
processor      : 0
model name     : ARMv7 Processor rev 4 (v7l)
BogoMIPS       : 38.40
Features       : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer        : 0x41
CPU architecture: 7
CPU variant    : 0x0
CPU part       : 0xd03
CPU revision   : 4
[...]
Hardware       : BCM2835
Revision       : a02082

Hi,
This also apply to RPI Model B on kernel 4.9.*
~-> cat /proc/cpuinfo
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 896.40
Features	: half thumb fastmult vfp edsp java tls
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2835
Revision	: 000d

It would be great to get this merged so we can have Pi 3 support back!
In the meantime I have a fork at https://github.com/lukepalmer/embd for this purpose that others can use. This was needed because go get cannot import from a branch. I hope to delete the fork when this is merged.


I cannot create BlazorApp

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/create
Operating System: macos
Template "Blazor Server App" could not be created.
Failed to create template.
Details: Read-only file system : '/BlazorApp'

In what path are you trying to create the app? Did the error message contain any other details?

/cc @danroth27

Hi @RubyRahman. I'm sorry to hear you're hitting some issues creating you first Blazor app! To help us understand what's going wrong, could you please share with us the output of running the following two commands:
dotnet --version
dotnet new blazorserver


chore(deps): upgrade jenkins-x/jx3-pipeline-catalog to version 3.2.212

from: https://github.com/jenkins-x/jx

/test gsm

already upgraded to 3.2.213
/close


Few remarks about the README

The README.md is a good explanation work :)
Here my few comments:

We have permalinks for releases which could advantageously replace https://mirrors.dotsrc.org/kiwix/release/kiwix-tools/kiwix-tools_linux-x86_64-3.0.1.tar.gz by https://download.kiwix.org/release/kiwix-tools/kiwix-tools_linux-x86_64.tar.gz
I would recommend AFAP to recommend HTTPS over HTTP, so better https://download.kiwix.org/zim/wikipedia_en_all_novid.zim over https://download.kiwix.org/zim/wikipedia_en_all_novid.zim
novid links will be soon be replaced by maxi, it is just a naming convention, so https://download.kiwix.org/zim/wikipedia_en_all_maxi.zim
ZIM/Kiwix has fulltext to the contrary to what you have written.
Wikipedia categories will come soon, this is still in alpha.
About the list of ZIMs, Wikipedia list is a mirror of https://download.kiwix.org/zim/wikipedia/
All the links on download.kiwix.org have a BitTorrent file, just add .torrent to any URL
The publication is not regularly like you have noticed, but our goal is one time a month for most of them. Still working on it (We are searching for HW to support us).
I would recommend to use permalinks everywhere, to avoid having to update the READMEmd

[X] We have permalinks for releases which could advantageously replace https://mirrors.dotsrc.org/kiwix/release/kiwix-tools/kiwix-tools_linux-x86_64-3.0.1.tar.gz by https://download.kiwix.org/release/kiwix-tools/kiwix-tools_linux-x86_64.tar.gz
[X] I would recommend ASAP to recommend HTTPS over HTTP, so better https://download.kiwix.org/zim/wikipedia_en_all_novid.zim over https://download.kiwix.org/zim/wikipedia_en_all_novid.zim
[X] novid links will be soon be replaced by maxi, it is just a naming convention, so https://download.kiwix.org/zim/wikipedia_en_all_maxi.zim
[X] ZIM/Kiwix has fulltext to the contrary to what you have written.
[X] Wikipedia categories will come soon, this is still in alpha.
[X] About the list of ZIMs, Wikipedia list is a mirror of https://download.kiwix.org/zim/wikipedia/
[X] All the links on download.kiwix.org have a BitTorrent file, just add .torrent to any URL
The publication is not regularly like you have noticed, but our goal is one time a month for most of them. Still working on it (We are searching for HW to support us).
I would recommend to use permalinks everywhere, to avoid having to update the READMEmd

Finally got around to making most of these changes: https://github.com/pirate/wikipedia-mirror/commit/8cf535d9a496c3377e5626a46a206018a3921011
Let me know if you see anything else that should be changed, thanks!

@kelson42 how much hardware do you need BTW? I have a server with a gigabit connection, 24 cores, and ~10TB sitting mostly unused. I could give you a pretty big VM on it if you needed.

@pirate Thank you for the offer. This would be really useful. Our ZIMfarm is meanwhile pretty open and we have instructions to setup a worker in a few minutes https://farm.openzim.org/about. Let me know if this would be doable and we could discuss the last few details on Slack.


Inconsistent image size rendering in ImageSet web Visualiser

With the following JSON either the ImageSet imagesSize property should override the individual image size property or each image size should be honoured. The inconsistency is evident in the WPF visualiser as opposed to the web visualiser:
{     "type": "AdaptiveCard",     "body": [         {             "type": "ImageSet",             "images": [                 {                     "type": "Image",                     "size": "medium",                     "url": "http://adaptivecards.io/content/cats/1.png",                     "altText": ""                 },                 {                     "type": "Image",                     "url": "http://adaptivecards.io/content/cats/1.png",                     "altText": ""                 }             ],             "imageSize": "large"         }     ],     "version": {         "Major": 1,         "Minor": 0     } }

That's a really interesting find, I don't think we ever considered that scenario. @dclaux do you recall if we ever discussed this, or should we figure it out now?

I know there is no trace of it, but our decision was that ImageSet.imageSize applies to all images and the size property of the image objects is ignored.


Including more precise deployment timestamps in webhook

What would you like to be added:
Including in PipeCD webhook the timestamp when an existing resource was changed by piped.
Specifically, PipeCD gets the deployment status by reportDeploymentCompleted. At this time, a timestamp (CompletedAt) of when the status was obtained is included in PipeCD webhook.
We can know precisely the timing of the deployment by obtaining the timestamp when receiving the apply result of the manifests.
Why is this needed:
PipeCD includes the deployment start time in CreatedAt, overwrites the status (triggered:0 -> planned:1 -> success:4 / failed:5), updates UpdatedAt, and includes it in PipeCD webhook.
However, the UpdatedAt is not an actual deploy completed timestamp because it includes the time when   PipeCD C-Plane updated the database status.
I confirmed a time difference of about 20-40s between the timestamp notified by PipeCD webhook and the timestamp displayed in the WebUI logs.
e.g.
{
  "Type": 4,
  "Metadata": {
    "deployment":
      ...
      ...
      "status_reason": "The deployment has been planned",
      "created_at":<PHONE_NUMBER>,// 2023-08-04 11:13:08 // deploy started
      "updated_at":<PHONE_NUMBER> // 2023-08-04 11:13:29 // received a success status
    }
  }
}

deployment_created_at: 2023-08-04 11:13:08
deployment.updated_at:  2023-08-04 11:13:29 <- 20s ~ 40s faster than successfully log

The actual time of successful applied the manifest was 11:13:54.
It should be after 11:13:54 that the success status can be included in PipeCD webhook.

@GotoRen I'm Not sure if I missed something, but I think there is a miss here. Across the issue description, the updated_at timestamp is for status reason "status_reason": "The deployment has been planned", while the stage log highlighted in the picture shows a message that it's manifests applied.
I think those timestamps are different because they're totally different events at first, aren't they?

@khanhtc1202
PipeCD Webhook seems to include the message "The deployment has been planned" in the status_reason,
even in the notification of a successful deployment (application of manifest).
I have prepared a webhook receiving server and verified it multiple times!
The data and image shown in the code block are the same event.
Indeed, when Type: 4 (DEPLOYMENT_SUCEEDED), "The deployment has been planned" is included in the status_reason.
I think the message "The deployment was completed successfully" should be included. Ref
Is it possible that PipeCD is including the wrong message in the status_reason?
[FYI]: the messages included in each event.

Type
Metadata.deployment.status_reason

0
The deployment is waiting to be planned

1
The deployment is waiting to be planned

4
The deployment has been planned


enquiry about the mail sending feature

dear @athyuttamre
this is a great chrome extension which helps me organize and manage everlasting pending tabs.
thanks.
i am interested to see the mail sending function.
are you using some free smtp gateway? or some paid one? if so, will later this extension need charge some days later.

Hi there, at the moment there isn't a mail sending feature in Tab Snooze. Perhaps you're confusing this with the other tabsnooze (www.tabsnooze.com)?

Thsi is your tab-snooze? http://athyuttamreddy.com/tab-snooze/
and...
this is the other one?? http://www.tabsnooze.com/

Yup, unfortunately. I used the name in the beginning, and it seems there was an unfortunate coincidence. You're right though, perhaps I should.


fix: add date to title

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


⚠ Secret Website 3 has degraded performance

In 2fb1870, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2979 ms

Resolved: Secret Website 3 performance has improved in fd1c394.


Added \impliedby and \thinspace

Adds \thinspace, which is simply an alias of \,, and the \impliedby arrow.

Could you rebased this an move the definition for \impliedby so that it comes after \implies?

We'll tackle this once we have macros.


Bring back script encryption in export preset

What started as curiosity ended up as an actual implementation. 😁
Retrieved working implementation from 2.1 branch and adapted to
existing export preset system.

Added Script tab in export preset to export script as raw text,
compiled, or encrypted (same as in 2.1). The script encryption key is
visually validated. The script export mode and the key is saved per
per preset in `export_presets.cfg`, so it makes sense to ignore this
file in version control system.

Each custom exporting procedure can retrieve an export preset set
during project exporting. Refactored project export dialog a bit to
allow easier code comprehension.

Tested in both debug and release modes, with text, compiled, and encrypted modes respectively. If wrong key is provided during export, the exported project will crash, which is expected:
ERROR: open_and_parse: Condition ' String::md5(md5.digest) != String::md5(md5d) ' is true. returned: ERR_FILE_CORRUPT
      At: core/io/file_access_encrypted.cpp:103

The scripts are exported as .gde as before. The default script export mode is still Compiled, not Text.
I'll also write documentation for this in godot-docs.
Fixes #24121.

Also, Merry Christmas! 🎄

wow... glad it's back thank you

As been discussed in linked issues, perhaps we should rename script export mode from Compiled to Binary to avoid confusion, and leave Compiled for an actual implementation.

Thanks!


Feature Request: Enable package overwrites

Describe the solution you'd like
An option to replace packages with matching version number would be nice. Right now, even with HardDelete set, I still get 409 - conflict when replacing the package. I read about the whole left-pad thing, and I understand it, but our organization's needs are different. It would help if the UI allowed for proper package management, but I understand it is in early stages, and it is looking GREAT!
We are currently using phpNuget, which supports deletion and replacement, but we are seeing very slow activity in the development and are looking for other options.

Hello, this should be addressed by https://github.com/loic-sharma/BaGet/pull/208. For more information, see this documentation: https://loic-sharma.github.io/BaGet/configuration/#enabling-package-overwrites
Let me know what you think!


Catch errors thrown in ensure block

Closes #78
If an error ever occurrs in an ensure block, then that is a serious problem. We should inform the user that this is not good by printing a huge nasty warning to the console.
However, if such a situation does occur, at least it should not leave the process tree in an inconsistent state. Other exit hooks should still run, and other processes should still shut down. Currently if such an error does occur, it will blow the stack, and cause finalization to stop
abrubtly. This is very much not good.
Here we're rescuing any such errors, printing them to the console, but crucially we are NOT re-raising them. This allows us to proceed with finalization, which will leave the process tree in a more consistent state.
It's worth noting though that such a situation really is very undesirable. The Rust language does a hard abort of the process with an error exit code if a destructor panics, we cannot do something similar in effection, since we want to run in browsers, and browsers cannot hard-exit.

A preview package of this pull request has been released to NPM with the tag catch-ensure-errors.
You can try it out by running the following command:
$ npm install effection@catch-ensure-errors

or by updating your package.json to:
{
  "effection": "catch-ensure-errors"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 6ca7c79b292540d811f4cfacd2af83a6a8be09f3

A preview package of this pull request has been released to NPM with the tag catch-ensure-errors.
You can try it out by running the following command:
$ npm install effection@catch-ensure-errors

or by updating your package.json to:
{
  "effection": "catch-ensure-errors"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 9dc53336b59443bcf7a9e41540c9bc5d27aca461

A preview package of this pull request has been released to NPM with the tag catch-ensure-errors.
You can try it out by running the following command:
$ npm install effection@catch-ensure-errors

or by updating your package.json to:
{
  "effection": "catch-ensure-errors"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 5867178c61724fff8dcc02ebd439058f675db90f

A preview package of this pull request has been released to NPM with the tag catch-ensure-errors.
You can try it out by running the following command:
$ npm install effection@catch-ensure-errors

or by updating your package.json to:
{
  "effection": "catch-ensure-errors"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 8ec127f427554f9d063064e4817eec50abba295f

@cowboyd not sure why the type tests are failing. It looks unrelated to this PR though.

@cowboyd not sure why the type tests are failing. It looks unrelated to this PR though.

I'm guessing that it's because we have our TS config pointed to esnext which is a moving target..... which moved. Maybe if we peg it to es2019 or some fixed target?

A preview package of this pull request has been released to NPM with the tag catch-ensure-errors.
You can try it out by running the following command:
$ npm install effection@catch-ensure-errors

or by updating your package.json to:
{
  "effection": "catch-ensure-errors"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 1ec6b7a10226e7ceb5e6059653e3ad6c724c6954

A preview package of this pull request has been released to NPM with the tag catch-ensure-errors.
You can try it out by running the following command:
$ npm install effection@catch-ensure-errors

or by updating your package.json to:
{
  "effection": "catch-ensure-errors"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 1ab9ce5bab504af111e6284d132934bb3ba9578d

:shipit:


gh-pages: 0.13.1 still marked as SNAPSHOT

This is related to the gh-pages branch.
https://github.com/angular-ui/bootstrap/commit/ea1c2a04849c88713f4ad05b21461a5b5d7d60d9 removed -SNAPSHOT from the filenames for 0.13.1, but the version headers in the actual files still have it (e.g. Version: 0.13.1-SNAPSHOT - 2015-07-23).

Fixed via 7af3115b0aec348b0871425cd137b90aacd38ca7

Looks like https://github.com/angular-ui/bootstrap/blob/gh-pages/ui-bootstrap-0.13.1.js and https://github.com/angular-ui/bootstrap/blob/gh-pages/ui-bootstrap-0.13.1.min.js still have -SNAPSHOT in them.

Hm weird - just removed them via b1218f73f1399410bbddd1ee383a6feb634c336b

Looks good now. Thanks!


Towards FilterMonadic and Map

Towards #288
Towards #170

@ruslansennov I've made some slight modifications - I hope this does not cause merge-conflicts at your fork. I'm now jumping on the 'collection' train. First I setup the FilterMonadic stuff, then Set interface, then SortedSet based on Red-Back-Tree...
HashSet should be relatively easy because it is backed on a HashMap, right?

@danieldietrich I believe any Set is a scecial case of Map :)

@ruslansennov Technically yes, and Tree is a List of Lists :)


rubyPackages.pwntools: init at 1.2.1

Description of changes

The pwntools-ruby is a collection of libraries who want to use the pwntools with Ruby, not Python.

The first commit, update, is a result after I run ./maintainers/scripts/update-ruby-packages
The second commit, init at 1.2.1, is a result after I add a single line in Gemfile and run the update-ruby-packages again.

At the beginning, I simply added pwntools gem in the default Gemfile and run the update script. but it updates the other gems unexpectedly. so I thought splitting it into two commits would be better.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

       Known issues:
        - This Ruby release has reached its end of life. See https://www.ruby-lang.org/en/downloads/branches/.

       You can install it anyway by allowing this package, using the
       following methods:

       a) To temporarily allow all insecure packages, you can use an environment
          variable for a single invocation of the nix tools:

            $ export NIXPKGS_ALLOW_INSECURE=1

        Note: For `nix shell`, `nix build`, `nix develop` or any other Nix 2.4+
        (Flake) command, `--impure` must be passed in order to read this
        environment variable.

       b) for `nixos-rebuild` you can add ‘ruby-2.7.8’ to
          `nixpkgs.config.permittedInsecurePackages` in the configuration.nix,
          like so:

            {
              nixpkgs.config.permittedInsecurePackages = [
                "ruby-2.7.8"
              ];
            }

       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
          ‘ruby-2.7.8’ to `permittedInsecurePackages` in
          ~/.config/nixpkgs/config.nix, like so:

            {
              permittedInsecurePackages = [
                "ruby-2.7.8"
              ];
            }

NIXPKGS_ALLOW_INSECURE=1 nix-shell -I nixpkgs=. -p "ruby_2_7.withPackages (ps: with ps; [pwntools])" --pure works. I can get a shell of it.

Thank you so much! @matthiasbeyer @marsam


Support integTests for OpenSearch core in OpenSearch integ-test workflow

@setiah can you fill this task in more? If there is work needed in the OpenSearch-Build please create tasks with acceptance criteria that can be worked on to so we can drive this to resolution.


Put constructor initializer on new line

closes #700

Did you link the wrong bug? I don't see how that's related to this change at all. 🤷

Ah yeah, I updated the commit but missed updating the PR.


Don't sort by uppercase first?

Is there a setting to not sort imports that start with an uppercase letter first?
Input
from foo import export, Mock

Output
from foo import Mock, export

I see there is
--case-sensitive      Tells isort to include casing when sorting module names

But is there something for the imports?

Same here: isort always include casing when sorting :(
I try to add case_sensitive=false in my .isort.cfg but doesn't change the misconduct.


[Backport 1.7.latest] Test ddtrace dependency range (#733)

Backport #733

This is only needed for older versions.


Store input XML as an attribute or the Dataset class with standardised encoding

This relates to what is contained within iati.core.Dataset().xml_str
Suggestion from @hayfield, based on review comments:

(It) would simplify use if we standardised encoding within a Dataset object ... assuming one of the utf-xy encodings can fully represent everything.

Following this suggestion, I had a look at this, and have concluded that this might not be that straightforward, as to decode a string – to say utf-8 – you need to know what encoding it is in.
An alternative might be to use an @property decorator to return the XML string as the output of etree.tostring, which would let lxml deal with all the encoding business.

Encoding detection is done in 0e6b5f35ecac5935a39ee9dde7f8b10483e4044d


Add capability to get a screenshot information in the test code

What is your Test Scenario?
I would like to implement tests which are comparing screenshots of the page
What are you suggesting?
Please enable the takeScreenshot-Command to return the binary data of the image directly without writing it into a file
What alternatives have you considered?
Currently, I need to manually load the image into memory again after testcafe has put it into the location specified by the command
Additional context
Hi guys, for tests which are comparing screenshots with a diffing-tool like rembrand, it would be useful to get the binary data representing the screenshot directly instead of first writing it into a file. I hope this wouldnt be a big change, but since I dont know how exactly you are taking the screenshot, the required change might be bigger than expected. Since it is quite easy to read the file into memory afterwards a workaround is present, so there is no huge issue to overcome.

Hi @ferencbeutel4711
Thank you for your suggestion. It can be useful in the screenshot comparison scenario.
We have a development plan - https://devexpress.github.io/testcafe/roadmap. Though it can be difficult to make time for that. If the proposed feature is very important for you, a PR will be highly appreciated.


Default verb treated as a value.

This was seen on version 2.8.0 targeting .NET Core 3.1 / 5.
Minimum code sample:
void Main()
{
	var parser = new Parser();
	var result = parser.ParseArguments<CopyArguments>(new[] { "copy", @"A:\", @"C:\", });
	result
		.WithParsed<CopyArguments>(a =>
		{
			Console.WriteLine(a.SourcePath);
			Console.WriteLine(a.DestinationPath);
		});
}

[Verb("copy", isDefault: true)]
class CopyArguments
{
	[Value(0, MetaName = "source", Required = true)]
	public string? SourcePath { get; set; }

	[Value(1, MetaName = "destination", Required = true)]
	public string? DestinationPath { get; set; }
}

This prints "copy" for SourcePath and "A:\" for DestinationPath.
At this point in development I only have one verb (more verbs are planned), and that verb is/will be the default one.

Yeah, it's a gotcha when beginning to design the CLI and starting with one verb.
The simple ParseArguments<T> method with a single generic type parameter does not support verb scenarios.
Verb scenarios are supported by either the generic ParseArgument<T1, ...> methods with two or more generic type parameters, or the non-generic ParseArguments(IEnumerable<string> args, params Type[] types) method.
Thus, you could workaround this transient issue by using a second dummy generic type parameter as a placeholder until you get around implementing your other verb(s):
var result = parser.ParseArguments<CopyArguments, object>(new[] { "copy", @"A:\", @"C:\", });

Note also how the documentation for each of the ParseArgument<T1, ...> methods with two or more generic type parameters explicitly mentions that these are for "verb commands scenarios" (https://github.com/commandlineparser/commandline/wiki/T_CommandLine_Parser), whereas the documentation for ParseArgument<T> does not mention verb command scenarios.


Audio playing twice on iOS

Bug
On iOS, sometimes the audio plays twice and produces an echo.  The issue is present with both local files and remote URL video sources.

Platform

iOS

Environment info
React native info output:
System:
    OS: macOS Mojave 10.14.4
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Memory: 1.78 GB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 11.12.0 - ~/.nvm/versions/node/v11.12.0/bin/node
    Yarn: 1.16.0 - ~/.npm-global/bin/yarn
    npm: 6.7.0 - ~/.nvm/versions/node/v11.12.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 23, 24, 25, 26, 27, 28
      Build Tools: 27.0.3, 28.0.3
      System Images: android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
  IDEs:
    Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.5 => 0.60.5

Library version: 5.0.2
Steps To Reproduce

Record a video with react-native-camera, select one from the picker with react-native-image-crop-picker, or find a remote video URL.
Mount the Video component and play the resource.
...

Expected behaviour

The audio plays once in sync with the video.

Reproducible sample code
<Video
            ref={(ref) => {
              this.player = ref
            }}
            source={{ uri: src }}
            id={id}
            repeat={this.props.id === 'preview' || Platform.OS === 'ios'}
            onProgress={this.handleProgress}
            progressUpdateInterval={100}
            onLoadStart={() => this.setState({ loading: true })}
            onLoad={this.handleLoad}
            onEnd={this.handleEnd}
            muted={this.props.meta.muteStatus}
            paused={!this.state.play}
/>

We found the issue on our end. We're using react-navigation and were rendering an additional instance of the same video on a screen that was mounted on the stack, so there were two mounted Video components playing at the same time.


Proposal: add new severity[].source field

Proposal to add a new optional string field on a severity entry that represents "who" scored or where that scoring came from.
Different entities score vulnerabilities differently and sometimes there are different sources that don't agree on scoring for the same vulnerability, this would allow the schema to support both instead of having to make a decision on which one is best.

Hi,
So sorry for missing this issue earlier!
As OSV is a distributed database, where database owners publish their own vulnerability records, the implication is that all values in that record (including severity values) come from the database itself.
For example, if a GHSA advisory has a severity field, then the implication is that this severity comes from GitHub (or at least, GitHub endorses the severity if it came from somewhere else).

Hi @oliverchang,
Just saw this issue and I think it would be nice to have a source field. Users/customers might be interested in seeing more than one rating in a single view. Therefore if Ubuntu wanted to have two different CVSS scores published in OSV, it would be unclear why they differ or who calculated/published it (for example one from NVD, one from Intel). It is more than just endorsing, it is also about users wanting this single view of all the different ratings.

I agree with @dodys here, it's not uncommon for distributions to provide their own CVSS and there is value in specifying who did the severity analysis. When looking at distro-specific CVEs, I don't know if the CVSS score listed there is specific to the distribution or it comes from the general CVE without having to consult both entries.
Talking about CVE entries coming from NVD, their CVSS scores can be both their own ones as well as others, like
CVE-2024-49394. In this particular case, the analysis actually comes from Red Hat and there is no way to identify this from OSV data.
Same happens with most NVD CVEs coming from a GitHub advisory, in which case the CVSS comes directly from GitHub.

Circling back to the point @oliverchang made in https://github.com/ossf/osv-schema/issues/248#issuecomment-2347745099 and attempting to restate it differently:
For a given OSV record with a given identifier prefix, it has a singular home database. That home database is implicitly the source of the entire record, including the severity scores in it. While OSV.dev is loosely analogous to the NVD in terms of being a downstream aggregator of OSV records, it's not aggregating multiple records into a single record, nor is it adding any subjectively determined data from other sources. In other words, the only way any severity values will appear in an OSV record if they are included by the record's publisher. Is the desire here for a record publisher to include multiple severity values and differentiate which ones are first-party versus third-party?
It may be helpful for the folks interested in this functionality to drop in some worked examples (take an existing OSV record and demonstrate how this functionality would work) to clarify?

Is the desire here for a record publisher to include multiple severity values and differentiate which ones are first-party versus third-party?

Yes, I think fundamentally that's the case, for example to list NVD CVSS and specific publisher CVSS.
Also, in some cases, to clarify who produced the information. The publisher chooses what information to publish, but this still does not clarify if the information was produced by the publisher or not. As per severity, I feel like it is relevant if the source of it is the publisher itself or if it was inherited from somewhere else. NVD takes a similar approach as they clarify where the CVSS came from.
As per an example, coming back to CVE-2024-49394, NVD shows this CVSS score was generated by "Red Hat, Inc". This "source" field will clarify this information was not produced by the publisher, but still wanted it to be showed.
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "source": "Red Hat, Inc."
    }

as per the multiple cases, given that Debian packages are listed there, I'll use that as the other party for the example. If Debian considers the complexity high:
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "source": "Red Hat, Inc."
    },
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "source": "Debian"
    }


Private Listing - Remove pending more testing

Comment out the Private Listing option on the Create/Edit page and anywhere else it currently appears.
We do not want to deploy this feature without more testing.

Passed on Latest.


Add deploy_chef support for RHEL 6

Currently for rpm based distros RHEL 5 repository is used

what do you think about something like this for solo.py (i'm not that experienced with python/git etc)
diff --git a/littlechef/solo.py b/littlechef/solo.py
index 977231b..fc21d50 100644
--- a/littlechef/solo.py
+++ b/littlechef/solo.py
@@ -14,6 +14,7 @@

"""Chef Solo deployment"""
import os
+import re
from fabric.api import *
from fabric import colors
@@ -91,7 +92,6 @@ def configure(current_node=None):
with hide('stdout'):
sudo('chown root:root {0}'.format('/etc/chef/solo.rb'))

def check_distro():
"""Check that the given distro is supported and return the distro type"""
debian_distros = ['wheezy', 'squeeze', 'lenny']
@@ -257,22 +257,43 @@ def _add_rpm_repos():
 """
 with show('running'):

   # Install the EPEL Yum Repository.

   with settings(hide('warnings', 'running'), warn_only=True):

       repo_url = "http://download.fedora.redhat.com"

       repo_path = "/pub/epel/5/i386/epel-release-5-4.noarch.rpm"

       output = sudo('rpm -Uvh {0}{1}'.format(repo_url, repo_path))

       installed = "package epel-release-5-4.noarch is already installed"

       if output.failed and installed not in output:

           abort(output)

   # Install the FrameOS RBEL Yum Repository.

   #get rhel version
   with settings(hide('warnings', 'running'), warn_only=True):

       repo_url = "http://rbel.co/rbel5"

       repo_path = ""

       output = sudo('rpm -Uvh {0}{1}'.format(repo_url, repo_path))

       installed = "package rbel5-release-1.0-2.el5.noarch is already installed"

       if output.failed and installed not in output:

           abort(output)

       output = sudo('cat /etc/redhat-release')

       rhel_version = re.findall("\d[\d.]*",output)[0].split('.')[0]

   if rhel_version =='5':

     # Install the EPEL Yum Repository.

     with settings(hide('warnings', 'running'), warn_only=True):

         repo_url = "http://download.fedora.redhat.com"

         repo_path = "/pub/epel/5/i386/epel-release-5-4.noarch.rpm"

         output = sudo('rpm -Uvh {0}{1}'.format(repo_url, repo_path))

         installed = "package epel-release-5-4.noarch is already installed"

         if output.failed and installed not in output:

             abort(output)

     # Install the FrameOS RBEL Yum Repository.

     with settings(hide('warnings', 'running'), warn_only=True):

         repo_url = "http://rbel.co/rbel5"

         repo_path = ""

         output = sudo('rpm -Uvh {0}{1}'.format(repo_url, repo_path))

         installed = "package rbel5-release-1.0-2.el5.noarch is already installed"

         if output.failed and installed not in output:

             abort(output)

   elif rhel_version =='6':

     with settings(hide('warnings', 'running'), warn_only=True):

         repo_url = "http://download.fedora.redhat.com"

         repo_path = "/pub/epel/6/i386/epel-release-6-5.noarch.rpm"

         output = sudo('rpm -Uvh {0}{1}'.format(repo_url, repo_path))

         installed = "package epel-release-6-5.noarch is already installed"

         if output.failed and installed not in output:

             abort(output)

     # Install the FrameOS RBEL Yum Repository.

     with settings(hide('warnings', 'running'), warn_only=True):

         repo_url = "http://rbel.co/rbel6"

         repo_path = ""

         output = sudo('rpm -Uvh {0}{1}'.format(repo_url, repo_path))

         installed = "package rbel6-release-1.0-2.el6.noarch is already installed"

         if output.failed and installed not in output:

             abort(output)

Hi,
what do you think about something like this?
https://gist.github.com/1318780

yes it works on centos 5
you might get that error since you still have the old elff yum repo on your machine, removing from /etc/yum/repos.d/ and doing yum clean all should fix it
Cheers,
Cristi

ok, yes, that did it!
Anyway, what about CentOS 6?

all good for CentOS 6 also
thank you for adding this feature

Great! Thanks for reporting!


Update spotify-player extension

Description
Scope: https://www.raycast.com/mattisssa/spotify-player
Added a new feature to display the explicit flag behind matching tracks with explicit lyrics
Added a settings prop in the Raycast menu to enable/disable the display of explicit flags (default: false)
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hey, we've been re-writing the Spotify Player extension for the last few weeks. The Beta version is now available on the store
→ https://www.raycast.com/mattisssa/spotify-beta
The new version also doesn't include the explicit icon, but happy to consider it.
Feel free to join our Community Slack and look for the #spotify-beta-testers channel


cleanup pipe

removing the dist folder :)

thinking better now, this is pretty much useless.
nervermind

thinking better now, this is pretty much useless.
nervermind

👍  - I'm using dist/ for my docker builds, this PR would have made it complicated


Partially refactor the documentation (partial fix for #71)

Unfortunately I didn't finish the job for #71, as I intended, but I'm submitting whatever I did.

@aptiko  Could you just reformat ./pydifact/segmentcollection.py with black - that's the only check that is failing - then I can merge this PR happily.
Thanks a bunch!

@nerdoc I did it. I did not add a separate commit; I amended the preceding one.

Thanks for your work - every bit is appreciated here.


Savings Method not providing solution to A-n32-k5 (CVRP Instance)

Hello,
I am trying to solve the CVRP instance A-n32-k5 with the savings method as the first solution strategy. However, no solution is displayed when I run the code.  When I change the first solution strategy to say PATH_CHEAPEST_ARC, I am getting a solution.
Language: Tried in Python (Collab) and C++17 (VS 2022) (Same Result)
OR Tools Version: 9.3
OS: Windows
Relevant Code:
search_parameters = pywrapcp.DefaultRoutingSearchParameters()
search_parameters.first_solution_strategy = (routing_enums_pb2.FirstSolutionStrategy.SAVINGS)
solution = routing.SolveWithParameters(search_parameters)
print_solution(data, manager, routing, solution)

The same program seems to work for a different instance.

These are heuristics. They may not find solutions for different instances, especially with capacity constraints.


Channel seperator node

Adds a node for separating the alpha and RGB channels of an image. This PR also adds some Blend modes to recombine the separate channels, those are intended as a temporary solution and will be combined into a new node soon.
Closes #1169

(Don't Merge yet, there are some weird WASM errors that don't show up with cargo check)

Was the plan to also add channel combine nodes in this PR? (A separate PR would be fine too if you prefer that.) And are there any further improvements planned in this PR?

I just rebased the branch, if the checks all pass this is ready for review, I'll add the 'combine' node in a new PR.
Also, I think the appearance of the node could maybe be improved, as it has 3 equally important outputs and no 'main' output, which makes it not that intuitive to use. It would be nice if you could have a look at that, as I'm not that involved in the front-end part of things.

Thanks for pointing out the fact that its input/output structure is rather ugly, I forgot to actually test it and comment on that! We want to have zero primary outputs and three (R/G/B) return value (i.e. non-primary) outputs.
We also want to name this "Split Channels". And what do you think about adding a fourth channel for alpha? The channel outputs themselves should probably be shortened to just "Red", "Green", "Blue", (and "Alpha"?).

As discussed on Discord, please also remove the three checkbox parameters and make the data output be the Luma type instead of the Color type, and add a "Luma to Color" node which takes the one channel and splats it to three channels (resulting visually in a gray color).
And since there's a single issue for this (#1169), would you actually mind doing the "Combine Channels" node in this PR too? I realize that'll delay its merge but it would help with organization. If you still prefer to merge this first, just say so and we can do that anyways :)

To summarize the desired functionality for the polished version of this PR feature set:

Split Channels node. One primary input (Color), zero primary outputs. Zero parameter inputs, three (or four?) returned outputs named "Red", "Green", "Blue" of type Luma. Consider also including "Alpha" as a fourth.
Combine Channels node. Zero primary inputs, one primary output (Color). Three (or four?) parameter inputs taking Luma parameter inputs named "Red", "Green", "Blue" (and "Alpha"?), zero returned outputs.
Luma to Color node. One primary input (Luma), one primary output (Color). Splats the single channel to the three channels and gives an alpha value of 1.

We also want to name this "Split Channels". And what do you think about adding a fourth channel for alpha? The channel outputs themselves should probably be shortened to just "Red", "Green", "Blue", (and "Alpha"?).

Should be all done :+1:

[ ] Combine Channels shouldn't have a primary input
[ ] Split Channels shouldn't have a primary output
[ ] I think it'd be best to also add Alpha to both
[ ] With the same reasoning, Extract Alpha can be a choice in the Extract Channel node instead of being a separate node

I also ran into a crash, twice, involving the usage of the Extract Alpha node but I can't seem to be able to find a reproducible case. Here's its stack trace:

With the same reasoning, Extract Alpha can be a choice in the Extract Channel node instead of being a separate node

But not every colour has alpha so it makes sense to model the proto nodes after the color traits

[ ]  Combine Channels shouldn't have a primary input
[ ]  Split Channels shouldn't have a primary output

I think I talked to @TrueDoctor about this when I implemented the split node, and if I remember correctly he said that it's not really possible to do this from the backend (the first input/output is always interpreted as main I/O by the frontend). I could maybe try to figure out where in the code this would need to be added, but I would assume that would be beyond the scope of this PR (and also probably my knowledge of the codebase).

[ ]  I think it'd be best to also add Alpha to both

That's actually already implemented: The 'main' I/O represents the Alpha Channel

[ ]  With the same reasoning, Extract Alpha can be a choice in the Extract Channel node instead of being a separate node

Initially, I had implemented it that way, but @TrueDoctor suggested splitting it into a separate node. While I can combine them again, it would make the code less elegant. Currently, I use the RedGreenBlue Enum to determine the channel for extraction/insertion. If I add the alpha channel, I would need to create a new Enum with the same value + Alpha.

I also ran into a crash, twice, involving the usage of the Extract Alpha node but I can't seem to be able to find a reproducible case. Here's its stack trace:

I'll look into that :+1:

I think I talked to @TrueDoctor about this when I implemented the split node, and if I remember correctly he said that it's not really possible to do this from the backend (the first input/output is always interpreted as main I/O by the frontend). I could maybe try to figure out where in the code this would need to be added, but I would assume that would be beyond the scope of this PR (and also probably my knowledge of the codebase).

Not having a primary input is sort of possible by just setting the primary input to the empty tuple in the document node definition but I don't think that is possible for primary outputs atm. I guess the only difference is that the primary output is not named and the others are but from a code perspective they are identical

That's actually already implemented: The 'main' I/O represents the Alpha Channel

I don't understand what you mean by that, could you please rephrase or elaborate? To clarify my intent, I am saying that the "Alpha" channel should be output as a fourth parameter and input as a fourth parameter so the user can shuffle it around like the other channels.

I am a bit confused what the channel split and combine nodes do here.

Why is the result of only connecting the red channel from the input image with the red channel of the output image a grayscale? Shouldn't it be a red image?
When I do the same with blue or/and green instead, the image goes blank
The original image (left) and the image with all channels splitted and merged again (right) somehow aren't exactly the same. If you take a close look at the zoomed in image section, you'll notice some artifacts like the red "dots" at the border of the petal. Could it be that some color information gets lost in this process?

Shure; The Split should have 4 Outputs. 3 Labeled Red, Green, and Blue and one unlabeled one (the Primary Output). For Images without an Alpha Channel, this outputs a white Image. The same happens with the Combine node, the unlabeled (primary) Input uses a Mask Node behind the scenes to insert an Alpha Channel into the Image. You can see this by inserting some data into the Alpha Channel of an Image using the Mask Node and then feeding the Result into a Split Node.

I see, thanks for explaining. Unfortunately that's rather unintuitive to make the alpha channel use the primary input/output though. I'd rather we lablel it "Alpha" and place it after the RGB channels.

I'd rather we lablel it "Alpha" and place it after the RGB channels.

Shure, but then the Red Channel would become the primary I/O, indicating a difference between the Red Channel and the Green/Blue Channel. If that is fine I can implement that change.

I was suggesting that the primary input/output be removed entirely from both nodes.

I was suggesting that the primary input/output be removed entirely from both nodes.

Yeah, but I thought that wasn't possible at the Moment? At least that's what I got from this message.

From that, it sounds like a lack of primary input is possible but not a lack of primary output. I'd suggest implementing that and then we file a followup issue to support optional primary outputs and a removal of the node's primary output (which should be set to output nothing).

The IO stuff should be implemented now, I have a solution for the Issues nat-rix brought up and am currently implementing that (Should be done soonTM, the biggest hurdle currently is figuring out how the node_registry works)

This is great!
Btw, when connecting the green channel of split channels with the green channel of combine channels, the editor crashes with the assertion:

When connecting the green channel of split channels with the green channel of combine channels, the editor crashes with the assertion

Thanks, I know what's causing that, that's also going to be fixed by the stuff I'm doing in the node_registry


Setting more than one property of Role in a callback doesn't work?

I'm up-to-date on 11.0.0.  I've got the following code from back when I was starting out, which I recently added permissions to:
guild.createRole({ name: "color_" + hex })
    .then(
        role => {
          role.setColor(hex);
          role.setPermissions(
              [
                "CREATE_INSTANT_INVITE",
                "CHANGE_NICKNAME",
                "READ_MESSAGES",
                "SEND_MESSAGES",
                "SEND_TTS_MESSAGES",
                "EMBED_LINKS",
                "ATTACH_FILES",
                "READ_MESSAGE_HISTORY",
                "EXTERNAL_EMOJIS", // use external emojis
                "ADD_REACTIONS", // add reactions to messages
                "CONNECT", // connect to voice
                "SPEAK", // speak on voice
                "USE_VAD" // use voice activity detection
              ]
          );
          getGuildMemberForUser(user, guild).addRole(role);
        })
    .catch(console.log);

When I run it, my color flickers and then resets, but the permissions are correct (aka I can't use @here.)  If I swap the order of the .setColor and .setPermissions lines, my color stays correct but my permissions are then wrong, like only the last change counts or something.  Either way, the .addRole line at the bottom still works.
Is this a bug, or am I simply mistaking what can be done inside a promise's callback?
Note that I replaced it with this code tonight, which appears to work fine, so at least I found a workaround:
guild
    .createRole(
        {
          name: "color_" + hex,
          color: parseInt(hex.substr(1), 16), // hex is of type "#123456"
          permissions:
              [
                "CREATE_INSTANT_INVITE",
                "CHANGE_NICKNAME",
                "READ_MESSAGES",
                "SEND_MESSAGES",
                "SEND_TTS_MESSAGES",
                "EMBED_LINKS",
                "ATTACH_FILES",
                "READ_MESSAGE_HISTORY",
                "EXTERNAL_EMOJIS", // use external emojis
                "ADD_REACTIONS", // add reactions to messages
                "CONNECT", // connect to voice
                "SPEAK", // speak on voice
                "USE_VAD" // use voice activity detection
              ]
        })
    .then(
        role => {
          getGuildMemberForUser(user, guild).addRole(role);
        })
    .catch(console.log);

Thanks for all your hard work! :)

the issue is calling two role edits at the same time. setting the color and setting the permissions both edit the role the same way. to fix this you should do something like
role.setColor(...).then(() => role.setPermissions(...));


CLI installed with Homebrew is missing version information

Bug description:
After installing v0.4.2 of the CLI with brew install osm, osm version does not contain version information.
% osm version
Version: dev; Commit: ; Date: 2020-10-23-15:49

This is because the version information is parsed out of git but the Homebrew formula only downloads the source without the git data. https://github.com/Homebrew/homebrew-core/blob/9f1c3731538887ee99d2fc1abaed6e3a19245d3b/Formula/osm.rb#L4
Affected area (please mark with X where applicable):

Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [ ]
Egress                     [ ]
Envoy Control Plane        [ ]
CLI Tool                   [X]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [ ]
CI System                  [ ]

Expected behavior: osm version gives the full version information, including semver and git SHA.
Steps to reproduce the bug (as precisely as possible):
% brew install osm
% osm version

How was OSM installed?: Homebrew
Anything else we need to know?:
Environment:

OSM version (use osm version):
Kubernetes version (use kubectl version):
Size of cluster (number of worker nodes in the cluster):
Others:

Fixed!
$ brew install osm
==> Downloading https://homebrew.bintray.com/bottles/osm-0.7.0_1.catalina.bottle.tar.gz
==> Downloading from https://d29vzk4ow07wi7.cloudfront.net/ee3e3de0a60d14d84038db764b49a7c2078c9c8a582afe92e79
######################################################################## 100.0%
==> Pouring osm-0.7.0_1.catalina.bottle.tar.gz
🍺  /usr/local/Cellar/osm/0.7.0_1: 5 files, 40.4MB
$ osm version
Version: v0.7.0; Commit: 75423a0b4a3d5e9114fd93a133d2485171243c4b; Date: 2021-02-10-22:09


node_modules\react-native-network-info\android\src\main\java\com\pusherman\networkinfo--- run gradlew assembleRelease to build APK error

when you run gradlew assembleRelease to build APK, there will be an error as below:
node_modules\react-native-network-info\android\src\main\java\com\pusherman\networkinfo\RNNetworkInfoPackage.java:26: 错误: 方法不会覆盖或实现超类型的方法
@Override

you can commented code as below:
@Override
public List<Class<? extends JavaScriptModule>> createJSModules() {
return new ArrayList<>();
}

Yup, for this version we should not have this class: https://github.com/facebook/react-native/commit/ce6fb337a146e6f261f2afb564aa19363774a7a8
not sure why this got added back but it makes any update past 3.1.0 break android builds.

Thanks guys!  Just pushed out a new release that should resolve it.


Headers configuration that allow underscores

[X] Bug fix
[ ] New feature
[ ] BC breaks
[ ] Deprecations
[X] Tests pass

Fixed tickets: [#101 - Params in header]
License: MIT

Symfony Doc: http://symfony.com/doc/current/components/config/definition.html#array-node-options

Thanks for this improvement and your effort, @PWalkow!

@florianpreusner Let us know please if this branch will be also released at 5.* tag that is used by stable version in packagist.

Yip, will be released this evening. 👍

Released https://github.com/8p/GuzzleBundle/releases/tag/v5.4.0

Thank you @florianpreusner but looks like packagist need an update as well to pick up latest 5.4 version

Fixed! Strange that I had to this manually. Thanks for the hint, @PWalkow!
https://packagist.org/packages/eightpoints/guzzle-bundle

Because of some issues I removed v5.4 and released a new major version 6.0.

https://github.com/8p/GuzzleBundle/issues/112
https://github.com/8p/GuzzleBundle/pull/106#issuecomment-319965075


Android OutOfMemoryError

Testing the latest GraphHopper on Android, I see often OutOfMemoryError during route calculations.
I don't remember having these issues with previous GH.
Current tests are with GraphHopper().forMobile() initialization, non CH graphs and bidirectional A* algorithm.
The routes causing the OOM are mainly country sized.
Will continue to investigate with other settings too, as it's quite serious issue.
(maybe related to #464 needed changes)

I tested also with the default bidirectional Dijkstra, situation is better but OOM exceptions happen again.
@karussell I remember you had mentioned that bidirectional A* is currently the fastest algorithm for non contraction hierarchies, is this still right?
java.lang.OutOfMemoryError
    at gnu.trove.map.hash.TIntObjectHashMap.rehash(TIntObjectHashMap.java:158)
    at gnu.trove.impl.hash.THash.postInsertHook(THash.java:388)
    at gnu.trove.map.hash.TIntObjectHashMap.doPut(TIntObjectHashMap.java:248)
    at gnu.trove.map.hash.TIntObjectHashMap.put(TIntObjectHashMap.java:222)
    at com.graphhopper.routing.DijkstraBidirectionRef.fillEdges(DijkstraBidirectionRef.java:212)
    at com.graphhopper.routing.DijkstraBidirectionRef.fillEdgesFrom(DijkstraBidirectionRef.java:157)
    at com.graphhopper.routing.AbstractBidirAlgo.runAlgo(AbstractBidirAlgo.java:74)
    at com.graphhopper.routing.AbstractBidirAlgo.calcPath(AbstractBidirAlgo.java:63)
    at com.graphhopper.GraphHopper.getPaths(GraphHopper.java:1053)
    at com.graphhopper.GraphHopper.route(GraphHopper.java:924)

Hmmh, I'm a bit surprised that it has worked before. I do not have something in mind which could cause this problem, as only the memory layout for CH has changed. But maybe you can memory profile both setups in more detail?
Also bidir A* should be the fastest although I noticed some contrary numbers - I have to dig into it the next days. As none CH will be a major focus for 0.6
Also related to our very first issue #1

You mean non CH large routing is not supposed to work in memory restricted environments like Android?
You puzzled me! I'm trying to remember if I performed indeed country sized queries on Android with <0.5 versions.. :-)
What we're dealing here is actually the VM heap size that we can use (not device RAM).
And it can differentiate per device and Android version...
@karussell  thanks for answering, I wanted your opinion regarding GH internal memory consumption with the latest major changes.
Of course I'll perform more tests along the way.

You mean non CH large routing is not supposed to work in memory
restricted environments like Android?

I think there are tricks like the 'big memory' option and similar stuff where you can make it working even in the current form, but as of today I had major difficulties to make it working without OOMs for none CH routes on my old 2.3 device.

What we're dealing here is actually the VM heap size that we can use (not device RAM).

Yes and no. Because if you are using the MMAP option (are you?) then some native RAM outside of the heap can be (automatically) utilized for the graph and the VM heap is only used for the algorithm traversal.
The best thing would be if you find the single commit where you observe the dramatic behaviour change. Although I'm pretty sure that this is very time-consuming even with git bisect ... never done so for Android ...

You mean the android:largeHeap directive in manifest.
I didn't prefer the MMAP option because of the different device storage speeds leading to slow routing, but that's a valid suggestion to put in testing.

You mean the android:largeHeap directive in manifest.

yes :)

I didn't prefer the MMAP option so far

Oh, wow! So you say you have used the in-memory option without CH on Android? With the largeHeap option? And which country?

Cruiser on Google Play is without MMAP and largeHeap options.
And I have not seen so far any user reports regarding OOM, but how many actually perform large country sized routing.

SORRY for the misunderstanding!
Like I said in the 1st post I actually use the GraphHopper().forMobile() which is MMAP.
(and of course so Cruiser does)
I mistook our conversation and GH options - forgot what the API calls underneath. :(

No problem, still would be worth if you can find out the the problematic change or something else

@karussell I performed some quick tests with GH version prior the aforementioned major changes and same client / graph settings.
Again we have Android OOM at large country sized routing, so apparently this is something not new.

Ok, so this is nothing newly introduced (?) and we have #1 and can close here?

Yes, you are right, I'm closing this.

Speed comparison is now here: #506

:+1:


Added example with countries

This PR is the first step to add more realistic examples. It reads country names from a JSON list, builds a spaczz ruler for NER on top of en_core_web_sm and then performs a few tests. It's not created as a unit test with assertions since I originally meant it as a benchmark, but it finds a few odd results and perhaps it should be added as one.
It's currently finding some basic errors, so let's consider it a starting point. Errors found:
Error in testMultiMatch
[('Northern Ireland', 'Northern Ireland'), ('Åland Islands', 'and Ireland')]
Error in testLorem
[('Chad', 'had'), ('Oman', 'man'), ('Chad', 'had'), ('Oman', 'man'), ('Togo', 'Too'), ('Oman', 'man'), ('Poland', 'norland'), ('Belize', 'believe'), ('Chile', 'children'), ('Belize', 'believe'), ('Yemen', 'men'), ('Chad', 'had'), ('Chad', 'Had'), ('France', 'face'), ('Poland', 'norland'), ('Spain', 'speaking'), ('Chad', 'hand'), ('Togo', 'too'), ('Togo', 'took'), ('Spain', 'speaking'), ('Guam', 'game'), ('Mayotte', 'matter')]

The "Åland Islands" mistake is pretty bad. The testLorem errors are understandable but indicate that the defaults are a bit too permissive, so it might be wise to tune them a bit. Note I'm running spaczz before spacy's NER -- which is what I'd first try in a real project, to make sure it finds these entities first.

Thanks @brunobg! I'm merging this and will start using it for additional profiling and testing.
While I agree that the examples you show above show less than stellar results, they make sense given spaczz's default settings.
from rapidfuzz import fuzz

fuzz.ratio('Åland Islands'.lower(), 'and Ireland'.lower())

75.0 # == spaczz's default `min_r2`

Perhaps the defaults should be less permissive but I think the truth is that different matching tasks probably require tuning the settings to maximize accuracy. Maybe there is an algorithmic approach to setting "optimal" defaults based on the data but that would require more research. Providing an automated tuning option for the settings given labeled data is another approach.
As of now tweaking those settings is in the hands of the user.

I understand that, but I suggest you write clearer documentation of these parameters. It's still a bit hard to understand which parameters to set and which values should more or less work.
Anyway, the main problem with 'Åland Islands' and  'and Ireland' is that to me it should pick Ireland instead. It's a perfect match, so it should rate higher. I imagine that most applications would rather get the exact match when it exists, and if I may suggest it, the default settings should enable that.


[CI] fix travis to use oap-master branch of arrow

Signed-off-by: Yuan Zhou<EMAIL_ADDRESS>

@zhixingheyi-tian just updated travis to use the oap-master branch.


[Bugfix] Fix a crash caused by a critical edge during  loop unrolling

This crash was found while refactoring the partition and deabstraction passes.
This PR makes sure we can even unroll loop body even if critical edges are introduced during canonicalization. Consider the following CFG:
    [0]
     |
 +->[1]-->[3]
 |   |
 +--[2]

This loop needs to be canonicalized as [1] contains side-effecting operations (sendToHost here). After the canonicalization the CFG looks like below:
    [0]
     |
 +->[NH]-->[3]
 |   |
 |  [1]--+
 |   |   |
 |  [2]  |
 |   |   |
 +--[L]<-+

Note that the edge [1] -> [L] is a critical edge. It also happens that this loop needs to be unrolled once. This PR makes sure such loops are unrolled correctly.

@swift-ci please test tensorflow


SyncBatchNorm NOT Supporting Mix Precision Training for Float16

Current SyncBatchNorm does not consider the mix precision training for float16. Standard BatchNorm allows using float32 params with float16 data.
http://mxnet.incubator.apache.org/versions/master/api/python/gluon/contrib.html?highlight=syncbatchnorm#mxnet.gluon.contrib.nn.SyncBatchNorm

Thanks for reporting the issue, taking a look at this now. @mxnet-label-bot [Feature Request, Operator].

The changes in #12261 are being verified with actual workloads at this time.

This would be very useful. How's it going?


Fix issue #314

[x] Helper method of the resource was returning a string type even though the schema of the MSFT_xWebApplicationAuthenticationInformation is expecting Boolean values.

[x] Include the namespace 'root\microsoft\windows\desiredstateconfiguration' when creating the cim instance.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

a discussion (no related file):
Could you please resolve the failing tests? I can't merge with failing tests.

DSCResources/MSFT_xWebApplication/MSFT_xWebApplication.psm1, line 583 at r1 (raw file):

    foreach ($type in @('Anonymous', 'Basic', 'Digest', 'Windows'))
    {
        $authenticationProperties[$type] = [Boolean](Test-AuthenticationEnabled -Site $Site `

Can you please verify this? If you look at the comment-based help for this helper function it returns a string of 'true' or 'false'. So maybe the OutputType is wrong on the helper function?

DSCResources/MSFT_xWebApplication/MSFT_xWebApplication.psm1, line 591 at r1 (raw file):

            -ClassName MSFT_xWebApplicationAuthenticationInformation `
            -ClientOnly -Property $authenticationProperties `
            -NameSpace 'root\microsoft\windows\desiredstateconfiguration'

Curious, why are we adding this? :slightly_smiling_face:

DSCResources/MSFT_xWebApplication/MSFT_xWebApplication.psm1, line 604 at r1 (raw file):

        -ClientOnly `
        -Property @{Anonymous=$false;Basic=$false;Digest=$false;Windows=$false} `
        -NameSpace 'root\microsoft\windows\desiredstateconfiguration'

Same curious question as previous comment.

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

a discussion (no related file):
Does this resolve issue #314 or are you pointing to the wrong issue maybe?  :thinking:  The proposed solution in issue #314 looks different.

Comments from Reviewable

Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

a discussion (no related file):
Previously, johlju (Johan Ljunggren) wrote…
Does this resolve issue #314 or are you pointing to the wrong issue maybe?  :thinking:  The proposed solution in issue #314 looks different.

I understand this PR now. Please ignore previous comments and review comments, let's start from the beginning again.

a discussion (no related file):
Please make sure that the tests are passing. See review comment

DSCResources/MSFT_xWebApplication/MSFT_xWebApplication.psm1, line 583 at r1 (raw file):

    foreach ($type in @('Anonymous', 'Basic', 'Digest', 'Windows'))
    {
        $authenticationProperties[$type] = [Boolean](Test-AuthenticationEnabled -Site $Site `

We should make sure Test-AuthenticationEnabled returns the  correct type instead of casting it here.

DSCResources/MSFT_xWebApplication/MSFT_xWebApplication.psm1, line 583 at r1 (raw file):

    foreach ($type in @('Anonymous', 'Basic', 'Digest', 'Windows'))
    {
        $authenticationProperties[$type] = [Boolean](Test-AuthenticationEnabled -Site $Site `

The same issue exist in xWebSite, the helper function Test-AuthenticationEnabled fails for the same reason. Those tests are failing. Would you mind fixing that helper function as well?

DSCResources/MSFT_xWebApplication/MSFT_xWebApplication.psm1, line 583 at r1 (raw file):

    foreach ($type in @('Anonymous', 'Basic', 'Digest', 'Windows'))
    {
        $authenticationProperties[$type] = [Boolean](Test-AuthenticationEnabled -Site $Site `

One helper functions unit test are failing, could you please resolve that?
https://ci.appveyor.com/project/PowerShell/xwebadministration/build/1.17.988.0#L2800

Comments from Reviewable

@BerheAbrha I'm closing and reopening this issue to kick off the tests again, for some reason the test ran for 3 hours and then timeout out, that can't be correct, must have been a glitch.

Reopening agin to kick off the tests

Review status: all files reviewed at latest revision, 6 unresolved discussions, some commit checks failed.

a discussion (no related file):
Please add an entry for this change under the Unreleased section in the README.md.

Comments from Reviewable

@BerheAbrha Now both resources are almost passing the tests, could you please look at the two last two test that are failing on for the helper function. Also, could you please look at the review comments that are left. Thanks.

Reviewed 1 of 1 files at r1, 4 of 4 files at r3.
Review status: all files reviewed at latest revision, 7 unresolved discussions.

Comments from Reviewable

Reviewed 4 of 4 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

For some reason the check for the tests has gone missing. I will close and reopen to see if that will kick off the tests.

@BerheAbrha Many thanks for this!!! 😄 🙇