Export to .pmdat fails

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
The following STEP file ply_boundaries.step.txt [1] cannot be loaded and then exported to the PMDAT format.
The following exception occurs:
CRITICAL -  -  logger - handle_exception - Uncaught exception
Traceback (most recent call last):
  File "<script_location>\pmdat_export_error.py", line 5, in <module>
    design.export_to_pmdb(".")
  File "<venv_location>\lib\site-packages\ansys\geometry\core\designer\design.py", line 474, in export_to_pmdb
    self.download(file_location, DesignFileFormat.PMDB)
  File "<venv_location>\lib\site-packages\ansys\geometry\core\errors.py", line 98, in wrapper
    raise GeometryExitedError(
ansys.geometry.core.errors.GeometryExitedError: Geometry service connection terminated: Could not find file '<TEMPDIR>\2a350bea-f124-4461-97c6-2aeb0781eb75.pmdb'.

[1] renamed to .txt to make Github happy
📝 Steps to reproduce

Download the STEP file linked above
Run the following code, changing the path to the file as needed:from ansys.geometry.core import launch_modeler_with_geometry_service

modeler = launch_modeler_with_geometry_service()
design = modeler.open_file("ply_boundaries.step")
design.export_to_pmdb(".")

💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2025R1
🐍 Which Python version are you using?
3.10
📦 Installed packages
aiohttp==3.9.5
aiosignal==1.3.1
ansys-api-dbu==0.3.3
ansys-api-geometry==0.4.4
ansys-geometry-core==0.6.5
ansys-tools-path==0.6.0
ansys-tools-visualization-interface==0.2.6
appdirs==1.4.4
async-timeout==4.0.3
attrs==23.2.0
beartype==0.18.5
certifi==2024.7.4
charset-normalizer==3.3.2
click==8.1.7
colorama==0.4.6
contourpy==1.2.1
cycler==0.12.1
flexcache==0.3
flexparser==0.3.1
fonttools==4.53.0
frozenlist==1.4.1
grpcio==1.64.1
grpcio-health-checking==1.64.1
idna==3.7
kiwisolver==1.4.5
matplotlib==3.9.1
more-itertools==10.3.0
msgpack==1.0.8
multidict==6.0.5
numpy==2.0.0
packaging==24.1
pillow==10.4.0
Pint==0.24.1
platformdirs==4.2.2
pooch==1.8.2
protobuf==5.27.2
pyparsing==3.1.2
python-dateutil==2.9.0.post0
pyvista==0.43.10
requests==2.32.3
scipy==1.14.0
scooby==0.10.0
semver==3.0.2
six==1.16.0
trame==3.6.3
trame-client==3.2.1
trame-server==3.0.3
trame-vtk==2.8.9
trame-vuetify==2.6.1
typing_extensions==4.12.2
urllib3==2.2.2
vtk==9.3.1
websockets==12.0
wslink==2.1.1
yarl==1.9.4

Hmm seems like you are using the local version of the Geometry Service (meaning, it is on your filesystem). Could you try running the script with the following modification?
design = modeler.open_file("ply_boundaries.step", upload_file=False)
design.export_to_pmdb()

Nonetheless it seems like the export/download API is the one failing... Let's give it a try to
https://geometry.docs.pyansys.com/version/0.6/api/ansys/geometry/core/designer/design/Design.html#Design.save
try calling
design.save("ply_boundaries.pmdb")

Fingers crossed...

upload_to_server=False

Produces the same error

design.save("ply_boundaries.pmdb")

Produces the following error:
ansys.geometry.core.errors.GeometryExitedError: Geometry service connection terminated: Path cannot be the empty string or all whitespace.

Can you reproduce the issue with the STEP above? Maybe I just got a bad daily build.
Otherwise, I suspect it's specific to this file. With another STEP file the original code works, but the design.save variant produces the same exception.

Hi @greschd - I came back to this issue after some time (sorry for the delay). I am able to reproduce the same problem you report. However, looking into the server logs I found an interesting error...
2024-08-30 13:06:17 1:06:17 PM: start save C:\Users\ContainerAdministrator\AppData\Local\Temp\43d7895b-f783-46d7-85d2-f7becf54befa.scdocx
2024-08-30 13:06:17 1:06:17 PM: ended save C:\Users\ContainerAdministrator\AppData\Local\Temp\43d7895b-f783-46d7-85d2-f7becf54befa.scdocx
2024-08-30 13:06:18 Failed to import assembly from SpaceClaim.    at AnsysSCPlugin.Transfer.AssemblyTransferer.Transfer(Part rootPart, TransferComponentCollection componentCollection) in D:\AnsysDev\NoBackup\SpaceClaim\Partners\ANSYS\25.1\AnsysSCPlugin.25.1\Transfer\AssemblyTransferer.cs:line 96
2024-08-30 13:06:18    at AnsysSCPlugin.TransferManager.<TransferAssemblyComponents>b__41_0() in D:\AnsysDev\NoBackup\SpaceClaim\Partners\ANSYS\25.1\AnsysSCPlugin.25.1\TransferManager.cs:line 418
2024-08-30 13:06:18    at SpaceClaim.Api.V251.WriteBlockStatic.ExecuteClientCode(Task task)
2024-08-30 13:06:18    at SpaceClaim.Api.V251.WriteBlockStatic.ExecuteTask(String commandText, TaskShim shim, Boolean addToLastCommand)
2024-08-30 13:06:18    at SpaceClaim.Api.V251.WriteBlock.ExecuteTask(String text, Task task)
2024-08-30 13:06:18    at AnsysSCPlugin.TransferManager.TransferAssemblyComponents() in D:\AnsysDev\NoBackup\SpaceClaim\Partners\ANSYS\25.1\AnsysSCPlugin.25.1\TransferManager.cs:line 405

My guess is that something is going on when exporting to PMDB only - because prior to these errors you can see that the export to scdocx worked just fine. I'll report it to the PMDB plugin team so that they can investigate.

FYI - I also tried it with SpaceClaim and it also failed so it might be something broader (not specific to the Geometry Service)...


Consistent database

In order for the app to always display the provided cheeps, I can as a programmer reset the database.
Criteria: have the workflow that deploys to azure, reset the cheepdatabase to the version provided in the course

Or maybe use some kind of db injection

This isn't the desired feature


Fix getFormParam content type check

Purpose

$Subject
Fixes #17494

Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #17512 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #17512   +/-   ##
=======================================
  Coverage   11.65%   11.65%
=======================================
  Files          50       50
  Lines        1545     1545
  Branches      240      240
=======================================
  Hits          180      180
  Misses       1351     1351
  Partials       14       14

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 6cc79a9...13c2e16. Read the comment docs.


Add co-maintainer

I don't really use this library that much anymore. I used to use it at $WORK and as part of MinGHC, but I changed $JOB and MinGHC got discontinued. A co-maintainer who actually used the library would be very beneficial.
CC @domenkozar and @jmitchell as two recent pull request authors who seem to have opinions about how it should be done.

I'm willing to be one, given that we're now using the library.

I'm happy to help too. :)

Thanks for the offers. I've given you both permissions to write to this repo. I'm happy to let the library sit as it is, but if you think it needs additions/extensions/big changes just raise tickets or patches and we can figure it out together. I'll announce it on my blog when I get around to it.

@ndmitchell, do you tend to merge all new work into master and bump the version and tag only once you're ready to make a release?

@jmitchell Yep, pretty much. I have a list of my general development style/guidelines/preferences at https://github.com/ndmitchell/neil/blob/master/README.md - I just added a note about merging into master.


create a standard pachctl docker image

What is the goal / desired outcome?
To enable CI/CD of my pipelines, I would like a standard pachctl docker image so that I don't have to build and maintain one myself.
If there is a way to accomplish this today via workaround, what does that require?
Building an image myself
(Optional) What is your proposal for a feature to solve this?
A standard docker image that's updated every version.

dupe of #3446?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Closing as dupe of #3446


2.3.0 causes build warnings with no explanation

Describe the bug
Getting warnings like this: swagger_code_generation:swagger_dart_code_generation on swaggers/mwork_api.swagger:[Frm] on all generated types. The warning does not tell what the problem might be...
To Reproduce
Build with this swagger file on 2.3.0
swagger.json.txt
Expected behavior
Please provide what the problem is in the warning.
Library version used:
2.3.0
Additional context
The problem is not severe, the code produced seems to work as expected.

Is it possible to share swagger file?

The swagger file is included above (linked as 'swagger.json.txt') it is renamed to .txt since github doesn't accept files ending with .swagger.

@RoarGronmo  Fixed in 2.3.1, I forgot to remove prints in generator :D


fix: resolve max_subscriptions and share sequence errors

Overview
This is a PR to test out changing back to the P-OPS RPC once they have changed the config to avoid this https://github.com/celestiaorg/celestia-node/issues/2238 and to test out the fix for https://github.com/celestiaorg/celestia-app/issues/1816 once the validator is updated to https://github.com/celestiaorg/celestia-app/releases/tag/v0.13.3
Resolves #19

Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

darn, no luck. I'm still seeing the max_subscriptions error as I don’t think P-OPS config has been updated yet. i imagine the share sequence has 1 shares but needed 0 shares has something to do with why the last safe block is 98

Here are some example snippets of errors:
Instance of share sequence has 1 shares but needed 0 shares:
op-node_1      | t=2023-05-25T16:35:35+0000 lvl=warn msg="unable to retrieve data from da"        origin=0x2aa86dd3b0a3b4e5fa8a4f0e8344d57675720d6c3daf967c510924f3d8a39282:190 err="share sequence has 1 shares but needed 0 shares"

Example of one of the light node panics:
celestia-light-node | 2023/05/25 16:03:35 http: panic serving <IP_ADDRESS>:54942: runtime error: invalid memory address or nil pointer dereference
celestia-light-node | panic({0x2544a40, 0x4c1e190})
celestia-light-node |   /usr/local/go/src/runtime/panic.go:890 +0x263

Unable to retrieve data from DA:
op-node_1      | t=2023-05-25T17:07:20+0000 lvl=warn msg="unable to retrieve data from da"        origin=0xc26bd0184386e88a4b627a75acd0c973c109941286e6714513ef9c4c8b8db9cf:315 err="Get \"http://da:26659/names
paced_data/e8e5f679bf7116cb/height/572941\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"

Max subscriptions error:
op-batcher_1   | t=2023-05-25T16:58:08+0000 lvl=warn msg="unable to publish tx"               err="rpc error: code = Unknown desc = max_subscriptions_per_client 5 reached" data_size=712                [1/135]
op-batcher_1   | t=2023-05-25T16:58:08+0000 lvl=warn msg="Failed to send transaction"         err="rpc error: code = Unknown desc = max_subscriptions_per_client 5 reached"
op-batcher_1   | t=2023-05-25T16:58:08+0000 lvl=warn msg="unable to publish tx to celestia"   service=batcher err="rpc error: code = Unknown desc = max_subscriptions_per_client 5 reached"
op-batcher_1   | t=2023-05-25T16:58:08+0000 lvl=warn msg="unable to publish tx"               err="rpc error: code = Unknown desc = max_subscriptions_per_client 5 reached" data_size=712
op-batcher_1   | t=2023-05-25T16:58:08+0000 lvl=warn msg="Failed to send transaction"         err="rpc error: code = Unknown desc = max_subscriptions_per_client 5 reached"

head request to trusted peer failed:
celestia-light-node | 2023-05-25T17:07:20.009Z  ERROR   header/p2p      p2p/exchange.go:144     head request to trusted peer failed     {"trustedPeer": "12D3KooWBtxdBzToQwnS4ySGpph9PtGmmjEyATkgX3PfhAo4x[0/11]
"err": "header/p2p: failed to open a new stream: context canceled"}

Full logs
Here are the full logs

This PR resolves max_subscriptions and share sequence errors, as it is intended to.
However, the safe block is stuck roughly 5.5k blocks behind the latest block, likely due to one of these errors:
One occurrence of head request to trusted peer failed (https://github.com/celestiaorg/celestia-node/issues/2241)
celestia-light-node | 2023-05-26T18:56:02.007Z  ERROR   header/p2p      p2p/exchange.go:144     head request to trusted peer failed     {"trustedPeer": "12D3KooWBtxdBzToQwnS4ySGpph9PtGmmjEyATkgX3PfhAo4xmf7", "err": "header/p2p: failed to open a new stream: context canceled"}

One occurrence of context deadline exceeded (Client.Timeout exceeded while awaiting headers https://github.com/celestiaorg/celestia-node/issues/2250
op-node_1      | t=2023-05-26T18:56:02+0000 lvl=warn msg="unable to retrieve data from da"        origin=0x4cacf6ed15337c9b85dfb9e23e693e6f793796e23910dcf44c973ae5017cac3f:221 err="Get \"http://da:26659/namespaced_data/e8e5f679bf7116cb/height/581437\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"

checking for safe and latest blocks
root@jcs-optimism:~/optimism# cast block safe --rpc-url http://localhost:9545 --field number
1208
root@jcs-optimism:~/optimism# cast block latest --rpc-url http://localhost:9545 --field number
6835

Full logs are here
https://drive.google.com/file/d/18N0060e6015HzYr1e6GyUi_U-ARuDiiE/view?usp=share_link (i ran out of space on my free tier of Git LFS)
Screenshot of the current errors and checks for old errors:

note: the docker image is https://github.com/orgs/celestiaorg/packages/container/celestia-node/96549596?tag=e5efcb0 this because the tag didn't exist for v0.10.1

This also may have resolved, #54 and #57 as I see no more instances of them

I debugged these logs https://drive.google.com/file/d/18N0060e6015HzYr1e6GyUi_U-ARuDiiE/view?usp=share_link
and found that
op-node_1      | t=2023-05-26T18:56:02+0000 lvl=warn msg="unable to retrieve data from da"        origin=0x4cacf6ed15337c9b85dfb9e23e693e6f793796e23910dcf44c973ae5017cac3f:221 err="Get \"http://da:26659/namespaced_data/e8e5f679bf7116cb/height/581437\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
and at the same time proposer stalls:
op-proposer_1  | t=2023-05-26T18:55:42+0000 lvl=eror msg="proposer unable to get sync status" err="Post "http://op-node:8545": context deadline exceeded"
op-proposer_1  | t=2023-05-26T18:55:52+0000 lvl=eror msg="proposer unable to get sync status" err="Post "http://op-node:8545": context deadline exceeded"
op-proposer_1  | t=2023-05-26T18:56:02+0000 lvl=info msg="proposer submission interval has not elapsed" currentBlockNumber=1208 nextBlockNumber=1320
I'm wondering if this was running without the extended proposer timeout fix #50
https://github.com/celestiaorg/optimism/pull/50/commits/61518e866fb58bc1312cc46c4645d7497ee994a3

it was running with fixes from #50 based on L128 of docker-compose-testnet.yml and L11 of devnetL1.json. Also, based on the commit history of this branch

OK, will need to look at timestamps, maybe it was running past even the 180s timeout? 🤔

Some more context, at the same time, node was throwing head request to trusted peer failed:
celestia-light-node | 2023-05-26T18:56:02.007Z	ERROR	header/p2p	p2p/exchange.go:144	head request to trusted peer failed	{"trustedPeer": "12D3KooWBtxdBzToQwnS4ySGpph9PtGmmjEyATkgX3PfhAo4xmf7", "err": "header/p2p: failed to open a new stream: context canceled"}


Update docfx.json

@jmazzotta @VesaJuvonen can you please merge this PR?

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint-server/docfx.json
:white_check_mark:Succeeded

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


docs: update LSP instructions

Context: version of Noir LSP extension was updated (0.0.11) to have better nargo executable visibility/selection.

Docs Preview
Hey there! 👋 You can check your preview at https://65e5ede324f0f9433736f79a--aztec-docs-dev.netlify.app


Official Gradle Wrapper Validation GitHub Action

See: https://github.com/gradle/wrapper-validation-action

Friendly ping about this


My new feature

Bower files were deleted
CSS was removed from .html to .css
made-with-love.html was moved up one level and its level dependancies
were updated.
index.html & demo.html were added for standard Polymer support
made-with-love.html markup was updated to work with index.html
some minor changes.

@AlbertSanIza I don't understand what you want removing bower files for ../ directory.
I understand that bower_components folder should be in .gitignore file. Here on my machine was all messy in directory above :(
The files index.html and demo.html should be in gh-pages branch for work with  http://randsonjs.github.io/made-with-love url.
And finally, if you can update README file I will be greatful :)
You can change these changes and squash your commits?
Glad you see this repo and send me a pull request.

@randsonjs  Hello there thanks for checking my pull request.
(sorry for bad english)
The reason I did that is because most of the new components has that directory, they are not being saved in the src folder.
Instead we have:
bower_components/made-with-love/made-with-love.html
bower_components/other-element/other-element.html
For the case of this component if I wanted to add it to a project I had this:
bower_components/made-with-love/bower_components/etc.
(wich is redundant)
and made-with-love.html was not at the same level as all the other components.. it was under src.
index.html and demo.html are ok in this branch to, because when working offline (if that is the case) or when you just don't want to search online... you can use them as docs... also if someone forks your project, they don't need to worry about generating everything for gh-pages its "already done".
readme must be updated to match this changes, but if there is no pull request, there is no need to change them.
Hope this was helpful.
let me know your comments :D

Thanks @AlbertSanIza, if exist any errors I'll fix later :)


⚠ Mobitopup has degraded performance

In 817ba8b, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4817 ms

Resolved: Mobitopup performance has improved in 091010c.


add grafana credential check

This adds another step check-grafana-credentials before collect metrics to ensure all the credentials are there before calling the collect metrics step.

@erikburt @chainchad what do you guys think about this check?
or should we add it here?
https://github.com/smartcontractkit/push-gha-metrics-action/blob/main/action.yml

@erikburt @chainchad what do you guys think about this check?

I think if we have to add this to every action then there's a lot of duplication. I guess ideally we update the action's source (the TS not the action.yml) to warn if the required parameters don't exist, instead of trying to make a request and then logging an error?

cool make sense :)


How to use coco dataset?

I've read guide documentation

https://mmdetection.readthedocs.io/en/latest/tutorials/new_dataset.html#customize-datasets-by-reorganizing-data

very many times but i don't know how to make it.
How can i configure?
Plz help me. Thank you.

In what format do you have your data? Is it in the coco format?

In what format do you have your data? Is it in the coco format?

oh, yes i have own coco dataset already : )

Let us assume you are using the mask_rcnn_r50_fpn_2x_coco for Instance Segmentation, then you can edit the class mmdetection/mmdet/datasets/coco.py and change the CLASSES to the classes you have.
Then you also edit the class 'configs/base/models/mask_rcnn_r50_fpn.py', and replace the num_classes with the number of classes you have, then you should be fine.
This is basically what I do. Do let me know if that works for you.

Let us assume you are using the mask_rcnn_r50_fpn_2x_coco for Instance Segmentation, then you can edit the class mmdetection/mmdet/datasets/coco.py and change the CLASSES to the classes you have.
Then you also edit the class 'configs/base/models/mask_rcnn_r50_fpn.py', and replace the num_classes with the number of classes you have, then you should be fine.
This is basically what I do. Do let me know if that works for you.

Oh! This is the long-awaited news for me !
OK i'm gonna try it now and i'll reply you if it works or not

Let us assume you are using the mask_rcnn_r50_fpn_2x_coco for Instance Segmentation, then you can edit the class mmdetection/mmdet/datasets/coco.py and change the CLASSES to the classes you have.
Then you also edit the class 'configs/base/models/mask_rcnn_r50_fpn.py', and replace the num_classes with the number of classes you have, then you should be fine.
This is basically what I do. Do let me know if that works for you.

Oh! This is the long-awaited news for me!
OK I'm gonna try it now and I'll reply to you if it works or not
I've edited all that you said.

I changed CLASSES = ('person', 'bycycle', 'car' ... etc) to CLASSES = ('person') in mmdetection/mmdet/datasets/coco.py.
I changed num_classes=80 to num_classes=1' in mmdetection/configs/base/models/mask_rcnn_r50_fpn.py`.

Then I tried python mmdetection/tools/train.py mmdetection/configs/detectors/mask_rcnn_r50_fpn_2x_coco.py
But I got an error like this.

Are there any things that I edited?

For some weird python reasons which I am not sure of, you need to have CLASSES = ('person', ) with the comma at the end rather than just having CLASSES = ('person') without the comma. Try that and let me know how that goes

For some weird python reasons which I am not sure of, you need to have CLASSES = ('person', ) with the comma at the end rather than just having CLASSES = ('person') without the comma. Try that and let me know how that goes

Oh, I mistake annotation file plz wait. Thanks @azibit u r angel.

For some weird python reasons which I am not sure of, you need to have CLASSES = ('person', ) with the comma at the end rather than just having CLASSES = ('person') without the comma. Try that and let me know how that goes

Oh, I mistake annotation file plz wait. Thanks @azibit u r angel.
Oh, bro, Reason of the error is my mistake.
My annotation file has "category_id" : "human" but i edited CLASSES = ('person') in mmdetection/mmdet/datasets/coco.py.
After i edit CLASSES = ('person') to CLASSES = ('human') training process works well!
Thank you @azibit.
 You're a lifesaver Thanks.

You are most welcome @blackCmd I wish you all the very best. Do let me know if you need anything else

You are most welcome @blackCmd I wish you all the very best. Do let me know if you need anything else

@azibit I executed image_demo.py in mmdetection/demo/` and I get this result.

But this is so weird. What are those that I indicate red arrows?

https://mmdetection.readthedocs.io/en/latest/tutorials/new_dataset.html#modify-classes-of-existing-dataset

For some weird python reasons which I am not sure of, you need to have CLASSES = ('person', ) with the comma at the end rather than just having CLASSES = ('person') without the comma. Try that and let me know how that goes

I know right, it's so weird. I spent 2 hours just to fix the missing comma


Action server does not register custom actions

I just added a custom action as explained in the tutorial, but rasa_core_sdk (action server) does not register my new action (file saved, rebuild, restart container..)
./actions
-/custom_actions
--/init.py
`class ActionFAQ(Action):
def name(self):
    return 'action_faq'`

-> OK
--/my_actions.py
`class GuestsAction(Action):
def name(self):
    return 'action_guests'`

-> Not registered (see screenshot) https://imgur.com/0I6xspD
All imports are done.
Do you have any idea what's the problem ?
Thank you.

@gothax is your file in the custom_actions folder? What is your OS?

@znat Yeah, i'm actually working on a MAC, but using Docker's containers.
https://imgur.com/QDLZXHh

Sometimes the logs are not contiguous, e.g. you might find your other registration further. Or... Did you run the watch script?
If none of the above works, the quick workaround is to move the code in my_action to init

@gothax did the above help?

@znat Nothing is happening when i try to call my custom action from the bot (even if it's declared on domain & stories).
When i create a custom action in init.py, it works. (The log register it).
Should i import  "custom_actions".py in the init.py to separate the differents custom actions in many files ?
The init is probably the only file which is imported and executed when rasa_core is reloading, no ?
Thanks for your help.

@gothax dis you run the watch script? (https://docs.botfront.io/guide/getting-started/rasa-stack.html#prepare-your-environment). It rebuilds the actions container on every change.

Nothing is happening when i try to call my custom action from the bot (even if it's declared on domain & stories).
You should.ar least see an error I'm the logs for calling an action that does not exist)

@znat I didnt run the watch script, but for now it works when i add actions to __init__file.
My problem is solved.


Jesse: Watch Bernie[\W_]*+Doran

Jesse requests the watch of the watch_keyword Bernie[\W_]*+Doran. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Bernie[\W_]*+Doran has been seen in 3 true positives, 0 false positives, and 0 NAAs.


[BUG] Documentation missing: how to deal with volumes?

Describe the bug
The documentation seems to be missing explanations on how to deal with volumes in harvester.
To Reproduce
Try to find out

what this does:

Find out in the documentation that online expansion of existing volumes is not possible.
Find out how to deal with left over / orphaned volumes (i.e. deleted RKE2 downstream cluster that had CSI)
more?

Expected behavior
We should have a chapter that explains how to deal with volumes in harvester.
How to verify that they have three replicas.
How to export / download images.. how to backup and restore volumes (not only VMs).
Maybe how to create snapshots?
Environment

Harvester ISO version: 1.0.3

Added Volume docs in v1.1 https://docs.harvesterhci.io/v1.1/volume/create-volume/

Thanks! Where can we see the replication / health status and is it supported to change the storage class on an existing volume (i.e. to move the volume from SSD to HDD or the other way)?

Where can we see the replication / health status?

Only in longhorn UI https://docs.harvesterhci.io/v1.1/troubleshooting/harvester#access-embedded-longhorn

is it supported to change the storage class on an existing volume?

image volumes -> no support
other volumes -> supported by:

take volume snapshot
using other storageclasses to restore the snapshot https://docs.harvesterhci.io/v1.1/volume/volume-snapshots#restore-a-new-volume-using-volume-snapshot

@futuretea  - thanks for the feedback! Could you add this info also to the Volumes docs section? Thanks!!

@futuretea - thanks for the feedback! Could you add this info also to the Volumes docs section? Thanks!!

OK


Fix[#2] separated routes

Fixes: #2 [Enhance code readability by nesting routes]
Files changed:

created routes.js
modified index.js

@suhanichawla plase look at it.


US 03.01.01

As a doer, I want to be uniquely identifiable in the system.

We are assuming this user story encompasses all of the user profiling. We are assuming this will be a lengthy process.

Completed and functional.  Closing.


Border Inconsistency in toolbar

Border is inconsistent at toolbar dropdown.
Steps to Reproduce:
Please refer the video clip:
https://drive.google.com/a/redhat.com/file/d/0BzAb-YONh7fscmRxb2ZXOUdXMTA/view?usp=sharing

Same behavior found with the filter from Angular Patternfly. In this example, we're switching from an input field to a dropdown menu, which uses a button with a 1px border.


JNI Support

I have a pretty solid base of a Swift JNI Wrapper ready. It doesn't do anything complex, but allows calling Java methods with varying levels of complexity, wraps some of the create jobject (e.g. Array) functions etc. At the moment it's coupled into my program code, but I'd like to make it a separate module and publish it as a part of SwiftAndroid.
For some reason I could only get JNI importing if I include $(NDK_PATH_TO_INCLUDE)/jni.h in the Bionic wrapper at the swift codebase level. Instead of that we'd ideally make JNI a separate Module so we can import JNI instead of import Glibc. I tried adding another target and ended up with no change in the output (my experience so far is that the build system seems to just ignore everything I do) – so I evidently don't understand the build system enough to do that.
I also couldn't seem to make a standard module out of it using the Package Manager, but that'd probably be the most maintainable solution in the medium-term. As a short aside, different users will want to target different Android-JDK versions, so maybe it'd be best to have users build the module themselves with a short script.
There's also the question of whether we include the Swift wrapper or just export the raw C functions. The C functions are a bit of a nightmare to work with, especially without an IDE, so my vote would be to include the Swift wrapper.
So this is me gauging interest / requesting help in packaging the module correctly and working on the wrapper for various use-cases.

For the Package Manager, I tried following the instructions from https://github.com/apple/swift-package-manager/blob/master/Documentation/SystemModules.md and was able to get jni.h importing on regular Linux openjdk, so I guess the procedure would be similar (create package, git commit, git tag, add to dependencies) for Android.
How do we take into account the install path of the NDK on each user's computer? Do we generate a module.modulemap at install or first run time?

As far as I can see, we'd have the same issues with a swiftpm module as with an 'inbuilt' package that is bundled with with Android Swift installations. Given that it's pretty much pointless to have Swift on Android without the JNI, my strong inclination would be to compile it alongside the stdlib (like Glibc/Bionic).
As for how to get the NDK path, according to http://clang.llvm.org/docs/Modules.html you can use relative paths in module maps. That means, depending where we install swift, we could have users symlink the NDK path and add on our subpath to that.
install_path
---> swiftbin
---> NDK (link)

Then again, if swift gets installed to (e.g.) /usr/local/bin, we'll have to think of something else.

Also, I saw that commit about adding a module, but noticed that I can't actually import Bionic either. Apparently it overlays the SDK correctly (otherwise I couldn't use the libc functions, I guess), but I don't get a separate module. Is that the same for you, or is there something else I need to do to get it working?

I've just pushed a jni-swift branch with some wrapper functions I've used so far in my swift android projects

Now that Android support is merged upstream, we're beginning to use Swift JIRA to track Android issues. @ephemer, if you're still interested in this, could you create a JIRA task (with the "Android" label) that summarizes the work done here, what needs to be done, and what open questions there are? I think a lot of people would appreciate it!!

@modocache thanks for bringing this up. I've created an issue for further discussion on JIRA: https://bugs.swift.org/browse/SR-1690. Going to close this GitHub issue now


CI, MAINT: special test_intermediate_overlow failure with latest NumPy (bisected)

The failure can be observed here: https://github.com/scipy/scipy/actions/runs/6878964267/job/18709821055?pr=19523
And summarized/preserved below the fold:

 __________________________ test_intermediate_overlow ___________________________
[gw1] linux -- Python 3.12.0 /opt/hostedtoolcache/Python/3.12.0/x64/bin/python
scipy/special/tests/test_trig.py:45: in test_intermediate_overlow
    assert_allclose(sinpi(p), std)
        p          = (1.00000000000001+227j)
        sinpi_pts  = [(1.00000000000001+227j), (1e-35+250j), (1e-301+445j)]
        sinpi_std  = [(-8.113438309924894e+295-infj), (1.9507801934611995e+306+infj), (2.205958493464539e+306+infj)]
        std        = (-8.113438309924894e+295-infj)
        sup        = <numpy.testing._private.utils.suppress_warnings object at 0x7f14e8d499a0>
/opt/hostedtoolcache/Python/3.12.0/x64/lib/python3.12/contextlib.py:81: in inner
    return func(*args, **kwds)
E   AssertionError:
E   Not equal to tolerance rtol=1e-07, atol=0
E
E   Mismatched elements: 1 / 1 (100%)
E   Max absolute difference among violations: nan
E   Max relative difference among violations: nan
E    ACTUAL: array(-8.113438e+295-infj)
E    DESIRED: array(-8.113438e+295-infj)
        args       = (<function assert_allclose.<locals>.compare at 0x7f14eb463060>, array(-8.11343831e+295-infj), array(-8.11343831e+295-infj))
        func       = <function assert_array_compare at 0x7f14fe931e40>
        kwds       = {'equal_nan': True, 'err_msg': '', 'header': 'Not equal to tolerance rtol=1e-07, atol=0', 'strict': False, ...}
        self       = <contextlib._GeneratorContextManager object at 0x7f14fe93aba0>

I bisected on NumPy and found the commit below, so maybe @mdhaber might have thoughts on it. It could be that improvements to the NumPy testing machinery actually caught something we didn't catch before, or it could just be some subtle issue with handling non-finite values on the NumPy side, not sure from a quick look, but this gets the dissection started at least.
303015970238ee140da3a0b71e7e9ada0c762d90 is the first bad commit
commit<PHONE_NUMBER>38ee140da3a0b71e7e9ada0c762d90
Author: Matt Haberland<EMAIL_ADDRESS>Date:   Sat Oct 28 23:44:55 2023 -0700

    MAINT: isclose/allclose: simplify support for array-like tolerances

 .../upcoming_changes/14343.future_change.rst       |  5 ----
 doc/release/upcoming_changes/24878.improvement.rst |  5 ++++
 numpy/_core/numeric.py                             | 23 ++++++--------
 numpy/_core/tests/test_numeric.py                  | 35 ++++++++++++----------
 4 files changed, 34 insertions(+), 34 deletions(-)
 delete mode 100644 doc/release/upcoming_changes/14343.future_change.rst
 create mode 100644 doc/release/upcoming_changes/24878.improvement.rst

I'll take a look.

Continued discussion of what exactly should be expected at https://github.com/numpy/numpy/pull/24878#issuecomment-1823861087

I merged the temporary skip for this test for now. My reasoning is summarized in the cross-listed PR, but is simply based on a reading through of what Marten and Matt have discussed (it sounds sufficiently complex/philosophical that it may take a little bit to resolve upstream). For now, checking that the real part matches to desired precision while the non-finite complex part simply points in the appropriate "infinity direction" seems like a compelling solution to me.


Force users to reset passwords on the first logins

I want admin users to manually create other users and make the created users reset their passwords on their first logins.
How can I implement a feature like this with devise_token_auth???

Not sure, but devise_invitable can help you to accomplish what you need.
https://github.com/scambra/devise_invitable

=> create(user)
=> reset_password_token
=> send an email with a link to reset password (with token)

@Tioneb12
Thanks for replying!
I think that would be the most straightforward way to achieve it with this gem. You can just restrict users from accessing the content unless they've changed the default passwords.
As for checking if the users changed their default passwords, you can add a column called password_updated_at: DateTime to your user's table and set the default value to CURRENT_TIMESTAMP and update it every time a user changes its password. That way, you can compare password_udpated_at to created_at and can know whether the user updated the default password or not.
(This is just an example and there are many other ways to check it)


Uncaught exception when using OverflowMenu

I'm getting this uncaught exception when trying to use the OverflowMenu from dialog.module. I'm on Angular 5.x and carbon-components-angular 1.8.1.

and after commenting out temporarily that particular line, it's still complaining about the 'options':

when used as per documentation:

Documentation needs an update...
Storybook gives a usage example:
<ibm-overflow-menu>
	<ibm-overflow-menu-option>Option 1</ibm-overflow-menu-option>
	<ibm-overflow-menu-option>Option 2</ibm-overflow-menu-option>
</ibm-overflow-menu>

First exception as shown above is still there. In addition, after I commented out that line (temporarily), now I'm getting this exception:

After commenting out this line, it got rendered ( i.e. the three vertical dots ).

We require a peer of rxjs@6 ... fromEvent and friends don't exist in<EMAIL_ADDRESS>An update should fix this, let us know if it doesn't :+1:

Also we require a peer of angular@6 ... I suggest you check your dependencies against our peerDependancies and update accordingly

In the context of an established product, unfortunately upgrading to angular-6, or even just to rxjs-6 is not as simple and may not be even possible as there're just too many implications. Is there anyway to make this library to be backward compatible with angular-5, rxjs-5? It's just a pity, if because of few items like this we end up can't use / adopt this library. Thanks!

That's, unfortunately, not something we can dedicate resources to, right now. Those implications go both ways.
You could look into somehow polyfilling missing parts, like fromEvent.

for reference, this is now possible by using: "rxjs": "~5.6.0-forward-compat.5",


Is that works with the MiR250?

First of all, thanks so much for your repositorie, that's very helpful.
Our lab want to buy a MiR250 and would like use ROS to control it. Not sure if anyone test it?
I saw you are test in MiR 100/200/500. But I didn't see these solutions in them web.
Thanks so much.

I'm pretty sure it works with the MiR250. I haven't tested it myself, but from a software perspective all MiR robots are very similar.

I'm pretty sure it works with the MiR250. I haven't tested it myself, but from a software perspective all MiR robots are very similar.

Thanks so much, that's will be great!

I tested on two different MiR250 and I can confirm that the repo works reliably for both of them.

I tested on two different MiR250 and I can confirm that the repo works reliably for both of them.

Thanks so much!


prow job for ack/pkg unit tests

In order to ensure the proper functioning of code-generator/pkg packages - we need to add new unit tests prow job for github.com/aws-controllers-k8s/pkg

/assign


Improve integration tests

[ ] get rid of the delays and delay method
[ ] add env var for indexer refresh period and make it lower for integration tests (around 5s)
[ ] find a replacement for waitToIndex()
[ ] maybe concatenate some of the flows and reuse parts of the logic
... to be extended

for the delays, timeouts,  maybe its worth try emit / listen events instead,  to trigger notifications for certain actions, instead of relying on pooling mechanisms

will take care of this one too

We should also look out for any try / catches that are used in the tests and might hide issues or failed requests. These can lead to the tests passing with just an error being logged, without the test itself failing. For example, the start order test in src/test/integration/completeFlow.test.ts:
  it('should start an order', async function () {
    this.timeout(15000) // Extend default Mocha test timeout
    try {

         ...

    } catch (error) {
      console.log(error)
    }
  })

closed on https://github.com/oceanprotocol/ocean-node/pull/267


Discrepancy in CPU Inference Latency: Cross-Encoder MiniLM Models vs. ColBERT

Greetings :wave:
I've been benchmarking the CPU inference latency for various models and observed some significant differences. Specifically, I'm comparing the performance of the sentence_transformers 'cross-encoder/ms-marco-MiniLM-L-12-v2' with other models. The latency for the top 10 re-ranking seems to vary quite a bit, and I'm trying to understand if this is an expected behavior or if there might be an issue with my setup.
For clarity, here's a quick summary of the latencies I've recorded:

ColBERT:  620 ms
Cross-encoder MiniLM-L-12-v2: 309 ms
Cross-encoder MiniLM-L-6-v2: 150 ms
I've attached a visual representation of these findings for reference:

Could someone please shed some light on this? Is there a particular reason why the ColBERT model has over double the latency of MiniLM-L-12-v2? Any insights or suggestions for improving the inference speed of ColBert on CPU would be greatly appreciated.

I think this isn't shocking given how reranking with ColBERT works, though I'd expect it to be a bit quicker. The main factor at play here is that MiniLM-L-12 is just ~35M parameters (L-6 is around 22M for comparison), whereas ColBERTv2 is 110, so a bit more than 3 times as big, which'll explain why it runs a lot slower comparatively.
The strenght of ColBERT as a reranker however is that you can pre-compute document representations in advance, which you cannot do with cross-encoders. In such a set-up it'd run noticeably quicker than cross-enc alternatives!


Update docs for new WPF/WinForms controls

Updates in this PR for WPF/Windows Forms controls:

New article for MapControl
Removed "coming soon" text about Windows Forms in all WPF/Windows Forms controls
Other miscellaneous updates for consistency/style

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/InkCanvas.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/InkToolbar.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MapControl.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MediaPlayerElement.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebView-known-issues.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebView.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebViewCompatible.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

docs/resources/images/Controls/MapControl.png
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

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


Allow for more thorough testing CI

Right now, we test extensively on Windows via Codeship, but not too much on Travis.  We need to add support for 32bit Linux as well as Mac OS.

Maybe just add cargo test --release on to the post build action for travis?

Travis now tests MacOS and automatically publishes tagged commits as releases, yay!  On the todo list: test 64b/32b linux (and mac if that's a thing).  Should be somewhat easy with travis.

I'm going to close this for now since I think CI is pretty robust.  We can update in the future if we need different arch support.


Troubleshooting time series layer behavior

@astrojonathan Here is an environment where you can test pywwt directly to figure out what's going on. I've added console.log statements to the wwt_json_api.js file from earlier that should print messages to the console to let you know what's being passed to the SDK. The instructions to set it the time series test are as follows.
Install the developer version of pywwt in terminal (if you don't have it already):
git clone https://github.com/WorldWideTelescope/pywwt.git
cd pywwt
pip install -e .

Clone this pull request branch to your machine:
git checkout -b ojustino-layer-time master
git pull https://github.com/ojustino/pywwt-web.git layer-time

It's possible to run pywwt via script, but it might be better to troubleshoot interactively on this one, so go to the pywwt/nbextension/static directory, open IPython on the command line, and then copy/paste as instructed from time_test.py.
A Qt window running the same wwt.html file we worked from last week will pop up once you've copied, pasted, and run the code block with the imports from time_test.py.

The first three of the new commits are focused on making what I hope are small improvements in trait functionality by expanding the docstrings for TableLayer traits, making the error messages in AstropyQuantity and Color more informative, and resolving some JS TypeErrors that arose from the wwt.*ground attributes having a flag they shouldn't have.
@pkgw, the most notable development is that I got time series layers to show up in the Qt version. I was also able to get decay working, so, if the user wants, they can make it so points disappear after a specific amount of time. (I also added time_test.ipynb to verify that things were still working for a Jupyter notebook in Firefox.)
I hear the concern in #175 about parsing dates from strings, but I don't think there's another way to do it that works for the Qt version. My solution verifies that those strings all conform to the ISOT standard before passing them to WWT. ISOT is browser-independent and should hopefully then be friendly with WebKit, Chromium, and Firefox.
As for time zones in Qt, I used datetime to find the user's current time and add the offset between that and the current UTC time to values in the time column before passing the column to WWT. The current drawback of this approach is Daylight Saving Time. If the user's current DST status is not the same as it is for the dates in their time column, there's a one hour offset. (The test script for the Qt version illustrates this discrepancy since the events are set in January.) It's also assumed that users are providing UTC times, but I hope that can be expanded in the future.
Other questions I have are marked in comments beginning with 'ISSUE' in layers.py, but that's the general summary. It would be great if @astrofrog could take a look and see how my implementation fits with how the rest of that file was set up.

OK, I changed wwt.set_current_time in core.py to also pass an ISOT string to WWT. (I also made a corresponding change in wwt_json_api.js .) I also integrated the pytz package to help verify/convert time zones for values provided to that method and in the time column of a table layer. These steps eliminated the issues I was having with DST, and the points from the table in the time_test files now pop up when they should in both Qt and Jupyter (on Firefox).
If this looks close to implementation we'll use going forward, I can go ahead and update the docs (for both table and image layers) and update the change log.
I wasn't sure how to handle adding a 'Z' to ISOT strings when some of them may already have a 'Z' or a '-05:00' at the end for time zone specification, so I didn't yet do so. I'm not sure if things are now synchronized because both wwt.set_current_time and the time series layer are in UTC or because they're both in the user's local time. Is there a simple way to test this?

I went ahead and added a method to core.py that returns the current time in the viewer -- wwt.get_current_time(). I followed @jsub1's methodology from #206 to ensure it works in Jupyter.
After reinstalling the directory with pip (due to changes to wwt.js), it seems to work as intended.

I also made more edits to TableLayer so it can now read time columns made from a) astropy Time, b) datetime.datetime (with or without time zone information), or c) UTC ISOT strings. It then turns the column entries into ISOT strings with a specified "+0:00" time zone (as suggested by @astrofrog). This removes the discrepancies in time between the Qt and Jupyter versions and ensures we are always working in UTC.
All that's left out is ISOT strings with time zones (e.g. "2014-06-30T22:00:34+03:00"). This is because I use astropy's Time to verify them, and Time seems to only accept ISOT strings with no time zone info or with a 'Z' for UTC at the end. Should we try to support them, too?
I also corrected some tests in the validation of time_att that weren't doing what I thought they were.

@ojustino OK, the CI is now getting a bit farther. It's now erroring out because it thinks that some of your test files are pytest tests and tries to run them as such, which doesn't work. If you're ready to remove your test files, doing so would help the CI make more progress.

@pkgw OK, I guess they'll still be there in the old commits. Did you get a chance to test out the time series functionality or wwt.get_current_time? If you or @astrofrog could, it would be helpful.

OK, I've been exploring this and am seeing some weird stuff that I think is a lot more about how the WWT engine works than the pywwt layer. For reference, here's the outline of a test notebook I'm using:
# ---- new cell ----
from pywwt.jupyter import WWTJupyterWidget
import numpy as np
from astropy import units as u
from astropy.table import Table
from astropy.time import Time

# ---- new cell ----
wwt = WWTJupyterWidget()
wwt.pause_time()
t0 = wwt.get_current_time()
wwt

# ---- new cell ----
n = 30
TIMESPAN = 100
ra_deg = np.linspace(0, 40, n)
dec_deg = np.zeros(n)
unix_times = t0.unix + np.linspace(0, TIMESPAN, n)
iso_times = [Time(ut, format='unix').isot for ut in unix_times]
table = Table({'ra': ra_deg, 'dec': dec_deg, 'time': iso_times})
layer = wwt.layers.add_data_layer(
    table,
    lon_att = 'ra', lat_att = 'dec', lon_unit = u.deg,
    time_att = 'time', time_series = True,
    size_scale = 60
)

# ---- new cell ----
wwt.set_current_time(t0)
wwt.play_time()

I'll see a dot show up, but in clumps instead of uniformly ... does WWT's time system lose precision at the few-second level? I'd be surprised.
Still trying to understand what's going on, but I wanted to write down the example that I'm looking at.

@pkgw I went over the results of pytest and fixed some that were failing due to changes I made in this PR. There are still 6 of 48 that fail -- a few mismatched images and a few that don't touch on time series layers.
I also updated the change log and moved the entry under 0.6.2 to 0.7.0 since it looks like we're going to skip the former.

The same behavior happens for me with your example, but if you try time_test.ipynb from commit ffa8d5b, the points appear one-by-one even though most are within a few (<5) seconds of one another. One difference is that my example is in solar system mode, though I don't know if that should matter.

Actually, your test now works as intended for me. Did you use pip install -e . after pulling the most recent changes to the PR? I tested on a different machine and that's what fixed things. (I could tell something was wrong because wwt.get_current_time() wasn't changing, and it only works after a fresh install since it involves some changed code in wwt.js.)

This was an arduous rebase; I have to do it over.

OK, I was able to track down my problem. It is in fact a precision issue in the WebGL shader implementation in the WWT SDK; the date calculations in SpreadSheetLayer are done relative to a baseDate field that is hardcoded to be January 1, 2010. Date differences that exceed floating-point precision away from that date will expose roundoff errors. So, if I change my example to fix it dates to be near baseDate, everything works OK:
# ---- new cell ----
from pywwt.jupyter import WWTJupyterWidget
import numpy as np
from astropy import units as u
from astropy.table import Table
from astropy.time import Time

t0 = Time('2010-01-01T12:00:00.000', format='isot')

# ---- new cell ----
wwt = WWTJupyterWidget()
wwt.pause_time()
wwt

# ---- new cell ----
n = 30
TIMESPAN = 100
ra_deg = np.linspace(0, 40, n)
dec_deg = np.zeros(n)
unix_times = t0.unix + np.linspace(0, TIMESPAN, n)
iso_times = [Time(ut, format='unix').isot for ut in unix_times]
table = Table({'ra': ra_deg, 'dec': dec_deg, 'time': iso_times})
layer = wwt.layers.add_data_layer(
    table,
    lon_att = 'ra', lat_att = 'dec', lon_unit = u.deg,
    time_att = 'time', time_series = True,
    size_scale = 60
)

# ---- new cell ----
wwt.set_current_time(t0)
wwt.play_time()

We could reduce these issues by wiring up something to change baseDate to be (e.g.) the mean date of the table, or something like that. While this isn't an issue I want to spend too much effort on, it did come up in literally the first manual example I tried, so it seems like something that should at least be documented. I'll ponder a bit more ... anyone else have thoughts?

The mean data would definitely be better than the lower date especially if we can remove outliers that are effectively null dates.


Bug: Cache keys erros using throttle

Describe the bug
When using throttle, the cache keys error occurs. Just instantiate and put in middeware as it is in the documentation.
If used the host localhost causes the error.
Error:

Print key:

File error:

CodeIgniter 4 version
4.1.3
Context

OS: Windows 10
Web server PHP - Server
PHP version 7.4

Resolved via #4908


Random renaming todos

For ease of readability.

Codecov Report

Merging #259 (14724dc) into main (b2d967b) will not change coverage.
The diff coverage is 50.00%.

@@           Coverage Diff           @@
##             main     #259   +/-   ##
=======================================
  Coverage   24.87%   24.87%
=======================================
  Files          31       31
  Lines        3063     3063
=======================================
  Hits          762      762
  Misses       2184     2184
  Partials      117      117

Impacted Files
Coverage Δ

pkg/server/router/presentation.go
3.46% <0.00%> (ø)

pkg/server/server.go
81.96% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


DeviceHistogram::HistogramEven and DeviceHistogram::MultiHistogramEven failing for some cases

Some change in cub/device/dispatch/dispatch_histogram.cuh from CUB 2.0.0 makes the test test_device_histogram.cu fail when HistogramEven is called with

CounterT
OffsetT
bins
lower_level
upper_level

int
int
65536
0
65536

and

SampleIteratorT
LevelT

int
int

double
float

and when MultiHistogramEven is called with

NUM_CHANNELS
NUM_ACTIVE_CHANNELS
CounterT
OffsetT
bins
lower_level
upper_level

1
1
int
int
65536
0
65536

and

SampleIteratorT
LevelT

int
int

unsigned short
int

float
int

double
int

double
float

Thanks for reporting the issue, @Beanavil. The issue has been addressed by https://github.com/NVIDIA/cub/pull/632 and should now be fixed.


[stable/nginx-ingress] NodePort http/https not working

I am wishing to run nginx-ingress on my home-grown Kubernetes cluster (Ubuntu VM's running via libvirt/kvm on Ubuntu host) listening on ports 30080 and 30443 for http/https respectively on my controller-nodes. Specifying the below helm command line along with values.yaml, the log for the controllers still claim it is trying to listen on port 80.
Version of Helm and Kubernetes:
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}

from 'kubectl version':
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:14:56Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/nginx-ingress
with values.yaml:
controller:
  replicaCount: 2
  minAvailable: 2
  tolerations:
  - key: "key"
    operator: "Equal"
    value: "value"
    effect: "NoSchedule"
  nodeSelector:
    role: controller
  stats:
    enabled: true
  podSecurityPolicy:
    enabled: True
  service:
    type: "NodePort"
    nodePorts:
      http: 30080
      https: 30443

What happened:
W0611 00:51:47.973409       5 queue.go:130] requeuing initial-sync, err
-------------------------------------------------------------------------------
Error: exit status 1
2019/06/11 00:51:47 [notice] 33#33: ModSecurity-nginx v1.0.0
nginx: the configuration file /tmp/nginx-cfg608773841 syntax is ok
2019/06/11 00:51:47 [emerg] 33#33: bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: configuration file /tmp/nginx-cfg608773841 test failed

-------------------------------------------------------------------------------
W0611 00:51:50.405483       5 queue.go:130] requeuing default/nginx-ingress-release-controller, err
-------------------------------------------------------------------------------
Error: exit status 1
2019/06/11 00:51:50 [notice] 41#41: ModSecurity-nginx v1.0.0
nginx: the configuration file /tmp/nginx-cfg785766829 syntax is ok
2019/06/11 00:51:50 [emerg] 41#41: bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: configuration file /tmp/nginx-cfg785766829 test failed
------------------------------------------------------------------------------

What you expected to happen:
Ports 30080 and 30443 would begin listening on those controller hosts pointing to my nginx ingress controller.
How to reproduce it (as minimally and precisely as possible):
helm --kubeconfig /nas1/git/kubernetes/configs/prod/admin/admin.kubeconfig install stable/nginx-ingress --name nginx-ingress-release -f /nas1/git/kubernetes/configs/helm/nginx-ingress/values.yaml

See above for contents of values.yaml
Anything else we need to know:

If you don't need pod security policy to manage the container's security. You should set that's false. Or, you should override the podsecuritypolicy.yaml

@Aisuko What in the podsecuritypolicy.yaml would I change? I am running k8s 1.14.2 with PSP enabled, but looking at that YAML all seems correct (the nginx ingress pod is running as UID 33, not root), and the ports i'm trying to bind (30080 and 30443) are within the 1-65535 range.
Are there other logs I could look at to determine if this is indeed a PSP problem?

I believe I've started to figure it out.
I believe it has to do with AppArmor in kubernetes 1.14.
I notices two different lists of annotations on two nginx-ingress controller pods on different clusters I have:
k8s 1.12 (nginx-ingress-controller 0.22.0):
Annotations:
k8s 1.14 (nginx-ingress-controller 0.24.1):
Annotations:        container.apparmor.security.beta.kubernetes.io/nginx-ingress-controller: runtime/default
kubernetes.io/psp: 999-privileged
seccomp.security.alpha.kubernetes.io/pod: docker/default
By setting:
controller:
podAnnotations:
container.apparmor.security.beta.kubernetes.io/nginx-ingress-controller: unconfined
in my values.yaml, the pods start up!
I still want to see if I can find some logs on the host machine complaining about the AppArmor violations.

Actually the pod starts up, but then gets killed by the PSP. Time to go back to using AppArmor but getting the PSP correctly configured for this service account to be able to use it.

@Aisuko Is there any reason why the podsecuritypolicy.yaml is not being populated and applied? When I perform a 'kubectl get psp', the PSP provided by the nginx-ingress chart is not present.

@jforman Please check your value.yaml about
https://github.com/helm/charts/blob/4527ebe8a36180ddd16973acddf476abe7264cfe/stable/nginx-ingress/values.yaml#L384
The default was false turn to 'true'

I am wishing to run nginx-ingress on my home-grown Kubernetes cluster (Ubuntu VM's running via libvirt/kvm on Ubuntu host) listening on ports 30080 and 30443 for http/https respectively on my controller-nodes. Specifying the below helm command line along with values.yaml, the log for the controllers still claim it is trying to listen on port 80.
Version of Helm and Kubernetes:
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}

from 'kubectl version':
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:14:56Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/nginx-ingress
with values.yaml:
controller:
  replicaCount: 2
  minAvailable: 2
  tolerations:
  - key: "key"
    operator: "Equal"
    value: "value"
    effect: "NoSchedule"
  nodeSelector:
    role: controller
  stats:
    enabled: true
  podSecurityPolicy:
    enabled: True
  service:
    type: "NodePort"
    nodePorts:
      http: 30080
      https: 30443

What happened:
W0611 00:51:47.973409       5 queue.go:130] requeuing initial-sync, err
-------------------------------------------------------------------------------
Error: exit status 1
2019/06/11 00:51:47 [notice] 33#33: ModSecurity-nginx v1.0.0
nginx: the configuration file /tmp/nginx-cfg608773841 syntax is ok
2019/06/11 00:51:47 [emerg] 33#33: bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: configuration file /tmp/nginx-cfg608773841 test failed

-------------------------------------------------------------------------------
W0611 00:51:50.405483       5 queue.go:130] requeuing default/nginx-ingress-release-controller, err
-------------------------------------------------------------------------------
Error: exit status 1
2019/06/11 00:51:50 [notice] 41#41: ModSecurity-nginx v1.0.0
nginx: the configuration file /tmp/nginx-cfg785766829 syntax is ok
2019/06/11 00:51:50 [emerg] 41#41: bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: [emerg] bind() to <IP_ADDRESS>:80 failed (13: Permission denied)
nginx: configuration file /tmp/nginx-cfg785766829 test failed
------------------------------------------------------------------------------

What you expected to happen:
Ports 30080 and 30443 would begin listening on those controller hosts pointing to my nginx ingress controller.
How to reproduce it (as minimally and precisely as possible):
helm --kubeconfig /nas1/git/kubernetes/configs/prod/admin/admin.kubeconfig install stable/nginx-ingress --name nginx-ingress-release -f /nas1/git/kubernetes/configs/helm/nginx-ingress/values.yaml

See above for contents of values.yaml
Anything else we need to know:

controller:
  replicaCount: 2
  minAvailable: 2
  tolerations:
  - key: "key"
    operator: "Equal"
    value: "value"
    effect: "NoSchedule"
  nodeSelector:
    role: controller
  stats:
    enabled: true
 podSecurityPolicy:
    enabled: True
  service:
    type: "NodePort"
    nodePorts:
      http: 30080
      https: 30443

Is your podsecuritypolicy.yaml have been change for Values.controller.podSecurityPolicy.enabled
https://github.com/helm/charts/blob/120415f9ef44fda52d4b1da3e1a3fa38bfcfc2ea/stable/nginx-ingress/templates/podsecuritypolicy.yaml#L1


Prune policy from regional hub when deleting policy from global hub

Signed-off-by: myan<EMAIL_ADDRESS>Ref: https://github.com/stolostron/backlog/issues/25859

/retest

/retest

/lgtm


[DO NOT MERGE] Tags: Add support for TagScope.

Fixes https://github.com/census-instrumentation/opencensus-java/issues/1666.
Spec is https://github.com/census-instrumentation/opencensus-specs/blob/master/tags/TagMap.md#tagscope.
Note that this is a breaking change because from now on TagContext will be non-propagating by default.

Going to submit a new PR with TagMetadata as per https://github.com/census-instrumentation/opencensus-specs/pull/233/. Closing this PR for now, since there will be a lot of changes.


JupyterBook Class overrides manual config changes in _config.yml

When using the jupyterbook-latex extension and then making an override to latex_docclass or latex_elements, jupyterbook still compiles with the jupyterbook_latex .cls file, which includes fontsize information as well. Here's the relevant part of my _config.yml
sphinx:
  extra_extensions:
    - jupyterbook_latex
  config:
    latex_elements:
      pointsize: 12pt
    latex_docclass:
      manual : article

From what I see now, it also depends on whether you put the extra extension before or after config. Is that intended behavior?

From what I see now, it also depends on whether you put the extra extension before or after config. Is that intended behavior?

Hey @amichuda, thanks for testing out this case. This is not intended behavior and I agree that the values specified manually should override the .cls file. Will have a look at it.


ci: support spell-checker

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Refactoring
[x] Build or CI related changes
[ ] Documentation content changes

What is the new behavior?
Best practice for big projects:
https://github.com/prettier/prettier/blob/main/cspell.json
https://github.com/swc-project/swc/blob/main/cspell.json
https://github.com/webpack/webpack/blob/main/cspell.json

@vladimirpotekhin @nsbarsukov hello, please review me)

@nsbarsukov hello, please review me


new file that uses DevEx include

Docs Build status updates of commit 76f1cf1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/choose-the-right-command-line-tool.md
:warning:Warning
View
Details

docs-ref-conceptual/choose-the-right-command-line-tool.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1b70b80:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

docs-ref-conceptual/choose-the-right-command-line-tool.md
:x:Error

Details

docs-ref-conceptual/choose-the-right-command-line-tool.md

Line 14, Column 1: [Error-include-not-found] Invalid include link: 'https://github.com/MicrosoftDocs/azure-dev-docs-pr/blob/master/articles/includes/choose-the-right-azure-command-line-tool.md'.
Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Closing this POC branch that was not meant to be published


System.DivideByZeroException within pwsh on linux

Environment data
# pwsh -c '
& {
    "PS version: $($PSVersionTable.PSVersion)"
    "PSReadline version: $((Get-Module PSReadline).Version)"
    if ($IsLinux -or $IsOSX) {
        "os: $(uname -a)"
    } else {
        "os: $((dir $env:SystemRoot\System32\cmd.exe).VersionInfo.FileVersion)"
    }
    "PS file version: $((dir $pshome\powershell.exe).VersionInfo.FileVersion)"
}'
PS version: 6.0.0-rc.2
PSReadline version:
os: Linux 18227f8f3aba 4.4.108-boot2docker #1 SMP Wed Dec 27 23:32:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
dir : Cannot find path '/opt/microsoft/powershell/6.0.0-rc.2/powershell.exe' because it does not exist.
At line:10 char:26
+     "PS file version: $((dir $pshome\powershell.exe).VersionInfo.File ...
+                          ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (/opt/microsoft/.../powershell.exe:String) [Get-ChildItem], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

Steps to reproduce or exception report

docker run -it microsoft/vsts-agent
in separate shell

docker exec -it <id of the container just started> /bin/bash
pwsh

PowerShell v6.0.0-rc.2
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /vsts>
Oops, something went wrong.  Please report this bug with the details below.
Report on GitHub: https://github.com/lzybkr/PSReadLine/issues/new
-----------------------------------------------------------------------
Last 0 Keys:

Exception:
System.DivideByZeroException: Attempted to divide by zero.
   at Microsoft.PowerShell.PSConsoleReadLine.Initialize(Runspace runspace, EngineIntrinsics engineIntrinsics)
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics)
-----------------------------------------------------------------------

Have the same issue with the vsts container as described by @lestephane .
Its blocking us because we could not use azure powershell sdk https://docs.microsoft.com/de-de/powershell/azure/install-azurermps-maclinux?view=azurermps-5.5.0
could you please look into this

I tried on a Debian 9 container, and couldn't reproduce the crash. Never tried on VSTS container though.
root@1ed6879ac3d8:/# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@1ed6879ac3d8:/#
root@1ed6879ac3d8:/# pwsh
PowerShell v6.0.2
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /> gmo

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Manifest   <IP_ADDRESS>    Microsoft.PowerShell.Utility        {Add-Member, Add-Type, Clear-Variable,...
Script     2.0.0      PSReadLine                          {Get-PSReadLineKeyHandler, Get-PSReadL...

@daxian-dbw  I added the container link which I can reproduce the issue

@joachimaumann I cannot reproduce the crash with the docker image microsoft/vsts-agent.
Could this be related to the host OS? Can you please provide detailed repro steps?
Please see the screenshot below:

I'm not longer able to reproduce with the latest image
REPOSITORY                             TAG                 IMAGE ID            CREATED             SIZE
microsoft/vsts-agent                   latest              3b66c4a0d020        5 days ago          5.72GB

So OK to close?

As far as I'm concerned, yes.
On Sun, Apr 1, 2018 at 9:35 PM, Jason Shirk<EMAIL_ADDRESS>wrote:

So OK to close?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzybkr/PSReadLine/issues/618#issuecomment-377807157,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFNTlDSO09KMN47KgjZOAXIMFquUj6A7ks5tkR4NgaJpZM4RcrAm
.

OK, closing.


Cylindrical axis orientation in README; refreshed external URLs, RTD config, Python versions

Let's say explicitly in README that the cylindrical axis for all Abel transforms is vertical, as this is not immediately obvious and keeps confusing some users (for example, #388, #383, #362, and several times before).
There also was a warning in a recent Read the Docs buid (for #387):

WARNING: Calling get_html_theme_path is deprecated. If you are calling it to define html_theme_path, you are safe to remove that code.

treated as a build error (due to fail_on_warning: true), so I've just removed that get_html_theme_path(), as suggested.
The supported Python versions are also updated up to 3.13 (released this month) — the tests pass locally on my system, and hopefully are already supported by Travis and AppVeyor.
And, last but not least, I've updated the rotten/moved external links in the documentation.

Hello @MikhailRyazanov! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file doc/conf.py:

Line 135:1: E265 block comment should start with '# '

OK, RTD seems to work.
@DanHickstein, could you please check what happened with Travis CI? We were already unhappy with it ~2 years ago (#365), but recently it has stopped running out tests completely — if I remember correctly, #373 was the first time, and since then it never worked. If the problem has a simple solution, we should probably include it in this PR (it needs a minor update anyway, as I forgot to include “3.13” in setup.py). But if not, we should really do something to address #365...

6-week old baby

Congratulations @DanHickstein !

Thanks @stggh and @DanHickstein! Travis started working again (perhaps emailing them indeed helped), but I was also experimenting with GitHub Actions (in my test repository), with encouraging results, so I'll work on migrating from Travis after ensuring that everything works as expected...

Travis started working again (perhaps emailing them indeed helped)

Yup, they emailed me back and said that it should work now. Presumably they added more credits to our account or something.

Congratulations @DanHickstein !

Thanks!! :)


Vault auto-unseal with AWS KMS

Use AWS KMS to auto-unseal Vault server when started/restarted. This ensures that the Vault unseal key(s) are not stored in plaintext on a machine, rather are stored in AWS KMS.

Hi @jagpreetsinghsasan / @suvajit-sarkar, can you guys please provide more info in the description for this task?
Thanks.

Vault integration with AWS auto-unseal / KMS is implemented by following this tutorial https://learn.hashicorp.com/vault/operations/ops-autounseal-aws-kms#step-2-test-the-auto-unseal-feature.
Current Vault config file is as follows:
disable_cache = true
disable_mlock = true
ui = true
log_level = "Debug"

storage "file" {
    path = "${local.mount_point}"
}

listener "tcp" {
    address = "<IP_ADDRESS>:${var.vault_port}"
    tls_disable = 1
}

seal "awskms" {
    region = "${var.aws_region}"
    access_key = "${var.aws_access_key}"
    secret_key = "${var.aws_secret_key}"
    kms_key_id = "${aws_kms_key.vault.key_id}"
}

So now, if the Vault servers/instances are restarted, after running vault init, Vault will be automatically unsealed.

This has been implemented in the infrastructure code, no changes in the BAF code.


Failures when running with webpack 5.x which is used by Angular 13

using cyclonedx\webpack-plugin version 1.0.1 fails with angular cli 13 (which uses webpack 5.x)
[INFO] (node:23556) [DEP_WEBPACK_MODULE_ISSUER] DeprecationWarning: Module.issuer: Use new ModuleGraph API
[INFO] (Use `node --trace-deprecation ...` to show where the warning was created)
[INFO] Error: Module.issuerThere was no ModuleGraph assigned to the Module for backward-compat (Use the new API)
[INFO]     at C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\webpack\lib\ModuleGraph.js:814:12
[INFO]     at deprecated (internal/util.js:89:15)
[INFO]     at Function.getModuleGraphForModule (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\webpack\lib\ModuleGraph.js:824:10)
[INFO]     at NormalModule.get issuer [as issuer] (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\webpack\lib\Module.js:279:22)
[INFO]     at buildBom (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\@cyclonedx\webpack-plugin\src\webpack-plugin\bomGenerator.js:53:29)
[INFO]     at resolveComponents (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\@cyclonedx\webpack-plugin\src\webpack-plugin\bomGenerator.js:174:11)
[INFO]     at generateBom (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\@cyclonedx\webpack-plugin\src\bom\index.js:37:9)
[INFO]     at C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\@cyclonedx\webpack-plugin\src\webpack-plugin\index.js:72:26
[INFO]     at new Promise (<anonymous>)
[INFO]     at CycloneDxWebpackPlugin.emitBom (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\@cyclonedx\webpack-plugin\src\webpack-plugin\index.js:70:10)
[INFO]     at Hook.eval [as callAsync] (eval at create (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:27:17)
[INFO]     at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\tapable\lib\Hook.js:18:14)
[INFO]     at Compiler.emitAssets (C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\webpack\lib\Compiler.js:873:19)
[INFO]     at C:\dev\dev\co\platform-model-hub_intellij_1\platform-model-hub\model-hub-user-interface\node_modules\webpack\lib\Compiler.js:461:10
[INFO]     at processTicksAndRejections (internal/process/task_queues.js:75:11)

frist mitigation found: activate compat mode in webpack. Add the following to your webpack config
module.exports = {
  //...
  experiments: {
    backCompat: true,
  },
};

see https://webpack.js.org/configuration/experiments/#experimentsbackcompat

thanks for the report, @barclay-reg .
could cou create an example project and showcase the issue?
Maybe pullrequest that example as an integration test? see https://github.com/CycloneDX/cyclonedx-webpack-plugin/tree/master/tests/integration

was able to reproduce the issue.
see #55

Many thanks for the heads up :)


test alignment

Docs Build status updates of commit d0e90a1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/media/blank.png
:white_check_mark:Succeeded
View

articles/media/dot_net.png
:white_check_mark:Succeeded
View

articles/media/jupyter-wht.png
:white_check_mark:Succeeded
View

articles/media/jupyter.png
:white_check_mark:Succeeded
View

articles/media/python.png
:white_check_mark:Succeeded
View

articles/media/quantum-wht.png
:white_check_mark:Succeeded
View

articles/media/quantum.png
:white_check_mark:Succeeded
View

articles/media/vs_code.png
:white_check_mark:Succeeded
View

articles/media/vs_studio.png
:white_check_mark:Succeeded
View

articles/quickstarts/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 2d94da2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/media/blank.png
:white_check_mark:Succeeded
View

articles/media/dot_net.png
:white_check_mark:Succeeded
View

articles/media/jupyter-wht.png
:white_check_mark:Succeeded
View

articles/media/jupyter.png
:white_check_mark:Succeeded
View

articles/media/python.png
:white_check_mark:Succeeded
View

articles/media/quantum-wht.png
:white_check_mark:Succeeded
View

articles/media/quantum.png
:white_check_mark:Succeeded
View

articles/media/vs_code.png
:white_check_mark:Succeeded
View

articles/media/vs_studio.png
:white_check_mark:Succeeded
View

articles/quickstarts/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit abd4265:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/media/blank.png
:white_check_mark:Succeeded
View

articles/media/dot_net.png
:white_check_mark:Succeeded
View

articles/media/jupyter-wht.png
:white_check_mark:Succeeded
View

articles/media/jupyter.png
:white_check_mark:Succeeded
View

articles/media/python.png
:white_check_mark:Succeeded
View

articles/media/quantum-wht.png
:white_check_mark:Succeeded
View

articles/media/quantum.png
:white_check_mark:Succeeded
View

articles/media/vs_code.png
:white_check_mark:Succeeded
View

articles/media/vs_studio.png
:white_check_mark:Succeeded
View

articles/quickstarts/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 54a8d29:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/media/blank.png
:white_check_mark:Succeeded
View

articles/media/dot_net.png
:white_check_mark:Succeeded
View

articles/media/jupyter-wht.png
:white_check_mark:Succeeded
View

articles/media/jupyter.png
:white_check_mark:Succeeded
View

articles/media/python.png
:white_check_mark:Succeeded
View

articles/media/quantum-wht.png
:white_check_mark:Succeeded
View

articles/media/quantum.png
:white_check_mark:Succeeded
View

articles/media/vs_code.png
:white_check_mark:Succeeded
View

articles/media/vs_studio.png
:white_check_mark:Succeeded
View

articles/quickstarts/index.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 0d372b6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/media/blank.png
:white_check_mark:Succeeded
View

articles/media/dot_net.png
:white_check_mark:Succeeded
View

articles/media/jupyter-wht.png
:white_check_mark:Succeeded
View

articles/media/jupyter.png
:white_check_mark:Succeeded
View

articles/media/python.png
:white_check_mark:Succeeded
View

articles/media/quantum-wht.png
:white_check_mark:Succeeded
View

articles/media/quantum.png
:white_check_mark:Succeeded
View

articles/media/vs_code.png
:white_check_mark:Succeeded
View

articles/media/vs_studio.png
:white_check_mark:Succeeded
View

articles/quickstarts/index.md
:white_check_mark:Succeeded
View

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


shorted Screen (help)

Any body out there blow the Nextion  Display fuse can it be replaced. When i was putting it in wall must have pushed to hard everything works when i swapped the screen out.@ 20 bucks a pop would love to fix this one.

To my knowledge the LCD itself is not fused.  I'd try asking around at unofficialnextion.com.


Video generation does not create parent folder

Describe the bug
When selecting the output path as e.g. c:\recordings\ the video will fail to generate with the error 'Raw files not found.' this happens after CS2 closes after video generation supposedly has completed.
When browsing to 'Videos' the path is revealed to be e.g. c:\recordings\guid
Manually creating the folder and retrying (thank you for the retry feature!) the process works perfectly.
I did not have to manually create a folder with the same guid for the output path, so it is only a problem for the raw path which appears to be missing a step in generating folders.
Demo links
N/A
Steps to reproduce
Described above
Expected behavior
Described above
How often does this bug happen?
Every time
Log file
No response
Environment information
3.8.1
Additional context
No response

I can not explain this but I am no longer unable to reproduce, must have been my end. Closing


shellinit command not working reliably on Powershell

The check performed in https://github.com/boot2docker/boot2docker-cli/pull/356/files to see if the user is in a Windows terminal (cmd or Powershell) is return os.Getenv("TERM") != "".
Unfortunately, this is not a reliable way of checking the type of terminal and it actually clashes with Powershell modules like Posh-Git, which have following code:
function Enable-GitColors {
    $env:TERM = 'cygwin'
}

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).


Specifying a specific VS Code engine in package.json does not work on linux

testing #1881 on linux:
specifying a specific VS Code engine in package.json:
"engines": {
    "vscode": "0.10.3"
}

and running "npm install" does not work for me.
The vscode module does not change.

@weinand please attach the full output of running this command.

@bpasero

@weinand ;). I mean "npm install"

@weinand btw see my comment: https://github.com/Microsoft/vscode/issues/1881#issuecomment-175119597

@bpasero first line is "npm install"
Output: the two warnings.
Then I tried the node ... install thing

@weinand ok makes sense, the extension you have seems not the one from the @next generator,

@bpasero yes, the downloaded sample is definitively different.

@bpasero yeoman was not creating the correct project.


[BUG] isLatest not working properly

Describe the bug
Not correctly works properly isLatest in messaging-history.set. it appears in first call, but it supposed to be when whole history was processed.
To Reproduce
Steps to reproduce the behavior:

Created a new connection
listen for event messaging-history.set

Expected behavior
isLatest should be true only after all history was proceeded and we should have whole chats, contacts and messages

Not yet resolve.

whatsapp even returns false, but you can verify if syncType is FULL and progress 100%


Visual Studio and ORTools

Here a project compliant with both Visual Studio 2017 and 2019.
https://github.com/philippe3263/ORTools_Visual_Studio
Just update the header file directory for the compiler
and the libraries directory for the linker

Thanks!


[RFC] Decide officially supported/tested platform

This issue originates from this and this. Particularly the comment

Here is what I propose. We declare that Ubuntu and Fedora are the official dev environment we support. We will create automation for setting up the environment for these two OS. Eventually, we would even make CI a matrix strategy running both Ubuntu and Fedora.

Given that this would be a big commitment as well as a big decision as a project, opening this RFC for discussion.
Note that this was already once considered in https://github.com/containers/youki/issues/39 and in even more detail in https://github.com/containers/youki/issues/369.
@containers/youki-maintainers Please feel free to share your views and opinions on this :)

I consider the cost of managing these to be high. And I do not think there is any part of Linux distros that makes a difference.
I want to support architectures other than x86, but I don't realistically have a CI to run them.
Would anyone actually benefit from doing this tier? I fear these will be a strong drag on the maintainer. We do not want to strangle ourselves.

I agree with @utam0k that the cost to maintain many distro/targets can be high. The project is best served to focus one, at most two platforms/distros/targets and build youki to be rock solid. Today, the only implicit "official" support we declare is Ubuntu x86 and kernel version >= 5.3, since we run CI tests on this target. We also do provide instructions for fedora and family, but we don't actively test them in CI. I mention fedora here only because it is one of the easiest way to run kernel that is closer to the bleeding edge, and it is likely the 2nd most popular dev platform in the wild. At the same time, github CI doesn't support fedora last time I checked.
For all other platforms and architectures, I would default to "Not for Now".

Oh, and in addition to platform, we may also want to support musl as a build target. There are two usecases:

statically linked youki binary. (libseccomp and libdbus is a blocker)
projects using libcontainer such as aurae, whose maintainer implemented the first musl support for us.


Slim v4 support

Any plans to support the upcomming Slim v4?
I'm currently starting to build an app based on v3, but decided to switch to Slim v4 (http://slim-website.lgse.com/docs/v4/start/upgrade.html), so it might be a good opportunity to also help with the integration, I have not yet startet to investigate whether the changes in Slim v4 actually mean any changes to this middleware are needed.

@tuupola Mika, as stupid as the above question might seem (considering that both Slim v3 and Slim v4 are PSR-7 compatible), currently the middleware does not work with Slim v4 when used together with slim/psr7 (one of the HTTP providers).
See https://github.com/tuupola/http-factory/issues/9
I prepared an update that adds support for the package here:
https://github.com/tuupola/http-factory/pull/10
With the changes, Slim v4 runs with the middleware as expected.

Slim 4 will have PSR-15 support so this middleware should be supported too. Currently the problem is that  tuupola/http-factory does not yet autodetect the new slim/psr7. I believe your PR should fix this problem. Will check on it soon.

For Slim 4 support tuupola/http-factory:^1.1 must be used.

@tuupola on slim 4, when require tuupola/slim-jwt-auth it's install http-factory other version. You can see this here:

https://packagist.org/packages/tuupola/slim-jwt-auth

Can you update composer.json to require 1.1 ?

@gravataLonga
All versions of tuupola/slim-jwt-auth since version 3.1.1 can install http-factory version 1.1, since ^1.0.2 is forward-compatible with 1.1. Read more here: Semantic versioning
Observe the requirement on packagist (as per the link you sent abovce):
tuupola/http-factory: ^0.4.0|^1.0.2

You probably want to call composer update tuupola/*
or check why the specific version is blocked by running composer why tuupola/http-factory,
also check what version of the middleware you are running composer show tuupola/slim-jwt-auth, you need 3.1.1 or above.

Yeah, that is true, but got this issue when using with php-di:
Argument 2 passed to Tuupola\Middleware\JwtAuthentication::__invoke() must be an instance of Psr\Http\Message\ResponseInterface, instance of Slim\Routing\Route given

That's not really a problem of the middleware, is it?

@gravataLonga you are obviously doing something wrong. PHP-DI has nothing to do with it.
Here, let mi give you a tip. There are basically 3 possible cases how you add this (or any other) middleware to slim (both v3 and v4), to the whole app, to a certain group or to a single route:
$slim = new Slim\App(...);
$authOptions = [...];

// add to the whole app / middleware stack
$slim->add(new JwtAuthentication($authOptions));

$slim
    ->group('/foo', function ($group) use ($authOptions) {
        $group
            ->get('/bar', function (Request $request, Response $response) {
                echo 'The end. 42';
            })
            // add to the single route
            ->add(new JwtAuthentication($authOptions));
    })
    // add to the whole group
    ->add(new JwtAuthentication($authOptions));

I'm obviously  not doing something wrong, if you get class from container it will work. Take this example:
This not work:
$app = new App();
// ... some code boot, container, php-di, etc.
        $app->get('/jwt', function (Request $request, Response $response) {
            return $response->json($request->getAttribute('token'));
        })->add(JwtAuthentication::class);

This will work:
$app = new App();
// ... some code boot, container, php-di, etc.
        $app->get('/jwt', function (Request $request, Response $response) {
            return $response->json($request->getAttribute('token'));
        })->add($container->get(JwtAuthentication::class));

And again, it's not a problem of this middleware.
First, check the calalble resolver you are using, this is most problably your misconfiguration issue.
If you still think that it is a bug, I suggest you file an issue with either Slim or PHP-DI.

I'm don't think that is a bug of this middleware, only point out that the problemis another than "i'm don't known what are doing". Will try to debugging.. and yes, i'm think the problem is php-di. ;)

@dakujem only for reference...

https://github.com/PHP-DI/Slim-Bridge/issues/51


Issue 344 compare lead acid

Description
Edit QuickPlot to be more flexible, and add scripts and notebooks for comparing models.
Fixes #344
Type of change

[x] New feature (non-breaking change which adds functionality)

Key checklist:

[x] No style issues: $ flake8
[x] All tests pass: $ python run-tests.py --unit
[x] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works
[ ] Any dependent changes have been merged and published in downstream modules

Ok, will remove those.
"Typical current density" was a bug, should have been "Typical current" from the start. (current is in [Amps] and current density is in [A m-2])
We might want to add explicit units to parameters (with the [unit] notation) to make these things clearer

We might want to add explicit units to parameters (with the [unit] notation) to make these things clearer

I am for this as it makes inputs consistent with outputs

This is also failing for the 10^(-5) need to increase to 10^(-4)...


Feature request: Support debug layer for DirectX 11

Motivation
Hey. I would like to see all DirectX debug messages when using windows crate. I have supplied D3D11_CREATE_DEVICE_DEBUG flag and I do not see debug messages.
In C++ I can see debug layer messages in Visual Studio's Output window or in VSCode's Debug Console window, but with windows-rs in VSCode's Debug Console window I do not see anything.
In stdout I see only basic info such as:
The parameter is incorrect. (0x80070057)
It is very hard to find the cause of the exception without additional debug info.
Drawbacks
No response
Rationale and alternatives
It is almost impossible to find the cause of exception without debug layer.
Additional context
No response

It's working for me in the displayrecorder project. I validated it by arbitrarily making one of the textures smaller than another and calling CopyResource. I got this in the VS Code debug output:
D3D11 ERROR: ID3D11DeviceContext::CopyResource: Cannot invoke CopyResource when the source and destination are not the same Resource type, nor have equivalent dimensions. Src has the following dimensions: Width (2560), Height (1440), Depth (1), MipLevels (1), and ArraySize (1). Dst has the following dimensions: Width (2543), Height (1440), Depth (1), MipLevels (1), and ArraySize (1).  [ RESOURCE_MANIPULATION ERROR #284: COPYRESOURCE_INVALIDSOURCE]

Are you sure you've attached the debugger?

Hey. Yep, I am pretty sure that I have attached the debugger. I use CodeLLDB to debug. I think that after you have pointed out that debugging is working for you, I should try to use Microsoft's C++ extensions, because it looks like VSCode on Windows does not support debugging.

Indeed, if I switch from CodeLLDB to Microsoft's C/C++ extension I can see debug layer messages.
It would be nice if this info would be added somewhere and highlighted.


fix: Remove frameworkreference

GitHub Issue (If applicable): #489
PR Type
What kind of change does this PR introduce?

Bugfix

What is the current behavior?
Required frameworkreference in winui app when added
What is the new behavior?
Frameworkreference not required
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tested code with current supported SDKs
[ ] Docs have been added/updated which fit documentation template. (for bug fixes / features)
[ ] Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
[ ] Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
[ ] Contains NO breaking changes
[ ] Updated the Release Notes
[ ] Associated with an issue (GitHub or internal)

Other information

Internal Issue (If applicable):

I believe @jeromelaban just added these lines back from here.
@jeromelaban is this needed?

I added those to get the CI running when downgrading to .NET 6. If the CI passes, I don't see any issue.