fix: degree not showing up in gradient background generator

Fixes Issue #303
My PR closes #issue_number_here
👨💻 Changes proposed(What did you do ?)
fixed the issue of empty deg indicator in gradient-background
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

Note to reviewers

📷 Screenshots

Please fix the compliance PR error above, if you don't know how, try this:

Read the error carefully or read the contributing file
Checkout past merged Pull requests to see how they were done for it to be merged

Note: you can edit your PR message, this PR won't be merged if the error isn't gone and may be closed if it isn't fixed soon

didn't understand why it giving error ?? code is clean

Has nothing to do with your code and everything to do with this👇🏽

@Dun-sin fixed now

@Dun-sin fixed now

It's not, the message will change if it has

@Dun-sin fixed now

It's not, the message will change if it has

bro check now it's showing green means no error

PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project.  The results are listed in the  following section.
Issue Reference In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

The green doesn't matter, this is what tells you if there are errors or not
If you don't want to bother to fix it, you can close the PR.
Thanks for wanting to contribute🙌🏽

@Dun-sin bro I'm new. can you plz explain what's wrong ? and what should i do to make this pr get merged ? i'm very confuse...

@Dun-sin bro I'm new. can you plz explain what's wrong ? and what should i do to make this pr get merged ? i'm very confuse...

My PR closes #issue_number_here
What does this mean👆🏽

It's like my name is your_name_here in a form.
When filling it you do it like this: my name is Dunsin
If you actually bother to read it, you won't be confused, but you didn't.

actually bro i did read it but couldn't understand. and also i checked other pr those doesn't have this option :/
is it ok now?

thank you man

:tada: This PR is included in version 2.21.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


VirtualizingStackPanel cannot work with ScaleTransform animation.

Describe the bug
VirtualizingStackPanel cannot work with ScaleTransform animation.
To Reproduce
1.XAML:
<Window xmlns="https://github.com/avaloniaui"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
        x:Class="AvaloniaApplication1.MainWindow"
		xmlns:Local="using:AvaloniaApplication1"
        Title="AvaloniaApplication1">
	<Window.Styles>
		<Style Selector="Grid.Expand">
			<Style.Animations>
				<Animation Duration="0:0:0.3" FillMode="Forward">
					<Animation.Easing>
						<CubicEaseOut></CubicEaseOut>
					</Animation.Easing>
					<KeyFrame Cue="0%">
						<Setter Property="ScaleTransform.ScaleY" Value="0"/>
					</KeyFrame>
					<KeyFrame Cue="100%">
						<Setter Property="ScaleTransform.ScaleY" Value="1"/>
					</KeyFrame>
				</Animation>
			</Style.Animations>
		</Style>
	</Window.Styles>
	<Grid RowDefinitions="auto,auto">
		<Button Name="B">Show</Button>
		<Grid RowDefinitions="auto,auto" Name="G" Grid.Column="1" IsVisible="false">
			<Border Background="Red" Height="200" Width="350"></Border>
			<ItemsControl ClipToBounds="True" Grid.Row="1">
				<ItemsControl.ItemsPanel>
					<ItemsPanelTemplate>
						<VirtualizingStackPanel></VirtualizingStackPanel>
					</ItemsPanelTemplate>
				</ItemsControl.ItemsPanel>
				<ItemsControl.ItemTemplate>
					<DataTemplate>

					</DataTemplate>
				</ItemsControl.ItemTemplate>
			</ItemsControl>
		</Grid>
	</Grid>
</Window>

2.Code-behind:
using Avalonia.Controls;
using Avalonia.Media;

namespace AvaloniaApplication1
{
    public partial class MainWindow : Window
    {
        public MainWindow()
        {
            InitializeComponent();
            B.Click += B_Click;
        }

        private void B_Click(object? sender, Avalonia.Interactivity.RoutedEventArgs e)
        {
            G.IsVisible = true;
            if (G.RenderTransform == null)
            {
                G.RenderTransform = new ScaleTransform(1, 0);
            }
            G.Classes.Clear();
            G.Classes.Add("Expand");
        }
    }
}

3This is what appears when the button is clicked:

As you see, it doesn't play animation any. And in DevTools it will throws error about RenderTransform:

PS:To reproduce this problem, you do not even need to assign a value to the ItemSource of ItemsControl.
Expected behavior
However, if I replace the VirtualizingStackPanel with StackPanel, it works well and it is what I expect.

Environment
OS: Windows 10 19045.3570
Avalonia-Version: 11.0.5

I found a temporary solution. When playing the ScaleTransform animation,set IsVisible of ItemsControl to false, and then set it to true after the animation plays.

@kyuranger I guess this is by design. Because virtulization Stackpanel needs "valid" bounds that are neither 0 nor infinite. otherwise it cannot caculate it's childrens correctly.

@kyuranger I guess this is by design. Because virtulization Stackpanel needs "valid" bounds that are neither 0 nor infinite. otherwise it cannot caculate it's childrens correctly.

I think what you said makes sense, but WPF doesn't seem to have such a problem (I discovered this problem just by migrating my old WPF project to Avalonia). And I think that even if Avalonia cannot solve the problem of VirtualizingStackPanel, it should skip rending VirtualizingStackPanel in animation instead of not rendering all content.

This sample in the OP now works fine with the latest 11.1 nightly build (and fails in 11.0.5). The fix is likely #13188.
I'm closing this issue as fixed, please reopen if needed.


Temperature unit in rensponses

There should be a option to pass in which temperature unit we are responding, so we can pass it to response.
Example:
  default: "It is {{ state.state }} degrees of <temperature_unit>"

We now have {{ state.state_with_unit }} available


Add new property to /open event

Add new "trigger" property to the cmake-tools /open event that indicates what caused the cmake-tools extension to activate.

Unfortunately, this information is not provided to us by VS Code.  Feature Request here: https://github.com/microsoft/vscode/issues/44711


Implement text-file architype definitions.

Already implemented - no work to be done here.

Already implemented - no work to be done here.


Page on "Advanced interaction with OS"

https://github.com/pharo-contributions/OSSubprocess
OSProcess ?

OSWinSubProcess


Windows asks for key PIN, native Linux does not

Less of an issue and more of a curiosity:
When I create or use an SSH key via my security key under Windows it asks for my security keys PIN, which is fair. The curious thing to me is that if I take the same keypair to Linux and present the security key, it only asks me to touch and not to supply any kind of PIN, even though the keypair was setup with one.
Wondering if this is an intentional design of windows fido bridge, some jankiness from the windows FIDO2/U2F api or something else beyond my understanding
To be clear I'm using a Solo Key 4.0.0 so if you can't reproduce it with another key then that's perfectly fair enough, mostly just curious if it's anything anyone knows about.

Some background: the WebAuthN standard allows the "relying party" (in this case, OpenSSH/windows-fido-bridge) to optionally request that the security key performs "user verification", which can include a variety of possibilities; in the case of your security key (and the YubiKeys I own), that means providing a PIN to the security key before a credential is generated. If the RP doesn't request user verification, the WebAuthN standard requires that the security key instead perform a "test of user presence", which for our security keys means physically touching a sensor on the key itself.
Likely what's happening is I'm not explicitly setting dwUserVerificationRequirement when making a credential or when getting an assertion (i.e. during a login) and Windows is defaulting to requiring user verification, which is why you get a PIN prompt. Also, OpenSSH passes in flags where it tells its SK middleware if it wants user verification or a test of user presence as well, but right now, windows-fido-bridge just ignores them. Best as I can tell from reading its source, OpenSSH only ever explicitly asks its SK middleware for a test of user presence, which is why it doesn't ask you for a PIN when you use it in Linux (though that doesn't necessarily mean you may never be asked for a PIN, something I assume depends on the security key you use).
The fix is to pay attention to the flags from OpenSSH and set the appropriate options in Windows' API accordingly. I'll find some time within the next few days to test it out and make a fix. Thanks for reporting the issue!

Thanks for the background information, that helps a lot in understanding why this happens!

Could you rebuild with the latest commit and try again? On my system, logging into a remote machine now only requires touching the security key, though creating an SSH key still requires entering a PIN if the key is set up with one, which seems to be enforced by either Windows or the security key itself.

Latest commit works great!
And same here, it asks for PIN only when creating a new SSH key, which I suppose is understandable and done rarely enough anyways that it's fine. I can't remember if baremetal Linux required a PIN to create keys when I last used it, I would check but can't right now.

Just tried it on a native Linux machine with the same YubiKey I tested on Windows and it did request a PIN before requiring me to touch the sensor:
mgbowen@seattle:~$ sudo ssh-keygen -t ecdsa-sk
Generating public/private ecdsa-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter PIN for authenticator:
Enter file in which to save the key (/root/.ssh/id_ecdsa_sk):
# ...

Interestingly, it didn't allow me to do that without being root, but I assume that's because I need to set up some udev rule or something to grant a specific user group access to the key's HID device.
I'll close this then, let me know if you run into any other issues.

@mgbowen Sorry to hijack this issue to ask this question but this got me thinking.
Does all this mean that even if a resident key is created with the user verification flag, there is nothing requiring user verification on subsequent uses of that resident key?
I'm asking because I was considering using a resident key so that I could avoid having to copy it from computer to computer but wanted to have it be protected by a PIN so that it would not be compromised in case of theft.
What's stopping an attacker from writing their own fido-bridge that unsets the uv flag and using the resident key to log into a server?
I'm having a hard time finding information on the subject.

Disregard, I should have read further, I was looking everywhere except your own README.


Ddpdupdates2

minor preperation for ddpd
also an IDL fix to pick up the local version and not SSW

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e539c8b) 76.80% compared to head (30a2366) 77.06%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #380      +/-   ##
==========================================
+ Coverage   76.80%   77.06%   +0.25%
==========================================
  Files          66       66
  Lines        6912     6889      -23
==========================================
  Hits         5309     5309
+ Misses       1603     1580      -23

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


Recognize All Contributors

Let's do what we can to recognize those in our community. Examples of how we have tried to do this to-date:

inclusion in project presentations
inclusion in internship flyers

Request:

Investigate use of https://allcontributors.org bot within the Meshery project.
Brainstorm and suggest alternatives.

We're not sold on allcontributors.org, specifically, but are in search of ways to elevate the work of contributors and the contributors themselves. Maybe this makes for a good page in the docs.

https://github.com/layer5io/meshery-istio/issues/45#issuecomment-572185885


npx partykit deploy fails

I'm trying npx partykit deploy for the first time. It opens github in a web browser, but then I click 'authorize' and nothing happens. In the browser console are some errors

In the meanwhile, you can use the legacy login mechanism which bypasses the PartyKit dashboard and logs you in directly via GitHub:

npx partykit login -p github

@nichoth thanks for reporting this! I've fixed this and released it as part of<EMAIL_ADDRESS>It seems that Chrome has started to roll out Private Network Access in Chrome 117. Curiously, upgrading to 117 did not break this for me, but enabling "Respect the result of Private Network Access preflights" in chrome://flags did, and I was able to fix the issue.

Somewhat more concerningly, the login callback seems to be broken on Safari and Brave currently, due to WebKit/Safari choosing not to observe the W3C Mixed Content specification and blocking localhost requests from public websites despite the spec explicitly.
https://bugs.webkit.org/show_bug.cgi?id=171934
I'll keep this issue open until we have a fix in place for WebKit.

Fixed by #473


update fn render path-index test cases

Close #1744
These tests were failing with the error that there were duplicate http-bin resources. This is because the functions that generate resources outside of their current package can't be idempotent; they have no means of checking if those resources already exist. As a result, running the test twice resulted in a path annotation conflict on the second run; the function tried to create a resource with the same path and index as the resource created in the first run.
This PR updates the test cases to reflect the non-idempotency of these functions.

@Shell32-Natsu PTAL


edit a task

Hello there,
why can I not edit a task? Like source and destination is disabled on WIN Portable. Bug or feature? Thanks

It was design decision long time ago. Plans were to add logging and history and it was easier to assume that source and destination stay the same within specific task. Was it right? I am not sure but it is legacy code and I don’t find it critical to change.

On 2 Jan 2020, at 15:14, adnoh<EMAIL_ADDRESS>wrote:

Hello there,
why can I not edit a task? Like source and destination is disabled on WIN Portable. Bug or feature? Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hey again,
I would like to add that I feel that, while this may technically be "non-critical", it can certainly end up being a major inconvenience as I have just experienced. Considering that when you hit edit, the box is right there already, it seems unnecessarily restrictive to not allow for editing the path. I needed to do this just a few minutes ago, which was what lead me here once I discovered I was unable to do so.
I was reorganizing my NAS and changed a few folder names for consistency when I went to change the paths in my tasks and realized I cannot edit them. Not only that, but I also was not able to edit the task file which contained them. I expected it to be a text file containing a command and appropriate arguments similar to when you would select the "copy command to clipboard option", but I see now that, that is not the case. Unfortunately, I now have to delete all of my tasks and their individual rules, settings, and excludes simply because I needed to change a space to an underscore in a folder name.
I can say with certainty that when you have multiple tasks and they have their own configurations, it would be a very welcome adjustment to be able to avoid having to completely remove them and recreate them if I just need to make some slight adjustments to the path.
Thanks again,
-MH

it will be also included in the next release - see #87

"Thanks" to quarantine I have a bit of spare time so working on massively improved next version. It is 90% ready. Can't commit to specific date but should roll it out in the next week or two.

Ah, perfect. I do apologize in that case. I had just done a search for the terms when I came across this thread and missed the other one.
As for quarantine, unfortunately, I understand all too well. I was just laid off yesterday so I have been using this time to do maintenance tasks I have been avoiding (such as reorganizing my NAS, lol), and doing updates to some of my projects as well.

If you are on windows you can try latest beta from here #93 (link in the first post)

On 2 Apr 2020, at 18:22, MostHated<EMAIL_ADDRESS>wrote:
Ah, perfect. I do apologize in that case. I had just done a search for the terms when I came across this thread and missed the other one.
As for quarantine, unfortunately, I understand all too well. I was just laid off yesterday so I have been using this time to do maintenance tasks I have been avoiding (such as reorganizing my NAS, lol), and doing updates to some of my projects as well.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/kapitainsky/RcloneBrowser/issues/63#issuecomment-607981703, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADXJHOUAQM2EQHY73VEEIOLRKTCUZANCNFSM4KCDKRRQ.

Very good. The machine I am currently working on reconfiguring is indeed Windows, so I will give it a try. 👍

One quick question, if you do not mind. When it comes to optional parameters, which ones take precedence? I had some within the general preferences under Default rclone options, such as --ignore-case --fast-list --checkers 8, but then the task menu has options as well. Do those override any that are set in the default options?

Good point I should make it more clear.
so you have in preferences

Default rclone options - they will be used for any rclone operation (listing remot,e download, upload etc) - perfect for —fast-list or to ignore invalid remote certificate
Default download and upload options - they will be added for all download/upload operations respectively - maybe some exclude or include options here
Default mount options - only added for mount operations

then you can add more options using extra option field.
you can always check effective rclone command in jobs - next to cancel button there is “copy rclone command to clipboard"

On 2 Apr 2020, at 18:40, MostHated<EMAIL_ADDRESS>wrote:
One quick question, if you do not mind. When it comes to optional parameters, which ones take precedence? I had some within the general preferences under Default rclone options, such as --ignore-case --fast-list --checkers 8, but then the task menu has options as well. Do those override any that are set in the default options?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/kapitainsky/RcloneBrowser/issues/63#issuecomment-607991712, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADXJHOX7XJABGPFH5KA2IX3RKTEXHANCNFSM4KCDKRRQ.

This issue is maked as closed however I would also like the ability to edit the source and destination fields. I migrated my rclone to a new install and I copied my tasks.bin file. These two fields changed and because I can't edit the fields I ended up having spend over 1 hour recreating all my jobs by copying and pasting. It was a messy and error prone task.
What could possible be the rational be for restrict the user from editing the task data that he has create?


New version: CamiXon v1.8.5

Registering package: CamiXon
Repository: https://github.com/walra356/CamiXon.jl
Created by: @walra356
Version: v1.8.5
Commit: a4f9f7242989148e8f3639c81562252c71ec5d1a
Reviewed by: @walra356
Reference: https://github.com/walra356/CamiXon.jl/commit/a4f9f7242989148e8f3639c81562252c71ec5d1a#commitcomment-130131144
Description: A package for image analysis of backscattered light

no not auto-merge

[noblock]


Tidied content in index pages

Updated the content of the main index pages to better reflect the prototypes and make it clearer what things are.

Looks good to me 🎉 . It's about time to update it, haha. I was thinking to put the forms admin as at the top of the links on the page. Can push the change if you agree.
And we can merge it in once we've completed testing sessions with users this week x

Sorry which page do you mean?
On Mon, 23 Jan 2023 at 13:47, agz deberny gomes @.***>
wrote:

Looks good to me 🎉 . It's about time to update it, haha. I was thinking
to put the forms admin as at the top of the links on the page. Can push the
change if you agree.
And we can merge it in once we've completed testing sessions with users
this week x
—
Reply to this email directly, view it on GitHub
https://github.com/alphagov/forms-prototypes/pull/176#issuecomment-1400380071,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF3XHE6IKW3D73ES5FFK5ZTWT2DYVANCNFSM6AAAAAAUALHXGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Have merged this now. @deberny happy to make more changes if you want to - which page did you mean?


dynamic import async component  gets error when build

I'm building a blog also using vite-ssg. I have a page whose dir is like './src/pages/post/[name].vue', here I'm using the name param to dynamic import the .md component:
const props = defineProps<{ name: string }>();

const { name } = toRefs(props);

const modules = import.meta.glob("../../mds/blog/*.md");

const markdown = defineAsyncComponent(
  () => import(`../../mds/blog/${name.value}.md`)
 //  modules[`../../mds/blog/${name.value}.md`]
);

it's ok to run dev, but when I run build, I've got this error:
✓ 30 modules transformed.
.vite-ssg-temp/main.js                     143.25 KiB
.vite-ssg-temp/assets/style.b0296a56.css   23.43 KiB

[vite-ssg] Rendering Pages... (4)
[Vue warn]: Unhandled error during execution of async component loader
  at <AsyncComponentWrapper ref=fn<ref> >
[Vue warn]: Unhandled error during execution of setup function
  at <AsyncComponentWrapper ref=fn<ref> >
Error: Unknown variable dynamic import: ../../mds/blog/:name.md
    at /home/qi/documents/vite-blog/.vite-ssg-temp/main.js:446:96
    at new Promise (<anonymous>)
    at __variableDynamicImportRuntime0__ (/home/qi/documents/vite-blog/.vite-ssg-temp/main.js:445:14)
    at /home/qi/documents/vite-blog/.vite-ssg-temp/main.js:458:57
    at load (/home/qi/documents/vite-blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1512:17)
    at setup (/home/qi/documents/vite-blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1565:24)
    at callWithErrorHandling (/home/qi/documents/vite-blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6582:22)
    at setupStatefulComponent (/home/qi/documents/vite-blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6208:29)
    at setupComponent (/home/qi/documents/vite-blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6164:11)
    at renderComponentVNode (/home/qi/documents/vite-blog/node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:198:17)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I think it's might be that the param name is not available in build ?  Or maybe I'm writing the wrong way, is there any workaround?

@hannoeru  checkout this branch then yarn install && yarn build shall reproduce

Because you are setting includeAllRoutes to true in vite-ssg options, that will include all routes including dynamic routes name. which is :name in here, the default option is excludes any dynamic routes.
You can check this repo https://github.com/antfu/antfu.me to see how to use markdown with SSG in Vite.
As this is not related to this plugin so I will close it.

I was understanding it wrong 😂，thanks for you suggestion!


Feat: move readFromTail and CleanFiles from watcher config to collect…

… config in filesource

Fix: https://github.com/loggie-io/loggie/issues/565


Creating evidence (POST /api/evidence) may not conform to evidence schema

BEL formats are converted into Evidence JSON schema which currently doesn't conform to http://next.belframework.org/schema/evidence.schema.json.

Make citation.authors an array or null
Metadata needs to be objects with name/value (optional uri) properties
Metadata object items should be allowed
Return single evidence resources as object instead of array
The references section should be added, but treated as an unchecked object (for now)

Fixed. Now working on rebuilding BEL evidence from public corpora. Will update on next.belframework.org later today.

An example of an evidence-collection resource and an evidence resource are provided in this gist.
An evidence resource is a JSON object with an evidence property and the evidence-collection resource holds zero or more of these evidence resources.
Additionally the facets property has been removed from each evidence resource since this is implementation data not useful to the client. The facets property still remains on the outer JSON object.
@wshayes How does this representation look? Will it improve client-side processing?

The approach and gist looks good to me.

Ok, thanks. This approach has been deployed to next.belframework.org. For example look at the documentation example for GET /api/evidence.
I am missing documentation for /api/namespaces and the examples are incorrect for /api/annotations/....

Documentation is complete for this, closing.


first pass at updating references

TL;DR
Please replace this text with a description of what this PR accomplishes.
Type

[x] Bug Fix

Are all requirements met?

[x] Code completed (for first phase, self-references)

Complete description
updated references
Tracking Issue
https://github.com/lyft/flyte/issues/744

And, @EngHabu -- this is an interesting error, that I need to think more about:
https://github.com/flyteorg/flytestdlib/pull/72/checks?check_run_id=1925315802
It looks like it is pulling the latest tag (v0.3.11) which has old/original module name.  But, I'm not sure what directive is calling (yet).  It also looks like there is a bit of a mess around
lyft/boilerplate.
I should also move this conversation elsewhere (since this is separate from flytectl -- this PR does seem like accomplishes the self-reference part, but then will need a follow-up to address the other dependency references)


How to export image

Great library, I would like to ask how to export pictures？

Oh, I can get it by plotlyId.
const image = await Plotly.toImage(plot_ref.value.plotlyId, {
        format: 'png',
        height: 800,
        width: 1000,
        scale: 1
      });


Stengthen types around AuthResponse

This PR strengthens the types around AuthReponse inspired by the changes in #75
Creating this PR as we did not get a response to https://github.com/Azure/ms-rest-nodeauth/pull/75#issuecomment-770492773
Additionally, this updates the execAz command to return a rejected promise when there is no output from running the az command

@ramya-rao-a Ah, sorry - I totally missed your message over in #75!
You might have to release these changes as semver-major, if the version numbers of this package are following semantic versioning. This is because I think some of these type changes are breaking backwards compatibility (but they're more correct than before).
Specifically, the change to the return type of withAuthFile() does not seem to be backwards compatible.

Hey @arthurschreiber
Can you elaborate on why the change in the return type for withAuthFile() would be breaking while similar changes to the return types for other method would not be?
Previously, the return type would be around TokenCredentialsBase and now it would be ApplicationTokenCredentials | ApplicationTokenCertificateCredentials. Both ApplicationTokenCredentials and ApplicationTokenCertificateCredentials extend TokenCredentialsBase.
If we were changing the return type from say ApplicationTokenCredentials to ApplicationTokenCredentials | ApplicationTokenCertificateCredentials, then I can see how the change would be breaking because not all properties of ApplicationTokenCredentials are available in ApplicationTokenCertificateCredentials
@sadasant, I see you have upvoted Arthur's concerns above. Do you have any insights on how the changes to the withAuthFile is breaking?

@ramya-rao-a no, I think you’re correct, I just wanted to validate the feedback somehow. Feedback is always good!


how put lines in different positions

Hi. When I have:
A-A
A-B
B-A
How to put the lines in different positions and not one over other? As in the image?
Thank you.

Was there a solution found for this problem?


Update README now that asyncqt is officially unmaintained

Ref https://github.com/gmarull/asyncqt/blob/master/README.rst.

Thanks!

Thanks!


yarn test Refference Error

Running yarn test I am getting Refference Error:
    ReferenceError: TextDecoder is not defined

TextDecoder is used in ipfs-http-client. When using the lib, it is working fine. Only the test suites are not working.

Same issue here.


Document Log4j security model

We should document our security model on our security page.
An example of such a description is the Commons Security Model

@rm5248, @swebb2066, @fluffynuts and @grobmeier: maybe this could be a document shared by all the projects?
The security risks seems pretty much similar to me.

From the top of my head, our security model should relieve us from any responsibility for:

CRLF injections if the user uses a line-oriented tool to parse logs,
other kinds of data corruption if the user uses PatternLayout to generate JSON, XML or other structured formats,

Attacks that require access to a configuration file should not be considered vulnerabilities.

I agree, one security model should match for all logging projects - maybe some extensions are necessary for Flume and Chainsaw

This Commons discussion might be interesting.
When the document is ready, we might ask @raboof to proofread it.

Some initial thoughts about this:

Configuration files or configuration code have the ability to execute arbitrary code by using custom plugins; as such, configurations must be controlled by the programmer, not arbitrary users.
Log message parameters are not evaluated for any sort of template strings like {}; template strings are limited to the non-parameter message argument. As such, log message parameters are not treated specially (such as with a prepared statement in SQL). When structure-preserving encoding is desired for things besides the log message as a whole, the Message API should be used for logging structured data rather than strings.
Unstructured layouts shouldn't be used if any user-controlled data can be logged through them; this largely includes logging exceptions if said exceptions can contain user input (which is a common use case for exceptions).
Code signing and verification is only performed at the artifact level (i.e., our jars, zips, and tarballs); we do not rely on jar signing to validate plugins or extensions (unlike, say, the Java cryptography APIs which require signed jars typically).
Given the equivalence to the halting problem, we cannot generically support any form of log masking for sensitive data. While external plugins may support limited forms of masking (e.g., for credit card numbers or similar easily identifiable byte patterns), it is up to the programmer to explicitly mark sensitive data for masking.
While the project goes to great lengths to minimize performance overhead along with options for minimizing latency or maximizing throughput, we cannot guarantee absolute availability of the system when using synchronous logging. If your application is writing log data faster than it can store it to disk, synchronous logging will affect the availability of your application. Using asynchronous logging can help to an extent here, though we do not support back pressure signals (this might be a patches welcome area; not sure if we need to define this in the security model).
We do not support running in a Java SecurityManager; this API is being removed from Java anyways.
Configurations can read system properties, environment variables, arguments to the main program, and any other data sources made available via StrLookup plugins (which includes some HTTP-related data if you use the WebLookup plugin).

Then we have some bits that are specific to various systems:

When using JNDI for configuration files (as in a JavaEE/JakartaEE application server) or for use with dependency injection of shared server resources (such as JMS connection pools, JDBC connection pools, etc.), only the java scheme is supported. We do not support nor recommend use of other JNDI providers that interact with potentially untrusted remote data sources due to the weak security model of JNDI itself. Yes, that means we don't support LDAP, RMI, DNS, or any other Context providers.
When using an unstructured layout, we cannot guarantee that user input cannot interfere with the output of the formatted log message. Within the pattern layout plugin specifically, we do offer various encoding methods to help address this for different use cases (such as encoding or escaping new lines or other special characters used in various formats), but they're all opt-in.
When using a structured layout such as JsonTemplateLayout, XML, etc., log message input data is encoded appropriately to the target layout (e.g., a log message containing XML data will be properly escaped inside an XML layout).
Advanced methods of handling configuration (such as a refresh period for the config file, JMX remote management, or other remote methods for updating a config) must be protected by the programmer behind some form of authentication and authorization; it is beyond the scope of this library to hand wave away your identity solution or file permissions.
Use of string lookup plugins that can reference user-controlled data should not be used with unstructured layouts
Use of PatternLayout is more of a developer convenience than a production-quality layout that can be reliably parsed by log collectors or other derivative systems. In that sense, any inline JSON, whitespace, XML, etc., are not treated differently as pattern layouts are fairly arbitrary. When a reliable format is needed for parsing the output of logs, a structured layout should be used.
Any form of encryption or signatures used on log data directly from the library must use a proper key management system. Use of cryptography anywhere requires a properly designed key management system, and any plugins or extensions that offer to do so using a single static key (symmetric or asymmetric) are likely broken beyond repair.
When using compression, if logs can contain user input, then the compressed log output must not be viewable directly or indirectly by the user if said logs are supposed to be private. This relates to the CRIME attack which affects older versions of TLS.

The Securing Tomcat page might also help as an example.

Yes, I covered that point in

Advanced methods of handling configuration (such as a refresh period for the config file, JMX remote management, or other remote methods for updating a config) must be protected by the programmer behind some form of authentication and authorization; it is beyond the scope of this library to hand wave away your identity solution or file permissions.

Though I suppose JMX in general could use a warning about using it properly, especially once it's been extracted into a standalone module.


7/25 Publish

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


5 digit extension is incorrect

https://docs.microsoft.com/en-us/microsoftteams/what-are-dial-plans#sample-normalization-rules
the regex number pattern in the table on this doc is incorrect under the sample normalization rules. the second rule "5digitExtension"
shows ^5(\d{4})$ and should display -
^(\d{5})$

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


spawnSync is not cross-platform

Steps To Reproduce:

On Windows: try to call the "runCommitLintOnMsg" function or debug a test to see the function results.

Current Results:
'spawnSync npx ENOENT'
workaround (not recommended) :
https://stackoverflow.com/a/37138541
Exepected Results:
Commitlint should be executed without errors.

Not recommended why?

Not recommended why?

My guess is: we might have related issues about this workaround in the future or the ".cmd" suffix may not work in all environments.

or the ".cmd" suffix may not work in all environments.

If it doesn't work in all environments, then let's only use .cmd in Windows? Simple solution really.


Driver and executor Pods will still be created after spark application has been deleted

Hi all,
We notice that if a sparkapplication is deleted immediately after creation, the driver/executor pods of this sparkapplication will still be created and keep running until completed.
To reproduce, we could use sparkctl with following commands:
> ./sparkctl create ../examples/spark-py-pi.yaml
SparkApplication "pyspark-pi" created

After creation, do the deletion immediately with:
> ./sparkctl delete pyspark-pi
SparkApplication "pyspark-pi" deleted

Although it shows the SparkApplication "pyspark-pi" is deleted, if we check the Pods with kubectl we could see that driver Pod is created and running:
> kubectl get pods -o wide
pyspark-pi-driver        1/1     Running

We would like to confirm with you whether this is expected behavior and do we have approaches to avoid this corner case?
Thanks!

I also ran into this problem when deleting a running sparkapplicaiton.
waiting for a solution.

@liyinan926


Implement no_std version of error

Closes #53
Creates the rclrs_core crate, and adds the error types + unit tests.
From a design standpoint - should I attempt to re-work the RclStatusCode to be more like a Result? Or stay as close to what rcl provides as possible?

I can do that, sure, but that means this one PR will be closing a lot of issues at the same time (since I'm not sure that this will compile until all the changes are implemented).
Also, from what I understand, Arc and Mutex, as well as most heap allocations will not work with no_std. Which means we may have difficulty implementing things like the "handles" for the various components. Part of the reason I was splitting this to a separate crate was so that we could use rclrs to import from that crate and add in the heap features, making the API look like it does now, and leaving rclrs_core as just a wrapper over the various rcl pieces.
Did you have a different idea for how to approach this problem?


HTML output?

Hi - just discovered this yesterday and it is extremely helpful! I would love to incorporate it into CI at work. When our playwright tests fail, we output the results HTML folder which is then statically served by our CI provider. It'd be great to be able to run a command like npx @eslint/config-inspector --outDir dist/eslint-config after our CI lint job fails. I'm imagining that would  dump some HTML/JS/CSS files into a folder so that it can be served as a webpage (like playwright).
Would this be possible? I haven't looked into whether the filtering is happening server-side or client-side. If it's server-side, it might not be so easy.

It's already implemented in https://github.com/eslint/config-inspector/pull/17, just haven't released yet


Project update

Will there be a project update in the future ? thank you

I've taken a break from updates at the moment because I'm focused on creating tools for other work projects.
But if a request pull or donate happens, I will prioritize UNanite.


Update Tabs component in Salt and Salt Next Figma libraries

Changes are done and merged. Needs to be published.

@ivan-calderon is this complete, can we close?

Completed. Branches as follow:

Tabs Figma branch (Next)
Tabs Figma branch (Light)
Tabs Figma branch (Dark)


Show sample batch content

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
Hi thanks for the library! A common practice of deep learning seems to be that, we log the exact inputs and labels of (a portion of) a single batch. For example, I personally log the input_ids (and convert it back to text), attention_masks, model outputs, labels, etc.
This can help debug a lot of problems. For example, if someone has a wrong BOS/EOS token, then it can be spotted immediately. As another example, if we want to train on completions only but forgets to do so, the logged labels can hint us on that.
✔ Solution
(see above)
❓ Alternatives
No response
📝 Additional Context
No response
Acknowledgements

[X] My issue title is concise, descriptive, and in title casing.
[X] I have searched the existing issues to make sure this feature has not been requested yet.
[X] I have provided enough information for the maintainers to understand and evaluate this request.

This might be feasible using the trainer_callback (see https://github.com/huggingface/transformers/blob/main/src/transformers/trainer_callback.py#L283-L284)
However, since it passes the train_dataloader to say the on_log or on_step_end callback, you could in theory get data from it, but I'm not exactly sure how to get the current row at the current step without moving the iterator on the dataloader and affecting the actual training.
If you're up for tackling this and submitting a PR, we would be happy to help and get it merged in.

I am currently writing a subclass and hack the compute_loss for it for my internal code, at the same time I want to use axolotl as a comparison test to reveal potential bugs my internal code (i.e. axolotl and my code should get same accuracy). Thus I may not have enough time to PR to axolotl. But if you like to have a look at how I hacked it as a rough draft, feel free to ping me.


Fix: Changed escape to correct escape attr helper

as above + short syntax

:+1:

Thank you, @ins0!

thanks @localheinz for this morning merge run

@ins0
:smile_cat:


Extract code into separate rpc client

Refactor command client so it can be used by multiple applications at once. I need this for my clipboard manager that is active at the same time as vscode.
This pull request basically does two things:

Splits the very large command_client.py in to several python files in the new rpc_client directory. This is done purely mechanically with as minimal changes as possible.
Introduces a new Talon action rpc_client_run_command that takes the communication directory name as well as the callback to press the keys that starts the request execution. This is what allows us to run multiple applications at once.

@knausj85 Will test this.

@nriley Mind having a look at this so we can merge it?


[BUG] When i change my fps counter to 240 its still stays 165 like my monitor

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
So even if i change the fps cap to 240 its still capping it at 162-165 idk why this is happening pls fix

Are you using exclusive fullscreen?

@Beyroz, If you are getting 240 FPS, it is capped by the amount the GPU can handle and what your display can show. Even if you set your fps to 240 but your monitor can only show 165, it will show 165.
The FPS shown is the weakest link between your GPU, Cable and Monitor. Your GPU can probably handle 1000fps but it depends on the speed of the cable and connectors to bring that. Then, there is the monitor restriction otherwise the monitor would take tonnes of power and not be able to continue.
If it doesn't make sense, I cant explain it better, sorry.

Fellas how do i fix my bloxstrap not capping my fps no more

Fellas how do i fix my bloxstrap not capping my fps no more

Open a new issue, what you said is way to broad.

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.

Same here, I'm not even in exclusive fullscreen, heck I even used windowed mode, my fps is capped at 240 even though I set it to 999. Every other game uncaps so it's not my fault. I've gotten 6000fps in osu so.

my fps is capped at 240 even though

You're not having the same issue then. Their issue is that they can't reach 240.
Roblox is intentionally limiting you to 240 for good reason. You can temporarily get past it, but I wouldn't recommend doing so if you have no real need.

my fps is capped at 240 even though

You're not having the same issue then. Their issue is that they can't reach 240.
Roblox is intentionally limiting you to 240 for good reason. You can temporarily get past it, but I wouldn't recommend doing so if you have no real need.

I found out you have to disable their limit 240 flag option


Update findgroups command

Codecov Report

Merging #466 (ef65e67) into master (00dde6e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #466   +/-   ##
=========================================
  Coverage     79.89%   79.89%
  Complexity     1069     1069
=========================================
  Files           136      136
  Lines          3208     3208
  Branches        430      430
=========================================
  Hits           2563     2563
  Misses          573      573
  Partials         72       72

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 00dde6e...ef65e67. Read the comment docs.

LGTM


Enable AES and SHA3 optimisations on Apple Silicon M4-based macOS systems

AES gets a performance enhancement of 7-33%.
Tested on an M4 Pro, but the CPU cores are the same on M4 and M4 Max.

I don't think the CI failure is related to this change
80-test_cmp_http.t ......................
Failed 1/6 subtests

This pull request is ready to merge

Merged to the master branch. Thank you for your contribution.

80-test_cmp_http.t ......................
Failed 1/6 subtests

@gerardobladimirmaciaslue

80-test_cmp_http.
Failed 1/6 subtests

This is usually related to proxy environment variables, but without any more information it is not really possible to help you.
it's generally a better idea to open a GitHub question with as much information as you can provide, after checking existing issues and questions to see if someone else has the same problem (and maybe a solution).


[Bug]: I am not able to reopen my dev container

Feature id and version
ghcr.io/devcontainers-contrib/features/fd:1
Devcontainer base Image
No response
What happened?
When I was trying to open a dev container from a json, It was failing due to the above feature, the issue started here
#0 13.40 nanolayer.installers.gh_release.resolvers.asset_resolver.AssetResolver.AssetResolverError: Too many matches found: ['fd-v8.7.0-arm-unknown-linux-gnueabihf.tar.gz', 'fd-v8.7.0-i686-unknown-linux-gnu.tar.gz']
Relevant log output
> [devcontainer dev_containers_target_stage 15/17] RUN chmod -R 0755 /tmp/dev-container-features/fd_6 && cd /tmp/dev-container-features/fd_6 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh:
#0 0.164 ==========================
[2023-06-07T12:32:31.627Z] =================================================
#0 0.164 Feature       : fd (via Github Releases)
#0 0.164 Description   : fd is a simple, fast and user-friendly alternative to 'find'.
#0 0.164 Id            : ghcr.io/devcontainers-contrib/features/fd
#0 0.164 Version       : 1.0.11
#0 0.164 Documentation : http://github.com/devcontainers-contrib/features/tree/main/src/fd
#0 0.164 Options       :
#0 0.164     VERSION="latest"
#0 0.164 ===========================================================================
[2023-06-07T12:32:31.628Z]
#0 0.167 bash: cannot set terminal process group (1): Inappropriate ioctl for device
#0 0.167 bash: no job control in this shell
#0 6.227 nanolayer
#0 11.72 cd /tmp/tmpo822hkn5 && chmod +x -R . && _REMOTE_USER="codespace" _REMOTE_USER_HOME="/home/codespace" REPO="sharkdp/fd" BINARYNAMES="fd" VERSION="latest" ASSETREGEX="" BINLOCATION="/usr/local/bin" LIBNAME="" LIBLOCATION="/usr/local/lib" NANOLAYER_VERBOSE="" NANOLAYER_FORCE_CLI_INSTALLATION="" NANOLAYER_PROPAGATE_CLI_LOCATION="1" NANOLAYER_CLI_LOCATION="/tmp/nanolayer-JGZvzE0sFQ/nanolayer" bash  -i  +H ./install.sh
#0 11.72 Found a pre-existing nanolayer which were given in env varialbe: /tmp/nanolayer-JGZvzE0sFQ/nanolayer

#0 13.32 'fd-musl_8.7.0_amd64.deb' filtered by '([Aa]md64|-x64|x64|x86[_-]64)' (negative)

#0 13.33 'fd-musl_8.7.0_i686.deb' filtered by '(\.deb|\.rpm|\.pkg|\.apk|\.[Aa]ppImage|\.snap)' (negative)

#0 13.33 'fd-v8.7.0-i686-pc-windows-msvc.zip' filtered by '(windows|Windows|WINDOWS|win32|\-win\-|\.msi$|.msixbundle$|\.e
[2023-06-07T12:32:31.628Z] xe$)' (negative)

#0 13.33 'fd-v8.7.0-x86_64-apple-darwin.tar.gz' filtered by '([Aa]md64|-x64|x64|x86[_-]64)' (negative)

#0 13.33 'fd-v8.7.0-x86_64-pc-windows-gnu.zip' filtered by '([Aa]md64|-x64|x64|x86[_-]64)' (negative)

#0 13.33 'fd-v8.7.0-x86_64-pc-windows-msvc.zip' filtered by '([Aa]md64|-x64|x64|x86[_-]64)' (negative)

#0 13.33 'fd-v8.7.0-x86_64-unknown-linux-gnu.tar.gz' filtered by '([Aa]md64|-x64|x64|x86[_-]64)' (negative)

#0 13.33 'fd-v8.7.0-x86_64-unknown-linux-musl.tar.gz' filtered by '([Aa]md64|-x64|x64|x86[_-]64)' (negative)

#0 13.33 'fd_8.7.0_amd64.deb' filtered by '([Aa]md64|-x64|x64|x86[_-]64)' (negative)

#0 13.33 'fd_8.7.0_arm64.deb' filtered by '(\.deb|\.rpm|\.pkg|\.apk|\.[Aa]ppImage|\.snap)' (negative)

#0 13.33 'fd_8.7.0_armhf.deb' filtered by '([Aa][Rr][Mm]hf)' (negative)

#0 13.33 'fd_8.7.0_i686.deb' filtered by '(\.deb|\.rpm|\.pkg|\.apk|\.[Aa]ppImage|\.snap)' (negative)

#0 13.33 'fd-v8.7.0-aarch64-unknown-linux-gnu.tar.gz' filtered by '([Aa]rm64|ARM64|-ARM)'
[2023-06-07T12:32:31.628Z]
#0 13.33 'fd-v8.7.0-arm-unknown-linux-gnueabihf.tar.gz' filtered by '([Aa]rm64|ARM64|-ARM)'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-musleabihf.tar.gz' filtered by '([Aa]rm64|ARM64|-ARM)'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-gnu.tar.gz' filtered by '([Aa]rm64|ARM64|-ARM)'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-musl.tar.gz' filtered by '([Aa]rm64|ARM64|-ARM)'

#0 13.33 'fd-v8.7.0-aarch64-unknown-linux-gnu.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-gnueabihf.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-musleabihf.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-gnu.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-musl.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-aarch64-unknown-linux-gnu.tar.gz' filtered by '.*static.*'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-gnueabihf.tar.gz' filtered by '.*static.*'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-musleabihf.tar.gz' filtere
[2023-06-07T12:32:31.628Z] d by '.*static.*'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-gnu.tar.gz' filtered by '.*static.*'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-musl.tar.gz' filtered by '.*static.*'

#0 13.33 'fd-v8.7.0-aarch64-unknown-linux-gnu.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-gnueabihf.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-musleabihf.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-gnu.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-i686-unknown-linux-musl.tar.gz' filtered by '(?i)(debian)'

#0 13.33 'fd-v8.7.0-arm-unknown-linux-musleabihf.tar.gz' filtered by '(?i)(alpine|musl)' (negative)

#0 13.33 'fd-v8.7.0-i686-unknown-linux-musl.tar.gz' filtered by '(?i)(alpine|musl)' (negative)

#0 13.33 'fd-v8.7.0-aarch64-unknown-linux-gnu.tar.gz' filtered by '(?i)(arch)' (negative)
[2023-06-07T12:32:31.628Z]
#0 13.39 Traceback (most recent call last):

#0 13.40   File "<string>", line 1, in <module>

#0 13.40   File "nanolayer.__main__", line 50, in main

#0 13.40   File "typer.main", line 328, in __call__

#0 13.40   File "typer.main", line 311, in __call__

#0 13.40   File "click.core", line 1130, in __call__

#0 13.40   File "typer.core", line 778, in main

#0 13.40   File "typer.core", line 216, in _main

#0 13.40   File "click.core", line 1657, in invoke

#0 13.40   File "click.core", line 1657, in invoke

#0 13.40   File "click.core", line 1404, in invoke
[2023-06-07T12:32:31.628Z]
#0 13.40   File "click.core", line 760, in invoke

#0 13.40   File "typer.main", line 683, in wrapper

#0 13.40   File "nanolayer.cli.install", line 159, in install_gh_release_binary

#0 13.40   File "nanolayer.installers.gh_release.gh_release_installer", line 163, in install

#0 13.40   File "nanolayer.installers.gh_release.resolvers.asset_resolver", line 292, in resolve

#0 13.40 nanolayer.installers.gh_release.resolvers.asset_resolver.AssetResolver.AssetResolverError: Too many matches found: ['fd-v8.7.0-arm-unknown-linux-gnueabihf.tar.gz', 'fd-v8.7.0-i686-unknown-linux-gnu.tar.gz']

#0 13.50 Sentry is attempting to send 2 pending error messages

#0 13.50 Waiting up to 2 seconds

#0 13.50 Press Ctrl-C to quit

#0 13.75 Traceback (most recent call last):
[2023-06-07T12:32:31.628Z]
#0 13.75   File "<string>", line 1, in <module>
#0 13.75   File "nanolayer.__main__", line 50, in main
#0 13.75   File "typer.main", line 328, in __call__
#0 13.75   File "typer.main", line 311, in __call__
#0 13.75   File "click.core", line 1130, in __call__
#0 13.75   File "typer.core", line 778, in main
#0 13.75   File "typer.core", line 216, in _main
#0 13.75   File "click.core", line 1657, in invoke
#0 13.75   File "click.core", line 1657, in invoke
#0 13.75   File "click.core", line 1404, in invoke
#0 13.75   File "click.core", line 760, in invoke
#0 13.75   File "typer.main", line 683, in wrapper
#0 13.75   File "nanolayer.cli.install", line 65, in install_devcontainer_feature
#0 13.75   File "nanolayer.installers.devcontainer_feature.oci_feature_installer", line 134, in install
#0 13.75   File "nanolayer.utils.invoker", line 56, in invoke
#0 13.75 nanolayer.utils.invoker.Invoker.InvokerException: The command 'cd /tmp/tmpo822hkn5 && chmod +x -R . && _REMOTE_USER="codespace" _REMOTE_USE
[2023-06-07T12:32:31.628Z] R_HOME="/home/codespace" REPO="sharkdp/fd" BINARYNAMES="fd" VERSION="latest" ASSETREGEX="" BINLOCATION="/usr/local/bin" LIBNAME="" LIBLOCATION="/usr/local/lib" NANOLAYER_VERBOSE="" NANOLAYER_FORCE_CLI_INSTALLATION="" NANOLAYER_PROPAGATE_CLI_LOCATION="1" NANOLAYER_CLI_LOCATION="/tmp/nanolayer-JGZvzE0sFQ/nanolayer" bash  -i  +H ./install.sh' failed. error: Return Code: 1. see logs for details.
[2023-06-07T12:32:31.628Z]
#0 13.85 Sentry is attempting to send 2 pending error messages
#0 13.85 Waiting up to 2 seconds
#0 13.85 Press Ctrl-C to quit
#0 14.00 ERROR: Feature "fd (via Github Releases)" (ghcr.io/devcontainers-contrib/features/fd) failed to install! Look at the documentation at http://github.com/devcontainers-contrib/features/tree/main/src/fd for help troubleshooting this error.
------
failed to solve: process "/bin/sh -c chmod -R 0755 /tmp/dev-container-features/fd_6 && cd /tmp/dev-container-features/fd_6 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh" did not complete successfully: exit code: 1
[2023-06-07T12:32:31.632Z] Stop (17438 ms): Run: docker-compose --project-name butler_server_devcontainer -f /Users/guru/Desktop/greyorange/butler_server/.devcontainer/docker-compose.yml -f /Users/guru/Library/Application Support/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1686141134193.yml build db zookeeper kafka kafka-ui emqx devcontainer
[2023-06-07T12:32:31.632Z] Error: Command failed: docker-compose --project-name butler_server_devcontainer -f /Users/guru/Desktop/greyorange/butler_server/.devcontainer/docker-compose.yml -f /Users/guru/Library/Application Support/Code/User/globalStorage/ms-vscode-remote.remote-containers/data/docker-compose/docker-compose.devcontainer.build-1686141134193.yml build db zookeeper kafka kafka-ui emqx devcontainer
[2023-06-07T12:32:31.632Z]     at FD (/Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1912:412)
[2023-06-07T12:32:31.632Z]     at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-06-07T12:32:31.632Z]     at async _se (/Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1912:2381)
[2023-06-07T12:32:31.632Z]     at async Bse (/Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1894:3170)
[2023-06-07T12:32:31.632Z]     at async Xse (/Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1961:2799)
[2023-06-07T12:32:31.632Z]     at async vh (/Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1961:3741)
[2023-06-07T12:32:31.632Z]     at async gae (/Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:2092:10213)
[2023-06-07T12:32:31.633Z]     at async mae (/Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:2092:9954)
[2023-06-07T12:32:31.635Z] Stop (28911 ms): Run: /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /Users/guru/Library/Application Support/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-7ba27fb0-2819-4e83-a394-d99ad7b20b1b1686141121703 --workspace-folder /Users/guru/Desktop/greyorange/butler_server --workspace-mount-consistency cached --id-label devcontainer.local_folder=/Users/guru/Desktop/greyorange/butler_server --id-label devcontainer.config_file=/Users/guru/Desktop/greyorange/butler_server/.devcontainer/devcontainer.json --log-level debug --log-format json --config /Users/guru/Desktop/greyorange/butler_server/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2023-06-07T12:32:31.635Z] Exit code 1
[2023-06-07T12:32:31.637Z] Command failed: /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Users/guru/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /Users/guru/Library/Application Support/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-7ba27fb0-2819-4e83-a394-d99ad7b20b1b1686141121703 --workspace-folder /Users/guru/Desktop/greyorange/butler_server --workspace-mount-consistency cached --id-label devcontainer.local_folder=/Users/guru/Desktop/greyorange/butler_server --id-label devcontainer.config_file=/Users/guru/Desktop/greyorange/butler_server/.devcontainer/devcontainer.json --log-level debug --log-format json --config /Users/guru/Desktop/greyorange/butler_server/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2023-06-07T12:32:31.637Z] Exit code 1

I have improved the ARM asset detection in latest version, please try ghcr.io/devcontainers-contrib/features/fd:1.0.12


Add channel upgrade ack and confirm tx commands

Summary
As part of the work of implementing channel upgradability in Hermes, we'll need to add hermes tx chan-upgrade-ack and hermes tx chan-upgrade-confirm CLI commands, similar to the hermes tx chan-open-* family of commands.
Part of this work also includes defining the message types needed in order for these commands to work.

Done by https://github.com/informalsystems/hermes/pull/3228


Query results not making sense

https://arax.ncats.io/?source=ARS&id=0cdc5dab-49ba-4a3d-9688-8f36f95b964d
Results are not making sense. E.g. coumarin being in the results and also immunology

Message received. I am investigating. https://github.com/RTXteam/RTX/issues/1538

My team has advised me that this issue is likely to be resolved when the new version of the RTX-KG2 knowledge graph (KG2.6.7) is deployed into production.

Just an FYI on this issue, biolink:correlated_with will not give you all the related phenotypes. Broadening the query using biolink:related_to gives 16 associated phenotypes and diseases:
{
  "edges": {
    "N1": {
      "object": "n1",
      "predicates": [
        "biolink:has_normalized_google_distance_with"
      ],
      "relation": "N1",
      "subject": "n0"
    },
    "e0": {
      "object": "n1",
      "predicates": [
        "biolink:correlated_with",
        "biolink:related_to"
      ],
      "subject": "n0"
    }
  },
  "nodes": {
    "n0": {
      "ids": [
        "MONDO:0005359"
      ],
      "is_set": false
    },
    "n1": {
      "categories": [
        "biolink:DiseaseOrPhenotypicFeature"
      ],
      "is_set": false
    }
  }
}

@edeutsch to test

Re-issuing this query seems to yield a better result with RTX-KG2.6.7:
https://arax.ncats.io/?r=15819
coumarin and immunology are no longer in the results list. Overall results seem better.
okay to close?

@cbizon ok to close?


Check if GodotConvexPolygonShape3D initialization happened

GodotConvexPolygonShape3D::get_support can run when _setup has not executed yet. In my testing especially when changing resolution.

I think technically there is still a race condition between the two, but don't know what's the appetite of adding a mutex to physics. I can't reproduce the issue with this workaround even when going fullscreen and back every frame.
Possibly this is the same issue someone else reproduced as well.

Is there an issue for this? If not it might be an idea to create one (preferably with MRP and / or reproduction instructions), to discuss solutions.
Fixing a race condition by changing the timing slightly (if this is what this PR is doing) would not be a great fix. So as you say a mutex, or more likely rearranging the higher level logic so that this could not occur is probably more appropriate.

I've added the issue here - https://github.com/godotengine/godot/issues/92956
You're right that this needs a higher level fix - something like pausing physics until all the lifecycle events are processed.


readme.md: boltholdIndex, boltHoldIndex

In the readme.md
boltholdIndex and boltHoldIndex is mix used

Canonically it should be boltholdIndex.  I'll update the README.
Thanks for the heads up.

@timshannon Thank you for your fast response.
I actually came from storm. coz storm does not have index support for the query.
I have some questions. Is there any proper place to ask? or issuing here is okay?
I think store.Insert() is getting too slow when there are a lot of records (for me it's over 200,000 and it takes 500ms)

It should be pretty easy to switch to badgerhold and try it out.  The slow inserts may be due to Bolt as I believe inserts are slower than with Badger.  However if you are using one or more non-unique indexes, you may be running into issue #106.
I'm still trying to figure out the best way to handle that.  I looked through storm's code to see if they were handling it better, but they do the same thing.  The problem is the index is just a slice, and when that slice gets really large it can take a long time to read, write and serialize.
Real databases break their indexes into btree pages the same as any other data, so I'd like to do something similar, but I haven't gotten around to working through all the implications of doing that yet.

yes, this is an interesting problem, and probably the next step to scaling bolthold into larger databases. Are implementations in databases like sqlite relevant for reference? I assume they solve this problem.


Blank screen/work items not loading when clicking on work items in estimation tool

Last week when our team used the estimation tool, we had a blank screen when clicking on 1 work item.
This week, we had to use another method instead of the Estimate tool in DevOps, because every work item we clicked on resulted in a blank screen/the work item not loading whatsoever. We were working in offline mode. Please advise.

We experience this as well. The problem occours everytime we use the "coffee" vote.

This is probably the same as #13 and #14. We're look into this now and will release a fix asap.

We released an update that should resolve this (2.3.1).


have no auth screen

hi，
when SignMessage or SignTransaction, can open the trust wallet App,
but there have no auth screen in the trust App.

like the demo

Hi, We have removed TrustSDK from the app, so it's not working anymore

we re-implemented rn sdk with multi coin support, close old issue now


Gmail reply header parser problem with languages different to english

The Gmail header parser problem that was fixed here #120 doesn't work if the language is different to english due the regex (it includes the word wrote).
/^\s*\>?\s*On.*\r?\n?\s*.*\s*wrote:\r?\n?$/
For other languages, such as Spanish where the new line looks like this:
El 27 de junio de 2014, 13:55<EMAIL_ADDRESS>escribió: The solution doesn't work.
Could make sense to change the regex to something like this??
/^\s*\>?\s*On.*\r?\n?\s*.*\s*:\r?\n?$/

Sorry to dig up an old thread but I was wondering if anything developed from this issue or is it still unsupported?

It is still failing on pt-br.


Fix packaging

Codecov Report

Merging #54 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #54   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          14     14
  Lines         452    452
  Branches       42     42
=====================================
  Hits          452    452

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 70078ab...118a1ca. Read the comment docs.


Background Modeling

I've been looking at the background modeling and it may be better to approach it by adding a node onto PointSource:
ps = PointSource(...,background_shape=Powerlaw() )

Otherwise, we are just adding a function inside of the plugin and have to dig into private members to access the free parameters of that function.
Is this too involved of an approach @giacomov ?

Sorry to intervene, just I was dealing with similar situations in astromodels.
If you add background to the source, does it not appear if the background is the property of the source? Background seems more to do with observation than with a source.
The source is included in multiple observations, with different backgrounds, what do you do then?
Maybe background could be another source, a "background" source, not part of the given point source.

I've found a solution dealing with just the plugin. I'll push tomorrow. Basically I just create an internal function and assign its parameters as nuisance.

See here:
https://github.com/giacomov/3ML/commit/8a6c0e2bb7e56f5d5f40f14fffb9bf1158266166

Hi,
as a general rule, you probably shouldn't have a discussion and act on it on a weekend... ;-)
Since the user is likely going to need to iterate the background modeling until he/she finds a good model, I think the most sensible way to handle it is through a separate source. That way you can interact with it using all the tools we already have, and then we you have found a good solution, you use it as background for something else.
Tomorrow I'll think this through a bit more and come up with some actionable idea.

No worries, this is basically what is going on except that it is buried in the plugin. This can be taken further outside, but the interaction will need to take place inside the plugin.

Here are my thoughts and my approach.
With SpectrumLike, we currently sum all the sources associated with the model when computing the likelihood:

    @staticmethod
    def _get_diff_flux_and_integral(likelihood_model):

        n_point_sources = likelihood_model.get_number_of_point_sources()

        # Make a function which will stack all point sources (OGIP do not support spatial dimension)

        def differential_flux(energies):
            fluxes = likelihood_model.get_point_source_fluxes(0, energies)

            # If we have only one point source, this will never be executed
            for i in range(1, n_point_sources):
                fluxes += likelihood_model.get_point_source_fluxes(i, energies)

            return fluxes

        # The following integrates the diffFlux function using Simpson's rule
        # This assume that the intervals e1,e2 are all small, which is guaranteed
        # for any reasonable response matrix, given that e1 and e2 are Monte-Carlo
        # energies. It also assumes that the function is smooth in the interval
        # e1 - e2 and twice-differentiable, again reasonable on small intervals for
        # decent models. It might fail for models with too sharp features, smaller
        # than the size of the monte carlo interval.

        def integral(e1, e2):
            # Simpson's rule

            return (e2 - e1) / 6.0 * (differential_flux(e1)
                                      + 4 * differential_flux((e1 + e2) / 2.0)
                                      + differential_flux(e2))

        return differential_flux, integral

This makes sense in the total = bkg+source part of the likelihood, but the conditional background part need to sum only over background sources, and we would need some kind of flag to differentiate.
I tried a rather ugly approach of building a Source inside the plugin:

 def set_background_model(self, background_shape):

        # we will create a point source for the background
        # with this shape

        bkg_ps = PointSource('background_model',0,0,spectral_shape=background_shape)

        self._background_model = Model(bkg_ps)

        # now extract the free parameters and set them to the nuisance list

        new_nuisance_parameters = self._nuisance_parameters

        for par_name, par in self._background_model.parameters.iteritems():

            new_name = "%s_bkg_%s" %(self._name, par.name)

            new_nuisance_parameters[new_name] = par

        differential_flux, integral = self._get_diff_flux_and_integral(self._background_model)

        self._background_integral_flux = integral

The source created here could be backed and created before passing to the class. What I do not like is that this is breaking the idea of sources passed to the model. You could instead add the source to the Model(), and then pass some sort of link that tells the plugin to only use that one for the background.
I took this approach following the idea that the background in the LAT plugin is not really an astromodels  "Source" but an internal property. Could that also be changed?

You are both touching on different issues here. Let me focus for the moment on how to achieve a "functional" background, instead of using the profile likelihoods.
Some thoughts in random order:

we need to provide a way for the user to iterate over the background fit, and seeing its results (residuals and so on). Indeed, we cannot assume that the user will know every time the function to be used and might need to adjust it.

the background pertain to an observation, i.e., to a plugin instance as @grburgess implied with his solution. Thus logically the background model does not belong into the Model itself (except for its parameters, that become nuisance parameters). Indeed, a Model is supposed to be an idealization of the sky and do not depend on any instrument

we have at least two cases: the typical X-ray case, where you have an observed spectrum and a background spectrum both measured directly, and the GBM-type case where you do not really have an independent background measurement, but you need to build it by interpolation. In both case, I would say, the background model should be compared to the background data and its likelihood summed to the total likelihood for the plugin. so that the background model is required also to model the background measurement and cannot go too crazy.

That being said, maybe a workflow would be:

back = XYLike.from_OGIP_background(...)

# or

back = XYLike.from_polynomial_fit(...)

# then fit a function to the background:

fitfunction = Powerlaw() # or whatever
parameters, like_values = xyl.fit(fit_function)
xyl.plot(x_scale='log', y_scale='log')

# Iterate until a good model is found, then:

ogip = OGIPLike(...., background=back)

# continue as usual

Note that I use the XYLike plugin as background for multiple reasons:

in general a background should be modeled in the count space, so no response is necessary
xylike can handle both Poisson and Gaussian data
we can use the get_log_like() method of XYLike inside OGIPLike to get the log-likelihood of the background model, and the function to get the expected background flux

What do you think?

I like the idea of having the background come from a plugin. Though, I wonder how biased you can become from fitting the background alone. It is probably mitigated with a good global optimizer and only a detail here.
I am modeling the background in count space and was going to ask you @giacomov if there was any case where that would not apply (it is emphasized in the XSPEC documentation).
I'm not opposed to XYLike, but SpectrumLike is binned, so maybe HistLike is a better choice? I can think of a few other issues, but in general I believe this approach is the same expect that the information is buried in the plugin instance rather.
So, when the background is coming from another plugin,

I will cycle through the plugin's parameters and add then as nuisance so that the fitting process picks them up
call the background model to get predicted counts
use get log like from the other plugin to sum with the other likelihoods

One issue I ran into is renaming parameters. I can name them in the dictionary to be associated with a plugin, but not in the parameter.name itself. @giacomov, what is the safe way to do this?

Hm, @giacomov, for me, the model is a model of representation of physical reality not just sky. Which is why it might include detector properties, in particular the background.
Otherwise, where do I keep them?
Of course, if they are specific to only one instance of plugin, they can be all hidden, but if not?

@volodymyrss you have a point, but there are different types of background.
A phenomenological background such as the one obtained from data in a typical X-ray on/off analysis definitely belongs to the data side, since it's applicability never goes beyond that specific data.
A more astronomical background such as the Galactic diffuse emission could as well belong to the Model, as it is always going to be there whatever instrument you choose to analyze that particular region of the sky.

Ok, but where I keep instrumental parameters, which I want to change and fit, and which shared by multiple plugin instances?
Is there a place for an Instrument Model?

@volodymyrss it would help me a lot if you could lay out the problem you are trying to solve. I guess it is an INTEGRAL analysis, can you describe in details how do you need it to work?
Normally nuisance parameters are added to the model by the plugin as "external parameters". Once each plugin has added its own nuisance parameters, you can also link them between each other and obtain what you want. But without details on what you want to achieve, it is not possible for me to understand if this is sufficient or not...

Regarding the
 XYLike.from_OGIP(....)

approach. Since these are all going to come from SpectrumLike and need the functionality of energy selection, etc., should we not build the internal background function from SpectrumLike rather than XYLike?

@giacomov one other issue I will run across is the rebinning and channel selection. They should remain the same between background data and total data. One way to solve is with a decorator on all those functions which sets the background plugin to the same selections/bins. This way you only need to add the get_log_like() of the background file.
The same behavior could be had by calculating the likelihood directly in the total plugin. Just depends on how we want it to look.

@grburgess I am not sure that it is the case. You can have a selection for the background with which you fit the background model, and a different selection for the "source".
For example, in the GBM you might be confident that you know how to model the K-edge in the counts space for the background spectrum (maybe putting a Gaussian there would suffice), however you do not trust the photon response in the middle of it and you exclude that region from the "source" spectrum. In this case you shouldn't exclude the K-edge from the background spectrum, but you should from the source one. Am I right?

Yup :) I was reading https://arxiv.org/abs/1007.1727 on a plane and realized this. It will then be on the user to really know what they are doing. I'll need to do some math and then I'll post my idea

@giacomov exactly, I have now tons of external parameters. They work similarly to cons_* things, except evolve with time. There are several needs for this.
But let me focus on one, related for background, since that's what this #227 issue is about.
Background in ISGRI consists of CXB (1), stray light from unmodeled off-axis sources (2), photon background generated in the spacecraft by photons and particles (3), and particles in the detector itself (4).
By default, we use maps averaged over long term, which sum all these things.
It is possible to model these components to a large degree.
So, following the logic you describe, I would put (1) and (2) in the model, and keep (3) and (4) in the plugin or external properties? Or maybe I put (3) in the model too (some of it is photons after all)? What if
I want to characterize local particle density, should I than put (4) in the model too?
I get that there is some physical sky independent of which instrument is used, and reconstructing it is the primary purpose of 3ML.
However, there is also a physical reality of instrument, and it might be hard to separate it from the sky contribution at first. To separate, by fitting, they are treated at the same level, as model.
Which is why I really need to have something like "instrument model" (which contains all kinds of background, and much more). Currently I achieve it with external parameters.
If you allow cons_* parameters, why not treat others in the same way (e.g background normalization, background shape parameters)
To be clear, what I described is not quite standard pipeline.

@volodymyrss I think you can still achieve this through modeling. However, some of these things seem like they should be outside the plugin as external software. Nevertheless, if you can model then, I suppose you can write them in as nuisance parameters. This is totally allowed.
I've now got the first attempt of background modeling implemented in #232
There is an example added that demonstrates how it is used.


Edge - Reduce visibility for util classes

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

We need to merge to Edge branch first.

We need to merge to Edge branch first.

Changed the base to staging commits, moving this to https://github.com/adobe/aepsdk-react-native/pull/77


1.12 Upgrade

Describe the bug

To Reproduce
Upgrade from 1.8 to 1.12
Expected
Upgrade to be successful and pods running.
Actual behavior
Agent Logs flooded with this errot
E0530 15:53:46.969895       1 ofSwitch.go:267] Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER
I0530 15:53:46.980139       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=26529 actualLength=1396
I0530 15:53:46.980159       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
E0530 15:53:46.980372       1 ofSwitch.go:267] Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER
I0530 15:53:46.989486       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=43364 actualLength=1396
I0530 15:53:46.989513       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
E0530 15:53:46.989734       1 ofSwitch.go:267] Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER
I0530 15:53:47.000031       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=14966 actualLength=1396
I0530 15:53:47.000060       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
E0530 15:53:47.000267       1 ofSwitch.go:267] Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER
I0530 15:53:47.010512       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=5891 actualLength=22
I0530 15:53:47.010551       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: buffer size too small"
E0530 15:53:47.010772       1 ofSwitch.go:267] Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER
I0530 15:53:47.019994       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=28525 actualLength=1396
I0530 15:53:47.020027       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
I0530 15:53:47.030227       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=25398 actualLength=1396
I0530 15:53:47.030247       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
I0530 15:53:47.039496       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=11572 actualLength=1396
I0530 15:53:47.039522       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
I0530 15:53:47.049930       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=12465 actualLength=1396
I0530 15:53:47.049956       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
I0530 15:53:47.059833       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=26990 actualLength=1158
I0530 15:53:47.059850       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: bad rdata"
E0530 15:53:47.060144       1 ofSwitch.go:267] Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER
I0530 15:53:47.070512       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=43713 actualLength=1190
I0530 15:53:47.070533       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: buffer size too small"
E0530 15:53:47.070773       1 ofSwitch.go:267] Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER
I0530 15:53:47.080502       1 fqdn.go:756] "Received a fragmented DNS response, partially unpacking it" lengthField=5891 actualLength=445
I0530 15:53:47.080532       1 fqdn.go:758] "Unable to unpack the DNS response partially, skipping it" err="dns: buffer size too small"
I0530 15:53:47.082991       1 traceflow_controller.go:188] Shutting down AntreaAgentTraceflowController
I0530 15:53:47.083009       1 agent.go:867] Stopping Antrea agent
I0530 15:53:47.083021       1 controller.go:188] Shutting down ExternalIPPoolController
I0530 15:53:47.083031       1 node_route_controller.go:365] Shutting down AntreaAgentNodeRouteController
I0530 15:53:47.083036       1 requestheader_controller.go:183] Shutting down RequestHeaderAuthRequestController
I0530 15:53:47.083053       1 ip_scheduler.go:241] "Shutting down Egress IP scheduler"
I0530 15:53:47.083023       1 configmap_cafile_content.go:223] "Shutting down controller" name="client-ca::kube-system::extension-apiserver-authentication::client-ca-file"
I0530 15:53:47.083055       1 cluster.go:352] "Shutting down" controllerName="MemberListCluster"
I0530 15:53:47.083163       1 secure_serving.go:255] Stopped listening on [::]:10350
I0530 15:53:47.083058       1 server.go:701] Shutting down CNI server
I0530 15:53:47.083064       1 discoverer.go:105] Stopping ServiceCIDRDiscoverer
I0530 15:53:47.083001       1 status_controller.go:217] Shutting down NetworkPolicy StatusController
I0530 15:53:47.083091       1 object_count_tracker.go:151] "StorageObjectCountTracker pruner is exiting"
I0530 15:53:47.083093       1 channel.go:87] "Stopping SubscribableChannel" name="PodUpdate"
I0530 15:53:47.083010       1 egress_controller.go:330] Shutting down AntreaAgentEgressController
I0530 15:53:47.083105       1 configmap_cafile_content.go:223] "Shutting down controller" name="client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file"
I0530 15:53:47.083104       1 configmap_cafile_content.go:223] "Shutting down controller" name="antrea-ca::kube-system::antrea-ca::ca.crt"
I0530 15:53:47.083119       1 tlsconfig.go:255] "Shutting down DynamicServingCertificateController"
Versions:

Additional context

@sba30 Thanks for reporting the issue.
The error message Received OpenFlow1.5 error: unknown error with type 14, code 1, vendor 0 on message OFPT_EXPERIMENTER in ofnet represents an Error message sent from OVS for type: OFPET_BAD_PROPERTY, code: OFPBPC_BAD_LEN for an openflow15.Type_Experimenter message.
I guess it is related with some issue when decoding PakcetIn2 message with a fragmented DNS packet. Could you help provided the OVS logs?

ovs-vswitchd.log
Logs attached

Can you also share the full antrea-agent log (starting from begining)? Even if antrea-agent receives fragmented DNS packet, it should be running. It seems to be killed by kubelet because of failed liveness probe, likely due to the "ovs" check: https://github.com/antrea-io/antrea/blob/141224ad16772ddc3c86d284228b4aa8137afd56/pkg/agent/apiserver/apiserver.go#L186-L191
The early logs may help us understand why the ovs check is not ready.

Having offline sync with @sba30 , these OVS error logs are printed on the issued setup,
2023-05-30T08:18:39.275Z|00048|connmgr|INFO|br-int<->unix#1: sending OFPBPC_BAD_LEN error reply to NXT_RESUME message
2023-05-30T08:18:39.405Z|00049|connmgr|INFO|br-int<->unix#1: sending OFPBPC_BAD_LEN error reply to NXT_RESUME message
2023-05-30T08:18:39.535Z|00050|connmgr|INFO|br-int<->unix#1: sending OFPBPC_BAD_LEN error reply to NXT_RESUME message
2023-05-30T08:18:39.665Z|00051|connmgr|INFO|br-int<->unix#1: sending OFPBPC_BAD_LEN error reply to NXT_RESUME message
2023-05-30T08:18:39.995Z|00052|ofp_packet|WARN|unknown continuation property type 7
2023-05-30T08:18:40.415Z|00053|ofp_packet|WARN|unknown continuation property type for exp_id 0x2320, exp_type 983032
2023-05-30T08:18:40.996Z|00054|connmgr|INFO|br-int<->unix#1: 486 flow_mods in the 6 s starting 10 s ago (485 adds, 1 deletes)
2023-05-30T08:18:41.045Z|00055|ofp_packet|WARN|unknown continuation property type 0
2023-05-30T08:18:44.978Z|00056|ofp_packet|WARN|unknown continuation property type 7

The errors showed that some issue exists when encoding the OpenFlow resume message (used in packetIn2 mechnism to continue the packet processing pipeline ). After OVS send the OpenFlow error message to antrea-agent, antrea-agent (ofnet) would disconnecct the previous connection from OVS and initiate a new connection. When health check happens at this time, it may think antrea-agent as unhealthy, and then restart the antrea-agent Pod.
Except for the resume message encoding error, I also observed that the flow entry for packet_in TCP DNS response is not installed as expected, the failed flow would send all TCP packets marked with flags "+ack+psh" to antrea-agent, which may indirectly lead to this failure. I use another issue #5077 to track it.


subnet_group_name is always precreated

There are cases where you want to create a new redis instance but attach it to an existing subnet group.  However, this is currently not possible with this implementation.  You should be able to disable creating the subnet group and instead pass it in as a variable.

@estein9825  thank you for testing and submitting the issue.
If you know how to implement it, please submit a PR, we'll review it promptly.


[Question]:  UpSampling1D method

Description
I need the UpSampling1D method for my project, is there this implementation in the tensorflow.net package?
Alternatives
No response

Sorry, there was no implementation before. But I've just implemented it and commit a PR, and in the next version you'll be able to use tf.keras.layers.UpSampling1D directly. ^_^

obrigado. Eu estou fazendo um projeto onde e necessario a implementaçao de um autoencoder, so i need this method or Conv1dTranspose to do this.

thanks. I am doing a project where it is necessary to implement an autoencoder, so i need this method or Conv1dTranspose to do this.


Jinja2 support

Any plan to support jinja2 template system?

Hard to say.
Changing template engines would require rewriting the parts that depend on Django (mainly,  page.py and template_tags.py). However, it'll break existing plugins that rely on Django, so at best we could make this an option.
Providing pluggable template engines (like we have for deployments) might however make sense. Django would be the default, but users would be free to add their own.


error: call to 'sqrt' is ambiguous

I was just testing YOLOv8 with OpenCL using a webcam:
GPU=1 DEBUG=4 python3 examples/yolov8.py webcam n

However, I got OpenCL compile error like this:
<kernel>:103:25: error: call to 'sqrt' is ambiguous
  float cast0 = (float)(sqrt(((half)(1.0f)/(val2.x+(half)(0.001f)))));

Always casting before sqrt may be a solution but not sure.

log.txt (stdout+stderr)
yolov8.py (modified for webcam)

I am having the exact same issue with an unmodified yolov8.py example file on a fresh tinygrad install from the main branch.

what hardware are you running on?

what hardware are you running on?

5900hx + 3080m 16gb + ubuntu 20.04


allParams() returns undefined ID

Sails version: 0.11.4
Node version:7.2.1
Operating system: OSX
Let's say we have AuthController with verify action in it.
When POST /auth/verify with body { code: 10 }
Expected behavior
req.allParams() returns { code : 10 }
Current behavior
req.allParams() returns { code:10, id: undefined }
I know blueprint generates all REST routes with shadows but id shouldn't be there. Am I missing something?
Thanks in advance

Hi @sercanov, I wasn't able to reproduce this with the environment you listed.  Would you mind setting up a repo that reproduces this in a new sails app real quick? I think that'd be the easiest way to see what's going on.
e.g.:
sails new sails-issue-3973
cd sails-issue-3973
# Now make whichever are the simplest/quickest changes which reproduce the issue,
# and when you for sure have the issue isolated, run:
git init
hub create  # or use the GitHub UI to create the repo and `git remote add` it manually
git add .
git commit -am 'Reproduces https://github.com/balderdashy/sails/issues/3973'
git push -u origin master
hub browse # or open the repo in your browser manually
# Then copy the URL of the new repo and paste it as a comment on this issue.
# We'll check it out, and since this way we'll be able to experience the problem
# ourselves, we should have no problem getting to the bottom of it.

Thanks!


Update finalized asm example in Sway Book

The finalized assembly looks a little different now. Also switching to using cargo test instead of forc test as I think forc test will be repurposed for in-Sway testing.

I forgot I changed the mismatched selector revert code to 123. It was annoying me as I tested things that revert(0) was used so much -- I'd have to dig into the bytecode to work out which RVRT was actually triggering.

That's probably a good change. Not sure what value we should select though 😆  - We've started using these code in the standard library: 0xffff_ffff_ffff_0001, 0xffff_ffff_ffff_0002, and so on, so maybe 0xffff_ffff_ffff_0000 is a good fit for the selector revert.


docker.network.list documentation missing

Firstly, great module!!! Starred!!!
docker.network.list()  works, but
I think that documentation is missing from:
https://gabrieldemarmiesse.github.io/python-on-whales/sub-commands/network/
Unless it's somewhere else ...

Thank you for the report. Indeed you are right, it's missing. I can see also that docker.network.inspect() and docker.network.prune() are not in the docs. Looking at the code, it's the only functions where a docstring is missing.
I believe if we add a docstring, they should appear in the docs. A pull request is welcome!

Just FYI I'm really (seriousy) a noob, but I will give it a shot!

This may be due to my noobness, but just FYI I had a couple of errors when trying to
python autogen.py && mkdocs serve

No such file or directory venv/python-on-whales/lib/python3.12/site-packages/img/full.png (fixed by copying it there)
No such file or directory venv/python-on-whales/lib/python3.12/site-packages/img/docker_clients.png (fixed by copying it there)
Need to sudo apt install podman (installed)
Error: python-on-whales/docs/generated_sources isn't an existing directory (just mkdir)
Lots of Warning:  reference to 'docker_client.md' is included in the 'nav' configuration, which is not found in the documentation files. type of warnings
... which probably explains 404s in all the pages
Also: Run tests / Render docs (pull_request) failed

So that's my excuse for not verifying that the added docstrings actually show up in the docs.
(+ my dog ate my code)

No worries, our current workflow to serve the docs locally isn't great at all. This is not very beginner friendly. I'll serve the docs from your pull request locally, with a bit of luck, everything should run fine and we'll be able to merge your pull request :)

Closing this issue as fixed :)


perf(transformer): arrow function transform: reduce stack memory usage

Arrow function transform maintains a stack for blocks which may (or may not) need a var _this = this; statement added to them.
This stack was Vec<Option<BoundIdentifier>> (24 bytes per block). Most blocks won't need a statement added, so most entries are None.
Introduce an abstraction SparseStack. This stores the stack split into 2 arrays. First array is Vec<bool> indicating if a statement needs to be added or not. Only if a statement does need to be added, then its details are pushed to a separate array Vec<BoundIdentifier>.
This means the memory taken up by the stack will be roughly 1 byte per block, instead of 24 bytes per block (assuming very few blocks need statements added).

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5940  👈
#5850
#5933
#5932
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Is SparseStack an alternative for #5049?

Is SparseStack an alternative for #5049?

Yes, I was planning to create a "common" transform which holds a SparseStack, and all these transforms can share it.