Help with running pyrrow on arm64 in Docker

I have an issue running Arrow with pyarrow on arm64 - in Docker - and hope to get some advice.
I get the following errors:
<jemalloc>: Unsupported system page size

The Docker image I’m building is Debian and based on python:3.8.9-slim-buster. It's used for Apache Airflow.
I’ve tried a nightly pyarrow wheel but it doesn't fix the issue. Neither does installing jemalloc from source.
Installing Arrow and pyarrow from source does fix the issue. Any advice for fixing this issue without installing Arrow and pyarrow from source?
I contacted the mailing list on the 27th of July for this. Thanks!

If you don't want to install Arrow from source you can try using the environment variable ARROW_DEFAULT_MEMORY_POOL to switch to a different allocator:
(arrow-release-5) pace@pace-desktop:~$ ARROW_DEFAULT_MEMORY_POOL=jemalloc python -c "import pyarrow; print(pyarrow.default_memory_pool().backend_name)"
jemalloc
(arrow-release-5) pace@pace-desktop:~$ ARROW_DEFAULT_MEMORY_POOL=system python -c "import pyarrow; print(pyarrow.default_memory_pool().backend_name)"
system
(arrow-release-5) pace@pace-desktop:~$ ARROW_DEFAULT_MEMORY_POOL=mimalloc python -c "import pyarrow; print(pyarrow.default_memory_pool().backend_name)"
mimalloc

I'm not sure off the top of my head what options are available in the pyarrow wheel.
Also, some research suggests that there might be certain settings that can be set to get jemalloc working.  Can you share your Dockerfile so I can try and reproduce?

I contacted the mailing list on the 27th of July for this. Thanks!

Yikes, unfortunately, I don't see any message on that date on either user@ or dev@
Did you make sure to subscribe to the mailing list before you sent your message?  The mailing list will ignore emails from unsubscribed users.  If you're pretty confident you subscribed then email me at weston dot pace at gmail dot com (remove spaces and replace dot with . and at with @) so I can get your email.

This error is known to me and can occur if you cross-compile pyarrow. @kszucs do we do that for ARM wheels? If so, we need to specify the page size in the jemalloc configure explicitly.

We build the arm64 wheels on graviton2 travis instances in docker, so we do not cross-compile. @xhochy do you have a reference to the issue?
Sadly I don't have an arm64 machine at hand, so I'm unable to reproduce the issue.
A wheel can be produced using the following command:
pip install -e arrow/dev/archery[docker]
ARCH=arm64v8 PYTHON=3.8 archery docker run python-wheel-manylinux-2014
# wheel is going to be available under arrow/python/repaired_wheels/

We build the arm64 wheels on graviton2 travis instances in docker, so we do not cross-compile. @xhochy do you have a reference to the issue?

I came across thus while building the conda packages for osx-arm64. No real documentation except what is in the recipe.

Sadly I don't have an arm64 machine at hand, so I'm unable to reproduce the issue.
A wheel can be produced using the following command:

pip install -e arrow/dev/archery[docker]

ARCH=arm64v8 PYTHON=3.8 archery docker run python-wheel-manylinux-2014

# wheel is going to be available under arrow/python/repaired_wheels/

I would expect the error to also happen when run using Qemu. It could also be that the kernel of the graviton instances has a larger than normal page size and thus only breaks on smaller machines.

I would expect the error to also happen when run using Qemu. It could also be that the kernel of the graviton instances has a larger than normal page size and thus only breaks on smaller machines.

Perhaps we can overcome that issue using https://github.com/jemalloc/jemalloc/issues/467#issuecomment-294383178 ?

Yes, I'm doing that with --with-lg-page=14 in the OSX case.

Thanks everyone for your help!

Can you share your Dockerfile so I can try and reproduce?

Unfortunately I can't as it's used at work.

If you don't want to install Arrow from source you can try using the environment variable ARROW_DEFAULT_MEMORY_POOL to switch to a different allocator:

This doesn't seem to help either. Here's a log snippet where I've echoed and grepped the container's environment to check that it's set properly:
[2021-08-16T03:16:17Z] ARROW_DEFAULT_MEMORY_POOL=system
SNIP
[2021-08-16T03:16:18Z] <jemalloc>: Unsupported system page size

Now I'm wondering if something else except for Arrow is using jemalloc

Did you make sure to subscribe to the mailing list before you sent your message? The mailing list will ignore emails from unsubscribed users. If you're pretty confident you subscribed then email me at weston dot pace at gmail dot com (remove spaces and replace dot with . and at with @) so I can get your email.

Yes, I overlooked subscribing to the mailing list. I have now. Thanks!

Yes, I'm doing that with --with-lg-page=14 in the OSX case.

I'll trying build a wheel and/or installing jemalloc from source. Thanks!

@nesyamun could you please try out pyarrow-6.0.0.dev45-cp38-cp38-manylinux2014_aarch64.whl?

Thanks @kszucs, unfortunately it doesn't work. I've checked the page size of the system I'm running pyarrow on - it's 64 KiB.
Would it be possible to get a wheel with jemalloc configured for this page size, or would that be something I would need to maintain myself? Building from your fork with ARROW_JEMALLOC_LG_PAGE=16 works. If it is merged, would it be possible for a wheel to be published configured as such?

@kszucs Thanks! I've tested this and it works: https://github.com/apache/arrow/pull/10940#issuecomment-900317827


WE Main Profile ReadMe

Go to the /profile/Readme.md area and update it to reflect a welcoming Readme for the entire organization.
Modify so we have the NAICS, Main company, etc - everything needed for the Galaxy program to function properly.
Here are some examples:
Github Official
Best ReadMes
ReadMe Templates

test

test

test2

Test3


flyover text for modal and open choice view

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #1516
**Description
duplicate PR of #1625 and addressed review comments
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: Bug fix
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

@jingtang10 Due to conflicts, i have created new PR duplicate of #1625, also addressed review comments from old PR

As original PR related issues are resolved . SO this PR is not needed so closing it


Add Test Data: Default Test Type Code dropdown

As an ECMPS user, I want the Test Type Code dropdown to display the applicable default option so that I know which Test Data I am adding
Acceptance Criteria:
Given I am an ECMPS user adding Test Data
When I click on 'Add' for Test Data
Then I see that the Test Type Code dropdown displays the default applicable option (Based on what Test Type Code screen the user is on)

Test Case: TC1234
Test Passed


Introduce interactive element

Actually added and then removed Interactive Component. Wound up introducing a Focusable interface that includes interactive features. Displayable embeds this interface and Component implements it.
Any component that is expected to be interactive, should set the IsFocusable attribute, which is also available as a ComponentOption. This makes it easy to make components interactive declaratively.
Also introduced some component CursorState values, which help us with setting Active, Hovered, Pressed, etc.


docs: describe build process

I would suggest to document the release process, and in particular how to reproduce the builds locally.

/gcbrun


fixes TurnerSoftware/Pingalot#12 AverageRoundTrip decimal places

resolves https://github.com/TurnerSoftware/Pingalot/issues/12
set totalRoundtrip as a double (was implicitly a long)
added a rounding of totalRoundtrip to two decimal places
work is under way to add a unit test method to validate all statistics in PingSession

@Turnerj this pull request all good?

Yeah, this one is good. The code coverage went down as from the changes with #11, both paths aren't being tested.


Useless action

What happen?
I commend /test apply
And two actions executed.
I think this could be avoided.

Relevant log output?
No response
What you expected to happen?
No response
How to reproduce it (as minimally and precisely as possible)?
No response
Anything else we need to know?
No response
What is the version of Sealer you using?
No response
What is your OS environment?
No response
What is the Kernel version?
No response
Other environment you want to tell us?

Cloud provider or hardware configuration:
Install tools:
Others:

@justadogistaken your picture has not been uploaded. Please take another look.


refactor(es6): Upgrade Parser Plugins which depend on AbstractPlugin to es6

What kind of change does this PR introduce?
Refactor
Did you add tests for your changes?
Existing Tests are passing
If relevant, link to documentation update:
N/A
Summary
update Parser Plugins which depend on AbstractPlugin to ES6 and remove AbstractPlugin
fixes #3674
Does this PR introduce a breaking change?
No

Done 🎉

First 5 commits are separate files refactoring. Last one is removing of AbstractPlugin.

Killer work. This is great. Thank you so much!!!

👍


Add interaction stories for buttons, number field, and anchor

Pull Request
🤨 Rationale
Part of #495
👩💻 Implementation
I had to make some changes in storybook-addon-pseudo-states to support our styling, but now we can pull in that fixed release and add some initial visual tests.
The way the addon typically works is that you set story parameters to select which component(s) should have the pseudo-state styling, e.g.
ButtonStory.parameters = {
  pseudo: {
    hover: ["#one", "#two", "#three"],
    focus: true, // means apply to all components
    active: ".some-class",
  },
}

However, this does work well with our matrix story approach. The effect of these parameters is just to set certain classes on the indicated elements. So, instead, we can bypass the story parameters and directly apply the classes to our elements. For example, any element with the class hover or pseudo-hover-all will be styled by the addon as if hovered.
NOTE: Because we have to put the classes directly on the elements in our Story html, we can't put them on any shadow DOM elements, e.g. the inc/dec buttons of the number field. However, puting pseudo-<state>-all on a host element will cause all elements in its shadow DOM to be styled as if they have that state. This can create some visuals that are practically impossible (e.g. a number field and both of its inc/dec buttons all having keyboard focus at the same time), but they are still useful from a visual testing standpoint.
The pseudo-states supported by the addon are:

:hover
:active
:focus-visible
:focus-within
:focus
:visited
:link
:target

It is only interesting to test states that we specifically style for, so generally, that is hover, active, and some form of focused. Because our components use both :focus-visible (focusVisible from FAST) and :focus-within, I'm not distinguishing the two, and I'm setting classes for both whenever we want to see "focused" styling. We could potentially test all combinations of these pseudo-states, but that seems unnecessary, especially considering that we want to test these states in conjunction with other appearance/config variations. So I'm limiting combination testing to just hovered+active, since that is a common use case for mouse-based interaction. To summarize, that means I'm proposing we test:

hover (only)
active (only)
focused (only)
hovered and active

Initially, I'm adding new test matrix stories for:

anchor
anchor-button
button
menu-button
number-field
toggle-button

These seemed to be some of the more interesting components in terms of having distinct keyboard-focused and/or active states, (in addition to hover, which applies to most/all? components).
🧪 Testing
Storybook visual tests
✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

@mollykreis I would ask Malcolm, but he's out this week, so can you please buddy for me?


Implement vyper-config

vyper-config would provide a similar configuration hierarchy, but simplify the process of tracking, adding, and updating parameters.
May be worth looking into this and comparing against other methods.

Would be really cool to implement this!

Ouu that would be very useful indeed, almost a necessity for configuration within discord actually.


Handle creation of unique indexes for not existing fields

What should be done?
When creating a unique index on a field that doesn't exist in the collection that field would be treated as null and therefore MongoDB would return Duplicate key error while PostgresSQL would just create required index.
We should either support creation of such indexes and add diff test or implement a check that would help to return correct error.
Where?
internal/handlers/pg/pgdb/indexes.go
Definition of Done

all handlers updated;
unit tests added/updated;
integration/compatibility tests added/updated;
spot refactorings done;
user documentation updated or an issue to create documentation created;
something else?

This might be related to https://github.com/FerretDB/FerretDB/issues/2910.


Run web test (WebdriverIO) and ios app test (Appium) within the same test

What are you trying to achieve?
I am trying to automate test cases where I have to do some stuff in the mobile app then move to a desktop browser and do other stuff.
Things that I have tried so far
Set both Appium and WebdriverIO as helpers

Mobile tests works fine but when I get to the browser part, I get a Method is not implemented error for I.amOnPage('/'). Note that I already have existing browser test cases that I wish to reuse.

Set Appium only as helper and pass url config(since the Appium driver only extends Webdriver)

Mobile tests works, then opens a browser within the Simulator.

I have noticed that it is always using the Appium driver, thus getting the error mentioned above. Is there a way to switch drivers? if there aren't any, what do you think is the best solution aside from rewriting the test cases themselves?

CodeceptJS version: 1.1.4

@chris-af you can add a tag to the WebDriverIO specific functions which you to include (or exclude). For example:
Here are you some tests (in the same file), use an "@appium" tag for appium specific tests.
Scenario('Appium example test 1 @appium' (I) => {
  I.amOnPage('/');
})

Scenario('WebDriverIO example test 1' (I) => {
  I.amOnPage('/');
})

Then run specific tests using the --grep option.
# Run appium tests
codeceptjs run -c ./codeceptjs.conf.json --grep "@appium"

# Run webdriverio (aka. non-appium) tests
codeceptjs run -c ./codeceptjs.conf.json --grep "@appium" --invert

Of course you can specify a "@webdriverio" tag to use, but using the --invert option means less typing for you :)

@reubenmiller I actually need to automate both mobile and backend website inside the same scenario
`Scenario('Mobile and web test', function(I, mobilePageObject, webPageObject) {
// Uses appium driver
mobilePageObject.login();
mobilePageObject.doStuff();
// Uses webdriverio, desktop browser only
webPageObject.assert1(); // I.amOnPage('/') is here
webPageObject.assert2();

})`

And the reason why you have it in the same scenario is because you want to check that an action from the mobile device is also displayed on the desktop version?

I am checking if the data is also shown in the web backend. It is not really a desktop version of the app. It is an entirely different application but using the same data.

And I'm assuming you can't replace the mobilePageObject calls with rest requests or something?
Otherwise, just to cover all bases, are you sure process.env.PROJECT_TEST_URL is being set correctly?
Then as next steps, maybe you can try creating a custom helper with then references the individual helper functions directly.
'use strict';
import assert from 'assert';

let Helper = codecept_helper;

class MyHelper extends Helper {
  async amOnPageUsingWD(url) {
    const helper = this.helpers['WebDriverIO'];
    try {
      await helper.amOnPage(url);
    } catch (err) {
      throw err; // re-throw error
    }
  }
}

module.exports = MyHelper;

Then use I.amOnPageUsingWD instead of I.amOnPage.
The idea behind this is to see if you can use the amOnPage function from WebDriverIO because I'm pretty sure amOnPage from WebDriverIO is being overwritten by the Appium Helper config (because it is defined after the WebDriverIO Helper in the config.

That works only on the methods that we reimplement.
amOnPage -> amOnPageWD
With that approach, I will be reimplementing other methods as well such as
waitInUrl
fillField <- I am getting 'locator.stringify is not a function' errors
I'm already using those pageobjects in other test cases that are desktop only.
Maybe there is a way to "switch" drivers from appium to webdriver? or dynamically load config

So I'm guessing that you are wanting to use the two helpers in a lot of scenarios together?
I'm not exactly sure how the api would look like (without being confusing for the user).
I.switchHelperTo('WebDriverIO')?
But then it would be only specific to WebDriverIO and Appium which is not so nice.

Yes, we have a lot of scenarios where the two helpers are needed.

@chris-af  I'm looking into this

@chris-af I've done a proof of concept.
I was able to hack the lib/actor.js file which enables this functionality, so feel free to test it if it works. Here are the steps to use it.
How to use it

Copy the actor.js contents from the gist and replace the contents of node_modules/codeceptjs/lib/actor.js
In your test, then use I.switchHelper to specify which helper you want to use (before using the helper functions that you're after).

Scenario('Mobile and web test', function(I, mobilePageObject, webPageObject) {
    // Uses appium driver
    I.switchHelper('Appium');
    mobilePageObject.login();
    mobilePageObject.doStuff();

    // Uses webdriverio, desktop browser only
   I.switchHelper('WebDriverIO');
   webPageObject.gotoLogin(); // I.amOnPage('/') is here, this is where the script throws the error
    webPageObject.assert1();
    webPageObject.assert2();
})

I did a quick test where I had both Puppeteer running chrome and WebDriverIO running firefox and I could control both browsers in the same scenario. So let me know if it works.
I'm still not sure if it will make it into the library, I'm discussing it with the other collaborators to gauge their reactions.

@reubenmiller I am gettting a weird locator.stringify is not a function error and a An unknown server-side error occurred while processing the command. Original error: Url or Uri must start with <scheme>:// when running the WebDriverIO steps
Scenario('Mobile and web test', function(I, mobilePageObject, webPageObject) {
    // Uses appium driver
    I.switchHelper('Appium');
    mobilePageObject.login();
    mobilePageObject.doStuff();

    // Uses webdriverio, desktop browser only
   I.switchHelper('WebDriverIO');
   webPageObject.gotoLogin(); // <--- Error here
    webPageObject.assert1();
    webPageObject.assert2();
})

//webPageObject

fields: {
 username: 'input#username',
 password 'input#password'
},

goToLogin() {
  I.amOnPage('/'); // First error here
  I.fillField(this.fields.username, username); // Second error here
  I.fillField(this.fields.password, pass);
}

But when i don't use the page object in the scenario, it works fine
Scenario('Mobile and web test', function(I, mobilePageObject, webPageObject) {
    // Uses appium driver
    I.switchHelper('Appium');
    mobilePageObject.login();
    mobilePageObject.doStuff();

    // Uses webdriverio, desktop browser only
   I.switchHelper('WebDriverIO');
   I.amOnPage('http://localhost:5000');
   I.fillField('input#username', username);
   I.fillField('input#password', pass);
})

So I tried to move the switchHelper method inside the page object itself
goToLogin() {
  I.switchHelper('WebDriverIO');
  I.amOnPage('/');
  I.fillField(this.fields.username, username);
  I.fillField(this.fields.password, pass);
}

Seems to work only in that specific page object. I does not work on other page objects like webPageObject2. I already have a lot of existing page objects

Yeah it was just a quick proof of concept so it appears that it doesn’t support page objects.
Though we were discussing this kind of feature, and it received a positive feedback but we can’t guarantee if or when just yet.

oh wow, thanks a lot @reubenmiller. This is really a lot of help to us. i'm hopeful that this feature gets added in the future

I need this too! :D actually, my whole team does

@reubenmiller  My current workaround for this is to call I.switchHelper('Appium') inside the page objects.

After reading this web site I am very satisfied simply because this site is providing comprehensive knowledge for you to audience.
Thank you to the perform as well as discuss anything incredibly important in my opinion. We loose time waiting for your next article writing in addition to I beg one to get back to pay a visit to our website in
Selenium training in Chennai

I love your blog.this all provided knowledge are unique than other testing blog.good explain.
keep updating
https://www.exltech.in/software-testing-course.html

This is available in other frameworks, should be possible.

Could you please let me know if this feature is implemented wherein I can switch between different helpers (for example: from Webdriver to Appium) in the same scenario?


DoD for 11/26

[ ] pipeline code that generates multiscale graphs
[ ] clear instructions
[ ] R reliability code (script)
[ ] timing of running pipeline somewhere
[ ] reliability matrices & adjacency matrices for 2 atlases for 2 datasets
[ ] A qualitative assessment detailing pipeline performance (length ~1 paragraph containing observations and/or recommendations about how to process 10^4 subjects)

I added an m2g section at the bottom of tutorials.  Let's populate that.  I did a first draft.
Things that need fixing:

[ ] Scrub of the tutorials.md info
[ ] On the sidebar, cloud services should be services.  Clusters are not clouds.
[ ] The validation page is a good start, but we should explicitly have a page that says against a tagged version of m2g, we ran the following 3 datasets and 3 atlases, and this is what happened.  There should be a paragraph for each dataset and atlases, with reliability scores and pictures highlighted, along with a direct link (see below)
[ ] In the link you give to the raw data, looks like there are random desikan results in the top level.
[ ] Why are we providing graphs on data/public if we have MROCP?  This is confusing.  If there's a reason, let's explain it.  Are these "nightly runs"?  That's ok.
[ ] Provide a brief explanation of the raw data suitable for someone just arriving.  What is there?  How can they read the files?  How can they learn more?

Validation Page

[ ] The validation page should have a preamble explaining how we validate the pipeline and an explicit link to the reliability function with instructions (linked to the sphinx doc for that function)
[ ] Tag the current release
[ ] Explicitly state that we validated capability by running a large data set (SWU) and two TRT datasets.  For each of the three data sets, provide:

[ ] Runtime
[ ] Validation (the actual score and relevant debug info like how many subjects were available to compare) - for the TRT
[ ] Location of graphs and more detailed results
[ ] A summary saying whether that dataset did well or poorly and why (this is obvious to us, but not to new readers)

[ ] Add a paragraph or two summarizing expected behavior of pipeline (where is the bulk of the work?  Fiber tracking and graph gen...How long per subject (6 hours)...a link to the data format/spec that people need to meet.  Any known issues that a new user might face and how to fix, like setting up paths, getting an account, etc.
[ ] An overall statement stating that this concludes our validation of m2g.

Clear instructions (standalone)

[ ] You should give people a clear pointer to where to go in tutorials
[ ] If ec2 still doesn't work when we sell this off, let's make a git issue stating such and be clear
[ ] Where does someone get a bc1 account?
[ ] Where does someone get LONI v6.0.1?  It's not available from LONI
[ ] I would suggest sample scp and chmod commands
[ ] where does one find the m2g workflow?  In the sidebar?  On disk?
[ ] which variables should people change?  Is there a link where they can know what each one does?
[ ] link to the output format spec and description for each output file

Clear instructions (standalone)

[ ] General links to ec2, and to AWS help.  Nothing too involved.
[ ] What choices should someone make for computer size, storage, and security?
[ ] Link to the AMI page with details (or add the relevant ones here and link to building an AMI)
[ ] Add recommendation for screenshare on a mac - built in and easy
[ ] Link to mounting a harddrive - I have a good way to do this if you don't
[ ] Example of moving data
[ ] Again, explain or link to the variables
[ ] Again, explain or link to the data derivatives people will find after the pipeline runs.

Review process
We can do a sample walkthrough of this tomorrow in our meeting; ideally doing everything except the data that are still running.

11/12/2015:
[ ] Clarify that client version is compatible, not 6.0.1
[ ] Clarify which version is needed.  If it's not on LONI's website currently, adjust documentation to say so.
[ ] Add pointer to sample dataset e.g. kki42 and explain that people can skip the transfer step

Feedback from jovo::
###Running on bc1

[ ] your computer (client)

(ignore the close, was a misclick) :)

Closed per pull request and completion of this and other related git issues.  Job well done team.


[Addition]: Some more hotspots in the previously described gaming system in Tallinn, Estonia

Hotspot b58 Addresses
112Hqc7Vb78CaZMeYQqoL1R1jf3Ratbp8FNAFSk3Z8fLKCuZHhRK
11Vk18xYrysFGxWkN4mGXB7GFnmrPRJHmAjncw92RH3MGWdMsEF
11AGUjFhxRXNgbs72XK1ruVNGrdJt8M7DU9RFXwT53UPfGuRYiX
Discord Handle
No response
Reason(s)
These three Pisces hotspots belong to wallet 13jEAoneWKxFhs9tzKgjhtXMDygFshA721o3vS8uWb54Y4kpDbT and they are part of the larger set of hotspots described at https://github.com/helium/denylist/issues/862 – apparently the entire system used to be asserted in the Netherlands, where they also witnessed only each other. Now they have been reasserted in Tallinn, Estonia. These three have been not very active so far but the connections with the farm can be seen from recent beacons, e.g. https://explorer.helium.com/txns/WVPv7CMWfMRrk-wIxptmA2xYlfsLVjO29G3CxUqJ8v8 , which were witnessed by no known local hotspots.

We have taken into account this addition request in the next iteration of the denylist. Some or all of the Hotspots listed may be added to the denylist. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


Can not start the localization module.

Hi,
I'm using apollo 2.0.0 version. My GPS is  NovAtel SPAN® ProPak6™ with IMU-CPT. After some configurations, the GPS module light turned green. Then i try to start the localization module but failed. I check rostopic and find data in /apollo/sensor/gnss/corrected_imu. But i cant find data in /apollo/sensor/gnss/imu using rostopic echo.
Is that the problem why I cant start the localization module?
Need some help, thank you.

you can try
bash scripts/llocalization.sh

if you have build it success,even if it failed,you could find the failed log in the data/log.

@gengqx thank you for your response.
I used script to start, and it failed again. I looked at localization.WARING, localization.FATAL, localization.ERROR, localization.INFO and they all show
F0503 10:08:57.974390  1530 velodyne_locator_omp_alt_align.cc:170] Reflectance map folder is invalid!
How can I solve it?

Due to the new apollo 2.5,it use MSF location method as default,so you need modify modules/localization/conf/localization_config.pb.txt
Replace MSF with RTK

@gengqx thanks a lot for your help.
I have solved it.


Get c3i working with a successful concourse update with tagging

To ensure we don't break our usual workflow (users don't have to specify --worker-tag in order to kick off general builds), we need a default value for the --worker-tag. The default should be an array with a single value containing the tag that each worker shares.

LGTM.  I assume we should hold off on merging this until all the workers are tagged again?

Yep, and we may need to test the resource (for rsync-recipe, etc) yaml generation to make sure that tagging workers won't prevent us from kicking off the resource tasks that pull the recipes off zeus. I think we saw some issues with that once we had all the workers tagged.


Is PW_CACHE_EXPIRE=0 not possible? (Proxy)

Is it not possible to permanently deactivate the cache with PW_CACHE_EXPIRE=0?
I have set this in the environment variables as a test, but the debug log still shows that cached values have been taken.
It also looks as if 5 seconds are cached anyway, even with a lower value.
My docker-compose.yml looks like this:
version: "3"

services:
  pypowerwall:
    image: jasonacox/pypowerwall:latest
    container_name: pypowerwall
    hostname: pypowerwall
    ports:
      - 8675:8675
    environment:
      - PW_PORT=8675
      - PW_HOST=<IP_ADDRESS>
      - PW_GW_PWD=123
      - PW_CACHE_EXPIRE=0
      - PW_TIMEZONE=Europe/Berlin
      - TZ=Europe/Berlin
      - PW_DEBUG=yes
    restart: always

Hum... There may be a bug in the proxy or the pypowerwall library. Can you check if the env variable is setting the cache config by looking at http://localhost:8675/help and find the cache setting?
Having said that, it looks like you are using TEDAPI endpoint. I highly recommend against using no-cache. You are very likely to trigger the Powerwall rate limiting, high CPU backoff error or cause other issues.

Don't worry, I don't want to deactivate the cache, but set it to 3 seconds.
0 was just to test whether the setting is adopted or not.
With 3 seconds, however, 5 seconds are also cached.
2-3 seconds is not a problem for the local API.
The env variable is applied correctly, see screenshot.

Thanks! Are you seeing the cache working via logs (via PW_DEBUG=yes) or is there some other way you see it not expiring the cache?
The main code for the TEDAPI caching that could be relevant:
https://github.com/jasonacox/pypowerwall/blob/2c93ce9327d97020cb1ff78862ab9c38c8006e09/pypowerwall/tedapi/__init__.py#L306-L310

I could see this in the MQTT log.
The cache expire was set to 2 seconds, the api was called every 3 seconds.
The MQTT log always showed 2 identical values, only from the 3rd value onwards was it different.
The debug log also showed “Using Cached Payload”.
I have now manually changed all occurrences in the container in the file __init__.py from pwcacheexpire: int = 5 to pwcacheexpire: int = 2. Now no more values are output twice.
It seems that the environment variable is not taken over correctly.

Thanks @erikgieseler - There has to be a bug in the constructor logic. I'll work on a fix...

I just tested the changes, looks good.
Thank you!

Is there also a fixed cache for backup_reserve_percent from the API endpoint /pod or /api/operation somewhere in the code?
When I change the value via the app, it takes about 4-5 minutes until the set reserve value is displayed.

Thanks for testing!
Yes, there was a separate config cache that needed to link to the expire settings. Hopefully latest commit fixes that.

Yes, it fixes the problem, the new backup_reserve_percent value now appears after 5 seconds.
Thank you!

Thanks! I can't recall why we added the separate 300s cache for the config data/payload. I will run this a while to ensure it doesn't introduce some instability before merging.

Test docker image: jasonacox/pypowerwall:0.12.2t67-beta

Test docker image: jasonacox/pypowerwall:0.12.2t67-beta

Looks good, no problems for me so far


Bug: sponsors cards on the main page have unsuitable background and broken size of the logo

Possible fix: remove a background completely and add some tailwind class that is responsible for proper resizing of the images.

Closed in #302


feat(avm): hacky e2e test

Please read contributing guidelines and remove this line.

Current dependencies on/for this PR:

master

PR #4470   👈

This stack of pull requests is managed by Graphite.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 545b3341 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,636
180,516
720,036

l1_rollup_calldata_gas
222,480
870,828
3,465,960

l1_rollup_execution_gas
314,967
988,568
3,685,617

l2_block_processing_time_in_ms
1,167 (+1%)
4,418 (+2%)
17,487 (+2%)

note_successful_decrypting_time_in_ms
311 (+2%)
1,010 (+5%)
3,797 (+6%)

note_trial_decrypting_time_in_ms
23.8 (+18%)
48.8 (-47%)
150 (+6%)

l2_block_building_time_in_ms
17,960
71,201 (+1%)
286,217 (+1%)

l2_block_rollup_simulation_time_in_ms
13,093
51,869 (+1%)
209,027 (+1%)

l2_block_public_tx_process_time_in_ms
4,838 (+1%)
19,247 (+2%)
76,915 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,683 (-11%)
26,464 (-10%)

note_history_successful_decrypting_time_in_ms
2,307 (-4%)
4,527

note_history_trial_decrypting_time_in_ms
81.2 (-5%)
205 (+2%)

node_database_size_in_bytes
17,350,736
33,087,568

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
311
44,476
26,153

private-kernel-ordering
199 (+1%)
44,473
16,553

base-rollup
1,404
128,930
881

root-rollup
82.8 (+1%)
4,088
677

private-kernel-inner
445
71,607
26,153

public-kernel-private-input
247
32,563
26,153

public-kernel-non-first-iteration
246
32,605
26,153

merge-rollup
7.83 (+4%)
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
17,187
39,991

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
560 (+1%)
1,325 (+1%)

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.521 (-13%)
593 (+1%)

Nice work!
How does this work for nested calls!? I'm so confused 😆 Does it work because the nested calls we're making don't create any side effects that need to be siloed by kernel?

It doesnt, going to follow up handling that


Kyocera FS-4200DN stops working after commit "Throw an error if a member attribute occurs outside a collection."

starting with commit
69ba26c811e4abfb92ebb6c7ed8070a9f74b72d7
"Throw an error if a member attribute occurs outside a collection."
Some of our Kyocera printers, for example all Kyocera FS-4200DN, stop working. Cups says it cannot determine the printer's status.
Before that commit ipptool reports:
ipptool ipp://blafasel/ipp ipp-everywhere.test
"document-format": Bad mimeMediaType value "" - bad characters (RFC 8011 section 5.1.10).
successful-ok
With this commit I get
ipptool ipp://blafasel/ipp ipp-everywhere.test
IPP member attribute outside of collection.
IPP member attribute outside of collection.
IPP member attribute outside of collection.
After bisecting I reverted that patch for 2.4.6 and this indeed fixed the problem.

Can you attach a Wireshark or tcpdump trace when you run this command? This looks like a serious bug in the printer but we'll know more once we see what it is returning...

blablabla.zip
This is the trace with iptool from cups v2.4.6 compiled as debian package (bookworm) with 69ba26c811e4abfb92ebb6c7ed8070a9f74b72d7 reverted.

OK, so the IPP response from this printer is bad. The problem appears to start with the pwg-raster-document-type-supported attribute, which contains a memberAttrName tag for "media-supported", followed by the list of supported media sizes. Please report this to Kyocera, and check for firmware updates for this printer.

I already thought that this is due to the printer.
But I doubt Kyocera will fix this (for the FS-4200DN or any other models which are end of life).
I just hoped that cups has a no regression and things should continue to work policy and may include quirks (as the linux kernel does for almost every category of hardware). We cannot throw away all these printers (and it would conform those thinking it works under windows but does not work under linux).
So basically we (and others who still use older kyocera models) either keep 2.3.3op2 from bullseye or maintain a fork where this patch is reverted. As the the version in bookworm has other flaws (printing in color stops working is one) one may have to do this anyway.


[QUESTION] Required socketIO parameters & CORS?

Hi,
I was trying to follow the socket.io example. I was having CORS errors.
While trying to configure I had to create in full:
  socketIO: {
    path: '/',
    serveClient: true,
    adapter,
    parser,
    connectTimeout: 45000,
    pingTimeout: 20000,
    pingInterval: 25000,
    upgradeTimeout: 10000,
    maxHttpBufferSize: 1e5,
    transports: ["polling", "websocket"],
    allowUpgrades: true,
    perMessageDeflate: false,
    httpCompression: true,
    wsEngine: require("ws").Server,
    initialPacket: undefined,
    cookie: false,
    cors: {
      origin: 'http://localhost:8080',
      methods: ['GET', 'POST'],
    },
    allowEIO3: false,
    destroyUpgrade: true,
    destroyUpgradeTimeout: 1000,
    allowRequest: (req, fn) => { fn(null, true) }
  },

All of these look required. Should some of them be optional?
Versions:
"@tsed/socketio": "^6.34.3",
<EMAIL_ADDRESS>"^2.1.13",
"socket.io": "^4.0.0"

I think I won’t be hepfull. I haven’t worked on socket module since a long time. So your question is totally out of my skills because it’s very specific to socket.io.
Maybe a repo with a reproducible process could help me ^^
see you
Romain

I was also having issues, i noticed i do not have to include the suggested imports
import "@tsed/platform-express"; import "@tsed/socketio"; // import socket.io Ts.ED module
If I include those imports, I also see that everything is required. Just leave them out.

Your help is welcome to improve documentation.
Documentation website can be edited directly from the website:

See you
Romain


feat: extend toc block

fix: title attribute was not settable
feat: add filter to block title output to increase flexibility for theme needs
fix: block icon was missing, added the same one used in Gutenberg's TOC block

Oops great point! Done 👍


Etsy V2 API support ended

Looks like V2 API support ended yesterday.
Getting this response from connecting;
{\"error\":\"API v2 deprecated.\",  \"message\":\"The API version 2 you are trying to access has been deprecated. Please upgrade to the latest version (v3) as soon as possible to resume service. For documentation on how to use API v3, please visit https://developers.etsy.com/documentation/migration/index.\"}
I presume progress on V3 hasn't really happened?

I made a new gem for this https://github.com/JaceBayless/betsy. This was the first gem I ever made and I was still fairly new to Ruby/Rails at the time so it's probably quite rough around the edges but if you have any issues feel free to open them and I can do my best to get it working for you!


chore: add examples and update documentation

Thank you for contributing to errors!
Please add a summary of your change
chore: add examples and update documentation
Does your change fix a particular issue?
Fixes #(issue)
Check list:

[ ] Mark if documentation changes are required.
[x] Mark if tests were added or updated to cover the changes.

Codecov Report

Merging #11 (7a7ab55) into main (41d19de) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   97.37%   97.37%
=======================================
  Files           6        6
  Lines         534      534
=======================================
  Hits          520      520
  Misses         12       12
  Partials        2        2

Flag
Coverage Δ

unittests
97.37% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Enter a host name: Is that just my Domain?

 I'm just starting out and would really appreciate help

Not it's a host name.
You should add the --test command line argument and play with it. (this turn off rate limits, but gives you a dummy certificate)
With the DNS system this is also called the "Domain name".
Some people make a distinction that it is a "full host name", including the rest of the domain name after the dots as opposed to a "plain" or "short" host name that's just the first part.
Some people call just the bit they sell a "Domain" because it's important to them. LE's certificates apply only to specifically named hosts (and they don't sell them).


cmd/cue: get go can leave stale CUE files behind

What version of CUE are you using (cue version)?

$ cue version
cue version v0.6.0-0.dev.0.20230320183351-d16b5758c12d

go version devel go1.21-5f1a0320b9 Tue Mar 21 13:10:36 2023 +0000
      -buildmode exe
       -compiler gc
        -ldflags -w -s
  DefaultGODEBUG panicnil=1
     CGO_ENABLED 1
          GOARCH amd64
            GOOS linux
         GOAMD64 v3

Does this issue reproduce with the latest stable release?
Yes.
What did you do?

If I move foo.go to bar.go, bar_go_gen.cue appears as expected, but foo_go_gen.cue remains in place.
What did you expect to see?
I expected cue get go to not leave its stale generated files behind.
For example, whenever it generates CUE for a Go package, it could start by removing all *_go_gen.cue files. Those that are still needed will be created again, and any other will stay removed.
One alternative would be to always generate one CUE file per Go package, like go_gen.cue, meaning that we don't have to worry about generated files needing to be removed. Though this would be a slightly more aggressive change.
What did you see instead?
The above.
cc @rogpeppe

I expected cue get go to not leave its stale generated files behind.

Hmm, I'm not clear that code generators in general should remove files.
Indeed I can't think of a situation where that does happen.
Am I missing some obvious examples?
If so, do they remove files by default, or do they do so behind a flag?

In a way, you're right. For example, https://pkg.go.dev/golang.org/x/tools/cmd/stringer produces one generated file per Go type, and doesn't delete anything. However, I have to run it like stringer -type Foo to have it generate foo_string.go, so I am already in control of which files it is generating, and those filenames are unlikely to change.
Another common example is protobuf generating Go code; it generates one output file per input proto file. Those can be placed in a separate output directory, but one could also have the generated files alongside the source files in the same directory. This makes it closer to cue get go, I think, and it also doesn't seem to remove files. Presumably it has the same quirk, though - if I rename foo.proto to bar.proto, then I can end up with bar.pb.go as well as the stale foo.pb.go. The difference is that the stale file will be extremely obvious - Go will reject duplicate declarations, for example. cue get go often doesn't make that kind of duplication as obvious, as declaring the same definition with the same value twice is OK.
In short - yes, other generators don't delete files, but other generators that I'm familiar with either generate just one file at a time, or often result in errors when stale files are left behind.

I'd agree that it's good practice to remove all generated files prior to running a generator. But in the general case I'm not clear that the generator can do that safely by itself. Especially if one can specify the file into which the generated output is written (because then there ceases to be a pattern of files that it would remove).

I'm going to close this as "unfortunate but not sure we can do better", because I can't disagree with you. I can always search the issue tracker and come back here if I get bitten by this again and have more useful thoughts.


feat(console): add metamask

Replacement for: https://github.com/akash-network/console/pull/291

@baktun14 just was scanning through PRs and notice this one is 3 weeks old. Just a heads up

@baktun14 just was scanning through PRs and notice this one is 3 weeks old. Just a heads up

I know thanks for the heads up, I was waiting for @schnetzlerjoe on a new version of cosmos-extension-metamask

@baktun14 just was scanning through PRs and notice this one is 3 weeks old. Just a heads up

I know thanks for the heads up, I was waiting for @schnetzlerjoe on a new version of cosmos-extension-metamask

What are you waiting on? Maybe I missed something but I mentioned above over a month ago that it's been pushed. Cosmos kit uses the most recent version of snapper ^0.2 which has all the updates we discussed in this thread.

@baktun14 just was scanning through PRs and notice this one is 3 weeks old. Just a heads up

I know thanks for the heads up, I was waiting for @schnetzlerjoe on a new version of cosmos-extension-metamask

What are you waiting on? Maybe I missed something but I mentioned above over a month ago that it's been pushed. Cosmos kit uses the most recent version of snapper ^0.2 which has all the updates we discussed in this thread.

I just tested and as I mentionned in my previous comment, the package cosmos-extension-metamask does not contain your latest changes or snapper ^0.2.

@baktun14 just was scanning through PRs and notice this one is 3 weeks old. Just a heads up

I know thanks for the heads up, I was waiting for @schnetzlerjoe on a new version of cosmos-extension-metamask

What are you waiting on? Maybe I missed something but I mentioned above over a month ago that it's been pushed. Cosmos kit uses the most recent version of snapper ^0.2 which has all the updates we discussed in this thread.

I just tested and as I mentionned in my previous comment, the package cosmos-extension-metamask does not contain your latest changes or snapper ^0.2.

Your version is probably being cached then via lock or yarn cache etc. https://github.com/cosmology-tech/cosmos-kit/blob/main/wallets%2Fcosmos-extension-metamask%2Fpackage.json#L65 you will have to clear the cache, regenerate lock, or edit it manually.

@baktun14 just was scanning through PRs and notice this one is 3 weeks old. Just a heads up

I know thanks for the heads up, I was waiting for @schnetzlerjoe on a new version of cosmos-extension-metamask

What are you waiting on? Maybe I missed something but I mentioned above over a month ago that it's been pushed. Cosmos kit uses the most recent version of snapper ^0.2 which has all the updates we discussed in this thread.

I just tested and as I mentionned in my previous comment, the package cosmos-extension-metamask does not contain your latest changes or snapper ^0.2.

Your version is probably being cached then via lock or yarn cache etc. https://github.com/cosmology-tech/cosmos-kit/blob/main/wallets%2Fcosmos-extension-metamask%2Fpackage.json#L65 you will have to clear the cache, regenerate lock, or edit it manually.

I have 0.2.6 locally and I still get the error ReferenceError: window is not defined when importing the wallets like the documentation says to do import { wallets as metamask } from "@cosmos-kit/cosmos-extension-metamask";

@baktun14 just was scanning through PRs and notice this one is 3 weeks old. Just a heads up

I know thanks for the heads up, I was waiting for @schnetzlerjoe on a new version of cosmos-extension-metamask

What are you waiting on? Maybe I missed something but I mentioned above over a month ago that it's been pushed. Cosmos kit uses the most recent version of snapper ^0.2 which has all the updates we discussed in this thread.

I just tested and as I mentionned in my previous comment, the package cosmos-extension-metamask does not contain your latest changes or snapper ^0.2.

Your version is probably being cached then via lock or yarn cache etc. https://github.com/cosmology-tech/cosmos-kit/blob/main/wallets%2Fcosmos-extension-metamask%2Fpackage.json#L65 you will have to clear the cache, regenerate lock, or edit it manually.

I have 0.2.6 locally and I still get the error ReferenceError: window is not defined when importing the wallets like the documentation says to do import { wallets as metamask } from "@cosmos-kit/cosmos-extension-metamask";

Latest version is 0.2.7 I believe so that's the problem then. All .7 does is support dynamic ssr compilation for your guys use case. Try updating to that and it should clear that error @baktun14


Document AKS + GlusterFS + Heketi for shared persistant storage

Hey there,
for shared persistent storage across nodes/pods, Azure Files does often not have enough IO throughput. Using software RAID on the host VMs on multiple attached disks creating one RAID volume, then exposing those high throughput volumes across the cluster using GlusterFS, Kubernetes can provide persistent storage via Heketi.
It would be great if the above was tested and documented in a detailed manner as an alternative to Azure Files.
Entry point: https://github.com/heketi/heketi/blob/master/docs/admin/install-kubernetes.md

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

ID: d634c63a-6194-86a6-b522-3310812c81e8
Version Independent ID: fa86da1e-9c86-88fe-170c-5e6aa9230b5f
Content: Use Azure File with AKS
Content Source: articles/aks/azure-files-volume.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! I have assigned this to the content author to review and see where we can update the docs

Thanks for the suggestion, @polarapfel. Depending on the scenario and workload, Azure Files is still a viable choice for customers. I'll raise this to the product team and see if this is a solution they'd like to showcase and provide documentation for. If so, I'll create a backlog work item and schedule this for a future doc release.
@MicahMcKittrick-MSFT For now, #please-close


Documentation wishlist

[ ] Tutorial on implementing trigger on an acquire bit that implements put-completion (crib from https://nbviewer.jupyter.org/github/bluesky/tutorials/blob/master/Device.ipynb)
[ ] Tutorial on implementing set on a signal that implements put-completion (crrb from https://nbviewer.jupyter.org/github/bluesky/tutorials/blob/master/Device.ipynb again)
[ ] How-to guides for more involved and/or specific trigger and set implementations (https://nbviewer.jupyter.org/github/bluesky/tutorials/blob/master/Device.ipynb and also PVPositionerPC).
[ ] Area detector basics (crib from CHX beamline config, for example)
[ ] Non-EPICS detector that generates external assets
[ ] Documentation of how AD dispatch works
[ ] Documentation on collect_asset_docs
[ ] Explanation of which methods return immediately, block (hopefully briefly for a little I/O), or return status objects. Mention future plans to do more async.

The relevant example notebooks can now be found in e.g. https://github.com/bluesky/tutorials/blob/main/archive/Device.ipynb.


Input Delay in FPFC (AMD issue maybe?) & Scene Toggles Broken in FPFC

So as a baseline, there is input lag in FPFC, where it takes a fraction of a second for anything to occur, whether it be turning camera, clicking things, or the audio sync in general. This surfaced when I swapped to an AMD based GPU, so may be related. Going from 1.27 to 1.29.1 tightened this up a bit but it's still present.
Removing Camera2 removes the input delay, so it is most certainly how the mod is functioning.
Part of this however, seems tied to cameras being visible when they're not supposed to be while in FPFC. Even with a camera fully disabled on all scenes, it seems to still remain visible no matter what.

It is in fact an AMD issue. Disable Vsync for BS in its driver

Yep that did it! Specifically I had to turn it from 'Off, unless application specifies' to 'Always off'. Glad it was that simple. Thank you! It is still odd that cameras remain visible during FPFC even if toggled off, but the main issue is solved.

Even with a camera fully disabled on all scenes, it seems to still remain visible no matter what.

Please make sure you fully understand how the Scenes System works, check the Wiki on that

Oh lordy. There's an entire flow control system to it I see.. Seems odd to me that it, under certain conditions, just disregards what you have set. I turned FPFC off on all cameras with the intent to just not have the default game camera, but according to this it then instead falls back to the camera being used for the main 'Menu' view. That's a little unintuitive honestly. But I'm sure you have your reasons, so I won't fuss about it - especially with the main issue solved.
I'll go ahead and close this now with that in mind, so, thank you again! ^^


Replace recursive dir creation with package compatible with Daedalus

Closes #10 by using the same package as Daedalus mkdirp

Yes agree 100%. The issue is not the native (experimental) lib, it's the version Daedalus indirectly targets


Chrome Canary not available for Ubuntu 16.04

The Canary version of Chrome is not currently available for ubuntu, will there be one in the future?

Not that I'm aware of. Chrome Dev is updated 1-2 week, and should be sufficiently bleeding edge for KITE testing.

the document states canary on ubuntu so we wanted tot be sure you would be ok with something else.
we would then be testing dev on ubuntu and canary on every other OS. Can you confirm you are OK with that, please.

Yes, testing on dev instead of canary is fine. Dev is typically only a few days behind canary.


whitepaper v1.0 improvements

future version should expand on the section "Economic sustainability" (it is mentioned there: We will publish a TomoChain economic analysis and proposal, separate from this technical paper in a later date)

typo in "enables a more incentive equality between stakers:"

typo fixed in thanhson1085@322abd8e594c38f8d34623b937f7439c106b7918


bug: nightly builds broken

See https://github.com/mage-os/generate-mirror-repo-js/actions/runs/10160780327/job/28097837609#step:8:113
/home/runner/work/generate-mirror-repo-js/generate-mirror-repo-js/src/release-branch-build-tools.js:104
    throw Error(`Unable to determine branch release version for input version "${version}"`)
          ^

Error: Unable to determine branch release version for input version "main"
    at calcNightlyBuildPackageBaseVersion (/home/runner/work/generate-mirror-repo-js/generate-mirror-repo-js/src/release-branch-build-tools.js:[104](https://github.com/mage-os/generate-mirror-repo-js/actions/runs/10160780327/job/28097837609#step:8:105):11)
    at transformVersionsToNightlyBuildVersion (/home/runner/work/generate-mirror-repo-js/generate-mirror-repo-js/src/release-branch-build-tools.js:99:29)
    at /home/runner/work/generate-mirror-repo-js/generate-mirror-repo-js/src/release-branch-build-tools.js:93:20
    at Array.reduce (<anonymous>)
    at transformVersionsToNightlyBuildVersions (/home/runner/work/generate-mirror-repo-js/generate-mirror-repo-js/src/release-branch-build-tools.js:92:43)
    at getPackageVersionsForBuildInstructions (/home/runner/work/generate-mirror-repo-js/generate-mirror-repo-js/src/release-branch-build-tools.js:80:10)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async processBuildInstructions (/home/runner/work/generate-mirror-repo-js/generate-mirror-repo-js/src/release-branch-build-tools.js:179:27)
Error: Process completed with exit code 1.

This appears to be happening because module commerce-data-export has no tags upstream:
Basing https://github.com/mage-os/mirror-commerce-data-export.git package versions on those from reference main
Inspecting Commerce Data Export Packages
Inspecting Commerce Data Export Metapackage

The change I made in https://github.com/mage-os/generate-mirror-repo-js/pull/165/files didn't help -- just shifted the error to a different code point. I don't understand the nightly build process well enough yet to know how it previously worked without tags. There are references to fallbackVersion for nightly builds, but the errors happen prior to that code point.
Possibly a regression in https://github.com/mage-os/generate-mirror-repo-js/pull/110 but I haven't pinpointed what/how.

It worked once upon a time; was discussed on Discord 2022-10-04: https://discordapp.com/channels/893449664093904936/950670671145467924/1026878893040336938
But frankly I'm not sure if this is worth the effort of fixing. commerce-data-export is a set of Sensei dependency modules that happen to be available to open source but not installed by default. We're not going to get any version or tag data from upstream because it's not a part of the normal Magento Open Source releases.

As far as I understand, commerce-data-export was removed in #172, but now the error is
Run cd satis && bin/satis build /tmp/satis.json ../build && cd -
Scanning packages

In ArtifactRepository.php line 142:

  Failed loading package in ../build/packages/magento/security-package-develo
  p.zip: Invalid version string "develop"

In VersionParser.php line 186:

  Invalid version string "develop"

build [--repository-url REPOSITORY-URL] [--repository-strict] [--no-html-output] [--skip-errors] [--stats] [--minify] [--] [<file> [<output-dir> [<packages>...]]]

I've noticed that, in the "generate the packages for the composer repo" I've notices that there's a reference to "develop":

could it be related?


Missing set function for 2.8

This is the followup of #1002 for 2.8

This PR is opened against 2.8 so it can be safely merged.

PR is incorrect


Remove kubelet ServiceMonitor

We should remove kubelet ServiceMonitor (and maybe others too) from service-monitor.yaml as it's conflicting with the one from fury-kubernetes-monitoring and causes false positives TargetDown alerts.

Hi Luca. You're right.
I see the kubelet ServiceMonitor inside the istio offering relabels some metrics:

I think that fury-kubernetes-monitoring kubelet ServiceMonitor needs some improving as also kube-prometheus is doing the same.

I think that fury-kubernetes-monitoring kubelet ServiceMonitor needs some improving as also kube-prometheus is doing the same.

Uhmmm i see.
So, i will add this task to my todo list. Thanks @lnovara

I think that fury-kubernetes-monitoring kubelet ServiceMonitor needs some improving as also kube-prometheus is doing the same.

I found the commit adding that part: https://github.com/coreos/kube-prometheus/commit/e4991fe7e5728ce9a7945f26f9b3e09f226b8e09
I can apply this git patch. But... i think it's going to be better to fully upgrade the package. What do you think?

I think it's better to include this patch during the fury-kubernetes-monitoring upgrade.

I think it's better to include this patch during the fury-kubernetes-monitoring upgrade.

Totally agree!


Changing sign of wrist y-position in Kinematic Chains docs

Hello! Thank you for your work on the kineticstoolkit and this fantastic repo of documentation. It's been an incredibly helpful resource to me!
I was working through the examples in 9.4 Kinematic Chains and came across one minor part of the documentation that I believe needs updating (and if not, I'd love to better understand). Specifically, the y-position of the wrist in the forearm coordinate system is currently set to 0.34. Using that position, when I calculate the global positions of the shoulder, elbow, and wrist (following the examples in 9.3.3), and plot them, they look like this.

Since Fig 9.4 defines the y-axis in the vertical direction, I believe that the y-position of the wrist, relative to the forearm, should be -0.34. When I make that update and re-plot the global joint positions, the shape of the arm matches the form of Fig 9.4.

For reference, this is the plotting script that I used.
import matplotlib.pyplot as plt
import numpy as np

global_p_forearm = global_T_forearm[:, :, 3]
global_p_upperarm = global_T_upperarm[:, :, 3]

# arm segments
x = np.array([global_p_upperarm[0, 0], global_p_forearm[0, 0], global_p_wrist[0, 0]])
y = np.array([global_p_upperarm[0, 1], global_p_forearm[0, 1], global_p_wrist[0, 1]])

plt.plot(x, y, c="grey")
plt.scatter(global_p_upperarm[:, 0], global_p_upperarm[:, 1], label="upperarm")
plt.scatter(global_p_forearm[:, 0], global_p_forearm[:, 1], label="forearm")
plt.scatter(global_p_wrist[:, 0], global_p_wrist[:, 1], label="wrist")

plt.legend()
plt.xlim(0, .8)
plt.ylim(0, .8);

Thank you!

Hi @collinprather
Thank you very much for this correction! You are absolutely right, this was an error in the doc. I merged your pull request, it will be integrated to the website in the following hours.
I'm very happy that the website is helpful to you, these comments are my main reward and they are important to me, so thanks for letting me know :-)


fix: data URI for image/svg+xml

What kind of change does this PR introduce?
bugfix https://github.com/webpack-contrib/css-loader/issues/1342
Did you add tests for your changes?
yes
Does this PR introduce a breaking change?
no
What needs to be documented once your changes are merged?
nothing

Thanks


Complete translation to simplified Chinese.

I have translated all files except tz.php.

I haven't been able to decide if the translation should reflect the names of proper nouns such as weapons or stages.
I know that at least some Chinese (including traditional Chinese) speakers have used the English version of game copy.
I also know that some of them use the Japanese version.
May be their "maximum common denominator of happiness" is to keep their English names.
(There's a statement on the wiki based on this premise, I wrote.)
If your translation is already widely used in the Chinese community, I have no objection to it.

Perhaps "median" is "中位置" (in Japanese, "中央値")

Yes, it should be “中位值” instead. I had a typo here.

Perhaps the translation of "mode" is not correct.
"Mode" is the "most frequently appearing value" (in Japanese, "最頻値").
For example, the dataset is "1 1 2 3 4 5 6",
min = 1
max = 6
average = 3.143
median = 3
mode = 1 (because only "1" appears twice)

Right, I didn't get it right. It should be “众数” instead。

The "MMMM y" is a format for the year and month (e.g., "January 2020") in ICU format.
This format is probably "2020年1月" in Chinese, the same as in Japanese.
If so, this sould be 'y\'年\'M\'月\''.

Yes, I'll update it.

I haven't been able to decide if the translation should reflect the names of proper nouns such as weapons or stages.
I know that at least some Chinese (including traditional Chinese) speakers have used the English version of game copy.
I also know that some of them use the Japanese version.
May be their "maximum common denominator of happiness" is to keep their English names.
(There's a statement on the wiki based on this premise, I wrote.)
If your translation is already widely used in the Chinese community, I have no objection to it.

Yes, it's really hard for me to decide, too. But according to posts and game videos from Chinese community. I think most of them are using the translations(meaning) of Japanese version. Therefore, I translated them based on Japanese version which I think should be accepted by most Chinese players.

If you don't need to express the plural (like Japanese lang.), you can use like '{n,plural,=1{battle} other{battles}}' => '对战',
https://github.com/fetus-hina/stat.ink/blob/3a8aa9a11d0984d27ccf15cbf5ef090814b30188/messages/ja/app.php#L604-L605

Cool, this is good to know.

Thank you for your hard work!
This pull-request has merged and will deploy soon.


The Japanese translation of “Pull request” is incorrect.

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

Example

https://docs.github.com/ja/get-started/using-github/github-flow#:~:text=発生しません。-,プルリクウェスト,-を作成する

Affected Articles (TOO MANY)

https://docs.github.com/ja/search?query=プルリクウェスト

What changes are you suggesting?
Pull request is called “プルリクエスト” in Japanese.
"プルリクウェスト" is an incorrect.
Additional information

InCorrect

Correct

@isso-719 Thanks for reaching out, and flagging this! Since we us an internal, automated solution for our translated docs, I will flag your request for our team 💛
For more information on translations, please see https://github.com/github/docs/blob/main/contributing/types-of-contributions.md#earth_asia-translations ✨


AMP <IP_ADDRESS> new install not populating generic templates in instance creation list

Bug Report
System Information

Various
<IP_ADDRESS>
Mainline

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms
A number of people installing a new AMP <IP_ADDRESS> have reported not having any generic templates showing in the instance creation dropdown. A Fetch Latest is required to populate the list.
Known to occur on both Linux and Windows systems.
Reproduction

See above.

How do you perform a "A Fetch Latest" ? I'm having the same issue.

Fixed in CI, ADS now updates that list on start again.


Multi trigger fix

https://github.com/ant-design/ant-design/issues/8720

Coverage increased (+0.2%) to 56.89% when pulling 5fc6678486d7e8367d901ae2e81e471771feb243 on multiTriggerFix into 558ac87a7ac0adbd6743753259d54fa8c5236a70 on master.

Coverage increased (+0.2%) to 56.89% when pulling 5fc6678486d7e8367d901ae2e81e471771feb243 on multiTriggerFix into 558ac87a7ac0adbd6743753259d54fa8c5236a70 on master.


Wait-Event - Adding -TimeSpan

Adding a -TimeSpan parameter to Wait-Event (Fixes #19704).  This allows more granularity in waiting on events.
Additionally, changed the polling interval within the command to be 1/100th of the timespan.
These changes improve the performance of Wait-Event substantially, as Wait-Event was always going to wait at least 1/5th of a second.
Due to requests for this to include an argument transformation attribute, this also fixes #20112 .
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

tests are missing

@SteveL-MSFT  added a test

@PowerShell/wg-powershell-cmdlets reviewed this, we agree that the desired behavior is for -TimeoutSec to take a [TimeSpan] and having a parameter type convertor that accepts an int  (to maintain existing behavior) or a double, so that partial seconds could be specified rather than having an additional parameter.

@StartAutomating can you review the CodeFactor issues?  Also, CI isn't passing.

@SteveL-MSFT

@StartAutomating can you review the CodeFactor issues? Also, CI isn't passing.

Fixed.
Please let me know if you'd like some tests on the ArgumentTransform attribute as well.

@SteveL-MSFT thanks for the approval, however, I was still planning on making the [ArgumentTransform] a bit better.
If this isn't fully merged, please let me do that this week.

@StartAutomating removing the community day label until you are ready


Functional Testing Sites

Key points:

Test all the baseline policies
Test different use cases and edge cases

For each policy verify if the output as expected when the tests pass/fail
For policies with multiple settings check that only the expected sub-policy will pass/fail and the other
dependent/independent policies are unaffected

Perform tests to verify multiple OU and OU inheritance settings wherever applicable
Perform tests to verify Group settings wherever applicable

Works as expected.


mean_samples_leaf does not do what it's suppose to do

min_samples_leaf=20 should ensure that we never do a split that would result in less than 20 samples in each of the two resulting leaves.
Our current implementation does not split nodes with less than 20 samples which is not the same. Our current implementation is akin to the min_samples_split of scikit-learn trees which is not a good hyperparameter to control over-fitting.
I am working on a fix.

min_samples_leaf is now doing what it's supposed to do (I think) but pygbm is still not 100% consistent with LightGBM. So #32 is not resolved yet.


Google sheet Sync error

Hello
In Defect Dojo, I've done Google Sheets synchronization. When I create a file in my drive, everything works well, but when I try to sync that file, it gives me an error.
Error:   ["'' value has an invalid format. It must be in YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ] format."]

Where are you seeing this error, please provide details as requested in the bug report template.

Hello,
When I try to sync a document with my drive, I get the following error.
Kindly find the attached Snapshot of the error.

Deployment method -- Docker

On which version are you? There has been a bug with empty values in Google sheets that have been fixed with 2.2.0. If you are on an older version, please upgrade to 2.2.1

@MHarsh24 what was the situation, upgrading?


Permit ReagentEffect PopupMessage to access the solutionEntity it occurs in.

About the PR
This patch allows the PopupMessage ReagentEffect to make use of the SolutionEntity (and possibly the OrganEntity) where it happens in, allowing for messages like { $entity } sweats. when a reagent is present within a person.
With this, you could have:
      - !type:PopupMessage
        type: Pvs
        visualType: Small
        messages: [ "sweat" ]

sweat = {CAPITALIZE($entity)} sweats!

And this will work. It'll be like DiseasePopUp, except for reagents.

Seems good, but how do popups handle getting more fields than they expect? At some point the behavior would error out completely and just display the loc string value, but I think I may have seen it change recently were it'll display as much of the string as it can instead of zzz-(loc line)

Is there an actual usecase for this in the PR?

Is there an actual usecase for this incoming?

several popups could use a third person variant.
examples:
buzzochloricbees-effect-histamine-swells = You swell like a balloon in the presence of the bees.
effect-sleepy = You feel a bit sleepy.


YARN-11434. [Router] UGI conf doesn't read user overridden configurations on Router startup.

Description of PR
JIRA: YARN-11434. [Router] UGI conf doesn't read user overridden configurations on Router startup.
How was this patch tested?
For code changes:

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

:confetti_ball: +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  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 16s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 48s

trunk passed

+1 :green_heart:
compile
1m 55s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
1m 42s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
0m 52s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 47s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 17s

trunk passed

+1 :green_heart:
shadedclient
29m 12s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
1m 52s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
1m 52s

the patch passed

+1 :green_heart:
compile
1m 44s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
1m 44s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 47s

the patch passed

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
javadoc
0m 39s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 37s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 22s

the patch passed

+1 :green_heart:
shadedclient
28m 44s

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

_ Other Tests _

+1 :green_heart:
unit
0m 24s

hadoop-yarn-server-router in the patch passed.

+1 :green_heart:
unit
0m 39s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

120m 29s

Subsystem
Report/Notes

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

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

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

uname
Linux 653ca0226cdc 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d259d280fbcb3e2e8e3b2cde62ab18c60b9fa4bc

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server

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

Docker mode activated.

-1 :x:
patch
0m 19s

https://github.com/apache/hadoop/pull/6011 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/6011

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

versions
git=2.17.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

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

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 26s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 30s

trunk passed

+1 :green_heart:
compile
1m 38s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
1m 30s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 49s

trunk passed

+1 :green_heart:
mvnsite
0m 52s

trunk passed

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 47s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 15s

trunk passed

+1 :green_heart:
shadedclient
21m  6s

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

-0 :warning:
patch
21m 24s

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 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
1m 32s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
1m 32s

the patch passed

+1 :green_heart:
compile
1m 21s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
1m 21s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 42s

the patch passed

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
javadoc
0m 38s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 35s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 15s

the patch passed

+1 :green_heart:
shadedclient
21m  1s

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

_ Other Tests _

+1 :green_heart:
unit
0m 24s

hadoop-yarn-server-router in the patch passed.

+1 :green_heart:
unit
0m 36s

hadoop-yarn-server-globalpolicygenerator in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

97m 26s

Subsystem
Report/Notes

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

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

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

uname
Linux e3398fbd9800 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c5b19a2154e16101cfc68f3bbde56fffbeaecdd9

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-router hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-globalpolicygenerator U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server

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

@goiri Can you help review this pr? Thank you very much! This pr  is based on the completion of YARN-9668. UGI conf doesn't read user overridden configurations on RM and NM startup.

@goiri Thank you very much for your help in reviewing the code!


Test and check compatibility with RDKit 2023.03.1

https://github.com/rdkit/rdkit/releases/tag/Release_2023_03_1

Enable latest rdkit in the test
Remove oldest rdkit from the test
Update the README and doc

I have dibs on this one!


x/text/message: Print, Println funcs do not do any language-specific formatting

What version of Go are you using (go version)?

$ go version
on Playground and in Docker

Does this issue reproduce with the latest release?
I don't know because I didn't use it before
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
on Playground and in Docker

What did you do?
package main

import (
	"golang.org/x/text/language"
	"golang.org/x/text/message"
	"os"
)

func main() {
	message.SetString(language.Dutch, "soccer", "voetbal")
	p := message.NewPrinter(language.Dutch)
	p.Println("soccer")
	p.Fprintln(os.Stdout, "soccer")
	p.Print("soccer", "\n")
	p.Printf("soccer", "\n")

}

https://play.golang.org/p/LjQ6DfG1CJX
What did you expect to see?
voetbal
voetbal
voetbal
voetbal
What did you see instead?
soccer
soccer
soccer
voetbal

cc @mpvl
should the verbs in https://go.googlesource.com/text/+/refs/heads/master/message/print.go#969 and https://go.googlesource.com/text/+/refs/heads/master/message/print.go#981 be 'm' instead of 'v'?


Migrating to Djs V14

Sub Tasks

[x] Check Out the Breaking changes of V14.
[ ] #33
[ ] #35
[ ] Make an event handler to handle my events separately.
[ ] Try making use of mongo db for scalable purposes.
[ ] Merge the v14 with dev and dev with main. (Obviously Do multiple checks Before that.)

Inactive / Stale


Interrogate has a lower bound on the Click version it can use

Environment

interrogate version(s) (interrogate --version: 1.4.0
Operating System(s): Linux
Python version(s): 3.6.8

Description of the bug
I have a project that uses a particularly old version of Click (v6.7). In version 1.3.0 of interrogate, this is fine, but version 1.4.0 uses the case_sensitive option in click.Choice(), which isn't present in that version.
This isn't a problem with interrogate, as it's perfectly reasonable behaviour, but I think it's reasonable to declare that Click needs to be version 7.x and up.
What you expected to happen
I expected that, at install time, pip would indicate that interrogate requires at least Click v7 and up and that this wasn't being met currently.
How to reproduce (as minimally and precisely as possible)
In a virtual env, install Click v6.7, then install interrogate. Invoking interrogate will cause a stack trace.
Anthing else we need to know?
Not a functional problem with interrogate as such; this is a packaging nicety.

Change merged (thank you, @econchick )! This can be closed out, I think.


Add support for relative term condition (#160)

Thanks! Will merge when the new version is released.

Closing in favor of #167.


L515 not showing up in Unity

Required Info

Camera Model
{L515}

Firmware Version
(<IP_ADDRESS>)

Operating System & Version
{Win (10)

Kernel Version (Linux Only)

Platform
Unity

SDK Version
{ 2.36 }

Language
{unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<I am getting the "Start Here" scene to open in Unity 2018, but the L515 will not show up once the Scene is in Play mode.  This happens in other provided scenes as well.  I get the message "Connect Sensor" but I have the L515 plugged into the computer on the provided USB3 to USBC cable.
I can see the L515 in the RealSense viewer 2.36 using firmware <IP_ADDRESS> so it is working otherwise.  Is the sensor not recognized by Unity yet?
Thanks for any help in advanced.  I'm looking to do some trajectory mapping with the device and SLAM scanning.  If anyone can guide me to a better method than Unity, for a non-programmer, let me know.  I'm wanting to access the trajectory and associate it with other sensors plugged into the laptop.>

Hi @VisibleMeasurement
Were you able to try the PR mentioned by dorodnic?

I pulled down the development branch and tried to open the Unity scene provided using the new download.  However, it still doesn't recognize the L515.  I did notice that I am having to load the same unitypackage file as before, so that might be a problem.
I am teaching myself how to compile the code, but it's taking me a while, I've never done that before.  I'm a power PC user but not a programmer.  I'll let you know if I have any success.

Hi @VisibleMeasurement
Please try the Unity Package from v2.37.0 pre-release

Hello, Ive installed the 2.37 prerelease sdk and 2.37pr unity package.  My 515L has <IP_ADDRESS> firmware.  Works with realsense viewer 2.37.  Unity 2019.3.13 Windows10.  Also tried to build from source but ran into atlcom.h missing headers, reinstalled visual studio 2019 but same problem.
In unity when running the DepthAndColor scene (that works with my D455) the error message when trying to connect either with or without "requested serial number" is:
ExternalException: rs2_pipeline_start_with_config(pipe:000002062D592D40, config:000002062D592BE0)
Rethrow as Exception: Couldn't resolve requests
Intel.RealSense.ErrorMarshaler.MarshalNativeToManaged (System.IntPtr pNativeData) (at <782525f085c64debb7028293360b3d39>:0)
Intel.RealSense.Pipeline.Start (Intel.RealSense.Config cfg) (at <782525f085c64debb7028293360b3d39>:0)
RsDevice.OnEnable () (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:71)

It took a while to get to it, but I did get the camera to work with the default scene and the new unity package.  It mimics the function of the realsense viewer.

Now that the Unity package was merged, is there anything else that is needed on this one?
*If we don’t hear from you in 7 days, this issue will be closed.

This is closed for me, thank you for the help.

is L515 supported as for today?


[BC Idea]: Allow debugging any first level app

BC Idea Link
https://experience.dynamics.com/ideas/idea/?ideaid=4b814ed7-0986-ef11-9443-6045bdb37955
Description
Some Apps from Microsoft set resource exposure policies to not allow debugging. from a developer experience perspective, this is not good and makes troubleshooting and traceability very difficult.
apps that do not allow debugging: https://github.com/search?q=repo%3Amicrosoft%2FALAppExtensions "allowDebugging"%3A false&type=code
I will provide the implementation for this BC Idea

[X] I will provide the implementation for this BC Idea

I will approve this issue, as flipping a flag on the property is a really cheap thing to do. But once we have a PR, we must look into if there was a reason to disallow debugging. Based on your query, I could tell that there are a few where it definitely wouldn't be a problem to change allowdebugging to true - but I cannot guarantee that's true for all of our apps.


Add basic sample of options pattern

Take the code from https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/filters
public MyActionFilterAttribute(IOptions<PositionOptions> options)

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

ID: ed39cb0e-aa85-8bba-ffb4-859b56a60723
Version Independent ID: dc7e3449-650b-d117-5eac-69e5ccb250cb
Content: Options pattern in ASP.NET Core
Content Source: aspnetcore/fundamentals/configuration/options.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @guardrex
Microsoft Alias: riande

Tracked in Options pattern master issue: Check here first #18291


Cluster styles

Location or cluster of locations on a cluster layer may only be represented by a symbol.
This symbol for location and cluster is currently defined by marker and markerMulti respectively. Each of these are a style object similar to the default / highlight style used for non-cluster layer.
There is a scale property which is used to scale a symbol.
There are markerMin/Max settings which can be defined inside the marker, markerMulti, and theme styles.
The markerMin and markerMax define the size range symbols. A single location will be drawn at the size of markerMin. A cluster will be drawn at a size according to the ratio of locations inside the cluster against the largest cluster in the viewport. The largest cluster in the viewport will be drawn at the markerMax size.
marker definitions are exactly the same as a default style definition for other types of layer. marker should be renamed to default to be in line with other layer style definitions.
markerMin needs to go. markerMin being the size of a single location. scale and size should be added to the default style and any other symbol styles.
Openlayers only understands scale to scale a symbol. Size should be introduced in addition to scale. Size should be defined as pixel. The size should be the average of width and height of a symbol. The size can then be used to scale a symbol.
markerMulti should be renamed to cluster as it only applies to cluster. The scale / size inside the cluster is the maxSize.
This allows for locations to be defined as default, cluster, in a theme, or as highlight.
Object assign applies in this order.
The default style will be applied to single locations.
The cluster style will be assigned to the default style for cluster. As a minimum we only need to define a scale or size in the cluster.
A theme style will either be applied to the default or default + cluster style for graduated themes or if all locations in a categorized theme are of the same type.
The highlight style will be assigned to the previously created style for when a location of cluster is highlighted. As a minimum we only need to set a scale or size in the highlight style.

An example style would be:
style: {
  default: {
    svg: 'https://...',
    size: 20
  },
  cluster: {
    size: 50
  },
  highlight: {
    scale: 1.2
  }

I would expect this style to work with a cluster as well as with an mvt layer. The mvt layer would just ignore the cluster style.
On a cluster layer I would expect the same symbol to be used for locations and cluster of locations.
A location symbol would be sized 20 pixel and the biggest cluster would be sized as 50 pixel. Cluster in between would be sized according to the ratio. Lets say the biggest cluster of 50 locations is sized at 50 pixel. A cluster of 25 locations should be sized 35pixel, half between 20 and 50 pixel.
A highlighted symbol should be 20% bigger than the original symbol for either location or cluster.
I would like for scale or size or both to work in either style definition.

marker renamed to default. I kept marker property in mvt/geojson styling though.
markerMulti renamed to cluster.
cluster inherits default but gets scale: 1.2 to make it slightly larger. Parameters can be overridden if style distinction is needed.
highlight inherits previous values but gets default scale: 1.3 - please note scale on highlight is slightly higher to prevent scaled icon from shrinking on interaction.
All styling can have size value and will grow proportionately for clusters, but layer.style.cluster.size is the maximum value cluster size can get. Default => size: 20
scale is now a friendlier number. Defaults to 1, can be set to anything.
Let me know how this works out and if any improvement is needed.
All added to docs.

Cluster styles have now a property clusterScale. The default is 2. The clusterScale defines the size which is applied to the largest cluster in the mapview.


Fix the readme so it has more info

I want to see more info on how to use github.

lets add more info. I will work on this, thanks!

Included with pre-release v0.0.1-alpha


key lengths clarification

I must be misunderstanding the requirement here. Can you advise? In my code, I generate a 256-bit key using a PasswordBasedKeyDerivation, but then it fails inside the CheckedKeyChain because it is not 32-bits long. See attached image for a shot of a debug session where I'm looking at the CryptoConfig for KEY_256:

My apologies - I clearly need to read a bit more carefully before my haste comes back to byte me.


Showing Error

{
"responseStatus": "error",
"errorResp": "Request failed with status code 426",
"data": "null"
}
"I have also tried logging in again but showing same error"

Your login may expired

Already tried logging many times.

follow this https://github.com/sumithemmadi/truecallerjs#login
use truecaller file to login and try again


PP-139 Facet ordering with last_update enabled for libraries

Description
Added a migration to retrospectively enable it for all libraries.
The admin panel will now show the additional ordering facet type.

Motivation and Context
Aspen OPDS2 feeds need to be sorted by "update time", we already have this data locally within the licensepool.last_checked and the work.last_update_time attributes. The Work.last_update_time attribute gets indexed in the search indexed which enables the facet ordering.

How Has This Been Tested?
Manually ran the migrations, and tested ordering.
Unit tests have been written for the migration.

Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

For this one, I don't think we need to add a data migration...
We don't serialize the defaults out to the database, in the dict() method of the settings class. Specifically for occasions like this, where we want to update defaults, so we don't need to use a migration.
That way if someone has changed the defaults, they keep their settings, but if they are using the defaults they get the new defaults.
The question arises, what happens if someone changes the defaults, and removes ORDER_LAST_UPDATE, but that question is the same with this PR. After the migration and site would be free to do that, and it might break the Aspin indexing.
I think adding this as a default is a good first step here, without a migration, then we can continue to iterate on this.

Since overriding the defaults would break the entire premise of the PR I have discarded the given approach for a less elegant but more robust solution.
The ORDER_LAST_UPDATE facet is manually added during the Facets.available_facets method, thereby skipping the Admin UI entirely, making it impossible for a user to remove the new sorting.
The new sort order will still show up in the feed and hence the Mobile Apps.

I've been thinking about this one a bit, and I think the solution here is that instead of adding the facets to the feed, we should just be directing Aspin to use the crawlable feed, which I believe has all the facets enabled by default. That would let them sort by last_updated, without us having to add these facets to the feed that our apps consume.
The biggest change we would need is that the crawlable feed would have to respond with OPDS2. Does that make sense to you @RishiDiwanTT?
Can you do some testing and make sure the crawlable feed gives us all the facets that aspin currently uses?

Closed this PR in favour of the crawlable endpoint


7 days to die, cannot install

Starting process: /var/lib/pufferpanel/binaries/dotnet-runtime/dotnet /var/lib/pufferpanel/binaries/depotdownloader/DepotDownloader.dll -app 294420 -dir /var/lib/pufferpanel/servers/50b441ef
=No username given. Using anonymous account with dedicated server subscription.
Connecting to Steam3... Done!
Logging anonymously into Steam3... Done!
Using Steam3 suggested CellID: 41
Got AppInfo for 294420
Using app branch: 'Public'.
Warning: Depot 294422 does not have branch named "Public". Trying public branch.
Depot 294422 () missing public subsection or manifest section.
Total downloaded: 0 bytes (0 bytes uncompressed) from 0 depots
Disconnected from Steam
DAEMON
Executing: chmod +x 7DaysToDieServer.x86_64
DAEMON
Starting process: /usr/bin/chmod +x 7DaysToDieServer.x86_64
chmod: cannot access '7DaysToDieServer.x86_64': No such file or directory
DAEMON
Server installed

You'll need to download a dev version of DepotDownloader (DepotDownloader-Windows-framework.zip from https://github.com/SteamRE/DepotDownloader/actions/runs/5153489983) and place the extracted files into /var/lib/pufferpanel/binaries/depotdownloader/