[Snyk] Security upgrade alpine from 3.17.3 to 3.18.6

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

dev-environments/https-proxy-upstream-tlsv1.3/tinyproxy.Dockerfile

We recommend upgrading to alpine:3.18.6, as this image has only 6 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

CVE-2023-5363 SNYK-ALPINE317-OPENSSL-6032385
  614

CVE-2023-5363 SNYK-ALPINE317-OPENSSL-6032385
  614

Use After Free SNYK-ALPINE317-BUSYBOX-7254940
  586

Use After Free SNYK-ALPINE317-BUSYBOX-7254941
  586

Use After Free SNYK-ALPINE317-BUSYBOX-7254942
  586

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Use After Free

superseded by https://github.com/3scale/APIcast/pull/1473


Printing maps

How do we allow large printings?
Possible issues:

pixelated maps
missing part of property (out of extent)
too small to be useful
multiple pages

Possible fixes:

[ ] limit size
[ ] print per tax lot
[ ] ...?

Issue moved to Ecotrust/landmapper #1 via ZenHub


Shell and npm tasks are unavailable on vscode desktop

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Try to debug monaco-editor, or any project with a launch.json that uses a preLaunch task
Tons of extensions (every extension that provides a task?) activate

I also notice at this point that the "Run Tasks" list doesn't have any of the tasks that are defined in the tasks.json, so I think debug is just trying to activate all of them to see if they might provide that task that is apparently missing

Tasks output for some reason indicates shell and npm tasks are unavailable, even though I'm running on vscode desktop

I hit this a few times over the last few weeks, but forgot to file an issue after I got back from vacation, apologies

The only thing that's changed in tasks within the last milestone was the implicit activation, so likely same root cause

Would that have caused the "shell tasks are unavailable" issue as well?

/closedWith 440bade


add_LCT015_color_temperature_values

Add color temperature values for the LCT015 bulb: https://zigbee.blakadder.com/Philips_LCT015.html

Great work. Could you also add the new light to supported lights chapter in the readme?

Of course, done :-) Mhmm, it looks like I'm creating some errors in the github check pipeline?

Yes the build is still failing, it has never passed yet. so no issue.
I have made an icon and submitted a PR, when this is merged by home assistant core developers, the build will pass.

@CM000n During inspection / analysing of the profile library I noticed this profile has incorrectly set the measure_device. It's either unknown of to generic model. Do you still remember which exact power meter model you used during measurements? That would help further improve the library quality also for future reference.

Hi @bramstroker. It was measured with one of these devices: https://avm.de/produkte/smart-home/fritzdect-200/


Ensure metadata of self-referential crates can be read.

Also ensure that if reading metadata fails, we don't crash and instead just avoid checking manifest-related lints.

Thanks to @jonathanpallant for reporting this issue!


Feat: Refactor the filter projects logic

What feature?
We can remove the use of useState hook for filtering the projects and can do it by just using the useSearchParams hook.
Add screenshots
No screenshots
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

hey, we are adding a new filter option so ig we don't need to refactor right now.

hey, we are adding a new filter option so ig we don't need to refactor right now.

okayy


v2.6.4 Release Task - Prepare Draft PRs for releasing charts.

Rancher Backend Engineering Task
This is a Rancher backend engineering task for (https://github.com/rancher/rancher/issues/36375) for the rancher engineering team 3 & the Release captain to:

[ ] System-Charts: Make a PR from the dev branch into the release-branch. Review to make sure the system charts seem aligned with what’s expected. The title of the PR should be the release vehicle that all the system charts are being added for.
[ ] Charts: See the checklist for specific information.

PR is ready, will be reviewed again this afternoon.


Adding Dockerfiles for 20.0.0 release

The 20.x dockerfiles are currently a copy of GraalVM/CE/19 with a different GRAALVM_VERSION var.

If the Dockerfiles are the same, why do we need a different set? Why can't we just set the Graal version at build?

I am unsure how to structure it best, we could also drop the directory for the version in "GraalVM/CE/19".
I slightly prefer having one directory per major version, because 19.3 is a LTS version. So there will be also new 19.x releases this year.
It gives us more flexibility to develop the Dockerfiles for 19 and 20 differently.

I definitely prefer simplicity and deduplication, so if the Dockerfiles are identical except for 19 vs 20, then I'm strongly more in favour of just removing the version from the path completely.

You've changed the files, but not the path? I would suggest removing the 19 from the path completely.


p005-ReLU-Activation_Spiral_Dataset C#

Added Spiral Dataset data from tutorial p005 to C#
use MathNet.Numerics to handle vector and matrix operations.

Hi,
We already have a submission for this part. Is there any reason why we should replace it with your implementation?

Hi Daniel,
Thanks for reaching out. Yes I noticed there was a submission for that part
already, however that submission doesn't includes the spiral dataset.
In the versiob I created the data set is implemented the same way as innthe
python example and therefore makes it more compatible with the book and I
assume the rest of the videos coming next.
Let me know what you think.
Cheers,
Tanai
On Wed., Dec. 23, 2020, 9:35 p.m. Daniel Kukieła<EMAIL_ADDRESS>wrote:

Hi,
We already have a submission for this part. Is there any reason why we
should replace it with your implementation?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Sentdex/NNfSiX/pull/126#issuecomment-750711037, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AP2DYV3YV4TRADZOQZGT4M3SWKSGXANCNFSM4N5XDAHA
.

@harigovind511 Since you implemented part 5, what do you think about it?

I'm going to accept this and replace the existing file.
Thank you for your submission!

I'm going to accept this and replace the existing file.
Thank you for your submission!


Visualizer not working - Failed to Initialize Audio Client

Howdy,
I recently downloaded Rainmeter and the Monstercat Visualizer onto my computer and have been having issues with the bars not responding to music at all. The Track Info and Album Cover skins work perfectly, however the visualizer bars remain at zero despite music playing through the speakers. I am playing music from the Spotify Desktop App.
After checking the Rainmeter log, I am constantly receiving this Warning while the Visualizer skin is loaded: "Failed to initialize audio client"
http://imgur.com/gallery/I3zxS
Things I have tried:

Updating my audio driver of my Motherboard
Reinstalling Rainmeter, Spotify, and the visualizer skin
Adjusting sensitivity, checking to see if Rainmeter is muted in volume mixer, setting my speakers to default.
Everything on the troubleshooting guide (https://forum.rainmeter.net/viewtopic.php?p=123883#p123883) except for putting my device ID into the skin due to lack of knowledge on how to do so. I downloaded the ExampleAudioLevelSpectrum skin but it didn't do anything when loaded except give a few gray bars.

Something I noticed: In the Monstercat Visualizer settings I can choose to change the audio device in the General tab, but nothing shows up on the current audio device next to it. I also noticed when using the Audio Device Information skin from step 6 of the troubleshooting list that nothing is registered as my Default Output Device, despite having it set as my speakers in Windows. Here is a picture of what I mean: http://imgur.com/gallery/oUIL4
I am running Windows 10, Rainmeter Version 4.0.0 r2746 64-bit, and Monstercat Visualizer Version 1.7.1
Thank you in advance for helping and let me know if you need any other information

One other comment I forgot to add: I have tried using other visualizers to check (Radian's LinearVisualizer to be exact) and the bars also do not respond to music.

This is clearly an issue with the audio plugin so not a lot we could do here.
However if I had to guess it may be that the name of one of your audio devices is causing an issue. Wanna screenshot your windows audio devices window? Preferably show disabled and disconnected devices when you do it.
If it is not that try uninstalling and installing any drivers for any audio devices in there or disabling all but one of the audio devices and restart rainmeter (fully exit and relaunch rainmeter not just the skin) and see if you can even get that menu to see anything.

Thanks for the reply!
I had a feeling it was a problem with the audio plugin and not the skin itself, I just didn't know who else to ask help from and a Google search didn't help that much. Below is the screenshot of the audio devices I have right now. The speaker is an old iHome speaker connected to the rear audio jack via 3.5 mm cable. I'll see what I can do about updating audio drivers on this thing (I tried updating it by updating them through the device manager, but still nothing).

Can you scroll down to see the rest and screenshot it? But yeah I am not seeing anything out of place with those devices and I doubt the rest of them will be any different.
Try though the disabling them all but the speakers you are using thing and rebooting rainmeter and see what that does.

As for where to go try just going to the rainmeter forums and posting there since it is an official part of rainmeter these days.

The last two things on the list were just two more "NVIDIA Outputs."
I'll try to disable everything and will get back to you if it works. I think I'll also post this issue on the rainmeter forums like you said.
Once again, thanks for the help and quick replies!

Found this today, seems close to your issue. https://forum.rainmeter.net/viewtopic.php?f=14&t=25735

Any luck getting it to work? If I dont hear back in a few days I will go on ahead and close this issue.

I'm gonna close this issue, @MrVincentC please write a comment below if you still got the issue and you want to reopen it.

im using realtek, n after some hours of frustration i found out that when i use my bluetooth speaker (external audio) the visualizer works, but when i return on using my laptop (realtek) speaker, it just stop working and the 'failed to initialize audio client' popped back, i tested by removing my bluetooth speaker, restarted back my laptop so that it return to using the laptop's speaker (the same thing as if you just put your default laptop speaker which in my case is realtek back as default speaker), the visualizer doesnt work, so i can assume for now that anyone whos using the latest buggy realtek should opt to using external audio or simply downgrade realtek, although the last time i downgraded it, the visualizer still wont work, its a hassle though, but for now i would just opt to using my external bluetooth speaker ^^ hope it helps others, btw if someone found out which realtek version work without using external audio please do share, thx!

Go to Device Manager and Uninstall Speakers devides. Restart computer and it works for me.


Don't export all of d3

followup from https://github.com/openstreetmap/iD/pull/4372#issuecomment-332292559
We're currently doing this in our iD index.js:
import * as d3 from 'd3';
export { d3 };

So that later we can use it from our spec_helper.js so that tests can use it.
window.d3 = iD.d3;   // TODO: remove

Instead our test harness should be able to require d3 separately in index.html:
<script src='../node_modules/d3/build/d3.js'></script>

... and that mostly works, except some of the tests that use events don't like it at all.  d3.event is special because it's like a global event reference.  The d3 docs have this to say:

If you use Babel, Webpack, or another ES6-to-ES5 bundler, be aware that the value of d3.event changes during an event! An import of d3.event must be a live binding, so you may need to configure the bundler to import from D3’s ES6 modules rather than from the generated UMD bundle; not all bundlers observe jsnext:main. Also beware of conflicts with the window.event global.

☝ So I think this is an actual problem for how the tests are written, and we should figure out what this means and how to do the thing.  I did a bit of debugging, but it involves digging into what the bundled d3 code is doing, because the sourcemaps lie.

I'll have a crack at it

ill work on this issue

when i make the following changes obviously by removing the import command, the entire site goes blank. So what exactly do i need to do, could you please guide me

when i make the following changes obviously by removing the import command, the entire site goes blank. So what exactly do i need to do, could you please guide me

I would expect that removing the
import * as d3 from 'd3';
export { d3 };

...should not make the whole site go blank - but it should make several of the tests fail.
What kinds of errors do you see in the JavaScript console?

Its going blank unfortunately, atleast on my local host. Please guide


"HELPER - ObjectOperations" does not need run-only users permissions setup

Child flow "HELPER - ObjectOperations" does not have connections defined as it seems to trigger other HELPER flows. So no need go to run-only permissions just enable the flow

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

ID: 9fe69498-a485-5379-97ff-53fbe029f11a
Version Independent ID: 5b3f9705-9e49-1575-4ae7-0293d12b739c
Content: Set up core components - Power Platform
Content Source: power-platform/guidance/coe/setup-core-components.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

We're reviewing this together with #990 for the next release and will update the docs for December.


Charts tokens - dupes in dark CSS

Looks like all of the charts tokens are output again in tokens-charts-dark.scss, not just the tokens that are different for dark theme compared to tokens-charts.scss. Shouldn't the dark stylesheet only include necessary overrides to the default tokens?

I agree, the dark charts stylesheet should only include the overrides.
At a glance, it seems to be something with the structure of the collection in figma and/or the exporter - the dark charts tokens aren't coming with 'dark' as a layer.
Once that's done, the dark charts config might also need to look for charts.dark instead of just charts


Some unwanted symbols on map

i have attached the image of the issue, i don't know how to reproduce it since it happen rarely

Any solution to avoid this

I don't think this happens with this module, also I  cannot reproduce this on my end.   Please include a plunker example so that I see this issue.

zoom control button png image is showing , instead of single plus it shows the full image
you can see this in latest chrome browser
https://www.bagyourjob.com


remove dev files from package

those files probably are not used by end user of the lib

@chr-hertel can you please request the review from other  repository owners?

@dbrumann I can remove it, if you want

Thank you @vladyslavstartsev.


Mail header matching and overriding

I see your TODO lists "Mail header matching and overriding."
I want to +1 that :smiley:
if I wanted to take a stab at implementing this as a PR, do you have any tips on where I should start, coding standards to follow, etc?

One way to look at it is that the Subject field is in email headers, so header matching is just a generalised form of subject matching.
My plan for implementing matching was to add a MatchHeader function on Filter, with corresponding test coverage. After that, refactoring the subject matching to use the general header matching function would be simple. Storage would require key/value pairs underneath a "Headers" string map on Filter. I was going to leave the Subject field in the UI though, as IMHO it is more user-friendly to have it.
I haven't got a plan for overriding the headers on a Route though.
As far as coding standards goes, I just try to keep functions small, and run go fmt on the files before I commit them.


EEPROMWrite

I use an arduino mega, after a power cut, the shutters go up, while they were positioned at 50.
I tried to understand how data was stored by callback without success.
If I had the address on the eeprom, I could check what happens. From 0 to 9 the value remains at 255.
Can you help me?

See https://github.com/marvinroger/homie-esp8266/blob/develop/examples/SonoffDualShutters/SonoffDualShutters.ino
You don't have the address, you store it wherever you want.

Ok c'est réglé 1000 merci


Removed ResourceHealthAlertRules private preview

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

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors 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

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

ResourceHealthAlertRules is an unused feature that was in private preview.  There are no customers and since the feature was lowered in priority there is no plan to bring it to customers in the near future. Therefore we would like to remove it from the specs repo and from the ARM manifest.
Here is a PR for removing it from the ARM manifest.
I followed instructions here to validate not resources currently exist, but the query is failing on nonexisting table. Are there updated instructions for this?

Can you please get a breaking change sign off and check this in ?

@ruowan can you please help us out to merge this PR?


Bug/backend type

To check:

The README.md example.
The python examples in the docs folder.
The ipython notebook examples in the doc folder.

Coverage remained the same at 100.0% when pulling 50855e9925860a24530f8e6e9cc3be007f08a8a8 on bug/backend_type into a0536a74640c7da930b9d4f5771b6a45e987befb on dev.

Coverage remained the same at 100.0% when pulling 50855e9925860a24530f8e6e9cc3be007f08a8a8 on bug/backend_type into a0536a74640c7da930b9d4f5771b6a45e987befb on dev.


feat: port CategoryTheory.Limits.Shapes.ConcreteCategory

Closing because the file is about to be deleted in mathlib3


Merge #14477: Add ability to convert solvability info to descriptor

@PastaPastaPasta

Should I update release-notes.md as well ?
test/functional/wallet_address_types.py is missing here


Move Row Up/down buttons bring the app to page 1 of the book when using the filter

Related to #37
Up/down scroll button brings the app to page 1 of the book.

Go to Chapter 10 of the book using the filter.
Click on the Up/down button, the app lands up the first chapter of the book.

2nd part of the issue:
After the app lands on the first page, Save button gets enabled, however no edits have been made.

Verified in Alpha-24. The issue with the Up/Down button has been fixed.
@klappy The second part of the issue- Save button getting enabled- This is still happening when the Up/down button is clicked.


Diversity through free speech

The way the  ´free speech´ is basically defined ( https://xkcd.com/1357/ ) , leaves it open for abuse, as we have seen happen in different communities.
We have seen people being fired from their jobs, shows being cancelled etc. This is mob rule mentality which is now being rationalized in a way  that it seems just as valid as any other view of free speech or activism.
We are living in times where society is under pressure to change and be more equal, accepting, understanding. This shift in attitude gives minority groups considerable amount of social power which can be abused if it is focused on individual or small group of individuals, even if they would be part of so called "privileged group".
Guidelines, code of conducts should be worded in a way that they cannot be abused instead of rationalizing kneejerk reaction and mob rule mentality, as it has been done in ´social justice movement´ , where outing people, contacting employers and getting people fired for jokes about dongles,  has become acceptable way of  conducting conversation.
These kind of attitudes are divise and assume bad faith first IMHO.
Also they can have exactly the opposite effect on community, instead of creating diversity they can create oppressive environment.
In order for society and people to grow, they need room to grow.
That room is created by  not just free speech as a right, but right to be heard.

Exactly, free speech and inclusivenes also includes the right express a currently to an unpopular opinion. The CIAFWYWCOC I wrote emphasises this as well.

@Michaelfemdom thank you for sharing your concern. It is up to each community that adopts the code of conduct to make it their own and uphold it.
If you have any suggested edits to the template, please open a pull request and the community can discuss them.


Not obvious how to nest rules

It took me the longest time to figure out how to add "any/all" rules. I don't know how I hadn't already stumbled across option-clicking the plus sign before, but I hadn't. I didn't even realize it was possible at first and was going to ask for it as a feature request. (Note: this is all on me, not you! Your docs were clear and accurate; I just didn't know how to use the rule editor.)
A sentence like "option-click to add nested rules", or maybe even a screenshot demonstrating it, would be helpful to other clueless people like me. 🙂

Well, I wouldn’t say this is on you either — I’d blame Apple and their constant neglect of macOS for this. The UI component we’re discussing hasn’t received significant updates in ages I believe, including those that’d increase its affordance (it’s pretty absurd that a core functionality of the component is hidden behind a press on the option key). I’ll confess too that when I first used it in the Finder it took me way too long to understand this. But once you do, it’s an amazing piece of UI.

The user guide now links to an official Apple support article that deals with this. It’s a great intro to rule editors.


fix: improvements in handling Pipeline Run + Activities

for multiple builds on the same context + for the build controller code

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr-build
0a863e3974c3443ce0a20cf53addc9151efb51f3
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr-build
0a863e3974c3443ce0a20cf53addc9151efb51f3
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


docs(readme): Added suzukimain to examples

Add suzukimain to Example usage in Readme.

Looks great :+1:

Thank you!


add annotations like meanings to permissible values

It would be great to have ontology classes associated with many of the permissible values - but I think this is a big ongoing task rather than 6.1.1->6.2.0


Attribute error when building the scipy docs

My issue is about the scipy docs.
I am trying to build the scipy sphinx documentation. I managed to install scipy from source and successfully run the tests. However when running sudo make html, I get the following error:
Error message:
Exception occurred:
  File "ckdtree.pyx", line 164, in init scipy.spatial.ckdtree
AttributeError: type object 'scipy.spatial.ckdtree.coo_entries' has no attribute '__reduce_cython__'
The full traceback has been saved in /tmp/sphinx-err-2wsd1gah.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
Makefile:109: recipe for target 'html' failed

The full traceback can be found in logs-file.txt
System specs:

Sphinx-build: 2.1.0
Scipy: 1.4.0
Numpy: 1.16.4
Cython: 0.29.7
Python: 3.6.7
OS: Ubuntu 18.04.2 LTS x86_64

I've never seen that particular issue. It looks like you're picking up the wrong SciPy or NumPy install though:
RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject

please check that you're using the versions you think you are (e.g. if you did an in-place build, is the build dir on PYTHONPATH?).
Also, never use sudo. Simply make html will do.

I've had similar errors from the scipy.spatial tests. They went away when I upgraded to Python 3.7

okay, this is not a bug I think - closing. thanks all

I can reproduce this on CircleCI:
https://circleci.com/gh/scipy/scipy-sphinx-theme/12
No idea why it's happening, but I'm going to resort to building SciPy from source instead of pip installing then building the docs.


Is a new boot2docker .iso required for each minishift update

The first thing that happens after every minishift update is that a new boot2docker is is pulled down. Is this .iso required to be versioned with minishift, or could just reference a concrete boot2docker version and maybe be split into 2 repositories?

Yeah that makes much more sense.

We are trying to do this as part of https://github.com/minishift/minishift/issues/134.

This is fixed now with https://github.com/minishift/minishift/commit/87aace40f322224a76fc39b606b94aeb23bb7b59


fix: icon not set when adding bookmark to iOS home screen

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/21064
PROPOSAL: https://github.com/Expensify/App/issues/21064#issuecomment-1597561421
Tests

Navigate to https://new.expensify.com/ in iOS Safari
Tap on share icon from toolbar
Select Add to Home Screen option
Tap Add on the following screen
Verify Expensify icon that gets added to Home Screen
Click the icon bookmark just added from Home Screen
Verify that it open https://new.expensify.com/ in iOS Safari
Repeat 1-7 on Android Chrome.

[x] Verify that no errors appear in the JS console

Offline tests
QA Steps
Same as test

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

N/A

Mobile Web - Chrome

https://github.com/Expensify/App/assets/117511920/cff9f286-4206-4c15-921f-e6374ac6a974

Mobile Web - Safari

https://github.com/Expensify/App/assets/117511920/36a587ff-4374-471e-9b95-b6267fd1a572

Desktop

N/A

iOS

N/A

Android

N/A

@eh2077 The icon for mWeb/Chrome added to the home screen is square instead of rounded.

untitled.webm

@mollfpr Thanks for checking it on mobile Chrome. But I can't reproduce it on mobile Chrome, see below video
https://github.com/Expensify/App/assets/117511920/13d3f354-5997-45fe-99c0-6bf8f7be5f57
From my emulator, the preview icon is round, see below screenshots

Dev
Staging

Did you use the icon provided here and rebuild(Cmd + c to exit the process and run npm run web again) the project?

https://github.com/Expensify/App/assets/25520267/bb0d7ed7-0b1e-4c4a-93c5-0919a3279552
Here's what I commented on the apple-touch-icon link, and it works. I also check on the real device have the same behavior.

That's so strange. I still can't reproduce it.
Below is my emulator setting

Do you test on the same branch of this PR? Or can you share the branch you're testing?
Let me setup another emulator using Pixel 5 and API 33 and try to reproduce it.

I'm checkout to this PR with GH CLI.

Still can't reproduce it on emulator of Pixel 5 API 33

@marcochavezf Could you help us here to check whether the icon on adding the page to the home screen is displayed correctly like on the staging? Thanks!

@mollfpr Would you mind testing with following changes on your env?

<link rel="icon" id="favicon" sizes="any" href="/favicon.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">

I still can’t reproduce it but I guess it's related to the legacy usage of rel="shortcut icon".
It looks like rel="shortcut icon" is not recommended for modern browsers and it's recommended to use rel="icon", see rel="shortcut icon" considered harmful and How to Favicon in 2023: Six files that fit most needs FYI.

https://github.com/Expensify/App/assets/25520267/50288d6f-11ba-459e-a6ff-4f69366ebdd8
@eh2077 It's still reproducing even after I clean up the project.

@mollfpr Could you update your Chrome and test with property sizes="any" added again? I had experienced other weird issues on outdated Chrome before. ChatGPT tells me that Chrome possibly reads icon from meta tag <link rel="apple-touch-icon"> if it can't find the proper icon 🤔 but I think, in this case, the Chrome should be able to find the right icon?

Friendly bump @mollfpr on https://github.com/Expensify/App/pull/21856#issuecomment-1617228769

Sorry for the delay! It's still resulting in the same.

ChatGPT tells me that Chrome possibly reads icon from meta tag  if it can't find the proper icon

Is there any information on what the proper icon is?
Although, the result in my phone is not too noticeable, and the icon on my home screen is not round like in the simulator.
https://github.com/Expensify/App/assets/25520267/e0e09e18-e35c-4a8d-b353-70c1b7126470
@shawnborton Could you help confirm if the icon in the above video for Android is okay? Where is previously the icon that shows in Android was the favicon.

@eh2077 Let's add test for mWeb/chrome too in the test case.

Added!

Friendly @marcochavezf

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/marcochavezf in version: 1.3.38-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.38-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


💬 [Question] Desired behaviour for invite button while in meeting

It was requested to add an "Invite" button in the new sidebar, to open a new mall talk. The main way to open new mall talks should be via the DreamMall button, so the idea was to show that to the users by simply opening that button.
But, when I'm in a meeting (= currently, on the table page), the DreamMall button shows options for the current meeting.
What is the desired behaviour when clicking "Invite" in a meeting?

Ask the user to leave the meeting first?
Render the create malltalk dialog in the button?
Something else?

Claudia is not comfortable with the design of the button

Different states:

in my malltalk
in a malltalk
in a project table
no meeting

From #2478
Invite Button in Sidemenü.
has two states:

Invite to own Malltalk (Einladen)
Create own Malltalk (Tisch eröffnen) -> Shows the user a Hint that he will leave the current Meeting

Clarify exactly what is to be implemented and how it works

Mein MallTalk -> Leute Einladen
Anderer Malltalk -> Eigener Tisch öffnen -> Popup Feld Warning -> Button eigener Tisch
Projekt Tisch -> Moderator -> Einladen
Projekt Tisch -> Kein Moderator -> Ausgegraut

closing in favor of https://github.com/dreammall-earth/dreammall.earth/issues/2666


Completion snippets for T::Struct and T::Enum

It would be nice if Sorbet had built-in support for some non-symbol-based snippets in completion requests. Two off the top of my head:

[ ] Snippet for T::Struct
struct<TAB>

could become
class ${1} < T::Struct
  ${0}
end

[ ] Snippet for T::Enum
enum<TAB>

could become
class ${1} < T::Enum
  enums do
    ${0}
  end
end

Fixed in #6216


[TVMC] Runner.py Updates

This PR does three things:

Makes hostname optional in run_module
Makes device mandatory in run_module
Changes the runner time measurements to be in milliseconds rather than seconds (with additional test updates)

@jwfromm @mdw-octoml @leandron @comaniac
Please let me know your thoughts :)

@comaniac, if you look at the full function, its already handling hostname=None and requiring that device is set. The change to the arguments here just more closely matches the actual behavior.

@comaniac, if you look at the full function, its already handling hostname=None and requiring that device is set. The change to the arguments here just more closely matches the actual behavior.

You're right. Yeah then it makes sense to adjust the arguments to align the actual behavior. Then please change the order accordingly and update the type in docstring.

Thanks @CircleSpin and @comaniac. This is now merged.


Add interview by uppy maintainer Artur Paikin

Hey @kvz, thanks for this submission! After looking through the interview, I don't think it's a great fit for this repo, because while it is an interview with a maintainer, the interview doesn't shed much light on the experience of being a maintainer. Ex. what are the processes, challenges, etc that they deal with? (Similar to my comments here: https://github.com/nayafia/awesome-maintainers/pull/32#issuecomment-410333274)
Gonna close this one out, but if you come across another interview that you think is a good fit, feel free to open another PR!


How to limit virtualenv file watches to prevent large workspace error

Discussed in https://github.com/microsoft/vscode-python/discussions/19523

Originally posted by ggydush-fn July 21, 2022
I have all of my virtual environments in a single folder (~/.virtualenvs/) and found that this causes the following issue in Vscode (even in an empty project):
Unable to watch for file changes in this large workspace folder. Please follow the instructions link to resolve this issue.

The logs show that the Python extension is watching the ~/.virtualenvs directory, but does it need to watch all files in these directories? When working on multiple projects, this can easily exceed the watcher limit (which I don't have much control over setting, as I'm operating on a remote machine).
Disabling the Python extension resolves, but am wondering if anyone else has come across this and knows a way around it? I've tried modifying Vscode's setting "files.watcherExclude" but that did not seem to have an effect.

Related: https://github.com/microsoft/vscode/issues/151827

@ggydush-fn Ideally the setting should help, I suggest to open a bug in https://github.com/microsoft/vscode/issues, it's possibly the same as https://github.com/microsoft/vscode/issues/151827.
As to what the extension can do, try a couple of things:

Do you have poetry environments? I think that's the only global watching extension does is that.
Try disabling Pylance extension which also does some watching. Set python.languageServer to Jedi.

Lastly, please provide the logs as mentioned in the issue template. Set python.logging.level to debug in User settings, reload window, then perform the steps to reproduce before providing the logs.

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

It contains information as to what and why we watch certain directories.

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


Add clean command

There should be a way to clean up the cache dir, without having to know where it checks out repos.

Released in v1.3.0.


using wagl out of a swarm context

I'd like to try wagl out of a cluster by using
docker run --net host --restart=always -p 53:53/udp --name=dns ahmet/wagl wagl --swarm "<IP_ADDRESS>:2375"

The problem is that every entry resolves to <IP_ADDRESS>:
 dig @localhost _web._tcp.swarm SRV

; <<>> DiG 9.10.3 <<>> @localhost _web._tcp.swarm SRV
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19899
;; flags: qr aa rd; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;_web._tcp.swarm.		IN	SRV

;; ANSWER SECTION:
_web._tcp.swarm.	0	IN	SRV	1 1 32770 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32772 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32769 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32768 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32774 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32776 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32775 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32773 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32777 <IP_ADDRESS>.
_web._tcp.swarm.	0	IN	SRV	1 1 32771 <IP_ADDRESS>.

;; Query time: 0 msec
;; SERVER: ::1#53(::1)
;; WHEN: Wed Dec 09 23:11:30 CET 2015
;; MSG SIZE  rcvd: 453

Any idea how I could circumvent that?
I know it's not really the goal of this project, but could there be a "mode" where wagl would actually use the container ip instead of the host ip ?

Hmm I cannot reproduce this by starting wagl like you mentioned. Are you running dig inside the container or outside the container (it should not matter but anyways).
Can you please check the logs (docker logs -f dns) if there's some warning going on?
Also, can you please give the docker -H :2375 ps of your swarm cluster? If we're seeing <IP_ADDRESS>, there's either a parsing error going on or swarm is returning IP addresses of these containers as <IP_ADDRESS>.

@ahmetalpbalkan I was running dig outside the container.
Tried inside a container too, by using docker run --dns <IP_ADDRESS> but I might should have give the docker0 bridge ip ?
 You should not do that. :-) it is only for clusters.

yeah I know, that was the goal of this issue :) to know if there was a way to use it this way.
I could use the random load balancing feature you provide even outside a swarm cluster.

In fact, there is only a few places where the hostIp is used:
https://github.com/ahmetalpbalkan/wagl/search?utf8=✓&q=HostIP
Do you think it would worth it to make wagl a DNS for docker engines too?
I can totally see a use case even without a swarm cluster.

Will this be any different than container linking (docker run --link)? It already does the same thing for containers on the same host.

Also there's not much we can do, if docker API gives us <IP_ADDRESS> as the address, that's it. I wouldn't prefer adding such an IP resolving feature simply because (1) wagl is not designed for single host (2) doing load balancing on a single host is highly unusual (3) there's no easy way workaround to this, and it will probably defeat minimalism aspect of wagl, this is not intended to solve everything. :)

I definitely agree it does not worth the complication for wagl.
but let me still discuss the advantages :) :
links are not compatible with networking (and soon to be deprecated).
Using docker-compose, links can lead to circular references, avoiding some configs.
links are static: once a container is dead, the resolved ip is wrong for other containers.
single host balancing might be unusual, but it would allow to scale a nginx fcgi backend pool very easily (f.e).
I'm not sure, but what I proposed was simply to replace the HostIp with the container.Ip, if you enabled wagl with --single-host f.e.
Anyway, that was just my 2 cents :)
I definitely understand that you have no plan to implement that, I was just wondering if what I said made any sense.
Thanks!
Flo

@docteurklein if you send a pull request, we can discuss. :)

Closing due to inactivity.


[Space] Gasless research

Will this be research and proposal on the solution or the actual implementation of the gasless flow?

https://www.notion.so/matterslab/Solution-for-Gasless-Transaction-e3be89aa6ead44d0aa26edae2acaa484

There will be a release of it, so close the research ticket. Feel free to reopen.


updated references to "mix.publish"

the "publish" function was replaced by "copy"
reference here: https://github.com/laravel/elixir/commit/b6d59b9f68978224064964a75a7639f95aa2eeee

Thanks again.


Add libsecret to LD_LIBRARY_PATH

Description of changes
Adds libsecret to the LD_LIBRARY_PATH of azuredatastudio.
Before, I couldn't connect to my company's Microsoft SQL Server, for azuredatastudio would error out with libsecret-1.so.0: cannot open shared object file: No such file or directory. This fixes this behavior, and I'm now able to connect without any trouble.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks!
Could you please check the convention for commit messages and adapt your commit accordingly?

Thank you for your time! I think my commit message is okay now

@xavierzwirtz everything okay with this PR?

I'm using dbeaver now, it works out of the box


OCPNODE-2339: Add PKI field to (cluster)imagepolicy

Add PKI to clusterimagepolicy with DevPreview featuregate SigstoreImageVerificationPKI.
This field allows verification of image signature created by cosign BYOPKI feature.
The enhancement: https://github.com/openshift/enhancements/commit/3b62d2f84f603e04f566236a33bccd799ba4f7ae
hold this PR before https://github.com/containers/image/pull/2579

/test all

/test verify-crd-schema

/test integration

/test all

/test verify-crd-schema

/test integration

/test integration

/test integration

/test integration

/test integration

/test integration

/hold

@JoelSpeed could you review?

/test integration

/test integration

@JoelSpeed could you help take a look? I am not sure the integration test failures: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_api/2088/pull-ci-openshift-api-master-integration/1865931550843998208

/lgtm
/override ci/prow/verify-crd-schema
New required fields are within an optional struct, so are valid. This is an error in the detection.


anchor build error

❯ anchor build
[2024-11-18T10:30:44.126522000Z ERROR cargo_build_sbf] Failed to install platform-tools: HTTP status client error (404 Not Found) for url (https://github.com/anza-xyz/platform-tools/releases/download/v1.42/platform-tools-osx-x86_64.tar.bz2)

It seems that osx-x86_64 is no longer provided since v1.4.0?

Already mentioned here: https://github.com/anza-xyz/platform-tools/issues/83
But I'd like to second this -- can support be added again? There are quite a large number of us still on intel macbooks and the download code is buried in the anchor scripts. I was able to replicate the scripts fairly easily in my fork, however changing the URL in anchor itself to locally point at my fork has proven unsuccessful.
Happy to open the PR myself if it'll be approved.

Hi I have the same issue, trying to build a project but everytime shows the error
2024-11-19T17:33:06.412763000Z ERROR cargo_build_sbf] Failed to install platform-tools: HTTP status client error (404 Not Found) for url (https://github.com/anza-xyz/platform-tools/releases/download/v1.42/platform-tools-osx-x86_64.tar.bz2)
And I notice the binaries for intel osx are no longer in the repo, @trezm I saw your repo, but not sure what package and what file I need to change to point to your package, could you add some instructions please?
Thanks

Totally fair, I finally got the whole thing working locally, but you have to trust my personal fork a bit!

Clone https://github.com/trezm/solana
Install it (scripts/cargo-install-all.sh)
Run anchor build as normal -- it should pull from the releases on https://github.com/trezm/platform-tools instead (which has the macos-x86_64 version)!

Thanks a lot! I temporary "fix" the issue by downgrading solana-cli to v1.18.17 as it points to the version 1.41 of the platform-tools (which had the binaries for intel mac osx). I'll try to update again to v2.0 and use your fix, thanks a lot!

We've re-added the runner for x86 Macs. The binary is now available again in platform tools version v1.43.


Template ufs-srw-public-v2 can no longer be installed

Describe the bug
Template ufs-srw-public-v2 explicitly requests<EMAIL_ADDRESS>but that version has been marked as deprecated in spack, which means that the installation fails.
We can of course update the template to use<EMAIL_ADDRESS>but then it is strictly speaking no longer the ufs-srw-public-v2 configuration. Arguably, there will be no difference between those two zlib versions, but how pedantic do we want to be?
EDIT: Ideally, we would create ufs-srw-public-v2.0.1 and mark ufs-srw-public-v2 as deprecated?
@kgerheiser Thoughts?
To Reproduce
Try to install an environment using template ufs-srw-public-v2.
Expected behavior
Installation successful.
System:
Tested on Cheyenne, but it happens everywhere.
Additional context
Add any other context about the problem here.

Update: same goes for<EMAIL_ADDRESS>- replaced by 1.6.37


Browser extensions in Webstore are out of date

The browserpass page shows the latest version as 1.0.5.: https://chrome.google.com/webstore/detail/browserpass/jegbgfamcgeocbfeebacnkociplhmfbk
But the latest version is 1.0.6.

Same goes for Firefox - we cannot do this without @dannyvankooten.

v2.0.0 was just released in Chrome and Firefox webstores!
These are the new extensions, rebranded as Browserpass - Community Edition, so you have to remove the old ones if you still have them installed.
Enjoy 🙂

This is the most satisfying thing, seeing all of these issues being resolved 🙂 Thanks for the release Maxim!
(As a side note, we should probably still take care to maintain backwards compatibility with the old extension, since a lot of people will still be using that)

I made the host app incompatible with the old extension, and I did it on purpose, as there is no excuse not to upgrade frontend if one is upgrading the host app to v2 😛
It is a one-time action anyway, future updates will be pushed via Webstore automatically. Furthermore, we have the chrome-policy.json back, meaning that Chrome extension is installed automatically from the store (no luck for Firefox... and for Windows users, for now - #163)

I don't know, I just don't like the idea of it silently failing because of an upgrade (many people won't even be aware of the new extension name).
I assume it just fails with Error talking to browserpass host now, right? My concern is primarily that people will be filing hard-to-debug errors caused by the upgrade that just say "it doesn't work". Though I guess we could figure it out if they manage to report their versions correctly 🤔
I guess there's not much we can do about it anyways, it's not like we can change the old extension (to display an appropriate error) 🤷♂.
Speaking of errors: I know this is getting off topic, but how about reporting more verbose errors to the UI in general? 🙂

I think it is worth the risk, it's a temporary inconvenience that has lots of long-term benefits for everyone. But the concern is valid, and I hope it will be at least partially handled by this ticket with catchy title that I'll leave open for a couple of weeks: #165.
Speaking of errors handling, let's discuss it separately - in #164.

Thank you very much Maxim! The new shortcut behavior seems acceptable too.
The "Find more username fields" feature is welcome and seems to improve some sites. Thanks! Unfortunately it's still broken on citi.com, which is only a very minor inconvenience.

@tanderson92 I fixed the citi.com support in https://github.com/dannyvankooten/browserpass/commit/4cf2dae69bbcfd83700fd3889470ae1ef57bf424 - will be a part of 2.0.1 release 😉
Note for everyone: do not hesitate opening new issues for sites where browserpass doesn't fill passwords in, sometimes we cannot do anything about it, but sometimes it is really useful, investigating citi.com actually brought up two major improvements to the detection algorithm, which will improve other websites too (details in the commit message for those of you who are interested).


GeoZarr to Support 2D RGB and Multi-Dimensional EO Data

Context
Consider an Earth Observation (EO) scene raster made available as a COG or via a Map Tiling Service:

COG Encoding: COGs typically encode 2D raster data with a single band or RGB, using image layers for each band (Note: There is no standard way to interpret multi-band GeoTIFFs beyond RGB). The COG URL provides access, and the scene footprint can subset the scene from a larger COG coverage.
Map Tiling Services: Similarly, Map Tiling Services allow straightforward scene extraction from a URL by using layer endpoints and bbox subsetting.

Concretly, OpenLayers can display easily a RGB thumbnail/visualisation on a map.
Considerations for GeoZarr

RGB Display in GeoZarr:

GeoZarr should enable encoding 2D rasters in an RGB format in a standardized way. The idea is that coordinates (latitude, longitude, and bands like RGB) are explicitly named to facilitate their interpretation. This way, a client wouldn’t need to deeply parse all metadata to understand these dimensions. Additionally, it could be useful to indicate explicitly that this data is of type 2D RGB in a main attribute so that users can easily identify it.

Multi-Dimensional Data Support (3D/4D+):

GeoZarr already allows encoding 3D and 4D+ rasters, with dimensions like time, wavelength, and altitude. There should be a syntax convention (that can be used within GeoZarr or in any metadata format such as STAC) to express a GeoZarr subset without requiring to parse all metadata (e.g. [time=1],[altitude=2])

For 3D time series, there should be a convention for the time dimension, and probably a type or requirement class advertised for such  GeoZarr.
For other 3D+ data, there should be a convention for a client application to express a visualisation/preview by identying the subset for R, G, B.

Variable Identification for Multi-Layer Data:

Similar to formats like NetCDF, GeoZarr may contain multiple data variables at the same level. A standard method for identifying these variables within GeoZarr is needed, especially in STAC items, to specify how to retrieve and display the data effectively.

This is only very basic initial thought, but I think that the OGC GeoDataCube SWG may be working on similar challenges.

Glad an equivalence between GeoZarr and STAC Catalogs is being proposed. It's common for STAC Collections to contain STAC Items with different CRSs. Do those working on the spec think this is within scope? Right now I only see examples online for resamping every raster to a common CRS before saving to Zarr, like https://earthmover.io/blog/serverless-datacube-pipeline/.
this section of the spec makes me think maybe this is within scope?

If multiple Array Variables share heterogeneous dimensions or coordinates, a primary homogeneous set of variables MUST be located at root level, and the other sets declared in children datasets.
https://github.com/zarr-developers/geozarr-spec/blob/main/geozarr-spec.md#geozarr-dataset

I would love to be able to turn STAC Collections or Catalogs into GeoZarrs with two geospatial index levels, one common CRS for all rasters that indexes each raster by it's extent on the common CRS. and another index level that is particular to each raster group that shares a common CRS.
My use case is inference on rasters and georeferencing the results. I might want to load a GeoZarr, filter rasters that intersect an area of interest using the top level CRS, run model inference on individual rasters and then use each rasters's individual CRS for georeferencing the model results. I'd like to avoid reprojecting all the raster pixels to a global projection throughout this process since it is an expensive operation and compromises on equal area.
I hope there is a way to handle the above with GeoZarr, while also getting the benefits of Zarrv3 sharding for performant data loading and cloud storage.

It's common for STAC Collections to contain STAC Items with different CRSs.
I expect the same with GeoZarr when simply converting a "product" (scene) to that format. Resampling would be applied to obtain aggregation (datacube), analysis-ready data, or to generate Level 3+ data.

Your idea seems very interesting but quite challenging. As a first step, I would simply aim to expose and access some typical product types in STAC, taking into account bands and extra dimensions.


Does runInLinuxVM really need "kvm" in systemFeatures?

I'm trying to build docker images on a hydra build server that doesn't have KVM support; the build job is never scheduled as "kvm" is propagated as a requiredSystemFeature via dockerTools.buildImage.runAsRoot: https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/vm/default.nix#L302
One year ago the same build server was successfully building .ovf artefacts, which I assume used runInLinuxVM; I suspect that qemu falls back to emulation if missing KVM support.
I can successfully build the docker layers locally after removing all kvm kernel modules and removing /dev/kvm. This was surprising to me as I was under the impression that the systemFeatures came from here: https://github.com/NixOS/nix/blob/fb35aaa42295940ca8dbfef17b081729636f9775/src/libstore/globals.cc#L101
Nevertheless, this local test along with the previous year's successful .ovf build leades me to believe that the KVM requirement may be superflous. Is there some way I can work around this without patching build-support to remove the requirement?

You can probably do another lib.overrideDerivation on the result of runInLinuxVM to override requiredSystemFeatures and args. The reason why kvm support is needed (from what I've seen) is due to the fact qemuCommandLinux [1] will end up calling -enable-kvm [2].
[1] https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/vm/default.nix#L195
[1] https://github.com/NixOS/nixpkgs/blob/master/nixos/lib/qemu-flags.nix#L19

Thanks for the helpful suggestion.
I tried this, and could indeed remove kvm as a requiredSystemFeature from the top-level derivation returned from dockerTools.buildImage.
Unfortunately that derivation still depends on a separate layer as the call to runInLinuxVM is nested [1]. I don't know of a way to override any "deeper".
Would it make sense to make the usage of kvm optional and configurable? I could produce a patch given some guidance on the user interface.

If you were to fix it without touching nixpkgs, you can copy the file over and fix the runInLinuxVM call there while redefining runWithOverlay = (import ./file.nix {}).runWithOverlay;.
Patching it would probably need an arg (something like enableKVM) propagated throughout all the calls which defaults to true to maintain the current behavior.

Again, thanks. I'll try to use this approach as a temporary workaround.
It seems [1] that @edolstra added kvm as a requiredSystemFeature almost a decade ago. I wonder if anyone remembers why. If there are no further insights then I plan to return with a patch that retains the current behaviour by default.
[1] https://github.com/NixOS/nixpkgs/commit/3cdc3c4abe820380ed0f66a87123d58589f67cf1

It seems [1] that @edolstra added kvm as a requiredSystemFeature almost a decade ago. I wonder if anyone remembers why.

Well, if a builder set contains both KVM-capable and non-KVM-capable ones, the performance benefit of using the former is clear.

Well, if a builder set contains both KVM-capable and non-KVM-capable ones, the performance benefit of using the former is clear.

Yes, no argument there - I still want to use KVM where avaliable. I'm questioning if kvm in requiredSystemFeatures is needed for kvm support. I suspect oppourtunistic kvm use with a graceful fallback is possible. I'm probably missing something.

I'm questioning if kvm in requiredSystemFeatures is needed for kvm support.

I don't think Nix has support for picking KVM-capable builders if they exist and ignoring the requirement otherwise.

Right, I'm making the assumption that the results are identical for emulated vs kvm; this may not hold in the presence of bugs so I'm behind making this an explicit builder option that changes the output hash. I'd lose the oppourtunistic usage of kvm, but it's a reasonable trade-off for better determinism guarantees.
I've just tested removing the requiredSystemFeature on hydra via importing a customised build-suport/docker, like so:
  runWithOverlay = x: lib.overrideDerivation (runWithOverlay' x) (a: { requiredSystemFeatures = []; });

And it works, so I'll be back with a patch. Thanks to all for the input.

@christian-marie did you get anywhere patching this ? I'm also trying to build docker images without kvm and found your ticket, also hit the same wall I guess..

@christian-marie Can you show your patch here? We'd also like to make use of this.

This is quite annoying if you are using dockerTools.buildImage.runAsRoot in a pipeline that is being run on Travis. Apparently a few years ago everything worked fine, now it just fails due missing server with KVM.

Patching it would probably need an arg (something like enableKVM) propagated throughout all the calls which defaults to true to maintain the current behavior.

I believe either this issue should be reopened or a new created to track that this should eventually be fixed. Perhaps you should have to explicitly set some flag but the end result should be that you can use runAsRoot without requiring KVM on the machine.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-to-run-chown-for-docker-image-built-with-streamlayeredimage-or-buildlayeredimage/11977/1

I also think this should be reopened

I'm happy to reopen this in the hopes that you all get a response.
The patch I mentioned is long lost and isn't particularly useful except to get a virtualised build working if you're willing to maintain a forked build-suport/docker. If you want to go down that road the clues here and code snippet should be enough to reproduce the hack, it was pretty much just the snippet in the right place.

In case anyone bumps into this trying to build docker images without support for kvm, I just created an overlay that implements @christian-marie 's suggestion at https://github.com/mzabani/codd/blob/7b6502b7b8e6d4a9c238f9c235cc105eca5ab5e4/nix/docker/no-kvm-overlay.nix
It's hacky, as the comments in the file say.
Also, I tested both with and without kvm enabled and verified that md5 sums of the results differ (at least for my project), so apparently it would really have to be an explicit flag.

Is it possible to add an additional command like dockerTools.buildImageWithoutKVM, then that would help solve the issue? Maybe expand dockerTools.buildImage with kvm = false; option so that we can apply it like that?

Does this problem also apply to the other container formats too?


microk8s on Ubuntu with raspberry 4 hardware (ARMv8)

I can't make your hello-world run on Ubuntu 20.04.1 LTS with microk8s running on raspberry Pi 4b model (ARMv8)
The pod get created but then "CrashLoopBackOff" forever.
microk8s is using containerd, is there some incompatibility with docker engine for which your image is probably tested/running ?

What do the kubectl logs show?

I get the "Hello from Docker! ..." when doing kubectl logs, so I suppose it means it works as designed.
From what I understand, the kubernetes pod is restarted because the docker container exits every time it completes its output which forces the pod to restart the container and here we are with a endless "CrashLoopBackOff" status. Is there an option to run the hello-world container as a service and not exit every time ? Cheers

Is there an option to run the hello-world container as a service and not exit every time ?

No, the hello-world image just prints a message and exits. If you just want a "dummy" service, then something like docker run -d bash sleep 100000 or docker run -d busybox httpd -f or even the nginx image should work.


Extend marker withrawals

This PR allow any funds to be withdrawn by a WASM smart contract from a marker account (not just the marker denom funds).
Hold until the following PR is merged in Provenance.
https://github.com/provenance-io/provenance/pull/193

Blockchain PR was merged.


Issue/383

Motivation
Which issue does this fix? Fixes #383

updated models to match API response
GetSyncAsync method updated
added support for dynamic resolution (otherwise JObject is returned)
fixed tests
adjusted some method descriptions

Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[ ] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
Initialize sync in your sample project, perform some changes, then get the token from initialization and run GetSyncAsync both with and without TypeProvider registered.

the model differed from the API response format, without mapping implemented to account for that. I adjusted the model to match sync API response, content item information is now nested in Data property.
a strongly typed item can be retrieved from newly introduced StronglyTypedData property, as long as a TypeProvider is registered and can found a suitable model. the property is null otherwise


[fix] killSession not working, #84

fix #84
The problem is caused by the use of unawaited, I think it is because the killSession request will not have any response and the author wants to run killSession and then use _handleSessionDisconnect to reset the local state immediately.
Unfortunately, the actual situation is that the local state is reset before the killSession request is sent out, so a valid killSession request cannot be sent successfully.
Future killSession({String? sessionError}) async {
   ...
   unawaited(_sendRequest(request));
   await _handleSessionDisconnect(errorMessage: message, forceClose: true);
   ..
}

To reduce the impact on other places, I just add a delay to ensure that the killSession request can be sent out before the _handleSessionDisconnect reset local state.
unawaited(_sendRequest(request));
// Avoid starting `_handleSessionDisconnect` before completing `_sendRequest`, which will cause the dapp to not be disconnected from the wallet, https://github.com/RootSoft/walletconnect-dart-sdk/issues/84
await Future.delayed(const Duration(milliseconds: 100));
await _handleSessionDisconnect(errorMessage: message, forceClose: true);

Hope to approve this PR, please let me know if there are any problems 🙏🏻 Thanks so much

I have tested on my android and ios device.
btw I know it's just a workaround solution.


Consolidate type-related helpers in new types package.

This collects type-related helpers in the registry tool into a new types package (internal to the tool). Along with chipping away at core, it reduces duplicate name-to-proto mappings previously in core/print.go and the patch package down to one.

@theganyo ack #887


Introduce react-query + use it to discriminate program version in the creation wizard

about react-query
I've been looking to introduce react-query into the codebase because it's super useful. I ran into a case (fetching and caching the programVersion of a Realms program) that wasn't covered by existing query stores, and thought it would be a good chance to do so.
By using react-query we can manage queries and caches on a pubkey-by-pubkey basis without needing to maintain a monolithic data store. react-query will also give us a really easy API for expressing how long queries should be cached or made stale.
feature
The "Custom Program ID" input now has a message displaying the version of the input program

Here's what happens when I put in a random pubkey:

(there is also a loading message while fetching, but I was not fast enough to capture it).
implementation notes
This is implemented using a useProgramVersionByIdQuery hook. While results are only cached for 5 minutes, they never expire, and this hook can be reused anywhere else in the app where we would want to get programVersion given a program id.
I intend to use this same hook in order to conditionally display form steps based on the program version.

I fixed the linter issue that Vercel was complaining about in previous checks and am not sure how to make it re-check.

Nice work, looks good to me we need to wait for @SebastianBor to look


Add new builder API and support customizing rationale dialog theme

#174
@samtstern What do you think of this PR? I'm using our new builder style to add the theme option. If you think the idea is good, I'll add documentation and all that good stuff and prep this PR for merging.

@SUPERCILEX this is a nice API but I am wary of making a breaking change for this (relatively) minor feature request of theme changing.  The API right now is simple and has a lot of users.
Is there anything else you think we'd add to the API in the future if it was Builder-style?

@samtstern Nope, I can't think of anything. However, here's my reasoning:

requestPermissions has way too many parameters: a common limit I've seen is 3 and then you consider a different way of passing in parameters. In our case, we can go up to 5 plus the varargs one which is unlimited. When you consider adding yet another parameter (now 6), things get tearfully messy.
We already have way too many int parameters: the signature = requestPermissions(Host, String, int, int, int, String...). Adding the theme int turns those 3 into now 4 ints in a row!
Overloads: it's getting ridiculous. To not break backwards compatibility, we need to add at least another 3 overloads. If we want to improve flexibility, we'd need to add 6 to the existing 6!
Current API limitations: a minor pet peeve of mine has been the inability to pass in a string resource int for the rationale and vice versa for the yes and no buttons. The new builder has String/int overloads for each of those options.
I don't see any reason to release a v2.0 anytime soon. I was basically thinking we could leave people a year or more to migrate away from the old API which should be more than enough time to migrate away from a method that's only used once per set of permissions.

@samtstern Maybe I've changed your mind? 😄 If not, we need to decide which overloads to add.

Ok I agree with you completely, I hate all the overloads and they're not scalable.
So maybe let's take a middle-road approach:

Keep supporting the EasyPermissions.requestPermissions(context, rationaleString, requestCode, perms) method call indefinitely.  That's the most common use case (99%) and it doesn't require too many overloads.
Introduce a new method: EasyPermissions.requestPermissions(PermissionsRequest) which uses the builder.
Mark all other overloads of EasyPermissions.requestPermissions() as @Deprecated so this can be just a minor version bump and won't break anyone.

@samtstern I like it, that's a perfect compromise! 😄

@SUPERCILEX awesome!  I think all that's left is the README, right?

Sweet! (Thanks for reminding me, I'd forgotten 😄)


Cannot disable vg-dash default logging

Can you provide some info please?

vg-dash uses dashjs and dashjs logs every event by default in browser console. So I looked into the code and found now way to disable logging of dashjs.
in vg-dash you are using:
// dash.js version 2.x                                 player = dashjs.MediaPlayer().                                 player.initialize(API.mediaElement[0], url, API.autoPlay);
dashjs require this to disable logging:
player.getDebug().setLogToBrowserConsole(false);
Therefore I created a PR too. you can have a look to it.


Collaborative wallet:Transactions are not visible in view more section.

Verified this issue on keeper app v 1.1.6(248)


[5.5][CSSimplify] Fix warning check to account that "from" might be less optional than "to" type

Cherry-pick of https://github.com/apple/swift/pull/38011

Explanation:

While checking whether compiler needs to produce a checked cast warning,
account for the fact that "from" could be less optional than "to" e.g.
0 as Any?, so the difference has to be stored as a signed integer
otherwise it's going to underflow and result in a crash or infinite
recursion in the diagnostics.

Scope: Expressions with coercions to optional types where source type is less optional.

Main Branch PR: https://github.com/apple/swift/pull/38011

Resolves: rdar://79523605

Risk: Low

Reviewed By: @hborla

Testing: Regression tests added to the suite

Resolves: rdar://79523605

@swift-ci please test


Support for GRPC services

I'm creating a system that is composed by multiple grpc services and I wanted to use x-ray to observe them.
Currently, as far as i noticed, there is no support for GRPC services (besides the one available for asp.net core applications). At the same time, on the client side, when setting up the http client, you can attach the x-ray handler.
This causes the odd behavior that a faulty request to a service is marked successful in the service but faulty in the caller. I suspect this is due to GRPC services always returning 200 but the client detects the fault when deserializing the response.

@Kralizek thank you for the feature request. You are correct that we currently do not support instrumenting gRPC clients, and it is not currently on our roadmap to do so. We are always open to pull requests if you'd be willing to contribute. AWS is also working on the AWS Distro for OpenTelemetry, which is a unified set of SDKs to collect all your traces and metrics. The .NET OpenTelemetry SDK supports gRPC instrumentation along with many other libraries. You can get started here if interested: https://aws-otel.github.io/docs/getting-started/dotnet-sdk/trace-manual-instr

@Kralizek
I have found the workaround to solve the problem, if you have distributed microservices, you can implement a middleware for each like this:
`        public async Task InvokeAsync(
HttpContext context,
IContextAccessor contextAccessor)
{
        var request = context.Request;
        var requestContext = contextAccessor.RequestContext;
        var xRayRecorderEntity = AWSXRayRecorder.Instance.GetEntity();
        if(contextAccessor.RequestContext.OperationId == null)
        {
            contextAccessor.RequestContext.OperationId = xRayRecorderEntity.TraceId;

        }
        if (requestContext != null)
        {
            xRayRecorderEntity.TraceId = contextAccessor.RequestContext.OperationId;
            if(requestContext.CurrentId != null){
                xRayRecorderEntity.ParentId = requestContext.CurrentId;
            }

            var parentId = requestContext.CurrentId;
            requestContext.ParentId = parentId;

            if (requestContext != null)
            {
                requestContext.CurrentId = xRayRecorderEntity.Id;
            }
        }

await Next(context);

    }`

So every microservices dosn't found the header in http request, and recreate a istance of _recorder, but you can manipulate it, and set manually the traceId and parentId, then the result is the same:

Off course you can manipulate directly the http header and solve it, but this is a transparent solution.


chore(mocks): update generated mocks

Some mocks are outdated, this PR updates all generated mocks to latest version.

How didn't we catch this earlier?

Codecov Report
Attention: Patch coverage is 0% with 25 lines in your changes missing coverage. Please review.

Please upload report for BASE (shwap@f48353c). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

nodebuilder/blob/mocks/api.go
0.00%
9 Missing :warning:

nodebuilder/node/mocks/api.go
0.00%
9 Missing :warning:

nodebuilder/share/mocks/api.go
0.00%
6 Missing :warning:

nodebuilder/state/mocks/api.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##             shwap    #3767   +/-   ##
========================================
  Coverage         ?   46.33%
========================================
  Files            ?      314
  Lines            ?    17989
  Branches         ?        0
========================================
  Hits             ?     8335
  Misses           ?     8634
  Partials         ?     1020

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Advanced message format

Hello,
I'm new to Node Red.
I discovered your work which seems to meet my expectations when reading it but I find it difficult to put it into practice
I'm doing a test on a classic flow in order to see all the options on a message but I have errors so I decided to reduce the number of options in order to target the error.
I have this error: TypeError: Cannot read properties of undefined (reading 'content') and I don't see who generates it

My flow is :

My function is :

`const msg1 = {};
msg1.channel = '911259838544228402';
msg1.embeds = {
"title": 'Test de Message Evolué',
"description": 'Description du message',
};
return msg1;`

Thank you for your help in correcting my error.

Thank you for your quick response, however I do not understand the subtlety of this one.
I think it comes from my youth on Node Red and its environment but I can't fix what I started doing at all
I wanted to start with a simple message and then increase the difficulty with the insertion of images from my cameras etc.
Your work is excellent for a novice like me it is difficult without an example from start to finish but I do not despair

The most simple message with de discordMessageManager:
[
    {
        "id": "bbe6e51927b4a2c0",
        "type": "debug",
        "z": "4bde5831221f6bb2",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 770,
        "y": 60,
        "wires": []
    },
    {
        "id": "709a8f3baf4e320e",
        "type": "discordMessageManager",
        "z": "4bde5831221f6bb2",
        "name": "",
        "channel": "",
        "token": "",
        "x": 550,
        "y": 60,
        "wires": [
            [
                "bbe6e51927b4a2c0"
            ]
        ]
    },
    {
        "id": "ca2521669295ab88",
        "type": "function",
        "z": "4bde5831221f6bb2",
        "name": "",
        "func": "msg.payload = \"Hello there\";\nmsg.channel = \"111111111111111\"; // Your channel ID\n\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 340,
        "y": 60,
        "wires": [
            [
                "709a8f3baf4e320e"
            ]
        ]
    },
    {
        "id": "373865a8cf8a50c6",
        "type": "inject",
        "z": "4bde5831221f6bb2",
        "name": "",
        "props": [],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "x": 150,
        "y": 60,
        "wires": [
            [
                "ca2521669295ab88"
            ]
        ]
    }
]

Thanks for the help I even managed to embed
ok i woke up at 4:00 in the morning :)

On the other hand for the colored text it seems not possible visually on the phone but just on the app and the browser ?

Good evening
I still have a usage question.
Attached is my flow with the Home Assistant sensors.

What I have in discord mobile app

What i have in discord app windows

To integrate the sensors in my message I use payloads with the call services
But with your node the payloads do not pass! I don't have to write it right yet...
Not easy to start on node red because every day is a discovery !
`const msg1 = {};
msg1.channel = "911259838544228402";
msg1.payload = "Message de Node Red";
msg.message = "msg.message"
msg1.embeds = {
color: '#111111',
title: "Ephéméride du " & payload.date_jour & "",
description: "Description du message",
author: {
name: "le nom de l'auteur",
icon_url: 'https://i.imgur.com/AfFp7pu.png',
url: 'https://discord.js.org',
},
thumbnail: {
url: 'https://i.imgur.com/AfFp7pu.png',
},
fields: [
{
name: ":innocent: Saint du jour",
value: payload.saint_jour,
},
{
name: ":innocent: Saint de demain",
value: payload.saint_demain,
inline: false,
},
{
name: ":sunny: Météo du jour",
value: payload.meteo,
inline: false,
},
{
name: ":sunrise: Lever du soleil",
value: payload.lever_soleil,
inline: true,
},
{
name: ":first_quarter_moon_with_face: Coucher du soleil",
value: payload.coucher_soleil,
inline: true,
},
],
image: {
url: 'https://i.imgur.com/AfFp7pu.png',
},
timestamp: new Date(),
footer: {
text: "Envoyé par Node-Red --- " & time,
icon_url: 'https://i.imgur.com/AfFp7pu.png',
},
};
return msg1; `

I invite you to have this discussion on the discord server if you want.
In the last version of the package (3.2.2), all the input message is kept in the output. The msg.payload field is used by the node, and is a pattern within Node-red use payload for the specific input parameters for the node.
You can change properties to copy data outside of the msg.payload if you want.
I'm gonna close the issue.


missing fallbacks for UFO3 attributes

Some new UFO3 font info attributes don’t have a fallback in ufo2fdk.fontInfoData.
Running the script below in RoboFont 2 will print the missing attributes:
from ufo2fdk.fontInfoData import *

f = NewFont()
f.info.familyName = 'Hello'
f.info.styleName  = 'World'

for attr in sorted(f.info.asDict()):
    try:
        getAttrWithFallback(f.info, attr)
    except:
        print attr

openTypeGaspRangeRecords
openTypeNameRecords
openTypeOS2WinAscent
openTypeOS2WinDescent
woffMajorVersion
woffMetadataCopyright
woffMetadataCredits
woffMetadataDescription
woffMetadataExtensions
woffMetadataLicense
woffMetadataLicensee
woffMetadataTrademark
woffMetadataUniqueID
woffMetadataVendor
woffMinorVersion

openTypeOS2WinAscent and openTypeOS2WinDescent where RF issues
the rest should have some sort of a fallback in the infoData

added here (my fork) see https://github.com/typemytype/ufo2fdk/commit/82ae9f11e480ab710a2669de12a9fcb42ff25937

thanks!
(keeping the issue open until the change is merged)

This looks merged. Closing.


Alt right mapped to Caps Lock after mapping Ctrl to Caps Lock

Microsoft PowerToys version
"0.35.0"
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
Map Ctrl to Caps Lock

✔ Expected Behavior
Ctrl should be mapped to Caps Lock and Alt Right should be unchanged.
❌ Actual Behavior
Ctrl and Alt Right is mapped to Caps Lock.
Other Software
No response

@Offpics
What is your system language? I suspect your left alt is actually alt gr. Is it correct?

My system language is English but I use Polish keyboard. I can confirm that English keyboard works fine but after switching to Polish it's wrong.
Also it's actually alt gr.

@Offpics
When you press alt gr system sends ctrl(left)+alt(right). So we can not do anything about it.

@mykhailopylyp
That makes sense and explains everything. Thank you!

I had the same issue. With single mapping: CapsLock -> Ctrl (left) CapsLock would turn on randomly and I had to remap again to turn it off to lower the characters . I left control as is and mapped CapsLock to something I do not use - PrtSc, I use snipping tools anyway and it looks like I can use ALT-modified characters without an issue.

I need to use it a little more to confirm that 100%, but it looks promising.


Count set bits in an integer

Title : Count set bits in an integer

Language : Python

Directory : Bit Manipulation

Name : Neeraj Pratap Hazarika

[x] Hacktoberfest

[x] Contributor

Description :
Write an efficient program to count the number of 1s in the binary representation of an integer.
@prathimacode-hub please assign me this issue.

Issue assigned to @NeerajHazarika


Proper webapp

Setup new routing
Changed baseUrl & absoluteBaseUrl
Removed menu item about
Removed the info page
Fixed the garbage collection of games
Remove site generation
routing fix, removed site styling

No specific thing to look for. Just the regular bad code, debug code that should be removed, wierd or difficult code, typoes etc.
Might spot some wrong logic or mising paths or unused code, just a second pair of eyes going over it and spot things that i don't think about.

Right. In that case, I'd guess the webapp.js file is where there's most likely to be bugs. Could you briefly explain what the file is supposed to do? Or if you want to (and this might be more useful, actually): maybe we could schedule a short walkthrough on Monday where you go through the code and explain to me what it does?


Changes class 'filter' from main to nav

The example below states that the <nav> element has the class 'filter', but in the example before the class is on <main>

Wow, nice catch.


webapp: change '--tier' to '--plan'

The background is webapp team updated it in xplat this week, in order to push the sku concept, so azure-cli follow.
Because the sku's naming and type definition are quite confusing in SDK, so in code, i still keep the tier, and just do alias at the command layer.

//cc @kamaljit

//cc @derekbekoe @burtbiel @tjprescott


update-oracle set-oracle-data added tests for new owner

What kind of PR is this?:

/kind feature
What this PR does / why we need it:
This adds additional tests to oracles Dftx to ensure that the owner can be updated to a non-foundation member and that the new owner can update the data on the oracle
Which issue(s) does this PR fixes?:

Fixes #
Additional comments?:

/kind feature


Rewrote acting and assertion step of tests by Shouldly when using 'Assert.Throws'

Hi Martin,
Thank you for your great job, I like your work and your idea about implementing a unique version of HttpClient for making robust testing.
I used to use WebApplicationFactory for testing my APIs which is not comfortable for testing REST API.
In this pull request, I try to implement your testing in a consistent way by using the Shouldly library for rewriting asserting of throwing an exception
I wish it is useful for this repo.

Codecov Report

Merging #359 (178c5e7) into main (30bd9ff) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #359   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        16
  Lines         1128      1128
=========================================
  Hits          1128      1128

Flag
Coverage Δ

linux
?

macos
100.00% <ø> (ø)

windows
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Thanks!


Document migration path for upgrade from helm template to helm upgrade

Related Issues

Summary
Document a migration path for existing Rancher users who initially installed Rancher via helm template to permit upgrade via helm upgrade, as is default for Rancher v2.6+
Details
Via https://github.com/rancher/rancher-docs/issues/982#issuecomment-1850612486 and https://github.com/rancher/rancher-docs/pull/1066 the Rancher v2.6+ documentation now includes a section on the upgrade of Rancher via helm template for users who installed their Rancher instance via helm template, which was the documented method for air-gap installation in Rancher v2.x < v2.6.
The request here is to document the required steps for a user to migrate from using helm template to helm upgrade for the upgrade, such that there is a single consistent air-gap upgrade path going forward.
One way this would be possible is by performing a helm upgrade --install repeatedly, and adding the missing labels/annotations to each resource as noted by the helm output, e.g.:
$ helm upgrade --install -n cattle-system rancher rancher-stable/rancher --version=2.7.9 --set hostname=rancher.example.com
Release "rancher" does not exist. Installing it now.
Error: Unable to continue with install: PriorityClass "rancher-critical" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "rancher"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "cattle-system"

kubectl label priorityclass rancher-critical app.kubernetes.io/managed-by=Helm
kubectl annotate priorityclass rancher-critical meta.helm.sh/release-name=rancher
kubectl annotate priorityclass rancher-critical meta.helm.sh/release-namespace=cattle-system

... and continuing for each reported resource with missing labels/annotations until the upgrade is successful

@axeal Are the missing labels and annotations common enough from user to user that we could include a list?

@martyav Yes, that set of label and annotations will be the same for every resource created by the rancher helm chart (assuming it was installed with the release name rancher and into the cattle-system namespace, per the installation documention). The set of resources created by the chart may vary depending upon helm chart values, and the helm upgrade --install command will only return the error for the first resource upon which it fails and exits, so the user would need to run the helm upgrade --install multiple times, adding the label and annotations to each resource for which the error is reported, until the command runs without error.