"Object reference not set to an instance of an object" on Initialize

🐛 Bug Report
The app crash on startup.
Expected behavior
App startup and push works.
Reproduction steps
Just follow the setup steps and "play" running VS on Windows SO.
Configuration
Version: 3.3.10
Platform:

[X] :iphone: iOS
[X] :monkey: Xamarin.Forms

Additional info:
[0:] An error occurred: 'Object reference not set to an instance of an object.'. Callstack: '  at Plugin.FirebasePushNotification.FirebasePushNotificationManager.Initialize (Foundation.NSDictionary options, System.Boolean autoRegistration) <0x1016d8600 + 0x0004c> in :0
at MYAPP.Mobile.iOS.AppDelegate.FinishedLaunching (UIKit.UIApplication app, Foundation.NSDictionary options) [0x00014] in PATHTOMYAPP\MYAPP.Mobile.iOS\AppDelegate.cs:29
at (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr)
at UIKit.UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate) [0x00005] in /Library/Frameworks/Xamarin.iOS.framework/Versions/<IP_ADDRESS>/src/Xamarin.iOS/UIKit/UIApplication.cs:86
at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) [0x0000e] in /Library/Frameworks/Xamarin.iOS.framework/Versions/<IP_ADDRESS>/src/Xamarin.iOS/UIKit/UIApplication.cs:65
at MYAPP.Mobile.iOS.Application.Main (System.String[] args) [0x00001] in PATHTOMYAPP\MYAPP.Mobile.iOS\Main.cs:12
at (wrapper managed-to-native) System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Reflection.RuntimeMethodInfo,object,object[],System.Exception&)
at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0006a] in /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/src/Xamarin.iOS/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:395 '
The app has been terminated.

Hello!
I encountered this problem too.
Tried debugging the application on a iPhone 11 Pro Max connected to a Windows 10 PC.
I started it using Hot Restart (preview) feature in Visual Studio 16.6.4.
All packages are up to date.

Encountered a similar issue, I placed FirebasePushNotificationManager.Initialize() after LoadApplication(new App(new iOSInitializer())). I simply exchange the sequence of the two where FirebasePushNotificationManager.Initialize() would be called first. This fixed the issue for me.

I remove the Plugin and migrate to Azure Notification Hub...

Hi, I am getting this error using Xamarin Forms V<IP_ADDRESS>7, Xamarin.Firebase.iOS.CloudMessaging V4.7.1, and the getting started guide code.
[HotReload] (2020-12-14 12:07:02.0): INFO: XAML Hot Reload Connected and Ready.
[0:] An error occurred: 'Object reference not set to an instance of an object.'. Callstack: '  at Plugin.FirebasePushNotification.FirebasePushNotificationManager.Initialize (Foundation.NSDictionary options, System.Boolean autoRegistration) [0x00029] in /Users/runner/runners/2.169.1/work/1/s/Plugin.FirebasePushNotification/FirebasePushNotificationManager.ios.cs:141
  at Plugin.FirebasePushNotification.FirebasePushNotificationManager.Initialize (Foundation.NSDictionary options, Plugin.FirebasePushNotification.NotificationUserCategory[] notificationUserCategories, System.Boolean autoRegistration) [0x00000] in /Users/runner/runners/2.169.1/work/1/s/Plugin.FirebasePushNotification/FirebasePushNotificationManager.ios.cs:176
  at BuzzApp.iOS.AppDelegate.FinishedLaunching (UIKit.UIApplication app, Foundation.NSDictionary options) [0x00123] in D:\INTEC.TS\INTEC.TheBuzzApp\Source\BuzzApp\BuzzApp.iOS\AppDelegate.cs:91
  at (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr)
  at UIKit.UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate) [0x00005] in /Library/Frameworks/Xamarin.iOS.framework/Versions/<IP_ADDRESS>/src/Xamarin.iOS/UIKit/UIApplication.cs:86
  at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) [0x0000e] in /Library/Frameworks/Xamarin.iOS.framework/Versions/<IP_ADDRESS>/src/Xamarin.iOS/UIKit/UIApplication.cs:65
  at BuzzApp.iOS.Application.Main (System.String[] args) [0x00001] in D:\INTEC.TS\INTEC.TheBuzzApp\Source\BuzzApp\BuzzApp.iOS\Main.cs:18
  at (wrapper managed-to-native) System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Reflection.RuntimeMethodInfo,object,object[],System.Exception&)
  at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0006a] in /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/src/Xamarin.iOS/mcs/class/corlib/System.Reflection/RuntimeMethodInfo.cs:395 '
The app has been terminated.

I have tried placing the  FirebasePushNotificationManager.Initialize in different places with no change in the error. Looking at line 141 of FirebasePushNotificationManager.ios.cs it would appear that https://github.com/CrossGeeks/FirebasePushNotificationPlugin/blob/cda71416f3f847df1b01708868bc1ef1196e33f6/Plugin.FirebasePushNotification/FirebasePushNotificationManager.ios.cs#L141 is where the error is?
So why is  Messaging.SharedInstance always = null?
Any help would be appreciated
Thanks

I have same issue here...
Does anyone have a solution for this ?

Up!
Any solution?

Not yet... I remove plugin and migrate to Azure Notification Hub..

The problem only appears on windows with a physical iPhone. https://github.com/xamarin/GoogleApisForiOSComponents/issues/486
I think it has nothing todo with this plugin.


ListView has a one pixel line between elements

Steps to Reproduce
When using a ListView where each elements have it's own background color, the list sometime has a one pixel transparent line between elements.
class TestScroll extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Container(
      color: Colors.white,
      child: ListView(
        children: <Widget>[
          for (var i = 0; i < 50; i++)
            Container(
              height: 50,
              color: Colors.black,
            )
        ],
      ),
    );
  }
}

Logs
There is no meaning full log for this issue.

[✓] Flutter (Channel beta, v1.7.8+hotfix.4, on Mac OS X 10.14.6 18G84, locale en-FR)
    • Flutter version 1.7.8+hotfix.4 at /Users/***/Documents/flutter
    • Framework revision 20e59316b8 (10 days ago), 2019-07-18 20:04:33 -0700
    • Engine revision fee001c93f
    • Dart version 2.4.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
    • Android SDK at /Users/***/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.3, Build version 10G8
    • CocoaPods version 1.7.5

[✓] iOS tools - develop for iOS devices
    • ios-deploy 1.9.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.36.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.2.0

[✓] Connected device (1 available)
    • Nokia 7 plus • <IP_ADDRESS>:5555 • android-arm64 • Android 9 (API 28)

• No issues found!

This problem seems to be limited to Android devices since I couldn't reproduce it using the iPhone Simulator

This looks like a known problem with antialiasing and mapping from logical pixels to device pixels. There's an open issue for a documentation fix: #14288
More info about the problem can be found here:
#14288 (comment)
#17084 (comment)
#15035 (comment)

I close this because of the other issues


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-30-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4789

Questions ?
Please refer to the Backport tool documentation


Implement the missing sync tests and make the existing ones work better

The changes to how BaaS is installed is for the sake of SPM; copying the BaaS files into the bundle is awkward to do there, so instead the tests just run it directly from the build directory (and the installation paths are adjusted to make that easier).
Reusing a single App for all of the tests cuts the runtime of the test suite in half and doesn't change anything about how the tests work, as the only thing that creating a new App per test was actually doing was generating unique partition values for each test.
While trying to get the tests passing when running via SPM I noticed that some of them weren't testing what they were trying to test, and then I ended up just implementing all of the tests which weren't fully ported from the old ROS tests.

@tgoyne did you check that this works on Big Sur? I copied the BaaS files to the bundle because I started getting strange permission errors after the Big Sur update.

Yes, this all works on 11.0 beta 10 for me (I guess I should install the final release huh...).


Minor Update to Terms & Conditions Page + Add 10 Project Detail Pages to Cards Under Project Section of website

Is your feature request related to a problem? Please describe.

Links are not clickable at terms and condition page
Project Detail Pages are not built yet

Describe the solution you'd like.

it will be better if this block is clickable  to contact us page in case some user need help

Describe alternatives you've considered.
I will add 10 pages to these cards similar to other available project pages.

Traffic Accident Prediction System
Personalized Learning Recommendation System
AI for Mental Health Analysis
AI-Driven Disaster Relief Supply Chain Optimization
Urban Sound Classification
Smart Home Energy Prediction
AI for Personalized Nutrition Plans
Plastic Waste Classification To Recycle
AI-Powered Virtual Therapist
Human Face Landmark Detection

Additional context.
@vivekvardhan2810
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@vivekvardhan2810 please assign me the task

@Adarsh-Chaubey03 please explain for this.

like what do you want to change.

@Adarsh-Chaubey03 please explain for this.

like what do you want to change.

These cards do not have project detail pages like cards above them are having. i will add respective project detail page for each project card like this:

@Adarsh-Chaubey03 assigning this issue to you.
Make sure to complete this.

As i have said earlier that this project and i am going to be inactive from today evening.


Better handle the output file

Using click.File we can be sure that the file is opened.
Additionally, the actual opening and closing of the file
can be left to click and one line of indent can be removed.
Thus the code is simlified.
Also as a nice bonus, this allows to output the gcode to
stdout by providing "-" as output file on the command line
similar to typical unix tools.

It looks like a bigger change than it is. Actually it is just removing the open call and its indent and replacing all f with output.

It looks like a bigger change than it is. Actually it is just removing the open call and its indent and replacing all f with output.

Do not merge, does not work 100% after the recent changes. We don't know the filename anymore, so we can't include it in the header.

Do not merge, does not work 100% after the recent changes. We don't know the filename anymore, so we can't include it in the header.

I think we have to decide: Do we want to be able to include the filename in the output, then we can't use click.File as the output could also be stdout or other non-files. On the other side, this would simplify the code base.I leave the call to @tatarize.

I think we have to decide: Do we want to be able to include the filename in the output, then we can't use click.File as the output could also be stdout or other non-files. On the other side, this would simplify the code base.I leave the call to @tatarize.

I'm done editing the code probably for a good long while... and likely stepped on your toes for this one a bunch of times. Should be good now.

I'm done editing the code probably for a good long while... and likely stepped on your toes for this one a bunch of times. Should be good now.

Yes, in principle, that's the better way to handle the output file and if done that way I'd entirely take merge that. Specifically for the reason that that is what write does within vpype.
@click.argument("output", type=click.File("w")) is directly from the vpype code. Making them generally the same or more similar is a fine way of doing that.
On the flip side there's always a weirdness with opening files with cli parsers because they don't actually get closed at the end very well, and sometimes get stuck open for the duration of the program. It's not much of a trouble here since it's quitting the program right afterwards.

Yes, in principle, that's the better way to handle the output file and if done that way I'd entirely take merge that. Specifically for the reason that that is what write does within vpype.
@click.argument("output", type=click.File("w")) is directly from the vpype code. Making them generally the same or more similar is a fine way of doing that.
On the flip side there's always a weirdness with opening files with cli parsers because they don't actually get closed at the end very well, and sometimes get stuck open for the duration of the program. It's not much of a trouble here since it's quitting the program right afterwards.

This is the right thing to do @theomega 👍🏻

Do we want to be able to include the filename in the output, then we can't use click.File as the output could also be stdout or other non-files.

Click has facilities to recover the name: output.name. I'm using this in write's implementation.
I think its fine to expose file name to the .format(). Users will just have to cope with it shows up as <stdout> when they use -.

This is the right thing to do @theomega 👍🏻

Do we want to be able to include the filename in the output, then we can't use click.File as the output could also be stdout or other non-files.

Click has facilities to recover the name: output.name. I'm using this in write's implementation.
I think its fine to expose file name to the .format(). Users will just have to cope with it shows up as <stdout> when they use -.

Side Q: is it normal that both dx and _dx params to format() are passed the save value?

Side Q: is it normal that both dx and _dx params to format() are passed the save value?

Side Q: is it normal that both dx and _dx params to format() are passed the save value?

Nah, just a bug. Corrected in 0.6.2

Side Q: is it normal that both dx and _dx params to format() are passed the save value?

Nah, just a bug. Corrected in 0.6.2

Okay, and I moved and checked these changes in 0.6.5 for #10, ported them in and they seem to work perfectly fine. Except that the stream doesn't flush and close() like it does with a with so I had to add that to the end.

Okay, and I moved and checked these changes in 0.6.5 for #10, ported them in and they seem to work perfectly fine. Except that the stream doesn't flush and close() like it does with a with so I had to add that to the end.

I'm pretty sure this was in draft because of the lack of close() unless there's some other issue within this PR I missed I'll go ahead and close it in a day or two.

I'm pretty sure this was in draft because of the lack of close() unless there's some other issue within this PR I missed I'll go ahead and close it in a day or two.


Update test1.yml

Hi @k0n4m1k0d3 It looks like you already found the issue with this request as I see you have completed the course, congratulations! I am going to close this PR, thank you!


Marlowe tutorial april2020

Updated section 10 of the tutorial for the new version of the playground.

Made all the changes asked for, and uploaded missing file

Updated section 6 of the tutorial to new video links.


Added some engineering design docs.

This is the most basic engieering docs I could think of.
I have no plans to extend it in the future, unless we get some repeated questions that justifies spending time on it.
After it's merged these docs would make it into: https://course-access-groups.readthedocs.io/
TODO

[ ] Get a review from John on the engineering design docs.

@johnbaldwin Please review this PR at your leisure. Being a doc-only PR allow us to keep it open for a longer time so we don't rush it.


TypeError: 'NoneType' is not iterable

In addition to the error traffic error reported in another issue, I've been getting this one:
`This error originated from a custom integration.
Logger: custom_components.googlewifi
Source: custom_components/googlewifi/init.py:171
Integration: Google WiFi Integration (documentation, issues)
First occurred: 6:36:10 PM (2 occurrences)
Last logged: 6:54:29 PM
Unexpected error fetching GoogleWifi data: 'NoneType' object is not iterable
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/googlewifi/init.py", line 171, in _async_update_data
system_data = await self.api.get_systems()
File "/usr/local/lib/python3.9/site-packages/googlewifi/init.py", line 191, in get_systems
return await self.structure_systems(response)
File "/usr/local/lib/python3.9/site-packages/googlewifi/init.py", line 289, in structure_systems
for this_station in system_metrics.get("stationMetrics"):
TypeError: 'NoneType' object is not iterable
`

I can't replicate this - it may be specific to your system or might be a periodic issue that the API for the metrics fails during the call.


Add support for redirects on 410 responses

In Optimizely, expired pages respond with a 410 http response which is ignored by the NotFound Handler.
This PR adds a option to enable the redirect manager to work on 410 responses.

@jevgenijsp @kaspars-ozols @marisks
Could any of you have a look at this PR?


configure google and other search engines to crawn the site

Add to search engines
Add sitemaps
Improve seo

added site to bing, google


Running YOLOX under mac M1

I had many problems regarding the necessary requirement under a Mac Pro M1

Same problem!

Could you plz show me some error log  @firasjlassi  @NourSoltani  ?

Here is my log, it related with onnx lib.
So how I can disable onnx and use with pt only ?

The true reason here is thop not onnx, try downgrade the package.


Add marginal distribution routines

For low-weight operators it is more efficient to marginalize the input distribution (counts) over those qubits with non-identity operators only.  This gives a much smaller state space over which to mitigate and makes things much faster.
This PR adds routines for marginalizing distributions given indices or operators as strings.  Optionally a qubit to bit mapping can be passed, which will also be marginalized so that it can be directly used in apply_correction

On hold for next Qiskit release, to make use of the rust version of the marginals

Ok, this is now using the Qiskit version of marginal_distribution.  It would be nice to have https://github.com/Qiskit/qiskit-terra/issues/8283 solved, but it is not a blocker as you can use lists everywhere to accomplish the same thing.


Verify method returns true even after changing the signature

Hello,
Why verify method returns true even after changing the signature char at the end?
I'm using the following code,
generate random key pair-
const bitcoin = require("bitcoinjs-lib");

 keyPair = bitcoin.ECPair.makeRandom();
 // get the private key
 const privateKey= keyPair.privateKey.toString("hex");
 // get the public key
 const publicKey = keyPair.publicKey.toString("hex");
//// get the address from the public key

 // generate the sha256 of Public Key
 const pbSha256Digest = calculateSHA256(publicKey);

 // generate the ripemd-160 of the sha256 of the public key
 const pbRipemd160Digest = calculateRipemd160(pbSha256Digest);

 // prefix 0x00 to pbRipemd160Digest, 0x00 is the main network id
 const pbMainNetwork = "00" + pbRipemd160Digest;

 // ------ Below process is to calculate the address checksum
 // generate the sha256 of the pbMainNetwork
 const pbMNSha256Digest = calculateSHA256(pbMainNetwork);

 // generate the sha256 of pbMNSha256Digest to get the address checksum
 const pbSHA256AddressCheckSum = calculateSHA256(pbMNSha256Digest);

 // first 4 bytes of the pbSHA256AddressCheckSum is the address checksum
 const addressCheckSum = pbSHA256AddressCheckSum.slice(0, 8);

 // concat the address checksum to the pbMainNetwork. This is the 25-byte binary Bitcoin Address.
 const addressInBinary = pbMainNetwork + addressCheckSum;

 const addressBytes = Buffer.from(addressInBinary, "hex");

 // Convert the result from a byte string into a base58 string using Base58Check encoding.
 const address = bs58.encode(addressBytes);

Sign message using private key and message -
    const keyPair = bitcoin.ECPair.fromPrivateKey(
      Buffer.from(privateKey, "hex")
    );
    // sign the message using the private key, convert it into base64 format
    const  signMessage = bitcoinMessage
      .sign(message, keyPair.privateKey, keyPair.compressed)
      .toString("base64");

Verify message using below-
     const bitcoinMessage = require("bitcoinjs-message");
      isVerified = bitcoinMessage.verify(message, address, signature);

Using the above methods below is the generated data -
"privateKey": "9f4a91e71fd597976908fa07243ea96cd6f0f3e09f3652c5fab52570733575d7",
"publicKey": "02c478cc171b516f4890b71f60eb52d757cb5cb8d86fbc799935504d28072872d1",
"address": "1CTy3z89FBQ7MAkbindJEeSkXGsK1JRy6N"
"message":"Hello Bitcoin"
"Signature":"HyjpzUupgE5xNzRgCgFzXWzTbYhxFeu6txf1x4wMAgWVRMPM3DCrz99IX3pENwcGF5K1j7bG1pnqOaUPqR4tfVE="
In the end, I'm verifying the signature using the below data and its giving true response,
"message": "Hello Bitcoin",
"signature": "HyjpzUupgE5xNzRgCgFzXWzTbYhxFeu6txf1x4wMAgWVRMPM3DCrz99IX3pENwcGF5K1j7bG1pnqOaUPqR4tfVE=",
"address": "1CTy3z89FBQ7MAkbindJEeSkXGsK1JRy6N"
But even if changing the signature to below one also its giving true only,
HyjpzUupgE5xNzRgCgFzXWzTbYhxFeu6txf1x4wMAgWVRMPM3DCrz99IX3pENwcGF5K1j7bG1pnqOaUPqR4tfVE===
HyjpzUupgE5xNzRgCgFzXWzTbYhxFeu6txf1x4wMAgWVRMPM3DCrz99IX3pENwcGF5K1j7bG1pnqOaUPqR4tfVE

Your code does not show the issue.
Perhaps this is a misunderstanding of the flag byte? Similar to #18 ?
I can't tell, since your code does not show me the issue.

As per the comments in https://github.com/bitcoinjs/bitcoinjs-message/issues/18, this issue is resolved. Then why I'm facing this?

= is optional padding, with or without it the encoded data is the same.

With this, if I do the changes like below then also it's giving a true result. Is this because of same reason?
........ at the end or start
///// at the end or start
abc at the end
1234 at the end
at the start or end
^^^^, &&& , ***,((( in the mid of sign msg

That's how base64 decoding works. Your issue has nothing to do with this library.
> Buffer.from('aGVsbG8=','base64').toString('utf8')
'hello'
> Buffer.from('aGVsbG8=.....','base64').toString('utf8')
'hello'
> Buffer.from('.....aGVsbG8=.....','base64').toString('utf8')
'hello'
> Buffer.from('aGV......sbG8=','base64').toString('utf8')
'hello'
> Buffer.from('aGVsbG8=abc','base64').toString('utf8')
'hello'
> Buffer.from('aGVsbG8=1234','base64').toString('utf8')
'hello'

Oh. Thank You so Much for the details.


[docs] Design system kit getting started grid not uniform

Describe the bug
The grid under the "Getting Started" section is not of uniform size.
Steps to reproduce

Go to https://ux.redhat.com/get-started/design-system-kit/
See that the grid below the "Getting Started" section is not uniform

Expected behaviour
Each section should be of uniform size
Screenshots

Operating System (OS)
macOS
Browser
Chrome
More browser information
No response
Additional Info
No response

@coreyvickery should these be rh-cards?