Non recoverable error

tar: не может открыть: нет такого файла или каталога

Я пытаюсь следовать инструкциям здесь, чтобы установить Jetty на Ubuntu, но у меня возникает проблема, когда я пытаюсь использовать tar.

Но когда я пытаюсь

Я получаю ошибку

Что я делаю неправильно? (Я тоже пробовал как root но это не помогло)

РЕДАКТИРОВАТЬ

Ни один из предложенных ответов не работает для меня. Ниже я копирую свои попытки из командной строки. Что я делаю неправильно?

4 ответа 4

Использование тире и порядок аргументов, кажется, проблема:

Изменить: следующие две команды, кажется, работают для меня:

Конечно, вам нужно заменить tar tzf на tar xzf и, возможно, придется добавить sudo .

Проблема может быть в позиции аргумента f . Предполагается, что имя архива должно следовать за аргументом f , поэтому ошибки говорят о невозможности открыть файл с именем z .

Команда sudo wget http://eclipse.org/downloads/download.php?file=/jetty/stable-9/dist/jetty-distribution-9.1.0.v20131115.tar.gz&r=1 неверна по двум причинам:

1. Ссылка на скачивание должна быть указана, так как вы используете &, который является особенным в Bash. См. Http://www.gnu.org/software/bash/manual/bash.html#Definitions.
2. Вы используете старую мертвую ссылку. Переход на страницу загрузки Jetty ( http://download.eclipse.org/jetty/ ) показывает http://eclipse.org/downloads/download.php?file=/jetty/stable-9/dist/jetty-distribution-9.1.3.v20140225.tar.gz&r=1 как правильная ссылка для скачивания.

Затем вы должны использовать следующую команду:

Аргумент -O помогает в выводе на правильное имя файла.

После этого tar xvf jetty-distribution-9.1.3.v20140225.tar.gz должен работать.

Здесь опция x использует режим извлечения, v показывает дополнительную информацию (имя извлекаемого файла), а f указывает, что следующий аргумент — это путь к архиву, который нужно извлечь.

Вам не нужна опция z которая указывает сжатый архив gzip так как tar распознает его автоматически.

Наконец, — предыдущие варианты устарели AFAIK.

Другое дело: я не рекомендую использовать sudo когда это действительно не нужно. Здесь вы просто хотите скачать и распаковать архив, который не нуждается в привилегиях суперпользователя, и вы можете сделать это в своем домашнем каталоге. Это позволяет избежать ошибок, которые могут привести к серьезным проблемам, особенно когда вы действительно не знаете, что делаете.

Источник

Prisma crashes with This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic. #2754

Bug description

Prisma panics on a valid query.

I make this Prisma call:

In the query, I request last_sent_user which is a relation based on the field last_sent_by (full schema shown later).

• This isn’t the default name for the relation which would be users ; however, last_sent_user is more representative of what the relation is.
• The last_sent_user related record does exist. I checked it manually and the related users.id exists in the database.
• If I remove last_sent_user from the query, it executes without error.
• The book relation works fine.

As can be seen in the error, Prisma is expected to receive a value for last_sent_user :

How to reproduce

I’ve provided details below but a minimal reproduction may be hard to create because my other relations work fine. I don’t know what is special about this one that makes it crash other than the naming is a little different (however, other relations are renamed to use a singular form in many cases).

Expected behavior

Should not panic.

Prisma information

These are the immediate models related to this query.

Environment & setup

• OS: Mac OS
• Database: PostgreSQL
• Prisma version: 2.0.0
• Node.js version: v12.16.2

The text was updated successfully, but these errors were encountered:

The was solved by removing @prisma/client and adding it again.

As the solution was unclear, I added issue #2753 to improve the error message.

The panic occurs again in the same place last_sent_user in production. Since it is in the same place, it feels like this is something more than just a one time corruption.

We are going live in two weeks.

Would appreciate somebody taking a look or offering some suggestions on how to prevent this when our app is live.

Does this always crash or just sometimes?
Can you maybe a dump of your SQL with the data that is causing this? Then it would be simple for us to reproduce.

When I run it, it always crashes.

These are the unedited SQL logs from Heroku.

Some of the queries are executed in the same Promise.all in parallel on the client. The API accepts a graph, and executes each branch of the graph in its own Promise which it then combines together at the end using Promise.all . I mention this in case parallelism in Prisma is part of the issue.

Based on the log, Prisma is looking for a users.id in 61 which I can confirm does not exist in the database. This explains the error PANIC: Application logic invariant error: received null value for field last_sent_user which may not be null

Prisma appears to be reusing the id from books.id which is 61 and which I can confirm is the correct id and that it exists.

I can also confirm that inside the database, the last_sent_by value is 13 and not 61 .

Note that shelves.id is also set to 13 and that is correct. In the implementation, shelves and users share the same id if the shelf belongs to the user which in the case of this query, it does.

Can you maybe a dump of your SQL with the data that is causing this? Then it would be simple for us to reproduce.

The logs I in the previous post includes the SQL and the input data. Scroll to the right to see them.

It does not show the result data because I don’t know how to make that work on Heroku but you can see from the SQL query and input data where the error comes from.

To break it down, this query is run:

From there, this query is run:

We can see that some time after that, the books which is specified as a nested select in the query is selected:

In this query, it can be seen that the id parameters is 61 . This is the correct return value as can be seen in the database screenshot here:

Then later still, we see this query being executed against the users table which is the join to last_sent_user :

The issue with this query, however, is that it is using the value 61 in its where clause but that is the value for book .

Again, looking at the data in the database:

We can see that the last_sent_by column has the value 13 . So somewhere during this query, the value from book_id was being used instead of the value from last_sent_by .

For additional clarity, the relation last_sent_user connects to the users table through the column last_sent_by as can be seen in the Prisma schema:

Can you please export the SQL database schema and the data in it into a .sql file so we can recreate your database ourselves and run the code you provided on that?

I will try to recreate this in a way that is transportable. For clarity, the code works on my Mac at the moment. My last deploy to Heroku did not but I changed the app to not make that query.

Reproducibility is important to bug fixes. It’s just inconsistent in how it gets to the broken state and I’m unclear how it got into that state. Any insight on things I can try?

It might be related to upgrading. I feel like it worked before and then started failing after an upgrade. On the Mac, I fixed the issue by removing then adding @prisma/client. On Heroku, it rebuilds each time I deploy and it continued to fail after a redeploy. however, I wonder if it’s a caching issue in their build process.

I remember reading that prisma uses a . file of some sort in newer versions in node_modules and I wonder if that is playing a part.

If you can give us a SQL file with the schema and some data we can totally try to reproduce this ourselves — maybe it already works on the first try with the code snippets you provided above.

@janpio How should I send the file to you? I have it ready.

@thesunny You can email it to «schemas@prisma.io». If you want us to sign an NDA, we can also do that.

Done. Let me know if there are any issues with it.

@thesunny I restored the pg_dump that you have sent but it looks like it is missing some data. The query posted here is for book_share_email_invitations but the restore doesn’t have that model.

Can you please send me a complete data? Also, I would prefer it to be a a simple pg_dump without -Fc flags as that export it in a custom format which is not very convenient to modify if I want to change the roles.

Also, as always, try with the latest dev version once to make sure if this was not already addressed in some other form.

Oh, my apologies. I used the dump feature in Heroku which I don’t have much experience with.

I will try again.

No problems at all. Take your time 🙂

I resent the file using pg_dump as requested. Note that I mistakenly read that you wanted it WITH the -Fc flag so the first version I sent you is wrong. I then sent the correct version in a follow up email.

@thesunny I was unable to reproduce the error:

I used the following code:

Can you please try again with the latest version? 🙏

Источник

This is non recoverable error

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I’m getting this error and not sure how to proceed yet. As seen in the screenshot below I’ve had 282 out of 285 successful replications.

The three errors are as follows.

Hyper-V suspended replication for virtual machine ‘XAVIER’ due to a non-recoverable failure. (Virtual Machine ID 554B5DA9-139C-4207-80B9-5E7E9CD8FAD3). Resume replication after correcting the failure.

Hyper-V could not replicate changes for virtual machine ‘XAVIER’: The device does not recognize the command. (0x80070016). (Virtual Machine ID 554B5DA9-139C-4207-80B9-5E7E9CD8FAD3)

Hyper-V suspended replication for virtual machine ‘XAVIER’ due to a non-recoverable failure. (Virtual Machine ID 554B5DA9-139C-4207-80B9-5E7E9CD8FAD3). Resume replication after correcting the failure

Answers

Virtual machine Replication Status will be shown as Critical — suspended and administrator intervention is required. Examples would include a broken VHD chain or the Replica virtual machine is in an invalid state.

You may encounter such error if there is:

Network Authentication Error, Authorization Error, or Virtual Machine not found. In the case of a standalone Hyper-V server, this is a non-recoverable error and administrator intervention is required. If the Replica server is a Hyper-V Failover Cluster with the Replica Broker configured, the same logic is applied as indicated above (Network Error — Replica Broker).

You may refer to this article to troubleshoot Hyper-V replica issues:

Источник

Rust Errors

Errors in Rust

Errors in Rust are nothing but logics or syntaxes which are illegal and cause an interruption in the normal working of the program.

There are two different types of errors, which are:

• Recoverable Errors : This kind of error can be handled by the compiler or by the user. And thus, the program execution can flow normally, after the necessary steps are taken to overcome the error.
• Non-recoverable Errors : This kind of error can be handled by the user, which means that the user can not recover from the error. There are no ways with the help of which one can recover from the errors. And so, the program execution will stop in the error.

This has to be noted that, in other programming languages there are methods where we can use exceptions for handling errors. But in Rust, there is no such facility. Rust handles errors in a different way.

• For recoverable errors, it returns an enum — Result .
• For non-recoverable errors, it will call the macro panic!() .

Non-Recoverable Errors in Rust

This kind of error can be handled by the user, which means that the user can not recover from the error. When this kind of error occurs, then the macro panic! is automatically invoked by the Rust compiler and the program execution stops.

It may be noted that the macro can also be called from the user’s side also.

Program to show the use of the macro panic!()

In the above program output, we are have intentionally invoked the macro panic()! to see how the program execution stops.

Program Output :

In the next example, we shall see how an error will automatically call the macro panic!() . Here, we shall refer to an array index that is not present.

A program which abort the program(macro panic!() is called in the background automatically)

In the above program, we have declared an array whose size of 3. This array has an index starting from 0 to 2. Now when we tried to print the element from an index 4, which is not present, we are creating an error for the program flow and it is non-recoverable. Therefore, the macro panic()! is called to abort the program.

Program Output :

Using panic!() intentionally

This can be explained by considering the example below, where we use the macro panic!(), if the program flow is transferred in an else block of an if-else program.

Program Output :

Recoverable Errors

Recoverable Errors are those errors that can be handled by the compiler. When this kind of error occurs, then the enum — Result .

The enum Result has two variants- T and E which are generic parameters. If in case, there are no errors then the variant T will be returned. Otherwise, the variant E will be returned.

Syntax :

Program to search for a file

In the above program we are willing to search for a file, which is not present inside the directory. And thus it is an error. Now the way to handle the error is to execute the Err part, and so that the error is handled and then the program flows normally.

Program Output :

unwrap() & expect()

unwrap()

The function unwrap() returns a panic if an operation fails along with printing the default error message. Otherwise, it will return the actual result.

A program to check whether a number is even

In the above program, we have concatenated the function unwrap() , with the function in operation check() . The function check(), returns an enum that has two default variants- OK and Err. When the check functions return a true, that is when the number is even, then the OK part is executed and the keyword true is returned.

On the other hand, when the check() function returns a false, then the macro unwrap() is automatically invoked to print the error message.

Program Output :

Case1 : When the number is even (TRUE case)

Program Output :

Case 1: When the number is not even (FALSE case)

expect()

Using the function expect() , we can generate custom message for an error. This is helpful, because the compiler generated messages are somewhat very technical and may not be always understood by everyone.

A program to check whether an integer is even (FALSE Case)

Program Out (When the function check() returns a false)

Источник

fn main() {
   panic!("Hello");
   }

thread 'main' panicked at 'Hello', rust-error-panic.rs:2:4
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

fn main() {
   let a = [1,2,3];
   a[4]; 
}

error: index out of bounds: the len is 3 but the index is 4
 --> rust-error-panic-calling.rs:3:4
  |
3 |    a[4];
  |    ^^^^
  |
  = note: #[deny(const_err)] on by default

error: aborting due to previous error

fn main() {
    let number = 123;
    if number == 123 {
      println!("Number is same");
      }
      else {
        panic!("Number is not same. Panic is invoked");
      }
    }

thread 'main' panicked at 'Number is not same. Panic is invoked', rust-error-panic-invoke.rs:7:9
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

enum Result<T,E> {
   OK(T),
   Err(E)
}

use std::fs::File;
fn main() {
  let file = File::open("my_pic01.jpg");
  match file {
    Ok(file) => {
        println!("file found {:?}", file);
      },
      Err(err) => {
        println!("file not found {:?}", err);
      }
  }
  println!("Hello! The program is still in flow.The error was handled properly");
}

file not found
Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }
Hello! The program is still in flow.The error was handled properly

fn main() {
  let result = check(8).unwrap();
  println!("Our check returned a {} result", result);
}
fn check(no: i32) - > Result < bool, bool > {
  if no % 2 == 0 {
    return Ok(true);
  } else {
    return Err(false);
  }
}

thread 'main' panicked at 'called `Result::unwrap()` on
an `Err` value: false', srclibcore
esult.rs:997:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

fn main() {
  let result = check(81).expect("Error, this is a custom error message");
  println!("Our check returned a {} result", result);
  println!("Hello, there was no error. Let us continue..");
}
fn check(no: i32) -> Result < bool, bool > {
  if no % 2 == 0 {
    return Ok(true);
  } else {
    return Err(false);
  }
}

C:UsersHPcheckersrc>rust-error-expect
thread 'main' panicked at 'Error, this is a custom error message: false', srclibcore
esult.rs:997:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

0 results