Add support for installing the ceph kernel client

I think this should be doable on VMs, e.g. from:
http://gitbuilder.sepia.ceph.com/gitbuilder-kernel-rpm-centos7-amd64-basic/
I'd like to do this for Linode but could use some advice/hints on what to do.
Copied from: http://tracker.ceph.com/issues/17305

Hum usually the Kernel client is already compiled with the client, an I missing something?

Are you saying the kernel module objects should be on the clients? I don't see them.

Which Kernel module are we talking about exactly?
Is it the rbd module?

The cephfs module.

Oh this one, well then into ceph-client please. Same place as https://github.com/ceph/ceph-ansible/issues/985

Done.

@leseb is this fixed in the upstream packages?

@batrick which upstream packages? ceph-ansible or ceph itself?

@batrick sorry, I think I had it wrong, this is not fixed and this deserves the same fix as https://github.com/joke-lee/ceph-ansible/commit/6e011d683814c3b0abd5f2583e29721f376faba1

@fullerdj can you take lead on this?

Sure.

On Aug 1, 2017, at 1:52 PM, Patrick Donnelly<EMAIL_ADDRESS>wrote:
@fullerdj can you take lead on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@batrick So, the kcephfs module should come with the distribution kernel. (kernel-* on Red Hat flavors and kernel-image-* on Debian flavors). We can install our versions when ceph_dev is selected (which makes sense), but I think it should be optional. I'll work on that.
Linode stuffs its own kernel in its default images (which doesn't track the distro closely), so this wouldn't be a solution there. They don't seem to publish a repo for modules, so we could generate a custom image there.

@batrick So, the kcephfs module should come with the distribution kernel. (kernel-* on Red Hat flavors and kernel-image-* on Debian flavors). We can install our versions when ceph_dev is selected (which makes sense), but I think it should be optional. I'll work on that.

So I'm not very knowledgeable on this but I would think we would always want to override whatever built-in/module is bundled with the kernel. From a quick google, this link:
https://stackoverflow.com/questions/29337119/override-duplicate-device-driver-for-kernel
indicates it should be possible. Or is that a problem because the kernel module we build may not be loadable by whatever particular old or new kernel the machine is using?

Linode stuffs its own kernel in its default images (which doesn't track the distro closely), so this wouldn't be a solution there. They don't seem to publish a repo for modules, so we could generate a custom image there.

So ya, you can select from Linode's pre-built kernels but we can also force the Linodes to use the kernel provided by the distribution. This is done by setting GRUB in the Linode config and installing grub/kernel in the distribution).

So I'm not very knowledgeable on this but I would think we would always want to override whatever built-in/module is bundled with the kernel. From a quick google, this link:
https://stackoverflow.com/questions/29337119/override-duplicate-device-driver-for-kernel
indicates it should be possible. Or is that a problem because the kernel module we build may not be loadable by whatever particular old or new kernel the machine is using?

That's the issue. We distribute our own fully-built kernel and modules (which is built from https://github.com/ceph/ceph-client, which doesn't track any distribution), which would ordinarily serve as a replacement for the kernel installed on the target system. We can install our RPM, but then the user would need to reboot using our kernel.

Okay well, perhaps a config option to install our kernel (based on branch, e.g. the usual "testing") and/or modules would be fine. If we install the kernel then ansible would need to reboot the machines which is not an uncommon thing to do. If the module can't be loaded then I guess it should FAIL and complain? What do you think?

Yes, that's what I was thinking.

Okay great, I pinged @ukernel by email on this in case he has any recommendations/thoughts.

building ceph modules (from the newest upstream code) for old version kernel is not easy. Because the kernel internal changes from time to time. need to add lots "#if  kernel_version > xxxx ... #endif"
to the code. I think install full kernel package and reboot is better.

https://github.com/ceph/ceph-ansible/pull/1748


feat: implement base ecosystem

What I did

fixes: #
How I did it
How to verify it
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

@antazoey if this is ok like this, i would like to merge and i should transfer this to apeworx right ?


Calling beeswarm multiple times on same shap_values produce different graphs

I am using the latest version 0.39.0.
Using this code snippet:
import shap

explainer = shap.Explainer(model)
shap_values = explainer(X)
shap.plots.beeswarm(shap_values, max_display=15)

If I run the beeswarm cell in jupyter notebook again, I get a completely different graph.
Also, if I change the shap_values to a DataFrame, then plot a beeswarm and then start doing operations on the DataFrame, the data is completely different than if I don't run the beeswarm.  The beeswarm is modifying the numpy array somehow.
shap_values_df = pd.DataFrame(shap_values.values, columns=X.columns)
but if I call copy, then this problem for the dataframe doesn't occur:
shap_values_df = pd.DataFrame(shap_values.values.copy(), columns=X.columns)

Yes, calling
shap.plots.beeswarm(shap_values)

changes the variable shap_values.
It actually adds a new feature which is the "Sum of X other features" (which should have been only temporarly created for the plot), and then if you use again the same variable shap_values you have an additional wrong feature which also takes a wrong name.

The same does not happen in other similar cases like when using shap.plots.waterfall, which also creates the "Sum of X other features", but does not change the variable shap_values.

I ran into this problem, too? Is anyone working on this? @slundberg

Hey everyone, I solved this issue by changing line 57 from
shap_exp = shap_values
to
shap_exp = copy.deepcopy(shap_values)
Don't forget to import the library :
import copy
I hope this doesn't create new bugs, it seems to work perfectly on my tests !

A simple change in beeswarm's code allowed me to solve this issue only by changing line 57 from
shap_exp = shap_values
to
shap_exp = copy.deepcopy(shap_values)
You only need to import the library :
import copy

This is happening with Summary Plot as well. Can someone confirm this please?


[FLINK-2103] Expose partitionBy to user

Merging.

We should first update the documentation.

Good point, will do that anyway because of the renaming discussed on the mailing list.

While merging realized, that it is missing from the windowed and connected datastreams and the from the scala API. Also adding those.


[bug]: installation failed

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
6GB
What happened?
ERROR: Ignored the following versions that require a different python version: 0.55.2 Requires-Python <3.5
ERROR: Could not find a version that satisfies the requirement torch==1.13.1 (from versions: none)
ERROR: No matching distribution found for torch==1.13.1
upgraded to 3.10.9, which sadly didn't alter the error
My machine:
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
64.0 GB RAM
Win 11 64bit OS
NVIDIA rtx 2080 with 6 Gb VRAM
Any help would be greatly appreciated
H
Screenshots
No response
Additional context
No response
Contact Details
<EMAIL_ADDRESS>

Hi, when installing python 3.10.9, make sure to check the box labeled 'add python.exe to PATH' in the installer at the bottom of the window - you might need to uninstall and reinstall to see that.


chore: update repo by service bot

This is a routine update from cc-service-bot based on the service.yml in your repo. This PR
should be approved and merged as soon as CI passes.

CHANGELOG
FILE NAME - CHANGED BY - COMMIT MESSAGE
.semaphore/semaphore.yml - framework - chore: update repo semaphore config
.semaphore/cp_dockerfile_build.yml - framework - chore: update repo semaphore task


 I'll fix it with a crazy hack. Why did you close the issue?

Should be fixed now.

 I'll fix it with a crazy hack. Why did you close the issue?

because i thought its your another genius design which out of my understanding-zone :)

because i thought its your another genius design which out of my understanding-zone :)

You should never assume that!


Option for Outline Song Title

I cannot seem to find a good background for the song title. Not the way I want it atleast. They all have some white where I want the song title located (sky area). I'm requesting the ability to have a outline and maybe able to change the size of the outline

Added with 82ab0b95adedbac5061cef51d65982151b06382a, will be in the next release.
If you want to use it now, you have to clone this repository and place the files in Documents/Rainmeter/Skins/Monstercat-Visualizer and then you can enable it under the settings tab Styling.


Working hours settings not saving

The new Light Syncing Schedule (working hours) does not seem to "save" the setting between session/re-starts of the app.

It also seems once Configure Working Hours is checked - you cannot Uncheck it!
(not 100% related but regular/reliable syncing seems broken now as well)

Please try the latest nightly, as I have cleaned up the light sync process

New nightly still seems to not be saving the working hours start/end time.  It also installed/started with the Configure Working hours pre-checked.

I know this is silly, but did you click save? I just tested Nightly and the the settings file is being updated. You can validate yourself, as the settings file is here
C:\Users\username\AppData\Local\Packages\37828IsaacLevin.197278F15330A.Local_dn7ec1ytrxd6a\LocalState\settings.json

hi :) - Definitely checked and re-checked - it says Saved in green text! - confirming the settings.json file is in the nightly packages folder   (noticed the date format does not match my locale in case that is a issue here as we are DD/MM/YYYY ) - but it still does not show the values on restarting the app!
"SyncLights": true,
"UseWorkingHours": true,
"WorkingHoursStartTime": "6/24/2020 8:00:38 AM",
"WorkingHoursEndTime": "6/24/2020 6:00:53 PM",

can you show me a screenshot of your about page?
On Thu, Jun 25, 2020 at 3:54 PM sborg-ms<EMAIL_ADDRESS>wrote:

hi :) - Definitely checked and re-checked - it says Saved in green text! -
confirming the settings.json file is in the nightly packages folder
(noticed the date format does not match my locale in case that is a issue
here as we are DD/MM/YYYY ) - but it still does not show the values on
restarting the app!
"SyncLights": true,
"UseWorkingHours": true,
"WorkingHoursStartTime": "6/24/2020 8:00:38 AM",
"WorkingHoursEndTime": "6/24/2020 6:00:53 PM",
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/isaacrlevin/PresenceLight/issues/72#issuecomment-649857260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDXTJQV45J5PEP7SZ2IRUTRYPIS7ANCNFSM4OGGNVJA
.

Sure here you are attached.

I am running that version and my working hours are not being set as that, they look like below
  "SyncLights": true,
  "UseWorkingHours": true,
  "WorkingHoursStartTime": "15:00:00",
  "WorkingHoursEndTime": "18:15:00",

If you clear out the values in settings file like so
  "SyncLights": true,
  "UseWorkingHours": true,
  "WorkingHoursStartTime": "",
  "WorkingHoursEndTime": "",

That try again do you see the same issue

cleared out as per above; updated to v2.0.75 and set my times 8am to 5:30pm and setting file still has the following
"WorkingHoursStartTime": "6/27/2020 8:00:00 AM",
"WorkingHoursEndTime": "6/27/2020 5:30:00 PM",

Can we also add Days of Week  (testing this here on a Saturday got me thinking working hours definition should also have Days Of Week).

@sborg-ms can you record a video of an empty settings file being set the incorrect way?

Days of week added to latest nightly

<IP_ADDRESS> - cant test this as overall i cant get this version to work/sign-in/setup settings.

Fixed as of 2.0.85

In case anyone else stumbles across this - if you're still having this issue even with the latest builds, it's necessary to delete the old working hours settings from the settings.json file (with the app closed), then re-enabling working hours will create the start and end time values correctly.


Does not work on windows

This program does not work on windows since windows does not use curl, wget... If anything you can include the file wget and curl from here https://github.com/chiwaka/linux-tools-for-windows

Solution : https://github.com/Manisso/fsociety/issues/4#event-1405219839


Show links in winget list command

Description of the new feature / enhancement
For portable apps, it would be good to show the symlinks created by a package in the list command. Alternately, a winget links command that shows the link name and target.
Proposed technical implementation details
Example powershell function:
function Get-WinGetLinks {
    <#
        .SYNOPSIS
            List winget links
    #>
    [CmdletBinding()]
    [Alias("wglinks")]
    param ()

    $linksPath = Join-Path $Env:LOCALAPPDATA -ChildPath Microsoft\WinGet\Links
    Get-ChildItem -Path $linksPath | Where-Object -Property LinkType -eq -Value "SymbolicLink" | Format-Table -Property Name, LinkTarget
}

[Policy] Area-Output


Fix and enable Windows tests

Previously some windows tests were disabled.  We desired to run all tests in nightly builds so those remaining tests should be enabled.
Unfortunately, some of those tests fail because they invoke bash to run a script that then calls the CLI.  The failure arises because the Haskell test code is unable to locate the bash executable.
This PR fixes that by allowing CI to defined BASH_PATH before invoking the tests so that the can look it up to find the bash executable.

bors merge


mouse scroll event delta doesn't fire the ScrollDelta::Pixels only the ScrollDelta::Lines

Is your issue REALLY a bug?
updating this comment:  In viewer.rs line 172, your match is with either lines or pixels so you return lines regardless.  So maybe you should separate this out or just do lines??

[X] My issue is indeed a bug!
[X] I am not crazy! I will not fill out this form just to ask a question or request a feature. Pinky promise.

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
While trying to incorporate the mouse ScrollDelta::Pixels into icedpygui,  previously only used the ScrollDelta::Lines, I have determined that it does not fired the Pixels, only the Lines.  I ran the event example and since it displays all of the events, Pixels is missing.  I used the example in the master and the example in the latest repos.
What is the expected behavior?
the event ScrollDelta::Pixels is fired.
Version
master
Operating System
Linux
Do you have any log output?
Here's a print out of part of the output of the event example.

Keyboard(ModifiersChanged(Modifiers(0x0)))
Keyboard(ModifiersChanged(Modifiers(0x0)))
Mouse(CursorMoved { position: Point { x: 526.7842, y: 579.4448 } })
Mouse(WheelScrolled { delta: Lines { x: 0.0, y: -1.0 } }) <---------only Lines
Keyboard(ModifiersChanged(Modifiers(0x0)))
Keyboard(ModifiersChanged(Modifiers(0x0)))
Mouse(CursorMoved { position: Point { x: 526

ScrollDelta::Pixels is fired when e.g. scrolling on a trackpad.


Support for Todoist Plugin

Using the light theme, when in Preview mode, the refresh button on the Todoist plugin is a black block.

Really enjoy this theme - thanks for sharing it!

Hi thank you for your Feedback :)
I will look into it!


New Errors in latest Pre-Release

2016-11-03 14:49:51.135 RollRandomiOS[23766:9991767] Image loading failed: https://cdn.rollrandom.com/event/d1e26ba0Image loading failed: https://cdn.rollrandom.com/event/d1e26ba0cc06452402c8d3472521a30a.jpg;210x0 System.AggregateException: One or more errors occurred. ---> System.Exception: HttpHeadersTimeout   at FFImageLoading.Cache.DownloadCache+<DownloadAsync>d__13.MoveNext () [0x0029b] in <611a611025f44893aab237a2b854ecd0>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535
at FFImageLoading.Cache.DownloadCache+<>c__DisplayClass12_0+<b__0>d.MoveNext () [0x00095] in <611a611025f44893aab237a2b854ecd0>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535    at FFImageLoading.Retry+<DoAsync>d__01[T].MoveNext () [0x0008f] in <611a611025f44893aab237a2b854ecd0>:0
--- End of inner exception stack trace ---
at FFImageLoading.Retry+d__01[T].MoveNext () [0x0017a] in <611a611025f44893aab237a2b854ecd0>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128    at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:357
at FFImageLoading.Cache.DownloadCache+d__12.MoveNext () [0x003bd] in <611a611025f44893aab237a2b854ecd0>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535    at FFImageLoading.DataResolvers.UrlDataResolver+<Resolve>d__7.MoveNext () [0x00092] in <453045e4088a49eeb980cce586230676>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535
at FFImageLoading.Work.ImageLoaderTask2+<RunAsync>d__104[TImageContainer,TImageView].MoveNext () [0x00270] in <611a611025f44893aab237a2b854ecd0>:0  ---> (Inner Exception #0) System.Exception: HttpHeadersTimeout   at FFImageLoading.Cache.DownloadCache+<DownloadAsync>d__13.MoveNext () [0x0029b] in <611a611025f44893aab237a2b854ecd0>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535
at FFImageLoading.Cache.DownloadCache+<>c__DisplayClass12_0+<b__0>d.MoveNext () [0x00095] in <611a611025f44893aab237a2b854ecd0>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535    at FFImageLoading.Retry+<DoAsync>d__01[T].MoveNext () [0x0008f] in <611a611025f44893aab237a2b854ecd0>:0 <---
---> (Inner Exception #1) System.Exception: HttpHeadersTimeout
at FFImageLoading.Cache.DownloadCache+d__13.MoveNext () [0x0029b] in <611a611025f44893aab237a2b854ecd0>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535    at FFImageLoading.Cache.DownloadCache+<>c__DisplayClass12_0+<<DownloadAndCacheIfNeededAsync>b__0>d.MoveNext () [0x00095] in <611a611025f44893aab237a2b854ecd0>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535
at FFImageLoading.Retry+d__0`1[T].MoveNext () [0x0008f] in <611a611025f44893aab237a2b854ecd0>:0 <---
---> (Inner Exception #2) System.Exception: HttpHeadersTimeout
at FFImageLoading.Cache.DownloadCache+d__13.MoveNext () [0x0029b] in <611a611025f44893aab237a2b854ecd0>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535
at FFImageLoading.Cache.DownloadCache+<>c__DisplayClass12_0+<b__0>d.MoveNext () [0x00095] in
<611a611025f44893aab237a2b854ecd0>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:143
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x00047] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:187
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:156
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:128
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in /Users/builder/data/lanes/3859/b638977c/source/xamarin-macios/_ios-build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/TaskAwaiter.cs:535    at FFImageLoading.Retry+<DoAsync>d__01[T].MoveNext () [0x0008f] in <611a611025f44893aab237a2b854ecd0>:0 <---`

Hi @alanspires It's not a bug, it was just written to log that HttpHeadersTimeout occured (when server doesn't respond with a certain amount of time). By default it's 6 seconds and it can be cached with config HttpHeadersTimeout parameter.

Written to the log?  I am seeing this error as a hard System.Exception in 2.2.4  or the latest 2.2.5pre.
https://github.com/luberda-molinet/FFImageLoading/blob/c7c769df0c344f65d1eaaf10a6bd6f7de030e383/source/FFImageLoading.Common/Cache/DownloadCache.cs#L99
This is not caught by an Error event on the CachedImage either, I am unclear as to how this should be handled when the source is a bound field in a XAML control?
If I roll back to 2.1.8 my app works perfectly, all the images in my lists load as expected.  If I upgrade to 2.2.4, nothing works, I get dozens of exceptions with System.OperationCanceledException: The operation was canceled. or System.Exception HttpHeadersTimeout. on every ListView with CachedImage controls.
How are we supposed to handle these exceptions on XAML Bound CachedImage controls?

Hi @mike-rowley

I am seeing this error as a hard System.Exception in 2.2.4 or the latest 2.2.5pre.

Could you explain? Does it cause your application to fail? What does hard exception mean? Unhandled? Or is it only written to log? Those exceptions should be catched.

I get dozens of exceptions with System.OperationCanceledException: The operation was canceled. or System.Exception HttpHeadersTimeout. on every ListView with CachedImage controls.

Is it possible that server doesn't respond within 6s?

Hi @daniel-luberda
I should have said base exception, the code I am seeing throw the error is throw new Exception("HttpHeadersTimeout");
However in the process of isolating the issue into a separate project it seems the Exception Dialogs may be related to my Exception Settings in VS.
What I am seeing is the "loading" graphic (an embedded resource) is displayed, then faded out half way on some ListView cells then the app seems to stall for a noticeable amount of time with graphics half faded in.
I can't see how the server doesn't respond in 6 seconds, let alone the 20 seconds I adjusted the timeout for as it is an Azure Storage account, here is a link to one file that it "fails" on.
https://pdproductionv2.blob.core.windows.net/files/miller/Logos/Logo.png
I tried to attach the Zip file but I get a GitHub error saying it doesn't support the file type. So here is a link to the test project.
https://dl.dropboxusercontent.com/u/45178675/2016-11-08-CachedImage.zip

Here is a screenshot of what I am seeing:

Hi @mike-rowley

Does it happen on Android only?
Does it happen with fade animation disabled?

It does happen on Android only.  However I do get HTTPTimeout Errors on iOS that I believe I shouldn't be getting.
It does not happen with fade animation disabled, the images load properly in that case.

It does not happen with fade animation disabled, the images load properly in that case.

I pushed some potential fix for that (see above).
BTW: I changed HttpHeaderTimeout to 10s by default.

Thanks @daniel-luberda, I tested pre-212 and it resolves the issue with the animations stalling on android, it also appears to resolve the HTTPTimeoutErrors I was seeing.
I did notice that what is happening now is that only the first image fades in, the others remain as the loading image until the first image fade is done, then the others rapidly transition from the loading image to the source image.
Not necessarily ideal for listviews but at least they are not stalling during the fade indefinitely now.
Thanks for your help with this and kudos on a phenomenal plug in, it truly is a game changer and your support of the product is greatly appreciated.

I did notice that what is happening now is that only the first image fades in, the others remain as the loading image until the first image fade is done, then the others rapidly transition from the loading image to the source image.

@mike-rowley I definitely want to have those animation effect back for all images. I have to find the way first (I'll try drawable.Mutate()` today and see if that would help).

Thanks for your help with this and kudos on a phenomenal plug in, it truly is a game changer and your support of the product is greatly appreciated.

Thanks

01-17 16:45:20.590 I/mono-stdout(19108): [FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/19404437/UPHO.59860402.V350.jpg
[FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/19404437/UPHO.59860402.V350.jpg
01-17 16:45:20.600 I/mono-stdout(19108): [FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/12369292/UPHO.48870820.V350.jpg
[FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/12369292/UPHO.48870820.V350.jpg
01-17 16:45:20.602 I/mono-stdout(19108): [FFE] [FFED] One or more errors occurred.
01-17 16:45:20.604 I/mono-stdout(19108): [FFE] [FFED] HttpHeadersTimeout
[FFE] [FFED] One or more errors occurred.
[FFE] [FFED] HttpHeadersTimeout
01-17 16:45:20.611 I/mono-stdout(19108): [FFE] [FFED] One or more errors occurred.
01-17 16:45:20.611 I/mono-stdout(19108): [FFE] [FFED] HttpHeadersTimeout
[FFE] [FFED] One or more errors occurred.
[FFE] [FFED] HttpHeadersTimeout
[FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/20109461/UPHO.73970681.V350.jpg
[FFE] [FFED] One or more errors occurred.
[FFE] [FFED] HttpHeadersTimeout
01-17 16:45:20.613 I/mono-stdout(19108): [FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/20109461/UPHO.73970681.V350.jpg
01-17 16:45:20.613 I/mono-stdout(19108): [FFE] [FFED] One or more errors occurred.
01-17 16:45:20.613 I/mono-stdout(19108): [FFE] [FFED] HttpHeadersTimeout
[FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/20268178/UPHO.77609625.V350.jpg
01-17 16:45:20.619 I/mono-stdout(19108): [FFE] Image loading failed: http://sg1-cdn.pgimgs.com/listing/20268178/UPHO.77609625.V350.jpg
[FFE] [FFED] One or more errors occurred.
[FFE] [FFED] HttpHeadersTimeout
01-17 16:45:20.620 I/mono-stdout(19108): [FFE] [FFED] One or more errors occurred.
01-17 16:45:20.620 I/mono-stdout(19108): [FFE] [FFED] HttpHeadersTimeout
@daniel-luberda
I just test 3 Android Devices(4.4.4 / 5.0/ 5.1), they just give me the same error, and I dont what to do.
use web browser view every image is ok
and with sim network every image seems work not that much slow
and with wifi network every image is slow or HttpHeadersTimeout
Im sure of my wifi is good.

@7934345
https://github.com/luberda-molinet/FFImageLoading/blob/master/source/FFImageLoading.Common/Cache/DownloadCache.cs#L142
As you see it's 100% related to connection problems. You could also try to use native http client handlers. Read more here: https://github.com/luberda-molinet/FFImageLoading/wiki/Native-Http-handlers-=-better-performance

still no solution for this ? i face the same problem sometimes response is slow so image doesn't appear
 (Inner Exception #3) System.Exception: HttpHeadersTimeout
01-03 16:34:27.490 I/mono-stdout(14248):   at FFImageLoading.Cache.DownloadCache+<DownloadAsync>d__17.MoveNext () [0x00800] in C:\projects\ffimageloading\source\FFImageLoading.Common\Cache\DownloadCache.cs:199
01-03 16:34:27.490 I/mono-stdout(14248): --- End of stack trace from previous location where exception was thrown ---
01-03 16:34:27.490 I/mono-stdout(14248):   at FFImageLoading.Cache.DownloadCache+<>c__DisplayClass16_0+<<DownloadAndCacheIfNeededAsync>b__0>d.MoveNext () [0x00050] in C:\projects\ffimageloading\source\FFImageLoading.Common\Cache\DownloadCache.cs:59
01-03 16:34:27.490 I/mono-stdout(14248): --- End of stack trace from previous location where exception was thrown ---
01-03 16:34:27.490 I/mono-stdout(14248):   at FFImageLoading.Retry+<DoAsync>d__0`1[T].MoveNext () [0x00047] in C:\projects\ffimageloading\source\FFImageLoading.Common\Helpers\Retry.cs:18 <---
01-03 16:34:27.490 I/mono-stdout(14248):

I'm having the same error as amrkamal1993. It started happening when I moved to .NET standard, having a lot of errors:
    --- End of inner exception stack trace ---   at FFImageLoading.Retry.DoAsync[T] (System.Func1[TResult] action, System.TimeSpan retryInterval, System.Int32 retryCount, System.Action onRetry) [0x00246] in :0
at FFImageLoading.Cache.DownloadCache.DownloadAndCacheIfNeededAsync (System.String url, FFImageLoading.Work.TaskParameter parameters, FFImageLoading.Config.Configuration configuration, System.Threading.CancellationToken token) [0x00401] in C:\projects\ffimageloading\source\FFImageLoading.Common\Cache\DownloadCache.cs:57
at FFImageLoading.DataResolvers.UrlDataResolver.Resolve (System.String identifier, FFImageLoading.Work.TaskParameter parameters, System.Threading.CancellationToken token) [0x00045] in C:\projects\ffimageloading\source\FFImageLoading.Common\DataResolvers\UrlDataResolver.cs:22
at FFImageLoading.DataResolvers.WrappedDataResolver.Resol
ve (System.String identifier, FFImageLoading.Work.TaskParameter parameters, System.Threading.CancellationToken token) [0x0004e] in C:\projects\ffimageloading\source\FFImageLoading.Common\DataResolvers\WrappedDataResolver.cs:21
at FFImageLoading.Work.ImageLoaderTask3[TDecoderContainer,TImageContainer,TImageView].RunAsync () [0x0032d] in <a159011f32534c8eb0455a9cf0bad5a7>:0  ---> (Inner Exception #0) FFImageLoading.Exceptions.DownloadHeadersTimeoutException: Headers timeout   at FFImageLoading.Cache.DownloadCache.DownloadAsync (System.String url, System.Threading.CancellationToken token, System.Net.Http.HttpClient client, FFImageLoading.Work.TaskParameter parameters, FFImageLoading.DownloadInformation downloadInformation) [0x007c3] in C:\projects\ffimageloading\source\FFImageLoading.Common\Cache\DownloadCache.cs:195    at FFImageLoading.Cache.DownloadCache+<>c__DisplayClass15_0.<DownloadAndCacheIfNeededAsync>b__0 () [0x00050] in C:\projects\ffimageloading\source\FFImageLoading.Common\Cache\DownloadCache.cs: 58    at FFImageLoading.Retry.DoAsync[T] (System.Func1[TResult] action, System.TimeSpan retryInterval, System.Int32 retryCount, System.Action onRetry) [0x00073] in :0 <---
2019-11-08 13:48:46.679 NPAInspectionWriteriOS[880:329455]
2019-11-08 13:48:46.705 NPAInspectionWriteriOS[880:329467] Image loading failed: https://url?PictureID=bbdf180f-f298-431e-883c-544bf4a9b066&width=160&height=120;150x0
FFImageLoading.Exceptions.DownloadAggregateException: One or more errors occurred. (An error occurred while sending the request) ---> System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: The operation has timed out.
at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in :0
at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00019] in /Library/Frameworks/Xamarin.iOS.framework/Versions/<IP_ADDRESS>/src/Xamarin.iOS/mcs/class/System/System.Net/HttpWebRequest.cs:1200
at System.Threading.Tasks.TaskF
actory1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func2[T,TResult] endFunction, System.Action1[T] endAction, System.Threading.Tasks.Task1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <939d99b14d934342858948926287beba>:0
--- End of stack trace from previous location where exception was thrown ---`


Most or all metrics exported by Retina should be counters, not gauges

Describe the bug
Retina is currently exporting gauge-type metrics in its modules (e.g. forward.go, drops.go. Since these metrics only go up (or are reset to 0), they should be counters. This is important since a metric type different from the metric's semantical meaning can break the implicit contract and assumptions that people make when querying the data.
From Prometheus documentation:

A gauge is a metric that represents a single numerical value that can arbitrarily go up and down.

A counter is a cumulative metric that represents a single monotonically increasing counter whose value can only increase or be reset to zero on restart. For example, you can use a counter to represent the number of requests served, tasks completed, or errors.

To Reproduce
N/A
Expected behavior
N/A
Screenshots
N/A
Platform (please complete the following information):
N/A
Additional context
N/A

I'm going to open a PR to address this in the forward plugin as an example.

@rbtr Could you assign this to me? I opened https://github.com/microsoft/retina/pull/238, but I need some help with figuring out how to build Retina locally: https://github.com/microsoft/retina/pull/238#issuecomment-2042712405.

just look at these metrics recently and thought of this issue. The reason why we are doing gauges and not counters, even though these metrics supposed to be only ever increasing, is that because we are doing snapshots of the bpf map periodically and Set the metric to whatever the values we've read. The actual counting is being done in eBPF. We should rename <MetricName>Counter to <MetricName>Gauge to prevent confusion


pytorch

Can zhusuan be applied within pytorch framework？
OR will it support pytorch in future？:-D

Maybe not. I'm personally preferring Tensorflow for several reasons. I may list them here in case other people have interests.

Static graphs will be much easier to optimize. Now TF may be reported slow under some settings. But it will soon change. The XLA compiler is not merged yet. Once done one is able to select optimization options when executing graphs (tf.OptimizerOptions.ON_1).

Dynamic graph style primitives are not that hard to support. Actually Tensorflow has made attempts towards this. See the tf.contrib.eager module. It will be merged into core of TF in future. I'm expecting more such as defining a function with dynamic style of code, and adding a decorator to transform to a static graph. And TF eager is actually showing some examples like this.

Distributed execution is better support in TF. Pytorch's distributed module is still only some abstractions over common protocols.

Many other reasons such as larger community, not good enough but complete documents, and

Many thanks for reply.
Just wondering is there a model zoo for the–state–of–the–art DGMs developed in your group?
If there is, it would be much easier to follow the published papers.

When I run the bayesian_nn.py, the results show that  "from examples import conf, ImportError: No module named 'examples'". However, I have installed the examples by "pip install ".[examples]"",. I wonder whether there is anything others need to be done before running it??

@renjinhao Since this is unrelated to this issue, can you raise your question in a new issue?

@ifangcheng In general any paper published with code should be released under the thu-ml organization. If you don't find them, that's probably due to it is still not ready for a release.

@thjashin   I noted a DGM project (mmdcgm ) under the thu-ml organization, However, it seems that it is NOT  developed based on zhusuan ?
Any zhusuan version about it? or will release in future?

@ifangcheng This is an early work before we have zhusuan, so unfortunately not :(


[gsl] Add a "d" debug postfix

See https://github.com/Microsoft/vcpkg/issues/1196#issuecomment-305751793 for details.
With the newly released (  https://blog.kitware.com/cmake-3-9-0-available-for-download ) CMake 3.9, this modification ensures that the correct libraries are found for Release and for Debug.
For older version of CMake, the Release library is still used for both Release and Debug, so there is no regression even for CMake <= 3.8 .

Looks good. Thanks for the PR!


Update Versions

Update MakeMKV to 2.15.0
Update FFmpeg to 4.2.2
Update FDK AAC to 2.0.1
Update QT to 5.14

Qt can not be upgraded for now, since recent versions are using the statx system call which is not white-listed in all Docker versions.

I applied the updates with the exception of Qt.


Short flag name don't trigger required setting

app.Flags = []cli.Flag{
    cli.StringSliceFlag{
      Name: "names, N",
      Required: true,
    },
  }

For example, flag setted as described, and i can write in terminal something like cli --names qwe --names asd - and that's fine. But also i should be able to write cli -N qwe -N asd and that's should work too, but i've got error.
Required flag "names" not set

A small repro would be nice, so we don't have to spend time crafting it up ourselves.

https://gist.github.com/errashe/2523b86554350a5e721ad015aecae796
Here we can run go run t.go --names qwe --names asd and that's will be fine. But if we try to use short tag - go run t.go -N qwe -N asd - got error (Required flag "names" not set).

Thanks @errashe! That repro makes sense, I'm marking this as help wanted since it's a pretty obvious bug.


Extend parsing Postgres logs

added slowlog parsing and parsing of logs where user@DB is mentioned
I'm attaching a sample log from Postgres 11
Though as far as I can tell, Postgres 12 logs seem to be on the same (default) format.

Thanks, Adnan!


Angular Xeditable Grid is not working with Typeahead

Hi,
I have tried as shown below.But it is not working.Could you tell me why ? Thanks.

          {{ showStatus(user) }}

Here is the : Fiddle

Have you tried building the latest version?  There were some changes in a recent commit to work with the latest version of ui-bootstrap.

@ckosloski Actually if you see the above example then it uses latest build (2016-03-24).But still it is not working.Am I missing something on the above fiddler ? Thanks.

You need to download and build it yourself.  The uib changes are merged but not yet released.

@ckosloski Thanks for the info.But could you tell me how to do that ? I'm an Asp.net (C#) developer.So Could you tell me the steps to do so and the editor which I have to use ? At this moment I do have Visual studio 2015.Thanks.

@Sampath-Lokuge, new version was just released, so you can instal it with npm

@eugef Thanks.But still it is not working with e-typeahead.Could you give me a working example ? Thanks.

@ckosloski But still it is not working with e-typeahead.Could you give me a working example ? Thanks.

Look at the examples here - http://vitalets.github.io/angular-xeditable/
It is using editable-text, not editable-select.
You could also try the new ui-select that was added.

@eugef @ckosloski  Here is the updated Fiddle which is not working.

@ckosloski Is that mean can't we use the drop downs with the  e-typeahead ? Thanks.

I haven't tried that, but it sounds like you should try the ui-select.

@ckosloski I have used typeahead with the Angular only drop downs. Which are working fine.The only problem is within the Xeditable grid which is not working ? Thanks.
Here is the AngulaJs drop down with the typeahead.Which is working.
<input name="contactType" id="contactType" type="text" placeholder="@L("OiEnterContactType")"
                           ng-model="vm.occupantDetail.contactType" typeahead="a as a.name for a in vm.contactTypes | filter:$viewValue" class="form-control" required>

@ckosloski The problem on the ui-select is, we cannot add a new item to the drop downs if that item is not in the popup list.But with typeahead we can do that.My requirement is that.That means,if a particular item was not there on the drop down then user can add it to the drop down.After that app will save that item into the table.Thanks.

Your AngularJS drop down example is using a text field.  The editable-text and typeahead should work the same.

@ckosloski Very good point.I have done that way.But still it's having issue when user clicks the Edit button.When user clicks it shows the id of the property.How can I get rid of this ? Thanks.

          {{ showStatus(user) }}

Here is the Fiddle

Here is your Fiddle working.

Wow ... Thanks a lot @ckosloski   :smile:
If you don't mind can you put this answer on the StackOverflow  also.


[ISSUE #7686] The bornTime is not set when using the popMessage API in cluster mode.

Which Issue(s) This PR Fixes

Fixes #7686
Brief Description
The bornTime is not set when using the popMessage API in cluster mode, So it will cause "timeout too much" error. And will never receive any messages.
How Did You Test This Change?
Fix before:
Use gRPC client to receive message by Proxy, you can not receive any messages.
Fix after:
Use gRPC client to receive message by Proxy, you can receive all messages.

Codecov Report
Attention: 40 lines in your changes are missing coverage. Please review.

Comparison is base (46962c2) 42.97% compared to head (b925723) 43.14%.
Report is 40 commits behind head on develop.

Files
Patch %
Lines

...main/java/org/apache/rocketmq/store/CommitLog.java
58.13%
8 Missing and 10 partials :warning:

...a/org/apache/rocketmq/store/MessageExtEncoder.java
78.26%
3 Missing and 7 partials :warning:

.../java/org/apache/rocketmq/store/MultiDispatch.java
87.09%
0 Missing and 4 partials :warning:

...rocketmq/common/message/MessageExtBrokerInner.java
25.00%
3 Missing :warning:

...org/apache/rocketmq/common/utils/MessageUtils.java
88.00%
0 Missing and 3 partials :warning:

...q/proxy/service/message/ClusterMessageService.java
0.00%
1 Missing :warning:

...pache/rocketmq/store/queue/MultiDispatchUtils.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #7687      +/-   ##
=============================================
+ Coverage      42.97%   43.14%   +0.16%
- Complexity      9677     9796     +119
=============================================
  Files           1158     1165       +7
  Lines          83987    84483     +496
  Branches       10917    10968      +51
=============================================
+ Hits           36093    36447     +354
- Misses         43399    43507     +108
- Partials        4495     4529      +34

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


ts: add dex coder scaffold

Looking for help. Free free to take this over.

I'll try this!

so I'm done with the dex program part, generated the idl, kinda had some doubts on the ts side

so I'm done with the dex program part, generated the idl, kinda had some doubts on the ts side

Please open a pr.

done, let me know any changes, ser

That was my first pr btw


Running playgrounds

Firstly nice work guys.
When building pointfreePackageDistribution I get the following issue:
Showing Recent Messages
unable to open dependencies file (...Developer/Xcode/DerivedData/PointFree-ghgmnwhqpbnvtibcslwnkunerblt/Build/Intermediates.noindex/PointFree.build/Debug/PointFreePackageDescription.build/Objects-normal/x86_64/PointFreePackageDescription_dependency_info.dat)

Hey there! The project file that SwiftPM generates is a little confusing. Those “package description” targets aren’t what you want to build. Try “PointFree-Package” and let us know if that gets you situated!

Thanks @stephencelis . I was able to build the scheme successfully. When running playgrounds I get the following inside the playground files:
error: missing required module 'CNIOAtomics'

I am going to investigate further. Feel free to close this if it is only me having this issue.

Hi guys, first of all - great and very inspiring work.
I'm also having the
error: missing required module 'CNIOAtomics'
issue while trying to execute playgrounds.

Hm, we may have an order of operations issue with our Makefile. If you run make bootstrap a second time does that get you situated? Can you outline the steps you’ve taken so far?

@stephencelis  running make bootstrap-oss sorts it out for me.

Closed by #251.


Update Release to Nexus 3.12.1 (Critical Bug Fix)

Please update the nexus bosh release to v3.12.1 to address a critical bug fix that is impacting the upload of artifacts to nexus.
https://help.sonatype.com/repomanager3/release-notes/2018-release-notes#id-2018ReleaseNotes-RepositoryManager3.12.1

0.10.1 has been released


Further scope out metrics

Metrics from the perspective of a Seqeucner being a user of the DA-Network:

DA cost per byte ( separation between how much they paid for the PFB and how much they paid for the blob)
See if they paid more gas than was consumed ( to catch the overestimation of gas consumption )
Current DA batch signer’s wallet balance
Size of the blob per transaction
Gas price
List of submitted transactions and their status

We should split these out based on scope.  For example
Performance / Cost

DA Cost / Byte
Gas pricing
Blob size
etc

Rollup Node Info

Wallet balance

Block / Txns

Txns status
Pending blocks
last block
etc

This will allow us to better break down the implementation, where/how we are going to get the metrics.

Request from Argus - "Make it easy to inspect blobs that are submitted from the sequencer node to the DA layer"

Request from Argus - "Make it easy to inspect blobs that are submitted from the sequencer node to the DA layer"

Added to https://github.com/rollkit/centralized-sequencer/issues/12


Show last watched position of an upload, and go to that last watched position when navigated to

A very important feature to have is to save where a user last was on a video and then show that progress when they are overviewing a channel page. When the user sees the progress bar they can know where they were in that video (a completed video should be a full red progress bar) and when they click that video they should be taken to where they last were while watching that video.
Example from NodeTube, YouTube has the same implementation:

It should be simple enough to make a call to the database on a recurring basis that will mark the current progress of the upload view. On the frontend most of this functionality exists because we are saving user's current state on the client side, so provided the backend can provide the last watched time along with the rest of the information about the claim all that is needed is a progress bar which is easy enough to implement.

Thanks for filing, will close my old issue for this (https://github.com/lbryio/lbry-desktop/issues/3614). This should also include some indicator that something was viewed fully (red bar all the way to the end, maybe different tile shading, etc).
We still need account API support for this to make it cross device / persistent: https://github.com/lbryio/internal-apis/issues/1790

Re: indicating fully watched videos, YouTube does a solid red bar, which feels natural and I support as the spec.


Multiple Slideshows

The release notes for 0.5 say you can multiple slideshows. I looked and can't find an example of how to do this. Could you provide an example?

Tried the  on the single version of remark, and it did not work. How can I properly use it?

@aldarionsevero remark currently doesn't come with any macros, but you can define your own include macro using the code supplied by @eljefe6a:
remark.macros.include = function () {
  var url = this;
  var xmlhttp = new XMLHttpRequest();
  xmlhttp.open('GET', this, false);
  xmlhttp.send();
  return xmlhttp.responseText;
};

var slideshow = remark.create();

Then, in your slideshow, ![:include](1.md) will be replaced with the contents of 1.md. For security reasons, most browsers denies filed to be loaded from the local filesystem like this. So if you're running your slideshow from a local file, this won't work. You have to serve the file via a web server.

@aldarionsevero If you're having any issues with this, please open a new issue.

Include is including properly only one plain slide inside md. Only the first is included. If there is more slides they are left out. And if there is images inside slides there will be an error.

The reason for that is in line 76ff. of parser.js
var value = macro.apply(token.obj, token.args);
if (typeof value === 'string') {
   value = self.parse(value, macros);
   appendTo(stack[stack.length - 1], value[0].content[0]);
}

So the complete return value of the macro will be parsed, but only the first content element of the first slide will be added to the current slide element. In many cases this may be appropriate, but when including complete files it should rather be adding these slides to the stack
slides.push(stack[0]);   //End current slide
slides.push(...value);   //Push slides from include
stack = [createSlide()]; //Start next slide

Maybe only do this if more than one slide was returned from the parsed value to not break existing behavior.


lalrpop compile error with Rust 1.56+

I know version 0.3.1 of this crate is old. But I wanted to give a heads up that it stops building on Rust 1.56+ due to a build error in the lalrpop crate:
   Compiling lalrpop v0.16.3
error[E0034]: multiple applicable items in scope
  --> /home/gps/.cargo/registry/src/github.com-1ecc6299db9ec823/lalrpop-0.16.3/src/message/horiz.rs:25:14
   |
25 |             .intersperse(self.separate)
   |              ^^^^^^^^^^^ multiple `intersperse` found
   |
   = note: candidate #1 is defined in an impl of the trait `Iterator` for the type `std::iter::Map<I, F>`
   = note: candidate #2 is defined in an impl of the trait `Itertools` for the type `T`
help: disambiguate the associated function for candidate #1
   |
22 ~         Iterator::intersperse(self.items
23 +             .iter()
24 +             .map(|c| c.min_width()), self.separate)
   |
help: disambiguate the associated function for candidate #2
   |
22 ~         Itertools::intersperse(self.items
23 +             .iter()
24 +             .map(|c| c.min_width()), self.separate)
   |

For more information about this error, try `rustc --explain E0034`.
error: could not compile `lalrpop` due to previous error

I'd love to port my code to version 0.5 of starlark-rust. But I haven't put in the time yet (and I'd really like #7 before I do so). The apparent imminent inability to build starlark-rust 0.3.1 on Rust stable is probably going to cause a number of bug reports for me :/
Would you be willing to publish a 0.3.2 release of this crate that uses newer versions of its dependencies so it continues to build on Rust stable / 1.56+?
(I wish I could commit to porting past the ancient 0.3 release, but I still haven't found the time to port the significant amount of code I have depending on the 0.3 semantics. But this lalrpop issue may force my hand...)

The 0.3.1 release was made by @damienmg, and the code behind it isn't even in this repo. That's not to say a new release couldn't take place (if someone gave me a package and told me how to upload it I have permissions). However, I see this is really an issue in lalrpop itself? I suspect some more restrictive upper bounds on lalrpop 0.16 and a new release of that would be the right way to solve the issue, might also benefit others, and as a happy side effect, means we need to make no changes?

It looks like that if a compatible lalrpop 0.16.4 were published that starlark 0.3.1 would pick it up and this would solve my problem. I agree that fixing this in lalrpop is the preferred solution and filed https://github.com/lalrpop/lalrpop/issues/629.

There's radio silence from the lalrpop project.
I took the liberty of creating a branch that ports to the latest lalrpop and is compatible with Rust 1.56+. If you are willing to publish an official 0.3.2, I can send a PR. If you don't publish an official 0.3.2, I'll probably publish a starlark-03-legacy crate or something so my builds keep working with Rust 1.56+.
https://github.com/indygreg/starlark-rust/tree/starlark-03-fork

A PR to this repo is useless since the history doesn't go back far enough. A PR to the old repo is useless since it's been archived. How about I grab your tree/branch, review it in place, and just make a direct release of 0.3.2 from there?

A PR to this repo is useless since the history doesn't go back far enough. A PR to the old repo is useless since it's been archived. How about I grab your tree/branch, review it in place, and just make a direct release of 0.3.2 from there?

This is fine for me if it is for you.  I imagine some people might question where the 0.3.2 release came from: they may want to see a corresponding tag on the canonical repo. (But the only thing I care about is a usable 0.3.x version of the crate on crates.io.)

I would suggest keeping the repo/commit/tag around, so that if you need to make a 0.3.3 release to update another library it's easy and we have a track of what the delta is over the last release. I suggest I make the release (can you confirm that the repo is in the releasable state? perhaps make a v0.3.3 tag?) and update the CHANGELOG.md in this repo so point at your repo, so anyone who wonders about hacks or what not can find some verifiable trace back to a source/discussion/code.

I agree that you/Facebook should perform the release. That keeps things simpler.
I've pushed a v0.3.2 tag to my fork: https://github.com/indygreg/starlark-rust/releases/tag/v0.3.2. I believe this commit to be releasable. Although I couldn't get GitHub Actions to run for some reason.
FWIW cargo test in the repo root appears to fail with all Rust versions before and after my commits due to some weird crate version issue when generating the docs. However, cargo test in the starlark directory does work. I'm not sure what's going on here. But it appears to be a pre-existing condition.
I'll send a PR to update CHANGELOG.md in this repo.

For me, cargo test fails because I'm on Windows and the tests end up with \ characters in the path, which then are treated as broken escape characters. I reviewed the changes since your diff and have published. If that works, I think we can close this issue.

I forgot to say thank you for publishing the 0.3.2 release. So, thank you so much!


fix: sync status after guest sync conf

这个 PR 实现什么功能/修复什么问题:
避免同步虚拟机状态两次，导致第二次change-config task未完成时虚拟机状态已经是ready
是否需要 backport 到之前的 release 分支:

release/2.8.0

/area region
/cc @swordqiu @yousong

Codecov Report

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

@@            Coverage Diff            @@
##           master   #2522      +/-   ##
=========================================
- Coverage    7.05%   7.04%   -0.02%
=========================================
  Files         457     457
  Lines       72062   72062
=========================================
- Hits         5086    5075      -11
- Misses      66558   66568      +10
- Partials      418     419       +1

Flag
Coverage Δ

#aFlag
7.04% <ø> (-0.02%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/util/rbacutils/rbac.go
70.89% <0%> (-3.41%)
:arrow_down:

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 1c9c670...c846b1f. Read the comment docs.

/lgtm

/approve


Adding token hash in DB for user-icu identification from short string

added an authenticator class to deal with authentication from tokens
backward compatible
updated url generation
will be useful for telegram support

Thanks @rth for the review! Agreed i will wait for @dulacarnold 's review.


Fix build warning from duplicate PackageReference for 'NewtonSoft.Json'

(The version stays the same.)

Thanks @fowl2 !


Remove "cpu" device

Right now we have and support "cpu" as a device for all supported libraries in the to_device() helper. In particular, we allow to_device(cupy_array, "cpu") to convert a CuPy array to a NumPy array.
This was implemented as a way to portably move an array to the host device, as per https://github.com/data-apis/array-api/issues/626. However, it looks like that issue is going to be resolved in a different way, by adding a device keyword to from_dlpack https://github.com/data-apis/array-api/pull/741.
So I propose we remove this behavior, as it extends things in a way that isn't specified by the standard. Since I'm not sure who is using this, we may want to issue a deprecation warning first.
CC @tylerjereddy @leofang

we aren't using it in SciPy at least - we now just use the test infra from the libraries we are testing with to remain on the same device.

Agreed, it seems too early to merge that.

BTW, is there an issue/PR to track implementation of the device= and copy= kwarg in xp.from_dlpack?
dlpack itself has been released (in RC) with an updated spec that says:

https://github.com/dmlc/dlpack/blob/main/docs/source/python_spec.rst

Starting Python array API standard v2023, a copy can be explicitly requested (or disabled) through the new copy argument of from_dlpack(). When a copy is made, the producer must set the DLPACK_FLAG_BITMASK_IS_COPIED bit flag. It is also possible to request cross-device copies through the new device argument, though the v2023 standard only mandates the support of kDLCPU.

but then array-api-compat does not seem to have been updated yet:
>>> import array_api_compat.torch as xp_torch
>>> import array_api_compat.numpy as xp_np
>>> xp_np.from_dlpack(xp_torch.ones(3, device="mps"))
Traceback (most recent call last):
  Cell In[40], line 1
    xp_np.from_dlpack(xp_torch.ones(3, device="mps"))
  File ~/miniforge3/envs/dev/lib/python3.11/site-packages/torch/_tensor.py:1450 in __dlpack__
    return torch.to_dlpack(self)
RuntimeError: Cannot pack tensors on mps:0

Similarly with array-api-strict:
>>> import array_api_strict as xp_strict
>>> xp_strict.from_dlpack(xp_torch.ones(3, device="mps"))
Traceback (most recent call last):
  Cell In[42], line 1
    xp_strict.from_dlpack(xp_torch.ones(3, device="mps"))
  File ~/miniforge3/envs/dev/lib/python3.11/site-packages/array_api_strict/_creation_functions.py:185 in from_dlpack
    return Array._new(np.from_dlpack(x))
  File ~/miniforge3/envs/dev/lib/python3.11/site-packages/torch/_tensor.py:1450 in __dlpack__
    return torch.to_dlpack(self)

I think the "cpu" device should not be deprecated while it's not possible to use from_dlpack to convert stuff back to CPU/numpy.

I'm definitely not going to deprecate "cpu" until this gets implemented upstream.
Is it possible to implement wrapping support for this in this library? My understanding was that we would need to just wait for upstream support.
By the way, the "cpu" device that is being deprecated here only refers to using CuPy with the to_device helper, where we manually support it as a device. The use of "cpu" with numpy or pytorch will continue to work because that's just a feature of the underlying library.

Indeed there is nothing to do in array-api-compat besides waiting for upstream. For the specific case of being able to replace to_device(cupy_array, "cpu") by np.from_dlpack(cupy_array), I am not sure which would need to be updated: numpy.from_dlpack or cupy's __dlpack__ / __dlpack_device__ or both.
For array-api-strict on the other hand this will require adding the new kwargs (copy and device) to implement the new spec fully.

There was some discussion at the meeting Thursday that there were some things that could be done here, but I don't know if I completely followed it. I will need to rewatch the recording. There was a reference to https://github.com/data-apis/array-api/pull/741#discussion_r1486470895.

Maybe we can revisit if this can be done now, or at least deprecated.


Chatbot timeout message

Jira Issue: https://issues.redhat.com/browse/AAP-35725

Description

Set API timeout to 28 secs and display an error message Chatbot service is taking too long to respond to your query. Try to submit a different query or try again later. in the chat window instead of showing an alert with a 504 error.

Testing

Steps to test

Pull down the PR
Run unit tests

Scenarios tested

A unit test case is included
Production deployment

[X] This code change is ready for production on its own
[ ] This code change requires the following considerations before going to production:

This could be a solution for the situation when model server is overloaded?

I am not sure... Let's run such a load test soon.


Update match to check type STRING for certain conditions before conve…

…rting to LIST
Description
Thanks for contributing this Pull Request. Make sure that you submit this Pull Request against the develop branch of this repository, add a brief description, and tag the relevant issue(s) and PR(s) below.

Relevant Issues : https://github.com/intuit/karate/issues/1714
Relevant PRs : (optional)
Type of change :

[ ] New feature
[x] Bug fix for existing feature
[ ] Code quality improvement
[x] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

@brock-aip thanks for the details. I'm investigating some parts of the code now after your analysis and will be making a few commits. this may require you to re-do some of the commits or I don't mind doing it. since all the tests pass with your changes, I'm okay to merge this. just that I'm making sure myself how the code works !! cheers

closing as it is possible to reference nested read() chunks as demo-ed in this commit: https://github.com/intuit/karate/commit/f9dcfe0f56db15efd386ce4ad0f68a6f3bc73134


Parallelize pyodide based docs

Allows parallelization of pyodide based docs by:

Storing a state dictionary per document
Writing resources out to disk (guarded by a lockfile) to ensure we can gather all required resources
Making the subprocesses daemons

I'm curious: Is the processing still needed when using sphinx parallelization?

Yes, absolutely. Each pyodide execution environment expects a clean slate. In theory we could try to clean up state but that seems very prone to issues.


IFormFile having incorrect Type in swagger.json (expected "file")

Im trying to use IFormFile for uploading file in Asp.NetCore  in the following manner with multipart/form-data :
I'm Using swashbuckle version "5.5.0"
[HttpPut("Id")]
        **[Consumes("multipart/form-data")]**
        public async Task<ActionResult<Attachment>> CreateAttachmentAsync(
            **IFormFile file**)
{
...
....
...
}

The swagger.json generated have type of the file as "string" :
{
            "in": "formData",
            "name": "file",
            "description": "File of size upto 5mb.",
            "type": "string",
            "format": "binary"
          },

where it should have been "file" which we need for generating the correct Clients with autorest
{
            "in": "formData",
            "name": "file",
            "description": "File of size upto 5mb.",
            "type": "file",
            "format": "binary"
          },

I have to explicitly write an operation filter to set the type of all the IFormFile Parameter. Kindly suggest the correct approach.

Looks to be a dup of #1769


Deprecated propeties don't have a warning anymore

VSCode Version: Insider

I am pretty sure that worked before. Do I need to do something to get a warning for deprecated properties.

Is actually a editor problem: https://github.com/Microsoft/vscode/issues/27076


Make an empty state for player points

An empty state for player points is missing. This results in an error when the score is 0-0 at the start of a game.
The player points are based of a .length function on points, but if this does not exist you get an error and the commentate view won't load.
Maybe add an if statement to check for 0 and handle it from there.

Added default values if .length function is null or undefined
let goal = gameStats.stats[0].point.filter(pt => pt.scoredBy.id === player.id).length ?? 0
let assist = gameStats.stats[0].point.filter(pt => pt.assistBy.id === player.id).length ?? 0

Added checks for point array length.
<% let team1Score %>
<% let team2Score %>

<!-- Check if points array has content -->
<% if (gameStats.stats[0].point.length > 0) { %>
<!-- Get last index of stats point array -->
<%  let lastPointIndex = gameStats.stats[0].point.length - 1
	team1Score = gameStats.stats[0].point[lastPointIndex].team1Score ?? 0
	team2Score = gameStats.stats[0].point[lastPointIndex].team2Score ?? 0
} else {
	team1Score = 0
	team2Score = 0
} %>

<!-- Check if points array has content -->
<% if (gameStats.stats[0].point.length > 0) { %>
    <!-- Loop through every scorepoint -->
    <% gameStats.stats[0].point.forEach(scorePoint => { %>

3829c5a4ca8ee672ec7a6281d4603224144da34b


Update rubitrack to 4.3.3

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Version is 4.3.5
https://github.com/caskroom/homebrew-cask/pull/2693


SoftAssertions#fail(String failureMessage, Throwable realCause) display information about realCause?

While taking a look at https://github.com/joel-costigliola/assertj-core/issues/539 I noticed that SoftAssertions#fail(String failureMessage, Throwable realCause) could be more useful, at the moment it does not show any information about realCause.
@Test
public void test() {
    softly.fail("failure", new RuntimeException("abc"));
    softly.assertAll();
}

just displays:

org.assertj.core.api.SoftAssertionError:
The following assertion failed:

failure
at org.assertj.core.api.SoftAssertions.assertAll(SoftAssertions.java:116)
at org.assertj.core.api.SoftAssertionsTest.test(SoftAssertionsTest.java:115)

The error message etc. of realCause is lost.

I agree, we should at least display the real cause message and probably the stack trace (although it might get more difficult to read the other errors because of a stack trace can be quite long).
WDYT ?

The real cause message (without the stacktrace) would be the best compromise between being concise and providing helpful information. (Stacktrace can also be added later on if there is demand for this feature.)

What about displaying the 5 first stack trace elements (and adding the fact that it is a truncated stack trace) ?

Sure, that should be enough information in almost all cases I guess.


Fixed #30070 -- Fixed content spoofing possiblity in the default 404 page.

This issue can lead to phishing, SEO injection and other issues. More
information is available on the OWASP website:
https://www.owasp.org/index.php/Content_Spoofing
How it looks in django with the fix applied (you can use the try the
same url with any django app to see pre-fix):
https://www.etesync.com/account was not found on this server. This usually means an issue with your account that may lead to data loss! Please contact support ASAP at<EMAIL_ADDRESS>to fix your account and report that your%
The fix:
Remove the path from the default template so it just includes a message
without the path.
The issue has been initially reported to me about my Django app running at
www.etesync.com by Jerbi Nessim. After investigating the issue I found
that the cause is Django's default 404 handler, and wrote this fix.
https://code.djangoproject.com/ticket/30070

Please can you create a ticket and add a test as per the contributing guidelines?
I agree with using urlencode, but I also wonder whether the following might be better:
-            '
The requested URL {{ request_path }} was not found on this server.
')
+            '
The requested URL was not found on this server: <tt>{{ request_path|urlencode }}</tt>
')

This gets rid of the link and changes the position and styling of the text to make it clearer that any surplus cruft has been added to the URL and is not part of the main text of the error page.

Sorry, I thought this falls under the trivial/typo fixes category (even though it has more significant implications), which seemed to not require a ticket under the guidelines. I'll take a look into creating a ticket soon.
My concern with urlencode was about usability. As for most users, a urlencoded path may as well be gibbrish, especially when using non-latin alphabets.
I like the idea of re-arranging the order, it's another variation I was playing with, will change it now.
Thanks for your review and comments.

Sorry, I just took your change as-is without running the tests, that now fail. I'll have to fix it all tomorrow or the day after.

Thank you for your reportand patch, @tasn.
I would prefer to not include the path at all and rephrase the message to something like "The requested resource was not found on this server."
For the future, may I kindly ask you to report potential security issues to<EMAIL_ADDRESS>according to the Django Security Policy. Thank you.

I would prefer to not include the path at all and rephrase the message to something like "The requested resource was not found on this server."

sounds good to me. Fwiw by default Nginx does not include the URL and Apache includes the requested URL but without an a-tag.

The default template dates to 8bd7b598b6de1be1e3f72f3a1ee62803b1c02010 and request_path is included in the template context before that.
I'm also in favor of not including the path in the default template but it could also make sense to apply urlencode to request_path in the view so that custom 404 templates don't have to do that.

Good idea, @timgraham.

@apollo13, the a tag was just to visually differentiate the link from the rest of the content in a way that an attacker can't control. Used the a tag because it was used on a link, so it made visual sense. It's however not needed if you urlencode the path.
@timgraham, I agree and I'm happy to send another PR, though this is out of scope for this PR, no?
Additionally, this is a breaking change that affects user code. Users could have, for example, already urlencoded the path in their templates (like I have in EteSync). How do you handle such breaking changes?
Anyhow, I just pushed the fixed PR.

@timgraham, I agree and I'm happy to send another PR, though this is out of scope for this PR, no?
Additionally, this is a breaking change that affects user code. Users could have, for example, already urlencoded the path in their templates (like I have in EteSync). How do you handle such breaking changes?

Since this is a security relevant change, we can, if there's no easy way around, break backwards compatibility.

I just pushed an additional commit that urlencodes the path in the context, so I think this PR is now ready to be merged.
Please let me know if you have any other comments.

I added release notes and made a few edits that could be reviewed.

Awesome, looking forward to having it in!
I see the commit message omits all of the information about content spoofing and the example failed url, and it also doesn't point back to this PR. Is this intentional?

Yes. The commit message refers to the Trac ticket. The Trac ticket refers to this PR.


Acquisition: Backoffice search pages

Added search pages for acquisition vendors and orders.
Requires #649
Vendor search:

Order search:

Thanks for the screenshots, a few comments (ping @kprzerwa):
VENDORS:

isn't too "empty/white" in full-width?

ACQUISITIONS:

Nice! 👏
why the paper part in Document (paper)? Is it the medium?
I am bit confused by the double numbering in the list of order lines 1 Orderline #1..., I would go for something easier... e.g.:

2 x Document (paper) for patron 1 - 20.00 CHF
2 x "The lord of the r..." for patron 1 - 20.00 CHF (if you have the title)
basically quantity x title for patron - total price. The orderline number might be not really relevant

I would remove the currency facet because I am not sure when I select a currency in which field I am fitering: grand total? In any case, not sure it is super useful...
delivery_date is it the date when delivered? if yes, I would change to Delivered the or Delivered:

BTW, in general, the Show x results per page looks globally broken...

@ntarocco I agree the vendor search is very empty. We couldn't come up with any useful facets but we could have a ghost facet column just to reduce the space to make it more compact.
Yes, paper is the medium. Unfortunately, we don't have the titles, only the document PID so it's hard to print the order lines in a meaningful way.
I like having the quantity in there though instead of the numbers since they don't mean anything.


asm output for benchmarks not showing up

example: cargo asm -p project --bench teststuff main

some more info:

The example might be contrived or I'm doing something wrong, but I haven't gotten this to output the asm of benchmarks, let alone show me the actual functions when listing. I'm using criterion. It also doesn't work with a real, working criterion benchmark.
Please tell me what other info I should provide.

Last line on the first screenshot says it is calling test_main_static, do you see it if you call cargo asm -p project --bench teststuff --everything?
If not - what are the versions of rustc, cargo-show-asm? What platform are you on? Can you share the full code?

if I pipe with --everything into a file, test_main_static doesn't show up anywhere, inner shows up like this:

rustc 1.67.0-nightly (edf018221 2022-11-02)
cargo-show-asm 0.2.17
win10

Here's the real code: https://github.com/hecatia-elegua/bilge/blob/main/benches/compared
Ok strange, if I add #[inline(never)] to these function, which I'm calling in compared/main.rs, they do show up now:

I thought I did that already...
Well that solved it, produces what I expected.

Magic.

funny enough, inner in this dumb example doesn't show up anyways, even if it's inline-never...
though I don't need that solved, so
thanks for this nice tool :)

Can you publish this dumb example somewhere?

https://github.com/hecatia-elegua/asmrepro

https://github.com/hecatia-elegua/asmrepro

This version does not use criterion and it seems like default bench harness from cargo/rustc replaces main function with something that would run actual benches. If you replace body of your main with panic!("this never runs") and try to run the benchmarks - it successfully runs showing 0 total tests.


Maybe cover the rest of TestSwarm API?..

For our case we required some additional methods, so I basically covered the whole API, or a big part of it at least (TestSwarm itself quite raw for console usage). Here: https://github.com/jayarjo/bunyip/blob/master/lib/testswarm.js. Your module gave initial inspiration, I've even retained namings for some methods :)
Would you be interested to pull that in as an update maybe?

Closing old issues and pull requests relating to TestSwarm.
Per https://github.com/jquery/testswarm, additional features are no longer considered.
Small bug fixes are still welcome, though!


Double encoding of special chars in URL doesn't work well in all cases

See for instance tcort/markdown-link-check#155
User is looking to check https://en.wikipedia.org/wiki/%3F:
But the ? sign is then decoded by link-check and not reencoded as it's a legit char for a url but that have a specific meaning of being the param part start. So https://en.wikipedia.org/wiki/%3F: becomes https://en.wikipedia.org/wiki/?: meaning https://en.wikipedia.org/wiki/ with parameter :.
We need to find a way to deal with encoded chars without all these issues. There's already a lot of tests for some specific cases in the test suite. They have to continue to work, but for now the risk is to have a pile of specific cases. Finding a generic way to deal with this would be nice.

I encountered the same issue using markdown-link-check failing on the URL https://libraries.io/npm/@action-class%2Fcore/tree
With the reencoding of %2F to / the request results in a 404 since the path argument parsing now receives an additional path component.
In my opinion the manual reencoding is unnecessary since the new URL() call already normalizes the URL.
Example:
new URL("https://example.com/foo%2Fbar/foo bar/?test=arg%20with+spaces&test2=arg unencoded").toString()

results in
https://example.com/foo%2Fbar/foo%20bar/?test=arg%20with+spaces&test2=arg%20unencoded

So my suggestion would be to completely remove the encodeURI and decodeURIComponen calls from https://github.com/tcort/link-check/blob/master/lib/proto/http.js#L40 and rely on the normalization of JavaScripts URL class.
diff --git a/lib/proto/http.js b/lib/proto/http.js
index f6530a4..548e7a8 100644
--- a/lib/proto/http.js
+++ b/lib/proto/http.js
@@ -31,13 +31,8 @@ module.exports = {

         let user_agent = opts.user_agent || `${pkg.name}/${pkg.version}`;

-        // Decoding and encoding is required to prevent encoding already encoded URLs
-        // We decode using the decodeURIComponent as it will decode a wider range of
-        // characters that were not necessary to be encoded at first, then we re-encode
-        // only the required ones using encodeURI.
-        // Note that we don't use encodeURIComponents as it adds too much non-necessary encodings
-        // see "Not Escaped" list in https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent#description
-        const url = encodeURI(decodeURIComponent(new URL(link, opts.baseUrl).toString()));
+        // rebase relative urls and normalize url encoding
+        const url = new URL(link, opts.baseUrl).toString();

         const options = {
             user_agent: user_agent,

Alternatively adding an option parameter to skip the reencoding would be highly appreciated. That way an per URL option could be added to the markdown-link-check config to disable this 'feature' for problematic URLs.


[Ollama AI] - Answer in different language

Extension
https://www.raycast.com/massimiliano_pasquini/raycast-ollama
Description
Today, in this extension, all prompt are in english.
Most of models are able to answer in different language.
An interesting feature can be to add in system prompt the answer language requested. Language can be a extension preference in a dropdown.
Fallback to english can be useful if model don't support language define in extension preferences.
For example, modifying prompt for extensions/raycast-ollama/src/ollama-explain.tsx who is :
const p =
    "Act as a writer. Explain the following text in simple and concise terms.\n\nOutput only with the modified text.\n";

by
const p =
    "Act as a writer. Explain the following text in simple and concise terms.\n\nOutput only with the modified text.\nYou only need to answer in French except if you don't support this language\n";

Will permit to answer in french. So if you replace French by the language preference, i think that's will be great.
Who will benefit from this feature?
Every people where english isn't easy to use
Anything else?
No response

Hi @mguyard, all provided commands are using prompt in english and are meant to be used as a base commands set. As described on README.md 'Create Custom Command' let you create as many commands you want with your own custom prompt.

@raycastbot close this issue

Yes I know and it like I use it. But it can be easily multi language without important modifications in extension.
And like this, it will not need to recreate all default commands to just have the right language


coqPackages_8_10.QuickChick: init at 1.2.0

Motivation for this change
Enable QuickChick for recent versions of Coq
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build coqPackages_8_10.QuickChick