Nice disasm

This is a long-requested feature.  It should make disassembly more readable.
It might enhance testabilty for SPIR-V generators since it will make it easier to write matchers against disassembled output.

I made up a simple scheme for driving names for types.  It does not necessarily match any single programming language, but it is highly regular in places.

+1

All issues addressed in #269.

#269 was merged.


[BUG] Not pasting the email id and continuously clicking "Next"

Before submitting a bug report...

[X] This bug wasn't already reported.
(I have checked every bug report on GitHub)

Title

[X] The title is no longer "[BUG] Title" and I edited it with the right error name.

Describe the bug
While trying to loging-in it is continuously hitting "Next" button without pasting the email-id
Copy and paste your error
2024-06-03 03:56:31,768 [ERROR] ElementNotInteractableException: Message: element not interactable
(Session info: chrome=125.0.6422.141)
Stacktrace:
GetHandleVerifier [0x00CAB8E3+45827]
(No symbol) [0x00C3DCC4]
(No symbol) [0x00B3138D]
(No symbol) [0x00B6CED9]
(No symbol) [0x00B6B825]
(No symbol) [0x00B92DFC]
(No symbol) [0x00B68075]
(No symbol) [0x00B93094]
(No symbol) [0x00BAC034]
(No symbol) [0x00B92B96]
(No symbol) [0x00B66998]
(No symbol) [0x00B6751D]
GetHandleVerifier [0x00F64513+2899763]
GetHandleVerifier [0x00FB793D+3240797]
GetHandleVerifier [0x00D313B4+593364]
GetHandleVerifier [0x00D382DC+621820]
(No symbol) [0x00C470A4]
(No symbol) [0x00C437A8]
(No symbol) [0x00C43947]
(No symbol) [0x00C359FE]
BaseThreadInitThunk [0x75D17BA9+25]
RtlInitializeExceptionChain [0x7742BD2B+107]
RtlClearBits [0x7742BCAF+191]
Traceback (most recent call last):
File "C:\Users\Mohi\Downloads\Microsoft-Rewards-Farmer-master\Microsoft-Rewards-Farmer-master\main.py", line 24, in main
executeBot(currentAccount, notifier, args)
File "C:\Users\Mohi\Downloads\Microsoft-Rewards-Farmer-master\Microsoft-Rewards-Farmer-master\main.py", line 128, in executeBot
accountPointsCounter = Login(desktopBrowser).login()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Mohi\Downloads\Microsoft-Rewards-Farmer-master\Microsoft-Rewards-Farmer-master\src\login.py", line 37, in login
self.executeLogin()
File "C:\Users\Mohi\Downloads\Microsoft-Rewards-Farmer-master\Microsoft-Rewards-Farmer-master\src\login.py", line 53, in executeLogin
self.webdriver.find_element(By.NAME, "loginfmt").send_keys(
File "C:\Users\Mohi\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\remote\webelement.py", line 231, in send_keys
self._execute(
File "C:\Users\Mohi\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\remote\webelement.py", line 395, in _execute
return self._parent.execute(command, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Mohi\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\remote\webdriver.py", line 348, in execute
self.error_handler.check_response(response)
File "C:\Users\Mohi\AppData\Local\Programs\Python\Python312\Lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 229, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.ElementNotInteractableException: Message: element not interactable
(Session info: chrome=125.0.6422.141)
Stacktrace:
GetHandleVerifier [0x00CAB8E3+45827]
(No symbol) [0x00C3DCC4]
(No symbol) [0x00B3138D]
(No symbol) [0x00B6CED9]
(No symbol) [0x00B6B825]
(No symbol) [0x00B92DFC]
(No symbol) [0x00B68075]
(No symbol) [0x00B93094]
(No symbol) [0x00BAC034]
(No symbol) [0x00B92B96]
(No symbol) [0x00B66998]
(No symbol) [0x00B6751D]
GetHandleVerifier [0x00F64513+2899763]
GetHandleVerifier [0x00FB793D+3240797]
GetHandleVerifier [0x00D313B4+593364]
GetHandleVerifier [0x00D382DC+621820]
(No symbol) [0x00C470A4]
(No symbol) [0x00C437A8]
(No symbol) [0x00C43947]
(No symbol) [0x00C359FE]
BaseThreadInitThunk [0x75D17BA9+25]
RtlInitializeExceptionChain [0x7742BD2B+107]
RtlClearBits [0x7742BCAF+191]
Screenshots

Value of dashboard variable

the same problem, I think Microsoft has changed something in authorization

I'm pretty sure is because the CSS class that is used to check the mail field (.find_element(By.ID, f"{id}") has been changed, I've checked in the code but I'm too dumb to understand anything, the only thing I know is that now the id of the field is something like this "iNNNN" where N stands for a random number, where before was like "userInput" or smth like that hopefully it get fixed soon .-.

To those here I'd move to: https://github.com/klept0/MS-Rewards-Farmer


PEP 8 Fix

Thanks! I will add CI at some point so this is checked for automatically. Just not had the chance yet.


Get rid of stevedore

Stevedore is not adapted to subliminal as it doen't support registering / unregistering providers.
Instead, use a similar approach as babelfish: https://github.com/Diaoul/babelfish/blob/master/babelfish/converters/init.py#L206

Rather than removing stevedore I subclassed it to fit subliminal's need without needing to re-implement too much logic around setuptools's entry points.
Fixed with 101da7367eeb5f4e27c0a7a97ab2dfd6dfc4363a
@pannal: this next version will be easier for you to work with hopefully. Would be nice if you could provide some feedback on this :+1:


[Forwardport]: Update error

Original PR:
https://github.com/rancher/rancher/pull/34939

We don't use master branch right now.


Routing Between GPS coordinates

The GPS coordinate look-up in map.project-osrm.de is producing results that may deviate far from the entered GPS coordinates.
When entering the coordinates 34.129382,-118.141254 and 34.124382,-118.141254 into the textfields, the route starts more than a block from the entered coordinate. (see).
The correct route should be like this.
So If I enter the GPS coordinates by hand into the URL, the results are just as expected. Entering them in src/dst fields, the deviation at the source is more than a block.
@amyleew could you take a look at this?

/cc @perliedman
I think what is happening here is that the coordinate is first send to Nominatim who snapps it to the nearest address. However it should be the other way around:
Coordinate -> OSRM -> Snapped coordinate -> Nominatim


add noindex option to mzoon build

for example, i don't want my staging deployments to be indexed

There is the method Frontend::index_by_robots. Is it what you meant? If so, please close the issue.
async fn frontend() -> Frontend {
    Frontend::new()
        .index_by_robots(false)
        .title("My app")
        ....

Implementation details:
https://github.com/MoonZoon/MoonZoon/blob/0279065c57a5637f464ccd1adb0ddd1f331de2c7/crates/moon/src/frontend.rs#L46
https://github.com/MoonZoon/MoonZoon/blob/0279065c57a5637f464ccd1adb0ddd1f331de2c7/crates/moon/src/frontend.rs#L87-L91

yes this is close, i want this exposed as a configuration option to mzoon build, i'll try to open a pr for it

@MartinKavik actually i don't think i can do this alone, how would i add a new env var for mzoon build NOINDEX=1 and thread it through to index_by_robots? an env var is ideal so i can set it to avoid indexing my staging deployment

I've just tested the code:
Frontend::new()
        .index_by_robots(not(matches!(std::option_env!("NOINDEX"), Some("1"))))

with the command
NOINDEX=1 makers mzoon start

and it seems to work without problem so I would recommend it as a workaround until I'll design & implement a better alternative.


256-bit custody atoms for better alignment with rest of the spec and greater efficiency

We previously chose 48 byte custody atoms because of the sizes of field elements in BLS signatures. However, this misalignment is not pretty when compared to the rest of the spec, and will also cause significant overhead as 48 byte integers are more expensive to handle than 32 bytes.
In comparison, the switch to 32 bytes will only require one secret re-sharing (from one prime to another prime) every nine days, so it will add only very minor overhead for MPC validators.

This should be ready for review, though I will probably go through the old tests again to make sure I haven't missed anything.

@dankrad FYI I fixed the conflicts from #1703


missing "dist" directory

I am a bit confused on the proper way to import funcunit and syn into my project.
I am using es6 modules with webpack which is attempting to load funcunit via cjs build:
I installed funcunit with:
npm install<EMAIL_ADDRESS>when I perform my build I get an error:
ERROR in ./~/funcunit/dist/cjs/funcunit.js Module not found: Error: Cannot resolve module 'syn' in .../node_modules/funcunit/dist/cjs
so i installed "syn"
npm install syn
but I still received the same error, I then saw that the git tag v0.2.0 had a "dist" folder so I installed directly from github using the v0.2.0 tag:
npm install git://github.com/bitovi/syn.git#v0.2.0
this worked, and now funcunit is working.
Should syn master branch have a dist folder?
Thanks for the great package, loving funcunit.

npm packages in the 0.1.x series have this, but 0.2.x does not.

hi @m-mujica
could you add dist to npm publish ?

hey @vitalets, sorry I'm out of the loop with this issue, but I'll take a look at the problem, I'll let you guys know when it's fixed.

It would be great! thanks a lot!

I'm going to reopen this, since adding !dist/ to .npmignore didn't work

ok guys, 0.2.2 fixes the problem with the dist folder, try that one and let me know if you find anything weird

I can confirm that now everything ok! Thanks a lot!

Confirmed. Its working for me now. Thank you.


Update software.md

Is this ready for review?

That's a question for @ethanrd. My contributions are complete and ready for review. BTW, I think the failed Markdown links check can be fixed by upgrading to Python 3.7+. At least that worked to fix the same error message that NCO was getting.

I added the cf-view text above (with minor change) to this PR (mainly just to see if it worked). So I think this PR can be merged once someone checks that my changes don't break anything.
I created another branch and PR with a few other additions and added it to issue #241. More details there, soon.

I think this one is ready to merge. Can someone take a look and merge if it looks OK?

Thanks @cofinoa !


Median Filtering After LR-Check

Start with the why:
As it stands now in the LR-Check implementation, the median filter is being applied before LR-check.  So this is very likely sub-optimal, as it is reducing per-pixel information prior to the improvement of LR-check voting on the disparity confidence and combination.
Move to the how:
Move the median filter to after the LR-check processing (instead of per each independent left and right disparity result).
Move to the what:
Support Media filtering on the output of the LR-Check disparity result.

As in https://github.com/luxonis/depthai-python/pull/284 this is now in progress and initially working:
7x7:

5x5:

3x3:

OFF:


Bump esbuild 0.12.20

Esbuild is still not ready for production. Ver 0.8.x has many issues but version 0.12.20 is very promising.

@michielvandergeest Version 0.8.x is really old. Let's bump it..

I think this should be fine ... double checking with @erikhaandrikman: anything against bumping to this version of ESbuild?
@JanSunavec just fo you to be aware, that atm we're still considering the use esbuild as lightning App bundler experimental

@michielvandergeest I know that esbuild is still not production ready. On the other hand we are able create better production build with 0.12.20 against rollup.

Any progress guys?


Implement multi-arch build for piraeus-client

Closes #74
I didn't remove the Makefile with this PR in case that's used elsewhere. If it isn't we should be able to drop it.

I saw this got some force pushes. So I suggest you get it into a state you are satisfied with and then please squash the commits, this does not need to be a series. Then I'd suggest you add myself as reviewer and assign @WanzenBug , he did the CI/workflow work.

Apologies for the delay here. Will finish my updates today.

That was 15 days ago. Do you still intend to work in this?

Hey, I would like to take this over (no idea what I'm getting in to). Is there a way for me to highjack this PR with my own branch or should I create a new one?

Hey, I would like to take this over (no idea what I'm getting in to). Is there a way for me to highjack this PR with my own branch or should I create a new one?

I'd say just create a new branch/MR and state in the description that this supersedes this ine

Wilco

Closing this one, see #84


generate_tfrecord.py

Hello Abdelrahman
I am getting an error in the file of generate_tfrecord.py in
from object_detection.utils import dataset_util from object_detection.utils import label_map_util
I checked my environment and the TF object detection, everything seems good, can you share with me what you think about this issue?
Thank you

It is because it seems like the object_detection library if you installed it from pypi uses tf1 code. You need to change line 132 in label_map_util to with tf.io.gfile.GFile(path, 'r') as fid: instead of tf.gfile.Gfile()


fixed chart dimensioning bug in ie browser

@krispo , @NameFILIP
fixes issue #158

Will this fix be merged into master? It doesn't look like it has and I'm curious why.

hm.. looks like the creator of PR has closed it and deleted the branch. @lnookl what was the reason?

Sorry, but this fix was neglected for a long time and I closed it. If you think that this fix is valuable I can do a pull request with it.


populate imu covariances when converting

🎉 New feature
Summary
This PR depends on those two other PR:

https://github.com/gazebosim/gz-sensors/pull/333
https://github.com/gazebosim/gz-msgs/pull/333

Once those are merged, this PR will allow forwarding the IMU covariance between ros <--> gz.
Checklist

[x] Signed all commits for DCO
[x] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Getting CI set up for harmonic here.  We are going to need to make sure that we #ifdef the appropriate bits because this message is only supported in harmonic+

Do you have an example of this somewhere in the code ? What is the token I should check for ? I couldn't find one.

Do you have an example of this somewhere in the code ? What is the token I should check for ? I couldn't find one.

I just pushed an implementation to your branch.  This isn't something we've really done much, so there isn't documentation on it.
I added a define based on the MAJOR version number of gz-msgs, as covariances are only available in gz-msgs10+

One more test failure here, @ejalaa12 can you take a look?
I think this repo isn't quite as subject to the freeze as there will be no harmonic/rolling binaries generated from here.

@mjcaroll, sorry for the long delay. I just pushed the fix, all checks are passing now :)


Per PR deployment of almighty on openshift?

Action Item from last sprint retrospective:

@Konrad: work with KB on getting PR deployment setup

Hi @kbsingh ,
in our last sprint retrospective, people from UI uttered the need to test against almighty-core in a specific state (e.g. a PR). The options given were:

checkout that PR locally, build it, run it

this is too complicated

run a docker-image of the PR that the UI person is interested in

currently we don't have a docker-image for every PR
we could add Make instructions on how to get this up and running, but this would require a docker setup and not everybody has that.

have an openshift pod that runs the specific PR's code

The 3rd option is the one that UI wants to have. Do you see a way to set this up in openshift? Maybe this can be setup on demand and not for all PRs? And maybe the lifetime is limited for such a pod?
@kbsingh any thoughs from you are helpful!

@kbsingh had outlined a high level UX/plan for this during the face to face.

Whenever a PR has a commit, a new instance is spawned with a url like PR-XXX.demo.almighty.io
This would be active for 24 hours.

Would be interesting to see the details churned out.

Hi,
We have an issue for this over at https://github.com/almighty/almighty-jobs/issues/11

Closed in favor of almighty/almighty-jobs#11


Add a devcontainer for GitHub CodeSpaces

Add a configuration for a devcontainer that can build Ghidra.
I am not sure if this is something that you would like in the repository,
but I built this to help with some training on Ghidra development I will
deliver and it might be useful for the project. Please close if this is not
wanted.
This integrates with GitHub and allows for creating a small VM
with the required dependencies to build Ghidra. This is useful
for remote situations (I am using this for training so students
don't need a VM locally).
This can be tested with the command line tool from GitHub
or with the web UI. Note if this is merged the --repo and --branch are
not required.
I have configured the dev container so the cost of storage and compute
is on the user, not the project. The machine is built from the specification
on demand rather than pre-built and stored (which would incur a cost
to the project).
The container has the recommended version of Java installed (17)
and Gradle. It also includes the recommended Java and C++ extensions
and the base image contains build-essential.
gh codespace create --repo cyberkaida/ghidra --branch cyberkaida-devcontainer
gh codespace code # Or gh codespace ssh if you prefer

When you are finished be sure to delete the codespace, you get
~40 hours for free I believe.
gh codespace delete

Thank you, but this is something we are not going to support at this time.


How to implement point cloud supervision？

hello，Thanks much for such an excellent work!
I saw that the paper mentioned that the supervision results of adding point clouds were analyzed. I would like to ask for some ideas or methods to implement point cloud supervision. Thank you！

This codebase follows the same organizational structure as BEVDepth. Please refer to the specific implementation of BEVDepth for details.

OK
I used “/scripts/data_converter/visual_tools.py ”to generate some ground truth, but there are some obvious errors, such as ：

What step went wrong?Thanks!

Hello, I would like to ask what the histogram drawn in section 3.1 of the paper, the horizontal axis range [-1,2], means? Does it mean the height of the horizontal plane where the radar is located as the reference? That is to say converted to [5,7]?

Hello, I have done a lot of experiments with reference to the supervision method of BEVDepth (point clouds are projected onto pictures, through minimum pooling and one hot encoding), but they cannot exceed the unsupervised results. I would like to ask about the one hot encoding part. Isn't it wrong that a discrete distribution should be set?


Require pin blocklist at the module scope

This is to facilitate some other work on module resolution. I'm running into issues with this specific change.

Well, it looks like there's some state in my working directory that's impacting this success of yarn test locally.  With a fresh clone, yarn test passes.


Update README.md

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes:

An unexpected error has occurred, could you please contact admins. Your RequestID: cd6f6a01-d020-4ee7-96f4-9134acb5a79e


FIX: Chart widget filter mobile view

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Summary
This PR fixes the unreadable style of chart-headings with filters.
Screenshots
Before (Viewport = 460px)
With description

or even more extreme with viewport 375px

Without description

After PR (Viewport = 460px)
With description

Without description

Desktop

No changes

Could you rebase this PR on the 3.1 branch, @bernhardh?
There we added support for section header actions, and it needs to work well with that.

Thanks for feedback! I will have a look at this next week :)

Yeah and 3.1 will potentially be released before this PR has been reworked already.

Thanks, @bernhardh.
I've fixed a number of cases that weren't properly handled yet.

@danharrin Why did you remove the sm:flex-row sm:items-center in your commit (https://github.com/filamentphp/filament/commit/36a1aa72abe7878293ad4dece334b4b79dab9f37#diff-4cbb45a38e248d0d4c26426ff92142f2d8d04651d2e75d1d8a4471d64657f672L61) ?
This results in having a wrong responsive behaviour of the filters again:

compared to v3.1.46

The section icon and collapsible button were not inline with the heading on mobile, if you want to reattempt a fix while keeping that in mind you can


Class description not showing anywhere in Swagger UI

I have a class description in my Swagger JSON, but I'm not seeing that description anywhere in the generated GUI.  Class properties are coming through OK.
Class1 {
id (integer, optional): Identifier property. ,
property (string, optional): Property of string type.
}
Any options for enabling this, just to provide some more description on the data model class?
"definitions" : {
    "Class1" : {
        "description" : "Data model for stuff.",
        "type" : "object",
        "properties" : {
            "id" : {
                "format" : "int32",
                "description" : "Identifier property.",
                "type" : "integer"
            },
            "property" : {
                "description" : "Property of string type.",
                "type" : "string"
            }
        }
    }
},

Given that the generated Swagger is as expected, this is really an issue for the swagger-ui folks.


Migrate to tun2

Since I have published tun2, so the wintun.rs can be deleted.
PS. I hope you can be a co-contributor and publisher of tun2. If you wish I'm happy to sending inviting.

 The problem is that I need backtrace. It is possible with thiserror itself right ?

yeah @planetoryd

PS. Hi @SajjadPourali , I hope you can be a co-contributor and publisher of tun2. If you wish I'm happy to sending inviting.

I'm certainly interested!
Thank you.

@ssrlive : Thanks! It looks good to me; however, I have some concerns about FreeBSD support since NarrowLink is officially available in the FreeBSD ports.


multi instance

Summary

Ticket Link

Codecov Report

Merging #538 into master will increase coverage by 11.93%.
The diff coverage is 23.93%.

@@             Coverage Diff             @@
##           master     #538       +/-   ##
===========================================
+ Coverage   33.92%   45.86%   +11.93%
===========================================
  Files          37       20       -17
  Lines        4604      883     -3721
===========================================
- Hits         1562      405     -1157
+ Misses       2893      449     -2444
+ Partials      149       29      -120

Impacted Files
Coverage Δ

server/utils/kvstore/cache.go
0.00% <0.00%> (ø)

server/utils/kvstore/entity.go
0.00% <0.00%> (ø)

server/utils/kvstore/id_index.go
0.00% <0.00%> (ø)

server/utils/kvstore/kvstore.go
0.00% <0.00%> (ø)

server/utils/kvstore/ots.go
0.00% <0.00%> (ø)

server/utils/kvstore/plugin_store.go
0.00% <0.00%> (ø)

server/utils/kvstore/store.go
0.00% <0.00%> (ø)

server/utils/kvstore/value_index.go
0.00% <0.00%> (ø)

server/utils/types/byte_size.go
0.00% <0.00%> (ø)

server/utils/kvstore/hashed_key.go
20.68% <20.68%> (ø)

... and 22 more

Continue to review full report at Codecov.

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

@mickmister @jfrerich here's the bulk of the server-side work; I'd like to get some early feedback, even if superficial before I get to the webapp part.

@levb, I am off of set this week and will get to this PR soon!

@aaronrothschild this is basically ready for review - it's missing the (critical?) UI component to select the instance in connect/disconnect/create/attach/subscribe but otherwise should be working.
@mickmister I'd appreciate a through, in-depth review of subs if you remember the code there. I haven't tested it much yet; it should be filtering by instanceID as appropriate. I'd also like to deprecate the "legacy" URLs - have the webhooks always go to /instance/XXX. Need to think through the backwards compatibility - probably ok since migration sets the old instance as "default".

connect to frontend logic?

Everything should be in place. I hooked up the existing code (GetInfo, websocket updates, and command hooks). The instance selectors can get all of their data from .instances and .user.connected_instances. If @mickmister or @jfrerich can quickly mock them up would be great, I was planning on filing them as separate issues once this is merged.

Closing the PR for time being.


[Bug fix] Fix tag name bug in model.go/ProcessInfo

Codecov Report

Merging #32 (e399b0c) into master (870da7e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #32   +/-   ##
=======================================
  Coverage   81.39%   81.39%
=======================================
  Files          33       33
  Lines        3795     3795
=======================================
  Hits         3089     3089
  Misses        541      541
  Partials      165      165

Impacted Files
Coverage Δ

entry/model.go
82.75% <ø> (ø)

Continue to review full report at Codecov.

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


Monospaced digits for the status bar items

When a status bar item updates frequently with something like a counter with a fixed number of digits it grows and shrinks depending on what digits are shown. This makes it look a bit broken, and it get worse if there are items to the sides of the counter.
I'd like to suggest that status bar items are rendered with fixed width/monospaced digits. I tried with making the whole VS Code UI render like this, with this CSS:
* { font-feature-settings: "tnum"; }

And I can't notice that it is bad anywhere. Here's what a timer-counter I wrote looks like with and without this CSS applied:

with
without

See also:

#73700

I'd like to PR this, btw. 😄

This is super cool also for the selection indicator, notice the before and after:
Before:

After:

Check with the selection status entry and change selection, the counters should not push the width.


Self-signed certificates don't work in HASS.io

Home Assistant release (hass --version):
0.57.0
Python release (python3 --version):
core-ssh:/config# python3 --version
-ash: python3: not found

Component/platform:
platform
Description of problem:
I followed the instructions to secure the web interface with a self-signed certificate on a fresh install.  After restarting Home Assistant the web page fails to load on either port 8123 or 443.
Expected:
Expect the web page to load, secured via SSL.
Problem-relevant configuration.yaml entries and steps to reproduce:
http:
  # Secrets are defined in the file secrets.yaml
  # api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123

  ssl_certificate: /ssl/certificate.pem
  ssl_key: /ssl/privkey.pem

openssl req -sha256 -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out certificate.pem
Update configuration.yaml as above.
hassio homeassistant restart

Is this still an issue?
Is there a reason for you not to use letsencrypt instead of self-signed?

Hi,
I cannot use Let's Encrypt as my Hass instance is not accessible outside my local network.
I guess the instruccions are not valid for hassio installations because when you connect via ssh you're connecting to the docker container and openssl is not installed here. This is why @NodeGuy get the -ash: python3: not found error.

Hi again,
I've developed a simple hassio addon to create self-signed certificates. You'll find it at my hass.io addons repository.
If you find it useful I can do a pull request to hassio-addons repository.
Regards,

@NodeGuy and @MacGulliver
If you want to go the manual route, I just configured my fresh install of hass.io with following entries in the configuration.yaml:
http:
  ssl_certificate: certificate.pem
  ssl_key: privkey.pem

and I copied both files into the /config folder via the ssh add-on, as this location is accessible from all docker containers. Both files need to be created on a computer with openssl installed.
This works and I can access my instance at https://hassio.local:8123.


docs: Start fixing links and formatting.

There's a lot left to do, but I have to travel, so figured something was better than nothing.


Make ford check including checking depth == 0

As the wiki says a ford can have depth=0 so we should include this in our check for all vehicles. Additionally we could use InstructionAnnotation to warn the user about this possible problem. What about intermittent=yes or seasonal=yes?
Which will fix e.g. this possible bus route:

http://graphhopper.com/maps/?point=Kulgera%2C Australia&point=Alice Springs%2C Australia

Probably we tag this route segment as potential dangerous (via instruction annotation). Also I got a report in france that this should be passable.

I'd vote for make fords routable with graphhopper. If the weren't passable the one or other way they wouldn't have been mapped as ford. You may warn users for fords (not the way between them), but there are less developed countries where routing with graphhopper will get you nowhere because of fords:
https://graphhopper.com/maps/?point=benje-novosele&point=40.299871%2C20.467808

Suggestion: Maybe in the Turn Instructions, list specifically that it is a Ford and may not be passable ..

Maybe we should try to give fords just a penalty instead of avoiding them altogether.

@malenki :+1:

I'd vote for make fords routable with graphhopper. If the weren't passable the one or other way they wouldn't have been mapped as ford. You may warn users for fords

@scaidermern :+1:

Maybe we should try to give fords just a penalty instead of avoiding them altogether.

See an example in France:  I use intermediates to force the algorithm to use this itinerary.
We could have the same problem with mountain pass in winter :wink:
:bulb: Add an option to avoid mountain pass, ford, toll…

You may want to look at some of the code I have done in engaric / graphhopper specifically the avoidance decorator hierarchy. Unfortunately I haven't managed to clear the contributor license with program management yet so cannot yet contribute it to upstream.
Sent from my BlackBerry 10 smartphone on the EE network.
From: pyrog
Sent: Friday, 12 June 2015 20:53
To: graphhopper/graphhopper
Reply To: graphhopper/graphhopper
Subject: Re: [graphhopper] Make ford check including checking depth == 0 (#236)
@malenki :+1:

I'd vote for make fords routable with graphhopper. If the weren't passable the one or other way they wouldn't have been mapped as ford. You may warn users for fords

@scaidermern :+1:

Maybe we should try to give fords just a penalty instead of avoiding them altogether.

See an example in France:  I use intermediates to force the algorithm to use this itinerary.
We could have the same problem with mountain pass in winter :wink:
:bulb: Add an option to avoid mountain pass, ford, toll…

Reply to this email directly or view it on GitHub:
https://github.com/graphhopper/graphhopper/issues/236#issuecomment-111598751

engaric schrieb
am Fri, 12 Jun 2015 13:22:17 -0700:

We could have the same problem with mountain
pass in
winter :wink: :bulb: Add an option to avoid mountain pass, ford, toll…

I wouldn't simply avoid mountain passes but only roads not cleared or
even closed in winter. gritting= and winter_service= do exist, though I
don't if roads closed in winter get mapped differently.
Now you just need to define "winter".

@malenki

I wouldn't simply avoid mountain passes but only roads not cleared or even closed in winter.

You're right :smile: I see your proposed feature winter_service.

Now you just need to define "winter".

We could compute it with the date and our position on the earth, but we could simply use conditional restrictions.
Another solution is to use TMC datas ?

depth=* is never used in France.
Also the value ford=stepping_stones is used (814 in TagInfo).
Cars, horses and maybe bicycles can't use theses fords :wink:
Only foot ?
As @malenki, @scaidermern and @MarkCupitt, I'd vote for make fords routable with graphhopper.

Ok, this is important but without route instructions warnings not good/safe IMO. Postponing for now

without route instructions warnings...

Currently, does GH can display route instructions warnings ?

...not good/safe IMO.

As an experienced backpacker and rider, I prepare carefully my treks using différents sources. (Digitals) maps and automatic routers are one of them.

Using only a digital router/map is dangerous, even if warnings are displayed. World is continually changing, (espacially weather) and any maps could up to date.

 Postponing for now

IMHO this issue should be fixed now, and a safety tips should be displayed like :

"Hiking [...] contains inherent risks which no amount of care, caution or expertise can eliminate. This site is no substitute for topo maps, route finding skill, compass, physical condition, sense of humor or good judgement"
Source: http://www.toddshikingguide.com/Warning/Warning.htm

Currently, does GH can display route instructions warnings ?

We can add annotations to instructions, which should be marked as warning then.

IMHO this issue should be fixed now, and a safety tips should be displayed like :

postponing only for the upcoming release

Hiking [...] contains inherent risks which no amount of care, caution or expertise can eliminate.

Sure, for example we have this in our terms. But as this is not really a big effort and of great help we should include it before enabling this for all.
Also if you really need this you can already enable routing through fords.

I also think routing through fords should be the default.
As said above, the routing program is not responsible for weather conditions.
Given that fords are used in many different places in the world, any assumptions on access implications will be incorrect in a different climate or culture.
IMO, any routing implications or restrictions should be tagged separately using access, width, weight, and similar tags.

I was pointed to https://wiki.openstreetmap.org/wiki/Key:flood_prone which says unlike flood prone areas, fords may be safe to cross if there is water across the roadway. So can/should we just assume fords are safe? And block/warn only flood_prone? Or is this dependent on the mapper/geographic region?

Are there any news on this issue? Is this still something we want to do?
A way I see to fix this would be to:

Allow routing through fords, [optionally] add a penalty?
Safe a flag per edge, to remember if the edge is a ford (ugly to spend one bit for < .01% roads (number is guessed)).
When routing over a ford, create an InstructionAnnotation that notifies about crossing a ford
Show the annotation in the web interface?

So probably it would make sense to make this change in the DataflagEncoder. Could be also added to other Encoders, but not sure if this would take about to much storage in the graph?

A way I see to fix this would be to:

Allow routing through fords, [optionally] add a penalty?
When routing over a ford, create an InstructionAnnotation that notifies about crossing a ford
Show the annotation in the web interface?

👍

Are there any news on this issue?
no
Is this still something we want to do?
yes, sure :)

So probably it would make sense to make this change in the DataflagEncoder. Could be also added to other Encoders, but not sure if this would take about to much storage in the graph?

Yes, maybe for now DataFlagEncoder and then the storage requirement is less than one bit :)

A note regarding a ford can now be given in the instructions, still for the DataFlagEncoder only.
To make this less of an issue what about the following:

use access=yes as new default for all encoders based on car on roads like primary&motorway&trunk&(secondary&tertiary) and also enable it for hike
additionally check regarding flood_prone=*.
for the foot encoder I'm still unsure if we should allow this

See also the discussion on the OSM forum

Seems that the fords are still regarded as unpassable.
eg. https://graphhopper.com/maps/?point=-39.233217%2C175.509124&point=-39.233284%2C175.510883&locale=en-NZ&vehicle=foot&weighting=fastest&elevation=true&use_miles=false&layer=Omniscale
Graphhopper doesn't want to cross the river, as a result the route is not making any sense.
Here in NZ it is very common to have to cross rivers on a hiking track, you can't really avoid them.

@bohwaz it does when you use the "hike" profile: https://graphhopper.com/maps/?point=-39.233217%2C175.509124&point=-39.233284%2C175.510883&locale=en-NZ&vehicle=hike&weighting=fastest&elevation=true&use_miles=false&layer=Omniscale

Ah great! Though I don't understand how you made all those new buttons appear ^^

@bohwaz there's a button like "..."  next to the bike

Oh my! Thanks! Didn't look like a button though.
Sorry then, thanks for your help :)

Fords are now routable? For instance: http://www.openstreetmap.org/directions?engine=graphhopper_car&route=-1.2329%2C37.4654%3B-1.2346%2C37.4666#map=17/-1.23424/37.46722

Fords are now routable? For instance: http://www.openstreetmap.org/directions?engine=graphhopper_car&route=-1.2329%2C37.4654%3B-1.2346%2C37.4666#map=17/-1.23424/37.46722

This is a way tagged as ford=yes. I guess this gets handled differently or not at all.

Good spot, yes :)
Also applies to nodes tagged as ford=yes:
http://www.openstreetmap.org/directions?engine=graphhopper_car&route=1.19272%2C35.74388%3B1.18673%2C35.74231#map=17/1.18975/35.74259
http://www.openstreetmap.org/node/4401108509
On 16 December 2017 at 14:48, Alexander Heinlein<EMAIL_ADDRESS>wrote:

Fords are now routable? For instance: http://www.openstreetmap.org/
directions?engine=graphhopper_car&route=-1.2329%2C37.4654%
3B-1.2346%2C37.4666#map=17/-1.23424/37.46722
This is a way https://www.openstreetmap.org/way/546604754 tagged as
ford=yes. I guess this gets handled differently or not at all.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/graphhopper/graphhopper/issues/236#issuecomment-352187949,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzxsj801_XOr19nI36UOgykF-Krvituks5tA9g5gaJpZM4CMuId
.

Yes, we now use the block_fords=false option that was already there and will see if this gets better feedback or worse as the current state gave us too many reports (similar to our still conservative behaviour for ferries and gates)

There is now a prominent warning for all vehicles due to #1811, so we've finally made block_fords=false the default for all FlagEncoders.
Additionally there is a bug fix to still block fords if explicitly tagged.


This is not a bug, but a suggestion

Hello dev!
Once again, congratulations on the incredible work!
I would like to make a suggestion... it would be great to include some more filters on the map, perhaps by item type?
You could also create a discord to interact with people, this project has a TOP future...
Hello dev!
Once again, congratulations on the incredible work!
I would like to make a suggestion... it would be great to include some more filters on the map, perhaps by item type?
You could also create a discord to interact with people, this project has a TOP future
I remain at your disposal for any feedback, topics or exchange of ideas! (Discord: g.siqueira)

Sorry for the late reply
Indeed, a map filter would be helpful
There already is a discord server about the server manager. You can find it in the readme (the chat button right at the top)

this has been added in v3.5.0


Markdown in marginnote

Hi, I'm not sure if this is a bug or a feature request, but I was surprised that marginnotes don't take markdown as input. The input is litterally copied into the HTML, so HTML is accepted.
Is this a stringent limitation of the theme?
Best regards,
Vic

Actually the marginote render as follow
{{ $marginnoteDomIdSuffix := .Ordinal }}
⊕

<input
  type="checkbox"
  id="marginnote-{{.Page.File.UniqueID}}-{{ $marginnoteDomIdSuffix }}"
  class="margin-toggle"
/>
{{ .Inner }}

Its not a theme limitation, it's just that you can't render markdown in shortcode natively. They are rendered "as is".
But that's actually fixable

@vicmortelmans Thanks for your contribution


It would be good to support .yaml file extension

This is a nice little tool, but I initially had trouble with it because all of my YAML files use .yaml instead of .yml as the file extension. When I tried to use yamlinc with one of those files, all I got was
Arguments error >> missing file name.
After trying a few other things, I eventually guessed that yamlinc might only recognize .yml file extensions, which turned out to be correct.
If you get a chance, please modify yamlinc to recognize .yaml file extensions as valid.

@StephenNay Good news! Support for multiple file extension is now on v0.0.63.
try to update with
$ npm install -g yamlinc

Isn't this already solved? npm has v0.1.1 already.

@StephenNay @Zaijo Yes! It works!


How to use tfhe-rs in guest?

We can currently compile the tfhe-rs crate, but we fail to fully use the crate as we are not able to directly pass the generated keys and input values from the host to the guest (more information can be found in this discussion thread)
It would be nice to create a demo example of how to integrate FHE into r0VM.

I am unable to compile the tfhe-rs crate on the guest side, could you share which version did you use?

The version used previously was 0.3.1

Were you eventually able to pass generated keys from host to guest?

Unfortunately, not yet.


TweetUtils cause freez of main thread.

hello,
In my applizacion I want to display TweetView in RecyclerView item.
I have added dependencies for app module gradle file:
compile 'com.twitter.sdk.android:twitter-core:3.2.0'     compile 'com.twitter.sdk.android:tweet-ui:3.2.0'
I'm initialising Twitter in App onCreate() method:
val config = TwitterConfig.Builder(this)                 .logger(DefaultLogger(Log.DEBUG))                 .twitterAuthConfig(TwitterAuthConfig(...))                 .debug(true)                 .build()         Twitter.initialize(config)
And here is how I load tweet:
`
TweetUtils.loadTweet(id, object : Callback<Tweet>() {
            override fun success(result: Result<Tweet>) {
                viewHolder.tweetViewRoot.addView(TweetView(viewHolder.itemView.context, result.data))
            }

        override fun failure(exception: TwitterException) {
            Log.d("TwitterRecycleItem", "---> failure()", exception)
        }
    })

`
It is called inside onBindViewHolder(...) method.
On the first load after application start, method invocation TweetUtils.loadTweet(...) cause freez of main thread for 4-5 seconds. When I enter to screen with TweetView second time it loads without any freez.
here is what I have noticed in logs during freez:

Twitter: Could not call getAdvertisingIdInfo on com.google.android.gms.ads.identifier.AdvertisingIdClient
Twitter: Could not call isLimitAdTrackingEnabled on com.google.android.gms.ads.identifier.AdvertisingIdClient$Info
Twitter: AdvertisingInfo not present

There is someting that I have missed?
Tested on Android 7.0

I've been seeing this issue as well with 3.2.0


Fix note naming according to scientific pitch notation and allow lower-case

In 2 days using this program it happened twice that I typed note names in lower case and stared at the screen for a long time, wondering what was wrong.

Please read the commit messages.


Point out our Docker support

Would be nice to be able to:
docker run crossbario/autobahn-cpp:gcc

and have a full SDK up and running in no time. The Docker image should contain:

GCC or Clang toolchain
boost
msgpack
websocketpp
autobahncpp

Note that this is about an SDK for AutobahnCpp, and hence the image is large. Executables built using that, and using static linking, can be fully self-contained.

Actually, that works already. Stuff is here https://github.com/crossbario/crossbar-docker/tree/master/autobahn-cpp
The clang variant has still issues. Docs in the README in this repo are missing. We should promote the Docker way as the easy way (and it is ..).

We now have Dockerfiles here:

https://hub.docker.com/r/crossbario/autobahn-cpp/
https://github.com/crossbario/crossbar-docker/blob/master/autobahn-cpp/Dockerfile.gcc
https://github.com/crossbario/crossbar-docker/blob/master/autobahn-cpp/Dockerfile.clang

We should prominently announce that in the README. In particular for beginners struggling with toolchain/library issues, this seems easier.

In your 20160416 comment, the links to Dockerfile.gcc and Dockerfile.clang are outdated.

The page linked to first, https://hub.docker.com/r/crossbario/autobahn-cpp/ also has links to outdated github repos (crossbar-starter, crossbar-docker).

That page also states that 'built executables do NOT need Docker and can be linked'. IMHO it would be more clear to change this into 'created clients do NOT need Docker and can be linked to' as it connects the sentence with the previous one.

@rogererens thx for collecting all the broken links!
In fact, I am in the process of finally cleaning things up:

the toolchain image building has moved here https://github.com/crossbario/autobahn-cpp/tree/master/docker (gcc works, clang is broken)
the app scaffolding has moved out from crossbar into cbsh https://github.com/crossbario/crossbar-shell#crossbario-shell
this is based on cookiecutter, and the abcpp one is here (and works): https://github.com/crossbario/cookiecutter-autobahn-cpp


Parse php code "$this->someMethod()"  without token

First, thank you for read this issues. I can write some simple English.
test code
A source code from laravel
<?php

namespace Illuminate\Auth;

trait Authenticatable
{

    /**
     * The column name of the "remember me" token.
     *
     * @var string
     */
    protected $rememberTokenName = 'remember_token';

    /**
     * Get the name of the unique identifier for the user.
     *
     * @return string
     */
    public function getAuthIdentifierName()
    {
        return $this->getKeyName();
    }
}

screenshots

expected
Should it be parsed as follows?
$this
->
getKeyName()
.
.
.

Highlight is done by outer package https://highlightjs.org/, and result is not related to this package anyhow.


silence warning if NIX_INDEX_DATABASE is set

Related to https://github.com/nix-community/nix-index-database/issues/92

I think checking if the file is writable would work better? WYD?

Also works. Maybe better semantics.


Work out how to use npm modules

The AsyncAPI parser code is embedded in the plugin which is horrible.
https://github.com/dalelane/node-red-contrib-plugin-asyncapi/blob/6b6182beebc3b182e4211834a7e1900d35aa77bb/asyncapi-plugin.html#L2-L4
I need to work out how to use npm modules in Node-RED plugins, so I can remove that.

One short-term alternative is to add a build stage to your plugin that bundles your dependencies into the html. That isn't entirely satisfactory.
I'm looking at the plugin design to see how plugins can register additional content that should be exposed to the editor. That's fine if the plugin has a static directory of content to load - you have a slightly different requirement to include a file that is not part of the plugin directly, but comes from a dependency of your plugin. That gets a little tricker as we cannot assume where that file will be on disk... npm could have stuck it higher up in the node-path.


1.17.1 - 37.0.27 - 20210730b

Made a white sofa chair, and after sitting in it, then trying to stand, it crashed my server.
Could no longer launch the server, getting the same error every time.
Had to remove the mod, launch the server, close it, and put the mod back to get it to launch.
Latest error log:
https://hastebin.com/duyaqilewu.yaml

fixed in 20210810a


Grammars

[x] Convert to mention_with_mod (now in Processors master)
-- update taxonomy
-- use action with modification rules to convert NPs
[x] Convert to universal dependencies

done


Broken symlinks to .mag files in install output?

I haven't had a chance to look at this closely yet, so this is somewhat of a guess, the continous builder has been failing for ~8 days due to the following;
+ find /host/out/pdk-all /host/out/pdk-all.build.log /host/out/pdk-all.install.log -name '*.mag' -exec sed -i '-es/timestamp [0-9]\+/timestamp 0/' '{}' +
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_01F600.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_45.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_6D.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_41.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_64.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_7B.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_74.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_48.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_51.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_2D.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_6B.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_2E.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_24.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_66.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_55.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_58.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_32.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_26.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_21.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_46.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_29.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_49.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_77.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_52.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_4D.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_36.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_30.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_6F.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_3C.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_6E.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_47.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_68.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_54.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/logo_open_source_hardware.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_2F.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_3B.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_79.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_63.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_22.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_7A.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_4E.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_42.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_38.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_2B.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_72.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_76.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_3D.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_2C.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_20.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_60.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_53.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_5C.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_50.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_75.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_4B.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_6A.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_31.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_70.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_43.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_71.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_3F.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_27.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_5F.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_73.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_67.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_78.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_37.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_44.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_23.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_59.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_5D.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_56.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_7C.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_61.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_5E.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_6C.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_A9.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_40.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_7E.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_28.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_4A.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_35.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_34.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_7D.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_3A.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_57.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_25.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_5B.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_65.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_39.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_5A.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_62.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_3E.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_33.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_4F.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_4C.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_2A.mag: No such file or directory
sed: can't read /host/out/pdk-all/usr/local/share/pdk/sky130B/libs.ref/sky130_ml_xx_hd/mag/font_69.mag: No such file or directory

I think the way find would ask sed to operate on a file that doesn't exist is if it was a directory or if the file was a broken symlink?

This seems to be caused by the change at https://github.com/RTimothyEdwards/open_pdks/commit/ae8d0f9f305148f9772b4ce7f7c4bc3325068594

From the output, I can figure out what happened.  The font library is basically hard-coded to sky130A, so I need to apply the same procedure I did to xschem to filter all files to turn the "sky130A" into a generic variable name that can be recast back into "sky130A" or "sky130B" as appropriate.  Should not take long to fix.

I found several other places where the scripts can't distinguish between sky130A and sky130B, so fixing them all while I'm at it.

This has now been fixed.  @mithro :  Please check the results after the next build.

Looks like the build work - https://foss-eda-tools.googlesource.com/skywater-pdk/output/+/43e103590065eb3dddcd5796fbd2d04cb510e146

@RTimothyEdwards -- Can you look over that diff? I think the changes all are okay but I'm not smart enough to be confident in that assessment...

I looked over the diff and it's okay with respect to this issue, which can be closed.  There were other issues that I'm still looking at, but they're unrelated.


90th percentile is missing from metrics

The documentation for the Dropwizard Metrics states that the Histogram should have the 90th percentile metric available, but it is currently missing and is generally a useful percentile to have to SLA purposes.
I am working on updating the code in the metrics-core project so that the 90th percentile is added into the Snapshot class along with the core reporters and unit tests within this section.
Is there anything else that should be looked into for this?
Otherwise i will work on the code and get the pull request submitted when your happy.
Thanks

I'd suggest that you not try to add in 90th percentile.  It's very likely that v4 will have configurable quantiles, and as a result most of the changes to add this would be overwritten. I'll keep this issue open to make sure we add in 90th percentile after the refactor is completed.

And also could you please add 50th percentile?

Median is 50th percentile.

thanks a lot for prompt response, sorry by mistake i had asked this question.

is there any way to get code for 3.1.2 version?

You can view the tags in github, so 3.1.2 is here - https://github.com/dropwizard/metrics/tree/v3.1.2 and can download the source as a zip.


[BUG] Receiving amount input on withdraw is configurable when it should be disabled.

Expected Behavior

The receiving amount input should be disabled and only show the amount the user will receive (before/after refund). It shouldn't be configurable as it is now.
Current Behavior

It is configurable and a bit odd as the state is updatable in 2 places. It doesn't adhere to the design.
Possible Solution

Implement according to the design in Figma.
Screenshot

This issue has been covered here


v1.2.0 update

[x] Add setup.py and incorporate it with environment.yml: Removes a lot of the sys methods that were used to set the path
[x] Sproc now returns a table
[x] Test case for sproc updated for new return type

Still an open question regarding importing UDFs into sproc

@sfc-gh-mrojas -- CI is breaking for some reason, filed an issue here: https://github.com/snowflakedb/snowpark-python/issues/992


Adding a local snippets file for to put common boilerplate handler code

Not 100% necessary but a standard snippets file could help onboard people and speed up development a bit.

Missed which branch this was going into, should have been into main as the localstack integration PR has already been merged.


Add "Send message" to profile page

There is already "Message" button on profile page when Conversation module is installed.


Key "import-x/order": Could not find plugin "import-x".

I'm seeing this when in compo with TS matching patterns for .ts but not for the .js side of things.

Key "import-x/order": Could not find plugin "import-x".

I'm doing something like
const getImportXFlatConfigs = isEsm => {
  const sharedImportXRules = {
    'import-x/order': [
      'warn',
      {
        groups: [
          'builtin',
          'external',
          'internal',
          ['parent', 'sibling', 'index'],
          'type'
        ],
        pathGroups: [
          {
            pattern: '@xyz/**',
            group: 'internal'
          }
        ],
        pathGroupsExcludedImportTypes: ['type'],
        'newlines-between': 'always',
        alphabetize: {
          order: 'asc'
        }
      }
    ]
  }
  return {
    recommended: {
      ...origImportXFlatConfigs.recommended,
      languageOptions: {
        ...origImportXFlatConfigs.recommended.languageOptions,
        ecmaVersion: LATEST,
        sourceType: isEsm ? 'module' : 'script'
      },
      rules: {
        ...origImportXFlatConfigs.recommended.rules,
        ...sharedImportXRules,
        'import-x/no-named-as-default-member': 'off',
      }
    },
    typescript: {
      ...origImportXFlatConfigs.typescript,
      settings: {
        ...origImportXFlatConfigs.typescript.settings,
        'import-x/resolver-next': [
          createOxcImportResolver({
            tsConfig: {
              configFile: rootTsConfigPath,
              references: 'auto'
            }
          })
        ]
      },
      rules: {
        ...origImportXFlatConfigs.typescript.settings.rules,
        ...sharedImportXRules
      }
    }
  }
}

and then later:
const importFlatConfigsForModule = getImportXFlatConfigs(true)

then
module.exports = [
  {
    files: ['src/**/*.ts', 'test/**/*.ts'],
    ...importFlatConfigsForModule.typescript
  }
]

Previously when @michaelfaith introduced flat presets, the plugins were only included in the base presets (recommended and more), other "addon" presets like typescript, react, reactNative, and electron doesn't contain plugins.

And the reasoning for that was that you can't "redefine" a plugin.  So if both the "core" and "addon" / "extension" configs defined the plugin then there'd be an error when users used both together. So this seemed like the least worst option.

Ah okay. I thought flat config meant not needing to specify the plugins prop. Does eslint offer good config merge helpers? Manually cherry-picking the props with spread is no problem, just curious.

That fixed it. Thanks @SukkaW!


Feature Request: Instead of BazelDependencies target possible to add run scripts to the actual target

Problem
Today when we add run scripts they get added to the BazelDependencies target instead of the actual Target. With this approach we lose on using some of Xcodebuild ENV variables such as TARGET_NAME & DERIVED_FILE_DIR in run scripts, so instead of adding these scripts to  the BazelDependencies, is it possible to add them to the actual app target itself?
Feature request
When we pass pre_build & post_build scripts to rules_xcodeproj, instead of adding them to  BazelDependencies, is it possible to add them to the top_level_targets of type Application? This would ensure we have all Xcode's ENV vars available.

What are your specific use cases you are trying to solve?

This is what I am trying to do :
We have a script to copy some files to the generated app bundle, To do this I need to access TARGET_BUILD_DIR but that's not available when for BazelDependencies target.
Update it in the issue description as well.

These files are from Security Framework to detect Fraud on the app.


Rails 7.1 Incompatibility

I am running a Rails 7.0 app with ActiveGraph 11.4.0 and see a deprecation warning when the app starts:

DEPRECATION WARNING: ActiveSupport::PerThreadRegistry is deprecated and will be removed in Rails 7.1.
Use Module#thread_mattr_accessor instead.

It references the line in application.rb which calls require 'active_graph/railtie'.
It looks like ActiveSupport::PerThreadRegistry is included here: https://github.com/neo4jrb/activegraph/blob/master/lib/active_graph/node/scope.rb#L147. Since that block of code references following ActiveRecord, perhaps whatever the latest ActiveRecord is doing could be used there as well?
Thank you.

@boone could you test activegraph 11.5.0.alpha.1? It has both zeitwerk migration and activesupport 7.1 compatibility.

@klobuczek So far all I changed was to set the ActiveGraph gem to the new alpha and updated Gemfile.lock. Trying to start the Rails app I encountered:
/usr/local/bundle/gems/activegraph-11.5.0.alpha.1/lib/active_graph/railtie.rb:45:in `block in <class:Railtie>': uninitialized constant ActiveGraph::Config (NameError)

      ActiveGraph::Config.configuration.merge!(neo4j_config.to_h)

I also noted the neo4j namespaced Rake tasks are unavailable.
Does something else need to change in our app for compatibility with the alpha changes?
Thanks!

I just tried it as well.
ActiveGraph version: 11.5.0.alpha.1
Rails version: 7.0.8
And I got this error:
(base) ➜  sh ✗ bundle exec rails c
/Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/io-event-1.3.2/lib/io/event/support.rb:24: warning: IO::Buffer is experimental and both the Ruby and C interface may change in the future!
/Users/jhulme/projects/orders/config/initializers/sidekiq.rb:67: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0
/Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activegraph-11.5.0.alpha.1/lib/active_graph/railtie.rb:45:in `block in <class:Railtie>': uninitialized constant ActiveGraph::Config (NameError)

      ActiveGraph::Config.configuration.merge!(neo4j_config.to_h)
                 ^^^^^^^^
Did you mean?  RbConfig
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:32:in `instance_exec'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:32:in `run'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:61:in `block in run_initializers'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:228:in `block in tsort_each'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:431:in `each_strongly_connected_component_from'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:349:in `block in each_strongly_connected_component'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:347:in `each'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:347:in `call'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:347:in `each_strongly_connected_component'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:226:in `tsort_each'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/3.2.0/tsort.rb:205:in `tsort_each'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:60:in `run_initializers'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/application.rb:372:in `initialize!'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/railtie.rb:226:in `public_send'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/railtie.rb:226:in `method_missing'
	from /Users/jhulme/projects/orders/config/environment.rb:5:in `<main>'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/zeitwerk-2.6.11/lib/zeitwerk/kernel.rb:38:in `require'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/application.rb:348:in `require_environment!'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/command/actions.rb:28:in `require_environment!'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/command/actions.rb:15:in `require_application_and_environment!'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/commands/console/console_command.rb:105:in `perform'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/thor-1.2.2/lib/thor/command.rb:27:in `run'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/thor-1.2.2/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/thor-1.2.2/lib/thor.rb:392:in `dispatch'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/command/base.rb:87:in `perform'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/command.rb:48:in `invoke'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-7.0.8/lib/rails/commands.rb:18:in `<main>'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/jhulme/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from bin/rails:4:in `<main>'

I'm not a zeitwork expert, but I think you still need require 'active_graph' in railtie.rb.
Looking at other gems like action_mailer and active_record they still require themselves in railtie.rb.
When I added require 'active_graph' to railtie.rb the error went away and everything seemed to load

@boone @jhulme-ut please have a look at 11.5.0.beta.1. The above issues should be fixed. Let us know if you find any further issues.

Thanks @klobuczek that seems to be working now - tested against neo4j 4.4.26
The only issue I've run into is that a couple of queries are throwing an error:
/usr/src/app/vendor/bundle/ruby/3.2.0/gems/activegraph-11.5.0.beta.2/lib/active_graph/model_schema.rb:103:in `validate_model_schema!':

Some schema elements were defined by the model (which is no longer supported), but they do not exist in the database.  Run the following to create them if you haven't already: (ActiveGraph::DeprecatedSchemaDefinitionError)

And we weren't getting this error in 11.4.0.
But I think this is just a problem with our database, that is finally being surfaced, not a bug in the gem. I'll see if I can make it go away by generating a migration

I'm using activegraph-11.5.0.beta.2 with rails-7.1.2 and neo4j-ruby-driver-4.4.5 but still encounter a problem with missing rake tasks. The attached file shows what happens when rake test is run. In my test helper there's the following:
  ActiveGraph::Base.query('MATCH (n) DETACH DELETE n')
  Rails.application.load_tasks
  Rake::Task.define_task(:environment)
  Rake::Task["neo4j:migrate"].invoke
  Rake::Task["graphs:populate_neo4j"].invoke

Commenting out the last two lines "fixes" the issue, and adding require 'active_graph' to the test helper doesn't. Can anyone suggest how I might work around this?
rails_upgrade_fail.txt

Just read through all your comments here as my attempt to use latest stable releases failed with this error:
cannot load such file -- active_support/per_thread_registry
the following combination doesn't mess with loading:
gem 'activegraph', '11.5.0.beta.2'
gem 'neo4j-ruby-driver', '~> 4.4.5'

@georgkreimer the latest stable release is not compatible with the latest rails. We have been hesitant in putting upper limits on the activegraph gem dependencies as that puts more repressibility on our end to frequently retest and re-release. We are stretched thin here. At the moment it is your responsibility to put the upper limits in your Gemfile if you found out an incompatibility. It will be mostly on rails gems.
BTW: The second line of your snippet should not be necessary.

@klobuczek I appreciate all the work you do!
Actually I was trying to use ActiveGraph together with memgraph, which didn't work for me at the end. I'm now on Neo4j 4.4.19. ActiveGraph works well with that.

gem 'activegraph', git: 'https://github.com/neo4jrb/activegraph', tag: 'v11.5.0.beta.3'
gem 'neo4j-ruby-driver', '~> 4.4', '>= 4.4.5'

still gives:
/usr/local/bundle/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/railtie.rb:8:in '<module:ActionDispatch>': uninitialized constant Rails::Railtie (NameError)

Updating to v.12 requires v5 of the driver:
gem 'activegraph', git: 'https://github.com/neo4jrb/activegraph', tag: 'v12.0.0.beta.4'
gem 'neo4j-ruby-driver', '~> 4.4', '>= 4.4.5'

resulting in:
    activegraph was resolved to 12.0.0.beta.4, which depends on
      neo4j-ruby-driver (>= 5)

but it looks like all of the neo4j-ruby-driver versions listed at rubygems after 4.4.5 require java, not the ruby-native driver. 🤷♂


Update AdvancedJetEngine.netkan

AJE has new maintainers and a new forum thread. Repository remains camlost2/AJE for now, however.
I also changed the license from LGPL-2.1 to LGPL-2.0, as far as I can tell from the README history it's always been LGPL-2.0. Will have to go back and update old meta.
The haphazard order of the properties was really annoying me so I also just reformatted it.

Looks good to me, merging with my thanks.


[ICON REQUEST] Clock

Describe the icon you'd like to be added
While the alarm icon is fantastic, a clock icon would be important to convey the time of something in a clear manner.
Sample icon
https://icon-sets.iconify.design/heroicons-solid/clock/

@LewisLarsen  Clock icon has been added. Thanks for the suggestion!


ImportError: No module named pyocd.tools.gdb_server

I used pip install -U pyocd to upgrade my pyocd version today.
I try to run a GDB server with pyocd-gdbserver and I get the following error output:
~ $ pyocd-gdbserver
Traceback (most recent call last):
  File "/usr/local/bin/pyocd-gdbserver", line 7, in <module>
    from pyocd.tools.gdb_server import main
ImportError: No module named pyocd.tools.gdb_server

I am using pyocd version 0.13.2 and arm-none-eabi-gdb version GNU gdb (GNU Tools for Arm Embedded Processors 7-2018-q2-update) <IP_ADDRESS>80315-git
In order to run a pyocd-gdbserver I need to downgrade pyocd to version 0.12.x

Hi @yennster, what OS are you using, and what pip and setuptools versions? You might need to uninstall pyOCD and reinstall.
The package name was changed from "pyOCD" to "pyocd" in order to be compliant with Python naming standards. Unfortunately, on case-insensitive filesystems, upgrading may not correctly rename the folder. What's weird is that I tried this on macOS, Windows, and Linux (Ubuntu) and it seemed ok (after some initial trouble in 0.13.0). Maybe it's and older pip or setuptools? I'll try reproducing it once I know your OS and versions.

got the same issue, running on windows 10. With pyocd 0.13, mbetgt fiails. A 'mbedgt --version' throws an error that pyOCD.board is missing.
Downgrading to 0.12 fixes the problem, upgrading to 0.13.2 raises the problem again.
D:\Projects\Sn\LocalGit\test\mbed-SDIO-V2>mbedgt --version
mbedgt: Not all required Python modules were imported!
mbedgt: No module named pyOCD.board

@flit Here's my version info:

Mac OS 10.14.1
pip 18.1
python 2.7.15
setuptools 39.2.0

@yennster I just tried reproducing your upgrade problem with no luck. I created a virtualenv with exactly the same versions as you have, installed pyOCD 0.12.0, then ran pip install -U pyocd to upgrade to the latest. pyocd-gdbserver still runs fine. So I'm not sure what the problem you are seeing could be caused by! Can you try using a virtualenv?
@JojoS62 In the meantime, I recommend using two virtualenvs. One for debugging with pyOCD, and one for running greentea. I've moved the issue you are having to #467 since it's different from @yennster's upgrade problem (but with similar errors).

Issue is resolved now


No suggestions given after the as keyword.

The language service doesn't give any suggestions here:
const wrapper = document.querySelector('.wrapper') as H

At H I expected to see HTMLElement. The suggestion is shown if I type ; and then H.

Duplicate of #4731. This should be fixed in the next release.


sharing access token between main-skill bot using generic oauth

please provide NodeJS/TypeScript sample for token exchange(SSO) between root bot and skill bot.
Also is this method supports other authentication method like Generic Oauth 2?
And if it's not possible, is it ok/good practice to create a certain REST endpoint on mainbot to request for user's specific access token between skill/main bot then we skip the oauthcard dialog?

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

ID: ab060f59-0fc6-d90d-6b71-a0756f1a8aa0
Version Independent ID: f7574aeb-0002-5e07-47ed-3d135a42f4ce
Content: Add Single sign on to a bot - Bot Service
Content Source: articles/v4sdk/bot-builder-authentication-sso.md
Service: bot-service
GitHub Login: @Kaiqb
Microsoft Alias: kamrani

SSO is supported only for AAD V2 and not for other providers (including generic oauth). This is because not all providers support SSO or even have a common protocol for token exchange.
Sharing the access token between skill/main bot is ok, as long as the same bot developer owns the main bot and skill (that is, they share the same trust boundary). Otherwise, it maybe be a security issue. I'll defer to @Jeffders for more on this scenario

@swagatmishra2007 @Jeffders thank you. I currently have a scenario where the main bot provide oauthcard to user to authenticate to ServiceNow, then there is a separate skill bot that also connects to ServiceNow, but it would not be a great experience if user had to reauthenticate again using oauthcard when they are accessing the skill bot.
Is it possible to send through a set of auth data using postToSkill method provided too? If we are using REST endpoint, what would be the most secured/best way for skillbot to request on behalf of current user context (any same context shared between main/skill bot?).
I'm using NodeJS for both main/skill bot with MS Teams and webchat as main bot channel for user to interact.
Thanks

The JavaScript sample will be available in the next samples release. Let me know if we answered your questions. Thanks

@mmiele thanks! does this sample also includes non-AAD V2 token sharing?

@jonathanhotono I do not have that information; it will depend on the team's schedule.
Thank you for your interest and patience.


Move more functions into generic

This PR moves the following Tensor functions into the generic directory:

mean/meanall are extended to all tensor types
clamp to all tensor types
cross to all tensor types
cmin/cmax to all tensor types
addcmul/addcdiv to all tensor types
std/stdall to float/half/double tensors
var/varall to float/half/double tensors
norm/normall to float/half/double tensors
renorm to float/half/double tensors
lerp to float/half/double tensors
Required refactoring a lot of float specific code into .cuh files.

Test Plan:
updated unit tests to compare using new tensor types

@killeent: can we coordinate that with https://github.com/torch/cutorch/issues/515 ?

Also, THCNumeric.h is getting way too much of code duplication. Let me submit a PR for refactored version that would be a small fraction of current size and allow for less changes going forward.

i will be merging this, as it's a big functional PR, and it brings a lot of features in. Delaying this will really result in merge conflicts and really hard refactoring work.
working with #515 should follow.

@soumith: sure, merging this fast what I was hoping for! There is nothing contradictory between this and pseudo-float work, except that we touch the same files and moving stuff around.


Add Database Monitoring team

What does this PR do?
Add Database Monitoring team to trello automation script
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Duplicate of #9671


Sidebar nav, default open

Hello,
is there a way, to make sidebar navigation, show for example 'Home' group opened, then you enter the admin area?
Also for example have: Home > Testimonials
then I am in Testimonials - it keeps sidebar opened, but when I press EDIT on some of the items, sidebar closes, and I see only main groups, and I need to click arrow, to show group items again
Thank you

Do you mean when you click outside the menu bar, the menu that is open will close?

Is this solve? Please reopen it not.


Fix the number of output index files

When nb_indices_on_src_folder = 101 and n (nb_nbindices_to_keep) =10,
it generated 11 output files instead of 10.
Now it can generate 10 outputs.

The problem is that nb_nbindices_to_keep is computed so that one batch fit in ram.

Yes, I am aware of this concern, but normally the memory usage has been checked before in here, no ?

Yes but last time I made this kind of change, this kind of ceiling was producing less indices that the number asked in one of the 2 stages and then that was using more memory than available.
If you think that's important to make that change, let's unit test it with a bunch of values of total number of indices and of NB embeddings to keep to make sure it's never above nor below the number that is asked.

I added a unit test for it.
I even removed the line n = math.ceil(nb_indices_on_src_folder / batch_size).

ok, lgtm

I did an error in the unit test, assert all(batch[0] <= input_size - 1 for batch in batches) should be assert all(batch[1] <= input_size - 1 for batch in batches).
After this change, the test failed, that means that there could be an empty batch.
I will fix it soon.


Feature: Automatically manage number of longhorn replicas upon node deletion.

Motivation

Currently, when a node contains a longhorn volume and we delete that node, a new replica of the volume is not created. The longhorn devs advise to temporarily increase the replica count, so a new one is scheduled and then decrease it back to the desired number. By doing this, we assure the volume will be accessible as long as there are any nodes assigned to that storage class. There will be a need for some additional logic, like checking if a new replica can be even created, or maybe deleting the old replica (from the deleted node).
Description

Claudie should try to manage longhorn volume replicas when deleting a node from the cluster.
Exit criteria

[ ] The replicas are now created whenever possible on a node deletion.
[ ] The docs will document how node deletion work in regard to the storage.

Comment about how to change number of replicas via kubectl


Fix pre-commit hook

The git pre-commit hook had a typo "," inside.
Here I:

fix the typo
calculate the git hooks path (can be different for bare repositories and git worktrees)
move set -x inside if statement (why not?)

SORRY, the "," was alright and I put it back. The rest of the changes are fine, I've checked that, can merge.


zile: 2.4.14 -> <IP_ADDRESS>

Motivation for this change
Upgrade package, possibly solve this request from the maintainer.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 106139 run on x86_64-linux 1

1 package built:

zile

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/fixing-a-hydra-build-of-a-gnu-project/10389/3

Result of nixpkgs-review pr 106139 run on x86_64-darwin 1

1 package built:

zile

@SuperSandro2000 requested changes made.