Ability to mark/star messages

Discuss this once with Mario if marking the message is actually required? We do have it on android but I am not sure about that. There are chances that it may be removed as it is not much of a use.

Will do when I come to this

I am not sure, if this is a priority now, cause this kind of "star" should be implemented in the server as well. So, messages show up as starred on all clients.
@chiragw15 I think this is not the case at the moment with the Android app.
As a rule of thumb - if Google Assistant or Siri has it, then we should have it. If not, then it is lower priority.

@mariobehling In android app we have this feature to star the message but it is done locally only (storing it in android database) and not related to server. So, it won't be displayed on all clients. Google assistant doesn't have this feature too(don't know about siri). This is the reason I asked @chashmeetsingh to confirm it once from you. So, I think this can be delayed for now in IOS and other clients. And for android, what do you suggest? Since it is already implemented, should we remove it or keep it?

Is there any use case for the same? Why are we actually starting the messages? @chiragw15

Not much but maybe a case when susi replies with something and user finds it important and may need it in future. So, he may star it and whenever in future he wants it, he may look up for it in starred messages. It has limited use thats why I am asking it to delay it for now.

I suppose if something's impt. user would prefer to create an event, save in calendar or add in the notes. I guess that's why Siri or Assistant do not have this feature. What do you think?

Yup we have an issue for reminder skill. https://github.com/fossasia/susi_skill_data/issues/108. We can also create a skill to add something to notes.

Ok, I am closing this for now as it does not seem a priority. Thanks for your input!


A DNX runtime has not been installed.

After upgrading to VS2015 RC, publishing stopped working (right click on the project in Solution Explorer, click "Publish") with the error
All packages are already installed and there is nothing to restore.
NuGet package restore finished.
1>------ Build started: Project: Xxx.Web, Configuration: Debug Any CPU ------
1>
1>  Build succeeded.
1>           0 Warning(s).
1>           0 Error(s).
1>
1>  Time elapsed 00:00:00.3450000
1>
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
Connecting to C:\Temp\Xxx_drop...
A DNX runtime has not been installed.

I've done dnvm upgrade and here's the dnvm list as of now
Active Version           Runtime Architecture Location                           Alias
------ -------           ------- ------------ --------                           -----
       1.0.0-beta4       clr     x64          C:\Users\akazyrevich\.dnx\runtimes
       1.0.0-beta4       clr     x86          C:\Users\akazyrevich\.dnx\runtimes
       1.0.0-beta4       coreclr x64          C:\Users\akazyrevich\.dnx\runtimes
       1.0.0-beta4       coreclr x86          C:\Users\akazyrevich\.dnx\runtimes
       1.0.0-beta4-11271 clr     x86          C:\Users\akazyrevich\.dnx\runtimes
       1.0.0-beta4-11271 coreclr x86          C:\Users\akazyrevich\.dnx\runtimes
       1.0.0-beta4-11566 clr     x86          C:\Users\akazyrevich\.dnx\runtimes default
  *    1.0.0-beta4-11566 coreclr x86          C:\Users\akazyrevich\.dnx\runtimes

Most likely I'm just missing something on my side - but is it possible to specify in the error, which runtime exactly is missing?

Reported on dnvm instead https://github.com/aspnet/dnvm/issues/264


⚠ API - RSS3 Domain has degraded performance

In ec86daa, API - RSS3 Domain ($RSS3_DOMAIN_API_URL) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: API - RSS3 Domain performance has improved in fbdc58b.


feat: ESM support

Description
Currently cdk-nag cannot be used for ESM modules. As I'm using SST as opposed to CDK I get all these __filename not supported errors.
Use Case
I'm using SST to build a lot of my CDK stacks in order to be more productive while developing and debugging lambdas.
Proposed Solution
This could be fixed in the library with a polyfill or by switching to ESM instead of commonjs.
Other information
No response
Acknowledge

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

Thanks for reporting! I am in no means an expert in this area, but from my initial research it seems like switching to ESM is not an option as it would  break CJS users (which I would assume is the vast majority of users).
I will have to do further research into an appropriate pollyfill for this use case. PRs and suggestions are welcome!


Searching for new contacts always returns 'No Results'

2016-02-02 00:24:37.672 Q-municate[4663:1404220] [QBCore] Request URL:https://api.quickblox.com/users/by_full_name.json?full_name=M&page=1&per_page=50
2016-02-02 00:24:37.674 Q-municate[4663:1404220] [QBCore] Request method: GET
2016-02-02 00:24:37.675 Q-municate[4663:1404220] [QBCore] Request parameters:{
"full_name" = M;
page = 1;
"per_page" = 50;
}
2016-02-02 00:24:37.675 Q-municate[4663:1404220] [QBCore] Request headers: {
"Content-Type" = "application/json";
"QB-OS" = "iOS 9.2.1";
"QB-SDK" = "iOS <IP_ADDRESS>";
"QB-Token" = 09f8699c900b665e51fcc302b705f1e4fe3f69c8;
"QuickBlox-REST-API-Version" = "0.1.1";
}
2016-02-02 00:24:38.084 Q-municate[4663:1404436] [QBCore] Response error: Error Domain=com.alamofire.error.serialization.response Code=-1011 "Request failed: forbidden (403)" UserInfo={com.alamofire.serialization.response.error.response=<NSHTTPURLResponse: 0x159243cb0> { URL: https://api.quickblox.com/users/by_full_name.json?full_name=M&page=1&per_page=50 } { status code: 403, headers {
"Access-Control-Allow-Origin" = "*";
"Cache-Control" = "no-cache";
Connection = "keep-alive";
"Content-Length" = 33;
"Content-Type" = "application/json; charset=utf-8";
Date = "Tue, 02 Feb 2016 08:24:38 GMT";
"QB-Token-ExpirationDate" = "2016-02-02 10:14:35 UTC";
"QuickBlox-REST-API-Version" = "0.1.1";
Server = "nginx/1.8.0";
Status = "403 Forbidden";
"X-Rack-Cache" = miss;
"X-Request-Id" = b9617af21d6df7675e76270acb19c36e;
"X-Runtime" = "0.063898";
"X-UA-Compatible" = "IE=Edge,chrome=1";
} }, NSErrorFailingURLKey=https://api.quickblox.com/users/by_full_name.json?full_name=M&page=1&per_page=50, com.alamofire.serialization.response.error.data=<7b226572 726f7273 223a7b22 62617365 223a5b22 466f7262 69646465 6e225d7d 7d>, NSLocalizedDescription=Request failed: forbidden (403)}

Hi!
There can only be 2 reasons.
It is not allowed in settings of your application to download users http://admin.quickblox.com/apps/YOUR_APP_ID/settings
Check "Allow to retrieve a list of users
2.You have created a session without user. ( You have completed this step already )
[QBRequest logInWithUserLogin:@"login" password:@"password"
successBlock:[self successBlock] errorBlock:[self errorBlock]];

We haven't heard any updates from you for a long time. I'm closing this issue for tracking purposes.
If you are still having any troubles, feel free to create separate issue.


fix(detail panel): Fix duplication of work item

When we add a work item using the detail panel the work item gets saved but the panel does not get the newly created work item. This happens as un-subscribe gets called and the GET on the work item gets cancelled so the panel remains as is.

@nimishamukherjee snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1980-fabric8-planner.int.rdu2c.fabric8.io

[test]


USB not automatically enabled when USB_UART_CONSOLE is set

Describe the bug
In Zephyr 2.4, the usb_enable() function was added with a message that it must be used to start USB support during the application, however, with a note that this would not be required if USB_UART_CONSOLE is set:
The usb_enable() function, which, for some samples, was invoked automatically on system boot up, now needs to be explicitly called by the application in order to enable the USB subsystem. If your application relies on any of the following Kconfig options, then it shall also enable the USB subsystem:
    CONFIG_USB_DEVICE_NETWORK_ECM
    CONFIG_USB_DEVICE_NETWORK_EEM
    CONFIG_USB_DEVICE_NETWORK_RNDIS
    CONFIG_TRACING_BACKEND_USB
    **CONFIG_USB_UART_CONSOLE**

However when testing 265cdf8dc6d08320665c1f898bce5403eb4df1a8 I find this statement to be incorrect and I have to manually add usb_enable(NULL); to a sample application to get the USB CDC port started despite this being set in the configuration:
grep -r "USB_UART_CONSOLE" zephyr/.config
CONFIG_USB_UART_CONSOLE=y

To Reproduce
Build a sample application for a board with a USB CDC port used for the console, I am testing with bl654_usb and samples/philosophers, flash to the device and no USB device will be enumerated. Then add this to src/main.c:
void main(void)
{
        usb_enable(NULL);

Build and flash the application, suddenly USB works.
Expected behavior
USB to work without the above function call
Impact
Showstopper, the bl654_usb board is entirely broken because of this bug
Logs and console output
Output before change:
dmesg | tail
[ 7760.180521] usb 3-13: new full-speed USB device number 39 using xhci_hcd
[ 7760.311121] usb 3-13: New USB device found, idVendor=1915, idProduct=521f, bcdDevice= 1.00
[ 7760.311125] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7760.311127] usb 3-13: Product: Nordic Open DFU Bootloader
[ 7760.311129] usb 3-13: Manufacturer: Laird Connectivity
[ 7760.311130] usb 3-13: SerialNumber: CE7B109A717C
[ 7760.314012] cdc_acm 3-13:1.0: ttyACM0: USB ACM device
[ 7774.686606] usb 3-13: USB disconnect, device number 39 <-- Bootloader, no USB enumeration after bootloader exits

lsusb | grep Nordic

Output after change:
dmesg | tail
[ 7855.047350] usb 3-13: new full-speed USB device number 40 using xhci_hcd
[ 7855.176054] usb 3-13: New USB device found, idVendor=1915, idProduct=521f, bcdDevice= 1.00
[ 7855.176059] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7855.176061] usb 3-13: Product: Nordic Open DFU Bootloader
[ 7855.176062] usb 3-13: Manufacturer: Laird Connectivity
[ 7855.176063] usb 3-13: SerialNumber: CE7B109A717C
[ 7855.178549] cdc_acm 3-13:1.0: ttyACM0: USB ACM device
[ 7867.228169] usb 3-13: USB disconnect, device number 40
[ 7868.295407] usb 3-13: new full-speed USB device number 41 using xhci_hcd
[ 7868.424362] usb 3-13: New USB device found, idVendor=2fe3, idProduct=0100, bcdDevice= 2.07
[ 7868.424367] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7868.424369] usb 3-13: Product: USB-DEV
[ 7868.424370] usb 3-13: Manufacturer: ZEPHYR
[ 7868.424371] usb 3-13: SerialNumber: 377ED198E19E7477
[ 7868.427149] cdc_acm 3-13:1.0: ttyACM0: USB ACM device

lsusb | grep Nordic
Bus 003 Device 041: ID 2fe3:0100 NordicSemiconductor USB-DEV

Environment (please complete the following information):

OS: Debian linux, also tried on windows 10
Toolchain: Zephyr SDK 0.13.1
Commit SHA or Version used: 265cdf8dc6d08320665c1f898bce5403eb4df1a8

Describe the bug In Zephyr 2.4, the usb_enable() function was added with a message that it must be used to start USB support during the application, however, with a note that this would not be required if USB_UART_CONSOLE is set:
The usb_enable() function, which, for some samples, was invoked automatically on system boot up, now needs to be explicitly called by the application in order to enable the USB subsystem. If your application relies on any of the following Kconfig options, then it shall also enable the USB subsystem:
    CONFIG_USB_DEVICE_NETWORK_ECM
    CONFIG_USB_DEVICE_NETWORK_EEM
    CONFIG_USB_DEVICE_NETWORK_RNDIS
    CONFIG_TRACING_BACKEND_USB
    **CONFIG_USB_UART_CONSOLE**

No, please read it again:
"If your application relies on any of the following Kconfig options, then it shall also enable the USB subsystem:
....
CONFIG_USB_UART_CONSOLE"
https://docs.zephyrproject.org/latest/releases/release-notes-2.4.html

@jfischer-no So what's the idea for boards with a USB CDC port then sample-wise so that the USB CDC port starts up open by default for console output as it would with a normal UART on other boards?

@jfischer-no So what's the idea for boards with a USB CDC port then sample-wise so that the USB CDC port starts up open by default for console output as it would with a normal UART on other boards?

The way it was solved for CDC ACM before version 2.4 had no technical advantages over "enable the USB subsystem in application code". There is currently no solution, and I know that it is not convenient for USB dongle like boards.


Allow ILC and Expert Mode to select mW-vs-PWM

addresses #159
also refactored LaserPowerControl with new ctl architecture

Where was it located before?

Where was it located before?

Sorry, can you expand on that?

Sorry, can you expand on that?

Referring to the original location of the button.

Ah.  It had been atop the Measurements clipboard, because it initially only affected Thumbnails (was introduced as a replacement for Thumbnail tooltips).


Update index.md

To make the documents more user-friendly, we need to break long lines in sample HTML/JavaScript code into short lines to avoid horizontal scrollbars caused by limited column width

ah, sorry, I saw the your comment.
LGTM.

@kazupon Thanks for the quick response! In this case document users have to use a horizontal scrollbar to view the hidden part of only one long line, but if we don't pay attention to source code line length sometimes many lines could be hidden, causing significant usability issues. You guys have done a great job in making Vue user-friendly. Let's keep the momentum going!


I got a strange behavior on real devices Android versions 9, 10 with rendering Object with Animation

Hi!
I got a strange behavior on real devices Android versions 9, 10.
Flutter 3.3.3 and higher.
Object motion animation is missing.
On emulators everything is fine.
On Ios everything is fine.
On a real device Android version 13 all is good.
I have attached a video with an example of the problem.
https://youtu.be/6BazKnSoMBk

Same issue with Android 10. Also everything fine on debug mode. It happens with release.


Remove flux limits

Working branch to remove flux limit code and restore previous removed data.
DO NOT MERGE
Closes #206

Codecov Report

Merging #210 into master will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #210      +/-   ##
==========================================
- Coverage   96.87%   96.71%   -0.17%
==========================================
  Files           8        8
  Lines         801      761      -40
==========================================
- Hits          776      736      -40
  Misses         25       25

Impacted Files
Coverage Δ

R/parser.R
97.54% <ø> (-0.11%)
:arrow_down:

R/qaqc.R
100.00% <ø> (ø)

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 b84c08c...17101cc. Read the comment docs.


[VRC9] Bedrock npm

Is it possible to get npm updated so that we can test theme building workflow in RC9? Currently following the docs here provides Bootstrap 4.3.1 and presumably equally outdated Bedrock?
https://documentation.concretecms.org/developers/appendix/concrete-cms-bedrock-foundation-concrete-and-concrete-themes
https://www.npmjs.com/package/@concretecms/bedrock

I have updated the bedrock docs to make it clear that they're (now) built on Bootstrap 5. Thanks!
Right now it's going to be difficult to use bedrock using those exact instructions until the 9.0rc branch is merged back into master. That can't happen yet but it will happen prior to the full 9.0 release.


Implement USR2 signal handler

Implements USR2 signal interpreter on a new tokio thread which can then be used by the applications to run custom business logic like:

Go into maintenance mode/take yourself out of the working pool
Change application behaviour on an individual node basis
Debug out current state of running applications/like a statuscheck

Initially, we can use this signal handler to move a node out of the working pool/for maintenance mode to prevent write corruption while updating the application binaries.
With this PR, it just logs out a message after the message has been caught successfully

chore: Fixes minor variable-naming issue within rebaser which was inconsistent based on the other binaries.

Superseeding with new branch


Towny commands not working

This has been discussed a bit on irc, but I thought I may put it here as well.
According to the wiki, depenizen should add several commands for towny, but none of them are working (unknown sub-command errors). It seems that part of the code concerning handling them is missing.

Based on what @Morphan1 has said... I'd say this is invalid for now.


(visualstudiocode) Get-PackageParameters is not recognized when installing using Install-Package

While PackageManagement believe's it's installed VisualStudioCode 1.8.1 it's not actually completing and it appears to be failing on one of the Chocolatey core extensions for some reason.  Below is the command line I was using as well as the output of the verbose/debug logs.
 Name='VisualStudioCode'
Using the provider 'Chocolatey' for searching packages.
00:00:01.1532573 PackageProvider::FindPackage with name VisualStudioCode
00:00:01.1536117 Calling SearchForPackages After Select 1
00:00:01.1555751 Calling 'Chocolatey::FindPackage' 'VisualStudioCode','','','','0'
00:00:01.1556174 Iterating
00:00:01.1883347 Yielding
00:00:01.1886588 Done Iterating
00:00:01.1930389 Calling 'Chocolatey::GetInstalledPackages' 'VisualStudioCode','1.8.1','',''
00:00:01.9540245 Calling 'Chocolatey::InstallPackage'
'$aHR0cDovL2Nob2NvbGF0ZXkub3JnL2FwaS92Mi8=\VmlzdWFsU3R1ZGlvQ29kZQ==\MS44LjE=\'
NuGet: Attempting to resolve dependency 'chocolatey-core.extension (≥ 1.0.4)'.
NuGet: Attempting to resolve dependency 'DotNet4.5.2'.
NuGet: Installing 'visualstudiocode 1.8.1'.
NuGet: Successfully installed 'visualstudiocode 1.8.1'.
Exception : DefaultDomain//CommandNotFoundException/The term 'Get-PackageParameters' is not recognized as the name of
a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
   at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
   at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input,
PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1
output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
   at Microsoft.PackageManagement.ChocolateyPrototype.ChocolateyRequest.Invoke(String script)
   at Microsoft.PackageManagement.ChocolateyPrototype.ChocolateyRequest.InvokeChocolateyScript(String path, String
workingDirectory)

Name                           Version          Source           Summary
----                           -------          ------           -------
VisualStudioCode               1.8.1            chocolatey       Visual Studio Code

I've confirmed that I have the chocolatey-core.extension.1.0.5 installed (or at least the folder shows up in C:\Chocolatey\lib.  Previous versions of this installer have worked through the PackageManagement module but it doesn't appear to work any longer.  If you need additional information let me know.

I wonder if maybe the powershell PackageManagement don't support importing chocolatey extensions (I'm almost sure I read somewhere that the provider used is using several years old code).
Have you tried installing it directly with choco install visualstudiocode?
I don't really have any experience when it comes to the Install-Module cmdlet, so let me reference some people that may help on this.
/cc @ferventcoder @gep13 @pascalberger

It doesn't - please use choco until you hear otherwise. Follow this thread - https://github.com/chocolatey/chocolatey-oneget/issues/5


simple style attribute bindings and styleObject filter not working in IE11 (maybe other versions as well)

see example in IE11 (other IEs not tested yet) here:
http://jsfiddle.net/k4L88/6/ - styleObject
http://jsfiddle.net/k4L88/7/ - simple style binding
Text in span on line 10 should be green but is red in IE. Chrome and Firefox are working just fine.

Kabunga !!!


Did I break the testing workflow?

I didn't change any code in 4d0dc3936f4a7057f3438ab4757c97b07c75bfa8 (added some mesh files, added the start of a visualization script) but the testing workflow is failing. I did a fresh pull, but I hadn't updated my local env in while. Could that have caused problems when pushing to remote? Sorry!

Apparently just needed a re-run! All passed now. Sorry for the false alarm!

Interesting to read that distutils will go away as of Python 3.12, but it does sound like pinning to an older version of setuptools will keep things functional?
I know I had encountered some issues with the testing workflow in the past, but now I'll know to try a rerun if I get failed tests upon committing.

I'm not certain.  What do you think about pinging Ben about this since it seems to be related to the building of okada_wrapper?


Don't use PyFloat_AS_DOUBLE() as an l-value

Use copysign() with PyFloat_FromDouble() in HelpersConstantsBlob.c.
Add PyFloat_SET_DOUBLE() function and use it in in-place operations.

Python 3.12 PyFloat_AS_DOUBLE() can no longer be used as an l-value: https://github.com/python/cpython/commit/02f72b8b938e301bbaaf0142547014e074bd564c
Thank your for contributing to Nuitka!
!! Please check that you select the develop branch (details see below link) !!
Before submitting a PR, please review the guidelines:
Contributing Guidelines
What does this PR do?
Why was it initiated? Any relevant Issues?
PR Checklist

[x] Correct base branch selected? Should be develop branch.
[ ] Enabled commit hook or executed ./bin/autoformat-nuitka-source.
[ ] All tests still pass. Check the Developer Manual about Running the Tests.
There are GitHub Actions tests that cover the most important
things however, and you are welcome to rely on those, but they might not
cover enough.
[ ] Ideally new features or fixed regressions ought to be covered via new tests.
[ ] Ideally new or changed features have documentation updates.

Thank you so much for pointing this out and sharing the information.
I am having 3.11 compile some things at this time, with --experimental=python3.12 you could probably compile it using current develop branch. As Nuitka is crazy enough to support all kinds of older Python versions, it will probably require some sort of abstraction to work with older ones and backport of the macro in case it is not defined. I didn't find a 3.12 branch yet. Can you point me to the macro definition on your branch?

Sorry for my bad reading skills, you of course linked the commit:
static inline double PyFloat_AS_DOUBLE(PyObject *op) {
    return _PyFloat_CAST(op)->ob_fval;
}
#define PyFloat_AS_DOUBLE(op) PyFloat_AS_DOUBLE(_PyObject_CAST(op))

I didn't find PyFloat_SET_DOUBLE but I imagine it follows what happened to Py_SIZE and Py_SET_SIZE in 3.11 before, and I agree, it makes sense. I will change it as suggested. Your Jinja2 template change removed a branch though, that I would like to keep, so I am going to make the change now in a similar fashion as you suggested.

I didn't find PyFloat_SET_DOUBLE

I added it to Nuitka. It doesn't exist in Python 3.12. Maybe it's a bad name. My implementation modifies a reference to a pointer: PyObject**. Maybe it's a bad name. I don't know Nuitka naming convention.

Your Jinja2 template change removed a branch though

Yeah, I moved the code into a function, to avoid code duplication. The function can be declared as a static inline function, if you prefer.

I will change it as suggested

Great! Thanks!


Fix #9 and Fix #10 IndexingError('Too many indexers')

@MaxHalford I'm hitting the same problem. Is this PR going to be accepted?

There we go! Sorry for the delay.

IndexingError: Too many indexers.
Iam also getting the error, i tried "pip install prince" but it wont working


[fix] Install ruby and SASS with Docker [Closes #789]

Same as #789 but squashed too one commit.
@liuhill If you want to squash yours and get yours merged in, go for it! I'm just trying to get a handful of these bug fixes merged in.

LGTM

@lirantal Are we waiting on something particular for this PR?

Nope, I'll merge it in.


New Posh-SSH release to support new key exchange algorithms from upstream lib SSH.NET

This issue relates to #314
Has a new version of SSH.NET been released so additional key exchange algorithms are supported?

Check the beta 1 release in gallery and here in github :)
Sent from my iPhone

On Jun 26, 2020, at 5:16 AM, dbrennand<EMAIL_ADDRESS>wrote:

This issue relates to #314
Has a new version of SSH.NET been released so additional key exchange algorithms are supported?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Cool, I will test on Monday 😉

Did some testing. Seems alright apart from one issue. I commented here: https://github.com/darkoperator/Posh-SSH/issues/329#issuecomment-651093666

-Force will simply not check if the key is valid and will not even save it if -AcceptKey is specified so my guess it is in the key format but if it works at the end that is the part that is confusing. Will try to generate a RSA key in the old OpenSSH format since the new one is only supported for Curve keys and try to authenticate with that, sadly SSH.Net http://ssh.net/ sis not add support for the new format for DSA and RSA kets. There is no deep SSH inspection like a Fortinet device in front of the server? Seen that break

No nothing like that in front of the server.

This issue is resolved.
The -Force parameter is a good workaround. I believe the issue resolved when I re-deployed the piece of infrastructure.


Question: Collection names.  Length and total?

Is the 3000 bytes limit of a Collection name the total byte limit for a single collection in a single database?  Or we only have 3000 bytes total for a combination of all the names of all collections in a single database?
This basically comes to about 30 characters in length for the name.  Can we expand this significantly?  We would like to use our class names as the collection names, and they can run up to 80-100 characters in length sometimes.
If the collection name is being used for storage with individual properties or something, is it possible to allow an "alias" collection name that we can put in a large string and allow us to get the collection by that alias?
Thanks

Hi @dfarrNTST,
3000 bytes for all collection names is limited becase all collections names (and link pointer, +6 bytes) must been stored in header page (each page has 4069 bytes). So it's not possible be larger than this.
About 30 chars per collection it's just an pattern represented here: ^[\w-]{1,30}$ (CollectionPage.cs)
In v3.1, it's possible now write your own ResolveCollectionName function based on your <T> type. Using this, now it's possible pass null in collection names (in LiteDatabse or LiteRepository) to use this convention. For this, try:
BsonMapper.Global.ResolveCollectionName = (type) => .....

Hi! With the objective of organizing our issues, we are closing old unsolved issues. Please check the latest version of LiteDB and open a new issue if your problem/question/suggestion still applies. Thanks!


Red and blue color components are inverted

Hi, using the latest release, the following image should be rendered red, but it is blue.
Result:

Expected result:

-3color.svg.zip

Was it normal with previous release?

I have just tested it in linux with latest svgren and it draws red circle. Which system are you running it on?

Or you're right @igagis, bgra was set to true. My mistake, sorry


Just a Thank you

I've been searching every day for the last 3 weeks for a noclip mode  for Deus Ex Mankind Divided and have not had any luck. This is the next best thing and I just want to say thank you for creating this amazing tool and making it work with many games.  Would love to see a noclip mode for some games as well. Not sure how difficult it would be with the toolset + skills you have.
I am kind of new to Github and do not know of another way  to contact someone  besides using the issues tab.
Thanks again.

You're welcome :) Enjoy :)
I've also created a console unlocker for  Unreal Engine 4 games, which works in many games and which allows you to enable the debug camera. See: https://framedsc.github.io/GeneralGuides/universal_ue4_consoleunlocker.htm
In case you have one of the many games supported by it ;)

Wow, you are quite talented!  I will definitely use the console unlocker as well as the Camera System.
Thanks again. It's much  appreciated!


Easy dangling PyObject with GILPool

This sample code produces a dangling PyObject after the GILPool is dropped:
use pyo3::prelude::*;
use pyo3::{ffi, GILPool, AsPyPointer};
use pyo3::types::PyList;

fn main() {
    let gil = Python::acquire_gil();
    let py = gil.python();
    let obj;

    {
        let pool = GILPool::new(py);
        obj = py.eval("object()", None, None).unwrap();
        println!("Count before pool drop {}", unsafe { ffi::Py_REFCNT(obj.as_ptr()) });
    }

    println!("Count after pool drop {}", unsafe { ffi::Py_REFCNT(obj.as_ptr()) });
}

As seen by the output:
Count before pool drop 1
Count after pool drop<PHONE_NUMBER>104

I think what must be going on is that obj has a lifetime tied to py, but it is actually only valid for the lifetime of pool. Because of the wrong lifetime semantics the Rust compiler lets us create the dangling pointer.
I'm not sure yet exactly what the solution should be. Maybe the change to GILPool / py relationship proposed in #800 will mitigate this issue.
I wonder whether this issue combined with #756 is telling us that the right design is really PyAny<'a> as proposed in #679

FWIW after #869 then we will need one line of unsafe here, so the original title will no longer apply. But I still think the point stands whether PyAny<'a> is still the right design - because then the refcount drop can be done when the PyAny<'a> drops, not when the GILPool drops.

But I still think the point stands whether PyAny<'a> is still the right design

I'm sorry but I can't understand why this problem is related to PyAny<'a>...
It's just my own view, but PyAny<'a>'s Drop implementation would be
struct PyAny<'a>(...);
impl PyAny {
    fn from_borrowed(ptr: ...) -> Self {
        Py_INCREF(ptr);
        Self(ptr)
    }
    fn from_owned(ptr: ...) -> Self {
        Self(ptr)
    }
}

impl<'a> Drop for PyAny<'a> {
    fn drop(&mut self) {
        Py_DECREF(self.0)
    }
}

So its reference count is not affected by GILPool or GILGuard and thus cannot be negative.

@kngwyu I agree with what what you say and how you propose PyAny<'a> would work. This is what I was trying to say :smiley: . If we had PyAny<'a> then it would not have to worry about GILPool.

Ah, sorry, I just misread.

FWIW; the change to GILPool to make GILPool::new unsafe has helped make the original example sound, but there is still the following example code using acquire_gil instead:
fn main() {
  use pyo3::prelude::*;
  use pyo3::{ffi, GILPool, AsPyPointer};
  use pyo3::types::PyList;

  let gil = Python::acquire_gil();
  let py = gil.python();
  let obj;

  {
    let gil2 = Python::acquire_gil();
    obj = py.eval("object()", None, None).unwrap();
    println!("Count before gil2 drop {}", unsafe { ffi::Py_REFCNT(obj.as_ptr()) });
  }

  println!("Count after gil2 drop {}", unsafe { ffi::Py_REFCNT(obj.as_ptr()) });
}

// Output:
// Count before gil2 drop 1
// Count after gil2 drop<PHONE_NUMBER>552


add place "hamlet"

You could add v = "hamlet" in places, with the zoom level that you think is appropriate.
In less populated areas this class is interesting for cross country.
Thanks!

Thanks for reporting, I've added hamlet, isolated_dwelling and locality.

They are at zoom 13 or whenever they appear.

Moved them over to zoom 14 to provide cleaner map.

I already inserted the new version in XC Track, I liked it a lot.


Series[Timestamp].diff() should return Series[Timedelta]

Describe the bug
Series[Timestamp].diff() returns Series[Timedelta] but stubs indicate it's Series[Timestamp] instead.
To Reproduce
# python bug.py & mypy bug.py & pyright bug.py
from __future__ import annotations

from typing import TYPE_CHECKING, reveal_type

import pandas as pd

if TYPE_CHECKING:
    from pandas.core.series import TimedeltaSeries, TimestampSeries

def fun1(times: pd.Series[pd.Timestamp]) -> pd.Series[pd.Timedelta]:
    reveal_type(times)
    reveal_type(times.diff())
    print(type(times[1]))
    print(type(times.diff()[1]))
    return times.diff()

def fun2(times: TimestampSeries) -> TimedeltaSeries:
    reveal_type(times)
    reveal_type(times.diff())
    print(type(times[1]))
    print(type(times.diff()[1]))
    return times.diff()

times = pd.Series([pd.Timestamp(0), pd.Timestamp(0)])
fun1(times)
fun2(times)

Output:
Runtime type is 'Series'
Runtime type is 'Series'
<class 'pandas._libs.tslibs.timestamps.Timestamp'>
<class 'pandas._libs.tslibs.timedeltas.Timedelta'>
Runtime type is 'Series'
Runtime type is 'Series'
<class 'pandas._libs.tslibs.timestamps.Timestamp'>
<class 'pandas._libs.tslibs.timedeltas.Timedelta'>
bug.py:13: note: Revealed type is "pandas.core.series.Series[pandas._libs.tslibs.timestamps.Timestamp]"
bug.py:14: note: Revealed type is "pandas.core.series.Series[pandas._libs.tslibs.timestamps.Timestamp]"
bug.py:17: error: Incompatible return value type (got "Series[Timestamp]", expected "Series[Timedelta]")  [return-value]
bug.py:21: note: Revealed type is "pandas.core.series.TimestampSeries"
bug.py:22: note: Revealed type is "pandas.core.series.Series[pandas._libs.tslibs.timestamps.Timestamp]"
bug.py:25: error: Incompatible return value type (got "Series[Timestamp]", expected "TimedeltaSeries")  [return-value]
Found 2 errors in 1 file (checked 1 source file)
C:\Build\project\bug.py
  C:\Build\project\bug.py:13:17 - information: Type of "times" is "Series[Timestamp]"
  C:\Build\project\bug.py:14:17 - information: Type of "times.diff()" is "Series[Timestamp]"
  C:\Build\project\bug.py:17:12 - error: Expression of type "Series[Timestamp]" cannot be assigned to return type "Series[Timedelta]"
    "Series[Timestamp]" is incompatible with "Series[Timedelta]"
      Type parameter "S1@Series" is invariant, but "Timestamp" is not the same as "Timedelta" (reportGeneralTypeIssues)
  C:\Build\project\bug.py:21:17 - information: Type of "times" is "TimestampSeries"
  C:\Build\project\bug.py:22:17 - information: Type of "times.diff()" is "Series[Timestamp]"
  C:\Build\project\bug.py:25:12 - error: Expression of type "Series[Timestamp]" cannot be assigned to return type "TimedeltaSeries"
    "Series[Timestamp]" is incompatible with "TimedeltaSeries" (reportGeneralTypeIssues)
2 errors, 0 warnings, 4 informations

Please complete the following information:

Windows 10 22H2
Python 3.12.0
mypy==1.7.1, pyright==1.1.337, pandas-stubs==<IP_ADDRESS>928

Additional context
I tried both Series[Timestamp] and TimestampSeries due to https://github.com/pandas-dev/pandas-stubs/issues/673#issuecomment-1739434074
Possibly related: https://github.com/pandas-dev/pandas-stubs/issues/718

Thanks for the report.  I think we have to add diff() as a method to TimestampSeries .

looking at series.diff documentation it looks like diff of Series[int] returns Series[float] and I made a test to confirm this. Current stubs returns Series[int]. I am not sure this is a correct behavior of pandas?

looking at series.diff documentation it looks like diff of Series[int] returns Series[float] and I made a test to confirm this. Current stubs returns Series[int]. I am not sure this is a correct behavior of pandas?

Yes, it seems that's an error in the stub for Series.diff().  So you'd have to make 2 changes to address this.  One in Series.diff(), so it returns Series[float].  The other in TimestampSeries so that it returns TimedeltaSeries

We have to manage objects also from bool and pd.Period. pd.Interval will require a Never

float ➡  float
int ➡  float
timestamp ➡  timedelta
period ➡  object
timedelta ➡  timedelta64
interval ➡  TypeError: IntervalArray has no 'diff' method. Convert to a suitable dtype prior to calling 'diff'.
bool ➡  object

Any other object people can think of before starting to code ?

Any other object people can think of before starting to code ?

You'd have to look at the definition of S1 to make sure you've handled all the cases.
You might want to look at how we handle Series.__sub__() as a guide.  Whereever you see def __sub__( in series.pyi, I think you'd have a similar overload for Series.diff()
Thanks for looking into this.  It's non-trivial.

For info, if it is ok, I'll need to create new classes in series.pyi for Series[bool], Series[bytes], Series[complex] and Series[dtype]

For info, if it is ok, I'll need to create new classes in series.pyi for Series[bool], Series[bytes], Series[complex] and Series[dtype]

You shouldn't have to do this.  Just follow the pattern used for Series.__sub__() and other __sub__() declarations in series.pyi

Almost finished fixing this issue in https://github.com/mutricyl/pandas-stubs/tree/821-series_diff-timestamp2
however I have got an issue with check function when running pytests:
>       check(
            assert_type(
                pd.Series(
                    [datetime.datetime.now().date(), datetime.datetime.now().date()]
                ).diff(),
                "TimedeltaSeries",
            ),
            pd.Series,
            pd.Timedelta,
        )

This test fails in pytest with:
RuntimeError: Expected type '<class 'pandas._libs.tslibs.timedeltas.Timedelta'>' but got '<class 'pandas._libs.tslibs.nattype.NaTTyp

>>> pd.Series( [datetime.datetime.now().date(), datetime.datetime.now().date()]  ).diff()
0      NaT
1   0 days
dtype: timedelta64[ns]

Looking at check function source code for series it uses the first item to determine the type:
    if isinstance(actual, pd.Series):
        value = actual.iloc[0]

first item of .diff() series is always some kind of None/NaN/NaT... altough type(NaN) is float which make it work for common case, type(NaT) is not timedelta or similar.
Any advise on how to solve this particular case @Dr-Irv  ?

Very interesting use case where how we designed check() doesn't work for Series.diff().
Do the following:  Introduce a parameter to check() called index_to_check_for_type: Literal[0,-1] = 0 and use actual.iloc[index_to_check_for_type] instead of actual.iloc[0] in the line you quoted.  Then for your test, you just add the parameter index_to_check_for_type = -1 in the check() call and the existing calls will all work, and yours should as well.

#907 closed this, but I am still seeing issues with the code example above. I minimized the code into this example:
# python bug.py & mypy bug.py & pyright bug.py
from __future__ import annotations

from typing import reveal_type

import pandas as pd

def fun(stamps: pd.Series[pd.Timestamp]) -> pd.Series[pd.Timedelta]:
    reveal_type(stamps)
    print(type(stamps[1]))

    deltas = stamps.diff()

    reveal_type(deltas)
    print(type(deltas[1]))

    return deltas

times = pd.Series([pd.Timestamp(0), pd.Timestamp(0)])
fun(times)

python says:
Runtime type is 'Series'
<class 'pandas._libs.tslibs.timestamps.Timestamp'>
Runtime type is 'Series'
<class 'pandas._libs.tslibs.timedeltas.Timedelta'>

So runtime behavior is as expected.
However, mypy (as pyright) thinks deltas is a series of float still:
bug.py:9: note: Revealed type is "pandas.core.series.Series[pandas._libs.tslibs.timestamps.Timestamp]"
bug.py:14: note: Revealed type is "pandas.core.series.Series[builtins.float]"
bug.py:17: error: Incompatible return value type (got "Series[float]", expected "Series[Timedelta]")  [return-value]
Found 1 error in 1 file (checked 1 source file)

This is with version <IP_ADDRESS>514.

As a workaround, I could replace pd.Series[pd.Timestamp] by TimestampSeries in my code, but then the type checkers don't allow this assignment:
Before (working):
times: pd.Series[pd.Timestamp] = df[TIME_COL]

After (not working):
times: TimestampSeries = df[TIME_COL]

error: Incompatible types in assignment (expression has type "Series[Any]", variable has type "TimestampSeries")

As a workaround, I could replace pd.Series[pd.Timestamp] by TimestampSeries in my code, but then the type checkers don't allow this assignment:

That's the right workaround for your example

also, #718 seems to imply pd.Series is to prefer.

We had to introduce TimestampSeries and TimedeltaSeries to get around some issues with how mypy processes operators on generic classes.  That's why #718 is there - to see if that is still necessary, since mypy has evolved since then.  Having said that, making consistent behavior between pyright and mypy on this issue is a challenge.  See https://github.com/microsoft/pyright/issues/5216#issuecomment-1594046589

Before (working):
times: pd.Series[pd.Timestamp] = df[TIME_COL]

The reason that works is that we can't track the types of columns within a DataFrame.  So the type of df[TIME_COL] is a Series without a tracked dtype, and you're then assigning it to a Series with a known dtype.  If you wrote times: pd.Series[int] = df[TIME_COL], that would be accepted as well.

After (not working):
times: TimestampSeries = df[TIME_COL]

This is again related to how the type checker is handling the generic aspect of Series in typing, and that df[TIME_COL] doesn't have a dtype associated.
In general, whenever you refer to a column of a DataFrame, via df[TIME_COL], you can't assume the type and have to do a cast.  So what would work is:
times = cast("TimestampSeries", df[TIME_COL])

That's the right workaround for your example
...
times = cast("TimestampSeries", df[TIME_COL])

So one cast needs to be necessary at least. Accepting that, it makes sense doing it as early as possible to catch errors in the processing. Thanks a lot!


Location cannot be determined

Hi,
I installed this app on Samsung galaxy s5 and when I run this app then I get "Location cannot be determined"
My GPS is enabled and I have internet connection.
When I go to google maps , look on my current location and then return to this app then it is OK.
How can I fix it ?

Is it occurring on other mobile phones as well ?

Yes. I also run on Nexus 4. I don't get a message "Location cannot be determined" but I also don't see any thing. After that I run google map and then return back to this app, then All is Ok.

@alexd555 do you have COARSE and FINE location enabled in android manifest?
https://github.com/Esri/nearby-android/blob/master/nearby-app/src/main/AndroidManifest.xml
and did you accept the permissions request for the app? if you reject the permissions request you will get this issue.

I did clone from the repository. That means that I have this configuration. @jf990

I wasn't able to reproduce this on devices I have currently (Samsung S6 and a Moto X). I'm not sure what could be causing problems on your devices. It's on my todo list to rework the permission handling soon which may end up fixing it.

This should be fixed with updates to target API level and some tweaks to the permission handling code put in place here: https://github.com/Esri/nearby-android/pull/83


Panic: Error occurs while running 'wake  runSim pioDUT' commands

Hi,
while running  wake runSim pioDUT . It throws the following error

PANIC: Error "gcc: could not find output file: build/api-generator-sifive/pioDUT/programs/demo/demo.elf" Nil
Requirement !panic_called failed at src/exception.cpp:69
ishita@DESKTOP-B4D4E03:~/workspace$

How do I fix this?

can you show the full log? It's hard to tell what the problem is just from these lines.

These are the warnings:
+ set -e
+ '[' 7 -ne 7 ']'
+ host=riscv64-unknown-elf
+ machine_name=pioDUT
+ machine_header=../pioDUT.h
+ machine_inline=../pioDUT-inline.h
+ platform_header=../pioDUT-platform.h
+ machine_ldscript=../pioDUT.lds
+ install_dir=..
++ pwd
+ machine_header=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT.h
++ pwd
+ machine_inline=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT-inline.h
++ pwd
+ platform_header=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT-platform.h
++ pwd
+ machine_ldscript=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT.lds
++ pwd
+ install_dir=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/..
+ export RISCV_PATH=
+ RISCV_PATH=
+ autoreconf -i
+ ./configure --host=riscv64-unknown-elf --disable-maintainer-mode --with-preconfigured --with-machine-inline --with-platform-header --with-machine-name=pioDUT --with-machine-header=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT.h --with-machine-inline=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT-inline.h --with-platform-header=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT-platform.h --with-machine-ldscript=/home/ishita/workspace/build/freedom-metal/pioDUT/freedom-metal/../pioDUT.lds --with-builtin-libgloss --prefix=
+ make 'RANLIB=riscv64-unknown-elf-ranlib -D' ARFLAGS=Dcr
src/drivers/fixed-clock.c: In function '__metal_driver_fixed_clock_get_rate_hz':
src/drivers/fixed-clock.c:14:44: warning: passing argument 1 of '__metal_driver_fixed_clock_rate' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
     return __metal_driver_fixed_clock_rate(gclk);
                                            ^~~~
In file included from src/drivers/fixed-clock.c:10:
./metal/machine.h:105:81: note: expected 'struct metal_clock *' but argument is of type 'const struct metal_clock *'
 static inline unsigned long __metal_driver_fixed_clock_rate(struct metal_clock *clock)
                                                             ~~~~~~~~~~~~~~~~~~~~^~~~~
ar: creating VTestDriver__ALL.a

Find the log here.
log.txt

Hi @ishitapvips, sorry for the delay. It seems like freedom-metal is not successfully compiling for you. Could you list the versions of Wit packages in your workspace to help us identify the specific versions being used? You can do this by uploading the contents of wit-lock.json, which can be found at the root directory of the workspace.

Hi @richardxia ,
Please find the content of wit-lock.json file
wit-lock.txt

hi @ishitapvips
can you rerun that command but with the -v flag e.g. wake -v 'runSim pioDUT' and post the log (the -v flag will tell wake to output stdout in addition to stderr). also are you sure you have published an environment json with an entry for riscv-tools/2019.05.0 like this one https://github.com/sifive/environment-blockci-sifive/blob/better-json-environment-runner/environment.json. you'll also need a wake file that publishes that path like this https://github.com/sifive/environment-blockci-sifive/blob/better-json-environment-runner/wake/environment.wake

Hi @albertchen-sifive
Firstly I didn't publish environment json as I was using environment-sanmateo . After publishing also It is giving same as above error
I have attached both the logs
log.txt
log_with_envjson.txt

Resolved with updating the drivers/metals version v0.1.0.


Use the original way of validating Bigtable Change Stream table existance to improve compatibility with testing

Use the original way of validating Bigtable Change Stream table existance to improve compatibility with testing.
In #31376 I moved around validation and introduced a different way of checking the existence of the Change Stream table using BigtableServiceFactory instead of BigtableChangeStreamAccessor. BigtableChangeStreamAccessor has some customization that is not included in BigtableServiceFactory and is needed for integration testing against different environments.
Ideally, we have only one way of interfacing with Bigtable services, so we would merge BigtableServiceFactory and BigtableChangeStreamAccessor. But meanwhile, we should revert back to using BigtableChangeStreamAccessor in the ChangeStream connector.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@jackdingilian for Bigtable review.

LGTM for bigtable


Pop up doesn't auto-close in non focused-window

For any feature request you can open a new discussion here:
https://github.com/Clooos/Bubble-Card/discussions/categories/feature-requests
For any question you can open a new discussion here:
https://github.com/Clooos/Bubble-Card/discussions/categories/q-a
Describe the bug
I have an autopop of a camera that pos automatically when someone rings, set with an auto-close timeout.
I have a PC with a chrome tab always open on a local HA server. When someone rings and the tab does not have focus the pop-up comes up, but never goes away, finally locking the tab: I have to force a refresh to make it go away.
To Reproduce
Steps to reproduce the behavior:

Set a pop-up with auto-close
leave browser unattended navigating a separate Tab
trigger the pop-up
wait until timeout expires

Expected behavior
The pop-up should auto close even if the window is not in focus.
YAML
If applicable, add any relevant YAML code.
type: vertical-stack
cards:
  - type: custom:bubble-card
    card_type: pop-up
    trigger_entity: binary_sensor.citofonato
    trigger_state: 'on'
    hash: '#citofonato'
    show_header: false
    auto_close: '5000'
    close_on_click: true
    trigger_close: true
  - type: custom:mushroom-template-card
    primary: >-
      Ultime immagini di: {%- set time = (as_timestamp(now()) -
      as_timestamp(states('input_datetime.citofono_ultima_chiamata'))) | int  %}

      {%- set minutes = ((time % 3600) // 60) %}

      {%- set minutes = '{} minuti'.format(minutes) if minutes > 0 else '' %}

      {%- set hours = ((time % 86400) // 3600) %}

      {%- set hours = '{} ore '.format(hours) if hours > 0 else '' %}

      {%- set days = (time // 86400) %}

      {%- set days = '{} giorno(i) '.format(days) if days > 0 else '' %}

      {{ 'Meno di 1 minuto' if time < 60 else days + hours + minutes }} fa
    secondary: ''
    icon: mdi:bell-ring
    icon_color: orange

[...] other cards in the vertical stack [...]

Informations (please complete the following information):

OS: Windows 10
Browser/App: Chrome
Bubble Card version: latest beta 2.3.0.beta-1
Home Assistant version: latest 2024.9.2

Thank you! 🍻

The issue is still there, I understand it's not urgent, but it's not clear if someone is looking on it.

Hi! I'm sorry for not having answered sooner, there are so many issues that it is not always easy to keep up, but I definitely need to take a look at this!

No problem, it was just so the issue is not deleted as stale. Take your time, I understand other issues might have priority.


Fix clippy::needless_lifetimes in Rust 1.83 and ShimLock ABI on ia32

Checklist

[ ] Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
[ ] Update the changelog (if necessary)

I'm not 100% sure that cdecl is what we want for ShimLock on ia32; the Rust docs are rather sparse, and shim doesn't document the protocol's ABI at all. But it at least compiles, which is better than sysv64.

Merging to unblock CI

Thanks for fixing this!


[.NET SDK] During OAuth Flow For 3rd Party Auth Provider, Sign In Button Does Not Launch Website

Bot Info

SDK Platform: .Net
SDK Version: 3.15.3
Active Channels: MS Teams
Deployment Environment:  Azure Bot Service

Issue Description
During oauth flow for 3rd party oauth provider, clicking on the button which provides the login link, does not bring up a new browser window to be used for login.
Code Example
await SendOAuthCardAsync(context, (Activity)context.Activity);
Reproduction Steps

Send message to bot in MS Teams
Attempt to authenticate
Click on button

Expected Behavior
button click launches browser window that redirects to authentication entry point.
Actual Results
button click does not bring up any window.
*NOTE, upon hover over of button, there seems to be a link that exists.

RIght now there are workarounds for this, but we have work items to deal with all of this we hope to get knocked out very soon.
Try the workaround I mention in #4768:
C#
You will need to first add a class like this that inherits from IMessageActivityMapper:
    public sealed class CustomActivityMapper : IMessageActivityMapper
    {
        public IMessageActivity Map(IMessageActivity message)
        {
            if (message.ChannelId == ChannelIds.Msteams)
            {
                if (message.Attachments.Any() && message.Attachments[0].ContentType == "application/vnd.microsoft.card.signin")
                {
                    var card = message.Attachments[0].Content as SigninCard;
                    var buttons = card.Buttons as CardAction[];
                    if (buttons.Any())
                    {
                        buttons[0].Type = ActionTypes.OpenUrl;
                    }
                }
            }
            return message;
        }
    }

next you will need to register that class in your global.asax like this:
                builder
                    .RegisterType<CustomActivityMapper>()
                    .AsImplementedInterfaces()
                    .SingleInstance();

If you copy and paste the magic code in teams you will get extra characters like "\r\n123456\r" Below is a way to deal with this from #4899:
In my messages controller I put a check for the magic code copy paste like this:
            if (activity.Type == ActivityTypes.Message)
            {
                if (activity.ChannelId == ChannelIds.Msteams && activity.Text.StartsWith("\r\n"))
                {
                        activity.Text = CustomCode.SanatizeMagicCodeForTeams(activity.Text);
                }
                await Conversation.SendAsync(activity, () => new RootDialog());
            }

Then I wrote this simple static class to handle it:
    public static class CustomCode
    {
        public static string SanatizeMagicCodeForTeams(string magicCode)
        {
            Regex regex = new Regex(@"\r\n(\d{6})\n");
            var match = regex.Match(magicCode);
            if (match.Success)
            {
                magicCode = magicCode.Substring(2, 6);
            }
            return magicCode;
        }
    }

@JasonSowers in the work arounds posted for the other (sms/slack) channels, I get to the sign in page, and am able to get a re-direction back to the conversation flow before it fails. In MS Teams, I can't even launch the login page, since clicking on the button does not launch a browser window.
Will the work around handle this as well?
Cheers,
Maciek

Yes the workaround I posted in #4897 will also take care of the issue in teams.   That workaround actually takes care of like 80% of the channel specific problems with Auth.  Just remember to add the correct channels to your if statement.  Or always run the SignInDialog instead of the GetTokenDialog.
But you are saying the workaround in #4897 is not working for you?

I will try the workaround tomorrow or Monday. Not sure if it works. Thanks for the response jason

@mkonkolowicz  I have a sample that has OAuth working on every channel in this repo.  Feel free to use the project as a reference while we sort things out in the SDK.

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Use the correct privacy aware manager.

Coverage increased (+0.03%) to 90.628% when pulling 12a7e6578586a4a53d5aa468a747c0de98a25fc2 on akatsoulas:view-profile-idp into 1ad9854e071ac595580f1fbc38585fd8f7e9dc28 on mozilla:master.


Crash in encrypted realm

How frequently does the bug occur?
All the time
Description
Hi, after upgrading Realm I noticed a crash happening once the app had started up which then seems to corrupt the realm object. I've narrowed it down to upgrading from realm swift 10.21.0 to 10.21.1.
The app will launch OK and seem to run until some kind of interaction happens with the realm. When the app is restarted the realm can no longer be opened and needs to be recreated. I've checked the password remains consistent and none of the code to do the setup has changed for a long time.
Stacktrace & log output
0   App                           0x000000010acc22dc _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28
1   App                           0x000000010acc259f _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 287
2   App                           0x000000010ac374ab _ZN5realm4util20EncryptedFileMapping13validate_pageEm + 1275
3   App                           0x000000010ac37524 _ZN5realm4util20EncryptedFileMapping8validateEv + 68
4   App                           0x000000010ac36043 _ZN5realm4util20EncryptedFileMapping5flushEv + 307
5   App                           0x000000010ac68826 _ZN5realm4util4File7MapBase5flushEv + 118
6   App                           0x000000010a46ba45 _ZN5realm4util4File3MapIcE5flushEv + 21
7   App                           0x000000010a46ba25 _ZN5realm11GroupWriter9MapWindow5flushEv + 21
8   App                           0x000000010a46c907 _ZN5realm11GroupWriter18flush_all_mappingsEv + 135
9   App                           0x000000010a470f4e _ZN5realm11GroupWriter6commitEm + 382
10  App                           0x000000010a42e2af _ZZN5realm11Transaction9async_endENS_4util14UniqueFunctionIFvvEEEENK3$_3clEv + 159
11  App                           0x000000010a42e205 _ZN5realm4util14UniqueFunctionIFvvEE17call_regular_voidIZNS_11Transaction9async_endES3_E3$_3EEvNSt3__117integral_constantIbLb1EEERT_ + 21
12  App                           0x000000010a42e169 _ZZN5realm4util14UniqueFunctionIFvvEE9make_implIZNS_11Transaction9async_endES3_E3$_3EEDaOT_EN12SpecificImpl4callEv + 25
13  App                           0x000000010a40db0a _ZNK5realm4util14UniqueFunctionIFvvEEclEv + 106
14  App                           0x000000010a40d6ed _ZN5realm2DB17AsyncCommitHelper4mainEv + 205
15  App                           0x000000010a41c6e8 _ZZN5realm2DB17AsyncCommitHelper12start_threadEvENKUlvE_clEv + 24
16  App                           0x000000010a41c68d _ZNSt3__1L8__invokeIZN5realm2DB17AsyncCommitHelper12start_threadEvEUlvE_JEEEDTclclsr3std3__1E7forwardIT_Efp_Espclsr3std3__1E7forwardIT0_Efp0_EEEOS5_DpOS6_ + 29
17  App                           0x000000010a41c625 _ZNSt3__1L16__thread_executeINS_10unique_ptrINS_15__thread_structENS_14default_deleteIS2_EEEEZN5realm2DB17AsyncCommitHelper12start_threadEvEUlvE_JEJEEEvRNS_5tupleIJT_T0_DpT1_EEENS_15__tuple_indicesIJXspT2_EEEE + 37
18  App                           0x000000010a41bea5 _ZNSt3__1L14__thread_proxyINS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_EEEEZN5realm2DB17AsyncCommitHelper12start_threadEvEUlvE_EEEEEPvSC_ + 101
19  libsystem_pthread.dylib             0x00007fff6da2b8fc _pthread_start + 224
20  libsystem_pthread.dylib             0x00007fff6da27443 thread_start + 15!!! IMPORTANT: Please report this at https://github.com/realm/realm-core/issues/new/choose

Can you reproduce the bug?
Yes, always
Reproduction Steps
The encryption of the Realm is handled as described here https://docs.mongodb.com/realm/sdk/swift/advanced-guides/encrypt-a-realm/
The configuration is
Realm.Configuration(
fileURL: Utils.documentsURLFor(fileName: "cache.realm"),
encryptionKey: {KEY},
schemaVersion: 113,
migrationBlock: {....}
)
And when accessing it the Realm initially with try Realm() there is no error thrown. The database has been integrated for a few years now and this basic flow hasn't changed in that time
Version
10.21.1
What SDK flavour are you using?
Local Database only
Are you using encryption?
Yes, using encryption
Platform OS and version(s)
iOS 15.2
Build environment
Xcode version: 13.2 & 13.2.1
Dependency manager and version: Swift Package Manager

same

same issue

Hi @allanweir
Sorry to hear that you are encountering this. To help narrow this down further could you tell us if you using Realm Sync? And does your model use EmbeddedObject's?

Same problem for me, as well.

Same problem for me.
One other issue we are having is a similar and happening even on 10.21.0 where TouchID devices crash on launch.

This is happening to me as well.

I am using Real Encrypted, only local realm, not Realm Sync
I am using EmbeddedObjects(s).

About the above, this is the error and the stack trace from firebase.

We're also still suffering crashes with encrypted Realms.  We upgraded Realm to 10.21.1 and started experiencing these issues.  Is there anyone from the Realm team actively investigating this issue?

@dianaafanador3 Thanks, Diana.  That's great to hear and I look forward to testing the next release!

@bmt2018 I'll try to investigate a little bit further into this next week when I get to do support, as it seems this affecting a lot of people.

@dianaafanador3 Thank you!  That would be much appreciated!  :-)

Hi, @dianaafanador3  any workaround for this issue? let's say I downgrade the realm SDK version and release a new version for my application, and if someone still faces this issue I can ask them to reinstall my application will this help?
My month crashlytics looked like 200-300 crashes after this update it has been 18k for this month only

I have just tested upgrading from 10.21.0 to 10.25.0 and everything seems to be working as expected, no errors on the first or subsequent runs of the build.
Thanks for looking into this and getting it sorted!
I'll leave closing the issue for when you're happy it's resolved everyone.

Actually there is still an issue:
About 7 builds/runs in I got an error similar to my original post. There were 2 errors in sequence it looks like:
/Users/user/Library/Developer/Xcode/DerivedData/MyApp-gbughxsxqnhbrdfiuvzigofzgcyo/SourcePackages/checkouts/realm-core/src/realm/util/encrypted_file_mapping.cpp:622: [realm-core-11.13.0]  0   MyApp                               0x000000010439b94c _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 28 1   MyApp                               0x000000010439bb9c _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 228 2   MyApp                               0x0000000104318cd0 _ZN5realm4util20EncryptedFileMapping13validate_pageEm + 1048 3   MyApp                               0x0000000104318d30 _ZN5realm4util20EncryptedFileMapping8validateEv + 76 4   MyApp                               0x00000001043179a8 _ZN5realm4util20EncryptedFileMapping5flushEv + 300 5   MyApp                               0x00000001043439e8 _ZN5realm4util4File7MapBase5flushEv + 108 6   MyApp                               0x0000000103c78eec _ZN5realm4util4File3MapIcE5flushEv + 24 7   MyApp                               0x0000000103c78ec8 _ZN5realm11GroupWriter9MapWindow5flushEv + 24 8   MyApp                               0x0000000103c79be0 _ZN5realm11GroupWriter18flush_all_mappingsEv + 128 9   MyApp                               0x0000000103c7d970 _ZN5realm11GroupWriter6commitEm + 404 10  MyApp                               0x0000000103c13be0 _ZN5realm2DB16low_level_commitEyRNS_11TransactionEb + 716 11  MyApp                               0x0000000103c13890 _ZN5realm2DB9do_commitERNS_11TransactionEb + 176 12  MyApp                               0x0000000103c13f10 _ZN5realm11Transaction27commit_and_continue_as_readEb + 260 13  MyApp                               0x0000000103daed64 _ZN5realm5_impl16RealmCoordinator12commit_writeERNS_5RealmEb + 216 14  MyApp                               0x0000000103eefe40 _ZN5realm5Realm18commit_transactionEv + 276 15  MyApp                               0x0000000103adbe8c -[RLMRealm commitWriteTransactionWithoutNotifying:error:] + 552 16  MyApp                               0x00000001044eef60 $s10RealmSwift0A0V11commitWrite16withoutNotifyingySaySo20RLMNotificationTokenCG_tKF + 148 17  MyApp                               0x00000001044eeab4 $s10RealmSwift0A0V5write16withoutNotifying_xSaySo20RLMNotificationTokenCG_xyKXEtKlF + 420 18  MyApp                               0x00000001037b2b68 $s7AppCore12RealmManagerC5writeyyy0B5Swift0B0VXEF + 376 19  MyApp                               0x00000001036a28e0 $s7AppCore14ContentDataSourceC7cleanupyyF + 88 20  MyApp                               0x00000001037b39c0 $s7AppCore12RealmManagerC7cleanup10completionyyAC16StepResponseTypeOc_tFyycfU_ + 256 21  MyApp                               0x000000010348d918 $sIeg_IeyB_TR + 52 22  libdispatch.dylib                   0x000000010aa406d4 _dispatch_call_block_and_release + 32 23  libdispatch.dylib                   0x000000010aa423b4 _dispatch_client_callout + 20 24  libdispatch.dylib                   0x000000010aa44f2c _dispatch_queue_override_invoke + 1052 25  libdispatch.dylib                   0x000000010aa56500 _dispatch_root_queue_drain + 408 26  libdispatch.dylib                   0x000000010aa56f0c _dispatch_worker_thread2 + 196 27  libsystem_pthread.dylib             0x00000001f1bbf0b8 _pthread_wqthread + 228 28  libsystem_pthread.dylib             0x00000001f1bbee94 start_wqthread + 8!!! IMPORTANT: Please report this at https://github.com/realm/realm-core/issues/new/choose2022-04-04 11:42:29.603246+0100 MyApp[6637:2564589] /Users/user/Library/Developer/Xcode/DerivedData/MyApp-gbughxsxqnhbrdfiuvzigofzgcyo/SourcePackages/checkouts/realm-core/src/realm/util/encrypted_file_mapping.cpp:622: [realm-core-11.13.0]
and
libc++abi: terminating with uncaught exception of type realm::util::DecryptionFailed: Decryption failed Exception backtrace: 0   MyApp                               0x0000000103b602c0 _ZN5realm4util6detail26ExceptionWithBacktraceBaseC2Ev + 48 1   MyApp                               0x0000000103b6d428 _ZN5realm4util22ExceptionWithBacktraceISt13runtime_errorEC2IJRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEEEEEDpOT_ + 88 2   MyApp                               0x0000000103b6d208 _ZN5realm4util4File11AccessErrorC2ERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEESB_ + 68 3   MyApp                               0x0000000104319ed4 _ZN5realm4util16DecryptionFailedC2Ev + 100 4   MyApp                               0x0000000104316a30 _ZN5realm4util16DecryptionFailedC1Ev + 28 5   MyApp                               0x0000000104316814 _ZN5realm4util10AESCryptor4readEixPcm + 504 6   MyApp                               0x0000000104318460 _ZN5realm4util20EncryptedFileMapping12refresh_pageEm + 228 7   MyApp                               0x0000000104319970 _ZN5realm4util20EncryptedFileMapping12read_barrierEPKvmPFmPKcE + 156 8   MyApp                               0x0000000103b606dc _ZN5realm4util26do_encryption_read_barrierEPKvmPFmPKcEPNS0_20EncryptedFileMappingE + 68 9   MyApp                               0x0000000103b5f9bc _ZN5realm4util23encryption_read_barrierEPKvmPNS0_20EncryptedFileMappingEPFmPKcE + 60 10  MyApp                               0x0000000103b6cba8 _ZNK5realm9Allocator18translate_criticalEPNS0_14RefTranslationEm + 220 11  MyApp                               0x0000000103b63014 _ZNK5realm9Allocator9translateEm + 72 12  MyApp                               0x0000000103d2f200 _ZN5realm13ArrayBigBlobs3getEPKcmRNS_9AllocatorE + 80 13  MyApp                               0x0000000103d2f0e8 _ZN5realm13ArrayBigBlobs10get_stringEPKcmRNS_9AllocatorEb + 48 14  MyApp                               0x0000000103d221e0 _ZN5realm11ArrayString3getEPKcmRNS_9AllocatorE + 164 15  MyApp                               0x0000000103d1ed58 _ZNK5realm3Obj4_getINS_10StringDataEEET_NS_6ColKey3IdxE + 384 16  MyApp                               0x0000000103d1ebbc _ZNK5realm3Obj3getINS_10StringDataEEET_NS_6ColKeyE + 172 17  MyApp                               0x00000001038962c4 _ZN12_GLOBAL__N_18getBoxedIN5realm10StringDataEEEP11objc_objectP13RLMObjectBasem + 124 18  MyApp                               0x000000010389623c RLMGetSwiftPropertyString + 36 19  MyApp                               0x0000000104471fc8 $sSS10RealmSwiftE23_rlmGetPropertyOptionalySSSgSo13RLMObjectBaseC_s6UInt16VtFZ + 40 20  MyApp                               0x00000001044720e8 $sSS10RealmSwift26_PersistableInsideOptionalA2aBP015_rlmGetPropertyE0yxSgSo13RLMObjectBaseC_s6UInt16VtFZTW + 20 21  MyApp                               0x0000000104477d98 $sSq10RealmSwiftAA26_PersistableInsideOptionalRzlE15_rlmGetPropertyyxSgSo13RLMObjectBaseC_s6UInt16VtFZ + 56 22  MyApp                               0x0000000104478078 $sxSg10RealmSwift12_PersistableA2B01_C14InsideOptionalRzlAbCP15_rlmGetPropertyyxSo13RLMObjectBaseC_s6UInt16VtFZTW + 20 23  MyApp                               0x00000001044d2158 $s10RealmSwift9PersistedV3getyxSo13RLMObjectBaseCF + 3436 24  MyApp                               0x00000001044d13b0 $s10RealmSwift9PersistedV18_enclosingInstance7wrapped7storagexqd___s24ReferenceWritableKeyPathCyqd__xGAHyqd__ACyxGGtcSo13RLMObjectBaseCRbd__luigZ + 204 25  MyApp                               0x000000010375a1ac $s7AppCore7ItemStepC14imageURLStringSSSgvg + 100 26  MyApp                               0x00000001037b5f58 $s7AppCore15UserFileManagerC11fileCleanupyyF + 1288 27  MyApp                               0x00000001037b3bc0 $s7AppCore12RealmManagerC7cleanup10completionyyAC16StepResponseTypeOc_tFyycfU_ + 768 28  MyApp                               0x000000010348d918 $sIeg_IeyB_TR + 52 29  libdispatch.dylib                   0x000000010aa406d4 _dispatch_call_block_and_release + 32 30  libdispatch.dylib                   0x000000010aa423b4 _dispatch_client_callout + 20 31  libdispatch.dylib                   0x000000010aa44f2c _dispatch_queue_override_invoke + 1052 32  libdispatch.dylib                   0x000000010aa56500 _dispatch_root_queue_drain + 408 33  libdispatch.dylib                   0x000000010aa56f0c _dispatch_worker_thread2 + 196 34  libsystem_pthread.dylib             0x00000001f1bbf0b8 _pthread_wqthread + 228 35  libsystem_pthread.dylib             0x00000001f1bbee94 start_wqthread + 8
5 runs later I just have a decryption error:
libc++abi: terminating with uncaught exception of type realm::util::DecryptionFailed: Decryption failed Exception backtrace: 0   MyApp                               0x0000000101edc280 _ZN5realm4util6detail26ExceptionWithBacktraceBaseC2Ev + 48 1   MyApp                               0x0000000101ee93e8 _ZN5realm4util22ExceptionWithBacktraceISt13runtime_errorEC2IJRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEEEEEDpOT_ + 88 2   MyApp                               0x0000000101ee91c8 _ZN5realm4util4File11AccessErrorC2ERKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEESB_ + 68 3   MyApp                               0x0000000102695e94 _ZN5realm4util16DecryptionFailedC2Ev + 100 4   MyApp                               0x00000001026929f0 _ZN5realm4util16DecryptionFailedC1Ev + 28 5   MyApp                               0x00000001026927d4 _ZN5realm4util10AESCryptor4readEixPcm + 504 6   MyApp                               0x0000000102694984 _ZN5realm4util20EncryptedFileMapping13validate_pageEm + 268 7   MyApp                               0x0000000102694cf0 _ZN5realm4util20EncryptedFileMapping8validateEv + 76 8   MyApp                               0x0000000102693968 _ZN5realm4util20EncryptedFileMapping5flushEv + 300 9   MyApp                               0x00000001026bf9a8 _ZN5realm4util4File7MapBase5flushEv + 108 10  MyApp                               0x0000000101ff4eac _ZN5realm4util4File3MapIcE5flushEv + 24 11  MyApp                               0x0000000101ff4e88 _ZN5realm11GroupWriter9MapWindow5flushEv + 24 12  MyApp                               0x0000000101ff5ba0 _ZN5realm11GroupWriter18flush_all_mappingsEv + 128 13  MyApp                               0x0000000101ff9930 _ZN5realm11GroupWriter6commitEm + 404 14  MyApp                               0x0000000101f8fba0 _ZN5realm2DB16low_level_commitEyRNS_11TransactionEb + 716 15  MyApp                               0x0000000101f8f850 _ZN5realm2DB9do_commitERNS_11TransactionEb + 176 16  MyApp                               0x0000000101f8fed0 _ZN5realm11Transaction27commit_and_continue_as_readEb + 260 17  MyApp                               0x000000010212ad24 _ZN5realm5_impl16RealmCoordinator12commit_writeERNS_5RealmEb + 216 18  MyApp                               0x000000010226be00 _ZN5realm5Realm18commit_transactionEv + 276 19  MyApp                               0x0000000101e57e4c -[RLMRealm commitWriteTransactionWithoutNotifying:error:] + 552 20  MyApp                               0x000000010286af20 $s10RealmSwift0A0V11commitWrite16withoutNotifyingySaySo20RLMNotificationTokenCG_tKF + 148 21  MyApp                               0x000000010286aa74 $s10RealmSwift0A0V5write16withoutNotifying_xSaySo20RLMNotificationTokenCG_xyKXEtKlF + 420 22  MyApp                               0x0000000101b2eb28 $s7AppCore12RealmManagerC5writeyyy0B5Swift0B0VXEF + 376 23  MyApp                               0x0000000101a1e8a0 $s7AppCore14ContentDataSourceC7cleanupyyF + 88 24  MyApp                               0x0000000101b2f980 $s7AppCore12RealmManagerC7cleanup10completionyyAC16StepResponseTypeOc_tFyycfU_ + 256 25  MyApp                               0x00000001018098d8 $sIeg_IeyB_TR + 52 26  libdispatch.dylib                   0x0000000108f086d4 _dispatch_call_block_and_release + 32 27  libdispatch.dylib                   0x0000000108f0a3b4 _dispatch_client_callout + 20 28  libdispatch.dylib                   0x0000000108f0cf2c _dispatch_queue_override_invoke + 1052 29  libdispatch.dylib                   0x0000000108f1e500 _dispatch_root_queue_drain + 408 30  libdispatch.dylib                   0x0000000108f1ef0c _dispatch_worker_thread2 + 196 31  libsystem_pthread.dylib             0x00000001f1bbf0b8 _pthread_wqthread + 228 32  libsystem_pthread.dylib             0x00000001f1bbee94 start_wqthread + 8
The sequence of events on my app starting up are:

Launch
Wait for Realm to be setup (i.e. let realm = try Realm())
When the Realm object is available run a cleanup on old content straight away, before the rest of the app can do anything
During cleanup items older than 30 days may be removed, or marked for deletion on an object property

The first crash sequence happened during this cleanup. All the cleanup is ran on the main thread in a sequence rather than concurrently. In that sequence the first error happens opening a write block (realm.write { .. } ). The second comes accessing an object property (.imageURLString)

Hi Pavel, looks to be working well! Thanks for the update and getting the fix out

Updated this morning and so far, so good.  Thank you for the update on this!


Error while storing Application session data in the database.

Describe the issue:
Error while storing Application session data in the database.
Error in performing Database query: '%s'INSERT INTO IDN_AUTH_SESSION_APP_INFO(SESSION_ID,SUBJECT,APP_ID,INBOUND_AUTH_TYPE)VALUES (?,?,?,?)
org.postgresql.util.PSQLException: ERROR: value too long for type character varying(100)
How to reproduce:
The Shibboleth IdP has been configured as a federated authenticator and trying a login the above error happens.
Expected behavior:
A successful authentication
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 5.9.0
OS: Linux, Mac
Database: PostgreSQL 11

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


KAFKA-12989: MockClient should respect the request matcher passed to prepareUnsupportedVersionResponse

Handle the case where matches returns false and throw the InvalidStateException as stated by the JavaDoc.
We need to guard against this unexpected runtime error in the KafkaAdminClient's sendEligibleCalls method with a try/catch. Not 100% sure if that's kosher or not.
Included a targeted unit test for this case. The remaining tests in KafkaAdminTestClient continue to pass.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Can someone from @confluentinc/clients review, please?

@hachikuji - would you be willing to assign a reviewer for this PR?
The failing tests look like they're related to KRaft tests, so I don't think they're related.

@cmccabe - could you take a look at this and/or assign a reviewer for this? Thanks!

Why is NetworkClient#send throwing an exception? It shouldn't be doing that, right? Can you explain more about the problem that this PR fixes?

Why is NetworkClient#send throwing an exception? It shouldn't be doing that, right? Can you explain more about the problem that this PR fixes?

Per the original issue the MockClient used for testing allows for fault injection via the RequestMatcher. If the test sets up the condition where the request doesn't match some condition, the MockClient.send method throws an IllegalStateException. Because it's not expecting any errors, this exception causes the thread in KafkaAdminClient that is servicing requests to die, hence the try/catch wrapper.
That said, I'm not 100% confident that this change is the right way to handle things.


'dark-theme' and 'goog-theme' year 'hover' state colors updated to improve readability

fixes #24
both dark-theme and goog-theme year hover state colors changed to improve readability.

@HaykoKoryun Really appreciate your active contribution to make this element even better. However, I've dived deeply into this issue and eventually I have to drop merging this PR for a few reasons:

I found that this patch is not enough to fix the issue entirely.
I've found some other issue that caused by hovering the mouse over the year on the list while other themes were applied.

Once again, thank you for your contribution.

No worries, I'll take a look at it again more thoroughly as we are using it for a certain project so will test my changes more before sending another pull request.


Pull trust height and hash automatically

If I am using the inventory-theta.yml inventory, having an ansible task or script collect the trust height and hash ID automatically would make it easier and faster to join the Theta testnet.

@uditvira will provide a script to do this automatically

Closed with PR #68


Update to extend default class or not

Current dependencies on/for this PR:

main

PR #146   👈

This comment was auto-generated by Graphite.


Raise a useful error when reconnecting with a circuit breaker

If you have reconnects enabled, and a circuit breaker configured, it's useful to raise the actual underlying error when we actually attempted the connection instead of simply the circuit breaker error. The circuit breaker error will still be raised if no attempts were tried.

Some minor code style things, but otherwise LGTM.

Ping @byroot

Rubocop is angry again, but I'll fix it on master

Rubocop is angry again, but I'll fix it on master

Thanks, I appreciate it :).


Build native launcher for linux aarch64

Did you try manually running the integration tests on a Linux/ARM64 machine? Just so that we have an idea if it works ok in most cases, or if it's just broken there?

I used generated launcher and run some tests such as(RunTestsDefault, BspTestsDefault, CompileTestsDefault) in Ubuntu with arm64 architecture and it works.

Doesn't work for me, please see #1714

This binary does not work for all aarch64 kernels out there. Most of the aarch64 Linux kernel will have a page size of 4k, which this binary is compatible with, but if a kernel runs another page size liek 64k or, in my case 16k, this binary will not work.
See https://github.com/coursier/coursier/issues/2636#issuecomment-1363491391

So this QEMU thing is quit slow, seems like James Ward came up with a faster approach: https://twitter.com/_JamesWard/status/1613201502469750785 (I didn't read it, just posting so you are aware and might like it)

So this QEMU thing is quite slow, seems like James Ward came up with a faster approach: https://twitter.com/_JamesWard/status/1613201502469750785 (I didn't read it, just posting so you are aware and might like it)

Thanks for the suggestions. I did a slightly different approach, used an actual runner that scala-cli builds macos-m1 launchers and there I run build the aarch64 linux launcher using docker. I reduced the build time to 20 minutes.


use alpine baseimage for glbc

33mb image versus 225mb

Last time we tried Alpine it had problems w/ our DNS @thockin do we know if this is still true?

Alpine does have DNS problems.  Does this image need to do DNS lookups at
all?  Like does it use kubernetes.default as a DNS name, even?
On Mon, Dec 14, 2015 at 8:14 PM, Brendan Burns<EMAIL_ADDRESS>wrote:

Last time we tried Alpine it had problems w/ our DNS @thockin
https://github.com/thockin do we know if this is still true?
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/contrib/pull/332#issuecomment-164640342.

Is there a preferred minimal baseimage that does DNS properly?

busybox is what we mostly use.  It's doesn't have a nice package manager
like Alpine, but it has a shell and basic utilities.
@bprashanth, I feel like there was a reason you didn't use busybox as a
base?
On Tue, Dec 15, 2015 at 7:57 AM, Matt Drollette<EMAIL_ADDRESS>wrote:

Is there a preferred minimal baseimage that does DNS properly?
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/contrib/pull/332#issuecomment-164806874.

Sorry for the delay. I think it was because certificat trust stores came pre-installed in the ubuntu image (or it was easy enough to apt-get when I needed them). I'm planning to swap the base image for something smaller very soon. @MDrollette if you want to swap it for busybox now I can figure out the roots later (we might get away with mounting them from host, I'm open to ideas; IIRC go checks standard locations by default: https://code.google.com/p/go/issues/detail?id=6391).

Also we use a custom alpine image with certs for the service-loadbalancer (https://github.com/kubernetes/contrib/blob/master/service-loadbalancer/Dockerfile), so I think that should be fine. I'll run this pr against E2Es and confirm.

alpine:edge is using new musl version, which supports search directive in resolv.conf.


SPIKE: Investigate open_metadata ingestion methods

User Story
As  a developer
I want to be able to ingest data from my  application
So that i can keep the catalogue uptodate with the data products created
Value / Purpose
This will help us to make decision on ingestion and method of ingestion whether it is a pull or push to api in open meta data
Additional Information
https://docs.open-metadata.org/v1.1.x/connectors/storage
https://github.com/open-metadata/OpenMetadata/pull/7984
https://www.youtube.com/watch?v=ZvA4wuvINFA
Definition of Done
Example -

[ ] Create confluence page
[ ] Create some tickets for ingestion

No longer using Open Metadata


Adding DRTs

Adding DRTS

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


Updating to Chromium 96.0.4664.110

Please respond if you would like to update ungoogled-chromium to the new stable Chromium version.
Notes for the developer
Once you claim it, it is advisable that you create a Draft Pull Request for increased visibility:

Finally, make sure to reference this issue in your PR.
Feel free to ask questions and discuss issues here along the way. Thanks!
Notes for others
Feel free to raise issues or questions throughout the process. However, please refrain from asking ETAs unless no visible progress has been made here or on the developer's PR for a while (e.g. 2 weeks).

The code just dropped so I'll start working on this in a bit.


[#2866] improve(java-clients) Graviton java client  support check version and backward compatibility

What changes were proposed in this pull request?
Graviton java client  support check version and backward compatibility
Why are the changes needed?
Fix: #2866
Does this PR introduce any user-facing change?
NO
How was this patch tested?
UT

Is it ready for review?

Is it ready for review?

Yes

One more missing thing is that we should also do this for python-client, can you please create an issue to track this?

One left thing, @diqiu50 can you please update it.

@diqiu50 please merge to the latest main and rerun the CI.


Add test for scrapy.spiders.sitemap.regex

I have implemented a test case for the function regex in scrapy/spiders/sitemap.py to get 100% branch coverage of the function. Before, there existed no tests that called this function with a parameter that was not of type str.
Close #20

Good job! The only thing that differs from some other places in the main for our tests, is that the comment for the import is placed next to and not on top of the statement. However, I am not sure what is the best.

I have moved the comment now


AnvilLoader does not release world files after unregistering instance

After saving instance files (world regions, level...), the AnvilLoader does not close some files
Code:
instance.saveInstance()
    .thenCompose(unused -> instance.saveChunksToStorage())
    .thenRun(() -> manager.unregisterInstance(instance));

Locked folder:

The folder is unlocked after closing/killing the server

After saving, this is working as expected: Minestom keeps files open because Hephaistos' RegionFile need them open to quickly access chunks.
What is (very probably) missing is a way to close the RegionFile when unregistering the instance.

Any news on this issue ?

Unfortunately this issue is still present, even after every chunk has been unloaded and the instance is unregistered. @jglrxavpok

The commit with the fix is on the lighter-anvil-loading branch, not master
(for now).
Le jeu. 4 août 2022 à 14:36, Lorenzo Lapucci @.***> a
écrit :

Unfortunately this issue is still present, even after every chunk has been
unloaded and the instance is unregistered. @jglrxavpok
https://github.com/jglrxavpok
—
Reply to this email directly, view it on GitHub
https://github.com/Minestom/Minestom/issues/423#issuecomment-1205198032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJNFMTSO7PM5PKPBKN2EMTVXO2LDANCNFSM5CR6CADA
.
You are receiving this because you were mentioned.Message ID:
@.***>

The commit with the fix is on the lighter-anvil-loading branch, not master
(for now).

Unfortunately this issue is still present, even after every chunk has been
unloaded and the instance is unregistered. @jglrxavpok
https://github.com/jglrxavpok
—
Reply to this email directly, view it on GitHub
https://github.com/Minestom/Minestom/issues/423#issuecomment-1205198032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJNFMTSO7PM5PKPBKN2EMTVXO2LDANCNFSM5CR6CADA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I didn't notice 🤦, sorry for the ping then.

Issue fixed by #1005


Update payments

Update payments to use dynamic gateways
Remove all settings from the config
Set payment factories and forms in config
Update payment method db structure

Coverage decreased (-0.08%) to 10.958% when pulling 89d24bc497925e623f2222e002d0f72e9d60b157 on pierredup:payments into eb78ecdf1aa6ad9ea98c9efc5db91fc485552e39 on CSBill:master.

Coverage decreased (-0.06%) to 10.973% when pulling 89d24bc497925e623f2222e002d0f72e9d60b157 on pierredup:payments into eb78ecdf1aa6ad9ea98c9efc5db91fc485552e39 on CSBill:master.

Coverage decreased (-0.06%) to 10.972% when pulling 89d24bc497925e623f2222e002d0f72e9d60b157 on pierredup:payments into eb78ecdf1aa6ad9ea98c9efc5db91fc485552e39 on CSBill:master.

Coverage decreased (-0.06%) to 10.972% when pulling 89d24bc497925e623f2222e002d0f72e9d60b157 on pierredup:payments into eb78ecdf1aa6ad9ea98c9efc5db91fc485552e39 on CSBill:master.

Coverage decreased (-0.08%) to 10.957% when pulling d3db8ec490bbea1250fa2d9a1aa99db973604d0c on pierredup:payments into eb78ecdf1aa6ad9ea98c9efc5db91fc485552e39 on CSBill:master.

Coverage decreased (-0.7%) to 10.295% when pulling c4e1696bf3158d2ec05fa0aff57fb03f43250ef4 on pierredup:payments into eb78ecdf1aa6ad9ea98c9efc5db91fc485552e39 on CSBill:master.


Resolving an instance registered as Singleton create new instance

Hi,
I'm facing a trouble about singleton resolution throught  the IDependencyResolver interface with the version 5.11.1 of UnityContaner
Indeed, a call to the resolve method with the concrete type as parameter  returns a new instance, while a call to the interface works as expected.
Here's a sample unit test to reproduce the problem :
public interface IMySingleton
{
	int Value { get; set; }
}

public class MySingleton : IMySingleton
{
	public int Value { get; set; } = 1;
}

[Fact]
public void ResolveSingletonOk()
{
	var container = new UnityContainer();
	container.RegisterSingleton<IMySingleton, MySingleton>();

	var singleton1 = container.Resolve<IMySingleton>();
	singleton1.Value = 5;

	var newSingleton = container.Resolve<IMySingleton>();
	newSingleton.Value.Should().Be(5); // Works fine
}

but
[Fact]
public void ResolveSingletonFail()
{
	var container = new UnityContainer();
	container.RegisterSingleton<IMySingleton, MySingleton>();

	var singleton1 = container.Resolve<MySingleton>(); // resolve concret type
	singleton1.Value = 5;

	var newSingleton = container.Resolve<MySingleton>(); // resolve concret type
	newSingleton.Value.Should().Be(5); // Fail because Value = 1
}

This poses a problem for me because when I implement the IDependencyResolver, the GetService pass the concret type and my software don't works.

You are registering IMySingleton an a singleton and mapping it to unregistered MySingleton.
For this to work as intended, you need to register it like this:
container.RegisterSingleton<MySingleton>()
container.RegisterType<IMySingleton, MySingleton>()

So, you are registering your singleton type and map an interface to the singleton.

Thanks you, it works well !


fix(material-experimental/mdc-slider): remove slider theme from all-theme

The MDC Web slider is going to be basically get rewritten. Removing the current CSS from the all-theme until we can update this to the new version.

You got it- this was causing a problem in Google because the import path changed. I also want to exclude the mdc-slider styles from all-theme because we 100% know people won't be using them in the current form, so they're inherently unused styles.

Merging as merge-safe because I already made this change in Google.


[Issue]: Media data parsing issue

Confirmations

[X] I have checked the issues tab, and couldn't find an existing open issue for the issue I want to report.

OS Type
Linux
Python Version
3.8.9
Package Version
2.4.0
Description
isubrip fails to scrape some some URLs and fails with a cryptic python error.
Changing the code to raise the error reveals that it's some issue with name parsing.
  File "isubrip/__main__.py", line 52, in main
    print(f"Found movie: {media_data.name} ({media_data.release_date.year})")
AttributeError: 'list' object has no attribute 'name'

Config
No response
Output Log
isubrip https://tv.apple.com/ca/movie/umc.cmc.2jhzj3f3ic3shrf0gt5450j9z?l=en
Scraping https://tv.apple.com/ca/movie/umc.cmc.2jhzj3f3ic3shrf0gt5450j9z?l=en
Error: 'list' object has no attribute 'name'

Hey, thanks (again) for reporting.
I've pushed a fix, and like I mentioned on the other issue, I'll probably release a bugfix version with it tomorrow.
You can install the package from Git meanwhile until the release if you want to have it working.

Fixed in v2.4.1


TriggerBot not working!

Please fix the TriggerBot Offset or kindly teach me how to find offset, Thanks! && How can i merge AimTux with this cheat? i wants to remove AimTux GUI and want it in comand-line, like this cheat.

Yep, I've noticed that today. Also my GlobalVars signature changed:
48 8B 05 ?? ?? ?? ?? 55 48 89 E5 5D 48 8B 00 F3 0F 10 40 10
New iCrosshairIndex offset: 0xBBD4
To find the offset in the future, check out this short how-to. Or just add/subtract 4 few times. It doesn't change much (this last one was only a minor shift by -4 bytes).
AimTux is an internal cheat, this is external glow and inCross trigger. AimTux is sooo much more complex that it's impossible to "merge" it with any external. I'm trying to recreate some of its functions in my java-csgo-external.


Override isInQueue & getQueueItem from WorkflowJob

Just noticed that these have placeholder implementations (false / null) in Job which are overridden by AbstractProject (because it is a Queue.Task) and WorkflowJob should do the same.

Need review from someone with write access: @olamy @rsandell @dwnusbaum @car-roll

Good question. I searched for usages of these Job methods in core (excluding calls from inside AbstractProject itself) including Jelly and AFAICT it only affects the REST API (@Exported).