text:
DSMR configuration page not working through Ingress

Gives this error:
Verboden (403)
CSRF-verificatie mislukt. Aanvraag afgebroken.
U ziet deze melding, omdat deze HTTPS-website vereist dat uw webbrowser een ‘Referer header’ meestuurt, maar deze ontbreekt. Deze header is om veiligheidsredenen vereist om er zeker van te zijn dat uw browser niet door derden wordt gekaapt.
Als u ‘Referer’-headers in uw browser hebt uitgeschakeld, schakel deze dan weer in, op zijn minst voor deze website, of voor HTTPS-verbindingen, of voor ‘same-origin’-aanvragen.
Als u de tag  gebruikt of de header ‘Referrer-Policy: no-referrer’ opneemt, verwijder deze dan. De CSRF-bescherming vereist de ‘Referer’-header voor strenge referer-controle. Als u bezorgd bent om privacy, gebruik dan alternatieven zoals <a rel="noreferrer" …> voor koppelingen naar websites van derden.
Meer informatie is beschikbaar met DEBUG=True.
Sorry for it being in dutch :-)
It's only the configuration page, were you need to login. After entering username password this error occurs. All other pages are working normal.

Same issue here

For me as well but only if I access Home Assistant through my ddns domain name via https.
If I access Home Assistant via local ip then the DSMR configuration panel opens fine.

I verified the problem. I will add it on my to do list after my holiday. For now indeed like @rboeters is saying, use the configuration panel from the internal ip address.

For me as well but only if I access Home Assistant through my ddns domain name via https.
If I access Home Assistant via local ip then the DSMR configuration panel opens fine.

Unfortunately that is not a workaround for me, I get the same error on the internal IP and outside URL

I'm running into the same issue, unfortunately the workaround does not work for me either.

Confirmed, will wait for the next DSMR Reader release. So for now you have to configure the software internally with a non secure address.

repo: sanderdw/hassio-addons


text:
Release/1.5.0

WIP
This pull request includes various changes to the Whisper.net project, including updates to files, target frameworks, and added functionality. The most important changes include adding a new parameter to specify the model's execution location (GPU or CPU), updating the target framework of the project, and adding new delegate types and fields to existing structs in the Data.cs file.
Main changes:

Whisper.net/Whisper.net.csproj: Updated the target framework of the Whisper.net project to net8.0.
Whisper.net/WhisperFactory.cs: Added a new parameter to specify whether the model should be loaded on the GPU or CPU.
Whisper.net/Internals/Native/Data.cs: Added new delegate types and a struct for logging and aborting callbacks, and added new fields to existing structs for context parameters. [1] [2]

Other changes:

Whisper.net/Logger/LogProvider.cs: Added a MIT license header to LogProvider.cs file.
Whisper.net/Internals/ModelLoader/WhisperProcessorModelFileLoader.cs: Added a new constructor parameter and updated a method to allow the user to specify whether a model should be loaded on the GPU or CPU.
Whisper.net/Logger/WhisperLogLevel.cs: Added a new enum, WhisperLogLevel, which includes three log levels: Error, Warning, and Info.
Whisper.net/Internals/ModelLoader/WhisperProcessorModelBufferLoader.cs: Updated the Dispose method to allow the user to specify whether the model should be loaded on the GPU or CPU, and added a new field useGpu to the WhisperProcessorModelBufferLoader class.
Whisper.net/Internals/Native/NativeMethods.cs: Included several changes to the NativeMethods class, including the addition of new methods and the replacement of existing methods.
Whisper.net/Whisper.net.Tests.csproj: Updated the target framework of the Whisper.net.Tests project to net8.0.
whisper.cpp: Updated the submodule commit in whisper.cpp from 2f52783a080e8955e80e4324fed73e2f906bb80c to e2f0eba2d4dbe4ded5625cbd8a9c17e13f2482f6.
Whisper.net.Demo/Whisper.net.Demo.csproj: Updated the target framework in the Whisper.net.Demo.csproj file to net8.0;net472.

Blocked by: https://github.com/ggerganov/whisper.cpp/pull/1519

Concerningly, no mention of #128

Concerningly, no mention of #128

Will be addressed in this release as well (at least for Whisper.net.Runtime.Cublas)

source: gharchive/pull-request

authors: Alumniminium sandrohanea

license: MIT

license_type: permissive

license_source: github-api


text:
PopUp div disappears after triggering 4-5 times.

Hi,
I have the problem that, the pop will be empty after 4-5 times triggering  from 4 different trigger for same div with selector method.
hera is my code looks like.

trigger 1
trigger 2
trigger 3
trigger 4

Lorem Ipsum is simply dummy text of the printing and typesetting industry.

First 2-3 times the popup shows 'lorem ipsum..' text but after that only one  triggers popup with text  but, others trigger the empty popup.
Thanks,
Bishwaksen.

I'm experiencing this same issue. I can reproduce it after a single click off of the popover onto another area (one which does not result in showing the popover), then click to open the same popover again. It shows up blank the second time for that popover and also blank for all other popovers in my list as indicated by Bishwasksen.

Although I'm certain that I tried this before, it could have been a combination of different things, but setting cache:false nearly fixes it. However, in IE, clicking on a target to open the popover, then clicking it again to close it (or clicking elsewhere to launch no popover), then clicking the same target to re-open, still seems to result in the div being blank. However, cache: false improved the issue significantly.

This bug is fixed , you can download the code from github, I'll make the release package when I've finish to fix the other bugs.

Thanks Sandy :)
On Jan 7, 2016 10:46 PM, "Sandy Duan" notifications@github.com wrote:

This bug is fixed , you can download the code from github, I'll make the
release package when I've finish to fix the other bugs.
—
Reply to this email directly or view it on GitHub
https://github.com/sandywalker/webui-popover/issues/131#issuecomment-169884977
.

source: gharchive/issue

authors: sandywalker smartsites-dev-n01 tlangreh

repo: sandywalker/webui-popover

license: mit

license_source: bigquery


text:
BUG - fix to walking and direction select dropdowns in UAT action for tag layout templates

Bugfix

I have one more check to do for this PR. In Limber tagging screen, there are two drop-down boxes, one for walking algorithm and one for direction. I will see if the controller changes have any side effect on them.

Thanks for testing with integration suite for the tagging screen.

authors: andrewsparkes yoldas

repo: sanger/sequencescape


text:
Update sbt-scoverage to 1.6.1

Updates org.scoverage:sbt-scoverage from 1.6.0 to 1.6.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-patch

Coverage remained the same at 89.873% when pulling ef3d5ab54eb84b1858bc8b570a851c05f0230691 on scala-steward:update/sbt-scoverage-1.6.1 into 7dfb251385c96f57496bd29edbfef8bf7b8ad22c on sangria-graphql:master.

issue with scala 2.13.0

Updated with https://github.com/sangria-graphql/sangria-ion/commit/7c49ece740c37f952b139debcbe41715f02711c2

authors: coveralls scala-steward sh0hei yanns

repo: sangria-graphql/sangria-ion


text:
Update scalafmt-core to 3.7.12

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.5.9 to 3.7.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #186.

repo: sangria-graphql/sangria-jackson


text:
Update scala-library to 2.12.13

Updates org.scala-lang:scala-library from 2.12.12 to 2.12.13.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.12.12).
You might want to review and update them manually.
.travis.yml

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, semver-patch, old-version-remains

Duplicated with https://github.com/sangria-graphql/sangria-json4s-jackson/pull/37


text:
Error: no query with @sanity/client v6.15.20 in React Native

I'm experiencing an issue with the latest versions of @sanity/client (v6.15.20) when used in a React Native project.
To Reproduce
Update @sanity/client to the latest version (v6.15.20) in your React Native project.
Expected behavior
The app should display a list of posts fetched from Sanity using the provided query.
Actual Behavior
When using v6.15.20, I encounter a "no query" error. However, the same code functions correctly when I downgrade to v6.4.5.
Screenshots

Which versions of Sanity are you using?
v6.15.20
What operating system are you using?
Windows
Which versions of Node.js / npm are you running?
v21.0.0

Which version of React Native are you using?

React Native: 0.74.0

authors: rexxars shukerullah

repo: sanity-io/client


text:
Use action with a monorepo with sanity in sub directory?

Hi,
I have this project structure:
frontend/
studio/

How can I run the workflow from this sub directory?

I believe you can set working-directory where you specify the job. So:
name: Deploy Sanity
on:
  push:
    branches: [main]
jobs:
  sanity-deploy:
    defaults:
      run:
        working-directory: studio
    runs-on: ubuntu-18.04
    name: Deploy Sanity
    steps:
      - uses: actions/checkout@v2
      - uses: sanity-io/github-action-sanity@v0.1-alpha
        env:
          SANITY_AUTH_TOKEN: ${{ secrets.SANITY_AUTH_TOKEN }}
        with:
          args: deploy

Haven't tested it myself, but you can go here to read more. Let us know if it works!

I believe you can set working-directory where you specify the job. So:
name: Deploy Sanity
on:
  push:
    branches: [main]
jobs:
  sanity-deploy:
    defaults:
      run:
        working-directory: studio
    runs-on: ubuntu-18.04
    name: Deploy Sanity
    steps:
      - uses: actions/checkout@v2
      - uses: sanity-io/github-action-sanity@v0.1-alpha
        env:
          SANITY_AUTH_TOKEN: ${{ secrets.SANITY_AUTH_TOKEN }}
        with:
          args: deploy

Haven't tested it myself, but you can go here to read more. Let us know if it works!

On step closer, but looks like it won't find the sanity.json config file. It is defined in studio/sanity.json. 🤔

On step closer, but looks like it won't find the sanity.json config file. It is defined in studio/sanity.json. 🤔

Same issue here, my Sanity studio is in a subfolder of my project causing the action to fail 😬

Same issue here, my Sanity studio is in a subfolder of my project causing the action to fail 😬

name: Deploy Sanity Studio
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Setup Node.js environment
        uses: actions/setup-node@v2
        with:
          node-version: 12.x
      - name: Install dependencies
        run: |
          cd sanity
          npm install
      - name: Deploy Sanity Studio
        run: |
          set -e
          cd sanity
          SANITY_AUTH_TOKEN="${{ secrets.SANITY_STUDIO_DEPLOY }}" npx sanity deploy

name: Deploy Sanity Studio
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Setup Node.js environment
        uses: actions/setup-node@v2
        with:
          node-version: 12.x
      - name: Install dependencies
        run: |
          cd sanity
          npm install
      - name: Deploy Sanity Studio
        run: |
          set -e
          cd sanity
          SANITY_AUTH_TOKEN="${{ secrets.SANITY_STUDIO_DEPLOY }}" npx sanity deploy

@stianlp I just tried that, but I get command not found: sanity. Any ideas? I tried adding sanity as a dependency.

@eivindml same here. really haven't found a way to get this to work in a subdirectory

The above code doesn't include a step to install @sanity/cli, if it's not already in your package.json. So you can add it like this. I've also added a paths-ignore key so it doesn't redeploy on changes to the website in the sam repo.
Change studio to the name of folder of your Sanity studio in your repo.
name: Deploy Sanity Studio
on:
  push:
    branches: [main]
    paths-ignore:
      - "./web/**"
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Setup Node.js environment
        uses: actions/setup-node@v2
        with:
          node-version: 12.x
      - name: Install dependencies
        run: |
          cd studio
          npm install
          npm install @sanity/cli
      - name: Deploy Sanity Studio
        run: |
          set -e
          cd studio
          SANITY_AUTH_TOKEN="${{ secrets.SANITY_AUTH_TOKEN }}" npx sanity deploy

(I forked Knut's action with the intention of updating it but this was quicker ... maybe next time! :D )

Here is the example for backups when the studio is inside a sub directory (admin).
name: Backup Routine
on:
    workflow_dispatch:
    schedule:
        # Runs at 04:00 UTC on the 1st and 17th of every month
        - cron: '0 4 */16 * *'

jobs:
    backup-dataset:
        runs-on: ubuntu-18.04
        name: Backup dataset
        defaults:
            run:
                working-directory: admin
        steps:
            - uses: actions/checkout@v2
            - name: Install dependencies
              run: yarn install

            - name: Export dataset
              run: |
                  SANITY_AUTH_TOKEN="${{ secrets.SANITY_AUTH_TOKEN }}" \
                  npx sanity dataset export \
                  development backups/backup.tar.gz

            - name: Upload backup.tar.gz
              uses: actions/upload-artifact@v2
              with:
                  name: backup-tarball
                  path: admin/backups/backup.tar.gz
                  # Fails the workflow if no files are found; defaults to 'warn'
                  if-no-files-found: error

There's a tagged pre-release, v0.3-alpha, that tests a new API to permit you to specify a subdirectory for the studio. Details are in the v0.3-alpha README, but the essential change to note (other than tagging @v0.3-alpha) is that args now takes two or more arguments (instead of one or more) and the first is the working directory (. for the top-level of the repo or a named subdirectory such as studio in the case of a monorepo, for example).
This is still an alpha and is not guaranteed to be the direction taken with the API. However, we'd be interested to see if it solves anyone's issues when using this workflow where the studio is in a subdirectory. Please let us know!

FWIW our team has targeted v0.3-alpha and with the new API for args, we're able to deploy Sanity studio from a subdirectory.
Thank you @geoffreyjball!
I will say, the API feels a little clunky and a better API would be to allow for a separate param for directory, in addition to the args param.

Hello Everyone,
The API v0.3 is supposed to work, however I get this weird output.

Here is my YAML configuration of workflow
name: Github Actions
on:
  schedule:
    # Runs at 00:00 UTC on each Sunday
    - cron: "0 0 * * 0"
  workflow_dispatch:
jobs:
  sanity-backup:
    runs-on: ubuntu-latest
    name: Backup dataset
    steps:
      - uses: actions/checkout@v3
      - name: Export dataset
        uses: sanity-io/github-action-sanity@v0.3
        env:
          SANITY_AUTH_TOKEN: ${{ secrets.SANITY_AUTH_TOKEN }}
        with:
          args: studio dataset export production backups/backup.tar.gz
      - name: Upload backup.tar.gz
        uses: actions/upload-artifact@v2
        with:
          name: backup-tarball
          path: backups/backup.tar.gz
          # Fails the workflow if no files are found; defaults to 'warn'
          if-no-files-found: error

Hey,

Hello Everyone,
The API v0.3 is supposed to work, however I get this weird output.

Here is my YAML configuration of workflow
name: Github Actions
on:
  schedule:
    # Runs at 00:00 UTC on each Sunday
    - cron: "0 0 * * 0"
  workflow_dispatch:
jobs:
  sanity-backup:
    runs-on: ubuntu-latest
    name: Backup dataset
    steps:
      - uses: actions/checkout@v3
      - name: Export dataset
        uses: sanity-io/github-action-sanity@v0.3
        env:
          SANITY_AUTH_TOKEN: ${{ secrets.SANITY_AUTH_TOKEN }}
        with:
          args: studio dataset export production backups/backup.tar.gz
      - name: Upload backup.tar.gz
        uses: actions/upload-artifact@v2
        with:
          name: backup-tarball
          path: backups/backup.tar.gz
          # Fails the workflow if no files are found; defaults to 'warn'
          if-no-files-found: error

Hey, i can't make it work to get the backup uploaded. As i can see in your screenshot, your upload process seems also to fail.
Did you manage to get it work?
Thanks

Here is the example for backups when the studio is inside a sub directory (admin).
name: Backup Routine
on:
    workflow_dispatch:
    schedule:
        # Runs at 04:00 UTC on the 1st and 17th of every month
        - cron: '0 4 */16 * *'

jobs:
    backup-dataset:
        runs-on: ubuntu-18.04
        name: Backup dataset
        defaults:
            run:
                working-directory: admin
        steps:
            - uses: actions/checkout@v2
            - name: Install dependencies
              run: yarn install

            - name: Export dataset
              run: |
                  SANITY_AUTH_TOKEN="${{ secrets.SANITY_AUTH_TOKEN }}" \
                  npx sanity dataset export \
                  development backups/backup.tar.gz

            - name: Upload backup.tar.gz
              uses: actions/upload-artifact@v2
              with:
                  name: backup-tarball
                  path: admin/backups/backup.tar.gz
                  # Fails the workflow if no files are found; defaults to 'warn'
                  if-no-files-found: error

This one help a lot thanks, man! By the way sanity-io/github-action-sanity@v0.4 dont work with sub dirs. Had before same issue as the dude above

Here is the example for backups when the studio is inside a sub directory (admin).
name: Backup Routine
on:
    workflow_dispatch:
    schedule:
        # Runs at 04:00 UTC on the 1st and 17th of every month
        - cron: '0 4 */16 * *'

jobs:
    backup-dataset:
        runs-on: ubuntu-18.04
        name: Backup dataset
        defaults:
            run:
                working-directory: admin
        steps:
            - uses: actions/checkout@v2
            - name: Install dependencies
              run: yarn install

            - name: Export dataset
              run: |
                  SANITY_AUTH_TOKEN="${{ secrets.SANITY_AUTH_TOKEN }}" \
                  npx sanity dataset export \
                  development backups/backup.tar.gz

            - name: Upload backup.tar.gz
              uses: actions/upload-artifact@v2
              with:
                  name: backup-tarball
                  path: admin/backups/backup.tar.gz
                  # Fails the workflow if no files are found; defaults to 'warn'
                  if-no-files-found: error

This one help a lot thanks, man! By the way sanity-io/github-action-sanity@v0.4 dont work with sub dirs. Had before same issue as the dude above

Wohoo Thanks! This finally works! 🎉

Glad you got this working, @ThomasWaghubinger. I agree with what's been said a few times, which is that my fix in v0.3-alpha and later is clunky. If you have suggestions for how to better approach this, I'm all ears.

Glad you got this working, @ThomasWaghubinger. I agree with what's been said a few times, which is that my fix in v0.3-alpha and later is clunky. If you have suggestions for how to better approach this, I'm all ears.

Thanks, hmm.. To be honest, this was the very first time I had anything to do with github actions. But the way @sokolenkov posted here works pretty good so far,  maybe it would make sense to reference this in one somewhere in one of the sanity posts about backup with github actions or so 🤷♂

authors: SimeonGriggs ThomasWaghubinger arenhovsepyan eivindml geball geoffreyjball kmelve lorenzorivosecchi ndimatteo nickdandakis sokolenkov stianlp tylermcrobert

repo: sanity-io/github-action-sanity


text:
Embedded Sanity displays blank page when using --turbo

Describe the bug
I'm using Next.js with an embedded Sanity Studio that is accessible at the /studio route. When I use next dev to do local development the studio functions correctly. However, when I use next dev --turbo I get a blank page with no visible errors in the browser console or terminal output.
To Reproduce

Run npx create-next-app next-sanity-starter and go with the defaults as prompted.
Run cd next-sanity-starter.
Run npx sanity init and setup an empty project that uses /studio for the route.
Run npx next dev.
Go to http://localhost:3000/studioand notice that it loads successfully.
Run npx next dev --turbo
Go to http://localhost:3000/studio and notice that it displays a blank page.

Expected behavior
The studio renders the default landing page.
Screenshots

Which versions of Sanity are you using?
$ sanity versions
@sanity/cli (global)  3.49.0 (latest: 3.52.2)
@sanity/image-url      1.0.2 (up to date)
@sanity/vision        3.52.2 (up to date)
sanity                3.52.2 (up to date)

$ npm list
next-sanity-starter@0.1.0
├── @sanity/image-url@1.0.2
├── @sanity/vision@3.52.2
├── @types/node@20.14.12
├── @types/react-dom@18.3.0
├── @types/react@18.3.3
├── eslint-config-next@14.2.5
├── eslint@8.57.0
├── next-sanity@9.4.2
├── next@14.2.5
├── postcss@8.4.40
├── react-dom@18.3.1
├── react@18.3.1
├── sanity@3.52.2
├── styled-components@6.1.12
├── tailwindcss@3.4.7
└── typescript@5.5.4

What operating system are you using?
macOS Sonoma 14.5
Which versions of Node.js / npm are you running?
$ npm -v && node -v
10.8.2
v20.15.1

Hello, can you attach the trace file content? To generate a trace file - .next/trace.log
You would have to run this command with Turbo flag - next dev --turbo NEXT_TURBOPACK_TRACING=1

Hi, could you try the latest canary? npm i next@canary --save-exact 🙌

Installed next@canary --save-exact and also had to upgrade to React 19 RC. Once I did that I was able to run npm run dev and the Next template website and Sanity Studio worked. However, when I did npx next dev --turbo the Next template website loaded, but the Sanity Studio output a bunch of errors.
⨯ Error: Could not parse module '[project]/node_modules/next/dist/server/route-modules/app-page/vendored/contexts/loadable.js'
    at Object.<anonymous> (/Users/username/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:162:11)
    at [project]/node_modules/next/dist/server/route-modules/app-page/vendored/contexts/loadable.js [app-rsc] (ecmascript) (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:165:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at commonJsRequire (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:146:20)
    at Object.<anonymous> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:198:73)
    at [project]/node_modules/next/dist/shared/lib/dynamic.js [app-rsc] (ecmascript) (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:299:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at commonJsRequire (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:146:20)
    at Object.<anonymous> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:302:18)
    at [project]/node_modules/next/dynamic.js [app-rsc] (ecmascript) (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:304:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at esmImport (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:132:20)
    at /Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:313:135
    at [project]/node_modules/next-sanity/dist/studio.js [app-rsc] (ecmascript) <locals> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:331:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at esmImport (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:132:20)
    at /Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:118:168
    at [project]/app/studio/[[...tool]]/page.tsx [app-rsc] (ecmascript) <locals> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:136:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at esmImport (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:132:20)
    at /Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:143:164
    at [project]/app/studio/[[...tool]]/page.tsx [app-rsc] (ecmascript) <module evaluation> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:146:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at esmImport (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:132:20)
    at /Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:170:176
    at [project]/app/studio/[[...tool]]/page.tsx [app-rsc] (ecmascript) <facade> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:174:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at esmImport (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:132:20)
    at /Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:177:32
    at [project]/app/studio/[[...tool]]/page.tsx [app-rsc] (ecmascript, Next.js server component) <facade> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[root of the server]__91df1f._.js:179:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at esmImport (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:132:20)
    at /Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:3848:199
    at [project]/node_modules/next/dist/esm/build/templates/app-page.js?page=/studio/[[...tool]]/page { COMPONENT_0 => "[project]/app/layout.tsx [app-rsc] (ecmascript, Next.js server component)", COMPONENT_1 => "[project]/node_modules/next/dist/client/components/not-found-error.js [app-rsc] (ecmascript, Next.js server component)", COMPONENT_2 => "[project]/app/studio/[[...tool]]/page.tsx [app-rsc] (ecmascript, Next.js server component) <facade>" } [app-rsc] (ecmascript) <module evaluation> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:3856:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at getOrInstantiateModuleFromParent (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:624:12)
    at esmImport (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:132:20)
    at /Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:4004:796
    at [project]/node_modules/next/dist/esm/build/templates/app-page.js?page=/studio/[[...tool]]/page { COMPONENT_0 => "[project]/app/layout.tsx [app-rsc] (ecmascript, Next.js server component)", COMPONENT_1 => "[project]/node_modules/next/dist/client/components/not-found-error.js [app-rsc] (ecmascript, Next.js server component)", COMPONENT_2 => "[project]/app/studio/[[...tool]]/page.tsx [app-rsc] (ecmascript, Next.js server component) <facade>" } [app-rsc] (ecmascript) <facade> (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/node_modules_798a95._.js:4008:3)
    at instantiateModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:572:23)
    at instantiateRuntimeModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:632:12)
    at Object.getOrInstantiateRuntimeModule (/Users/usernam/Desktop/next-sanity-starter/.next/server/chunks/ssr/[turbopack]_runtime.js:647:12) {
  code: 'MODULE_UNPARSEABLE',
  page: '/studio'
}

I've also attached a screenshot of the error.

Currently getting the same issue with next 15-rc and react 19-rc, when using --turbo flag with next dev command, has it been confirmed to be a compatibility issue with the turbo build system in next? and is there a fix?

Same problem. Any updates? mode details

Confirming the problem still exists.
A temporary "fix" is to remove —turbo as described above, but I guess removing turbo is not the idea of using turbo hmm. Tested with moving the sanity config in another project; tested even by cloning this repo as-is (which throws other errors).

Hi ya'll 👋
Could you give v9.5.3 a go and tell me if it solves it for you?

Good news! Using the instructions in my original report it seems to work properly. It's a blank schema, but the Studio loads. I then tried it on my existing, up-to-date, Sanity/Next setup. The new wrinkle is that in my existing project I'm still getting some errors. A few of sections load in the Studio, but others often have an error like this:
Error: Module [project]/node_modules/sanity/lib/_chunks-es/pane.mjs [app-client] (ecmascript, async loader) was instantiated because it was required from module [project]/node_modules/sanity/lib/_chunks-es/index3.mjs [app-client] (ecmascript), but the module factory is not available. It might have been deleted in an HMR update.

authors: afullsnack dmorda dohooo saurabhje stipsan xavortm

repo: sanity-io/next-sanity


text:
Create hemitha-b.md

Hi GSSoC,
This is the PR I have raised and has been merged.
It's Level 1 PR
Could you review and merge it.
@sanjay-kv @MastanSayyad
https://github.com/bHemitha/Open-source-Practice/new/main/pending PR

No response. If you have any Unmerged PRs -- create a new PR

repo: sanjay-kv/Open-source-Practice


text:
🛑 PORTAINER_URL is down

In 58f64d2, PORTAINER_URL ($PORTAINER_URL) was down:

HTTP code: 502
Response time: 3733 ms

Resolved: PORTAINER_URL is back up in 26a8681.

repo: santomaharaj/upp


text:
Asset integration test cases for ioThink

Test cases for ioThink asset integration
Before executing the test case, set the below parameters in the local.json
"assetConnectors": {
  "ioThink": {
    "user": ioThink username,
    "password": ioThink password,
    "meterID": meterID connection string used to connect to actual asset,
    "url": optional parameter, defaults to "https://api.kheiron-sp.io"
  }
}

Test:

Setup the parameters as metioned above
Verify if the asset connector test cases for ioThink are passing successfully

@OliveGerste Will you review this PR?

@OliveGerste Will you review this PR?

Yes I can do it.

@RohanAntony PR with review assigned to people other than me should be put in Cross review pipeline.
I just moved it there ;-)

authors: LucasBrazi06 OliveGerste RohanAntony

repo: sap-labs-france/ev-server


text:
Changed KUBERNETES_PUBLIC_ADDRESS in 01-infrastructure.md .…

Hi All
In 01-infrastructure.md KUBERNETES_PUBLIC_ADDRESS set to 10.47.40.96
neutron floatingip-create FloatingIP-external-monsoon3
export KUBERNETES_PUBLIC_ADDRESS=10.47.40.96

But in 04-kubectl.md and 05-kubernetes-controller.md KUBERNETES_PUBLIC_ADDRESS set to 10.47.40.33
Configure Kubectl

In this section you will configure the kubectl client to point to the Kubernetes API Server Frontend Load Balancer.

Use the load balancer's floating ip from earlier:

KUBERNETES_PUBLIC_ADDRESS=10.47.40.33

Attach our previously reserved floating-ip:

neutron port-list
+--------------------------------------+----------------------------------------------------------------------------------------+-------------------+------------------------------------------------------------------------------------+
| id                                   | name                                                                                | mac_address       | fixed_ips                                                                          |
+--------------------------------------+----------------------------------------------------------------------------------------+-------------------+------------------------------------------------------------------------------------+
| 08899903-ca6c-42a0-b210-f8a380dfcd80 | loadbalancer-abb068fc-d6ed-4a81-b424-b95a5f775bcc                                      | fa:16:3e:8b:54:99 | {"subnet_id": "83aab941-87f4-4372-9fbc-9f702092e3cf", "ip_address": "10.180.0.7"}  |
...
+--------------------------------------+----------------------------------------------------------------------------------------+-------------------+------------------------------------------------------------------------------------+

neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id                                   | fixed_ip_address | floating_ip_address | port_id                              |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| cacce782-68b6-4944-87c6-3640c94f7159 |                  | 10.47.40.33         |                                      |
| 9a4bff45-d72c-4777-a5b1-abe5e76de613 | 10.180.0.30      | 10.47.41.49         | 848396d3-5e18-4410-9a7f-949295428e3f |
+--------------------------------------+------------------+---------------------+--------------------------------------+

neutron floatingip-associate cacce782-68b6-4944-87c6-3640c94f7159 08899903-ca6c-42a0-b210-f8a380dfcd80

LGTM. @SchwarzM any thoughts?

repo: sapcc/kubernetes-the-hard-way


text:
Hide Unsubscribe button from bell icon flyout

it looks out of place
.ytd-menu-popup-renderer.style-scope:nth-of-type(4){
        display: none;
}

what does it do?

it seems to be affected other pages

This should work
ytd-menu-service-item-renderer[use-icons]:has(tp-yt-paper-item[style-target="host"] > yt-icon.ytd-menu-service-item-renderer > svg > g path[d^="M13.72\,11.93C15.58\,11.59\,17\,9.96\,17\,8c0-2.21-1.79-4-4-4S9\,5.79\,9\,8c0\,1.96\,1.42\,3.59\,3.28\,3.93"]) {
    display: none;
}

Thanks

Nope didnt work

which browser are you currently using?

Firefox

Firefox still doesn't support :has selector yet so you need to enable it by following these steps

authors: rounk-ctrl sapondanaisriwan

repo: sapondanaisriwan/AdashimaaTube


text:
Build Failing

Build is failing because of link https://www.scruminc.com/velocity/ that requires a password.
We should probably remove it or replace it for a definition of velocity.

It's very odd, even the base site now requests a pwd... Seems like something gone wrong, not just a paywall thing... :thinking:

Problem is fixed this morning

authors: gcharest smellems

repo: sara-sabr/ITStrategy


text:
Sass removes first two characters in variable

I have a specific use  case where I have an svg that is encoded and I need to be able to use a color variable without the #. I added a variable in the background-image.
Problem is that sass removes the two first characters and it becomes 468E.
http://codepen.io/stephendesjardins/pen/Krkayw
The checkbox is suppose to be blue but because sass removes the two 00 I need, it doesn't work.
Anyway to tell sass not to do this?
Thank you!
Input :
$checkbox-color : 00468E;
.test {
  output : $checkbox-color ;
}
.checkbox {
      &:before {
        content: "";

        background-size: 70%;

        background-image: url("data:image/svg+xml,%3Csvg%20version%3D%221%2E1%22%20id%3D%22Layer%5F1%22%20xmlns%3D%22http%3A%2F%2Fwww%2Ew3%2Eorg%2F2000%2Fsvg%22%20x%3D%220px%22%20y%3D%220px%22%0D%09%20viewBox%3D%220%200%208%208%22%20enable%2Dbackground%3D%22new%200%200%208%208%22%3E%0D%3Cpath%20fill%3D%22%23"+ $checkbox-color +"%22%20d%3D%22M6%2E4%2C1L5%2E7%2C1%2E7L2%2E9%2C4%2E5L2%2E1%2C3%2E7L1%2E4%2C3L0%2C4%2E4l0%2E7%2C0%2E7l1%2E5%2C1%2E5l0%2E7%2C0%2E7l0%2E7%2D0%2E7l3%2E5%2D3%2E5l0%2E7%2D0%2E7L6%2E4%2C1L6%2E4%2C1z%22%0D%09%2F%3E%0D%3C%2Fsvg%3E%0D");
      }
}

Output :
.test {
  output: 468E;
}

.checkbox:before {
  content: "";
  background-size: 70%;
  background-image: url("data:image/svg+xml,%3Csvg%20version%3D%221%2E1%22%20id%3D%22Layer%5F1%22%20xmlns%3D%22http%3A%2F%2Fwww%2Ew3%2Eorg%2F2000%2Fsvg%22%20x%3D%220px%22%20y%3D%220px%22%0D%09%20viewBox%3D%220%200%208%208%22%20enable%2Dbackground%3D%22new%200%200%208%208%22%3E%0D%3Cpath%20fill%3D%22%23468E%22%20d%3D%22M6%2E4%2C1L5%2E7%2C1%2E7L2%2E9%2C4%2E5L2%2E1%2C3%2E7L1%2E4%2C3L0%2C4%2E4l0%2E7%2C0%2E7l1%2E5%2C1%2E5l0%2E7%2C0%2E7l0%2E7%2D0%2E7l3%2E5%2D3%2E5l0%2E7%2D0%2E7L6%2E4%2C1L6%2E4%2C1z%22%0D%09%2F%3E%0D%3C%2Fsvg%3E%0D");
}

Okay I found a solution :
When declaring this variable do :
$checkbox-color : "00" + 468E;

You should just quote the whole value value
$checkbox-color: "00468E"

authors: nschonni stephenbe

repo: sass/node-sass


text:
Windows gems do not install on JRuby

I will preface this by saying that sassc-ruby works great on JRuby as long as you have build tools available!
Of course this is a problem for all Rubies running on Windows, since most users do not have build tools there. To fix this, you started releasing binary gems in 2.1+.
Unfortunately, the way that RubyGems selects binary gems means that they will not install on JRuby. In order for JRuby to have its own binary gems, we have always set our RUBY_PLATFORM to "java", and you will see those gems out there with a -java suffix. When RubyGems attempts to install sassc on JRuby on Windows, it does not see a -java suffix, so it falls back to the non-platform gem... and we're back where we started trying to build on Windows.
The fix is actually fairly simple: we need either the base gem release or a new -java gem release to include all the binaries for Windows and select the correct one at install or runtime. Since you already have the logic to pre-build the libsass binaries, this is just a packaging/release issue.
We are standing by to help make this happen.
Thank you very much for using FFI for this gem... it makes JRuby support almost automatic.

This is the underlying problem in rails/rails#38492.

the loading problem on Windows is already fixed by https://github.com/sass/sassc-ruby/pull/173 but the change wasn't released yet.
You still need a devkit, we can't ship precompiled binaries for Linux until we have a solution to this ticket https://github.com/sass/sassc-ruby/issues/141
ping @larskanis @glebm ?

@ahorek I don't know about this loading issue. If I'm understanding correctly, this would be a problem if you're able to build the binary on Windows... it won't load because it's trying to use a ".jar" extension?
We are fine without precompiled binaries if the library can be built. Precompiled binaries will never work for JRuby if they're only distributed in the platform-specific gems, since RubyGems will never select those versions on JRuby (or on TruffleRuby, since they now force platform to always be "ruby").

sassc 2.2.1 has prebuilt binaries on Windows, but not for JRuby on Windows.
it was built correctly, but it can't be loaded because it attempts to load the .so extension. The correct extension on Windows is ".dll".
dl_ext = (RbConfig::CONFIG['host_os'] =~ /darwin/ ? 'bundle' : 'so')

the second problem is about different C libraries like MUSL on Alpine Linux. Nokogiri has a similar issue https://github.com/sparklemotion/nokogiri/pull/1990 and I think it applies to JRuby as well.
this is the reason why sassc don't ship prebuild binaries on Linux anymore, see https://github.com/sass/sassc-ruby/pull/145 but this is the only blocker. Other than that it's just about a configuration to also build a java version.

JRuby's version of nokogiri does not use any native libraries, so that issue does not apply to us.
It sounds like the Windows binary gems don't work for CRuby either.

nokogiri has his own java library, but sassc use ffi + c library

Is there a way to target Windows + JRuby only? Won't the -java suffix also match on non-Windows?

Is there a way to make an automatic fall back to a compilation in a single gem (platform "java") or separate those platforms somehow? If so, we can ship at least Windows binaries.

There's no way to target just JRuby + Windows because RubyGems only supports a single platform per gem. We've lobbied for adding more dimensions to this platform selection, but no work has been done toward that end. So yes, the -java gem will be selected on all platforms if that's the direction we go.
The options I see right now are:

Ship a -java gem that also includes prebuilt binaries for Windows. If it's installed on Windows, use the binaries; otherwise build them.
Ship the Windows binaries as part of the platformless gem and do the same thing as above. This avoids the need for separate binary gems for Windows but doesn't scale with many platforms.
Ship a single separate gem that contains binaries for all supported platforms, and have the platformless gem use that to pick a binary or build at install time.

Note also that TruffleRuby now forces its platform to always be "ruby" in terms of gems, so it won't pick up native binaries either. So the binary gems as they stand will only ever be installed when using CRuby.

This issue still exists today, jruby (9.2.13.0) and Rails (6.0.3.4), on Windows 10

I have some things to report which might help (anyway, I am seeking answers as well).
Setup:

CRuby 2.6.6 with DevKit
JRuby 9.2.18.0
SassC 2.4.0
Windows 10
pik is used to switch between Ruby versions

I was able to install sassc-2.4.0 into my JRuby installation by making sure that I enabled the DevKit before doing the installation. I posted this here: https://notepad.onghu.com/2021/ruby-tricks-009-jruby-sassc-installation-error/
However, I have a new problem.
When I start jirb and did require sassc it fails with an error:
       16: from org/jruby/RubyKernel.java:1189:in `catch'
       15: from org/jruby/RubyKernel.java:1189:in `catch'
       14: from org/jruby/RubyKernel.java:1442:in `loop'
       13: from org/jruby/RubyKernel.java:1048:in `eval'
       12: from (irb):1:in `evaluate'
       11: from C:/jruby-9.2.18.0/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:158:in `require'
       10: from org/jruby/RubyKernel.java:974:in `require'
        9: from C:/jruby-9.2.18.0/lib/ruby/gems/shared/gems/sassc-2.4.0/lib/sassc.rb:31:in `<main>'
        8: from org/jruby/RubyKernel.java:1002:in `require_relative'
        7: from org/jruby/RubyKernel.java:974:in `require'
        6: from C:/jruby-9.2.18.0/lib/ruby/gems/shared/gems/sassc-2.4.0/lib/sassc/native.rb:5:in `<main>'
        5: from C:/jruby-9.2.18.0/lib/ruby/gems/shared/gems/sassc-2.4.0/lib/sassc/native.rb:6:in `<module:SassC>'
        4: from C:/jruby-9.2.18.0/lib/ruby/gems/shared/gems/sassc-2.4.0/lib/sassc/native.rb:13:in `<module:Native>'
        3: from C:/jruby-9.2.18.0/lib/ruby/stdlib/ffi/library.rb:84:in `ffi_lib'
        2: from org/jruby/RubyArray.java:2588:in `map'
        1: from C:/jruby-9.2.18.0/lib/ruby/stdlib/ffi/library.rb:114:in `block in ffi_lib'
Could not open library 'C:/jruby-9.2.18.0/lib/ruby/gems/shared/gems/sassc-2.4.0/ext/libsass.dll' : The operation completed successfully.

I checked - the DLL file is actually at the correct place. So, that's not it.
Finally... I found that it works if the DevKit is still on the path. So, when I have this as my path, I have no problems.
PATH=C:\jruby-9.2.18.0\bin;C:\Ruby26-x64\msys64\mingw64\bin;C:\Ruby26-x64\msys64\usr\bin;___other_stuff

Hope this helps. Happy to help you check something if it helps. It feels like we are close :)

@mohits Thanks for the follow-up! Perhaps it is linking to some library (e.g. libc bridge or something) in the devkit that is not always on your path? Glad to hear that it at least can work with devkit installed but it really should be able to use the pre-built dll.

hi @headius - as @ahorek  has identified in https://github.com/sass/sassc-ruby/pull/224 the issue is related to LINWINPTHREAD-1.DLL and related dependencies. Adding just C:\Ruby26-x64\msys64\mingw64\bin to the PATH works around it since the necessary files are on the path then. Once that pull request goes through, I expect that it would eventually work fine.
Good!

@mohits devkit is still necessary for the installation, this wasn't fixed, but after the installation, you'll be able to use sassc without a devkit available.
btw you don't have to adjust paths manually, just run ridk enable it should do the trick.

Hi @ahorek - thanks! I have to adjust paths (a bit) because I use pik which takes the Ruby that you're not using off the path. That sadly means that ridk enable does not work since it uses Ruby itself. But I will clean up the instructions anyway to indicate:

Need devkit for installation
Don't need devkit on path for running it

Thanks for keeping Windows and JRuby support as a priority. I'm trying to maintain notes for problems people face with RubyOnWindows and JRuby and I appreciate you helping to ssolve these problems on Windows & JRuby.

So checking on status here... with #224 the devkit is no longer required at runtime, but is still required to install (naturally).
The other path we need to explore is how to structure the gems so that the prebuilt Windows binaries could be downloaded and installed for JRuby users. RubyGems will not select platform gems since our platform is java but if a java gem were pushed it could work like this:

Includes the win32 prebuilt dlls
Modify the ext build to start with Rake, since rake will be available everywhere but make might not be (without devkit)
On non-Windows, build normally
On Windows, just use the existing dlls. The rake ext build would be a no-op.

That would eliminate the need for JRuby users on Windows to have devkit installed.

Modify the ext build to start with Rake

It may already be this way... I just remember this being an issue with e.g. io-console since even a dummy Makefile would force make to be installed.

authors: ahorek glebm headius linojon mohits

repo: sass/sassc-ruby


text:
Add validation for values specified in viya_deployment_settings.ini file.

In case an invalid value is encountered, exit with a helpful message regarding the invalid.  The ini file comments should also clearly indicate the format of the values that can be specified.

Addressed by release 1.5.0

authors: kevinlinglesas lasiva


text:
feat: (IAC-1020) add support for Azure service bus

Changes:
Support added for  Message broker: Azure service bus to be used by SAS Viya Platform deployment instead of RabbitMQ.
The changes to create Azure service bus were added in viya4-iac-azure: PR #320
Tests:
Verified following on the scenarios listed below, please see internal ticket for details.

Verified cluster creation was successful.
Azure Service bus was created.
SAS Viya Platform consumed the Azure service bus information from state file correctly.
Rabbitmq pods were not created.

Note: SAS Viya Platform services are still not ready. Almost all pods stabilized except for few services. Launcher service is failing with [BROKER_MISSING_USERNAME] causing other services to fail. This is expected until all the services are updated to use the new Azure Service bus instead of Rabbitmq.

Scenario
Task
Deploy method
Cadence

1
Defaults, create_azure_message_broker= true, internal Postgres
ansible
fast:2020

2
create_azure_message_broker= true, external Postgres
ansible
fast:2020

3
create_azure_message_broker= true, message_broker_name= "ritika1", aks_cluster_sku_tier = "Standard", external Postgres
ansible
fast:2020

Same comment as with the other changes. This should have been more generic and cloud agnostic or at least investigated and reasoning why the naming was kept azure specific especially since we'll probably need to handle this on AWS/GCP in the future.

Same reply as with the other repo. After investigation across cloud for message brokers, these are available options:
Azure: Azure Service Bus
AWS: Amazon MQ
GCP: Google Pub/Sub

To keep variables and module names generic I went with name as message broker. Azure service bus provides option to create queues or topics and SAS Viya Platform creates Topics.
I thought it would be confusing to name the variables/modules as message queue when we don't create queues.
I don't mind changing variable/module names, please let me know.


text:
[1.12] Support for Thermal Foundation armor types

Is your feature request related to a problem? Please describe.
I wouldn't say this frustrates me, or is a problem, but its a little strange to play lots of modpacks which include this mod and it has armors like copper, silver, lead, etc, and i can make myself look fancy in it, but not my wolf buddy!
Describe the solution you'd like
Armors of all of the armor types in thermal foundation!
Why is this enhancement desirable?
This feature would be super desirable due to thermal foundation being the backbone of a lot of modpack's metal variety, every modpack i've ever played, including the one i am making uses thermal foundation in some way for their metals, so this would help me, and many, many others make their modpack just that little bit more put-together <3
Describe alternatives you've considered
I can't find any way of adding or found any way of using alternatives since this mod is just so unique, i thought about pack-makers just using contenttweaker but i tried this myself and there is no way to get anything on another mob :c
Mockup Screenshots / Videos / Diagrams
I made these mockup gifs using Contenttweaker, Resource packs, and Crafttweaker. I based these colors and armor types off of the horse armor that comes provided from thermal foundation, because it makes sense to match the armors with what is available for pets!

showcasing of all the 12 armors
in order:
Tin
Invar
Constantan
Lead
Aluminum
Nickel
Copper
Silver
Platinum
Steel
Electrum
Bronze

crafting of wolf armor

all wolf armor icons
Additional context
There is many more armors, but i felt showcasing only the armors that the horse has is much more reasonable and makes sense in regard to which armors to make for the wolf armor and which not to. I was trying to think of proper armor values by referencing them to how you did it with iron, gold, diamond, chainmail, etc, but it seems they are a bit more personalized and i sadly didn't have much more time to think and implement values... anyways, I think this would be an awesome edition and really make packs that bit more well put together, and make the mod more involved rather than just getting diamond and calling it a day! Tysm for reading <3!!

You are super welcome! I had a ton of fun making this and thought you would enjoy the effort too! Also conditional item registration sounds AWESOME! :o

repo: satyrnidae/wolfarmor


text:
Renaming MD files to MDX

🌟 Type of Pull Request (check all that apply):

[ ] New Selenium Tip
[ ] Reporting a Bug
[ ] New Feature
[x] Documentation Changes
[ ] Other (please replace this text with details)

🚀 Description
MD files are now MDX files
#565

@aquaomarine approved, but it's showing a conflict. Can you check it out? :)

Yep!

authors: aquaomarine discombobulateme

repo: saucelabs/elemental-next


text:
cleanup unused methods and endpoints

First part of changes from #1105: cleanup of CloneRepositoryController.kt and support changes in save-cli

Save CLI part is refactored without testing, it will be covered in scope #1061

repo: saveourtool/save-cloud


text:
Added progress bar

The progress bar will show the criticality of the vulnerability. For clarity, we will highlight the vulnerability rating in red if it is above 50%.

Is it only a function to add this progress bar without using in existed code?

Yes, the use will be in the next PR.

Directory is also name progrASS bar. Fix it

This code was removed? By mistake?

Please fix typos, add docs and description. And check if you have removed the logic with 51%

Logic removed here. It will be moved later to another location.

anyway will need to fix build


text:
Cargo commands stop working after "Current document not in workspace" warning

Let me just say I'm new to both Visual Studio Code and rust, so I may have missed something obvious here.
Sometimes when creating a new rust file inside of the src directory I'll get a warning saying that the "Document is not in the workspace" or words to that affect, after this none of the cargo commands will function, I cannot test, build or run the project until I restart VSC.
I get no output or feedback of any kind when I try to run a command.

Same here. The only solution seems to restart VS Code.

authors: bjorg stoatally

repo: saviorisdead/RustyCode


text:
Proper completed/errors messages for PaqInstall and PaqUpdate

Currently,  paq-nvim doesn't show any errors if something wrong happen.
For example, with a wrong repo name (e.g: paq 'neovim/nvim-lspconfg'),  I had three differents behavior when trying other and other (until I figure it.. ^^' ):

seems to be stucks at the previous package
doesn't show anything
print  Username for 'https://github.com': at the top of my current window (and freeze neovim)

It can be a bit confusing.
Also, it could be great to habe a message at the end of installation/update saying something like '15 packages was installed/updated !'
Thank's for this plugin btw, really appreciate it in my new nvim config :]

Currently, paq-nvim doesn't show any errors if something wrong happen.

Yeah, Paq isn't very good in that aspect.

print Username for 'https://github.com': at the top of my current window (and freeze neovim)

This has been a common issue, it's been mentioned before, but it's been hard for me to reproduce.

message at the end of installation/update saying something like '15 packages was installed/updated

Paq does show the package count… Could you try deleting the directory where it's installed and reinstalling it again?

I've added a troubleshooting section to the docs. Just the most basic things for now. I'll see what I can add in the future.
I also updated the prompt messages so that errors are properly highlighted (with hl-Error I assume). Remember you can always re-check the messages with the :messages ex-command.

@savq I noticed that you'll get a github prompt for a username when you try to install a package that doesn't exist.  In my case, I was trying to install mhartington/formatter.  However the repo is actually named mhartington/formatter.nvim.

authors: gammons kiuKisas savq

repo: savq/paq-nvim


text:
PrivDropToUser and PrivDropToGroup are only available on rsyslog 4.1.1 and newer

Added a conditional statement to templates/rsyslog.conf.erb so that the resulting configuration works on RHEL5 hosts, where the rsyslog package is 3.x.

As RHEL 5 is pretty old (same as this PR...) I'll close this issue.

authors: saz sirinek

repo: saz/puppet-rsyslog


text:
Add test for handling of suite-level failures

While upgrading the JUnit Foundation dependency of agent-java-junit, I discovered that we couldn't handle suite-level (@BeforeClass) failures. The notifications generated for such failures are associated with the class, not a specific JUnit test of the class. However, the AtomicTest class had no way to represent the description for a JUnit class.
I modified this class so it can handle non-test elements, although this is definitely not what clients are likely to expect. These "atomic non-tests" have no identity and no particle methods. I could potentially attach the specific configuration method that caused the failure, but this may only lead to confusion.
At the least, I need to add at least one unit test to verify that suite-level configuration method failures are handled properly.

Resolved by #107
Prior to the merge of PR #107, we actually have a unit test that covered the general scenario, but this test lacked verification of the "atomic test" object that was supposed to be included with the failure notification. We now explicitly verify that the notification includes a non-test "atomic test" object.

repo: sbabcoc/JUnit-Foundation


text:
Forward port sbt/sbt#2261

sbt/sbt#2261

Ported in #54

repo: sbt/incrementalcompiler


text:
[1.3.0-RC4] Error when launching sbt on AdoptOpenJDK OpenJ9

steps
sbt version: 1.3.0-RC4
Start sbt using AdoptOpenJDK J9 on Linux
problem
When starting sbt 1.3.0-RC4 on Ubuntu or WSL (Debian) with AdoptOpenJDK J9, a stacktrace is printed almost right away: https://gist.github.com/hugo-vrijswijk/c49fbbdc613a088efb7819a02957c36f
3 files are also written to disk:
https://gist.github.com/hugo-vrijswijk/e284188579cf729ce80389792f79e4d9
And a binary file with the name Snap.20190824.112919.24863.0003.trc I could upload somewhere else if needed.
expectation
Sbt starts normally.
notes
WSL:

Java versions: AdoptOpenJDK J9 8.0.222 or 11.0.4
Used latest sbt-extras script
Distro: Debian 10
Windows version 1903

Ubuntu:

Java version: AdoptOpenJDK J9 11.0.4
Used latest sbt-extras script
Distro: Ubuntu 18.0.4

Works fine when in the following cases:

OpenJDK 11 WSL
AdoptOpenJDK 11 HotSpot on WSL
AdoptOpenJDK OpenJ9 11 on Windows.

Did sbt 1.2.8 work?

Yes. 1.2.8 and 1.3.0-RC3 work

I can confirm I am no longer running into the issue. Thanks a lot!!

@hugo-vrijswijk FYI I reported this upstream - https://github.com/eclipse/openj9/issues/6940

repo: sbt/sbt


text:
Make GAS Code Public & Add Open Source License

Hello @sc1314520! Great thanks to your work on the system.
I just want to inform you that any protection on the client side is not enough. People can always use other tools to bypass the protection. So, the protection should be done on the server side, in this case, the Google Apps Script.
As a community member, I believe that many of us would like to help you improve and secure the system if you can share the source code and choose an open-source license for it.
Thanks again for your work!

That's fine. If you can help me to develop the GAS file for server security, I could give you the permission to edit the GAS. By the way,if you want,just reply this message with your gmail address.


text:
Test post-processing workflows from command line

There needs to be a better way for testing post-processing runs. The user should be able to specify one or more local directories containing results from workflow runs and then trigger (from the command line or a notebook) the execution of the post-processing workflow with those run results as input.

Closed by commit 712f1be51686299be545b2dd9ae9c49d02362cb1

repo: scailfin/flowserv-core


text:
re-add scala-gopher

it is in the 2.11 build. I couldn't find the commit where it got
dropped here, perhaps it happened inadvertently?

tested locally

fyi @rssh

repo: scala/community-builds


text:
Expand macro annotations in REPL

sbt console fails to initialize correctly if the paradise-3.xxx plugin is enabled.
The error message is:
[init] error: error while loading Object, Missing dependency 'object scala in compiler mirror', required by /usr/lib/jvm/java-8-oracle/jre/lib/rt.jar(java/lang/Object.class)
A minimal build.sbt that reproduces the issue:
resolvers += Resolver.url( "scalameta-bintray", url("https://dl.bintray.com/scalameta/maven"))(Resolver.ivyStylePatterns)
addCompilerPlugin("org.scalameta" % "paradise" % "3.0.0-M5" cross CrossVersion.full)
scalaVersion := "2.11.8"
libraryDependencies ++= Seq(
        "org.scalameta" %% "scalameta" % "1.1.0"
)

Thanks for reporting! Here is a minimal template to reproduce the error: https://github.com/olafurpg/scalameta-macro-template/blob/98d4a69f43f6346abf32ee559a485c3feb9f7e32/build.sbt
[master] scalameta-macro-examples: app/console
[info] Starting scala interpreter...
[info]
Welcome to Scala 2.11.8 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_102).
Type in expressions for evaluation. Or try :help.

scala> [init] error: error while loading Object, Missing dependency 'object scala in compiler mirror', required by /Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre/lib/rt.jar(java/lang/Object.class)

[init] error: error while loading Object, Missing dependency 'object scala in compiler mirror', required by /Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre/lib/rt.jar(java/lang/Object.class)
null
The compiler did not initialize.
That entry seems to have slain the compiler.  Shall I replay
your session? I can re-run each line except the last one.
[y/n]
Abandoning crashed session.

Here is a diff to fix the issue: https://github.com/olafurpg/scalameta-macro-template/commit/3f5c1e2bc967cd1cac902b5ff69b0c8bf21ab652
Does that work for you?

Well, it doesn't throw errors, but I wouldn't say that it works. As the paradise plugin is not present, the repl is of no use for playing around. (e.g. in sbt macros/console, @main object X { println(5) } outputs an error message, which I completely understand)

I see what you mean, I haven't used the repl to play around with macro annotations. I just do ~app/run and hack on the original code. The benefit to this workflow is that you can edit both the macro definition and call-site. The repl is complicated the setup for macros because they need separate compilation.

I want to do this only because this works with paradise 2.1.0. If I’m not mistaken, each „line” in the REPL is a separate compilation.
From: Ólafur Páll Geirsson [mailto:notifications@github.com]
Sent: Friday, November 4, 2016 1:49 PM
To: scalameta/paradise paradise@noreply.github.com
Cc: Kralik Barnabas kralikba@inf.elte.hu; Author author@noreply.github.com
Subject: Re: [scalameta/paradise] The plugin kills sbt console (#117)
I see what you mean, I haven't used the repl to play around with macro annotations. I just do ~app/run and hack on the original code. The benefit to this workflow is that you can edit both the macro definition and call-site. The repl is complicated the setup for macros because they need separate compilation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/scalameta/paradise/issues/117#issuecomment-258422257, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABGICYB8PE_atkJtf9INSWEqQwUiJHUEks5q6ym3gaJpZM4KpOZA.

I've updated the issue title, I agree that it would be great to be able to experiment with macro annotations in the REPL.

This is a duplicate of #10. I'll link this very helpful discussion there.

authors: kralikba olafurpg xeno-by

repo: scalameta/paradise


text:
[3.0.x] Scalactic Without Scala-xml

Removed scala-xml dependency from scalactic.

Actually Prettifier is using xml classes, not sure why it builds in 2.12 and travis, will investigate further.

Ok, found the reason, scala-compiler 2.12 depends on scala-xml:
https://mvnrepository.com/artifact/org.scala-lang/scala-compiler/2.12.8
while 2.13 does not:
https://mvnrepository.com/artifact/org.scala-lang/scala-compiler/2.13.0-M5

Closing, as Prettifier still needs xml support.

repo: scalatest/scalatest


text:
added ability to list models

Adds support for listing models, and printing the model to console in a human readable way.
This was requested by an intern working on WildML, and was previously left as NotImplemented
Tested locally, with and without models being present for a given user.

Left comments. Please also add a unit test for the new endpoint.

authors: rkaplan srikanth-scale

repo: scaleapi/nucleus-python-client


text:
Docs/SK-956 | Update docs to include new CLI entrypoints commands

Update the documentation with new CLI entrypoint commands

Great. But are you sure fedn train works this way for the mnist-pytorch example, I wonder about --data-path

Yes, If there is no --data-path, it picks from
if data_path is None:
data_path = os.environ.get("FEDN_DATA_PATH", abs_path + "/data/clients/1/mnist.pt")
which is specified in data.py.

--data-path is specific for mnist examples. FEDn is not keep track of use-cases data, user have to make sure the training (and test) data is loaded in for whatever command is defined in train entrypoint. So, for mnist examples fedn run startup (to download the data, path will default to "/data/clients/1/mnist.pt" for torch for example ) needs to be run before fedn run train

you can add a note for this in the docs "Please observe that many of the fedn examples requires you to first download the training and test data before you run "fedn run train/validate" entrypoints. The downloads are usually handled by the "fedn run startup" command "

authors: Wrede sowmyasris

repo: scaleoutsystems/fedn


text:
fix: missing client validation call

Summary
What's changed?

Validate the client

Why do we need this?

Create more meaningful error messages

How have you tested it?

Tested manually

Checklist

[x] I have reviewed this myself
[ ] There is a unit test covering every change in this PR
[ ] I have updated the relevant documentation

Details

Asking for a rereview because I had to modify a lot of stuff to change the tests :pray:
I'm not exactly sure why my PR was what broke it and why it was complaining about the missing config file as opposed to the client being wrong, but clearly were loading a scaleway_client regardless of if we were deployed or in docker compose, so I refactored to avoid it.

repo: scaleway/serverless-gateway


text:
Permitting non-users to send invitations, but retaining invited_by functionality

Thanks for an outstanding addition to Devise -- this is extremely helpful.  I am struggling to adjust one element of the function and seek your help.
I want to keep the exact same functionality of invitable:  users inviting others to the site, who then register with the invited_by_id recorded.
However, I would also like non-users (not logged in) to be able to send invitations. In this case, user would still require an invitation to register, they would continue with password confirmation and everything the same, except that the invited_by_id would be nil or blank.
It appears to me that I need to put "authenticate_inviter!" in the ApplicationController to overwrite the default code. I have been able to do this -- leaving the method blank -- to allow non-users to send invitations.  But I am unable to determine where the code is to record invited_by_id when there is a current user logged in.
Many thanks for help on this!
-Dave

You could set authenticate_inviter! to current_user, which won't force to be authenticated to invite, but will record invited_by_id if user is logged in.

Thank you so much, Sergio, for the quick and super-helpful reply. That did the trick exactly right.  I just put this in my ApplicationController and all seems to work as hoped:
def authenticate_inviter!
current_user
end
Many thanks!

authors: daidekman scambra


text:
generate not work

typing following command:
rails generate devise_invitable:install

it show me:
Could not find generator 'devise_invitable:install'. Maybe you meant 'devise:install', 'ckeditor:install' or 'rails_admin:install'

I use 1.5.2

sorry, maybe zeus problem, I restart my mac, it works

Yeah. Restarting worked for me too. weird.

I tried with restarting and not worked in my case ruby 2.5.1 rails 5.2.3 dell xps ubuntu 18.04.
What worked is:
bundle exec gem install devise_invitable
then I saw that it installed version:
Successfully installed devise_invitable-2.0.1
Parsing documentation for devise_invitable-2.0.1
Done installing documentation for devise_invitable after 0 seconds
1 gem installed

so I updated Gemfile line to correct version:
gem 'devise_invitable', '~> 2.0.1'
and then run rails generate devise_invitable user successfully!

authors: TangMonk nezirz spchetan11


text:
Update dynamodb to 2.17.139

Updates software.amazon.awssdk:dynamodb from 2.17.125 to 2.17.139.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk", artifactId = "dynamodb" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #1388.

repo: scanamo/scanamo


text:
Audio Narration Suport

Can you please add support to extract/import/manage slides audio narration? PowerPoint has very shallow support in this area, especially on MacOS, and the generated audio is quite large in size, and uneditable in PowerPoint aside from trimming. Both problems are easily addressed in dedicated audio software (e.g., Audacity) but it is not possible to update the edited narrated audio files to a PPTx file. Attaching an audio file is a lengthy workaround that is not easy to do when multiple slides narrations are to be edited at once.
I envision a small Python utility using python-pptx to whole-sale extract all audio files, and then when editing is done, whole-sale import and timing auto adjusted using the utility. For example the workflow extract narrations --> convert to lower bit rate using ffmpeg --> update narrations --> save pptx file could be completely automated.
Can you please consider adding this feature, especially in today's online environment (due to COVID-19) this will make remote/unattended presentations management a lot easier.
Thanks!

Would also be very interested in this.
@scanny any temporary workarounds?

@NathanTech7713 I don't know how this behavior works, so the first order of business would be to do the analysis and work out the mechanisms here, probably starting with description of the actual behavior in PowerPoint. For example, if the audio just starts playing when you enter the slide, I would suspect a relationship to slide transitions. On the other hand, if you needed to click on a shape to start the narration I would look at click-actions (which are already partially implemented).
Once you got to the point where you understood what XML elements and attributes needed to show up where then I might be able to help with workaround code.
I don't have any plans to dig into this anytime soon, so this would be likely be something you would do yourself or in collaboration with another user with the motivation and skills to at hammer out something that works for at least some use-cases.

authors: NathanTech7713 SinanSalman scanny

repo: scanny/python-pptx


text:
Occasional type error

Often while a SpaceShoes app is running, we'll get a function with mismatched type error when attempting to report the Ruby VM state. It's possible this is a ruby.wasm error that will get worked out upstream, or even an emscripten error -- there's one that looks similar.
It's also possible we're doing something wrong that causes this. File operations like fwrite seem to be easy to misuse in a way that can cause it, though the error happens even in Shoes apps that use no additional files. (Huh, maybe I should remove the file loader since we usually don't need it?)
This issue is a place to dump information about this bug as we go along.
For instance, it will often occur after the Shoes app has been running awhile, many heartbeats in. So it doesn't seem to be immediately triggered by something new that just happened a moment ago. There seems to be some built in randomness or delay.

It's possible that we're generating an RbFatalError on the JS side (ref: https://www.npmjs.com/package/@ruby/wasm-wasi). If so, might be possible to catch it and reload. That would lose any data in Ruby mem, of course.

I haven't seen this, including in calc.html, since I got rid of the JS-based DOM modification and replaced with the JS gem. I also made sure an element exists in the DOM before trying to modify it in all cases. So maybe this is fixed.
I'll consider it provisionally fixed for now, and update this issue if I see it again.


text:
feat: mount settings.toml inside container

Hello @scarvalhojr!
As done prior to this commit, every time a configuration change was necessary it required a rebuild of the Docker image.
With this PR, that is now done instead with a volume mount by mounting settings.toml at /app/settings.toml inside the container.
I've also updated the documentation.

Briliant, thank you!

authors: scarvalhojr tatupesonen

repo: scarvalhojr/aocleaderboard


text:
SqlServer2000 migrations fail when creating the version table

All migrations fail to start as currently for sql server 2000 we use the standard sqlserverprocessor which implements schemaexists using the sys.objects view.  As this does not exists in 2000 the migrations fail.
The 2000 generator also does not implement any schema logic, so we need to create a new SqlServer2000Processor and just return true for the test, as happens with other db processors that do not support schemas.

Pull request #193 fixes this and it is merged in now.

authors: abusby daniellee

repo: schambers/fluentmigrator


text:
Use only DSL to generate SQL

Hi,
Is it possible to use only the "SQL DSL" to generate sql scripts with Fluentmigrator? Or are there any other libraries which allow this?

@bertvan If you just want to run scripts, you could use Execute.Script or Execute.EmbeddedScript

Hi, it's been a while, and I can't really remember why I wanted this... But, I know (knew) acout Execute.Script, so that wasn't it.
I think, I wanted to have access to the actual SQL that is generated by FluentMigrator.

@bertvan You could do that by using the --preview and --output switches

OK thanks!

authors: bertvan tommarien


text:
ValueError: update only works with $ operators

TinyMongo allows you to update a document like this:
collection.update_one({"_id": "fh98h43f89fh4fh"}, {"some_field": "some update"})

But on the real MongoDB database (on mLab) I get this error: ValueError: update only works with $ operators.
So I needed to change the code like this:
collection.update_one({"_id": "fh98h43f89fh4fh"}, {"$set": {"some_field": "some update"}})

This also works on TinyMongo and it is a more appropriate way to update a document. TinyMongo should follow the MongoDB/pymongo behaviour and throw the same error in the first case.

i have already using $ operators but its giving error:         servers.update_one({'_id': str(ctx.guild.id)}, {'$set': {'prefix': prefix}}, upsert=True)


text:
Error in /monitors: Timed out while waiting for event Event.MONITOR_LIST

2024-09-03 17:29:18,154 - __main__ - INFO - Starting the backend...
2024-09-03 17:29:18,158 - waitress - INFO - Serving on http://0.0.0.0:5005
2024-09-03 19:59:17,844 - __main__ - INFO - Accessing /status endpoint
2024-09-03 19:59:17,878 - __main__ - INFO - Accessing /monitors endpoint
2024-09-03 19:59:22,675 - __main__ - INFO - Accessing /monitors endpoint
2024-09-03 19:59:23,875 - __main__ - INFO - Accessing /monitors endpoint
2024-09-03 19:59:27,886 - __main__ - ERROR - Error in /monitors: Timed out while waiting for event Event.MONITOR_LIST
2024-09-03 19:59:29,184 - __main__ - INFO - Accessing /status endpoint
2024-09-03 19:59:29,273 - __main__ - INFO - Accessing /monitors endpoint
2024-09-03 19:59:32,677 - __main__ - ERROR - Error in /monitors: Timed out while waiting for event Event.MONITOR_LIST
2024-09-03 19:59:33,713 - __main__ - INFO - Accessing /monitors endpoint
2024-09-03 19:59:33,883 - __main__ - ERROR - Error in /monitors: Timed out while waiting for event Event.MONITOR_LIST
2024-09-03 19:59:39,277 - __main__ - ERROR - Error in /monitors: Timed out while waiting for event Event.MONITOR_LIST
2024-09-03 19:59:43,720 - __main__ - ERROR - Error in /monitors: Timed out while waiting for event Event.MONITOR_LIST

First of all: i do NOT have MFA enabled in uptima-kuma, and not in the compose!
Second: Is not able to connect to endpoint ;)
Updated App in iOS and the compose file

services:
  uptime-buddy-api:
    image: schech1/uptime-buddy-api:latest
    ports:
      - 5005:5005
    environment:
      - UPTIME_KUMA_URL=http://192.168.0.44:3001
      - USERNAME=myuname
      - PASSWORD=mynicepassword
      - TOKEN=yes-mytoken
      - MFA=false

Please try to remove the line with  - MFA=false  completely from docker compose

I fixed it with the latest commit.
-MFA can be now true/false or removed completely


text:
Can we make search papers based on the organization or coutry?

Hi,
I am looking for paper metadata based on the organization and country. Does the current version of the library can do this?
Regards,

There's a way to search for all the scholar profiles in a given organization, but if you're asking about papers, I don't think Google Scholar has such a feature. Can you share a link or a query in Google Scholar that does what you're thinking of?

authors: arunkannawadi bbardakk

repo: scholarly-python-package/scholarly

license: Unlicense


text:
Fix bug using internal javascript files to allow SSL

I noticed that on newer versions of Omeka, this plugin was failing when my site loaded using https because of dynamic loaded of external scripts that are hard coded to use http. I noticed that the plugin supports using local javascript files, which fixes this problem neatly, but that functionality was not working with my Omeka 2.4 installation.
It looks like this is caused by a syntax change in the Omeka config.ini file that happened a few years back: https://github.com/omeka/Omeka/issues/305
I made a quick change that fixes the issue.
I also removed the "http" from one dynamically loaded script so that it could load using the protocol of the parent page if need be, but this alone will not get the timeline to work on a page loaded with SSL.

Well, inexplicably and inexcusably, it's only taken us three years and a few months to actually review and merge this pull request. Thanks for contributing it @NedHenry

authors: NedHenry jeremyboggs

repo: scholarslab/NeatlineTime


text:
ESP32-S3

I invested some time to get this running on an ESP32-S3 and wanted to share the work.
esp32-s3.patch
I didn't test every aspect, but I can send data back and forth.

OK, thanks.
So one of the reasons I'm accessing the register for stretch_cause directly is that IDF says (incorrectly) that the S2 does not support clock stretching, and that function is a no-op.
But I think the correct change in that case is to call the function i2c_ll_slave_get_stretch_cause if it's not the S2.
Probably the hal should be fixed for S2 anyway, regardless of the status of the driver.
The other additions: i2c_ll_slave_tx_auto_start_en and i2c_ll_update I'm unfamiliar with. Looks like they are no-ops in the S2 hal as well.
I must admit, I mostly just copy-pasted what the low level code was doing for the initialize function. It's unfortunate the initialization is very tied to the existing driver.
I'll see if I can add this with a #ifdef for S2 for getting the clock stretch cause.

authors: bernd-herzog schveiguy


text:
Add notes from first discussion

This needs editing and review before merging.  I also need to link to the video once it is made public.

@rgommers Should we merge this now?  And then you can update it in a subsequent PR?
@juanis2112 uploaded the cleaned up video and I updated (in f01f139) the link to the video in the meeting notes.

I don't like that I turn the camera down at the end of the video.  Any thoughts about how to remove that part?  Would fading to an final slide with a link to the website to cover up my mistake be reasonable?
https://api-dispatch.scientific-python.org/discussion/2021-12-15.html
or
https://api-dispatch.scientific-python.org/
The first link won't exist until this PR is merged.

I fixed the affiliations, I'm fairly sure they're correct now.

I don't like that I turn the camera down at the end of the video. Any thoughts about how to remove that part?

Maybe that's already fixed? I don't see it in the video. Overall the video looks really good to me!

@rgommers Should we merge this now? And then you can update it in a subsequent PR?

Makes sense to me. You did say right at the end of the video that you were going to send around a link to the recording so people could check. I just watched most of the recording, and I don't think anyone said anything they'd have second thoughts about, but I just thought I'd point that out.

I emailed the participants and told them we would wait until Wednesday (1/12) before merging this.

authors: jarrodmillman rgommers

repo: scientific-python/api-dispatch


text:
New blank line everytime a folder is entered

A new blank line gets inserted at the top of the panel every time a folder is entered. After entering a few folder, user always needs to scroll down to see the entire panel.

@JeanBilheux could you verify this fix works for you? You will need to install ipywe from source. Please see Dev.md

Works great. Thanks.

authors: JeanBilheux yxqd

repo: scikit-beam/ipywe


text:
tests/HZZ*.root typo in Photon_E branch descriptor

running root-dump on the tests/HZZ.root files I get:
$> root-dump HZZ.root
>>> file[HZZ.root]
key[000]: events;1 "" (TTree)
root-dump: error dumping file "HZZ.root": rootio: Tree "events" has no branch named "Photons_E"

and indeed:
root-ls -t HZZ.root
=== [HZZ.root] ===
version: 53201
TTree                         events                                  (entries=2421)
  NJet                        "NJet/I"                        TBranch
[...]
  NPhoton                     "NPhoton/I"                     TBranch
  Photon_Px                   "Photon_Px[NPhoton]/F"          TBranch
  Photon_Py                   "Photon_Py[NPhoton]/F"          TBranch
  Photon_Pz                   "Photon_Pz[NPhoton]/F"          TBranch
  Photon_E                    "Photons_E[NPhoton]/F"          TBranch
  Photon_Iso                  "Photon_Iso[NPhoton]/F"         TBranch
[...]

there is a typo in the branch descriptor for Photon_E (which reads Photons_E, with an extra s).
not sure who's "right" here (uproot that presumably correctly reads that file, or groot that chokes on it)

This was probably a typo when creating the file, but it's not an invalid file. The branch's name is "Photon_E" and its title is "Photons_E[NPhoton]/F". There's nothing illegal about that.
Inside of the branch, there's a name and title for each basket (only 1 in this case), and I suppose it could break something if the basket's name is different from the branch name. The basket name in this case is "Photon_E", in agreement with the branch name.
The branch has one leaf, and its name is different from the branch name: "Photons_E" with title "Photons_E[NPhoton]". If some process requires the singleton leaf name to equal the branch name, I suppose that would be a problem. But a branch can in principle have many leaves, all with different names, so I don't know why a tool would require the leaf name to be equal to the branch name.
I'll close this then.

authors: jpivarski sbinet

repo: scikit-hep/uproot


text:
ModuleNotFoundError: No module named 'skmultilearn.model_selection'

At the risk of being told this is a Stackoverflow issue:
Trying to run: iterative_train_test_split example from the http://scikit.ml/stratification.html page.
Did a pip install:
scikit-multilearn in /anaconda3/lib/python3.6/site-packages (0.0.5)
would this be the wrong version?

Hi Maarten!
As you said it's for the version. Currently the library is in the 0.2.0 version
Try to do a pip install --upgrade to the package ^^

The stratification was introduced in version v0.1.0. Can you validate that it works after updating the package?

Jose, Christian,
Confirming it works fine after running the upgrade, thanks for the quick reply.
BTW a collegue of mine ran the pip install and he also installed the old version; some wrong pointer in a script somewhere?
Merry Christmas!
Maarten

On 18 Dec 2018, at 12:22, Jose Perez-Parras Toledano notifications@github.com wrote:
pip install --upgrade

Maybe it was already installed. In this case pip doesn't install the already installed package:
λ pip install scikit-multilearn
Requirement already satisfied: scikit-multilearn in /opt/miniconda3/lib/python3.7/site-packages (0.1.0)

λ pip install scikit-multilearn --upgrade
Collecting scikit-multilearn
  Downloading https://files.pythonhosted.org/packages/bb/1f/e6ff649c72a1cdf2c7a1d31eb21705110ce1c5d3e7e26b2cc300e1637272/scikit_multilearn-0.2.0-py3-none-any.whl (89kB)
    100% |████████████████████████████████| 92kB 515kB/s
Installing collected packages: scikit-multilearn
  Found existing installation: scikit-multilearn 0.1.0
    Uninstalling scikit-multilearn-0.1.0:
      Successfully uninstalled scikit-multilearn-0.1.0
Successfully installed scikit-multilearn-0.2.0

same issue with last version
Requirement already up-to-date: scikit-multilearn in /usr/local/lib/python3.7/site-packages (0.2.0)

ModuleNotFoundError: No module named 'skmultilearn.problem_transformation'

@Camus12  Solved long time ago. Can’t remember the solution. Seems dependency version problems. You can search and try more.

@shm007g can u remember the solution. I am having the same issue. @Camus12 did you find the solution?

@shm007g i solved the issue. Everyone, solution is here https://stackoverflow.com/a/70233495/17108206

@MFaheem407 your given solution is not working for me

repo: scikit-multilearn/scikit-multilearn


text:
include models in result passed to callback(s)

I am continuously saving the current_result in gp_minimize() using a wrapper around dump() as a callback after every iteration like this:
def dump_cb(res):
    res2 = copy.deepcopy(res)
    del res2.specs['args']['func']
    del res2.specs['args']['callback']
    dump(res2, 'result.pkl', store_objective=True)

(I copied the deepcopy from https://github.com/scikit-optimize/scikit-optimize/blob/master/skopt/utils.py#L88 and added deletion of the callback as it was not serializable - it might make a useful additon to the callbacks.py module, let me know if you want me to implement it)
I then want to be able to inspect the ongoing training progress using the visualization plots. this worked fine except for plot_objective() which crashed because the result was missing the models in the following line: https://github.com/scikit-optimize/scikit-optimize/blob/master/skopt/plots.py#L307
this pull request includes the models in the result passed to the callback making them available to plot_objective() through the dump.

Current coverage is 85.45% (diff: 100%)

Merging #280 into master will not change coverage

@@             master       #280   diff @@
==========================================
  Files            25         25
  Lines          1375       1375
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1175       1175
  Misses          200        200
  Partials          0          0

Powered by Codecov. Last update 6250360...902d1f3

Good catch! Thanks for your contribution :)

authors: codecov-io glouppe lefant

repo: scikit-optimize/scikit-optimize


text:
Add pipeline copy method

This makes it possible to make a copy of an existing pipeline.
One can then, for example modify the parameters of the new pipeline.

Looking at Pipeline:
        self._providers: Dict[Key, Provider] = {}
        self._subproviders: Dict[type, Dict[Tuple[Key | TypeVar, ...], Provider]] = {}
        self._param_tables: Dict[Key, ParamTable] = {}
        self._param_name_to_table_key: Dict[Key, Key] = {}

Why can't we just copy these four dicts, and copy the testing dicts in _subproviders?

and copy the nested dicts in _subproviders

Can you have more than one level of nesting?

and copy the nested dicts in _subproviders

Can you have more than one level of nesting?

No.

authors: SimonHeybrock nvaytet

repo: scipp/sciline


text:
ENH: allow matching of general bipartite graphs

This provides a Cython implementation of the Hopcroft--Karp algorithm for solving the maximum matching problem for bipartite graphs.
Context and motivation
SciPy currently implements a solver for maximum bipartite matching in scipy.sparse.csgraph.maximum_bipartite_matching. However, the main interest in this one appears to have been in reordering rows/columns of sparse matrices, and the function makes the assumptions that the partitions in the input graph have equal cardinality and that a perfect matching exists; as such, not much maximization is actually going on and all the algorithm does is find a feasible solution. Now, there's nothing wrong with that, but it's likely not what you might expect coming to a method called maximum_bipartite_matching from a graph theory context.
This PR ties in with the discussion towards the end of #10296 in which the topic was including a version of scipy.optimize.linear_sum_assignment that takes advantage of sparsity; although this is a separate problem, before moving to that it seemed to make more sense to deal with the more fundamental problem of finding a maximum matching. It also follows the spirit of #10566 and provides an implementation of a well-known algorithm that's easy to understand and thus hopefully maintain, with an eye towards performance so that we improve on the existing implementation for the cases where they overlap, and with large improvements over pure Python implementations such as the one in NetworkX.
The algorithm revolves around the notion of augmenting paths, which matches the approaches in scipy.optimize.linear_sum_assignment and the proposed scipy.sparse.csgraph.maximum_flow; this isn't a huge benefit in and of itself, but it does mean that being able to read one makes it easier to read the others. As such, a reviewer with a surplus of time going through this might also want to take a look at #10566.
In the process, we also fix an issue with the old documentation: Here, the main concern was permuting the rows/columns of a matrix to make its diagonal zero-free, but in case the input matrix contained explicit zeros in its sparse representation, the diagonal would in fact as well; we fix this by turning the bug into a feature and explicitly interpreting explicit zeros as edges in the bipartite graph. We keep the original motivation as an example in the xmldoc of the revised function.
Correctness
In addition to the included unit tests, we've run checks against the corresponding function in NetworkX, checking that the cardinalities of a maximum matching agree for random inputs, e.g.:
from random import randint, random
for _ in range(100):
    n = randint(100, 1000)
    m = randint(100, 1000)
    density = random()
    graph = scipy.sparse.rand(n, m, density=density, format='csr')
    G = nx.algorithms.bipartite.from_biadjacency_matrix(graph)
    assert 2 * np.sum(maximum_bipartite_matching(graph, perm_type='column') >= 0) ==\
        len(nx.algorithms.bipartite.maximum_matching(G, top_nodes=range(n)))

This clearly does not prove correctness in any way, but it does at least provide some confidence that it's working.
Performance
Using the same random matrices as above we can provide a rough benchmark of our approach against the existing implementation and the one available in NetworkX. How well it performs will depend on characteristics of the input, but we do at least seem to be gaining a good amount of performance in addition to solving a much more general problem:
n = 5000
density = .1
graph = scipy.sparse.rand(n, n, density=density, format='csr', random_state=42)
G = nx.algorithms.bipartite.from_biadjacency_matrix(graph)

>>> %timeit maximum_bipartite_matching(graph, perm_type='column')
8.95 ms ± 183 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)
>>> %timeit old_maximum_bipartite_matching(graph, perm_type='column')
141 ms ± 8.52 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
>>> %timeit nx.algorithms.bipartite.maximum_matching(G, top_nodes=range(n))
2.01 s ± 118 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

Marking this as WIP just to get a chance to look at the CI output, including the documentation this builds.

This looks good, let's try to get it in for 1.4.0.
There's a small merge conflict, could you rebase @fuglede?

Thanks @rgommers, merged and rebased.
Here's a possible release note entry:

scipy.sparse.csgraph.maximum_bipartite_matching now allows non-square inputs, no longer requires a perfect matching to exist, and has improved performance.

CI failure is unrelated:
=================================== FAILURES ===================================

 build/testenv/lib/python3.6/site-packages/scipy/optimize/tests/test__differential_evolution.py

[gw1] linux -- Python 3.6.7 /home/travis/virtualenv/python3.6.7/bin/python

worker 'gw1' crashed while running 'build/testenv/lib/python3.6/site-packages/scipy/optimize/tests/test__differential_evolution.py::TestDifferentialEvolutionSolver::test_immediate_updating'

Thank you once again @rgommers for the review. I went through your comments, so modulo CI, it's back to you.

Merged! Thanks again @fuglede. Also for the excellent description and commit messages, very helpful for reviewing.

authors: fuglede rgommers

repo: scipy/scipy


text:
ENH, MAINT: Implementation of MINRES (Trac #12861, #885 )

Reference issue
CLOSES  #12861
What does this implement/fix?
This implement changes addes the new implementation of MINRES explained in  https://web.stanford.edu/group/SOL/software/minres/.
Additional information
Fix requested by @ceboy

Hi @tylerjereddy,
I ran the test on my computer with
`>>> import scipy

scipy.test()`

As mentionned in the documentation, I got no errors on minres (the only thing that we need to do is to add some unit tests for to test the new parameters) but the checks are not successful.
I am new to open source contribution, I might have forgot something could you guide me please.

Hi @tylerjereddy, could you help me review the code please ?

Hi @ilayn could you review the changes please ?
I don't know why it is not fully checked now, specially the scipy.scipy because it was working, but for the continuous integration I had to add some   after some , and now it is failing.

I am still trying to understand what we want to achieve here. We modified some lines but then how is this going to renew the actual minres? Are you planning to update the lib files too?

The actual 'Minres' was not taking consideration of the preconditionner which according to the paper is something that we should take in consideration since we could have different ways of implementing the algorithms depending on the parameters we have and the solution we want to achieve.

@ilayn  Could you tell me please which lib files to update plus how to do it ?

authors: ilayn yacth


text:
DOC: reorganize scipy.stats overview docs page

I got triggered by the stats.qmc merge and the very outdated sentence on rpy at the end of the page. This should help get a much better sense of what's in scipy.stats and where else to look for areas of statistics.

CI failure on 32-bit Linux is unrelated.

CI failure on 32-bit Linux is unrelated.

This should be safe to merge, all the failing CI is unrelated.

OK, because of the force push I can't see what changed, but I have checked that the comments were addressed.
I agree from the diff that it looks safe, so in it goes.

authors: mdhaber rgommers