MTOUCH : warning MT1302: Could not extract the native library

Hey there,
I don't know if this is the correct place to write this,
but I found an anomaly with Firebase (iOS packages) and Xamarin.Build.Download (0.4.11).
Similar Issues
The problem that I meet is similar to these issues:

https://github.com/xamarin/GoogleApisForiOSComponents/issues/144
https://github.com/xamarin/GoogleApisForiOSComponents/issues/158

The problem
If you try to build a project that using the following packages.config:
<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="Microsoft.IdentityModel.Clients.ActiveDirectory" version="3.19.2" targetFramework="xamarinios10" />
  <package id="System.Net.Http" version="4.3.3" targetFramework="xamarinios10" />
  <package id="Xam.Plugin.DeviceInfo" version="3.1.0" targetFramework="xamarinios10" />
  <package id="Xam.Plugins.Settings" version="3.1.1" targetFramework="xamarinios10" />
  <package id="Xamarin.Build.Download" version="0.4.11" targetFramework="xamarinios10" />
  <package id="Xamarin.Firebase.iOS.Analytics" version="<IP_ADDRESS>" targetFramework="xamarinios10" />
  <package id="Xamarin.Firebase.iOS.Core" version="<IP_ADDRESS>" targetFramework="xamarinios10" />
  <package id="Xamarin.Firebase.iOS.InstanceID" version="2.0.8" targetFramework="xamarinios10" />
  <package id="Xamarin.Forms" version="<IP_ADDRESS>0555" targetFramework="xamarinios10" />
</packages>

With this command line:
msbuild /t:Clean,Build,Archive /p:Configuration=Debug iOS/MyProj.iOS.csproj /v:diag

You should get an error like this:
"~/workspace/iOS/MyProj.iOS.csproj" (Clean;Build;Archive target) (1) ->
(_CompileToNative target) ->
  clang : error : no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseCore' [~/workspace/iOS/MyProj.iOS.csproj]
  clang : error : no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseAnalytics' [~/workspace/iOS/MyProj.iOS.csproj]
  clang : error : no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseCoreDiagnostics' [~/workspace/iOS/MyProj.iOS.csproj]
  clang : error : no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseNanoPB' [~/workspace/iOS/MyProj.iOS.csproj]
  clang : error : no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseInstanceID' [~/workspace/iOS/MyProj.iOS.csproj]
  error MT5209 : Native linking error : clang: error: no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseCore' [~/workspace/iOS/MyProj.iOS.csproj]
  error MT5209 : Native linking error : clang: error: no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseAnalytics' [~/workspace/iOS/MyProj.iOS.csproj]
  error MT5209 : Native linking error : clang: error: no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseCoreDiagnostics' [~/workspace/iOS/MyProj.iOS.csproj]
  error MT5209 : Native linking error : clang: error: no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseNanoPB' [~/workspace/iOS/MyProj.iOS.csproj]
  error MT5209 : Native linking error : clang: error: no such file or directory: '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseInstanceID' [~/workspace/iOS/MyProj.iOS.csproj]
  MTOUCH : error MT5202: Native linking failed. Please review the build log. [~/workspace/iOS/MyProj.iOS.csproj]

I did some debug and I found also these warnings messages:
Xamarin.iOS 11.12.0 using framework: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.3.sdk (TaskId:477)
MTOUCH : warning MT1302: Could not extract the native library 'FirebaseCore' from '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseCore'. Please ensure the native library was properly embedded in the managed assembly (if the assembly was built using a binding project, the native library must be included in the project, and its Build Action must be 'ObjcBindingNativeLibrary'). [~/workspace/iOS/MyProj.iOS.csproj]
MTOUCH : warning MT1302: Could not extract the native library 'FirebaseAnalytics' from '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseAnalytics'. Please ensure the native library was properly embedded in the managed assembly (if the assembly was built using a binding project, the native library must be included in the project, and its Build Action must be 'ObjcBindingNativeLibrary'). [~/workspace/iOS/MyProj.iOS.csproj]
MTOUCH : warning MT1302: Could not extract the native library 'FirebaseCoreDiagnostics' from '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseCoreDiagnostics'. Please ensure the native library was properly embedded in the managed assembly (if the assembly was built using a binding project, the native library must be included in the project, and its Build Action must be 'ObjcBindingNativeLibrary'). [~/workspace/iOS/MyProj.iOS.csproj]
MTOUCH : warning MT1302: Could not extract the native library 'FirebaseNanoPB' from '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseNanoPB'. Please ensure the native library was properly embedded in the managed assembly (if the assembly was built using a binding project, the native library must be included in the project, and its Build Action must be 'ObjcBindingNativeLibrary'). [~/workspace/iOS/MyProj.iOS.csproj]
MTOUCH : warning MT1302: Could not extract the native library 'FirebaseInstanceID' from '~/workspace/iOS/obj/iPhone/Debug/mtouch-cache/FirebaseInstanceID'. Please ensure the native library was properly embedded in the managed assembly (if the assembly was built using a binding project, the native library must be included in the project, and its Build Action must be 'ObjcBindingNativeLibrary'). [~/workspace/iOS/MyProj.iOS.csproj]
  Process exited with code 1, command: (TaskId:477)

"Workaround"
Casually, when I was looking for a workaround, I read the dependencies needs to Xamarin.Firebase.iOS.Analytics
So, instead  Xamarin.Build.Download.0.4.11, I tried to using:
  <package id="Xamarin.Build.Download" version="0.4.6" targetFramework="xamarinios10" />

And the build ends with no errors!
Considerations

I'm not sure whether this problem would be a dev or sys error, but downgrading the version of 'Xamarin.Build.Download' worked for me.

In your README.md seems there are no explicit references to specific dependencies and in nuget I see Xamarin.Build.Download (>= 0.4.6): so I guess Xamarin.Firebase.* packages should work also with 0.4.11. If not, I think you should declare this better!

Based on the first 2 points, I don't know if that would be a workaround.

In any case, the WARN messages should be elevated to ERROR messages, because it's impossible to finish the linking phase without those files.

I don't want criticize your project management, but I was trying to do some debug, building my project directly with your source code, and I realized that is impossible go back to that specific version: there aren't tags for previous versions.

Regards,
Luke

Hi I am getting exactly same error mentioned in issue 158.But none of the solutions worked for me.
However I am not using Xamarin Forms but I have created a project in  mvvmcross with .NetStandard 2.0 as my core.Connecting to mac having  Xcode 9 and have pushnotifications enabled in my provisioning profile.Also have enabled push notifications in Entitlements.plist.
One thing I noted in this solution is the  packageconfig does not include CloudMessaging package so is it not required ?
Is there something I need to do with linkerpleaseinclude file ?
I guess the setup would be the same for Firebase  irrespective if it is a XamarinForms ios project or an independent ios project but please correct me if I am wrong.
Will it be possible to share some sample code/project  as well please where firebase is implemented in ios.
Found at below two places though
http://blog.xamarians.com/Blog/2017/9/18/firebase-cloud-messaging
https://qiita.com/yamachu/items/cee6104ac579ea657deb
Thanks,
Santosh

@x21Kenobi @santoshg31  could you please provide a small samples with each of your issues so that we can investigate further.
Thanks in advance

Hi @newky2k,
unfortunately, I can't.
The project is under internal policy rules of the company where I work and now we have resolve with that "workaround".
As I wrote previously, I didn't open this ticket to criticize your project but to leave a trace of the problem we had encountered.
Maybe this was only a case and nobody will encounter it (I hope).
Regards,
Luke

Hi @newky2k,
unfortunately, I can't.
As I wrote previously, I didn't open this ticket to criticize your project but to leave a trace of the problem we had encountered.
Maybe this was only a case and nobody will encounter it (I hope).
Regards,
Luke

Hi @newky2k, sorry even I won't be able to share.
However I have managed to build the solution in a very weird way.

First I upgraded the Cloudmessaging package from <IP_ADDRESS> to 3.0.3 which upgraded the other firebase packages as well. I was able to successfully build where Xamarin.Build.Download version was 0.4.6. However I got a message at the top saying unable uinstall the package
Xamarin.Build.Download 0.4.6 asking to me to restart visual studio.
So after restarting I discovered my Xamarin.Build.Download was upgraded to 0.4.11 and my build failed. So as @x21Kenobi   suggested I downgraded Xamarin.Build.Download to 0.4.6 but it aautomatically downgraded CloudMessaging package to <IP_ADDRESS> and also the subsequent firebase package and then my build was successfull. I have no clue what happened as this was the state i was before I upgraded cloudmessaging to 3.0.3. But atleast  I am now able to successfully build the solution with the below packages.

  <package id="Xamarin.Build.Download" version="0.4.6" targetFramework="xamarinios10" />   <package id="Xamarin.Firebase.iOS.Analytics" version="<IP_ADDRESS>" targetFramework="xamarinios10" />   <package id="Xamarin.Firebase.iOS.CloudMessaging" version="<IP_ADDRESS>" targetFramework="xamarinios10" />   <package id="Xamarin.Firebase.iOS.Core" version="<IP_ADDRESS>" targetFramework="xamarinios10" />   <package id="Xamarin.Firebase.iOS.InstanceID" version="2.0.8" targetFramework="xamarinios10" />
I am not using Xamarin.Forms but have created an application using MVVMCross with  android and ios as UIProjects. I have got the FirebaseBase notification working in android  but I am still searching for a proper setup code for ios as there is no proper documentation like in android for it. Only found the below two links but it seems like I not able to get the firebase token at all.
http://blog.xamarians.com/Blog/2017/9/18/firebase-cloud-messaging
https://qiita.com/yamachu/items/cee6104ac579ea657deb
`Firebase.InstanceID.InstanceId.Notifications.ObserveTokenRefresh((sender, e) =>
{
var newToken = Firebase.InstanceID.InstanceId.SharedInstance.Token;
// if you want to send notification per user, use this token
System.Diagnostics.Debug.WriteLine(newToken);
            //connectFCM();
        });`

The code never comes in this handler.
@x21Kenobi  @newky2k, can you please help what I might be missing here. Are there any samples that I can refer specifically for ios . I am relatively new to mobile development any help would be really appreciated !!
Thanks,
Santosh

Hi @santoshg31
do you the code online on github?
I mean, is open source? If yes, where can I see it?
Regards,
Luke

Hi @x21Kenobi
Sorry I don't have the code on github but here is Appdelegate class which I created referring the above two links. Hope this helps in identifying whats going wrong.
`[Register("AppDelegate")]
public class AppDelegate : MvxApplicationDelegate, IUNUserNotificationCenterDelegate
{
// class-level declarations
    public override UIWindow Window
    {
        get;
        set;
    }

    public CKDatabase PublicDatabase { get; set; }
    public CKDatabase PrivateDatabase { get; set; }

    public override bool FinishedLaunching(UIApplication application, NSDictionary launchOptions)
    {
        /* iCloud  capability start */
        application.RegisterForRemoteNotifications();
        PublicDatabase = CKContainer.DefaultContainer.PublicCloudDatabase;
        PrivateDatabase = CKContainer.DefaultContainer.PrivateCloudDatabase;
        /* iCloud  capability end */

        Window = new UIWindow(UIScreen.MainScreen.Bounds);
        var setup = new Setup(this, Window);

        setup.Initialize();

        var startup = Mvx.Resolve<IMvxAppStart>();
        startup.Start();

        Window.MakeKeyAndVisible();

        // Register your app for remote notifications.
        if (UIDevice.CurrentDevice.CheckSystemVersion(10, 0))
        {
            // iOS 10 or later
            var authOptions = UNAuthorizationOptions.Alert | UNAuthorizationOptions.Badge | UNAuthorizationOptions.Sound;
            UNUserNotificationCenter.Current.RequestAuthorization(authOptions, (granted, error) =>
            {
                //Console.WriteLine(granted);
                //Mvx.Warning("granted");
            });

            UNUserNotificationCenter.Current.Delegate = this;

            //Messaging.SharedInstance.RemoteMessageDelegate = this;
        }
        else
        {
            // iOS 9 or before
            var allNotificationTypes = UIUserNotificationType.Alert | UIUserNotificationType.Badge | UIUserNotificationType.Sound;
            var settings = UIUserNotificationSettings.GetSettingsForTypes(allNotificationTypes, null);
            UIApplication.SharedApplication.RegisterUserNotificationSettings(settings);
        }

        //Firebase.Analytics.App.Configure();
        UIApplication.SharedApplication.RegisterForRemoteNotifications();
        Firebase.InstanceID.InstanceId.Notifications.ObserveTokenRefresh((sender, e) =>
        {
            var newToken = Firebase.InstanceID.InstanceId.SharedInstance.Token;
            // if you want to send notification per user, use this token
            System.Diagnostics.Debug.WriteLine(newToken);

            connectFCM();
        });

        return true;
    }

    private void connectFCM()
    {
        //Messaging.SharedInstance.ShouldEstablishDirectChannel = true;
        Messaging.SharedInstance.Connect((error) =>
        {
            if (error == null)
            {
                Messaging.SharedInstance.Subscribe("/topics/all");
            }
            System.Diagnostics.Debug.WriteLine(error != null ? "error occured" : "connect success");
        });
    }

    //iOS 9 <=, fire when recieve notification foreground
    public override void DidReceiveRemoteNotification(UIApplication application, NSDictionary userInfo, Action<UIBackgroundFetchResult> completionHandler)
    {
        Messaging.SharedInstance.AppDidReceiveMessage(userInfo);

        // Generate custom event
        NSString[] keys = { new NSString("Event_type") };
        NSObject[] values = { new NSString("Recieve_Notification") };
        var parameters = NSDictionary<NSString, NSObject>.FromObjectsAndKeys(keys, values, keys.Length);

        // Send custom event
        Firebase.Analytics.Analytics.LogEvent("CustomEvent", parameters);

        if (application.ApplicationState == UIApplicationState.Active)
        {
            System.Diagnostics.Debug.WriteLine(userInfo);
            var aps_d = userInfo["aps"] as NSDictionary;
            var alert_d = aps_d["alert"] as NSDictionary;
            var body = alert_d["body"] as NSString;
            var title = alert_d["title"] as NSString;
            //debugAlert(title, body);
        }
    }

    // iOS 10, fire when recieve notification foreground
    [Export("userNotificationCenter:willPresentNotification:withCompletionHandler:")]
    public void WillPresentNotification(UNUserNotificationCenter center, UNNotification notification, Action<UNNotificationPresentationOptions> completionHandler)
    {
        var title = notification.Request.Content.Title;
        var body = notification.Request.Content.Body;
        //debugAlert(title, body);
    }

    public void ApplicationReceivedRemoteMessage(RemoteMessage remoteMessage)
    {
        //Console.WriteLine(remoteMessage.AppData);
        Mvx.Warning(remoteMessage.AppData.ToString());
    }

    public override void RegisteredForRemoteNotifications(UIApplication application, NSData deviceToken)
    {

#if DEBUG
Firebase.InstanceID.InstanceId.SharedInstance.SetApnsToken(deviceToken, Firebase.InstanceID.ApnsTokenType.Sandbox);
#endif
#if RELEASE
Firebase.InstanceID.InstanceId.SharedInstance.SetApnsToken(deviceToken, Firebase.InstanceID.ApnsTokenType.Prod);
#endif
}
    public override void OnResignActivation(UIApplication application)
    {
        // Invoked when the application is about to move from active to inactive state.
        // This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message)
        // or when the user quits the application and it begins the transition to the background state.
        // Games should use this method to pause the game.
    }

    public override void DidEnterBackground(UIApplication application)
    {
        // Use this method to release shared resources, save user data, invalidate timers and store the application state.
        // If your application supports background exection this method is called instead of WillTerminate when the user quits.
        //Messaging.SharedInstance.Disconnect();

        Settings.AppBackGroundTime = DateTime.Now;
    }

    public override void WillEnterForeground(UIApplication application)
    {
        // Called as part of the transiton from background to active state.
        // Here you can undo many of the changes made on entering the background.

        if (Settings.LogoutTimeId > 0 && Settings.AppBackGroundTime != DateTime.MinValue)
        {
            int timeDiff = DateTime.Now.Subtract(Settings.AppBackGroundTime).Minutes;
            if (timeDiff >= Settings.LogoutTimeId)
            {
                var viewModelRequest = new MvxViewModelRequest(typeof(Core.ViewModels.LoginViewModel));
                var view = (IMvxIosView)UIStoryboard.FromName("Tasks", null).InstantiateViewController("LoginView");
                var viewController = view.CreateViewControllerFor(viewModelRequest) as UIViewController;
                UINavigationController nav = (UINavigationController)Window.RootViewController;
                nav.PushViewController(viewController, true);
            }
        }
        Settings.AppBackGroundTime = DateTime.MinValue;
    }

    public override void OnActivated(UIApplication application)
    {
        // Restart any tasks that were paused (or not yet started) while the application was inactive.
        // If the application was previously in the background, optionally refresh the user interface.
    }

    public override void WillTerminate(UIApplication application)
    {
        // Called when the application is about to terminate. Save data, if needed. See also DidEnterBackground.
    }

    /* iCloud  capability start */
    //public override void RegisteredForRemoteNotifications(UIApplication application, NSData deviceToken)
    //{
    //    Console.WriteLine("Registered for Push notifications with token: {0}", deviceToken);
    //}

    public override void FailedToRegisterForRemoteNotifications(UIApplication application, NSError error)
    {
        Console.WriteLine("Push subscription failed");
    }

    public override void ReceivedRemoteNotification(UIApplication application, NSDictionary userInfo)
    {
        Console.WriteLine("Push received");
    }
    /* iCloud  capability end */
}`

Closing due it seems to be a duplicate of issue #158. Please, keep an eye on #158 to see if something can help you to solve this issue. If you feel that this is a different issue, feel free to re-open it.


Do not reinitialize badConsts in each constant synthesis try

This patch fix the bug causing multiple guesses of same constant.

wow that fix was easy :)
should I wait for tests to complete or can this be merged?

@regehr This is a rather stupid bug made by me. This PR can be merged directly.

The test seems to be taking unusually long.
Can you check if there is an unexpected performance regression?


Explorer sort order is not alphabetical

Issue Type: Bug
As far as I can tell, there are some issues with the sort order in the Explorer panel, at least when folders do have a "." (dot) in their names.
As is (notice that Core.Domain[.*] folders are not in sequence)

As expected:

In terms of settings
Settings > Features > Explorer > Sort Order: Default
the sort order is set to Default, so I would expect that files and folders to sort alphatically
VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z)
OS version: Windows_NT x64 10.0.14393
Extensions (1)

Extension
Author (truncated)
Version

markdown-all-in-one
yzh
3.3.0

It is a weird result, but I dont think it's a bug. Based on this explanation it seems that vscode ignores file extensions when sorting unless the names are the same. So what vs code is sorting by is

Core
Core
Core.Domain
Core.Queries
Shared
Shared

Your file manager is sorting by the entire length of the name including the extension, which gives a different result

that would have been probably correct if the sorted targets were files,
but as a matter of fact those are folders,
and should not be treated as having an extension :)


Save a data dump of OldCantus in Digital Alliance storage

In order to preserve the data as is was at EOL of Cantus DB on the UWaterloo servers, we should transfer a copy of the database at that point to a storage location on DRAC.

I'm pretty sure I don't have access to the OldCantus server. @jwang44, is this a thing you could do without much trouble?

I'm not sure whether I still have access, but I will check today or tomorrow.
After I get the sql file, where would you like me to send it?

Thank you, @jwang44!

Yes, thank you!

does @jwang44 have access to the DDMAL cloud whatever-it-is?

Iff @jwang44 has access to Ich's Arbutus allocation.

Are there instructions for how to access this?

On the wiki... which I guess I also don't know if @jwang44 has access to?
@jwang44 I think you should transfer in whatever way is easiest for you (@jacobdgm's suggestion sounds good) and we will make sure it gets where it needs to go.

Sounds good. I'll just scp it to the staging server. I'll reply here with the path when it's done.

The database dump has been made. But I cannot connect to the jump box in the lab, therefore cannot upload it to the staging server. Is the jump box still alive?
The wiki is not working for me either. I used to have access, but for some reason now I have no internet connection once connected to McGill VPN.

@jwang44
I don't know about the wiki/vpn...
But the location of the jumpbox did change at some point in the past 6-ish months, so if that may be the issue if you haven't logged in in that time.
Try HostName jumpbox.simssa.ca rather than whatever IP you may have in your ssh arguments...

It's official. I have lost access to the jumpbox.
Since we might still collaborate more in the future, I think it makes sense to set up or fix my access properly.
Linking this to https://github.com/DDMAL/Operations/issues/95 for record keeping.

OK. Seems my config was out of date and I was using the wrong key.
I have access now, and the database dump has been uploaded to staging at /home/ubuntu/cantus_prod_240319.sql.gz
Let me know if you need anything else.

Thanks @jwang44 !!

I've uploaded this to storage on Ich's arbutus allocation at cantusdb/oldCantus.
@jacobdgm @lucasmarchd01 I think that technically closes this issue. Anywhere else you think it should go?

Thank you, @dchiller, @jwang44!
@dchiller, I just created a stub in the CantusDB Wiki at https://github.com/DDMAL/CantusDB/wiki/OldCantus - can you replace the couple of placeholders I left?

I've added the path on that wiki stub, so I'm going to close this issue.

We might want to preemptively set the permissions more permissively to the main file in ubuntu's ~, to make it easy for future developers who may need to download the file to get it...

Note that the staging server will be removed shortly, so I think this is only relevant to this transfer.


Update handler.go

Updated for 0.9.0

Please also update the version number to 0.9 in the Sample README (sample info section) https://github.com/dapr/samples/blob/master/twitter-sentiment-processor/README.md#sample-info


String interpolation support (i18n / l10n)

It is currently very difficult to produce interpolated names/messages. Such a feature would be useful to e.g. produce different schema, with different type/field names and descriptions, for different locales.
E.g.
@GraphQLQuery(name = "${test.name}", description = "${test.description}")
public String test(@GraphQLArgument(name= "${test.param.name}", description = "${test.param.description}") String param) {
...
}

See the tests for usage examples.

Closed via https://github.com/leangen/graphql-spqr/commit/5c99fb6e630dfe598a8ace4b4de47ef52c83aa64


Consider using inclusive terms rather than Blacklist/Whitelist

Would be possible to change the terms blackList/whiteList to allowList/denyList?
Perhaps add an option to use the allow/deny alternative to avoid creating a major release change.
Thanks for your library!

Yes of course, thank you for pointing it out. If we don’t get a volunteer before the I'll do it this weekend.

If you’d like, I can attempt it this weekend!

Go ahead @dsafanyuk

@dsafanyuk Thank you for posting this, we now have a plan to address it, check #247

I personally don't feel this kind of terminology change will help solve any kind of issue, either in this repository or in the world: this will just add some confusion in a place where those terms have nothing to do with racism, nor they share any ethimological roots with racial discriminations.
But if you feel like this kind of fig leafs will help the society in any way, who am I to disagree?

So guys, we did it. Racism is no more.

Laughable. And the fact that this is still sitting around over a year later just goes to show the true colors being displayed here. Total empty, fake, virtue signaling nonsense. You all should be ashamed.


Is it possible to draw the default drawer of an object using RabbitGUI?

I have a window which extends BetterWindow and I'm using the gui object to create something a bit like an inspector. I have a list that I'd like to display but currently, it looks like I may have to write my own code for rendering the list. Is it possible to somehow leverage the existing code in VFW which renders the list drawer?

After doing some searching around, it looks like it would be possible with the Member function of BaseGUI but it takes an EditorMember which I'm not sure how to get

I should have an example there for custom stuff in a Window, check the examples folder it should be there.
Yeah you have to use that .Member function IIRC. You create the member via Member.Create, you give it your target object (the window in this case), the field/property/function name and a unique id used internally for persisting foldouts etc.

Here's the file. Looks like I was doing it a different way, both are possible though.
https://github.com/vexe/VFW/blob/master/Assets/VFW Examples/Editor/DrawersInEditorWindowExample.cs


XMLHttpRequest properties instead of GET parameters

At the moment, setting HttpConfig properties and using this as part of a $http request will cause them to be added to the request as GET parameters.
For example, this code:
val host = "http://localhost:8080"
val config = HttpConfig("withCredentials" -> true)

def findAll(): HttpPromise[js.Array[Group]] = $http.get(s"$host/groups", config)

Sends the following GET request:
http://localhost:8080/groups?withCredentials=true

However, the withCredentials boolean should be enabled as a property on the XMLHttpRequest object, not sent along as a GET parameter.

Hmm, the HttpConfig object is passed on unmodiifed to AngularJS; have you checked what happens in "pure" AngularJS when you pass withCredentials to $http.get()?

You're absolutely right, the effect of passing withCredentials to HttpConfig does not seem to be the same as setting $httpProvider.defaults.withCredentials, which does work for me in plain AngularJS.
However, I cannot seem to get the defaults setting to work, even after pulling 0.2.1 which includes the defaults.withCredentials addition. I tried the following code:
$httpProvider.defaults.withCredentials = true
$httpProvider.defaults.xsrfCookieName = "something"

While compiling, this returns the following error messages:
[error] /Users/jeroen/42/dashboard2/scripts/App.scala:23: value withCredentials is not a member of biz.enef.angulate.core.HttpDefaults
[error]       $httpProvider.defaults.withCredentials = true
[error]                              ^
[error] /Users/jeroen/42/dashboard2/scripts/App.scala:24: value xsrfCookieName_= is not a member of biz.enef.angulate.core.HttpDefaults
[error]       $httpProvider.defaults.xsrfCookieName = "something"
[error]                              ^

I've purposefully added the xsrfCookieName setting, to ensure that I am actually using the latest version and it's not just the withCredentials flag that's not working.
Any idea why this isn't working?

Sorry, my fault: I declared the properties in HttpDefaults to be defs instead of vars... I'll publish a corrected snapshot.

@offerijns could you please check if it works with 0.2.2-SNAPSHOT?

Absolutely, checking now!

It works perfectly now, thanks!


Precise parallel relation size

Hi:
Can ask for the reason why in default RelIndexRead implementation for CRelIndex, we are computing an approximate size?
I was thinking use precise relation size may avoid the redundunt computation in the case that some inner join body clause is empty.
Yihao

For more details, what I want do is add following change in line 522 in ascent_macro/src/ascent_codegen to :
let size_check_code_list = rule.body_items.iter().filter_map(|bi| {
         if let MirBodyItem::Clause(clause) = bi {
            let rel = expr_for_rel(&clause.rel, mir);
               Some(quote! {
                  #rel.len() > 0
               })
         } else {None}
      });
      // connect the size check code with logical and
      let size_check_code = size_check_code_list.reduce(|a, b| quote!{#a && #b}).unwrap_or(quote!{true});
      evaluate_rules.push(if rule_parallelism { quote! {
         ascent::internal::comment(#msg);
         if #size_check_code {
            __scope.spawn(|_| {
               #before_rule_var
               #rule_compiled
               #update_rule_time_field
            });
         }
      }} else { quote! {
         #before_rule_var
         ascent::internal::comment(#msg);
         if #size_check_code {
            #rule_compiled
         }
         #update_rule_time_field
      }});
   }

Seems when running large rules like ddisasm, this extra check could save us lots of time avoid spinning in long tail iterations

Hey @StarGazerM, yeah I think that's reasonable. I initially made the len an estimate for perf reasons (you can check its impl for parallel relations). But maybe we can calculate the len when freezing the rel. But I'd need to think about how it would affect BYODS rels. In any case, if making the len precise turns out not to be feasible for BYODS rels, we can add an is_empty() method to RelIndexRead and do the optimization you suggested.

yep, I agree, if the len can be unreliable for many data structure maybe we can consider rename? ==, although now these change will immediate force everywhere to be changed in current BYODS relations....


Improving resource URLs

Minor fixes on the resources URLs:

A Byte of Python is now using a clean Amazon URL (no search, no referrals)
Automate the Boring Stuff with Python is now using a HTTPS Amazon URL
Fluent Python is now using a O'Reilly URL, avoiding the redirection
Added GitHub repository for Visual Studio Code, like Atom

this looks great! good first PR, other lemon.


tests: build_all: Fix building for lps25hb and lsm6ds0

The introduction of device tree support sensors need to update the
dts.fixup file in build_all to make sure that we still build.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #6032   +/-   ##
=======================================
  Coverage   52.51%   52.51%
=======================================
  Files         406      406
  Lines       39683    39683
  Branches     7715     7715
=======================================
  Hits        20839    20839
  Misses      15663    15663
  Partials     3181     3181

Continue to review full report at Codecov.

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


no support for Cortex-R5F processors

It is strange that there is no support for Cortex-R5F processors. For example, for new TI AM243x processors.

@edbek Unfortunately, for DSP extensions, the library is dependent on CMSIS-Core.
And CMSIS-Core is still essentially Cortex-M oriented.
CMSIS-DSP only needs instructions macros (like QADD etc ...) and compiler abstraction from CMSIS-Core. But CMSIS-Core has to provide much more.
If at some point the DSP intrinsics and compiler abstractions were moved outside of CMSIS-Core, then it should be easy to support Cortex-R.
You may open an issue on the CMSIS project regarding CMSIS-Core refactoring.

Issue closed since problem is on CMSIS-Core side.


Create Gamespace

The "jump game" layout should be modified so that the player starts in the center of the screen and can move around.

The character moves! Yay!

The character moves! Yay!


ng test --code-coverage doesn't include files outside of src folder

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [ ] build
- [ ] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions
node v8.9.4
npm v6.4.1
Mac OS Mojave
Angular CLI: 6.2.4
Angular: 6.1.9

Repro steps

ng new test-app
create packages/test-package outside of src folder
add there simple test.component.ts and test.component.spec.ts
Modify test.ts file and add context of 'packages directory
replace

const context = require.context('./', true, /\.spec\.ts$/);
context.keys().map(context1);

with
const context1 = require.context('../packages', true, /\.spec\.ts$/);
const context2 = require.context('./', true, /\.spec\.ts$/);

context1.keys().map(context1);
context2.keys().map(context2);

Add "../packages/**/*.spec.ts", to tsconfig.spec.json in "include" section

ng test --code-coverage and open coverage/index.html

Description
Files from packages directory don't include in final coverage report
Desired functionality
All files despite on their location should be presented in final coverage report

This is actually by design, Only files under sourceRoot are listed in the code coverage report. Anything which is not under sourceRoot is considered as external.
https://github.com/angular/angular-cli/issues/11934

It would be great if we could supply an optional list of external directories to include. (perhaps in angular.json?)
That commit completely broke coverage reporting in my team's mono-repo setup :(


Modal pop-up not working

I was trying to deploy an app with the examples provided for the modal pop-up, but when I click the button, nothing shows up.
In the hydralit-components repo it mentions this:
"NOTE: You need to force reload (browser refresh) the entire page after the experiemntal features have been enabled (you will see a notification in the terminal) to ensure the additions have been loaded into the web page."
How can I force reload the browser? And is this even the issue or the modal doesn't work on apps that have been deployed? Thanks!
Streamlit version 3.10.0
Python version 3.9.7
Latest version of hydralit as of this post

Could you solve the issue?


transcrypt: 1.0.2 -> 1.0.3

Semi-automatic update. These checks were performed:

built on NixOS
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/transcrypt -h got 0 exit code
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/transcrypt --help got 0 exit code
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/transcrypt -v and found version 1.0.3
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/transcrypt --version and found version 1.0.3
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/.transcrypt-wrapped -h got 0 exit code
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/.transcrypt-wrapped --help got 0 exit code
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/.transcrypt-wrapped -v and found version 1.0.3
ran /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/.transcrypt-wrapped --version and found version 1.0.3
found 1.0.3 with grep in /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3
found 1.0.3 in filename of file in /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3

cc "@elasticdog"

Success on x86_64-linux (full log)
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3
gzipping man pages under /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin
patching script interpreter paths in /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3
/nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3/bin/.transcrypt-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/bash"
checking for references to /tmp/nix-build-transcrypt-1.0.3.drv-0 in /nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3...
/nix/store/dbpy65mkqdmjij53vjpcfisvhbwnrav5-transcrypt-1.0.3

Success on x86_64-darwin (full log)
Partial log (click to expand)
building
no Makefile, doing nothing
installing
post-installation fixup
gzipping man pages under /nix/store/fvlpk4vg3wc43isdbz86ghl2dmnbbmq8-transcrypt-1.0.3/share/man/
strip is /nix/store/4sdh09gmvl15cy0zb6i7mbvxh5syz206-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/fvlpk4vg3wc43isdbz86ghl2dmnbbmq8-transcrypt-1.0.3/bin
patching script interpreter paths in /nix/store/fvlpk4vg3wc43isdbz86ghl2dmnbbmq8-transcrypt-1.0.3
/nix/store/fvlpk4vg3wc43isdbz86ghl2dmnbbmq8-transcrypt-1.0.3/bin/.transcrypt-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/pkjmwq7sqrvjg7cjiph6hq0khsmfl6p8-bash-4.4-p12/bin/bash"
/nix/store/fvlpk4vg3wc43isdbz86ghl2dmnbbmq8-transcrypt-1.0.3

Success on aarch64-linux (full log)
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/crl9lzs4wh01yfxd84kni1w1ccxa3vs9-transcrypt-1.0.3
gzipping man pages under /nix/store/crl9lzs4wh01yfxd84kni1w1ccxa3vs9-transcrypt-1.0.3/share/man/
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/crl9lzs4wh01yfxd84kni1w1ccxa3vs9-transcrypt-1.0.3/bin
patching script interpreter paths in /nix/store/crl9lzs4wh01yfxd84kni1w1ccxa3vs9-transcrypt-1.0.3
/nix/store/crl9lzs4wh01yfxd84kni1w1ccxa3vs9-transcrypt-1.0.3/bin/.transcrypt-wrapped: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/bash"
checking for references to /build in /nix/store/crl9lzs4wh01yfxd84kni1w1ccxa3vs9-transcrypt-1.0.3...
/nix/store/crl9lzs4wh01yfxd84kni1w1ccxa3vs9-transcrypt-1.0.3


Support renewal of generated certificates

The operator can generate its own self-signed certificates to use for the opensearch pods. However the operator does not have functionality to renew the certificates once they expire after a year.
The operator should check during reconcile runs if any certificates are about to expire and renew them if needed. After renewal the operator needs to do a rolling restart of the opensearch pods so they pick up the new certificates.

i'm not sure if OpenSearch Security already has this feature (the documentation for OpenSearch is still incomplete), but at least Search Guard supports TLS certificate hot reloading.
if OpenSearch Security supports this (or support is added for it) then the operator could use the hot reload API to trigger the re-load.
do you have plans on how to handle the rollover of the CA (which will also expire at some point)?
IMHO this correlates a bit with #141 as cert-manager could take care of some things (though the triggering of the hot reload would still have to be done as cert-manager isn't aware of OpenSearch)

@rursprung

then the operator could use the hot reload API to trigger the re-load.

Sounds like a good idea. Although we might still need to implement a restart variant for older opensearch versions.

do you have plans on how to handle the rollover of the CA (which will also expire at some point)?

No idea yet. Maybe something where a new CA is generated ahead of time and the certificate is signed by both CAs for a time to give services to switch out their CA. Depends a bit on if clients actually use the CA cert to verify connections. Suggestions are always welcome.

Proposed Solution: We will create a secret based on the existing flag which will control whether we need per node certificate or a single certificate for all nodes.
In the case of a single certificate for all nodes, we will create a certificate object and then map the secret created using that object into the Opensearch custom resource.
In the case of per node certificate, we will generate multiple certificates using and merge them into a single secret let's say node-cert-merged(using custom code and adding watcher in the same), as there will be any certificate changes, we will sync the node-cert-merged.
Solutions:

we can have a node-cert-merged reconciler which manages(watch and updates) and does the trick.
We can have a webhook that will watch the secret events and update the master secret accordingly.

and merge them into a single secret

i'd suggest to ask some security experts for their opinion on this. i doubt that they'll be happy with the private key for one node being visible to another node. i don't think that it's super critical in this case, but it definitely goes against the best practices for private/public key usage (where you never, ever give anyone else access to your private key).

Hi,
Thanks for thinking about this issue. This is a very important topic for us since an expired certificate will break the whole OS cluster. Our current workaround is to create certificates with long expiry dates manually, but since transport encryption is only within the cluster, I would like to do no manual steps at all. When using the certificates generated by the operator, is there a way to trigger a renew manually? Like for example removing config from OpenSearchCluster manifest (so that demo certificates are used) and then adding it again?
PS: Hi @swoehrl-mw we worked together a long time ago at MW, nice to see you again :)

Hi @swoehrl-mw

Afterwards you would need to get the operator to do a rolling restart (for example by adding a dummy change to the config). Theoretically this should work without downtime.

Kubernetes tracks the change in secret and updates the volume automatically
From k8s documentation:
When a volume contains data from a Secret, and that Secret is updated, Kubernetes tracks this and updates the data in the volume, using an eventually-consistent approach

The operator should check during reconcile runs if any certificates are about to expire and renew them if needed.

Doing this alone should be fine I feel

@Gokul-Radhakrishnan
If we enable hot-reload of certs (which AFAIK is disabled by default) then yes, just updating the secrets should be enough.

Any movement on this?
Setup a new cluster using our PKI, following this.
I set it up a couple days ago, and went to make a change this morning but the node I restarted would not come up with errors like.
javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[ERROR][o.o.s.s.t.SecuritySSLNettyTransport] [mycluster-masters-2] Exception during establishing a SSL connection: javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
Even though it has mounted the new cert. In order to get the everything up and running all nodes need to be restarted.
Using these certs
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: opensearch-certs-pki
  namespace: opensearch
spec:
  secretName: opensearch-certs-pki
  privateKey:
    size: 2048
    algorithm: RSA
    encoding: PKCS8
  dnsNames:
    - mycluster
    - mycluster-masters-0
    - mycluster-masters-1
    - mycluster-masters-2
    - mycluster-bootstrap-0
    - mycluster-discovery
    - mycluster.opensearch
    - mycluster.opensearch.svc
    - mycluster.opensearch.svc.cluster.local
  usages:
    - key encipherment
    - server auth
    - client auth
  commonName: Opensearch_Node
  issuerRef:
    group: certmanager.step.sm
    kind: StepClusterIssuer
    name: step-issuer
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: opensearch-admin-certs-pki
  namespace: opensearch
spec:
  secretName: opensearch-admin-certs-pki
  privateKey:
    size: 2048
    algorithm: RSA
    encoding: PKCS8
  commonName: OpenSearch_Admin
  usages:
    - key encipherment
    - server auth
    - client auth
  issuerRef:
    group: certmanager.step.sm
    kind: StepClusterIssuer
    name: step-issuer
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: opensearch-dashboards-certs-pki
  namespace: opensearch
spec:
  secretName: opensearch-dashboards-certs-pki
  privateKey:
    size: 2048
    algorithm: RSA
    encoding: PKCS8
  dnsNames:
    - mycluster-dashboards
  usages:
    - key encipherment
    - server auth
    - client auth
  issuerRef:
    group: certmanager.step.sm
    kind: StepClusterIssuer
    name: step-issuer

And this config
---
apiVersion: opensearch.opster.io/v1
kind: OpenSearchCluster
metadata:
  name: mycluster
  namespace: opensearch
spec:
  security:
    tls:  # Everything related to TLS configuration
      transport:
        generate: false
        perNode: false
        secret:
          name:  opensearch-certs-pki
        nodesDn: ["CN=Opensearch_Node", ]
        adminDn: ["CN=OpenSearch_Admin", ]
      http:
        generate: false
        secret:
          name: opensearch-certs-pki
    config:
      adminSecret:
        name: opensearch-admin-certs-pki
      securityConfigSecret:
        name: securityconfig-secret
      adminCredentialsSecret:
        name: mycluster-admin-password
  general:
    serviceName: mycluster
    version: 2.10.0
    setVMMaxMapCount: true
  dashboards:
    enable: true
    opensearchCredentialsSecret:
      name: mycluster-admin-password
    tls:
      enable: true
      generate: false
      secret:
        name: opensearch-dashboards-certs-pki
    version: 2.10.0
    replicas: 2

For now, I am going to test with this: https://github.com/stakater/Reloader

my certificates expired today :(

@KannappanSomu could you perhaps confirm this approach as a feasible workaround until automatic cert-renewal is implemented?

This worked in my cluster.  I still had to scale down the operator to update (recreate) the statefulset with spec.podManagementPolicy: Parallel though.  That's bug #685.

This really seems like something that should have a clear warning in the docs: Like, your cluster will stop working after exactly one year.
Or at least put a warning that this project is far from mature if something critical like this can go unsolved for more than a year after reporting..

@jonathon2nd  any updates ?

@swoehrl-mw

If you delete the -transport-cert and -http-cert secrets the operator should generate new ones during the next reconcile run (so after 30 seconds).

The admin certs expire as well right? Don't we need to regenerate them as well?
With them expired, Security APIs that require admin cert auth might not work, right?

The admin certs expire as well right? Don't we need to regenerate them as well? With them expired, Security APIs that require admin cert auth might not work, right?

@AniketKariya You are correct, the admin cert needs to be recreated as well, otherwise the securityconfig-update job would not work.

I have created this repo as a temporary (but stable) alternative while we wait for an official implementation in the operator: https://github.com/flavienbwk/opensearch-k8s-certmanager
It explains how to setup cert-manager + Reloader with ready-to-deploy examples.


Styles different on my Atom

instead of the one in the screenshot, is something supposed to happen?

@NikhilKalige seems to be fixed.


Add project on https://drupaltools.github.io/

Dear @cyberswat, please create a Pull Request to add this project at https://drupaltools.github.io/. See more at https://github.com/drupaltools/drupaltools.github.io#contributing.
Thanks!

@theodorosploumis Pull request created at https://github.com/drupaltools/drupaltools.github.io/pull/6 ... Thanks for the great work.

Awesome, and thanks for the invite @theodorosploumis . Closing. Followups in the PR https://github.com/drupaltools/drupaltools.github.io/pull/6


Gitlab private token cannot be remove

In GitLab configuration, private token cannot be removed. This way, the plugin cannot be deactivated.

@pluskal is this still an issue? We're considering trying this plugin out.

Yes, to best of my knowledge. We have this plugin and I needed to create an dedicated user for it.


How to get crashlytics stacktraces deobfuscated

Step 1: Describe your environment

Android device: Any
Android OS version: Any
Google Play Services version: 4.2.0
Firebase/Play Services SDK version: 17.0.0

Step 2: Describe the problem:
Ever since Google introduced R8 I'm not getting my crashes stacktraces in crashlytics deobfuscated.
I used to get them before, but not anymore, have the configuration described in this page.
What should I do to get my crashlytics crashes report deobfuscated, the Stack Traces from Google Play are deobfuscated.
Relevant Code:
proguard-rules.pro
-keepattributes *Annotation*
-keepattributes SourceFile,LineNumberTable
-keep public class * extends java.lang.Exception
-keep class com.crashlytics.** { *; }
-dontwarn com.crashlytics.**

@GuanacoDevs are you using the plugin to upload the R8 mapping file to Crashlytics?
You need to use 1.28.0 or higher to get R8 to work:
https://docs.fabric.io/android/changelog.html#march-15-2019

Yes
buildscript {
    repositories {
        google()
        jcenter()
        maven { url 'https://maven.fabric.io/public' }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.1'
        classpath 'com.google.gms:google-services:4.2.0'
        classpath 'io.fabric.tools:gradle:1.28.0'
    }
}

and in app:
dependencies {
    implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'
}

Do you see any errors in the logs?  They would be in this file:
On Linux / Windows:
/.crashlytics/com.crashlytics.tools/crashlytics.log

On Mac:
~/Library/Caches/com.crashlytics/com.crashlytics.tools/crashlytics.log

There is an error but from dec '18.
I have saved the logs from what I think is the last production release that I have uploaded and published here if you get the chance to take a look at it.
This is how a crash looks on the Console:

Can't seem to find the same crash in Play Console, but another crash looks deobfuscated.
I'm using linux mint.
The full app build.gradle is:
apply plugin: 'com.android.application'
apply plugin: 'io.fabric'

android {
    compileSdkVersion 29
    buildToolsVersion '28.0.3'
    defaultConfig {
        applicationId "com.guanacodevs.ubv"
        minSdkVersion 21
        targetSdkVersion 29
        //noinspection HighAppVersionCode
        versionCode<PHONE_NUMBER>
        versionName "Iñaki 2.5.5"
        resConfigs "en", "pt", "es"
        vectorDrawables.generatedDensities = []
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }
    buildTypes {
        release {
            shrinkResources true
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility 1.8
        targetCompatibility 1.8
    }
}

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    androidTestImplementation('androidx.test.espresso:espresso-core:3.2.0', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })

    implementation 'androidx.appcompat:appcompat:1.0.2'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
    implementation 'androidx.recyclerview:recyclerview:1.0.0'
//
    implementation 'com.android.billingclient:billing:1.2.2'
//
    implementation 'com.google.android.ads.consent:consent-library:1.0.7'
    implementation 'com.google.android.material:material:1.0.0'
//
    implementation 'com.google.firebase:firebase-core:17.0.0'
    implementation 'com.google.firebase:firebase-database:18.0.0'
    implementation 'com.google.firebase:firebase-ml-vision:21.0.0'
    implementation 'com.google.firebase:firebase-ads:18.0.0'
    implementation 'com.google.firebase:firebase-auth:18.0.0'
    implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'
//
    implementation 'com.otaliastudios:cameraview:2.0.0-beta04'
    implementation 'com.google.code.gson:gson:2.8.5'
//
    testImplementation 'junit:junit:4.12'
}
apply plugin: 'com.google.gms.google-services'

and the project build.gradle:
buildscript {
    repositories {
        google()
        jcenter()
        maven { url 'https://maven.fabric.io/public' }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.1'
        classpath 'com.google.gms:google-services:4.2.0'
        classpath 'io.fabric.tools:gradle:1.28.0'
    }
}

allprojects {
//    tasks.withType(JavaCompile) {
//        options.compilerArgs << "-Xlint:unchecked" << "-Xlint:deprecation"
//    }
    repositories {
        google()
        jcenter()
        maven { url "https://jitpack.io" }
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Thank you for your time @samtstern

Hmmm I do see things in the logs that indicate the deobfuscation file should have been uploaded:
2019-06-22 02:48:34.987 [DEBUG] (Execution worker for ':' Thread 3) com.crashlytics  - Uploading deobfuscation file
2019-06-22 02:48:34.992 [DEBUG] (Execution worker for ':' Thread 3) com.crashlytics  - POST file: /home/racu/.crashlytics/com.crashlytics.tools/********************************************/deobs/db4bad94-d95e-4624-9124-a0dde6d753cc.zip to URL: https://cm.crashlytics.com/api/v3/platforms/android/code_mappings
2019-06-22 02:48:41.318 [DEBUG] (Execution worker for ':' Thread 3) com.crashlytics  - POST response: [reqId=f62395bf6f551a20bc6a64fe49c1ef9f9229a2c3a6e98ed8] 202
2019-06-22 02:48:41.319 [DEBUG] (Execution worker for ':' Thread 3) com.crashlytics  - Deobfuscation file(s) uploaded.
2019-06-22 02:49:48.581 [DEBUG] (Execution worker for ':' Thread 2) com.crashlytics  - Invoked Crashlytics Developer Tools with arguments:

So I am not sure what's going on.  I will have to ask around.

I have added to my application tag in the manifest
        <meta-data
            android:name="firebase_crashlytics_collection_enabled"
            android:value="true" />

and removed from my Application class were used to initialize Crashlitycs, but I still can't get stack traces deobfucated.
    private void configureCrashReporting() {
        CrashlyticsCore crashlyticsCore = new CrashlyticsCore.Builder()
                .disabled(BuildConfig.DEBUG)
                .build();
        Fabric.with(this, new Crashlytics.Builder().core(crashlyticsCore).build());
    }

@GuanacoDevs had the same issue after updating to 'io.fabric.tools:gradle:1.31.0' crash reports are deobfuscated properly

@AndroidGecko Thank you, I'll try that and close this issue.

Updating to io.fabric.tools:gradle:1.31.0 did not work, still can't get the stack traces deobfuscated, this is really painful.
What am I missing here?

Same problem.

same problem

also seeing the same issue after migrating to R8

While build your application to be release look for this task > "crashlyticsUploadDeobs" and check if it's executed correctly or not
you can also find more logs under
Library/Caches/com.crashlytics/com.crashlytics.tools/crashlytics.log

I couldn't find the file crashlytics.log anywhere on my computer

i updated fabric plugin to io.fabric.tools:gradle:1.31.0 and its working now

To add to oahmedazab's comment, you can specifically run:
./gradlew clean assembleDebug --console=plain
and see if the task "crashlyticsUploadDeobsDebug" appears.
You should be able to find the crashlytics.log in that path and that will tell you if the mapping file is getting successfully uploaded or not, but if that doesn't work, these are all possible paths:
Windows/Linux:
~/.crashlytics/com.crashlytics.tools/crashlytics.log
~/.crashlytics/com.crashlytics.tools.androidstudio/logs/crashlytics.log
~/.crashlytics/com.crashlytics.tools.intellij/logs/crashlytics.log
Mac:
~/Library/Caches/com.crashlytics/com.crashlytics.tools/crashlytics.log
~/Library/Caches/com.crashlytics/com.crashlytics.tools.androidstudio/logs/crashlytics.log
~/Library/Caches/com.crashlytics/com.crashlytics.tools.intellij/logs/crashlytics.log
We're not yet able to reproduce this problem, but it's interesting that for some people upgrading to Fabric Gradle plugin 1.31.0 helps but not for others. @oahmedazab are you able to observe any difference in the crashlytics.log between builds before upgrading and for builds after?

I get the same problem with io.fabric.tools:gradle:1.31.2.
Logs show that Deobfuscation file(s) uploaded, but stack traces in Crashlytics are obfuscated, for example b.a.a.a.s0.m.j1.l.

That was my mistake. I've looked into exception description, not stack trace. Stack trace is fine.

We were struggling with this issue as well - thought bumping to 1.30+ would be the solution (per https://github.com/firebase/firebase-android-sdk/issues/745). What we ended up finding was that we were losing the deobfuscation only when distributing the apk through Firebase, and only when doing so via the appDistributionUploadRelease gradle command. (Manual APK uploads to Firebase were fine). In our case, we were running ./gradlew appDistributionUploadRelease after running ./gradlew assembleRelease both on their own. We realized the appDistributionUploadRelease task didn't call crashlyticsUploadDeobsRelease, and thus realized we should have been calling ./gradlew assembleRelease appDistributionUploadRelease as a single command. (As the docs state, sheesh!) Hopefully that will help someone some headache in the future (or help y'all potentially repro the issue :) )

I get the same problem with io.fabric.tools:gradle:1.31.2 and gradle:3.5.3
crashlytics.log :
com.crashlytics  - POST response: [reqId=null] 403
2020-02-01 21:05:39.337 [WARN] (Execution worker for ':' Thread 3) com.crashlytics  - Crashlytics had a problem uploading the deobs file. Please check network connectivity and try again...

Thanks @poko
We had the same issue but after we added the distributionUpload to the single-line command it is worked.

Thanks all for the continued reports and information on R8 + Crashlytics. Has anyone tried this with Android Gradle plugin version 3.5.3 and can report back what the behavior is when using that version? We believe we've seen some improved behavior when using that version of AGP, but would like to confirm if there are any reports of this behavior in other setups.

We were having this issue in a recent release, and it looks like upgrading the Gradle plugin version to 3.5.3 has solved it for us.

This issue is very old and makes use of the deprecated Fabric Crashlytics Plugin.
Crashlytics now has a new Firebase Plugin which has (hopefully) fixed this issue.
There's also a new documentation page regarding deobfuscation.
Closing the issue for now.


Errors on site without expected parameters set

Hello again:)
$subj, when trying to run this theme against my blog source I get following (site won't render at all):
Building sites … ERROR 2018/03/20 19:04:10 Error while rendering "page" in "": template: theme/_default/single.html:6:7: executing "theme/_default/single.html" at <partial "single_arti...>: error calling partial: template: theme/partials/single_article.html:8:15: executing "theme/partials/single_article.html" at <partial "article_hea...>: error calling partial: template: theme/partials/article_header.html:6:76: executing "theme/partials/article_header.html" at <.Site.Params.date_fo...>: invalid value; expected string
ERROR 2018/03/20 19:04:10 Error while rendering "page" in "post/": template: theme/_default/single.html:6:7: executing "theme/_default/single.html" at <partial "single_arti...>: error calling partial: template: theme/partials/single_article.html:8:15: executing "theme/partials/single_article.html" at <partial "article_hea...>: error calling partial: template: theme/partials/article_header.html:6:76: executing "theme/partials/article_header.html" at <.Site.Params.date_fo...>: invalid value; expected string
ERROR 2018/03/20 19:04:11 in .Render: Failed to execute template "theme/_default/summary.html": template: theme/_default/summary.html:22:91: executing "theme/_default/summary.html" at <.Site.Params.date_fo...>: invalid value; expected string
ERROR 2018/03/20 19:04:12 Error while rendering "home" in "": template: theme/index.html:9:7: executing "theme/index.html" at <partial "article_lis...>: error calling partial: template: theme/partials/article_list.html:14:15: executing "theme/partials/article_list.html" at <partial "article_hea...>: error calling partial: template: theme/partials/article_header.html:6:76: executing "theme/partials/article_header.html" at <.Site.Params.date_fo...>: invalid value; expected string

The reason is likely some absent .Site. parameter but you can't tell it from error message, I guess input parameters handling could be improved. https://github.com/cboettig/hugo-now-ui/issues/9 might be used as reference point.
Also everyone around seems to use .Site.Params.dateformat instead of .Site.Params.date_format.

hi :)
thanks, fixed.

Wow! It works pretty well, only thing is not working is the search, but it's probably my fault and really require some configuration.
Thanks a lot! Resolving.


Error in README

In "Mix queries" using the where before the search generates a SQL Error:
SQLSTATE[HY093]: Invalid parameter number: parameter was not defined (SQL: select count(*) as aggregate
moving the where after the search seems to work without issues !

Witch db engine do you use? I does work with mariadb I've tested it!

I'm using postgres


Setting zwave node parameter results in int16 overflow error

Home Assistant release with the issue:
0.85.1
Last working Home Assistant release (if known):
Not known
Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu 16.04.5 LTS
Component/platform:
https://www.home-assistant.io/components/zwave/
Description of problem:
I've added a FIBARO  FGRGBWM441 RGBW light controller to my system. Parameter 14 of this node , in my case, needs to be set to 39321 (HEX: 9999) according to the manual.
https://manuals.fibaro.com/content/manuals/en/FGRGBWM-441/FGRGBWM-441-EN-A-v1.1.pdf
Trying to set any value above 32767 results in a failure and an error is logged.
Traceback (if applicable):
Mon Jan 14 2019 16:33:56 GMT+0100 (Central European Standard Time)

Error handling message: {'type': 'call_service', 'domain': 'zwave', 'service': 'set_config_parameter', 'service_data': {'node_id': 13, 'parameter': '14', 'value': 39321}, 'id': 14}
Traceback (most recent call last):
  File "/opt/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api/decorators.py", line 17, in _handle_async_response
    await func(hass, connection, msg)
  File "/opt/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api/commands.py", line 148, in handle_call_service
    connection.context(msg))
  File "/opt/homeassistant/lib/python3.6/site-packages/homeassistant/core.py", line 1121, in async_call
    self._execute_service(handler, service_call))
  File "/opt/homeassistant/lib/python3.6/site-packages/homeassistant/core.py", line 1145, in _execute_service
    await self._hass.async_add_executor_job(handler.func, service_call)
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/opt/homeassistant/lib/python3.6/site-packages/homeassistant/components/zwave/__init__.py", line 539, in set_config_parameter
    value.data = int(selection)
  File "/opt/homeassistant/lib/python3.6/site-packages/openzwave/value.py", line 292, in data
    self._network.manager.setValue(self.value_id, value)
  File "src-lib/libopenzwave/libopenzwave.pyx", line 2875, in libopenzwave.PyManager.setValue
OverflowError: value too large to convert to int16_t

Additional information:
This is a blocking issue. The field should support larger values than int16.

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant and report back if this is still a problem? Thanks!


Use old_relation for renaming in default materializations

Describe the bug
In the default view and table materializations, dbt should rename old_relation to backup_relation, instead of renaming target_relation to backup_relation. The issue here is that, if old_relation.type != target_relation.type, dbt will run the wrong alter ... rename statement.
I think this is as simple as switching these to
  {% if old_relation is not none %}
    {{ adapter.rename_relation(old_relation, backup_relation) }}
  {% endif %}

Steps To Reproduce

Create + run a view model
Change config to table + rerun

This does not break on any of the core adapters:

Redshift and Postgres use alter ... rename, but they support alter table for both tables + views
Snowflake and BigQuery don't use alter ... rename, they instead use create or replace

It does break on Presto, which distinguishes between alter view and alter table. dbt will attempt to run alter table (because target_relation.type is table) against an existing view and return an error.
Expected behavior
dbt should use the type of the old relation when it attempts to rename it.
The output of dbt --version:
dbt --version
installed version: 0.15.2
   latest version: 0.15.2

Up to date!

Thanks for the report @jtcohen6. We can get this fixed in a future release, but I'd advise addressing this in a materialization override in the presto plugin for the time being!

I opened a pull request on 0.19.latest to fix this issue.
Since the macro is the same in 0.20.latest, should I also open a pull request on branch 0.20.latest?


profiles controller for admin

There are two actions: update and admin_update in admin/profiles_controller.rb doing similar things, so check to use one action instead.
See: https://github.com/rubymonsters/speakerinnen_liste/blob/master/app/controllers/admin/profiles_controller.rb

This is my first time looking at Speakerinnen code (yay!), so I could use some input:
I've searched in the code, it seems the admin profiles controller (controllers/admin/profiles_controller.rb)'s regular update action is not being used, only the admin_update action. But I might have overlooked something. Has anyone recently looked at this?
Seems unnecessary to have an extra admin_update action, as we are already in a controller in the admin scope.
So I could put the code inside admin_update, which does a bit more, into update and then change all the paths to point to it as well.
Thoughts? :)

YAY 🎉 Welcome @ariaru \o/
It's a long time ago I worked on this, but it seems to me you are right. I would prefer to use the update action instead of admin_update because it's the rails default (then we don't need an extra route; it's also clear that we use the admin controller, so it's repeated unnecessarily).
Maybe it's a good way to look at the tests here
https://github.com/rubymonsters/speakerinnen_liste/blob/master/spec/controllers/admin/profiles_controller_spec.rb
and check what that covers (I guess not all functionality is tested), write a test for the wanted behavior so you can verify the code works properly.
Feel free to ask again! :)


release 0.4.0

Ⅰ. Describe what this PR did
release 0.4.0
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #630 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #630   +/-   ##
==========================================
  Coverage      31.66%   31.66%
  Complexity       863      863
==========================================
  Files            227      227
  Lines           8817     8817
  Branches        1060     1060
==========================================
  Hits            2792     2792
  Misses          5712     5712
  Partials         313      313

Continue to review full report at Codecov.

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


Make SorterProcessor's default comparator public

For applications that define custom sorting comparator
functions it is useful to be able to invoke the default
comparator function that SorterProcessor uses internally.
Move this function to be a static to sap.ui.model.Sorter

 You should sign our Contributor License Agreement in order to get your pull request merged.

This pull-request aims to make the private fnCompare comparator function in sap.ui.model.SorterProcessor public by moving it to sap.ui.model.Sorter as a static function that can be accessed publicly via sap.ui.model.Sorter.defaultComparator.

Hi Jonathan,
I brought this to the attention of the responsible developer and am awaiting his feedback.
If the function is supposed to be public, it definitely needs some JsDoc, but let's wait first, whether the overall approach is fine.
Regards
Andreas

I went ahead and added the jsdoc for the newly-public function and gave this pull-request a fresh rebase against master.

Re-asked @goligo ...


missing redirect for old workers sites endpoint

https://developers.cloudflare.com/workers/sites/ this used to resolve and it doesnt anymore

Thanks @EverlastingBugstopper. Fixed with https://github.com/cloudflare/cloudflare-docs/commit/d3feaa28b83fa1ee0f968483278ad1108e4459d4


C# compiler should not report any warnings.

It is not a good development practice when compiler reports warnings. I created a pull request to address that issue.

Resolved with pull request #1125


Cannot click on an element whereas document.querySelector().click works

Hello
I try to expand a div by clicking on it but it doesn't expand.
If you go to https://www.perfectstay.com/fr-FR/bv-oly-hotel?uuid=test, you can expand the "Plus de détails"
Before expand :

After expand :

Using this code on the console do expand the div :
document.querySelector(".accommodation__introduction .more-details .rc-collapse-header").click()
However, using the chromeless click API does not expand the div. Here is my code runnable in the Playground
const chromeless = new Chromeless({ remote: true })
const screenshot = await chromeless
  .goto('https://www.perfectstay.com/fr-FR/bv-oly-hotel?uuid=test')
  .click(".accommodation__introduction .more-details .rc-collapse-header")
  .scrollTo(0, 2000)
  .screenshot()
console.log(screenshot)
await chromeless.end()

Thanks
Best regards !

This seems to work for me
https://243760423205-eu-west-1-chromeless.s3.amazonaws.com/cj69nsmai001001qqt2emh5al.png
.goto('https://www.perfectstay.com/fr-FR/bv-oly-hotel?uuid=test')
  .scrollTo(0, 2000)
  .click(".accommodation__introduction .more-details .rc-collapse-header")
  .wait(1000)
  .screenshot()

Hi @DavidReinberger
Your code works indeed.
But why do I have to scroll to the element before clicking on it in order to expand it ?
Any explanations ?
thanks


Can you add a license in the repo?

I have IDX support working, but need a license to contribute

Done!


APPCMD failed with error code 4312

I have a docker file with some variables and CMD instruction. It do not work. Simplified example below.
Docker file:

FROM mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2019
ENV MY_SUPER_VARIABLE="Hello world!"
ENTRYPOINT ["C:\ServiceMonitor.exe", "w3svc"]
CMD ["C:\ServiceMonitor.exe", "w3svc"]

docker info:

Client:
Debug Mode: false
Server:
Containers: 46
Running: 0
Paused: 0
Stopped: 46
Images: 65
Server Version: 19.03.2
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows Server 2019 Standard Evaluation Version 1809 (OS Build 17763.615)
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 7.906GiB
Name: WIN-P1U2Q5DO49C
ID: 4BOF:LAK4:XOTP:2FNA:3OBR:YDIU:LFWW:3MZ3:N6R4:ZIAC:QK3X:VDSX
Docker Root Dir: C:\ProgramData\Docker
Debug Mode: true
File Descriptors: -1
Goroutines: 41
System Time: 2019-10-01T05:15:37.0250428-07:00
EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Product License: Community Engine

Commands:

docker build -t oracle_db .
docker run -it oracle_db

Result:

Service 'w3svc' has been stopped
APPCMD failed with error code 4312
Failed to update IIS configuration

Interesting to note, if I simply remove line ENV MY_SUPER_VARIABLE="Hello world!" it will work. I cannot understand it.

You don't need to define the entrypoint. IIS image already defines it. See the example on the first page.

@bariscaglar, yeah, I did it just for testing. But without this line result is the same.

Did you also remove CMD?

I need CMD. No matter what I put here. It is not work.
For example:
FROM mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2019
ENV MY_SUPER_VARIABLE="Hello world!"
copy start_db.ps1 start_db.ps1
CMD ["powershell.exe", "-file", "start_db.ps1"]

Simply removing ENV solves the issue. But I need both instructions.

Hi. I found why it is not working. The CMD command instead of executing "powershell.exe" it extends argument list of ENTRYPOINT. That's why it stop to work.
So the question is, why CMD do not execute executable file in exec form?

@StasClick I am having the same issue, even when using the docker file coming with https://github.com/microsoft/dotnet-framework-docker.git. Did you have any success finding a solution?

@kejvi-doko Hi. Yes, solved. But already not remember how. I guess it was related to some windows updates, and when I downloaded new image version and the issue disappeared.

[Environment].
Docker Engine:20.10.7, build f0df350
Docker for desktop: 3.5.2
CMD ["C:\ServiceMonitor.exe", "w3svc"] to
ENTRYPOINT ["C:\ServiceMonitor.exe", "w3svc"].
In my environment, the container was started and the environment variable was also set to the container.

In my case the error was fixed by using RUN instead of CMD


Draft: add lfs support

This is a draft to add LFS support as metioned in issue #42, but was stuck due to the same-origin policy of github.
I've

Analyze whether the file is LFS with it's content
Try to do a POST request to get the download link (failed because CORS is not allowed)
Download from the link (not implemented yet)

The problem I've encountered is similar to this comment
What can I do to solve the CORS problem?

What can I do to solve the CORS problem?

That's the whole issue, I think. Probably it cannot be done


Add sendPidsAndRates

Well, its an example, please change it as you pleased.

Thanks a ton again, I had already hacked something and was too far along...


Builder Script Requires Podman despite container engine set to "docker"

What happened:
Builder script requires podman
Debug Logs:
$ ./build --container-engine=docker metal-server_pxe
./build: line 85: podman: command not found

How to reproduce it:

git clone git@github.com:gardenlinux/gardenlinux.git
cd gardenlinux
./builder --container-engine=docker metal-server_pxe

Environment:
$ docker version
Client:
 Version:           26.1.4
 API version:       1.45
 Go version:        go1.21.11
 Git commit:        5650f9b
 Built:             Wed Jun  5 11:26:02 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.31.0 (153195)
 Engine:
  Version:          26.1.4
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.11
  Git commit:       de5c9cf
  Built:            Wed Jun  5 11:29:12 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.33
  GitCommit:        d2d58213f83a351ca8f528a95fbd145f5654e957
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ uname -a
Darwin Ricks-Air-2 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:19:05 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8112 arm64

Hi @RiRa12621, thanks for your issue.
I think the issue is because we don't parse the equals sign.
Please try ./build --container-engine docker and let me know if that works for you.
Best,
Florian

Works like that. thanks

Thanks for the quick confirmation. I think from a UX perspective this is not ideal.


Not able to connect to Queue manager running in AKS via MQ Explorer

Hi,
We have setup MQ in AKS and networking within the cluster is implemented with Istio. I was able to connect and login to web console but when trying to connect to queue manager from MQ Explorer tool I get this error
"Could not establish a connection to the queue manager - reason 2009. (AMQ4059)
Severity: 10 (Warning)
Explanation: The attempt to connect to the queue manager failed. This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken.
Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded."
Is there a default username and password we'd have to pass like how we did for web console or do we need any other settings? Please let me know.

@arthurbarr, any help would be much appreciated.

There are two main things to consider here:

The MQ queue manager configuration
The MQ Explorer configuration

IBM MQ does not configure users for you, in the queue manager or web console.  The MQ Advanced for Developers container image however, does offer a simplified set up of two users called "app" and "admin".  If you want to use these users, you need to turn them on, and set passwords for them.  See https://www.ibm.com/docs/en/ibm-mq/9.4?topic=reference-mq-advanced-developers-container-image for some more information.
The connection from MQ Explorer (on your laptop) to the queue manager on AKS will be done using an MQ client.  It will need to be routed correctly in the networking layer.  In OpenShift, the HAProxy router uses the TLS Server Name Indicator (SNI) header to do that routing, so you need to configure MQ to use that.  See https://community.ibm.com/community/user/integration/blogs/avinash-ganesh/2023/06/14/ibm-mq-queue-manager-on-ocp-kubernetes-cluster-mq?CommunityKey=183ec850-4947-49c8-9a2e-8e7c7fc46c64 for some more details.  If you're using another sort of networking configuration, things will be different.

I've set both variables in the configuration, and for the connection from MQ Explorer to the queue manager, I've set similar route to allow connections on 1414. Verified there are no firewall denies and verified connectivity using network tools. Still I'm only getting "reason 2009. (AMQ4059)". I've ran a trace from the explorer and it says "MQQueueManager not defined to " does this mean anything?

Port 1414 is set for plain communication, does Qmanager expect TLS on this port too? if so can we use out gateway's TLS certs? or do we have to configure any certificates for Qmanager?
@arthurbarr please help.

Port 1414 can be used for TLS and non-TLS traffic.
Connecting via TLS is notoriously complex, as the underlying TLS code can't expose detailed error messages, as that could represent a security risk.  It's all handled low down in the networking and security stacks.
Which certificates you need depends on which "gateway" you're using, and whether it is terminating the TLS connection or not.  e.g. one approach is to use a "passthrough" mode on a gateway/router, which just passes the bytes directly across — this means that the client (MQ Explorer) needs the cert of the queue manager.  If the gateway/router is terminating the TLS connection and making a new one onto the queue manager, then the client (MQ Explorer) will need the gateway's certificate, and the gateway will need to be configured with the queue manager certificate.

Closing due to inactivity


fix comment typo in Histogram::Remap

minor typo 'onto' instead of 'unto' in Histogram::Remap comment

Can you please fix multiple typos? There are PRs that fix all possible typos using a script for example (see PRs with title "NFC: Fix typos..")
This way, we don't spin hours of CI for just one tiny letter change.

@mihaimaruseac that's fair, I'll add multiple spelling corrections together in a PR. Scripting though may not always be possible, 'unto' is a word but 'onto' was meant for the surjection.


raw counts instead of cpm

Dear wbazant,
Is it possible to get raw counts instead of cpm? I tried to replace "cpm" by "column" in the parameter 'summaryColumn', but it did not work.
Best regards,
Ailton.

Hi Ailton, thanks for the question! Yes it is, I've updated the documentation in the link below. I'm on my other laptop - could you do me a favour and check that the options I listed all work?

Dear wbazant,
Thank you for the support. All summaryColumn values work.
Bests,


Related to issue #37

If you set your time to GMT, it says:
The label 8:30 would trigger the email on Tuesday March 7, 2017 8:30:00am.
That's right.
Now, if you set it to, say, Mountain, it says:
The label 8:30 would trigger the email on Tuesday March 7, 2017 1:30:00am.
8:30 != 1:30

I also had this issue, where some entries would register time normally (like "1 hour later"), but others (like "09:00am Monday"), would register GMT time. Unfortunately makes this script somewhat unusable, since I don't know exactly what time is going to be used. Looks great otherwise though! I would be super excited if this bug was fixed.


AMBARI-22918 Decommission RegionServer fails when kerberos is enabled

What changes were proposed in this pull request?
Change the hbase_decommission.py to make it work when kerberos is enabled.

Move {master_security_config} into the environment variable HBASE_OPTS.

How was this patch tested?
I manually tested it my local env.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/464/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/465/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/468/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/571/
Test FAILed.
Test FAILured.


Shift key doesn't work in web export

Godot version
v4.0.stable.official [92bee43ad]
System information
Firefox 110.0, Linux
Issue description
On web exports, inputs mapped to the shift key are not triggered. Nor does comparing event.physical_keycode == KEY_SHIFT work. For some reason though, event.as_text() still returns Shift on web.
This same issue seems to have been reported for Godot 2.1.3 but was closed without being resolved: https://github.com/godotengine/godot/issues/10120
Steps to reproduce

try to capture an input mapped to shift in a web exported project
input doesn't register, other keys work as normal

Minimal reproduction project
MRP_shift_html5.zip
This project contains several different ways of detecting inputs. Should be useful to compare how editor/desktop/web builds react to shift keypresses.

Shift, Ctrl, Alt seem to match the keycodes of their initials in web exports.

Duplicate of #74415


Add mutating profiler symbols to symbols package

Summary
The MutatingMonitorProfiler.pdb symbols are missing from the symbols archive packages. Add them so they are registered when publishing symbols.
Validation build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2312327&view=results

Release Notes Entry

/backport to release/8.x


Ignore adb's "im starting server" spew.

We should ignore lines from 'adb devices' when the line is empty or starts with a *.  My pool.rb contains
  {
    :name => 'name', # description
    :serial => '* daemon not running. starting it now on port 5037 *',
  },

  {
    :name => 'name', # description
    :serial => '* daemon started successfully *',
  },

Hi. How did you generate this pool.rb file?