Sample app targets .NET 7, prerequisite section states .NET 6 which causes an error.

Sample app and docker image target .NET 7, but the prerequisite states .NET 6.  This produces an error during the project build and app push to docker.

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

ID: 3653642e-61ef-717b-5436-9bd0a3c4e6f4
Version Independent ID: 80c1ce51-46fb-0693-525a-7cad37150c7b
Content: Docker images for ASP.NET Core
Content Source: aspnetcore/host-and-deploy/docker/building-net-docker-images.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

The problem is larger than just the 6.0/7.0 difference. There are separate doc pages for each .NET version. So even before the change to make the dotnet-docker samples to be based on .NET 7 instead of .NET 6, there was a problem with the doc pages related to .NET Core 3.1. That's because the 3.1 doc page is referring to the same dotnet-docker repo and so there was a 3.1 pre-requisite on the doc page but the repo was configured to use .NET 6 in the sample projects.
I've outlined some potential solutions at https://github.com/dotnet/dotnet-docker/pull/3989#pullrequestreview-1077365611. PTAL @Rick-Anderson

Moved to #27141


Offset not working for search

The offset parameter is not working for the /v1/search endpoint, regardless of the value it always return the same results.
An example is this

Thank you for the issue. It fixed in #555. We deliver fix to production asap.

Fixed. You can test it! =)


[BUG] Offset is not applied when loading .chart files

Please give System Info
OS: Windows 10
CPU: Ryzen 7 5800X
GPU: RTX 2080Ti
Storage: SSD
Please give your StepMania Info
StepMania Version: Outfox 4.9.9 (latest release today)
Theme: default
Describe the problem
Loading a .chart file that has an offset will not have the offset be applied. No matter the offset in the .chart file, the song will always have a beat 0 offset of 0
Describe what should happen
The beat zero offset should be set according to the offset parameter, IIRC it should be set to -1 * (offset)
Test song with copyright free audio of me imitating the opening attached.
Add any other context or screenshots here.

Example.zip

This is now fixed for .chart files.
Seems when we were looking at the methodology used for the parser from your implementation for 5.2, the offset is not actually even calculated or configured correctly, and we missed it.
Thanks for the report, and I can happily report this is fixed now.

using your example as a testbed.

Fix will be added to the next release, but will be available in a nightly shortly.
Cheers for letting us know!


Status bar

Type: Feature Request
When files are clicked in explorer section, are not showing in status bar side by side. When a file is clicked earlier file will disappear. So how to solve this issue.
VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:49:37.021Z)
OS version: Windows_NT x64 10.0.19045
Modes:

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Feature Request: Unread button

Can you please add the button: Mark as Unread
You can simple allow everyone to add it in the "Customise Toolbar"
I really miss this button.
Many thanks

There is a Mark Unread button in the toolbar — sometimes it says Mark Read (depending on whether or not the the selected article is read or not).


Add column delimiter for SAP Table/open hub

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask<EMAIL_ADDRESS>(or NullMDR in github) for additional help.

/openapibot sdkautomation

/azp run automation - sdk

@NullMDR It seems I still lack of the permission although I am in the Azure group. Could you please advise? thanks.

/azp run automation - sdk

/azp run automation - sdk

@Jingshu923  will help add the SDK. Thanks.

Can one of the admins verify this patch?


How to open the development tools programmatically

I am a kiosk developer. The browser kiosk mode cannot open the development tools.

ctrl+shift+i works on opening the dev tools on firefox in kiosk mode.  Don't know about the other browsers as I only really use Firefox.


OpenCV docs

Reviewers:
@XaverianTeamRobotics/senior-programmers

Don't delete the branch, it's still WIP


No random responses

Hi! I have an issue with the responses I get with Chatterbot. I keep getting the same responses regardless of how many times I enter the input. It happens for my own corpus and the english corpus that comes with the package.
Here is my code:
https://pastebin.com/dSTBsmLB

@UziFTW Do you know what version of ChatterBot you are using?

@gunthercox can you please respond?

Your code sample that you posted looks correct. I am uncertain why you are getting the same response repeatedly.

You have to add the response_selection_method for the BestMatch adapter:
{
    'import_path': 'chatterbot.logic.BestMatch',
    'response_selection_method': 'chatterbot.response_selection.get_random_response'
}


[-𝐍𝐎𝐖-𝟐𝟎𝟐𝟒-]— Lana Rhoades Video Original Video Link Lana Rhoades Video Viral On Social Media X Now [1P2B3N]

20 seconds ago
L𝚎aked Video Lana Rhoades Original Video Viral Video L𝚎aked on X Twitter Telegram
[-𝐍𝐎𝐖-𝟐𝟎𝟐𝟒-]— Lana Rhoades Video Original Video Link Lana Rhoades Video Viral On Social Media X Now [1P2B3N]
[-wATCH-]— Lana Rhoades Video Original Video Link Lana Rhoades Video Viral On Social Media X Trending Now
[-wATCH-]— Lana Rhoades Video Original Video Link Lana Rhoades Video Viral On Social Media X Trending Now
[-wATCH-]— Lana Rhoades ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Lana Rhoades ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Lana Rhoades Video Original Video Link Lana Rhoades Video Viral On Social Media X Trending Now
Lana Rhoades Original Video video took the internet by storm and amazed viewers on various social media platforms. Lana Rhoades, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Lana Rhoades Original Video Viral Video L𝚎aked on X Twitter
Lana Rhoades Original Video video oficial twitter
L𝚎aked Video Lana Rhoades Original Video Viral Video L𝚎aked on X Twitter..

gfht


ratioMetric is missing a raw: type

ratioMetric combines the good query or the bad query with the total query to get a ratio.
Except the ratio itself can already be present as a precalculated metric. Sloth supports this option with a sli.raw.error_ratio_query option (example).
I'm proposing adding a similar option to ratioMetric. Something like:
raw: # raw ratio query, either "good/bad" + "total" or "raw" must be provided
  type: success | error  # indicates whether query returns the success or the error ratio
  metricSource:
    (…)

(I'm not married to calling it raw, so if anybody has better ideas, feel free.)

Just noticed that this is a duplicate of #7. Please keep it up for a bit, I'll try to make this an actual PR containing the proposed syntax asap, at which point I'll reference the original issue.

Cool idea, it makes so much easier to work with ratio data that you are already measuring, but you want to put in into SLO without splitting it. If you prepare PR i'd love to take look into it and review :smiley_cat:

Wouldn't a precalculated ratio just be a thresholdMetric?


Windows @ GCE: exec startup script to enable WinRM

Longer term, we should look at how better to configure a startup script. Different clouds within jclouds seem to use userMetadata in different ways, making our code fiddly.
Note this change isn't enough to get Windows@GCE working. We also need to write some code for generating + retrieving a Windows password. See https://cloud.google.com/compute/docs/instances/automate-pw-generation
If testing, the following location config is also important for users, to avoid jclouds waiting for port 22 to be reachable (and thus failing): templateOptions: { autoCreateKeyPair: false }

@andreaturli @bostko @neykov can you review please? Would like this available tomorrow (Tuesday) morning if possible!

LGTM


Temporary items (Crafting tab) do not respect size of formula item

Reproduction:

create/use a player character with class "Alchemist" (medium sized ancestry)
make a copy of any (equipment) item and change "Size" to a different size than the character (e.g. take a Healing Potion and set it to "Tiny")
add the Tiny potion to the known formulas of the crafting tab
add the formula to the "Advanced Alchemy" formulas
use the "Complete Daily Crafting" button

Expected:

the resulting temporary item is of size "Tiny", as the formula item is set to that

Currently:

the resulting temporary item is of size of the actor ("medium")
same when using "Quick Alchemy" or "Toggle Free Crafting" and using the "Craft" button (works as expected when those are not toggled on
=> currently there is no way to create temporary items as alchemist that are of a different size, e.g. to prepare a potion for a tiny friend

Screenshot:

"Craft" buttons under "Known Formulas" creates a tiny/medium item as expected, as long as "Quick Alchemy" is not active
"Complete Daily Crafting" creates two items of the size of the character

Formulas are agnostic to item size: the same formula can be used to craft an item of any size. So while the current behavior is intended (and really it should happen with all types of crafting), it'd be good to have a way to select the size of the item one wants to craft.


one question about predict

thank you for sharing, I encontered a problem while testing the data that the resulting disparity maps were completely black, can I ask what is wrong? Thank you!
warning:
warn('%s is a low contrast image' % fname)
data/testing/image_2/000073_10.png data/testing/image_3/000073_10.png

It means the code doesn't run correctly on your machine and produces only zeros.
You should first make sure that the libs are compiled correctly.
Then, whether the pretrained model is loaded correctly.
You can also try to find and locate which layer has bugs and output zeros by printing it out.
This should not be a bug of the code.

Hello, I have encountered the same problem. When I try to debug it, it comes to this:

I have found elements in output are all zeros after sga_cuda_forward, I worder if it is normal for a correct compile? Looking forward to your reply!

I think you can try to print the g0, g1,g2,g3 and input.
See whether they are reasonable values.
If yes, that should be the problem when you compile the cuda library.
For example, lib conflicts, compiled with some version of thirdlibs but run with another.
Also sometimes it maybe the pytorch problem. Did you try to install from source? Pip install sometimes have serious lib conflict problem.

It means the code doesn't run correctly on your machine and produces only zeros.
You should first make sure that the libs are compiled correctly.
Then, whether the pretrained model is loaded correctly.
You can also try to find and locate which layer has bugs and output zeros by printing it out.
This should not be a bug of the code.

Thank you very much for sharing. What should be the final training and prediction results?

It means the code doesn't run correctly on your machine and produces only zeros.
You should first make sure that the libs are compiled correctly.
Then, whether the pretrained model is loaded correctly.
You can also try to find and locate which layer has bugs and output zeros by printing it out.
This should not be a bug of the code.

I can't get the test data result in train.py

@UESTCtubiao you should use predict.py for testing. Train.py is mainly for training.

Sorry guys, my question might be irrelevant to your initial question, but I need feedback from people who are working with this repo.
So my question:
Where are the trained weights saved? it does not save anything in the --save_path.
OUTPUT='checkpoint'
mkdir $OUTPUT
CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7
python train.py --batchSize=2
--crop_height=288
--crop_width=288
--max_disp=192
--thread=16
--data_path='/home/jonmoham/DataForTraining/BlenderData/'
--training_list='lists/blender_train.list'
--save_path=OUTPUT
--resume=''
--model='GANet_deep'
--nEpochs=80
--nEpochs=1 2>&1 |tee logs/log_train_Blender3.txt
exit
After training there is nothing in the OUTPUT.

@YJonmo  change to set --save_path=${OUTPUT}/
Also please make sure you make the "train.py" save checkpoint every epoch.

Thanks, I still didn't manage to get the trained weights saved at $OUTPUT.
By the way, I do not know how to save checkpoint every epoch like you mentioned.
Regards,

@pinkteae @Alien1007 were you able to figure out this error? I too get black disparity maps with the warning:
UserWarning:  ./result/output.png is a low contrast image
Strangely, I get nice results for input image of size 1024x436x3, whereas the above error for image of size 4000x3000x3. I tried resizing the second image and then feeding, the output disparity map is not good but at least it's not completely black. I think size of image has an effect, and also the amount of disparity. When I input images with not too high disparity, the result is not very good. Any suggestions @feihuzhang?

Have you solved this problem? It is how to predict the high-resolution image. If the high-resolution image is cut and then put into the prediction, the prediction effect of each small resolution image cut out is not good. However, if the large-resolution image is resized into a small resolution image, the disparity map obtained by prediction is very good. The problem is that we don't know how to restore the large score accurately at this time Resolution of parallax, hope to get your answer!


[CI:BUILD] Packit: initial enablement

This commit will run COPR builds on every PR against all active releases of CentOS Stream and Fedora, thus allowing buildability checks before the PR merges.
Builds are done on a custom COPR project:
rhcontainerbot/packit-builds.
Ref: https://copr.fedorainfracloud.org/coprs/rhcontainerbot/packit-builds/
The build targets are set in the copr itself, so we don't need to explicitly mention them in .packit.yaml, making upstream configuration a lot simpler.
The spec.rpkg file meant for rpm builds post-pr-merge at rhcontainerbot/podman-next copr gets reused for packit builds, so the packit jobs are independent of Fedora / CentOS dist-git.
Fixes: #1103
Signed-off-by: Lokesh Mandvekar<EMAIL_ADDRESS>
What type of PR is this?

/kind ci
What this PR does / why we need it:
Checks for fedora and centos stream buildability pre-merge.
Which issue(s) this PR fixes:

Fixes #1103
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

I haven't enabled i686 packit builds cause I don't want to bother with those for podman and others either. Hope that's alright :D

hmm, where's the version specified? don't see it in Cargo.toml .  I think we can do without it as the release field of the generated rpms will show the HEAD commit id and the PR #.

Codecov Report

Merging #1104 (0fb5c8e) into main (4731234) will increase coverage by 0.44%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1104      +/-   ##
==========================================
+ Coverage   34.31%   34.76%   +0.44%
==========================================
  Files          13       13
  Lines        1119     1119
  Branches      391      389       -2
==========================================
+ Hits          384      389       +5
+ Misses        479      467      -12
- Partials      256      263       +7

@saschagrunert @haircommander PTAL. Also, ci / test-integration (pull_request) failed twice already.

@saschagrunert @haircommander PTAL. Also, ci / test-integration (pull_request) failed twice already.

third time's the charm :smile:

errrr wait ... let me make a few comment fixes.

nvm, the comment fixes can go in later. no biggie.


Using pandas with PyQt

I've written a simple data model for showing pandas DataFrame in a QDataTable. It is all in the sandbox, qtpandas.py. This file can be run stand-alone as an example.

Also, why instead of a setter use an instance attribute?
def __init__(self, df, parent=None):
    super(DataFrameModel, self).__init__(parent)
    self.dataframe = df

Do you want me to merge this or are you planning to do some more work here?

I'll redo this later on. Just skip it, it's sandbox anyway.
On Thu, Dec 8, 2011 at 12:37 AM, Wes McKinney <
<EMAIL_ADDRESS>
wrote:

Do you want me to merge this or are you planning to do some more work here?

Reply to this email directly or view it on GitHub:
https://github.com/wesm/pandas/pull/435#issuecomment-3055479


Add fixes for Stack deprecation

This adds a dart fix for the deprecated Stack.overflow as well as some tests for the fix.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I signed the CLA.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Verified the google failures are not the result of this PR. Manually changing to green.

Verified the google failures are not the result of this PR. Manually changing to green.


Provide default instance

When require('toposort-class'), a default instance could be returned, so the user doesn't have to do new.

Would you mind if I closed this one, too? I don't think having a global instance of it would be a good idea, even with .clear added. It would be too easy to have a memory leak since there is always a reference to it.

Your pick!

Alright, closed. Using new on a class is expected, I think.


Add post job option on curator menu

Implementa a issue https://github.com/PedroMarianoAlmeida/baby-dev-open-source/issues/32


Fill CUTOFF Gap with proxy process for 'Starch, at plant' and other starch cutoffs

Create proxy process to fill data gap. I simple proposal for filling the data gap is provided below. However, using more robust process data would be preferable if resources are readily available and the level of effort to utilize is not too great. Metadata should be provided for the proxy process.
Proposed dislaimer. Include in first line of description metadata field: "This process is a temporary proxy to replace a pre-existing CUTOFF (unlinked) process. This process should be replaced with more robust data as it becomes available or if the input contributes considerably to product system results."
Simple modeling approach:
Create industrial starch proxy to represent 90% corn and 10% potato feedstocks and process inputs per peer reviewed literature

I noticed that there are potato and corn starch cutoffs... should we change these to proxies and then create a combined starch process?

That sounds good to me


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ff0995gf1b/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_ff0995gf1b/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_ff0995gf1b/clone/recipe/meta.yaml:32: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_ff0995gf1b/clone/recipe/meta.yaml:38: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_ff0995gf1b/clone/recipe/meta.yaml:38: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_ff0995gf1b/clone/recipe/meta.yaml:38: missing_dev_url: The recipe is missing a dev_url
WARNING: /tmp/abs_ff0995gf1b/clone/recipe/meta.yaml:38: missing_description: The recipe is missing a description
Errors were found


nheqminer_zcash missing in 0.4b release

Why is nheqminer_zcash.exe is missing in 0.4b release?

Just enter the stratum details in location:
"-l stratum.zcash.nicehash.com:3357"

Thank you!


Add list of available models

Reference Issues/PRs

Fixes #224
What does this implement/fix? Explain your changes.

This PR adds a list of the current available models to the --help doc in the command line.
Modifies:
sweagent/agent/models.py
sweagent/__init__.py
run.py
Any other comments?
I'm very open to refactoring this commit/making whatever changes are necessary to fit in the style guidelines, or if there's a better approach to solving this problem that someone else sees!
🧡 Thanks for contributing!

Thanks! I'll deal with the merge conflict and will push some smaller changes on top :)

Thanks! I'll deal with the merge conflict and will push some smaller changes on top :)

Woohoo! Happy to do so, I'll keep my eyes peeled for any other issues that I could help with :)

One of the problems is that some models require a certain prefix that they strip (see for example the upcoming #207). I'll have to think how to handle this. At first I thought we could just add a PREFIX class variable, but in case of the OpenAI model, there's already multiple. So I'm actually not sure if we can simply list all of these. So perhaps instead every model class should have a list_models method which we then combine.

@klieret

One of the problems is that some models require a certain prefix that they strip (see for example the upcoming #207). I'll have to think how to handle this. At first I thought we could just add a PREFIX class variable, but in case of the OpenAI model, there's already multiple. So I'm actually not sure if we can simply list all of these. So perhaps instead every model class should have a list_models method which we then combine.

Ah, so for example
'azure:gpt-4'  when used as the argument for OpenAIModel will produce an instance of the Azure client, as opposed
to 'gpt-4' which will just produce the OpenAI client, and we want to distinguish that both are available models?

@klieret

One of the problems is that some models require a certain prefix that they strip (see for example the upcoming #207). I'll have to think how to handle this. At first I thought we could just add a PREFIX class variable, but in case of the OpenAI model, there's already multiple. So I'm actually not sure if we can simply list all of these. So perhaps instead every model class should have a list_models method which we then combine.

Ah, so for example 'azure:gpt-4' when used as the argument for OpenAIModel will produce an instance of the Azure client, as opposed to 'gpt-4' which will just produce the OpenAI client, and we want to distinguish that both are available models despite the models dict only containing references to gpt-4 after the fact?

Maybe then the approach is to create an abstract 'list-models' function on the BaseModel class(as per your idea), that handles for any number of prefixes, then define them in each model instance with the relevant prefixes and append them to the given models? If that sounds like the right approach I'd love to take another crack at this!

@klieret I tried out the aforementioned approach and it seems fruitful, if you get a chance to look it over would love to know what you think!

@klieret can we merge or close please?

@ofirpress The whole model selection thing is a bit messy at the moment. Cannot merge this as-is (also because we since have diverged from it). Planning to get back to this after the next updates to the agent.
@hminsky2002 Thanks again for this! I'll probably take another look at this in the coming weeks and will try start from your commit so you get partial authorship on it, but there's also a few changes that we probably need to make.

@ofirpress The whole model selection thing is a bit messy at the moment. Cannot merge this as-is (also because we since have diverged from it). Planning to get back to this after the next updates to the agent.
@hminsky2002 Thanks again for this! I'll probably take another look at this in the coming weeks and might try start from your commit so you get partial authorship on it, but there's also a few changes that we probably need to make.

No worries! Thanks for taking the time to look it over, happy to have tried it out! partial authorship would be cooooool but no sweat either way B)


Anchor fixes

Closes #26

#define STATE_COUNT 243
#define STATE_COUNT 313

That's what I was worried about... As we use the parser for (potentially very large) tree view in Neovim, I'm hesitant whether this is worth it?

313 is nothing really, like way smaller than most other small grammars already and is only a 4kb increase in compiled size for me

back to 243 anyways


Create an Openshift-console client

Create an Openshift-console client
currently we have queries for "mock" static data, and for the stand alone application,
we are missing a client that can get data from Openshift console proxy server.

@yaacov this is the same use case we solved in https://github.com/konveyor/crane-ui-plugin with https://github.com/konveyor/crane-reverse-proxy. That service can be exposed via a service proxy configuration in the ConsolePlugin CR. The UI can create secrets on the host cluster using the plugin SDK's k8s client containing remote cluster URLs, and then make requests via that proxied URL using the kube-client module in lib-ui.
I'm happy to help with this implementation, I got it working smoothly in crane-ui-plugin before it was put on hold :)

@jmontleon maybe we should rename crane-reverse-proxy to k8s-reverse-proxy or something, since it can be used for any app that wants to make API calls to another cluster such as this, not just crane.

Ah, but hang on, I may be getting confused -- the remote providers would be accessed using the existing inventory API, right? @yaacov are you just looking to interact with the k8s API on the cluster the plugin is installed on? There are functions exposed by the plugin SDK for that (k8sGet, k8sPost, useWatchK8sResource, etc)

@mturley HI, some more information and context:
we plan to proxy the inventory using the plugin sdk mechnism:
https://github.com/konveyor/forklift-console-plugin/blob/c15c9ec996d155f72a644b3660ee3734bb0c047c/deployment/forklift-console-plugin/templates/consoleplugin.tpl#L14
and authenitacte using the authorize: true flag in the proxy api.
we plan to use the plugin fetch/post utilities, useK8sWatchResource
https://github.com/yaacov/forklift-console-plugin/blob/4015d1df5d8095dc5feb3f014bb5dc03b47f3b2e/src/extentions/Providers/ProvidersPage.tsx#L164
and a custom fetch for inventory:
https://github.com/yaacov/forklift-console-plugin/blob/4015d1df5d8095dc5feb3f014bb5dc03b47f3b2e/src/extentions/Providers/hooks/useInventory.tsx#L11
we are missing the best way to glue together this hooks and proxy patterns with the current fetch mechanism

I see, okay. If you want to stick to the react-query pattern used elsewhere you can replace most of the contents of that useInventory hook with useQuery, using that consoleFetchJSON in your queryFn and using a select function for the indexing you're doing there. react-query handles the state internally, fetches on mount and refetches for you under certain conditions.
https://react-query-v3.tanstack.com/reference/useQuery
https://react-query-v3.tanstack.com/guides/important-defaults

Thank you for for the links.

If you want to stick to the react-query pattern used elsewhere you can replace

I'm actually thinking of the pros and cons of each aproach :-)
I don't know what is best, on the one hand I don't want to do too many changes to the current code (e.g. mockable...), on the other I want to slowly converge to using the console sdk patterns e.g. only uaeK8s..., but react-query looks cool, so  that is also apoint to consider :-) , @sjd78 @rszwajko WDYT?

@yaacov

I don't want to do too many changes to the current code (e.g. mockable...), on the other I want to slowly converge to using the console sdk patterns e.g. only uaeK8s..., but react-query looks cool,

react-query provides caching and other benefits, however useK8s... seems to fetch data via Console's redux store so this is already cached. I assume it also gets re-loaded when needed. So for resources we can drop using react-query
non-resources queries (inventory) would definitely benefit from react-query. It seems that the extensions API is limited to consoleFetch. Going the
mock mode is very useful and I would keep this feature regardless of underlying query library i.e. I could imagine useMockableK8s...

+1, you definitely don't need react-query for the places where you're using useWatchK8sResource(s) especially, which have the benefit of re-rendering when data changes via websockets instead of having to use the react-query refetchInterval. That will certainly improve the user experience of watching the migration status change. It makes sense to me to only use useQuery in places where you're using another service like the inventory API. useMutation might still be useful though (for POST/PUT/PATCH) since I don't believe the console SDK has a built in way of tracking the result / state / error of its k8sPost etc.
There was also an effort a while back to try and figure out if we could load things from the inventory API via websockets too, because it does support a "watch mode" if I remember correctly. @jortel would know. The issue we ran into there is how to include the Authorization bearer token when opening the socket, because the browser's WebSocket API doesn't support arbitrary headers (very strange imo). If there is a way to get that working, I can see a scenario where you don't need react-query at all, except maybe for mutations.
As for the mock mode, @rszwajko do you anticipate wanting to use the UI with mock data while connected to a real cluster? The original use case (building static preview versions of the UI to deploy on surge.sh and automatically post a link in each PR) wouldn't work with a plugin I imagine, since you'd need the whole console to be built statically and runnable with no cluster. Either way, the useMockable... with mock data conditionally used in the actual UI source is something I sort of regret now that I know about https://mswjs.io/.

@mturley

As for the mock mode, @rszwajko do you anticipate wanting to use the UI with mock data while connected to a real cluster?

It depends how you define "real cluster" - I'm running minikube + console in off-cluster-mode (kudos to @yaacov for setting it up).  Mock mode definitely unblocked my flow.

The original use case (building static preview versions of the UI to deploy on surge.sh and automatically post a link in each PR) wouldn't work with a plugin I imagine, since you'd need the whole console to be built statically and runnable with no cluster.

@yaacov would off-cluster mode handle that? or perhaps the next gen console plugins could handle that via standalone app mode?

Either way, the useMockable... with mock data conditionally used in the actual UI source is something I sort of regret now that I know about https://mswjs.io/.

For sure there is some space for improvements here but it's not the most urgent enhancement:)

Ah, the minikube + off-cluster use case for mock mode makes total sense. Nice.

or perhaps the next gen console plugins could handle that via standalone app mode?

yeah, I think that would certainly make it easier to have a plugin target a barebones static shell app for preview deployments.

it's not the most urgent enhancement

heh yeah, sorry, I'm focusing too much on the back-burner stuff that was interesting to me when we had no high-priority dev to do on forklift :) thanks for humoring me

@yaacov would off-cluster mode handle that? or perhaps the next gen console plugins could handle that via standalone app mode?

I hope the new SDK will help here, @sjd78 ?

Speaking of the new SDK, I assume you're talking about https://github.com/openshift/dynamic-plugin-sdk (as opposed to https://github.com/openshift/console/tree/master/frontend/packages/console-dynamic-plugin-sdk)? From my earlier conversations with them about it, I think it is currently not compatible with the OpenShift Console UI (it's being developed for the new Hybrid Application Console and the intention is to converge the two SDKs in the future so plugins can be compatible with both host UIs). I may be wrong here. But depending on your intended release schedule for this plugin, it might be too early to use the new SDK. See discussion from a while back here: https://coreos.slack.com/archives/C011BL0FEKZ/p1651188114246069

I think it is currently not compatible with the OpenShift Console UI

AFAIK the console will support it in 4.12, @vojtechszocs please keep me honest here

cc:// @sjd78 ^^

I think 4.12 is the GA of the original console plugin SDK (which has been functional but unsupported in 4.9-4.11). Maybe it's both, I'm not sure.

@yaacov you're right about the new SDK being supported in OCP 4.12, according to Sam Padgett here: https://coreos.slack.com/archives/C011BL0FEKZ/p1661460257313869?thread_ts=1661455337.669829&cid=C011BL0FEKZ


Tabs are not disaplaying the view content

I just downloaded the Tabbed Views core template and then in app.js I enabled the pushState. Now when I click on any tab it does display the content/page. Tabs become active but the content does not change. It keep displaying the first page

Sorry but pushState can only work for single main View.


addTrackEventIkeyConfig

linked issue: https://github.com/microsoft/ApplicationInsights-JS/issues/1595
this PR makes the following updates:

add an optional iKey config to trackEvent/PageView/Trace/Metric/Dependency, if the defined iKey is not empty, envelope data will use this iKey instead.
fix the issue that iKey will always use the senderConfig iKey
add more test coverage

Removed the linked issue as this causes GitHub to close the issue, where we tag it as "fixed - waiting release" for tracking purposes


Use a up-to-date swarm client URL

maven.jenkins-ci.org has been deprecated and redirecting to repo.jenkins-ci.org for years

@rtyler rebase?

@jhoblitt Travis still hates beaker (womp womp); i'm merging


GPG KEY Incorrect, repo failing to install anything

This just happened and I'm not sure as to when the key was updated, but the key listed in this repo is being rejected with:
The GPG keys listed for the "IUS Community Packages for Enterprise Linux 7 - x86_64" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
Failing package is: php72u-bcmath-7.2.23-2.el7.ius.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/IUS-COMMUNITY-GPG-KEY
UPDATE: Turns out the key was changed in May.
Here is the link to the new key: https://github.com/iusrepo/ius-release/blob/master/RPM-GPG-KEY-IUS-7

any estimate on when this might be fixed?


Can this tool be used in the command line?

And also can the tool automatically format a list of files instead of a single file?

Hi @jafara . The general answer for both questions is no. It's implemented using XcodeKit which doen't give access to the whole project, but only for currently opened file.
But there is a module of the Snowonder project called ImportArtisan, which is an independent part that is responsible for import declarations processing. I'll think about implementation of command line interface built on top of it. And of course, if you already have such kind of implementation of it feel free to open pull request 😊


Integrate Gollum Dashboard Widget for overplotting spectral models

See https://github.com/BrownDwarf/gollum/issues/45

Cross-ref @gully https://github.com/BrownDwarf/gollum/issues/67

Creating a nohup bokeh serve instance running through the apache server. Perhaps point an iframe on the main website towards this server.

Update: @gully recently won a NASA grant to do this work!

Given that Gully is starting a new job, this is not likely to happen anytime soon. Keeping it open though.


Remove partial key size limit from trie codec

This PR remove the partial key size limit of the trie codec.
Previous size limit was set to U16::max nibbles, and not really meant to be reach.
It occurs that when reach, (as reported), the state will not be readable, and generally previous idea to truncate key does not sounds practical (difficult to implement with rocksdb key prefixing and even if it can be deterministic, storing at a truncated key will lead to a state that is not really usable).
After this change limit will be hardware limit (u32 with wasm u64 native), runtime should therefore enforce they are not reaching these limits, more generally the codec is not suited at all for big keys and any sane runtime will never reach these numbers (even old limit), but it will be good if the codec behave properly though.

This requires an update of the spec.
Also please add some test.
CC @athei this is especially important for contracts. There should be some sensitive upper limit on key lengths.

I did add a test on the upper limit (was already implemented from my attempted at implemented key truncate from codec change only).
I find this test not too usefull though, but got no other idea what to test.
Alternatively we can also change the node codec trait to allow returning an error and error on the upper limit, but would require more changes.

CC @athei this is especially important for contracts. There should be some sensitive upper limit on key lengths.

Thanks. We are already limiting the key:
https://github.com/paritytech/substrate/blob/696bdc67af5fd83aca318263dbd405593b043ba3/frame/contracts/src/lib.rs#L331-L332

@cheme does this requires an update of the spec?

@cheme does this requires an update of the spec?

I would think no (except for cumulus pvf maybe, but I would really not expect the limit to be reach somewhere (otherwhise should put the change also behind a new version of storage root and keep old codec)).

I more meant, is the spec currently already mentioning any upper limit that we should remove?

Ok :face_palm: , added https://github.com/w3f/polkadot-spec/issues/578

bot merge

@cheme can you please run cargo fmt?


Modded NBT-Tags not implemented in case-item

Spark link
No response
Plugin Version
1.13
Server Version
1.20.1
Server Platform
Spigot
Describe the bug
I am the owner of a Cobblemon server, and I wanted to use your plugin to create cases with Pokémon. However, for some reason, the method I wanted to use to implement this does not work completely correctly.
I wanted that when I add an item using the command /cc additem CRATE cobblemon:pokemon_model with the NBT tag {species:"cobblemon:pikachu"}, the item would display correctly. The item also has an NBT tag from CMI that triggers certain commands. But for some reason, the cobblemon tag is not displayed. However, the NBT tags that I assigned from CMI appear correctly both in the file and when the item is given as a reward. Could you help me fix this issue?
Crate Type
None
Steps to reproduce

Install Cobblemon and CrazyCrates
Add item in crate
Try get reward-pokemon (cobblemon model)

Additional context
No response
Agreements

[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] I ticked all the boxes without actually reading them
[X] My version of Minecraft is supported by CrazyCrew.

We do not support 1.20.1,
We do not support Spigot,
and the plugin version 1.13 is outdated.
we also do not support modded hybrid servers either, and thus cannot specify fixes for them.


Update CloudFlareUtilities library to 1.3.0.

This version of the library adds support for addition types of CloudFlare authentication, so logging in to Procurement should be much, much less troublesome now.
Fixes #1002.

👍
@Stickymaddness Can we get some merges, please?


Return headers sync upload

Resolves #10685
Note that EncryptedBlobClient inherits BlobClient's upload method, so this change implicitly applies to EncryptedBlobClient as well.

@JonathanGiles could you take a review on the API changes here.


Switch to GitHub's new issue templates.

GitHub came out with a new issue template workflow a while back which I enjoy a lot. I think using this approach will help facilitate maintenance of issues/features and help new users create more meaningful issues.
You can see an example of how the new "create issue" screen looks like here: https://help.github.com/en/articles/about-issue-and-pull-request-templates
New feature requests will be tagged with kind/feature and bugs with kind/bug automatically.
I also modified the content of bug_report.md slightly from the original content since issues aren't being closed in 7 days and no additional commands are provided for people to run. Open for feedback on how to improve this content.

Signed-off-by: Eric Hotinger<EMAIL_ADDRESS>

Codecov Report

Merging #3358 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3358   +/-   ##
=======================================
  Coverage   44.83%   44.83%
=======================================
  Files         113      113
  Lines       12531    12531
=======================================
  Hits         5618     5618
  Misses       6057     6057
  Partials      856      856

Flag
Coverage Δ

#linux
48.7% <ø> (ø)
:arrow_up:

#windows
40.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 8bb5213...63a8dee. Read the comment docs.

LGTM

Thanks @crosbymichael @estesp  - so shiny now. ⭐


Fix jupyter update

This is mainly a port to the newer jupyter version. It works with teh conda environment and hopefully also with pip (didn't test that...).
Closes: #36  -> new knitpy.render(filename, format) function
Closes: #34 -> use the new jupyter version for traitlets
Closes: #33  -> replaced all old code imports with new ones. This also makes knitpy incompatible with older versions of ipython, which still included the notebook/...
Partly adresses: #29 -> mimedata isn't a problem anymore, but the matplotlib stuff still is...

Ok, travis is green, merging...


Bump golang to 1.18

Geth bumped the minimum golang version to 1.18 a few days ago. Since we're building directly from master we need to do the same.

Going to go ahead and just merge since CI is broken on main.


python310Packages.greeclimate: 1.0.3 -> 1.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.greeclimate is: "Discover, connect and control Gree based minisplit systems"
meta.homepage for python310Packages.greeclimate is: "https://github.com/cmroche/greeclimate"
meta.changelog for python310Packages.greeclimate is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.1.0 with grep in /nix/store/468ck4lsvdwli6rbji6rwa0270sy800c-python3.10-greeclimate-1.1.0

found 1.1.0 in filename of file in /nix/store/468ck4lsvdwli6rbji6rwa0270sy800c-python3.10-greeclimate-1.1.0

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.gree
python310Packages.greeclimate
python39Packages.greeclimate

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/468ck4lsvdwli6rbji6rwa0270sy800c-python3.10-greeclimate-1.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.greeclimate https://github.com/r-ryantm/nixpkgs/archive/dd1f13c3243c7e64211c01427e039d142f331e2e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/468ck4lsvdwli6rbji6rwa0270sy800c-python3.10-greeclimate-1.1.0
ls -la /nix/store/468ck4lsvdwli6rbji6rwa0270sy800c-python3.10-greeclimate-1.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.gree
python310Packages.greeclimate
python39Packages.greeclimate

Maintainer pings
cc @dotlambda for testing.

duplicate of #163092


Added docstring and formated code to PEP8

Made changes to adapt the code to PEP8 rules and added the docstrings on methods an classes.

Hey thanks for this. I really like the exceptions changes you made. The origin of those exceptions is a lot clearer now.
If you can sign our CLA, I'll merge this in.
https://developer.vimeo.com/cla

Hey, just signed the CLA.

Thanks!


fix: arg code for PostgreSQL read replica detection

Overview/Summary

Initial ARG code "Find Database for PostgreSQL instances that are read replicas" but we're looking for "Database for PostgreSQL instances that do not have read replicas".
Before my fix 👇

After my fix 👇

As part of this pull request I have

[X] Read the Contribution Guide and ensured this PR is compliant with the guide
[X] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Ensured PR tests are passing
[X] Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

Thanks for these improvements @jdmsoss! When you have a chance, could you share a screenshot of the query showing the correct results please?

Please see my screenshots in my initial comment.


Version 2

Update ESLint config according to these suggestions: https://github.com/einride/eslint-plugin/discussions/31

Can you review this @bjornlexell, and mainly check that https://github.com/einride/eslint-plugin/pull/34/commits/f5fef358cb23dbbab725e6e87a11bab9e187c091 has changes according to https://github.com/einride/eslint-plugin/discussions/31? 🙂


docs: update readme

Codecov Report

Merging #185 (f44bb10) into main (98433e1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #185   +/-   ##
=======================================
  Coverage   80.24%   80.24%
=======================================
  Files          20       20
  Lines        2480     2480
=======================================
  Hits         1990     1990
  Misses        490      490

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update array-slice.md set threshold 256

In go 1.22, the threshold was set to 256 when increasing the slice capacity.
https://github.com/golang/go/blob/b6778c5230d554c1ba1a69b104513021467d32b2/src/runtime/slice.go#L274

I made a mistake - from version 1.18

Thanks


Update language detection test for local testing

What does this PR do?

Removes the hard coded agent version used for local testing, as we can now test using E2E_PIPELINE_ID to specify an CI version to test against
Add the E2E_DEVMODE env var option so the test environment is not destroyed for debugging purposes.

Motivation
Test cleanup
Additional Notes
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
No functional changes

/merge


[feat] added get_model and get_models fct to mmcif

Code of Conduct
Description
Added get_model and get_models methods to PandasMmcif class, similar to PandasMmtf.
Related issues or pull requests

Pull Request Checklist

[ ] Added a note about the modification or contribution to the ./docs/sources/CHANGELOG.md file (if applicable)
[ ] Added appropriate unit test functions in the ./biopandas/*/tests directories (if applicable)
[ ] Modify documentation in the corresponding Jupyter Notebook under biopandas/docs/sources/ (if applicable)
[ ] Ran PYTHONPATH='.' pytest ./biopandas -sv and make sure that all unit tests pass (for small modifications, it might be sufficient to only run the specific test file, e.g., PYTHONPATH='.' pytest ./biopandas/classifier/tests/test_stacking_cv_classifier.py -sv)
[ ] Checked for style issues by running flake8 ./biopandas

LGTM! Can you add a couple tests? https://github.com/BioPandas/biopandas/blob/main/biopandas/pdb/tests/test_multiple_models.py

I've updated the existing changelog. Can you git rm the changelog you created?


Default cities

Everything except loot tables that don't show on the wiki

Looks good, but I'd like to have keycards included and also just run through each undocumented room and set the loot table to whatever you get so there is always loot.


Compile-time-weaving for injecting Spring Beans into unmanaged objects broken?

We use compile-time-weaving for injecting Spring Beans (using @Autowired) into unmanaged objects inside a Spring boot application for a long time now. Inside the pom.xml, aspectj-maven-plugin is used to do the magic. Using the plugin from org.codehaus.mojo worked fine up to java 16.
To upgrade to java 17, we tried to switch to dev.aspectj plugin assuming not to change the behavior - but this somehow breaks the compile time weaving. Those @Autowired variables are suddenly null with this plugin.
Some version information:

Spring boot 2.7.8
Java 17

Sample of a class to be weaved:
package de.ba.wws.dtoassembler.impl;

@Configurable
public class ArtikelinfoDtoAssembler {

    @Autowired
    private ArtikelSearchDao artikelSearchDao;
    @Autowired
    private ArtikelBeinhaltetDao artikelBeinhaltetDao;
    @Autowired
    private BestandDao bestandDao;

    // ...
}

Extract from pom.xml, ${aspectj.version} is 1.9.8:
            <!-- ... -->
            <plugin>
		<groupId>dev.aspectj</groupId>
		<artifactId>aspectj-maven-plugin</artifactId>
                <configuration>
                    <proc>none</proc>
                    <showWeaveInfo>true</showWeaveInfo>
		    <!-- <verbose>true</verbose>-->
                    <complianceLevel>${java.compiler.version}</complianceLevel>
                    <Xlint>ignore</Xlint>
                    <aspectLibraries>
                        <aspectLibrary>
                            <groupId>org.springframework</groupId>
                            <artifactId>spring-aspects</artifactId>
                        </aspectLibrary>
                    </aspectLibraries>
                    <sources>
                        <source>
                            <basedir>${basedir}/src/main/java</basedir>
                            <includes>
                                <include>de/ba/wws/bo/*</include>
                                <include>de/ba/wws/dtoassembler/impl/*</include>
				<!-- ... lots more ... -->
                            </includes>
                        </source>
                    </sources>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>compile</goal>
                        </goals>
                    </execution>
                </executions>
                <dependencies>
                    <dependency>
                        <groupId>org.aspectj</groupId>
                        <artifactId>aspectjrt</artifactId>
                        <version>${aspectj.version}</version>
                    </dependency>
                    <dependency>
                        <groupId>org.aspectj</groupId>
                        <artifactId>aspectjtools</artifactId>
                        <version>${aspectj.version}</version>
                    </dependency>
              </dependencies>
            </plugin>

Thanks for any help!

You claim that switching the plugin causes the problems, but maybe it is not the plugin but rather switching to Java 17, which you cannot do with the Mojohaus plugin in the first place. To isolate the problem and find out if this plugin really is part of the problem, does the exact same project which builds on Java 16 with the Mojohaus version also build with this one here, or does it break already?
Furthermore, in order to find out what is the problem with your Java 17 compilation, please provide a minimal reproducer project on GitHub. I do not need your original project with confidential code, just a small, but complete reproducer. I cannot compile, run and debug your out-of-context snippets. Without further evidence, for now I am assuming that the problem sits in front of the computer. As soon as I have reprodiucible evidence to the contrary, I shall be more than ready to investigate and fix the problem, either in the project or in AspectJ itself.

${aspectj.version} is 1.9.8

P.S.: No need to stick with 1.9.8, you can use the latest release 1.9.19.

Thanks for your quick responses! I'll try to setup a small project that reproduces the issue and then come back to you.

While trying to setup a reproducer project by stripping down our big application into something small, I found out that there was another piece in our pom (<pluginExecutionFilter>) that needed to be switched to the dev.aspectj plugin as well. Doing so solved the issue!
Without further evidence, for now I am assuming that the problem sits in front of the computer.
I must admin that your assumption was right ;-) . Sorry for bothering you.

You were not bothering me at all. After all, you thought that there was a problem in this plugin. You just have to bear with me challenging your assumptions, if I think I have reason to do so. 😉
I am glad you managed to solve the problem. This is why I like asking for sMCVEs: By creating one, usually you learn something about your own problem already. Creating a reproducer is a great tool to focus on the essential part of a problem. 🙂

there was another piece in our pom (<pluginExecutionFilter>) that needed to be switched to the dev.aspectj plugin as well

Note to myself for similar future inquiries: Said part of the POM should be completely irrelevant for the Maven build as such. It is only used to map plugin executions to the Eclipse IDE lifecycle when importing Maven projects.


Increased stability of metric asynchronous execution

What type of PR is this?
/kind enhancement

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

That's no longer necessary.


Add handling for invalid input types in sent events

Description
Events that are sent with numeric values get rejected with a pretty opaque go error message: json: cannot unmarshal number into Go struct field Event.events.attributes of type string.
Proposed solution
A better-formed error response which highlights the problematic event in a more human readable format would aid in future troubleshooting/look more intentional.
Context
See #269

The same issue happens when you trie to sent an array: jcannot unmarshal array into Go struct field Exception.exceptions.context of type string


Update github links to xref links

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

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 856b560:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 1d5c6b3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit 3af7a87:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit 0fdffc8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit 53837f1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit bfaba2f:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 2a43585:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit a605637:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

.openpublishing.redirection.json
:x:Error

Details

.openpublishing.redirection.json

Line 693, Column 4: [Error-json-syntax-error] After parsing a value an unexpected character was encountered: {.
Line 693, Column 4: [Error-json-syntax-error] After parsing a value an unexpected character was encountered: {.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:bulb:Suggestion

Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

.openpublishing.redirection.json

Line 270, Column 74: [Suggestion-redirect-url-invalid] Can't redirect document ID for redirected file 'techniques/testing-and-debugging.md' because redirect URL '/quantum/user-guide/using-qsharp/testing-debugging' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.

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

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:bulb:Suggestion

Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/ProgramStructure/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

.openpublishing.redirection.json

Line 270, Column 74: [Suggestion-redirect-url-invalid] Can't redirect document ID for redirected file 'techniques/testing-and-debugging.md' because redirect URL '/quantum/user-guide/using-qsharp/testing-debugging' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.

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

Docs Build status updates of commit 61d19b7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:bulb:Suggestion

Details

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/Expressions/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/ProgramStructure/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/TypeSystem/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

.openpublishing.redirection.json

Line 270, Column 74: [Suggestion-redirect-url-invalid] Can't redirect document ID for redirected file 'techniques/testing-and-debugging.md' because redirect URL '/quantum/user-guide/using-qsharp/testing-debugging' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.

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

Docs Build status updates of commit 4a7051e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/Expressions/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/ProgramStructure/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/TypeSystem/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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

Docs Build status updates of commit f50564f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/user-guide/host-programs.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/Expressions/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/ProgramStructure/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/TypeSystem/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

articles/user-guide/host-programs.md

Line 62, Column 313: [Warning-xref-not-found] Cross reference not found: 'microsoft.quantum.qsharplibintro'.
Line 603, Column 48: [Warning-xref-not-found] Cross reference not found: 'microsoft.quantum.qsharplibintro'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/user-guide/host-programs.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/Expressions/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/ProgramStructure/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/TypeSystem/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/programs.md
:white_check_mark:Succeeded
View

articles/user-guide/toc.yml
:white_check_mark:Succeeded

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


Feat improvements m5180 driver

This PR includes some minor improvements of the Coppermountain M5180 driver and it passes kwargs to its baseclass as required by qcodes.
@FarBo could you please review it? Thanks.

Thanks @simonzihlmann for the update
It looks good to me

great, thanks!


Feature/p2p mods

Still unresolved: Identifiers. Leigh wants us to use oai identifiers. We were previously using isShownAt.

Going to fix codacy issues...

This is now in CQA and could use a review @moltude @AudreyAltman !

Looks good other than the impending ID breakage.

Yeah, I have to reach out to them about that. Thanks for reminding me!


Add experimental hook declarations to index.d.ts

Currently a blocker with using these hooks with typescript-based projects.
Should resolve #216. Per feedback on #217, this PR declares types for all experimental hooks. Discussion on #217 considers migrating the library to be native typescript, but this is a less-invasive stopgap.

Thank you!


VoteMVP Frontend: Vote slider control does not default to the expected min/max values

5/4/22 AirClaim Votemvp Frontend v0.5.2qa5 Link: https://tjrhs-gqaaa-aaaad-qa24a-cai.raw.ic0.app/vote
On the Vote Locking Threshold page, the slider control does not default to the expected min/max values.
Default showing as 0.017-0.025. Current Price in exchagerate table is 0.01300149144607182. Hence, expecting range to be 0.016700-0.033400.
To work out the max threshold value:
f (current_price < HARD_EXCHANGE_RATE_FLOOR of 0.0167) {
locking_threshold_upper_limit = lock_factor * HARD_EXCHANGE_RATE_FLOOR;
} else {
locking_threshold_upper_limit = lock_factor * current_price;
}
lockfactor is configurable and is currently set to 2.0

Changed vote range to be in steps of "0.0001" so range is 0.0167-0.0334 also with changes from calc v0.5.4

6/4/22 Retest in v0.54-qa5. Slider control defaults to the expected min/max value of 0.016700-0.033400. I can see the steps in increments of 0.0001. However, Tom wanted all locking threshold values to be in 6 decimal places. If that's not possible, please have a chat with Tom. Will keep this open for now.

.

11/4/22 Retest in v0.5.4-qaii. Slider control now defaults to the correct min/max locking threshold values. However, all locking threshold values must be in 6 decimal places. See JeromeK's confirmation below:
Jerome | freeos.io | freedao.io — Today at 12:33
6…. although I’m not fond of having that many decimals in the UI
But we have to be accurate

19/4/22 Retest in new rel v0.5.5-qa5 using billbeaumont's account in iteration 16.
On Vote Locking Threshold page, min and max values were displayed on each end of the slider control prior to clicking on the slider so the user knows what the locking threshold range is. Locking threshold values were displayed with 6 decimal places where appropriate i.e. trailing zeroes omitted. This means that the default locking threshold ranges were showing as 0.0167 and 0.04 accordingly. Also, blue dot on the left hand side of the page is no longer showing.
Note: 19/4/22 JK is happy with the omission of trailing zeroes when displaying the locking threshold amounts.
Issue fIxed. Closed.


AutoGenerateAttribute decorator doesn't autogenerate ID for entitites

Hello, I tried following this guide to create an entity and try the library, my User entity is practically copy-pasted from the guide
The entityManager throws "id" was referenced in USER#{{id}} but it's value could not be resolved. if I try to do
const user = new User()
user.name = 'Loki';
user.status = 'active';
user.email =<EMAIL_ADDRESS>const response = await db.create(user)

It doesn't throw when I manually set the ID though

Also, I'm using a local DynamoDB container (in case it matters).

Hi @franco-roura
Closing this as I have not seen any more updates from you.
If the issue continues please feel free to reopen.


Add publishing-app custom dimension

This will help differentiate smart-answers from transactions.
Related to https://github.com/alphagov/govuk_publishing_components/pull/470.
https://trello.com/c/vhfMGngX/239-investigate-and-correct-smart-answer-google-analytics-tracking

What's the reasoning behind the ordering change? Numerical ordering is really useful when looking up dimensions.

@cbaines I hadn't noticed the custom dimension ordering! I thought it was a near-alphabetical ordering so wanted to improve it. Have removed that commit now.


Bugfix #13. Table.Create(data) throws PublicPropertiesNotFoundException

Issue #13 describes a bug that can result in unwanted behavior. Classes which serve as data models for table creation and lack public properties would result in the construction of an empty and deformed table. A preferable behavior, as mentioned in the original issue, is to throw an exception which can be properly handled.
Now when an empty list of class properties is returned, and exception is thrown. In order for the exception to be descriptive, a custom exception PublicPropertiesNotFoundException was created. This has been tested and is passing.

@tdwright Great! Thanks for doing your part to keep the open source community enjoyable :)


[New API] : CurrencyLayer API

Brief Description 🤓
Provides real-time and historical exchange rate data, including conversion between different currencies.
How will you develop it?🤩
react,js
Deployment
None
Select the open source program you are contributing to
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINES of this project.

Greetings @AmruthaPariprolu🎀 ! , We are excited to have you dive into another issue with us!🚀
Your involvement in our project has been invaluable, and we're confident that your skills and insights will help us conquer this challenge😇.  Use command /gssoc24 to self assign the issue.  This issue represents an exciting opportunity for us to improve and enhance our project, and we are thrilled to have you on board.
We request you to follow CONTRIBUTING GUIDELINES.
Looking for your PR soon!
In case of any issues, you can contact us on Discord.❣

/gssoc24


use GraphQL call instead of git push

If we care about restricting git push in the workflow and create a signed commit, we can use a GraphQL API call instead of git push.
I've tested it with https://github.com/TestOrgPleaseIgnore/bluesky/actions/runs/12287645499/job/34290039602, which created https://github.com/TestOrgPleaseIgnore/bluesky/commit/b10d255dc8d7df71cda4f740bb0594bff9c28882

Do we actually care about signed commit shere? And what's the downside of git push in the workflow? I do find the current format easier to read/debug, and easy to replicate/test locally.

Yeah I kinda agree, it started as a simple idea, but it turned out to be more complicated than I envisioned. Let's keep the current approach for now


added handle user fn

Call handle_user_command() func

It's called at line 140

It's called at line 140

Umm sorry I meant call processed_user_input(). Check the description again


Update version number of the agent for 1.13.0-alpha0

Having the wrong agent version there causes the following error:
https://github.com/kata-containers/osbuilder/pull/520#issuecomment-832874777
ERROR: rootfs build failed
INFO: ERROR: test failed
INFO: rootfs:
total 8
drwxr-xr-x 17 root root 4096 May  5 17:22 clearlinux_rootfs
drwxr-xr-x 21 root root 4096 May  5 17:22 ubuntu_rootfs
INFO: images:
total 0
INFO: running: /home/runner/work/osbuilder/osbuilder/../tests/cmd/kata-manager/kata-manager.sh configure-image
file not found: /home/runner/work/osbuilder/osbuilder/../tests/cmd/kata-manager/kata-manager.sh at /usr/bin/chronic line 66.

Fixes: #3170
Signed-off-by: Christophe de Dinechin<EMAIL_ADDRESS>

This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.

Important:
All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.

This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:

http://lists.katacontainers.io/pipermail/kata-dev/2020-November/001601.html
http://lists.katacontainers.io/pipermail/kata-dev/2021-April/001843.html
http://lists.katacontainers.io/pipermail/kata-dev/2021-May/001896.html

If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.


ADD New search component for GridFields

Resolves silverstripe/silverstripe-cms#1777

I think this got merged prematurely. I've restored the branch and force-push over the merge commit on the 4 branch.
I've open an identical PR at https://github.com/silverstripe/silverstripe-framework/pull/8338

I think this got merged prematurely. I've restored the branch and force-push over the merge commit on the 4 branch.

Sorry for merging this, but in the future please do not rewrite history once it's on the main branches. This is explicitly against our contribution/maintainers guide.
If there's a bad commit, revert it. if there just needs to be amendments, they could either be an additional PR or it can be reverted and resubmitted.


ARROW-4018: [C++] Fix RLE tests' failures on big-endian platforms

This PR adds big-endian support in RLE related classes. The data for RLE is stored using a little-endian format. The current code assumes a little-endian CPU in two places.

RleDecoder::NextCounts (fix was proposed in ARROW-4018)
packing and unpacking from https://github.com/lemire/FrameOfReference/blob/6ccaf9e97160f9a3b299e23a8ef739e711ef0c71/src/bpacking.cpp

After applying #7136 & this PR, the following failures in arrow-utility-test's failures will be fixed.
[  FAILED  ] Rle.SpecificSequences
[  FAILED  ] Rle.TestValues
[  FAILED  ] BitRle.Flush
[  FAILED  ] BitRle.Random
[  FAILED  ] BitRle.RepeatedPattern
[  FAILED  ] BitRle.Overflow
[  FAILED  ] RleDecoder.GetBatchSpaced

This failure may not be related to this PR.

Thank you very much @kiszk !


Create IG Route: /domestic-scheduled-payments/{DomesticScheduledPaymentId}

Description
A PISP can retrieve the domestic-scheduled-payment to check its status.
Issues related

https://github.com/SecureBankingAccessToolkit/SecureBankingAccessToolkit/issues/114

Route Specifications

read/write API: Payment initiation
Specification link: GET /domestic-scheduled-payments/{DomesticScheduledPaymentId} v3.1.8
Endpoint: /domestic-scheduled-payments
Method: GET
API version spec: Domestic Scheduled Payment v3.1.8
API uri: /rs/open-banking/v3.1.*/pisp/domestic-scheduled-payments/{DomesticScheduledPaymentId}

Acceptance criteria

[ ] Functional tests passed in nightly environment
[ ] Functional tests passed in dev environment
[ ] Proper response expected by the spec
[ ] Errors expected match with the OBIE specs
[ ] Route documented

[ ] Route source commented
[ ] Add the route documentation to the wiki route section

We will use new subtask in an Epic.


"No tasks found" option for when your filter matches nothing

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.
[X] I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
[X] I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description
Essentially allow a flag to return a custom string if no tasks were found per the filters provided
✔ Solution
Maybe a new keyword like "not found message"
❓ Alternatives
No response
📝 Additional Context
No response

Hi, thanks for using Tasks.
What real-world problem is this solving?
Currently if there are no found tasks, the display is:
0 tasks

Which seems pretty clear to me.

I actually disable that because its not the prettiest.
This is my dataview filter
not done
due before today
hide postpone button
hide edit button
hide due date
hide backlink
hide task count

I'd like it to read "No tasks due" instead of "0 tasks"
I know its pretty nitpicky, but I imagine others are as particular as me about this too.

Difficulty

It could read "No tasks due later this week"

It could, but Tasks searches are very flexible, and there are often multiple filters in one query - not to mention filter by function.
So it's not feasible for Tasks to come up with a general interpretation of all queries.

I know its pretty nitpicky, but I imagine others are as particular as me about this too.

It is nitpicky, and it's asking volunteers to spend time writing, testing and documenting something which is purely cosmetic.
Alterative option
There is this existing request, which would allow you write a custom description for your task count.

https://github.com/obsidian-tasks-group/obsidian-tasks/issues/2380

Hi @acrylicus, just to follow up on this.
The fact that two different people have suggested different wording for the 0 tasks is useful info - and confirms that value of making it customisable. And we only need one ticket to track that.
So I'm closing this in favour of #2380. I suggest you subscribe to that and up-vote it - with 👍 .
In the meantime, if you want a count of the number of tasks, you can always use the existing show task count.
And you can search for Styling in the docs to use CSS to change the  appearance of the current task count, if you wish.


no-named-as-default with React, Redux

Hi, I've got an error when linting my App.js file.
error  Using exported name 'AreasSection' as identifier for default export           import/no-named-as-default

App.js
import AreasSection from './AreasSection';
/* code */

AreasSection.js
import React, { Component, PropTypes } from 'react';
import { connect } from 'react-redux';

class AreasSection extends Component {
    /* code */
}

export { AreasSection };
export default connect(mapStateToProps)(AreasSection);

I use default for real usage and named exports for testing. Is this because the component is wrapped with connect?

This is a precedented confusion with no-named-as-default (see #468).
TL;DR: this common pattern and no-named-as-default cannot coexist. It's just a warning to identify a possible error, and in this case, it can't do its job, unless you rename the named, undecorated export to something else, like
export { AreasSection as Pure }

which, again, is a diversion from this common (and totally fine) Redux component pattern, and thus may be worse than just disabling this rule.

Unfortunately, React + Redux is the most common scenario. However, there are lots of other cases where HOCs will force developers to shut down this rule.

I developed a strategy like naming my component as 'Component' and exported it via export default connect(mapStateToProps, mapDispatchToProps)(Component);. Simple, yet it works and there's no confusion.

@mehmetnyarar and what do you do if you want to export the Component for testing without connect() ?

@mariustop you don't want that. If it's never used in production without connect, there's no value in testing it without connect. Use .dive() instead.

@ljharb It is terrible to suggest that your components should be tested with your stores attached. Anytime your store changes the component test will break even in non related changes. I think there is a use case for this rule but in no way should it determine your testing strategy.

I highly disagree; I think it's terrible to test your store-connected components in conditions that they'll never exist in in production, namely, without the store.

We can agree to disagree. But I find value in testing components as they will be rendered by the browser using snapshots. That being said, testing the state machine to fetch, process and deliver props to the component in their expected structure is just as important. However, coupling the two inside of a single test, from my experience, only leads to a more complex and fragile test.


LOC: request device configuration and publish metrics/info

This work introduces two LOC related things if LOC configuration exists (LOC URL is set by a controller):

Device configuration can be fetched from another source, aka LOC, if main controller is unreachable or returns an error.

/info and /metrics are published to the LOC URL along with publishing to a controller. The main difference is that /info is made recurring for the LOC case, because LOC is supposed to be stateless so all /info structures are published without any sending error handling.

Most of the commits are API changes to support different destinations for publishing requests: controller, loc, local server.

cca1885 handleconfig: handle 'CertInvalid' and 'CertMiss' similar in the getLatestConfig()
Do we really handle 'CertMiss' and 'CertInvalid' differently? I unify the logic.

They are different things; CertMiss is about the controller (signing) certificate, and CertInvalid is about the TLS certificate chain. We should probably add that information in the comments for the enums to make this more clear.

Difference to the previous version:

Unite two LOC related works in one PR: fetch config, publish /info, /metrics
Remove config refactoring commits as not very much helpful

cca1885 handleconfig: handle 'CertInvalid' and 'CertMiss' similar in the getLatestConfig()
Do we really handle 'CertMiss' and 'CertInvalid' differently? I unify the logic.

They are different things; CertMiss is about the controller (signing) certificate, and CertInvalid is about the TLS certificate chain. We should probably add that information in the comments for the enums to make this more clear.

Commit is removed.

Dco is saying some commit is not signed

Differences to the previous version:

Refactor deferred logic by creating another deferred context for all recurring (periodic) requests. The periodic deferred queue is handled separately from another goroutine in order not to block the main event loop and not to interfere with /attest requests. Also all requests to the periodic deferred queue ignore all errors.
Changes based on Milan and Erik comments: function renames, type renames, comments tweaks, private structure members, etc

It seems that dev_local_info.txt is failing, which is an eden test related to LPS and could have been broken by this PR, hence worth investigating.

Difference to previous version:

A couple of fixes for the LOC case
Yetus fixes, comments tweaks, code tweaks
Added global rename of LocalProfileServer,LocalServer,LocalProfile,etc,etc to lps or LPS. @milan-zededa last 7 commits worth to review, hope this was the intention. The changes are rather mechanical with some obvious reverts in protocol/API files, so some of the LocalProfileServer are still there in the code

Looks like yetus is tripping on:
yetus: pkg/pillar/cmd/zedagent/handlelps.go#L118golangcilint: getconfigCtx.localServerMap undefined (type *getconfigContext has no field or method localServerMap) (typecheck)

Difference to the previous version:

Rebased on master
Removed all commits related to the renaming of the LocalServer to LPS etc. I do not feel comfortable to commit these changes in this PR.

I'll kick off another run, but @rouming can you figure out why TestEdenScripts/port_forward fails 2/2 times in https://github.com/lf-edge/eve/actions/runs/4376395843/jobs/7658444261 and the eden tests run out of time?

I'll kick off another run, but @rouming can you figure out why TestEdenScripts/port_forward fails 2/2 times in https://github.com/lf-edge/eve/actions/runs/4376395843/jobs/7658444261 and the eden tests run out of time?

Can try

I'll kick off another run, but @rouming can you figure out why TestEdenScripts/port_forward fails 2/2 times in https://github.com/lf-edge/eve/actions/runs/4376395843/jobs/7658444261 and the eden tests run out of time?

Can try

@eriknordmark Port forwarding does not work. As far as I can tell all nat iptables rules exist (2223->22), but indeed you can't ssh to the app using eve ip addr: $ ssh <IP_ADDRESS> -p2223, but directly app-vm accepts the connection: $ ssh <IP_ADDRESS>, I will try to debug further.
These eden tests successfully passed on this PR on my local machine:
./eden test tests/eclient -e profile -v debug
./eden test tests/eclient -e radio_silence -v debug
./eden test tests/eclient -e dev_local_info -v debug
so I'm about to rebase and merge this PR.


Update transparent-data-encryption-tde-overview.md

as per PG team, certificates are rotated once in a year

@GithubMirek
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

PG confirmed.
#sign-off