Signed URLs being created in mixed/wrong regions from rp_upload

Describe the bug
Having followed the steps here:
https://docs.runpod.io/docs/using-s3-to-upload-files-with-serverless
I've got a serverless template that's uploading files successfully to my s3 bucket:
https://crypts-test.s3.eu-west-2.amazonaws.com/
Unfortunately all the URLs created to access these files contain an error in that they're mixed region such as the below:
https://crypts-test.s3.eu-west-2.amazonaws.com/09-23/patches/98ad184c.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA5LZJBQWDDB5D6F27%2F20230911%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230911T112129Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=9fc3ce06538c4fb1a88a721ac890c0f74397d0226ed57c4aad036eb985cece27
You can see that at the start the bucket ID is correct and has eu-west-2 in it, but half way through it says %2Fus-east-1%2F which is causing an error. If you follow that link it complains about region mismatches.
A correct link should look like this:
https://crypts-test.s3.amazonaws.com/WSI/110-B3-HP.ndpi_ROI__mpp0.44_reg000_crop_sk00000_(0%2C0%2C15855%2C15855).png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA5LZJBQWDDB5D6F27%2F20230911%2Feu-west-2%2Fs3%2Faws4_request&X-Amz-Date=20230911T121426Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=8187a969fca6122d02a380d954c165fd8e1d49be2c34e59eb7c4213e53fb7473
To Reproduce
Steps to reproduce the behavior:

create an s3 bucket in eu-west-2 region
create endpoint as in https://docs.runpod.io/docs/using-s3-to-upload-files-with-serverless
get output
click on link to see error message or not

Expected behavior
I link should be created that leads to the image file on s3 directly
Screenshots

Desktop (please complete the following information):

OS: windows
Browser chrome
Version latest

Additional context
None of the above links contain anything confidential, but by their nature they will expire. The actual text of the link contains the error too, but please let me know if you need me to generate any new examples.

I encountered the same issue. Ideally, checking the region of the bucket and automatically setting the region_name would be the best solution. However, as a temporary workaround, I found that setting AWS_DEFAULT_REGION as an environment variable can bypass this problem.
My apologies if you already knew this. I hope this helps.

I didn't know about the AWS_DEFAULT_REGION workaround - I was thinking about making a bucket in us-east-1 just to keep things moving while this is being fixed!

Resolved with #130


Add cors config option

Connects to https://github.com/tilezen/tileserver/issues/30
@zerebubuth could you review please?

:+1:


Type error: This expression is not callable.

Next config:
/**
 * Run `build` or `dev` with `SKIP_ENV_VALIDATION` to skip env validation. This is especially useful
 * for Docker builds.
 */
await import('./src/env.mjs')

import withExportImages from 'next-export-optimize-images'

/** @type {import('next').NextConfig} */
const config = withExportImages({
  reactStrictMode: true,
  output: 'export'
})

export default config

Error:
> next build && next-export-optimize-images

- info Loaded env from DIR/.env
info - [next-export-optimize-images]: Configuration was not loaded. (This is optional.)
- info Linting and checking validity of types ..Failed to compile.

./next.config.mjs:10:16
Type error: This expression is not callable.
  Type 'typeof import("DIR/node_modules/.pnpm/next-export-optimize-images@3.1.0_next@13.4.12_react-dom@18.2.0_react@18.2.0/node_modules/next-export-optimize-images/dist/index")' has no call signatures.

   8 |
   9 | /** @type {import('next').NextConfig} */
> 10 | const config = withExportImages({
     |                ^
  11 |   reactStrictMode: true,
  12 |   output: 'export'
  13 | })
 ELIFECYCLE  Command failed with exit code 1.
 ```

Can you try with next.config.js?

Adding a // @ts-nocheck seems to fix Next compilation.
It's just missing a call signature in the type

I see...
If you are able to provide a revised PR, I would very much appreciate it!

It's a very small fix so I won't bother with a PR, but I believe it stems from the fact that index.ts sets module.exports instead of using the export keyword which omits the typing from the .d.ts file


Migrated to Slick 2.3.0-M1

Migration to Slick 3.2.0-M1 (No need of Slick Extensions and its expensive subscription)

Thanks, I have taken your code and released a test version 2.6.12-3.2.0-M2.


Issue with hover tool and invert_yaxis=True

I am displaying an image in the form Image((X,Y,Z)) as explained here with inverted y axis.
I also am using the hover tool to display raw values.
However, the region where the hover tool is actually working is not on the image, but below:

The code I used to make this figure is
%%opts Image [width=400, aspect=0.5, invert_yaxis=True]
img = hv.Image( (cpos, mpos, sim.transpose()) ).opts(cmap=colorcet.fire)
img..opts(tools=['hover'], invert_yaxis=True)

I am using JupyterLab 1.0.2, Holoviews 1.12.3 and Bokeh 1.2.0

MWE if anybody else wants to try it:
import holoviews as hv
import numpy as np
hv.extension('bokeh')

img = hv.Image((np.arange(10), np.arange(10), np.random.rand(10,10)))
img.opts(tools=['hover'], invert_yaxis=True, ylim=(0, 20))

@poplarShift Thanks for warning me about %%opts!
I will only use .opts from now on, however I think %%opts was useful in case I had many similar figures to show in a Layout and did not want to manually write the options for each of them.
Probably there is a way that does not require %%opts? If there is, please excuse me, I started using Holoviews only recently.

@Thalos12, you can use .opts with options you declare separately by type (as for %%opts), where they will later be applied only to the items of the declared type:
import holoviews as hv
import numpy as np
hv.extension('bokeh')

img = hv.Image((np.arange(10), np.arange(10), np.random.rand(10,10)))
opts = hv.opts.Image(tools=['hover'], invert_yaxis=True, ylim=(0, 20))
img.opts(lopts)

BTW, I"m curious where you ran across %%opts; we've tried to eliminate that from our examples to avoid confusion.

@jbednar Thanks for the suggestion, I will a variable to store the options then.
Regarding the %%opts, I likely copied some code from the internet and never discovered that it was deprecated!

@jbednar Actually, using the search bar of the website I found two places:

in the FAQ, towards the end (Q: Why isn’t my %%opts cell magic being applied to my HoloViews object?)
in the Notebook Magics section of the User guide.

I don't think I ever visited those pages before though.

Fixed in #4010

@philippjfr Thanks a lot!


kie-issues#1549: kn-workflow-plugin check for the presence of an image in the local Docker image does not cover all cases

Closes https://github.com/apache/incubator-kie-issues/issues/1549

@ricardozanini looking


Update version to 1.0.83-2 on staging

Update version to 1.0.83-2

🚀 Deployed to staging by @OSBotify in version: 1.0.83-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @isagoico in version: 1.0.85-9 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Why is there an empty space instead of a variable in after MULTIPART_PART_HEADERS:charset ?

Describe the bug
I am configuring ModSecurity using Nginx by following this https://www.linode.com/docs/guides/securing-nginx-with-modsecurity/#configuring-modsecurity on Linode by hackersploit. I have done everything said but when I run the command sudo nginx -t after adding modsecurity_rules_file it is giving an error which says
nginx: [emerg] "modsecurity_rules_file" directive Rules error. File: /usr/local/modsecurity-crs/rules/REQUEST-922-MULTIPART-ATTACK.conf. Line: 27. Column: 53. Expecting a variable, got:  :  MULTIPART_PART_HEADERS:_charset_ "!@eq 0" \ in /etc/nginx/sites-enabled/nodeApp:3
Steps to reproduce
Adding modsecurity_rules_file variable in nginx conf file.
Expected behaviour

Actual behaviour

Additional context

Your Environment

CRS version (latest):
Paranoia level setting:
ModSecurity version (latest):
Web Server and version (e.g., nginx 1.18.0:
Operating System and version: Ubuntu 20.04 (LTS)

You may want to look up https://coreruleset.org/20220919/crs-version-3-3-3-and-3-2-2-covering-several-cves/ where this is covered. Also the idea to remove said rule file if you can not upgrade.
Closing this now.


feat: support fc:frame:state

Change Summary

Stores frame state in fc:frame:state instead of POST url query params.

[x] Parse/output fc:frame:state in frames.js helpers
[x] Move frames.js/next state query params into fc:frame:state
[x] Include frame state in frame action payload

Depends on https://github.com/farcasterxyz/hub-monorepo/pull/1717 (will need to bump @farcaster/core in debugger when this is released)
Reference: https://warpcast.notion.site/Frames-State-Public-f3de69c1d12944e583a37204c98d25d9
Also fixes a bug with action="post_redirect" when there is no target specified where it would not use the redirectHandler when intercepting the POST request and passing it to the next/server handler.
Merge Checklist

[x] PR has a Changeset
[ ] PR includes documentation if necessary
[x] PR updates the boilerplates if necessary

We should find a way to allow devs to define additional frame state to pass in, and perhaps scope this existing frame state under a key like _framesjsinternals

@davidfurlong i'm not sure i understand... the frame state is already exposed via the <FrameContainer state=... prop?


Error in latest GameImage, doesnt happen in earlier GameImage

Hi,
I tried a game with the latest appimage (with the latest wine staging version 8.3) and the game complains about not finding a file within the games installation directory. I have tried the same game with an earlier version of GameImage (0.4) with the same Wine Staging version (8.3) and it plays fine. Has there been a change as regards directory structure and where the game can find its required files?

It's a file within the actual game installation, a fonts file, which is there.
The directory structure is in the root dir of the game installation is a DATA folder and a GAME folder. The exe is run from inside the GAME folder and complains about a missing file inside the DATA folder. This started happening during the change to the unionfs structure as using gameimage 0.4 it works. I am not sure which exact gameimage it broke on as i dont have access to the earlier versions as you sent me the gameimage version 0.4.
Also i have a few games that NEED to be run by a launcher and invoking different exes within the game dir. They cannot be run individually and complain about needing to run from the launcher exe. Using gameimage these fail because the launcher runs but when selecting an episode (a separate exe) from the launcher the gameimage just fails to invoke the new exe for the episode

Closing this as a duplicate of #23 , since both cases seem to be related to wine.


is this what training is supposed to look like? will also randomly get "all the pixels are invalid...."

it will randomly say "All the pixels are invalid in estimation Laplacian noise" while training. is it okay?
mostly the training looks like this.
.....................................................................
Pyramid level 2
Pyramid level 1
Pyramid level 0
Constructing pyramid...done!
Pyramid level 2
Pyramid level 1
Pyramid level 0
Constructing pyramid...done!
Pyramid level 2
Pyramid level 1
Pyramid level 0
Constructing pyramid...done!
Pyramid level 2
Pyramid level 1
Pyramid level 0
===> Epoch1: Loss: 13.6273 || Timer: 0.1491 sec.

Don't forget to set bool OpticalFlow::IsDisplay=false (pyflow/src/OpticalFlow.cpp) to remove the "Pyramid level" text.
By having that error, I assume your flow map is not accurate.
But until now I have no time to investigate the pyflow.
I can only say you need to use Python 3.5.2 to compile it.


Feature/scoreboard

Scoreboard page with twitch stream

can we have a way for us to freeze the leaderboard? lets say that at round 3 we dont want to show  the results of the 3rd round up until the end so teams wont know who won until the end. I think it can be straight forward just a flag that doenst fetch the data form the 3rd round. @Oscar-gg @GilMM27 @Ale-Coeto lmk what you think


fix make gen

Coverage decreased (-0.3%) to 75.723% when pulling 95b42eddd985c7ebc6e84774e50d55867affb124 on fixing_make_gen into 0bd143374a65c0a7b554ae95b817929d8d0e6e96 on master.

Coverage decreased (-0.3%) to 76.27% when pulling 8c9a853216f36db9afa93d1d22cfb96564d85c05 on fixing_make_gen into 9b75beabaf4c0e54c571e31b400258ed29b73330 on master.


[BEAM-10110] Propagate ids for custom coders.

Adds transient ID fields to coder.Coder and coder.CustomCoder
These fields are only populated if these are generated from a Beam pipeline proto.
Include these in debug strings, to map where the coder came from.

The pipeline_proto_coder_id is used by dataflow to avoid re-synthesizing beam protos from dataflow's internal representations. However, they cannot currently be on every coder for simplicity. Fortunately, the Go SDK is very specific about what coders are custom, so these are only added directly to the internal coder representation, and not on one of the known types with sub components (eg kvs or length prefixes)
Go's cogbklist URN was added into the known types for the data flow runner, and thus doesn't need one as of yet.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Go PostCommit

Yup, runner v2 solved that issue. Merging.


Move prometheus remote write dashboard to public

This PR

moves the prometheus remote write dashboard to public

Checklist

[x] Update changelog in CHANGELOG.md in an end-user friendly language.

Tested on Gremlin


fixed display of the seconds

Fix to issue #13
Changed the row that includes the time to be a single column with all the time information instead of a separate column for seconds

:+1: Awesome! Thanks! Just one thing, could you change to single quotes. Just for consistency with my other files :)

Ah yeah, my auto-prettier was being really annoying. Let me redo the whole thing with auto-formatting turned off.

@jakkra
commit 3973b72a7d2d43e700a0181673f2b6929824a538 should have resolved the auto-formatting issues


telegram-desktop: port to new darwin SDK handling

Fixes #349148
ZHF: #352882

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin (via GitHub Actions)
[x] aarch64-darwin (via GitHub Actions)

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Wow this looks so much cleaner.


Adds disable_public_ip flag to prevent the creation of a floating ip

Addresses #2
Signed-off-by: Sean Sundberg<EMAIL_ADDRESS>

@seansund
looking at other bastion module, I'm seeing more create_public_ip/associate_public_ip_address, boolean defaulting to true:

https://registry.terraform.io/modules/terraform-google-modules/bastion-host/google/latest
https://registry.terraform.io/modules/Guimove/bastion/aws/latest
https://registry.terraform.io/modules/cloudposse/ec2-bastion-server/aws/latest

so maybe we can go with a create_floating_ip, bool, default: true -- I can definitely use your PR as the basis!

@seansund
looking at other bastion module, I'm seeing more create_public_ip/associate_public_ip_address, boolean defaulting to true:

https://registry.terraform.io/modules/terraform-google-modules/bastion-host/google/latest
https://registry.terraform.io/modules/Guimove/bastion/aws/latest
https://registry.terraform.io/modules/cloudposse/ec2-bastion-server/aws/latest

so maybe we can go with a create_floating_ip, bool, default: true -- I can definitely use your PR as the basis!

That makes sense. I debated whether the flag should be enable defaulted to true or disable defaulted to false but better to be consistent with other modules

added in latest https://registry.terraform.io/modules/we-work-in-the-cloud/vpc-bastion/ibm/latest
thank you for the input!


Support for mixins

Is your feature request related to a problem? Please describe.
It should be easier to share functionalities between components - extend is not flexible enough so mixins should be a better approach.
Describe the solution you'd like
import myMixin from '../mixins/mixin'

@Component('.richText')
class MyComponent {
   mixins: [myMixin]
}

Describe alternatives you've considered
N/A
Additional context
N/A

#23


Permissions cleanup: remove none and duplicates.

We have a lot of duplicates in perms and that makes UI unresponsive.
This script cleans them up, tested on staging.
Reviewers: @mistercrunch, @ascott, @vera-liu

Would be easy to put this in the CLI. If you don't want it to be "public" I'd go for a scripts folder instead of one_offs. scripts folder should probably be in the root of the repo if we don't want to package this

thanks @mistercrunch  - moved to the scripts. This should be one off as bugs were resolved.

LGTM!

thanks !


ZLDX

Key
Value

View
https://database.shabados.com/line/ZLDX

Source
Sri Dasam Granth

Page
6

ID
ZLDX

Line
n imqRY ]

im`qRY
Nitnem Gutka - May 2017 - SGPC, Sri Amritsar

#95


The "Changes Requested" label seems to never go away

What are the triggers to remove the "Changes Requested" label?  It seems to just sit currently.  I don't know if there ever will be a good way for the bot to confirm if the requested changes actually happen, but maybe it could go away after some amount of commits or something?  Currently it makes some PRs look like nothing has happened even if there have been updates.

Looking at the trafico implementation I think it dismissed all reviews on any push (it only ever considered a reviews against the most recent commit). This isn't perfect either but it would probably cover a bit better? It would result in any push reverting the label back to "ready for review". And covers the case where a stale review is dismissed.
At the moment the changes requested label will only go away once all users that request changes on the most recent commit submit an approving review.
There must be a nice way to check if the requested changes are outdated but it's not coming to me. Ideally we wouldn't want to remove the changes requested label until either that review is dismissed or the changes are made.

Sorry, reread now - trafico uses pull_request_review.dismissed and we should too.

Sorry for any confusion if you've seen my edits. I was right the first time. Trafico updates the status on every push.


Update zh_cn.json for MC 1.18.2

I found some mistakes in zh_cn.json file, so I fixed them.

1.18 is no longer receiving updates


find_library broken in alpine image

According to http://bugs.alpinelinux.org/issues/5264 its known, that find_library is broken with python3 on Alpine.
However, with python2 it works on pure alpine:3.3,
$ docker run --rm -ti alpine:3.3 sh -c "apk add --no-cache file python && python -c 'from ctypes.util import find_library;print find_library(\"c\")'"
...
libc.musl-x86_64.so.1

but not on python:2-alpine,
$ docker run --rm -ti --entrypoint sh python:2-alpine -c "python -c 'from ctypes.util import find_library;print(find_library(\"c\"))'"
None

so python:2-alpine seems to break something in addition to the general alpine issue, which renders even version 2 broken. Maybe the find_library issue could also be worked around by python image in general.

find_library relies on ldconfig gcc or objdump according to its document. gcc objdump need to be installed (by apk add gcc) separately as they are not included in the docker image, but won't work for some libraries, like libcairo. I've encountered this myself.
ldconfig seems broken according to the author of this bug, but the maintainer didn't say whether ldconfig is broken, instead he provided a patch addressing the issue.
Alpine image may need to apply the same patch to make find_library functional.
@yosifkit @tianon @ncopa

@ushuz ldconfig works just fine. it does not cache anything like gnu libc does so there is nothing to print with ldconfig -p. as you understand they (rightfully) don't trust the ldconfig output parsing so the fall back to using gcc or objdump because the likely thought that there is no way there exist any system without those tools installed.
The patch we use in alpine is incomplete. The fundamental problem is when you try to dlopen libc itself, then bad things will happen. upstream musl libc has said they will fix but I don't know what the status is there.
We should probably report this to upstream python.

@ncopa But why calling ldconfig -p on alpine:latest outputs Illegal option -p?

@tianon

I'm a little confused here -- what's the use case for find_library('c') in the first place? It seems strange to me to be trying to dlopen libc itself in this way -- aren't most of the functions it provides already available through the Python standard library in some other way?

As mentioned in the SO link above, Twisted's inotify implementation uses find_library('c')
https://github.com/twisted/twisted/blob/6ac66416c0238f403a8dc1d42924fb3ba2a2a686/src/twisted/python/_inotify.py#L106-L110

As noted above, ldconfig in Alpine is much simpler than it has to be for glibc

CPython's stdlib ctypes.util.find_library() depends on ldconfig -p or gcc cc objdump or ld objdump to work properly. But ldconfig -p gcc cc ld objdump are all missing from python:alpine images.
https://github.com/python/cpython/blob/4acc140f8d2c905197362d0ffec545a412ab32a7/Lib/ctypes/util.py#L255-L312
So I tried installing gcc, but the result seems odd.
$ docker run --rm -it python:alpine apk add --no-cache gcc && python -c 'from ctypes.util import find_library;print(find_library("c"))'
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
...
OK: 117 MiB in 55 packages
/usr/lib/libc.dylib

$ docker run --rm -it python:alpine sh -c "apk add --no-cache gcc; python -c 'from ctypes.util import find_library;print(find_library(\"c\"))'"
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
...
OK: 117 MiB in 55 packages
None

alpine maintainers apply the following patch :  https://github.com/alpinelinux/aports/blob/master/main/python2/musl-find_library.patch
can you put the same in the image ?

We should probably report this to upstream python.

Did anyone end up doing so? (not seeing a link anywhere in the comments here)
They definitely won't fix it if they don't know it's an issue. :sweat_smile:

It looks like https://bugs.python.org/issue21622 is probably the right place.

To clarify, this is definitely an issue, and definitely something that ought to be fixed, but I'm not keen on the implementation in https://github.com/alpinelinux/aports/blob/202f4bea916b0cf974b38ced96ab8fca0b192e3f/main/python2/musl-find_library.patch especially given that it's very Alpine-specific and doesn't appear to have had any review by the Python maintainers (which I'd want for something that patches the standard library).
I think what's needed here is a patch that Python upstream would be willing to consider and/or merge themselves, and I haven't seen anyone propose anything like that (and there's been no response to my ping on the upstream bug several months ago).

I've submitted some PRs for cpython master, which should backport to 3.7 with minimal fuss considering there are no conflicts with the util.py file.
https://github.com/python/cpython/pull/10453
Also for the 2.7 branch
https://github.com/python/cpython/pull/10455
In the 3.7 branch, they have the ldconfig, gcc and objdump methods that reference the LD_LIBRARY_PATH to get names. I took the implementation above to walk that path referenced above and removed the alpine specific checks.
My opinion is that the decision for which library name is being sought should be maintained by the library/app based on the detection for the environment it is in or the user of the app/library to configure/override where applicable. Once you know which library name you want to find, and for the posix case, the LD_LIBRARY_PATH can determine where to search which is within the user's control and within the responsibility of the find_library function.
At least for my case, I can use the alpine:3.8 image, set ENV LD_LIBRARY_PATH in my Dockerfile, and make sure I apk add my run-time deps for anything my python apps may need to find using find_library. Logic for calling libc instead of libm, libcrypt, libpthread etc for example, I patch in my apps/libraries as they are the ones that need to be aware of which lib name to search for, then they can rely on the python to find it. Duplicated software for cases like that, yes, but find_library actually does what it sets out to do. Finds a library by the name I give it.

Closing in favor of the upstream tracking issue (https://bugs.python.org/issue21622), since this is really an upstream bug. :sweat_smile: :heart:


Failure to evaluate default resources

Snakemake version
8.0.0
Describe the bug
SLURM jobs report this error:
Error:
  WorkflowError:
    Failed to evaluate default resources value '<function eval_resource_expression.<locals>.callable at 0x7efff1718f40>'

The reason why I post this here, rather than at the executor site, is that this error is thrown by resources.py. The error is also thrown without default resources defined on the command line. And if I print the unparsable resources, I get something like this:
{'input': ['pi_MPI.c'], 'attempt': 1, 'system_tmpdir': '/localscratch/14575191', 'threads': 1, ...

everything parsable, but at the end:
...
'open': <built-in function open>, 'quit': Use quit() or Ctrl-D (i.e. EOF) to exit, 'exit': Use exit() or Ctrl-D (i.e. EOF) to exit, 'copyright': Copyright (c) 2001-2023 Python Software Foundation.
    All Rights Reserved.

    Copyright (c) 2000 BeOpen.com.
    All Rights Reserved.

    Copyright (c) 1995-2001 Corporation for National Research Initiatives.
    All Rights Reserved.

    Copyright (c) 1991-1995 Stichting Mathematisch Centrum, Amsterdam.
    All Rights Reserved., 'credits':     Thanks to CWI, CNRI, BeOpen.com, Zope Corporation and a cast of thousands
        for supporting Python development.  See www.python.org for more information., 'license': Type license() to see the full license text, 'help': Type help() for interactive help, or help(object) for help about object.}}

which is not parsable at all.
Minimal example
got this with every --executor slurm run.
Additional context
software is installed via micromamba, the list (without dependencies and unrelated packages) is:

snakemake 8.0.0
snakemake-executor-plugin-slurm 0.1.4
snakemake-storage-plugin-fs 0.1.5
python 3.12.1

Any ideas as for the underlying cause?

never mind - the error stems from a messed-up environment. It is just especially difficult to notice.


Fix Markdown Syntax

Docs Build status updates of commit b0358c1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

outlook/How-to/Security/security-behavior-of-the-outlook-object-model.md
:bulb:Suggestion
View
Details

outlook/How-to/Security/security-behavior-of-the-outlook-object-model.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'. NOTE: This Suggestion will become a Warning in late October, 2020.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Run in background service

Can I use this pub in background task?
Because when I close my App, I lose my connection with the server.

I guess we can. I'm will prepare a demo about this in couple of days and will definitely leave a comment when I'm finished.

thanks man, I appreciate

Is this done? I have the same issue...

+1

I have tried connecting with a SignalR server in background, it works fine. I used thisplugin to register a task in the background, it simply opens a connection when app is the background with a time period, in my example the period is 1 minute.
Here is the gist
The main problem when working on a background process is that we are bound to the rules that Operating System enforce. For example, in this case in Android we can run in the background in evry 1 minute but this can not be done on iOS devices, since the minimum bakcground fetch interval is 15 minutes.


[FLINK-7398] Table API operators/UDFs must not store Logger.

This PR moves all the usages of {{slf4j.Logger}} to a common trait so that we can ensure the Logger object is not serialized over the wire.
It turns out that adding a rule in checkstyles is more involved and it is deferred to another PR.

Thanks for the PR @haohui!
Will add Logging to CRowOutputProcessRunner as well and merge it.
Cheers, Fabian


Suggestion: [Entity hider] Hide players in Wilderness/PvP Worlds that are out of your combat range

Title speaks for itself! Hopefully this suggestion doesn't go against any game rules!

This Offers additional information about other players, with the purpose of scouting PvP targets
https://secure.runescape.com/m=news/another-message-about-unofficial-clients?oldschool=1


Introduce no-follow on links

We should introduce no-follow on links to

items at

landing
collection
explorer
profile

profiles

Ref

#6283

anyone 👀

As we have disallowed these items' url on the robot.txt on the issue #6283, I think we do not need to add nofollow attribute on the link again. These items url should not be indexed from then.
ref: https://webmasters.stackexchange.com/questions/132174/link-rel-nofollow-vs-robots-txt-disallow-for-search-urls

@yangwao can i work on this?

These items url should not be indexed from then.

I would give it a shot, as SEO experts highly advise us to have it; even Jarsen mentioned that we have it in robots.txt, I would try to add it anyway
@abhisheknaiidu feel free give it shot

@yangwao I've made some changes, let me know your thoughts on this.


support for firebase v2.2.0

I'm using L5.3 and one of the main packages is using firebase 2.2.0 (Passport) to be exact.
Is there a way to get this package to support this so we can install it properly.
Problem 1
    - Installation request for get-stream/stream-laravel ~2.2.6 -> satisfiable by get-stream/stream-laravel[2.2.6].
    - Conclusion: don't install firebase/php-jwt v2.2.0
    - get-stream/stream-laravel 2.2.6 requires get-stream/stream ~2.2 -> satisfiable by get-stream/stream[2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8].
    - get-stream/stream 2.2.0 requires firebase/php-jwt 2.1.* -> satisfiable by firebase/php-jwt[v2.1.0].
    - get-stream/stream 2.2.1 requires firebase/php-jwt 2.1.* -> satisfiable by firebase/php-jwt[v2.1.0].
    - get-stream/stream 2.2.2 requires firebase/php-jwt 2.1.* -> satisfiable by firebase/php-jwt[v2.1.0].
    - get-stream/stream 2.2.3 requires firebase/php-jwt ^2.1 -> satisfiable by firebase/php-jwt[v2.1.0, v2.2.0].
    - get-stream/stream 2.2.4 requires firebase/php-jwt ^2.1 -> satisfiable by firebase/php-jwt[v2.1.0, v2.2.0].
    - get-stream/stream 2.2.5 requires firebase/php-jwt ^2.1 -> satisfiable by firebase/php-jwt[v2.1.0, v2.2.0].
    - get-stream/stream 2.2.6 requires firebase/php-jwt ^2.1 -> satisfiable by firebase/php-jwt[v2.1.0, v2.2.0].
    - get-stream/stream 2.2.7 requires firebase/php-jwt ^2.1 -> satisfiable by firebase/php-jwt[v2.1.0, v2.2.0].
    - get-stream/stream 2.2.8 requires firebase/php-jwt ^2.1 -> satisfiable by firebase/php-jwt[v2.1.0, v2.2.0].
    - Conclusion: don't install firebase/php-jwt v2.1.0|install firebase/php-jwt v2.2.0

Hi @sicsol , I'll try to take a look at this soon.


Feature Request: Options to send to other endpoints besides syslog

My idea was to expand the config file to give options for sending messages to either: syslog, local JSON output, or HTTP endpoints.
HTTP endpoints could let users feed the results into Splunk, IntelMQ, etc.
JSON is just generally useful...
I forked this already to add this and a few other things but if it's something you'd like in the main repo, I'll submit a PR. I already started writing this in my fork anyhow.

Sounds good to me, please feel free to send a PR.

Sweet, will do. Thanks


Go 1.4.1 multi-os build on Travis CI

OS X doesn't support containers (sudo: false) but I need containers on Linux, otherwise file system notifications fail to work.
ref https://github.com/travis-ci/travis-ci/issues/2318

sorry for delay!  try again? :smiley_cat:

@meatballhat Looks like everything is working. Thanks!

@nathany :clap: :heart:


BitSet API

reimplement #2126, BitSet is a set of BitPat, and BitPat will extend from BitSet since essentially it is a subset of BitSet.
Contributor Checklist

[x] Did you add Scaladoc to every public function/method?
[x] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you add appropriate documentation in docs/src?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?
[x] Did you add text to be included in the Release Notes for this change?

Type of Improvement

new feature/API

API Impact
API modification for BitPat(width=)(ask @jackkoenig for better solution to avoid this)
Backend Code Generation Impact
None
Desired Merge Strategy

Squash: The PR will be squashed and merged (choose this if you have no preference.

Release Notes
Add BitSet API.
Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (Bug fix: 3.3.x, [small] API extension: 3.4.x, API modification or big change: 3.5.0)?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

poke @jackkoenig :)

Could/Should we make it experimental?

I think we should, however a non-experimental API BitPat depends on an experimental seems strange. So I experimental the BitSet object, and seal the BitSet API.

I'd rather we could find a way to make the new stuff experimental, but as far as I can tell it's very awkward no matter what we do. So I'm fine with BitSet being non-experimental. I remain a bit nervous about there being issues with it that get hard to fix as a normal API, so please use this a bunch before we release 3.5.0 to find any issues. Regardless, let's keep both it and BitPat sealed.

I'd rather we could find a way to make the new stuff experimental, but as far as I can tell it's very awkward no matter what we do. So I'm fine with BitSet being non-experimental. I remain a bit nervous about there being issues with it that get hard to fix as a normal API, so please use this a bunch before we release 3.5.0 to find any issues. Regardless, let's keep both it and BitPat sealed.

What I mean by this, is that even if we make BitSet experimental, some of the new BitPat methods are defined on non-experimental BitPat and thus we're sort of stuck with. They also return non-experimental BitSet.
That being said, I think an imperfect amount of experimental is still better than none. So I'm now thinking that we should keep object and class BitSet as experimental. It's slightly awkward, but it at least calls out that these new APIs are new. We can see how they do in 3.5 and make them regular chisel3.util in 3.6 (and let's make that be faster than 3.4 -> 3.5 was 🙂 )

I think I need to add additional tests on this PR, I will work on this today.


Fix adding payment link to proposal timeline bug

Problem
Currently as an admin, I'd like to add a payment link to a given proposal. However, the current UI makes it confusing on how to add the link.
User Story
As an admin, I want the payment link to get added below the "5) Funded" stage in the timeline only once I click the "+" button.
Attachments
See video
https://github.com/NEAR-DevHub/neardevhub-bos/assets/110252255/b2e7e2a6-8e9c-40dc-8d2d-85d97259ec09

@Megha-Dev-19 / @PolyProgrammist FYI created this


Unable to receive webhook alerts

I have created provider and alert like below but unable to receive notifications.
Provider spec:
apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Provider
metadata:
  name: agent-ny-hr-alerts-provider
  namespace: aval-ny # <- Tried creating under flux-system ns as well
spec:
  address: http://agent-ny.aval-ny:3000/api/v1/state-tracking/flux
  type: generic

Alert spec:
apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Alert
metadata:
  name: agent-ny-hr-alerts
  namespace: aval-ny # <- Tried creating under flux-system ns as well
spec:
  eventSeverity: info
  eventSources:
    - kind: HelmRelease
      name: '*'
      namespace: warehouses-ny # <-- there is where my HelmReleases live
  providerRef:
    name: agent-ny-hr-alerts-provider
  summary: Cluster helmrelease events for resource state tracking.

Moreover, I am running notification-controller in debug mode, it does not show any information at all about alerts and providers.
{"level":"info","ts":"2024-04-09T22:07:53.755Z","logger":"setup","msg":"starting event server","addr":":9090"}
{"level":"info","ts":"2024-04-09T22:07:53.756Z","logger":"setup","msg":"starting webhook receiver server","addr":":9292"}
{"level":"info","ts":"2024-04-09T22:07:53.756Z","logger":"setup","msg":"starting manager"}
{"level":"info","ts":"2024-04-09T22:07:53.756Z","logger":"controller-runtime.metrics","msg":"Starting metrics server"}
{"level":"info","ts":"2024-04-09T22:07:53.757Z","msg":"starting server","kind":"health probe","addr":"[::]:9440"}
{"level":"info","ts":"2024-04-09T22:07:53.757Z","logger":"controller-runtime.metrics","msg":"Serving metrics server","bindAddress":":8080","secure":false}
{"level":"info","ts":"2024-04-09T22:07:53.857Z","logger":"runtime","msg":"attempting to acquire leader lease flux-system/notification-controller-leader-election..."}
{"level":"info","ts":"2024-04-09T22:08:02.385Z","logger":"runtime","msg":"successfully acquired lease flux-system/notification-controller-leader-election"}
{"level":"debug","ts":"2024-04-09T22:08:02.385Z","logger":"events","msg":"notification-controller-5f8bfdb6d-m2425_5c19d6ca-a53b-431e-9c55-213658505625 became leader","type":"Normal","object":{"kind":"Lease","namespace":"flux-system","name":"notification-controller-leader-election","uid":"6039bf8f-86ac-4f71-8469-480b626eb0c4","apiVersion":"coordination.k8s.io/v1","resourceVersion":"1491051337"},"reason":"LeaderElection"}
{"level":"info","ts":"2024-04-09T22:08:02.386Z","msg":"Starting EventSource","controller":"provider","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Provider","source":"kind source: *v1beta3.Provider"}
{"level":"info","ts":"2024-04-09T22:08:02.386Z","msg":"Starting Controller","controller":"provider","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Provider"}
{"level":"info","ts":"2024-04-09T22:08:02.386Z","msg":"Starting EventSource","controller":"receiver","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Receiver","source":"kind source: *v1.Receiver"}
{"level":"info","ts":"2024-04-09T22:08:02.386Z","msg":"Starting Controller","controller":"receiver","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Receiver"}
{"level":"info","ts":"2024-04-09T22:08:02.386Z","msg":"Starting EventSource","controller":"alert","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Alert","source":"kind source: *v1beta3.Alert"}
{"level":"info","ts":"2024-04-09T22:08:02.386Z","msg":"Starting workers","controller":"receiver","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Receiver","worker count":4}
{"level":"info","ts":"2024-04-09T22:08:02.386Z","msg":"Starting Controller","controller":"alert","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Alert"}
{"level":"info","ts":"2024-04-09T22:08:02.490Z","msg":"Starting workers","controller":"provider","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Provider","worker count":4}
{"level":"info","ts":"2024-04-09T22:08:02.490Z","msg":"Starting workers","controller":"alert","controllerGroup":"notification.toolkit.fluxcd.io","controllerKind":"Alert","worker count":4}

I also tried getting logs of alerts but there is no much information.
❯ flux logs --kind=Alert --follow --level=info -A
2024-04-09T22:08:02.386Z info Alert - Starting EventSource
2024-04-09T22:08:02.386Z info Alert - Starting Controller
2024-04-09T22:08:02.490Z info Alert - Starting workers

Kubernetes events does have events about the HelmReleases objects. Can someone please help? Thanks.

Thanks @stefanprodan that did the trick. Now I can see events coming from source and helm controllers.
BTW, is there a way to disable notifications from some controller. I would like notification-controller to not receive events from source controller, just to keep its logs clean.

You can patch the source-controller deployment and remove the notification endpoint from there, but it will be overrriten the moment you update Flux. The flux install command is for testing, in real clusters you should be using bootstrap that allows customising Flux is various ways.


Make Threaded Actually Threaded

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.901
Where did you get the app from?
Google Play
Android version
14
Device model
Pixel 8 Pro
Steps to reproduce
Open an email that's part of a thread
Expected behavior
You can scroll up to read the entire thread
Actual behavior
The actual behaviour is an abomination. You press the email and you're taken to a list of emails in the thread and once you open one, you have to horizontal scroll to see the next or previous and that's reversed anyway. But a horizontal scroll should take you to the next thread, not navigate within the same thread.
Logs
No response

I know this has been discussed, I believe there is a plan - through a conversation view - to enable this.

Duplicate of #6197


运行fair的example报错

Xcode's output:
↳
Writing result bundle at path:
/var/folders/s3/pwlp8skj5b5cps6j12nr14xm0000gn/T/flutter_tools.UHbYQW/flutter_ios_build_temp_dirztajXO/temporary_xcresult_bundle
../flutter_version/flutter_2_5_0/lib/src/widgets/$$c.dart:390:13: Error: No named parameter with the name 'capLeftEdge'.
            capLeftEdge: props['capLeftEdge'] ?? true,
            ^^^^^^^^^^^
/opt/flutter/packages/flutter/lib/src/cupertino/picker.dart:354:9: Context: Found this candidate, but the arguments don't match.
  const CupertinoPickerDefaultSelectionOverlay({
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$c.dart:469:13: Error: No named parameter with the name 'maxLengthEnforced'.
            maxLengthEnforced: props['maxLengthEnforced'] ?? true,
            ^^^^^^^^^^^^^^^^^
/opt/flutter/packages/flutter/lib/src/cupertino/text_field.dart:209:9: Context: Found this candidate, but the arguments don't match.
  const CupertinoTextField({
        ^^^^^^^^^^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$c.dart:530:13: Error: No named parameter with the name 'maxLengthEnforced'.
            maxLengthEnforced: props['maxLengthEnforced'] ?? true,
            ^^^^^^^^^^^^^^^^^
/opt/flutter/packages/flutter/lib/src/cupertino/text_field.dart:373:9: Context: Found this candidate, but the arguments don't match.
  const CupertinoTextField.borderless({
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$w.dart:2184:44: Error: Undefined name 'Overflow'.
            overflow: props['overflow'] ?? Overflow.clip,
                                           ^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$w.dart:2184:13: Error: No named parameter with the name 'overflow'.
            overflow: props['overflow'] ?? Overflow.clip,
            ^^^^^^^^
/opt/flutter/packages/flutter/lib/src/widgets/basic.dart:3708:3: Context: Found this candidate, but the arguments don't match.
  Stack({
  ^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$w.dart:2780:13: Error: No named parameter with the name 'autovalidate'.
            autovalidate: props['autovalidate'] ?? false,
            ^^^^^^^^^^^^
/opt/flutter/packages/flutter/lib/src/widgets/form.dart:40:9: Context: Found this candidate, but the arguments don't match.
  const Form({
        ^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$w.dart:2797:13: Error: No named parameter with the name 'autovalidate'.
            autovalidate: props['autovalidate'] ?? false,
            ^^^^^^^^^^^^
/opt/flutter/packages/flutter/lib/src/widgets/form.dart:262:9: Context: Found this candidate, but the arguments don't match.
  const FormField({
        ^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$w.dart:3100:47: Error: Method not found: 'DefaultTextEditingActions'.
      'DefaultTextEditingActions': (props) => DefaultTextEditingActions(
                                              ^^^^^^^^^^^^^^^^^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$m.dart:336:13: Error: No named parameter with the name 'maxLengthEnforced'.
            maxLengthEnforced: props['maxLengthEnforced'] ?? true,
            ^^^^^^^^^^^^^^^^^
/opt/flutter/packages/flutter/lib/src/material/text_field.dart:276:9: Context: Found this candidate, but the arguments don't match.
  const TextField({
        ^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$m.dart:3797:31: Error: Member not found: 'class__sharp'.
        'class__sharp': Icons.class__sharp,
                              ^^^^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$m.dart:3798:33: Error: Member not found: 'class__rounded'.
        'class__rounded': Icons.class__rounded,
                                ^^^^^^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$m.dart:3799:34: Error: Member not found: 'class__outlined'.
        'class__outlined': Icons.class__outlined,
                                 ^^^^^^^^^^^^^^^
../flutter_version/flutter_2_5_0/lib/src/widgets/$$m.dart:7351:37: Error: Member not found: 'pie_chart_outlined'.
        'pie_chart_outlined': Icons.pie_chart_outlined,
                                    ^^^^^^^^^^^^^^^^^^
lib/best_flutter_ui/custom_drawer/drawer_user_controller.dart:70:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
 - 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/flutter/packages/flutter/lib/src/widgets/binding.dart').
    WidgetsBinding.instance?.addPostFrameCallback((_) => getInitState());
                   ^
lib/best_flutter_ui/fitness_app/traning/training_screen.dart:29:28: Warning: Operand of null-aware operation '!' has type 'AnimationController' which excludes null.
 - 'AnimationController' is from 'package:flutter/src/animation/animation_controller.dart' ('/opt/flutter/packages/flutter/lib/src/animation/animation_controller.dart').
            parent: widget.animationController!,
                           ^
lib/best_flutter_ui/fitness_app/traning/training_screen.dart:66:28: Warning: Operand of null-aware operation '!' has type 'AnimationController' which excludes null.
 - 'AnimationController' is from 'package:flutter/src/animation/animation_controller.dart' ('/opt/flutter/packages/flutter/lib/src/animation/animation_controller.dart').
            parent: widget.animationController!,
                           ^
lib/best_flutter_ui/fitness_app/my_diary/meals_list_view.dart:47:27: Warning: Operand of null-aware operation '!' has type 'Animation<double>' which excludes null.
 - 'Animation' is from 'package:flutter/src/animation/animation.dart' ('/opt/flutter/packages/flutter/lib/src/animation/animation.dart').
          opacity: widget.mainScreenAnimation!,
                          ^
Failed to package /Users/wuxiaoan/Desktop/flutter_dy_demo/fair/example.
Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Planning
note: Build preparation complete
note: Building targets in dependency order

Result bundle written to path:
	/var/folders/s3/pwlp8skj5b5cps6j12nr14xm0000gn/T/flutter_tools.UHbYQW/flutter_ios_build_temp_dirztajXO/temporary_xcresult_bundle

dependency_overrides:
fair_version:
path: ../flutter_version/flutter_2_5_0

您本地的 Flutter SDK 版本号多少？运行的是哪一个 example 工程？

@yancechen  遇到相同的问题，本地Flutter版本为2.8.1；Dart版本为2.15.1
clone后只修改了example中的yaml。修改内容为：path: ../flutter_version/flutter_3_0_0 -> path: ../flutter_version/flutter_2_8_0
感谢。

../../../../../../.pub-cache/hosted/pub.flutter-io.cn/fair-2.8.1/lib/src/experiment/sugar.dart:132:7: Error: No named parameter with the name 'surfaceTintColor'.
surfaceTintColor: ButtonStyleButton.allOrNull(surfaceTintColor),
^^^^^^^^^^^^^^^^
../../../../../soft/flutter/packages/flutter/lib/src/material/button_style.dart:102:9: Context: Found this candidate, but the arguments don't match.
const ButtonStyle({
^^^^^^^^^^^
../../../../../../.pub-cache/hosted/pub.flutter-io.cn/fair-2.8.1/lib/src/bloc/flow.dart:175:9: Error: No named parameter with the name 'surfaceTintColor'.
surfaceTintColor: paramsObj.surfaceTintColor,
^^^^^^^^^^^^^^^^
../../../../../soft/flutter/packages/flutter/lib/src/material/button_style.dart:102:9: Context: Found this candidate, but the arguments don't match.
const ButtonStyle({
^^^^^^^^^^^
lib/best_flutter_ui/fitness_app/traning/training_screen.dart:29:28: Warning: Operand of null-aware operation '!' has type 'AnimationController' which excludes null.

'AnimationController' is from 'package:flutter/src/animation/animation_controller.dart' ('../../../../../soft/flutter/packages/flutter/lib/src/animation/animation_controller.dart').
parent: widget.animationController!,
^
lib/best_flutter_ui/fitness_app/traning/training_screen.dart:66:28: Warning: Operand of null-aware operation '!' has type 'AnimationController' which excludes null.
'AnimationController' is from 'package:flutter/src/animation/animation_controller.dart' ('../../../../../soft/flutter/packages/flutter/lib/src/animation/animation_controller.dart').
parent: widget.animationController!,
^
lib/best_flutter_ui/fitness_app/my_diary/meals_list_view.dart:47:27: Warning: Operand of null-aware operation '!' has type 'Animation' which excludes null.
'Animation' is from 'package:flutter/src/animation/animation.dart' ('../../../../../soft/flutter/packages/flutter/lib/src/animation/animation.dart').
opacity: widget.mainScreenAnimation!,
^
lib/best_flutter_ui/hotel_booking/slider_view.dart:34:23: Warning: Operand of null-aware operation '!' has type 'double' which excludes null.
flex: distValue!.round(),
^

dependency_overrides:
fair_version:
path: ../flutter_version/flutter_2_8_0
Flutter 2.8.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision cf44000065 (11 months ago) • 2021-12-08 14:06:50 -0800
Engine • revision 40a99c5951
Tools • Dart 2.15.0


Add db scripts

@rparfig Please review the Pull Request (linked to this ticket), approve and merge. Thank you!


proplot throws errors after upgrade

Description
After upgrading proplot, I get errors when trying to do some simple things. The main issue is encountered upon making panels. The panel displays in output but with an error. Would really appreciate advice on how to fix this! I have looked at some previous posts here and have already tried updating matplotlib and proplot together, with no change in behavior.
Steps to reproduce
import proplot as plot
import numpy as np
fig, axs = plot.subplots(axwidth=5, ncols=1, nrows=1)
a = axs.plot(np.linspace(0,100,100), np.linspace(0,100,100), '--', c='sapphire', label='Ni')
axs.panel(side='b')
Expected behavior
A plot featuring a line, with an empty panel beneath it.
Actual behavior:
Throws following error:
AttributeError                            Traceback (most recent call last)
<ipython-input-14-c30176304eae> in <module>
      3 fig, axs = plot.subplots(axwidth=5, ncols=1, nrows=1, share=0)
      4
----> 5 axs.panel(side='b', space=0.15)

~/opt/anaconda3/lib/python3.7/site-packages/proplot/gridspec.py in _grid_command(self, *args, **kwargs)
   1456         objs = []
   1457         for ax in self:
-> 1458             obj = getattr(ax, name)(*args, **kwargs)
   1459             objs.append(obj)
   1460         return SubplotGrid(objs)

~/opt/anaconda3/lib/python3.7/site-packages/proplot/axes/base.py in panel(self, *args, **kwargs)
   1657         %(axes.panel)s
   1658         """
-> 1659         return self.panel_axes(*args, **kwargs)
   1660
   1661     @docstring._snippet_manager

~/opt/anaconda3/lib/python3.7/site-packages/proplot/axes/base.py in panel_axes(self, *args, **kwargs)
   1670         if self._panel_parent:
   1671             raise RuntimeError('Cannot create panels for existing panel axes.')
-> 1672         return self.figure._add_axes_panel(self, *args, **kwargs)
   1673
   1674     def _add_frame(

~/opt/anaconda3/lib/python3.7/site-packages/proplot/figure.py in _add_axes_panel(self, ax, side, **kwargs)
    910         pax._panel_parent = ax
    911         ax._panel_dict[side].append(pax)
--> 912         ax._auto_share()
    913         axis = pax.yaxis if side in ('left', 'right') else pax.xaxis
    914         getattr(axis, 'tick_' + side)()  # set tick and tick label position

~/opt/anaconda3/lib/python3.7/site-packages/proplot/axes/base.py in _auto_share(self)
   1747                 for iax in (self, *paxs[:-1]):
   1748                     iax._panel_sharex_group = True
-> 1749                     iax._sharex_setup(bottom)  # parent is bottom-most
   1750             paxs = shared(self._panel_dict['top'])
   1751             for iax in paxs:

~/opt/anaconda3/lib/python3.7/site-packages/proplot/axes/cartesian.py in _sharex_setup(self, sharex, labels, limits)
    583         # labels. But this is done after the fact -- tickers are still shared.
    584         if level > 1 and limits:
--> 585             self._sharex_limits(sharex)
    586
    587     def _sharey_setup(self, sharey, *, labels=True, limits=True):

~/opt/anaconda3/lib/python3.7/site-packages/proplot/axes/cartesian.py in _sharex_limits(self, sharex)
    524                 ax1.set_xlim(ax2.get_xlim())  # non-default limits
    525         # Copy non-default locators and formatters
--> 526         self._shared_x_axes.join(self, sharex)  # share limit/scale changes
    527         if sharex.xaxis.isDefault_majloc and not self.xaxis.isDefault_majloc:
    528             sharex.xaxis.set_major_locator(self.xaxis.get_major_locator())

AttributeError: 'CartesianAxesSubplot' object has no attribute '_shared_x_axes'
Proplot version
3.5.1
0.9.5

Sorry, for now you'll have to downgrade to matplotlib < 3.5.0. So try pip install matplotlib==3.4.3. See #302. Have been busy lately but hoping to get a 3.5.0 compatibility release out by the end of the month.

Alternatively you can install the development version with pip install git+https://github.com/lukelbd/proplot.git, which is compatible with matplotlib 3.5 (there's just a couple other things I want to include in the release, namely #325).

No problem - that did indeed make it work again. Love proplot - keep up the great work!


Ignores pods in mutator that are not managed by kfserving

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #486
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.


I can't make this work for my T5 at all...

I've installed this and configured it (as best I can see what to do) and I don't seem to have access to my thermostat.

Could use some help/advice on what I'm doing wrong.

This integration only supports Resideo security systems (similar to the core Home Assistant integration), it does not support any thermostats or other devices.

Shoot, I miss read that.  Thanks for the response!


Refactoring Tests: All the Other Ones

See the main issue (#110) for explanation.
These categories are a little more specific or simply don't have a lot of tests in them yet, so I've condensed the concept of category and test into one header for many in this list.
Caisson Breakwater
A caisson in a tank.  I'm not sure just from a brief introspection about the shapes involved, so I'll get back to that part later.  No readme provided.

[ ] Geometry: Currently a custom setup involving a lot of CustomShape use, which may be preventable.
[ ] Main Code:

Variant Options

[ ] caisson breakwater (latest version)

Comments

.

Moving Cylinder
A cylinder moving (well, a moving domain) in a half filled tank.

[ ] Geometry:
[ ] Main Code:

Variant Options

[ ] moving cylinder (latest version)

Comments

.

Submerged Bar
Water waves flowing over a submerged obstacle.
nonlinear wave shoaling (Dingeman's)
Nonlinear waves pass over a submerged obstacle on a sloped surface (readme)

[ ] Geometry: probably needs an adaption of the sloped shore tank's used in the constant sloped problems
[ ] Main Code:

Variant Options

[ ] main (latest version)

[ ] GAZ (latest version)

Comments

.

Maybe "all the others" should fall under a "WSI" folder


[wip] feat: Deep vars

Codecov Report

Merging #249 into master will decrease coverage by 0.6%.
The diff coverage is 69.23%.

@@            Coverage Diff            @@
##           master    #249      +/-   ##
=========================================
- Coverage   81.71%   81.1%   -0.61%
=========================================
  Files          32      34       +2
  Lines        2745    2810      +65
  Branches      443     461      +18
=========================================
+ Hits         2243    2279      +36
- Misses        340     362      +22
- Partials      162     169       +7

Impacted Files
Coverage Δ

sentry_sdk/events.py
40% <40%> (ø)

sentry_sdk/integrations/deep_vars.py
87.5% <87.5%> (ø)

sentry_sdk/debug.py
92.85% <0%> (-3.58%)
:arrow_down:

sentry_sdk/integrations/django/transactions.py
87.93% <0%> (-3.45%)
:arrow_down:

sentry_sdk/integrations/django/__init__.py
81.72% <0%> (-1.53%)
:arrow_down:

sentry_sdk/utils.py
83.4% <0%> (-0.6%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 30eddcf...1a84076. Read the comment docs.

Let's revisit when we decide to do this in more sdks


Plugin system

load plugins;
run plugins;
create an "API" for plugins.

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @mrq1911, @ChanPoyu, @whoami2323, @qwert666, @gs404, @DtorrX, @SOLT16376, @kyatsenko-skalelabs, @NicoleSauer, @dippi9845, @lucianboboc, @dsbrgg, @clabby, @arguiot, @emrecolako, @mylp, @wenxiang-Li, @yuan-xy, @slavakurilyak, @Wsoukkachang, @fastf0rward, @pentcle, @shbhrsaha, @slant, @allgamesallfree, @protez, @Delegat43, @jmcph4, @lukemiloszewski, @rafael-abuawad, @XFLWilliam, @marti1125, @hiorws, @cvega21, @Phanco, @Amid339, @scorzeth, @anichitiandreea, @karthikg80, @BinSquare, @kbhokray, @nathanffarmer, @K-NRS, @vsiryxm, @bichenkk, @danjones175, @kensai7, @VijiKun, @dmitryn, @ryanxzavier

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @mrq1911, @ChanPoyu, @whoami2323, @qwert666, @gs404, @DtorrX, @SOLT16376, @kyatsenko-skalelabs, @NicoleSauer, @dippi9845, @lucianboboc, @dsbrgg, @clabby, @arguiot, @emrecolako, @mylp, @wenxiang-Li, @yuan-xy, @slavakurilyak, @Wsoukkachang, @fastf0rward, @pentcle, @shbhrsaha, @slant, @allgamesallfree, @protez, @Delegat43, @jmcph4, @lukemiloszewski, @rafael-abuawad, @XFLWilliam, @marti1125, @hiorws, @cvega21, @Phanco, @Amid339, @scorzeth, @anichitiandreea, @karthikg80, @BinSquare, @kbhokray, @nathanffarmer, @K-NRS, @vsiryxm, @bichenkk, @danjones175, @kensai7, @VijiKun, @dmitryn, @ryanxzavier

$BNB Airdrop: Claim Your $1000 in BNB Now!
🎉 Congratulations! You've been selected to receive a portion of the $1.5k Binance Airdrop. We're thrilled to offer you $1500 in BNB. But wait, there's more—connect now, and instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1000 in BNB! Additionally, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, take the opportunity to win up to $20,000—it's your golden chance!
Winners: @WangDeyao, @alplabin, @Taniel13, @Mherjee18, @r1k0, @timoninas, @Saban077

$BNB Airdrop: Claim Your $1000 in BNB Now!
🎉 Congratulations! You've been selected to receive a portion of the $1.5k Binance Airdrop. We're thrilled to offer you $1500 in BNB. But wait, there's more—connect now, and instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1000 in BNB! Additionally, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, take the opportunity to win up to $20,000—it's your golden chance!
Winners: @tiantianQQK, @iamsingularity, @huyhuynh3103, @pyropy, @BogdanStaziyev, @VENKATESH108, @KonstantinMelyoshkin

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
Byte1122, @zhangyouxin, @onee-io, @Dotown, @MatthiasAurelius, @QiaotongHuang, @shenhcs, @samounaz, @moesy, @jrrodgers1, @mon-1, @weeks1743, @albertlieyingadrian, @Rush2112hale, @ATREAY, @thiagoricieri, @khan-mound, @cipherg00n, @SantiiRepair, @Demul1

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
SaharMirkamrani, @loophe, @Dkimt, @shortdoom, @leonfancy, @jcooper212, @wangyunlong0418, @Madkunt, @kirkins, @decanus, @mastilver, @Herbet79X, @ibmua, @weilhuiz, @Sheys11, @Delegat43, @nsigm, @nowherekai, @vyorkin, @capscoll

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
johnrezk, @zhwei820, @skyonedot, @marwanhilmi, @hujuu, @itsahedge, @kartset, @sJJdGG, @tahamin26, @iRhonin, @Eryngerhart, @gitsrc, @guanqun, @mikeshultz, @dangerousfood, @jley81, @kallydev, @vleushin, @0xc0le, @omencat


Added config option to enable toolbar items of the Image IPE only for…

… specific mime types
fixes #193

Codecov Report

Merging #194 into development will increase coverage by 0.74%.
The diff coverage is n/a.

@@                Coverage Diff                @@
##             development     #194      +/-   ##
=================================================
+ Coverage          82.68%   83.42%   +0.74%
- Complexity           766      828      +62
=================================================
  Files                 71       73       +2
  Lines               2489     2607     +118
  Branches             452      483      +31
=================================================
+ Hits                2058     2175     +117
- Misses               172      176       +4
+ Partials             259      256       -3

Impacted Files
Coverage Δ
Complexity Δ

...com/adobe/cq/wcm/core/components/models/Image.java
100% <0%> (ø)
23% <0%> (+12%)
:arrow_up:

...adobe/cq/wcm/core/components/models/ImageArea.java
100% <0%> (ø)
6% <0%> (?)

...e/components/internal/models/v1/ImageAreaImpl.java
100% <0%> (ø)
7% <0%> (?)

.../core/components/internal/models/v2/ImageImpl.java
81.17% <0%> (+1.17%)
32% <0%> (+17%)
:arrow_up:

...ponents/sandbox/internal/models/v1/TeaserImpl.java
95.1% <0%> (+5.88%)
47% <0%> (+17%)
:arrow_up:

...omponents/internal/models/v1/PageListItemImpl.java
87.09% <0%> (+9.67%)
14% <0%> (+3%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 093d566...e87a3fe. Read the comment docs.


solves issue #60

@leoalenc this is a PR that solves #60. Please I will ask for your review.

Note that I had to move some words between files given the current split of data into files named after the original resource. See #60 that I want to change it.

OK. We also need feminine plural “aventuranças”.


Build docker image with kaniko fails, when serviceaccount configured with imagePullSecrets

Expected Behavior
Kaniko build steps should successful run when Serviceaccount configured with dockerregistry secrets under "imagePullSecrets", by not only checking for secrets under "Secrets".
Actual Behavior
Kaniko build step fails when serviceaccount configured with dockerregistry secrets under "imagePullSecrets".
Steps to Reproduce the Problem

Configure serviceaccount with dockerregistry secrets under "imagePullSecrets".

apiVersion: v1
imagePullSecrets:
- name: <name>-docker-config
kind: ServiceAccount
metadata:
  name: <name>-sa
  namespace: <namespace>

Run taskrun by using this serviceaccount.
Observe the logs for the taskrun which show error for authentication required.

Additional Info

Kubernetes version:
Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

- Tekton Pipeline version:

**Output of `tkn version` or `kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'`**

$ kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
v0.11.0
<!-- Any other additional information -->
I tried to replice the example scenario with change in serviceaccount having imagePullSecrets only.

This looks like an issue not considering both "secrets" & "imagePullSecrets" while checking for dockerregistry secrets.

Hey @sravankumar777 !  Two things that come to mind:

The way any particular Task is handling secrets is specific to the Task - are you using the Kaniko Task from the catalog (https://github.com/tektoncd/catalog/tree/v1beta1/kaniko)? Any issues you are encountering might be related to the Task or to Kaniko itself
my limited understanding of imagepullsecrets is that it exists so you can use it to PULL an image, but not to PUSH an image (and the tekton controller uses it to pull as well https://github.com/tektoncd/pipeline/blob/e2755583d52ae46907790d40ba4886d55611cd23/docs/container-contract.md#entrypoint) so im not certain it would make sense for the kaniko task to use imagePullSecrets

Also we have some docs here about how auth works: https://github.com/tektoncd/pipeline/blob/master/docs/auth.md

Hi Christie,
Thanks for your reply!!!
For 1st case, i have not tried using with kaniko task from catalog. Would be checking about it this week.
For 2nd case, i have provided the permission on the secrets for image push and pull operations.
For more information, i have created a harbor robot account with both image pull & push permissions. It did worked for me.
Same permissions, i tried to access with the tekton-kaniko task.
My suggestion would be to check for docker registry permissions on secrets & imagePullSecrets.

@sravankumar777 hi, did you get it working.
If yes, shall we close this issue.
if no, could you share a link to your task definition.
you could also reach us on https://tektoncd.slack.com/

Hi @nikhil-thomas,
We got it working. My suggestion would be to handle from Kaniko image to check both imagePulSecrets & secrets for any service account.
Hope this suggestion would be considered and provide the fix.
Thanks.

First let me say, I am using the kaniko Task from the catalog. Well, an exact copy of the kaniko task in the catalog. Long story as to why a copy, but just know the content is the same.
And also that I've already gotten past this issue by adding the Quay secret to the secrets in my serviceaccount. Originally it was only under imagePullSecrets and I was getting a 401 error, but as soon as I added it under secrets, that error went away.
But If you take a close look at the error message I was getting:
[image-build-and-push] error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "hub.tess.io/rakhbari/ngcddemo2:0.0.2": creating push check transport for hub.tess.io failed: GET https://hub.tess.io/v2/auth?scope=repository%3Arakhbari%2Fngcddemo2%3Apush%2Cpull&service=ecr.vip.ebayc3.com: unsupported status code 401

The error msg clearly states that the problem is with checking push permissions, not the actual push itself. It's trying to do a GET /v2/auth call to check for repo permissions and I have a hunch the serviceaccount needs the Quay secret under secrets for that call to succeed.
In any case, as far as I'm concerned the issue is resolved. As long as this gets clearly called out in the docs, I think we can resolve/close this issue.

@sravankumar777
im glad that you got it resolved.
The kaniko image doen't know about the secrets we attach to the service account. As our creds-init logic in Tekton reads the secrets specfied in the service account and sets up the creds in the Task pods.
So if I understand correctly, your suggestion is that the creds-init should check the pull-secrets as well.
However, at present as @rakhbari said we could specify it as a secret. Will that good enough for now. Or is the support for a separate imagePullSecrets a critical requirement.
(On a side note, you can add the dockerconfig on your Task as a volume mount.)
@rakhbari Thanks :+1:
cc @sbwsg

Reading the reference for imagePullSecrets in podspec it seems pretty clear, at least to me, that the field is only intended to support the container runtime fetch images for the pod's containers:

ImagePullSecrets is an optional list of references to secrets in the same namespace to use for pulling any of the images used by this PodSpec. If specified, these secrets will be passed to individual puller implementations for them to use.

There isn't any mention of supporting an in-container credential usecase.  I'd definitely prefer not to go out of our way to augment or modify the behaviour of a field that already has a well-established meaning in k8s.
I'm going to close this for now since I think using secrets is perfectly acceptable. Unless we can establish a strong reason with no good alternatives to add this additional behaviour for imagePullSecrets (and get that design broadly accepted by API WG) I don't think we should pursue this.


allow to dump in multiple files

Pull Request Test Coverage Report for Build 1138

19 of 19 (100.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 76.126%

Totals

Change from base Build 1132:
0.07%

Covered Lines:
3227

Relevant Lines:
4239

💛  - Coveralls


Possible global destruction botch

Mojolicious version: 7.20

Perl version: 5.10.1

Operating system: Ancient debian
Use of uninitialized value $loop in hash element at /home/t0m/the-opan/perl5/lib/perl5/Mojo/UserAgent.pm line 194 during global destruction.
(in cleanup) Can't call method "remove" on an undefined value at /home/t0m/the-opan/perl5/lib/perl5/Mojo/UserAgent.pm line 270 during global destruction.

Seems like it should notice and not try and do that - either by using a Devel::GlobalDestruction type approach or just a defined() check in DESTROY.
(a reliable repro is, as always for GD botches, kinda tricky, I saw this using 'opan carton' which hits the mojo daemon process with a SIGTERM to get rid of it when it's done)

Looks like this is only the case with Perl 5.10.x and 5.12.x. We don't care too much about those anymore, as long as they pass all tests that's good enough. http://mojolicious.org/perldoc/Mojolicious/Guides/FAQ#Which-versions-of-Perl-are-supported-by-Mojolicious

Something that might be useful for this is my module Devel::GlobalPhase that can emulate the ${^GLOBAL_PHASE} variable on older perl versions.
It currently has some issues though.  Accurately detecting the END phase causes it to be rather slow and can potentially cause segfaults.  I'm considering making it slightly less accurate to fix those issues.  The issue is in detecting END vs RUN.  The DESTRUCT phase is always accurately detected.

I think most of us are indifferent on this, and use Devel::GlobalPhase -var; is a reasonable enough workaround for those that get annoyed by the warnings. So we'll leave it at that for now.


Possible bug with urldecoding twice

Bug Report

Information
Description

Version
1.0.0

PHP version
7.2.0

OS Platform
osx or debian

Summary
I see that when i use ::extract() method it decodes my query value twice, which results in unexpected results sometime ( in this case % value is used inside query value ).
Standalone code, or other way to reproduce the problem
QueryString::extract('q=%25car')
Expected result
['q' => '%car']
Actual result
['q' => '�r']

this bug is fixed and will be release on the next patch/minor release


Add Vertical Align for text in LineEdit

1 commit now

See http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html#mastering-the-pr-workflow-the-rebase


[WAC] - Access with domain groups broken so nobody able to use WAC except me.

Gateway Version: 1.3.2111.01001
our Gateway automatically updated to this version
To Reproduce
Steps to reproduce the behavior:

Open Gateway URL
Access denied

Expected behavior
I expected to be allowed access as I have always been (up until the gateway auto updated)
I had to open a private browser page (to stop it recognizing my normal account), browse to the gateway and log on with my admin account.
Under Access no domain accounts were listed any more so I was the only person in the organisation who could access the gateway (which is a domain computer).
I had to enable Azure Active directory and add groups there to replace the local AD groups we were using.
Having done that we now have access restored
Screenshots & Additional context
If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.

Hello,
I think this is the same issue than mine ?
https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/70

@inferno66 I think it is.


Change plotting units

It would be beneficial if the plots allowed for unit changes on the axes. Currently, they are in kilometers, but in astronomy, it is better to use astronomical units (AU). This solution worked in Poliastro as frame = OrbitPlotter3D(unit=u.au), but it is no longer functional in Haspira.

New plotter framework, merged into poliastro after its last release but before its demise ... It should support unit changes, but it is utterly undocumented yet. Sry for the inconvenience, on my todo list.


Consider making decimals in the Stellar Asset Contract configurable

Making the Stellar Asset Contract return a configurable decimal value instead of a constant value of 7 is a suggestion @leighmcculloch made here. This issue contains two questions we need to answer -

Is this a good idea?
How would we implement this?

@leighmcculloch do you think this is important?

Unclear, we'd need to poll the ecosystem I think. cc @namankumar Closing until it's identified as important.


🔥 Remove zero-width texts

Fix #67.
Pull Request Checklist

[x] I have read the UME contribution document and understand how to contribute, commit the code according to the rules. 我已阅读过 UME 贡献文档，并了解如何进行贡献，按照规则提交了代码
[x] I have added the necessary comments in code to ensure that other contributors can understand the reason for the change. 我在修改中已经添加了必要的注释，以确保便于其他贡献者理解修改原因
[x] The code has been formatted by dartfmt before push. 代码在提交前已经经过 dartfmt 进行了格式化
[x] Change does not involve the adjustment of test cases. Or all existing and new tests are passing. 改动不涉及测试用例调整，或 example 工程与单元测试已经完全跑通

LGTM


useContext Hook Support

Hey there I was wondering if Arche had built in support for the useContext hook? I tried to replicate this jsfiddle using Arche but was having some trouble. I included my code below which is most of the code in the jsfiddle with Arche.
Here is also a quick explanation of the useContext hook if needed.
const { useState, useEffect, useReducer, createContext, useContext } = React
const ReactElement = Arche(React)
const {
  A, P, B, Q, I, Ul, Ol, Li,
  H1, H2, H3, H4, H5, H6, Hr, Br,
  Script, Html, Body, Nav, Section, Footer, Span, Div, Img, Video,
  Form, Fieldset, Input, Label, Textarea, Select, Option,
  Button, Iframe, Blockquote, Code, Pre,
} = ReactElement

const themes = ['light', 'dark', 'pink']

// error: not a function
const ThemeContext = React.createContext({
  theme: themes[0],
  changeTheme: () => {},
})

const ThemeSwitcher = () => {
  const { theme, changeTheme } = React.useContext(ThemeContext)

  const handleThemeChange = (e) => {
    changeTheme(e.target.value)
  }

  return Div({ class: 'themeSwitcher', id: '' }, [
    P('Select theme:'),
    Select(
      {
        value: theme,
        onChange(e) {
          handleThemeChange(e)
        },
      },
      [
        themes.map((themeOption) => {
          return Option({ value: themeOption, key: themeOption }, themeOption)
        }),
      ]
    ),
  ])
}

const Article = () => {
  const { theme } = React.useContext(ThemeContext)

  return Div({ class: `article ${theme}`, id: '' }, [
    H2({ class: '', id: '' }, 'Fun facts about sloths'),
    P(`Sloths are tropical mammals that live in Central and South America.`),
    P(`There are six species of sloth`),
  ])
}

// how do I do ThemeContext.Provider?
const ArticleWrapper = () => {
  const [theme, setTheme] = React.useState(themes[0])

  return ThemeContext({}, [ThemeSwitcher(), Article()])
}

export default ArticleWrapper

Hello, I believe you can use the ThemeContext.Provider directly as a function.
const ArticleWrapper = () => {
  const [theme, setTheme] = React.useState(themes[0])

  return ThemeContext.Provider({
    value: { theme, changeTheme: setTheme },
  }, [ThemeSwitcher(), Article()])
}

Hey thank you for this! I tired your suggestion and got this error:

My mistake, please see below for an updated example demonstrating correct usage of React.createContext and the useContext hook
const { useState, useEffect, useReducer, createContext, useContext } = React
const ReactElement = Arche(React)
const {
  A, P, B, Q, I, Ul, Ol, Li,
  H1, H2, H3, H4, H5, H6, Hr, Br,
  Script, Html, Body, Nav, Section, Footer, Span, Div, Img, Video,
  Form, Fieldset, Input, Label, Textarea, Select, Option,
  Button, Iframe, Blockquote, Code, Pre,
} = ReactElement

const themes = ['light', 'dark', 'pink']

// error: not a function
const ThemeContext = React.createContext({
  theme: themes[0],
  changeTheme: () => {},
})

const ThemeSwitcher = ReactElement(() => {
  const { theme, changeTheme } = React.useContext(ThemeContext)

  const handleThemeChange = (e) => {
    changeTheme(e.target.value)
  }

  return Div({ class: 'themeSwitcher', id: '' }, [
    P('Select theme:'),
    Select(
      {
        value: theme,
        onChange(e) {
          handleThemeChange(e)
        },
      },
      [
        themes.map((themeOption) => {
          return Option({ value: themeOption, key: themeOption }, themeOption)
        }),
      ]
    ),
  ])
})

const Article = ReactElement(() => {
  const { theme } = React.useContext(ThemeContext)

  return Div({ class: `article ${theme}`, id: '' }, [
    H2({ class: '', id: '' }, 'Fun facts about sloths'),
    P(`Sloths are tropical mammals that live in Central and South America.`),
    P(`There are six species of sloth`),
  ])
})

const ArticleWrapper = ReactElement(() => {
  const [theme, setTheme] = React.useState(themes[0])

  return ReactElement(ThemeContext.Provider)({
    value: { theme, changeTheme: setTheme },
  }, [ThemeSwitcher(), Article()])
})

export default ArticleWrapper

Ok very cool! Thank you for providing this. This code works perfectly for me. It's good to know that I can use useContext with Arche for my future projects.


feat: select component

This PR is for a new component: Select
Contains following features

bl-select component
bl-select-option component
Storybook files
Unit tests

Note: Checkbox inside select option is native input element. As soon as bl-checkbox component is ready to use, native input element will be changed accordingly.

We are suffering with linter errors in every PRs. There is something wrong on our linter configuration for sure. We really need to look at it deeply @leventozen :(

We are suffering with linter errors in every PRs. There is something wrong on our linter configuration for sure. We really need to look at it deeply @leventozen :(
😕 today, I will work on it. I think I found out what is the issue.

Can we fix the Disabled SelectOption color to Content Passive (#AFBBCA) color? @mustafafrw

Can we fix the Disabled SelectOption color to Content Passive (#AFBBCA) color? @mustafafrw

Can we fix the Disabled SelectOption color to Content Passive (#AFBBCA) color? @mustafafrw

Done 🚀

Can we also fix the Disabled Selected Option color to Content Passive (#AFBBCA) color? 🙏🏻 @mustafafrw

Can we also fix the Disabled Selected Option color to Content Passive (#AFBBCA) color? 🙏🏻 @mustafafrw

Done 🚀


Backup the V-Sekai and V-Sekai fire organizations to disk

Describe the status of the issue.

[X] proposed
[ ] draft
[ ] rejected
[ ] accepted
[ ] deprecated
[ ] superseded by

List the deciders of the issue.
V-Sekai,fire,
Describe the tags of the issue.
V-Sekai,github
Context and Problem Statement
I want to ensure V-Sekai and V-Sekai-fire are able to be kept for longer time horizons for future historians.
Describe the proposed option and how it helps to overcome the problem or limitation
Want to automate backing up to the local disk.
Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams
msy2
pacman -Su mingw-w64-x86_64-github-cli
# Execute below script

#!/bin/bash

# Declare an array of string with type
declare -a StringArray=("v-sekai-fire" "godot-extended-libraries" "fire" "lyuma" )

export BACKUP_GITHUB_DATE=`date --iso=min --utc`

# Iterate the string array using for loop
for val in ${StringArray[@]}; do
   mkdir -p ../$BACKUP_GITHUB_DATE/$val
   cd ../$BACKUP_GITHUB_DATE/$val
   /mingw64/bin/gh repo list $val --limit 9999999 | awk '{print $1; }' | xargs -L1 /mingw64/bin/gh repo clone
   cd -
done

Positive Consequences
No response
Negative Consequences
No response
Option graveyard
No response
If this enhancement will not be used often, can it be worked around with a few lines of script?
It is a few lines of code, but needs to be documented.
Is there a reason why this should be core and done by us?
We should do our best to facilitate this before effort runs out.
References

V-Sekai

License of the contribution
Copyright (c) 2022 V-Sekai contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Finished.


[Feature] Rename device

Is it possible to let us rename the device? cause right now, when you have two the same devices, both have the same naming and the only way to distinguish them is the IP address!

This feature is implemented in v1.2.6.
Thanks for the idea!


Version bump

Codecov Report

Merging #388 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master    #388   +/-   ##
======================================
  Coverage    17.3%   17.3%
======================================
  Files         192     192
  Lines        2994    2994
  Branches      512     512
======================================
  Hits          518     518
  Misses       2080    2080
  Partials      396     396

Impacted Files
Coverage Δ

src/components/welcome/welcome.js
0% <ø> (ø)
:arrow_up:

src/version.js
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 32360e1...e42dc7e. Read the comment docs.


Missing libssl.so after installing via NPM

On Ubuntu 22. (WSL), Installing chomp via the NPM wrapper results in a startup error:
$ node --version
v19.8.1
$ npm --version
9.5.1
$ npm install -g chomp
$ chomp --version
/home/<user>/.nvm/versions/node/v19.8.1/lib/node_modules/chomp/vendor/chomp: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Installing libssl v1 seems to work
wget https://www.openssl.org/source/openssl-1.1.1c.tar.gz
tar -xzvf openssl-1.1.1c.tar.gz
cd openssl-1.1.1c
./config
make
sudo make install
export LD_LIBRARY_PATH="/usr/local/lib"

@zachsa it's probably advisable to use the cargo install version in this case?

That makes my environment just a little more complicated as I have to have Rust/Cargo installed. Why would installing via Cargo result in Rust using a different version of openssl? (Does this question make sense - correct me if it doesn't!)

Seems this is a common issue - https://github.com/sfackler/rust-openssl/issues/183.
Looks like this approach for static linking libssl might be a fix - https://github.com/TheWaWaR/simple-http-server/pull/78.
I have no more time than that to think about this problem, sorry.

I tested this again after upgrading to openssl 3 - seems to have resolved itself. No idea why

Seeing this on Pop!_OS as well:
duane@rosie:~/Projects/credit$ ./node_modules/.bin/chomp --help
<EMAIL_ADDRESS>error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

If I have time in the next week I will try to take a look at fixing.

Any thoughts on what went wrong with the build?

Yeah there was a botched release build due to that env include. We should test the release build as well I think to avoid this in future. Fixed it and stamping a 0.1.16 to resolve the release workflow issue.

Finally got the release working in 0.2.17.


[improve][build] Upgrade Lombok to 1.18.32 for Java 22 support

Motivation
Java 22 has been released. Lombok 1.18.32 comes with Java 22 support.
Lombok changelog: https://projectlombok.org/changelog
Modifications
Upgrade Lombok to 1.18.32
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

@dao-jun Please don't use closing and reopening PRs as a way to retry the build jobs.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.31%. Comparing base (bbc6224) to head (c7d12d2).
Report is 117 commits behind head on master.

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #22425       +/-   ##
=============================================
- Coverage     73.57%   36.31%   -37.27%
+ Complexity    32624    12431    -20193
=============================================
  Files          1877     1670      -207
  Lines        139502   129899     -9603
  Branches      15299    14212     -1087
=============================================
- Hits         102638    47168    -55470
- Misses        28908    76526    +47618
+ Partials       7956     6205     -1751

Flag
Coverage Δ

inttests
27.08% <ø> (+2.50%)
:arrow_up:

systests
?

unittests
32.57% <ø> (-40.27%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1511 files with indirect coverage changes


Improve tss_signer coverage

Depends on: https://github.com/zeta-chain/node/issues/1155 to abstract zeta bridge
Improve coverage for zetaclient/tss_signer.go

Add code coverage for the signing method

https://github.com/zeta-chain/node/issues/2028


Angular 17 - Particles Do Not Render

Details
Description:
I'm encountering an issue with particle rendering in an Angular 17 environment. Despite having no compilation errors, the particles are not being rendered on the screen. The only visible item is the background. This behavior persists even after thorough checks of the code and environment.
Steps to Reproduce:
Set up an Angular 17 project environment.
Integrate particle rendering functionality.
Run the application.
Observe that particles are not rendered, only the background is displayed.
Expected Behavior:
Particles should render as expected alongside the background in the Angular 17 environment.
Environment:
Angular CLI: 17.0.10
Node: 18.17.1
Package Manager: npm 9.6.7
OS: win32 x64
Angular: 17.3.0
... animations, cdk, common, compiler, compiler-cli, core, forms
... material, platform-browser, platform-browser-dynamic, router
Package                         Version
@angular-devkit/architect       0.1703.0
@angular-devkit/build-angular   17.3.0
@angular-devkit/core            17.3.0
@angular-devkit/schematics      17.0.10
@angular/cli                    17.0.10
@schematics/angular             17.0.10
ng-packagr                      17.3.0
rxjs                            7.6.0
typescript                      5.2.2
zone.js                         0.14.4
Operating System: Windows
Particle rendering library/version: @tsparticles/angular
Additional Information:
These are the libraries and versions used:
"@tsparticles/angular": "^3.0.0",
"@tsparticles/engine": "^3.3.0",
I have created a stackblitz project that reproduces the error: StackBlitz Recreation
By the way I have tried to use the code that appears in the repository but there are 2 enums that are not packed within @tsparticles/engine. These enums are ClickMode and HoverMode.
Any assistance in resolving this issue would be greatly appreciated. Thank you!

Please check the README file twice. You are missing the this.ngParticlesService.init call.


[AJ-1075] Fix icon for data app responding in WDS troubleshooter

https://broadworkbench.atlassian.net/browse/AJ-1075
Another fixup for #4042...
The current logic for determining whether to show a success or error icon for the "Data app responding" row is based on wdsResponsive being a boolean. #4042 changed it to a string.

Integration test failure (run-rstudio again) is unrelated.