that is, that instead of using dockerhub_run.sh, one can use ./bin/docker_build_image.sh + ./bin/docker_run.sh

This option actually worked for me but it's not documented, while ./bin/dockerhub_run.sh didn't work.

RLHF without RL - Direct Preference Optimization | ICLR Blogposts 2024

We discuss the RL part of RLHF and its recent displacement by direct preference optimization (DPO). With DPO, a language model can be aligned with human preferences without sampling from an LM, thereby significantly simplifying the training process. By now, DPO has been implemented in many projects and seems to be here to stay.

https://iclr-blogposts.github.io/2024/blog/rlhf-without-rl/

The download falls when trying to retrieve module from http://deb.debian.org/debian bookworm

Updating package manager, pruning docker image in my local and every step in guide has failed me.

To Reproduce
Steps to reproduce the behavior:

1. Run ./bin/docker_run.sh
2. See error in additional context

System (please complete the following information):

• OS: Ubuntu 16.04.6 LTS
• Docker version: Docker version 18.09.6, build 481bc77

Additional context

Step 3/16 : RUN apt-get update -y
.
.
.
Err:3 http://deb.debian.org/debian-security bookworm-security InRelease
  At least one invalid signature was encountered.
Reading package lists...
W: GPG error: http://deb.debian.org/debian bookworm InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian-security bookworm-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian-security bookworm-security InRelease' is not signed.
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
The command '/bin/sh -c apt-get update -y' returned a non-zero code: 100
Unable to find image 'al-folio:latest' locally
docker: Error response from daemon: pull access denied for al-folio, repository does not exist or may require 'docker login'.
See 'docker run --help'.

I get the error "

Could not find gem 'jekyll-target-blank' in locally installed gems
Run `bundle install` to install missing gems.

The error message is confusing, as I guess this is an error from docker not having some packages? running locally bundle install doesn't change anything

Building Diffusion Model's theory from ground up | ICLR Blogposts 2024

Diffusion Model, a new generative model family, has taken the world by storm after the seminal paper by Ho et al. [2020]. While diffusion models are often described as a probabilistic Markov Chain, their fundamental principle lies in the decade-old theory of Stochastic Differential Equation (SDE), as found out later by Song et al. [2021]. In this article, we will go back and revisit the 'fundamental ingredients' behind the SDE formulation, and show how the idea can be 'shaped' to get to the modern form of Score-based Diffusion Models. We'll start from the very definition of 'score', how it was used in the context of generative modeling, how we achieve the necessary theoretical guarantees, how the design choices were made and finally

https://dasayan05.github.io/2024/blog/diffusion-theory-from-scratch/

Markdown links don't appear to be rendering when they are placed in footnotes. When the example below is rendered, the link in the body appears as expected, but the one in the footnote appears as the markdown.

---
layout: distill
title: Example
description: Example
date: 2024-05-07
future: true
authors:
  - name: Anonymous
bibliography: 2024-05-07-distill-example.bib
toc:
  - name: Footnotes
---

## Footnotes

Just wrap the text you would like to show up in a footnote in a `<d-footnote>` tag.
The number of the footnote will be automatically generated.<d-footnote>This will become a hoverable footnote. [Test link](https://www.google.com/)</d-footnote>

***

[Lorem ipsum](https://www.google.com) dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Hi,

When pushing a modified figure in the blogpost repo, the modification is not taken into account in the deployed blogpost under the url https://d2jud02ci9yv69.cloudfront.net/2024-05-07-[SUBMISSION NAME]. The figure https://d2jud02ci9yv69.cloudfront.net/2024-05-07-[SUBMISSION NAME]/assets/img/2024-05-07-[SUBMISSION NAME]/my_figure.png is still the first version of the figure which differs from the one in the repo.

Hi,

Thanks for the great efforts!

I am trying to submit a PR, which has passed all checks but it returns a website showing 404 Not Found. The error message is below:

404 Not Found

Code: NoSuchKey
Message: The specified key does not exist.
Key: 2024-05-07-seesaw-91/blog/seesaw/index.html
RequestId: J4E4M0M4ZBW8EJ9M
HostId: p3rwnNxc8xkaFfELTj7WY8eFtM9xjfrEWPdCDHaDwkizqAyMLaKM6+lBA/rilGDGBMzRTsjMdFA=

Hope you could help with this issue.

Thanks again :)

I currently see in the repo _bibliography/papers.bib and assets/bibliography/2024-05-07-distill-example.bib.

What is the first one used for? do we need both?

see for example https://github.com/iclr-blogposts/2024/actions/runs/6591771757

I'm commenting out for now the offending lines since the upload script depends on the success of this script

The relevant section of the Sample Blog Post is now rendered like this on my Mac, both in Chrome and Safari:

Which doesn't seem correct. If I reload the page, for a split second it seems to show the correct C++ syntax highlights, so I suspect there is some unintended style sheet overwrite going on. The same happens when I work on my own blog post with python syntax highlighting.

Section "Other Typography?". This is what I see in https://iclr-blogposts.github.io/2024/blog/distill-example/#other-typography

While from the description, " Unordered sub-list." should be a sub-element of the previous item

Ideally, information should be in only one place.

1. Hi @fabianp, how do I add submission label to PR ?

2. The URL that I get after the PR build is https://xxxxxxxx.cloudfront.net/2024-05-07-submission-name/. But openreview is expecting (erroring otherwise) something like https://iclr-blogposts.github.io/2024/blog/[YOUR_SUBMISSION]/. Where do I get the submittable URL ?

The submission instructions state:

Open a pull request against the main branch of the [2024 repo](https://github.com/iclr-blogposts/2024). Fill in the checklist provided in the PR template. The title of your pull request should be exactly the name of your markdown/html file.

i.e. _posts/2024-05-07-[SUBMISSION NAME].md would require a PR name 2024-05-07-[SUBMISSION NAME]

(TBD) Your post will automatically run two pipelines: one to verify that you have not modified any other file in the repo, and another that will create a unique URL for your contributed blog post.

Verify that everything looks correct in the given URL.
If the pipelines failed, check if it was because of improper formatting (i.e. you modified restricted files). If this is the case, fix the issues. If the issue persist, please ping one of the repo admins.

I opened a PR here but I've been unable to find out where our submission URL is. I don't see a comment on the PR and I haven't received anything by email.

Could someone please clarify?

The example post includes in the header

future: true
htmlwidgets: true

It would be nice to add a comment to explain what is the impact of these variables

see for example the failure here (https://github.com/iclr-blogposts/2024/actions/runs/6591862546/job/17911339054#step:9:38), which happened for the title "test post "