Retrain on COCO ok, yolo.py with new trained_weights.h5 cause error

Thank you very much for this great model!
I have retrained this model with pretrained 'darknet53_weights.h5' and COCO dataset, and I got a trained weights in logs/000/trained_weights.h5, I moved it to model_data.
I have modified yolo.py for using this new weights as followed:
class YOLO(object):
    def __init__(self):
        self.model_path = 'model_data/trained_weights.h5' # model path or trained weights path
        self.anchors_path = 'model_data/yolo_anchors.txt'
        self.classes_path = 'model_data/coco_classes.txt'

To makesure using yolo_body, I modified codes as followed:
    def generate(self):
        model_path = os.path.expanduser(self.model_path)
        assert model_path.endswith('.h5'), 'Keras model or weights must be a .h5 file.'

        # Load model, or construct model and load weights.
        num_anchors = len(self.anchors)
        num_classes = len(self.class_names)
        is_tiny_version = num_anchors==6 # default setting

        # try:
        #     self.yolo_model = load_model(model_path, compile=False)
        # except:
        #     self.yolo_model = tiny_yolo_body(Input(shape=(None,None,3)), num_anchors//2, num_classes) \
        #         if is_tiny_version else yolo_body(Input(shape=(None,None,3)), num_anchors//3, num_classes)
        #     self.yolo_model.load_weights(self.model_path) # make sure model, anchors and classes match
        # else:
        #     assert self.yolo_model.layers[-1].output_shape[-1] == \
        #         num_anchors/len(self.yolo_model.output) * (num_classes + 5), \
        #         'Mismatch between model and given anchor and class sizes'

        self.yolo_model = yolo_body(Input(shape=(None,None,3)), num_anchors//3, num_classes)
        self.yolo_model.load_weights("model_data/trained_weights.h5")

When I use python yolo.py to predict pic, I got errors:
/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/h5py/__init__.py:36: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
Using TensorFlow backend.
Traceback (most recent call last):
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1567, in _create_c_op
    c_op = c_api.TF_FinishOperation(op_desc)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Dimension 0 in both shapes must be equal, but are 1 and 75. Shapes are [1,1,1024,255] and [75,1024,1,1]. for 'Assign_360' (op: 'Assign') with input shapes: [1,1,1024,255], [75,1024,1,1].

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "yolo.py", line 210, in <module>
    detect_img(YOLO())
  File "yolo.py", line 32, in __init__
    self.boxes, self.scores, self.classes = self.generate()
  File "yolo.py", line 69, in generate
    self.yolo_model.load_weights("model_data/trained_weights.h5")
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/keras/engine/topology.py", line 2667, in load_weights
    f, self.layers, reshape=reshape)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/keras/engine/topology.py", line 3393, in load_weights_from_hdf5_group
    K.batch_set_value(weight_value_tuples)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/keras/backend/tensorflow_backend.py", line 2372, in batch_set_value
    assign_op = x.assign(assign_placeholder)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/ops/variables.py", line 615, in assign
    return state_ops.assign(self._variable, value, use_locking=use_locking)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/ops/state_ops.py", line 283, in assign
    validate_shape=validate_shape)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/ops/gen_state_ops.py", line 60, in assign
    use_locking=use_locking, name=name)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
    op_def=op_def)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 3392, in create_op
    op_def=op_def)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1734, in __init__
    control_input_ops)
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1570, in _create_c_op
    raise ValueError(str(e))
ValueError: Dimension 0 in both shapes must be equal, but are 1 and 75. Shapes are [1,1,1024,255] and [75,1024,1,1]. for 'Assign_360' (op: 'Assign') with input shapes: [1,1,1024,255], [75,1024,1,1].
Exception ignored in: <bound method BaseSession.__del__ of <tensorflow.python.client.session.Session object at 0x7fdb13964940>>
Traceback (most recent call last):
  File "/home/cooli7wa/venv/yolo/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 707, in __del__
TypeError: 'NoneType' object is not callable

Sorry for this long post. Thank you very much for your help!

sorry for this

@ljning  Thanks Very Much for the solution.


Add notebook-based demonstration with real-world data

Description
This PR adds a notebook-based demonstration of software information entropy measurements using PubMed data.
Closes #71, #73
What is the nature of your change?

[x] Content additions or updates (adds or updates content)
[ ] Bug fix (fixes an issue).
[x] Enhancement (adds functionality).
[ ] Breaking change (these changes would cause existing functionality to not work as expected).

Checklist
Please ensure that all boxes are checked before indicating that this pull request is ready for review.

[ ] I have read the CONTRIBUTING.md guidelines.
[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own contributions.
[ ] I have commented my content, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to related documentation (outside of book content).
[ ] My changes generate no new warnings.
[ ] New and existing tests pass locally with my changes.
[ ] I have added tests that prove my additions are effective or that my feature works.
[ ] I have deleted all non-relevant text in this pull request template.

@d33bs, I've just pushed my changes to software-information-entropy.ipynb and would appreciate your feedback whenever you get the chance. I consulted with the internet for the best library to use for parallel processing, and came across concurrent.futures. After testing the two models, I found that ProcessPoolExecutor works best for me. I'm curious, though, if you have any ideas for a better approach or suggestions to further optimize this process. Thanks!

Thanks for the feedback @d33bs ! I will start implementing your comments now

@d33bs I have pushed changes to software_information_entropy.py and would like your feedback when you get the chance! Changes that have been made,
1.) Refactored src code to allow the notebook to reference these modules through import statements
2.) Added pygit2 to almanack dependencies
3.) Added code documentation

Thanks @willdavidson05 ! I've just updated the PR with new organization and included some other changes for correcting the Jupyter-book build and deployment (specific to mostly Plotly rendering and citations). Interested to get your feedback when there's a moment!

Thank you @willdavidson05 for your amazing work in helping make this happen! Going to merge this in.


low global rate of mutations for molecular clock

I’m surprised by the low global rate (~0.06), which would predict only ~70 mutations over the ~1200 days shown, not ~140.  Did you force the regression through the intercept (we should because the root will have 0 divergence from the root)?  Also, perhaps we should limit the global regression to data from the last three months to focus on the overall rate to the present.

closed by PR #265


[v4] Different persist behavior in development and release build

Describe the bug
We use @tanstack/query-sync-storage-persister and @tanstack/react-query-persist-client in react-native project with react-native-mmkv as storage.
Before using any useQuery, we should wait for restoring queries in queryClient by PersistQueryClientProvider. But we've faced the issue, when in developer mode our queries were already restored and contains correct data on the start of the render, but in release mode our queries were not restored and were undefined at the same time. After researching the problem, we found a useIsRestoring hook, which help to avoid undefined data in the start of using query. All the same, in developer and release modes behavior is different, but should be the same.
Your minimal, reproducible example

Steps to reproduce

Connect react query persist and react-native-mmkv like in the example
Add persist for any query, for example CatalogQuery:

const MAX_PERSIST_TIME = Number.MAX_SAFE_INTEGER;
const clientPersister = createSyncStoragePersister({ storage: clientPersistStorage });

export const clientPersistOptions: PersistQueryClientProviderProps['persistOptions'] = {
  dehydrateOptions: {
    shouldDehydrateQuery: (query) => {
      if (isEqual(query.queryKey, CatalogQueryKeys.catalog)) {
        return query.state.status === 'success' || query.state.status === 'error';
      }

      return false;
    },
  },
  maxAge: MAX_PERSIST_TIME,
  persister: clientPersister,
};

Run two apps: react-native run-ios (Developer mode) and react-native run-ios --mode Release (Release mode)
FYI: also it can be reproduced for android

Fetch data for CatalogQuery and persist it to the storage

Close and reopen the app

Watch for data on the first render
[Developer Mode]: data of query on first render will be from persistor
[Release Mode]: data of query on first render will be undefined, after restoring it will be from persistor

Expected behavior
As a developer, I expected the same sync persistor behavior for production and developer modes, but I am seeing that developer mode doesn't do restoring, when production does.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: [IOS, Android]
Browser: [React native]

Tanstack Query adapter
react-query
TanStack Query version
4.13.0
TypeScript version
5.2.2
Additional context
No response

we found a useIsRestoring hook, which help to avoid undefined data in the start of using query

that's not what the hook does. restoring happens asynchronously, and while that happens, react-query still renders the application. The queries will be in status: 'loading' ('loading' in v4, 'pending' in v5) and fetchStatus: 'idle' while that happens. The QueryFunction will not run while we're restoring.
This is documented here: https://tanstack.com/query/v4/docs/react/plugins/persistQueryClient#persistqueryclientprovider
The restore it self happens in a useEffect. It can be that timings are different in react between prod and dev, I can't comment on that.
If you want to prevent rendering your app until restore has finished, you'd probably want some sort of Gate component and wrap your app in it:
import { useIsRestoring } from '@tanstack/react-query'

export function PersistGate({ children, fallback = null }) {
  const isRestoring = useIsRestoring()

  return isRestoring ? fallback : children
}

Okey, maybe if someone meet this issue, he find needed information. I don't know about timings on dev and prod, but in my opinion they shouldn't be different in different modes (if restoring is really async operation), but on the other side, I haven't found any related to NODE_ENV or other env variable code in react-query.
Now close the issue for the moment, let's have a look for someone else who stuck with this and can find more info.
Thanks for your reply!


Position graticule labels relative to the viewport when view is rotated

Fixes #10673

I noticed that as well, but as soon as the map is panned it fixes itself..  I presume the loader isn't being called at every change in rotation and the previously calculated positions are still being used.

You are right @mike-000. The loader is only called as the image size increases, until it has reached the maximum size it can get from rotating.
I'm wondering if it wouldn't be better to draw the labels in a postrender function. That way, it would also not be necessary to pass the rotation to the loader.


Improve image quality on hidpi desktop displays

Images are kind of bad on a Mac

Updated, but now images are too high-res. Problem stems from overwide image element dimensions, which can't be easily fixed without regressing a CLS bug with flex and lazy-loaded images.


cell segmentation cs.score_and_mask_pixels function modulenotfounderror

Hi,
I am trying to follow the Spateo cell segmentation tutorial, but I am throwing a ModuleNotFoundError for fbgbp at this step for segmentation:
st.cs.score_and_mask_pixels(     adata, 'nuclear', k=5, method="EM+BP" )
Checking my installed libraries, however, it appears that fbgbp==0.2.1 is already installed.
To try to get around this problem, I directly cloned the fbgbp locally and inserted a path via
sys.path.insert(0, "/Users/lab/Downloads/fbgbp/")
import fbgbp
prior to the st.cs.score_and_mask_pixels function, but I am getting a new ModuleNotFoundError: No module named 'fbgbp.binary_belief_propagation'

Any help with this would be appreciated. Thanks!

Hi Vivan, I think you will need to update the fbgbp version to be 0.2.1.
@YifanLu2000 can you please fix the version issue and dependency issue for spateo?


Maliha: Created about me page

Love how it looks!
If you are up for a challenge, instead of using absolute pixel positions, play around with css grids or other more responsive / relative ways of formatting the text + images.

visual nit: the social icon colors blend into the background right now. A thin outline might help with their readability.

added some more nits since you have to address Henry's comments anyways. Reminder that you can feel free to dismiss nits if you disagree or comment that you will address it later.


getViewProperties() shouldn't take string array

We might not want to depend on splitting an incoming string for ui components because UI doesn't support loading all widgets (components) by string - just zoom, compass and attribution. Furthermore, the location e.g. top-right of the ui component should also be passed in so I think we need to re-think this structure.
https://github.com/Esri/application-boilerplate-js/blob/4master/js/boilerplate/UrlParamHelper.js#L56
Here's how I handle it in config.json and and use main.js to set up the UI.
{
  "appid": "",
  "group": "",
  "title": "",
  "subtitle": "",
  "about": "",
  "webmap": "de5fe9b1be9b43a9aa195164438b557f",
  "webscene": "",
  "uiComponents": {
    "zoom": {
      "visible": true,
      "position": "top-left"
    },
    "attribution": {
      "visible": true,
      "position": "top-left"
    },
    "search": {
      "visible": true,
      "position": "custom"
    }
  },
...

@kellyhutchins what do you think? I think you wrote this piece, correct?

@driskull @alaframboise  I'm fine with updating to the structure Al proposes or perhaps a better option would be to leave the ui component bit out of the boilerplate. Group templates wouldn't support this behavior so perhaps we just leave it up to the template developer to add config for the components they want users to be able to configure.

Hey @kellyhutchins, with the flexibility of the new UI components, it's easy to allow users to add/remove UI components and position them with just strings, so I think it might be a good idea to leave this out of boilerplate and leave it up to the app to configure the UI from config.json?
When I get a little further along I can show you.

Ok. can you submit a PR to remove them?

looks like this is good now.


How to write attributes from clients

Hi
I'm developing fan control integration, but this cluster don't have any commands to set speed. I would like to set speed attribute but python-matter-server don't support any API to do it.
Similarly, I think we should have APICommand.WRITE_ATTRIBUTE
@api_command(APICommand.WRITE_ATTRIBUTE)
    async def write_attribute(self, node_id: int, endpoint: int, attribute: ClusterAttributeDescriptor, timedRequestTimeoutMs: int = None, interactionTimeoutMs: int = None):
        """Write a attribute on a target node."""
        LOGGER.info("Write Attributes node_id: %s", node_id)
        attributes = [(endpoint, attribute)]
        return await self.chip_controller.WriteAttribute(
            nodeid=node_id,
            attributes=attributes,
            timedRequestTimeoutMs=timedRequestTimeoutMs,
            interactionTimeoutMs=interactionTimeoutMs,
        )

We are currently working on some other aspects but we can add the write attributes feature after that. If you are in a rush, feel free to PR the addition.

We are currently working on some other aspects but we can add the write attributes feature after that. If you are in a rush, feel free to PR the addition.

I can send a PR to add it recently.

@marcelveldt how can I become a contributor? how can I create PR?
@hidaris please send your PR to implement this feature. Thanks

@marcelveldt how can I become a contributor? how can I create PR? @hidaris please send your PR to implement this feature. Thanks

Hi, I implemented this part locally, but I'm debugging the Thermostat integration these two days, so I don't have time to submit for now, if you're in a hurry, I'll see about sending a PR this weekend

@marcelveldt how can I become a contributor? how can I create PR? @hidaris please send your PR to implement this feature. Thanks

Hi, I implemented this part locally, but I'm debugging the Thermostat integration these two days, so I don't have time to submit for now, if you're in a hurry, I'll see about sending a PR this weekend

Thanks a lot.
in fact, I implemented both write_attribute and Thermostat, FanControl integration locally, but I don't know how I can create PR and become a contributor :(((

@vinhpn96 You can just open a PR here if its server related. If you want to contribute to the Home Assistant project (for he integration part), simply open a PR on the core project here: https://github.com/home-assistant/core/pulls

@hidaris are you on discord ?

@hidaris are you on discord ?

I’m on Discord, but not in the ha server. Can you add me? My username is hidaris#7947


fix: use main config's language option

the current setting is a duplicate of the main config's.
https://github.com/hexojs/hexo/pull/3654
https://github.com/hexojs/hexo-starter/pull/12
This PR shouldn't affect the languages folder (based on preliminary testing).

LGTM. thanks very much


Gltf bones do not import with correct positions, causing animations to break.

Godot version
3.4.5
System information
windows 10
Issue description
Importing gltf with bones will position them incorrectly.
This causes the animations to be incorrect and the model to morph weirdly.
The top of the picture shows the incorrect bones, and the bottom shows the correct bones.

In other programs, the gltf opens just fine with the corrrect bone positions and animates correctly,
However, when it comes to Godot, godot fails to load them correctly.
Here's another example,
You can see clearly how the bones in godot don't have the correct angle.

Steps to reproduce
Here is the simple box example gltf.
boxgltf.zip
Minimal reproduction project
No response

At least half of this issue is not a bug.
Blender uses the Head-Tail format, while most other 3D software uses the Node format; in the Node format, the Tail has no Position and is treated as just an angle, so it is not visualized. In other words, Blender allows the octahedron to be oriented in a direction that has nothing to do with parent-child relationships, while other 3D software forces the octahedron to be oriented from parent to child.
I don't know why the mesh and bones are offset, it could be something wrong with the EditBone bindings in Blender, or it could be that the Rest is set up corruptly when Godot imports it.

@TokageItLab , I'm not using Blender. The gltf files weren't exported from Blender.
I'm not sure what you mean. I just know that when importing into Godot, godot changes the positions and angles of the bones, causing the animations to become inaccurate.

@prominentdetail If you have imported an external gltf into Blender and seen it work, it may be due to a problem with Blender's gltf importer changing the axis of the bone by default, see https://github.com/KhronosGroup/glTF-Blender-IO/issues/1662.

@TokageItLab , I didn't use Blender to create the gltf or animation. It was created in another program. I tested importing it into Blender, and it imported fine. Impoorting into any program works except Godot. Godot messes up the bones.
I'll repeat, I'm NOT using Blender. This isn't a Blender issue.

@prominentdetail Can you confirm the problem with Godot 4?

@prominentdetail Can you confirm the problem with Godot 4? This may be a 3.x specific bug, and may be related #60345 or #49974.

I just tested 4.0 and It looks like it imports the animations fine in 4.0

cc @fire

We did a gltf upgrade in summer 2021, maybe a fix got lost.

Also may be related #65988.

Also may be related https://github.com/godotengine/godot/issues/62403.

Thanks for looking into this! 👍

Does this issue occur in Godot 4.x, such as Godot 4.3 stable, or is it only in Godot 3.x?

@aaronfranke I just tested importing animations in 4.3 stable and there are still bugs with importing. I will create a new report.

The positions of Godot Engine 4.3 and Blender 4.2.1 match. There is no animation.


Unit test for matching panda rate limits

When the user overrides, panda expects the down rate is at least as high as the rate limit, but up needs to be under the limit. Add a test like in panda, but add user overriding. Would have caught mismatch in https://github.com/commaai/openpilot/pull/26934, or the panda PR that changed it, when bumped.

@adeebshihadeh do you think a good place for this is https://github.com/commaai/openpilot/blob/8d3e661f795260ebd708975105d98f1bdbbcf181/selfdrive/car/tests/test_models.py#L204 ?
Can start adding more cases like these for torque cars


Fixed user notifications so they are only seen once

Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

What are the relevant tickets?
Fixed #193
What's this PR do?
Prevents repeated displays of a user notification that came from the backend
How should this be manually tested?

Enroll a user in a course run via the product detail page

When the enrollment completes, you should be redirected to a new page and see a success banner message

Navigate to the home page right away (with or without dismissing the notification)

You should not see the success message. On the main branch, this message would be shown every time you loaded a new page within the cookie's life span (20 seconds)

Codecov Report

Merging #236 (45680be) into main (39bab4a) will increase coverage by 0.03%.
The diff coverage is 97.56%.

@@            Coverage Diff             @@
##             main     #236      +/-   ##
==========================================
+ Coverage   90.94%   90.97%   +0.03%
==========================================
  Files         214      214
  Lines        6281     6314      +33
  Branches      309      309
==========================================
+ Hits         5712     5744      +32
- Misses        482      483       +1
  Partials       87       87

Impacted Files
Coverage Δ

.../containers/pages/login/LoginForgotPasswordPage.js
96.29% <ø> (-0.14%)
:arrow_down:

static/js/lib/api.js
97.77% <80.00%> (-2.23%)
:arrow_down:

static/js/containers/App.js
96.96% <100.00%> (+0.09%)
:arrow_up:

static/js/containers/App_test.js
100.00% <100.00%> (ø)

static/js/containers/HeaderApp.js
95.83% <100.00%> (+0.59%)
:arrow_up:

static/js/containers/HeaderApp_test.js
100.00% <100.00%> (ø)

static/js/lib/api_test.js
100.00% <100.00%> (ø)

static/js/lib/notificationsApi.js
77.14% <100.00%> (+2.14%)
:arrow_up:

static/js/lib/notificationsApi_test.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 39bab4a...45680be. Read the comment docs.


Popup offset

I want to modified the offset of a CircleMarker's popup (I use geojson datas)
var geojsonLayer = new L.GeoJSON(null, {
    pointToLayer: function (latlng){
        return new L.CircleMarker(latlng, {
            radius: 8,
            fillColor: "#ff7800",
            color: "#000",
            weight: 1,
            opacity: 1,
            fillOpacity: 0.8
        });
    }
});
geojsonLayer.on("featureparse", function (e) {
    var popupContent = e.properties.popupContent;
    e.layer.bindPopup(popupContent);
});
map.addLayer(geojsonLayer);

I didn't find where to add the offset : I tried in bindPopup (after popupContent) but it's not working.
e.layer.bindPopup(popupContent,(10,10));

Someone can help me?

IS there a way to dynamically reset the offset? I am trying a variable for offset that is set on a map zoom, but it doesn't seem to work..thanks!

@mourner  You just saved my day!!


Add .crate file support

These are .tar files I believe. Should be an easy patch.

Related to #41


chore: Remove startTransition's synchronous examples and infos

Fix #7027: chore: Remove startTransition's synchronous examples and infos

Deleting it is probably not enough. It should include documentation for the async callbacks.


[fix] TimeTable timelag error

CATEGORY
Choose one

[X] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
Off by one error 🙃
We displayed an error about time lags if the time lag was > than the length of the data. It should actually be >=.
For example, if the time lag is 7 days and there are 7 data points, there should be an error because there are only 6 days in between the first and last day. However, this error was not caught, so users saw:
An error occurred while rendering the visualization: TypeError: Cannot read property 'Unknown' of undefined
Fixed viz to include the = case.
TEST PLAN
Narrow date range to include n points. Add a comparison column with a time lag of n. Ensure that you get the correct error.
REVIEWERS
@graceguo-supercat @michellethomas @etr2460

Codecov Report

Merging #8619 into master will increase coverage by 6.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #8619      +/-   ##
=========================================
+ Coverage   65.78%   71.8%   +6.01%
=========================================
  Files         482     121     -361
  Lines       23798   12763   -11035
  Branches     2589       0    -2589
=========================================
- Hits        15655    9164    -6491
+ Misses       7974    3599    -4375
+ Partials      169       0     -169

Impacted Files
Coverage Δ

superset/assets/src/components/Checkbox.jsx

.../assets/src/dashboard/reducers/dashboardFilters.js

...ets/src/dashboard/components/dnd/DragDroppable.jsx

superset/assets/src/components/EditableTitle.jsx

...src/explore/components/controls/VizTypeControl.jsx

...t/assets/src/components/InfoTooltipWithTrigger.jsx

.../src/dashboard/components/UndoRedoKeylisteners.jsx

...ts/src/explore/components/ExploreActionButtons.jsx

.../src/dashboard/components/FilterTooltipWrapper.jsx

...sets/src/dashboard/components/DashboardBuilder.jsx

... and 350 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff6773d...e30e5fe. Read the comment docs.


Create official Rust template

It would be good to have official Rust template

Expected Behaviour
Having Rust's OpenFaaS template

Current Behaviour
No Rust template

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Docker version docker version (e.g. Docker 17.0.05 ):

Are you using Docker Swarm or Kubernetes (FaaS-netes)?

Operating System and version (e.g. Linux, Windows, MacOS):

Link to your project or a code example to reproduce issue:

/lock


No auth

Remove auth0 integration to make initial startup of nodeSpeed IDE easier.

Pull request created against wrong repo. Closing...


ConflictBuilder creates geometry with duplicate consecutive points

ConflictBuilder.getGeometry() uses OtsLine2d.offsetLine() which can produce lines with duplicate consecutive points.

The following code reproduces the bug.
        List<Point2d> pointList = new ArrayList<>();
        pointList.add(new Point2d(58.8008890211771, -3.98492795650657));
        pointList.add(new Point2d(58.7352328155604, -3.87671405467892));
        pointList.add(new Point2d(58.6022745872352, -3.66684760589021));
        pointList.add(new Point2d(58.463988530184, -3.45735023359504));
        pointList.add(new Point2d(58.3205653656466, -3.2484126590331));
        pointList.add(new Point2d(58.1721958148626, -3.04022560344412));
        pointList.add(new Point2d(58.0190705990717, -2.83297978806779));
        pointList.add(new Point2d(57.8613804395136, -2.62686593414384));
        pointList.add(new Point2d(57.6993160574282, -2.42207476291196));
        pointList.add(new Point2d(57.533068174055, -2.21879699561188));
        pointList.add(new Point2d(57.3628275106338, -2.0172233534833));
        pointList.add(new Point2d(57.1887847884042, -1.81754455776593));
        pointList.add(new Point2d(57.0111307286061, -1.61995132969947));
        pointList.add(new Point2d(56.8300560524791, -1.42463439052365));
        pointList.add(new Point2d(56.6457514812629, -1.23178446147817));
        pointList.add(new Point2d(56.503621700788, -1.08749368041061));

        OtsLine2d line = new OtsLine2d(pointList);

        OtsLine2d left = line.offsetLine(1.4000000000000004, 1.4000000000000001);
        OtsLine2d right = line.offsetLine(-1.4000000000000004, -1.4000000000000001).reverse();

        Point2d[] points = new Point2d[left.size() + right.size()];
        System.arraycopy(left.getPoints(), 0, points, 0, left.size());
        System.arraycopy(right.getPoints(), 0, points, left.size(), right.size());

        Polygon2d geometry = new Polygon2d(points);

        OrientedPoint2d location = new OrientedPoint2d(58.80088902117715, -3.9849279565065774, 2.1161468637905547);
        BoundingPolygon.geometryToBounds(location, geometry);

In BoundingPolygon.geometryToBounds(...) the following code produces duplicate points based on a transformation of points that are already very close together.
        Iterator<Point2d> itSource = geometry.getPoints();
        Iterator<Point2d> itTarget = new Iterator<>()
        {
            /** {@inheritDoc} */
            @Override
            public boolean hasNext()
            {
                return itSource.hasNext();
            }

            /** {@inheritDoc} */
            @Override
            public Point2d next()
            {
                return transformation.transform(itSource.next());
            }
        };

The following code solves this by explicitly checking whether points are the same.
        Iterator<Point2d> itSource = geometry.getPoints();
        Point2d prev = null;
        List<Point2d> points = new ArrayList<>();
        while (itSource.hasNext())
        {
            Point2d next = transformation.transform(itSource.next());
            if (!next.equals(prev))
            {
                points.add(next);
            }
            prev = next;
        }
        BoundingPolygon b = new BoundingPolygon(new Polygon2d(points));

BoundingPolygonTest has been added to test the code that generated the bug above. It runs without failure now.


powerpc/altivec: use __vector instead of vector

The gcc altivec extension defines keywords for vector, bool, and pixel, both with underscores and without. However, unless another extension is used the keywords without underscores conflict with standard types.
To resolve the conflict use the keywords with underscores for the altivec vector types.
Fixes: #2711
Note: with this dlib can be compiled but crashes during tests. This crash is not specific to powerpc. There is probably something missing when neither the AMD nor the Arm vector implementation is available.

__vector is fine, it generally should not make any difference. It's specific to avx/vsx where-as vector is a generic extension.

Yeah I'm surprised it's crashing.


HDFS-17506. [FGL] Performance for phase 1

Add some benchmarks

Thanks. What is the purpose of this PR? Provide a benchmark tool and each one can test the HDFS cluster performance? or just test the namenode performance locally?

Thanks. What is the purpose of this PR? Provide a benchmark tool and each one can test the HDFS cluster performance? or just test the namenode performance locally?

FSNLockBenchmarkThroughput is a tool, each one can do the performance tests through this tool after deploying FGL.
TestFSNLockBenchmarkThroughput is a UT, it mocks a MiniQJMHACluster and do some performance tests locally.

Thanks. What is the purpose of this PR? Provide a benchmark tool and each one can test the HDFS cluster performance? or just test the namenode performance locally?

FSNLockBenchmarkThroughput is a tool, each one can do the performance tests through this tool after deploying FGL. TestFSNLockBenchmarkThroughput is a UT, it mocks a MiniQJMHACluster and do some performance tests locally.

Got it, thanks.

Can also add usage referring to hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/BenchmarkThroughput.java

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 22s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ HDFS-17384 Compile Tests _

-1 :x:
mvninstall
35m 34s
/branch-mvninstall-root.txt
root in HDFS-17384 failed.

+1 :green_heart:
compile
0m 44s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
0m 40s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
0m 43s

HDFS-17384 passed

+1 :green_heart:
mvnsite
0m 45s

HDFS-17384 passed

+1 :green_heart:
javadoc
0m 43s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  9s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 56s

HDFS-17384 passed

+1 :green_heart:
shadedclient
21m 58s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 37s

the patch passed

+1 :green_heart:
compile
0m 38s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 30s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project/hadoop-hdfs: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 43s

the patch passed

+1 :green_heart:
shadedclient
21m 13s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
212m 26s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

306m 48s

Reason
Tests

Failed junit tests
hadoop.hdfs.tools.TestDFSAdmin

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6806/2/artifact/out/Dockerfile

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

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

uname
Linux 3535f61db013 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
HDFS-17384 / 3b26cc4461beb5090016838299add8be22d8dd97

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6806/2/testReport/

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

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6806/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 01s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

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

_ HDFS-17384 Compile Tests _

+1 :green_heart:
mvninstall
128m 34s

HDFS-17384 passed

+1 :green_heart:
compile
10m 30s

HDFS-17384 passed

+1 :green_heart:
checkstyle
7m 37s

HDFS-17384 passed

+1 :green_heart:
mvnsite
10m 54s

HDFS-17384 passed

+1 :green_heart:
javadoc
9m 03s

HDFS-17384 passed

+1 :green_heart:
shadedclient
218m 59s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
7m 15s

the patch passed

+1 :green_heart:
compile
5m 24s

the patch passed

+1 :green_heart:
javac
5m 24s

the patch passed

+1 :green_heart:
blanks
0m 01s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 41s

the patch passed

+1 :green_heart:
mvnsite
6m 18s

the patch passed

+1 :green_heart:
javadoc
5m 27s

the patch passed

+1 :green_heart:
shadedclient
224m 07s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
8m 28s

The patch does not generate ASF License warnings.

614m 22s

Subsystem
Report/Notes

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

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

uname
MINGW64_NT-10.0-17763 ab4e39a29189 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
HDFS-17384 / 3b26cc4461beb5090016838299add8be22d8dd97

Default Java
Azul Systems, Inc.-1.8.0_332-b09

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

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

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

versions
git=2.44.0.windows.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 00s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

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

_ HDFS-17384 Compile Tests _

+1 :green_heart:
mvninstall
88m 04s

HDFS-17384 passed

+1 :green_heart:
compile
6m 18s

HDFS-17384 passed

+1 :green_heart:
checkstyle
4m 39s

HDFS-17384 passed

+1 :green_heart:
mvnsite
6m 24s

HDFS-17384 passed

+1 :green_heart:
javadoc
5m 43s

HDFS-17384 passed

+1 :green_heart:
shadedclient
144m 30s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 44s

the patch passed

+1 :green_heart:
compile
3m 26s

the patch passed

+1 :green_heart:
javac
3m 26s

the patch passed

+1 :green_heart:
blanks
0m 01s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 17s

the patch passed

+1 :green_heart:
mvnsite
3m 59s

the patch passed

+1 :green_heart:
javadoc
3m 26s

the patch passed

+1 :green_heart:
shadedclient
155m 07s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
5m 14s

The patch does not generate ASF License warnings.

415m 09s

Subsystem
Report/Notes

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

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

uname
MINGW64_NT-10.0-17763 45a322de9117 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
HDFS-17384 / 3b26cc4461beb5090016838299add8be22d8dd97

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6806/2/testReport/

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6806/2/console

versions
git=2.44.0.windows.1

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

This message was automatically generated.

The failed UT hadoop.hdfs.tools.TestDFSAdmin is not caused by this PR, I will create a ticket to fix it.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 23s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ HDFS-17384 Compile Tests _

+1 :green_heart:
mvninstall
33m 21s

HDFS-17384 passed

+1 :green_heart:
compile
0m 43s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
0m 43s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
0m 40s

HDFS-17384 passed

+1 :green_heart:
mvnsite
0m 47s

HDFS-17384 passed

+1 :green_heart:
javadoc
0m 44s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  7s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 53s

HDFS-17384 passed

+1 :green_heart:
shadedclient
21m 56s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 42s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
0m 42s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 31s

the patch passed

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  6s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 51s

the patch passed

+1 :green_heart:
shadedclient
21m 49s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
213m 38s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

306m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6806/3/artifact/out/Dockerfile

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

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

uname
Linux 6412d6991c5d 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
HDFS-17384 / db92d267a8d598d36f9fbe59ec8c24ccf754c558

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6806/3/testReport/

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

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6806/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 00s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 01s

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

_ HDFS-17384 Compile Tests _

+1 :green_heart:
mvninstall
108m 02s

HDFS-17384 passed

+1 :green_heart:
compile
7m 17s

HDFS-17384 passed

+1 :green_heart:
checkstyle
5m 38s

HDFS-17384 passed

+1 :green_heart:
mvnsite
8m 07s

HDFS-17384 passed

+1 :green_heart:
javadoc
7m 02s

HDFS-17384 passed

+1 :green_heart:
shadedclient
177m 17s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 46s

the patch passed

+1 :green_heart:
compile
4m 29s

the patch passed

+1 :green_heart:
javac
4m 29s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m 53s

the patch passed

+1 :green_heart:
mvnsite
5m 08s

the patch passed

+1 :green_heart:
javadoc
4m 19s

the patch passed

+1 :green_heart:
shadedclient
193m 49s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
6m 26s

The patch does not generate ASF License warnings.

512m 36s

Subsystem
Report/Notes

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

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

uname
MINGW64_NT-10.0-17763 a4a169f40776 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
HDFS-17384 / db92d267a8d598d36f9fbe59ec8c24ccf754c558

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6806/3/testReport/

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6806/3/console

versions
git=2.44.0.windows.1

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

This message was automatically generated.

Thanks for contribution. Merged.


[CBR-250] Record chain state in the wallet

For detailed discussion, see comment at CBR-250.
Description
Add chain state (available updates, max tx size, etc.) to the passive wallet.
Linked issue
https://iohk.myjetbrains.com/youtrack/issue/CBR-250
Type of change

[ ] 🐞 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 change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

Going to close this for the time being, as we develop a better understanding of how this relates to restoration.


Pornhub breaking

My issue was closed in #532 however I believe this is still an issue (I was not able to re-open the issue)
Please remove ci.phncdn.com and di.phncdn.com from the blocklist.
With these 2 domains blocked, Pornhub looks like this:

Trying to validate...

@funilrys I am having a really hard time validating which domains are breaking Pornhub
It is one of:
ci.phncdn.com
di.phncdn.com
cm.phncdn.com
ew.phncdn.com
cdn1-smallimg.phncdn.com
cdn1d-static-shared.phncdn.com
cs.phncdn.com

Ok,i admit i was wrong on the first issue due to on my end those two domains are not dns blocked but my adblocker is blocking some nasty scripts from them.
Sooo...this is the case here...PING @smed79 as the lists owner.
@funilrys you included one of the EXTRA @smed79's lists which i believe is more for individual use and not for everyone due to probably most of the domains are breaking something.If this is the case it'll be probably for the best if that list is removed from the Ultimate-Hosts...but let's wait for verification first and i guess it's up to you two to decide the next step.
@p1r473  apologies again,the issue is on track to be fixed soon 👍

Let's continue this in the backend (for history purpose)!

/move to Ultimate-Hosts-Blacklist/whitelist

All good now, thanks!


Lookup table tests

Fixed some lint errors and moved the lookupTable_test.js file into test/colors so that the test folder continues to mirror the structure of src.

Coverage remained the same at 60.111% when pulling fe8be8e59ed6ae95ac1fc9433783a72cb2775c5d on ComputerComps:lookupTableTests into 16b8df8fdde51d0a85c44a1193b5483856306b02 on cornerstonejs:master.

Thanks!


When watching a file, watch the config too!

Suggestion
When watching a file, watch the corresponding tsconfig.json too!
🔍 watch, tsconfig.json
watch tsconfig.json
My suggestion meets these guidelines:
[] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[] This wouldn't change the runtime behavior of existing JavaScript code
[] This could be implemented without emitting different JS based on the types of the expressions
[] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
⭐ Suggestion
When a file is being watched, if its tsconfig.json has been updated, TypeScript should look at the configuration and check if any options that affected the output has been updated, if so, it should recompile the watched file.

This is already happening.

Not sure what's being described here. Please give complete steps in a new issue if the above response didn't address your problem.


Add an option to output crate build timings

Currently cargo outputs a line at the end of the build like Finished dev [unoptimized + debuginfo] target(s) in 4.78 secs giving the overall build time. It would be nice if there was a way to get out build times for the individual crates that were built, and even timings for the individual build steps within each crate, like compiling a build script, executing a build script, compiling the crate, compiling any binaries, etc. The most useful thing to me would be to just output a JSON file, probably.

Note that with #7405 this is more or less already in place.

Yea, I'll close in favor of #7405.


Updated to work with vue 3

Updated the code to work with the default version of Vue 3.
https://blog.vuejs.org/posts/vue-3-as-the-new-default.html

Instead of your upgrade to Vue v3 (which @hymccord points out includes many updates we also don't want), I've instead accepted @hymccord's PR to instead just pin to Vue v2.  If we decide we need to upgrade to Vue v3 in the future, we can return to this PR, which has the correct v3 code updates. Thanks for your help!


Wrong principal stress with SOLID189

Hi,
I have the folowing input file representing a rotor with several layers:
!**********************************
!	Variables
!**********************************

R_out	=	0.125
r_in	=	0.025
D_plate	=	0.005
d_layer	=	1
omega_z	=	1

/PREP7
!**********************************
!
MPDATA,GXZ,1,,4.2E9
MPDATA,DENS,1,,1950
!**********************************
!	Elements
!**********************************
ET,1,SOLID186
!**********************************
!	Geometry
!**********************************
CSYS,1

K,1,r_in,0,-D_plate/2
K,2,r_in,0,D_plate/2
K,3,R_out,0,D_plate/2
K,4,R_out,0,-D_plate/2
L,1,2
L,2,3
L,3,4
L,4,1
AL,1,2,3,4

K,5,0,0,D_plate/2
K,6,0,0,-D_plate/2

VROT,1,,,,,,5,6

arcdiv = 20*4
darc = 360/arcdiv
layer = 6

*dim,layers,array,layer
layers(1) = 90,0,0,0,0,0

LSEL,S,LOC,X,r_in
LSEL,R,LOC,Z,-D_plate/2
LESIZE,ALL,,,arcdiv/4

LSEL,S,LOC,X,r_in
LSEL,R,LOC,Z,D_plate/2
LESIZE,ALL,,,arcdiv/4

LSEL,S,LOC,X,R_out
LSEL,R,LOC,Z,-D_plate/2
LESIZE,ALL,,,arcdiv/4

LSEL,S,LOC,X,R_out
LSEL,R,LOC,Z,D_plate/2
LESIZE,ALL,,,arcdiv/4

*Do,i,0,3
LSEL,S,LOC,Y,90*i
LSEL,R,LOC,Z,-D_plate/2
LESIZE,ALL,,,arcdiv/4

LSEL,S,LOC,Y,90*i
LSEL,R,LOC,Z,D_plate/2
LESIZE,ALL,,,arcdiv/4

LSEL,S,LOC,Y,90*i
LESIZE,ALL,,,layer
*EndDo

LSEL,ALL

MSHAPE,0,3D
Mshkey,1
VMESH,ALL

EPLOT,ALL

*Do,j,1,layer
*Do,i,0,arcdiv
		CSYS,1
		ESEL,S,CENT,Y,darc*(i + 0.5)
		ESEL,R,CENT,Z,-D_plate/2+D_plate/layer*(j-1),-D_plate/2+D_plate/layer*(j),D_plate/layer/2
		LOCAL,j*100+i,0,0,0,0,layers(j,1)+darc*(i + 0.5)
		EMODIF,all,ESYS,j*100+i
	*EndDo
*ENDDo
ESEL,ALL

/VSCALE, all, 10, 1
/PSYMB,ESYS,1

!**********************************
!	Load
!**********************************
/SOLU
CSYS,1
OMEGA,,,omega_z
NSEL,S,LOC,X,r_in
D,ALL,UX,0
D,ALL,UY,0
NSEL,R,LOC,Z,0
D,ALL,UZ,0
ALLS

outres,ALL,ALL

solve

finish

!**********************************
!	Plot
!**********************************
/Post1
ALLS
plnsol,s,1

resulting in maximum principal stress of 37.
But when I do:
import pyansys
import numpy as np
import os

path = os.getcwd() + "\\ws"
mapdl = pyansys.launch_mapdl(run_location=path, interactive_plotting=True, loglevel='ERROR', override=True)
mapdl.run("/INPUT, modell.inp")
result = mapdl.result
result.plot_principal_nodal_stress(0, '1', show_edges=True, show_axes=True)

resulting in  a maximum principal stress of only 18. Additionaly the maximum stress is the same at both side, while in ANSYS this is not the case.
Best regards
Willi
P.S. I first modeled the same problem using SHELL elments and had similar problems, but then I read that SHELL elements ae still not supported by pyansys so this is my try to still solve my problem with pyansys.

Thanks for posting this!
There's a release coming out shortly that fixes this (and several other bugs).  See #256

Just tested this out with pyansys==0.42.0 and it works.  Release will be out on PyPi shortly.

I am sorry, but even after upgrading to 0.42.0
>pip show pyansys

Name: pyansys
Version: 0.42.0
Summary: Pythonic interface to ANSYS binary files
Home-page: https://github.com/akaszynski/pyansys
Author: Alex Kaszynski
Author-email<EMAIL_ADDRESS>License: MIT

and updating the "plot_principal_nodal_stress" arguments
import pyansys
import numpy as np
import os

path = os.getcwd() + "\\ws"
mapdl = pyansys.launch_mapdl(run_location=path, interactive_plotting=True, loglevel='ERROR', override=True)
mapdl.run("/INPUT, modell.inp")
result = mapdl.result
result.plot_principal_nodal_stress(0, 'S1', show_edges=True, show_axes=True)

the same error occurs. Are you sure that that the bug is realy fixed with version 0.42.0?

Weird.  Can you upload the result file here?  I'm getting the correct results using v20.1

Oh sorry, Its my fault!
I tested with an already converted python script, but in the conversion process was a misstake. As you might know *Do Commands cant be use with mapd.run(), so I tried to improve your automated conversion process to python by myself, but I missed that arrays in python starts with 0 and in ansys with index 1. :(

Nice.  Thanks!
As a favor, could you please post the script here?  I'd like to add it to the gallery of examples as it's currently lacking:
https://akaszynski.github.io/pyansys/examples/index.html#

Of course! I realy like your work and I am happy to contribute where I can. I couldn't find an option to post my script, can you describe me how to post it?

Hello,
I'm pinging you on this closed issue because GitHub doesn't have an email address for you.
ANSYS is busy improving and extending pyansys.  As an existing user, we are interested in learning about your experience and opinions using this package.  Most notably:

What is your application?
How does pyansys facilitate your work?
What new pyansys features or improvements would you find valuable?
Your feedback will help us prioritize our investments and make pyansys even better.

On behalf of the pyansys development team, I look forward to hearing any feedback from you as it will be used to improve and advance pyansys.
Feel free to respond here to this issue, or email me at<EMAIL_ADDRESS>Alex Kaszynski


can not run on RISC-V linux

bleak version: 0.22.3
Python version: 3.11
Operating System: RISC-V
BlueZ version (bluetoothctl -v) in case of Linux: 5.6.8

Description

The following code can run normally on the Windows platform, but it cannot run on Linux development boards on the RISC-V platform.

What I Did

get a linux borard (Sipeed LicheeRV Nano)
https://www.alibaba.com/product-detail/Sipeed-LicheeRV-Nano-Litchi-Pi-SG2002_1601059587927.html?spm=a2700.galleryofferlist.normal_offer.d_title.59f213a0npUk9B

wiki: https://wiki.sipeed.com/maixpy/en/index.html

pip install bleak

create hci with /dev/ttyS1 and up it.

run above-mentioned test code

import asyncio
from bleak import BleakScanner, BleakClient

async def main():
    device = await BleakScanner.find_device_by_address(
            'F6:0C:C0:F5:66:52'
        )

    print(device)

    if device is None:
        print('not found device')
        return

    async with BleakClient(device) as client:
        print('connected')
        print(client)

asyncio.run(main())

Logs
F6:0C:C0:F5:66:52: NRF_BATTERY_01
Traceback (most recent call last):
  File "src/dbus_fast/_private/unmarshaller.py", line 301, in dbus_fast._private.unmarshaller.Unmarshaller._read_sock_with_fds
BlockingIOError: [Errno 11] Resource temporarily unavailable

During handling of the above exception, another exception occurred:

BlockingIOError
Exception ignored in: 'dbus_fast._private.unmarshaller.Unmarshaller._read_sock_with_fds'
Traceback (most recent call last):
  File "/usr/lib/python3.11/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
BlockingIOError:

this is full logs:
# btmon
Bluetooth monitor ver 5.68
= Note: Linux version 5.10.4-tag- (riscv64)                                                0.708175
= Note: Bluetooth subsystem version 2.22                                                   0.708186
= New Index: C4:3C:B0:6D:53:BD (Primary,UART,hci0)                                  [hci0] 0.708190
= Open Index: C4:3C:B0:6D:53:BD                                                     [hci0] 0.708193
= Index Info: C4:3C:B0:6D:53:BD (RivieraWaves S.A.S)                                [hci0] 0.708198
@ MGMT Open: bluetoothd (privileged) version 1.18                                 {0x0001} 0.708202

@ MGMT Command: Start Service Discovery (0x003a) plen 4                   {0x0001} [hci0] 22.810137
        Address type: 0x06
          LE Public
          LE Random
        RSSI: invalid (0x7f)
        UUIDs: 0
< HCI Command: LE Set Random Address (0x08|0x0005) plen 6                       #1 [hci0] 22.811904
        Address: 3D:31:BA:07:FD:92 (Non-Resolvable)
> HCI Event: Command Complete (0x0e) plen 4                                     #2 [hci0] 22.812883
      LE Set Random Address (0x08|0x0005) ncmd 5
        Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8             #3 [hci0] 22.812987
        Own address type: Random (0x01)
        Filter policy: Accept all advertisement (0x00)
        PHYs: 0x01
        Entry 0: LE 1M
          Type: Active (0x01)
          Interval: 11.250 msec (0x0012)
          Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4                                     #4 [hci0] 22.813647
      LE Set Extended Scan Parameters (0x08|0x0041) ncmd 5
        Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6                 #5 [hci0] 22.813707
        Extended scan: Enabled (0x01)
        Filter duplicates: Enabled (0x01)
        Duration: 0 msec (0x0000)
        Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4                                     #6 [hci0] 22.814640
      LE Set Extended Scan Enable (0x08|0x0042) ncmd 5
        Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4                            {0x0001} [hci0] 22.814764
      Start Service Discovery (0x003a) plen 1
        Status: Success (0x00)
        Address type: 0x06
          LE Public
          LE Random
@ MGMT Event: Discovering (0x0013) plen 2                                 {0x0001} [hci0] 22.814786
        Address type: 0x06
          LE Public
          LE Random
        Discovery: Enabled (0x01)
> HCI Event: LE Meta Event (0x3e) plen 28                                       #7 [hci0] 22.824706
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Random (0x01)
        Address: 54:B0:00:9A:91:70 (Resolvable)
        Data length: 16
        TX power: -9 dBm
        Service Data: Google (0xfe2c)
          Data:<PHONE_NUMBER>11b41464
        RSSI: -83 dBm (0xad)
> HCI Event: LE Meta Event (0x3e) plen 28                                       #8 [hci0] 22.825432
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Scan response - SCAN_RSP (0x04)
        Address type: Random (0x01)
        Address: 54:B0:00:9A:91:70 (Resolvable)
        Data length: 16
        Name (complete): ACTON III [LE]
        RSSI: -84 dBm (0xac)
@ MGMT Event: Device Found (0x0012) plen 46                               {0x0001} [hci0] 22.828137
        LE Address: 54:B0:00:9A:91:70 (Resolvable)
        RSSI: -84 dBm (0xac)
        Flags: 0x00000000
        Data length: 32
        TX power: -9 dBm
        Service Data: Google (0xfe2c)
          Data:<PHONE_NUMBER>11b41464
        Name (complete): ACTON III [LE]
> HCI Event: LE Meta Event (0x3e) plen 32                                       #9 [hci0] 22.831819
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Random (0x01)
        Address: C0:C6:5B:9D:20:64 (Static)
        Data length: 20
        Flags: 0x04
          BR/EDR Not Supported
        Company: Zound Industries International AB (1626)
          Data: 0800505e5c6bc61400
        16-bit Service UUIDs (partial): 1 entry
          Unknown (0xaa00)
        RSSI: -84 dBm (0xac)
> HCI Event: LE Meta Event (0x3e) plen 28                                      #10 [hci0] 22.833748
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Scan response - SCAN_RSP (0x04)
        Address type: Random (0x01)
        Address: C0:C6:5B:9D:20:64 (Static)
        Data length: 16
        Name (complete): ACTON III [LE]
        RSSI: -83 dBm (0xad)
@ MGMT Event: Device Found (0x0012) plen 50                               {0x0001} [hci0] 22.834270
        LE Address: C0:C6:5B:9D:20:64 (Static)
        RSSI: -83 dBm (0xad)
        Flags: 0x00000000
        Data length: 36
        Flags: 0x04
          BR/EDR Not Supported
        Company: Zound Industries International AB (1626)
          Data: 0800505e5c6bc61400
        16-bit Service UUIDs (partial): 1 entry
          Unknown (0xaa00)
        Name (complete): ACTON III [LE]
> HCI Event: LE Meta Event (0x3e) plen 30                                      #11 [hci0] 22.841379
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Public (0x00)
        Address: 04:CD:15:2A:8C:B6 (Silicon Laboratories)
        Data length: 18
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        Service Data: Xiaomi Inc. (0xfe95)
          Data: 1055641bc1b68c2a15cd04
        RSSI: -90 dBm (0xa6)
> HCI Event: LE Meta Event (0x3e) plen 12                                      #12 [hci0] 22.842058
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Scan response - SCAN_RSP (0x04)
        Address type: Public (0x00)
        Address: 04:CD:15:2A:8C:B6 (Silicon Laboratories)
        Data length: 0
        RSSI: 1 dBm (0x01)
@ MGMT Event: Device Found (0x0012) plen 32                               {0x0001} [hci0] 22.842126
        LE Address: 04:CD:15:2A:8C:B6 (Silicon Laboratories)
        RSSI: 1 dBm (0x01)
        Flags: 0x00000000
        Data length: 18
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        Service Data: Xiaomi Inc. (0xfe95)
          Data: 1055641bc1b68c2a15cd04
> HCI Event: LE Meta Event (0x3e) plen 15                                      #13 [hci0] 22.845229
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Public (0x00)
        Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Data length: 3
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        RSSI: -47 dBm (0xd1)
> HCI Event: LE Meta Event (0x3e) plen 28                                      #14 [hci0] 22.846014
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Scan response - SCAN_RSP (0x04)
        Address type: Public (0x00)
        Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Data length: 16
        Name (complete): NRF_BATTERY_01
        RSSI: -47 dBm (0xd1)
@ MGMT Event: Device Found (0x0012) plen 33                               {0x0001} [hci0] 22.846061
        LE Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        RSSI: -47 dBm (0xd1)
        Flags: 0x00000000
        Data length: 19
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        Name (complete): NRF_BATTERY_01
@ MGMT Command: Stop Discovery (0x0024) plen 1                            {0x0001} [hci0] 22.865936
        Address type: 0x06
          LE Public
          LE Random
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6                #15 [hci0] 22.866018
        Extended scan: Disabled (0x00)
        Filter duplicates: Disabled (0x00)
        Duration: 0 msec (0x0000)
        Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4                                    #16 [hci0] 22.867646
      LE Set Extended Scan Enable (0x08|0x0042) ncmd 5
        Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4                            {0x0001} [hci0] 22.867728
      Stop Discovery (0x0024) plen 1
        Status: Success (0x00)
        Address type: 0x06
          LE Public
          LE Random
@ MGMT Event: Discovering (0x0013) plen 2                                 {0x0001} [hci0] 22.867752
        Address type: 0x06
          LE Public
          LE Random
        Discovery: Disabled (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8            #17 [hci0] 22.994765
        Own address type: Public (0x00)
        Filter policy: Ignore not in accept list (0x01)
        PHYs: 0x01
        Entry 0: LE 1M
          Type: Passive (0x00)
          Interval: 60.000 msec (0x0060)
          Window: 60.000 msec (0x0060)
> HCI Event: Command Complete (0x0e) plen 4                                    #18 [hci0] 22.995845
      LE Set Extended Scan Parameters (0x08|0x0041) ncmd 5
        Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6                #19 [hci0] 22.995965
        Extended scan: Enabled (0x01)
        Filter duplicates: Enabled (0x01)
        Duration: 0 msec (0x0000)
        Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4                                    #20 [hci0] 22.996535
      LE Set Extended Scan Enable (0x08|0x0042) ncmd 5
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 15                                      #21 [hci0] 23.047680
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Public (0x00)
        Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Data length: 3
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        RSSI: -47 dBm (0xd1)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6                #22 [hci0] 23.047762
        Extended scan: Disabled (0x00)
        Filter duplicates: Disabled (0x00)
        Duration: 0 msec (0x0000)
        Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4                                    #23 [hci0] 23.049088
      LE Set Extended Scan Enable (0x08|0x0042) ncmd 5
        Status: Success (0x00)
< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26             #24 [hci0] 23.049156
        Filter policy: Accept list is not used (0x00)
        Own address type: Public (0x00)
        Peer address type: Public (0x00)
        Peer address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Initiating PHYs: 0x01
        Entry 0: LE 1M
          Scan interval: 60.000 msec (0x0060)
          Scan window: 60.000 msec (0x0060)
          Min connection interval: 30.00 msec (0x0018)
          Max connection interval: 50.00 msec (0x0028)
          Connection latency: 0 (0x0000)
          Supervision timeout: 420 msec (0x002a)
          Min connection length: 0.000 msec (0x0000)
          Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4                                      #25 [hci0] 23.049695
      LE Extended Create Connection (0x08|0x0043) ncmd 5
        Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 31                                      #26 [hci0] 23.149076
      LE Enhanced Connection Complete (0x0a)
        Status: Success (0x00)
        Handle: 7
        Role: Central (0x00)
        Peer address type: Public (0x00)
        Peer address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Local resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
        Peer resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
        Connection interval: 50.00 msec (0x0028)
        Connection latency: 0 (0x0000)
        Supervision timeout: 420 msec (0x002a)
        Central clock accuracy: 0x00
@ MGMT Event: Device Connected (0x000b) plen 16                           {0x0001} [hci0] 23.149132
        LE Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Flags: 0x00000000
        Data length: 3
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2               #27 [hci0] 23.149325
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
> HCI Event: LE Meta Event (0x3e) plen 4                                       #28 [hci0] 23.149900
      LE Channel Selection Algorithm (0x14)
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Algorithm: #1 (0x00)
> HCI Event: Command Status (0x0f) plen 4                                      #29 [hci0] 23.150706
      LE Read Remote Used Features (0x08|0x0016) ncmd 5
        Status: Success (0x00)
@ RAW Open: btmon (privileged) version 2.22                                      {0x0002} 23.158359
@ RAW Close: btmon                                                               {0x0002} 23.158396
> HCI Event: LE Meta Event (0x3e) plen 12                                      #30 [hci0] 23.244967
      LE Read Remote Used Features (0x04)
        Status: Success (0x00)
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Features: 0x0f 0x49 0x01 0x00 0x00 0x00 0x00 0x00
          LE Encryption
          Connection Parameter Request Procedure
          Extended Reject Indication
          Peripheral-initiated Features Exchange
          LE 2M PHY
          LE Coded PHY
          Channel Selection Algorithm #2
          Minimum Number of Used Channels Procedure
< ACL Data TX: Handle 7 flags 0x00 dlen 7                                      #31 [hci0] 23.252419
      ATT: Exchange MTU Request (0x02) len 2
        Client RX MTU: 517
> HCI Event: Number of Completed Packets (0x13) plen 5                         #32 [hci0] 23.294371
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 41 msec (41-41 msec ~41 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 7                                      #33 [hci0] 23.344380
      ATT: Exchange MTU Response (0x03) len 2
        Server RX MTU: 247
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #34 [hci0] 23.344796
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0001-0xffff
        Attribute type: Server Supported Features (0x2b3a)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #35 [hci0] 23.394387
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~45 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 9                                      #36 [hci0] 23.544408
      ATT: Error Response (0x01) len 4
        Read By Type Request (0x08)
        Handle: 0x0001
        Error: Attribute Not Found (0x0a)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #37 [hci0] 23.544785
      ATT: Read By Group Type Request (0x10) len 6
        Handle range: 0x0001-0xffff
        Attribute group type: Primary Service (0x2800)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #38 [hci0] 23.594404
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~47 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 18                                     #39 [hci0] 23.744549
      ATT: Read By Group Type Response (0x11) len 13
        Attribute data length: 6
        Attribute group list: 2 entries
        Handle range: 0x0001-0x0005
        UUID: Generic Access Profile (0x1800)
        Handle range: 0x0006-0x0009
        UUID: Generic Attribute Profile (0x1801)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #40 [hci0] 23.744926
      ATT: Read By Group Type Request (0x10) len 6
        Handle range: 0x000a-0xffff
        Attribute group type: Primary Service (0x2800)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #41 [hci0] 23.794388
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~48 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 26                                     #42 [hci0] 23.944661
      ATT: Read By Group Type Response (0x11) len 21
        Attribute data length: 20
        Attribute group list: 1 entry
        Handle range: 0x000a-0x0010
        UUID: Vendor specific (19b10000-e8f2-537e-4f6c-d104768a1214)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #43 [hci0] 23.945032
      ATT: Read By Group Type Request (0x10) len 6
        Handle range: 0x0011-0xffff
        Attribute group type: Primary Service (0x2800)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #44 [hci0] 23.994392
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~48 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 9                                      #45 [hci0] 24.144417
      ATT: Error Response (0x01) len 4
        Read By Group Type Request (0x10)
        Handle: 0x0011
        Error: Attribute Not Found (0x0a)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #46 [hci0] 24.144905
      ATT: Read By Group Type Request (0x10) len 6
        Handle range: 0x0001-0xffff
        Attribute group type: Secondary Service (0x2801)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #47 [hci0] 24.194406
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~49 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 9                                      #48 [hci0] 24.344432
      ATT: Error Response (0x01) len 4
        Read By Group Type Request (0x10)
        Handle: 0x0001
        Error: Attribute Not Found (0x0a)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #49 [hci0] 24.344811
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0001-0x0010
        Attribute type: Include (0x2802)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #50 [hci0] 24.394394
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~49 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 9                                      #51 [hci0] 24.544415
      ATT: Error Response (0x01) len 4
        Read By Type Request (0x08)
        Handle: 0x0001
        Error: Attribute Not Found (0x0a)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #52 [hci0] 24.544794
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0001-0x0010
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #53 [hci0] 24.594386
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~49 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 27                                     #54 [hci0] 24.744637
      ATT: Read By Type Response (0x09) len 22
        Attribute data length: 7
        Attribute data list: 3 entries
        Handle: 0x0002
        Value: 020300002a
            Properties: 0x02
              Read (0x02)
            Value Handle: 0x0003
            Value UUID: Device Name (0x2a00)
        Handle: 0x0004
        Value: 020500012a
            Properties: 0x02
              Read (0x02)
            Value Handle: 0x0005
            Value UUID: Appearance (0x2a01)
        Handle: 0x0007
        Value: 200800052a
            Properties: 0x20
              Indicate (0x20)
            Value Handle: 0x0008
            Value UUID: Service Changed (0x2a05)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #55 [hci0] 24.745009
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0008-0x0010
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #56 [hci0] 24.794408
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (41-49 msec ~49 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 27                                     #57 [hci0] 24.944626
> ACL Data RX: Handle 7 flags 0x01 dlen 21                                     #58 [hci0] 24.945275
      ATT: Read By Type Response (0x09) len 43
        Attribute data length: 21
        Attribute data list: 2 entries
        Handle: 0x000b
        Value: 1a0c0014128a7604d16c4f7e53f2e80100b119
            Properties: 0x1a
              Read (0x02)
              Write (0x08)
              Notify (0x10)
            Value Handle: 0x000c
            Value UUID: Vendor specific (19b10001-e8f2-537e-4f6c-d104768a1214)
        Handle: 0x000e
        Value: 120f0014128a7604d16c4f7e53f2e80200b119
            Properties: 0x12
              Read (0x02)
              Notify (0x10)
            Value Handle: 0x000f
            Value UUID: Vendor specific (19b10002-e8f2-537e-4f6c-d104768a1214)
< ACL Data TX: Handle 7 flags 0x00 dlen 11                                     #59 [hci0] 24.945638
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x000f-0x0010
        Attribute type: Characteristic (0x2803)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #60 [hci0] 24.994393
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 48 msec (41-49 msec ~49 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 9                                      #61 [hci0] 25.144412
      ATT: Error Response (0x01) len 4
        Read By Type Request (0x08)
        Handle: 0x000f
        Error: Attribute Not Found (0x0a)
< ACL Data TX: Handle 7 flags 0x00 dlen 9                                      #62 [hci0] 25.172611
      ATT: Write Request (0x12) len 4
        Handle: 0x0009 Type: Client Characteristic Configuration (0x2902)
        Value Handle: 0x0008 Type: Service Changed (0x2a05)
          Data: 0200
            Indication (0x02)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #63 [hci0] 25.194371
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 21 msec (21-49 msec ~35 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 5                                      #64 [hci0] 25.344357
      ATT: Write Response (0x13) len 0
< ACL Data TX: Handle 7 flags 0x00 dlen 7                                      #65 [hci0] 25.345641
      ATT: Read Request (0x0a) len 2
        Handle: 0x0003 Type: Device Name (0x2a00)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #66 [hci0] 25.394379
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 48 msec (21-49 msec ~42 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 12                                     #67 [hci0] 25.544456
      ATT: Read Response (0x0b) len 7
< ACL Data TX: Handle 7 flags 0x00 dlen 7                                      #68 [hci0] 25.544907
      ATT: Read Request (0x0a) len 2
        Handle: 0x0005 Type: Appearance (0x2a01)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #69 [hci0] 25.594359
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (21-49 msec ~45 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 7                                      #70 [hci0] 25.744389
      ATT: Read Response (0x0b) len 2
@ MGMT Command: Disconnect (0x0014) plen 7                                {0x0001} [hci0] 32.853461
        LE Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
< HCI Command: Disconnect (0x01|0x0006) plen 3                                 #71 [hci0] 32.853529
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Reason: Remote User Terminated Connection (0x13)
> HCI Event: Command Status (0x0f) plen 4                                      #72 [hci0] 32.856314
      Disconnect (0x01|0x0006) ncmd 5
        Status: Success (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4                                 #73 [hci0] 32.894392
        Status: Success (0x00)
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Reason: Remote User Terminated Connection (0x13)
@ MGMT Event: Command Complete (0x0001) plen 10                           {0x0001} [hci0] 32.894446
      Disconnect (0x0014) plen 7
        Status: Success (0x00)
        LE Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
gs 0x00 dlen 9                                      #62 [hci0] 25.172611
      ATT: Write Request (0x12) len 4
        Handle: 0x0009 Type: Client Characteristic Configuration (0x2902)
        Value Handle: 0x0008 Type: Service Changed (0x2a05)
          Data: 0200
            Indication (0x02)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #63 [hci0] 25.194371
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 21 msec (21-49 msec ~35 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 5                                      #64 [hci0] 25.344357
      ATT: Write Response (0x13) len 0
< ACL Data TX: Handle 7 flags 0x00 dlen 7                                      #65 [hci0] 25.345641
      ATT: Read Request (0x0a) len 2
        Handle: 0x0003 Type: Device Name (0x2a00)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #66 [hci0] 25.394379
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 48 msec (21-49 msec ~42 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 12                                     #67 [hci0] 25.544456
      ATT: Read Response (0x0b) len 7
< ACL Data TX: Handle 7 flags 0x00 dlen 7                                      #68 [hci0] 25.544907
      ATT: Read Request (0x0a) len 2
        Handle: 0x0005 Type: Appearance (0x2a01)
> HCI Event: Number of Completed Packets (0x13) plen 5                         #69 [hci0] 25.594359
        Num handles: 1
        Handle: 7 Address: F6:0C:C0:F5:66:52 (OUI F6-0C-C0)
        Count: 1
        Latency: 49 msec (21-49 msec ~45 msec)
> ACL Data RX: Handle 7 flags 0x02 dlen 7                                      #70 [hci0] 25.744389
      ATT: Read Response (0x0b) len 2


fill-in image properties when publishing an instance

The incus publish command allows setting image properties: description, name, os, release, serial, variant, which go into the image metadata.yaml file.
An example from an images:alpine/3.19 image:
properties:
  architecture: aarch64
  description: Alpinelinux 3.19 aarch64 (20240426_13:00)
  name: alpinelinux-3.19-aarch64-default-20240426_13:00
  os: alpinelinux
  release: "3.19"
  serial: "20240426_13:00"
  variant: default

When I use "incus publish" to create an image from an instance.  I typically set only the alias (which is not in metadata.yaml).
This causes the new image to have the same properties as the image that the instance was created from.  This was not a problem while I used images by alias.  But I recently tried to make a simplestreams image server from my images, and they were listed with misleading metadata.
Modify "lxops instance publish" so that it can set the image properties.  The "name" and "description" properties seem to have a certain structure that incorporates other properties (release, architecture, serial, variant).  Generate "name" and "description" automatically.
From the above properties, only "alpinelinux" needs to be specified, and it can default to the "os" of the original image.

I modifed the "lxops publish" command, and accidentally linked the commit to #25.

"incus publish" seems to use default properties if no properties are specified on the command line.
If any property is specified, then the unspecified properties are not set.
Modified "lxopso publish" to just pass arguments to "incus publish", without doing anything else.
Any scripts that use this should set all 7 properties:  architecture, os, release, variant, serial, name, description.


fix: fix filterable dropdown style bug and json schema form bug

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[x] Not that difficult

Type of Change

[ ] New feature
[x] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[ ] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[ ] Updated Storybook documents for component
[ ] Wrote test codes for composable, utils and etc.
[x] Tested with console(if usages are changed)

Description
Commit messages say it all
Things to Talk About

:tada: This PR is included in version 2.0.0-beta.15 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] Allow named layers and some Misc Fixes

Example
julia> c = Chain(feature_extractor=Chain(Dense(2, 3, relu), BatchNorm(3)),
                 classifier=Chain(Dense(3, 2)))
Chain(
    feature_extractor = Chain(
        layer_1 = Dense(2 => 3, relu),  # 9 parameters
        layer_2 = BatchNorm(3),         # 6 parameters, plus 7
    ),
    classifier = Dense(3 => 2),         # 8 parameters
)         # Total: 23 parameters,
          #        plus 7 states, summarysize 48 bytes.

Closing this since, most features have been pulled into different PRs (already in main). We still need to work on named layers for container types.


chore(lanes): merge main into feature branch

I had to manually merge #4058 because the iterator code has changed significantly (see this commit).

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments

Waiting for #4107 to be merged first on feature/mempool-qos.


Granular test skip on macOS Python 3.9

Changes
Instead of skipping all tests on macOS Python 3.9, skip just the ones that use asyncio PIPE
Types of changes
What types of changes does your code introduce?

[ ] Bugfix (a non-breaking change that fixes an issue)
[ ] New feature (a non-breaking change that adds functionality)
[ ] Breaking change (a change that causes existing functionality not to work as expected)
[ ] Optimization
[ ] Refactoring
[ ] Documentation update
[x] Build-related changes
[ ] Other: Description

The skipif currently doesn't work. Not quite sure why. I may need a print statement :sweat_smile:


Sendable checking for overrides

When an override means crossing an actor boundary, check Sendability of
parameters and results.

@swift-ci please smoke test

Superseded by https://github.com/apple/swift/pull/59086


Create karmoyskolen.txt

karmoyskolen.no is a shared domain for all schools in the Karmøy council of Rogaland, Norway.
All schools under it include Vormedal ungdomsskole, Åkra ungdomsskule, Ådland barnaskule, Mykje barneskole, Stangeland ungdomsskole, and more.

@Proximyst Pull request merged. Thank you!


new_geisha tweaks, notification proof of concept (training)

Special missions need test in dev environment before deploy to production.


TabSet.SetActivateTab should, maybe, be SetActiveTab

The TabSet's SetActivateTab method doesn't read how I'd expect. Should it be SetActiveTab?

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

ID: 7e7ba96d-bae0-96ee-e76a-71c6e5f4c23f
Version Independent ID: 5fe884b8-51e1-1b91-57f8-522ff0b7890c
Content: ASP.NET Core Blazor cascading values and parameters
Content Source: aspnetcore/blazor/components/cascading-values-and-parameters.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @serpent5 ... Possibly/probably so. I'll take a look at this on Monday -ish. I'm buried in localization updates on https://github.com/dotnet/AspNetCore.Docs/issues/18372 right through the weekend. ⛏⛰😅

Sure, no worries. I'm happy to patch it up if you like, but of course it's fine if not.

Sit tight, hold the fort and keep the home fires burning. And if I'm not back by Monday ... call the president.
       — Jack Burton (Kurt Russell), Big Trouble in Little China, ©1986 20th Century Fox

Well, I was too curious to wait for an investigation.
This goes way, way ... WAY back 👴. It's been like this since ancient Blazor times ... two years ago 😄. I don't recall naming it that way. I'm not sure if I had a reason or if another wonderful 🙈 find-'n-replace debacle 🙈 did this in ancient times.
Whatever the case, yeah! ... I think ur right @serpent5. Go ahead if you want to and fix it up. It should be in both the WASM and Server common sample apps. Fortunately, it's not in the text of the topic, so no changes needed there.

@guardrex Yeah, like you said in your most recent edit, the example works properly as it is. It probably wasn't worth reporting.

I think it's worth changing tho. It sounds funky like that. I'll take care of it.

Ok, sorry. I was more than happy to do it, but after your edit I didn't feel like it was really significant. Sorry about closing this, then. I will just leave you to take care of it now to save the back and forth.


Add tests

Put the use cases it works on the tests, to check them through all versions

Added the most basic tests, more to come :-) Thanks!