displays not detected on linux 6.2 + evdi 1.12 or 1.13

Are you using the latest driver?
displaylink 5.6.1
Are you using the latest EVDI version?
evdi 1.13.0
If you are using a DisplayLink device, have you checked 'troubleshooting'
on DisplayLink's website?
yes, device is dell d3100
Is this issue related to evdi/kernel?
I don't know

Linux distribution and its version: arch linux
Linux kernel version: 6.2.2
Xorg version (if used):  21.1.7 (xorg-server)
Desktop environment in use: Gnome (43.2)

I had a running system with linux 5.18 (I think) and evdi 1.12.0 and recently decided to update my system again
(yes, I do not update regularly anymore, because typically there would be issues with evdi so that I lose my monitors).
I updated my system to 6.2.2 and applied the patches in #401 to evdi 1.12.0 to get evdi running.
Although most peripherals of the docking station are working, none of my monitors show up.
I also tried the recently published 1.13.0 code, but I do not manage to get my monitors working anymore.
Things that I have tried (with evdi 1.13.0):

re-plugging monitors in the hub
powering off/on the hub
restarting my notebook
re-plugging the hub

However, no matter what I try, nothing appears in the logs (no monitors, but also no errors).
Is it possible that the 1.13.0 release requires a displaylink manager update again?

Same here, did exactly the same on a Lenovo 40AF docking station. Everything is recognised except Displays. Have to wait for a fix, or go back to kernel 5.15.

Is it possible that the 1.13.0 release requires a displaylink manager update again?

Yes. DisplayLinkManager checks if the correct major and minor version of the evdi module is loaded. Only the patch part may differ. Because of this, compiling devel won't always work.

We pay for this dock and we cannot use it.
@displaylink-emajewsk please tell us when it will work on linux kernel 6 ?

@displaylink-emajewsk In that case, would it be possible to make a 1.12.1 release that incorporates the changes required to make things work on linux 6?
As a general path forward: have you ever considered adopting semantic versioning?
It would really be nice if evdi could have more frequent updates (e.g. for every breaking change in the kernel) than the DisplayLinkManager.
In return for those frequent updates, the community could help report/resolve bugs more quickly for newer kernels.

We pay for this dock and we cannot use it. please tell us when it will work on linux kernel 6 ?

@bastoune  Arch Linux isn't officially supported. I am sorry. Only Ubuntu LTS kernels are.

In that case, would it be possible to make a 1.12.1 release that incorporates the changes required to make things work on linux 6?

@mrTsjolder Technically, you could run ci/set_version 1 12 1 from the Evdi repo (current devel). Then install both libevdi and evdi kernel module. I've just tried it with the released DLM 5.6.1 and it works on my test machine, but your mileage may vary.

As a general path forward: have you ever considered adopting semantic versioning?

We were actually supposed to follow semver from the start, if we are to trust evdi documentation. I have raised this issue before, and unfortunately the upcoming release still works like that, but hopefully future versions will comply to semver.

It would really be nice if evdi could have more frequent updates (e.g. for every breaking change in the kernel) than the DisplayLinkManager.

I agree.

Hi @displaylink-emajewsk
Whoever plays the role of product owner/manager for DisplayLink from Synaptics, I am assuming, is also the same person for EVDI.  I acknowledge that the Linux Community pales compared to your macOS and Windows user base, but there is still a substantial market here. Does any feedback from the community represented here make it in front of their eyes?
The DisplayLink team takes some abuse from time to time, from me included, usually around the time there are Linux Kernel updates, so I want to thank you for always being even-keeled and offering a bit of transparency to us here.

It would really be nice if evdi could have more frequent updates (e.g. for every breaking change in the kernel) than the DisplayLinkManager.

I agree.

Wouldn't it be easier and more streamlined if the whole driver was open sourced and shipped in the kernel? It would not break for each kernel release and updates would be more frequent and community driven.

New linux kernels is no surprise for everyone except here :D

Hello @mrTsjolder, if you haven't tried it already, you might want to try out evdi-compat-git by varungarg from the AUR. Saying this as you listed Arch Linux as your OS in the description. That package worked for me, it uses a fork of evdi repo that is on 1.12 and has the Linux 6.x patch.

I can confirm that @olof-nord's solution works on Arch Linux with kernel 6.2.6 :+1:

Turns out that I installed (and re-installed) the 5.6-1 release of the displaylink package (in the AUR) instead of the 5.6.1-3 release.
Installing the correct displaylinkmanager resolved my issues.
The solution proposed by @displaylink-emajewsk worked without a problem.
Is there any reason why there could not be an official 1.12.1 release?

Turns out that I installed (and re-installed) the 5.6-1 release of the displaylink package (in the AUR) instead of the 5.6.1-3 release. Installing the correct displaylinkmanager resolved my issues.
The solution proposed by @displaylink-emajewsk worked without a problem. Is there any reason why there could not be an official 1.12.1 release?

Breaking changes bump evdi to 1.13.0.
They're apparently waiting for the displaylink release to be "ready"

Alternatively you can lower minor version in library/evdi_lib.h and rebuild to workaround the problem (tried on both 6.1 and 6.2 kernels):
--- library/evdi_lib.h
+++ library/evdi_lib.h
@@ -13,7 +13,7 @@ extern "C" {
 #endif

 #define LIBEVDI_VERSION_MAJOR 1
-#define LIBEVDI_VERSION_MINOR 13
+#define LIBEVDI_VERSION_MINOR 12
 #define LIBEVDI_VERSION_PATCH 0

 struct evdi_lib_version {

Does any feedback from the community represented here make it in front of their eyes?

@djallits Yes. I forward and voice all the concerns and frustrations I see here or on the unofficial AUR, plus a whole bunch of my own.

Is there any reason why there could not be an official 1.12.1 release?

@mrTsjolder The reason is mostly historical. There's certainly room for improvement, but any changes are subject to business needs.

@displaylink-emajewsk Just to make sure: with "official", I just meant a v1.12.1 tag and/or a corresponding github release pointing to this tag.
I understand that it is silly to have two releases pointing to the same code, but I do not see how this relates to "business needs".
In the end, this is merely a technicality in a github repository.
@gringus It is probably more convenient to use the ci/set_version script, which also changes version numbers in other files.
I will close this issue since my original problem has been solved, but I don't believe that this will be the last confusion/frustration due to this particular versioning scheme.
PS: I used the script to create a 1.12.2 version from the v1.13.1 branch and this still seems to work on linux 6.2.


Add ability to pull all activity data from a project

this is helpful if you are looking to build metrics based on events, eg, how many stories were started in the past month?  Seems like a minor extension of the recently merged activity capability.

Coverage increased (+0.67%) when pulling 09d9b4a1b641a35e1e3d6296e010e54a83696435 on omadahealth:master into 45cd400053fb2f069662d0dd11fbbd22ac34c360 on dashofcode:master.

@austinfromboston  thanks for the pull request. There have been 4 for adding activity, so will be taking the best from all to get this in the next release.

@austinfromboston I added support for project Activity based on all the pull requests. Thanks.


[Bug] Fill hitboxes bug in practice mode

I have 'Show hitboxes on death' on, with 'Fill hitboxes' on as well. It works as expected in normal mode, but in practice mode, the hitboxes are always shown even without dying. Not only that, but also, while the hitboxes are shown, they aren't filled and the hitboxes are only filled once the player dies.

I think Prevter already said that the hitboxes are always shown in practice mode and is intentional

Well the hitboxes still aren't filled with 'Fill Hitboxes' even in practice mode until you die. Also the only thing that is filled is the player hitbox without dying yet

Also is the player hitbox appearing at the bottom of the ground intentional?

For me, the hitboxes always show afterwards with "Show Hitboxes on Death" enabled if i die in practice.


System Family and System SKU not detected on B650E Steel Legend WiFi

<------- MOTHERBOARD INFORMATION ------->
Motherboard Model: B650E Steel Legend WiFi
Motherboard Manufacturer: ASRock
Serial Number: Default string
System Family: Not detected
System SKU: Not detected
Chipset: AuthenticAMD
BIOS Publisher: American Megatrends International, LLC.
 BIOS Date: 28.07.2023 BIOS Version: 1.28 SM-BIOS Version: ALASKA - 1 BIOS Mode: UEFI Last BIOS Time: 51.1 Second Secure Boot State: Off TPM Status: Active - Version: 2.0 (2.0, 0, 1.59) TPM Physical Asset Version: 1.3 TPM Manufacturer: AMD TPM Manufacturer ID:<PHONE_NUMBER> TPM Manufacturer Version: <IP_ADDRESS> TPM Full Manufacturer Version: <IP_ADDRESS> TPM Manufacturer Publisher: AMD Motherboard Model Version: Default string Primary Bus Type: PCI Secondary Bus Type: ISA BIOS Major-Minor Version: 5.26 SM-BIOS Major-Minor Version: 3.4

Not detected on desktop computers. It is not a bug.


ruby-2.3.1 / rake issue

hello,
I have a probleme using rest-client with rake (for test integration).
when I use the rakefile linked  with ruby-2.2.3 it work.
but when I use it with ruby-2.3.1 I have:
rake aborted!
NoMethodError: undefined method `this' for #<Gem::Specification:0x93ce5c mime-types-3.1>
/home/Tophe/.rvm/gems/ruby-2.3.1/gems/mime-types-3.1/lib/mime/types.rb:8:in `<top (required)>'
/home/Tophe/.rvm/gems/ruby-2.3.1/gems/rest-client-2.0.0/lib/restclient/request.rb:2:in `<top (required)>'
/home/Tophe/.rvm/gems/ruby-2.3.1/gems/rest-client-2.0.0/lib/restclient.rb:11:in `<top (required)>'
/home/Tophe/.rvm/gems/ruby-2.3.1/gems/rest-client-2.0.0/lib/rest-client.rb:2:in `<top (required)>'
/data/git/gogs.artprice.bil/artdb/artist_cli/Rakefile:1:in `<top (required)>'
/home/Tophe/.rvm/gems/ruby-2.3.1/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
/home/Tophe/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
/home/Tophe/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `<main>'
LoadError: cannot load such file -- rest-client
/data/git/gogs.artprice.bil/artdb/artist_cli/Rakefile:1:in `<top (required)>'
/home/Tophe/.rvm/gems/ruby-2.3.1/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
/home/Tophe/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
/home/Tophe/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `<main>'

it break on the load off the rest-client
Rakefile.txt

rest-client is tested and known to work on Ruby 2.3.1, so I think you've encountered an unrelated bug.
Have you tried upgrading rubygems? It might be related to this issue:
https://github.com/rubygems/rubygems/issues/1420

hello,
I was using gem v2.5.1,  after
gem update --system
Updating rubygems-update
Fetching: rubygems-update-2.6.8.gem (100%)
every thing is OK.
thank you for your help !


move payload to /payload and add version to /

No need to move to /payload, just deliver the version on GET /


Improving PandasDataset tutorial

The tutorial on PandasDataset should be improved to cover common workflows like:

loading data from a single "long" CSV file
doing a groupby on it to then cast the groups to have a certain frequency using asfreq (and filling the gaps)
loading data from a "wide" CSV file, where each column is a separate univariate target

Essentially, it would be nice to expose all common ways one can bring data from a file to GluonTS via Pandas, with common adjustments/preprocessing that might be needed, instead of randomly generating the DataFrame objects directly.

@lostella , thank you for opening the issue!
An example, please consider incorporating the following "story".
A business wants to make predictions about future customer orders for specific items on a monthly basis. The dataset is customer placed orders for an item with order_id, quantity, and timestamps.
timestamp,order_id,item_id,quantity
2022-05-15 15:20:12,ODR123,foobar,1234

timestamp            order_id  item_id  quantity
2022-05-15 15:20:12  ODR123    foobar   1234

The more advanced would be adding item_cat column, which would hold the category of an item, e.g. tshirts, sweaters, etc.

Notably, a particular item_id could be ordered every other month, creating gaps in the time-series.

Notably, a particular item_id could be ordered every other month, creating gaps in the time-series.

I think those cases should be disambiguated from the user: if there are gaps in the time index, it could be that an observation is missing, or that it can be assumed to be zero. The safest thing to do is not to accept gaps in the data, and require the user to fill them in: this is something the tutorial should be very clear about, and provide examples on how to do that I believe.


How to share data from my app to another app

Hi,
I am able to call another application from my application. But how can I send share data between two apps.
Kindly suggest..

Hi!
Using extras data:
var sApp = startApp.set({ /* params */
    ...
}, { /* extras */
    "EXTRA_STREAM":"extraValue1",
    "extraKey2":100500
});

hi @lampaa
Please help having same issue with me marked above.


Import user guide to github Wiki

Hi guys !
I think that it would be great for your project to import your user guide into the github wiki.
Why ? Only to get better harmony between the work you propose and your documentation :)

I'm going to bump this, it really should be here on the wiki


Changes needed in the "osm_param-species.csv" config file

@jhpoelen Could you please remove the "species.length2weight.fl.sp*" keys (and corresponding values) from the "osm_param-species.csv" config file?

Parameters was removed as requested. Please verify.

The present issue has been resolved; therefore, I am closing it today.


feature: add brand new tool for creating DAOs & Multisigs

Respect to the DAO creation:

[ ] it costs 6N to create a DAO, is that the minimum necessary - to the yoctoNEAR?
[ ] we should add in the bottom the list of DAOs that the user created
[ ] such lists should have a link to somewhere where the user can now use / control the DAO

Respect to multisig:

[ ] I got a frontend error, even when the multisig contract was created

@gagdiez required deposit for DAO creation is now calculated based on user's input


Metrics.process_times() data frame creation warning

In line 1304 of post_processor.py, the datatypes have to be cast after creation.

This has long been closed.


Help with command

I am trying to log in to a linux device and send the command "miner restart"
I have this code but just get an error failed to execute any ideas?
- command: miner restart
  name: Start miner
  icon: mdi:script-text-play

If I login using HA terminal, then just type miner restart it works perfect.

The SSL seems to connect well, and logs in ok.  However the command just dont seem to be sent well

Hi! Did you try to run your command with ssh.execute_command action in the developer tools? Could you please post the response you are getting?

I have not done that, sorry, how do I do that? sorry still learning, it is now giving me sensor data from the remote device, so we are definitely connected, just unable to send the commands i need :) Thank you for your help again, really close to making this work

Sorry still struggling with this.  Can you help with what I type?
So the order I do this manually is.  SSH into the linux machine with username and password.  Then the command I would type is miner stop or miner start followed by enter.  That's all I need.  Not sure how to format this in here.

I got it working, and found the issue.  Please close this, I had to send the command like this
echo 1 | sudo -S miner start


Automated Quiz Generator from Folder Files for Personalized Practice

Script Title - Automated Quiz Generator from Folder Files for Personalized Practice
Brief - This script automates the process of generating quizzes by extracting content from PDF files stored in a specified folder. It uses a large language model (LLM) to intelligently analyze the text, formulate questions, and generate a quiz based on the extracted information. The generated quiz is saved as a text document, making it easy for users to review and practice the material. This tool is ideal for educators, students, or anyone looking to create personalized quizzes from their study materials.
More Features

Support for More File Formats
GUI-Based Quiz Interface
Multiple Question Types

User Requirements

GROG API Key for the LLM (free)
Source Files

Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md (using this template) in your folder for program Instructions
add requirements.txt if needed

Programming Language

[x] Python

Happy Coding

i want to contribute . plz assign me thank you

I am interested in contributing. Please let me know if I can help.

I am really glad people are willing to contribute to this script, but I already have it ready and I am waiting for the issue to be assigned to me. I love to add your contributions once the core script is merged. Thank you :)

I am interested in contributing. Please let me know if there is something I can help with. Thank you :)

@pawangeek I added the script as a pull request. Could you please check and let me know if more changes are required before merging it. Thank you.


Great job! LGTM

          Great job! LGTM

I wonder if we should consider exposing mkfifo from coreutils since it tags the fifo file:
[ITODORO@ZOSCAN2B ~/projects/coreutilsport_new2/coreutils-9.1/src]$ ./mkfifo a
[ITODORO@ZOSCAN2B ~/projects/coreutilsport_new2/coreutils-9.1/src]$ ls -lT a
t ISO8859-1   T=on  prw-rw-r--   1 ITODORO  CDEV           0 Nov  1 09:51 a
[ITODORO@ZOSCAN2B ~/projects/coreutilsport_new2/coreutils-9.1/src]$

Originally posted by @IgorTodorovskiIBM in https://github.com/ZOSOpenTools/texinfoport/pull/16#pullrequestreview-1708272363

The potential downside - will there be cases where mkfifo is a binary (or EBCDIC) stream? For binary, perhaps this is ok - just needs some thought.

Running with just mkfifo added in as a new test shows 2 more failures in 'wc' (and one new pass in 'wc' ?)
tools/refine-test-results -d */20231106_220821_check.log wc
FAIL: tests/wc/wc.pl
FAIL: tests/wc/wc-files0-from.pl
PASS: tests/wc/wc-files0.sh
PASS: tests/wc/wc-nbsp.sh
SKIP: tests/wc/wc-parallel.sh
PASS: tests/wc/wc-proc.sh
PASS: tests/wc/wc-total.sh
FAIL: tests/wc/wc
FAIL: tests/wc/wc-files0-from
SKIP: tests/wc/wc-parallel

vs:
PASS: tests/wc/wc.pl
FAIL: tests/wc/wc-files0-from.pl
PASS: tests/wc/wc-files0.sh
PASS: tests/wc/wc-nbsp.sh
PASS: tests/wc/wc-parallel.sh
PASS: tests/wc/wc-proc.sh
PASS: tests/wc/wc-total.sh

from the last good build (https://<IP_ADDRESS>:8443/job/Port-Build/1122/)

it appears that these are just 'double counts' of the same test (tests/wc/wc is the same as tests/wc/wc.pl) and (tests/wc-files0-from.pl is the same as tests/wc-files0-from)

merged


Generate new CDR files

Develop generate-cdrs.sh script to run SemTK's IngestTemplateGenerator on RACK.  Run generate-cdrs.sh with RACK/nodegroups/generate-cdrs.sh semtk-opensource/standaloneExecutables/target/standaloneExecutables-jar-with-dependencies.jar, see first run fail with exception "No enum constant ANYURI", fix by generating new OWL files to pick up change to PROV-S.sadl (string instead of anyURI), and see second run succeed now.  Also add steps toGitHub Actions workflows to start generating CDR files automatically.
Please review and give me a +1 so I can merge this pull request.
action.yml: Add new steps to start rack-box container, generate CDR files, and then stop rack-box container in GitHub Actions jobs.
**/SadlImplicitModel.owl: Changes due to indeterminate ordering, not worth paying attention to.
PROV-S.owl: Pick up change to PROV-S.sadl (string instead of anyURI).
nodegroups/CDR/*.csv: Regenerate using generate-cdrs.sh with changes to many files which will need to be tested.
nodegroups/generate-cdrs.sh: Develop script to clear rack model, import RACK models, remove old CDR files, and generate new CDR files.
nodegroups/ingestion/**.json: Regenerate using generate-cdrs.sh with changes to many files which will need to be tested.
nodegroups/ingestion/**.csv: Regenerate using generate-cdrs.sh with changes to a few files which will need to be tested.

With the sheer volume of automatically-generated files and changes, it is hard to be certain,
but I've scrolled through them all and done some spot checking and it all seems to be in order.
I'm excited to see this all automated.   Thanks John!

Great!  I'll merge the PR so people can test the new rack-box dev image.


Use face expression model on hidden video feed

Hello,
Just found out about this awesome repo, and I'm having a great time using the face expressions API. Maybe because I was smiling too much (for the testing).
Anyway, In my app, I want to check if the user is smiling but without displaying the camera video on the screen.
For now, I can check if the user is smiling or not with a pretty good accuracy, but the video has to be on my screen.
How can I remove the video from the screen?
Here is the js code:
<video id="video" width="500" height="500" autoplay muted ></video>

async startVideo() {
      let stream = null;
      try {
        stream = await navigator.mediaDevices.getUserMedia({
          audio: false,
          video: { width: 1280, height: 720 },
        });
        this.video.srcObject = stream;
      } catch (e) {
        console.log(e);
      }
    },

this.video = document.getElementById('video');
    Promise.all([
      faceapi.nets.tinyFaceDetector.loadFromUri('/models'),
      faceapi.nets.faceExpressionNet.loadFromUri('/models'),
    ]).then(this.startVideo);
    this.video.addEventListener('play', () => {
      console.log('video started');
      setInterval(async () => {
        const detections = await faceapi.detectAllFaces(
          this.video,
          new faceapi.TinyFaceDetectorOptions(),
        ).withFaceExpressions();
        detections.forEach((detection) => {
          if (detection.expressions.happy >= 0.7) {
            this.isHappy = true;
          } else {
            this.isHappy = false;
          }
        });
      }, 100);
    });

The app is in vue.js, so I only took the parts that matter.
Your help is greatly appreciated.
Cheers,

video element does not have to rendered to work, just add style="display: none" to the video tag.

video element does not have to rendered to work, just add style="display: none" to the video tag.

You can hide the video by setting the style="display: none;"  of the video. The video tag then becomes:
<video id="video" width="500" height="500" style="display: none;" autoplay muted ></video>

or using JS:
var vid = document.createElement("video");
vid.setAttribute('id', 'video');
vid.setAttribute('autoplay', 'muted');
document.body.appendChild(vid);
document.getElementById("video").style.display = "none";

You can hide the video by setting the style="display: none;"  of the video. The video tag then becomes:
<video id="video" width="500" height="500" style="display: none;" autoplay muted ></video>

or using JS:
var vid = document.createElement("video");
vid.setAttribute('id', 'video');
vid.setAttribute('autoplay', 'muted');
document.body.appendChild(vid);
document.getElementById("video").style.display = "none";

Thank you so much @vladmandic  and @sudarshan-parvatikar !
I had of course tried to use "display: none;" but it doesn't work somehow. Could it be due to vue.js and its virtual dom?
Anyway, I created the element in javascript as suggested by @sudarshan-parvatikar, and it works! I still don't know why it works this way and not the other, but I'm glad it does. Thanks again guys, you are awesome!

Thank you so much @vladmandic  and @sudarshan-parvatikar !
I had of course tried to use "display: none;" but it doesn't work somehow. Could it be due to vue.js and its virtual dom?
Anyway, I created the element in javascript as suggested by @sudarshan-parvatikar, and it works! I still don't know why it works this way and not the other, but I'm glad it does. Thanks again guys, you are awesome!

Most likely it is Vue that is avoiding placing element with display:none, but can't do that when it's added programmatically via JS.
Best way to determine what is Vue doing is to open inspector in browser and see which elements are present on the page.

Most likely it is Vue that is avoiding placing element with display:none, but can't do that when it's added programmatically via JS.
Best way to determine what is Vue doing is to open inspector in browser and see which elements are present on the page.

@hamza-bentahar glad it worked out. I suggest trying out @vladmandic 's recommendation as I don't know Vue and I use that snippet in Vanilla JS . Also, if your issue is solved, I'd suggest closing this issue.

@hamza-bentahar glad it worked out. I suggest trying out @vladmandic 's recommendation as I don't know Vue and I use that snippet in Vanilla JS . Also, if your issue is solved, I'd suggest closing this issue.


Release 0.14.0

Placeholder to discuss the release

Would it be possible to do the upgrade to Sinatra 2.0?
It's on their master branch (2.0.0-alpha) https://github.com/sinatra/sinatra/blob/master/lib/sinatra/version.rb

mongoid 5 should be supported

@basex Sinatra 2 alpha is tested and working with current Padrino no problem.
We can plan to drop ruby < 2.2 (as Sinatra 2 and Rack 2 require) for 0.15.0 Padrino version.

I released Padrino <IP_ADDRESS> including the latest minor fixes.
I also pushed 0.14.0.rc1 with the only difference: it does not do this:
require 'active_support/core_ext/string/output_safety'      # SafeBuffer and html_safe
require 'active_support/core_ext/object/blank'              # present?
require 'active_support/core_ext/hash/keys'                 # symbolize_keys
require 'active_support/core_ext/hash/indifferent_access'   # params[:foo]
require 'active_support/core_ext/hash/reverse_merge'        # reverse_merge
require 'active_support/core_ext/module/aliasing'           # alias_method_chain
require 'active_support/core_ext/array/extract_options'     # Array#extract_options!
require 'active_support/core_ext/hash/slice'                # slice
begin
  require 'active_support/core_ext/object/deep_dup' # AS 4.1
rescue LoadError
  require 'active_support/core_ext/hash/deep_dup' # AS >= 3.1
end

It also has no gem 'activesupport'. To bring it back you will have to add gem 'activesupport' to your project Gemfile and add these requires somewhere around boot.rb. You also can export AS_VERSION=X.0 to your environment and padrino-support.rb will require the features for you.

Congrats @ujifgc on having successfully extracted ActiveSupport, that's an exciting milestone for the framework!

@nesquena I pushed Padrino 0.14.0 to rubygems:
== 0.14.0 (2017-03-15)
- NEW #2120 enable cascading with Rack application (@namusyaka)
- FIX lock rake < 11.0 to avoid last_comment error (@namusyaka)
- FIX handle nil database passwords for create_db and drop_db (@phallstrom)
- FIX #2119 add rake gem tasks to gem project Rakefile
- NEW support Erubi ERB engine (@adam12)
- FIX #2125 do not load in cycle files excluded from reloading

== 0.14.0.rc2 (2017-01-19)
- FIX #2109 change the format of session_id for Padrino Admin AccessControl
- WARN #2109 Existing sessions will be dropped
- FIX #2097 Use exe folder for application executables (@adam12)
- FIX #2105 Run bundle with --binstubs on -b switch (@adam12)
- FIX #2111 disallow conflicting project names
- NEW remove deprecations planned for 0.14.0
- NEW stop managing Ruby default encodings
  Default Encoding.default_internal is now nil (Ruby default) instead of UTF-8 (Padrino < 0.14 default)
- FIX #2113 properly override default values in route definitions if parameter is present (@fidalgo)
- FIX #2116 fix plugin list `padrino g plugin -l` (@fnordfish)

== 0.14.0.rc1 (2016-11-02)
- NEW remove the requirement of ActiveSupport (export AS_VERSION=X.0 to put it back)

This is great news, thanks @ujifgc for your hard work on this! Will be upgrading my applications to 0.14.0 soon, are there any major upgrade notes we should put together?
@wikimatze would you be able to help draft up a blog post announcing the release?

Removal of requiring of AS: https://github.com/padrino/padrino-framework/issues/1971#issuecomment-257792761
Removal of 'lib' from $LOAD_PATH: https://github.com/padrino/padrino-framework/commit/365f23b5dcf69d72bfab7fb6dcbf4c82fe5d7945

@nesquena on may way.

@wikimatze great, thanks! 👍

You can see a draf under: https://github.com/padrino/padrino-docs/blob/draft-0-14-release/blog/2017-03-20-padrino-0-14-0.html.md @namusyaka can you post and example for https://github.com/padrino/padrino-framework/pull/2120 and @ujifgc can you explain "Remove deprecations planned for 0.14.0" is this just a refactoring or are we planning to print deprecation notices for older older things.

I'd say the Erubis Support should be Erubi Support - without the trailing s.
https://github.com/padrino/padrino-docs/blob/draft-0-14-release/blog/2017-03-20-padrino-0-14-0.html.md#erubis-support

@wikimatze I'll write the section in a few days

@adam12, agree and changed in https://github.com/padrino/padrino-docs/commit/1b37573893b2ee87d8886cd28b520e3e14a8dc96
@namusyaka great, maybe just fork the branch and create the PR or should I just integrate in master and so that you can create your PR there?

Post is merged in https://github.com/padrino/padrino-docs/pull/134

We are life under http://padrinorb.com/blog/padrino-0-14-0/

Thank you so much! @nesquena @wikimatze

Let's close this issue and go for the next release!


Add an i18n solution

Text in the UI is defined directly in React components as English-language strings.
If the intention is ever to add multi-language support, we should start using something like https://github.com/formatjs/react-intl (or investigate what others are using) to wrap strings in a function call that could return translated forms of the strings in the future. Even if we can't add the actual translations until much later, it would help to establish the usage of this kind of library so it is easier to add languages in the future.

@jwmatthews is this a required feature?


Chain test

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues
#105

Chain test isn't passing tests.
\Yiisoft\Yii\Web\Middleware\Chain description is:

Chain executes middlewares in the order they are added to constructor.

But actually, Chain process only first middleware. Is it bug in Chain class or in the test?
@samdark can you help with clarifying?

I guess that is because these are mock middleware. In order for next middleware to be executed, currently executing middlware should delegate handling:
https://github.com/yiisoft/docs/blob/master/guide/en/structure/middleware.md#delegating-handling-to-the-next-middleware

Thank you for explain. Is test correct now?

Merged. Thanks!


MA2: SMB Scanning also scans Video files (mp4, avi etc)

What version of Music Assistant has the issue?
2.0.0b2
The problem
MA2: SMB Scanning also scans Video files (mp4, avi etc). Prior version never did this.
This means its scanning my entire multimedia folder, which just happens to include several thousand snippet movie files.
How to reproduce
Set up SMB to point to SMB folder with movie file in
Relevant log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2022.3.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

I think that is because of mp4 because that is used as both audio and video extension.
Make sure that you add a subfolder to MA only containing the music files.
So instead of e.g. /media use /media/music
or if you're using smb:
smb://ipaddress/media/music

Please follow Marcels advice and restructure your music folders. We recommend following the guidance here https://kodi.wiki/view/Music_tagging


Remove eval

Remove eval in favour of type conversion, then check for isNaN instead of isFinite. This allows the polyfill to run strict mode.

I'm afraid removing eval() without regressing functionality isn't so easy. parseDimension() can handle arbitrary calc() expressions, see test case: https://github.com/web-animations/web-animations-js/blob/dev/test/js/dimension-handler.js#L19

Are there any work arounds to move forward with this without regressing? It would be great to add our CSP policy back to forbid eval.

I intend to implement this soon.
On 18 Mar 2017 8:54 am, "Jason Nelson"<EMAIL_ADDRESS>wrote:

Are there any work arounds to move forward with this without regressing?
It would be great to add our CSP policy back to forbid eval.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/web-animations/web-animations-js/pull/105#issuecomment-287480993,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4ttpD4Fz3E_6lhVCalmL7ORQdpDEC1ks5rmwEegaJpZM4LzYkE
.

<https://github.com/web-animations/web-animations-js/pull/105#issuecomment-287480993

Eval replacement is up for review in https://github.com/web-animations/web-animations-js/pull/151


SecAuditLogFormat in libmodsecurity

Issue: SecAuditLogFormat is documented in the reference manual, but is not a valid configuration item on libmodsecurity 65bd06fb7 / slightly outdated v3-master.
(with ModSecurity-nginx)
nginx: [emerg] "modsecurity_rules_file" directive Rules error. File: /opt/nginxmodsec/conf/modsecurity.conf. Line: 179. Column: 25. Invalid input:  SecAuditLogFormat native in /etc/nginx/sites-enabled/example.com:16
nginx: [emerg] "modsecurity_rules_file" directive Rules error. File: /opt/nginxmodsec/conf/modsecurity.conf. Line: 178. Column: 23. Invalid input:  SecAuditLogFormat JSON in /etc/nginx/sites-enabled/example.com:16
Expected: Note in the manual that this does not work in libmodsecurity.
Manual entry: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#secauditlogformat
Related: #1395 (closed prematurely?)

Indeed, SecAuditLogFormat directive is currently not supported on libModSecurity.
As of now, for libModSecurity Serial logging is using the regular log format by default.
But if you want JSON logging you need to switch to Concurrent (aka Parallel) or HTTPS logging type as these are using JSON by default.
I'll propose an update to the parser to make it clear instead of the "invalid input" error message until this is tested and known to be working.

Implemented already.


fix documentation

new docs have some inconsistencies

Hey @Oluwaseun241 👋
Do you want to pick this up?

Yes


Replaced local ci workflow with one from external repo

Codecov Report

Merging #39 (84e1065) into main (58386d0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #39   +/-   ##
=========================================
  Coverage     97.02%   97.02%
  Complexity      137      137
=========================================
  Files            24       24
  Lines           403      403
=========================================
  Hits            391      391
  Misses           12       12

Continue to review full report at Codecov.

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


[reproc]: Update to v11.0.0.

@DaanDeMeyer, thanks for the PR!
It failed on x86-windows on CI testing, could you help have a look?

I fixed x86, the other failures seem unrelated.

It looks like this upgrade got picked up by our mass-upgrade script:
https://github.com/microsoft/vcpkg/commit/08c951fef9de63cde1c6b94245a63db826be2e32
Please open a new PR if there are any remaining issues!


Move cursor to -100, -100 before each test

fixed by https://github.com/ihodes/seltest/commit/fd7cba8f6f4ba9eb3e60584d1b455dd7066c9d3a


async_setup_entry: migrate to new API

I think this is the right fix but I haven't worked out how to test against the dev image. Does a PR kick off CI?

Looks good, thanks!


Adding C++ code to Unicode/ICU

Mingalaba,
I am trying to add the Burmese calendar to Unicode / ICU / CLDR
https://github.com/unicode-org/icu
Your C++ Code is open source, so I intend to use it in the module. But you are still the main author.
Would you sign the Contributor License Agreement (CLA) for Unicode? https://cla-assistant.io/unicode-org/icu ? Please let me know if you have questions.
You can see my progress at https://github.com/Georeactor/icu/blob/buddhist-hack/icu4c/source/i18n/buddhcal.cpp
Thanks!

Hi @mapmeld,
Thanks for the effort to add the Burmese calendar to Unicode. I just signed the CLA.
Cheer!


How do I give explicit permissions to Faculty leaders?

While the documentation says that IT needs to give explicit permissions for leaders to view the insights in the Insights-app: It does not say how, or where to actually do so. This should be added to a documentation written specifically for IT-admins.

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

ID: 3501fde1-69ef-1908-876c-4f50e90649f5
Version Independent ID: e9c673d9-6c18-7440-da5d-cdeff4dd9b8b
Content: IT Admin Guide to Insights in Teams for Education - Microsoft Teams
Content Source: Teams/class-insights.md
Service: msteams
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

@zircuitz Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Update test.txt

Please add my edit.

no way what the hell is this

We need this edit!

conflitcs


arch: x86_64: add no-relax to the linker flags

Summary
Using newer gcc toolchains (version 7 and 9), without --no-relax linker flags, x86_64 boards failed to build.
Impact
x86_64 boards failed to build, including the ostest example in the repository
Testing
Following the READMEof x86_64 build, one should be able to build ostest binary and successfully run it on qemu or boches emulator.
I might need someone with older distro, e.g. Ubuntu 16.04, to test will the old toolchain be affected by this patch or not.
As I remember, 16.04's gcc 5.4 doesn't have this problem.

@sonicyang Looks like we were both fixing this issue... I also just opened a PR #904 as well to address some other issues as well.  Although I fixed the linker in another place, your flag might be more appropriate.

@sonicyang Looks like we were both fixing this issue... I also just opened a PR #904 as well to address some other issues as well. Although I fixed the linker in another place, your flag might be more appropriate.

Nice synchronicity.
I do also think adding at the Makefile instead of Make.defs is more proper way?
I am not so definite about the answer.

Looks like we were both fixing this issue...

Hmmm... since those of us willing to help with the merge are not so familar with all of the isues here, can you please advise.  Should both of these be merged?  Neither?  Do the depend on additional changes?

Should both of these be merged?
I think the change of PR #904 should definitely be merged.

From a point of view on functionality the change of the linker flag in either Makefile of Make.defs have no difference, but I prefer adding the no relax flag in the Makefile, as thin PR did.

I think this is fine to merge in, I'll pull this part of the fix out of my PR later as it also needs style fixes.


Feature enhancement: Create a Subsegments for operations handled by Powertools

Is your feature request related to a problem? Please describe.

When using the idempotency module with Tracing: Active, it is not possible to see from the Trace how much time was spent inside Powertools code.
Adding a subsegment will make it easier to correlate the DynamoDB SDK calls, with the Idempotency functionality from Powertools.
Describe the solution you'd like

I would like an XRay subsegment to be created to show how long it's spent inside the Idempotency code.
This is an initial idea for discussion/consideration, it could be further expanded to other Powertools functionality.

Good idea but the idempotency module works before and after the handler method is actually executed. Should we add 2 segments?

One before when we check in the DB if the idempotency key is already there or insert it
One after when we update the record

Also, we may have a "dependency" issue. This should happen only if tracing is enabled / powertools-tracing is used. But we don't want to add a (maven) dependency to xray in the idempotency module...

Let's do this in v2

Idempotency isn't the only module that calls AWS services. Do we want to add it to everything (e.g. the various params?)

Also, we may have a "dependency" issue. This should happen only if tracing is enabled / powertools-tracing is used. But we don't want to add a (maven) dependency to xray / powertools-tracing in the idempotency module...

This will be the trick.

@heitorlessa wdyt?


New package: EiffelSoftware.EiffelStudio.Stable version 23.09

Description

Resolve #109535

Checks

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@Dragon1573  Thank you!


Hardened RKE2 cluster is not passing CIS scan with rke2-cis-1.23-profile-hardened profile

Description
I deployed a downstream cluster following the rke2 hardening guide https://ranchermanager.docs.rancher.com/pages-for-subheaders/rke2-hardening-guide.
spec:
  defaultPodSecurityAdmissionConfigurationTemplateName: rancher-restricted
  rkeConfig:
    machineSelectorConfig:
      - config:
          profile: cis-1.23
          protect-kernel-defaults: true

Then I tried CIS scan using rke2-cis-1.23-profile-hardened profile following this guide https://ranchermanager.docs.rancher.com/pages-for-subheaders/cis-scan-guides.
But have 7 failed scans.

First, I am wondering if this result is positive false or negative false.
If this is correct result, hardening process has some missing parts?
Or mismatching betwen CIS benchmark version and rke2 version could be the reason?
I tried cis-1.23-profile for CIS scan also, but the result is worse. 17 Fail, 45 Warn
Versions
management cluster: rke2 1.25.7
rancher version: 2.7.3
downstream cluster: rke2 1.25.7
rancher-cis-benchmark app version: 4.0.0
Actual results and expected results

Actual results: 28 Warn, 7 Fail (see above screenshot plz)
Expected result: 0 Warn, 0 Fail

PS: Please correct me if I filed the issue in the wrong place.

@josedev-union All the failures above except 5.1.5 is expected with CIS Benchmark version 1.23. We'll be introducing CIS Benchmark 1.24 in next quarter, so these issues are expected to get fixed automatically.
Test 5.1.5 got fixed recently and it's available on CIS Benchmark chart version 4.0.0 with security-scan version v0.2.11.
More details on the issue and the fix is here https://github.com/rancher/rancher/issues/40817
After creating the RKE2 hardened cluster please follow the steps mentioned here https://ranchermanager.docs.rancher.com/pages-for-subheaders/rke2-hardening-guide#configure-default-service-account
Also I just validated the scans n Rancher latest version with downstream v1.25.9+rke2r1 and CIS Benchamrk chart 4.0.0, 5.1.5 test is passing and all the rest are in failure state (which is expected.).

@rayandas I'm getting similar failures on hardened RKE2 v1.26.7 with cis-benchmark chart 4.1.0 which has cis-operator 1.0.12 and security-scan 0.2.12. Can you please advice? TIA!

Hi @msa200, would you mind sharing the missing information :

Downstream cluster: RKE2 v1.26.7
cis-benchmark chart version: 4.1.0
rancher/cis-operator version: v1.0.12
rancher/security-scan: v0.2.12
Rancher version: ?
List Scan results (FAILS) : ?

Thanks.

Hi @andypitcher, Rancher version is v2.7.6 and list of scans which are failing are the same which are mentioned in the issue description.
Are these failures fixed in the newer chart version shipped with v2.7.7/v2.7.8?

@msa200 some of the checks are expected to fail as documented in each distribution's hardening-guides, you can have look there:

RKE
RKE2
K3S

Regarding the cis-benchmark chart version, I would recommend you to install and rerun the scan the latest one (4.2.0) which embeds the latest security-scan:v0.2.13.
Cheers.

Closing this issue for inactivity. @msa200 Feel free to reopen it, make sure to provide your scan results with 4.2.0 chart, as per my last comment.


CI: Prevent metrics step from failing when tensorboard dir is not found

If a CI job fails before the tensorboard dir is created, it causes the entire metrics step to fail. Instead, we'd like for the metrics for only that job to fail and for the metrics to be checked for the remaining jobs.

This CI run shows that the metrics step passes even though the multinode tests fail: https://github.com/NVIDIA/JAX-Toolbox/actions/runs/9277815075


pageant ssh auth

Is it posibble to use pageant to auth ssh?

I don't know what is Pageant, so I don't know. Help welcome!

ok. I will investigate the code i check possibilities.

I see that you are wrapping ssh cmd tool. I saw pageant usage with this pure JS ssh client https://github.com/mscdex/ssh2 Look for agent - string - in README.md.
So in this version it's not up to shipit to handle agent auth but it's a system(shell) setup matter.


[Suggestion] remove <>

Hey, I'm sick of the global prefix or just the rank prefixes that have <>, How do I remove them?

Do you mean as in way names are displayed in chat?  *<Pugzy>: Hey etc.


fix: Kokoro builds with missing pyaudio package

An attempt to fix failing Kokoro builds due to E: Unable to locate package python-pyaudio  error.
Note: I am not 100% sure if we need portaudio19-dev and python3-pyaudio at all as I couldn't find any references to these libraries in the source code.

Thanks @rsamborski I've gone ahead and made some updates that have resolved the underlying issue for now.


Add the option to provide ART and ERT keywords

@tanner-andrulis Is this the correct way to do to it? I.e., am I using the add_attr calls correctly and does the style match the project?
I also didn't put any tests.  If you think this is good, I'll think of some.

It's an OK start, but there's no type checking inside the ERT/ART. We'd also need some objects to reflect their internal structures rather than just allowing an "anything" in that place

I'm hitting a snag here.
The current version fails test_eyeriss_like in test_compare. This seems to be due to the ART and ERT keys not being removed even though they are not specified by the user, thus causing an error when ruamel attempts to stringify the NotRequired class.
This is not supposed to happen since the ART and ERT keys are supposed to be removed during parsing if the user does not provide them. The code that is supposed to remove them is in _parse_elem, which is called at the end of the ctors of DictNode and ListNode. This leads me to believe that somehow _parse_elem is either note being called or the ART and ERT keys are being added again after being removed.

Try now. All tests are passing. Now the behavior is:

ART & ERT are initialized with an empty tables list if not specified (so users may simply add to these tables if they desire, or they can overwrite).
If ART and/or ERT tables are empty, they are not dumped

@tanner-andrulis Thank you very much.
This last commit, 6218c46, cleans up the code I added to support my last commit, which is reverted to use your solution instead.


Fix cli create git fail

Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[x] I have added description of my changes into CHANGELOG file
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

@dreaquil , thanks for the contribution. Could you please remove all training whitespaces in core.py? See artefacts for Linter / PyLint if you have more questions.

Thanks for the contribution!


BCMOHAD-25285: Fiscal Year Reporting Dates ETL

Description of changes:

Added ETL for Fiscal Year Reporting Dates.

Hi @weskubo-cgi, I've finished the items you commented on, and requested another review, please have the following in your application.properties:

pcd-fiscal-year-reporting-dates-dir=

pcd.fiscal.year.reporting.dates.username=
pcd.fiscal.year.reporting.dates.password=


Remove SOLR Managed Schema

Removing the managed-schema generation. We currently don't have a use case for making changes to the schema via the api, and this is just making our workflow more complicated. See https://cwiki.apache.org/confluence/display/solr/Schema+Factory+Definition+in+SolrConfig for more info.

Coverage remained the same at 95.728% when pulling edfcc819ae1a57f8598b927a21a0427d743df95f on solr-additional-cleanup into 1f1e01fa8ed1dd6d2df12b3f3c691686680f676b on master.

Coverage remained the same at 95.728% when pulling 4ee0a2e91d4563cce7e4e24d0df1f6c6d0e43b5d on solr-additional-cleanup into 1f1e01fa8ed1dd6d2df12b3f3c691686680f676b on master.


Dropown for changing number of rows disappears when rotating to portrait mode

Dropdown for changing number of rows disappears when rotating to portrait mode  both on mobiles and tablets and also in the chrome simulator.  A refresh is needed for the drop-down to be displayed again.

Needs to be tested if it is a problem outside the client or not. If only in the client, we scope this out of phase 1


Water Sensors- SOW

Site never made initial connection.

Sarah emailed Cynthia 8/11 to ask about last check at this site. Cynthia responded that Esleyther had helped her take this site offline since it was never able to have cell signal. No files uploaded for this site yet.

Cynthia is downloading the data from the nodes today. When she was connected to the gateway she noticed there was an "SD error" message popping up. Upon further inspection, Cynthia noticed that the SD card is cracked and when she tried to take it out it wouldn't budge.

I checked over the data that was uploaded for this farm, Bare 2 was not reading any of the sensors, so no data is present on the node. (the node was on, but no sensors were detected).  Cover 2 and Cover 1 are perfectly good.
there is no file for Bare 1 they submitted a gateway file for ULW as Bare 1 SOW


Configs / Instructions to Replicated Experiments in Paper

I am hoping to reproduce the results. When can I expect the configs/instructions to replicate the experiments in the paper to be updated?

Hi @StephAO. Thanks for your interest. We will provide you with specific instructions to run all experiments within 1-2 days. Please stay tuned.
@gao-g @ataymano .

Thank you for the update @dkmisra
A few additionally notes I've found going through your repository:

The spacing and capitalization in your prompts is inconsistent (e.g. "ARTICLE: {input}" vs " Article:{input}")
Triple quotations keeps all white spaces contained within them, so indenting them on newlines to match the previous lines ends up leaving a a number of white spaces in weird places in the generated prompts.
The paper mentions that you use cosine similarity for document retrieval, and while the mpnet implementation does normalize the tensors, the Bert implementation does not, which means the Bert implementation is doing a dot product, not a cosine similarity. Further, it is standard to use the CLS token to compare strings, however, the current implementation averages all the tokens instead --- is there a reason for this?

Hi @StephAO,
Thank you for your interest!
Please find the experiments folder with the running instructions here
Please let me know if you have more questions or need any further help.

Hi @StephAO
I can comment on these other comments. By the way, thanks for very precise and helpful comments.

We'd standardize them and re-run the experiments. @gao-g and @ataymano (noting for next version). I doubt this will cause a significant difference but let's see what the new results say.

Would you happen to have an example of this? @ataymano

You are right that the code isn't normalizing BERT embeddings. This needs to be fixed. We'd do that in the next version.

We didn't compare against CLS embedding but the use of averaging makes sense to me and has been used in the literature for text encoding (e.g., 1, 2). A CLS token might be more focused on certain words, perhaps towards the boundaries of the text. In contrast, averaging gives more weight to each token but can dilute important words. I feel in hindsight we should have used something like BertScore.

@dkmisra Thank you for your reply. As you mention, I suspect most of these won't have any significant impact on the takeaways of the work.
For 2. all the prompts are in this format (for example ). Easy to fix by using a different notation (see below).
>>> edit_prompt = f"""Email: {output} \n
...                   Assume that you prefer {preference}.
...                   Please revise the above email to meet your style:"""
>>>
>>> edit_prompt
'Email: output \n\n                  Assume that you prefer preference. \n                  Please revise the above email to meet your style:'
>>> edit_prompt2 = (f"Email: {output} \n"
...                 f"Assume that you prefer {preference}. "
...                 f"Please revise the above email to meet your style: ")
>>> edit_prompt2
'Email: output \nAssume that you prefer preference. Please revise the above email to meet your style: '
>>>

Another quick issue. In the paper, you include "question answering style, direct, concise" as the preferences for Movie Review, however in the code, it is only "question answering style" (https://github.com/gao-g/prelude/blob/8fe20a8f1332090ccdd2f9498b7d7c33d0de7c49/src/task/summarization.py#L15)

I found your work very interesting, so I'm happy to help.
While unnecessary, if you would like to acknowledge me, my full name is Stéphane Aroca-Ouellette

We would totally love to acknowledge your help @StephAO. And please feel free to send us any papers you write in this space. Thanks for very useful feedback.


SDK Not Supported By Compiler

Hi there,
I am getting the following errors when using the latest version (10.19.0).

I have the latest Flutter / Dart version and the latest Firebase Plugins.
If I don't use this pre-compiled library (and use the default Firebase SDKs), these errors don't happen (but the building time is ridiculous).
Is this related to the XCode versions used to generate this artifact ?
Best!

A couple thoughts -
1- I don't believe anything higher than 10.16.0 is supported at the moment because of #79 - you might like #82 to get away from the whole idea of this build optimization hack and use a more industry-standard build-time optimization
2- there is not quite enough version information to go on (what version of macOS + Xcode resulted in that error message?)
3- it looks like at minimum you need to bump your IOS_DEPLOYMENT_TARGET to 12 to use the framework

@mikehardy updating to the latest Xcode and Mac didn't help, I am going to downgrade Firebase to 10.16.0. Thanks for your help!


fix: Remove default P.html = True from prototypes

Ever wondered why every module you want to access by URL without specifying a renderer throws out an error message like this?

Well, this pull requests removes the inconsequent Prototype.html = True from the List and Singleton prototype. The Tree prototype was always not by default visible to the html-render.
This is how the same call is rendered now:

Normally, all modules being visible to the standard html render have a Module.html = True on the bottom. Therefore, this little change wouldn't break too much. I'm also of the opinion, that it is a security issue.

Ever wondered why every module you want to access by URL without specifying a renderer throws out an error message like this?

honestly, not really

The Tree prototype was always not by default visible to the html-render.

I think this is due to historical reasons. the prototype is/was mostly only used for the menu and file module, so it wasn't necessary.

Normally, all modules being visible to the standard html render have a Module.html = True on the bottom

No, not really.
Like I don't write required=False on a bone every time, I rely on the inherited default value here. So IMO this would also be a breaking change.

As long as the HTML renderer is set as the default renderer, I don't really see the benefit of this PR and the security issue

Normally, all modules being visible to the standard html render have a Module.html = True on the bottom

No, not really. Like I don't write required=False on a bone every time, I rely on the inherited default value here. So IMO this would also be a breaking change.
As long as the HTML renderer is set as the default renderer, I don't really see the benefit of this PR and the security issue

For me, this is a security problem. By default, all modules shall not be accessible by any render, except the admin. In case the viur-base was used, there is a default view.html template, so the above call would render data which was not explicitly allowed to be rendered.
This is not a breaking change, it is a bug- and security-fix. Maybe, some projects which don't follow standards need to be fixed.

In the viur-meeting from Feb 2, 2024, we decided to apply this pull request.
Additionally, any P.admin = True-assignments should be removed, too.
For latter one, I would like to discuss why the vi-render is not simply renamed into admin, and aliased by vi to stay backward-compatible.


Allow users to set the scheduled executor service

grpc-based services use a ScheduledExecutorService. We should allow users to set an executor other than the default one in the service options.
Related to this: should we create an abstract option class for grpc-based services (that extends ServiceOptions?) That could expose some of the grpc-only configurations like setting the executor or converting the connection timeouts (see here).
/cc @aozarov @ajkannan

+1 for creating an abstract options subclass of ServiceOptions for gRPC configs

I have the feeling that we may need to have one top-level abstract service options and 2 other abstract sub classes for apiclient and gRPC.  Aside from executor there are other differences such as the way timeout is handled.

This was closed in #1011


Compile error on native ubuntu 2204

Hi,
i have to use the sick_scan_xd library on a native ubuntu c++ project to read out a LSM 1xxx. When I try to compile the library I get a strange error:
[  7%] Building CXX object _deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/driver/src/abstract_parser.cpp.o <command-line>: error: token "=" is not valid in preprocessor expressions /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/sick_scan_base.h:62:31: note: in expansion of macro ‘__ROS_VERSION’    62 | #if !defined __ROS_VERSION || __ROS_VERSION == 0       |                               ^~~~~~~~~~~~~ <command-line>: error: token "=" is not valid in preprocessor expressions /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/sick_ros_wrapper.h:118:5: note: in expansion of macro ‘__ROS_VERSION’   118 | #if __ROS_VERSION <= 1 // ROS-SIMU (native Linux or Windows) or ROS-1 (Linux only)       |     ^~~~~~~~~~~~~ <command-line>: error: token "=" is not valid in preprocessor expressions /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/sick_ros_wrapper.h:242:7: note: in expansion of macro ‘__ROS_VERSION’   242 | #elif __ROS_VERSION == 2 // ROS-2 (Linux or Windows)       |       ^~~~~~~~~~~~~ In file included from /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/abstract_parser.h:39,                  from /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/driver/src/abstract_parser.cpp:63: /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/sick_ros_wrapper.h:446:2: error: #error __ROS_VERSION undefined or unsupported, build with __ROS_VERSION 0, 1 or 2   446 | #error __ROS_VERSION undefined or unsupported, build with __ROS_VERSION 0, 1 or 2       |  ^~~~~ <command-line>: error: token "=" is not valid in preprocessor expressions /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/sick_ros_wrapper.h:453:5: note: in expansion of macro ‘__ROS_VERSION’   453 | #if __ROS_VERSION == 2 // ROS 2       |     ^~~~~~~~~~~~~ <command-line>: error: token "=" is not valid in preprocessor expressions /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/sick_ros_wrapper.h:491:7: note: in expansion of macro ‘__ROS_VERSION’   491 | #elif __ROS_VERSION == 1 // ROS 1       |       ^~~~~~~~~~~~~ In file included from /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/abstract_parser.h:39,                  from /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/driver/src/abstract_parser.cpp:63: /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/sick_ros_wrapper.h:503:10: fatal error: diagnostic_updater/diagnostic_updater.h: No such file or directory   503 | #include <diagnostic_updater/diagnostic_updater.h>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. gmake[2]: *** [_deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/build.make:76: _deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/driver/src/abstract_parser.cpp.o] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:1400: _deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/all] Error 2 gmake: *** [Makefile:136: all] Error 2
I have added the library by using cmpaddpackage as follows:
CPMAddPackage(   NAME sick_scan_xd   GIT_REPOSITORY "https://github.com/SICKAG/sick_scan_xd.git"   GIT_TAG master )
I have added the library to my project by:
target_link_libraries(   sick_scan_xd_lib )
Can anyone help me out?

I have answered it to my self. I forgot to set the ROS_VERSION ENV to 0.
But now I got another error:
[ 13%] Building CXX object _deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/driver/src/sick_generic_laser.cpp.o In file included from /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/ldmrs/sick_ldmrs_node.h:12,                  from /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/driver/src/sick_generic_laser.cpp:70: /home/vagrant/.cpm-source-cache/sick_scan_xd/9da84fc9d165813149d60f87a1b1a46864af7282/include/sick_scan/ldmrs/sick_ldmrs_driver.hpp:58:10: fatal error: sick_ldmrs/manager.hpp: No such file or directory    58 | #include <sick_ldmrs/manager.hpp>       |          ^~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. gmake[2]: *** [_deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/build.make:216: _deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/driver/src/sick_generic_laser.cpp.o] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:1400: _deps/sick_scan_xd-build/CMakeFiles/sick_scan_xd_lib.dir/all] Error 2 gmake: *** [Makefile:136: all] Error 2
How exactly is it possible to disable the LDMRS? I have set this:
option(BUILD_WITH_LDMRS_SUPPORT "Build ${PROJECT_NAME} with LDMRS support (ON, libsick_ldmrs from https://github.com/SICKAG/libsick_ldmrs required) or without LDMRS support (OFF)" OFF) if(WIN32)     set(BUILD_WITH_LDMRS_SUPPORT OFF CACHE BOOL "Build ${PROJECT_NAME} with LDMRS support (ON, libsick_ldmrs from https://github.com/SICKAG/libsick_ldmrs required) or without LDMRS support (OFF)" FORCE) elseif(LDMRS EQUAL 0)     set(BUILD_WITH_LDMRS_SUPPORT OFF CACHE BOOL "Build ${PROJECT_NAME} with LDMRS support (ON, libsick_ldmrs from https://github.com/SICKAG/libsick_ldmrs required) or without LDMRS support (OFF)" FORCE) else()     set(BUILD_WITH_LDMRS_SUPPORT ON CACHE BOOL "Build ${PROJECT_NAME} with LDMRS support (ON, libsick_ldmrs from https://github.com/SICKAG/libsick_ldmrs required) or without LDMRS support (OFF)" FORCE) endif()

Thanks for your feedback. Use cmake flags -DLDMRS=0 -DSCANSEGMENT_XD=0 to build sick_scan_xd without LDMRS and scansegment_xd support, which are not required for LMS 1xxx lidars. See https://github.com/SICKAG/sick_scan_xd/blob/master/INSTALL-GENERIC.md#build-on-linux-generic-without-ros for further options. Please remove all temporary build and cmake files from the build folder to ensure a complete rebuild.

Thanks for the quick reply. That worked perfectly fine. But is it possible to use the sick_scan_xd without installing it? When I use the CPMAddPackage I ran into the error mentioned here https://github.com/SICKAG/sick_scan_xd/issues/223#issuecomment-1770726130
For some reason in that case the compiler wants to have the sick_ldmrs/manager.hpp even if I have set BUILD_WITH_LDMRS_SUPPORT and BUILD_WITH_SCANSEGMENT_XD_SUPPORT = OFF in the CPMAddPackage options section.
Any idea?

It is possible to use sick_scan_xd without installation. Just make sure that the library can be found, i.e. environment variables PATH and LD_LIBRARY_PATH contain the sick_scan_xd build folder.
sick_generic_laser.cpp includes ldmrs-header, if LDMRS_SUPPORT is defined and not equal 0. It looks like LDMRS_SUPPORT is still defined within the CPM environment; maybe the CPM cache folder (/home/vagrant/.cpm-source-cache) needs to be cleared or removed to ensure a complete rebuild.


502 Bad Gateway

https://goreportcard.com

Thanks for reporting, we got the service back up and running now. We'll look into it to try and prevent it from happening again in the future.


Statistics navigation/drilldown suggestion

I found the navigation/drilldown for the existing statistics pages didn't work the way I expected (after coming back to the packages with fresh expectations after a while).
Problem:
You cannot drill down into the by-version statistics for a package from the package's overall statistics.
Repro:

Navigate to https://www.nuget.org/stats
Click on the downloads number for Newtonsoft.Json in the left-hand column (Downloaded Packages)
Click on a Version number in the table

Expected:
To be taken to the statistics page for that specific version
Actual:
Taken to the package details page for that version
Note:
You can get to the version-specific statistics page for package versions that make the Downloaded Package Versions list, but there's no drill down that gets you there for a version that isn't in that report (even though the page can render).

Site navigation issues are being fixed as part of the v3 gallery development.


Look into render props for auth

This could be a good way to use render props.

Using render props for authorization checks inside feature/add-user-roles-permissions. Will close when merged into develop.


actool: Add patch-manifest --ports and --isolators.

/cc @alban @jonboulle
Maybe can get this in as 0.6.1?

@jonboulle updated

@yifan-gu thanks for persevering. LGTM
LGTM

Oops,doubled up


Update 'joints' example

RAPIER.BodyStatus is currently undefined. This PR replaces RAPIER.BodyStatus by RAPIER.RigidBodyType.
The variable 'status' was also renamed accordingly.

Well spotted, thanks!


When support raster image support?

When support raster image support from Flare 1.1?

When support raster image support?

We've got no ETA on it just yet, but we're hoping to having it out soon!

We've got no ETA on it just yet, but we're hoping to having it out soon!

Thanks, is Flare-Flutter now support raste image?

Hi @zhangjunmax. Yes, Flare-Flutter does support raster images.

Hi @zhangjunmax. Yes, Flare-Flutter does support raster images.

Thanks, I will try Flare-Flutter, another question, is Flare-Flutter support runtime raster images replacement(from remote server)?

Hey @zhangjunmax we just merged a big update and this runtime now fully supports raster images!
Also, image replacement from the server is now available! This is the API, and works in conjunction with dynamic image support in the Flare editor.
Take a look at this Flare-Flutter example, the logic and the workflow are the same!


fixed signup page

fixes #18
Problem
earlier when a users clicked on the sign up button, the control wont go to the navigate function and stop there because of that users stay stuck in the signup page

Fix
just added a try catch around the setDoc() and now the control goes to the navigate function. so, if a user signups, he will be navigated to the search page and he wont stay stuck there

Thank you!


Add AnalysisAction and AnalyticResult

Background
Actions of performing analysis are very common across the targeted domain scope of UCO.
This could include analysis actions as diverse as file extraction analysis as part of digital forensics, human-based malware behavior analysis, ML-based multimedia classifiers, etc.
There is a need to express such analysis across domains, including digital forensics, cyber-investigation, cyber threat intelligence domain, risk, and security operations.
There is value in being able to clearly distinguish analysis actions from other forms of action, to constrain certain forms of relationships as to or from analysis actions specifically, and the ability to adorn such actions with analysis-specific properties.
There is further value in being able to pair the expression of such analysis actions with specific forms of expression of analysis results.
UCO does not currently provide capability to uniquely specify analysis-specific actions in a standard yet flexible form.
UCO would benefit from such capability to support a wide range of analysis actions and their results in a consistent yet flexible standardized form.
At its simplest level this could be illustrated by the following simple scenario:

Analysis action A was performed by B on object(s) C using instrument D at time E and location F and produced the analytic result G
The analytic result G of analysis action A conveys a simple statement of the analysis result

This general approach could then be tailored for specific forms of analytic result.
UCO would benefit immediately from the capability to specify analysis actions and analytic results for the specific case of ML classification such as multimedia classification.
A simple scenario for this would be something like:

An analyst has a photo image that they desire to know if there is any money displayed in the image
The analyst performs a multimedia classification analysis action on the photo image using a specific automated ML classifier at time E and location F and produced the analytic result G containing the classification results of the analysis
The analytic result G utilizes specialized property extensions (using core:hasFacet) of the general analytic result to convey what sort of artifact classification was performed and the confidence level that the targeted artifact is present in the analyzed photo image

The ability to express such ML classification analysis actions and analytic results supports other varieties of such analysis such as computed similarity classification analysis.
From the Casey and Bollé chapter titled "Formalising Representation and Interpretation of Digital Evidence to Reinforce Reasoning and Automated Analysis":

The simplest example is a computed similarity or ML classification. Figure 4 depicts such a scenario, with a similarity comparison meeting a preset threshold. Performing an AnalysisAction using an AnalyticTool to process input data and produce an AnalyticResult such as a similarity score that meets the threshold, establishing a Relationship between the inputs.

Figure 4: Simple example of an AnalysisAction operating on input data using an AnalyticTool to produce an AnalyticResult (e.g., similarity score or classification confidence). When a threshold is set and met by the AnalyticResult, a Relationship can be drawn between the inputs (e.g., similar emails).

Requirements
Requirement 1
Represent an analysis action of some performed analysis to produce an analytic result.
Requirement 2
Represent the analysis action of running an analytic tool on data to produce an analytic result.
Requirement 3
Represent the general analytic result of a general analysis action
Requirement 4
Represent the specific analytic result of a specific type of  analysis action
Requirement 5
Represent the specific analytic result (including type of classification and confidence in classification) of an automated multimedia classifier action
Requirement 6
Represent the specific analytic result (including types of classification and confidence in classifications) of an automated multimedia classifier action performing multiple classifications in a single pass
Risk / Benefit analysis
Benefits
This proposal provides a consistent and flexible capability for expressing different forms of analysis and their accompanying results. It would provide the ability to clearly distinguish analysis actions from other forms of action. It would provide the ability to constrain certain forms of relationships as to or from analysis actions specifically. It would provide the ability to adorn analysis actions and their accompanying analytic results with analysis-specific properties.
It would provide the specific capability to express ML classifier actions such as multimedia classification analysis and their specific analytic results in a standard form.
Risks
Might be duplicative of existing ML ontology work such as A MACHINE LEARNING ONTOLOGY (https://osf.io/preprints/frenxiv/rc954/download)
Competencies demonstrated
Competency 1
A user is looking to understand the details of some particular analysis that was performed.
Competency Question 1.1
What specific type of analysis was performed?
Result 1.1
Review core:name of the Analysis
Competency Question 1.2
Who performed the analysis?
Result 1.2
Review action:performer of the Analysis
Competency Question 1.3
What tools/instruments were used to performed the analysis?
Result 1.3
Review action:instrument of the Analysis
Competency Question 1.4
When was the analysis performed?
Result 1.4
Review action:startTime and action:endTime of the Analysis
Competency Question 1.5
Where was the analysis performed?
Result 1.5
Review action:location of the Analysis
Competency Question 1.6
In what environment was the analysis performed?
Result 1.6
Review action:environment of the Analysis
Competency Question 1.7
Was the analysis automated or manual?
Result 1.7
Review action:isAutomated of the Analysis
Competency Question 1.8
What was the input for the analysis?
Result 1.8
Review action:object of the Analysis
Competency Question 1.9
What was the result of the analysis?
Result 1.9
Review core:statement and any facets of the AnalyticResult
Competency Question 1.10
From which analysis did a particular AnalyticResult come from?
Result 1.10
Review aanalysis:originatingAnalysis of the AnalyticResult
Competency 2
A user is looking to understand the details of some ML classification analysis of digital photo content that was performed.
Competency Question 2.1
What is the result of ML classifier on photo?
Result 2.1
Classified as containing money with 0.9 confidence
Solution suggestion

Create a new "analysis" namespace to contain analysis-specific concepts
Create a new analysis:Analysis class as a subclass of action:Action to convey analysis actions
Create a new action:isAutomated boolean datatype property that would optionally (cardinality 0..1) go on any action:Action including analysis:Analysis to convey if the action is automated or manual
Create a new analysis:AnalyticResult class as a subclass of core:Assertion

making it a subclass of Assertion would enable it to optionally include a core:statement property making a summary statement for an AnalyticResult for cases where something simple is appropriate or to provide a simple summary even when more complex structured content is included via facets

Create a new analysis:originatingAnalysis object property (range of analysis:Analysis) that would optionally (cardinality 0..1) go on analysis:AnalyticResult to reference back to the Analysis action that it resulted from
Create a new analysis:resultContent object property (range of core:UcoObject) that would optionally (cardinality 0..*) go on analysis:AnalyticResult to contain any object content that resulted from the Analysis
Create a new analysis:AnalyticResultFacet as a subclass of core:Facet that would be abstract and serve as a basis for characterizing specific forms of analytic result
Create a new analysis:ArtifactClassificationResultFacet as a subclass of analysis:AnalyticResultFacet to convey results of classification analysis actions
Create a new analysis:classification object property (range of analysis:ArtifactClassification) that would optionally (cardinality 0..*) go on analysis:ArtifactClassificationResultFacet to convey one or more classification results
Create a new analysis:ArtifactClassification class to convey details of a single classification result
Create a new analysis:class datatype property (range of string) that would be required on analysis:ArtifactClassification and convey a specific classification type (e.g., money, face, car, water, etc)
Create a new analysis:classificationConfidence property (xsd:decimal) that would optionally (cardinality 0..1) go on analysis:ArtifactClassification to convey the confidence in the classification

Examples
First general scenario from Background above (in this case, manual software malware analysis within the Cyber Threat Intelligence application domain):
{
  "@graph": [
    {
      "@id": "kb:AnalyticTool-0b635b9f-bdb8-4492-9b4e-dec6797b82db",
      "@type": "uco-tool:AnalyticTool",
      "uco-core:name": "IDA Pro",
      "uco-tool:toolType": "binary code analysis tool",
      "uco-tool:creator": "hex-rays",
      "uco-tool:version": "7.7"
    },
    {
      "@id": "kb:Analysis-f365add7-1326-426f-9266-406bdeed86a1",
      "@type": "uco-analysis:Analysis",
      "uco-core:name": "Reverse engineer software to determine malicious intent",
      "uco-core:startTime": {
        "@type": "xsd:dateTime",
        "@value": "2022-05-12T10:21:00.00Z"
      },
      "uco-core:endTime": {
        "@type": "xsd:dateTime",
        "@value": "2022-05-14T15:58:00.00Z"
      },
      "uco-action:isAutomated": false,
      "uco-action:location": {
        "@id": "kb:9b82c2bc-10f7-47b2-81a8-443a9f458440"
      },
      "uco-action:performer": {
        "@id": "kb:Analyst-c1d5f9cc-10cd-4fdb-9570-e9d00e6df6f7"
      },
      "uco-action:instrument": {
        "@id": "kb:AnalyticTool-0b635b9f-bdb8-4492-9b4e-dec6797b82db"
      },
      "uco-action:environment": {
        "@id": "kb:Computer-e640f827-1f5b-4e8a-bd89-7afdf2c85caa"
      },
      "uco-action:object": [
        {
          "@id": "kb:Software1-2ef1d3c7-eb2d-470d-89ea-291daed6549b"
        }
      ],
      "uco-action:result": [
        {
          "@id": "kb:ProvenanceRecord-aa90afe6-9069-49bb-8ad8-b05d3f4f143b"
        },
        {
          "@id": "kb:AnalyticResult-67fb2d95-dc94-4833-a270-582c37feb879"
        }
      ]
    },
    {
      "@id": "kb:AnalyticResult-67fb2d95-dc94-4833-a270-582c37feb879",
      "@type": "analysis:AnalyticResult",
      "uco-analysis:originatingAnalysis": "kb:AnalyticTool-0b635b9f-bdb8-4492-9b4e-dec6797b82db",
      "uco-core:statement": "Software exhibits malicious intent"
    }
  ]
}

Second multimedia classification-specific scenario from Background above"
{
  "@graph": [
    {
      "@id": "kb:AnalyticTool-DAE5EE58-E5ED-4588-93BE-CDEC6FAA9C6A",
      "@type": "uco-tool:AnalyticTool",
      "uco-core:name": "Hansken",
      "uco-tool:toolType": "DFaaS",
      "uco-tool:creator": "NFI",
      "uco-tool:version": "1.0",
      "uco-core:hasFacet": [
        {
          "@type": "uco-tool:ToolConfigurationTypeFacet",
          "uco-tool:configurationSettings": [
            {
              "@type": "uco-tool:ConfigurationSettingType",
              "uco-tool:itemName": "classifier",
              "uco-tool:itemValue": "nfi-forensic"
            },
            {
              "@type": "uco-tool:ConfigurationSettingType",
              "uco-tool:itemName": "TrainingSet",
              "uco-tool:itemValue": "0.0.7"
            }
          ]
        }
      ]
    },
    {
      "@id": "kb:Analysis-7cd51fa7-63ee-4f40-a482-9ce8333c7556",
      "@type": "uco-analysis:Analysis",
      "uco-core:name": "compute string similarity",
      "uco-core:startTime": {
        "@type": "xsd:dateTime",
        "@value": "2022-05-10T08:49:00.00Z"
      },
      "uco-core:endTime": {
        "@type": "xsd:dateTime",
        "@value": "2022-05-10T09:54:00.00Z"
      },
      "uco-action:isAutomated": true,
      "uco-action:location": {
        "@id": "kb:ESC-6FAC81EF-0966-4F05-94BB-2A5D572513CA"
      },
      "uco-action:performer": {
        "@id": "kb:Analyst-13A167EE-D3B5-4AA4-B8BA-83C25F8B8FF4"
      },
      "uco-action:instrument": {
        "@id": "kb:AnalyticTool-DAE5EE58-E5ED-4588-93BE-CDEC6FAA9C6A"
      },
      "uco-action:environment": {
        "@id": "kb:Computer-533FA61A-BE79-469E-A05F-1A341848B925"
      },
      "uco-action:object": [
        {
          "@id": "kb:RasterPicture1-b67308c0-c31b-41a6-805a-10ec526ec8bc"
        }
      ],
      "uco-action:result": [
        {
          "@id": "kb:ProvenanceRecord-d628b0f6-686d-4d22-a577-ec737e5947bc"
        },
        {
          "@id": "kb:AnalyticResult-3205CB19-0820-4009-B70B-646DBD19598B"
        }
      ]
    },
    {
      "@id": "kb:AnalyticResult-3205CB19-0820-4009-B70B-646DBD19598B",
      "@type": "analysis:AnalyticResult",
      "uco-analysis:originatingAnalysis": "kb:Analysis-7cd51fa7-63ee-4f40-a482-9ce8333c7556",
      "uco-core:hasFacet": [
        {
          "@type": "uco-analysis:ArtifactClassificationResultFacet",
          "uco-analysis:classification": [
            {
              "@type": "uco-analysis:ArtifactClassification",
              "uco-analysis:class": "money",
              "uco-analysis:classificationConfidence": 0.997359037
            }
          ]
        }
      ]
    }
  ]
}

(Edit: Github presentation syntax and needed prefixes added by OC Chair.)
Coordination

Tracking in Jira ticket OC-246

[x] Administrative review completed, proposal initially announced to Ontology Committees (OCs) on 2022-06-13; revised Issue announced 2022-07-07.
[ ] Requirements to be discussed in OC meeting, 2022-07-12
[ ] Requirements Review vote has not occurred

[ ] Requirements development phase completed.
[ ] Solution announced to OCs on (TODO-date)
[ ] Solutions Approval to be discussed in OC meeting, date TBD
[ ] Solutions Approval vote has not occurred

[ ] Solutions development phase completed.
[ ] Implementation has not been merged into develop

[ ] Milestone linked
[ ] Documentation logged in pending release page

@cyberinvestigationexpress , there are a few questions the illustration JSON opens.

Is this proposing a new namespace with prefix analysis:?
Are the drafting:-prefixed concepts in-scope or out-of-scope  of this proposal?  For instance, the last I saw originatingAction, it was part of a proposal of mine that ended up being dropped on a new characteristic of Facets becoming understood.
How should core:confidence play into this?  I think the only place there is a demonstration of confidence is on Oresteia, and it's flagged as being known to be non-conformant.
How does drafting:class differ from core:tag?

I also have questions from your solution suggestion.

Your first suggestion is to add AnalysisAction to the Action namespace.  Why not the Analysis namespace?
Would there be a ClassificationResult class accompanying the ClassificationResultFacet class?

Last, I have a question on the potential scope of this class.  With the way this is illustrated presently, this proposal can help us associate confidence with a result that is structured closely to a tag.  The CASE Inference Proposal (which one of us needs to transcribe to Github from Confluence) associates a confidence with a result structure that is a significantly more complex stucture, able to be consumed as a graph.  Can you please include an illustration of how this money-with-0.99-confidence AnalyticResult could be used?  Is it possible to illustrate something with an AnalyticResult that doesn't look like a tag, or is this scoped to tag-like conclusions only?
I will schedule this for the OC call in a few Thursdays, but if there are no answers to the above questions, I will only give this 10 minutes of committee time.  I estimate this having a low chance of passing a Requirements Review vote before we see some further explanation.

A few suggestions for refining the proposal based on conversations that @cyberinvestigationexpress and I have had on this topic:

Create a new "analysis" namespace
Create a new analysis:Analysis class as a subclass of action:Action
Create a new analysis:AnalyticResult class as a subclass of core:Assertion

making it a subclass of Assertion would enable it to optionally include a core:statement property making a summary statement for an AnalyticResult for cases where something simple is appropriate or to provide a simple summary even when more complex structured content is included via facets

Create a new analysis:originatingAnalysis property (range of analysis:Analysis) that would optionally go on analysis:AnalyticResult to reference back to the Analysis action that it resulted from
Create a new analysis:resultContent (range of core:UcoObject) that would optionally go on analysis:AnalyticResult to contain any object content that resulted from the Analysis
Create a new analysis:AnalyticResultFacet as a subclass of core:Facet that would be abstract and serve as a basis for characterizing specific forms of analytic result
Create a new analysis:ArtifactClassificationResultFacet as a subclass of analysis:AnalyticResultFacet to convey results of classification analysis actions
Create a new analysis:classification property (range of analysis:ArtifactClassification) that would optionally go on analysis:ArtifactClassificationResultFacet (no max cardinality) to convey one or more classification results
Create a new analysis:ArtifactClassification class
Create a new analysis:class property (range of string) that would be required on analysis:ArtifactClassification and convey a specific classification type (e.g., money, face, car, water, etc)
Create a new analysis:classificationConfidence property that would optionally go on analysis:ArtifactClassification to convey the confidence in the classification

This would enable the immediate need to support expressing classification analysis results but do so in a way that sets us up to support a wide range of use cases going forward. The basic Analysis and AnalyticResult setup here is needed for many cyber application subdomains.

@cyberinvestigationexpress , @sbarnum:
Thank you for creating this Change Proposal. Unfortunately, I don't understand it.
My comment on this CP is focused on the Why of it. Without a proper description on its background and the Problem that currently exists, leaves us with insufficient criteria for not only developing the proper artefacts, but more importantly, we don't know how to value the result of the work in terms of the extent it achieves the user/business demands. There is a major risk in specifying requirements in terms of the perceived solution, because it overlooks the business value that one wants to achieve as well as other potential solutions that might be (more) appropriate in the context of use.
So I'd like to urge you to take the time to do the tedious work of fleshing out the Problem that is required to be solved, and the requirements that are to be met. In terms on an ontology, that translates to:

describing the problem in the background section;

(what goes wrong if we cannot classify, or, what can be achieved when we are capable of classifying analysis results)

fleshing out the (functional and possibly extra-functional) Requirements in terms of What it is that needs to be achieved (on the user & application level, not the technology level);

(what are the things that are to be classified, on the basis of what do we classify them, what kind of classifications do we expect to emerge or do we have fixed set of them, and what are the results of doing the classification)

describing the precise situation/case serving as an example about the kind of things in reality that apply (competencies);

(under what conditions will the classification be performed, who will be doing the classification, what data will be subject to classification)

and, using those (and possibly existing competencies), the questions with their anticipated answers that the ontology should understand and produce;

(formulated in plain English, you can apply ParticularConcepts that apply, using the exemplified case description as reference to show right and wrong answers)

My criterion for a properly formulated CP is whether I myself, as an outsider to the domain, can explain the gist of the CP to an insider. Please support me in achieving that goal, because it results for the community in a much clearer CP with much more down-to-earth discussions, reaching conclusions and agreements much faster and providing significant clarity to the developing team about the scope, depth and demand of the ontological artefacts.

The included example JSON-LD snippets appear to show some SHACL validation errors, and/or confusions of CASE and UCO concepts.  Specifically, a non-CASE action is generating a CASE ProvenanceRecord.  This isn't necessarily wrong (CASE's and UCO's SHACL doesn't disallow this).
If the uco-analysis:Analysis object is also classified as a CASE InvestigativeAction, this point is moot.

@cyberinvestigationexpress , @sbarnum - is there a reason the cited ontology in "A MACHINE LEARNING ONTOLOGY" was not proposed for adoption?  I am concerned with effort required in significant reinvention, but would appreciate understanding any risks with adopting another's solution.

Remark in the meeting on "A MACHINE LEARNING ONTOLOGY" is that its scope is more focused than the general analysis action's needs.

I've added this to the post-1.0.0 milestone, due to perceived backwards-compatibility with 1.0.0.  Though, if somebody is interested in implementing and testing this proposal by end of day Thursday, we can hold a Solutions Approval vote at next Thursday's meeting.

From the English definition of analysis:ArtifactClassification, analysis:class's value is meant to be a taxonomy member.  Yet, analysis:class is implemented as an any-xsd:string-permitted property.
This is another instance of UCO avoiding staying just outside of using taxonomies, such as would be encoded by SKOS narrower-broader concept sets, or OWL class hierarchies.
I appreciate that it may be impractical to require a machine learning algorithm to provide a structured hierarchy of all of its potential classification results encoded in an RDF syntax.  Strings are (by my understanding) a fairly guaranteed common-ground.
But, using strings for analysis:class imposes on the user that they provide their own mapping into a hierarchy, as an after-analysis step.
We should be aware that accepting this proposal with analysis:class introduces another usage of strings to represent taxons, and without such a mapping a user can't do things like determine whether there is any relationship between classification results (such as "Sedan" being a specialization of "Car").
I think this is something we would need to revise in the future, if not now.


[Business Api] add ForeignExchange resource

Description
Related Issue: https://github.com/moraki-finance/revolut-connect/issues/26
Add the ForeignExchange resource, to retrieve information on exchange rates between currencies and exchange currencies.
Implementation
Revolut::ForeignExchange.rate(
  from: "EUR",
  to: "USD",
  amount: 100
)

Revolut::ForeignExchange.exchange(
  request_id: "49c6a48b-6b58-40a0-b974-0b8c4888c8a7", # The ID of the request, provided by you. It helps you identify the transaction in your system.
  from: {
    account_id: "8fe12333-5b27-4ad5-896c-38a25673fcc8",
    currency: "USD"
  },
  to: {
    account_id: "b4a3bcd2-c1dd-47cc-ac50-40cdb5856d42",
    currency: "GBP",
    amount: 10
  },
 reference: "exchange"
)

Screenshots
Revolut::ForeignExchange.exchange() call:

Revolut::ForeignExchange.rate()  call:

Testing check:

Checks

[x] Have you followed the guidelines in our Contributing section?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Nice! Thank you! There's only one lint failing.


Way to ignore specific line

Is there a way to ignore a specific line (or region of code in a file) to not be processed by autoflake?

You can add a # noqa comment: https://github.com/PyCQA/autoflake/blob/HEAD/README.md#excluding-specific-lines

Thanks. Completely missed that somehow.

@csm10495 no worries, it happens! 😁


Governance. Delegation. Crash when try to open delegator card.

Description
Crash when open delegator card.
https://github.com/novasamatech/nova-spektr/blob/ddfa3266133bcb8670bfd51587f837e691145df4/src/renderer/widgets/DelegateDetails/ui/YourDelegations.tsx#L74
https://github.com/user-attachments/assets/fb6ea073-9df8-4b31-98a9-aa77b013ebd3
Steps to Reproduce

Delegate
Remove delegation
Go to Governance page
Click "Add delegation"
Open delegator card

Expected Behavior
Show add delegation button
Actual Behavior
Crash with TypeError: Cannot read properties of undefined (reading 'balance')
Environment
https://github.com/novasamatech/nova-spektr/commit/c8a8e989a58c4798deb402b449e7f8cc50721236

Status verification: ✅


Software license needed for sharing files

Hi,
@matthewjackowski thanks for putting the Pelican Dockerfile together.
It looks wonderful but can you please add a license to your repo and docker image build?
Right now it is not legal for other people to use your code.
Thanks,
Karen

@karenyyng Thanks for pointing this out!  I added a permissive BSD-2 clause.  I'm glad you found this project useful!

I appreciate the quick response :)