I'm developing a Zendesk App on my Windows 10 machine using WSL/Ubuntu to run zat.
It's been working fine for six months or so. I'm guessing a new years update blew it up. Anytime I run a zat command now I'm seeing the following error. Has anyone seen this issue and know how to resolve?
Top level ::CompositeIO is deprecated, require 'multipart/post' and use `Multipart::Post::CompositeReadIO` instead!
Top level ::Parts is deprecated, require 'multipart/post' and use `Multipart::Post::Parts` instead!
/home/####/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/faraday-0.17.5/lib/faraday/upload_io.rb:65: warning: constant ::UploadIO is deprecated
/home/####/.rbenv/versions/2.6.9/lib/ruby/gems/2.6.0/gems/faraday-0.17.5/lib/faraday/upload_io.rb:66: warning: constant ::Parts is deprecated
I tried uninstalling/installing the zat gem with no change.
Welcome to stack overflow. An incident has affected local development in ZAT and zcli yesterday. It has since been resolved.
Related
I have set my development environment on another system with everything new. Latest android studio version, flutter, and everything.
Now I am trying to run my previous code but the whole code is full of errors. The code was working perfectly fine on my previous version of flutter. I didn't get the issue with this new version.
Here is the screenshot of my code:
1
Anyone please help me to solve this issue. This is my whole project with some other code as well and there are nearly 70 files of code.
I would be thankful if anyone can help me with this issue.
Thanks
Well, you semed to have had a really, really old version of Flutter (and Dart) before.
One way to fix those errors is to read and understand the guide to null safety and modify your project. It will be better after you do it, null safety is an amazing feature.
If you don't have the time to do that right now, you should be able to just constrain your SDK to an earlier version. Quite frankly I'm surprised that you got null safety out of the box because your project should have had constraints. If you set the minimum SDK version to something smaller than 2.12 you should be running without that feature. But please note that sooner or later you will need to enable it, you cannot stay on an obsolete version. So maybe it's time to do that now.
This is because Dart introduced null safety. You have to make your code null safe by using various annotations and operators. You can learn more about them here -
https://dart.dev/null-safety
https://dart.dev/codelabs/null-safety
https://dart.dev/null-safety/understanding-null-safety
I have been working on building react-native apps for a few months now. Recently, I have been getting this error when I run my app for iOS. Looks like an error in the Scene.js file. Has anyone faced a similar issue? Any directions here is much appreciated.
I am using react-native version 0.40.0.
[Update] Did some research and found the root of this issue. The issue has been since the new version of react-native-router-flux version 3.39. There is an issue raised on their github page as well https://github.com/aksonov/react-native-router-flux/issues/1926
I have an application that is part Polymer Dart and part AngularDart 2, and I'm getting a large string of errors when I attempt to do a pub get. The errors I'm getting look like this:
[DirectiveProcessor]:
Failed with 27 errors
Error 1: line 1, column 1 of lib\common\PaxHeader\service.dart and parts: Expected a method, getter, setter or operator declaration
17 gid=234561557
^^
My Angular dependency is set in my pubspec.yaml as angular2: "2.0.0-beta.22" and I am running Dart 1.19.0 on Windows 7 64 bit. I found this issue on Github:
https://github.com/angular/angular/issues/5599
This seems to be the exact same problem, but was marked as fixed in alpha48 last December, so I'm not exactly sure what could be happening here. I have verified with other teams that this issue is not present on OSX.
Is there something I am missing?
Issue https://github.com/angular/angular/issues/7395 goes into greater detail on what the root cause is - the build process for the bundled archive sometimes includes things that Windows tar handlers don't know how to handle, and the devs at Google don't notice because they're working in Unix. It was supposedly fixed permanently in that issue, but that was before the Dart version branched off to be independent and maybe they didn't copy that bit of setup.
I suggest reporting a new issue at https://github.com/dart-lang/angular2/issues and linking to the old 7395.
apologies for cluttering up stackoverflow with what is clearly a trigger.io support request.
I've created 2 native modules, and uploaded multiple versions of each. However, when I try to add one of these 'private modules' to one of my trigger.io apps via the Toolkit.app, I get an error 'You cannot activate this module as it has no uploaded versions.' - which is clearly not the case.
anybody have any insight on why this error is happening?
or more to the point are there any trigger.io staff on SO who can get this fixed / or explain to me where I might be going wrong?
This is a bug in how we're comparing versions in the 3.3.62 version of the Toolkit - we'll be deploying a new version with a fix later today.
Sorry for the inconvenience!
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
How to fix PHP errors related to timezone (function.strtotime and function.date)
I installed PhpDocumentor-1.4.0a2.tgz which is the latest version on CentOS 5.7 64, my current lamp installation is with php 5.3.3
I am using
pear install phpDocumentor-alpha
after installing it the following is shown:
Warning: strtotime(): It is not safe to rely on the system's timezone settings.
You are required to use the date.timezone setting or the
date_default_timezone_set() function. In case you used any of those methods and you are still getting
this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST'
instead in PEAR/Validate.php on line 454 and 486
I know this error has to do with the version of php, and 5.3 is not compatible with PEAR.
I did not mind because the instalation process gave me an ok.
The I tried to generate the documentation, it is not being completed for some reason.
$ phpdoc -c /usr/share/pear/data/PhpDocumentor/user/bigstep.ini
PHP Warning: strftime(): It is not safe to rely on the system's timezone settings.
You are required to use the date.timezone setting or the date_default_timezone_set() function.
In case you used any of those methods and you are still getting this warning,
you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST'
instead in /usr/share/pear/PhpDocumentor/phpDocumentor/Smarty-2.6.0/libs/Smarty_Compiler.class.php on line 370
It is a php warning that should not be stoping the documentation generation. But, the process gets in the middle,
and at the end does not generate the files.
it seems that I have to check on those libraries myself. Does anyone have seen this error before, what should I try next to resolve this issue
Set the timezone in your php.ini