• user warning: Got error 28 from storage engine query: SELECT DISTINCT t.* FROM drupal_term_node r INNER JOIN drupal_term_data t ON r.tid = t.tid INNER JOIN drupal_vocabulary v ON t.vid = v.vid LEFT JOIN drupal_forum_access fa ON t.tid = fa.tid LEFT JOIN drupal_acl acl_fa ON acl_fa.name = t.tid AND acl_fa.module = 'forum_access' LEFT JOIN drupal_acl_user aclu_fa ON aclu_fa.acl_id = acl_fa.acl_id AND aclu_fa.uid = 0 WHERE ((fa.grant_view >= 1 AND fa.rid IN (1)) OR fa.tid IS NULL OR aclu_fa.uid = 0) AND ( r.vid = 24747 )ORDER BY v.weight, t.weight, t.name in /var/www/dikutal.dk/modules/taxonomy/taxonomy.module on line 632.
  • user warning: Got error 28 from storage engine query: SELECT DISTINCT node.nid AS nid, node.title AS node_title, node.language AS node_language, node.type AS node_type, node.vid AS node_vid, node_revisions.teaser AS node_revisions_teaser, node_revisions.format AS node_revisions_format, node_data_field_date.field_date_value AS node_data_field_date_field_date_value FROM drupal_node node LEFT JOIN drupal_content_field_date node_data_field_date ON node.vid = node_data_field_date.vid LEFT JOIN drupal_term_node term_node ON node.vid = term_node.vid AND (term_node.tid = 9 OR term_node.tid = 10 OR term_node.tid = 12 OR term_node.tid = 19 OR term_node.tid = 18 OR term_node.tid = 13 OR term_node.tid = 16 OR term_node.tid = 17 OR term_node.tid = 11 OR term_node.tid = 14 OR term_node.tid = 15) LEFT JOIN drupal_node_revisions node_revisions ON node.vid = node_revisions.vid INNER JOIN drupal_node_access na ON na.nid = node.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 1 AND na.realm = 'book_page_access_view') OR (na.gid = 1 AND na.realm = 'forum_access'))) AND ( ((node.status <> 0) AND (node.type in ('event')) AND (term_node.tid IS NULL)) AND (DATE_FORMAT(ADDTIME(node_data_field_date.field_date_value, SEC_TO_TIME(7200)), '%Y-%m-%d') >= '2014-10-22') )ORDER BY node_data_field_date_field_date_value ASC LIMIT 0, 3 in /var/www/dikutal.dk/sites/all/modules/views/includes/view.inc on line 771.

What The FileReadingExceptionIf you’re a programmer, or even just a bro-grammer, check this comment on the official .NET documentation out:

Offset and position parameters wrong in intellisense
Its *really* annoying when the Intellisense documentation is wrong when you are coding … it has been a frustrating exercise to figure this out. As a previous poster mentioned, the Intellisense doco for the offset and position parameters are swapped around. The parameter descriptions as shown on this page are correct.
[Source]

.NET intellisense pulling a dick move

Screencap of the “sligtly” misleading intellisense description from VS2010.

And let me just add that I would only stumble upon comedy gold like this after having had the most inexplicable out-of-bounds exception ever. Here is some simplified code that will throw an out-of-bounds exception on the 2nd read when reading from a file of 8 bytes or more:

using System;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using KeyValueBase.Interfaces;
using System.IO;
using System.IO.MemoryMappedFiles;

public class SomeClassName
{
public void Init(String indexfile)
{
uint[] keypair = new uint[4];
var mmName = Path.GetFileName(indexfile);
using (var mStream = new FileStream(indexfile, FileMode.Open)){
using (var mmf = MemoryMappedFile.CreateFromFile(
mStream,
mmName,
mStream.Length, MemoryMappedFileAccess.Read, null,
HandleInheritability.None, false)){

using (var a = mmf.CreateViewAccessor(
0, mStream.Length,
MemoryMappedFileAccess.Read)){
for (int i=0; i /* The wrongly documented function that leads
* to the most inexplicable out-of-bounds
* exception.
* The following line is well behaved */
a.ReadArray(i, keypair, 0, 4);
/* This line on the contrary does something
* "funny" with your program, try it! */
// a.ReadArray(0, keypair, i, 4);
}
}
}
}
}
}

I would of course be the last to want to generate negative prejudice towards the entire subspecies of .NET dependent bro-grammers, but I think it is fair to assume that this error would have been patched a long time ago if they in general were more prone to and proficient in dealing with binary data ;)

Handlinger