text:
Datatree release blog post

[x] Closes #708, and a bullet from https://github.com/pydata/xarray/issues/8572

I would like to merge this soon, ideally before AGU next week. Note the post is actually much more about the NASA x Xarray collaboration than it is about the DataTree class itself, as that should be covered by the docs. Let me know if you agree with my summary of how the migration project went! 😀
cc @shoyer @keewis @owenlittlejohns @flamingbear @eni-awowale @aladinor @briannapagan

Thanks for the comments - I've addressed them and am planning to publish this tomorrow.


text:
Alter column operations should allow specification of unchanged fields

Alter column operations should support specifying fields that are unchanged as no-ops.
For example, this migration:
{
  "name": "35_alter_column_multiple",
  "operations": [
    {
      "alter_column": {
        "table": "events",
        "column": "name",
        "name": "event_name",
        "nullable": false,
        "up": "(SELECT CASE WHEN name IS NULL THEN 'placeholder' ELSE name END)",
        "down": "name"
      }
    }
  ]
}

Renames a field and sets it to NOT NULL. If the field is already NOT NULL, the operation should not perform any column duplication or backfilling to support setting the column nullability.

@andrew-farries I'm not sure what needs to be done here. Can you give an example of the desired migration schema?

The motivation for this was to allow migrations like the following:
Create a table with a NOT NULL field:
{
  "name": "01_create_table",
  "operations": [
    {
      "create_table": {
        "name": "reviews",
        "columns": [
          {
            "name": "id",
            "type": "serial",
            "pk": true
          },
          {
            "name": "review",
            "type": "varchar(255)",
            "nullable": false
          }
        ]
      }
    }
  ]
}

Attempt to set the already NOT NULL field to NOT NULL:
{
  "name": "02_no_op",
  "operations": [
    {
      "alter_column": {
        "table": "reviews",
        "column": "review",
        "nullable": false,
        "up": "(SELECT CASE WHEN review IS NULL THEN product || ' is good' ELSE review END)",
        "down": "review"
      }
    }
  ]
}

Starting the second migration currently fails with a validation error:
Failed to start migration: migration is invalid: column "review" on table "reviews" is NOT NULL

This issue would allow the second migration, making it a no-op rather than failing validation. This could make it easier for clients to generate migrations by pushing the no-op calculation on to pgroll.
Thinking about it some more though, I'm not sure this would be a good change. What should the result of the second migration be? We'd need some way for a migration to pass validation but not be executed. In most cases I think the second migration is an error that should be reported rather than silently turned into a no-op.

@andrew-farries Given that we're not convinced this actually a good change, shall we close the issue?
Perhaps we can consider it again if it comes up often in real world scenarios.

source: gharchive/issue

authors: andrew-farries ryanslade

repo: xataio/pgroll

license_type: permissive

license_source: github-api


text:
github actions for multi-arch builds

Create a GitHub secret with the name DOCKER_TOKEN and add your docker-hub access token to it.

Some consideration

Change main to develop, as stable/main use tag version vX.Y.Z and develop as rolling release one.
Add qemu before buildx.

      # https://github.com/docker/setup-qemu-action
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v1
      # https://github.com/docker/setup-buildx-action
      - name: Set up Docker Buildx
        id: buildx
        uses: docker/setup-buildx-action@v1

Docker login using actions. Like for reusability

-
        name: Login to Docker Hub
        uses: docker/login-action@v1
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}

Use meta and build push, practically just tag conditioning

# https://github.com/docker/metadata-action
-       name: Docker meta
        id: <themetaname>
        uses: docker/metadata-action@v3
        with:
          images: <the image name>
          tags: |
            type=ref,event=branch
            type=ref,event=pr
            type=semver,pattern={{version}}
            type=semver,pattern={{major}}.{{minor}}
-       name: Build and push
        uses: docker/build-push-action@v2
        with:
          context: .
          push: ${{ github.event_name != 'pull_request' }} #push except PR.
          tags: ${{ steps.<themetaname>.outputs.tags }}
          labels: ${{ steps.<themetaname>.outputs.labels }}

Don't really need QEMU, GitHub support multiarch images by default

Really? cant really make it to run, https://github.com/martadinata666/goaccess-for-nginxproxymanager/actions/runs/2043113126

@martadinata666 thanks, I added QEMU.
  {
    "name": "builder-2a695eea-186a-4b5e-a061-c5cded613a82",
    "driver": "docker-container",
    "node_name": "builder-2a695eea-186a-4b5e-a061-c5cded613a820",
    "node_endpoint": "unix:///var/run/docker.sock",
    "node_status": "running",
    "node_flags": "--allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host",
    "node_platforms": "linux/amd64,linux/amd64/v2,linux/amd64/v3,linux/arm64,linux/riscv64,linux/ppc64le,linux/s390x,linux/386,linux/mips64le,linux/mips64,linux/arm/v7,linux/arm/v6"
  }

For some reason,  it worked out of the box for another test repo I was testing in
https://github.com/Just5KY/scalyr-tool/runs/5697565469?check_suite_focus=true
I will add

@martadinata666 thanks, I added QEMU.
  {
    "name": "builder-2a695eea-186a-4b5e-a061-c5cded613a82",
    "driver": "docker-container",
    "node_name": "builder-2a695eea-186a-4b5e-a061-c5cded613a820",
    "node_endpoint": "unix:///var/run/docker.sock",
    "node_status": "running",
    "node_flags": "--allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host",
    "node_platforms": "linux/amd64,linux/amd64/v2,linux/amd64/v3,linux/arm64,linux/riscv64,linux/ppc64le,linux/s390x,linux/386,linux/mips64le,linux/mips64,linux/arm/v7,linux/arm/v6"
  }

For some reason, it worked out of the box for another test repo I was testing in https://github.com/Just5KY/scalyr-tool/runs/5697565469?check_suite_focus=true I will add

Because it doesnt do anything, ADD itself from use internal docker function to fetch files, so basically it just repacking. THe manifest itself will overwrite each other i assume.

I looked this over and tested it on a different repo and it appears to be working correctly.
However, I found that it builds from scratch every time. It takes about 6 minutes. It's not horrible but I was looking into using caching on the docker layers. I implemented the following code on my other repo. It seems to work. Let me know what you guys think.
https://evilmartians.com/chronicles/build-images-on-github-actions-with-docker-layer-caching
https://github.com/docker/build-push-action/blob/master/docs/advanced/cache.md
@Just5KY @martadinata666
name: Main branch build & push

on:
  #schedule:
  #  - cron: '50 15 * * *'  #Change this to when you want automatic builds
  push:
    branches: [ main ]
    tags: [ 'v*.*.*' ]
  pull_request:
    branches: [ main ]
  workflow_dispatch:

env:
  REGISTRY: docker.io
  IMAGE_NAME: goaccess-for-nginxproxymanager

jobs:
  build:

    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write
      # This is used to complete the identity challenge
      # with sigstore/fulcio when running outside of PRs.
      id-token: write

    steps:
      - name: Checkout repository
        uses: actions/checkout@v2

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v1

      - name: Setup Docker buildx
        uses: docker/setup-buildx-action@79abd3f86f79a9d68a23c75a09a9a85889262adf

      - name: Cache Docker layers
        uses: actions/cache@v2
        with:
          path: /tmp/.buildx-cache
          key: ${{ runner.os }}-buildx-${{ github.sha }}
          restore-keys: |
            ${{ runner.os }}-buildx-

      - name: Login to Docker Hub
        uses: docker/login-action@v1
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}

      - name: Build and push
        uses: docker/build-push-action@v2
        with:
          context: .
          push: true
          tags: xavierh/goaccess-for-nginxproxymanager:latest
          platforms: linux/amd64,linux/arm/v7,linux/arm64/v8
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache-new

      - name: Move cache
        run: |
          rm -rf /tmp/.buildx-cache
          mv /tmp/.buildx-cache-new /tmp/.buildx-cache

the considertion with cache is, it using cached version instead newest image. Ex  we use alpine:3.15 AS builder as this rarely changed, alpine3.15 today not the same alpine3.15 upstream if upstream got update. Personally not a fan of this.
setup-buildx-action@79abd3f86f79a9d68a23c75a09a9a85889262adf" it just version revision.
My workflows, using consideration i mention above
name: Docker Image Build

on:
  push:
    branches: [ 'develop' ] #rolling build on develop only
    tags: 'v*' #tag for specific release v1.0.2,or anytag, start with v
  pull_request:
    branches: [ 'main' ] #build test on main, not pushing
  workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write
      # This is used to complete the identity challenge
      # with sigstore/fulcio when running outside of PRs.
      id-token: write

    steps:
      - name: Checkout repository
        uses: actions/checkout@v2

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v1

      - name: Setup Docker buildx
        uses: docker/setup-buildx-action@v1
      - name: Login to Docker Hub
        uses: docker/login-action@v1
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}

      - name: Docker meta
        id: metaid
        uses: docker/metadata-action@v3
        with:
          images: ${{ secrets.DOCKERHUB_USERNAME }}/goaccess-nginx-proxy-manager
          tags: |
            type=ref,event=branch
            type=ref,event=pr
            type=semver,pattern={{version}}
            type=semver,pattern={{major}}.{{minor}}

#      - name: Cache Docker layers
#        uses: actions/cache@v2
#        with:
#          path: /tmp/.buildx-cache
#          key: ${{ runner.os }}-buildx-${{ github.sha }}
#          restore-keys: |
#            ${{ runner.os }}-buildx-

      - name: Build and push
        uses: docker/build-push-action@v2
        with:
          context: .
          push: ${{ github.event_name != 'pull_request' }} #push except PR.
          platforms: linux/amd64,linux/arm64,linux/arm/v7
          tags: ${{ steps.metaid.outputs.tags }}
          labels: ${{ steps.metaid.outputs.labels }}
          cache-from: type=local,src=/tmp/.buildx-cache
          cache-to: type=local,dest=/tmp/.buildx-cache-new

#      - name: Move cache
#        run: |
#          rm -rf /tmp/.buildx-cache
#          mv /tmp/.buildx-cache-new /tmp/.buildx-cache

i updated the docker action and changed setup-buildx-action@79abd3f86f79a9d68a23c75a09a9a85889262adf with setup-buildx-action@v1
since they both were doing the same thing

@Just5KY I'll get to this in a couple of days. I already confirmed that everything works.

Yes it works
I push images to my dockerhub using this for the latest version

Only need :latest tag?  🤔
Isn't usually
v1.0 latest
then
v1.1 latest
So there will be roll back to prev image in case errored out. Well, it depends on your need, if it suit you, it ok. 👍🏼

@martadinata666 i am not really good with variables, if you can edit that part

source: gharchive/pull-request

license: MIT


text:
Any idea how to improve rendering performance ?

Hi,
Nice job, this is the best pdf reader library i found for rn so far, easy to install.
I was wondering if you would have some advice to improve the rendering, i have a client which use really heavy PDF file.
On iOS with the default reader it takes forever, with your library it is slightly better but not enough to be seamless.
Any idea on how i could improve the performance ?
Thanks

Please try the latest version, in a decrease package size that may help to improve performance a bit.

authors: nrcaz xcarpentier

repo: xcarpentier/rn-pdf-reader-js


text:
Parsing failed on Windows 11

Describe the bug
I run cargo tarpaulin and receive error Error: "Parsing failed".
I am using Windows 11 and run this from Git Bash.
Complete ouptut (skipping compilation):
    Finished test [unoptimized + debuginfo] target(s) in 51.35s
May 11 00:51:58.814  INFO cargo_tarpaulin::process_handling: running C:\work\probranchinator\target\debug\deps\probranchinator-5c461d614048b00c.exe
May 11 00:51:58.815  INFO cargo_tarpaulin::process_handling: Setting LLVM_PROFILE_FILE

running 5 tests
test tests::analysis_test::test_analysis_one_branch ...
 ███████████████████████████████████████████████████ 0/1 branches analysed in 0s
ok
test tests::analysis_test::test_analysis_unrelated_branches ... ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░2 branches analysed in 0s
ok
test tests::analysis_test::test_analysis_up_to_date_and_fast_forward ... ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░2 branches analysed in 0s
ok
test tests::repo_test::test_delete_remote_branch ... Pruning origin
URL: file:///C:/Users/strow/AppData/Local/Temp/.tmppCMm2h/my-repo.git/
 * [pruned] origin/test-branch
ok
test tests::repo_test::test_get_repo ... ok

test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.21s

May 11 00:52:00.254  INFO cargo_tarpaulin::statemachine::instrumented: For binary: target\debug\deps\probranchinator-5c461d614048b00c.exe
May 11 00:52:00.254  INFO cargo_tarpaulin::statemachine::instrumented: Generated: target\tarpaulin\profraws\probranchinator-5c461d614048b00c.exe_12256345248713744009_0-25344.profraw
May 11 00:52:00.254  INFO cargo_tarpaulin::statemachine::instrumented: Merging coverage reports
May 11 00:52:00.260 ERROR cargo_tarpaulin: Parsing failed

I did not pass "--engine", not sure if it is ptrace or llvm instrumentation.
To Reproduce
I am getting it on this repository - https://github.com/strowk/probranchinator
Attached from "target/tarpaulin/profraws":
probranchinator-5c461d614048b00c.exe_12256345248713744009_0-25344.zip
Expected behavior
No errors, result of coverage analysis.

Note, that the output is OK when I run same project via docker like this:
docker run --security-opt seccomp=unconfined -ti -v "$(pwd -W):/volume" xd009642/tarpaulin bash -c " git config --global user.name 'Test Fella' && git config --global user.email 'justfortest@domain.example' &&  cargo tarpaulin"

(pwd -W is specific for combination of Mingw and docker in Windows, git config is  for tests as they use git CLI a little bit)
I get "10.40% coverage, 99/952 lines covered" and more output, so this seems a success (barring low coverage, but that's why I want to measure it in the first place).
This run via docker utilizing wsl 2, which is basically linux in VM, so basically same as real linux AFAIK.
This make me think that the issue I have is potentially Windows specific.

Sorry it's taken a while, I did just download the file you uploaded to test to see if there was anything i could glean from it. Running with the llvm tools I get:
error: probranchinator-5c461d614048b00c.exe_12256345248713744009_0-25344.profraw: malformed instrumentation profile data: function name is empty

There's a chance this may be OS specifc as these tools aren't designed to parse files generated on different architectures to the host and I'm running on Linux. I'll get access to a windows machine some point next week and test it there as the project works fine on linux for me in tarpaulin.

It happens to me also.

I reproduced this on Linux.
It seems that this is broken on Nightly rust, on Stable, things work just fine.

So releasing a new version today that may solve this, let me know how it works - sorry for the delay

I re-ran a workflow that previously failed on one of my personal FOSS projects.
I can confirm this now runs.
Thank you a lot.

license_source: bigquery


text:
Types of pi's usable

What types of raspberry pi's has this been tested on?
Does this take a significant amount of power or it is it lightweight? Would this work on a raspberry pi zero w work?
Btw this is an amazing idea! Keep up the good work dude

I would suggest using one of the Pi's that has an Ethernet port bc imagine making a Dropbox that has a ton of adapter (Pi Zero)

Could this be used over a usb connection with the pizero?
IE
https://learn.adafruit.com/turning-your-raspberry-pi-zero-into-a-usb-gadget/ethernet-gadget
Love it so far, thanks for the work put in.

I can also confirm this works under headless pi using usb0 interface.

authors: MrOgieBogie thehappydinoa zerocolTHS

repo: xdavidhu/lanGhost


text:
rpi5: fix build of dom0 app

commit dbe6b2c ("xen-dom-mgmt: Get back the domain id from xen_domctl_createdomain") went xenlib
commit eb0ed211274 ("xen: domctl: Get back created domain id") went zephyr-v3.6.0-xt
The above commit is also required for rpi 5 - so cherry-pick it to fix the build.

Thanks

repo: xen-troops/zephyr


text:
Support for seelie.me

Hello.
First up great work. Was looking for an achievement scanner and finally found one that worked perfectly.
While I personally use paimon.moe for achievements there are also other sites like seelie.me that support achievements.
Seelie.me is also offering an data import/export feature which should allow you to add the data like with paimon.moe

Will add this soon. Thanks for the suggestion!

authors: Gol-D-Ace xenesty

repo: xenesty/AkashaScanner


text:
Dual switch mode doesn't work.

First off, great program. My only issue is that when switching default Playback device the Recording device doesn't switch as well. Not sure if I'm doing something wrong or if it's a bug. Thanks.

Dual Switch mode switches Communications along with the Default, it's not meant to switch playback and capture at the same time.

authors: Lochstock xenolightning

license: MS-PL


text:
[Bug] Uncaught Error: Cannot find module 'onnxruntime-node'

This bug happens after I upgrade the package from 1.4.3 to 2.4.2.
I am using Next.js, is it due the client/server side issue?

Can you post your next config file?
I am busy working on a next.js example application, which you can find here: https://github.com/xenova/transformers.js/pull/211

Yes I followed that example...
`/** @type {import("next").NextConfig} */
const nextConfig = {
// Override the default webpack configuration
webpack: (config) => {
// Ignore node-specific modules when bundling for the browser
// https://webpack.js.org/configuration/resolve/#resolvealias
config.resolve.alias = {
...config.resolve.alias,
sharp$: false,
"onnxruntime-node$": false,
};
return config;
},
};
module.exports = nextConfig;
`

I am not using the App router.

The above tutorial was designed for the app router. So that might explain why that config is causing an issue.
From the previous solution (which worked for v1.4.3), just remember to remove the part where you use the IgnorePlugin

I got it working using your next.config! It turns out it's some other issues... Also how can I use the models on the server-side?

Also how can I use the models on the server-side?

Working on that! I think it should be possible by:

Using node-loader or webpack-asset-relocator-loader
Updating config to separate server and client bundling (work in progress).

// Override the default webpack configuration
webpack: (config, { buildId, dev, isServer, defaultLoaders, nextRuntime, webpack }) => {
    if (isServer) {
        // TODO...
    } else {
        // Ignore node-specific modules when bundling for the browser
        // https://webpack.js.org/configuration/resolve/#resolvealias
        config.resolve.alias = {
            ...config.resolve.alias,
            "sharp$": false,
            "onnxruntime-node$": false,
        }
    }

    return config;
},

That's great! Does server-side support mean that the models could run on the serverless functions within Vercel hosting?

Does server-side support mean that the models could run on the serverless functions within Vercel hosting?

I haven't tested it yet, but if they can run normal node packages, then it should be possible 👍

Got server-side working 👍  PR: https://github.com/xenova/transformers.js/pull/211 (will merge into main soon)
Demo app: https://huggingface.co/spaces/Xenova/next-server-example-app


text:
[feat] Image and artifact signing

This adds signing for xeol using SigStore's public tlog via GitHub Actions OIDC device flow.
Adds signing for the binaries and for the docker images, as well as associated SBOM data.
Verifying the xeol binary
This is how we'd verify the checksums associated with the xeol binary v0.3.4
cosign verify-blob \
--certificate https://github.com/xeol-io/xeol-io/releases/download/v0.3.4/checksums.txt.pem \
--signature https://github.com/xeol-io/xeol-io/releases/download/v0.3.4/checksums.txt.sig \
--certificate-identity https://github.com/xeol-io/xeol-io/.github/workflows/release.yml@refs/tags/v0.3.4 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
https://github.com/xeol-io/xeol-io/releases/download/v0.3.4/checksums.txt

Verifying the xeol docker image
And this is how we'd verify the docker image
cosign verify ghcr.io/xeol-io/xeol \
--certificate-identity https://github.com/xeol-io/xeol/.github/workflows/release.yaml@refs/tags/v0.3.4 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com

Don't have time to complete this right now, will do at a later time.

repo: xeol-io/xeol


text:
Preload is never resolved when an empty array is passed in.

When an empty array is passed into the preload() function, the promise is never resolved. Changed the code so that is checks for an empty array.
Also might be a good idea to add a Prettier file into the project so the styling is consistent.

Unfortunately i messed up when adding the pull requests but this is added in the latest release.
Best regards 🚀

authors: joe-yeomans xerdnu

repo: xerdnu/react-native-blasted-image


text:
Show tooltip/title on the tags in select inputs with enableMulti: true

This could be useful to users when the select component is not wide enough to show the whole tag value.

Resolved in #3367

authors: amcclain cnrudd

repo: xh/hoist-react


text:
demo里面播放的时候怎么没有声音？

https://xiangyuecn.github.io/Recorder/
demo里面播放的时候怎么没有声音？

录制的时候有没有观察到绿色进度条随着音量跳动？
如果有：控制台中把输出的blob存储为变量，然后URL.createObjectURL(temp1)，把生成的地址在新标签中打开试试，也可以通过这个地址把音频下载下来。
如果没有：把demo放手机上试试。

能不能支持暂停呢？

@dirtyclean 已提供暂停支持

谢谢大神。

demo 声音播放在手机上面是可以的，那么chrome，70上面播放没有声音？

@TML4140  笔记本win 7，新下载的 chrome 版本 70.0.3538.110（正式版本） （64 位） 有声音，你啥电脑

Chrome 本地mp3 无声音 进度条走动 但是mp3 播放没有声音

@shuaiyinoo 怪不得好几个人都说没声音呢，原来mp3编码器的锅，能发一下浏览器useragent我来复现一下吗

@xiangyuecn 全部码率都有声音了。感谢

@David-webb 苹果估计只有最新版系统自带浏览器才支持，其他app，嘿嘿嘿嘿
uc没试过，国内自带浏览器一般都是渣渣，腾讯的X5都比他们支持的好，囧

请问没有声音和手机系统有关系吗？ 微信里两种方式都可以，测试如下环境chrome、oppo自带浏览器、火狐、QQ浏览器、搜狗浏览器都没有声音（没有绿色，下载下来也没声音），但是在chrome用您推荐的那个auto-only.html测试网页是有声音的，还请大神看看什么原因呢？
浏览器环境情况:
AudioContext:true
webkitAudioContext:false
mediaDevices:true
mediaDevices.getUserMedia:true
navigator.getUserMedia:true navigator.webkitGetUserMedia:true UA:Mozilla/5.0 (Linux; Android 6.0.1; OPPO R9sk Build/MMB29M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.91 Mobile Safari/537.36

authors: TML4140 abczdefg dirtyclean fxjs shuaiyinoo xiangyuecn xml4cn

repo: xiangyuecn/Recorder


text:
文档

大神考虑写一份中文文档吗？读起来方便

暂时不考虑

repo: xianhu/PSpider