Debugging in the Cloud Sandbox not (anymore) possible

Describe the bug
Debugging is currently not possible in the Cloud Sandbox. It does not work with the standard sandbox "Sandbox" nor with any other sandbox with a different name. The extension can be published to the sandbox and installed, but Visual Studio code cannot start the debug process.
To Reproduce
Steps and to reproduce the behavior:

Add a new launch option to the launch.json file. This looks like this.

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Microsoft cloud sandbox",
            "type": "al",
            "request": "launch",
            "startupObjectId": 22,
            "breakOnError": true,
            "breakOnRecordWrite": false,
            "launchBrowser":true
        }
    ]
}

I have activated the detailed log in the settings. It contains the following error which is probably responsible for the fact that debugging does not work:
 initialize
06/26/2019 07:54:22 [/6] Process:

 launch
06/26/2019 07:55:11 [/13] Process:

 disconnect
06/26/2019 07:55:11 [/13] 05:54:50.3468991 - null - ChangeState(Disconnected, Connecting)
05:55:11.4297311 - null - Disconnected
05:55:11.4307441 - null - Transport.Dispose()
05:55:11.4307441 - null - Closed
05:55:11.4457379 - null - Error: System.Net.Http.HttpRequestException: Error sending the request. ---> System.Net.WebException: The connection to the remote server cannot be established. ---> System.Net.Sockets.SocketException: A connection attempt failed because the remote peer did not respond correctly after a certain period of time, or the established connection was faulty because the connected host did not respond <IP_ADDRESS>:7049
   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of internal exception stack monitoring ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of internal exception stack monitoring ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.DebugAdapter.DebuggerService.<OpenConnectionAsync>d__53.MoveNext() in F:\a\435\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\DebugAdapter\ServerConnection\DebuggerService.cs:Line 201.
--- End of stack monitoring from the previous location where the exception was raised. ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.DebugAdapter.DebugAdapterLaunchRequestHandler.<StartDebugging>d__8.MoveNext() in F:\a\435\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\DebugAdapter\DebugAdapterLaunchRequestHandler.cs:Line 267.
--- End of stack monitoring from the previous location where the exception was raised. ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.DebugAdapter.DebugAdapterLaunchRequestHandler.<HandleAsync>d__4.MoveNext() in F:\a\435\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\DebugAdapter\DebugAdapterLaunchRequestHandler.cs:Line 90.
05:55:11.4737396 - null - Error: System.Net.Http.HttpRequestException: Error sending the request. ---> System.Net.WebException: The connection to the remote server cannot be established. ---> System.Net.Sockets.SocketException: A connection attempt failed because the remote peer did not respond correctly after a certain period of time, or the established connection was faulty because the connected host did not respond <IP_ADDRESS>:7049
   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of internal exception stack monitoring ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of internal exception stack monitoring ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.DebugAdapter.DebuggerService.<OpenConnectionAsync>d__53.MoveNext() in F:\a\435\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\DebugAdapter\ServerConnection\DebuggerService.cs:Line 201.
--- End of stack monitoring from the previous location where the exception was raised. ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.DebugAdapter.DebugAdapterLaunchRequestHandler.<StartDebugging>d__8.MoveNext() in F:\a\435\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\DebugAdapter\DebugAdapterLaunchRequestHandler.cs:Line 267.
--- End of stack monitoring from the previous location where the exception was raised. ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.DebugAdapter.DebugAdapterLaunchRequestHandler.<HandleAsync>d__4.MoveNext() in F:\a\435\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\DebugAdapter\DebugAdapterLaunchRequestHandler.cs:Line 90.

Expected behavior
Debugging must be possible again in the Business Central Cloud Sandbox. Connection question: How is it possible that port 7049 is also used in the cloud? Has this been the case so far? I thought that was purely for the on-premises variant.
Versions:

AL Language: 3.0.126610

Business Central: 14.0.29537.29654 and 14.1.33107.0, tried both

Hi! Let's get the issue to customer support as we will require more detailed information on the issue.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal

Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company


Initial approach to reduce install times

Part of #1870

what about other places like the repository images?

what about other places like the repository images?

what do you mean about repository images? As I said in the issue #1870 these are the changes done for now to reduce the times as shown since these mappers were the worst performers. The other modules might be follow-up tasks?

what do you mean about repository images?

https://github.com/iasql/iasql/blob/main/src/modules/aws_ecr/index.ts#L482. I think this one runs sequentially.

As I said in the issue #1870 these are the changes done for now to reduce the times as shown since these mappers were the worst performers. The other modules might be follow-up tasks?

ah got it, a follow-up makes sense.


⚠ Bofrost.at has degraded performance

In 0a3f684, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1721 ms

Resolved: Bofrost.at performance has improved in 4e4c414 after 30 minutes.


docs(README): Update translation status URL

https://www.isreacttranslatedyet.com/ is dead

A comment is always appreciated :)

@machour sorry about the curt closing, we mass-closed older issues today as we're bootstrapping the translation effort for the new docs.
All these issues don't apply anymore as:

This repo doesn't feed the legacy FR translation site anymore
New site's languages will only get published once we reach a critical translation content threshold, which would by definition start from upstream content (so any content issues would be better applied there).

'Hope this clarifies things a bit.


Speed up Hermes builds in CI

Summary
The build_hermes_macos jobs builds four architecture sequentially: iphoneos, iphonesimulator, catalyst and macos.
This PR tries to split the build process on 4 machines and then to collect the output on a following job.
This could  ~75% of the time spent by the CI when building hermes.
Changelog
[internal] - Speedup hermes builds
Test Plan
Wait for CircleCI. It should be green and Hermes builds should take about 10 minutes rather then 40 minutes.

Closing as this is already implemented in main now


factor code to smaller crates

async and tokio runtime are factored into a cli specific trait
consts are moved to config

Codecov Report

Merging #20 (97b5247) into dev (5376dee) will decrease coverage by 0.05%.
The diff coverage is 3.70%.

@@            Coverage Diff             @@
##              dev      #20      +/-   ##
==========================================
- Coverage   58.28%   58.22%   -0.06%
==========================================
  Files          31       31
  Lines        5832     5838       +6
==========================================
  Hits         3399     3399
- Misses       2433     2439       +6

Impacted Files
Coverage Δ

cli/src/lib.rs
0.00% <0.00%> (ø)

cli/src/main.rs
0.00% <ø> (ø)

config/src/lib.rs
40.29% <ø> (ø)

lib/src/wallet/keys.rs
45.86% <ø> (ø)

lib/src/lightclient/lightclient_config.rs
34.48% <100.00%> (+5.07%)
: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 5376dee...97b5247. Read the comment docs.


Add instant update to volume graphic upon changes caused by interactions

Warning: Untested - I needed slightly different commands for my machine so I was unable to fully test this change. Please give it a whirl before accepting! (If this is inconvenient, I can try it out next time I'm at a different machine)
Added functionality to audio widget so the graphic updates immediately when you modify the volume through it, rather than taking up to a second to reflect changes.
Additionally made some minor changes to code to make it more consistent.

That's great! Thank you very much! :+1:


Aggregators

Please avoid one word issues - they lack the context for everybody to participate openly. We should define a template with minimum viable content for a valid issue...


test_esd.ESDTestJSON.test_create_esd fails with profile not found

@jlongstaf
Please don't merge this until #705 has been merged, as it improves test teardown. This change was based on having a more consistent teardown process for tests.
What issues does this address?
Fixes #596
What's this change do?
Added a retry when checking whether esd has been applied. Since this can
take some time, we may expect one or two iterations of this retry to be
kicked before we succeed in applying esd with the policy given. If we
run out of iterations and we still haven't see the profile we're looking
for, then the test fails.
Where should the reviewer start?
Any background context?
test_esd fails because ESD is not fully applied before the verification
code runs. Inserting a delay (e.g. time.sleep(3) )before check_esd()
allows test to pass.
Ran the test multiple times. Did not see a failure ever, but this should
serve as a good starting point for a retry if there's a bug in the test
code.

@szakeri: if travis indicates this is a good build, I have tested this change with the new testrunner container and the esd test passes:
==================================================== test session starts ====================================================
platform linux2 -- Python 2.7.12, pytest-3.2.0, py-1.4.34, pluggy-0.4.0 -- /usr/bin/python
cachedir: ../../../../.cache
pytest-autolog: outputdir is /home/jenkins/f5-openstack-lbaasv2-driver/systest/test_results/f5-openstack-lbaasv2-driver_mitaka-tempest_12.1.1_undercloud_vxlan/api_7983ef1_20170802-201833
pytest-autolog: trace is disabled
rootdir: /home/jenkins/f5-openstack-lbaasv2-driver, inifile:
plugins: f5-sdk-2.3.3, f5-openstack-test-0.2.0, autolog-1.1.0, meta-0.1.1, symbols-0.1.0a3
collected 49 items
pytest-meta: discarded 0 items

api/test_esd.py::ESDTestJSON::test_create_esd PASSED
api/test_l7policy.py::L7PolicyTestJSON::test_create_l7_redirect_to_pool_policy PASSED
api/test_l7policy.py::L7PolicyTestJSON::test_create_l7_redirect_to_url_policy PASSED
api/test_l7policy.py::L7PolicyTestJSON::test_create_l7_reject_policy PASSED


[DOC] Reports scheduler

What do you want to do?

[ ] Request a change to existing documentation
[X] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Add documentation for reports scheduler feature
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

Resource - https://github.com/opensearch-project/reporting

After reading through the code and testing the plugin I found that I could not hit the reporting endpoints without errors. Reaching out to SME (maharup), they clarified that the report scheduler plugin can not be used without the reportsDashboard plugin. It is backend for reportsDashboard.  This feature is already documented at - https://opensearch.org/docs/latest/dashboards/reporting/. This the only use cases for end-users: working through Dashboards and API calls directly to reports-scheduler won’t work.
This being the case, I am closing out this PR as there is not further action for documentation to take.

Thanks, Aria!


Make it easier to plug in different parsers for file types.

Currently you can either use the built-in ones or provide a callable for each parser call.
This is an issue if, say, you want to plug in a different yaml parser for all yaml usage, particularly when configurator is used within an application or library whose source code you don't want to modify.
This also came up on #7 ...

@wimglenn ^^


Improve doc

Hi @amohrland,
When trying your project, I encountered this error
[warn] 	Note: Unresolved dependencies path:
[error] stack trace is suppressed; run last update for the full output
[error] (update) sbt.librarymanagement.ResolveException: Error downloading io.confluent:kafka-avro-serializer:5.3.1
[error]   Not found
[error]   Not found
[error]   not found: /Users/jules/.ivy2/local/io.confluent/kafka-avro-serializer/5.3.1/ivys/ivy.xml
[error]   not found: https://repo1.maven.org/maven2/io/confluent/kafka-avro-serializer/5.3.1/kafka-avro-serializer-5.3.1.pom

@guizmaii Thanks for this. CI should now be fixed for PRs (https://github.com/Banno/kafka4s/pull/111#issuecomment-547156097). Would you mind opening a new PR for this branch too? Travis CI doesn't seem to want to build older PRs.


CameraInfo not published to ROS Noetic unless the image is viewed in the Gazebo GUI

Environment

OS Version: Ubuntu 20.04.5 LTS x86_64
Source or binary build? Gazebo Fortress from source (as of yesterday)

Description

Expected behavior: The CameraInfo should be published as soon as the ros-ign-bridge has registered a ROS listener for the image topic.
Actual behavior: You need to manually view the image in the Gazebo GUI to trigger the publishing of the CameraInfo

Steps to reproduce

Open a Gazebo world with a camera
Run the ros-ign-bridge to publish the CameraInfo topic
rostopic echo the CameraInfo topic
BUG: No message is published
In the Gazebo GUI, add Image Display
Select the camera and hit the refresh button
The CameraInfo should now be published

Note: This might not be completely related to the ros_gz_bridge. Since this issue also happens with the following steps:

Open a Gazebo world with a camera
ign topic -l
ign topic -e -n 1 -t camera/camera_info
No data is echoed
Click on the refresh button in Image Display
The data should now be echoed in the terminal

Output

Before refresh:

After:

likely an issue in gz-sensors. Camera sensors do not generate / publish any data if there are no subscribers to the image topic. The CameraSensor::HasConnections only checks for subscribers to image data but not camera info. One potential fix is to also check camera info topic subscribers and in CameraSensor::HasConnections and change CameraSensor::Update function to publish only camera info data (and skip rendering image data) if there are only camera info subscribers.

Should I open a new issue in gz-sensors?

Closing because the root issue is in gz-sensors


Change dataset

Update sample dataset

New names: retail_stores and retail_stores_revenue
New store types (styling updated)
Update the SQL queries

Done at: https://github.com/CartoDB/cra-template-carto/pull/107


Linux Installation fails

Ubuntu 20.04 LTS
Python 3.8.2
I tried to install ledfx with "pip3 install ledfx" (pip (without "3") was not found)
Error message is that the file numpy/arrayobject.h is not found when trying to build wheel for aubio.
Then "ledfx --open-ui" says command not found.
If I try a second time no error message is displayed. (It says Requirement already satisfied for some packages, but does not install anything.)
I tried with sudo, error message was displayed once again, but not in an second try.

Try changing to Python Version. I run in Linux Mate (Ubuntu) Python version 3.6.9

Try changing to Python Version. I run in Linux Mate (Ubuntu) Python version 3.6.9

Also don't forget to try removing all needed packages en reïnstalling them.

Try Using :
/home/pi/.local/bin/ledfx --open-ui


feat(DataTable): expose pageButtonsCount config

@dclerici-ssc I added the prop to the story controls so it's configurable now


Do not mutate input buffer when computing the SHA1

In some cases, the input that was to be SHA1'd would be modified, which
was something of a problem if you were, for example, hashing a buffer
and then writing it to a file: the content to be written to the file
was no longer what it originally was! This only seemed to happen if the
buffer was long enough; the case in the added test triggered the
now-fixed bug.

Merged, thank you!


[windows] Pin Azure CLI to 2.52.0

Description
Pin Azure CLI to 2.52.0
Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run windows2019,windows2022


Fix(UI): Add the add element at rear

[ ] Add an "Add" button for creating new notes, boards, or rows at the end of rear, similar to the functionality in Google Keep.

[ ] Ensure that empty containers occupy their designated space and allow for seamless addition of new items at the rear.

@narainkarthikv what do you mean by rear ??


feat: Add github link button to learn documentation pages

merged https://github.com/ockam-network/website/commit/5cc38bfb7160fd53adfca0e30f448d651b995971


Incorrect link to missing file "docs/api.md" in README.md

On the GitHub page for UniK, in README.md, in the Documentation section, under the Developer Documentation heading, the first link ("UniK's REST API") does not work (the linked-to file "docs/api.md" does not exist in the repo), so GitHub returns a 404 error.

True!
I removed the link for now.
@ilackarms  do you have the api docs file on hand and can push it?

Can't seem to find that doc lying around. It may have to be rewritten. It may have never been written at all come to think of it...


Mount the storage(empty-dir) for cortex ruler

This PR mounts the storage (empty dir) also for ruler (like what we did for alertmanager, we mount /tmp for it).
This is needed, otherwise, the ruler will have some errors like make /rules, read-only filesystem in the log.
However, every rules/rule groups are stored in minio.

/lgtm


Failed migrations are not properly reflected on the VMI

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened:
After a failed migration I see
  migrationState:
    migrationUid: b0a83915-a7b6-11e9-a058-525500d15501
    sourceNode: node01
    targetNode: node02
    targetPod: virt-launcher-vmi-migratable-46t7x

on the VMI. If I try to create a new migration, I get
Error from server: error when creating "examples/migration-job.yaml": admission webhook "migration-create-validator.kubevirt.io" denied the request: in-flight migration detected. Active migration job (b0a83915-a7b6-11e9-a058-525500d15501) is currently already in progress for VMI vmi-migratable.

The migration object was not even present anymore and I did not do a force-delete, so with finalizers it would have been able to  clean this up.
What you expected to happen:
If a migration fails, the VMI status should be updated accordingly.
How to reproduce it (as minimally and precisely as possible):
The target pod crashed when it was in the PreMigrationTarget preparations.
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Tricky :) ... I'll take a look.

I guess this is still an issue?
/remove-lifecycle stale


Use CharSequence instead of String

AppIntroFragmet was overkill. Even the example with Html.fromHtml works now and it is simpler.

Why I didn't used the CharSequence instead of Spanned on my PR!!! :) :+1:

@SandroMachado exactly. CharSequence is the mother of all. :)

@tasomaniac thanks for your work :)


Fixing Typos

Made use of the ReSpeller Extension for ReSharper

There are a few cases where _field is replaced by this._field since the rest of the source doesn't use this you might want restore this to the original behaviour.

@DevWouter  Ah, good catch!  That is ReSharper getting ahead of itself, I will correct.

I have fixed up the issue pointed out by @DevWouter

Looks good now. :+1:

@gep13 think it looks good, there's breaking changes which we really try to avoid. But in this case makes sense to do an exception,
Please get branch up to date and I'll look gain.

@devlead rebased and pushed.
That is a very good point about the potential breaking change.  Although in this case, the Chocolatey Alias is slated for release in 0.5.6, so not currently available outwith MyGet Sources, so I "think" in this instance, we are ok.  Right?

@gep13 yes in this case it's "ok", it's just get a bad gut feeling when seeing rename of public members :wink:


Support ELKO ESH 316 Endevender RF

Issue
Homebridge pull #3409 added support for the ELKO ESH 316 Endevender RF (see also issue #3258). The device needs support in homebridge-hue, so that it is not shown as an "unsupported" accessory tile on the front of the Home app.
The device in question is a battery powered rotary dimmer knob with three events: Rotate counter-clockwise ("Dim Down"), rotate clockwise ("Dim Up") and press rotary wheel ("Press"). The device has pictures and documentation on the manufacturers website.
Suggested implementation
I'm too inexperienced with GitHub to actually make a pull for this, so I'd like to simply propose the following change that I've made and tested to work quite well.
I suggest that HueSensor.js is amended to include the following in the same area as the IKEA remotes etc (line 281-924 area):
      } else if (
        this.obj.manufacturername === 'ELKO' &&
        this.obj.modelid === 'ElkoDimmerRemoteZHA'
      ) {
        // ELKO ESH 316 Endevender RF
        this.createLabel(Characteristic.ServiceLabelNamespace.ARABIC_NUMERALS)
        this.createButton(1, 'Press', SINGLE)
        this.createButton(2, 'Dim Up', SINGLE)
        this.createButton(3, 'Dim Down', SINGLE)
        this.type = {
          key: 'buttonevent',
          homekitValue: function (v) { return Math.floor(v / 1000) },
          homekitAction: hkZLLSwitchAction
        }

Improvement potential
The suggested change works, and all three button events are registered in HomeKit. Firing sequential button events on rotary knob rotation is somewhat nonsensical, though. I don't really know how to address this, as I cannot see any other device that I can steal any approach from, and I cannot find that HomeKit really supports incremental/delta change actions (e.g. "Increase luminosity by X percentage points" etc.) I would be more than happy to have improvements suggested to take this into account.
Cheers!

I know a couple of devices with a dial or otherwise supporting turning:

The old model IKEA Trådfri wireless dimmer (model: TRADFRI wireless dimmer).
The IKEA Symfonisk controller (model: SYMFONISK Sound Controller).
The Xiaomi magic cube (model: lumi.sensor_cube);
The Lutron Aurora (model: Z3-1BRL);

The deCONZ REST API reports regular button event values for the IKEA devices and the Lutron Aurora, so there's no special handling in Homebridge Hue.  It reports the rotation angle for the Xiaomi cube, which Homebridge Hue translates to 0° <= Single Press < 45° <= Double Press < 90° <= Long Press, with different buttons for clockwise vs counterclockwise turns.
The Hue bridge uses the ZLLRelativeRotary sensor type for the Aurora.  Currently, Homebridge Hue only looks at the direction and maps all values to Single Press.  It's been a while since I looked at this device.  Not sure I fully understand the ZLLRelativeRotary; I don't think the Hue bridge exposes it to HomeKit, so no help there.

I see, thanks. I understand that Apple isn't positioning HomeKit to handle such delta (incremental/relative) changes in HomeKit – I guess HomeKit is a touch too slow to handle this gracefully, and Apple would rather this be handled internally by the device manufacturers. Still, it'd be nice to get this sort of integration in the future, so that users would be able to control anything with rotary knobs like this – audio volume, colour, fan speed etc.
I would then suggest that the change is implemented as suggested, as it is in line with the solution for TRADFRI wireless dimmer and that it, in fact, works.

In v0.12.22.

I'm trying to understand the outcome of the recent addition to v0.12.22 you both discussed here. Am I to understand I can not currently incorporate one of these dials for incremental brightness/volume changes?

Do you use the SYMFONISK Sound Controller to dimm the lights or is it possible to do the sound controller connected to hue bridge to set the volume of the Sonos in Homekit?


Add info icon to multiplex test card

Background
Our users are unclear where their results are submitted after entering test results. This is important information to know especially for users submitting multiplex information as flu isn't reportable in all states. When a disease is not reportable, users have to go through a formal process with their state to justify submitting data. It's important for our users to know that flu data is only stored in SimpleReport and not shared with anyone else. This will give them the peace of mind that they're doing nothing wrong in entering flu results.
The proposed solution is to add an info icon next to the "Submit" button on the multiplex test card. When a user hovers over the icon, they can learn more about where their test results are sent.
Design
Figma: https://www.figma.com/file/NPSPM5SBzQ7Ra3mmr9M9cB/SimpleReport-Public-Site?node-id=7645%3A26943
Screenshot

Tool tip copy:
COVID-19 results are reported to your public health department. Flu results are not reported at this time.
Specs

Acceptance Criteria
Use the existing tool tip pattern we have for the test card.

Dependent on #3481, since we only want this info icon to appear on multiplex test cards.
The update will probably happen in QueueItem.tsx


Better handle unknown state.

Fixes https://github.com/containerd/cri/issues/1039.
For https://github.com/containerd/containerd/issues/3873.
Use a new in-memory only field to represent unknown state. With this, we'll preserve the status checkpoint, instead of overwriting it with unknown status.
We may want to cherry-pick the fix.
/cc @sofat1989
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

I've tested this change with the version before we removed the unknown state test https://github.com/containerd/cri/issues/1310

Use a new in-memory only field to represent unknown state. With this, we'll preserve the status checkpoint, instead of overwriting it with unknown status.

I like that better.

Agree cherry pick.


Why does Client configuration data have to be JSON-LD serialized?

When a Client Identifier is dereferenced, the resource MUST be serialized as an application/ld+json document unless content negotiation requires a different outcome.

Why does Client configuration data have to be JSON-LD serialized?
OpenID Federation Specification defines Automatic Registration feature that achieves the same goal and the Entity Statement is a signed JWT: https://openid.net/specs/openid-connect-federation-1_0.html#section-10.1

Issue #95 seems to be referencing the Federation draft too

We should take a serious look at whether we could replace the use of Solid-OIDC client identifiers with this definition from the OpenID Federation spec


Fix string equality checks

From the Python 3.8 changelog:

The compiler now produces a SyntaxWarning when identity checks (is and is not) are used with certain types of literals (e.g. strings, numbers). These can often work by accident in CPython, but are not guaranteed by the language spec. The warning advises users to use equality tests (== and !=) instead.

Cheers


[FSPE-7725] Added portal template for page level actions

https://ctl.atlassian.net/browse/FSPE-7725

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-45/1/. :white_check_mark:

You can check this PRs instance in https://6b0690d19a980f80cd27a89eb6fa5f71864224aa-chi-pr.enterprise.ctl.io


Move getLaunchOptions from ReactActivity to ReactActivityDelegate

After https://github.com/facebook/react-native/commit/3c4fd42749e0079b0cf54e1106bf81c993f9d29a, getLaunchOptions no longer exists in class ReactActivity.
We need refactor UIExplorerActivity to fix the build error.

cc @foghina

Good catch, thanks for the PR! Please fix the class thing & I'll import this.

@foghina Done.

@leeight updated the pull request.

Two more nits but that's it.

@facebook-github-bot import

Thanks for importing.If you are an FB employee go to Phabricator to review internal test results.

(^ ignore this, we'll ship it normally, I'm testing our import script)

@leeight updated the pull request.

@leeight updated the pull request.

Thanks!!

@facebook-github-bot shipit

Thanks for importing.If you are an FB employee go to Phabricator to review internal test results.

so how can i send data via android to RN now ?


CT-3144 Fix test edges type filter on Graph

resolves #8692

Problem

After upgrading to 1.6.2 from 1.5.1 our build is taking way longer to start the first model
From around 7 to 8 minutes to complete to more than 1 hour without starting.
Solution

Changed the networkx function used to filter test type edges
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
[x] This PR includes type annotations for new and modified functions

@renanleme Thanks again for your work here.
I found that there were a couple remaining problems, which can be resolved by using this definition of filter_edges_by_type in your PR:
    def filter_edges_by_type(self, first_node, second_node, edge_type):
        return self.graph.get_edge_data(first_node, second_node).get("edge_type") != edge_type

I found that the use of get_edge_data() is considerably faster than the double index operation it replaces, and the != comparison fixes a simple typo.
If you are able to make this change in your PR and sign the CLA, I will merge it and get it backported so that all dbt users can benefit!

@renanleme Thanks again for your work here.
I found that there were a couple remaining problems, which can be resolved by using this definition of filter_edges_by_type in your PR:
    def filter_edges_by_type(self, first_node, second_node, edge_type):
        return self.graph.get_edge_data(first_node, second_node).get("edge_type") != edge_type

I found that the use of get_edge_data() is considerably faster than the double index operation it replaces, and the != comparison fixes a simple typo.
If you are able to make this change in your PR and sign the CLA, I will merge it and get it backported so that all dbt users can benefit!

Hey, @peterallenwebb, thanks for helping me with it!
I updated the pr as suggested, I tested my use case locally and it's a little bit faster indeed.
Let me know if anything else is needed.


Bug in ProgressIndicator plugin is causing crash in iOS

The ProgressIndicator native code plugin (org.pbernasconi.progressindicator) is causing EXC_BAD_ACCESS crashes in iOS. This seems to occur sometimes when calling hide() after an indicator has already been hidden. This happens in the JavaScript exception handlers in Application.ts.
There are a couple of options here:

Look for a replacement progress indicator plugin
Don't call hide() in the script exception handlers
Fork and attempt to fix the current plugin
Submit issue to the original plugin maintainer

Option 1 is attractive because the current plugin does not support Android, so finding an alternative plugin that has Android support would allow me to ditch the MockApi implementation for Android. If no subtable alternative could be found, perhaps I could just use the mock implementation which utilizes Ionic.
I would like to avoid option 2 because if an exception occurs during an HTTP request the progress indicator may never be hidden, leaving the user stuck.
I'll try 4 for now; opened pbernasconi/cordova-progressIndicator#20.

I have submitted a fix ahd pull request for this bug in the plugin's github project.
pbernasconi/cordova-progressIndicator#21


Issue with k8s.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/

This is a Bug Report

Problem:
At 181 line: Link to OpenAPI v3.0 validation is broken.
| Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes.  Most validation can be specified in the CRD using OpenAPI v3.0 validation.
Proposed Solution:
| Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes.  Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation).
Page to Update:
https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/

/language en

/assign @pjhwa


Invalid token or serial number

Hello!
After I installed from HACS, I tried to add:

And the values are good:

What could be the problem?

At the moment the integration has no functionality for retries, so it could be that it fails on the first attempt. so retry it again, but wait a couple of minutes in between.


Support Safari as a default browser

When using assume with a fresh MacOS install I receive the following:
chrisnorman@MacBook-Pro ~ % assume

ℹ  Could not find default browser

? Select one of the browsers from the list  [Use arrows to move, type to filter]
> Chrome
  Brave
  Edge
  Firefox
  Chromium
  Stdout
  FirefoxStdout

Safari isn't included in this list - we should be able to detect it as a default browser or at least have it selectable in the list of browsers.

Even though I couldn't select Safari from the list, the settings that Granted created for me (TOML config below from ~/.granted/config) do actually open Safari for logging in to AWS SSO.
DefaultBrowser = "FIREFOX"
CustomBrowserPath = "/Applications/Firefox.app/Contents/MacOS/firefox"
CustomSSOBrowserPath = ""
LastCheckForUpdates = 1
Ordering = ""
ExportCredentialSuffix = ""

[Keyring]
  Backend = "keychain"


FINERACT-1079: Run spotlessApply before compileJava task

Description
Developers consistently have problems manually running the spotlessApply task after coding changes... See: https://github.com/apache/fineract/pull/1151 and https://github.com/apache/fineract/pull/1148
maybe we should just run spotlessApply just before compilation and skip the tasks to check for spotless failures? Or we run both of them: Run spotlessApply before spotlessCheck (seems wasteful). Is this a good idea? I wonder?
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[ ] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[ ] API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm has been updated with details of any API changes.

[ ] Integration tests have been created/updated for verifying the changes made.

[ ] All Integrations tests are passing with the new commits.

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

Is this a good idea? @thesmallstar , @xurror , @ptuomola ?

I think if you do this spotlessCheck would run in the end.
But, SpotlessApply would have already fixed the violations (since it ran first).
I would suggest deliberately do a spotless Violation and  check if it does actually fix it, if it does I think we can safely do this.

I made a local violation and it was fixed..Please can you pull this locally and also test and let us know if it LGTY?

Yes. I've been thinking about this the very first time they asked me to run spotlessApply. It was kind of a PITA. I have no objections Concerning this. Thanks sending this.

@awasum @xurror @thesmallstar @vorburger Just one concern: doesn't this mean that you can then check in code that doesn't pass the Spotless formatting standards, and get that to pass the build anyway?
In other words: if I now commit code that is completely wrongly formatted, when Travis runs the build, it does spotlessApply so the build passes - but the fixed code is never committed into Github: so if I look at the source code on Github (or clone/branch the repository), it is still incorrectly formatted?
This to me would seem to defeat the whole purpose of Spotless: it should ensure that the code in Github is correctly formatted, not that the code that is compiled is formatted correctly. The compiler doesn't care about code formatting...
Also this means that the code everyone is running is actually different from what is checked into Github. So if you e.g. look at a stack trace from someone's build and compare the line numbers with source in Github - then the line numbers will not match, as spotlessApply may have changed them. Also this means that any source code you write is automatically modified by spotless without you getting a chance to review whether the changes are correct.
Unless I'm missing something here, then this does not sound like a good idea to me...

@awasum @xurror @thesmallstar @vorburger Just one concern: doesn't this mean that you can then check in code that doesn't pass the Spotless formatting standards, and get that to pass the build anyway?
In other words: if I now commit code that is completely wrongly formatted, when Travis runs the build, it does spotlessApply so the build passes - but the fixed code is never committed into Github: so if I look at the source code on Github (or clone/branch the repository), it is still incorrectly formatted?
This to me would seem to defeat the whole purpose of Spotless: it should ensure that the code in Github is correctly formatted, not that the code that is compiled is formatted correctly. The compiler doesn't care about code formatting...
Also this means that the code everyone is running is actually different from what is checked into Github. So if you e.g. look at a stack trace from someone's build and compare the line numbers with source in Github - then the line numbers will not match, as spotlessApply may have changed them. Also this means that any source code you write is automatically modified by spotless without you getting a chance to review whether the changes are correct.
Unless I'm missing something here, then this does not sound like a good idea to me...

@ptuomola ..I now see this as a problem than a solution. Thank you very much for catching this. I did not see all the edge cases and frankly should have put this as draft. I am not reverting this for us to look for a better solution. We should be looking for something like this: https://cwiki.apache.org/confluence/display/BEAM/Spotless+pre-commit
https://medium.com/@aruny3/improve-code-formatting-on-every-commit-7fbb0cdfdab6
https://github.com/diffplug/spotless/issues/178

Initially, I wanted something that will run just before the build or bootRun tasks.. But it looks like one needs to look for a way to do this immediately before committing.

#1158


Do not show scale in "Upgrade service" page.

Server version - V0.43.0-rc2
Steps to reproduce the problem:
Create a service with scale 2.
Upgrade the service , by setting the scale to some different value say 6.
Only existing 2 instances get upgraded. No new instances to satisfy the scale set during upgrade is created.
The scale set during upgrade service is ignored , which is the expected behavior.
Do not show scale in "Upgrade service" page.

Server version - V0.43.0-rc2
scale is not shown in upgrade page anymore.


Proxy for AdGuard Status

Is your feature request related to a problem? Please describe.
No problem; I was looking to setup a Heimdall widget that concisely shows the enabled/disabled status of my three AdGuard Home instances. I was thinking if this sync app had an API that returned the status of each configured AdGuard instance it would make configuration of the widget and accessing the statuses much easier.
Describe the solution you'd like*
The simplest option might be to modify the existing replicaStatus type used by the/api/v1/status endpoint:
type replicaStatus struct {
	Host   string `json:"origin"`
	URL    string `json:"url"`
	Status string `json:"status"`
	Error  string `json:"error"`
	ProtectionEnabled *bool `json:"protection_enabled"`
}

Where ProtectionEnabled is the value returned from the AdGuard Home /control/status endpoint. Or, nil if the endpoint is unavailable.
I've not used Go, it looked like *bool is how to do an optional boolean.
Describe alternatives you've considered
This feature is more related to AdGuard Home and Heimdall, as opposed to syncing. So the more direct alternative is to just have Heimdall query each AdGuard instance directly. However, the configuration is much messier since a URL, username, and password are required for each instance.
Anything else?
I'd be happy to do the update; I wanted to get feedback on this idea before doing that.

Hi @JCapriotti
Thank you for this request.
I can add the flag to the status, the information is already fetched anyway.
Heimdal has already an API integration in adguard-home.
You could also extend this integration, to show the protection status. (Just a thought)

Great; I saw the PR... thanks for handling that so fast!
Regarding Heimdall, I was torn between adding to the existing integration vs creating a new one. I'll have to play around with the layout a bit to see if I can make the existing one work for this.

The change can be tested in the latest image.

released with https://github.com/bakito/adguardhome-sync/releases/tag/v0.5.3


fine-tune pinch gesture/mouse wheel zoom speed

From Discord:

Alder Agilao: Hi. Zooming on an iPad is incredibly difficult, it zooms and zooms out way to much. Any better way to control? Using an iPad to out to a tv for my group

jeepinbird: I second this. Pinch zooming goes really fast but using the buttons works great.

Relevant code:
https://github.com/dungeon-revealer/dungeon-revealer/blob/3da9d6add384babdd4f12b7dafe657a1414dfa47/src/map-tools/drag-pan-zoom-map-tool.tsx#L68
https://github.com/dungeon-revealer/dungeon-revealer/blob/3da9d6add384babdd4f12b7dafe657a1414dfa47/src/map-tools/drag-pan-zoom-map-tool.tsx#L91

The exponential function might be the problem 🙈

My guess is that the scroll wheel on a mouse changes in discrete and predictable steps, while the pinch gesture can vary a lot. The exponential function will wildly exaggerate whatever wheel is doing.

The wheel variable does have either the value -1 or 1 for both wheel and mouse zoom. There is not really a right speed, only too fast or too slow, so I feel it is a bit of a hard task to figure out the "correct" value, especially since I did not perceive stuff as too fast 😅

Hmm, maybe the pinch gesture has a higher sample rate than a wheel scroll and that leads to the difference in perceived speeds.


ecosystem-ci

reference:

vite: https://github.com/vitejs/vite-ecosystem-ci
vue: https://github.com/vuejs/ecosystem-ci

our ecosystem for now:

rspack-plugins: https://github.com/rspack-contrib/rspack-plugins
modern.js: https://github.com/web-infra-dev/modern.js
nx: https://github.com/nrwl/nx-labs/tree/main/packages/rspack

add nx to the list

add npm create rspack@latest test to test our scaffold

Close by for we have implemented the ecosystem-ci


NO-ISSUE: Fail the bootc image build if all retries for container pull fail

/assign @pmtk

/lgtm


InvalidARN for some Elasticache resources

Version: 3.2.2
Minimal Config
regions:
  - global
  - eu-central-1
presets:
  common:
    filters:
      global:
        - property: "tag:to-delete/.*"
          type: "regex"
          value: "true"
          invert: "true"
accounts:
  <account_id>:
    presets:
      - common
resource-types:
  includes:
    - ElasticacheCacheCluster
    - ElasticacheSubnetGroup

Hi,
When running aws-nuke with the above config, the operation fails with the following errors:
ERRO[0005]elasticache-memcacheclusters.go:60 unable to retrieve tags                       error="InvalidARN: Input ARN string does not have 7 components.\n\tstatus code: 400, request id: <id>"

ERRO[0005]elasticache-subnetgroups.go:57 unable to retrieve tags                       error="InvalidARN: Input ARN string does not have 7 components.\n\tstatus code: 400, request id: <id>"

:tada: This issue has been resolved in version 3.3.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

@ekristen Thank you very much! Appreciate the prompt response!


Can't deactivate CSR - can't set status to -1

Our logic likely limits the status to positive values. We should check != 0 for status so we can deactivate the user/CSR.

This is invalid... I was accidentally using an old version of the SDK. Master already has this fixed.


Protocol Level field is missing in connect packet

From the spec:

The Server MUST respond to the CONNECT Packet with a CONNACK return code 0x01 (unacceptable protocol level) and then disconnect the Client if the Protocol Level is not supported by the Server [MQTT-3.1.2-2].

That means, the Parser should parse the CONNECT packet successfuly and save protocol level. However, there is no field to store protocol level in ConnectPacket.
The scope of the issue is to add the field to ConnectPacket and modify Encoder to properly encode it.

Fixed by #17.


Error: Could not start recording within 5 seconds

Sentry Issue: KAP-5VJ

macOS version:    Mojave (10.14)
Kap version:      3.3.1
Recording error

Error: Could not start recording within 5 seconds
    at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:108:21)

I had it too today

Me three. Reported via app.

Additional context for when this happened to me (and could repro). Kapturing another video of mine in Chrome with the contents zoomed in using the trackpad, not ⌘+ or ⌘-. Meta, right?!?

Changing the title of this issue to be a bit more specific, thank you for reporting!

**MacOS Version : ** Catalina ( 10.15.7 )
**Kap Version : ** 3.3.2
Recording error

Error: Could not start recording within 5 seconds
    at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:108:21)

I am still getting this error.

I just got the issue today as well. recording started and automatically stopped within 2 second showing failure message.
Mac OS Big Sur
Version 11.0.1

I'm getting the same error on macOS Catalina 10.15.5
Recording error
Error: Could not start recording within 5 seconds
    at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:108:21)

I'm getting the same error on macOS Catalina 10.15.5
Recording error
Error: Could not start recording within 5 seconds
    at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:108:21)

Just from having the same issue just now on macOS Big Sur.

Just from having the same issue just now on macOS Big Sur.

i just have this issue too .
Recording error
Error: Could not start recording within 5 seconds
at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:108:21)
This issue is already being tracked!

i just have this issue too .
Recording error
Error: Could not start recording within 5 seconds
at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:108:21)
This issue is already being tracked!

got it again today

Just to help about the root cause of this issue, it happens sometimes on my computer after multiple records (randomly) and i wasn't able to record again (even after reinstallation, temporary folders removed, etc), until i disabled microphone record 👍
cc. @sindresorhus

Confirming that this happens when using node-aperture 6.0.1, but not a problem on 5.2.0. Behaviour is inconsistent however, no problems on one machine, always fails with this error another.

Just had this problem :)

Just had this error
Kap 3.5.1
macOS 12.0.1
Intel Core
it works well the first time, then always shows me Error: Could not start recording within 5 seconds.
Tested aperture-node 6.1.0 example code with the electron-quick-start, it also show me Error: Could not start recording within 5 seconds.

Confirming that this happens when using aperture-node 6.0.1, but not a problem on 5.2.0. Behaviour is inconsistent however, no problems on one machine, always fails with this error on another.

it works well with aperture-node 5.2.0
and when I test it in node, aperture-node 6.1.0 also can work well.
so maybe aperture-node 6.x has some compatibility issues with electron?

Experiencing this issue. Happens on both primary and external monitors. Worked the first time, then fails every time after.
Kap 3.5.1, installed using brew.
macOS Big Sur 11.6 (20G165)
MacBook Pro (16-inch, 2019)
2.4 GHz 8-Core Intel Core i9
32 GB 2667 MHz DDR4
AMD Radeon Pro 5300M 4 GB

Seems like it's an issue with 3.5.1 or even 3.5.0. I reinstalled older version (3.4.2) and everything is working fine
MacOS 12.0.1
MacBook Pro (13", 2017)

Recording error
Error: Could not start recording within 5 seconds
at Timeout._onTimeout (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/aperture/index.js:132:19)
MacOS 12.1

This issue was fixed in https://github.com/wulkano/aperture-node/pull/24 but Kap didn't update to aperture-node 6.1.1 yet.

Same error for me on 3.5.0/3.5.1— on latest OS version / Intel 2017 macbook pro
Tried reinstalling 3.4.2 but that won't run at all. It only works on the first capture after a system restart.

started seeing this the other day.
MacOS 11.4
Kap 3.5.1
Intel macbook pro, 2019
going to update this machine's OS and see if it helps

Same issue here. on mac 11.6.2 (unknown Kap version, the about screen doesn't open up but I believe it should be the latest.)

@ron23 Try to open the about screen while having settings open. Then it pops up like expected.

Perhaps it could be helpful for somebody.
There was this issue with Kap 3.5.0 and above.
Environment for testing: Big Sur 11.6.2 (CPU Intel).
As a workaround, the success solution is migration on v3.4.2 version of Kap. But before install, we need to completely remove previous version of Kap and all files related to this app. In this case would be helpful to use free app like AppCleaner (or other). Below is image about how it was look for tested environment above.
IMPORTANT: this view and list of files could be different on your side; use AppCleaner app with caution - only you are responsible for which files to remove.

BTW, a restart fixes this

BTW, a restart fixes this

Not necessarily. I would have to reboot my intel-based Mac to get it working again. It works a single time before I experience the error and have to reboot again. Downgrading to v3.4.2 seems to have solved my issue for now.

@BuffMcBigHuge Yup it broke again right after I posted the comment :(

The following steps solved it for me!

AppCleaner -> Re-install Kap -> Reboot Mac(Intel)

The following steps solved it for me!

AppCleaner -> Re-install Kap -> Reboot Mac(Intel)

From my experience and @BuffMcBigHuge 's, reboots only fixes it for 1 launch


HTTP 503 when accessing radiobrowser api

When accessing radiobrowser api, the application stops with an HTTP 503 error.
Analysis: The endpoint that is used by the application is broken and it is not yet using the auto discovery of endpoints provided by radiobrowser4j.

Fix with version 1.6.6: use endpoint auto discovery to not be stuck with a broken API endpoint.


[✨]: Include NIST85 tests - adjusted

I see that this compiler is mostly targeted at "modern standard COBOL", which I guess would be the 2022 standard.
This means - in general - that many COBOL85 code would not be accepted - but it is likely reasonable to either "support enough" to compile and test NIST85 code - or at least do the following:

get GnuCOBOL 3.2 preview or later
build it from source
run make test -j8 COBOL_FLAGS=--save-temps
try to compile the generated ".i" files with otterkit - those have all copybooks included, all comments removed all line-continuation replaced and the code effectively in free format

Either add "enough" COBOL85 like the comment paragraphs (AUTHOR. and friends) or remove them with sed or by hand.
Ignore others like the ones using ALTER.
Aim for the NC module first, increasing your own testsuite with everything that does not compile and also check for the execution results in your testsuite. Compile and add the features of all program one by one.
This will get you many failures on the first modules - but very reasonable ones, and much less with each follow-up.
And in the end this will get you many of the real world usages of COBOL and some special cases, too.

Hey Simon, do you know which license the NIST test suit uses? Maybe we could add those into the compiler depending on which license it has.

I suggest to check out https://www.itl.nist.gov/div897/ctg/cobol_form.htm and possibly ask via mail.

Managed to open the COBOL source file from the NIST test suite, and it's 300k lines of COBOL code. Is it meant to be that big?
Also there's an empty repo on this GitHub org called Otterly Testing, it's meant for a future COBOL unit test framework. Maybe we could start implementing that and add compiler tests for each implemented feature, including the stuff from the NIST test suite?
Also, I wasn't able to find the license file for the NIST test suite. That makes me worried about copyright issues.

Is it meant to be that big?

Yes, but these are multiple sources. The easiest way to unpack those is to let the GnuCOBOL build system do that once.

That makes me worried about copyright issues.

Asking the contact specified at that page seems most reasonable, explain what you want to do and ask under what license you can directly copy and redistribute it, then go on from there in a follow-up mail.

Well, I wasn't able to send the email apparently. It doesn't exist anymore? That's weird.

@GitMensch We might have to make a new one for COBOL 2022.

Well, I wasn't able to send the email apparently. It doesn't exist anymore? That's weird.

The wrong address is a webmaster issue - so send a note to<EMAIL_ADDRESS>pointing out that erroneous reference and ask it to be replaced by the right person to ask on the suite.

We might have to make a new one for COBOL 2022.

That would be really nice. Fair warning: the person that created the NIST85 was also working on all of the newer standards and said something like "that could be done, but would take several weeks of complete working days".
If you go for it, please ensure this suite can be run on a gnu system that runs GnuCOBOL, too. ;-)
You could - of course - take the GnuCOBOL testsuite and copy from there - as long as the license matches (testsuite GPL3+) and you leave the copyright in - have fun.
The "run" tests don't check for compiler messages (other than expecting none) and only in very rare cases have a GnuCOBOL specific result. If you filter those that don't match the COBOL standard, than you'd have a very good base.

That would be really nice. Fair warning: the person that created the NIST85 was also working on all of the newer standards and said something like "that could be done, but would take several weeks of complete working days".

Well, Otterkit will be a long-term thing, I'm not planning to ever abandon it, so we'll have a ton of time to work on a new test suite.
We could integrate that into the Otterly Testing unit test framework. But instead of calling only the Otterkit compiler, it could ask for any compiler and it's command line "build and run" options and test the standard output against a set of pre-written COBOL tests.
C# has a method for that, allows to call a program and redirect it's standard output into a variable. That means that the Otterly Testing framework could also work with GnuCOBOL, and probably any compiler that has a "build and run" command. The output redirect method is used internally in the Otterkit compiler to call the dotnet compiler and display its output together with Otterkit's output.

If you go for it, please ensure this suite can be run on a gnu system that runs GnuCOBOL, too. ;-)

We could work on it together if you'd like. Everyone would benefit from a general COBOL testing suite and unit test framework.

@GitMensch let me know what you think, and if you'd like yo work on this as well.

I guess one can't run C# on some old linux distros; this would therefore make the test suite less useful.
"autoconf generated testsuites work everywhere a shell exists".
Going for a full COBOL 2022 testsuite would likely mean to check each rule (first compile, then later result). to get an idea what this means have a look at https://sourceforge.net/p/gnucobol/code/HEAD/tree//branches/gnucobol-3.x/tests/testsuite.src/syn_redefines.at.
To directly support multiple COBOL software one would have to either drop the check of the message, or would make this a list of valid outputs.
as noted: you are invited to use the GnuCOBOL testsuite as basis - and of course also to send PRs to improve it.
This would be also useful for later testing of otter ;-)
For now I'd help on the GnuCOBOL side and also with inputs for a new suite where missing, I'm out of time for quite a while to create a new testsuite.

I guess one can't run C# on some old linux distros; this would therefore make the test suite less useful.

We might be able to test that, C# also has a nativeAOT compilation mode that compiles C# ahead of time to native machine code with LLVM. This means that technically it would be similar to compiling C to native code with Clang. Only way to find out if it works with older distros would be to test the compiled binary.

as noted: you are invited to use the GnuCOBOL testsuite as basis - and of course also to send PRs to improve it.

We can't use GnuCOBOL's test suite though, due to license differences. It kinda goes one way, Otterkit uses the Apache 2.0 license which as far as I know should be compatible with GnuCOBOL's GPL license if you ever decided to use our test suite, BUT we can't use any of GnuCOBOL's test suite code without also having to change our license from Apache 2.0 to GPL, which is something that I can't do.
So the only option would be to write a new Apache 2.0 licensed COBOL 2022 test suite, that way not only will it be compatible with Otterkit and GnuCOBOL, but also any proprietary compiler that might decide to use it as well.

@GitMensch I know that you're busy working on GnuCOBOL and that you'd like me to use the tests there, but if we're going to make a new COBOL 2022 test suite to replace the old NIST85 one then we can't restrict it to GPL only, we need one that can be used freely no matter which license the compiler uses. The Apache license helps with that.

I'm quite sure the license view is not correct here. Anyone can test with a GPL-licensed test suite anything - but it can only be passed on with passing the possibly adjusted test source.
the test suite is not linked into anything so if we create a COBOL 2022 testsuite under GPL and MicroFocus or IBM wants to use those they are free to do so; the also would be able to extend it, only if they pass the testsuite on they have to pass the sources for the testsuite, too.

if we create a COBOL 2022 testsuite under GPL and MicroFocus or IBM wants to use those they are free to do so; the also would be able to extend it, only if they pass the testsuite on they have to pass the sources for the testsuite, too.

Yes and that's kind of an issue as well. GnuCOBOL would be able to use it internally to test the compiler, but Otterkit and others won't.
If I understand how the GPL license works, if I add a GPL-licensed test suite into the Otterkit repo and make a command-line option for it (so the compiler would directly call GPL code, similar to how Otterkit calls Libotterkit internally) then we would have to GPL the compiler.

@GitMensch  But the opposite is not true, GnuCOBOL won't have to change to Apache 2.0 if you decide to statically link with the test suite

If we have that portable as scripts then no linking is necessary at all.
As long as we have a test runner binary, then there's again no need to link anything, because the compiler and result will be called via system.

If we have that portable as scripts then no linking is necessary at all.

Well, I was thinking something a little more than just COBOL scripts, the Otterly Testing thing was meant to be a COBOL 2022 test suite and unit test framework.
Some COBOL syntax is implementor-defined, even if strictly following the standard. Like the device names for example. The scripts (or the test itself inside of the testing framework) needs to be slightly changed depending on which compiler you're testing it, it's not possible to correctly test device names with just a portable COBOL script file like the NIST test suite.
I'm sure that if the NIST test suite uses any implementor-defined features then it won't be able to correctly run on compilers that define it differently. Some of this might be inevitable, but things like device names could be changed with a config file and replaced by the testing framework before passing it to a compiler.

Let's put it that way: I'm keen to see some starting and would adjust in detail / COBOL questions, as well as testing the test suite with GnuCOBOL :-)

Hey @GitMensch I couldn't find anything about this on the standard. How does COBOL determine the entry point of the program? Meaning, how does it choose the "main" program or class that should be executed first?
Does it just choose the first program that is defined in the source file?

so the first (not prototype) program (functions are only called) are executed first

Alright so, it should be safe to let the user specify a start file and then the first program there is the entry point. Other files would then be included and compiled when the compiler encounters a call to a program from another file (libraries should include everything though).

Specified extra ENTRY points are an extension since COBOL 2002 - because they aren't included there - as we just have seen.

I had an alternative idea to allow users to specify a different entry point. We could provide an entry point "syntax" with the build command. Like this: entry.cob#ENTRY-PROGRAM. That way we can avoid adding extra non-standand extensions directly into the language.

@GitMensch Working on the preprocessor right now, the most recent commit has the code for the >>SOURCE FORMAT directive. Reading this part of the standard made me realize that it should also be possible to add a new directive to specify the entry point.
The standard allows for implementor defined directives with >>IMP, so an >>IMP ENTRY-POINT directive should conform to the standard just fine.

The NIST sub system was written at the behest of U.S. Navy along with other tools for the testing of Cobol compilers almost all (if not all) of the other tools were dropped as technology moved onwards, which included a flowcharter creator that read a Cobol source file it was a right pain to read and could use up a lot of continuous stationary - as in a box worth or more.
Any subsequent updates to NIST has to be within the original copyright and was the equivalent of O/S.
Therefore it is free to use for all developers of compiler and ancillary tools.
Yes, I was a holder of the complete toolset which was supplied on tape starting from the mid/late 60's (cannot remember the exact date) onwards.

The test suite is made public available on https://www.itl.nist.gov/div897/ctg/cobol_form.htm
When strictly following what it contains it is "free for use, but not for distribution".
I did ask NIST once about the copyright and also the option to distribute it, the response was:

The COBOL suite is actually owned by the NCC.  Please contact them at
http://www.ncc.co.uk/

But this website of the National Computing Centre (NCC) [an UK organization] is down, so one should likely ask the NCC Group group.
Could you try to do that (the most important thing would be to ask for the person responsible for the NIST85 testsuite)?

Hey @GitMensch, I just sent them an email. I'll let you know what they said as soon as I receive an email back from them.

Any updates concerning the distribution possibility of an adjusted version?
What about using it locally (as it is done with GnuCOBOL) - at least checking some of the test groups possibly with an additional preprocessor that handles "obscure" things like line continuation?

Any updates concerning the distribution possibility of an adjusted version?

I haven't received any replies from them yet, which makes me a bit worried about modifying and redistributing the test suite.
We don't know who actually owns the copyright right now (and can't contact them), and it doesn't have a license attached to it. So in the future if the copyright holder shows up and decides that they want to enforce the copyright in a proprietary way, we'd probably be in a lot of legal trouble.
Legally speaking we can't really do anything with the test suite (other than run it) without a license that explicitly gives us the rights to modify and redistribute.

Legally speaking we can't really do anything with the test suite (other than run it locally) without a license that explicitly gives us the rights to modify and redistribute.

Sure, that's the current state. So... What about running it locally (or at least try to handle the test source that you get when using make -C tests/cobol85 modules in GnuCOBOL)?


Adding CORS configuration while using EXT Auth service does not resolve CORS issue

I'm running 2 Kubernetes clusters with ambassador edge stack. One cluster does not use any Auth Service so setting CORS configuration by following the instructions here: https://www.getambassador.io/docs/latest/topics/using/cors/ resolved the CORS issue.
But in the cluster where I have external auth enabled using the same configuration does not seem to work there. My external Auth code is CORS enabled and works fine when tested separately but when the request is passed through the gateway I still get the CORS issue. I'm attaching my YAML configurations and other details below, Please suggest a way through this.
Ambassador Edge Stzack version: 1.4.3
Auth service config
---
apiVersion: getambassador.io/v2
kind: AuthService
metadata:
  name: auth
spec:
  auth_service: "authentication-svc:80" # required
  proto: http
  path_prefix: "/auth"                 # optional; default is "http"
  timeout_ms: 5000                  # optional; default is 5000
  #allow_request_body: true         # deprecated; use include_body instead
  status_on_error:                  # optional
    code: 503                         # optional; default is 403
  failure_mode_allow: false         # optional; default is false
  # the following are used only if `proto: http`; they are ignored if `proto: grpc`
  allowed_request_headers:         # optional; default is []
  - "*"

Auth Mapping
---
apiVersion: getambassador.io/v2
kind:  Mapping
metadata:
  name:  authmapping
spec:
  prefix: /auth/
  rewrite: /auth/
  service: authentication
  cors:
    origins: "*"
    methods: POST, GET , OPTIONS
    headers: "*"
    credentials: true
    exposed_headers: "*"
  timeout_ms: 30000
  idle_timeout_ms: 500000
  connect_timeout_ms: 30000
---

I have found the fix for the CORS issue. Basically, when you have header-based routing and CORS together in the mapping for some reasons they don't go together and it throws CORS issue. The small workaround has 2 separate mapping one for CORS and other with a header for the same service (i.e 2 mappings for each service) will resolve this issue. Please check this thread for example -> https://github.com/datawire/ambassador/issues/574


Fix double free on Crystal::Loader#close_all

Crystal::Loader#finalize calls #close_all, but the FFI and loader specs call the latter manually, which means that upon a GC cycle all the dynamic library handles are closed once again. This PR prevents this by clearing the list of handles once they are closed.
Resolves #11561. I have also confirmed that #11343 with this patch will turn the LLVM 13 CI green. I managed to reproduce this locally with just:
$ make clean crystal
$ bin/crystal build -o specs spec/compiler/ffi/ffi_spec.cr spec/compiler/loader/unix_spec.cr spec/compiler/semantic/abstract_def_spec.cr
$ ./specs
#Using compiled compiler at .build/crystal
#........................Invalid memory access (signal 11) at address 0x8000
#[0x558b4b517f76] *Exception::CallStack::print_backtrace:Nil +118 in ./specs
#[0x558b4b4f4686] ~procProc(Int32, Pointer(LibC::SiginfoT), Pointer(Void), Nil) +310 in ./specs
#[0x7f84a015e200] ?? +140207598199296 in /lib/x86_64-linux-gnu/libpthread.so.0
#[0x7f84a68daee6] ?? +140207706713830 in /lib64/ld-linux-x86-64.so.2
#[0x7f84a68cdae1] _dl_exception_create +49 in /lib64/ld-linux-x86-64.so.2
#[0x7f84a002f894] _dl_signal_error +52 in /lib/x86_64-linux-gnu/libc.so.6
#[0x7f84a68ccd71] ?? +140207706656113 in /lib64/ld-linux-x86-64.so.2
#[0x7f84a002f940] _dl_catch_exception +128 in /lib/x86_64-linux-gnu/libc.so.6
#[0x7f84a002f9ff] _dl_catch_error +47 in /lib/x86_64-linux-gnu/libc.so.6
#[0x7f84a00eda59] ?? +140207597738585 in /lib/x86_64-linux-gnu/libdl.so.2
#[0x7f84a00ed364] dlclose +36 in /lib/x86_64-linux-gnu/libdl.so.2
#[0x558b4c764742] *Crystal::Loader#close_all:Nil +82 in ./specs
#[0x558b4c7646e6] *Crystal::Loader#finalize:Nil +6 in ./specs
#[0x558b4b4f7606] ~proc15Proc(Pointer(Void), Pointer(Void), Nil) +6 in ./specs
#[0x558b4c7868ae] GC_invoke_finalizers +158 in ./specs
#[0x558b4c7869fe] GC_notify_or_invoke_finalizers +174 in ./specs
#[0x558b4c787e41] GC_generic_malloc +33 in ./specs
#[0x558b4c7880d1] GC_malloc_kind_global +225 in ./specs
#[0x558b4b5cc016] *GC::malloc<UInt64>:Pointer(Void) +6 in ./specs
#[0x558b4b4f4966] ~procProc(UInt64, Pointer(Void)) +6 in ./specs
#[0x7f84a02fcb6d] ?? +140207599897453 in /lib/x86_64-linux-gnu/libpcre.so.3
#[0x7f84a0302962] pcre_study +738 in /lib/x86_64-linux-gnu/libpcre.so.3
#[0x558b4b693dae] *Regex#initialize<String, Regex::Options>:Int32 +302 in ./specs
#[0x558b4b693c6c] *Regex::new<String, Regex::Options>:Regex +92 in ./specs
#[0x558b4b4ecd9f] ~$Regex:2:init +15 in ./specs
#[0x558b4c772a77] *Crystal::OnceState#once<Pointer(Bool), Pointer(Void)>:(Pointer(Bool) | Nil) +183 in ./specs
#[0x558b4b4d3eb5] __crystal_once +37 in ./specs
#[0x558b4b4ecd7e] ~$Regex:2:read +30 in ./specs
#[0x558b4c2aa7fa] *LLVM::default_target_triple:String +106 in ./specs
#[0x558b4c2aa43a] *Crystal::Config::host_target:Crystal::Codegen::Target +42 in ./specs
#[0x558b4b70fb77] *Crystal::Program::new:Crystal::Program +423 in ./specs
#[0x558b4c7725b9] */home/quinton/crystal/crystal/spec/spec_helper.cr::new_program:Crystal::Program +9 in ./specs
#Segmentation fault

However it seems to happen even on earlier LLVM versions; I tried 9 and 11, and both of them produced the same error. I believe calling dlclose more than dlopen on the same handle is undefined behaviour and it is sheer coincidence the other CI jobs didn't break. The following will show that a double free has indeed occurred:
class Crystal::Loader
  def close_all : Nil
    @handles.each do |handle|
      unless LibC.dlclose(handle) == 0
        STDERR.puts String.new(LibC.dlerror)
      end
    end
  end
end

The same spec binary above will print shared object not open a few times. The count varies between runs of the binary for some reason.

A more robust solution would be maintaining our own reference counts for each successful dlopen, to ensure the handles are correctly closed even if they were opened multiple times.

Also as a rule of thumb, if a class defines a finalize method and another public method that ends up doing the same thing, you should use a "closed" flag to prevent double finalize.


Removed dead code from test

Description
Removed dead code from test
Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.04%. Comparing base (3371fd2) to head (c6389e9).
Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1154      +/-   ##
==========================================
- Coverage   95.48%   93.04%   -2.44%
==========================================
  Files          56       56
  Lines        2390     2388       -2
==========================================
- Hits         2282     2222      -60
- Misses        108      166      +58

see 5 files with indirect coverage changes

/retest

/lgtm

/approve

/override "Red Hat Konflux / lightspeed-service-on-pull-request"


dialogue??

Describe your problem here.
It's a simple problem, I can't figure out how to get dialogue working in custom weeks. If there's an in-depth tutorial on how to set it up than that would be helpful. (also the "script_dialogue.lua" download link is down for some reason sooo)
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Nope.

If you want to make default dialogues go to main menu, press "7" and choose dialogue editor.
here's a tutorial if you needs it https://www.youtube.com/watch?v=6zKIB1Ov66M


TestCafe's proper fixture name in output file #1978

better to run `npm run lint-fix' to cover all lints.

@orihomie please resolve the conflicts.

Outdated


[Feature]: Allow code transformations to work without parsing source

🚀 Feature Proposal
Currently, the process and processAsync options for a code transformation receive both the source text and file name necessary to run the transform. This presumably requires Jest to load the entire file prior to running the transform.
Ideally, the transformation module should be able to supply a method that does not receive the source text and can run with only the filename. If this method is provided and returns a truthy value, it should short-circuit any attempt to load the source text.
Motivation
It is fairly common to import non-JavaScript assets such as image directly into JavaScript files. When done in conjunction with a bundler like Webpack, these imports can be transformed into source paths that can be used in JS.
Since Jest generally doesn't interact directly with a tool like Webpack, the recommendation is to write a custom transform that takes the asset and returns a JS file, like this example from the bottom of https://jestjs.io/docs/code-transformation:
const path = require('path');

module.exports = {
  process(sourceText, sourcePath, options) {
    return {
      code: `module.exports = ${JSON.stringify(path.basename(sourcePath))};`,
    };
  },
};

The problem is that certain assets (e.g. videos) can be quite large. Loading the entire contents of this large file as sourceText can eat up quite a bit of memory and is, in many cases, unnecessary to generate the transformed module.
A related use case may also be a scenario where the import references a file that does not actually exist on the local file system or can't be easily loaded for whatever reason (e.g. maybe large assets aren't downloaded to the developer's machine when cloning the repo and are only available over the network).
Example
The above asset transform with the file name only option might look like this:
const path = require('path');

module.exports = {
  processWithoutSource(sourcePath, options) {
    return {
      code: `module.exports = ${JSON.stringify(path.basename(sourcePath))};`,
    };
  },
};

Pitch
The transformation API is already part of the Jest core platform. This would merely extend it to better handle use cases where we want to transform a filepath without parsing the file.

For anyone stumbling on this, one workaround we're trying that seems to be handling things well is writing a custom resolver that points requests for large assets to an empty stub file. The file still gets loaded and transformed, but since it's empty, we don't see the same perf hit.

Still applicable

Still applicable.

Seems reasonable to me, but I'm not sure how easy such an optimization is to fit into the current way the transformer is called. With no promise of it landing, is this something you can put together a PoC for? No need to add any tests - happy to take a look if and when you've got something working before deciding if we wanna do this or not.


The images are shown broken

Laravel Version: 5.4.*
Voyager Version: 0.11.9
PHP Version:7
Database Driver & Version:

Description:
The images are shown broken
Steps To Reproduce:
After of te instalation with dummy

@ztvMark make sure APP_URL in your .env is the same with the url you use right now.

Yes work
Laravel development server started: http://<IP_ADDRESS>:8000
.env
APP_URL=http://<IP_ADDRESS>:8000

@ztvMark, are you saying that this is now working correctly for you?  If so, please close the issue.


fix bug with NA values in ska.distances.tsv and add known user error for divergent samples

There are cases where NA values will appear in the ska.distances.tsv file for samples with no overlapping kmers. We were filling na values with zeroes at a later step in the ComputeClusters script, but this gives the false appearance that these samples are extremely similar. This update applies fillna = 1 earlier in the parsing of the ska.distances.tsv file so that the samples with NA values are maximally divergent in the resulting heatmap.
Additionally, cases where NA values appear in the ska.distances.tsv file may result in the case where there are no variants from which to construct the tree. This causes an error due to invalid inputs to iqtree (i.e. a malformed .fasta file). For example:
>seq1

>seq2

>seq3

This PR also adds functionality to catch such errors under the class of TooDivergentError.
This was tested on a sample set that generated NA values in the ska.distances.tsv file.

@morsecodist fasta filetype validation could improve our ability to transmit debuggable errors to the dev team (wouldn't make a difference from a user-interpretation side), but if you think it would help with maintainability then we should definitely do that. Do you think that should be wrapped into this PR?


android phone keyboard covered ion-datetime-picker

I use ion-datetime-picker  in my project. It works very well.
However, during testing I find ion-datetime-picker on android phone will be covered by android keyboard.
I try to google but didn't find any good solution.
no sure how to fix or get around or config.

Seems like the whole app is being covered by the keyboard but it can be noticed in picker only. You need to test with the particular phone, no other fix exists.
This is out of scope of this plugin.

Hi Kate
I find a solution to get around it. it is simple but tricky.

.platform-android.keyboard-open .ion-datetime-picker-popup .popup {
position:inherit;
top:10px;
left:50%;
margin-left:-125px;
}
now once keyboard is pop up whole dialog will move up to top:10px.
This is the best way to get around it.
Regards

This is ionic long-term bugs causing this issue. I also reply to ionic bugs in github.

This was my solution:
body.keyboard-open .ion-datetime-picker-popup {
    align-items: flex-start;
    padding-top: 10px;
}


Fix fusing of p2p barrier tasks

[ ] Closes #xxxx
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

see https://github.com/dask/distributed/pull/8944

I've only linked to the distributed PR in the 3.12 build, so the others will have one test failure

I haven't checked the CI failures


Better handling of missing stereochemsitry

Description
Sometimes a new chiral center can form. This PR addresses this for combinatorial fragmentation by:

Save SMILES that have new chiral center
Generate all enantiomers around the new chiral center for combinatorial fragmentation.

Status

[x] Ready to go

Codecov Report

Merging #38 into master will increase coverage by 0.67%.
The diff coverage is 37.68%.


Fixes #1983 - Upgraded dependencies, added CycloneDX

Test failure due to breaking change in Mantine <MultiSelect> component in 6.0.10.  Down arrow does not go to "+Create xyz" menu option.
It looks like there are a handful of changes to <MultiSelect> in both 6.0.9 and 6.0.10, so I'm going to revert to 6.0.8.
https://github.com/mantinedev/mantine/issues?q=is%3Aissue+is%3Aopen+MultiSelect

Unfortunate growth in package-lock.json... No single culprit.  cyclonedx only added about ~1k lines.  Most of the growth is indirectly from @aws-sdk, @storybook, and workbox 😢

Coverage: 94.267%. Remained the same when pulling 5bb0f67cc4d639d83905ccf6cc7a154fb5ff0301 on cody-cyclonedx-sbom into 0221ef064905c073ac6ec113a581dd863e06021e on main.


Dispatcher warning for target-keys=tracing,cpu

https://github.com/apache/incubator-tvm/blob/64766c2cb1cd3ce41ee91a54909882036fffd412/python/tvm/autotvm/task/dispatcher.py#L419
Currently it seems that the warning will always print, even after tuning (e.g., for x86 CPU) when the key is "tracing,cpu". Is this the desired behavior or can the warning be suppressed here?

Ideally we would like to supress the warning and only show once per error kind


[3.1.0] Introduce BorshStorageKey

3.1.0

Introduce trait IntoStorageKey and updating all persistent collections to take it instead of Vec<u8>.
It's a non-breaking change.
Introduce trait BorshStorageKey. It's useful to create enums for unique storage key. Example:

#[derive(BorshSerialize)]
enum StorageKey {
    Records,
    UniqueValues,
}

// Implement `BorshStorageKey`, so `StorageKey` gets `IntoStorageKey`
// trait implementation based on `BorshSerialize`.
impl BorshStorageKey for StorageKey {}

#[near_bindgen]
#[derive(BorshDeserialize, BorshSerialize, PanicOnDefault)]
pub struct StatusMessage {
    pub records: LookupMap<String, String>,
    pub unique_values: LookupSet<String>,
}

#[near_bindgen]
impl StatusMessage {
    #[init]
    pub fn new() -> Self {
        Self {
            records: LookupMap::new(StorageKey::Records),
            unique_values: LookupSet::new(StorageKey::UniqueValues),
        }
    }
}

#[derive(BorshSerialize)]
enum StorageKey {
    Records,
    UniqueValues,
}

// Implement `BorshStorageKey`, so `StorageKey` gets `IntoStorageKey`
// trait implementation based on `BorshSerialize`.
impl BorshStorageKey for StorageKey {}

This feels sort of like two lines of boilerplate. How much work would it require to make the macro StorageKey-specific? Something like this:
#[derive(BorshStorageKey)]
enum StorageKey {
    Records,
    UniqueValues,
}

@evgenykuzyakov I love it! :+1:
I agree with Chad about the boilerplate, though I am unsure if the derive macro worth it.
Another point, the example is not very compelling; I had to read it twice to understand what exactly is proposed here, and that is for a person who has a prior background with near-sdk-rs and Rust, so I think it is worth exploring the space for a better example.

Another point, the example is not very compelling; I had to read it twice to understand what exactly is proposed here, and that is for a person who has a prior background with near-sdk-rs and Rust, so I think it is worth exploring the space for a better example.

It's explained in the https://github.com/near/near-sdk-rs/pull/178 how to use it more details, but I can provide more context.

This feels sort of like two lines of boilerplate. How much work would it require to make the macro StorageKey-specific?

Macro derives requires to introduce a new macro near-sdk-macro, but looking at our zero boilerplate goal, it maybe worth it :)

Actually, making it with #[derive] will still require BorshSerialize, which is not looking nice:
#[derive(BorshStorageKey, BorshSerialize)]
enum StorageKey {
    Records,
    UniqueValues,
}

It's also possible to make it with proc_macro_attribute, e.g.:
#[storage_key]
enum StorageKey {
    Records,
    UniqueValues,
}

But then the shortest one is probably a macro:
storage_key! {
    Records,
    UniqueValues,
}

But maybe the macro will not be autocompleted nicely.

#[derive(BorshSerialize, BorshStorageKey)]

It looks perfectly fine to me, and the least magical. storage_key! macro looks short, but it is hard to reason about it.

For now, I've decided to go with storage_key! { ... }. It does auto-complete for me through macro-extention, so this is not a concern anymore. So long as we can explain how this works, it should be easy to use.

I actually prefer #[derive(BorshSerialize, BorshStorageKey)] or #[storage_key] to the macro. Feels surprising to have a StorageKey variable show up "out of nowhere" with the macro version.

Ok, let's switch to #[derive(BorshSerialize, BorshStorageKey)]


Add Hakuneko-Stable

Hakuneko is a open source comic reader
They have a deb available from their website.
https://github.com/manga-download/hakuneko/releases/download/v6.1.7/hakuneko-desktop_6.1.7_linux_amd64.deb

Sorry, we are only accepting software that is actively maintained/released. Please see:

Add guidelines for what packages are acceptable for inclusion

@flexiondotorg this one actively release https://github.com/wimpysworld/deb-get/issues/68


Add support for opt-in reporting via manual SDK initialization.

Resolves #132.
Test/validation app project: https://github.com/dpa99c/cordova-fabric-plugin-test

Is this repo still being maintained?


dependency constraints

Its possible to install this with expressive 0.x, but it requires zendframework/zend-expressive-helpers 1.1, which uses attachRouteResultObserver which is available only on master.

This is a temporary situation, as a stable version of zend-expressive has not yet been released. I'm preparing RC3 currently, which should resolve the situation.

@weierophinney But even with the rc tag, if you don't add a dependency constraint to 1.x to zendviewrenderer it will still allow us to install expressive 0.x.

@fabiocarneiro Yes, you can install this package, the helpers, and the router without Expressive.
The real question is: what real-world scenario do you envision where somebody would install them alongside Expressive <1.0.0rc3? This feels like a case of "what if?" versus a real concern.


Vue Official extension not working on Microsoft VSCode 1.88

I am simplifying this report as this is my first issue opened.
Yesterday, the Vue Official extension stopped working on my VS Code. It seems like it can't recognize Vue in my project:

Vue Official: v2.0.12
Microsoft VS Code:
Version: 1.88.0
Commit: 5c3e652f63e798a5ac2f31ffd0d863669328dc4c
Date: 2024-04-03T13:25:57.039Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Linux x64 6.5.0-27-generic snap
Initially, I thought the problem could be related to the extension version, but nothing solved it. The only solution was to install another version of VS Code. However, Microsoft VS Code does not allow me to install previous versions on Ubuntu, so I had to install the older version of Codium.
This is the result:

Codium:
Version: 1.87.2
Release: 24072
Commit: f7ed6417a7cfae92f98129384c13b505bb9cfc53
Date: 2024-03-12T18:30:28.994Z
Electron: 27.3.2
ElectronBuildId: undefined
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.5.0-27-generic
This is my report.

Duplicate of https://github.com/vuejs/language-tools/issues/4237


Line reformatting triggers when typing "}

Haxe context.
			while (--i >= 0) {
				var c = body.charAt(i);
				if (c ==
			}

Put the caret after c ==
Type "}

Actual result: The if (c == "} line is unindented one level.
Expected result: No reformatting, since the closing brace is quoted.

Still reproducible


neo-go.service doesn't start if one of the interfaces is down

neo-go.service can be configured to listen several IP interfaces, e.g
ApplicationConfiguration:
  P2P:
    Addresses:
      - "<IP_ADDRESS>:40333"
      - "<IP_ADDRESS>:40333"

If on of the interfaces is down
ifdown data1
and neo-go service is restarted, the service doesn't start
`
systemctl restart neo-go
systemctl status neo-go
● neo-go.service - NeoGo N3-neo-go node
Loaded: loaded (/lib/systemd/system/neo-go.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/neo-go.service.d
└─limits.conf
Active: activating (auto-restart) (Result: exit-code) since Tue 2023-01-17 09:32:21 UTC; 367ms ago
Process: 2411 ExecStart=/usr/bin/neo-go node --mainnet --config-path=/etc/neofs/neo-go (code=exited, status=2)
Main PID: 2411 (code=exited, status=2)
CPU: 826ms
Jan 17 09:32:21 az systemd[1]: neo-go.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 17 09:32:21 az systemd[1]: neo-go.service: Failed with result 'exit-code'.
`

It should print some error before exiting, like
2023-01-17T12:40:27.732+0300    PANIC   TCP listen error        {"error": "listen tcp <IP_ADDRESS>:9191: bind: cannot assign requested address"}
panic: TCP listen error

But what's surprising about this behavior? You don't have an IP that a service wants to bind to, it fails. What else can it do?

neo-go should behave like neofs-storage does - if one of the interfaces is down, the servise starts and leastens to all other interfaces

It's just a neofs-storage bug, it gets an incorrect configuration and pretends to be working, this is just dangerous, you won't notice when it'll break.

I see you're using these different addresses ("<IP_ADDRESS>:40333" - "<IP_ADDRESS>:40333") for redundancy, but normally I'd expect the behavior NeoGo currently has from a service. Unless it can dynamically track interfaces/handle IPs coming and going, which not something services do often.

this issue is that neo-go doesn't start, whereas it works ok if a redundant interface gets down after the service has started and has been running. IMO while starting neo-go should check all redundant interfaces and start if there is at least one active interface.

How can it differentiate redundant and required addresses/interfaces?
Imagine this scenario:

there an SN config with X and Y addresses
Y interface is down
SN starts, binds to X and pretends to be working
Y gets up
X gets down
SN is broken, even though you may think it's OK (it has started with X and Y configured)

Will the operator be happy in this case?

There is Health Check service to alert about inyerfaces issue. When the alert has been received, support service will fix the issue and restart neo-go and other services if nedeed.

Cool, then we don't need to change anything.
BTW, there is another scenario for SN that starts with a typo for address Y, you'll even have Y interface/address working fine, but won't notice the typo in configuration until SN drops out of the network.

wrong configuration is another separate issue.

@ikovalev1 please use triple backtick for code block.

ifdown data1 not just puts the interface "down", but completely deconfigures it, removing all IP addresses.

I used ifdown command  to emulate the physical link disconnection case.

I used ifdown command to emulate the physical link disconnection case.

But that's very much different (as @532910 mentioned above). You should've used ip link set data1 down. That'd be the closest thing you can get to link physically going down. And in this case you won't see any problem at all.

There may be another network issue : Etnernet adapter failure. In this case Linux removes all IP configured on the adapter;s port.

Too rare to care (and still with side-effects from above). We better solve some real problems.


Residence Error

Please HELP!, I have HEXXIT server with PEX and Residence, and when I use /residence (alias: /res) it wrote: "An internal error occured while attempting to perform this command." Running Hexxit server on version: 1.5.2. Thanks

I'm not promising I can solve this problem, since you're using a version of Minecraft which is literally more than 4 years old, but I'll take a shot at it...  (Minecraft 1.5.2 was released May 2nd, 2013.)
Copy the full server startup log— from the moment the server starts until text stops printing to the server console and you see a message similar to "Done!" —to Pastebin and leave the link generated by that site in this thread.
Do the same with your permissions.yml file, which will be located inside the plugins\PermissionsEx folder.  The formatting of this file (for you) is going to be unlike the formatting of any permissions.yml file I used on a server because I didn't start running a server of my own until 1.6.4 and I don't have any files previous to 1.7.2 on this computer, but I may be able to help if there are fundamental errors in your file.
I'll see what I can figure out.

No reply in 7 days.  This issue must be resolved.


Mach calculator correction / Speed Conversions

Hi,
Please correct the mach calculator.
Mach number is not constant.
It varies with local outside temperature.
The correct formala is below.

M: Mach Number
TAS : True Air Speed in knots.
C: Local temperature in celcius
Thanks.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Awesome!!!


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(engines<EMAIL_ADDRESS>chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

.travis.yml

chore(travis): remove node versions 10.15.2
chore(travis): add node versions -10,10.15.3

Codecov Report

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

@@          Coverage Diff          @@
##           master   #512   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          29     29
=====================================
  Hits           29     29

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 b5a8eef...c3b7e06. Read the comment docs.

Coverage remained the same at 97.619% when pulling c3b7e067c1b32e0e39e02ad40f8a0870209e97d5 on template-sync-1 into b5a8eefd95ab17818c59c81003b5ad68ebfb533c on master.


NullReferenceException

When I use this tool I get a NullReferenceException.
My Command Line is:
compile -d2 "..." -stack "..." -cg "..."
The cause seems to be the class ModelCompiler.NodeSetReaderSettings, which has a member NamespaceUris.
As far as I can see, this member is never set and the value is always null, however it is accessed in two places.

Try updating your NuGet packages- that was an issue with the NETStandard library.
If that does not resolve the issue can you provide the exact command line.

I updated but it did not resolve the issue.
This is my command line:
compile -d2 "somepath\opc.ua.fx.cm.nodeset2.xml" -stack "somepath\stack" -cg "somepath\identifiers.csv"
The NRE happens in the following line:
NodestToModelDesign.cs line 709:
NodeId importedNodeId = new NodeId(nodeId.Identifier, m_nsMapping[nodeId.NamespaceIndex]);
m_nsMapping is null, and IMO will always be null, because of that settings class I mentioned above.

Try:
compile -version v105  -d2 ".\Opc.Ua.ModelCompiler\Design.v105\DemoModel.xml" -cg ".\Opc.Ua.ModelCompiler\CSVs\DemoModel.csv" -o2 ".\DemoModel\" -useAllowSubtypes

this command line works, thanks
I will try to figure out what the difference is

The -stack option is only for use when generating the OPC UA service implementation code. It is not for use with normal information models. The help will be updated to indicate that it is for OPC Foundation use only.