Typo in link at page docs.gradle.org/current/userguide/build_file_basics.html

Issue type
Typo (please open a PR instead)
Problem description
At the bottom of the page docs.gradle.org/current/userguide/build_file_basics.html
on the very last text line of the guide thre is a wrong text for the link to the next section.
"Consult the Writing Settings File" should be
"Consult the Writing Build Scripts"
Context (optional)
No response
Page with the problem
https://docs.gradle.org/current/userguide/build_file_basics.html

Thank you for your interest in Gradle!
This is a valid documentation issue.


example.tex: add client email

Makes sense 👍 Thanks for the PR.
Only weird thing is that the invoicer and the client are at the same @example.com domain 😄 but I don't think anyone will think that hard about it.


x/tools/internal/refactor/inline,x/tools/gopls: undo variadic elimination when it is safe to do so

Follow up on this comment on a semi-automated CL: https://go-review.googlesource.com/c/tools/+/537475/1/gopls/internal/lsp/source/rename.go#973
The inliner should undo variadic elimination (packing variadic arguments as []T{...}) when it is safe to do so. As a result of the current logic, the inliner may introduce this redundancy at the callsite.
CC @adonovan

FWIW, "Safe to do so" means there is exactly one use in the callee body and it is the final argument of an ellipsis call f(param...).

I don't think that's right. []T{a,b,c}... is safe to replace with a, b, c wherever it occurs.

Good point. Though I suspect that if there were multiple uses of the parameter, it would not have been substituted, so you would not see f([]T{a, b, c}...), only f(args...) after a binding decl var args = []T{a, b, c}.


Adding a cookbook section in the doc

Adding a Krypton cookbook with recipes for :

Login / register users with email and username
Adding user roles

Is it possible to use extended schema fields to login?


Switch the VRPTW instances over to VRPLIB format

Our VRPTW instances are in Solomon format. All others are VRPLIB-formatted, including the prize-collecting instances which extend the VRPTW instances. For consistency, I think we can just format all instances in VRPLIB format, and use the .vrp extension.

@leonlan would there be any reason not to do this? I know Keld Helsgaun for example also did the same thing with his versions of the GH1000 instances - those are all in VRPLIB format.

There is no reason not to do this. The only suggestion that I have when using Keld Helsegaun's VRPTW instances is that we remove the SERIVCE_TIME : 90 specification and make it a data section instead.

The only suggestion that I have when using Keld Helsegaun's VRPTW instances is that we remove the SERIVCE_TIME : 90 specification and make it a data section instead.

Why do we not want to have a specification? I just noticed our prize-collecting instances also have this (those are based on the same VRPLIB formatted data of Helsgaun).

The only suggestion that I have when using Keld Helsegaun's VRPTW instances is that we remove the SERIVCE_TIME : 90 specification and make it a data section instead.

@leonlan why do we not want to have a specification? I just noticed our prize-collecting instances also have this (those are based on the same VRPLIB formatted data of Helsgaun).

The service time specification was (presumably) introduced to convert the GH/Solomon instances to VRPLIB style. Since the GH instances had only constant service times, Helsgaun added a specification, but I think the ideal case is to have all client data presented as data sections. The only exception to make is for vehicle data (because a homogeneous fleet is widespread In the VRP literature).


Attention scores out of memory

Hi, I'm trying to execute step 5 to extract attention scores.
I use the following settings:
    --max_seq_length 1536
    --per_gpu_pred_batch_size=64
    --fp16

The dataset contains 89848 samples. I get the following out of memory error when the attention_scores numpy array is instantiated.
02/08/2022 09:39:01 - INFO - __main__ -   Saving features into cached file ./cached_de│
v_ft_0_1536_dnaprom                                                                   │
02/08/2022 09:41:15 - INFO - __main__ -   ***** Running prediction  *****             │
02/08/2022 09:41:15 - INFO - __main__ -     Num examples = 89848                      │
02/08/2022 09:41:15 - INFO - __main__ -     Batch size = 64                           │
Traceback (most recent call last):                                                    │
  File "run_finetune.py", line 1284, in <module>                                      │
    main()                                                                            │
  File "run_finetune.py", line 1191, in main                                          │
    attention_scores, probs = visualize(args, model, tokenizer, prefix=prefix, kmer=km│
er)                                                                                │
  File "run_finetune.py", line 612, in visualize                                      ├
    attention_scores = np.zeros([len(pred_dataset), 12, args.max_seq_length, args.max_│
seq_length])                                                                          │
MemoryError: Unable to allocate 18.5 TiB for an array with shape (89848, 12, 1536, 153│
6) and data type float64                                                              │
                                                                                │
*************************************

Any idea on how to solve this issue? Thanks.

FYI @israa-alqassem


Car with this is already configured

Hi,.
Im getting this error during setup in Homeassistant
Car with this is already configured

anyone who can help me


GLTF export: Use sparse accessors for morph targets

Implements sparse for vec3 vertex position, normal and tangent buffers within morph targets (blend shapes).
Reduces buffer sizes on some blendshape-heavy exported gltf files by 50%
The exported size of this file was reduced from 18MB down to 12MB:
https://hub.vroid.com/en/characters/673873032957715085/models/7956797656633477494
Fixes: https://github.com/godotengine/godot-proposals/issues/9276

After making this change, I determined that Godot's morph normal and tangent exports were completely incorrect, and hence that we were using the incorrect reference buffer: because morph targets are relative to zero, it is appropriate to compare to a zero-initialized buffer (undefined bufferView).
As it is a separate change, I have included this bugfix as a separate commit.
As a testcase, I activated 4 blend shapes in at once a blender exported gltf to make the effect extremely obvious:
Current Godot 4.x gltf export: you will notice the mouth is more grey and some wrinkles around the mouth are less prominent:

Fue to blendshapes effectively including the sum of the original normals and the new normals, it produces roughly an average, so the normal deltas are about half what they should be
Bug-fixed gltf export:

Original gltf from blender: should look identical to the bug-fixed version:

Upon debugging why exported blend shapes were still far larger than expected despite the sparse buffers, I determined that the blend shape handling during export was entirely incorrect for normals and tangents, and the sparse code was handling vertex positions incorrectly. This bug affects existing versions of Godot, so it can be viewed as a separate bugfix. Therefore, I made it a separate commit.
I also adjusted the is_zero_approx factor for blend shape normals and tangents to account for normals and tangents requiring lower precision than vertex positions: 0.0001 should be sufficient.
Due to a lot of code change to handling of blend shape exports, I am requesting another review,

Commentary:
Whether these blend shape normals are even desirable or correct on most models is an entirely different discussion. Blend shape normals seem highly distrusted by most toon shaded model authors, with the official VRM exporter excluding them entirely. fbx files (as well as FBX2glTF converted files) seem to often have zero deltas on blend shape normals.
Godot really needs the ability to calculate correct blend shape normals in this case, at least on fbx files: I'm pretty sure there's a reason that Unity re-calculates blend shape normals by default.
In fact, it seems rare to find models with deliberately authored blend shape normals, so it seems odd to build the rendering pipeline in such a way that requires not only blend shape normals to be defined, but also blend shape tangents, and for all vertices. This requirement is new as of Godot 4.2, and I consider it a regression especially for toon shaded characters which often do not use normals maps and should not require tangent vectors at all.
I hope that Godot's rendering team considers an overhaul of storage of blend shape normals and tangents to be more memory efficient, which would probably also be more GPU efficient in terms of how the compute shader might be able to iterate over the sparse indices instead of all vertices on the mesh.

I was asked for a better explanation of the change I made to (normalized blend shape mode) normal and tangent export.
The current behavior (4.0-4.2) of Godot's gltf export is incorrect: it converts normalized vertex blend shapes correctly to relative by subtracting, but it does not perform the subtraction for normals and tangents. I needed to fix this in order for the sparse accessors to work, since they would have been otherwise referencing the wrong buffer
For example, let's take a mesh with one vertex and one blend shape. Say a blend shape moves a vertex left by 0.5, from (3.0,0,0) to (2.5,0,0), and the normal changes from (0,0,1) to (0.05, 0, 0.99)
Godot's base mesh will have: vertices: (3,0,0); normals: (0,0,1)
Godot's blend shape will have: vertices: (2.5,0,0); normals: (0.05, 0, 0.99)
However, glTF stores in relative, so glTF export will have the same base vertices, but glTF blend shape should have: vertex (-0.5,0,0); normal: (0.05, 0, -0.01)
The bug is Godot's current gltf exporter is outputting blend shape vertex: (-0.5,0,0); normal: (0.05, 0, 0.99)
the effect of this is not quite as bad as it appears, and this is what surprised me when trying to understand how we didn't notice the bug. What happens is the normal is applied as relative during import. this will calculate the following:
normal = (0,0,1) + (0.05, 0, 0.99) = (0.05,0,1.99) ... This result will be normalized, roughly: (0.025,0,0.995) or something
In effect, due to the bug I am fixing here, exported glTF normals were almost exactly half as pronounced as they should be, and that can be difficult to notice, when it only applies to blend shapes, and only blend shapes that affect the normal, and only when using standard shading with enough contrast in the lighting.

Thanks!


[New workshop] There remains 'Це поле є обов'язковим' error after choosing a day in the schedule of classes.

Environment: Windows 10, 64-bit, Google Chrome 107.0.5304.107.
Reproducible: always.
Preconditions
1.Follow the link https://oos.dmytrominochkin.cloud/#/
2.Log in as SP (e.g<EMAIL_ADDRESS>'Password'="Qazwsx789!")
3.Select «Мої гуртки» in the menu bar at the top right corner.
4.Click on the “Додати гурток” button and fill in all mandatory fields.
Steps to reproduce

Select Monday and Thursday in the schedule.
Cancel the choice of days.
Select again Monday.
Pay attention to the 'Це поле є обов'язковим' error.

Actual result
There remains 'Це поле є обов'язковим' error after choosing a day in the schedule of classes.

Expected result
After choosing a day in the schedule of classes, the error disappears.
Labels to be added
"Bug", Priority ("low "), Severity ("low").

Bug is fixed, thank you)))


TODAY - Google Stops Supporting Physical Web on iOS Chrome - and soon on Android...

Hello,
BIG DISAPPOINTING NEWS -
I just learned today that Google is no longer supporting Physical Web on iOS Chrome.  Today had two customers upload newest iOS Chrome on their iPhone and Physical Web is gone.  I checked and learned that according to Google Team - Yes Physical Web on iOS Chrome has been removed and that "Physical Web will soon be no longer supported on Android Chrome.... Only on Android Nearby..."     Has anyone seen any formal announcement from Google?   I am sure we all want to know why.
Try it out... Install the latest iOS Chrome from the Apple Store...
I know this helps Apple and Apple iBeacon deployments but is a huge cost to those of us who supported Physical Web and are in the middle of pilots, responding to RFPs, and having to go back to live customers.
Any comments or discussions on what this does for Eddystone Hardware vendors and VARS?  What does this do for you?   Google/Scott, please tell me I am wrong.
Regards, Chip Hysler

Hi,
i have the same problem.  When i did the IOS Chrome upgrade to chrome release 62, physical web on chrome dissapeared, and there is no more eddystone notifications on chrome.
What do you think Chip Hysler, is it the official news that google chrome does not support any more physical web? Is there some kind of workaround solution?
Regards,
bisaicx

Hello, I had several customers contact me on Friday about this disappearing.  Talked to my beacon supplier and other folks. They too saw the problem too with no warning from Google.   According to what I have seen last it was removed from iOS and soon from Android Chrome.   So the idea of the Physical Web of being able to go across iOS and Android without a custom app appears to be dead...  Nearby works (Android only) So now the only browser that supports Eddystone beacons is Samsung (Android only).  So if we need our apps on both platforms with need to develop a custom app.
Eddystone beacons where  really designed with Physical Web in mind, without Chrome... iBeacons may be the way to go.
In any case, it would nice to get an official statement from Google... It's bad, with all the excitement built up over the last 2 years in the press, with developers, and hardware manufacturer's and no warning.
Regards

Hello, I had several customers contact me on Friday about this disappearing.  Talked to my beacon supplier and other folks. They saw the problem too with no warning from Google.   According to what I have seen last it was removed from iOS and soon from Android Chrome.   So the idea of the Physical Web of being able to go across iOS and Android without a custom app appears to be dead...  Nearby works (Android only) So now the only browser that supports Eddystone beacons is Samsung (Android only).  So if we need our apps on both platforms with need to develop a custom app.
Eddystone beacons were really designed with Physical Web in mind, without Chrome... iBeacons may be the way to go.
In any case, it would nice to get an official statement from Google... It's bad, with all the excitement built up over the last 2 years in the press, with developers, and hardware manufacturer's and no warning.
Regards

Yeah, I agree with you, removing the physical web with no warning is not correct... did you get or see any official statement from google? maybe this is just a first step of reconfiguring the whole system... and in that case maybe will be some other opportunity to have a eddystone protocol works without a custom app...
Regards

Hello, I hope this is the case. I just saw a text from Google's Head of Chrome development.  But download the lastest iOS Chrome, you will see.
Hopefully I am wrong...
Regards...
Sent from my Sprint Samsung Galaxy Note5.
-------- Original message --------From: bisaicx<EMAIL_ADDRESS>Date: 10/23/17  9:50 AM  (GMT-06:00) To: google/physical-web<EMAIL_ADDRESS>Cc: chiphysler<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [google/physical-web] TODAY - Google Stops Supporting Physical
  Web on iOS Chrome - and soon on Android... (#931)
Yeah, I agree with you, removing the physical web with no warning is not correct... did you get or see any official statement from google? maybe this is just a first step of reconfiguring the whole system... and in that case maybe will be some other opportunity to have a eddystone protocol works without a custom app...
Regards
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/google/physical-web","title":"google/physical-web","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/google/physical-web"}},"updates":{"snippets":[{"icon":"PERSON","message":"@bisaicx in #931: Yeah, I agree with you, removing the physical web with no warning is not correct... did you get or see any official statement from google? maybe this is just a first step of reconfiguring the whole system... and in that case maybe will be some other opportunity to have a eddystone protocol works without a custom app...\r\n\r\nRegards\r\n"}],"action":{"name":"View Issue","url":"https://github.com/google/physical-web/issues/931#issuecomment-338684230"}}}

Hello,
I try to download-it but there is still no update available on Apple Store...
What do you mean, that Google re-enable the physical web on Chrome?
Regards

Can we have a contributor respond to this please? @scottjenson @mmocny
It's really odd that there has been no official word on this so far. Even the documentation hasn't been updated: https://google.github.io/physical-web/try-physical-web#ios

Google has a history of this kind of ecosystem surprise.

However, in this specific case, this lack of tech traction which caused Chrome team to drop support has something to do with the wholistic caliber of the awareness efforts and the awareness execution.
In light of the rising interest in personal privacy concerns and the European Data Privacy Laws (GDRP) coming into effect early next year, this decision to back away from the valuable tech seems quite shortsighted. Proximity-based, contextual engagement is not conducive to resist data leaks from a privacy tracking perspective unless you take the Eddystone Physical Web URL approach.
Admittedly it was quite frustrating that the Chrome Team pulled PW support. There are even some tiny oversights in the pull, like forgetting to take out the "chrome://chrome-urls" referencing the previously available "chrome://physical-web".  According to @scottjenson which was indicated via Twitter in response to a direct inquiry, the only detection path for PW in the future will be via the Nearby API. This would almost certainly steer a logic to use the EID direction over the Physical Web version of Eddystone. Additionally, @scottjenson also seemed to indicate that Chrome team would make an announcement about this in the next few days about the decision to drop it.
But in my humble opinion, the "trailblazing" Google did to implement Physical Web is/was excellent. Nothing in this hardware/software BLE space is fully ideal but some interesting progress was spearheaded by Google and the PW team.
Of course, I think they (Google) really missed a key set of opportunities to influence a wider adoption due to their well-intentioned efforts to make sure it was a "neutral ingredient technology". And while it would be better if they stayed fully focused and even expanded the support for PW into more than just the "dinky notifications" in chrome's today screen, the buried Nearby privacy settings, or the decision to back out of Omnibox support, there is an opportunity for others to pick up where they are leaving off.
If we can get permission and maybe even support from Google to build a consortium of stakeholders that want to see a universal proximity browser, it is likely that we enhance the chances of success.  One key issue is notification management.  This is actually a very solvable issue but we have not had that opportunity because we were waiting for Google to up the game.
The people listening here are part of a  community of PW oriented people and businesses who believe in this novel technical implementation. There is a unique opportunity to move the needle forward on adoption, increase awareness, drive larger scale implementations, and create high-value engagements with PW.
If interested in participating in this initiative, please contact me directly.
Don't whine, act.  :)
best regards,
Agustin

@auge2u Could you please link to the Tweet from @scottjenson that you've mentioned above?

The announce happened yesterday by the Chrome team. Please follow the discussionn w/in that thread on Google groups: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/physical-web-discuss/5hkPwciMdH4

I'm very disappointed as well. But, I agree with @auge2u that this latest abrupt move by google creates a void that may present interesting opportunities. I certainly bought into the idea of the Physical Web and its possibilities and I still think it's viable. One thing our team has been forced to do over the last 2 and a half years is roll with the punches. This latest announcement is a shot to the gut, but we'll just have to get more creative.

Scott, you and your teams are late... You turn PW off a week before any communication or warning to a large OW following.  Who is cleaning up all the PW info on all the Google PW areas on the web.  Now a lot of miscommunication and outdated info. Apple ibeacon team is going to love all. Plus now Samsung has the only official browser with beacon detection.

Scott isn’t on that team anymore, since August. He mentioned it in another github issue.

My guess is this project is going to be up to the community to move forward, which was the original idea. If the need is there it will continue. I don’t believe there’s much of a dedicated team at google for this project now.

I Just learned about the PW and what is was capable of. I have invested a significant amount of time and energy into implementing this for my business. I hope there will be some form of cross platform communication developed with beacons in mind. #bringbackphysicalweb / #keepphysicalweb / #bringsomethingbetter #google

I am very glad to see a few companies and people with a strong interest in building a path forward for the Physical Web Eddystone URL. With ubiquitous iOS adoption as a key goal, at least from my side, the likelihood of success is higher if we plan to initiate a shared resource strategy on several fronts.
I have been in discussion with several business leaders that have similar goals and are open to contributing energy and focus.  Not only do they have an excellent background in their own needs but also some very well thought out concepts and comments on the limitations and challenges of physical web and where to go next.
However, despite the earlier message, I don't have anyone on this list as part of the current working group.  A few other people I have contacted actively have assumed that something would happen to/for them with no participation.  While the "wait and see" attitude works well in some cases, this is not one of them. We need participants to join the conversation, drive the criteria and maybe support in collaborative development.  If you see the potential or even want to be part of the group that shapes the phase 2 of the physical web, please reach out over twitter @auge2u or contact me here.
I am bumping the following to suggest participation because you are feeling a need.
@chiphysler @aakashjain @cjzip2016 @bisaicx @derekshull @beaconstalk @luciofr
What we can do is collaborate and execute for shared value.
rgs
a

@auge2u I would be interested in helping in any way I can. I had originally had a developed a prototype product with @bryceewatson using Physical Web but with support now pulled, I'd like to see if we can do better here. One thing that always bugged me was the lack of native support on iOS without Chrome, so maybe that's something that could be improved on.

@auge2u We are also ready to support in this. We have put a big investment on the physical web platform hoping that native support will be available on IOS.

I'm up for creating a working group of the next phase.  Though without someone from the iOS or Android team to help push the groups agenda forward I wonder how far we will be able to get?

Hi all, well after investing a lot of time and effort into the physical web I guess I’m in the same boat as everyone else here.  That doesn’t mean it has to sink though.  In th UK it still means 50% of people can still receive notifications so best to be optimistic :).
Scott Jenson told me in a thread of mine a few months ago he was no longer on the Google Chrome Team.  I raised my concerns then and he stated that they were not too interested in the project but the eddystone protocol was here to stay so it’s up to us all to make it happen in any way we can.
So we know it’s doable to create scanning apps as there’s a few already, and they show already in notifications when selected as widgets.  But they do have their user faults.
I agree that it would be in the interests of many of us coming together and collaborating to perhaps create a single dominant branded scanning app.  The alternative will be lots of people putting time and money into lots of different scanning apps all basically doing the same thing.  If that time and money could be used between collaborative partners putting together a much more functional app using the principles of the physical web.  Well that would be good, and a much better use of our resources.  The alternative is to sit and wait to see if Apple do anything, but that’s not productive.

Hello everybody, I have great interest to participate in this group, we are
currently with our platform 100% operating with the URLs eddystone in
Brazil 94% of the base of smartphones is Android then gets easier, but it
is obvious that if iOS the nearby was via Google maps, we would have more
success, since Safari already comes pre installed. I am available to help
somehow.
Em 01/11/2017 11:19, "Agustin Musi"<EMAIL_ADDRESS>escreveu:

I am very glad to see a few companies and people with a strong interest in
building a path forward for the Physical Web Eddystone URL. With ubiquitous
iOS adoption as a key goal, at least from my side, the likelihood of
success is higher if we plan to initiate a shared resource strategy on
several fronts.
I have been in discussion with several business leaders that have similar
goals and are open to contributing energy and focus. Not only do they have
an excellent background in their own needs but also some very well thought
out concepts and comments on the limitations and challenges of physical web
and where to go next.
However, despite the earlier message, I don't have anyone on this list as
part of the current working group. A few other people I have contacted
actively have assumed that something would happen to/for them with no
participation. While the "wait and see" attitude works well in some cases,
this is not one of them. We need participants to join the conversation,
drive the criteria and maybe support in collaborative development. If you
see the potential or even want to be part of the group that shapes the
phase 2 of the physical web, please reach out over twitter @auge2u
https://github.com/auge2u or contact me here.
I am bumping the following to suggest participation because you are
feeling a need.
@chiphysler https://github.com/chiphysler @aakashjain
https://github.com/aakashjain @cjzip2016 https://github.com/cjzip2016
@bisaicx https://github.com/bisaicx @derekshull
https://github.com/derekshull @beaconstalk
https://github.com/beaconstalk @luciofr https://github.com/luciofr
What we can do is collaborate and execute for shared value.
rgs
a
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/physical-web/issues/931#issuecomment-341103694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AageQOjUW23OLni0gzg6QPCJFNw2GTctks5syG_mgaJpZM4QBNUQ
.

The physical web protocol was under recognized and under utilized.
Something i wanted to take advantage of going into 2018. I don't think
there are any mainstream apps that are on both ios and android that
businesses can take advantage of like we could with physical web being in
chrome for ios. If anyone knows of an app, please let me know. I would like
if safari could pick up on nearby beacons (whether ibeacon, or eddystone).
This would be a great solution to the current issue. I'm not sure what
action we can take collectively to enable the general smartphone user to be
able to interact with nearby beacons.
What do you guys think?
On Nov 1, 2017 9:19 AM, "Agustin Musi"<EMAIL_ADDRESS>wrote:

I am very glad to see a few companies and people with a strong interest in
building a path forward for the Physical Web Eddystone URL. With ubiquitous
iOS adoption as a key goal, at least from my side, the likelihood of
success is higher if we plan to initiate a shared resource strategy on
several fronts.
I have been in discussion with several business leaders that have similar
goals and are open to contributing energy and focus. Not only do they have
an excellent background in their own needs but also some very well thought
out concepts and comments on the limitations and challenges of physical web
and where to go next.
However, despite the earlier message, I don't have anyone on this list as
part of the current working group. A few other people I have contacted
actively have assumed that something would happen to/for them with no
participation. While the "wait and see" attitude works well in some cases,
this is not one of them. We need participants to join the conversation,
drive the criteria and maybe support in collaborative development. If you
see the potential or even want to be part of the group that shapes the
phase 2 of the physical web, please reach out over twitter @auge2u
https://github.com/auge2u or contact me here.
I am bumping the following to suggest participation because you are
feeling a need.
@chiphysler https://github.com/chiphysler @aakashjain
https://github.com/aakashjain @cjzip2016 https://github.com/cjzip2016
@bisaicx https://github.com/bisaicx @derekshull
https://github.com/derekshull @beaconstalk
https://github.com/beaconstalk @luciofr https://github.com/luciofr
What we can do is collaborate and execute for shared value.
rgs
a
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/physical-web/issues/931#issuecomment-341103694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae8vZ-XTXotD9OrfwJ8grvbteRVZcI5uks5syG_mgaJpZM4QBNUQ
.

Hello all,
The general enthusiasm is strong.
Next step is a clear call to action regarding the initiative and shape.
Essentially the outline of the plan is to create a formal foundation where private people and/or companies can participate with the shared goal of increasing and enhancing adoption with standards to protect the consumer from abuse and give them choice over permission to interrupt or to be notified.
I would like to have a group conf. call with those who are ready to participate and contribute.
The goal would be next week Tuesday, November 7, 4pm – 5pm (GMT+1) which should cover a bridge time frame between Europe and US at least.
This will not be the only option but I am starting with a suggestion.
I will post the follow-up details for an international dial-in and video call if we all see fit.
rgs
agustin

Hello all,
I am ready to participate too, to find the right solution for this issue.
I am in.
2017-11-03 18:05 GMT+01:00 Agustin Musi<EMAIL_ADDRESS>
Hello all,
The general enthusiasm is strong.
Next step is a clear call to action regarding the initiative and shape.
Essentially the outline of the plan is to create a formal foundation where
private people and/or companies can participate with the shared goal of
increasing and enhancing adoption with standards to protect the consumer
from abuse and give them choice over permission to interrupt or to be
notified.
I would like to have a group conf. call with those who are ready to
participate and contribute.
The goal would be next week Tuesday, November 7, 4pm – 5pm (GMT+1) which
should cover a bridge time frame between Europe and US at least.
This will not be the only option but I am starting with a suggestion.
I will post the follow-up details for an international dial-in and video
call if we all see fit.
rgs
agustin
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/physical-web/issues/931#issuecomment-341766565,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aff-U6AEA_Xh92oLtMs1cihzz0IGWJ35ks5sy0fmgaJpZM4QBNUQ
.

I'd like to sit in as well, if I may. I'm not sure how much technical help I can be, but I would love to share whatever advancements are made with a couple other communities.

HI all,
I would be willing to get involved as collaboration for something that should be free to download to increase adoption rates will benefit everyone and all business in the long run.
I have already been considering some elements to a workable and better case for a physical web scanner that would essentially need to work across both Android and IOS.

There has been a lack of clarity from Google in respect of the algorithms they are using to decide what notifications are relevant and which are not, and the "discarding" of notifications having a bearing on its gradually disappearing altogether.  I personally find it ridiculous at this early stage as there seems to be many barriers that are going to hinder momentum for both consumers and business adoption.

I do believe it is important however to reduce spammy notifications.

Ultimately the user should have the choice, and some good examples have surfaced as to why they should not gradually fail to appear just because they have been discarded by people.  What is useful for one person may not be useful o another.
I would consider a series of generalised icons such as Food & Drink, Events, Information, Shopping, Other etc etc.  This would allow a user to select which notifications they would be interested in at the time.  If someone want to receive lots of offers or discounts then that is what they are looking for and it should be available as an option.  If they don't they just turn this option off therefore reducing spam of this type.  It is something that needs consideration but a good place to start.  My platform already uses a specific location based icon for each sector so that it is clearly identifiable.

People, we of TagPoint / TagCity understand that the Eddystone Protocol
will only succeed in iOS if Google puts the Top10 Apps reading this
protocol, otherwise it will be very difficult, iOS Users are "religious"
and will not replace Safari by Chrome, Google needs to put Maps and other
Apps doing this and generating notifications, but ultimately, we rely
heavily on Google so that iOS Users are also impacted.
Our TagPoint Platform already features QRCode features that point to the
Eddystone URL exactly so that iOS users are curious to read the QRCode and
receive the content of the Platform, all the Establishments are directed to
post "Turn on Bluetooth and Location "on posters with the QRCode and
message URL, so we were able to impact more users, including iOS.
We currently use Beacons that simultaneously emit iBeacon and Eddysotne,
what we could do in our iOS Apps (TagPoint and TagCity), would read the
Beacons of the Participants of that Group, so we would increase the base of
Apps that also read using iBeacon.
We are at the disposal of initiatives to add, a strong embrace to all.
Att.
Lúcio Flávio
2017-11-02 8:21 GMT-02:00 infinitybeacons<EMAIL_ADDRESS>
The physical web protocol was under recognized and under utilized.
Something i wanted to take advantage of going into 2018. I don't think
there are any mainstream apps that are on both ios and android that
businesses can take advantage of like we could with physical web being in
chrome for ios. If anyone knows of an app, please let me know. I would like
if safari could pick up on nearby beacons (whether ibeacon, or eddystone).
This would be a great solution to the current issue. I'm not sure what
action we can take collectively to enable the general smartphone user to be
able to interact with nearby beacons.
What do you guys think?
On Nov 1, 2017 9:19 AM, "Agustin Musi"<EMAIL_ADDRESS>wrote:

I am very glad to see a few companies and people with a strong interest
in
building a path forward for the Physical Web Eddystone URL. With
ubiquitous
iOS adoption as a key goal, at least from my side, the likelihood of
success is higher if we plan to initiate a shared resource strategy on
several fronts.
I have been in discussion with several business leaders that have similar
goals and are open to contributing energy and focus. Not only do they
have
an excellent background in their own needs but also some very well
thought
out concepts and comments on the limitations and challenges of physical
web
and where to go next.
However, despite the earlier message, I don't have anyone on this list as
part of the current working group. A few other people I have contacted
actively have assumed that something would happen to/for them with no
participation. While the "wait and see" attitude works well in some
cases,
this is not one of them. We need participants to join the conversation,
drive the criteria and maybe support in collaborative development. If you
see the potential or even want to be part of the group that shapes the
phase 2 of the physical web, please reach out over twitter @auge2u
https://github.com/auge2u or contact me here.
I am bumping the following to suggest participation because you are
feeling a need.
@chiphysler https://github.com/chiphysler @aakashjain
https://github.com/aakashjain @cjzip2016 <https://github.com/cjzip2016
@bisaicx https://github.com/bisaicx @derekshull
https://github.com/derekshull @beaconstalk
https://github.com/beaconstalk @luciofr https://github.com/luciofr
What we can do is collaborate and execute for shared value.
rgs
a
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/google/physical-web/issues/931#
issuecomment-341103694>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ae8vZ-
XTXotD9OrfwJ8grvbteRVZcI5uks5syG_mgaJpZM4QBNUQ>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/physical-web/issues/931#issuecomment-341377292,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AageQDpx6tQDfmr2wZ_ngdWrsMkpA4uGks5syZe1gaJpZM4QBNUQ
.

Hi all.
We have the seeds to escort this tech over the chasm from "high tech" to "boring ol' utility" and high consumer value.
For the moment, let's call our shared efforts "PhysicalWeb2" and make these statements;

PW should remain an active solution for universal access of proximity resources
Eventually, we may try to add controls for notification filtering (category or region based)
We would like ubiquitous iOS adoption (cross-platform PW access)

My personal priorities of the PhysicalWeb2 mission would be to enhance adoption of BLE PW, drive value creation awareness, influence the path of broad adoption with press/PR/ads, build a unified strategy for the balance of consumer notification control, provide access, develop standards, decentralized control, and stability.
The purpose of a call is to determine who is interested in active participation vs. supportive participation, have an initial bonding goal setting discussion, and validate the immediate steps for action.
SLACK
I have opened a slack workplace under This link
I have scheduled a meeting for 4 pm GMT+1
US Pacific Coast is 7 am
Eastcoast 10 am
New Zealand is 9 pm
The time selection was intended to create the broadest options for inclusion.
Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap :
Switzerland: +41315280988,,275157386#
Or Telephone：
Dial(for higher quality, dial a number based on your current location)：
Switzerland: +41 (0) 31 528 0988
US: +1<PHONE_NUMBER>  or +1<PHONE_NUMBER>  or +1<PHONE_NUMBER>
Brazil: +55 11 4680 6788  or +55 21 3958 7888
Hungary: +36 1 701 0488
Germany: +49 (0) 30 3080 6188
Mexico: +52<PHONE_NUMBER>
Sweden: +46 (0) 8 4468 2488
United Kingdom: +44 (0) 20 3695 0088
Netherlands: +31 (0) 20 241 0288
Israel: +972 (0) 3 978 6688
Italy: +39<PHONE_NUMBER>
Estonia: +372 880 1188
Denmark: +45 89 88 37 88
Canada: +1<PHONE_NUMBER>
Australia: +61 (0) 2 8015 2088
Spain: +34 91 198 0188
Russia: +7 (0) 49 5283 9788
Japan: +81 (0) 3 4578 1488
Meeting ID: 275 157 386
: More International numbers available here
Looking forward to meeting you or seeing you on Slack.. or both.  :)

Custom Browser is the new solutions, supports ibeaon, alt beacon and
eddystone. Plus integrates with Chrome & Safari.
Other Function

A.R.
V.R.

There is an application called Phy Browser that still works for iOS for
nearby physical web beacons. Would be great to have a non profit
organization dedicated to making a similar browser and handling all of the
promoting of the app etc.
On Nov 5, 2017 2:09 PM, "Tauta2"<EMAIL_ADDRESS>wrote:

Custom Browser is the new solutions, supports ibeaon, alt beacon and
eddystone. Plus integrates with Chrome & Safari.
Other Function

A.R.
V.R.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/physical-web/issues/931#issuecomment-341996884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae8vZ4VJfwws6WIJcpN-2wRmCQepHkF9ks5szgfRgaJpZM4QBNUQ
.

I followed the evolution of PW since the start, and I'm also the developer of the Beacon Toy app used by many people to create virtual beacons on supported Android phones. As you can see nobody from Google is getting himself involved in the discussions here. I believe a few of you are losing the original idea behind why Eddystone scanning was built into Android Nearby - no need for a dedicated app. PW is just a URL-based subset of the Eddystone standard. It sounds a lot like what some of you are trying to do is to go the opposite route, of building a "universal app" to scan. This idea already failed, unless you only heard about beacons since yesteday. Unless you guys convince Apple to integrate Eddystone scanning as a core iOS feature you cannot possibly accomplish anything. As for Android, you already have Nearby APIs, the fact that some of you consider Nearby Notifications as a "black box" when it comes to filtering URLs doesn't really do it justice. Is it buggy? Sure, but there are so many technical issues to workaround, that any initiative would be as buggy. I mean, we're talking about Google here, not a startup's attempt of some viral app. People that want to see all the beacons around them will find the tools to do so. Imagine what the experience would be if all NFC tags had a range of 30 meters instead of a few mm?

Totally agree with adiancretu. Then from this point it is up to iOS users to choose one of the existing applications to scan for Physical Web URL's and mobile applications with ibeacons and Android users Nearby (Samsung)...Newly built QR scanner can not replace Physical Web for iOS due to fact it is not long range, but it can deliver the same content as Physical Web URL. What would be good pitch to use from now on for iOS users regarding Physical Web if any or just focus on mobile applications with ibeacons?

Adrian, the physical web capability is more useful in my opinion because it
lets users across platforms discover links; and customizable messages can
also be created through the meta tags for the URL. The Google api is cool
in it's way, but it is not cross platform. I would much rather keep
physical web capability on both iOS and Android. I think most here are here
for that reason, not to move on to Google api. Physical web was largely not
understood, and I think most people were not aware of the meta tag method
to change the messages associated with the url.   For these reasons,
physical web was much more than just a url broadcasted.
On Nov 5, 2017 11:43 PM, "AndyShelly"<EMAIL_ADDRESS>wrote:

Totally agree with adiancretu. Then from this point it is up to iOS users
to choose one of the existing applications to scan for Physical Web URL's
and mobile applications with ibeacons and Android users Nearby
(Samsung)...Newly built QR scanner can not replace Physical Web for iOS due
to fact it is not long range, but it can deliver the same content as
Physical Web URL. What would be good pitch to use from now on for iOS users
regarding Physical Web if any or just focus on mobile applications with
ibeacons?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/physical-web/issues/931#issuecomment-342045248,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae8vZ9t1wL-Tbg2PKt3id1_22LoqVGAzks5szo5jgaJpZM4QBNUQ
.

I agree with infinity beacons here too.  Adrian in a perfect world (for those of us involved with beacons) all we need to do is persuade Apple to integrate it.  Great in theory but probably quite a task.  Why google have pulled it personally I feel is silly as in the UK as I stated IOS is dominant.
It would be SO much harder to promote when immediately I am losing over 50% of a customer base.  Asking people to do one thing for one system and one thing for another starts to re-introduce the friction process.
The physical web is about being “app free” but this is more about users being able to communicate with multiple sources (or companies and things) without the need for a dedicated app for each and everyone.  If it means going away from the principle by having one identifiable scanner across platforms then I would be happy to take a step backwards in this respect.
My other reason for this is this:  If business are spending time and money to develope their ideas, only to have Google or Apple one day wake up and say.....let’s drop it!!! Where do we stand?  To much dependancy.  I had been looking at creating my own scanner up for some time, now it seems we have been given a push to do so......as google keep saying and as Scott Jensonreplied in August when he first told me he was no longer involved....it’s in our hands now.

In regards to a marketing effort I think the barriers for this are high as we are seemingly spread across the globe and to market greatly on such a scale will cost millions.  Starting with a simple product that businesses can implement should be enough to get the ball rolling.

I think it would be good if we could develop a common API that can be easily integrated into existing apps of any kind. Thus, we could ensure a further spread and adoption rate of Eddystone Beacons.
At the same time, as @craigahunter mentioned, we should develop a Beacon scanner app with a uniform branding, which can be extended by adding additional features and own branding. Because surely some companies (like mine, for example) want to implement functions that may not match the existing app. Parts of these adaptations could of course be made available to the general public again.
We have a working Android (written in Kotlin) and a beta iOS app (rejected in the App Store) as a base, but it currently uses a webview to display the beacons and displays our FriendChip website in it. This part would have to be removed and a native display of the beacons would have to be developed. We would like to make this app available for further development.
In order to display metadata such as title and description for the beacons found, we need a metadata service.
It is essential that the same metadata service is used everywhere, so that no company has control over which data is displayed and which is not, as Google does with the current implementation. This is the only way to achieve widespread distribution.
The metadata service will cost money and must be developed further.
We currently have our own metadata service based on https://github.com/mozilla-magnet/magnet-metadata-service on Heroku.
Mozilla Magnet is an implementation in Nodejs of a Physical-Web metadata service.
Unfortunately, the project doesn't seem to be actively maintained at the moment. The last commit is dated November 3,2016.
Who bears the costs for hosting?
We also thought a lot about how to get a better display of nearby beacons on Android.
I will try to communicate this to the Android team somehow, does anyone have direct contacts to the developers of the Nearby Notifications?
For example, Ryan Bavetta from the Nearby Notifications Team (see this video https://youtu.be/1a0wII96cpE?t=379)
However, I also have some concerns and questions:
It takes a lot of effort to coordinate a group of people.
Collaboration tools need to be set up, which tools are needed?
Is github enough?
There may be different opinions on how things should work in an App/API.
How should decisions be made? Via voting system? Is github enough?
Who can participate?
Under which license should the app or API be released?
Who pays the costs?
Who takes over which tasks?
How do we get the notifications on iOS?
I hope we can answer some of these questions here or at the @auge2u meeting or in the slack channel @auge2u mentioned.

Hello
My name is Abhishek Kanodia, from India.
I have been following physical web since July 2015. Like a lot of people here, I was also a big believer of this technology. Hence, I spent nearly 2 years of all my time and effort promoting it and building applications and use cases around it.
I launched multiple pilot runs on it through physical web on chrome ios, physical web inside chrome android, and nearby notifications. The range of pilot runs covered providing exclusive deals at events, retail stores to tracking assets in a FMCG supply chain.
And of course, I had thought and ideated about a lot more possible use cases regarding physical web
During my 2 years, I had spoken to 10000+ people about this technology, given demo and interacted with users.
But, after all my efforts, and failing multiple times on this technology, I sort of lost my belief on it.
The technology no doubt is charming and fascinating, more so because of its app less nature, but to be honest, this technology can only work when people switch on bluetooth and know what is it. We are easily talking at-least 4-5 years in future.
Expecting people to switch on bluetooth and then using physical web is not going to happen on its own. There needs to be a complete ecosystem built like wifi, where people know what is physical web, just like wifi.
Hence, to conclude, the odds against it are very high, especially in the next 4-5 years
THanks
Regards
PS: If people need any insights on my experience regarding physical web, I ll be happy to share

Hey @auge2u and @jmartsch,
are you still working on the stuff you described? I just discovered your discussion, but unfortunately the Slack URL does not work anymore.
Some time last year as a result of Google Chrome dropping Physical Web I developed a Physical Web browser for iOS so I am really interested in your efforts and would like to brainstorm, how I can support or how we can work together on this matter.
Regards
Manuel

This is too bad, especially since Google still has not updated the https://google.github.io/physical-web/try-physical-web#ios about this change.
I do feel like this technology has a future, especially to whisper something to a potential customer that is just passing along.

Reading through this thread, why do you want Google to solve Apple issues. Google should not be bailing out Apple again.  Apple should  smell the coffee and do something with their IBeacon. Oh but maybe they are so busy with their own self importance?
Downloading an app to scan a beacon is not an option. The mobile user should only have bluetooth enabled and automatically receive notifications as with Google's Nearby on Android.
If you are not part of the IOS and or IBeacon Team the chances that you will succeed is pretty slim. This type of technology needs to be integrated into IOS.

We finally launched the https://phwa.io website.
The site should be able to communicate the fundamental value proposition for membership and steer the rationale for participation and allow membership subscription.
"Ready enough" is obviously subjective, but progress is being made and the refreshed version of the PhyWeb iOS app (thanks to James Grant and the initial contributor) is ready for TestFlight invitations for subscribed members.
The membership will provide access to this initial version for feedback, steering, and strategy communication. https://phwa.io/membership/
Extending the initial version with development resources will need some funding and active participation.
The proceeds of the membership fees will go directly toward funding the software development and the coordination of the initial consumer-awareness campaign pilots over the next few months.
We have some interest from both private and some government organizations here in Switzerland, specifically Zurich, Bern, and Basel to develop the smart-city play using Physical Web tech.
If you have some interest in representing PHWA in your area as a local, non-profit, consumer service, please contact me so we can budget and tie press into your project.
In the initial pilot, the PW app and the Android instructions will be promoted with out-of-home advertising (posters and postcards) and press contacts. Please let me know if you can assist with press relationships and/or content in local languages.
In the short-term, signing up to a membership is the easiest way to help us move forward.
The more membership support we have, the more likely we will succeed in creating a perpetual motion to develop further. We will develop and provide hosting services such as a GDPR compliant metadata gateway and reports on adoption with transparency. Additionally, we aim to begin "embracing and extending" the Physical Web standards to solve constraints such as native OS integration, solve the low adoption rates, and to provide more granular content notification controls for consumers.
We have some clear plans and want to help everyone get a positive result.
Best regards from the association founding officers,
Agustin Musi - President
James Grant - Vice President
David Butler - Secretary
Physical Web Association

Just an FYI.
As the end of 2019 is nearly here, this new version of Physical Web is about [faster], [cleaner] code, and [new] options.
Version 2.1 is primarily about providing and establishing an updated code foundation to build the next wave of long-awaited features while providing the first unified experience across mobile platforms.
PHWA iOS URL Browser 2.1
PHWA Android URL Browser 2.1
Took a lot longer than we planned but we have the same trajectory as always.

We agree with your vision and have also created a free Physical Web Mobile Application for both iOS and Android with NO ADS EVER.
Enjoy Everyone!!
https://www.nearbynotifications.org
https://play.google.com/store/apps/details?id=com.nearbynotification.main
https://itunes.apple.com/us/app/nearby-notifications/id1462420406


parser & checker (images to video conversion): parsing the json to retrieve information about tiff images

User Story
I want to convert any .TIFF image to AVI and MP4 types video.
so that i can use these data for WF NTP
To do so, I need to parse an argument being supposely the path to the directory containing:

several tiff images
1 json which may be metadata concerning the video settings.

This part is dealed in the issue #17 and is the first step realised by the execution of:
python -m converter --path [path_arg]

Based on path_arg I want that the program converter.py to parse the json file and retrieve the different information to check the validity of the tiff files.
The handle of the variable frame rate is tricky (related issue: #24 ). Thus to level of development is expected:

average the frame rate a construct a video with this average.
use the instant frame rate

It may be important for futur analysis to keep a track of the instant frame rate. Two choices are possible:

generate a json with the time interval between consecutive frame
develop the functions to easily retrieve this information from the json file containing the metadata video.
This choice is at the developper discretion.

Acceptance Criteria

based on the json file check if

[x] .tiff files are valid (may need to check if there is header in tiff file and check it).
[x] .tiff files are of the same size
[x] .tiff files have the same pattern (or the name is identical to those one can find in the json)
[x] there is no missing tiff
[ ] check minimum number of files to convert (100 files)
[ ] retrieve frame rate from the json file.

Definition of Done

[ ] Product Owner accepts the User Story
[ ] Acceptance criteria met

Defined by CICD:

Code reviewed
black compliant
Unit tests passed
Functional tests passed
Non-Functional requirements met

@COTHSC user story is updated

@COTHSC and @rcatini, for the tests you can perform some of them to start with the URI:

s3://lab-nematode/tests/test_1/   is valid
s3://lab-nematode/tests/test_2/ is invalid because name of a tiff is modified
s3://lab-nematode/tests/test_3/ is invalid because a file tiff has been deleted
s3://lab-nematode/tests/test_4/ invalid because the size of an image has been modify in the metadata.json

Instead of a list of the time intervals between the frames, it could be better to have a dictionary with the format
dict =	{   "filename0.tiff": interval0_ms,   "filename1.tiff": interval1_ms,   ...,    "filenameN.tiff": intervalN_ms, }
where interval0_ms is equal to 0.


fix: update comments component incase of no provider

Incase if someone does not have any commenting platform enabled, the code will still show the Load Comments button.
This PR fixes it and only shows the Load Comments button if a commenting platform is provided.

@timlrx please be so kind to have a look at this PR.

There's an error in the deployed build:
Error:
  x An object member cannot be declared optional
    ,-[/vercel/path0/components/Comments.tsx:11:1]

Could you fix it and ensure that it builds without error?

@timlrx Fixed it! Thanks ✌

Thanks for the fix!


AS3 does not respect line breaks in iRules

ISSUE TYPE

Bug Report

AS3 BUILD/ VERSION

3.5.0-3

BIGIP VERSION

BIG-IP 13.1.1 Build 0.0.4 Final

SUMMARY

The JSON parser does not appear to respect line breaks "\n" in multi line iRules
This is important because TCL syntax is line break aware
STEPS TO REPRODUCE

POST this example declaration with a mutli-line iRule
{
    "class": "AS3",
    "action": "deploy",
    "syncToGroup": "/Common/Sync-Failover",
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.5.0",
        "id": "error-codes",
        "label": "iRules and pools for http status",
        "test_tenant": {
            "class": "Tenant",
            "shared_app": {
                "class": "Application",
                "template": "shared",
                "test_irule": {
                    "class": "iRule",
                    "iRule": "# 503 for service unavailable\nif {[active_members [LB::server pool]] < 1} {\n  if {[HTTP::path] eq \"/robots.txt\"} {\n    HTTP::respond 200 content \"<title></title>User-agent:*
Disallow:/
\"\n  }\n  else {\n    HTTP::respond 503 content [ifile get 503.html] \"Content-Type\" \"text/html\"\n  }\n}\n"
                }
            }
        }
    }
}

EXPECTED RESULTS

message: success
host: localhost
tenant: test_tenant
code: 200
ACTUAL RESULTS

  "results": [
    {
      "message": "declaration failed",
      "response": "[active_members unknown property",
      "code": 422,
      "host": "localhost",
      "tenant": "test_tenant",
      "runTime": 1527
    }
...

Hello @ColinHeathman , thanks for reporting, we are looking into this.

Hey @kaustriaf5, I'm thinking this is just from my iRule being invalid.... Sorry about that.
Maybe "message": "invalid iRule declaration" would be a more helpful error message

@ColinHeathman no problem and thanks for the feedback, we will look into making the error message specific, maybe something like:
"message": "invalid iRule declaration: [active_members unknown property "

This is tracked internally as 638.


added resources to Problem & Tips, Video Tutorials, Interview Prep

In the problems & tips added a new blog named "Getting Started with CP"
In the Video tutorials added a new channel named "take U forward"
In the Interview prep added a new blog named "Guide For Interview Prep"
Also added a new section named Interview experiences
All the changes are made in the last line of each section.

Hey @kunal-kushwaha Could you please look into this PR? If you find it useful then you can merge it.


.NET 8 and Native AOT approach

Description
If I publish my code in Native AOT then all parts of code which are related to Kafka usage (such as: Producers and Consumers) stopped working. I have got the next message in Console after running published to native AOT app
Unhandled Exception: System.InvalidOperationException: Sequence contains no matching element
   at System.Linq.ThrowHelper.ThrowNoMatchException() + 0x2b
   at System.Linq.Enumerable.Single[TSource](IEnumerable`1, Func`2) + 0x27
   at Confluent.Kafka.Impl.Librdkafka.SetDelegates(Type) + 0xdb
   at Confluent.Kafka.Impl.Librdkafka.TrySetDelegates(List`1) + 0x16
   at Confluent.Kafka.Impl.Librdkafka.LoadNetStandardDelegates(String) + 0xb2
   at Confluent.Kafka.Impl.Librdkafka.Initialize(String) + 0xd0
   at Confluent.Kafka.Producer`2..ctor(ProducerBuilder`2) + 0x19d
   at BLL.Core.KafkaService..ctor(IServiceProvider serviceProvider) + 0x1f5
   at WebApplication1!<BaseAddress>+0xcf395d
   at System.Reflection.DynamicInvokeInfo.InvokeWithFewArguments(IntPtr, Byte&, Byte&, Object[], BinderBundle, Boolean) + 0x95
   at System.Reflection.DynamicInvokeInfo.Invoke(Object, IntPtr, Object[], BinderBundle, Boolean) + 0x11d
   at Internal.Reflection.Execution.MethodInvokers.InstanceMethodInvoker.CreateInstance(Object[], BinderBundle, Boolean) + 0x44
   at Internal.Reflection.Core.Execution.MethodBaseInvoker.CreateInstance(Object[], Binder, BindingFlags, CultureInfo) + 0x3b
   at System.Reflection.Runtime.MethodInfos.RuntimePlainConstructorInfo`1.Invoke(BindingFlags, Binder, Object[], CultureInfo) + 0x55

I'm using a very simple code which works in regular published app:
IDictionary<string, string> config = new Dictionary<string, string>()
{
    { "bootstrap.servers", BootstrapServers },
    { "socket.max.fails", "0" },
    { "message.send.max.retries", "10" },
    { "batch.num.messages", "1000000" },
    { "queue.buffering.max.ms", "1" },
    { "request.timeout.ms", "2000" },
    { "message.timeout.ms", "5000" },
    { "client.id", Dns.GetHostName() }
};

//     -->  This line of code throws an exception  <--
_producer = new ProducerBuilder<Null, byte[]>(new ProducerConfig(config)).Build();

OS -> Windows 11
Nuget package is the latest one on the current moment
Confluent.Kafka, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=12c514ca49093d1e
How to reproduce

Create a new ConsolApp project (.NET 8) using Visual Studio, VS Code, or just using terminal
Install Nuget package (Confluent.Kafks <IP_ADDRESS>)
Add the next lines into .csproj file

<PublishAot>true</PublishAot>
<PublishReadyToRun>true</PublishReadyToRun>
<PublishTrimmed>true</PublishTrimmed>

Use my code I provided above to try to create Producer (there are required minimum changes)
Publish App using the next command (terminal should be open from the path where .csproj file is located)
dotnet publish -c Release -o "otput_path_where_app_will_be_published"
Run published app and check the error

Checklist
Please provide the following information:

[x] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[x] Confluent.Kafka nuget version.
[ ] Apache Kafka version.
[ ] Client configuration.
[x] Operating system.
[ ] Provide logs (with "debug" : "..." as necessary in configuration).
[ ] Provide broker log excerpts.
[ ] Critical issue.

Hello, not sure if it will help but I managed to make it work on windows aot by changing only one line
        private static void LoadNetStandardDelegates(string userSpecifiedPath)
        {
            if (userSpecifiedPath != null)
            {
                if (WindowsNative.LoadLibraryEx(userSpecifiedPath, IntPtr.Zero, WindowsNative.LoadLibraryFlags.LOAD_WITH_ALTERED_SEARCH_PATH) == IntPtr.Zero)
                {
                    // TODO: The Win32Exception class is not available in .NET Standard, which is the easy way to get the message string corresponding to
                    // a win32 error. FormatMessage is not straightforward to p/invoke, so leaving this as a job for another day.
                    throw new InvalidOperationException($"Failed to load librdkafka at location '{userSpecifiedPath}'. Win32 error: {Marshal.GetLastWin32Error()}");
                }
            }

-            TrySetDelegates(new List<Type> { typeof(NativeMethods.NativeMethods) });
+            SetDelegates(typeof(NativeMethods.NativeMethods));
        }

Having the same issue here (Publishing as trimmed, no AOT).

Any updates from the team on this?

Any updates on this?


Check for toolbar config being passed in through props, remove default array

This will check to see if a toolbar config is sent through the props and remove the defaults that are being merged in to the ultimate config.
@pdesmarais would you mind testing?
Resolves #16

Hey @BrockReece !
Sorry for the LONG delay! Was caught in other things in my project.
I finally did get around to testing this. Works perfectly! Tested with my config (which is really basic) and without a config (which brings the default toolbar).
All good! Good work!

@pdesmarais, perfect thanks.
I will get it merged in and write some release notes.

Released in v1.4.0


Nested where clause generating incorrect SQL

Describe the bug
I have a schema that stores sporting events with a startTime and home/away teams.  I want to query for upcoming games for a particular team so have a where clause that looks something like this:
{
   "$and":[
      {
         "startTime":{
            "$gt":"2020-10-13T20:11:12.234Z"
         }
      },
      {
         "$or":[
            {
               "homeTeam":{
                  "id":"3001f525-fb45-47c7-aabf-58b6b99ac0d4",
               },
               "awayTeam":{
                  "id":"3001f525-fb45-47c7-aabf-58b6b99ac0d4",
               }
            }
         ]
      }
   ]
}

it appears to be generating a query that looks like:
select `e0`.* from `event` as `e0` where `e0`.`start_time` > '2020-10-13 15:12:32.676' and `e0`.`home_team_id` = '2fc2ae1d-53e4-4e98-9e70-0d35e85d16dd' and `e0`.`away_team_id` = '2fc2ae1d-53e4-4e98-9e70-0d35e85d16dd'

however I would expect something like:
select `e0`.* from `event` as `e0` where `e0`.`start_time` > '2020-10-13 15:12:32.676' and (`e0`.`home_team_id` = '2fc2ae1d-53e4-4e98-9e70-0d35e85d16dd' OR `e0`.`away_team_id` = '2fc2ae1d-53e4-4e98-9e70-0d35e85d16dd')

Versions

Dependency
Version

node
v14.5.0

typescript
3.8.3

mikro-orm
4.0.7

your-driver
sqlite

Your query is wrong, you have only one item in the $or array, this is what you need:
{
  "$and":[
    { "startTime":{ "$gt":"2020-10-13T20:11:12.234Z" } },
    {
      "$or":[
        { "homeTeam": { "id":"3001f525-fb45-47c7-aabf-58b6b99ac0d4" } },
        { "awayTeam":{ "id":"3001f525-fb45-47c7-aabf-58b6b99ac0d4" } }
      ]
    }
  ]
}

Yep you're right, that was the issue, sorry for the noise.


Ionicons font issue in 2.7.1 release

node, npm, react-native, react and native-base version

node v8.11.1
npm 5.6.0
react 16.3.2
react-native 0.53.0
native-base 2.7.1

Expected behavior

Icons of type Ionicons renders as expected

Actual behavior

Questionmark renders instead of an expected icon

Steps to reproduce should include code snippet and screenshot

Upgrade/install NativeBase 2.7.1
Use the following icon:
<Icon name="ios-cart-outline"/>

Is the bug present in both iOS and Android or in any one of them?

Checked only in iOS

Any other additional info which would help us debug the issue quicker.
I blame recent fonts update because if you replace Ionicons.ttf with a font from 2.7.0 branch Ionicons icons renders OK. As only you revert font from 2.7.1 the problem shows up again.

yes the icon names with *-outline are not rendering with vector icons

Commits 951f154, f93b115 fixed this

When will those commits be available in release branch?

Fixed with 2.7.2


Container/app crashing after downloading larget data sets

Please provide us with the following information:

This issue is a: (mark with an x)

[x ] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
I have a Container App running with a mounted 200GiB mounted file share (StorageV2, LRS).
Number of CPU cores: 0.25 and Memory size (Gi): 0.5Gi
The file storage shows a quota of 200Gib, and a maximum capacity of 5 TiB, currently only about 30mb used.
The app downloads large data sets on request as a gz file than uncompresses and reads the file.  The files uncompressed is about 230-250MB. When i run this process locally, it works fine.
When this process is run on the container hosted in my  azure Container App env, it downloads the data as a gz file, but then the process appears to crash when it tries to read the file.
The trigger for the downloading of the data is a simple flask app.  But on the portal, after the file is downloaded, i see the following in console:
./start.sh: line 9:     8 Killed                  flask --app /apps/data_svc/web/app.py run --host=<IP_ADDRESS>
I cannot find anything in the app logs or in the logs or metrics on azure portal that is giving me a hint as to cause.
Any suggestions on how to go about debugging this issue?  Does the memory size above above for my container app seem reasonable for this process?
Thanks for any help or hints in resolving this issue.

are you buffering the content in memory anywhere during download or decompressing? You can check system events if the kill was due to memory (it would have an OOMKilled event if that was the case). That would be my first guess at least.
You could also rule that out by trying to increase your memory request on the app and see if that works.

are you buffering the content in memory anywhere during download or decompressing? You can check system events if the kill was due to memory (it would have an OOMKilled event if that was the case). That would be my first guess at least.
You could also rule that out by trying to increase your memory request on the app and see if that works.

Scaling the container app to .5/1 failed.  Scaling to 1/2 worked.  So it does seem to be memory.
Related.  Where would this OOMkilled event be logged or how would I query for this?  The metrics I looked at did not really show anything alarming.  The diagnostic tab showed the failure, but just a generic message to look at logs ..nothing really helpful

Most of the usage of this app is fine at .25/.5.
It's only the download and processing, which happens once a day, that is problematic.
My thought then was that maybe I could dynamically spin up a second container app based on the first, but scaled up, trigger the download and processing activity, then scale it to 0 replicas....all the while the first container app remains active to serve requests.
Is that feasible?  What would be the best way to go about doing this?

Jobs would probably be the best solution if you have control over the app: https://learn.microsoft.com/en-us/azure/container-apps/jobs?tabs=azure-cli

Jobs would probably be the best solution if you have control over the app: https://learn.microsoft.com/en-us/azure/container-apps/jobs

ah interesting. i did not know about this.  it seems though from the docs that you either use that or container apps.  will give it a try

It is just a "special" kind of container app. It can be started on a schedule and it is stopped when container is done its work. It is not always running like ordinary container app. Everything else is more or less the same.

It is available in ARM, not sure if it is also available in the portal or CLI

It is available in ARM, not sure if it is also available in the portal or CLI

i dont see an options using the CLI:  https://learn.microsoft.com/en-us/cli/azure/containerapp/job?view=azure-cli-latest#az-containerapp-job-create
im assuming if its available in arm, then perhaps it may be supported via terraform + azurerm or azapi.  i hope...

@dss010101 It's available in ARM/Bicep and TF AzAPI: https://learn.microsoft.com/en-us/azure/templates/microsoft.app/jobs?pivots=deployment-language-arm-template
In CLI, volumes are currently supported via YAML when you use az containerapp job create/update.
In portal, currently, you can't configure a volume when creating a job. However, it's available when you edit the job container:


Fix importing linked packages

Resolves #1661 and backports #1359

Does this work in tests?

Forgot that we probably need an equivalent in Jest for this 😅.
Will look into it.

Yea, we need testing to be 100% consistent with browser bundling.

We need to add tests which validates the linked functionality.


Ask geo permission only when the map is mounted/rendered

RN 0.46.4, react-native-maps 0.15.3
As soon as I open the app it's asking for geo permission, is there a way to show it only when the component with the map is being mounted/rendered for the first time?
Thanks 😄

Any hint on this? 😄

I need this too :(

https://github.com/react-community/react-native-maps/issues/209#issuecomment-350907665

@alvelig why did you close this?
Your comment is about "showing the user location" which is different than the subject of this issue.
This issue is about asking the geo permission popup on request rather than automatically when the app is loadded and/or the map is mounted.
I'm talking about this, if it's not clear:

Removing showsUserLocation prop did it for me, it asks for location permissions immediately it seems.


Deploy vsp from daemon v2

Pass a list of vsp images to config Daemon as env variables.
Once these images are built internally, they will be set in manager.yaml. Until this time, the default will be to leave these variables unset.
If these images are set, the daemon should deploy the vsp ds. Otherwise, the daemon should deploy as before.

@bn222 @wizhaoredhat This is ready for review.
Only work outstanding from this PR is to add proper platform detection for dpu mode daemon: https://github.com/openshift/dpu-operator/pull/128/files#:~:text=// TODO%3A We need to also detect the platform in dpuMode

/retest

/retest

Noting this PR will require a change in CDA to first be merged, and updated here: https://github.com/bn222/cluster-deployment-automation/pull/257

ci passed https://net-hw-ci-jenkins-csb-nst.apps.ocp-c1.prod.psi.redhat.com/job/99_E2E_IPU_Deploy/22/

/override ci/prow/e2e-dpu-operator-tests


Caching behavior/rules with ARM or Powershell

Are there options to set caching behavior with ARM templates? I see only queryStringCachingBehavior is supported

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

ID: 2c83339e-38d0-e504-4410-9112b3325bdf
Version Independent ID: a6544c01-4cb2-22d8-7e1e-81e4ce6a4ee4
Content: Control Azure CDN caching behavior with caching rules
Content Source: articles/cdn/cdn-caching-rules.md
Service: cdn
GitHub Login: @mdgattuso
Microsoft Alias: magattus

@robynt34  When working with templates, it is always best to use the portal or Powershell / CLI to make the change, and then use Resources.Azure.Com to see what happens with the JSON. You can compare the difference to see how templates would like to receive the new data.

I've used portal to make the change and found no CLI instructions. The JSON at resources.azure.com does not change after this. Can you confirm "Caching behavior" is only editable through portal?
"Query string caching behavior" is not applicable for this situation

With "Caching behavior"="Bypass cache" and "Query string caching behavior"="Ignore query strings" my json is:
{
"name": "",
"id": "/subscriptions//resourcegroups//providers/Microsoft.Cdn/profiles//endpoints/",
"type": "Microsoft.Cdn/profiles/endpoints",
"tags": {},
"location": "WestUs",
"properties": {
"hostName": ".azureedge.net",
"originHostHeader": ".blob.core.windows.net",
"provisioningState": "Succeeded",
"resourceState": "Running",
"isHttpAllowed": true,
"isHttpsAllowed": true,
"queryStringCachingBehavior": ""BypassCaching",
"originPath": null,
"origins": [
{
"name": "-blob-core-windows-net",
"properties": {
"hostName": "*****.blob.core.windows.net",
"httpPort": 80,
"httpsPort": 443
}
}
],
"customDomains": [],
"contentTypesToCompress": [
"text/plain",
"text/html",
"text/css",
"text/javascript",
"application/x-javascript",
"application/javascript",
"application/json",
"application/xml"
],
"isCompressionEnabled": true,
"optimizationType": null,
"geoFilters": []
}
}

@robynt34 I do not believe there is a way at this time to do this with templates. If you would like to add this functionality in the future, please leave your feedback Here.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Add this within your endpoint in the template
"deliveryPolicy": {
"description": "",
"rules": [
{
"order": 1,
"conditions": [
{
"name": "UrlPath",
"parameters": {
<EMAIL_ADDRESS>"#Microsoft.Azure.Cdn.Models.DeliveryRuleUrlPathConditionParameters",
"matchType": "Wildcard",
"path": "/myPath/*"
}
}
],
"actions": [
{
"name": "CacheExpiration",
"parameters": {
<EMAIL_ADDRESS>"#Microsoft.Azure.Cdn.Models.DeliveryRuleCacheExpirationActionParameters",
"cacheBehavior": "Override",
"cacheDuration": "14.00:00:00",
"cacheType": "All"
}
}
]
}
]
}


Add link to imprint and privacy policy

Description
Add a link to the imprint and privacy policy to the dApp
Acceptance criteria

The link is called "Privacy Policy, Disclaimer & Imprint"
It needs to be accessible from every page

Tasks

[ ]

Story Points

@christianbrb there is either one or two places at most where we have to add it for it to be available all across the dApp.


TensorFlow 2.8.0 compatibility

tensorflow_decision_forests is not yet compatible with the (just released) TF 2.8.0 and python3.10
Is the compatibility planed for the near future or should we stick to TF 2.7 and python<3.10? Thanks!

You are right, and we are working at it, and apologies for the delay. Very
soon we'll have a TF 2.8.0 compatible version.
On Thu, Feb 3, 2022 at 12:28 PM JC Louis @.***> wrote:

tensorflow_decision_forests is not yet compatible
https://github.com/tensorflow/decision-forests/blob/main/configure/setup.py#L31
with the (just released) TF 2.8.0
Is the compatiblity planed for the near future or should we stick to 2.7?
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/decision-forests/issues/80, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABY5KE4C77DDRW2NSXQJ55DUZJRERANCNFSM5NOU54VQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Jan Pfeifer
Research Engineer
Google Switzerland GmbH
@ : @.***
@ : @.***
T : +41 79 907 3855

Updates

TF-DF 0.2.4, compatible with TF 2.8, was released today.
The Linux pypi package was published.
The MacOS pypi package will be published in a few hours.

thanks!

https://github.com/tensorflow/decision-forests/pull/83


Fix issues from FutureThinking testing comments

I've fixed the small mistakes people have pointed out, but I will email you the ones I couldn't solve on my own.

Please see the attached document for task details
Future Thinking comments.docx

I'm closing this out, as we intent to pull Future Thinking at R01 launch.


Helm-Chart for Mattermost Enterprise 9.5.6?

As per the Security updates listed, there is MMSA-2024-00345 with a Severity of "high" and fixed version 9.5.6, but the latest Helm Chart I could find for ESR versions is
version: 2.6.47
appVersion: 9.5.2
The next chart version 2.4.8 is having the app version 9.6.0 already.

Waiting for 9.5.7 (ESR)...

Indeed, in the meantime there was an update for 9.5.x

@amyblais

We have a ticket open to investigate this.

https://nvd.nist.gov/vuln/detail/CVE-2024-39274

That NIST link certainly provides usefule information...
Yet, this issue was not about why to update but about that updating using this path of deployment wasn't (easily) possible...
In the meantime the release has already moved on to 9.5.8...


is there any simple way to filter property name that is in some time in lower case and sometimes in upper case and time mix of both?

i have a case where our different applications write same property in a different way like I have a property called "User ID" and our applications some write-in camel case (UserId) sometime pascal case (userId) and some time like this UserID, sometimes like this "userid"
Here are some examples

Everytime when i need to filter user, i use query like this
userId = 'xyz' or UserId ='xyz' or userid='xyz' or Userid='xyz'
So, is there any simple solution?

Hi Muhummad! There are a couple of options, I don't know if either is a vast improvement on what you have, but you should be able to use:
'xyz' in [userId, UserId, userid, Userid]

Or, since they're GUIDs an unlikely to clash with too many other values, you could try:
@Properties[?] = 'xyz'

(I.e. where any property of the event is the value xyz.)
Hope this helps,
Nick

@nblumhardt Thanks for quick response,
it's working as required, just one more thing related to property values i have a case like this
Environment = 'QA' or Environment = 'Qa' or Environment = 'qa'
as you can see property name is same but values are in different formates, is there any easy solution?

👍 -- for better or worse, like is the case-insensitive comparison:
Environment like 'QA'


[Kraken] Multiple currency pairs not supported for the book subscription message

An instance of KrakenStreamingMarketDataService.getOrderBook() does not support subscribing to multiple currency pairs.

What happens when you try to do this?

Apologies, this is a non-issue. User error :)


webkit would like flexibility to throttle rect computation to scroll event frequency instead of requestAnimationFrame frequency

Pending hearing from smfr whether webkit actually throttles scroll separately from requestAnimationFrame.

We think running at the same frequency as scroll events is reasonable, but the current spec, which we agree with, has scroll events firing at the same frequency as requestAnimationFrame.
The open work here is to merge the following section into the html spec. http://rawgit.com/WICG/IntersectionObserver/master/index.html#event-loop
That points to https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-8. Section 7.5 runs the scroll steps and 7.9 runs requestAnimationFrame.
I think we should keep the spec as is for now. If folks want to be able to change this, then I think the work to do is to change the HTML spec to not require firing scroll events in sync with requestAnimationFrame.


Sound Classifier: Feature Extraction using TensorFlow

Since we're changing this unconditionally, should we now also make Turi Create formally depend on TensorFlow? (To the best of my knowledge, we haven't done this yet, right?)

@nickjong - That's a really good point. Yes, I believe we haven't done that yet. I was actually thinking of putting up a seperate PR tomorrow that removes the MXNet dependency and adds the TensorFlow dependency. I could make that part of this PR if you prefer.

Is it safe to depend on both temporarily, while we still have other toolkits that default to MXNet? If so, maybe we can have that as a separate PR that goes in before this one

Is it safe to depend on both temporarily, while we still have other toolkits that default to MXNet? If so, maybe we can have that as a separate PR that goes in before this one

It should be safe to have both TensorFlow and MXNet as dependencies; I smoked tested that a few weeks ago.
Pull request to add TensorFlow: #2541

@TobyRoseman Seems like you might want to rebase against master.

@TobyRoseman Seems like you might want to rebase against master.

Thanks. Done.

@TobyRoseman Seems like there are build failures unrelated to this. Should be good to merge.


Issue on running on sthv2

Hi @huang-ziyuan
We meet problems when running the script on something.
Some abstract methods may not be implemented in somethingv2 dataset class.
The error is shown as below:

It seems to be the problem with PyTorch version later than 1.8.0. These abstract methods are fine without implementation in PyTorch 1.7.1 and before. A quick solution would be to implement the abstract methods to return None, since they are not used in the current version. We will update the code to fit for later versions soon.

Thank you so much. We have solved this problem according your instructions.~


Fix Issue 18887 - inout badly described

Moved the inout section from functions to type qualifiers.

Did you change the content?

Nope, simply copy-pasta. The only thing I added was a link in the inout function section to the new inout type qualifier section.

@RazvanN7 I get that it is only copy-pasta, but it would be nice to have an example of the usage of inout const.


enable field() to handle an object

Allows .field() to behave similar to .set() and handle an object to set multiple key-values. Would it also be desirable to have it handle arrays? i.e
The following:
req.field({ array: [1, 2, 3]  });

would translate to something like:
req.field('array', 1);
req.field('array', 2);
req.field('array', 3);

The underlying form-data's append() does not support this and errors out as it feels this sort of call is ambiguous (multiple interpretations). Would this be inline with superagent or is it indeed too ambiguous?
Also I could not find browser-side tests for .field(), is this intended?

Thank you for the pull request.
Consistency with set is a good idea.
We're having problems with localtunnel.me, so I'm going to give Travis a few kicks and merge it when tests pass.


add_vagrant_box.sh: remove downloaded files after installing a VM image

Installing new VM images consists in downloading a metadata.json file, a package.box file containing the image, and then in unpacking the latter. After that, both metadata.json and package.box can be removed.
To speed up downloads of package.box files (several GB), add_vagrant_box.sh relies on aria2c. When downloading multiple VM images, we had an issue in the past where aria2c would rename the downloaded file (e.g. package.box.1 if package.box is already present), causing vagrant to install the wrong image.
To avoid that, we passed the --auto-file-renaming=false option to aria2c. However, in some cases (but not all, it seems - exact conditions have not been determined) the tool refuses to overwrite an existing file. One solution could be to add --allow-overwrite=true.
But instead, this PR follows another approach. Considering that, for downloading multiple images, we overwrite the previous package.box with the new one, we end up removing all download files except for the last box installed. In order to be consistent for all images and to fix any renaming/overwriting issue, simply delete the download files after unpacking a VM image.

On second though, re-adding --auto-file-renaming=false that I removed in the first version. Better error out if the user already had a package.box in the output directory than taking the risk of overwriting it.

On second though, re-adding --auto-file-renaming=false that I removed in the first version. Better error out if the user already had a package.box in the output directory than taking the risk of overwriting it.


⚠ TorrentLeech has degraded performance

In f2518af, TorrentLeech ($TL) experienced degraded performance:

HTTP code: 200
Response time: 5435 ms

Resolved: TorrentLeech performance has improved in 1c87131 after 8 minutes.


Verbosity

what's the verbose syntax?

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

ID: 379f00ab-ebc1-50eb-6779-3a22ec41a80d
Version Independent ID: 6f88dfb3-c9f9-3715-5121-83a1f22223b8
Content: Modules (F#)
Content Source: docs/fsharp/language-reference/modules.md
Service: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

The verbose syntax is on a different page.

Verbose Syntax isn't mentioned in this article. Given that we want to steer people away from the syntax (aside from OCAML interop), I don't think we should add a link.


reverseContourPen_test: check outputImpliedClosingLine works as expected

In https://github.com/fonttools/fonttools/pull/2922, @behdad added an outputImpliedClosingLine parameter to the ReverseContourPen, plus a test that only expected a certain number of segments.
I was looking at this again today, and got a little suspicious as I noticed the number of pen commands increases from 4 in the default outputImpliedClosingLine=False case, to 6 in the outputImpliedClosingLine=True case, whereas I would only expect it to increase by +1, i.e. to 5, in the latter case, given it no longer omits the closePath's closing line.
It turns out, with outputImpliedClosingLine=True, not only the implied closing line is emitted, but also an additional, duplicate lineTo right after moveTo is emitted, which I belive is incorrect.
Here I first push the failing test that exemplifies the issue, without changing the code. I'll follow up with the fix.

as expected, CI test fails https://github.com/fonttools/fonttools/actions/runs/4204996225/jobs/7296452293
E       AssertionError: assert [('moveTo', (...osePath', ())] == [('moveTo', (...osePath', ())]
E         At index 1 diff: ('lineTo', ((0, 0),)) != ('lineTo', ((0, 10),))
E         Left contains one more item: ('closePath', ())
E         Use -v to get more diff

If I pass -v verbose to pytest, we get the full diff. Notice the additional lineTo((0, 0)) after the moveTo((0, 0)):
E         Full diff:
E           [
E            ('moveTo',
E         +   ((0,
E         +     0),)),
E         +  ('lineTo',
E             ((0,
E               0),)),
E            ('lineTo',
E             ((0,
E               10),)),
E            ('lineTo',
E             ((10,
E               0),)),
E            ('lineTo',
E             ((0,
E               0),)),
E            ('closePath',
E             ()),
E           ]

I am not referring to the final lineTo((0, 0)) before closePath, that is correct and as expected because outputImpliedClosingLine=True.

https://github.com/fonttools/fonttools/pull/2995/commits/847ce2866e2f0f5366c8404f3514403de246127e fixes it, this is now ready for review


How to run scala script

I see you have provided py (Python) file example. I want to run my scala script. Can you guide?
Also - the above folder structure can not be created without any files on blob.

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

ID: 6d8c8b1a-3b61-1dde-c11c-69043a56dfef
Version Independent ID: 9ad9804b-27c1-f1ea-2dd3-c20a4d9857fc
Content: Transform data using Spark activity in Azure Data Factory
Content Source: articles/data-factory/transform-data-using-spark.md
Service: data-factory
GitHub Login: @douglaslMS
Microsoft Alias: douglasl

@HemantChandurkar Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#in-progress

@HemantChandurkar I apologize for the delay. I am following up on this again. Keep in mind the ADF forum where instead or reaching one person, you'll reach a large body of ADF team members and subject matter experts.

@HemantChandurkar Where is the Python script that you're referring to, please? Is it within the context of a Spark activity that you want to run a Scala script?

@HemantChandurkar Please help me respond to your questions by providing the clarifications that I requested a few days ago. Thank you!

I m out vacation. Will respond tmrw. Tnx
On Tue, May 29, 2018, 10:29 PM Douglas Laudenschlager <
<EMAIL_ADDRESS>wrote:

@HemantChandurkar https://github.com/HemantChandurkar Please help me
respond to your questions by providing the clarifications that I requested
a few days ago. Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/8039#issuecomment-392854049,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHjjs7HCXsGv_vUZFPQ-aecdxcZOjDQDks5t3X5pgaJpZM4Tw6NA
.

In the document under section "Spark Activity Properties". There is py file path mentioned:
"entryFilePath": "test.py",
I assume this is Python file (and I tested it, worked!). I wanted to run Scala script instead of Python (or Pyspark?) within Spark context.

@HemantChandurkar Thanks for the clarification. I'm not personally experienced with Spark. I'm waiting for an answer to your question.

@HemantChandurkar The entryFile must be either a Python or a jar file, you would need to compile your Scala source code to jar file before running it as spark applications.

@HemantChandurkar @nabhishek I will update the page of documentation to make this requirement clear. Thanks for bringing this to our attention.

@HemantChandurkar We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Tighten Speech Asynchronous encoding support.

This adds an exception if any encoding other than LINEAR16 is used for asyn recognition.

Uncompressed 16-bit signed little-endian samples. This is the only encoding that may be used by AsyncRecognize.

See: https://cloud.google.com/speech/reference/rpc/google.cloud.speech.v1beta1#audioencoding

@daspecster I prefer the review commits don't go in history. It's not a big deal, but if it doesn't bother you too much, in the future can you either use the "squash merge" feature on GitHub or rebase your local branch before merging?

@dhermes I realized that, right after I hit merge. Apologies.


Support request : How can I use it on multiuser sites?

For example, I am using Drupal 5 where there are many users each of whom has a profile page, a blog etc - when they post a b;log post and also posts its link to facebook, and then someone comments in facebook how can they get the comment in their individual blog post ?
https://indieauth.com/setup enables to set up things on the entire drupal site but not on individual user or individual user blog ? Isn't it so?
Many users are using similar set-up for Drupal 5 and 6 - so some guide for them would be appreciated or still better a drupal 5 and 6 compatible plugin. Drupal 7 has some rdf or microformat support but 7 is not yet that widely used and upgradation to 7 not possible for all sites.

hmm. have you tried bridgy on a multi-user site? if the site accepts webmentions, and attaches them to the target post appropriately, it should Just Work. (indieauth is unrelated to bridgy, so it doesn't matter that indieauth may or may not support multi-user sites.)

tentatively closing. feel free to reopen if you run into a problem!


Bot.deliver error handling

As the API is growing at Facebook, it appears some new error codes are being returned.
We've been working with the API for the last weeks, and I'm almost sure that when someone deleted a conversation with a bot, Facebook would return 100 error in response to the Bot.deliver action, a Facebook::Messenger::Bot::RecipientNotFound.
Now, apparently it is returning a new error code, 200, per the API:
"This person isn't receiving messages from you right now."
I'm relying on these errors to keep track of the real bot users (I destroy those who don't receive messages), so it would be cool either to upgrade the gem with the recently added error responses (https://developers.facebook.com/docs/messenger-platform/send-api-reference#response) or wrap the errors in the exceptions in a way that the code was still available for us to check, e.g., see: https://github.com/ryanb/cancan/blob/master/lib/cancan/exceptions.rb#L35.
Any thoughts on this?
Thanks in advance.

I think that'd be awesome, @pjpires! I'd be very happy to merge a pull request with new and improved error handling (and I like the approach where each error has its own exception that you can rescue from).

@jgorset took me a while to have time for it, but what do you think about this?
https://github.com/hyperoslo/facebook-messenger/pull/99

Love it, @pjpires – merged. :wink:


Enable auto imports and add missing import for module/package names

Suggestion

🔍 Search Terms

auto import
quick fix
missing import

⭐ Suggestion
Auto imports / add missing imports should be able to add import * as XYZ from 'XYZ' when triggered on the symbol name XYZ in a file. This is useful if you prefer using namespace imports and can also help with discovering/exploring new packages
Right now we have auto imports and an add missing import quick fix for symbols in a module, but I don't see these options for the module itself
📃 Motivating Example

In a new project
npm I @types/vscode
Open new TS file and write vscode.

Right now I don't get an auto import for vscode. I'd expect an import that adds: import * as vscode from 'vscode';  at the top of the file
💻 Use Cases

Make it easier to reference a symbol if you prefer using namespaces from the start
Helping users explore new packages (just type vscode. to see suggestions in the vscode package)
Working with node packages. It'd be nice to be able to type fs. to get an fs import
Fixing code that has been copy and pasted between files

This was discussed at https://github.com/microsoft/TypeScript/issues/23830, right?

@DanielRosenwasser Looks like it. Andrew's answer makes sense but it does feel like we could do better here. Maybe only apply this for node packages to start?