The value for 'DataContext' property is null when opening a window programmatically

I am trying to open a window programmatically like this:
        private void OpenSettings(Window win) {
            var sw = new SettingsWindow { DataContext = new SettingsViewModel() };
            sw.ShowDialog<bool>(win);
        }

However, when I run this, my application crashes with an XamlObjectWriterException where the message is The value for 'DataContext' property is null.
How do I open a window correctly?
EDIT: I changed this to be async like this:
        public MainWindowViewModel() {
            SettingsCommand = ReactiveCommand.Create<Window>(async win => await OpenSettings(win));
        }

        private async Task OpenSettings(Window win) {
            var sw = new SettingsWindow { DataContext = new SettingsViewModel() };
            await sw.ShowDialog<bool>(win);
        }

However, this only causes the application to not crash, the window doesn't open. I suppose it throws the exception silently.

Turned out that I had a typo in the Design.DataContext in the XAML file.

kys


Granule to STAC Item / Kerchunk Script

This adds a script for generating Kerchunk JSON references for an image pair granule, and from these a STAC item.
Usage:
python gran_to_cat.py /path/to/gran.nc

There is an optional --s3_path flag if processing a granule locally, but the included URLs in both JSON files will reference their S3 Path.

@jhkennedy I went and addressed most of your comments but regarding your issue I could use some additional information about your package versions (mainly kerchunk, h5py, and netCDF4) since after these changes my code still works in my environment.

@agoodm I included the listing of the environment in my comment (env_list.txt) which has the versions for every package in the environment.

@jhkennedy Sorry for missing that!
I was unable to track down which package is causing the inconsistency but I realized that my code should be more robust in handling this case anyway, so I made a quick change. Please try running it again with the latest commit.

This latest version now uses pathlib with your suggested changes. how does it look to you now?

This latest version now uses pathlib with your suggested changes. How does it look to you now?

@agoodm looks good!
I've finished my review of the stac item (below) and have a couple of questions about how you're using the refs.

kerchunk refs
@agoodm in the stac item, I don't see the entire refs encoded in the STAC item; are you just using the chunks, shape, and attrs for each variable in item['properties']['cube:variables'], or are you expecting to use the refs file (either directly off S3 or separately encoded in the catalog)?
Overall, it'd be good to know exactly what you intend to use from the STAC item.

stac item
I've reviewed the STAC item from a search and discovery standpoint since that's the primary purpose of the STAC catalog (e.g., facilitating the queries @betolink will need to do). I don't know enough about how you're using the STAC item, so some of these points may affect that.
Using this granule as the test again:
s3://its-live-data/velocity_image_pair/landsatOLI/v02/N70W040/LC08_L1GT_004010_20140206_20200912_02_T2_X_LC08_L1GT_004010_20140529_20200911_02_T2_G0120V02_P008.nc

I have a few comments/suggestions on the generated STAC item:

id shouldn't have the .nc extension
for the cube:dimensions property,

each dimension reference_system is a proj json object, but could just be the EPSG code: https://github.com/stac-extensions/datacube?tab=readme-ov-file#horizontal-spatial-raster-dimension-object
there's no description for the dimension, but I'm not sure if it is worth putting "x coordinate of projection in meters", so maybe that's fine

for the cube:variables property,

the mapping variable is missing, so the grid_mapping attribute doesn't really make sense to include in each variable
For these variables, I think we can drop attrs, shapes, and chunks entirely (they aren't in the cube extension spec) -- are they needed for your kerchunk work?

for the assets,

we should include the thumbnail and browse image
we should describe them a bit better by including the type, description, and title as well as the href: https://github.com/radiantearth/stac-spec/blob/master/commons/assets.md#asset-object
I think the asset key should be "data" so it's easy to select that asset for any item

we'll need a bunch more metadata,

most everything should be included from the img_pair_info variable as item properties
we'll need most of the information encoded in the variable name as well in the item properties
we'll need the ITS_LIVE datacube "tile" in the item properties
we'll need some of the global attributes in the item properties

I've edited the output stac item for how I'd like to see it:
LC08_L1GT_004010_20140206_20200912_02_T2_X_LC08_L1GT_004010_20140529_20200911_02_T2_G0120V02_P008.stac-joe.json
which results in this mini catalog using stac_geoparquet (zipped b/c GitHub):
its_live_mini_catalog.zip
But there are a few things there that may need to change. @betolink @alex-s-gardner @markf6  it'd be good for y'all to review my proposed STAC item as well. I've got a few open questions regarding the item:

[ ] Is the "roles" specifier for assets valuable? It's not required and the spec implies it's mostly for items with multiple data assets.
[ ] Are we happy with the item property names? There are some changes as compared to the netCDF metadata. The major one is:

[ ] In @betolink's db he uses sat1 and sat2, while in the netCDF granule we use img1 and img2. I've used reference and secondary as that's more common in the remote sensing/InSAR world (ref and sec could also work) and is more descriptive, I think.

[ ] Is there metadata in the granule I missed?

@agoodm I'm happy to make some (all?) of these changes myself -- do you want me to just push to your branch or open a PR to your branch, or do you want to handle all of it?

@agoodm I'm happy to make some (all?) of these changes myself -- do you want me to just push to your branch or open a PR to your branch, or do you want to handle all of it?

You can go ahead and apply these yourself, none of them should have any major impact with my planned virtual cubes work. As far as that is concerned the additional STAC metadata is primarily useful for potential ways to narrow down queries when arrow expands these into separate columns in the geoparquet. However we decided to keep the kerchunk JSON entirely separate for now since it is a bit cleaner without it and also easier and faster to decode later this way.


Payload serde-json support

This PR tackles #19 in a way that does not modify the build script.

I'll approve anyway, as code compiles without problems, so the comment is just aesthetic. Implementation looks good 👍

Hey guys, we really need this one in llm-chain <3

@TmLev thanks for your interest!
I propose you open a PR with your alternative design, it will be easier to discuss there and see how it fits into the library.


Add JSDoc comments to source

Working towards better documentation, I added JSDoc commentary throughout the source. In addition to being readable in situ, it compiles to HTML pretty cleanly.
While at it, I cleaned up the source in a couple of places, most visibly moving mparser = require('./message_parser') to be within MessageFormat._parse, and removing the _ prefixes of the runtime functions.
This could be left as is, or we could add jsdoc as a dependency, along with a suitable config file and a make rule. Here's the minimal conf.json I've been using so far:
{
  "source": { "include": [ "lib/messageformat.dev.js" ] },
  "plugins": [ "plugins/markdown" ]
}

Regarding the copyright statement, I went for now with "2012-2015 Alex Sexton and other contributors". Is that all right?

All of that sounds good and better. Add your name though. It's half your code now too.
"2012-2015 Alex Sexton, Eemeli Aro, and Contributors"

Wow, good job

I updated all the copyright statements that I could find to match the same pattern.
The Travis CI build is failing with odd errors in the dependencies for Node 0.8, is that a target we should still care about? I'm pretty sure none of the changes in this commit should be their cause.

Kill 0.8, add 0.12 -- and also maybe add some io.js love? http://docs.travis-ci.com/user/languages/javascript-with-nodejs/

Ah, 0.12 isn't on travis yet. so just add the io.js stuff, I guess.

(we could do 0.11 as a stopgap since the last 0.11 release is invariably the RC for 0.12)

As it turns out, the Travis CI documentation is outdated, and it does support 0.12. :)

Boom. This probably eventually warrants killing a lot of the README, and generating a github.io page, but let's take it in steps.

Aye, I agree. Now, should we include jsdoc as a dependency or not? I'd be tempted to put it in as a devDependency, and use it to generate API docs that could get hosted on the aforementioned Github Pages site.

Seems like a devDep to me.

I merged this, as we seem to be in agreement. I'll continue on the documentation & readme update when I can.


Memory leak in the library

Right now the library contains following code in the LwipImage destructor
// delete _cimg;

This code when uncommented produce unreliable test crashes on Windows.

Fixed in #182


Full support for Proxy-Authorization

Full support (for both CONNECT and full-url styles) for the Proxy-Authorization header and "Basic" authentication.

**Hello,
Thanks but i allways get:**

_http_client.js:53
    throw new TypeError('Request path contains unescaped characters');
    ^

TypeError: Request path contains unescaped characters

**I have read some post and googled and installed tunnel 0.0.4 but also same problem still exists
Hope you or someone can help me ?**


Sensors stop updating after HA restart?

I had to restart HA through the UI, and then noticed all my temperature/humidity sensors stopped updating. Going to integrations and clicking "reload" on the tuyav2 integration seemed to refresh them once, but now it's back at not updating. I checked through the official SmartLife app and they are still updating. Found this in the logs, if it helps? :

Thank you!

@philhzss  Can you provide more logs? It seems something wrong when integration receives sensors' data.

@tsutsuku  Do you know if I can find more details somewhere else? In the logs, its always the same thing as in the screenshot I sent. Sometimes though, it says "uncaught thread exception" instead of "task exception was never retrieved", but other than that it's always the same lines in the log, seems to happen every 2-3 hours (I guess every time the sensor tries to update)

Thank you!

@philhzss  from the terminal where you launch home assistant, you can find more logs.
Also, can you provide your sensor's device info from the logs?

Hi @tsutsuku , I found several entries in the terminal log and Im not sure which one could be useful to you, but here are some of them:
[tuya-openapi] Request: method = POST, url = https://openapi.tuyaus.com/v1.0/iot-01/associated-users/actions/authorized-login, params = None, body = {'username': 'xxxxxxxxxxxxxx', 'password': 'xxxxxxxxxxxxxxx', 'country_code': '1', 'schema': 'smartlife'}, headers = {'client_id': 'xxxxxxxxx', 'sign': 'xxxxxxxxx', 'sign_method': 'HMAC-SHA256', 'access_token': '', 't': '1623430023316', 'lang': 'en', 'dev_lang': 'python', 'dev_version': '0.1.1', 'dev_channel': 'hass'}
[tuya-openapi] Response: {
  "code": 2406,
  "msg": "skill id invalid",
  "success": false,
  "t":<PHONE_NUMBER>697
}

[tuya-openapi] Request: method = GET, url = https://openapi.tuyaus.com/v1.0/devices/eb825a593493013079gglx/functions, params = None, body = None, headers = {'client_id': 'xxxxxxxxxx', 'sign': 'xxxxxxxxxx', 'sign_method': 'HMAC-SHA256', 'access_token': 'xxxxxxxxxx', 't': '1623430394625', 'lang': 'en'}
[tuya-openapi] Response: {
  "code": 2009,
  "msg": "不支持此設備",
  "success": false,
  "t":<PHONE_NUMBER>696
}

[tuya-openapi] Response: {
  "result": [
    {
      "active_time":<PHONE_NUMBER>,
      "biz_type": 18,
      "category": "wsdcg",
      "create_time":<PHONE_NUMBER>,
      "icon": "smart/icon/ay1558597489826VMjh1/c78381c006bd14beaa408dca2ef9bb7d.png",
      "id": "eb825a593493013079gglx",
      "ip": "xxxx",
      "lat": "xxxx",
      "local_key": "xxxx",
      "lon": "xxxx",
      "name": "Basement temp",
      "online": true,
      "owner_id": "xxx",
      "product_id": "vvldcafpaiwnh3t3",
      "product_name": "Temperature Humidity Sensor",
      "status": [
        {
          "code": "va_temperature",
          "value": 213
        },
        {
          "code": "va_humidity",
          "value": 35
        },
        {
          "code": "battery_state",
          "value": "high"
        }
      ],
      "sub": false,
      "time_zone": "-04:00",
      "uid": "xxx",
      "update_time":<PHONE_NUMBER>,
      "uuid": "xxx"
    },

I also noticed that it seems the sensors are updating now, but really randomly and not often, for example one of my thermometers will update every 6-7 hours, another one takes 22 + hours to update, etc.

@philhzss Try the v1.3.

@tsutsuku  Ok just installed it, will let you know in a few days if they get stuck again! Thanks

@tsutsuku
So it's weird, they do update but not very often. For example right now, one of my sensors updated 4 hours ago, another 8 hours ago, another 11 hours ago and one of them 14 hours ago. However if I open smart life app, they all updated less than 1 hour ago.
So it's strange that Home Assistant and this integration isn't updating as often as the sensor is?? Using 1.3.1 right now

Ok, now it seems they have updated within the last 1 to 6 hours. So even the ones that are stuck eventually update.


Fail if no RPCO release version set

Do NOT include any confidential information, this issue will be created on a public repo
This section is completed by the issue reporter
On which version(s) do you encounter this issue?
Please provide the output to 'git describe --all' for  all deployments where you have confirmed it occurs.
heads/master
What type of issue is this? Please tick the appropriate box.

[ ] bug - existing functionality that does not work for you as documented
[x] feature - new functionality that you would like to see added

What is the expected behavior?
If the release version cannot be discovered, the RPCO playbooks should fail.
What is actually happening?
What currently happens is that the variable rpc_release gets set to 'UNKNOWN_RELEASE' if not the version is not discovered. Given that this should always be known it would be better to fail.
What were you attempting to do when you encountered this error (give as much detail as possible)?
This was spotted as part of some MaaS work for Mitaka https://github.com/rcbops/u-suk-dev/issues/397
How can we reproduce this issue?
Once the fix for https://github.com/rcbops/u-suk-dev/issues/397 merges there should be nothing known that causes this issue on master. A test playbook that prints rpc_release should be sufficient to test this.
How can we verify your issue is addressed?
Attempting to use rpc_release when version has not been discovered fails.
If you are using or know of a workaround please describe the necessary steps?
There are no known breaking failures due to this, the workaround would depend on the failure.
What is your evaluation on the importance of this issue, and why?
While there are no know problems caused by this when the defined deployment/upgrade path is used it has the potential to cause unpredictable failures and so a prio-2 seems most reasonable.
This section is completed during the issue resolution process. If you are reporting an issue, please do not modify the section below.
Which branches are impacted by this issue?
Remove branches that are not impacted.
For each pull request, update the branch line to reference it.

[ ] master
[ ] mitaka-13.0
[ ] liberty-12.2
[ ] kilo

Upgrade impact. Consider the impact on moving between major, minor and patch releases.

[ ] This change does not impact upgrades
[ ] This change addresses a potential upgrade impact
[ ] The upgrade impact is being tracked by another issue.

The issue tracking the upgrade impact is:
Testing impact

[ ] An issue/pull-request has been create or exists to track the testing gap, and is referenced below
[ ] This change includes additional testing
[ ] This change is tested by the existing setup

Additional testing links:
Release note

[ ] This change includes a release note.
[ ] This change does not require a release note.

Doc Impact
Does your change require documentation?

[ ] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[ ] No documentation required for this change

Additional documentation links (please add links if you have ticked yes):

Speaking of this, would it be better to just hardcode the release into the code itself, like we do in [1]?  The upside being that we don't need different bits of code trying to auto-discover this, while the downside being that the release manager would have to keep this updated when new branches, etc. are created.  Thoughts?
[1] https://github.com/openstack/openstack-ansible/blob/stable/mitaka/playbooks/inventory/group_vars/all.yml#L17

I think it's better to have a script to bump version too.
This script could bump osa submodule sha, consuming roles sha (like ceph), change the appropriate version numbers, etc.
In the meantime, we can just ensure failures to avoid silent issues later.

So not looking to blame anyone but I am looking for more context around why this work was completed. I see @cloader89 merged the issue based on some work by @major and @evrardjp, but as @git-harry mentioned, this has not been approved for work. Is there a specific customer drive or need that needs to be triaged or addressed? Thanks.

No, I will take the blame here, I was just reviewing items in the PR list. I should have communicated with @evrardjp and I will revert it if necessary.

@cloader89 Again, not looking to blame here just want a reason to make this work official or not. Just make sure that future work has been approved so that we can put our limited capacity to the things that are deemed important.
@git-harry At this point, do we want to make this official and get this backported to the specific versions that need it? cc: @alextricity25

@git-harry Let's pull this is at next week's replenishment meeting.


Update Java SDK + refactor public API

Hi @wensheng! First of all, thank you for your work.
Library is not updated in a while, so I would like to contribute changes that were done by our team while using it.
Summary of changes

Updated Hedera Java SDK submodule to latest version + added patch for new .kts scripts
Refactored public API

Added dynamic __all__ property for generated code and package root
Exposed additional "standard" Java autoclasses (JInstant,  JDuration)

@Reccetech, @dmueller2001 FYI ^


[Feedback 0.35.0-RC]: Are GATT-related exceptions deprecated?

With 0.34.0, there was a need of catching more exceptions than the ones documented, for example we have the following cases:
Peripheral.connect
catch (e: GattRequestRejectedException) {
    ...
} catch (e: GattStatusException) {
    ...
}

Peripheral.write
} catch (e: GattWriteException) {
    ...
} catch (e: GattRequestRejectedException) {
    ...
} catch (e: GattStatusException) {
    ...
}

My question is, I read in the release version the following:

In general, you should now only ever need to catch IOException when calling Kable functions, all other exceptions should be considered programming error (could've been prevented by pre-checking conditions). Pre-conditions that could change between a check and call are thrown as IOExceptions.

Does that means that we no longer have to catch the above exceptions?

Does that means that we no longer have to catch the above exceptions?

That is correct, you should only need to catch IOException. This is because the exception hierarchy was unified/commonized (if specific failure exceptions are thrown, they'll be sub-classes of either IOException or IllegalStateException). Whereas, you could let IllegalStateException crash the app (to capture it via your app crash reporting tool), as all IllegalStateExceptions should be preventable (e.g. thrown because BLE is unsupported, which could've been checked before making the call).
Regarding your examples specifically:
try {
    peripheral.connect()
} catch (e: GattRequestRejectedException) {
    ...
} catch (e: GattStatusException) {
    ...
}

With the above exceptions, your course of action does not differ based on which exception was thrown. With either exception, you can either abort the the connection process, or try again. There is no need to have unique logic based on the specific failure.  You just need to know if connect succeeded (no exception) or failed (IOException).
try {
    peripheral.write(..)
} catch (e: GattWriteException) {
    ...
} catch (e: GattRequestRejectedException) {
    ...
} catch (e: GattStatusException) {
    ...
}

Again, you're not going to need unique logic based on which of the above exceptions was thrown, instead, we can now just catch IOException to know that write did not succeed, and either inform the user, or try again.
The major benefit, is that IOException is common (whereas many of the exceptions in the examples above were platform specific), so we can now write I/O code and corresponding error handling in common source set.
Definitely let me know though, if there are use-cases where unique logic was actually needed based on the specific failure case.

Does that means that we no longer have to catch the above exceptions?

That is correct, you should only need to catch IOException. This is because the exception hierarchy was unified/commonized (if specific failure exceptions are thrown, they'll be sub-classes of either IOException or IllegalStateException). Whereas, you could let IllegalStateException crash the app (to capture it via your app crash reporting tool), as all IllegalStateExceptions should be preventable (e.g. thrown because BLE is unsupported, which could've been checked before making the call) so it is likely a programming error that should/can be fixed/prevented.
Regarding your examples specifically:
try {
    peripheral.connect()
} catch (e: GattRequestRejectedException) {
    ...
} catch (e: GattStatusException) {
    ...
}

With the above exceptions, your course of action does not differ based on which exception was thrown. With either exception, you can either abort the the connection process, or try again. There is no need to have unique logic based on the specific failure. You just need to know if connect succeeded (no exception) or failed (IOException).
try {
    peripheral.write(..)
} catch (e: GattWriteException) {
    ...
} catch (e: GattRequestRejectedException) {
    ...
} catch (e: GattStatusException) {
    ...
}

Again, you're not going to need unique logic based on which of the above exceptions was thrown, instead, we can now just catch IOException to know that write did not succeed, and either inform the user, or try again.
The major benefit, is that IOException is common (whereas many of the exceptions in the examples above were platform specific), so we can now write I/O code and corresponding error handling in common source set.
Definitely let me know though, if there are use-cases where unique logic was actually needed based on a specific failure case(s).

I see, yes these are some valid points and currently as you said we don't take different actions based on "Gatt-related exceptions", so having to catch only IOException definitely helps in having cleaner code.
Thanks, I'm closing this issue as my question is answered and we don't need to "confuse" anyone who might think there is a real issue here.


DNSProviders cannot handle Certification Authority Authorization (CAA) records

Summary
Libcloud DNSProviders cannot handle Certification Authority Authorization (CAA) records
Detailed Information
First I manage a dns zone with CAA records in it.
Reproducer:
 #!/usr/bin/env python

from libcloud.dns.providers import get_driver as get_dns_driver
from libcloud.dns.types import Provider as DNSProvider

import os

cls = get_dns_driver(DNSProvider.GANDI_LIVE)
driver = cls(os.getenv('TOKEN'))

for zone in driver.list_zones():
  for record in zone.list_records():
    print(record)

Produces this issue:
./caa.py
Traceback (most recent call last):
  File "./caa.py", line 12, in <module>
    for record in zone.list_records():
  File "/home/petter/caa/venv/lib/python3.8/site-packages/libcloud/dns/base.py", line 81, in list_records
    return self.driver.list_records(zone=self)
  File "/home/petter/caa/venv/lib/python3.8/site-packages/libcloud/dns/drivers/gandi_live.py", line 136, in list_records
    return self._to_records(records.object, zone)
  File "/home/petter/caa/venv/lib/python3.8/site-packages/libcloud/dns/drivers/gandi_live.py", line 434, in _to_records
    records += self._to_record(r, zone)
  File "/home/petter/caa/venv/lib/python3.8/site-packages/libcloud/dns/drivers/gandi_live.py", line 388, in _to_record
    record = self._to_record_sub(data, zone, rrset_value)
  File "/home/petter/caa/venv/lib/python3.8/site-packages/libcloud/dns/drivers/gandi_live.py", line 424, in _to_record_sub
    type=self._string_to_record_type(data['rrset_type']),
  File "/home/petter/caa/venv/lib/python3.8/site-packages/libcloud/dns/base.py", line 584, in _string_to_record_type
    record_type = getattr(RecordType, string)

And indeed, CAA record is missing from RecordType class. I don't know how much more work it'd be to add support for this one, aside from adding it to the RecordType class. Anyhow creating a bug report seemed to be a prudent first step.

Yeah, most likely just adding it to the base RecordType enum class + GANGI_LIVE (https://github.com/apache/libcloud/blob/trunk/libcloud/dns/drivers/gandi.py#L90) provider should do the trick.
But you might also need to utilize extra dictionary in case you want to manage all the tags (issue, issuewild, iodef).
For simplicity / ease of use, we should likely default tag to issue if only value is provided, but extra['tag'] is not.

#1464 should do it.
I only tested and implemented it for the CloudFlare and Gandi Live driver.
Other drivers will likely also require some minor modifications to make them support CAA record type.

neat!


HDFS-17292. Show the number of times the slowPeerCollectorDaemon thread has collected SlowNodes.

Description of PR
JIRA: HDFS-17292. Show the number of times the slowPeerCollectorDaemon thread has collected SlowNodes.

Add a new metric of the number of times the DatanodeManager#slowPeerCollectorDaemon thread collects SlowNodes, and display it in a map structure.
The same SlowNode may always appear in the prod env, so when slowPeerCollectorDaemon is turned on, record the number of times it has been collected by the slowPeerCollectorDaemon thread. If the collection frequency is too high, SRE or DEV need to repair the machine.
The following figure shows the number of write request threads(DataNodeWriteXceiversCount) for SlowNodes collected by the slowPeerCollectorDaemon thread at different time periods.
(If "DataNodeWriteXceiversCount" is 0, there is no write request, indicating a SlowNode)
The legend above shows that the same node was collected three times by the slowPeerCollectorDaemon thread. The network latency will decrease because there are no write requests after being collected. After a period of time, there will be new write requests, and after writing for a period of time, they will be collected as SlowNode again.

How was this patch tested?
Add Unit Test.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
12m 14s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 16s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 31s

trunk passed

+1 :green_heart:
compile
5m 26s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m 16s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 23s

trunk passed

+1 :green_heart:
mvnsite
2m  1s

trunk passed

+1 :green_heart:
javadoc
1m 43s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  8s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 32s

trunk passed

+1 :green_heart:
shadedclient
32m 37s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 42s

the patch passed

+1 :green_heart:
compile
5m 16s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 16s

the patch passed

+1 :green_heart:
compile
5m  4s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m  4s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 12s

the patch passed

+1 :green_heart:
mvnsite
1m 49s

the patch passed

+1 :green_heart:
javadoc
1m 23s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 52s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 36s

the patch passed

+1 :green_heart:
shadedclient
32m 20s

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

_ Other Tests _

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

+1 :green_heart:
unit
21m 58s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

409m 22s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

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

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

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

uname
Linux bb937227289f 5.15.0-86-generic #96-Ubuntu SMP Wed Sep 20 08:23:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / cbebf02945d70310cb8afdc21eb78211bff6fb90

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/1/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 57s

trunk passed

+1 :green_heart:
compile
5m 28s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m  9s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 22s

trunk passed

+1 :green_heart:
mvnsite
2m  1s

trunk passed

+1 :green_heart:
javadoc
1m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 12s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 32s

trunk passed

+1 :green_heart:
shadedclient
32m 49s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 41s

the patch passed

+1 :green_heart:
compile
5m 19s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 19s

the patch passed

+1 :green_heart:
compile
5m  5s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m  5s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 12s

the patch passed

+1 :green_heart:
mvnsite
1m 45s

the patch passed

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 52s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 37s

the patch passed

+1 :green_heart:
shadedclient
33m 48s

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

_ Other Tests _

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

+1 :green_heart:
unit
21m 59s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

402m  0s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

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

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

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

uname
Linux 7c595286f429 5.15.0-86-generic #96-Ubuntu SMP Wed Sep 20 08:23:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / aaa2dee8eb8a162eed390f963d0a086168b3ff45

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/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.

Hi @ayushtkn, Please help review this pr when you are available, Thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 18s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
36m 50s

trunk passed

+1 :green_heart:
compile
6m  8s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m 53s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 32s

trunk passed

+1 :green_heart:
mvnsite
2m  4s

trunk passed

+1 :green_heart:
javadoc
1m 44s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  5s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 39s

trunk passed

+1 :green_heart:
shadedclient
39m 51s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 41s

the patch passed

+1 :green_heart:
compile
5m 58s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 58s

the patch passed

+1 :green_heart:
compile
5m 51s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m 51s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 18s

the patch passed

+1 :green_heart:
mvnsite
1m 47s

the patch passed

+1 :green_heart:
javadoc
1m 27s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 52s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 45s

the patch passed

+1 :green_heart:
shadedclient
38m 27s

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

_ Other Tests _

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

+1 :green_heart:
unit
23m 22s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

450m 22s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

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

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

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

uname
Linux d7afeccbfbfd 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 21fced341c2b1af22c668d9d3270fc1f5346841e

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m  0s

Docker mode activated.

-1 :x:
patch
0m 20s

https://github.com/apache/hadoop/pull/6364 does not apply to trunk. Rebase required? Wrong Branch? See https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute for help.

Subsystem
Report/Notes

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/4/console

versions
git=2.34.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 51s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 44s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
35m 30s

trunk passed

+1 :green_heart:
compile
6m  4s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m 48s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 27s

trunk passed

+1 :green_heart:
mvnsite
2m  3s

trunk passed

+1 :green_heart:
javadoc
1m 45s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 10s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 35s

trunk passed

+1 :green_heart:
shadedclient
37m 48s

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

-0 :warning:
patch
38m  9s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 43s

the patch passed

+1 :green_heart:
compile
5m 56s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 56s

the patch passed

+1 :green_heart:
compile
5m 47s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m 47s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 22s

the patch passed

+1 :green_heart:
mvnsite
1m 47s

the patch passed

+1 :green_heart:
javadoc
1m 26s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 53s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 43s

the patch passed

+1 :green_heart:
shadedclient
37m 58s

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

_ Other Tests _

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

+1 :green_heart:
unit
23m  5s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

454m  6s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/5/artifact/out/Dockerfile

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

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

uname
Linux 7dc127800ea0 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c9654cd4f91559e069e10513a2b92ca812556499

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/5/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/5/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

+0 :ok:
reexec
11m 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  1s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 18s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
32m 12s

trunk passed

+1 :green_heart:
compile
5m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m 26s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 26s

trunk passed

+1 :green_heart:
mvnsite
2m  6s

trunk passed

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 13s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 44s

trunk passed

+1 :green_heart:
shadedclient
34m 51s

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

-0 :warning:
patch
35m 12s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 30s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 48s

the patch passed

+1 :green_heart:
compile
5m 16s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 16s

the patch passed

+1 :green_heart:
compile
5m 23s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m 23s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

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

+1 :green_heart:
mvnsite
1m 49s

the patch passed

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 56s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 57s

the patch passed

+1 :green_heart:
shadedclient
33m 51s

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

_ Other Tests _

+1 :green_heart:
unit
211m 28s

hadoop-hdfs in the patch passed.

+1 :green_heart:
unit
22m 32s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

413m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/6/artifact/out/Dockerfile

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

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

uname
Linux 9b840dac70f1 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 77430991fd4fabe34db17fe33bf4608de9e99c74

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/6/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/6/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.

repush a complete PR.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 33s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
31m 30s

trunk passed

+1 :green_heart:
compile
5m 42s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
6m  4s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 22s

trunk passed

+1 :green_heart:
mvnsite
1m 58s

trunk passed

+1 :green_heart:
javadoc
1m 36s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 10s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 39s

trunk passed

+1 :green_heart:
shadedclient
36m 53s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 51s

the patch passed

+1 :green_heart:
compile
5m 52s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 52s

the patch passed

+1 :green_heart:
compile
5m 55s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m 55s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 15s

the patch passed

+1 :green_heart:
mvnsite
1m 48s

the patch passed

+1 :green_heart:
javadoc
1m 23s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 54s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
5m  2s

the patch passed

+1 :green_heart:
shadedclient
37m 24s

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

_ Other Tests _

+1 :green_heart:
unit
212m  4s

hadoop-hdfs in the patch passed.

+1 :green_heart:
unit
22m  8s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

409m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/7/artifact/out/Dockerfile

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

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

uname
Linux 26286a49a545 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / e3fb4883e6f03da8d7cd22062eb88b83e7194d6e

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/7/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/7/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.

Hi! @ayushtkn @slfan1989 @tomscut,I have repushed this PR, Please help review this pr when you are available. Thanks very much.

@huangzhaobo99 Thanks for the contribution! LGTM. let me wait for other partners' suggestions.
For other partners, it may be the holidays and we need some patience.

@huangzhaobo99 Thanks for the contribution! LGTM. let's wait for other partners' suggestions. For other partners, it may be the holidays and we need some patience.

@slfan1989 Thanks for your review, waiting for them to return from vacation.

Optimize UT

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 29s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 15s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m  9s

trunk passed

+1 :green_heart:
compile
6m 31s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
6m  3s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 24s

trunk passed

+1 :green_heart:
mvnsite
2m  7s

trunk passed

+1 :green_heart:
javadoc
1m 45s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  9s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

-1 :x:
spotbugs
3m 28s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-warnings.html
hadoop-hdfs-project/hadoop-hdfs in trunk has 1 extant spotbugs warnings.

+1 :green_heart:
shadedclient
33m  1s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 45s

the patch passed

+1 :green_heart:
compile
6m 14s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
6m 14s

the patch passed

+1 :green_heart:
compile
6m  2s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
6m  2s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 17s

the patch passed

+1 :green_heart:
mvnsite
1m 55s

the patch passed

+1 :green_heart:
javadoc
1m 26s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  0s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
5m  6s

the patch passed

+1 :green_heart:
shadedclient
32m 21s

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

_ Other Tests _

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

+1 :green_heart:
unit
22m 41s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

408m 20s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestReconstructStripedFile

hadoop.hdfs.TestErasureCodingPolicyWithSnapshotWithRandomECPolicy

hadoop.hdfs.TestDecommissionWithStriped

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/10/artifact/out/Dockerfile

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

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

uname
Linux 0882e415bbfe 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8a3756bba5e0600e7baba24f56e2a728214f8666

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/10/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 55s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 15s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
31m 17s

trunk passed

+1 :green_heart:
compile
5m 56s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
6m 12s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 49s

trunk passed

+1 :green_heart:
mvnsite
2m  9s

trunk passed

+1 :green_heart:
javadoc
1m 43s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  9s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

-1 :x:
spotbugs
3m 29s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-warnings.html
hadoop-hdfs-project/hadoop-hdfs in trunk has 1 extant spotbugs warnings.

+1 :green_heart:
shadedclient
33m 30s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 47s

the patch passed

+1 :green_heart:
compile
6m  8s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
6m  8s

the patch passed

+1 :green_heart:
compile
6m 10s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
6m 10s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 34s

the patch passed

+1 :green_heart:
mvnsite
1m 50s

the patch passed

+1 :green_heart:
javadoc
1m 23s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 59s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 59s

the patch passed

+1 :green_heart:
shadedclient
33m  9s

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

_ Other Tests _

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

+1 :green_heart:
unit
22m 34s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

418m 29s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestReconstructStripedFile

hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.TestDecommissionWithStriped

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/9/artifact/out/Dockerfile

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

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

uname
Linux 1876975cf958 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8a3756bba5e0600e7baba24f56e2a728214f8666

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/9/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/9/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m  4s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
36m 25s

trunk passed

+1 :green_heart:
compile
6m  3s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m 43s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 28s

trunk passed

+1 :green_heart:
mvnsite
2m  2s

trunk passed

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  7s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

-1 :x:
spotbugs
3m 21s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-warnings.html
hadoop-hdfs-project/hadoop-hdfs in trunk has 1 extant spotbugs warnings.

+1 :green_heart:
shadedclient
37m 45s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 43s

the patch passed

+1 :green_heart:
compile
5m 58s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 58s

the patch passed

+1 :green_heart:
compile
5m 47s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m 47s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 17s

the patch passed

+1 :green_heart:
mvnsite
1m 45s

the patch passed

+1 :green_heart:
javadoc
1m 27s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 55s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 43s

the patch passed

+1 :green_heart:
shadedclient
38m  9s

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

_ Other Tests _

+1 :green_heart:
unit
246m 14s

hadoop-hdfs in the patch passed.

+1 :green_heart:
unit
22m 53s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

450m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/8/artifact/out/Dockerfile

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

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

uname
Linux ba7b62d432dc 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8a3756bba5e0600e7baba24f56e2a728214f8666

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/8/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/8/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 30s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 39s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 57s

trunk passed

+1 :green_heart:
compile
5m 24s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m 14s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 22s

trunk passed

+1 :green_heart:
mvnsite
2m  3s

trunk passed

+1 :green_heart:
javadoc
1m 42s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  8s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

-1 :x:
spotbugs
3m 14s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-warnings.html
hadoop-hdfs-project/hadoop-hdfs in trunk has 1 extant spotbugs warnings.

+1 :green_heart:
shadedclient
33m  9s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 30s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 43s

the patch passed

+1 :green_heart:
compile
5m 35s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 35s

the patch passed

+1 :green_heart:
compile
5m 17s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m 17s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 11s

the patch passed

+1 :green_heart:
mvnsite
1m 46s

the patch passed

+1 :green_heart:
javadoc
1m 20s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 50s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 38s

the patch passed

+1 :green_heart:
shadedclient
34m 45s

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

_ Other Tests _

+1 :green_heart:
unit
211m  9s

hadoop-hdfs in the patch passed.

+1 :green_heart:
unit
21m 45s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

398m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/11/artifact/out/Dockerfile

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

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

uname
Linux c50a77a17dbd 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 141ce0b6eb9c83f6a5c1f3a0c87397f01123e7aa

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/11/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/11/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
11m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 47s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 58s

trunk passed

+1 :green_heart:
compile
5m 24s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
5m 10s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
1m 23s

trunk passed

+1 :green_heart:
mvnsite
2m  1s

trunk passed

+1 :green_heart:
javadoc
1m 41s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 11s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 26s

trunk passed

+1 :green_heart:
shadedclient
32m 34s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 39s

the patch passed

+1 :green_heart:
compile
5m 16s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
5m 16s

the patch passed

+1 :green_heart:
compile
5m  5s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
5m  5s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

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

+1 :green_heart:
mvnsite
1m 45s

the patch passed

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 58s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 33s

the patch passed

+1 :green_heart:
shadedclient
32m 38s

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

_ Other Tests _

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

+1 :green_heart:
unit
22m 11s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

418m 32s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/12/artifact/out/Dockerfile

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

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

uname
Linux 0c25b2b539f7 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 4d5d50144572e8eb3b6e356bde203d89f2fbe486

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/12/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6364/12/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.


DEV: Switch to new API to render into plugin outlet

Why this change?
The renderInOutlet plugin API was introduced in Discourse core which
we will prefer to use going forward.

Thank you again @martin-brennan :+1:


boostrap 4 template fade in issue

bootstrap 4 uses show css class to display elements, instead of in class.
when you fix this issue?

Meanwhile there is a simple fix for those who are looking for one : https://stackoverflow.com/questions/42249722/how-to-update-blueimp-jquery-file-upload-to-use-bootstrap-4#48162651

Thanks for the report @SalehGladius and thanks for providing an alternative solution @titulebolide.
The latest version of blueimp-file-upload (10.4.0) now provides a showElementClass option that can be set to show for use with Bootstrap 4.


Enable Share URL option

Would be nice to be able to share the linear configuration across different project. Currently we need to add for every project.

Thanks for raising the issue. I'm looking for some help and would love to have some contributions. Let me know if you are interested to implement this feature.

Would love to help, I don't have a lot of time nor experience with this language but will try look into it. If you have any pointers would be awesome, otherwise will try to look into documentation before the end of the month.

No worries! I also didn't know anything about plugin development but Jakub Chrzanowski and Mikhail Golubev from Jetbrains helped me get started. They pointed me to some great references. You can check them in the thread on Youtrack https://youtrack.jetbrains.com/issue/IDEA-265362.

@umbertix I think this is fixed in v1.0.0-alpha03. Can you please install the latest version of the plugin and verify the fix, please?

It is working, that's fantastic. Thanks a lot :), will close the issue


Demo readme file has un-useful information.

Describe the bug
The file: https://github.com/aws/amazon-freertos/blob/release-1.5/demos/README.md
Please remove the following from the file because it suggests duplicate ways of doing the same thing. The "make flash" is especially harmful becuase this is the legacy method of building and it sets the expectation that other legacy commands work, but they do not. Specifically "make flash monitor" and "make erase_flash" do not work.
This creates unnecessary friction for the customer to adopt to the latest version of AmazonFreeRTOS.

Hello,
Make flash is a supported command so it has its place in the readme.
The purpose is to give users a list of what is supported and what can be used.
Hugues


[PE-D] Inconsistency between documentation and application for editing a player's tags

Summary
The documentation mentions that editing a player can be done with the syntax [T/TAGS], however, when this is input in the application, it is invalid. Is this a typo where it is supposed to be [t/TAG]?
Screenshot
Documentation:

Labels: type.FunctionalityBug severity.Low
original: sbhbenjamin/ped#15

duplicate #237


Some content doesn't download properly

Example: https://www.fakku.net/hentai/cat-studio-r18-part-1-english
For some reason it gets the wrong width and height for these pages.
If I remove (comment) the block then it grabs the whole image but it is getting more canvas than it should (because it isn't resizing anymore).  The image sizes it detects for the pages is 300x150 for the cover and 300x424 for the other pages.
If I load the doujin in a normal login session it gives appropriate data that I'd expect.
Platform: Windows 11
Python: 3.10.5
ChromeDriver 110.0.5481.77

After some digging replacing
                        width = self.browser.execute_script(
                            f"return document.getElementsByTagName('canvas')[{n-2}].width"
                        )
                        height = self.browser.execute_script(
                            f"return document.getElementsByTagName('canvas')[{n-2}].height"
                        )

With
                        width = self.browser.execute_script(
                            f"return document.getElementsByClassName('layer')[{n-2}].firstChild.width"
                        )
                        height = self.browser.execute_script(
                            f"return document.getElementsByClassName('layer')[{n-2}].firstChild.height"
                        )

in downloader.py may be viable.  Currently testing but it seems to work.  When looking in Firefox (and Chrome) the former gave the values for the wrong element for some reason (not your scripts fault!) but the latter seemed to give the correct size.  You may know better than me on this.

May be the same issue as #13 but hard to say since they indicate it is random.  I was able to reproduce consistently.


Is "with-custom-font" example monorepo missing <SafeArea> provider?

I noticed this difference between two of the example monorepos.
I'm not sure if <Dripsy> provides <SafeArea>.

"with-custom-font"
https://github.com/nandorojo/solito/blob/master/example-monorepos/with-custom-font/packages/app/provider/index.tsx
import { Dripsy } from './dripsy'
import { NavigationProvider } from './navigation'

export function Provider({ children }: { children: React.ReactNode }) {
  return (
    <NavigationProvider>
      <Dripsy>{children}</Dripsy>
    </NavigationProvider>
  )
}

vs.
"with-tailwind"
https://github.com/nandorojo/solito/blob/master/example-monorepos/with-tailwind/packages/app/provider/index.tsx#L6-L8
import { NavigationProvider } from './navigation'
import { SafeArea } from './safe-area'

export function Provider({ children }: { children: React.ReactNode }) {
  return (
    <SafeArea>
      <NavigationProvider>{children}</NavigationProvider>
    </SafeArea>
  )
}

Should it be something like the following??
import { NavigationProvider } from "./navigation";
import { SafeArea } from "./safe-area";
import { Dripsy } from "./dripsy";

export function Provider({ children }: { children: React.ReactNode }) {
  return (
    <SafeArea>
      <NavigationProvider>
        <Dripsy>{children}</Dripsy>
      </NavigationProvider>
    </SafeArea>
  )
}

yeah you can do that. with custom font is more for showing how it’s done, less of a complete starter. will probably move it elsewhere.


My anime list error 401

Steps to reproduce
Try adding a manga/anime to anime list
Realise you can't
Expected behavior
Try adding a manga/anime to anime list
It works
Actual behavior
When trying to add the media MAL responds with a 401 error code
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 14
Device
Samsung galaxy A34 5G ; SM-A346B/DSN
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extension's repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Log out and back in.


evaluate alternate detrending method

In light of a reviewer's concerns, we have resolved to detrend all chronologies with a 50-year fixed width spline. Neil will detrend a few example species, and we will then evaluate whether it makes a difference.

50-year spline ARTSAN files are now added within the LITU, QUAL, and FAGR folders here.
@ValentineHerr , let's run a comparison of the results we get this way compared to the previous detrending method. At this point, the goal is to see whether the different detrending methods are produce meaningfully different results. I'd suggest we :
(1)  compare chronologies (residuals) with the two methods (visually and/or regression)
(2) run species analyses for the two, see if results differ.

I've compared res values (from "SPECIESdrop.rwl_tabs.txt") from 50-year fixed spline (new) and 2/3 spline (current) detrending methods for LITU, QUAL, and FAGR. Values are highly correlated: R2=0.99, slopes between 0.99 and 1. Details are in project Dropbox folder. Based on this, it is not worth re-running analyses with a 50-year fixed spline detrending method. Closing this issue.


[Bug]: Cannot horizontally scroll in IDE when the split view

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I have the IDE 2.0 open in split view with the UI i cannot horizontally scroll to see longer lines of code.
I would expect to be able to horizontally scroll. It would also be nice if we could change the width of the code editor.
Note that moving with the cursor along the line does move the view and I am able to see the code that way.

Steps To Reproduce

Open the code editor in split view
Write a line of code longer than the viewport
Try to horizontally scroll

Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
Cloud

Sorry but the issue still persists. I think this would need further attention. Also selecting accross a wrapped line just doesn't work like it should on a correctly wrapped line.

@albinAppsmith just wanted to say that the fix has propagated to my app as well. Works perfectly!


Fix Issues #12 and #15

Issues fixed:
https://github.com/absinthe-graphql/absinthe-socket/issues/12
https://github.com/absinthe-graphql/absinthe-socket/issues/15

Hey @mgtitimoli does this address some of the issues you'd found with the other PRs?

@rjacobskind thanks for creating this PR. I had a chat with @mgtitimoli a few weeks ago and he was not entirely happy with my solution but wanted to pursue a different approach.
Anyway, I recently found another issue in my original fix. You might wanna take a look at the last two commits at https://github.com/Lean5/absinthe-socket/commits/master and include the fix in this PR.

Thanks for the heads up @mpoeter . I'll take a look at it soon and adjust the PR accordingly

Any update on this? We are seeing the described errors and would love to get a fix 😄

Can we just cherry pick @mpoeter's commits directly? These commits are identical to his, but don't retain the original authorship. His branch also has a few followup fixes: https://github.com/Lean5/absinthe-socket/commits/master
We've been using that fork with no problems 👍

Feel free to cherry pick @archSeer . I copied these commits and submitted a PR because several people are seeing this bug. A fix should really be incorporated into the library, rather than have everybody cherry pick the fix

I would have created a PR myself back then, but I had a chat with @mgtitimoli via Slack and he was not happy with my solution, but wanted to pursue a different approach. I was under the impression that he wanted to provide a different fix within a few weeks, but this was almost 3 months ago and I am not aware of any progress since then.
IMHO these are serious issues in the currently released version and I absolutely agree that it is high time that a new release that fixes these issues gets published.

I can verify that the patch here (which are commits from @mpoeter I believe?) solves my issues regarding #12. It would be great to have a fix for the faulty behaviour released soon.


Broke on >= RN36

https://github.com/sonnylazuardi/react-native-credit-card/issues/7

this PR fixes this problem: https://github.com/sonnylazuardi/react-native-credit-card/pull/6

@sbycrosz can u upgrade react-native-credit-card ?
the PR https://github.com/sonnylazuardi/react-native-credit-card/pull/6 was fixed

Done!
Thanks @sibelius

this is still broken on 0.2.8 on iOS. The Lite form I can't see the input. The regular form the Card image doesn't render.

It seems RN0.37+ broke the existing { flex: 1 } styles.
I fixed the LiteCreditCardInput for now & I'll try to update this lib by the weekend ;)

Should be fixed @latest


Basic Classification Examples

Make a list of the most common classifiers in Machine Learning, like Random Forest, Naive Bayes, SVM, etc. and make a detailed documentation and implementation for the same.

I would like to work on this issue

Sure, please document in an ordered manner.


TypeError: cannot unpack non-iterable NoneType object

Some documents throw following exception
ERROR  BoxProcessorUlimDit@321636                                                                                [04/14/23 18:47:03]
Traceback (most recent call last):
  File "/home/gbugaj/environments/pytorch2-3.10/lib/python3.10/site-packages/gradio/routes.py", line 384, in run_predict
    output = await app.get_blocks().process_api(
  File "/home/gbugaj/environments/pytorch2-3.10/lib/python3.10/site-packages/gradio/blocks.py", line 1024, in process_api
    result = await self.call_function(
  File "/home/gbugaj/environments/pytorch2-3.10/lib/python3.10/site-packages/gradio/blocks.py", line 836, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/home/gbugaj/environments/pytorch2-3.10/lib/python3.10/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/gbugaj/environments/pytorch2-3.10/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/home/gbugaj/environments/pytorch2-3.10/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/home/gbugaj/dev/marieai/marie-ai/workspaces/pipeline-gradio/./app.py", line 120, in process_image
    ) = box_processor.extract_bounding_boxes("gradio", "field", image, PSMode.SPARSE)
  File "/home/gbugaj/dev/marieai/marie-ai/marie/boxes/dit/ulim_dit_box_processor.py", line 404, in extract_bounding_boxes
    raise ex
  File "/home/gbugaj/dev/marieai/marie-ai/marie/boxes/dit/ulim_dit_box_processor.py", line 309, in extract_bounding_boxes
    bboxes, polys, scores, lines_bboxes, classes = self.psm_sparse(image)
TypeError: cannot unpack non-iterable NoneType object

Resolved with commit https://github.com/marieai/marie-ai/commit/fb003f285e7241199b60a177149fd7a8f4dd96b4


Building and installing w/ python3 -m pip install . does not install slam headers and libraries.

Describe the bug
After installing symforce with python3 -m pip install ., my C++ program has an error using #include <symforce/slam/imu_preintegration/imu_factor.h> because the slam subdirectory is not installed. Libraries are also missing.
To Reproduce
Clone the symforce repository, cd into it, and run python3 -m pip install . to install.
On my computer this installs headers into /Library/Frameworks/Python.framework/Versions/3.9/include and libraries into /Library/Frameworks/Python.framework/Versions/3.9/lib/.
Make a file test.cc
#include <symforce/slam/imu_preintegration/imu_factor.h>
int main() {
    return 0;
}

Try building the test program with the flags that have otherwise worked for me.
clang test.cc -std=c++17 -DSPDLOG_FMT_EXTERNAL=1 -I/usr/local/include/eigen3 -I/Library/Frameworks/Python.framework/Versions/3.9/include
test.cc:1:10: fatal error: 'symforce/slam/imu_preintegration/imu_factor.h' file not found

I was able to fix this issue by adding the following lines to symforce/slam/CMakeLists.txt:
# ------------------------------------------------------------------------------
# install

install(TARGETS symforce_slam DESTINATION lib)
install(DIRECTORY ./ DESTINATION include/symforce/slam FILES_MATCHING PATTERN "*.h" PATTERN "*.tcc")

Expected behavior
All standard Symforce libraries and headers should be installed when running a build/install command.
Environment (please complete the following information):

OS and version: MacOS Ventura 13.3.1
Python version: Python 3.9.13
SymForce Version: 0.8.0

Additional context
cmake version 3.26.3

This is also fixed in the current master. We might put out a new release that addresses all these issues.


Grouping extension types in scaffold select type prompt

WHY are these changes introduced?
Fixes https://github.com/Shopify/shopify-cli-planning/issues/323
Only public extension types

All extension types

WHAT is this pull request doing?

Added public extensions group information. The order used to define the groups is used to the order the extension group types are displayed in the prompt
Add optional group attribute to CLI Question->choice model.
Map new choice group information to inquirer separator component so the extension types are showed with the group name as the separator
Reimplement the default inquirer separator component style

How to test your changes?

Run the command yarn shopify app scaffold extension

Updated PR with decisions made in the issue


How to crawl a dynamic web page

This crawler is cool.
But I always met some contents in the web page is loading.
And I can't get the loaded contents in the html.
Can this lib help me to get the contents after the page load completely?
-^-

Sorry dude, this lib is like calling an api. You get only whatever the api returns. You have to find out which api returns the data you want or you can have a look at some web driver based lib.

#103


Hotfix null user

We just saw a production error in which the Archive index failed to load because a null author was passed into a model's normalized_attrs_for_views method. This PR changes those methods to use safe accesses.
We'll address null authors getting into the DB with https://github.com/TechAndCheck/hypatia/issues/42
Testing

Archive posts from each source
Check that the archive page loads

The error in question
2022-06-23T07:09:49.464353+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] ActionView::Template::Error (undefined method `profile_image_url' for nil:NilClass
2022-06-23T07:09:49.464354+00:00 app[web.1]:
2022-06-23T07:09:49.464355+00:00 app[web.1]: author_profile_image_url:         self.author.profile_image_url,
2022-06-23T07:09:49.464356+00:00 app[web.1]: ^^^^^^^^^^^^^^^^^^):
2022-06-23T07:09:49.464356+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4]     1: <% archive_items.each do |archive_item| %>
2022-06-23T07:09:49.464357+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4]     2:   <%= render partial: "archive_item", locals: { **archive_item.normalized_attrs_for_views } %>
2022-06-23T07:09:49.464357+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4]     3: <% end %>
2022-06-23T07:09:49.464358+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4]
2022-06-23T07:09:49.464359+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/models/sources/facebook_post.rb:183:in `normalized_attrs_for_views'
2022-06-23T07:09:49.464359+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/models/archive_item.rb:121:in `normalized_attrs_for_views'
2022-06-23T07:09:49.464359+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/views/archive/_archive_items.html.erb:2
2022-06-23T07:09:49.464360+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/views/archive/_archive_items.html.erb:1
2022-06-23T07:09:49.464360+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/views/archive/index.html.erb:13
2022-06-23T07:09:49.464360+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/views/archive/index.html.erb:12
2022-06-23T07:09:49.464360+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/controllers/archive_controller.rb:16:in `block (2 levels) in index'
2022-06-23T07:09:49.464360+00:00 app[web.1]: [70b0ea00-6312-4b9a-a799-6d24dd36cfd4] app/controllers/archive_controller.rb:10:in `index'

No longer needed. Underlying issue fixed


Update ROSA scalability workflow to commit the result numbers to github

Added Schedule run config for Rosa scalability benchmark

@mhajas thanks for your review. I have updated the code according to the comments. Ready for review.


feat: add new design of nav menu in mobile devices

You can view the figma file here.

The design should be responsive.

ℹ We recommend updating the styling of existing components, otherwise you can add extra components if there is a need.

You can get icons from here
You need to implement the active state and navigating to correct route based on selected nav icon.

Any changes to the above design are welcome. Please feel free to share your thoughts, and we will discuss them thoroughly.

⚠ Make sure to push all the changes into dev branch

@rupali-codes
I'm creating this because the header design PR is merged, and since there's no sidebar option, I assume we're going with bottom navigation.

Hi @Anmol-Baranwal could you please assign this issue to me.

@MAXASSASSINS
I have assigned you the issue. Please proceed with it, and don't hesitate to tag any of the maintainers if you require any assistance.