Community License RuntimeError

Hello. With some models I get a Runtime Error when attempting to .exportGurobiModel() an amplpy.AMPL object into the ampls-api for use with a community licensed environment. However, when I run the same example in a fully licensed environment it works fine.
It is also worth mentioning that it is not all models that have this behavior, running the same examples will always error in the community licensed environment but running some other models will always work just fine.
Additionally, if I stay within amplpy and use amplpy.AMPL.solve() without exporting to gurobi model it works just fine...
Not sure what's going on here. I have attached a python script that will always error in my community licensed environment and will never error in my full licensed environment.
recreateAmplpyGurobiRuntimeError.py.txt

Let me know if this issue should go in the amplpy repo (https://github.com/ampl/amplpy) instead and I can close this issue and copy it over there.

Thanks for reporting this issue and for providing a reproducible example. We have just released amplpy-gurobi/ampl-cplex/amplpy-xpress v0.1 and this issue has been addressed (we changed the license validation procedure):
$ python -m pip install amplpy_gurobi==0.1 --upgrade
$ python recreateAmplpyGurobiRuntimeError.py
Gurobi 10.0.1: optimal solution; objective 25
2 simplex iterations
Objective Value = 25.0
amplpy solve with 10 variables complete
Gurobi 10.0.1: optimal solution; objective 2550
0 simplex iterations
Objective Value = 2550.0
amplpy solve with 101 variables complete
Gurobi 10.0.1: optimal solution; objective 25
2 simplex iterations

Gurobi 10.0.1: optimal solution; objective 25
2 simplex iterations
Objective Value = 25.0
amplpy_gurobi solve with 10 variables complete
Gurobi 10.0.1: optimal solution; objective 2550
0 simplex iterations

Gurobi 10.0.1: optimal solution; objective 2550
0 simplex iterations
Objective Value = 2550.0
amplpy_gurobi solve with 101 variables complete

Please let us know if the problem persists or if any new issue arrises. This was a major update but we tried to keep backward compatibility with the previous version.


support for CC

Can we add a test for CC similarly to TO?

cc: doesn't exist in Gmail's Filter resource, so the way to do this today is with has: "cc:whatever". However, I'll leave this issue open for a bit, because it should be easy enough to add support for Gmail's custom search operators to declutter your configuration file.


Support for ARM/Raspberry pi

Arm architectures do not have the dmidecode command.  On the Raspberry pi the serial can be obtained with cat /proc/cpuinfo | grep Serial

Looks good, thanks!


HDDS-5242. Skip failing acceptance suite by default

What changes were proposed in this pull request?
Acceptance tests are split into a few suites, which can be activated by setting OZONE_ACCEPTANCE_SUITE.  CI checks execute 3 splits for faster feedback:

secure
unsecure
misc + anything without suite

There are some other tests, tagged suite:failing, which exist only to test the behavior of the acceptance test runner when failures happen.
The goal of this change is to skip the failing suite by default, i.e. when acceptance tests are run without suite filter.  This would allow running all tests in sequence (e.g. in nightly job) while retaining the ability to run these special tests by setting OZONE_ACCEPTANCE_SUITE=failing.
https://issues.apache.org/jira/browse/HDDS-5242
How was this patch tested?

Added bats test case.
Ran test-all.sh with a small tweak to exit after finding tests.  The output does not include failing1 or failing2:compatibility/test.sh ozone-csi/test.sh ozone-ha/test.sh ozone-mr/test.sh ozone-topology/test.sh ozone/test.sh ozones3-haproxy/test.sh ozonescripts/test.sh ozonesecure-ha/test.sh ozonesecure-mr/test.sh ozonesecure/test.sh restart/test.sh upgrade/test.sh xcompat/test.sh

while on master it does:compatibility/test.sh failing1/test.sh failing2/test.sh ozone-csi/test.sh ozone-ha/test.sh ozone-mr/test.sh ozone-topology/test.sh ozone/test.sh ozones3-haproxy/test.sh ozonescripts/test.sh ozonesecure-ha/test.sh ozonesecure-mr/test.sh ozonesecure/test.sh restart/test.sh upgrade/test.sh xcompat/test.sh

https://github.com/adoroszlai/hadoop-ozone/runs/2613248841?check_suite_focus=true#step:4:27
https://github.com/adoroszlai/hadoop-ozone/actions/runs/853780974

Thanks @elek for reviewing and committing it.


[Bug]: FileReadObservation.init() got an unexpected keyword argument 'impl_source'

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
https://www.all-hands.dev/share?share_id=89cc5c6565e8372271be4bb803ec6eff0cee8201800be7514a63500edda88490
OpenHands Installation
Docker command in README
OpenHands Version
0.16.1
Operating System
WSL on Windows
Logs, Errors, Screenshots, and Additional Context
No response

+1 on this (Workflow log)

It seems like this particular issue was solved with the bot's update

Reopening this issue, still facing the issue on main
Sample workflow log

OpenHands started fixing the issue! You can monitor the progress here.

An attempt was made to automatically fix this issue, but it was unsuccessful. A branch named 'openhands-fix-issue-5741' has been created with the attempted changes. You can view the branch here. Manual intervention may be required.

To note, this looks like a version conflict:

this was merged after 0.16.1 release https://github.com/All-Hands-AI/OpenHands/pull/5508

it does indeed introduce two new attributes, which don't exist in the 0.16.1 version of the event

the workflow uses the 0.16.1 version

Ah gotcha, how about this workflow log? It's using main

It looks like this is not main, it's 0.16.1... 🤔

I mean line 139 there

Ah I see the confusion - the previous step in the workflow checks for the latest version

However for the step that installs the package, I forced it to install from main

When I use the released version 0.16.1, this issue doesn't occur (another workflow log
)
It seems like this is an issue only on main

Hmm, how about the sandbox? This code above is running in the sandbox 🤔

I believe the resolver runs on eventstream instead of sandbox runtime; am I interpreting this correctly?

The "eventstream runtime" is a docker sandbox, which communicates using an API sending/receiving events from the sandbox. It's not local, it's in docker.

EDIT: we can confirm this by running fix-me vs fix-me-experimental on an issue; I believe fix-me-experimental will fail

I ran fix-me-experimental here last night, it worked. The difference might be that your test repo is an external repo, while the successful workflow worked on this repo?

OpenHands started fixing the issue! You can monitor the progress here.

Possibly! Did a quick test, was able to reproduce the error again on this repo; there may be a PR that caused a regression in the last day or so

Oh, it failed with the same error!
I saw this: https://github.com/All-Hands-AI/OpenHands/actions/runs/12455745077/job/34768492590#step:10:37

I think the issue is due to the resolver used a specified runtime image, which skips the runtime image build process:
https://github.com/All-Hands-AI/OpenHands/blob/4a8bf3d2d0b3a032b16962b62f2cce65c4fe1850/openhands/resolver/resolve_issue.py#L593-L596
One way to address might be to not specify this runtime image at all, similar to the dev workflow, which can add some build time overhead to the resolver, but can keep it up to date with all the changes in main. What do you guys think?

+1
I'll revert to the last known stable commit as i'm just getting familiar with the project :)

I think the issue is due to the resolver using a specified runtime image, which skipped the runtime image build process:
https://github.com/All-Hands-AI/OpenHands/blob/4a8bf3d2d0b3a032b16962b62f2cce65c4fe1850/openhands/resolver/resolve_issue.py#L593-L596
One way to address might be to not specify this runtime image at all, similar to the dev workflow, which can add some build time overhead to the resolver, but can keep it up to date with all the changes in main. What do you guys think?

Aha, that was the code. I agree! I think we should fix it as you suggest: let it build the runtime it needs.
Because we now use main in our fairly regularly used workflow, and also, importantly, other repos also build on top of our main workflow. Conflicts like this between the sandbox image and main can be pretty bad and they're almost blocking for external workflows.
Please note that this isn't always: this is for fix-me-experimental and equivalent macro (at openhands-agent-exp), which run on main. For the rest, the regular fix-me workflow (and equivalent macro), we can keep the released runtime, so there are no build times concerns there. Those run on the pypi version.

@glgh @gordicaleksa If you encounter this without running the resolver, can you please remove all openhands-related images from docker, and let it re-download?

@enyst Yeah, let me have a closer look and try a PR for that! This is a good opportunity for me to learn more about the resolver! 😅


[EPIC] ROCM HAL Semaphore support

HAL semaphore implementation based on the cuda2 experimental semaphore implementation

Last ctest log (from 2023-10-26)
LastTest.log


How to get sub-items

Hello,
I'm trying to get the sub-items of an isssue, the only thing that is available is SubItemsCount and .WithSubItemsCount(). Is there missing variable in the issue class and function in IssuePartialExtensions ?

Hi @ArthurVasseur! There should also be a WithSubItemsList() that you can use on the issue partial. (in the latest release from yesterday), although I'm not 100% sure it is deployed to the service yet. But that will be the extension you are looking for :-)

The version I have is 1.0.0-beta.v2022.2.0-DEV.107983.9110, and WithSubItemsList it's not available in it.
I suppose I have to wait for the new version

It should be there if you add a using JetBrains.Space.Client.IssuePartialBuilder, can you try?

I reinstalled the package it seems to have worked !
Thanks for your help :)

I have another problem
Here's my code :
await foreach (var issue in project.Planning.Issues.GetAllIssuesAsyncEnumerable(
                   ProjectIdentifier.Key(_projectName), IssuesSorting.UPDATED, true,
                   tags: _tags,
                   partial: _ => _
                       .WithAllFieldsWildcard()
                       .WithCreationTime()
                       .WithDescription()
                       .WithStatus()
                       .WithSprints()
                       .WithCustomFields()
                       .WithChannel()
                       .WithSubItemsCount()
                       .WithSubItemsList(subItem => subItem.WithName().WithDescription().WithRoot())
                       .WithTags(tag => tag.WithName().WithId())
                       .WithAssignee(assignee => assignee.WithName())
               ))
{
    _issues.Add(issue);
}

If I want to access to the member SubItemsList I've got an exception : JetBrains.Space.Common.PropertyNotRequestedException: The property SubItemsList was not requested in the partial builder for Issue. Use .WithSubItemsList() to include it. Expected full path: Batch1->WithData().WithSubItemsList() at JetBrains.Space.Co…
But I have already call WithSubItemList(...)

This may be caused by the subitemslist field not yet being exposed by the API. Just checked on my own organization, and it's not yet deployed to Space. Can you check if this is also the case on your organization?
https://<org>.jetbrains.space/extensions/httpApiPlayground?resource=projects_xxx_planning_issues&endpoint=rest_query

Same for me

I'll keep an eye on it and let you now when it goes live 👍

Okey thanks !

It just appeared on my organization 👍

Yup, I have it too ! Thanks


fixed minor typo

Fixed a minor typo as I was working through the tutorial.  Putting my skills to use immediately!
Thanks for creating the workshop -- it has been very helpful!

Yay! Thanks so much for this! It seems no matter how many times I read this over, I still miss things. :sparkles:


updated my profile

Please see suggestions above

Please check in out I have correct that one

:) Thanks for adding your profile to LinkFree!
We'll remove the package-lock.json file, while merging this in a staging branch

@Vyvy-vi it would be nice if you could format the file as well, before it is merged into main


HDDS-6354. EC: Fix allocateBlockIfFull condition in ECKeyOutputStream#write()

What changes were proposed in this pull request?
remLen > 0 will always be true if this while loop ever gets entered.
I think it's intended to be lastCellSize > 0.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6354
How was this patch tested?
N/A

This patch won't be needed if HDDS-6358(#3120) gets merged.

Thanks @kaijchen for reporting and @guihecheng for the initial review.
Here is my suggestion: Let's review the refactor JIRA first as that will supersede this issue anyway.


How to check the detail of status of container instance after creating

Query/Question
Recently I found many container instances were not accessible after creating it.  It last for 30min and than we stop the task
However , we have no idea what's going on? How can I get the container instance status ( or event, or debug information) for it?
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-get-logs#get-diagnostic-events
the docs says cli az container show --resource-group myResourceGroup --name mycontainer can query the events, how can I do that in .NET sdk?
Environment:

Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0]
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8]
IDE and version : [e.g. Visual Studio 16.3]

To view container logs, you have to use the storage management plane SDK instead
https://www.nuget.org/packages/Microsoft.Azure.Management.ContainerInstance/
I will relabel this issue with Mgmt, so it gets routed and gets the proper attention. Please relabel with client and storage if this is a Azure.Storage.Blobs issue.

no need, already done

can someone elaborate on this one? The list of Events on an instance of ContainerGroupImpl queried by fluent Management SDK is empty.
I cant find any documentation on how to get events from a ContainerGroup


Update the dds stats command to get the rows from Statistics endpoint

Before submitting this PR

Description: The current method of stats was to calculate number of projects etc every time the command dds stats was run. Now, there's a new endpoint which gets the statistics from the reporting table and returns all rows. This PR updates the dds stats command to return those rows and print them as tables.
Jira task / GitHub issue: DDS-1575
How to test: Add information on how someone could manually test this functionality. As detailed as possible.
Type of change: Check the relevant boxes in the section below
Add docstrings and comments to code, even if you personally think it's obvious.

What type of change(s) does the PR contain?

[x] New feature

[ ] Breaking: Please describe the reason for the break and how we can fix it.
[x] Non-breaking

[ ] Bug fix

[ ] Breaking: Please describe the reason for the break and how we can fix it.
[ ] Non-breaking

[ ] Security Alert fix
[ ] Documentation
[ ] Tests (only)
[ ] Workflow

Checklist

Sprintlog

[x] Added
[ ] Not needed (E.g. PR contains only tests)

Rebase / Update / Merge from base branch (the branch from which the current is forked)

[ ] Done
[ ] Not needed

Blocking PRs

[ ] Merged
[x] No blocking PRs

PR to master branch

[ ] Yes: Read the release instructions

[ ] I have followed steps 1-7.

[x] No

Actions / Scans

Black: Python code formatter. Does not execute. Only tests.
Run black . locally to execute formatting.

[ ] Passed

Pylint: Python code linter. Does not execute. Only tests.
Fix code producing warnings. Code must get 10/10.

[ ] Warnings fixed
[ ] Passed

Prettier: General code formatter. Our use case: MD and yaml mainly.
Run npx prettier --write . locally to execute formatting.

[ ] Passed

Yamllint: Linting of yaml files.

[ ] Passed

Tests: Pytest to verify that functionality works as expected.

[ ] New tests added
[ ] No new tests
[ ] Passed

TestPyPi: Build CLI and publish to TestPyPi in order to verify before release.

[ ] Passed

CodeQL: Scan for security vulnerabilities, bugs, errors

[ ] New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
[ ] Alerts fixed: What?
[ ] Alerts ignored / dismissed: Why?
[ ] Passed

Trivy: Security scanner

[ ] New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
[ ] Alerts fixed: What?
[ ] Alerts ignored / dismissed: Why?
[ ] Passed

Snyk: Security scanner

[ ] New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
[ ] Alerts fixed: What?
[ ] Alerts ignored / dismissed: Why?
[ ] Passed

Tests and fixes of the failed checks needed


weave stop explodes on docker <1.9

I am running docker 1.8.3...
$ weave launch
$ weave stop
FATA: 2015/12/22 12:04:20.337536 unable to connect to docker: API error (400): client is newer than server (client API version: 1.21, server API version: 1.20)

Duplicate of #1815


Allow whitespace in prerelease command

Fixes a bug where the prerelease command didn't work it the user accidentally added any whitespace characters.

/prerelease


Fix for issue #61, #62 and #63

Fix for issue #62: Using 'data-checklist-model' instead of 'checklist-model' results in stack overflow exception
Fix for issue #61 Use value if checklist-value is not present
Fix for issue #63 package.json also defines 'main' now.
Plunkr for current version to illustrate issues: http://plnkr.co/DFXIfT
Plunkr with fixes: http://plnkr.co/dJP23c

Any info about when this would be merged into master?

Merged


remove weird characters from README.rst

There's no reason to remove these. What are you trying to achieve here?

What are they? And what are they for? They are not displayed well in my computer.
From Readme in GitHub

From pip

They are emoji. They're pictograms that have been assigned Unicode glyphs. If your computer cannot render them you can either elect to resolve that by installing an emoji font, or you can simply ignore them: you aren't losing out on any critical data. The picture you can't see, for the record, is a slice of cake.

The cake is a lie.


Move Docs to Next.js App

Rationale
Migrates the Playbook docs into a Next.js & MDX application. This is a part of my effort to standardize our processes, to make it easier for our mentors to start projects and to make it easier for our members to make contributions.
Screenshots:
GIF

Test Deployment
I've deployed this on my own Vercel account just to able to preview this. Let me know if you are happy to accept, and I will take my deployment down.
https://code-sydney-playbook.vercel.app/
Issue Resolved

Fixes #13

I just noticed that the original preview image hasn't been changed.
I'll make a quick change to this PR.

Thanks @davidtaing for these updates. Honestly, I have yet to check it. 😅


Add new branch patch/content/custom-info

Add new branch patch/content/custom-info and fill in resume with my details.

Done.


🏷 Update GraphQL Schema with Custom Vote

Fixes #472.
Changes proposed in this pull request:

Update GraphQL schema to include CustomVote type

Not sure what this PR is for, the issue miss context but the idea is to make it possible to cast a vote with a custom choice that is not defined yet in the proposal. If you want to do this festure you should first make specs for it.

If you want to do this festure you should first make specs for it.

@bonustrack Could you point me to any other past PRs or other resources for guidance? I've never written a spec before :D

Closing this as stale


Include mnesia_rocksdb version with fix for backup

Finishes https://www.pivotaltracker.com/story/show/155748313
TODO:

[x] Get https://github.com/aeternity/mnesia_rocksdb/pull/5 merged first
[x] Update rebar.config/lock to merged https://github.com/aeternity/mnesia_rocksdb/pull/5
[x] Check that actually mnesia:backup works

I see CI (that includes a couple of test suites using DB) passed.
I checked that backup/restore works:

I started node configured with persisted DB and automining true;
At height 1, I called ok = mnesia:backup("/tmp/mnesia.bak").
I checked node managed to mine further;
I stopped node;
I deleted DB;
I started node configured with persisted DB but with automining false and without peers;

Idea was to start node for restoring DB without allowing DB to be used at the same time. I attempted to use bin/epoch console_clean with flag -pa for OTP patches and -pz for Mnesia ebin, though did not manage to get mnesia module loaded probably because embedded release and not in .boot.

I restored DB:

(epoch@localhost)1> {atomic, [_|_] = Tabs} = mnesia:restore("/tmp/mnesia.bak", []).
{atomic,[aec_tx,aec_chain_state,aec_blocks,
               aec_account_state,aec_contract_state,aec_block_state,
               aec_oracle_cache,aec_oracle_state,aec_name_service_state,
               aec_name_service_cache,aec_headers]}

I checked chain was at same block height 1 (aec_chain:top_block_with_state().);
I stopped node;
I started node configured with persisted DB and automining true;
I quickly checked chain was at same block height 1 (aec_chain:top_block_with_state().);
I checked node managed to mine further.

I checked that backup/restore works:

@lucafavatella is this the procedure you want to be documented ? I mean the general steps:

disable mining and peers
start the node
restore
stop the node
enable mining and peers
start the node

@lucafavatella is this the procedure you want to be documented ? I mean the general steps:

@dincho Yes. I though of writing an automated test for this though it would have taken more time and this functionality is more Dev related than for running node.

@dincho Yes. I thought of writing an automated test for this though it would have taken more time and this functionality is more Dev related than for running node.

I agree, few lines of docs should do.

I see CI failure https://circleci.com/gh/lucafavatella/epoch/1085 , I am investigating whether related to this PR.
I suspect https://github.com/aeternity/epoch/blob/9ad96ce5/apps/aecore/src/aec_sync.erl#L474 , combined with lack of atomicity of writing block to DB and writing chain state (e.g. top block hash) to DB, to cause one of at least two concurrent syncs of same peer (potentially even same chain from distinct peers) to declare itself as done (client_done) without conductor having necessarily updated top block (aec_chain:top_block/0).
I have not yet proven it though, so it may still be a lack of guarantee of read-after-Mnesia-transaction-write in Mnesia backend.

I have not yet proven it though, so it may still be a lack of guarantee of read-after-Mnesia-transaction-write in Mnesia backend.

I now performed further analysis and I have no reason for suspecting guarantees of Mnesia backend. This PR is now open for review.


davix: 0.8.6 -> 0.8.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/davix/versions.
meta.description for davix is: Toolkit for Http-based file management
meta.homepage for davix is: https://github.com/cern-fts/davix
meta.changelog for davix is: https://github.com/cern-fts/davix/blob/R_0_8_7/RELEASE-NOTES.md
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.7 with grep in /nix/store/vpfxc8dv04fjshmfwqgzrd8p4kix7y02-davix-0.8.7
found 0.8.7 in filename of file in /nix/store/vpfxc8dv04fjshmfwqgzrd8p4kix7y02-davix-0.8.7

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

25 total rebuild path(s)

25 package rebuild(s)

First fifty rebuilds by attrpath

davix
davix-copy
gfal2
gfal2-util
hepmc3
ns-3
python311Packages.coffea
python311Packages.fsspec-xrootd
python311Packages.gfal2-python
python311Packages.gfal2-util
python311Packages.hepmc3
python311Packages.snakemake-storage-plugin-xrootd
python311Packages.xrootd
python312Packages.coffea
python312Packages.fsspec-xrootd
python312Packages.gfal2-python
python312Packages.gfal2-util
python312Packages.hepmc3
python312Packages.snakemake-storage-plugin-xrootd
python312Packages.xrootd
root
xfitter
xrootd
yoda-with-root

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vpfxc8dv04fjshmfwqgzrd8p4kix7y02-davix-0.8.7 \
  --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 davix https://github.com/r-ryantm/nixpkgs/archive/2dd083632866ca1a2fe86d2347e38a99edca064d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2dd083632866ca1a2fe86d2347e38a99edca064d#davix

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vpfxc8dv04fjshmfwqgzrd8p4kix7y02-davix-0.8.7
ls -la /nix/store/vpfxc8dv04fjshmfwqgzrd8p4kix7y02-davix-0.8.7/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.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @adevress for testing.

Result of nixpkgs-review pr 323625 run on x86_64-linux 1

4 packages marked as broken and skipped:

python312Packages.gfal2-python
python312Packages.gfal2-python.dist
python312Packages.gfal2-util
python312Packages.gfal2-util.dist

36 packages built:

davix
davix-copy
gfal2
gfal2-util (python311Packages.gfal2-util)
gfal2-util.dist (python311Packages.gfal2-util.dist)
hepmc3
ns-3
python311Packages.coffea
python311Packages.coffea.dist
python311Packages.fsspec-xrootd
python311Packages.fsspec-xrootd.dist
python311Packages.gfal2-python
python311Packages.gfal2-python.dist
python311Packages.hepmc3
python311Packages.snakemake-storage-plugin-xrootd
python311Packages.snakemake-storage-plugin-xrootd.dist
python311Packages.xrootd
python311Packages.xrootd.dist
python312Packages.coffea
python312Packages.coffea.dist
python312Packages.fsspec-xrootd
python312Packages.fsspec-xrootd.dist
python312Packages.hepmc3
python312Packages.snakemake-storage-plugin-xrootd
python312Packages.snakemake-storage-plugin-xrootd.dist
python312Packages.xrootd
python312Packages.xrootd.dist
root
root.debug
xfitter
xrootd
xrootd.bin
xrootd.dev
xrootd.etc
xrootd.man
yoda-with-root


Added white background to faq questions

Increased readability of FAQ questions
Added in contributors list

Nice :) ⬜

Thanks! 😊


Update README.md

Proposed Changes
I had to remove the client name in order to make it working.

The service name is official optional but is definitely part of the configuration.
For more information see the Tor manual:
https://www.torproject.org/docs/tor-manual.html.en


Update BaseArrayHelper.php

Why not, it usefully.

please read the lines next to it
https://github.com/yiisoft/yii2/pull/13151/files#diff-c5ab028029554c59da3b92c6a49d8ac6R207


zc.ticket447.helpful-missing-param-error-messages.0

ref: https://github.com/Electric-Coin-Company/zerocashd/issues/447

LGTM

@ebfull in b4 review-needed. ;-)
I noticed the on the waterfall the build for this PR branch fails the zerocashTest build step fails with this stdio log. That shows that MerkleTreeSimpleTest fails.
I verified the same test is failing in builds for previous branches such as build #77 for zc.latest.0.ticket378.consistent-zksnark-parameters.0.
So I think that failure should not block this PR and instead we should have a separate ticket to fix that failing test.


README updates

Derived from PR #19

Commits a8cb719 and 9ee6910 are not signed off, but approved on my end.

Made a host of updates -- I broke the formatting out into actual sections, as the list formatting was getting really busy.

LGTM


Adding multilines, imports, and a shows command line option that allows for entering partial hosts

Treats additional lines as "notes" that are simply a separate array of values.
The editing action is a bit more complex due to needing to re-encrypt existing notes.  When notes exist, a prompt for the master password is required.  A multiline edit allows the user to remove existing notes as well as add notes whereas a typical edit assumes retention.

We aren't going to do this. You can insert files, so I recommend doing that.


Sdk 305 ruby type hinting

closes #306
closes #305

https://github.com/coinbase/protoc-gen-rbi/pull/33 <- trying to get my tool merged.


No v1.3 (trial) JAR

FYI, there is no .jar file in your v1.3 (trial) release. So, our scripts will smoke-tests the latest available JAR file (if any).

Thank you Prof! @damithc


Pathfinder 0.16

0.15 and 0.16: skill page, acp and maxdex fix, buff total dmg fix, css divider cleanup,touch, cmd, check, class  buffs, vision

this is ready


[WIP] Use facterdb as main source of facts

This PR is open only to start discuss about using facts in onceover. I will add another commits when we agree how this feature should look like.
Now all facts are delivered by json files which are in factsets folder or could be given in command line (--facts_dir, --facts_files). Facts are close connected with node name.
New way of deliver would be very similar, facts will be delivered by facterdb and connected with node name, this will be base. Additional system will replace (by default) or extend/merge facts from json files. So in replace mode system should behave same as before.
@dylanratcliffe Any thoughts?

@mandos are you planning on using rspec-puppet-facts?

Also note that when using FacterDB a user can supply custom external facts as well.
https://github.com/mcanevet/rspec-puppet-facts#suppling-custom-external-facts-through-facterdb

Hey I'm going to close this as I'm cleaning up some old PRs and issues, if you'd like to continue work on this though feel free to reopen!


How to set "Content-Type" header to "application/octet-stream"

Hello,
First of all thanks for such helpful library 👍
Using: Moya (13.0.0)
My server side guy wants the header "Content-Type" set to "application/octet-stream" when uploading files. Before i was using "multipart/form-data".
I could not find a way to set this header. Would you please guide me for the best way to set this header.
Best Regards
PS: I tried setting it with custom headers but as far as i see Moya or Alamofire overwrites this header

Hey @metisdev. AFAIK Alamofire is updating the multipart's Content-Type header just before executing the request so you can't really change the multipart/form-data into application/octet-stream while doing multipart upload.
If you can upload the file without using a multipart request, you can use pure Task.upload() case and set the header in your TargetType - then it shouldn't be overwritten.


contactform module continues to not send email

Hi
the function sendMessage inside of contactform.php does not work of version 4.1.1, in many sites
the past version 3.0 works
why do you continue to use this version?
to solve this problem I need to use the past version
thanks

I don't get any errors, but the confirm message, but any emails arrive
replacing that function all is ok

Hi @maofree, I have tested the module and everything is ok. Perhaps you have a wrong configuration in your email settings.
Go to you backoffice -> Advanced Parameters -> Email address and scroll down until the "TEST CONFIGURATION E-MAIL", click on the button "Send a test email".

Be sure that your setting is similar to:

hi
all is ok, it is necessary to set the second option on true on the contactform module to get emails
bye


argocd: 1.8.5 -> 1.8.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/argoproj/argo-cd/releases.
meta.description for argocd is: "Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes"
meta.homepage for argocd is: "https://github.com/argoproj/argo"
meta.changelog for argocd is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

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.8.6 with grep in /nix/store/kmhvd9vf1bfbp5ymzsnb4smw6ls73lsa-argocd-1.8.6

directory tree listing: https://gist.github.com/0c74b6fbe4b367bf9474459b6d104f22

du listing: https://gist.github.com/68e27b1099bbd62658867ec8fde1a2a1

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
argocd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kmhvd9vf1bfbp5ymzsnb4smw6ls73lsa-argocd-1.8.6 \
  --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 argocd https://github.com/r-ryantm/nixpkgs/archive/f361a1a90250f8c020032bf0fda1f9ddcfc500d8.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/kmhvd9vf1bfbp5ymzsnb4smw6ls73lsa-argocd-1.8.6
ls -la /nix/store/kmhvd9vf1bfbp5ymzsnb4smw6ls73lsa-argocd-1.8.6/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

1 package built:

argocd

Maintainer pings
cc @shahrukh330 @kalbasit for testing.

Result of nixpkgs-review pr 114621 run on x86_64-linux 1

1 package built:

argocd


Verbose test run

the multinode-HA failed at the last step (starting content nodes)
presumably OOM, lets see if verbose is useful

If it really is memory that is the problem, we are already using the max available resources. It is possible to work around by running only one config server in the auto testing, this will test 90% of the guide. We will see
... or @hmusum

Getting there :success


Remove version: Prog.ProgDVB.Professional version 7.60.4

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://files.progdvb.com/progdvb/ProgDVB7.60.4Pro.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 911)


About grid feature

Hi, I've reading your paper, impressive work!
I've been wondering how the grid tokens work, I guess it is used to compensate the inaccurate point estimation? Have you guys done any ablation study about grid tokens and maybe can give some data when PointHMR is without grid token?

I'm sorry. We didn't conduct the ablation study for grid tokens. However, we referred to the idea from MeshGraphormer, and the ablation study for the grid tokens is also provided in the paper. We thought that the grid features play an important role in approximately aligning the mesh structure to the image by preserving the entire image information.

Ok, I might do an ablation experiment myself. Thanks for your reply.

Thank you for your interest!


worldmap: fix invalid description for prifddinas farming patch

This farming patch does not include a herb patch as the tooltip was describing.

Closes #10111

Duplicate of #10114 oops 😄


Add release notes for 6_6_0 Major release

Missed info about fiat:
— Added Fiat value in Operations history for each record


text: Set max size.

This commit sets the max resulting width for a text element. Running all of the Community apps with default config, the max width was 616 pixels.

1000 pixels on a 4 pixel wide font is 250 characters. Additionally, 1000 pixels / 64 pixels is 15, which would mean the entire display would have to be filled with text for 1 sec for ~15 seconds to get all of the text displayed.


[Improvement] Prompt LM to return SQL query in markdown format for easy extraction

Prompt LM to use markdown (```) to indicate code text. Involves editing the few shot examples. Currently, we take text before ';' and after ':' from the LM response to extract the SQL query.

I think you already implemented this? @alex-sun-kuo


[BUG] Bluk Company import via admin page not adding data

In trying to import a dataset (I've tried .xlsx and .csv, using the template columns) for our existing vendors list. When I click submit, the file is uploaded but nothing is populated (No data, no errors). the id field in my dataset is blank but when I add numbers to it I get the same result. I'm running in a development environment so i do not know if this occurs in production.
Steps to reproduce the behavior:

Create .xlsx sheet, columns as directed in company import tab.
Save file on local, go to inventree admin page, under companies click import and upload the file.

Expected behavior
Other imports I have done so far include a small sample of products and locations, both uploaded without issue. I was able to see the data organized and identify any errors before adding to the system.
Deployment Method
Docker on local desktop
Version Information
0.5.0 dev

It's working for me. Try this file (XLSX format):
company_test_import.zip
Maybe one of your fields is incorrect? Can you show a screenshot of the import step before confirmation? (hide sensitive data first)

That worked. I was using a spreadsheet with all of the columns listed below. Not sure why the scaled down list is working but the full list is not. I tried some other variations with the full column list with no luck. I'll use the scaled down version for now and try to figure out what caused the bug.
thanks @eeintech
id, name, description, website, address, phone, email, contact, link, image, notes, is_customer, is_supplier, is_manufacturer, currency

@Matthewmads it would be worth checking the error logs (in the admin interface) to see if an error was recorded:

@SchrodingersGat Error was not recorded in the log related to this one.


Must redraw screen to fix highlighting

Newsboat version: newsboat 2.10.1
Steps to reproduce the issue:

Set highlight article "^Title: .*$" default default bold

Skim through unread articles in article view using next-unread

Watch as Title: Archiving repositories changes to Title: Search repositories by license

This is fixed by redrawing the screen with ^L (i.e., Title: Search repositories by license changes to Title: Search repositories by license

Couldn't reproduce this with STFL 0.22 and
newsboat 2.10.1-r2.10.1
System: Linux 4.9.46 (x86_64)
Compiler: g++ 6.4.0
ncurses: ncurses 6.0.20170902 (compiled with 6.0)
libcurl: libcurl/7.56.1 OpenSSL/1.0.2m zlib/1.2.11 libssh2/1.8.0 nghttp2/1.20.0 (compiled with 7.56.1)
SQLite: 3.21.0 (compiled with 3.21.0)
libxml2: compiled with 2.9.5

Tried both in URXVtc and Tmux 2.6 in URXVtc 9.22.
What terminal, STFL and ncurses do you have?

iTerm2 build 3.1.5, and Terminal.app version 2.8.
Output of brew info libstfl:
libstfl: stable 0.24

Output of newsboat -v:
newsboat 2.10.1
System: Darwin 17.2.0 (x86_64)
Compiler: g++ 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.38)
ncurses: ncurses 5.7.20081102 (compiled with 5.7)
libcurl: libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0 (compiled with 7.54.0)
SQLite: 3.19.3 (compiled with 3.19.3)
libxml2: compiled with 2.9.4

Example with clean config: https://youtu.be/u0UYakQlJyw

I tried again with ncurses 5.9 (the oldest one available from repos) and STFL 0.24 (self-built), and still can't reproduce this.
I asked if anyone on IRC has OS X and can reproduce this, but haven't heard anything yet. Lyse (who's on Linux) tried but couldn't reproduce this either.


Extending Campaign Admin Lock/Unlock

This will extend issue #39 and PR #499.
Thoughts are to add:
Additional column(s) to store a reason why the campaign is being locked, the date it was locked and possibly the username / contact details of the site admin who locked it.
I also thought perhaps we should email the owner of the campaign / org admin to alert them that it has been locked and why?
I also wonder if we need a mechanism for a campaign organizer to mark a campaign as "fixed" to alert an admin that it is now ready for unlocking (issues have been addressed)?
I'll like to pick this up if this is an extension we need for the current milestones?
cc/ @mheggeseth @tonysurma

I'm not sure you necessarily need a way to mark the campaign as "fixed". Maybe just a way for the campaign organizer to send a message to the site admin.

@mheggeseth Sounds reasonable. Based on the above I propose the requirements be:

[ ] Update UI for Campaign Details to make a locked campaign more obvious and a bit cleaner
[ ] Update UI for Campaign Details to include a link to "Read More / Provide Feedback" (wording to be discussed)
[ ] Clicking on the link will display a modal window with details of when and why the campaign was locked.
[ ] Include a send message form under the lock details (single text area and button) for the org admin to type a message and submit it.
[ ] On submit an email will be sent to the site admin who originally locked the campaign to begin a conversation with the org admin as necessary.

Does that all sound reasonable for now? Is so, I will get started on this.

sounds reasonable

@tonysurma Thanks Tony. I'll work on this during the code-a-thon this weekend!

Currently available as I never started this!


Blocks are badly extracted

I'm trying to evaluate A/B Street and LTN for my pro-bike association in Montpellier, France.
When analyzing Montpellier, it seems that the algorithm that extract blocks can create polygonal shapes that have auto-intersections as well as having into one single block, several disconnected cells.
In the following example, the dark blue zone is one single block.

If i'm looking at the whole city, there are several similar problems (another example is that the city center is considered as one block, another problem is a residential district that is part of no block whatsoever).
I've quickly looked at the OSM data but I didn't find any obvious problem that could be the cause.
Are there manual tools to redelimit the different blocks? Or does the extracting only exist as an automatic procedure? How can I help to fix this problem?
Thank you for all the hard work done on A/B street. It's a project i've been following for years... yet i've only started to experiment with it this week :).

Thanks for the infos :

there seems to be a different problem for the small black on the left. How does A/B street map understand that there is some kind of road maintenance there? The OSM nodes don't seem to reflect that. (Note that there are currently some road blocks there).

Have you considered to remove the bridges/tunnels edges from the graph, transforming them into virtual deadends for the blockfinder algorithm? And re-adding them later when blocks are defined? It might be a naive idea you've already explored.

Also, have you also considered iterating on all edges (even non-car edges)? Or is it too costly performance wise? Some blocks, especially near rivers, aren't taken into account ; yet are completly enclosed. Those blocks could then be merged together until some border is a car street.

Finally, do the triangulation always work with simple or weakly simple polygons? Those large triangles overlapping the whole district are a bit distracting and it seems some are produced even with planar blocks (?). But I agree that 90% of them are produced thanks to tunnels/bridges :(

Thanks you @dabreegster ! Feel free to close this issue if you think that it's a duplicated of #857.

How does A/B street map understand that there is some kind of road maintenance there?

Not sure what you mean here -- the light pink road in the screenshot is "private / access only", according to some OSM tags. If you link to the OSM object or view from your second screenshot, I can dig into it.

Have you considered to remove the bridges/tunnels edges from the graph, transforming them into virtual deadends for the blockfinder algorithm?

I've tried something like that, a while ago, just haven't gotten it all working yet. Latest experiment was over in https://github.com/a-b-street/osm2streets/tree/planar_graph_literally, trying to work much more generically to create planar graphs on any type of edge -- regular road segments, also edges of water/park areas.

Finally, do the triangulation always work with simple or weakly simple polygons?

Not sure what you mean. The result is supposed to be a bunch of simple polygons. Most of the time, bridges/tunnels or buggy geometry produced by osm2streets is the cause of non-simple polygons.

I'm having similar issues in Brest, France, so I'd be happy to help discuss/troubleshot it. See the screenshot below for some more examples.

2 and 3 are most likely bridge related, 1 is odd block selection I can't figure out why.

Hi both! Thanks for the patience here. I'm working on a big new version of the LTN tool, and I think the problem with both of these areas is fixed, but I want to be sure. If you go to https://dabreegster.github.io/ltn/, choose your area from the example dropdown, and add a new boundary, you can stretch a polygon over the area(s) you want to analyze. The tool no longer tries to automatically divide everything. If you hit a problem with this, let me know. And if it works decently and your example involves some tricky situation with a bridge, I'd love to use it as a test case. So if you "Save / load project", "Save to GJ", and send the file, I'll set up tests to avoid breaking the area in the future. Thanks!

I just quickly tested: it seems to be better at handling bridges/tunnels. From what I understand, you now use the reconstructed plannar graph to edit neighbours boundaries (and NOT to handle the routing network)?
I'll dig deeper this week. :)
Thanks for all the hard work. I'm still using A/B street to analyze my city and try some proposals. :) Do you have a blog note about your current and future work? I was wondering last weekend if you were still working on the LTN app. I have discovered a few bugs/crash on the old app I could reproduce if you want (sadly, my Rust left is probably too low to correct them myself).

Thanks for testing!

From what I understand, you now use the reconstructed plannar graph to edit neighbours boundaries (and NOT to handle the routing network)?

Exactly. There's no sane way to handle bridges/tunnels otherwise. In the old version, I made too-strong assumptions that the entire perimeter of a neighbourhood is all routable. Some assumptions about forcing the perimeter to be a "main road" were relaxed in #1071. But revisiting things, the only things really needed to calculate shortcuts and cells are interior roads and entrance/exit intersections. Those can both be calculated just by looking at the boundary as a polygon, not using too much of the routing/network properties. It's imperfect in the new version -- sometimes a piece of perimeter road gets marked as interior and has shortcuts shown on it -- but I'm pretty sure those problems can be fixed.

Do you have a blog note about your current and future work?

Not really, the closest thing is https://dabreegster.github.io/prose/dec2023/pt8_tech.html. I've really been meaning to start blogging more frequently, and at least write an updated status for things I'm working on. Will keep you posted if I finish that.

I have discovered a few bugs/crash on the old app I could reproduce if you want

Please do report if it's not too much trouble. The "old" LTN app is still the real usable one, so I'll do my best to maintain it, unless it's things like these boundary problems that're too hard to make work with the old approach. When the newer version has caught up, I'll communicate some kind of migration plan.

Ok, I've toying with the new version for the last hour. It is really impressive :). I think you have the solution. Thank you very much. I would be impossible to work on some parts of Montpellier without that.
Note that there's still the slight issue with the triangulation if the polygon self-intersect but otherwise, it seems to work on the other case I've tried (even weakly simple polygons work !).
Of course this new version of LTN lacks several major features ("one-ways" is probably the most important for me right now) but now, I can't wait for that version to be released :) Also, the UI is a bit sleeker as well, it's kinda pleasant <3
(Just FYI, there's another tool, "Coplano" to create LTN that I discovered on the main french bike-activist board and that was recently demoed . It's developped by @alxbck at https://github.com/alxbck/street-plan and it uses cocarto tables as its input (cocarto is some kind of excel-like sheet tool specifically aimed to create geographic data collaborativly)).
See a (french) presentation here : https://youtu.be/A5OAFJDGRq8?t=3815

@TFCx, some updates. First, I added in one-way support again (it was surprisingly easy the second time around... wish I could say the same for turn restrictions). Second, I started https://github.com/dabreegster/ltn/issues/16 as a dev blog. If there are other big gaps in the new version stopping you from using it, let me know!
And Coplano looks super cool, thanks for sharing!


Centering Nodes and Tooltips is weird when graph gets panned around

When panning around the graph and clicking a node through graph.onClick() the clicked node gets center to where the center was before panning the graph around, it should be centric to the viewport, right?
Also tooltips jitter, when graph was panned around.

We used the following workaround: https://groups.google.com/d/msg/javascript-information-visualization-toolkit/kfEXlKs8rak/D25M-NFUSvEJ
Seems though that the workaround doesn't completely work as wanted when we call chart.addSubtree(subNodes, 'replot') inside the label.onclick = function () {
Another workaround is to reset the canvas by chart.canvas.translate(-chart.canvas.translateOffsetX, -chart.canvas.translateOffsetY);. This worked also in the case of addSubtree. Ain't perfect though as it directly warps to the last centered node (prior to panning) before smoothly animating to the clicked one.


Login Redirection Bug

So, usually, after you login, it will take your to /dashboard by default. But, if I go to a page that is restricted by AccountsEntry.signInRequired() and it takes me to the sign-in route with the error message that I must be logged in and I then log in, it does not redirect. It does log into the user, but it does not leave the page at all and stays at the same sign-in form.
TLDR
Go to restricted page -> Redirects to sign-in with error message -> sign in --
-> signs in, but does not redirect... still on sign-in page with input data

it's still not solve yet!


HBASE-24165 maxPoolSize is logged incorrectly in ByteBufferPool

maxPoolSize should be logged as a plain number.
Raising PR#1483 again for QA run.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m 56s
Docker failed to build yetus/hbase:d9b4982ad4.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/1624

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1624/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Retry build

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
1m 14s
Docker failed to build yetus/hbase:d9b4982ad4.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/1624

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1624/2/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Triggered one more build, let's see if build issue is resolved this time.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
1m 19s
Docker failed to build yetus/hbase:d9b4982ad4.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/1624

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1624/3/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Fails because we don't have
HBASE-24251 PreCommit build is failing because of can not build docker image; addendum (#1579)

Signed-off-by: Duo Zhang<EMAIL_ADDRESS>
on branch-2.2?

I tried to apply to branch-2 but it won't go.
Put up a new PR against branch-2 or master?

Carry over the +1s from here to your new PR?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m 57s
Docker failed to build yetus/hbase:d9b4982ad4.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/1624

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1624/4/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

I tried to apply to branch-2 but it won't go.
Put up a new PR against branch-2 or master?

Master or branch-2 doesn't have this problem,
https://github.com/apache/hbase/blob/2774510e2bd70968a76a9f77df51ce987453aeba/hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteBufferArray.java#L69


Frontend has a horizontal scrollbar

Version:  commit 837c4701760dc479be7e0b4b7dabe2f1408b1be0
OS: Linux (Debian 9)
Browser:  Chromium 66.0.3357.0
Problem: The application's web page forces the user to scroll horizontally, which is not ergonomically efficient.
Reproducibility: have not tried (no FF/Safari/IE at the moment).
Possible underlying problem: card names are too long for a three-column layout to fit the screen width.

Fixed in d735ca1.


Publish extensions sequentially.

It was a mistake to do them all in parallel...

On my local machine, yes. I'd like to be able to use my cursor, even when running a command.

Unbounded concurrency will get you every time.


Not arm my quad

Hi
i have install last version of firmware for my ESP32 but when i connect battery not arm the quad.
I use MPU6050 and my radio is Flysky I6.
how i can solve ?
thanks

Hi @skimans,
It seems that you gyro is very noisy and callibration not finishing. Ensure your model is not moving when you connecting it. Consider mounting it with using adhesive tape and solder with flex cables instead direct soldering. If it won't help, you should look for replacement.

Hi
I have solved.
Was a problem on my gyro/acc.
I have used GY87 but not work becouse i have used 3,3 volt.
Now i have used GY521...normal MPU6050 and now work fine
One question . It's posible have a version firmware for Inav ?
Thanks much.
And my complimentes for this your wonderful project.
Stefano
Il sab 19 ago 2023, 16:10 rtlopez @.***> ha scritto:

Hi @skimans https://github.com/skimans,
It seems that you gyro is very noisy and callibration not finishing.
Ensure your model is not moving when you connecting it. Consider mounting
it with using adhesive tape and solder with flex cables instead direct
soldering. If it won't help, you should look for replacement.
—
Reply to this email directly, view it on GitHub
https://github.com/rtlopez/esp-fc/issues/62#issuecomment-1684985938, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASVQTJ5CJSQ3BXYG3YGCNP3XWDCMDANCNFSM6AAAAAA3WPHBCI
.
You are receiving this because you were mentioned.Message ID:
@.***>

What do you mean by

firmware version for Inav?

This firmware is neither Betaflight nor Inav. It is only partialy compatible to work with Betaflight-configurator. Not all features are available here.


Implemented Indexable ByteValue Indications

Added indexable indication array for ByteValues within the viewport displays.
Created categorical byte indiciations values & CSS selectors.

Screenshot: ByteValue Search Result Indication

Screenshot: ByteValue Replace Result Indication

Replacing 0x 00 00 00 -> 0x FF 01 FF

Closes #784

There seems to be some unintended merge changes between this branch and main that I did not change myself. These following items are marked as being removed:

src/language/dfdl.ts
src/providers/attributeHover.ts
src/providers/attributeHoverItems.ts

I'm currently working on resolving this.

I've come across a bug in the on:click event propogation while re-basing another ticket to include this PR's changes.
I'm currently working on a fix for this.

I hope to get to this review tomorrow.

The issue I ran into was due to the fact that I moved the listener events for the highlight selection. Previously, there were listeners for each ByteValue but it was less load on the extension to have a single listener at the ByteValue container level, then parse which element fired the event.
There are two separate on:mousedown and on:mouseup events that are distinct but the child components during a single byte selection only have on:click events. This meant that the parent container was still registering the mousedown and preventing a full click/release cycle needed for a click.

This is a nice new feature.  We can see replaced sequences.

We can select a range of bytes to edit.

We can select a single byte to edit in-line.

One minor inconsistency is that we we can close the multi-byte selection using the X in the 3rd column, but we lack that for the single byte selection.  To "escape out of" single byte mode edit, ESC works, but doesn't "escape out of" multi-byte edit mode.  It would be good to have ESC and the X work for both selection modes.

Things get more complicated when changes are made, then undone. The highlights are now incorrect when changes have been undone. It would be good to have the highlights work with undo/redo.

The issue with the undo / redo seems to be within the fact that there's no longer a history of changes being kept with messages between the extension, server, and UI. I believe this was changed with the search & replace got restructured to be incremental search & replace.

@stricklandrbls, that's right.  If a 1M file of 'a's gets changed to 'xX' that's a lot to keep track of and will not scale well.  I'd recommend doing the same here.  Just highlight the last replacement and the current search.  There will be no highlighting for replace all or replace rest since that's all done on the server side and is opaque on the client side.
If I insert or delete bytes the highlights float on top and do not float with the content.  If I delete or insert bytes in the middle of a selection, it doesn't shrink or grow.  If I revert all changes, the highlights remain.
Maybe the "fix" is to clear the selections when any edit is made or any change is undone/redone.  I think it's still possible to show the last replacement and the current search, but any other change to the content clears the selections.

... If I delete or insert bytes in the middle of a selection, it doesn't shrink or grow. If I revert all changes, the highlights remain.

Can you elaborate on this one? I was able to make a selection and have the highlights grow & shrink according to the length of the edited segment.

@stricklandrbls, I was deleting and inserting into the highlights from a search and replace.  That's pretty awesome how it works with the selection for editing.

I need those 3 bytes replaced with the new bytes (growing the file by 7 bytes), not just overwrite 10 bytes with 10 new bytes.

Is that not fundamentally how the applyChanges event works? Even on the extension side the message data members are:

originalDataSegment - The selected data from the unedited viewport perspective.
editedSegment - The segment of data to replace the original.
offset - Where in the viewport to apply the overwrite.

The highlights are based off the byte length of the  selectionDataStore

Here I append abc to PDF and the replacement results is PDFabc-1... growing the file by 3 bytes.

@stricklandrbls, these selections should not grow unless we're doing overwrite only.  If we are doing overwrite only, I like the second GIF that shows what additional bytes will be overwritten if the changes are applied.
applyChanges by default effectively deletes the original segment, and inserts the new one.  If overwrite only is used, it effectively overwrites the bytes starting at the given offset for the length of the edited segment.  I say effectively because Ωedit™ has an algorithm to change one segment into another using the smallest change possible.
You could use Ωedit™ viewports to power the selections and keep them updated when changes are made.  They are designed to track changes in data segments from a content perspective (use isFloating = true) or from a position perspective (use isFloating = false).  In this case, we want the the viewport to move with changes i the content, so use isFloating = true.  Ωedit™ can handle many of these for you and is one of the reasons for having floating viewports.

@scholarsmate
Is this a highlighting scenario that accurately depicts replacements of bytes < or > the original selection byte length?

The different highlighting for extending / shortening the byte selection via the editor panel, has been removed. Now, once a multiple byte selection has been made, only those bytes will be highlighted in the viewports. This is regardless of the size of the edited data segment.

Rebased on the most recent main.


⚠ Bofrost.at has degraded performance

In 5a6ac17, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2307 ms

Resolved: Bofrost.at performance has improved in 1c30200 after 13 minutes.


waiting for facehd-100 dataset

Thank you for your work.
When will the dataset be published ?

Thank you for your interest in our work. Because the dataset contains a large amount of face information, which is relatively sensitive and needs to go through the company's approval process. We are desensitizing the data and will make the dataset public as soon as possible.


Move release flow from travis to github actions

Following this PR by @kentcdodds, we're migrating all travis pipelines to github actions :)
An example for the action can be seen here.

We're moving development efforts to Testing Playground which already uses GitHub Actions.


canvas renderer prevents propagation of events

Related to #3937.
If a canvas renderer is on a pane on top of everything else, it will catch all DOM events and prevent any other layers from triggering their event handlers.
Reproducible with something like:
map.createPane('red');
map.getPane('red').style.zIndex = 650;
var canvasRenderer = L.canvas({pane: 'red'});

var redcircle = L.circle([51.506, -0.091], {radius: 100, renderer: canvasRenderer, color: 'red', fillOpacity: 1}).addTo(map);

var marker = L.marker([51.505, -0.09]).addTo(map);

Then, event handlers for the marker will not be fired when clicking on the red circle, or even when clicking outside of the red circle.

Duplicate of #4135


Cannot Publish App to Docker

When I try to publish my Extension to a local docker Image (BCOnPrem), I get "Could not publish the package to the Server. See Visual Studio Code debug console for more Details"
The debug console is empty. I found a related GitHub issued and changed to Runtime 2.0, but I still get the same error.
Then I tried the EventLog of the docker Image, here Is the error:
Index              : 859
EntryType          : Error
InstanceId         : 701
Message            : Server instance: NAV
Category: Development
ClientSessionId: 00000000-0000-0000-0000-000000000000
ClientActivityId: 2fb5bdbc-2492-4109-b9b4-7f31f3df51b9
ServerSessionUniqueId: cf9d74a9-9166-4a89-ad1a-456dae741181
ServerActivityId: 32c9699d-e5c5-403d-a415-ecdb152f661a
EventTime: 12/18/2018 15:45:11
Message Failed request -- Method:POST;
Url:http://bc:7049/nav/dev/apps?SchemaUpdateMode=synchronize; StatusCode:422;
ReasonPhrase:Unprocessable Entity; Token:
ProcessId: 1840
Tag: 00006NR
ThreadId: 27
CounterInformation:
Category           : (33)
CategoryNumber     : 33
ReplacementStrings : {Server instance: NAV
Category: Development
ClientSessionId: 00000000-0000-0000-0000-000000000000
ClientActivityId: 2fb5bdbc-2492-4109-b9b4-7f31f3df51b9
ServerSessionUniqueId: cf9d74a9-9166-4a89-ad1a-456dae741181
ServerActivityId: 32c9699d-e5c5-403d-a415-ecdb152f661a
EventTime: 12/18/2018 15:45:11
Message Failed request -- Method:POST;
Url:http://bc:7049/nav/dev/apps?SchemaUpdateMode=synchronize; StatusCode:422;
ReasonPhrase:Unprocessable Entity; Token:
ProcessId: 1840
Tag: 00006NR
ThreadId: 27
CounterInformation: }
Source             : MicrosoftDynamicsNavServer$NAV
TimeGenerated      : 18.12.2018 16:45:11
TimeWritten        : 18.12.2018 16:45:11
UserName           :

It seems to be, that an already published app cannot be updated from VSCode. If I go to Docker PowerShell and Uninstall & Unpublish the app, the next time it works again.
But why can't VSCode update the app automatically?

Hi @JulianTillmann,
There was a bug in the previous version of VScode (1.29.x) which had the effect that you didn't saw the errors when publishing. Update VSCode to version 1.30.x.

I'm using 1.30

Then you should see the error in the Debug console.
For why you are seeing the problem is hard to say but having some good steps to reproduce the issue would help us tremendously.

I'm still not getting any info in my debug console
I posted an update, Maybe that would help with the Repro?

      It seems to be, that an already published app cannot be updated from VSCode. If I go to Docker PowerShell and Uninstall & Unpublish the app, the next time it works again.

But why can't VSCode update the app automatically?

Right now I'm experimenting with Extension dependencies, Maybe I cannont update an Extension, when a dependant Extension is already installed?

Hi @JulianTillmann ! This seems related to #4256 . Could you try the following flow?

Publish version <IP_ADDRESS> of an extension from the command line.
Install the extension from the command line.
Try to publish version <IP_ADDRESS> from VScode. This will fail.
Increase the version to <IP_ADDRESS> from VSCode and try to publish again. This time it should work.

I'm still not getting any info in my debug console
I posted an update, Maybe that would help with the Repro?

      It seems to be, that an already published app cannot be updated from VSCode. If I go to Docker PowerShell and Uninstall & Unpublish the app, the next time it works again.

But why can't VSCode update the app automatically?

Right now I'm experimenting with Extension dependencies, Maybe I cannont update an Extension, when a dependant Extension is already installed?

Yes. You must uninstall the dependent extension first. Also F6 gives you more info in the debug output than what F5/ctrl+F5 currently does

@larswestman that seems to be the solution. What does F6 mean?

You run the in-client designer with F6. For some reason the error messages when publishing with F5/ctrl+F5 no longer shows as they have done in the debug output. errors when publishing with F6 still does though.
So use F5 och ctrl+F5 but if you get an error press F6 to see the error message

There is a new feature in VSCode that pops up multiple Debug windows and hides the output of the latest publish with F5. We have another bug tracking this problem and we hope to get it resolved soon. @JulianTillmann can I close this issue?

Thanks for the info, that's good to know.
I think this Case can be closed, but I'm not sure if that was the only Problem. The whole VSCode-AL-Docker-Thing seems still a bit beta-testy ;-)

Like all software, it can be improved, and we are working hard on doing so :)


Separate HappyTreeFunctions for internal and leaf nodes

The goal of this PR is to separate the functions for leaf and internal nodes based on tags. There are several items:

This PR allows to return different bounding volume types for leaf and internal nodes
This means that one cannot use (is_leaf_node ? getBoundingVolume(LeafNodeTag{}, ...) : getBoundingVolume(InternalNodeTag{}, ...)
The processing of leaf node indexing is moved out of the HappyTreeFriends to reduce the number of the i - (bvh.size()-1) calculations
This required a bit more code churn than I hoped due to having to replace all getLeafPermutationIndex. If desired, that function could have both global and local index variants, which would slightly reduce the amount of code. But I'm not really concerned about it at the moment, as getLeafPermutationIndex will be replaced by getValue in the next patch, requiring the same amount of changes.

GitLab results are pretty good, with minimal slowdowns. I'll double check on A100 and MI250X, and will check DBSCAN and MST results.

HIP benchmark results are unsatisfactory, and are very different from CUDA.

Comparison against current master or pre-merge of #860 ?

Comparison against current master or pre-merge of #860 ?

For benchmarks:
Against the current master: GitLab CI shows 17-21% slowdown in Serial knn for Power9.  I don't understand why Power9 is slowed down, and am willing to accept it.
Against the pre-#860 master, about 5-6% construction/5-8% radius/0% knn in Serial for AMD CPU, 6-14% construction/0% radius/0% knn on V100, 5-6% construction/7-8% radius/-5-10% knn on MI250X.

I think we might be using the wrong encoding for the left child and rope now that we are storing them in two independent arrays.

I tried a different scheme where internal nodes are always negative (offset by -1), leaf nodes are nonnegative. The code is indeed simpler, however, there's no performance difference.
Moreover, and the real stopping block, is that I am afraid to touch minimum spanning tree. It is a complete mess, where the current scheme is hardcoded so tightly in multiple arrays, keeping track of everything through permuted indices, and the whole thing is so fragile, that I believe it would take days to make any progress on it. I really don't want to spend time doing that for little benefit.

Converted to draft to figure out bvh index situation.

What is the next step after this PR? Is it immediately enabling different types for the node "bounding volumes"?

No, not immediately. I see at least few steps before that:

Converting leaf node to store value, which would be a pair index + bounding volume, and changing getLeafPermutationIndex to getValue
Introducing IndexableGetter internally which would use the value pair
Introducing Range
Changing the interface to allow user-defined indexable getter

The different bounding volume type for leaf and internal volumes can be part of 4, or even later.


No more able to debug with azure dev spaces

I was able to debug an ASP.NET CORE web app deployed on AKS cluster the first time I enabled azure dev spaces
Now I want to debug again the same app and it doesn't work anymore.
service and deployment are created on the cluster but the pod never gets created . Last time I tried I got this error in the azure dev spaces tab
Starting warmup for project 'WebApplication1'.
Using dev space 'default' with target 'TestAks'
Release "default-webapplication1-bf1cdcbc" does not exist. Installing it now.
NAME:   default-webapplication1-bf1cdcbc
LAST DEPLOYED: Thu Oct 25 18:35:09 2018
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Service
NAME             TYPE       CLUSTER-IP   EXTERNAL-IP  PORT(S)  AGE
webapplication1  ClusterIP  <IP_ADDRESS>         80/TCP   1s
==> v1beta2/Deployment
NAME             DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
webapplication1  1        0        0           0          1s
NOTES:

Get the application URL by running these commands:
export POD_NAME=$(kubectl get pods --namespace default -l "app=webapplication1,release=default-webapplication1-bf1cdcbc" -o jsonpath="{.items[0].metadata.name}")
echo "Visit http://<IP_ADDRESS>:8080 to use your application"
kubectl port-forward $POD_NAME 8080:80
Failed to build container image.
Service cannot be started.
An error occurred during warmup for project 'WebApplication1':
System.InvalidOperationException: Service cannot be started.
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.d__70.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClient.d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass26_0.<b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass26_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.DebugService.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass9_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass7_0.<b__3>d.MoveNext()
Enabling debugging...

@antogh what region is your cluster/controller in? We're patching Dev Spaces controllers in East US and West US 2 right now, so you may experience some intermittent failures while that's happening. If you're not in one of those two regions, let me know so we can investigate further.

Hi @lisaguthrie
the aks cluster is in west Europe (and me too)
yesterday the dev space debugger  was working fine
now it seems that VS gets stuck when it tries to deploy the container to the cluster to create the pod . Vs is still able to create the service and the deployment in the cluster . The problem occurs creating the pod

@antogh I just heard from one of the devs that we are patching West Europe now, too :) Can you wait for a couple of hours and try again?

@lisaguthrie  now magically  it works again :)
hope the next time I need it will still work.
Let’s wait another day and then close the issue ;)

@antogh glad to hear it :) And sorry for the inconvenience! Definitely let us know if you run into further issues.


ci: add sonar scan

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary
(describe what this merge request does)
Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
84.20
< 80

Duplicated lines density
:white_check_mark: OK
5
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
7
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/10/2024, 14:40:55 (UTC+0)

SonarQube Code Analytics
Quality Gate passed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
84
< 80

Duplicated lines density
:white_check_mark: OK
5
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
7
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 5/10/2024, 16:11:33 (UTC+0)


#nosec doesn't work as documented

The documentation describes that any lines annotated with #nosec should be ignored, but the actual code just looks for nosec.  This is causing some lines to be ignored as a false negative.
The code in core/analyzer.go looks like it just looks for 'nosec':
// ignore a node (and sub-tree) if it is tagged with a "nosec" comment
func (gas *Analyzer) ignore(n ast.Node) bool {
        if groups, ok := gas.context.Comments[n]; ok && !gas.ignoreNosec {
                for _, group := range groups {
                        if strings.Contains(group.Text(), "nosec") {
                                gas.Stats.NumNosec++
                                return true
                        }
                }
        }
        return false
}

Thanks. This is fixed in PR #99


Unable to load any file

When trying to load a file it fails, looking at the console the error is:
"File doesn't exist:"
Digging in the reasons I see that the problem happens in the operator Import_OT_mfnetCDF.
In my system, these two lines doesn't work properly.
split_path = self.properties.filepath.split('/')[0:-1]
fdir = ('/'.join(str(dir) for dir in split_path))

Using dirname from os.path this works properly.
fdir = dirname(self.properties.filepath)

I think that this approach is safer and more portable.

Excellent solution!!!


feat: add a api for unifying the KCL cli

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

re #289

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

307 of 1386 (22.15%)  changed or added relevant lines in 16 files are covered.
42 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-5.6%) to 38.592%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/cmd/cmd_push.go
0
1
0.0%

pkg/oci/oci.go
3
8
37.5%

pkg/downloader/downloader.go
25
34
73.53%

pkg/package/package.go
0
11
0.0%

pkg/cmd/cmd_run.go
0
12
0.0%

pkg/opt/opt.go
0
23
0.0%

pkg/client/visitor.go
85
113
75.22%

pkg/utils/utils.go
0
28
0.0%

pkg/client/pull.go
0
56
0.0%

pkg/client/client.go
46
103
44.66%

Files with Coverage Reduction
New Missed Lines
%

pkg/oci/oci.go
1
23.56%

pkg/cmd/cmd_run.go
2
0.0%

pkg/client/client.go
39
51.67%

Totals

Change from base Build<PHONE_NUMBER>:
-5.6%

Covered Lines:
2647

Relevant Lines:
6859

💛  - Coveralls


Laravel 10 support

As this project seems to be dead (sad because this package is pure gold!), have anyone forked this to work with Laravel 10?

I'm using this if is any help https://github.com/maksuco/laravel-blade-sortable , tested with L10 and Livewire V3

Could not find a matching version of package maksuco/laravel-blade-sortable. Check the package spelling, your version constraint and that the package is available in a sta
bility which matches your minimum-stability (dev).

Sorry about that, the correct way to install is composer require maksuco/laravel-blade-sortable:dev-master

Sorry about that, the correct way to install is composer require maksuco/laravel-blade-sortable:dev-master

doesnt work unfortunately

maybe because the package is not in packagist

First add repository to your composer.json file:
{
    "require-dev": {
        ...
    },
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/maksuco/laravel-blade-sortable.git"
        }
}

Now run composer require maksuco/laravel-blade-sortable:dev-master


(doc) Fix links on crates.io to repo

Seemed slightly concerning when I couldn't click through from the crates.io page to this repo 😅 I'm super excited to use this project for this exact use case!!! I nearly rebuilt the same thing and stumbled upon this. Thank the packaging gods!

I'm a little unclear on why this failed 🤔  Regardless, it would be nice to fix up the links on the crates.io page

Thanks!

So, I just revisited the crates.io / lib.rs pages, and I think the links are still broken. I suspect doing a point release would fix this?
Anywho, thanks for accepting the PR and making this tool! Gives me hope I'm not crazy when I find someone has already built the thing I assumed did not exist :-)


Possible memory leak caused by loadSnapshot

Because undoStack is not cleaned up, memory usage will increase dramatically on Chrome if you call loadSnapshot for multiple times.
Possible fix is set undoStack to empty in loadSnapshot method.
loadSnapshot: (snapshot) ->
     // ...
    if snapshot.shapes
      @shapes = []
      @undoStack = []
    // ...

This is not a memory leak (per definition [1]), just some unintended behaviour.
But to be fair, resetting @undoStack (maybe by doing @undoStack.length = 0 in loadSnapshot is a good idea. I guess when you load a (new) snapshot, you want the undoStack to be empty.
If you want, I can make a PR for that.
[1] Wikipedia says: In computer science, a memory leak is a type of resource leak that occurs when a computer program incorrectly manages memory allocations in such a way that memory which is no longer needed is not released.
undoStack is still needed and accessed by literally canvas. The unintended behaviour is that undoStack still contains content from previous snapshots.

@anx-ckreuzberger Thank you for your reply. Yes it's not a memory leak, sorry for my misspeaking, I updated the title, hope it describes the problem more properly.
I think it's a good idea to reset undoStack when load a new snapshot. I appreciate it if you can make a PR.

Yep, if someone sends a PR for this I'll happily merge it. Thanks for the investigation!

PR is in :) Sorry for the waiting time


Add an "edit mode" so the recycling center worker can modify the "layout", number and type of bins

I'm not sure what you mean.

Closed by #15


InvalidStateError at not awaited task connection.close

Looks like there is 2 problems:

InvalidStateError at connection.close
Not awaited tasks at https://github.com/micro-fan/aiozk/blob/master/aiozk/session.py#L124, https://github.com/micro-fan/aiozk/blob/master/aiozk/session.py#L127

states.py:50 - transition_to() DEBUG --- Session transition: connected -> suspended
session.py:179 - repair_loop() DEBUG --- Repair state reached
session.py:109 - find_server() INFO --- Connecting to localhost:2182
connection.py:75 - connect() DEBUG --- Initial connection to server localhost:2182
connection.py:57 - _make_handshake() DEBUG --- Sending 'srvr' command to localhost:2182
connection.py:69 - _make_handshake() DEBUG --- Version info: (3, 6, 1)
connection.py:70 - _make_handshake() DEBUG --- Read-only mode: False
connection.py:72 - _make_handshake() DEBUG --- Actual connection to server localhost:2182
session.py:113 - find_server() INFO --- Connected to localhost:2182
session.py:123 - find_server() DEBUG --- Close old connection
base_events.py:1619 - default_exception_handler() ERROR --- Task exception was never retrieved
future: <Task finished coro=<Connection.close() done, defined at /Users/bkhasanov/Envs/ipv4mgr/lib/python3.7/site-packages/aiozk/connection.py:256> exception=InvalidStateError('invalid state')>
Traceback (most recent call last):
  File "/Users/bkhasanov/Envs/ipv4mgr/lib/python3.7/site-packages/aiozk/connection.py", line 264, in close
    await self.read_loop_task
  File "/Users/bkhasanov/Envs/ipv4mgr/lib/python3.7/site-packages/aiozk/connection.py", line 170, in read_loop
    f.set_exception(response)
asyncio.base_futures.InvalidStateError: invalid state

@khasanovbi
I'll look into it
Thanks,

Hi, the second problem is not fixed, fire-and-forget is bad pattern for asyncio, maybe aiojobs will help in this case.

Hi @khasanovbi
I agree with you. At line no 127, .find_server task is created and forgot. This can make multiple number of .find_server tasks run simultaneously. Thus this can incur undefined behavior. I am going to fix it soon.
At line no 124, old_conn.close task is created. But I think it is not bad because we do not need to spend time on waiting for closing the obsolete connection and fire-and-forget saves the time.
Thanks,


prop-types are ignored when render returns a React.createElement

One of the features of a library I'm developing is allowing the return tag to be of type string, function or ReactElement. In order to make that work reliably I use an anonymous function as my return tag, so the foot print of my render may look like:
render() {
    let Tag = React.DOM.div;

    return Tag({
        className: this.props.className,
        ...this.props
    }, this.props.children());

In my usecase the Tag can either be a React.DOM element or it can be an anonymous function that returns a cloned ReactElement. This completely breaks prop validation, I get no errors. Right now I have to insert a random return statement (such as return(<div/>)) above my actual return statement to see if there are prop errors.

This is actually fixable by wrapping the Tag in a React.createElement and it will work for any element (including strings) so closing this.

Thought this was fixed, but it is not. If the return function of the render is a React.createElement the react/prop-types validation simply won't fire at all:
export class Test extends React.Component {
    render() {
        return React.createElement(
            'div',
            this.props,
            this.props.children
        );
    }
}

react/prop-types won't ever fire if you return a ReactElement this way. I've tested this with several other props as well to no avail. Putting a return (); above the return will fire all react/prop-types properly.

It should be fixed in master by #206 but the fix is not released on npm yet.

Just bumped to 3.3.2 and still no luck. Here's a gist of a simple React (es6 + experimental) that doesn't throw any prop-type warnings/errors:
https://gist.github.com/hallister/7a450c921a9907a87cd9

After test, I correctly have all the warnings with your gist (for dog, cat, stuff, component and children).
Tested with<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Hey thanks for the versions, didn't realize I was running on a fairly dated eslint (whoops!). Problem solved.


Homebridge

Any way this could be turned into a homebridge plugin to control heos speakers from a iOS device. I’m a newb so please excuse my ignorance....

Yes it should be possible to use this package in that package. This package is a wrapper for all possible api-calls.
Basically this package makes it easier to talk to any heos-device.
I would love to help if you have any more questions or need help getting started. I have not had any use cases to test this package on so I'm not really sure how good / bad it is, but if anything doesn't work I'll gladly fix it.

Awesome. I would love your help getting it started. Kinda new to all of this. I already have Homebridge installed on my home computer. I have a couple plug-ins already installed and working properly.  I just don’t know what steps need to been done to make this compatible with the homepage server.

First of all you will have to write your own plugin. This project will not be a plugin only for homebridge as it is a general purpose tool, however use this project to simplify all the api-calls. To create a plugin for homebridge check out this link for information on how to do that.
I have not made any plugins for homebridge so I can not help you with that. Please tell me if you stumble on any problems with heos-api and I'll gladly help with them.

Thank you


do not request x64 for latest macos to work

latest macOS (currently macOS-14) uses arm64 , so we should not request x64 explicitly.

Also with the new sphinx, we need to ignore cache warning, see
https://github.com/sphinx-doc/sphinx/issues/12300


[CI][Integration] Spark jobs are failing with problem on org.apache.arrow.flatbuf

Describe the bug, including details regarding any error messages, version, and platform.
The spark jobs:
test-conda-python-3.10-spark-v3.5.0
test-conda-python-3.11-spark-master
test-conda-python-3.8-spark-v3.5.0
Are currently failing with:
 Error: ] /spark/sql/core/src/main/scala/org/apache/spark/sql/execution/arrow/ArrowConverters.scala:26: object flatbuf is not a member of package org.apache.arrow
Error: ] /spark/sql/core/src/main/scala/org/apache/spark/sql/execution/arrow/ArrowConverters.scala:456: Class org.apache.arrow.flatbuf.Message not found - continuing with a stub.
Error: [ERROR] two errors found
Error:  Failed to execute goal net.alchim31.maven:scala-maven-plugin:4.8.0:compile (scala-compile-first) on project spark-sql_2.12: Execution scala-compile-first of goal net.alchim31.maven:scala-maven-plugin:4.8.0:compile failed: org.apache.commons.exec.ExecuteException: Process exited with an error: 255 (Exit value: 255) -> [Help 1]
Error:
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
Error:
Error:  After correcting the problems, you can resume the build with the command
Error:    mvn <args> -rf :spark-sql_2.12

Component(s)
Continuous Integration, Integration

This is also reproducible for 16.1.0 but I don't think this is related to any change on our side and doesn't seem to be a blocker.
@danepitkin @vibhatha @kiszk any thoughts?

The error message is the same as https://github.com/apache/arrow/issues/40549.

2024-05-07?, failure
test-conda-python-3.10-spark-v3.5.0
2024-05-09, failure
test-conda-python-3.10-spark-v3.5.0

In the previous issue, this PR causes the issue.

MINOR: [Java] Bump org.apache.maven.plugins:maven-shade-plugin from 3.2.4 to 3.5.2 in /java

This PR, which was merged on April 29, include the following change.

Update maven-shade-plugin to 3.5.1 (via org.apache:parent)

@danepitkin @lidavidm what should we do with this one?

https://github.com/apache/arrow/pull/41309#issuecomment-2106123625 causes this failure.

I am just surprised this comment is completely ignored.

We can revert. Sorry about that @kiszk

It would be good to know why maven-shade-plugin is causing issues, though

I guess my bad but it's quite hard to work on improving the build and also track tests which are not part of the CI. I will repost the change though with hopefully a fix, although nobody really understands what's the exact issue?

Yes, I've asked Vibhatha if we can get more of those tests into proper CI...

The issue seems to be because maven-shade-plugin generates and attach a new pom file containing the following dependency:
    <dependency>
      <groupId>org.apache.arrow</groupId>
      <artifactId>arrow-format</artifactId>
      <version>17.0.0-SNAPSHOT</version>
      <scope>provided</scope>
    </dependency>

which is exactly what the plugin is supposed to be doing
I have the same resulting pom by using maven-shade-plugin 3.3.0, and going through changes, I found this change which is a bugfix to the plugin for this issue
As to how to address this within the Arrow project, I'd need some perspective. The main issue is that a Maven module has a unique pom.xml definition for all the artifacts attached to it. But when attaching shaded artifacts the list of dependencies is not quite the same, and this is definitively conflicting.
I have no idea which project is actually using the shaded version of arrow-vector, but Spark isn't and so if we agree that the pom.xml should reflect the dependencies for the main artifact, then we should tell maven-shade-plugin to not generate a new pom.xml file. If we need both dependencies, then we are quite in a predicament I'd guess (and same would apply to the other plugins using maven-shade-plugin)

Hmm, the POM should reflect the main file. The shaded version might need to be split into a separate artifact...

FYI: This is my trial. In the current configuration, we cannot upgrade 3.3 or later. It is consistent with @laurentgo 's observation.


SPR_getAnimationDone() is missing

https://github.com/Stephane-D/SGDK/blob/617e3cb5118be3b1e5c30ef0b778bd675e1e9485/inc/sprite_eng.h#L49
According to the changelog SPR_getAnimationDone() was added in SGDK 1.90 but unnincluded in source code

Use SPR_isAnimationDone()

Method has simply be renamed :)