python3Packages.quart: init at 0.16.2

Motivation for this change
Closes  #157341
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Closed in favor of https://github.com/NixOS/nixpkgs/pull/168268.

Help in reviewing and approving said PR is appreciated ;)


Can't send messages using Slack Bot

Everywhere I look I don't find where to get the Slackbot token. All I get is [this[(https://api.slack.com/methods/chat.postMessage)
If I use a bot token on the configuration token value I keep getting 404s.
Is the Slackbot feature working?

@PedroBrochado Sorry for the delay...
Looks like they are trying to discourage it. I can easily find it in one of my teams (very old) but not one of the new ones.  However, looks like you can still go directly to it.
https://.slack.com/apps/A0F81R8ET-slackbot
Try that and let me know if it works and I can update the README.


Unnecessarily deep indent on arguments following some paren-heavy code

Given this config, rustfmt insists, that this is the best way to format this code chunk:
for elem in try!(gen_epub_book::ops::parse_descriptor_file(&mut try!(File::open(&opts.source_file.1).map_err(|_| {
    gen_epub_book::Error::Io {
        desc: "input file",
        op: "open",
        more: None,
    }
})),
                                                           "input file")) {
    println!("{}", elem);
}

When I'd expect it to do something like this:
for elem in try!(gen_epub_book::ops::parse_descriptor_file(&mut try!(File::open(&opts.source_file.1).map_err(|_| {
    gen_epub_book::Error::Io {
        desc: "input file",
        op: "open",
        more: None,
    }
})), "input file")) {
    println!("{}", elem);
}

Also happens here:
fn write_content() {
    io::copy(try!(File::open(in_f).map_err(|_| {
        Error::Io {
            desc: "Content",
            op: "open",
            more: None,
        }
    })),
             w);
}

You could consider using fn_call_style = "Block". With your other settings, output will be like the following:
fn foo() {
    for elem in try!(gen_epub_book::ops::parse_descriptor_file(
        &mut try!(File::open(&opts.source_file.1).map_err(|_| {
                gen_epub_book::Error::Io {
                    desc: "input file",
                    op: "open",
                    more: None,
                }
            })),
        "input file"
    )) {
        println!("{}", elem);
    }
}
fn write_content() {
    io::copy(
        try!(File::open(in_f).map_err(|_| {
                Error::Io {
                    desc: "Content",
                    op: "open",
                    more: None,
                }
            })),
        w,
    );
}

That's ugly though

This no longer applies.

@kadiwa4 thanks for looking into this. I can confirm that when I use the default rustfmt configs I can't reproduce this issue. Here are the configs orginally listed:
max_width             = 160
ideal_width           = 128
fn_call_width         = 96
fn_args_paren_newline = false
fn_args_density       = "Compressed"
struct_trailing_comma = "Always"
wrap_comments         = true

Not all of them exist anymore. I don't think we have substitutes for ideal_width, and fn_args_paren_newline so lets not worry about those options anymore. In release 1.3.0 fn_args_density was renamed to fn_args_layout. struct_trailing_comma doesn't exist but trailing_comma does. So an updated config for the current rustfmt would be:
max_width      = 160
fn_call_width  = 96
fn_args_layout = "Compressed"
trailing_comma = "Always"
wrap_comments  = true

given this input:
fn foo() {
    for elem in try!(gen_epub_book::ops::parse_descriptor_file(&mut try!(File::open(&opts.source_file.1).map_err(|_| {
        gen_epub_book::Error::Io {
            desc: "input file",
            op: "open",
            more: None,
        }
    })),
                                                               "input file")) {
        println!("{}", elem);
    }
}

fn write_content() {
    io::copy(try!(File::open(in_f).map_err(|_| {
        Error::Io {
            desc: "Content",
            op: "open",
            more: None,
        }
    })),
             w);
}

fn foo() {
    for elem in try!(gen_epub_book::ops::parse_descriptor_file(
        &mut try!(File::open(&opts.source_file.1).map_err(|_| {
            gen_epub_book::Error::Io {
                desc: "input file",
                op: "open",
                more: None,
            }
        })),
        "input file"
    )) {
        println!("{}", elem);
    }
}

fn write_content() {
    io::copy(
        try!(File::open(in_f).map_err(|_| {
            Error::Io {
                desc: "Content",
                op: "open",
                more: None,
            }
        })),
        w,
    );
}


Italy Entry Updated

Italy updated as they are now publishing an activity file

This PR suggested a merge to the master branch. The change should have been applied to the dev branch. Therefore, this PR is being reverted and suggest applying to the dev branch.


Fix flaky test AwalaTest.deleteExpiredOnSetUp

tech.relaycorp.awaladroid.AwalaTest > deleteExpiredOnSetUp FAILED
    java.lang.AssertionError at AwalaTest.kt:87

https://github.com/relaycorp/awala-endpoint-android/actions/runs/2971016223/jobs/4757781102
https://scans.gradle.com/s/2mfrpujkqar7u/tests/:lib:testDebugUnitTest/tech.relaycorp.awaladroid.AwalaTest/deleteExpiredOnSetUp?top-execution=1

BTW, this happened in #265, so it may or may not be a regression introduced in that PR.

Fixed with https://github.com/relaycorp/awala-endpoint-android/pull/265


Sql value function

This fixes #92
Future work: we have a hardcoded copy of the value functions in our source, this will probably get out of sync someday, should we generate it from the postgres source?

@herwinw Yeah, thats a good idea - we should probably extract this from the Postgres source in the future.


LET return an object

ArangoDB Version:        3.6.2

Hi, this AQL returns ["12345"]
FOR doc IN TestCollection
RETURN doc._key

But this AQL returns [["12345"]]
LET d = (FOR doc IN TestCollection
              doc._key)
return d

Is that intended? I thought LET is just a variable

I'm getting the same behaviour. And it seems that if I try and do d[0] or FIRST(d) or d[**] at the end, it only returns the first item of the inner array, instead of spreading out the entire inner array as the returned rows as I would expect.
LET col = [{ a: 1 }, { a: 2 }, { a: 3 }, { a: 4}]

LET test = (FOR c IN col RETURN c)

RETURN test
// OR
RETURN test[**]
// OR
RETURN FLATTEN(test)

returns
[
  [
    {
      "a": 1
    },
    {
      "a": 2
    },
    {
      "a": 3
    },
    {
      "a": 4
    }
  ]
]

Hence, we don't get a regular list of docs as intended (and get no nice table display in the web view).

RETURN test[0]
// OR
RETURN FIRST(test)

returns
[
  {
    "a": 1
  }
]

Which can show in the web view, but its only the first row... so not what we were intending.
So these commands seem to actually not work as intended (as far as the end user might expect), because if we have an array that is 2-deep and we pull out the first element we expect to just get the full inner array back.
Is there any way for us to just get the regular flat list array?

Ah, just figured it out while finishing this off...
FOR ele IN test
  RETURN ele

I guess this makes sense in the way AQL works? AQL always expects RETURN to be called for each returned row, hence return just basically pushes items to the final returned array? So here we were returning the entire row as a single item, and when we called FIRST() it was actually calling it on the array of inner items, and not the final AQL returned array.

I don't think so. If you look at my example, I am RETURN doc.key, it should not be an array or object but the RETURN d gives me an array of array

The reason for this behavior is that the result of an AQL query always is an array.
if there is no FOR loop on the top-level of the query, there will be an implicit one (invisible) which will make the result go into an extra array.
That means
LET d = (subquery returning an array)
RETURN d

and
FOR d IN ...
  RETURN d

are not equivalent.
This behavior may be confusing, but we cannot change it without breaking downwards-compatibility for a lot fo queries.

Ok, that's makes sense. But I'm don't agree to make an array result implicitly without FOR. It should be up to AQL statement to ensure it returns an array if its a requirement. So I have to flatten my results before I RETURN, either this is not very clear in the docs.

Queries and subqueries always return an array, which is mentioned on the following documentation pages:

https://www.arangodb.com/docs/stable/aql/operations-return.html
https://www.arangodb.com/docs/stable/aql/examples-combining-queries.html
https://www.arangodb.com/docs/stable/aql/data-queries.html#data-access-queries

I can work around it, it's just a return without FOR,  an array is created , that is unexpected.


Apple M2 环境CMake 构建失败

环境：macbook air m2
Python 版本：3.10.13
参考教程执行，构建失败，报错日志如下：
-- Found Python: /opt/miniconda3/envs/wiring/bin/python3.10 (found suitable version "3.10.13", required range is "3.10...<3.11") found components: Interpreter Development Development.Module Development.Embed
WANRINGCannot find core_avx.so, using core_noavx.so instead.
FATALcore_noavx.so NOT found in /opt/miniconda3/envs/wiring/lib/python3.10/site-packages/paddle/fluid/
CMake Error at build/third_party/gflags/tmp/extern_gflags-mkdirs.cmake:6 (file):
  file failed to create directory:

    /third_party/gflags

  because: No such file or directory
Call Stack (most recent call first):
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:1790 (include)
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:4354 (_ep_set_directories)
  cmake/external/gflags.cmake:64 (ExternalProject_Add)
  cmake/third_party.cmake:27 (include)
  CMakeLists.txt:69 (include)

CMake Error at /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:3235 (message):
  No download info given for 'extern_gflags' and its source directory:

   /third_party/gflags

  is not an existing non-empty directory.  Please specify one of:

   * SOURCE_DIR with an existing non-empty directory
   * DOWNLOAD_COMMAND
   * URL
   * GIT_REPOSITORY
   * SVN_REPOSITORY
   * HG_REPOSITORY
   * CVS_REPOSITORY and CVS_MODULE
Call Stack (most recent call first):
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:4418 (_ep_add_download_command)
  cmake/external/gflags.cmake:64 (ExternalProject_Add)
  cmake/third_party.cmake:27 (include)
  CMakeLists.txt:69 (include)

-- Configuring incomplete, errors occurred!

@lishicheng1996 帮忙回复下

环境：macbook air m2 Python 版本：3.10.13 参考教程执行，构建失败，报错日志如下：
-- Found Python: /opt/miniconda3/envs/wiring/bin/python3.10 (found suitable version "3.10.13", required range is "3.10...<3.11") found components: Interpreter Development Development.Module Development.Embed
WANRINGCannot find core_avx.so, using core_noavx.so instead.
FATALcore_noavx.so NOT found in /opt/miniconda3/envs/wiring/lib/python3.10/site-packages/paddle/fluid/
CMake Error at build/third_party/gflags/tmp/extern_gflags-mkdirs.cmake:6 (file):
  file failed to create directory:

    /third_party/gflags

  because: No such file or directory
Call Stack (most recent call first):
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:1790 (include)
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:4354 (_ep_set_directories)
  cmake/external/gflags.cmake:64 (ExternalProject_Add)
  cmake/third_party.cmake:27 (include)
  CMakeLists.txt:69 (include)

CMake Error at /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:3235 (message):
  No download info given for 'extern_gflags' and its source directory:

   /third_party/gflags

  is not an existing non-empty directory.  Please specify one of:

   * SOURCE_DIR with an existing non-empty directory
   * DOWNLOAD_COMMAND
   * URL
   * GIT_REPOSITORY
   * SVN_REPOSITORY
   * HG_REPOSITORY
   * CVS_REPOSITORY and CVS_MODULE
Call Stack (most recent call first):
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:4418 (_ep_add_download_command)
  cmake/external/gflags.cmake:64 (ExternalProject_Add)
  cmake/third_party.cmake:27 (include)
  CMakeLists.txt:69 (include)

-- Configuring incomplete, errors occurred!

不好意思，对苹果M芯片的支持属于实验性质。仅在开发阶段进行了demo验证，未持续跟进paddle框架的更新。

环境：macbook air m2 Python 版本：3.10.13 参考教程执行，构建失败，报错日志如下：
-- Found Python: /opt/miniconda3/envs/wiring/bin/python3.10 (found suitable version "3.10.13", required range is "3.10...<3.11") found components: Interpreter Development Development.Module Development.Embed
WANRINGCannot find core_avx.so, using core_noavx.so instead.
FATALcore_noavx.so NOT found in /opt/miniconda3/envs/wiring/lib/python3.10/site-packages/paddle/fluid/
CMake Error at build/third_party/gflags/tmp/extern_gflags-mkdirs.cmake:6 (file):
  file failed to create directory:

    /third_party/gflags

  because: No such file or directory
Call Stack (most recent call first):
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:1790 (include)
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:4354 (_ep_set_directories)
  cmake/external/gflags.cmake:64 (ExternalProject_Add)
  cmake/third_party.cmake:27 (include)
  CMakeLists.txt:69 (include)

CMake Error at /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:3235 (message):
  No download info given for 'extern_gflags' and its source directory:

   /third_party/gflags

  is not an existing non-empty directory.  Please specify one of:

   * SOURCE_DIR with an existing non-empty directory
   * DOWNLOAD_COMMAND
   * URL
   * GIT_REPOSITORY
   * SVN_REPOSITORY
   * HG_REPOSITORY
   * CVS_REPOSITORY and CVS_MODULE
Call Stack (most recent call first):
  /opt/homebrew/Cellar/cmake/3.28.3/share/cmake/Modules/ExternalProject.cmake:4418 (_ep_add_download_command)
  cmake/external/gflags.cmake:64 (ExternalProject_Add)
  cmake/third_party.cmake:27 (include)
  CMakeLists.txt:69 (include)

-- Configuring incomplete, errors occurred!

不好意思，对苹果M芯片的支持属于实验性质。仅在开发阶段进行了demo验证，未持续跟进paddle框架的更新。

后续还会跟进么？
我想修复这个错误，可以给些建议么？

你好，可以尝试切换 Paddle 到支持 apple metal 最新提交的时间
从错误上看是Paddle的更新导致，可以对比下 PaddleCustomDevice/backends/mps/cmake/paddle.cmake  和 PaddleCustomDevice/backends/npu/cmake/paddle.cmake，以及 PaddleCustomDevice/backends/mps/kernels 下各个 kernel 是否与 npu 一致

@tongda 请问还有问题吗？

2周未有新的comments，关闭此issue。如果您有新的问题，可以open新的issue提问，谢谢！


Fixed Issue #267 & #269

Fixed typo errors in chapter 02 - Get Started.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you!


Could Not Find C:\Users\bhara\Downloads\apk-decompiler_1.1\apk-decompiler\jad\classes-dex2jar.jar

I'm getting this when executing go.bat

I placed the wrong file in the source folder. Just realized.


Patched with genshin 3.5

The game states you should launch the game from the launcher and then closes.

Try run unlocker as administrator. It works for me

Runs fine for me.

Turns out it was launching a wrong game EXE after the update. had to run setup again


Add ability to set different Nutch crawl configurations

Nutch crawl configuration set to default and number_of_rounds set to two in all crawls:
https://github.com/ContinuumIO/memex-explorer/blob/master/app/crawls.py#L47

[ ] Change default number of rounds to one.
[ ] Write nutchpy script to use a continuously running loop that is interruptible with an API call.
[ ] Nutch crawl script could be able to select the folder with the configuration to use.

Open separate issue tasks: #134, #135, #136

Still relevant?


Seed 3 is omitted in plot_against_baseline.py?

https://github.com/microsoft/oac-explore/blob/715db5a2f0b8fead865fafc522d5820d477a7ed3/plotting/plot_against_baseline.py#L130
Is there a reason seed 3 is omitted?

Oh this was only for debugging. One of the run on my local computer fails because the machine ran out of memory and I was trying to figure out which one it was.
I have updated the code to include the result for seed 3.


Why logout endpoint doesn't require authorization?

What sense is there to have logout, that doesn't check whether it actually logged out an user?

@Nicarim Do you have any trouble with logout?

My mobile developer expected to get error when token is invalid or it wasnt
provided (i.e. Lost state) but instead they got success which wasnt what
they wanted (they expected to get error so they could redirect user to log
in screen)
pon., 22.02.2016, 14:55 Egor użytkownik<EMAIL_ADDRESS>napisał:

@Nicarim https://github.com/Nicarim Do you have any trouble with
logout?
—
Reply to this email directly or view it on GitHub
https://github.com/Tivix/django-rest-auth/issues/174#issuecomment-187185595
.

@Nicarim Really i don't understand which business logic you want to write around logout.
That is logout view, at any situation if it return success, mean data about your session(or token) is successfully deleted from server.
Your mobile developer can redirect to login screen always after logout. You also must remember some views can let to users get access to data without be logged in.
If you want to know status of user you can get data from /rest-auth/user/ if user not login you get error.

It says success even when there is no token at all being removed (or not
even being provided). I just found it misleading, that it says there was a
success when nothing even was done. My dev wouldnt know if they made a
proper logout or not.
pon., 22.02.2016, 15:33 Egor użytkownik<EMAIL_ADDRESS>napisał:

@Nicarim https://github.com/Nicarim Really i don't understand which
business logic you want to write around logout.
That is logout view, at any situation if it return success, mean data
about your session(or token) is successfully deleted from server.
Your mobile developer can redirect to login screen always after logout.
You also must remember some views can let to users get access to data
without be logged in.
If you want to know status of user you can get data from /rest-auth/user/
if user not login you get error.
—
Reply to this email directly or view it on GitHub
https://github.com/Tivix/django-rest-auth/issues/174#issuecomment-187205859
.

If token not provided, it success deleted not provided token. If provided wrong token, it success delete not provided token. What wrong?
I though more better additionally use oAuth2 package for auth on mobile devices.

I thought about this too.  In any case, after logout your token won't exist, so no point in having a nuanced success response about whether that token was actually valid in the first place.  It's gone.

I find this highly counterintuitive. If it's not changed, it should at least be explained in the documentation. Here's a stackoverflow question about this exact issue.
http://stackoverflow.com/questions/37744963/drf-django-rest-auth-how-to-expire-or-delete-token?noredirect=1#comment62962135_37744963

IMHO Login is not required to logout is  to handle session based authentication.
If you are are using Token Based Authentication you must pass Authorization Headers to delete the token.

@haakenlid
More better if you will write unittests for login/logout around your Auth backend. And that will help to you more better understand how is works login and logout with your Auth backend.
Anyway if you Auth by token and then trying logout, you removed that token from your app, but server still have it. After that you can't get access to site, and that not big difference have server token linked to your user account or not. And you still can get new token by login again

I concur with this point being an issue. Websites are often an integration of code of many sources. What about a oddly-placed button whose link has been wrongly constructed to point to "/auth/logout"? If this API endoint also works with GET, we'll get a free logout with everything it implies, just by mistake.

@onekiloparsec
How much often in your projects, you can see links on wrong url? I though if link is broken that is already problem, and if that link to wrong place that is problem too.

That's not the point. We make APIs independently from usages. Logout, having potentially important effects, should be something requiring "authorization"

IMO the reasonable behavior is that (1) logout should not strictly require authentication, but (2) should return information whether the logout did successfully delete a token.

This is largely based on my experience in production with the following scenario: my app is on two devices and I logout on one of them.  Requiring authorization on logout could make logging out on the second device effectively impossible (given on how you design your app) - OR - you have to decide what to do when that logout operation fails (and i suspect the decision will be to treat the user like they're unauthorized, i.e. logged out)

It is good to know that your code is operating as intended and this information would be useful in ensuring everything is set up properly.

Overall (2) won't necessarily help you discriminate between whether (A) the developer messed up or whether (B) the token has been deleted at a previous time/place.  But you can easily test and ensure against (A) and you should expect (B) in the wild.
@onekiloparsec requiring authorization as a deterrent to front end mistakes is a non sequitur
@haakenlid documentation would be good.

@Nekothrace

That app not just for token auth.
If you logout you don't need login again for logout on second device.
Feel free override logout/login behavior in your application.

If token not provided, it success deleted not provided token. If provided wrong token, it success delete not provided token. What wrong?

I would expect that when the API receives an invalid token (or an additional logout call) that the response would be a '404 Resource Not Found'. Which would be more indicative than a '200 Success', since in reality the operation could not have been performed and would be misleading the caller into believing they had a valid Token in the first place and moreover that logging out with the same token succeeds every time the endpoint is called (which is odd, it should only succeed once).
Missing header or parameter fields should respond with 400/404/412/422 error code responses.


Create a logo for Design System Day 2024

Deadline for branding 12 April 2024

What
Create a logo and accompanying look and feel/ identity for Design System Day(s) 2024. The logo and identity will be used across a range of materials, including:

Attendee stickers
Speaker / facilitator stickers
Organiser / volunteer stickers
Event booklets
A1 A board
Pull up banners
2x A0 prints
Digital event profile pic
Digital event registration pages
GDS blog
GDS Twitter
GDS LinkedIn
Slack
Mailchimp

Steps/ done when

[ ] Potential themes discussed and chosen
[ ] Rough ideas presented to squad for feedback
[ ] Idea chosen
[ ] Design of logo and and supporting assets
[ ] Squad feedback
[ ] Final artwork

Kick-off meeting notes
Brand outline (async team workshop)


Various small improvements to the PDF

Description
Closes #451 and #477.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[x] Code is formatted according to CONTRIBUTING.md
[x] Self-reviewed the diff

thank you!


TemplateFactory.prototype.makeComponentTemplate breaks component-name-based CSS styling

This is a:

[x] Bug Report
[ ] Feature Request
[ ] General Query

My version of UI-Router is: 1.0.0
Bug Report
Current Behavior:
When routing to components, the constructed templates are prefixed with "x-". As such, stylings that rely on component names break. I.e: my-component { color: red; } won't apply to <my-component /> because it's been renamed to <x-my-component />.
Expected Behavior:
The component should not be renamed so that styles apply as expected.
Link to Plunker that reproduces the issue:
https://plnkr.co/edit/NKTlKYBCtKG6xg0Oqsgd?p=preview

After thinking about this for a bit, I think we should prefix with x- only when the component name starts with x- or data-

Closed by https://github.com/angular-ui/ui-router/commit/60b9ef923c701c831c66a145ebae36039782cf68


MetadataFile, as a decorator of PackageOutput, should behave on close()

Apparently MetadataFile does it's mean job during the call to save() but I believe it would simplify many things to:

move this behaviour to close()
pass the digest and naming strategy to its constructor

Like this, there will be no need to explicitly call save in Repository: the repomd.xml file would be updated as soon as the wrapped metadata file is closed.
Next step would then be to move the content of the save method of Repository to its close method too, to homogenise APIs.

@g4s8/z please, pay attention to this issue

The job #99 assigned to @g4s8/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

@g4s8 ping, we have #105 waiting for this. You can assign me if you want

@0crat assign @paulodamaso

@0crat assign @paulodamaso  (here)

@g4s8 The job #99 assigned to @paulodamaso/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job

@0crat/z I see that you unassigned this issue; the order is still assigned to @paulodamaso/z though; to cancel the order use refuse, as in §6

@paulodamaso/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@0crat out

@0crat out (here)

@olenagerasimova GitHub issue is still open, won't close

@0crat wait

@paulodamaso @victornoel I'm closing this issue as I'm planning to reorganize Repository, MetadataFile and other MetadataFile abstractions, I do not see them implementing Closable after the reorganization.
@sereshqua please do not report bad quality on this issue as the job was actually done

@sereshqua/z please review this job completed by @paulodamaso/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat quality good


[Popover] Fix update position action

[X] I have followed (at least) the PR section of the contributing guide.

Fix #16901

@netochaves Could you add a failing test case? This should help to prevent similar regressions in the future.

@oliviertassinari Sure! It will fail if the popover prop open is false, do you know another case?

@netochaves Thanks!


Use an options object for extensibility

This is likely that more options will be introduced in the future (see #4). Therefore I recommend passing an object to the constructor to make it easier to extend the API.

I know how to do this, but I'm wondering what folks might want to customize. Ideas:

The left / right alignment of the menu
Erm...

Regarding supporting non-button element types as menuitems, I think we should just allow that or not, but it would mean scripting the Enter / Space key events of course.

Regarding extensibility, you don’t really know where you library is going to go. Today, there might be no need for options, but maybe in the future there will be. This is a mistake I made in a11y-dialog; I should have started right away with accepting an object in the constructor. It will be the case in v4.
Let’s move the discussion about selectors in #4.

Now handled for the checkable option.


Potential problems

Edit: turned it into a general thread instead

The AGZ spreadsheet mentions only one filter for the value head. In this implementation, two filters are used. Any reason to it? I don't think it's going to have a big impact, but I'm just putting it out there.

The target policies that are created during simulated games are taken from the prior probabilities p. These are calculated by the neural net.  From the AGZ cheatsheet I believe that the target policies should instead be the search probabilities, which are given by the number of visits of a move and the temperature parameter.

Some notes:

During MCTS search, there are lots of zero Q-values and often patches of Q-values that are almost 1 appear. (This might just be due to a bad network)

The MCTS batched search yields more Q-values, but the search depth will be considerably lowered. Chosen moves are only at max depth 4 from the current position and usually 2 or 3. Running 64 simulations with batch size 1 can give chosen moves with up to depth 66 from the current position, but of course, it will be slower. Unsure on what is a good balance. Hard to tune.

What do you mean 2 filters ? The value head is one conv, with batch normalization and one dense layer:

Not sure about that. I imagine the cheat sheet you are referencing is this:
https://medium.com/applied-data-science/alphago-zero-explained-in-one-diagram-365f5abf67e0
If you would use number of visits and temperature, because temperature is most of the time 0, you policy target would be most of the time all 0 but one 1. Not sure it is desirable. I tried looking at the paper again, but this point is not perfectly clear to me.
The best segment I could find is this:

Evaluator To ensure we always generate the best quality data, we evaluate each new neural
network checkpoint against the current best network f θ ∗ before using it for data generation. The
neural network f θ i is evaluated by the performance of an MCTS search α θ i that uses f θ i to evalu-
ate leaf positions and prior probabilities (see Search Algorithm).

Not sure I understand the problem here. The Q-value is probably wrong yes, but the question is why.
What do you mean patches of 1 ? The Q-value of moves close to each other are the same ? It does not seem too wrong for a naive player (the details are not yet seen)

I used MCTS_BATCH_SIZE=8 personnally. It is the same mentionned in the paper.

Positions in the queue are evaluated by the neural network using a mini-batch size of 8; the
search thread is locked until evaluation completes. The leaf node is expanded and each edge (s L , a)
is initialised to {N (s L , a) = 0, W (s L , a) = 0, Q(s L , a) = 0, P (s L , a) = p a }; the value v is then
backed up.

I am not sure why they use threaded search to be honest instead of sequential because, it is a deterministic search, and everything uses the same tree. You do win some performance by using multiple cores I guess, but you also might end up trying to expand the same node multiple times (especially when temperature is zero). I expected that could be a source of problems (because in this implementation I always expand different nodes in the tree search), but I don't think expanding too greedily would be a problem in the long run.


Feature/flutter dart nullsafety

Some strangeness here from legacy dart
Some quicker fixes implemented near the tail end of commits...
If it works
Significant refactoring work should probably have been undertaken before null safety (or any other changes)
Break out into separate files (circular)
Should probably refactor linear more later.

or rewrite it faster
minimal tests


No Video Capture Device Error rs2_create_device

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{  D435 }

Firmware Version
(Open RealSense Viewer --> 2.53.1)

Operating System & Version
Linux (Ubuntu 22.04 LTS)

Kernel Version (Linux Only)
(5.15.0-56-generic)

Platform
PC (x86 CPU)

SDK Version
{ 2.53.1}

Language
{C/C++ }

Segment
{others }

Issue Description
I have been attempting to install on a new Ubuntu distro 22.04 LTS, however when running my program which previously worked on Ubuntu 20.04 I find the following error being thrown:
RealSense error calling rs2_create_device(info_list:0x555e5b7a8c00, index:1):
    /dev/video0 is no video capture device Last Error: Invalid argument

When I go to list my devices out for my computer I see the following and indeed the Depth camera does not correspond with /dev/video0
$: v4l2-ctl --list-devices
ipu3-imgu (PCI:0000:00:05.0):
	/dev/video0
	/dev/video3
	/dev/video4
	/dev/video5
	/dev/video6
	/dev/video7
	/dev/video8
	/dev/video10
	/dev/video12
	/dev/video13
	/dev/media1

Intel IPU3 CIO2 (PCI:0000:00:14.3):
	/dev/video1
	/dev/video2
	/dev/video9
	/dev/video11
	/dev/media0

Intel(R) RealSense(TM) Depth Ca (usb-0000:00:14.0-1):
	/dev/video14
	/dev/video15
	/dev/video16
	/dev/video17
	/dev/video18
	/dev/video19
	/dev/media2
	/dev/media3

I have tested out the realsense-viewer and recorder which seems to work fine. I only have one device connected. I have also checked my code and found that the problem starts when I query for the devices. specifically looping through any connected devices:
for (rs2::device &&dev : ctx.query_devices()){
...

I have seen a similar issue from here  #10072. I have checked for memory leaks which don't seem to present. I have seen that they used docker (which currently I am not using). Is there any way to get this fixed short of a custom build? Thanks.

Hi @yeric1789  If you are only using one camera, an alternative to looping thorugh all connected devices may be to query for the first depth sensor that can be detected.  For example in C++:
auto sensor = selection.get_device().firstrs2::depth_sensor();

OK thanks that was able to fix it.

That's great to hear, @yeric1789 - thanks very much for the update!


other port number?

Hi,
would it be possible to add an option to use a port number other than the default, like 8080?
Best regards,
Victor

Hey, since I'm using the HUE API that uses HTTP it's not possible. Is there any particular reason you need to use a different Port? I can't do UDP over a browser because it requires hue API v2 if that is what you are looking for.

I'm using Home Assistant emulated HUE. My Home Assistant runs on port 80, so I've set the emulated hue to use port 8080.

Unfortunately, the Hue controller will not work with the emulated HUE because my controller uses Philips Hue API. You need to connect to a different API if there exists one for the emulated HUE which I don't know much about. You are always welcome to fork the repository and make your own implementation. :)


fix:Added extra test cases for 'arguments-optional' problem

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #38774

I have added extra test cases that don't allow any possibility of solution creation without actual input addition. The previous test case could easily be hacked as it always gives answers either 5 or undefined.

@moT01 , @Sky020 : Can you please review the PR and let me know if it's fine.

Hi @rajat641
Thanks for your interest and excitement.
We request you to bear with the mods and respect their time, they are volunteers like you 🙂, and will surely get back to you with the feedback.
Thanks for your patience, and meanwhile please I encourage you to go ahead and work on other help wanted issues.

Hi @raisedadead , I didn't know that you were a part of a really small team and you had other things to do. I will take care of it in the future. I appreciate your response.

:sparkles: :sparkles: AWESOME! LGTM. :sparkles: :sparkles:
Thanks @rajat641, for this pull request and contributing to the code-base for the first time.
We will be looking forward for more contributions in future.
Cheers and happy contributing!


Why are addresses 32 bytes?

Addresses are specified in code as 32 bytes https://github.com/aionnetwork/AVM/blob/master/org.aion.avm.api/src/avm/Address.java#L11
But documentation for FastVM states addresses are 128-bits. Documentation for AVM does not specify bit length.

Where does the FastVM doc state that the addresses are 128-bit?  Here, it defines them as 32 bytes:  https://github.com/aionnetwork/aion_fastvm/wiki/Specifications
This isn't specific to either VM but a defined constant of the Aion network.

Thank you. I was confused with FastVM documentation. No problem here.


Compare advantages and test on whole set

Compare our vs tensorflow advantages for the same model, in order to make sure very small numbers are reasonable.
Test our code on the whole dataset and not only 100 datapoints.

It was due to ART returning labels instead of confidence scores. It is now fixed with the new version, although the advantage score for the rule-based attack doesn't make sense still because there we still have zeroes and ones.


fix Bug: KeyError: 'text' Corresponding to issue #296

Solution for issue #296
File data_juice/config/config.py lines 418-429 did not consider the situation when arg: text_key was initialized to 'text', resulting in arg: text_key not being updated properly and always being initialized to the value of 'text'
Thus, I just supplement the set of "text_key".

Original Code:
    for op in cfg.process:
        for op_name in op:
            args = op[op_name]
            if args is None:
                args = {
                    'text_key': text_key,
                    'image_key': cfg.image_key,
                    'audio_key': cfg.audio_key,
                    'video_key': cfg.video_key,
                }
            elif args['text_key'] is None:
                args['text_key'] = text_key
                args['image_key'] = cfg.image_key
                args['audio_key'] = cfg.audio_key
                args['video_key'] = cfg.video_key

Fixed:
    for op in cfg.process:
        for op_name in op:
            args = op[op_name]
            if args is None:
                args = {
                    'text_key': text_key,
                    'image_key': cfg.image_key,
                    'audio_key': cfg.audio_key,
                    'video_key': cfg.video_key,
                }
            elif args['text_key'] is None:
                args['text_key'] = text_key
                args['image_key'] = cfg.image_key
                args['audio_key'] = cfg.audio_key
                args['video_key'] = cfg.video_key
            if text_key:
                args['text_key'] = text_key
                args['image_key'] = cfg.image_key
                args['audio_key'] = cfg.audio_key
                args['video_key'] = cfg.video_key

            op[op_name] = args

Hi @shiweijiezero , thanks for your contribution!
You're correct👍🏻. According to your report and modification, we found out that a previous PR #165 made the code snippet useless because args for each OP are initialized by the default args and command line args before.
https://github.com/modelscope/data-juicer/blob/094440bbf01636cc62aee8e214b203df2bfc756d/data_juicer/config/config.py#L418-L434
In the data-juicer config modules, args of OPs are expected to be overwritten in this priority order: default args -> config args -> command line args. Following this rule and based on your modification, we suggest you continue to fix this bug completely by:

swapping these two lines 271 and 272 of code. Function init_setup_from_cfg updates OP args from config files and function update_op_process updates them from command line args. So we need to apply init_setup_from_cfg then update_op_process.
https://github.com/modelscope/data-juicer/blob/094440bbf01636cc62aee8e214b203df2bfc756d/data_juicer/config/config.py#L269-L273

decoupling the updates for text/audio/image/video keys. These keys are updated only by the changes of text_key before, which would cause the same issue you met on audio/image/video keys. So we suggest you modify this part (lines 425 to 429) of the code like the below:

            ......
            else:
                if 'text_key' not in args or args['text_key'] is None:
                    args['text_key'] = text_key
                if 'image_key' not in args or args['image_key'] is None:
                    args['image_key'] = cfg.image_key
                if 'audio_key' not in args or args['audio_key'] is None:
                    args['audio_key'] = cfg.audio_key
                if 'video_key' not in args or args['video_key'] is None:
                    args['video_key'] = cfg.video_key
            op[op_name] = args
            ......

Thanks for your contribution again! Feel free to discuss the fix suggestions with us if you have any further considerations!

Yeah,
Following your suggestion, everything seems to be OK.
And I had committed it again.

One last thing, you might need to apply pre-commit checking according to coding style doc.


tried using your example prompt and got an error for destination argument

tried a couple other things like a directory but nothing works

running without the parameter gives this error

Try removing the backslash ()


It is not sending either heartbeat events or regular tracking events when the app is closed.

Your Environment

Plugin version: 5.2.4
Platform: Android
Device OS version: Android 14
Device manufacturer / model: Motorola g53
XCode version:
Capacitor info (npx cap doctor)
Plugin config provided to #ready:

iniciarPLuginLocalizacao() {
      const token = localStorage.getItem('token');

      BackgroundGeolocation.ready({
        url: '***',
        headers: {
          "Content-Type": "application/json",
          "Accept": "application/json"
        },
        authorization: {
          strategy: "JWT",
          accessToken: token ? token : '',
        },
        params: {
          latitude: this.convite.latitude,
          longitude: this.convite.longitude,
          motorista_id: this.convite.motorista_id,
          user_id: this.convite.motorista_id,
          veiculo_id: this.convite.veiculo_id,
          status: this.convite.status,
          pedido_id: this.convite.pedido_id,
          pedido_detalhe_id: this.convite.pedido_detalhe_id,
          data_hora: this.convite.data_hora,
          evento: this.evento + '-' + this.atividade,
        },
        autoSync: true,
        desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_NAVIGATION,
        logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
        distanceFilter: 5000,  /// versao 1.0.7
        httpTimeout: 180000,
        stopOnTerminate: false,
        startOnBoot: true,
        preventSuspend: true,
        debug: false,
        disableElasticity: true,
        showsBackgroundLocationIndicator: false,
        backgroundPermissionRationale: {
          title: "Permita que o {applicationName} acesse a localização o tempo todo deste dispositivo mesmo quando fechado ou não em uso.",
          message: "Este aplicativo coleta dados de localização para permitir o registro de suas viagens ao trabalho e calcular a distância percorrida.",
          positiveAction: 'Mudar para "{backgroundPermissionOptionLabel}"',
          negativeAction: 'Cancelar'
        }
      }).then((state) => {
        this.ready = true;
        this.enabled = state.enabled;
        BackgroundGeolocation.start();
        BackgroundGeolocation.changePace(true);
        this.addEvent('State', state);
      }).catch((err) => console.log('Erro ao iniciar o Servico', err));
    }

Expected Behavior
"It was expected that the app would send both heartbeat and location events even when the app was closed. This used to happen before, and it didn't work last week, but since 2023 it had been working normally."
Actual Behavior
"It is not sending either heartbeat events or regular tracking events when the app is closed."
Steps to Reproduce

Context

Debug logs

Logs
PASTE_YOUR_LOGS_HERE

debug: false,

See wiki “Debugging”.  The first thing to do, before seeking assistance, is set debug: true so you can hear debug soundFX.  Learn to observe the plug-ins incredibly verbose logs.  Go outside and move at least 200 meters after terminate.


fix: replicaSet.enabled

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Thanks for the contribution, before continue, you need to sign your existing commits, you can find custom instructions in the “Details” link from the below DCO check, also you should increment the chart version in the Chart.yml according to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

@iamcc Actually you can close this PR as this change has been already merged (https://github.com/helm/charts/pull/10346)


auto_increment_type configration not working

While passing auto_increment_type, still it is creating major version. Below is code:

name: Create Release
id: create_release
uses: zendesk/action-create-release@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
auto_increment_type: minor
draft: false
prerelease: false

@PrateekKhatri I had a similar error and found your report when looking for a fix.
I just noticed that setting tag_schema: semantic seems to make it work for me.


Pass binary filename to sqlite3_open

Closes https://github.com/elixir-sqlite/exqlite/issues/277
This looks like it's your issue since Elixir strings at UTF-8 encoded. But I have to admit I'm not sure why it was latin-1 before. So I might be stepping on a landmine without knowing it.

Ok I learned very quickly why it was ERL_NIF_LATIN1 before. It's because ERL_NIF-UTF8 is new. So instead of passing it as a charlist I pass it as a binary and then convert it to a proper null terminated string inside the nif.

i'm pretty sure the failures are race conditions because they were not touched in this pr

I guess it's not a race condition =(

I'll take a look at this later in the evening.

This may be an issue with how the filesystem represents utf8 characters in windows. I'm not a windows dev, but I think we'll need to dig in to wchar stuff for the filesystem. I suspect it's utf16.

@greg-rychlewski it's been a while, can you try re-running the CI. I can't see where to kick it off on my end.

@warmwaffles done


Create Failed Could not unzip uploaded file. Error Code: InvalidParameterValueException

Not sure how to proceed with this, I've tried changing launch parameters but can't seem to get anything to work.
2020-02-05 12:56:14 UTC-0500 |
lambdaEmailNotification |
CREATE_FAILED |
Could not unzip uploaded file. Please check your file, then try to upload again. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: cdda5ef8-7b9d-4eb5-96f8-cf0e28e461f9)
-- | -- | -- | --

Had to do with permissions on the S3 bucket. After bucket creation I went to permissions , access control list and just made it open as read only to public.


  Just remove the Closes: #XXX line!
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >  --

## What is the purpose of the change

As part of getting osmoutils into its own go.mod, makes its store tests and module accounts test no longer depend on integrated osmosis testing. Instead we directly setup a custom store for store tests, and directly wire an auth keeper for module account testing.

What remains to get osmoutils into its own go.mod is:

- [ ] Move osmoassert from app/apptesting/osmoassert into osmoutils/osmoassert
- [ ] Make store_test no longer use twaptypes, as "place holder proto message thats not sdk.ProtoDec"

I plan to do those two in separate PRs.

These helpers in `noapptest` made here should suffice for also enabling us to put `x/downtime-detector` and `x/epochs` into their own go.mod.

## Brief Changelog

No public facing change, just alters tests.

## Testing and Verifying

The same tests still pass, just without importing osmosis repo.

## Documentation and Release Note

  - Does this pull request introduce a new feature or user-facing behavior changes? no
  - Is a relevant changelog entry added to the `Unreleased` section in `CHANGELOG.md`? no
  - How is the feature or change documented? N/A

Woah, I wrote a description for this PR. Must have had some issue with it not getting into github, sorry about that
For future ref:
This PR is part of moving osmoutils into its own go.mod. osmoutils depended on the osmosis app for wiring an auth keeper, and a custom store w/ a ctx.
This PR makes helpers to make ctxs' more easily with no integrated osmosis app. Its expected to be able to use this in x/epochs and x/downtime-detector as well. unfortunately to wire the auth keeper, we also had to wire params, which took many lines of code.
What remains to migrate osmoutils:

[ ] move osmoassert into an osmoutils sub-folder
[ ] Change the twaptypes import in tests, to be any other proto message in SDK, thats not "sdk.ProtoDec"


add(plugins): tailwindcss-container-query

Name
Link

tailwindcss-container-query
Resource link here

A plugin that provides CSS Container Queries for tailwindcss.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

Can you remove that Content header?

I didn't add it. It is adding automatically every time when I save vscode. I managed to delete it by editing it with notepad.

the icon is corrected now

It's one of your VSC extensions. Thanks!


[OGNL-102] Improves performance when null was returned

Improves performance of chained expressions in case if the root is null
Refs OGNL-102

@davoustp @harawata @quaff could you take a look? this should improve performance a bit, it's in relation to https://github.com/jkuhnert/ognl/pull/138 and the JIRA ticket.

Hi @lukaszlenart ,
I'm sorry about the slow response (as always)!
So, is root the only concern here?
With the following test, for example, the for-loop is still evaluated for the second node and the similar exception is thrown :

ognl.OgnlException: source is null for getProperty(null, "key2")

public void testNullHnadling() throws Exception {
  OgnlContext context = (OgnlContext) Ognl.createDefaultContext(null, new DefaultMemberAccess(false));
  Map<String, Object> root = new HashMap<>();
  root.put("key1", null);
  String expr = "key1.key2.key3";
  assertNull(Ognl.getValue(expr, context, root));
}

Right, but if I did that on children level in the for loop a lot of tests have started to fail, especially this one

Yes, it will change the designed behavior and @davoustp seems to be aware.
I'll just show some tests that emphasizes the difference in behavior.
If these results match @davoustp 's expectation, this PR should be fine.
public void testNullValue() throws Exception {
  OgnlContext context = (OgnlContext) Ognl.createDefaultContext(null, new DefaultMemberAccess(false));
  Map<String, Object> root = new HashMap<>();
  root.put("key1", null);
  String expr = "key1.key2.key3";
  assertNull(Ognl.getValue(expr, context, root)); // FAIL : OgnlException
}

public void testEmptyRoot() throws Exception {
    OgnlContext context = (OgnlContext) Ognl.createDefaultContext(null, new DefaultMemberAccess(false));
    Map<String, Object> root = new HashMap<>();
    String expr = "key1.key2.key3";
    assertNull(Ognl.getValue(expr, context, root)); // FAIL : OgnlException
}

public void testNullRoot() throws Exception {
    OgnlContext context = (OgnlContext) Ognl.createDefaultContext(null, new DefaultMemberAccess(false));
    Map<String, Object> root = null;
    String expr = "key1.key2.key3";
    assertNull(Ognl.getValue(expr, context, root)); // PASS
}

Changes will be moved into #155


[BUG] Do not require "admin_identifiers" when creating event linked to group/s in Client APIs

Describe the bug
Groups BB fails to create event linked to group/s because of requirement in the post body for admin_identifiers field.
To Reproduce
Try to create event from group in UIUC app. The request fails.
Expected behavior
A user is able to create event linked to group/s without error. And admin_identifiers not to be required for the Client APIs.
Screenshots

Additional context

Maybe this is a consequence of #408 but the field admin_identifiers should not be required for the Client APIs

Two examples of request / response pairs:

Request 1:
POST: https://api-dev.rokwire.illinois.edu/gr/api/group/05073b36-4920-432f-a1ec-7ca06275a013/events/v3

Body:
{
  "event": {
    "id": null,
    "name": "Group Event 14 20240126",
    "description": "test group event 14",
    "instructions": null,
    "image_url": null,
    "event_url": null,
    "timezone": "Europe/Sofia",
    "start":<PHONE_NUMBER>,
    "end":<PHONE_NUMBER>,
    "all_day": false,
    "event_type": "in-person",
    "location": {
      "id": null,
      "latitude": 40.101839,
      "longitude": -88.225389,
      "name": "Art E Annex, Studio 1",
      "description": null,
      "building": "Art E Annex, Studio 1",
      "fullAddress": null,
      "address": null,
      "city": null,
      "state": null,
      "zip": null,
      "floor": null,
      "room": null
    },
    "online_details": null,
    "grouping": null,
    "attributes": {
      "category": "Ceremonies and Services"
    },
    "private": false,
    "canceled": null,
    "published": true,
    "role": null,
    "free": true,
    "cost": null,
    "registration_details": null,
    "attendance_details": null,
    "survey_details": null,
    "sponsor": null,
    "speaker": null,
    "contacts": null,
    "source": null,
    "data": null
  },
  "to_members": null
}

Response 1: 500
{
  "message": "Error validating request: request body has an error: doesn't match schema #/components/schemas/_bbs_req_CreateEvent: Error at \"/admins_identifiers\": Value is not nullable\nSchema:\n  {\n    \"items\": {\n      \"properties\": {\n        \"account_id\": {\n          \"type\": \"string\"\n        },\n        \"external_id\": {\n          \"type\": \"string\"\n        }\n      },\n      \"type\": \"object\"\n    },\n    \"type\": \"array\"\n  }\n\nValue:\n  null\n",
  "status": "bad-request"
}

Request 2:
POST: https://api-dev.rokwire.illinois.edu/gr/api/group/events/v3

Body:
{
  "event": {
    "id": null,
    "name": "Group Event test DD 20240126",
    "description": "dsedas",
    "instructions": null,
    "image_url": null,
    "event_url": null,
    "timezone": "Europe/Sofia",
    "start":<PHONE_NUMBER>,
    "end":<PHONE_NUMBER>,
    "all_day": false,
    "event_type": "in-person",
    "location": {
      "id": null,
      "latitude": 40.101113,
      "longitude": -88.226812,
      "name": "Location",
      "description": null,
      "building": "Location",
      "fullAddress": null,
      "address": null,
      "city": null,
      "state": null,
      "zip": null,
      "floor": null,
      "room": null
    },
    "online_details": null,
    "grouping": null,
    "attributes": {
      "category": "Career Development"
    },
    "private": false,
    "canceled": null,
    "published": true,
    "role": null,
    "free": true,
    "cost": null,
    "registration_details": null,
    "attendance_details": null,
    "survey_details": null,
    "sponsor": null,
    "speaker": null,
    "contacts": null,
    "source": null,
    "data": null
  },
  "group_ids": [
    "05073b36-4920-432f-a1ec-7ca06275a013",
    "d4cadfda-9deb-11ec-9db3-0a58a9feac02"
  ]
}

Response 2: 500
{
  "message": "Error validating request: request body has an error: doesn't match schema #/components/schemas/_bbs_req_CreateEvent: Error at \"/admins_identifiers\": Value is not nullable\nSchema:\n  {\n    \"items\": {\n      \"properties\": {\n        \"account_id\": {\n          \"type\": \"string\"\n        },\n        \"external_id\": {\n          \"type\": \"string\"\n        }\n      },\n      \"type\": \"object\"\n    },\n    \"type\": \"array\"\n  }\n\nValue:\n  null\n",
  "status": "bad-request"
}

Fixed


fugacity_coefficient throwing error from static arrays

Possibly this is an issue with StaticArrays rather than you, it certainly doesn't seem to be on your end
To reproduce:
julia> using Clapeyron
[ Info: Precompiling Clapeyron [7c7805af-46cc-48c9-995b-ed0ed2dc909a]

julia> model = VTPR(["carbon dioxide"])
PR{BasicIdeal, TwuAlpha, RackettTranslation, VTPRRule{VTPRUNIFAC{PR{BasicIdeal, PRAlpha, NoTranslation, vdW1fRule}}}} with 1 component:
 "carbon dioxide"
Contains parameters: a, b, Tc, Pc, Mw

julia> p = 1e5
100000.0

julia> T = 273.15
273.15

julia> volume(model, p, T)
0.022547066007297695

julia> fugacity_coefficient(model, p, T)
ERROR: setindex!(::StaticArraysCore.SVector{1, Float64}, value, ::Int) is not defined.
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:33
 [2] setindex!(a::StaticArraysCore.SVector{1, Float64}, value::Float64, i::Int64)
   @ StaticArrays ~/.julia/packages/StaticArrays/dcWsT/src/indexing.jl:3
 [3] fugacity_coefficient(model::PR{BasicIdeal, TwuAlpha, RackettTranslation, VTPRRule{VTPRUNIFAC{PR{BasicIdeal, PRAlpha, NoTranslation, vdW1fRule}}}}, p::Float64, T::Float64, z::StaticArraysCore.SVector{1, Float64}; phase::Symbol, threaded::Bool)
   @ Clapeyron ~/.julia/packages/Clapeyron/NEYMK/src/methods/pT.jl:334
 [4] fugacity_coefficient (repeats 2 times)
   @ ~/.julia/packages/Clapeyron/NEYMK/src/methods/pT.jl:329 [inlined]
 [5] top-level scope
   @ REPL[6]:1

This error occurs when assiging a value to $\varphi$ on this line:
In #fugacity_coefficient#331(phase, threaded, , model, p, T, z) at /home/luc/.julia/packages/Clapeyron/NEYMK/src/methods/pT.jl:328
 330      μ_res = VT_chemical_potential_res(model,V,T,z)
 331      φ = μ_res
 332      Z = p*V/R̄/T/sum(z)
 333      for i ∈ @comps
>334          φ[i] = exp(μ_res[i]/R̄/T)/Z
 335      end
 336      return φ
 337  end

This occurs on Clapeyron release 0.3.7
(@v1.7) pkg> status
      Status `~/.julia/environments/v1.7/Project.toml`
  [6e4b80f9] BenchmarkTools v1.3.1
  [7c7805af] Clapeyron v0.3.7

Hopefully it is reproducable for you and a simple fix

we can rely on broadcasting at the expense of an additional allocation, but it seems worth it

it is a known problem with StaticArrays.jl, and packages, like BangBang.jl were done to help make the experience of using static arrays better. probable we would need to check all methods, for now, to fix it, you just need to do:
function fugacity_coefficient(model::EoSModel,p,T,z=SA[1.]; phase = :unknown, threaded=true)
    V = volume(model,p,T,z;phase,threaded)
    μ_res = VT_chemical_potential_res(model,V,T,z)
    φ = μ_res
    Z = p*V/R̄/T/sum(z)
    return exp.(μ_res ./ R̄ ./ T) ./ Z
end


chore: updates python_requires in setup.py

Description
The setup.py file doesn't specify the minimum Python version requirement. This leads to installation on unsupported Python versions. We had dropped support for Python 3.7 and lower months ago, however it is still possible to install it on system with lower Python versions.

:tada: This PR is included in version 7.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Possible memory corruption

https://github.com/freetonsurfer/ton_client_dart/blob/62fd01a02af9bced52047f35db6b15d4e523f6c5/lib/src/tonsdklib/wrapper.cpp#L93
You must use res.len here.

thx. this library not used now.


Site Navigation Is Unusable

I'm trying to navigate your site using the side nav. I click on a section the first time and nothing happens. I'm not scrolled anywhere. The second time a click it it scrolls a little bit but never to the right section.

Duplicate https://github.com/zeit/next-site/issues/132

Solved in zeit/next-site#132


Postinstall not waiting for pods in STS to become Ready (Running)

Output of helm version:
Client: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:47:40Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:37:43Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
I am trying to deploy a stateful set with 3 pods and i want to run a postinstall job.
I have used below hooks   in postinstall yaml file
annotations:
"helm.sh/hook": post-install,post-upgrade
"helm.sh/hook-delete-policy": hook-succeeded
As soon as statefulset is deployed (i.e none of the pods are in ready. Only 1 pod is in initializing state), postinstall job is already running. Shouldnt it wait for all pods in STS to get to running state before starting the postinstall job?
I tried using --wait argument in helm install, still its the same. Post install is triggered as soon as STS is deployed.
Can someone throw some light on this behaviour please.

Can you try to reproduce with a more recent version of Helm? 2.16.9 is the latest Helm 2 release.
It's important to note here that Helm 2 will no longer accept bug fixes after August 13th, so if you identify a bug, please submit a patch soon before the patch window has closed. See this blog post for more details.

@bacongobbler Unfortunately , im restricted to this version for now. But im just looking for answer, if its  a known bug in earlier versions of helm 2. Im not looking for a solution.

We are no longer accepting bug fixes for Helm 2. See https://helm.sh/blog/helm-v2-deprecation-timeline/ for more details.


Request: Black theme

Black is very friendly color for oled technology display

The latest version 1.7.2 now fully supports black theme. Please check it and let me know!

it's perfect!


OS and pytorch version

Is the OS Ubuntu 18.04? Or is it 20.04?
Also, what version of pytorch are you using?

I tried Ubuntu 18.04 and pytorch 1.5/1.6.


release artifacts for release v1.0.4

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/ok-to-test


changelog

I love this tool! thanks for working on this!
every time I see a release I am happy but then its super hard to figure out what actually changed.
do you consider starting a changelog?

Thanks for the suggestion. I've added a changelog file which lists changes for the last two versions + any unreleased changes.


Spotify controls are hidden from view

Describe ur issue:
Spotify controls are hidden below the bottom left corner when using this theme.

Working on it


Does db.session.delete() delete associated data?

Does db.session.delete() delete associated data? I want to change the physical delete to the logical delete using the "is_del" field distinction, but I am afraid that the associated data will not change according to the original logic, causing the data that should be logically deleted to be found

It would only delete the associated data if the associations were defined as on delete cascade, so the answer is unfortunately it depends on the implementation.


Special characters in XML attributes not being escaped correctly

Thanks very much for this very useful library. I've run into an issue since ampersands in XML attributes aren't being escaped by js2xml. This seems to have happened after the change described here: https://github.com/nashwaan/xml-js/issues/26#issuecomment-323543868 however the StackOverflow answer that is referenced seems to be incorrect or just very badly structured? The spec extract that is quoted seems to contradict its recommendation and attributes with ampersands don't validate properly - e.g. try https://validator.w3.org/check with
<?xml version="1.0"?>
<elt attr="abc&def"></elt>

@eug48 , you are right. I got it wrong when I based my solution on that StackOverflow thread.
I wasn't aware about https://validator.w3.org/#validate_by_input+with_options online checking.
Now I can conclude correctly that the 5 characters: & < > " ' should be replaced with & < > " ' in both text of tags AND attributes.
Will need to find time to fix this issue.

I also ran into this issue.

@nashwaan When this issue will resolve?

is there any update on this issue? thanks!

Also experiencing this issue, raised here:
https://github.com/dolanmiu/docx/issues/2443


Tesla P40 only using 70W underload

So my P40 is only using about 70W while generating responses, its not limited in any way(IE. Power delivery or temp)

P40 isn't very well supported (yet). ExLlama relies heavily on FP16 math, and the P40 just has terrible FP16 performance.
I'm not sure what to do about it, because adding a whole second code path for FP32 would be a lot of work with a lot of maintenance afterwards. Inference would also use considerably more VRAM, so I'm not sure you'd be able to run e.g. a 33B model at full context length despite the 24 GB of VRAM.
For now I just don't have enough time to make it a priority. I have to focus on modern (consumer) GPUs.

Is there anything I can do to improve performance on the P40?
Also is there any way to lower normal ram usage?

Basically by continuing to use the existing huggingface GPTQ implementations.
This is the curse of using dated hardware, eventually software stops being able to work with it due to its limitations, and with the P40s you're stuck with the software that's got the "development oomph" to support edge cases like yours.
If you really really want to get it to work, you or someone else with the programming knowledge will probably need to fork this repo then update the 16 bit code to cast to 32 bit on the fly right before calculations are done, then maintain that code in the future as this "modern support" version gets updated over time.
It's a big task, and probably worth a few thousand dollars of labor at least.

Same here. I'm seeing 20+ tok/s on a 13B model with gptq-for-llama/autogptq and 3-4 toks/s on my P40.
There is a flag for gptq/torch called use_cuda_fp16 = False that gives a massive speed boost -- is it possible to do something similar in exllama?

There is a flag for gptq/torch called use_cuda_fp16 = False that gives a massive speed boost -- is it possible to do something similar in exllama?

Well, it would give a massive boost on the P40 because of its really poor FP16 support. It would slow things down a lot on newer GPUs. More importantly it would require a lot of extra work, basically a whole new code path that would essentially just be for the P40. Although I'd like have good P40 support, right now I'd rather invite someone else to contribute the code for it.

Also with gptq, I can load 33B models using only 20GB VRAM (with fp16 = False).

Can you use the full context as well?

Doesn't all pascal cards, older and maybe turning cards have bad FP16 performance?

They do (pascal). On 3090 supposedly FP16 is equal to FP32. FP16=false doesn't move the needle in either direction. On 4090 people were getting speedups.
The driver appears to change some FP16 operations to FP32 unless I'm seeing things. I found some FP16 math did well while some caused 1/2 speed cut.
I can full context on P40 without group size using classic GPTQ and autogptq. Another problem will be mixing/matching cards. I've run into it already on my server and had to recompile things with the P40 hidden due to work arounds for stuff like atomic add or lack of proper tensor support.

P40 weirdness seems to be even stranger than just "it's slow".  I wanted to chart VRAM usage for different models at different prompt context sizes, and the results were... impossible?
Guanaco 33b
Context		VRAM (GB)	T/S (P40)	Coherent?
Idle 		        16.6		        N/A		N/A
1k			19.9		        0.34	        No
2k			OOM		N/A		N/A

Tulu 30b
Context		VRAM (GB)	T/S (P40)	Coherent?
Idle		       16.7		        N/A		N/A
1k			23.1		        0.38		Yes
2k			23.2		        0.22		Yes(ish)
3k			23.4		        0.15		Yes
4k			23.5		        0.13		Yes
6k			OOM		N/A		N/A

Nous-Hermes 13b
Context		VRAM (GB)	T/S (P40)	Coherent?
Idle		        7.5			N/A		N/A
1k			14.0		        0.96		Yes
2k			14.2		        0.54		Yes
3k			14.3		        0.38		Yes
4k			14.5		        0.21		Yes
6k			14.7		        0.02		No
7.5k		        14.9		        0.05		No

Manticore-chat 13b
Context		VRAM (GB)	T/S (P40)	Coherent?
Idle		        7.6			N/A		N/A
1k			14.0		        0.96		Yes
2k			14.3		        0.36		Yes
6k			14.7		        0		No

Either exllama has somehow made the memory requirement curve sub-linear, or it's really, really broken on Pascal.

I'm curious how you're configuring the model in this case? If you're running with max_seq_len = 8192 in all cases, then the model is correctly allocating the full cache in advance.
And is this on the latest commit? If so then the VRAM usage should top out at the 2k sequence length unless you're overriding the default max_input_len and max_attention_size.

Ah, my apologies.  I had no idea it was allocating memory for max context, regardless of how much context was actually being fed in.  In retrospect, that perfectly explains what I'm seeing, but as autogptq and llamacpp claim VRAM as needed, it didn't even occur to me that was what you are doing.

Yep. It's necessary to avoid memory fragmentation, but it also makes more sense to me to allocate up front what you can predict you're eventually going to need anyway. But as to that, if this is on the latest commit you still shouldn't be seeing the slight increase in VRAM usage after 2k tokens. And I'm concerned about it going incoherent after about 5k tokens. That was supposed to be fixed.

I'm actually doing this in oobabooga, not exllama proper.  My ooba install is up to date, but I have no clue if their implementation is up to date with your repo.  That likely explains the VRAM increases.  So I'm probably wasting your time on that front as well.
I'm happy to test it directly on exllama if you want.

Nah, it's fine. It explains it well enough, since it looks like they're a little behind with their packaging of ExLlama as a library.

My P40 gets stuck every other message and then sillytavern times it out, I get about 3.7 tokens a second (On AVG) but it hangs every other message

As mentioned above by @turboderp, fp16 performance on p40 means exllama is going to be slow.
Try autogptq/gptq-for-llama loaders instead.

its not that though, it does work, as shown by that spike, i sometimes get a run of 4 or 5 within 5 seconds then it just hangs
and the others just dont work on the P40


Dealabs Bridge - Recherche : shopmium failed with error 0

Error message: Call to a member function find() on null
Query string: action=display&bridge=Dealabs&q=shopmium&hide_expired=on&priceFrom=&priceTo=&format=Atom
Version: dev.2019-05-08

The commit f3c6876 fix this issue !

Fixed, thanks :)


Support private key-based connections to Snowflake

Is your feature request related to a problem? Please describe.
It is not possible to connect to a Snowflake instance where a user's authentication happens via an RSA private key, this is preventing us from using dbt-sugar.
Describe the solution you'd like
dbt-sugar to support RSA private keys for Snowflake connections
Describe alternatives you've considered
The alternative is setting up a different user login method, but this is less secure.

Hey @badge thanks a lot for your interest in the tool.
Quick question, I assume dbt allows for that kind of connection in its profile right?
I've been thinking of finding some time to rework the entire package to leverage dbt's API more directly now that they have a stable version. In that case, instead of us reading the profile "manually" we could make dbt read it and then pass that to the connector.
I'll have to look into dbt's code to see a bit more.
Would it be something you may want to contribute to? I'd be more than happy to assist you with that. Otherwise, it may take a bit of time as I am a little snowed under with my main job.
Let me know!

Oh! I see that you already contributed! That's super awesome. I'll take a look later today and hopefully we can get that merged so that you can continue and hopefully it works out for you.
I'm in serious need or extra pairs of hands on this project given the intention to leverage dbt's API directly so your contribution is a blessing!


Docs should mention the requirement to remove nav

The docs currently don't state that this only works if nav is removed. This should be explicitly stated.

This is confusing to me. If I remove the nav section I don't have my website anymore, just the blog section. I can get the blog pages showing but I have to enter them manually into the nav section. I thought this plugin would parse all the .md files under blog/YYYY/MM/DD and automatically add them to a "blog" entry in the nav bar in addition to my normal nav web pages. Am I missing something?

This is a really interesting plugin. Unfortunately, since this question has not been answered for so long, I wonder if it is still actively maintained.


the Caffe2 library does not seem to be linked with whole-static library option

i successfully compile caffe2 lib with visual studio 2015 as static library. but when add .lib's into my c++ project and want to run my program this run time error occur :
[F operator.h:644] You might have made a build error: the Caffe2 library does not seem to be linked with whole-static library option. To do so, use -Wl,-force_load (clang) or -Wl,--whole-archive (gcc) to link the Caffe2 library.
i set DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS in CMAKE when want create solution but not solve.

Windows uses -WHOLEARCHIVE - could you give that a shot?
https://msdn.microsoft.com/en-us/library/mt732963.aspx

Also, this macro might be helpful:
https://github.com/caffe2/caffe2/blob/f2cf8933fc8c04f149ea27f30381517df358c1b5/cmake/Utils.cmake#L173-L185

i try very different way but not work. finally i find this problem  in tensotflow,  and it's solution work for caffe2.
you just attach all .obj files to your solution and compile it.

@aligoglos Could you show how to do that " attach all .obj files to your solution"? sorry ,I have been troubled by this problem for weeeeeks!

hi you should just use 'Add -> Existing items' to add all .obj files in
your solution.
On Tue, Feb 6, 2018 at 12:30 PM, badtiger8013<EMAIL_ADDRESS>wrote:

@aligoglos https://github.com/aligoglos Could you show how to do that "
attach all .obj files to your solution"? sorry ,I have been troubled by
this problem for weeeeeks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/caffe2/caffe2/issues/1370#issuecomment-363354814, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADvaKJhzsspOrkZ55HszdX8Yk8R7sAn6ks5tSBSPgaJpZM4QDGyC
.

@aligoglos you mean : thanks for the reply. you mean, for each project in the solution , add the corresponding .obj file and then build ALL_BUILD？

just for that project, you want add caffe2 libraries.
solution of your test project.
On Thu, Feb 8, 2018 at 9:33 AM, badtiger8013<EMAIL_ADDRESS>wrote:

@aligoglos https://github.com/aligoglos you mean : thanks for the
reply. you mean, for each project in the solution , add the corresponding
.obj file and then build ALL_BUILD？
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/caffe2/caffe2/issues/1370#issuecomment-364011795, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADvaKLzLfon4dcGKwnchivCebvJ8D_fyks5tSo4ngaJpZM4QDGyC
.

Hi @aligoglos ,
I succesfully compiled Caffe2 on windows 10. Now, I would like to use caffe2 libraries in Visual Studio 2015. How should I add the libraries and from what path?
Should I add only these libraries?

Should I include the mentioned libraries in my project, e.g., as:
#include <caffe2/core/init.h>
#include <caffe2/core/operator.h>

???

yes you just add this libs and if you get this error :
the Caffe2 library does not seem to be linked with whole-static library
option
you must add .obj into your project also.


Instance variables for Windows.initialize

Allows inference of variables which was creating an error in Crystal 0.25.1

Nice work! Thank you! 💯


Polish examples (especially CLI apps)

Polishing Qt examples was done in #39. CLI app has still to be improved.


Dynamic route problem in Next js

@DuCanhGH I have similar problem just on dynamic route I have for example [phone] route and in this specific dynamic route I got error and if I change this to phone all things work correctly, have any suggest on dynamic routing?
also I use like this and also I saw the @guilatrova  project but for my case did not work correctly
sw.ts
import { Serwist } from 'serwist';
import { CUSTOM_CACHE } from './caching';

import type { PrecacheEntry, SerwistGlobalConfig } from 'serwist';

// This declares the value of `injectionPoint` to TypeScript.
// `injectionPoint` is the string that will be replaced by the
// actual precache manifest. By default, this string is set to
// `"self.__SW_MANIFEST"`.
declare global {
  interface WorkerGlobalScope extends SerwistGlobalConfig {
    __SW_MANIFEST: (PrecacheEntry | string)[] | undefined;
  }
}

declare const self: ServiceWorkerGlobalScope;

const serwist = new Serwist({
  precacheEntries: self.__SW_MANIFEST,
  skipWaiting: true,
  clientsClaim: true,
  navigationPreload: true,
  runtimeCaching: CUSTOM_CACHE,
});

const DEFAULT_URLS = ['/', '/auth'];

self.addEventListener('install', (event) => {
  event.waitUntil(
    Promise.all(
      DEFAULT_URLS.map((entry) => {
        const request = serwist.handleRequest({
          request: new Request(entry),
          event,
        });
        return request;
      })
    )
  );
});
serwist.setCatchHandler(async ({ event, request, url }) => {
  if (request.destination === 'document' && url.origin === location.origin && url.pathname.startsWith('/auth')) {
    const match = serwist.handleRequest({ event, request: new Request('/auth') });
    return match ? await match : Response.error();
  }
  return Response.error();
});

serwist.addEventListeners();

I pass one matcher like this:
   {
        matcher: ({ sameOrigin, url: { pathname } }) => {
          // Exclude /api/auth/callback/* to fix OAuth workflow in Safari without having
          // an impact on other environments
          // The above route is the default for next-auth, you may need to change it if
          // your OAuth workflow has a different callback route.
          // Issue: https://github.com/shadowwalker/next-pwa/issues/131#issuecomment-821894809
          // TODO(ducanhgh): Investigate Auth.js's "/api/auth/*" failing when we allow them
          // to be cached (the current behaviour).
          if (!sameOrigin || pathname.startsWith('/app/(auth)/auth/*')) {
            return false;
          }

          if (pathname.startsWith('/auth/')) {
            return true;
          }

          return false;
        },
        method: 'GET',
        handler: new NetworkFirst({
          cacheName: 'auth',
          plugins: [
            new ExpirationPlugin({
              maxEntries: 16,
              maxAgeSeconds: 24 * 60 * 60, // 24 hours
              maxAgeFrom: 'last-used',
            }),
          ],
          networkTimeoutSeconds: 10, // fallback to cache if API does not response within 10 seconds
        }),
      },

and I got this error

I also facing the similar issue

@DuCanhGH Any update?

the parallel route is the problem because it's not url encoding the @ in @login

what worked for me is this:
const manifestTransform = async (manifestEntries) => {
  const manifest = manifestEntries.map((m) => {
    if (m.url.includes("@")) m.url = m.url.replace("@", "%40");

    return m;
  });
  return { manifest, warnings: [] };
};

add this to bottom of next.config.js
then in your serwist config in next.config.js just add manifestTransforms: [manifestTransform],


Validation not triggered

Validation of the requestbody is not triggered while bean-validation is true in the configuration.
I think because the @Valid annotation is missing for the method arguments in the generated code.
If I add the @Valid annotation in the method implementation, I get an exception:
javax.validation.ConstraintDeclarationException: HV000151: A method overriding another method must not redefine the parameter constraint configuration, but method TestRequest#setSomeBoolean(Boolean) redefines the configuration of CreateTestRequest#setSomeBoolean(Boolean).
CreateTestRequest & TestRequest (with lombok):
@Data
public class CreateTestRequest {
  @NotNull
  private Boolean someBoolean;
}

@Data
public class TestRequest extends CreateTestRequest {
  @NotNull
  private Long id;
}

TestRequest is a subclass of CreateTestRequest where the javax constraints are.
I use specific type mapping to generate the code:
openapi-processor-mapping: v2

options:
  package-name: com.apis.test
  one-of-interface: true
  bean-validation: true
  generated-date: true
  format-code: false
  javadoc: false

map:
  result: org.springframework.http.ResponseEntity
  types:
    - type: TestRequest => com.apis.custom.TestRequest
    - type: CreateTestRequest => com.apis.custom.CreateTestRequest

Generated code:
@PutMapping(path = "/api/test/{id}", consumes = {"application/json"}, produces = {"application/json"})
    ResponseEntity<TestResponse> update(
@PathVariable(name = "id") @NotNull @DecimalMin(value = "1") Long id,
@RequestBody @NotNull TestRequest body);

Implementation:
@Override
  public ResponseEntity<TestResponse> update(
      final Long id,
      final TestRequest input) {
    // implementation
  }

the issue is caused by the mapping.
Without the mapping it puts the @Valid annotation at the request body parameter. An annotation mapping as workaround doesn't work either, it has the same issue.
I wonder if this is a bug or something I never implemented. ;-)
Looking at it..

looks like this is something that I never properly implemented.
I will implement/fix it.
here is a quick & dirty workaround with annotation mapping until it is fixed:
map:
  types:
    - type: Foo => validate.Foo2

  parameters:
    # add an annotation to an endpoint method parameter of an OpenAPI type

    # should use the OpenAPI Foo (annotation mapping has the same mapping issue)...
    # - type: Foo @ javax.validation.Valid

    # ... but using annotation mapping with the mapped name works.
    - type: Foo2 @ javax.validation.Valid

    # so in your case, this should work
    - type: TestRequest @ javax.validation.Valid

It works! Thank you for the quick response and the workaround! :)
I also needed to add this to the mapping:
- type: Long @ javax.validation.Valid
Is that caused by the same issue?

yes, it works but is unwanted. It should only work on the original OpenAPI type.
I think you don't need the @Valid on the Long. The @Valid tells the validation to check the properties of an object.

improved in 2023.1, the workaround will not work anymore and should not be necessary.


How can I setup HA(High Availability) for  HDFS,Hive ?

Hi.
I need to setup the HA(High Availability) for  HDFS,Hive.
Is it simply changing the replicas?
ex)
$ kubectl edit statefulset hdfs-namenode

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: apps/v1
kind: StatefulSet
metadata:
  creationTimestamp: 2019-02-01T08:11:16Z
  generation: 5
  labels:
    app: hdfs-namenode
  name: hdfs-namenode
  namespace: metering
  resourceVersion: "47842114"
  selfLink: /apis/apps/v1/namespaces/metering/statefulsets/hdfs-namenode
  uid: f28b96f0-25f8-11e9-ba86-fa163ec5257c
spec:
  podManagementPolicy: OrderedReady
  replicas: 1    # ->  2 ??
  revisionHistoryLimit: 10
  selector:

Do I need additional work?
Thank you.

We don't support running multiple copies of any Hive components, and for HDFS we only support increasing HDFS datanode replicas. Running multiple namenodes requires a coordination service like zookeeper which we don't want to currently support.

@chancez
Thank you :)


Fix PackageName for Aegisub.Aegisub.Dev version 0.0.0

to make sure it doesn't conflict with the stable version.
Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Domain


Implement events

Implement events for classes!

This is out of scope of the design goals since it involves adding new runtime functionality.


Please publish a release (e.g.: v1.0)

Please create a tag and publish as a release (e.g: v1.0)
So we can monitor any new packages released and we don't get this message when installing with Composer:

Could not find a matching version of package rfdeoliveira/procob-php. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).

I just published a release tagged as v1.0.0. Could you please test if everything is ok, before I close this issue?
Thanks for reaching out =)

@rfdeoliveira mmm still not working
composer require rfdeoliveira/procob-php

In InitCommand.php line 727:
  Could not find a matching version of package rfdeoliveira/procob-php. Check
   the package spelling, your version constraint and that the package is avai
  lable in a stability which matches your minimum-stability (stable).

Have you published this project in packagist.org?

Sorry, I haven't, because I thought you were trying to install it this way. I made it available on Packagist, it should be working now!


Not booting... Connecting to database...

I'm seeing this:
db:
PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-07-01 08:06:13.007 UTC [1] LOG:  starting PostgreSQL 15.4 (Debian 15.4-2.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-07-01 08:06:13.008 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2024-07-01 08:06:13.008 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-07-01 08:06:13.166 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-07-01 08:06:13.273 UTC [24] LOG:  database system was shut down at 2024-07-01 08:03:37 UTC
2024-07-01 08:06:13.414 UTC [1] LOG:  database system is ready to accept connections
2024-07-01 08:06:16.048 UTC [28] LOG:  could not receive data from client: Connection reset by peer

and app:
[dialoqbase]    |
[dialoqbase]    | 36 migrations found in prisma/migrations
[dialoqbase]    |
[dialoqbase]    |
[dialoqbase]    | No pending migrations to apply.
[dialoqbase]    | npm notice
[dialoqbase]    | npm notice New minor version of npm available! 10.7.0 -> 10.8.1
[dialoqbase]    | npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.1
[dialoqbase]    | npm notice To update run: npm install -g<EMAIL_ADDRESS>[dialoqbase]    | npm notice
[dialoqbase]    | Running seed command `ts-node prisma/seed.ts` ...
[dialoqbase]    | Seeding new models...
[dialoqbase]    |
[dialoqbase]    | 🌱  The seed command has been executed.
[dialoqbase]    | ┌─────────────────────────────────────────────────────────┐
[dialoqbase]    | │  Update available 5.15.1 -> 5.16.1                      │
[dialoqbase]    | │  Run the following to update                            │
[dialoqbase]    | │    yarn add --dev prisma@latest                         │
[dialoqbase]    | │    yarn add @prisma/client@latest                       │
[dialoqbase]    | └─────────────────────────────────────────────────────────┘
[dialoqbase]    | [info] use ffmpeg.wasm v0.12.0
[dialoqbase]    | Connecting to database...

Hi! No. The app is not available...


[Outreachy] Sticky searchform

The Sticky Search Form is a feature designed to improve the user experience on the OpenTelemetry website by enhancing accessibility and ease of use for search functionality. This feature keeps the search form anchored at the top of the page as users scroll through content, ensuring that the search field remains readily available without requiring users to scroll back to the top. This is particularly beneficial on content-heavy pages where navigating back to the search bar may disrupt the browsing experience.
Key Features:
Search Accessibility: The search form becomes "sticky" once the user scrolls beyond a predefined threshold, staying fixed at the top of the viewport. This allows users to initiate a search from anywhere on the page.
Dynamic User Experience: The sticky search form improves navigation efficiency by offering quick access to content search, eliminating the need for unnecessary scrolling.
Responsive Design: The implementation ensures that the sticky search form adapts to various screen sizes, providing a seamless experience across devices, from desktop to mobile.
https://github.com/user-attachments/assets/0f7837b1-3572-4308-b7bb-a5c7b09c7ab4
https://github.com/user-attachments/assets/f36739cc-7818-4e64-b42e-344a6e754e70
Desktop view mode, not so sure about the UI look on mobile though, would love to hear your input mentor. @svrnm

This looks good, thank you!
A thing that I saw while trying it out is that the buttons have a transparent background, and therefore text in the background shines through, I guess you need to change that to a solid background

Yes indeed, you’re right. I will fix

Fixed mentor @svrnm . The Search form buttons are now solid with a white background (bg-white).

I am still awaiting your review mentor @svrnm  .

Hey, the sticky search looks good to me! Can you remove the scroll up button from this PR, so both features are in separate PRs as discussed? thanks

Oh yeah, my bad, will fix now
On Wed, 16 Oct 2024 at 10:45 AM Severin Neumann @.***>
wrote:

Hey, the sticky search looks good to me! Can you remove the scroll up
button from this PR, so both features are in separate PRs as discussed?
thanks
—
Reply to this email directly, view it on GitHub
https://github.com/open-telemetry/opentelemetry.io/pull/5400#issuecomment-2416286510,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5F4OZ4HCPPDTFVJH4CM6ADZ3YYVDAVCNFSM6AAAAABP4U6OHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJWGI4DMNJRGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@bintus-ux can you run npm run fix:format locally and upload the changes? This should resolve the CI issue

@bintus-ux can you run npm run fix:format locally and upload the changes? This should resolve the CI issue

Oh yeah, on it now.

Done mentor. @svrnm

@svrnm Its ready now mentor. Please review.

I consider this as done! After the outreachy application phase we will take another look and see if we can merge this PR. Thank you!

Got you, on it.
On Mon, 11 Nov 2024 at 3:29 PM Severin Neumann @.***>
wrote:

@.**** requested changes on this pull request.
hey @bintus-ux https://github.com/bintus-ux, we would like to merge
this PR into the project, there are a few more changes I need you to look
into. thanks!
On assets/js/stickySearch.js
https://github.com/open-telemetry/opentelemetry.io/pull/5400#discussion_r1836753778
:
can you move this to the content of assets/js/registrySearch.js since it
is unique to the registry and does not need to live in it's own file
In layouts/partials/hooks/body-end.html
https://github.com/open-telemetry/opentelemetry.io/pull/5400#discussion_r1836755079
:

@@ -2,3 +2,4 @@
{{ partial "script.html" (dict "src" "js/tracing.js") -}}
{{ end -}}
{{ partial "script.html" (dict "src" "js/navScroll.js") -}}
+{{ partial "script.html" (dict "src" "js/stickySearch.js") -}}

⬇ Suggested change
-{{ partial "script.html" (dict "src" "js/stickySearch.js") -}}
This will not be necessary anymore when you have moved the stickySearch.js
to be included in the registrySearch.js
—
Reply to this email directly, view it on GitHub
https://github.com/open-telemetry/opentelemetry.io/pull/5400#pullrequestreview-2427426044,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5F4OZ4G5YCCK4GHSZVNEV32AC5NJAVCNFSM6AAAAABP4U6OHWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMRXGQZDMMBUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Btw, this is what it looks like on mobile:

I don't think that we want such a floating search form on mobile.
Given #5331, we might not want this on desktop either.
Thoughts @svrnm et all?

Yes true i was contemplating on a way to adjust the Search form UI on mobile @chalin

Btw, this is what it looks like on mobile:

I don't think that we want such a floating search form on mobile.
Given #5331, we might not want this on desktop either.
Thoughts @svrnm et all?

What do you think of the idea of displaying a search icon alone on mobile which is sticky of course and on user clicking on the icon it smoothly reveals the contents of the searchform, that way its less congested for mobile? @chalin

let's focus on the scroll to top functionality for now, and revisit this one later. I agree with @chalin that maybe having one of the 2 solutions should be enough

let's focus on the scroll to top functionality for now, and revisit this one later. I agree with @chalin that maybe having one of the 2 solutions should be enough

Noted mentor.

I will close this now in favor of the scroll to top functionality


add a readme

we need clear instructions on how to configure the bot and run the app

I've added a readme with the set up instruction


💥Feature: Add a "Custom Popup" for feedback form

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
hey @sk66641 ,
I want to suggest a feature for the feedback form of the website -
I want to add a Custom Feedback "Successfully submitted popup" after the user submits a feedback form.
This will enhance the user experience so better.
Current notification -

and here's example of my previous work -
https://github.com/sk66641/Random-Disco-Light-Simulator/assets/131389695/58776e5d-f958-4040-bce1-a725a4d70b01
Please assign me this issue under GSSoC'24
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sk66641 , Please assign me this issue

@sk66641


fix(modal): modal gets stuck when swiping too fast

Pull request checklist
Please check if your PR fulfills the following requirements:

[X] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[X] Build (npm run build) was run locally and any changes were pushed
[X] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Modal throws an error when swiping down too fast. This fix should prevent "newStepValue" from being "NaN" because the velocity or step is 1, greater than 1, 0 or less than 0.
And also the modal gets stuck when swiping up very fast, so the step is becoming less than zero and it would just "return".

What is the new behavior?

Fixes the issues described above
Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Merged. Thank you!


CMake only logs warning when roscpp is not found

When CMake want's to find the roscpp package, it currently only logs a warning.
Since rosbag_v2 depends on roscpp, the build should fail and not skip.

I don't think we want this, because otherwise we'll have to remove this package or otherwise disable it when building without ROS 1 (a common practice).
If you want to change this to an error I think you should also move this package into a separate repository.

Oh sorry, this is already a separate repository. And it's not in the main ros2.repos file, so that should be ok. Sorry for the noise.


We couldn't find the code for the Biformer used for  object detection

Thank you very much for such a great work. But we couldn't find the code for the Biformer used for object detection.
There is no code for Biformer.py in this directory “/BiFormer/object_detection/mmdet/models/backbones/”.
We would be very grateful if you could provide this code.
Thank you very much！

https://github.com/rayleizhu/BiFormer/blob/8c6f0f7d908e9842d6dd6d11ed87507948d934fc/object_detection/train.py#L1
https://github.com/rayleizhu/BiFormer/blob/public_release/object_detection/models_mm/biformer_mm.py

I truly appreciate your helpful response! Thank you so much for taking the time to address my issue.


ENH: stats: add geometric zscore

Reference issue
Closes issue #14816.
What does this implement/fix?
It implements gzscore, the geometric version of zscore, and it adds tests.
Additional information
All details can be found in issue #14816.

Close-reopen for CI. I will merge if green

Thanks @qbarthelemy!