From professional translators, enterprises, web pages and freely available translation repositories.
fataalne viga päringu töötlemisel
a fatal error occurred while processing the request
Last Update: 2014-01-18
Usage Frequency: 1
Quality:
Reference:
fataalne viga
fatal error
Last Update: 2014-08-15
Usage Frequency: 1
Quality:
Reference:
viga päringu salvestamisel@ info
error saving request
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
Reference:
bugzilla andis sinu päringu töötlemisel vea, kuid seda vastust pole võimalik töödelda.
bugzilla reported an error when trying to process your request, but was unable to parse the response.
Last Update: 2014-08-20
Usage Frequency: 1
Quality:
Reference:
“kõnealune ajapikendus ei või lisada põhjustavad fataalne viga.
“the extension may not be incorporated as causing a fatal error.
Last Update: 2018-02-21
Usage Frequency: 1
Quality:
Reference:
leian, et see on fataalne viga, olenemata sellest, kumb osapool sellisesse lahendusse usub.
i consider this a fundamental error regardless of which side believes it.
Last Update: 2012-02-29
Usage Frequency: 2
Quality:
Reference:
täisrežiimis, mille saab avada käsuga kdebugdialog -- fullmode, on näha ikka samad silumispiirkonnad, aga hüpikkastist saab korraga valida neist vaid ühe. seejärel saab eraldi määrata erinevat laadi väljundi - informatsioon, hoiatus, viga ja fataalne viga - andmise või mitteandmise ning iga tüübi korral ka määrata, kuhu väljund saadetakse. valikud on järgmised:
in full mode, which is what you get when you start kdebugdialog as kdebugdialog --fullmode, the same list of debugging areas as in plain mode is available, but you can select only one at a time from a drop-down box. you may then independently set the output for various types of messages: information, warning, error and fatal error. for each of these types, you can choose where the messages are sent. the choices are:
Last Update: 2011-10-23
Usage Frequency: 1
Quality:
Reference: