Encontrar

Artículo
· 9 hr atrás Lectura de 4 min

IRIS no Docker para iniciantes

O artigo foi motivado pelo 2025 September Article Bounty
********************************************************


O princípio do Docker é simplesmente convincente para mim.

  • Obtenha uma área restrita onde você pode brincar e tentar o que quiser/precisar fazer.
  • Depois de terminar, você pode descartá-la sem deixar rastros em seu ambiente de trabalho.

Essa foi a base técnica que me permitiu executar cerca de 700 revisões no OEX 
quase sem efeitos colaterais  (exceto aqueles causados por mim mesmo).

Para iniciantes, vou começar com o IRIS puro, sem *health, *ML, *whatever.

Primeiro, você precisa instalar o Docker. Ele está disponível em quase todas as plataformas.
Minha preferência pessoal é o Windows Docker Desktop por seu console de
administração confortável. Não me aprofundo na gestão detalhada do Docker.
Há material de leitura suficiente para pesquisar no Docker Docs

Segundo, você decide sobre uma encarnação do IRIS de sua escolha
a mais simples: intersystemsdc/iris-community  pronta para usar

  • roda no Ubuntu
  • tem uma licença comunitária válida
  • tem o Apache httpd instalado
  • tem o cliente IPM/ZPM instalado

Aviso nº 1:  Como iniciante, não estude os pacotes oferecidos no OEX
Eles são ótimos (na maioria), mas sempre direcionados a alguma funcionalidade
para alguma aplicação especial que requer configurações especiais e uma instalação complicada.

Aviso nº 2:  O Docker tem um rico conjunto de comandos com tudo o que você precisa
E esses comandos oferecem uma enxurrada de parâmetros (às vezes confusos).
Portanto, sugiro torná-los reproduzíveis usando scripts dedicados.
Dockerfile  é a maneira de lidar com construções complexas com muitos extras a serem
carregados antecipadamente. Normalmente, eu os via relacionados ao Python e a vários casos de demonstração de IA.
Não há necessidade desse exemplo.
docker-compose.yml é o verdadeiro responsável por ativar seu contêiner.
Ele precisa de:

  • uma definição do que deseja “compor”  >> service: 
    • um nome para elet  >>  iris:
    • qual imagem executar  >> image: intersystemsdc/iris-community
  • Em seguida, você precisa definir como a porta 1972 do SuperServer e a   porta padrão 52773 do WebServer ficarão visíveis fora do contêine
    •     ports:      - 41773:1972   - 42773:52773
  • Por fim,  não é um requisito urgente, mas muitas vezes é muito útil mapear seu diretório local para algum diretório interno no contêiner. Eu usei /external Especialmente no início, esse caminho bidirecional facilita muito a vida
    • volumes:  - ./:/external

Agora, este é o texto final do docker-compose.yml

services:
  iris:
    image: intersystemsdc/iris-community
    ports: 
      - 41773:1972
      - 42773:52773
    volumes:
      - ./:/external

Agora você está pronto para executar sua primeira instância do IRIS no Docker

  • docker-compose up  permite que você assista à inicialização completa
  • docker-compose up -d  inicia uma  inicialização em segundo plano e mantém
  • docker ps -a    mostra as portas e as imagens em execução do seu contêiner

OK, seu novo IRIS está no Docker agora.
Mas como você pode usá-lo?

  • Você tem o WebServer e, portanto, o Portal de Gerenciament
  • Você tem o SuperServerPort para acesso ODBC, IRIS NATIVE, ... (e até mesmo Studio).
  • E você também pode acessar o IRIS a partir da linha de comando dentro do contêiner.er​​​​​​
    • docker-compose exec iris iris session iris
  • Dividindo essa única linha, você acessa primeiro o contêiner e depois o IRIS
    • docker-compose exec iris bash
    • Then iris view
      • Instance 'IRIS'   (default)
                directory:    /usr/irissys
                versionid:    2025.1.0.223.0com
                datadir:      /usr/irissys
                conf file:    iris.cpf  (WebServer port = 52773)
                status:       running, since Thu Sep  4 14:35:19 2025
                SuperServers: 1972
                state:        ok
                product:      InterSystems IRIS
      • E iris session iris
      • Node: 3266c5c8b21f, Instance: IRIS 
        USER>
    • Aqui, no nível do bash, você tem todas as opções para operar o IRIS em suas mãos Seu usuário Ubuntu é   irisowner
    • para os raros casos em que você pode precisar de acesso root  docker-compose exec -u root iris bash
    • Pare seu contêiner com   docker-compose down

Algumas considerações sobre alterações durante a sessão do contêiner.

  • Tudo o que você criar, alterar ou modificar existirá enquanto o contêiner existir.
    • Depois que o contêiner for excluído, todas as alterações, etc., desaparecerão. 
  • Isso pode ser incômodo em configurações grandes.
  • O Dockerfile cuida de uma configuração que é feita uma vez em um ciclo de compilação, em vez de executar a configuração a cada inicialização do contêiner.
  • Essa é uma boa prática em pacotes OEX, embora eu
Comentarios (0)1
Inicie sesión o regístrese para continuar
Pregunta
· 9 hr atrás

LOAD DATA from file erroring after upgrade to 2025.1

We have a task that runs objectscript code to load data into a linked external table.  After upgrading from 2024.1 to 2025.1, the load is throwing an error, with error code -400, and no error message.  The data DOES get loaded into the external table in its entirety, so with no meaningful error message, its hard to determine what the issue is.  The result is the same with and without the USING clause, so don't let that confuse you.  We have logs of this statement succeeding before upgrade, and were able to get this statement to work in our production environment, which is still on version 2024.1.  I have recompiled all namespaces after upgrade, stopped and restarted the JDBC server, and have dropped and relinked the external table, all without success.

Code: LOAD DATA FROM FILE '/intersystems/filepath/loadtest.csv' INTO SCM_Table_sandbox.dontest USING {"maxerrors":0,"from": {"file": {"header":false,"columnseparator": ","}}}

SQL Diagnostic Log:

Start time 2025-09-05 18:07:06.822705
User xxxx
Status Complete
Process ID 650691
SQLCODE -400 - See detailed error messages below
Input record count 0
Error count 2 (max error count: 0)
Statement LOAD DATA FROM FILE '/intersystems/filepath/loadtest.csv' INTO SCM_TABLE_SANDBOX . DONTEST USING { "MAXERRORS" :MAXERRORS 0 , "FROM" :FROM { "FILE" :FILE { "HEADER" :HEADER FALSE , "COLUMNSEPARATOR" :COLUMNSEPARATOR "," } } }

Messages:

18:07:06.848 (server) - info: {"resultid":"21","bufferrowcount":500,"queuesize":2,"statistics":false,"from":{"file":{"file":"/intersystems/filepath/loadtest.csv","columns":null,"header":false,"types":null,"columnseparator":",","lineseparator":"\n"},"select":["name","id"],"intotypes":[12,4]},"into":{"table":"SCM_Table_sandbox.dontest","hints":"","columns":["name","id"],"types":[12,4],"values":["?","?"],"bindings":[0,1],"jdbc":{"threads":3}}}

18:07:07.123 (FileReader) - completed: Reader Complete: Total Input file read time: 42 ms,

18:07:07.124 (JdbcWriter) - completed: Writer Complete: Total write time: 45 ms,

18:07:08.219 (JdbcWriter) - completed: Writer Complete: Total write time: 1142 ms,

18:07:08.220 (JdbcWriter) - error: 1

18:07:08.220 (JdbcWriter) - abort: 1

Any help would be appreciated!

-Don Martin, Sanford Health

Comentarios (0)1
Inicie sesión o regístrese para continuar
Artículo
· 14 hr atrás Lectura de 4 min

IRIS in Docker para principiantes

El artículo fue motivado por 2025 September Article Bounty
***********************************************************


El principio de Docker me resulta simplemente convincente..

  • Consigue un sandbox donde puedas jugar y probar lo que quieras o necesites hacer.
  • Una vez hecho, lo sueltas sin dejar rastros en tu entorno de trabajo.

Esta fue la base técnica para que yo pudiera realizar alrededor de 700 revisiones en OEX 
con casi ningún efecto secundario (excepto los causados ​​por mí mismo).

Para principiantes, comenzaré con IRIS puro, sin *Health, *ML, *lo que sea. 

Primero, necesitas una instalación de Docker. Está disponible en casi cualquier plataforma.
Mi preferencia personal es Windows Docker Desktop por su cómoda consola de administración.
No profundizo en la gestión detallada de Docker.
Hay suficiente material de lectura para buscar en Docker Docs

En segundo lugar, decides la encarnación de IRIS que prefieras.
El más simple: intersystemsdc/iris-community  preparado para usar

  • Funciona en Ubuntu.
  • Tiene una licencia comunitaria válida.
  • Tiene instalado Apache httpd.
  • Tiene instalado el cliente IPM/ZPM.

Advertencia #1:  Como principiante, no estudies los paquetes que se ofrecen en OEX.
Son excelentes (en su mayoría), pero siempre están orientados a alguna funcionalidad
o aplicación especial que requiere configuraciones especiales y una instalación compleja.

Advertencia #2:  Docker cuenta con un amplio conjunto de comandos con todo lo necesario.
Y esos comandos ofrecen una gran cantidad de parámetros (a veces confusos).
Por lo tanto, sugiero que se puedan reproducir mediante scripts dedicados.
Dockerfile es la mejor manera de trabajar con construcciones complejas que requieren
una carga inicial de muchos extras. Normalmente los he visto relacionados con Python
y con varios casos de demostración de IA. Este ejemplo no es necesario.
docker-compose.yml es el lugar real para hacer estallar tu contenedor. Necesita:

  • una definición de lo que quieres "componer" >> service: 
    • un nombre para ello  >>  iris:
    • qué imagen ejecutar  >> image: intersystemsdc/iris-community
  • A continuación, debe definir cómo el puerto SuperServer 1972 y el puerto WebServer predeterminado 52773 serán visibles fuera del contenedor.
    •     ports:      - 41773:1972   - 42773:52773
  • Por último, no es un requisito urgente, pero a menudo es muy útil asignar su directorio local a algún directorio interno dentro del contenedor. Yo usé /external
    • ​Especialmente al principio, este camino bidireccional hace la vida realmente fácil.
      <strong>volumes:</strong>
       - ./:/external

Ahora bien, este es el texto final de docker-compose.yml

services:
  iris:
    image: intersystemsdc/iris-community
    ports: 
      - 41773:1972
      - 42773:52773
    volumes:
      - ./:/external

Y ahora está listo para ejecutar su primera instancia de IRIS en Docker

  • docker-compose up  Permite ver el inicio completo.
  • docker-compose up -d  Inicia un inicio en segundo plano y mantiene su línea de comandos libre
  • docker ps -a    Muestra puertos e imágenes en ejecución de su contenedor IRIS

Bien, tu nuevo IRIS ya está en Docker..
¿Pero cómo puedes utilizarlo?

  • Tienes el WebServer y por tanto el Portal de Gestión http://localhost:42773/csp/sys/UtilHome.csp
  • Tienes el SuperServerPort para acceso ODBC, IRIS NATIVE, ... (e incluso Studio)
  • Y también puedes acceder a IRIS desde la línea de comandos dentro del contenedor​​​​​​
    • docker-compose exec iris iris session iris
  • Al dividir esta única línea, se accede primero al contenedor y luego a IRIS.
    • docker-compose exec iris bash
    • Álora iris view
      • Instance 'IRIS'   (default)
                directory:    /usr/irissys
                versionid:    2025.1.0.223.0com
                datadir:      /usr/irissys
                conf file:    iris.cpf  (WebServer port = 52773)
                status:       running, since Thu Sep  4 14:35:19 2025
                SuperServers: 1972
                state:        ok
                product:      InterSystems IRIS
      • y iris session iris
      • Node: 3266c5c8b21f, Instance: IRIS 
        USER>
    • Aquí en el nivel bash, tienes todas las opciones para que IRIS funcione en tus manos.
      • Tu usuario de Ubuntu es irisowner.
    • Para los casos excepcionales en los que pueda necesitar acceso root
      • docker-compose exec -u root iris bash
    • Detenga su contenedor con  docker-compose down

Algunas consideraciones sobre los cambios durante la sesión del contenedor.

  • Todo lo que crees, cambies o modifiques existirá mientras exista el contenedor.
    • Una vez que se elimina el contenedor, todos los cambios, ... desaparecen.
  • Esto podría resultar molesto con configuraciones grandes.
  • Dockerfile se encarga de una configuración que se realiza una vez en un ciclo de compilación, de manera diferente para ejecutar la configuración en cada inicio del contenedor..
  • Esta es una buena práctica en paquetes OEX, aunque puede parecer exagerada en algunos casos. 
Comentarios (0)1
Inicie sesión o regístrese para continuar
Pregunta
· 17 hr atrás

Elevate Your Vaping Journey with the Vaporesso Xros 4 Nano Pod Kit

 

The vaping world continues to evolve with innovative devices that make every puff smoother, more flavorful, and more satisfying. Among the latest launches, the Vaporesso Xros 4 Nano Pod Kit has quickly gained attention for its impressive combination of portability, performance, and advanced features. Built to deliver a premium experience in a compact form factor, this device appeals to both new vapers looking for convenience and experienced users seeking customization.

In this detailed blog, we will take an in-depth look at the Xros 4 Nano Pod Kit, its specifications, design, performance, and all the little details that set it apart. Whether you’re after a flavorful mouth-to-lung (MTL) session or a smooth restricted direct-lung (RDL) vape, this pod kit is designed to give you the best of both worlds.

Compact Design with Big Capabilities

One of the standout features of the Xros 4 Nano is its compact, pocket-friendly design. Measuring approximately 56.5 × 55 × 20.9 mm, the device slips easily into your pocket or bag, making it perfect for vaping on the go. Despite its small size, it feels sturdy and durable, thanks to its aluminum-alloy unibody construction. The design not only adds to its durability but also gives it a premium texture that feels comfortable in the hand.

The balance between size and performance is what makes this device special. It looks stylish without being flashy, and its build quality ensures long-lasting use. For users who value both portability and durability, the Xros 4 Nano Pod Kit delivers on all counts.

Strong Battery Life and Rapid Charging

Battery life is one of the most important considerations for any pod kit. The Vaporesso Xros 4 Nano features a 1350 mAh internal battery, which is one of the largest capacities in the Xros series. This powerful battery ensures long-lasting vaping sessions without constant recharging, making it an excellent choice for heavy vapers.

When it does need charging, the USB Type-C 2A fast charging system gets the device back to 80% in just 20 minutes. That means less waiting and more vaping. A full charge easily lasts throughout the day, depending on usage, which is ideal for both casual and consistent users.

Vivid TFT Color Display

Unlike many compact pod kits, the Xros 4 Nano comes with a 1.3-inch circular TFT color display. This bright, sharp screen shows essential information like battery percentage, wattage, puff count, and mode selection. What makes it more interesting is the ability to choose from three customizable themes: Flower, Motion, and Universe.

This feature allows users to personalize their vaping experience visually, adding a fun and modern touch to the device. The screen makes it easy to stay on top of your settings at a glance, making the Xros 4 Nano Pod Kit not just functional but also engaging.

COREX 2.0 Technology for Superior Flavor

At the heart of the Vaporesso Xros 4 Nano Pod Kit is its advanced COREX 2.0 mesh coil technology. This technology enhances heating speed and improves temperature control, delivering a more consistent vaping experience.

With COREX 2.0, you can expect:

  • 30% better flavor thanks to improved mesh design and faster heating.
  • 30% longer pod lifespan because of upgraded cotton that resists burning and maintains performance.
  • 15% more vapor production, perfect for those who enjoy thicker clouds.

The result is a richer, fuller flavor profile and smoother hits, whether you’re using freebase e-liquids or nicotine salts.

Pod Versatility and Easy Refilling

One of the greatest strengths of the Xros 4 Nano is its full compatibility with all Vaporesso Xros pods. This includes pods ranging from 0.4 Ω to 1.2 Ω, giving you the flexibility to switch between different vaping styles.

The device usually comes with a 0.4 Ω COREX 2.0 pod pre-installed, along with a spare pod, often a 0.8 Ω option. This makes it ideal for experimenting with both MTL and RDL vaping.

Refilling is effortless thanks to the top-fill clamshell design. Just pop open the cap and fill without removing the pod from the device. The pods also include Vaporesso’s SSS leak-resistant technology, which prevents messes and keeps your e-liquid securely in place.

Customizable Wattage and Airflow

Vapers who like to fine-tune their experience will love the adjustable options on the Xros 4 Nano Pod Kit.

  • When using the 0.4 Ω pod, the device allows precise wattage adjustment in 0.5 W increments. This gives you incredible control over vapor production and flavor intensity.
  • With other pods, you can select from three preset modes: ECO (longer battery life), Normal (balanced performance), and Power (maximum output).

In addition, the slider-style airflow control lets you adjust between tight MTL draws, looser MTL, and smooth RDL vaping. This adaptability ensures that every user finds their perfect balance.

Dual Activation for Ease of Use

The Xros 4 Nano Pod Kit offers both button activation and auto-draw activation. Beginners may prefer auto-draw for its simplicity, while experienced users often enjoy the tactile control of pressing a button. Having both options makes the device versatile and user-friendly.

What’s Inside the Box?

When you purchase the Vaporesso Xros 4 Nano, the package typically includes everything you need to start vaping right away:

  • 1 × Xros 4 Nano Device
  • 1 × 0.4 Ω COREX 2.0 Pod (pre-installed)
  • 1 × Spare Pod (commonly 0.8 Ω)
  • 1 × USB Type-C Charging Cable
  • 1 × Lanyard
  • 1 × User Manual
  • 1 × Warranty Card

The packaging itself is sleek and premium-looking, often with clear labeling, product images, and authenticity verification. It makes the unboxing experience enjoyable while ensuring you get a genuine product.

A Spectrum of Colors

The Xros 4 Nano Pod Kit is available in a variety of stylish finishes to suit different personalities. Some of the most popular colors include:

  • Graphite Black
  • Titanium Silver
  • Aquamarine
  • Twilight Purple
  • Camouflage
  • Race Track
  • Word-pop Blue
  • Word-pop Yellow

From sleek metallics to bold graffiti-inspired prints, the range of choices allows users to pick a device that reflects their style.

Technical Specifications

For those who love the details, here are the key specifications of the Vaporesso Xros 4 Nano Pod Kit:

  • Battery Capacity: 1350 mAh (rechargeable)
  • Charging: USB Type-C, 2A fast charging
  • Pod Capacity: 3 mL (standard) / 2 mL (TPD version)
  • Compatible Pods: All Vaporesso Xros pods (0.4 Ω – 1.2 Ω)
  • Display: 1.3-inch TFT color screen
  • Output Power: 1–30 W
  • Filling System: Top-fill clamshell or side-fill
  • Airflow: Adjustable slider for MTL to RDL
  • Dimensions: ~56.5 × 55 × 20.9 mm
  • Build Material: Aluminum alloy

Why Choose the Xros 4 Nano Pod Kit?

There are countless pod kits available, but the Vaporesso Xros 4 Nano stands out for several reasons

  1. Powerful Battery – All-day usage with fast recharging.
  2. Advanced Technology – COREX 2.0 enhances flavor, vapor, and pod longevity.
  3. User-Friendly Controls – Simple enough for beginners, customizable for experts.
  4. Stylish Variety – Multiple finishes to match any personality.
  5. Pocket-Sized Durability – Compact but built to last.
  6. Complete Kit – Comes with everything needed to get started.
  7. Full Pod Compatibility – Works seamlessly with the entire Xros pod range.

This balance of convenience, performance, and versatility makes it one of the most well-rounded devices currently available.

Final Thoughts

The Vaporesso Xros 4 Nano Pod Kit is proof that small devices can deliver big performance. With its powerful battery, stunning display, leak-resistant pods, and innovative COREX 2.0 technology, it creates a vaping experience that is smooth, customizable, and enjoyable.

Whether you are switching from disposables, upgrading from an older device, or simply looking for a reliable daily pod kit, the Xros 4 Nano deserves your attention. It combines sleek design, advanced features, and user-friendly operation into a device that feels tailored to every kind of vaper.

If you value flavor, convenience, and innovation, this pod kit will elevate your vaping journey to the next level.

Comentarios (0)1
Inicie sesión o regístrese para continuar
Pregunta
· 17 hr atrás

Best Sainik School Coaching Institute

Young Star Defence Academy is India’s No.1 Sainik School Coaching Institute is a reputed coaching institute dedicated to preparing students for various defence service entrance exams in India. The academy specializes in coaching for Sainik School, Rashtriya Military School and RIMC. Read more.

 

Comentarios (0)1
Inicie sesión o regístrese para continuar