hwloc: 1.11.9 -> 1.11.10

Motivation for this change
Version bump
CC @fpletz
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg  build hwloc

Success on x86_64-linux (full log)
Attempted: hwloc
Partial log (click to expand)
checking for references to /build in /nix/store/x6160j297gv5m79vzlvdvhqh54506mpy-hwloc-1.11.10-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/6272sfxsvxh1kvbjwrxx13949zh69q18-hwloc-1.11.10-doc
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/6272sfxsvxh1kvbjwrxx13949zh69q18-hwloc-1.11.10-doc
checking for references to /build in /nix/store/6272sfxsvxh1kvbjwrxx13949zh69q18-hwloc-1.11.10-doc...
shrinking RPATHs of ELF executables and libraries in /nix/store/z3fk3y38wps2f906yslrf0p6ny9lpy2s-hwloc-1.11.10-man
gzipping man pages under /nix/store/z3fk3y38wps2f906yslrf0p6ny9lpy2s-hwloc-1.11.10-man/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/z3fk3y38wps2f906yslrf0p6ny9lpy2s-hwloc-1.11.10-man
checking for references to /build in /nix/store/z3fk3y38wps2f906yslrf0p6ny9lpy2s-hwloc-1.11.10-man...

Success on x86_64-darwin (full log)
Attempted: hwloc
Partial log (click to expand)
patching script interpreter paths in /nix/store/n0nhzsklxibrf5bman89yxld2a2ccv57-hwloc-1.11.10-lib
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/l3h7qrzmc76px8yi3a1g1vl59mifrms8-hwloc-1.11.10-dev/lib
patching script interpreter paths in /nix/store/l3h7qrzmc76px8yi3a1g1vl59mifrms8-hwloc-1.11.10-dev
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/lyzwsg04ryn2wf9f5xr8ibmjhmzi4xqw-hwloc-1.11.10-doc
gzipping man pages under /nix/store/dl00rh7wadsh4il825aj89b3jzfpzmd5-hwloc-1.11.10-man/share/man/
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/dl00rh7wadsh4il825aj89b3jzfpzmd5-hwloc-1.11.10-man
/nix/store/3mp6rywhv8xblbz1wzlh8lj9fcp5rvbn-hwloc-1.11.10

Success on aarch64-linux (full log)
Attempted: hwloc
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/89x5lckx87szpjhsq8q48dli145hvi15-hwloc-1.11.10-doc
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/89x5lckx87szpjhsq8q48dli145hvi15-hwloc-1.11.10-doc
checking for references to /build in /nix/store/89x5lckx87szpjhsq8q48dli145hvi15-hwloc-1.11.10-doc...
shrinking RPATHs of ELF executables and libraries in /nix/store/xsayr8sfvxpbvgkcav49qxp2qsf2pvmp-hwloc-1.11.10-man
gzipping man pages under /nix/store/xsayr8sfvxpbvgkcav49qxp2qsf2pvmp-hwloc-1.11.10-man/share/man/
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/xsayr8sfvxpbvgkcav49qxp2qsf2pvmp-hwloc-1.11.10-man
checking for references to /build in /nix/store/xsayr8sfvxpbvgkcav49qxp2qsf2pvmp-hwloc-1.11.10-man...
/nix/store/8i4n643zynfjn8fgh9wswk2nkh81z2mm-hwloc-1.11.10


UV and normal parameters in "add_mesh" swapped

Similar to #4, the binding says that the last two parameters are "uvs" and "normals":
https://github.com/mworchel/xatlas-python/blob/752d97089a57e91bdbfbbda5a90ed8fa14f8b772/src/atlas.cpp#L264
but Atlas::addMesh actually takes "normals" and then "uvs":
https://github.com/mworchel/xatlas-python/blob/752d97089a57e91bdbfbbda5a90ed8fa14f8b772/src/atlas.cpp#L45-L48

Thanks for reporting. The issue is fixed in version 0.0.8.

Thanks for the fix!


[Feature Request] Make Zmodel color schema looks cool and consistent

Currently, in some color themes, the Zmodel schema looks 'empty' and quite different with prisma and the ts file:

@jiashengguo do we know if this is going to be released?

@Jonatthu  Sorry for the late response. I think it would be included in the v1.1 release within this month.

I'm also looking forward to this. Replacing the schema.prisma with schema.zmodel file creates the expectation to the users that they would interact with it the same way.
Keep up the great work!


Tidy UI Error when filtering

When filtering module settings with the Tidy UI module the Sync buttons change to have the description text of the owning setting.

When filtering by module title there is no error.

When filtering by setting the error appears for sync buttons under existing settings, but not for sync buttons added at a whole module level.

The error does not occur except when Tidy UI is installed. MODULE LINK

Hi,
I've seen this error myself, but honestly I'm not sure what causes it or how to fix it. My guess is that tidy UI is doing something strange when filtering.
In short, I don't think it's worth the time and effort to hack together a fix for this.

I can't reproduce this error. And honestly I can't explain what would cause this. I'm not doing anything fancy here, just hiding complete sections by its title. But I'm a bit confused regarding the screenshot. Looks like there are two search fields?
That's how it "should" tm look like - I chose the provided example to conform it is working (for me)

Looking at it now there seems to be a few other modules at work with the colored borders and icons. I suspect there is more at work here if the error still exists.

Had a closer look, the incompatibility is between "DF Settings Clarity" and "Socket Settings"


Positioning of objects from Tile

In layer/objectlayer.lua, lines 396 to 402 are
-- Tile image
elseif o.gid then
  data.type = "image"
  data.transfer._objType = "image"
  data.tileData = tileIndex[o.gid]
  data.transfer.x, data.transfer.y = o.x + mapData.stats.tileWidth * 0.5, o.y - mapData.stats.tileHeight * 0.5
  data.width, data.height = tileWidth, tileHeight

I find that the following code works where the image object is not the same dimensions as the tiles in the tiles
-- Tile image
elseif o.gid then
  data.type = "image"
  data.transfer._objType = "image"
  data.tileData = tileIndex[o.gid]
  data.transfer.x, data.transfer.y = o.x + o.width * 0.5, o.y - o.height * 0.5
  data.width, data.height = o.width, o.height

Here the object x,y, widths and heights are based on the object image properties rather than assuming they conform to the tileset which is used in the tiles layer.

This is part of v1.0.


New Provisioning Example for Distributed Execution Using IaC - Terraform/AWS/EC2

The proposal is to offer an uncomplicated example of distributed load execution.
With just a few steps we have Locust provisioned and distributed in the number of nodes provided, running in the aws cloud under ec2.
1. AWS Authentication
export AWS_ACCESS_KEY_ID=AIAXXXXXXXXXXXXXXXXX
export AWS_SECRET_ACCESS_KEY=T9HyXXXXXXXXXXXXXXXXXXXXXXXXXXXX

2. Configure your provisioning

Don't forget to provide the correct subnet name in the variable file
Define location and file of your locust plan script
Define the number of nodes to create

variables.tf
variable "node_size" {
    description = "Size of total nodes"
    default = 2
}

variable "loadtest_dir_source" {
    default = "plan/"
}

variable "locust_plan_filename" {
    default = "basic.py"
}

variable "subnet_name" {
    default = "subnet-prd-a"
    description = "Subnet name"
}

3. Execute Terraform
cd examples/distribuited_execution_terraform/aws
terraform init
terraform apply --auto-approve

4. Access UI
Click on the link below to access the UI:
Result exemple:
Apply complete! Resources: 14 added, 0 changed, 0 destroyed.

Outputs:

dashboard_url = "http://<IP_ADDRESS>"
leader_private_ip = "<IP_ADDRESS>"
leader_public_ip = "<IP_ADDRESS>"
nodes_private_ip = [
  "<IP_ADDRESS>",
  "<IP_ADDRESS>",
]
nodes_public_ip = [
  "<IP_ADDRESS>",
  "<IP_ADDRESS>",
]

5. Cleanup
terraform destroy --auto-approve

6. More information

Terraform aws-get-started >> install-terraform-on-linux

Terraform module aws loadtest distribuited

Cool stuff!

Black-ify the code (that's why the build is failing)
Link it from the documentation somewhere to make sure people can find it! Put it as a new paragraph in "Running in docker" (we should probably rename that page to something like "Cloud integration" or something, but I can do that later if you cant be bothered to figure out how to do it :)
distribuited_execution_terraform <- typo in the directory name :)

Perhaps you could also show how locust settings can be set? (locust supports environment vars, command line and .conf-file, whatever is easiest, but you dont have to support all of them)

Thanks @cyberw , I will do what you said and updates PR.

Hi @cyberw , I made the first considerations you pointed out.
Could you please validate if it is as expected?
Tks.
Obs: I'll prepare an example covering the other ways to configure locust and I promise to send it in the next PR.

The docs ended up a little weird. Can you take a look? https://docs.locust.io/en/latest/running-cloud-integration.html

Perhaps it is better to make the documentation shorter and just link to the markdown file?

(the documentation could state what what it is useful for and give a brief description, but the details are a little too verbose to have in the docs)


Class and Style Bindings: Minor grammar and rewording updates

Removed a few unnecessary instances of "also" (lines 21 and 100)
Change a colon to a semicolon (line 7)
Replace a space-hyphen-space with a proper em dash (line 156)
Add a note about kebab-case close to where it's first used

Any news on this small change?

@sdras can you make the small change? If not I'll do it and you can approve it.


A few port matching Host header bugs

This is primarily documentation for the bugs fixed in a PR.
There are two sets of issues:

Wildcard domains: we cannot match *.com:*, so we make the port explicit (*.com:80). If a user users an unexpected port for the Host, we will not match. We only put one port

More complex -- we have two route configs. One has wildcard and one doesn't:

- domains: [*.example.com:443] # match wildcard
- domains: [foo.example.com, foo.example.com:*] # match concrete

If a user sends foo.example.com:443 it would match the first one; we want the latter.

https://github.com/envoyproxy/envoy/issues/22664 will be the fix


Typo fixes in MS Edge documentation

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: BenMcGarry sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/dev-guide/css/filter-effects.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/device/fullscreen-api.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/device/screen-orientation-api.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/graphics/svg.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/html5/audio.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/html5/video.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/html5/video/timed-text-tracks.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/multimedia/media-source-extensions.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/multimedia/web-speech-api.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/performance/xmlhttprequest.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/security.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/security/hsts.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/storage/indexeddb/how-to-create-a-tag-cloud-using-indexeddb.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/storage/web-and-offline-storage.md
:white_check_mark:Succeeded

microsoft-edge/dev-guide/tools/console-logging-api.md
:white_check_mark:Succeeded

microsoft-edge/extensions/guides/packaging/creating-and-testing-extension-packages.md
:white_check_mark:Succeeded

microsoft-edge/extensions/tips-and-tricks.md
:white_check_mark:Succeeded

microsoft-edge/f12-devtools-guide/elements.md
:white_check_mark:Succeeded

microsoft-edge/f12-devtools-guide/elements/accessibility.md
:white_check_mark:Succeeded

microsoft-edge/f12-devtools-guide/emulation.md
:white_check_mark:Succeeded

microsoft-edge/f12-devtools-guide/memory.md
:white_check_mark:Succeeded

microsoft-edge/f12-devtools-guide/performance.md
: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.

Thanks for your help @BenMcGarry! These edits will come in handy as we port web standards conceptual content over to our new home on MDN web docs.


ServiceBus : Swagger Split and Added PrivateEndPointConnection API

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[X] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

@v-Ajnava, could you please fix all the errors from tool check?

In case there is no new API been added ARM API review is not required.

Refers to: specification/servicebus/resource-manager/Microsoft.ServiceBus/stable/2017-04-01/servicebus.json:2 in 792f037. [](commit_id = 792f037ddde8fc1b5280affc307c0306ebd70c00, deletion_comment = True)

/azp run automation - sdk

@lirenhe , can you please review the PR


[Log] Wire server_log handler

This is the last part of the new server:log command.
Maybe a release of the monolog bundle could be better to avoid to require a dev package.
ping @Seldaek
WDYT?

monologbundle 3.1.0 is out

I rebased the PR. Now it required the new symfony/monolog-bundle package.

Thank you @lyrixx.


add gps fence

gps click me

developer.android.com

https://github.com/googlesamples/android-play-location/tree/master/BasicLocationSample/app/src/main

add option to select location

@sirprice could use some help with this part, i have no idea how that part of the code works


As a non-technical reviewer, I would like a tool to review an OSCAL document in a pretty format.

Issue description / feature objectives
This may be too far outside the scope of the trestle project, however, in an ideal world review UI could pop up from a PR in a fashion similar to how codecov.io does for code coverage.
Future thought - but to record it down here.

Markdown functionality covers this.


Gracefully reload maxmind DB

Hi,
Is there any possibility of gracefully reload Maxmind db after db upgrade?
Can libvmod-geoip2 re-read db file from time to time?
Thanks.

Please see https://github.com/fgsch/libvmod-geoip2#db-updates.

Thanks.


Copy pasting of the campfire code causes incompatibility with mods that change campfires

Like the title of the issue mentions, copy and pasting the code from the campfires causes incompatibility with mods that change campfire beheaviour, like fabrication. Simply extending the class and only adding the new functions you need it to have and getting rid of the excess code would fix this issue, I think.

fixed in 1.19.4 > release


User should be able to change his own data.

Updating and deleting user data should be added to the user features instead of only being in admin.

Completed in other issues


Fixing empty links

In GitHub markdown a link of the form [.*]() will just link back to the current page.  The intended usage of the links were to to go to themselves, which GitHub does for you when a URL appears in normal Markdown text.

I signed it!

LGTM!  Merging


dns/ddclient - Service not listed on dashboard

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I'm convinced that mine is new.
[x] The title contains the plugin to which this issue belongs
Describe the bug
The ddclient service is not listed on the dashboard nor on System->Diagnostics->Services

I have read, that you need to uninstall os-dyndns first, and then it shows up in services with exactly the same name as os-dyndns.
But I am too scared to lose my settings to verify that.
Maybe we could change the service name of either one of them to get around that issue?
Like os-dyndns could be "Dynamic DNS legacy"

uninstall doesn't remove settings and then there's always a history saved in System: Configuration: History as well. https://github.com/opnsense/plugins/commit/400110af010e8a2cd3ea0f01d4b3db87154bacb6 closes this issue (move the old one to a separate location)


adding Indiana medicare exclusions crawler

the file says this shouldn't be used as an exclusion list. Just confirming with them what that means and whether we can use it as planned.

800-457-4515 option 8 https://www.in.gov/medicaid/providers/files/quick-reference.pdf

let's add these without the debarment topic, and with target=False
for that to work, also add
exports:
  - statistics.json
  - entities.delta.json
  - entities.ftm.json
  - names.txt
  - senzing.json

to the metadata so that we exclude targets.nested.json, which will be empty.


Clean up github issues

We should go through all our open issues and somehow organize them so future developers know where we left off.

cleaned


Static file serving slowness

We've noticed on and off static files serving slowness.
Root cause is still TBD. Might be due to Google shared disk performance degrading over high load?
A cheap mitigation could be to move Brave to CDN serving since that is likely the store that causes high load.

Has this shown up again or is this just to track the issue?
Will see about moving the one store to the CDN.  Would alleviate some load from the backend nodes.
I also want to take a couple of days in the near future to migrate to a new dshop-only cluster.  It'll reduce technical debt by being tied up with the old marketplace, bring in likely thousands of bugfixes, and give us better opportunities for troubleshooting.  Probably the only way we're going to see the long-term hands-off stability we're looking for.

Has this shown up again or is this just to track the issue?
Will see about moving the one store to the CDN.  Would alleviate some load from the backend nodes.
I also want to take a couple of days in the near future to migrate to a new dshop-only cluster.  It'll reduce technical debt by being tied up with the old marketplace, bring in likely thousands of bugfixes, and give us better opportunities for troubleshooting.  Probably the only way we're going to see the long-term hands-off stability we're looking for.

There hasn't been any recent slowness report that I know of... All the known reports you have handled :)
Agreed moving the big store that starts with a B to CD makes sense.
Also agreed that if moving to a new dedicated shiny kube cluster is only a couple days of work, then it is probably an investment that will pay off by bringing more stability to the system. Can you think a it more about the detailed scope of the work and then we can finalize the decision?

There hasn't been any recent slowness report that I know of... All the known reports you have handled :)
Agreed moving the big store that starts with a B to CD makes sense.
Also agreed that if moving to a new dedicated shiny kube cluster is only a couple days of work, then it is probably an investment that will pay off by bringing more stability to the system. Can you think a it more about the detailed scope of the work and then we can finalize the decision?

A lot of the scope is "figure it out as I go along" but generally:

Make sure there haven't been any revolutionary new kubernetes services added to GCP that might replace GKE if not...
Stand up a new relatively small GKE cluster.  Large enough to leave some room to wiggle but not break the wallet.
Create necessary helm charts in dshop repo, mostly based off existing ones.  Should generally just be moving and making small tweaks for the new cluster or to cleanup unnecessary leftovers from previous configuration.  Not reinventing the wheel here.
Apply charts to new cluster
Test its working.  If not, tweak and GOTO 3
Migrate DNS records to move traffic to the new cluster

Shouldn't be any need to transfer data or anything like that.  Will probably take a day or so, but I quoted 2 in proper engineering fashion of dealing with the unknown unknowns.  And should it be necessary, we could revert to the old cluster.

A lot of the scope is "figure it out as I go along" but generally:

Make sure there haven't been any revolutionary new kubernetes services added to GCP that might replace GKE if not...
Stand up a new relatively small GKE cluster.  Large enough to leave some room to wiggle but not break the wallet.
Create necessary helm charts in dshop repo, mostly based off existing ones.  Should generally just be moving and making small tweaks for the new cluster or to cleanup unnecessary leftovers from previous configuration.  Not reinventing the wheel here.
Apply charts to new cluster
Test its working.  If not, tweak and GOTO 3
Migrate DNS records to move traffic to the new cluster

Shouldn't be any need to transfer data or anything like that.  Will probably take a day or so, but I quoted 2 in proper engineering fashion of dealing with the unknown unknowns.  And should it be necessary, we could revert to the old cluster.

Thanks. I think it's worth standing up a new cluster.
As a bonus, I'd encourage us to document the setup steps and make the config self-contained so that anyone from the community can easily bring up their own kubernetes dshop backend.

Thanks. I think it's worth standing up a new cluster.
As a bonus, I'd encourage us to document the setup steps and make the config self-contained so that anyone from the community can easily bring up their own kubernetes dshop backend.

New cluster deployed.  Want to migrate our largest shop to a CDN ahead of time just to minimize the likelyhood of double-downtime.  The new cluster is up and running, sans queue workers to prevent collisions.  Migrating should be as simple as updating DNS record for dshop.originprotocol.com to point at the new IP.
There's one gotcha we will need to take care of.  In some custom domain cases (root domains) we did instruct users to use an IP address for an A record.  This IP would be for the IP of the old issuer.  Immediately after the migration, the old cluster will continue to serve their shop from this IP.  Before shutting down the old dshop cluster, we should move the IP to a new Kubernetes LoadBalancer pointed at the issuer on the new cluster.  This should be relatively trivial, but may result in a few minutes of downtime for these users.  Just don't want to forget this, so documenting here.

The previously mentioned shop has been moved over to the CDN.  Clear to migrate the dshop cluster whenever.  I expect the migration to be smooth, but it's not a high priority so I may drag my feet on it a little.


Rename module refactoring for Python not working anymore

Type: Bug
The "Rename Module" refactoring as explained here does not work anymore. It used to work very nicely, prompting the message if I want to do the refactorings, but this message does not appear anymore when I rename or move a file in my Python package. I did not change any settings as far as I know. Are there known problems with Extensions that might block this function?
Would be great to get suggestions on how I might solve this and get it working again. Thanks a lot in advance!

The fix was also included in our latest prerelease build 2023.11.11, so switching to the prerelease version is another viable workaround.

Thanks a lot, this worked! :)

hm I think the fix doesn't work for Ubuntu:
Version: 1.84.1
Commit: 2b35e1e6d88f1ce073683991d1eff5284a32690f
Date: 2023-11-06T12:35:31.181Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.2.0-36-generic

the prompt and refactor don't happen for either renaming of files or folders. I have the same VSCode version as @jwrth, and have tried both Pylance pre-release build 2023.11.11 and 2023.11.12. Referencing #4964 I tried pre-release version 2023.10.31, and it refactors files but not folders.
The fix does work on Windows:
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

when renaming both file and folder, the refactor prompt appeared, changes to other files could be previewed and applied.
Should I be expecting different behaviour on Linux?

@tirameshu, could you please open a new issue for what you are describing above? with repro steps included?
thanks

@tirameshu just to make sure I understand. it works for file but not folder? but with exact same set up, both works for windows, but not for linux? as judej said, it would be nice if we can get exact repro step to see why that is happening.
by the way, I assume you have __init__ file for the folder you are renaming.

Ah thanks, __init__.py is needed for folder renaming to work on both Windows and Linux. Does Pylance renaming of folders not work for implicit namespace packages? Sorry if I missed the documentation!
Should I still open a new issue for this discussion?


v2.0.0

Advancement to 1.2.0 due to new modules and rework of existing Filetree management

due to extent of breaking changes, version will be advanced to 2.0.0

v2.0.0 locked. ready for review


Incompatibility: Optimization: Meats - C# edition

Description
Looks like this mod raises an error when loaded with typhon.

Hey just wanted to let you know that I believe the mod Optimization: Meats - C# edition removes the typhon organ and causes errors when used with this mod. I reported it there too.

Probably due to the fact that all typhon creatures are using a custom meat def and flesh type. It'll require some digging into.
Looks like the mod is open source, so I can dig around in there to figure out where the error is happening.

Fixed in the Meat Optimization mod, though it likely won't be updated for a while due to the author being in the military.


#haq-gest | Dataset pages - headings not editable as content doesn't show up on strapi

Gave the super admin access, so this is fixed


Drawer Refactor

For PXBLUE-1808.
Fixes #221
Fixes #139
Ladies and gentlemen, here it is...the long awaited and highly-anticipated refactor or the drawer component!
I did some testing on this to make sure things still work as expected, but would like some eyes to give it a deep and thorough run through to make sure I didn't miss anything.

Changes proposed in this Pull Request:

Refactor the drawer sub components to be able to render as standalone items

Each item appearance is determined completely deterministically from its props

Shared/Inherited prop types were cleaned up and separated to accommodate rail items and nav items
Added common items to the drawer context (activeItem, etc.) to avoid having to pass them through the hierarchy as props.
Cleaned up all of the style/class overrides and make sure we are applying them and exposing them correctly
Moved the nesting logic into the DrawerNavItem instead of the DrawerNavGroup

If you so choose, you can now build a drawer by passing in children instead of using the items array (or you can even mix and match if you want), e.g.:
<Drawer>
    <DrawerHeader />
    <DrawerBody>
        <DrawerNavGroup>
            <DrawerNavItem>
                <DrawerNavItem>
                    <DrawerNavItem/>
                </DrawerNavItem>
            <DrawerNavItem>
            <DrawerNavItem/>
        </DrawerNavGroup>
    </DrawerBody>
    <DrawerFooter />
</Drawer>

The drawer should continue to look and function exactly as it did before (maybe slightly better) — visually you shouldn't see any difference.

Love the new structure! I will take a look at this on Monday or Tuesday

Love the new structure! I will take a look at this on Monday or Tuesday

I'm taking a look right now; one thing I noticed was that the full config drawer story has a duplicate divider in the DrawerFooter.  Could you remove it so we only use the prop?

I'm taking a look right now; one thing I noticed was that the full config drawer story has a duplicate divider in the DrawerFooter.  Could you remove it so we only use the prop?

I'm taking a look right now; one thing I noticed was that the full config drawer story has a duplicate divider in the DrawerFooter. Could you remove it so we only use the divider prop?

Consider it removed. I'll just sit on pushing it to see if there are other change requests I can bundle with it.

I'm taking a look right now; one thing I noticed was that the full config drawer story has a duplicate divider in the DrawerFooter. Could you remove it so we only use the divider prop?

Consider it removed. I'll just sit on pushing it to see if there are other change requests I can bundle with it.

DrawerBody line 40 you can remove the eslint comment.
// eslint-disable-line @typescript-eslint/no-unused-vars

DrawerBody line 40 you can remove the eslint comment.
// eslint-disable-line @typescript-eslint/no-unused-vars

Nice mergeStyleProp function, this is looking a lot cleaner.

Nice mergeStyleProp function, this is looking a lot cleaner.

Nice mergeStyleProp function, this is looking a lot cleaner.

Pretty sure I stole this from what you did for RN 😆
I wanted to make it even more powerful (less repetitive) by letting you pass in an array of props to merge so we could do the merge in a single line, but it got kinda hairy so I left it the way it is for now.

Nice mergeStyleProp function, this is looking a lot cleaner.

Pretty sure I stole this from what you did for RN 😆
I wanted to make it even more powerful (less repetitive) by letting you pass in an array of props to merge so we could do the merge in a single line, but it got kinda hairy so I left it the way it is for now.

DrawerBody line 40 you can remove the eslint comment.
// eslint-disable-line @typescript-eslint/no-unused-vars

Same applies to line 117 of DrawerNavGroup
 // eslint-disable-line @typescript-eslint/no-unused-vars

DrawerBody line 40 you can remove the eslint comment.
// eslint-disable-line @typescript-eslint/no-unused-vars

Same applies to line 117 of DrawerNavGroup
 // eslint-disable-line @typescript-eslint/no-unused-vars

DrawerNavItem line 501 and 460 @ts-ignore can be removed as well; seems line 481 still gives issues.

DrawerNavItem line 501 and 460 @ts-ignore can be removed as well; seems line 481 still gives issues.

I really like this refactor; I think this makes more sense than before, it's more flexible for users.  Only stuff I noticed was some lint comments and @ts-ignore comments that were probably outdated.

I really like this refactor; I think this makes more sense than before, it's more flexible for users.  Only stuff I noticed was some lint comments and @ts-ignore comments that were probably outdated.

Is it possible to make the title of DrawerRailItem optional and have it default to an empty string?

Is it possible to make the title of DrawerRailItem optional and have it default to an empty string?

Nested divider is on when the knob turns it off
http://localhost:6006/?path=/story/components-drawer--with-nested-list-items

Nested divider is on when the knob turns it off
http://localhost:6006/?path=/story/components-drawer--with-nested-list-items

Nav Rail, check the condensed knob

http://localhost:6006/?path=/story/components-drawer--with-different-variants

Nav Rail, check the condensed knob

http://localhost:6006/?path=/story/components-drawer--with-different-variants

Can we rename Accordions so that the console won't scream out red texts?

http://localhost:6006/?path=/story/components-drawer--with-subheader

Can we rename Accordions so that the console won't scream out red texts?

http://localhost:6006/?path=/story/components-drawer--with-subheader

It looks like when nestedBackgroundColor is set, the activeItemBackgroundColor is gone. I expect the activeItemBackgroundColor to be an overlay on top of the nestedBackgroundColor

http://localhost:6006/?path=/story/components-drawer--with-nested-list-items

It looks like when nestedBackgroundColor is set, the activeItemBackgroundColor is gone. I expect the activeItemBackgroundColor to be an overlay on top of the nestedBackgroundColor

http://localhost:6006/?path=/story/components-drawer--with-nested-list-items

Same for the regular backgroundColor

Same for the regular backgroundColor

Full config story, can we add a "(persistent only)" to the knob name "openOnHover"?

Full config story, can we add a "(persistent only)" to the knob name "openOnHover"?

I added classes={{ root: 'root-test' }} to line 319 of react-component-library/demos/storybook/stories/drawer/with-full-config.tsx, and two classes show up

I added classes={{ root: 'root-test' }} to line 319 of react-component-library/demos/storybook/stories/drawer/with-full-config.tsx, and two classes show up

RTL indentation on depth 2 items

http://localhost:6006/?path=/story/components-drawer--with-nested-list-items

RTL indentation on depth 2 items

http://localhost:6006/?path=/story/components-drawer--with-nested-list-items

Design and code otherwise look fine... my TODO: read README

Design and code otherwise look fine... my TODO: read README

Really like how you handle the prop inheritance

Really like how you handle the prop inheritance

Is it possible to make the title of DrawerRailItem optional and have it default to an empty string?

We talked about this on the original drawer rail story. I'm inclined to leave it for now (we don't want people to use a regular rail without labels do we?). We're using it for the tooltips on the condensed style as well.

Is it possible to make the title of DrawerRailItem optional and have it default to an empty string?

We talked about this on the original drawer rail story. I'm inclined to leave it for now (we don't want people to use a regular rail without labels do we?). We're using it for the tooltips on the condensed style as well.

we don't want people to use a regular rail without labels do we?

I personally think this falls into that "technically possible but we don't encourage you to do so from the design perspective"

we don't want people to use a regular rail without labels do we?

I personally think this falls into that "technically possible but we don't encourage you to do so from the design perspective"

It looks like when nestedBackgroundColor is set, the activeItemBackgroundColor is gone. I expect the activeItemBackgroundColor to be an overlay on top of the nestedBackgroundColor

It's there...it's blue[500] at 5% opacity on black so it's nearly impossible to see.

It looks like when nestedBackgroundColor is set, the activeItemBackgroundColor is gone. I expect the activeItemBackgroundColor to be an overlay on top of the nestedBackgroundColor

It's there...it's blue[500] at 5% opacity on black so it's nearly impossible to see.

I added classes={{ root: 'root-test' }} to line 319 of react-component-library/demos/storybook/stories/drawer/with-full-config.tsx, and two classes show up

There is a separate bug logged for the duplicate classes: #216

I added classes={{ root: 'root-test' }} to line 319 of react-component-library/demos/storybook/stories/drawer/with-full-config.tsx, and two classes show up

There is a separate bug logged for the duplicate classes: #216

RTL indentation on depth 2 items

This is currently broken in dev (i.e. not related to the refactor). We may want a separate issue for this if I can't find a quick fix for it.

RTL indentation on depth 2 items

This is currently broken in dev (i.e. not related to the refactor). We may want a separate issue for this if I can't find a quick fix for it.

Write unit tests for the declarative styled components

Write unit tests for the declarative styled components

@huayunh I think I covered all of your comments. If not let me know.

@huayunh I think I covered all of your comments. If not let me know.

Since it is only for the drawer and no other components, I must say I strongly dislike the idea of moving the selected logic into ILI. It just gets creepy when you can do a "rounded" highlight shape in a list item.
I would still prefer a

    <activeHighlight style={{backgroundColor: props.activeItemBackgroundColor}} />
    <InfoListItem />

structure

Since it is only for the drawer and no other components, I must say I strongly dislike the idea of moving the selected logic into ILI. It just gets creepy when you can do a "rounded" highlight shape in a list item.
I would still prefer a

    <activeHighlight style={{backgroundColor: props.activeItemBackgroundColor}} />
    <InfoListItem />

structure


Analyzer: Parsing trailing comma in assert in initializer list fails

The following program causes dartanalyzer (version 2.0.0-dev.6.0) to stop with a syntax error:
class C {
  C() : assert(true,);
}

and so does this one:
class C {
  const C.n2() : assert(true, "Message",);
}

Presumably, trailing commas in assert in an initializer list has not yet been implemented.

see also #29959, #30039

Thanks for noticing these very similar issues!
#30039 is an area-language issue which was closed with 'The behavior is currently correct' before it was decided to add trailing comma support to assert.
#29959 is similar to this one, mentions that the feature is now part of the language and the spec has been updated. It has 'area-language' as well, but it also includes references to two committed CLs where the analyzer is modified to support trailing commas in asserts (563720617c9a25dba653a2eddeebe42000556789, f93da679a12d93c45048fbb0f2e8c654eaec42d7).
However, the analyzer still doesn't handle trailing commas in asserts in initializer lists, hence this issue.

https://dart-review.googlesource.com/c/sdk/+/29520


Getting Trending is freezing

Any body can help ? in my local environment work it great, but in my aws server is freezing.. :(

if Crtl + C to cancel

+1, it is freezing in my env
user_feed works fine

Hope you found a solution for this. I think TikTok changed their welcome interface and requires few clicks to close the modals opened at startup. It worked for me after providing cookies, maybe try doing so.


Beware of preferunits

preferunits allows to change the preferred units such that they will deviate from the default SI base units:
julia> using DynamicQuantities, Unitful

julia> Unitful.preferunits(u"km")

julia> convert(DynamicQuantities.Quantity,3u"km")
3 𝐋 ¹

I think users shall be made aware of this possibility.
In LessUnitful.jl I tried to provide an API function to allow a consistency check.

Thanks for the notice. The intention of upreferred was for instances like this to be a feature rather than a bug, so users could change the standardized form we convert to before performing calculations. But I just took a look and it seems like in fact due to how upreferred works, your example points out a bug:
julia> using DynamicQuantities, Unitful

julia> Unitful.preferunits(u"km")

julia> convert(DynamicQuantities.Quantity,3u"km")
3 𝐋 ¹

julia> convert(Unitful.Quantity, convert(DynamicQuantities.Quantity,3u"km"))
3 m

So I guess upreferred should always be called within the conversion function, rather than to define a global conversion constant as is being done right now.


Various small fixes

Fixed the name in package.json and bower.json.
Updated dependencies to newer compatible versions
Replaced deprecated ngmin with ngAnnotate
Added tests for readAsBinaryString
Updated README to explain avalability of readAsText and readAsBinaryString.

readAsBinaryString is now obselete


Node-RED is not updated if package lock exists

Current Behavior
When switching snapshots with different versions of Node-RED specified, "Installing Packages" is ran but Node-RED version remains old.
npm install --production (as the launcher and agent execute) ignore package.json and respect the lock file instead
Expected Behavior
We should either we be inspecting the package or indiscriminately deleting the lock file in the agent device project dir when "Updating configuration files"-> writePackage() is called
Steps To Reproduce
Only repeatable with new Deploy Snapshot to App Owned Devices.
Environment

FlowForge version:
Node.js version:
npm version:
Platform/OS:
Browser:

npm install --production should always read the package.json and update the package-lock. So I think there must be something else at the root of why the NR package for example isn't updating.
It's npm ci that is intended to read the package lock and fail the command if the package-lock and package.json aren't in sync.
Testing locally:
// package.json
{
  "name": "testing",
  "dependencies": {
    "node-red": "^3.0.0"
  }
}

$ npm install
$ ls
node_modules/      package-lock.json  package.json
$ cat node_modules/node-red/package.json | jq .version
"3.0.0"

// Updated package.json
{
  "name": "testing",
  "dependencies": {
    "node-red": "^3.1.0"
  }
}

$ npm install --production
npm WARN config production Use `--omit=dev` instead.

up to date, audited 299 packages in 617ms

$ cat node_modules/node-red/package.json | jq .version
"3.1.0"

@Pezmc thanks for taking the time to reason this out.
I can only say, from what I witnessed what was occurring. And deleting package lock fixed the issue.
Perhaps it was an NPM version thing, or a windows thing, or a ~^>= thing, or something else entirely.  The only thing I can say without re-testing and capturing more details is that deleting the lock, this stopped happening 100%.

Brain engaged
This might have been when changing stack from NR 3.1 to NR3.0.2.  But I was certain it was in both upgrade and downgrade situations.

If it was only for the downgrade, that could explain things, 3.1.0 is semantically compatible with 3.0.2, so it wouldn't downgrade the package.
That applies across the board, if you're putting ^3.0.2 in the package, you could always end up with 3.1.0 or even 3.5.3 since they're both semantically compatible with ^3.0.2. A downgrade is never guaranteed, even if you delete the package-lock file.
We should perhaps swap to using specific version number or the tilde, to only pull in patches?

@Steve-Mcl is this fix in 1.14 or outstanding?

Apologies, I thought I'd commented to let everyone know. Perhaps I did in slack and considered the matter parked?
Anyhow, I was unable reliability make the issue reoccur.
Consider this issue parked for now (feel free to close it)


Should Leaflet have an Accessibility Statement?

Motivation
Inaccessibility may be a legal liability under certain international laws and policies. End-users of Leaflet maps have the right to an accessible experience, and implementers (e.g. organizations, individual developers) need to know if they meet those requirements. Documentation should be provided, describing if - and to what extent - Leaflet is accessible.
Proposed solution
The W3C Web Accessibility Initiative (WAI) provides a tool to generate an accessibility statement that could be published to the Leaflet website (reachable through the Leaflet site link in the attribution).
Additional context
Originally suggested in #3210 (comment).

Please label this issue "docs" as well.


Feat: Add fzflua as a picker

I had a little trouble trying to bring in those commits that just came in. I ended up breaking my telescope implementation and part of the fzflua implementation. It is probably because I was doing home renovation all day and now I am falling asleep trying to do all of this. I figured I might as well get this out there for others to critique/help fix up....or send me down a different path entirely...

Thanks!
There is no rush to get this out. Just an interesting experiment to see if it's possible to do in a good way. Next week for me is back to work after vacation, so I expect to be tired and not spend a lot of time on the plugin either.
But it's great to have this as a start and something to learn from and experiment with.


Bump ARENA_FILE_VERSION, add corresponding check to tests

How come that the merged commit (685ec9c) has a different author email than the commit I submitted the PR (5afc7c6d63cf9e115332757c21c3b8af1f495924)?

No idea, it seems like GitHub is doing something weird when merging branches.


Converter changes files codification

The EU4-Vic2 converter sadly changes files codification, making many cultures vanish and destroying any word with diacritics.

Part of that is Vic2 using a different file encoding (8859-15), where EU4 uses UTF-8. Some of those are going to get destroyed no matter what we do, because Vic2 just can't represent them.
If you have particular examples of ones that still get missed though, I can try to fix them.

Vic2 reads UTF-8 correctly. But the converter copies files decodified and
diacritics are all screwn up.


HOLD: Generate self-signed CA and separate certificate

This is a potential fix for reports of Chrome reporting
ERR_CERT_INVALID. Our suspicion is that Chrome may be rejecting the
use of a certificate with both CA: TRUE and the serverAuth extended
key usage.
Here we generated a self-signed CA and then generate a cert signed by
that CA.  Both certificates are concatenated for use in nginx.
Signed-off-by: Steven Danna<EMAIL_ADDRESS>

Unfortunately, this is even worse on Windows.  On Windows 10 and Chrome, it appears there is no easy path to allow the chained certificate like you would allow the current self-signed certificate.
I'm thinking we ship the already-merged Serial fix and see if that helps the users who reported this.
There are a couple of things identified here that we might want to look into:

[ ] Having CA: true and the serverAuth extended key usage on the same cert seems to cause a violation according to x509lint.  Perhaps we can just remove one or both of these for our self-signed cert?

[ ] Having CA: true without a Subject Key ID is also flagged by x509lint.  Perhaps we can just add that to our self-signed cert?

Now that I can test a bit of this on at least 2 OSes I'll play with this sometime this week.

I'll close this if I don't make progress on it this week.


publish<EMAIL_ADDRESS>

Requested by: @chadwhitacre
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[ ] github
[ ] registry
[ ] gcs
[ ] docker[release]
[ ] docker[latest]

Okay, investigated the failure reported on https://github.com/getsentry/publish/issues/540#issuecomment-920223558
Looks like this was a transient issue with GitHub as their servers responded with 500 errors twice before failing with a 422, claiming the asset already exists. GitHub experienced an issue that morning regarding packages (re storage). Although the timestamps don't match, I think this might be related.
We may arguably add a pass-through for 422 - Asset already exists error but given this was the first occurrence and even after their API claimed we had the assets already there, they were missing so I'd rather not change anything yet.
My guess is we could have just retried without deleting the branch or the release as Craft deletes existing assets and can work with existing releases but this is not documented anywhere. Good reason to start writing some playbooks, maybe as a wiki inside this repo.


hover doesn't work on constants on consecutive lines

e.g. in this example i can hover and get info for a and g through l. hovering b through f doesn't show anything.
If i were to add a line between a,b,c,...f then i could hover them and get info
package main

a :: int
b :: f32
c :: quaternion128
d :: 1
e :: 2
f :: 3

g :: int

h :: f32

i :: quaternion128

j :: 1

k :: 2

l :: 3

Seems to be an issue with core:odin/parser not setting the correct column and offset end. Will have to wait for a fix, or If I have time, i'll look into it.

i can take a look, do you have a repro of the odin parser problem?

I'll make one tomorrow for you.

import "core:fmt"
import "core:odin/ast"
import "core:odin/parser"

main :: proc() {
	p: parser.Parser

	pkg := ast.Package {
		kind = .Normal,
	}

	file := ast.File {
		pkg      = &pkg,
		src      = `
        package test
a :: int
b :: int`,
		fullpath = "test.odin",
	}
	parser.parse_file(&p, &file)

	decl_a := file.decls[0]
	decl_b := file.decls[1]

	fmt.println(decl_a.pos, decl_a.end)
	fmt.println(decl_b.pos, decl_b.end)

	fmt.printf("'%v' \n", file.src[decl_a.pos.offset:decl_a.end.offset])
	fmt.printf("'%v' \n", file.src[decl_b.pos.offset:decl_b.end.offset])
}

I think I've found the problem: https://github.com/odin-lang/Odin/blob/c50eaa0b7781e65778fed57870007094690b6127/core/odin/parser/parser.odin#L3718
here p.prev_tok is a semicolon token that was inserted instead of the rhs of the "assignment"

is the issue up? If not nw I can do it just don't want to make a duplicate issue

yeah forgot to make the issue. You can make the issue. Thanks a lot for looking into it!

Couple of weird things I found with the issue:

hovering on the space after right after b, c, etc. works (also works on a)

even if its a, b, etc is changed to asdf,bsdf, etc hovering s all the way to (and including) the space after f works

I can't reproduce in procedure scope or block scope, though the odin parser still returns an incorrect end offset in those cases
hovering a: int in file scope works (and is subject to the same issue here), but not in struct scope

e.g. a and b can't be hovered here, but if they were just global declarations they could be
foo :: struct {
    a : int,
    b : int,
}

Yeah that hasn't been implemented. I didn't see any reason to show anything in the struct field, when you can literally see the types, but that might change with: https://github.com/DanielGavin/ols/issues/488

Closing. The desired feature will first be added with #488

Will that fix the hovering consecutive constants issue?

I'm sorry. I thought you had fixed the issue on Odin.

I've had a pretty busy week (Canadian thanksgiving) so I haven't been able to get around to it. I think I'm right about the problem but I'm not sure what the fix is, and to know I need to look through both core:odin and the actual compiler's parser. I'll update here when I've gotten around to it.

Oh no hurry then. Not trying to rush you.

the parser issue got fixed


Problem with single dash

Hello there, I accidently created an issue ticket in a wrong repository, the people from gulp-sass-import-json were still kind and tried to help :)
https://github.com/acusticdemon/gulp-sass-import-json/issues/7
Longs to short: When I add just a single dash in a value node-sass seems to have a problem to process the json file:

Hi @soelen! I guess - isn't a valid value for a SASS variable? Unfortunately, SASS handles strings ambiguously and its difficult for us to determine what the intention is in JSON. Almost all of the issues that come up concern strings.
There is a workaround that always works: If it's intended to be a string, wrap it in single quotes.
"shadePrefix": "'-'"

More about handling strings here: https://github.com/Updater/node-sass-json-importer#importing-strings


Taskbarx causes laptop screen to glitch

Describe the bug
Whenever you turn your device on it will cause the laptop screen to show multicolor lines, flashing, black screen, and just glitch out.
To Reproduce
Steps to reproduce the behavior:

Download taskbarx and turn your laptop on

Expected behavior
You should see a black screen and glitching
Screenshots
https://streamable.com/grljhf
Desktop (please complete the following information):

Windows 10
Latest

Additional context
You will have to reboot your laptop to have the issue fixed

I am 100% sure taskbarX is causing this, as whenever taskbarX is downloaded this issue happens and when it is not on my system this does not happen.
If you had this same issue please comment saying so

Had a similar issue on my Surface Laptop 3, though when opening my browser instead of booting up

Had a similar issue on my Surface Laptop 3, though when opening my browser instead of booting up

Had a similar issue on my Surface Laptop 3, though when opening my browser instead of booting up

Had a similar issue on my Surface Laptop 3, though when opening my browser instead of booting up


[mbedtls] update to 2.25

This PR updates mbedTLS version to 2.25 (used in the TF-M 1.3 project) and contains two commits:
[mbedtls] update to 2.25
Which simply replaces the mbedtls files in the third_party/mbedtls/repo
[mbedtls] adapt OpenThread to new mbedtls version
Which:

modifies Autotools, CMake and Android build configuration
increases heap size as new version requires additional 64B
replaces deprecated API (mbedtls_ecdsa_sign_det)
removes workaround with defining mbedtls_ecp_restart_ctx

Apart from making CI green, I've done some manual commissioning tests on nRF52833/nRF52840 with various combinations.
The heap size has been increased by 48B and 64B experimentally (the issue with old values appeared only on CI with -m32 build). However, the overall RAM increase seems to be approx 10B, and almost 2K of flash (on nRF52833).
Probably it might be easier just to review the last commit. Finally, the squash would be needed when merging.

@romacdon the only reason is that this exact version is a part of the latest ARM's official TF-M project (released 3 weeks ago). As we try simultaneously introduce PSA Architecture this might help to reduce potential issues and maintain just one mbedTLS version. I haven't done any experiments to check if there might be any compatibility issues with the 2.26 version, to be honest - so this argument might not be strong enough :smile:.


Add extra headers to request

Add possibilty to inject user defined request headers for tracking purposes.

I like the idea!
Does it make sense to have one on PlaidClient as well, in case one wants to specify a global header that doesn't have to be added by the consumer to each request?

I like the idea!
Does it make sense to have one on PlaidClient as well, in case one wants to specify a global header that doesn't have to be added by the consumer to each request?

Good point! I have added global headers to PlaidClient as well. Those will be merged with the per-request ones.

Thank you @zmijat. This will be included in the next release.


[Feature] Datepicker Component

Description
A Date picker component

This component provide a simple way to select a date value from calendar popup.
You can customize the year and month area on the calendar.
You can set the type of day display. ('narrow' | 'short')

Related Issues
#305 [Feature] DatePicker
Tests
Simple rendering snapshot tests.
Checklist
Before you create this PR confirms that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] Run yarn test or yarn test -u if you need to update snapshot.
[x] Run yarn lint
[x] I am willing to follow-up on review comments in a timely manner.

and renderDay is better than a dayComponent prop.

Refer the parameter names: https://github.com/wix/react-native-calendars

Test will be passed after increasing coverage more.

Good! Do not forget update snapshots.


Resolving Nuget references unreliable in .fsx files when starting VS Code

Describe the bug
When opening workspaces with .fsx files open in VS Code I often get

The namespace or module 'packagename' is not defined

for packages referenced with

#r "nuget: packagename"

Running the Developer: Reload Window command from the Command Palette can make the error go away after one or more attempts.
I just noticed that having multiple (as little as two) different .fsx files open in split editor (both files visible at the same time) makes it much more frequent, to the point of one file/editor causing an error almost every time.
Not entirely sure I was seeing the same issue without split editor, I thought I was but it seems hard to reproduce so could be I'm just imagining.
Steps to reproduce
Create two .fsx files both referencing some nuget packages.
View: Split Editor command from Command Palette or keyboard shortcut
Arrange so both files are open/visible at the same time in the different halves of the editor.
Developer: Reload Window command from the Command Palette (or close and restart VS Code opening the same workspace)
On my machine one of the files will fail to resolve the dependency (almost?) every time.

Expected behavior
Dependencies resolving for script files upon starting VS Code (or reloading  window) even if multiple editors and files are open.
Workaround
Make sure only one .fsx file is open and visible in workspace. Reload window until it works.
Machine infos

Operating system: Windows_NT
Arch: x64
VSCode: 1.88.1
UI Kind: Desktop
Ionide: 7.18.2
Runtime: netcore
Dotnet version: 8.0.100

Thank you for a good repro! I've had this happen so often it was difficult to find time to try to fix it.

I added https://github.com/ionide/FsAutoComplete/pull/1248 a bit ago to help diagnose this and I end up with:

C:\Program Files\dotnet\sdk\8.0.101\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1004: Assets file 'C:\Users\jimmy.packagemanagement\nuget\Projects\251972--31cbe924-5124-4242-968f-17358f43591c\obj\project.assets.json' not found. Run a NuGet package restore to generate this file. [C:\Users\jimmy.packagemanagement\nuget\Projects\251972--31cbe924-5124-4242-968f-17358f43591c\Project.fsproj]F#

I'm guessing there's some restore not happening on F# Compiler Service side, probably can't handle parallel requests.

@TheAngryByrd I'm glad that my repro was helpful and great work in solving the issue so quickly!


[Bug] [Data Development] The button of Check doesn't seem to effect currently

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
在 flinkJar 作业中，点击【检查】后前台抛出错误，且展示时 args 没有正常显示，执行历史一直加载中；同时后台日志显示作业正在运行且有数据生成。
似乎 yarn session 模式作业直接提交到了集群，yarn application 模式作业提交到了本地

What you expected to happen
点击作业后验证语法正确性，不需要提交作业
How to reproduce
在 flinkJar 作业中，点击【检查】
Anything else
No response
Version
1.2.0
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I will check it. thx


Documentation: System Requirements for additional nodes

Right now the system requirements added in https://github.com/replicatedhq/kURL/pull/14 (visible at https://kurl.sh/docs/install-with-kurl/system-requirements) suggest that a kURL node requires the following:

4 CPUs or equivalent per machine
8 GB of RAM per machine
30 GB of Disk Space per machine

My understanding is that this is the requirement for a single-node single-master cluster, where all the default kURL addons get stacked on the single node, including:

prometheus
grafana
weave
contour
kotsadm stack
k8s control plane
rook

Many of these do not need to be replicated for each additional node, be it a master or a worker. It would be great to get an understanding of what the requirements are for both additional master nodes and for additional worker nodes. Kubeadm recommends 2/2:

2 GB or more of RAM per machine (any less will leave little room for your apps)
2 CPUs or more

But I'm guessing that at rest this might be more like 1/1, and that worker nodes would need even less.
Ask
Can we document the differences here? Right now it seems that every node in the cluster requires at least 8GB/4CPU which seems like a very high overhead given what's running.
I think some statement about what is actually used by a kURL stack and what is recommended to leave room for applications is warranted as well.

Hi @dexhorthy,
We tracked this one in an internal issue as well. See [sc-62116].
Thank you for raising it.


Error when run systems uses CLIENT_SECRET

A lot of oauth2 servers/systems uses CLIENT_ID parameter to get the auth code. It would be good to provide this way of authentication

I just noticed it was implemented in the last update


AST for Agda

Similar to the language-coq package that contains the AST definitions, parser and "pretty"-printer for the Coq backend, we need a similar package for the Asda backend.

[ ] search for a language-agda package that is already available in the Haskell ecosystem
[ ] (optional, depends on other options) checkout the Agda compiler for a AST implementation and ask for a separate package
[ ] (optional, depends on other options) outsource the necessary parts form the Asda compiler to its own package

A separate AST package does not seem to exist. The Agda compiler has it's  own internal AST.

Since we decided to use the AST from the Agda compiler, can we close this Issue?


Dynamic Middleware

How do I dynamically enable/disable a Middleware?
This is useful when crawling a series of pages. e.g. page A is a normal HTML page with needs the ExecuteJavascriptMiddleware Middleware and, page B is an ajax page, which has to ignore the ExecuteJavascriptMiddleware Middleware.

There's currently no way to do this as all middleware gets applied to all requests. For your particular example, running the ExecuteJavascriptMiddleware on pages that don't require it still works, however. It might be a little slower, though.

Thanks for the clarification.


Macros for use in BUILD files, such as 'location' or 'exe', are undocumented/poorly specified

Another one for documentation. Let's say you have something like this:
rule1(name = "foo")

genrule(name = "test", cmd = "cat $(location :foo) > $OUT")

There is no documentation about what $(location <PATTERN>) could mean. I mean, OK, in this case it's kind of obvious, it just refers to the output artifact(s) from :foo using the buck-generated, relative path to buck-out/. And similarly you can use $(exe <PATTERN>) to refer to something that has a RunInfo in order to execute it, I believe.
But it's not obvious what other things like this exist, if these take options, etc. I only know of $(location) and $(exe) at least...  My entire understanding of these comes from reading the prelude source code. There are only vague references to this in the Buck1 documentation, but this is something both rule authors and rule users need to be aware of! So it should really get some straight documentation, I believe.
(Side nit: I call these "macros" which I'm sure isn't great because Starlark functions that aren't rules are already called "macros" but I don't know what else to call them?)

Also: there's some special interactions here I discovered with attr.arg() and RunInfo a while back, where, IIRC, you could have a rule that takes an args = [ ... ] parameter of type attrs.list(attrs.arg()), have it produce a RunInfo using those args as part of the command, and then, in the rule call site in a BUCK file, write things like args = [ "$(location :other-target)" ];. Then, when you do something like buck2 run <PATTERN> -- --param1, and the result will be the --param1 is passed after the "$(location :other-target)" i.e. some arguments to the RunInfo come from the rule, and some come from the command line.
The reason I mention this is because maybe there are other particular interactions like this. They should also be documented.

All correct, and indeed needs documentation. The other nuance is that location stays on the current platform, while exe moves to the execution platform. Then you have $(exe_target to stay on the same platform but take the RunInfo. Definitely needs documenting!


CARIN Blue Button - Search parameter that conflicts with the base - SearchParameter-carin-bb-searchparameter-explanationofbenefit-created

In CARIN Blue Button, there is a search parameter that conflicts with the base specification
Currently, this causes the Search Query to generate a bad query to token_values:
SqlQueryData [queryString=SELECT COUNT(R.RESOURCE_ID)  FROM ExplanationOfBenefit_LOGICAL_RESOURCES LR JOIN ExplanationOfBenefit_RESOURCES R ON R.LOGICAL_RESOURCE_ID=LR.LOGICAL_RESOURCE_ID AND R.RESOURCE_ID = LR.CURRENT_RESOURCE_ID AND R.IS_DELETED <> 'Y'  JOIN (SELECT DISTINCT LOGICAL_RESOURCE_ID FROM ExplanationOfBenefit_TOKEN_VALUES  WHERE (PARAMETER_NAME_ID=1392 AND ((TOKEN_VALUE = ?)))) ExplanationOfBenefit0 ON ExplanationOfBenefit0.LOGICAL_RESOURCE_ID = R.LOGICAL_RESOURCE_ID, bindVariables=[2000-04-15]]

I've opened https://jira.hl7.org/browse/FHIR-27738 to track the specification issue. Once the specification issue is resolved, the test CarinBlueButtonTest.testCARINBlueButton_ExplanationOfBenefit_Created_SearchParameter should be enabled.
Once fixed, the Search Query generates the search with DATE_VALUE instead.
Acceptance Criteria

Test passes

The query returns the proper response https://localhost:9443/fhir-server/api/v4/ExplanationOfBenefit?_count=10&_page=1&_format=application/fhir+json&_pretty=true&status=ge2000-04-15

switched to 'Created' per recommendation.


Support GET with a param which has multiple values

So than we can GET like this:
Unirest.get("http://httpbin.org/get").fields(new HashMap<String, Object>() {
            {
                this.put("name", Arrays.asList(0, 1, 2));
            }
        }).asJson();

Is it possible to merge this request?  The inability to pass arrays is blocking us right now and this fix is exactly what we need.

+1 for this pull request. This is a much needed feature for me.

+1 also. I need this exact functionality in my current project. Would love to see it pulled in so I don't have to do it outside of the library.

+1 could really use this capability

+1
This is extremely useful for me.

 Let's pull it in!!

+1 could really use this feature! thanks

+1 - this would really help our use case!

+1 This would really help!

+1 we could really use this feature!

+1 ditto, could use this feature!

+1 This would really help us, can you get this in

:+1:

I've decided to implement this feature by allowing to call the field(name, value) or queryString(name, value) multiple times, like:
Unirest.get("http://httpbin.org/get").queryString("name", 1).queryString("name", 2).queryString("name", 3);

or
Unirest.post("http://httpbin.org/post").field("name",1).field("name", 2).field("name", 3).asJson();

@thefosk - thanks, but instead of making the user go through each query parameter, check if any are a  Collection and then iterate through them and append them as described above, would it be possible for UniRest to perform this?

@jjwyse available in version 1.4.1

@thefosk when value of field is provided in collection style, it will make the fluent api not so fluent because user have to iterate the collection and call the field in a loop. It will also force users to know about the return type of the post  method which should be hidden perfectly. So think about it!

@qiuxiafei - I definitely agree with you on this one.  Would be really nice to handle these Collections in the library as opposed to the users having to do all of the work.

@jjwyse @qiuxiafei As a result of this thread, this feature has already been implemented and available from version 1.4.1 (which is not the latest version anymore): https://github.com/Mashape/unirest-java/blob/master/src/main/java/com/mashape/unirest/request/HttpRequestWithBody.java#L76

good job @thefosk

@thefosk - Sorry, I'm probably just missing something here, but with your changes, when something like Unirest.get(url).queryString(query) is called, you still cannot pass in a Collection in the query map.  I see you updated the HttpRequestWithBody class but it seems like that object isn't used on GET requests.  Like I said, I could very well just be missing something here or looking at your changes incorrectly, so if that's the case, I apologize.
I'm hoping to be able to make a GET request with something like GET http://api.foo.com?bar[]=1&bar[]=2 but it seems this functionality still takes a lot of work on my end.  Thanks again.

@jjwyse You're are right, I've implemented the method only for requests with a body, and not for GET requests. I just pushed a fix, and the latest version supports it.

@thefosk  - great, thanks so much - really appreciate it!


(3.6) HHH-5359 : Derived entity use case fails when the association is bidirectional

Is this pull request out of date?  What are we doing here?


Updates examples/imagenet to use Optax.

#1053

Results from testrun:

v100_x8_mixed_precision 76.27% 4h16m (compared to run from README with 76.47% 7h39m)
v100_x8 76.72% 13h9m (compared to run from README with 76.72% 13h32m)


Add symbols to microsoft's public symbol server

For all IdentityModel assemblies the retail pdb's need to be added to microsoft's symbol servers so debuggers such as WinDbg can find the symbols.

@brentschmaltz - We upload symbols to the NuGet.org symbol server (SourceLink enabled) and to symweb.
Is there still a requirement to upload symbols to Microsoft Symbol Servers?

@GeoK since the goal is for users to be able to get symbols, closing this issue.


chore: release main

:robot: I have created a release beep boop
rnd-compose: 1.0.0
1.0.0 (2024-10-23)
Features

✨ Add rnd-compose template (#186) (2706620)

Bug Fixes

remove development environment  from create-issue-action (#28) (09f31e4)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

rnd-compose-v1.0.0
:sunflower:


Update CodeMirror to the 5.37.0 release

(commit 00f50fb6ed3f7cff629b1c354f7e244e5b53dbb5)
Change-Id: I2b9cbaa62b0a3d754dbc4782b506d27908e856e6

Thanks for the reminder :) Closed by e20a6c227a505ea5dd2203fa68ecbe1311f0d05d

Thanks. When will this version be available on maven central?

I've deployed it to WebJars. It should appear soon.


feat!: update task status

Companion PRs
https://github.com/Substra/substra-backend/pull/823
https://github.com/Substra/orchestrator/pull/366
Part of FL-1397
Please check if the PR fulfills these requirements

[ ] If necessary, the changelog has been updated
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] The commit message follows the conventional commit specification
For any breaking changes, companion PRs have been opened on the following repositories:

[ ] substra-tests
[ ] substrafl
[ ] substra-documentation

/e2e --refs substra-backend=feat/add-new-compute-tasks-status-linked-to-function-status,orchestrator=feat/add-new-compute-tasks-status-linked-to-function-status --tests=sdk,mnist,frontend,camelyon

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --refs substra-backend=feat/add-new-compute-tasks-status-linked-to-function-status,orchestrator=feat/add-new-compute-tasks-status-linked-to-function-status --tests=sdk,mnist,frontend,camelyon

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --refs substra-backend=feat/add-new-compute-tasks-status-linked-to-function-status,orchestrator=feat/add-new-compute-tasks-status-linked-to-function-status --tests=sdk,mnist,camelyon

End to end tests: :hourglass_flowing_sand: STARTING

End to end tests: :hourglass_flowing_sand: STARTING

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --refs substra-backend=feat/add-new-compute-tasks-status-linked-to-function-status,orchestrator=feat/add-new-compute-tasks-status-linked-to-function-status,substra-tests=feat/add-new-compute-tasks-status-linked-to-function-status --tests=sdk,mnist,camelyon

End to end tests: :hourglass_flowing_sand: STARTING

/e2e --refs substra-backend=feat/add-new-compute-tasks-status-linked-to-function-status,orchestrator=feat/add-new-compute-tasks-status-linked-to-function-status,substra-tests=feat/add-new-compute-tasks-status-linked-to-function-status --tests=sdk,mnist,camelyon

End to end tests: :hourglass_flowing_sand: STARTING


Text fields not being cleared because of document's javaScript

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Firefox 112.0.2
Operating system and its version: MacOS Monterey 12.0.1
PDF.js version: 3.5.35
Is a browser extension: no

Steps to reproduce the problem:

Open attached pdf
Type some text into the field, click outside of the field to unfocus
Remove all text from the field and click outside of the field to unfocus

What is the expected behavior? (add screenshot)
The field should be empty.

What went wrong? (add screenshot)
Field is not being cleared - it's not possible to make the field empty.
I found out that if you add any and I mean just any javascript - e.g. just a simple console print statement this problem occurs. However if I remove all javascript, the text field is cleared properly

empty-text-field.pdf
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

I have updated my firefox - pdf.js version is now 3.6.13 but the problem persists


AudioFileReader currentTime goes past the duration

Hi,
I am using this library for a music app. Thanks for the great library! Anyway, I noticed that for some songs the AudioFileReader currentTime goes past the duration. For example there's this song that has a duration of 234.143997 with a last current time of 253.638702. I am not that familiar with audio and I wonder if there's a property that I can set to minimize the difference. Btw, I also tried timing the song while it's playing and the duration is just right(the song plays for 234 sec) but the currentTime exceeded. Thanks!

I'm having a similar issue, but in my case, the current time is sometimes negative and it never reaches the duration.


Fix Linovelib

fix  #860

fix next page check in Linovelib

fix incorrect next page url if chapter has more than 3 pages in Linovelib

you have to increase the plugin version (1.1.2)


FIX: cask changes /usr/local ownership recursively

Problems
Relatively old code in Hbc::Caskroom recursively changes the ownership
of the directory where the Caskroom directory exists, that changes
entire files in /usr/local to user:staff if Homebrew setup with default
configuration.
This is really dangerous because it's easy to trigger (just simply type
brew cask something by following some installation documentation.)
Solution
This patch removes entire chown with -R option and make the logic
simply creating Caskroom directory with default Homebrew directories
ownership and permission.

👍 to not changing permissions of toplevel_dir.

@reitermarkus How's this looking?

Thanks @niw!


aliases shadowing program names

I found some aliases to shadow program binaries. There should not be clashes at least with widely used software as this can have unwanted side effects, e.g. for scripts.
Example
The alias gs='git status' from aliases/available/git.aliases.bash shadows the ghostscript binary named gs. This should be corrected, maybe use ggs or something that does not create a name clash.
Testing all aliases
I quickly wrote up a check for all aliases, using apt-file
for i in $(sed -e '/^alias/!d;s#=.*$##;s#.#\.#g;s#alias #bin/#;s#$#$#' *); do echo "-- $i --"; apt-file -x search "$i"; done |tee /tmp/bashit-alias-check.txt
bashit-alias-check.txt
File is attached (the loop takes a while, maybe it can be sped up with a regexp containing all patterns).
On a quick scan, I found the following being problematic, too:

--  bin/edit$ --
mime-support: /usr/bin/edit
389-dsgw: /usr/lib/x86_64-linux-gnu/dirsrv/dsgw-cgi-bin/edit
-- bin/gm$ --
graphicsmagick: /usr/bin/gm
-- bin/gst$ --
gnu-smalltalk: /usr/bin/gst
-- bin/gs$ --
ghostscript: /usr/bin/gs
-- bin/gpo$ --
gpodder: /usr/bin/gpo
-- bin/gc$ --
graphviz: /usr/bin/gc
-- bin/bup$ --
bup: /usr/bin/bup
-- bin/bls$ --
bacula-sd: /usr/sbin/bls
-- bin/jed$ --
jed: /usr/bin/jed
-- bin/jls$ --
libtsk3-3-dbg: /usr/lib/debug/usr/bin/jls
sleuthkit: /usr/bin/jls
-- bin/jdb$ --
gcj-4.8-jdk: /usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/bin/jdb
openjdk-6-dbg: /usr/lib/debug/usr/lib/jvm/java-6-openjdk-amd64/bin/jdb
-- bin/nup$ --
dvi2ps: /usr/bin/nup
-- bin/r$ --
littler: /usr/bin/r
-- bin/restart$ --
fastdnaml: /usr/lib/fastdnaml/bin/restart
interchange: /usr/lib/interchange/bin/restart
upstart: /sbin/restart

OS and bash version
I use:
bash --version
GNU bash, Version 4.3.11(1)-release (x86_64-pc-linux-gnu)
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty

What are your suggestions for resolving these conflicts?
Btw, I couldn't run the script, got the following error:
sed: read error on data: Is a directory

Agreed, so far these conflicts have not been an issue for me (or for anyone else, at least nobody reported them).
I use the gs (git status) alias all the time, and I never use Ghostscript, so it's not an issue for me.
I'm not sure how to handle this - open for suggestions and ideas...

Personally, I have the issue with gs, but for my daily work, I prefer having the gs (git status) alias by hand, because I rarely need ghostscript.
A proposal that will work is to have a kind of "hook or "check step" that will try to guess if a command exists with the same name of an alias or a function name (in the past, this problem was with a function) https://github.com/Bash-it/bash-it/pull/401) and ask the user for confirmation or for an alternative, like renaming the alias or function, or something similar...
This problem is not simple to solve, but we can try to do a "best effort" to mitigate it.

I found the 'namespace notation' not bad (with colon or maybe a dot, which is always near/same, even on different keyboard layouts), then it would be g.s for git status (or b:gs for bashit_namespace:alias). This will never clash with other binaries. And it is clearly an alias and easy to guess where it is defined.
Or check aliases against existing binaries as I did above.

@MunifTanjim this "script" had be run from within aliases/available/ dir, I added the full path, so it should work now from everywhere.

So what are we suggesting to do for this? How about the following (open for discussion, of course):

The default behavior stays the same as it currently is to provide backwards compatibility.
Add a flag to the installer that sets a config value to use the "b:" (or "bi:") namespace for aliases.
If this config value is set, all of Bash-it's aliases are prefixed with the above namespace, so e.g. b:gs instead of just gs.

This would be an all-or-nothing setting, so that you either use the namespace for all aliases or for none of them. Why? I'd like to avoid having to check for existing commands at startup, which will be costly and time-consuming. Secondly, your aliases might change depending on what you install, which means you might be in for a surprise after installing a new OS package.
Ideally, the above can be implemented without changing any of the existing *.alias.bash files - maybe we can squeeze in the namespace while sourcing the alias files - which would prevent us from having to touch all of the alias files.
What do people think about this approach?

I'm not very worried about gs. I had one script that fails when I run it in my shell but it's fine when it is run from cron, whicxh is where I need it to work, I 'll just add an unalias gs to the script if I see I'll need it.
What did bother me is gst switching from status to stash all of a sudden in #1352, but I override it in my personal dotfiles.

Did y'all know that defining functions captures aliases?
So, if aliases/git is loaded first (which creates a gs alias), and then a function repdf referring to Ghostscript gs is loaded later, and then finally the user's custom.bash deletes the gs alias (since they use Ghostscript), then: declare -F repdf will still show a weird git command and will need to be loaded again fresh.

Aliases should be loaded dead-last, and I suggest extra care should be taken to avoid unintentional naming conflicts with existing commands.

Did y'all know that defining functions captures aliases?

TIL !
BUT really functions should probably be using command gs when they explicitly want to invoke ghostscript.
On the reverse side, bash-it has its own issues when encountering user-defined aliases for popular commands, ie ls, grep etc ... and we have to remember to explicitly invoke the command to avoid the alias.

Aliases should be loaded dead-last

Yeah that's probably true.
Another kinda related concern: Functions and aliases area meant to be loaded within .bashrc and not in .bash_profile - At some point I think we're going to need to look into separating bash-it into two/multiple stages.


Fixing toleration for recent version of Kubernetes

On recent Kubernetes versions, Romana does not deploy on fresh kubeadm deployed cluster due to missing Toleration to "node.kubernetes.io/not-ready:NoSchedule" taints being present on all nodes before CNI to be functionnal.
This fix is just a toleration to this taint to let romana deploy on unready nodes.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Alexis Ducastel seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

In facts, the problem appears with version 1.12 of kubernetes, 1.11 does not apply taint"not-ready", 1.12 does !


Replacing vm.createScript in favour of vm.Script

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
It seem's vm.createScript is deprecated, because it's not mentioned in the official docs. This PR replaces vm.createScript by vm.Script.
This was needed by myself to run node-red with bun.sh. vm.createScript is not available in bun, because I think they missed it due of the missing documentation? Not sure.
The advantage of running node-red with bun is support of esm :)
I also opened a PR there to add support for vm.createScript: https://github.com/oven-sh/bun/issues/8312
Checklist

[X] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[X] I have run npm run test to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

This was needed by myself to run node-red with bun.sh. vm.createScript is not available in bun, because I think they missed it due of the missing documentation? Not sure.

NodeJS has not documented createScript since Node V0.12  (24 Nov 2015)

It seem's vm.createScript is deprecated, because it's not mentioned in the official docs. This PR replaces vm.createScript by vm.Script.

My guess is that it was simply undocumented while node was still in beta/pre V1. (tho it is odd that they have kept it around!)

PS: Since you are playing with bun, be aware there is a major problem with GOT (the http request library we use under the hood) + Bun.
You will crash node-red with the exception "A retry listener has been attached already" when attempting to do HTTP requests.
It doesnt look like a quick fix nor does it look like GOT or BUN are in any hurry to resolve it.

https://github.com/sindresorhus/got/issues/2299
https://github.com/oven-sh/bun/pull/4395

PS: Since you are playing with bun, be aware there is a major problem with GOT (the http request library we use under the hood) + Bun.
You will crash node-red with the exception "A retry listener has been attached already" when attempting to do HTTP requests.
It doesnt look like a quick fix nor does it look like GOT or BUN are in any hurry to resolve it.

https://github.com/sindresorhus/got/issues/2299

https://github.com/oven-sh/bun/pull/4395

Sadly yes, I discovered the error just after I created this PR ;(
Switched back to node for now.

Thanks for this. Given the node.js (undocumented) implementation of createScript is to simply delegate to new Script() this appears to be a pretty sensible change to make.


Where can I found calc_psnr and calc_ssim?

I was trying to reproduce the validation results, I was able to get the same results for MSE and MAE, but I got different results for PSNR and SSIM. (I'm using the pretrained models provided)
Now I'm using skimage.metrics:
from skimage.metrics import structural_similarity as ssim
from skimage.metrics import peak_signal_noise_ratio as psnr

I can't find the "qualitycc" import anywhere.
Where can I find the two functions "calc_psnr" and "calc_ssim" placed inside validation.py?

https://github.com/gaoguangshuai/survey-for-crowd-counting/tree/master/Python-script

thanks!


Question

Hello, thanks for this, amazing!
One question, in doc "Note: As transaction fees may be huge, it is strongly advised to only deploy EthAir Balloons models in private Ethereum blockchains or locally using ganache-cli", in case how to create "private Ethereum blockchains"?
For production mode is recommend using private Ethereum blockchains ou ganache-cli?
Thx!

Hello @fabioselau077 , thanks for your question and your kind words!
Here is an extensive article explaining how you can create a private Ethereum Blockchain.
https://medium.com/swlh/how-to-set-up-a-private-ethereum-blockchain-c0e74260492c
If you enjoyed Ethairballoons, please do not forget to star the project.
Thanks again,
Petros


Slow Inference

Hi, the inference with the current code is very slow. Takes more than 30 mins for a single inference on a v100 gpu. How could we speedup the inference?

#125
This issue I created may be useful to you 😃


Windows Server 2008R2  No Tasks Being Listed

So I had the service set up to enumerate the tasks and add some info to a datatable, which I then databind to a webpage.  When testing on my local pc, running XP, the service worked perfectly, but as soon as I moved it over to the server, the list of services was null.  I've checked manually using the console, and there is an extensive list of services.  Please advise.
Code is as follows:
using (TaskService ts = new TaskService( ))
{
            Version ver = ts.HighestSupportedVersion;
            bool newVer = (ver >= new Version(1, 2));

            // Output all the tasks in the root folder with their triggers and actions
            TaskFolder tf = ts.RootFolder;

            foreach (Task t in tf.Tasks)
            {
                tasks.Add(t);
                string trStr = "";
                DataRow r = schedTable.NewRow();
                try
                {
                    r["Name"] = t.Name;

                    foreach (Trigger tr in t.Definition.Triggers)
                    {
                        if (trStr != "")
                            trStr += ";";
                        trStr += tr.ToString();
                    }
                    r["Schedule"] = trStr;
                    r["Next"] = t.NextRunTime;
                    r["Last"] = t.LastRunTime;
                    r["Status"] = t.State;
                    r["Enabled"] = t.Enabled;
                    r["Description"] = t.Definition.RegistrationInfo.Description;

                    schedTable.Rows.Add(r);
                }
                catch { }
            }
        }

Originally posted: 2011-03-23T10:37:35

See the bottom of post http://taskscheduler.codeplex.com/discussions/247469 about permissions needed to access the Task Scheduler. Your code is correct, and I know others are having no problems with WS08R2, so I'm guessing it's a permissions issue.
Originally posted: 2011-03-23T12:11:32

I had just finished checking that post, and I agree that the situation seems very similar.
Originally posted: 2011-03-23T13:02:05

I run this from an administrator account, and I've checked, and I have SeBatchLogonRight permissions, but I still get an access denied error
Originally posted: 2011-03-24T11:19:29

Below is a short PowerShell script that should list all the task names in the root folder. Running this while logged in to a user session may show you the errors your C# code may not and should give you some further information about what works and what doesn't. You will need to change the path in the first line to the path on your system. If scripting is restricted, you can open the PowerShell console and cut and paste each line of the script in order for the same results.
Add-Type -Path 'C:\Users\dahall\Documents\Visual Studio 2010\Projects\TaskService\bin\Release\Microsoft.Win32.TaskScheduler.dll'
$ts = New-Object Microsoft.Win32.TaskScheduler.TaskService
$ts.RootFolder.Tasks | ForEach-Object {Write-Host $_.Name}
Originally posted: 2011-03-24T15:10:08

The list of tasks is no longer a problem, it was a permissions error.
Adding tasks, however, is still something of a problem.  At any attempt to do so, I am met with "System.Runtime.InteropServices.COMException: (48,7):Body:" as my stack trace at
ts.RootFolder.RegisterTaskDefinition(txtName.Text.Trim(), td);
My code for this section is: protected void btnSave_Click(object sender, EventArgs e)
    {
        TaskDefinition task = (TaskDefinition)Session["Duplicate"];

        using (TaskService ts = new TaskService())
        {
            TaskDefinition td = ts.NewTask();

            foreach (Trigger t in task.Triggers)
            {
                td.Triggers.Add((Trigger)t.Clone());
            }
            foreach (Microsoft.Win32.TaskScheduler.Action a in task.Actions)
                td.Actions.Add(a);

            td.RegistrationInfo.Description = task.RegistrationInfo.Description;

            ts.RootFolder.RegisterTaskDefinition(txtName.Text.Trim(), td);
        }

        Session["Duplicate"] = null;

        Response.Redirect("~/Default.aspx");
    }

Originally posted: 2011-03-31T09:41:04

COMException usually will include the COM error (result code) from the method execution. Can you provide the internal details of the COMException? This could also be a permissions problem as creating task requires more rights than reading tasks. One thing to consider is that the way you are calling it, without any user information, will assume the current user and an interactive logon type.
Originally posted: 2011-03-31T13:52:08

I would try the following code which uses cloned Actions as well as cloned triggers, which works for me:
TaskDefinition td = ts.NewTask();
foreach (Trigger t in task.Triggers)
td.Triggers.Add((Trigger)t.Clone());
foreach (Microsoft.Win32.TaskScheduler.Action a in task.Actions)
td.Actions.Add((Microsoft.Win32.TaskScheduler.Action)a.Clone());
ts.RootFolder.RegisterTaskDefinition(taskName, td);
Originally posted: 2011-04-23T23:53:57


add metadata

This PR adds Metadata (map[string]string) to the Command struct.

needed to fix https://github.com/containous/staert/issues/20

Coverage remained the same at 86.486% when pulling 29f09d7236ea5342476ed67cd8da701d913117c1 on add-metadata into b98687da5c323650f4513fda6b6203fcbdec9313 on master.

Coverage remained the same at 86.486% when pulling 29f09d7236ea5342476ed67cd8da701d913117c1 on add-metadata into b98687da5c323650f4513fda6b6203fcbdec9313 on master.

Coverage remained the same at 86.486% when pulling f7788df500b7ac9a361bbe2359e4a169ea6f2c6c on add-metadata into b98687da5c323650f4513fda6b6203fcbdec9313 on master.

LGTM


chore/use-plug-on-refresh

Use <Plug>(kubectl.refresh)
TBH I'm not sure if we need it, but just in case.

I like it!


Suggestion: Syncmatica as a Server-Side Plugin

I have a suggestion that might make Syncmatica even more versatile: what if it could be installed as a server-side plugin?
A plugin version would likely be easier for server owners to set up and could make Syncmatica more accessible and widely used across various servers. Instead of requiring a modded server installation, the plugin could seamlessly integrate with existing server setups, offering a more convenient solution for admins.
Just an idea that might help shape the future of this project! Thank you for considering it, and I look forward to seeing how Syncmatica evolves.

That's out of the scope of my fork.


Update changelog

Codecov Report

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

@@            Coverage Diff            @@
##           master     #162     +/-   ##
=========================================
+ Coverage   83.55%   85.95%   +2.4%
=========================================
  Files          30       30
  Lines        1678     1809    +131
  Branches      201      260     +59
=========================================
+ Hits         1402     1555    +153
+ Misses        227      209     -18
+ Partials       49       45      -4


Selecting year does not work in single date picker

This is almost done in development but still has a strange bug if you go next year it and then select others years it will bug

yes me to

I think it only does not work in the web version at the moment. Can you confirm? And are you on the latest version?

This is fixed in v0.2.10


ROX-10069 add cluster id flag in deployment check

Description
[WIP]
Add cluster flag to deployment check in roxctl to allow central to evaluate system policies with network policy fields.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on stackrox/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed

@lvalerom could we close this for now and open it again when we have to address it?

@lvalerom could we close this for now and open it again when we have to address it?

Absolutely


Cursor keys for character selection

Use the cursor keys to navigate and select a character

see https://github.com/nurpax/petski/issues/25

With multiple screen support now in, I'd vote for using the cursor keys for screen switching. At least for me something of greater importance

Maybe a,w,s,d for char selection?  Added left/right for screen selection just now.  Char selection is pretty common too, maybe more common than screen selection.


Run on fewer container versions

This will make CI faster and still provide sufficient coverage of relevant versions. We now only run on the major.minor container tags (latest maint release) and latest-preview. This skips over a bunch we were trying before that had expired community edition licenses.
This change partially addresses #451 but doesn't provide the entire solution.

There's a fix for the failing unit test (not reported as a failing check still, that's another part of #451) in https://github.com/intersystems/ipm/pull/447


C#: Remove results from cs/local-shadows-member

Remove a few results in the extractor codebase.
Change the query to remove results whereby a constructor parameter shadows a member, because it is probably used to initialise the variable, and having the same name helps document that.

This pull request fixes 12 alerts when merging 8cdfb8707c65176ef090a78b5c85c0d0c99ef171 into 292189c1e03c94a64a5248fda8b4adb9ad9579be - view on LGTM.com
fixed alerts:

12 for Local scope variable shadows member

Comment posted by LGTM.com

This pull request fixes 12 alerts when merging 448b080d4fa3adccf898879c4dd9f3b155cdd9d8 into c577f6d9f8427e8193542e467158e0aad491136e - view on LGTM.com
fixed alerts:

12 for Local scope variable shadows member

Comment posted by LGTM.com


⚠ DDoS-Relay EU-W-lon1-02 has degraded performance

In bfb8f33, DDoS-Relay EU-W-lon1-02 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 189 ms

Resolved: DDoS-Relay EU-W-lon1-02 performance has improved in 409e990 after 5 minutes.


UTCT-24: Power C frontend logo; frontend text config.

For 12/13/2023 demo.

https://gotest.utc.edu

I love it, but just curious, are we allowed to cut the power c in half in the background?

@bridget, IDK but it can be moved up or down if required. It's just using the default positioning of the default logo.

So, I did verify... the Power C is not allowed to be on a background that bisects it for brand compliance. Also, it was requested that the whole horizontal logo be presented above the white field, not just the power C. Otherwise, I think it looks FANTASTIC!

[ ] Steve Rumbaugh requests we use the full UTC Wordmark, in the dark blue area above the white form.