Not finding documentation with the list of runtime supported currently, other than customizing runtime
I get this error:
Step #0: gcr.io/gcp-runtimes/aspnetcorebuild#sha256:f5552a5efdaf278a3124ea10fd1c9636b09fc9f98f9e620cbd71279797576b3f
Step #0: The app requires .NET Core runtime version 5 which is not supported at this time.
Take a look on this post (https://github.com/GoogleCloudPlatform/google-cloud-visualstudio/issues/847), it's the same case as yours were they report working fine 'til version 2.0.X (Last comment is from last year).
In the documentation, even though is not specified that is the last supported version, it makes a code example with core version 2.1: The .NET Runtime.
In that same document is provides a another link with a [list of images provided by google to build .NET containers] (http://gcr.io/google-appengine/aspnetcore) were the higher version used is 3.1.
Unfortunately, it seems to be no list (as is) of supported version in the documentation.
Related
I’m currently on CakePHP 3.5
My ISP is forcing us off PHP 7.2 onto either 7.3 or 7.4
There are some errors from the Cake core code in 7.3, mostly related to compact() (a known breaking change), but I think there are others as well. I’ve seen references to these errors, but I can’t find a definitive version of Cake to target.
What is the minimum CakePHP version needed for PHP 7.3 or PHP 7.4?
That shouldn't really matter too much, if you'd upgrade to 3.6 you could as well just upgrade to 3.9 while your at it, besides fixes it's mostly deprecations and new features, and a handful of behavior changes.
That being said, 7.3 has been added to the test runs in 3.6.13, and 7.4 was added in 3.8.7, so the latest 3.6/3.8 would be your minimum.
When submitting Excel add-in to the office store. Which version of the Excel API should be referenced in the manifest file?
We have experienced being rejected because we didn’t refer to the newest version of the Excel API.
But if our Excel add-in supports an older version of the API. Shouldn't we be referencing this?
There are several aspects to the versioning of the Office.js library.
First, there is versioning of the actual JavaScript source files. Fortunately, this part is pretty simple: you always want the latest and greatest of the production Office.js, which is conveniently obtainable through our CDN: https://appsforoffice.microsoft.com/lib/1/hosted/Office.js. The files are also shipped as a NuGet package to allow corporate firewalled development, but the NuGet may lag a few weeks behind the CDN -- and in any case, any Store-bound add-in is required to reference the CDN location. So, in terms of Office.js versions, there isn't really versioing there: there is simply the one and only evergreen, frequently-updated, always-back-compatible, Store-required CDN version.
(While on the subject of CDNs: we also have a beta CDN, available at https://appsforoffice.microsoft.com/lib/beta/hosted/Office.js. This one is great to testing newly implemented-but-not-yet-officially-stamped-as-done features, which you'll find in our Open Specs: http://dev.office.com/reference/add-ins/openspec. However, any new APIs therein should be considered as strictly "beta", and they may well be renamed, re-grouped, or postoponed -- so your app should not rely on them, as we explicitly reserve the right to break pack-compat on the beta branch. An API is not "done" until it is listed in IntelliSense ande Documentation as complete, until it's available on the Production CDN, *and until its isSetSupported returns true -- more on that momentarily).
The more interesting bit for versioning are the actual API capabilities that are offered by each host. The Office.js library will have the latest JS code to be able to run them, but older hosts might not be able to support some of the functionality. For example, if you look at https://dev.office.com/reference/add-ins/requirement-sets/excel-api-requirement-sets, you will see that the 2016 wave of Excel APIs -- grouped under the "ExcelApi" requirement set -- has had three versions to date: 1.1, 1.2, and 1.3. ExcelApi 1.1 was what shipped with Office 2016 RTM in September 2015; 1.2 shipped in early March 2016; and 1.3 shipped just recently, and is in the process of being rolled out to the CDN. Each API set version has a corresponding Office host version that supports this API set (for most APIs, there have to be both JS and host-side changes; it's fairly rare that something can be a purely-JS addition). The version numbers are listed in the table, and there are links below the table to find a mapping from build numbers to dates.
Each of the API set versions contain a number of fairly large features, as well as incremental improvements to existing features. The topic for each requirment set, such as the link above, will provide a detailed listing of each of those features. And as you're programming, if you are using the JavaScript or TypeScript IntelliSense, you should be able to see the API versions for each of your APIs displayed as part of the IntelliSense:
You can use the requirement set in one of two ways. You can declare in the manifest that "I need API set ExcelApi 1.2, or else my add-in doesn't work at all" -- and that's fine, but then of course you aren't able to service older hosts, and so your add-in won't even show up there. Alternatively, if you add-in could sorta work in a 1.1 environment, but you want to light-up additional functionality on newer hosts that support it, you can use the manifest to declare only your minimal API sets that you need (e.g., ExcelApi 1.1), and then do runtime checks for higher version numbers via the isSetSupported API. Neat ways to get environment (i.e. Office version) has a very detailed explanation of this isSetSupported API-checking.
Hope this helps!
I would like to use Autofac in my Sitecore project with Solr,
I have set next code to global.asax
<%#Application Language='C#' Inherits="Sitecore.ContentSearch.SolrProvider.AutoFacIntegration.AutoFacApplication" %>
but i see an error
Method not found: 'Void Autofac.RegistrationExtensions.RegisterModule(Autofac.ContainerBuilder, Autofac.Core.IModule)'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.MissingMethodException: Method not found: 'Void Autofac.RegistrationExtensions.RegisterModule(Autofac.ContainerBuilder, Autofac.Core.IModule)'
I have checked AutoFac version and it is correct 3.5.2 like in Sitecore.ContentSearch.SolrProvider.AutoFacIntegration
What should I do to set up it correct in term of Sitecore.
This issue happens because Sitecore's Solr support package relies on an old Autofac version (3.1.5 or earlier) where the method builder.RegisterModule() was still defined in Autofac.RegistrationExtensions. Newer Autofac versions have a similar method defined in the class Autofac.ModuleRegistrationExtensions.
Without Sitecore recompiling the Solr/Autofac integration dlls, unfortunately, there are only two ways around this:
Use another DI library;
Write your own Solr/Autofac integration.
This issue is still present in the Solr support package shipped with Sitecore 8.2.
I have registered this issue with Sitecore Support.
Edit: Sitecore replied that the support of Autofac 3.2 and later is on the wish list. To track the status of this request, you can use the reference number 94626.
Have you removed all the Lucene config files and added in all the solr config files in the App_Config/Include.
You will also need to drop in all the Solr Dlls as shown below.
I'm using MSpec to drive some automated UI tests using Selenium WebDriver. Much like the examples I found online. I'm having problems getting it to take screenshot when the test fails.
I saw a comment on another issue where it works because they have a ResultSupplementer in the sample web specs. However, ResultSupplementer does not seem to exist in the latest version of Mspec (0.9.1).
Is there a different way to do this in the latest version of mspec? Ultimately, I'm going to generate HTML reports as TeamCity artifacts and include the screenshot on any failing specs.
I've updated the samples for the latest version of MSpec (in short, you need to implement ISupplementSpecificationResults yourself).
I've also merged the solutions and converted the MVC project to Nancy. You'll find that there's a bit more infrastructure-related code that grew over the last couple of years and works around various things, like
status codes 4xx and 5xx logged by IIS Express
IIS and Chrome Driver ports bound by other processes
page objects access the web driver with a high-level API
I use Paket for dependency management because it's far more powerful than plain NuGet
All that said, you need to run msbuild.exe mspec-samples.sln and then All-Specs.cmd. I've also checked that a TeamCity build creates screenshots.
Can any one tell me liferay 6.1.2 ce ga3 on tomcat 7 and solr 4.6 on tomcat 7 are compatible?
Used the solr web portlet avaible from liferay market.
I am working on this from last 3 days and i am still getting version issues,executing query issues ,SolrCore 'collection1' is not available issues, CommonsHTTPSolrServer even after following lot of suggestion.
I tried all permutation regarding the jars.
slf4j-api-1.6.6
slf4j-log4j12-1.6.6
slf4j-simple-1.6.6
solr-common-1.3.0
solr-core-4.6.0
solr-solrj-4.6.0
httpclient-4.3.1
httpcore-4.3
httpmime-4.3.1
I also raised this issue on liferay support forum : https://issues.liferay.com/browse/LPS-42758
No they are not compatible (out of the box).
But it is doable, at least it is with Solr 4.4.0 and 4.5.1, so I would guess with Solr 4.6.0 also.
General steps to make it work:
solr-web
download latest solr-web plugin (source) for 6.1.x
modify dependacies (see below)
modify source files (resolve compilation errors)
modify solr-spring.xml (if needed)
modify schema.xml (look at both liferay's and solr version, and "merge" (what makes sense) them)
List of jars
commons-codec-1.6.jar
commons-io-2.1.jar
httpclient-4.2.3.jar
httpcore-4.2.2.jar
httpmime-4.2.3.jar
noggit-0.5.jar
portal-compat-shared.jar
slf4j-api-1.6.1.jar
solr-solrj-4.5.1.jar
wstx-asl-3.2.7.jar
zookeeper-3.4.5.jar (probably could be removed, I did not)
Additional (provided) jars not packaged in war
portal-service-6.1.1.jar
util-java-6.1.1.jar
servlet-api-2.5.jar
Specifically for CommonsHTTPSolrServer ClassNotFoundException
in BasicAuthSolrServer constructor you should use HttpSolrServer, instead of CommonsHTTPSolrServer