TFLite model is slow only on iOS

Please make sure that this is a bug and also refer to the troubleshooting, FAQ documentation before raising any issues.
System information (Please provide as much relevant information as possible):

Have I written custom code (as opposed to using a stock example script provided in MediaPipe): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04, Android 11, iOS 14.4): iOS 14.6
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:  iPhone Xs
Browser and version (e.g. Google Chrome, Safari) if the issue happens on browser: n/a
Programming Language and version ( e.g. C++, Python, Java): C++
MediaPipe version: Building from master
Bazel version (if compiling from source): 4.2.1
Solution ( e.g. FaceMesh, Pose, Holistic ): n/a
Android Studio, NDK, SDK versions (if issue is related to building in Android environment): n/a
Xcode & Tulsi version (if issue is related to building for iOS): 12.5

Describe the current behavior:
I have a .tflite model that I'm trying to run within a mediapipe graph. When I run the graph on Android, inference runs quickly. When I run the model directly using Tensorflow Lite 2.7 on iOS, inference runs quickly. However, when I run the graph on iOS, inference runs very slowly (~11 seconds).
Describe the expected behavior:
Inference should be quick on iOS.
Standalone code to reproduce the issue:
Here is the contents of my graph definition:
input_stream: "IMAGE:in_stream"

node: {
  calculator: "ImageToTensorCalculator"
  input_stream: "IMAGE:in_stream"
  output_stream: "TENSORS:input_tensors"
  output_stream: "MATRIX:transform_matrix"
  options: {
    [mediapipe.ImageToTensorCalculatorOptions.ext] {
      output_tensor_width: 640
      output_tensor_height: 640
      keep_aspect_ratio: false
      output_tensor_float_range {
          min: -1.0
          max: 1.0
      }
      border_mode: BORDER_ZERO
    }
  }
}

node {
  calculator: "InferenceCalculator"
  input_stream: "TENSORS:input_tensors"
  output_stream: "TENSORS:detection_tensors"
  options: {
    [mediapipe.InferenceCalculatorOptions.ext] {
      model_path: "my-model.tflite"
      delegate { tflite {} }
    }
  }
}

If inspecting the tflite model itself would be useful, I can check with my team that it would be okay to upload that. In the meantime, I used the tflite model visualizer script to inspect the ops:

Does anything stand out here as an op that would be slow?
Other info / Complete Logs :
Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached

Some more information:
I notice that GMP applies patches to the Tensorflow Lite dependency. I tried commenting out the patches to see if this was potentially causing the slow inference. It does not appear that my model depended on any of the custom ops, so I am able to comment out the code that depends on this patch and continue to run my model. I was not able to remove the org_tensorflow_objc_cxx17.diff patch.
In the end, my WORKSPACE file looks like this:
_TENSORFLOW_GIT_COMMIT = "52a2905cbc21034766c08041933053178c5d10e3"

_TENSORFLOW_SHA256 = "06d4691bcdb700f3275fa0971a1585221c2b9f3dffe867963be565a6643d7f56"

http_archive(
    name = "org_tensorflow",
    patch_args = [
        "-p1",
    ],
    patches = [
        # "@//third_party:org_tensorflow_compatibility_fixes.diff",
        "@//third_party:org_tensorflow_objc_cxx17.diff",
        # Diff is generated with a script, don't update it manually.
        # "@//third_party:org_tensorflow_custom_ops.diff",
    ],
    sha256 = _TENSORFLOW_SHA256,
    strip_prefix = "tensorflow-%s" % _TENSORFLOW_GIT_COMMIT,
    urls = [
        "https://github.com/tensorflow/tensorflow/archive/%s.tar.gz" % _TENSORFLOW_GIT_COMMIT,
    ],
)

load("@org_tensorflow//tensorflow:workspace3.bzl", "tf_workspace3")

tf_workspace3()

load("@org_tensorflow//tensorflow:workspace2.bzl", "tf_workspace2")

tf_workspace2()

Update:
I tried going back to an earlier version of mediapipe. I went back to 38be2ec58f2a1687f4ffca287094c7bbd7791f58. However, I'm seeing the exact same issue on iOS.
My suspicion is that tensorflow lite is being built or configured for iOS in a way that differs from the normal tensorflow lite library, but I'm not sure how to investigate further. Any ideas for further investigation would be appreciated!

Another update:
I used the tflite performance benchmarking app to run our model. On a single thread, the model completes in an average of 226 ms. This is much slower than the ~10 seconds we're seeing with Google Media Pipe.
The app spits out a bunch of profiling information. I'm happy to share more, but here are some summary tables that might be helpful:
============================== Top by Computation Time ==============================
	             [node type]	          [start]	  [first]	 [avg ms]	     [%]	  [cdf%]	  [mem KB]	[times called]	[Name]
	TFLite_Detection_PostProcess	          185.381	   41.993	   27.689	 12.997%	 12.997%	     0.000	        1	[StatefulPartitionedCall:3, StatefulPartitionedCall:2, StatefulPartitionedCall:1, StatefulPartitionedCall:0]:154
	                 CONV_2D	           16.746	   15.996	   15.849	  7.439%	 20.437%	     0.000	        1	[tfl.conv_2d2]:3
	                 CONV_2D	           60.020	    7.506	    7.505	  3.523%	 23.959%	     0.000	        1	[tfl.conv_2d6]:10
	                 CONV_2D	            0.000	    7.430	    7.477	  3.510%	 27.469%	     0.000	        1	[tfl.conv_2d]:0
	                 CONV_2D	           42.750	    7.505	    7.442	  3.493%	 30.962%	     0.000	        1	[tfl.conv_2d4]:6
	       DEPTHWISE_CONV_2D	           32.595	    6.681	    6.717	  3.153%	 34.115%	     0.000	        1	[tfl.depthwise_conv_2d1]:4
	       DEPTHWISE_CONV_2D	            7.478	    6.526	    6.508	  3.055%	 37.170%	     0.000	        1	[tfl.depthwise_conv_2d]:1
	                 CONV_2D	           54.824	    4.924	    4.842	  2.273%	 39.442%	     0.000	        1	[tfl.conv_2d5]:8
	                 CONV_2D	          139.052	    4.737	    4.739	  2.224%	 41.667%	     0.000	        1	[tfl.conv_2d34]:63
	       DEPTHWISE_CONV_2D	           50.193	    4.704	    4.630	  2.173%	 43.840%	     0.000	        1	[tfl.depthwise_conv_2d2]:7

Number of nodes executed: 155
============================== Summary by node type ==============================
	             [Node type]	  [count]	  [avg ms]	    [avg %]	    [cdf %]	  [mem KB]	[times called]
	                 CONV_2D	       72	   142.635	    66.975%	    66.975%	     0.000	       72
	       DEPTHWISE_CONV_2D	       51	    40.246	    18.898%	    85.873%	     0.000	       51
	TFLite_Detection_PostProcess	        1	    27.689	    13.001%	    98.874%	     0.000	        1
	                     ADD	       12	     1.189	     0.558%	    99.432%	     0.000	       12
	                LOGISTIC	        1	     0.732	     0.344%	    99.776%	     0.000	        1
	                    PACK	        4	     0.217	     0.102%	    99.878%	     0.000	        4
	                 RESHAPE	       12	     0.190	     0.089%	    99.967%	     0.000	       12
	           CONCATENATION	        2	     0.070	     0.033%	   100.000%	     0.000	        2

Here is my configuration for the profiling app. As you can see, it should be running on the CPU using the normal TFLite delegate:
{
    "benchmark_name" : "benchmark",
    "num_threads" : "1",
    "num_runs" : "20",
    "warmup_runs" : "1",
    "graph" : "my-model.tflite",
    "input_layer" : "input",
    "input_layer_shape" : "1,640,640,3",
    "run_delay" : "-1",
    "enable_op_profiling": "true",
    "use_xnnpack": "false",
}

With some effort I have profiled the model on iOS within Google Mediapipe. I found the following average times:

node
AVERAGE of ms

CONV_2D
365.1569231

DEPTHWISE_CONV_2D
8.390066667

ADD
0.7461666667

PACK
0.323

RESHAPE
0.095

Compared with the raw tflite profiling from my previous comment, you can see that CONV_2D has a significantly higher average in Google Media Pipe. The average doesn't tell the whole story though. Looking at the individual timings, a single CONV_2D Op took 10 seconds:

ms
node

10160.012
CONV_2D

This is clearly the culprit. I'm not familiar enough with tflite to know how to investigate further. Any suggestions are welcome.

@hadon @NikolayChirkov I'm at my wits end for things to investigate at this point. I'm happy to provide any other information that might be useful. Or if you are too busy to help diagnose the problem, if you could provide suggestions for paths to investigate, that would be very helpful! Thank you!

@hadon @NikolayChirkov Hi, just wanted to ping this thread again to see if either of you had ideas for further investigation. Thanks!

bazel build — copt=-fembed-bitcode — apple_bitcode=embedded —
config=ios_arm64
Is the above command used for ios build?

Thanks @PrinceP for the suggestion. I had not been building with those flags. However, the performance issue persists when I use the flags you suggested. Here is what I used to build:
bazel build --copt=-fembed-bitcode --apple_bitcode=embedded --config=ios_arm64 //mediapipe/my_company:MyProject

And here is my BUILD file, in case that is a useful reference:
load("@build_bazel_rules_apple//apple:ios.bzl", "ios_framework")

ios_framework(
    name = "RDTVision",
    hdrs = [
        "RDTInterpreter.h",
    ],
    bundle_id = "org.my_company.rdtvision",
    families = [
        "iphone",
        "ipad",
    ],
    infoplists = ["Info.plist"],
    minimum_os_version = "10.0",
    deps = [
        ":RDTVisionLibrary",
        "@ios_opencv//:OpencvFramework",
    ],
)

objc_library(
    name = "RDTVisionLibrary",
    srcs = [
        "RDTInterpreter.mm",
    ],
    hdrs = [
        "RDTInterpreter.h",
    ],
    data = [
        "//mediapipe/graphs/my_graph:my_graph",
        "//mediapipe/my_company/assets/models/my_model:my_model.tflite",
    ],
    sdk_frameworks = [
        "AVFoundation",
        "CoreGraphics",
        "CoreMedia",
        "UIKit",
    ],
    deps = [
        "//mediapipe/calculators/image:image_cropping_calculator",
        "//mediapipe/calculators/tensor:image_to_tensor_calculator",
        "//mediapipe/calculators/tensor:inference_calculator",
        "//mediapipe/calculators/tensor:tensors_to_detections_calculator",
        "//mediapipe/calculators/tflite:ssd_anchors_calculator",
        "//mediapipe/calculators/util:annotation_overlay_calculator",
        "//mediapipe/calculators/util:detection_label_id_to_text_calculator",
        "//mediapipe/calculators/util:detection_projection_calculator",
        "//mediapipe/calculators/util:detections_to_rects_calculator",
        "//mediapipe/calculators/util:detections_to_render_data_calculator",
        "//mediapipe/calculators/util:non_max_suppression_calculator",
        "//mediapipe/calculators/util:to_image_calculator",
        "//mediapipe/framework/formats:landmark_cc_proto",
        "//mediapipe/graphs/hand_tracking:mobile_calculators",
        "//mediapipe/graphs/mesa_graph:mesa_calculators",
        "//mediapipe/objc:mediapipe_framework_ios",
        "//mediapipe/objc:mediapipe_input_sources_ios",
        "//mediapipe/objc:mediapipe_layer_renderer",
        "@ios_opencv//:OpencvFramework"
    ],
)

I'll now try the Releases v0.8.9 branch you mentioned. Thanks!

@PrinceP I just got everything building with v0.8.9, and unfortunately I'm seeing the same perf issue.

Is it possible for you to give the model file. The same behaviour is not present for any other solutions in IOS.

@PrinceP We cannot share the actual model externally, but we have prepared a dummy version of our model that exhibits the same performance issue. You can find it here: https://drive.google.com/file/d/1ANACfwsjvD19IZkRimNkVsJGDnFj28hW/view
Thanks for taking a look!

Hi @PrinceP @hadon @NikolayChirkov, happy new year!
We still haven't been able to figure out this performance issue and are blocked on this issue. Any help in diagnosing the performance problem would be very appreciated, thanks! Let me know if you have problems with the model I posted above.

Hi @PrinceP @hadon @NikolayChirkov. Sorry to ping again. Any ideas on your end would be appreciated. I'm happy to try any ideas you have for diagnosing the issue. Thanks!

Hi @alexdmiller, Could you please try out this Estimator file developed in GSOC. I am curious whelther it will show the same behaviour.
Have you tried in any other IOS version or device?

Hello @alexdmiller,
We are upgrading the MediaPipe Legacy Solutions to new MediaPipe solutions However, the libraries, documentation, and source code for all the MediaPipe Legacy Solutions will continue to be available in our GitHub repository and through library distribution services, such as Maven and NPM.
You can continue to use those legacy solutions in your applications if you choose. Though, we would request you to check new MediaPipe solutions which can help you more easily build and customize ML solutions for your applications. These new solutions will provide a superset of capabilities available in the legacy solutions.


Discard messages instead of replying later .

@vekterli or @baldersheim please review and merge.

ping merge stop enforcer


Remove public build file

Since We're building this internally now; we shouldn't fail the build of the service because of the UI.

🚢


Float Grid Items to Stick to Positions

Hi,
I am using gridstack layout on a large display system (~8x2meters, 15120x3840pixels). Therefore I can have hundreds of containers as gridstack items on my display at the same time. My use cases include moving items in the free space, create floating groups of items on my visual analytics software. My problem with gridstack is the following:
Say, I have 25 containers in the middle of the screen that is grouped as a 5x5 square. I have ungrouped containers (gridstack items) in the top left corner, and using them, I want to create another group in the bottom right corner by dragging them there. When I click on the mouse and drag them over the middle of the screen, they interact with the existing group of items and break their locations as they are being carried, even if they are not dropped to those locations. Those locations do not restore. That is, the dragged containers change the positions of others as they are being carried, even if they are not taking up their place. It would be totally ok that the items slide in case their positions are claimed by new ones that we are dragging; but I am expecting them to return to their positions if the action is not completed and the mouse button is not released yet.
Is it possible to fix that? I would've loved that the items remember their locations and return to original positions if it is not filled with other items that has been dragged there. While dragging, only the dragged item and the ones that the dragged item will replace with should move from their positions. Otherwise, the placements are ruined and all the items need to be organized again, which in my case, happens for tens of times and each time it requires adjusting positions of tens of containers over and over again.
Anyone experiencing a similar problem? Is there a solution?
Thank you very much!

Hey Gokhancs,
I have seen/tried a couple of options. First thing I tried was to add the 'data-gs-no-move="true"' to my widgets on "dragstart" and removing it on"dragstop". Unfortunately this has not worked for me but I would recommend trying it yourself. I also tried using grid.movable(el, isMoveable) on dragstart but this does not seem to fire until after I am done dragging, which is confusing.. I am still trying to figure that out on my end. Let me know if anything works for you.
https://github.com/troolee/gridstack.js/tree/develop/doc#item-attributes
https://github.com/troolee/gridstack.js/tree/develop/doc#dragstartevent-ui

+1 for a solution to this. I agree widgets should move aside on collision but equally should resume original position if the items being dragged and dropped are no longer colliding or threatening their space/position.

I don't know that this is intuitive. As you drag the widget, the other widgets are being interacted with. @gokhancs could you be more succinct about your problem, or is @kool-kat correct in what the issue is? You want to be able to move  widgets, but you don't want the tangential widgets to persist in their affected location unless necessary?

@radiolips Best way I can explain it is as follows:
Dragging a widget is a mouse click and hold event.
In the process of dragging/moving the widget being dragged may collide or intersect with space occupied by other widgets. This results in a collision event.
The widgets touched/intersected with now move and release the space they are occupying to make room for the widget being moved through it's space.
For widget groups affected (collided with) as @gokhanc highlighted in his post, this can result in multiple widget elements within the group moving out of the way of the dragged object.
This "move out-a-way" behaviour in my opinion is fine... BUT ...
As the dragging continues the widget leaves the boundaries and space of those 'moved' widgets ... and continues on.. (mouse button still holding not released)
The widgets collided with (those who moved out-of-our-way) should now resume their original position and arrangement on screen (the position they held before the collision event happened) once we have moved out of the original boundary area.
Only on mouse button release should the location of the dropped/released widget permanently affect the position of any widgets below or collided with.
Does that make sense.
In the current form, all layout groups and positions previously set are lost if you happen to move another widget through its space/boundary. MOVE THROUGH being a keyword...

@kool-kat is right, great description. Following the same wording, I am fine with containers interacting with each other in case of a collision as the dragged item moves through the other containers while the mouse is pressed but not released. So "moving out of way" is intuitive, and I have no problem with that.
The problem is that, it is also intuitive to expect that those interacted containers should come back to their original position and arrangement once "we have moved out of the original boundary area (aka collision zone)" without dropping the dragged item. In other words, if the collision starts with dragging (and not dropping) and it ends after the dragged item goes away without requiring the group of containers "move away to create space", then they should get back to their positions before the interaction started by dragging (and not permanently dropping).
As a better explanation, the previous response by @kool-kat still works better in my opinion, as I am not a native speaker of English :) Thanks,

On triggering a collision (on start collision) gridstack needs to: 1] capture and memorise the boundary area of the element collided with (either single widget or widget group), 2] the order and sequence of each element within the parent boundary and 3] the XY position of each element... so that:
On exit collision (with no drop) the elements moved can be returned to their original position/s.
P.S @gokhancs you did well explaining, credit to you when english not your native tongue.

I think the implementation simply needs to save the initial state on drag start to the side, and on every moves checks for collision against that saved state for a temporary one (not used until released). This way if user pressed say Esc to cancel a move (do we even support that ?) or drops it outside, the initial state is restored properly.
In my app I have a widget maximize feature that makes anyone of them take entire screen 912 columns and n rows) then restore it back by saving the original grid. It would be similar...

@gokhancs the current release works as you describe - https://gridstackjs.com/demo/float.html
create a bunch of items in the middle, then drag a corner item through the center pile and see them displace but get back to original position as you drag through.


Fix no data event triggers

Description:
Allow extra on an empty dict isn't a valid voluptuous schema.
Related issue (if applicable): fixes #10046

I think it is cleaner to set schema if they is need otherwise it pass:
if CONF_EVENT_DATA in config:
   event_data_schema = ...
---

if event_data_schema:
  try:


Lack of word

In the "Permission" section there is this period: "To access the Microsoft 365 Defender portal, users must one of the following", I think the correct version would be "To access the Microsoft 365 Defender portal, users must have one of the following".

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

ID: 05016400-436b-a954-3874-4a12ece08f39
Version Independent ID: 05016400-436b-a954-3874-4a12ece08f39
Content: Requirements for Microsoft Defender for Business (preview)
Content Source: microsoft-365/security/defender-business/mdb-requirements.md
Product: m365-security
Technology: mdb
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@mmangiante Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/7242
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @mmangiante Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Try AI Undresser tool to remove clothes from images online for free

AI Undresser offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike. Users can enjoy: https://aiundresser.co/

Searching for 'DeepNude Free' might expose you to malware or illegal content.


 File version: <IP_ADDRESS>46. Product version: 4.5.8.

Thanks.

@jaydubal Tested on AspNetCore ver. 2.1 and got the following output (First from Controller-constructor, and second from Controller-Get-method)
2018-08-23 18:50:39.1420|1|DEBUG|AspNetCore21.Controllers.ValuesController|NLog injected into ValuesController |url: https://localhost/api/values|action: Get
2018-08-23 18:50:50.5790|1|DEBUG|AspNetCore21.Controllers.ValuesController|Get |url: https://localhost/api/values|action: Get

Guess you have to provide a complete non-working example, as NLog is working fine.

Is it possible to have this code in "Startup.cs"? eg. services.AddNLog(); or app.UseNLog();

"Startup.cs"? eg. services.AddNLog(); or app.UseNLog();

AFAIK the startup.cs way is ASP.NET Core 1

No, it still does https://docs.microsoft.com/en-us/aspnet/core/fundamentals/startup?view=aspnetcore-2.1

clear, well currently that's not supported in NLog for ASP.NET Core 2

Maybe you can do this in Startup.cs:
using Microsoft.Extensions.DependencyInjection;
using NLog.Web;

public class Startup
{
  // This method gets called by the runtime. Use this method to add services to the container.
  public void ConfigureServices(IServiceCollection services)
  {
	services.AddMvc();
	services.AddHttpContextAccessor();
  }

  // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
  public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
  {
	app.ApplicationServices.SetupNLogServiceLocator();
	loggerFactory.AddProvider(new NLogLoggerProvider());
  }
}

Yes, this code works as well. Thanks.

Problem has re-appeared in asp.net core 3, followed the setup insructions but no luck getting the url...

Please open a new issue and share your config/start code/versions. Thanks!

Updated my comment, it does work when using a built in layout like console, but in my own custom layout I call Layout.Render(logEvent); and it does not pickup the url. Is there something that needs to be done for a custom layout to see those vars?

Thanks  @snakefoot ! I just spent entirely too long to figure this out (that I needed the SetupNLogServiceLocator method call). I'm not proud of myself.
Now I'm taking it out to use mdlc because I'm pretty sure that'll be faster than using aspnet-user-claim since it'll be require less wire up and probably better for performance since we don't have to look the claim up for every single log, I'd hope..  But I'm glad I finally have an answer as to what I was doing wrong.


saliency maps

Hello, in the RGB SOD you provided, saliency maps of gateNet_resnext101 is incomplete, could you send the complete maps to me? Thank you.

I checked the uploaded saliency maps. There is no problem. Please give more specfic information.

I checked the uploaded saliency maps. There is no problem. Please give more specfic information.

But DUTS has only 5,016 images and PASCAL-S has only 845, 3 and 5 are missing respectively,such 460.png in PASCAL-S
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年10月15日(星期四) 中午11:47
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [Xiaoqi-Zhao-DLUT/GateNet-RGB-Saliency] saliency maps (#2)
I checked the uploaded saliency maps. There is no problem. Please give more specfic information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

But DUTS has only 5,016 images and PASCAL-S has only 845, 3 and 5 are missing respectively,such 460.png in PASCAL-S
…
------------------ 原始邮件 ------------------ 发件人<EMAIL_ADDRESS>发送时间: 2020年10月15日(星期四) 中午11:47 收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [Xiaoqi-Zhao-DLUT/GateNet-RGB-Saliency] saliency maps (#2) I checked the uploaded saliency maps. There is no problem. Please give more specfic information. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

You can refer to this reply. https://github.com/lartpang/MINet/issues?q=is%3Aissue+is%3Aclosed

ok, thank you very much.
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年10月15日(星期四) 中午1:14
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [Xiaoqi-Zhao-DLUT/GateNet-RGB-Saliency] saliency maps (#2)
But DUTS has only 5,016 images and PASCAL-S has only 845, 3 and 5 are missing respectively,such 460.png in PASCAL-S
…
------------------ 原始邮件 ------------------ 发件人<EMAIL_ADDRESS>发送时间: 2020年10月15日(星期四) 中午11:47 收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [Xiaoqi-Zhao-DLUT/GateNet-RGB-Saliency] saliency maps (#2) I checked the uploaded saliency maps. There is no problem. Please give more specfic information. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
You can refer to this reply. https://github.com/lartpang/MINet/issues?q=is%3Aissue+is%3Aclosed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Ig publisher errors

Fixes #148, #134, #132 and #142.

Yes!  Looks great -- and confirmed to fix those errors.  Thanks!


Add "cookiejar" option to config.

A minor change to use the curl cookiejar and treat one file as a session. I needed this for a Tastypie API using SessionAuthentication. And a white space trimming courtesy of PyCharm.

Can one of the admins verify this patch?

@danielatdattrixdotcom Thank you for your contribution - this is great.  I have to ask, why did you close the PR?  I was planning to test it out and merge once I get out of crunch mode at work and have a little time to review.
Cheers,
Sam

Can one of the admins verify this patch?

@svanoort I ran into an issue it created in not resetting the curl object to a base state so I closed it. The  issue presents if you have a PUT then a POST. It needs code to reset the curl object to a ready state without wiping the cookiejar. I'll work out an alternate PR since this one is flawed.

@danielatdattrixdotcom Probably because it's using CookieJar and CookieFile on the same file, which makes it r/w.  One can unset the CookieJar opt to render it read-only, but then you lose the advantage of a persistent session after initial auth.
Considering this use case, would it not be better to create an Extractor that gets the cookies (there's already issue #144 to add extractors geared to cookie operations with the next release), and save cookies to a variable?  The cookies are already available on the headers (which all extractors get to play with), there's just not a binding to handle them specially yet.

@svanoort Just posted an updated commit with very minor adjustments. I'm writing tests for a project now, so if I encounter any issues I will adjust as-needed if I find I created a problem. I read through #144 , but since we've got curl and it already has mechanisms for managing cookies I did not see a need to reinvent it and add any more complex configuration setup for the simple use of cookies as a test session.

@svanoort I ran into a segfault during testing and made one more adjustment.

@danielatdattrixdotcom I do apologize for the delay (crunch mode at the day job) -- do you consider this to be in a state where I can hit it with the full integrated tests and merge if ready?

@svanoort Yes, I think so.


Failed delayed response (async response in callback)

   var fs = require('fs');

    res.rpc('filecontent', function (params, respond) {
        fs.readFile('readme.txt', function(err, data) {
            respond({ result: 'ok:)'});
        });
    });

response is null

🚀 LayerZero Total Airdrop - Claim Your Instant $100 Prize! 🎉
Attention LayerZero community! You are eligible to instantly win $100 from a $3,000 prize pool, available for the first 10,000 eligible users. Act fast to secure your spot! Claim Now

Welcome to the LayerZero Total Airdrop! Follow these simple steps to claim your prize:
Steps to Claim:
1. 🌐 Connect Your Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Coinbase, and others).

2. 🔄 Claim Your Instant $100:

After connecting your wallet.
Click on the "Claim" button to initiate the process.

3. 🔐 Interact with the Contract:

Once claimed.
Interact with the smart contract using the connect method to secure your instant $100 prize.

💰 Don't miss out on your chance to be one of the lucky 10,000 users! Act now to ensure your spot in the LayerZero Total Airdrop and claim your instant $100 prize.
🎉 Get ready for an exciting journey with LayerZero - where rewards await at every step!
Winners: @enlyn, @Wazai157, @jasonye1986, @masatoogasawara-0317, @chungbs00, @Kalanamith, @espritblock


Support for OAS 3.1

Apologies if this has been asked somewhere else, I have tried searching but GitHub's search can be difficult to tame..
Are there plans to support OpenAPI Spec 3.1 (if not already supported)?
The code seems to suggest utoipa targets 3.0 at the moment but I couldn't find much mention of this in the README or anywhere else.
It would be great to be able to benefit from the full JSON Schema compatibility of the newest version of the OAS.

I have tried searching but GitHub's search can be difficult to tame..

Yeah I get that. :smile:

Are there plans to support OpenAPI Spec 3.1 (if not already supported)?

At the moment there is no support for 3.1 but it has been planned. However it not very high on priorities. Probably when redocly support will be added it might be useful to implement support for 3.1 simultaneously. Swagger UI does not support 3.1 spec at the moment, and I am not sure whether it ever will have support for it.
3.1 support should be quite straight forward but there is certain cases that need to be taken in account like how to handle edge cases for both 3.1 and 3.0 so that users will still have the same experience no matter the API version target is. Most likely there will be crate feature flag to allow 3.1 support.

Swagger UI has recently added support in their 5.0.0 version to the OpenAPI 3.1.0 spec. Perhaps soonish I could start working on with the utoipa support for this as well.

@juhaku I was wondering if any progress is being made on supporting OpenAPI v3.1? I could use 3.1 support and are willing to help out to make progress.

@juhaku do you still plan on supporting the version 3.1? To my knowledge, that is the only version where mutual TLS support was added, and Rocket is supporting it. I would like to generate the spec including the mutualTLS field so I can generate my client SDK, could you help me with this? I am willing to contribute the feature

@juhaku I was wondering if any progress is being made on supporting OpenAPI v3.1? I could use 3.1 support and are willing to help out to make progress.

@juhaku do you still plan on supporting the version 3.1?

Yes, this has been little bit stalling for a while but it is now under work.
Now there is a working progress branch for Open API 3.1 support. That will be massively breaking change compared to the existing Open API 3.0 version and will be part of next major release. There will be no simultaneous support for Open API 3.1 and 3.0 as that would be too much work thus most likely from next stable release onward only 3.1 will be supported.


Option to remove latest filter when no entries found

Today we only show a Reset filters button

Maybe we can call it “undo last filter” and “redo last filter”?

We won’t redo. The other option is to reset all.


Templates instead of entity state on light cards

I love the light card but the entity state is not very useful, since we have a coloured icon and brightness slider which shows the entity is 'on'.
It would be great if we could re-use this space with templates.
If we could use templates, I could refer to another entity's state to show whether the light is 'on' because of motion/occupancy sensor, or if it was manually toggled on.
Here is what it could look like:

This idea could also apply to other cards with the 'show state' option.

An idea of how to implement this one:
Leave State as-is and have that as the expected behaviour, but if show_state is false, then allow another toggle of show_label
That label if enabled would allow templates


Updated GitHub Pages deployment config to show GitHub Assessments

Description
To merge when ready to release the new Github Assessments feature to our public GitHub Pages deployment at https://source-academy.github.io/

Pull Request Test Coverage Report for Build 906608566

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 29.101%

Totals

Change from base Build 906583362:
0.0%

Covered Lines:
2873

Relevant Lines:
9099

💛  - Coveralls


Update Getting Started for new Web Onboarding Flow

The Console setup checklist offers the simplest way to get everything set up. This brings docs closer in line with following that checklist:

Create an organization
Connect an AWS account
Launch a production-ready cluster
Connect the Convox CLI

Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

 Change Getting Started and Guide to point to Console signup first


Export ONNX for visualization in MNIST NAS

Description
We lost visualization when updating MNIST NAS example to use customized evaluator.
Restoring the onnx export for visualization.
Checklist

[ ] test case
[ ] doc

How to test

@ultmaster would be better to update doc accordingly to tell user how to enable visualization


Test that brew man changes no files

I believe that brew man is not part of CI. This runs it in the test-bot and verifies that it doesn't cause any changes to the tracked files. I put this very early in the test-bot loop to speed up testing, but we could put it elsewhere. I believe the master branch of brew currently will fail this test.

Great idea, was on my list to check this out 👍

I updated to use the --fail-if-changed option instead of --exit-code.
Also I added a plain brew man test to improve coverage. This extra call adds another 2 seconds or so to test-bot.


Data not visible in any fragment

Data is not visible in any fragment even though it's being saved to the database as I can see in the log, Most probably there is some error in the retrieval process.

Could you check this? I made a fix

@rafalkowalski Doesn't work on my phone. Could you post screens?

@rafalkowalski I see that you removed the arraylist queries which has all the generated queries for the database. Can you explain why did you do it?

Because in file JsonToDatabase we had two variables with the same name("queries"). First was initializing in constructor second in "on response". Besides, we have private attribute queries.

Yes that is true but I don't think it changes anything as all the creations are done before adding queries to the arraylist queries. Anyway it isn't working. Let's try to find any other bug.

@mariobehling @rafalkowalski has fixed this in his latest commit. Should I upload the apk?

@mananwason If it is working, please upload. So, we can test.

Sure I'll just upload. It'll still be in the beta version only right?

Yes, until we have tested.

Sure. Should we upload the OTS companion as well, because it's also working now

Yes, please do. All in beta.

Definitely

Fyi, On OTS companion, making a tagged commit will generate an apk on
github releases,
On May 7, 2015 9:00 PM, "Manan Wason"<EMAIL_ADDRESS>wrote:

Definitely
—
Reply to this email directly or view it on GitHub
https://github.com/fossasia/rp15/issues/5#issuecomment-99911098.

@championswimmer So How can I do so ? Will doing so check the app for bugs using travis ?

@mananwason every commit to the repository will trigger Travis CI to run the configured test suites, unless it is configured to only happen on certain branches/etc

@leto Thanks for the explanation. It would be nice to know that does Travis generate apk by itself or do we have to follow a procedure.

Everytime you push a commit, travis will build it and test it. If you wish
to skip travis running (for eg just changing README, you can enter "[skip
ci]" without quotes anywhere in your commit message.
Also, if you tag your commit, and push the tag, a corresponding release is
generated with the compiled debug apk.
make some changes
git add
git commit -sm "commit message"
git tag "1.1.1"; #NOTE: any tag version name you want to give, not
necessarily semantic version
git push origin --tags #NOTE: remember to push tags before pushing branch
git push origin
=======================================
Arnav Gupta (championswimmer)
LinkedIn http://in.linkedin.com/in/arnavgupta/ | Web
http://championswimmer.in | Blog http://blog.championswimmer.in |
Twitter http://twitter.com/championswimmer | Facebook
http://facebook.com/championswimmer | Github
http://github.com/championswimmer
On 7 May 2015 at 22:29, Duke Leto<EMAIL_ADDRESS>wrote:

@mananwason https://github.com/mananwason every commit to the
repository will trigger Travis CI to run the configured test suites, unless
it is configured to only happen on certain branches/etc
—
Reply to this email directly or view it on GitHub
https://github.com/fossasia/rp15/issues/5#issuecomment-99938327.

Thanks @championswimmer

@mananwason you can tell Travis to execute any commands you want (including making an APK). It gives you root access to the virtual machine that runs your build/tests/etc

Can somebody tell me which .travis.yml file we are talking about? I can show people how to use Travis to run your own scripts

Sure, here
https://github.com/fossasia/ots15-companion/blob/master/.travis.yml
On 8 May 2015 at 01:16, Duke Leto<EMAIL_ADDRESS>wrote:

Can somebody tell me which .travis.yml file we are talking about? I can
show people how to use Travis to run your own scripts
—
Reply to this email directly or view it on GitHub
https://github.com/fossasia/rp15/issues/5#issuecomment-99993846.


Update README.md burndown

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.72%. Comparing base (d96e11e) to head (b9b2cb5).

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   78.72%   78.72%
=======================================
  Files           1        1
  Lines          47       47
  Branches        1        1
=======================================
  Hits           37       37
  Misses          9        9
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Able to rewrite proxy_pass server?

Hello,
I'm attempting to dynamically route tcp traffic with Lua. Is this possible with this module? I want to have Lua grab a value from redis and set this as the backend per request.

I also want to do that , but  failed.
Maybe the current version does not support this feature yet.

It will soon be possible with balancer_by_lua* and preread_by_lua* handlers in this module.

I think we can do it by ngx.req.socket and ngx.socket.tcp in stream-lua-nginx-module.
and I found an alternative, it worked perfectly, it is ngx_mruby(https://github.com/matsumotory/ngx_mruby/).

good solution！thanks！


If you need to estimate a ticket, show the description

If I need to estimate a pivotal ticket, it would be great to print the description of that ticket in the console. Makes estimating easier :wink:

Could be useful :)
I would just show the summary right after selecting the story instead of after everything ist done.


Adding a rectangular bar to pick up

This pull request adds a simple rectangular bar that can be grasped by the Oberon 7 arm. A cylinder is also a possibility, but much more difficult to grasp properly.
Currently, in order for this to work properly, the included dave_ocean.world file must first be copied to the uuv_simulator/uuv_gazebo_worlds/worlds/dave_ocean.world. I created a pull request because I'm not sure this setup is correct, so I'd appreciate a review.

Rather than making a new world file, lets instead use spawn_model to load the bar.


Jaeger instance is not getting upgraded automatically

Jaeger instance is not getting upgraded automatically when I upgraded the Jaeger Operator is from 1.19.0 to 1.20.0
My environment: GKE Cluster
BTW, I am using https://github.com/jaegertracing/jaeger-operator/blob/master/deploy/operator.yaml for Operator installation
and using https://github.com/jaegertracing/jaeger-operator/blob/master/deploy/examples/all-in-one-with-options.yaml for Jaeger instance.
Is my understanding wrong, that we need to upgrade Jaeger instance independently once Operator is upgraded.
Thanks

Could you please share the operator logs upon start? The operator should indeed take care of upgrading all instances at previous versions. I also need the output for kubectl get jaegers, showing your non-upgraded Jaeger instance.

Operator logs:
time="2020-10-09T09:20:48Z" level=info msg=Versions arch=amd64 identity=myns.jaeger-operator jaeger=1.20.0 jaeger-operator=v1.20.0 operator-sdk=v0.18.2 os=linux version=go1.14.4
chandu9333@test:~$ kubectl -n myns get jaeger
NAME              STATUS    VERSION   STRATEGY   STORAGE   AGE
jaeger-instance   Running   1.19.2    allinone   memory    41m

Operator logs:
time="2020-10-09T09:20:48Z" level=info msg=Versions arch=amd64 identity=myns.jaeger-operator jaeger=1.20.0 jaeger-operator=v1.20.0 operator-sdk=v0.18.2 os=linux version=go1.14.4
chandu9333@test:~$ kubectl -n myns get jaeger
NAME STATUS VERSION STRATEGY STORAGE AGE
jaeger-instance Running 1.19.2 allinone memory 41m

That's just the first line of the log. Is that all you see? There should be a lot more :-)

I could see below log:
time="2020-10-09T09:20:48Z" level=info msg=Versions arch=amd64 identity=myns.jaeger-operator jaeger=1.20.0 jaeger-operator=v1.20.0 operator-sdk=v0.18.2 os=linux version=go1.14.4
I1009 09:20:49.291046       1 request.go:621] Throttling request took 1.033169816s, request: GET:https://:443/apis/charts.helm.k8s.io/v1alpha1?timeout=32s
time="2020-10-09T09:21:04Z" level=info msg="Consider running the operator in a cluster-wide scope for extra features"
time="2020-10-09T09:21:05Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"
I1009 09:21:05.713191       1 request.go:621] Throttling request took 1.0431635s, request: GET:https://:443/apis/cert-manager.io/v1beta1?timeout=32s
time="2020-10-09T09:21:12Z" level=info msg="Auto-detected the platform" platform=kubernetes
time="2020-10-09T09:21:12Z" level=info msg="Auto-detected ingress api" ingress-api=networking
time="2020-10-09T09:21:12Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no
time="2020-10-09T09:21:12Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=yes
time="2020-10-09T09:21:12Z" level=info msg="The service account running this operator does not have the role 'system:auth-delegator', consider granting it for additional capabilities"
I1009 09:21:15.749306       1 request.go:621] Throttling request took 2.943649241s, request: GET:https://:443/apis/apm.k8s.elastic.co/v1?timeout=32s
time="2020-10-09T09:21:20Z" level=warning msg="could not generate and serve custom resource metrics" error="discovering resource information failed for Jaeger in jaegertracing.io/v1: unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
time="2020-10-09T09:21:21Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"
I1009 09:21:25.751451       1 request.go:621] Throttling request took 1.44745299s, request: GET:https://:443/apis/integreatly.org/v1alpha1?timeout=32s
I1009 09:21:35.775960       1 request.go:621] Throttling request took 3.297778484s, request: GET:https://:443/apis/custom.metrics.k8s.io/v1beta1?timeout=32s
time="2020-10-09T09:21:37Z" level=warning msg="could not create ServiceMonitor object" error="unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
time="2020-10-09T09:21:37Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"
time="2020-10-09T09:48:48Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"
time="2020-10-09T09:48:48Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"
time="2020-10-09T09:49:22Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"
time="2020-10-09T10:06:22Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"
time="2020-10-09T10:06:22Z" level=warning msg="failed to setup the Jaeger exporter" error="write udp <IP_ADDRESS>:41127-><IP_ADDRESS>:6831: write: connection refused"

Are you sure your Kubernetes cluster is in a sane state?

@chandu9333 looking at the example you are using, it references a very old version of Jaeger:
image: jaegertracing/all-in-one:1.13

Could you either try with a more recent version (1.19) - or remove the image line from the CR?

Removed image line from CR, but still no change

One thing I noticed now, when I did the test again.

I am able to upgrade by changing jaegertracing/jaeger-operator:1.19 to jaegertracing/jaeger-operator:1.20.

It automatically upgrades Jaeger-instance pod iwith the version as 1.20 but I can see through describe pod command only.

when I run kubectl get jaeger command then the output still shows 1.19.2 only

Instance events shows the latest image(BTW, I removed the image line from CR)
instance
Events:
Type    Reason     Age    From                                                          Message

Normal  Scheduled  4m32s  default-scheduler                                             Successfully assigned my-ns/jaeger-instance-7bff55675-6tc2v to mycluster-gke
Normal  Pulled     4m31s  kubelet, mycluster-gke  Container image "jaegertracing/all-in-one:1.20.0" already present on machine
Normal  Created    4m31s  kubelet, mycluster-gke Created container jaeger
Normal  Started    4m31s  kubelet, mycluster-gke Started container jaeger

Could you run the operator with --log-level=debug? Upon bootstrap, the Jaeger Operator will list all Jaeger instances that it manages and will attempt to upgrade all of them. I don't see anything about it in the log: this, and the other warnings in the log, are what made me think that your cluster isn't healthy.
The debug-level log entries will help us understand if the Jaeger Operator is even finding the Jaeger instances.

Log during the deployment using jaeger-operator version 1.19 (cr points to 1.19 image)
time="2020-10-13T07:49:42Z" level=info msg=Versions arch=amd64 identity=my-ns.jaeger-operator jaeger=1.19.2 jaeger-operator=v1.19.0 operator-sdk=v0.18.2 os=linux version=go1.14.4
I1013 07:49:43.220853       1 request.go:621] Throttling request took 1.025828713s, request: GET:https://IP:443/apis/enterprisesearch.k8s.elastic.co/v1beta1?timeout=32s
time="2020-10-13T07:50:07Z" level=info msg="Consider running the operator in a cluster-wide scope for extra features"
I1013 07:50:08.234133       1 request.go:621] Throttling request took 1.043145701s, request: GET:https://IP:443/apis/kafka.strimzi.io/v1alpha1?timeout=32s
time="2020-10-13T07:50:15Z" level=info msg="Auto-detected the platform" platform=kubernetes
time="2020-10-13T07:50:15Z" level=info msg="Auto-detected ingress api" ingress-api=networking
time="2020-10-13T07:50:15Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no
time="2020-10-13T07:50:15Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=yes
time="2020-10-13T07:50:15Z" level=info msg="The service account running this operator does not have the role 'system:auth-delegator', consider granting it for additional capabilities"
I1013 07:50:18.274961       1 request.go:621] Throttling request took 2.944503099s, request: GET:https://IP:443/apis/pxc.percona.com/v1-5-0?timeout=32s
time="2020-10-13T07:50:23Z" level=warning msg="could not generate and serve custom resource metrics" error="discovering resource information failed for Jaeger in jaegertracing.io/v1: unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
I1013 07:50:28.277252       1 request.go:621] Throttling request took 1.44747271s, request: GET:https://IP:443/apis/internal.autoscaling.k8s.io/v1alpha1?timeout=32s
I1013 07:50:38.287855       1 request.go:621] Throttling request took 3.246205942s, request: GET:https://IP:443/apis/integreatly.org/v1alpha1?timeout=32s
time="2020-10-13T07:50:39Z" level=warning msg="could not create ServiceMonitor object" error="unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
time="2020-10-13T07:50:39Z" level=debug msg="Not running on OpenShift, so won't configure OAuthProxy imagestream."
time="2020-10-13T07:50:39Z" level=debug msg="Reconciling Jaeger" execution="2020-10-13 07:50:39.841876538 +0000 UTC" instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="Strategy chosen" instance=jaeger-instance namespace=my-ns strategy=allinone
time="2020-10-13T07:50:39Z" level=debug msg="Creating all-in-one deployment" instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="Assembling the UI configmap" instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="Assembling the Sampling configmap" instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="Assembling an all-in-one deployment" instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="skipping agent daemonset" instance=jaeger-instance namespace=my-ns strategy=
time="2020-10-13T07:50:39Z" level=debug msg="updating service account" account=jaeger-instance instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="updating config maps" configMap=jaeger-instance-ui-configuration instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="updating config maps" configMap=jaeger-instance-sampling-configuration instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:39Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-collector
time="2020-10-13T07:50:39Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-query
time="2020-10-13T07:50:40Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-agent
time="2020-10-13T07:50:40Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-collector-headless
time="2020-10-13T07:50:40Z" level=debug msg="updating deployment" deployment=jaeger-instance instance=jaeger-instance namespace=my-ns
time="2020-10-13T07:50:40Z" level=debug msg="Deployment has stabilized" desired=1 name=jaeger-instance namespace=my-ns ready=1
time="2020-10-13T07:50:40Z" level=debug msg="Reconciling Jaeger completed" execution="2020-10-13 07:50:39.841876538 +0000 UTC" instance=jaeger-instance namespace=my-ns
**Logs during the upgrade (Using 1.20 image which is again created a new operator pod) **
time="2020-10-13T07:59:45Z" level=info msg=Versions arch=amd64 identity=my-ns.jaeger-operator jaeger=1.20.0 jaeger-operator=v1.20.0 operator-sdk=v0.18.2 os=linux version=go1.14.4
I1013 07:59:46.201610       1 request.go:621] Throttling request took 1.032274139s, request: GET:https://IP:443/apis/admissionregistration.k8s.io/v1?timeout=32s
time="2020-10-13T07:59:53Z" level=info msg="Consider running the operator in a cluster-wide scope for extra features"
I1013 07:59:56.241410       1 request.go:621] Throttling request took 2.940179401s, request: GET:https://IP:443/apis/admissionregistration.k8s.io/v1beta1?timeout=32s
time="2020-10-13T08:00:01Z" level=info msg="Auto-detected the platform" platform=kubernetes
time="2020-10-13T08:00:01Z" level=info msg="Auto-detected ingress api" ingress-api=networking
time="2020-10-13T08:00:01Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no
time="2020-10-13T08:00:01Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=yes
time="2020-10-13T08:00:01Z" level=info msg="The service account running this operator does not have the role 'system:auth-delegator', consider granting it for additional capabilities"
I1013 08:00:06.248832       1 request.go:621] Throttling request took 1.397398195s, request: GET:https://IP:443/apis/apm.k8s.elastic.co/v1beta1?timeout=32s
time="2020-10-13T08:00:09Z" level=warning msg="could not generate and serve custom resource metrics" error="discovering resource information failed for Jaeger in jaegertracing.io/v1: unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
I1013 08:00:16.251300       1 request.go:621] Throttling request took 3.296738372s, request: GET:https://IP:443/apis/cert-manager.io/v1beta1?timeout=32s
time="2020-10-13T08:00:25Z" level=warning msg="could not create ServiceMonitor object" error="unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request, custom.metrics.k8s.io/v1beta2: the server is currently unable to handle the request, external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
time="2020-10-13T08:00:25Z" level=debug msg="Not running on OpenShift, so won't configure OAuthProxy imagestream."
time="2020-10-13T08:00:25Z" level=debug msg="Reconciling Jaeger" execution="2020-10-13 08:00:25.949458463 +0000 UTC" instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:25Z" level=debug msg="Strategy chosen" instance=jaeger-instance namespace=my-ns strategy=allinone
time="2020-10-13T08:00:25Z" level=debug msg="Creating all-in-one deployment" instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:25Z" level=debug msg="Assembling the UI configmap" instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:25Z" level=debug msg="Assembling the Sampling configmap" instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:25Z" level=debug msg="Assembling an all-in-one deployment" instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:25Z" level=debug msg="skipping agent daemonset" instance=jaeger-instance namespace=my-ns strategy=
time="2020-10-13T08:00:26Z" level=debug msg="updating service account" account=jaeger-instance instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:26Z" level=debug msg="updating config maps" configMap=jaeger-instance-ui-configuration instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:26Z" level=debug msg="updating config maps" configMap=jaeger-instance-sampling-configuration instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:26Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-agent
time="2020-10-13T08:00:26Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-collector-headless
time="2020-10-13T08:00:26Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-collector
time="2020-10-13T08:00:26Z" level=debug msg="updating service" instance=jaeger-instance namespace=my-ns service=jaeger-instance-query
time="2020-10-13T08:00:26Z" level=debug msg="updating deployment" deployment=jaeger-instance instance=jaeger-instance namespace=my-ns
time="2020-10-13T08:00:26Z" level=debug msg="Deployment has stabilized" desired=1 name=jaeger-instance namespace=my-ns ready=1
time="2020-10-13T08:00:26Z" level=debug msg="Reconciling Jaeger completed" execution="2020-10-13 08:00:25.949458463 +0000 UTC" instance=jaeger-instance namespace=my-ns
Once the Operator is up and running I can see the Jaeger-operator and Jaeger version as 1.20 on the pod (exec to pod) as below
Jaeger-operator version display as below for old deployment using 1.19 image
chandu9333@test:~$ kubectl -n my-ns exec -it jaeger-operator-55fb49b65b-7lgsw -- bash
bash-4.4$ jaeger-operator version
{"jaeger-operator":"v1.19.0","build-date":"2020-08-27T11:46:42Z","jaeger-version":"1.19.2","go-version":"go1.14.4","operator-sdk-version":"v0.18.2"}
bash-4.4$ command terminated with exit code 137
When I start deployment again using 1.20 image (operator.yaml file), pod gets terminated and re-created the new pod with new version
Below is the output once I exec into operator pod
chandu9333@test:~$ kubectl -n my-ns exec -it jaeger-operator-79ffc9fc48-q6rs8 -- bash
bash-4.4$ jaeger-operator version
{"jaeger-operator":"v1.20.0","build-date":"2020-09-30T10:52:11Z","jaeger-version":"1.20.0","go-version":"go1.14.4","operator-sdk-version":"v0.18.2"}
After the upgrade also still shows the jaeger version as 1.19.2
chandu9333@test:~$ kubectl -n my-ns get jaeger
NAME              STATUS    VERSION   STRATEGY   STORAGE   AGE
jaeger-instance   Running   1.19.2    allinone   memory    100m
One more question (sorry for my layman terms as I am new to k8s) ?
Why pods get terminated and re-created when we update image. Is this expected behavior?
Lets assume, I have an operator and all-in-one deployment ready with 1.19 and able to see the traces
After somedays, If want to upgrade it to latest version as soon as it is available in the market, do I loose data/spans/traces/mesh which are from old version?

Looks like the upgrade is indeed somehow broken, I was able to reproduce your case. @rubenvp8510 is it perhaps because of the semantic versioning changes? Could you investigate it ?

Why pods get terminated and re-created when we update image. Is this expected behavior?

This is the expected Kubernetes behavior: whenever a deployment changes, new pods are created to use the new configuration and the old pods are killed.

So if I use Production/streaming strategy with elastic search as backend storage, we don't loose any data after upgradation right?

You won't lose any data that is already in the storage. You should also not lose any in-flight data while the old pod is shutting down and the new one is starting, but I wouldn't be surprised if a few spans would be lost during this process.

Thanks.
When can we expect the fix for the issue regarding the version?

We might have it ready for the next release (1.21.0), which should be due in a month or so. But no promises.


Xrm.Page.formContext deprecated but no alternative provided

"An HTML web resource may interact with the Xrm.Page or Xrm.Utility objects within the form by using parent.Xrm.Page or parent.Xrm.Utility"
Also Xrm.Page is being deprecated. Article
To prevent a gap in functionality, how will an HTML web resource included on an entity form access the form's context, when the only supported method available today is being deprecated?
Can we depend on there being a supported alternative to "parent.Xrm.Page" by the time Xrm.Page is removed?

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

ID: f3caa944-4167-d25d-4464-ee6b4eddfe71
Version Independent ID: f75e4fb9-a542-e20a-7c02-96dde0be4a44
Content: Webpage (HTML) web resources (Developer Guide for Dynamics 365 Customer Engagement (on-premises))
Content Source: ce/customerengagement/on-premises/developer/webpage-html-web-resources.md
Service: crm-online
GitHub Login: @JimDaly
Microsoft Alias: jdaly

Please find someone who is accountable for this API to own this topic.

@Tim-Townsend Please use the getContetWindow method in the form and pass the Xrm object and/or the formContext into the HTML webresource. Closing the issue. Please reopen the issue, if you think the information provided is not enough.

So the getContentWindow method will work if you've got it on a form, but what about open a resource in a new page or from the sitemap?


scripts: use current Python executable when running command lines

Some of the "prebuild" command lines require execution of Python; but running the "python" command doesn't work on some systems (e.g. Linux systems that use "python" to mean Python 2 and "python3" to refer to Python 3, that don't happen to have Python 2 installed), and can cause the invocation of an unknown Python in any case (e.g. if a script is started with Python3.7, but there's also an installed Python2, the "wrong" Python may be invoked).
This fix allows a syntax, "{python}", that can be used for command strings in known_good.json.  The command strings are formatted to replace "{python}" with a value dependent on the system runtime, and then are split via shlex.split() and invoked.
update_deps.py:

define a split_command() function that both formats and splits a command line
use split_command() instead of shlex.split()

known_good.json:

glslang prebuild "python update_glslang_sources.py" replaced with "{python} update_glslang_sources.py"

CI Vulkan-ExtensionLayer build # 214 passed.

CI Vulkan-ExtensionLayer build queued with queue ID 22894.

CI Vulkan-ExtensionLayer build # 215 running.

CI Vulkan-ExtensionLayer build queued with queue ID 22901.

CI Vulkan-ExtensionLayer build # 216 running.

CI Vulkan-ExtensionLayer build # 216 passed.


Lodash "Prototype Pollution"

Lodash needs to be updated ti 4.17.19 or later to fix this error.
When you install quick.db, it makes an npm audit security error. (viewable from npm audit)
Whenever someone can fix this, it would be great!
More info; https://npmjs.com/advisories/1523

Fixed #166


feat: Supabase development and integration (BE)

[x] Implement sign up for supabase.
[x] Implement sign in for supabase.
[x] Implement API authentication for supabase access token.
[x] Migrate postgres DB and migrations to supabase.

This is done.


Fix GET > POST

I can't merge it because I have no right on cozy-labs. It's good to merge for me.

Looks like nobody besides @frankrousseau has access to cozy-labs repo
(they dont belong to the "Cozy Team" team ?)
I will version and publish to NPM directly.


good first issue

What is the current behavior?

What changes are you suggesting?

Additional information

What is the current behavior?
What changes are you suggesting?
Additional information

This issue is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussions!


HADOOP-16104. Wasb tests to downgrade to skip when test a/c is namesp…

…ace enabled. Contributed by Masatake Iwasaki.
(cherry picked from commit aa3ad3660506382884324c4b8997973f5a68e29a)

Description of PR
cherry-pick of aa3ad3660506382884324c4b8997973f5a68e29a from trunk to branch-2.10
The unit tests that fail in this PR are also failing in the vanilla branch-2.10
@omalley  can you please review it?
How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[x] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
8m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 5 new or modified test files.

_ branch-2.10 Compile Tests _

+1 :green_heart:
mvninstall
17m 13s

branch-2.10 passed

+1 :green_heart:
compile
0m 35s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
0m 29s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
0m 27s

branch-2.10 passed

+1 :green_heart:
mvnsite
0m 36s

branch-2.10 passed

+1 :green_heart:
javadoc
0m 34s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
0m 23s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
1m 17s

branch-2.10 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
compile
0m 23s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
javac
0m 23s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 14s

the patch passed

+1 :green_heart:
mvnsite
0m 28s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 21s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
0m 55s

the patch passed

_ Other Tests _

-1 :x:
unit
1m 15s
/patch-unit-hadoop-tools_hadoop-azure.txt
hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
0m 26s

The patch does not generate ASF License warnings.

38m 29s

Reason
Tests

Failed junit tests
hadoop.fs.azure.TestNativeAzureFileSystemOperationsMocked

hadoop.fs.azure.TestNativeAzureFileSystemContractMocked

hadoop.fs.azure.TestOutOfBandAzureBlobOperations

hadoop.fs.azure.TestBlobMetadata

hadoop.fs.azure.TestNativeAzureFileSystemFileNameCheck

hadoop.fs.azure.TestWasbFsck

hadoop.fs.azure.TestNativeAzureFileSystemMocked

hadoop.fs.azure.TestNativeAzureFileSystemConcurrency

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4137/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4137

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell xml

uname
Linux 564b735fb2cc 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / db01a368182827061289353e189f36b7f0c7f8f1

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4137/1/testReport/

Max. process+thread count
261 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4137/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

+1 on this cherry pick


[BUG] Unable to install OpenSearch from repo since SHA-1 for signing is deprecated in RHEL9

Describe the bug
Unable to install OpenSearch using yum/dnf in RHEL9 distros due to SHA-1 for signing being deprecated
https://www.redhat.com/en/blog/rhel-security-sha-1-package-signatures-distrusted-rhel-9
To Reproduce
Steps to reproduce the behavior:

Following docs from https://opensearch.org/docs/latest/install-and-configure/install-opensearch/rpm/#install-opensearch-from-a-yum-repository
run sudo curl -SL https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/opensearch-2.x.repo -o /etc/yum.repos.d/opensearch-2.x.repo
dnf clean all
dnf update
dnf install opensearch-2.0.1

Importing GPG key 0x9310D3FC:
 Userid     : "OpenSearch project<EMAIL_ADDRESS> Fingerprint: C5B7 4989 65EF D1C2 924B A9D5 39D3 1987 9310 D3FC
 From       : https://artifacts.opensearch.org/publickeys/opensearch.pgp
Is this ok [y/N]: y
warning: Signature not supported. Hash algorithm SHA1 not available.
Key import failed (code 2). Failing package is: opensearch-2.0.1-1.x86_64
 GPG Keys are configured as: https://artifacts.opensearch.org/publickeys/opensearch.pgp
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

Expected behavior
To be able to install OpenSearch from repo using a package manager on RHEL9 base distros
Plugins
N/A
Screenshots
N/A
Host/Environment (please complete the following information):

OS: Rocky Linux 9
Version 9.1 (Blue Onyx)

Additional context
GPG key and packages should be signed using SHA256 or SHA521.

This issue has been tracked at https://github.com/opensearch-project/opensearch-build/issues/3124

Closing this issue as duplicate of https://github.com/opensearch-project/opensearch-build/issues/3124


Bigrat is slightly too small on my machine

I'm using Firefox Windows 10. As it stands, Bigrat is a little bit too small for me. Here's what I mean:
Bigrat (small) is outlined in red. My proposed Bigrat (big) is outlined in green.

Please fix asap (no worries if you can't get to it today), I would like Bigrat to be a little bit bigger. Thank you

kek


MongoError: cannot use the part (roles of roles.global_roles) to traverse the element

The user in question has roles that are not part of a group.  I am trying to add a role which is part of
Roles.GLOBAL_GROUP

and I get the following error
MongoError: cannot use the part (roles of roles.__global_roles__) to traverse the element

Any insight into it's meaning would be great, thanks.  Not really sure where to start on this.

I would guess that it has to do with the structure of the roles field on the user object.
The choice to use groups should be a global one; either all users should use groups or none of your users should use them.  To convert from no-groups to groups, you would manually change the structure to match what the roles package expects as shown here:  https://github.com/alanning/meteor-roles#changes-to-default-meteor-behavior
Here's a small script that I used when we did the conversion for our startup:  https://gist.github.com/alanning/0686f29c71b8cab54cc7
Any issues, let me know.

That was indeed the issue, thanks a ton.


Fix shellcheck warnings

This resolves some of the obvious shellcheck warnings. There are still a few more, but they require a bit more digging to fully grasp what is being called out so I decided to leave them untouched.

Tests passed! Merging now.

https://github.com/hashicorp/terraform-aws-consul/releases/tag/v0.7.8


x/sync: skipping acquisition if the context is done is a breaking change

Go version
go version go1.21.1 darwin/arm64
Output of go env in your module/workspace:
GO111MODULE='on'
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/xinyu.liu/Library/Caches/go-build'
GOENV='/Users/xinyu.liu/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS='-count=1'
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/xinyu.liu/go/pkg/mod'
GONOPROXY=''
GONOSUMDB='github.cbhq.net'
GOOS='darwin'
GOPATH='/Users/xinyu.liu/go'
GOPRIVATE=''
GOPROXY='https://gomodules.cbhq.net/'
GOROOT='/opt/homebrew/opt/go/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/opt/go/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.21.1'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/xinyu.liu/src/streaming-sdk/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/hh/kbt1yk9d3y56yxzxr382jth80000gn/T/go-build912487987=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?
The PR below introduced a breaking change - a regression, and broke our services deployed in production environments.
https://github.com/golang/sync/commit/14be23e5b48bec28285f8a694875175ecacfddb3
What did you see happen?
We explicitly make use of a zero-timeout context,
ctx, cancel := context.WithTimeout(context.Background(), 0)
defer cancel()

and pass the ctx to sem.Acquire(ctx, 1) to minimize the wait time on a critical path. The goal is to avoid latencies causing by the wait timeouts due to upstream back pressure.
For instance, we use sem to control in-flight messages sent to Kafka. When Kafka brokers experience back pressure, we would like the call to sem.Acquire failed immediately to unblock the main thread, otherwise, it would introduce extra latencies to the critical, user-facing threads.
With this change in the PR, ctx with 0 timeout immediately returns a context cancelled error from sem.Acquire(ctx, 1) even if the semaphore still has a full capacity.
What did you expect to see?
Passing ctx with 0 timeout to sem.Acquire(ctx, int) should successfully acquire the semaphore counts as long as there are still capacity immediately available on the semaphore.

The change in question is https://go.dev/cl/536275, written to address issue #63615.  CC @szuecs @zephyrtronium

From the description of your code, it sounds like you should be using the TryAcquire method rather than the Acquire method.

In that case, I need to figure out the timeout on the context, and call TryAcquire when the timeout is set to zero, and call Acquire when the timeout is not zero.
Since the timeout is set by a client program, it doesn't seem to be viable.
Thoughts?

You can call the context.Context.Deadline method to find out whether the context has timed out.

The 0 timeout that triggers done depends only on the context, so you should fix the context


Question: Vue filtering from graphql dataset

Hi!
How do I create a dynamical filter using a computed property from vue and the graphql dataset from gridsome? I've looked at several articles that all use the array.filter()-method, but I can't get it to work on my case. It seems like the "node"-part of the graphql-object ($page.posts.edges.node.[values]) are making it difficult to use the array.filter(). Is there a way of removing the "node"-part so that the object would be $page.posts.edges.[values]?
This is my first coding project since early 2000, so please feel free to point me in the right direction if this is the wrong forum for this question.
This is my page query:
<page-query>
    query Members {
        posts: allMember(sort: [{ by: "priority", order: ASC }, { by: "created", order: DESC }]) {
            edges {
                node {
                    id
                    slug
                    name
                    image
                    created
                    priority
                    team {
                        name
                    }
                }
            }
        }
    }
</page-query>

I loop through the dataset with:
<member-card
v-for="item in filteredData"
:key="item.node.id"
:item="item">
</member-card>

And try to filter the data from a search box:
<input
type="text"
placeholder="Enter keyword  ..."
v-model="search"
v-on:keyup="getfilteredData"
/>

My method for returning the filteredData is:
getfilteredData: function() {
      this.filteredData = this.$page.posts.edges;
      let filteredDataByfilters = [];
      let filteredDataBySearch = [];
      if (this.search !== "") {
        filteredDataBySearch = this.filteredData.node.filter(
          obj => obj.name.indexOf(this.search.toLowerCase()) >= 0
        );
        this.filteredData = filteredDataBySearch;
      }
    }

I tried to set up a jsfiddle to play with the case without the graphql from gridsome (using an example from https://jsfiddle.net/paulsandip2110/23wws1ac/14/).

Computed properties in a Vue component should return your filtered data like this:
export default {
  data () {
    return {
      search: ''
    }
  },
  computed: {
    filteredData () {
      return this.$page.posts.edges.filter(edge => {
        return edge.node.name.indexOf(this.search.toLowerCase()) >= 0
      })
    }
  }
}

With this computed property, there is no need to call a getfilteredData method on keyup. The reactivity system in Vue will automatically re-evaluate filteredData and re-render your template when search is changed :)

That worked. Thanks!

Hi, can this be ammended to filter posts from allPages?


docs: show how to make optional and required field-label

Purpose
FieldLabel does not provide out-of-box solution for required and optional identification, such should be composed manually.
Approach
Two new stories shows how "optional" and "required" field labels can be composed.
Testing
On Storybook.
Risks
N/A

As requested by @Subcide ☝


Certificate Error

I dont know what went wrong:
------------------------ LOGS----------------------
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 703, in urlopen
httplib_response = self._make_request(
File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 386, in _make_request
self._validate_conn(conn)
File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
conn.connect()
File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 467, in connect
_match_hostname(cert, self.assert_hostname or server_hostname)
File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 540, in _match_hostname
match_hostname(cert, asserted_hostname)
File "/usr/local/lib/python3.10/site-packages/urllib3/util/ssl_match_hostname.py", line 155, in match_hostname
raise CertificateError("hostname %r doesn't match %r" % (hostname, dnsnames[0]))
urllib3.util.ssl_match_hostname.CertificateError: hostname 'tw.business.smartcamera.api.io.mi.com' doesn't match 'home.mi.com'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 489, in send
resp = conn.urlopen(
File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 787, in urlopen
retries = retries.increment(
File "/usr/local/lib/python3.10/site-packages/urllib3/util/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='tw.business.smartcamera.api.io.mi.com', port=443): Max retries exceeded with url: /common/app/get/eventlist?xxx (Caused by SSLError(CertificateError("hostname 'tw.business.smartcamera.api.io.mi.com' doesn't match 'home.mi.com'")))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update
raise exc
File "/config/custom_components/xiaomi_miot/camera.py", line 295, in async_update
rdt = await mic.async_request_api(api, rqd, method='GET', crypt=True) or {}
File "/config/custom_components/xiaomi_miot/core/xiaomi_cloud.py", line 160, in async_request_api
return await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/xiaomi_miot/core/xiaomi_cloud.py", line 174, in request_miot_api
rsp = self.request_rc4_api(api, params, method, **kwargs)
File "/config/custom_components/xiaomi_miot/core/xiaomi_cloud.py", line 578, in request_rc4_api
response = self.session.get(url, params=params, timeout=timeout)
File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 600, in get
return self.request("GET", url, **kwargs)
File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 587, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 701, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 563, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='tw.business.smartcamera.api.io.mi.com', port=443): Max retries exceeded with url: /common/app/get/eventlist?xxx (Caused by SSLError(CertificateError("hostname 'tw.business.smartcamera.api.io.mi.com' doesn't match 'home.mi.com'")))

Please contact MiHome customer service to update the ssl certificate.


README.md contains broken links

Hi Aos maintainers,
I found three broken links in the root CM README.md.
I sent PR https://github.com/aoscloud/aos_communicationmanager/pull/7 for the first one.
The following two I can not fix as I can not be sure what to link to:

Link to architecture document.
Source: https://github.com/aoscloud/aos_communicationmanager/blob/fc8fb43c854630ccbb5251946c793d1674d0cde8/README.md?plain=1#L13
I couldn't find architecture.md in the CM component source and there is no doc sub-directory.

Link to config.md
Source: https://github.com/aoscloud/aos_communicationmanager/blob/fc8fb43c854630ccbb5251946c793d1674d0cde8/README.md?plain=1#L55

Thank you for finding. We will fix it as soos as define documentation storage.

Resolved


example uploading media

thanks for this lib
do you think you could provide an example of posting media, as does this lib:
https://github.com/istrategylabs/node-twitter
thx!!

https://github.com/desmondmorris/node-twitter/tree/master/examples
answered my own bad questions


SSH fingerprints and key length in the Lagoon UI

Describe the feature
I wish to see the SSH key fingerprint in the UI next to the keyname. Bonus points for the key length in bits.
Expected behavior
Seeing this data is a lot more useful in the UI.
$ ssh-keygen -l -E md5 -f ~/.ssh/id_rsa.pub
4096 MD5:cf:19:96:94:52:7c:33:98:10:60:31:33:96:a3:69:44<EMAIL_ADDRESS>(RSA)

Prior art
This is what Github does

Github uses the new way to output:

It looks like this was already fixed in #2125, as currently we have:

Github uses the new way to output:

It looks like this was already fixed in #2125, as currently we have:

@seanhamlin can this be closed?

Sure can, thanks!


Split up monolithic SConstruct into many small parts.

New Module system.
Many modules to deal with common libraries.
Simple "hello, world" for Beast.

A no-op build went from ~1 sec with the old sconstruct to ~4 secs with the new. We should look at putting some of those optimizations back. (I don't know what specifically yet).

All right!
I made some more changes to clean things up though I still haven't fixed the problems I listed before:
In particular, a new Build.py has all the names that a client uses from the build system.

I just pushed a lot more changes.
Now it works perfectly again on OS/X.  I simplified a lot of names and some of the logic.
I still don't know if it works on Windows, anyone want to test for me?

Does not work on Windows:

The vcxproj is invalid
scons vcxproj malfunctions

Can I get more information than "malfunctions"?

(I can fix the vcxproj if it doesn't work, but what goes wrong with the main build?)

scons vcxproj works on Linux, and does not result in a delta...

Fixing travis for this branch...

@rec The vcxproj at the tip of the branch fails to load in msvc, and issuing scons vcxproj returns immediately with an empty vcxproj.

OK, I can repro that.  I'll see what I can do!

Update:  I got past two problems involving the vcxproj but now I have an issue which I just discovered was because I have a list of files, some of which are strings and some, SCons.Node.FS.File objects, and the VSProject code doesn't like that.  (Clearly the rest of Scons doesn't mind at all...)
I'm not stuck and we're getting further into it, just wanted to report.
It took me a while to realize overall how the vcxproj process works - in the special case of the target vcxproj, it adds targets as if for the msvc targets, and as a side effect gathers some values for msvc in a "global variable".  The issue is that I had equated adding a target to be buildable, with actually building that target!  Fixing that wasn't hard, once I understood, but then the problem was figuring out a way to do it without hardcoding vcxproj in the build structure...  (which I did...)
Ongoing work here:  https://github.com/rec/rippled/tree/x-scons-2

Closing this, it is no longer being actively worked on. It may be re-opened later.


Does transformers use the custom CUDA kernel?

You mean the huggingface implememtation? No

You mean the huggingface implementation? No

So the time complexity is still O(n^2) ?
Why not use global attention for all tokens if the time complexity is not falling ？

So the time complexity is still O(n^2) ?

The HF implementation is using our sliding_chunks implementation of the sliding window attention (check readme for details), and its time/memory complexity if O(n).

Why not use global attention for all tokens if the time complexity is not falling ？

Global attention for all tokens is equivalent to full O(n^2) attention which is still problematic.

So the time complexity is still O(n^2) ?

The HF implementation is using our sliding_chunks implementation of the sliding window attention (check readme for details), and its time/memory complexity if O(n).

Why not use global attention for all tokens if the time complexity is not falling ？

Global attention for all tokens is equivalent to full O(n^2) attention which is still problematic.

Thanks~

Closing. Please feel free to reopen if needed.


Add Engineer Level Fixer from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of civilwargeeky, to add Engineer Level Fixer to CKAN.
Please direct questions about this pull request to civilwargeeky.

Oh hey. I hadn't realized that I checked the "add to CKAN" box when I published my mod. I had instead earlier made #3218 to add my new mod to CKAN.
Sorry for the trouble.

Closing this for #3218


🐛 Bug Report: Catalog won't start due to TypeError: meter.createGauge is not a function (v1.34.0-next.1)

📜 Description
We upgraded the Demo site to the latest next version - v1.34.0-next.1 - and now it isn't starting up. After running the code locally we noticed the following error during the start up of the backend:
Error: Failed to instantiate service 'core.scheduler' for 'catalog' because the factory function threw an error, TypeError: meter.createGauge is not a function

👍 Expected behavior
The backend should start up as expected.
👎 Actual Behavior with Screenshots
The backend does not start up and we get the following error:
Error: Failed to instantiate service 'core.scheduler' for 'catalog' because the factory function threw an error, TypeError: meter.createGauge is not a function

👟 Reproduction steps
Pull down the latest code from the Demo site and run yarn dev you'll get the error right away.
📃 Provide the context for the Bug.
This is preventing us from deploying the latest next version - v1.34.0-next.1 - of the Demo site and it's currently crashing.
🖥 Your Environment
This is specifically a regression in v1.34.0-next.1
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

Closing as duplicate of as I didn't think they were related initially: https://github.com/backstage/backstage/issues/27979

This will be fixe din the next, next release, workaround for now is to add a resolution like this: @opentelemetry/api": "1.9.0"


Remove old maximum-likelihood fitters

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

These have been deprecated, but now let’s remove them completely.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Fixed in PR 213


Required conditional fields prevent form submission

As the title states if you have a conditionally required field you can not submit the form.
Running the latest version of this module 2.1.2 and all supporting modules are fairly up to date.
Gravity Forms export: gravityforms-export-2024-08-07 (1).json

Built the latest git version and the conditional logic looks to be working. Thanks for the quick fix on this.

We've released version 2.1.3, which should resolve this issue. Therefore, I'm closing it now


[Specific-PSXPC_N] Textures when underwater are bad.

If Lara is underwater the textures are messed up.

Fixed in: https://github.com/TOMB5/TOMB5/commit/23b97050ceac7a95b32a5ff3fbb5f06767ae96ac


Payggy: form validation

Check whether user has enough money, they have inputted valid number etc.

Related issue: #182


folasade/auth context

What's new in this PR
Auth context
Description
Added auth context file, but some changes still need to be made for functions inside file
Screenshots
How to review
Right now the only function that is currently using the authcontext file is the sign up function, there's some console.logs (i will be taking out very soon) in the profile tab that you can compare the current auth queries to the auth context file
Next steps
Still need to change functions that should rely on auth context file rather than supabase queries, clean up authcontext file
Relevant Links
Online sources
Related PRs
CC: @ronniebeggs

Still soooo much to do this is truly a WIP

We merged this functionality into the app form a different PR.


Create the Post Card and Post Component

[ ] Create the Post card which will be used to show case the Post
[ ] Create the Post section to list all the posts
[ ] Connect Upvote and downvote functionaliies to Post

[x]  Create the Post card which will be used to show case the Post
[x]  Create the Post section to list all the posts
[x]  Connect Upvote and downvote functionaliies to Post