Unable to find 7z on Linux,  "No such file or directory"

OS: Linux Mint 21.2
In a terminal:
$ whereis 7z
7z: /usr/bin/7z /usr/share/man/man1/7z.1.gz

Then I enable external archiver in settings and set /usr/bin/7z as the file archiver path for Unix. When I make a backup or one is made automatically, I get the "No such file or directory /usr/bin/7z
For me, /usr/bin/7z is a shell script just containing
exec /usr/lib/p7zip/7z, but when I try that path I get the same error

Hi, try to install p7zip. :)

Hi, try to install p7zip. :)

I had p7zip installed on both my laptop and desktop and saw the same issues on both. On my laptop the path for the 7z executable is /usr/lib/p7zip/7z by default, and i get the error whether i use that or /usr/bin/7z

Hi, maybe I reproduced your problem, I installed pyzip on my ubuntu 22.04 (WSL), and after I typed /usr/bin/p7zip -h, it didn't show the command I need:
Usage: /usr/bin/p7zip [options] [--] [ name ... ]

Options:
    -c --stdout --to-stdout      output data to stdout
    -d --decompress --uncompress decompress file
    -f --force                   do not ask questions
    -k --keep                    keep original file
    -h --help                    print this help
    --                           treat subsequent arguments as file
                                 names, even if they start with a dash

So I tried to type /usr/bin/7 and click "tab" button, I finally found the file we need: /usr/bin/7zr:
cgc@DESKTOP-UFCDD51:~$ /usr/bin/7zr -h

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C.UTF-8,Utf16=on,HugeFiles=on,64 bits,24 CPUs 13th Gen Intel(R) Core(TM) i7-13700K (B0671),ASM,AES-NI)

Usage: 7za <command> [<switches>...] <archive_name> [<file_names>...]
<EMAIL_ADDRESS>
<Commands>
  a : Add files to archive
  b : Benchmark
  d : Delete files from archive
  e : Extract files from archive (without using directory names)
  h : Calculate hash values for files
  i : Show information about supported formats
  l : List contents of archive
  rn : Rename files in archive
  t : Test integrity of archive
  u : Update files to archive
  x : eXtract files with full paths
...

So, the solution is replace /usr/bin/7z with /usr/bin/7zr, thank you for using and hope this helps.

7zr and 7za both didn't work for me

7zr and 7za both didn't work for me

Hi, use Ctrl+Shift+I in Obsidian, then run local backup once to see the log, and share me the log if possible.

Or install p7zip-full instead of p7zip, and try again.

command: "/usr/bin/7z" a "/home/jay/Documents/ObsidianBackup/Obsidian-Backup-2024_02_19-00_40_59.7z" "/home/jay/Documents/Obsidian"

Failed to create file by 7-Zip: Error: Command failed: "/usr/bin/7z" a "/home/jay/Documents/ObsidianBackup/Obsidian-Backup-2024_02_19-00_40_59.7z" "/home/jay/Documents/Obsidian"
/bin/sh: line 1: /usr/bin/7z: No such file or directory

    at __node_internal_genericNodeError (node:internal/errors:867:15)
    at ChildProcess.exithandler (node:child_process:430:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:513:28)
    at Pipe.<anonymous> (node:net:322:12)

Error during archive attempt 1: Error: Command failed: "/usr/bin/7z" a "/home/jay/Documents/ObsidianBackup/Obsidian-Backup-2024_02_19-00_40_59.7z" "/home/jay/Documents/Obsidian"
/bin/sh: line 1: /usr/bin/7z: No such file or directory

Failed to create vault backup after 1 attempts.

Strange because when i try to manually run the command from the first console log it works just fine

Almost identical errors with 7za and 7zr

For me, /usr/bin/7z is a shell script just containing
exec /usr/lib/p7zip/7z, but when I try that path I get the same error

Remove this script first.
Then you could try to install p7zip-full, after installation, you can use /usr/bin/7z directly.

p7zip-full

I am on Debian. This still does not work


very slow

We have written the needed data into your clipboard because it was too large to send. Please paste.

Very bad issue description


Asuswrt for 0.83 gives occasional errors.

**Home Assistant release with the issue: ** 0.83.0b0

Last working Home Assistant release (if known): none, new module
Operating environment (Hass.io/Docker/Windows/etc.): Docker (but not relevant in this case)

Component/platform: asuswrt sensor https://www.home-assistant.io/components/asuswrt/ https://www.home-assistant.io/components/sensor.asuswrt/

Description of problem: The log is filled with errors as the sensor lacks a few checks.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
asuswrt:
   host: <IP_ADDRESS>
   username: !secret asuswrt_user
   port: 22
   ssh_key: /config/ssh_key

Traceback (if applicable):
Update for sensor.asuswrt_upload fails

Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity.py", line 221, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/app/homeassistant/helpers/entity.py", line 347, in async_device_update
    await self.async_update()
  File "/usr/src/app/homeassistant/components/sensor/asuswrt.py", line 126, in async_update
    self._state = round(self._rates[1] /<PHONE_NUMBER>, 1)
IndexError: list index out of range

Additional information:

@kennedyshead Perhaps you are missing a test if the data is correct.

This should be in the aioasuswrt rather than in home-assistant

Oh! no my bad! Ofc. it should be fixed in hass


Use os.remove to remove generated .biom file

This PR implements a simple solution to the problem illustrated in issue #1990. It also includes some formatting changes to the file made by ruff.
Please complete the following checklist:

[ ] I have read the contribution guidelines.

[x] I have documented all public-facing changes in the changelog.

[ ] This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the licenses directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied.

It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.

[x] This pull request does not include code, documentation, or other content derived from external source(s).

Note: This document may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.

@wasade Do you see any issue in handling things with os.remove?

@wasade Do you see any issue in handling things with os.remove?

Specifically, we were a bit concerned whether writing a file in the current directory might cause an issue if skbio is installed into a non-writable directory (e.g., through sudo apt install skbio). We attempted to do this in a writtable temporary directory by Sphinx decoratives .. testsetup:: and .. testcleanup::. However, they didn't work despite our trying. Therefore, we had to give up but simply use os.remove to delete the file in the current directory.

Does writing to an instance of io.BytesIO work here? see eg:
In [7]: f = io.BytesIO()

In [8]: fp = h5py.File(f, 'w')

In [9]: biom.example_table.to_hdf5(fp, 'asd')

@qiyunzhu @wasade I made a new commit with a io.BytesIO solution, but I'm not sure if it's exactly what we want.

@wasade @mataton I did some research and found that .. testsetup:: could not be triggered because we are using pytest instead of Sphinx's make doctest to run the doctests. The latter would make the doctests more flexible. There are additional limitations associated with the pytest method (e.g., you can't run a single doctest). This can potentially be addressed in the future.


[Bug] Nesting Wildcards

Trying to use nesting is breaking the entire extension for me.
To Reproduce

Put a nested prompt into positive containing wildcards. For example: {__season__,__outdoor__,__time__|__indoor__,__time__}
Click on Generate.
See error.

Expected behaviour
It should process both wildcards and the nested prompts.
Additional context
Traceback (most recent call last):
  File "/home/miyuu/stable-diffusion-webui/modules/scripts.py", line 338, in process
    script.process(p, *script_args)
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/scripts/dynamic_prompting.py", line 409, in process
    all_prompts = generator.generate(num_images)
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 203, in generate
    all_prompts = [self.generate_prompt(self._template) for _ in range(num_prompts)]
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 203, in <listcomp>
    all_prompts = [self.generate_prompt(self._template) for _ in range(num_prompts)]
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 194, in generate_prompt
    prompt = self.pick_variant(old_prompt)
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 179, in pick_variant
    return re_combinations.sub(lambda x: self._replace_combinations(x), template)
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 179, in <lambda>
    return re_combinations.sub(lambda x: self._replace_combinations(x), template)
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 158, in _replace_combinations
    collected = collector.collect((low_range, high_range))
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 75, in collect
    picked = self._selector.pick()[0]
  File "/home/miyuu/stable-diffusion-webui/extensions/sd-dynamic-prompts/prompts/generators/randomprompt.py", line 41, in pick
    picked.append(self._random.choice(option))
  File "/usr/lib/python3.10/random.py", line 378, in choice
    return seq[self._randbelow(len(seq))]
IndexError: list index out of range

I have only been able to reproduce this while using the same wildcards nested. So for example if I simply have {__indoor__|__outdoor__} it works fine but {__indoor__|__indoor__,cat} will break. When this occurs it fails to process all wildcards in the prompt, even those not nested. However if I was to do {__indoor__|__outdoor__},__indoor__ it would work fine, so it seems unrelated to using the same wildcard twice outside of nesting purposes. I assume contents of wildcards doesn't matter since I can reproduce this even with wildcards with two random items in them but if necessary I can provide some.
Furthermore it seems I'm only able to reproduce this on certain seeds. For example I have been able to reproduce it on 3714. Despite this selecting "Unlink Seed From Prompt" does not resolve the issue.

Thanks for reporting this. I'll look into it, but only in a few days

Could you please test the latest version -  v1.4.1?

Thanks! It does appear to be fixed now! The only thing I would say is there seems to be a new minor issue. With every generation with the script enabled I'm now seeing INFO:dynamic_prompting.py:Prompt matrix will create 1 images in a total of 1 batches. regardless of whether I'm using any wildcards or functionality. I don't believe it has any actual impact however and I haven't the time right now to do a lot of testing but otherwise seems fine.


Remove a redundant trailing backquote

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[x] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

/retest e2e-bookInfoTests-envoyv2-v1alpha3-master

/test e2e-bookInfoTests-envoyv2-v1alpha3-master


Clear out Rubocop ToDos

Coverage increased (+4.4%) to 93.117% when pulling 3446204b3befcc3f81e08dbb1885c5fb0c6090a0 on further-adventures-in-rubocop into 680e4cfb413e5bd9e924cf7292f4b6828462d417 on master.


[e2e]: go release main config-ldflags-assets-tag slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v23.0.591
Run: https://github.com/slsa-framework/example-package/actions/runs/7706110559
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-assets-tag.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.release.main.config-ldflags-assets-tag.slsa3.yml
Trigger: release
Branch: v23.0.591
Date: Tue Jan 30 04:08:51 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v23.0.592
Run: https://github.com/slsa-framework/example-package/actions/runs/7721032714
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-assets-tag.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.release.main.config-ldflags-assets-tag.slsa3.yml
Trigger: release
Branch: v23.0.592
Date: Wed Jan 31 04:08:48 UTC 2024


SET ROLE statement problem on clustered instances

Describe the bug
SET statement is not working with clustered instances
See https://github.com/ClickHouse/ClickHouse/discussions/40924
Steps to reproduce

Install the latest version of driver
Bring up a clickhouse instance (clustered)
Add the instance and try to run query on that

Expected behaviour
Use HTTP Params or disable impersonation on clustered instances
Error log
Configuration
Environment

metabase-clickhouse-driver version: 1.2.1
metabase-clickhouse-driver configuration: Default
Metabase version: v1.47
OS: Docker with K8s

ClickHouse server

ClickHouse Server version: 22.8
ClickHouse Server non-default settings, if any: Not Needed
CREATE TABLE statements for tables involved: Not Needed
Sample data for all these tables, use clickhouse-obfuscator if necessary

Any updates on this?
I was into fix that but I have a problem where I don't know what are the props of the first argument of  (driver) in set-role-statement
I think adding a property in driver and user select that if ClickHouse instance is clustered or not, If yes this method can return empty string
https://github.com/ClickHouse/metabase-clickhouse-driver/blob/master/src/metabase/driver/clickhouse.clj#L203

@mhkarimi1383, this is clearly an overlook from me. I think this feature should be turned off for now, as SET ROLE and other session-level commands are currently limited to a particular node even with session usage, which essentially renders them useless with pooled connections as they are executed as separate statements and there is no guarantee that the consecutive requests will use the same connection and inherit what was previously set there.
Stay tuned.

@slvrtrn Thanks, Also adding clustered ClickHouse to the current docker compose setup for testing will be great 😃

@mhkarimi1383, I think it will introduce some complications as datasets are ENGINE Memory, and many of them are created in place, and we need to use wait_end_of_query and other parameters to ensure that the data is synchronized across the nodes, etc, etc...
But I agree that adding both an on-premise cluster of two nodes and ClickHouse Cloud to the mix is highly beneficial (that's how clickhouse-js CI is set up)

@slvrtrn If it's okay I will add clustered ClickHouse docker compose setup

@mhkarimi1383, you could try (we already have a sample setup available, for example, here with all the necessary configs).
Don't expect that it will work out of the box, though. Some additional changes will be needed depending on cluster/non-cluster setup. E.g., how dataset DDLs look like, what additional options to pass (at least wait_end_of_query=1 for cluster), and many other things.
See how different table creation is for single-node/cluster/CH Cloud in clickhouse-js tests: https://github.com/ClickHouse/clickhouse-js/blob/main/packages/client-common/tests/fixtures/simple_table.ts#L23-L48
Client instance is also different across these:

General settings (all queries) https://github.com/ClickHouse/clickhouse-js/blob/main/packages/client-common/tests/utils/client.ts#L36-L41
DDLs settings: https://github.com/ClickHouse/clickhouse-js/blob/main/packages/client-common/tests/utils/client.ts#L114-L117

To add a bit more: many tests use datasets created in place using tx/dataset-definition calls. ON CLUSTER part should also be squeezed in there somehow.

@slvrtrn Yeah I see, but I will try to do it as much as I can 😁

@mhkarimi1383, please try https://github.com/ClickHouse/metabase-clickhouse-driver/releases/tag/1.2.2

@mhkarimi1383, please try https://github.com/ClickHouse/metabase-clickhouse-driver/releases/tag/1.2.2

I will do it today

@slvrtrn fix, thank you :)

I am closing this, as the offending feature was disabled in the end, and unblocked the driver usage on clustered instances.
Proper implementation of the "connection impersonation" feature that correctly works with clusters will be tracked in this one: https://github.com/ClickHouse/metabase-clickhouse-driver/issues/219


Make build operator leader durations configurable

In case the build operator needs to be started with very specific leader
lease duration configuration, there is currently no way to configure it.
Introduce new section in build configuration that contains some of the
manager options to be configurable and passed through to the manager.
Pass new section values as-is into the manager options for the build
operator setup. Any nil value will result in the default value.
Add four new environment variables to override these settings:

BUILD_OPERATOR_LEADER_ELECTION_NAMESPACE
BUILD_OPERATOR_LEASE_DURATION
BUILD_OPERATOR_RENEW_DEADLINE
BUILD_OPERATOR_RETRY_PERIOD

Please note: All duration based environment variables use the time duration
parse function, so they expect an input like 42s.

A comment:

Please review the comments and default value settings on OpenShift in issue: https://github.com/shipwright-io/build/issues/414
There is no document to tell how to set it
Please fix the Conflicting files: cmd/manager/main.go


log duration of health checks

OVH is having trouble, in large part due to very slow health checks
but there's currently no way to tell what's being so slow
I have a hunch that it's queued requests in the shared executor used to talk to k8s (and ultimately caused by the k8s API being slow), but that's just a guess. Could be the registry as well.
This should help us identify what's wrong, at least.

Tests are caused by k3s latest isn't so stable, because they upload artifacts a while after updating the release channel "latest".


GEODE-8455: Fix difference between create region with gw sender and a…

…lter region with gw sender
Geode behaves differently with respect to transactions when
creating a partitioned region with a parallel gateway sender to
when first the partitioned region is created and then the
parallel gateway sender is added by altering the region.
In the first case (create region with gateway sender), when
sending a transaction for the region, an event is sent
to each server hosting the bucket for the data in the transaction.
In the second case (create region + alter region),
when sending a transaction for the region, an event
is sent to every cache member and not only to those hosting
the bucket for the data in the transaction. This leads to,
in the servers not hosting the bucket for the data,
that the events are stored in the
bucketToTempQueueMap member variable of the
ParallelGatewaySenderQueue.
The behavior in the first case is the right one.
The wrong behavior is provoked by the setting to true of the
requiresNotification variable of the PartitionedRegion
by the distributeUpdatedProfileOnSenderCreation method.
This method should only set this variable to true
in case the sender is serial as it is done when
a partitioned region is initialized.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

A few small changes to clean up the code a bit. I also notice that there are several DUnit test failures associated with this change (more than we would expect just due to the known flakiness of some WAN DUnit tests) so I would prefer not to merge this change until they have been diagnosed and remedied.
Also, while it's not strictly within the scope of this PR, I notice that in WANTestBase.createSender() line 1747, the call to gateway.create(dsName, remoteDsId); comes before the call to gateway.setBatchTimeInterval(batchTimeInterval); which means the second call has no effect on the batch time interval. If fixing this has no effect on existing tests, then it would be okay to include it as part of this PR, I think. If fixing it causes tests to start failing, a separate JIRA ticket should be created to address the changes.

@DonalEvans Thanks a lot for your comments. You have an incredible eye to find every error and identify items to improve.

I have added a fix for the distributed tests that were failing.
I have incorporated all the fixes you have suggested in your comments.
I have also tackled the issue you mentioned regarding WANTestBase.createSender() when specifying a batchTimeInterval. The way to address it has been to remove the parameter from the method as it had no effect anyway. I think it was me the one who introduced it in the first place when I implemented the "GEODE-7971" and was trying to fix some flaky tests. But obviously, that parameter did not have anything to do to the fix of the test cases.


json-formatter

cant it use for android phone....thank u

Here is a tool website you can try, not plug-in oh   :)
https://www.jsonformatting.com/jsonformat


Scale Relative to distance hides the annotations

When   self.scaleRelativeToDistance = true  then no annotations are displayed at all. Any ideas?

@azamsharp You need to implement SceneLocationViewDelegate methods

Hello, were you able to solve this? When I set a LocationAnnotationNode's scaleRelativeToDistance to true, the annotations are not displayed. I have these functions implemented:
sceneLocationViewDidAddSceneLocationEstimate, sceneLocationViewDidRemoveSceneLocationEstimate, sceneLocationViewDidConfirmLocationOfNode,
sceneLocationViewDidSetupSceneNode, and
sceneLocationViewDidUpdateLocationAndScaleOfLocationNode

It probably is displaying them, just scaled very small so that you can't see them. It's very sensitive. Try plotting a node very close to your location.

@azamsharp as @marcshilling said, it might appear really tiny if you enable scaleRealtiveToDistance since the library doesn't apply adjustment to make the node bigger. Try adding some scale to annotationNode to make it bigger to see if you can see them.

it is too small

Closing this issue - it's old and stale.

I am willing to change the scale relative to distance boolean value based on users selection on segmented control. To provide user flexibility of selecting the modes 1. To view distant landmarks and 2. To view nearby landmarks scaled relative to the user's current location. HOW CAN I DO THAT?


Typo: nodejs DropletSlugs consts use VPCU, should be VCPU

Guess fixing this would break existing scripts, but it sure looks weird when reading 🤔
See e.g.: https://github.com/pulumi/pulumi-digitalocean/blob/master/sdk/nodejs/dropletSlug.ts#L30

d'oh! thanks for pointing this our @pjoe
I will mark these old ones as deprecated and then create new ones in the union type!
Paul


chained workspaces and include search path

Ran across some search path problems for includes if you have chained source workspaces sitting on top of released debs.

Old ecl in debs residing in /opt/ros/groovy.
New source workspace for ecl with some changes in /opt/ecl.
Chained workspace for kobuki on top of compiled ecl on top of installed groovy.

I source /opt/ecl/devel/setup.bash and proceed to catkin_make the /opt/kobuki workspace. I got some wierd errors, but just to test clearly, I removed some files that were included in the /opt/ros/groovy/ecl/sigslots.hpp (the one that kobuki calls) so that it would throw an error if it was using /opt/ros/groovy headers before /opt/ecl/src/ecl_core/ecl_sigslots/include headers.
/usr/bin/c++   -Dkobuki_EXPORTS -DROS_BUILD_SHARED_LIBS=1 -fPIC -isystem /opt/ecl/devel/include -isystem /opt/ecl/src/ecl_navigation/ecl_mobile_robot/include -isystem /opt/ecl/src/ecl_lite/ecl_errors/include -isystem /opt/ecl/src/ecl_core/ecl_geometry/include -isystem /opt/ecl/src/ecl_lite/ecl_config/include -isystem /opt/ecl/src/ecl_core/ecl_type_traits/include -isystem /opt/ecl/src/ecl_core/ecl_mpl/include -isystem /opt/ecl/src/ecl_core/ecl_containers/include -isystem /opt/ecl/src/ecl_core/ecl_exceptions/include -isystem /opt/ecl/src/ecl_core/ecl_formatters/include -isystem /opt/ecl/src/ecl_core/ecl_converters/include -isystem /opt/ecl/src/ecl_core/ecl_concepts/include -isystem /opt/ecl/src/ecl_core/ecl_utilities/include -isystem /opt/ecl/src/ecl_core/ecl_linear_algebra/include -isystem /opt/ecl/src/ecl_core/ecl_math/include -isystem /opt/ecl/src/ecl_core/ecl_devices/include -isystem /opt/ecl/src/ecl_core/ecl_threads/include -isystem /opt/ecl/src/ecl_core/ecl_time/include -isystem /opt/ecl/src/ecl_lite/ecl_time_lite/include -isystem /opt/ecl/src/ecl_core/ecl_sigslots/include -isystem /opt/ecl/src/ecl_core/ecl_command_line/include -isystem /usr/include/eigen3 -I/opt/kobuki/src/kobuki/kobuki_driver/include    -o CMakeFiles/kobuki.dir/packet_finder.cpp.o -c /opt/kobuki/src/kobuki/kobuki_driver/src/driver/packet_finder.cpp
In file included from /opt/kobuki/src/kobuki/kobuki_driver/src/driver/../../include/kobuki_driver/packet_handler/packet_finder.hpp:27:0,
                 from /opt/kobuki/src/kobuki/kobuki_driver/src/driver/packet_finder.cpp:15:
/opt/ros/groovy/include/ecl/sigslots.hpp:28:31: fatal error: sigslots/signal.hpp: No such file or directory

Bam, it's trying to get stuff from /opt/ros/groovy. Now, why? There is no -I or -isystem for /opt/ros/groovy/include above. That comes from the environment variable configured by /opt/ecl/devel/setup.bash:
CPATH=/opt/ecl/devel/include:/opt/ros/groovy/include

CPATH > -isystem, so the higher priority headers in /opt/ecl are not found before /opt/ros/groovy. Is this a break in the logic for chained workspaces?

Aye, it's fixed, so I'll close it for now. Was just wondering if people actually have a need to use SYSTEM at all, and if they do, this tiny corner case with overlays might come up. Probably not worth worrying about it till it does though.

I've had issues where warnings were being tracked across headers to the library. The recommendation was to add SYSTEM to the include_directories to fix them.


Review the API docstrings

📰 Custom Issue
Great to have the built API docs up.
But just roughly scanning, I reckon there is quite a bit in there that needs some attention / improvement.
For instance (in my personal views)..

esmf_regrid.schemes.ESMFAreaWeighted

I don't, personally, much fancy the use of the word "separated" for X and Y coords.
You could say that the coordinate system is "separable", but I'm not sure this gives the right impression directly.
I think the best approach in the Iris docs is to focus on the dimensions : to say that X and Y coordinates have separate dimensions

esmf_regrid.schemes.ESMFAreaWeightedRegridder

It says "Regridder class for unstructured to rectilinear Cubes.", but this seems at odds with "src_cube – A rectilinear instance of Cube"

So,
I'd suggest this could do with thorough general review, when we can find time.
I know from bitter experience (1) how very hard is to precisely + clearly describe these different types of coordinate mappings, given that nearly all the recognised technical terms are used ambiguously in different contexts, and (2) how confused users are about these distinctions in the first place
So, it's always an uphill struggle to define terms clearly.
But we can at least aim to be complete + consistent in our usage
-- which would at least be definite progress, since the existing Iris docs have made rather a mess of it !!

We did make a lot of progress in #155, but not focused on the things mentioned here. Should this be kept open @pp-mo?


Add safety checks for events in ConnectedField

When you pass a value to a Field's Component's onChange, ConnectedField passes that raw value as the event.
Using the Field's onChange or other handler overrides lets us event.preventDefault(), but if the event is a value, we get an error.
This does a safety check before calling event.preventDefault().

@hook, if you had actually run the tests, you'd have spotted this simple bug I just fixed. https://github.com/erikras/redux-form/pull/2964/commits/495444c40bc4ce6dd5d1d5e0ee28bf9af6c7ae47

Codecov Report

Merging #2964 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #2964   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          67      67
  Lines        1395    1410   +15
======================================
+ Hits         1395    1410   +15

Impacted Files
Coverage Δ

src/ConnectedField.js
100% <100%> (ø)
:arrow_up:

src/structure/immutable/keys.js
100% <0%> (ø)
:arrow_up:

src/immutable.js
100% <0%> (ø)
:arrow_up:

src/ConnectedFieldArray.js
100% <0%> (ø)
:arrow_up:

src/createReduxForm.js
100% <0%> (ø)
:arrow_up:

src/index.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

It's always nice when a unit test actually finds a bug. :-)

My bad on missing the bug, I sent the PR from work and then forgot to revisit it later (I saw the test failed but the firewall at work was blocking Travis).
Excellent library by the way!

Published in v6.8.0.


update dolfinx tests to dolfinx

The dolfinx tests in vtkplotter import dolfin, which is the alpha-release API for dolfinx.  The beta release has updated the namespace to dolfinx so that old dolfin and dolfinx can be installed at the same time.
So the dolfinx tests need to be updated to import dolfinx instead of dolfin.

Thanks Drew for letting me know, i made the changes though at the minute dolfinx support is not  ready and the tests in dolfinx folder are not yet run.


SyncReadMem strange read behavior after rdEn gets deasserted

I am seeing that the read data output port gets an X (random) value in FIRRTL interpreter when I deassert rdEn in the previous cycle whereas I would expect the port to keep the previous read data instead. In fact, the generated verilog behaves as I expected. Do you think it is a bug or this is intentional? As far as I know all sequential memories behave as I would like here.

ASIC SRAMs, which SyncReadMem needs to model, generally have undefined outputs after the read-enable is not asserted.

Perhaps make consistent with behavior in #550

Behavior is defined to undefined, which is the correct behavior when modeling ASIC SRAMs
Workaround: explicitly register the data.


Bug when building Polymer() in stk==2<IP_ADDRESS>

Bug, feature request, or proposal:
Bug
Expected Behaviour:
Building of Polymer() works in version 2<IP_ADDRESS> from the 3 building blocks attached and the code below.
Current behavior:
MacroMoleculeBuildError() exception occurs using up-to-date version of stk from pip:
An error message comes up on Traceback:

RuntimeError: Pre-condition Violation
bond already exists
Violation occurred on line 284 in file Code/GraphMol/RWMol.cpp
Failed Expression: !(boost::edge(atomIdx1, atomIdx2, d_graph).second)
RDKIT: 2018.09.1
BOOST: 1_65_1

To reproduce:
import stk

# load in molecules
core = stk.StructUnit('core.mol', ['bromine'])
liga = stk.StructUnit('liga.mol', ['bromine'])
link = stk.StructUnit('link.mol', ['bromine'])

# build molecule
    polymer = stk.Polymer([liga, link, core],
                          stk.Linear(repeating_unit='ABCBA',
                                     orientation=[0, 0, 0, 1, 1],
                                     n=1, ends='fg'))
# output as built
json_file = 'Test.json'
polymer.dump(json_file)
mol_file = 'Test.mol'
polymer.write(mol_file)

I had to convert .mol files to .txt to upload, although I am sure there is a way around this.
core.txt
liga.txt
link.txt

Should be fixed in the latest commit.


Adding a testset source-set to the compile path of another testset

I have a scenario where I want to re-use code from a testset in another testset. The setup is as follows
plugins {
    id 'groovy'
    id 'idea'
    id 'org.unbroken-dome.test-sets' version '1.5.1'
}

group 'testset'
version '1.0-SNAPSHOT'

sourceCompatibility = 1.8

repositories {
    mavenCentral()
}

testSets {
    sharedTest
    integrationTest
}

dependencies {
    compile 'org.codehaus.groovy:groovy-all:2.3.11'
    testCompile group: 'junit', name: 'junit', version: '4.12'

    integrationTestCompile 'org.spockframework:spock-core:1.1-groovy-2.4'

    integrationTestCompile sourceSets.sharedTest.output
}

This compiles and runs fine when running the gradle CLI to build and test. However the IDEA integration seems to fail as the code does not compile in the IDE. Running this with JDK 8 + IDEA 2018.2.4.
See https://github.com/MartinAhrer/gradle-testset-plugin-ideabug.
It looks like this has worked with earlier versions of IDEA + the testset plugin.

Hi,
I've got your sample project to compile and run the test with two small modifications:

make sure that the groovy-all dependency version matches the one used by Spock, i.e. either upgrade groovy-all to 2.4.x or downgrade Spock to 1.1-groovy-2.3
remove the idea plugin (not sure why this fixes the problem, but I'll look into it). The idea plugin built into Gradle was used by early versions of the IDEA Gradle support, right now I think it's only used to generate IDEA project files initially, IDEA now seems to use a different mechanism under the hood (which is neither documented nor open-sourced). That's why unfortunately the possibilities for a plugin to influence IDEA's behavior are now very limited.

Agree, removing the idea plugin makes the project work. However, I think the idea plugin still has relevance. It allows to customise the workspace (e.g. by manipulating the XML based configuration of IDEA projects).
For example in my project where I originally hit the problem I'm also using the https://github.com/tbroyer/gradle-apt-plugin.  See https://github.com/SoftwareCraftsmen/continuousdelivery/blob/master/build.gradle
It has a plugin for managing apt configuration in IDEA. As soon as I add the plugin, the same symptom appears (as the apt plugin pulls in the idea plugin again).

Hi @MartinAhrer @tkrullmann
At a guess, could you use something similar to the below? (untested)
sourceSets {
    integrationTest {
        compileClasspath += sourceSets.sharedTest.runtimeClasspath
    }
}

Using 2.1.1 with Gradle 5.5
trying to add a dependency from a module to integration tests:
dependencies {
    implementation project(":core")
    implementation project(":xxx")

    e2eTestImplementation project(":xx").sourceSets.test.output
}

testSets {
    e2eTest
}

This also fails with
Could not find method e2eTestImplementation() for arguments [test classes] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

Both IDEA & CLI compile fails with the same error

After upgrading to version 2.2.1 of the plugin and Gradle 6.0.1 this issues still exists (with current IDEA 2019.1.3).
But a workaround is to use the new testFixtures feature introduced with Gradle 5.6.x. The IDE will then properly recognise the classes from the fixture.
testSets {
    integrationTest {
    }
}

sourceSets {
    testFixtures {
        java {
            srcDirs = ['src/sharedTest/java']
        }
        groovy {
            srcDirs = ['src/sharedTest/groovy']
        }
    }
}


Nested folder support

Allows users to organize their assets. Should also reflect in the outputted files.

fixed in bbaf2260e3d1f68a0fb8cb7927f00f0d249221a3


Windows 11:  Dual Interface Confguration

Describe scenario
I am using an Intel Ghost Canyon NUC with both WiFi and wired ethernet available running Windows 11.
I was using the NUC previously with Hyper-V for some Mariner and Ubuntu VMs using an external vswitch bridged to the WiFi interface while using the wired ethernet for the OS. It was working fine, the VMs could get out to the internet and connect to other systems on the local <IP_ADDRESS> network.
The first time I installed AKS-EE I used the existing vSwitch bridged to WiFi - as per the instructions. Everything appeared to be  working, I was even able to follow the GitOps demo and get that working. The problems started after a reboot of the NUC. After a reboot I had to reconnect the WiFi adapter to the network which seemed to work - I could run kubectl commands.  But the cluster/VM/network became very unstable after that and eventually stopped communicating.
I then started getting certificate errors when trying to run "Invoke-AKS-EdgeNodeCommand".
During this time the existing Mariner VMs had no issues communicating via the same switch.
Thinking there was some existing configuration interfering I removed everything, including HyperV and started over.

I tried bridging the wired ethernet but that didn't work so I went back to a dual network setup.
I went back to the bridged WiFi setup and everything installed fine and looked like it was working, until I shutdown/restarted the NUC and now I'm back to the original situation.
Note that another NUC on the same network with just a WiFi connection, no w3ired Ethernet, is working fine, very stable, even aftre reboots etc.

Question
What is the best way to setup AKS-EE on a Windows 11 node?
Can you use a dual connection like I have or can you only use WiFi?  Bridging and sharing the wired connection didn't appear to work (maybe if the WiFi interface is completely removed?)
Can you use HyperV for other VMs while AKLS-EE is using it?
Thanks!

Hi @kvietmeier,
Thanks for reaching out.  We are working on fixing an open issue with WiFi virtual switches for our next update.  Answering below your questions:

If you need just one node, use a singe machine cluster, and we will create the internal switch for you. If you're using Scalable Cluster, the best option is to use an Ethernet connection to create your External Virtual Switch.
For Dual Nics, please check Configure multiple Nics.  Bridging is something that we do not recommend.
Yes our VM lifecycle is managed completely by us and shouldn't impact your other VMs running on the host OS. However, we recommend not changing the AKS EE VM configurations using Hyper-V Manager.

Thanks,
Francisco

@Francisco,
This helps clarify things a bit and I may have used the term bridge incorrectly.
HyperV is creating a bridge when I allow HyperV and the host OS to share the same interface.
On one system I only have a WiFi connection and I followed the instructions to create an external vSwitch.  This system works perfectly as expected.
On another system (the one not working) my primary interface is a wired connection but it also has a WiFi interface.  Previous to AKS-EE I had created an external vSwitch bridged to the WiFi connection for the VMs and it was working fine - sort of - I would still need to manually  reconnect to the WiFi after a reboot. AKS-EE will install fine on this system and even work properly, until a restart, then you lose connection to the VM.
Interestingly - when I tried disabling the WiFi interface and just share the wired connection I couldn't get AKS-EE to install/work at all.
I'm inclined to think that using both interfaces is more effort than it is worth and may just go to WiFi only on both.  But I will give the dual interface setup a try before reverting to one interface.
A note on single vs. multiple nodes and networking:
If you want to be able to access the apps running in the cluster from the local network you need the external vSwitch, it just makes everything much, much easier.  That isn't clear in the docs but it comes out in some blog posts and issues. So - if you want to be able to give your apps IP addresses on your local network you should create a multi-node cluster with a single node.
VM lifecycle - The VMs do not show up in HyperV Manager, only the vSwitch.

Closing:   Collapsing onto the the WiFi interface seems to have worked (until updating the BIOS and rebooting but that is another issue)


Add notification area

Adds a NotificationArea with clickable icons that then open a window with a more detailed message.
NOTE: Mac build via circle-ci appears to be broken not due to code. All other checks pass so I would merge this if it looks good regardless and find a fix for the mac build after the fact.

MacOS builds should now be fixed by #885. You can merge master, or rebase on top of master, and the builds should pass.

Quite a lot of commits there. Time to experiment with git rebase? :wink:

MacOS builds should now be fixed by #885. You can merge master, or rebase on top of master, and the builds should pass.
Quite a lot of commits there. Time to experiment with git rebase? 😉

Already did two rebases with this one, no issues with rebasing again :D


Fire class should support generic parameters

The Fire class should support generic pass-through parameters and return types and should avoid creating closures wherever possible.

Completed, waiting release in .5.0.8


Add a new flag in RemoteRepository to identify if remote host is a indy instance

This will be used in static-proxy content listing enhancement to get the correct content listing result.

Will it be possible to calculate from the remote url? like url.getHost().matches('^indy.*'). anything written to the repo definition is not easy to change.

This flag is mostly to use as a fail-fast flag, which means if false then we will not do further checking. For true side, it is not the only flag to do the checking, but will be a flag for further checking on different functions, like content api checking.

Ok. LGTM.

LGTM!


Control bundle config through pkgr?

I'm trying to package my Rails app that depends on nokogiri. Apparently Bundler needs special configuration to build on my Ubuntu 14.04 VM:
bundle config build.nokogiri "--use-system-libraries --with-xml2-include=/usr/include/libxml2"
Can I control that through pkgr? Otherwise it fails:
$ pkgr package simple-merchant/
-----> Ruby app
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.0.0
-----> Installing dependencies using 1.7.12
Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j2 --deployment
Fetching gem metadata from https://rubygems.org/.........
Installing rake 10.4.2
Installing i18n 0.7.0
Installing json 1.8.2
Installing minitest 5.5.1
Installing thread_safe 0.3.5
Installing tzinfo 1.2.2
Installing activesupport 4.2.1
Installing builder 3.2.2
Installing erubis 2.7.0
Installing mini_portile 0.6.2
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
/tmp/d20150427-20456-8lhcav/opt/simple-merchant/vendor/ruby-2.0.0/bin/ruby extconf.rb
checking if the C compiler accepts ... yes
Building nokogiri using system libraries.
libxml2 version 2.6.21 or later is required!
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Hello,
I was able to do this using bundler's --local option. This option writes the config in the app directory so pkgr will have access to it.
Try this:
bundle config --local build.nokogiri "--use-system-libraries --with-xml2-include=/usr/include/libxml2"

Thanks, that works a treat!

Thanks for the tip @luizsignorelli !

Was there any way of controlling this through .pkgr.yml?  The problem is that running that on my Debian build server doesn't make any difference - I get the same error.  And if I set it in the repository, it'll affect my OS X development machine.

Even leaving out the --local when running the bundle config command on the build machine doesn't work (I don't know if anyone would expect it to).

@andyjeffries I suppose you could run that command as a before step in the .pkgr.yml file, so that it gets run on the build machine?
before:
  - bundle config --local build.nokogiri "--use-system-libraries --with-xml2-include=/usr/include/libxml2"


Some way to stop the template from running (for when there aren't two players)

This might not be necessary if we work on player renumbering


fix: Handling of non-json content types

I need to fix #852 first and then rework serialization.
Fixes #850

Closing in favor of #862


pkg-config?

Hi @zecruel .
Maybe replace
https://github.com/zecruel/CadZinho/blob/bbcf4ff2efd3c71693e2ee782f7c218b65793be6/Makefile#L3-L6
to
CFLAGS = -g -c
CFLAGS += -I. -I./src/ `pkg-config --cflags lua sdl2`
LDFLAGS = `pkg-config --libs lua sdl2` -lm -lGL -lGLU -lGLEW -L/usr/lib -L.

?
See also https://github.com/zYg-sys/CadZinho/pull/1

Hi!
Thanks, it worked fine in Linux (look in the 'linux' folder in the repository).
But I couldn't get it to work on mingw (msys2)...

@zecruel say:

But I couldn't get it to work on mingw (msys2)...

Maybe  replace:
https://github.com/zecruel/CadZinho/blob/f617168c093bcef39832df51f1e91c0a704fb9d1/Makefile#L4-L5
to
ifeq ($(OS),Windows_NT)
LINKER_FLAGS = `sdl2-config --cflags --libs` -llua -lm -lGL -lGLU -lGLEW
INCLUDE_PATHS = -I. -I./src/ -I/usr/include/SDL2
else
LINKER_FLAGS = `pkg-config --libs lua sdl2` -lm -lGL -lGLU -lGLEW
INCLUDE_PATHS = -I. -I./src/ `pkg-config --cflags lua sdl2`
endif
?


gps and gsm not working

when i first pluged in the device the power led (blue) was on and there was 2 other led (red) i belive for gsm and gps
once i uploaded the firmware from github and started working on it using platform , io the problem started
the gps and the gsm dont even blink anymore and can be seen
i tried to change the wire reset etc nothing worked
also there is a problem with the baudrate i keep getting random raw data whenever i upload anycode
it compiles well but then the terminal shows !!!!#($#J$ somthing like this
i would love any help i can get on these issues

Show this? Can you give me a full screenshot? I've never seen this error before, and I don't know which software this is from

i tried to change the baudrate but samething
also the 2 led are not blinking

Monitor baud rate is 9600, change sketch baud rate to 9600 or set monitor to 115200

alright one problem out of the way
but still the gps and gsm led are not on and i get this

You need SIM-HAT hardware support to run. The examples above all need SIM-HAT hardware support. Please run the minimum ATDebug to test and read the README first.

this is kind of my first time here
could you explain more ?

All examples with SIMhat in their names require the support of this hardware to run https://www.lilygo.cc/products/lilygo®-t-simhat-can-rs485-relay-5v
README explains which examples can be used and which cannot

i saw many videos on youtube that connected a wifi and gps to the same excat model i use which is a7670e esp32 wroover e
if i cant use these libaraies how should i proced?

What do you mean? I don't understand what you mean?

before i decided to buy this model which is A7670E
i checked some youtube videos to make sure it can work without any extra hardware
but if the examples above require some extra hardware
can you help me find examples for the board itself alone ?

hmmmmmm wait so in order to be able to use gsm and gps i need to buy the extra hardware ??

Well, to use GSM and GPS you only need to buy A7670. SIM-HAT is a separate additional hardware, you can exclude it completely, I just want to tell you that SIMHAT*** example requires additional hardware support, understand? I think I made it clear.

yeah i get it now
what tuturial do i follow to start the gps and gsm
right now there leds are off

ATDebug

done that already
every time i check the serial moniter when uploading any code i always get Failed to find INA219 1 chip in

https://github.com/Xinyuan-LilyGO/LilyGO-T-A76XX/blob/a4aef6e8a0c768eef6ada97d62b5747b5a840c08/platformio.ini#L44


Fixed tutorial to point to the correct template

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[x] The title, template, and date` are all set
[x] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[x] Has passed bart check
[x] Has run npm run build-index
[x] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[x] Headings are using Title Case
[x] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[x] Have tested with npm run test and resolved all errors

tagging @kate-goldenring for viz :)

Hi @macolso
i think this tutorial is suppose to  use redis-rust template.

I walked through this yesterday using the redis rust template, and ran into issues. After chatting with Kate, I learned redis-* templates aren't supported on cloud yet.

Hi @macolso
i think this tutorial is suppose to use redis-rust template.
we should probably change references of http-rust to redis-rust :)

@rajatjindal the distinction here is that this example is for outbound redis. We don't support the redis trigger on Fermyon Cloud (https://github.com/fermyon/developer/issues/90#issuecomment-1281858366) -- right now, apps cannot be triggered by redis events; however, they can publish messages to redis. This was an error in the docs to install the redis-rust template instead of http-rust. This is probably something we could make clearer in the docs writeup -- why we are using http component for something redis related. Maybe a note.

I really liked Ivan's suggestion in #90 to create a conceptual article that elaborates on templates and trigger as well as their relationship. Maybe this is something I can work on with @melissaklein24.


synths-diy, eurorack-diy, selfhosted added

Me enseñan por favor porq yo soy el que lo cargo ok

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

1 addition per PR.


backup functionality

Hi @giovannipizzi @sphuber, as discussed (also in #20), I moved the disk-objectstore backup functionality from https://github.com/aiidateam/aiida-core/pull/6069 to this project.
It works currently, but I added everything currently in a separate file backup_utils.py, to keep it a bit decoupled for now. Also requires some polishing (e.g. the logging part).
However, there are some issues:

Code duplication w.r.t. https://github.com/aiidateam/aiida-core/pull/6069: i basically added the same utility functions to run commands on local and remote machines & to call rsync. Is this duplication fine or do you have some ideas how to change this design?
We say windows is supported for this repo (in the README.md), but I think relying on the unix commands breaks this. e.g. i'm using [ -e <path> ] to check if a folder exists. I used this so that I could use the same method for both local and remote paths. However, another option is to use python-specific checks for local paths (e.g. pathlib.Path.exists() for this case) and unix-specific ones for remote ones. This might be a way to keep the windows support, at least if doing backups to a local folder.

Any ideas welcome.
If this approach works, i can polish it further and add some tests.

@eimrek let me know if you want me to have a look at this and or have particular questions. Since you marked it as WIP I haven't gone through it yet

@sphuber sure. i think the main features are there, i just need to add tests.

Note after discussion with @edan-bainglass : his usecase (mounting a windows folder to a linux container and backing up there) might not support symlinks. At least in my case, where to mount a windows folder to my linux virtual machine doesn't, by default. Therefore, it might make sense to avoid using symlinks altogether.

Hi @sphuber @giovannipizzi, this PR is in a state where your feedback would be great. the functionality is there and i added main CLI tests. But some notes/comments regarding things i'm not sure about:

in many places, I check for success of a subprocess command based on the exit code & if it fails, print something and "return False" from the backup function. I'm not fully sure if this is the best way to handle these errors, suggestions welcome (e.g. maybe assert is better or using exceptions more directly, ...). Additionally, testing all of these failures does not seem straightforward.
currently we're running tests on "windows-latest", which are failing. how to deal with this?
additionally, the "ssh localhost" currently is failing on mac-os, i'll soon investigate this further

@sphuber @giovannipizzi feel free to submit your review if you have a moment to check.


NFT not showing up in chart view

Ryan called the hotline this afternoon after noticing that the surface, middle, and deep sensors were not showing up on the tech dashboard chart view.
I went and looked at the device status and saw that the gateway was connected to all of the nodes and was sending data to the tech dashboard. I asked for the serial number of the node (18000472) and noticed that there's a -999 error message immediately following the sensor serial number. According to the PSA Water Sensor Instructional Guide this indicates that there is an error in the sensor depth, and that it was not correctly entered during the configuration.
This needs to be corrected in the database.

This error is recurring due to the mis-configuration, as you've noted. The only in-season fix is an periodic batch update of those rows in the database. I'll run the script and verify that NFT is working again.

Updated ~14k rows, NFT appears to be working + others


Adopt Google yamlfmt pre-commit hook

This copy of yamlfmt respects licenses at the beginning of YAML files that Google contributions are required to have. The old copy of yamlfmt does not. Running this hook (and yamlfmt) configuration against all files creates changes in 14 files which appear to be:

fixing indentation of comments (harmless)
taking strings that were split across lines and making them appear on one line

We have encountered cases where the old yamlfmt hook wrongly and harmfully split YAML/jinja strings across lines (1cd5a03a) so these changes are probably good but need to be tested.
I am manually testing the image building process and will report in a follow-up comment.

I have used Packer to build images from the following VM families

debian-10
debian-11
hpc-centos-7
hpc-rocky-linux-8
ubuntu-2004-lts

The builds succeeded without error. Example pkrvars.hcl file:
project_id = "toolkit-demo-zero-e913"
zone       = "us-central1-a"
source_image_project_id = "ubuntu-os-cloud"
source_image_family = "ubuntu-2004-lts"
image_family_alt = "u20-pmix"
machine_type = "n2-standard-16"
tags = [
  # "tag0",
  # "tag1",
]
slurm_version = "23.02.7"
install_lustre = false
service_account_email = "default"
service_account_scopes = [
  "https://www.googleapis.com/auth/cloud-platform",
]
extra_ansible_provisioners = [
  #  {
  #    playbook_file = "/home/user/playbooks/custom.yaml"
  #    galaxy_file = null
  #    extra_arguments = ["-vv"]
  #    user = null
  #  },
]


Refs assigned to effects are always undefined

The problem
At the moment of 1.0.0-beta3 if you try to pass a ref to an effect it will become undefined.
It happens because ref prop is already occupied in EffectComposer:
https://github.com/react-spring/react-postprocessing/blob/3a89610a586326e5b78d7fb325053efd49326788/src/EffectComposer.tsx#L70
Solution
One of the solutions is trying to merge refs. However, React drops an error about inproper usage of refs.
Warning: [object Object]: `ref` is not a prop. Trying to access it will result in `undefined` being returned. If you need to access the same value within the child component, you should pass it as a different prop.

I think the right one is making a custom prop innerRef. Last time I tried it, everything that used refs got broken  because of composer becoming null so I don't know yet what's the proper way of doing things here.

What's reacts error when you merge? I use mergerefs all the time and never saw a warning, must be something else imo

@drcmda here is the error I get:
Warning: [object Object]: `ref` is not a prop. Trying to access it will result in `undefined` being returned. If you need to access the same value within the child component, you should pass it as a different prop.

it happens when I try to merge refs[i] and el.props.ref
here's a demo of this case: https://codesandbox.io/s/trying-to-get-effect-ref-9zzl1?file=/src/App.js

try clone in that case https://reactjs.org/docs/react-api.html#cloneelement

Clone and return a new React element using element as the starting point. The resulting element will have the original element’s props with the new props merged in shallowly. New children will replace existing children. key and ref from the original element will be preserved.

@drcmda maybe I'm using this wrong but it's still { current: undefined } :/
I used this SO answer so the code looks like this:
React.Children.map(children, (el: JSX.Element, i) => {
   return cloneElement(el, { ref: refs[i] })
})

and in demo it looks like this:
https://github.com/react-spring/react-postprocessing/blob/3a89610a586326e5b78d7fb325053efd49326788/examples/pages/outline.jsx#L10-L40
Even if it is said that cloneElement preserves refs, looks like here it gets overidden anyway.

I've set up a codesandbox to debug the composer easier, but still no result yet :/
https://codesandbox.io/s/boring-noether-7uli0?file=/src/components/EffectComposer.tsx
it's being undefined

@drcmda so I talked to some guys in a React chat and came to a conclusion that the whole EffectComposer implementation is wrong. We cannot merge refs, neither we can't assign them because they are occupied already.
I think that it's worth trying to implement it with children again, but there is a problem with state....
any ideas?
should I keep the existing implementation and keep trying to make it work (but I honestly don't know what else to try)
or it's better to completely rewrite the composer and effects?

I think I got something: https://codesandbox.io/s/intelligent-dhawan-yo4lj?file=/src/App.tsx
might be some unexpected problems though

Fixed in last version, works nicely!


Port changes from v0.10.2, apply patches from DuckDB core

I think the solution to the _rtools failure and possibly also the one for wasm are here: https://github.com/carlopi/duckdb_spatial/pull/2, trying to see how that will end up failing.


Bug in concatenating dataframes

Hello,
I believe there is a bug in line 207 of atm/model.py   The call to concat should be as follows:
all_data = pd.concat([train_data, test_data])
See here: https://pandas.pydata.org/pandas-docs/version/0.20/generated/pandas.concat.html?highlight=concat#pandas.concat
I would submit a pull request but I have other changes and don't want to complicate things.

Good catch. I'll submit a pull request tonight.
Just FYI, I recently joined EFF, and I'm no longer maintaining this project as my day job. I'll try to keep up with issues here, but I'll be a lot less responsive than I was.


Morte fails on Windows (due to unicode output?)

Morte 1.6.2 is DOA on Windows 7 both on Cygwin and the Windows cmd shell:
On Cygwin:
$ cat hello.mt
\(a : *) -> \(x : a) -> x

$ morte < hello.mt
morte.exe: <stderr>: hPutChar: invalid argument (invalid character)

In cmd.exe:
C:\Users\cactus\Documents\playground\morte>type hello.mt
\(a : *) -> \(x : a) -> x

C:\Users\cactus\Documents\playground\morte>d:\local\stack\Local\bin\morte < hello.mt
morte: <stderr>: hPutChar: invalid argument (invalid character)

Is there a way to turn off Unicode output? I'd like to try that and see if that works (i.e. using \/ instead of ∀ etc.)?

I've found a relevant Stackoverflow quesiton.

So if I could apply the fix described in the Stack Overflow question, would that be an acceptable solution for you or would you still prefer an option to disable Unicode output?

I'd prefer to have both options. Also, I think I take back my original suggestion of using \/ in particular for ∀; I'd prefer forall instead.

Alright, this is fixed by these two commits:

Use the correct code page on Windows so that Unicode works and doesn't crash: ffae9df8c4b6f03060d8839b487ac030b21393a4
Provide an --ascii option: aa94462de7c6a442752ddc76cd5650060b288a82

The latter uses forall when rendering ASCII like you requested (and that's also my preference, too)


We should enforce that swiftlint and swiftformat are installed and using specific versions

We use these tools in the build steps for libraries to ensure code style consistency. Issues arise when different versions are used, and if these tools aren't present, the build stage ignores this.
Currently we are using swiftlint 0.46.3 and swiftformat 0.49.4.

Additionally, we need to:

[ ] Force the build agent to install these specific versions as this has led to regressed packages breaking our build
[ ] Rearrange the sequence of the build steps because currently "Lint and Format Sources" happens before the sources are compiled. It should happen first.


[Suggestion] Solar And Or Lunar Eclipses

it would be cool if we had eclipses (it would give some more life to the sky in my eyes.
Only downside is it wont be able to darken the surface unless you make it a datapack that darkens the surface to act like its sunrise. (unless someone makes a shaderpack that directly is compatible with the resource pack that automatically make it darker client sided.)
Overall Id love to see this get added.

Actually I can make it darken the surface, that's not a problem (unless you mean darken in such a way that mobs spawn, that I cannot do).
The larger problem is that there is no simple way to do it. I can't just put it on some timer, because in the very next version, anyone will be able to change every single part of the sky using resourcepacks, so if someone were to just decide the moon should move a bit faster, or orbit in a different direction, that timer would cause things to look weird.
I have some ideas in mind, which involve checking if the projections of objects are overlapping by taking the size and projection position of any object, but it will first require me to prepare the grounds for such a system first.

I actually diddnt know you can darken the surface. and yes i meant in a way for mobs to spawn, Thats why i mentioned a Datapack that could do that.
I agree with making eclipses by overlapping by taking the size and projection position of any object.  the 2 downsides is, The Moon is Smaller than the sun by a couple skybox pixels, So its going to be Annular anytime it reaches totality, AND The moon and sun need to be at angles in order to make Solar Eclipses Rare instead of of being common everytime when the moon reaches new moon state.

The sun can be made smaller. Eclipses wouldn't be 'timed' exactly, it's just whenever the moon passes in front of the sun or through an earth-sized area of space behind the sun, eclipses happen
just check for the moon entering either zone, and make stuff happen accordingly

The sun can be made smaller. Eclipses wouldn't be 'timed' exactly, it's just whenever the moon passes in front of the sun or through an earth-sized area of space behind the sun, eclipses happen
just check for the moon entering either zone, and make stuff happen accordingly
gonna have to wait until 0.3 gets further along tho

The "just check for the moon entering either zone" is THE most complicated part of the whole thing.

To simulate eclipses in a general manner, we need to know where the sun is in the sky, as well as any object that might cast a shadow over the observer, or that the observer would cast a shadow over. Spherical coords. We also want the apparent sizes of these objects.
Solar eclipses are simple enough with this information alone. We know the apparent size and location of the sun, as well as the apparent size and location of anything that would pass over the sun (Ex. Luna, Mercury, Venus). We could then calculate based on how close to each other the sun and occluding objects are in the sky. Objects that are fully over the sun should be darkened significantly, to appear as a dark square over the sun. The more the sun is covered, the darker the skybox gets, with a fully covered sun leading to the sky darkening enough that it looks like night.
Lunar eclipses require an additional variable, the distance between the observer and anything it might cast a shadow on. The observer casts two shadows, that being the penumbra and umbra. The penumbra darkens any object that can pass through it, while the umbra tints the object with the observer's Rayleigh scattering (red for earth, blue for mars, whatever color the evening sky takes)


feat: add automatic tooltip repositioning for viewport overflow

Added logic that detects when tooltips would render outside the viewport and automatically flips/updates their position to maintain visibility.

Related: #7

Added test case for tooltip overflow.
I used the screeninfo package to get monitor information as it supports multiple platforms. AFAIK there's no reliable way to obtain monitor information natively with Tkinter.


EIDW loaded

How can I open a single pull request with multiple branches?

You've added airport_load, but EIDW file is not in the tree, you need to add it (git add) and commit.

You've added airport_load, but EIDW file is not in the tree, you need to add it (git add) and commit.

You can just git add the file to your patch-7 branch - when you do that, the pull request is automatically updated.

@Fechulo looks like you created one pull request per commit, no need for that, just make one branch and one PR, and push into that branch. Only if you work on separate tasks it makes sense to have several branches and requests.

Thanks for the help! Unfortunately, I'm a complete noob, so where exactly do I put the "git add" command.
Thanks!


opengrok: <IP_ADDRESS> -> 1.0

Motivation for this change
Follow up to #36639 which changed the version in derivation name but we were still fetching the source tarball of v<IP_ADDRESS>
The SHA hash was the same, just changed from base16 to base32.
This PR actually updates opengrok to v1.0
/cc @lethalman
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: opengrok
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: opengrok
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0
gzipping man pages under /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/lib  /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin
patching script interpreter paths in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin/Groups: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin/Messages: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin/.OpenGrok-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0...
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: opengrok
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: opengrok
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0
gzipping man pages under /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/share/man/
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/lib  /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin
patching script interpreter paths in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin/Groups: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin/Messages: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0/bin/.OpenGrok-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0...
/nix/store/ffg9ihx0wfrw5hp10pknv9zrsd5xa9qb-opengrok-1.0


Refactor templates to take advantage of format replacement fields.

As a suggestion, this fulfills #2

Awesome, merge & close :)

Fixes #2


chore(master): release 1.1.80

:robot: I have created a release beep boop
1.1.80 (2023-06-06)
Miscellaneous

deps: update dependency vite-node to v0.32.0 (27563c2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/keywind/releases/tag/v1.1.80 :sunflower:


[DismissableLayer] Prevent issue when mounting via pointerdown

Hi @benoitgrelard @jjenzz Can you explain what it means by "mounting via pointerdown", thanks!


Let's talk about removing synchronous provision and binding requests for v3.

Added this to the Ideas for v3 wiki page. Closing here.


[BUG REPORT] no content filter found

Hello!
I think I've come across a bug, maybe it's nothing and maybe I'm just stupid (Probably the latter 😆)
Here is the error reported by the console:
getContent @ featherlight.min.js:8
open @ featherlight.min.js:8
i @ featherlight.min.js:8
(anonymous) @ featherlight.min.js:8
dispatch @ jquery.min.js:3
q.handle @ jquery.min.js:3

Here is my code where I'm trying to use Featherlight.
<a href="https://www.youtube.com/embed/'+videoId+'" data-featherlight="iframe" data-featherlight-iframe-allowfullscreen="true" data-featherlight-iframe-width="940" data-featherlight-iframe-height="529">

Any help would be majorly appreciated, I'm trying to wrap this project up as soon as possible :)

If you’ve found a bug, you must provide a minimal example in a CodePen, starting from http://jsfiddle.net/JNsu6/15/ .

@jenil I have been using the lib in my website for over a year and just started experiencing the same error Featherlight: no content filter found  (no target specified) and I haven't changed anything 👎

@crobinson42 sorry about the troubles you are having. Please try to find a minimal reproducible example.


Bump upper bound for base to <4.9

Otherwise it won't build on ghc 7.10 ;)

Thanks!

Released 0.2.1 with this change.


WIP: add direct-sharing messaging API

Current coverage is 87.69%

Merging #486 into master will decrease coverage by -0.06% as of ff61569

@@            master    #486   diff @@
======================================
  Files          237     237
  Stmts        10625   10639    +14
  Branches         0       0
  Methods          0
======================================
+ Hit           9324    9330     +6
  Partial          0       0
- Missed        1301    1309     +8

Review entire Coverage Diff as of ff61569

Powered by Codecov. Updated on successful CI builds.


Fix missing context argument to pre_execute method

Fixes #223

Coverage increased (+0.1%) to 85.102% when pulling ea8fd2cc3965e7429a03c13eabffc57117625311 on fix/ior_prexec into dccdb37334a9d66d7641f54f0e6e3839a4c50350 on master.


Restore FPGA USM target to the VS project

Description
Restore FPGA USM target to the VS project. This was removed in https://github.com/oneapi-src/oneAPI-samples/pull/257.
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

These test failures are completely unrelated to this PR. The Windows CI tests exercise the Makefile, while this PR fixes a problem in the vcxproj.
Can we merge this PR (which has been tested by @Jenn500 in Visual Studio), and allow the sample owner to resolve the test failures in a separate change?


Grapi error when guest joins a group

In the currently provided examples/meet setup, whenever I join a public session as guest, it just hangs with an endless "loading" indicator. I see the user in the session, but no picture and audio.
In the logs I see:
kopano_grapi        | 2020-03-29 13:56:03,098 rest7     [   65] ERROR    unhandled exception while processing request
kopano_grapi        | Traceback (most recent call last):
kopano_grapi        |   File "/usr/lib/kopano/python3-extras/lib/python3.7/site-packages/falcon/api.py", line 244, in __call__
kopano_grapi        |     responder(req, resp, **params)
kopano_grapi        |   File "/usr/lib/python3/dist-packages/grapi/api/v1/decorators.py", line 21, in wrapperResourceException
kopano_grapi        |     return f(resource, req, resp, **params)
kopano_grapi        |   File "/usr/lib/python3/dist-packages/grapi/api/v1/decorators.py", line 40, in wrapperRequireResourceHandler
kopano_grapi        |     return f(resource, req, resp, **params)
kopano_grapi        |   File "/usr/lib/python3/dist-packages/grapi/api/v1/api.py", line 31, in on_get
kopano_grapi        |     return self.getResource(req).on_get(req, resp, *args, **kwargs)
kopano_grapi        |   File "/usr/lib/python3/dist-packages/grapi/backend/ldap/user.py", line 196, in on_get
kopano_grapi        |     data = value[0]
kopano_grapi        | IndexError: list index out of range

Hmm nope, the error wasn't the blocking issue. A connection limit on the TURN server was.
But still: this error only shows up when joining guest sessions, so I guess there is still some bug - just not as critical as it seemed :)

Hi @aksdb,
can you share a bit more about your environment? I am unable to reproduce the above error in grapi when logging in with a guest account.

Sure thing:
$ git describe --always
0e06017

$ docker-compose images
       Container                 Repository           Tag       Image Id       Size
-------------------------------------------------------------------------------------
kopano_grapi               kopano/kopano_core        latest   698d3b8633da   594.7 MB
kopano_kapi                kopano/kopano_core        latest   698d3b8633da   594.7 MB
kopano_kopano_konnect_1    kopano/kopano_konnect     latest   bf1332d56dec   85.45 MB
kopano_kopano_kustomer_1   kopano/kustomerd          latest   5c23d1ca0656   10.4 MB
kopano_kopano_kwmserver_   kopano/kopano_kwmserver   latest   9a0671a91c58   27.98 MB
1
kopano_kopano_meet_1       kopano/kopano_meet        latest   e50a5718397e   430.6 MB
kopano_kopano_ssl_1        kopano/kopano_ssl         latest   6b1414d40ab8   12.06 MB
kopano_ldap                kopano/kopano_ldap_demo   latest   a16d084d45ee   275.7 MB
kopano_web_1               kopano/kopano_web         latest   609a2c211586   33.2 MB

$ cat .env
# please consult https://github.com/kopano-dev/kopano-docker
# for possible configuration values and their impact

# Access to the Kopano Turn service can be requested at https://portal.kopano.com/content/turn-server-access-request
TURN_USER=
TURN_PASSWORD=

# Defines how Kopano can be accessed from the outside world
FQDN=my.domain
FQDNCLEANED=my.domain
DEFAULTREDIRECT=/meet
EMAIL=self_signed
CADDY=2015
HTTP=80
HTTPS=443

TZ=Europe/Berlin

LDAP_CONTAINER=kopano_ldap_demo
LDAP_ORGANISATION="Kopano Demo"
LDAP_DOMAIN=my.domain
LDAP_BASE_DN=dc=my,dc=domain
LDAP_SERVER=ldap://ldap:389
LDAP_ADMIN_PASSWORD=F9614754F9A0BF397F1AB784401BF2F5
LDAP_READONLY_USER_PASSWORD=77865102B7105B661C0322D54381380A
LDAP_BIND_DN=cn=readonly,dc=my,dc=domain
LDAP_BIND_PW=77865102B7105B661C0322D54381380A
LDAP_SEARCH_BASE=dc=my,dc=domain

# Settings for test environments
INSECURE=yes

# Docker and docker-compose settings
# Docker Repository to push to/pull from
docker_repo=kopano
COMPOSE_PROJECT_NAME=kopano

So it should be as close to a default setup as possible.

Ok, I was not able to reproduce the message. I have created https://jira.kopano.io/browse/KC-1734 for followup.
Thanks for reporting!
As this does not block usage or is an error with the containers in general I will now close this issue.


Add timecheck to bsi timestamp

It seems that the bsi timestamp has not been time checked, so add it.

Thanks @warpkwd for your first contributions. Great start :+1:  !!

@warpkwd could you please sign your commits ? Just add  -s while commit.


Add sidecard docs

Description
This PR includes the following proposed change(s):

add sidecard documentation

Type of change

[x] Refactoring / Documentation

How Has This Been Tested?

local storybook and tests

In the image above: the code displayed for information sidecard and sidecard with image looks the same, is not clear what changed in the call to create them

the slight drop in coverage is expected since we are removing duplicate mobile viewport stories/snapshots for those :)


TryFunction Error in Base Application Event Subsriber to OnAfterSendEmail

Please include the following with each issue:
1. Describe the bug
The BaseApp subscribes to events that are called inside a tryFunction
2. To Reproduce
Steps to reproduce the behavior:
The publisher Event inside the codeunit 8888 "Email Dispatcher"
    [TryFunction]
    local procedure FireOnAfterSendEmail(MessageID: Guid; Success: Boolean)
    var
        Email: Codeunit Email;
    begin
        Email.OnAfterSendEmail(MessageID, Success);
    end;

The following event subscriber is implemented in the codeunit 1368 "Monitored Field Notification"
    [EventSubscriber(ObjectType::Codeunit, Codeunit::Email, 'OnAfterSendEmail', '', false, false)]
    local procedure OnAfterSendEmail(MessageId: Guid; Status: Boolean)
    begin
        UpdateEmailStatus(MessageId, Status);
    end;

    procedure UpdateEmailStatus(MessageId: Guid; Status: Boolean)
    var
        ChangeLogEntry: Record "Change Log Entry";
    begin
        ChangeLogEntry.SetRange("Notification Message Id", MessageId);
        ChangeLogEntry.SetRange("Field Log Entry Feature", ChangeLogEntry."Field Log Entry Feature"::"Monitor Sensitive Fields");
        ChangeLogEntry.SetRange("Notification Status", ChangeLogEntry."Notification Status"::"Email Enqueued");
        if ChangeLogEntry.FindFirst() then begin
            if Status then
                ChangeLogEntry."Notification Status" := ChangeLogEntry."Notification Status"::"Email Sent"
            else
                ChangeLogEntry."Notification Status" := ChangeLogEntry."Notification Status"::"Sending Email Failed";

            ChangeLogEntry.Modify(); ///PROBLEM in Try Functions
        end;
    end;

3. Expected behavior
Could you please add a Background Task or something else asynchronusly, that will call this publisher event out of this try function. We need this in our applications that we can track the status of the email outbox messages.
And the BaseApp needs this, too.
4. Actual behavior
A clear and concise description of what happened accompanied by images, animations, or a link to a video showing the issue occurring
5. Versions:

AL Language:
Visual Studio Code:
Business Central:
List of Visual Studio Code extensions that you have installed:

Final Checklist
Please remember to do the following:

[x] Search the issue repository to ensure you are reporting a new issue

[ ] Reproduce the issue after disabling all extensions except the AL Language extension

[ ] Simplify your code around the issue to better isolate the problem

@AlexanderYakunin do I need to open a Support Request too, that this will be fixed for BC17 or will you provide a fix for this Error in "Monitored Field Notification" Subscriber?
This issue is related to the following issue #9553

@JesperSchulz - forwarding to your team

@pri-kise I am not sure yet whether we should change the event or the subscriber.
You can get unblocked by changing your subscriber to start a task for making the database changes.

@GiorgosPa okay this could maybe work for our sue case.
Do we need to open a support case that this will be in the Base Application?

You ask is not a hotfix, but design change. CSS and SE team are not doing design changes. This is a task for feature team working on Email module. And it should be done for Master branch first.

@pri-kise I think you will need a support case to get this hotfixed on 17.5.

Just noticed @AlexanderYakunin comment. Not sure what the process is let me find out and I will get back to you.

@pri-kise You need a support ticket to get any fix for BC17

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

@JesperSchulz
As far as I can see.
This isn't fixed in the next major or minor in the BaseApp
[EventSubscriber(ObjectType::Codeunit, Codeunit::Email, 'OnAfterSendEmail', '', false, false)]
local procedure OnAfterSendEmail(MessageId: Guid; Status: Boolean)
begin
    UpdateEmailStatus(MessageId, Status);
end;

procedure UpdateEmailStatus(MessageId: Guid; Status: Boolean)
var
    ChangeLogEntry: Record "Change Log Entry";
begin
    if IsNullGuid(MessageId) then
        exit;

    ChangeLogEntry.SetRange("Notification Message Id", MessageId);
    ChangeLogEntry.SetRange("Field Log Entry Feature", ChangeLogEntry."Field Log Entry Feature"::"Monitor Sensitive Fields");
    ChangeLogEntry.SetRange("Notification Status", ChangeLogEntry."Notification Status"::"Email Enqueued");
    if ChangeLogEntry.FindFirst() then begin
        if Status then
            ChangeLogEntry."Notification Status" := ChangeLogEntry."Notification Status"::"Email Sent"
        else
            ChangeLogEntry."Notification Status" := ChangeLogEntry."Notification Status"::"Sending Email Failed";

        ChangeLogEntry.Modify(); ///This is the problem
    end;
end;

Let me double-check! We'll get back to you.

Hi @pri-kise, there isn't a change to the subscriber in BaseApp because the fix addressed the root cause: the OnAfterSendEmail is no longer raised from inside a TryFunction (please, see "Email Dispatcher" codeunit), so database write transactions will be allowed inside subscribers.

Hi @IhorHandziuk,
Thanks for the clarification. Seems, that I missed that change.


Allow non-interactive bk configure command

Currently bk configure is interactive and this prevents from using it in poduction, eg github actions. This PR adds --org and --token options for non-interactive bk CLI configure.
Note: due to multiple bugs in current buildkite packages system, I can't verify that I really can push packages after non-interactive configuration. But I can't push packages with current release version too. I am not familiar with other buildkite features, so unfortunately can't test my changes

Thanks for the contribution @stone-w4tch3r! ❤


add better labeling for endpoints

Adds better labeling. Instead of one label string it's now multiple labels
micro_stats_stats_total_requests{instance_id="RDwcmXgtzvf04yRAQtZsnS",name="command",service="roku",subject="services.roku.command"} 4


"TypeError: path.charAt is not a function"

Since https://github.com/eslint/eslint/pull/2711 isn't in a tagged release yet, if your .eslintrc file has:
{
  "extends": ["standard", "standard-react"]
}

It'll throw TypeError: path.charAt is not a function.
It looks like standard is using a hardcoded eslint: https://github.com/feross/standard/blob/22e640da289a6d30e631bacbd85037ba33d776de/package.json
For people that wanna use this on its own, you'll need to install the hard-coded version of eslint until there's a new tagged release.
Maybe it's a good idea to add a temporary note to the README?

For anyone that might have this same issue, in the meantime it can be solved by using:
{
  "eslint": "git://github.com/eslint/eslint.git#fff52aecaf1d073952201b3f128e6664f529a24e"
}

@cesarandreu Yeah, feel free to add a note to the readme! Good idea!

eslint 0.23.0 is now released so this is no longer an issue! :+1:

:+1:

I'm getting the same error in Sublime and I am at eslint 0.24 already.
This is my project npm list:
eslint.........................[0.24.1]
eslint-config-standard..........[3.4.1]
eslint-config-standard-react....[1.0.1]
eslint-plugin-react.............[2.7.1]
Any idea what might be causing this?


Sign up with email?

Is it not possible to sign up in the app with email? It shows in the screenshots that you can but when you load the latest build of the app you have to use your telephone number or facebook. I need to use email. Is this possible? Is it a setting I need to change?
Thanks,
Martyn.

@RomanPronin In which commit the ability to register via email is removed?

@EminDemiri commit - https://github.com/QuickBlox/q-municate-android/commit/2a70f12ab022d72fc5d41748e6f668043e8255e4


TypeError: Cannot redefine property: ReadStream

After updating my project to NodeJS 14.4.0, graceful-fs ungracefully throws
TypeError: Cannot redefine property: ReadStream
    at Function.defineProperty (<anonymous>)
    at Object.patch ([PATH]\node_modules\graceful-fs\graceful-fs.js:223:10)
    at Object.<anonymous> ([PATH\MYFILE.ts])
    at Module._compile (internal/modules/cjs/loader.js:1200:30)
    at Module._compile ([PATH]\node_modules\ts-node\src\index.ts:858:23)
    at internal/modules/cjs/loader.js:1220:10
    at Object..ts ([PATH]\node_modules\ts-node\src\index.ts:861:12)
    at Module.load (internal/modules/cjs/loader.js:1049:32)
    at Function._load (internal/modules/cjs/loader.js:937:14)
    at Module.require (internal/modules/cjs/loader.js:1089:19)

It seems that line 223 is run twice, one with a callstack from loader.js, another one directly from the gracefulfs.gracefulify(fs) call in my code.
NodeJS: 14.4.0
Windows 10
graceful-fs: 4.2.4

This indicates something else has replaced the fs.ReadStream property with a non-configurable property or otherwise frozen fs.  I just tried the following on node.js 14.4.0 and 14.5.0:
const gfs = require('graceful-fs');
const fs = gfs.gracefulify(require('fs'));

No exceptions from this.  Maybe you could find some additional information using console.log(fs.ReadStream.toString()) - this might help you find what has locked the property.
IMO the exception you are seeing is a legitimate failure, graceful-fs should not suppress this error.

Finally came back to this project. Thanks for the hint, here's the output of the console.log(fs.ReadStream.toString()):
function ReadStream(path, options) {
  if (!(this instanceof ReadStream))
    return new ReadStream(path, options);

  // A little bit bigger buffer and water marks by default
  options = copyObject(getOptions(options, {}));
  if (options.highWaterMark === undefined)
    options.highWaterMark = 64 * 1024;

  // For backwards compat do not emit close on destroy.
  if (options.emitClose === undefined) {
    options.emitClose = false;
  }

  this[kFs] = options.fs || fs;

  if (typeof this[kFs].open !== 'function') {
    throw new ERR_INVALID_ARG_TYPE('options.fs.open', 'function',
                                   this[kFs].open);
  }

  if (typeof this[kFs].read !== 'function') {
    throw new ERR_INVALID_ARG_TYPE('options.fs.read', 'function',
                                   this[kFs].read);
  }

  if (typeof this[kFs].close !== 'function') {
    throw new ERR_INVALID_ARG_TYPE('options.fs.close', 'function',
                                   this[kFs].close);
  }

  Readable.call(this, options);

  // Path will be ignored when fd is specified, so it can be falsy
  this.path = toPathIfFileURL(path);
  this.fd = options.fd === undefined ? null : options.fd;
  this.flags = options.flags === undefined ? 'r' : options.flags;
  this.mode = options.mode === undefined ? 0o666 : options.mode;

  this.start = options.start;
  this.end = options.end;
  this.autoClose = options.autoClose === undefined ? true : options.autoClose;
  this.pos = undefined;
  this.bytesRead = 0;
  this.closed = false;
  this[kIsPerformingIO] = false;

  if (this.start !== undefined) {
    checkPosition(this.start, 'start');

    this.pos = this.start;
  }

  if (this.end === undefined) {
    this.end = Infinity;
  } else if (this.end !== Infinity) {
    checkPosition(this.end, 'end');

    if (this.start !== undefined && this.start > this.end) {
      throw new ERR_OUT_OF_RANGE(
        'start',
        `<= "end" (here: ${this.end})`,
        this.start
      );
    }
  }

  if (typeof this.fd !== 'number')
    this.open();

  this.on('end', function() {
    if (this.autoClose) {
      this.destroy();
    }
  });
}

Seems this is an older version of lib/fs.js from the nodejs/node repo. I'm using NodeJS 12.18.0, and here's my package.json:
{
  "name": "...",
  "version": "1.0.0",
  "description": "...",
  "main": "index.js",
  "scripts": {
    "start": "ts-node index.ts",
    "test": "jest"
  },
  "author": "",
  "license": "ISC",
  "engines": {
    "node": "=12.18.2"
  },
  "engineScrict": true,
  "dependencies": {
    "@google-cloud/translate": "^4.1.1",
    "add": "^2.0.6",
    "axios": "^0.18.0",
    "better-sqlite3": "^5.4.0",
    "chalk": "^2.4.2",
    "cheerio": "^1.0.0-rc.3",
    "commander": "^2.20.0",
    "crypto": "^1.0.1",
    "csv-parser": "^2.3.3",
    "firebase-admin": "^7.4.0",
    "fs": "0.0.1-security",
    "fs-extra": "^8.0.1",
    "graceful-fs": "^4.2.2",
    "https-proxy-agent": "^2.2.1",
    "image-size": "^0.7.4",
    "js-yaml": "^3.13.1",
    "json-stable-stringify": "^1.0.1",
    "log-update": "^3.3.0",
    "mongodb": "^3.5.9",
    "mz": "^2.7.0",
    "node-fetch": "^2.3.0",
    "ora": "^3.4.0",
    "probe-image-size": "^4.1.1",
    "sharp": "^0.24.1",
    "svg-to-png": "^4.0.0",
    "tiny-async-pool": "^1.0.4",
    "unbzip2-stream": "^1.3.3",
    "xml-stream": "^0.4.5",
    "yarn": "^1.22.5"
  },
  "devDependencies": {
    "@types/better-sqlite3": "^5.2.3",
    "@types/cheerio": "^0.22.11",
    "@types/commander": "^2.12.2",
    "@types/fs-extra": "^7.0.0",
    "@types/graceful-fs": "^4.1.3",
    "@types/image-size": "^0.7.0",
    "@types/jest": "^24.0.12",
    "@types/js-yaml": "^3.12.1",
    "@types/json-stable-stringify": "^1.0.32",
    "@types/mz": "0.0.32",
    "@types/node": "^11.13.7",
    "@types/node-fetch": "^2.3.3",
    "@types/ora": "^3.2.0",
    "@types/sharp": "^0.24.0",
    "@types/unzip": "^0.1.1",
    "jest": "^24.7.1",
    "ts-jest": "^24.0.2",
    "ts-node": "^8.1.0",
    "typescript": "^3.9.7"
  }
}

Just noticed it might be connected to TypeScript. When using TypeScript 3.7.5, everything runs fine. This issue happens when TypeScript is at 3.9.7.
No idea why.

It could be the TypeScript implementation of import * as fs from 'fs' which is breaking the object.  Not sure if TypeScript will allow you to import fs from 'fs' (node.js provides the whole module via the default export).  You can do a test without using graceful-fs:
import * as fs from 'fs';

let ReadStream = fs.ReadStream;
Object.defineProperty(fs, 'ReadStream', {
  get: function () {
    return ReadStream
  },
  set: function (val) {
    ReadStream = val
  },
  enumerable: true,
  configurable: true
});

Again maybe import fs from 'fs' will do better.  I'm closing this issue as I believe the bug is (or maybe was) in TypeScript.


[Toolkit feature]: Ability to see size of area/cylinder lights

Contact Details (Optional)
No response
What is the context of the feature/improvement?
It gets a bit difficult to see the size of lights.
Please describe the feature/improvement?
Positioning and rotating lights can get frustrating when you don't even know what direction it's facing.
What would be your solution? (optional)
A little wireframe of the shape of the light (like in blender) would be really helpful.
Version
2024.1.1

Hey @macxwdc ,
We have an internal ticket ( REMIX-2670 ) to create better light manipulators (with interactive features).
This should implement your feature.
Thank you

Hi @macxwdc ,
We now have manipulators for the 5 main light types and they should all be in the 2024.4.1 version of the toolkit full changelog


Script execution time can't go below ~1s

Seemingly an interval of less than 1000ms has no effect. Needs investigating.

Have confirmed this was a script-specific issue


content was covered by flutter_sticky_header

info_popup does not show content when info_popup action on flutter_sticky_header. version 4.0.0 is ok, but not available on 4.3.1

If you can share the mistake you received, I can be more helpful. Thank you.


Added check for update in any mandatory release of karmor CLI

Signed-off-by: sibashi<EMAIL_ADDRESS>Fixes #249
the function checkForUpdates first finds the latest release that contains the keyword "mandatory" in its release notes
compared it with current version from selfupdate.GitSummary
If diffrent informs the user

Hey @TheRealSibasishBehera . Great work on this 🚀.
Could you show an image/gif that this feature is working? If tested.

the first stdout The client is up to data is from CheckForUpdates()
For this feature to identify major updates , the release notes must have a keyword mandatory , i dont think this keyword is used in release notes till now .
On further releases we can add the mandatory keyword in case of a major update
If its alright i can add a unit test with a mock *RepositoryRelease , which have that keyword and test it.

@TheRealSibasishBehera i don't think a test would be necessary for this feature. As long as the keyboard isn't case sensitive. If it is case sensitive, could you make it "MANDATORY" all caps?

@PrimalPimmy I have updated the code , please take a look


Update from deprecated ADS extension to current

Existing doc recommends SQL Server 2019 extension, which is deprecated for this purpose in favor of the Data Virtualization Extension.

@nfd9001 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MikeRayMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


api,ui: vm template format, fix vm info link

Description
Fixes #9084
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
https://github.com/apache/cloudstack/assets/153340/190e05a8-b6dc-45cc-9ba1-6f16bd9af8a7
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9654

@blueorangutan test rocky8 kvm-rocky8

@weizhouapache a [SL] Trillian-Jenkins test job (rocky8 mgmt + kvm-rocky8) has been kicked to run smoke tests

[SF] Trillian test result (tid-10236)
Environment: kvm-rocky8 (x2), Advanced Networking with Mgmt server r8
Total time taken: 49562 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9094-t10236-kvm-rocky8.zip
Smoke tests completed. 128 look OK, 3 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_events_resource
Error
425.66
test_events_resource.py

test_02_trigger_shutdown
Failure
346.71
test_safe_shutdown.py

test_02_list_cpvm_vm
Failure
0.05
test_ssvm.py

test_04_cpvm_internals
Failure
0.06
test_ssvm.py