Have julialauncher use execve() instead of launching a new process

I think we should change julialauncher to use execve() (or its moral equivalent, wherever possible) instead of fork() when launching the julia sub-process.  Because this does not launch a child process but instead causes the current process to be replaced by the new process, this would have the following advantages:

gdb naturally follows exec() calls, whereas with fork() there's some ambiguity, so it has to be told to follow the child rather than stay with the parent.
Process listings would now show only one julia process, instead of two.  (a minor benefit, but still nice)
We would no longer need to worry about passing exit codes back up; once we call execve() the rest is on the shoulders of the true julia application
We would no longer need to worry about signal handlers.

This would be Linux/Mac only, right? I don't think Windows has something like this?
And the second question is: right now julialauncher spawns the real julia process async, and then does other things, in particular check for new versions, while it waits for the julia process to finish. Could we still do that?

This would be Linux/Mac only, right? I don't think Windows has something like this?

No, I don't think it does, unless @vtjnash knows of a secret execve-like function on Windows.

right now julialauncher spawns the real julia process async, and then does other things, in particular check for new versions, while it waits for the julia process to finish. Could we still do that?

The way I would do it is to have julialauncher fork() off a second process and then execve() the true julia executable.

I think my primary worry is that this would essentially mean the Windows and Linux/Mac version would be more or less completely different... That doesn't strike me as ideal.
I think the exit codes and signal stuff is now handled properly? So I'm not too worried about that. But the gdb thing seems like a real benefit...

This seems like a good idea to me as well and I don't think the deviation between Windows and UNIX would be so bad—it could be very contained. Everything is the same right up until the moment of starting the julia process and then:

UNIX: fork a background process and do execve to replace the current process with julia
Windows: start julia as child process and then do the background stuff while waiting for it

In both cases you end up with some code running to do background stuff and the only other difference is whether to wait on julia as a child process and propagate its status (UNIX: no; Windows: yes). Sure, these are different, but it's a very contained difference and the way child process are started is radically different between these OSes anyway.

On windows you can pick a parent process and get status on anything, if you care enough to

Let's have this discussion over here instead of on a tangentially related (closed) issue. @davidanthoff wrote:

Yeah, I'm just quite nervous about the interaction of execve and Rust packages, there seems to be a lot of potential for pain. And on Windows that won't ever work, and I'm also not keen to have such a massive difference there...
My sense right now is that the only way to really have a one-process solution that is architecturally similar on the various platforms would be some variant of https://github.com/JuliaLang/juliaup/issues/327. Which also seems anything but trivial...

I don't want a one process solution—I'm happy to have julialauncher spawn a separate child process to do updates. But I do think that it's strictly better if the julialauncher process replaces itself with the actual julia process that the user wants to run. Can you elaborate on  what the possible Rust issue might be? Once the process has called execve I don't see problems Rust can possibly cause since the process has been replaced. I do get the desire to have all platforms work the same, but it seems like the difference in logic can be kept pretty small and at this point we have enough users on all platforms that I think we'll know if something isn't working on one of them.


Navigation issue

Describe the bug
When a user signs in or registers and navigates to the home screen, clicking the back button should close the application, but currently it navigates back to the login screen.
To Reproduce
https://github.com/sourabhkumar47/ResQFood/assets/81826285/ed376cff-f536-4635-b2c6-5be542367da9
Expected behaviour
Close the app or tap again to confirm exit.

I would like to work on this.

I would like to work on this.

Assigned


How to calculate the FLOPs and parameters of your model?

How to calculate the FLOPs and parameters of your model?

I don't think there is anything specific to our model. General methods (https://www.google.com/search?q=pytorch+compute+flops+and+parameter+count) will work.


When switching between modes, modlets list does not update installed modlets

When switching into Advanced mode, any modlets which are installed in the game's Mod directory are not updated to show as installed.

Happen intermittently, need to investigate.


[bug] :view key being deleted from options hash by #render

Is there an existing issue for this?

[X] I have searched the existing issues

Is this a regression?

[X] Yes, this used to work before

Current Behavior
It seems that the process of rendering is deleting the :view key from the options hash.  This breaks batching as only the first batch can be rendered correctly with subsequent ones falling back to the default view.
Expected Behavior
Options k-v pairs should persist through to subsequent renders.
Steps To Reproduce
> project = Project.last
=> #<Project 57:Fake Project Name>
> options = { view: :normal }
=> {:view=>:normal}
> ProjectBlueprint.render(project, options)
=> "{\"id\":57,\"name\":\"Fake Project Name\",\"some_key\":null,\"a_different_key\":null}"
> options.keys
=> []
> ProjectBlueprint.render(project, options)
=> "{\"id\":57}"

Environment
- OS: OSX 14.4.1
- Browser Name and version: N/A
- Ruby Version: 3.2.4

Anything else?
No response

FWIW this looks like a good candidate to me, although it's five years old. But if your options hash is newly being shared across multiple renders, it seems a likely cause.

Ah, apologies, I could have sworn this was working before and I saw this recent change in base.rb and thought that was the culprit.
The code that @jhollinger references above is indeed the issue, so this is perhaps more of a 'feature request'.
I have this draft PR (currently without tests) that would be a possible 'fix' for this if we agree this is a good idea.  I'm not really sure why the existing uses delete but perhaps someone has a good reason.


seralizer: Fix wrong order of unittest/docu

The documentation for isStringSerializable / isPolicySerializable is generated from the unittests.
The unittests are however in the wrong order, so that the docu for isStringSerializable is found where
one would expect to see isPolicySerializable and vice versa.
See an example of the wrong docu at (see example code there):
http://vibed.org/api/vibe.data.serialization/isStringSerializable
http://vibed.org/api/vibe.data.serialization/isPolicySerializable

Thanks! Wonder how that happened...


Kitti Viewer issue

Hello
Now I have trained the Kitti dataset follow the read me and got the model file. And I use Web KItti Viewer to visualize the result. I can open Web KItti Viewer and see the image/point cloud/object, but have some problems compared to demo image in readme.

can't render 360 degree data in bird's eye view and point cloud, only part of data, seems 75 degree FOV, I change the FOV parameter in Web KItti Viewer but it does not change amnything
no bounding box display in Image window

Could anyone help me for this issues?

Hi, do you solve the problems? I have the same problem with you.

The bounding box in image has been removed in V1.6, you change to use V1.5 or earlier branch, then you can see 360 degree FOV lidar data and bbox in image. That's what I have tried from my side.

Hi, thanks for your information. May I know how can I change the branch to V1.5 and do I have to retrain everything again? Sorry I am still a newbie.

you can use below command to clone v1.5 repo:
git clone -b v1.5 https://github.com/traveller59/second.pytorch.git
I think you don't need to retrain the model, you can just input the data and model which create using v1.6.

Hi @hefc2016 , thanks for your information. May I know how you evaluate your model on test data? I change the eval_input_reader 'kitti_info_path' with kitti_infos_test.pkl in the all.fhd.config file ,then run 'python ./pytorch/train.py evaluate...'，it can't show any evaluation results. Also, when I put kitti_infos_test.pkl as my infoPath and key in the image index but there are not any ground truth box on the point cloud and BEV. Sorry for disturbance.

@AngYikHong  I believe the reason you cannot get evaluation results because of there are no  label files( the ground truth) for test set. you could only get final evaluation by submit your result on KITTI webside, and  they would do this for you online.


Orientation control

Add necessary scripts to keep a game object oriented toward the camera so that menus and similar attachments maintain legibility and don't turn upside down.

Done.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.4.181",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d411b2a5da68b8a130c23097014434ac140a2ace"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d411b2a5da68b8a130c23097014434ac140a2ace",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "nvme-rdma: fix possible use-after-free in transport error_recovery work\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.181 by commit d411b2a5da68b8a130c23097014434ac140a2ace. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000355


Feat: add the behavior parameter

Added the HitTestBehavior parameter that describes how the GestureDetector should behave during hit tests

Great! thank you for your contribution.

Don't forget to publish 😉


Copy dev bundle.js output to actual path

I use create-react-app in subfolder in my webform/mvc/.NET core.. projects.
In development I have a fetchData() function in create-react-app that serves JSON (fake API)
To test it with the 'core project' API I have to run npm build and point the project to the output.
I would very much like to (know how to) copy/add an extra output here:
webpack.config.dev.js
// This does not produce a real file. It's just the virtual path that is
// served by WebpackDevServer in development. This is the JS bundle
// containing code from all our entry points, and the Webpack runtime.
filename: 'static/js/bundle.js',

Can you use proxy setting in development for this?
It is documented here.

Awesome! I am cross-site-scripting my self :)
Thanks - I'll close it now


Test added Mar 10

Added Secure Channel test
TC-SC-4.2
Attached execution logs for reference:
Execution_log.txt

Fast-tracking test addition.


Cache exception

The CacheException class was missing..

... it was... missing?

LGTM 👍

:(( not even gonna git blame ...

@Rican7 next time just squash my commits when there's a fixup! ... amongst them. Or let me rebase before merge. That way we can avoid fixup commits :)

Especially when it's still labeled work in progress 🙃

Whoops! Sorry about that! I didn't even realize the label. The merge seemed obvious, so I trigger fingered it. Sorry about that. :/


OakHash API

Add design and implementation of new OakHash API. API only, without the underlying HashMap. Probably the merge can go into a separate branch.
Similar to OakMap, OakHash should be extending ConcurrentHashMap, but must also support Zero-Copy API methods. Most likely new ZeroCopyHash should extand or be similar to ZeroCopyMap. And OakHash should return ZeroCopyHash, having all interfaces.
For more explanations feel free to add questions in this issue.

OakMap implements (the majority of) ConcurrentNavigableMap<K, V>, respectively new OakHash should implement ConcurrentHashMap<K,V> also possibly not fully.
However, via
/* ------ Zero-Copy API methods  ------ */

    public ZeroCopyMap<K, V> zc() {
        return new OakZeroCopyMap<>(this);
    }

OakMap supports the ZeroCopyMap interface of itself. Also respectively, the new ZeroCopyHash is required and needs to be tailored.


Kap screen recorder blocks gesture input from magic trackpad

macOS version:
OSX Catalina 10.15.6
Kap version:
Version 3.3.2 (<IP_ADDRESS>8
Steps to reproduce
Start Kap application
Current behaviour
Trackpad gestures not recognized
Expected behavior
Ability to navigate OSX using trackpad gestures
Workaround
TBD

I couldn't reproduce with a Magic Trackpad, using gestures both when Kap is open and actively recording. Are you on a MacBook?


AppBAr

closedDisplayMode in app bar with new winjs 4.1. full is not working. I know this only works on 4.0. can you direct me in your code so I can take a look and see if I can do anything?
thank you very much in advance.

never mind sorry


feat: throw an error if token has been created in getTickerReservation

:tada: This PR is included in version 6.0.0-beta.3 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unit tests for AppendHistoryNodes

What changed?
Added unit tests for AppendHistoryNodes

Why?

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018ec2da-4ee3-4039-b68f-a088d57aec04
Details

0 of 0   changed or added relevant lines in 0 files are covered.
22 unchanged lines in 6 files lost coverage.
Overall coverage increased (+0.03%) to 67.374%

Files with Coverage Reduction
New Missed Lines
%

common/task/weighted_round_robin_task_scheduler.go
2
89.05%

service/history/task/transfer_active_task_executor.go
2
72.7%

service/matching/taskListManager.go
3
80.2%

service/history/task/transfer_standby_task_executor.go
4
87.01%

common/task/fifo_task_scheduler.go
4
83.51%

service/history/execution/mutable_state_task_refresher.go
7
66.46%

Totals

Change from base Build 018ec2d0-2d55-4385-9005-feae08321986:
0.03%

Covered Lines:
98211

Relevant Lines:
145769

💛  - Coveralls


Server: add API endpoint for reporting server build info

Adding a new API endpoint that returns package/build # and the corresponding git commit hash. These values are determined at build time.

Pulling in shadow-rs as a dependency for server to compute git hash.

I'm not sure what the testing story is here, so lmk how/if I can test this out without integrating into clients.

Our dockerfiles are a lil wonky: https://github.com/lockbook/lockbook/blob/master/containers/Dockerfile.server. Cargo doesn't let us do a "build the dependency only step" (last time I checked), so the suggestion is to move a dummy main.rs / lib.rs to allow the dependency build cache to saturate.
We've added more and more cruft into this over time as you can see. Maybe there's a clean cargo extension that you can add that "dry"'s this up a bit.
If you don't feel like solving this particular problem right now you can just move the build.rs you created into the container before the deps.


Broken Link for AWS Cloudformation Deployment

PR #82 introduced a broken link for AWS Cloudformation deployment for docs/it-manual/sre-playbook/initial-deployment.md on line 7.
https://github.com/civiform/civiform-deploy does not contain an infra folder as https://github.com/seattle-civiform/civiform-deploy does.

Thanks!


Plugins + extends not working on Mac

I'm using Lab which uses eslint-plugin-hapi (https://github.com/cjihrig/eslint-plugin-hapi) and I extend the config from lab (https://github.com/hapijs/lab/blob/master/lib/linters/eslint/.eslintrc) and it's not working.
I've tried installing globally and in the folder of brackets-eslint and in the node_modules of my project

seems like only hapi-capitalize-modules is not being found, weird

seems to work now, weird stuff :P


[Polymetis] Align pybullet version

Description
Fixes issue where inconsistent versioning of PyBullet across the repo causes newer versions of PyBullet breaks circleci tests.
The most recent outage happened when PyBullet 3.1.9 was released on PyPI on Sep 20th 2021: example
Type of change
Please check the options that are relevant.

[x] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[ ] I want a thorough review of the implementation.
[x] I want a high level review.
[ ] I want a deep design review.

Before and After
If this PR introduces a change or fixes a bug, please add before and after screenshots (if this is causes a UX change) or before and after examples(this could be plain text, videos etc ) to demonstrate the change.
If this PR introduces a new feature, please also add examples or screenshots demonstrating the feature.
Testing
Please describe the tests that you ran to verify your changes and how we can reproduce.
Checklist:

[ ] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[x] New and existing unit tests pass locally with my changes.
[x] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I have verified that all scripts in tests/scripts runs on hardware.

Codecov Report

Merging #717 (c35e6a7) into main (937305a) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #717   +/-   ##
=======================================
  Coverage   34.54%   34.54%
=======================================
  Files         317      317
  Lines       31038    31038
=======================================
+ Hits        10721    10722    +1
+ Misses      20317    20316    -1

Impacted Files
Coverage Δ

interpreter/robot/tests/world.py
88.32% <0.00%> (-0.73%)
:arrow_down:

interpreter/craftassist/tasks.py
72.28% <0.00%> (-0.19%)
:arrow_down:

agents/craftassist/tests/fake_agent.py
72.17% <0.00%> (+0.65%)
:arrow_up:

Looks good.
Any insight into why the new version breaks tests?

Not sure, it's still confusing to me at the moment. This is the error msg:
ERROR: Command errored out with exit status 1: /opt/conda/envs/polymetis-local/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-z_xzvlwi/pybullet_1dbe809bac9e4e0cb70945e5f432b1de/setup.py'"'"'; __file__='"'"'/tmp/pip-install-z_xzvlwi/pybullet_1dbe809bac9e4e0cb70945e5f432b1de/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-l84pzm67/install-record.txt --single-version-externally-managed --compile --install-headers /opt/conda/envs/polymetis-local/include/python3.8/pybullet Check the logs for full command output.
Exception information:
Traceback (most recent call last):
  File "/opt/conda/envs/polymetis-local/lib/python3.8/site-packages/pip/_internal/req/req_install.py", line 782, in install
    success = install_legacy(
  File "/opt/conda/envs/polymetis-local/lib/python3.8/site-packages/pip/_internal/operations/install/legacy.py", line 121, in install
    raise LegacyInstallFailure
pip._internal.operations.install.legacy.LegacyInstallFailure

Merging first to unblock other PRs


DNR: Wip: Poc/catsrc v2

This PR attempts to integrate the Catalogd project (which introduces catsrcv1) to Operator controller. It also removes existing support with OLMv0 catsrc CRDs. The following action items are required:

[ ] Introduce new EntitySource that converts v1beta bundles to entities.

[x] Write the logic implementing the entity source methods.
[ ] Modify deppy interface to return an error when bundles are fetched from cluster -  Modify the function signature here to return an error along with an entity. (https://github.com/operator-framework/deppy/pull/90)
[ ] Write unit tests for each of these methods.

[ ] After a catlogd release is out, pin that particular release in go.mod. Right now Go workspaces are being used. To be specific, this commit is being taken into consideration.

Follow up:

[ ] Remove support for v0 catsrc and write e2e tests
[ ] The following code would end up being unused. Remove the following files
- [ ]  Entity to bundle implementation which is already re-written for catsrc v1beta - here.
- [ ] ListEntities implementation for v0 - here.
- [ ] Catsrc reconciler implementation. I'd suggest to even remove the reconciler logic and leave it as is, so that we can come back and implement optimization on it later. Having a file of unused code to be implemented in future should be fine.

Since catalogd currently uses CRDs for Package and BundleMetadata, we get caching for free if we use the default controller-runtime client. Also, given there is more planned work on the catalogd APIs, I propose the following:

Revert the OLMv0 catalog source support. (This ensures we don't have to think about how to handle the presence of both APIs simulatenously)

Create an EntitySource implementation that uses a caching controller-runtime client to generate deppy entities on the fly via c-r Client Get and/or List calls for the catalogd Package and BundleMetadata APIS. I think we can get away with not even having a controller that watches the catalogd CatalogSource API. Anytime we reconcile Operator objects, we would just go directly to this c-r client based implementation, fetch the underlying objects directly, and convert them to entities on the fly.

Does this seem like a reasonable path?

I think that sounds reasonable.
If we are getting caching for free that's nice, but does the default caching implementation end up caching all instances of those resources?  For example, if I do a Get for a specific BundleMetadata resource, does the cache end up creating a new watch for all BundleMetadata resources? For the time being, are we concerned about large amounts of memory consumption due to caching so many resources (for BundleMetadata we are talking in terms of 1000s)? Are we comfortable saying that the operator-controller could run into OOM issues and it is an optimization we have to make in the future?

does the cache end up creating a new watch for all BundleMetadata resources

yes

are we concerned about large amounts of memory consumption due to caching so many resources

If it makes operator-controller unusable, that would be a problem, but I think its fine to ignore the memory concerns for now. We can optimize later, IMO.

1 .Revert the OLMv0 catalog source support. (This ensures we don't have to think about how to handle the presence of both APIs simulatenously)
2. Create an EntitySource implementation that uses a caching controller-runtime client to generate deppy entities on the fly via c-r Client Get and/or List calls for the catalogd Package and BundleMetadata APIS. I think we can get away with not even having a controller that watches the catalogd CatalogSource API. Anytime we reconcile Operator objects, we would just go directly to this c-r client based implementation, fetch the underlying objects directly, and convert them to entities on the fly.

https://github.com/operator-framework/operator-controller/pull/182

@varshaprasad96, should this be closed now that #182 merged?

Closing in favour of #182.


Removed trailing '=' signs from the header and the payload.

It turns out the '=' signs must be removed from each part of the signature.
As a side effect this fixes #31 so I've added a unit test reflecting it :)

Thanks!


Restore missing library versions in build.rs

Part of https://github.com/gtk-rs/gir/pull/920#issue-413449143
cc @GuillaumeGomez , @sdroege

@GuillaumeGomez Green CI


Create an environment with clang, libc++ with support of clangd

Describe the bug
Not really a bug but I'm struggling setting up an environment with clang, libc++ and the support of clangd as a linter in vim.
I wonder if anyone already managed to set up this kind of environment.
To Reproduce
Here are the minimum files I created to try to setup the whole thing:
The shell.nix:
{ pkgs ? import <nixpkgs> {} }:

with pkgs;
let
  vim = pkgs.vim_configurable.customize {
    name = "vim";
    vimrcConfig = {
      customRC = ''
        let g:ale_linters = {
          \ 'cpp': ['clangd'],
          \ }
        let g:ale_fixers = {
          \ 'cpp': ['clang-format'],
          \ }

        set omnifunc=ale#completion#OmniFunc
        let g:ale_completion_enabled = 1

        let g:ale_c_parse_compile_commands = 1
        let g:ale_c_build_dir = 'build'
        let g:ale_c_clangformat_options = '-style=file'
        let g:ale_cpp_clangd_options = '-compile-commands-dir=build'
        let g:ale_fix_on_save = 1
      '';

      packages = {
        core = {
          start = with pkgs.vimPlugins; [ale];
        };
      };
    };
  };
in
pkgs.llvmPackages_9.libcxxStdenv.mkDerivation {
  name = "env-clang-libc++";
  buildInputs = [cmake ninja vim];
  shellHooks = ''
    mkdir -p build
    export SRC_DIR="$PWD"
    export BUILD_DIR="$(realpath build)"
    alias cm='pushd "$BUILD_DIR" && cmake -G Ninja -DCMAKE_EXPORT_COMPILE_COMMANDS=ON "$SRC_DIR" && popd'
    cm
  '';
}

... a main.cpp:
#include <cstdlib>
#include <iostream>

int main() {
  std::cout << "hello world" << std::endl;
  return EXIT_SUCCESS;
}

... a minimal CMakeLists.txt:
cmake_minimum_required(VERSION 3.10)
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
project(Main)
add_executable(Main main.cpp)

Running nix-shell obviously launches the shell and runs cmake for compile_commands.json to be present in the build directory.
Lets build Main and check that libc++ is linked:
~/projects/llvmenv  λ. nix-shell
~/projects/llvmenv/build ~/projects/llvmenv
-- The C compiler identification is Clang 9.0.1
-- The CXX compiler identification is Clang 9.0.1
-- Check for working C compiler: /nix/store/7cz8fmvmp94bxbd57p7wm22qw1q0qq9h-clang-wrapper-9.0.1/bin/clang
-- Check for working C compiler: /nix/store/7cz8fmvmp94bxbd57p7wm22qw1q0qq9h-clang-wrapper-9.0.1/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /nix/store/7cz8fmvmp94bxbd57p7wm22qw1q0qq9h-clang-wrapper-9.0.1/bin/clang++
-- Check for working CXX compiler: /nix/store/7cz8fmvmp94bxbd57p7wm22qw1q0qq9h-clang-wrapper-9.0.1/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/identity/projects/llvmenv/build
~/projects/llvmenv
[nix-shell] ~/projects/llvmenv  λ. cd build && ninja
[2/2] Linking CXX executable Main
[nix-shell] ~/projects/llvmenv/build  λ. readelf -d Main && cd ..

Dynamic section at offset 0x2cf0 contains 32 entries:
  Tag        Type                         Name/Value
 0x0000000000000001 (NEEDED)             Shared library: [libc++abi.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc++.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x000000000000001d (RUNPATH)            Library runpath: [/nix/store/rr1hdv6cvb8bd86x3qf1na88ml15rr45-env-clang-libc++/lib64:/nix/store/rr1hdv6cvb8bd86x3qf1na88ml15rr45-env-clang-libc++/lib:/nix/store/i8cgz3in0v41kzays4mwn1mv5xrrsjb1-libc++-9.0.1/lib:/nix/store/4xnjwan2nnnkc2wsqvpdbfq86wdgqifs-libc++abi-9.0.1/lib:/nix/store/9hy6c2hv8lcwc6clnc1p2jf09cs5q9dp-glibc-2.30/lib]

So the build environment is correctly set up.
But there's something wrong with clangd. It should lint when running vim main.cpp but whatever I write into the file it gets correctly formatted thanks to clang-format but not linted at all.
Running the command :ALEInfo in the editor tells me clangd has been found but nothing else :man_shrugging: .
Anybody managed to have a working clangd in this kind of environment?

clangd doesn't get wrapped like clang itself, see also the above issue. Maybe have a look at the wrapper script (cat $(type -p clang in the nix-shell) and see if setting some of those environment variables helps.

This may be obvious but just to check since I've been bitten by it myself recently - did you symlink / copy compile_commands.json into the root of your project (unless your main.cpp is in the the build folder..)? From clangd documentation:
Clangd will look in the parent directories of the files you edit looking for it.
After I've done this clangd worked for me without needing any further changes although it was on a simple C/meson project on Linux/NixOS.

This affects me I think

@fakedrake yes indeed. Sorry for not posting it.
This is what I came with at some point. It might require some cleaning :sweat_smile:
{ pkgs ? import <nixpkgs> {}, buildInputs ? [], shellHook ? "", ... }@attrs:

let
  llvmPackage = pkgs.llvmPackages_11;
  stdenv = llvmPackage.libcxxStdenv;
  libcxx = llvmPackage.libraries.libcxx;
  libcxxabi = llvmPackage.libraries.libcxxabi;
  clang-python = llvmPackage.clang-unwrapped.python;

  rest = builtins.removeAttrs attrs ["pkgs" "buildInputs" "shellHook"];

  extraBuildInputs = buildInputs;
  localBuildInputs = [libcxx libcxxabi clang-python llvmPackage.lldb];
  extraShellHook = shellHook;

in stdenv.mkDerivation (rec {
  name = "libcxxStdenv";
  buildInputs = localBuildInputs ++ extraBuildInputs;
  shellHook = ''
    export CPATH=$CPATH:${llvmPackage.libcxx}/include/c++/v1:${stdenv.glibc.dev}/include
    export CPLUS_INCLUDE_PATH=$CPATH
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${libcxx}/lib:${libcxxabi}/lib
    export PATH=$PATH:${clang-python}/share/clang
  '' + extraShellHook;
  CPATH = pkgs.lib.makeSearchPathOutput "dev" "include" (localBuildInputs ++ extraBuildInputs);
} // rest)

Thank you! Much appreciated


Implement copy-paste from spreadsheet-based clipboard

It would seem that when pasting, every cell is separated with \t. Let's try doing it.

Closed by https://github.com/imballinst/markdownclap/pull/18.


Add Code_of_Conduct, Contributions and WaveDiff_Dev_Workflow markdowns

I prepared three Google Docs which should be converted to Markdown files:

CODE_OF_CONDUCT.md
CONTRIBUTING.md
DEV_WORKFLOW.md

Save the files in the top-level of the repo.
Update the documentation file: https://github.com/CosmoStat/wf-psf/blob/main/docs/source/index.rst?plain=1 by adding at the bottom:
Contributing
------------

For information on how to contribute to the development of WaveDiff, see
`Contributing to WaveDiff <./CONTRIBUTING.md>`_.

Make sure the links work.

Hi @nadamoukaddem I granted you edit access, but if there are changes you would like to propose please you suggest them instead of editing the document directly. Thanks

Hi @jeipollack , should I include the last paragraph in DEV_WORKFLOW.md ?

Hi @jeipollack , should I include the last paragraph in DEV_WORKFLOW.md ?

Hi @nadamoukaddem, thanks for catching this. Omit it from the new markdown file.


MJST-28 Add script params and interactive prompts

First drafts.

Task linked: MJST-28 Add script params and interactive prompts


//tensorflow/python/client:session_partial_run_test is flaky

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
git HEAD
Custom Code
No
OS Platform and Distribution
Ubuntu 20.04
Mobile device
n/a
Python version
3.9.16
Bazel version
5.3.0
GCC/Compiler version
10.2.1
CUDA/cuDNN version
n/a
GPU model and memory
n/a
Current Behaviour?
Unit test reports as FLAKY or FAILED.
See https://source.cloud.google.com/results/invocations/dea422ff-7e14-4fc1-b324-0129ecd7ffbc/log or https://github.com/tensorflow/tensorflow/actions/runs/4731924097/jobs/8397430880#step:5:23224
Standalone code to reproduce the issue
docker exec tf bazel --bazelrc=/usertools/cpu.bazelrc test --config=rbe --config=pycpp --config=build_event_export

Relevant log output
======================================================================
ERROR: testPartialRunMissingPlaceholderFeedExceptionDist (__main__.PartialRunTest)
PartialRunTest.testPartialRunMissingPlaceholderFeedExceptionDist
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1379, in _do_call
    return fn(*args)
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1369, in _prun_fn
    return self._call_tf_sessionprun(handle, feed_dict, fetch_list)
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1460, in _call_tf_sessionprun
    return tf_session.TF_SessionPRun_wrapper(self._session, handle, feed_dict,
tensorflow.python.framework.errors_impl.InternalError: From /job:localhost/replica:0/task:0:
ValidateDevices called before initialization.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/framework/test_util.py", line 1629, in decorated
    return f(self, *args, **kwargs)
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session_partial_run_test.py", line 269, in testPartialRunMissingPlaceholderFeedExceptionDist
    self.RunTestPartialRunMissingPlaceholderFeedException(
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session_partial_run_test.py", line 119, in RunTestPartialRunMissingPlaceholderFeedException
    sess.partial_run(handle, fetches[0])
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1026, in partial_run
    return self._run(handle, fetches, feed_dict, None, None)
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1192, in _run
    results = self._do_run(handle, final_targets, final_fetches,
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1375, in _do_run
    return self._do_call(_prun_fn, handle, feeds, fetches)
  File "/b/f/w/bazel-out/k8-opt/bin/tensorflow/python/client/session_partial_run_test.runfiles/org_tensorflow/tensorflow/python/client/session.py", line 1398, in _do_call
    raise type(e)(node_def, op, message)  # pylint: disable=no-value-for-parameter
tensorflow.python.framework.errors_impl.InternalError: Graph execution error:

From /job:localhost/replica:0/task:0:
ValidateDevices called before initialization.

----------------------------------------------------------------------
Ran 25 tests in 2.625s

FAILED (errors=1, skipped=1)
================================================================================

Hi @elfringham ,
Thanks for reporting. I would like to know whether this is docker specific? can we replicate it with linux environment? If so please provide command(s) that replicates the reported behaviour. Thanks!

@SuryanarayanaY Sorry but the behaviour is too intermittent to draw any conclusion about whether it is docker specific or not. Current results show two failures together then 12 passing jobs.


Navigation: Add dropdown for "About" section

Describe the bug
The nav bar's "About" section is missing a dropdown to the subpages.
Impact on ReportStream
The dropdown will make it easier for users to quickly find what they're looking for in the the About (currently, the site's largest section).
Steps to reproduce
Steps to reproduce the behavior:

Go to 'reportstream.cdc.gov'
Click on 'About'
See that no dropdown appears.

Expected behavior
Upon click, the dropdown menu should appear listing the following links:

Our network
News
Case studies
Security
Release notes

Resources
N/A
Logs
N/A
Device info
N/A
Desktop (please complete the following information)

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information)

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
The dropdown functionality is already built, it just needs to be toggled on for the About section. Depending on when this ticket is picked up, the pages that are still being engineered (Case Study, News, Security) will have to be added later.

Per Jillian

I confirmed with Audrey - we can add a link that says "About ReportStream" (instead of "Overview") that redirects to the About landing page


Refactor: contract-workflow-name

PFM-2002 - workflow re verification state introduced

Update the workflow json as well


Click on the Map on iOS doesn't fire a SelectionChanged value to null

Description
Click on the Map on iOS doesn't fire a SelectionChanged Event with Null Value.
Located Issue
In the iOSUnifiedMapRenderer  the private property _shouldNotDismiss is always false when touchEnded if we don't move the touch.
public override void TouchesEnded(NSSet touches, UIEvent evt)
{
	base.TouchesEnded(touches, evt);
	if (Element != null && Element.ShouldDeselectOnMapTouch && _shouldNotDismiss)
	{
		var isAnnotation = false;
		var touch = touches.FirstOrDefault() as UITouch;
		if (touch != null && Control != null)
		{
			if (touch.View is MKAnnotationView)
			{
				isAnnotation = true;
			}
		}
		if (!isAnnotation)
		{
			// Deselect annotation when map is touched
			SelectedItem = null;
		}
	}
}

Expected Behavior
Click on the Map should raise selectionChanged event with null value.
Actual Behavior
The _shouldNotDismiss property block the event because it is always false.
Is this _shouldNotDismiss property is necessary? Should we revert the _shouldNotDismiss condition condition or just remove the property?

there is #79


Change enlarge on hover?

IMHO the enlarge on hover effect looks really out of date and there's no other place in the UI where this happens (as far as I can see). Maybe a colour change instead?
I realise this is personal opinion so feel free to shut me down!

I agree, the hover effect is not right here. I'd be happy with changing the color of the svg fill.


Bugfix dragndrop

when plugin doesn't have children it was not possible to drop anything on it

LGTM

:+1:


FlowFuse Team Dashboard 2.0 Journey

Description

Related Issue(s)

Checklist

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

Not going to publish.  Other similar blog didn't create activity.


Extractor error

When creating a trail with a website that is part of another trail, none of the extracted data is persisted.
The following error occurs in the depot:
{ [MongoError: E11000 duplicate key error index: datawake.DwUrlExtraction.$id dup key: { : 1 }]
name: 'MongoError',
message: 'E11000 duplicate key error index: datawake.DwUrlExtraction.$id dup key: { : 1 }',
driver: true,
code: 11000,
index: 0,
errmsg: 'E11000 duplicate key error index: datawake.DwUrlExtraction.$id dup key: { : 1 }',
getOperation: [Function],
toJSON: [Function],
toString: [Function] }

I believe this is because of the dw-url-extraction model.  The model properties are: value, occurrences, extractorTypes, extractor, requester, created.
If we extract "John Smith" from two different urls in a trail you can see how all of the above properties would be duplicated and cause the error (the created field is populated on save so doesn't count).  I had thought that the "dwTrailUrlId" from the "trailUrl" relation would cause the record to be unique, but this is apparently not the case.
Need to investigate how to get the trailUrl included so that the insert is unique.

believe we need to add this to the DWUrlExtraction model.  This will need to be done on a clean database (at least with no extractions). Haven't tested:
"indexes":{
"trailUrl_extraction_index":{
"keys":{
"id":1,
"dwTrailUrlId":1
},
"options":{
"unique":true
}
}

do we see a similar problem if we hit the same url multiple times within a trail?

Not that I've ever noticed but that doesn't mean much.

Went to same URL as contained within another trail.  I got extractions just fine and they were persisted.  Closing as not an issue (at least not anymore).


Swaylock transparency is weird

If you run swaylock with a color with transparency, such as
swaylock -c 00000022

It appears as expected. Then, while typing the password to unlock, the screen gets darker and darker at every keystroke. My impression is that the colors get layered and therefore the alpha channel is not the expected one

I can reproduce your issue.


Self-contained local development environment

We'd like people to do some local dev work at the Wyoming hackathon. However, we don't want to waste lots of time getting people set up (not to mention that we haven't tested building our stuff with many configurations).
So, it would be good to provide a pre-pacakged development environment that people can just start using. The goal would be that people could just enter it, fire up an editor, and immediately start writing code in a skeleton project.
My suggestion would be a Docker container (easy for us to build with Nix).
In order of importance, this could contain:

A skeleton project which depends on our packages and is buildable.

How do we make sure our stuff is buildable?

Can we put a pre-prepared nix store in the image?
If we're confident that it works with stack we could just use that

How do we set up the project nicely?

It doesn't seem that easy to depend on our bunch of unreleased pacakges - I think we'll have to add a load of source-repository-package stanzas, plus the ones for the dependencies that we pin specific versions of. But at least we can do this for the user!

Some decent editor preinstalled, ideally with some kind of IDE support set up.

I suggest VSCode as an editor, it requires comparatively little configuration, and has plugins for things already. Plus, it's in nixpkgs, along with support for including extensions.
I suggest HIE for the IDE part. I think it's at a usable point now. It's not in nixpkgs, but there is support for building it in nix, so we should be able to borrow that. Plus, hopefully we can do any painful configuration bits.

Sounds like a good plan. The only issue might be that the VSCode Haskell config probably doesn't know how to deal with a Haskell environment running in a Docker container, so we'll have to see how easy or hard that is to fix up.

I meant we put VSCode in the container. TBH, I don't normally do stuff inside Docker containers so I'm not sure how feasible it is to run a graphical application from inside one.

If VSCode is in the container, one option is to use a remote X connection, but that will only work on Linux hosts.
The other option is to use a VNC connection. This may or may not require installing a separate VNC client on the host. On Mac and Windows that might involve getting a (paid) third party VNC client. I don't know how good VNC client support is on Linux.
It'll also require some experimentation as to whether the performance is sufficient, as going via a remote X connection or VNC will effectively kill all graphic acceleration (which may be quite annoying when scrolling and similar).
Finally, the set up must be such that it properly maps a subtree of the host file system into the container where it is edited (otherwise, all changes get lost when the container terminates). This is not really hard with the right docker run options, but it may start to get annoying once you want to edit more than one project at once.

I don't know how good VNC client support is on Linux.

Pretty good! I've used them before and there are decent free options.
Possibly we should try and make it work with a VSCode installation on the host, but I don't know how feasible that is.

This is not really hard with the right docker run options, but it may start to get annoying once you want to edit more than one project at once.

Yeah, although for now I think it's fine if this only works for one project.

I think a VM image is probably better, no?

Possibly we should try and make it work with a VSCode installation on the host

According to this, std in/out is all that's needed for the HIE VSCode plugin. If this works I'd much prefer it over running VSCode inside docker.

OK, so the plan at the moment is to build a VM image that contains VS Code hooked up to HIE and an example plutus stack project. Docker is not really designed for this type of thing and I think a VM will make everyone's lives much easier.
Building an image tends to be a bit tricky but I am working on creating a NixOS configuration.nix file that contains everything required, there is then a tool https://github.com/nix-community/nixos-generators/ that can be used by someone with a linux computer (not a VM) to build an image for VirtualBox or some other VM hypervisor. Alternatively the configuration.nix file can be used in a running NixOS VM and the machine snapshot distributed. While this is slightly more manual it might mean we can set some minor things up that can't be done in configuration.nix.
Once I have a working configuration.nix I will investigate again the best way to build an image.

Question: we can set up a nice NixOS VM to have vscode and hie installed and working but adding an example project is a bit trickier since it is stateful. I suggest we just have as part of the instructions that you need to clone plutus and copy the example project that I am creating (or alternatively put the example project in a separate repo). The project will be tested with the VM image so it should work just fine, what do you think?

This would also mean that anyone who wants to be a rebel and not use the VM will have an easier time, they should only need nix installed

Can't we stick a cheeky activation script in there that clones the git repo into the user's home dir or something? I guess if we want them to mount the project into the VM then that's the wrong way around.
Cloning the demo project would be reasonable. Maybe we should just put it in this repository? That would also simplify the setup process: you can use our stack.yaml/cabal.project and you don't have to deal with extra-deps. The cost is that it's not a very "proper" way of doing it, but maybe that's okay?

I thought of the startup script but it's pretty nasty and I don't think it's a big deal to ask people to
https://github.com/input-output-hk/plutus.git
cd example
nix-shell
cabal new-build

Although now that I've written that down I realise that cabal new-build will take quite a long time. The activation script would at least get rid of that issue.
Remember we can't use stack at the moment due to those symlink issues but nix-shell and cabal seems fine to me.

This is in the guest OS, right? It would be nice if we didn't require people to have nix installed on their host machine.
cabal new-build will take a while, but hopefully not too long. It would be cute if we could do it in advance but I wouldn't worry about it too much.

Yeah I mean we will provide a VM with nix, vscode and hie and then the user must clone and build the example project however if they want to they could clone and build on their host machine (or after the course they can)

Yeah that seems fine.

PR at https://github.com/input-output-hk/plutus/pull/1373

VSCode has some extensions for running the editor backend (file system as well as compiler, git, etc.) in a process on another machine or in a docker container (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack)
I got it to work with WSL & the Plutus project yesterday, but the result wasn't great because the type checking plugin kept opening new terminals and in each one it had to run nix shell which takes about 20s just to set up the environment.

@michaelpj can this issue be closed now? @j-mueller do you mean in order to run everything  difficult in docker? This might be a nice improvement. Why do they need to nix-shell? If we had a container built with nix then it shouldn't need nix-shell?

If we had a container built with nix then it shouldn't need nix-shell?

I initially tried to get it to work with my own setup, which involves nix-shell, but if it runs in a container then you are right, we shouldn't need nix-shell.

Sure, we can continue this discussion elsewhere.
I thought one of the remaining issues with the VM image we're providing is that people may not be able to easily use their host VSCode with it, and they may have a worse experience using VSCode inside the VM. So it could be good to get the remote support working.


Upgrade Elyra with odh-elyra for kfp v2 support

Upgrade Elyra with odh-elyra for kfp v2 support
Description

Related-to: https://issues.redhat.com/browse/RHOAIENG-4548

Removed the patches that were applied earlier.
fixed the onnxconverter-common version, for protobuf issue.

How Has This Been Tested?

NA
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

Merging to get the release out.


Investigate which mapping framework to use

As a developer
I want to use a mapping framework
So that I can easily map CIM Objects to IEC61850 Objects
To map the CIM Files it would be nice to use a mapping framework, like Orika, to map properties between CIM and IEC61850.
It would be nice to not have it only in code, but that there is also some kind of GUI to maintain these mappings. This way mapping can be updated in the future by other people then developers.

Currently it looks like there are 3 Java Framework that can be considered.

Orika, MapStruct and JMapper

JMapper has 1 big pro, the configuration can be done in XML, so it could be done by a non-java developer.
The biggest con is that the standard way of mapping is done with annotations on the destination class.
In our case these are generated classes by JAXB, so we are not able to added them easily and that is also done in a other repository.
Orika and MapStruct work kind of the same. The pro on MapStruct is that the project is still active and Orika hasn't made a release since 2019. So for now MapStruct seems the best choice.


'C:\Program' is not recognized as an internal or external command

Following instructions for installing the admin plugin, I'm running into the following error:
$ bin/gpm version -f
Preparing to install vendor dependencies...

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

I'm running Windows and PHP is in the path. I'm using the Git for Windows Linux emulator.
$ php -v
PHP 7.2.7 (cli) (built: Jun 19 2018 23:44:15) ( NTS MSVC15 (Visual C++ 2017) x86 )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies

I get the same results in PowerShell:
PS C:\inetpub\wwwroot\grav> php -v
PHP 7.2.7 (cli) (built: Jun 19 2018 23:44:15) ( NTS MSVC15 (Visual C++ 2017) x86 )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies

PS C:\inetpub\wwwroot\grav> php bin\gpm version -f
Preparing to install vendor dependencies...

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

cd php bin/gpm version -f

D:\xamp\htdocs\dom.local>php bin\gpm version
You are running Grav v1.6.23

@YuraL0ns I get the same result when I append 'php' to the command.

@darmentrout I received an error yesterday, but I did not use php, but today I work with php and there are no errors.

This is most likely due to bin/gpm not escaping the command returned by composer (can be tricky tho'
https://github.com/getgrav/grav/blob/develop/bin/gpm#L15
calling:
https://github.com/getgrav/grav/blob/develop/system/src/Grav/Common/Composer.php#L59
replacing that line 59 with:
return $executor  . escapeshellarg($composer);
and on line 46:
$executor = escapeshellcmd(PHP_BINARY) . ' ';
should do it.
Also the same could happen on any platforms allowing spaces in paths btw.

(btw, sorry for no PR yet, I am just starting to look at Grav and begin to like it, needed for one of my projects :)

on windows if u have PATH php setup i run php bin/gpm install admin without PATH just run c:/pathtoyourphp/php.exe bin/gpm install admin


Add ndarray and Tensor types

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (83205a3) 100.00% compared to head (264d8d0) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #67   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           24        25    +1
  Lines          692       692
  Branches        80        80
=========================================
  Hits           692       692

Impacted Files
Coverage Δ

src/arctix/stats/base.py
100.00% <ø> (ø)

src/arctix/stats/continuous.py
100.00% <100.00%> (ø)

src/arctix/stats/discrete.py
100.00% <100.00%> (ø)

src/arctix/summarizers/summarizer.py
100.00% <100.00%> (ø)

src/arctix/utils/types.py
100.00% <100.00%> (ø)

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


Allow installing multiplatform ocp image

This allows to install multiplatform image

/lgtm

Thank you!

/retest

/approve


Copying and pasting dist folder's contents from Classifai_FrontEnd to classifai's webroot

This is an automatically created PR :robot::robot:

It will triggered once codes in dist folder from repo Classifai_FrontEnd has been pushed.
Files & sub-folder in dist folder of repo Classifai_FrontEnd will be copied into classifai's webroot
Committed frontend PR's URL can be found in the commit history below.

Tested and working on Windows 10


Bugfix - use "ID" instead of "Id"

Issue occurs on Iresis Feed - ReplyCode 20513

Looks like the other 2 spots in that file were fixed in this: https://github.com/sbruno81/rets-client/commit/629b7a22bbaa521e369304be347f0129486236f9#diff-f1c5c342824a8c59d66bc53d07cbc2cc but that one got missed.

Cool, I've lost 4 days on that :)

Hey @sbruno81 @zacronos @esvinson,
Any chance you can accept PR by the end of this week? I have prod release next week...
Thank you!

@Marko-Jankovic v5.2.3 released

@zacronos Please, publish to npm. Thank you!

That's what I meant by "released".  ;-)


boot2docker-cli stop does nothing

on windows - I've not tested elsewhere yet.
this is the 0.8.0 release :(

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).


Update sbt-dotenv to 2.1.233

Updates au.com.onegeek:sbt-dotenv from 2.1.227 to 2.1.233.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "au.com.onegeek", artifactId = "sbt-dotenv" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #90 (1946f61) into master (bb87dad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #90   +/-   ##
=======================================
  Coverage   42.82%   42.82%
=======================================
  Files          54       54
  Lines         509      509
  Branches       16       16
=======================================
  Hits          218      218
  Misses        291      291

Continue to review full report at Codecov.

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


Warnings when using with Home Assistant 2023.8.0

Hi!
I was using SwitchBot-MQTT-BLE-ESP32 with Home Assistant and till now everything was ok, no error, no warning. From yesterday, when I updated Home Assistant to a newer version, I got this warning, and not only me. Any idea how to solve this? Thank you!

These warning can be safely ignored by users but this project should be updated to reflect changes introduced in HA 2023.8.
@devWaves do you think you could find some time to update names?
I might try to make a PR but I am not sure to know the code enough to do it without breaking something and I personally use Switch Bot with the native integration which is enough for my use so not sure to succeed in making efficient tests.

Is there really no need for action and the message can be ignored!?

At least till 2024.2.0 :-D

18 warnings in less than 2 minutes
Logger: homeassistant.components.mqtt.mixins
Source: components/mqtt/mixins.py:294
Integration: MQTT ([documentation](https://www.home-assistant.io/integrations/mqtt), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+mqtt%22))
First occurred: 23:40:24 (18 occurrences)
Last logged: 23:40:24

    MQTT entity name starts with the device name in your config {'name': 'door_sensor BinaryContact', 'device': {'identifiers': ['switchbot_DB:63:F6:1C:E1:E2'], 'manufacturer': 'WonderLabs SwitchBot', 'model': 'Contact', 'name': 'door_sensor', 'connections': []}, 'availability_topic': 'switchbot/entrance_switchbot/lastwill', 'unique_id': 'switchbot_DB:63:F6:1C:E1:E2_bincontact', 'icon': 'mdi:door', 'state_topic': 'switchbot/entrance_switchbot/contact/door_sensor/bin', 'payload_on': 'OPEN', 'payload_off': 'CLOSED', 'qos': 0, 'force_update': False, 'availability_mode': 'latest', 'enabled_by_default': True, 'payload_not_available': 'offline', 'encoding': 'utf-8', 'payload_available': 'online'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'BinaryContact'
    MQTT entity name starts with the device name in your config {'name': 'door_sensor In', 'device': {'identifiers': ['switchbot_DB:63:F6:1C:E1:E2'], 'manufacturer': 'WonderLabs SwitchBot', 'model': 'Contact', 'name': 'door_sensor', 'connections': []}, 'availability_topic': 'switchbot/entrance_switchbot/lastwill', 'unique_id': 'switchbot_DB:63:F6:1C:E1:E2_in', 'icon': 'mdi:motion-sensor', 'state_topic': 'switchbot/entrance_switchbot/contact/door_sensor/in', 'payload_on': 'ENTERED', 'payload_off': 'IDLE', 'qos': 0, 'force_update': False, 'availability_mode': 'latest', 'enabled_by_default': True, 'payload_not_available': 'offline', 'encoding': 'utf-8', 'payload_available': 'online'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'In'
    MQTT entity name starts with the device name in your config {'name': 'door_sensor Out', 'device': {'identifiers': ['switchbot_DB:63:F6:1C:E1:E2'], 'manufacturer': 'WonderLabs SwitchBot', 'model': 'Contact', 'name': 'door_sensor', 'connections': []}, 'availability_topic': 'switchbot/entrance_switchbot/lastwill', 'unique_id': 'switchbot_DB:63:F6:1C:E1:E2_out', 'icon': 'mdi:exit-run', 'state_topic': 'switchbot/entrance_switchbot/contact/door_sensor/out', 'payload_on': 'EXITED', 'payload_off': 'IDLE', 'qos': 0, 'force_update': False, 'availability_mode': 'latest', 'enabled_by_default': True, 'payload_not_available': 'offline', 'encoding': 'utf-8', 'payload_available': 'online'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Out'
    MQTT entity name starts with the device name in your config {'name': 'door_sensor Button', 'device': {'identifiers': ['switchbot_DB:63:F6:1C:E1:E2'], 'manufacturer': 'WonderLabs SwitchBot', 'model': 'Contact', 'name': 'door_sensor', 'connections': []}, 'availability_topic': 'switchbot/entrance_switchbot/lastwill', 'unique_id': 'switchbot_DB:63:F6:1C:E1:E2_button', 'state_topic': 'switchbot/entrance_switchbot/contact/door_sensor/button', 'icon': 'mdi:gesture-tap-button', 'payload_on': 'PUSHED', 'payload_off': 'IDLE', 'qos': 0, 'force_update': False, 'availability_mode': 'latest', 'enabled_by_default': True, 'payload_not_available': 'offline', 'encoding': 'utf-8', 'payload_available': 'online'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Button'
    MQTT entity name starts with the device name in your config {'name': 'door_sensor Illuminance', 'device': {'identifiers': ['switchbot_DB:63:F6:1C:E1:E2'], 'manufacturer': 'WonderLabs SwitchBot', 'model': 'Contact', 'name': 'door_sensor', 'connections': []}, 'availability_topic': 'switchbot/entrance_switchbot/lastwill', 'unique_id': 'switchbot_DB:63:F6:1C:E1:E2__illuminance', 'state_topic': 'switchbot/entrance_switchbot/contact/door_sensor/illuminance', 'device_class': <BinarySensorDeviceClass.LIGHT: 'light'>, 'payload_on': 'BRIGHT', 'payload_off': 'DARK', 'qos': 0, 'force_update': False, 'availability_mode': 'latest', 'enabled_by_default': True, 'payload_not_available': 'offline', 'encoding': 'utf-8', 'payload_available': 'online'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Illuminance'

I was able to fix, several lines need to be changed:
Basically:
Search for "addToPublish"
The ones that have line similar with:    + ""name":"" + host + " Linkquality"," +
Need to be replaced with:    + ""name":"Linkquality"," +
The same applies for all other properties like Firmware, Switch ........

Basically, the change requires that properties only contain property name not deviceName + property name like the code is now.
It would be nice if some developer with access to this repo apply changes and release a version with the fix in it. Really simple changes.

I was able to fix, several lines need to be changed: Basically:
Search for "addToPublish" The ones that have line similar with: + ""name":"" + host + " Linkquality"," + Need to be replaced with: + ""name":"Linkquality"," +
The same applies for all other properties like Firmware, Switch ........

which line in the code exactly, do you mean, this + ""name":"" + host + " Linkquality"," +  line?
replace with  that? → (  + ""name":" Linkquality"," + )
also the lines with + ""name":"" + deviceName + " Energy"," +........ need to be replaced?
!are not displayed here! " \ "

It is working for you? I still get the same error in Home Assistant...

Update to HA 2023.8.3 not work , I use the curtain, and ESP32 can detect and work with MQTT, but curtain is not work showing unavailable, roll back to 2023.8.2 is work fine, anyone who updated to 2023.8.3 is work??

Just update , HA 2023.8.4 Work

Same issues here (this issue affect all users).
WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'name': 'esp32 Firmware', 'device': {'identifiers': ['switchbotesp_esp32_00:3C:C6:37:XX:X0'], 'manufacturer': 'WonderLabs SwitchBot', 'model': 'ESP32', 'name': 'esp32', 'connections': []}, 'availability_topic': 'switchbot/esp32/lastwill', 'unique_id': 'switchbotesp_esp32_00:3C:C6:37:XX:X0_firmware', 'icon': 'mdi:cog', 'state_topic': 'switchbot/esp32/esp32/firmware', 'enabled_by_default': True, 'encoding': 'utf-8', 'payload_not_available': 'offline', 'qos': 0, 'payload_available': 'online', 'force_update': False, 'availability_mode': 'latest'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Firmware'

Hope @devWaves will fix it.
Thanks.

Hei... don't wait for devWaves, he will not update this anymore, I am 100% sure.... Instead this, I have another solution, if you use esp32 or similar devices... Try to use ESPHome, and transform your device into an Active Bluetooth device, now Home Assistant will recognize all the switchbot devices, by extending bluetooth range with proxies. I use this code and I can detect and use ALL my switchbot or other bluetooth device...

esphome:
  name: XXXX
  platform: ESP32
  board: esp-wrover-kit

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

captive_portal:
logger:
api:
  encryption:
    key: "XXXX"
ota:

esp32_ble_tracker:
  scan_parameters:
    active: true
bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    name: ${display_name} (Safe Mode)

Hei... don't wait for devWaves, he will not update this anymore, I am 100% sure.... Instead this, I have another solution, if you use esp32 or similar devices... Try to use ESPHome, and transform your device into an Active Bluetooth device, now Home Assistant will recognize all the switchbot devices, by extending bluetooth range with proxies. I use this code and I can detect and use ALL my switchbot or other bluetooth device...

esphome:
  name: XXXX
  platform: ESP32
  board: esp-wrover-kit

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

captive_portal:
logger:
api:
  encryption:
    key: "XXXX"
  ap:
    ssid: XXXX
    password: !secret wifi_password
    ap_timeout: 3min
ota:

esp32_ble_tracker:
  scan_parameters:
    active: true
bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    name: ${display_name} (Safe Mode)

Hello Pickonedev,
Thank you for your infromation, and I search from google, there have a similiar solution
https://www.creatingsmarthome.com/index.php/2023/03/27/guide-bluetooth-proxy-to-home-assistant-using-esphome/
and I haven't process yet, I have a questions, is my ESP32 Dev1 board which is flashed this Switchbot firmware can transfer to ESPHOME, just install ESPHome from HA, and then open ui , Add new device and type SSID, password
then connect the previous ESP32 Dev1 board to USB port and then the ESPHome will flash the board??
If not , please tell me how to flash the ESP32 to match with HA ESP32 Home
Thanks~~~

Hei... don't wait for devWaves, he will not update this anymore, I am 100% sure.... Instead this, I have another solution, if you use esp32 or similar devices... Try to use ESPHome, and transform your device into an Active Bluetooth device, now Home Assistant will recognize all the switchbot devices, by extending bluetooth range with proxies. I use this code and I can detect and use ALL my switchbot or other bluetooth device...

esphome:
  name: XXXX
  platform: ESP32
  board: esp-wrover-kit

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

captive_portal:
logger:
api:
  encryption:
    key: "XXXX"
  ap:
    ssid: XXXX
    password: !secret wifi_password
    ap_timeout: 3min
ota:

esp32_ble_tracker:
  scan_parameters:
    active: true
bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    name: ${display_name} (Safe Mode)

Hello Pickonedev,
Thank you for your infromation, and I search from google, there have a similiar solution https://www.creatingsmarthome.com/index.php/2023/03/27/guide-bluetooth-proxy-to-home-assistant-using-esphome/
and I haven't process yet, I have a questions, is my ESP32 Dev1 board which is flashed this Switchbot firmware can transfer to ESPHOME, just install ESPHome from HA, and then open ui , Add new device and type SSID, password then connect the previous ESP32 Dev1 board to USB port and then the ESPHome will flash the board??
If not , please tell me how to flash the ESP32 to match with HA ESP32 Home
Thanks~~~

Yes, this is all what I have done. I just reflashed my esp with ESPHome. When you do that, ESPHome will erase the device first, then it will write the new code. Easy. Use Chrome Browser for this, Firefox does not have support for COM ports and even with an addon, you can still get errors...

Hei... don't wait for devWaves, he will not update this anymore, I am 100% sure.... Instead this, I have another solution, if you use esp32 or similar devices... Try to use ESPHome, and transform your device into an Active Bluetooth device, now Home Assistant will recognize all the switchbot devices, by extending bluetooth range with proxies. I use this code and I can detect and use ALL my switchbot or other bluetooth device...

esphome:
  name: XXXX
  platform: ESP32
  board: esp-wrover-kit

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

captive_portal:
logger:
api:
  encryption:
    key: "XXXX"
  ap:
    ssid: XXXX
    password: !secret wifi_password
    ap_timeout: 3min
ota:

esp32_ble_tracker:
  scan_parameters:
    active: true
bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    name: ${display_name} (Safe Mode)

Hello Pickonedev,
Thank you for your infromation, and I search from google, there have a similiar solution https://www.creatingsmarthome.com/index.php/2023/03/27/guide-bluetooth-proxy-to-home-assistant-using-esphome/
and I haven't process yet, I have a questions, is my ESP32 Dev1 board which is flashed this Switchbot firmware can transfer to ESPHOME, just install ESPHome from HA, and then open ui , Add new device and type SSID, password then connect the previous ESP32 Dev1 board to USB port and then the ESPHome will flash the board??
If not , please tell me how to flash the ESP32 to match with HA ESP32 Home
Thanks~~~

Yes, this is all what I have done. I just reflashed my esp with ESPHome. When you do that, ESPHome will erase the device first, then it will write the new code. Easy. Use Chrome Browser for this, Firefox does not have support for COM ports and even with an addon, you can still get errors...

Hello pickonedev,
Thank you so much, will try this later!

Hello All,
Just update my status, I use ESPHome BLE Proxy with switchbot work
Just like the previous content, you need to modify config file , board to match with your ESP32 and change the framework
then add ble tracker and bluetooth_proxy to the config
and I have a problem on flash the ESP32, it's stuck on "Preparing Installation"
I googled, and update driver .... press button on the esp32 etc... nothing work
when I want to give us, I switch the broswer from chrome to edge "acutally I check the chrome that can commuicate with ESP32, cause I can screen the log, that's why I didn't alert the problem maybe on the browser"
magically, it's work
For someone who use the chrome and stuck on this "Preparing Installation" over 20mins, then try EDGE
normally this screen may need around 10~20mins , depend on your machine speed, the background is download and compile the firmware.elf
Thanks~

I have now also moved over to ESPHome, relatively easy following the guide posed above by yauyauwind.
I only have contact & motion sensors and 1 light strip so I cant say what else will be found by ESPHome and will be compatible. There has been zero loss in connectivity or delay - in fact I would say it's slightly improved overall, feels more snappy.
The Switchbot LED strip was not part of this repo so I had no control via home assistant, but no I do - although I'm looking to move to WLED and remove all of my old LIFX runs that just randomly lose internet for no reason...

Hello.
For what I know If we switch to ESPHome we can see all our Switchbot Bluetooth devices on Home Assistant.
Well, but personally I need to have MQTT messages on my Broker.
This project "SwitchBot-MQTT-BLE-ESP32" will publish MQTT messages as first main goal, after we can "import" data into Home Assistant (or other systems).
Is it possible via ESPHome to have MQTT messages for all entities (sensors) of all Switchbot Bluetooth devices discovered?
So I would like to have:
Switchbot device -> MQTT -> Home Assistant (like I use with "SwitchBot-MQTT-BLE-ESP32"=
and not:
Switchbot device -> Home Assistant -> MQTT
Thanks!

Hello. For what I know If we switch to ESPHome we can see all our Switchbot Bluetooth devices on Home Assistant. Well, but personally I need to have MQTT messages on my Broker. This project "SwitchBot-MQTT-BLE-ESP32" will publish MQTT messages as first main goal, after we can "import" data into Home Assistant (or other systems).
Is it possible via ESPHome to have MQTT messages for all entities (sensors) of all Switchbot Bluetooth devices discovered? So I would like to have: Switchbot device -> MQTT -> Home Assistant (like I use with "SwitchBot-MQTT-BLE-ESP32") and not: Switchbot device -> Home Assistant -> MQTT
Thanks!

Why do you need them to be In mqtt?
You will be able see all the enity details and be able to control them via Home Assistant with esphome [where applicable]
Esphome replaces the need for this repository as it is out dates and not maintained. You will have all of the same information you get from this repository via mqtt as a device in HA

I need/want sensors data on MQTT because I need to "manage" that sensors data on Linux.
I use some shell script.
More I notice that "SwitchBot-MQTT-BLE-ESP32" is more fast (real real-time) than ESPHome.
With "SwitchBot-MQTT-BLE-ESP32" when my Switchbot Meter Plus change values, the values are sent via MQTT in real-time.
These are the temp values via "SwitchBot-MQTT-BLE-ESP32":

These are the temp values via "ESPHome":

As you can see, with "SwitchBot-MQTT-BLE-ESP32" we have a better view of all values.

and, using ESPHome, the charts on Home Assistant are updated every 5 minutes (and the charts have min/average/max values),
Instead, using "SwitchBot-MQTT-BLE-ESP32", the charts on Home Assistant are updated every times there is a new value returned from the sensor.

Hello all.
For those want to solve the the Waring "MQTT entity name starts with the device name in your config... this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes..."
this what I have done and it works for me.
Replace the line 3154 from:
+ "\"name\":\"" + host + " Linkquality\"," +
to:
+ "\"name\":\"Linkquality\"," +
Replace the line 3156 from:
+ "\"uniq_id\":\"switchbotesp_" + host + "_" + wifiMAC.c_str() + "_linkquality\"," +
to:
+ "\"uniq_id\":\"switchbotesp_" + wifiMAC.c_str() + "_linkquality\"," +
Replace the line 3162 from:
+ "\"name\":\"" + host + " Firmware\"," +
to:
+ "\"name\":\"Firmware\"," +
Replace the line 3165 from:
+ "\"uniq_id\":\"switchbotesp_" + host + "_" + wifiMAC.c_str() + "_firmware\"," +
to:
+ "\"uniq_id\":\"switchbotesp_" + wifiMAC.c_str() + "_firmware\"," +
More you need to edit some other code in the "device" part, according on which SwitchBot device you use,
Since I use only for Meters (as SwitchBot devices), I changed only the Meters part.
Scrolling down I arrived to line 3417 and I starts the replacements after this line (so do not edit line 3417).
Replace the line 3423 from:
+ "\"name\":\"" + deviceName + " Battery\"," +
to:
+ "\"name\":\"" + " Battery\"," +
Replace the line 3432 from:
+ "\"name\":\"" + deviceName + " Linkquality\"," +
to:
+ "\"name\":\"" + " Linkquality\"," +
Replace the line 3441 from:
+ "\"name\":\"" + deviceName + " Temperature\"," +
to:
+ "\"name\":\"" + " Humidity\"," +
Replace the line 3451 from:
+ "\"name\":\"" + deviceName + " Humidity\"," +
to:
+ "\"name\":\"" + " Humidity\"," +
It works for me without any issues.
Generally you should remove the "deviceName" after `+ ""name":""'.
Hope this can help you.

Thanks to @iz8mbw , I've created a fork that incorporates his changes. I haven't had the chance to test it yet.
https://github.com/NewsGuyTor/SwitchBot-MQTT-BLE-ESP32/blob/patch-1/Arduino IDE Files/SwitchBot-BLE2MQTT-ESP32.ino


should update introduction docs

to reflect our current and future vision, mission and values.

@hoavt please verify


Documentation on CurseForge is gone

I can't find the documentation anywhere, please repost it

I know its a bit late but they're in the Pages tab on CF. https://www.curseforge.com/minecraft/mc-mods/custom-main-menu/pages/custom-main-menu/

Nope


[SPARK-6194] [PySpark] fix memory leak in collect()

Because circular reference between JavaObject and JavaMember, an Java object can not be released until Python GC kick in, then it will cause memory leak in collect(), which may consume lots of memory in JVM.
This PR change the collect() to get the iterator from JVM directly (avoid a method call iterator()), it also fix a bug in py4j, which will create a Java member for all the JavaObject parameters.
cc @JoshRosen

Test build #28324 has started for   PR 4923 at commit 9517c8f.

This patch merges cleanly.

It looks like we take the result of collectAsIterator and end up passing it back into Java to save it to the temporary file.  Do you think that we should just skip this layer of indirection and save it to a temporary file in the JVM then return that file's path back to Python?

Test build #28324 has finished for   PR 4923 at commit 9517c8f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28324/
Test FAILed.

I had some thought of that, found that by separating these two then we can reuse writeToFile() for runJob(), should we change all of them to use socket to transfer data?

Test build #28331 has started for   PR 4923 at commit ba54614.

This patch merges cleanly.

Test build #28331 has finished for   PR 4923 at commit ba54614.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28331/
Test FAILed.

Test build #28347 has started for   PR 4923 at commit 24c92a4.

This patch merges cleanly.

Test build #28347 has finished for   PR 4923 at commit 24c92a4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28347/
Test PASSed.

Now that this has been updated to collect results via a socket, it looks like we may finally be able to close https://issues.apache.org/jira/browse/SPARK-677, one of the oldest Spark issues.

This looks really good to me overall.  It would be great if you could update the PR description to reflect the most recent changes (collecting via a socket instead of a temporary file).
A couple of quick questions:

Does this have a performance impact (positive or negative)?
Do we need to write any additional tests?  Are there any corner cases that we should explicitly address in their own tests, such as not consuming the iterator or not connecting to the socket after creating it?

Test build #28405 has started for   PR 4923 at commit d730286.

This patch merges cleanly.

@JoshRosen This should have positive performance impact, the end-to-end time of a job (collect 50M integers) changed from 10.6s to 9.2s.
For the additional failure tests, it's nice to have. I'd like leave them out of this PR, do it later if we really need it.
I think we should backport this as-is to maintenance branches.

LGTM; I'll merge this as soon as Jenkins passes.  Thanks!

Test build #28405 has finished for   PR 4923 at commit d730286.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28405/
Test PASSed.

I've merged this into master (1.4.0) and branch-1.2 (1.2.2).  I'll edit the JIRAs to add a reminder to backport this to 1.1.x and 1.3.1.

I have now cherry-picked this into branch-1.3 (1.3.1).

Note that this patch introduced a bug which can call collect() to hang under certain rare circumstances: https://issues.apache.org/jira/browse/SPARK-6667.  This bug should be fixed in #5324.


Remove dependency to mineflayer

plugins should not depend on mineflayer
Can have a dev dependency to it for examples

done


iPhone5 (iOS 10) isn't protected from screenshot

I thought PrivacyScreenPlugin applied iOS7 means iOS version(something like 10.2.1).
I tested this on iPhone 5s (10.2.1) but this wasn't work properly, and just normal screenshot works well. (but android works fine)
Is there anything I miseed? or old iPhone 5 or 6 isn't applied for this module?
What I want is just black screen or any protection from the screenshot on my app.
Thanks.
Expected Behaviour
Screenshot isn't applied or black screen saved
something like android does
Actual Behaviour
Screenshot works normally on iPhone 5s (os version 10.2.1) devices
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Cordova CLI version and cordova platform version
cordova --version                                    # e.g. 6.0.0

6.4.0
cordova platform version android                     # e.g. 4.1.1

Plugin version
cordova plugin version

Sample Code that illustrates the problem
Logs taken while reproducing problem

@MeteorStartup
Test:

Device
OS
Version
Cordova
Android
iOS
BLACK-Screen available?
Can do screenshots?
Plugin work OK

iPad
iOS
10.0.2
6.5.0
4.3.1
-
YES
YES
NO

Samsung S3 Neo
Android
4.4.2
6.5.0
-
6.1.2
YES
NO
YES

@MeteorStartup  / @devgeeks
any news?

UIApplicationUserDidTakeScreenshotNotification posted when the user presses the Home and Lock buttons to take a screenshot. This notification does not contain a userInfo dictionary. This notification is posted after the screenshot is taken.
- (void)viewDidLoad
{
    [super viewDidLoad];
    // Do any additional setup after loading the view from its nib.
    NSLog(@"FIRE viewDidLoad()");

    NSOperationQueue *mainQueue = [NSOperationQueue mainQueue];
    [[NSNotificationCenter defaultCenter] addObserverForName:UIApplicationUserDidTakeScreenshotNotification
                                                      object:nil
                                                       queue:mainQueue
                                                  usingBlock:^(NSNotification *note) {
                                                      // executes after screenshot
                                                      NSLog(@"FIRE UIApplicationUserDidTakeScreenshotNotification");
                                                  }];
}

AFAIK, blocking screenshots is not possible on iOS.
It was never an intended feature on iOS. It is only a feature in Android because it is part of the flag used to prevent the display of the paused app in the task switcher.

ok, thank you!


feat!: prepended OneTrust to tracking integrations loads

Overview

Adds OneTrust initialization to the initializeTrackingIntegrations call per the Delay Loading OneTrust RFC.

I'm working on testing it out directly in the monolith with a feature flag now: https://github.com/codecademy-engineering/Codecademy/pull/24430
This is also being tested in portal-app: https://github.com/codecademy-engineering/portal-app/pull/39
Notes
Removes any runtime dependency on React from the tracking package. Yay, portability!
PR Checklist

~[ ] Related to designs:~
[x] Related to JIRA ticket: WEB-1422
[x] I have run this code to verify it works
~[ ] This PR includes unit tests for the code change~

📬Published Alpha Packages<EMAIL_ADDRESS>
📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://609c3bcc063003272ec8b52e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60a29d4c30595c009d0b46f8--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60abb17deedff70dcfc738e8--gamut-preview.netlify.appDeploy Logs


Where is current page class?

Sorry for the late response. The class is '.item_page.active', hope it helps.


GitHubSource reports obscure error with incorrect scopes

When I try to use GitHubSource to create an organization-level scope, unless my access token has the "admin:org_hook" scope I get the following error:
failed to create webhook: failed to create the webhook: POST https://api.github.com/orgs/knative/hooks: 404 Not Found []

cc @grantr

test comment


Fix for #6 < unable to use single xeditable form elements (without whole form editing) + use angular's form validation

This fix addresses http://github.com/vitalets/angular-xeditable/issues/6)
To use, simply include e-single on any element you wish to 'ignore' the hasForm variable.
Example:
{{ person.FirstName || \'First Name\' }}
Passes JShint

I'm going to submit this from a new branch on my fork


Add Nix Flake for Latest Postgres Driver

Added in https://github.com/rupurt/odbc-scanner-duckdb-extension/pull/23


GDExtension classes inheriting from Resource are not using icons in FileSystem

Tested versions
4.3 dev 1
System information
Windows 10 Godot 4.3 dev 1 Vulkan
Issue description
I am aware there is https://github.com/godotengine/godot/issues/32706, but it does not seem to cover GDExtensions.
Currently, GDExtension classes inheriting from Resource are not using icons in FileSystem. It seems to work in every other place, but not in FileSystem for some reason.

Steps to reproduce

Create a class in GDExtension that inherits Resource
Assign an icon in .gdextension file to said class
Observe how FileSystem is using default icon for this class, while the property viewer is displaying everything as expected

Minimal reproduction project (MRP)
You can see an example in the root of the project here

IconTest.zip

I tested it and found the same problem when using gdscript to inherit resource subclasses.


CI

Fixes #108

@ChrisRackauckas did something change in solution indexing (yesterday?) https://github.com/ODINN-SciML/DiffEqSensitivity-Review/actions/runs/9492247292/job/26159059628?pr=112#step:5:1412
All the scripts were working locally just yesterday for me.

Ok Zygote with ODESolution seems pretty much broken right now :(

@avik-pal any idea of what is causing the error? Should I wait to integrate this PR?
I ran all in local today and worked perfectly well.

One of the big changes around symbolic indexing seems to have broken master. We're doing a hotfix:

https://github.com/SciML/SciMLBase.jl/pull/716

Retrigger


Enforce no export * in eslint

As part of converting all the export *'s to named exports, we need to enforce that future PRs cannot introduce any export *s. This PR introduces an eslint rule that will enforce this.
Related Issue: https://github.com/microsoft/FluidFramework/issues/10062

And made me curious if there's a reason we still have the eslint7.js file when the only place it seems to be used/extended (in our repo, at least) is minimal.js, so I'm tempted to merge them. But we'd need to know if an internal partner is using it.

There's no need for the eslint7.js file anymore. It was used when we migrated to eslint8 awhile back, to make it easier to gradually upgrade. My (quite old) PR #9748 is the ultimate direction we've been going with the config, and you'll note that the eslint7.js file is gone in that PR.
I don't think we'll merge that PR in as-is, but it represents the direction we've been heading. @Josmithr may have more to add, but I think it's OK to leave as-is for now.

I would recommend enabling this rule in our strict config, rather than in the base ones. I'm not sure every package will necessarily want this rule. Then we can update the packages we want to prioritize to use the strict config on a package-by-package basis.
For what it's worth, I think using our strict api-extractor config, which enforces that anything transitively exposed in the public API is explicitly enumerated in the root package export, gets us the same sort of enforcement we're looking for here without needing to forbid export *. This only works for packages using API-Extractor, but I think all of our library packages should be using that anyways.

I would recommend enabling this rule in our strict config, rather than in the base one(s). I'm not sure every package will necessarily want this rule. Then we can update the packages we want to prioritize to use the strict config on a package-by-package basis.

I think @ghoshkaj has gone to great lengths to make it possible for us to enable this rule across the repo, so I'd rather get this into the minimal config.

I guess my other concern with forbidding this pattern wholesale is that it removes the ability to use export * in package sub-directories.

I think we should be treating subdirectories as modules with an explicit API. There was a discussion about this recently; I'll find a link. From that discussion, @ChumpChief pointed out:

The main problem I've hit with subdirectory organization is that it can cause tension with the no-internal-modules rule.  a naive response to that lint error might be to over-export subdirectory contents, in the worst case unintentionally exporting internal concepts across the package boundary if they're not careful.

And @CraigMacomber mentioned:

packages/dds/tree has lots of directories under src, each with their own index. I like this pattern as it allows for more scope control. We also use good-fences to control deps between the folders. We just suppress the import restriction for the specific file under test, and leave it on for everything else.

This is also the pattern I adopted in build-cli, sans the readme (which I should add).

I would recommend enabling this rule in our strict config, rather than in the base one(s). I'm not sure every package will necessarily want this rule. Then we can update the packages we want to prioritize to use the strict config on a package-by-package basis.

I think @ghoshkaj has gone to great lengths to make it possible for us to enable this rule across the repo, so I'd rather get this into the minimal config.

I guess my other concern with forbidding this pattern wholesale is that it removes the ability to use export * in package sub-directories.

I think we should be treating subdirectories as modules with an explicit API. There was a discussion about this recently; I'll find a link. From that discussion, @ChumpChief pointed out:

The main problem I've hit with subdirectory organization is that it can cause tension with the no-internal-modules rule.  a naive response to that lint error might be to over-export subdirectory contents, in the worst case unintentionally exporting internal concepts across the package boundary if they're not careful.

And @CraigMacomber mentioned:

packages/dds/tree has lots of directories under src, each with their own index. I like this pattern as it allows for more scope control. We also use good-fences to control deps between the folders. We just suppress the import restriction for the specific file under test, and leave it on for everything else.

This is also the pattern I adopted in build-cli, sans the readme (which I should add).

Ah, okay. If we're in good shape to enable globally, then I'm more comfortable with this. I think we might end up with some tool-wise enforcement overlap between eslint, api-extractor, good-fences, etc., but we can always re-evaluate / loosen tooling requirements later as we want.

If we could enforce this only for the package root export module, that would be fantastic.

An override that filtered just the root index.ts and applied the rule only to that should accomplish what you're describing. We do something similar for test files: https://github.com/microsoft/FluidFramework/blob/e9155b8ea8e7262ae9d1c3bee9b95b3a98a542eb/common/build/eslint-config-fluid/minimal.js#L288-L304

If we could enforce this only for the package root export module, that would be fantastic.

An override that filtered just the root index.ts and applied the rule only to that should accomplish what you're describing. We do something similar for test files:
https://github.com/microsoft/FluidFramework/blob/e9155b8ea8e7262ae9d1c3bee9b95b3a98a542eb/common/build/eslint-config-fluid/minimal.js#L288-L304

That would match my personal preferences nicely and would let us further discuss how we want to manage sub-package hierarchies going forward, while still giving us more granular package API control.
But I'm also happy with this as is - we can always loosen these requirements at a later date if we decide we would prefer not to enforce in package sub-directories.


bug: Module not found: Can't resolve 'ethers'

Package Version
1.3.6
Current Behavior
I get the following error when trying to SIWE with the latest version of wagmi.
./node_modules/siwe/dist/ethersCompat.js:5:0
Module not found: Can't resolve 'ethers'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/siwe/dist/client.js
./node_modules/siwe/dist/siwe.js
./src/pages/closet/index.page.tsx

When I set the wagmi version to 1.1.0, the error no longer occurs.
Other versions
"next": "^13.4.8",
"viem": "^1.2.9",
"siwe": "^2.1.4",

Might be worth raising this issue on the siwe repo? Seems like it's coming from there.


[Bug]: Inbucket's json file has an invalid value for INBUCKET_WEB_UIDIR

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
inbucket
Expected/Current Behaviour
This value is not correct for the current version of inbucket:
"INBUCKET_WEB_UIDIR": "$dir\\ui"

As a result, inbucket will not work without overriding this with an environment variable. The correct value is $dir\\ui\\dist.
Steps to Reproduce
PS> scoop install inbucket
...
PS> inbucket

Open web browser to http://servername:9000 where you will see the message "Failed to parse HTML template".

Possible Solution
Correct the value to:
"INBUCKET_WEB_UIDIR": "$dir\\ui\\dist"

Scoop and Buckets Version
PS> scoop --version
Current Scoop version:
859d1db5 (HEAD -> master, tag: v0.5.2, origin/master, origin/HEAD) chore(release): Bump to version 0.5.2 (#6080)

'main' bucket:
fa68ef2df (HEAD -> master, origin/master, origin/HEAD) uv: Update to version 0.4.2

'extras' bucket:
23bd88941 (HEAD -> master, origin/master, origin/HEAD) sidekick-browser: Update to version <IP_ADDRESS>405-4e57373

'sysinternals' bucket:
6b2b695 (HEAD -> main, origin/main, origin/HEAD) sysmon: Update to version 15.15

'nonportable' bucket:
f55b2aba (HEAD -> master, origin/master, origin/HEAD) 10x-np: Update to version 1.0.203

Scoop Config
PS> scoop config

last_update                       proxy               scoop_repo                              scoop_branch
-----------                       -----               ----------                              ------------
2024-09-01T17:53:27.7954104-04:00 <IP_ADDRESS>:9888 https://github.com/ScoopInstaller/Scoop master

PowerShell Version
PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.20348.2652
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.20348.2652
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Additional Softwares
No response

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

Relates to inbucket/inbucket#525.


[question] External Server when should I use it?

[question] External Server when should I use it? i often hear cut voice from others, from rp-radio when somebody talking while going fast with vehicle, if I use external server, should it be better or no?

External server for above 120+ members would be enough not really matters if you have a server under 100

so it should help to remove player voice suttering ?

You shouldn't need to use an external server until 400-600 players, if you're having voice stuttering before this check and make sure you're not capping your bandwidth.


Install packages needed for quarto to knit to PDF

Package list comes from the log provided by
Nathan in https://2i2c.freshdesk.com/a/tickets/952, listing the packages needed by quarto PDF knitting.
Ref https://github.com/2i2c-org/infrastructure/issues/2729

Pushed upstream to https://github.com/rocker-org/rocker-versioned2/pull/741

Adding this here for now as this works its way upstream.


Initial proposal for collaboration on lakeFS merge

The proposal should offer some initial way to collaborate on top of a lakeFS change (merge, commit)

Collaboration isn't on the roadmap for now.