Ecobee Integration breaks after random number of manual restarts of HA

Home Assistant release with the issue: 0.100.x
Last working Home Assistant release (if known): <0.100.x -- I think
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Integration: Ecobee
Description of problem:
Ecobee integration stops working after a manual HA restart and logs a message.  The only way to get it working again is to remove the entire ecobee integration from HA... Restart HA... Remove the app from the ecobee developer page.  Then add ecobee integration to HA again, add the app to ecobee developer page, and submit in HA.
2019-11-04 10:51:25 ERROR (SyncWorker_7) [pyecobee] Error while refreshing tokens from ecobee: 400: {'error': 'invalid_grant', 'error_description': 'The authorization grant, token or credentials are invalid, expired, revoked, do not match the redirection URI used in the authorization request, or was issued to another client.', 'error_uri': 'https://tools.ietf.org/html/rfc6749#section-5.2'}
2019-11-04 10:51:25 ERROR (MainThread) [homeassistant.components.ecobee] Error updating ecobee tokens

I also get random messages throughout the day such as...
2019-11-01 17:03:33 WARNING (MainThread) [homeassistant.components.ecobee] Ecobee update failed; attempting to refresh expired tokens

This doesn't seem to be an indication after a restart that the integration will break.  It's just a random message.  There is no rhyme or reason.  I manually restart HA for various configuration reasons.  Could be the next restart or it could be 10 restarts later.  Eventually the ecobee integration fails.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Configuration is done via integrations.  No configuration.yaml in HA
Traceback (if applicable): Not Applicable
Additional information:
I do not recall seeing this issue pre 0.100.x

I experienced the same and discussed this with @marthoc. Here's a summary of what he said:
It is because HASS got shutdown/restarted in the middle of or before the config entry could be updated with a new token. What happens is: we request an update, ecobee tells us our access token expired (it expires every hour) we call to refresh the access token, new access and refresh tokens get updated into the config entry

The resolution right now is to remove the integration and add it. But, he did indicate that the proper way for how that error will need to be handled is, we catch that error on a refresh attempt and then automatically unload the integration and create a notification that it needs to be reauthorized

@arsaboo if the tokens expire every hour what is preventing the component from refreshing the token on its own every 60 min and 1s?

The tokens are refreshed automatically. This error only appears when we restart HA during the refresh. I have been using the integration for a while now and restart my HA frequently, but have only encountered this error once.
I agree that it should be handled little more gracefully as it can happen and the dev is aware of it.

@edif30 - there are two things going on in your issue, one of which is normal:
Ecobee update failed; attempting to refresh expired tokens

That error is not really an error and in a future PR that will get changed to a debug level message; every 3600 seconds (1 hour) the ecobee access token expires, we try to update and fail, and we request a new token. Normal behaviour, and it happens every hour.
However, this error:
2019-11-04 10:51:25 ERROR (SyncWorker_7) [pyecobee] Error while refreshing tokens from ecobee: 400: {'error': 'invalid_grant', 'error_description': 'The authorization grant, token or credentials are invalid, expired, revoked, do not match the redirection URI used in the authorization request, or was issued to another client.', 'error_uri': 'https://tools.ietf.org/html/rfc6749#section-5.2'}
2019-11-04 10:51:25 ERROR (MainThread) [homeassistant.components.ecobee] Error updating ecobee tokens

Indicates that the refresh token is no longer valid, and the only solution is to reauthorize the ecobee integration (i.e. delete it and re add it and go through the process on ecobee.com again).
@arsaboo is correct, this error could happen because we unfortunately happen to restart during the process of updating Home Assistant's config entry with the new token and so on restart we don't have the new token. However, I've also found another "bug" in the underlying python-ecobee-api library related to retrying failed requests that could be causing this issue - the details are in this PR: https://github.com/home-assistant/home-assistant/pull/28296.
Bottom line is that soon, hopefully this issue will be 99% solved.

@marthoc Great thank you.  I am happy to test this out locally but looks like the PR has a merge conflict.

@edif30 the PR has been updated to fix some comments and the merge issue, so if you’d like to test you can! Much appreciated.

@marthoc is a removal and re-add of the integration required after adding in this PR?
EDIT: Just added the PR to my local.  Will report any issues.  🤞

@edif30 I don’t think re-adding the integration should be necessary, but perhaps you can let me know.

PR has been running and no need to do any integration changes.  I will keep an eye on things and let you know how this goes.  I've already had to restart several times today due to changes in my environment/testing and so far so good.

@marthoc I think it's been long enough to say that I am no longer seeing the random updating tokens error as well as I am no longer losing the integration from the token 1 hour expiration.  I am using the PR that you provided.  Seems to be working great!  I will continue to monitor.

Thanks for reporting! These changes should get merged into a release soon.

Hi @marthoc !
I wanted to check back with you on that PR? I see that you are close!
I've been watching this issue and that PR hoping that it would be approved soon. Very much looking forward to getting this fixed, especially with winter upon us.
Thanks!

Just a heads up, I integrated your commit into my local Home Assistant integration since it was totally failing out as described here. I'm no longer seeing these issues anymore in the logs. Seems pretty solid on 0.101.3 with those changes in:
#28296
https://github.com/home-assistant/home-assistant/pull/28296/files/aedbe9886cd8c99396c8fcd0062e7f74d867b0f3

I just ran into the logs being full of the expired token messages. @marthoc, do you know when the update was supposed to happen as I still see the messages in 0.103.0.

@ZetaPhoenix until this PR is merged the “problem” won’t be fixed. Sorry to all that I haven’t had a lot of time to work on this recently. But to be clear, the log messages don’t actually indicate a problem with the component.  If all you’re seeing is this error in the logs, but things are still working, then there’s no real problem.

Just wanted to clarify, I'm seeing the error with the logs and my ecobee integration hasn't been working since October. Is this an issue with log messages, or with the tokens/integration? If it's just related to log message spam then I may want to do more research.

Just wanted to clarify, I'm seeing the error with the logs and my ecobee integration hasn't been working since October. Is this an issue with log messages, or with the tokens/integration? If it's just related to log message spam then I may want to do more research.

Sounds like a problem with the token refresh. Problem seems to have a fix, just waiting for the PR to merge and a new release of homeassistant. You can merge the changes locally as others have done to fix it for yourself before a new release is made.

I also just got this error, hope the PR will be added soon to fix it.

So after removing and re-adding the integration it works fine for me. Even with restarts, however - I’m restarting the entire docker container. I’m curious - are you all calling the service restart?

So after removing and re-adding the integration it works fine for me. Even with restarts, however - I’m restarting the entire docker container. I’m curious - are you all calling the service restart?

Shouldn't make a difference for the integration given what the bug is

This problem seems to be happening more often and not just after restarting HA.  I have added the Ecobee integration 3 times in the past 2 weeks due to the token issue.  Two times it broke after a HA restart and one time is broke while running normally.  Almost like a response isn't being acknowledged on one side or the other.  Delete and re-adding the integration is the only fix that I am aware of once the token issue surfaces.

Same problem for me. Here are some logs I get, if it helps
2020-02-13 13:22:58 WARNING (MainThread) [homeassistant.components.ecobee] Ecobee update failed; attempting to refresh expired tokens
2020-02-13 14:23:56 WARNING (MainThread) [homeassistant.components.ecobee] Ecobee update failed; attempting to refresh expired tokens
2020-02-13 15:00:39 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.thermo is taking over 10 seconds
2020-02-13 15:00:51 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.thermo fails
Traceback (most recent call last):
File "/home/fidget/home-assistant/lib/python3.8/site-packages/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/home/fidget/home-assistant/lib/python3.8/site-packages/homeassistant/helpers/entity.py", line 459, in async_device_update
await self.async_update()
File "/home/fidget/home-assistant/lib/python3.8/site-packages/homeassistant/components/ecobee/climate.py", line 289, in async_update
await self.data.update()
File "/home/fidget/home-assistant/lib/python3.8/site-packages/homeassistant/components/ecobee/init.py", line 96, in update
await self._hass.async_add_executor_job(self.ecobee.update)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/home/fidget/home-assistant/lib/python3.8/site-packages/pyecobee/init.py", line 199, in update
self.get_thermostats()
File "/home/fidget/home-assistant/lib/python3.8/site-packages/pyecobee/init.py", line 173, in get_thermostats
logger.error(f"Error connecting to ecobee while attempting to get thermostat data: "
File "/home/fidget/home-assistant/lib/python3.8/site-packages/requests/models.py", line 897, in json
return complexjson.loads(self.text, **kwargs)
File "/usr/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
2020-02-13 15:24:53 WARNING (MainThread) [homeassistant.components.ecobee] Ecobee update failed; attempting to refresh expired tokens
2020-02-13 16:25:48 WARNING (MainThread) [homeassistant.components.ecobee] Ecobee update failed; attempting to refresh expired tokens

this just happened to me too - was troubleshooting/upgrading something else and, after a Linux update/reboot, I ran into this.

Just happened to me as well.  3 days into using ecobee integration.
2020-02-16 16:44:24 ERROR (SyncWorker_38) [pyecobee] Error while refreshing tokens from ecobee: 400: {'error': 'invalid_grant', 'error_description': 'The authorization grant, token or credentials are invalid, expired, revoked, do not match the redirection URI used in the authorization request, or was issued to another client.', 'error_uri': 'https://tools.ietf.org/html/rfc6749#section-5.2'} 2020-02-16 16:44:25 ERROR (MainThread) [homeassistant.components.ecobee] Error updating ecobee tokens

The same issue. I have to re-register Ecobee every few days. Frustrating...
The PR with fix  #28296 was just canceled due to inactivity

Yea I saw. I find it ridiculous that it was closed. I've seen PRs and Issues open for months. 1 month and this one is closed???  Hrmmm

I have this issue every few days as well.
One of the many reasons why I don't contribute to HA directly anymore. I
just maintain my custom components/cards. I've seen stuff like this happen
and other PRs get merged in so quickly that don't even have tests. Makes no
sense.
On Tue, Feb 18, 2020, 11:09 PM edif30<EMAIL_ADDRESS>wrote:

Yea I saw. I find it ridiculous that it was closed. I've seen PRs and
Issues open for months. 1 month and this one is closed??? Hrmmm
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/28531?email_source=notifications&email_token=AA7FQBMMUFMUD7ILFGFMFWTRDSWJPA5CNFSM4JIV45MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMGI5SQ#issuecomment-588025546,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7FQBM7CNTEC4Q73AN6KELRDSWJPANCNFSM4JIV45MA
.

Again all, sorry for the delay. This isn't on the HASS dev team, it's on me. I haven't had the time needed to push PR #28296 over the line. But, I think I can push a much narrower PR to fix the bug itself in the meantime. I've got the code written and will test tonight before opening a PR. Hopefully the devs can merge it while the refactor moves forward in parallel.

Thanks for the update @marthoc much appreciated. Looking forward to seeing this resolved.

Just for greater transparency regarding the issue raised in this thread, I'll explain why the ecobee integration keeps breaking for all of you.
Before config entries, ecobee authentication tokens were stored in a file called ecobee.conf that was stored in the Home Assistant config directory. On HA startup, the ecobee component would read the tokens from this file and use them to authenticate. The python library took care of retrieving the tokens from ecobee, storing them in the file, and (importantly) refreshing them and updating ecobee.conf with the new tokens if the old tokens became stale. If HA was shut down, on the next startup, ecobee.conf would contain the most recent tokens as the python library had been updating that file each time the tokens were refreshed.
Moving ecobee to using config entries meant that the tokens would now be stored in the entry itself, rather than in ecobee.conf. From a logic perspective, this meant that HA itself would now need to be in charge of refreshing the tokens and updating the config entry with any refreshed tokens. Easy enough.
However, the python library still contained logic as though it was responsible for refreshing tokens. On a failed API access attempt (because of connectivity issues or otherwise), the library would (without being prompted by the logic in HA) retry the failed call but also (and the origin of the bug) attempt to refresh the authentication tokens. If this succeeded, HA would go on using the correct tokens for the time being, but, when those tokens became stale (as they do every 3600 seconds/1 hour) the attempt by HA to refresh them would fail as the tokens in the config entry had been invalidated by the issuing of new tokens to the request made by the python library, and HA was presenting those stale tokens on the refresh request.
This explains why this issue is not cropping up for everyone - if you have no connectivity issues to ecobee (i.e. calls to the API don't fail), then the library would never independently refresh your tokens and this error would not happen.
I had previously refactored the underlying python library to fix this issue. The broader ecobee refactor was undertaken not only to clean up the component, but also to allow the component to refresh failed calls. For the time being, I think that bumping the library to the newest version (and fixing a few minor aspects of the HA refresh logic) should at least stop the error that is cropping up in this issue.

@marthoc thank you for your effort and the great explanation! Much appreciated!

@marthoc Please keep us posted on the new PR! Would be a relief to not having to deal with the ecobee issue again. Thanks for staying on top of it.

PR has been submitted: #32008. I was not experiencing this bug, but the integration appears to continue to work correctly with the changes to fix the bug in place.

I don’t like to keep posting in closed issues but can anyone confirm that upgrading to 106 has solved this problem?

Thanks again for getting this integrated. I have not yet upgraded to 106, but now that this, as well as a few Unifi bugs, have been integrated I will certainly do so soon and will report back.

It still happens on my 106.

I just had it happen on my 106.1

Alright we should reopen this issue. Can someone turn debug logging on for both the integration and pyecobee and then post the logs when the error happens?

I can confirm that this happens on my system as well on 0.106.2. I'm always afraid to restart out of the hassle of re-integrating.

@pashdown @yang3535 @FidgetyRat Since you have all confirmed that this is still happening for you, can you please help me debug? If you could turn on debug logging for the integration and for pyecobee, then send me your .log after the error happens, it would help me greatly to figure out what happens to cause the tokens to become invalid.

Welp, I've turned on the logging and killed and restarted HA several times, which used to always cause the problem.  It isn't happening anymore for me.  If it does, I'll try and capture some logs for you.

I’ve only seen this after numerous restarts on any version. I’m on 106.6
and do still see errors in log occasionally but only experienced a
de-integration once ever.
On Fri, Mar 13, 2020 at 3:31 PM pashdown<EMAIL_ADDRESS>wrote:

Welp, I've turned on the logging and killed and restarted HA several
times, which used to always cause the problem. It isn't happening anymore
for me. If it does, I'll try and capture some logs for you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/core/issues/28531#issuecomment-598957282,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFCPURE6OLORTGSN3GGOFCLRHKX3LANCNFSM4JIV45MA
.

@balloob yet you closed this issue without even being involved and without it even being fixed. Your attitude is misplaced to just close this issue when you had no business to.
@marthoc you already have two people provide logs. My logs are no different than theirs.

@ljmerza This issue was closed because I opened a PR that I thought addressed the issue. It was closed automatically when that PR was merged. You need to check your attitude.
Also, what everyone is posting is not logs. That’s the error itself, which tells me nothing about what caused the error. The debug logs will have a lot of information about the specific call that provoked the error and the calls leading up to it. I’ve actually added a lot of debug output to pyecobee since I started contributing to it, which is precisely so that when an issue arises, I have all the information I need to diagnose.

Going to lock this issue.
People that have this issue, feel free to open a new issue if you can reproduce it after running the Home Assistant version with the bugfix.


Adversary Plugin error code 500

Thought to have installed Caldera successfully, followed the documented procedure to get the adversary plugin going but whenever I try to access it on the web page it raises error 500. I have already tried debugging this to a certain extent without any success. Any tip to help me get this going?

Caldera itself works fine, I have it hosted on a private Ip address and can access it successfully, the problem is when I access the adversary tab it raises error 500 without any debug line or exception to give me a hint on what's going wrong

@Francisco4fonso Unfortuantely, a lot of potential debug information is currently unavailable in the current design, but we should still be able to get to the bottom of this issue. When you first hit the adversary tab, Caldera runs the planner method of adversary\app\service\adversary_api.py, which handles a lot of the interaction for the page. I suspect what may be happening here is that your auth_svc call may be crashing in some manner, though the issue could also be with connecting to the dao, or the exploder. If you have a python debugging tool, I'd recommend stepping through the planner function in order to find which one is crashing, otherwise, I'd use print statements to verify which ones successfully complete. If you can figure out which call is to blame, we should be able to get closer to fixing the issue overall.
Also, you will want to likely update to the most recent version of Caldera at some point, as the adversary plugin had a rather unfortunate bug that broke communication between the agents and the server for a period of time (fixed as of #47).

@Francisco4fonso If this is still an issue for you, I've create a merge request with a toggle in the main caldera repo's config file that re-enables debug information. If you use it, you should be able to get more information to resolve this.

Closing due to inactivity. If the issue persists, feel free to re-open this ticket or create a new one.


check that the answers belong to the current test

in rare case if the subscription associated to a test is not empty at the end, all further test will fail because they consume last message of previous one and think the payload is corrupted.
As the test stop message consumption once he reached the attended value, this issue propagate to next tests.

fixed


Pixelify Package Based On Pixel 5?

Device name: Pixel 6 Pro
Rom name: OEM
Android version: 13
Pixelify version: 3
I received this email after setting up the device. Is the Pixelify package based off a Pixel 5?

Just noticed this has not been updated since November 5, 2023.


[#76] Add multiple choice UI [Last part]

Closes #76
What happened 👀
Add multi-choice UI.
Insight 📝

Basic list implementation with choice stored as selected states.

Proof Of Work 📹
https://user-images.githubusercontent.com/13435717/125420159-fe8febf0-28dc-4906-8cdf-a92efcf227b8.mp4
Text size has been reduced in the latest commit:

thanks @manh-t 🙏  all updated


Upgrade to 8.10.4

Addresses https://github.com/MondayMorningHaskell/haskellings/issues/37
It seemed there was an issue where GHC would non-deterministically fail to create the final executable. After upgrading the system to use GHC 8.10.4 instead of 8.8.4, I am unable to reproduce this failure.

I'm going to skip CI on this...seems like there's not a Docker container for LTS 18.4 just yet, but I think it's worthwhile to move forward here.


[imgui] metal C++ binding can't be linked against

Describe the bug
The C++ Metal Binding for ImGui can't be linked against.
It looks like the Metal Binding is not built with IMGUI_IMPL_METAL_CPP
Environment

OS: Mac OSX 12.4
Compiler: Clang

To Reproduce
vcpkg install imgui[metal-binding,osx-binding,glfw-binding]

find_package(imgui CONFIG REQUIRED)
target_link_libraries(Runtime PRIVATE imgui::imgui)
target_include_directories(Runtime PRIVATE ${IMGUI_INCLUDE_DIRS})

target_compile_definitions(Runtime PRIVATE IMGUI_IMPL_METAL_CPP)

Failure logs
[build] Undefined symbols for architecture x86_64:
[build]   "ImGui_ImplMetal_NewFrame(MTL::RenderPassDescriptor*)", referenced from: [...]
[build]   "ImGui_ImplMetal_RenderDrawData(ImDrawData*, MTL::CommandBuffer*, MTL::RenderCommandEncoder*)", referenced from: [...]
[build] ld: symbol(s) not found for architecture x86_64

Function ImGui_ImplMetal_NewFrame is declared in https://github.com/ocornut/imgui/blob/master/backends/imgui_impl_metal.h with 2 simlar mode:
...
#ifdef __OBJC__
IMGUI_IMPL_API void ImGui_ImplMetal_NewFrame(MTLRenderPassDescriptor* renderPassDescriptor);
...
#endif
...
#ifdef IMGUI_IMPL_METAL_CPP
#include <Metal/Metal.hpp>
#ifndef __OBJC__
...
IMGUI_IMPL_API void ImGui_ImplMetal_NewFrame(MTL::RenderPassDescriptor* renderPassDescriptor);
...
#endif
#endif

So IMGUI_IMPL_METAL_CPP has conflict with __OBJC__ which related to build .mm file. Right?

I am not sure. To me it looks like the vcpkg port is compiled without the CPP define

@ocornut Needs some help here.

Hello,
Can't really help myself.
I am not very well acquainted with Mac infrastructure even less so about this ObjC/C++ shenanigans.

We need to understand the source code before we fix this issue.

The port needs to compile the files with a Cpp compiler and a ObjC compiler separately I guess

Hi @ocornut , do you know who contribute these related code?

@warrenm and @o-micron might know but lacking details i’m not sure its a problem on our end. If you have a linking error without specifying exact compile/linking params it is difficult to help.
The backend can indeed be built both for ObjC and C++, I don’t know how this handled in term of vcpkg but i imagine it should be an option.

Metal-cpp is a header only library, so we need to add these definitions to generate the implementation in a cpp file
#define NS_PRIVATE_IMPLEMENTATION
#define CA_PRIVATE_IMPLEMENTATION
#define MTL_PRIVATE_IMPLEMENTATION
#include <Foundation/Foundation.hpp>
#include <Metal/Metal.hpp>
#include <QuartzCore/QuartzCore.hpp>

Sorry for last comment I thought the linking errors were related to Metal-cpp ..
I think yes if we build the current metal backend (objc), we need to define IMGUI_IMPL_METAL_CPP  before building or simply the symbols won't be exported with the library.

Exactly. There are two things in the metal binding:
The Obj-C part which is compiled with an objc-compiler and the C++ part, which is compiled with a C++ compiler and with IMGUI_IMPL_METAL_CPP. Both need to be compiled separately.

I'll test this locally, curious myself.


Add support to send LOG and EVENT to OtelCollector as logs

Description
This incorporates the changes from #595 to add support for forwarding logs over otlp. It also adds configuration to turn logs/metrics/traces on and off.
⚠ This change renames temporary_emit_otel_traces ⚠
We don't believe anyone is using it, and since we were adding the other signals we figure these properties are as permanent as any others.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing performed?

[x] Unit tests
[ ] Integration tests
[ ] Acceptance tests

Checklist:

[x] This PR is being made against the main branch, or relevant version branch
[ ] I have made corresponding changes to the documentation
[x] I have added testing for my changes

If you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack

In https://github.com/cloudfoundry/otel-collector-release/pull/48 we made the otel-collector release add noop pipelines for any signal that doesn't have a pipeline defined. This should make it safe to turn these properties on by default, and allow users to turn them off as a (probably minor) performance optimization if they want to.


RTL Application dialog is LTR

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Content inside a dialog should be similiar to the application direction
What is the current behavior?
Dialog content inside RTL application (html dir="rtl") is LTR
What are the steps to reproduce?
Opening any dialog in RTL app
What is the use-case or motivation for changing an existing behavior?
Make dialog work again for RTL apps
Which versions of Angular, Material, OS, browsers are affected?
Angular 2.3.0
Material 11
All browsers
Is there anything else we should know?
The RTL applied fine and worked as excepted in Material 10

This will be addressed as part of #1719


Support for setting and accessing HttpContext.Items

Hello, I am working on multitenant application and crucial part of the tenant resolution is to store the resolved tenant Id in context.Items within my middleware and retrive it later.
How can I set up HttpContextMoq to actually store the items?

Hi @mebymyself
Yes, you can! In the latest version, I created a test sample to show how to set up a HttpContext with fake Items.
Please check the sample here: https://github.com/tiagodaraujo/HttpContextMoq/blob/master/tests/HttpContextMoq.Samples/HttpContextItems.cs
Thank you for opening an issue with your question. Hope this answer helps you.

@tiagodaraujo Thank you! my tests are passing now


Plans/ideas to make geolocator a sticky service on Android?

This is a

[ ] Bug
[x] Feature Request

Which plugin does this impact:

[ ] Battery
[ ] Connectivity
[ ] Contacts
[ ] DeviceInfo
[ ] ExternalMaps
[x] Geolocator
[ ] Media
[ ] Permissions
[ ] Settings
[ ] Text To Speech
[ ] Vibrate
Other:

I was wondering if there were any plans to offer the possibility to make the geolocator a sticky service on Android (resulting e.g. in the service being restarted after a device reboot). If otherwise someone has an idea of how to achieve this behavior with the current plugin, I'd be happy to hear about it, too.

I have thought about this, usually you want to customize and have control of how that works. I think an example is a way to do it to show everyone how to use it. However, the documentation on services is really good and has this exact example.

Thanks, I'll look into that.


Remove errant 'i' from sed, causing corrupt config

It looks like this was accidentally added when cleaning up this area in e2f738022648755b727f51c0ef5dc99cd3732a5e. This insert had no effect on the first run (or if a replication key was statically defined), but on subsequent runs the replication token would contain this sed pattern and a newline, causing the JSON prettify-ing of config.json to fail. This ultimately left the config corrupt and broke other key discovery methods on further runs.
Before this patch (debug output):
ok: [consul-0] => {
    "consul_acl_replication_token": "s/^ *//;s/ *$//\n            d6ac41c2-7f46-428c-9391-a80aa1d8525b"
}

After this patch:
ok: [consul-0] => {
    "consul_acl_replication_token": "d6ac41c2-7f46-428c-9391-a80aa1d8525b"
}

This is perhaps related to GH issue brianshumate/ansible-consul#160

Thanks!


translation German - state missing

Hi,
just figured out that state is still showing in English for entities like cover.xxx if UI is set to German.
proposed translation:
English = German
Open = Geöffnet
Closed = Geschlossen
Are further states like 'closing' will be displayed?

I do not know if localisation is top priority right now?
Maybe it is possible to reference the work done in ha to get a congruent experience, without any effort?
besides I am a native speaker of German and would love to take part in this project. Just pm me.

https://github.com/matt8707/ha-fusion/releases/tag/2023.12.4


libnvidia-ml.so.1: cannot open shared object file: no such file or directory: unknown.

The following error occurs:
Starting Docker image r8.im/openai/whisper@sha256:30414ee7c4fffc37e260fcab7842b5be470b9b840f2b608f5baa9bbef9a259ed and running setup()...
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: load library failed: libnvidia-ml.so.1: cannot open shared object file: no such file or directory: unknown.
ⅹ Failed to start container: exit status 127
For the command:
cog predict r8.im/openai/whisper@sha256:30414ee7c4fffc37e260fcab7842b5be470b9b840f2b608f5baa9bbef9a259ed -i<EMAIL_ADDRESS>Thanks

@homerokzam any luck?

No. I gave up.

Hi, I had the same issue.
I use ubuntu 20.04 LTS, cog latest version, Cuda 12, and latest version of docker desktop and it failed.
When I used docker desktop, I could not config docker daemon runtime. So, I uninstalled docker-desktop and use only docker engine instead.
make sure to use docker engine or if anyone knows how to config docker daemon runtime please let me know.
I fixed by followed this https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
follow along this part

Doesn't work on Mac, and doesn't work on Windows 10 - so I guess Linux is the only REAL supported OS?
Which is fine but I wish I haven't wasted 2 hours trying to make it work on Windows 10 and Mac Intel/Apple Silicon.

@coolnalu Cog doesn't support Window 10. But I have never tried on Mac because I don't have one.
But it does support on Window11. You can follow this link https://github.com/replicate/cog/blob/main/docs/wsl2/wsl2.md

Most likely "libnvidia-ml.so.1" is not found because you dont have the nvidia-container-toolkit installed:
https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html


Deploy template sets in separate deployables

As a cobigen developer, I want to deploy every template set in a separate deployable so that I can release each template set separately. Please setup all template sets under the groupId com.devonfw.cobigen.templates.

[ ] separation of template sets into different maven modules
[ ] extension of configuration folder to hold installed jars next to adapted template tests
[ ] adapt reader to take both into consideration while preferring adapted over installed sets
[ ] adapt templates should extract all installed sets

What do you think about a "CobiGenTemplateSet_" prefix?
Like: "CobiGenTemplateSet_crud-java-server-app" to make template set projects easily distinguishable from other projects.
Should be a shorter prefix though.


Which source file contains the code for loading the model?

I want to customize the model loading process and modify the logic for loading the model

https://github.com/NVIDIA/TensorRT-LLM/blob/main/examples/llama/convert_checkpoint.py#L414

https://github.com/NVIDIA/TensorRT-LLM/blob/main/examples/llama/convert_checkpoint.py#L414
Thank you, I would like to modify the CPP file.  Another issue， Executor(std::vector<uint8_t> const& engineBuffer, std::string const& jsonConfigStr, ModelType modelType, ExecutorConfig const& executorConfig);     the interface how call


Change docker badge color from orange to blue

Make the Docker badge more consistent with the Docker(hub) color scheme, and also because blue is a nicer color than orange in my opinion.

Fremen Button


Fixes URL errors with left-right quotation marks in card titles

Left-right quotation marks (retrieved from data from xwing-data2) are now removed from wiki links.

Tested with local bot, works fine.


clearInterval on useEffect unload

Related to:

updating guildInfo
updating DiscordLive

I think I have already resolved this issue in some commit. Closing.


Propose following every Ubuntu LTS

Summary
This is to propose to

Release Ubuntu Noble based stacks and builders asap
Follow every Ubuntu LTS release, i.e. do the same once 26.04, 28.04, etc are released

Use Cases
Having an up-to-date root file system.
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

I worry about this creating more work than we as a team can handle.

Do we have enough people willing to take on the work of producing stacks for every release, instead of every other release? That's effectively twice as much work. It would be nice to hear from @paketo-buildpacks/stacks-maintainers and @paketo-buildpacks/builders-maintainers on how they feel about this.

Do we know that this is a problem for users? Have we seen users requesting the latest stack when it's not available? It will also create twice as much work for users. That's twice as often that they need to review applications and make sure they run on the new stack. Do we have any user feedback that supports a need for more frequent stacks?

3.) I'd also be curious if you could elaborate on the security improvements of releasing twice as often. The way I read the RFC, there is an implication that our present release cycle may have security drawbacks. I think it would be good to more clearly state these drawbacks. My understanding is that the present stack release cycle we follow keeps us in the Ubuntu patch cycle, but that what we miss out on are low/minor patches (sometimes Ubuntu defers these to the next release) and new/updated libraries (not security related). This is what we have documented on the website anyway, https://paketo.io/docs/concepts/stacks/#when-are-paketo-stacks-updated.

In regards to 2.), I've not observed that personally. The question I usually get is do you have X stack, where X is some other non-Ubuntu distribution of Linux. Debian, UBI, Alpine, or some other base that promises to have marginally smaller images. I'd be curious to hear from users on what they want/expect/need in this regard.

I worry about this creating more work than we as a team can handle.

I am a bit surprised to read this, because I recall this has been a topic in a past WG meeting (quite a while ago though) and I thought the only thing missing was materializing the decision from then in an RFC.

Do we have enough people willing to take on the work of producing stacks for every release, instead of every other release? That's effectively twice as much work. It would be nice to hear from @paketo-buildpacks/stacks-maintainers and @paketo-buildpacks/builders-maintainers on how they feel about this.
Do we know that this is a problem for users? Have we seen users requesting the latest stack when it's not available? It will also create twice as much work for users. That's twice as often that they need to review applications and make sure they run on the new stack. Do we have any user feedback that supports a need for more frequent stacks?

3.) I'd also be curious if you could elaborate on the security improvements of releasing twice as often. The way I read the RFC, there is an implication that our present release cycle may have security drawbacks. I think it would be good to more clearly state these drawbacks. My understanding is that the present stack release cycle we follow keeps us in the Ubuntu patch cycle, but that what we miss out on are low/minor patches (sometimes Ubuntu defers these to the next release) and new/updated libraries (not security related). This is what we have documented on the website anyway, https://paketo.io/docs/concepts/stacks/#when-are-paketo-stacks-updated.
In regards to 2.), I've not observed that personally. The question I usually get is do you have X stack, where X is some other non-Ubuntu distribution of Linux. Debian, UBI, Alpine, or some other base that promises to have marginally smaller images. I'd be curious to hear from users on what they want/expect/need in this regard.

Anyway, regarding your points.
Regarding 1. This is - unfortunately - a good point and I am curious to hear from the @paketo-buildpacks/stacks-maintainers and @paketo-buildpacks/builders-maintainers what they think. FWIW I would see the potential to counter that with reducing efforts by changing the stacks and builder setup for 26.04 onwards. We could have single 26.04 stack producing multiple build and/or run images. That way we still have different lists of packages to maintain, but they don't change frequently. The releases would be reduced from currently four to one. Given that pack meanwhile has support for merging layers, we should also be able to extend that to a single builder. Either extensions could be used to change build and/or run images or we could align on the largest build image and the user should pick the run image (instead of picking the builder as they do now).
Regarding 2. & 3. I suppose users usually don't care much about the stack, that's why they use buildpacks and not Dockerfiles in the first place. However, we've seen in the past that the number of known CVEs on Ubuntu LTS releases grows over time. This might not be an immediately worrying concern, as Ubuntu indeed patches critical vulnerabilities throughout the five years an LTS is maintained. But there are CVEs in the security advisory that have been rated low priority while they show a CVSS score >7.
I suppose with security awareness increasing users don't want to see those vulnerabilities in their security scans and having to explain why they are not critical.
Using docker scout cves --format markdown on 22.04 an 24.04 might be a minor difference, but it is a difference.
:mag: Vulnerabilities of ubuntu:22.04
:package: Image Reference ubuntu:22.04

digestsha256:981912c48e9a89e903c89b228be977e23eeba83d42e2c8e0593a781a2b251cbavulnerabilities
size31 MB
packages143

    pam 1.4.0-11ubuntu2.4 (deb)
pkg:deb/ubuntu/pam@1.4.0-11ubuntu2.4?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score7.4
CVSS VectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score0.09%
EPSS Percentile41st percentile

Description

A flaw was found in pam_access, where certain rules in its configuration file are mistakenly treated as hostnames. This vulnerability allows attackers to trick the system by pretending to be a trusted hostname, gaining unauthorized access. This issue poses a risk for systems that rely on this feature to control who can access certain services or terminals.

Affected range>=0
Fixed versionNot Fixed
CVSS Score4.7
CVSS VectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score0.05%
EPSS Percentile23rd percentile

Description

A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.

    krb5 1.19.2-2ubuntu0.4 (deb)
pkg:deb/ubuntu/krb5@1.19.2-2ubuntu0.4?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile11th percentile

Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile11th percentile

Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile11th percentile

Description

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

    gcc-12 12.3.0-1ubuntu1~22.04 (deb)
pkg:deb/ubuntu/gcc-12@12.3.0-1ubuntu1~22.04?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score4.8
CVSS VectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score0.06%
EPSS Percentile26th percentile

Description

DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables. The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.

Affected range>=0
Fixed versionNot Fixed
CVSS Score5.5
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score0.09%
EPSS Percentile39th percentile

Description

libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.

    ncurses 6.3-2ubuntu0.1 (deb)
pkg:deb/ubuntu/ncurses@6.3-2ubuntu0.1?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score6.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score0.06%
EPSS Percentile28th percentile

Description

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile11th percentile

Description

ncurses 6.4-20230610 has a NULL pointer dereference in tgetstr in tinfo/lib_termcap.c.

    openssl 3.0.2-0ubuntu1.18 (deb)
pkg:deb/ubuntu/openssl@3.0.2-0ubuntu1.18?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile17th percentile

Description

Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.

    libzstd 1.4.8+dfsg-3build1 (deb)
pkg:deb/ubuntu/libzstd@1.4.8%2Bdfsg-3build1?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.22%
EPSS Percentile61st percentile

Description

A vulnerability was found in zstd v1.4.10, where an attacker can supply empty string as an argument to the command line tool to cause buffer overrun.

    glibc 2.35-0ubuntu3.8 (deb)
pkg:deb/ubuntu/glibc@2.35-0ubuntu3.8?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.20%
EPSS Percentile59th percentile

Description

sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.

    pcre2 10.39-3ubuntu0.1 (deb)
pkg:deb/ubuntu/pcre2@10.39-3ubuntu0.1?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.09%
EPSS Percentile38th percentile

Description

Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.

    libgcrypt20 1.9.4-3ubuntu3 (deb)
pkg:deb/ubuntu/libgcrypt20@1.9.4-3ubuntu3?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile17th percentile

Description

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

    gnupg2 2.2.27-3ubuntu2.1 (deb)
pkg:deb/ubuntu/gnupg2@2.2.27-3ubuntu2.1?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score3.3
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS Score0.05%
EPSS Percentile19th percentile

Description

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

    systemd 249.11-0ubuntu3.12 (deb)
pkg:deb/ubuntu/systemd@249.11-0ubuntu3.12?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score5.9
CVSS VectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score0.07%
EPSS Percentile33rd percentile

Description

A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.

    coreutils 8.32-4.1ubuntu1.2 (deb)
pkg:deb/ubuntu/coreutils@8.32-4.1ubuntu1.2?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score6.5
CVSS VectorCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
EPSS Score0.04%
EPSS Percentile5th percentile

Description

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

    shadow 1:4.8.1-2ubuntu2.2 (deb)
pkg:deb/ubuntu/shadow@1:4.8.1-2ubuntu2.2?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score3.3
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score0.05%
EPSS Percentile22nd percentile

Description

In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.

    pcre3 2:8.39-13ubuntu<IP_ADDRESS> (deb)
pkg:deb/ubuntu/pcre3@2:8.39-13ubuntu<IP_ADDRESS>?os_distro=jammy&os_name=ubuntu&os_version=22.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score7.5
CVSS VectorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.37%
EPSS Percentile73rd percentile

Description

In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.

:mag: Vulnerabilities of ubuntu:24.04
:package: Image Reference ubuntu:24.04

digestsha256:cdc507f6026a62440bc601815bba185960e93f8b971112722cebe3cae1e125a0vulnerabilities
size29 MB
packages130

    pam 1.5.3-5ubuntu5.1 (deb)
pkg:deb/ubuntu/pam@1.5.3-5ubuntu5.1?os_distro=noble&os_name=ubuntu&os_version=24.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score7.4
CVSS VectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score0.09%
EPSS Percentile41st percentile

Description

A flaw was found in pam_access, where certain rules in its configuration file are mistakenly treated as hostnames. This vulnerability allows attackers to trick the system by pretending to be a trusted hostname, gaining unauthorized access. This issue poses a risk for systems that rely on this feature to control who can access certain services or terminals.

Affected range>=0
Fixed versionNot Fixed
CVSS Score4.7
CVSS VectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score0.05%
EPSS Percentile23rd percentile

Description

A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.

    libgcrypt20 1.10.3-2build1 (deb)
pkg:deb/ubuntu/libgcrypt20@1.10.3-2build1?os_distro=noble&os_name=ubuntu&os_version=24.04

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile17th percentile

Description

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

    openssl 3.0.13-0ubuntu3.4 (deb)
pkg:deb/ubuntu/openssl@3.0.13-0ubuntu3.4?os_distro=noble&os_name=ubuntu&os_version=24.04

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.04%
EPSS Percentile17th percentile

Description

Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.

    glibc 2.39-0ubuntu8.3 (deb)
pkg:deb/ubuntu/glibc@2.39-0ubuntu8.3?os_distro=noble&os_name=ubuntu&os_version=24.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.20%
EPSS Percentile59th percentile

Description

sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.

    coreutils 9.4-3ubuntu6 (deb)
pkg:deb/ubuntu/coreutils@9.4-3ubuntu6?os_distro=noble&os_name=ubuntu&os_version=24.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score6.5
CVSS VectorCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
EPSS Score0.04%
EPSS Percentile5th percentile

Description

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

    gnupg2 2.4.4-2ubuntu17 (deb)
pkg:deb/ubuntu/gnupg2@2.4.4-2ubuntu17?os_distro=noble&os_name=ubuntu&os_version=24.04

Affected range>=0
Fixed versionNot Fixed
CVSS Score3.3
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS Score0.05%
EPSS Percentile19th percentile

Description

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

@dmikusa I'd say that https://github.com/paketo-buildpacks/rfcs/pull/313 would make a decision to follow every LTS easier. Would you agree?

Yes @loewenstein-sap - That would alleviate my concerns for 1.)


bumping the version from 2.7 to 2.8

Description
version bump from 2.7 to 2.8
Issues Resolved
partially resolves Release version 2.7.0#170
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #194 (04afa2f) into 2.x (ed0f955) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##              2.x     #194   +/-   ##
=======================================
  Coverage   86.27%   86.27%
=======================================
  Files          15       15
  Lines         204      204
  Branches       40       40
=======================================
  Hits          176      176
  Misses         26       26
  Partials        2        2

Flag
Coverage Δ

dashboards-search-relevance
86.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Build against the master branch v2

I'm still working on this man. There's some weird stuff going on with libtool that I don't fully grock yet. I guess libtool doesn't work with DESTDIR installs. It's like a 15 year old bug / feature argument. Done way more reading of the libtool / autotools mailing list / docs over the last few days than I'd like to admit.

Try make install in a fakeroot env, maybe?

I've got a PR with the build fixes in #167. I still can't explain one remaining issue with the GCC build (clang is fine) but I've got a work around in the PR. I'm closing this one but if anyone has the time to look at #167 and knows the quirks of the travis-ci stuff feel free to help out over there.


Suggest improvement for website element shadows in dark mode

The current website element (buttons, inputs) shadows don't look good in dark mode as compared to white mode. Suggest tweaking of shadows to achieve glass texture in dark mode.
Current dark mode button

Current white mode button

Adding gradient to the button like in the picture below might help


Modified TypeScript definition

Added missing property HttpClient.isRequesting. Changed HttpResponseMessage.statusCode from string to number
this addresses my own issue as well #114

Updates the type info in the original sources. Thanks for finding those issues!


https://istio.io/downloadIstio redirects to 1.6

See:
$ curl -I https://istio.io/downloadIstio
HTTP/2 301
access-control-allow-origin: *
cache-control: public, max-age=0, must-revalidate
content-length: 107
content-type: text/plain; charset=utf-8
date: Mon, 03 Aug 2020 23:50:09 GMT
location: https://raw.githubusercontent.com/istio/istio/release-1.6/release/downloadIstioCandidate.sh
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
age: 43869
server: Netlify
x-nf-request-id: c62fe669-d69a-4313-aba0-218ecfce32a4-46345804

Shouldn't it redirect to master?

Right now, for example, if I fix is made in that shell script, it should be backported to 1.6. This doesn't make sense to me.

Attempt to fix it: https://github.com/istio/istio.io/pull/7865

I believe we want it to redirect to the stable branch. Agreed that changing the script should require back porting to the appropriate release.


[AIRFLOW-1781] case insensitive search in LDAP group

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1781

Description

[x] Fix incorrect search user in group. Use case insensitive DN search inside group.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2750 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #2750      +/-   ##
=========================================
+ Coverage   73.19%   73.2%   +<.01%
=========================================
  Files         157     157
  Lines       11923   11923
=========================================
+ Hits         8727    8728       +1
+ Misses       3196    3195       -1

Impacted Files
Coverage Δ

airflow/models.py
87.3% <0%> (+0.04%)
:arrow_up:

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 3fde104...128bba3. Read the comment docs.

LGTM

+1


managing priority?

sorry i'm throwing so many questions at you!
as it's built now, how i understand it is that it's a first-come-first-serve type of model. is there a way to manage the priority of tasks? i.e. if i have a long queue of tasks running, is there a way i can then shoot off an e-mail asynchronously without too much delay? or, in this scenario, would i have to setup a separate background worker and queue purely for e-mails?
-chris

Hi @claudeomusic, I'm not a pro with SQS I think you should use separated SQS queue for Urgent tasks, it will fits with your requirements and perform urgent job without delays. I don't know other way to set priority for the task.

@AlexanderUlitin is right. You will need to setup another worker environment with its own queue for your email jobs.

@AlexanderUlitin @tawan :+1:


[FEATURE REQUEST] Parametrize to check also closed PRs

Great tool, but it checks only opened PRs:
https://github.com/agrc/reminder-action/blob/c9dca07e06ab280b813702662cce06acd0b47452/index.js#L39
Would it be possible to paramterize it, so it also iterate over closed PR's?
We often merge some code, and close, but we want to be reminded about some code change in one month, to revert it or recheck.

I have the exact same use case, is this a won't fix?

I have the exact same use case, is this a won't fix?

No it's not a won't fix but it's not a feature we use so it will likely be a community contribution.

I see. How large do you think the scope is? Would simply adding more states to the call suffice or it's more complicated than that?

Yah that might be. But th op wants to be able to configure it so a bit of file reading would be required. I think the scope is a few hours.

For now forked version which will read all closed PRs and issues by default: https://github.com/gladykov/reminder-action/commit/70cac9925c5583a56536ac4cfb4e375eab00766b
For us is not a problem, as we are not using issues at all. We also limited action to run only once per day, not to use too much resources.

@steveoh I want to reopen the issue after a certain time and this action is a great candidate for usage but unfortunately it doesn't remind on closed issue 😞

I'm going to close this as it doesn't seem like anyone is wanting to contribute this feature and we aren't going to add it. Basically it's a stale issue. Thanks everyone! We are still open to a pull request to add the feature.


How to Include scripts in subtemplates Loaded via Ajax

My ContentPage includes shortcode which loads scripts.
Scripts are generally loaded only when template as head  tag other wise scripts or not loaded.
In Requirements.php line 700
public function includeInHTML($templateFile, $content) {
if(
(strpos($content, '') !== false || strpos($content, '</head ') !== false)
&& ($this->css || $this->javascript || $this->customCSS || $this->customScript || $this->customHeadTags)
)
I am loading the sub template via ajax . this does not include scripts
What is the solution to the problem
I am not sure  if  in the Admin loads  required scripts if so how. entwine on the front would increase the page load.
So what is solution . I need  a feedback on how to include scripts in a subtemplate loaded via ajax

@blpraveen You'll need to do this on your own js. To load an external script see something like http://stackoverflow.com/questions/3261408/good-practice-method-for-loading-javascript-via-ajax

You're probably going to want to look into something like requirejs or some other front-end dependency loader.


[Question] LlamaParse as open source

If LlamaParse available as open source for non-production-grade applications.
Also I am interested to parse private data on-prem.
What possibilities for my case for using LlamaParse ?
Thanks

Hi @snassimr,
We now have a BYOC offer. Please contact us for more information.


another exhtml bug

Internal error, yaws code crashed

ERROR erlang code threw an uncaught exception:
 File: /Users/ev/erlang/apps/yawstest/www/exhtml.yaws:2
Class: error
Exception: {case_clause,{inline,yes,<<"p">>}}
Req: {http_request,'GET',{abs_path,"/ab.yaws"},{1,1}}
Stack: [{yaws_exhtml,format,5,[{file,"src/yaws_exhtml.erl"},{line,82}]},
        {yaws_exhtml,format,5,[{file,"src/yaws_exhtml.erl"},{line,117}]},
        {yaws_exhtml,format,5,[{file,"src/yaws_exhtml.erl"},{line,119}]},
        {yaws_exhtml,format,5,[{file,"src/yaws_exhtml.erl"},{line,117}]},
        {yaws_exhtml,format,2,[{file,"src/yaws_exhtml.erl"},{line,66}]},
        {yaws_server,handle_out_reply,5,
                     [{file,"src/yaws_server.erl"},{line,3179}]},
        {yaws_server,deliver_dyn_part,8,
                     [{file,"src/yaws_server.erl"},{line,2817}]},
        {yaws_server,aloop,4,[{file,"src/yaws_server.erl"},{line,1230}]}]

How to reproduce:
out(_Arg) ->
	Struct = {html, [], [
		{head, [], [
			{meta, [{charset, <<"utf-8">>}]},
			{title, [], <<"title">>}
		]},
		{body, [], [
			{p, [], <<"p">>}
		]}
	]},
	{exhtml, Struct}.

As before, ehtml version is ok (see issue #216)

Thanks, I'll have a look at this as well.

I'm wondering if there might be more exhtml problems lurking beyond this one, so I pushed branch exhtml-fixes that fixes this problem. @evbogdanov, can you try it and let me know if you run into any other exhtml bugs? If you see any other issues I can then fix them on that branch as well. Thanks.

@vinoski, nice! I'll check it out tomorrow.
I want to ask. Have you considered merging ehtml / exhtml into one-to-rule-them-all format?
The point is just to make this beast compatible with HTML5. After all, this is what newcomers expect from such feature.

@evbogdanov that's a good question for @klacke.

@vinoski, I did some testing:
https://github.com/evbogdanov/yaws_exhtml_fixes
Overall, I think the branch is usable. But a couple of bugs were found.
IMO, the number one bug is an inconsistency between ehtml / exhtml. For example:

foo

bar

baz

vs

    foo

    bar

    baz

Another example:
EXHTML = {h1, [], {lists, max, [[1, 2, 3]]}},
{exhtml, EXHTML}.
% Internal error, yaws code crashed...

EHTML = {h1, [], {lists, max, [[1, 2, 3]]}},
{ehtml, EHTML}.
% no error?

And one more:
EXHTML = {h1, [], 123},
{exhtml, EXHTML}.
%

%   123
%

EHTML = {h1, [], 123},
{ehtml, EHTML}.
%
{

EXHTML = {h1, [], 1234},
{exhtml, EXHTML}.
%

%   1234
%

EHTML = {h1, [], 1234},
{ehtml, EHTML}.
% Internal error, yaws code crashed...

There are bound to be differences between ehtml and exhtml, as they're intended to be different. I wasn't involved in putting the exhtml support together but I would guess it's meant to be more strict and to follow the XHTML spec, where ehtml was just more about being able to realize HTML using Erlang terms and it's not intended to be restrictive. Again, @klacke is probably the best person to describe the origins and intentions of each.
That said, some of what you're showing with your examples seems questionable, so I'll look into those issues a bit.

If I remember correctly, at the time there was no XHTML, there was only lax HTML. Maybe there was (XHTML) but is wasn't on the radar at the time.
The exhtml tag was added later.

@klacke @vinoski thanks for your replies!
Guys, have a look at ehtml5.
It's my HTML5 rethinking of ehtml with a couple enhancements:

Doctype is auto generated by {html} struct.
Tag attributes use maps instead of proplists.
Ability to use structs like {Tag, Content}. In ehtml it looks like {Tag, [], Content}, and I constantly forget adding these empty lists :-)

Personally, I think ehtml / ehtml5 can become very interesting with further improvements. But what do you think? Should we spend more time on this or it's ok how it's now?

@evbogdanov I haven't looked at it in detail, but one initial comment is that the use of maps is problematic since not everyone using Yaws uses a version of Erlang/OTP supporting maps.


Wrong punctuation in QoS Class glossary entry

This is a Bug Report

Problem:
There are too many closing brackets in

QoS Class (Quality of Service Class)) provides a way for Kubernetes to classify Pods within the cluster into several classes and make decisions about scheduling and eviction.

Proposed Solution:
Remove the extra closing bracket.
Page to Update:
https://kubernetes.io/docs/reference/glossary/?all=true#term-qos-class
/good-first-issue

@sftim Can this issue be closed?

Sure
/close


Support using RTLD_NEXT

Signed-off-by: Hal Gentz<EMAIL_ADDRESS>Depends on: https://github.com/MaikKlein/ash/pull/77#discussion_r201234586
PR checklist:

[ ] make succeeds (on *nix)
[ ] make reftests succeeds
[x] tested examples with the following backends: vulkan on archlinux

Is this still blocked?

@kvark Yes, till @MaikKlein releases 0.24.4.

@ZeGentzy Should be live now

@kvark Try now.

would be good to test it on CI as well


physicsLayout.getPhysics().giveRandomImpulse() bug

call method multiple time gone items please help me

Do you mean that the items are now gone from your view? Because yes, this is a known issue. Basically you will want to not use giveRandomImpulse() as it is only intended for testing and instead create your own method that will give impulses to views


Revert "Create reduce command"

Reverts soar-telescope/goodman_pipeline#272

Pull Request Test Coverage Report for Build 470

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.2%) to 68.42%

Files with Coverage Reduction
New Missed Lines
%

goodman_pipeline/core/tests/test_check_version.py
1
94.44%

Totals

Change from base Build 469:
0.2%

Covered Lines:
3035

Relevant Lines:
4131

💛  - Coveralls


Use new class ProxyConfig for proxy selection in OIDC configuration

Hi,
following this (closed/not merged) issue https://github.com/stevespringett/Alpine/pull/422 , I create this new one to make use of the newly created ProxyConfig class in order to have OIDC configuration use proxy if declared in configuration.
Thanks @nscuro for the work on ProxyConfig, looks good to me !

Depending on how you plan to test it, I might be able to help :

if that means you will build a docker image for DT (with a specific tag) and push it somewhere public, I could pull it and try to use it as I originally intended to (behind corporate proxy) with minimal effort (as I would reinvest that time when deploying it).
if you were by some way planning to build and test things locally, as I'm in no way familiar with building DT, I'm not sure I will be fit for this task. But once a newer version of DT is released, I would perform the test anyway, so you'd have feedback.

Keep me informed!

@nscuro Have you tested this with DT?

@stevespringett Not yet, sorry. I'll try to get it done tomorrow.


Error: gifsave_buffer: frame too large

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

If you cannot confirm both of these, please open an installation issue instead.
Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?

  System:
    OS: macOS 12.5.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 124.95 MB / 64.00 GB
    Shell: 3.5.0 - /opt/homebrew/bin/fish
  Binaries:
    Node: 16.16.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.16.0 - /opt/homebrew/bin/npm

On server (inside Docker):
  System:
    OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (2) x64 AMD EPYC 7T83 64-Core Processor
    Memory: 4.15 GB / 7.63 GB
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 18.7.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.15.0 - /usr/local/bin/npm
  npmPackages:
    sharp: ^0.30.3 => 0.30.7

What are the steps to reproduce?

When processing gif larger than 2000x2000. sharp (libvips) will throw error:
Error: gifsave_buffer: frame too large

What is the expected behaviour?
sharp (libvips) should handle large gif without any issue.

Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem

import sharp from 'sharp';
const media = sharp('test.gif', { animated: true })
const metadata = await media.metadata()

Please provide sample image(s) that help explain this problem
test.gif.zip

Yes, the change you've highlighted is the reason for this. The forthcoming sharp v0.31.0 will provide prebuilt binaries for libvips v8.13.x.


Load agent from dedicated agent class loader

Stop adding all the agent classes into the bootstrap class loader

Hides the agent from the regular classpath
Reduces risk of interfering with classpath scanners

Depends on #1337
Prerequisite for #1339

When implementing this, consider using the agent class loader for a dedicated log4j context - in LoggingConfiguration#init we may want to switch to using org.apache.logging.log4j.core.config.Configurator#initialize(ClassLoader, Configuration) instead of the current org.apache.logging.log4j.core.config.Configurator#initialize(Configuration) and use that to further separate agent loggers from others.


The ranking pages do not display correctly

On the main  page, the ranking pages, for example ranking of wealth, are not operating. After clicking, the page show nothing.
Please fix this bug.
And in the posts, if you upload a video links, you cannot size up the video in PC. But it can be done in mobile phones.

@mit1987 thx for your support.
Could you plz give us more detail?  better screenshot.
thank you！


[#131876783] Parameterise CONCOURSE_HOSTNAME

What
Add a new CONCOURSE_HOSTNAME variable so that we can deploy Concourse with a
different hostname. The default for the build-concourse target remains the
same.
This change is necessary because we're planning to remove the bootstrap code
from alphagov/paas-cf and use alphagov/paas-bootstrap instead, however
paas-cf expects a Concourse with the hostname of deployer.${domain}
instead of concourse.${domain}.
We can change the URL in the README when we come to introduce a new target.
How to review

Make a bootstrap Concourse with: make dev build-concourse bootstrap
Confirm that you can login and it has the right TLS cert at: https://concourse.${DEPLOY_ENV}.dev.cloudpipeline.digital/

Who can review
Not @dcarley or @alext

lgtm


fortifyExecuteScan settings files

Hi,
it seems the projectSettingsFile and globalSettingsFile parameter isn't recognized by the step fortifyExecuteScan.

Leads to debug output:
13:18:11  debug fortifyExecuteScan - Global settings file not provided via configuration.
13:18:11  debug fortifyExecuteScan - Project settings file not provided via configuration.

So our config is not recognized and it tries to downloaf from maven central (not reachable from our network).
File exists in the root of repository ... maybe not stashed / unstashed ?

Hi @T1mey
just to avoid misunderstandings: The file does exist in the path .pipeline/config.yml, right? "root" might be a bit ambiguous.
Also, the fortifyExecuteScan section is in the steps, not in the stages section of your config file, right? Do other steps use the configuration?
Which Pipeline are you using? Which version?
Best,
Florian

So with config file I meant 'settings.xml'... sorry for unclear description.
yes, the settings.xml file is recognizeg by the other steps e.g. mavenExecute and mtaBuild
fortifyExecuteScan and params are defined as step.

Hi @T1mey
I think we need some more information. Ideally, it would be great if you could share a reproducible minimal example project (just to demonstrate this issue).
If this is not possible, the log of the fortify stage of this run would be helpful, of course with any confidential information redacted. If can't post it here, feel free to reach out via email.
Which version of the Pipeline are you using?

During fortifyExecuteScan the maven settings (m2Path, projectSettingsFile, globalSettingsFile) are used only for generating the class-path which is then handed to the sourceanalyzer CLI tool.
I've tried to understand where this log-output comes from, and /maybe/ it is misleading. When the fortifyExecuteScan step starts, it needs to determine "artifact coordinates". For a maven project, this means evaluating the pom.xml file, which is also done with a maven execution. The log-output could come from this phase. But it is also possible that it actually doesn't work and the settings are really required, even for evaluating just groupId, artifactId, and version. In that case, a fix is needed in fortifyExecuteScan to pass on these parameters also for pom evaluation.
Can you clarify and perhaps provide the complete log-output if possible up to the point where the snippet is from?

I have opened this PR. Not sure if this already enough, or whether the options also need to be passed to sourceanalyzer somehow.

I've created a branch in the public repository of our pipeline library. To test whether the above change in the fortifyExecuteScan step fixes your issue, you could consume the branch "fix-fortify-maven". I.e. in the Jenkinsfile for your project, make the following change:
-String pipelineVersion = "v39"
+String pipelineVersion = "fix-fortify-maven"

Please let me know how this goes.

Thanks a lot for provding this fix... Just want to give it a try, but it seems that something else might have been changed.
There is a file requested from an external URL which is at the moment not accesible from our network.

It might be a good idea to provide list to which external systems / URL's the pipeline is connecting.
This will cause all our pipelines to fail if such a call is introduced.  --> breaking change

No... that is a problem only with consuming a non-release branch of the repo where I needed to make the fix. Normally, the Groovy code in that library would load a release binary of the command line tool piper. The piper binary contains the new go-based portion of that library. The Groovy code realizes that no release is available for "fix-fortify-maven", and wants to fall-back to building the binary itself. It fails while fetching dependencies.
I think we have to wait until my fix is on master. A binary for the master branch is always available shortly (i.e. without actual "release").

Thanks for information... when does this in general happen ?

The fix is on master now, and the new binary should be available already. I adjusted the branch fix-fortify-maven of our library. You could just retry it now.

@stippi2  Can confirm that config is loaded now.
Struggeling with some internal setup on getting projects from SSC., but that's no pipeline issue.

Thanks for the update!

Thanks for letting us know. Closing this issue as the original issue is resolved.


Publish "getting started" guide

See PR#19

Completing this also means that the references in the getting started examples should be stable. So all referenced plugins should be released, and the workflow examples should use the versioned plugins.

Metadata plugin PR#9 and PR#10 are relevant.

The examples also need to incorporate pending affinity and loop features.

Pending https://github.com/arcalot/arcaflow-workflows/pull/8 and arcalot/arcalot.github.io#23


Can't access outside of class

Describe the bug
I can't access t('key') outside React class it's just outputs key name. It works when i call it with this.props.t("name") inside of class
Occurs in next-i18next version
"next-i18next": "^4.5.0"

OS (please complete the following information)

Device: MBP 2015 15"
Browser: Firefox 80.0.1

import { i18n, Link, withTranslation } from "../../i18n";

const columns = [
  {
    name: i18n.t("name"),
  },
]

class Test extends React.Component {} ..
export default withTranslation("common")(Test);

That's down to how React context works. Most likely, the i18n import isn't initialised at the time when you declare columns, and therefore returns the key instead of the value. You'll need to await the initPromise.

@fuzunspm how did you solve this?

my old solution is not working at the moment with the latest update. I'm using getServerSideProps now and moved all most of variables inside render() method

@isaachinman could you provide an example of how to deal with that?


respond to cancellation of task that already have been cancelled with "success: false" instead of timing out

Currently, trying to cancel a task that is already cancelled will cause a timeout on the rmf_api_server. Ideally, this should be a response like
{
  "success": false
}

one way to do this would be to keep track of all tasks that have been finished or cancelled. This could be implemented by querying a fleet adapter database, once that is implemented.

I also would like to add a similar enhancement request regarding the task API, for example:

Task submission

return failure instead of not responding
return success or failure with additional info (e.g. current status of the task) if a task with the same task_id exists

Task cancellation, kill, interrupt, etc

return failure if the task is already, canceled/interrupted/completed, etc.

Task status query:

New API to check the current task status.


Capital letters in Swedish species names

In the BirdWeather PUC community I have posted the following and Tim Clark asked me to post it here instead. I hope this can be fixed and am attaching the file with Swedish species names.

You are now using the list from eBird where there are no capital letters in the Swedish species names. I have sent a request to eBird to change this, but no feedback so far. In the BirdNET-Pi setup we have corrected this.
The species names must have a capital letter in the first word, just in the same way as the scientific names are structured! Remember to also do this in cases where two different names exist for a species where they are separated by a slash.
Unfortunately, text files cannot be attached here, but please let me know how I send this, and this change is probably very easy to do.
Thank you
_@svardsten - we’re using the species translations in the BirdNET-Analyzer from Stefan - GitHub - kahst/BirdNET-Analyzer: BirdNET analyzer for scientific audio data processing. - could you possibly post in the discussions there? As then it would get integrated in at the source.
Thanks!
-Tim

Swedish species names.txt

Thank you!


chore: Fix size-limit step

:tada: This PR is included in version 1.0.0-alpha.51 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Missing git tag v4.0.0

Description
On NPM I can see 4.0.0 has been published

I go looking for the source code so I can read the CHANGELOG.md ... but there is no tag for this release on github

4.0.0 tag missing
no mention in master CHANGELOG.md

No way I'm installing the latest if I have no idea what it breaks (assuming major semver version breaks the API right?)
Anything else?
sad FOSS developer noises

Hello @mixmix unfortunately we had an issue in our CI pipeline this release and due to this reason the tag and changelog was not created correctly.
We are indeed introducing some breaking changes, so its really important to inform about those, what will. happen now is we will manually merge the changelog in master and trigger another release after 4.0.1.
If u want to see the breaking changes before it gets merged to speed up on your side, please take a look at the PR directly.


Module 'ngStorage' is not available!

I use requirejs in my project to load all the JS files and dependencies. Original I used version 0.3.0 without any problem. Today I upgraded to 0.3.4 and I receive this error while my app tries to bootstrap:
Error: [$injector:modulerr] Failed to instantiate module ngStorage due to:
Error: [$injector:nomod] Module 'ngStorage' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

im having the same issue

Same here with 0.3.4 even bower is not able to resolve ngStorage.

Due to some changes that was made in the UMD/CommonJS/RequireJS/ code there is a slight problem with this. We are working on getting this resolved and should have a new release asap.
@Dathix the readme states : bower install ngstorage to install. Which should work. ngStorage is some other module.

Same here, the bower.json file has the right dependency... it works on 0.3.0 but fails in 0.3.4

Issue is still present with Ionic and ngstorage version 0.3.10

Re-open issue?

I fixed this problem with uninstall ngStorage and reinstall with bower install ngstorage


Cast Kernel Ignores Timezone

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
The beginnings of timezone support were added in #824, however, this is currently ignored by the cast kernel
Describe the solution you'd like
Timezones should be correctly handled by the cast kernel
Describe alternatives you've considered
We could not support timezones
Additional context
Noticed whilst investigating #1932

I'd like to work on this. Could you assign it to me? @tustvold

I would recommend writing up the expected behaviour first, as timezone handling is notoriously messy, and once we have consensus we can move forward with implementing that.
FYI @avantgardnerio @waitingkuo

@tustvold thank you for pinging me, i'm working on these things now as well.
@doki23 it would be great if you could help ❤
You could find some other related issues here apache/arrow-datafusion#3148
some hints that might help
1
https://github.com/apache/arrow-rs/blob/3bf6eb98ceb3962e1d9419da6dc93e609f7893e6/arrow/src/compute/kernels/cast.rs#L1284
to make casting function consider timezone, we have to fix the second _ identifier and check whether it's None or Some
2
https://github.com/apache/arrow-rs/blob/3bf6eb98ceb3962e1d9419da6dc93e609f7893e6/arrow/src/array/array_primitive.rs#L209
while using fmt to print, we first convert it to NaiveDateTime (from chrono-rs) which contains no timezone info so that you could only see timestamp without timezone

@doki23 are you planning to draft the proposal?

@doki23 are you planning to draft the proposal?

sure, plz wait me hours

We consider tz only if from_type and to_type both needs it. For example, ignoring tz is ok when we cast ts to i64, because i64 array doesn't care about timezone.
So, there're 2 situations:

ts is from_type, and the to_type needs tz.
ts is to_type, and the from_type has tz.

when ts is from type
I noticed that timestamp array is always treat as PrimitiveArray. We can't get tz from ArrowPrimitiveType::DATA_TYPE, because there're only utc ts definitions like:

make_type!(
    TimestampSecondType,
    i64,
    DataType::Timestamp(TimeUnit::Second, None)
);

So, ArrayData::data_type makes sense.

ts is to type
We may need a TimestampBuilder::from in place of TimestampSecondArray::from_xxx which can realize the timezone.

what's expected behavior for casting timestamp with timezone to timestamp without time zone?
e.g. if the timestamp with timezone is 1970-01-01T08:00:00+08:00 (note that the timestamp underline is 0), what's the casted result? 1970-01-01T08:00:00 (underline timestamp as<PHONE_NUMBER>0000) or 1970-01-01T00:00:00  (underline timestamp as 0)?
i recommend that listing these ambiguous cases and your proposed behavior so we could discuss
btw i tested it on pyarrow, it simply changes the datatype but not change the underline timestamp (1970-01-01T08:00:00+08:00 becomes 1970-01-01T00:00:00

what's expected behavior for casting timestamp with timezone to timestamp without time zone?

The intuitive answer would be to convert it to UTC. I think postgres effectively casts it to server (local) time.

I believe this section of the arrow schema definition is relevant - https://github.com/apache/arrow-rs/blob/master/format/Schema.fbs#L280
In particular

One possibility is to assume that the original timestamp values are relative to the epoch of the timezone being set; timestamp values should then adjusted to the Unix epoch

Given this is the only possibility enumerated in the schema, I feel this is probably the one we should follow unless people feel strongly otherwise. My 2 cents is that anything relying on the local timezone of the system is best avoided if at all possible, it just feels fragile and error-prone.

local timezone of the system

Yes - these RecordBatches could be part of Flights, yes? In which case the whole point is to send them around to different computers that may be in different timezones, so it kind of forces our hand here.
And if we are doing it this way in arrow where we don't have the luxury of following postgres, maybe this is also where we break postgres compatibility in DataFusion. Just because postgres did it wrong doesn't mean we should follow...

what's expected behavior for casting timestamp with timezone to timestamp without time zone?
Tz has no affect to the value, it just used for display.

what's expected behavior for casting timestamp with timezone to timestamp without time zone?

The specification states

/// However, if a Timestamp column has no timezone value, changing it to a
/// non-empty value requires to think about the desired semantics.
/// One possibility is to assume that the original timestamp values are
/// relative to the epoch of the timezone being set; timestamp values should
/// then adjusted to the Unix epoch (for example, changing the timezone from
/// empty to "Europe/Paris" would require converting the timestamp values
/// from "Europe/Paris" to "UTC", which seems counter-intuitive but is
/// nevertheless correct).

As stated above, given this is the only possibility enumerated I think we should follow this. The inverse operation, i.e. removing a timezone, I would therefore expect to do the reverse i.e. 1970-01-01 01:00:01 +01:00 would become 1970-01-01 01:00:01. This is consistent with both postgres and chrono.

thank you @tustvold , didn't aware this spec before
This looks good to me
btw, i think with_timezone_opt already covered another possibility - keep the underline i64 value and change the metadata

Yeah let's do the "hard" operation in the cast kernel, and if people don't like it, they can perform a metadata-only cast usingwith_timezone_opt :+1:

https://github.com/apache/arrow-rs/issues/3794 is related to this, and implements the necessary machinery for timezone aware parsing of strings

Reopening as there are still issues around casting between timestamps with timezones #4201


Remotion better licensed alternative

Currently remotion seems to be available as a provider and its licensing is not very friendly..Would you consider https://github.com/redotvideo/revideo an MIT licensed library

We won't be adding new providers for the mean time. How is the Remotion license not fair?
You are eligible to use Remotion for free if you are:

an individual
a for-profit organization with up to 3 employees
a non-profit or not-for-profit organization
evaluating whether Remotion is a good fit, and are not yet using it in a commercial way

Seems super fair.


How to create edge without using database foreign key ?

I want to use ent manage my entity without using Edges generated database foreign key,How can I define my entity ?

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

User、Car、UserCar
// Fields of the User.
func (User) Fields() []ent.Field {
    return []ent.Field{
        field.Int("age").
            Positive(),
        field.String("name").
            Default("unknown"),
    }
}

// Fields of the Car.
func (Car) Fields() []ent.Field {
    return []ent.Field{
        field.String("model"),
        field.Time("registered_at"),
    }
}

// t_user_car
func (UserCar) Fields() []ent.Field {
    return []ent.Field{
        field.Int("user_id").
            Positive(),
        field.Int("car_id").
            Positive(),
    }
}

I hope to create a UserCar Model as Edges, not use the following Edges
// Edges of the User.
func (User) Edges() []ent.Edge {
    return []ent.Edge{
        edge.To("cars", Car.Type),
    }
}

what should I do to slove the problem ? foreign keys in mysql is negative when inserting、updating、deleting，so i hope to Use the middle table t_user_car manage the relationship between Use and Car, Is it possible in Ent ?
Motivation 🔦

As far as I know, ent must depend on the foreign key for edges. Just remove the Edges in your code in the schema definition. And then implement the logic in your own code. This is what I do currently.

May refer to migrate/#foreign-keys?

migrate/#foreign-keys

thanks，I will try it  by self implement foreign key logics ~

migrate/#foreign-keys

thanks，I will try it by self implement foreign key logics ~

That's it. However it may be execellent to auto-generate codes implementing logics without foreign keys, cascading ... It must be difficult as well to implement in ORM.

migrate/#foreign-keys

thanks，I will try it by self implement foreign key logics ~

That's it. However it may be execellent to auto-generate codes implementing logics without foreign keys, cascading ... It must be difficult as well to implement in ORM.

yes, auto-generate perhaps have standard mappings, for example, generate from table name to a middle table ,with two unique keys table_name_a_id, table_name_b_id


Unable to load schema from https://json.schemastore.org/swcrc

Describe the bug
The url is returning a 503 error
https://json.schemastore.org/swcrc
Unable to load schema from 'https://json.schemastore.org/swcrc': Service Unavailable. The server is currently unavailable (overloaded or down).
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Service Unavailable</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=u.

Input code
No response
Config
{
  "$schema": "https://json.schemastore.org/swcrc",
  "sourceMaps": true,
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "decorators": true,
      "dynamicImport": true
    },
    "transform": {
      "legacyDecorator": true,
      "decoratorMetadata": true
    },
    "target": "es2021",
    "baseUrl": "./"
  },
  "minify": false
}

Playground link (or link to the minimal reproduction)
https://play.swc.rs/?version=1.3.100&code=H4sIAAAAAAAAAwMAAAAAAAAAAAA%3D&config=H4sIAAAAAAAAA1WPSw7DIAwF9zkF8rrbdtE79BCIOhERP9mOVBTl7oUE0maH3xszsA5KwcwGnmotxzIkTYx0ziXhHER%2FSgKSE7IhmwRuvRWu1agd4x5tRwOiaUKpW8j3hoOLkbHjLfM22DH%2FC030iZD5ClZUh8nhVTc0Jfj4XvayfaQ%2B9tA%2F4Ad12XkxWH71TaEFh%2B0LYuVI0xQBAAA%3D
SWC Info output
No response
Expected behavior
The website should be available
Actual behavior
No response
Version
0
Additional context
No response

It's not managed by the SWC team. Closing as not actionable.


Many gradle updates and added runtime permission check

@djnotes Thank you very much for your pull request.

No problemThank you for the nice job
Sent from Yahoo Mail on Android
On Tue, Apr 10, 2018 at 10:12 PM, Akshika<EMAIL_ADDRESS>wrote:
@djnotes Thank you very much for your pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.