Boost header(s) files not found

Describe the bug
After updating BOOST_ROOT according to #661 to list(APPEND BOOST_ROOT $ENV{BOOST_ROOT_1_72_0}). CMake finds the this folder:
 - Boost_INCLUDE_DIRS: C:/hostedtoolcache/windows/Boost/1.72.0

The problem is our compilation fails because it cannot find some headers files:
* boost/pending/disjoint_sets.hpp
* boost/function_output_iterator.hpp
* boost/range.hpp

I looked into C:/hostedtoolcache/windows/Boost/1.72.0/boost but the files are not present (starting at line 165 of our pipeline, youll see all the files present in boost folder).
I also tried with 1_69_0 same result.
Do I need to do something special to have access to the previous header files ?
Area for Triage:

Question, Bug, or Feature?:

Bug and question.
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[X] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
Build passes succesfully.
Actual behavior
Build fails with boost header files not found.

Hello, @MonkeyBreaker
These headers are located in {BOOST_ROOT_1_72_0}\include\boost.

Okay, thank you !
But why is Boost_INCLUDE_DIRS set to C:/hostedtoolcache/windows/Boost/1.72.0  ? It should point to the folder containing the headers files, no ? If I understood correctly the documentation.

We use non default path for boost thus, not be found by CMake, you can tell CMake where to look for:
SET (BOOST_ROOT "$ENV{BOOST_ROOT_1_72_0}")
SET (BOOST_INCLUDEDIR "$ENV{BOOST_ROOT_1_72_0}\boost\include")
SET (BOOST_LIBRARYDIR "$ENV{BOOST_ROOT_1_72_0}\lib")

We could also add them to the .yaml file directly as variables ?
Or would they be overwritten if we call find_package(Boost) ?

@MonkeyBreaker, any updates?

I'll look this week for a solution to add the variables into the .yaml file.
As a workaround, we download boost header into a specific location, It's not very efficient, but it works.
As I said before, I'll look for a better solution this week, and post here any updates.

Hi,
Well after digging this morning on the issue, I did not find any solution with only touching the .yaml file. I'm not an expert on this field, maybe someone else could come with a solution, but I'm won't explore further.
The solution in our case that would not impact other users for the library is to do as follow:
if(DEFINED $ENV{BOOST_ROOT_1_72_0})
    list(APPEND BOOST_ROOT "$ENV{BOOST_ROOT_1_72_0}")
    list(APPEND BOOST_INCLUDEDIR "$ENV{BOOST_ROOT_1_72_0}\boost\include")
    list(APPEND BOOST_LIBRARYDIR "$ENV{BOOST_ROOT_1_72_0}\lib")
endif()

find_package(Boost ...)

I only have a last remark, could it be possible that you create a "generic" variable to the latest version of boost in the system ? Something around BOOST_ROOT_LATEST, in my opinion, if you update to a newer release in the future, I won't need to update my files to use the latest version in the pipeline.
Have a nice day,
Julián

Hello @al-cheb,
I like your solution, if you update on your side, we only need to touch the yaml file.
For me we can close this issue, but I don't know if it's already in the documentation, maybe add more information about the boost include directories, what do you think ?
Otherwise, thank you for your help,
Julián

@MonkeyBreaker thank you for your suggestion!
 We will add this point there as soon as it is ready.
I am closing this issue for now. Feel free to ping if you have any questions


DeviceId returns the board instead of the device Id

Hello,
I am a bit confused at why this line: https://github.com/react-native-device-info/react-native-device-info/blob/master/android/src/main/java/com/learnium/RNDeviceInfo/RNDeviceModule.java#L193
doesn't use Build.DEVICE instead.
On my side, changing that returns the expected values for android (the ones from this list: https://storage.googleapis.com/play_public/supported_devices.html )

https://github.com/react-native-device-info/react-native-device-info/blob/1a10a875c840bbe1ea0cb00fed592974d32d5f32/android/src/main/java/com/learnium/RNDeviceInfo/RNDeviceModule.java#L733-L736
Different API has the Build.DEVICE key - been that way forever, so not likely to change now, but the info you want is available


Support CommandPlugin

CI looks good. Can you squash the commits and re-push them so we can keep the history (even after merge) a bit cleaner?

I cleaned up git history.
I don't know git squash well, Is it ok?


EmissionTracker not updating .csv file, but create new

CodeCarbon version: 2.1.4
Python version: 3.8.16
Operating System: Linux (Colab)

Description
Hi all,
I was trying to update my .csv emission file with some results. However it keeps creating new "*.bak" file, even tho i've setted:
tracker = codecarbon.EmissionsTracker(output_dir = "/content/emissions/",
output_file = "test.csv",
tracking_mode = "process",
log_level = "debug",
on_csv_write = "append")
Every time i try to run this cell, a new file named "test.csv_n.bak" (where n is the number of times i runned the cell) is created
What I Did
tracker = codecarbon.EmissionsTracker(output_dir = EMISSION_PATH+"/",
                                    output_file = "test.csv",
                                    tracking_mode = "process",
                                    log_level = "debug",
                                    on_csv_write = "append")

tracker.start()

train_val_mnist = fit_and_eval(snet_mnist, epochs, optimizer, criterion, mnist_nclasses,
                                                  train_dataload_mnist, val_dataload_mnist, device,
                                                  T=5, validation_step=True, convolution=False, onehot=False)

emissions_mnist_snn: float = tracker.stop()

Just remove the initialization of the tracker from the cell.

Did you solved your problem by initializing EmissionsTracker just one time ?


[dv] Fix build seed CI issue

Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

I had a closer look and realized that we were looking in the wrong spot.
There seems to be an issue when RndCnst are regenerated in the build phase only, possibly because SW headers & images are generated in the run phase. E.g. it could be that the ROM image is scrambled with the wrong RndCnst that is being used as the scrambling key.
I am reverting this for now until we found a way to pipe this through bazel.
(Note that this is not an issue if Dvsim is launched locally since the in-tree changes persist between build and run phase.)


make scala-collection-compat a test only dependency

we have code in pekko for what we get from scala-collection-compat
one thing we don't have is LazyList which is used in 1 test class

lgtm - just scala.collection.compat.immutable.LazyList needs to be handled

thanks @nvollmar - I added back scala-collection-compat but just as a test dependency


Specify that read-only volumes are not currently supported

Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

 Specify that read-only volumes are not currently supported

@nzoschke I see what you mean. It just feels weird to say "X isn't supported" without giving people a route to express that they want it.


gpscorrelate: 2.1 -> 2.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dfandrich/gpscorrelate/releases.
meta.description for gpscorrelate is: GPS photo correlation tool, to add EXIF geotags
meta.homepage for gpscorrelate is: https://dfandrich.github.io/gpscorrelate/
meta.changelog for gpscorrelate is: https://github.com/dfandrich/gpscorrelate/releases/tag/2.2
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 2.2 with grep in /nix/store/1f6507dqd72c4jansjbkc40csc39w9yf-gpscorrelate-2.2
found 2.2 in filename of file in /nix/store/1f6507dqd72c4jansjbkc40csc39w9yf-gpscorrelate-2.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

gpscorrelate

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1f6507dqd72c4jansjbkc40csc39w9yf-gpscorrelate-2.2 \
  --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 gpscorrelate https://github.com/r-ryantm/nixpkgs/archive/524ff236e6bed501da139810dff3aa88b834a123.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/524ff236e6bed501da139810dff3aa88b834a123#gpscorrelate

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1f6507dqd72c4jansjbkc40csc39w9yf-gpscorrelate-2.2
ls -la /nix/store/1f6507dqd72c4jansjbkc40csc39w9yf-gpscorrelate-2.2/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 result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

gpscorrelate

Maintainer pings
cc @sikmir for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 349545

x86_64-darwin

:white_check_mark: 1 package built:

gpscorrelate

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

1 package built:

gpscorrelate


request: add autocomplete component

What is Autocomplete component
Autocomplete component is a simple text input enhanced by panel of suggested options depending on what the user has typed. It would be easier to have autocomplete logic handled and user would provide array of possible options. It is similar to Combobox.

Duplicate of #173

up

up

I have been attempting to implement a reusable form autocomplete component using the combobox. So far I have integrated the combobox as a reusable from item, and added a button when an item searched isn't included in the options. Now just need some ts magic to update the field and get the updated field displayed.

up

up

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


[MM-35251] Add JavaScript Apps quick start guide

Summary
It's heavily based on the go guide. I've keep it on plain JS and therefore easy to use.
@mickmister I would love to hear your feedback on the code.
Ticket Link
https://mattermost.atlassian.net/browse/MM-35251
Fixes https://github.com/mattermost/mattermost-plugin-apps/issues/168

Thank you @hanzei this really rounds it out and makes me more confident pushing the "in any language" by having at least 2 examples :)

Your welcome @justinegeffen. Glad you like it.

Sorry, miss clicked there.

@mickmister, are we good to merge this?

Thanks for all the feedback. I've submitted https://github.com/mattermost/mattermost-developer-documentation/pull/812 to implement it.


feat: add GitHub component

Because

We need a GitHub component to complete some development automation tasks
This commit

Related Issue
instill-ai/instill-core#1025
Todo

[X] TASK_GET_ALL_PULL_REQUESTS: function to get all prs given owner name and repository name.
[X] TASK_GET_PULL_REQUEST: function to get a specific pr given owner name, repository name, and pr number. (including file changes)
[X] TASK_GET_REVIEW_COMMENT: get review comment inside a pull request
[X] TASK_CREATE_REVIEW_COMMENT: create review comment inside a pull request
[X] TASK_GET_COMMIT: get commit messages and file changes
[x] TASK_CREATE_ISSUE: post issue
[x] TASK_GET_ALL_ISSUES: get all issues in a repo
[x] TASK_GET_ISSUE: get an issue
[x] TASK_CREATE_WEBHOOK: register webhook, https://docs.github.com/en/webhooks/webhook-events-and-payloads

Concerns about this component

The rate limit of GitHub API calls for unauthenticated requests is 60 requests per hour, which is quite small. I left the token field optional because some tasks are available without authentication.

Personal access token rate limit: 5000/hr
GitHub Enterprise Cloud organization: 15000/hr

The "create review comment" task may need more checks. The docs of GitHub are quite unclear and there seems to be some mismatch between the document and the actual API call.
I am using a Mock server to simulate the API calls just like in other components. I don't know whether it will be difficult to maintain in the future.

Hi @YCK1130
Could you fix the conflict?


Use generate_key_pair() everywhere

Use the generate_key_pair() convenience function everywhere that a key pair is needed.
Also standardise on privkey and pubkey as variable names for private keys and public keys, and index keys on 1.
A few other minor tidy-ups.

rebased on master

Thanks for the review, @bitschmidty !


refactor: restore grouping of functions in script

Recent(ish) changes placed functions in the wrong sections. Fix that and label the sections more clearly.

I've put this in 1.6 since it's the kind of change that would otherwise cause continued merge headaches.
Note that github does a rather mediocre job of showing what has actually happened here, which is simply moving some functions and adding some section heading comments.


Support for the IQ Pro

I'm considering an IQ Pro instead of a IQ Panel 4 and was wondering if this homebridge plugin will have pending support for the Pro. I see the Hub is marked as support pending already.
Thanks!

I'm considering an IQ Pro instead of a IQ Panel 4 and was wondering if this homebridge plugin will have pending support for the Pro. I see the Hub is marked as support pending already.
Thanks!

Hi,
I wrote ´status pending' for IQ4 Hub because no one reported using it with the plugin yet ...
In spec, it's stated that Control4 is still an integration partner for IQ pro, but I can't find any procedure in installation guide to enable the feature. The Control4 integration has been fairly consistent between all supported panels and official driver hasn't been updated in a long time. IQ pro might work with this plugin, but don't take this for granted...

Thanks for the info @EHylands - if I do go with the Pro over the IQ 4 I will be a guinea pig and see if i can find the ability to enable Control4!

Thanks for the info @EHylands - if I do go with the Pro over the IQ 4 I will be a guinea pig and see if i can find the ability to enable Control4!

The Pro panel looks line a really nice product!
Please report back to us if you can get it to work with the plugin (or with log file if you need us to debug anything!)

Both the IQ Pro and the IQ 4 NS are programmed using a Qolsys mobile app so it is going to depend on what they expose in the app.

@smacgregor can you confirm that you got the plugin running against the IQ Pro?

Closing for now under the unconfirmed assumption that the plugin does work against the IQ Pro, when the IQ Installer app is used to configure Control4 support the same as an IQ4.


1088 plots and no wins 3 days pass

Ubuntu 20.04 x64 client version v 1.1.5 installed from source
Logs | grep warning

2021-12-20T22:34:17.697 full_node full_node_server        : WARNING  [Errno 32] Broken pipe <IP_ADDRESS>
2021-12-20T22:51:48.526 full_node full_node_server        : WARNING  Banning <IP_ADDRESS> for 10 seconds
2021-12-20T22:51:48.536 full_node full_node_server        : WARNING  Invalid handshake with peer. Maybe the peer is running old software.
2021-12-20T23:05:29.424 full_node full_node_server        : WARNING  [Errno 32] Broken pipe <IP_ADDRESS>
2021-12-20T23:09:46.408 full_node full_node_server        : WARNING  Was not able to get peername from <IP_ADDRESS> - closing connection
2021-12-20T23:29:23.962 full_node full_node_server        : WARNING  Cannot write to closing transport <IP_ADDRESS>
2021-12-20T23:44:42.399 full_node full_node_server        : WARNING  [Errno 32] Broken pipe <IP_ADDRESS>
2021-12-21T00:17:27.352 full_node full_node_server        : WARNING  Was not able to get peername from <IP_ADDRESS> - closing connection
2021-12-21T00:25:57.864 full_node full_node_server        : WARNING  [Errno 32] Broken pipe <IP_ADDRESS>
2021-12-21T00:59:06.511 full_node full_node_server        : WARNING  [Errno 32] Broken pipe <IP_ADDRESS>
2021-12-21T02:35:51.796 full_node full_node_server        : WARNING  Banning <IP_ADDRESS> for 10 seconds
2021-12-21T02:35:51.961 full_node full_node_server        : WARNING  Banning <IP_ADDRESS> for 10 seconds
2021-12-21T02:35:52.320 full_node full_node_server        : WARNING  Banning <IP_ADDRESS> for 10 seconds
2021-12-21T02:35:52.357 full_node full_node_server        : WARNING  Banning <IP_ADDRESS> for 10 seconds
2021-12-21T02:35:52.496 full_node full_node_server        : WARNING  Banning <IP_ADDRESS> for 10 seconds
2021-12-21T02:35:52.903 full_node full_node_server        : WARNING  Banning <IP_ADDRESS> for 10 seconds
2021-12-21T03:09:02.102 full_node full_node_server        : WARNING  Cannot write to closing transport <IP_ADDRESS>

nothing interesting
sit farm summary

Farming status: Farming
Total silicoin farmed: 0.0
User transaction fees: 0.0
Block rewards: 0.0
Last height farmed: 0
Local Harvester
1088 plots of size: 107.682 TiB
Plot count for all harvesters: 1088
Total size of plots: 107.682 TiB
Staking addresses:
(balance: 0, plots: 1088)
Estimated network space: 290.583 PiB
Expected time to win: 13 hours and 59 minutes
Note: log into your key using 'sit wallet show' to see rewards for each key

Please, help me to understand what I doing wrong nothing interesting

You should stake 108 SIT

You should stake 108 SIT
How I can check this?

Silicoin support both old protocol and new protocol.
Please follow https://github.com/silicoin-network/silicoin-blockchain/wiki/How-To-Stake to stake your SIT.


chore: Release v5.1.0

Added

New DiceTerm.Result parameter locked (boolean): When set to true, the result cannot be pushed, but is still active and counted for the total.
Foundry V10 compatibility for the manifest.

Fixed

Negative modifiers are now correctly applied to ALIEN RPG rolls with stress.

Removed

DOCUMENTATION.md is removed in favor of JSDocs-generated documentation.

Note: the DiceTerm.Result.locked parameter is mandatory for the game Blade Runner and the ability to choose which die can be selected for the push.


feat: add exception code

feat: add exception code

Codecov Report

Merging #11859 (e2dd85b) into 3.2 (6b7a735) will decrease coverage by 0.17%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.2   #11859      +/-   ##
============================================
- Coverage     69.16%   68.99%   -0.17%
+ Complexity      341        2     -339
============================================
  Files          3277     1554    -1723
  Lines        153902    64250   -89652
  Branches      25683     9370   -16313
============================================
- Hits         106444    44332   -62112
+ Misses        38077    15632   -22445
+ Partials       9381     4286    -5095

see 1885 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@AlbumenJ @EarthChen PTAL


Cannot import name 'Markup' from 'jinja2'

Flask==2.1.1
Jinja2==3.1.1
In flask_modals/modal.py replace
import Markup from jinja2
with
from jinja2.utils import markupsafe
markupsafe.Markup()
https://pypi.org/project/flask-modals-markupsafe/
Author and licence are unchanged.

Hey, this issue seems to still be occuring some of the markup changes have been missed in the modal.py file.


 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 48s
root in the patch failed.

-1 :x:
compile
0m 37s
hbase-server in the patch failed.

-0 :warning:
javac
0m 38s
hbase-server in the patch failed.

-1 :x:
shadedjars
6m  7s
patch has 20 errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 35s
hbase-server generated 1 new + 21 unchanged - 0 fixed = 22 total (was 21)

_ Other Tests _

-1 :x:
unit
0m 38s
hbase-server in the patch failed.

25m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25881

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e1c93b5142cd 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3c70bc1f31

Default Java
AdoptOpenJDK-1.8.0_282-b08

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/patch-compile-hbase-server.txt

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/patch-compile-hbase-server.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/testReport/

Max. process+thread count
88 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 50s
root in the patch failed.

-1 :x:
compile
0m 43s
hbase-server in the patch failed.

-0 :warning:
javac
0m 43s
hbase-server in the patch failed.

-0 :warning:
checkstyle
0m 59s
hbase-server: The patch generated 4 new + 0 unchanged - 0 fixed = 4 total (was 0)

-0 :warning:
whitespace
0m  0s
The patch 1 line(s) with tabs.

-1 :x:
hadoopcheck
2m  6s
The patch causes 20 errors with Hadoop v3.1.2.

-1 :x:
hadoopcheck
4m 12s
The patch causes 20 errors with Hadoop v3.2.1.

-1 :x:
hadoopcheck
6m 21s
The patch causes 20 errors with Hadoop v3.3.0.

-1 :x:
spotbugs
0m 35s
hbase-server in the patch failed.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

-1 :x:
mvninstall
2m 17s
root in the patch failed.

-1 :x:
compile
0m 43s
hbase-server in the patch failed.

-0 :warning:
javac
0m 43s
hbase-server in the patch failed.

-1 :x:
shadedjars
6m 16s
patch has 20 errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 23s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
0m 41s
hbase-server in the patch failed.

31m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25881

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0d3e2e8e93fe 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3c70bc1f31

Default Java
AdoptOpenJDK-11.0.10+9

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk11-hadoop3-check/output/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/testReport/

Max. process+thread count
96 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 36s
the patch passed

+1 :green_heart:
compile
3m 16s
the patch passed

+1 :green_heart:
javac
3m 16s
the patch passed

-0 :warning:
checkstyle
1m  1s
hbase-server: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-0 :warning:
whitespace
0m  0s
The patch has 1 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>.  Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 39s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

-1 :x:
shadedjars
6m 33s
patch has 10 errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
the patch passed

_ Other Tests _

-1 :x:
unit
147m 32s
hbase-server in the patch failed.

175m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25881

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6d1baddbc321 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3c70bc1f31

Default Java
AdoptOpenJDK-1.8.0_282-b08

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/2/artifact/yetus-jdk8-hadoop3-check/output/patch-shadedjars.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/2/testReport/

Max. process+thread count
4264 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/2/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 28s
the patch passed

+1 :green_heart:
compile
1m 17s
the patch passed

+1 :green_heart:
javac
1m 17s
the patch passed

+1 :green_heart:
shadedjars
8m 23s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

-1 :x:
unit
158m 15s
hbase-server in the patch failed.

190m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25881

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e68b783f4974 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3c70bc1f31

Default Java
AdoptOpenJDK-11.0.10+9

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/3/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/3/testReport/

Max. process+thread count
4201 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/3/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

Still have to look into test failure. @shahrs87 @anoopsjohn wondering if you guys can have a look and provide feedback about the approach if any. Thanks

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  6s
the patch passed

+1 :green_heart:
compile
1m 21s
the patch passed

+1 :green_heart:
javac
1m 21s
the patch passed

+1 :green_heart:
shadedjars
10m 59s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 49s
the patch passed

_ Other Tests _

-1 :x:
unit
258m 17s
hbase-server in the patch failed.

300m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25881

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c2711f9d5258 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 5f0950558f

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/4/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/4/testReport/

Max. process+thread count
3454 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/4/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 54s
the patch passed

+1 :green_heart:
compile
1m 22s
the patch passed

+1 :green_heart:
javac
1m 22s
the patch passed

+1 :green_heart:
shadedjars
11m 21s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 45s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
243m  3s
hbase-server in the patch passed.

280m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/5/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25881

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 88ec729fc881 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ed4b51a6b7

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/5/testReport/

Max. process+thread count
2731 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/5/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

@virajjasani @apurtell @anoopsjohn Looking for review on this PR. Thanks

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 17s
the patch passed

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

+1 :green_heart:
shadedjars
9m  1s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
the patch passed

_ Other Tests _

-1 :x:
unit
216m 18s
hbase-server in the patch failed.

249m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25881

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 560a6c6caf48 4.15.0-162-generic #170-Ubuntu SMP Mon Oct 18 11:38:05 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / f6348d4100

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/testReport/

Max. process+thread count
3522 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3518/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.


Update New Relic credentials via command line options

Design notes
Make it possible to specify multiple New Relic account credentials as command line options.

Design notes
Previously a single NR account could be specified via
--new-relic-api-key <single api key>
--new-relic-account-id <single account ID>
Add support for sending data to multiple NR accounts, just like in the Butler tool.
--new-relic-account-name 1 or more account names>
--new-relic-api-key <1 or more api keys>
--new-relic-account-id <1 or more IDs>


Remove demographic event attributes

Addresses #96, #97. The split, merge, etc functions in the DemeGraph class now are underscored. get_demographic_events() has been changed to list_demographic_events() and returns a dictionary of lists of discrete demographic events.
Is there a better name for list_demographic_events or is that fine?

I think this is ok, but definitely could use an extra set of eyes or suggestions for API tweaks if needed @grahamgower

Looks good @apragsdale, thanks! I'm not sure about the name list_demographic_models() either. But to be honest, I don't have a better suggestion. I still have some questions about the newly underscored methods, but I'll take that over to #97.

Yeah, I'm not sure of a better name either. I'll merge what we have here for now, and if we want to update the name later we can come back to it.

Sounds good!


Make build-and-install-dotnet-interactive.ps1 work on Linux and macOS with pwsh

Make build-and-install-dotnet-interactive.ps1 work on Linux and macOS with pwsh (the cross-plat PowerShell).
$IsLinux and $IsMacOS are the built-in readonly variables defined in pwsh.

Thanks @daxian-dbw!


I want to add QR Code Generator

QR Code Generator
A simple QR Code Generator web app built with HTML, CSS, and JavaScript.

Features

Generate QR codes by entering text or URLs.
Customizable QR code size and appearance.
Download the generated QR code for easy sharing.

I know html ,css, javascript well.
please assign this issue to me under GSSoC'23

I would like to work on this issue under the GSSOC '23 Please assign me this task.


Nick: Watch trustpva.com

Nick requests the watch of the watch_keyword trustpva\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

trustpva\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Mast in Charcoal HQ


New user for under 13<= and <18

If the new user is 13 or older and less than 18.

Required to get the parent's name and email.
Parent also gets a copy of the new user email

Done


python-s2-protocol cannot be an external dependency

At the moment of releasing, we realized that PyPi doesn't allow to have external dependencies (i.e. they need to be from inside PyPi), see error trace below.
Some users experienced this as well and even have proposed PyPi to allow for external dependencies but, for security reasons, they have declined the proposal. Apparently, someone could inject malicious code into the users of the flexmeasures-client pushing code to the dependency.
I though that using a requirements.txt would bypass this but It wouldn't because in the end PyPI checks install_requires.
Given that python-s2-protocol  is not the definitive library, I would prioritize to integrate the library that we are developing with TNO.
 Notice: Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
Checking dist/flexmeasures_client-0.1.2-py3-none-any.whl: PASSED
Checking dist/flexmeasures-client-0.1.2.tar.gz: PASSED
Uploading distributions to https://upload.pypi.org/legacy/
Uploading flexmeasures_client-0.1.2-py3-none-any.whl
25l
  0% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0.0/37.4 kB • --:-- • ?
  0% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0.0/37.4 kB • --:-- • ?
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 37.4/37.4 kB • 00:00 • 56.5 MB/s
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 37.4/37.4 kB • 00:00 • 56.5 MB/s
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 37.4/37.4 kB • 00:00 • 56.5 MB/s
25hWARNING  Error during upload. Retry with the --verbose option for more details.
ERROR    HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
         Invalid value for requires_dist. Error: Can't have direct dependency:
         'python-s2-protocol @
<EMAIL_ADDRESS>

@victorgarcia98 Can this issue be closed?


Constraints on giving people triage/write permissions

Are there any basic rules of jupyterlab-contrib for giving contributors triage and/or write permissions, @krassowski @fcollonval ?
There have been some consistent contributors (both code and otherwise) to this repo that I'd like to offer increased permissions to.

No rules are enforced and I'm basically accepting any requests.
For a specific repository as in this case, maintainers should not be constrained by any organization rules. The issue template created at the organization level was initiated for two reasons:

request specific rights across all repositories
request rights on a repository archived or unmaintained

But it could be interesting to ask new contributors to create that issue in all cases in order to:

introduce themselves to the community
be invited as a member of the organization

Based on the discussion above I extended invitation to the organisation and elevated rights to one of the active contributors in this repo :) I agree that in general we should encourage new contributors to open an issue, but maybe we should adjust the template or documentation to make it more welcoming/add another template implying a lower level of commitment (some folks may want to help by regular contributions but may not want to commit to higher level of maintenance like releases and it is perfectly fine).

Thanks for inviting me!

Based on the discussion above I extended invitation to the organisation and elevated rights to one of the active contributors in this repo :) I

That's exactly who I was thinking of :) - thanks for all the contributions @firai !


Add line shuffling (beta)  #7

This works in my project (~3k lines)

Looks good, but I unfortunately can't merge it like that, as it breaks line assignments in source maps. I might work on it soon to have it properly link to the source lines.

Looks good, but I unfortunately can't merge it like that, as it breaks line assignments in source maps. I might work on it soon to have it properly link to the source lines.

Sure, take my source if you need

Closed by 7faaac7.


updating stress paths to match feature

API change check
API changes are not detected in this pull request.


1.5

Codecov Report
Patch and project coverage have no change.

Comparison is base (5275c80) 100.00% compared to head (7287b10) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@                    Coverage Diff                     @@
##           1.5-criteria-import-prep     #1095   +/-   ##
==========================================================
  Coverage                    100.00%   100.00%
==========================================================
  Files                            46        46
  Lines                          2652      2652
  Branches                        396       396
==========================================================
  Hits                           2652      2652

Flag
Coverage Δ

foundry
79.05% <ø> (ø)

production
100.00% <ø> (ø)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Breaking change in new released version v1.4.0: MongoError: unknown top level operator: $push

Hi Team
Thanks for the new release of this module.
I have however picked an issue which has caused a breaking change to occur. It seems that the $push operation is no longer supported with the new changes introduced. Within your test script you have a test which should verify this but it doesnt seem to be working in a real world scenario.
I have created a basic gist of the files and steps needed to reproduce the error. I have made use of your actual test file in the master branch and removed the unrelated sections for this issue (Only testing the $push related operation).
https://gist.github.com/BMartinos/d24dab6cb6d5b77600a5aeb990c0d40f
The error being returned when executing the reproducible test script can be seen below:
Error:  { MongoError: unknown top level operator: $push
    at MessageStream.messageHandler (/../mongoose-patch-history-test/node_modules/mongodb/lib/cmap/connection.js:266:20)
    at MessageStream.emit (events.js:198:13)
    at processIncomingData (/../mongoose-patch-history-test/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
    at MessageStream._write (/../mongoose-patch-history-test/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
    at doWrite (_stream_writable.js:415:12)
    at writeOrBuffer (_stream_writable.js:399:5)
    at MessageStream.Writable.write (_stream_writable.js:299:11)
    at Socket.ondata (_stream_readable.js:710:20)
    at Socket.emit (events.js:198:13)
    at addChunk (_stream_readable.js:288:12)
    at readableAddChunk (_stream_readable.js:269:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17) ok: 0, code: 2, codeName: 'BadValue', name: 'MongoError' }

Hey @BMartinos, thanks for the report!
Would you mind trying to install from master via npm i codepunkt/mongoose-patch-history or yarn add codepunkt/mongoose-patch-history and telling us whether this is fixed there or not?

@codepunkt great thanks! Pulling from your master branch resolved my issue. Any idea of when this might be published to npm?

I'd say as soon as I figured #63 out to work as I want it too 😅
I'm actively working on getting it resolved so hopefully this week.

Ok great thanks for the quick feedback @vinerich Will keep an eye out for when the new version is released. Thanks

@BMartinos done 👌🏾
2.0.0 was released by @codepunkt and includes the fixes for $pull, $push + new excludes and rollback without save option!

@vinerich @codepunkt Awesome! thanks for the new release and quick response :). I can confirm this fix is now also in the newly released npm update and working again for me.


Fix misplaced field in comparison_operator

The previous commit misplaced the field in comparison_operator. I hadn't caught this until I noticed that "children" was no longer marked as multiple for the relevant node in src/node_types.json

Thanks for following up!


ArangoDB 3.03 crash. Ubuntu 14.04

Hi,
Honestly I am a bit scared of my choice of arangodb right now. It is the second time I started a job that led to a database crash during the night.
I have only one machine with a very few requests per seconds and only create or update operations. I don't use Foxx only pyArango so HTTP interface.
I do however maintain simultaneous connections to the database on multiple python processes and update a collection where I have open cursors iterating.
Instead of crashing right away, it took between 6 and 12 hours after the job was started so I cannot find a reason for it.
The collection is only 30k documents.
The job is fairly simple: read a collection for objects, update each object last crawled timestamp and add in another collection the current value of the object at that particular timestamp.
One the side note, I tried an 'apt-get upgrade' and arangodb wants to update anyways even though I already have the latest version, then complains.
Setting up arangodb3 (3.0.3) ...
Upgrading database files.
2016-07-19T09:37:11Z [18775] ERROR cannot open datafile '/var/lib/arangodb3/journals/logfile-5481572.db': 'Permission denied'
2016-07-19T09:37:11Z [18775] ERROR unable to open logfile '/var/lib/arangodb3/journals/logfile-5481572.db': system error
2016-07-19T09:37:11Z [18775] FATAL could not inspect WAL logfiles: system error
dpkg: error processing package arangodb3 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 arangodb3
E: Sub-process /usr/bin/dpkg returned an error code (1)

I join all the files that I can via dropbox because of the size. Notably a file created after the crash and another after dpkg failed.
Files here

since your error message is 'Permission denied' does
chown -R arangodb:arangodb /var/lib/arangodb3

fix the issue?
Or, if maybe your filesystem is mounted read only? You can check by typing:
mount
....
/dev/sda3 on /var type ext4 (rw,relatime,data=ordered)

...
rw means Read Write, ro means Read Only

@dothebart I did sudo apt-get upgrade. But changing the permission seemed to do the trick.  My main issue is the database crash without any apparent reason.

To start the service you need root permissions:
sudo service arangodb3 start

The ArangoDB daemon itself is then in term responsible to drop root permissions during its startup phase.
In linux you need to be privileged (= be root) in order to bind lower ports (> 1024). Though ArangoDB binds port 8529 by default, its able to do all this if users want to bind privileged ports.
If you run arangod as root without the proper parameters, it won't drop root privileges, and thus create new files with root:root permissions.
It would be interesting to understand which circumstances lead to the state of the permission problems.
Did you start arangod by hand as described above?

Yes, I did.
I used to run arangodb either by the service or by hand with: sudo arangod. Maybe because of this root user, when the database grows it creates new journal files with the wrong permissions. Then when they are accessed it makes the database crash?
Have you been able to read the log files I joined in my first post?

Its not a crash. It simply panics during startup because of it can't access all of its required resources.

If you call it like sudo -u arangodb /usr/sbin/arangod you shouldn't see these issues.

I am not sure we understand each other here. The whole startup thing and apt-upgrade was a side issue maybe related to the real issue:
Arangodb crashed unexpectedly after 6 hours of work.
Quoting my original post:

It is the second time I started a job that led to a database crash during the night.
I have only one machine with a very few requests per seconds and only create or update operations. I don't use Foxx only pyArango so HTTP interface.

I do however maintain simultaneous connections to the database on multiple python processes and update a collection where I have open cursors iterating.
Instead of crashing right away, it took between 6 and 12 hours after the job was started so I cannot find a reason for it.  The collection is only 30k documents.

The job is fairly simple: read a collection for objects, update each object last crawled timestamp and add in another collection the current value of the object at that particular timestamp.

Ok, I thought the log lines were related.
I've been looking at pyArango the last days; It seems to not re-use connections (at least in current devel)
If you run
 netstat -alpnt | grep CLOSE_WAIT

Do you see many lines with your python client?

My code is running on the same machine.
Only two lines:
# Ipython notebook with port forwarding
tcp        0      0 xxx.xxx.xxx.86:8889     xxx.xxx.xxx.2:51959     CLOSE_WAIT  20887/python
# arangodb web interface port forwarding
tcp        1      0 <IP_ADDRESS>:53675         <IP_ADDRESS>:8529          CLOSE_WAIT  20887/python

ok, so at least ATM this doesn't happen to you. Can you share the AQL you're running on your database?

All the requests are contained in one file here
Mainly I have multiple processes running the query l. 392 and 396
'FOR p in col_name FILTER (p.last_scraped < 'timestamp' AND p.priority > 0) SORT p.last_scraped ASC, p.pirority DESC RETURN p'

While iterating through the results I call add_full_video l.364 and add_full_playlist l. 345 that are basic CREATE or UPDATE operations.
These functions update the database if necessary and add the timeseries value is a dedicated collection.
Tell me if you need more precision.

Update: I started a the same job yesterday, the DB crashed again during the night.

Hm, the corefile only contains bogus information. I will try to reproduce this.

can you share a sample data set so the queries run properly?

@dothebart I found the issue. My code was leaking and the machine was out of memory during the night enhance making the system crash. Maybe it would be nice to log this case as it may happen to others in the future. Thanks for the support.

The answer

Its not a crash. It simply panics during startup because of it can't access all of its required resources.

If you call it like sudo -u arangodb /usr/sbin/arangod you shouldn't see these issues.

Should be much more documented, I spent more than 24 hours when I tried to tell arangodb to create database on mounted directory, it always created it as a root and then arangodb user didn't have permissions to write to that database directory.  if I didn't start arangodb as root it crashed on no permissions to change uid\gid
anyway sudo -u arangodb after mounting with permissions does the job


Create Snippets for Basic Functionality

#2 @patrickdemers6
Implements new snippets:

br
bl
addi
subi

And Refactors old snippets to be more intuitive

Thanks! I will create a new release soon with these changes.

Sounds good!
Obter o Outlook para iOShttps://aka.ms/o0ukef

De: Patrick Demers @.>
Enviado: Friday, January 13, 2023 3:07:34 PM
Para: patrickdemers6/legv8-vscode @.>
Cc: JoaoLira-br @.>; Author @.>
Assunto: Re: [patrickdemers6/legv8-vscode] Create Snippets for Basic Functionality (PR #3)
Thanks! I will create a new release soon with these changes.
—
Reply to this email directly, view it on GitHubhttps://github.com/patrickdemers6/legv8-vscode/pull/3#issuecomment-1382387256, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZM2N4JIIKE3J62AIFVMNQ3WSG7ZNANCNFSM6AAAAAASMXOPLI.
You are receiving this because you authored the thread.Message ID: @.***>


Updated Dockerfile for smaller images

Use node:alpine for smaller base
Reworked commands to increase use of build cache
Install only production dependencies (don't need test and
electron dependencies when running the app)

And just an FYI... this will update images from 391MB compressed (the latest on Docker Hub) to 44MB compressed. 👍


Use a dynamic launch config for more kernels

launch_config could probably be generalized with an arch argument to work on both GPUs and CPUs, but I'll leave that to you guys.

Also splits the large kernel in two. Might have to revert that if we get a good shmem solution instead.


Temperatur/Humidity +/- Offset

Hello,
Is it possible to offset temperature or humidity in the plugin like it can be done in the Govee App?

Closing this as a bit overwhelmed with issues.
Please update to the beta version of the plugin, and if you are still having issues, do reopen this ticket!
Thanks and apologies if closing prematurely.


Update tutorials to match with the new way of running experiments

Pull request information

Status: ready to merge
Kind of changes: documentation
Related PR or issue: #720

Description

Update tutorials to match with the new way of running experiments. This is one of the tasks of #720 that was excluded from the PR as that PR was getting huge.

Pull Request Test Coverage Report for Build 4922

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.77%

Totals

Change from base Build 4916:
0.0%

Covered Lines:
8547

Relevant Lines:
9521

💛  - Coveralls

@AboudyKreidieh can you please check my last commit and confirm it is correct?


component slot v-show @click not working

hello, i have this probles
my main component
<template>

     <wizard>
        <button @click="doThis">click</button>

show this

   .......
</template>


Kata Containers 1.1.1

Stable 1.1.1 candidate

d3dfdaa versions: Update CRI-O supported version
6374e40 main: Pass runtime CLI command to vc logger
35a9430 virtconainers: rollback the NetNs when createNetwork failed
3bbcdbc virtcontainers: add rollback to remove sandbox network
85b1627 virtcontainers: fix kata-agent fail to start
01906ee virtcontainers: add qemu process rollback
bd5c8fe virtcontainers: add kata-proxy rollback
a4de4e6 vc: cni: add SPDX license to OWNERS file
4021697 cli: Make message of using initrd OR rootfs clearer
a6668af network: Error out when host-networking is requested
7b5f920 virtcontainers: ppc64le: Add nvdimm to defaultQemuMachineOption
f9446e5 kernel: Remove initcall_debug boot option
21ae323 codecov: remove codecov.yml
e4ccf03 agent: check: Increase timeout check request.
28b299f kata-agent: Improve error message.
7ca24d6 cli: add AMD support to kata-check
3438a11 codecov: Explicitly disable codecov/patch coverage
b2d9d95 sandbox: change container slice to a map
a3b11df cli: tests: Clarify who cleans up tmpdir
9fac082 cli: tests: remove the tmpdir to the config.json
b0e5614 cli: update_test: defer remove tmpfile
a712155 kata_agent: print request details
8c5be51 makefile: update PREFIX to remove redundant slash
8a1469b kata-env: tests: add JSON out/in verify test
ceac6fd kata-env: Do not leave temp files on test
89e22e5 kata-env: Fix test cases for kata-env JSON
b21646a kata-env: Add ability to output as JSON
b4595ae ci: no-exit: Do not run no-exit check on test files
b71cae0 ci: no-exit: Allow path override for os.Exit check
1b23e15 ci: no-exit: Skip check if no files to check
e640655 ci: no-exit: Document and echo what the check is
9868cf2 api: To stop its monitor after a sandbox paused
d10b1d8 virtcontainers: Set ppc64le maxmem depending on qemu version
3dda260 tests: Refactor CC proxy test for Kata
61607e7 ci: reconstructure image-type and initrd for architecture-independant
9774c2a logging: Reset external loggers when cid+sid available
371dc14 logging: Add function to handle external loggers
fdf1312 create: Remove redundant logging code
c4658c3 api: To watch the vm console in FetchSandbox api

LGTM. I've restarted travis (which failed due to network connectivity issue). Once that passes, we can merge this.

CI green. Need one more review though.


Fixed miniaudio on macos

It's an entitlements issue that is solved with a #define for miniaudio: https://github.com/mackron/miniaudio/issues/203
This also lets us simplify the soloud xmake.lua file somewhat, since it inherits the linker flags.

Is there anything I can do to get this pull request approved?

Is there anything I can do to get this pull request approved?

iphoneos ci failed

Before I try to fix it, are we sure it used to work?


Create unit test for pkg/time/time.go

What this PR does / why we need it: Resolves openebs/litmus#300 by adding tests for pkg/time/time.go
Which issue this PR fixes: openebs/litmus#300
Special notes for your reviewer:
I had to provide a way to replace calls to actual time.Sleep to test longer duration values.

Looks like build environment is broken.
make: gometalinter: Command not found

My code has nothing to do with gometalinter.

The travis build has been fixed. Once we done with/agree to the changes, should be ok to merge!


Run thru OWASP top 10 project

via @charleshuang80 : https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project

I'm gonna backlog this -- we've gotten a lot of this out of the way, and I think we should revisit when we get closer to release 2.

No clear action to take here after reviewing the doc. Closing.


bugwarrior: update homepage

bugwarrior has been migrated to GothenburgBitFactory
Description of changes
updated homepage URL, see https://github.com/GothenburgBitFactory/bugwarrior/issues/812#issuecomment-1848436609
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

LGTM. Don't think it matters but there's a missing space after : in the commit message

Added space to commit msg and PR title.


WIP: fix(code): better error code returning in confirmation

We need a better flow to code verification to tackle this.


Positive deltas are not accepted in many character sheet fields

Foundry Version: 10.285
DnD5e Version: 2.0.2
Modules: None
If I enter "+X" in a currency box on the inventory panel of the Actor sheet then that currency is set to X. I expected X to be added to the current value. If I enter "-X" instead then X is subtracted from the current value. Using no prefix sets the value to whatever I entered, as expected.
UPDATE: This affects more than just the currency fields (see below).

Note this is also the case for other places where deltas should be accepted, like XP and HP.

I remember something about some <input> fields changing from input type string to number. Could that be it? Could the fields now only be accepting numbers, so when they're submitted they're changed from +10 as a string to just 10 the number?

So I did some testing. What I found, all testing done on the currency fields.

This bug only happens when you add a positive delta to a non zero field.

If you manually go into the HTML of foundry and change the input of the file to text instead of number. The bug is not present.

If you manually set the currency as text before run, neither deltas work.

The code for handling delta's simply is not running when the bug is present.

The code for activating listeners, (around line 600 in base-sheet.mjs) does not run when bug is present.

This is where my investigation into the bug currently is stuck at, I can't follow the data up past the listener activation failure. I will provide more info when I discover it.

Looks like this is only an issue in Chrome, it works fine in Firefox. It seems like Chrome is removing the leading plus from the value before we get a chance to handle it (e.g. "+15" turns into "15") while Firefox leaves it alone.

Looks like this is only an issue in Chrome, it works fine in Firefox. It seems like Chrome is removing the leading plus from the value before we get a chance to handle it (e.g. "+15" turns into "15") while Firefox leaves it alone.

I can confirm this, I was able to get a proof of concept working where I changed the input type to text. Then changed the delta function to handle this by parsing to float in the addition line, ~line 700 base-sheet.mjs.
input.value = parseFloat(foundry.utils.getProperty(this.actor, input.name)) + delta;
Notably this breaks a bunch of other things, so I can't just do this then push a fix. Specifically it's breaking the CSS right now, which I'm working on.

I am about 90% done fixing this. Will get the code up soon.


Implement Azure Identity Authentication for Azure Transport

Resubmission of PR #1042 as its original changeset was lost
Summary
The purpose of this pull-request is to introduce support within the Azure Transport for more secure authentication vectors. Specifically, it allows the use of a Service Principal or Managed Identity as opposed to using the Access Key.
There are inherit risks in utilizing the access key of a storage account, namely that it grants whoever has access to the key full privileged rights to that account. Microsoft generally recommends that you do not use this key for everyday access and that you should manage access through other means such as the ones noted above so that it can be properly controlled and audited through RBAC.
Direct Dependency Changes
[+] github.com/Azure/azure-sdk-for-go/sdk/azcore
[+] github.com/Azure/azure-sdk-for-go/azidentity
[+] github.com/Azure/azure-sdk-for-go/azblob
[-] github.com/Azure/azure-storage-blob-go/azblob
Authentication
Every effort has been made to ensure that the original authentication pathway was retained as to avoid creating a breaking change scenario. If the environment variable IMGPROXY_ABS_KEY is set, the transport will continue to authenticate via NewSharedKeyCredential and not attempt any other path.
For users that wish to use one of the newer authentication methods, they can simply unset the IMGPROXY_ABS_KEY variable and the transport attempt to authenticate via NewDefaultAzureCredential. For authentication via a Service Principal, the following environment variables must be set:
Service principal with secret

AZURE_CLIENT_ID: Specifies the client ID for your application registration
AZURE_TENANT_ID: Specifies the tenant ID for your application registration
AZURE_CLIENT_SECRET: Specifies the client secret for your application registration.

Service principal with certificate

AZURE_CLIENT_ID: Specifies the client ID for your application registration
AZURE_TENANT_ID: Specifies the tenant ID for your application registration
AZURE_CLIENT_CERTIFICATE_PATH: Specifies the path to a PFX or PEM-encoded certificate including private key
AZURE_CLIENT_CERTIFICATE_PASSWORD: (optional) the password protecting the certificate file (PFX (PKCS12))
AZURE_CLIENT_CERTIFICATE_CHAIN: (optional) send certificate chain in x5c header to support subject name / issuer-based authentication

Hi @xaevik! Please add support for ranged requests and fix the things I commented

I'm experiencing a road block in this implementation. req.Header.Get("Range") is always nil even when passing the Range header via cURL. Any input on this would be great so that I can do appropriate end-to-end testing.

Looks good now 👍 Thanks for your contribution!


Your configuration files are not serializable

config/sentry.php
<?php

use Sentry\Event;

return [

    'dsn' => env('SENTRY_LARAVEL_DSN', env('SENTRY_DSN')),

    'before_send' => function (Event $event): ?Event {
        // literally anything
        return $event;
     },
];

php artisan config:cache

Yes, that is because you are using a closure in your configuration file which is not allowed :)
This is a Laravel limitation (and a good one because serializing closures is a hack).
You can circumvent this by doing the following:
<?php

namespace App\Exceptions;

use Sentry\Event;

class Sentry
{
    public static function before(Event $event): ?Event
    {
        // literally anything

        return $event;
    }
}

Which you can set in your configuration like:
<?php
return [

    'dsn' => env('SENTRY_LARAVEL_DSN', env('SENTRY_DSN')),

    'before_send' => [App\Exceptions\Sentry::class, 'before'],

];

This works because we allow PHP callables to be passed for all callbacks.

Because I have not heard back I am going to assume my directions were sufficient and the problem was solved, closing this issue, feel free to reopen or open a new one if there are still unsolved issues.

Yes, that is because you are using a closure in your configuration file which is not allowed :)
This is a Laravel limitation (and a good one because serializing closures is a hack).
You can get around this limitation by doing the following:
<?php

namespace App\Exceptions;

use Sentry\Event;

class Sentry
{
    public static function before(Event $event): ?Event
    {
        // literally anything

        return $event;
    }
}

Which you can set in your configuration like:
<?php

return [

    'dsn' => env('SENTRY_LARAVEL_DSN', env('SENTRY_DSN')),

    'before_send' => [App\Exceptions\Sentry::class, 'before'],

];

This works because we allow PHP callables to be passed for all callbacks.

doing the following on which file?

doing the following on which file?

config/sentry.php
It's not explicitly documented as the config options are passed through directly to Sentry. So when you read something like https://docs.sentry.io/platforms/php/#tagging-events , it's basically the content of config/sentry.php passed internally to this init.

doing the following on which file?

config/sentry.php
It's not explicitly documented as the config options are passed through directly to Sentry. So when you read something like https://docs.sentry.io/platforms/php/#tagging-events , it's basically the content of config/sentry.php passed internally to this init.

i don't have that file in config folder

Seems to me you didn't follow the installation guide then, see e.g. https://sentry.io/for/laravel/
Especially the last step ("create the sentry configuration")


Big difference in examples log for Box ddp solver

When comparing the logs to make sure that modifications don't produce a divergence in the output of DDP, it seems normal to expect some difference in numerical outputs because of floating point operations. However, when comparing the logs for the current devel in my system, there is a big difference in the cost outputs of the BoxDDP, which should not be there.
My system is Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz, and I have Ubuntu 16.04.6 LTS and all the system dependencies that come with it.
This PR is not to be merged, this is simply to discuss this issue and to provide a diff between the two computations.

@proyan I am not sure if this might be connected, but I merged recently a PR that solves an issue, in quadruped examples, reported by @wxmerkt.
This is the PR:
https://github.com/loco-3d/crocoddyl/pull/694
So my question is did you use this commit when you generated these log files?

@proyan I am not sure if this might be connected, but I merged recently a PR that solves an issue, in quadruped examples, reported by @wxmerkt.
This is the PR:
#694
So my question is did you use this commit when you generated these log files?

Yes, this is the logs from the commit fc20ca74b1674c88bf83cb1c4fa2d05ab85d5e42

@proyan Are these diffs with multi-threading? Can you try to run the same with a clean build with a single thread build and check the logs again? I had a similar occurrence back in autumn when using multi-threading, however, I thought you had it fixed back then?

@wxmerkt These logs are with the standard cmake install that we have with crocoddyl (i.e without Multi-threading and without vectorization)

Okay, thank you for the clarification. That's a good insight

@proyan I don't know if useful, but could you report the version of examples-robot-data, pinocchio, eigen(py) and numpy?

I'll close this PR since this problem has already been documented in separate issues.


Architecture problem (Segmentation fault error or cannot execute binary file : Exec format error)

I cannot run my programs on different platforms. For example I cannot run a program on an x86_64 Linux if the program has been created on an i686 Linux platform. Besides if I run "pkg" command without any commands, it creates 3 files for each 3 platform (macos, win, linux) but again I cannot run them on different platforms. I get a "Segmentation Fault" error or a "cannot execute binary file : Exec format." error.
I converted my NodeJS app into an exe with PKG on MacOS (x64). I get a "Segmentation fault" on a x86_64 Linux (CentOS) and "cannot execute binary file : Exec format error" on a i686 Ubuntu.

It is not possible to compile a binary that runs cross platform.

Segmentation fault had happened to me after I used FTP to deploy binaries on server due to ASCII transfer mode. I'd recommend not to use FTP for apps deploying to prevent any possibility of that kind of error.


Fix merge button detection

GitHub seems to have changed their CSS a bit, which broke this extension.

@Fryguy Perfect!

We shipped v1.0.6 :tada:


Registration issue

This issue was created as a membership registration magnet. When a user that is not necessarily a member leaves a comment, it would be possible from that point on to assign him issues and mention him in discussions.

Test 1
housssec is not a member of this repository.

housssec could not be mentionned with @
housssec could not be assigned this issue

Test 2
housssec is asked to leave a comment

Test 2
housssec is asked to leave a comment

My comment is: I can work on this issue

Test 2
housssec is asked to leave a comment

My comment is: I can work on this issue

Now housssec appears in the list of participants

Test 2
housssec is asked to leave a comment

My comment is: I can work on this issue (this is the comment of housssec)

Now

housssec appears in the list of participants
housssec could be mentionned. A refresh might be required and may be only in a new comment

@housssec I can now mention you
@housssec I can now assign the issue to you


More clear Statement of Need

From https://joss.readthedocs.io/en/latest/submitting.html#what-should-my-paper-contain
A summary describing the high-level functionality and purpose of the software for a diverse, non-specialist audience.

A clear Statement of Need that illustrates the research purpose of the software.

In my opinion, the paper does not fully convey WHY this package is needed. Is this just another simulation package?
cc https://github.com/openjournals/joss-reviews/issues/2120

I will add here some parts of the text that we have added/modified to make this clearer:
“Computational mechanical models aim to simulate the behavior of such mechanical systems. These models are used to support research and decision making. To this purpose, we present ROSS, an open source library written in Python for rotordynamic analysis.”
“To our knowledge, in the rotordynamic field, ROSS is the first software being developed using the open source concept, with the code being fully available on code hosting platforms, issues tracked online, clear license and possibility of direct contribution.”
“Developing the software using Python and its scientific ecosystem enables the user to also make use of this ecosystem, making it easier to run rotordynamics analysis. It is also easier to integrate the code into other programs, since we only use open source packages and do not depend on proprietary commercial platforms.”

@raphaeltimbo :

Please link the PR/commit that adds these statements
ROSS is the first software being developed using the open source concept, how is that novel compared to commercial finite element softwares that have a rotordynamic module[s]?
While I personally love Python for its general ease of use, I'm not convinced by the statement Developing the software using Python and its scientific ecosystem enables the user to also make use of this ecosystem, making it easier to run rotordynamics analysis.

@raphaeltimbo :

Please link the PR/commit that adds these statements

Link to commit: def64b5462d227cc902cf671942101a760179270

ROSS is the first software being developed using the open source concept, how is that novel compared to commercial finite element softwares that have a rotordynamic module[s]?

As discussed on #494, we believe that having an open source alternative to commercial rotordynamics softwares presents benefits to research in this area.

While I personally love Python for its general ease of use, I'm not convinced by the statement Developing the software using Python and its scientific ecosystem enables the user to also make use of this ecosystem, making it easier to run rotordynamics analysis.

My point in this statement is that with some of these rotordynamic commercial softwares you are  'locked' on their environment, interacting with the software only through a GUI, which makes it harder (impossible sometimes) to automate analysis, extract results to use in other tools, present results in different ways, run analysis with different settings and so on.
When you have an open source software developed in Python it is much easier to do those tasks since you have easy access to scientific tools, plotting tools, etc., all within the same environment.
Please, let me know if this makes the point clearer and if you want we can add it to the paper.

@raphaeltimbo yes, definitely add that to the paper. [...] 'locked' on their environment, interacting with the software only through a GUI, which makes it harder (impossible sometimes) to automate analysis, [...] is the key point that satisfies both of my above concerns

@nnadeau , I have added that here: 565aee5

to automate analysis, To our knowledge, in
typo: period instead of comma

to automate analysis, To our knowledge, in
typo: period instead of comma

Fixed that on https://github.com/ross-rotordynamics/ross/pull/517/commits/75c93b42c24ae4eea27411349f5b517fb138b5c3

Hi there @nnadeau !
I forgot to tag you so I don't know if you received a notification for this.
Just wanted to let you know that I have fixed the typo.


reskusic_190219_232034.474

Type: Incomplete
Summary:
Added information for for OpenSSL 1.0.2o
Details:
The license information was missing for this component.
Resolution:
The license information is here, from the git repository: https://github.com/openssl/openssl/blob/3ce7bc40a3c48da1c96c2d04c10045bd797c6aa3/LICENSE
NOTE: The second license (the "Original SSLeay License") does not appear to be in the ClearlyDefined license catalog.
Affected definitions:

openssl 3ce7bc40a3c48da1c96c2d04c10045bd797c6aa3

The OpenSSL license includes the SSLeay license in its text.
https://www.openssl.org/source/license.txt
https://spdx.org/licenses/OpenSSL.html


[FEATURE] map_values() could be improved

Category:
Description
Can be done in a single line.
Current Snippet Behavior

Current code:
def map_values(obj, fn):
	ret = {}
	for key in obj.keys():
		ret[key] = fn(obj[key])
	return ret

Possible Solution

Suggested replacement:
def map_values(obj, fn):
	return {key: fn(obj[key]) for key in obj}

Resolved in #102


Full JUNIT4 & Embedded JPL fixes

Fixes a few corner cases with JUNIT4, including dependency with hamcrest (fixes post and fixes #40)
Fixes call to SWI in embedded application so that it always sets up the search paths for libraries; resolved #32
Clean up some tests
Integrate old tests and deleted the ones that were not relevant anymore
Refactor tests to make them easily extensible

Thanks!  passes for me.


Misleading Links

Describe the bug 🐞
Attempting “copy link” for any Endpoint Root URL in the RPC Providers page copies the wrong URL.
Expected behavior
The Endpoint URL should be copied.
Meta
https://github.com/near/docs/pull/1110 introduced a patch that routed these links back to the page itself, in order to avoid having broken links in CI.
However, these links aren't broken, they're just not your typical webpage.
As an alternative, we could use inline code blocks.

I think the alternative of using code blocks could be useful, something like:
http://some.rpc.serv

Unknown what the alternative would be for this:
https://github.com/near/docs/blob/672d39f6200495f46fdd3988ce374a14a8968425/docs/1.concepts/basics/networks.md?plain=1#L19

those 2 URLs actually work and don't reply with a 404, so I think they could be linked properly.

Yeah, I'd advocate for directly linking it. Wasn't sure why we went the other way in #1110.


Edit function extractor to only extract required map definitions from phase 1

is this issue related to fixing the present problem occuring when trying to load cilium functions ?

Done..


clearBeforeRender has no effect?

Version
Phaser: 3.52.0 (latest), Chrome:  87.0.4280.141 (latest)
Description
I'm possibly using clearBeforeRender wrong, but it seems as if things generally render normally despite setting clearBeforeRender: false. That is to say, they wipe the previous render and redraw on update rather than leaving the previous render stained on the screen.
Example Test Code
This can be happily pasted into the Phaser 3 Sandbox:
class Brain extends Phaser.GameObjects.Sprite {
  constructor(scene, x, y) {
    super(scene, x, y);
    this.setTexture("brain");
    this.setPosition(x, y);
  }
  preUpdate(time, delta) {
    super.preUpdate(time, delta);
    this.rotation += 0.01;
  }
}
var config = {
  type: Phaser.AUTO,
  parent: "phaser-example",
  scene: {
    preload: preload,
    create: create,
    update: update,
  },
  render: {
    clearBeforeRender: false,
  },
};
var game = new Phaser.Game(config);
function preload() {
  this.load.image("brain", "assets/sprites/brain.png");
}
function create() {
  // Graphics are fine
  this.graphics = this.add.graphics({ lineStyle: { color: 0x00ff00 } });
  this.circle = new Phaser.Geom.Circle(400, 500, 20);

  // ! Sprites seem to ignore clearBeforeRender: false
  this.add.existing(new Brain(this, 400, 250));

  // ! Particles seem to ignore clearBeforeRender: false
  const particles = this.add.particles("brain");
  particles.createEmitter({
    x: 110,
    y: 110,
    speed: 100,
    alpha: { start: 1.0, end: 0 },
  });
}
function update() {
  this.circle.radius += 5;
  this.graphics.strokeCircleShape(this.circle);
}

Additional Information
I know it's achievable with PIXI, at least within an autoDetectRenderer instance so I can't imagine why this isn't working.

@gammafp It's the same with canvas or WebGL

@gammafp It's the same with canvas or WebGL

It won't be visible unless the game config is transparent with no background colour set.

It won't be visible unless the game config is transparent with no background colour set.

No joy, I've added transparent: true to render but it didn't help. Also is it possible to have multiple renderers?

No joy, I've added transparent: true to render but it didn't help. Also is it possible to have multiple renderers?

No, you can't have multiple renderers.
clearBeforeRender is pointless in v3. Probably sensible to just remove the config property entirely.

No, you can't have multiple renderers.
clearBeforeRender is pointless in v3. Probably sensible to just remove the config property entirely.

Oh really? Bugger.
Was hoping to have a bloodstain kinda layer like a previous project https://entozoon.itch.io/tankblade or a Spheres of Chaos kinda thing going on.
Thank you though, @photonstorm , helpful as ever!

Oh really? Bugger.
Was hoping to have a bloodstain kinda layer like a previous project https://entozoon.itch.io/tankblade or a Spheres of Chaos kinda thing going on.
Thank you though, @photonstorm , helpful as ever!

That's not really how I would do a blood stain effect personally. Would much rather draw the stains to a Render Texture. Then I'd have more control over fading this out over time and not also having my main sprites, UI, etc all drawn to it as well.

That's not really how I would do a blood stain effect personally. Would much rather draw the stains to a Render Texture. Then I'd have more control over fading this out over time and not also having my main sprites, UI, etc all drawn to it as well.

This is now possible in the master branch by setting:
    clearBeforeRender: false,
    preserveDrawingBuffer: true


gapi.auth.authorized with response_type='id_token' broken

From<EMAIL_ADDRESS>on January 11, 2014 04:03:51
What steps will reproduce the problem? If possible, provide a live demo of the issue. 1. open http://jsbin.com/uweBAyo/1 2. click on authorize
3. The following error message is shown in the popup: Parameter not allowed for this message type: include_granted_scopes
This only happens for calls to gapi.auth.authorize with response_type set to 'id_token', which worked fine until recently. What is the expected output? What do you see instead? Authorization should succeed. What version of the product are you using? On what operating system? Irrelevant Please provide any additional information below. It works as expected when include_granted_scopes is removed the request parameters (for example by executing delete Sv.params.include_granted_scopes  before Sv.callback = ... in the uglified client js client)
Original issue: http://code.google.com/p/google-api-javascript-client/issues/detail?id=123

Just ran into this issue. Setting response_type: 'token id_token' fixed it for me.


Is it instagram blocked the graphql api?

I am having trouble fetching comments for an Instagram post. Has anyone encountered and solved this issue?
"name": "QueryReturnedBadRequestException",
"message": "400 Bad Request - "fail" status, message "feedback_required" when accessing https://www.instagram.com/graphql/query?query_hash=2b0673e0dc4580674a88d426fe00ea90&variables={"shortcode"%3A"DC32CXfy4aK"}",
Output of the URL:
{'errors': [{'message': 'execution error', 'severity': 'CRITICAL'}],
'status': 'ok'}

incomplete bug report

no version information
no command line

instaloader version 4.14

I try get reels (profile.get_reels()), but get this errors:
  File "/Users/me/PycharmProjects/project/.venv/lib/python3.12/site-packages/instaloader/instaloadercontext.py", line 468, in get_json
    raise ConnectionException(error_string) from err
instaloader.exceptions.ConnectionException: JSON Query to graphql/query: 401 Unauthorized - "fail" status, message "Please wait a few minutes before you try again." when accessing https://www.instagram.com/graphql/query?variables=%7B%22data%22%3A%7B%22page_size%22%3A12%2C%22include_feed_video%22%3Atrue%2C%22target_user_id%22%3A%221501916106%22%7D%2C%22__relay_internal__pv__PolarisFeedShareMenurelayprovider%22%3Afalse%7D&doc_id=7845543455542541&server_timestamps=true

I waited a few minutes, hours and tried again, but have the same error. Im confident that I authorized because I can get some info from profile instance like biography.
I use:
MacBook (Intel), MacOS 14.5
Instaloader 4.14
Python 3.12


Stop Using Ancestors

Hi, I have a project using your awesome module, but I don't want to use the ancestor/descendant thing, its not usefull for my case and I do not want to create a sql table for that. When I try to add a new row I get this error:

Table 'database.tableancestors' doesn't exist

I don't want to create and use this functionality, is there a way to turn it off?

Hi. I'm afraid I don't really understand. You say "I don't want to use the ancestor/descendant thing" but that is the whole essence of this package! If you don't want it, you'd have no use for this package.
What I mean by this is: The ancestors table is what allows you to fetch an entire nested tree in one query. It tracks the ancestry of every node in the tree, so you can make queries which basically say "give me all the nodes in the tree below this one, and structure it as a tree". The first part of that is equivalent to "find all the nodes which are ancestors of this one".
So to do what this package does, it requires the data in the ancestors table. If you delete the ancestors table, it will break.
I hope that makes sense.

Oh, Ok, my fault then. Sorry to bother, and thank you very much for the help!


can't pretty print nested [][]T

Zig ver: 0.12.0-dev.3533+e5d900268
Minimal reproduction:
try pretty.print(std.heap.page_allocator, [0][0]u8{}, .{});

 I'll come back to it when I reach my laptop.

First, thanks for the first pull request. Essentially, you put the comptime in front of the if and that solved the problem. However, you introduced another one. Here is your commit:
.Array => {
                // String
                comptime if (opt.str_is_u8 and typeIsArrayString(T)) {
                     try self.writeValueString(&val, c);
                     return;
                };

This comptime forces the body to be also comptime known, which will make self.something impossible to evaluate (self will be inevitably a non const pointer, and so a runtime thing). The question is, however, why then the [0][0]u8{} was successfully printed? It is simply because originally, the condition was assumed runtime and zig was forced check this branch (body) for the subject of type mismatch. And there was indeed potential mismatch, the error of which you posted above. But when I wrote the code, I assumed the condition is comptime because opt is comptime by definition and typeIsArrayString(T) shoud be comptime, as it just has a single type argument, which is inherently comptime. However, as it turns out, zig sees the function call and immediately assumes it's gonna be the runtime if otherwise not specified. Thus, what we actually need to quick-fix it is to put comptime just in front of that function (to localize comptime-ness within the condition):
.Array => {
                // String
                if (opt.str_is_u8 and comptime typeIsArrayString(T)) {
                     try self.writeValueString(&val, c);
                     return;
                }

Another thing that I do appreciate is the style change you made. You put the return right after the try, and got rid of the else for the next block, which I consistently did in other parts of the code. So thank you again!
TL;DR I'll do this small fix, change the typeIsArrayString (it is a bit too restrictive), test, commit and push. After, I'll close your pull request with the reference to that commit.


Add support for frozen objects

I think this exactly matches the API and semantics of the Java implementation outside of spelling differences, so see the PR there for information on design decisions.

@tgoyne ,
How does freezing affect one-to-many relationships?
For example, if I have:
typealias ID = String

class User: Object {
    @objc dynamic var ID: ID!
    let friends = List<User>()

    // For Realm
    override class func primaryKey() -> String? {
        return "ID"
    }

    convenience required init(ID: ID) {
        self.init()
        self.ID = ID
    }
}

What does the following return?
// user is of type User, and let's assume user's friend list is not empty
user.freeze().friends.first?.isFrozen

All objects obtained from a frozen object are themselves frozen as well.

All objects obtained from a frozen object are themselves frozen as well.

Yup, I just experimented and that seems to be the case.
@tgoyne , Now, for efficiency, are the objects obtained from a frozen object lazy generated, or is it the case that when I freeze even a single object, I could be making an expensive copy of the reachable object graph from the object I froze?
I hope it is the former.

Everything is lazy. Frozen objects work the same as regular objects and read data from the file as needed on a per-property basis, with the only difference being that they never update the version of the data which they read. The fact that it's lazy is sort of an implementation detail (there shouldn't be any observable effects from it being lazy other than that freezing objects doesn't take a long time and a bunch of memory), but also isn't in that it's the main reason to use the feature rather than manually copying objects out of the Realm.

So in other words, if I do the following:
let frozenUser = user.freeze()

I could get different values for frozenUser.friends.count depending on when I query it (due to the fact that the db may have changed in between queries of the friend count)

The entire object graph is frozen and you will not see different values after writes are made.

The entire object graph is frozen and you will not see different values after writes are made.

So I will always see the same value for frozenUser.friends.count, regardless of how I make writes to the actual db afterwards?

Yes.


Last exchange context of every PASE/CASE exchange is leaked

Problem
Due to the fact that message 3 of every PASE/CASE exchange is currently designed as imbalanced (it only gets a response if there is an error) the active context allocated by the exchange manager is never released. To see it, add the following to ExchangeManager::OnMessageReceived.
mContextPool.ForEachActiveObject([&](auto * ec) {
printf("---active %04x %04x 0x%llx 0x%x\n", ec->GetExchangeId(), ec->GetSecureSession().GetAdminId(),
ec->GetSecureSession().GetPeerNodeId(), ec->GetSecureSession().GetPeerKeyId());
return true;
});
Filtered output during and after commissioning:
---active acd9 ffff 0xffffffffffffffff 0x0
---active acd9 ffff 0xffffffffffffffff 0x0
---active acd9 ffff 0xffffffffffffffff 0x0
---active acda 0000 0xbc5c01 0x0
---active acd9 ffff 0xffffffffffffffff 0x0
---active acdb 0000 0xbc5c01 0x0
---active acd9 ffff 0xffffffffffffffff 0x0
---active acdc 0000 0xbc5c01 0x0
---active acd9 ffff 0xffffffffffffffff 0x0
---active acdd 0000 0xbc5c01 0x0
The context with exchangeid acd9 is stuck indefinitely in active state and never released.
Suggested solution
Fix PASE/CASE so message 3 (or more generally every request) always gets a response, whether there is an error or not. In addition ensure that exchange contexts do not get stuck indefinitely.

yep, we also detect this issue in cirque test.
CHIP:EM: Sending Standalone Ack for MsgId:00000006
CHIP:IN: Secure message was encrypted: Msg ID 9
CHIP:IN: Sending msg from 0x000000000001b669 to 0x0000000000bc5c01 at utc time: 742640 msec
CHIP:IN: Sending secure msg on generic transport
CHIP:IN: Secure msg send status No Error
CHIP:EM: Flushed pending ack for MsgId:00000006
CHIP:DMG: Client[0] moving to [INIT]
Read Response: 3/3(100.00%) time=0.008ms
CHIP:DMG: ICR moving to [Uninitiali]
CHIP:DMG: Client[0] moving to [UNINIT]
CHIP:DMG: Client[0] moving to [UNINIT]
CHIP:DMG: IM RH moving to [Uninitialized]
chip-im-initiator: ../../../../../src/messaging/ExchangeMgr.cpp:104: CHIP_ERROR chip::Messaging::ExchangeManager::Shutdown(): Assertion `ec.GetReferenceCount() == 0' faile
Not sure how we guarantee the ec are deterministically released after this change
we are continuing to trace down these issues...not sure what is the right mechanism to make cirque back to work

Note https://github.com/CHIP-Specifications/connectedhomeip-spec/issues/2542

Thank, I'll try to fix it.

fixed


➕ add pyyaml type stub dependency

Generated summary (powered by Graphite)

TL;DR
This pull request adds types-PyYAML as a new dependency to the project. This is reflected in the changes made to .pre-commit-config.yaml, poetry.lock, and pyproject.toml files.
What changed

In .pre-commit-config.yaml, types-PyYAML was added to the list of additional dependencies for the mypy hook.
In poetry.lock, a new package entry for types-pyyaml was added, including its version, description, and file hashes.
In pyproject.toml, types-pyyaml was added to the list of project dependencies.

How to test
To test these changes, follow these steps:

Pull the changes from this PR to your local environment.
Run poetry install to install the new dependency.
Run pre-commit run --all-files to check that the mypy hook runs successfully with the new dependency.
Run your test suite to ensure that the addition of the new dependency does not break anything.

Why make this change
The addition of types-PyYAML provides type annotations for the PyYAML library, which can help catch potential bugs and improve code quality. This is particularly useful when using tools like mypy for type checking.

Current dependencies on/for this PR:

main

PR #23   👈

PR #24

PR #25

This comment was auto-generated by Graphite.

Merge Activity

Oct 8, 12:22 PM: @mingi3314 started a stack merge that includes this pull request via Graphite.


Separate the ALTREP constructor for vectors.

Before this change, vector constructors require many bounds on the iterator.
This is still true of ALTREP constructors, but the regular from_values is now
much simpler.
Explicit allocated vector.
        let vec = Doubles::from_values((0..3).map(|i| 2.0 - i as f64));
        assert_eq!(vec.is_altrep(), false);
        assert_eq!(r!(vec.clone()), r!([2.0, 1.0, 0.0]));
        assert_eq!(vec.elt(1), 1.0);
        let mut dest = [0.0.into(); 2];
        vec.get_region(1, &mut dest);
        assert_eq!(dest, [1.0, 0.0]);

Explicit ALTREP vector.
        let vec = Doubles::from_values_altrep((0..1000000000).map(|x| x as f64));
        assert_eq!(vec.is_altrep(), true);
        assert_eq!(vec.elt(12345678), 12345678.0);
        let mut dest = [0.0.into(); 2];
        vec.get_region(12345678, &mut dest);
        assert_eq!(dest, [12345678.0, 12345679.0]);

If no one objects, I'm just going to merge this.

If you want a thouroug review, I need some extra time. Otherwise, feel free to merge though I am concerned about failed CIs.

I'll look at the tests. Looks like the very large vector is allocated in memory, which is not good!

Down to an ephemeral failure in test_altreal.
In theory everything is protected by single_threaded, if this persists. I'll take a deeper look.

The original from_values tests should be unchanged, but I've renamed some of them to from_values_altrep.

Oops, mea culpa.

I think you managed to put your data frame derive commits into this branch before you merged, which isn't ideal.