Remove extra "rejected" events

Only "message_rejected" will be emitted for rejected definition messages -
no special per-type event will be emitted.
This requires one extra lookup in syncasync to find rejected token pools,
but seems better for overall consistency.

Codecov Report

Merging #482 (23fbf61) into main (83c265f) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #482   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          266       266
  Lines        15154     15147    -7
=========================================
- Hits         15154     15147    -7

Impacted Files
Coverage Δ

pkg/fftypes/event.go
100.00% <ø> (ø)

...ternal/definitions/definition_handler_contracts.go
100.00% <100.00%> (ø)

...ternal/definitions/definition_handler_tokenpool.go
100.00% <100.00%> (ø)

internal/syncasync/sync_async_bridge.go
100.00% <100.00%> (ø)

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 83c265f...23fbf61. Read the comment docs.

Note that this change was prompted after drawing this picture of events:


Scientist contribution

hey can you please add more details? @UpendarRaoGunda

That's a good idea for a personal project. Maybe something you can do with this package but not a part of it. Closing.


Refactor save routine for all template pages / settings

Due seperation (issue #85) we need to refactor how the settings are getting saved and how the css files are minified and written

refactor $template->setTemplateSettings() to save server ressources and loadingtime (update template setting only if it has changed) - this spares a looot of time.

done!


update: percy packages to cli and removed agent

Upgrade percy gatsby plugin
Describe this PR

Changes

What issue does this fix?

Any other relevant information

(Merged main in here so the Percy comparison is more recent - hopefully)

Footer seems to have a problem now, and on a single page some other CSS rendering problems :/

A list of the removed redirects that should keep working:

https://docs-git-update-percy-migrate-prisma.vercel.app/reference/tools-and-interfaces/prisma-schema/prisma-schema-file
https://docs-git-update-percy-migrate-prisma.vercel.app/reference/tools-and-interfaces/prisma-schema
https://docs-git-update-percy-migrate-prisma.vercel.app/reference/tools-and-interfaces/prisma-client/api
https://docs-git-update-percy-migrate-prisma.vercel.app/reference/tools-and-interfaces/prisma-schema/models
https://docs-git-update-percy-migrate-prisma.vercel.app/concepts/components/prisma-data-platform#prisma-data-proxy
https://docs-git-update-percy-migrate-prisma.vercel.app/concepts/overview/what-is-prisma/data-modeling#data-modeling-without-sometext


Stealthcoin wallet do not receive coin transfers

Stealthcoin wallet do not receive coin transfers

After a node update, the coins arrived.


Update to Angular 13

Updated to try and figure out what is causing the following type of compilation warnings to occur:
Warning: C:\Dev\sample-angular-oidc-client-ts\node_modules\oidc-client-ts\dist\esm\oidc-client-ts.js depends on 'crypto-js/enc-base64.js'. CommonJS or AMD dependencies can cause optimization bailouts.


Resolve KubeArmor Installation Issue: Transition to Helm-Based Method in MicroK8s Community Addons

This PR addresses an issue with the previous installation method of KubeArmor within the microk8s-community-addons/addons/kubearmor directory. The prior installation and removal methods were causing unsuccessful KubeArmor installations within MicroK8s.
Details
Issue Resolved: The issue causing unsuccessful KubeArmor installation within MicroK8s due to outdated installation and removal methods has been resolved in this PR.
Updated Approach: The outdated installation and removal methods have been replaced entirely with a Helm-based approach.
Helm Installation: Helm is now responsible for installing the latest version of KubeArmor into MicroK8s.
Comprehensive Testing: The entire installation process, from installing to removing KubeArmor within MicroK8s, has been thoroughly tested to ensure functionality.
File Modifications
Changes have been made to the enable and disable files to accommodate the new Helm-based installation and removal methods for KubeArmor within the specified directory.
This update ensures a more reliable and successful KubeArmor installation process within MicroK8s by adopting Helm as the installation method.

Thank you for this PR @udit-uniyal could you please sign the CLA so we can distribute the addon with MicroK8s? The error we are having is:
Checking the following users on Launchpad:
-<EMAIL_ADDRESS>✕ (has no Launchpad account)

We have to install a specific version of kubearmor  via this addon so we do not break future releases and we offer same user experience within a K8s release.
I assume you are in sync with @gopiak regarding this change.

Hi @ktsakalozos, I have signed the CLA. You can distribute the addon now.

Thank you for this work @udit-uniyal It will be available with the next 1.29 patch release.


[Transaction] Transaction log

Master Issue: PIP31
Motivation
Implemention of PIP31, transaction log
Modifications
Add TransactionMetadataStore implemention by managed ledger
Verifying this change
Add the tests for it
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (yes)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Version support

Summary
This PR adds support for older minecraft versions.
Checklist

[ ] I wrote tests for the code changes.
[ ] I have added the change to CHANGELOG.md.

Aaaand all commands for each version are done (I hope).
There still needs to be some re-organizing in the tests and updating the README to be done.
But everything else is working.

Aaaand all commands for each version are done (I hope).
There still needs to be some re-organizing in the tests and updating the README to be done.
But everything else is working.

There's an issue with the execute command calling parse_command without version.

There's an issue with the execute command calling parse_command without version.


Allow the access token to be configured by appsettings file

Add this section of json into your appsettings.Production.json
"Masterserver": {
    "Endpoint": "[Your Master Server IP]:[Port]",
    "FullAccess": "ChangeThis",
    "CreateAndDestryPermanentServers": "ChangeThis"
  }

This is probably a temporary solution given the TODOs in the MasterserverConfiguration.cs file


D455 External Sync is not supported for color camera

Required Info

Camera Model
D455

Firmware Version
<IP_ADDRESS>

Operating System & Version
Raspberry Pi OS

Kernel Version (Linux Only)
5.4.65-v7l+

Platform
Raspberry Pi

SDK Version
2.38.1

Language
python

Issue Description
When running the the D455 in "genlock" mode the external signal only triggers the depth camera. The color camera runs out of sync and at the full frame rate.
Trying to call: set_option(rs.option.inter_cam_sync_mode, 4) on the color sensor returns the error: object doesn't support option #42
This is the same behavior as the D435. It is expected on the D435 because the color camera is a rolling shutter and separate from the global shutter stereo cameras.
However the color camera on the D455 is a global shutter, and apparently the exact same sensor as the two infrared cameras. In theory this camera should not have the same limitation. Multiple times this whitepaper states this feature is "supported for Intel RealSense Global Shutter cameras":
https://dev.intelrealsense.com/docs/external-synchronization-of-intel-realsense-depth-cameras
Is this something that can be fixed in a software/hardware update? Or is it a hardware limitation where the color sensor on the D455 still separate from the infrared sensors like on the D435?

Hi @sam598   I would speculate that since color is not usually synced to depth in the Extenal Synchronization (Genlock) mode due to the hardware limitation of the color rolling shutter on camera models equipped with Global Shutters that preceded the D455 (e.g D435 and D435i) then D455-specific support for genlocking the color sensor is not currently part of the External Synchronization function.
@dorodnic would be better able to comment on whether D455-specific support for color genlocking is likely to be added in the future.

I can also confirm that this behavior is the same in v2.39.0 of the SDK and firmware <IP_ADDRESS>
In the latest firmware I can get a "genlocked" color image from the left IR sensor, but this is not the ideal color camera.

Sorry to ping you again @dorodnic, but if this is a hardware limitation like with the D435 and a firmware/SDK update is completely out of the question, it would be better to know sooner than later so I can look for an alternate solution.

There is not HW limitation. But we have not enabled it yet.

Thanks @agrunnet that is great news. Looking forward to it!

Guys, looking forward for this feature too!

This would be great to have this feature enabled! @agrunnet

I will add a note to keep this case open for the time being as there is strong interest in the feature mentioned by @agrunnet

Thanks @MartyG-RealSense
@agrunnet I know and greatly appreciate that the RealSense team is moving as fast as they can to add new features every month. Is there any chance this will make it into next month's release?

Adding a reminder for @agrunnet about the question of @sam598 above.   Thanks!

Hi @agrunnet @MartyG-RealSense !
Recently we received D455 cameras and looking for this feature too.
We are working with x86 platform but it does not matter in this case.
Ability to sync RGB sensor was main reason for switch D435 to D455.
Could you provide ETA for this feature ?
Thanks!

Hi @s-t-e-p-a-n-o-v   I do not have that ETA information.  @agrunnet may do.  Thanks for your patience.

Request noted and we are working on it. I do not have a release date yet.

Required Info
Camera Model	D455
Firmware Version	<IP_ADDRESS>
Operating System & Version	Raspberry Pi OS
Kernel Version (Linux Only)	5.4.65-v7l+
Platform	Raspberry Pi
SDK Version	2.38.1
Language	python
Issue Description
When running the the D455 in "genlock" mode the external signal only triggers the depth camera. The color camera runs out of sync and at the full frame rate.
Trying to call: set_option(rs.option.inter_cam_sync_mode, 4) on the color sensor returns the error: object doesn't support option #42
This is the same behavior as the D435. It is expected on the D435 because the color camera is a rolling shutter and separate from the global shutter stereo cameras.
However the color camera on the D455 is a global shutter, and apparently the exact same sensor as the two infrared cameras. In theory this camera should not have the same limitation. Multiple times this whitepaper states this feature is "supported for Intel RealSense Global Shutter cameras":
https://dev.intelrealsense.com/docs/external-synchronization-of-intel-realsense-depth-cameras
Is this something that can be fixed in a software/hardware update? Or is it a hardware limitation where the color sensor on the D455 still separate from the infrared sensors like on the D435?

Hi ！I test the code below with a 75FPS, could you show your result? Thanks very much!
Test Program
// include the librealsense C++ header file
#include <librealsense2/rs.hpp>

#include <opencv2/opencv.hpp>

#include <chrono>

using namespace std;
using namespace cv;

int main()
try
{
    //Contruct a pipeline which abstracts the device
    rs2::pipeline pipe;

    //Create a configuration for configuring the pipeline with a non default profile
    rs2::config cfg;
    //Add desired streams to configuration
    cfg.enable_stream(RS2_STREAM_COLOR, 480, 270, RS2_FORMAT_BGR8, 90);

    //Instruct pipeline to start streaming with the requested configuration
    pipe.start(cfg);

    //Sensor Settings
    auto sensor1 = pipe.get_active_profile().get_device().query_sensors()[1];
    sensor1.set_option(RS2_OPTION_ENABLE_AUTO_EXPOSURE, 1);
    auto sensor2 = pipe.get_active_profile().get_device().query_sensors()[1];
    sensor2.set_option(RS2_OPTION_AUTO_EXPOSURE_PRIORITY, 0);

    // Display in a GUI
    const auto window_name = "Display Video";
    namedWindow(window_name, WINDOW_AUTOSIZE);

    //用于计时
    //show time
    auto start = chrono::system_clock::now();
    int frame = 0;

    while (waitKey(1) < 0 && getWindowProperty(window_name, WND_PROP_AUTOSIZE) >= 0)
    {
        rs2::frameset data = pipe.wait_for_frames(); // Wait for next set of frames from the camera

        //获取彩色图像帧
        rs2::frame color = data.get_color_frame();

        //保存彩色图像
        Mat image(Size(480, 270), CV_8UC3, (void *)color.get_data(), Mat::AUTO_STEP);

        // Update the window with new data
        imshow(window_name, image);

        frame++;
        //one loop end
        auto end = chrono::system_clock::now();
        auto duration = chrono::duration_cast<chrono::microseconds>(end - start);
        double timecost = double(duration.count()) * chrono::microseconds::period::num / chrono::microseconds::period::den;

        cout << frame / timecost << " FPS" << endl;
    }

    return 0;
}
catch (Exception ex)
{
    cout << "Error!!!" << endl;
    cerr << ex.msg << endl;
}

Hi @FrankCreen    Please post your question as a new issue using the New Issue button at the link below and do not post it on multiple D455 cases if the question is unrelated to that case.   Thank you.
https://github.com/IntelRealSense/librealsense/issues/

Really looking forward to when this functionality will work.

As there is not a release date yet for the feature but it is being worked on, I wil close this case in the meantime.

The issue has not been fixed and has no release date, why was it closed?

This case is not linked to the feature's development and so it does not need to be kept open - work on the feature will continue even if this is closed.

This is long awaited feature I am keeping track of. Now when you have closed this issue how should I (and other developers) know  that it least this feature has been selected for development?

You would not automatically receive a notification of a new feature's release.  So the open / close status would not make a difference.  You can check the release notes of new librealsense releases for details of what has been added to it
https://github.com/IntelRealSense/librealsense/wiki/Release-Notes
Closed discussions remain findable by internet search for developers searching for a subject, such as as external sync for color camera.

@MartyG-RealSense as the one who opened the issue, I will happily close it once the release notes say that the feature has been added (if you would please re-open it).
As you have said yourself there is no way for people subscribed to the thread to be notified otherwise.

Hi @sam598   As the creator of this discussion, I will respect your wish for the discussion to be open.  I have added an Enhancement tag to this discussion as a reminder for it to be kept open.  There is no time schedule that I can provide for release of the feature though.

Thanks @MartyG-RealSense I greatly appreciate it. I have purchased 12 of these cameras for a project that is on hold until this fix is released, so I can assure you I am checking for updates regularly.

Hi! I would like to up this thread.
Is there any news about ETA for now ?

Hi @s-t-e-p-a-n-o-v   I do not have that information unfortunately.

Adding a note to keep this case open for a further time period.

Hi @sam598 !
Saw your reply here https://github.com/IntelRealSense/librealsense/issues/8197#issuecomment-763904671
"
Genlock through external sync signal (modes 4-255):
D415 - No Genlock support. All cameras are rolling shutter.
D435 - Genlock support for infrared/depth cameras. No Genlock support for rolling shutter color camera.
D455 - Genlock support for infrared/depth cameras. Genlock support for color cameras are planned but no ETA.
One RealSense camera generates a master signal, others are slaved to it (mode 1 and 2):
D415 - Full support.
D435 - Rolling shutter color camera may not be in sync with Global Shutter infrared cameras (this may have changed).
D455 - Full support.
"
Does it mean that color camera of D455 is in sync when master-slave mode is applied (mode 1 and 2) ?

Hi!
@MartyG-RealSense, is there any updates on this ?

No sorry @s-t-e-p-a-n-o-v   I do not have any information to provide on this subject.

@s-t-e-p-a-n-o-v
In some tests I ran with recent a firmware and SDK version, it appears now that the color and depth cameras of the D455 will be synced in modes 1 and 2 (master and slave). https://github.com/IntelRealSense/librealsense/issues/8958#issuecomment-833060193
Mode 0 'default', Mode 3 'full slave', and Modes 4+ 'genlock' did not run in sync in my tests.
In a previous comment RealSense support said that the D455's color camera would not run in sync in mode 2, so this would seem to contradict that. There has been no official word from the RealSense team about this yet. @MartyG-RealSense since the devices are working differently from what Intel has said, it would be great to get clarification.

@sam598  I do not have any information to share on the subject of D455 RGB multicam sync.

Hi! I would like to ask status again ? Will it be realized at all according recent news ?

Hi @s-t-e-p-a-n-o-v   I am now able to provide information about the future of RealSense, as an 'End of Life' notice has been released by Intel.  Although some RealSense models are being discontinued, the 400 Series stereo depth cameras are continuing.  The official PDF of the End of Life notice explaining the changes is attached below.
PCN118463-00.pdf
Whilst the D455 model and the librealsense SDK are continuing, I still do not have information specifically about D455 RGB multicam sync.

Hi everyone, thanks very much for your patience on this issue.  Intel's investigation of D455 hardware sync for RGB is now closed.  It concluded that when comparing a frameset of depth and RGB in order to calculate the sync, the difference between them is determined by FPS, and although sync on the D455 was slightly more shaky than the D415 camera model, it was consistently steady.

Hi @MartyG-RealSense, I appreciate you following up on this issue.
I have to admit I do not understand your last post. Why would Intel need to "investigate" their own product? Shouldn't they know which features the camera and SDK do and do not support? Because this is a rather long thread please let me try to simplify the initial question:
Is it possible for the D455 to synchronize (capture at the same moment in time) RGB and Depth frames when receiving an external sync signal (modes 2, 3, or 4+)?
Earlier in this thread @agrunnet said that the feature may come in an SDK update:

There is not HW limitation. But we have not enabled it yet.

Has this feature been added? If so what is the correct way of enabling it? Does it happen automatically? Or does the sync option need to be set on the RGB sensor?
Thanks again!

When a feature request is made or an issue that is possibly a bug is identified, that request or possible bug goes through a formal review process.  The outcome of this may be that an action is taken or no further action is taken for various reasons.
In this particular case relating to D455 RGB sync, the review was concluded and closed.  The decision at the outcome of the process is final.  My understanding of the above explanation is that no further action was deemed necessary because the depth-RGB sync was already found by the review process to be performing steadily on D455.

Thanks @MartyG-RealSense. So you are saying that it is now possible to synchronize RGB and Depth frames (capture at the same moment in time) on a D455 when receiving an external sync signal (modes 2, 3, or 4+)?

I do not have access to sync cabling and equipment to test the feature myself.  I recommend performing tests with your own sync setup to see what results you achieve.

I'm sorry but I do not understand why would you @MartyG-RealSense would need to test it yourself if Intel has already "investigated" it. That makes it sound like this feature may not work.
Previously the D455 could not sync RGB and Depth from an external sync signal. Has this feature been added? This should really be a "yes" or "no" answer.

I was making the point that whilst the investigation regarding whether or not to proceed with adding an RGB-depth sync feature for D455 concluded that performance on D455 was steady, I am not able to test RGB-depth sync myself and so suggested that you try it yourself to see what results you get.
Please bear in mind that I am not involved in evaluations of RealSense feature requests or bug reports. I report the outcome of the process.  The purpose of the feature request that was concluded was whether to add RGB-depth sync for D455.  It was concluded that D455 already provided steady RGB-depth sync performance.  You could take that as saying No to creating a new D455 RGB-depth sync feature because D455 RGB-depth sync is already working (and FPS is the primary determining factor in how well it works).

I understand that you are only passing along information. But the information you are forwarding does not seem to answer the issue at hand.
As stated in the title, the issue is whether or not the D455 is capable of RGB-depth sync from an external sync signal. Not just RGB-depth sync on a single D455. It is not clear from your report if the D455 was in sync mode 2 (validated), 3 (placeholder), 4 (experimental), or receiving a sync signal at all.
It is also incorrect to say that FPS is the primary determining factor in whether or not sync works. Two cameras can run at the exact same frame rate, but if those cameras are not capturing the same moment in time each frame, then they are not in sync.
It is not possible to determine sync by just looking at FPS. If that is all that the investigator did, then they did not validate that the RGB and Depth cameras are in sync.
If there is any other information you can provide about the report it would be appreciated. Otherwise it is not clear that this issue has been resolved.

There is nowhere further for this case to go, unfortunately.  The D455 RGB-depth sync feature request is closed and will not be re-opened or recreated, and there is no further information that can be provided.  The only possible outcome remaining is to close this case, even if you did not receive the answer that you wanted.  I do very much understand your frustration.

The D455 RGB-depth sync feature request is closed

It feels like you are choosing these words very specifically. By "D455 RGB-depth sync feature request" does that mean sync sync from an external or multi-camera signal? Because that is what this open GitHub issue is about.

The only possible outcome remaining is to close this case, even if you did not receive the answer that you wanted.

It very well might be the answer to this issue, but there seems to be an unwillingness or inability to clarify.

I regret that you are not satisifed, but there is nothing further that can be said or done in this case.

If you are saying that the feature is working then why would I be unsatisfied? That doesn't make any sense.
I am simply asking for clarification so that this issue can be closed.

Please test RGB-depth sync with your own D455 sync setup.  That will provide the answer about whether it now works for you.

Hi @sam598  Where you able to test RGB-depth sync with your own D455 sync setup to confirm whether it now works for you, please?  Thanks!

Case closed due to no further comments received.


not an issue.

will this get made for legion go handheld?

Use bazzite-deck:39 for now, next build should substantially improve the experience. No extra button support yet.

cool, so things are slowly egtting to work. how to install it?

Use bazzite-deck:39 for now, next build should substantially improve the experience. No extra button support yet.

cool, so things are slowly getting to work. how to install it?

Wait until Tuesday for the Fedora 39 builds to drop and have a smoother experience, but if you want to try it early and test it yourself:

Install Bazzite on it normally then once you reach the desktop, open the terminal and enter:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:39
Keep in mind you should rebase back to :latest after Tuesday because the :39 branch will not be upgraded to 40 when that comes out in 6 months, so to do that enter in the terminal:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:latest

Please refer to the installation guide on how to install Bazzite properly.

Use bazzite-deck:39 for now, next build should substantially improve the experience. No extra button support yet.

cool, so things are slowly getting to work. how to install it?

Wait until Tuesday for the Fedora 39 builds to drop and have a smoother experience, but if you want to try it early and test it yourself:

Install Bazzite on it normally then once you reach the desktop, open the terminal and enter:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:39
Keep in mind you should rebase back to :latest after Tuesday because the :39 branch will not be upgraded to 40 when that comes out in 6 months, so to do that enter in the terminal:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:latest

Please refer to the installation guide on how to install Bazzite properly.

so its comign early. i wait for that one then. awhile im still looking for a distro to run on legion.


How to make VirtualizedScrollPane scroll to the bottom?

I use RichTextFX 0.10.9 and I have the following code:
    InlineCssTextArea textArea = new InlineCssTextArea();
    VirtualizedScrollPane scrollPane = new VirtualizedScrollPane(textArea);
       .....
     But it doesn't work. Please, could anyone tell me how to do it?

Could anyone say if this is a bug or I do something wrong?

Hi there are various ways of accomplishing this, depending on what it is you want to achieve, try:
textArea.requestFollowCaret();

or maybe:
int last = textArea.getParagraphs().size()-1;
textArea.showParagraphAtBottom( last );

and then there's also textArea.showParagraphAtTop( p );

@Jugen Thank you very much. This variant textArea.requestFollowCaret(); works fine.

@Jugen  When I try to compile this code:
int last = textArea.getParagraphs().size() - 1;

I get compilation error:
java.util.List.size() is defined in an inaccessible class or interface

I use JDK 11 and JPMS. Is this problem with my code? Does it work for you?

Using JDK 11 with class path works for me, can't say about modules ?

Could you give me the following output:
System.out.println(textArea.getParagraphs().getClass().getCanonicalName());

@Jugen I just wander what is wrong with this class or one of its interfaces. Maybe I miss some modules in module-info ...

Requested output is: org.reactfx.collection.SuspendableListWrapper
Are you using the fat jar: richtextfx-fat-0.10.9.jar ?

@Jugen No, I don't use richtextfx-fat. I solved the problem with the compilation error by adding requires reactfx; to my module-info. Thank you for your help.


"Material You" dynamic colors

Not sure how well this works for EVMap, I've not seen many 3rd party apps that implement this feature yet.
https://github.com/material-components/material-components-android/blob/master/docs/theming/Color.md#using-dynamic-colors

At least 5 of the apps I use already support it. They mostly change the accent and secondary colours of headers/titles, buttons, toggles, and sometimes icons. I'm neutral about this.
On some apps, it makes apps look more "integrated" with the system. For example, the file manager I use almost looks like Android menus as it now uses the same colours. On others, I think it makes apps lose their "branding", so I'm not sure if all apps will implement this. Companies especially... I doubt PayPal, Amazon, banks, etc, want their app to be pink or something like that.
For EVMap, I wouldn't mind, but I guess you as developer would have to be okay with it losing the green tones. You could still use some of the green colors, but then it might be look like a "frankenstein" app if colors don't mix well. I guess it's one of those features that shouldn't be half implemented.
It could help with readability and consistency across the app, by the way. For example, the bright green (on a white background) used in the titles of the settings menu might not be the best color in terms of contrast/accessibility and using the system default would pick something the user is happy with. It would also fix the different types of green that are used for the different buttons, titles, options, etc. (Something that you may want to consider to improve even if you implement this as not everyone uses the latest Android version.)
There's also a new feature called "themed icons". I think it's part of the same theming/customisation features. I've never used it, but I think it's something worth implementing as otherwise the icon looks out of place with the other apps. This article has some screenshots/info about it: https://www.androidpolice.com/android-13-themed-icons-how-to-activate/


Created a html file, assets folder and css file

Apologies, in my first commit I already created an assets file, it has been pushed to the main. Please pull the latest version so it doesn't clash.


[flutter_tools] Restore base/platform.dart

Description
In https://github.com/flutter/flutter/pull/7642, the tool's wrapper around dart:io Platform was pulled out into a separate package package:platform. That package may soon see some breaking changes which are easiest dealt with in the tool by bringing the wrapper back in where it was under src/base/platform.dart.
In a subsequent PR, I'll update the tool's pubspec.yaml, and run update-packages.
Tests
I added the following tests:
Tests are migrated to the internal wrapper. Added the tests from the package.
Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].

[x] No, no existing tests failed, so this is not a breaking change.

Can we pull in the test file too?

Done.


FACT-1439 Facter detecting only enabled network card

Changing the way facter list NIC on Windows. Get rid of the NetEnabled statement so that every NIC are listed, even the disabled.
modified :         lib/facter/util/ip/windows.rb

CLA signed by all contributors.

Hi, thanks for
The change that added the NetEnabled check was intended to [https://projects.puppetlabs.com/issues/22619](fix a bug), and merged in #537  I think in order to effectively list disabled interfaces, additional logic would have to be added elsewhere to facter to handle the cases that ticket was trying to correct for. @ferventcoder do you have any thoughts here?
Beyond that, facter 2 is essentially in "extended support" at this point. We try not to make changes to it that could negatively impact the users who rely on older versions of software for stability. Can you explain a bit more about what your use case is for having facter include the extra information, so we can determine if it's something that's worth bringing in to the old code?

Sorry, for the delay the summer was very busy.
I'm just relaying this contribution. I think that this is a very specific need, and that this could be helpful for someone else.
However, all the travis builds failed because the spec were not modified accordingly. So I think that we can just put this contribution aside.
Thanks for coming back.

OK. I'm going to go ahead and close this, then.
Thanks for reaching out to us, and please don't hesitate with other contributions in the future.


More fulfillment lib cleanup

Codecov Report
Patch coverage has no change and project coverage change: -0.01 :warning:

Comparison is base (8979c42) 99.96% compared to head (e3904e7) 99.95%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1222      +/-   ##
==========================================
- Coverage   99.96%   99.95%   -0.01%
==========================================
  Files          47       47
  Lines        2653     2415     -238
  Branches      396      354      -42
==========================================
- Hits         2652     2414     -238
  Misses          1        1

Flag
Coverage Δ

foundry
?

production
99.91% <ø> (ø)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 29 files with indirect coverage changes

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


[#2073] fix(server): throws EventRetryException If Exception is encountered during create write handler

What changes were proposed in this pull request?
Throws EventRetryException If Exception is encountered during create write handler.
Why are the changes needed?
Fix: #2073
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI

Should we change the default value of rss.server.hybrid.storage.fallback.strategy.class to RotateStorageManagerFallbackStrategy? @zuston @jerqi @rickyma @smallzhongfeng
https://github.com/apache/incubator-uniffle/blob/57f0f8bbcd530feb6ab1284c2eed0c08b9e2c9ae/server/src/main/java/org/apache/uniffle/server/storage/HybridStorageManager.java#L85-L88

@zuston PTAL

Should we change the default value of rss.server.hybrid.storage.fallback.strategy.class to RotateStorageManagerFallbackStrategy? @zuston @jerqi @rickyma @smallzhongfeng
https://github.com/apache/incubator-uniffle/blob/57f0f8bbcd530feb6ab1284c2eed0c08b9e2c9ae/server/src/main/java/org/apache/uniffle/server/storage/HybridStorageManager.java#L85-L88

I prefer not.


Update KickstartRT SDK

Update KickstartRT SDK to support Win11 on debug build.

I have read the CLA Document and I hereby sign the CLA


#M10. Update Hackathon and Profile model with new fields.

Hackathon:
- org (default: CodeInstitute)
- status (draft/published/deleted; default: draft)
User:

org (default: CodeInstitute)

@auxfuse I'll take this one too. Do we have a proposed list of organisations? Or, will this just be a CharField with a default value of CI?

@stefdworschak @TravelTimN Can this issue be closed please so that we get it off the in progress list 😀🤜


Pin docker to python 3.7

Summary of Changes
Pin docker to python 3.7 - this way we make sure we have the typed-ast wheel available so we do not need gcc which is not available in the -slim image (part of what makes it slimmer ;).
Note: Since our existing docker rreleases are already baked on 3.7 they shouldn't be affected.

Reproduced! Turns out this happened: https://docs.python.org/3/whatsnew/3.8.html
Which also means a fresh pull of python:3 docker images are now 3.8. It looks like with python 3.7 we could rely on .whl files for a number of things including typed-ast which currently has wheels for py3.5 - 3.7, but nothing for 3.8 yet: https://pypi.org/project/typed-ast/#files
I propose we pin our Dockerfiles to 3.7-slim until the dust settles on 3.8 :tornado:. I will post a PR.

Background Slack thread: https://amundsenworkspace.slack.com/archives/CHQERT0D7/p1571242121003300?thread_ts=1571215339.001400&cid=CHQERT0D7
Tests
No automated test changes. Tested manually - To reproduce the original problem if you have an existing python:3-slim image hased on python <= 3.7 you need to docker rmi that first before you will experience the problem.
Documentation
No changes
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes make test

Codecov Report

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

@@           Coverage Diff           @@
##           master      #66   +/-   ##
=======================================
  Coverage   80.65%   80.65%
=======================================
  Files          14       14
  Lines         517      517
  Branches       47       47
=======================================
  Hits          417      417
  Misses         83       83
  Partials       17       17

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 2837975...372c2a8. Read the comment docs.

looks good, do we need to bump the version so that dockerhub get a new image?

No I don’t think so, since our existing docker releases are already baked on 3.7 they shouldn't be affected.

@jornh  : Looks good now. Thx

Thank you for the quick merge @feng-tao  🙂
I put up similar changes for metadata and frontend - linked above.

Also thank you for the feedback @rahulraina7 🎉


MDF scheduling wrappers

One thing that would be nice though is if there was a wrapper class around the PNL specific classes/fields so that all the terms used (trial/timescale/sequence) are MDF's own and can be changed/updated easily on our side without impacting PNL. Also the "innards" of that wrapper class can eventually substituted with a MDF specific implentation (or a standalone schedluer) without too much additional changes...

Thinking a bit more about this I feel this file (modeci_mdf/scheduler.py) is the proper place for the "wrapper" class/fields (i.e. the MDFScheduler) which hides the specifics of PNI in an MDF specific API, and the EvaluableGraph could be extracted out & just use that API...

Originally posted by @pgleeson in https://github.com/ModECI/MDF/issues/60#issuecomment-832594701, https://github.com/ModECI/MDF/pull/60#issuecomment-832893942

The way I see it, there isn't much to wrap. The scheduler is ok with just accepting the ids of MDF nodes, and EvaluableGraph handles the interface between MDF and the scheduler. As for naming of things like "trial", the MDF versions of these terms can be used via monkeypatching in 4745e87. While custom naming for these time scales could be implemented in the future by the scheduler, the meaning of the scales is fixed and critical to the scheduler's function.

Out of date now I believe


Did you try to compare rendertimes?

One of the Blender devs, LazyDodo, wrote to me: "if you render from the UI it'll generally do the color management in glsl which will appear single-threaded, when doing a CLI render, OpenGL is not used, and it'll run multithreaded on the cpu"
First I tried to render a 100 frames of a color strip, using Parallel Render, with just one instance and one part and it seemed to render as fast as the native Blender render(which actually used all 4 cores on my computer), spitting it into 4 instances and 8 parts seemed to render at least 10 sec. longer.
But maybe the speed enhancements are when rendering multiple tracks doing compositing?

Short answer is "no". Especially not with newest Blender versions.
However, my parallel render was meant for very specific use case I had which was also the most common for me: rendering purely VSE project to h264 files. In that case all h264 compression was going done no CPU and that was bottleneck not being multithreaded. Nice perk was being able to render in chunks which meant when things crash I only lost ongoing segments.
If you're using it for rendering 3d scenes there might be no benefit at all.
And with all of that said, I haven't checked what happens on newest (2.83 I think at the time of writing) version. There might have been an enhancements to VSE/compression (built-in ffmpeg?) that would utilise all available cores. I haven't checked it.

I tried the native Blender render compared to Parallel Render and Blender seems to use about 40-50% of all 8 threads of my CPU, and Parallel Render uses 100% of all threads.

I am really glad I found this. Cut down my VSE render time from 27min with Blender to 2 min with 24 thread.


Use FZF_DEFAULT_COMMAND in more places

The CTRL-T and ALT-C bindings were ignoring the FZF_DEFAULT_COMMAND when it was set. This left users wondering why "ignored" files/directories were still showing up in searches with these bindings.

@Keating950 is there something I need to do to get this either merged or rejected?

@Keating950 is there something I need to do to get this either merged or rejected?

Don't know; I'm not a maintainer, it just happens that my PR is the current head commit. I'll tag @junegunn.

I don't think we should do this.

Unfortunately, there is no guarantee that a user configures FZF_DEFAULT_COMMAND to list file paths under the current directory. It can be anything.

export FZF_DEFAULT_COMMAND='cat ~/docs/items.txt'

Even if it is configured to produce a list of file paths, it will not be compatible with ALT-C binding which expects a list of directories excluding files.
The options are clearly documented on the README page

https://github.com/junegunn/fzf#environment-variables

⚠ This variable is not used by shell extensions due to the slight difference in requirements.

https://github.com/junegunn/fzf#key-bindings-for-command-line

Thanks for pointing out where it was hiding in the documentation


Sending/Receiving Complex Data Structures

Required information
Operating system:
Ubuntu 18.04 LTS
Compiler version:
GCC 7.5.0
Iceoryx versioin:
<IP_ADDRESS>
Observed result or behaviour:
I created a structure which is as follows:
struct MyStruct {
std::vector charArray;
};
I am using this in place of "RadarObject" struct in the untyped example
Publisher code:
auto result = untypedPublisher.loan(sizeof(MyStruct));
if (!result.has_error())
{
auto& sample = result.value();
// In the untyped API, the returned sample is a void pointer, therefore the data must be constructed
// in place
auto object = static_cast<MyStruct*>(sample.get());
*object = MyStruct();
object->charArray.push_back('A');
sample.publish();
}
Subscriber code:
if (untypedSubscriber.getSubscriptionState() == iox::SubscribeState::SUBSCRIBED)
{
untypedSubscriber.take()
.and_then([](iox::popo::Sample& sample) {
auto object = static_cast<const MyStruct*>(sample.get());
std::cout << "Got value: " << object->charArray.at(0) << std::endl;
})
.if_empty([] { std::cout << std::endl; })
.or_else( { std::cout << "Error receiving chunk." << std::endl; });
}
else
{
std::cout << "Not subscribed!" << std::endl;
}
When I run my application, publisher crashes.
I have tried something similar with Iceoryx version <IP_ADDRESS>, but I was receiving blanks at the receiver
I mainly want to know whether we can actually transfer complex data types with Iceoryx or we need to follow some workaround?
Expected result or behaviour:
Data transfers successfully

@Indra5196 to implement a zero copy data transfer we us a shared memory approach. This requires that every data structure needs to be stored in there and that they do not use the heap.
An std::vector uses the heap to acquire memory to store the elements in there. This leads to the following problem.

Your application send the data
The receiver receives a pointer to the data in the shared memory (zero copy)
When the receiver dereferences the data it accesses the std::vector which then would like to access his heap memory to read the elements which is stored in the process space of your sender application and this causes a segmentation fault since you as a stranger process are not allowed to access memory of another process. This is only with shared memory possible.

Solution:
Update your structure so that it uses our cxx::vector implementation and you are good to go.
struct MyStruct {
  cxx::vector<char, 1337> charArray;
};

It can be used like a normal vector but it does not use the heap under the hood. This is why you have to provide the maximum cxx::vector capacity at compile time - in this case it is 1337.

@Indra5196 to implement a zero copy data transfer we us a shared memory approach. This requires that every data structure needs to be stored in there and that they do not use the heap.
An std::vector uses the heap to acquire memory to store the elements in there. This leads to the following problem.

Your application send the data
The receiver receives a pointer to the data in the shared memory (zero copy)
When the receiver dereferences the data it accesses the std::vector which then would like to access his heap memory to read the elements which is stored in the process space of your sender application and this causes a segmentation fault since you as a stranger process are not allowed to access memory of another process. This is only with shared memory possible.

Solution:
Update your structure so that it uses our cxx::vector implementation and you are good to go.
struct MyStruct {
  cxx::vector<char, 1337> charArray;
};

It can be used like a normal vector but it does not use the heap under the hood. This is why you have to provide the maximum cxx::vector capacity at compile time - in this case it is 1337.

Thank you very much. That helped a lot!

Thank you very much. That helped a lot!

Added an item in #482 that we need to document the limitations of what can be transmitted via shared memory. Closing this issue and we can continue the wishlist of data types and possible solutions in #594


build with CPU optimization and GPU support are conflict?

bazel build --copt=-march=native -c opt --config=cuda //tensorflow/tools/pip_package:build_pip_package

Can I use both --copt=-march=native and --config=cuda , for now it gives out an error
ERROR: /home/wenjian/tensorflow-1.0.0-alpha/tensorflow/core/BUILD:1200:1: C++ compilation of rule '//tensorflow/core:framework_internal' failed: crosstool_wrapper_driver_is_not_gcc failed: error executing command external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -fPIE -Wall -Wunused-but-set-parameter ... (remaining 123 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
In file included from ./tensorflow/core/framework/numeric_types.h:25:0,
                 from ./tensorflow/core/framework/allocator.h:23,
                 from ./tensorflow/core/framework/tensor.h:21,
                 from ./tensorflow/core/util/sparse/group_iterator.h:21,
                 from tensorflow/core/util/sparse/group_iterator.cc:16:
./third_party/eigen3/unsupported/Eigen/CXX11/FixedPoint:42:52: fatal error: src/Tensor/TensorContractionThreadPool.h: No such file or directory
compilation terminated.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 78.339s, Critical Path: 66.15s

Have the same issue.

Similar thing was fixed 2 days ago in https://github.com/tensorflow/tensorflow/pull/6759, can you check with master?

@yaroslavvb master branch seems solved the problem


[enhancement] Add missing bower.json.

Hey, maintainer(s) of oyvindkinsey/easyXDM!
We at VersionEye are working hard to keep up the quality of the bower's registry.
We just finished our initial analysis of the quality of the Bower.io registry:
7530 - registered packages, 224 of them doesnt exists anymore;
We analysed 7306  existing packages and  1070 of them don't have bower.json on the master branch ( that's where a Bower client pulls a data ).
Sadly, your library oyvindkinsey/easyXDM is one of them.
Can you spare 15 minutes to help us to make Bower better?
Just add a new file bower.json and  change attributes.
{
  "name": "oyvindkinsey/easyXDM",
  "version": "1.0.0",
  "main": "path/to/main.css",
  "description": "please add it",
  "license": "Eclipse",
  "ignore": [
    ".jshintrc",
    "**/*.txt"
  ],
  "dependencies": {
    "<dependency_name>": "<semantic_version>",
    "<dependency_name>": "<Local_folder>",
    "<dependency_name>": "<package>"
  },
  "devDependencies": {
    "<test-framework-name>": "<version>"
  }
}

Read more about bower.json on the official spefication and nodejs semver library has great examples of proper versioning.
NB! Please validate your bower.json with jsonlint before commiting your updates.
Thank you!
Timo,
twitter: @versioneye
email<EMAIL_ADDRESS>VersionEye - no more legacy software!

+1

+1

:+1:

+1


Add senacrs

Added Senac rs.
See website

@xteam-ivoneijr First stage of verification passed, official domain is senacrs.com.br as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@xteam-ivoneijr Pull request merged. Thank you.


Problem when using with package messageformat

Hello, i was having this problem and some others and thought that everything would be fixed with the EJSON update, but still getting a lot of exceptions related to messageformat package (not happening with 0.2.2)
.....
"Exception in template helper: EJSON.parse@http://localhost:3000/packages/ejson.js?71047b64b5196348bdbe5fd5eea9ac97a5a9eb14:384:30
_psGet@http://localhost:3000/packages/u2622_persistent-session.js?0306d57630d05c163aba01e8e718801e18f08f4a:101:13
mf@http://localhost:3000/packages/gadicohen_messageformat.js?83c396c542f25fc81c0cdfc190e63eea66803f1a:1759:1
mfPkg.mfHelper@http://localhost:3000/packages/gadicohen_messageformat.js?83c396c542f25fc81c0cdfc190e63eea66803f1a:2558:9
bindDataContext/<@http://localhost:3000/packages/blaze.js?4e49999979a58da0e2265f7bd3f5910f9901b07b:2786:14
Blaze._wrapCatchingExceptions/<@http://localhost:3000/packages/blaze.js?4e49999979a58da0e2265f7bd3f5910f9901b07b:1607:14
wrapHelper/</<@http://localhost:3000/packages/blaze.js?4e49999979a58da0e2265f7bd3f5910f9901b07b:2834:14
Template._withTemplateInstanceFunc@http://localhost:3000/packages/blaze.js?4e49999979a58da0e2265f7bd3f5910f9901b07b:3382:12
wrapHelper/<@http://localhost:3000/packages/blaze.js?4e49999979a58da0e"[…]
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data"Exception in delivering result of invoking 'mfLoadLangs': EJSON.parse@http://localhost:3000/packages/ejson.js?71047b64b5196348bdbe5fd5eea9ac97a5a9eb14:384:30
_psGet@http://localhost:3000/packages/u2622_persistent-session.js?0306d57630d05c163aba01e8e718801e18f08f4a:101:13
updateSubs@http://localhost:3000/packages/gadicohen_messageformat.js?83c396c542f25fc81c0cdfc190e63eea66803f1a:2715:15
mfPkg.loadLangs/<@http://localhost:3000/packages/gadicohen_messageformat.js?83c396c542f25fc81c0cdfc190e63eea66803f1a:2627:4
Meteor.bindEnvironment/<@http://localhost:3000/packages/meteor.js?e53378596562e8922a6369c955bab1e047fa866b:978:17
._maybeInvokeCallback@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:3860:7
.receiveResult@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:3880:5
._livedata_result@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:4970:7
Connection/onMessage@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:3725:7
._launchConnection/self.socket.onmessage/<@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:2717:11
_.forEach@http://localhost:3000/packages/underscore.js?0a80a8623e1b40b5df5a05582f288ddd586eaa18:156:7
._launchConnection/self.socket.onmessage@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:2716:9
SockJS</REventTarget.prototype.dispatchEvent@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:156:9
SockJS</SockJS.prototype._dispatchMessage@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:1141:5
SockJS</SockJS.prototype._didMessage@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:1199:13
SockJS</SockJS.websocket/that.ws.onmessage@http://localhost:3000/packages/ddp.js?d1840d3ba04c65ffade261f362e26699b7509706:1346:9
"

@tcastelli I can't seem to replicate this at all. It looks like a value is getting saved into Session that is not EJSONable. Perhaps there was a problem with the update from 0.2 to 0.3. If you clear your localStorage does the problem still persist?

Thanks for the hint, I tried to clear my localStorage and the page loaded again, so after looking for a while what was generating those non EJSONable parts i found out that at some point i use a package called planifica:wizard (for aldeed:autoform) that had created those values and were stored with amplify. (I guess i should contact the author to ask for an update, since that data is not compatible anymore with EJSON).

@tcastelli If they were stored in amplify (and not through Session) then you shouldn't be getting the error, as we shouldn't be trying to do EJSON.parse on all of the data in amplify. If that's the case this is definitely a bug on our side. Is that what is happening?

yes seems like the package is using amplify directly. I switched to
forwarder@wizard package to solve the issue,  since that one is using
session instead of amplify
El 20/4/2015 19:09, "Richard Gould"<EMAIL_ADDRESS>escribió:

@tcastelli https://github.com/tcastelli If they were stored in amplify
(and not through Session) then you shouldn't be getting the error, as we
shouldn't be trying to do EJSON.parse on all of the data in amplify. If
that's the case this is definitely a bug on our side. Is that what is
happening?
—
Reply to this email directly or view it on GitHub
https://github.com/okgrow/meteor-persistent-session/issues/24#issuecomment-94511459
.

Ah, yes. If something is set directly using amplify.store but then accessed using Session.get, that would cause this error. This can be fixed by having Session.get only attempt to use EJSON.parse if the key is a known key to persistent-session.
We'll fix this eventually, but I suspect this isn't commonly encountered, so it may be a few weeks. If anyone else encounters this, please :+1: here.

@rgould  - if things are merged, is the issue closable ?

@tcastelli This shouldn't be an issue anymore, but if you encounter it again, please re-open :)


how to setup perl checker to run 'perl -cw' instead of 'perl -c'

Hi, how to setup perl checker to run 'perl -cw' instead of 'perl -c'? I tried let g:syntastic_yaml_yamlxs_exec='perl\ -cw' but it doesn't work.

The perl checker already runs perl -cw.  The yamlxs checker doesn't need, nor supports, running under perl -cw.  So, what checker do you want to run, and what are you actually trying to do?

maybe I misunderstood this page: https://github.com/scrooloose/syntastic/wiki/Perl:---perl but in this page, it mentioned it use perl -c.
What I want is to detect syntax errors using perl -cw. However, when I check a file in which there are some errors by manually running perl -cw, no errors show up in syntastic.

Syntastic first runs perl -c -X, then perl -c -Mwarnings.   This is lame, but the reason is that otherwise warnings could obscure errors.  The side effect however is that warnings are only shown if there are no errors.  Basically this is only intended as a quick guard against syntax errors.  Use the perlcritic checker if you want more useful diagnostics.
Either way, changing g:syntastic_yaml_yamlxs_exec is not going to have any effect on the perl checker.

But it doesn't show up any errors even missing braces. When I run perl -cw manually, it did show errors. Therefore, there is for sure some settings wrong but I cannot figure out.
Syntastic version: 3.6.0-117 (Vim 704, Linux)
Info for filetype: perl
Global mode: active
Filetype perl is active
The current file will be checked automatically
Available checkers: perl perlcritic podchecker
Currently enabled checker: perlcritic

Please post a test file that illustrates the problem.

sure. sample code:
#!/usr/local/bin/perl -w
use strict;
use warnings;

my $good = 1;
$bad = 2; # no my specified as local variable.

while($good < 5
    $good += 1;

test result:
perlcritic test.pl
test.pl source OK

perl -cw test.pl
Scalar found where operator expected at test.pl line 9, near "$good"
        (Missing semicolon on previous line?)
Global symbol "$bad" requires explicit package name at test.pl line 6.
syntax error at test.pl line 9, near "$good "
test.pl had compilation errors.

no errors in syntastic.

As I said: your perl checker is not enabled.  It seems to be working fine here:

How to set this? I tried let g:syntastic_perl_interpreter='perl' but it doesn't work.

Just like any other checker, you also need to add it to g:syntastic_perl_checkers:
let g:syntastic_perl_checkers = ['perl', 'perlcritic']

yeah! after I set let g:syntastic_enable_perl_checker = 1 and let g:syntastic_perl_checkers = ['perl', 'perlcritic'] it works! Thank you your your help!


IE panning

Sometimes I face a problem with panning in internet explorer running from web browser control in C# as it often do panning with only mouse move without pressing mouse down.

It sounds like a bug with the web browser control not raising the mousedown event. Have you tried looking for a reason for that?

I faced this problem also with internet explorer browser as it sometimes not capture mouse up event so it continues panning forever

any help please?

Do you reproduce it on http://openseadragon.github.io as well?

yes but after panning for some time.

What version of IE are you using? I am not able to reproduce it with IE11.

you can reproduce it using web browser control in c# which will use IE8.

Have you tried to force a more recent version of IE as I suggested in #920 ?
Here is the link on how to do that: https://blogs.msdn.microsoft.com/patricka/2015/01/12/controlling-webbrowser-control-compatibility/

yes I tried this already.
On 12 May 2016 at 15:35, Antoine Vandecreme<EMAIL_ADDRESS>wrote:

Have you tried to force a more recent version of IE as I suggested in #920
https://github.com/openseadragon/openseadragon/issues/920 ?
Here is the link on how to do that:
https://blogs.msdn.microsoft.com/patricka/2015/01/12/controlling-webbrowser-control-compatibility/
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/openseadragon/openseadragon/issues/933#issuecomment-218758774

What was the result? Were you able to force IE11?

I will try to publish my website and give you an exe to test it soon and
thanks for your care
On 13 May 2016 at 01:39, Antoine Vandecreme<EMAIL_ADDRESS>wrote:

What was the result? Were you able to force IE11?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/openseadragon/openseadragon/issues/933#issuecomment-218915978

you can test this exe : https://www.dropbox.com/s/4tciej5d8mpboi6/OSDViewer.rar?dl=0

Sorry, I only have a Linux machine. I can't help you with that.
Plus, it wouldn't be safe to run an unknown executable on my machine...

Ok never mind.

Should be fixed in my next patch (v.2.4.3 or possibly 2.5.0), assigning to myself

@hossam707
I know this is an OLD issue, but I'm finishing up an event-handling (MouseTracker) patch and I'm curious if the new code improves the issues you're seeing (it should!).
If you have a little time to try it out, I would love to hear your feedback!
Links to Demos and Preview Builds
Cheers


Update installation command

While installing Casbin for Go as per instructions here using the go get command I received the following error -
go: go.mod file not found in current directory or any parent directory.
	'go get' is no longer supported outside a module.
	To build and install a command, use 'go install' with a version,
	like 'go install example.com/cmd@latest'
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.

after which found that go get is deprecated (https://go.dev/doc/go-get-install-deprecation).
I installed using go install github.com/casbin/casbin/v2@latest.
It looks like the installation command need to be updated in the docs. Please let me know and I will be happy to send a PR, thanks!

@PokIsemaine

@harshalmittal4 Thanks for your feedback, but I tried to follow your instructions and did not install successfully

After reading Deprecation of 'go get' for installing executables, it is my understanding that go get is just no longer used to "install executables", not completely deprecated.
As indicated in the picture, casbin is not a main package, so it cannot be installed via go install. You should get casbin via go get, just like the official website.
In addition, according to your error message, you may not execute go get in the correct directory (where the go.mod file exists), so an error occurred
go: go.mod file not found in current directory or any parent directory.

I tried to install casbin using go get and it worked

Hope this helps you

Oh sorry @PokIsemaine , I ran go install after which it started downloading some projects due to which I switched to another window.  I just checked that it's not installed.

I was not in the correct directory, I am able to install it now via go get. Thanks and sorry to bother you with this! Closing the issue

Hey @PokIsemaine ,
unrelated to this issue, I find the Casbin project piquing my interest as it's related to policy enforcement and control, which is similar to something to what I've worked on earlier, and also because I'm looking for a Go project to contribute to for learning and developing my skills.
I wish to participate work on a Casbin project for GSoC and currently exploring as much as I can about the project. Would you be please able to help me know if there are some easy issues that I can try?

@harshalmittal4 you can try to contact @hsluoyz in
https://gitter.im/casbin/gsoc

Thanks


[nrf noup] soc: nrf54l: Disable CRACEN RAMs on system off

Configure the CRACEN internal RAMs to avoid being retained during system off. Exiting system off triggers a system level reset so there is no need for the CRACEN RAMs to be retained during that.
Noup since the upstream code is not TFM aware yet and the edited function does not exist upstream.

@Vge0rge is this PR still valid?

It is but I didn't have a chance to work on it for some time now :/


Closing moved files creates IndexError

Description
What steps will reproduce the problem?

close all files so that you have untilted1.py
open two files
move/delete/rename them outside of spider
when coming back to spyder, a windows appears that will ask you to close the first one. do that
You end up on the second one. The windows doesn't appear
click on untilted1.py
click back on the second one
a windows appears that will ask you to close it. do that
Indexerror

Traceback
  File "/Users/quentinpeter/pyscripts/spyder/spyder/plugins/editor/widgets/editor.py", line 1971, in current_changed
    (index, self.data[index].editor.filename))
IndexError: list index out of range

Versions

Spyder version: 4.0.0.dev0 dccf03854
Python version: 3.7.0
Qt version: 5.9.3
PyQt5 version: 5.9.2
Operating System: Darwin 18.2.0

Dependencies
pygments >=2.0    :  2.2.0 (OK)
qdarkstyle >=2.6.4:  2.6.4 (OK)
sphinx >=0.6.6    :  1.8.1 (OK)
psutil >=0.3      :  5.4.7 (OK)
pyls >=0.19.0     :  0.21.2 (OK)
nbconvert >=4.0   :  5.4.0 (OK)
pandas >=0.13.1   :  0.24.1 (OK)
numpy >=1.7       :  1.15.2 (OK)
sympy >=0.7.3     :  1.3 (OK)
cython >=0.21     :  0.28.5 (OK)
qtconsole >=4.2.0 :  4.4.1 (OK)
IPython >=4.0     :  7.0.1 (OK)
matplotlib >=2.0.0:  3.0.2 (OK)
pylint >=0.25     :  2.1.1 (OK)

Thanks for the very clear way to reproduce this.


Unsaved file does not detect underlying file changes

Refs: #33302

Have auto save off, make changes to a file.
Open the same file in some other editor and make changes to it and save
Go back to vscode and save your original changes. Notice that the saved changes from step 2 get overwritten. I would expect I get some conflict dialog

@isidorn I cannot reproduce and I think it is unrelated to #33302. does it reproduce all the time?

@bpasero for some reason I can no longer reproduce this.
Yes it is unrelated to the undo stack, I just found this while testing that
Will reopen if I see it again

@isidorn the condition that brings this up is relatively simple: the modification time of the file is checked before saving, and if that one is newer it means another editor has changed it.


Request to Add a oneAPI Sample OpenMP Offload Jupyter Notebook

Summary
I have some OpenMP Offload tutorial jupyter notebooks and associated code that I would like to add to oneAPI samples (currently they are on the DevCloud). This is similar to the DPC++ essential training that's currently in the samples.
I have both C++ and Fortran jupyter notebooks. The sample should reside in DirectProgramming/C++/Jupyter   and DirectProgramming/Fortran/Jupyter
Problem statement
Having these notebooks and code samples would help introduce users to OpenMP Offload which is supported in the oneAPI HPC toolkit.
@pmpeter1 @JoeOster  @srdontha

You are citing two domains, so long as the samples are unique to that domain, I have no real issues. Please supply the proposed folder names and paths

No objection.


[PR-1339] read test users from test config

read test users from test config instead of hardcoded values in setup-test-users.
no need to rename the util script since this no longer is tied to an instance (broad vs other).

testing --
terra-cli (dexamundsen/pf-1339) >> ./tools/setup-test-users.sh test
ERROR: Usage: ./setup-test-users.sh [adminUsersGroupEmail] [testConfigFile]

terra-cli (dexamundsen/pf-1339) >> ./tools/setup-test-users.sh trdt src/test/resources/testconfigs/broad.json

Checking whether the server requires inviting new users.
Inviting test users.
execute -->  terra user status<EMAIL_ADDRESS>|| terra user invite<EMAIL_ADDRESS>execute -->  terra user status<EMAIL_ADDRESS>|| terra user invite<EMAIL_ADDRESS>execute -->  terra user status<EMAIL_ADDRESS>|| terra user invite<EMAIL_ADDRESS>execute -->  terra user status<EMAIL_ADDRESS>|| terra user invite<EMAIL_ADDRESS>execute -->  terra user status<EMAIL_ADDRESS>|| terra user invite<EMAIL_ADDRESS>execute -->  terra user status<EMAIL_ADDRESS>|| terra user invite<EMAIL_ADDRESS>
Creating the SAM group for CLI test users.
execute -->  terra group describe --name=cli-test-users

Granting the admin users group ADMIN access to the SAM group for CLI test users.
execute -->  terra group add-user --name=cli-test-users --policy=ADMIN --email=trdt

Granting the SAM group USER access to the spend profile.
execute -->  terra spend enable --policy=USER<EMAIL_ADDRESS>
Adding<EMAIL_ADDRESS>as an ADMIN of the SAM group.
execute -->  terra group add-user --name=cli-test-users --policy=ADMIN<EMAIL_ADDRESS>
Granting<EMAIL_ADDRESS>OWNER access to the spend profile.
execute -->  terra spend enable --policy=OWNER<EMAIL_ADDRESS>
Adding<EMAIL_ADDRESS>as a MEMBER of the SAM group.
execute -->  terra group add-user --name=cli-test-users --policy=MEMBER<EMAIL_ADDRESS>
Adding<EMAIL_ADDRESS>as a MEMBER of the SAM group.
execute -->  terra group add-user --name=cli-test-users --policy=MEMBER<EMAIL_ADDRESS>
Adding<EMAIL_ADDRESS>as a MEMBER of the SAM group.
execute -->  terra spend enable --policy=USER<EMAIL_ADDRESS>
Adding<EMAIL_ADDRESS>as a MEMBER of the SAM group.
execute -->  terra spend enable --policy=USER<EMAIL_ADDRESS>
do nothing<EMAIL_ADDRESS>

@marikomedlock / @melissachang --> FYI since this ticket was from an earlier PR you had worked on
https://broadworkbench.atlassian.net/browse/PF-1339


Quote Creating a Safe App

https://app.safe.global/apps/open?safe=matic:0xc16e9bFFE08033efb0A0BF509167ac07a1811439&appUrl=https%3A%2F%2Fbison-narwhal.vercel.app

https://docs.safe.global/learn/safe-apps/get-started

In order to get to the app natively within the Gnosis Safe interface we need to use the Safe Apps SDK. Once we get everything added and tested there is a review process. Should not be anything major but it is not a trivial amount of work to fulfill the Gnosis  requirements. We can quote this one out too if you want to prioritize adapting your app to be used as a Safe App.


Uncaught TypeError: query.bindings.map is not a function

Since a little while, Ignition doesn't show itself when an exception is triggered on a Laravel 9 project. Instead, I get the following in the console:
Uncaught TypeError: query.bindings.map is not a function
    queries https://localnova.local/make-pdf:23144
    transformIgnitionError https://localnova.local/make-pdf:23138
    ignite https://localnova.local/make-pdf:23087
    <anonymous> https://localnova.local/make-pdf:23264
[make-pdf:23144:38](https://localnova.local/make-pdf)
    queries https://localnova.local/make-pdf:23144
    map self-hosted:224
    transformIgnitionError https://localnova.local/make-pdf:23138
    ignite https://localnova.local/make-pdf:23087
    <anonymous> https://localnova.local/make-pdf:23264

In my case, the query object looks like the following:
{
  "sql": "    SELECT code, nom_departement FROM departementfr\n    WHERE id_departement = :id\n    LIMIT 1",
  "time": 13.72,
  "connection_name": "mysql-legacy",
  "bindings": {
    "id": "28"
  },
  "microtime":<PHONE_NUMBER>.315789
}

So bindings there is an object, not an array.

We'll handle this in #43


The white border of Code’s icon is too thin, inconsistent with Visual Studio

Compare:

(cc @rebornix)

We've got an updated icon coming soon that addresses your issue here.  Thanks for sharing your feedback :)

Actually, I prefer the thin line of VS Code.

https://github.com/Microsoft/vscode/issues/6607


Connection refused

I'm getting this when trying to run the following command
ssh clidle.duckdns.org -p 3000

Duplicate of #8.


where am I supposed to put the javascript in my meteor app?

So far I have simply put the javascript into a  tag inline in the template, but there must be a better way.
If I use the jQuery style syntax in the onCreate or onRendered, it doesn't work (function does not exist)
so where am I supposed to put the Semantic-ui declarations in my Meteor app?
A short example would be nice in the docs.
thanks

I am not sure what Javascript you are talking about - but I feel your pain. It is, like many things, really simple when you don't think about it too much. Adding the Semantic-UI package makes it available anywhere in your app on the client side. Then, to add javascript to dropdowns, selects (which actually use a menu metaphor to override the ugly "native" dropdowns that smartphones try to have you use), accordions, etc (all of the "modules") you can add them to the onRendered callback in the associated template. It is simply adding jquery selector (either the id or class name) and name of the javascript component like this
$('.ui.accordion').accordion({options});
You can then add custom event handlers to whatever callbacks are exposed by the component - by default the initialize refresh and destroy life-cycle event hooks and others like onChange or onBlur depending on the module - you can read about each in the Usage tab for each component.
 I have spent a crazy amount of time trying to use the built in capabilities for serializing and loading data - it is ugly and I am sure I am doing something wrong. Right now I know I am using a hack but it would be nice to be able to call .form('set values',  formData) and have it update all fields - except it does strange things with caching values that really doesn't work well with the "Meteor way" - at least not the way I am doing it.
Good luck,

i figured it out. i think it didn't have an additional package that was required.

@streamnsight which package? I'm having the same problem. This:
Template.tpl.onRendered(function () {
  $('.toggle-popup')
    .popup({
      popup: '.popup',
      on: 'click',
    });
});

doesn't work ([Log] TypeError: $('.js-toggle-search-settings').popup is not a function. (In '$('.js-toggle-search-settings').popup', '$('.js-toggle-search-settings').popup' is undefined) (meteor.js, line 930)). scoping it to the tamplate (this.$) also doesn't work.

Problem solved. Meteor 1.3 puzzled me a bit. I accidentally put it in the imports directory and the js files didn't load.

Closing this

@andrewpeterprifer Can you please elaborate on your fix or a give us a link to the repo?


Implemented value array prefixing (mutation)

Fixes https://github.com/rofrischmann/inline-style-prefix-all/issues/13
Implemented with forEach and mutation https://github.com/rofrischmann/inline-style-prefix-all/pull/14 (same thing but with map/reduce)
In theory, this should perform better, though it's actually slightly more lines than #14

Awesome thank you! Would love if you could remove the semicolons to keep it consistent. Also you might add some line comments to describe some steps, but I guess it is nothing which one would not understand while reading.
I will merge this after semicolons are removed :P

Oops! Totally forgot about your style ;)

Gentle bump :)


Fix interactive testing

This provides a fixture setting up onyo.lib.ui, that is run for every
test. Settings for yes, quiet and debug are read from a new test
marker 'ui' if given. Otherwise set to defaults (False for all of
them). The marker takes a dictionary, allowing to enhance this later on
for other future features of the UI object (like using the rich
package or redirecting logging or whatever else).
Note, that this is not going to work for CLI tests, since they spawn a
subprocess with its own python context. However, that is obviously
fine, since the CLI calls take explicit flags for that.

In general, this looks good to me and I will merge :)
Other than punctuation, I just want to add that I really like the ui fixture. You did just apply it to the tests that needed the fixture to be successful, not everywhere along the tests, which is fine, but since there are a lot of tests that can be removed based on the changes in the code base (discussed multiple times before), I want to note that once somebody cleans them up, we should also apply the new fixture to the other tests were it makes sense.


the media element need add a event like 'dragBegin','dragEnd' when you drag the processbar?

i use my lyric plugin with this tool, i can't get the audio process when i drag the process bar,then i read the api document,i found all  supported events are come from html5,no solution i want.
please forgive me that my english is not well.

@joney-pinkman Is this still an issue?

Closing this issue since no answer has been posted in more than 2 weeks. If you'd like to reopen this, let us know. Thanks!


Update crate dependencies

Updated all dependencies to the latest versions, expect xml-rs, which we're very behind on and will require some code updates to be compatible with the newest version. Hyper is now 0.8.x, which means downstream crates that use Rusoto currently have to build two versions of hyper if they're using 0.8.x.
Updated the format of the Cargo.toml files via cargo add. Now we can use that to update dependencies. (cargo install cargo-edit, https://github.com/killercup/cargo-edit)

Closing in favor of PR #225 which has the same changes but rebased after the ETS work.


osram flex rgbw

Thanks!
Is there any model number written on the strip?

I have the Osram Stip.
This is the Model No.<PHONE_NUMBER>110
You can finde it on the datasheet:
https://www.led.de/media/pdf/ff/3d/46/datenblatt_10051_osram_lightify_flex_rgbw_flexibler_led_strip.pdf

plz merge

Thanks!


Add start and end events

I've added start and end events and the mousedown and up fallbacks

Great job! Thanks for your contribution.
I think the moving event is very useful when you want to create a swipe effect and make the swiper following your finger. 😄


Connection to SQL Server 2019 using SQL Server Native Client 11.0

From the below document it looks like SQL Native Client 11.0 does not support connection to SQL Server 2016 and above.
https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/support-policies-for-sql-server-native-client?view=sql-server-ver15
“SQL Server Native Client 11.0 supports connections to, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 (11.x), SQL Server 2014 (12.x), and Azure SQL Databases";
Connection to SQL Server 2019 using Native Client 11.0 works in some environments and fails in another. Could you please clarify whether Native Client 11.0 supports connection to SQL Server 2019.
If it will not support 2016 and above , Can you make explicit statements like 'Native Client 11.0 does not support connection to SQL Server 2016 and above'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e062762e-59ff-be08-1f92-7a5046ead8cc
Version Independent ID: c8ee4fa3-21d5-0f8d-d89f-bbbbc6819c42
Content: Support Policies - SQL Server Native Client
Content Source: docs/relational-databases/native-client/applications/support-policies-for-sql-server-native-client.md
Product: sql
Technology: native-client
GitHub Login: @markingmyname
Microsoft Alias: maghan

@Ash46 -- thank you for your feedback.  Please consider these resources for additional information:

DBA Stack Exchange
Stack Overflow

@markingmyname -- please look into this issue.

@WilliamAntonRohm @markingmyname  Thank you for the links. I could not found the information related to my questions in those links. It would be great if you could confirm the connectivity support from your end.

@Ash46,
SQLNCLI - from sqlncli.dll is deprecated, and SQL Native Client remains deprecated. However, sqlncli11.dll is still shipped with SQL Server 2019. I believe it's a different iteration sqlnclirda11.dll. SQL Native Client is no longer receiving updates, but there should be no issues with the provider working to connect to SQL Server 2019.
I will add this Note to the article as well.
The article will be updated by the end of the week.
I hope this info helps.
Thank you.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue. To see what the community is wanting, please visit the UserVoice site.


Credit card form language

Coverage remained the same at 100.0% when pulling 662220dbdbab19fb53fbf90172c96b3430c289a0 on CreditCardFormLanguage into 7c76826f2b6522cd11daebab4de30fbe98a03652 on master.


Use schema title also when using allOf

Consider the following yaml:
MyBase:
  properties:
    foo:
      type: string

MyType1:
  allOf:
    - $ref: '#/components/schemas/MyBase'
    - title: SomeTitle1
      properties:
        bar:
          type: string

MyType2:
  allOf:
    - $ref: '#/components/schemas/MyBase'
    - title: SomeTitle2
      properties:
        baz:
          type: string

MyType:
  oneOf:
    - $ref: '#/components/schemas/MyType1'
    - $ref: '#/components/schemas/MyType2'

When MyType is rendered (e.g. in a response), the oneOf selector buttons display MyType1 and MyType2, not SomeTitle1 and SomeTitle2 as expected:

However, when removing the allOf in MyType1 and MyType2, i.e. when doing
MyType1:
  title: SomeTitle1
    properties:
      bar:
        type: string

and similar for MyType2, then it renders correctly:

I would expect title to be used for the oneOf selector also when the different types are defined using allOf.

Interestingly, they will render correctly (use the title) if the schema objects are placed in a reference object (see also #721).

Another workaround (or perhaps the intended use?): Define title at the top level:
MyType1:
  title: SomeTitle1
  allOf:
    - $ref: '#/components/schemas/MyBase'
    - properties:
        bar:
          type: string

If I have misunderstood the OpenAPI specification and this is the only correct usage, feel free to close this issue.

Just define the title at the top level. It is the intended use.
MyType2:
  allOf:
    - $ref: '#/components/schemas/MyBase'
    - title: SomeTitle2
      properties:
        baz:
          type: string

Resulting type is, in fact, a combination of two types so semantically it shouldn't inherit the title of any of types.
E.g.:
Type:
  allOf:
    - title: Type with foo property ONLY
      properties:
        foo:
          type: string
    - title: Type with baz property ONLY
      properties:
        baz:
          type: string

If the Type inherits any of titles it would be semantically incorrect.


Update custom collection documentation (leverage new collection protocol)

Follow up to #8674 - this PR updates the custom collection docs leveraging the inline documentation in the new dask.typing.DaskCollection protocol. I've cut out the "by hand" documentation of the collection methods (and in the process improved some of the protocol class docstrings). I also updated the example Tuple collection (now reflects the builtin collections a bit more, with a __dask_optimize__ defined outside of the class).

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

Thanks, Jim!


bench(clippy): Fix manual_clamp lint

This is new in Rust 1.79

@bonsairobo Just checking in on this…

Ah sorry this slipped my mind. Looks good!


Not rounding coordinates in CFF

See:
http://blog.typekit.com/2015/10/01/smoother-curves-with-decimal-coordinate-values/
The gist of it is, non-integer numbers are allowed in CFF, and they seem to work.  Given that UPEM 1000 is used in CFF, and we are interpolating a lot, we should consider using those sometimes.  Now, encoding a non-integer takes 5 bytes (instead of 1 or 2 for most numbers), so we should be very cautious about this.  But would be good to think about supporting it (and in fonttools's t2CharStringPen).
Since coordinate data is encoded using relative coordinates (essentially 2d vectors), a good heuristic would be, to compare the rounding error to the magnitude of the vector, or to the individual components (x/y), or possibly even the change in direction.  So, perhaps adding a tolerance would be enough, but we have to consider different cases, test with a bunch of fonts, and decide what rule is most useful.
On the fonttools side, we need to support these three cases:

Round everything,
Round nothing,
Round some things,

again, using a tolerance does all of them.  Value of 0 means don't round anything (no rounding error is tolerated).  Value of 1 means round everything (100% rounding error is tolerated!).  Values like 0.05 might be good for most workflows, specially for interpolations.
@readroberts can you share your script font with us for testing please?

@readroberts ping :)

I sent a copy of  BickhamScriptTestPro3-SemiBold.otf to Behdad by e-mail on Tuesday, February 23, 2016. Let me know if I need to send another copy.

The fonttools T2CharStringPen now includes a roundTolerance argument, since version 3.5.0.
https://github.com/fonttools/fonttools/issues/804
I guess now we need to also modify the ufo2ft.outlineOTF.OutlineCompiler class so it also accepts a similar roundTolerance argument (with default 0.5, round everything).
And finally, we need to update fontmake to allow passing the --round-tolerance as a command-line option.

Support for roundTolerance added with #118. Will now add a command-line argument to fontmake


Add a script to generate the contributors list

For progress reports.
Things it should do:

Take a commit hash to start at and another to end at
Have a txt file or something where people can put their github name and the name they want to override it with
Alphabetize the list after applying overrides
Be able to do both content and engine
Dump the total commit count

Might also be nice to have a script to override the patrons list too.

Done in https://github.com/space-wizards/space-station-14/commit/d0c0dfc1dc0df2b66488d73a45695cdb8db4690a


Update examples to use accumulated mouse input

#14044 adds accumulated mouse inputs in the form of resources. I know some of the examples in bevy_math and bevy_transform (e.g. align, random_sampling, sampling_primitives) manually accumulate mouse inputs to handle camera movement, so those should probably be updated in light of the linked PR. There might be some others outside bevy_math as well. Updating these would help set a good example for making proper use of the new tool!

first_person_view_model should probably use accumulated mouse input as well

I might give this a crack if no-one's looking at it, just to dip my toes in the project 🙂


Auto-install latest modified exploitable.py

Let setup.py take care of installing latest modified exploitable.py, if necessary. This might influence gdb script generation (and execution) of afl-collect.

This has been incorporated in v1.19a.