[Python][C++] How to limit the memory consumption of to_batches()

In order to get the unique values of a column of a 500GB Parquet dataset (made of 13 000 fragments) on a computer with 12GB of memory, I chose to use to_batches() as following :
import pyarrow as pa
import pyarrow.dataset as ds
partitioning = ds.partitioning( pa.schema([(timestamp, pa.timestamp("us"))]),flavor="hive",)
unique_values = set()
dataset = ds.dataset(path, format="parquet", partitioning=partitioning)
batch_it = dataset to_batches(columns=[column_name])
for batch in batch_it:
    unique_values.update(batch.column(column_name).unique())
The problem is that the process quickly accumulates memory and exceeds the amount available.
When I put a breakpoint on the line "for batch in batch_it", the process continues to accumulate memory until it crashes.
I understand that to_batches readahead but I thought I could limit it with "fragment_readahead" parameter. Is there a way to limit readahead ? Is there a way to "free" memory after a batch has been consumed ?
Is there another way to go ? My first try was using to_table() but it needs 20GB of memory in that case. It seems that to_batches would also need 20GB
Component(s)
Python

I use pyarrow 10.0.1

Hmm, backpressure should be applied then.  Once you call to_batches it should start to read in the background.  Eventually, at a certain point, it should stop reading because too much data has accumulated.  This is normally around a few GB.  You mention there are 13k fragments, just to confirm this is 13k files right?  How large is each file?  How many row groups are in each file?

Code to generate a dataset would be helpful.  We likely need some refinement on memory usage (and monitoring) in the execution engine in general but I don't know that I will be able to get to it soon.

While writing code to write and read the dataset, I have noticed that my problem is linked to the size of the metadata of the schema ; is there a limit ?
Here is my code :
import json
from typing import Any
import numpy as np
import pandas as pd
import pyarrow as pa
import pyarrow.dataset as ds
DATASET_HEADER = "dataset_header"
PARQUET_FLAVOR = "hive"
PARQUET_FORMAT = "parquet"
TIME_COLUMN = "gps_time_stamp"
DEFAULT_PARTITIONING: ds.Partitioning = ds.partitioning(
pa.schema([(TIME_COLUMN, pa.timestamp("us"))]),
flavor=PARQUET_FLAVOR,
)
dataset_path = "/tmp/dataset"
nb_data_values = 60000
def generate_dataframe():
nb_rows = 400
data = np.float32(np.random.normal(size=nb_data_values))
return pd.DataFrame([{"ATTRIBUTE": i, "data": data} for i in range(nb_rows)])
def write_fragment(df, path):
dataset_header: dict[str, Any] = {}
dataset_header["sampling"] = np.arange(0, nb_data_values, 1).tolist()  # if removed, the problem disapear
schema_with_metadata = pa.Schema.from_pandas(df).with_metadata({DATASET_HEADER: json.dumps(dataset_header)})
ds.write_dataset(
data=pa.Table.from_pandas(df).cast(schema_with_metadata),
base_dir=path,
format=PARQUET_FORMAT,
partitioning=DEFAULT_PARTITIONING,
existing_data_behavior="overwrite_or_ignore",
file_options=ds.ParquetFileFormat().make_write_options(allow_truncated_timestamps=True),
)
def write():
trace_length_pd = pd.Timedelta(milliseconds=60000)
first_timestamp = pd.Timestamp("2023-01-23 09:15:00.000000")
nb_timestamps = 260
for i in range(nb_timestamps):
df = generate_dataframe()
df[TIME_COLUMN] = pd.Timestamp(first_timestamp + i * trace_length_pd)
print("Generating data for timestamp ", i)
write_fragment(df, dataset_path)
def read():
dataset = ds.dataset(dataset_path, format="parquet", partitioning=DEFAULT_PARTITIONING)
unique_values = set()
for batch in dataset.to_batches(columns=[TIME_COLUMN]):
unique_values.update(batch.column(TIME_COLUMN).unique().to_numpy())
print(len(unique_values))
write()
read()

I think the problem is on my side : I divert the use of metadata from the schema of each fragment to put a large amount of data (around 400kB).
I have centralised the metadata in a _metadata file (like in https://arrow.apache.org/docs/python/parquet.html#writing-metadata-and-common-metadata-files) and the problem disapears.

Thanks for the explanation.  I do think we cache the metadata per-file when opening a dataset.  The original thought was that a user might open a dataset and then scan it multiple times.  If we cache the data the first time then we can save time on future reads.  However, if you have large metadata and many files then I think that becomes problematic.  I will open a separate issue for that.

I've opened #33888 to address this metadata caching problem.

I wanted to second this issue as I am having the same problem. In my case the problem stems from the python package deltalake which uses the arrow format. We use deltalake to read from Delta with arrow because Spark is less performant in many cases. However, when trying dataset.to_batches() it appears that all available memory is quickly consumed even if the dataset is not very large (e.g. 100M rows x 50 cols). I have reviewed the documentation and its not clear what I can do to resolve the issue in its current state. Any suggestions workarounds would be much appreciated. We are using pyarrow==10.0.1 and deltalake==0.6.3.

Also for reference #33624 is the same issue where a 54MB small file results in GBs of memory usage.

I wanted to second this issue as I am having the same problem. In my case the problem stems from the python package deltalake which uses the arrow format. We use deltalake to read from Delta with arrow because Spark is less performant in many cases. However, when trying dataset.to_batches() it appears that all available memory is quickly consumed even if the dataset is not very large (e.g. 100M rows x 50 cols). I have reviewed the documentation and its not clear what I can do to resolve the issue in its current state. Any suggestions workarounds would be much appreciated. We are using pyarrow==10.0.1 and deltalake==0.6.3.

Do you also have many files with large amounts of metadata?  If you do not then I suspect it is unrelated to this issue.  I'd like to avoid umbrella issues of "sometimes some queries use more RAM than expected".
#33624 is (as much as I can tell) referring to I/O bandwidth and not total RAM usage.  So it also sounds like a different situation.  Perhaps you can open your own issue with some details about the dataset you are trying to read (how many files?  What RAM consumption are you expecting?  What RAM consumption are you seeing?)

I wanted to second this issue as I am having the same problem. In my case the problem stems from the python package deltalake which uses the arrow format. We use deltalake to read from Delta with arrow because Spark is less performant in many cases. However, when trying dataset.to_batches() it appears that all available memory is quickly consumed even if the dataset is not very large (e.g. 100M rows x 50 cols). I have reviewed the documentation and its not clear what I can do to resolve the issue in its current state. Any suggestions workarounds would be much appreciated. We are using pyarrow==10.0.1 and deltalake==0.6.3.

Do you also have many files with large amounts of metadata? If you do not then I suspect it is unrelated to this issue. I'd like to avoid umbrella issues of "sometimes some queries use more RAM than expected".
#33624 is (as much as I can tell) referring to I/O bandwidth and not total RAM usage. So it also sounds like a different situation. Perhaps you can open your own issue with some details about the dataset you are trying to read (how many files? What RAM consumption are you expecting? What RAM consumption are you seeing?)

My issue is that when I use ‘to_batches()’ even on a small datasets sub 1GB my free memory is quickly consumed which often results in an OOM error. Based on the issue title and the description by the OP I thought the issue was similar or perhaps the same and did not require new issue. However, I can open a new one if you find it appropriate.

I wanted to second this issue as I am having the same problem. In my case the problem stems from the python package deltalake which uses the arrow format. We use deltalake to read from Delta with arrow because Spark is less performant in many cases. However, when trying dataset.to_batches() it appears that all available memory is quickly consumed even if the dataset is not very large (e.g. 100M rows x 50 cols). I have reviewed the documentation and its not clear what I can do to resolve the issue in its current state. Any suggestions workarounds would be much appreciated. We are using pyarrow==10.0.1 and deltalake==0.6.3.

Do you also have many files with large amounts of metadata? If you do not then I suspect it is unrelated to this issue. I'd like to avoid umbrella issues of "sometimes some queries use more RAM than expected".
#33624 is (as much as I can tell) referring to I/O bandwidth and not total RAM usage. So it also sounds like a different situation. Perhaps you can open your own issue with some details about the dataset you are trying to read (how many files? What RAM consumption are you expecting? What RAM consumption are you seeing?)

I thought it was likely related both issues are caused when using ‘to_batches()’ on small data with the difference being I am reading directly from a mounted disk and the OP is reading over the network. If the scanner is the cause as some comments have suggested both our issues would be resolved by a fix.

I thought it was likely related as both issues are caused when using ‘to_batches()’ on small data with the difference being I am reading directly from a mounted disk and the OP is reading over the network. If the scanner is the cause as some comments have suggested both our issues would be resolved by a fix.

OP's issue has been identified and they have found a workaround (don't store full metadata in each file) and we have identified a long term fix (#33888).  That problem and fix do not have anything to do with #33624.  In #33624 the total data transferred is larger than the on-disk size of the data.  This would not be caused by arrow retaining metadata in RAM.

Ok thank you for redirecting me to the appropriate issue number.


Support AWS cloudwatch datasource

This is PR seeks to add support to go-grafana-api for Grafana's AWS cloudwatch datasource, which requires jsonData and secureJsonData fields in the JSON POST'd during cloudwatch-datasource-creation as documented here.
This PR is also necessary to address terraform-providers/terraform-provider-grafana issue #4.
Thanks!

@apparentlymart Hi Martin - Any thoughts on this PR? Thanks!

Great, thanks. This looks good to me!


CL - NavigationView Viper Implementation

📋 PR Description
This PR is an example created to demonstrate the use of NavigationView. Users can navigate to the detail page using NavigationLink, and a settings button is placed in the top toolbar. This provides a simple example to explain navigation functionality in SwiftUI.

✅ Checklist

[x] Code follows the project standards and guidelines.
[ ] Relevant unit tests are written and all tests are passing.
[ ] Test coverage is adequate for the changes.
[ ] Any unnecessary files or debug statements have been removed.
[ ] Documentation is updated where necessary.
[x] The PR has been reviewed by at least one team member before merging.

🛠 Steps to Test

Launch the application.
Navigate to the NavigationView screen from HomeView by clicking the "NavigationView" button.
Test the back button to ensure it navigates correctly to the HomeView.

🔗 Related Links

Documentation:
https://medium.com/@dickareynaldisiahaan/viper-architecture-in-swift-building-robust-ios-apps-ed30d673d459
https://developer.apple.com/documentation/swiftui/navigationview

📷 Screenshots (Optional)

The content and scope of this PR do not accurately reflect the relevant changes and file modifications. It is imperative to thoroughly review the associated work to ensure its correctness and alignment with the project requirements.
Please review and refine the submitted changes accordingly to ensure alignment with the goals of the project. This is essential for progressing effectively. @beyzanuravsar
Where is your changed files?

Changed files added. PR edited. @gurkanfikretgunak


query params will get escaped accidentally

First of all, thank you for building this amazing tool.
I am trying with some Google API, and I realized if the request path contains query params (e.g. ?format=metadata), it will get escaped by the Handlebars template at this line https://github.com/jrmdayn/googleapis-batcher/blob/45f73fe317638556c88183745ebf11a438666179/src/makeMultipartMixedRequest/handlebarsTemplates.ts#L16
which will result in a request failure.
My temporary fix is changing {{path}} to {{{path}}}, but I am not an expert of Handlebars, so not sure if this has any side effect, but this change did fix my issue.

thank you @jrmdayn , works fine for me 👍


Feature Request: Support for Session Affinity

Is your feature request related to a problem? Please describe.
I have experienced a problem with a customer implementing Azure Container Apps, as a solution for migrating the entire environment of Web applications from Docker Containers to Azure.
However, one of the problems that I have encountered when working with multiple replicas and Auto scale in Container Apps is authentication failure since this application in question is an NGINX and PHP-FPM that uses an authentication Forms and every time a user connects and is with multiple replicas the process fails, only when it returns to a single replica does it work again.
Describe the solution you'd like.
I believe what will actually solve this scenario will be the use of Session Affinity.
Describe alternatives you've considered.
We are considering not migrating this environment to Azure using Container Apps due to this limitation

@maiaacademy We are working on adding support for session affinity to Container Apps. Initially, it’ll use an http cookie to route clients back to their previous replica and available only in single revision mode. Will this work for your scenario?

It will help, because we depend on this feature to migrate to Azure Container Apps.
Would you have an estimated date to pass on to the customer?

This item is on our roadmap, you can track it at #590. I'm not sure what the estimated date is yet.

@maiaacademy Estimated time for public preview is by end of Q1 (End of march) :)

This is available for single revision mode. If you also need session affinity for multiple revision mode as well, please open a separate issue.


[Bug] Tabs shaking when there's a lot of them opened

Sanity checks (must complete)

[X] I have read and followed the installation instructions in the README
[X] I have not modified the userChrome.css file
[X] I have tested the latest release or commit on master

Describe the bug
When opening multiple tabs to the point that they need to shrink, they start shaking a lot.
To Reproduce
Steps to reproduce the behavior:

Open multiple tabs.
See issue

Video
https://i.imgur.com/i3X31ho.gifv
System info

OS: Windows 10
Firefox version: 75.0

Unable to reproduce

OS: Windows 10
I can confirm this behavior but only when I open the customization menu. The shaking is essentially the switching of the tabs into overflowing and out. Therefore I can only reproduce it between 6 and 21 tabs (including the customize Firefox tab). Below 6 the tabbar isn't full and above 21 the tabs overflow anyway.

I'm able to reproduce this whenever I move the New Tab button away from the default position. The tabs begin to "shake" as described.
Release: MaterialFox-76.2

I'm also able to reproduce this on the latest release (MaterialFox-76.2):

For me, commenting out the
#tabbrowser-tabs[overflow] .tabbrowser-tab[last-visible-tab]:not([pinned])
{
	margin-inline-end: 8px !important;
}

block in tabbar.css here seems to fix the issue.

Had the same issue, @rojidev 's workaround worked like a charm

https://github.com/muckSponge/MaterialFox/pull/242
@rojidev I'm not sure as to what exactly this code is intended for (i.e. What are the side effects of commenting it out), any ideas?

#tabbrowser-tabs[overflow] .tabbrowser-tab[last-visible-tab]:not([pinned])
{
	margin-inline-end: 8px !important;
}

@KhushrajRathod I had a quick look into it and that block simply adds a margin to the end of the visible tabs when they're overflowing:

The top being with the block commented out, and the bottom with margin-inline-end: 7px !important instead of 8px. Interestingly changing it to 7px seems to be working fine for me, the tabs don't shake anymore.
Looking at the browser content toolbox, it seems like it's an issue with the tabs being marked and unmarked as 'overflowing' constantly when it's set to 8px (you might have to open this image fully to actually read it):

The tabs element (#tabbrowser-tabs) has an "overflow" tag being set to true and unset, same with the arrowscrollbox element (#tabbrowser-arrowscrollbox). The last tab has the
#tabbrowser-tabs[overflow] .tabbrowser-tab[last-visible-tab]:not([pinned])
{
	margin-inline-end: 8px !important;
}

style being constantly added and removed. Not entirely sure of the actual root cause, but changing it to 7px instead seems to work fine for me so that might be a better idea instead of commenting the block out completely.

@rojidev Can confirm it works with 7px, I'll update the PR now


Caches of view containers, views and viewlets are not getting cleared

When I checked my view container, views and viewlet locations caches, I see there are lot of generated view containers which are redundant and not cleared. They are not getting cleared even after resetting all view locations

Move views, view containers around, say,

move view to another view container
move view to its own new view container

Reset all view locations

Open dev tools console and run the VS Code command Log Storage Database Contents
Cached view container, views and viewlet locations are not cleared.
@sbatten FYI

I'm not sure exactly what to look for here. @sbatten are you able to verify this?

Removing verified label because not sure whether I verified the issue properly.
Before resetting the view locations, and after resetting the view locations, the size of the storage database stayed the same in both cases.

To verify:

Open VS Code using fresh user data dir and open VS Code repo
Move time line view to sidebar, Move outline views to panel.
Run Developer: Log Storage Database Contents
Check following keys in global storage

workbench.activity.pinnedViewlets2 - Generated container (id containing UUID) exists
workbench.activity.pinnedPanels - Generated container (id containing UUID) exists
views.cachedViewContainerLocations - Has two entries
views.cachedViewPositions - Has two entries
There are two storage keys for generated containers workbench.views.service.sidebar.${uuid}.state.hidden

Run the command Reset View Locations
Make sure above two views got reset to their original locations
Check following keys in global storage

workbench.activity.pinnedViewlets2 - Does not container generated containers
workbench.activity.pinnedPanels - Does not container generated containers
views.cachedViewContainerLocations - Has NO entires
views.cachedViewPositions - Has NO entires
There are NO storage keys for generated containers workbench.views.service.sidebar.${uuid}.state.hidden

@sandy081 I cannot find workbench.activity.pinnedPanels after running the command, can you check your stepsß

It was workbench.panel.pinnedPanels


add missing commas in subaru/values.py

comma.ai was missing some commas.
Bug fix
Description
Without the comma, python does string concatenation across lines.
Verification
Nothing beyond the automated tests. If you'd like someone with a Subaru to test this, please let me know.

values.py has plenty of types of encoding. \x00 \000 \a and ascii characters. Perhaps standardizing on all \x00 encoding would be nice.
I should remember how to run the tests locally instead of pushing to this PR to trigger the github workflows.

Nice catch. The linter should catch this after #23513.


Fix token permission code scanning alerts

Fixes the following code scanning alerts:

https://github.com/transparency-dev/trillian-tessera/security/code-scanning/4
https://github.com/transparency-dev/trillian-tessera/security/code-scanning/30
https://github.com/transparency-dev/trillian-tessera/security/code-scanning/31
https://github.com/transparency-dev/trillian-tessera/security/code-scanning/32
https://github.com/transparency-dev/trillian-tessera/security/code-scanning/33
https://github.com/transparency-dev/trillian-tessera/security/code-scanning/34
https://github.com/transparency-dev/trillian-tessera/security/code-scanning/35

@AlCutter gentle ping :)


Dynamically change ID

If I have a Node, and I put another one before the one that was already there
the Node that was already there, goes with ID = 1, when I add a new Node it goes with ID = 2, but this new node I put before Node 1
that is, you would have to change the order in the IDs automatically
Is there a way to do this?

What do you mean add it before?
The order is correlative.
If you want you can generate the id's with UUID. Adding:
editor.useuuid = true;


One event only in some hours

Hello,
We are trying to using github data for building information flow simulation models and noticed that for the following hours in github archive, there is only one event recorded.
2015-01-06-4
2015-01-05-20
2015-01-07-13
2015-01-08-2
2015-01-09-11
2015-01-09-9
2015-02-03-16
Not sure if this can be fixed as these are 'ancient' data, but thought will give a heads-up.
Thank you for the great work and kindly sharing this valuable data.

Thanks for reporting this. Unfortunately nothing we can do about it at this point. :(
I'm sure you'll find a few other gaps as well.. Some of these may be due to maintenance on our side, but most of the time this is due API downtime @ GitHub.

Thank you for the prompt response. Just wanted to try my luck.:)


Add CraftCMS setup to documentation

ISSUE TYPE

Documentation

SUMMARY
Add CraftCMS setup to documentation
Goal
Be able to easily set up Craft CMS

I've just added a Craft CMS install - with asset building done by Blendid (https://github.com/vigetlabs/blendid) on a Windows 10 machine - no real difference to those other frameworks you have listed - i actually followed your WP one (https://devilbox.readthedocs.io/en/latest/examples/setup-wordpress.html) ...
winpty ./shell.bat
mkdir craft-demo
cd craft-demo
yarn init (https://github.com/vigetlabs/blendid)
yarn add blendid
yarn run blendid -- init-craft (https://github.com/vigetlabs/blendid/wiki/Craft-Setup)
exit exit
... back out of container (as i'm using Craft 2.6 so it's only available as a downloaded ZIP) and download Craft 2,6 from https://craftcms.com/support/download-previous-versions

add contents of downloaded '/craft/' to '/craft/'
add contents of downloaded '/public/' to '/public/'

... also do a few misc tasks whilst out of container ..

Add to hosts ("<IP_ADDRESS> craft-demo.loc")
Update browserSync.proxy with dev URL (craft-demo.loc) - never got browserSync.proxy working!
Add Blendid helpers to templates (https://github.com/vigetlabs/blendid/wiki/Craft-Setup)

... back into container ...
winpty ./shell.bat
cd craft-demo
ln -s public/ htdocs (Symlink /public/ folder)
mysql -u root -h <IP_ADDRESS> -p -e 'CREATE DATABASE craft_demo;'
... test compiling of assets ..
yarn run blendid
exit exit
... out of container ...

http://craft-demo.loc:8080/admin (install Craft)
activate 'Rev' plugin (https://github.com/vigetlabs/blendid/wiki/Craft-Setup)
confirm everything works - http://craft-demo.loc:8080/

I will add it and let you know in this issue.

Documentation for Installation is done via composer

Sorry dont follow?

I meant instead of using yarn to install CraftCMS, I am using composer (as they also recommend this method on their documentation).
Docs will be available in ~1 hour. I let you know. Feel free to address any issues with it then.

OH yeah absolutely - sorry my particular requirement was using an older version of Craft as in that procedure i added above - but yeah Craft 3 - perfect

https://devilbox.readthedocs.io/en/latest/examples/setup-craftcms.html

Seriously amazing how quick you evolve Devilbox!
On Wed, Aug 8, 2018 at 11:36 AM, cytopia<EMAIL_ADDRESS>wrote:

https://devilbox.readthedocs.io/en/latest/examples/setup-craftcms.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cytopia/devilbox/issues/341#issuecomment-411362707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/An9R4m2uA0dYm5HTpb6mxfWeWRlJKbxvks5uOr9HgaJpZM4Vx5yv
.


(React SDK): Forward refs in withOptimizely HoC

Implement ref forwarding in withOptimizely HoC.

@jamesopti @mikeng13 I refactored this a little and combined it with hoisting statics. Moved into a separate PR: https://github.com/optimizely/fullstack-labs/pull/32


Feature request: add a dropdown to select the json file to use

Thanks for your very nice Styles custom node, I have it in use with all my workflows.
Since the update, all json files load. This can be convenient, but it also can lead to a very long dropdown to select a style ... too long atually to have good oversight
I know I can change and shuffle the json files, and there also is the search field, but I had this idea if maybe it would be possible to add a dropdown selector, where one can choose which styles show up (which json file will be used) in the second selector? And there can also be an entry that says 'all'. It would be a bit more convenient than the search field.
Greetings, Rudy.

This has been requested before but there are no built in mechanism in ComfyUI to handle this. If you have found a workaround for this in another node I might have a look and see if it's worth including.

Thanks for your reply. I was afraid of that, I bet the json files load at startup and there's no mechanism to make this dynamic. Well ... I think I'll cretae a json file with my personal favorite styles as a workaround and swap files if I need more styles.

Is that what you want? The author ported fooocus's style selection list and preview feature, which is still being further optimized by the author. It does not affect the current use.
https://github.com/yolain/ComfyUI-Easy-Use.git


Using redux-offline with Vue

Hello,
Is there a guide to use this library with Vue?
I read on the blog post that Vue is supported, but i can't find a mention or a guide for this on the docs.
I'm using Vue with Vuex (a state manager like Redux). It's possible to use this library with Vuex?
Thanks, and great work!!!

@ibarral I have not tried to use this library with Vue, but my assumption was that you'd be able to use a Redux store with Vue with or without Vuex.
In retrospect, the createOfflineStore API makes this hard. Once I'm able to land https://github.com/jevakallio/redux-offline/pull/17, I think it should get easier.
Is there a simple Vuex sample repo I could try this in?


Improving the "the url should match" step

Hello,
In the default Mink step, there that one
@Then /^the url should match "(?P<pattern>(?:[^"]|\\")*)"$/

Problem:
When I use it, with a valid regular expression, the test fails.
Then the url should match "#reservation/abonnes/modification/\d+#"       # FeatureContext::assertUrlRegExp()
    Current page is "/default/reservation/abonnes/modification/id/21474836000814/", but "/" expected

This test should pass, as the regex is #reservation/abonnes/modification/\d+# and the current session url is /default/reservation/abonnes/modification/id/21474836000814/.
Debug
There a validation on the inputed pattern in order to check if the pattern is a regex. If not, the pattern is considered to be a full url, and compared like so. Code here
Problem is that "something that looks like a regex" for Mink is something that match this regex : /^\/.*\/$/, so when I want to check that I go to a url like example.comreservation/abonnes/modification/34674/, using this step:
Then the url should match "#reservation/abonnes/modification/\d+#"

Mink thinks I'm giving him a full url, instead of a regex, and send me to this step:
@Then /^(?:|I )should be on "(?P<page>[^"]+)"$/

This step perform a string comparaison between the url and the pattern. The steps obviously fail then, even if the current url of the session indeed match the pattern example.com/reservation/abonnes/modification/34674/
$: php -r "var_dump(preg_match('#reservation/abonnes/modification/\d+#', 'example.com/reservation/abonnes/modification/34674/'));"
int(1)

Solution
Changing the way this steps works, by completely removing the "Pattern is not a pattern but a url" detection, leaving the end user choosing between "Is the current url this one" and "Does my current url looks like this regular expression".
PS: No PR attached for now, will do it after discussing.

Fixed with #174

Great, thank you =)
--
Clément Herreman
Le vendredi 13 janvier 2012 à 13:25, Konstantin Kudryashov a écrit :

Fixed with #174

Reply to this email directly or view it on GitHub:
https://github.com/Behat/Mink/issues/145#issuecomment-3479014


Some non-congruity between save and load.

This problem is mostly because the loading mechanism is overly dumb. When you load a file with jumps it calls most all the jumps to be actual cuts and unsewn. But, if bookended between two stitches the obvious consequence is a longer than usual jump with that jump location between them. While the EmbroiderIO functionality is correct and simply preserves and correctly writes everything the interpretation of this loaded data is too naive and as such appears to truncate the data in error.

This problem was corrected in the update for pyembroidery by interpolating the trims in a manner that is correct with regard to the machine type as well as giving options to permit that. So DST readers accept an input with a criteria for how many jumps equals a trim and then reads the file with the default value of 3. This is similarly done for JEF files etc.
This error will be fixed upon the completion of EmbroidePy/EmbroideryIO#11


Safari 11 has been released

Safari 11 has been released
Highlights:

WebRTC
Media Capture API
WebAssembly
Resource Timing
Drag and drop events on iOS
Variable fonts
CSS stroke support

Might make a PR tonight if I can find the time...

My bad, it's already listed I see.


Ensure that fill outputs correctly tile on Bricks and Uneven Bricks 2

As discussed this fixes the tiling on the Fill outputs.

This resolves https://github.com/RodZill4/material-maker/issues/415


FromPrimitive f64 trait casts to i64?

https://github.com/rust-num/num-traits/blob/bfd62d4638392deff20907ad078d2b1521aa45ba/src/cast.rs#L355
also
https://github.com/rust-num/num-traits/blob/bfd62d4638392deff20907ad078d2b1521aa45ba/src/cast.rs#L75
Is this right?

Those are the default implementations -- specific implementations should override that to work with floats directly, if they can do something better.
However, the first should probably be more like i64::from_f64(n).and_then(Self::from_i64) so it can handle overflow correctly -- at least when #12 is fixed.


feat: add more fields to AssetInfo type

Closing as superseded by https://github.com/maestro-org/haskell-sdk/pull/69.


tests: benchmarks: move pthread_pressure to benchmarks/posix

The pthread_pressure test was not a typical test per se. It was a benchmark in search of the proper home.
Let's move it to the correct place in the Zephyr tree, add a doc, and provide some reporting.
Currently, k_threads out-perform pthreads by almost a factor of 2. The theoretical maximum performance of pthreads would be at parity of k_threads, since pthreads are a wrapper around kernel threads. It would be great to reduce the gap.

I guess technically, with assertions enabled, this would become a stress test rather than a benchmark.
Any thoughts about how that should be organized @peter-mitsis ?

Any thoughts about how that should be organized?

I don't have anything new to offer/suggest; I'm good with how this has been laid out.


can't handle  tag

Hello,
I've tried to transform html content to contentState
Everything goes fine but
The output result shows there's not any image element but only '~' string
Would you take a look and fix it?
Thanks a lot!

+1

It works if you wrap the  into a
. I think there should be a way to use just  without a

I'm not entirely sure what the expected behavior is when encountering an .

@sergiodxa How did you get it to work by wrapping it in a
 element. It didn't work for me.
None of these work for me:
let html = '

'
// let html = '

'
// let html = ''
// let contentState = stateFromHTML(html)
let editorState = EditorState.createWithContent(contentState)

Up


[loc][Query][AzureStorageExplorer] Localizability of 0; "LabelAriaEditEntityButton"

Hi,
please help localization team to answer question from translator.
In case translator is not sure about context/meaning/localizability of string we raise a question to Core team.
Please re-assign back to use in case you are not the right contact person or you can´t assign to a proper person.
Can you help, please?
Thanks!
Source:
%s property edit entity
File Name:
loc\en\src\Standalone\resources\EntityEditorDialog.json
Resource ID:
0; "LabelAriaEditEntityButton"
Query:
Would you please confirm if "edit" acts as a noun or verb? In other words, can I translate this string as "editing of entity" where "entity" is an object?

There is no string with that ID in Activities. Are you talking about EntityEditorDialog.json?

Corrected path. Yes you are right

I should probably change the ARIA label for this button. The label here is probably best interpreted as "%s property edit value button" or "edit %s property value button". So, yes, "edit" here is a verb.

@PDostalek Does that answer your question?

@PDostalek Do you have everything you need for translation now?

Closing due to inactivity.


Missing KPIs in Ticker.info

Hello,
Thank you a lot for your great work.
Working with yfinance I realized than some KPIs in Yahoo Finance website are not available in Ticker.info. Could you please consider to add them ?
Summary:

Beta (3Y Monthly) : the beta3Year field returns None
1y Target Est

Statistics:

Operating Margin (ttm)
All KPIs in Management Effectiveness
All KPI in Income Statement
All KPI in Balance Sheet
All KPI in Cash Flow Statement
Avg Vol (3 month)
Avg Vol (10 day)

Profile:

All KPI in Key Executives

Thank you in advance,
Acudo

Could you please provide a code example of what is the issue?


Improve indentation and whitespace

@MathiasReker Sorry but I must close this pull request. It doesn't bring any value in fixing a bug or implementing a feature.


result of every iteration in trust-constr

I want to save result of every iteration in trust-constr
Reproducing code example:

Nfeval=1
def callbackF(v):
    global Nfeval
    print '{0:4d}   {1: 3.8f}   {2: 3.8f}   {3: 3.8f}   {4: 3.8f}'.format(Nfeval, v[0], v[1], objective(v), cons_f(v))
    Nfeval += 1
    out_file = open('ite_objective.txt', 'a')
    out_file.write("{}\n".format(objective(v)))
    out_file.close()
    out_file = open('ite_cons.txt', 'a')
    out_file.write("{}\n".format( cons_f(v)))
    out_file.close()

Error message:
callbackF() takes exactly 1 argument (2 given)
However this works well in SLSQP. How can I fix this to save results of each iteration?
Also, I think I may face the same problem as  SLSQP #12949, Can trust-constr handle similar problem in #12949
--> Scipy 1.2.0,

I believe this is addressed in the minimize documentation:

Please submit other usage questions on Stack Overflow; GitHub is for feature requests and bug reports.


docs: Fix a few typos

There are small typos in:

flask_admin/contrib/sqla/ajax.py
flask_admin/contrib/sqla/tools.py
flask_admin/static/bootstrap/bootstrap4/js/bootstrap.bundle.js

Fixes:

Should read otherwise rather than othwerise.
Should read occurring rather than occuring.
Should read explicitly rather than explicity.
Should read contains rather than containes.

Semi-automated pull request generated by
https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Please remove the vendor library changes in bootstrap4, closing until then.


Running Queries doesn't show data in Instance column on drill down from Slow Queries

If you click the session id column on the slow queries tab to view the available running query snapshots for the session, the Instance column is visible but doesn't contain any data.

Fix included in 2.22.6 🚀


Fix #411: Cannot attach debugger to interactive window

Propagate debug options (that make sense in that context) to the REPL, and then from the REPL to the main debugger script, when using $attach command.

:+1:

+1


use --all-features for generating our coverage report

 Test Coverage in features richtig berechnen lassen von coverall

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage increased (+4.6%) to 83.633%

Files with Coverage Reduction
New Missed Lines
%

services/src/datasets/external/nature40.rs
1
88.06%

services/src/bin/main.rs
2
0%

services/src/pro/datasets/external/sentinel_s2_l2a_cogs.rs
2
79.55%

Totals

Change from base Build<PHONE_NUMBER>:
4.6%

Covered Lines:
20546

Relevant Lines:
24567

💛  - Coveralls


Active module causes entire companion install to lag

Running latest release (2.2.0) on Mac.  Whenever an instance of rsc is enabled, all button presses in companion have a 1-3 second delay, and feedback/variable display is slowed or fails. This is not limited to rsc control, but every other button press, even just page changes.

Very peculiar. I just took a look at the module code, and it has not had any significant changes in 2 years. I'm wondering if there could possibly be a network issue or something else causing a hangup. Can you try nuking your setup and starting fresh, to rule out some config issues?

I’ll give it a go when I’m back on site tomorrow.  I wondered about
networking being an issue (there’s a new Cisco based rollout which has not
gone well) but i had the same storms when i tried out with no network
access.
I’ll also try exporting my setup and putting it on a PC and see what
happens.
On Tue, 5 Apr 2022 at 13:34, Joseph Adams @.***> wrote:

Very peculiar. I just took a look at the module code, and it has not had
any significant changes in 2 years. I'm wondering if there could possibly
be a network issue or something else causing a hangup. Can you try nuking
your setup and starting fresh, to rule out some config issues?
—
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-irisdown-remoteshowcontrol/issues/4#issuecomment-1088649146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5KABPC6WWO4EMBD6EEFOLVDQXMVANCNFSM5SSQJXCQ
.
You are receiving this because you authored the thread.Message ID:
<bitfocus/companion-module-irisdown-remoteshowcontrol/issues/4/1088649146@
github.com>

--
Cheers,
Nige


[Feature] Add Invoice Service

Documentation : https://www.synnexcorp.com/esolutions/wp-content/uploads/sites/63/2023/04/XML-Invoice-Spec-v1.01.pdf


Take 2 on adding CI

Setting up CI in a new PR
last PR didn't copy the files over correctly

It looks like we have to get rid of msmbuilder for the testing environment to work. I will finish addressing the clustering PR #22 and then a lot of these types of issues should be solved.

That sounds like a great plan.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@905232a). Click here to learn what that means.
The diff coverage is n/a.

It's working now - I'll merge then.


[flux2] support containerName for deployments can be customised

Is your feature request related to a problem ?
Currently all containerNames in a flux deployment/pods are called manager. As we are using datadog as a monitoring tool its hard to figure out which container has maybe some resource issues because they are all named the same.
Describe the solution you'd like.
We would like to have the option to configure the name of the container in the helm_release like:
helmController:
  container:
    name: <some-container-name>
sourceController:
  container:
    name: <some-container-name>
etc...

Describe alternatives you've considered.
None
Additional context.
No response

@stefanprodan I don't understand the connection between the flux upstream and the name of the Kubernetes resources like container name. Could you elaborate this a bit more? Is it realy not possible to have an option of configuring different names and having the default as manager?


bump substrate to polkadotv0.9.30

Summary of changes
Changes introduced in this pull request:

bump substrate to polkadotv0.9.30

Codecov Report
Base: 50.44% // Head: 50.42% // Decreases project coverage by -0.02% :warning:

Coverage data is based on head (0e6ec3b) compared to base (31e0f27).
Patch coverage: 9.52% of modified lines in pull request are covered.

:exclamation: Current head 0e6ec3b differs from pull request most recent head 5a8a32e. Consider uploading reports for the commit 5a8a32e to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #273      +/-   ##
==========================================
- Coverage   50.44%   50.42%   -0.03%
==========================================
  Files          55       55
  Lines        2014     2013       -1
==========================================
- Hits         1016     1015       -1
  Misses        998      998

Impacted Files
Coverage Δ

client/tests/utils.rs
0.00% <0.00%> (ø)

pallets/asset-registry/src/lib.rs
81.86% <ø> (ø)

pallets/hasher/src/lib.rs
84.00% <ø> (ø)

pallets/hasher/src/weights.rs
0.00% <0.00%> (ø)

pallets/key-storage/src/lib.rs
37.50% <ø> (ø)

pallets/key-storage/src/weights.rs
0.00% <0.00%> (ø)

pallets/linkable-tree/src/lib.rs
88.42% <ø> (ø)

pallets/mixer/src/lib.rs
70.09% <ø> (ø)

pallets/mt/src/lib.rs
90.00% <ø> (ø)

pallets/mt/src/weights.rs
0.00% <0.00%> (ø)

... and 19 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix getting default queue settings

This is follow-up for #197
Problem description
Queue check doesn't work properly when you name your queue other than default.
Problem details
The issue is that in laravel the default queue connection is stored as config('queue.default'), but this package calls config('queue. driver'). As a result, the package cannot find the connection config and selects default queue as one to check:
protected function getDefaultQueue($connection)
{
    return config("queue.connections.{$connection}.queue", 'default');
}

Thanks!


Can not open the Codewars website

Dear Codewars Team,
I'm Student Programmer
In this week I trained for some katas for python but today when I opened the website it shows me 5xx: Server Error
In the normal the expected behavior is to open my account dashboard or my last kata that I trained
Screenshot of what happened

I'm using Chrome Browser

OS: Windows
Browser Chrome
Version 105.0.5195.102

Duplicate issue of #2807
Please look for already existing issue before opening a new one.

Ok Thanks!


pull request for e2e test at 11/20/2016 19:26:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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


Wrong output with other backbone networks

Hi there, thanks very much for this nice work. However,  since the original fcn8_resnet is large,  when I tried the LCFCN loss with other backbone networks such as Unet and LinkNet in this link https://github.com/ternaus/robot-surgery-segmentation/blob/master/models.py or lightweight mobilenet,  the loss seems to be decreasing normally, but the predict output count is always 1, please refer to the figure attached. I debugged the codes and can't find out what's wrong. Can you give me any tips? Thanks very much!

Is the output of these networks binary or multi-class?

@IssamLaradji The output is multi-class

Ah that explains it, multi-class is not supported well yet. I will look into it

Okay, thanks a lot!

Okay, thanks a lot!


[WIP] Replace revision build_ methods with services

This PR is to provide a place for discussion about what I've got so far.
I've still got the unit tests to sort out, but it makes sense to look at the
approach together before I spend time on those...
Previously our revision models had a build_revision_update method to
handle creating a new revision tree when certain attributes change.
Having the versioning logic directly on the models makes it cumbersome
to figure out which attributes are changing; in particular, it's not
compatible with the changed_attributes feature provided by ActiveRecord.
This makes it hard to answer questions like 'has the lead image
changed?', which is necessary in order to correctly redirect the user.
This extracts the versioning logic into services, which provide changed?
and changed_attributes methods to better support our controllers. I've
used inheritance to reduce the amount of duplicated versioning logic for
sub-revisions like Image::FileRevision and Image::MetadataRevision.
updater = BaseUpdater.new(<revision>, <user>)
  .track_attributes(%i[title summary blah])

next_revision = updater.assign_attributes(title: "new title")

do_something if updater.changed?
do_something_else if updater.changed_attributes.key?(:title)

Some of the actions on (lead) images require custom versioning logic to
figure out what the new values of attributes should be. It seems best
to have this logic in the ImagesController so that both it and the
controller can make use of the updater methods. Hopefully this will be
refactored as part of a larger overhaul of the controllers.

@kevindew the description doesn't really cover one decision point, as I feel it's more minor, but I'd like to discuss it here: the choice between specifying ignored attributes vs. allowed attributes.
The first thing I noticed is that we already take the 'allowed attributes' approach when assigning attributes to sub-revisions, using Hash#slice. I don't think there's a simple way to get the same result using the 'ignored attributes' approach, and it's confusing to use 'allowed attributes' when assigning stuff vs. 'ignored attributes' when we're checking if the revision has changed.
The second problem I had with the 'ignored attributes' approach was a discrepancy between the attribute keys we use for assignment and the ones we get when generating a list of attributes that have changed. For example, we (have to) use 'lead_image_revision' to assign a new lead image (without an id); taking an 'ignored attributes' approach means we only get to check 'lead_image_revision_id', which doesn't accurately reflect the change ( =>  vs.  => ). On the other hand, using an 'allowed attributes' approach with #public_send allows us to inspect 'virtual attributes' like image_revisions, which resolves the discrepancy between assign/changed and yields accurate results from changed_attributes.

Thanks @benthorner for putting together and writing it up. It's looking really promising. 👍
First thing I'd like us to do with this is split this out from the underlying story: https://trello.com/c/JcQEznco/605-add-checkbox-to-select-unselect-a-lead-image-on-metadata-page since we're probably in a position now where we can complete the story this sprint without needing to merge these changes.
Things where I think this is going well:

I like having that we have the two classes RevisionUpdater and ImageRevisionUpdater
Using the updater.changed? is nicer than the equality
The updaters feel natural places for other common questions

Areas where I feel like we could use more work/regressions:

It's a bit strange to be instantiate a Base* class - since that is terminology commonly used to reference an abstract class in Ruby due to it's lack of the feature
The frequent use of super in methods on RevisionUpdater and ImageRevisionUpdater makes them harder to understand than the code they replace - basic suggestion would be that these don't inherit
It seems a bit strange we've moved more stuff to the ImagesController
Assuming you haven't got to it yet after our discussion but do still want to see ActiveRecord type casting
Feel like the move to controller methods on ImagesController is something of a complexity regression, since that adds more code to an already large multi-responsibility entity

Re: attribute whitelist vs blacklist
So maybe it got lost in various other discussions, but the concern I was trying to iterate with the approach of slice and ignore was that if we pass in keys that aren't understood then the whitelist approach will just take things it understands and discard others and therefore concealing changes. That was the aspect that I was concerned about, I notice even looking at current Revision and Image::Revision classes that this is possible which is an oversight of mine 😞 but that's the thing I wanted to achieve with the whitelist/blacklist part.
So in a nutshell I don't really mind which approach we take there but it'd be good if something blew up if unknown attributes are passed in.
Finally, apologies for a big question here, but something I'm unsure of is what the goal/success criteria for this work is?

Superseded by https://github.com/alphagov/content-publisher/pull/853.


Terminal icon colors not working in panel

Testing #127192
The terminal icon colors aren't showing in the panel:
https://user-images.githubusercontent.com/31675041/123832490-a0534980-d8c2-11eb-80b2-41a2761a3bce.mp4

Was working off of an outdated version, closing.


automaticDataCollectionEnabled' is missing in type 'FirebaseApp'

Version info

Angular: 5.2.9
Firebase: ^4.13.0
AngularFire2: ^5.0.0-rc.6.0
**Other (e.g. Ionic/Cordova, Node, browser, operating system):**Ionic/Cordova
How to reproduce these conditions
package.json
"dependencies": {
    "@angular/common": "5.2.9",
    "@angular/compiler": "5.2.9",
    "@angular/compiler-cli": "5.2.9",
    "@angular/core": "5.2.9",
    "@angular/forms": "5.2.9",
    "@angular/http": "5.2.9",
    "@angular/platform-browser": "5.2.9",
    "@angular/platform-browser-dynamic": "5.2.9",
    "@ionic-native/core": "4.7.0",
    "@ionic-native/splash-screen": "4.7.0",
    "@ionic-native/status-bar": "4.7.0",
    "@ionic/pro": "1.0.20",
    "@ionic/storage": "2.1.3",
    "angularfire2": "^5.0.0-rc.6.0",
    "firebase": "^4.13.0",
    "ionic-angular": "3.9.2",
    "ionicons": "3.0.0",
    "promise-polyfill": "^7.1.2",
    "rxjs": "5.5.8",
    "sw-toolbox": "3.6.0",
    "zone.js": "0.8.26"
  },
  "devDependencies": {
    "@ionic/app-scripts": "3.1.9",
    "typescript": "~2.6.2"
  }

Debug output
Errors in the JavaScript console
typescript: node_modules/angularfire2/firebase.app.module.d.ts, line: 10
            Class 'FirebaseApp' incorrectly implements interface 'FirebaseApp'. Property
            'automaticDataCollectionEnabled' is missing in type 'FirebaseApp'.

       L9:  export declare const FirebaseAppConfigToken: InjectionToken;
      L10:  export declare class FirebaseApp implements FBApp {
      L11:      name: string;

Expected behavior
Ionic compile would complete with any errors

Actual behavior
Because automaticDataCollectionEnabled is missing in type 'FirebaseApp', error occurs.

This issue is related to latest firebase update https://github.com/firebase/firebase-js-sdk/commit/7c1aa4470c0f5474b11fe57ada4edff65ed90adc
Temporary solution is to set version of firebase in your projects package.json to 4.12.1
"dependencies": {
     "firebase":"4.12.1",
     "angularfire2":"^5.0.0-rc.6"
}

@Tamango92 Does he work for you? I trying your solution and it doesn't working

I have installed "@firebase/app": "^0.1.10" and it's working

@Tamango92 actually I was using firebase 4.12.1. So it didn't work for me.
But I would solve this issue @zverbeta 's solution.
Thank you.
#1572 and I sent PR about this.

It worked for me, but with ‘npm cache clean’ before installing

I can confirm this worked for me as well.

Compiling successfully but, getting issue with Google Authentication Provider
ERROR TypeError: Cannot read property 'GoogleAuthProvider' of undefined

Simple 1-line patch for lazy people like 😊
sed -i.bak 's|^}$|    automaticDataCollectionEnabled: false;}|' node_modules/angularfire2/firebase.app.module.d.ts

@Tamango92 Downgraded, but facing more issues

npm cache clean

"dependencies": {
     "firebase":"4.12.1",
     "angularfire2":"^5.0.0-rc.6"
}

Now I'm asked to install all @firebase modules, for example:
[11:08:28]  typescript: node_modules/angularfire2/firestore/observable/fromRef.d.ts, line: 1
            Cannot find module '@firebase/firestore-types'.

       L1:  import { DocumentReference, Query, QuerySnapshot, DocumentSnapshot } from '@firebase/firestore-types';
       L2:  import { Observable } from 'rxjs/Observable';

I have seen this change already merged so we need to wait for a new release of angularfire2 on npm.
In the mean time, just update @firebase/app": "0.1.10". It works for me.

for me this config work:

"firebase": "^4.13.1",
"angularfire2": "^5.0.0-rc.6",
"@firebase/app": "0.1.10",
"@firebase/auth": "0.4.1",
"@firebase/database": "0.2.1",
"@firebase/firestore": "0.3.7",
"@firebase/functions": "0.1.0",
"@firebase/messaging": "0.2.3",
"@firebase/polyfill": "0.3.0",
"@firebase/storage": "0.1.8",
"ngrx-store-freeze": "^0.2.2",

Found this fix here: https://stackoverflow.com/questions/49963223/property-automaticdatacollectionenabled-is-missing-in-type-firebaseapp
"export declare class FirebaseApp implements FBApp {
name: string;
options: {};
automaticDataCollectionEnabled: boolean; // this is the missing line
auth: () => FirebaseAuth;
database: () => FirebaseDatabase;
messaging: () => FirebaseMessaging;
storage: () => FirebaseStorage;
delete: () => Promise;
firestore: () => FirebaseFirestore;
}
also add @firebase/app
npm i -S @firebase/app"

Same issue solved as suggested above...
At first, I had :
"dependencies": {
     "firebase":"^4.13.1",
     "angularfire2":"^5.0.0-rc.6"
}

Then after visiting here I did :

npm uninstall firebase
npm clean cache --force
npm install<EMAIL_ADDRESS>
As a result, it all works well for me. I got :
"dependencies": {
     "firebase":"^4.12.1",
     "angularfire2":"^5.0.0-rc.6"
}

It is worked for @cicode225 ,Thanks a lot
Same issue solved as suggested above...
At first, I had :
"dependencies": {
"firebase":"^4.13.1",
"angularfire2":"^5.0.0-rc.6"
}
Then after visiting here I did :
npm uninstall firebase
npm clean cache --force
npm install<EMAIL_ADDRESS>As a result, it all works well for me. I got :
"dependencies": {
"firebase":"^4.12.1",
"angularfire2":"^5.0.0-rc.6"
}

@cicode225  thanks it work

@cicode225  Thank you!!! solved mi problem

@cicode225 works fine thanks.....but i had to use 'npm cache clean --force' :)

Thank you cicode225  .... This saved my work

@cicode225 nice!


DTLS server does not respond to retransmitted "Client Hello"

Version: 20af01d46ca4086f6b1339b67c15c81d8b4a040d (4 commits before OpenSSL_1_1_1p)
In order to reproduce the issue, use https://github.com/mniestroj/openssl/tree/reproduce-dtls-handshake-deadlock or just apply https://github.com/mniestroj/openssl/commit/b314ee46815c10d52c94f1f13afd67035edcb91e commit, which simulates dropping reply to first "Client Hello" packet (this means that client does not receive response to "Client Hello" and continues retransmitting it).
$ apps/openssl s_server -dtls1_2 -accept <IP_ADDRESS>:5684 -psk_identity mark-one-id@one -psk 3172306e6d406e -cipher PSK-AES128-CCM8 -nocert -security_debug_verbose
Using default temp DH parameters
ACCEPT

Security callback: Version=???: yes
Security callback: Version=???: yes
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 0 (s->statem.hand_state 0)
Don't send this message!
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)

Recurring comparing msg_hdr.seq 0 ... messages are printed whenever new retransmitted "Client Hello" message is received. Unfortunately openssl treats that message as invalid. It looks like handling of retransmitted "Client Hello" is not handled correctly.
mbedTLS based DTLS client was used, though it should be reproducible with any DTLS client.
See that "Client Hello" messages are visible in Wireshark as well:

This is quite severe bug, because restarting client (or starting new handshake) does not solve the issue and this means that there is persistent deadlock for such client. A workaround was developed, which seems to solve the issue: https://github.com/mniestroj/openssl/commit/18ad4353e8b5f35d05e742097e416b8d6a0d3f6d. After applying this workaround, DTLS server properly continues:
$ apps/openssl s_server -dtls1_2 -accept <IP_ADDRESS>:5684 -psk_identity mark-one-id@one -psk 3172306e6d406e -cipher PSK-AES128-CCM8 -nocert -security_debug_verbose
Using default temp DH parameters
ACCEPT
Security callback: Version=???: yes
Security callback: Version=???: yes
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 0 (s->statem.hand_state 0)
Don't send this message!
comparing msg_hdr.seq 0 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
special case for handling Client Hello retransmit 1 21
comparing msg_hdr.seq 1 s->d1->handshake_read_seq 1 (s->statem.hand_state 21)
Security callback: Version=???: yes
Security callback: : yes
Security callback: Shared Signature Algorithm scheme=ecdsa_secp521r1_sha512, security bits=256: yes
Security callback: Shared Signature Algorithm scheme=rsa_pkcs1_sha512, security bits=256: yes
Security callback: Shared Signature Algorithm scheme=ecdsa_secp384r1_sha384, security bits=192: yes
Security callback: Shared Signature Algorithm scheme=rsa_pkcs1_sha384, security bits=192: yes
Security callback: Shared Signature Algorithm scheme=ecdsa_secp256r1_sha256, security bits=128: yes
Security callback: Shared Signature Algorithm scheme=rsa_pkcs1_sha256, security bits=128: yes
Security callback: Shared Signature Algorithm scheme=ecdsa_secp521r1_sha512, security bits=256: yes
Security callback: Shared Signature Algorithm scheme=rsa_pkcs1_sha512, security bits=256: yes
Security callback: Shared Signature Algorithm scheme=ecdsa_secp384r1_sha384, security bits=192: yes
Security callback: Shared Signature Algorithm scheme=rsa_pkcs1_sha384, security bits=192: yes
Security callback: Shared Signature Algorithm scheme=ecdsa_secp256r1_sha256, security bits=128: yes
Security callback: Shared Signature Algorithm scheme=rsa_pkcs1_sha256, security bits=128: yes
Security callback: Shared Ciphersuite=PSK-AES128-CCM8, security bits=128: yes
comparing msg_hdr.seq 2 s->d1->handshake_read_seq 2 (s->statem.hand_state 26)
comparing msg_hdr.seq 3 s->d1->handshake_read_seq 3 (s->statem.hand_state 31)
-----BEGIN SSL SESSION PARAMETERS-----
...

@bernd-edlinger was recently looking at DTLS so perhaps he could comment?

That is a limitation of the s_server command.
It does only allow one single connection at a time.
Try to use the -timeout option as a workaround,
to allow the s_server to disconnect after a timeout
is detected.
'openssl s_server -dtls -timeout`
should work.

That is a limitation of the s_server command.

No. There is a real bug here. I have it replicated locally. Still looking at it.

Fix for this in #18654.
Note that this is only a problem when using "stateful" cookie exchange. The preferred way is to use "stateless" cookies via the DTLSv1_listen API - and that API does not suffer from this problem. s_server implements this via the -listen flag. See:
https://www.openssl.org/docs/man3.0/man3/DTLSv1_listen.html


Error when adding zigbee Philips Hue Lamp

Make sure you are running the latest version of Home Assistant before reporting an issue.
Home Assistant release (hass --version):
0.53.1
Python release (python3 --version):
3.5.2
Component/platform:
zha
Description of problem:
I am unable to add zigbee-based Phlips Hue Lamp. After forcing the pair-mode on the lamp, hass spits bunch of errors in the log file
Expected:
Lamp should be recognized and paired by home-assistant.
Traceback (if applicable):
2017-09-14 13:25:03 INFO (MainThread) [homeassistant.components.zha] Permitting joins for 60s
2017-09-14 13:25:03 DEBUG (MainThread) [bellows.ezsp] Send command permitJoining
2017-09-14 13:25:03 DEBUG (MainThread) [homeassistant.components.api] STREAM<PHONE_NUMBER>40160 WRITING data: {"data": {"service_call_id": "140194999062312-123", "service_data": {}, "domain": "zha", "service": "permit"}, "time_fired": "2017-09-14
T17:25:03.262033+00:00", "event_type": "call_service", "origin": "LOCAL"}
2017-09-14 13:25:03 DEBUG (MainThread) [bellows.uart] Sending: b'33d9218a68004f7e'
2017-09-14 13:25:03 DEBUG (MainThread) [bellows.uart] Data frame: b'34d9a18a54ab1e7e'
2017-09-14 13:25:03 DEBUG (MainThread) [bellows.uart] Sending: b'8430fc7e'
2017-09-14 13:25:03 DEBUG (MainThread) [bellows.ezsp] Application frame 34 (permitJoining) received
2017-09-14 13:25:03 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=140194999062312-123>
2017-09-14 13:25:03 DEBUG (MainThread) [homeassistant.components.api] STREAM<PHONE_NUMBER>40160 FORWARDING <Event service_executed[L]: service_call_id=140194999062312-123>
2017-09-14 13:25:03 DEBUG (MainThread) [homeassistant.components.api] STREAM<PHONE_NUMBER>40160 WRITING data: {"data": {"service_call_id": "140194999062312-123"}, "time_fired": "2017-09-14T17:25:03.281203+00:00", "event_type": "service_executed",
 "origin": "LOCAL"}
2017-09-14 13:25:03 DEBUG (MainThread) [homeassistant.components.websocket_api] WS<PHONE_NUMBER>26384: Sending {'type': 'result', 'result': None, 'id': 11, 'success': True}
2017-09-14 13:25:09 DEBUG (MainThread) [homeassistant.components.websocket_api] WS<PHONE_NUMBER>26384: Connection closed by client
2017-09-14 13:25:10 DEBUG (MainThread) [bellows.uart] Data frame: b'44d9b1d57f3910116d914a4aa7559008fc7e'
2017-09-14 13:25:10 DEBUG (MainThread) [bellows.uart] Sending: b'8520dd7e'
2017-09-14 13:25:10 DEBUG (MainThread) [bellows.ezsp] Application frame 125 (incomingManyToOneRouteRequestHandler) received
2017-09-14 13:25:12 INFO (MainThread) [homeassistant.components.http] Serving /api/12345678901234567890/lights to <IP_ADDRESS> (auth: True)
2017-09-14 13:25:12 INFO (MainThread) [homeassistant.components.http] Serving /api/12345678901234567890/lights to <IP_ADDRESS> (auth: True)
2017-09-14 13:25:15 DEBUG (MainThread) [bellows.uart] Data frame: b'54d9b1ee54aaea077895822855aa6db678ce323a1229688b02396889f77e2ff92bdcde6f0cc121b8d7c034017e'
2017-09-14 13:25:15 DEBUG (MainThread) [bellows.uart] Sending: b'8610be7e'
2017-09-14 13:25:15 DEBUG (MainThread) [bellows.ezsp] Application frame 70 (macFilterMatchMessageHandler) received
2017-09-14 13:25:22 INFO (MainThread) [homeassistant.components.http] Serving /api/12345678901234567890/lights to <IP_ADDRESS> (auth: True)
2017-09-14 13:25:22 INFO (MainThread) [homeassistant.components.http] Serving /api/12345678901234567890/lights to <IP_ADDRESS> (auth: True)
2017-09-14 13:25:23 DEBUG (MainThread) [homeassistant.components.light.lifx] <IP_ADDRESS> (Lamp) async_update
2017-09-14 13:25:23 DEBUG (MainThread) [homeassistant.components.light.lifx] <IP_ADDRESS> (Freak) async_update
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.uart] Data frame: b'64d9b18c65bfdb8b47944badbd5593499c4e5d9f7e'
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.uart] Sending: b'87009f7e'
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.ezsp] Application frame 36 (trustCenterJoinHandler) received
2017-09-14 13:25:25 INFO (MainThread) [bellows.zigbee.application] Device 0x9531 (00:17:88:01:00:1e:39:ce) joined the network
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.zigbee.application] Skip initialization for existing device 00:17:88:01:00:1e:39:ce
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.uart] Data frame: b'74d9b1ed502a15a159944a2daa55924963f6163e12316b8bcc53adb0e27e3e2ffccdd012427e'
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.uart] Sending: b'8070787e'
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-09-14 13:25:25 DEBUG (MainThread) [bellows.zigbee.zdo] [0x9531:zdo] ZDO request 0x0013: [38193, 00:17:88:01:00:1e:39:ce, 14]
2017-09-14 13:25:27 DEBUG (MainThread) [bellows.uart] Data frame: b'04d9b1d5779da73c6d914a4aa7559317037e'
2017-09-14 13:25:27 DEBUG (MainThread) [bellows.uart] Sending: b'8160597e'
2017-09-14 13:25:27 DEBUG (MainThread) [bellows.ezsp] Application frame 125 (incomingManyToOneRouteRequestHandler) received
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.uart] Data frame: b'14d9b1ed542e14b459954b65aa55925e63f34cb312316f8bd7cd684530b2f308ae7e'
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.uart] Sending: b'82503a7e'
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-09-14 13:25:39 ERROR (MainThread) [bellows.ezsp] Exception running handler
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/ezsp.py", line 198, in handle_callback
    handler(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 146, in ezsp_callback_handler
    self._handle_frame(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 169, in _handle_frame
    tsn, command_id, is_reply, args = deserialize(aps_frame, message)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/zcl/__init__.py", line 56, in deserialize
    value, data = t.deserialize(data, schema)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/__init__.py", line 9, in deserialize
    value, data = type_.deserialize(data)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/basic.py", line 13, in deserialize
    r = cls(int.from_bytes(data[:cls._size], 'little', signed=cls._signed))
  File "/usr/lib/python3.5/enum.py", line 241, in __call__
    return cls.__new__(cls, value)
  File "/usr/lib/python3.5/enum.py", line 476, in __new__
    raise ValueError("%r is not a valid %s" % (value, cls.__name__))
ValueError: 204 is not a valid Status
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.uart] Data frame: b'24d9b1ed542e14b459954b65aa5592ce63860cb812316f8bfacd684c39bbfaf7727e'
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.uart] Sending: b'83401b7e'
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-09-14 13:25:39 ERROR (MainThread) [bellows.ezsp] Exception running handler
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/ezsp.py", line 198, in handle_callback
    handler(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 146, in ezsp_callback_handler
    self._handle_frame(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 169, in _handle_frame
    tsn, command_id, is_reply, args = deserialize(aps_frame, message)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/zcl/__init__.py", line 56, in deserialize
    value, data = t.deserialize(data, schema)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/__init__.py", line 9, in deserialize
    value, data = type_.deserialize(data)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/basic.py", line 13, in deserialize
    r = cls(int.from_bytes(data[:cls._size], 'little', signed=cls._signed))
  File "/usr/lib/python3.5/enum.py", line 241, in __call__
    return cls.__new__(cls, value)
  File "/usr/lib/python3.5/enum.py", line 476, in __new__
    raise ValueError("%r is not a valid %s" % (value, cls.__name__))
ValueError: 197 is not a valid Status
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.uart] Data frame: b'34d9b1ed542e14b459954b65aa5592686389041c12316f8bf8cd684134b6f7ff137e'
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.uart] Sending: b'8430fc7e'
2017-09-14 13:25:39 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-09-14 13:25:39 ERROR (MainThread) [bellows.ezsp] Exception running handler
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/ezsp.py", line 198, in handle_callback
    handler(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 146, in ezsp_callback_handler
    self._handle_frame(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 169, in _handle_frame
    tsn, command_id, is_reply, args = deserialize(aps_frame, message)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/zcl/__init__.py", line 56, in deserialize
    value, data = t.deserialize(data, schema)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/__init__.py", line 9, in deserialize
    value, data = type_.deserialize(data)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/basic.py", line 13, in deserialize
    r = cls(int.from_bytes(data[:cls._size], 'little', signed=cls._signed))
  File "/usr/lib/python3.5/enum.py", line 241, in __call__
    return cls.__new__(cls, value)
  File "/usr/lib/python3.5/enum.py", line 476, in __new__
    raise ValueError("%r is not a valid %s" % (value, cls.__name__))
ValueError: 200 is not a valid Status
2017-09-14 13:25:41 DEBUG (MainThread) [bellows.uart] Data frame: b'44d9b1ed542e14b459954b65aa5592ce63880cb812316f8bfacd684c39bbfa4e0f7e'
2017-09-14 13:25:41 DEBUG (MainThread) [bellows.uart] Sending: b'8520dd7e'
2017-09-14 13:25:41 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-09-14 13:25:41 ERROR (MainThread) [bellows.ezsp] Exception running handler
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/ezsp.py", line 198, in handle_callback
    handler(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 146, in ezsp_callback_handler
    self._handle_frame(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 169, in _handle_frame
    tsn, command_id, is_reply, args = deserialize(aps_frame, message)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/zcl/__init__.py", line 56, in deserialize
    value, data = t.deserialize(data, schema)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/__init__.py", line 9, in deserialize
    value, data = type_.deserialize(data)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/basic.py", line 13, in deserialize
    r = cls(int.from_bytes(data[:cls._size], 'little', signed=cls._signed))
  File "/usr/lib/python3.5/enum.py", line 241, in __call__
    return cls.__new__(cls, value)
  File "/usr/lib/python3.5/enum.py", line 476, in __new__
    raise ValueError("%r is not a valid %s" % (value, cls.__name__))
ValueError: 197 is not a valid Status
2017-09-14 13:25:42 INFO (MainThread) [homeassistant.components.http] Serving /api/12345678901234567890/lights to <IP_ADDRESS> (auth: True)
2017-09-14 13:25:42 INFO (MainThread) [homeassistant.components.http] Serving /api/12345678901234567890/lights to <IP_ADDRESS> (auth: True)
2017-09-14 13:25:42 DEBUG (MainThread) [bellows.uart] Data frame: b'54d9b1ed542e14b459954b65aa5592ce63890cb812316f8bfacd684c39bbfa56f67e'
2017-09-14 13:25:42 DEBUG (MainThread) [bellows.uart] Sending: b'8610be7e'
2017-09-14 13:25:42 DEBUG (MainThread) [bellows.ezsp] Application frame 69 (incomingMessageHandler) received
2017-09-14 13:25:42 ERROR (MainThread) [bellows.ezsp] Exception running handler
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/ezsp.py", line 198, in handle_callback
    handler(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 146, in ezsp_callback_handler
    self._handle_frame(*args)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/application.py", line 169, in _handle_frame
    tsn, command_id, is_reply, args = deserialize(aps_frame, message)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/zigbee/zcl/__init__.py", line 56, in deserialize
    value, data = t.deserialize(data, schema)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/__init__.py", line 9, in deserialize
    value, data = type_.deserialize(data)
  File "/srv/homeassistant/lib/python3.5/site-packages/bellows/types/basic.py", line 13, in deserialize
    r = cls(int.from_bytes(data[:cls._size], 'little', signed=cls._signed))
  File "/usr/lib/python3.5/enum.py", line 241, in __call__
    return cls.__new__(cls, value)
  File "/usr/lib/python3.5/enum.py", line 476, in __new__
    raise ValueError("%r is not a valid %s" % (value, cls.__name__))
ValueError: 197 is not a valid Status

Additional info:

@rcloran I just checked with 0.56.2 and it's still the same. Please let me know if I can help debugging this.


Menu pre container

Motivation:

 is wrapped into
 but if that container was given by author then, do not create that wrapper.

I was wondering if I should rewrite the container for layout as the same I did for menu...

The same question for tab container

Layout is a much harder sell to make this kind of change for. At this point unless it is a direct bug-fix Layout is basically read-only. It is a huge monolithic and complex component and sites exist that are relying on its idiosyncrasies. I'd rather we do nothing to  mess with a piece that important to a site.

Ok so, we are doing one last release to MDL. In light of this, I'm not going to merge this in as it may possibly have some adverse affects on existing applications. While it theoretically looks good I'm simply not sure what developers are relying on as far as the current functionality here. So I'm going to be cautious and err on the side to not break as much as possible.
Please check out Material Components for Web while it is in development and verify that the new components fit your needs. If they don't file issues there so they can try to be addressed as early as possible.
Thank you for the effort here, it is appreciated.


Skip Build Phrase Fix and Improvements

Bug:  Skip Build Phrase in the Advanced Section under Github Pull Request Builder on a job cannot be modified.  If you change it's value to anything else, it doesn't work and will always retain the default value.
Improvement: It would be great if Skip Build Phrase would also check the pull request's title (it currently just checks the pull request's body) for the skip phrase.  I have members of my team requesting this.
Improvement: Skip Build Phrase doesn't have any Job DSL support, it would be great to add DSL support for this.

Looks like this has been addressed with #340. Closing.


Request to use your COVID-19-CT-Seg segmentation dataset in our challenge

Hi, thank you for providing such a wonderful Dataset
We are working to release a challenge on Covid-19, and we are wondering if we can use your COVID-19-CT-Seg segmentation dataset in our challenge
Best Regards

@faresbougourzi , thanks for your interest very much.
Sure.
Please also give the credits to the other contributors as listed in
https://github.com/JunMa11/COVID-19-CT-Seg-Benchmark#acknowledgements

Sure, Thanks a lot
Best regards


bundle inject must show the usage when it is used incorrectly

HackerDude-2:test_dundle shekharrajak$ bundle inject 'pry' 1 '>0'
--- ERROR REPORT TEMPLATE -------------------------------------------------------
Error Report
Questions
Please fill out answers to these questions, it'll help us figure out
why things are going wrong.

What did you do?
I ran the command bundle inject 'pry' 1 '>0'

What did you expect to happen?
I expected Bundler to show error message saying the correct format and usage of bundle inject.

What happened instead?
Showing to open an issue

Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?

Asked in slack channel.

Have you read our issues document, https://github.com/bundler/bundler/blob/master/ISSUES.md?
yes

Backtrace
NoMethodError: undefined method `start_with?' for nil:NilClass
  /Users/bundler/lib/bundler/cli/inject.rb:23:in `block (2 levels) in run'
  /Users/bundler/lib/bundler/cli/inject.rb:23:in `any?'
  /Users/bundler/lib/bundler/cli/inject.rb:23:in `block in run'
  /Users/bundler/lib/bundler/cli/inject.rb:21:in `each_slice'
  /Users/bundler/lib/bundler/cli/inject.rb:21:in `run'
  /Users/bundler/lib/bundler/cli.rb:468:in `inject'
  /Users/bundler/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /Users/bundler/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /Users/bundler/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /Users/bundler/lib/bundler/cli.rb:21:in `dispatch'
  /Users/bundler/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /Users/bundler/lib/bundler/cli.rb:11:in `start'
  /Users/bundler/exe/bundle:32:in `block in <main>'
  /Usersbundler/lib/bundler/friendly_errors.rb:121:in `with_friendly_errors'
  /Users/bundler/exe/bundle:24:in `<main>'

Environment
Bundler   1.14.3
Rubygems  2.5.1
Ruby      2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
GEM_HOME  /Users/.rvm/gems/ruby-2.3.1
GEM_PATH  /Users/.rvm/gems/ruby-2.3.1:/Users/.rvm/gems/ruby-2.3.1@global
RVM       1.28.0 (latest)
Git       2.10.1
Platform  x86_64-darwin-15
OpenSSL   OpenSSL 1.0.2j  26 Sep 2016
rubygems-bundler (1.4.4)

Bundler settings
gem.test
  Set for the current user (/Users/.bundle/config): "false"
gem.mit
  Set for the current user (/Users/.bundle/config): "true"
gem.coc
  Set for the current user (/Users/.bundle/config): "true"
trampoline_disable
  Set via BUNDLE_TRAMPOLINE_DISABLE: "1"

Also bundle inject 'pry' > '>0' shows(and does) nothing.
and
bundle inject 'pry'1234 '>0'
Fetching gem metadata from https://rubygems.org/.........
Fetching version metadata from https://rubygems.org/.
Could not find gem 'pry1234 (> 0)' in any of the gem sources listed in your Gemfile.

must show the bundle inject usage.

I am working on it and  i'll open PR soon.


Tech Doc - User management how-to

[ ] Warren to write content
[ ] Abi to help publishing in Backstage

Added to the PR @abibat-adesina made for the Azure docs structure
https://github.com/bcgov/public-cloud-techdocs/pull/48
https://github.com/bcgov/public-cloud-techdocs/blob/azure-placeholder/docs%2Fazure%2Fdesign-build-and-deploy-an-application%2Fuser-management.md


feat(wandb): support media logging

What does this PR do?

Support media logging with W&B.
TODO:

[x] implement log_text
[x] implement log_image
[x] evaluate other media logging (molecule, audio, etc): will do it in a follow-up PR
[x] add simple artifact table logging (refer to doc for more complex use cases)
[x] add documentation
[x] add tests

Does your PR introduce any breaking changes? If yes, please list them.

None
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Not really sure how to fix the error building the docs.
I think it's related to pandas not being available. Should I change the type hint to Any?

Hi @justusschock

We cannot have the logger API to diverge across the different logger implementations.

I understand the interest to have a unified logger API but I see a few drawbacks:

Loggers already have their differences

the input arguments are different between each logger due to their unique functionality
WandbLogger supports a watch method used to track gradients, parameters, etc
WandbLogger has a unique way of logging models as artifacts with aliases
NeptuneLogger also has its own unique methods such as log_text, log_image and log_artifact

It would be limiting and would prevent from offering features that are unique to each logger

Neptune seems to log images one at a time while in wandb, they must be logged in batches for a single step
wandb supports unique medias (segmentation masks, bounded boxes, video, audio, 3d point cloud, molecule, histograms, scatter plots, ROC curves, confusion matrix, interactive charts through vega spec, etc). It would be a pain to prevent users from using these media types just because they are not supported by the other loggers
wandb now also supports W&B Tables that can be queried to visualize, analyze and compare any form of data. It would have been nice to add this feature in Pytorch Lightning (through log_table as proposed in this PR)

Limiting logging to a list of supported types is actually a breaking change as reported in #8088. I would suggest letting people pass any type of object to their loggers to ensure we don't limit any logger functionality. Typically only one logger is used and it is probably expected that users would have to adapt their logging code if using very specific features and switching between loggers (wandb, mlflow, neptune, tensorboard, etc).

As an example this is some data logged directly using log_images and log_text from this PR: W&B run

Hi @borisdayma
I know that wandb already has different methods such as watch but these are things that are simply not supported by other frameworks like that.
With other more common features like logging media though, I think we should generalize the API there.
I'm not saying that we should already have implementations for all loggers right away. More that we need to provide abstract functions as interfaces to the base logger class and then add the implementations for wandb. And all loggers not implementing these methods will just raise NotImplementedError

Are you ok using *args, *kwargs in the generic implementation so loggers have more flexibility with the methods?
Wandb accepts for example many different arguments and multiple types for images so it would be better to control it at the logger level.

To some extend yes. E.g. when logging an image, the name and the image should not be in args or kwargs :) All the others can probably go in there.

@justusschock What do you think of making them generic like this.
The reason is that loggers may have different implementations:

wandb is more adapted to lists vs neptune seems to use individual items
for text the item is not required as a dataframe could be passed to wandb (so we can pass "data + columns" or "dataframe"
for images, it would be hard to do type checking as each logger may accept different types

But wouldn't you agree that each logger takes at least a tag and the object to log? This is why I'd like to have them explicit and use *args and **kwargs only for the other arguments.
Thoughts @awaelchli @borisdayma ?

But wouldn't you agree that each logger takes at least a tag and the object to log?

Giving a tag/key seems to make sense. At least I can't think of an edge case against it.
For log_text, within LigthningLoggerBase, you would have:
def log_text(self, key:str, value, *args, **kwargs):
    pass

Then if we want to a type checking on value, we already have NeptuneLogger, which accepts a str and WandbLogger which would accept Union(List[List[str]], pandas.Dataframe). If we try to unify the type of the argument, we limit one of the loggers.
In the case of Images it becomes even complex as for wandb it would be something like Union[str, wandb.Image, matplotlib.artist.Artist, PIL.Image, TorchTensorType, np.ndarray].
Also I would not expect users to think anything is gonna get logged if they only pass a key with no other args and an error should be raised by the loggers themselves (if they have the method implemented). It would fail in wandb for example.

In case of your wandb example I'd then suggest to internally do a typecheck and if text is a dataframe or a list parse for the respective other arguments

It could be ok here but I've been trying to simplify as much as possible this integration and use it as much as possible as a wrapper to wandb client for easier maintenance, which is why I even try to use consistent args whenever I can so wandb users have an easier time with the integrations.
wandb already does a lot of checking, debugging, tries to provide helpful error messages so it would be easier to delegate the entire task of parsing/checking/processing the arguments directly to that library.

So on my side my last questions are:

How to solve the error building the docs? I think it's due to pandas not being available and it's only for type checking of log_text. Should I change the type checking to Any?
Can I copy the same doc in the loggers page? The reason is that W&B gets a lot of questions on this integration where the answers are in wandb doc but not in PL doc and people always refer to the loggers page or the WandbLogger page when asking their questions.

There seems to be a mismatch version between pandas & numpy in the test environment.
Should I remove my pandas test?
ImportError: this version of pandas is incompatible with numpy < 1.17.3
   your numpy version is 1.17.2.
   Please upgrade numpy to >= 1.17.3 to use this pandas version

The PR is now ready for final review (failed test seem unrelated).
Let me know if any change is needed.


API to get object ids from task id

https://github.com/algolia/algoliasearch-client-node/issues/29

@bodinsamuel @Haroenv

Hello I am using https://www.algolia.com/doc/rest-api/search/#get-a-tasks-status
I am using this API to get the status of my task but in case if some tasks are completed means status is not completed then i want to update those objects present in that task ids
currently what i observed for around 1700 objects its created 2 task ids, and for 16K objects its creating 17 task ids
so if some of the tasks are not completed successfully i want to get objects from those tasks and update again
or instead of getting objects and updating them again is there a way to just retry using task id
or not sure if there is better way to achieve this, could you please assist here

Bsically what i am saying is when i got to know my task is not successful from status API then what is the next steps
either retry all update again
find objects from that failed taskid and only update that (so here is there API to get objectids from taskid)

Hey, in the snippet you shared you are calling the wait method, which means you are already waiting for these tasks to be considered as completed (published).
You also shouldn't have to handle the task retrying yourselves, the validation that matters to you happen at the API call time, any error will be reported there and you'd have to retry your call, but you don't have to interact with the queue other than making sure the task is published (which is the equivalent of completed)

@shortcuts Thanks for reply
I am using Wait yes but its just returning taskID its not telling its completed successfully or not
so the next step is using those taskId i am checking the status using published
but what if the taskid returns status unpublished

@shortcuts Thanks
so you mean to say wait will return only if all tasks are successful and throws error if any task fails

so you mean to say wait will return only if all tasks are successful and throws error if any task fails so no need to check the status of each taskid in case of success

Yes, and more exactly, wait will only stop fetching tasks status when they are all published. You can consider that once you API call gets through, all you have to do is call the wait method and not bother with anything else.

You can find the exact implementation here: https://github.com/algolia/algoliasearch-client-javascript/blob/master/packages/client-search/src/methods/index/waitTask.ts and the usage in the saveObjects file

@shortcuts Thanks
So waitTask internally taking care of retrying part so it makes sue that all tasks are completed.
so if i use .wait() i dont have to do error handling

so if i use .wait() i dont have to do error handling

Not on the task, but keep a catch for any API calls anyway as you can encounter other issue :)
I'm closing this issue as completed, but in case you encounter any issue please re-open it!

@shortcuts how long the taskId maintained at algolia side
for example if i got a taskId after saveObject and after one month if i call get status API passing task Id can i get the status for same
Thanks,


Refactor long-press code

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


feat: logging improvements

Provides logging on relevant steps to improve DX while debugging

bors r+

bors r+

bors r+


Not compatible with VS Code 1.54.3?

Everything in the title... Is there a way to get a compatible version?

Same here.

Native testing is a new feature and is only present on recent versions of VS Code. The latest release is 1.56.


docs(platform): update run data retention info

Change Free Retention "microcopy" -> following the update in console (apify-core repo), link to zenhub issue here
I have updated 2 places -> platform: runs and builds, and tutorials: tasks. Please, let me know if there is some other page where it suits well, thanks!
Issue:

Right now we are (supposed to be) preserving the last 10 runs that a free-user made beyond 30 days. This is for reactivation and debugging purposes. We don't explain this to the user at all, so we should do a better job of that.

Updated sections in docs ⬇

It looks pretty good to me. I think I would just add the note in usage>data retention as well.
https://docs.apify.com/platform/storage/usage#data-retention

thanks, updated as well


Take a look at https://github.com/ACEsuit/ACE.jl

Can we use this toolbox to compute SNAP?

Now we have a pure Julia version of SNAP in InteratomicPotentials.jl and a wrapper to ACE1jl in InteratomicBasisPotentials.jl.  We will use this versions for the time being.


USB-C voltage trigger

CC1 is connected to CC2 and share only 1 resistor. According to the USB PD2 design documentation must CC1 and CC2 each have it’s own 5k1 resistor.

Yeah, this is probably the reason why this board is super-sensitive with chargers... The initial Raspberry Pi 4 had that "error" as well...


Implement And instruction

LGTM. I think it would be great for the gadgets to have this functionality in simpleworks. Let's merge this PR and revisit this when we have that!

The CI isn't working. I'll run the checks on my side and merge.

 Support and instruction


Suspending Julia via Ctrl-Z requires two presses

The following happens for me with Julia 1.6.7, 1.8.5 and 1.9.0rc1 on both macOS 12.6.4 and a Ubuntu 20.04.
On Unix like systems (including macOS and Linux) one can usually suspend programs with a REPL using Ctrl-Z and then later resume them (e.g. by entering fg in bash).
This kinda works for Julia, but one has to press ctrl-Z twice: after the first press, Julia is in a weird limbo state: it echos whatever I type, even overdrawing its own REPL prompt, but is otherwise unresponsive. Ctrl-C is also ignored. Pressing ctrl-Z a second time then fully suspends it and I am back in my shell.
Also, if I press Ctrl-Z Ctrl-C Ctrl-Z and then resume it (via fg), it crashes.

A trivial way to fix this would be if the launcher just replaced itself with Julia (i.e., no fork, just exec), instead of launching Julia as a child process. It seems to do the latter in order to check for updates? But I'd gladly trade that for having this issue resolved; I really prefer to run juliaup update manually anyway

Yes, or fork the update process (orphan it) and then exec the main Julia process.


Add linting action for documentation

Addresses Issue: 53

Starting the process, but need to fix the existing errors first.

Fixed the markdownlint errors in the project.


add new Cask for ManicTime 1.3.3

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Uninstalling failed with the following output:
$ brew cask uninstall manictime
Warning: Unexpected method 'pkgutil' called on Cask manictime.
Follow the instructions here:
  https://github.com/caskroom/homebrew-cask/blob/master/doc/reporting_bugs/pre_bug_report.md

If this doesn’t fix the problem, please report this bug:
  https://github.com/caskroom/homebrew-cask#reporting-bugs

Warning: Unexpected method 'pkgutil' called on Cask manictime.
Follow the instructions here:
  https://github.com/caskroom/homebrew-cask/blob/master/doc/reporting_bugs/pre_bug_report.md

If this doesn’t fix the problem, please report this bug:
  https://github.com/caskroom/homebrew-cask#reporting-bugs

Any help appreciated.

You need pkgutil: instead of pkgutil to fix the uninstall.

Thanks @Moisan. Shouldn't the audit or the style checker have caught this issue?

I am not deeply familiar with Homebrew audit and style checker but my feeling is that those will only make sure that the formula is properly formatted (e.g. correct indentation, all attributes needed are present), not that it will necessarily work at runtime.

Yes, that makes sense, but since "pkgutil:" is a known keyword, I don't think it would be out of scope to check for the necessary punctuation. At the very least (IMHO), one of these checkers (or the uninstall command) should print out an informative error message that would lead cask authors towards the solution.

Thank you for your contribution.

@gobinathm I'm sorry, I missed some of your review comments. I agree with you about the token, but the one I used was generated according to the instructions in adding_a_cask.md, which is why I didn't think of changing it.
As for the zap delete, that makes sense. Should I send a new PR adding that, @miccal?

@waldyrious i guess new PR is not need for the token change, that can be ignored.

@waldyrious you are welcome to open a new PR to add the zap stanza.


Dev tools: remove erpc

Hi @kasrakhosravi ! The eRPC tooling needs to be internally reviewed by our security team before we include usage directions in the technical docs. Please reach out to<EMAIL_ADDRESS>to learn more about Polygon's security standards and explore integration. Thanks!


Problem about OStateMementCache's synchronized method 'get'

OrientDB Version, operating system, or hardware.
OrientDB 2.2.12
Operating System

[x] Linux
[ ] MacOSX
[ ] Windows
[ ] Other Unix
[ ] Other, name?

Hi,
I use plocal orientDB ,and submit a lot of sql-like query at the same time. I find many sql querys are blocked on the OStateMementCache object's get method , like

After reading the code, I think is it necessary to use Synchronized method ? If there are hundreds of concurrent querys, the last one may wail a long time. It may be not a good idea.

Hi @BruceMu
I think you're right, we could just synchronize the internal map and reduce the contention a lot.
I'll work on it asap
Thanks
Luigi

Hi @BruceMu
I just pushed a fix for this. I did some more fine-grained locks that do not involve query parsing (that is the expensive part of that method).
The fix is in 2.2.x branch and will be released with 2.2.14
This should completely solve the problem, but please reopen if you see anything that can be improved.
Thanks
Luigi


Task goes to exception when defined as port_driven

If the task is set as port_driven, it goes to exception caused by read timeout.
During debuging, it was checked that the method iodrives_base::hasIO() was returning true, but no left data was checket in the extractPacket buffer. Still needs more investigation on that.
Actually the task execute the updateHook every 'read timeout' period.

Why port_driven instead of fd_driven? We are getting usbl data from a file descriptor aren't we?

The last commit in https://github.com/Brazilian-Institute-of-Robotics/drivers-orogen-usbl_evologics/pull/15, fix it.
The Task is now port_driven and fd_driven.
Just a remark, in case there is no data in the file descriptor or in the port to trigger the task, the updateHook is called every io_read_timeout period.

The last commit in #15, fix it.

 The last commit in #15 just sets port_driven ....

https://github.com/Brazilian-Institute-of-Robotics/drivers-orogen-usbl_evologics/pull/15/commits/08f3a88c62cea39215b5367676bc04be8e5553de

It is fixed by the PR https://github.com/Brazilian-Institute-of-Robotics/drivers-orogen-usbl_evologics/pull/15.
Closing it.