Parse animations in GltfLoader

This PR modifies ModelComponents and GltfLoader such that animation data can be loaded into ModelComponents from the glTF.
Question: I have a loadAccessor function in GltfLoader that basically acts as a wrapper for the loadBufferView code. I made this because:

loading the accessor for the inverseBindMatrices in loadSkin() was basically the same as loading the input and output accessors for loadAnimationSampler()
the key difference is what to do with the packedTypedArray in the promise, and the default behavior if the accessor is invalid

I'm not proud of the way I wrote the loadAccessor function, so any feedback is appreciated. I wanted to circumvent writing a whole  GltfAccessorLoader class (which would also require modifying ResourceCache and ResourceCacheKey), while being able to write something reusable.

Thanks for the pull request @j9liu!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

The structure of the PR looks good but I agree that loadAccessor doesn't feel quite right.
According to the glTF spec when accessor.bufferView is undefined it must be initialized with zeros. So I think it's fine if loadAccessor returns a promise to a typed array filled with zeros if the buffer view is undefined. Then the callbacks won't be needed.
To simplify the code further loadAccessor could return an array of the unpacked type (e.g. Number, Cartesian3, Matrix4) instead of a typed array. That way the calling code doesn't have to do the unpacking, instead it can pass the type to loadAccessor to let it do the unpacking.


fix merkel tree compilation error

Pull Request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: #107
What is the new behavior?

Alexandria data structures compile now

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

format por favor

sorry, it's done ✅

😅 I thought I was supposed to run scarb format, I'll resolve this asap


Animations between sibling routes

RactCSSTransitions work when navigating from a Parent Route to a child route, but does not work when navigating between sibling routes. Is there a different method?
Also, in the animation example you should add transitionEnterTimeout and transistionLeaveTimeout.

fixed the warning https://github.com/rackt/react-router/commit/e4a19e8773cafb8fad52d4a7e88b187aea2fdd7e

This is by design because nothing is entering or leaving. You'll have to find another path to animate just changes on received props. Not a bug or feature request so I'm closing this.


Introduce "dry run" option for provision and deploy commands

Azure CLI, and many other CLI tools that allow for cloud resource deployments, have "dry run" mode, that validates the deployment, but stops short of creating actual cloud resources. We should introduce a similar mode for AZD.
In particular, it would be useful for the dry-run mode to expose the final result of Bicep/Terraform build process, including results of parameter substitution and name/unique suffix generation. This will help developers troubleshoot deployment issues.

note: ARM has 'what-if' command that could be used for this.

Related to what @vhvb1989 is starting to take a look at with #141


some issues of ABS

1.Indium Tin Barium Titanium Cuprate is produced in higher yields in ABS than Mixer
2.Molten Ruridit's recipe is gone
Edit:Molten Ruridit itself was gone

ABS?

it's a typo sorry

This is resolved as of d47d87378fdbda1972276c39eab006378634106a, so I am closing this issue.


Only tar.gz format is made with flit build when there is .git?

flit build normally produces both tar.gz and .whl format
but when I use git init to have .git in the project, only tar.gz is made.

That's weird, what do the messages say? Most of my projects have a .git folder and Flit generally builds wheels as well.

The message is a bit different.
Structure

pytest_skip_slow_DIY (directory)

dist (directory)
examples (directory)
LICENSE (file)
pyproject.toml (file)
pytest_skip_slow_module.py (file)

But here this is with .git folder
(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY> git init
Initialized empty Git repository in C:/Users/SJ/Desktop/Programs/Python/PyTest/code/ch15/pytest_skip_slow_DIY/.git/
(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY> flit build
Untracked or deleted files in the source directory. Commit, undo or ignore these files in your VCS.
(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY>
(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY> ls dist

    Directory: C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY\dist

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----          7/6/2024   2:32 AM             79 pytest_skip_slow_module-0.0.5.tar.gz

(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY>

This is when I don't have the git folder
(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY> flit build
Built sdist: dist\pytest_skip_slow_module-0.0.5.tar.gz  I-flit_core.sdist
Copying package file(s) from C:\Users\SJ\AppData\Local\Temp\tmp_9wzr_4r\pytest_skip_slow_module-0.0.5\pytest_skip_slow_module.py  I-flit_core.wheel
Writing metadata files                               I-flit_core.wheel
Writing the record of files                          I-flit_core.wheel
Built wheel: dist\pytest_skip_slow_module-0.0.5-py2.py3-none-any.whl  I-flit_core.wheel
(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY> ls dist

    Directory: C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY\dist

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----          7/6/2024   2:35 AM           5271 pytest_skip_slow_module-0.0.5-py2.py3-none-any.whl
-a----          7/6/2024   2:35 AM           4316 pytest_skip_slow_module-0.0.5.tar.gz

(venv) PS C:\Users\SJ\Desktop\Programs\Python\PyTest\code\ch15\pytest_skip_slow_DIY>

Aha, OK. So it's by design that it's stopping early, as the message indicates:

Untracked or deleted files in the source directory. Commit, undo or ignore these files in your VCS.

It uses git to decide which files to include in the sdist, but if they're neither checked in nor ignored, it doesn't know what to do, so it refuses until you decide on those files. (This is what it does for now, anyway - we're actually moving away from this).
You can override this with the --no-use-vcs option.
There is a bug, however, in that it's creating the .tar.gz file before doing that check. It's actually giving you an empty archive, that's why the length is only 79 bytes. It shouldn't do this if it's refusing to build.

1
ok so flit build --no-use-vcs does work. It creates tar.gz and the .whl. 🙂
2

It (Flit) uses git to decide which files to include in the sdist, but if they're neither checked in nor ignored, it doesn't know what to do, so it refuses (to build) until you decide on those files.

I'm not very knowledgeable at Flit. So I'm assuming "it" means "Flit" and "it refuses" mean "it refuses to build" is what you meant for clarity.
Anyways, so shouldn't adding .gitignore also fix this problem?
Even I add .gitignore so that ignore whatever the files inside the dist folder and do flit build I suffer from the same problem generating only the tar.gz format and not the .whl.
.gitignore
dist
__pycache__

All the files in your project directory (where pyproject.toml is) need to be either ignored or added (git add blah.txt) to git. If git status shows you any 'Untracked files', Flit will give you this error.


edit README after docker being mandatory

Hello here is  a small edition after docker now mandatory (see https://github.com/ligolang/dao-cameligo/commit/f9fd1374f2e80af6cb519ccad22721ad8f8beaae)

@melwyn95 @Laucans

@Laucans can you have a look?

Hello @der-alter,
Starting by thanks for your feedback.
Docker still not mandatory you can use make and override the ligo compiler using following command :
make compile ligo_compiler=<LIGO_COMPILER_COMMAND>
It's also available for protocol or project-root.
But you got a point documentation is not correct and I gonna fix it on every templates than we provide.

Hi! of course, but then = must be replaced by ?=
uniformisation of variable names seems required too PROTOCOL_OPT is capitalized
I close this MR, let you find the standard way !


fix: returns correct mods if double check fails

What
fix: returns correct mods if double check fails

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


Update readme

Add license, in the readme.

Please assign this to me

@codenameakshay @LiquidatorCoder Interested about learning on license, can you assign this to me?

@codenameakshay @LiquidatorCoder Interested about learning on license, can you assign this to me?

The license is already present in the repo, you just need to add it in the readme, i.e. a header License, and then copy the whole license below it, at the end of the readme file.

@codenameakshay @LiquidatorCoder @swai-collins  Completed


DOC: first version of the installation instructions

This is an attempt to fix issue #250 (sorry for the delay). @arobert01 @LucasGandel @codeling @NiklasFauth @acoussat can you review and comment before I merge? This file will replace the first section of the wiki.

Sorry, there was a problem with my commit. I don't know how I did this but it's now in the PR and the file is visible here.

Looks good to me

Haven't tried all details, but looks good to me!
The only thing I could think of that might be added is something regarding adding RTK to the COMPONENTS section of cmake's FindPackage call in an application using RTK (see https://github.com/SimonRit/RTK/issues/250#issuecomment-514516784)

Looks good to me!
+1 for adding a section about find_package as suggested by codeling

Looks good to me! Nice that you list and explain the RTK-specific CMake options, I have learned something new along the way.

Thanks for your feedbacks and sorry for the delay. I have added a GettingStarted.md file and I have added a link to the line containing find_package of the FirstReconstruction CMakeLists.txt. It's now merged.


Local Storage

Hello,
First off awesome application / palette, if you send me a link I’ll buy you a coffee.
I am trying to inject something into the local storage, some user session data, so that the site auto logins.
Example
driver.executeScript(function () {
localStorage.setItem("Id", '{"_expired":0,"_value":"133"}');
})
Would the run script node work?
Would you have any ideas how to go about this?
Thanks

Hi @franco-101 ,
Thanks!
Sorry for the late reply. It should work as it is executed in the context of the web page.
Were you able to figure out your issue?
Best regards,

@simonradier
Everything is working thanks!


chore: remove dependency on deprecated golang.org/x/crypto/ssh/terminal

From pkg.go.dev:

Deprecated: this package moved to golang.org/x/term.

Thanks!


bug: When opening the sidebar on the website, the main content area unexpectedly shrinks

Describe the bug
When opening the sidebar on the website, the main content area unexpectedly shrinks, causing a disruption in the layout and usability of the page.
To Reproduce
Steps to reproduce the behavior:
1.Navigate to the page where the sidebar is present.
2.Open the sidebar by clicking on the corresponding toggle button or action.
3.Observe that the main content area reduces in size or is compressed.
4.Close the sidebar to return to the normal layout.
Expected behavior
When opening the sidebar, the main content area should remain unaffected in size and layout. The sidebar should overlay on top of the content without causing any resizing or compression of the main content area.
Screenshots or GIFs
what it looks like:

how it should look:

hey @Raj-Thombare I think just adding
max-sm:fixed max-sm:z-10 to sidebar.tsx at line 162 will do this. It works well on my local. can I be assigned this issue

hey @harpreetsinghsandhu021 and @Raj-Thombare , This issue has already been reported here: #607 and maybe fixed by: #612

ok then im closing it


Idempotent flag ignored for retries

Hello,
I was testing goCQL behavior with request shedding enabled.  So I set
max_concurrent_requests_per_shard: 10
I was testing vanilla insert with value clause.
Initially, requestRetryPolicy was disabled, and I received shedding errors.
I then enabled requestRetryPolicy with ExponentialBackoffRetryPolicy.
    requestRetryPolicy := &gocql.ExponentialBackoffRetryPolicy{
		Min:        100 * time.Millisecond,  // Minimum retry delay
        //Min:        time.Second,  // Minimum retry delay
        Max:        10 * time.Second, // Maximum retry delay
        NumRetries: 10,           // Maximum number of retries
    }

As expected, queries were retried.  I still observed shedding in monitoring, but the driver retried the requests with exponential backoff.
I then tested with idempotent set to false.
func insertQuery(session *gocql.Session, ctx context.Context, firstName, lastName, address, pictureLocation string, increment int, logger *zap.Logger) bool {
	//sp := &gocql.SimpleSpeculativeExecution{NumAttempts: 2, TimeoutDelay: 1 * time.Millisecond}
	query := session.Query("INSERT INTO mutant_data (first_name,last_name,address,picture_location) VALUES (?,?,?,?)", firstName, lastName, address, pictureLocation)
	//query.SetSpeculativeExecutionPolicy(sp)
	query.Idempotent(false)
	if err := query.Exec(); err != nil {
		logger.Error("insert mutant_data "+firstName+" "+lastName, zap.Error(err))
	}
}

Problem: Even with Idemotent false, which should block retry - the queries were still retried with exponential backoff policy.  It also looks like it might be in general for all retries (speculative and timeout):
https://github.com/apache/cassandra-gocql-driver/pull/1809/commits/92b4056c1a125e7094b397cfab8bd8ac8d48f26e
All retry policies should honor the idempotent flag.

I don't have permissions to scylla-go-driver do I cannot transfer the issue

Done!

Fixed by https://github.com/scylladb/gocql/pull/376


validation summary All throws NotSupportedException: The invoked member is not supported in a dynamic assembly.

When use

 and no validation error exists it throws exception below.
When I use

 or some validation errors occurs it works, but I in this case I do not see all errors in summary.
System.NotSupportedException: The invoked member is not supported in a dynamic assembly.
   at System.Reflection.Emit.InternalAssemblyBuilder.GetManifestResourceNames()
   at System.Resources.ManifestBasedResourceGroveler.HasNeutralResources(CultureInfo culture, String defaultResName)
   at System.Resources.ResourceManager.CommonAssemblyInit()
   at System.Resources.ResourceManager..ctor(String baseName, Assembly assembly)
   at Microsoft.Extensions.Localization.ResourceManagerStringLocalizerFactory.CreateResourceManagerStringLocalizer(Assembly assembly, String baseName)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.AspNetCore.Mvc.DataAnnotations.Internal.DataAnnotationsMetadataProvider.CreateDisplayMetadata(DisplayMetadataProviderContext context)
   at Microsoft.AspNetCore.Mvc.Internal.DefaultCompositeMetadataDetailsProvider.CreateDisplayMetadata(DisplayMetadataProviderContext context)
   at Microsoft.AspNetCore.Mvc.ModelBinding.Metadata.DefaultModelMetadata.get_DisplayMetadata()
   at Microsoft.AspNetCore.Mvc.ModelBinding.Metadata.DefaultModelMetadata.get_Order()
   at System.Linq.EnumerableSorter`2.ComputeKeys(TElement[] elements, Int32 count)
   at System.Linq.EnumerableSorter`1.Sort(TElement[] elements, Int32 count)
   at System.Linq.OrderedEnumerable`1.<GetEnumerator>d__1.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Microsoft.AspNetCore.Mvc.ModelBinding.Metadata.DefaultModelMetadata.get_Properties()
   at Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ValidationHelpers.Visit(ModelStateDictionary dictionary, ModelStateEntry modelStateEntry, ModelMetadata metadata, List`1 orderedModelStateEntries)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ValidationHelpers.GetModelStateList(ViewDataDictionary viewData, Boolean excludePropertyErrors)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.DefaultHtmlGenerator.GenerateValidationSummary(ViewContext viewContext, Boolean excludePropertyErrors, String message, String headerTag, Object htmlAttributes)
   at Microsoft.AspNetCore.Mvc.TagHelpers.ValidationSummaryTagHelper.Process(TagHelperContext context, TagHelperOutput output)
   at Microsoft.AspNetCore.Razor.TagHelpers.TagHelper.ProcessAsync(TagHelperContext context, TagHelperOutput output)
   at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperRunner.<RunAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at AspNetCore._Views_SAPBetriebsmittelanforderung_Edit_cshtml.<ExecuteAsync>d__48.MoveNext() in /Views/SAPBetriebsmittelanforderung/Edit.cshtml:line 24
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.<RenderPageAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.<RenderAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.<ExecuteAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.ViewResult.<ExecuteResultAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeResultAsync>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResultFilterAsync>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResultExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResourceFilter>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResourceExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Web.BrowserLink.Runtime.BrowserLinkMiddleware.<ExecuteWithFilter>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.<Invoke>d__7.MoveNext()

@pranavkm do we need this open while it moved to localization repo?

@hishamco not sure if there's more to investigate here vis-a-vis DataAnnotationsMetadataProvider.

@pytlus93 - is there anything exotic here about your model type?

Closing because there is not enough information to reproduce this problem.


Update Dark Mode documentation for configuring strategy in tailwind.config.js

Describe the bug
I ran into some problems using the 'class' strategy for DarkMode with tailwind.config.js, being that its very inconsistent and sometimes toggle certain elements and sometimes not. That was because as of tailwind 3.4.1, the 'class' strategy has been replaced with 'selector'.
the documentation should add a note on top of of the strategy configuration which mentions this, something like what I wrote below:
The selector strategy replaced the class strategy in Tailwind CSS v3.4.1.
// tailwind.config.cjs
const config = {
  darkMode: 'class' //'selector'
  // ...
};

Reproduction
...
Flowbite version and System Info
flowbite-svelte: 0.45.0

Thanks. Please use the latest version.


App name on navbar should be margin-left not right

I'm not sure why margin has been set to right for this line, since every time I have to change it to ml-6 to show it properly on small screens.

Happy to accept a PR with this change.

@michaeldyrynda seems that there was no problem with the previews mr-6, but since my template was for both LTR/RTL directions, I thought that it should be ml-6 bor both dirs.
So expect my apologies and roll-back, please.


Add Collapse, Accordion and Avatar components

Codecov Report

Merging #2 into master will increase coverage by 0.24%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
+ Coverage   70.94%   71.18%   +0.24%
==========================================
  Files          10       10
  Lines         117      118       +1
  Branches       17       17
==========================================
+ Hits           83       84       +1
  Misses         26       26
  Partials        8        8

Impacted Files
Coverage Δ

src/Card/Card.js
100% <100%> (ø)
:arrow_up:

src/theme.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Auth Without Javascript Client

Hi
I want to get refresh token and since it isn't possible to do with Javascript Client Library, how can I do auth without it?
Even manually doing it is fine, I only need it once anyway

You could still use the JS client and request an offline code, refer to the documentation here: https://developers.google.com/identity/sign-in/web/server-side-flow. Would that work?

Well it requires server-side code aswell, I needed to do it client-side only

By design, it is not possible to get a refresh token without any server side code.
Could you explain a bit more your use case? Why isn't Google Sign-In JS client library good for it? It handles refreshing token automatically.

Is the JS client library refreshing the token automatically a new feature? When I implement gapi.auth2 last year the auth token invalidated itself every hour and never refreshed.

This is not a new feature. How do you get the token? Once a user is signed in, gapi.auth2 automatically refreshes the token. You should be able to get a valid one at all time, by calling GoogleUser.getAuthResponse(true). Have you tried recently?

Nope. Maybe I just didn't see that in the docs when I started writing the app last year.
I worked around it by getting a refresh token for the server and then having my server get a new auth token at ~50 minute intervals. It works well...but I'll look into changing that to use the method you mentioned above. Thanks.

@Jeckstart could you expand a bit more on your use case?

@Jeckstart please reopen if you still need guidance on this issue. Closing as the thread is inactive.


FIX fxi array nested struct literal

Proposed changes
link: https://github.com/apache/doris/pull/26270
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Assigned default value to simulatorFriendly in README

Thx for the great lib! As I copy pasted your sample code I noticed this issue in README :)


Add lost x el rap del pepe ete sech by crim3s

Song Name
lost x el rap del pepe ete sech
Artist Name
crim3s
Source
Direct File download
Youtube Link
qFHRLsoTVRA
Direct File Link
https://www.mediafire.com/file/laatifg6brd24a7/945695.mp3/file
Song ID
945695
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 105623347

reject
wrong offset


Readme implementation fails credential verification

I tried implementing issuing and verification of a Verifiable Credential as described in this readme with a simple typescript application.
I can succesfully create and sing a VC. If I copy the generated VC to https://api.did.actor/credentials/verify I get a succesful verification. However, if I try to verify the credential using verifiable.credential.verify, I get the following error
{
  "verified": false,
  "verifications": [
    {
      "status": "good",
      "title": "Proof",
      "description": "did:key:z6MkokrsVo8DbGDsnMAjnoHhJotMbDZiHfvxM4j65d8prXUr#z6MkokrsVo8DbGDsnMAjnoHhJotMbDZiHfvxM4j65d8prXUr"
    },
    {
      "status": "good",
      "title": "Activation",
      "description": "This credential activated 13 years ago"
    }
  ],
  "error": [
    "This credential contains invalid JSON-LD allowing it to be mutable.",
    {
      "proofResult": false
    },
    {
      "name": "VerificationError",
      "errors": [
        {
          "name": "jsonld.SyntaxError",
          "details": {
            "code": "invalid local context",
            "context": [
              null
            ]
          },
          "message": "Invalid JSON-LD syntax; @context must be an object.",
          "stack": "jsonld.SyntaxError: Invalid JSON-LD syntax; @context must be an object.\n    at _throwInvalidLocalContext ([REDACTED PROJECT ROOT]\\node_modules\\jsonld\\lib\\ContextResolver.js:212:9)\n    at ContextResolver.resolve ([REDACTED PROJECT ROOT]\\node_modules\\jsonld\\lib\\ContextResolver.js:68:9)\n    at api.process ([REDACTED PROJECT ROOT]\\node_modules\\jsonld\\lib\\context.js:65:50)\n    at api.expand ([REDACTED PROJECT ROOT]\\node_modules\\jsonld\\lib\\expand.js:211:23)\n    at jsonld.expand ([REDACTED PROJECT ROOT]\\node_modules\\jsonld\\lib\\jsonld.js:325:24)\n    at jsonld.frame ([REDACTED PROJECT ROOT]\\node_modules\\jsonld\\lib\\jsonld.js:474:38)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
        }
      ]
    }
  ]
}

I don't understand what this error means. I implemented my own simple documentLoader following the examples here (later I will need to support custom did methods), but I log all resolutions and they all appear correct. Can anyone help me? Am I doing smething wrong?
This is my app.ts
import {
  JsonWebKey,
  JsonWebSignature,
  JsonWebKey2020,
} from "@transmute/json-web-signature";
import { verifiable } from<EMAIL_ADDRESS>import * as didKey from<EMAIL_ADDRESS>import axios from 'axios';
import { documentLoaderFactory, Url } from "@transmute/jsonld-document-loader";

async function main() {

  const aDocumentLoader = documentLoaderFactory.build({
    // resolution function: async ( iri: Url) : didDocument as JSON
    ["did:key"]: async (iri: Url) => {
      console.log("resolving " + iri.toString() + " as did:key");
      const out = await didKey.key.resolve(iri);
      console.log(JSON.stringify(out, null, "  "));
      return out;
    },
    ["https:"]: async (iri: Url) => {
      console.log("resolving " + iri.toString() + " as https");
      const { data } = await axios.get(iri);
      console.log(JSON.stringify(data, null, "  "));
      return data;
    }
  })

  const key = {
    id: "did:key:z6MkokrsVo8DbGDsnMAjnoHhJotMbDZiHfvxM4j65d8prXUr#z6MkokrsVo8DbGDsnMAjnoHhJotMbDZiHfvxM4j65d8prXUr",
    type: "JsonWebKey2020",
    controller: "did:key:z6MkokrsVo8DbGDsnMAjnoHhJotMbDZiHfvxM4j65d8prXUr",
    publicKeyJwk: {
      kty: "OKP",
      crv: "Ed25519",
      x: "ijtvFnowiumYMcYVbaz6p64Oz6bXwe2V_9IlCgDR_38",
    },
    privateKeyJwk: {
      kty: "OKP",
      crv: "Ed25519",
      x: "ijtvFnowiumYMcYVbaz6p64Oz6bXwe2V_9IlCgDR_38",
      d: "ZrHpIW1JBb-sK2-wzKV0mQjbxpnxjUCu151QZ9_F_Vs",
    },
  };

  const credential = {
    "@context": [
      "https://www.w3.org/2018/credentials/v1",
      "https://w3id.org/security/suites/jws-2020/v1",
    ],
    id: "http://example.edu/credentials/3732",
    type: ["VerifiableCredential"],
    issuer: {
      id: "did:key:z6MkokrsVo8DbGDsnMAjnoHhJotMbDZiHfvxM4j65d8prXUr",
    },
    issuanceDate: "2010-01-01T19:23:24Z",
    credentialSubject: {
      id: "did:example:ebfeb1f712ebc6f1c276e12ec21",
    },
  };

  const suite =  new JsonWebSignature({
    key: await JsonWebKey.from(key as JsonWebKey2020),
  })
  const createOutput = await verifiable.credential.create({
    credential,
    format: ["vc", "vc-jwt"],
    documentLoader: aDocumentLoader,
    suite: suite,
  });

  const vc  = createOutput['items'][0];
  const jwt = createOutput['items'][1];

  console.log("VC creation complete. VC type: " + typeof vc);
  console.log(JSON.stringify(vc, null, "  "));

   const verificationOutcome = await verifiable.credential.verify({
    credential:vc  ,
    format: ["vc" /*, "vc-jwt"*/],
    documentLoader: aDocumentLoader,
    suite:  [new JsonWebSignature()],
  });

  console.log(JSON.stringify(verificationOutcome, null, "  "));

}

main();

Is this the right place to ask this question? If no, where can I ask?
Thank you for your time

Thanks for this but report, see similar comment here:
https://github.com/transmute-industries/verifiable-data/issues/238#issuecomment-1613891673
We don't plan to support JsonWebSignature2020 now that v2 data model supports JWTs better.


WIP: Clarify icon meaning (#304)

Before working through the rest of th to resolve #304, does this type modification work? It adds a human readable message about the status in addition to color and icon. For some pages, the strategy may need to differ.

Slick! :)

This was merged prematurely, note that it is still a WIP as there are other pages where this clarification is necessary. I've reopened #304 to reflect this.

Thanks! I didn't notice the WIP.

@wasade This functionality is entirely awesome!  I will be thrilled to see it in the software!
I therefore hesitate to point out that the (legit) problem it is fixing is not the one I was trying to capture in the issue #304 write-up :)  The issue I was recording there was actually much simpler ... a user thought the "x" in a red circle that appears next to a plate in a list of selected plates (in compression page, extraction page, library prep pages, etc--see screenshot below from compression page as an example) was an error message indicating they had done something wrong, whereas in fact it is just a "remove" button to show that you can remove the plate from the selected list  :( .    Possibly all that misunderstanding requires is a tool tip or something.

I'll add this additional info to #304 to augment its clearly inadequate description :)

Thanks! I was working toward that to be honest :) My initial attempt was to explore different glyphicons that were friendlier but didn't see any. I then tried to figure out if and how to place text immediately next to the button to provide clarity but was unable to make that work (possibly or likely due to limited HTML/JS experience). A tooltip is certainly a great idea, and seems like it may be a relatively "easy" thing to add in!

@wasade I had another thought: in addition to a tooltip, maybe another help would be simply to change the color of the little X circle icon for removing the plates.  Interface convention has trained users that red usually means "error" ... maybe the X icon could be black or gray?  You know, the way it is in most interfaces where it offers low-danger functionality like "shut this box" ...

:+1:


move generator/bng.py content into bng.py

Is removing pysb.generator still a goal? This would be fairly straightforward to do.


Forever repeating Supabase error 100M tokens wasted

Describe the bug
This error keeps coming up:
Supabase API error, 400, Failed to run sql query: ERROR:  23505: duplicate key value violates unique constraint "schema_migrations_pkey"
DETAIL:  Key (version)=(0018) already exists.
I've ran a repeating fix action for almost 100M worth of credits.  This is not working, i've tried deleting all databases and restarting but that did not fix anything.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-untda6wg
Validations

[X] Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce
Unsure how to reproduce below is the error message:
Supabase API error, 400, Failed to run sql query: ERROR:  23505: duplicate key value violates unique constraint "schema_migrations_pkey"
DETAIL:  Key (version)=(0018) already exists.
Expected behavior
I expect the supabase record to be repaired.
Screen Recording / Screenshot
Forever repeating issue:

Platform

OS: [e.g. macOS, Windows,]
Browser: [e.g. Brave]
Version: Supabase

Additional context
No response

Same issue on my project. It seems like the migration files don't get properly numbered since somehow bolt can create more than 6 migration files at once but idk tbh.

Same. Spent 15M tokens and still an issue. Hope they fix this asap so I can deploy a fully functional web app. Lot's of bugs right now.


feat(blueprint): add blueprint for generating interfaces

Fixes #729

Need more e2e tests.

@hansl tests have been added, and rebased upon latest master.


Can't use variable when schema define something as boolean

Sanity check

[X] I certify that the redhat.ansible extension is in use and the language of the document in this bug report shows up as Ansible

Summary
Describe the bug
When something is define as boolean in the schema, like ignore_errors when the value is set by a variable, vscode show an error telling Incorrect type. Expected "boolean".yaml-schema: BeremothTaskModel, even with the filter bool to force the type of the variable.
To Reproduce
Create a task like:

name: "Demo error"
fail:
msg: fail except in check mode
ignore_errors: "{{ ansible_check_mode }}"

Expected behavior
If I specify an ansible expression, I'm pretty sure you guys cannot figure out what type it will return. In that case, I take on responsibility and you guys shouldn't sow an error. Especially not for variables like ansible_check_mode which are universally used at especially this location.
Platform:
Mac latest versions of everything, os, vscode, plugin. Sorry, I don't have access to a linux box.
Extension version
v0.7.1
VS Code version
Name: Ansible ID: redhat.ansible Beschreibung: Ansible language support Version: 0.7.1 Herausgeber: Red Hat Link zum Visual Studio Marketplace: https://marketplace.visualstudio.com/items?itemName=redhat.ansible
Ansible Version
ansible [core 2.11.6]
  config file = None
  configured module search path = ['/Users/dwt/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/dwt/.virtualenvs/sntl-provisioning/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/dwt/.ansible/collections:/usr/share/ansible/collections
  executable location = /Users/dwt/.virtualenvs/sntl-provisioning/bin/ansible
  python version = 3.9.10 (main, Jan 18 2022, 08:19:17) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
  jinja version = 3.0.3
  libyaml = True

OS / Environment
% uname -a
Darwin nathan.fritz.box 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64 x86_64
% ansible-lint --version
ansible-lint 5.3.2 using ansible 2.11.6
FATAL: Ansible CLI (2.11.6) and python module (2.12.1) versions do not match. This indicates a broken execution environment.
Relevant log output
There is no such server.

This looks very much like #125 - but is still present.


WFLY-19668 Upgrade Infinispan to 14.0.31.Final.

https://issues.redhat.com/browse/WFLY-19668
Supersedes https://github.com/wildfly/wildfly/pull/18148
containing additional rxjava upgrade.

Thanks @pferraro


badge test rename

List of related issues or pull requests
Refs: #295
Describe the changes made in this pull request
Updated the repository names and name of paths used for live testing the cli, after

https://github.com/fair-software/badge-test changed its name to https://github.com/fair-software/howfairis-livetest and
https://githlab.com/jspaaks/badge-test changed its name to https://gitlab.com/jspaaks/howfairis-livetest

Also set the sleep duration to 0 for gitlab platfaorm, API rate limit there is plenty high
Instructions to review the pull request
git clone <this repo>
git checkout <this branch>
cd howfairis
python3 -m venv venv3
source venv3/bin/activate
pip3 install --editable --no-cache-dir .[dev]
bash clitests/script.sh

Github action status for this branch

Thanks!


tN card Editing: null column is being added when Occurrence Notes is edited after clearing the previous text completely

Open GE app with org and language selection.
On the tN card, Remove the text from OccurrenceNote and save the card.
On the same verse, add a new text or paste the old text.
OnBlur you can see that a null column is added with the pasted/new text while OccurrenceNote remains blank and Save button does not get enabled.

Looks good in the latest build v1.0.0 build 484cda1. Not seeing the Null column when Occurrence Note is edited.


fix(container): recreate container with multiple networks

Now Portainer will create a container with the first network from the list(if there is any) and then add other networks after a container creation. I was thinking to add this step before container started inside of containerService but I didn't want to mix services together.
Please let me know what do you think!
Fixes #1849

No worries, I'm glad that you got time to take a look at it. You are right about the message, I've removed it.

Thanks @G07cha :+1:


Increase the test coverage rate

Today, SkyWalking's tests are mostly around integration tests, which are benifit for end users. Now we hope through this, people from community could help on Unit Tests.
JUnit and Mockito are provided. This is a good start for everyone wants to contribute codes. When you submit test cases PR, please ref to this issue.

Also, in this kind of pull request, we don't limit how many test cases you provide. Even one new test case, which could effectively test one more line, it will be acceptable. Just try your best to make tests more sense.

Where can I find the code coverage report?

The coverage is here, https://coveralls.io/github/apache/skywalking

Update here, we are only just increasing the test case coverage, we are doing more.

[x] @kezhenxu94 set up the Jenkins of ASF for power test env.
[ ] @ascrutae lead the agent test in Jenkins jobs of every PR when necessary
[ ] @kezhenxu94 lead the e2e test, make agent/backend integration test done in every PR.

We have e2e tests fro single node w/ H2 and cluster mode w/ ES. We are trying to build more. Including MySQL storage tests, alarm tests, and aggregation accuracy tests.

After #3561, we have 30%+ coverage now.

@ascrutae lead the agent test in Jenkins jobs of every PR when necessary
This task is lead by @dmsolr on #3528. Ownership replaced.

Agent autotest framework has been provided, and 300+ test cases have been added. Seems working well. Just working for @dmsolr to provide the official documents, rather than guide users to do that one by one.


update amhswagger and add folder structure

ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

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

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

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

Change to data plane APIs
Adding new properties
All removals

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

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.

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

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

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@athulvijayanmsft please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

Please address or respond to feedback from the ARM API reviewer. When you are ready to continue the ARM API review, please remove the ARMChangesRequested label. This will notify the reviewer to have another look. If the feedback provided needs further discussion, please use this Teams channel to post your questions - https://aka.ms/azsdk/support/specreview-channel. Please indicate that this is an ARM-related question in the title of your post by including "[ARM Query]" in the title.

Please address the breaking changes and once you have either fixed the PR or gotten a breaking change approval, you can remove the ARMCHangesRequested label from the PR to continue the review

Please check and fix errors: https://github.com/Azure/azure-rest-api-specs/pull/24162/checks?check_run_id=16066130798

Please check and fix errors: https://github.com/Azure/azure-rest-api-specs/pull/24162/checks?check_run_id=16066130798

Can you continue review the rest while I fix the prettier checks? as we are reaching deadline for completion.

Please address or respond to feedback from the ARM API reviewer. When you are ready to continue the ARM API review, please remove the ARMChangesRequested label. This will notify the reviewer to have another look. If the feedback provided needs further discussion, please use this Teams channel to post your questions - aka.ms/azsdk/support/specreview-channel. Please include [ARM Query] in the title of your question to indicate that it is ARM-related.

@rkmanda
fixed prettier errors and prettier check is passing locally for all the files; but the PR check still fails. Please unblock here.
Please queue this for further review

Please check and fix errors: https://github.com/Azure/azure-rest-api-specs/pull/24162/checks?check_run_id=16066130798

Resolved and checks are passing now.

      "nextLinkName": null

Pagination needs to be supported for the list calls. nextLinkName cannot be null

Refers to: specification/migrate/resource-manager/Microsoft.Migrate/MigrateProjects/stable/2023-01-01/hubmigrate.json:224 in 20fefa5. [](commit_id = 20fefa52c90f4a6e9791b2d5934dc071122e46ce, deletion_comment = False)

/pr RequestMerge

@athulvijayanmsft - Your PR needs to pass checks and address the SDK breaking change labels before merge. Add the MergeRequested label back after addressing those items. If you get stuck, you can ask for help in the API Spec Review Teams channel: https://teams.microsoft.com/l/channel/19%3A0351f5f9404446e4b4fd4eaf2c27448d%40thread.skype/API%2520Spec%2520Review?groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47.

please resolve conflict first

Hi @athulvijayanmsft, please update default tag.

/azp run

Hi @athulvijayanmsft, please update default tag.

Hi @athulvijayanmsft, why revert default tag? If so, GO-SDK-CI cannot capture new changes.

/azp run

your pr has duplicate operations:
azure-rest-api-specs/specification/migrate/resource-manager/Microsoft.Migrate/AssessmentProjects/stable/2019-10-01/migrate.json at f7ee5557ca7cd99ade16373216e81e28e2d3237a · Azure/azure-rest-api-specs (github.com)
and
azure-rest-api-specs/specification/migrate/resource-manager/Microsoft.Migrate/MigrateProjects/stable/2023-01-01/hubmigrate.json at f7ee5557ca7cd99ade16373216e81e28e2d3237a · Azure/azure-rest-api-specs (github.com)
Is the result of calling these two the same?

your pr has duplicate operations: azure-rest-api-specs/specification/migrate/resource-manager/Microsoft.Migrate/AssessmentProjects/stable/2019-10-01/migrate.json at f7ee5557ca7cd99ade16373216e81e28e2d3237a · Azure/azure-rest-api-specs (github.com) and azure-rest-api-specs/specification/migrate/resource-manager/Microsoft.Migrate/MigrateProjects/stable/2023-01-01/hubmigrate.json at f7ee5557ca7cd99ade16373216e81e28e2d3237a · Azure/azure-rest-api-specs (github.com)
Is the result of calling these two the same?

Hi @kazrael2119, The first one is not part of the PR. Please check the files changed tab of the PR.
They are flagged just because it was added in readme default tag.

@athulvijayanmsft the duplicate operation will make sdk generation fail, so can you confirm whether the result of calling these two the same? If they are the same, we should be able to avoid this duplicate by adding directive

@athulvijayanmsft the duplicate operation will make sdk generation fail, so can you confirm whether the result of calling these two the same? If they are the same, we should be able to avoid this duplicate by adding directive

Hi @kazrael2119, the said files under AssessmentProjects (The first link) are taken up in another PR where the local duplicate definitions are replaced by common-types. PR for the same https://github.com/Azure/azure-rest-api-specs/pull/25417
In the current PR, it is already referencing the common-types as per guidelines.
So, when the other PR is merged, there will not be any duplicates.
The scope of this PR is only for MigrateProjects, as AssessmentProjects is a different RP and PR for same is under review.

Hi @kazrael2119 , can you approve the sdk/PR as there are no real breaking changes here?

/azp run

I think it's best to review your pr after https://github.com/Azure/azure-rest-api-specs/pull/25417 is merged into main and your pr is merged into main branch. After this, sdk-ci-check in this pr may not have duplicate operation and contains your change

@athulvijayanmsft , is this a new service? I found that hubmigrate.json is totally different with migrate.json. Can you change the default tag to the latest one so that the SDK package can be generated in this PR for review?

Hi @raych1,
This is for a different resourcetype named migrateProjects under Azure.Migrate, while the existing migrate.json is for different resourcetype assessmentProjects. Currently SDK breaking changes-for-js are flagged as the types under existing assessmentProjects are not using common-types which is taken care in https://github.com/Azure/azure-rest-api-specs/pull/25417 as a new version and the existing default tag will be deprecated. We request you to approve the changes in this PR and we will take responsibility for any fixes if required during sdk generation in separate PR.

@athulvijayanmsft , as they are different resource types and the new swagger file doesn't include the previous resource types, the sdk package name shouldn't be the same one as previous package.

@athulvijayanmsft , as they are different resource types and the new swagger file doesn't include the previous resource types, the sdk package name shouldn't be the same one as previous package.

Hi @raych1,
The package names are different, the old default tag package was package-migrate-2019-10 which contained assessmentProjects resourcetype.
The current PR package is tag: package-hubmigrate-2023-01 which has different resourcetype.
Keeping either/both of the package names as the default tag causes checks failure as the resourcetypes and related definitions are different. Also in the current PR we are using common-types for few definitions which was local definitions in older resourcetype; which causes duplicate definition flagging.

@athulvijayanmsft , as they are different resource types and the new swagger file doesn't include the previous resource types, the sdk package name shouldn't be the same one as previous package.

Hi @raych1, The package names are different, the old default tag package was package-migrate-2019-10 which contained assessmentProjects resourcetype.
The current PR package is tag: package-hubmigrate-2023-01 which has different resourcetype.
Keeping either/both of the package names as the default tag causes checks failure as the resourcetypes and related definitions are different. Also in the current PR we are using common-types for few definitions which was local definitions in older resourcetype; which causes duplicate definition flagging.

Hi @raych1 / @kazrael2119, as the breaking change tests are failing just due to duplicate entries in an older tag which will be deprecated and since the current package follows recommended common-types, please approve the sdk breaking change and the PR?

approve because of the 2019-10-01 version is going to be deprecated according to service team.

approve because of the 2019-10-01 version is going to be deprecated according to service team.

Thanks @kazrael2119. Can you approve the PR review and add MergeRequested tag?

Hi @kazrael2119, can you approve the PR and add merge requested label?

Hi @kazrael2119, can you approve the PR and add merge requested label?

I‘m just responsible for reviewing JS sdk breaking

/pr RequestMerge


Path isn’t correct (tested on macOS)

I get ERROR: Could not find minecraft install at /Users/cyberflame/Downloads/patchypatchy/L4J-Vuln-Patch/build/libs/~/Library/Application Support/minecraft??? when trying to run the applet.
My understanding is that the applet is treating the path returned from the function(?) as a relative path, though I have limited experience with Kotlin so I’m unsure

I've modified the code a bit can you let me know if its working now? Im not too sure I cannot test on operating systems that arent windows

Yep that did it! I didn’t understand the reason it wasn’t working myself honestly XD


Request: Better error handling or more granularity in auth status

In my app, I'm trying to show a fatal error message when the OAuth server is down. I can't seem to find a way to do this. The middleware logs the error in the console, but I can't seem to catch it. Maybe consider adding an error property to the state or dispatch an error action of some kind?
I would think that the user property being null and isLoadingUser being false would mean that something has gone wrong, but there are brief moments when that state exists but nothing is wrong.
Maybe isLoadingUser should initially be true and only go to false once the user has been found or an error has occurred? Then user == null && isLoadingUser == false would mean that something is wrong.
Am I totally off base here? Do I need to just write my own method to ping the OAuth server and make sure it's accessible?

I don't quite follow you here. It is perfectly fine for the user to be null and isLoadingUser to be false. This just says that no user is currently logged in and doesn't in itself suggest that something has gone wrong. When the auth server is down, redirection on a login attempt would fail visibly, as in you get an error in the browser during redirection. Since the auth server is completely separated from the app itself, it is hard to check for this until you run into it,
You could implement something yourself by manually pinging the auth server before redirection occurs to dispatch some kind of error into your reducer when it returns 404 or 500. However I don't think that this is a requirement for this library.

I get what you're saying, my issue probably is more due to my unique specs than any drawbacks with this library.
In my app, I don't have a login screen. My app is being integrated into another code-base and the login is done in the other code-base. So when you enter the home page of my app, I dispatch a random action right away to get the middleware started. When everything is working, it'll hit the OAuth server and redirect to the callback page, which then redirects back to the previous page. But when my OAuth server is down, it just sits on the homepage of my app with actions that try and ultimately fail to make requests to my API. The only indication I have that anything has gone wrong (other than my API methods failing) is an error in the console saying that the connection to my OAuth server was rejected.
But I suppose I can handle this by either writing a method to ping the server or just wait for my API call to fail and check the status code.
Thanks for your input!

No problem. I'll close this for now.


Use WallTimer to always publish pose and submaps.

This makes the publishing independent from the inflow of sensor data and
is more in line with how the ROS world works.
Fixes #44.

LGTM

LGTM

This actually doesn't work correctly for all use cases. Currently, the transform is repeatedly published, but always with the last pose estimate timestamp. If pose estimates are internally generated at low rate (such as when aggregating spinning LIDAR data and matching only every few seconds or so), this means that the fixed rate publisher republishes the exact same tf data over and over, but as the timestamp does not progress, all system components waiting for tf connectivity stall until the SLAM pose estimate (and the timestamp alongside it) is updated. I'll open a PR with a fix for discussion.


Deploy to Salesforce button not working for sandbox

Expected Behavior
Deploy to Salesforce button should deploy code to sandbox
Actual Behavior
Deploy to Salesforce button doesn't deploy code to sandbox

Steps to Reproduce the Problem

Click Deploy to Salesforce
Specify branch as master
Error received

Specifications

Version:
Platform:

Thanks for bringing this to my attention.
I think this is an issue with the Deploy to Salesforce Heroku app - https://github.com/afawcett/githubsfdeploy.


Clean charts

@Kelvin-M Yes, the commit 18697fb was functioning but the latest isn't, I'm going to re-test them once Guillaume pushes its latest fix

It should be ok


Suggested Enhancement
Show:

How many people are in ICU because of COVID-19
How many people are in ICU in general
How many free % of ICU capacity are available

Expected Benefits
Users are misinterpreting the number of people on ICU because of COVID-19. They think that these % are all people who are in ICU & forget that there are also non-COVID patients in ICU.

Internal Tracking ID: EXPOSUREAPP-10983

Internal Tracking ID: EXPOSUREAPP-10983

As the CWA project went into ramp-down mode, I don't expect this feature to be implemented. I'm therefore closing this issue.


Refactor Status to avoid large stack size in happy path

Follow the implementation of Status in RocksDB, google absl, doris and more, we refactor the Status to make it just a pointer (8 instead of 40 for libstdc++ std::string).
For happy path (OK status) with large probability, it benefits the performance.

I remember I review a similar patch before, but I cannot find it now..
Good to merge for this one.

@tisonkun Yeah, I also had a strong feeling of déjà vu.

Yeah, I used to submit this patch in #1330, but there is always an ICE in gcc9 during LTO.
It has been workarounded in d13dbfd2c0bab0cdc2bc4b3e8f512041b5173633, so this patch can be merged.

@PragmaTwice That's it! I browse the first page of closed PRs and don't find it. That said, what a large traffic in the community recently 🤣


gRPC reflection in the grpc-gateway plugin

Enable ability to use gRPC reflection in the grpc-gateway plugin
Instead of providing a path to proto file, it would much easier if the plugin were able to take advantage of the reflection protocol to obtain the proto file
other tools capable of using reflection: grpc-cli, Evans

There have been a few proposals about how to avoid having to deploy the proto file with Kong, especially in the context of container images.  Options include:

specify a URL instead of a file path.  Kong would download it at startup.
include the whole content of the .proto file in the configuration.  Might be too heavy on declarative configurations, but workable if injected via the admin API.
this one: use gRPC reflection to pull the definitions from the service.

The first one (pull from an URL) is doable, but has little advantage, since it's hardly easier than making the file accessible, either by adding to a custom image, or by mounting a read-only volume with the required file(s).
Including in the database was proposed at first, but quickly dismissed when seeing not only the size of some .proto specs, but also the problem of adding imported definitions.  There was some possibility of precompiling into binary DescriptorProto bundles, but again, it results in many extra steps for little usability improvement.
gRPC reflection seems very tempting, especially since it's so easy to add on Golang gRPC services.  But the design of Nginx makes it surprisingly hard to initiate an HTTP/2 request that is not a redirection of the main request.  To have a Lua-initiated gRPC call would require an HTTP/2 client Lua library, which are still not stable enough.
Finally, remember that the .proto specification returned by a server via reflection describes the .proto file as it was when the server was compiled (or rather, when protoc compiler generated the gRPC/protoBuf stub code).  If the RESTish interface is added after that, the annotations required by this plugin to perform the transformation would not be there.  That means this option would probably help only for in-house services and not to expose third-party services.
In all, I don't want to discard any of these options, but so far all of them seem to provide limited benefit.

Forgive me for spitballing here, I'm not super familiar with nginx, but could it be done like a write-though cache. Grab the protofile the first hit, cache it for subsequent, expire cache eventually?

Dear contributor,
We're closing this issue as there hasn't been any update to it for a long time. If the issue is still relevant in the latest version, please feel free to reopen it. We're more than happy to revisit it again.
Please have a look at our pledge to the community for more information.
Sincerely,
Kong Gateway Team


Feature/jen preserve contact address

Warning
Info
Issues
Fixes #2111

@davidhabib would you mind reviewing this address fix pull request?

@jjbennett @jlantz not sure why this feature build is now failing.  seems totally unrelated to the changes in this pull request.

@davidhabib I spoke with @jlantz and it appears to be the limit issue with the physical delete again.


Add support to quantifiers on wildcards

The wildcards number and word for example, does not support quantifiers, all have by default the + as match quantifier. Now is supported all the regex quantifiers but * and ?. See more about quantifiers here.

I see the value of allowing for quantifiers when the user is defining a custom regex, but not on the prebuilt matchers. Can you provide an example of why you'd want to quantify those matchers?

Sorry, but with prebuild matchers you mean this?
The main goal is to expand the flexibillity of writing routes, there is the possibility to abstract the regex part of the dynamic segment but with more control, now is no more necessary to write regex for slug to define a limit range logic of database, that define one slug as having at least 3 chars and no more than 120 chars, for example.
$router->map('get', '/articles/{slug:[a-z0-9-]{3,120}}'); // old
$router->map('get', '/articles/{slug:slug{3,120}}'); // new

Quantifiers are not necessary, you can define that you want only one number, or two, or any.
$router->map('get', '/user/{id:number}'); // /user/1
$router->map('get', '/user/{id:number{2}}'); // /user/12
$router->map('get', '/user/{id:number+}'); // /user/123456789...

So, this is something you can already do by adding a custom pattern matcher. However, I'm not against putting it going in for the pre-built matchers we already have.
I don't think it should be put in to the logic for adding a custom matcher though as it makes assumptions. As things stand you can do whatever you like with those custom ones so I don't think we need to make a specific change to look for a quantifier.

yes, this already can be done with custom pattern matchers, but, the main goal of this pr is to increase simplicity and flexibility of mapping routes.
It's a good point, but as the quantifier is optional, the custom pattern can define one "static" quantifier normally, and if is necessary a "dynamic" definition of quantifers, the custom pattern must only leave the quantifier segment empty, and add this on route definition.
$router->addPatternMatcher("hexStaticDelimiter", "0[xX][0-9a-fA-F]{3,6}");
$router->addPatternMatcher("hexDynamicDelimiter", "0[xX][0-9a-fA-F]");
// ...
$router->map('get', '/{hex:hexStaticDelimiter'}, '...');
$router->map('get', '/{hex:hexDynamicDelimiter{3,6}'}, '...');

My only issue is whether a normal user would know this is happening and not end up double registering the dynamic part.
I think it probably makes perfect sense for the built in matchers but maybe not for the custom ones.

So, we can allow quantifiers to override the existing ones in pattern matchers?
Or just throw exceptions, but actually, I don't think this is a good idea.

No, I mean that the pre built matchers would benefit from us adding
quantifiers to them, custom ones though, we should leave completely custom.
On Tue, 16 Feb 2016 15:58 Alex Rohleder<EMAIL_ADDRESS>wrote:

So, we can allow quantifiers to override the existing ones in pattern
matchers?
Or just throw exceptions, but actually, I don't think this is a good idea.
—
Reply to this email directly or view it on GitHub
https://github.com/thephpleague/route/pull/101#issuecomment-184744336.

@philipobenito sorry I have rewrite the comment while you respond that :+1:

@alexrohleder96 I'm happy with that if you want to refactor it, as I say, my main issue would be any introduction of possible misunderstanding of how the regex of a custom matcher would work, but if you can ensure that there is no scope for duplication of what a user may input or confusion around how it works then I'm happy for it to go in.

@alexrohleder96 Is this something you'll have time to refactor or would you like me to look at it?


Getting compilation errors after installing in VS2019

Me too. You solved the error?

Got the same errors

I reproduced the error by installing visual studio 2019, and have pushed a new ue4_smarter_macro_indenting_vs2017-2019.vcmd specifically for newer versions of visual studio that require a referenced assembly to work properly.  Let me know if this resolves your issue, thanks!

It works now in VS2019. Nice!

Works now


Test URL

This is a URL you can use as a test
http://up.mykings.pw:8888/update.txt

tests has been added, thanks


Go operator doesn't shutdown gracefully on SIGTERM

Bug Report
The operator terminates immediately on SIGTERM
What did you do?
Start the built operator and press CTRL+C
What did you expect to see?
The operator wait for all reconcile loops to finish and then exit
What did you see instead? Under which circumstances?
The operators exits immediately interrupting the ongoing reconciles which leaves my kubernetes cluster in a dangling state.
Environment

operator-sdk version:
0.9.0

That is the expected behaviour for SIGINT (Control + C). SIGTERM and SIGINT are generally not handled by the operator and are expected to exit without clean up.

Actually, I think this is supposed to be handled by controller-runtime's signal handler (which SDK uses), but there's a bug that causes the manager to return before the Runnables have stopped.
See https://github.com/kubernetes-sigs/controller-runtime/issues/350
We'll pick this fix up when it makes it into a controller-runtime release.

Does https://github.com/kubernetes-sigs/controller-runtime/pull/967/ allow this to progress?


tests: Improve AggregationTestCase to use partial states

Resolve an aggregate function which operates on the partial results (call terminatePartial()), to make use of Partial states of aggregate functions, e.g. TopKAggregation, PercentileAggregation.

It looks good to me. I think this deserves a comment on why we are building and invoking the aggregation function with the partial type.

It looks good to me. I think this deserves a comment on why we are building and invoking the aggregation function with the partial type.

Would you mind taking a look at the comments I've added?

It looks good to me. I think this deserves a comment on why we are building and invoking the aggregation function with the partial type.

Would you mind taking a look at the comments I've added?

Great, thanks!


Please link: https://www.webrtc-experiment.com/screenshot.js ERROR in Crome Console

I am trying to record animation overlayed over video element using RecordRTC in Angular 9 but when I start recording it gives me an error of "Please link: https://www.webrtc-experiment.com/screenshot.js"

You can see the error in the above image
my code
`play = () => {
const square = new Square(this.ctx);
this.squares = this.squares.concat(square);
// this.draw();
const recorder = new RecordRTC(this.canvas.nativeElement, {
type: 'canvas',
mimeType: 'video/webm;codecs=h264'
});
recorder.startRecording();
recorder.stopRecording(() => {
  const recordedBlobs = recorder.getBlob();
  const url = URL.createObjectURL(recordedBlobs);
  console.log(url);
  const file = new File([recordedBlobs], 'video.mp4', {
    type: 'video/mp4'
  });
  invokeSaveAsDialog(file, 'test');
});

}`
@muaz-khan

@muaz-khan How can i add screensort.js to my angular.json or install in my angular project to fix this issue

Wonder why is this closed?
I am getting this in my vue.js project.

Wonder why is this closed?
I am getting this in my vue.js project.

Hello there!

I solved this with a quick hack by creating screensort.js and copy-paste the content for the above website
by configuring it in my angular project my error was resolved
I hope is works for you as well. cheers

Hello  @hiren3897 I just added this script to the project and it was solved
https://www.webrtc-experiment.com/EBML.js

@hiren3897
For me, its creating a lot of errors in the screenshot.js file. What I did is I created this file in the same directory as the file where I'm using it and imported it like:  import "./screenshot.js" and its showing a lot of errors in the screenshot.js file. :(
some are below:

@RacketyWater7
I fixed it by adding <script src="https://www.webrtc-experiment.com/screenshot.js"></script>


forward_with_cond_scale(*) in classifier_free_guidance.py

Hi, @lucidrains! In forward_with_cond_scale(*) function of classifier_free_guidance.py, it seems that the code return null_logits + (logits - null_logits) * cond_scale is not right. According to the original paper (CLASSIFIER-FREE DIFFUSION GUIDANCE) I think the code should be logits + (logits - null_logits) * cond_scale. Maybe I am wrong. Could you please respond to this question?

@xunguangwang it is equivalent, just my scale starts at 1, but theirs start at 0


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-apimanagement
Module Details
Resource Module for API Management
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
sharmilamusunuru
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

Have noticed a open issue on the similar contribution

Hey, I've got draft Terraform module for API Management here: https://github.com/lukemurraynz/terraform-azurerm-avm-res-apimanagement-apimangement
Let me know if you have any thoughts, successfully deployed API Management with it, could be a good baseline to start.


Fix: App is crashing when try to change the status bar color programatically

Issue
App is crashing with the following error as soon as it is launched.

Expected
App should not crash.
Steps to reproduce
Run application.

@kaungkhantsoe Can you please add device-specific such as Model, and OS version 😄

@kaungkhantsoe Can you please add device-specific such as Model, and OS version 😄

@hoangnguyen92dn Updated 🙏


Add License to project

Probably will be adding MIT license but have a look again at it.

Added MIT License.


WW-4873 Makes ActionInvocation not serializable and InvocationSessionStore$InvocationContext transient

⚠  For simpler review, please review each commit separately.
❓ Why serialize and deserialize methods of ActionInvocation deleted? ActionInvocation is a large complex object which contains request, response, container, value stack and action context. It's hard to maintain it serializable e.g. user may want to store a private not serializable object in action. And It's not a good practice (CWE-579: J2EE Bad Practices: Non-serializable Object Stored in Session).
ℹ I know I also deleted that.container = actionContext.getContainer(); (replacing restored invocation container with current container) with ActionInvocation.deserialize method. I saw it's not needed and even it's better for restored default invocation to work with itself stored container to keep consistency. Anyway currently it's really not needed because only TokenSessionStoreInterceptor uses it and it only passes the invocation to result and result is not aware about DefaultActionInvocation (only knows ActionInvocation):
if ((result != null) && (savedInvocation.getProxy().getExecuteResult())) {
    result.execute(savedInvocation);
}

Changes Unknown when pulling 2941416a1832393a25a9bb823f5763fc7851da23 on yasserzamani:WW-4873_2 into ** on apache:master**.

wtf :\

Looks lik a known issue https://github.com/lemurheavy/coveralls-public/issues/351

That is weird. https://coveralls.io/github/apache/struts always claims it's a FIRST BUILD ON MASTER. To test coveralls.io, I simulated at https://coveralls.io/github/yasserzamani/struts but it works there!
Another thing is it jumps from #1 to #606 at https://coveralls.io/repos/188307/builds?page=2, I'm not sure if it's a problem but https://coveralls.io/repos/52976/builds?page=64 is not like this.

I think I have fixed it, I forgot that I had setup the build on Travis to be triggered only by PRs - now also changes to the master branch trigger a build :)

Looks good to me, 👍

Works :) 👍  example


Status 502: [WARNING] Invalid HTTP request received.

I was trying to build a typeahead search API. This API gets called in quick succession, and I am getting an intermittent 502 response.
To Reproduce
Not sure how to reproduce this, as normal API calls, when spaced out, are working fine.
Expected behavior - Logs
2019-11-05T06:17:55.447961016Z [2019-11-05 06:17:55 +0000] [16] [INFO] ('<IP_ADDRESS>', 50964) - "POST <<URL_NAME>> HTTP/1.1" 200

Noted Intermittent Behaviour - Logs
2019-11-05T06:17:56.459601437Z [2019-11-05 06:17:56 +0000] [16] [WARNING] Invalid HTTP request received.

Environment:

OS: Debian GNU/Linux 10 (buster)
FastAPI Version : 0.38.1
Python version: 3.6
Server: Gunicorn with 2 Uvicorn workers (see config file below)

bind = "<IP_ADDRESS>:4000"
workers = 2
worker_class = "uvicorn.workers.UvicornWorker"
timeout = 300

Additional context

Added timeout in config after searching on the internet, did not work

Not sure how to help without a minimum example, maybe you can try to hit
your endpoint with ab or wrk and get reproducibility?
Le mar. 5 nov. 2019 à 7:25 AM, gautamsinghania95<EMAIL_ADDRESS>a écrit :

I was trying to build a typeahead search API. This API gets called in
quick succession, and I am getting an intermittent 502 response.
To Reproduce
Not sure how to reproduce this, as normal API calls, when spaced out, are
working fine.
Expected behavior - Logs
2019-11-05T06:17:55.447961016Z [2019-11-05 06:17:55 +0000] [16] [INFO] ('<IP_ADDRESS>', 50964) - "POST <<URL_NAME>> HTTP/1.1" 200
Noted Intermittent Behaviour - Logs
2019-11-05T06:17:56.459601437Z [2019-11-05 06:17:56 +0000] [16] [WARNING] Invalid HTTP request received.
Environment:

OS: Debian GNU/Linux 10 (buster)
FastAPI Version : 0.38.1
Python version: 3.6
Server: Gunicorn with 2 Uvicorn workers (see config file below)

bind = "<IP_ADDRESS>:4000"
workers = 2
worker_class = "uvicorn.workers.UvicornWorker"
timeout = 300
Additional context

Added timeout in config after searching on the internet, did not work

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tiangolo/fastapi/issues/680?email_source=notifications&email_token=AAINSPUEFVDANXRABQ2TEODQSEGWJA5CNFSM4JI6FYKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HWZQLVA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAINSPVFFABQU2ZPFAQ77KTQSEGWJANCNFSM4JI6FYKA
.

Hi!!
This is an issue with the deployed version of the app. I have tried to reproduce the problem in my local environment, but to no effect.
Please see if you can help in some other fashion.
Thanks!
Gautam

Hi,
Closing the issue as it was resolved from my end.
Resolution: The deployment platform only accepted HTTP 1.1 calls, but the uvicorn worker class I was using uvicorn.workers.UvicornWorker was sending both types of request. Replacing it with uvicorn.workers.UvicornH11Worker resolved it.
Thanks.

glad you solved it, for reference which plateform is it and by both types of request you mean 1.0 and 1.1 calls ?

Thanks for the help here @euri10 ! :clap: :bow:
Thanks for reporting back and closing the issue @gautamsinghania95  :+1:

@gautamsinghania95 sorry but can you give more information on how to do that? I have the same issue as you and can't seem to find how to change uvicorn.workers.UvicornWorker
Thanks in advance

According to https://github.com/tiangolo/uvicorn-gunicorn-docker/pull/38, you can set it as an environment variable now WORKER_CLASS="uvicorn.workers.UvicornH11Worker"

I had this issue as well, the issue was that I was trying to access with HTTPS instead of HTTP.

I had this issue as well, the issue was that I was trying to access with HTTPS instead of HTTP.

Hi, I'm getting the same error, could you explain how you solved it? I used Caddy which auto issues https :/

This not work for me, have you found any other solutions guys?

According to tiangolo/uvicorn-gunicorn-docker#38, you can set it as an environment variable now WORKER_CLASS="uvicorn.workers.UvicornH11Worker"


Multicharacter operations failure

“NOT” cannot be added as a unary operator.
jsep.addUnaryOp("NOT")
>>> JavaScript Expression Parser (JSEP) v0.3.0
>>> Object {type: "Compound", body: Array[2]}
jsep("(NOT x)")
>>> jsep.min.js:2 Uncaught Error: Unclosed ( at character 5(…)

This works with other operators:
jsep.addUnaryOp(“%")
>>> JavaScript Expression Parser (JSEP) v0.3.0
jsep("% x")
>>> Object {type: "UnaryExpression", operator: "%", argument: Object, prefix: true}

Closed as duplicate of #43.


Recognition of Profile pages.

I noticed that pageProfile is set to true also on some nonprofile pages. For instance on
https://www.wikitree.com/wiki/Space:Data_Doctors_Report_2022-10-02
it causes the timeline to display.
The problem is in regex: /(/wiki/)\w.-[0-9]/g where "." should be "[^:]". This regex /(/wiki/)\w[^:]-[0-9]/g should exclude all other namespaces.
Aleš

I corected the regex, you got it wrong.
dot means any character and [^:] equaly means any character except semicolon. * means any number of repetitions and must be after the dot or [^:] expression.

I corected the regex, you got it wrong.

Thanks, I missed that.


415 - Switch up some requireds, optionals, & if applicables

https://app.zenhub.com/workspaces/ccbc---delivery-board-61c0c1204c8bcb001491c5f3/issues/bcgov/conn-ccbc-portal/415
@wenzowski I added altOptionalText to ui:options so we can override the optional text as you asked. I decided to keep the hideOptional flag to hide the label on non required fields but I'm open to other suggestions.

I decided to keep the hideOptional flag to hide the label on non required fields
Makes sense. Small increments of value. I'd love to track eliminating hideOptional as a new tech debt ticket though, if we can?


That looks perfect thank you very much!


Document 0 for max_conections_in disables it

Document that setting proxy.config.net.max_connections_in to 0 disables the max_connections_in throttling.

For 9.2.x: https://github.com/apache/trafficserver/pull/11647

[approve ci autest]


Update test-at module dependencies

Sparkta maven dependencies of this modules are deprecated

Issue migrated to JIRA.


Refactor to (hopefully) make writing docs easier

Makes everything a plugin, should allow for easier development & docs
Splits lib.rs up into a few more files
Flattens import structure
Makes util public again as testing showed that having those functions to hand is helpful

Makes util public again as testing showed that having those functions to hand is helpful

Yeah, it makes sense to have a "lib" of utils funcs to simplify user's life.


Add info

Add info in:

Messaging request
fix link issues
fix typo

I have had a look, and the cdn-resize seems to be using Fastly on the backend. Using my industry knowledge, I am almost confident that this is going to be this: https://developer.fastly.com/reference/io/
I would mark it down as
Image optimization CDN

"I added the modification into my pull request. Thanks for the feedback!"

Thanks ! @userbradley


Improvement: Optimize image paths for better maintainability

Currently, the images in the code are imported and used directly, which can cause issues if the folder structure is modified. This makes it difficult to fetch the images correctly from the public folder. To improve maintainability and ensure consistent image retrieval, it is recommended to utilize Next.js' built-in support for relative paths relative to the public folder.
In this code snippet, I propose the following changes:

Update image imports to use absolute paths relative to the public folder.

These modifications will enhance the code's flexibility and make it more resilient to changes in the folder structure.
For example, In signup for organization page, it is implemented like this:
import welcomeImage from "../../../public/images/signup/welcome_img.png";
import emailIcon from "../../../public/icons/email.png";
import lockIcon from "../../../public/icons/lock.png";
import phoneIcon from "../../../public/icons/phone.png";
import contactIcon from "../../../public/icons/contact.png";

<Image src={welcomeImage} height={500} width={500} alt="Welcome to Carbonops" />
...
<Image src={emailIcon} width={30} height={30} alt="Email" />
...
<Image src={phoneIcon} width={30} height={30} alt="Contact" />
...
<Image src={cakeIcon} width={30} height={30} alt="Date of Birth" />

And the better way to implement this is to
Replace the imported images with their respective absolute paths
<Image src="/images/signup/welcome_img.png" height={500} width={500} alt="Welcome to Carbonops" />

<Image src="/icons/email.png" width={30} height={30} alt="Email" />

<Image src="/icons/phone.png" width={30} height={30} alt="Contact" />

<Image src="/icons/cake.png" width={30} height={30} alt="Date of Birth" />

Please assign the issue to me, and I will start working on it promptly.

Hello s2sharpit, thanks for opening a issue, your contribution is valuable to us. The maintainers will review this issue and provide feedback as soon as possible.

Hey @shreya024
ould you kindly review and merge this pull request as soon as possible if everything looks good? It would greatly assist me in proceeding with another issue, #148, as it addresses the problem I'm currently facing.


Fix issue with theme day of week calculations

I was trying to figure out why Tricordarr wasn't calculating the cruiseDayIndex the same way as Swiftarr, and after much swearing I realized that perhaps maybe Swiftarr is wrong. If a cruise starts "tomorrow" (which we define as midnight in the portTimeZone it is expected that "today's" cruiseDayIndex is -1 (tomorrow is 0, etc). This was not the case since we were not anchoring the current date in the comparison calculation. A sample program using snippets from the various Swiftarr calculations revealed:
---
Start: 2024-03-09 05:00:00 +0000
Prior: Day -64 Hour -10 Minute -14
  New: Day -65 Hour 0 Minute 0
---
---
Start: 2024-01-03 05:00:00 +0000
Prior: Day 1 Hour 13 Minute 45
  New: Day 1 Hour 0 Minute 0
---
---
Start: 2024-01-04 05:00:00 +0000
Prior: Day 0 Hour 13 Minute 45
  New: Day 0 Hour 0 Minute 0
---
---
Start: 2024-01-05 05:00:00 +0000
Prior: Day 0 Hour -10 Minute -14
  New: Day -1 Hour 0 Minute 0
---

Since we only look at the .day component of dateComponents the number of full days on the day before the cruise can be 0, which is inaccurate. By also using cal.startOfDay for the comparison we lock the comparison to midnight to ensure that the correct index comes back.

The sample program:
import Foundation

var cal = Calendar(identifier: .gregorian)
cal.timeZone = TimeZone(identifier: "America/New_York")!

func cruiseStartDate(_ dateString: String) -> Date {
    let startFormatter = DateFormatter()
    startFormatter.dateFormat = "yyyy-MM-dd"  // 2023-03-05
    guard let date = startFormatter.date(from: dateString) else {
      fatalError("Must be able to produce a Date from SWIFTARR_START_DATE if it is set.")
    }
    let cruiseStartDateComponents = Calendar(identifier: .gregorian)
      .dateComponents(
        [.year, .month, .day, .weekday],
        from: date
      )
		var cal = Calendar(identifier: .gregorian)
		cal.timeZone = TimeZone(identifier: "America/New_York")!
		var startDateComponents = cruiseStartDateComponents
		startDateComponents.calendar = Calendar(identifier: .gregorian)
		startDateComponents.timeZone = TimeZone(identifier: "America/New_York")!
		guard let result = cal.date(from: startDateComponents) else {
			fatalError("Swiftarr Settings: must be able to produce a Date from cruiseStartDate.")
		}
		return result
	}

func testDate(_ dateString: String) -> Void {
    let components = cal.dateComponents(
      [.day, .hour, .minute],
      from: cal.startOfDay(for: cruiseStartDate(dateString)),
      to: Date()
    )

    print("---")
    print("Start:", cruiseStartDate(dateString))
    print("Prior:", "Day", components.day!, "Hour", components.hour!, "Minute", components.minute!)

    let adjcomponents = cal.dateComponents(
      [.day, .hour, .minute],
      from: cal.startOfDay(for: cruiseStartDate(dateString)),
      to: cal.startOfDay(for: Date())
    )
    print("  New:", "Day", adjcomponents.day!, "Hour", adjcomponents.hour!, "Minute", adjcomponents.minute!)
    print("---")
}

testDate("2024-03-09")
testDate("2024-01-03")
testDate("2024-01-04")
testDate("2024-01-05")

https://sarunw.com/posts/getting-number-of-days-between-two-dates/ was helpful in getting ideas on this.


API endpoint api/restore does not accept Base64 encoded backup files

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
When using Ansible's uri module to upload a Portainer backup file to api/restore the the API responds with:
fatal: [ansibleTarget -> localhost]: FAILED! => changed=false
  connection: close
  content: |-
    {"message":"Failed to restore the backup","details":"cannot extract files from the archive. Please ensure the password is correct and try again: gzip: invalid header"}
  content_length: '168'
  content_type: application/json
  date: Sun, 21 Jan 2024 11:01:32 GMT
  elapsed: 0
  json:
    details: 'cannot extract files from the archive. Please ensure the password is correct and try again: gzip: invalid header'
    message: Failed to restore the backup
  msg: 'Status code was 500 and not [200]: HTTP Error 500: Internal Server Error'
  redirected: false
  status: 500
  url: https://<Portainer-IP>:9443/api/restore
  x_content_type_options: nosniff
  x_xss_protection: 1; mode=block

The backup file I'm uploading is an unencrypted tar.gz file.
Apparently this is because the underlying Python libs Ansible is using for its uri module encode transmitted content in Base64 (see tcpdumps under Additional Information) but the Portainer API doesn't decode the Base64 content it receives and therefore detects an unexpected/invalid file header.
Expected Behavior
Receive HTTP response code 200
Actual Behavior
Receive HTTP response code 500 with following JSON message:
{
  "message":"Failed to restore the backup",
  "details":"cannot extract files from the archive. Please ensure the password is correct and try again: gzip: invalid header"
}

Full HTTP response:
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Date: Sun, 21 Jan 2024 11:50:16 GMT
Content-Length: 168
Connection: close

{"message":"Failed to restore the backup","details":"cannot extract files from the archive. Please ensure the password is correct and try again: gzip: invalid header"}

Steps to Reproduce
Use something like this in an Ansible playbook:
- name: "restore Portainer"
  ansible.builtin.uri:
    url:              "https://<Portainer-IP>:9443/api/restore"
    method:           "POST"
    headers:
      Accept:         "application/json"
      Content-Type:   "multipart/form-data"
      Connection:     "keep-alive"
    body_format:      "form-multipart"
    body:
      file:
        filename:     "/path/to/portainer_backup.tar.gz"
        mime_type:    "application/octet-stream"
    validate_certs:   False
    return_content:   True

Portainer logs or screenshots
see API response in Problem Description
Portainer version
2.19.4
Portainer Edition
Community Edition (CE)
Platform and Version
Docker version 24.0.7, build tag v24.0.7
OS and Architecture
Void Linux
Browser
n/a (Ansible, cURL)
What command did you use to deploy Portainer?
---
version: "3.8"

services:
  portainer:
    image: "portainer/portainer-ce:latest"
    ports:
      - 9443:9443
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "/path/to/portainer/data:/data"
      - "/var/run/docker.sock:/var/run/docker.sock"
    restart: "always"

Additional Information
For debugging purposes, I've used the plaintext HTTP endpoint and recorded the transmitted data using tcpdump. Both times the same backup file was used.
Here's the HTTP streams:
cURL
POST /api/restore HTTP/1.1
Host: <Portainer-IP>:9000
User-Agent: curl/8.5.0
Accept: application/json
Content-Length: 17224
Content-Type: multipart/form-data; boundary=------------------------zfMKhpVsUbL5SALniLNlVH

--------------------------zfMKhpVsUbL5SALniLNlVH
Content-Disposition: form-data; name="file"; filename="portainer_backup_file.tar.gz"
Content-Type: application/octet-stream

............M.$K....G.~ox.z...`.......*.+..c......;.S..=s.fhGfFVEwVFNfdW......^...h#.
.X.o.0hc[...F.al.J`.m......_YU.wf....g`.3.D....'".9.... I.dh...$.....5]W.v[R..I2TE...G.m'
	.v$.C.)W.W.-..$..e<..eIm.u.?...g.7}8.$eP~....,I.R.+...........Aaox8:........~.b.B...F{...{.>.....~....^C.5.n....>y..]..........NN..^.d..._....''...'......tv.....:=..).]..'.7.....g....ki.........ki..n

<snip/>

6......<./..A....txw!.:...._x........'........4.?k...G..)c..W....o...1.0....0..;...f....p...3..........(.{..nm..O......*.~i..PC
5.z........m{.....
--------------------------zfMKhpVsUbL5SALniLNlVH--
HTTP/1.1 200 OK
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Date: Sun, 21 Jan 2024 11:51:31 GMT
Content-Length: 0
Connection: close

Ansible
POST /api/restore HTTP/1.1
Accept-Encoding: identity
Content-Length: 23500
Host: <Portainer-IP>:9000
User-Agent: ansible-httpget
Accept: application/json
Content-Type: multipart/form-data; boundary="===============4522595178099711248=="
Connection: close

--===============4522595178099711248==
Content-Transfer-Encoding: base64
Content-Type: application/x-compressed-tar
Content-Disposition: form-data; name="file"; filename="portainer_backup_file.tar.gz"

H4sIAAAAAAAA/+y9TYgkS7cY1vdH735veH96tvHCYJL8ntATt6sqfyur6mPQq+6q7q47/VPT1T1z
f2ZoR2ZGVkV3VkZOZmRX1wwDAq8MXr2dEGgjgw3GWAtvvDBoY1sIBPZGC2Fs0EpgC20E3hkTEflf
WVXdd2b6zv2UZ2CqM+JExIkTfycizjnR3Pn0IEmSZGga+5UkqfzL/pY1XVfldltS5B1JMlRF3RH0
R6BtJwoJCHYk6UPzKVfuVwItCwYk/LRlPLj9ZUlt63X7Pwbw9mf/N304/yRlUH6017e/LEntUvsr
sqTuCI/CxH/P279BYW94ODoV9ofnF6OD0X7/YshCn5yMRnuX1/t73z7rD/rT4X5/tqfcXkPSNS5u
z77z4D55+eNdq/3ipI8P9/ffHE5OtO5e/2T/pN9fHM2s0ycn188XJxeju5PBjXR28fzu5cw6Pbm+

<snip/>

of3jyXnrxxt/6gXd4Q8j1ULT9tn1pTa4+PHJ26k81i8GjkGO1dmBdHh3Ic86+vO+2V94h/KPivr8
6dMnjNjh6aCyDr80iz9ryOsIR+anKWPb+FeM9ur4b9fj/zGgMP4Hk74wvtw7Hu3nZoCDm8Vw8cPR
M/zj6O21tN9//sMo/nvQf25tHdhP1o3shw7sKuJ+ae7VUEMNNfx64f8PAAD//+Vte38ADgIA

--===============4522595178099711248==--
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Date: Sun, 21 Jan 2024 11:50:16 GMT
Content-Length: 168
Connection: close

{"message":"Failed to restore the backup","details":"cannot extract files from the archive. Please ensure the password is correct and try again: gzip: invalid header"}

When sending the file with Ansible, the "form header" (?) Content-Transfer-Encoding with value Base64 is added. This could be used to trigger a Base64-Decode before trying to extract the backup file.

Turns out, it's not only the api/restore endpoint.
Just tested the api/custom_templates/create/file endpoint and got (kinda) same result. Although that endpoint doesn't throw an HTTP 500 response, but the content of the submitted docker-compose.yml file ends up as Base64-Text in the successfully created custom template.


[Upstream] Rolling Stats rebased against the upstream AC Stats branch

This change is

cachelib/allocator/Cache.h line 89 at r2 (raw file):
Previously, igchor (Igor Chorążewicz) wrote…
Is it needed?

fixed