THIS is not a duplicate question!
In my app, I have collections directory (in project root) with files (every file corresponds to one collection). My tempates (in client/templates/...), of course, use collections. Everything perfect with one small exception. One of my collections is undefined but the rest is ok. Every collection is defined in the same directory and in the same directory level. Where is the problem?
EDIT: I tryed inserting collections inside lib. Not works. I tryed deep nesting. Not works.
EDIT: Tell me, why I have 2 downvotes. Downvotes are for good for nothing questions, this question may help in future another Meteor users. So, why are you downvoting this quetion?
Bug has interesting roots. I'm using fedora 21, and in theese times, Chrome has bug which causes complete freeze (1-5 hours). This bug has many Linux distributions. After I restarted chrome after freeze, the error vanished. So, the result is that Chrome has two bugs instead of one :)
EDIT: No. It's premature conclusion. It works only for a while but then it failed again. In Chrome and in Firefox too. I'm really confused.
Related
I stumbled upon an issue when I recently switched to VSCode as editor.
I have several projects that have a full (medium-complex+) autotool
setup and they all work fine. However I discovered that the makefile plugin for VSCode in order to initialize itself (and finding all dependencies and targets) starts by running
make --dry-run --always-make
as first time initialization. This throws the makefile (or actually the
re-config) into an endless loop re-running "configure" (since the targets are never resolved to disk).
I have also confirmed this behavior with the smallest possible autoconf/automake
setup. I can also kind-of understand why this happens (and it seems make
have an internal way to discover this exact situation with the special
variable MAKE_RESTARTS that could possible be used to detect a cyclic
behavior)
Is there a known best-practice workaround ? or is it even a reasonable expectations that these two options in combination should work? (Good to have a second opinion before I go down the rabbit-hole of reminding myself of all the details I forgot about the magical land of autotools)?
Grakn is awesome, but it also seems very unstable.
The exactly same initial import queries -run in another keyspace- (meaning both were empty before) are only working in one keyframe, the other throws this stupid error:
Error status: 400, error info: facebookCategory doesn't have an 'isa', a 'sub' or an 'id'
In my scheme facebookCategory is defined like this facebookCategory sub category. Category is defined as category is-abstract sub entity.
So - what's wrong with Grakn?
This is a known issue we are working on right now:
when you start migrating data on a keyspace and for some reason your schema or data are wrong/missing, the keyspace sometimes gets corrupted. So when you will try to reload data - even if now everything is correct - you will get that error, again because the keyspace is corrupted.
We are working on this issue internally to solve it as soon as possible.
The error you get is trying to tell you that there is a corrupted schema, we will try to improve it and make it more explicit so that you don't think it's stupid.
We know Grakn is still far from perfect but we can assure you we are just trying to fix as many bugs as possible.
Please try to migrate everything in a clean keyspace, you can find also more issues discussed in our github repo and our support forum
Just wondering if any one might now how to fix this issue.
Every part of the databroker is created and also all the database connectivity is functional.
But once we try to place them together we come up with a error saying cannot create Null Databroker.
The thing that is really strange is that we have databrokers that are basicly the exact same working.
Can any one shine some light on this issue?
We worked on this together today. We did three things to troubleshoot and fix the problem:
we changed the calling workflow so that the dataset is refreshed inside the show-screen tags (previously, this was done before the screen was called).
we refreshed the dataset (a H2 db) and connected the database (before, it showed as pool not open)
we changed the database name to main
It is working now.
"Null databroker" suggests that the broker was not created correctly, although it doesn't look like that was the case since you don't mention having to modify it to get it to work.
In these cases it can be useful to look at the error logs through the admin app to see if there are errors being thrown at some time other than compile time.
Recently, I've noticed strange behavior by Subversion. Occasionally, and seemingly randomly, the "svn up" command will wreak havoc on my CSS files. 99% of the time it works fine, but when it goes bad, it's pretty damn terrible.
Instead of noting a conflict as it should, Subversion appears to be trashing all incoming conflict lines and reporting a successful merge. This results in massively inconvenient manual merges because the incoming changes effectively disappear unless they're manually placed back into the file.
I would have believed this was a case of user error, but I just watched it happen. We have two designers that frequently work on the same CSS files, but both are familiar and proficient with conflict resolution.
As near as can figure, this happens when both designers have a large number of changes to check in and one beats the other to the punch. Is it possible that this is somehow confusing SVN's merging algorithm?
Any experience or helpful anecdotes dealing with this type of behavior from SVN are welcome.
If you can find a diff/merge program that's better at detecting the minimal changes in files of this structure, use the -diff-cmd option to svn update to invoke it.
It may be tedious but you can check the changes in the CSS file by using
svn diff -r 100:101 filename/url
for example and stepping back from your HEAD revision. This should show what changes were made , at what revision and by whom. It sounds like a merging issue I've had before but unfortunately I found myself resolving it by looking at previous revisions and merging them manually too.
I can see where to get an rss feed for the BUG LIST, however I would like to get rss updates for modifications to current bugs if possible.
This is quite high up when searching via Google for it, so I'm adding a bit of advertisement here:
As Bugzilla still doesn't support this I wrote a small web service supporting exactly this. You can find its source code here and a running instance here.
What you're asking for is the subject of this enhancement bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=256718
but no one seems to be working on it.
My first guess is that the way to do it is to add a template somewhere like template/en/default/bug/show.atom.tmpl with whatever you need. Put it in custom or an extension as needed.
If you're interested in working on it or helping someone with it, visit channel #mozwebtools on irc.mozilla.org.
Not a perfect solution, but with the resolution of bug #255606, Bugzilla now allows listing all bugs, by running a search with no criteria, and you can then get the results of the search in Atom format using the link in the bottom of the list.
From the release notes for 4.2:
Configuration: A new parameter search_allow_no_criteria has been added (default: on) which allows admins to forbid queries with no criteria. This is particularly useful for large installations with several tens of thousands bugs where returning all bugs doesn't make sense and would have a performance impact on the database.