Can't publish GitBook, the error message is vague and without detail - gitbook

I'm trying to publish something that I've written to my GitBook page using the GitBook GUI on Ubuntu 14. To do that I'm just going to book > publish as > book-name
But this error appears:
This doesn't happen often, but it looks like something is broken. Hitting the back button and trying again might be your best bet. If that doesn't work you can head back to the homepage.
There might be more information on our status page which is reporting All Systems Operational.
The book names already been set up as a thing on the website, and I'm signed in on both programme and website.
I'm not sure what I'm meant to do.

The current GitBook version 1.1.1 (and previous versions) have a bug/issue reported which relates to this error message and its vagueness.
https://github.com/GitbookIO/editor/issues/185
The problem you are experiencing is likely due to an invalid value specified for the Version when you try to publish.
Although the publish dialog does provide a hint:
Version must be a semver (ex: 0.0.1, 0.4.5, ...)
there is nothing in the error message to help you understand that this Version value is source of the error.
If you provide a value for Version in the format suggested by the hint in the dialog, I believe you will no longer encounter this error.

Related

I can't get Catel.sln to load its projects

I cloned the catel repo, opened Catel.sln in VS 2019, and switched to master branch. None of the projects load. In the Solution output window I'm getting messages like
\Catel.Tests.TestReferenceC\Catel.Tests.TestReferenceC.csproj : error : The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluated. The path is not of a legal form.
for each project in the solution. The message also mentions
.nuget\packages\msbuild.sdk.extras\2.0.54\Sdk\Sdk.props
It looks like the problem is in msbuild.sdk.extras. How do I fix it?
Please check out the section in the readme about building Catel:
https://github.com/catel/catel#building-catel
MSBuild.Sdk.Extras is required as sdk for the projects (allows multi-targeting and more). The most important thing is to restore packages. Once packages (especially MSBuild.Sdk.Extras) are restored, it should work as expected.

Node.js installation (windows installer) terminates prematurely on windows 10 64-bit

After going through a windows 10 re-installation due to a windows update crashing my laptop, I was left with re-installing many applications. One of them being node.js. When I tried to install it through the windows installer, I kept getting 'setup wizard ended prematurely because of an error message'. I am not sure what the problem is. I used x64 version which is what my OS is and there is no nodejs folder in program files. When I logged the installation this message popped in a lot of the lines has no eligible binary patches. Before the no eligible lines there were error logs such as:
'WixSchedInternetShortcuts: Error 0x8007000d: failed to add temporary row, dberr: 1, err: Directory_'
'WixSchedInternetShortcuts: Folder 'ApplicationProgramsFolder' already exists in the CreateFolder table; the above error is harmless'
If that is not enough information please advice me on how to send the full logs without spamming huge text in the thread. Thank you.
The MSI log file:
https://gist.github.com/luki2000/ab00476127d54aaf610d8bda84d40a64
Maybe try to search the log for "value 3" as explained by Rob Mensching in his blog. Doing so will find the locations in the log file that describe errors of significance.
Many people use dropbox, gdisk or similar to post logs. Some put it on github (just a sample log for OP, leaving in for reference). Check that last link, is that the same problem you see perhaps? (search for "value 3" as explained above - without the quotes of course). Looks like there is an error creating an Internet shortcut. Perhaps that is a Windows 10 problem? I will take a quick look.
I am betting Bob Arnson knows what this problem is outright. He will probably give us the real answer, see below for my workaround.
The correct thing to do overall, would probably be to communicate the problem back to the Node.js guys so they can fix the problem once and for all.
UPDATE: Maybe see if this answer helps you: node.js installer failing with 'CAQuietExec Failed' and 1603 error code on Windows 7. Essentially un-check Event tracing(ETW) in the setup's feature dialog - or you can try to launch the MSI from an elevated command prompt.
UPDATE: There seem to be two Internet shortcuts configured for this MSI in the WixInternetShortcut table. I would just create a transform to remove these two shortcuts and try a reinstall. If you feel bold and fearless and like to break the law, you can delete the two rows from the table and just save directly to the MSI itself. This is never the right thing to do if you are a deployment specialists. The original MSI is sacred, but if this is for your own system and you need to get something done, that would work. Then you just install the MSI direct afterwards. Otherwise you can install the transform after creating it with a simple command line:
msiexec.exe /i node-v8.11.2-x64.msi TRANSFORMS="C:\MyTransform"
You can create the transform using Orca, InstEd or SuperOrca or any commercial tool that supports creating transforms.
In case you don't know, transforms are little database fragments that are applied to the original MSI (which is also a database under the hood). After the transform is applied the in-memory version of the MSI is the MSI + the changes from the transform.

Crafter CMS 3.0 - deleted status pages

After start Crafter CMS Authoring mode successfully, I create a new site as instructed at Crafter CMS Your First Website, but the results are not the same as the description of the tutorial, all pages have status "Deleted". See the screenshot here.
Please let me know what's wrong and how to solve it. Thanks.
It's difficult to know what the issue is here because there is no log file (link does not work) but I do notice on the image a couple of things:
Everything is showing a deleted status, typically if the item is NOT in the repository it does not show at all. The deleted status typically shows up on historical dashboards.
Everything is lower cased/filename rather than internal name from the file
Hieu:
Anything you can tell us like:
OS version
Java version
Steps you took / how to reproduce
Other servers running for anything else?
I believe the correct answer to this is that there is an error in the Windows binary. I tried installing on 3 different Windows machines and had the same issue as the original poster. Plus the OP stated that the Linux distribution worked for them. I hope the Crafter people will look at this and make the correction.

Error on installing any module in DotNetNuke 5.6.3

When I upload any module in System->Extensions in DotNetNuke 5.6.3, running on a Windows 2008 R2 server, IIS 7.5, after the correct module information is displayed and I hit next, I receive the error message
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object.. ---> System.NullReferenceException: Object reference not set to an instance of an object.at DotNetNuke.UI.WebControls.FieldEditorControl.CreateEditor()at DotNetNuke.UI.WebControls.FieldEditorControl.DataBind()at
DotNetNuke.UI.WebControls.PropertyEditorControl.AddFields(Table tbl)at
DotNetNuke.UI.WebControls.PropertyEditorControl.CreateEditor()
[...]
and the module is not installed. The file system of the web has not been touched, so I thought it was a permission problem, but even allowing user Everyone to do everything doesn't help (after making sure the ApplicationPoolIdentity user has been allowed full access as well).
Any hint is appreciated.
The manifest of the module is valid (it's Dynamic Registration 4.1).
Update: Installation steps (note: I am using a German installation of Windows 2008, so some translations might not be accurate)
Log in as Hosts Super User (Admin)
Either navigate to System->Extensions or System->Module Definitions (System might be identical to Hosts) - I tried both
In System->Extensions, click Installation assistant for extensions
Select file to upload
Click next
Description of uploading package appears correctly - click next
Error message Object reference not set to an instance of an object. appears on top of the page. Log View shows stack trace as partly displayed above.
What can cause an error in DotNetNuke.UI.WebControls.FieldEditorControl.CreateEditor()?
What kind of permissions could be missing?
Update 2: By step-by-step debugging, I found out that the view state is broken, for some reason. The method BindPackage() in DesktopModules\Admin\Extensions\Install.aspx.vb doesn't find the current Installer Package. I have not yet found out why the viewstate breaks. It is enabled and huge in the rendered page source.
As described in Update 2, the page's viewstate is lost in DesktopModules\Admin\Extensions\Install.aspx.vb. Simply replacing ViewState by Session works (but this workaround may be lost after the next DNN update).
Update (in case someone has a similar issue):
The DNN container that was used had its viewstate turned off! This results in all kinds of weird behaviour, but it took time to track that error. Now it's obvious.

Build Process failed with maven package

I am working on a maven project to build a simple utility api. The same source code when build on my office win XP machine, was successful. Now i am at home and working with same source code on CentOS machine. Here the build process failed strangely. The error it reports is ideally in my points should we warning message. As shown below.
[ERROR] com.vsd.Provider:[12,240] The import java.util.Set is never used
Can you please give me some idea, where can I look into?
It's hard to say without seeing your POM but the error reported looks like a violation of the Checkstyle rule UnusedImports (or something equivalent). Maybe this verification is triggered because of a setting defined in a profile that is not activated on your CentOS machine (as I said, hard to say). Anyway, to fix it, remove the unused import.
The problem was with the plug in being used to compile, It was a bug a shown below.
http://jira.codehaus.org/browse/MCOMPILER-118

Resources