Package request: daisyui

Project description
daisyui is a component library for tailwindcss

Metadata

homepage URL: https://daisyui.com/
source URL: https://github.com/saadeghi/daisyui
license: mit
platforms: unix, linux, darwin, ...

Where this package can be used? As a tailwind plugin, viz.:
pkgs.nodePackages.tailwindcss.overrideAttrs
  (oa: {
    plugins = [
      pkgs.nodePackages."@tailwindcss/aspect-ratio"
      pkgs.nodePackages."@tailwindcss/forms"
      pkgs.nodePackages."@tailwindcss/language-server"
      pkgs.nodePackages."@tailwindcss/line-clamp"
      pkgs.nodePackages."@tailwindcss/typography"
    ];
  })

Upstream repo has no package-lock.json (https://github.com/saadeghi/daisyui/discussions/2217) so I suppose we would have to maintain one, and use that in postPatch. Are there other ways?

@srid - did you ever find a way to use daisyui w/ tailwindcss?

I resorted to generating a lockfile with
npm i --package-lock-only

and creating a daisyui package inside my project flake.nix using a random nixpkgs package as basis, overriding tailwindcss like above.
Something like this:
packages.tailwindCss = pkgs.nodePackages.tailwindcss.overrideAttrs (oa: {
          plugins = [
            pkgs.nodePackages."@tailwindcss/aspect-ratio"
            pkgs.nodePackages."@tailwindcss/forms"
            pkgs.nodePackages."@tailwindcss/language-server"
            pkgs.nodePackages."@tailwindcss/line-clamp"
            pkgs.nodePackages."@tailwindcss/typography"
            self'.packages.daisyui
          ];
        });

 packages.daisyui = pkgs.buildNpmPackage rec {
          pname = "daisyui";
          version = "4.6.3";

          src = pkgs.fetchFromGitHub {
            owner = "saadeghi";
            repo = pname;
            rev = "v${version}";
            hash = "sha256-O1YZF2mMNWnoj6sRrbQKJBTqlQ+NIcpZf0kawDDeVxM=";
          };

          npmDepsHash = "sha256-hbcgdk4Q9pf/Pif/zVyxEtYUspKhYkd8OUi73LG88nw=";

          # use generated package-lock.json as upstream does not provide one
          postPatch = ''
            cp ${./daisyui-package-lock.json} ./package-lock.json
          '';

          # The prepack script runs the build script, which we'd rather do in the build phase.
          npmPackFlags = ["--ignore-scripts"];

          NODE_OPTIONS = "--openssl-legacy-provider";

          meta = with lib; {
            description = "A free and open-source Tailwind CSS component library ";
            homepage = "https://daisyui.com/";
            license = licenses.mit;
          };
        };

And using self'.packages.tailwindCss as a nativeBuildInputs for mkShell

I followed these steps, without any problems:
https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/javascript.section.md#adding-and-updating-javascript-packages-in-nixpkgs-javascript-adding-or-updating-packages
I can try opening a PR.

@larstvei Try my pull request
As explained in the pull request, don't know the feasibility of this package in the nixpkgs repo, maybe we should put all npm or web development packages in another repo.
For example, I'm maintaining private packages of prettier-plugin-jinja-template and prettier-plugin-tailwindcss, with a patched prettier package to add the node_modules to it similar to the nixpkgs tailwindcss definition.
Nevertheless, I can't make VSCode tailwindcss-intellisense work as it needs a project node_modules, and I'm not too inclined to hack a nix derivation to add all those packages node_modules right now.
This web world have a serious dependency management problem...

Nice, that worked well for as well. I didn't know using nodePackages was discouraged when I added the PR 😅

Just linking this discussion, since it looks relevant: https://github.com/tailwindlabs/tailwindcss/discussions/12294#discussioncomment-8268378


Create greetings.yaml

Added for #228

Hi Mate, you are missing lots of places, please slow down and give attention to detail

PR description and commit guidelines is not being followed

Chat gpt /bard gives me this ... You have greeting template going not sure how this is greeting, it is mostly a warning message, I don't want to greet anyone tbh.
3. Please test it before doing a PR.
@Mayur-666 please take care of this use case, it will be challenging but high need https://github.com/krishnaacharyaa/wanderlust/issues/230, test it in your other project and then raise the PR. Because this is the need, I'll revise the acceptance criteria soon for this issue....

@krishnaacharyaa I have this one in mind
name: 'Greetings'
on:
fork:
push:
branches: [main]
issues:
types: [opened]
pull_request_target:
types: [opened]
jobs:
welcome:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: Welcome Issue
if: github.event_name == 'issues'
uses: EddieHubCommunity/gh-action-community/src/welcome@main
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
issue-message: |
Congratulations, @${{ github.actor }}! 🎉
Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work!
We will promptly review your issue and offer feedback.
Kindly remember to check our [contributing guidelines(https://github.com/krishnaacharyaa/wanderlust/blob/main/.github/CONTRIBUTING.md)
- name: Welcome Pull Request
if: github.event_name == 'pull_request_target'
uses: EddieHubCommunity/gh-action-community/src/welcome@main
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
pr-message: |
Great job, @${{ github.actor }}! 🎉
Thank you for submitting your pull request. Your contribution is valuable and we appreciate your efforts to improve our project.
We will promptly review your changes and offer feedback.
Kindly remember to check our contributing guidelines

@krishnaacharyaa  It will be something like this / or we can do some changes in message

@krishnaacharyaa It will be something like this / or we can do some changes in message

LGTM, we'll change the message, not getting if it is the issue wala or the PR wala... ig you wantedly just tried both the things
Lets focus on the PR raised github action first... and if @sanmarg doesn't reply quick enough post #230 issue you can take others in the sequence as well.
In #230 there are many other factors, written neatly in the acceptance criteria, can you kindly look into that.
You can raise 1 by 1 I'm fine with that...
I just need those acceptance criteria to be fullfilled... Shall we now work on that then?

@Mayur-666

Yes sure @krishnaacharyaa

ig you have picked it from here https://github.com/Sanchitbajaj02/palettegram/issues/306
Thats good, we need to check what are others upto,
He has used some bots in the PR as well, can you look into that? And see if even we can leverage that kinda thing.
Very similar to what we are looking for
@Mayur-666

well i have taken it from swapnil, he's my friend and we made that at time of social summer of code.

@Mayur-666 Then I guess this guy has taken from swapalin aswell 😂😂
Well it's never a problem for me ...
I'm happy to know you are part of the root thing or closely related ...
I thoo copy from everywhere possibly and do it ☺. That's how we all learn

@sanmarg i saw you like docker in your blog. this project uses Docker for cicd but it only does one kind of build using clang-12. it needs to also install react or vite dependencies in the docker image and then devs can run the react or vite frontend webserver using docker with a tcp port hole punch in say port 3000 or maybe --net=host
i just wanted to mention the need to you in case you are interested. there is also a need for an emscripten build (in addition to the clang-12 build we already check in cicd) to go into the react/vite frontend. ideally devs can then run docker container locally to see the changes they are making work etc


[EAGLE-783] Add unit test for eagle-jpm-util.

Add unit test for eagle-jpm-util.

https://issues.apache.org/jira/browse/EAGLE-783

Test comment. Should go to issues@ list

Reviewed, LGTM, will merge later.


Implement desktop notifications

It would be nice to have desktop notifications for private messages.
Ex using https://github.com/gen2brain/beeep
#wishlist

I have investigated the use of sound/beep. But there are not good libraries for using sound devices for cross platform (that are not too large projects). Using system \a or \007 seems to be working just in some terminals (configuration dependent I guess).
But using some notification system would be better I guess. I will look into this!

Fixed in 055e2c77c845784a79d6457c914ea89e0be2fc11


API limit exceeded

Source information
MangaHub 1.4.38
Source language
English
Steps to reproduce
When I open a manga to read it it shows a message like "API limit exceeded"
Expected behavior
I should be able to read the manga
Actual behavior
It's showing API limit exceeded and closes the manga
Mihon/Tachiyomi version
0.17.1
Android version
Android 11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

See closed #703

I tried clearing cookies but nothing happened

See closed #703, otherwise, it's just like that, wait it out/read less

I am waiting since days

The error message is a red herring. The extension is not doing the same dance as the site, which it could be changed to do. Last time I looked at it the limit was 10 chapters every x minutes (x being somewhere between 20 and 60 minutes). There is an implementation of the logic here: https://github.com/manga-download/hakuneko/blob/2e57d194582807e16c07646e3799044532d4bffa/src/web/mjs/connectors/MangaHub.mjs#L185

The error message is a red herring. The extension is not doing the same dance as the site, which it could be changed to do. Last time I looked at it the limit was 10 chapters every x minutes (x being somewhere between 20 and 60 minutes). There is an implementation of the logic here: https://github.com/manga-download/hakuneko/blob/2e57d194582807e16c07646e3799044532d4bffa/src/web/mjs/connectors/MangaHub.mjs#L185

Is there any solution for it? I didn't read any chapters since months


Collapsable agenda, one panel for each motion comment and hide closed…

… agenda items in the item slide.

One minor remark after testing:
A long title of an agenda item needs more indentation in second line, see screenshot:

Also a bit more margin-left need the hover menu which is not exactly below the agenda item title.

Rest looks good.

wait for #3565 to be merged and resolve todo...

@emanuelschuetze Please check new commit. This should resolve the style issue.

@emanuelschuetze Ready for merge

@FinnStutzenstein Please add Changelog entry. Thx.


Changing file extension does not update currently opened files' tabs

When a file is renamed with a different extension the file explorer updates properly, but any open files' tabs do not update the icon unless reopened

:+1:

This seems to be an issue with the tabs package, related to https://github.com/atom/tabs/issues/189. In short: the data-name attribute isn't updated correctly after a rename, therefor the css selector sees the old name.

:+1:

Sorted.


the project is missing its open-source LICENSE file and headers

This is problematic given that we use TypePal in the Rascal-core project and rascal-lsp and rascal-eclipse.

True, some files have a BSD2 license, while others have no license.


git-bash clear

Little problem on "clear" command use with git-bash, the scene do not clear and go to top, writing on top of the older text.

dup of https://github.com/Eugeny/terminus/issues/28 ?

Yes didn't see it sorry :D


Update JCommander to 1.83

Fixes #3122 .
Did you remember to?

[ ] Add test case(s): not needed for this update
[x] Update CHANGES.txt
[ ] Auto applied styling via ./gradlew autostyleApply: not needed for this update

Thank you for merging it


Video Doorbell Phantom Rings and HomeBase2 False Alarm Triggering[Bug]:

What happened?
Since updating to v1.0.0-rc.2 my HomeBase2 displays the "alarm triggered" status in homekit when the system is set to Eufy's "Off" mode rather than "Disarmed." And today I started getting phantom rings on the doorbell. I still haven't fixed this issue. The doorbell will ring every 30 minutes or so. The doorbell may just be a hardware issue with the chime, but I wanted to bring it up for your SA.
Thank you for all of the work you've done on this plug-in!
Plugin Version
v1.0.x (Supported)
HomeBridge Version
v1.3.x (Supported)
NodeJS Version
v14 (Supported)
Operating System
Raspbian
Relevant log output
No response

Hello,
Are you sure using v1 ?
About the off/disarmed :
Can you go back to the plugin settings and choose disarmed instead of off ? We disabled the off settings.
Know issue will fix in 1.1.0 #147
For the phantom ring. Can you enable debug and send us the log output ?


make use of packages-meta-ext-v1.json.gz?

hi.  below is a hack to use the packages-meta-ext-v1.json.gz file announced last year.
i wonder if this sort of functionality, if not this implementation, might be of interest?
this allows some amount of queries that would otherwise go to aur.archlinux.org to be handled locally.  this is likely good for the community, and possibly (if network connections are slow) for the user.
this implementation, however, only attempts to infer dependency information locally.  and, being lazy, i did it only in aur-depends, not in aur-query where it probably belongs.
an issue: info requests are probably easy to handle locally.  the semantics of search requests might be hard to handle  locally; it depends on how byzantine the code running on aur.archlinux.org might be; i have no idea -- maybe it would be very simple.
the "user interface" is an environmental variable, that i named AUR_META_FILE.  i'm not wild about that user interface, but it works, and my sense is that it is compatible with the code.
a second issue is that by using this file, the user is exposed to very stale information if once they download the file, and set up the environmental variable pointing to the file, they never update it.  one could, in the code, check the date on the file, and fall back to querying over the network if the file is too stale.
if interested, let me know in what ways i might help.
here's the patch.  for whatever reason (because of the .patch extension?), i couldn't "attach" it.
From be4d60211ac892e4588a195e7115239b56d9478c Mon Sep 17 00:00:00 2001
From: Greg Minshall<EMAIL_ADDRESS>Date: Tue, 21 Jun 2022 10:23:15 +0300
Subject: [PATCH] aur-depends: use packages-meta-ext-v1.json.gz

to reduce network traffic, load on aur.archlinux.org
---
 lib/aur-depends | 28 ++++++++++++++++++++++++++--
 1 file changed, 26 insertions(+), 2 deletions(-)

diff --git a/lib/aur-depends b/lib/aur-depends
index 0e87340..e995026 100755
--- a/lib/aur-depends
+++ b/lib/aur-depends
@@ -67,13 +67,37 @@ tr_ver() {
     sed -r 's/[<>=].*$//g'
 }

+aur_query() {
+    if [ -z "${AUR_META_FILE}" ]; then
+        aur query -t info "$@"
+    else
+        if [ "$1" != "-" ]; then
+            IFS="|"
+            names="$*"
+        else
+            # okay, not the most efficient, but ...
+            names=""
+            sep=""
+            while read -r name; do
+                names="${names}${sep}${name}"
+                sep="|"
+            done
+        fi
+        if [ -n "${names}" ]; then
+            zcat "${AUR_META_FILE}" |
+                jq --arg search "^(${names})\$" \
+                   '[.[] | select(.Name | test($search)) ] | { "results":.,"resultcount":length }'
+        fi
+    fi
+}
+
 # shellcheck disable=SC2086
 chain() {
     local a num sub
     local select_args=("$1" "$2" "$3" "$4")
     shift 4

-    aur query -t info "$@" > json/0 || exit
+    aur_query "$@" > json/0 || exit
     num=$(count json/0)

     if (( num < 1 )); then
@@ -93,7 +117,7 @@ chain() {
         # Avoid querying duplicates (#4)
         cut -f1 tsv/$sub >> seen # pkgname
         cut -f2 tsv/$sub | tr_ver | grep -Fxvf seen | \
-            aur query -t info - > json/$a || exit # rpc error
+            aur_query - > json/$a || exit # rpc error

         if [[ -s json/$a ]]; then
             num=$(count json/$a)
--
2.37.0

I've looked into this approach in the past, but it was too slow for my liking: https://github.com/AladW/aurutils/issues/859#issuecomment-1094069933
I made a quick prototype for the upcoming aur-format, and things don't look much better:
❯ hyperfine 'aur pkglist -i | ./aur-format'
Benchmark 1: aur pkglist -i | ./aur-format
  Time (mean ± σ):     842.8 ms ±  10.3 ms    [User: 697.4 ms, System: 114.8 ms]
  Range (min … max):   817.6 ms … 852.7 ms    10 runs

The issue is that the metadata dumps are not suited for incremental parsing, so you have to load the whole thing. There's a proposal for a hybrid pkgname/JSON format so that it is easy to filter out the names you want:
https://gitlab.archlinux.org/archlinux/aurweb/-/issues/172
The environment variable (I called it AUR_METADEST) and TTL logic are already available in aur-pkglist, though. Note that new lists are only created every 5 minutes by aurweb.
What I've settled on for my personal use is an caching back-end:
https://github.com/moson-mo/goaurrpc
Per the above, this is always 5 minutes out-of-date, but the performance is better:
❯ hyperfine 'aur depends ros-melodic-desktop'  # JSON::XS with goaurrpc
Benchmark 1: aur depends ros-melodic-desktop
  Time (mean ± σ):      1.103 s ±  0.048 s    [User: 0.625 s, System: 0.138 s]
  Range (min … max):    1.051 s …  1.196 s    10 runs

❯ hyperfine 'aur depends ros-melodic-desktop'  # JSON::XS with aurweb
Benchmark 1: aur depends ros-melodic-desktop
  Time (mean ± σ):      1.910 s ±  1.003 s    [User: 0.603 s, System: 0.104 s]
  Range (min … max):    1.513 s …  4.752 s    10 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet PC without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

❯ hyperfine 'aur depends ros-melodic-desktop'  # jq with goaurrpc
Benchmark 1: aur depends ros-melodic-desktop
  Time (mean ± σ):      1.808 s ±  0.035 s    [User: 1.464 s, System: 0.085 s]
  Range (min … max):    1.754 s …  1.854 s    10 runs

❯ hyperfine 'aur depends ros-melodic-desktop'  # jq with aurweb
Benchmark 1: aur depends ros-melodic-desktop
  Time (mean ± σ):      2.313 s ±  0.286 s    [User: 1.394 s, System: 0.087 s]
  Range (min … max):    2.131 s …  3.108 s    10 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet PC without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

As you may notice from the benchmarks, the performance of a third-party backend is also much more stable than aurweb upstream, which sees much heavier use/traffic. To use it, set AUR_QUERY_RPC=https://server.moson.rocks/rpc.

thanks.  it is funny that parsing from a local disk is slower than over the network!  though, the fact that jq needs to parse, and re-parse, the 43MB file, certainly explains it.
thanks for the pointers to goaurrpc and to the proposal for a hybrid file format.
i guess this is closed.  cheers!


CSCC Create Finding: 404 Method not found

In 2.4.0 release testing:

This error came from using a release project that was not whitelisted.  No errors when using a project that was whitelisted.


Allow errorClass to survive undefined

Just noticed errorClass generator can fail if props.errors is undefined. It's another question why that can happen in the first place of course.

I tend to play fast and loose with passing null and undefined values around. I usually do a variable == null test to catch both cases, which is admittedly a somewhat cryptic idiom, or !variable if I don't expect strings or numbers to be passed in. In this particular case I believe that the || errors === null after the !errors test is redundant.

On Friday, 27 March 2015, Olaf Delgado-Friedrichs<EMAIL_ADDRESS>wrote:

I tend to play fast and loose with passing null and undefined values
around. I usually do a variable == null test to catch both cases, which
is admittedly a somewhat cryptic idiom, or !variable if I don't expect
strings or numbers to be passed in. In this particular case I believe that
the || errors === null after the !errors test is redundant.

Yeah, that's true. I will change the PR.

—
Reply to this email directly or view it on GitHub
https://github.com/AppliedMathematicsANU/plexus-form/pull/25#issuecomment-86774216
.

I removed the extra check.

Sorry for the long wait! That shouldn't have taken me 5 days.

No problems. :)


Type-inference failure when using --check-bounds=no on ARM

I am on a Nvidia Grace CPU, using Polyester.jl v0.7.9 and Julia 1.10.0.
When starting Julia with julia -t 16 --check-bounds=no:
julia> using Polyester

julia> f(n) = @batch for _ in 1:n end
f (generic function with 1 method)

julia> f(50)

julia> @time f(50)
  0.000696 seconds (146 allocations: 4.562 KiB)

julia> @time f(500)
  0.001785 seconds (596 allocations: 18.625 KiB)

julia> @code_typed f(50)
CodeInfo(
1 ─── %1   = Base.Threads.cglobal(:jl_n_threads_per_pool, Ptr{Int32})::Ptr{Ptr{Int32}}
│     %2   = Base.pointerref(%1, 1, 1)::Ptr{Int32}
...
122 ┄ %437 = φ (#120 => %322, #88 => 0x0000000000000000)::UInt64
│     %438 = Base.add_int(%437, 0x0000000000000001)::UInt64
│     %439 = Base.bitcast(Int64, %438)::Int64
│     %440 = Base.bitcast(Int64, %51)::Int64
│     %441 = invoke Main.:*(%439::Int64, static(1)::Static.StaticInt{1})::Any
│     %442 = (%441 + static(1))::Any
│     %443 = (%442 - static(1))::Any
│     %444 = invoke Main.:*(%440::Int64, static(1)::Static.StaticInt{1})::Any
...

Allocations happen at each loop iteration, because for some reason *(::Int64, ::StaticInt{1}) was not inlined? AllocCheck.jl reports a lot of dynamic calls where Static values are used. The rest of @code_typed shows similar occurrences.
This does not happen on x86.

This does not happen on x86.

Even with --check-bounds=no?
There have been similar reports elsewhere about --check-bounds=no causing inference problems that I could reproduce on x86, e.g. https://github.com/JuliaSIMD/StrideArrays.jl/issues/78

Upon trying again, it does also happen on x86 with Julia 1.10. I mistakenly used Julia 1.9.4 for which the bug does not happen, therefore it might very well be the exact same bug as you mentioned.


Added assets and updated readme tested up to 4.8

Updated the assets and the readme

Wait to merge until we have the updated compiled.js here.

For PR's like this try to to do different commits for stuff we can't review, and stuff we can review. For this one PR, assets could be one commit and .php, .txt files could be another commit.

For compiled.js update
I do a frontend release npm run build:production
https://github.com/cloudflare/cloudflare-plugin-frontend/releases
Then do a commit with the version
https://github.com/cloudflare/Cloudflare-WordPress/commit/160d606b8b9fe03fc36cab9d2aea9aa2d8ec6677

@thellimist sorry about the single commit, I was feeling annoyed because nothing actually changed, github is diffing the content and git is diffing the meta data. I'm going to wait to PR the prod build till @jwineman tests all the integrations

Built from https://github.com/cloudflare/cloudflare-plugin-frontend/commit/b4b4c72da6637b861cbf06e0991dd806c21baa5c


Need to support OpenJPEG 2.x

Our FindOpenJPEG.cmake seems to look specifically for OpenJPEG 1.5. We should prefer 2.x, if found, and use it properly.
The solution will need to be backported to the release branch, since some Linux distributions may drop 1.5 soon.

Let Matteo Vescovi know when this is completed.

@lgritz I've noticed that issue #957 could probably be closed once this one has a fix.
And yes, it was reported against 1.4.13... but that version is out of release at this point, afaik.

Hey folks, is there any timeline on the next release at all?
We're trying to update our main openjpeg in homebrew/core (Which is the one users get by default when they brew install openjpeg) to 2.1 & the currently released version of this project is one of the hold-ups: https://github.com/Homebrew/homebrew-science/pull/3865.
That PR there inserts a semi-hacky workaround but if we can hold off for a short time for a new tag & avoid the workaround that's certainly more desirable.

I'm planning to cut releases on Aug 1, and it will build fine against OpenJpeg 2.1. Is that soon enough, or do I need to try to do it sooner? (I'm at SIGGRAPH this week, it's not a good time to try to do a release and be careful about it, unless there's an emergency.)

August 1st sounds great to me. We've waited well over a year to start moving on updating our primary formula to OpenJPEG 2.1, it won't kill us to wait a little under a week more. Thanks!


Very long username breaks though the container on Users page

Describe the bug
On the "Users" page, when a user has a very long username, it will makes his username break though the container and overlapped with the profile picture of the next user.
To Reproduce
Steps to reproduce the behavior:

Set a very long username
Go to 'Users'
See error

Expected behavior
Username needs to be truncated with the ellipsis.
Platform

Device: Desktop
OS: macOS
Browser: Chrome
Version: 114

Yes, it is a problem.
But a more suitable way for us to handle it is to force line feeds to be displayed.
We will have this fix in a recent release.
@conr2d Thanks!


BFE blank node generation when adding

A disconnected blank node appears in the RDF/JSON-LD generated by the tool.
For example, on the demo site (http://bibframe.org/bfe/index.html), select monograph and then work and on the resulting form click on "genre form" and type in soul music in the search box. The URI for the authority is http://id.loc.gov/authorities/genreForms/gf2014027106 .  Select your result and save and then select preview to see the RDF/JSON-LD/N3.
The following is the result:
"@prefix bf: http://id.loc.gov/ontologies/bibframe/.
@prefix bflc: http://id.loc.gov/ontologies/bflc/.
@prefix madsrdf: http://www.loc.gov/mads/rdf/v1#.
@prefix pmo: http://performedmusicontology.org/ontology/.
@prefix rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#.
@prefix rdfs: http://www.w3.org/2000/01/rdf-schema#.
@prefix xsd: http://www.w3.org/2001/XMLSchema#.
http://id.loc.gov/authorities/genreForms/gf2014027106 a bf:GenreForm.
http://id.loc.gov/resources/works/e13856367125358014071859220359091762907 a bf:Work;
bf:content http://id.loc.gov/vocabulary/contentTypes/txt;
bf:genreForm http://id.loc.gov/authorities/genreForms/gf2014027106.
http://id.loc.gov/vocabulary/contentTypes/txt a bf:Content;
rdfs:label "text".
_:b0_b0 a bf:GenreForm;
rdfs:label "Soul<EMAIL_ADDRESS>_:b0_b0 is a blank node which saves the label for soul music, but the blank node is not connected to the rest of the RDF.
We have seen this behavior when adding other properties such as subject heading.
For example, when adding a result for "soul music" in "Subject for this work", the following is the result of previewing after saving subject:
"http://id.loc.gov/authorities/subjects/sh85125359 a bf:Topic.
http://id.loc.gov/resources/works/e136303650385176791529541883584948437650 a bf:Work;
bf:content http://id.loc.gov/vocabulary/contentTypes/txt;
bf:subject http://id.loc.gov/authorities/subjects/sh85125359.
http://id.loc.gov/vocabulary/contentTypes/txt a bf:Content;
rdfs:label "text".
_:b1_b0 a bf:Topic;
rdfs:label "Soul music"@en. "
I am creating this issue here but if this is not the right place for it, please feel free to move it or let me know. Thanks!

Also feel free to add/remove whatever labels are appropriate.

What is the correct behavior? Not to output the label at all? We do not need the label in the RDF output, correct? We don't need statements like http://id.loc.gov/authorities/genreForms/gf2014027106 a bf:GenreForm or http://id.loc.gov/authorities/subjects/sh85125359 a bf:Topic either, is that right?

With other links BFE tends to have a text label (and this is useful for display). It CERTAINLY should not have the disconnected label -- so fix, or remove.

Basically when you click a button that opens a resource template with a lookup type property, the modal window creates a new blank node in the form store but notes there's a lookup option. When the user selects a uri it also pull the label into the form. When you save, what is supposed to happen is the blank node is replaced with the uri, the type and label are changed to have the uri as the subject in the form store and then those triples are put in the editor store.  Also, there should only be a delete button since you can't really edit a lookup.
I am not sure what is wrong, looking into it.

Fixed on bibframe.org...
@prefix bf: <http://id.loc.gov/ontologies/bibframe/>.
@prefix bflc: <http://id.loc.gov/ontologies/bflc/>.
@prefix madsrdf: <http://www.loc.gov/mads/rdf/v1#>.
@prefix pmo: <http://performedmusicontology.org/ontology/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.

<http://id.loc.gov/authorities/genreForms/gf2014027106> a bf:GenreForm.
<http://id.loc.gov/resources/works/e96952614330921705131910809654817944531> a bf:Work;
    bf:content <http://id.loc.gov/vocabulary/contentTypes/txt>;
    bf:genreForm <http://id.loc.gov/authorities/genreForms/gf2014027106>.
<http://id.loc.gov/vocabulary/contentTypes/txt> a bf:Content;
    rdfs:label "text".

Closing, fixed in master.


Is it possible to add the the french layer "Agriculture/Cours d'eau BCAE 2021" from Géoportail

I am curious to know the use.
To trace your track for the moment I don't see the use of it.

to avoid to use some beds of small rivers when the weather is dry

They are not on IGN or OpenStreetMap?
I map the streams in my area on OpenStreetMap.

When #121 is implemented, users will be able to add such specific maps.


feat(sst/rds): add additional rds versions

feat(sst): add support for additional rds engine versions
doc(sst/rds): add additional engine version

For serverless mode not all versions are supported.


update spec.html to current spec

Hi folks,
This partially addresses my issue #139 where I was having a hard time seeing what was different between the proposal and the existing spec. There are a couple of changes that have happened in the last year which were not merged into this spec. I tried to get all of them.
The biggest one is that TopLevelEvaluationJob no longer exists (https://tc39.es/proposal-top-level-await/#sec-toplevelmoduleevaluationjob) removed in (https://github.com/tc39/ecma262/pull/1597/files). It is not in this pull request either, because I wasn't sure which part of thee spec this would now touch.
the other significant change is https://tc39.es/proposal-top-level-await/#sec-source-text-module-record-execute-module -- in the original, the change was quite small, but now it is larger. I don't know if this is accurate.
I think we could do with some tooling to make these diffs easier... Looking forward to peoples comments.
You can see the "diff" from the current to the version in this repo here: https://github.com/codehag/proposal-top-level-await/pull/1/files

The text around TopLevelModuleEvaluationJob is replaced by logic in HTML's JS module loading. See #45 . @Ms2ger , could you review this patch?

Thanks for the PR, I'll try to look in detail soon.

sorry it took a while to do those @Ms2ger -- do you have further comments?


[Feature Request] Option to download an episode without subtitles

Title.
I am from South America and I would like to start subbing some episodes that aren't on South America (Oregairu, for example). I can use the Unblocker to get the episodes but the subtitles are already on the .mp4, I would like to have the original .raw with their subtitles on the other hand.
Thanks.

That would be "Softsub" which is currently not supported by this app.

Sorry, there is no way to get subtitle-free videos with the Crunchyroll API, from what I could see.

Cancel that, I have added a new experimental feature in 1.3.5 to download without subtitles... --language=none
Please report any bugs you find! If this feature works well, I will look into softsub functionality :)

Amazing, I will be testing it :) going to update ASAP.

I will look into softsub functionality :)

YAY 🎉
If this tool can download softsub and hardsub, then it will have no competitors.
you could open an issue for testing the softsub functionality I would be glad to give some ideas about it.


restore passing in a pkgbuild path

Commit a07cd59cea847d182b500b0b17c7b7c750b3101c removed the option to specify a file in place of a PKGBUILD, but did not remove the option from the "Usage:" line of the help text. As makepkg supports a -p switch to do a similar thing, the functionality can be restored completely.

--
I am aware that I could just use makepkg directly, and that ist what I am actually doing in practice. But before switching away, I wanted to leave a pull request fixing the inconsistency with the help text so that others won't be confused like I was. If you instead want to remove the parameter from description entirely, that would be just as fine.

I'd prefer the chdir take place outside of mksrcinfo, as I suggested in the commit message you cite.

All chdir takes place only in second commit. You can also only merge the first one, which would allow for PKGBUILDs not named "PKGBUILD" and fits the help text accordingly.

I really wonder what the use case is for this....

Templates are, in my case. Expanding the templates in PKGBUILDs and composing parts thereof is easier to be done in dedicated files. Using a directory pkgbuilds/variant/PKGBUILD instead of a file PKBUILD.variant does not only introduce more hierarchy, all supplementary files would also be needed to be copied or linked besides the new PKGBUILD to use it.


notesnap_driver.c: modify struct notesnap_s member type

Summary

clang atomic no support other type:
modify .index type size_t --- atomic_int
modify .dumping type bool --- atomic_bool

Impact
Testing

https://github.com/apache/nuttx/blob/master/drivers/note/notesnap_driver.c#L372
ditto

https://github.com/apache/nuttx/blob/master/drivers/note/notesnap_driver.c#L372 ditto

OK


Can create a new data type without specifying the 'underlying' data type

You can save a data type using the Admin Only Property property editor without having specified the underlying data type, which of course then leads to unexpected behaviour. Would be better if you couldn't save whilst this property is blank

There's meant to be something with an IValueValidator for the Data Type's configuration field.
https://our.umbraco.com/apidocs/v8/csharp/api/Umbraco.Core.PropertyEditors.IValueValidator.html
But I've never fully got my head around how it works... I haven't even implemented these on Contentment! 😳


Doc updates for DH/DSA examples

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Thanks for reviewing. Merged to master.


Clean up controllers.js

Currently, controllers.js is approx. 1k lines long. I'd like to break this up into manageable chunks, perhaps making a controllers/ directory with a file for each resource type/page.

Closed via 8f7bce224b8a85fcebf8f0b759d8ce06e02e2276 with migration to jQuery. JS is now in separate files.


Cleanup: move ArrayPropertyOpt out of COWArrayOpt.cpp.

These are separate, mostly unrelated passes. Putting them in their own
files makes it easier to read the code, understand how to control the
passes, and makes it possible to independently trace, and debug them.

@swift-ci test

This is part of my work to consolidate SILCloner logic and fully ban address-type block args.

@swift-ci smoke test and merge


lint: raise timeout to avoid flakyness

A two seconds timeout makes the test suite a bit flaky on heavily loaded build machines.
This commit raises the timeout to 10 seconds to give a bit more headroom to the scheduler.

see: https://github.com/NixOS/nixpkgs/pull/350654#issuecomment-2434491169

thanks so much. I'm working on a new release now

I can just pull the change here in a patch or something. I don't necessarily need a release (unless you were already going to make one, then by any means).


Possible to set lastRelease?

I have an existing repo that I'm converting into a monorepo. So there are already tags using the default format v${version}.
So when running with -e semantic-release-monorepo it cannot find any previous releases because it's looking for the wrong tag.
The --tag-format can't be used as I want the nextRelease to have the new format.
Log
[semantic-release] » √  Completed step "verifyConditions" of plugin "@semantic-release/git"
[semantic-release] » i  No git tag version found on branch master
[semantic-release] » i  No previous release found, retrieving all commits
[semantic-release] » i  Found 64 commits since last release
[semantic-release] » i  Start step "analyzeCommits" of plugin "[Function: ]"
[semantic-release] [[Function: ]] » i  Found 0 commits for package test-package since last release
[semantic-release] [[Function: ]] » i  Analysis of 0 commits complete: no release

Not sure why I didn't think of this. But a workaround is simply to create the correct tag where the previous release tag is.

Glad it worked out!


suggestion: update changelog when new version releases

CHANGELOG.md is outdated. 😄

actually i think it would be a good idea to get rid of it

I recommend keeping it, it's generally a good thing to have if only a release is bug fixes and minor changes

changelog has been successfully updated!


(feat) add ttyd and tmux  to dockerfiles

Adds ttyd to docker distribution. This doesn't change any existing functionality, but in future allows exposing TTY via browser to avoid docker (kubectl) attach.
CMD ttyd python bin/hummingbot_quickstart.py

UI could be exposed via usual HTTP(S) protocols, which makes it much easier to operate in orchestrators.

P.S. I've prepared a Helm chart that relies on this potential functionality: https://github.com/DevopsCare/artifacts/tree/master/charts/hummingbot

Just figured out ttyd runs a new instance of command instead of "sharing" that. Will work on that, maybe add a screen

Hello @vermut
The Hummingbot Foundation just started the governance process for the community to approve or reject Pull Requests through Pull Request Proposals.
For more information about how PRP votes work, check this page: https://hummingbot.org/governance/prp/
We want to know if you still have interest in having your Pull Request merged into the main codebase.
If so, please check the following on your Pull Request for our team to be able to open it for community voting:

Your Pull Request is targeted to the development branch
Your branch is up to date with the current development branch
All GitHub checks have passed
There is no merging conflicts

If you have any questions or need any help, feel free to reach us out on the #dev-general channel on our Discord (https://discord.gg/HAgZ79nzU4)

If you have no interest in merging this PR to our code-base or don't reply to this comment in 30 days, the Foundation team will close this PR.
You can still create a new PR any time you want!
Thank you for contributing to Hummingbot Client!

Closing this PR as the developer has not responded and created a PRP.


logging: Cleaning references to tracing in logging

There were some leftovers in logging after attempt to use
logging as tracing backend. Removing all references since it
lead to test compilation failures.
It fixes currently broken CI.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

this didn't go in to v2.7, so does it really need a backport?

Removing the backport tag, as the changes that likely introduced this were not introduced into v2.7-branch.
See #38811

this didn't go in to v2.7, so does it really need a backport?

the code being removed here was not part of #38811, it was before and was merged long time ago.

So there are 2 things:

dirty code, references to tracing which is not supported
failing CI in tests introduced by #38239. Which started to fail after #38811 merge.

So if we consider references to not supported feature as bug then we should backport it to 2.7.

this didn't go in to v2.7, so does it really need a backport?

the code being removed here was not part of #38811, it was before and was merged long time ago.

I see - added the backport label again

I suspect the removal of z_log_msg2_put_trace is causing CI issues.


Puplisher 2.1.3 can not subscribe from some OPC UA servers anymore

Hello,
I have recently updated the opc publisher from version 2.1.2 to version 2.1.3
Now the opc publisher refuses to publish variables from some opc servers:
11/27/2017 09:57:37: Object reference not set to an instance of an object.
11/27/2017 09:57:37: Error processing monitored item notification

With the previous version, this has worked.

With version 2.1.2 the delivered data looks in device explorer like this:
27/11/2017 11:51:33> Device: [publisher.example.com], Data:[{"ApplicationUri":"urn:00:06:71:33:00:17:example.com","DisplayName":"ns=3;s=_System.General.Temperature","NodeId":"nsu=urn:System_items;ns=3;s=_System.General.Temperature","Value":{"Value":48.5,"SourceTimestamp":"2017-11-27T10:51:17.7664654Z"}}]Properties:
'content-type': 'application/opcua+uajson'
'devicename': 'publisher.example.com'

Hello @hansgschossmann
I have tried with your doker image hansgschossmann/iot-edge-opc-publisher:2_1_3_fix
and it does not solve the problem.:
12/18/2017 10:12:32: Object reference not set to an instance of an object.
12/18/2017 10:12:32: Error processing monitored item notification

publishednodes.json.txt

It was not supposed to fix it, but get more info. Could you also send me the publisher log file?

Here is the corresponding publisher logfile:
publisher.log.txt

hi @JuergenKosel, could you give the docker container another try?

With your new docker image it looks much better. It looks like the issue is solved.

Could you please send me the publishednodes.json and the publisher.log.txt of this?
From: Juergen Kosel<EMAIL_ADDRESS>Sent: Dienstag, 19. Dezember 2017 08:55
To: Azure/iot-edge-opc-publisher<EMAIL_ADDRESS>Cc: Hans Gschoßmann<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/iot-edge-opc-publisher] Puplisher 2.1.3 can not subscribe from some OPC UA servers anymore (#100)
With your new docker image it looks much better. It looks like the issue is solved.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fiot-edge-opc-publisher%2Fissues%2F100%23issuecomment-352666496&data=02|01|johanng%40microsoft.com|432e28aa5f464a95315f08d546b5bdb2|72f988bf86f141af91ab2d7cd011db47|1|0|636492668739888981&sdata=RvDkNKOrAEaT1VdsEWhTPITS0YxBS18f%2BUgP8ZHo4bM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHxelh2tzO6Vd9bewAvejIBTCsX0r4Eyks5tB2u3gaJpZM4Qrb4D&data=02|01|johanng%40microsoft.com|432e28aa5f464a95315f08d546b5bdb2|72f988bf86f141af91ab2d7cd011db47|1|0|636492668739888981&sdata=xAySxWMMa8KkXcrhoxZERG73sUOQSD66w%2BKwP27310Y%3D&reserved=0.

Yes
publishednodes.json.txt
publisher.log.txt

Closing due to inactivity/solved issue.


0.4.4: Mutations overlapping queries stop SSR

Take the following query:
const withGrades = graphql(gql`
  query grades($limit: Int!, $offset: Int, $order: Object, $search: Object) {
    grades (limit: $limit, offset: $offset, order: $order, search: $search) {
      count
      items {
        id
        title
        description
        createdAt
        updatedAt
      }
    }
  }
`, {
  options(ownProps) {
    const query = queryToState(ownProps.location.query);
    return {
      variables: {
        limit: query.limit || 10,
        offset: query.offset || 0,
        order: query.sortKey ? { [query.sortKey]: (query.sortDsc === true || query.sortDsc === 'true') } : null,
        search: query.search && Object.keys(query.search).length ? query.search : null
      }
    };
  },
  props({ ownProps, data }) {
    if (data.errors) return { errors: data.errors };
    return {
      loading: data.loading,
      refetchQuery: data.refetch,
      item: null,
      items: data.loading ? [] : data.grades.items,
      queryCount: data.loading ? 0 : data.grades.count,
    };
  }
});

Here SSR works well, but the mutation has no access to the refetchQuery prop on the client.
@graphql(gql`
  mutation ($title: String!, $description: String) {
    createGrade(title: $title, description: $description) { id }
  }
`,
{
  props({ ownProps, mutate }) {
    return {
      createItem(variables) {
        return mutate({ variables })
          .then(() => ownProps.refetchQuery());
      }
    }
  }
})
@withGrades // << BELOW
export class GradesSidebar extends React.Component {
  render() {
    return <Sidebar singular="Grade" {...this.props} />
  }
}

Here the exact opposite happens: SSR doesn't work, but the client can access the props normally.
@withGrades /// << ABOVE
@graphql(gql`
  mutation ($title: String!, $description: String) {
    createGrade(title: $title, description: $description) { id }
  }
`,
{
  props({ ownProps, mutate }) {
    return {
      createItem(variables) {
        return mutate({ variables })
          .then(() => ownProps.refetchQuery());
      }
    }
  }
})
export class GradesSidebar extends React.Component {
  render() {
    return <Sidebar singular="Grade" {...this.props} />
  }
}

I traced the issue to line 221 in graphql.jsx:
      // for use with getData during SSR
      static fetchData = operation.type === DocumentType.Query ? fetchData : false;

When I turned it into an if statement everything worked:
if (operation.type === DocumentType.Query)
    GraphQL.fetchData = fetchData;

And for the life of me I have no idea why. (I'd really appreciate an explanation!)

@voodooattack thank you for the excellent example and starting to hunt down the issue! I'll take a look and see what I can figure out!

@voodooattack I have no idea why that changes fixes it, but it definitely does! I've made the change and will release it and keep poking around to figure out why!

@jbaxleyiii Excellent. Thank you!


Debug cleanup on Python 3.9.

The CI has been often hanging at the end of the pytest run on Python 3.9. I suspect it's related to the changes in the client.

I can reproduce this hanging on Python 3.8.5 locally:
In [1]: from tiled.client import from_profile
c
In [2]: c = from_profile("bmm_direct")
OBJECT CACHE: Will use up to 6_290_642_534 bytes (15% of total physical RAM)

In [3]: c
Out[3]: <Catalog {22521, 22524, 22525, 22526, 22528, 22529, 22534, ...} ~123 entries>

In [4]: del c

In [5]: del _3

In [6]:
Do you really want to exit ([y]/n)? y
<HANGS HERE UNTIL I INTERVENE WITH ^C>
^CError in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/home/dallan/miniconda3/envs/py38/lib/python3.8/concurrent/futures/thread.py", line 40, in _python_exit
    t.join()
  File "/home/dallan/miniconda3/envs/py38/lib/python3.8/threading.py", line 1011, in join
    self._wait_for_tstate_lock()
  File "/home/dallan/miniconda3/envs/py38/lib/python3.8/threading.py", line 1027, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
KeyboardInterrupt

To be clear the above is on this branch.
Very likely the problem is with the portal failing to shut down: https://github.com/bluesky/tiled/blob/main/tiled/client/_testclient.py

The best fix may be to refactor all the tests to use context managers. Not a small task, but probably a good idea.


Test driver should correctly quote arguments

When invoking other commands from the compiler driver (rm, gcc, etc) we need to quote arguments with Filename.quote_command in order to properly handle file paths with spaces, etc.
(Discovered while investigating nlsandler/writing-a-c-compiler-tests#44)

Fixed in updated main branch


[build] Add Dockerfile to build on an Ubuntu image

Description
Add Dockerfile to build on an Ubuntu image and documentation on how to use Dogecoin from the container.

I do not run a node myself and honestly just tried a couple of commands, but there is probably some configuration to do.
Some configuration with the environnement variables, how to give some files if needed, how to backup. If I'm not wrong it need also credentials ?
It have to be generic.

Closing and re-opening to trigger Travis.

Some configuration with the environment variables, how to give some files if needed, how to back up. If I'm not wrong it need also credentials ?
@rnicoll @patricklodder What would be the default settings to consider to run a node ?

I haven't dug into this in depth yet, but my intuition is it should have the entire data directory mounted into the Docker container (as in persisted outside Docker), so the configuration is provided/editable from the host. Let me know if that seems crazy?

@p-j01 Globally seems okay globally but the COPY will take a long time because of qa-assets.
IMO, We should do the compile on an ENTRYPOINT

Agree that using mounting data directory is a (quick) way to configure the node, but for me a docker way would be to use environment variables.
Actually, I think it really depends on the end user of dogecoind, who are they, and what are their needs ?
Is it a small user with his GUI and his buck to send to his friends (I guess main dogecoin user use other solution like exchanges ?), a miner, a mining pool, anyone/any organization who want to validate transaction by his own (custodial services), a developer who want to code, etc.
Depending on that, the configuration might really change, from a small change in RPC credentials, to specific settings designed for a complex network, with or without backup/wallets (aka volumes). The docker install can probably bring more flexibility.
For example, in the current Dockerfile,  dogecoin-qt is created by default, some user won't need GUI by default (is it cross-platform, windows compatible?).

Some configuration with the environment variables, how to give some files if needed, how to back up. If I'm not wrong it need also credentials ?
@rnicoll @patricklodder What would be the default settings to consider to run a node ?

I haven't dug into this in depth yet, but my intuition is it should have the entire data directory mounted into the Docker container (as in persisted outside Docker), so the configuration is provided/editable from the host. Let me know if that seems crazy?

I haven't dug into this in depth yet, but my intuition is it should have the entire data directory mounted into the Docker container (as in persisted outside Docker), so the configuration is provided/editable from the host. Let me know if that seems crazy?

@rnicoll Which directory are you referencing?

@p-j01 Globally seems okay globally but the COPY will take a long time because of qa-assets.
IMO, We should do the compile on an ENTRYPOINT

@mmicael1 Where is located qa-assets ?

I made a Dockerfile from scratch, see https://github.com/dogecoin/dogecoin/pull/2337

Why

It was simple base, the design of the other version is different and nothing was reused. Using release instead of sources, adding user, manage volume permission, using variable for image build, entrypoints... The docker-entrypoint.py script.
Wasn't able to reuse, starting from scratch made sense.

I suggest updating the documentation to urge users using dogecoind to create a volume for their data directory.
Each time a user casually performs a docker run, their data directory will be lost.  This will initiate a new download of the blockchain data which can take days or weeks, and unnecessarily pulls resources from the nodes on the network.  To a user of the docker image, the internal directory structure of the docker image is not known - they won't know where to point a volume.
My method of urging users to do so was to only give an example of running the image with a volume.  #2578

I have created https://github.com/dogecoin/docker and seeded it with #2337.


Consider flattening Sequence storage and making Interval Collection blob optional if empty

ODSP storage is sensitive to number of nodes.
So, while this might not be good practice in general (of design runtime based on one storage data point), I wonder if we want to consider flattening sequence storage. I.e. instead of having
header
content/header
content/body
content/catchUpOps

We have
(optional, only if not empty) intervalCollection
header
body
(optional, PR is out) catchUpOps

This obvious adds a requirement for Sequence to know about all the names that merge tree can write out, which is not ideal. And it has non-trivial back compat impact, so chances of us doing anything here is low.

Flattening seems good. I'd love to use some kind of mixin/plugin model for shared interval to make it truly pay to play, and decouple it from shared string even more. This would also open the door for other indexing type that preserve data on top of the shared string

Flattening seems good. I'd love to use some kind of mixin/plugin model for shared interval to make it truly pay to play, and decouple it from shared string even more. This would also open the door for other indexing type that preserve data on top of the shared string

@anthony-murphy - are you planning to take a look soonish? If not, I'd rather close it :)
The priority of that item dropped a bit with latest improvements in ODSP storage (it's less sensible now to edge count) and upcoming blob aggregation. Might be still good change if it's not that hard, but if it's a ton of work, it's probably worth punting.

I think we should just close this, as this would be a format breaking change for shared string, which would also affect things like search, so does not seem worth it.


Tag a new release

Describe the bug
Can you tag a new release? You've recently relaxed version constraints but those are not in a pypi released version, that still declares incompatibility with sphinx 6
Reproduce the bug
...
List your environment
...

cc @choldgraf  ?

Any updates on this? Would be great to get those constraints removed if possible! Looks like all the changes have already been made and the package just needs a new tagged release for PyPI/conda-forge.

We would greatly appreciate a new release in the near future 🙏 - this would close https://github.com/executablebooks/MyST-NB/issues/466 and https://github.com/executablebooks/MyST-NB/issues/493 and allow us to move to Sphinx 7 (and away from nbsphinx).

Can be closed, v1.0.0 has been released and is on PyPi.


Add optional argument for glob pattern in databricks COPY INTO

Description

This PR adds an optional key word argument to the databricks_copy_into macro that allows the user to specify a pattern for file globbing. Please let me know if there are unintended consequences i'm not considering but based on my reading of the docs this should work. Please let me know how you normally handle unit testing.
Checklist

[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

Hi @dluftspring, could you add an item in CHANGELOG? I'll backport this to 1.4, so the item would be under the section for 1.4.0. Thanks.

The linter failure is not related to this PR. Let's fix it later.

Thanks! merging.


features: add unsafeAnnotationsInConfig

Fix #1202 , for prohibiting propagation of insecure annotations from remote images into OCI runtime config.json
https://github.com/opencontainers/image-spec/pull/1061/files#r1194531089

@cyphar PTAL

@utam0k @cyphar @giuseppe Can we merge this?

@utam0k @cyphar @giuseppe Can we merge this?

I am fine with merging it, though @cyphar had some comments.  @cyphar are you fine to merge as it is?

@utam0k @cyphar @giuseppe Can we merge this?

As for me, it is fine.

I'm still not sure I agree that treating all annotations that "affect runtime behaviour" as "unsafe" is the desirable behaviour (IMHO it should be based on whether it could be used to escalate privileges -- but to be fair, this might be hard to figure out in some cases), but I can see @AkihiroSuda's point (and ultimately the stopSignal example is theoretical since no runtime implements that behaviour).
A small nit, but maybe we should rename the annotation to potentiallyUnsafeConfigAnnotations or parseableConfigAnnotations (if there is a less ugly sounding version of this I would prefer that) since the annotations are not necessarily unsafe, they just have the potential to be unsafe.

Renamed to potentiallyUnsafeConfigAnnotations as suggested

@cyphar LGTY?

cc @neersighted


No AD/SAML for now: Just make a throw-away login screen

We'll supply the credentials that have been configured by hand on the current instance.

Direction changed:

#35

We will be using CAS authentication.


Krew: fix DL URLs, add test instructions, add Linux/arm64 and Windows/amd64

This fixes Krews download URLs, which have been broken since this repository switched
from x.y.z to vx.y.z git tags, in kube-capacity v0.4.0.
Linux/arm64 and Windows/amd64 are added to the Crew manifest.
Instructions are added to the top of .krew.yaml describing how to render and test that template.

This addresses issue #54

Thanks @ivanfetch!


Questions about ablation study on rounds of training

First, I just want to say, thank you so much for the great work, and for open-sourcing your code as well!
I was looking at the training script and noticed that it seems to contain more than 3 rounds of training, while the paper only included the results from the first 3 rounds. Have you tried more rounds of training and if so did it lead to further performance improvement?

Hi, thank you for the interest!
Yes, the performance gets better with more rounds of training.
As mentioned in README.md, we have provide a checkpoint folder for your reference. You can try it with tensorboard --logdir=.


Shift after hovering on admin? button #280

Issue that this pull request solves
Closes: #280
Proposed changes
Brief description of what is fixed or changed
Types of changes
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Put an x in the boxes that apply

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] My changes does not break the current system and it passes all the current test cases.

Screenshots
Please attach the screenshots of the changes made in case of change in user interface
Other information
Any other information that is important to this pull request

@Kajol-Kumari done changes in navebar.css

@Kajol-Kumari done changes in navebar.css

@Kajol-Kumari please view the changes in navebar. Css

@Kajol-Kumari please view the changes in navebar. Css

@Kajol-Kumari please view the changes in navebar. Css

Remove the unnecessary changes from this PR

@Kajol-Kumari please view the changes in navebar. Css

Remove the unnecessary changes from this PR

Ok

Ok


Should enable streaming results

The API doesn't currently allow creating streaming results. It should.
Details:
The run and start methods of DuckDBPreparedStatement return DuckDBPendingResults that are in non-streaming mode, because they use duckdb_execute_prepared and duckdb_pending_prepared, not duckdb_execute_prepared_streaming or duckdb_pending_prepared_streaming. The latter have "DEPRECATION NOTICE"s, which means they will likely be removed in the future, but it's likely they will be replace by some other way to create streaming results. So, they can be used with relatively low risk that the functionality will go away.
Probably DuckDBPreparedStatement should have new methods, stream and startStream, that use duckdb_execute_prepared_streaming and duckdb_pending_prepared_streaming to return DuckDBPendingResults that are in streaming mode.
There should also be an isStreaming (or streaming) boolean property on DuckDBResult that uses duckdb_result_is_streaming.
There's duckdb_stream_fetch_chunk function, but there seems to be no point in exposing it, because it just calls duckdb_fetch_chunk (after checking whether the argument is in streaming mode).

This has been fixed in 1.1.3-alpha.8. See the updated README for details. Happy holidays! 🎉


Feat: Modify the font style of the entire website .

Describe the feature
Current font style of the website is ordinary one and not much attractive . Assign this task to me and I can change it to a much better font such as Poppins .
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSoC'24 contributor
[X] I want to work on this issue

Hey @meetarora10 Thank you so much for your raising issue.

As of now, we do not need it. We will let you know in the future if there is a need. Please search for another issue and raise it, which I'm happy to assign to you


Revert "Update docker image version"

Reverts atlassian/landkid#132

Original pull request appeared to be merging in content already present in master, but after merging it and inspecting its complementary revert PR, this no longer appears to be the case. Putting it down to a big in Github


cluster_setup.sh up-full crashes with TypeError: unsupported operand type(s) for -: 'str' and 'int'

doing a cluster_setup.sh up-full crashes with TypeError: unsupported operand type(s) for -: 'str' and 'int'

[jaten@instance-1 solutions-google-compute-engine-cluster-for-grid-engine]$ ./cluster_setup.sh up-full
Creating master boot disk(s): my-grid-mm
INFO: Resolved debian-7 to projects/debian-cloud/global/images/debian-7-wheezy-v20140415
INFO: Waiting for insert of disk my-grid-mm. Sleeping for 3s.
INFO: Waiting for insert of disk my-grid-mm. Sleeping for 3s.

Table of resources:

TypeError: unsupported operand type(s) for -: 'str' and 'int'

[jaten@instance-1 solutions-google-compute-engine-cluster-for-grid-engine]$

here is my properties file:
#!/bin/bash

# Copyright 2014 Google Inc. All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# Select a prefix for the instance names in your cluster
readonly CLUSTER_PREFIX=my-grid

# Name of GCE network to add instances to
readonly CLUSTER_NETWORK=default

# By default, instance and disk names will be of the form:
#   Master:     my-grid-mm
#     boot:     my-grid-mm
#     data:     my-grid-mm-data
#   Workers: my-grid-ww-<number>
#     boot:     my-grid-ww-<number>
#     data:     my-grid-ww-<number>-data
#
readonly MASTER_NODE_NAME_PATTERN="${CLUSTER_PREFIX}-mm"
readonly MASTER_BOOT_DISK_PATTERN="${CLUSTER_PREFIX}-mm"
readonly MASTER_DATA_DISK_PATTERN="${CLUSTER_PREFIX}-mm-data"

readonly WORKER_NODE_NAME_PATTERN="${CLUSTER_PREFIX}-ww-%d"
readonly WORKER_BOOT_DISK_PATTERN="${CLUSTER_PREFIX}-ww-%d"
readonly WORKER_DATA_DISK_PATTERN="${CLUSTER_PREFIX}-ww-%d-data"

# By default all hosts will be 4 core standard instances
# in the zone us-central1-a, running debian-7
readonly MASTER_NODE_MACHINE_TYPE=n1-standard-1
readonly MASTER_NODE_ZONE=us-central1-a
readonly MASTER_NODE_IMAGE=debian-7
readonly MASTER_NODE_DISK_SIZE_GB=500
readonly MASTER_NODE_SCOPE=https://www.googleapis.com/auth/devstorage.full_control

readonly WORKER_NODE_MACHINE_TYPE=n1-standard-1
readonly WORKER_NODE_ZONE=us-central1-a
readonly WORKER_NODE_IMAGE=debian-7
readonly WORKER_NODE_DISK_SIZE_GB=500
readonly WORKER_NODE_SCOPE=https://www.googleapis.com/auth/devstorage.full_control

# Specify the number of each node type
readonly MASTER_NODE_COUNT=1
readonly WORKER_NODE_COUNT=2

# Output file on the local workstation for logs
readonly SCRIPT_LOG_DIR=/tmp

This may have been fixed by https://github.com/GoogleCloudPlatform/solutions-google-compute-engine-cluster-for-grid-engine/pull/2, merged into master in June.
Note this repository has been marked as deprecated, along with a pointer to:
Create a Grid Engine cluster on Google Compute Engine


Fix failing raytracing unit test

Unclear why this worked before - setting caplog.at_level(logging.INFO) uses the correct logging level.
Further minor changes:

remove a spurious debug print out in a test
slightly rearrange the check for KeyError in raytraing:plot (asking for forgiveness..)

OK, thanks for the review!!


Formulate rule descriptions consistently

The majority of rule descriptions incorporated into the current version (v1.19.0) seems to be formulated as a sequence of (one or more) short sentences outlining the issue that triggered the rule, potentially extended by a direct recommendation towards the developer. The sentences are usually ended with a period, while inline code is sometimes surrounded by  ` characters.
Consider the following descriptions as an example:

ForbiddenVoid:  `Unit` should be used instead of `Void`.
ComplexMethod: Prefer splitting up complex methods into smaller, easier to understand methods.
AnnotationOnSeparateLine (from detekt-formatting): Multiple annotations should be placed on separate lines.
DuplicateCaseInWhenExpression: Duplicated case statements in when expression. Both cases should be merged.
InjectDispatcher: Don't hardcode dispatchers when creating new coroutines or calling `withContext`. Use dependency injection for dispatchers to make testing easier.

However, there are also various rules that deviate from this style as follows:

One-sentence descriptions are sometimes formatted without a period at the end...

LibraryEntitiesShouldNotBePublic: Library class should not be public
OptionalWhenBraces: Optional braces in when expression

In descriptions with multiple sentences, the last sentence is sometimes lacking the period...

FunctionOnlyReturningConstant: (...) is misleading. Consider declaring a constant instead

Sometimes, sentences are separated from each other using newlines:

ImplicitUnitReturnType: (...) return type.\nChanging the type (...)

Inline code is sometimes surrounded by ' characters or not surrounded at all:

NonBooleanPropertyPrefixedWithIs: Only boolean property names can start with 'is' prefix.
EqualsAlwaysReturnsTrueOrFalse: (...) implementation. For example this == other

Especially in detekt-formatting, many texts describe what the rule itself does instead of what the underlying issue is:

MaximumLineLength: Reports lines with exceeded length
NoTrailingSpaces: Detects trailing spaces

I am not trying to say that the first set of descriptions is "right" and the second set of descriptions is "wrong". In my opinion, however, it would make (console) reports more readable and pleasing to look at if all descriptions were given in a consistent manner. What do you think, would the introduction of a convention that deals with the description format be possible?

Thank you for taking the time to create this issue with all these samples! Detekt grew in an organic way. That makes that this kind of inconsistencies appear.
But for sure that's something that we could work on and improve. I see that you have a good idea of how this descriptions could be written and formatted. Could you write a small style guide and create a PR with it? Then, with that guide, we could review all the rules in detekt and make sure that them follow that style guide.
I think that .github/contrbuting is the perfect place to have this style guide.

Sure, I am happy to contribute. Thank you for your response!
I have written down a few guidelines that I think would at least be consistent. I am not quite sure if all of them are feasible. Please feel free to take a look at them and modify the document as you think is appropriate.

I went quickly over the rule sets and corrected the rule descriptions according to the style guide.

I'm closing this. Now we have our own style guide, thanks @pnq32 !! If there is any issue that doesn't follow the our style guide a new issue should be open pointing our the issue (or a PR fixing the issue directly).
Again, thank you @pnq32 :)


Fix intersphinx for SciPy 1.7.1 docs

pfnCI, test this please.

Jenkins CI test (for commit 7006934c20367d0c78318892a9b7aeb7ada0e46d, target branch master) succeeded!


Remove the argument to the intrinsic functions

They cause nothing but pain.

Proposed definitions:
  /// Returns the minimum width that this box could be without failing to paint
  /// its contents within itself.
  ///
  /// The height argument may give a specific height to assume. The given height
  /// can be null, meaning that the intrinsic width in an unconstrained
  /// environment is being requested. The given height should never be negative
  /// or infinite.
  ///
  /// Override in subclasses that implement [performLayout].
  ///
  /// If the layout algorithm is independent of the context (e.g. it always
  /// tries to be a particular size), or if the layout algorithm is
  /// width-in-height-out, or if the layout algorithm uses both the incoming
  /// width and height constraints (e.g. it always sizes itself to
  /// [BoxConstraints.biggest]), then the `height` argument should be ignored.
  ///
  /// If the layout algorithm is strictly height-in-width-out, or is
  /// height-in-width-out when the width is unconstrained, then the height
  /// argument is the height to use.
  ///
  /// This function should never return a negative or infinite value.
  double getMinIntrinsicWidth(double height) {
    return 0.0;
  }

  /// Returns the smallest width beyond which increasing the width never
  /// decreases the preferred height. The preferred height is the value that
  /// would be returned by [getMinIntrinsicHeight] for that width.
  ///
  /// Override in subclasses that implement [performLayout].
  ///
  /// If the layout algorithm is strictly height-in-width-out, or is
  /// height-in-width-out when the width is unconstrained, then this should
  /// return the same value as [getMinIntrinsicWidth] for the same height.
  ///
  /// Otherwise, the height argument should be ignored.
  double getMaxIntrinsicWidth(double height) {
    return 0.0;
  }

(The height ones are exactly symmetric.)


Web React: Use new Demo App partials

Description

https://github.com/lmc-eu/spirit-design-system/pull/1363
Additional context

Issue reference

https://jira.almacareer.tech/browse/DS-1231

coverage: 80.657%. remained the same
when pulling f0a170e29451ec63eba7c0252b81868c2dd90027 on refactor/web-react-use-new-demo-app-partials
into 14f702bcb82ff19bc52827645222e7e6d99f38c8 on refactor/demo-app-partials.


Some Qs about implementation

AMOS represents an innovative approach that leverages automated Mapping Generation and performance optimization to enhance the utilization of emerging hardware units like TensorCore. I have encountered some implementation challenges that I seek guidance on.

in computing compute latency, the intrinsic latency, a fixed value, can be approximated using hardware models. The resulting latency is then multiplied by the trip counts of sequential loops, which operate in a sequential manner not tethered to parallel cores. An inquiry arises: why is this sequencing necessary?
Operations like tiling, fusion, and other scheduling actions typically precede tensorization, leading to the generation of parallel code. Moreover, scheduling adjustments may introduce variations in the number of software iterations. How should this fluctuation be addressed, and what is the current efficacy of the mapping generation process?

When there are no enough cores for parallel execution, some loops still remain sequential. This is common for tensor computation.
Mapping takes three steps: compute transform, scheduling, tensorization. Compute transform changes the compute expressions according to hardware intrinsic, scheduling mutates the loop structure, tensorization replaces innermost loops with intrinsic. To make sure tensorization won't be affected by scheduling, we perform a pre-tiling step in compute transform step to keep a fixed number of iterations as innermost loops. For example, a GEMM:

for i
 for j
  for k
   ...

will be transformed into
for io
 for jo
  for ko
   for ii in range 16
    for ji in range 16
     for ki in range 16
      ....

As for the efficacy, mapping generation is fast (several seconds) but performance tuning is slow (tens of minutes).


Creating a Seamless World

I nipped and edited two lines from your code to make the world Seamless. Please check.

That is cool! I'll accept this change!
But first, could I just ask you a question (as it seems that you have experience with pygame):
Is there a way that the drawing performance could be increased? I would like to run this program with a 1000x1000 grid. Currently that results in less than 1 FPS...

There are some optimizations that can be done with pygame but the effect would be minimal. The most time consuming part of the code is the one using numba, which sweeps through all the array's cell for creating a new array. So, to speed up the processing, I can think of 2 ways to do it.

Use multi-threading to split the work on creating the newGrid. Though single-threaded CPU's will not benefit from this.

Optimize the code used for the function nextGenerationCalculation. I think there are a lot of ways to do this faster with numpy.

I am currently considering the no. 2. option. I will pull once more when I'm done.

I don't think that the problem lies in the the numba-code as it should be extremely fast now.
I benchmarked the main loop by adding the following code to benchmark:
t0 = time.time() #<-------------------------
display.fill((0, 0, 0))
for event in pg.event.get():
    if event.type == pg.QUIT:
        running = False
for row in range(ROWS):
    for column in range(COLUMNS):
        if life.grid[column][row]==1:
            pg.draw.rect(display, (255, 255, 255), (squareSide*column, squareSide*row, squareSide, squareSide))
text = font.render(f"FPS: {round(1/(time.time()-lastTime))}",True, (255,255,255))
lastTime = time.time()
display.blit(text, (0,0))
pg.display.update()
t1 = time.time()#<-------------------------
life.nextGeneration()
t2 = time.time()#<-------------------------
print("Drawing: ", t1-t0, "Next generation:", t2-t1)#<-------------------------

This game me the following results:
Drawing:  0.04296469688415527 Next generation: 0.00099945068359375
Drawing:  0.04297137260437012 Next generation: 0.0009984970092773438
Drawing:  0.042966365814208984 Next generation: 0.000997781753540039
The majority of the time is spent drawing. I believe the reason is getting the values from the numpy ndarray (I hypothesized this in the README).
By getting the ndarray in a bulk operation making the following changes:
t0 = time.time()
display.fill((0, 0, 0))
for event in pg.event.get():
    if event.type == pg.QUIT:
        running = False
pythonGrid = life.grid.tolist()#<-------------------------
for row in range(ROWS):
    for column in range(COLUMNS):
        if pythonGrid[column][row]==1:
            pg.draw.rect(display, (255, 255, 255), (squareSide*column, squareSide*row, squareSide, squareSide))
text = font.render(f"FPS: {round(1/(time.time()-lastTime))}",True, (255,255,255))
lastTime = time.time()
display.blit(text, (0,0))
pg.display.update()
t1 = time.time()
life.nextGeneration()
t2 = time.time()
print("Drawing: ", t1-t0, "Next generation:", t2-t1)

This small changed resulted in a doubling in speed:
Drawing:  0.02398085594177246 Next generation: 0.0009992122650146484
Drawing:  0.02198171615600586 Next generation: 0.0019989013671875
Drawing:  0.02198171615600586 Next generation: 0.0019989013671875
I do not know what could be done to shave of the remaining time drawing.

I'll merge the pull request in the meantime. Please open a new one if you have more code to contribute.
Thanks for the help so far! :)

I see.
I found a possible replacement for the whole drawing of the array.  Either way, here:
Instead of:

        for row in range(ROWS):
            for column in range(COLUMNS):
                if life.grid[column][row]==1:
                    pg.draw.rect(display, (255, 255, 255), (squareSide*column, squareSide*row, squareSide, squareSide))

Try:
game_surf = pg.surfarray.make_surface(life.grid)
game_surf = pg.transform.scale(game_surf, (WIN_SIZE, WIN_SIZE))
display.blit(game_surf, (0, 0))

Where WIN_SIZE is the dimension of your screen.


Document best practices and caveats around usage of exists/notexists joins

Usage of exists/notexists joins can introduce issues in data selection or manipulation. For example, some combinations of exists and notexists joins in the same select can impact performance. Another example is that usage of order by in an exists join does not work.
These and other behaviors should be documented so that developers can avoid these kinds of issues.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3f2875aa-c614-a807-90eb-247f8259cb1b
Version Independent ID: 95a6e7b3-2f3d-cdb2-64e6-7c610704ae78
Content: X++ data selection and manipulation - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/dev-ref/xpp-data-query.md
Service: dynamics-ax-platform
GitHub Login: @RobinARH
Microsoft Alias: robinr

@RobinARH Can you review this documentation request?

Bug 308970 has been logged to track this issue.

I added a link to this topic to the X++ data selection and manipulation overview topic:
Common misconception about Exists and Notexists joins
It will go live later today.


[WIP] Use unboxed sums for change / no-change tracking

…instead of pervasive ptrEq.

With the benchmarks I'm getting a lot of noise and rather reliable 2-3% speedup in HashMap.insert-dup.ByteString.

The last time I experimented with this idea, the performance was worse, but maybe things have changed. Or maybe there are differences between HashMap and Map that explain the difference.

FWIW, I think those old experiments used unboxed tuples with Int# tags rather than the (then bleeding edge) unboxed sums, but I don't know why that would make a difference, considering the way GHC implements unboxed sums.