Merge branch 'master' into rei/roadmap-path

blog/news-and-updates/2024-12-28-update.mdx

@@ -0,0 +1,55 @@
+---
+title: Developer weekly update December 18, 2024
+description: This week, we're going to take a look at the road ahead for ICP developers in 2025 and dive into some roadmap items and ongoing initiatives that we'll see take the stage in the new year.
+tags: [Devs]
+image: /img/blog/dev-update-blog-dec-18.jpg
+---
+
+# Developer weekly update December 18, 2024
+
+![December 18 2024](../../static/img/blog/dev-update-blog-dec-18.jpg)
+
+Hello developers, and welcome to this week's developer weekly update! This week, we're going to take a look at the road ahead for ICP developers in 2025 and dive into some roadmap items and ongoing initiatives that we'll see take the stage in the new year. Let's get started!
+
+## Roadmap milestones
+
+In 2025, ICP will work toward several roadmap milestones, including:
+
+- Flux: Focused on increasing network compute capacity and scalability, Flux plans to implement asynchronous checkpointing and canister migration between subnets.
+
+- Ignition: Part of the decentralized AI roadmap, the Ignition milestone will expand compute and memory capabilities of canisters.
+
+- Helium: Next up in the Chain Fusion roadmap is an integration with Solana through a Solana RPC canister.
+
+- Niobium: The long-awaited vetKeys feature enabling decentralized key management.
+
+You can view details about the roadmap on [internetcomputer.org](https://internetcomputer.org/roadmap).
+
+## Decentralized AI: DeAI Manifesto
+
+Decentralized AI on ICP is just getting started and will be a major topic of conversation and development in 2025. Recently, the DeAI working group put together the [DeAI Manifesto](https://deaimanifesto.com/), a set of parameters and values that they believe will drive decentralized AI across all ecosystems—not just ICP. Some of these values include:
+
+- DeAI is safe AI.
+
+- DeAI is responsible AI.
+
+- DeAI is verifiable. AI
+
+You can read and sign the [DeAI Manifesto](https://deaimanifesto.com/) to participate in DeAI on ICP.
+
+## ICP developer ecosystem growth
+
+In the [Electric Capital 2024 Developer Report](https://www.developerreport.com/developer-report), the ICP developer community ranked highly across several different statistics, including:
+
+- In 2024, ICP was the third largest ecosystem for new developers.
+
+- In 2024, ICP was the second highest chain for full-time developer growth.
+
+- In Africa, ICP was the third most popular blockchain ecosystem.
+
+More details can be found [on X](https://x.com/dfinity/status/1867619158906876252).
+
+That'll wrap up this week and this year! Tune back in 2025 for more developer updates!
+
+-DFINITY
+

docs/references/https-outcalls-how-it-works.mdx

@@ -162,7 +162,7 @@ There are a number of error cases that can happen when using this feature. The m
 * **SysFatal - Timeout expired:** requests are timed out if not fulfilled within the timeout period. One important instance when this happens is when there are not sufficiently many equal responses to achieve consensus. This happens, for example, when the transformation function is not written accurately to account for all variable parts of responses.
 * **SysTransient - Failed to connect: error trying to connect: tcp connect error: Connection refused (os error 111):** this error indicates that a TCP connection could not be established with the other server. This is most likely due to the fact that the server you are calling is not supporting IPv6.
 * **CanisterReject - http_request request sent with 0 cycles, but ... cycles are required:** at least the required amount of cycles need to be sent with the request in order for it to get fulfilled by the subnet.
-* **CanisterReject - max_response_bytes expected to be in the range [0..2097152], got ...:** this error indicates that the network response received from the server was too large. This happens if the response size is underestimated and the `max_response_bytes` value set too low.
+* **CanisterReject - max_response_bytes expected to be in the range [0..2000000], got ...:** this error indicates that the network response received from the server was too large. This happens if the response size is underestimated and the `max_response_bytes` value set too low.
 * **SysFatal - Transformed http response exceeds limit: 2045952:** this error indicates that the limit for the transformed response size was reached. This is currently a hard response size limit of the HTTPS outcalls functionality. Note that the response size is computed based on response body and headers.
 
 Developers new to the feature are likely to run into certain problems in the beginning, materializing in one of the following errors. This page lists the most prominent issues when starting with this feature.