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
Related
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.
I am trying to add auto update support to my electrom-app using electron-updater(electron-builder version), and it has gotten to the point where it starts to download the update but the download progress just decreases and increases infinitely afterwards. After checking the logs, it says there is a sha512 checksum mismatch, and that it got an incorrect SHA512 value. I tried to solve it by checking some previous issues and trying applying those but they didn't work. I read that it might be because of my code signing techniques(I use my EV Code signing cert to code sign my app after I make the executable using a sign tool command). To try and solve this, I tried integrating it with electron builder using sign.js, but that did not work, since it would try to sign the .exe before it even existed. Additionally, I tried going into the latest.yml and manually changing the sha512 values of the update and the original software to match, but that didn't make a difference either. What can I do, and what exactly does this error mean?
Here is info about my project if that helps.
Error Code
Error in auto-updater. Error: sha512 checksum mismatch, expected <long_encrypted_value>, got <different_long_encrypted_value>
Electron-Builder Version: 22.9.1
Node Version: 16.7
Electron Version: 18.2.0
Electron Type (current, beta, nightly): Current
Electron Builder Version: 4.3.9
Target: Windows
Hi I am needing to get a swift package version at runtime. How would this be executed? Best if possible to complete through the command line.
Assuming that when you say "through the command line" you mean "using Swift code", you will need to expose the version in some way, like a global constant. Then you can have script that changes the value this constant and also the package version (i.e. git tag).
Note that if you distribute a framework, and store its version in its Info.plist, then Xcode will change that version when your clients upload their app to the app store. (You can use this workaround if that what you're after.)
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.
Whenever I tried to change CC and CPP in build.sh(ImportedSources/VLCKit/MobileVLCKit/ImportedSources/vlc/extras/package/ios)
This error comes
"Cannot pull with rebase: You have unstaged changes.
Please commit or stash them."
What is the right way to change CC and CPP path? I am trying to build VLC for iOS.
But "C compiler not working message" comes every time I build for device(for simulator it works fine). I found an answer from VLC forum that this might be due to xcrun points to wrong compiler (https://forum.videolan.org/viewtopic.php?f=36&t=117736).
But I can't change path in build.sh:( . Is there another way to deal with this error.
Where can I change the compiler path so that my C compiler works. I have searched a lot for this error, still no luck. Please provide some guidance.
Thanks,
Sibinesh M.C
Delete the existing and repull.
Next time just check that you are using zsh or iTerm2 (recommended by VLC). Also check the path expected by script file is same as yours. If not add by sudo.
I also faced the same issue, but setting the path by sudo does the job for me.