วีดีโอ

@@ulfark7934 in collab under runtime menu you can find an option change runtime type, there you can see default "CPU" selected , I think you need to change that to GPU and try

Notice for cold drinks it even sub categorised large and small

This is the response from second image : { "products": [ { "brand": "Lay's", "type": "Snack packets", "count": 4 }, { "brand": "Kurkure", "type": "Snack packets", "count": 5 }, { "brand": "Gopal", "type": "Papdi Gathiya snack packets", "count": 3 }, { "brand": "Teddy Money", "type": "Snack packets", "count": 3 }, { "brand": "Funtastik", "type": "Moon Chips snack packets", "count": 2 }, { "brand": "Gillette Vector", "type": "Razors", "count": 1 pack (multiple individual units visible) }, { "brand": "Unbranded", "type": "Plastic disposable cups", "count": 1 pack } ] }

@@CenkKose-ks9us not sure why that behaviour is happening may be try rebooting the tv and see if it fixes it

If you are able to get the USB debugging toggle ON then you can skip the prompt and see if from your terminal whether you are able to do an adb connect with the IP or not, in the UI if you are not seeing adb just use the IP of the tv to connect.

when doing adb connect IP , you will see the prompt again

@@devashishpriyadarshi6366 My tv box hasn't network debugging option. Can this cause all of these problem?

@@CenkKose-ks9us are you able to see developer options? If developer options is there USB debugging should also be there. In smart TVs based on OS other than android the option might not be present

The main branch might get update, refer to ths branch for exact code from teh video: github.com/devashish234073/wifi-devices-in-local-network/tree/making-api-call-to-update-instead-of-reloading

The main branch might get updated , refer this branch for exact same code as the above video : github.com/devashish234073/wifi-devices-in-local-network/tree/initial-page-reload-to-refresh-data

@@ggg9gg other than better computer you can use cloud vms with better specs. For example t2.xlarge instances in AWS , you can use it and terminate it after you are done. Since t2.xlarge does not come under free tier you will be charged for it even during free tier period. However if you use it for few hours charge will be very low.

Bro will i able to run this 16 gb ram ryzen 7 octa core processor with gpu 6 gb rtx 3050

@@mohammad-xy9ow yes, it will work with better response time than shown in this video

@@Harini-f7c yes if you switch to your local runtime it will run the code against you local python installation

For screenshot please refer comment from this video: www.linkedin.com/posts/devashish-priyadarshi-96554112b_improved-the-script-injection-logic-for-the-activity-7226790394280173568-Qsla?

APIs available against any AI model is mostly paid with free versions have limits. May be you can create an ec2 using this github.com/devashish234073/ui-for-ai/blob/main/cloudformation-no-gpu-qwen2.json and then you can directly use the ollama apis which are listening on port 11434 as you can see in this template I have already kept the 11434 port open which is to interact with the ollama apis. You can find the ports open in the "SecurityGroupIngress" part of the template. And to access it you need to do the curl or write equivalent client code to do this: curl localhost:11434/api/generate -d '{"model": "qwen2:0.5b","prompt": "Write a poem on goat in 10 words"}') Here you will replace the localhost with the public IP of your EC2 instance Even the "<PUBLICIP>:9999/generate" that UI is calling that is a wrapper over the ollama api so you can even use that, you can get its details from the network tab of the browser's dev tools.

Note: you will still pay for the ec2 or gcp compute instance but that will be comparatively lesser if you are running it against light weight model like quen2 and terminating the instance when you are not using it. Even quen2 one requires at least t2.small type instance which is not in free tier.

(32,9.5)

This video is after implementing the fix : www.linkedin.com/posts/devashish-priyadarshi-96554112b_created-a-cloudformation-template-that-setup-activity-7225027301741146112-E8SW?

Tried a t2.large instance with llama3.1 model but startup script failed with error: pulling 87048bcd5521... 81% ▕████████████ ▏ 3.8 GB/4.7 GB 69 MB/s 12s^[[?25h Error: write /home/ec2-user/.ollama/models/blobs I tried to ssh to the instance and pull manually then got this: Error: write /home/ec2-user/.ollama/models/blobs/sha256-87048bcd55216712ef14c11c2c303728463207b165bf18440b9b84b07ec00f87-partial: no space left on device ubuntu@ip-10-0-1-9:/var/log$ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 7.6G 7.6G 0 100% / tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 1.6G 876K 1.6G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock /dev/xvda15 105M 6.1M 99M 6% /boot/efi tmpfs 794M 4.0K 794M 1% /run/user/1000 ubuntu@ip-10-0-1-9:/var/log$ vi cloud-init-output.log

I might have to attach an additional volume

This is the video after attaching a 15GB volume: www.linkedin.com/posts/devashish-priyadarshi-96554112b_created-the-other-template-to-install-llama31-activity-7225252941673156608-S8g3?

Here's the response I got : curl localhost:11434/api/generate -d "{\"model\": \"llama3.1\",\"prompt\": \"Why is the sky blue?\"}" {"model":"llama3.1","created_at":"2024-07-30T04:15:08.0926584Z","response":"The","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:08.3555334Z","response":" sky","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:08.6283079Z","response":" appears","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:08.8860595Z","response":" blue","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:09.1865226Z","response":" to","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:09.4849016Z","response":" us","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:09.7824486Z","response":" because","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:10.0341468Z","response":" of","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:10.3007863Z","response":" a","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:10.5504437Z","response":" phenomenon","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:10.8221666Z","response":" called","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:11.2341383Z","response":" scattering","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:11.5670524Z","response":",","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:11.8733136Z","response":" which","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:12.1689381Z","response":" occurs","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:12.4342679Z","response":" when","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:12.6927458Z","response":" sunlight","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:12.9862022Z","response":" interacts","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:13.3482728Z","response":" with","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:13.6833401Z","response":" the","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:13.9920272Z","response":" tiny","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:14.3078334Z","response":" molecules","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:14.6498076Z","response":" of","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:14.9607043Z","response":" gases","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:15.2677077Z","response":" in","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:15.601236Z","response":" the","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:15.9127104Z","response":" atmosphere","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:16.2127908Z","response":".","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:16.5424011Z","response":" Here","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:16.8758314Z","response":"'s","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:17.1994567Z","response":" why","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:17.5266942Z","response":": ","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:17.8386617Z","response":"1","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:18.1556406Z","response":".","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:18.4738938Z","response":" **","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:18.8085976Z","response":"Sun","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:19.1559211Z","response":"light","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:19.5318295Z","response":"**:","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:19.8837797Z","response":" The","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:20.2609939Z","response":" sun","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:20.59175Z","response":" emits","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:20.9072251Z","response":" white","done":false} {"model":"llama3.1","created_at":"2024-07-30T04:15:21.2382555Z","response":" light","done":false}

Not immediately but in my future projects with microservices I will integrate xray then I will reply to this with the video. For now can you take a look at how AWS_XRAY_DAEMON_ADDRESS environment variable is used to reach a remote xray domain? you will have one EC2 in which xray daemon will be installed and others will talk to same host using the environment variable. Also make sure security group is properly configured so that communication between instances is allowed

Even there is a "AWSXRay.setDaemonAddress" method you can explore this too as a starting point you can read this stackoverflow.com/questions/61728733/aws-xray-daemon-locally-unable-to-connect-xray-using-xray-daemon-from-my-app

Currently I am working on the reimplementing an angular version of the application so the change will be delayed. The angular version progress can be seen at github.com/devashish234073/honest-social-net/tree/angular-frontend-node-express-backend

😀

I haven't tested it in apple devices but see if the tab is having access to camera or not. Also once try in chrome if you are using some other device

Also s3 does not allow all the files to be downloaded from the console at once. However it can be done using aws cli. you can do it by running the below for your bucket: aws s3 sync s3://tempu-folder .

you can have your services running in same ec2 if they are running in different ports, they will still showup but incase you need to do tracing across multiple ec2 instances in that case you will need to have xray daemon service running only in one instance and other instances sending the traces to the same instance remotely

Even for a springboot application you will need to add the same xray sdk dependencies in your pom file and need to install the xray daemon in the ec2 instance the same way as shown in the video.

Also make sure you test the application by running it in the ec2 instance only. Locally xray tracing parts will not work

Will u upload the developer services integration with springboot

You can try the change runtime option to use a GPU, I read somewhere that in the free version of clab notes can run for at most 12 hours continuously. Also when changing the runtime of the the GPU option was selectable while others were not probably those are for the pro version

Pydroid let's you install jupyter notebook, it runs locally within your phone you can use the localhost url to connect from your phone's browser. It's also possible to have jupyter notebook running in your PC and your phone connect to the url by being in the same network like by using same wifi in this case however you need to replace the localhost part of the url with the 192. series ip of your laptop

Not sure if there is a direct integration like lambda but I think having xray daemon installed in the images that are used in the cluster will be the first step I believe then just like with ec2 instance you will have to assume the xray role.

Not sure if there is a direct integration like lambda but I think having xray daemon installed in the images that are used in the cluster will be the first step I believe then just like with ec2 instance you will have to assume the xray role.

Sometimes it takes time for first time traces to appear, if its still not coming after a long wait try seeing if any error is there in the xray daemon log file it will be some file in the /var/log directory try looking for a file like /var/log/xray-daemon.log or something with xray in name in the /var/log

make sure your jupyter notebook is installed properly, the localhost url that is printed while launching it if you paste that in browser url and if that works then it will woork in google colab too without any error