DataWeave Try Function Requires Explicit Import from dw::Runtime to Avoid Errors

·3 views

A DataWeave script using the try() function will fail with an 'Unable to resolve reference' error if dw::Runtime is not explicitly imported at the top of the script. The try() function, which returns a Result object for error handling, is not available by default and must be imported with 'import try from dw::Runtime'. When applied to invalid input — such as a malformed number string like '12.5O' — the function captures the error details without crashing the transformation. The script can then return an RFC 7807-compliant error response, including fields like type, title, status, detail, and instance. Developers are advised to verify the import exists before executing any transformation that relies on the try() function.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Evidence Mounts That Self-Driving Cars Are Safer Than Human Drivers

Emerging data is strengthening the case that autonomous vehicles can reduce road fatalities compared to human-driven cars. Researchers and industry analysts have been examining real-world performance records from self-driving fleets to assess their safety profiles. The findings suggest that automated driving systems may commit fewer critical errors than human drivers, who are often affected by fatigue, distraction, and impairment. While the technology is still maturing, the accumulating evidence is shifting the conversation around autonomous vehicle safety from skepticism toward cautious optimism.

0 comments Read more at Hacker News

ProgrammingHacker News ·

RDLTR Launches as an Inbox-Zero Read-Later App to Replace Pocket and Rivals

A developer has released RDLTR, a read-later web app designed around an inbox-zero model where articles disappear from the queue once read but remain accessible in an archive. The project was inspired by frustration with tab clutter across multiple devices and the shutdown of Pocket, after alternatives like Instapaper and Raindrop failed to match the desired workflow. RDLTR supports URL pasting, drag-and-drop, browser extensions for Chrome and Firefox, a bookmarklet, and an iOS share sheet shortcut. Extensions offer additional features such as sending article text to AI tools like ChatGPT or Claude, and opening links via the Internet Archive to bypass paywalls. The app is built on Bun, TypeScript, HTMX, and SQLite, hosted on a Hetzner VPS, and is available at rdltr.app.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

How question framing shifts which arguments AI models emphasize, not just tone

A developer ran an informal experiment last week testing how differently worded prompts affected responses from three AI assistants on the same underlying question. Using neutral, positively loaded, and negatively loaded versions of the same query, the tester found that framing influenced which considerations the model foregrounded, not merely the tone of its language. The neutral prompt surfaced a broader range of arguments, while loaded prompts led models to prioritize the side implied by the question, sometimes omitting key counterpoints entirely. This behavior is linked to how large language models are trained on human preferences, which can incentivize responses that align with a user's implied conclusion. The author warns that a model can appear balanced while still being directionally persuasive through selective emphasis and ordering of arguments.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Connect VS Code to a Remote JupyterLab Server on GeoLab

Developers can connect their local VS Code editor to a remote JupyterHub instance running on GeoLab, a 2i2c-managed Kubernetes platform hosted at geolab.earthscope.cloud. The setup requires the VS Code Jupyter extension and a running GeoLab server pod, from which users generate a tokenized public URL using a short Python script. This URL replaces the internal 0.0.0.0:8888 address with the public hub host and appends an authentication token, which must be kept private. Users paste the URL into VS Code's kernel picker under 'Existing Jupyter Server' to route notebook execution to the remote GeoLab pod rather than their local machine. Common issues include expired tokens, incorrect URL encoding of OAuth2 user IDs, and pod culling, all of which have documented workarounds in the guide.

0 comments Read more at DEV Community