EOX Ingestion and FAIRiCUBE Dataset Metadata

@eox-cs1
When ingesting data under rasdaman, we now have a fairly consistent process where we first create an issue containing all relevant information for the desired dataset (either directly as a data request Issue, or by activating the entry for the relevant dataset via the Project), triggering:

ingestion of the dataset
creation of a metadata record for the dataset by extracting this information from the request issue

When ingesting data under EOX, to my understanding the UC partners have to fend for themselves, upload the data to the bucket, fill the metadata forms for EDC/SentinelHub. How is the corresponding metadata record for this dataset generated? Does this utilize the EDC approach with AWS compliant YAML? How will dataset metadata concepts not covered under EDC be provided?

@eox-cs1 IS ANYBODY OUT THERE???

just to document, from our side we have this issue for discussing rasdaman/metadata linkage.

once available, ticket can be closed?


Migrate cache module with git history

Purpose
$Subject

@kalaiyarasiganeshalingam Shall we add .yml files related to git-actions?


SimpleModel Encoder

Description of feature/enhancement
Implement encoder class for SimpleModels so they can be leveraged in methods such as __str__ and __repr__.
Description of implementation
Don't have anything specific in mind at the moment, but we will need to handle cases such as type conversion.
Why this is a good feature/enhancement
This will allow us to encode general purpose SimpleModel information in a separate module.
Additional context
n/a

@Turtle24 I have created this issue to keep track of encoder features

@Turtle24 I have created this issue to keep track of encoder features

@skekre98 here's a bit more context. Hopefully this helps 😃
This is the import from  simple_learn.encoders import simple_model_encoder for further context.
So far the npEncoder is just sub class of the json.JSONEncoder class. When you def default it returns a serializable object for the int32 that's passed in. The if statement isinstance checks if the object is np.int32 and then returns an int(object) as to convert it. Otherwise the normal object is returned.
import json
import numpy as np

class npEncoder(json.JSONEncoder):
    def default(self, obj):
        if isinstance(obj, np.int32):
            return int(obj)
        return json.JSONEncoder.default(self, obj)

This is the current use case for the npEncoder.  cls=simple_model_encoder.npEncoder uses the complex subclass that was created.
def __repr__(self):

        attr = {
            "Type": self.name,
            "Training Duration": "{}s".format(self.train_duration),
            "GridSearch Duration": "{}s".format(self.gridsearch_duration),
            "Parameters": self.attributes,
            "Metrics": self.metrics,
        }

        repr_out = json.dumps(attr, cls=simple_model_encoder.npEncoder, indent=4)
        return repr_out

@skekre98 here's a bit more context. Hopefully this helps 😃
This is the import from  simple_learn.encoders import simple_model_encoder for further context.
So far the npEncoder is just sub class of the json.JSONEncoder class. When you def default it returns a serializable object for the int32 that's passed in. The if statement isinstance checks if the object is np.int32 and then returns an int(object) as to convert it. Otherwise the normal object is returned.
import json
import numpy as np

class npEncoder(json.JSONEncoder):
    def default(self, obj):
        if isinstance(obj, np.int32):
            return int(obj)
        return json.JSONEncoder.default(self, obj)

This is the current use case for the npEncoder.  cls=simple_model_encoder.npEncoder uses the complex subclass that was created.
def __repr__(self):

        attr = {
            "Type": self.name,
            "Training Duration": "{}s".format(self.train_duration),
            "GridSearch Duration": "{}s".format(self.gridsearch_duration),
            "Parameters": self.attributes,
            "Metrics": self.metrics,
        }

        repr_out = json.dumps(attr, cls=simple_model_encoder.npEncoder, indent=4)
        return repr_out


Make Typeutil.ToCSharpString produce more C#-like formatting

This changes the way how TypeUtil.ToCSharpString formats certain types to a representation that looks more like C#:

Generic type parameters. Those are currently surrounded with a centered dot (·) that noone quite seems to know what they're good for. (†) (See #406, esp. the recommendation made in https://github.com/castleproject/Windsor/pull/406#issuecomment-394178922.)

Nested generic types. For example, given Outer<bool>.Inner<char>, it outputs "Outer<·T·>.Inner<bool, char>" which is likely to be confusing rather than helpful. This changes the way how such types get formatted to something more familiar to C# users: "Outer<bool>.Inner<char>". (This resolves #404.)

These changes are classified in the changelog as an "enhancement". Given that there were explicit unit tests about that behavior, it's not really a bugfix, but a change. Classifying as a "breaking change" would be accurate, but given that the method's intended use case is for diagnostics, it seems somewhat over-the-top to mark it as "breaking".
(†) My personal theory about the centered dots is that they were needed to mark a placeholder, so you'd know how to apply, or "distribute", the generic type arguments from the innermost type over the outer types. Now that this distribution is done automatically, the dots aren't really needed anymore.

@stakx beat me to it! :)
I had mine on a branch but did not finish it in time.

Merged, thanks.


MB-4248: Fix datadog causing app crash when an invalid path is given

Fix crash when an invalid path is given. It appears that req does not have route when the given path is invalid.
Change:

Partially reverted https://github.com/wiivv/node-connect-datadog/commit/e034e97d2ce473bde4857781c03cd6d04b586aba by using originalUrl for the case when req.route is null.

Hey guys,
Somehow I am still getting these emails. Probably want to remove me. 😅
On Wed, Sep 13, 2017 at 11:27 AM Eric Lin<EMAIL_ADDRESS>wrote:

@ericln requested changes on this pull request.
have a look at this, you'll know why the build breaks :)
https://github.com/wiivv/development-guide/wiki/Private-npm-module
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wiivv/node-connect-datadog/pull/3#pullrequestreview-62532851,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARmNtp6Y6KJt8cm2TkuK2m3B6M5v4l3uks5siB6LgaJpZM4PWelj
.

@stevegaossou question is...WHY CAN YOU EVEN SEE IT AND REPLY TO IT!!!

Hi Steve! 👋

you 2 GAOs

Hi Mary 👋🏽👏🏽
Haha 😂
Eric I don't know how I am on this thread. Magic!
I remember seeing a lot of emails when you guys removed me from the repos.
Maybe I am still on one of the wiivv GitHub teams where new repos
automatically include me?
Anyways, hope you guys are doing good! Maybe I should visit and stop by for
a Heros of Storm session. 😆
Btw if I was still a wiivv when Mary joined it would have been 2 Gao's 2
Mary's.
On Wed, Sep 13, 2017 at 11:32 AM Eric Lin<EMAIL_ADDRESS>wrote:

you 2 GAOs
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wiivv/node-connect-datadog/pull/3#issuecomment-329257190,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARmNtnDZTrReVe9-wpkursWE3J1YJWieks5siB-5gaJpZM4PWelj
.

UPDATE: By request, changed the circle.yml to stop publishing modules on feature and bugfix branches. Also by request bumped the version number in the PR itself.
@stevegaossou Yes do visit us! The guys wouldn't mind having one more person join in their "team-building" gaming Fridays.


LiveSettingProperty is not Supported for Status bar apeared in 'Workbook front page'

Steps to Reproduce

Open "Xamarin Workbook"
Products window is opened.
Navigate to the "wpf "icon and select "create workbook".
4.Navigate to target platform Combo box and expand it
Select any other target platform such as 'iOS'
Observe the Inspect property for Status bar item

Expected Behavior
LiveSettingProperty should be True for change of status in Status bar
Actual Behavior
LiveSettingProperty is not Supported for change of status in Status bar
Narrator Behavior: Narrator is not announcing the change of status in Status bar
NVDA behavior:NVDA is not announcing the change of status in Status bar
User Impact:
Users who rely on screenreader will be unable to know the status appearing in Status bar
Screen-Shots:

Video Attachments:
LiveSettingProperty_Status_bar_Narrator.zip
Environment:
Windows :Windows 10 Pro Version 1803 (OS Build : 17672.1000)
Xamarin Version : 1.4 (master/b3f92f9)
NVDA Version: 2018.1

Log File

Exemption Approved - 1813


intelliSense should show exact match first

VSCode Version: 1.7 Insider
OS Version: OS X 10.11.6

This this fix caused other issues, I have reverted the changes for this issue


[RFC] Platform support

I'm bringing the discussion of which platforms we should support after this comment. I think we should do the following changes to the Platform Support document, and act accordingly.
My proposal is to state that in Tier 1 we only support supported platforms. That is, if a platform reached EOL (like macOS 10.X), it doesn't make sense to keep it here.
Therefore, the two main Tier 1 platforms should be split according to their own support. macOS 10.X, for instance, can still be considered Tier 2.
In case of Linux, as of today, they should be also split in 3.X vs 2.X.

For Windows there is #10085

Fair point. As a person living in a third-world country, I can understand the need to support older systems. But maybe not in Tier 1? In the specific cases of current Tier 1 platforms, we know they still compile in lower systems, we would simply not claim to have binaries ready.

Seem reasonable to me to demote macOS 10.x to tier 2 at this point.

Just a thought: I think it depends heavily on what is to be supported: building or being able to run a built application. A developer can choose the OS used for building, but very often they have no power over which OS will be used to run the application which was built by crystal.
I think to remember there was once an issue regarding (runtime) support for Windows 7, where the question, whether OS support should refer to building or running crystal applications already came up

@kjarex Yes that's a good point. And in fact, we're mainly talking about another, even less critical level of support: What we provide official packages for.
Specifically https://github.com/crystal-lang/distribution-scripts/issues/228 is only about the packaging, which the way we're building them requires or would be easier to achieve if we drop support for macOS 10.
That would just mean our release builds are expected to work only on macOS 11+. But the compiler and stdlib are still fully compatible with older OS versions. You just won't get a compatible version of libpcre2 and the compiler from the official distribution packages.

#8919 and #10768 are some examples of Linux features requiring relatively recent kernel versions

It's worth noting they're completely optional, though. A matching linux kernel is only required if you you use copy_file_range or io_uring explicitly.

Some questions/notes:

We can probably drop the Compiler/Std columns. They don't add any real value (at least for the higher tiers) and take up space.
The interpreter is another platform that's not listed here. It technically doesn't have a specific target triple (it's just the one of the host). Should we use interpreted for that?
For practical reasons, it's not a good idea to duplicate entries for unsupported OS versions in lower tiers. That would just be a lot of noise and hard to understand. Instead, a note that supported versions generally only covers supported OS versions should be enough. We can still give a minimum supported version in the same entry.


Export specs as Postman collections

The Registry tool may be able to leverage the postmanlabs/openapi-to-postman library to export OpenAPI v3 specs as Postman collections. Below are some suggestions for how this feature might be offered.
Command: registry export postman [spec]
Output: The Postman collection (v2.1.0) in JSON format.
Since the library is released on npm, some investigation is necessary to determine whether it can be interoperable with our Go code, and how we would would handle that. Adding a NodeJS dependency to the Registry tool isn't an ideal solution.

Unassigned for now. We can pick this up after thinking more about how to integrate with Postman and the provided JavaScript libraries.


Impl Default for (String|Bytes|Boolean|None|Ellipsis)Literal

Summary
This PR adds Default for the following literal nodes:

StringLiteral
BytesLiteral
BooleanLiteral
NoneLiteral
EllipsisLiteral

The implementation creates the zero value of the respective literal nodes in
terms of the Python language.
Test Plan
cargo test

Current dependencies on/for this PR:

main

PR #8341   👈

This comment was auto-generated by Graphite.


Error on build

Hello,
I'm running test on your repo, but it seems I cannot call cuda SDK.
   Compiling cuda v0.1.0 (file:///Users/kwangin/workspace/study/cuda)
error[E0432]: unresolved import `self::ll::CUdevice_attribute_enum::*`
   --> src/driver/mod.rs:130:13
    |
130 |         use self::ll::CUdevice_attribute_enum::*;
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Could not find `CUdevice_attribute_enum` in `ll`

error[E0432]: unresolved import `self::ll::cudaError_enum::*`
   --> src/driver/mod.rs:414:9
    |
414 |     use self::ll::cudaError_enum::*;
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Could not find `cudaError_enum` in `ll`

error[E0412]: cannot find type `CUcontext` in module `ll`
  --> src/driver/mod.rs:43:13
   |
43 |     handle: ll::CUcontext,
   |             ^^^^^^^^^^^^^ not found in `ll`

Is it problem of cuda SDK, or something else?
It causes on OSX 10.10, Cuda 7.5.

That seems odd. Did you use the create-bindings.sh script? Because you should not; you should compile / use the crate as it is right now.

@japaric I did it by cargo build

cargo build works for me on HEAD. Can you pase the output of these commands:
$ git rev-parse HEAD
5f10580f0f25c783b09c18897cbadb4d8661c098

$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean

$ rustc -V
rustc 1.16.0-nightly (eedaa94e3 2017-02-02)

@japaric Oh sorry, there was some work in my git. It's my mistake.
cargo build, cargo test works well. Thanks~


iRODS remote functionality - issues with "zone"

Hello! Snakemake is quickly becoming one of my favourite tools and I was pleasantly surprised to find out there was support for iRODS. I've observed two issue however that I have debugged for myself and just wanted to share it here for the benefit of other users. I will format the two issues separately but they are related.
Snakemake version
7.3.0 (as far as I can tell these issue still exists on the main branch)
Issue 1. glob_wildcards requires anti-pattern to work properly
Describe the bug
https://snakemake.readthedocs.io/en/stable/snakefiles/remote_files.html#irods
The example provided in the documentation has the following code:
from snakemake.remote.iRODS import RemoteProvider

irods = RemoteProvider(irods_env_file='setup-data/irods_environment.json',
                       timezone="Europe/Berlin") # all parameters are optional

# please note the comma after the variable name!
# access: irods.remote(expand('home/rods/{f}), f=files))
files, = irods.glob_wildcards('home/rods/{files})

The last line causes an issue by throwing irods.exception.CollectionDoesNotExist. This issue can be traced to the fact that the iRODS "zone" is not being included when running glob_wildcards. When I manually add the zone as a prefix to the path, it runs fine. (i.e files, = irods.glob_wildcards('/zone/home/rods/{files})). However, this does not seem to be the correct pattern - the documentation states:

Please note that the zone folder is not included in the path as it will be taken from the configuration file. The path also must not start with a /.

Proposed solution
The way to fix this is to include the zone as a prefix, as the documentation suggests should happen. The glob_wildcards function is defined in snakemake/remote/__init__.py. The snakemake/remote/iRODS.py RemoteProvider class can override the function as follows:
def glob_wildcards(self, pattern, *args, **kwargs):
    remote_pattern = os.path.join(os.sep, self._irods_session.zone, pattern)
    return super().glob_wildcards(remote_pattern, *args, **kwargs)

This will append the zone as a prefix prior to execution of the super function. This has resolved the issue for me.

Issue 2. Uploading functionality is broken for users without access to complete directory structure
Describe the bug
This issue lies in the RemoteObject class of snakemake/remote/iRODS.py:
    def _upload(self):
        # get current local timestamp
        stat = os.stat(self.local_path)

        # create folder structure on remote
        folders = os.path.dirname(self.remote_path).split(os.sep)[1:]
        collpath = os.sep

        for folder in folders:
            collpath = os.path.join(collpath, folder)

            try:
                self._irods_session.collections.get(collpath)
            except:
                self._irods_session.collections.create(collpath)

The function splits up the directory structure, such that /zone/home/rods becomes ["zone", "home", "rods"]
folders = os.path.dirname(self.remote_path).split(os.sep)[1:]
Then for each one of these folders, it tries to either "get" it or "create" it. That is, it will try to access /zone, /zone/home and /zone/home/rods. This will throw an iRODS exception CAT_NO_ACCESS_PERMISSION and fail if any of these are inaccessible to the user. In my case, I only have access to the subdirectory /zone/home/rods, which means all uploading fails for me on the first iteration of the "for loop". I imagine that having limited access to the "root" /zone directory is not uncommon.
Proposed solution
What I did to fix this for myself is to check if the directory is not accessible before attempting to get/create it.
Include iRODS access exception:
from irods.exception import CollectionDoesNotExist, DataObjectDoesNotExist, CAT_NO_ACCESS_PERMISSION
Skip over directory parts that are not accessible:
    def denied_access(self, collpath):
        try:
            self._irods_session.collections.get(collpath)
            return False
        except(CAT_NO_ACCESS_PERMISSION):
            return True
        return False

    def _upload(self):
        # get current local timestamp
        stat = os.stat(self.local_path)

        # create folder structure on remote
        folders = os.path.dirname(self.remote_path).split(os.sep)[1:]
        collpath = os.sep + folders.pop(0) + os.sep + folders.pop(0)

        for folder in folders:
            collpath = os.path.join(collpath, folder)
            print(collpath)
            if not self.denied_access(collpath):
                try:
                    self._irods_session.collections.get(collpath)
                except:
                    self._irods_session.collections.create(collpath)

I see, good catch! Could you create a PR with your fix?


Switch to ESP-IDF Framework

Testing on ESPHome 2024.10.3
Switch to ESP-IDF Framework to avoid Arduino-ESP32 related issues.
Edit: ESP-IDF webserver does not allow multipart content so no upgrades via the web interface. Deal breaker for now. Will need to revert to Arduino-ESP32

IDF Webserver does not support multipart uploads. Upgrade put on ice for now


Fix and improve adguard home helm chart

This PR is about adguard home helm chart and:

Fixes the port definitions of the deployment
Add priorityClassName support
Put all the probes definitions into the values.yaml
Add existingClaim support

Thanks for doing this helm chart !

It also removes the useless 3000 TCP port and service and ingress

@rm3l i wait for this fix. the current version breaks the dns service.


Consider adding a custom typ header value for tokens

recommended here
https://tools.ietf.org/html/draft-ietf-oauth-jwt-bcp-06#section-3.11
@vibronet proposes
at+jwt for access tokens here
https://tools.ietf.org/html/draft-ietf-oauth-access-token-jwt-00#section-2.1

was already done in 3.0


:book: Add dynamic waiting to example1

Summary
This PR replaces the fixed time waiting periods after starting KCP, mailbox-controller, where-resolver, and placement-translator. This reduces waiting time on fast machines, and prevents errors on slow machines.
Related issue(s)
Fixes #

The branch in this PR has gotten entangled with a lot of other work. Could you please rebase on main keeping only the commits that are unique to this PR?

"Merge branch 'main' into example1" is the exact opposite of what we need. What we need is that a branch in a PR builds on main by adding commits that are unique to that PR (more complex arrangements are possible, but not needed here).

For example, what I see now is two commits unique to this branch plus a merge of main into this branch. Could you start from main and cherry-pick the two commits that are unique to this branch? That would create something with the desired structure.

Sorry for the mess... hopefully I got it right this time

What I see now is that the branch in this PR (example) diverges from main with two commits (e8e7fa9faf1cb98a0c69f4a5b2f25b6f6fdc3cef then a3c227564eece20a6a7d2a56af4929d7291e02c7) that unique to this PR and then comes a commit (91c5b982b5897c967f25d8f32de233db7e4bfcdb) that is a merge of main into example1.  That merge is not what you should be doing.
What happens if you do the following?  I assume here that you have a remote named upstream that refers to the shared repo on GitHub; if not then substitute whatever name you are using for that remote, or create one if you do not already have one.
git fetch upstream
git checkout -b example1a --no-track upstream/main
git cherry-pick e8e7fa9faf1cb98a0c69f4a5b2f25b6f6fdc3cef
git cherry-pick a3c227564eece20a6a7d2a56af4929d7291e02c7

That would create a branch named example1a that diverges from main by just the two commits that are unique to this PR. If that looks like what you mean, then you could update this PR to request that with the following commands (assuming that origin is the name of your remote that refers to your fork of this repo).
git branch -D example1
git checkout -b example1
git push -u --force origin example1


Change speed (easeljs)

Is there a solution other than FPS to adjust the speed?

I've discovered that Proton.Mass affects the speed, but it isn't all that intuitive, seems a simple "speed" setting would be more useful.

There are many factors that affect the speed, such as Proton.Velocity or Proton.Force. Specific you want to achieve what effect


Can ALVR support eye tracking in quest pro?

Hello, I just read the source code of ALVR, I wonder whether it can support for eye tracking in quest pro? If so, where is the code for getting the eye tracking information from hmd? Thank you in advance!

ALVR support eye and face tracking for the Quest Pro. The code is scattered between client and server, depends on what you are looking for. You can grep for "face" or "eye".

Thank you for your reply!

Hello, Could I ask what is the difference of global eye and local eye. I saw a function tracking::to_local_eyes. Thank you in advance!

Global eye pose if the pose returned by OpenXR and it's relative to the global reference frame, usually a point on the floor with direction aligned with your playspace. Local eye is the pose of the eyes relative to the head pose, looking straight ahead. The head pose is the mid point between the two eyes.

Hello, it seems like alvr doesn't use the real eye gaze data to do FFR? I trace the code from sending the tracking information to server, and after the server received the tracking information. There is a function call (sink.send_tracking(face_data);), I saw the code in send_tracking, could you explain me more about the functions send_osc_message() and append_packet_vrcft(). Where the data would be sent to when using send_osc_message(), and where is the receving code of the osc message, what is the funcationality? Thank you so much!


Browse Page: update name search box to use typeahead

Fixes #548

really nice job!

Love this. Awesome!  Do agree with @dabutvin about the duplicate code. Especially a complex/long regex. Hard to tell if they are actually different or supposed to be the same, or to update. At the very least extract the regex as a constant. Or do what @dabutvin suggested.


member list scraping failed

Describe the bug
So when I try to run it using one specific account it doesn't work and shows this error.

.
**Desktop

OS: [Windows 11]
Browser [Chrome]

Additional context
Add any other context about the problem here.

it will do this for like 20 seconds then start working, the problem is i tried using this account with another one then i notced it will get the rare limited or discord something  and it will wait like 20 seconds then  I got captcha.

I think it's working now not sure..

Eh.. i will just close issue i changed the timing of hunting and i think it's better? weird.....


NEW Add afterUpdateCMSFields method to DataObject. Fixes #9797

Adds afterUpdateCMSFields method to DataObject as discussed in #9797

I thought all extension points executed a before and after hook automatically?

Extensible::extend`` does execute callbacks that have been added to the protected beforeExtendCallbacksandafterExtendCallbacksproperties, which from what I can tell can only be added to using the protectedbeforeExtendingandafterExtendingmethods, or via any methods that take advantage of those such asDataObject::beforeUpdateCMSFieldsand this pull request'sDataObject::afterUpdateCMSFields`.
I can't see, neither in the code nor documentation, any automagic before or after hook calls but if I've just glanced over it I'd be happy to be wrong.

beforeUpdateCMSFields() was never really needed IMO... but does make it a little more accessible. You can just do...
function getCMSFields()
{
    $this->beforeExtending('updateCMSFields', function ($fields) {
         // same code as beforeUpdateCMSFields()
    });

    $this->afterExtending('updateCMSFields', function ($fields) {
        // ...
    });

    return parent::getCMSFields();
}

@christopherdarling Those methods are great if you're actually inside a DataObject already, but as I mentioned in #9797

unfortunately afterExtending is a protected method, so I don't have access to it from an Extension. The shortcut method would expose it to extension classes as a public method, basically the same as the beforeUpdateCMSFields method.

Ah, sorry I missed that! For what it's worth, I think adding this would be useful 👍
Perhaps opens a wider discussion on whether before/afterExtend should be public methods?

@emteknetnz Yup. I'm not sure if I'm meant to do anything or not though... waiting for @sminnee to respond.


Include available payload from Rails' Rollbar into browser JS's Rollbar

I was trying to move Rollbar JS config from an HAML template to Rails' Rollbar JS config and I realized that, contrary to what I thought, neither the environment nor the person data that comes in the server-side errors payload isn't available in browsers JS errors. Unfortunately, I can't define person data payload in the Ruby config file as it only runs once when the app boots up and not in every request.
I guess I'll have to keep the HAML template meanwhile, but I'd really like to move to the Ruby config file as it looks cleaner.
Thanks!

Hi @esaborit4code,
we added automatic support for the persona data in the rollbar.js integration with the gem in this PR https://github.com/rollbar/rollbar-gem/pull/602. It was merged and released few weeks ago, you can check the changelog https://github.com/rollbar/rollbar-gem/blob/master/CHANGELOG.md#2150.
You should ensure that you are using the version 2.15.0 of the gem. If you are indeed using it we would appreciate a bit more of information of the problem so we can fix the bug.

Hi @jondeandres, thanks for such a quick response!
It totally was my fault, I thought I was logged in but I wasn't, so that's why I couldn't see any person data! I'm sorry! 😅
Anyway, I've also found some other issues while moving to the Rails config file:

Payload's environment isn't set and I think it makes sense for it to be the same as Rails Rollbar environment. Now I'm setting it manually (not a big problem as it isn't dynamic).
I also used to include the request controller and action in the payload, now I can't. I think that it could be solved using Procs that get run in controller's context. It would look like this:payload: {
  controller: proc { params[:controller] },
  action: proc { params[:action] }
}

If you think that would be cool, I can try to make some pull requests.
Thanks again!


Add support for RESTful JSON APIs access tokens and OAuth2.0 For Login

This commit adds a new submodule feature 'access_token', it is intended
for RESTful JSON APIs, it allows rich client-side applications to use
access tokens to communicate with the backend server.
It also adds support for OAuth 2.0 For Login - Implicit Grant Flow -.

So, why this request was not accepted?

@slava-nikulin it got caught up in a rollover between maintainers in 2014 I believe. If @fzagarzazu wants to rebase it, I can take a look.


Updating readme from branch example

Updates
I updated the readme file. Please review and accept.

Thoughts
I probably shouldn't, but okay :+1:


Increase the size of the toolbar depending on the uidensity (bug 1171799)

/botio-linux preview

There might be other issues as well, but quick testing revealed the following.
It seems that, when manually setting the compact density, the buttons in the secondaryToolbar will overflow the toolbar-element at the bottom; this is easily visible when zoom-in on the following screen-shot.

It should be fixed now. My devtools are on the right side... so I would have been enabled to see this bug.


FRQ Connections to PBL + Reflection

Show how FRQs or principles of FRQs are incorporated into to your final project.
FRQ 1: Arrays/Array List

This FRQ was testing understanding of how to use 1D and 2D arrays in the context of iterating through them, accessing the elements, and using nested loops and conditional statements to reach the desired outcome (check whether or not elements of an array are diverse). For my group's cybersecurity educational game website, the code below functions to retrieve all game sessions for the particular game, calculate the minimum session time for each user, and return a sorted leaderboard that ranks each user by how fast they were able to complete the game.

In our code we did not explicitly use 1D or 2D arrays; however, we did use Lists and Maps in the context of Java Streams that conceptually reflect principles similar to working with 1D arrays. The List<Gamesession> sessionList serves as a collection, analogous to a 1D array, containing game session data. The iteration through the sessionsByUId Map involves traversing the keys (user IDs) and their associated values (lists of game sessions), similar to iterating through a 1D array and accessing its elements. We also did use a nested for loop for each user iterates through a list of game sessions (gList) and used a conditional if statement within this loop to check for the minimum session time.
One integral part of this code that deviates from college board knowledge was our decision to use a tuple (Tuple2<Long, Double>) (which I learned is a built-in data type that allows you to create immutable sequences of values) since it allowed us to pair user IDs with their corresponding minimum session times in an organized bundled manner.
FRQ 2: Classes

This FRQ was all about knowing what are the necessary components for a Java class which include the private instance variables, constructors, and main method. In our PBL we used this framework for many different features but most prominently we used it for the login feature. In the code segment below we declared the public class Person that holds information on their user ID, birthday, and two strings for their email and password.

Here we can see the use of a parameterized constructor that holds all of this user information to build object from the API. A custom getter method is also used to return the age of user after doing calculations from their date of birth input

I would say that the anatomy of our Person class is quite standard to other login systems with the use of some variables, constructors, and getter methods.
FRQ 3: 2D Array

This FRQ introduced the idea of sparse arrays to me. For my own understanding in simple words, I see it as a big matrix with mostly 0s and in order to not bother with all that memory you just track the nonzeros (the picture below really helped me visualize). I believe its main function is to efficiently represent and store arrays where the majority of elements have a default value.

In our project, we have not explicitly implemented any sparse or 2D arrays. However, I believe we could implement it when we complete our "spot the difference" game for phishing attack emails. When the game displays two similar images and the player's task is to identify the differences between them, we can represent these images using a 2D array of pixels. Further, as the player advances to higher levels and there are only a few differences between the two pictures we can use a sparse array to optimize storage! It could work something like this:
# Using a dictionary to represent a sparse array
sparse_difference = {
    (1, 3): 0  # (row, column): value
    # ... other differences
}

When the player points to a location (row, column) and claims there's a difference, you can check their input against the sparse array.
def check_difference(player_input, sparse_difference):
    return player_input in sparse_difference

FRQ 4: Methods & Control Structures

For this one I was a bit confused on what differentiates this type of FRQ from the classes type FRQ because it seemed to just have me go through the same process of building a class, initializing instance variables an constructors, and using iterative statements to achieve the goal of figuring out if an integer was in a NumberGroup. After some google searching I learned that one way to see a difference is that: A class can implement multiple interfaces, but it can only extend a single class. If you need a class to inherit behavior from multiple sources, interfaces provide a way to achieve this.
In our project, we definitely used a public interface for the log in feature, but I thought I should highlight the use of "public interface Link extends JpaRepository<Template, Long>" in my feature that mimics when in the FRQ I did "Range implements NumberGroup". My feature was about taking user input of what kind of operating system they had and then displaying useful information about how to combat certain vulnerability issues they were facing.

Here, the code segment above showcases the use of method control structures in the context of a Spring Data JPA repository interface (Link). It extends a generic repository interface (JpaRepository) to inherit standard CRUD operations and includes a custom query method for fetching data based on the operating system name. I think this is a pretty standard way that shows the way inheritance can lead to greater code efficiency.
Overall Reflection on FRQ & PBL

Number one takeaway: By going through this process of completing each FRQ and contemplating how the learning targets are reflected in my own group's project, my number one takeaway is that although the exact same type of data structure may not have been used, there are underlying principles and more abstract concepts that are easily comparable across many different files. For example, our project may not have explicitly used 2D arrays, but I can see that we stored information, iterated through them, and manipulated the elements to achieve a certain outcome using Lists and Maps or Tuples. I think that when I try to learn a subject I tend to gravitate towards just memorizing an exact step to step tutorial of how to solve a problem, but for computer science, I definitely believe that if you take the time to truly understand the big picture logical theories of how to handle data, figuring out what data structure or method will come with time.

What I have proficiency in: I believe that I have become pretty familiar with how to build a class and all the details within such as when to declare private or public, initializing instance variables and constructors, using getter and setter methods, and a main method for testing (FRQ 2). Also I think that I have come to understand the simple manipulation of 1D and 2D arrays through the use of iterative statements (for, while, enhanced for loops, backwards loops) and pointers when wanted to compare 2 different values within an array (FRQ 1).

What I need to work on: What really stumped me the most was FRQ 3 because at first I was just totally miffed on what even is a sparse array. I definitely think when it comes to college board FRQs that provide more given code and ask to fulfill multiple conditions, I need to take the time to thoroughly annotate each condition I need to address and to just really understand what it is asking me to do before immediately coding. I found it helpful for myself to just jot down what a sparse array is in my own words (a big matrix w/mostly 0s and to not bother with all that memory you just track the nonzero) so I can better comprehend how to even start coding.

Plans for trimester 3 : As the AP exam is approaching, I want to follow this schedule: take a year's FRQ on Saturday, reflect and take notes on what I learned on Sunday, and then spend Monday-Friday working on school assigned work and drawing parallels from the FRQs I just worked on. In this way, I can ensure that I truly grasp the abstract concepts by implementing them in my PBL assignments which will not only prepare me for the exam, but also allow me to improve my actual coding efficiency and tool kit for my computer science journey in college and beyond.

4/4 Cool Project


catt errors on Python 3.10 (Arch)

When trying any subcommand with catt (e.g. scan or cast_site) I get the following error:
$ catt scan
Scanning Chromecasts...
Traceback (most recent call last):
  File "/usr/bin/catt", line 33, in <module>
    sys.exit(load_entry_point('catt==0.12.1', 'console_scripts', 'catt')())
  File "/usr/lib/python3.10/site-packages/catt/cli.py", line 644, in main
    return cli(obj=get_config_as_dict())
  File "/usr/lib/python3.10/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3.10/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3.10/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3.10/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/catt/cli.py", line 483, in scan
    devices = get_cast_devices_info()
  File "/usr/lib/python3.10/site-packages/catt/discovery.py", line 65, in get_cast_devices_info
    devices = get_cast_devices()
  File "/usr/lib/python3.10/site-packages/catt/discovery.py", line 50, in get_cast_devices
    devices = [
  File "/usr/lib/python3.10/site-packages/catt/discovery.py", line 51, in <listcomp>
    CastDevice(pychromecast.get_chromecast_from_cast_info(c, browser.zc), c.host, c.port) for c in cast_infos
  File "/usr/lib/python3.10/site-packages/pychromecast/__init__.py", line 69, in get_chromecast_from_cast_info
    return Chromecast(
  File "/usr/lib/python3.10/site-packages/pychromecast/__init__.py", line 272, in __init__
    cast_info = get_cast_type(cast_info, zconf)
  File "/usr/lib/python3.10/site-packages/pychromecast/dial.py", line 121, in get_cast_type
    status = _get_status(
  File "/usr/lib/python3.10/site-packages/pychromecast/dial.py", line 78, in _get_status
    host, _, _ = get_host_from_service(service, zconf)
  File "/usr/lib/python3.10/site-packages/pychromecast/dial.py", line 38, in get_host_from_service
    service_info = zconf.get_service_info("_googlecast._tcp.local.", service.data)
  File "/usr/lib/python3.10/site-packages/zeroconf/_core.py", line 523, in get_service_info
    if info.request(self, timeout, question_type):
  File "/usr/lib/python3.10/site-packages/zeroconf/_services/info.py", line 455, in request
    assert zc.loop is not None and zc.loop.is_running()
AssertionError

The versions used are:

Python 3.10.1
catt v0.12.1, Zaniest Zapper.
OS ManjaroLinux - catt installed from aur - https://aur.archlinux.org/packages/catt/

Looks similar to the already closed issue #349

Yes, sounds like the same bug, can you try the latest version and see if that solves it?

When switiching to catt-git (https://aur.archlinux.org/packages/catt-git) it reports the following version:

catt v0.12.5, Zaniest Zapper.

However the problem still exists - its the same stacktrace as above

Hmm, what's the PyChromecast version?

It's aur/python-pychromecast 10.2.2-1

That's the wrong version, please either use one of the supported methods of installation or file a bug with AUR.

@skorokithakis I am having the same issue. What is the required python-pychromecast version?


PayloadAttributes struct fields are not public

Is there a reason why the fields of PayloadAttributes are not public?
https://github.com/ralexstokes/ethereum-consensus/blob/72800f5e4cc28ad384f9cc7639d19da8dab50fb0/beacon-api-client/src/types.rs#L310-L322

#390

its yours!


os-iperf web gui fails to render when result contains error (eg, due to iperf2 client)

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] The title contains the plugin to which this issue belongs

Describe the bug
The web UI for iperf can crash and fail to render both open iperf instances and results. A JS TypeError is logged:
Uncaught TypeError: Cannot read properties of undefined (reading 'time')
    at result_to_html (iperf:1278:59)
    at callback (iperf:1317:9)
    at Object.complete (opnsense.js?v=e65c3d146db5fcd1:272:21)
    at c (jquery-3.5.1.min.js?v=e65c3d146db5fcd1:2:28294)
    at Object.fireWith (jquery-3.5.1.min.js?v=e65c3d146db5fcd1:2:29039)
    at l (jquery-3.5.1.min.js?v=e65c3d146db5fcd1:2:79928)
    at XMLHttpRequest.<anonymous> (jquery-3.5.1.min.js?v=e65c3d146db5fcd1:2:82254)

The failing line is output += table_tr_kv("Time", start.timestamp.time);
The JSON payload looks something like:
[
    {
        "start_time": "2024-04-20 14:12:10 +0000",
        "interface": "vtnet0",
        "port": 5830,
        "result": {
            "start": {
                "connected": [],
                "version": "iperf 3.16",
                "system_info": "FreeBSD OPNsense.localdomain 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 stable\/24.1-n255007-1d6e165fb40 SMP amd64"
            },
            "intervals": [],
            "end": [],
            "error": "error - unable to receive parameters from client: "
        }
    },
    {
        "start_time": "2024-04-20 14:14:54 +0000",
        "interface": "vtnet0",
        "port": 36726
    },
]

The problem is that an errored-out result does contain a start block, but that start block doesn't contain a valid timestamp.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:

Go to 'http://<IP_ADDRESS>/ui/iperf'
Click on 'Create Instance'
An iperf server instance is created and a port is shown
Connect to the specified port using an iperf2 client
An error occurs due to the mismatch in client version (iperf2) and server (iperf3) - I think
Web ui no longer renders iperf instances or results

Expected behavior
Even if errors occur, the web ui should not crash and should display errors as best as possible.
Screenshots
Not really useful, hard to screenshot something that's just missing in the UI.
Relevant log files
See above.
Additional context
I believe it's a common mistake to use an iperf2 client. For example, on both Mac and Debian Linux, installing iperf via brew install iperf or apt install iperf installs iperf2. It's not obvious that OPNSense's os-iperf plugin is iperf3, nor that the version incompability causes an irrecoverable crash (in the web ui).
This ticket seems to be very similar: https://github.com/opnsense/plugins/issues/3545
This ticket describes that iperf2 and iperf3 clients can be incompatible: https://github.com/esnet/iperf/issues/530. Regardless, the web ui should display errors better.
Environment
Software version used and hardware type if relevant.
OPNSense 24.1.6-amd64
os-iperf 1.0_1
iperf 3.16

I've raised a simple PR to fix this: https://github.com/opnsense/plugins/pull/3928
It renders the error instead of trying to render the result.

I've already "stepped up and worked on" this issue :(
It's a pretty simple PR, are there any maintainers that can have a look?

Sorry, nobody responded (was hoping for maintainer feedback) but things happen. Appreciate the ping :)


Grammatical error in file deletion dialogue.

VSCode Version: 1.41.1
OS Version: win10 x64 1909

Steps to Reproduce:

Create A File Through VS Code
Delete Said File
MAKE SURE TO ADD TEXT AND SAVE BEFORE DELETION

Expected result:
The dialogue box description Should say "You Can Restore This File (these files) from the recycle bin."
Actual Result:
The dialogue box description says "You can restore from the recycle bin."

Does this issue occur when all extensions are disabled?: yes

Can you follow the steps here to get crash logs for us? https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#windows
/needsMoreInfo


How to resolve exports from gts files as imports in ts files to prevent import-x/no-unresolved

Hi, we have an Ember app written in TypeScript.  We use the import-x plugin and the new eslint flat file config and everything has been working fine. We have updated our app to use the Ember Template Tag format and since then a pure TypeScript file in say the app/lib folder cannot resolve an import from a component in .gts format.
Example code;
// appname/app/components/app/animation-dropdown/index.gts
export interface AnimationOptions {
  [key: string]: AnimationOption;
}

// appname/app/lib/timeline/element.ts
import type { AnimationOptions } from "client/components/app/animation-dropdown/";  // errors in linting with import-x/no-unresolved

I have tried various incantations of resolving and parsers and what not but nothing has worked.
What is a configuration in settings: {} that should in theory at least work and have import-x resolve the imports?
I have seen conversation in a different thread about dropping the concept of resolvers which makes me think what I am trying to do should work?
Here is an example snippet from our eslint.config.mjs
import globals from "globals";
import eslint from "@eslint/js";
import eslintPluginEmber from "eslint-plugin-ember";
import eslintPluginEmberRecommended from "eslint-plugin-ember/configs/recommended";
import eslintPluginImportX from "eslint-plugin-import-x";
import typescriptEslint from "typescript-eslint";
import eslintPluginPrettier from "eslint-plugin-prettier";
import eslintPluginPrettierRecommended from "eslint-plugin-prettier/recommended";
import eslintNode from "eslint-plugin-n";
import emberEslintParser from "ember-eslint-parser";

export default [
  eslint.configs.recommended,
  ...eslintPluginEmberRecommended,
  eslintPluginPrettierRecommended,
  eslintPluginImportX.flatConfigs.recommended,
  eslintPluginImportX.flatConfigs.typescript,
  {
    files: ["**/*.ts"],
    plugins: {
      ember: eslintPluginEmber,
      "@typescript-eslint": typescriptEslint.plugin,
      prettier: eslintPluginPrettier,
      import: eslintPluginImportX
    },
    languageOptions: {
      globals: {
        ...globals.browser,
        ...globals.node
      },
      parser: typescriptEslint.parser,
      parserOptions: {
        ecmaVersion: "latest",
        sourceType: "module",
        projectService: true,
        tsconfigRootDir: import.meta.dirname
      }
    },
    settings: {
      "import-x/extensions": [".ts", ".gts", ".js", ".cjs", ".mjs"],
      "import-x/parsers": {
        "@typescript-eslint/parser": [".gts"]
      },
      "import-x/resolver": {
        typescript: {
          alwaysTryTypes: true
        },
        node: {
          extensions: [".js", ".ts"],
          moduleDirectory: ["node_modules", "app"]
        }
      }
    }
  }
]

Based on snippets around the web about the various plugins etc I have tried various incantations of parsers, eg setting the configuration parser to the emberEslintParser or using that in settings like;
"import-x/parsers": {
  "ember-eslint-parser": [".gts"]
}

But nothing seems to make import-x scan .gts files for exports.
Is it possible?
What might a configuration look like?

Please try https://github.com/import-js/eslint-import-resolver-typescript?tab=readme-ov-file#extensions

Thank you I have already tried;
settings: {
  "import-x/extensions": [".ts", ".gts"]
}

and it did not work.
Should the setting be extensions or "import-x/extensions"?

It's not import-x/extensions setting, it's eslint-import-resolver-typescript's option, they are different.

eslint-import-resolver-typescript should be able to resolve ember template files. Closing.


Problem: Task Template ARGS Tags Not Working

Issue
Using --tags in 'Args' section in Task Templates causes job to fail
Impact
Web-Frontend (what users interact with), Ansible (task execution)
Installation method
Package
Database
BoltDB
Browser
Firefox
Semaphore Version
2.10.22-e44910d-1721658299
Ansible Version
No response
Logs & errors

Manual installation - system information
nginx
Configuration

Additional information
Adding the arg --check to the task template seems to work but --tags does not. Running the playbook from the commands line with --tags works as expected.

Hey,
it's working for me with the Arg "-t users".

Same issue here, using -t works but I would also like to use --skip-tags

Agree. The old style of specifying additional args as json array seemed to work without issue. The new UI for specifying additional args seems limited.

Hi all, thank you! Fix be fixed soon.

What if try --tags=users.

What if try --tags=users? Or you should use 2 items --tags, users.

Thanks for the tip. Separating args for '--tags' and tag name does work as expected. I guess it is just a misunderstanding on how args need to be used in the UI?
Screenshot shows working tags as recommended:

I can confirm that --tags=users also works.

Hi @fiftin, do you have an ETA for fixing this? Once fixed, it'll unlock wonderful things for us... at the moment we have to duplicate dozens of playbooks...! Thanks

I can confirm that --skip-tags and  as individual entries just works as if executed in CLI.
This probably needs to be communicated more exactly.


OCPCLOUD-1675: Add support for generic platforms without failure domains

This PR allows CPMS to manage control plane machines on all platforms that do not require modification of machine spec for failure domains.
It does so by creating a generic provider config that contains the spec as RawExtension to allow us to compare machine spec to template spec.
I've also added resourcebuilder for VSphere for use in test as an example of platform without failure domains.

Fixed lint

/lgtm


Design proposal for variadic generics

Closes #4825.

I've done the review.
It looks good to me now, only few nit-picks left.


Subtract blending is inverted

BYOND does src - dst, not dst - src.
https://github.com/OpenDreamProject/OpenDream/blame/a3dcd596ff1db5cc06299fe1eee8ce3ebd679fd5/OpenDreamRuntime/Objects/DreamIcon.cs#L317

In that code dst represents the icon being blended onto, and src is where the color is coming from.
icon1.Blend(icon2, ICON_SUBTRACT)
icon2 would be src here and icon1 is dst. My testing in BYOND is showing that it does icon1 - icon2 which makes the current code correct.

Oh? My interpretation was backwards then. Apologies. When I ported this logic to Rust I assumed src was the icon being blended onto.


Cant Configure the form of the status bar

Yo! i just installed this, and when i opened neovim (not vim), the status bar looked like this:
| NORMAL | [No Name]                                                 | [unix] | etc..
what i want to know, is how do i make the ends of every item on the status bar look like in the screenshots where the end is triangular.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


2455582.yml can be removed.

The topic of this SAP note (GCC 6.x) is already covered completely by vars/RedHat_7.yml. And RHEL 8 comes with GCC 6 compatibility.

Also remove this note from the __sap_hana_preconfigure_sapnotes variable in vars/RedHat_7.yml.


Hardware/README.md : correct reference to action_examples/memcopy

Several times appears reference to ACTION_ROOT=$SNAP_ROOT/hardware/action_examples/memcopy
which doesn't exist anymore. Can you please correct it?
I guess it should be $SNAP_ROOT/hardware/action_examples/hdl_example
thx

The fixes are in branch jsv_README

Sounds ok. Thx


test_environment with gymnasium

test_env.py is the new environment compatible with SingleAgent wrapper and gymnasium. register_test.py is the test file.

This is already addressed.


Refactor verification options

This refactors all verification options to common documentation in openssl.pod
I also rewrote the prose text about how verification works.
I'd like #10118 to get reviewed and merged first because the options that control the trust chain (no-cafile, etc) affect this and I can add the necessary L<> link.

I did some editing on the verification options in openssl.pod, and I tried to put them into a more sensible ordering.  Once this is reviewed and merged, I will change OPT_V_OPTIONS
in include/opt.h to match the ordering.

This is now based on #10159 and needs that to go in first.

Rebased since #10159 was merged.

re-pushing to restart hung CI jobs.

rebased and fixed conflicts.

Thanks for reading this, @vdukhovni I appreciate it.  Fixup commit pushed.

I had to rebase because of a conflict.  I fixed various failure descriptions and moved the verification error description all to the man3 file.  That file now has the define name and the text.  Should the text, which is basically a repetition of the text description, be removed? I think so.

Travis failure is a timeout.

I restarted the job.

Ping for a second review.  Should be easy, it made it past one of the harder reviewers already :)  And #10587 is kinda waiting on this.

There were conflicts, so I did a squash/rebase.  The conflicts were simple, but this probably needs another review from @vdukhovni (as well as a committer).

I generated the pod files using 8062c027e9cdef644f1e63b210384e760c65a354 and its parent, see attached comparison.zip. For better comparison I sorted the options in the SYNOPSIS section.
The diff shows some duplicates (-CAfile, -CApath, -certfile) and some options which have disappeared (-no_check_time) or appeared (-verbose). I think the duplicates need to be removed and the other changes need a closer look and/or an explanation why they were changed.
See for example openssl-cms.pod:
msp@msppc:~/src/openssl$ diff before/openssl-cms.pod after/openssl-cms.pod
--- before/openssl-cms.pod	2020-01-06 16:25:32.978669176 +0100
+++ after/openssl-cms.pod	2020-01-06 16:26:16.407071393 +0100
@@ -15,6 +15,8 @@

 B<openssl> B<cms>
 [B<-CAfile> I<file>]
+[B<-CAfile> I<file>]
+[B<-CApath> I<dir>]
 [B<-CApath> I<dir>]
 [B<-CAstore> I<uri>]
 [B<-EncryptedData_encrypt>]
@@ -25,6 +27,7 @@
 [B<-binary>]
 [B<-cades>]
 [B<-certfile> I<file>]
+[B<-certfile> I<file>]
 [B<-certsout> I<file>]
 [B<-check_ss_sig>]
 [B<-cmsout>]
@@ -56,10 +59,11 @@
 [B<-keyopt> I<name>:I<parameter>]
 [B<-md> I<digest>]
 [B<-no-CAfile>]
+[B<-no-CAfile>]
+[B<-no-CApath>]
 [B<-no-CApath>]
 [B<-no-CAstore>]
 [B<-no_alt_chains>]
-[B<-no_check_time>]
 [B<-noattr>]
 [B<-nocerts>]
 [B<-nodetach>]
@@ -102,6 +106,7 @@
 [B<-trusted_first>]
 [B<-uncompress>]
 [B<-use_deltas>]
+[B<-verbose>]
 [B<-verify>]
 [B<-verify_depth> I<num>]
 [B<-verify_email> I<email>]
@@ -476,14 +481,16 @@

 =item B<-attime>, B<-check_ss_sig>, B<-crl_check>, B<-crl_check_all>,
 B<-explicit_policy>, B<-extended_crl>, B<-ignore_critical>, B<-inhibit_any>,
-B<-inhibit_map>, B<-no_alt_chains>, B<-no_check_time>, B<-partial_chain>, B<-policy>,
+B<-inhibit_map>, B<-no_alt_chains>, B<-partial_chain>, B<-policy>,
 B<-policy_check>, B<-policy_print>, B<-purpose>, B<-suiteB_128>,
 B<-suiteB_128_only>, B<-suiteB_192>, B<-trusted_first>, B<-use_deltas>,
 B<-auth_level>, B<-verify_depth>, B<-verify_email>, B<-verify_hostname>,
 B<-verify_ip>, B<-verify_name>, B<-x509_strict>

-Set various certificate chain validation options. See the
-L<openssl-verify(1)> manual page for details.
+Set various options of certificate chain verification.
+See L<openssl(1)/Verification Options> for details.
+
+Any verification errors cause the command to exit.

 =item B<-CAfile> I<file>, B<-no-CAfile>, B<-CApath> I<dir>, B<-no-CApath>,
 B<-CAstore> I<uri>, B<-no-CAstore>

Note: I did not go through all the diffs yet.

The duplicates (CApath,no-CApath,CAfile,no-CAfile,certfile) where rebase mistakes that slipped through; fixup commit pushed.  The no_check_time isn't implemented so I removed it.  As you go through the review, I'll fix each one in turn.  Thanks!

The no_check_time isn't implemented so I removed it.

Are you sure it's not implemented?
$ git grep -in no_check_time apps
apps/include/opt.h:30:         OPT_V_PARTIAL_CHAIN, OPT_V_NO_ALT_CHAINS, OPT_V_NO_CHECK_TIME,
apps/include/opt.h:82:         { "no_check_time", OPT_V_NO_CHECK_TIME, '-', "ignore certificate validity time" },
apps/include/opt.h:115:         case OPT_V_NO_CHECK_TIME:
apps/lib/opt.c:608:     case OPT_V_NO_CHECK_TIME:
apps/lib/opt.c:609:         X509_VERIFY_PARAM_set_flags(vpm, X509_V_FLAG_NO_CHECK_TIME);

Thanks @mspncp you're right.  Lucky a simple fix in only one file fixes it everywhere :)

-no_check_time
Did you restore -no_check_time already?
More duplicates
I see more duplicates of the following options:
-CAfile, -CApath, -no-CAfile, -no-CApath

I'm sure you'll find them all using grep ;-)
Verbosity
The -verbose option was somehow 'inverted': it is now documented where it previously wasn't and vice versa.
msp@msppc:~/src/openssl$ grep -- -verbose before/*
before/openssl-verify.pod:[B<-verbose>]
before/openssl-verify.pod:=item B<-verbose>

msp@msppc:~/src/openssl$ grep -- -verbose after/*
after/openssl-cms.pod:[B<-verbose>]
after/openssl-ocsp.pod:[B<-verbose>]
after/openssl-s_client.pod:[B<-verbose>]
after/openssl-s_server.pod:[B<-verbose>]
after/openssl-smime.pod:[B<-verbose>]
after/openssl-ts.pod:[B<-verbose>]

According to my quick test, none of the latter commands supports this flag:
msp@msppc:~/src/openssl$ for cmd in cms ocsp s_client smime ts; do openssl $cmd -verbose ; done

cms: Unrecognized flag verbose
ocsp: Unrecognized flag verbose
ocsp: Use -help for summary.
s_client: Option unknown option -verbose
s_client: Use -help for summary.
smime: Unrecognized flag verbose
smime: Use -help for summary.
ts: Unrecognized flag verbose
ts: Use -help for summary.

Apropos: the missing-flag error messages are also very higgledy-piggledy:
cms: Unrecognized flag verbose
ocsp: Unrecognized flag verbose
ocsp: Use -help for summary.
s_client: Option unknown option -verbose
s_client: Use -help for summary.
smime: Unrecognized flag verbose
smime: Use -help for summary.
ts: Unrecognized flag verbose
ts: Use -help for summary.

Could you open a separate issue for https://github.com/openssl/openssl/pull/10132#issuecomment-571358064 ?  Thanks.

Could you open a separate issue for #10132 (comment) ? Thanks.

Done, see #10773.

-no_check_time
Did you restore -no_check_time already?

Yes but I didn't push waiting for your other feedback.

More duplicates
...
-CAfile, -CApath, -no-CAfile, -no-CApath

I found them in ocsp, s_time, smime, ts, and verify manpages.

I'm sure you'll find them all using grep ;-)

Hope so :)

Verbosity

I removed the -verbose flag from the synopsis (which is the only place it appeared) from cms, ocsp, s_client, s_server, smime, and ts manpages.
Thanks for your attention to detail!  BTW, you might find "find-doc-nits -c" interesting.  And issue #9730

Rebased to address conflicts after #10128 was merged.

The Travis failure is relevant.

Fixed; typo was in doc/perlvars.pm

Lost and Found
I feel a little bit dizzy after chasing all those options which have moved around and checking whether no ~sheep~ options got lost. In particular those options which were moved into openssl.pod are hard to track. (Which doesn't mean at all that I dislike your idea to collect these common options in a common place. On the contrary, I think it's a very good thing to do.)
The following diff shows a comparison of the sorted options of the respective SYNOPSIS section. Please be so kind and check the diffs once more. Some changes are ok, because only the name of the option arg has changed.  For example it is suprising that the 'Extended Verification Options' precede the 'Verification Options'.
Please take a closer look:
doc/man1/openssl.pod:496:=head1 OPTIONS
doc/man1/openssl.pod:501:=head2 Common Options
doc/man1/openssl.pod:519:=head2 Format Options
doc/man1/openssl.pod:622:=head2 Pass Phrase Options
doc/man1/openssl.pod:668:=head2 Trusted Certificate Options
doc/man1/openssl.pod:722:=head2 Random State Options
doc/man1/openssl.pod:752:=head2 Extended Verification Options
doc/man1/openssl.pod:797:=head2 Verification Options
doc/man1/openssl.pod:1037:=head2 Name Format Options
doc/man1/openssl.pod:1187:=head2 Engine Options

Ping for a second review. Should be easy, it made it past one of the harder reviewers already :)

LOL. You didn't expect me, did you?

Do you know the term "nerd snipe" ? :)

The sub-section issue I put into its own issue, #10809

Do you know the term "nerd snipe" ? :)

You previously about it. But now I know why I felt so dizzy...

Whew!  Changes made

s_client has no -certfile option, re-removed it (was in perlvars.pm)
s_server has no -certfile option, re-removed it (was in perlvars.pm) allow_proxy_certs and issuer_checks were moved into perlvars.pm (so they shows up in several commands now). Confirming that the argument names for attime, authlevel, engine, policy, purpose, verify_{depth,email,hostname,ip,name} changed.
ts.pod.in verifying that the argument names for CAfile,CApath,CAstore, changed. Removed -certfile (was in perlvars.pm) and restored -untrusted
verify Similar changes to s_server; also added missing show_chain, sm2-id and sm2-hex-id, verbose, trusted, untrusted

Using ./util/find-doc-nits -c to add missing options is the planned subject of a separate PR.  (I think the perl script needs some work)

Rebased to fix conflicts in s_client,s_server POD pages.

@richsalz your pr is not forgotten. I had (resp. have) some busy days, not sure when I will get around to finish the review.

Travis Errors are relevant:
doc/man1/openssl-verify.pod around line 16: Unterminated B<B<...>> sequence
POD document had syntax errors at /usr/bin/pod2man5.18 line 72.
make: *** [doc/man/man1/openssl-verify.1] Error 255

YAF pushed.

BTW, @mspncp I am not worried about your review -- once you start, you don't let go :)

YAF pushed.

Young Adult Fiction?
Youth Arts Foundation?
Yet Another Fotoalbum?
Young Americans for Freedom?
Yugoslav Air Force?

Just too many possibilities...

Context is all: Yet Another Fixup

Context is all: Yet Another Fixup

You didn't get to see the tooltip, did you?


Implement a linker for SPIR-V modules?

Hello,
I have been working on a SPIR-V linker for Mesa, and thought that maybe it could live in SPIRV-Tools instead; I would then just link SPIRV-Tools to Mesa, like I already do to get the SPIR-V validator.
Would you be interested in having a linker here? (Or in SPIRV-LLVM, whichever place is the best fit for it.)

Yes.  We'd be very interested in adding a linker to SPIRV-Tools.
A few of us have done an 90% job in a short time, but never got all the way to 100%.
It ought to reuse basic things like the binary parser.

Is the code for any of those attempts available somewhere?
I have some code that does most of the job, but it does not remove names/types/decorations used by imported declarations, yet. This is only problematic for types, as the validator complains that some types are not the same, due to having different IDs.
I’ll try to reuse as much as I can.
As always, remember the validator is not complete.   :-)
I'll still review carefully but will definitely be happy to review work-in-progress.

I don't think I've prototyped one... Or apparently I cannot find it anywhere.
I remember @AWoloszyn's implementation is based on Golang?

Closing as this can be tracked in #693 now.


perf(table): Use only one column classname and do string interpolatio…

…n once per column
In the "Table with sticky headers, footers and columns" example which has 10 rows, this roughly halves time spent on computing and adding these classes (3.5ms -> 1.8ms), but for tables with more rows/columns the effect is worthwhile.
This is potentially a slightly breaking change as there could be apps using MatTable that are depending on the Cdk classes for something.

Leaving merge-ready for @andrewseguin

The biggest change here comes from only adding one css class instead of 2, but spread across thousands of cells the concatenation has a small impact as well.

Sorry this took so long to get in. We likely ran into failures internally from this. If you'd still like to land it, feel free to reopen a new rebased PR and we can take another shot at it


More flexible batching for graph-level properties

🚀 Feature
It would be great if Data subclasses had more control over the batching behavior of properties that are not per-node. In particular, two features would be very useful:

The ability to concatenate some properties along a new batch dimension:

class MyData(Data):
    def __cat_dim__(self, key, value):
        if key == 'some_prop':
            return None
        else:
            return super().__cat_dim__(key, value)

# ...
N_data = 3
datas = [MyData(some_prop=torch.randn(4, 7)) for _ in range(N_data)]
batch = Batch.from_data_list(datas)
batch.some_prop.shape # => [N_data, 4, 7]

I think None is a reasonable choice for this value since it gives a new axis in numpy indexing.

The ability to keep, but exempt from batching, properties of the Data objects that are conceptually "batch-level" and can be taken once from any one of the individual Data objects in the batch:

class MyData(Data):
    def __cat_dim__(self, key, value):
        if key == 'some_prop':
            return False
        else:
            return super().__cat_dim__(key, value)

# ...
N_data = 3
datas = [MyData(some_prop=torch.randn(4, 7)) for _ in range(N_data)]
batch = Batch.from_data_list(datas)
batch.some_prop.shape # => [4, 7]
torch.all(batch.some_prop == datas[-1].some_prop) # => True

False might make sense here in the sense that it is saying to not concatenate, but there may be a better way of doing this.
Instead of explicitly using None and False, there could also be constants Batch.CAT_DIM_NEW and Batch.CAT_DIM_DISABLE, or something similar.
Motivation
For 1., if I have a per-graph target property that is not scalar (for example, a fixed-size [M, N] Tensor), it would be logically correct for this property to have dimension [M,N] in an individual Data object, but to have dimension [n_batch, M, N] in a Batch assembled from those Datas. Currently, to get this behavior, the property must be stored as [1, M, N] in the individual example and have __cat_dim__ of 0, which while workable is conceptually incorrect.
For 2., as I said in #2028,

In some cases, Data objects may contain per-graph fields that are known to be the same across the entire batch/dataset. In cases where the model code is aware of this and knows how to deal with a missing batch dimension for those fields, it would be nice to avoid constructing an unneeded full [n_batch, ...] set of copies.

In some such scenarios, the value of the property at any one of the individual Data objects should be taken and stored in the final Batch. This can be done by a custom collate function, but it would be nice if  torch_geometric supported it directly.

For 2., another option could be allowing a Data subclass to provide a list of "batch-level" properties outside of __cat_dim__ that will be treated separately, and perhaps optionally checked for consistency (checked that they are all equal across Datas in the batch, raising an error otherwise).

For 2., another option could be allowing a Data subclass to provide a list of "batch-level" properties outside of __cat_dim__ that will be treated separately, and perhaps optionally checked for consistency (checked that they are all equal across Datas in the batch, raising an error otherwise).

I think those are some great suggestions. Are you interested in contributing those?

I think None is a absolutely fine.
Not sure if this is really necessary. I would expect global attributes to be in dataset.global_attribute instead of in each individual data object.

I think those are some great suggestions. Are you interested in contributing those?

I think None is a absolutely fine.
Not sure if this is really necessary. I would expect global attributes to be in dataset.global_attribute instead of in each individual data object.

Sure!
My thinking for the second case was based around properties that may sometimes be per-graph, or sometimes per-dataset, depending on the dataset in question. In that case it seemed easier to me to have the information inside the Batch regardless so that the training loop doesn't need access to the Dataset object. It's easy when loading individual Data objects to do this in an efficient way, since they can each carry a reference to the single Tensor with the data, but this becomes suddenly memory inefficient when batching happens.
Still, I agree that this may be to specialized for inclusion in the library and may be better implemented by subclassing Batch and wrapping from_data_list. What do you think?

Sure!
My thinking for the second case was based around properties that may sometimes be per-graph, or sometimes per-dataset, depending on the dataset in question. In that case it seemed easier to me to have the information inside the Batch regardless so that the training loop doesn't need access to the Dataset object. It's easy when loading individual Data objects to do this in an efficient way, since they can each carry a reference to the single Tensor with the data, but this becomes suddenly memory inefficient when batching happens.
Still, I agree that this may be to specialized for inclusion in the library and may be better implemented by subclassing Batch and wrapping from_data_list. What do you think?

@rusty1s I've filed a draft pull request implementing the first feature along with a simple unit test. The test suite passes but it would probably be good if you could take a look and see if it changes the API in any problematic ways

@rusty1s I've filed a draft pull request implementing the first feature along with a simple unit test. The test suite passes but it would probably be good if you could take a look and see if it changes the API in any problematic ways

Closed by #2036


HP Dock Audio

Hi
I cannot exclude the App "HP Dock Audio". Do you know why?
Regards,
Sergio

Post log so I can see what's going on please. They're in C:\BRU by default.
Thanks!

Here the Log:
Bloatware-Removal-26-Jun-2020-11-25.log

Thanks for the log. You can put quotes around items that have spaces in them so they will be excluded properly. This way of doing it with | separators between items may work better too:
powershell.exe -noprofile -executionpolicy bypass -file .\Bloatware-Removal-Utility.ps1 -s -exclude "keyboard|driver|HP Universal Camera Driver|HP Hotkey Support|HP Wireless Button Driver|HP Dock Audio" -includelast "HP Client Security Manager|HP Support Assistant" -norestorepoint -rebootafterremoval

i've tried it. The exclusion is not working. it wants to uninstall the HP Dock Audio. :(

Ok I'll look into it and try to repeat the issue.

Thank you for the support 👍

any news? :)

Still working on it. I know what I need to do now and will rewrite the match code. Holiday and family visiting delayed me a bit.

Perfect :) i was just curious if you found a solution. Enjoy your Holidays :D

Just a quick update on the progress of this fix: I'm rewriting the core matching code and making it easier to maintain/make changes. This is taking a while and I've got lots of testing to work out. When it is ready it should resolve the inconsistencies and fix unknown bugs with the cli include options.

I've pushed an updated version with fixes. Please let me know if you still have issues.
https://github.com/arcadesdude/BRU/releases/tag/09-20-2020


Cannelloni should be built with SCTP support

[x] Add SCTP support to cannelloni by including library in bundle and compiling with SCTP support
[ ] Update documentation:

[x] Installing SCTP is no longer required (Readme)
[ ] Check if licensing requirements are met (e.g. Sources.md)

[x] Check newly created binaries run on the following platforms (armv6, arm64, x64)
[x] Check if newly created binaries work for our setup

The architecture armv7 is currently untested due to lack of hardware with soft-float installation (raspbian is hardfloat).
The binary cangw from the debian package can-utils is still required to run EDGAR.

Add cannelloni source code to cannelloni package

Added source code to cannelloni package. Tested the following packages on the hardware:

cannelloni_linux-arm64-lts_1.1.0.tar.gz
cannelloni_linux-armv6-lts_1.1.0.tar.gz
cannelloni_manylinux_2_28-x64_1.1.0.tar.gz


Pipeline implementation of learning algorithm

Fixes #232
Fixes #177

Thanks Travis...
Removing the current learning tests, since they should be rewritten (see #226)

^ eh jk I'll just patch the current ones

Oy and I need to update the docs. Hang tight on this one

Adding @SenWu 's suggestion...
Fixes #237

Cool checking out this PR now
On Sun, Jun 12, 2016 at 10:23 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

Adding @SenWu https://github.com/SenWu 's suggestion...
Fixes #237 https://github.com/HazyResearch/ddlite/issues/237
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/ddlite/pull/236#issuecomment-225477190,
or mute the thread
https://github.com/notifications/unsubscribe/ABgw_WhqhmpWJuuTdKHM090V_OsmQlosks5qLL8MgaJpZM4Iz6wP
.

^ don't merge quite yet

Okay ping again when ready
On Sun, Jun 12, 2016 at 10:24 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

^ don't merge quite yet
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/ddlite/pull/236#issuecomment-225477321,
or mute the thread
https://github.com/notifications/unsubscribe/ABgw_WO0YqDbJ9ohZkjc_gmk2EvaqAReks5qLL94gaJpZM4Iz6wP
.

@ajratner ping good to go!

This ca. 1972 A320 that jetblue is flying doesn't have plugs, so may cut out suddenly

Sounds good will look at in a bit
On Sun, Jun 12, 2016 at 10:50 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

This ca. 1972 A320 that jetblue is flying doesn't have plugs, so may cut
out suddenly
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/ddlite/pull/236#issuecomment-225479547,
or mute the thread
https://github.com/notifications/unsubscribe/ABgw_e1fBNeqzFFat4m9AHzjXjGYy5pYks5qLMWJgaJpZM4Iz6wP
.

@SenWu could you take a look at this commit and see if it gets you what you need?
@henryre Thanks for the help with this first of all.  Overall I think the code here is getting a bit opaque and bloated for such a simple core alg, and some of the terminology is a bit off or confusing; we've discussed a refactor here so let's just clean up a bit for now, then do that?  Happy to discuss next week / intermittently this one!

@ajratner Where specifically are you seeing bloat besides the argument passing?

Didn't mean to sound too critical- just a lot of lines of code for LR.  We'll review / I'll try to qualify that statement soon...

No, no prob. Let's just get to the bottom of it. We should have a clean version in Python now in case the refactor gets delayed. The args got bloated because I was trying to let people just swap pipeline=True and pipeline=False, but 1. not a real use case and 2. easier ways to do that. I'll clean that up tomorrow

@SenWu try pulling again. _lf_w is now the weights associated with the LF accuracies (so len(_lf_w) == num_lfs(). The function get_predicted_probability_lf() uses these weights and returns the marginal probabilities for each candidate. You can then index the returned array of probabilities however you want.

@ajratner ok here's the "three pronged plan" for fixing this up

Remove option for joint learning in DDLite. This will remove needless confusion, allow cleaner integration with LSTMs, and remove the parameter passing bloat since we only need checks for calls to the pipeline function
Remove the log odds-based functions and instead store a precomputed array of LF marginal probabilities and probabilities output from the final model. This again removes needless confusion, and allows cleaner integration with LSTMs.
Disrupt.

I like 3.
On Mon, Jun 13, 2016 at 4:35 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

@ajratner https://github.com/ajratner ok here's the "three pronged
plan" for fixing this up

Remove option for joint learning in DDLite. This will remove
needless confusion, allow cleaner integration with LSTMs, and remove the
parameter passing bloat since we only need checks for calls to the pipeline
function
Remove the log odds-based functions and instead store a precomputed
array of LF marginal probabilities and probabilities output from the final
model. This again removes needless confusion, and allows cleaner
integration with LSTMs.
Disrupt.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/ddlite/pull/236#issuecomment-225739397,
or mute the thread
https://github.com/notifications/unsubscribe/AHPtuCxGmMHv6AQkrgFjW7pld9VOvqWCks5qLelUgaJpZM4Iz6wP
.

Sounds like a good plan to me! I would also add that we should continue
thinking of ways to maintain a separation between the "core alg" (eg
gradient update, etc) and all the parameter tuning bells and whistles code,
just for cleanliness
Otherwise sounds great
As for disruption: i think of this PR as basically deep learning for the
uber for marginal probabilities delivery. So yeah, it's gonna disrupt.
On Mon, Jun 13, 2016 at 7:41 PM chrismre<EMAIL_ADDRESS>wrote:

I like 3.
On Mon, Jun 13, 2016 at 4:35 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

@ajratner https://github.com/ajratner ok here's the "three pronged
plan" for fixing this up

Remove option for joint learning in DDLite. This will remove
needless confusion, allow cleaner integration with LSTMs, and remove the
parameter passing bloat since we only need checks for calls to the
pipeline
function
Remove the log odds-based functions and instead store a precomputed
array of LF marginal probabilities and probabilities output from the
final
model. This again removes needless confusion, and allows cleaner
integration with LSTMs.
Disrupt.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/HazyResearch/ddlite/pull/236#issuecomment-225739397
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AHPtuCxGmMHv6AQkrgFjW7pld9VOvqWCks5qLelUgaJpZM4Iz6wP
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/ddlite/pull/236#issuecomment-225740361,
or mute the thread
https://github.com/notifications/unsubscribe/ABgw_ZwqE7-bxcKlE8Iy5GMFBEvYB5Ggks5qLeq5gaJpZM4Iz6wP
.

@henryre Let me know when ready to look at; also anything I can help code up?

@ajratner Ok take a look at this before I update docs

@henryre Only minor comments, otherwise as long as we can confirm that the tests run LGTM!
Also, I'm hoping to move documentation to just (1) single (CDR) tutorial, and (ii) auto-generated docs.  So I would just beef up the doc strings (see this handy, down-to-earth little reference!), then use pdoc as in:
https://github.com/HazyResearch/ddlite/blob/candidate-extractor-2/generate_docs.sh

I'm just going to merge this in without @ajratner's docstring fanciness to get the code in and stop blocking. Will start on new docs today

PEP 8

:( wrong platform

All checks passed on Henry CI!

PEP-257 sheesh. Sounds good :)
On Wed, Jun 15, 2016 at 1:53 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

All checks passed on Henry CI!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/ddlite/pull/236#issuecomment-226316609,
or mute the thread
https://github.com/notifications/unsubscribe/ABgw_Uhndd_uHIrgMlR7Ki5OWKTmHbZrks5qMGZBgaJpZM4Iz6wP
.

Do add in any post-merge though!
On Wed, Jun 15, 2016 at 2:10 PM Alex Ratner<EMAIL_ADDRESS>wrote:

PEP-257 sheesh. Sounds good :)
On Wed, Jun 15, 2016 at 1:53 PM Henry Ehrenberg<EMAIL_ADDRESS>wrote:

All checks passed on Henry CI!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/ddlite/pull/236#issuecomment-226316609,
or mute the thread
https://github.com/notifications/unsubscribe/ABgw_Uhndd_uHIrgMlR7Ki5OWKTmHbZrks5qMGZBgaJpZM4Iz6wP
.


Multiply axis value by 8 in Wayland

Description
When using wlfreerdp, the number of scrolling rows is less than either
xfreerdp or other window.
In KDE Wayland session, I get a default axis value, which is 15.
And according to the comment in issue #6087, we have a default step
value in X11, which is 120.
To make wlfreerdp and xfreerdp behave identically, we should multiply
axis value by 8.
Test Environment

Arch Linux
KDE Plasma 5.20.5

Related Issues

Inconsistent mouse wheel scroll behavior on Wayland (#6087)
Scrolling and keyholding behaviour (#6388)

@0140454 thank you for the pull request.
I´ve checked wayland documentation and found the reason for the inconsistent behaviour and fixed it in #6766
(that one matches the behaviour of the xfreerdp version exactly as it listens to discrete events and uses the same conversion value)

@0140454 thank you for the pull request.
I´ve checked wayland documentation and found the reason for the inconsistent behaviour and fixed it in #6766
(that one matches the behaviour of the xfreerdp version exactly as it listens to discrete events and uses the same conversion value)


MAINT: change dtype comparison in optimize.linear_sum_assignment.

Follow-up to gh-7031.  Thanks to @pv for pointing out that
dtypes must not be considered singletons.

LGTM, thanks Ralf. Merging.


Add section:  ASSIGNMENT Operators explained wit example

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Congrats @ on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Could I use it in Unity 3D?

Hello, I'm looking forward to make game with Unity 3D which uses
real-time 3d reconstruction. Is it possible to make this work in Unity 3D?

Hi, I didn't use Unity before. But I think you could refer to some other works that try to convert Pytorch-implemented work to the one Unity can load?


Adding support for Django 4.0

Adding support for Django 4.0
ERRORS:
pghistory.AggregateEvent.pgh_data: (fields.E904) django.contrib.postgres.fields.JSONField is removed except for support in historical migrations.
HINT: Use django.db.models.JSONField instead.
pghistory.AggregateEvent.pgh_diff: (fields.E904) django.contrib.postgres.fields.JSONField is removed except for support in historical migrations.
HINT: Use django.db.models.JSONField instead.
pghistory.Context.metadata: (fields.E904) django.contrib.postgres.fields.JSONField is removed except for support in historical migrations.
HINT: Use django.db.models.JSONField instead.

Thanks! This was fixed with https://github.com/Opus10/django-pghistory/pull/25
Opening a PR for the other fix integrated here. Will comment when the newest version is deployed

fix is in 1.3.0! I added you as a contributor in the README


Bundle command line tools with xde

It would be useful to be able to open a directory, open a URL in the simulator, get the URL for a project, etc. for scripting and just for development.
The command line tools should be installable the way that the atom shell commands are.
And they should roughly line up with the exp command line tools, though with a few differences.

This is mostly done -- but by adding buttons to xde instead of command line tools.
I think something to open an exp:// URL would still be useful too, but I don't think this is critical for now compared to other things.

there have been new requests for command line tools, both so people can script xde, and just because some people prefer it that way.

there have been new requests for command line tools, both so people can script xde, and just because some people prefer it that way.

I think having an XD (exponent developer) API and having XDC (exponent developer command line) and XDE (exponent developer environment) as UI layers could work well. Also for scripting, XD API could then be directly used by Javascript scripts.

I think this is covered by the development of xdl and exp. Let me know if I shouldn't have closed this :).


Minor cleanup to minimize changes to files

This PR includes minor changes to the buildspecs and Makefile to minimize unnecessary edits that were made during the proof of concept testing to the Deprecation of TTB Intern project.
For example, there were some trailing spaces in pr-build and Makefile.
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

The first commit [3e3a7ee] included adding [[ double brackets ]] to an if/then argument in pr-build-ubuntu.yml which is intended to readjust path for testing codebuild within a personal fork. This was done to attempt to realign the file with the upstream repo. However, the ubuntu codebuilds fail with double brackets. The next commit [acd225d] modifies that line to accommodate the ubuntu platform and switches back to a single bracket, which was successful in testing.


Add Binary LogicalType

As a developer, I wish I could use Woodwork to categorize columns that contain only one of two values with a logical type of Binary. This would be useful in setting up machine learning classification problems as users would clearly know that the target column with a Binary logical type contains only two values and they should structure the problem as a binary classification and not a multi-class classification.
The Binary logical type should have a dtype of category as it should work with multiple data types including strings, integers and doubles. Missing values should be allowed. This should not include boolean values of True and False as those should be recognized as a Boolean or BooleanNullable logical type. Binary should be a child type of Categorical.
Code Example
import pandas as pd
import woodwork as ww
from woodwork.logical_types import Binary

df = pd.DataFrame({"binary_col": ["yes", "no", "no", "yes"]})
df.ww.init()

assert isinstance(df.ww.logical_types["binary_col"], Binary)

Part of this issue will to update our documentation, specifically this page:

https://woodwork.alteryx.com/en/stable/guides/logical_types_and_semantic_tags.html#Categorical-Logical-Types

For this new Logical Type, we will not do type inference.


package.json missing, not on npm

Hi there, saw your article and video and this looks interesting. Have you considered publishing to npm? Specifically, I tend to follow these suggestions:
https://egghead.io/series/how-to-write-an-open-source-javascript-library
Bower is fine but since you need npm to install it, it might be extra unnecessary complexity in the project.

I specifically have not published it on npm because if you're using it in node you're doing it wrong. Node has Buffer and it does not have atob or btoa.
I suppose I should link to an article showing how to do all of this in node or something...

Gotcha, Thanks for replying.
The problem is that npm !== node. Npm is a javascript module distribution channel. Yes, it is used to download dependencies for node but it is also increasingly used to download javascript dependencies for the browser. Take Angular2, Ionic2 or other large projects for example. They are all moving towards making their source available via npm, even if they only run in the browser. Especially in npm@3 all dependencies are maximally flattened so as to minimize browser payloads.
I guess my recommendation would be to let people know in big letters in the readme that this is specifically for the browser or even better allow it to be used either place and internally handle the various implementation details for the environment (browser or node).
Regardless of this though, npm is increasingly becoming the go-to distribution method for browser dependencies and ignoring it will limit the adoption of your library so I'd highly recommend not equating npm and node.

I'm convinced. I'll publish it.

Awesome. Thanks a bunch. Look forward to playing with this.

Published.
I tried specifying the browser attribute so that it will work in browser systems but throw an error in node.js. I may publish a separate wrapper for node that uses Buffer and thirty-two to expose the same functions.

Let me know if it works for you.

Thanks @coolaj86!


More config options for HDFS storage (e.g. Kerberos)

This adds to the implementation that already exists, and even more so marks https://github.com/rovio/rovio-ingest/issues/47 resolved.
This code was extracted from https://github.com/fabricebaranski/rovio-ingest/commit/9c6eb40e1b7b00ac9f5126e38bb27c8e644ef173, as agreed with the author. Thank you for the contribution!

👍


Brand new project Serenity (not Serene) 3.9.12 fails to compile

Hi all,
I want to modify some stuff in the connectionKey area within Serenity (not Serene). I just have downloaded the newest code from github.
On trying to run a full build, I have the following behavior:
I get 3413 lines of error messages.
Some of them read like this:
D:\Development\Serenity-3.9.12\SharedAssemblyInfo.cs(4,12,4,27): error CS0246: The type or namespace name 'AssemblyCompanyAttribute' could not be found (are you missing a using directive or an assembly reference?)
D:\Development\Serenity-3.9.12\SharedAssemblyInfo.cs(4,28,4,38): error CS0518: Predefined type 'System.String' is not defined or imported
Authorization\ImpersonatingAuthenticationService.cs(3,7,3,13): error CS0246: The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
On closer inspection I see that it cannot resolve references to .NEt FW 4.5 and to .net standard 2.0.
On trying to install .NET FW 4.5, the Installer blocks and says that this is a component of the OS (WS 2016) and that a newer version of it is already installed.
Is it possible to successfully compile Serenity (not Serene) with .NET FW 4.7.2 (as this is on the system and it works fine for compiling a Serene-based project).
And if yes, what exactly do I have to do within the SF project references to get rid of .NET FW 4.5 and .NET Std 2.0 dependencies and to link to .NET FW 4.7.2 assemblies?
(I know that this must be basic DEV knowhow - but I just don't get it).
Thanks for any help.
With kind regards,
John

update:
I had to do a:
Install-Package NETStandard.Library -Version 2.0.3
```

Then most cleared up. Still getting some errors. Will post update here when fully resolved.

John


Add a new parameter set to Invoke-DscResource that takes a DscResourceInfo

Summary of the new feature / enhancement
The current implementation of Invoke-DscResource always calls Get-DscResource. If the caller already has the result of Get-DscResource, it should be able to pass the DscResourceInfo object to Invoke-DscResource and avoid the internal call to Get-DscResource, as well as being able to pipe Get-DscResource to Invoke-DscResource and improve performance.
Proposed technical implementation details (optional)
No response

Should this be implemented for v2 and/or v3?


The / endpoint needs content

Apparently for security reasons the / endpoint of the app needs to have some content. A 404 isn't sufficient.

Argh, wrong repo


[Bug][Jenkins] FullName,FullDisplayName,JobPath too long to save db

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
A user triggered the error as follows:
subtask extractApiBuilds ended unexpectedly caused by: error adding the result to batch caused by: Error 1406: Data too long for column 'full_display_name' at row 138

As we see in the code, full_display_name has come from Jenkins API. and it limits by 255 in the tool layer.

in the domain layer. it will convert to the CICD name and limit by 255.

Since fullname and jobpath have a high probability of being too long when FullDisplayName is too long, the above fields may also have the same problem and need to be dealt with.
What do you expect to happen
Jenkins can get data success.
How to reproduce
With a very deep and long path to save Jenkins jobs.
Anything else
No response
Version
main
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

After check, we can just drop fullDisplayName, this is resolved by #4066 4066


Update README.md

Updated the README.md

I just started using the exporter. It works great so thanks for your work first of all!
The example docker-compose file had an error in IntelliJ and I found some parts of the README difficult to understand so I wrote some sentences which would have made it a lot clearer and faster for me to get it running the way I want it.
I'm curious for your input and feedback.

This PR is out of date. I am closing but if you make updates to the source, you can reopen. The docker-compose in the README looks ok to me. I do not thing adding the second example makes the intent any more clear, but adding some text may be useful. The environment variables have also been removed for the most part.


Segmentation Fault (core dumped) when running pytest

Hi, when running tests ( conversions/test_meshconversions.py ), 'Segmentation fault (core dumped)' is raised.
Here is the output
================================================================== test session starts ==================================================================
platform linux -- Python 3.6.9, pytest-5.0.1, py-1.8.0, pluggy-0.13.0
rootdir: /home/zhangyang/QYD/kaolin
plugins: arraydiff-0.3, openfiles-0.4.0, doctestplus-0.4.0, remotedata-0.3.2, cov-2.8.1
collected 177 items

tests/test_import.py ....                                                                                [  2%]
tests/conversions/test_meshconversions.py .....Fatal Python error: Segmentation fault

Current thread 0x00007fa502a8a740 (most recent call first):
  File "/home/zhangyang/anaconda3/envs/kaolin/lib/python3.6/site-packages/kaolin-0.1.0-py3.6-linux-x86_64.egg/kaolin/metrics/point.py", line 36 in forward
  File "/home/zhangyang/anaconda3/envs/kaolin/lib/python3.6/site-packages/kaolin-0.1.0-py3.6-linux-x86_64.egg/kaolin/metrics/point.py", line 65 in forward
  File "/home/zhangyang/anaconda3/envs/kaolin/lib/python3.6/site-packages/torch/nn/modules/module.py", line 541 in __call__
  File "/home/zhangyang/anaconda3/envs/kaolin/lib/python3.6/site-packages/kaolin-0.1.0-py3.6-linux-x86_64.egg/kaolin/metrics/point.py", line 124 in directed_distance
  File "/home/zhangyang/anaconda3/envs/kaolin/lib/python3.6/site-packages/kaolin-0.1.0-py3.6-linux-x86_64.egg/kaolin/conversions/meshconversions.py", line 164 in eval_query
  File "/home/zhangyang/QYD/kaolin/tests/conversions/test_meshconversions.py", line 56 in test_trianglemesh_to_sdf

The error seems related to the second code following:
sdf = kal.conversions.trianglemesh_to_sdf(mesh)
distances = sdf(torch.rand(100,3).to(device) -.5)

Any suggestion to figure out the trouble?
My system,
Ubuntu: 18.04
CUDA: 10.0.130
Driver: 410.48
GPU: 1080Ti
Python: 3.6.9
Pytorch: 1.3.1

How did you fix it?

how it was fixed?


[Documentation]Advanced builder section added

I added npm run buildreact command to replace the build command, so we shouldn't need these instructions anymore, but the ⌘ + R bit is useful (might add it).

This is just useless because the watch task will need to be done again if you are not recloning the repo and building the react components.

What do you mean by this? You shouldn't need to reclone the repo 😅

the buildreact command is the perfect things.
⌘ + R is so useful ;)


new bug

VSCode Version:
OS Version:

Steps to Reproduce:

Any details about this bug?

Please provide information about the bug


Fix URL to plugin submit docs in user guide

The plugin submit documentation moved from http://plugins.gradle.org/submit to http://plugins.gradle.org/docs/submit, but the URL in the user guide section on custom plugins is not updated yet.

Many thanks Kevin. I've made this change locally and it will go out in 2.4. It was easier for me to just make the change.
Thanks again.