float\_ref error when using tf-trt
i use this code:

import tensorflow as tf

import tensorflow.contrib.tensorrt as trt

from tensorflow.python.compiler.tensorrt.trt\_convert import (

trtprecisionmode, trtgraphconverter)

from tensorflow.python.compiler.tensorrt import trt\_convert

config = tf.configproto(

gpu\_options=tf.gpuoption…
this error is caused by some bugs with tensorflow’s freeze graph tool. it can happen when you try to convert a model that was created with a different version of tensorflow, but it also seems to happen randomly.

you can fix it by manually adjusting the bugged nodes:

# load saved model and freeze g…
hi yerhu,

i could imagine, that one of the two following scenarios may cause the issue:

you’re using an outdated version of tk-core. check in your configuration: core/core\_api.yml

you’re using a pipelineconfiguration, which is pointing to a local-path and includes a file like python\_interpreter, i… a couple of things to check:

(1) make sure your file realy exists

(2) your file path does not seem to be correct full path, should it be something like c://users/…

(3) you can also try a relative path, namely, copying your tiff file to the same directory as where you start your jupyter. then, use… this is my first time digging into the processing source code so i hope this helps. the problem you are facing is more of a java problem though than a processing one.

by extending pgraphics you would have to replace the renderer implementations to inherit from your subclass(tgraphics) and not pgrap… that error happens when there's no handle to close. i see you call the 'open()' and you're not getting an object reference error before closehandle(). check your memory.pointerwrite() function to make sure it's not doing a closehandle() prematurely. it sounds like you're calling closehandle() twice. [@najoua.abbaci](/u/najoua.abbaci)

mabye the flow can be adopted to following:

assign:

leftside: drresult (datatype: datarow)

right side:

dt\_datepv.asenumerable.orderby(function ( r ) datetime.parseexact(r(0).tostring.trim, “dd.mm.yyyy”, system.globalization.cultureinfo.currentuiculture.datetimeformat)).last()

so… actually, ftl does not care about #. instead, everything ftl cannot parse as valid config setting is ignored. so using ; everywhere is fine as well. prepending with ä would equally work, too, etc.

additional hint: pi-hole v6.0 will change the config file format to [toml](https://toml.io). the existing pihole-ftl.conf … thanks for your comment!

i definitely should’ve used mkshell, not sure why i wasn’t. it does seem to produce a different error:

make: entering directory '/build/source/doc/manual'

xsltproc --nonet --param section.autolabel 1 --param section.label.includes.component.label 1 --param html.stylesheet … [image] nirgrahamuk:

observe({

fv <- req(input$filter\_var)

td <- req(tabledata())

updateselectizeinput(inputid = "filter\_vals",

choices = pull(td,fv))

})

observe({

fv <- as.character(req(input$filter\_var))

td <- req(table… The best way to  

do it is to rename the file then force a replication from a known good server.


If it is not too  

corrupted you can do an updall -r and it will rebuild the indexes.


Try running  

nfixup.exe against it. If that doesn’t work, try ncompact -c against it.


Note: ncompact  

exists in all workstation installs. nfixup is not part of the client — you can  

copy it off a server that runs at a similar NBotes version.


Make sure to use  

the -c option with compact (ncompact -c whatever\your\file.nsf)


In case it didn’t assist you, then you may use professional recovery software <http://www.nsf.openfiletool.com/> NSF Open File Tool This error has to do with the XFree86 config file. I'm not sure about Mandrake, but in Windows it's at /etc/X11/XF86Config or /etc/X11/XF86Config-4



This file can be hand-edited or configured via a program such as Xconfigurator or xf86config (I think those are the names of the programs? if you have them installed)



What video card are you using? If you're using an Nvidia based card, go to the Linux section of [nvidia.com](http://nvidia.com/) and there is a detailed text file with everything you need to know about this file to get it to work.