Support Facebook Login without email

Addresses #623.
I didn't know if I should bump up the version, so I left it as it is now.

@puilp0502 just wanted to say I know this is lingering, I have been caught up on some other stuff and will test this soon.  Thank you for doing it!

@puilp0502 FYI I changed the target branch to version-2.0.0-dev as that's where the next version will come from.  You may have to change your local setup a bit, let me know if that's confusing.

Ok I just went and got a new phone number (thanks Google Voice) and then made a Facebook account that has no email.  Then I signed in and got the following (see below).
I am surprised that signing in like that even works!  I guess email is not a hard requirement for Facebook accounts (learn something new about your own products every day haha).
I am fine to merge this change, but @amandle can you chime in and let me know if this could cause any potential problems?

LGTM, Twitter also doesn't require email be shared, so I don't foresee this change causing problems


fix issue 15930 - min/max of pointers violates const

Is that working around a bug in the compiler?

No, it's a library bug, if it was a compiler bug then the following would fail.
void main(string[] args)
{
    import std.traits;
    auto test()
    {
        const int* a;
        return a;
    }
    static assert(is(ReturnType!test == const)); // OK
}�

The bug is that min() and max() in some cases select always the first type but the second might be const.


Appending SVG to a div container. Possible?

After publishing the Adobe Animate file. The SVG is always added to as last item of the body. Is there a way to place it inside a certain DIV tag?

https://github.com/cjgammon/SnapSVG-Animator/wiki/FAQ

Thank you @c


feat: Support FormData object entries parsing

Here is a solution to support object entries in FormData which enables <input type="file" /> parsing.
FormData object entries are stringified before FormData is parsed using the URLSearchParams trick.
FormData object entries are not parsed by the default parser, making it rather versatile as it enables users to parse object entries of any type using a custom parser.
I had to make some typings generic in order to support custom parsed search params types.
Fixes #14.

Thank you, that'd be great!

Thanks again for adding this, @mdoury. I just published it as v0.3.1.

You're welcome @rileytomasek. I'd be happy to help more if you want.

Thanks @mdoury. Let me know if you have any ideas, but I'd like to keep Zodix as lean as possible, and prevent it from evolving into another of the many bloated form libraries.


Missing video thumbnail on hosted allsky website

How to generate thumbnail for video on hosted allsky-website?
https://www.wijaya.com/allsky/videos/
It is hosted on Dreamhost.

It seems that you're missing this file. https://github.com/thomasjacquin/allsky-website/blob/master/NoThumbnail.png
Make sure it has been uploaded properly to your website.

Noted, The image file was corrupted, and now it has been replaced,
But still no thumbnails from the videos.

Thomas,
do you know how to create thumbnails from video files?  Will ffmpeg do it?
Eric

Yes, @EricClaeys. See this thread https://stackoverflow.com/questions/27145238/create-thumbnail-from-video-using-ffmpeg
I meant to do it a while ago but lacked the time. I believe extracting a frame in the middle of the video should be fine as it would avoid dusk and dawn over-exposure.

Hi Thomas & Eric -
I also ran into this 'No Thumbnail' problem after moving your website code to my NAS.  Turns out to be a known issue with some NAS's (and some site hosting) not supporting ffmpeg h264 encoding/decoding on the host - something about commercial usage rights for codecs from VLC.
The " --disable-decoder=h264" shows up on the host's ffmpeg command line list, and "Decoder (codec h264) not found for input stream #0:0" is the result.  No luck searching for a way to enable it other than installing another version of ffmpeg on the host and hard coding to that.
Workaround:  I got it working by adding the ffmpeg video thumbnail command line from functions.php into timelapse.sh after the video generation, and having the PI do the generation and lftp upload to the thumbnail folder just after the lftp of the video.  Otherwise the website's PHP code fails to generate the video thumbnail.  I have more details on the fix I configured if that would be helpful. Seems to be working well and not much extra load on the Pi to create/upload a thumbnail each morning.
Sam

Hi Sam, i have the same problem aith allsky on Azure App Service, but i am not an expert with php.
Please can you explain at which point do you made the changes in functions.php and timelapse.sh.
Sascha

@int48 (for ref @thomasjacquin  & @EricClaeys )
After a few PMs requesting more info, here's the revised section of timelapse.sh that creates and uploads a thumbnail from the PI, rather than relying on the PHP server-side code.  No changes are needed to the PHP code on the web server, as the web page will now find an existing thumbnail instead of trying to create one.
Rather than upload a revised timelapse.sh to GIT and get sucked into GIT file mgmt for this one change, I'm simply showing the changes I made below, and assuming anyone using this is familiar with reading & editing shell scripts.  Make a copy of any files being modified before making changes!
Note that all added code is a copy and reuse of existing functionality from Thomas and others work, I just duplicated sections rather than spending time to rewrite it, so it works but isn't as efficient as it could be.
Also, this uses a hard coded THUMBNAIL_SIZE_X value of 100 rather than the value from config.js, and creates the thumbnail jpg file in the $DIR folder on the PI, so it will get cleaned up by the existing auto-delete function.
(existing section in timelapse.sh that generates the video file:)
ffmpeg -y -f image2 \
	-loglevel warning \
	-r $FPS \
	-i $DIR/sequence/%04d.$EXTENSION \
	-vcodec libx264 \
	-b:v ${TIMELAPSE_BITRATE:-2000k} \
	-pix_fmt yuv420p \
	-movflags +faststart \
	$SCALE \
	$DIR/allsky-$DAY.mp4
RET=$?

(add this revised code below the section above:)
if [ $RET -ne 0 ]; then  # if any error generating video then quit, otherwise create a thumbnail
	echo -e "\n${RED}*** $ME: ERROR: ffmpeg failed with RET=$RET"
	echo "Links in '$DIR/sequence' left for debugging."
	echo -e "Remove them when the problem is fixed.${NC}\n"
	exit 1
else # Create thumbnail - per code from functions.php
	ffmpeg -ss 00:00:05 -i $DIR/allsky-$DAY.mp4 \
		-frames:v 1 \
		-filter:v scale='100:-1' \
		-frames:v 1 $DIR/allsky-$DAY.jpg
	RET=$?
fi

(finally, add the lftp of the thumbnail to the server after copying the video file - add the second section to the existing code as shown:)
		TEMP_NAME="tl-$RANDOM"
		(
			FILE="allsky-$DAY.mp4"
			FULL_FILE="/$DIR/$FILE"
			lftp "$PROTOCOL://$USER:$PASSWORD@$HOST:$MP4DIR" -e "set net:max-retries 1; put "$FULL_FILE" -o $TEMP_NAME; rm -f "$FILE"; mv $TEMP_NAME "$FILE"; bye"
			RET=$?
			if [ $RET -ne 0 ]; then
				echo "${RED}*** $ME: ERROR: lftp failed with RET=$RET on '$FULL_FILE'${NC}"
		       fi
			FILE="allsky-$DAY.jpg"
			FULL_FILE="/$DIR/$FILE"
			lftp "$PROTOCOL://$USER:$PASSWORD@$HOST:$MP4DIR/thumbnails" -e "set net:max-retries 1; put "$FULL_FILE" -o $TEMP_NAME; rm -f "$FILE"; mv $TEMP_NAME "$FILE"; bye"
			RET=$?
			if [ $RET -ne 0 ]; then
				echo "${RED}*** $ME: ERROR: lftp failed with RET=$RET on '$FULL_FILE'${NC}"
		       fi
		) &

Feel free to reply on this thread if any questions or comments...
Sam

Hi,
Can you include the entire timelapse.sh file?
Thanks
Baltazar

Closing Issue - fixed in PR #1255 which will be in the next version of Allsky.


Update Add-VMGpuPartitionAdapter (2025) Related Links section

PR Summary
Resolve cabgen error related to incorrect formatting of Related Links section. Related Links should not include - to define the list.
PR Checklist

[X] Descriptive Title: This PR's title is a synopsis of the changes it proposes.
[X] Summary: This PR's summary describes the scope and intent of the change.
[X] Contributor's Guide: I have read the contributors guide.
[X] Style: This PR adheres to the style guide.

Thanks for submitting your pull request. To improve the quality of your content and make sure all errors are resolved, we recommend that you use the PubOps publishing process.

Add the Sign off label when you think your PR is ready to merge. A PR reviewer either merges it, or adds the Back to Submitter label with a comment about what needs to be fixed and sends it back to you.

If you need to update your content per the PR reviewer feedback, add the Sign off label again.

Your content is published live during one of the next publishing cycles, which are weekdays at 10:30 AM Pacific Time and 3:30 PM Pacific Time.

If you have a question, post it on the Ask an Admin support channel.

@mtrilbybassett,
Thank you for catching this. Merging shortly.
Have a most pleasant day!


dbeaver: 21.0.3 -> 21.0.4

Motivation for this change
Update to latest release https://github.com/dbeaver/dbeaver/releases/tag/21.0.4
Things done

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

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

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

/nix/store/dj5h2lzg3347yll268cdkq31pwa0wz2k-dbeaver-ce-21.0.3<PHONE_NUMBER>
/nix/store/sa95wr6vr58mcwqlqr3zbnwrwgn06ssk-dbeaver-ce-21.0.4<PHONE_NUMBER>

[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121570 run on x86_64-linux 1

1 package built:

dbeaver


More StackHPC OpenStack tests

CI: Add Grafana and OpenSearch Dashboards variables for SOT
CI: Add Docker and SELinux variables for SOT
CI: Separate monitoring vs host test execution in SOT
SOT: Support OpenSearch and Dashboards TLS
ci-multinode: Add internal interface to seed
DNM: Slim CI, pin sot_version

This isn't too far off. The aio job has passed. It would take more effort to get it working on a multinode, but is not a million miles away.

recheck


Add a platform independent way to validate if the runtime client has internet access

XRTK - Mixed Reality Toolkit Feature Request
Is your feature request related to a problem? Please describe
There should be a simple single flag/property/method to query the XRTK to check if there is a valid internet connection, regardless of which platform the project is running on.
Ideally, this should integrate with the Platform system to give a single point of call.
How would you classify your suggestion

New platform support
Usability / Configuration
Architecture / Services

Describe the solution you'd like
A single property/field/method against the Platforms interface with a single call that is served by the currently active platform.

I would assume this would be a flag in the networking system

I would agree, yes


[SpeedDial] should interact better with clicks

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
If you look at any of the speeddial demos, you can see that if you move your mouse over the button and click, the menu opens partially then closes. This is pretty unintuitive. Clearly anyone hovering over the icon and clicking immediately expects to open the speeddial on click, not cancel opening the speed dial. I recommend adding functionality that ignores clicks until the menu has completely opened.
Examples 🌈
No response
Motivation 🔦
When trying the component out for the first time, I tried to click on it, which immediately closed the menu. It seems there are edge cases that could be improved without any significant downside.

From material design guidelines, it shows on hover. However, I agree with you that it is not intuitive and there should be a way to disable this behavior.
https://material.io/components/buttons-floating-action-button#extended-fab

@billytetrud Note that you can control the open prop to adapt the behavior to your need.

@siriwatknp To be clear, I'm not suggesting disabling open-on-hover (although making the mechanism of opening it configurable would be useful). Rather, I'm suggesting that if both click and hover are mechanisms of changing the open state, there should be some reasonable handling of the edge case I brought up above where the user hovers over and immediately clicks.
@oliviertassinari Ah interesting. Thanks. It sounds like you're suggesting something like capturing an onOpen event and re-toggling open in the appropriate cases. Looks like the event.reason can be used to figure out what kind of event caused the open state change. Is that what you're suggesting ?

I agree that mui should provide a default behavior that solves this to improve the UX of the speed dial.


DoNotMock removed without notice

As part of: https://github.com/google/error-prone/commit/66f4d6ef01a90d7422d2292c8735d4e14375599c#diff-e9fcfd3db76c805219c6849391a9cdcf
DoNotMock and SpyNoMock were removed.  But there are no notes indicating that this was the case in any of the release notes since this change.
This means anything that used the public annotation was spontaneously broken when they upgraded.

@cushon can we document the replacement?

Sorry about this.  These were not intended to be external because the enforcement story is more difficult.  I will re-opensource @DoNotMock, but I'm less happy with @SpyNoMock, and I'm not excited about people using that one.  Do you use both these annotations, or just @DoNotMock?

Just DoNotMock. It feels like it should be put over in JSR for anyone to use.


WIP More docs

Note here I moved the function reference to a pymd file to enable evaluation of examples.  However not sure how that should work with #173 ...
Marked as WIP, will continue along with time series, nodata, and pandas/numpy ...  Just shout if anyone wants to go ahead and merge this for any reason.

Note here I moved the function reference to a pymd file to enable evaluation of examples. However not sure how that should work with #173 ...

If/when we get Sphinx processing of .py files to generate docs, the reference.pymd file will likely be obsolete.

@metasim ready to take a look and merge so we can  get smaller increments of changes from more authors


Cannot set extension (extended) property

I have no success in setting extended property whatever I do. I have isolated the reproducible piece of code:
      public async Task CleanTest(string extName)
      {
         ExtensionProperty ep = new ExtensionProperty
         {
            Name = extName,
            DataType = "String",
            TargetObjects = { "User" }
         };

         App app = (App)(await _client.Applications.Where(a => a.AppId == _managementAppClientId).ExecuteSingleAsync());
         app.ExtensionProperties.Add(ep);
         await app.UpdateAsync();

         GraphUser user = (GraphUser)(await _client.Users.Where(u => u.UserPrincipalName.Equals("email")).ExecuteSingleAsync());
         string propName = FormatExtensionPropertyName(extName); //formats properly as extesion_xxx_name
         user.SetExtendedProperty(propName, "testvalue");
         //user.SetExtendedProperty(extName, "testvalue");
         await user.UpdateAsync(); // fails here
      }

user.UpdateAsync() according to Fiddler doesn't even go out and application fails with an exception:
"The property 'extension_e206e28ff36244b19bc56c01160b9cf0_UserEEEqdbtgd3ixx2' does not exist on type 'Microsoft.Azure.ActiveDirectory.GraphClient.Internal.User'. Make sure to only use property names that are defined by the type."

I am also having this issue - has there been an Active Directory update?

@ronanscally hey, i still wasn't able to solve this. I think there was an update, I also tried to keep downgrading Client Library version by version and can reproduce the issue straight away, therefore not a Client Library issue.

Does anyone have any update on this?

no, unfortunately still having the same issues.... :(
I will ask in the Azure Advisors Yammer Network with your post.

Thanks. Please keep us posted, this bug is eating me alive.

This bug seems to have been introduced between Graph API library that depends on Microsoft.Data.Services.Client v5.7, compared to v5.6.4. I was able to workaround the problem either use assembly redirects in your configuration, or revert back to the v5.6.4 package.

I'm still struggling. I have this method that should create an extended property, but when it hits the await application.UpdateAsync() line, my simple console project exits. Any ideas?
`private static async Task Run()
{
Uri serviceRoot = new Uri(serviceRootURL);
ActiveDirectoryClient _adClient = new ActiveDirectoryClient(serviceRoot, async () => await GetAppTokenAsync());
var application = (Application)_adClient.Applications.Where(app => app.AppId.Equals(clientID, StringComparison.InvariantCultureIgnoreCase)).ExecuteSingleAsync().Result;
bool isExtended = false;
foreach (var item in application.ExtensionProperties)
{
    if (item.Name.Equals("reachOutClientInstallKey", StringComparison.CurrentCultureIgnoreCase))
    {
        isExtended = true;
        break;
    }
}

if (!isExtended)
{
    ExtensionProperty reachOutClientInstallKey = new ExtensionProperty
    {
        Name = "reachOutClientInstallKey",
        DataType = "String",
        TargetObjects = { "User" }
    };
    ExtensionProperty reachOutClientInstallSecret = new ExtensionProperty
    {
        Name = "reachOutClientInstallSecret",
        DataType = "String",
        TargetObjects = { "User" }
    };
    application.ExtensionProperties.Add(reachOutClientInstallKey);
    application.ExtensionProperties.Add(reachOutClientInstallSecret);
    await application.UpdateAsync();
    Console.WriteLine("Done!");
    Console.ReadLine();
}

}
`
This is my packages.config
`

`

This is affecting me as well.

Oddly enough, I can test my exact same code out in LinqPAD and it works just fine.  When I run it in my actual app is when it starts failing on me.

Alternative Workaround (v5.7 compatible)
I've got an alternative workaround for this bug, for those that want to use the version 5.7 OData libraries rather than redirecting to the v5.6.4 versions.
Thanks to various contributors on this thread for hints that pointed me to this end.
Add a request pipeline configuration handler.
// initialize in the usual way
ActiveDirectoryClient activeDirectoryClient =
  AuthenticationHelper.GetActiveDirectoryClientAsApplication();
// after initialization add a handler to the request pipline configuration.
activeDirectoryClient.Context
  .Configurations.RequestPipeline
  .OnMessageWriterSettingsCreated(UndeclaredPropertyHandler);

In the handler, change the ODataUndeclaredPropertyBehaviorKinds value on the writer settings to SupportUndeclaredValueProperty.
private static void UndeclaredPropertyHandler(MessageWriterSettingsArgs args)
{
  var field = args.Settings.GetType().GetField("settings",
    BindingFlags.NonPublic | BindingFlags.Instance);
  var settingsObject = field?.GetValue(args.Settings);
  var settings = settingsObject as ODataMessageWriterSettings;
  if (settings != null)
  {
    settings.UndeclaredPropertyBehaviorKinds =
       ODataUndeclaredPropertyBehaviorKinds.SupportUndeclaredValueProperty;
  }
}

Some background for those that care.
Looking at the stack trace produced from the error: "The property 'extension_....' does not exist on type 'Microsoft.Azure.ActiveDirectory.GraphClient.Internal.User'. Make sure to only use property names that are defined by the type."
Error: System.Data.Services.Client.DataServiceRequestException An error occurred while processing this request.
   at System.Data.Services.Client.DataServiceContext.EndSaveChanges(IAsyncResult asyncResult)
-- snip --
Caused by: Microsoft.Data.OData.ODataException
   at Microsoft.Data.OData.WriterValidationUtils.ValidatePropertyDefined(String propertyName, IEdmStructuredType owningStructuredType, ODataUndeclaredPropertyBehaviorKinds undeclaredPropertyBehaviorKinds)
-- snip --
   at System.Data.Services.Client.Serializer.WriteEntry(EntityDescriptor entityDescriptor, IEnumerable`1 relatedLinks, ODataRequestMessageWrapper requestMessage)
-- snip --

The ValidatePropertyDefined() is passed a ODataUndeclaredPropertyBehaviorKinds value that is None by default, by changing that value to SupportUndeclaredValueProperty we can avoid the exception.
So look at the WriteEntry() method further up the stack, it creates a new ODataMessageWriter with ODataMessageWriterSettings. There is no way to customize these settings that I could find, they are created as a local instance and never exposed outside of WriteEntry().
However, we can plug into the writer pipeline through the Context.Configurations object.  The handler passed to OnMessageWriterSettingsCreated is passed a MessageWriterSettingsArgs with that ODataMessageWriterSettings instance.
The MessageWriterSettingsArgs object contains a shim (of type DataServiceClientMessageWriterSettingsShim) for the settings but we need
to get to the underlying settings object (of type ODataMessageWriterSettings). Its a private field a little bit of reflection is required; naughty.
Once we get that, change the UndeclaredPropertyBehaviorKinds and we are done.
A more intelligent handler would only switch the value for the specific methods you need. No guarantees of what side-effects might be, but in my testing it works fine.
Tested and working with the latest packages (at time of writing):
Microsoft.Azure.ActiveDirectory.GraphClient version="2.1.0"
Microsoft.Data.Edm version="5.7.0"
Microsoft.Data.OData version="5.7.0"
Microsoft.Data.Services.Client version="5.7.0"
Microsoft.IdentityModel.Clients.ActiveDirectory version="3.13.4"
System.Spatial version="5.7.0"

Enjoy!

This solution worked for me with the OData version set 5.8.1 after I ran into this issue AGAIN.

Sure would be nice to see this fixed - ended up having to use the workaround in version 5.8.4.


Pass url params in rewrites and redirects

** Please describe which feature you have a question about? **
Rewrites and redirects
** Provide additional details**
Hello, I'm trying to set up a 301/302 redirect from a path in my amplify application. i.e. /test to another domain i.e. https://example.com/test. The redirect works as expected, but if I try to add some url parameters, /test?utm_test=test the redirect strips the url parameter and redirects to https://example.com/test. With the 200 rewrite, url params don't get stripped.
I want
/test?utm_test=test&utm_something=something -302-> https://example.com/test?utm_test=test&utm_something=something
I get
/test?utm_test=test&utm_something=something -302-> https://example.com/test
Is there a way to pass along all the url parameters in one shot?
As a side note, I am trying to redirect the path including the trailing slash and excluding the trailing slash. i.e. /test and test/. I know you can use the regex route to do both i.e. </(\/test)(\/)?/> -> https://example.com/test but there doesn't seem to be a way to use path parameters with regex paths?
i.e. </(\/test\/<path_param>)(\/)?/> --> https://example.com/<path_param>  or even a way to specify the regex match group? --> https://example.com/<regex[1]> or something like that.
Thanks for the help

1 Currently we do not support redirect with query string, we have added the feature into our backlog
2 <> can be used to redirect everything after path to another url
example:
Source: /test/<> Target: https://example.com/<*> Type: 301/302

@hzhenmin Thanks for the <> tip. I didn't know you could do that. 👍
We found a workaround for the querystring issue for now. Thank you.

@patleeman could you share your workaround for other users who end up here?

@swaminator sure thing.
I ended up doing a 200 rewrite to an endpoint I wrote that returned a 302 redirect to the domain I wanted with the url parameters appended.
Not the best solution but it works for now.

@hzhenmin , Re-asking the question that @patleeman asked.
If we use regex to get a capture group, can we reuse that group?
</^([^\.]+(?<!\/))$/> will match for:
/test
But not match for:
/test/
/test.html
So if a user hits https://example.com/test is there anyway to say we want to redirect them to https://example.com/test/ using that capture group?
You mentioned the functionality of a query string in the backlog but I thought more generically it would imply anything in a capture group.  Is there an update if that functionality will be out soon/is out but the documentation is lacking so we don't know the syntax?

This seems to be breaking OIDC callbacks, where the user is redirected from the IdP back to the app route like: https://myapp.com/implicit/callback?code=abcxyz
The user is then immediately redirected by Cloudfront to https://myapp.com/implicit/callback/ without the query parameters, which breaks the OIDC flow.
The only solution was to force a 200 back to index.html using the rewrite rule specified here: https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html#redirects-for-single-page-web-apps-spa
Though, it's not clear how that's working, without seeing the underlying Cloudfront configuration. It simply stops executing the 301, which preserves the query parameters.
@hzhenmin what's the solution proposed to allow redirects while preserving query parameters in Amplify?

+1 , We are trying to do RegEx with capture groups. Very difficult to replicate redirects from existing systems.

Is this feature implemented with a Lambda@Edge? Maybe if we could get access to the source it would become clearer to people?

This seems to be breaking OIDC callbacks, where the user is redirected from the IdP back to the app route like: https://myapp.com/implicit/callback?code=abcxyz
The user is then immediately redirected by Cloudfront to https://myapp.com/implicit/callback/ without the query parameters, which breaks the OIDC flow.
The only solution was to force a 200 back to index.html using the rewrite rule specified here: https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html#redirects-for-single-page-web-apps-spa
Though, it's not clear how that's working, without seeing the underlying Cloudfront configuration. It simply stops executing the 301, which preserves the query parameters.
@hzhenmin what's the solution proposed to allow redirects while preserving query parameters in Amplify?

Hi berniedurfee,
Did you resolve the issue with OIDC callback url not preserving parameters?
I am trying to implement OKTA authentication (OIDC) for a React based SPA and trying to host the application into AWS Amplify (I tried initially to host SPA in S3 as static website along with Cloudfront  and had PKCE errors not supporting http protocol with S3 website endpoint and eventually ended trying to use AWS Amplify)
When deployed to AWS Amplify, application tries to authenticate initially, but redirecting back to callback url (https://domainname.com/implicit/callback) seems to be not routing to the react callback component.
I tried using a hack to rewrite the callback url, https://domainname.com/implicit/callback to https://domainname.com/#!implicit/callback in order to route to the Logincallback component, but missing code and state parameters which are required to complete authentication.
Secondly, I was not able to use the regular expression  (</^[^.]+$|.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>) redirect for SPA successfully as given in AWS amplify documentation. This redirect rule is working only until redirecting the callback url to index.html and does nothing after that.
Any thoughts on how to approach this issue?
Thank you!
Regards,
Sudharshan.

This seems to be breaking OIDC callbacks, where the user is redirected from the IdP back to the app route like: https://myapp.com/implicit/callback?code=abcxyz
The user is then immediately redirected by Cloudfront to https://myapp.com/implicit/callback/ without the query parameters, which breaks the OIDC flow.
The only solution was to force a 200 back to index.html using the rewrite rule specified here: https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html#redirects-for-single-page-web-apps-spa
Though, it's not clear how that's working, without seeing the underlying Cloudfront configuration. It simply stops executing the 301, which preserves the query parameters.
@hzhenmin what's the solution proposed to allow redirects while preserving query parameters in Amplify?

Were you ever able to resolve this or build a workaround that allowed for query parameters?

+1 Same question here. Using </index.html/> => /404.html [404 Rewrite] #823

I'm running into the exact same issue using the same setup as @FelixRe0 for a Gatsby site.

I guess I can say it feels better to not be the only one struggling with this.

Others at my company have recommended trying to build some sort of component that would be able to redirect to where the traffic needs to go (in my case its the callback after logging in to Okta) and somehow preserve the query parameters.  But, unless I misunderstand something, there's literally no way to access those parameters in the app, or any app running in Amplify, because as soon as the call hits that boundary, the query parameters are lost.  Is that everyone else's understanding as well?  Or am I oversimplifying this?

@bighoot We ended up reaching out to AWS technical support so hopefully they can help; I think that passing query params is a pretty vital task.
That's how it should work. The redirects are handled on the CloudFront edge server rather than the client.

We reached out to AWS support and they said that this is currently not supported; referencing this issue.
@bighoot @FelixRe0 One way that we are currently getting around it is passing the UTM's with the trailing slash on the end of the URL with UTMS like https://www.example.com/products/kit/?example=true. AWS console doesn't remove the query params when the trailing slash is included. Not sure if this supports your use case but it seems like it's working for us for the time being.

I added the trailing / to the end of the redirect URL and to the callback route in the angular app and, like magic, the redirect that took away the params vanished.  Thanks!  This seems like a complete hack and I have no idea why it works, but it does.  Thank you again.

Same problem here... stopping an ec2 and starting amplify... everything ok except some issues... one of them refer to authentication from usr/pwd provider during user registration with specific token and tokenId sent by email to the user.... then the user confirm from email through url similar to https://example.com/confirmRegistry?token=value1&tokenId=value2
Adding trailing slash seems not to solve it.
Any new idea???
Thanks in advance

Hi @gwryssekk , parameters are used into component to run the provider function that confirms the registry...
params = new URLSearchParams(window.location.search);
token = this.params.get('token');
tokenId = this.params.get('tokenId');
ngOnInit(){
confirmUser(this.token, this.tokenId)
.then( () => {
...
})
.catch( err => console.log(err));
}
The confirmUser function its an http POST request and params are always null because of Amplify redirects to https://example.com/confirmRegistry removing them. So user never can be confirmed.
Regards,
Jose Luis Campos

Hi @jlcampos-iies -- Can you give more detail on your use case? What is the expected result when the user tries to confirm via https://example.com/confirmRegistry?token=value1&tokenId=value2 and what is the actual result?

Use https://example.com/confirmRegistry/?token=value1&tokenId=value2 and it will work. Notice the / before the query parameters.
Still, the amplify team should make any url work...

Hi everyone!
Adding from backend / before the query parameters had desired effect.
Thanks again!
Regards,
Jose Luis Campos

@hzhenmin has there been any progress in adding support for this feature? This is a critical need for simply redirecting from a naked domain https://example.com to the WWW version --> https://www.example.com
We are not able to preserve any UTM parameters that are crucial to our Jekyll site. Please let me know if there is any type of transparency into the backlog.
Thank you!

Can we please have an update on this issue?
I can confirm that @cmaycumber's solution works, but query parameters are an essential feature of web apps. We often don't have control over the code that is calling the uri and can't enforce the addition of a trailing slash.
In my case, I am unable to use Utterances until this issue is resolved since the token is appended to a callback uri that does not a '/'.

Any progress with this? It's not okay that I have to update all my links to the ridiculously looking /page/?param=value structure due to the breaking change in Amplify's redirect behavior. I seriously consider migrating to Netlify because of this issue.

Hi, can someone please provide an update for this issue?
I'm using VueJS with nasty workaround for URL parameter.

Any updates? It is a very necessary feature.

I'm also struggling with this. We have moved our website to a new domain and we need to redirect all requests including query params. This is a critical issue for us. Is there any workaround right now?

Any update?!?!

Hello, WE NEED THIS feature? Look like AWS is not interest in keepe paying costumer. And AWS it's not free. Please. FIX this BUG

+1, same issue, after hours of tests it's impossible to migrate existing routes to amplify. This missing feature it's more than blocking

same issue here
I confirm however that https://myapp.amplifyapp.com/sso/?param1=value1&param2=value2&.... has the desired effect however, this additional / before the ? is not viable.
Can this be fixed please?

same issue here
I confirm however that https://myapp.amplifyapp.com/sso/?param1=value1&param2=value2&.... has the desired effect however, this additional / before the ? is not viable.
Can this be fixed please?

I agree. if we construct the links ourselves and send it to somebody, then manually adding the slash would be a fine solution.
However, if a user is at /shop?brand=SomeBrand and wants to bookmark the page, they will get sent back to /shop/ when using the bookmark later.

For those who are using the trailing slash hack to resolve this issue, how are you preventing the trailing slash from being automatically removed when the URL loads?
eg. When I refresh a page with a URL that has a query string, this is what happens to the URL:
https://myapp.com/section/?id=1   -->   https://myapp.com/section?id=1   -->   https://myapp.com/section

For those who are using the trailing slash hack to resolve this issue, how are you preventing the trailing slash from being automatically removed when the URL loads?
eg. When I refresh a page with a URL that has a query string, this is what happens to the URL:
https://myapp.com/section/?id=1 --> https://myapp.com/section?id=1 --> https://myapp.com/section

this is still an ongoing issue; so the workaround hack isnt great for now

Is there any ETA on resolving this? Most of our sites are on Amplify. For this particular issue we would have to migrate couple of our sites to firebase hosting.

We are going to migrate 4 sites next week for this issue, it's 10 months
that we are asking to solve this issue
Il giorno ven 20 ago 2021 alle ore 07:13 Pankaj Soni <
@.***> ha scritto:

Is there any ETA on resolving this? Most of our sites are on Amplify. For
this particular issue we would have to migrate couple of our sites to
firebase hosting.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/97#issuecomment-902436680,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPNYQMCMU5EBGANH6HP5YDT5XQBLANCNFSM4ITKFR6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Any updates?

Anyone have a good resource for removing Amplify hosting but keeping the rest of the infrastructure? The workaround doesn't work amazingly well with Angular.

I confirm things work well with firebase hosting. The deployment/migration is a breeze too, without much downtime.

Great I will do that soon
Il Sab 21 Ago 2021, 08:09 Pankaj Soni @.***> ha scritto:

I confirm things work well with firebase hosting. The deployment/migration
is a breeze too, without much downtime.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/97#issuecomment-903066498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPNYQNUJS2TX4BNM25CDT3T547JLANCNFSM4ITKFR6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

How can this still not work? We don't have a single page app so the redirect rule fix doesn't apply. UTM tracking is impossible now on any amplify app ever, we can't ask of people to always include a trailing slash (which is a bad workaround because refreshing removes the querystring again anyway). It's issue number 97, so it's basically been reported since day 1?!
We are fixing this by deploying after the test stage to our own S3 bucket and ignoring the CD deploy and verify steps. But to break out of Amplify's features just to make a trivial web feature work baffles me

The issue has several components:

When S3 static web hosting encounters an url without trailing slash, it tries "x.html". If that can't be found, it will do a 301/2 redirect to "x/" and then tests "x/index.html", which works with static websites like Gatsby. S3 removes the query string and there is no way around it
Gatsby by default (or actually reach router) wants to remove trailing slashes

I fixed this by doing the following things:
For Gatsby
Install gatsby plugin to force trailing slashes (https://www.gatsbyjs.com/plugins/gatsby-plugin-force-trailing-slashes/) -- this is only specific to gatsby
To fix the S3 redirect
You can only fix this by routing to a trailing slash before going to S3, so this has to be done in cloudfront with a lambda@edge function, like this one: https://github.com/riboseinc/terraform-aws-s3-cloudfront-website/issues/1
However, you can't change the cloudfront settings of an amplify deploy, so I added this in the test phase of the amplify.yml deploy script:
test:
  phases:
    test:
      commands:
        # Do test things

        # This would be better in postTest, but that runs even when test fails
        - echo "Deploying site to S3"
        # You could here add a thing to exit when not main branch for example
        - aws s3 sync public s3://CUSTOM_S3_BUCKET
        - aws cloudfront create-invalidation --distribution-id YOUR_ID --paths '/*'
        - rm -rf public/*
        - touch public/hoi # necessary for successful pipeline

This deploys your public folder (or change into dist) into your own bucket that you can configure using cloudfront to use the lambda@edge. It then removes the public folder and deploys nothing in the amplify bucket. So you basically use everything from amplify, but circumvent the actual deploy.
I can confirm this 100% works for /x?a=b and /x/?a=b and the querystring also stays when redirecting etc :)
however, it still is quite annoying we need this quite elaborate workaround to get something simple as querystrings working, but I do understand why this is such a long standing issue for the Amplify team: it's actually a limitation of S3.
However, a possible permanent fix would be to allow origin requests in the amplify cloudfront distributions from the amplify settings page.

@watilde your solution worked perfectly. I had to re-order my rules slightly in a different order of preference but after that, it worked perfectly.

Hello, this is still needed and unfortunately the workarounds are still workarounds...

AGree! FIXXXXXXX

AGREE
Il giorno dom 27 feb 2022 alle ore 17:14 Thomas Mosmant <
@.***> ha scritto:

Hello, this is still needed and unfortunately the workarounds are still
workarounds...
—
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/97#issuecomment-1053603421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPNYQM67KORPY53KR5JXO3U5JEXZANCNFSM4ITKFR6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

Any updates regarding this? It should not work like this

No it still works like that afaik, we're currently moving away from amplify ci/cd completely to github actions so we have more control. The "solution" I posted earlier is still how we handle things which is running stable for months now, but it's kind of a non-solution.

@parikls @l-hendriks we just launched support for this: https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html#query-strings-and-path-parameters

@swaminator Thanks for the update.
This is working properly if I define the redirects manually like this:
/foo?bar=<value> => /foo/?bar=<value>

But it is not working for dynamic URLs using *. Sometimes it is throwing 502.
Any idea on how to implement this?

@apal21 Could you please share the exact redirect rule that you're using and elaborate on your intended behavior? Thank you!

@swaminator Thanks for the update, but I think we are still facing the same problem here, query parameters are not passed to the rewritten URL.
Our redirection rule:
{
   "source": "https://foo.com",
   "target": "https://www.foo.com",
   "status": "301",
   "condition": null
}

$ curl -v -L https://foo.com/player.html?uid=3000
> GET /player.html?uid=3000 HTTP/2
> Host: foo.com
>
< HTTP/2 301
< content-length: 0
< location: https://www.foo.com/player.html
< server: CloudFront

> GET /player.html HTTP/2
> Host: www.foo.com

From the documentation:

Query parameters
You can use query parameters for more control over your URL matches. Amplify forwards all query parameters to the destination path for 301 and 302 redirects, with the following exceptions:

If the original address includes a query string set to a specific value, Amplify doesn’t forward query parameters. In this case, the redirect only applies to requests to the destination URL with the specified query value.
If the destination address for the matching rule has query parameters, query parameters aren’t forwarded. For example, if the destination address for the redirect is https://example-target.com?q=someParam, query parameters aren’t passed through.

I don’t think we are in the exceptions mentioned above, or do we?

@Narrator
We have some redirect URLs for OAuth like this:
/salesforce/auth/callback?code=<code> => /salesforce/auth/callback/?code=<code>
/google/auth/callback/?code=<code> => /google/auth/callback/?code=<code>

But I have to put all the rules manually. In some cases, there are multiple query params (?code=<code>&state=<state>).
I thought since this is a pattern, is there a way to have a single rule I can write for this? That way I have to maintain a single redirect only.
Thanks.

@Narrator
It doesn't seem to support SPA redirection with query string params
I created a thread here but I haven't got any reply https://github.com/aws-amplify/amplify-hosting/issues/2781
For example
https://our-website.com/application/path1?param1=XXX&param2=YYY
application is an SPA
path1 is a a path managed by the SPA
I tried with 301 redirect but it didn't work.
It worked with rewrite but it would drop the query params

Some more details for SSG(Static Site Generator) websites:
In a Static Site Generator, when we deploy generated HTML to Amplify. It removes the query params in any case when the page points to an index.html file when inside subfolders.
On the index.html in the root domain, it works really fine. So, www.example.com?utm_source=foo redirects well to www.example.com/?utm_source=foo without any problems.
But the issue is when it is in a sub path/folder:
When we have a file like this: contact/index.html when the browser access www.example.com/contact?utm_source=foo it removes the queries parameters and always redirects to www.example.com/contact/ when if we do not have any rewrite rule with the query strings.
An example with Nuxt.js' default behavior: for a pages/contact.vue page component. It generates the HTML file in a subPath like this /contact/index.html. And Amplify automatically points paths on www.example.com/contact to it. Amplify appends the trailing slash / in this case. An alternative solution is to change the default behavior of Nuxt and set the generator's [subFolders](https://nuxtjs.org/docs/directory-structure/dist/#the-subfolders-property) option to false. This will make Nuxt's generator to generate a contact.html file instead instead of contact/index.html. So, Amplify will not redirect from www.example.com/contact?utm_source=foo to www.example.com/contact/ and it will jeep the browser at www.example.com/contact?utm_source=foo. This is an alternative solution/ workaround.
I believe there is a bug in the code path where Amplify needs to append the trailing slash / and removes the original query parameters.

Almost 3 years later and there's no fix yet... 😞

yeah it could be fixed easily if there just was an option to deploy it on your own S3 bucket instead of Amplify's. You can then add your own cloudfront distribution and have full control of what you need

This is some sorta bull-shit, how could query params bother your setup at first place team amplify? Resolution must be initiated before a workaround.

This is happening to me as well, I spent a whole day debugging to figure out the cause and find myself here. Sad to see the issue isn't closed yet after 3+ years

Also I haven't seen it mentioned anywhere but if you just use a url with 'www', the query params are preserved.
So trying to navigate to 'example.com/path?query=query1' --results in-->  'example.com/path'
But if you just throw in the 'www' (essentially avoiding the redirect in the first place). Such as:

navigating to 'www.example.com/path?query=query1' --succesfully results in-->  'www.example.com/path?query=query1'

Not a fix at all or even a work around. Just a tip to try and avoid the redirect in the first place.

@DevPowers you saved my night!

Any hope for this issue to be fixed?

Believe it or not, the following works:
In the AWS Amplify rewrites section:

Source address: </^[^.]+$|\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|woff2|ttf|map|json|webp)$)([^.]+$)/>
Target address: /
Type: 200 (Rewrite)

Unfortunately, this doesn't work for me, I am redirecting www to non-www while trying to keep the query string.

this solution works for me
the whole rewrite and redirection configuration as below
[
    {
        "source": "/<*>",
        "target": "/index.html",
        "status": "404-200",
        "condition": null
    },
    {
        "source": "</^[^.]+$|\\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>",
        "target": "/index.html",
        "status": "200",
        "condition": null
    }
]

this solution works for me the whole rewrite and redirection configuration as below
[
    {
        "source": "/<*>",
        "target": "/index.html",
        "status": "404-200",
        "condition": null
    },
    {
        "source": "</^[^.]+$|\\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>",
        "target": "/index.html",
        "status": "200",
        "condition": null
    }
]

This is so close to working for me but I lose my custom font when I have this rule :(

@ChoiYongWon Where does that JSON go? I cant find any docs on specifying the redirect rules outside of the amplify console web UI. I would prefer to specify this in code rather than the horrible AWS UI

It's 2024 and the issue is still there...

@trandaison could you explain what you mean by the trailing slash not working?

@swaminator Sorry for the confusion.
In my case, the root cause was the cloudfront was not forwarding the query string to the amplify. So adding the traling slash was not working. The problem was not on the amplify itself.

Hello everyone -- this issue has been resolved! Now redirects will preserve the query parameter passed to it. Please let me know if you see the correct behavior. @trandaison @dev-sym @iyunusov

@mauerbac, is it required to declare all the query parameters to it to keep the query parameters in the URL? For example, UTM parameters:
/some-page?utm_content=foo&utm_medium=bar
/some-page/?utm_content=foo&utm_medium=bar
Should we declare variables in all redirects to preserve them, or is this fix still pending deployment?


Terminal command netlify dev --live generating broken links

There seems to be an issue with generating links using netlify dev --live. It sometimes output the link as "netllify" or "netlifyy" as seen in the image attached.
I search through my entire projected to see if i have mispelled netlify and everything seems to be find. Spend quite sometime pointlessly debugging just to notice this in the end.

Hi! This is a super interesting bug 😲 Is there some specific thing you can do to reproduce this, or does this show up randomly? Also, is it only the rendering that's broken? Or are your functions also available under the misspelled endpoint?

I am on cli 8.16.1
Reproducing the issue:
First try:

Opened the project in VScode
Netlify build in terminal
Netlify dev --live in terminal
-> Works as expected.

Second try:

Again Netlify dev --live
-> Works as expected

Third try:

I split my screen in two windows. [ half google chrome, other half vscode]
Netlify build in terminal
Netlify dev --live
-> Issue reproduced!

"is it only the rendering that's broken? Or are your functions also available under the misspelled endpoint?"
-> Functions works as expected when I manually correct the spelling mistakes in the links.

Wow, what a riddle! This is interesting :D
What stands out to me is that in the first screenshot you share, the duplicated letter is always the last one before it wraps around to the next line. Could you try playing around with the terminal width to see if that's true always?
It kind of looks like a rendering bug in the terminal. I see you're on windows, what terminal is this (VS-Code builtin terminal/powershell/cmd.exe/something else)?

@jackiewmacharia I see you worked on https://github.com/netlify/cli/issues/4311, do you have an idea what might be causing this?

Trying out different VScode width

Width 1300x852
->Issue with links persists

Width 1530x943
-> No issue with links. Even after resizing window!

It seems that the issue occurs when there is a line break upon generating the link in correlation with the terminal width size.
what terminal is this (VS-Code builtin terminal/powershell/cmd.exe/something else)?
-> I am on VScode builtin terminal.
Version: 1.67.2 (user setup)
Date: 2022-05-17T18:15:52.058Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621

Marking this as stale as it is several years old. Please feel free to reopen if you are still having issues.


ASP Version

It was not possible to find any compatible framework version
The framework 'Microsoft.AspNetCore.App', version '2.1.1' was not found.

The following frameworks were found:
3.1.7 at [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]

You can resolve the problem by installing the specified framework and/or SDK.
The specified framework can be found at:

https://aka.ms/dotnet-core-applaunch?framework=Microsoft.AspNetCore.App&framework_version=2.1.1&arch=x64&rid=win10-x64
The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.
The program '[2604] customerkeystore.dll' has exited with code -2147450730 (0x80008096).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 484b1a6d-dfd0-1da6-5405-7826ed4c088f
Version Independent ID: 6e0ba9d2-aaa6-528a-daab-0e75c80f7135
Content: Double Key Encryption (DKE) - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/double-key-encryption.md
Service: information-protection
GitHub Login: @KCCross
Microsoft Alias: krowley

@timkittelberger-sits Thank you for your feedback. The prerequisite is to install .NET Core 3.1 SDK. Are you having trouble installing that? Could you please elaborate more on which part of the document needs modification?
Thanks
Sri

@msbemba: Thx for the reply. The error is coming if I try to open the root page localhost:5001 but if I open the key website it is showing the key so maybe the error is not relevant. The error message look like some of the commands need the old net core libs. I installed the 3.1 SDK and I will test further.

@timkittelberger-sits Thank you for your feedback. You are correct as this required only 3.1SDK. If that doesn't work I'd recommend you contact our support team via the need help button on the admin center.
In case you would like to make some modifications to the document post troubleshooting, let us know.
@yogkumgit There are no changes required in the document and the issue can be closed.
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @timkittelberger-sits Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


@babel/parser	7.10.0

Type: Missing
Summary:
@babel/parser	7.10.0
Details:
Harvested license file is MIT
Resolution:
Harvested json file also indicates license is MIT
Affected definitions:

parser 7.10.0

Closing - license is already declared as MIT.


adding url shortner django web app

created a web app in django for url shortner.

Also check out my other Hacktoberfest repos.

Sure, will do.


edgeql: Update SDL syntax allowing setting fields on indexes.

The index in SDL now allows to set origexpr field explicitly, just
as DDL.

This is one of the changes that I stumbled upon when dealing with SDL. It's nice and self-contained, so I factored it out.
I'm not sure if we consider SET origexpr part of the interface that's supposed to be exposed to the user, so I didn't update the documentation. Let me know if I need to do that, though.

I'm not sure if we consider SET origexpr part of the interface that's supposed to be exposed to the user

Um. Now I'm having second thoughts about this change.  Since we're discarding the usual session module aliases when processing the SDL declarations, origexpr should really be used to render the on (<origexpr>) part.

Isn't that beside the point? The question ultimately is whether it's legal to set "origexpr" in SDL the same way as DDL. And if not, why not? Basically, what makes it valid to set "origexpr" in DDL, but invalid in all cases for SDL?
Incidentally, I should probably come up with a test case that breaks "origexpr" in some horrible way in DDL. Like mismatching the current module and the module of the declared type (and index).

Also, SET origexpr was broken in DDL because it failed to override the "expr" value in introspection queries, so that got fixed here as well.

Isn't that beside the point? The question ultimately is whether it's legal to set "origexpr" in SDL the same way as DDL.

DDL uses the session module aliases, and SDL doesn't.  The whole point of expression rewrite that mangles the original expression in the first place is to record the current module alias. This is not a problem in SDL.

Also, origexpr in DDL exists only for the benefit of introspection and reproducible dumps.  It does not make sense at all as a user-facing feature.

Regarding user-facing feature, see my comment about DESCRIBE AS DDL. It currently produces the fully-disambiguated expression and a SET origexpr to compensate for this. So unless we come up with some clever way of avoiding that, the "origexpr" has to be available to the user on some level in DDL at least.

DDL uses the session module aliases, and SDL doesn't. The whole point of expression rewrite that mangles the original expression in the first place is to record the current module alias.

Fair enough, it may be unnecessary feature in SDL, but give me a little time to see if I can come up with some odd use-case that needs it.


iOS 17 display bottom sheet below tab bar

With iOS 17, the bottom sheet presented under tab bar and not like above tab bar.

@Madara2hor  Yeah just presented with tab bar controller

@Madara2hor  Yeah just presented with tab bar controller

So u just hide tab bar or what? In my case I can't just hide it

would you please consider updating the version, so we can use this? :)


Client <-> Server <-> Python Thread -- IO/DB/FS discussion

Discuss

What information should be given from which to which
What should be generated inside the module
What should be stored in what format. How will the directory/path organized
etc.

Server <-> Python Thread

train.py

INPUT

uuid (Every other necessary information will be under the directory named with the uuid)

train config .json

NN type and config

OUTPUT

training information

epoch
loss
evaluation win rate
elapsed time

game.py
human_play.py

일단

Train Output은 uuid dir에 파일을 하나 만들어두고 저장해도 될 것 같음
train config랑 nn configuration파일이랑 별개의 json으로 받는건 어떨까? 모델 생성시에 model.json이 생기고 유저가 hyperparameter 이용해서 train 시작하면 그때 train.json이 생겨서 그 두개로 트레이닝 하는 방식이 더 나을거같아서 (train시작과 model 생성이 별개이니깐)

executing the following command in /Server/ will copy the AlphaZero codes into the ml folder, while preserving tensorboard runs data.
rm -rf ../AlphaZero_Gomoku/runs ; cp -r ./src/ml/AlphaZero_Gomku/runs/ ../AlphaZero_Gomoku/runs ; rm -rf ./src/ml/AlphaZero_Gomoku ; sudo cp -r ../AlphaZero_Gomoku/ ./src/ml/AlphaZero_Gomoku

Train related input and outputs are all contained in
/Server/src/ml/models/{uuid}
ㄴtrain.json     INPUT     (contains hyperparameters and test parameters)
ㄴmodel.json  INPUT     (contains layer information)
ㄴoutput.json OUTPUT  (contains train progression information)
ㄴbest.model, curr.model
Battle configuration (INPUT) is stored at
/Server/src/ml/AlphaZero_Gomoku/data
Battle results (OUTPUT) are stored as
/Server/src/ml/battle_records/{timestamp}-{uuid1}-{uuid2}.json (contains array of [{start player}, {moves}, and {winner}])
Play configuraton (INPUT) is also stored at
/Server/src/ml/AlphaZero_Gomoku/data

The inconsistency is the Battle and Play's input .json are inside AlphaZero_Gomoku while all the other train related or other outputs are outside of it.
If you think it's better to fix this, let me know asap without hesitation. I think I won't be sleeping until at least 3 a.m. today for other reason. So no need to hold back.


HBASE-24827 BackPort HBASE-11554 Remove Reusable poolmap Rpc client type.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 39s
the patch passed

+1 :green_heart:
compile
0m 29s
the patch passed

+1 :green_heart:
javac
0m 29s
the patch passed

+1 :green_heart:
shadedjars
6m 25s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 25s
hbase-client in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 21s
hbase-client in the patch passed.

27m 37s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2208

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f46cb3701513 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c39cad220d

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/testReport/

Max. process+thread count
204 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 46s
master passed

+1 :green_heart:
checkstyle
0m 26s
master passed

+1 :green_heart:
spotbugs
1m  0s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 28s
the patch passed

-0 :warning:
checkstyle
0m 26s
hbase-client: The patch generated 1 new + 6 unchanged - 2 fixed = 7 total (was 8)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
11m 30s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
1m 12s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

29m 57s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2208

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux f6f6d2e28d30 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c39cad220d

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-client.txt

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2208/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

the above two commits corrected the commit metadata to include a jira id at the start of the subject and to put in the original author in addition to the co-authored-by.

Thanks @busbey for amend


add usercache package

Used by kube-apiserver and openshift-apiserver. Seems small and contained.
/cc @deads2k

/hold
The only actual usage of this is now in the kube-apiserver.  Remove the reference in openshfit-apiserver because that's a stale way to wire to an informer we don't use.


Ripple button effect

Description
Added ripple button effect html and css files. The ripple effect is called when the button is clicked, it gives users the confirmation that the button has been clicked with a smooth and beautiful animation.
No dependencies.
Fixes #116

feature add

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

Explain the Testing instructions
It has been manually tested. To test run the html file in any browser.
Test Configuration:

Operating system: any
Version: any latest version, done in Windows10
Text-editors used: VS Code

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@arpit456jain u can merge it


[Release] sdk/resourcemanager/containerservicefleet/armcontainerservicefleet/0.1.0

https://github.com/Azure/sdk-release-request/issues/4173

/azp run go - armcontainerservicefleet - ci

/check-enforcer override


Create Function with Types crashes when argument is an array

Describe the bug
When using the "Create function" (with types) action on a function that takes an array the action is not provided as a code fix. If I execute it via the command palette I receive an error:
// hocuspocus.ts
function bla() {
	const c: number[] = [1, 2, 3];
	doSomething(c);
}

Select doSomething and perform the action ->
Something went wrong: Error: Cannot find module 'typescript'
Require stack:
- /home/tobias/.vscode/extensions/nicoespeon.hocus-pocus-1.4.0/out/extension.js
- /usr/share/code/resources/app/out/vs/loader.js
- /usr/share/code/resources/app/out/bootstrap-amd.js
- /usr/share/code/resources/app/out/bootstrap-fork.js

How to reproduce
Just copy the above code into a .ts file and perform the action on doSomething.
Expected behavior
It should generate the function with the correct param type, in this case number[].
Additional information

Version of the extension impacted: v1.4.0

Here's my installed TS versions if it helps:
# TS not installed globally
tobias@tobias-Precision-3541:~/git/lofino-backend$ npm ls -g | grep typescript
│ │ │ │   ├─┬<EMAIL_ADDRESS>│ │ │ │   │ └─┬<EMAIL_ADDRESS>tobias@tobias-Precision-3541:~/git/lofino-backend$ npm ls | grep typescript
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

Weird, "typescript" is part of the dependencies. Also, it worked during debug. I didn't tested the compiled version, maybe the issue lies in prod bundle 🤔
Thanks for reporting!

FYI I'm also running into this

Hey, thanks for reporting but it's been a while since I updated this extension and I'm not planning to do this in the foreseeable future. I'm archiving the extension 👍


Space application supporter can get and list security groups

Allowed access:

GET /v3/security_groups/:guid - Can see globally–enabled security
groups or groups associated with a space they can see
GET /v3/security_groups - Can see globally–enabled security groups or
groups associated with a space they can see
GET /v3/spaces/:guid/running_security_groups
GET /v3/spaces/:guid/staging_security_groups

Closes #2230
Co-authored-by: Matthew Kocher<EMAIL_ADDRESS>Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:

An explanation of the use cases your change solves

Links to any other associated PRs

[X] I have reviewed the contributing guide

[X] I have viewed, signed, and submitted the Contributor License Agreement

[X] I have made this pull request to the main branch

[X] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

I made a commit to update the name of the role in this PR, as it has been changed on the main branch. It looks like the EasyCLA check is now passing, just waiting to hear back on the test removal before merging this PR in
cc: @mkocher @mariash


ARROW-378: Python: Respect timezone on conversion of Pandas datetime columns

arrow is now pandas datetime timezone aware

I left a comment on https://issues.apache.org/jira/browse/ARROW-378

@ahnj can you rebase on the the lastest master? this is based on a commit from 10 days ago https://github.com/ahnj/arrow/commits/timestamp-aware

rebased with the latest master.


merging rows generating weird report with multiple rows after the merged rows.

Environment
Carbone SDK Version: Carbone 1.0.0
Node Version: Node 16.0.0
Steps to reproduce

Have multiple rows
Merge rows of first column & remaining rows are nested value of first-row value.

Screenshots
This is the template.

Generated report:

Hope it's understandable.

Already answered but here is the solution for future persons coming on the thread.
Carbone can't keep a single merged column when it is mixed with a loop of rows, the column will be transformed as a row on the generated report. However it exists a solution, it is to create a table inside a table, such as:

It is possible to remove the margin space between the inner table and the cell, follow these instructions for MS Word:
0. Right-click on the table > properties

Select the tab "Table"
Click on the "Options..." button
Set the left and right margin at zero
Save

Then render the report with Carbone and the column will not be transformed or changed, voilà 🎉

Already answered but here is the solution for future persons coming on the thread.
Carbone can't keep a single merged column when it is mixed with a loop of rows, the column will be transformed as a row on the generated report. However it exists a solution, it is to create a table inside a table, such as:

It is possible to remove the margin space between the inner table and the cell, follow these instructions for MS Word:

Right-click on the table > properties
Select the tab "Table"
Click on the "Options..." button
Set the left and right margin at zero
Save

Then render the report with Carbone and the column will not be transformed or changed, voilà 🎉

Thank you for your solution to the gaping issue. However, I've tried in Ms. Word 2013 for left & right gaping. Unfortunately, it's not working in any of the editors I've used. And there's at least a gap in the inner table. I don't know why. Maybe I'm doing it in the wrong way. Can you please look into it. Thank you


web-animation.min.js

how i download the web-animation.min.js file,
please send me a link where i download the js folder.

It's on the master branch: https://github.com/web-animations/web-animations-js/tree/master


All run-related working files should go in the rundir unless otherwise configured

At the moment, run-related working files appear in various places, including in the hidden directories .scripts and .ipp_controller.
These should all go in the relevant rundir, when that directory is available.
At present, I'm finding it confusing to find relevant files: both because I have to remember there are several places to look, and because many of the automatically named files do not correlate easily with parsl runs that happen close in time/simultaneously.

Agreed!
Related to #442.

If it's useful, here is an example of a Config that gets (almost) everything under a working directory, wd. The relevant overrides are called out. The folder .ipython remains in $HOME and an empty directory $HOME/parsl_scripts is still created.
The code below uses local modifications to work around an issue I reported here and a launcher I have submitted a PR for here.
blocks = 2
nodes = 2
ppn = 32

wd = os.getenv("HOME") + '/hello_parsl/'
os.makedirs(wd, exist_ok = True)

ipp_config = Config(
    run_dir = wd, # Override 1
    retries = 0,
    executors = [
        IPyParallelExecutor(
            label="IPPHello",
            engine_dir = wd, #Override 2
            engine_file = wd + '/ipcontroller-engine.json', #Override 3
            provider = TorqueProvider(
                launcher = MpiExecLauncher(),
                init_blocks = blocks,
                max_blocks = blocks,
                min_blocks = 0,
                nodes_per_block = nodes,
                tasks_per_node = ppn,
                walltime = "00:02:00",
                script_dir = wd + 'provider_scripts', # Override 4
                channel = SSHChannel(hostname='hostname',
                                     username=os.getenv("USER"),
                                     script_dir = wd + '/channel_scripts'), # Override 5
                overrides = f'''
# Override 6
cd {wd}
                '''
            )
        )
    ]
)

parsl.load(ipp_config)


Can't push data to eeprom

Describe the bug
I'm correctly connect with eeprom but when i'm trying to push data into it it doesn't work.
To Reproduce
I think there's problem with eeUAWrite function in ftd2xx.py file where casting function works wrong
Expected behavior
Correctly casting types and pushing data to eeprom
Logs
File "/usr/local/lib/python3.9/dist-packages/ftd2xx/ftd2xx.py", line 577, in eeUAWrite     call_ft(_ft.FT_EE_UAWrite, self.handle, buf, len(data))   File "/usr/local/lib/python3.9/dist-packages/ftd2xx/ftd2xx.py", line 131, in call_ft     status = function(*args) ctypes.ArgumentError: argument 2: <class 'TypeError'>: expected LP_c_ubyte instance instead of c_char_Array_97
Desktop (please complete the following information):

OS: Linux
OS Version: Debian 11 Bullseye
Python Version: 3.9.2
FTDI driver version: newest FTD2XX

Additional context
I found a solution. It works correctly.
Original code look like:
def eeUAWrite(self, data: bytes) -> None:         """Write data to the EEPROM user area. data must be a string with         appropriate byte values"""         buf = c.create_string_buffer(data)         call_ft(_ft.FT_EE_UAWrite, self.handle, ptr, len(data))
I change second line as below:
def eeUAWrite(self, data: bytes) -> None:         """Write data to the EEPROM user area. data must be a string with         appropriate byte values"""         ptr = c.cast(c.c_char_p(data),c.POINTER(c.c_ubyte))         call_ft(_ft.FT_EE_UAWrite, self.handle, ptr, len(data))

@VadalTheGod Looks like you're right. Could you try if the following works:
def eeUAWrite(self, data: bytes) -> None:
    """Write data to the EEPROM user area. data must be a bytes object with
    appropriate byte values"""
    buf = (c.c_ubyte*len(data)).from_buffer_copy(data)
    call_ft(_ft.FT_EE_UAWrite, self.handle, buf, len(data))

Sorry, that i haven't answered for a long time. I checked your code and it works correctly.


[Java 11] Bump to upcoming fixed JAXB API plugin

JENKINS-55202
2.2.11 had a dependency using systemPath, which was causing issues on Java 11.
Using here a timestamped SNAPSHOT from https://github.com/jenkinsci/jaxb-plugin/pull/6
@rpionke
cc @jenkinsci/java11-support

@batmat sorry for the delay, i was on vacation.
I installed the latest plugin build from ci.jenkins.io in the jenkins/jenkins:jdk11 docker image and created a test job with the following result:
Started by user admin
Building in workspace /var/jenkins_home/workspace/asdasd
[PERFSIG] starting session recording ...
ERROR: Build step failed with exception
javax.xml.bind.JAXBException: Implementation of JAXB-API has not been found on module path or classpath.
 - with linked exception:
[java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory]
	at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:278)
	at javax.xml.bind.ContextFinder.find(ContextFinder.java:421)
	at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:721)
	at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:662)
	at retrofit2.converter.jaxb.JaxbConverterFactory.contextForType(JaxbConverterFactory.java:74)
	at retrofit2.converter.jaxb.JaxbConverterFactory.responseBodyConverter(JaxbConverterFactory.java:67)
	at retrofit2.Retrofit.nextResponseBodyConverter(Retrofit.java:328)
	at retrofit2.Retrofit.responseBodyConverter(Retrofit.java:311)
	at retrofit2.HttpServiceMethod.createResponseConverter(HttpServiceMethod.java:68)
	at retrofit2.HttpServiceMethod.parseAnnotations(HttpServiceMethod.java:46)
	at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:36)
	at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:168)
	at retrofit2.Retrofit$1.invoke(Retrofit.java:147)
	at com.sun.proxy.$Proxy79.getServerLicense(Unknown Source)
	at de.tsystems.mms.apm.performancesignature.dynatrace.rest.DTServerConnection.getServerLicense(DTServerConnection.java:253)
	at de.tsystems.mms.apm.performancesignature.dynatrace.PerfSigStartRecording.perform(PerfSigStartRecording.java:89)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
	at hudson.model.Build$BuildExecution.build(Build.java:206)
	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
	at hudson.model.Run.execute(Run.java:1816)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)
Caused by: java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
	at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
	at javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:122)
	at javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:155)
	at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:276)
	... 25 more
Caused: java.lang.IllegalArgumentException
	at retrofit2.converter.jaxb.JaxbConverterFactory.contextForType(JaxbConverterFactory.java:76)
	at retrofit2.converter.jaxb.JaxbConverterFactory.responseBodyConverter(JaxbConverterFactory.java:67)
	at retrofit2.Retrofit.nextResponseBodyConverter(Retrofit.java:328)
	at retrofit2.Retrofit.responseBodyConverter(Retrofit.java:311)
	at retrofit2.HttpServiceMethod.createResponseConverter(HttpServiceMethod.java:68)
Caused: java.lang.IllegalArgumentException: Unable to create converter for class de.tsystems.mms.apm.performancesignature.dynatrace.rest.xml.model.LicenseInformation
    for method CustomXMLApi.getServerLicense
	at retrofit2.Utils.methodError(Utils.java:52)
	at retrofit2.HttpServiceMethod.createResponseConverter(HttpServiceMethod.java:70)
	at retrofit2.HttpServiceMethod.parseAnnotations(HttpServiceMethod.java:46)
	at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:36)
	at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:168)
	at retrofit2.Retrofit$1.invoke(Retrofit.java:147)
	at com.sun.proxy.$Proxy79.getServerLicense(Unknown Source)
	at de.tsystems.mms.apm.performancesignature.dynatrace.rest.DTServerConnection.getServerLicense(DTServerConnection.java:253)
Caused: de.tsystems.mms.apm.performancesignature.dynatrace.rest.xml.CommandExecutionException: error while querying server license: Unable to create converter for class de.tsystems.mms.apm.performancesignature.dynatrace.rest.xml.model.LicenseInformation
    for method CustomXMLApi.getServerLicense
	at de.tsystems.mms.apm.performancesignature.dynatrace.rest.DTServerConnection.getServerLicense(DTServerConnection.java:256)
	at de.tsystems.mms.apm.performancesignature.dynatrace.PerfSigStartRecording.perform(PerfSigStartRecording.java:89)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
	at hudson.model.Build$BuildExecution.build(Build.java:206)
	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
	at hudson.model.Run.execute(Run.java:1816)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)
Build step 'Start Dynatrace session recording' marked build as failure
Finished: FAILURE

@rpionke can you please rather test with jenkins/jenkins:2.164-jdk11 and/or confirm which Jenkins version was in use?
Because given how docker works. If by chance, you already had pulled jenkins/jenkins:jdk11 previously and just docker runed it, then it would not have forced a new pull to get the latest.
And that error is expected on any version < 2.164.
Thanks!

@batmat i tested it with the jenkins/jenkins:2.164-jdk11 image, but the result stays the same :/

Urgh, then that is no good indeed. Can you please file a JIRA with a clear reproducer please (esp. taking in account we might not have an access to some performance-signature-dynatrace related infra, or tooling, so if this can done without it's way better)?
Make sure to label it with java-11 at least, so that it shows up under the triage filter https://issues.jenkins-ci.org/browse/JENKINS-51965?filter=19376.

@rpionke eager to read the reproducer if you can file the JIRA report, but by chance how did you install your plugin? Did you do through the Plugin Manager, or did you put the HPI manually for instance?

@batmat I create a reproducer and a follow-up ticket: https://issues.jenkins-ci.org/browse/JENKINS-56265
I installed the plugins from ci.jenkins.io manually.

IIUC you installed the hpi either by dumping directly the plugins to the
disk, or using the advanced mode in the plugin manager?
If so then the failure is expected. The jaxb plug-in is a detached plugin,
aka an implicit dependency, and is only installed when installing a plug-in
through the normal plugin installation flow.
Can you both try possibly installing your plug-in in this normal flow, and
maybe also trying fixing the current seen failure by installing the jaxb
plugin too? (Which shouldn't be needed in general)
Thanks
Le lun. 25 févr. 2019 à 15:32, Raphael Pionke<EMAIL_ADDRESS>a
écrit :

@batmat https://github.com/batmat I create a reproducer and a follow-up
ticket: https://issues.jenkins-ci.org/browse/JENKINS-56265
I installed the plugins from ci.jenkins.io manually.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jenkinsci/performance-signature-dynatrace-plugin/pull/7#issuecomment-467032581,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANqbRihcj_KWRnryNtNeDnTAIf9BZjaks5vQ_PzgaJpZM4acOPw
.

@batmat Yeah i know about the dependency management. Required and optional dependencies are also getting installed by manual upload. I used a clean Jenkins instance from the Docker image without any plugins and uploaded both Performance Signature plugins. The dependencies, the jaxb plugin too, got installed so i'm wondering what i'm missing cause the JUnit test is successful with java 11 but not the manual one :/
I'm always checking if the jaxb plugin is installed and i'm restarting the instance to proof that everything got set up.


Tutorial on using the cheat on linux

The header in readme literally says that the cheat is available for windows and linux systems, but there is no tutorial on how to build or inject it. Should there be any?

#3808 Check that

thx!


Create elizabethHelloWorld in JS

:warning: This is a Pull Request Template :warning:

Checkout all the things you've done by placing an x within the square braces below.

Proposed Changes

[x] I've read the CODE OF CONDUCT and abide to it.
[x] I've read the CONTRIBUTING.md
[x] I've forked the repository.
[x] I've created a branch and made my changes in it.
[x] I understand opening a PULL REQUEST doesn't mean it will be merged for sure.

We've already got one for you in #940 ... thanks!


hevc_qsv-decoder done: 0 frames, 1497 decoder errors

Current Behavior
Im running handbrake in docker and trying to decode these files I used to decode on nvenc. I am using an Intel 12900H with IrisXE iGPU. My other apps that need a gpu work fine by passing the device. The handbrake log detects the GPU and the right encoder. But when it runs it fails on all the video frames resulting in a small "successful" encode but only containing audio:
Expected Behavior
A successful job complated with video as well as audio
Steps To Reproduce
I am running the latest docker container on Ubuntu 22.04 with iGPU pass through. Other containers can see the device that is passed through, via 12900H IrisXE iGPU. The drivers are loaded correctly and it seems detected by handbrake jobs. It takes a 250MB video file and creates a 500K video fail, that only contains the audio.
Run the job and use the qsv encoder 4k and try to proceess a video.
Environment

OS: Ubuntu
OS version: 22.04
CPU: 12900H
Docker version: Latest
Device model: ?
Browser/OS: Chrome

Container creation
handbrake:
image: jlesage/handbrake:nightly-latest (trying latest, same prob)
container_name: handbrake
environment:
- USER_ID=6969
- GROUP_ID=6969
- TZ=America/Los_Angeles
- AUTOMATED_CONVERSION_PRESET=Hardware/H.265 QSV 2160p 4K
- AUTOMATED_CONVERSION_FORMAT=mp4
- AUTOMATED_CONVERSION_OUTPUT_DIR=/output
Container log
[13:55:52] qsv_enc_init: using 'hardware (1) via VAAPI' implementation, API: 2.9

[13:55:52] work: average encoding speed for job is 0.000000 fps

[13:55:53] vfr: 0 frames output, 0 dropped

[13:55:53] vfr: lost time: 0 (0 frames)

[13:55:53] vfr: gained time: 0 (0 frames) (0 not accounted for)

[13:55:53] pcm_mulaw-decoder done: 1504 frames, 0 decoder errors

[13:55:53] hevc_qsv-decoder done: 0 frames, 1497 decoder errors

[13:55:53] sync: got 0 frames, 1504 expected

How can i see the logs for the decoder errors?

Container inspect
NA

Anything else?
NA

You say that you passed the iGPU to the container but i don't see the device : /dev/dri:/dev/dri envvar. How did you setup the passthrough ?


Flutter version 3.16 and above issue resolved

Issue #79 resolved. Now works for flutter version 3.16.0 and above. Updated image_picker_plus version to 0.5.10
@AhmedAbdoElhawary

Hello Sir @AhmedAbdoElhawary, is there any chance this PR would be merged? I am encountering the same bug and this PR solves it.
Thank you!

Hello Ye Lwin Oo,
First of all, I apologize for this long delay, this year I served in my
military services, and it's been a rough year.
I appreciate your contribution and to be honest I will not apply to the
test until November or December.
I will keep you updated,
Thank you.
On Fri, Oct 4, 2024 at 1:21 PM John Patrick Prieto @.***>
wrote:

Hello Sir @AhmedAbdoElhawary https://github.com/AhmedAbdoElhawary, is
there any chance this PR would be merged? I am encountering the same bug
and this PR solves it.
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/AhmedAbdoElhawary/image_picker_plus/pull/82#issuecomment-2393366671,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVG3I4WYYYEU2OBL3NS6THLZZZT2DAVCNFSM6AAAAABPLSRGF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJTGM3DMNRXGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Increase container width

Matches Github's container width of 980px.

Thanks @takezoe. Would you be able to take a look at PR #849 ? All that does is basically make it easier to click the buttons.

OK. I will check it.


#isEqualTo(Object other) takes invalid shortcut

Summary
Before PR #1767 (specifically commit 76762a3664b3af2101d580355a05c6f0b3aa46cc) an object x was not automatically considered equal to itself when using BDDAssertions.assertThat(x).isEqualTo(x);
By switching from
    if (o1 == null) {
      return o2 == null;
    }
    if (o1.equals(o2)) {
      return true;
    }

to calling java.util.Objects.deepEquals(o1, o2); we end up with
    if (o1 == o2)
        return true;
    else if (o1 == null || o2 == null)
        return false;
    else
        // defaults to o1.equals(o2) if type is not an array
        return Arrays.deepEquals0(o1, 2);

This means when testing a custom equals implementation of a class, BDDAssertions doesn't actually do what we expect it to do and we may oversee bugs in the application code.
Example
// fails with assertj 3.16.1; succeeds with 3.13.2; probably broken since 13.15.1
@Test
void testEquals() {
	Object x = new Object() {
		@Override
		public boolean equals(Object other) {
			return false;
		}
	};
	BDDAssertions.assertThat(x).isNotEqualTo(x);
}

Thanks for the detailed explanation here and in #1948, I will look into it.

Before PR #1767 (specifically commit 76762a3664b3af2101d580355a05c6f0b3aa46cc) an object x was not automatically considered equal to itself when using BDDAssertions.assertThat(x).isEqualTo(x);

Right and I think the previous behavior was wrong because it was violating the contract of equals, where it is mentioned:

for any non-null reference value x, x.equals(x) should return true

The custom equals in the example is also violating that requirement.
Honestly, I would not restore the previous behavior. @joel-costigliola what do you think?

I do agree with @scordio, it is very to argue that given o1 == o2 then o1.equals(o2) could return false.
I don't think the previous behaviour intended to allow that (might date from the Fest Assert library AssertJ is based upon).
If you want to have total control over isEqualTo, you can register a comparator:
// fails as isEqualTo checks is: comparator.compare(actual, other) == 0
assertThat(frodo).usingComparator((o1, o2) -> 1)
                 .isEqualTo(frodo);

Anyway @nioertel thanks for the detailed issue, appreciated!
I'm curious what was the exact use case that led you to raise this issue? Maybe there is something we can do.

I disagree.
AssertJ should not make any assumptions about the code under test regarding compliance with any contracts from the JDK docs. It should give the developer a chance to test whether the code under test fulfils these contracts.
Until this change, assertThat(a).isEqualTo(b) for single objects behaved exactly like a.equals(b), except that it added null-safety on top. In my opinion this was the correct way, as explained above.
Niels

It should give the developer a chance to test whether the code under test fulfils these contracts.

I missed this point in the issue description. Do I understand correctly that you would like to use isEqualTo to test if the equals implementation fulfills the contract? I would suggest to use EqualsVerifier for this purpose. AssertJ might help with that, but supporting equals testing was never the main target.
Anyway, playing a bit more with this topic and the equals implementation above, another way to see the issue is with the following example:
assertThat(x.equals(x)).isFalse(); // succeeds
assertThat(x).isNotEqualTo(x); // fails

More specifically:
x.equals(x); // false
java.util.Objects.equals(x, x); // true
java.util.Objects.deepEquals(x, x); // true

The shortcut is in the java.util.Objects#equals implementation:
    public static boolean equals(Object a, Object b) {
        return (a == b) || (a != null && a.equals(b));
    }

which states in the javadoc:

Returns true if the arguments are equal to each other and false otherwise. Consequently, if both arguments are null, true is returned and if exactly one argument is null, false is returned. Otherwise, equality is determined by using the equals method of the first argument.

but the sentence in bold is actually in contrast with the result above.
Same for deepEquals. We could argue that this is a JDK issue.
I am still not sure how to proceed.

There is no obvious answer here, either AssertJ isEqualTo fully sticks to equals semantics and would not perform null check or reference checks or it performs them and the array comparison ones.
I would keep the current behaviour for now until we are presented a real life use case or more arguments in favor of the old behaviour.
The current behaviour does not prevent alternatives approaches like EqualVerifier or a simple assertThat(x.equals(x)).isFalse();
Let's leave that issue open for the sake of discussion, happy to reevaluate our position in light of new arguments.

This topic has been also discussed in JDK-8196069.

Hello maintainers.
Summary
Breaking change detected in code coverage. Self-reference check in equals() not recognized by isEqualTo(..) which leads to less code coverage.
Works with AssertJ 3.14.0
Not working with AssertJ 3.18.1
Example
class EqualToTest {

    @Test
    void test() {
        final var myObj = new MyObject();
        assertThat(myObj).isEqualTo(myObj);
    }

    private static class MyObject {
        @Override
        public boolean equals(Object obj) {
            // simplified check for demo purposes
            return this == obj;
        }
    }

}

Example with AssertJ 3.14:

Example with AssertJ 3.18.1:

Hope that helps and hope it will be fixed soon and there won't be a forced need for a workaround using an extra dependency like EqualsVerifier as AssertJ should recover the most important parts OOTB 👍

Hello maintainers.
Summary
Breaking change detected in code coverage. Self-reference check in equals() not recognized by isEqualTo(..) which leads to less code coverage.
Works with AssertJ 3.14.0
Not working with AssertJ 3.18.1
Example
class EqualToTest {

    @Test
    void test() {
        final var myObj = new MyObject();
        assertThat(myObj).isEqualTo(myObj);
    }

    private static class MyObject {
        @Override
        public boolean equals(Object obj) {
            // simplified check for demo purposes
            return this == obj;
        }
    }

}

Example with AssertJ 3.14:

Example with AssertJ 3.18.1:

Hope that helps and hope it will be fixed soon and there won't be a forced need for a workaround using an extra dependency like EqualsVerifier as AssertJ should recover the most important parts OOTB 👍

@pitschr AssertJ isEqualTo is not designed to provide full coverage for custom equals implementations. We usually suggest EqualsVerifier to achieve this.

@pitschr AssertJ isEqualTo is not designed to provide full coverage for custom equals implementations. We usually suggest EqualsVerifier to achieve this.

Yeah, EqualsVerifier is a good library. I agree that the EqualsVerifier is superior when we need to check equals and hashCode. But I still think that AssertJ should call the real equals method even if self-reference to avoid unexpected behavior.
The missing coverage through isEqualTo(..) was just accidentally discovered. Now I am in the situation that I am not sure if there might be other methods/scenarios which are "not designed" for AssertJ. Especially when it was covered before.
It is good to have it clarified that this drawback was done consciously. I still hope that AssertJ can be improved in this area in future.

Yeah, EqualsVerifier is a good library. I agree that the EqualsVerifier is superior when we need to check equals and hashCode. But I still think that AssertJ should call the real equals method even if self-reference to avoid unexpected behavior.
The missing coverage through isEqualTo(..) was just accidentally discovered. Now I am in the situation that I am not sure if there might be other methods/scenarios which are "not designed" for AssertJ. Especially when it was covered before.
It is good to have it clarified that this drawback was done consciously. I still hope that AssertJ can be improved in this area in future.

@nioertel @pitschr we evaluated this issue again and decided to address it. Feel free to have a look at #2114.

@nioertel @pitschr we evaluated this issue again and decided to address it. Feel free to have a look at #2114.


unable to launch Spyder, and new version of spyder is not supporting python 2.7

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Unable to launch Spyder for python 2.7 and upgraded or new version of Spyder not supporting python 2.7
What steps reproduce the problem?

Launch Spyder in windows

What is the expected output? What do you see instead?
Spyder application should open
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version: from anaconda2
Python version: 2.7
Qt version:
PyQt version:
Operating System name/version:  Windows 7

Dependencies

PASTE DEPENDENCIES HERE

Please describe step by step how you got this error so we can reproduce it in our side. If you fail to do that, we'll close this issue in a week from now.
Also, please read our
https://github.com/spyder-ide/spyder/wiki/Troubleshooting-Guide-and-FAQ
to see if you are able to fix this problem by following it.

Closing because of lack of response.


Not working with package.reload

metrics == 0.5.0
unix/:/var/run/tarantool/app.control> package.reload()
---
- error: '/.rocks/share/tarantool/metrics/quantile.lua:10: cannot change a protected
    metatable'
...

@TvoroG
Fixed in #149. Fix is already available in scm and will be included in the next release.

Thanks a lot! Will update soon.


allowedVmSizes default values are not correct

As per the title allowedVmSizes are not correct in the template.

Can you please elaborate? Which artifact? Can you provide a sample?


Google books won't get blocked

Hello Again
When i'm using google search a link of google books is showing without the blue text
"Block this site" and cannot be blocked.
Example:
https://www.google.com/search?q=google+books+ancient+egypt&ei=k81fX7DZG8y_gQbIhJuwBA&start=50&sa=N
It's showing before the last result.
Sincerely
Alex

Hello
I forget to mention that issue is on "mobile" layout!
Sincerely
Alex