Improved login

Logging in is a pain right now. You have to specify it for each action, and pass in a bunch of flags and remember to suppress output:
- az:
      description: "Logging into Azure..."
      arguments:
        - login
      flags:
        service-principal: ""
        username: "'{{bundle.credentials.AZURE_CLIENT_ID}}'"
        password: "'{{bundle.credentials.AZURE_CLIENT_SECRET}}'"
        tenant: "'{{bundle.credentials.AZURE_TENANT_ID}}'"
      suppress-output: true

We could add a custom login command to the mixin to simplify the default login, which assumes the default environment variable names:
install:
- az:
     login:

In addition, we could have the mixin detect if we are logged in (a file gets stored in ~/.azure after login) before running a command and then automatically logging in if needed.

It would be awesome if support was added for using azcli credentials like Packer , as you'd be able to use a service principle from azure pipelines and handle permissions that way.

That should be possible now that you can mount the ~/.azure directory into the invocation image.

I drafted https://github.com/getporter/az-mixin/pull/74. Please have a look and let me know if this is on the right track to solve this issue.

@lbergnehr Thank you for working on this, it looks like a good way to handle this issue. I have a few comments, nothing big, but I didn't want to add them to the PR yet, as it is still in draft. If you want me to add them, please let me know, just don't know how "draft" the PR is in the current state :)

@lbergnehr Thank you for working on this, it looks like a good way to handle this issue. I have a few comments, nothing big, but I didn't want to add them to the PR yet, as it is still in draft. If you want me to add them, please let me know, just don't know how "draft" the PR is in the current state :)

No problem adding them now from my side! I added a checklist in the PR of things I already know are missing and that I thought I'd add if I would continue finishing this up.

@lbergnehr Thank you for working on this, it looks like a good way to handle this issue. I have a few comments, nothing big, but I didn't want to add them to the PR yet, as it is still in draft. If you want me to add them, please let me know, just don't know how "draft" the PR is in the current state :)

No problem adding them now from my side! I added a checklist in the PR of things I already know are missing and that I thought I'd add if I would continue finishing this up.


Not taking care of "Maximum number of field transformations" in BulkWriter

Hi there
According to the doc
https://firebase.google.com/docs/firestore/quotas#writes_and_transactions

Maximum number of field transformations that can be performed on a single document in a Commit operation or in a transaction : 500

I couldn't find any code handling to this limit in the BulkWriter.
Is this a bug or intended?

I'm not sure I fully understand your question. What is the "bug" you are referring to? Perhaps you could pose your question with "steps to reproduce", the "expected results" and "actual results". Thank you.

Hi @dconeybe
will this help?
https://stackoverflow.com/questions/70764076/what-is-field-transformations-in-firestore

Thanks @dconeybe , I'm asking for BulkWriter to be modified to enforce this limit.

Ok thank you for the clarification. This is likely something that we could add in the future. Unfortunately, we don't have the bandwidth to work on it any time soon. I've added this issue to our product backlog and we will update this issue if/when we have an update. Thank you for taking the time to make this suggestion. It is a good one.

Thanks @dconeybe  🥳🥳🥳


Loosen merlin-sdk deps in components

Description

Update merlin's components dependencies to merlin-sdk with less strict version constraints. So we don't need to update it once we release the merlin-sdk.
Modifications

Update merlin-pyfunc-server and merlin-batch-job's requirements.txt to have merlin-sdk<0.42.0
Tests

Checklist

[x] Added PR label
[ ] Added unit test, integration, and/or e2e tests
[x] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduces API changes

Release Notes

Correct me if I'm wrong, but whenever we don't have to update this anymore even when releasing newer versions of Merlin (e.g. v0.43, v0.44, ...)?

Yes, as we've discussed offline, we start with pinning the merlin-sdk version first to maintain forward compatibility. The merlin-pyfunc-server and merlin-batch-job may have new versions in the future, but for some time, they will still use merlin-sdk<0.42.0

Okay, thanks a lot for clarifying the release process! :D


Perspective projection in 3D should support picking and other UI interactions

Please feel free to close this as duplicate but I actually couldn't find an existing issue.
Whenever viewer.camera.perspective is nonzero, layer.get_value doesn't return the correct value and tools like selection or painting don't work at the correct location. That's because the coordinate transformations involved don't use the perspective projection matrix, so they don't match what's going on on-screen.
We should be able to synchronise our transforms reasonably easy with whatever's going on in VisPy. The best explanation of the current situation is currently found in this Zulip thread.

I solved it by replacing event.position and event.view_direction by values calculated directly from the click position on canvas. I got the transformation needed from viewer.window.qt_viewer.view.camera._scene_transform, which transforms homogeneous canvas coordinates to scene coordinates. A little trick was used here (I don't exactly know why it works): use infinite far z- coordinate (w/2,h/2,-inf,1) to represent eye position, then the ray direction can be correctly calculated with the click pos and eye pos, and then get_ray_intersections() works perfectly.
import napari
import numpy as np
from skimage import data

def click_on_points(layer, event):
    x, y = event.pos
    print(f"event position: {event.pos}")
    w, h = viewer.window.qt_viewer.canvas.size
    transform = viewer.window.qt_viewer.view.camera._scene_transform

    p0 = transform.imap([x,y,0,1]) # map click pos to scene coordinates
    p1 = [w/2,h/2,-1e10,1] # canvas center at infinite far z- (eye position in canvas coordinates)
    p1 = transform.imap(p1) # map eye pos to scene coordinates
    p0 = p0[0:3]/p0[3] # homogeneous coordinate to cartesian
    p1 = p1[0:3]/p1[3] # homogeneous coordinate to cartesian

    # calculate direction of the ray
    d = p1 - p0
    d = d[0:3]
    d = d / np.linalg.norm(d)

    p0 = list(p0[::-1]) # xyz to zyx
    d = list(d[::-1]) # xyz to zyx

    near_point, far_point = layer.get_ray_intersections(
        p0,
        d,
        event.dims_displayed
    )

    distances = calculate_distances(p0,d,point_layer.data)
    closest_point = np.argmin(distances)
    min_dis = distances[closest_point]
    if min_dis<2:
        pick_layer.data = np.array([point_layer.data[closest_point]])

def click_on_image(layer,event):
    #based on ray casting
    x, y = event.pos
    print(f"event position: {event.pos}")
    w, h = viewer.window.qt_viewer.canvas.size

    transform = viewer.window.qt_viewer.view.camera._scene_transform
    p0 = transform.imap([x,y,0,1]) # map click pos to scene coordinates
    p1 = [w/2,h/2,-1e10,1] # canvas center at infinite far z- (eye position in canvas coordinates)
    p1 = transform.imap(p1) # map eye pos to scene coordinates
    p0 = p0[0:3]/p0[3] # homogeneous coordinate to cartesian
    p1 = p1[0:3]/p1[3] # homogeneous coordinate to cartesian

    # calculate direction of the ray
    d = p1 - p0
    d = d[0:3]
    d = d / np.linalg.norm(d)

    p0 = list(p0[::-1]) # xyz to zyx
    d = list(d[::-1]) # xyz to zyx

    near_point, far_point = layer.get_ray_intersections(
        p0,
        d,
        event.dims_displayed
    )

    sample_ray = far_point - near_point
    length_sample_vector = np.linalg.norm(sample_ray)
    increment_vector = sample_ray / (2 * length_sample_vector)
    n_iterations = int(2 * length_sample_vector)
    bbox = np.array([
        [0, layer.data.shape[0]-1],
        [0, layer.data.shape[1]-1],
        [0, layer.data.shape[2]-1]
    ])
    sample_points = []
    values = []
    for i in range(n_iterations):
        sample_point = np.asarray(near_point + i * increment_vector, dtype=int)
        sample_point = np.clip(sample_point, bbox[:, 0], bbox[:, 1])
        value = layer.data[sample_point[0], sample_point[1], sample_point[2]]
        sample_points.append(sample_point)
        values.append(value)
    max_point_index = values.index(max(values))
    max_point = sample_points[max_point_index]
    print('Put point at: ', max_point)
    pick_layer.data = np.array(max_point)

def calculate_distances(line_point, line_direction, points):
    line_point = np.array(line_point)
    line_direction = np.array(line_direction)
    points = np.array(points)

    line_direction = line_direction / np.linalg.norm(line_direction)
    diff_vectors = points - line_point
    cross_products = np.cross(line_direction, diff_vectors)
    distances = np.linalg.norm(cross_products, axis=1)
    return distances

if __name__ == '__main__':
    viewer = napari.Viewer(ndisplay=3)
    points = np.random.rand(100, 3)*128
    point_layer = viewer.add_points(points,size=2,face_color='red')
    point_layer.mouse_drag_callbacks.append(click_on_points)
    pick_layer = viewer.add_points(np.array([0,0,0]),name='pick',face_color='green',size=3)
    blobs = data.binary_blobs(length=128, volume_fraction=0.05, n_dim=3)
    image_layer = viewer.add_image(blobs)
    image_layer.mouse_drag_callbacks.append(click_on_image)
    napari.run()

More demo

Wow!

Was this closed by #7090?

Um, partially? Picking was solved, but not dragging. Arguably, the remaining to-dos are covered by #7205, but I'm not sure.


Label features in status bar inconsistent with label identifier

🐛 Bug
Hi all,
I'm observing an inconsistency in the status bar of napari when inspecting a label image. In the following screenshot, I was hovering over a label with intensity 17; label 17. In napari-skimage-regionprops lives an interactive table that also highlights label 17 in that situation. However, the status bar of napari then lists the properties/features of label 18 and the wrong area measurement for this object.
I'm wondering if the status bar takes the colum "label" in the table into account.

To Reproduce
Steps to reproduce the behavior:

Install napari, napari-segment-blobs-and-things-with-membranes and napari-skimage-regionprops
Open the blobs.tif image
Apply the menu Tools > Segmentation / Labeling > Voronoi-Otsu-Labeling (nsbatwm) with parameters 5 and 2.
Apply the menu Tools > Measurement > Regionprops (nsr)
Hower over labels in the image. It will show the inconsistency in the status bar.

Expected behavior
The status bar text should show the right value (row) from the table, from the line where label=17 in my above mentioned case.
If this is an error in napari-skimage-regionprops, I'm happy to fix it, I just need precise instructions how layer.features should be interpreted to assign the right measurements to the right label. Thanks!
Environment

Please copy and paste the information at napari info option in help menubar here:

napari: 0.4.15rc3
Platform: Windows-10-10.0.19042-SP0
Python: 3.9.10 | packaged by conda-forge | (main, Feb 1 2022, 21:22:07) [MSC v.1929 64 bit (AMD64)]
Qt: 5.12.9
PyQt5: 5.12.3
NumPy: 1.21.5
SciPy: 1.8.0
Dask: 2022.02.0
VisPy: 0.9.6

OpenGL:
- GL version: 4.6.14761 Compatibility Profile Context <IP_ADDRESS> 30.0.13002.1001
- MAX_TEXTURE_SIZE: 16384

Screens:
- screen 1: resolution 1920x1200, scale 1.0

Plugins:
- PlatyMatch: 0.0.3
- RedLionfish: 0.6
- aicsimageio-in-memory: 0.5.0
- aicsimageio-out-of-memory: 0.5.0
- animation: 0.0.2
- cellpose-napari: 0.1.4
- clEsperanto: 0.15.5
- console: 0.0.4
- devbio_napari: 0.4.0
- napari-3d-ortho-viewer: 0.0.1
- napari-accelerated-pixel-and-object-classification: 0.6.6
- napari-allencell-segmenter: 1.1.4
- napari-assistant: 0.1.0
- napari-brightness-contrast: 0.1.7
- napari-clusters-plotter: 0.2.2
- napari-crop: 0.1.5
- napari-curtain: 0.1.1
- napari-folder-browser: 0.1.3
- napari-itk-io: 0.1.0
- napari-ome-zarr: 0.1.0
- napari-plot-profile: 0.2.1
- napari-plugin-search: 0.1.3
- napari-segment-blobs-and-things-with-membranes: 0.2.17
- napari-simpleitk-image-processing: 0.2.1
- napari-tabu: 0.1.5
- napari-time-slicer: 0.4.3
- napari-tools-menu: 0.1.10
- napari-workflow-optimizer: 0.1.3
- napari_skimage_regionprops1: 0.2.9
- napari_skimage_regionprops2: 0.2.9
- ome-types: 0.2.10
- ome_zarr: 0.0.18
- scikit-image: 0.4.15rc3
- svg: 0.1.5

Any other relevant information:

Additional context

Interesting! Thanks for the report @haesleinhuepf! I think you are right that we probably have an off-by-one error in indexing the features...

Aaaah, memories flooding in, you are running into #2596! For now, you need to rename 'label' to 'index'.
If you look at examples/add_labels_with_features.py, you will see that we sweep this issue completely under the rug there. :joy:
So, yeah, for now, renaming 'label' to 'index' should fix your problem...

Thanks for the feedback @jni ! I cannot rename the "label" column because this would break a hand full of plugins and scripts. Thus, I added a workaround to napari-skimage-regionprops: If there is a "label" column, I'm adding an "index" column with the same content. This solves the issue; presumably in all plugins the use our tables.


Enable compression when sending json to client

Make server compress json content when transmitting to client. Json is quite verbose and compresses well.
A real world example is history_graph requested data for in my case 4 temperature sensors updating every half a second for a graph over 10 days lead to 6MB json which compressed to 200KB using deflate compression.

Hi @elupus,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Note. This was a quick proof of concept from github gui, that was tested locally with just web tests.

This needs on-device testing. Specifically how cpu-time compares between transmitting uncompressed data vs compressing+transmitting compressed data.

Let's turn it on and see how it goes.


Expand "Tod task edit"

"Tod task Edit" only returns prompt to edit the name.
It should prompt or allow for:

Name
Description
Priority
Due Date
Labels
Comments

I don't think all 5 need to be there by default (maybe additional parameters), but definitely 1, 2, and 3

Look at the way github does it when creating issues

Ooh nice, I haven't used GH Cli heavily.  I like the way they do it.
Either having extra parameters, or "Edit more, add metadata", or "submit"

v0.6.17 allows editing of content, description, and priority through multi-select.
Still to do (I'm going to make comments a separate thing):

[ ] Due Date
[ ] Labels

Merging into main


dont html tags work in js codes of tagui?

I want to enter array elements in each rows in an element, How can i do it other than below. In below br is not recognized. So output come along with br
sample:
arrayUnique = ["12","14"]
js begin
var ts = arrayUnique.join("")
function generateVar() {
val = ts
}
js finish
generateVar();
enter //*[@id=":sv"]//div as val

I think you ask in the previous issue and I answered - https://github.com/kelaberetiv/TagUI/issues/1054#issuecomment-856897654
Closing this issue.


Update the product name in the offering

Update the product name in the offering

Correct term to use is IBM WebSphere Application Server traditional

Done


Fixed the date of BIP148, should be from August

As @shaolinfry noted, the date was wrong in previous pr.
This should fix it.
@shaolinfry please review this

Please see my other pull request for updated code: https://github.com/bitcoin/bips/pull/512/files

Shaolinfry
I'm the guy whose computer you just hacked in to "help" me. Please contact me as soon as possible I need to celerity a few things


[FIX] Fix git message in info CLI command

fix: #1031
Description

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

  "git": {
    "branch": "fix/cli-git-message",
    "commit": "\"706268f7: [FIX] Fix git message in info CLI command\""
  },

we can get the message like this after fixing it

Just a small change
Please change the commit message to,  Fix git message in info CLI command

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

Comparison is base (a4a75f1) 78.27% compared to head (b13ae51) 78.23%.
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1032      +/-   ##
==========================================
- Coverage   78.27%   78.23%   -0.04%
==========================================
  Files         101      101
  Lines        6351     6345       -6
==========================================
- Hits         4971     4964       -7
- Misses       1380     1381       +1

Files
Coverage Δ

superduperdb/cli/info.py
86.04% <100.00%> (-4.66%)
:arrow_down:

... and 6 files with indirect coverage changes

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

Just a small change
Please change the commit message to, Fix git message in info CLI command

Done

@jieguangzhou Thanks, will merge soon!


[Internal] Autoscale: Add migration for interop layers

Pull Request Template
Description
This adds internal migration APIs for compute and interop layers.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

This is no longer needed. User will use the portal or CLI to do the migration.


Bad indentation of scope for multi-line function definition

Problem
I noticed an indentation issue of the scope highlighting when viewing C++ files. However I saw the same issue also in Java files so I assume it's a general issue.
My project puts the opening brace { in the same line as the if-clause, function parameters, etc. If the parameter list spans multiple lines then it uses the wrong indentation to display the scope (see images).

Steps to reproduce

This is using indent-blankline v3.
Scopes must be enabled.
Create a C++ file and a function with a multi-line parameter list as shown in the images.
Move the cursor inside the function

Expected behavior
It should instead highlight the leftmost line in case of the function scope and in case of the if-clause, it should highlight the 2nd line, aligning with the indentation of the if.
Neovim version (nvim -v)
0.9.1

If you want to keep the meaning of scope, I don't think it should just highlight the first line in the first picture or the second line in the second picture (assuming the scope is within the curly braces?). I guess you would want it to highlight lines 216-219 in the first picture and all but the top row of the second line in the second picture. I don't think this would look very good though.
I think your formatting style just doesn't really work well together with scope, and it might be better to just use current indent for those files when it is ready.

Yeah, your formatting is just very weird. The scope is correct, it starts with the curly braces. It just doesn't look correct because of your formatting.
There isn't really anything I can do.

Hello, thank you for your responses.
I attached two more images that visualize in red how where I think the scope highlighting should be placed. You're right that the scope is identified correctly, it is just the placement which is not ideal.

The code formatting actually doesn't really matter as along as the function parameters are placed on separate lines, which is really really common for functions with long parameter names if you want to adhere to any kind of maximum line length. In the example this is of course not really necessary because the parameter types are short. Putting the opening brace on the same line is also really common in C++, Java, and probably other languages too. Nothing weird about that.
Here is a different parameter formatting which shows the same issue:

Here is where I think it should be placed.

Here is a Java example showing the same issue:

To me it looks like the scope indentation is simply based on the line of the opening brace. My idea for a possible fix would be to determine the indentation based on the closing brace instead? This could be configured using an additional option. I think this would work for most C-like languages and formatting styles.

Fair, basing the scope indent on the end of the scope would make this look better.
But the way the scope is currently implemented, this is not possible. It would require a lot of refactoring.
I don't think I will work on this, PRs are always welcome.

I have run into what seems to be the same problem. It seems that the problem is caused by the newline in the function or if statement (+ the way the C language tree works). Here are some pictures showing how different formatting doesn't give the problem, but a newline in the if statement and { at the end of the line doesn't work.

I think I have an idea for how to solve this after #743 is committed, so I can look at it at that time.

@sfc-gh-mjendruk #795 fixes this for my test cases (above pictures). Could you check if it highlights as you wanted too? (I think the red line goes up one more line than your pictures, because it starts highlighting on the line with { which is what starts the scope [this can be seen by showing the exact scope start].)

Hello, thanks for your work. It got a little better, but it's still not entirely as I would expect it:
There is now no visible scope line in the following case. Previously, the scope line would be aligned with int var3) {

If I add something whose indentation level is higher than int var3) { then the scope line appears.

Hi, I tried out v3.5.1 again, and now it looks like in your screenshot. Not sure what was wrong before, thank you!


Bump path-to-regexp on 1.x branch to resolve CVE-2024-45296

Would it be possible to bump path-to-regexp to a more recent version that contains the fixes for CVE-2024-45296. The current dependency on 2.4.0 is causing our application to be flagged by our customer's security scanning tools.
See https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j for details.

The new version is not 100% backwards compatible in some edge cases and we have evaluated that the impact of the vulnerability is quite small due to the way we're not using that library on the server.
For this reason, we're planning to create a new 2.0 branch and take that into use starting from the upcoming Vaadin 24.5 release while keeping the current version for older Vaadin versions to preserve backwards compatibility.

Would like to see this as well, as for our company provisions we have to fix the CVE

Also same here. We use Vaadin in a few applications in our company and it is causing us to be noncompliant

Thanks for all your feedbacks.
we are aiming to get the vaadin-router 2.0.0.rc1 out this week.

Hi all, Thanks for your patience. the @vaadin/router 2.0.0-rc1 has been released finally.
the final version is planned next week, 🙏

@ZheSun88 awesome, is there an changelog anywhere available?

@ZheSun88  are there any plans to go, to a not releaseCandidate version soon?


dead end connection

fixes #1213: Connecting a lane to itself creates dead end
TMPE.zip
it looks like this:

Note: as it was the case already: if a lane cannot have a possible target, then laneEnd node maker will node be displayed.
data base:

I store it as a lane connection to the same lane.

lane arrows:

no lane arrows for dead ends

BONUS: lane arrows are reset when all outgoing lane connections are removed form the lane.

when user hovers over same lane

it draws a lane curve to the same lane:
any other existing lane connections would hide to indicate what is the post condition of the action.

PS: I also deleted some redundant code.

Tested and i love it.
The mouse cursor on loop lane does not change to (+)

The mouse cursor on loop lane does not change to (+)

its intentional. should it change to + ? Creating dead end removes all existing connections.

The mouse cursor on loop lane does not change to (+)

its intentional. should it change to + ? Creating dead end removes all existing connections.

Maybe use some road sign like 🚫⛔ (easy to confuse with minus) or ❌or something

@kvakvs Maybe use some road sign like 🚫⛔ (easy to confuse with minus) or ❌or something

I think there is no need for mouse sign in here. it only makes things more confusing.

@kianzarrin dead end icon is not visible if you close tool and open again.

Code looks ok, I hadn't got a chance to test it in game yet.

should I wait?

OK I reset all lane arrow for node regardless of whether or not it had lane connection.


[SQL] Ignore character casing for backup storage redundancy param value for managed instance

Description
Ignore character casing for backup storage redundancy param value for managed instance
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

SQL

/azp run


Automatic Dependency for NPM and PIP packages

For NPM packages, the app Npm should be added automatically.
For PIP packages, the app Python2/3 should be added automatically.
Regard the ambiguity with Python versions: #19

Resolved by 35e7ab6a2af3e639a77862835ab9fe9cc6be5042


revert release version

@iskey sorry had to revert it again. Maven team claimed that all systems are working now but the uploads failed again. So had to revert the commit again

@iskey sorry had to revert it again. Maven team claimed that all systems are working now but the uploads failed again. So had to revert the commit again

ok, got it.


Updated NotifyUser description in Set-ProtectionAlert.md

Closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/6164.
@chrisda could you kindly report it? Thanks!

Docs Build status updates of commit 24ea6ac:
:clock10: Full build: the average full build time is 17 min(s) 42 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 24ea6ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-ProtectionAlert.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2078d43:
:clock10: Full build: the average full build time is 17 min(s) 41 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 2078d43:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-ProtectionAlert.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


reqwest middleware support for object_store

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
We could instrument all requests made with object with otlp trace propagation(https://www.w3.org/TR/trace-context/#trace-context-http-headers-format) and for that we would need to be able to inject headers on each request with a different headervalue.
Using https://docs.rs/object_store/latest/object_store/struct.ClientOptions.html#method.with_default_headers doesnt really solve this issue for us because that allows us to set static custom headers but for tracing the injected headervalues need to be dynamic (each request has its own parent trace).
Describe the solution you'd like
Currently, there is no native support for this in reqwest (https://github.com/seanmonstar/reqwest/issues/155) and for the time being we need to look into alternative solutions.
https://github.com/TrueLayer/reqwest-middleware is one of those solutions that allows us to register custom middlewares. So the idea is that object_store could use this crate internally (and wrap the currently used reqwest client with their client wrapper) and provide an interface to pass in new middlewares, which we could then use to provide a trace propagation middleware and other users their own custom once
Describe alternatives you've considered

Additional context

I have wondered in the past about decoupling object_store from reqwest to allow users to provide their own HTTP implementations. This would also potentially have benefits for WASM support, as reqwest's WASM support is a tad incoherent (through no real fault of its own).
I don't hate the idea of adding a middleware abstraction, but I would prefer to stick with first-party abstractions where possible. In fact we avoid exposing reqwest in the public APIs, let alone a third-party extension for it...
Taking a step back, perhaps we could tackle the desired use-case, namely distributed tracing, as opposed to your chosen solution to this problem? How do you envisage trace context propagating through to the HTTP requests from the caller?

I can second this. We also would like instrument our calls to object storage. We couldn't find a way to plugin a reqwest client with tracing.

The only thing I'd use the middleware bits for would be to add specific headers to the request before sending it out.
I can only really speak for my usecase, but I can also assume other folks might want to modify requests in a different fashion.
In terms of wasm support, I think reqwest does do support running in WASM these days (see https://github.com/seanmonstar/reqwest/blob/646b1f80842fb513c31ad3d78374b13932c721c4/examples/wasm_github_fetch/src/lib.rs for an example) - but I personally didn't try yet - so not sure how much replacing reqwest with something else would buy us.


InferenceLogger from the GUI package should be pulled into the core

This logger has usefulness outside of the GUI, should probably exist in the core.

Not sure here. If a nars_lab analyzer want to log something of core that's fine it can do so, but why would core need to do that assuming it works?

core currently uses InferenceLogger in two places. I removed it since they were unreachable code anyway. But from what I could tell InferenceLogger lets you log/display core objects. Its a tool that anyone who has core might want to use to debug their application. Not sure why it wouldnt be in core really. I have no issue with leaving it out either, just seems "awkward" to have to include a whole package just to be able to get some debugging output.

Indeed, in this case no one was using it over the last 4 years. But for the GUI it's ok to support it. I followed an a bit different philosophy in nars_core and nars_gui/nars_lab:
nars_core staying as minimal as possible meaning everything that does not contribute to "NARS running" was removed from there. Also this is the part that is used in applications, so it needs to be as well documented, well tested and as fast as possible, will try my best in summer to catch up here.
nars_gui:  I didn't enforce anything there, and didn't change it much in the last 4 years. But when someone found something annoying, I usually immediately fixed it, it didn't demand test cases to make the GUI bug-free as there are no deep ideas or complex algorithms involved there.
nars_lab: I didn't enforce anything there also, and don't mind if it grows and grows. Whatever NARS-applications one wants to try,  they can go there. Additionally, those that work well, were always added to the Launcher GUI, so that people can run it from the release .jar without demanding knowledge of how to run particular examples. As in nars_gui, not having testcases in nars_lab didn't cause problems so far, as it can be directly visually seen whether an example works or not, differently than in nars_core where extensive testing, profiling and documenting is very important.
My work in the last 4 years was mostly in nars_core (which was created by Pei and then performance-optimized by automenta), and in nars_lab for adding new programmatic examples. nars_gui was fully created by automenta, I didn't touch much there as I am quite happy with the GUI.

Sounds like a good approach. I think having a slim core is important. Just
seemed at the time the logger made sense there as it seemed critical for
debugging. But I retract that assertion based on your statements. Feel free
to close this ticket.
On Thu, May 3, 2018, 7:33 AM patham9<EMAIL_ADDRESS>wrote:

Indeed, in this case no one was using it over the last 4 years. But for
the GUI it's ok to support it. I followed an a bit different philosophy in
nars_core and nars_gui/nars_lab:
nars_core staying as minimal as possible meaning everything that does not
contribute to "NARS running" was removed from there. Also this is the part
that is used in applications, so it needs to be as well documented, well
tested and as fast as possible, will try my best in summer to catch up here.
nars_gui: I didn't enforce anything there, and didn't change it much in
the last 4 years. But when someone found something annoying, I usually
immediately fixed it, it didn't demand test cases to make the GUI bug-free
as there are no deep ideas or complex algorithms involved there.
nars_lab: I didn't enforce anything there also, and don't mind if it grows
and grows. Whatever NARS-applications one wants to try, they can go there.
Additionally, those that work well, were always added to the Launcher GUI,
so that people can run it from the release .jar without demanding knowledge
of how to run particular examples. As in nars_gui, not having testcases in
nars_lab didn't cause problems so far, as it can be directly visually seen
whether an example works or not, differently than in nars_core where
extensive testing, profiling and documenting is very important.
My work in the last 4 years was mostly in nars_core (which was created by
Pei and then performance-optimized by automenta), and in nars_lab for
adding new programmatic examples. nars_gui was fully created by automenta,
I didn't touch much there as I am quite happy with the GUI.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opennars/opennars/issues/107#issuecomment-386265431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC5JAgXTTLIGqZPnrKlc7YmloixrBV-Nks5tuursgaJpZM4TwYTG
.


Video feature

Hi, i have a request for a feature that can significantly decrease the size of course downloaded. Since udacity uses youtube for their video so while downloading video through udacimak, instead of downloading the video can you add the youtube link and your video player will render the youtube video?

Hi @thisisamank . I didn't consider this feature because I want the content to be completely usable offline.
Thanks for the suggestion but I don't have a plan to implement it.


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

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

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

OPS Build status updates of commit 6e2e8db:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 6e2e8db:
:clock10: Incremental building: average incremental building time is 23 sec(s)

OPS Build status updates of commit 6e2e8db:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/databricks-monitoring/databricks-monitoring.md
:white_check_mark:Succeeded
View

docs/databricks-monitoring/databricks-performance-dashboard.md
:white_check_mark:Succeeded
View

docs/databricks-monitoring/databricks-troubleshooting.md
:white_check_mark:Succeeded
View

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

there is a small typo in https://github.com/mspnp/architecture-center/blob/peter/databricks/docs/databricks-monitoring/databricks-performance-dashboard.md
below bold
Sum Task Execution per host
This visualization shows the sum of task execution latency per host running on a cluster. Viewing task execution latency per host identifies hosts that have much higher overall task latency thatn other hosts. This may mean that tasks have been inefficiently or unevenly distributed to hosts.

Superseded by #1372 and #1392


New "since" query

Hi! This adds the new since <year> query to target all versions released since the year specified.
This PR relies on changes made in ben-eb/caniuse-lite#11.
P.S. Also, will it be useful to as well add similar until rule for browser versions released until certain year? May be useful for legacy environments.
#145

Looks good.

ts variable is not really clear.
Can you use reduce with other QUERIES to have common style.

Awesome. Now we need to wait @ben-eb for caniuse-lite. Feel free to ping he every few days.

Now we need to wait next caniuse-lite release (it works automatically, depends on caniuse-db releases)

It's just been released: https://github.com/ben-eb/caniuse-lite/commit/6b0083db60a7f5b4441e1ca6306ef27ec77b1ffb


Walls are wrong on Windows

I have tried both the version from the master branch directly and the version from melpa: in both of them I see something strange instead of the brand new walls.

This may be my configuration issue, but I suggest further investigation. I am using the vanilla emacs that had no problems with pacmacs earlier.
This problem currently stops me from working on issue #137.

I'll take a look!

Dang it! I know what's wrong...  Let me fix that. :)

Basically, it's a regression of #59 I think we need a label for such things...

 I think I can workaround all of the problems I currently facing, but if we will have more in the future I'll drop the XBM support immediately!

Well, maybe due to #138 we will drop it much sooner. %)

I can't workaround them.

Blocked by #141

Fixed in 528ca62e2810f8c23bb8b812c24a575df2bf3f2c

Verified on MELPA Pacmacs 20151102.1138, Windows 8.1, official Emacs build 24.5. Everything works well.


Add .nullable property

Why
Props may also be null and not undefined depending on the model. Using the .optional property would then lead to a type error: Type 'T | null' is not assignable to type 'T | undefined'..
How

[x] Added prop type function nullable
[x] Added nullable to prop options generator
[x] Added tests
[x] Changed docs

I think I'm missing some changes in the readme file - will add them.

I think I'm missing some changes in the readme file - will add them.

Updated it now.


[gemm_v2] MIOpen API needs to change when int8x4 was removed in rocBLAS

Deprecation for rocblas_gemm_flags_pack_int8x4 was announced in the rocBLAS major version rocBLAS 3.0  here: https://github.com/ROCmSoftwarePlatform/rocBLAS/blob/develop/docs/API_Reference_Guide.rst#removal-of-rocblas_query_int8_layout_flag
So for MIOpen this line needs to be changed for a rocBLAS version upper limit:
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/9798115d51eb2fbf799026e0f0071de509826b6b/src/gemm_v2.cpp#L65
We are asking rocBLAS to provide that upper limit

Feedback from rocBLAS team:
rocBLAS version 4 or greater removes rocblas_gemm_flags_pack_int8x4.
rocBLAS version 3 or earlier has rocblas_gemm_flags_pack_int8x4.
You only need to check the rocBLAS major version number.

@junliume I think https://github.com/ROCmSoftwarePlatform/MIOpen/labels/IMPACTS_API should be removed.

@junliume @JehandadKhan This needs to be reopened with https://github.com/ROCmSoftwarePlatform/MIOpen/labels/bug.
The simple removal of deprecated flags leads to correctness issues in GemmFwd solvers with INT8x4 datatypes. The simplest examples of failing configs:
./bin/test_conv2d --int8 --output_type int32 --vector_length 4 --int8_vectorize 1
./bin/test_conv2d --int8 --output_type float --vector_length 4 --int8_vectorize 1

I am working on this.

@junliume The decision is to remove int8x4 support, so the test failures are no longer an issue. The real issue will show up as build errors (with ROCm 6.0 RC).

@junliume Resolved via #2441, let's close this.


Cannot see number genie nodejs working on simulator.

I followed all the steps mentioned in readme file and successfully able to import the actions and deploy the node on firebase. When I goto the simulator to check then I get default response and get the following error on Google actions simulator:
 "message": "Webhook error (206)"
On DialogFlow simulator, in the diagnostic report I see following error in the fulfillment response:
{
  "error": "Converting circular structure to JSON"
}

Hey, thanks for reporting this!
It's a bug with the most recent client library release. We are working on a fix right now.

Hey, I am also facing the same issue, my app when I am deploying to cloud functions, using firebase deploy. The deployed code seems to be throwing this error from GCF.
However the app is working fine locally, using firebase serve.
Even after manually downgrading to 2.0.1 and even 2.0.0. still the same issue persists, when i do a firebase deploy

@Canain, Yep, I have already tried that, its still not working.

It is working when i changed it to
"actions-on-google": "2.0.1",
Thanks a lot for the help.

Should be fixed now, delete the installed packages with rm -rf node_modules package-lock.json and then do npm install again


Implemented getUbcTerm

Sadly, this required huge updates to how we were doing mocking/spying on the Date constructor!

LGTM


Remove hard dependency on kubernetes-client-api

Remove hard dependency on kubernetes-client-api to allow automatic resolution.
This is needed by the sync plugin which may require higher version than the kubernetes-plugin.

/override ci/prow/e2e-aws-jenkins

/lgtm


how to add lighting from all direction

Hi, thanks for the great work, I'm wondering how to add lights from all directions.
https://github.com/yinyunie/depth_renderer/blob/57af7716516a04bd012961f2bc283d636660439b/render_all.py#L236-L245

my mesh in meshlab looks like 1st image but I got RGB like 2nd/3rd images (left, right and top are black, apparently affected by the light) after rendering. Are there any ways to solve this?


Update Azure extension to include waiting for 0.8.4 keptn workflow events.

At the moment the only event that you can wait for using Keptn extension is deprecated "evaluation-done" event.

It would be great to have "Wait for Keptn Event" task updated.

You are right. This is something I want to update ASAP.
Could you help me out with the API call? You probably know exactly which endpoint and how the json body should look like. If you could attach an example I will make some time for the fix.

Just released 1.3.6 of the extension. Its supporting any type of waiting for sequence now. If it's an evaluation the feature to mark the pipeline as red or orange still applies. If it's another type of event, you will recieve the JSON string as a pipeline variable so you can do whatever you want with it. See updated README file.


WebExtensions' web-accessible resources are being hijacked from within Kiwi Browser

Describe the bug
WebExtensions are supposed to be able to list "web-accessible resources:" files contained inside of the extension that web pages are allowed to load. The idea is that the extension's privileged JavaScript can call chrome.runtime.getURL, passing a file path relative to the extension directory, to retrieve a special URL with the protocol chrome-extension://. Under the hood, in the browser internals, this URL is mapped to the extension's file. The extension can then create link, script, etc., elements on the page, and set this URL as their href or src, to inject the file into the page.
As of a recent update to Kiwi's Play Store version, these URLs are being hijacked. Browser debugging indicates that getURL is still returning a chrome-extension:// URL as normal; however, that URL does not map to the actual file in the extension. Instead, on random calls, it maps to some resource hosted on sitescout.com. I know this because when the resource is injected into the page, Chrome immediately blocks it from loading, logging the following error in the extension's errors list:

Chrome blocked resource http://sitescout.com on this site because this site tends to show ads that interrupt, distract, mislead, or prevent user control. Learn more at https://www.chromestatus.com/feature/5738264052891648

The line of code listed for the error is whatever line of code caused the URL to load. For example, if your WebExtension content script creates a script element, sets the URL as the src, and then injects the script element into the page via document.documentElement.append, it's the append line that's flagged as the source of the error.
This issue has the obvious effect of completely breaking WebExtensions that rely on web-accessible resources; it's also greatly concerning from a security and privacy perspective. WebExtensions' web-accessible resource URLs should not map to anything but the underlying files in the extension, and that this seems to happen randomly rather than consistently is suspicious.
To Reproduce
I have attached a bare-minimum-test-case WebExtension that can reproduce this issue. Install it, enable it, and navigate to https://example.com/. Then, rapidly and repeatedly refresh the page, and check the extension's error log.
kiwi sus test (packed).zip
kiwi sus test (unpacked).zip
I performed the test with the packed version. I also used this site to extract my CRX file and check whether it was somehow being tampered with outside of Kiwi (e.g. by a virus on my computer), but I didn't see anything suspicious.
Expected behavior
When the extension functions properly, its content script and the injected web-accessible script file should log to the dev console. The only thing the extension does is create a script element, set it to the web-accessible file's URL, and add that element to the document; the web-accessible script should then log to the console.
Smartphone (please complete the following information):

Device: Galaxy A50
Android Version : Android 11
Kiwi Browser Version 116.0.5845.24

After disabling Kiwi Browser's "Block ads" option in its main menu, I am unable to reproduce this issue. It's possible that "sitescout" is some service Kiwi may have been using to try and scan for ads to block. However, without some kind of explanation, I can't be sure that the problem has gone away.

Hello,
I am looking into the issue, it's clearly an adblocking issue. I am not totally sure yet what causes it.
While I do understand why sitescout.com may appear, I don't see how it could be returned by getURL (for now but there will be a solution)
About sitescout.com, this is is actually part of the adblocker implementation.
To make it simple, in Kiwi the adblocker (subresource_filter) is technically always on all the time (even if it is disabled in the UI).
To display the status in the UI accurately, the browser issues a few real-world checks to see if the adblocking is actually running (by sending actual checks to the adblocking).
This is done to have a reliable way to ensure that the UI and the actual rules executed are coherent (and later if user has custom rules, then the logic is super easy to maintain for me in the UI).
I needed one advertising domain to check in the general case "hey is the adblocker running or not?" so I picked one "random" domain: sitescout.com
-> Not so random: I know it's an advertising domain, and it's also not used for serving ads because the company has shut down.
  if (GetSubresourceFilter()) {
      shouldBlockAds = !(GetSubresourceFilter()->AllowLoad(KURL("http://sitescout.com"), mojom::blink::RequestContextType::XML_HTTP_REQUEST,
                                               reporting_disposition));
  } else {
      shouldBlockAds = false;
  }

I'll check what is going-on rapidly.
Thank you so much for the reproduction steps and troubleshooting !
Arnaud.

Are you sure that the returned resource is different from the chrome-extension URL and that the warning that you see isn't just the adblocker checking whether it is active ? (and actually checks each chrome-extension URL whether to block it or not ?)

In my personal WebExtensions, I was seeing issues that would only occur if my web-accessible resources completely failed to load.
As an example, custom elements don't work properly when defined in WebExtension content scripts, so you have to inject custom element definitions files into page scope, as web-accessible JS resources, to use them. In an extension that had previously done this successfully, I was seeing these custom elements suddenly just intermittently fail to work, and only while Kiwi's adblock was enabled in the UI.

I have a theory: I think that sometimes some URLs or elements names that you use actually hit the adblocker.
The sitescout.com message is actually a side-effect, it just means that the adblocker has loaded and has been hit (that's all it means).
What we could try, is:

If a webpage (on the open internet) tries to load a resource from chrome-extension://, then the resource URL should be loaded anyway even if the chrome-extension:// URL supposed to be blocked by the integrated adblocker rules
except if it is a third-party extension (uBlock Origin, etc), then it should be blocked if the extension wanted it

What do you think ?

By the way, you can know if the adblocker has been hit, this way:
chrome://inspect on your laptop (or in developer tools if you have courage on mobile)
then in Network tab, check if there (blocked:subresource-filter)

Ok trying such changes:
Resources loaded on a chrome-extension:// page (whether foreground or background) cannot be blocked by integrated adblocker.
Web accessible resources (aka chrome-extension:// resources) integrated in a standard web context are not blocked with the integrated adblocker.

It's live


[ConstraintSystem] Fix type-checking of closures in pack expansion contexts

There were two issues here:

Closures were disconnected from the outer expansion they reference elements of;
Isolated conjunctions should bring in count type of the referenced pack expansions into element context otherwise pack element gets disconnected from its pack expansion.

@swift-ci please test


installed keybase on another laptop and permission denied when I cd into /keybase

https://github.com/keybase/client/issues/new?body=[write something useful and descriptive here]

my log id: a8897246f9f54ff9e487f71c
if I use the UI then I can access it but not with the terminal...

Hi @ChrisFernandez -- it may take some time for your other devices to rekey your folders to give your new device access -- maybe you tried to get into them on the terminal for they were ready?  Does it work now, or is it still broken?  I don't see any unusual "permission denied" errors in your log.

@ChrisFernandez did you see any notifications that you should facilitate rekey by turning your original device on (or by entering your backup key)/

@maxtaco you were right.. works now... thanks... BTW what's the ETA for a non-beta version :dancer:


ocean surface forcing documentation

I cannot find, in the documentation, a clean explanation of how fresh-water is accounted for
in the ocean (combination of these parameters: useRealFreshWater, convertFW2Salt, temp_EvPrRn with linear or non-lin free-surface cases). May be adding a sub-section in part-2 regarding ocean surface forcing
(how forcing fields in FFIELDS.h are accounted for) would be useful.

As I have stumbled over closing the salt budget for a linear free surface case (lab_sea) with this combination:
 rigidLid=.FALSE.,
 implicitFreeSurface=.TRUE.,
 exactConserv = .TRUE.,

I strongly support the idea of adding a section about surface forcing, and closing the budget to the manual.
I can imagine that this will be a tedious procedure as many different flag combinations are prossible. I guess the most useful would be:

rigidLid (relatively simple)

@mjlosch I agree this is certainly a useful endeavor, I've struggled with it too. As a starting point, we can get from @jm-c which cases he knows the answer, and which need further testing or exploration (and  how to best obtain user feedback as per your note above)
Suggest we chat about this at next dev meeting?

Definitely something to talk about in the next dev-meeting. But we could start collecting information here. I have used the default lab_sea experiment (directory input), which uses
 implicitFreeSurface=.TRUE.,
 exactConserv = .TRUE.,

changed writeBinaryPrec=64, and added these diagnostics:
  fields(1:3,1) = 'oceSflux','SFLUX   ','surForcS',
   fileName(1) = 'diagsSurf',
  frequency(1) = 36000.,
  timePhase(1) =  3600.,

  fields(1,2)  = 'SALT    ',
   fileName(2) = 'snpSalt',
  frequency(2) =  -36000.,
  timePhase(2) =  3600.,
#
  fields(1:7,3)  = 'ADVx_SLT', 'ADVy_SLT', 'ADVr_SLT',
                   'DFrI_SLT', 'KPPg_SLT', 'WSLTMASS',
		   'AB_gS   ',
   fileName(3) = 'diagsFluxes',
  frequency(3) =  36000.,
  timePhase(3) =  3600.,
 &

and ran with
 startTime=3600.0,
 nTimeSteps=11,
 deltaTmom=3600.0,
 deltaTtracer=3600.0,
 deltaTClock =3600.0,

The following python code
import numpy as np
from MITgcmutils import rdmds

rac=rdmds('RAC')
drf=rdmds('DRF')
hf =rdmds('hFacC')
vol = drf*rac * hf

msk = hf[0,...]
msk[msk>0]=1

dt = 10*3600
rhoConst = 1027

flxs = rdmds('diagsFluxes',11)
srfs = rdmds('diagsSurf',11)
slt  = rdmds('snpSalt',[1,11]) # snapshots of salinity

advx = flxs[0,...] # advective flux in i-direction
advy = flxs[1,...] # advective flux in j-direction
advr = flxs[2,...] # vertical advective flux
dfri = flxs[3,...] # implicit vertical diffusive flux
kppg = flxs[4,...] # KPP counter gradient flux
wslt = flxs[5,...]*rac*msk # "flux of salinity" with moving surface
abgs = flxs[6,...]*vol # tendency due to AB II

osflx = srfs[0,...] * rac*msk # oceSflux
sflux = srfs[1,...] * rac*msk # SFLUX # this contains the virtual salt flux due to fresh water forcing
#sflux = srfs[2,...] * rac*msk # surForcS is the same as SFLUX in this case

sforc = np.zeros(advx.shape)
sforc[0,:,:]=sflux/rhoConst
#
tmpx = np.zeros(advx.shape)
tmpx[:,:,:-1] = advx[:,:,1:]
tmpy = np.zeros(advy.shape)
tmpy[:,:-1,:] = advy[:,1:,:]
divx = (tmpx-advx)
divy = (tmpy-advy)

advr1 = np.zeros(advr.shape)
advr1[:-1,...] = advr[1:,...]
advr[0,:,:] = wslt[0,:,:] # this is important for the linear free surface
divr = (advr - advr1)

dfri1 = np.zeros(dfri.shape)
dfri1[:-1,...] = dfri[1:,...]
ddir = (dfri - dfri1)

kppg1 = np.zeros(kppg.shape)
kppg1[:-1,...] = kppg[1:,...]
ddgr = (kppg - kppg1)

adv = (divx+divy+divr)
diff = ddir+ddgr

dsdt = ((slt[1,...]-slt[0,...])*vol/dt)

resid=(dsdt+adv+diff - sforc - abgs)

print('dsdt = %e'%(dsdt.sum()))
print('adv = %e'%(adv.sum()))
print('diff = %e'%(diff.sum()))
print('kppg = %e'%(ddgr.sum()))
print('sflux = %e'%(sflux.sum()))
print('abgs = %e'%(abgs.sum()))
print('--------------------')
print('resid = %e'%(resid.sum()))
print('====================')

leads to
dsdt = 6.187230e+06
adv = 1.723323e+04
diff = -2.769411e-10
kppg = 3.892637e-10
sflux = 6.373604e+09
abgs = -1.577600e+03
--------------------
resid = 1.624893e-03
====================

For
 rigidLid=.TRUE.,
 exactConserv=.FALSE.,

this works too, because then 'WSLTMASS' = 0 (because WVEL=0). The AB_gS contribution is zero for multidimensional advection schemes, e.g. 33, 7, which is something that I forgot (thanks to @jm-c for pointing this out).


Support for throw/catch/errors

First: Amazing project would like to contribute in any way possible.
Now onto the real issue, why the support for runtime errors(throw, catch, and the Error constructor) isn't planned on being supported?

Nope, it isn't, at least currently.
It's possible to emulate exceptions in C with goto, so potentially I think it can be done at some point.

Good starting point: http://www.di.unipi.it/~nids/docs/longjump_try_trow_catch.html
This solution does not support case when exception is thrown inside another function though, for this we would need to arrange some sort of a stack of jmp_buf variables.
If nothing unexpected pops out, I think the implementation should actually be rather straightforward.


Sending the feedback data to an email?

Hey,
Just looking through the code. Is there any way we can send the feedback and the images to an email? Is this something that we have to implement ourselves?
Also, where can we get the data once we press 'Send'? Any help would be appreciated.
Regards,
Sujan

Since this script only runs in the browser, it can't send email. You'd have to send it to the server, and then send the email from there.

http://stackoverflow.com/questions/14131022/feedback-js-server-api


Add currency field to Piximedia bidder documentation

Hello Team!
Based on your request to comment on our default currency, I noticed the “currency” field for our bidder was missing from our documentation.
Here is the fix!
Thanks you all!

LGTM


Fix build by making du not use futures

Use channels and push them into a vector instead. Code remains largely the same.
Addresses #681 with a simple solution.

@samfoo thank you

:tophat:


Caliper using v1 connector even when SUT set to 2

Which Caliper version are you using?
v0.4.2
Which Node.JS version are you using?
10.22
Which operating system are you using?
Alpine
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
I am building caliper from source in a docker container -
FROM node:10.22-alpine
RUN apk add --no-cache python g++ make git
RUN mkdir -p /hyperledger/caliper/workspace
RUN mkdir caliper
RUN chown -R node hyperledger/
RUN chown -R node caliper/
RUN chown -R node /usr/local/lib
USER node:node
RUN git clone https://github.com/hyperledger/caliper
RUN cd caliper && git checkout v0.4.2
COPY FabricGateway.js ./caliper/packages/caliper-fabric/lib/connector-versions/v2/FabricGateway.js
RUN cd caliper && npm install && npm run repoclean -- --yes && npm run bootstrap
WORKDIR /hyperledger/caliper/workspace
ENV CALIPER_WORKSPACE=/hyperledger/caliper/workspace
ENV CALIPER_BIND_ARGS -g
RUN mkdir /usr/local/lib/.npm-global/lib/node_modules
RUN npm config set prefix "/usr/local/lib/.npm-global"
ENV NODE_PATH /usr/local/lib/.npm-global
ENV PATH /usr/local/lib/.npm-global:$PATH
ENTRYPOINT ["node", "/caliper/packages/caliper-cli/caliper.js"]

And I run it using the following docker-compose file
version: '2'
networks:
  byfn:
    external:
      name: first-network

services:
  caliper:
    container_name: caliper
    image: m0bi5/caliper
    command: launch manager --caliper-fabric-gateway-localhost false --caliper-workspace ./ --caliper-networkconfig /hyperledger/caliper/workspace/networks/networkConfig.yaml --caliper-benchconfig /hyperledger/caliper/workspace/benchmarks/myAssetBenchmark.yaml --caliper-bind-sut fabric:2.2 --caliper-flow-only-test --caliper-fabric-gateway-enabled --caliper-fabric-timeout-invokeorquery 60000 --caliper-fabric-timeout-chaincodeinstantiate 60000 --caliper-fabric-timeout-chaincodeinstantiateevent 60000
    volumes:
      - ./caliper-workspace:/hyperledger/caliper/workspace
      - ./swarm-networks/2host-swarm:/hyperledger/caliper
    networks:
      - byfn

What was the observed incorrect behavior?
Caliper uses the v1 FabricGateway even when I pass the --caliper-bind-sut fabric:2.2 flag. It works as expected when I use the hyperledger/caliper:0.4.2 image so I think it has something to do with the local installation.
Please provide the error logs and their surroundings.
Creating caliper ... done
Attaching to caliper
caliper    | 2022.03.03-13:52:30.027 info  [caliper] [cli-launch-manager]       Binding specification is present, performing binding for "fabric:2.2"
caliper    | 2022.03.03-13:52:30.030 warn  [caliper] [bind]     Working directory not specified. Using "/hyperledger/caliper/workspace"
caliper    | 2022.03.03-13:52:30.030 info  [caliper] [bind]     User-provided arguments for npm: "-g"
caliper    | 2022.03.03-13:52:30.030 info  [caliper] [bind]     Binding for<EMAIL_ADDRESS>This might take some time...
caliper    | 2022.03.03-13:52:30.030 info  [caliper] [bind]     Using working directory: /hyperledger/caliper/workspace
caliper    | 2022.03.03-13:52:30.031 info  [caliper] [bind]     Calling npm with: install -g<EMAIL_ADDRESS><EMAIL_ADDRESS>caliper    | npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
caliper    | npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
caliper    | npm WARN deprecated<EMAIL_ADDRESS>This package is no longer maintained.
caliper    | npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
caliper    | npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
.
.
.
caliper    | make: Leaving directory '/usr/local/lib/.npm-global/lib/node_modules/fabric-network/node_modules/pkcs11js/build'
caliper    |
caliper    | ><EMAIL_ADDRESS>postinstall /usr/local/lib/.npm-global/lib/node_modules/fabric-ca-client/node_modules/protobufjs
caliper    | > node scripts/postinstall
caliper    |
caliper    |
caliper    | ><EMAIL_ADDRESS>postinstall /usr/local/lib/.npm-global/lib/node_modules/fabric-network/node_modules/protobufjs
caliper    | > node scripts/postinstall
caliper    |
caliper    | +<EMAIL_ADDRESS>caliper    | +<EMAIL_ADDRESS>caliper    | added 187 packages from 167 contributors in 53.412s
caliper    | 2022.03.03-13:53:23.956 info  [caliper] [cli-launch-manager]       Set workspace path: /hyperledger/caliper/workspace
caliper    | 2022.03.03-13:53:23.957 info  [caliper] [cli-launch-manager]       Set benchmark configuration path: /hyperledger/caliper/workspace/benchmarks/myAssetBenchmark.yaml
caliper    | 2022.03.03-13:53:23.957 info  [caliper] [cli-launch-manager]       Set network configuration path: /hyperledger/caliper/workspace/networks/networkConfig.yaml
caliper    | 2022.03.03-13:53:23.958 info  [caliper] [cli-launch-manager]       Set SUT type: fabric
caliper    | 2022.03.03-13:53:24.013 info  [caliper] [benchmark-validator]      No observer specified, will default to `none`
caliper    | 2022.03.03-13:53:24.013 info  [caliper] [caliper-engine]   Starting benchmark flow
caliper    | 2022.03.03-13:53:24.664 info  [caliper] [fabric-connector]         Initializing gateway connector compatible with installed SDK: 1.4.19
caliper    | 2022.03.03-13:53:24.755 info  [caliper] [IdentityManager]  Adding User1 (admin=false) as User1 for organization Org1MSP
caliper    | 2022.03.03-13:53:24.998 info  [caliper] [caliper-engine]   Skipping start commands due to benchmark flow conditioning
caliper    | 2022.03.03-13:53:24.999 info  [caliper] [caliper-engine]   Skipping initialization phase due to benchmark flow conditioning
caliper    | 2022.03.03-13:53:24.999 info  [caliper] [caliper-engine]   Skipping install smart contract phase due to benchmark flow conditioning
caliper    | 2022.03.03-13:53:25.001 info  [caliper] [monitor.js]       No resource monitors specified
caliper    | 2022.03.03-13:53:25.003 info  [caliper] [default-observer]         Observer interval set to 5000 seconds
caliper    | 2022.03.03-13:53:25.005 info  [caliper] [round-orchestrator]       Preparing worker connections
caliper    | 2022.03.03-13:53:25.006 info  [caliper] [worker-orchestrator]      Launching worker 1 of 1
caliper    | 2022.03.03-13:53:25.012 info  [caliper] [worker-orchestrator]      Messenger not configured, entering configure phase...
caliper    | 2022.03.03-13:53:25.013 info  [caliper] [worker-orchestrator]      No existing workers detected, entering worker launch phase...
caliper    | 2022.03.03-13:53:25.013 info  [caliper] [worker-orchestrator]      Waiting for 1 workers to be connected...
caliper    | 2022.03.03-13:53:25.442 info  [caliper] [cli-launch-worker]        Worker is a locally forked process, skipping binding step already performed by the manager process
caliper    | 2022.03.03-13:53:25.443 info  [caliper] [cli-launch-worker]        Set workspace path: /hyperledger/caliper/workspace
caliper    | 2022.03.03-13:53:25.444 info  [caliper] [cli-launch-worker]        Set benchmark configuration path: /hyperledger/caliper/workspace/benchmarks/myAssetBenchmark.yaml
caliper    | 2022.03.03-13:53:25.444 info  [caliper] [cli-launch-worker]        Set network configuration path: /hyperledger/caliper/workspace/networks/networkConfig.yaml
caliper    | 2022.03.03-13:53:25.444 info  [caliper] [cli-launch-worker]        Set SUT type: fabric
caliper    | 2022.03.03-13:53:25.493 info  [caliper] [worker-orchestrator]      1 workers connected, progressing to worker assignment phase.
caliper    | 2022.03.03-13:53:25.494 info  [caliper] [worker-orchestrator]      Workers currently unassigned, awaiting index assignment...
caliper    | 2022.03.03-13:53:25.494 info  [caliper] [worker-orchestrator]      Waiting for 1 workers to be assigned...
caliper    | 2022.03.03-13:53:25.532 info  [caliper] [worker-orchestrator]      1 workers assigned, progressing to worker initialization phase.
caliper    | 2022.03.03-13:53:25.532 info  [caliper] [worker-orchestrator]      Waiting for 1 workers to be ready...
caliper    | 2022.03.03-13:53:26.416 info  [caliper] [worker-orchestrator]      1 workers ready, progressing to test preparation phase.
caliper    | 2022.03.03-13:53:26.417 info  [caliper] [round-orchestrator]       Started round 1 (Store)
caliper    | 2022.03.03-13:53:26.802 info  [caliper] [worker-message-handler]   Initializing Worker#0...
caliper    | 2022.03.03-13:53:26.802 info  [caliper] [fabric-connector]         Initializing gateway connector compatible with installed SDK: 1.4.19
caliper    | 2022.03.03-13:53:26.802 info  [caliper] [IdentityManager]  Adding User1 (admin=false) as User1 for organization Org1MSP
caliper    | 2022.03.03-13:53:26.803 info  [caliper] [worker-message-handler]   Worker#0 initialized
caliper    | 2022.03.03-13:53:26.803 info  [caliper] [worker-message-handler]   Preparing Worker#0 for Round#0
caliper    | 2022.03.03-13:53:26.803 info  [caliper] [connectors/v1/FabricGateway]      Connecting user with identity User1 to a Network Gateway
caliper    | 2022.03.03-13:53:26.803 info  [caliper] [connectors/v1/FabricGateway]      Successfully connected user with identity User1 to a Network Gateway
caliper    | 2022.03.03-13:53:26.803 info  [caliper] [connectors/v1/FabricGateway]      Generating contract map for user User1
caliper    | 2022.03.03-13:53:26.843 info  [caliper] [caliper-worker]   Info: worker 0 prepare test phase for round 0 is starting...
caliper    | 2022.03.03-13:53:26.852 info  [caliper] [caliper-worker]   Info: worker 0 prepare test phase for round 0 is completed
caliper    | 2022.03.03-13:53:26.852 info  [caliper] [worker-message-handler]   Worker#0 prepared for Round#0
caliper    | 2022.03.03-13:53:26.854 info  [caliper] [worker-orchestrator]      1 workers prepared, progressing to test phase.
caliper    | 2022.03.03-13:53:26.855 info  [caliper] [round-orchestrator]       Monitors successfully started
caliper    | 2022.03.03-13:53:26.856 info  [caliper] [worker-message-handler]   Worker#0 is starting Round#0
caliper    | 2022.03.03-13:53:26.861 info  [caliper] [caliper-worker]   Worker #0 starting workload loop
caliper    | 2022-03-03T13:53:26.865Z - error: [Transaction]: verifyArguments: Transaction arguments must be strings:<PHONE_NUMBER>385, "blue", "20", "penguin", "500"
caliper    | 2022.03.03-13:53:26.866 error [caliper] [connectors/v1/FabricGateway]      Failed to perform submit transaction [CreateStoreAsset] using arguments [1355960796385,blue,20,penguin,500],  with error: Error: Transaction arguments must be strings:<PHONE_NUMBER>385, "blue", "20", "penguin", "500"
caliper    |     at verifyArguments (/caliper/node_modules/fabric-network/lib/transaction.js:34:9)
caliper    |     at Transaction.submit (/caliper/node_modules/fabric-network/lib/transaction.js:156:3)
caliper    |     at V1FabricGateway._submitOrEvaluateTransaction (/caliper/packages/caliper-fabric/lib/connector-versions/v1/FabricGateway.js:383:44)
caliper    |     at process._tickCallback (internal/process/next_tick.js:68:7)
caliper    | 2022-03-03T13:53:27.059Z - error: [Transaction]: verifyArguments: Transaction arguments must be strings:<PHONE_NUMBER>602, "blue", "20", "penguin", "500"
caliper    | 2022.03.03-13:53:27.059 error [caliper] [connectors/v1/FabricGateway]      Failed to perform submit transaction [CreateStoreAsset] using arguments [1041877621602,blue,20,penguin,500],  with error: Error: Transaction arguments must be strings:<PHONE_NUMBER>602, "blue", "20", "penguin", "500"
caliper    |     at verifyArguments (/caliper/node_modules/fabric-network/lib/transaction.js:34:9)
caliper    |     at Transaction.submit (/caliper/node_modules/fabric-network/lib/transaction.js:156:3)
caliper    |     at V1FabricGateway._submitOrEvaluateTransaction (/caliper/packages/caliper-fabric/lib/connector-versions/v1/FabricGateway.js:383:44)
caliper    |     at process._tickCallback (internal/process/next_tick.js:68:7)
caliper    | 2022-03-03T13:53:27.259Z - error: [Transaction]: verifyArguments: Transaction arguments must be strings:<PHONE_NUMBER>80, "blue", "20", "penguin", "500"
caliper    | 2022.03.03-13:53:27.259 error [caliper] [connectors/v1/FabricGateway]      Failed to perform submit transaction [CreateStoreAsset] using arguments [579335630680,blue,20,penguin,500],  with error: Error: Transaction arguments must be strings:<PHONE_NUMBER>80, "blue", "20", "penguin", "500"
caliper    |     at verifyArguments (/caliper/node_modules/fabric-network/lib/transaction.js:34:9)
caliper    |     at Transaction.submit (/caliper/node_modules/fabric-network/lib/transaction.js:156:3)
caliper    |     at V1FabricGateway._submitOrEvaluateTransaction (/caliper/packages/caliper-fabric/lib/connector-versions/v1/FabricGateway.js:383:44)
caliper    |     at process._tickCallback (internal/process/next_tick.js:68:7)
caliper    | 2022-03-03T13:53:27.459Z - error: [Transaction]: verifyArguments: Transaction arguments must be strings:<PHONE_NUMBER>69, "blue", "20", "penguin", "500"
caliper    | 2022.03.03-13:53:27.459 error [caliper] [connectors/v1/FabricGateway]      Failed to perform submit transaction [CreateStoreAsset] using arguments [946082815769,blue,20,penguin,500],  with error: Error: Transaction arguments must be strings:<PHONE_NUMBER>69, "blue", "20", "penguin", "500"
caliper    |     at verifyArguments (/caliper/node_modules/fabric-network/lib/transaction.js:34:9)
caliper    |     at Transaction.submit (/caliper/node_modules/fabric-network/lib/transaction.js:156:3)
caliper    |     at V1FabricGateway._submitOrEvaluateTransaction (/caliper/packages/caliper-fabric/lib/connector-versions/v1/FabricGateway.js:383:44)
caliper    |     at process._tickCallback (internal/process/next_tick.js:68:7)
caliper    | 2022-03-03T13:53:27.658Z - error: [Transaction]: verifyArguments: Transaction arguments must be strings:<PHONE_NUMBER>73, "blue", "20", "penguin", "500"
caliper    | 2022.03.03-13:53:27.659 error [caliper] [connectors/v1/FabricGateway]      Failed to perform submit transaction [CreateStoreAsset] using arguments [773283190773,blue,20,penguin,500],  with error: Error: Transaction arguments must be strings:<PHONE_NUMBER>73, "blue", "20", "penguin", "500"
caliper    |     at verifyArguments (/caliper/node_modules/fabric-network/lib/transaction.js:34:9)
caliper    |     at Transaction.submit (/caliper/node_modules/fabric-network/lib/transaction.js:156:3)
caliper    |     at V1FabricGateway._submitOrEvaluateTransaction (/caliper/packages/caliper-fabric/lib/connector-versions/v1/FabricGateway.js:383:44)
caliper    |     at process._tickCallback (internal/process/next_tick.js:68:7)
caliper    | 2022.03.03-13:53:28.762 info  [caliper] [connectors/v1/FabricGateway]      disconnecting gateway for user User1
caliper    | 2022.03.03-13:53:28.763 info  [caliper] [worker-message-handler]   Worker#0 finished

### Please provide your benchmark configuration file content, if possible.

_No response_

### Please provide your network configuration file content, if possible.

_No response_

### Please provide your workload module content, if possible.

_No response_

### Please provide any additional information you deem relevant to the error.

_No response_

@davidkel So that I can implement what you have said in #1245

@m0bi5 I have a PR awaiting review to fix that issue and once it's merged there will be an unstable caliper build which would include it (both a npm module and a docker image)
Another way you could do this would be to install the npm module when building your docker image then patch the file rather than cloning the source. It should be easy to do that approach.

@m0bi5 the fix has been merged and should be in available using  docker pull hyperledger/caliper:0.5.0-unstable-20220304102214
as well as an npm module for the cli npm install<EMAIL_ADDRESS>

@davidkel Thanks a lot, the release works!


Not working in Sketch 5.0

Hi, just to let you know I tried it in Sketch 5.0 and it isn't affecting shapes at all.

@calderaricaio Thank you for feedback! This plugin no longer maintained, sorry.


Why not use https in the url example with passwords?

Hi,
Would it make sense to use HTTPS when passing passwords in the url?
-Pete

And it seems that the HTTPS is not ok there.
Maybe a warning then?
Password will be blindly broadcast in plain text, is it not?

Since obs-websocket doesn't support https/wss (Palakis/obs-websocket#26), loading the site over https will block the ws connection in most browsers since it's mixed content. Hence the warning when it is being loaded over https
I don't think the hash part of the URL gets sent to the server (when loading the page) so I think that part is fine, ofc MITM threat still is gonna exist. The connecting itself doesn't broadcast the password but a one-time hash.
Probably worth extra warning somewhere in UI about password security 🤷♂


[auto] Update benchmark content

Automated changes by create-pull-request GitHub action

We might need to rethink how we handle dev/release here. These changes are now on openproblems:main but corresponding results won't be posted to this repo until the benchmark runs. I wonder if we need a separate release branch?


LoggingConfigurationChangedEventArgs: removed obsolete OldConfiguration and NewConfiguration properties (replaced with ActivatedConfiguration and DeactivatedConfiguration in NLog 4.5)

…n and NewConfiguration
Replaced with ActivatedConfiguration and DeactivatedConfiguration in NLog 4.5

Codecov Report

Merging #3358 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##             dev   #3358    +/-   ##
======================================
+ Coverage     80%     80%   +<1%
======================================
  Files        356     356
  Lines      28205   28231    +26
  Branches    3750    3764    +14
======================================
+ Hits       22588   22614    +26
+ Misses      4535    4511    -24
- Partials    1082    1106    +24


chore(deps): bump https://github.com/jenkins-x/jx-cli-base-image from 0.0.28 to 0.0.29

Update jenkins-x/jx-cli-base-image from 0.0.28 to 0.0.29
Command run was jx step create pr regex --regex (?m)^FROM gcr.io/jenkinsxio/jx-cli-base:(?P<version>.*)$ --version 0.0.29 --files Dockerfile --repo https://github.com/jenkins-x/jx-git-operator.git

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Display likers: server

Add endpoint to get list of people who liked a post

PR in my fork
https://github.com/r1oga/zkitterd/pull/2


Use correct TF device depending on configuration

TF visible devices was being hardcoded to use CPU. This PR fixes TF CPU/GPU paths so that GPU can be used when benchmarking CUDA. Each test much run in a separate process to get around TF global GPU memory management: https://github.com/tensorflow/tensorflow/issues/36465#issuecomment-582749350

@monorimet please review and merge


Kobweb's design

Hey there! I have been testing Kobweb in order to migrate my full stack project running in production. It was built with a custom framework, and uses Ktor. I really appreciate the tooling that Kobweb brings which is lacking in the Kotlin for web community. That being said I have a hard time trying to migrate my existing Ktor server despite having the option to create a custom ServerPlugin and there's a few reasons for that.
While a ServerPlugin (which needs it's own tedious setup) gives you access to the configuration of Ktor and I was able to create custom endpoints I still can't reconfigure e.g. ContentNegotiation and the likes. "Hot restart" also doesn't seem to pull ServerPlugin changes which was a selling point for me.
For the best developer experience when you setup kobweb core, You immediately have your compose html with a ktor webserver working with Ktor exposed. But no additional configuration between the client and the server should be part of core, and any core configuration to the webserver should potentially be supplemented.
Silk, Api, Streaming should be built on top of this leaving no trace in Kobweb's core. I understand these might need their own configuration, but this should be done as an additional dependency and as a plugin to Ktor. Exposing Ktor might produce conflicting configurations, doing so via plugins we would be able to make suitable changes and opt into features as we see fit.
While I understand this was the initial focus of the project I believe this would enable many more projects to consider using Kobweb for it's many advantages.
Thank you for your hard work and building Kobweb

I really appreciate comments like this. It's clear you're taking your time to explore and engage with the framework.
Just to make sure you're aware, I absolutely want the "user has a custom ktor server" approach to work someday. You can see me mentioning this both in our roadmap and this very old bug (which shows I've been biting my nails about this one for a while).
"Hot restart" was a lot of effort to get working, and it works only because it introduces a level of abstraction. Even all my ktor code is baked in at compile time -- all the hot reloading stuff is one level down. (This is why I don't use web sockets directly in Kobweb but introduce my own API streams -- they look like web sockets but they're all new code which are delegated to by web sockets)
As for having the server drive the behavior of your site, that unfortunately wouldn't work for a vast majority of Kobweb's users who use a static hosting site provider to serve their files directly. (See this discussion if you're not already familiar with it).
For now, my best recommendation for custom ktor folks is to have them export their sites using kobweb export --layout static and then add code in their own ktor servers to serving those files directly. (It should be really easy using the APIs discussed here). Of course you'll lose live reloading at this point, but at least it will give you access to kobweb routing and Silk support if that's important to you.
I think the ultimate plan will be to refactor parts of the Kobweb ktor server out into separate libraries which then you could import in your own ktor server. But given everything else on my list, it's not something high on my current priorities, and it may even prove troublesome for reasons I can't quite foresee.
I hope this helps explain a bit why Kobweb is designed the way it is, although please keep the conversation going if you feel like I'm missing something.


On the certifications pages change the text that says expand/collapse courses to expand/collapse lessons

Currently when you go to a page for a certification such as the responsive web design page.
 for each course there is an accordion dropdown which says "expand/collapse courses".
I'm suggesting that it should say expand/collapse lessons instead as I consider the content in the accordion to be more like lessons than courses.
It could alternatively be changed to 'expand/collapse modules' or 'expand/collapse challenges' perhaps.
Here's a screenshot of what I mean:

This sounds like a great clarification. Would you mind if I worked on it?

Hey @raisedadead I saw you closed this PR #41331 and said this issue might be closed too, could you explain why?

I have reached out to @QuincyLarson to get this clarified, thanks for your patience.

@tomjbradley @HBDanks This is a good observation. We changed the word from "lessons" to "courses" for 2 reasons:

Courses sounds more substantial
The word "courses" is much, much more frequently searched on Google than "lessons". And one of the reasons we updated the design of these pages was to make them more useful to people arriving from Google.

Though I'm not an expert I do understand the SEO concerns, but it still seems a tiny bit misleading, after all they're shorter form lessons so they're not that substantial and although it seems unlikely, I could see this confusing people.
Wouldn't it maybe be better to mention courses on the curriculum page like so:

and edit each certification/course page to say 'units' at the top instead and 'expand/collapse lessons'

Wouldn't having the word courses featured prominently on the curriculum page be more informative and have similarly good SEO?

Hey @tomjbradley,
Thank you for your suggestion, but as Quincy stated we would like to keep it the same.
Enjoy your day and happy contributing


fix(meta): no shuffle rule on TPC-H Q18

Signed-off-by: Alex Chi<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Before:

After:

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

hold until @yuhao-su has finished fixing the Q18 bug.


The height of the camera center

Hi, I'm very interesting in different camera settings in different datasets.
Recently I'm observing the differences of object distribution across different datasets like Waymo Open and NuScenes. My question is that, what are the height of the cameras from the ground?
I can use camera extrinsics to recover the heights from ego center to the cameras, but I can not get the exact height of the camera from the ground. I can't infer it by the transformations, since I have no idea about the properties of the global origin or ego center.
To be specific, could you please tell me what is the height of the five camera optical centers of Waymo Perception Dataset, relative to the ground? I mean the ground that vehicle is driving on. Or, maybe there is any method to recover this property from the existing open dataset?

Hi, great question! The vehicle frame origin (ego center) is located on the ground, so you can read the height from the camera extrinsics directly.

Here is one of the camera pose I get in the dataset：
CAM_FRONT (front camera to ego)
[[-0.    0.    1.    1.54]
[-1.   -0.02 -0.   -0.02]
[ 0.02 -1.    0.    2.12]
[ 0.    0.    0.    1.  ]]
So the height is approximately 2.12 meters?

Thank you! It helps a lot.


Make heroku-keepalive optional

Suggested in https://github.com/github/hubot/issues/827 by @mal

We have to run our Hubot on our own hardware due to security policy, unfortunately this means we get messages about missing Heroku URLs when starting up.
I've removed the plugin from the package.json and external-scripts.json but it would good to have it as an option at creation time.

@technicalpickles It looks like heroku-keepalive is still in the generator script: https://github.com/github/generator-hubot/blob/97746f1fe73df1aa00859c9a8c9ba5fd4fedae9e/generators/app/index.js#L139

Hi,
This is still an issue.

Hi,
This is still an issue.

no longer a problem.


Modsuits

About the PR
Adds modsuit (just standard modsuits in this PR) that can be sealed, requires power and uses backpack slot.
Modules not implemented yet, but they'll be ready soon. Other types of modsuits will be added with modules.
I'll try to finish modules logic and add first modules in next two weeks (it'll be faster after i finish modules system)
Modsuit parts can be researched in experimental branch as T1 technology. Modsuit Cores can be found in cargo catalog. Modsuit control have flashlight and storage (it'll be replaced with modules)
Technical details

Fully changes ToggleableClothingSystem to work with multiple toggleable clothings.
Changes some systems that should work with ComponentToggler.
Slightly improves ConfirmableAction allowing it to use iconOn as confirm icon
Improves ChargerSystem allowing it to raise relayed FindPowerCellEvent

Media
Modsuit crafting:
https://github.com/user-attachments/assets/8ff03d3a-0fc1-4818-b710-bfc43f0e2a68
Modsuit sealing:
https://github.com/user-attachments/assets/6671459a-7767-499b-8678-062fc1db7134
:cl:

add: Modsuits can be reseached as T1 experimental technology. Modules not implemented yet.

pretty sure these are roundstart in ss13

Can you put AI in this suit version?

Can you put AI in this suit version?

Nope. It'll be implemented in future.

Remember Goobers, this is an addition you cannot walk out of :feelsgood:

Are security, medical, syndicate ect modsuits included? Or do they still use hardsuits

Just standard modsuit in this PR. Department/Syndicate modsuits will be added with modules.

(Also check YAML Linter fail)


Implement support for Fastify framework

This is a first PR to implement basic support for Fastify framework. If accepted, I'll work on improving test coverage and also will look into supporting granular per-endpoint validation as well.

Coverage decreased (-2.2%) to 96.992% when pulling 0f295e3a71ab0e3806246e622d385db07302efa9 on feature/fastify into f3db16356ee7e87632866ef16ca168f83d0b3f9f on master.

@kobik Coverage reduction seems to be in trivial parts of fallback logic that would require import registry reset to test properly, but if you feel strongly about it being tested, I can figure out a way :)

@kobik Any chance you could take a look?

yes, i'll take a look tomorrow morning.
On Mon, Apr 6, 2020 at 1:24 AM Igor Savin<EMAIL_ADDRESS>wrote:

@kobik https://github.com/kobik Any chance you could take a look?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Zooz/express-ajv-swagger-validation/pull/111#issuecomment-609494538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI2JZ6KUW5DYYS7KZRUSMLRLEAH7ANCNFSM4LZAD7SA
.

@kobik Any updates?

yes, i'm on it.
need to read about Fastify middlewares.
On Thu, Apr 9, 2020 at 1:39 PM Igor Savin<EMAIL_ADDRESS>wrote:

@kobik https://github.com/kobik Any updates?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Zooz/express-ajv-swagger-validation/pull/111#issuecomment-611459284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI2JZ3MKBAYUW634BKBIPDRLWQXNANCNFSM4LZAD7SA
.

@kibertoad i'd really like the package to have to same api for all frameworks and think i have an alternative for the getPlugins addition.
It would be easier to explain in code than in words, so please see https://github.com/Zooz/express-ajv-swagger-validation/tree/feature/fastify-support
seems like i'm missing something because i can't make the validation to happen in fastify though, maybe you'll figure this out quicker than me.
let me know what you think

app.register(inputValidation.validate);
@kobik The problem is that you are passing function that invokes validator, while fastify expects to get validator itself. If we want to preserve exact same API, validate should return FP-wrapped plugin, otherwise inputValidation.validate() could return it, but in general I don't think that exactly same API can be preserved, due to fastify plugin system somewhat differing from connect-style middleware.

@kobik Opened https://github.com/Zooz/express-ajv-swagger-validation/pull/112 as an alternative.
See https://github.com/Zooz/express-ajv-swagger-validation/pull/112/commits/34b0597e25e2b1df0b78eb41ad688e7a92b3dc55 for the needed change. I think this is as close as we can possibly stay to common API.

@kibertoad can we close this one?


Error downloading nasm

As noted in issue #6950 nasm-2.12.02.tar.bz2 is currently unavailable. (www.nasm.us does not accept connections.) @trsaunders observed this for head of r0.12 and I can confirm this for v0.12.0.
Workaround: Google the file to get it from another source and update URL in tensorflow/workspace.bzl (if you download a .gz file re-compress to bz2 and put it on a webserver) - sha256 fingerprinting should check that the file contents are correct; if you don't trust ./configure to check this, check the sha256sum yourself against the sha256 given in the .bzl file.

pasting error message for people googling the problem (shortening local paths)
ERROR: /tmp/bazel/external/jpeg/BUILD:162:1: no such package '@nasm//': Error downloading [http://www.nasm.us/pub/nasm/releasebuilds/2.12.02/nasm-2.12.02.tar.bz2] to /tmp/bazel/external/nasm/nasm-2.12.02.tar.bz2: GET returned 503 Service Unavailable and referenced by '@jpeg//:simd_x86_64_assemblage23'. ERROR: /tmp/bazel/external/jpeg/BUILD:162:1: no such package '@nasm//': Error downloading [http://www.nasm.us/pub/nasm/releasebuilds/2.12.02/nasm-2.12.02.tar.bz2] to /tmp/bazel/external/nasm/nasm-2.12.02.tar.bz2: GET returned 503 Service Unavailable and referenced by '@jpeg//:simd_x86_64_assemblage23'. ERROR: Evaluation of query "deps((//tensorflow/... union @bazel_tools//tools/jdk:toolchain))" failed: errors were encountered while computing transitive closure.

I meet the same issue.

It looks like the nasm website is totally down for the count. Still.
The good news is that, at HEAD, this isn't a problem because we have the redundant GCS mirror URL. However I've got two PRs out to fix it anyway at HEAD and in the r0.12 branch. Earlier release branches do not need to be fixed because ≤r0.11 don't build nasm.
Thank you for bringing this to our attention.

This is fixed at HEAD so I'm marking as resolved. The fix for r0.12 should be merged probably tonight or tomorrow. It just seems like the tests aren't being cooperative.

I am unable to build tensorflow on Ubuntu Linux 16.04. This issue with the nasm website hasn't been fixed yet. Copying and pasting the URL works fine but the build process still says that the site is inaccessible.

@case540 Last comment raises questions w.r.t. international viability of mirror.bazel.build. Fedora appears to have deleted old NASM source of truth link. We need to find a working failover URL for that tarball that isn't pkgs.fedoraproject.org.
cc: @gunan @martinwicke

Most external mirrors seem to have tar.xz instead of tar.bz2.
Option 1: Download one of these tar.xz mirrors, uncompress it to .tar, compare to a .tar obtained from the currently used .tar.bz2, run sha256 on the tar.xz file and update workspace.bzl to use the tar.xz file from a few suitable mirrors. (This assumes that Bazel knows how to extract a tar.xz archive. The docs only mention gz and bz2.)
Option 2: Set up another build mirror, for example on google drive, not just for nasm but for all dependencies. According to https://stackoverflow.com/questions/39925649/is-it-possible-to-get-the-download-link-with-sharing-option-from-gdrive-api-in-c it is fairly easy to automatically obtain the download URLs for uploaded files on google drive. I'm suggesting google drive as google is connected to tensorflow.

I am able to download the pkgs.fedoraproject.org NASM mirror. Just to clarify, is the reason we want to replace it because it is not reliable (and not that is doesnt work at all)?
And Option 1 should be work. Looks like some deepmind project has Bazel handle a tar.xz archive...
https://github.com/deepmind/lab/blob/master/WORKSPACE#L28

Bazel can absolutely handle .tar.xz.
mirror.bazel.build and the canonical authoritative URL is the minimum requirement.
Long term might be nice if more trusted orgs wanted to help us diversify our mirroring of public artifacts.

More specifically, would it be possible for us to get nasm from here?
http://www.nasm.us/pub/nasm/releasebuilds/2.13.02/nasm-2.13.02.tar.gz

The source used to be http://www.nasm.us/pub/nasm/releasebuilds/2.12.02/nasm-2.12.02.tar.bz2 (not .gz) but it was changed because www.nasm.us did not accept connections on the 19th of January 2017. It would increase reliability if this URL was added as a 3rd source. I can confirm that the sha256sum is still right, i.e. is is the same tar file and the same bzip2 compression parameters were used (presumably the defaults).
What traffic can a mirror site expect that hosts the 0.9 MiB nasm packages from bazel clients? In other words, how many fresh builds are made worldwide per month?

Even GitHub itself had 98.7% availability, back when I helped rewrite Bazel's downloader. If we start adding additional mirrors (e.g. AWS, Alibaba, etc.) then I'd ideally like to see it be systemic, i.e. more than just nasm. That would elevate Bazel to carrier grade status.

jart's comment points to 2 different approaches:

Ask (publicly) for a volunteer to mirror all of https://mirror.bazel.build/ -- This call should include some statistics what monthly traffic, peak hourly traffic, number of concurrent connections etc. to expect.

Hand-picking individual low priority fall back mirror sites for individual packages where the 2nd URL is not github.com. If not confident that the site can deal with high traffic we should ask for permission. Google search finds the following candidates for nasm:

https://ftp.osuosl.org/pub/blfs/conglomeration/nasm/
http://ftp.oregonstate.edu/.1/blfs/conglomeration/nasm/ (this probably is the same server as the above)
https://mirror.sobukus.de/files/src/nasm/
http://ftp.lfs-matrix.net/pub/blfs/conglomeration/nasm/

Those are important concerns. It's part of why we designed Bazel downloader to do failover. We don't want our CI systems hammering anyone's web server. We also want to protect user privacy with opt-in trust while respecting the decisions of their policymakers.
We could hand-pick mirrors, but I'd recommend we hold off and focus on just making sure our URLs aren't broken. Expanding our mirror ecosystem in a delicate way that engenders trust with the community is something that goes way above my paygrade. I'm just an ordinary engineer.

While we are waiting for the grand solution, can somebody with Google Contributor License Agreement add http://www.nasm.us/pub/nasm/releasebuilds/2.12.02/nasm-2.12.02.tar.bz2 as a third URL (after mirror.bazel.build and pkgs.fedoraproject.org) in tensorflow/tensorflow/workspace.bzl?
A 3rd source, even one with mediocre uptime, is better than no 3rd source. No need to ask nasm.us for permission as they used to be the primary source.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.