We are currently using the Python 2.7 and Google App Engine NDB client.
Planning to migration from Google App Engine to Google Cloud NDB
As per docs, "google-cloud-ndb" library officially supports for Python 2.7 and Python 3.x as well.
So, we are trying to access the datastore through google-cloud-ndb.
We are facing the below trace which is related to DisturbutionNotFound Error
raise DistributionNotFound(req, requirers) DistributionNotFound: The 'google-cloud-ndb' distribution was not found and is required by the application
In Google App Engine, Python 2.7 doesn't support the use of requirements.txt file. This means you have to install all the modules/libraries you need for your App and deploy it together with your App to production. In your specific case, it means you have to install google-cloud-ndblibrary.
Follow the instructions here to install the libraries you need to run your App
Related
We have our own swift framework REFFramework that is using carthage to import Firebase (analytics and firestore). This is the cartfile in REFFramework:
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseFirestoreBinary.json"
The REFFramework is used in the app also using carthage to import it.
In addition the app itself also imports other modules from firebase (remote config).
This is the cartfile of the app:
git ".../REFFramework"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseAnalyticsBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseFirestoreBinary.json"
binary "https://dl.google.com/dl/firebase/ios/carthage/FirebaseRemoteConfigBinary.json"
As far as I know carthage is designed to fully support this kind of structure. We use other frameworks also embedded in REFFramework like this such as Alamofire.
However we notice a crash in the app that does not happen when we remove the Firebase out of the REFFramework.
So it's clearly todo with the embedding of Firebase in an intermediate Framework.
The crash is happening in "0 __pthread_kill", here is a screenshot of the debugger in xCode 10.3:
I see a remark in the documentation:
Note that the Firebase frameworks in the distribution include static libraries. While it is fine to link these into apps, it will generally not work to depend on them from wrapper dynamic frameworks.
Not sure if this is releated to this issue?
Yep, the Firebase Carthage frameworks include static libraries and can only be linked to other static library frameworks.
I'm using Ubuntu 16.10. Installed Kaa Sandbox and tested with notification demo in terminal. I'm using CCSv7 to program on CC3200. I confused what is correct way to create project in CCS with Kaa SDK generate from Kaa Sandbox. Here is how I do but I can't build project:
Generate SDK and run build by cmake with target platform is cc32xx, I use notification example
Create new project then include Kaa SDK path
Include Kaa file library (*.a): libkaac.a, libextension_user.a, libextension_event.a, libextension_logging.a, libextension_profile.a, libextension_bootstrap.a, libextension_notification.a, libextension_configuration.a, libmbedtls.a, librsa_keygen.a. I'm not sure that need all of them but just include all to prevent error.
Copy some code from kaa_demo.c and blinky demo project to my main.c.
Hit build. Error occur that libmbedtls.a not build for ARM so I go to folder thirdparty and build it. Solved.
Occur another error: Description Resource Path Location Type
#10099-D program will not fit into available memory. placement with alignment fails for section ".cinit" size 0xc41 . Available memory ranges: cc3200v1p32.cmd /demo1 line 75 C/C++ Problem. I try to increase or decrease stack size but not work.
More error: Description Resource Path Location Type
unresolved symbol __assert_func, first referenced in /opt/ti/kaa-sdk/build/libkaac.a demo1 C/C++ Problem. This error occur when missing include library file but it occur in another library file so I dont know how to fix.
Anyone can help me or suggest how to make a project for CC3200 with Kaa SDK, in any IDE. Its take me 2 weeks.
At the moment of Kaa 0.10.0 release the CC32xx sample applications were broken due to the same issue you mentioned in 7). The binary build did not fit into the CC32xx program memory. That is why whole the CC32xx platform was disabled in the Kaa 0.10.0 Sandbox release.
Now, the issue on the GitHub repository is fixed and the CC32xx platform will be re-enabled in the Kaa 0.10.1 Sandbox release (comming soon). So, you can either wait for the Kaa 0.10.1 release or try building the CC32xx application with the CMake from GitHub.
Regarding your question for build from CCSv7 IDE directly you should search for integration of CMake builds into the CCSv7 IDE. Kaa team does not provide such integration for now considering you should use any IDE you prefer for development and build by CMake (manually or from IDE).
We download the Kaa platform source code from git.
We can build it successfully under linux OS.
And we also try to import it by Eclipse.
But, it will show a lot of error after import Kaa project into Eclipse.
Does the develop environment need under linux and need to use other develop tool??
Have anyone can share the guide instruction to help setup the Kaa platform develop environment??
Thank you!!
We try to use IntelliJ IDEA (community version) to import all source from git.
And then, use the "Generates Sources and Updates Folders" function of Maven to generate some source that it need.
After generating the source that lack before and the project can be built successfully.
Finally, we use the package command to generate the rpm and deb file.
Above all operation is on Linux OS.
The Eclipse should also support above operation, but it should be more setting need to set. And it seems more convenient by IntelliJ IDEA.
I'm trying to use the meteor 1.4 beta and wanted advice on the best way to get set-up - I've never used a software beta before and am a bit unsure.
Do I just download the latest file from github? In this case https://github.com/meteor/meteor/releases/tag/release%2FMETEOR%401.4-beta.7
How do I configure the file on my system such that I can use the meteor command in my terminal as normal?
Are there any other things I need to set up or be aware of to use this version?
Create a new project using the recommended (current) Meteor version :
meteor create test
Then upgrade the newly created project to the latest beta available :
cd test
meteor update --release 1.4-beta.7
There you go, the test project is on the latest beta and outside of it you can still use your system-wide Meteor install.
Regarding 1.4 specifically :
The latest dev bundle comes with MongoDB 3.2, if you're upgrading an existing project it will warn you about the need to migrate your database, the easiest way to do so in dev is simply to run meteor reset.
Also, meteor node still points to v0.10.45 but your app will run with v4.4.7 (just console.log(process.version)).
I'm trying to understand what the docs say about the meteor package server.
In addition to Isopacks, the Package Server contains distributions,
which are sets of packages that have been tested together by a release
engineer and that are known to work well together. For example, when
you use Meteor 1.0, you're using the METEOR distribution at release
1.0.
(https://www.meteor.com/services/package-server)
and
Other people can also publish their own distributions to the package
server as well. If developer alice published a distribution called
SPACE-ROCK, you could switch your project to it by typing something
like meteor update --release alice:SPACE-ROCK#1.2.
(https://www.meteor.com/projects)
I know I can browse packages thru meteor search ... or on atmosphere. But the distrubutions are not listed there.
Is there any way to search/list distributions published to the package server?
meteor search will show releases (I believe a 'distribution' is just a release), but from the documentation, I can't find any way to limit it to only show releases. Here's my result, as an example:
> meteor search
.... // literally all of the packages
Matching releases:
CORDOVA-PREVIEW An experimental release of meteor with Cordova support.
GITHUBBLE Release for githubble.meteor.com.
METEOR The Official Meteor Distribution
METEOR-CORE An experimental release of meteor.
WINDOWS-PREVIEW Preview of Meteor on Windows
diegosampaio:METEOR meteor 1.0.0 compatible
ekate:METEOR-SHOW Meteor Shows Things
ekate:REL-TEST test
ekate:TEST Packaging UX Wrangling
glasser:PUBLISHTEST Test release for isopack-cache branch.
glasser:TPS-PREVIEW Preview releases for tool performance and stability work.
glasser:UPDATE-TEST The official Meteor distribution.
konecty:METEOR meteor 1.0.0 compatible
lawshe:FULLPAGE Meteor smart package for FullPage.js. Create full screen pages fast and simple.