feat: added routing test to amtool

Hi @stuartnelson3, we talked for a while at the PromCon about multi-tenancy of Alertmanager and increasing complexity of routing configuration.
So I thought some testing would be useful to avoid misconfiguration.
This PR adds routing-test command to the amtool which accepts label definition of an alert and returns all receivers which the alert resolves to. It allows to load Alertmanager config from file or remotely
example usage is
$ ./amtool routing-test --config.file=doc/examples/simple.yml  service=database
team-DB-pager

I also added flag --verify.receivers which also checks if resulting receivers match those specified and if not the return code is 1. I'm not sure if it should be implemented in the amtool but it makes testing easier.
This should allow user to define tests for the routing rules.
Also you can run it against the new config and actual config using the remote config loading and display changes in routing introduced by the new updates.
I'd be glad for any comments or suggestions on this.

if we go that path, would a --debug option help too to see the routes taken by the labels?

Hmm that sounds reasonable, but the issue is routes does not have any names so I'm not sure how should the output look like.

also there is possibility to use something like https://github.com/xlab/treeprint
to also draw simple ASCII tree view. But that would be duplication of https://prometheus.io/webtools/alerting/routing-tree-editor/ functionality.

Thanks for looking at this!
I think the treeprint suggestion would be pretty cool, personally. I think there's a huge benefit to having this, and being able to do it locally is something a lot of people would like. Although the tree routing visualizer on the website does everything in the browser and doesn't store or transmit any of the entered data, people are still cautious about copying and pasting their information into a website.
The functionality so far looks cool, but it would also be helpful to add something like --tree so that the route could be visualized as @roidelapluie said (or --debug, we can think about the naming)

I'm also thinking where this should live .. maybe it should be under amtool config routing-tree

Ok, no problem. I'll be happy to add the tree visualization option.
I like the amtool config routing-tree naming, but I'm not sure how should the rest look like.
amtool config routing-tree test [--tree] lavel=value (test the alert routing, --tree would print just tree for specified alert)
and
amtool config routing-tree show  (would print the tree or without the show)
? Thanks for suggestions

for a rough UI how about:
amtool config routes [show] # shows tree, default action with no subcommand.
amtool config routes test [--tree] label1=value1 label2=value2 labeln=valuen # see how alert creation implements this

We've been calling it a routing-tree for a while but I've been wondering about that name. Let's try just using routes as the subcommand and see how it feels for now, and see what others think about it.

Ok I have a new version according to your suggestion
I added to vendor the https://github.com/xlab/treeprint library
The tree visualization could be better but the library is simple and works quite well.
But we can change it if you want.
Output looks like this:
$ ./amtool config routes --config.file test.yml
Routing tree:
.
└── {}  continue: false  receiver: blackhole
    ├── {service="api"}  continue: true  receiver: slack
    │   ├── {severity="critical"}  continue: true  receiver: pagerduty
    │   └── {severity="low"}  continue: true  receiver: mattermost
    ├── {service="database"}  continue: true  receiver: pagerduty
    └── {service=~"^(?:.*)$"}  continue: true  receiver: email
        └── {service=~"^(?:.*)$"}  continue: true  receiver: email
            └── {service=~"^(?:.*)$"}  continue: false  receiver: email

The tree output in test mode omits continue and receivers of parent routes
$ ./amtool config routes test --tree --config.file test.yml service=api severity=critical
Matching tree:
.
└── {}
    ├── {service="api"}
    │   └── {severity="critical"}  receiver: pagerduty
    └── {service=~"^(?:.*)$"}
        └── {service=~"^(?:.*)$"}
            └── {service=~"^(?:.*)$"}  receiver: email

pagerduty,email

Thanks once more for all the comments.
I didn't notice the vendor, I had bad global .gitignore :/

Yay I'm glad you like this feature.
thanks for accepting it :)


run_optimiser.launch ，the program will not exit

Run the program in the ros melodic environment and execute 'roslaunch cam.lidar_calibration run_optimiser. launch import_stamples:=true'. The program will not automatically exit after running, as shown in the following figure

This is normal


ccNumber directive is only returning first four for control value, making validateCCNumber return that the field is invalid

Here's a stackblitz with the example - https://stackblitz.com/edit/angular-sdsgck
With a log here, control.value is always only the first four digits. I haven't been able to find where in the directive this is happening (everywhere I log has all the digits as expected) but with the directive removed, validateCCNumber works great.
Will update as I find more.

In your stackblitz example, you have type='number' and type='tel' on your input.
Remove them and put type="text".
Probably problem not in the library itself, but in angular or browser behaviour, with this attributes it doesn't accept spaces as value in model.

Problem not related to library itself, if you still think this is a library mistake, please create a new issue with a detailed description.


Ability to choose the damage type of a spell / feature when rolling damage

Probably a far - off request but being able to choose the damage type of a roll before its rolled would be nice the have. The two examples that only come to mind would be Chromatic Orb & Nature Domain Cleric's Divine Strike feature.

Possible also useful for features that add damage of the same type to an attack, e.g. sneak attack

I guess Transmuted Spell from sorcerer's metamagic feature can also possibly use this


Incomplete json import

ohai!
Got a weird issue. Only some of the json data gets added to my table. Weird!
json file is here: https://github.com/saltcod/overcast/blob/master/assets/js/overcast.json
All of the data was imported properly a few weeks back when I was working on this, but now I get this situation happening. Not sure what happened in the meantime. Appreciate any suggestions!
https://dl.dropboxusercontent.com/s/fy73b53klgleja6/2017-09-08 at 10.19 PM.png
Thanks!

Hmmm, looks like something got tweaked during an update. I can reproduce it so I'll get it fixed quickly.

This should be fixed in the latest version. Re-open if needed.

Woah!  Ultra quick!!
Yep this fixes the issue.
Many, many thanks for the really quick reply.  Greatly appreciate that, and the plugin itself. Fantastic work!


Populate the database with templates and examples

We'd like to start creating as many general templates as we can to make it easier to find reusable Programs and have something for designers to pull from. This post contains a list of general templates we would like to create in the templates playspace.
Please recommend additional Programs in this issue and they will be added to the top post (this one). If you have access, you may also directly edit this post. Mark off templates that have been created.

[ ] Create Dial mapped to paper rotation
[ ] Create Radio Button
[ ] Create Slider with value mapped to paper position

[ ] And rotation

[ ] Use mouse click event to make something happen

[ ] Mouse down
[ ] Mouse up
[ ] Use mouse position to make something happen

[ ] Use keypress event to make something happen

[ ] Key down
[ ] Key Up

[ ] Create a model Property
[ ] Link to a model Property
[ ] Play sound (complete)

[ ] Play looping sound
[ ] Play sound in response to new value (e.g., from model Property)

[ ] Play TTS

[ ] Play TTS in response to new value (e.g., from model Property)

[ ] Create Image

[ ] Animate Image

[ ] View code for a slider that allows for Qualitative values

Specifically, wondering how a designer can design and test parameters for a slider.

@jessegreenberg and @terracoda spent 2.5 hours creating a few templates and a few snippets and then trying to use them.
We created 3 templates:

Model Template
View Template
Slider Template

To help fill in the templates, we created at least 2 snippets:

a NumberProperty that could be used to create model properties for Voltage and Resistance
a DerivedProperty to calculate Current from Voltage and Resistance
Note each snippet contains code blocks to put under "onProgramAdded" and "onProgramRemoved"

We ran into trouble when we tried to use the templates to recreate the Ohm's Law sliders that we already created.
A typo in the resistance property was one issue we were able to resolve. Unfortunately, there is something else that is not throwing an error that is not working. @jessegreenberg will take a deeper look into the templates to see what the problem is.

I got the template we were working on today working. There was a small problem with how we were positioning our slider. I created a few more examples (in jg-tests space for now), and some more snippets (Voicing, Checkbox, link)

Working on templates has lead us to believe that we should focus on examples instead of open-ended templates. I want to convert this list into keywords we can search for and find places in examples to implement the above desired "templates".
Self-assigning for now to complete and close in favor of specific issues for examples.

We've moved away from templates and examples and have focused on a component interface. Closing.


(3/9) RUM-2127 store the synthetics test info in the RUM Context

This PR has been created automatically by the CI
Store the synthetics test info in the RUM Context.
We store the info directly at the application level, as it will be the same for a given run in Synthetics. If a Synthetics run creates multiple session for any reason, we want  the info to stay available.

Codecov Report

Merging #1716 (a366d7e) into xgouchet/RUM-2127/2_read_synthetics_info (5684cd7) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

Additional details and impacted files
@@                             Coverage Diff                              @@
##           xgouchet/RUM-2127/2_read_synthetics_info    #1716      +/-   ##
============================================================================
- Coverage                                     83.38%   83.35%   -0.03%
============================================================================
  Files                                           465      465
  Lines                                         16085    16089       +4
  Branches                                       2384     2385       +1
============================================================================
- Hits                                          13411    13410       -1
- Misses                                         2034     2042       +8
+ Partials                                        640      637       -3

Files
Coverage Δ

...d/rum/internal/domain/scope/RumApplicationScope.kt
89.90% <100.00%> (+0.43%)
:arrow_up:

... and 17 files with indirect coverage changes


More customization for profile page aesthetics

Who is your user?
Registered users of the website.
What are they trying to achieve?
They would like more customizability when it comes to the aesthetics of their profile. From a specific user request: "We want to change our OC page template- especially by getting rid of the 'bubbles' graphics at the top of the page to somehting more professional."
When , I want to , so I can
How are they currently doing this?
As of right now, it is not possible.
How well understood is this problem?

[X] Surfacing: if you feel this is a seed of an idea that needs to be researched.
[ ] Understanding: if you've done some research and feel it is already well understood and ready for shaping.
[ ] Shaping:  if you feel a solution is clearly defined and can be made into a pitch (read more about shaping)
[ ] Pitching: if you feel that it is ready to be presented for prioritisation (read more about pitching)

especially by getting rid of the 'bubbles' graphics at the top of the page to somehting more professional

We got this feedback a few times, I think @opencollective/design already considered it for future collective page iterations.
Related: https://github.com/opencollective/opencollective/issues/4680
Renaming the issue to be a bit more specific.


Fixed : issue #54

I changed the get in touch section to Subscribe to newsletter section .

@parthpathakpp1 fix conflicts

@parthpathakpp1 fix conflicts

ok

@parthpathakpp1 fix conflicts

@varun-singhh I raised a new PR https://github.com/Deveimer/vovoca-frontend/pull/94 . Please check it .


syncthing: Update to 0.10.17

Changes:

Syncthing's repo moved
One of the tests won't build on Go 1.3. I submitted a pull request to fix that, and also just included the patch so we don't have to wait for the next release.
Dependencies are easier to deal with now, since there's only one "internal" folder.
The TestPredictableRandom test relies on global state, so we can't run it with -cpu.
stcli doesn't exist anymore. I have no idea what this is so maybe someone else should sanity check this.

stcli is probably syncthing/syncthing-cli. You should also raise an issue with tests relying on global state I think.

Global state issue: https://github.com/syncthing/syncthing/issues/1184
Presumable syncthing-cli should be a separate package?

It is, in the same organisation.

stcli should be a separate package then.


Adding keybinds

Would make it easier to hop to a random world, quicker

I was thinking about adding this, but I didn't have a personal need. I will work on adding this.

Updated in the plugin hub release!


Remove Radium.wrap

Remove Radium.wrap, and change Radium.Enhancer to just Radium.
Update all the docs.
Closes #188

I've got to say, Radium as a decorator is absurdly beautiful. Great idea to promote it as the recommended way to use the lib. Everything here looks great :+1:

Coverage remained the same at 100.0% when pulling 546322fe3ebfc944c0d511e0ad7f960a3be8211a on remove-wrap into 9ad6dc500f4d01ec24deb2497ab6880badd5719d on master.


If Face BlendShape is a production ready solution ?

I referenced the source code of FaceBlendShapesGraph and put it into a "legacy" solution in the same way (because TaskRunner didn't work), I used the TensorsToClassificationCalculator and face_blendshapes.tflite file to caculate the ClassificationList and succeeded. After this, I brought it into Unreal Engine.
There are some things that I don't quite understand, and I hope to be able to give guidance：

Whether I solve blendshape through a camera or a video file, I find that the right eye is always smaller than the left eye, and is sensitive to head rotation, and once the character is not directly facing the camera, it seems that the value cannot be solved.

In fact, the left and right eyes of the characters in these pictures are almost the same size.

I integrated iris landmarks in Holistic because I wanted to capture both pose and face blendshapes, and when I requested HolisticTrackingToRenderData render a face landmark with iris, I got strange white lines overlay in face.

Here is a part of the graph  code I used to render annotation overlay：
# Gets two landmarks which define left eye boundary.
node {
  calculator: "SplitNormalizedLandmarkListCalculator"
  input_stream: "face_landmarks"
  output_stream: "left_eye_boundary_landmarks"
  node_options: {
    [type.googleapis.com/mediapipe.SplitVectorCalculatorOptions] {
      ranges: { begin: 33 end: 34 }
      ranges: { begin: 133 end: 134 }
      combine_outputs: true
    }
  }
}
# Gets two landmarks which define right eye boundary.
node {
  calculator: "SplitNormalizedLandmarkListCalculator"
  input_stream: "face_landmarks"
  output_stream: "right_eye_boundary_landmarks"
  node_options: {
    [type.googleapis.com/mediapipe.SplitVectorCalculatorOptions] {
      ranges: { begin: 362 end: 363 }
      ranges: { begin: 263 end: 264 }
      combine_outputs: true
    }
  }
}
# Detects iris landmarks, eye contour landmarks, and corresponding rect (ROI).
node {
  calculator: "IrisLandmarkLeftAndRightCpu"
  input_stream: "IMAGE:transformed_input_video"
  input_stream: "LEFT_EYE_BOUNDARY_LANDMARKS:left_eye_boundary_landmarks"
  input_stream: "RIGHT_EYE_BOUNDARY_LANDMARKS:right_eye_boundary_landmarks"
  output_stream: "LEFT_EYE_CONTOUR_LANDMARKS:left_eye_contour_landmarks"
  output_stream: "LEFT_EYE_IRIS_LANDMARKS:left_iris_landmarks"
  output_stream: "LEFT_EYE_ROI:left_eye_rect_from_landmarks"
  output_stream: "RIGHT_EYE_CONTOUR_LANDMARKS:right_eye_contour_landmarks"
  output_stream: "RIGHT_EYE_IRIS_LANDMARKS:right_iris_landmarks"
  output_stream: "RIGHT_EYE_ROI:right_eye_rect_from_landmarks"
}
node {
  calculator: "ConcatenateNormalizedLandmarkListCalculator"
  input_stream: "left_eye_contour_landmarks"
  input_stream: "right_eye_contour_landmarks"
  output_stream: "refined_eye_landmarks"
}
node {
  calculator: "UpdateFaceLandmarksCalculator"
  input_stream: "NEW_EYE_LANDMARKS:refined_eye_landmarks"
  input_stream: "FACE_LANDMARKS:face_landmarks"
  output_stream: "UPDATED_FACE_LANDMARKS:refined_face_landmarks"
}

node {
  calculator: "ConcatenateNormalizedLandmarkListCalculator"
  input_stream: "refined_face_landmarks"
  input_stream: "left_iris_landmarks"
  input_stream: "right_iris_landmarks"
  output_stream: "face_landmarks_with_iris"
}

#------------------------Holistic Rendering--------------------------

node {
  calculator: "HolisticTrackingToRenderData"
  input_stream: "IMAGE_SIZE:image_size"
  input_stream: "POSE_LANDMARKS:pose_landmarks"
  input_stream: "POSE_ROI:pose_roi"
  input_stream: "LEFT_HAND_LANDMARKS:left_hand_landmarks"
  input_stream: "RIGHT_HAND_LANDMARKS:right_hand_landmarks"
  input_stream: "FACE_LANDMARKS:face_landmarks_with_iris"
  output_stream: "RENDER_DATA_VECTOR:render_data_vector"
}

#Draws annotations and overlays them on top of the input images.
node {
  calculator: "AnnotationOverlayCalculator"
  input_stream: "IMAGE:transformed_input_video"
  input_stream: "VECTOR:render_data_vector"
  output_stream: "IMAGE:output_video"
}

I also had a similar problem when I used this model: https://github.com/google/mediapipe/blob/master/mediapipe/tasks/testdata/vision/face_landmarker_with_blendshapes.task

Using  "https://storage.googleapis.com/mediapipe-assets/face_landmarker_with_blendshapes.task" as the task, results in the following error whenI use detect.
Uncaught (in promise) Error: WaitUntilIdle failed: $CalculatorGraph::Run() failed in Run:
Calculator::Process() for node "mediapipe_tasks_vision_face_landmarker_facelandmarkergraph__mediapipe_tasks_vision_face_landmarker_multifacelandmarksdetectorgraph__mediapipe_tasks_vision_face_landmarker_singlefacelandmarksdetectorgraph__mediapipe_tasks_vision_face_landmarker_faceblendshapesgraph__SplitNormalizedLandmarkListCalculator" failed: RET_CHECK failure (third_party/mediapipe/calculators/core/split_proto_list_calculator.cc:126) ListSize(input) >= max_range_end_ (468 vs. 478) Max range end 478 exceeds list size 468; WaitUntilIdle failed
at O.handleErrors (tasks-vision.js:7781:15)
at O.finishProcessing (tasks-vision.js:7769:47)
at O.process (tasks-vision.js:7883:228)
at O.processVideoData (tasks-vision.js:7860:10)
at O.detectForVideo (tasks-vision.js:7948:40)

Hello @endink, @baronha,
Thank you both for detailed observation. The white lines overlay looks like incorrect landmark connections list and incorrect landmark id's. Further, We are reassigning issue to right owner to understand more about the issue. Thank you

Hello @endink, @baronha, Thank you both for detailed observation. The white lines overlay looks like incorrect landmark connections list and incorrect landmark id's. Further, We are reassigning issue to right owner to understand more about the issue. Thank you

Many thanks for your assistance @kuaashish

Hello @endink, @baronha,
Thanks for looking into the newly provided face blendshapes solution!
The face blendshape graph is not ready to be used as production yet, and we will publish the document once it is ready.
Could you provide the whole graph you use in the legacy graph with face blendshape graph so that the we can take a look? Thanks!

@yichunk Hi, thanks for your reply, sorry for late.
Here is my graph:
node {
calculator: "ImageTransformationCalculator"
input_stream: "IMAGE:input_video"
output_stream: "IMAGE:transformed_image"
input_side_packet: "FLIP_HORIZONTALLY:input_horizontally_flipped"
input_side_packet: "FLIP_VERTICALLY:input_vertically_flipped"
input_side_packet: "ROTATION_DEGREES:input_rotation"
}
node {
calculator: "ImagePropertiesCalculator"
input_stream: "IMAGE:transformed_image"
output_stream: "SIZE:__stream_0"
}
node {
calculator: "HolisticLandmarkCpu"
input_stream: "IMAGE:transformed_image"
output_stream: "FACE_LANDMARKS:face_landmarks"
output_stream: "LEFT_HAND_LANDMARKS:left_hand_landmarks"
output_stream: "POSE_DETECTION:pose_detection"
output_stream: "POSE_LANDMARKS:pose_landmarks"
output_stream: "POSE_ROI:pose_roi"
output_stream: "RIGHT_HAND_LANDMARKS:right_hand_landmarks"
output_stream: "SEGMENTATION_MASK:segmentation_mask_rotated"
output_stream: "WORLD_LANDMARKS:pose_world_landmarks"
input_side_packet: "ENABLE_SEGMENTATION:enable_segmentation"
input_side_packet: "MODEL_COMPLEXITY:model_complexity"
input_side_packet: "REFINE_FACE_LANDMARKS:refine_face_landmarks"
input_side_packet: "SMOOTH_LANDMARKS:smooth_landmarks"
input_side_packet: "SMOOTH_SEGMENTATION:smooth_segmentation"
input_side_packet: "USE_PREV_LANDMARKS:use_prev_landmarks"
}
node {
calculator: "SplitNormalizedLandmarkListCalculator"
input_stream: "face_landmarks"
output_stream: "__stream_1"
options {
[mediapipe.SplitVectorCalculatorOptions.ext] {
ranges {
begin: 33
end: 34
}
ranges {
begin: 133
end: 134
}
combine_outputs: true
}
}
}
node {
calculator: "SplitNormalizedLandmarkListCalculator"
input_stream: "face_landmarks"
output_stream: "__stream_2"
options {
[mediapipe.SplitVectorCalculatorOptions.ext] {
ranges {
begin: 362
end: 363
}
ranges {
begin: 263
end: 264
}
combine_outputs: true
}
}
}
node {
calculator: "IrisLandmarkLeftAndRightCpu"
input_stream: "IMAGE:transformed_image"
input_stream: "LEFT_EYE_BOUNDARY_LANDMARKS:__stream_1"
input_stream: "RIGHT_EYE_BOUNDARY_LANDMARKS:__stream_2"
output_stream: "LEFT_EYE_CONTOUR_LANDMARKS:left_eye_contour_landmarks"
output_stream: "LEFT_EYE_IRIS_LANDMARKS:left_iris_landmarks"
output_stream: "LEFT_EYE_ROI:left_eye_rect"
output_stream: "RIGHT_EYE_CONTOUR_LANDMARKS:right_eye_contour_landmarks"
output_stream: "RIGHT_EYE_IRIS_LANDMARKS:right_iris_landmarks"
output_stream: "RIGHT_EYE_ROI:right_eye_rect"
}
node {
calculator: "ConcatenateNormalizedLandmarkListCalculator"
input_stream: "left_eye_contour_landmarks"
input_stream: "right_eye_contour_landmarks"
output_stream: "eye_landmarks"
}
node {
calculator: "UpdateFaceLandmarksCalculator"
input_stream: "FACE_LANDMARKS:face_landmarks"
input_stream: "NEW_EYE_LANDMARKS:eye_landmarks"
output_stream: "UPDATED_FACE_LANDMARKS:updated_face_landmarks"
}
node {
calculator: "ConcatenateNormalizedLandmarkListCalculator"
input_stream: "updated_face_landmarks"
input_stream: "left_iris_landmarks"
input_stream: "right_iris_landmarks"
output_stream: "__stream_3"
}
node {
calculator: "SplitNormalizedLandmarkListCalculator"
input_stream: "__stream_3"
output_stream: "__stream_4"
options {
[mediapipe.SplitVectorCalculatorOptions.ext] {
ranges {
begin: 0
end: 1
}
ranges {
begin: 1
end: 2
}
ranges {
begin: 4
end: 5
}
ranges {
begin: 5
end: 6
}
ranges {
begin: 6
end: 7
}
ranges {
begin: 7
end: 8
}
ranges {
begin: 8
end: 9
}
ranges {
begin: 10
end: 11
}
ranges {
begin: 13
end: 14
}
ranges {
begin: 14
end: 15
}
ranges {
begin: 17
end: 18
}
ranges {
begin: 21
end: 22
}
ranges {
begin: 33
end: 34
}
ranges {
begin: 37
end: 38
}
ranges {
begin: 39
end: 40
}
ranges {
begin: 40
end: 41
}
ranges {
begin: 46
end: 47
}
ranges {
begin: 52
end: 53
}
ranges {
begin: 53
end: 54
}
ranges {
begin: 54
end: 55
}
ranges {
begin: 55
end: 56
}
ranges {
begin: 58
end: 59
}
ranges {
begin: 61
end: 62
}
ranges {
begin: 63
end: 64
}
ranges {
begin: 65
end: 66
}
ranges {
begin: 66
end: 67
}
ranges {
begin: 67
end: 68
}
ranges {
begin: 70
end: 71
}
ranges {
begin: 78
end: 79
}
ranges {
begin: 80
end: 81
}
ranges {
begin: 81
end: 82
}
ranges {
begin: 82
end: 83
}
ranges {
begin: 84
end: 85
}
ranges {
begin: 87
end: 88
}
ranges {
begin: 88
end: 89
}
ranges {
begin: 91
end: 92
}
ranges {
begin: 93
end: 94
}
ranges {
begin: 95
end: 96
}
ranges {
begin: 103
end: 104
}
ranges {
begin: 105
end: 106
}
ranges {
begin: 107
end: 108
}
ranges {
begin: 109
end: 110
}
ranges {
begin: 127
end: 128
}
ranges {
begin: 132
end: 133
}
ranges {
begin: 133
end: 134
}
ranges {
begin: 136
end: 137
}
ranges {
begin: 144
end: 145
}
ranges {
begin: 145
end: 146
}
ranges {
begin: 146
end: 147
}
ranges {
begin: 148
end: 149
}
ranges {
begin: 149
end: 150
}
ranges {
begin: 150
end: 151
}
ranges {
begin: 152
end: 153
}
ranges {
begin: 153
end: 154
}
ranges {
begin: 154
end: 155
}
ranges {
begin: 155
end: 156
}
ranges {
begin: 157
end: 158
}
ranges {
begin: 158
end: 159
}
ranges {
begin: 159
end: 160
}
ranges {
begin: 160
end: 161
}
ranges {
begin: 161
end: 162
}
ranges {
begin: 162
end: 163
}
ranges {
begin: 163
end: 164
}
ranges {
begin: 168
end: 169
}
ranges {
begin: 172
end: 173
}
ranges {
begin: 173
end: 174
}
ranges {
begin: 176
end: 177
}
ranges {
begin: 178
end: 179
}
ranges {
begin: 181
end: 182
}
ranges {
begin: 185
end: 186
}
ranges {
begin: 191
end: 192
}
ranges {
begin: 195
end: 196
}
ranges {
begin: 197
end: 198
}
ranges {
begin: 234
end: 235
}
ranges {
begin: 246
end: 247
}
ranges {
begin: 249
end: 250
}
ranges {
begin: 251
end: 252
}
ranges {
begin: 263
end: 264
}
ranges {
begin: 267
end: 268
}
ranges {
begin: 269
end: 270
}
ranges {
begin: 270
end: 271
}
ranges {
begin: 276
end: 277
}
ranges {
begin: 282
end: 283
}
ranges {
begin: 283
end: 284
}
ranges {
begin: 284
end: 285
}
ranges {
begin: 285
end: 286
}
ranges {
begin: 288
end: 289
}
ranges {
begin: 291
end: 292
}
ranges {
begin: 293
end: 294
}
ranges {
begin: 295
end: 296
}
ranges {
begin: 296
end: 297
}
ranges {
begin: 297
end: 298
}
ranges {
begin: 300
end: 301
}
ranges {
begin: 308
end: 309
}
ranges {
begin: 310
end: 311
}
ranges {
begin: 311
end: 312
}
ranges {
begin: 312
end: 313
}
ranges {
begin: 314
end: 315
}
ranges {
begin: 317
end: 318
}
ranges {
begin: 318
end: 319
}
ranges {
begin: 321
end: 322
}
ranges {
begin: 323
end: 324
}
ranges {
begin: 324
end: 325
}
ranges {
begin: 332
end: 333
}
ranges {
begin: 334
end: 335
}
ranges {
begin: 336
end: 337
}
ranges {
begin: 338
end: 339
}
ranges {
begin: 356
end: 357
}
ranges {
begin: 361
end: 362
}
ranges {
begin: 362
end: 363
}
ranges {
begin: 365
end: 366
}
ranges {
begin: 373
end: 374
}
ranges {
begin: 374
end: 375
}
ranges {
begin: 375
end: 376
}
ranges {
begin: 377
end: 378
}
ranges {
begin: 378
end: 379
}
ranges {
begin: 379
end: 380
}
ranges {
begin: 380
end: 381
}
ranges {
begin: 381
end: 382
}
ranges {
begin: 382
end: 383
}
ranges {
begin: 384
end: 385
}
ranges {
begin: 385
end: 386
}
ranges {
begin: 386
end: 387
}
ranges {
begin: 387
end: 388
}
ranges {
begin: 388
end: 389
}
ranges {
begin: 389
end: 390
}
ranges {
begin: 390
end: 391
}
ranges {
begin: 397
end: 398
}
ranges {
begin: 398
end: 399
}
ranges {
begin: 400
end: 401
}
ranges {
begin: 402
end: 403
}
ranges {
begin: 405
end: 406
}
ranges {
begin: 409
end: 410
}
ranges {
begin: 415
end: 416
}
ranges {
begin: 454
end: 455
}
ranges {
begin: 466
end: 467
}
ranges {
begin: 468
end: 469
}
ranges {
begin: 469
end: 470
}
ranges {
begin: 470
end: 471
}
ranges {
begin: 471
end: 472
}
ranges {
begin: 472
end: 473
}
ranges {
begin: 473
end: 474
}
ranges {
begin: 474
end: 475
}
ranges {
begin: 475
end: 476
}
ranges {
begin: 476
end: 477
}
ranges {
begin: 477
end: 478
}
combine_outputs: true
}
}
}
node {
calculator: "LandmarksToTensorCalculator"
input_stream: "IMAGE_SIZE:__stream_0"
input_stream: "NORM_LANDMARKS:__stream_4"
output_stream: "TENSORS:face_tensor_in"
options {
[mediapipe.LandmarksToTensorCalculatorOptions.ext] {
attributes: X
attributes: Y
flatten: false
}
}
}
node {
calculator: "InferenceCalculatorCpu"
input_stream: "TENSORS:face_tensor_in"
output_stream: "TENSORS:face_tensor_out"
options {
[mediapipe.InferenceCalculatorOptions.ext] {
model_path: "./mediapipe/modules/face_landmark/face_blendshapes.tflite"
}
}
}
node {
calculator: "SplitTensorVectorCalculator"
input_stream: "face_tensor_out"
output_stream: "__stream_5"
options {
[mediapipe.SplitVectorCalculatorOptions.ext] {
ranges {
begin: 0
end: 1
}
combine_outputs: true
}
}
}
node {
calculator: "TensorsToClassificationCalculator"
input_stream: "TENSORS:__stream_5"
output_stream: "CLASSIFICATIONS:face_blendshapes"
options {
[mediapipe.TensorsToClassificationCalculatorOptions.ext] {
min_score_threshold: -1
top_k: 0
label_map {
entries {
id: 0
label: "_neutral"
}
entries {
id: 1
label: "browDownLeft"
}
entries {
id: 2
label: "browDownRight"
}
entries {
id: 3
label: "browInnerUp"
}
entries {
id: 4
label: "browOuterUpLeft"
}
entries {
id: 5
label: "browOuterUpRight"
}
entries {
id: 6
label: "cheekPuff"
}
entries {
id: 7
label: "cheekSquintLeft"
}
entries {
id: 8
label: "cheekSquintRight"
}
entries {
id: 9
label: "eyeBlinkLeft"
}
entries {
id: 10
label: "eyeBlinkRight"
}
entries {
id: 11
label: "eyeLookDownLeft"
}
entries {
id: 12
label: "eyeLookDownRight"
}
entries {
id: 13
label: "eyeLookInLeft"
}
entries {
id: 14
label: "eyeLookInRight"
}
entries {
id: 15
label: "eyeLookOutLeft"
}
entries {
id: 16
label: "eyeLookOutRight"
}
entries {
id: 17
label: "eyeLookUpLeft"
}
entries {
id: 18
label: "eyeLookUpRight"
}
entries {
id: 19
label: "eyeSquintLeft"
}
entries {
id: 20
label: "eyeSquintRight"
}
entries {
id: 21
label: "eyeWideLeft"
}
entries {
id: 22
label: "eyeWideRight"
}
entries {
id: 23
label: "jawForward"
}
entries {
id: 24
label: "jawLeft"
}
entries {
id: 25
label: "jawOpen"
}
entries {
id: 26
label: "jawRight"
}
entries {
id: 27
label: "mouthClose"
}
entries {
id: 28
label: "mouthDimpleLeft"
}
entries {
id: 29
label: "mouthDimpleRight"
}
entries {
id: 30
label: "mouthFrownLeft"
}
entries {
id: 31
label: "mouthFrownRight"
}
entries {
id: 32
label: "mouthFunnel"
}
entries {
id: 33
label: "mouthLeft"
}
entries {
id: 34
label: "mouthLowerDownLeft"
}
entries {
id: 35
label: "mouthLowerDownRight"
}
entries {
id: 36
label: "mouthPressLeft"
}
entries {
id: 37
label: "mouthPressRight"
}
entries {
id: 38
label: "mouthPucker"
}
entries {
id: 39
label: "mouthRight"
}
entries {
id: 40
label: "mouthRollLower"
}
entries {
id: 41
label: "mouthRollUpper"
}
entries {
id: 42
label: "mouthShrugLower"
}
entries {
id: 43
label: "mouthShrugUpper"
}
entries {
id: 44
label: "mouthSmileLeft"
}
entries {
id: 45
label: "mouthSmileRight"
}
entries {
id: 46
label: "mouthStretchLeft"
}
entries {
id: 47
label: "mouthStretchRight"
}
entries {
id: 48
label: "mouthUpperUpLeft"
}
entries {
id: 49
label: "mouthUpperUpRight"
}
entries {
id: 50
label: "noseSneerLeft"
}
entries {
id: 51
label: "noseSneerRight"
}
}
}
}
}
node {
calculator: "HolisticTrackingToRenderData"
input_stream: "FACE_LANDMARKS:face_landmarks"
input_stream: "IMAGE_SIZE:__stream_0"
input_stream: "LEFT_HAND_LANDMARKS:left_hand_landmarks"
input_stream: "POSE_LANDMARKS:pose_landmarks"
input_stream: "POSE_ROI:pose_roi"
input_stream: "RIGHT_HAND_LANDMARKS:right_hand_landmarks"
output_stream: "RENDER_DATA_VECTOR:__stream_6"
}
node {
calculator: "AnnotationOverlayCalculator"
input_stream: "IMAGE:transformed_image"
input_stream: "VECTOR:__stream_6"
output_stream: "IMAGE:output_video"
}

It has to be said that most of the BlendShapes work well, and the problems mainly appear in the eyes. My program calibrated bs before running mediapipe.

When the eyes are half-closed, the eyeball will move closer to the center ( eyeLookInRight, eyeLookInLeft have unreasonable values),
The right eye is a little "small".

@endink hi mate, sorry I am a bit new to creating my own graphs etc, I am writing a new updated plugin for feeding iOS FaceMesh landmarks in Unity from one I did a while ago, the update being the new data that can now come through, i.e the transformation matrix and blendshapes. I was wondering how I would take what you have done there and adapt it to work with one of the standard iOS example solutions?

@creativewax Hi，I think you'd better wait google, I have done legacy solution (in Unreal Engine), but its  not good enough. I also done new solution in Android, and push to unreal engine app, it's a little bit of an improvement over the legacy solution, but it's still not good enough to drive a 3D avatar.

@endink thank you, I have explained this to my client, but they want to push ahead with the update anyway, I started putting together a new legacy graph last night, but I have not looked at the supporting bits around that. That is the main thin I was unsure about looking at the graph you put above, what is the corresponding code around it. Does the Classification BS just get passed through?

@creativewax You can use my graph above, but you need dowload face_blendshapes.tflite file. BS is in ClassificationList. Label is bs name , value is bs weight (0-1) ,I saw google release a new version for mediapipe(0.9.3), I have not try it. A google developer let me try on another issue. I think you can try it  , use C++ task api is a better choise(task api is not worked 0.9.2).

@endink cool, ill take a look, basically all I want to do is use the same Face Mesh solution and pull the BS data into it, so atm I am unsure where to reference the face_blendshapes.tflite atm, but I saw that in the graph, so ill dig a bit deeper. I am guessing the ClassificationList. Label is exposed into the legacy FaceMesh solution?

@endink yup, I told my client about it not being production ready and they was still really keen on getting it in, no idea why

Just use my graph, and observe/poll "face_blendshapes" stream. 😄

If you want to know how mediapipe bs actually works, I recorded a video on my youtube channel: https://youtube.com/playlist?list=PL1Bnbwb6xrM-WhM0XgK6mSMpkTL73kmln

@endink nice, ill take a look :)

@yichunk Why C++ was abandoned？

It is not abandoned. There is C++ API for mediapipe Tasks https://github.com/google/mediapipe/blob/master/mediapipe/tasks/cc/vision/face_landmarker/face_landmarker.h
You can still mediapipe graph to build your own pipeline.

@yichunk
Thanks for the reply！
Won't there be C++ documentation and code examples in the future? Is it that C++ users can only get the usage method by reading the source code

@yichunk
Could you provide C++documentation or code examples? Thank s!

@yichunk
Could you provide C++documentation or code examples?  Thanks!

I need C++ documentation and code examples, too.

@creativewax Hi，I think you'd better wait google, I have done legacy solution (in Unreal Engine), but its not good enough. I also done new solution in Android, and push to unreal engine app, it's a little bit of an improvement over the legacy solution, but it's still not good enough to drive a 3D avatar.

@yichunk facing same performance issue on even high end android devices! Is there any workaround or it's just a dead end?

Is anyone able to crack this one?

@emphaticaditya i have it working on iOS and Android now. I can post my graph and solution later when I am at my computer.

It seems that Google will no longer respond to this issue, and the only can do is mix the new TaskAPI, the old solution used to do Holistic, and the TaskAPI specifically handles Face.
One image send to two pipes. It is not much difference in performance. That's how I use it at this moment.

@endink @creativewax thanks for responding!!
I tried using blendshapes in android and it is extremely gittery and laggy. Even had worse performance than web version running on M1. Same code I ran on iPhone and got a much better response.
I am afraid if the only bottleneck is hardware?

I use android too, I got 30FPS (java sdk)

@emphaticaditya
it can be download :
https://github.com/endink/Mediapipe4u-plugin/releases/tag/M4U_Remoting_App

@creativewax Can you share the performance benchmarks? I am getting 30fps fixed with 33.8ms latency on android s10.
Can anyone comment on the same regarding the performance?
It would be helpful really!
Thanks

@creativewax Can you share the performance benchmarks? I am getting 30fps fixed with 33.8ms latency on android s10.
Can anyone comment on the same regarding the performance?
It would be helpful really!
Thanks

@emphaticaditya sorry for the delay, them benchmarks seem inline with what I got, and mine was piping into Unity as well, ran pretty well in the end after code optimisations etc

I also have an error in getting Unreal Blendshape calculator.
Currently, the following error occurs in the Unreal Output Log in the part of the pbtxt(endink's holistic pbtxt)in LandmarksToTensorCalculator calculator [LogMediaPipe:Error:; mediapipe::ParseTextProtomediapipe::CalculatorGraphConfig (config_str, &config)].
Changing the configuration inside the node of pbtxt causes a ParseTextProto error.
I need your help!


Define required headers in one place for all service methods

Description
Hi! The OpenAPI spec I'm working with has a required header parameter (SomeHeader) for certain methods. See below:
[/some/endpoint/get:]
operationId: SomeOperation
parameters:
 - name: SomeHeader
   in: header
   required: true

I am using this library to generate types/methods that will be used for an API wrapper SDK. This SDK will consist only of the methods that require the SomeHeader header. Since every single method in this API is going to use SomeHeader, it'd be great if I could define this in just one place, such as in the client config. However, because the header parameter is required in the OpenAPI spec, each generated service method requires the header in its input:
// generated input type for SomeOperation
export type SomeOperationData = {
    headers: {
        'SomeHeader': string;  // this is required
    };
    ...
};

This means that despite setting the header in the client config, each service method still require me to pass in the header. Is there any way I can avoid having to pass in the header for every single method?
// ideally I can just define this here and avoid passing the header in every single method call
client.setConfig({
      ...,
      headers: {
        "SomeHeader": "some-value",
      },
});

This works perfectly if the header is optional, but because it's required in the OpenAPI spec, the generated input type also requires it. I'd really appreciate if I could achieve this without making the header optional in the OpenAPI spec.

@SpiffyJif to clarify, the proposed approach you have works, but TypeScript will complain, correct? At which point, this becomes a TypeScript issue rather than a new feature. If that's true, there are two possible approaches – either provide a mechanism to alter the generated types (without modifying your OpenAPI spec) or improve TypeScript interfaces. My general take would be to attempt to do the latter, I am just not sure how doable it is. I can't find that discussion now, but other people requested this too in relation to throwOnError. The underlying problem is the same, the code works, but TypeScript does not know that.

Looks the same here:
https://github.com/hey-api/openapi-ts/issues/1020

@SpiffyJif did you come up with some workaround for this?


Feature/25176 bitbucket readme

Summary

This PR organizes README.md, admin-guide.md and project assets in a way described here https://github.com/mattermost/mattermost/issues/25176
I have

reorganized files (admin guide split to separate file, assets moved to docs/images)
updated files that use images (new directory)
added outline to both .md files
added missing headlines
formatted files
added badges to README (however, I don't have access to any code coverage report so it's empty for now)

Ticket Link

Fixes https://github.com/mattermost/mattermost/issues/25176
https://mattermost.atlassian.net/browse/MM-55077

Hello @kat-kan,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla

@mickmister - Looking forward to your technical review of this PR -- particularly the image updates.

I am also looking forward to the review :)

@kat-kan - You've done a very good job with this PR. Thank you for being so flexible and understanding about the feedback you received during @hanzei's technical review.
@hanzei - Thank you for a most excellent review! :)

@hanzei - I believe the only check remaining is to ensure that the image assets are in the correct location.

@cwarnermm I believe they are but builds are failing after moving images because they expect specific location. I am waiting for confirmation that I should revert changes.

I reverted the changes related to images.

@cwarnermm as we are still waiting for @hanzei to accept the changes, can you please consider adding "hacktoberfest-accepted" label? The review period in Hacktoberfest ends tomorrow and PR has to be either merged or have the label to be even considered.

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

Comparison is base (84a4030) 15.03% compared to head (29bf6d4) 15.03%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #125   +/-   ##
=======================================
  Coverage   15.03%   15.03%
=======================================
  Files          13       13
  Lines        2301     2301
=======================================
  Hits          346      346
  Misses       1936     1936
  Partials       19       19

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

@mickmister The broken CI is unrelated to the PR. What are the next steps to getting it fixed?

@hanzei I created https://github.com/mattermost/mattermost-plugin-bitbucket/pull/127 to fix the issue

/update-branch

@mickmister - Looking forward to your technical review of this PR -- particularly the image updates.

@cwarnermm I'm not sure there are any image updates in the PR?

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!


Migrate pkg/controller logs to structured logging

Migrate  some logs  of pkg/controller to structured logging

/retest

Closing due to inactivity. Feel free to reopen if needed.


add challenge 'zoo-animals'

js-array-methods-2/zoo-animals
📄 Rendered Exercise
🔎 Review
Review via 🔗 CodeSandbox or locally by running this command in your Terminal:
npx ghcd@latest neuefische/web-exercises/tree/js-array-methods-2_zoo-animals/sessions/js-array-methods-2/zoo-animals -i

✨ Copyable Markdown for Curriculum
Solve this challenge on
[🔗 **CodeSandbox**](https://codesandbox.io/s/github/neuefische/web-exercises/tree/main/sessions/js-array-methods-2/zoo-animals?file=/README.md)
or locally by running this command in your Terminal:

```
npx ghcd@latest neuefische/web-exercises/tree/main/sessions/js-array-methods-2/zoo-animals -i
```

I applied some changes. Please have a look.


Refactor and fixes multigpu support

Refactor the multigpu and cuda context stack management (in numba.cuda.cudadrv.devices)

enforces one context per device per process rule as introduced in CUDA 4.0 Runtime API
all cuda users (including tests) must use this to create context

Fixes context leaking problems on python2.7 and python3.3
Fixes exception leaking in threads (numba/cuda/tests/cudadrv/test_reset_device.py)
All cuda tests must use the new cuda context management

The following:
from numba import cuda
len(cuda.gpus)

results in:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/gmarkall/work/numba/numba/cuda/cudadrv/devices.py", line 44, in __len__
    return len(self.lst)

should this be expected to work?

Something I've observed related to push_context always pushing - if I run the following after a context for a GPU is already created:
with cuda.gpus[0]:
    with cuda.gpus[0]:
        pass

Then during execution, there are three contexts on the stack:
[<CUDA context c_void_p(28950752) of device 0>,
 <CUDA context c_void_p(28950752) of device 0>,
 <CUDA context c_void_p(28950752) of device 0>]

It seems to me to be desirable to be able to have nested contexts in this way, since I wouldn't necessarily want to bother making sure I always avoided nesting contexts in a large program. Therefore, I think push_context just has an inaccurate docstring "Push a context for the given GPU if it is not the current context") rather than the implementation being incorrect - furthermore, I expect it would cause problems in pop_context if push_context did not always push a context when called.
I've not yet spotted a case where I think this behaviour is actually going to be a problem - do you agree with this?

Then during execution, there are three contexts on the stack:

Just to clarify - I mean the same context is pushed three times.

@gmarkall, It is expected to always push a context to the context stack even if it is the currently active context.  The behavior (pushing the same context 3 times) is expected in your code snippet.

and, @gmarkall, thanks for reviewing!


[Swift 3] print __attribute__((noescape)) in generated Obj-C headers

Explanation
Cherry-picks my change to print __attribute__((noescape)) in generated Obj-C headers from #4438 (reviewed by @jrose-apple).
Specifically, introduces a macro SWIFT_NOESCAPE to the generated header which expands to __attribute__((noescape)) when available.
Also grabbing a NFC commit from @slavapestov that was necessary to make the cherry-picking conflict-free.
Note: there are still some remaining issues that make this feature less-than-"perfect"/"complete". I filed follow-up issues for these when I discovered them along the way:
https://bugs.swift.org/browse/SR-2520 "Type alias is lost when applying @escaping-ness"
https://bugs.swift.org/browse/SR-2529 "Keep __attribute__((noescape)) when importing Clang types"
However, I believe there's no harm in including this change in Swift 3: some support for the noescape attribute is better than none.
Scope
Affects only PrintAsObjC.
SR issue
https://bugs.swift.org/browse/SR-2406 "Print __attribute__((noescape)) in the generated header"
Risk
Affects only generated Obj-C headers.
Possible failure modes would be:

Including SWIFT_NOESCAPE in places where it shouldn't be.
Not including SWIFT_NOESCAPE in places where it should be.
Producing a header that is not valid Obj-C.

Note that 2. was already happening, because SWIFT_NOESCAPE wasn't being printed.
The risk for 1. is low, because to my knowledge clang doesn't actually take this attribute into account when compiling (Obj-)C(++) code.
All 3 are tested by the additional tests that were added.
Testing
Added tests to PrintAsObjC/blocks.swift; added PrintAsObjC/imported-block-typedefs.swift; updated other tests as necessary.

@swift-ci please test

Please add the template from the Swift 3.0 process.

Oops, I wasn't aware of that template. Thanks.

@jtbandes I feel confident pulling in this change.


Comment the armhf version of alpine + clean image

Fix the issue with the URL that was not updated for the alpine-dig.
Add cleaning to the image


Static files (robots.txt,...) error : PermanentRedirect

<Error>
PermanentRedirect
<Message>
The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
</Message>
<Endpoint>assets.cuistotducoin.com.s3.amazonaws.com</Endpoint>
<Bucket>assets.cuistotducoin.com</Bucket>
<RequestId>70179CC3BDA875DE</RequestId>
<HostId>
mZi2KGHgQ/Y+yicPFNcnTf+bt7PyxV2Tk0k6jv0iP38CCzIECxhPSoRXwuBYHrF8A1XZuI4bZPs=
</HostId>
</Error>

My serverless.yml config :
custom:
  sentry:
    dsn: ${env:SENTRY_DSN}
    organization: cuistotducoin
    project: front
  serverless-nextjs:
    assetsBucketName: assets.cuistotducoin.com
    staticDir: ./static
    routes:
      - src: ./static/robots.txt
        path: robots.txt
      - src: ./static/browserconfig.xml
        path: browserconfig.xml
      - src: ./static/manifest.json
        path: manifest.json

Full project : https://github.com/CuistotduCoin/front
Did I missed some rights ? Should I "reset" the stack ?

You shouldn't need to reset the stack, there aren't any breaking changes AFAIK.
I think this is a bug. I suspect its got to do with the region the bucket was created at. Currently the api gw -> s3 proxy forwards to
https://s3.amazonaws.com/{bucketName}/{path};

Which I think will only work for US East (N. Virginia). For other regions you have to specify the region it in the URL as per https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html

Can you try using 2.0.2-alpha.0? Just pushed a fix that I think will solve this.

👍 , it's working like a charm


What is 'show me' in admin panel?

What is 'show me' and how it works in admin panel? (/vanity)

The link should be constructed so that clicking on it shows the alternative.
https://github.com/assaf/vanity/blob/a87dcccbdebb95897602194170df3e24c2e2bc7f/lib/vanity/templates/_ab_test.erb#L30-L31
How do you think we could make it more clear?

I think that it will be more clear(most understandable), if you will remove this links from view.


Improve public liked songs playlist load time

Feature Request
The loading time for creating a public liked song playlist should be shorter.
Instead of adding all the songs to the playlist and then returning the playlist id, all the songs could be added after returning the created playlist. This may result in adding songs as the user views the playlist, but that's better than such a lengthy load time.

This can be achieved by splitting the create call into two calls, create and populate.


DOC: fix documentation of som EVP_MD_CTX functions

They were documented to take an EVP_MD pointer, when they really take
an EVP_MD_CTX pointer.
Fixes #9993

Merged.
7c2a981ff7ca721a85687dcd972d54361434806f DOC: fix documentation of som EVP_MD_CTX functions


New Pypi release

There is a big performance issue on the current version "0.5" with the related fields (FK or o2o), SQL queries count (Using Debug toolbar) can be from 20 to 400 and even more with this update (from "0.3" to "0.5")
This is not the case when installing directly from git.
Thanks

Hi @MounirMesselmeni !
The new release (0.6) will be deployed soon (few days) to fix that.
Thanks for reporting.

Thank you very much :+1:

0.6 released !


"Add a Host" link has the wrong URI shortly after environment creation

Rancher Versions:
Server: 1.3.1
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker Version:
1.1.12
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 14.04, private cloud
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA Rancher, external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Create new Environment
Immediately click on the environment name
Click "Add a Host"

Results:
The link in "Add a host" contains an "undefined" environment, ie:
https://server/env/undefined/infra/hosts/add
Wait about 10 seconds for the environment to get an envid, go back into the Environments tab, click "Add a Host" and the link will have the correct environment ID

@sdlevi27 - this has been fixed and will be in the next release.  Verified in master, so I'm going close it and after our next release if you still see the issue, reopen and let me know.


Ignore CHP unavailability during multiple outages

Currently,  inconsistent with the deterministic single outage scenario which ignores CHP unavailability during the outage, the stochastic multiple outages was not ignoring CHP unavailability. This PR changes that to ignore CHP unavailability during the outages, while preserving the unavailability periods for the 8760 grid-tied operation. This allows consistency in the economic dispatch between non-outages and outages scenarios.

Github has queued the workflows/actions runner, but all tests pass locally for me so I'm going to merge.


Document ObjectProperties/patterns for use in TC plugin

Which OPs/patterns does the plugin work for?
This is a good opportunity to standardize across OBO

all instances of C must be in T: C SubClassOf in-taxon some T // no need for only-in-taxon if in-taxon is functional
no instances of C are in T: C SubClassOf in-taxon only not T
there exists some instance of C in T (currently only used in Uberon): keep as annotation assertion for now?

Will the PTC plugin would with 1 + 2?
Note for 2 we have historically used an AP. This will still be necessary if ontology maintained in .obo. But we can standardize to the most precise OWL for use with this tool

+1

Modification of the above, allowing for a canonical logical representation and a canonical shortcut

all instances of C must be in T:
a. Logical: C SubClassOf in-taxon some T // no need for only-in-taxon if in-taxon is functional
b. Shortcut: no need
no instances of C are in T:
a. Canonical logical representation: C SubClassOf in-taxon only not T
b. Alternative EL logical representation: C disjointWith in-taxon some T (depends on injecting GCIs into NCBITaxon)
c. Canonical Shortcut: AnnotationAssertion: C never-in-taxon T
there exists some instance of C in T
a. Canonical logical representation: [a C]  Type in-taxon some T
b. Canonical shortcut: C present-in-taxon T

Note: none of the above can be considered to be statements about evolutionary gain or loss
It's important for us in GO to be able to indicate

gain in ancestral node X
lost in ancestral node X

@thomaspd's proposal here:
https://docs.google.com/presentation/d/1Z3d8SBz-BWHPV5a9oaniPypZIYzV7VzBwVcleLdpk_c/edit#slide=id.p
This essentially adds a qualifier to a TC such that it can be declared GLOBAL strengthening the meaning

Only in = Gained at the specified branch in evolution
Never in = Lost at the specified branch in evolution

These could be represented by paired statements. cc @balhoff


[FLINK-6315] Notify on checkpoint timeout

https://issues.apache.org/jira/browse/FLINK-6315
A common use case when writing a custom operator that outputs data to some third party location to partially output on checkpoint and then commit on notifyCheckpointComplete. If that external system does not gracefully handle rollbacks (such as Amazon S3 not allowing consistent delete operations) then that data needs to be handled by the next checkpoint.
The idea is to add a new interface similar to CheckpointListener that provides a callback when the CheckpointCoordinator times out a checkpoint
This is required for the eventually consistent sink coming in FLINK-6306 to be able to differentiate between concurrent checkpoints and timed out checkpoints.

@aljoscha Could you review this or point me in the direction of the correct person? I need this to land for the EventualConsistencySink

I commented on the issue because we might need a general discussion about the feature first.


resolved issue #5

implemented filtering options for all/events/errors/cleared errors/active errors
a "session" is now identified as each time the DDM receives a BEGIN signal
program prompts for autosave whenever a "session" ends, or when the DDM or CSIM receives a CLOSING_CONNECTION signal (also clears linked lists here)
fixed CSIM bug not clearing dump messages when stopped / deleted
fixed bug where DDM was receiving disconnect message from CSIM despite not being connected

lgtm


Typo in 'workon' output

When calling git phlow workon #, there's a typo in the progress message that appears.
The spinner displays "Fetching form remote", this should be "Fetching from remote".
Relevant file:
https://github.com/Praqma/git-phlow/blob/e8525bce7773ec6559be15a4c9d4714e14c12c64/phlow/workon.go

I might have opened a duplcate issue #95 that I accidentially pushed a fix to.

I am closing the issue since it has been solved in #95 as @RandomSort said.


Fix uniques + some text cleanup

Updates to Unciv from 4.10 onward have deprecated several old uniques/conditionals, so those have been adjusted to the new correct ones. Also, fixing my own screw-up on the Opinionspeople in a previous PR (which was due to me not understanding what the new GP unique actually did).

Done.


added location info to popover

Issue https://github.com/fossasia/open-event-webapp/issues/565
It will add room info to popover,

Description, screenshot, related issue?

@championswimmer I am not sure why the build is failing. I am able to pass 100% test on my local.
Can you please help https://travis-ci.org/fossasia/open-event-webapp/builds/153345833


Dialogs are non-modal

When submitting pipelines, the resulting dialogs are non-modal. e.g. if you have a slow internet connection, you and click multiple times, a queue of the same dialogs builds up and you loose state where you actually are in the submission process

Just noticed this again - I was thinking the pipeline is still submitting but I had a network issue and only saw the "underlying" dialog once I've closed the previous one.
I suggest not waiting for an upstream fix in jupyterlab but moving those outputs to the status panel

Just noticed this again - I was thinking the pipeline is still submitting but I had a network issue and only saw the "underlying" dialog once I've closed the previous one.
I suggest not waiting for an upstream fix in jupyterlab but moving those outputs to the status panel

One problem with modal dialogs is that they prevent the user from doing anything else. In some scenarios this would be a major issue, e.g. when a pipeline is executed locally, which might take a long time.

One problem with modal dialogs is that they prevent the user from doing anything else. In some scenarios this would be a major issue, e.g. when a pipeline is executed locally, which might take a long time.

agree, that's why I suggested:

I suggest not waiting for an upstream fix in jupyterlab but moving those outputs to the status panel

Do you know if this is possible?

agree, that's why I suggested:

I suggest not waiting for an upstream fix in jupyterlab but moving those outputs to the status panel

Do you know if this is possible?

Duplicate of #1064


Updated readme.md file

Content changed to a CV based on my Linked In Profile:

added my profile photo
added About section
added Experience section
added Education section
added Skills section
added Languages section

Content changed to a CV based on my Linked In Profile:
added my profile photo
added About section
added Experience section
added Education section
added Skills section
added Languages section

All changes have been made as suggested. Thank you

Please approve so that I can merge the branch

@Laura-Novich-OBW ,
I don't have an option for merging this PR.


External Keyboard : First responder issue when switching between apps

Correct iOS 14, most up to date.
Just realized I left out critical information. I’m using the apple magic keyboard. Just tested it now without using the keyboard and it works just fine. So this is something to do with the apple keyboard.
I just tested the following:

Keyboard connected, fired up WebSSH, connected to my machine.
Keyboard still connected, switched over to chrome
Keyboard still connected, switched back to WebSSH - No input works as stated before
pulled my ipad off the keyboard. On screen keyboard works just fine
Put ipad back on the magic keyboard, everything works.

Very interesting. Anything else you want me to try? I really like this product and would like to help out in any way.
Originally posted by @rkratochvil in https://github.com/isontheline/pro.webssh.net/discussions/408#discussioncomment-1351297

@rkratochvil Good to hear that iOS 15 solves your issue.
Reopen this issue at any time if the trouble occurs again.
Have a nice day ☀


bugfix: when pgsql multi schema then channel not found

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

fixes: #3591
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #3879 (447034f) into develop (0f92415) will decrease coverage by 0.08%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             develop    #3879      +/-   ##
=============================================
- Coverage      40.71%   40.63%   -0.09%
  Complexity      3042     3042
=============================================
  Files            679      679
  Lines          22779    22755      -24
  Branches        2841     2793      -48
=============================================
- Hits            9275     9247      -28
+ Misses         12634    12613      -21
- Partials         870      895      +25

Impacted Files
Coverage Δ

...n/java/io/seata/rm/datasource/DataSourceProxy.java
45.45% <0.00%> (-1.43%)
:arrow_down:

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
:arrow_down:

...otobuf/convertor/BranchReportRequestConvertor.java
90.90% <0.00%> (-9.10%)
:arrow_down:

...obuf/convertor/BranchRollbackRequestConvertor.java
92.00% <0.00%> (-8.00%)
:arrow_down:

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
:arrow_down:

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

...obuf/convertor/GlobalRollbackRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

...protobuf/convertor/RegisterTMRequestConvertor.java
94.73% <0.00%> (-5.27%)
:arrow_down:

...protobuf/convertor/RegisterRMRequestConvertor.java
90.47% <0.00%> (-4.77%)
:arrow_down:

... and 27 more

LGTM

LGTM


Automatic file watching not working on linux

Hi, my Git tab does not auto-update and I always have to click refresh.
Additionally, the left margin does not have highlighting of the changes (to allow me to see the difference between the working copy and the committed file when I click on it), unlike in Windows.
I have tried uninstalling (with purge) and reinstalling code, and also deleting the ~/.vscode folder, to no avail. I have also increased my file watcher limit to the maximum allowed by the system (about 524,000) and it doesn't help.

@bpasero What info can the user provide further?

@siauderman if you run code --verbose and watch development tools console, there should be file watching related output that would be helpful.

Based on the output of code --verbose, the file watching seems to be working. However, the git tab doesn't update unless i click the refresh button and there's still no way of seeing the past changes by clicking the left margin as on Windows (I just updated to the latest version).
[15180:1108/095315.874250:INFO:CONSOLE(1742)] "%cTRACE color: #888 [text file model] save() - enter file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.875481:INFO:CONSOLE(1742)] "%cTRACE color: #888 [text file model] doSave(7) - enter with versionId 7 file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.888137:INFO:CONSOLE(1742)] "%cTRACE color: #888 [text file model] doSave(7) - before write() file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.898570:INFO:CONSOLE(1742)] "%cTRACE color: #888 [text file model] handleSaveSuccess(7) - setting dirty to false because versionId did not change file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.898899:INFO:CONSOLE(1742)] "%cTRACE color: #888 [backup tracker] discarding backup file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.903178:INFO:CONSOLE(1742)] "%cTRACE color: #888 [text file model] save() - exit file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.909658:INFO:CONSOLE(1742)] "%cTRACE color: #888 [File Watcher (chokidar)] [CHANGED] /home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.916263:INFO:CONSOLE(1742)] "%cTRACE color: #888 CommandService#executeCommand setContext", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.952258:INFO:CONSOLE(1742)] "%cTRACE color: #888 [text file model] load() - enter file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.952404:INFO:CONSOLE(1742)] "%cTRACE color: #888 [text file model] loadFromFile() file:///home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)
[15180:1108/095315.954697:INFO:CONSOLE(1742)] "%cTRACE color: #888 [File Watcher (chokidar)]  >> normalized  [CHANGED] /home/walfin/Dokumentujo/Bitbucket/sendall/src/css/app.styl", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (1742)

Also, git autorefresh is enabled in settings.

@siauderman yes, the output [File Watcher (chokidar)] is the relevant one for file events. So you say you see output for the file in question in the logs but the git view does not update to show the change as outgoing?

Yes, the git view does not update and I also cannot see the red/blue thing in the left margin to show deleted / modified lines.

Sounds more like a git issue to me then.

Is your repository in a network share? In a symlink?

No.
The strange thing is that even after I refresh the git pane, the red/blue indicator in the left margin which I can click on to see the change still doesn't appear on linux. It works perfectly fine on windows.
I don't know if something is wonky in my settings. Is there a way to reset all my settings? I had uninstalled and reinstalled but that didn't reset my settings.

You can try with a new settings folder just to confirm that would be the case by running code --user-data-dir NEWFOLDER

You can try with a new settings folder just to confirm that would be the case by running code --user-data-dir NEWFOLDER

Just tried it. Didn't work.
I have found the problem, it's because I was opening the folder through a symlink. When I open it without going through the symlink, it works.
Is there any way to make the file watching work even when the folder is opened through a symlink?

#5970


Code has a few errors

Hello Hao,
Your paper is really interesting! Could you please consider running your code again and then upload it? In its current state, the results are not reproducible. Even the names of the files are not correct.
Thank you in advance.
Aristotelis-Angelos Papadopoulos

Hi Aristotelis! thank you a lot for bringing up this issue! sorry for that I didn't manage to conduct a test run after cleaning up my messy codes! I just fixed the errors, now it should reflect what I did in the paper :)
I'll run some complete tests to further verify it and release the pertained model, will let you know!
Feel free to email me at<EMAIL_ADDRESS>or reopen the issue if you have further questions. Take care!!


Use container based infrastructure on Travis.

As containers are taking over the world, this needs no explanation.
http://docs.travis-ci.com/user/workers/container-based-infrastructure/

..yepp, Travis works now :dancers:


Issue with steam streaming (skip launcher?)

Is there any launch parameter we can use to skip the launcher and go straight into the game?
the launcher has issues with steam link streaming but if the game launched directly it would work flawlessly, anyway to do this?

ignore me, after posting this found that /launch works as a parameter ^^;


Release ES Groovy 2.2.0

I am currently unable to run my tests within Gradle without disabling the security manager.
gradle clean test -Dtests.security.manager=false

Until I can, then I am very hesitant to release v2.2.0. This actually appears to be a bug in Gradle itself with how it handles the security manager related specifically to Groovy tests. I'm hoping to see this fixed in the upcoming Gradle 2.12 release. If that happens, then ES Groovy 2.2 (and later) will require that release or later.
The Elasticsearch project has switched to using Gradle for ES 3.x (currently the master branch of both projects), and they bypass this issue by using their own customer Gradle runner. For ES Groovy 3.x, I plan to switch to that approach, but I cannot use it for 2.x builds (without a clone-and-own version, which I'd rather not support).

Hi, gradle 2.12 is released. Do you have any news ?

Tried to build it here with gradle 2.12, branch 2.2 (commit 2ea9a2e)
Test are freezing without security manager option :
Gradle Test Executor 2 started executing tests.

org.elasticsearch.groovy.action.ListenableActionFutureExtensionsTests STANDARD_OUT
    [2016-03-22 23:43:15,444][WARN ][bootstrap                ] JNA not found. native methods will be disabled.
    java.lang.ClassNotFoundException: com.sun.jna.Native
    	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
    	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
    	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    	at java.lang.Class.forName0(Native Method)
    	at java.lang.Class.forName(Class.java:264)
    	at org.elasticsearch.bootstrap.Natives.<clinit>(Natives.java:45)
    	at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:89)
    	at org.elasticsearch.bootstrap.BootstrapForTesting.<clinit>(BootstrapForTesting.java:85)
    	at org.elasticsearch.test.ESTestCase.<clinit>(ESTestCase.java:99)
    	at java.lang.Class.forName0(Native Method)
    	at java.lang.Class.forName(Class.java:348)
    	at com.carrotsearch.randomizedtesting.RandomizedRunner$2.run(RandomizedRunner.java:585)
    [2016-03-22 23:43:15,447][WARN ][bootstrap                ] cannot check if running as root because JNA is not available
    [2016-03-22 23:43:15,448][WARN ][bootstrap                ] cannot install syscall filters because JNA is not available
    [2016-03-22 23:43:15,448][WARN ][bootstrap                ] cannot mlockall because JNA is not available
    [2016-03-22 23:43:15,448][WARN ][bootstrap                ] cannot register console handler because JNA is not available
> Building 50% > :test^C%

With the security manager option, 151 tests completed, 15 failed.

Hi Yann, I think it's time to make the shift and rewrite the Gradle build to reuse Elasticsearch's build code. I was hoping to avoid that until ES 5.0 came out, but I think it's time to bite the bullet.

Wow, that's a quick feedback :)
I understand that's not the happy path.... But there is hope you won't need to touch it while owning it.
Can we expect a release soon ?

I'll try to get to that within the next week.

As a side note to this issue. ES Groovy 2.1.x is compatible with ES 2.3. It's just that the builds are not working due to the security manager and time to rewrite it has been sparse.

All, this has proven not worth the technical effort to attempt to rewrite the Gradle build for the 2.2, 2.3, and 2.4 branches. As a result, I have no plans to release these builds. Now that the corresponding ES issue has been merged, I am making the necessary changes so that it works with 5.x in #21773.
As a reminder, v2.1.2 is compatible with ES 2.2 - 2.4 releases.


Google Bard

Would be great to be able to also use Google Bard.

Google Bard => Gemini
See also https://github.com/charmbracelet/mods/issues/176


Are match_kinds compile-time known?

This code fails to type check:
#include <core.p4>

match_kind { fuzzy }

T f<T>(T t) { return t; }

control c()() {
    apply {
        if(f(exact) == fuzzy) { }
    }
}

because match_kinds are not compile-time known values. However, this code does type check:
#include <core.p4>

match_kind { fuzzy }

T f<T>(T t) { return t; }

control c()() {
    apply {
        if(f(exact) == fuzzy) { }
    }
}

It is a silly example, but is this what we want?

I think that the first question to ask is whether match kinds are real types :)
I was just thinking where we can use them in practice and so far the only thing that came to mind was to use them as parameters in a control, e.g.:
control c(. . .)
         (match_kind t1_match_kind=exact)
{
    table t1 {
        key = { hdr.h.f1 : t1_match_kind; }
        actions = { . . . }
        size =
                    t1_match_kind == exact    ? 65536 :
                    t1_match_kind == ternary ? 1024    :
                    0;
    }
    apply {
         . . .
    }
}

The compiler stopped at the line (match_kind t1_match_kind=exact) with the message:
test.p4(140):syntax error, unexpected MATCH_KIND
    (match_kind
     ^^^^^^^^^^

Indeed, there sees to be no way to name the match_kind type. But in some cases you can let type inference fill it in...

Should we just treat match_kind and error by utilizing a big part of the mechanism for enum? As the Petr4 paper argued that "The match_kind and error types are “open enumerations,” comparable to the extensible exception type in Standard ML".

These types are very much like enums.

I am not sure, but perhaps this PR is related?  https://github.com/p4lang/p4-spec/pull/1020
Issue I filed recently with a different test program I was trying to make compile with at least p4test, but failed: https://github.com/p4lang/p4c/issues/3091
PR on p4c that is recently merged in (less than an hour ago as I write this comment) that Mihai wrote to fix that issue: https://github.com/p4lang/p4c/pull/3099
@vgurevich You might want to try compiling your test program above with the latest main version of p4c and see if the error message has changed, or maybe there might even not be any error message now?

I hope that we have now answered this question in the affirmative. Can we close this issue?


Add unit tests for slack integration

This SDK would require unit tests for slack integration with dialogflow.

Links to https://github.com/Sampriti-Mitra/dialogflow-slack-sdk/issues/36


Sqllab autocomplete for table should also add the schema name

When writing queries in SQLlab, after the relevant schema is selected in the left pane, table names get autocompleted. However if any other schema than "public" is chosen, the query will fail, because the schema name is not prefixed to the table name as part of auto completion - this defeats the purpose of autocomplete for tables names.
How to reproduce the bug

Go to Sqllab
Click on NewTab
Select the relevant schema on right, e.g. "myschema"
Write SqlQuery "select * from mytable" (use autocomplete on mytable)
See error "mytable not found"

Expected results
The table name should autocomplete with myschema.mytable - defeats the purpose of autocomplete otherwise
Actual results
Only the table name is autocompleted
Environment
(please complete the following information):

browser type and version: Chrome 120
superset version: 2.0.0
python version: Python 3.8.12
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

@betodealmeida @justinpark I was tempted to close this as stale, but I wanted to check with both of you first to see if this is indeed a bug that others just haven't complained about, or if something has since been updated.
@raags we no longer support 2.0... is this still happening in 3.1 or 4.0?

@rusackas I tested on 3.1 and it still happens - the bug is that the table autocomplete doesn't add the schema prefix, without which the query will fail.


Fix Product feature seed through more complete tests

We have several duplicated identifiers in the db/fixtures/miq_product_features.yml when they must be unique.  The seed method will create on the first instance and update on each subsequent instance and the last one in the file always wins.  Since only the last one survives, I chose to delete these "all but last duplicates" cc @h-kataria @dclarizio
To get this list, I checked manually, but then decided to write a test so we don't accidentally add duplicates again.
Once these duplicates were eliminated, I then enhanced the tests to validate the first seed does only creates, a subsequent seed does not make any changes and eliminated some slowness (11 seconds -> 6 locally).
Finally, I also removed the unused "feature" to seed product features from the non-existing db/fixtures/miq_product_features directory.  cc @Fryguy @gtanzillo @dclarizio Please let me know if this was wrong, I can't see this being used.

Finally, I also removed the unused "feature" to seed product features from the non-existing db/fixtures/miq_product_features directory.

I believe this is for downstream productization.  Can you verify?

If identifier is meant to be unique...let's put a unique validation on the model.  Then you don't need to self-check.  Seed will just straight-up fail if there are duplicates.

Finally, I also removed the unused "feature" to seed product features from the non-existing db/fixtures/miq_product_features directory.
I believe this is for downstream productization. Can you verify?

I looked, I couldn't see anything besides an ae datastore... @h-kataria @dclarizio can you confirm?

If identifier is meant to be unique...let's put a unique validation on the model. Then you don't need to self-check. Seed will just straight-up fail if there are duplicates.

It's already there.  Seed will create or update based on the identifier.  It was looping through each identifier section of the yaml, fetch the row (N+1) matching the record, creating or updating it.
For example, tail of a log which no product features + seeding showing that we had duplicate identifiers in the yaml that were first created, then updated:
[----] I, [2015-09-30T12:52:04.120682 #32449:3fd8b5460208]  INFO -- : MIQ(MiqProductFeature.seed_from_hash) Creating product feature: Identifier: [ab_group_new], Name: [Add a new Button Group]
[----] I, [2015-09-30T12:52:05.439592 #32449:3fd8b5460208]  INFO -- : MIQ(MiqProductFeature.seed_from_hash) Updating product feature: Identifier: [ab_group_new], Name: [Add Button Group]

Finally, I also removed the unused "feature" to seed product features from the non-existing db/fixtures/miq_product_features directory.
I believe this is for downstream productization. Can you verify?
I looked, I couldn't see anything besides an ae datastore... @h-kataria @dclarizio can you confirm?

The other thing it might be used for is the UI module plugin piece.

The other thing it might be used for is the UI module plugin piece.

@martinpovolny?

@Fryguy I think I applied all of your suggestions

Finally, I also removed the unused "feature" to seed product features from the non-existing db/fixtures/miq_product_features directory. cc @Fryguy @gtanzillo @dclarizio Please let me know if this was wrong, I can't see this being used.

Ok, rebased, @martinpovolny any idea about the above directory that doesn't exist anywhere?  I'd like to remove that feature if we're not using it.  Thanks!

@martinpovolny @dclarizio Can you review/merge this? Thanks!

@jzigmund can you look over changes in db/fixtures/miq_product_features.yml, i think you are renaming a feature in your PR https://github.com/ManageIQ/manageiq/pull/3987 that's being deleted by this PR.

@h-kataria @jzigmund @martinpovolny Can we get this reviewed?  Part of the benefit of the revised spec is that it will now fail if we accidentally introduce a new duplicate identifier.  Currently, we have duplicate identifiers we had no idea we had, nor if there are parts of the UI that needed the now deleted duplicates, and finally, it was costly both in tests and in seeding to create and then update the same duplicated identifier as only the last one in "wins".

Bump, this really needs to get in so as we add new product features, the tests are verifying that the identifiers are unique.

@h-kataria @martinpovolny @jzigmund @himdel @skateman Can someone please review the Finally, I also removed the unused "feature" to seed product features from the non-existing db/fixtures/miq_product_features directory part of this PR?   Do we ever seed product features anywhere using a yaml file that is not db/fixtures/product_features.yml?  That feature is being removed in this PR since it's unused AFAIK.

@jrafanie : The possibility to add product features is needed for the UI plugins to work. See https://github.com/ManageIQ/manageiq/pull/1680. We need to provide a different way for the plugins to add product features if we remove the db/fixtures/miq_product_features directory.

Thanks @martinpovolny, I'll fix this PR to not kill that feature since it's in use.

@jrafanie : @Fryguy did not like the way I hacked this originally. So we might use the opportunity to address his concerns.

@martinpovolny Yeah, we can revisit, but not for this performance PR.

Ok @martinpovolny @Fryguy, I kept the UI plugins feature of loading additional product features and added a test.  I also sped up the tests some more.  See updated description above.

@Fryguy @martinpovolny please review


[QUESTION] I have a question about the default storage path in Longhorn，Can not take effect

I have a question about the default storage path in Longhorn. I deployed it using the kubectl method, and I modified the "/var/lib/longhorn" path throughout the configuration. However, the changes didn't take effect after deployment.
Partial configuration
spec:
nodeSelector:
app: longhorn
containers:
- name: longhorn-manager
image: longhornio/longhorn-manager:v1.5.3
imagePullPolicy: IfNotPresent
securityContext:
privileged: true
command:
- longhorn-manager
- -d
- daemon
- --engine-image
- "longhornio/longhorn-engine:v1.5.3"
- --instance-manager-image
- "longhornio/longhorn-instance-manager:v1.5.3"
- --share-manager-image
- "longhornio/longhorn-share-manager:v1.5.3"
- --backing-image-manager-image
- "longhornio/backing-image-manager:v1.5.3"
- --support-bundle-manager-image
- "longhornio/support-bundle-kit:v0.0.27"
- --manager-image
- "longhornio/longhorn-manager:v1.5.3"
- --service-account
- longhorn-service-account
ports:
- containerPort: 9500
name: manager
- containerPort: 9501
name: conversion-wh
- containerPort: 9502
name: admission-wh
- containerPort: 9503
name: recov-backend
readinessProbe:
httpGet:
path: /v1/healthz
port: 9501
scheme: HTTPS
volumeMounts:
- name: dev
mountPath: /host/dev/
- name: proc
mountPath: /host/proc/
- name: longhorn
mountPath: /data/longhorn/
mountPropagation: Bidirectional
- name: longhorn-grpc-tls
mountPath: /tls-files/
env:
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
volumes:
- name: dev
hostPath:
path: /dev/
- name: proc
hostPath:
path: /proc/
- name: longhorn
hostPath:
path: /data/longhorn/
- name: longhorn-grpc-tls
secret:
secretName: longhorn-grpc-tls
optional: true
serviceAccountName: longhorn-service-account
updateStrategy:
rollingUpdate:
maxUnavailable: "100%"
Can not take effect
I also try this way
https://longhorn.io/docs/1.5.3/advanced-resources/default-disk-and-node-config/ Can not take effect
Can you help me，thank you.

I use the latest

You should not modify the mountPath or hostPath directly.
IMO you should modify the ConfigMap longhorn-default-setting instead.
Such as the example in this section https://longhorn.io/docs/1.5.3/advanced-resources/deploy/customizing-default-settings/#using-the-longhorn-deployment-yaml-file.

thank you


request help: apisix ingress controller is support apisix 2.15？

Issue description
apisix ingress controller is support apisix 2.15？
Environment

your apisix-ingress-controller version (output of apisix-ingress-controller version --long):2.14.1
your Kubernetes cluster version (output of kubectl version):1.18
if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):centos7.6

yes. we use APISIX 2.15 as default e2e environment

yes. we use APISIX 2.15 to run e2e test cases

yes. we use APISIX 2.15 to run e2e test cases

thanks


Added cards for speakers and materials.

This completes the "prettyfication" of the materials section (fix #13)

LGTM!


doc: process: Rename meeting labels

Rename the labels used to mark an issue/PR as to be discussed
in a meeting as "meeting: something", for easier filtering
and for clearer communication with the contributors.

If/once this is merged, I will rename the label:

dev_review =>meeting: dev_review,

Will create a new label

meeting: API

And will link from the wiki https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings into this doc section with a minimal explanation

@nashif : What is the other meaning of the TSC tag?

@nashif : What is the other meaning of the TSC label?

https://docs.zephyrproject.org/latest/development_process/dev_env_and_tools.html#tsc
I do not think adding meeting to the label clarifies anything, it just adds a bottleneck which is a meeting of 1 hour weekly where not much can be processed. We can document that any items with those labels will require attention of the respective groups, whether meetings, slack, mailing lists or any available means. We should not use the github labels and make them stick to a meeting.

it just adds a bottleneck ..

@nashif : Just because something has a "meeting: something" label, it doesn't mean that it cannot be discussed somewhere else earlier, and the label removed before the meeting. Escalating something to a meeting should be a last resort in general.
The label is meant to:

Allow to filter fast in the meeting. So that during the meeting you don't need to decide which of the 20 items, which have had a given label for the last 3 months, is actually relevant.
Allow people to know if something / what is going to be discussed in the meeting.

As soon as something does not need attention in the next meeting, the label is removed.
Very few items should have "meeting: something" attached to them, and ideally they will be handled/de-escalated before the meeting.
@nashif To indicate something requires TSC members attention, I can change the TSC label description to "1w review, requires attention from TSC members" , and create a separate "meeting: TSC"

@nashif In any case, I do not think that we should have any label to bring a issue or PR to the TSC. We should have people request such items added to the TSC agenda instead.
So I just removed the TSC label from the meetings section.

@nashif In any case, I do not think that we should have any label to bring an issue or PR to the TSC. We should have people request such items added to the TSC agenda instead.

we should be consistent, there are other meetings and labels, how do we deal with backport PRs? Back to my original objection, I do not think we should have "meeting: "  in the label, everything else I am ok with mostly. We probably need to optimize our meeting structure and how we run meetings and have owners for those meetings and let the owner decide how to manage agenda, either manually or using some label or project.

We probably need to optimize our meeting structure and how we run meetings and have owners for those meetings and let the owner decide how to manage agenda, either manually or using some label or project.

Ok, let's postpone this until we have a more general discussion


chore: Update badge pipeline

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Extract constraint code into functions.

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#644  👈
#642
#639
#638
#637
#636
#634
#633
#631
#582 : 1 other dependent PR (#589 )
#573 : 1 other dependent PR (#574 )
#572
#562
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @alonh5 and the rest of your teammates on  Graphite

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

Project coverage is 92.67%. Comparing base (f54597b) to head (09db1b5).

Additional details and impacted files
@@                          Coverage Diff                          @@
##           05-26-use_securefield_in_interaction     #644   +/-   ##
=====================================================================
  Coverage                                 92.67%   92.67%
=====================================================================
  Files                                        69       69
  Lines                                      9145     9145
  Branches                                   9145     9145
=====================================================================
  Hits                                       8475     8475
  Misses                                      596      596
  Partials                                     74       74

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

Merge activity

Jun 27, 8:38 AM EDT: @alonh5 started a stack merge that includes this pull request via Graphite.


Rename JTstuff

I am not sure, if we want to run readlink at all in case it does not support -f.  In that case, it fails if argument is not symlink (i.e. if javac is not symlink). Even when javac is a symlink usefulness is somewhat questionable, e.g.:
readlink /usr/bin/javac
/etc/alternatives/javac

I am not sure, if we want to run readlink at all, in case it does not support -f. In that case, it fails if argument is not symlink (i.e. if javac is not symlink). Even when javac is a symlink, usefulness is somewhat questionable, e.g.:
readlink /usr/bin/javac
/etc/alternatives/javac

Yah, I know that. But still better then fail. What troubles me more, is  the second usage if [ ! readlink $READLINK_F ${SCRIPT_DIR}==pwd  ] ; then  where
readlink "."
echo $?
1
 readlink "..
echo $?
1
 echo $PWD/..
/home/jvanek/..

So it is making the condition unusable. But still better then  fail I think

Well, if argument is not symlink, it will fail. :)

Actually I was also looking at begining of the script, with some effort you could put it in a function and reuse it...

Actually I was also looking at begining of the script, with some effort you could put it in a function and reuse it...

yy!

Btw, is then second usage even necessary? As SCRIPT_DIR should already be canonized by that very code on the beginning.

Btw, is then second usage even necessary? As SCRIPT_DIR should already be canonized by that very code on the beginning.

In theory no. I think I added it as safe belt, to prevent nasty surprises

Actually I was also looking at begining of the script, with some effort you could put it in a function and reuse it...

function readlink-f() {
  local SOURCE="${1}"
  if [ -f "${SOURCE}" ] ; then
    local NAME="/$(basename "${SOURCE}")"
  else
    local NAME=""
  fi
  while [ -h "$SCRIPT_SOURCE" ]; do # resolve $SOURCE until the file is no longer a symlink
    local DIR="$( cd -P "$( dirname "$SCRIPT_SOURCE" )" && pwd )"
    local SOURCE="$(readlink "$SOURCE")"
    # if $SOURCE was a relative symlink, we need to resolve it relative to the path where the symlink file was located
    [[ $SOURCE != /* ]] && SOURCE="$DIR/$SOURCE"
  done
  local RESULT="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
  echo "${RESULT}${NAME}"
}

donot work as hoped.  Morning would be better then evening. Thanx and see you tomorrow!

Actually I was also looking at begining of the script, with some effort you could put it in a function and reuse it...

function readlink-f() {
  local SOURCE="${1}"
  if [ -f "${SOURCE}" ] ; then
    local NAME="/$(basename "${SOURCE}")"
  else
    local SOURCE="$SOURCE/blah"
    local NAME=""
  fi
  while [ -h "$SCRIPT_SOURCE" ]; do # resolve $SOURCE until the file is no longer a symlink
    local DIR="$( cd -P "$( dirname "$SCRIPT_SOURCE" )" && pwd )"
    local SOURCE="$(readlink "$SOURCE")"
    # if $SOURCE was a relative symlink, we need to resolve it relative to the path where the symlink file was located
    [[ $SOURCE != /* ]] && SOURCE="$DIR/$SOURCE"
  done
  local RESULT="$( cd -P "$( dirname "$SOURCE" )" && pwd )"
  echo "${RESULT}${NAME}"
}
}

Wookrs fine for all except symlinked file, which is natureal due to dirname usage.. Morning would be better then evening. Thanx and see you tomorrow!

No I dont like that :D I will rather drop the usage in java/javac


3.0.0-beta.3 release

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

Checklist

[ ] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[ ] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 68.235% when pulling 83655a749c4eb3b410ec261ae1d908b3671f96ca on 30-release into b9444e8197943db7acf96b67d39a50a9c5f09f78 on master.


Freeze during "The Information"

Bug
Operating system:  Windows 10 19045.3570
Game version: 2.01
CET version: 1.27.1
GPU: RTX 4070 Ti
Description
Latest version seems to cause the game to freeze after the first store robbery BD with Judy, freezes as soon as the BD ends, at the white screen.
This is only happening post 2.01 / 1.27.1, the last version I had before that was on 2.00 / 1.26.1 and didn't have this issue.
Expected behaviour
Not freezing :|
Reproduction
Play The Information quest without skipping the tutorial.

Also, I forgot to mention, but I installed it manually, no mod manager.

Try downgrade CET to 1.27.0?
I got lots of freeze/crash during main stories in chapter 1 w/ CET 1.27.1, includes:

on the way to meet Meredith Stout;
1st time in front of Afterlife, after Jack end his call;
a few minutes later, when following Dexter' guard;
a few minutes later, when talk to Delamain...

I bypassed 1-3 by uninstalling CET temporarily. Then I tried to downupgrade CET from 1.27.1 to 1.27.0 and passed crash 4 safely. I really don't want to try again with the previous crashes...

I just downgraded to 1.27.0 and that fixed 2. for me, I hadn't run into the others yet.

A bit off topic but would you generally recommend keeping CET installed? Does it have any passive benefits apart from the stuff under Settings (which I don't use)? Otherwise it seems like it might be better to install it on a "need to" basis if I don't have any mods that require it, at least until CDPR stops updating the game for good.

A bit off topic but would you generally recommend keeping CET installed? Does it have any passive benefits apart from the stuff under Settings (which I don't use)? Otherwise it seems like it might be better to install it on a "need to" basis if I don't have any mods that require it, at least until CDPR stops updating the game for good.

Some mods work as CET plug-ins, I'm using 3 of them.

Anyway, I went through the scenarios you described, with 1.27.0. Got through all of them fine, so I guess 1.27.1 has problems.

BTW, I also bypassed the crash during "Run This Town" by uninstalling CET in my previous save.

Same issue, CET 1.28.1, Game version 2.02
Game will just freeze during the time skip "glitch effect" transition after meeting with Jago and de-cloaking from Aguilar imprint
Tried disabling CET mods, disabled .archive mods, Red4ext mods, and redscripts mods aswell, no luck
Deleting "cyber_engine_tweaks.asi" allows me to progress after de-cloaking from Aguilar after meeting with Jago

Tried w/ 1.28.1 + Game v2.02, passed:

on the way to meet Meredith Stout;
after finish Judi's tutorial;

Tried 1.28.1 + Game v2.02,
still freezing on
3. 1st time in front of Afterlife, after Jack end his call;
Only redscript and CET installed.

1.29.1 + Game v2.1.
Froze on "Leave Weapon, before exiting the delamain cab"
Solution, Uninstall 1.29.1, get past that point then reinstall.

1.32.2 + Game v2.12
Still seems to be an issue on a fresh reinstall playthough, mods newly installed. Crashed repeatedly right after Judy's braindance demo, always somewhere between when the screen flashes white or just as Judy reaches for V. When it happened the first two times, my computer was overclocked, and the second time, my computer blue screened.


Allow disabling the new line requirement

Most packcage managers will remove the trailing new line when adding or removing packcages, but otherwise the file matches dprints format.
Allow ignore mising newlines at the end of the file

Maybe:
"eofNewLine": "maintain" | "always" | "never"


release

@JCQuintas
Can you release please?
I need this - https://github.com/JCQuintas/ni18n/pull/168

done, sorry for the delay :/