Too many request

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[ ] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS:
- Continue:
- IDE:

Description
Continue error: HTTP 429 Too Many Requests from https://proxy-server-blue-l6vsfbzhba-uw.a.run.app/stream_chat  {"message":"Too many requests. Please try again later."}
To reproduce

Log output
No response

Even I am facing the same.

@Adityagaddhyan @ruthcyg @AkshatSoni26 This should now be solved as long as you are on the latest version. It was mistaken rate limiting as we were attempting to prevent abuse.
Note that this will never happen if you use your own personal API key or a local model

Closing this as a duplicate of https://github.com/continuedev/continue/issues/993

Encountered the same problem, and do not have their own local large model, how to deal with it？


remove componentWillMount/WillReceiveProps

componentWillMount and componentWillReceiveProps are no longer supported by React

Maybe something like this ?
When a component updates, the instance stays the same, so that state is maintained across renders. React updates the props of the underlying component instance to match the new element, and calls UNSAFE_componentWillReceiveProps(), UNSAFE_componentWillUpdate() and componentDidUpdate() on the underlying instance.
Next, the render() method is called and the diff algorithm recurses on the previous result and the new result.

Note:
These methods are considered legacy and you should avoid them in new code:

UNSAFE_componentWillUpdate()
UNSAFE_componentWillReceiveProps()

Maybe something like this ?
When a component updates, the instance stays the same, so that state is maintained across renders. React updates the props of the underlying component instance to match the new element, and calls UNSAFE_componentWillReceiveProps(), UNSAFE_componentWillUpdate() and componentDidUpdate() on the underlying instance.
Next, the render() method is called and the diff algorithm recurses on the previous result and the new result.

Note:
These methods are considered legacy and you should avoid them in new code:

UNSAFE_componentWillUpdate()
UNSAFE_componentWillReceiveProps()

Seems good to me :+1:

Seems good to me :+1:

Thanks!

Thanks!


Lifetimes do not match method in trait

Describe the bug
When you copy one of the examples or in general use the 'implement missing members' of rust-analyzer you'll get error[E0195]: lifetime parameters or bounds on method '<method>' do not match the trait declaration. This could be related to the removal of async_trait, I assume?
To Reproduce
Steps to reproduce the behaviour:

Copy example into crates main.rs
run cargo check
See above error.

Expected behaviour
It works without manually researching on the error.
Additional context
rustc --version --verbose

rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-pc-windows-msvc
release: 1.76.0
LLVM version: 17.0.6

[package]
name = "actor-test"
version = "0.1.0"
edition = "2021"

[dependencies]
# ractor = "0.9" -> doesn't work either
ractor = { git = "https://github.com/slawlor/ractor", branch = "main" }
rand = "0.8.5"
tokio = { version = "1.36.0", default-features = false, features = ["rt-multi-thread"] }
tracing = "0.1.40"
tracing-glog = "0.3.0"
tracing-subscriber = { version = "0.3.18", features = ["env-filter"] }

Example used: https://github.com/slawlor/ractor/blob/main/ractor/examples/monte_carlo.rs

The reason is you haven't disabled the use of the async-trait feature on ractor, which is a default feature. If you want to use the new async fn in traits functionality, you have to bring ractor to the same.
The default mode, in order to not break backwards compatibility and while we assess the impact of not boxing the futures, is to continue using async-trait for the time being

Related #202


Restructure repository to be pip install-able

Hi there @ks00x, I came across this repo via @reetuelzajoseph and the SEM mapping tool, and would love to integrate it as an example in our MaRDA metadata extractors working group. As such, I've made this PR to make the current code pip installable, but I have a few questions.

First things first, are you happy with me doing this? If you'd prefer I can just maintain this work on my fork.
Relatedly, what license would you like to apply to this repo as it stands? Currently it is unlicensed which heavily restricts re-use. I think technically I shouldn't even be allowed to make a fork of unlicensed code! (see e.g., https://choosealicense.com/no-permission/)
Finally, if you are interested, I'm happy to add some tests and make a PyPI release for this, which should make it much easier for others to reuse. We don't have a Zeiss in the labs I work with but would be great to compare to Oxford instruments etc and other extractor codes.

Hi Matthew
I am not 100% sure if I did things correctly but I added a license file and did the merge request. In any case I am happy with whatever you do with the code!
Kind regards
Klaus
From: Matthew Evans @.>
Sent: 22 January 2024 13:02
To: ks00x/zeiss_tiff_meta @.>
Cc: Klaus Schwarzburg @.>; Mention @.>
Subject: [ks00x/zeiss_tiff_meta] Restructure repository to be pip install-able (PR #1)
Hi there @ks00xhttps://github.com/ks00x, I came across this repo via @reetuelzajosephhttps://github.com/reetuelzajoseph and the SEM mapping tool, and would love to integrate it as an example in our MaRDA metadata extractors working grouphttps://github.com/marda-alliance/metadata_extractors. As such, I've made this PR to make the current code pip installable, but I have a few questions.

First things first, are you happy with me doing this? If you'd prefer I can just maintain this work on my fork.
Relatedly, what license would you like to apply to this repo as it stands? Currently it is unlicensed which heavily restricts re-use. I think technically I shouldn't even be allowed to make a fork of unlicensed code! (see e.g., https://choosealicense.com/no-permission/)
Finally, if you are interested, I'm happy to add some tests and make a PyPI release for this, which should make it much easier for others to reuse. We don't have a Zeiss in the labs I work with but would be great to compare to Oxford instruments etc and other extractor codes.

You can view, comment on, or merge this pull request online at:
https://github.com/ks00x/zeiss_tiff_meta/pull/1
Commit Summary

f4316f6https://github.com/ks00x/zeiss_tiff_meta/pull/1/commits/f4316f63bcaf4fb2a37998cc52563ab128bd2553 Restructure package
5c5a45fhttps://github.com/ks00x/zeiss_tiff_meta/pull/1/commits/5c5a45f42fd0c3c9ff326c3409e1d109588135ac Add README note
128d503https://github.com/ks00x/zeiss_tiff_meta/pull/1/commits/128d503736c8f88bfe6797c63a261e906314f919 Add pyproject.toml
1c7a100https://github.com/ks00x/zeiss_tiff_meta/pull/1/commits/1c7a100e6b6cece3307b30b41a04f22824a28882 Add version number
7cc6df1https://github.com/ks00x/zeiss_tiff_meta/pull/1/commits/7cc6df122c19a37e33a9f6cf6c44f0468979c7b8 Use platform-independent paths
eda3ed5https://github.com/ks00x/zeiss_tiff_meta/pull/1/commits/eda3ed5c08364be5694899c09654aac4f9e1c1f0 Include test data in built package

File Changes
(6 fileshttps://github.com/ks00x/zeiss_tiff_meta/pull/1/files)

M README.mdhttps://github.com/ks00x/zeiss_tiff_meta/pull/1/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5 (5)
A pyproject.tomlhttps://github.com/ks00x/zeiss_tiff_meta/pull/1/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711 (31)
D zeisstiffmeta.pyhttps://github.com/ks00x/zeiss_tiff_meta/pull/1/files#diff-5bf2fa307fa412343990b8dee115a8ca119e622c24a6f1e080c1986d0fddafd9 (192)
R zeisstiffmeta/init.pyhttps://github.com/ks00x/zeiss_tiff_meta/pull/1/files#diff-4ee6ad54e79ad93107d35b40f0c61a07453a0b4457cae857dab6c42b9f1bd856 (4)
R zeisstiffmeta/test.tifhttps://github.com/ks00x/zeiss_tiff_meta/pull/1/files#diff-273752a338ab987283fb052eb9c1c6947daafa4d7989581cae14f9ba94d362f8 (0)
A zeisstiffmeta/zeisstiffmeta.pyhttps://github.com/ks00x/zeiss_tiff_meta/pull/1/files#diff-e2dac4e03ead043d888a60a5b5b59f3439e73dd88e6c17071e6c00614b886ce6 (233)

Patch Links:

https://github.com/ks00x/zeiss_tiff_meta/pull/1.patch
https://github.com/ks00x/zeiss_tiff_meta/pull/1.diff

Reply to this email directly, view it on GitHubhttps://github.com/ks00x/zeiss_tiff_meta/pull/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJBLLUU6MHK2U2F3ISKC3J3YPZILHAVCNFSM6AAAAABCFCRGU2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4TGNZVHE3DKMY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Thanks! In that case I will just open a PR that removes the note I added in the README, and will try to go from there.


⚠ Redacted has degraded performance

In 8a4f0f9, Redacted ($RED) experienced degraded performance:

HTTP code: 200
Response time: 6759 ms

Resolved: Redacted performance has improved in 4d57170.


Internet Explorer issue (integrations)

Internet Explorer issue (integrations)
The following example in IE11:
http://datapackagist.okfnlabs.org/base/from/?url=http%3A%2F%2Fdatahub.io%2Fapi%2Faction%2Fpackage_show%3Fid%3Dpopulation-number-by-governorate-age-group-and-gender-2010-2014
gives SCRIPTS: Access is denied.
File: okf-panel.html, Line 1, Column 1

The package data on the left populates but the JSON on the right is empty:

My environment is:
Windows 8.1
Internet Explorer 11.0.9600.17937
I think this issue relates to IE's policies around cross site scripting.  Having this functionality working smoothly in IE is an important use case for UK public sector adoption of the tool.

@gvidon we would like to get down even to IE9 support if possible. Can you please address this and let us know. Definitely, I'd expect IE10 and 11 to work pretty much as part of the core code functionality, and maybe IE9 with some additional, targeted polyfills, etc.

@gvidon any progress here?

@pwalsh not yet, I had problems with launching IE9 in VM locally and switched to other tasks.

#180


[Docs] Delete model deployment after testing.

Is your feature request related to a problem? Please describe.
There is no delete instructions in the quickstart guide currently. However, this is a feature we already support.
Describe the solution you'd like
Add delete instructions to examples, wherever appliable.

@future-xy This issue could be closed.


DEV: lint: disable UP031

Reference issue
gh-21972
What does this implement/fix?
ruff has improved their detection again (🎉) but that means we are once again exposed in the form of red CI :) so we disable the rule here and someone can fix the issues up to close gh-21972.
Additional information

self-merging to unblock CI


ToDO: missing red text on NULL fields in 'Add Tree' AND enable user to save data entries and enter another

ToDO : Our current build has 1 shipblocker.  It can be described in two parts.

For some reason there is missing red text for the NULL fields - note: this was entered FOR EVERY FIELD and has been working since the completion on #34 .)

Also odd - this was captured by the same Android user - using the below dropbox video.... but I'll explain here as well.

If you fill out the form to add a tree, and fill it out completely, you can Calculate Tree Benefits and Save with no issue as many times as you'd like.
However, if you forget to fill out one of the fields and click Calculate Tree Benefits and Save, nothing happens and no error is visible(see part 1 of this ticket).
From that point on, the Calculate Tree Benefits and Save button does not appear to do anything,  even if you fill out the form completely. Even if you clear out the current form and start over, it still won't do anything. The only way to get it working again is to restart the app.
Here is a video (with audio) of the error:
https://www.dropbox.com/s/1w8ebfwy71ry1aq/IMG_8189.MOV?dl=0

Hi @bestw07  @TreeMama
Have a better viable fix. Please accept my(Rimnesh Fernandez) Upwork proposal and I will be happy to share.
Thanks

Pardon me. I mean no offence to any.

The change made above will fix the 2nd issue - Could add a tree first time, but if tried to add again after that without killing the app, nothing happens.
Justification: It is because
useEffect(() => {
    ; (async function () {
      console.log('loadBenefitsCall ===', loadBenefitsCall)
      if (loadBenefitsCall) {
        await loadBenefits()
      }
    })()
  }, [loadBenefitsCall])

This method will only be triggered if loadBenefitsCall value has changed.
On initial render the loadBenefitsCall is false. When first tree is added it is changed to true, but when tried to add a tree again, it is again set to true. true -> true - no change. Hence await loadBenefits() will not be called.

appears resolved as of 1/19/23 v 4.0.2 (69)


Unable to use pyside6-uic generated UI file

Nuitka version, full Python version, flavor, OS, etc. as output by this exact command.
2.4.8
Commercial: None
Python: 3.12.5 (main, Aug  6 2024, 19:08:49) [Clang 16.0.6 ]
Flavor: Unknown
Executable: /Users/elct9620/Workspace/Finlab/quill/.venv/bin/python
OS: Darwin
Arch: arm64
macOSRelease: 14.5

How did you install Nuitka and Python
# Setup Python
devbox init
devbox add<EMAIL_ADDRESS>devbox add poetry
devbox add clang

# Setup Nuitka
poetry add nuitka

The specific PyPI names and versions
Package               Version Location                                                                                Installer
--------------------- ------- ------------------------------------------------------------------------------------------------ ------------
argon2-cffi           23.1.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
argon2-cffi-bindings  21.2.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
behave                1.2.6   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
cffi                  1.17.1  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
docstring-to-markdown 0.15    /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
fugle-trade           1.2.0   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
fugle-trade-core      2.1.0   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
importlib_metadata    8.5.0   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
jedi                  0.19.1  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
keyring               23.5.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
keyrings.cryptfile    1.3.8   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
Nuitka                2.4.8   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
ordered-set           4.1.0   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
parse                 1.20.2  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
parse_type            0.6.3   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
parso                 0.8.4   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
pip                   24.0    /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        pip
pluggy                1.5.0   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
poetry                1.8.3   /nix/store/vzr6bly4qcqrqr661gqpfy2mapm8d30l-python3.12-poetry-1.8.3/lib/python3.12/site-packages
pycparser             2.22    /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
pycryptodome          3.20.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
PySide6               6.7.2   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
PySide6_Addons        6.7.2   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
PySide6_Essentials    6.7.2   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
python-lsp-jsonrpc    1.1.2   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
python-lsp-server     1.12.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
ruff                  0.6.7   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
shiboken6             6.7.2   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
six                   1.16.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
ujson                 5.10.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
websocket-client      1.8.0   /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
zipp                  3.20.2  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3
zstandard             0.23.0  /Users/elct9620/Workspace/Finlab/quill/.venv/lib/python3.12/site-packages                        Poetry 1.8.3

Many times when you get an error from Nuitka, your setup may be special
N/A
Also supply a Short, Self Contained, Correct, Example

Create an example UI file following the example (https://doc.qt.io/qtforpython-6/tutorials/basictutorial/uifiles.html)
Run pyside6-uic -o ui_mainwindow.py mainwindow.ui to generate ui_mainwindow.py
Import it from main.py and package with Nuitka

Provide in your issue the Nuitka options used
nuitka main.py --onefile --plugin-enable=pyside6

Note if this is a regression
Yes, each time running the standalone binary raises this error
AttributeError: 'MainWindow' object has no attribute 'objectName'. Did you mean: 'object_name'?

The pyside6-uic generate code didn't use snake_case feature. But when packaged with Nuitka always enables it and is unable to disable.

You wrote:

The pyside6-uic generate code didn't use snake_case feature. But when packaged with Nuitka always enables it and is unable to disable.

How would you normally disable it snake_case with pure Python? Is that a runtime toggle of PySide6?

@kayhayen
I run with python main.pyin directly and it works correctly.
To locate the issue, I tried to add this line into pyside6-uic generated ui_mainwindow.py file and saw the same error after I package with Nuitka.
from __feature__ import snake_case

https://doc.qt.io/qtforpython-6/developer/feature-motivation.html
I guess PySide6 didn't use it by default, but for some unknown reasons enabled this feature after packaging it.

Maybe the created binary is reading some sort of Qt configuration on your machine, that it ought not to, but I cannot reprocuce it with the steps given, it just works correctly for me.

If you figure out, which and what Qt configuration file this is caused by, we should check out ways to make Nuitka ignore that part, but https://doc.qt.io/qtforpython-6/developer/feature-motivation.html doesn't indicate that such files play a role.


Use pkg-config to find llama-cpp libs

Hi first of all, thank you for ollama, its amazing !
Im one of the person trying to maintain this on nixos. Since 0.1.19 i think llama-cpp is directly included as a submodule in the repo. Also the .so objects are directly referenced by path in the go build files. Would it be possible to use pkg-config to find those files ?
This would make building ollama from source much easier as llama-cpp can just be specified as a dependency.
I understand that you might have a million more important things to do, i just want to start the discussion.

We've switched to a vendored model for llama.cpp as we need to apply patches for it to work with Ollama.  Using an unmodified upstream version of llama.cpp wont be possible.  You should give the new build process a try.
https://github.com/ollama/ollama/blob/main/docs/development.md#transition-to-go-runner


Support Javascript as input

Allow to use Javascript files as input, filling JsDoc comments with types inferred from their dependencies. I'm not worried too much about having a lot of any types as far as it generates the JsDoc comments with all parameters and return type, so later I can keep improving them by hand. If possible, do it replacing the actual files in place. Is that possible? Does it falls on scope of this project? If not, is there any one that can do this? I would not like to move to Typescript just for typing, and creating all the JsDoc comments by hand is tyring...

If I'm understanding correctly, this sounds like something your editor should be capable of doing? JetBrains IDEs have Infer JSDoc from usage, VS Code is also capable of generating JSDoc for you.

It's not the same, IDE support is just helpers to add JsDoc comments, one by one. What I want is a CLI tool that can add all of them at once (modules, classes, methods, variables...), also if being redundant, and since ts-to-jsdoc can do it from TypeScript code by inferring the types, do the same with Javascript files.

Gotcha.
@piranna Does an extension like Document This cover that? I'm not opposed to implementing this (depending on how useful the type info we can get out of a JS file even is), but I want to make sure existing work isn't being unnecessarily duplicated.

Does an extension like Document This cover that?

Almost! :-) It seems the logic is there, in fact it also detect and fills the Typescript interface in the function argument, but you need to go over all classes, modules, functions and methods one-by-one, instead of filling all of them at once. Also the fact that the repo is archived and link to VSCode Marketplace throw a 404 error, it's not a good sign... The points I'm missing on Document This are:

fill all possible docs at once, instead of one-by-one
being a CLI tool to automate
sync and update already available JsDoc entries, specially regarding default values and interpolated types

Does this makes sense?

Whoops, I meant to link to this fork that does appear to be actively maintained ;)
That definitely makes sense. I do want to note that point 3 may or may not fit ts-to-jsdoc as is; it's written to assume there aren't already any types in doc comments as is. I'll take a look at how much value implementing this would create.

Yeah, point 3 would be more difficult to implement, since we would need to parse and merge current JsDoc strings too. Just by adding new ones would be enough.

Closing this as out of scope — for the time being, I don't see a tool called ts-to-jsdoc transforming anything other than TS into anything other than JSDoc.

Since Typescript is being sold as an extensión to JavaScript, i see It as being in scope...

You'll have to take that up with Microsoft :P


update the token website link #16798

I'm submitting a ...
[ ] feature request
[ ] question about the decisions made in the repository

Hello sir/mam, my token MCOP has wrong website address. I copied someone else token link. Please update the link to https://metacopsnft.io. or merge request #16798.

Also it can be classified as bug too as I  can make a new token use someone else social link and try to sell the coin to new web3 users.

can i get a response soon

merged


added upload profile picture functionality

Summary of Changes

Added new feature to upload and update profile pictures.
Implemented front-end UI components for profile picture upload.
Updated backend API endpoints to handle profile picture upload and storage.
Added necessary validations and error handling for the upload process.

Purpose
These changes introduce the ability for users to upload and update their profile pictures, enhancing the personalization and user experience of the chat application.


Fenced frame appears broken in latest Chromium revision

Sorry, I don't think this is related to the fledge-demo itself but I did not know where to go with this, maybe someone here can forward the issue to the right place.
It seems like the latest development chromium versions broke the fenced frame and thus the demo. I also noticed this in my own tests outside https://fledge-demo.glitch.me. The ad does show with chromium revision 991192 (102.0.4999.0) but it is no longer the case with revision 994825 (103.0.5018.0). I did not set out to find the exact revision where it no longer works but hopefully this is informative enough to help. As you can see from the images below, the fenced frame in the latter version looks as if width and height were compressed.
Revision 991192:

Revision 994825:

@MarcoLugo Just to say — haven't forgotten this! Just checking what's going on.

Hi @MarcoLugo.  Sorry it took some time to get back to you. The reason why the ad isn't rendering in a fenced frame is because:

The PrivacySandboxAdsAPIsOverride flag needs to be included in the Chrome starting arguments. (--enable-features=InterestGroupStorage,AdInterestGroupAPI,Fledge,FencedFrames,PrivacySandboxAdsAPIsOverride)
The fenced frame tag's mode attribute needs to be set to opaque-ads. (Example: <fencedframe id='fledge-ad' mode='opaque-ads'></fencedframe>)

We are in the process of migrating the FLEDGE demo to a different hosting solution at the moment, and the existing demo at https://fledge-demo.glitch.me has not been updated yet. While we make the full switch, you can check out the fenced frame functionality at https://fledge-demo.web.app/ (Repo: https://github.com/GoogleChromeLabs/fledge-demo/).


Update azure-pipelines.yml for Azure Pipelines

Approved as Sonar cloud checks are force-enabled now


Fix: Handle Ctrl-C or exit gracefully after OpenAI API interaction

Description
When attempting to interrupt (Ctrl-C) or exit the application after interacting with the OpenAI API, a messy error is thrown. This needs to be handled gracefully.
Steps to Reproduce

Interact with the OpenAI API in the application.
Attempt to interrupt or exit the application using Ctrl-C.
Observe the messy error output.

Expected Behavior
The application should handle the situation gracefully, ensuring that any necessary cleanup is performed and no error messages are displayed.
Suggested Fix
Implement a signal handler for SIGINT (Ctrl-C) that safely exits the application without throwing errors. Ensure that any resources are properly cleaned up before exiting.
Additional Information

Ensure compatibility with other parts of the application that may also handle signals.
Test on different operating systems to ensure consistent behavior.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "\?\C:\Users\kord\miniconda3\envs\webwright\Scripts\webwright-script.py", line 33, in
sys.exit(load_entry_point('webwright', 'console_scripts', 'webwright')())
File "c:\users\kord\code\mitta\webwright\webwright\main.py", line 240, in entry_point
tasks = [task for task in asyncio.all_tasks() if not task.done()]
File "C:\Users\kord\miniconda3\envs\webwright\lib\asyncio\tasks.py", line 44, in all_tasks
loop = events.get_running_loop()
RuntimeError: no running event loop
Exception ignored in: <function _ProactorBasePipeTransport.del at 0x000002A84F718280>
Traceback (most recent call last):
File "C:\Users\kord\miniconda3\envs\webwright\lib\asyncio\proactor_events.py", line 116, in del
self.close()
File "C:\Users\kord\miniconda3\envs\webwright\lib\asyncio\proactor_events.py", line 108, in close
self._loop.call_soon(self._call_connection_lost, None)
File "C:\Users\kord\miniconda3\envs\webwright\lib\asyncio\base_events.py", line 719, in call_soon
self._check_closed()
File "C:\Users\kord\miniconda3\envs\webwright\lib\asyncio\base_events.py", line 508, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed


Synchronize DiscoveredPackage model with toolkit PackageData model

Some fields supported by the toolkit are missing on the ScanCode.io side:
https://github.com/nexB/scancode-toolkit/blob/develop/src/packagedcode/models.py#L533
>>> from packagedcode.models import PackageData
>>> from scanpipe.models import DiscoveredPackage
>>>
>>> toolkit_fields = [field.name for field in PackageData.__attrs_attrs__]
>>> discovered_package_fields = [field.name for field in DiscoveredPackage._meta.get_fields()]
>>> set(toolkit_fields).difference(set(discovered_package_fields))
{'sha512', 'parties', 'api_data_url', 'repository_download_url', 'datasource_id', 'sha256', 'file_references', 'repository_homepage_url'}

New fields to consider adding to DiscoveredPackage:

sha512
sha256
parties
api_data_url
repository_download_url
datasource_id
file_references
repository_homepage_url

Let's add a unit test that would ensure the fields on DiscoveredPackage are in sync with PackageData before closing this on for good.


Creating Table component using shorthand component causes "keys" warning

React / ReactDOM version: 15.4.2
Semantic UI React version: 0.64.3
Warnings:

Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of Table.
Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of TableRow.

The Codepen below does specify a key for each dataRow, but not for headerRow values.
Could that be the issue? If so, under what key should the header values be placed? (i tried turning headerRow into a dictionary, but the rendering would not know how to pick up the header vals)
http://codepen.io/khorkhe/pen/ggWEmm

The tableData has keys, however, the table cells do not:
cells: [
  name || 'No name specified',
  status ? {
    icon: 'attention',
    content: status
  } :
  'Unknown',
  notes ? {
    icon: 'attention',
    content: notes,
    warning: true
  } :
  'None',
],

The TableCell shorthand objects must have a key as well.  When I add a key to those, the warnings go away.

I see.  I had tried this:
const renderBodyRow = ({ name, status, notes, key }) => ({
  cells: [ name, status, notes, key ],
})

when it really should have been this:
const renderBodyRow = ({ name, status, notes, key }) => ({
  cells: [ name, status, notes ],
  key
})

Sorry for the trouble

No worries, thanks for using SUIR and reporting issues!


model shows "Invalid tensor data size." when click on the bias tensor

I am working on a tool that manipulates tflite directly without using tf tools, it's mostly working, but when I use the web version of netron, click on the bias tensor of the conv nodes it says "Invalid tensor data size.". The bias was float values and I changed the tensor to int32 and quantized them, replaced the tensor buffer to be the new numpy array. Everything looks fine to me, I did the similiar thing to the weight tensor and it was fine, but looks like there are something else I missed. Wondering how to debug this issue, what's special about bias tensor? Is there a place I can upload my generated tflite model to? Or, if I sync the code, is there a doc explain how to run it on browser?

@tensorbuffer can you share a sample file to reproduce the issue.

https://www.dropbox.com/scl/fi/3v9tixfmoolxwc0rq2f9r/output.tflite?rlkey=kdnr36an0djnq47fl3k4wcs4q&dl=0


BS: add neigh_ia label to missed metrics

The following BS metrics (found with {job="beacon_servers",if_id=~".+", neigh_ia=""}) have an if_id label, but no neigh_ia label:

bs_keepalive_received_msgs_total
bs_keepalive_sent_msgs_total

These metrics no longer exist.


Newly installed app has over 100 content-groups

...this are hidden items in the scope "2SexyContent-System" which have no use. Please delete for next release.

@ropalko is this still an open issue or has this been fixed a long time ago?

@ropalko pls close this after clean-up.

Updated in Version 3.0.2


Consider increasing client reconnect delay

When there are certain errors, for example one on the client side, I do not want to swamp the other end with connection requests. Also this should reduce the chances of Discord banning the IP address or something.

Went for the very bare minimum of block_sleep(2).

Increased to 2 but also made this a configurable parameter.


Installing via homebrew requires manual linking step if Xcodes GUI cask installed

Steps:

brew install --cask xcodes to install the GUI app
brew install robotsandpencils/made/xcodes to install the CLI

Behaviour:
$ xcodes version
zsh: command not found: xcodes
$ brew link xcodes
Linking /usr/local/Cellar/xcodes/0.17.0... 1 symlinks created.
$ xcodes version
0.17.0

Brew output during install:
$ brew install robotsandpencils/made/xcodes
==> Tapping robotsandpencils/made
Cloning into '/usr/local/Homebrew/Library/Taps/robotsandpencils/homebrew-made'...
remote: Enumerating objects: 83, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 83 (delta 8), reused 32 (delta 7), pack-reused 47
Receiving objects: 100% (83/83), 42.72 KiB | 2.37 MiB/s, done.
Resolving deltas: 100% (18/18), done.
Tapped 1 formula (15 files, 71.6KB).
==> Installing xcodes from robotsandpencils/made
==> Downloading https://github.com/RobotsAndPencils/xcodes/releases/download/0.17.0/xcodes-0.17.0.mojave.bottle.tar.gz
==> Downloading from https://github-releases.githubusercontent.com/171964196/753be900-7841-11eb-9635-36e1bcf2c174?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CS
######################################################################## 100.0%
==> Pouring xcodes-0.17.0.mojave.bottle.tar.gz
==> xcodes cask is installed, skipping link.
🍺  /usr/local/Cellar/xcodes/0.17.0: 2 files, 8MB

I assume it's the "skipping link" bit that's the issue, maybe because the formula and the cask have the same name?

This hit me as well. Not ideal.

Also, why do I have to install the CLI using brew install robotsandpencils/made/xcodes?
It would be much better to install the CLI using brew install xcodes and the GUI via brew install --cask xcodes like it's intended to be for Homebrew. GUIs are Cask apps, regulary.

somehow the both formulars are the same?
brew cat xcodes

class Xcodes < Formula
  desc "Install and switch between multiple versions of Xcode"
  homepage "https://github.com/RobotsAndPencils/xcodes"
  url "https://github.com/RobotsAndPencils/xcodes.git", tag: "1.0.0"
  head "https://github.com/RobotsAndPencils/xcodes.git", branch: "main"

  bottle do
    root_url 'https://github.com/RobotsAndPencils/xcodes/releases/download/1.0.0'
    sha256 cellar: :any_skip_relocation, mojave: "23f4ee4ecac29c8816011895d18da9e78f2ec1fa3184489809d6e126039fa499"
    sha256 cellar: :any_skip_relocation, arm64_mojave: "23f4ee4ecac29c8816011895d18da9e78f2ec1fa3184489809d6e126039fa499"
  end

  def install
    system "make", "install", "prefix=#{prefix}"
  end

  test do
    system "#{bin}/xcodes"
  end
end

brew cat robotsandpencils/made/xcodes

class Xcodes < Formula
  desc "Install and switch between multiple versions of Xcode"
  homepage "https://github.com/RobotsAndPencils/xcodes"
  url "https://github.com/RobotsAndPencils/xcodes.git", tag: "1.0.0"
  head "https://github.com/RobotsAndPencils/xcodes.git", branch: "main"

  bottle do
    root_url 'https://github.com/RobotsAndPencils/xcodes/releases/download/1.0.0'
    sha256 cellar: :any_skip_relocation, mojave: "23f4ee4ecac29c8816011895d18da9e78f2ec1fa3184489809d6e126039fa499"
    sha256 cellar: :any_skip_relocation, arm64_mojave: "23f4ee4ecac29c8816011895d18da9e78f2ec1fa3184489809d6e126039fa499"
  end

  def install
    system "make", "install", "prefix=#{prefix}"
  end

  test do
    system "#{bin}/xcodes"
  end
end

@muescha Thanks for confirming my observation. I had to find this issue sorely to find out how to install the CLI via Homebrew. I think it was a poor decision and I'm afraid there is no turning back, or is it?

Same trouble/observation here. Expected xcodes to get shell version, but then ended up with the GUI app cask. Tried GUI and it presented problems such as a hang on unarchiving (reported) and tried to go back here to see what's going on... Headache.


Add missing sibling method

Added method parseEightDigitsUtf8 analogous to parseEightDigitsUtf16.

Thank you. 🙂
Actually, I forgot to delete method parseEightDigitsUtf16 when I deleted parseEightDigitsUtf8.
I have now deleted it as well.


[HW] Saideep Dicholkar

Name: Saideep Dicholkar
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/saideep-dicholkar
Attach the homework screenshots below for both step II and step III:
SCREENSHOTS:
Step II:

Execute CRUD Operations:

Step III (Cassandra short courses):

Cassandra Data Modeling:

Cassandra Query Language:

Looks great Saideep, thank you.

Hey Saideep Dicholkar, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/tv3A-kxIQfWFwN--Mq6bRQ


v1.5.1 does not create all registry keys anymore

With the new v1.5.1 installer, no new key in "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Raspberry Pi" gets created anymore.

Right, so what is the issue with that really? We don't need this registry key as part of the functionality of the installer.

Yes, that's right, not for the functionality for the installer but it's a good functionality for other projects and users as it's currently the simplest way to detect all installed Pico-SDKs (an their paths) if you don't want to scan the FS or for something like the uninstaller in the registry.
Also it doesn't make the installer faster or less complex if this registry key is removed.

I'd say checking the uninstall keys is the recommended approach if you want to detect the presence of this installer. This is how tools like winget check for installed packages, and is also how a lot of other (first party and third party) software detects, for example, if VS Code is installed. You can check, for example, HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\Raspberry Pi Pico SDK v1.5.1.
Removing something isn't always about speed, performance, or complexity. Engineering is about doing exactly what's needed, and nothing more.

Does the uninstall uninstall the uninstall key?

It is customary for the uninstall to uninstall the uninstall keys at the end of the uninstall process.
So... yes. :)

I could do that, and probably will at some point -- however that is going to be a low priority because:

People who already have SDK v1.5.0 installed are not going to come back and look for an updated installer. So you'll need to handle the case of the current v1.5.0 installer as it was released.
People who are installing the SDK afresh have little reason to choose the v1.5.0 installer over the latest one.

My recommendation to detect the installed versions and their paths would be:

Find all keys that look like: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Raspberry Pi Pico SDK vX.Y.Z. Additionally, while user installers are not planned currently, you might want to check HKEY_CURRENT_USER as well, and both the 32/64-bit versions of HKLM, if you wanted to be thorough/complete.
Extract the version from the key name, not the DisplayName (as that might change if we decide to localize the installer at some point.)
Extract the path from UninstallString.

This will work for all current and future releases.

Closing as no further action is needed.


added links that open in new tab for books

for the buildCard function I added attributes that would use the previewLink in the object and user will be able to open up a new tab on the click.

also left html at the bottom to use for main index


[Feature Request]: Operations on multiple pages in Multitool

Feature Description
Be able to do the move, rotate or delete operations on multiple pages at once in the Multitool
Why is this feature valuable?
At te moment you only can move, rotate and delete 1 page at a time in the Multitool. In larger files you'd want to do these operations on multiple pages at once. For instance moving 5 pages at the back to the front; now you have to move these one by one.
Suggested Implementation
Select mutiple files by using the CTRL or SHIFT-buttons (don't know how well this would work on a webpage) or by providing a checkbox per page so you can select mutiple pages at once before moving/rotating/deleting them.
Additional Information
No response
No Duplicate of the Feature

[X] I have verified that there are no existing features requests similar to my request.

is anyone working on this? If no I can work on this.

to fix your trouble check this solution click
maybe this will solve your problem.

Looks very good, you can delete and rotate multiple pages at once now. But if I'm not mistaken moving multiple pages at once still isn't possible? Or did I miss how you can do this?


Not found in scope

Hi, thanks that, your code works, but it does not work  in my project, how i can solve this?

Hi. Please check the target membership.

Go to ActivityAttributes.swift

Be sure it targeted WidgetDemoExtension too.

Let me know if it works :)

Thanks, it works. And when you integrate widget with remote notification (fcm) ?

@alphaSoft99
Please see if this pull request can answer your question.
https://github.com/1998code/iOS16-Live-Activities/issues/8#issuecomment-1293176462


error

Hi,
I tried batch mode several times but it gave me error message like this:
ERROR: (gcloud.ml-engine.jobs.submit.prediction) Projects instance [angular-stacker-325501] not found: Field: prediction_input.model_name Error: The model resource: "deepmass_prism" was not found. Please create the model resource first by using 'gcloud ai-platform models create deepmass_prism'.

'@type': type.googleapis.com/google.rpc.BadRequest
fieldViolations:

description: "The model resource: "deepmass_prism" was not found. Please create
\ the model resource first by using 'gcloud ai-platform models create deepmass_prism'."
field: prediction_input.model_name

Can you pls help me with it? Thank you!

Same here, didn't get any reply from the email address listed. Cox only told me that I should do as the git readme.

@naomikk7 and @snail123815 Just out of curiosity I tried to list the models available, and there are none available to perform any AI prediction.  For example:
[pgrosu]$ gcloud ml-engine models list
Listed 0 items.
[pgrosu]$

Maybe they are still in the process of updating Google's AI model resources.  It mentions that contacting<EMAIL_ADDRESS>might help.

@pgrosu I have contacted them for quite some times already, no reply from that side.
The empty list I think is actually because updated google policy, they do not expose existing models to users like before I guess. But I don't know how to find and add the deep mass model.

@snail123815 I wouldn't be surprised if DeepMass might be a Google dead project, and we just weren't told about it, see: https://killedbygoogle.com/

Hi all,
First, apologies for the slow reply. The DeepMass project isn't a dead Google project, but we have been either away or distracted by other work.
Re: this issue -- I'm still looking into it. It seems there's been a change in project region. Could someone here try selecting global instead of us-central1 region, and see if that makes any difference?

Hi @petercim,
Thanks for clarifying! This worked:
gcloud ai-platform predict --model deepmass_prism --project deepmass-204419 --format json --json-instances "input.json" --region global > prediction.results

Glad to hear that worked, thanks for giving it a try @snail123815 ! I just updated the README file and will now close this issue. Thanks all!


Tags containing dash can't render properly

Describe the bug
Tags containing dash can't render properly,
for example
#rock-climbing  #day-trip
Steps to reproduce
Null
Screenshots or additional context

This behavior is catched by this regex /#((?:[^\s\p{P}]|_)+)/u, and therefore you cannot use the hyphen in here.
You can use the underscore instead eg: #day_trip, #rock_climbing

@waterdrops Sorry for annoying you, but the issue has not been closed yet

@tranquanghuy0801 You're very welcome, Let me share more info about this issue:
I pulled the latest code and built an image using the main branch (PR #1974 has been merged into main), and tags with underscores can now render properly. However, tags containing hyphens are still not rendering correctly.

@waterdrops I mean the PR #1974 exclude all chars in the tag name except for the underscore. So I think the output showed in your image is reasonable.

I'll close this issue, By the way, I was wondering if it would be possible to include hyphens in tags.

@waterdrops I would suggest adding your comment in that PR to ask the team why we need to do that

Hi, just found this issue on my instance too. It is quite unexpected behaviour, the change also doesn't seem to be very well rolled out, because now the filters by tag don't work at all (viz. screenshots) so all tags with dashes prior to 0.14.1 are not usable.

I personally don't like the change, the support of the dashes was nice and (at least for me) expected feature.

Hi, just found this issue on my instance too. It is quite unexpected behaviour, the change also doesn't seem to be very well rolled out, because now the filters by tag don't work at all (viz. screenshots) so all tags with dashes prior to 0.14.1 are not usable.

It can be related to #2027

Probably the question is for @boojack. Any reasons why we have the PR https://github.com/usememos/memos/pull/1974 as this one prevents rendering dashes in tags

This issue has been fixed in v0.14.2 https://github.com/usememos/memos/releases/tag/v0.14.2


Use layer name as filename prefix in zip export

Hi!
Piskel is such a great project; I use it all the time for making scenes and characters in my video games. Thanks for making this!
I'd like to have the exported layers optionally start with the layer name, rather than the layer index. For most of my games, I'm copying over the exported layers and frames from Piskel into another project, and then referencing them by filename in the game code. If I need to come back to Piskel and add another layer in the middle of others are re-export, my the existing layers' filenames are now shifted due to the index change and my game code's file references are wrong. Optionally using the layer name in the exported files rather than index would allow easier migration of files to other projects that aren't expecting layer file names to change each time.
I added a new checkbox to the zip export html template to enable this option, and supporting logic to the zip export controller. The new checkbox should not show unless the "split by layers" options is checked.
Let me know what you think.
Thanks again,
Alex

Thanks for the nice feedback and for the PR. The idea sounds good, I'll review the change this weekend.

Makes sense! I'll make those changes and push an update. Thanks.

Looks good, thanks for addressing the comments @sharpfives ! Merging. I'm preparing release v0.14 right now so your change should be available very soon on piskelapp.com :)

@juliandescottes  No problem, thanks again for making this. Also nice work keeping the code clean and organized - made it super easy for me to get up and running.


#496 One time links should be generated by our url shortener

#496
One time links should be generated by our url shortener
We’ve changed forming of links and add conditions for prod and qa/dev. We’ve added two new parameters
REACT_APP_RECEIVE_URL=
REACT_APP_SEND_URL=
For prod they should be
get.gdlr.info/
give.gdlr.info/
There is condition, if it’s Prod, then we add code after slash ( have to add other parameters as well), if dev/qa we add GET parameters.
Payment links params should stay the same on production the only the difference is the format of the link, that the code is in url other params should be the same.
For payment we can simply use dapp.gooddollar.org/?paymentCode=
for receive it should go to the .../Send?code=
And removed double encodeURI

/?paymentCode= and /?code= ?

@Nordwhale @StanislavShevchenko
do we still need to make the link with the whole path? ie /Applicaiton/Dashboard/Receive?code=
or is it enough to use /?paymentCode= and /?code= ?

Yes, now it’s enough to have a link
/? paymentCode = and /? code =?
This can be specified in environment variables:
REACT_APP_RECEIVE_URL=
REACT_APP_SEND_URL=

why was this closed?
Sorry, maybe clicked

why was this closed?
please add unit tests that verify link is created correctly

done


Dependency Issues

Hey,
Thanks for your amazing work! I want to point out a current installation dependency problem:
pip install dgl -f https://data.dgl.ai/wheels/cu116/dgl-1.1.3%2Bcu116-cp38-cp38-manylinux1_x86_64.whl installs dgl version 2.1.0 and also torch version 2.2.2. This in itself is a problem as dgl version 2.1.0 only supports torch versions 2.0.0/1, 2.1.0/1/2, 2.2.0/1.
On the other hand, your environment.yaml file depends on pytorch 1.13.1, which does not work with dgl 2.1.0. In addition, pytorch 1.13.1 does not work with torchdata 0.7.1. However, it seems that you need torchdata>0.5.1, which is the last version that is compatible with pytorch 1.13.1.
What worked for me was to install torch 2.1.0 and update torchvision to 0.16 after having installed the newest dgl version using your command. Maybe your intent was to install dgl 1.1.3, which supports pytorch 1.13.1, but I think your pip install link should then be https://data.dgl.ai/wheels/dgl-1.1.3-cp38-cp38-manylinux1_x86_64.whl.

I have faced this issue too... Ended up using dgl v2.1.0 with some workarounds here and there

Hi,
The EDIT 2 suggested by @pawanw17 works! Thanks for the suggestion and we will update the README accordingly.


create a method which recieves aid and returns issuerName

closing as it is merged with https://github.com/WebOfTrust/signify-browser-extension/pull/135


Added datastore QueryParams

refactored all list functions to use that instead of page / pageSize

Codecov Report

Merging #72 (1268152) into master (ca1d8d9) will decrease coverage by 0.26%.
The diff coverage is 32.30%.

@@            Coverage Diff             @@
##           master      #72      +/-   ##
==========================================
- Coverage   56.91%   56.65%   -0.27%
==========================================
  Files         106      106
  Lines        9858     9915      +57
==========================================
+ Hits         5611     5617       +6
- Misses       3877     3928      +51
  Partials      370      370

Flag
Coverage Δ

unittests
56.65% <32.30%> (-0.27%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

action_access_key.go
0.00% <0.00%> (ø)

action_paymails.go
48.48% <0.00%> (+0.72%)
:arrow_up:

action_transaction.go
39.73% <0.00%> (ø)

action_utxo.go
28.57% <0.00%> (+0.79%)
:arrow_up:

datastore/models.go
0.00% <0.00%> (ø)

model_incoming_transactions.go
45.32% <0.00%> (-2.60%)
:arrow_down:

model_paymails.go
58.01% <0.00%> (ø)

model_sync_transactions.go
19.24% <0.00%> (-0.69%)
:arrow_down:

monitor.go
0.00% <0.00%> (ø)

tasks.go
0.00% <0.00%> (ø)

... and 11 more

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 ca1d8d9...1268152. Read the comment docs.


ARROW-2807: [Python] [Parquet] Add memory_map= option to parquet.read_table, read_pandas, read_schema

The default for memory_map remains True for now.

Codecov Report

Merging #2954 into master will increase coverage by 0.86%.
The diff coverage is 92.85%.

@@            Coverage Diff             @@
##           master    #2954      +/-   ##
==========================================
+ Coverage   86.51%   87.38%   +0.86%
==========================================
  Files         490      422      -68
  Lines       68879    63679    -5200
==========================================
- Hits        59590    55643    -3947
+ Misses       9201     8036    -1165
+ Partials       88        0      -88

Impacted Files
Coverage Δ

python/pyarrow/parquet.py
93.69% <100%> (ø)
:arrow_up:

python/pyarrow/tests/test_parquet.py
97.36% <90.9%> (-0.15%)
:arrow_down:

cpp/src/arrow/csv/column-builder.cc
95.1% <0%> (-2.1%)
:arrow_down:

rust/src/record_batch.rs

go/arrow/array/table.go

rust/src/array.rs

go/arrow/math/uint64_amd64.go

go/arrow/internal/testing/tools/bool.go

go/arrow/array/bufferbuilder.go

go/arrow/internal/bitutil/bitutil.go

... and 61 more

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 1ef6c26...7ec33db. Read the comment docs.

+1


TestSample

Testing github desktop

5 Points are assured. No Errors found by AI system, you must be really good in writing uipath code. An expert need to review your code and it will be done before next sunrise :)

welcome to basic team
complete a tasks as per task list


REQ-1. The Project will run as a docker image in user machine.

For running the application as a docker image follow the documentation "production mode" part.
Follow the link :
https://github.com/rakiiibul/spa-app#production-mode
@b-rodrigues


Generate grpc cc library using built-in shell environment

This commit updates the implementation of cc_grpc_library to use the built-in shell environment. It aligns the implementation with the proto_gen rule for protocol buffers.
Migrated from bazelbuild/bazel#11260

@donnadionne

What's the benefit of this PR?

In my specific case, this change was needed to fix an error while building Bazel from source on a server where several (non-standard) paths for the loader are defined in the env to make sure that binaries load the correct libraries.
During the bootstrap of Bazel, grpc libraries were failing to compile because protoc was having trouble loading the right version of the libraries, but regular protobufs were doing fine because the environment variables were being propagated.
I couldn't see any reason why proto_gen and cc_grpc_library should behave differently in terms of handling of the environment variables, given that they invoke protoc in similar ways.

Adding @gnossen  as our local expert on bazel build.


Add the ability to check if a remote artifact is a bundle

Describe the problem/challenge you have
[A description of the current challenge that you are experiencing.]
Following another issue I've opened in upstream Tanzu Framework:
https://github.com/vmware-tanzu/tanzu-framework/issues/3757
Describe the solution you'd like
[A clear and concise description of what you want to happen. If applicable a visual representation of the UX (ex: new CLI argument name, the behavior expected).]
In that case, a specific bundle couldn't be pulled using imgpkg copy because this script had incorrectly attempted to use imgpkg copy -i rather than imgpkg copy -b. Also, currently, as you can see, the script has some hardcoded values for specific bundles, as it doesn't know which artifacts are bundles and which artifacts are images.
I think it would be great to have the ability to "inspect" a remote artifact to determine whether it's a bundle or not. This would allow for a dynamic pre-check in such cases.
Using Docker or Crane CLI, I've managed to get this information.
For example:
Output of docker inspect projects.registry.vmware.com/tkg/packages/capabilities:v0.25.0-23-g6288c751_vmware.1:
...
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {
                "dev.carvel.imgpkg.bundle": "true" # This is the label imgpkg should be able to extract
            }
        },
...

Output of crane config projects.registry.vmware.com/tkg/packages/capabilities:v0.25.0-23-g6288c751_vmware.1:
{"architecture":"","created":"0001-01-01T00:00:00Z","history":[{"author":"imgpkg","created":"0001-01-01T00:00:00Z","created_by":"imgpkg"}],"os":"","rootfs":{"type":"layers","diff_ids":["sha256:1390449d75a402107fd54acb217a4941ef5175da7725026ad5abe625e7befc84"]},
"config":{"Labels":{"dev.carvel.imgpkg.bundle":"true"}}}

The last part of that output also contains this info.
Anything else you would like to add:
[Additional information that will assist in solving the issue.]
See above.

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help work on this issue.

Hello @itaytalmi
imgpkg does have a command that describes the contents of a bundle.
in your example:
$ imgpkg describe -b projects.registry.vmware.com/tkg/packages/capabilities:v0.25.0-23-g6288c751_vmware.1
Bundle SHA: sha256:03d22253164c1aabbd3527a4287ef18808466b26346d79ade57238d66e2ed468

Images:
  - Image: projects.registry.vmware.com/tkg/tanzu_core/capabilities/capabilities-controller-manager@sha256:4a91b04faa30f7b6e0dd41f50e231aaba829381354d9bb430ddda8354ee4c1df
    Type: Image
    Origin: projects.registry.vmware.com/tkg/tanzu_core/capabilities/capabilities-controller-manager@sha256:4a91b04faa30f7b6e0dd41f50e231aaba829381354d9bb430ddda8354ee4c1df
    Annotations:
      kbld.carvel.dev/id: capabilities-controller-manager:latest
      kbld.carvel.dev/origins: - resolved:
          tag: v0.25.0-23-g6288c751
          url: projects.registry.vmware.com/tkg/tanzu_core/capabilities/capabilities-controller-manager:v0.25.0-23-g6288c751

Succeeded

The only caveat with this is if you try to run describe on an image you will get the following error:
$ imgpkg describe -b projects.registry.vmware.com/tkg/tanzu_core/capabilities/capabilities-controller-manager@sha256:4a91b04faa30f7b6e0dd41f50e231aaba829381354d9bb430ddda8354ee4c1df
imgpkg: Error: Only bundles can be described, and projects.registry.vmware.com/tkg/tanzu_core/capabilities/capabilities-controller-manager@sha256:4a91b04faa30f7b6e0dd41f50e231aaba829381354d9bb430ddda8354ee4c1df is not a bundle

Do you think this behavior is enough to get what you need?

No, that functionality does not exist.
imgpkg tries to be very precise about the operation that is executing. So there is an expectation that when a user calls imgpkg, it knows what they want to copy/pull.

the other issue with describe is that it can be a long running command if the bundle is large and has many nested bundles making it not an optimal choice.
it would be nice if like we have the "tag ls" command in imgpkg, if we also had a "inspect", or "labels ls" command that could return data on a specific oci artifact.

ah .  ok.  some kinda imgpkg support would be good here, any equivalent ideas we could implement @joaopapereira ?

from offline discussions we had, looks like tanzu-framework is reworking that script which should solve your original problem.

it would be nice if like we have the "tag ls" command in imgpkg, if we also had a "inspect", or "labels ls" command that could return data on a specific oci artifact.

@vrabbi What kind of information you are thinking about? Do you have an use case for it apart from the original one in this issue?

Another use case is images built with buildpacks have labels added to them with a bunch of information that could br very beneficial for people to know such as what buildpacks were used, sbom information and so on. As this is metadata on an image, it would be nice to be able to use imgpkg to view the labels on the images so as to have a simple way of detecting what an kmage contains

@joaopapereira Additionally, the original issue wasn't solved - Tanzu Framework hardcodes imgpkg bundle names in that script, which is the reason we ran into this issue in the first place. If we could inspect the image/bundle using imgpkg before pulling it, we could have a much more dynamic and generic approach and it wouldn't be necessary to hardcode any bundle names anywhere. It makes a lot of sense in my opinion.

@itaytalmi the issue is being solved via a new command in tanzu cli that will make this script irrelevant in the future. PRs are already starting to show up in framework for it.

@itaytalmi I was talking about https://github.com/vmware-tanzu/tanzu-framework/pull/3743

Is it ok if we close this issue since it looks like there will be a solution in tanzu-framework for this particular problem?

Yes. Thanks.


test: fix redirect tests

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
e2e and ssr redirect tests depended on a now-moved page on the nuxt docs ... which ironically was redirected, thereby breaking the test
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

Would it make sense here to rely on a "more stable" domain like example.com?

@manniL 😆 Agreed. I would just creating an endpoint we control and which is used just for these redirect tests. (e.g. a serverless function that just returns an empty HTML page.)

I'll merge this for fixing build and not blocking other prs.


Removed duplicate words from verify-email/page.js

This commit removes 3 duplicate words in page.js. Originally, the text had duplicate words "verify verify" [line 18-19], "gladly gladly" [line 20-21], "address address" [line 26-27]. This commit changes it to single word.

Thanks!


"Windows Azure Access Control Service" almost retired

"for example, the Windows Azure Access Control Service (ACS)."
ACS will be retired during next 3 weeks. It will be right to cleanup this document from this retired feature during next couple of weeks
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-acs-migration

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

ID: 1597a0b7-494d-0cca-bc54-e432719d2256
Version Independent ID: 17d1429f-ff5d-8f13-bdbd-b8147808305b
Content: Claims Based Authorization Using WIF
Content Source: docs/framework/security/claims-based-authorization-using-wif.md
Product: dotnet-framework
GitHub Login: @BrucePerlerMS
Microsoft Alias: dotnetcontent

@SychevIgor thanks for your input. I believe we're trying to retire the entire section for WIF: https://docs.microsoft.com/en-us/dotnet/framework/security/.
/cc @brentschmaltz

@mairaw the WIF code is still part of .Net Framework and will be supported for some time. What do you mean by 'retire'?

@mairaw @brentschmaltz

Brent, https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-acs-migration

@jordanmills I am not seeing where WIF is being 'retired' in the link above.


Backport "candidates" from develop to v0.15.x

https://github.com/dashpay/dash/pulls?q=is%3Apr+label%3Abackport-candidate-15.x+is%3Aclosed

FYI, removed backport-candidate-15.x label from PRs which were backported in this PR.


New tweets pile on top

How about a feature that would pile new tweets on top of the most recent tweet? In other words, a feature that would prevent Tweetdeck from pinning to top and allow users easily to read new tweets, right from where left off.
There is a "workaround" to scroll just a bit down so Tweetdeck doesn't automatically keep timeline in the uppermost position, but it's tedious in a long term.

There's a setting for this on tweet deck, called something like auto refresh.

If you mean streaming, that's not quite what I mean. Even if streaming is disabled, it still pins to top. Just loads tweets a bit slower.

This would be an interesting thing to have, and it's definitely something to consider implementing


Create docs to project

We need to remove the README documentation from the project and provide her with a worthy home :)

This project has a good example

I started writing the project documentation and preferred to use the github wiki as the documentation repository.
I'll document the basics of using the library and any comments I deem necessary. With that I believe I can give this issue as closed.

We create a wiki for the project.


El Capitan & Homebrew w/ iTerm2

Whenever I open a new tab or window in iTerm 2 I'm seeing this notice:
Last login: Thu Oct 15 09:58:06 on ttys005
/Users/brianjking/.zshenv:1: command not found: brew

The contents are as follows:
cat /Users/brianjking/.zshenv
export PATH="$(brew --prefix)/bin:$PATH"

Any tips?

brew is installed in /usr/local/bin, which is not on the path by default. /usr/local/bin is added by a /usr/libexec/path_helper invocation in the global startup files. In 10.9, this was done in /etc/zshenv. In El Capitan, Apple moved it to /etc/zprofile, which runs later in the startup file order, after .zshenv. So now, at the point your .zshenv runs on El Cap, /usr/local/bin isn't on the path yet.
You can fix it by moving that command from your .zshenv to your .zprofile or .zshrc, which run after /etc/zprofile, so /usr/local/bin will be in place. (You could also pull the path_helper invocation in to your .zshenv, but that zsh mailing list advises against it, so a caller's exported $PATH will be respected in subshells.) And maybe wrap it in a test for the existence of brew, so it doesn't break on machines that don't have Homebrew installed.

@apjanke -- Just to make sure I understand.
It sounds like the best option is to paste the contents of .zshenv into my .zshrc?
export PATH="$(brew --prefix)/bin:$PATH"

@brtianjking: Yes, and then delete your .zshenv.

@apjanke Does it matter where in the .zshrc I put it?

It depends on exactly how you want your setup to behave. But in the typical case, you would want your Homebrew-installed stuff to take priority over system-installed commands, and you'd want the $PATH to be consistent for everything. If you had it in .zshenv before, that's the case for you. So put it at or near the top of .zshrc, before loading OMZ or anything else. Otherwise you might find that OMZ plugins or other things are complaining about not being able to find commands they need.

@apjanke I think your suggestion worked! Thanks!
export PATH="$(brew --prefix)/bin:$PATH"

# Path to your oh-my-zsh installation.
export ZSH=/Users/brianjking/.oh-my-zsh

# Set name of the theme to load.
# Look in ~/.oh-my-zsh/themes/
# Optionally, if you set this to "random", it'll load a random theme each
# time that oh-my-zsh is loaded.
ZSH_THEME="agnoster"

Great.
If that worked, could you close this issue out?

Thanks again @apjanke. Everything seems to be working fine now. Closing issue as complete & fixed.