#docker build tag

[codeonedigest]

Docker Tag and Push Image to Hub | Docker Tagging Explained and Best Practices

Full Video Link: https://youtu.be/X-uuxvi10Cw Hi, a new #video on #DockerImageTagging is published on @codeonedigest #youtube channel. Learn TAGGING docker image. Different ways to TAG docker image #Tagdockerimage #pushdockerimagetodockerhubrepository #

Next step after building the docker image is to tag docker image. Image tagging is important to upload docker image to docker hub repository or azure container registry or elastic container registry etc. There are different ways to TAG docker image. Learn how to tag docker image? What are the best practices for docker image tagging? How to tag docker container image? How to tag and push docker…

[labexio]

Understanding Docker Playground Online: Your Gateway to Containerization

In the ever-evolving world of software development, containerization has become a pivotal technology, allowing developers to create, deploy, and manage applications in isolated environments. Docker, a leader in this domain, has revolutionized how applications are built and run. For both novices and seasoned developers, mastering Docker is now essential, and one of the best ways to do this is by leveraging an Online Docker Playground. In this article, we will explore the benefits of using such a platform and delve into the Docker Command Line and Basic Docker Commands that form the foundation of containerization.

The Importance of Docker in Modern Development

Docker has gained immense popularity due to its ability to encapsulate applications and their dependencies into containers. These containers are lightweight, portable, and can run consistently across different computing environments, from a developer's local machine to production servers in the cloud. This consistency eliminates the "it works on my machine" problem, which has historically plagued developers.

As a developer, whether you are building microservices, deploying scalable applications, or managing a complex infrastructure, Docker is an indispensable tool. Understanding how to effectively use Docker begins with getting comfortable with the Docker Command Line Interface (CLI) and mastering the Basic Docker Commands.

Learning Docker with an Online Docker Playground

For beginners, diving into Docker can be daunting. The Docker ecosystem is vast, with numerous commands, options, and configurations to learn. This is where an Online Docker Playground comes in handy. An Online Docker Playground provides a sandbox environment where you can practice Docker commands without the need to install Docker locally on your machine. This is particularly useful for those who are just starting and want to experiment without worrying about configuring their local environment.

Using an Online Docker Playground offers several advantages:

Accessibility: You can access the playground from any device with an internet connection, making it easy to practice Docker commands anytime, anywhere.

No Installation Required: Skip the hassle of installing Docker and its dependencies on your local machine. The playground provides a ready-to-use environment.

Safe Experimentation: You can test commands and configurations in a risk-free environment without affecting your local system or production environment.

Immediate Feedback: The playground often includes interactive tutorials that provide instant feedback, helping you learn more effectively.

Getting Started with Docker Command Line

The Docker Command Line Interface (CLI) is the primary tool you'll use to interact with Docker. It's powerful, versatile, and allows you to manage your Docker containers and images with ease. The CLI is where you will issue commands to create, manage, and remove containers, among other tasks.

To begin, let's explore some Basic Docker Commands that you will frequently use in your journey to mastering Docker:

docker run: This command is used to create and start a new container from an image. For example, docker run hello-world pulls the "hello-world" image from Docker Hub and runs it in a new container.

docker ps: To see a list of running containers, use the docker ps command. To view all containers (running and stopped), you can add the -a flag: docker ps -a.

docker images: This command lists all the images stored locally on your machine. It shows details like the repository, tag, image ID, and creation date.

docker pull: To download an image from Docker Hub, use docker pull. For example, docker pull nginx fetches the latest version of the NGINX image from Docker Hub.

docker stop: To stop a running container, use docker stop [container_id]. Replace [container_id] with the actual ID or name of the container you want to stop.

docker rm: Once a container is stopped, you can remove it using docker rm [container_id].

docker rmi: If you want to delete an image from your local storage, use docker rmi [image_id].

Conclusion

Mastering Docker is a crucial skill for modern developers, and utilizing an Online Docker Playground is one of the most effective ways to get started. By practicing Docker Command Line usage and familiarizing yourself with Basic Docker Commands, you can gain the confidence needed to manage complex containerized environments. As you progress, you'll find that Docker not only simplifies the deployment process but also enhances the scalability and reliability of your applications. Dive into Docker today, and unlock the full potential of containerization in your development workflow.

[tutorialsfor]

Fundamentals of Docker for Beginners - Learn Docker from Scratch - Saifosys.com by TutorialsFor #dockertutorials #dockerforbeginners #learndocker Unlock the power of containerization! 🚀 Learn the fundamentals of Docker in this beginner-friendly tutorial. Discover how to simplify your development workflow, improve app deployment, and increase efficiency. In this video, we'll cover: - Comparison of Traditional approach vs Virtualization vs Containerization https://ift.tt/wH9K5dp - Docker basics: Docker Architecture https://ift.tt/jPrafFd What is Docker Daemon? What is Docker Client ? What is Docker Registry ? What is Docker Host ? What is Docker Images ? What is Docker Container ? How to Install Docker on Windows How to Create account on Docker hub How to pull the images from Docker Hub How to Run images and create containers How to list the containers How to list images How to go inside container How to stop container How to start container How remove container How to remove images https://ift.tt/Tl0w6k9 How to build docker image from dockerfile How to run docker image and create container locally How to tag docker images How to push docker images to docker hub registry How to verify the published docker images on docker hub https://ift.tt/08mvztC Perfect for developers, DevOps engineers, and anyone curious about Docker! 💻 Watch now and start containerizing your future! #DockerForBeginners #Containerization #DevOps #DockerTutorial" - #DockerTutorial - #Containerization - #DevOps - #DockerBasics - #DockerTraining - #CloudComputing - #Virtualization - #TechTutorial - #DockerContainers - #DockerImages - #Dockerfile - #DockerHub https://www.youtube.com/watch?v=398al57gwaQ

[qcs01]

Containerization with Docker and Kubernetes: An Essential Guide

Docker and Kubernetes have emerged as foundational tools for containerization and orchestration in the rapidly evolving landscape of cloud-native technologies. This blog post explores their roles, provides setup guides, and highlights key use cases demonstrating their power and flexibility.

Introduction to Containerization

Containerization is a lightweight alternative to traditional virtualization, enabling applications to run in isolated environments. This approach solves many problems related to environment consistency, application deployment, and scalability. 

Docker: The Containerization Pioneer

What is Docker?

Docker is an open-source platform that automates the deployment of applications inside lightweight, portable containers. It encapsulates an application and its dependencies, ensuring it runs consistently across various environments.

Why Use Docker?

Consistency: Ensures the application behaves the same, regardless of where it is run.

Efficiency: Reduces overhead by sharing the host OS kernel.

Portability: Facilitates seamless movement of applications between development, testing, and production environments.

Setting Up Docker

1. Install Docker:

   - Windows & macOS: Download the Docker Desktop installer from [Docker's official site](https://www.docker.com/products/docker-desktop).

   - Linux: Use the package manager. For example, on Ubuntu:

     sudo apt-get update

     sudo apt-get install docker-ce docker-ce-cli containerd.io

2. Verify Installation:

 docker --version

3. Run Your First Container:

    docker run hello-world

Docker Use Cases

- Microservices: Simplifies the deployment and management of microservice architectures.

- DevOps: Streamlines CI/CD pipelines by providing consistent environments.

- Hybrid Cloud: Enables seamless movement of workloads between on-premises and cloud environments.

Kubernetes: Orchestrating Containers at Scale

What is Kubernetes?

Kubernetes, often abbreviated as K8s, is an open-source platform for automating the deployment, scaling, and operation of containerized applications. It manages clusters of containers, ensuring high availability and scalability.

Why Use Kubernetes?

- Scalability: Automatically scales applications based on demand.

- Self-Healing: Automatically restarts, replaces, and reschedules containers when they fail.

- Service Discovery & Load Balancing: Efficiently balances traffic and discovers services without manual intervention.

Setting Up Kubernetes

1. Install Kubernetes Tools:

   - kubectl: Command-line tool for interacting with Kubernetes clusters.

   - Minikube: Local Kubernetes cluster for development.

   # Install kubectl

   sudo apt-get update

   sudo apt-get install -y kubectl

    Install Minikube

   curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64

   chmod +x minikube

   sudo mv minikube /usr/local/bin/

2. Start Minikube:

  minikube start

3. Deploy an Application:

   kubectl create deployment hello-node --image=k8s.gcr.io/echoserver:1.4

   kubectl expose deployment hello-node --type=LoadBalancer --port=8080

   minikube service hello-node

Kubernetes Use Cases

- Complex Applications: Manages applications with multiple, interdependent services.

- CI/CD Pipelines: Enhances automation and reduces the risk of deployment issues.

- Multi-Cloud Deployments: Orchestrates applications across various cloud providers.

Integrating Docker and Kubernetes

While Docker provides the containerization platform, Kubernetes offers robust orchestration capabilities. Together, they form a powerful combination for building, deploying, and managing cloud-native applications.

Example Workflow:

1. Build Docker Image:

   docker build -t my-app .

2. Push to Container Registry:

   docker tag my-app my-repo/my-app

   docker push my-repo/my-app

3. Deploy with Kubernetes:

   kubectl create deployment my-app --image=my-repo/my-app

   kubectl expose deployment my-app --type=LoadBalancer --port=80

Conclusion

Containerization with Docker and Kubernetes revolutionizes how applications are developed, deployed, and managed. By leveraging Docker's simplicity and Kubernetes' powerful orchestration capabilities, organizations can achieve greater agility, scalability, and reliability in their cloud-native journey.

For more details click www.hawkstack.com 

[leanitcorp]

Lightning Web Runtime (LWR) in Salesforce – A Modern Approach to Web Application Development

Discover the capabilities of Lightning Web Runtime (LWR) – a cutting-edge technology by Salesforce that empowers developers to create web applications using popular frameworks like React, Angular, and Vue. With LWR, you can build standalone web apps that operate independently from the Salesforce platform, while seamlessly accessing Salesforce data and services through APIs. This article explores the benefits, limitations, and potential of LWR in revolutionizing web application development.

Benefits of LWR in Salesforce:

Advanced Technology Stack: LWR leverages modern web technologies such as Node.js, Express.js, and Webpack. It provides a lightweight runtime environment, enabling swift development and deployment of web applications.

Developer-Friendly Tools: Take advantage of the Lightning Web Components framework, Salesforce CLI, and VS Code extensions that simplify the building, testing, and deployment process for LWR applications.

Enhanced Security Features: LWR includes robust security measures like user authentication and authorization, HTTPS encryption, CSRF protection, and cross-origin resource sharing (CORS) for seamless communication with external services.

Versatile Deployment Options: Deploy LWR applications on a variety of platforms, including Heroku, AWS, Google Cloud Platform, or on-premises using Docker containers.

Limitations of LWR in Salesforce:

Browser Support: Currently, LWR is only compatible with the latest versions of Google Chrome and Microsoft Edge, which may require additional development efforts to support other browsers.

Functionality Constraints: While LWR allows access to Salesforce data and services through APIs, it does not support all the features available in Salesforce. Notably, Visualforce pages and certain complex Salesforce platform functionalities are not supported.

Availability Restrictions: LWR is currently available as a pilot program exclusively for select customers and partners. Keep in mind that it is not yet generally available and may undergo changes before its official release.

Limited Customization Options: Customizing LWR applications within Salesforce using declarative tools is limited. Comprehensive customizations may require additional development work outside the LWR framework.

Developing Ecosystem: Although LWR employs popular web technologies like Node.js and React, the developer community is comparatively smaller when compared to frameworks like Angular or React.

Lightning Web Runtime (LWR) emerges as a powerful technology from Salesforce, allowing developers to build and deploy web applications using contemporary standards and frameworks. By harnessing LWR, developers can create standalone web applications independent of the Salesforce platform, while leveraging Salesforce data and services through APIs. Stay tuned for the official release of LWR, and explore the immense potential it holds for transforming web application development.

Author: Yashbhal Singh

Read More At: https://leanitcorp.com/lightning-web-runtime-lwr-in-salesforce-a-modern-approach-to-web-application-development/

Tags: Salesforce implementation partners, salesforce nonprofit consultants, top Salesforce consulting firms, best salesforce consulting firms

[this-week-in-rust]

This Week in Rust 543

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Rust Nation UK

Tim McNamara - 4 levels of error handling

Mithun Hunsur - Ambient: A Rust and WebAssembly Runtime for Cross-Platform Multiplayer Games

Alice Ryhl - What it takes to keep Tokio running

Chris Biscardi - Bevy: A case study in ergonomic Rust

Pietro Albini - How Ferrocene qualified the Rust Compiler

Ben Wishovich - Full Stack Rust - Building Rust Websites with Leptos

Natalie Serebryakova - Rustic Persistence: Automating PVC Lifecycles with Rust in Kubernetes

Daniel McKenna - Creating a Text-To-Speech System in Rust

Konstantin Grechishchev - Java and Rust Integration

Heiko Seeberger - EventSourced – async_fn_in_trait in anger

Tim Janus - Let's get interdisciplinary: Rust Design Patterns for Chemical Plants

Marco Ieni - How Rust makes open-source easier

Newsletters

New Meshes, New Examples, and Compute Shaders

Project/Tooling Updates

futures-concurrency v7.6.0: Portable Concurrent Async Iteration

Ratatui v0.26.2

Rust on Espressif chips

Introducing Dust DDS – A native Rust implementation of the Data Distribution Service (DDS) middleware

Announcing the first audited Rust implementation of CGGMP21, the state-of-the-art ECDSA threshold protocol

Nutype 0.4.2 - newtype with guarantees

venndb 0.2.1 - any filters

[ZH|EN] Announcing async-openai-wasm, and thoughts on wasmization and streams

Observations/Thoughts

Climbing a (binary) Tree - Noise On The Net

Why is there no realloc that takes the number of bytes to copy?

Some useful types for database-using Rust web apps

My logging recipe for server side Rust

Rust Walkthroughs

Getting started with SurrealDB using Docker and a Rust client

[video] developerlife.com - Rust testing deep dive with r3bl_terminal_async crate

Research

Rust Digger: 7.53% of crates have both 'edition' and 'rust-version', 11.21% have neither

Miscellaneous

Iced Tutorial 0.12

[video] Infinite Pong in the Bevy Game Engine - Let's Code!

[audio] Release-plz with Marco Ieni

Crate of the Week

This week's crate is venndb, an append-only memory DB whose tables can be build via a derive macro.

Thanks to Glen De Cauwsemaecker for the self-suggestion!

Please submit your suggestions and votes for next week!

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No calls for testing were issued this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Call for Participation; projects and speakers

CFP - Projects

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

mirrord - medschool generated malformed JSON

If you are a Rust project owner and are looking for contributors, please submit tasks here.

CFP - Speakers

Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.

RustConf 2024 | Closes 2024-04-25 | Montreal, Canada | Event date: 2024-09-10

RustLab 2024 | Closes 2024-05-01 | Florence, Italy | Event date: 2024-11-09 - 2024-11-11

EuroRust 2024| Closes 2024-06-03 | Vienna, Austria & online | Event date: 2024-10-10

Scientific Computing in Rust 2024| Closes 2024-06-14 | online | Event date: 2024-07-17 - 2024-07-19

Conf42 Rustlang 2024 | Closes 2024-07-22 | online | Event date: 2024-08-22

RustConf 2024 | Closes 2024-04-25 | Montreal, Canada | Event date: 2024-09-10

If you are an event organizer hoping to expand the reach of your event, please submit a link to the submission website through a PR to TWiR.

Updates from the Rust Project

430 pull requests were merged in the last week

add support for Arm64EC inline assembly (as unstable)

statx probe: ENOSYS might come from a faulty FUSE driver

account for trait/impl difference when suggesting changing argument from ref to mut ref

add REDUNDANT_LIFETIMES lint to detect lifetimes which are semantically redundant

add unsafe to two functions with safety invariants

add const generics support for pattern types

add support to intrinsics fallback body

async closure coroutine by move body MirPass refactoring

avoid a panic in set_output_capture in the default panic handler

be more specific when flagging imports as redundant due to the extern prelude

call lower_const_param instead of duplicating the code

call the panic hook for non-unwind panics in proc-macros

detect borrow checker errors where .clone() would be an appropriate user action

disable Ctrl-C handling on WASM

discard overflow obligations in impl_may_apply

do not add prolog for variadic naked functions

do not allocate for ZST ThinBox (attempt 2 using const_allocate)

don't delay a bug if we suggest adding a semicolon to the RHS of an assign operator

don't do coroutine-closure-specific upvar analysis if tainted by errors

don't even parse an intrinsic unless the feature gate is enabled

don't leak unnameable types in -> _ recover

don't rely on upvars being assigned just because coroutine-closure kind is assigned

fix UB in LLVM FFI when passing zero or >1 bundle

fix invalid silencing of parsing error

fix various bugs in ty_kind_suggestion

generic associated consts: Check regions earlier when comparing impl with trait item def

improve diagnostic by suggesting to remove visibility qualifier

just use type_dependent_def_id to figure out what the method is for an expr

linker flavors next steps: linker features

linker: avoid some allocations in search directory iteration

linker: remove laziness and caching from native search directory walks

make PlaceRef and OperandValue::Ref share a common PlaceValue type

make the computation of coroutine_captures_by_ref_ty more sophisticated

only assert for child/parent projection compatibility AFTER checking that theyre coming from the same place

only collect mono items from reachable blocks

openBSD fix long socket addresses

panic on overflow in BorrowedCursor::advance

propagate temporary lifetime extension into if and match

provide suggestion to dereference closure tail if appropriate

refactor panic_unwind/seh.rs pointer use

remove From impls for unstable types that break inference

rework ptr-to-ref conversion suggestion for method calls

set target-abi module flag for RISC-V targets

skip unused_parens report for Paren(Path(..)) in macro

stop making any assumption about the projections applied to the upvars in the ByMoveBody pass

stop using HirId for fn-like parents since closures are not OwnerNodes

stop using PolyTraitRef for closure/coroutine predicates already instantiated w placeholders

store all args in the unsupported Command implementation

suppress let else suggestion for uninitialized refutable lets

tweak value suggestions in borrowck and hir_analysis

typeck: fix ? suggestion span

use fn ptr signature instead of {closure@..} in infer error

use suggest_impl_trait in return type suggestion on type error

miri: MIRI_REPLACE_LIBRS_IF_NOT_TEST: also apply to crates.io crates

miri: add some basic support for GetFullPathNameW

miri: fix error display for './miri run --dep'

miri: handle Miri sysroot entirely outside the Miri driver

miri: make split_simd_to_128bit_chunks take only one operand

miri on Windows: run .CRT$XLB linker section on thread-end

miri: windows: add basic support for FormatMessageW

stabilize --json unused-externs(-silent)

stabilize (const_)slice_ptr_len and (const_)slice_ptr_is_empty_nonnull

stabilize cstr_count_bytes

implement FromIterator for (impl Default + Extend, impl Default + Extend)

re-enable has_thread_local for i686-msvc

std::net: TcpListener shrinks the backlog argument to 32 for Haiku

show mode_t as octal in std::fs Debug impls

add A: 'static bound for Arc/Rc::pin_in

f16 and f128 step 4: basic library support

add a Debug impl and some basic functions to f16 and f128

specialize many implementations of Read::read_buf_exact

windows: set main thread name without re-encoding

cargo: make sure to also wrap the initial -vV invocation

cargo resolve: Respect '--ignore-rust-version'

cargo resolve: Fallback to 'rustc -V' for MSRV resolving

cargo fix: dont apply same suggestion twice

cargo package: Normalize paths in Cargo.toml

cargo test: don't compress test registry crates

rustdoc: correctly handle inlining of doc hidden foreign items

rustdoc: check redundant explicit links with correct itemid

rustdoc: point at span in include_str!-ed md file

rustdoc: reduce per-page HTML overhead

clippy: module_name_repetition Recognize common prepositions

clippy: fix: incorrect suggestions when .then and .then_some is used

clippy: pin remark-lint-maximum-line-length version

clippy: turn duplicated_attributes into a late lint

clippy: use check_attributes in doc lints

rust-analyzer: add static and const highlighting token types

rust-analyzer: better inline preview for postfix completion

rust-analyzer: wrap/Unwrap cfg_attr

rust-analyzer: VFS should not confuse paths with source roots that have the same prefix

rust-analyzer: fix impl Trait<Self> causing stack overflows

rust-analyzer: fix inlay hint resolution being broken

rust-analyzer: fix: support auto-closing for triple backticks

rust-analyzer: run cargo test per workspace in the test explorer

Rust Compiler Performance Triage

A quiet week, with slightly more improvements than regressions. There were a few noise spikes, but other than that nothing too interesting.

Triage done by @Kobzol. Revision range: 86b603cd..ccfcd950b

Summary:

(instructions:u) mean range count Regressions ❌ (primary) 0.5% [0.3%, 1.4%] 9 Regressions ❌ (secondary) 0.4% [0.2%, 1.1%] 20 Improvements ✅ (primary) -0.6% [-2.5%, -0.2%] 41 Improvements ✅ (secondary) -0.8% [-1.4%, -0.2%] 4 All ❌✅ (primary) -0.4% [-2.5%, 1.4%] 50

1 Regressions, 3 Improvements, 6 Mixed; 5 of them in rollups 62 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

[disposition: merge] Move the Crates.io Team under the Dev Tools team

[disposition: merge] Arbitrary self types v2

[disposition: merge] RFC: Syntax for embedding cargo-script manifests

[disposition: merge] rust-lang org GitHub access policy

Tracking Issues & PRs

Rust

[disposition: merge] Enforce closure args + return type are WF

[disposition: merge] Tracking Issue for io_error_downcast

[disposition: merge] More DefineOpaqueTypes::Yes

[disposition: merge] Tracking Issue for std::path::absolute

[disposition: merge] Tracking Issue for utf8_chunks

[disposition: merge] restrict promotion of const fn calls

[disposition: merge] Fix trait solver overflow with non_local_definitions lint

[disposition: merge] Use fulfillment in method probe, not evaluation

[disposition: merge] rustdoc-search: single result for items with multiple paths

[disposition: merge] Ignore -C strip on MSVC

New and Updated RFCs

No New or Updated RFCs were created this week.

Upcoming Events

Rusty Events between 2024-04-17 - 2024-05-15 🦀

Virtual

2024-04-17 | Virtual (Cardiff, UK) | Rust and C++ Cardiff

Reflections on RustNation UK 2024

2024-04-17 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Camigo (Peter Kehl)

2024-04-18 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-04-21 | Virtual (Israel) | Rust in Israel

Using AstroNvim for Rust development (in Hebrew)

2024-04-23 | Trondheim, NO | Rust Trondheim

Show and Tell in April

2024-04-24 | Virtual + In Person (Prague, CZ) | Rust Czech Republic

#2: Making Safe Rust Safer (Pavel Šimerda)

2024-04-25 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-04-30 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2024-05-01 | Virtual (Cardiff, UK) | Rust and C++ Cardiff

Rust for Rustaceans Book Club: Chapter 5 - Project Structure

2024-05-01 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

2024-05-02 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-05-07 | Virtual (Buffalo, NY) | Buffalo Rust Meetup

Buffalo Rust User Group

2024-05-09 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-05-09 | Virtual (Israel) | Rust in Israel

Rust at Microsoft, Tel Aviv - Are we embedded yet?

2024-05-09 | Virtual (Nuremberg/Nürnberg, DE) | Rust Nuremberg

Rust Nürnberg online

2024-05-14| Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2024-05-14 | Virtual + In-Person (München/Munich, DE) | Rust Munich

Rust Munich 2024 / 1 - hybrid (Rescheduled)

2024-05-15 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Rust Study/Hack/Hang-out

Africa

2024-05-04 | Kampala, UG | Rust Circle Kampala

Rust Circle Meetup

Asia

2024-04-20 | Kuala Lumpur, MY | GoLang Malaysia

Rust Talk & Workshop - Parallel Programming April 2024 | Event updates Telegram | Event group chat

2024-05-11 | Bangalore, IN | Rust Bangalore

May 2024 Rustacean meetup

Europe

2024-04-17 | Bergen, NO | Hubbel kodeklubb

Lær Rust med Conways Game of Life

2024-04-17 | Lyon, FR | Rust Lyon

Rust Lyon Meetup #10

2024-04-17 | Ostrava, CZ | TechMeetup Ostrava

TechMeetup: RUST

2024-04-20 | Augsburg, DE | Augsburger Linux-Infotag 2024

Augsburger Linux-Infotag 2024: Workshop Einstieg in Embedded Rust mit dem Raspberry Pico WH

2024-04-23 | Berlin, DE | Rust Berlin

Rust'n'Tell - Rust for the Web

2024-04-23 | Paris, FR | Rust Paris

Paris Rust Meetup #67

2024-04-24 | Virtual + In Person (Prague, CZ) | Rust Czech Republic

#2: Making Safe Rust Safer (Pavel Šimerda)

2024-04-25 | Aarhus, DK | Rust Aarhus

Talk Night at MFT Energy

2024-04-25 | Berlin, DE | Rust Berlin

Rust and Tell - TBD

2024-04-25 | København/Copenhagen, DK | Copenhagen Rust Community

Rust meetup #46 sponsored by Nine A/S

2024-04-25 | Vienna, AT | Rust Vienna

Rust Vienna x Python User Group - April

2024-04-27 | Basel, CH | Rust Basel

Fullstack Rust - Workshop #2 (Register by 23 April)

2024-04-27 | Stockholm, SE | Stockholm Rust

Ferris' Fika Forum #2

2024-04-30 | Budapest, HU | Budapest Rust Meetup Group

Rust Meetup Budapest 2

2024-04-30 | Salzburg, AT | Rust Salzburg

[Rust Salzburg meetup]: 6:30pm - CCC Salzburg, 1. OG, ArgeKultur, Ulrike-Gschwandtner-Straße 5, 5020 Salzburg

2024-05-01 | Utrecht, NL | NL-RSE Community

NL-RSE RUST meetup

2024-05-06 | Delft, NL | GOSIM

GOSIM Europe 2024

2024-05-07 & 2024-05-08 | Delft, NL | RustNL

RustNL 2024

2024-05-09 | Gdańsk, PL | Rust Gdansk

Rust Gdansk Meetup #2

2024-05-14 | Virtual + In-Person (München/Munich, DE) | Rust Munich

Rust Munich 2024 / 1 - hybrid (Rescheduled)

North America

2024-04-18 | Chicago, IL, US | Deep Dish Rust

Rust Talk: What Are Panics?

2024-04-18 | Mountain View, CA, US | Mountain View Rust Meetup

Rust Meetup at Hacker Dojo

2024-04-24 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

2024-04-25 | Nashville, TN, US | Music City Rust Developers

Music City Rust Developers - Async Rust on Embedded

2024-04-26 | Boston, MA, US | Boston Rust Meetup

North End Rust Lunch, Apr 26

2024-05-04 | Cambridge, MA, US | Boston Rust Meetup

Kendall Rust Lunch, May 4

2024-05-12 | Brookline, MA, US | Boston Rust Meetup

Coolidge Corner Brookline Rust Lunch, May 12

Oceania

2024-04-17 | Sydney, NSW, AU | Rust Sydney

WMaTIR 2024 Gala & Talks

2024-04-30 | Auckland, NZ | Rust AKL

Rust AKL: Why Rust? Convince Me!

2024-04-30 | Canberra, ACT, AU | Canberra Rust User Group

CRUG April Meetup: Generics and Traits

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

There is absolutely no way I can imagine that Option is causing that error. That'd be like turning on the "Hide Taskbar" setting causing your GPU to catch fire.

[...]

If it's not any of those, consider an exorcist because your machine might be haunted.

– Daniel Keep on rust-users

Thanks to Hayden Brown for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

[sandeep2363]

Steps to deploy the docker latest image in AWS

To deploy the latest image in AWS, you typically follow these general steps: Create or Update Your Docker Image: Ensure that you have the latest version of your Docker image ready. This might involve pulling the latest changes from your code repository, building a new image, and tagging it appropriately with a version number or tag like “latest”. Once your Docker image is ready, push it to a…

[kubernetesonline]

Docker and Kubernetes Training | Hyderabad

How to Store Images in Container Registries?

Introduction:

Container registries serve as central repositories for storing and managing container images, facilitating seamless deployment across various environments. However, optimizing image storage within these registries requires careful consideration of factors such as scalability, security, and performance. - Docker and Kubernetes Training

Choose the Right Registry:

Selecting the appropriate container registry is the first step towards efficient image storage. Popular options include Docker Hub, Google Container Registry (GCR), Amazon Elastic Container Registry (ECR), and Azure Container Registry (ACR). Evaluate factors such as integration with existing infrastructure, pricing, security features, and geographical distribution to make an informed decision.

Image Tagging Strategy:

Implement a robust tagging strategy to organize and manage container images effectively. Use semantic versioning or timestamp-based tagging to denote image versions and updates clearly. Avoid using generic tags like "latest," as they can lead to ambiguity and inconsistent deployments. - Kubernetes Online Training

Optimize Image Size:

Minimize image size by adhering to best practices such as using lightweight base images, leveraging multi-stage builds, and optimizing Dockerfiles. Removing unnecessary dependencies and layers helps reduce storage requirements and accelerates image pull times during deployment.

Security Considerations:

Prioritize security by implementing access controls, image signing, and vulnerability scanning within the container registry. Restrict image access based on user roles and permissions to prevent unauthorized usage. Regularly scan images for vulnerabilities and apply patches promptly to mitigate potential risks. - Docker Online Training

Automated Builds and CI/CD Integration:

Integrate container registries with continuous integration/continuous deployment (CI/CD) pipelines to automate image builds, testing, and deployment processes. Leverage tools like Jenkins, GitLab CI/CD, or GitHub Actions to streamline workflows and ensure consistent image updates across environments.

Content Trust and Image Signing:

Enable content trust mechanisms such as Docker Content Trust or Notary to ensure image authenticity and integrity. By digitally signing images and verifying signatures during pull operations, organizations can mitigate the risk of tampering and unauthorized modifications.

Data Backup and Disaster Recovery:

Implement robust backup and disaster recovery strategies to safeguard critical container images against data loss or corruption. Regularly backup registry data to redundant storage locations and establish procedures for swift restoration in the event of failures or disasters. - Docker and Kubernetes Online Training

Performance Optimization:

Optimize registry performance by leveraging caching mechanisms, content delivery networks (CDNs), and geo-replication to reduce latency and improve image retrieval speeds. Distribute registry instances across multiple geographical regions to enhance availability and resilience.

Conclusion:

By following best practices such as selecting the right registry, optimizing image size, enforcing security measures, and integrating with CI/CD pipelines, organizations can streamline image management and enhance their containerized deployments without diving into complex coding intricacies.

Visualpath is the Leading and Best Institute for learning Docker And Kubernetes Online in Ameerpet, Hyderabad. We provide Docker Online Training Course, you will get the best course at an affordable cost.

Attend Free Demo

Call on - +91-9989971070.

Visit : https://www.visualpath.in/DevOps-docker-kubernetes-training.html

Blog : https://dockerandkubernetesonlinetraining.blogspot.com/

[hydrus]

Version 556

windows

zip

exe

macOS

app

linux

tar.zst

I had an ok week. I fixed some bugs and added a system to force-set filetypes.

You will be asked on update if you want to regenerate some animation thumbnails. The popup explains the decision, I recommend 'yes'.

full changelog

forced filetype

The difference between a zip and an Ugoira and a cbz is not perfectly clear cut. I am happy with the current filetype scanner--and there are a couple more improvements this week--but I'm sure there will always be some fuzziness in the difficult cases. This also applies to some clever other situations, like files that secretly store a zip concatenated after a jpeg. You might want that file to be considered something other than hydrus thinks it technically is.

So, on any file selection, you can now hit right-click->manage->force filetype. You can set any file to be seen as any other file. The changes take affect immediately, are reflected in presentation and system:filetype searches, and the files themselves will be renamed on disk (to aid 'open externally'). The original filetype is remembered, and everything is easily undoable through the same dialog.

Also added is 'system:has forced filetype', under the 'system:file properties' entry, if you'd like to find what you have set one way or the other.

This is experimental, and I don't recommend it for the most casual users, but if you are comfortable, have a play with it. I still need to write better error handling for complete nonsense cases (e.g. calling a webm a krita is probably going to raise an error somewhere), but let me know how you get on.

other highlights

I fixed some dodgy numbers in Mr. Bones (deleted file count) and the file history chart (inbox/archive count). If you have had some whack results here, let me know if things are any better! If they aren't, does changing the search to something more specific than 'all my files'/'system:everything' improve things?

Some new boot errors, mostly related to missing database components, are now handled with nicer dialog prompts, and even interactive console prompts serverside.

I _may_ have fixed/relieved the 'program is hung when restored from minimise to system tray' issue, but I am not confident. If you still have this, let me know how things are now. If you still get a hang, more info on what your client was doing during the minimise would help--I just cannot reproduce this problem reliably.

Thanks to a user who figured out all the build script stuff, the Docker package is now Alpine 3.19. The Docker package should have newer libraries and broader file support.

birthday and year summary

The first non-experimental beta of hydrus was released on December 14th, 2011. We are now going on twelve years.

Like many, I had an imperfect 2023. I've no complaints, but IRL problems from 2022 cut into my free time and energy, and I regret that it impacted my hydrus work time. I had hoped to move some larger projects forward this year, but I was mostly treading water with little features and optimisations. That said, looking at the changelog for the year reveals good progress nonetheless, including: multiple duplicate search and filter speed and accuracy improvements, and the 'one file in this search, the other in this search' system; significant Client API expansions, in good part thanks to a user, including the duplicates system, more page inspections, multiple local file domains, and http headers; new sidecar datatypes and string processing tools; improvements to 'related tags' search; much better transparency support, including 'system:has transparency'; more program stability, particularly with mpv; much much faster tag autocomplete results, and faster tag and file search cancelling; the inc/dec rating service; better file timestamp awareness and full editing capability; the SauceNAO-style image search under 'system:similar files'; blurhashes; more and better system predicate parsing, and natural system predicate parsing in the normal file search input; a background database table delete system that relieves huge jobs like 'delete the PTR'; more accurate Mr. Bones and File History, and both windows now taking any search; and multiple new file formats, like HEIF and gzip and Krita, and thumbnails and full rendering for several like PSD and PDF, again in good part thanks to a user, and then most recently the Ugoira and CBZ work.

I'm truly looking forward to the new year, and I plan to keep working and putting out releases every week. I deeply appreciate the feedback and help over the years. Thank you!

next week

I have only one more week in the year before my Christmas holiday, so I'll just do some simple cleanup and little fixes.

[onlinecoursesusa]

DevOps Certification Training at H2KInfosys

In today's fast-paced tech industry, staying competitive and relevant is crucial. As organizations increasingly adopt DevOps practices to enhance collaboration, boost efficiency, and accelerate software delivery, professionals with DevOps skills are in high demand. To meet this demand and help individuals advance their careers, H2K Infosys offers a comprehensive DevOps certification training that equips learners with the knowledge and hands-on experience they need to excel in this dynamic field.

Why DevOps Certification Matters

DevOps is not just a buzzword; it's a fundamental shift in the way software development and IT operations work together. By obtaining a DevOps certification at H2K Infosys, you'll prove to employers that you have the skills and knowledge to streamline processes, automate tasks, and foster a culture of collaboration within an organization. Whether you're a software developer, system administrator, or IT manager, a DevOps certification is an investment in your future.

H2K Infosys: Your Trusted DevOps Training Partner

H2K Infosys has a sterling reputation as a provider of high-quality IT training and certification programs. The DevOps certification course at H2K Infosys is designed to meet the needs of beginners and experienced professionals alike. Here's why H2K Infosys is the ideal choice for your DevOps journey:

Comprehensive Curriculum: Our DevOps certification program covers the entire DevOps lifecycle, including version control, continuous integration, continuous deployment, automation, and collaboration. You'll gain proficiency in tools like Git, Jenkins, Docker, Kubernetes, and more.

Hands-On Experience: Theory is essential, but practical experience is equally crucial. H2K Infosys provides extensive hands-on labs and projects to ensure that you can apply what you've learned in real-world scenarios.

Expert Instructors: Our instructors are seasoned DevOps professionals with real-world experience. They are dedicated to guiding you through the intricacies of DevOps practices and technologies.

Flexibility: We understand that everyone has different schedules. Our DevOps certification program offers flexible options, including weekday and weekend classes, ensuring that you can acquire DevOps skills without disrupting your work or personal life.

Job Assistance: H2K Infosys goes the extra mile to help you secure a job in the DevOps field. We offer resume building, interview preparation, and job placement assistance to our certified students.

Tags: H2KInfosys, DevOps certification, H2K Infosys DevOps, DevOps tools, Devops certification H2K Infosys, Automation in DevOps, Best DevOps in GA USA, worldwide top rating AWS DevOps Certification | H2K Infosys, devops certification, aws devops certification, azure devops certification, devops training,devops training near me, devops tutorial,devops certification training course

Contact:  +1-770-777-1269

Mail: training@h2kinfosys.com

Location: Atlanta, GA - USA, 5450 McGinnis Village Place, # 103 Alpharetta, GA 30005, USA.

Facebook: https://www.facebook.com/H2KInfosysLLC

Instagram: https://www.instagram.com/h2kinfosysllc/

Youtube: https://www.youtube.com/watch?v=fgOgOCT_6L4

Visit: https://www.h2kinfosys.com/courses/devops-online-training-course/

DevOps Course: bit.ly/45vT1nB

[t-3-planet]

Step-by-Step Guide: TYPO3 Auto Deployment with Bitbucket CI/CD

Say goodbye to the days of manual deployment and complex command-based workflows! With TYPO3 CI/CD, you can automate the deployment of your TYPO3 project. By simply using commands like git push or git tag, you can trigger the automatic deployment of your latest code to the staging or production server.

TYPO3 CI/CD also offers a nifty feature: code testing before deployment. This allows you to ensure that your TYPO3 code meets the highest quality standards and gives you greater control over its overall quality. It's time to simplify your TYPO3 development process and take it to the next level!

Following are the Steps to Auto Deployment TYPO3:

Auto-deploying TYPO3 using Bitbucket CI/CD is as easy as 1-2-3:

Make code changes and commit them using git push.

Start the TYPO3 Bitbucket pipeline runners.

Sit back and relax! Your new code will be automatically deployed to the server.

Just run git push, and your deployment is taken care of seamlessly. It's that simple and cool! Enjoy the convenience of automating TYPO3 deployment with Bitbucket CI/CD.

Trying TYPO3 CI/CD auto-deploy, especially if you're still using traditional manual deployment methods. To automated deployment aligns perfectly with the goals and vision for 2023. If you encounter any obstacles along the way, don't hesitate to reach out.

Are you interested in automating TYPO3 deployment effectively? This article explores deployment standards of TYPO3, employing tools such as Bitbucket CI/CD, deployer, Code review, frontend build, docker/ddev, and setting up development, staging, and production environments.

Discover the recommended practices for TYPO3 v12 and DevOps in this informative article - Step-by-Step Guide: TYPO3 Auto Deployment with Bitbucket CI/CD

[qcs01]

How to migrate your app to Kubernetes containers in GCP?

Migrating your application to Kubernetes containers in Google Cloud Platform (GCP) involves several steps. Here is a comprehensive guide to help you through the process:

Step 1: Prepare Your Application

Containerize Your Application:

Ensure your application is suitable for containerization. Break down monolithic applications into microservices if necessary.

Create a Dockerfile for each part of your application. This file will define how your application is built and run inside a container.

# Example Dockerfile

FROM python:3.9-slim

WORKDIR /app

COPY . /app

RUN pip install -r requirements.txt

CMD ["python", "app.py"]

     2. Build and Test Containers:

Build your Docker images locally and test them to ensure they run as expected.

docker build -t my-app .

docker run -p 5000:5000 my-app

Step 2: Set Up Google Cloud Platform

Create a GCP Project:

If you don’t have a GCP project, create one via the GCP Console.

Install and Configure gcloud CLI:

Install the Google Cloud SDK and initialize it.

curl https://sdk.cloud.google.com | bash

exec -l $SHELL

gcloud init

    3. Enable Required APIs:

Enable Kubernetes Engine API and other necessary services.

gcloud services enable container.googleapis.com

Step 3: Create a Kubernetes Cluster

Create a Kubernetes Cluster:

Use the gcloud CLI to create a Kubernetes cluster.

gcloud container clusters create my-cluster --zone us-central1-a

      2. Get Cluster Credentials:

Retrieve the credentials to interact with your cluster.

gcloud container clusters get-credentials my-cluster --zone us-central1-a

Step 4: Deploy to Kubernetes

Push Docker Images to Google Container Registry (GCR):

Tag and push your Docker images to GCR.

docker tag my-app gcr.io/your-project-id/my-app

docker push gcr.io/your-project-id/my-app

     2. Create Kubernetes Deployment Manifests:

Create YAML files for your Kubernetes deployments and services.

# deployment.yaml

apiVersion: apps/v1

kind: Deployment

metadata:

  name: my-app

spec:

  replicas: 3

  selector:

    matchLabels:

      app: my-app

  template:

    metadata:

      labels:

        app: my-app

    spec:

      containers:

      - name: my-app

        image: gcr.io/your-project-id/my-app

        ports:

        - containerPort: 5000

3. Deploy to Kubernetes:

Apply the deployment and service configurations to your cluster.

kubectl apply -f deployment.yaml

kubectl apply -f service.yaml

Step 5: Manage and Monitor

Monitor Your Deployment:

Use Kubernetes Dashboard or other monitoring tools like Prometheus and Grafana to monitor your application.

Scale and Update:

Scale your application as needed and update your deployments using Kubernetes rolling updates.

kubectl scale deployment my-app --replicas=5

kubectl set image deployment/my-app my-app=gcr.io/your-project-id/my-app:v2

Additional Tips

Use Helm: Consider using Helm for managing complex deployments.

CI/CD Integration: Integrate with CI/CD tools like Jenkins, GitHub Actions, or Google Cloud Build for automated deployments.

Security: Ensure your images are secure and scanned for vulnerabilities. Use Google Cloud’s security features to manage access and permissions.

By following these steps, you can successfully migrate your application to Kubernetes containers in Google Cloud Platform, ensuring scalability, resilience, and efficient management of your workloads.

For more details click www.hawkstack.com 

[this-week-in-rust]

This Week in Rust 516

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Official

Announcing Rust 1.73.0

Polonius update

Project/Tooling Updates

rust-analyzer changelog #202

Announcing: pid1 Crate for Easier Rust Docker Images - FP Complete

bit_seq in Rust: A Procedural Macro for Bit Sequence Generation

tcpproxy 0.4 released

Rune 0.13

Rust on Espressif chips - September 29 2023

esp-rs quarterly planning: Q4 2023

Implementing the #[diagnostic] namespace to improve rustc error messages in complex crates

Observations/Thoughts

Safety vs Performance. A case study of C, C++ and Rust sort implementations

Raw SQL in Rust with SQLx

Thread-per-core

Edge IoT with Rust on ESP: HTTP Client

The Ultimate Data Engineering Chadstack. Running Rust inside Apache Airflow

Why Rust doesn't need a standard div_rem: An LLVM tale - CodSpeed

Making Rust supply chain attacks harder with Cackle

[video] Rust 1.73.0: Everything Revealed in 16 Minutes

Rust Walkthroughs

Let's Build A Cargo Compatible Build Tool - Part 5

How we reduced the memory usage of our Rust extension by 4x

Calling Rust from Python

Acceptance Testing embedded-hal Drivers

5 ways to instantiate Rust structs in tests

Research

Looking for Bad Apples in Rust Dependency Trees Using GraphQL and Trustfall

Miscellaneous

Rust, Open Source, Consulting - Interview with Matthias Endler

Edge IoT with Rust on ESP: Connecting WiFi

Bare-metal Rust in Android

[audio] Learn Rust in a Month of Lunches with Dave MacLeod

[video] Rust 1.73.0: Everything Revealed in 16 Minutes

[video] Rust 1.73 Release Train

[video] Why is the JavaScript ecosystem switching to Rust?

Crate of the Week

This week's crate is yarer, a library and command-line tool to evaluate mathematical expressions.

Thanks to Gianluigi Davassi for the self-suggestion!

Please submit your suggestions and votes for next week!

Call for Participation

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

Ockam - Make ockam node delete (no args) interactive by asking the user to choose from a list of nodes to delete (tuify)

Ockam - Improve ockam enroll ----help text by adding doc comment for identity flag (clap command)

Ockam - Enroll "email: '+' character not allowed"

If you are a Rust project owner and are looking for contributors, please submit tasks here.

Updates from the Rust Project

384 pull requests were merged in the last week

formally demote tier 2 MIPS targets to tier 3

add tvOS to target_os for register_dtor

linker: remove -Zgcc-ld option

linker: remove unstable legacy CLI linker flavors

non_lifetime_binders: fix ICE in lint opaque-hidden-inferred-bound

add async_fn_in_trait lint

add a note to duplicate diagnostics

always preserve DebugInfo in DeadStoreElimination

bring back generic parameters for indices in rustc_abi and make it compile on stable

coverage: allow each coverage statement to have multiple code regions

detect missing => after match guard during parsing

diagnostics: be more careful when suggesting struct fields

don't suggest nonsense suggestions for unconstrained type vars in note_source_of_type_mismatch_constraint

dont call mir.post_mono_checks in codegen

emit feature gate warning for auto traits pre-expansion

ensure that ~const trait bounds on associated functions are in const traits or impls

extend impl's def_span to include its where clauses

fix detecting references to packed unsized fields

fix fast-path for try_eval_scalar_int

fix to register analysis passes with -Zllvm-plugins at link-time

for a single impl candidate, try to unify it with error trait ref

generalize small dominators optimization

improve the suggestion of generic_bound_failure

make FnDef 1-ZST in LLVM debuginfo

more accurately point to where default return type should go

move subtyper below reveal_all and change reveal_all

only trigger refining_impl_trait lint on reachable traits

point to full async fn for future

print normalized ty

properly export function defined in test which uses global_asm!()

remove Key impls for types that involve an AllocId

remove is global hack

remove the TypedArena::alloc_from_iter specialization

show more information when multiple impls apply

suggest pin!() instead of Pin::new() when appropriate

make subtyping explicit in MIR

do not run optimizations on trivial MIR

in smir find_crates returns Vec<Crate> instead of Option<Crate>

add Span to various smir types

miri-script: print which sysroot target we are building

miri: auto-detect no_std where possible

miri: continuation of #3054: enable spurious reads in TB

miri: do not use host floats in simd_{ceil,floor,round,trunc}

miri: ensure RET assignments do not get propagated on unwinding

miri: implement llvm.x86.aesni.* intrinsics

miri: refactor dlsym: dispatch symbols via the normal shim mechanism

miri: support getentropy on macOS as a foreign item

miri: tree Borrows: do not create new tags as 'Active'

add missing inline attributes to Duration trait impls

stabilize Option::as_(mut_)slice

reuse existing Somes in Option::(x)or

fix generic bound of str::SplitInclusive's DoubleEndedIterator impl

cargo: refactor(toml): Make manifest file layout more consitent

cargo: add new package cache lock modes

cargo: add unsupported short suggestion for --out-dir flag

cargo: crates-io: add doc comment for NewCrate struct

cargo: feat: add Edition2024

cargo: prep for automating MSRV management

cargo: set and verify all MSRVs in CI

rustdoc-search: fix bug with multi-item impl trait

rustdoc: rename issue-\d+.rs tests to have meaningful names (part 2)

rustdoc: Show enum discrimant if it is a C-like variant

rustfmt: adjust span derivation for const generics

clippy: impl_trait_in_params now supports impls and traits

clippy: into_iter_without_iter: walk up deref impl chain to find iter methods

clippy: std_instead_of_core: avoid lint inside of proc-macro

clippy: avoid invoking ignored_unit_patterns in macro definition

clippy: fix items_after_test_module for non root modules, add applicable suggestion

clippy: fix ICE in redundant_locals

clippy: fix: avoid changing drop order

clippy: improve redundant_locals help message

rust-analyzer: add config option to use rust-analyzer specific target dir

rust-analyzer: add configuration for the default action of the status bar click action in VSCode

rust-analyzer: do flyimport completions by prefix search for short paths

rust-analyzer: add assist for applying De Morgan's law to Iterator::all and Iterator::any

rust-analyzer: add backtick to surrounding and auto-closing pairs

rust-analyzer: implement tuple return type to tuple struct assist

rust-analyzer: ensure rustfmt runs when configured with ./

rust-analyzer: fix path syntax produced by the into_to_qualified_from assist

rust-analyzer: recognize custom main function as binary entrypoint for runnables

Rust Compiler Performance Triage

A quiet week, with few regressions and improvements.

Triage done by @simulacrum. Revision range: 9998f4add..84d44dd

1 Regressions, 2 Improvements, 4 Mixed; 1 of them in rollups

68 artifact comparisons made in total

Full report here

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

[disposition: merge] RFC: Remove implicit features in a new edition

Tracking Issues & PRs

[disposition: merge] Bump COINDUCTIVE_OVERLAP_IN_COHERENCE to deny + warn in deps

[disposition: merge] document ABI compatibility

[disposition: merge] Broaden the consequences of recursive TLS initialization

[disposition: merge] Implement BufRead for VecDeque<u8>

[disposition: merge] Tracking Issue for feature(file_set_times): FileTimes and File::set_times

[disposition: merge] impl Not, Bit{And,Or}{,Assign} for IP addresses

[disposition: close] Make RefMut Sync

[disposition: merge] Implement FusedIterator for DecodeUtf16 when the inner iterator does

[disposition: merge] Stabilize {IpAddr, Ipv6Addr}::to_canonical

[disposition: merge] rustdoc: hide #[repr(transparent)] if it isn't part of the public ABI

New and Updated RFCs

[new] Add closure-move-bindings RFC

[new] RFC: Include Future and IntoFuture in the 2024 prelude

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No RFCs issued a call for testing this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Upcoming Events

Rusty Events between 2023-10-11 - 2023-11-08 🦀

Virtual

2023-10-11| Virtual (Boulder, CO, US) | Boulder Elixir and Rust

Monthly Meetup

2023-10-12 - 2023-10-13 | Virtual (Brussels, BE) | EuroRust

EuroRust 2023

2023-10-12 | Virtual (Nuremberg, DE) | Rust Nuremberg

Rust Nürnberg online

2023-10-18 | Virtual (Cardiff, UK)| Rust and C++ Cardiff

Operating System Primitives (Atomics & Locks Chapter 8)

2023-10-18 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Rust Study/Hack/Hang-out

2023-10-19 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2023-10-19 | Virtual (Stuttgart, DE) | Rust Community Stuttgart

Rust-Meetup

2023-10-24 | Virtual (Berlin, DE) | OpenTechSchool Berlin

Rust Hack and Learn | Mirror

2023-10-24 | Virtual (Washington, DC, US) | Rust DC

Month-end Rusting—Fun with 🍌 and 🔎!

2023-10-31 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2023-11-01 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

Asia

2023-10-11 | Kuala Lumpur, MY | GoLang Malaysia

Rust Meetup Malaysia October 2023 | Event updates Telegram | Event group chat

2023-10-18 | Tokyo, JP | Tokyo Rust Meetup

Rust and the Age of High-Integrity Languages

Europe

2023-10-11 | Brussels, BE | BeCode Brussels Meetup

Rust on Web - EuroRust Conference

2023-10-12 - 2023-10-13 | Brussels, BE | EuroRust

EuroRust 2023

2023-10-12 | Brussels, BE | Rust Aarhus

Rust Aarhus - EuroRust Conference

2023-10-12 | Reading, UK | Reading Rust Workshop

Reading Rust Meetup at Browns

2023-10-17 | Helsinki, FI | Finland Rust-lang Group

Helsinki Rustaceans Meetup

2023-10-17 | Leipzig, DE | Rust - Modern Systems Programming in Leipzig

SIMD in Rust

2023-10-19 | Amsterdam, NL | Rust Developers Amsterdam Group

Rust Amsterdam Meetup @ Terraform

2023-10-19 | Wrocław, PL | Rust Wrocław

Rust Meetup #35

2023-09-19 | Virtual (Washington, DC, US) | Rust DC

Month-end Rusting—Fun with 🍌 and 🔎!

2023-10-25 | Dublin, IE | Rust Dublin

Biome, web development tooling with Rust

2023-10-26 | Augsburg, DE | Rust - Modern Systems Programming in Leipzig

Augsburg Rust Meetup #3

2023-10-26 | Delft, NL | Rust Nederland

Rust at TU Delft

2023-11-07 | Brussels, BE | Rust Aarhus

Rust Aarhus - Rust and Talk beginners edition

North America

2023-10-11 | Boulder, CO, US | Boulder Rust Meetup

First Meetup - Demo Day and Office Hours

2023-10-12 | Lehi, UT, US | Utah Rust

The Actor Model: Fearless Concurrency, Made Easy w/Chris Mena

2023-10-13 | Cambridge, MA, US | Boston Rust Meetup

Kendall Rust Lunch

2023-10-17 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

2023-10-18 | Brookline, MA, US | Boston Rust Meetup

Boston University Rust Lunch

2023-10-19 | Mountain View, CA, US | Mountain View Rust Meetup

Rust Meetup at Hacker Dojo

2023-10-19 | Nashville, TN, US | Music City Rust Developers

Rust Goes Where It Pleases Pt2 - Rust on the front end!

2023-10-19 | Seattle, WA, US | Seattle Rust User Group

Seattle Rust User Group - October Meetup

2023-10-25 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

2023-10-25 | Chicago, IL, US | Deep Dish Rust

Rust Happy Hour

Oceania

2023-10-17 | Christchurch, NZ | Christchurch Rust Meetup Group

Christchurch Rust meetup meeting

2023-10-26 | Brisbane, QLD, AU | Rust Brisbane

October Meetup

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

The Rust mission -- let you write software that's fast and correct, productively -- has never been more alive. So next Rustconf, I plan to celebrate:

All the buffer overflows I didn't create, thanks to Rust

All the unit tests I didn't have to write, thanks to its type system

All the null checks I didn't have to write thanks to Option and Result

All the JS I didn't have to write thanks to WebAssembly

All the impossible states I didn't have to assert "This can never actually happen"

All the JSON field keys I didn't have to manually type in thanks to Serde

All the missing SQL column bugs I caught at compiletime thanks to Diesel

All the race conditions I never had to worry about thanks to the borrow checker

All the connections I can accept concurrently thanks to Tokio

All the formatting comments I didn't have to leave on PRs thanks to Rustfmt

All the performance footguns I didn't create thanks to Clippy

– Adam Chalmers in their RustConf 2023 recap

Thanks to robin for the suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust

[sandeep2363]

Docker command as Cheat Sheet

Docker daily usage commands list for Devops team Check the images and repository in Docker # List all available local imagesdocker images# Search for docker imagesdocker search <image># Build an image with a dockerfiledocker build -t <image>:<tag> <run_directory># Login to a remote repositorydocker login <repository>#push an image to your remote repositorydocker push <image>:<tag># remove a…

[tibbo]

Docker Makes Building Custom Linux Images Quick and Easy

Creating a Linux-based product can seem daunting at first. Even experienced developers can get bogged down configuring and creating projects from scratch. From downloading tools and software repositories to actually developing the application, these projects require a significant investment in time.

As we've mentioned before, Tibbo supplies a free Docker container to facilitate and simplify the development of products based on our Size 3 Linux Tibbo Project PCB (LTPP3), Gen. 2 or its Plus1 CPU. Docker containers hold an application and its dependencies, and can be run from any Linux, Windows, or macOS computer. Our container allows you to download the development environment in a working state without requiring any configuration.

Tibbo's container for the LTPP3(G2) provides a stable, consistent, and convenient starting point for your projects. It contains our Ubuntu-based distribution, Out-of-Box-Experience (OOBE) scripts, and drivers, as well as our build tools so that you can completely customize the image to serve your needs. And because it is regularly updated and tagged, it's always easy to work off either the latest version or any earlier release you've previously used.

The whole process is remarkably easy. First, download and run the container. Then, modify it in any way you see fit; for example, you can install and remove packages or even edit the device tree. When you're done, run our automated scripts to build a fully working image ready to be uploaded to your LTPP3(G2).

Since we first mentioned our Docker container, many of you have asked us for more information regarding its use. To help you with this process, we've created a video demonstrating how to pull our Docker container, modify the image, build, extract, and even upload it to the LTPP3(G2).

As you'll see for yourself, the entire process is straightforward, as well as significantly faster and easier than creating a virtual machine, installing Linux, downloading repositories, and customizing the image. It is also reliably repeatable, so you can always start projects from your preferred development point.

[lichray]

Develop LLVM on Windows Dev Kit 2023

If you read the article Building LLVM in 90 seconds using Amazon Lambda in 2021, you might wonder whether you can do the same without the author's AMD Ryzen desktop. This blog will show you how I reproduce the results on a $600 ARM64 machine -- Windows Dev Kit 2023.

The software that offloads the compilation tasks to AWS Lambda is called "llama." I forked it to support ARM64. Everything to be discussed here will be using ARM64 -- Windows 11 ARM64, WSL that runs openSUSE Tumbleweed AArch64, Docker image that contains AArch64 binaries, LLVM that generates AArch64 codes, etc.

If you happen to use openSUSE Tumbleweed as well, you can check out the images I uploaded to Docker Hub: lichray/llama-gcc12 for GCC + gold linker and lichray/llama-clang15 for Clang + lld linker; the latter offers only libstdc++. As a jump start, let's give the GCC option a try.

First, clone https://github.com/zhihaoy/llama and switch to the aarch64 branch. Set the GOBIN environment variable to some PATH, go install ./... under the project root. Follow the Getting started guide carefully and bootstrap AWS resources for llama.

Next, make my Docker tag available on your local system with docker pull lichray/llama-gcc12:latest. Then you can create an AWS Lambda in your own account with llama update-function -create -tag lichray/llama-gcc12:latest gcc. The function name "gcc" is a llama default; we will change that when trying out Clang.

Everything is ready. I configure my llvm-project with the following:

env LLAMACC_LOCAL=1 \ cmake -G Ninja \ -DCMAKE_BUILD_TYPE=MinSizeRel \ -DLLVM_ENABLE_PROJECTS="clang" \ -DLLVM_USE_LINKER=gold \ -DCMAKE_C_COMPILER=llamacc \ -DCMAKE_CXX_COMPILER=llamac++ \ -DBUILD_SHARED_LIBS=YES \ -DLLVM_TARGETS_TO_BUILD=AArch64 \ -DCLANG_ENABLE_STATIC_ANALYZER=NO \ -DCLANG_ENABLE_ARCMT=NO \ -B build llvm

To simplify this small example, I didn't set up libc++. The full clang build finishes within 6 minutes with ninja -j 40 -C build/ clang

As you can see, there're warnings. For obvious reasons, the LLVM project guarantees warning-free only when building with Clang, so I'll set up a frustration-free LLVM dev environment next with Clang.

Create an AWS Lambda with my Clang image:

docker pull lichray/llama-clang15:latest llama update-function -create -tag lichray/llama-clang15:latest clang

Export an environment variable to change the Lambda function used by llama (you may want to save that in your shell profile):

# csh setenv LLAMACC_FUNCTION clang

Change cc and c++ commands to match what llamacc and llamac++ use from the image:

update-alternatives --install /usr/bin/cc cc /usr/bin/clang 30 update-alternatives --install /usr/bin/c++ c++ /usr/bin/clang++ 30

Now I can configure:

env LLAMACC_LOCAL=1 \ cmake -G Ninja \ -DCMAKE_BUILD_TYPE=MinSizeRel \ -DLLVM_ENABLE_PROJECTS="clang" \ -DLLVM_USE_LINKER=lld \ -DCMAKE_C_COMPILER=llamacc \ -DCMAKE_CXX_COMPILER=llamac++ \ -DBUILD_SHARED_LIBS=YES \ -DLLVM_TARGETS_TO_BUILD=AArch64 \ -DCLANG_ENABLE_STATIC_ANALYZER=NO \ -DCLANG_ENABLE_ARCMT=NO \ -B build llvm

200 seconds! It's totally not bad, as the original "90 seconds" article used the -O0 flag, which renders the resulting clang executable impractical to use in building clang checks or libc++ later.

And the build costs only 30¢. That is why I moved my dev environment to ARM64. ARM chips are inexpensive, even in the cloud (-20% cost overall). To take full advantage of that, all I did is to make my dev machine consume native artifacts from the cloud.

Caveats

WSL datetime can drift when the host sleeps, disrupting your cached AWS token. Read the comments in this issue to find a solution: #8204

AWS accounts that are new to Lambda have very low concurrency quota. Read this guide before requesting a quota increase: Lambda function scaling