Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/binary-amd64/Packages' #84

Closed
hoanphi2201 opened this issue May 24, 2019 · 22 comments

Comments

@hoanphi2201
Copy link

image

Hello. What do I have to do to fix it?

@gargpk
Copy link

gargpk commented May 24, 2019

hey @hoanphi2201

I'm too facing this problem.

here is the details:

Get:6 http://security.debian.org jessie/updates/main amd64 Packages [846 kB]
Err http://deb.debian.org jessie-backports/main amd64 Packages
  
Err http://deb.debian.org jessie-backports/main amd64 Packages
  
Err http://deb.debian.org jessie-backports/main amd64 Packages
  
Err http://deb.debian.org jessie-backports/main amd64 Packages
  
Err http://deb.debian.org jessie-backports/main amd64 Packages
  404  Not Found
Fetched 10.1 MB in 23s (425 kB/s)
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease  Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages  404  Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.
ERROR: Service 'api' failed to build: The command '/bin/sh -c apt-get update && apt-get install -y vim' returned a non-zero code: 100
ERROR: No container found for api_1

found this solution:
https://unix.stackexchange.com/a/508728
can you take a look at this and revert if this worked for you.

@hoanphi2201
Copy link
Author

hoanphi2201 commented May 24, 2019

@gargpk
Can you show me how to do it? I use ubuntu instance google clound
image

@hoanphi2201
Copy link
Author

Did you fix it successfully?

@gargpk
Copy link

gargpk commented May 24, 2019

@hoanphi2201
i tried but was not successful

@hoanphi2201
i did this as follows:

adding these lines of code in the Dockerfile.dev just after LABEL

RUN echo "deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main" > /etc/apt/sources.list.d/jessie-backports.list
#RUN echo "deb [check-valid-until=no] http://archive.debian.org/debian jessie main" > /etc/apt/sources.list.d/jessie.list

RUN sed -i '/deb http:\/\/deb.debian.org\/debian jessie-updates main/d' /etc/apt/sources.list

RUN apt-get -o Acquire::Check-Valid-Until=false update

you can check this thread for more details regarding this issue:
stackexchange
and this one
stackoverflow

@hoanphi2201
Copy link
Author

@gargpk
I also tried it but failed. It took me a long time to find a solution.
I don't know what I should do right now

@gargpk
Copy link

gargpk commented May 24, 2019

@hoanphi2201

i read alot of threads they are suggesting to migrate to debian-stretch from debian-jessie as this is officially deprecated

there are many workaround tried by people, many of them i also tried, none is working.
i think we have to create a docker image for debian-stretch compatible with judge0/api

@hoanphi2201
Copy link
Author

It will be great if you solve it. I wait for a solution from you.

@hoanphi2201
Copy link
Author

Do you encounter this problem? When I use https://api.judge0.com/ on the postman it returns stdout, when it returns null in the application

@gargpk
Copy link

gargpk commented May 24, 2019

have you checked this:
https://api.judge0.com/dummy-client.html
this is working completely fine and so is the:
https://github.com/judge0/api/releases/tag/v1.1.5
in release mode maybe containing all the details and all try this one may be a relief.

@hoanphi2201
Copy link
Author

This version can build on my device, right?

@hoanphi2201
Copy link
Author

I have seen it work

@hoanphi2201
Copy link
Author

#include <iostream>

long unsigned int fib(unsigned int n);

long unsigned int fib(unsigned int n) {
	if (n == 0) return 0;
	if (n == 1) return 1;
	return fib(n-1) + fib(n-2);
}

int main() {
	unsigned int number;

	while (std::cin >> number) {
		std::cout << fib(number) << std::endl;
	}
	return 0;
}

You can test it: language_id: 10

@gargpk
Copy link

gargpk commented May 24, 2019

@hoanphi2201
its working completely fine here is the output

[Request 5/24/2019, 3:47:59 PM] POST http://192.168.1.174:3000/submissions?wait=true
{
    "source_code": "#include <iostream>\n\nlong unsigned int fib(unsigned int n);\n\nlong unsigned int fib(unsigned int n) {\n\tif (n == 0) return 0;\n\tif (n == 1) return 1;\n\treturn fib(n-1) + fib(n-2);\n}\n\nint main() {\n\tunsigned int number;\n\n\twhile (std::cin >> number) {\n\t\tstd::cout << fib(number) << std::endl;\n\t}\n\treturn 0;\n}\n",
    "language_id": "10",
    "number_of_runs": "1",
    "stdin": "5",
    "expected_output": "5",
    "cpu_time_limit": "2",
    "cpu_extra_time": "0.5",
    "wall_time_limit": "5",
    "memory_limit": "128000",
    "stack_limit": "64000",
    "max_processes_and_or_threads": "30",
    "enable_per_process_and_thread_time_limit": false,
    "enable_per_process_and_thread_memory_limit": true,
    "max_file_size": "1024"
}
[Response 5/24/2019, 3:47:59 PM] 201 Created
{
    "stdout": "5\n",
    "time": "0.004",
    "memory": 496,
    "stderr": null,
    "token": "51c108af-d33d-4c3b-80a9-a5cabef00e9a",
    "compile_output": null,
    "message": null,
    "status": {
        "id": 3,
        "description": "Accepted"
    }
}

[DONE 5/24/2019, 3:47:59 PM]

@hoanphi2201
Copy link
Author

Oh, I discovered the problem here. I need setTimeOut for the process of retrieving the returned data. Did I understand correctly?

@hoanphi2201
Copy link
Author

Thank you for your concern. I have done it. we should have a callback when status.description == processing || in queue.

@hoanphi2201
Copy link
Author

@gargpk
Can I send multiple test sets in one submit?

@gargpk
Copy link

gargpk commented May 25, 2019

I don't think so.
we can't!

@gargpk
Copy link

gargpk commented May 25, 2019

this apis production environment is working fine but its dev environment is broken need to fix it soon.

@hoanphi2201
Copy link
Author

@gargpk 413 Request Entity Too Large
Have you met this situation? I need a solution to do it with big test kits

@hermanzdosilovic
Copy link
Member

Hi everybody. I am aware of this problem with buildpack-deps:jessie image and I am working on it.

@pethanin
Copy link

Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/binary-amd64/Packages' - facing same issue.

@hermanzdosilovic
Copy link
Member

This is fixed with Judge0 API v1.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants