dynamic inputs for scan job schedule

@susanev will fill in more details in a bit
Overview
Currently, the scan job schedule inputs are not dynamic which means you can choose a non-valid date.
Design Details

On month and year selection change the day options should be updated to always be valid, if the user had already selected a day option that is no longer valid, it should reset to the last day of that particular month.

this work has been deprioritized, so closing.


hickory-dns failing due to missing config options and defaults

Describe the bug
There's a number of options that are missing in nixos/modules/services/networking/hickory-dns.nix that causes the package to build, and defaults missing that cause the service to fail to start if using a default configuration, and it is not so straight-forward to create the files in the default locations.
       error: The option `services.hickory-dns.settings.zones."[definition 1-entry 6]".stores' does not exist. Definition values:
       - In `/etc/nixos/configuration.nix':
           {
             name_servers = [
               {
                 protocol = "udp";
                 socket_addr = "<IP_ADDRESS>:53";
           ...

Steps To Reproduce
Steps to reproduce the behavior:

Try to enable the service along with the default zones.
Try to use the zone.store option such as outlined under Additional Context

Expected behavior

Enabling the service along with references to default zone files should result in the service successfully starting
Using options that hickory-dns supports should not cause build failure

Additional context

Zone definition files
There's no way to configure the files for /var/lib/hickory-dns, and they aren't auto-created either.

A workaround is to change the default directory to etc and then configure the zones under environment.etc. Since the zone definitions are how this works, either there needs to be a way to configure the zone definitions from configuration.nix, or the default location for zones should change to /etc/hickory-dns

Options that are used in the examples should be added to hickory-dns.nix
https://github.com/hickory-dns/hickory-dns/blob/main/tests/test-data/test_configs/consulting_blocklist.toml
https://github.com/hickory-dns/hickory-dns/blob/main/tests/test-data/test_configs/chained_blocklist.toml
https://github.com/hickory-dns/hickory-dns/blob/main/tests/test-data/test_configs/example_forwarder.toml
https://github.com/hickory-dns/hickory-dns/blob/main/tests/test-data/test_configs/example_recursor.toml

There should probably be some method of generating keys but that's a different issue.

Metadata
Not necessary
Notify maintainers
@uninsane

Note for maintainers: Please tag this issue in your PR.

services.hickory-dns = {
  enable = true;
  settings = {
    directory = "/etc/hickory-dns";
    zones = [
      {
        zone = "localhost";
        zone_type = "Primary";
        file = "default/localhost.zone";
      }
      {
        zone = "0.0.127.in-addr.arpa";
        zone_type = "Primary";
        file = "default/<IP_ADDRESS>.zone";
      }
      {
        zone = "<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.0.0.0.ip6.arpa";
        zone_type = "Primary";
        file = "default/ipv6_1.zone";
      }
      {
        zone = "255.in-addr.arpa";
        zone_type = "Primary";
        file = "default/255.zone";
      }
      {
        zone = "0.in-addr.arpa";
        zone_type = "Primary";
        file = "default/0.zone";
      }
      {
        zone = ".";
        zone_type = "Forward";
        stores = {
          type = "forward";
          name_servers = [
            {
              socket_addr = "<IP_ADDRESS>:53";
              protocol = "udp";
              trust_negative_responses = false;
            }
            {
              socket_addr = "<IP_ADDRESS>:53";
              protocol = "tcp";
              trust_negative_responses = false;
            }
          ];
        };
      }
      {
        zone = "example.com";
        zone_type = "Primary";
        file = "example.com.zone";
        #allow_update = true;
      }
    ];
  };
};

  environment.etc = {

    "hickory-dns/example.com.zone".text = ''
      $TTL 86400
      @   IN  SOA ns1.example.com. admin.example.com. (
<PHONE_NUMBER> ; Serial
              3600       ; Refresh
              900        ; Retry
              1209600    ; Expire
              3600       ; Minimum TTL
          )
          IN  NS  ns1.example.com.

      @   IN  A   <IP_ADDRESS>
      *   IN  A   <IP_ADDRESS>
    '';

    "hickory-dns/default/0.zone".text = ''
      $TTL 3D
      @               IN      SOA     example.com. root.example.com. (
                                      199609203       ; Serial
                                      28800   ; Refresh
                                      7200    ; Retry
                                      604800  ; Expire
                                      86400)  ; Minimum TTL
                              NS      example.com.
    '';

    "hickory-dns/default/<IP_ADDRESS>.zone".text = ''
      $TTL 3D
      @               IN      SOA     example.com. root.example.com. (
                                      199609203       ; Serial
                                      28800   ; Refresh
                                      7200    ; Retry
                                      604800  ; Expire
                                      86400)  ; Minimum TTL
                              NS      example.com.

      1                       PTR     localhost.
    '';

    "hickory-dns/default/255.zone".text = ''
      $TTL 3D
      @               IN      SOA     example.com. root.example.com. (
                                      199609203       ; Serial
                                      28800   ; Refresh
                                      7200    ; Retry
                                      604800  ; Expire
                                      86400)  ; Minimum TTL
                              NS      example.com.
    '';

    "hickory-dns/default/localhost.zone".text = ''
      $TTL 3D
      @               IN      SOA     example.com. root.example.com. (
                                      199609203       ; Serial
                                      28800   ; Refresh
                                      7200    ; Retry
                                      604800  ; Expire
                                      86400)  ; Minimum TTL
                              NS      example.com.

      localhost.              A        <IP_ADDRESS>
                              AAAA     ::1
    '';

    "hickory-dns/default/ipv6_1.zone".text = ''
      $TTL 3D
      @               IN      SOA     example.com. root.example.com. (
                                      199609203       ; Serial
                                      28800   ; Refresh
                                      7200    ; Retry
                                      604800  ; Expire
                                      86400)  ; Minimum TTL
                              NS      example.com.

      1                       PTR     localhost.
    '';
  };

thank you for the detailed bug report!
i've addressed some of this in https://github.com/NixOS/nixpkgs/pull/363001, please do give that a look if you're able.

Zone definition files: There's no way to configure the files for /var/lib/hickory-dns, and they aren't auto-created either.

it seems you found the way to do that in your example. i would like this to be easier, not sure the best solution.

is /etc/zones a standard of any sort? if that's used by other DNS servers (like bind), that seems a good default.
if not, could we work with upstream and convince them to search for zones along multiple paths? right now, they hardcode a single default, /var/named, into bin/src/lib.rs, and that's not really better w.r.t. the issues you highlight.

Options that are used in the examples should be added to hickory-dns.nix.

for now i've created https://github.com/NixOS/nixpkgs/pull/363001 to ensure users can specify options not known to the nixos module. manually enumerating all the config options in the nixos module comes with some downsides -- for example, the bug you report here only occurs because the module manually specified (the wrong type for) settings.zone: if the module had specified only settings, as a freeform type, you would have been able to put anything you like into the zone field.
explicitly declaring a few of the most commonly used options can help with discoverability though, so it's a balancing act. if you have a proposal for a specific list of options to declare, i'm open to that.

There should probably be some method of generating keys but that's a different issue.

this part is beyond my knowledge, but i'm happy to review solutions should anyone want to tackle this.

The standard in this case is that there would be several zone files in /var/lib/hickory-dns/default, which were included up above, that would be available to selectively use in the config.
According to the example config they have, those defaults should exist and be enabled in pretty much every case.
Any user configurations are typically placed in either /var/lib/hickory-dns or some subfolder in there, but the config does allow for absolute paths per-zone. I figured that we'd want to stick with that default but I'm not sure if there's a good way for a user to create the zone files within configuration.nix

Thanks, I'll give #363001 a shot once I figure out how to use it 😆

The SSL key thing is more of a minor point but in order to do some of the TLS stuff some keys have to be generated, and I imagine that would have to be handled in here, but that can be an issue for someone else 😉

Well I've never tried to test a nixpkg PR before, really struggling with getting it to work right.
With that being said, I tested the following /etc/hickory-dns/config.toml by just running the service manually (not using nixos-rebuild) and it worked, so as long as I can either point it to an existing config or have the following
      {
        zone = ".";
        zone_type = "Forward";
        allow_update = true;
        stores = {
          type = "forward";
          name_servers = [
            {
              socket_addr = "<IP_ADDRESS>:53";
              protocol = "udp";
              trust_negative_responses = false;
            }
            {
              socket_addr = "<IP_ADDRESS>:53";
              protocol = "tcp";
              trust_negative_responses = false;
            }
          ];
        };
      }

Write the following TOML
[[zones]]
zone = "."
zone_type = "Forward"
stores = { type = "forward", name_servers = [{ socket_addr = "<IP_ADDRESS>:53", protocol = "udp", trust_negative_responses = false },
                                             { socket_addr = "<IP_ADDRESS>:53", protocol = "tcp", trust_negative_responses = false }] }

Then it should work just fine.
dig @<IP_ADDRESS> google.com

; <<>> DiG 9.18.28 <<>> @<IP_ADDRESS> google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13606
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1232
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             219     IN      A       <IP_ADDRESS>

;; Query time: 39 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>) (UDP)
;; WHEN: Sun Dec 08 06:36:18 CST 2024
;; MSG SIZE  rcvd: 65


Bump node version for typescript publish

Needed for latest version of npm

Summary

Release Note

Documentation

@haydentherapper I wouldn't worry about updating the version value in the lock file. It's not part of the published package so it doesn't really matter.
node 18 is going to be good for another year or so, so I wouldn't worry about 20 yet.

thank you!


upload file change not working version new vscode

hi, button upload file change to day not working in version 1.37.1 vscode.
tks


Design the home page UI of the website

I am a GSSoC'22 contributor and I want to design the home page UI of DoctorVerse website
Kindly assign me this issue

Hi @mohammadshaad, go for it & happy coding 😄

I will be doing the designing part not the coding 😅

hi @mohammadshaad any update on it ?

hi @mohammadshaad any update on it ?

I will definitely make a PR tomorrow
Actually I was busy in college projects so forgot to make the PR although the design is ready


Not showing up in post processing drop down list

This is a very clever method and I can't wait to try it out. I followed your isntructions and have the python script saved inside the scripts directory. I ran Cura 4.8, sliced a cyliner, clicked on Extensions > Post Processing > Modify Gcode and clicked on add script. GradientInfill was not there. Restarted Cura. Same result. Rebooted everything. Same thing or did I mess up somewhere?

There is an error loading the script. If your script file is not called 'GradientInfill.py', it will fail to load.
Click 'Help' at the top and then 'Show Configuration Folder'. From there, open the cura.log file in notepad and do a search for text for 'GradientInfill' and it will jump you to the part explaining what the error is.

To get it to show up in the latest version of Cura, you have to add a small bit of code in the GradientInfill section:
Add the folowing:
def init(self):
super().init()
before the section for:
def getSettingDataString(self):
restart Cura, and it should show up in the scripts section now.


scanr to compliment Enum.scan

Would be nice to have a right scan

Might just submit this to the standard lib...


Wishlist: add authors to the page where public templates are browsed

This information can be extracted from Q. 6 (authors)

Add author's name to registration form.

New idea: it would probably better that a list of contributors to creating the template is here, and not authors of the study. The two teams could be different!


Is this library compatible with .Net Framework 4.7.2? i was able to use it with .Net Core 6 , worked flawlessly but facing issues with .Net Framework, or is there any workaround?

Is this library compatible with .Net Framework 4.7.2? i was able to use it with .Net Core 6 , worked flawlessly but facing issues with .Net Framework, or is there any workaround?

Hi @amitsahu-work - Unfortunately not.  This library was built against .NET 6.0 which implements .NET Standard 2.1 (see here).  And .NET Framework doesn't support this latest standard (see here).

Hi @amitsahu-work - Unfortunately not. This library was built against .NET 6.0 which implements .NET Standard 2.1 (see here). And .NET Framework doesn't support this latest standard (see here).

hey @pglombardo  can you suggest a mqtt client library for .Net Framework 4.7.2 which supports persistence of messages while disconnected

"persistence of messages while disconnected"

This could mean a couple thing but I don't know of any C# client that has local file persistence.  I'd like to add that to this client eventually but there is no ETA currently.
Also note that the HiveMQ broker will queue Quality of Service level 1 and 2 messages when the client goes offline.  Once you reconnect (with CleanStart=false) all of the queued messages will be delivered upon reconnecting.
See the ConnectReceiveAndPublish example that offers a bit more explanation and code.
The queue size and discard strategy can be configured in the HiveMQ broker.  See the documentation here.

"persistence of messages while disconnected"

This could mean a couple thing but I don't know of any C# client that has local file persistence. I'd like to add that to this client eventually but there is no ETA currently.
Also note that the HiveMQ broker will queue Quality of Service level 1 and 2 messages when the client goes offline. Once you reconnect (with CleanStart=false) all of the queued messages will be delivered upon reconnecting.
See the ConnectReceiveAndPublish example that offers a bit more explanation and code.
The queue size and discard strategy can be configured in the HiveMQ broker. See the documentation here.

Thanks @pglombardo  i have explored that option , it seems HiveMQ .net library does not support .net framework 4.7.2, if you have anything else in mind would appreciate

Hi @amitsahu-work if you have a HiveMQ broker license, contact your sales rep and have the request communicated.  Possibly we can get in a FR to add legacy support.


Add some engine jobs that run with Oracle GraalVM

Closes #9266.
Pull Request Description
Adds Oracle GraalVM configuration for some backend jobs. Oracle GraalVM jobs run only on Linux so far. The old jobs use GraalVM CE.
Important Notes

The JDK to download and use is deduced from the JAVA_VENDOR environment variable. By default, GraalVM CE is used.
sbt can be started with both GraalVM CE and Oracle GraalVM without any warnings.

If you try to start sbt with JDK from a different vendor, but with the same Java version, a warning is printed.

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[ ] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Oracle GraalVM seems to be downloaded and I assume we'll be green. The same applies for scala tests on Oracle GraalVM.


Update to latest version of 3rd party dependencies

VAULT_VERSION=1.5.3 --> 1.7.1
CONSUL_VERSION=1.9.1 --> 1.9.5
REDIS_VERSION=6.0.9-alpine --> 6.2.3-alpine
KONG_VERSION=2.3-alpine --> 2.4.0-alpine
MOSQUITTO_VERSION=1.6.3 --> 2.0.10

There are some breaking changes in Vault API JSON response for the version after 1.6.x  if I remember right. So we need to fix these first before we can upgrade Vault beyond 1.5.x

@jim-wang-intel , Interestingly it doesn't look to be an issue. PR #77 is passing Smoke Tests.
Maybe Vault reverted that change since the until 2.0 version since it is a breaking change. Thought I had head something about that. @bnevis-i any insight here.?

@jim-wang-intel , Interestingly it doesn't look to be an issue. PR #77 is passing Smoke Tests.

@lenny-intel   ok, but passing TAF doesn't mean we don't have an issue here- maybe TAF doesn't cover test that part of code.  I think we need to look deeper into it.

Predicted disaster with the Vault version change didn't occur.  Still seems to be using the same json keys as the older versions.

@jim-wang-intel , that issue would tank security services to start-up. @bnevis-i agrees and has closed his issue. PR merged.

Neglected to rebuild the compose files in the #77 so reopening this issue and submitted #78

@jim-wang-intel , that issue would tank security services to start-up. @bnevis-i agrees and has closed his issue. PR merged.

awesome, then no more concerns from me, thank you and @bnevis-i .


CLI available?

Is there a CLI available?
Regards
Chris

I think you can easily embed this lib to a customized cli application.


Added simplified Chinese translation

.

Oh didn't realize that GH just submitted the comment on its own. oops
Anyway IMO this is not a translation. You just interpreted what the items and blocks do and described them as literally as possible, while completely ignoring the original, albeit somewhat flowery, prose. Please try and respect the original text a bit more next time.

Oh didn't realize that GH just submitted the comment on its own. oops
Anyway IMO this is not a translation. You just interpreted what the items and blocks do and described them as literally as possible, while completely ignoring the original, albeit somewhat flowery, prose. Please try and respect the original text a bit more next time.

I'm sorry for the incomplete translation. It was thoughtless on my part.


Test multithreading

This pull request makes the tester run all tests, that currently work multithreaded, with 3 threads.
We should eventually get rid off all the
dealii::MultithreadInfo::set_thread_limit(1);

Codecov Report

Merging #183 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #183      +/-   ##
==========================================
+ Coverage    87.3%   87.34%   +0.03%
==========================================
  Files          53       53
  Lines        2891     2899       +8
==========================================
+ Hits         2524     2532       +8
  Misses        367      367

Impacted Files
Coverage Δ

tests/hierarchy_driver.cc
45.39% <100%> (+0.33%)
:arrow_up:

tests/test_hierarchy.cc
86.31% <100%> (+0.34%)
:arrow_up:

Continue to review full report at Codecov.

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

Need to create an issue to keep track of these


rueidis doesn't expose tmp query structs in internal/cmds, making it hard to construct the query dynamically

for example, we don't know how many identifiers would be returned ahead of time and need to construct the query dynamically.
Is there any method to do this without exposing cmds? Thanks.

Hi @m3ngyang,
Could you provide an example command you want to send and which part of it should be dynamically constructed?
BTW, You always can use https://github.com/rueian/rueidis#arbitrary-command.

I see. I can use arbitrary-command to concatenate an original query.


[TASK] Weird darkmode look

Estimated story points: 1
Description

The darkmode should not look that weird.

Acceptance criteria

The dark mode does look consistent.

time: 1h

time: 1h


Add license checks for Arcs

Introduce js-green-licenses at version 0.5.0
Add a stub for test:licenses in package.json
Whitelist WTFPL license usages for now

Addresses #1724

Ready for re-review.

Adds sigh licenses task
Updates server packages to eliminate some licenses
Adds whitelist for existing usages.

Test can be enabled once google/js-green-licenses#96 is fixed.


Use V2 for the publishing-api to write content to the content store

:+1: looking good. Few minor comments left. Can you add some context to the commit message and PR?

:+1: :fireworks:


Spacing field transport auto doesn't work

Hi (again) Ari,
The 'transport' => 'auto' mode on spacing field seems not working. Is it disabled or a bug?

Have you tried the develop branch?
I believe this one was already fixed...


Decode single-quote unicode code points

These changes should address issue #3.

"roc check main.roc" and "roc test main.roc" seems to be hanging. I had run the tests only on the Rvn.roc file before commiting.
Will take a look later.

This looks great so far, thanks so much!


Missing Prism-Text Asset

Just noticed a missing asset within chrome inspector. The CDN link is no longer available.
GET https://cdnjs.cloudflare.com/ajax/libs/prism/1.15.0/components/prism-text.min.js net::ERR_ABORTED 404

please don't use
```text
your text here
```
just use
```
your text here
```

or ```json


added SearchTag

Added this function to use 'Search by TAG' in NakamoriPlugin 1.1.8

Those fixes are needed for Nakamori Plugin version 1.2.3 to work properly

Fixed Typo in https://github.com/bigretromike/jmmserver/commit/9937bbc209b4720777a933fbfdc4036b01c5f2da


[doc] Develop ACC task.

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Add Develop an AdmissionCheck Controller task page.
Which issue(s) this PR fixes:

Fixes #2932
Special notes for your reviewer:
Does this PR introduce a user-facing change?

None

/cc @tenzen-y

I just noticed the original discussion motivating the effort: https://github.com/kubernetes-sigs/kueue/discussions/2699 which focuses on documenting the process of adding external controllers.

I just noticed the original discussion motivating the effort: #2699 which focuses on documenting the process of adding external controllers.

We could reference some documentation that describes how e controller can be created an deployed and so on maybe something from kubebuilder book , do you know a good link for that? (In my opinion kueue's documentation should not be the place one learns how to create an operator )

LGTM I think we could expand it to better describe the case of building an external ACC, similarly as we do for Job framework, but I think we can expand it later when we have such examples. I consider it a good starting point for future extensions.
Leaving tagging to @tenzen-y or @alculquicondor in case they have more comments.

I guess that we may be able to provide good examples and more informable documentation after we finalize this: https://github.com/kubernetes-sigs/kueue/pull/2458
Anyway, this document looks good to me.
/cherry-pick website

/cherry-pick website


Unskip building horizontest container

Unskipping building horizontest container as we are no more facing issue seen https://issues.redhat.com/browse/OSPCIX-378 to build the horizontest container while building the tcib containers. Previously the issue was due to https://pypi.org/project/setuptools/71.0.1/ which was yanked
Resolves OSPCIX-378
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

recheck

Horizontest container built successfully: https://logserver.rdoproject.org/31/2131/e4095a4bbef3a8366195aafa222f0f86ed18d839/github-check/cifmw-tcib/27ddf94/ci-framework-data/logs/776988d8-89ed-40b4-94e9-9c52b6495b70/base/os/horizontest/horizontest-build.log
/lgtm
/approve


Open/Managed access Data Policy for HCA DCP, available on contribute.data

As a data submitter to HCA DCP,
I would like to find out what the HCA DCP data policy is with regards to:

what types of data are suitable for submission to the DCP, especially with regards to open/managed access
what is considered identifiable data
how to avoid breaking GDPR laws unintentionally

Acceptance criteria:

[ ] stakeholders like T Burdett are happy with the wording
[ ] potential contributors are clear with the rules on submitting their data

We have chatted about using the existing content on GDPR from Wrangler SOP docs, and accommodating it to contributor audience...
Examples: https://www.ebi.ac.uk/fg/annotare/help/uhts_submissions.html
https://ega-archive.org/privacy-notice
https://docs.google.com/document/d/1YrQtCnTIdpRnNCbj_pb5ZJJYoPLS3f7it2ry1Im7EHw/edit#heading=h.mz3q1vll2r1z (DCP approach to identifiable human data)


Extimg-patch

Related:

Ticket 1
Ticket 2

Issue

Solution

Impact

Usage Changes

Considerations

Testing

@nlemoine, all - I am not too happy with this "null-handling" - please see my comments in the original patch I submitted: https://github.com/timber/timber/pull/2818#issuecomment-1772929850

coverage: 88.515% (-0.007%) from 88.522% when pulling 7315b6b7cab57d3d893ddc9c563da788e49a95a5 on extimg-patch into 9054d6664e4895b73207ba0925d7ede437822767 on 2.x.


Google Classroom: create free courses for CoCo as well

For some unknown reason, createFreeCourseInstances was only called in Ozaria.
By this fix course instances will be created for all free courses at classroom creation.

How would it have ever worked before?

@nwinter no idea. Maybe it didn't worked on the new dashboard for coco.


Graceful shutdown doesn't shutdown at all

Hello,
I have followed the documentation but I don't see to be able to exit the process with a graceful shutdown.
The code in the shutdown block never gets executed. Last line does but the process does not exit.
// if both buttons are pressed, disconnect:
if (left && right) {
process.once('SIGTERM', function(sig) {
kue.shutdown(5000, function(err) {
console.log('Kue shutdown: ', err || '');
process.exit(0);
});
});
tag.disconnect();
}
Any help is wildely appreciated.
thx

Is your shutdown callback getting called? (do you see 'Kue Shutdown' at console?)

The entire code in the process.once block doesn't get called (sorry I implicitly implied that some gets called in my previous statement) - it doesn't shuts down at all.

process.once('SIGTERM', function(sig) will be called when you send a SIGTERM signal to your node.js process which can be done by pressing CTRL+C  in the terminal which you process is running.
This is nothing to do with Kue.

Thank you for the explanation, now I understand how it is suppoesed to be used.
What would be the recommened way to shutdown at will (exist the process naturally and not by sig.)?

kue.shutdown(2000, function(err) {
  console.log('Kue shutdown: ', err || '');
  //process.exit(0); you should not need this line
});


Added 'preferredAuthentications' option to camel-jsch

This is a simple change to pass a new config option through to JSch. We need to set the 'preferredAuthentications' option to override the default order on our servers, specifically to prevent a kerberos password prompt being shown.
More details here...
http://stackoverflow.com/questions/29669459/skipping-kerberos-authentication-prompts-with-jsch
Regards,
James

Thanks @the-james-burton , I'll review ASAP.

Thanks :-)

Awesome, thanks for reviewing and merging so quickly!

Thanks for your contribution! It will be available in Camel 2.19.0 :-)


How to make a multi-thread application with C, accessing a LevelDB?

Hi,
I am a new with leveldb.
Is there another option to make a multi-thread application accessing a LevelDB Database?
Any ideas or sample code would be extremely helpful.
Thank you so much

See the concurrency section of the documentation.

Hello, @cmumford ! Thanks for your great work with leveldb.
I'm not a native speaker of either English or leveldb. So, I'm confused by the phrasing about Concurrency in the text that you quoted: there's "different threads may write into or fetch iterators or call Get on the same database without any external synchronization", but there's also "However other objects (like Iterator and WriteBatch) may require external synchronization."
So, my question is: Is there a way to use leveldb's concurrent abilities while using iterators ?
Could you please be as kind as to point me to a sample code where this question is enlightened ?
Thank you,
Hilton

Requests for specific sample code are best suited for StackOverflow.

Hi, @pwnall  !
What about requests for explanation of documentation ? Are they fit for these issues ?


Fix #2749 - Cython 0.29 broke support for C++ enum classes.

@orivej @da-woods

Note that the GCC_DIAGNOSTIC macro is not necessarily defined, it was local to a specific utility code section which only gets added conditionally. I renamed it and made it available for other utility code now, see a2b2efca3ef268cb29bd9bb4335384acf5dd3b4f.
Could you please rebase (or merge) your branch on the latest master,  add the //@requires: GCCDiagnostics dependency, and adapt the macro name in your change?

@scoder Thanks, done.

Thanks!

I was wondering - should this - and the commit it depends on - be backported to the 0.29.x branch?
I'm not familiar with the workflow but it looks like the master branch corresponds to Cython 3 right?

Yes, I picked it over.

Great, thanks!


UX Improvement: Add a home dashboard to grafana

Right now when users open grafana there is pretty much a blank page. We can add a home dashboard that at least lists all the istio dashboards so they don't have to dig through home > dashboards > istio. We are all probably mostly familiar with this by now, but I have seen people, including myself, confused by this.
One example: https://istio.teststats.cncf.io/d/8/dashboards?refresh=15m&orgId=1

Home dashboards are per-user or per-org, as I understand it. And there is no good way to set them via the provisioning process, meaning that it would require a series of API calls at grafana startup to star the appropriate dashboard and then set it as the org default.

That makes sense. if that is the case this probably isn't feasible so you can close it if you want

OK. I'll close it for now, but continue to think about better UX for the dashboard consumption.


[Code Addition Request]: Automate Workflows through Web Scraping

Have you completed your first issue?

[X] I have completed my first issue

Guidelines

[X] I have read the guidelines
[X] I have the link to my latest merged PR

Latest Merged PR Link
https://github.com/UppuluriKalyani/ML-Nexus/pull/324
Project Description
Description:
I propose developing a web scraping tool to automate workflows within PyVerse. This tool will extract data (e.g., prices, news, or stock data) from static and dynamic websites, store it for analysis, and run periodically using schedulers like cron or Task Scheduler.

Tech Stack:

Python Libraries: requests, BeautifulSoup, Selenium
Scheduling: cron (Linux) / Task Scheduler (Windows)
Error Handling and Logs: logging module

Approach:

Identify websites to scrape based on user needs (e.g., financial or product data).
Build modules for scraping both static and dynamic pages.
Implement automated scheduling with logging for status tracking.
Create detailed documentation and examples to guide users.

How This Helps Users:

Automates repetitive data extraction tasks.
Saves time and ensures users always have the latest data for analysis.
Encourages contributions from beginners and advanced users alike through modular code and documentation.

Please assign this issue to me so I can begin implementation.
Full Name
Sanchit Chauhan
Participant Role
GSSOC, HACKTOBERFEST

Hi @UTSAVS26 ,
Thank you for assigning the issue! I’d like to kindly request an update to a level 2 label. The project involves web scraping, which requires handling both static and dynamic content using requests, BeautifulSoup, and Selenium. Additionally, I'll implement error handling and logging to ensure robustness. Given these complexities, I believe a level 2 label would be more appropriate.
Thank you for your understanding!

Based on work done i will change the level.

Hi again @UTSAVS26 I am done with the work on this issue and pulled a request for the same. Please check it whenever you feel comfortable and let me know if you face any doubts regarding anything in the PR feel free to ask me.
Also can you please go through it well and based on my work, I would like to request you to please give me at least level 2 for the work.
Regards,
Sanchit Chauhan


Roadmap

[x] Add localstorage adapter
[x] Add code coverage
[ ] Create time travel mechanism

#4 added local storage

#5 adds coverage

#6


Fix integration test.py multitest case

Summary of the Pull Request
What is this about?
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #3595 (b4e2f6d) into main (8224382) will increase coverage by 0.00%.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3595   +/-   ##
=======================================
  Coverage   28.84%   28.85%
=======================================
  Files         136      136
  Lines       14758    14758
  Branches     1721     1721
=======================================
+ Hits         4257     4258    +1
  Misses      10181    10181
+ Partials      320      319    -1

see 1 file with indirect coverage changes

This turned out to be unnecessary, issue was in ADO not the integration-test.py script.


Missing "Hemogoblin" from Monster-A-Day Day 25

https://www.reddit.com/r/monsteraday/comments/62n770/day_25_hemogoblin/
I've tried resetting sources, adding and removing sources (including Monster-A-Day), changing up CR values to narrow down the search, removing all values except sources and typing "goblin" "hemo" and other variations.
I'm also not sure if you are able to keep all Monster-A-Day creatures on Kobold FC but if you do, this one is missing.

The Monster a Day Compendium (which is the source included in KFC) ist the collection of monsters done by /u/StoneStrix from that reddit. No other monster since then has been included.

That's just what the person who compiled the info provided. Assuming that subreddit is still active, if someone wanted to compile updates since then I'd be happy to add them.


Bug Fix

Bug Issue in webscraping it finds 110 matches on hltv.org/results for URL and ID but there should only be 100. When checking result-con only 100 matches are found so that doesn't seem to share the same bug. check web page for sidebar divs of featured matches

Tackling this now seems to be located on sidebar replay.

Bug appears to be fixed in HLTVMATCh branch. cleaning up and refactoring for readability before I push to main


Line Break

My code in HTML page
a href="abcd.html" class="link">My Link
$(document).ready(function () {
$(".link").on("click", function () {
$.cookie('myCookie', 'In this string I want to break the Line like \n second line starts', { expires: 2  , path: '/' });
});
});

Yes, you'll have to add a \n in order to produce a line break in that string.
>> "foo\nbar"
"foo
bar"

Closing, as it's not really a problem with the plugin.

Sorry, but \n is not breaking my line in the output.
I tried with both:
In this string I want to break the Line like \n second line starts
In this string I want to break the Line like\nsecond line starts.
I don't know why it is not working for me.

@mborah The Line Feed (LF) is a control character (CTL) and therefore it is NOT allowed in the cookie value, as per RFC 6265

Ah, thanks @FagnerMartinsBrack :+1:
So, a browser likely silently swallows that character.

I have no idea which browsers it breaks and how it breaks. When I was building the encoding tests, Safari and IE seemed to be the worst for invalid chars. Sometimes in Safari it ignored the value, and sometimes it ignored everything after the offending char or even prevented the whole cookie to be set.
Since the behavior is undefined, I like to assume that if you do something that goes against the RFC the browser will turn off your computer and it will never turn on again ;D

@FagnerMartinsBrack and @carhartl  ... Thanks for your reply..
Same here, even for me sometimes in Mozilla it ignored the value, and sometimes it ignored everything or sometime shows the whole character including "\n". God Knows uffff....
So, finally what shud I do? Should I set two different cookies for different lines? Any suggestion would be helpful.

You could use say "__" to denote a line break, then, when reading a cookie, replace that again with a real line break using a converter function:
$.cookie("foo", "first__second");
$.cookie("foo", function (s) {
    return s.replace("__", "\n");
});

Thanks I will try with that.

Or you can post this issue in the new JavaScript Cookie project. I just ignored the control characters encode handling because I never thought someone would create a cookie with that, supporting it costs unnecessary bytes to the codebase.


nuclei: 2.3.2 -> 2.3.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/projectdiscovery/nuclei/releases.
meta.description for nuclei is: "Tool for configurable targeted scanning"
meta.homepage for nuclei is: "https://github.com/projectdiscovery/nuclei"
meta.changelog for nuclei is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/d21ip2vpsm57w5rajii8v122gs0dcazs-nuclei-2.3.3/bin/nuclei passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 2.3.3 with grep in /nix/store/d21ip2vpsm57w5rajii8v122gs0dcazs-nuclei-2.3.3

found 2.3.3 in filename of file in /nix/store/d21ip2vpsm57w5rajii8v122gs0dcazs-nuclei-2.3.3

directory tree listing: https://gist.github.com/b6d3e79654c1bcf7a4ef434766f11fad

du listing: https://gist.github.com/39360c429a0cdc5acdebf6f11011bce1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
nuclei

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d21ip2vpsm57w5rajii8v122gs0dcazs-nuclei-2.3.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A nuclei https://github.com/r-ryantm/nixpkgs/archive/9c626bff8070deb7f5e463f84a88aefc0ce6b670.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d21ip2vpsm57w5rajii8v122gs0dcazs-nuclei-2.3.3
ls -la /nix/store/d21ip2vpsm57w5rajii8v122gs0dcazs-nuclei-2.3.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

Maintainer pings
cc @fabaff @kalbasit for testing.

Duplicate of #118209


fixedcodeblock

Fixed codeblock to remove white space before first curly bracket
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Grrr - I think this is an old branch. Sometimes, when I pull the latest I get an old branch from master for some reason.
I'm going to delete this and start over.


Forward working-directory to rb-sys-dock

The action was forcing the use of the passed in "working_directory" argument in the CI step.
Now, it is instead forwarded as the "--directory" argument if provided.
Also, if rb_sys has not been installed, it will change into the working directory before attempting to install, to ensure the version specified by the gemfile is used.

I dont know why github actions isnt running or letting me allow the check, but from a spotcheck it LGTM

cc: https://github.com/oxidize-rb/actions/actions/runs/8655950685/job/23735685073


[PR] The proj files have been updated to enable SourceLink

CSProj files have been updated to enable SourceLink in your nuget
[This pull request was created with an automated workflow]
I noticed that your repository and Nuget package are important for our .NET community, but you still haven't enabled SourceLink.
We have to take 2 steps:

Please approve this pull request and make .NET a better place for .NET developers and their debugging.
Then just upload the .snupkg file to https://www.nuget.org/ (now you can find the snupkg file along with the .nuget file)

You can find more information about SourceLine at the following links
https://github.com/dotnet/sourcelink
https://www.hanselman.com/blog/ExploringNETCoresSourceLinkSteppingIntoTheSourceCodeOfNuGetPackagesYouDontOwn.aspx
If you are interesting about this automated workflow and how it works
https://github.com/JTOne123/GitHubMassUpdater
If you notice any flaws, please comment and I will try to make fixes manually

thnks for the PR however we already distribute pdb together with symbols, indexed against the online repos and also symbols are reindexed each time there is a patch from VersionConverter. Sourcelink is just a build target we use the a variation of the https://github.com/eXpandFramework/XpandPwsh/wiki/Update-Symbols which gives more flexibility.
https://github.com/eXpandFramework/DevExpress.XAF/blob/04f45af808416a3cf8b733e0cb67fc9dc1ed9e7f/Build/BuildDevExpress.XAF.ps1#L24-L29
Unless I miss something I think this PR offers no additional value and does not support VersionConverter, so if no objections I will close without merging

closed


Feature request: add new device export API

From documentation the current device "download" API is deprecated in favor of the new "export" API.
It would be nice if this was integrated in the python client, since it has a significant changes because the download API directly respondes with the exported data, while the export API responds with the URL of the export job which should be polled to check completition and then it should be downloaded from an other URL.

Supported added with https://github.com/carbonblack/carbon-black-cloud-sdk-python/pull/479 and will be released in 1.5.1


Extend script configuration usage to non-sql file types.

Which version and edition of Flyway are you using?
Flyway Teams Edition 9.20.0
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using? (Type & version)
mssql/server:2017-cu13-ubuntu docker image
Which operating system are you using?
Windows 10
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
This is not a bug, rather a (hopefully small) feature enhancement. I wish to use a script configuration file to avail of the shouldExecute option for controlling the deployment of a powershell script. The documentation clearly states script configurations apply to sql files only so this is currently working as expected.
What did you expect to see?
What did you see instead?

Hi @vzdm , this is requirement is on our radar.
For now, could you try using if statement in your powershell script to work around this?

A Powershell script will, if executed as a callback or script, be able to read all the user placeholders as environment variables. In order to control whether a script executes, just set a value to a user placeholder and program the script to check the value to see what it should do.


Casmuser 2926

Summary and Scope
Apply fixes to address issues from COS/CSM/DVS found during loki testing:
Applied DVS-2377 fix
Applied SKERN-5608 fix
Update copyright headers
Update the repos for COS/DVS/Lustre after migration (SKERN-5680)
Issues and Related PRs

Resolves CASMUSER-2926
Required for https://github.com/Cray-HPE/uan-product-stream/pull/15

Tested on:

loki

Test description:
These fixes were manually put in place on loki to validate SS11, SHS 1.6, COS 2.2

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)? y
Were continuous integration tests run? If not, why? y
Was upgrade tested? N, there was no previous UAN installed and this is the only SS11 system
Was downgrade tested? If not, why? N
Were new tests (or test issues/Jiras) created for this change? N

Risks and Mitigations
This should not introduce new risk.
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

Reviewers, it would be best to look at each commit in this PR due to the large change required by the license check.


[RFC] General Attestation Service Design Proposal

Design
According to [RFC] Generic Key Broker Service (KBS) & Attestation Service high level architecture proposal, CC's general Attestation system relies on Attestation Service and KBS to verify the Attestation-Agent's running environment and distribute critical messages(such as KEK). The KBS is the role of RATS Relying Party, it's hardware agnostically and focuses on vendor-specific requirements. The Attestation Service is an implementation of the RATS Verifier role, it focuses on the verification of Evidence's identity and TCB status.
And the CC's Attestation Service is a general infrastructure service that mostly focuses on providing a Evidence verification service to KBS. So it needs to be compatible with all CC-supported HW-TEEs and should have excellent scalability to support potential new HW-TEE in the future. It also can be compatible with existing third-party attestation services with modularization.
To support the verification of TCB status, Attestation Service has the capability of parse the received Evidence to extract its corresponding TCB status. At the same time, it also includes the Policy Engine component which is an implementation of RATS Verifier Owner, It relies on the reference data from Reference Value Provider and the info extracted from Evidence to match the Attestation-Agent's running environment's TCB status dynamically. And generate the corresponding Attestation Results.
Attestation Service supports different deployment modes, as a service or as a library. One Attestation Service maybe needs to support several KBS services simultaneously when it is deployed as an infrastructure service. This will enhance the flexibility of the service's deployment.
Goals

Define the format of Evidence and Attestation Results messages for SGX and TDX.
Distribute the Attestation Service as a library or single service.
It's a general infrastructure service that:

It should compatible with various HW-TEEs and have good scalability.
It should compatible with different third-party attestation Services.

Support management API to set reference data by Reference Value Provider and set other configurations.

Non-Goals

Define the format of Evidence and Attestation Results messages for SEV(-ES) and SEV-SNP.
Proxy sub-modules that support existing third-party attestation services.

Architecture
The following diagram demonstrates the overall architecture and internal modules:

Service: Provides interface that can be used to communicate with KBS. It receives Evidence from KBS and returns the Attestation Results.
Attestation: The core module that implements Evidence's attestation.

Verification Drivers: Includes HW-TEE sepcific sub-modules and policy module to verify Evidence identity and TCB status.

TDX/SGX/SEV-SNP/SEV(-ES): Pluggable and HW-TEE specific sub-modules which invoke Endorser to verify Evidence's identity.
Policy Engine: Act as RATS Verifier Owner to verify TCB status.

Proxy: Includes pluggable proxy sub-modules that can invoke third-party attestation services to attest the Evidence.

Management API: It provides APIs that are used by Reference Value Provider to set Verifier Owner reference data and execute some other configurations.

Service Module
This module is used to communicate with external modules such as KBS, its mainly features are:

Support the following two different running modes:

As a Library: It can be integrated and invoked by KBS directly.
As a Service: Running as a separate service.

Receive the Evidence sent by KBS and return the corresponding Attestation Results.

Evidence
Different types of HW-TEE Evidences are various, as example:

TDX Evidence:

{
    "tee" : "tdx",
    "quote": <Base64 encoded quote>,
    // The ehd's hash will be embeded in Quote->report_data.
    "ehd":
    {
        "nonce" : "cdfunsas23445xd",
        "public-key" : "xxxxxxxx"
    },
    "aad":
    {
        "tdelInfo" : <Base64 encoded eventlog's information>,
        "tdelData" : <Base64 encoded eventlog's data>
    }
}

SGX Evidence:

{
    "tee" : "sgx",
    "quote": <Base64 encoded quote>,
    //The ehd's hash will be embeded in Quote->report_data.
    "ehd":
    {
        "nonce" : "cdfunsas23445xd",
        "public-key" : "xxxxxxxx"
    },
    "aad":{}
}

SEV-SNP Evidence: TBD

Attestation Results
The Entity Attestation Token (EAT) format compliant Attestation Results of the Evidence. Its format should be:
{
    "alg": "RS256",
    "jku": "https://xxxxx.xxx/certs",
    "kid": <self signed certificate reference to perform signature verification of attestation token,
    "typ": "JWT"
}.{
    "exp":<PHONE_NUMBER>,
    "iat":<PHONE_NUMBER>,
    "iss": "https://xxxxxx",
    "attestation_results":{}
}.[Signature]

attestation_results: The result of the Evidence's attestation.
Signature (Optional): The value will be empty in the following scenario:

Attestation Service is called as a Crate.
The connection between Attestation Service and KBS is security and trusted.

The attestation_results of different types of HW-TEE are various, as examples:

TDX Evidence attestation results:

"attestation_results":
{
    "tee": "TDX",
    "attestation-type": "TDX",
    "policy":
    {
        "allow": "true", //true/false: the verification state
        "name": <>, //The name of the used evaluation policy file
        "hash": <>, //The hash of the used evaluation policy file
        "diagnose":"" //Diagnose message from Policy Engine
    }
    "aad":
    {
        "collateral":
        {
            "qeidcertshash": <SHA256 value of QE Identity issuing certs>,
            "qeidcrlhash": <SHA256 value of QE Identity issuing certs CRL list>,
            "qeidhash": <SHA256 value of the QE Identity collateral>,
            "quotehash": <SHA256 value of the evaluated quote>,
            "tcbinfocertshash": <SHA256 value of the TCB Info issuing certs>,
            "tcbinfocrlhash": <SHA256 value of the TCB Info issuing certs CRL list>,
            "tcbinfohash": <SHA256 value of the TCB Info collateral>
         },
        "ehd": <>,
        "is-debuggable": true,
        "mrseam": "xxxxxx",
        "mrseamsigner": "xxxxxx",
        "mrtd": "xxxxxx",
        "rtmr0": "xxxxxx",
        "rtmr1": "xxxxxx",
        "rtmr2": "xxxxxx",
        "rtmr3": "xxxxxx",
        "cpusvn": 1,
        "svn": 1
    }
}

SGX Evidence attestation results:

"attestation_results":
{
    "tee": "SGX",
    "attestation-type": "SGX",   //String value representing attestation type
    "policy":
    {
        "allow": "true", //true/false: the verification state
        "name": <>, //The name of the used evaluation policy file
        "hash": <>, //The hash of the used evaluation policy file
        "diagnose":"" //Diagnose message from Policy Engine
    }
    "aad":
    {
        "collateral":
         {
            "qeidcertshash": <SHA256 value of QE Identity issuing certs>,
            "qeidcrlhash": <SHA256 value of QE Identity issuing certs CRL list>,
            "qeidhash": <SHA256 value of the QE Identity collateral>,
            "quotehash": <SHA256 value of the evaluated quote>,
            "tcbinfocertshash": <SHA256 value of the TCB Info issuing certs>,
            "tcbinfocrlhash": <SHA256 value of the TCB Info issuing certs CRL list>,
            "tcbinfohash": <SHA256 value of the TCB Info collateral>
        },
        "ehd": <>,
        "is-debuggable": true,
        "mrenclave": <SGX enclave mrenclave value>,
        "mrsigner": <SGX enclave msrigner value>,
        "product-id": 1,
        "svn": 1
    }
}

SEV-SNP Evidence attestation results:
TODO

As a Library
The Attestation Service will provide the following interface:
pub fn attestation(evidence: String) -> Result<String, String> {}

attestation()：

Role: Verify the evidence and return the corresponding Attestation Results.
Evidence(Input): Attestation-Agent generated Evidence. It's a JSON string that includes the target HW-TEE identity and TCB status information that needs to be verified.
Attestation Results(Output): The Entity Attestation Token (EAT) format compliant Attestation Results of the Evidence.

As a Service
The Attestation Service can be extended to add a separate service application which also relies on the upper library. Its Cargo.toml file example:
[[bin]]
name = "attestation_service"
path = "app/attestation_service/src/main.rs"

Note: The service can be connected with localhost:port only in POC stage.
The POC will select the gRPC, so its proto file should be:
syntax = "proto3";

package attestation;

message AttestationRequest {
    bytes evidence = 1;
}
message AttestationResponse {
    bytes results = 1;
}

service AttestationService {
    rpc Attestation(AttestationRequest) returns (AttestationResponse) {};
}

Attestation Module
Its responsibility is to verify these various received Evidence. It includes the following two internal modules:

Verification Drivers: It includes different HW-TEE specific modules and some common modules. The former verifies the Evidence's identity, the common modules verify the TCB status.
Proxy: It includes proxy sub-modules that are compatible with third-party Attestation Service in order to use these services to attest Evidence directly.

It also defines a trait that needs to be implemented by its internal modules.
trait Attestation{
    fn attestation(&self, evidence : String) ->Result<String, String>;
}

Verification Drivers
It includes different HW-TEE specific pluggable verification modules and some common modules to verify the Evidence's identity and TCB status:

TDX/SGX/SEV(-ES)/SEV-SNP (pluggable): HW-TEE specific modules.
Eventlog-rs (common): Parse the TCG protocol compliant eventlog inside Evidence.

TDX/SGX/SEV(-ES)/SEV-SNP
Its features:

Each module corresponds to a specific HW-TEE type.
Each module can be enabled/disabled by feature, such as #[cfg(feature = "tdx")].
It can verify the received Evidence's identity.
It can extract the TCB information inside the received Evidence.

Eventlog-rs
To verify all running programs' measurements inside TEE-based VM, the TCG protocol compliant eventlog will be included inside Evidence. So the eventlog-rs is used to parse that eventlog and extract the following components' measurements which will be sent to Policy Engine for final verification (as an example):

Bootloader
Kernel Parameters
Kernel
...

Policy Engine
It uses Open Policy Engine to reach Develop Policy as Code. And OPA relies on the following files to execute verification:

OPA Input (JSON): These data need to be verified such as TCB status and running programs' measurement.
OPA Data (JSON): The reference data that is provided by Reference Value Provider.
OPA Policy (.rego): The judgment policy.rego file.

Policy.rego
The different HW-TEE TCB status's verification policy is various, as examples:

Policy.rego used to check Bootloader, Kernel Parameters, and Kernel measurements extracted from eventlog:

package policy

import future.keywords.in
default allow = false
allow {
    bootloader_is_granted
    kernel_is_granted
	kernelparameters_is_granted
}

bootloader_is_granted {
    count(data.bootloader.hashes) == 0
}
bootloader_is_granted {
    input.bootloader == data.bootloader.hashes[_]
}
kernel_is_granted {
    count(data.kernel.hashes) == 0
}
kernel_is_granted {
    input.kernel == data.kernel.hashes[_]
}
kernelparameters_is_granted {
    count(data.parameters.hashes) == 0
}
kernelparameters_is_granted {
    input.parameters == data.parameters.hashes[_]
}

Policy.rego used to check SGX Evidence's TCB information:

package policy

# By default, deny requests.
default allow = false

allow {
    mrEnclave_is_grant
    mrSigner_is_grant
    input.productId >= data.productId
    input.svn >= data.svn
}

mrEnclave_is_grant {
    count(data.mrEnclave) == 0
}
mrEnclave_is_grant {
    count(data.mrEnclave) > 0
    input.mrEnclave == data.mrEnclave[_]
}

mrSigner_is_grant {
    count(data.mrSigner) == 0
}
mrSigner_is_grant {
    count(data.mrSigner) > 0
    input.mrSigner == data.mrSigner[_]
}

Proxy
It includes pluggable proxy sub-modules that are used to support third-party Attestation Services, such as:

Microsoft Azure Attestation Service
ISecL Attestation Service

Management API Module
Attestation Service also enables a management API to provide the following functionalities:

Set Policy Engine's reference data by Reference Value Provider.
Set proxy sub-modules configurations.

So this module provides the following interfaces:
fn set_policy(request: &SetPolicyEnginePolicyRequest) -> Result<(), String> {};
fn export_policy(request: &ExportPolicyEnginePolicyRequest) -> Result<PolicyEnginePolicy, String> {};
fn set_reference(request: &SetPolicyEngineReferenceRequest) -> Result<(), String> {};
fn export_reference(request: &ExportPolicyEngineReferenceRequest) -> Result<PolicyEngineReference, String> {};
fn test(requets: &TestPolicyEngineRequest) -> Result<TestPolicyEngineResponse, String> {};

As a Service
If the Attestation Service is built as a service, it will provide these functions as GRPC services. So its proto file should be:
syntax = "proto3";

package managementapi;

message SetPolicyEnginePolicyRequest {
    bytes name = 1;
    bytes content = 2;
}
message SetPolicyEnginePolicyResponse {
    bytes status = 1;
}

message SetPolicyEngineReferenceRequest {
    bytes name = 1;
    bytes content = 2;
}
message SetPolicyEngineReferenceResponse {
    bytes status = 1;
}

message ExportPolicyEnginePolicyRequest {
    bytes name = 1;
}
message ExportPolicyEnginePolicyResponse {
    bytes status = 1;
    bytes content = 2;
}

message ExportPolicyEngineReferenceRequest {
    bytes name = 1;
}
message ExportPolicyEngineReferenceResponse {
    bytes status = 1;
    bytes content = 2;
}

message TestPolicyEngineRequest {
    bytes policyname = 1;
    bytes policycontent = 2;
    bool policylocal = 3;
    bytes referencename = 4;
    bytes referencecontent = 5;
    bool referencelocal = 6;
    bytes input = 7;
}
message TestPolicyEngineResponse {
    bytes status = 1;
}

service PolicyEngineService {
    rpc SetPolicy(SetPolicyEnginePolicyRequest) returns (SetPolicyEnginePolicyResponse) {};
    rpc exportPolicy(ExportPolicyEnginePolicyRequest) returns (ExportPolicyEnginePolicyResponse) {};
    rpc setReference(SetPolicyEngineReferenceRequest) returns (SetPolicyEngineReferenceResponse) {};
    rpc exportReference(ExportPolicyEngineReferenceRequest) returns (ExportPolicyEngineReferenceResponse) {};
    rpc Test(TestPolicyEngineRequest) returns (TestPolicyEngineResponse) {};
}

Opens

Currently the Attestation Service only supports the runtime attestation (TDX/SEV-SNP/SGX), the pre-attestation (SEV(-ES)) is supported by simple-kbs.

Reference

[1] https://www.ietf.org/archive/id/draft-ietf-rats-architecture-15.txt

Looks good. A few notes, mainly for future reference.
First, eventlog-rs won't be used by the SNP module because the SNP evidence doesn't include any kind of event log (although at some point we might be using vTPMs with SNP, which could provide something like that). Instead the evidence will include some other reference to the firmware, kernel, etc. that the VM booted with. It's not yet clear exactly what this will look like.
I don't think we want to have a boolean verification state. Will rego allow us to return a verification result that can be set to more than just two values? Similarly can the allow field in the verification result be changed to something like verification_result which could be set to more than just two different values. This would allow us to create more expressive key policies. For example, we could make a policy that only releases keys when a new version of firmware is  used in the guest. It would also help reconcile different architectures where approved evidence might come with different security properties.
Finally, maybe we should think about having a Keylime attestation proxy?

@fitzthum Thank you for your comments, the following are my answers.

First, eventlog-rs won't be used by the SNP module because the SNP evidence doesn't include any kind of event log (although at some point we might be using vTPMs with SNP, which could provide something like that). Instead the evidence will include some other reference to the firmware, kernel, etc. that the VM booted with. It's not yet clear exactly what this will look like.

I think it's not a problem here. And maybe a new general separate libray which is compatible with both TDX eventlog and SEV-SNP should be added in future. But I am not sure about this currently.

I don't think we want to have a boolean verification state. Will rego allow us to return a verification result that can be set to more than just two values?

Yes, the OPA can return multiple evaluation values simultaneously. It's all depends on the policy.rego file. You can play this OPA example to have a try, it will output the following:
{
    "allow": true,
    "user_is_admin": true,
    "user_is_granted": []
}

Finally, maybe we should think about having a Keylime attestation proxy?

Yes, the design is modularized, so it's easy to extend to add some other proxy sub-modules. I think in the POC stage, maybe none proxy sub-module will be supported.

wouldn't the message format for SEV(-ES) and SEV-SNP need to considered in the goals now, for it to be accommodated later?

I think the assumption is basically that SEV-SNP is going to be similar enough to TDX (with some of the differences I mentioned above) that it should work with this proposal. On the other hand SEV-ES is different enough that it is never going to be a great fit so we will either just try to shoe-horn it in later or leave it to simple-kbs to support pre-attestation.
I know there was some interest in discussing SNP support more generally. We might want a separate issue for that.
One thing that I alluded to above is that SNP does not have the same kind of event log that TDX does. I am assuming that for SNP we are going to continue to use the measured-direct-boot approach that we are currently using for SEV(-ES). To simplify validation of the measurement we're going to need to provide some hints to the KBS/AS as part of the evidence. For example, we will probably want to send the hash of the kernel and initrd as part of the evidence. We will also probably need to include the CPU count of the guest so that the AS can construct an appropriate VMSA. These values can be evaluated using a rego policy. If the policy is valid we will construct an expected measurement from that and compare it to the measurement in the attestation report.
One interesting thing is that the AS will likely need access to the full firmware binary so that it can calculate the launch measurement (unless we try to pre-compute launch measurements offline). This is a bit annoying. The proposal above has some tooling to provide reference data to the AS. It looks like this is more aimed at providing hash, but we would probably use it to provide the full firmware binary as well.
So like I said, I believe that this proposal will work with SNP, but if someone wants to try filling in more details that would definitely be welcome.

Hi @vbatts Thank you your comments.

wouldn't the message format for SEV(-ES) and SEV-SNP need to considered in the goals now, for it to be accommodated later?

I think the SEV-SNP should be considered now, we should support these runtime attestation simultanesously. And for SEV(-ES), as I mentioned in the OPEN section, maybe we can consider it later, because it has been supported by simple-kbs.

Hi @fitzthum ,

One thing that I alluded to above is that SNP does not have the same kind of event log that TDX does. I am assuming that for SNP we are going to continue to use the measured-direct-boot approach that we are currently using for SEV(-ES)

If the SNP evidence includes these hashs (kernel ...) directly, I think it will be better. It simplified the attestation procedures. At least it needn't to use such as eventlog tool to parse the evidence to get them.
And according to the design, each type of HW-TEE has its own corresponding module, so it can implement it's special and separate .rego file (such as policy-snp.rego) and the verification logic. I think it's not a problem here.

One interesting thing is that the AS will likely need access to the full firmware binary so that it can calculate the launch measurement (unless we try to pre-compute launch measurements offline). This is a bit annoying.

Inside TDX evidence, it includes a special register named MRTD which is used to store the launch firmware's hash exclusively. With this register AS can compare the TEE running firmware hash to the reference value directly. I don't sure whether SNP's evidence has such a register also. But I will also help to check that.

Do you know how to calculate the SNP launch measurement?

Calculating the launch measurement for SNP is actually a bit more complicated than calculating the launch measurement for SEV-SNP. There is a reference implementation here and @dubek can probably answer any specific questions.
The basics are that instead of just hashing flash0 + VMSA, we actually hash every memory page individually, with each page extending the hash of the previous page. There are also some new mechanisms with different types of pages. The underlying memory that we load into flash0 and the VMSA are roughly the same as with SEV(-ES) though. So just like for SEV(-ES) we will need to know the hash of the initrd, kernel, and cmdline so that we can inject them into the firmware (this is how measured-direct-boot works). We will also need to generate the VMSAs (initial register state of guest) and we'll need to know a few things to do this like the number of CPUs the guest is running.

Calculating the launch measurement for SNP is actually a bit more complicated than calculating the launch measurement for SEV-SNP. There is a reference implementation here and @dubek can probably answer any specific questions.

@fitzthum Thank you for this information. And I also updated the proposal to mention that only TDX supports the eventlog mechansim currently.

@liangzhou121 thank you for the proposal, it looks great. I have a question regarding the Attestation Results as proposed we are going with Entity Attestation Token(EAT) format. Is there any particular reason for using JWT as typ rather than CBOR Web Token (CWT). JWT is not inherently secure. It doesn't concern it with encryption, it only care about validation.

@knrt10 Thank you for your comments.

Is there any particular reason for using JWT as typ rather than CBOR Web Token (CWT). JWT is not inherently secure. It doesn't concern it with encryption, it only care about validation.

Actually both the JWT and CWT are recommended by RATS that can be used to transfer the Attestation Results. And the Attetsation Results only needs the integrity protection, so we think the JWT should be enough.
By the way, none of the JWT/CWT will be used during the POC stage. Because the attestation service will be used as a local service or a Crate which is intergrated by KBS directly in this stage.

@liangzhou121 - can I confirm that "MAA" refers to "Microsoft Azure Attestation" in the diagram?


invalid_request_error when using any of the tools

I cloned the project, installed dependencies, filled out the env vars, started the relay server and the React frontend.
Everything seems to work fine until it tries to access one of the tools. If I say "What is the weather in Chicago?" (or any location) it will output the following in the logs:
{
  "type": "error",
  "event_id": "event_AQJyeAN9SM0lxdiYtgtXf",
  "error": {
    "type": "invalid_request_error",
    "code": null,
    "message": "Conversation already has an active response",
    "param": null,
    "event_id": null
  }
}

And say something to the effect "I am having trouble accessing the weather information right now".
The strange thing is the conversation output window on the bottom actually displays a successful result from the weather API call as "function call output". Here is an example:
t
{"latitude":40.710335,"longitude":-73.99309,"generationtime_ms":0.02205371856689453,"utc_offset_seconds":0,"timezone":"GMT","timezone_abbreviation":"GMT","elevation":32,"current_units":{"time":"iso8601","interval":"seconds","temperature_2m":"°C","wind_speed_10m":"km/h"},"current":{"time":"2024-11-05T19:45","interval":900,"temperature_2m":19.9,"wind_speed_10m":19.9}}

So it's calling the function, getting the weather from the API, returning it, but somehow the voice agent does not recognize this.
Anyway this is running locally on Chrome (latest version) on a Windows 11 machine, but I think it's a problem with the code and not on my end.
If anyone else has encountered this or has a solution let me know please.

Possibly related to #474


Avoiding specific Node-to-Node routes for CNI traffic

We have a setup where Nodes are connected by a number of disjoint networks, some of which are intended for bulk-transfers and can often become congested, leading to dropped traffic or otherwise undesirable conditions. We use BGP between Nodes, which can lead to these sub-optimal paths being used and timeouts occurring.
Expected Behavior
Want to be able to tell the BGP daemon to prefer routes between Nodes, or to blacklist certain routes.
Current Behavior
All routes are used and we observe timeouts or inconsistencies in CNI traffic.
Possible Solution
Allow configuration of the BGP daemon to prevent traffic to certain routes.
Your Environment

Calico version - 3.20
Orchestrator version - Kubernetes 1.21
Operating System and version: SLES 15 SP3

https://github.com/projectcalico/calico/blob/89f90a81558ff2c4fa71e7e052af458750e3a85d/confd/etc/calico/confd/templates/bird.cfg.template#L212-L214
^ Calico sets the source address parameter for BGP sessions based on the auto detected node IP.
There are a few ways to configure this: https://projectcalico.docs.tigera.io/networking/ip-autodetection
I suspect you just need to configure auto detection such that BGP binds to the correct source address on the network that you want pod traffic to be routed over.
Note that if you're using BGPPeer objects, you will need to set UseNodeIP to force this binding (as described here: https://projectcalico.docs.tigera.io/reference/resources/bgppeer). This field was introduced in Calico v3.22.0.
For full mesh, looks like we always set the source address option so that isn't needed.

https://github.com/projectcalico/calico/blob/89f90a81558ff2c4fa71e7e052af458750e3a85d/confd/etc/calico/confd/templates/bird.cfg.template#L212-L214
^ Calico sets the source address parameter for BGP sessions based on the auto detected node IP.
There are a few ways to configure this: https://projectcalico.docs.tigera.io/networking/using
I suspect you just need to configure auto detection such that BGP binds to the correct source address on the network that you want pod traffic to be routed over.
Note that if you're using BGPPeer objects, you will need to set UseNodeIP to force this binding (as described here: https://projectcalico.docs.tigera.io/reference/resources/bgppeer). This field was introduced in Calico v3.22.0.
For full mesh, looks like we always set the source address option so that isn't needed.

We are using nodeAddressAutodetectionV4:  interface: but this appears to result in issues we describe where the nodes have multiple addresses. From reading the docs it appears that this address is used to establish the BGP mesh, but once the mesh is established Nodes on the same subnet can form paths over alternative interfaces. Can you confirm that this address is the only one which will be used for CNI traffic with a BGP mesh configuration and not just the address used to identify the Node?

If you're using BGP mesh, then yes you should see source address <node IP> set in your BIRD configuration on each node. My understanding is that will tell BIRD to use that IP as the next hop address advertised to remote BGP peers.
What those remote BGP instances do with that next hop information, however, is dependent on how routing is configured on that node. For example, if for some reason the remote BIRD believes that the received next hop is only reachable via a different interface, it will try to route traffic via that interface instead.
It might help if you share some more details of a couple of the nodes in your cluster, in case I'm misunderstanding something. e.g.,
ip addr show

ip route show

It looks like there hasn't been that much recent activity on this issue so I'm going to close it. I'll reopen the issue if there's more activity.


Does the pheno file accepts missing values for a variable/covariable?

Hi,
I am wondering if the pheno file accepts missing values when running the GWAS locally...
Thanks

Yes, the program should be able to handle missing phenotypes (the sample with missing values will be automatically dropped).


Add TMP102

Add library for the TMP102 Library

library
examples
test
doc

Hi Jan, it seems that you forget to add target TMP102 in Package.swift of MadDrivers, so Github CI fails to build the example.
Besides, I notice a typo in Package.swift of the example MonitorTemp, the branch of MadDrivers should be main instead of mein.

I have revised the errors and typo.


Actual releases?

Feature Request
Is your feature request related to a problem? Please describe:
Running 'latest' images makes rollbacks very hard.
Describe the feature you'd like:
It would be nice if you could tag a monotonic series of images - even if every build is properly gated, unintended consequences can still cause rollbacks to be desirable and the lack of discrete tags makes that impossible today.
Describe alternatives you've considered:
None
Teachability, Documentation, Adoption, Migration Strategy:

@rbtcollins Thanks for your suggestions, we will release version 1.0 this quarter and will continue to maintain a certain release frequency.

@rbtcollins We have release a v0.8.0 version and will continue to maintain a certain release frequency.


[bug] Command::output() never executes/completes in async commands

Describe the bug
If you try to execute a sidecar or Commands in general in an async command it never drives to completion (or probably doesn't even start in the first place).
I tested this only on windows, but according to discord it's a problem on linux or macOS too (can't remember which one they had)
Reproduction
Create a simple async command (I'm using windows for this example):
#[tauri::command]
async fn list_dir() {
    let c = Command::new("powershell.exe").args(["ls"]);
    dbg!(c.output().unwrap());
}

It works if you remove the async keyword. Same if you use (the underlying) std::process::Command::output().
Command::spawn() works fine fwiw.
Expected behavior
No response
Platform and versions
Operating System - Windows, version 10.0.19044 X64
Webview2 - 98.0.1108.55
Visual Studio Build Tools:
   - Visual Studio Build Tools 2022

Node.js environment
  Node.js - 16.14.0
  @tauri-apps/cli - 1.0.0-rc.5
  @tauri-apps/api - 1.0.0-rc.1

Global packages
  npm - 8.3.1
  pnpm - 6.31.0
  yarn - Not installed

Rust environment
  rustup - 1.24.3
  rustc - 1.58.1
  cargo - 1.58.0
  toolchain - stable-x86_64-pc-windows-msvc

App directory structure
/dist
/node_modules
/src
/src-tauri

App
  tauri - 1.0.0-rc.3 (no lockfile)
  tauri-build - no manifest (no lockfile)
  tao - no manifest (no lockfile)
  wry - no manifest (no lockfile)
  build-type - bundle
  CSP - default-src 'self'
  distDir - ../dist
  devPath - http://localhost:3000/
  framework - React

Stack trace
No response
Additional context
No response

For context the discord thread: https://discord.com/channels/616186924390023171/731495047962558564/944170846707122216
Do we have any ideas why this may be happening? Command::spawn works like a charm so it's the output method that is the problem?

I think we can refactor the Command APIs a little bit and make them async instead, and offer blocking variants similar to what we did for the dialog APIs.


Remove CoreConfig.mod and enable CoreNEURON execution via NEURON Python API

Context
Instead of using a mod file (CoreConfig.mod) to launch the CoreNEURON simulation using NEURON's C++ API we replace the file with NEURON's Python API to launch CoreNEURON in file mode.
Scope
The changes in Neurodamus include:

A new mechanism (mod file CoreNEURONArtificialCell.mod) to be instantiated in the processes that don't have any cells (i.e. simulation with 3 cells but 4 MPI ranks)
New CoreConfig Singleton object that holds all the needed information for CoreNEURON and the related functions to write the simulation and report configurations read by CoreNEURON
New tests
Enabling again failing tests from https://github.com/BlueBrain/neurodamus/pull/38
Disable test_hoc_target_generate_subtargets which fails in python3-base CI without any reason

Apart from the changes in Neurodamus there are also changes needed in NEURON which are done in https://github.com/neuronsimulator/nrn/tree/jblanco/coreneuron_from_neurodamus
Testing
Unit tests for the new way to print the CoreNEURON configutarions were added.
All the other tests should pass without an issue apart from py38-full-spack which fails due to the dependence in the deployed module in BB5 and its mechanisms
Review

[x] PR description is complete
[x] Coding style (imports, function length, New functions, classes or files) are good
[x] Unit/Scientific test added
[x] Updated Readme, in-code, developer documentation

Note that because of the changes in the mod files in this branch and the fact that py38-full-spack depends on the deployed modules, this test will always fail

With the latest changes and https://github.com/BlueBrain/spack/commit/f5e66bd6bd4ae54ce902d2268d1fd61bc223c991 this is now ready to merge.
I've run locally the tests from py38-full-spack and they now pass with the changes mentioned above


Update information on how tree-shaking may be ineffective

https://github.com/webpack/webpack/issues/4784 and https://github.com/webpack/webpack/issues/2867 are serious issues that show that tree-shaking in Webpack is completely broken in certain (common!) situations.
This change adds a small section to the introduction of tree-shaking explaining what happens and how tree-shaking actually works in Webpack.

Ah, a "Drawbacks" section would be useful! I'll try to the PR tomorrow (as in when it's Sunday in Europe :) )

As always, "tomorrow" turned into "within a week maybe". Sorry :). Added a "Caveats" section


Add volume/stats API, polish streaming results, and upgrade to Python 3.6

I have added support for volumes API and polished streaming results for graceful shutdown, based on zbyte64's fork. I also have wrapped exceptions in "DockerError". Most string interpolation code are rewritten using Python 3.6's f-string literals and the streaming result is now handled via asynchronous generators (yield in async def functions).
Though I still need to add test cases, I'd like you to review the changes and discuss if my approach aligns with your direction (and if this could be merged eventually of course). Please feel free to add your opinions about improvements you want for this PR.
There seems to be different forks that adds different functionalities (e.g., detailed filtering condition support in logs API in findmine/aiodocker's expansion branch). Before multiple forks diverge out too much, I think we need to discuss on what the maintainer thinks for next steps.

@achimnol would you like to be added as a collaborator? Thank you so much!

@paultag Thanks a lot! 👍


Friendly error messages

The error handling needs to be changed so this doesn't output a Ruby backtrace to the user.
$ slather coverage -s CGFloatTypeTests/CGFloatType.xcodeproj
/Users/kylef/gems/gems/slather-1.0.1/lib/slather/project.rb:34:in `coverage_files': No coverage files found. Are you sure your project is setup for generating coverage files? Try `slather setup your/project.pbxproj` (StandardError)
	from /Users/kylef/gems/gems/slather-1.0.1/lib/slather/coverage_service/simple_output.rb:13:in `post'
	from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:50:in `post'
	from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:30:in `execute'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'
	from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:6:in `<top (required)>'
	from /Users/kylef/gems/bin/slather:23:in `load'
	from /Users/kylef/gems/bin/slather:23:in `<main>'

$ slather
Slathering...
/Users/kylef/gems/gems/slather-1.0.1/lib/slather/coverage_service/coveralls.rb:24:in `coveralls_coverage_data': Environment variable `TRAVIS_JOB_ID` not set. Is this running on a travis build? (StandardError)
	from /Users/kylef/gems/gems/slather-1.0.1/lib/slather/coverage_service/coveralls.rb:35:in `post'
	from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:50:in `post'
	from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:30:in `execute'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'
	from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'
	from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:6:in `<top (required)>'
	from /Users/kylef/gems/bin/slather:23:in `load'
	from /Users/kylef/gems/bin/slather:23:in `<main>'

the same error


Test RoBERTa Psych

Try fine-tuning RoBERTa-psych: https://huggingface.co/mlaricheva/roberta-psych

A quick test shows no difference from roberta base. Might be worth discussing in a paper.


Usage of package server to download registry for Julia 1.4 and newer.

Fixes #209 #244
It's a bit mess but I couldn't figure out better way and it's working.
I'm able to run CompatHelper behind corporate firewall with my own registry on GitHub Enterprise with this change.

@DilumAluthge is it ok like this or should it be split into multiple smaller PRs? (technically this is fixing 2 different issues)

Yeah can you split it up into two different PRs, one for each issue that you are fixing?


Implement request #316, and minor ui fixes.

Implement request #316: viewer menu now opens/closes on handle click instead of hover, just like editor.
Menu handle icon now changes on open/close as appropriate.  Added necessary image files.
Default is still open, auto-closing after 3 seconds.
Explicit open or close cancels the initial auto-close timeout.
Since Examples doesn't close on hover-out any more, there needs to be a way to close it, so made clicking on Examples toggle it instead of just opening it.
Fix: Clicking on Examples now cancels the initial auto-close timeout.
Fix: The initial auto-close now closes Examples too, if open.
Fix: Editor handle icon now changes on open/close as intended (the icon was getting set on the wrong element before)

@donhatch Wow! Thanks for,the nice changes.
Just for reference, which browsers are you testing with?

Very nice work @donhatch  , much appreciated !
I'll do a full review/ local test tonight.

Hi @z3dev,
I tested this using chrome 61.0.3163.100 and safari 10.0,
both on a macbook pro running macos 10.12 (sierra).

@donhatch I tried your PR locally, and I like it a lot !
But one thing is still weird : unless you explicitly click on the handle it still opens 'on hover'
I think it would feel more natural if after the initial closing after the timeout, it would only open/close with explicit clicks.

Hi @kaosat-dev, I agree it shouldn't open on hover any more; I'm surprised if it's still doing that for you.
I don't think it's doing that for me, on the browsers I mentioned above.
And I thought I removed the lines that implement open-on-hover, in style.css, didn't I?
So it's very strange if it's still doing it for you; are you sure?

Hi @donhatch double checked after your message & turns out it is the Chrome's caching that was messing things up!
Testing in Chrome, Safari and Firefox on MacOs.
Will merge asap

@kaosat-dev , I fixed the semicolons.
I guess my two commits should be squashed into one-- I'm not sure whether that's something that I should do somehow, or whether you will do it during the pull?

@donhatch thanks ! It is fine , we always use 'squash and merge' strategy, so we can ensure a single commit per PR and standardised final commit names (that get used by tooling down the line for things such as changelog generation, etc)


Add a tag to latest images to trigger Flux deployments

This PR is related to the implementation of flux and allows it to trigger a deployment in the aat AKS cluster when any new master image is pushed in the hmcts registry.
The known drawback is that it'll create loads of tags but I assume we'll create or re-use the existing images cleanup scripts.
Typically this modification means that any image built with the following name:
<image-name>:latest

will also be tagged as
<image-name>:latest-dfb02 # corresponding to the {{.Run.ID}} of the acr build task

There is no other functional change, and should not have any impact on the existing pipelines. It just generates an additional tag triggering a deployment in the aat aks cluster if Flux is in use and expecting this pattern.

What does it get tagged with?
i.e. can you add an example, not sure what shortName returns
Also I don't think the jenkins-library is currently running the tests for docker because of the issue with plum not being able to pull from the hmcts registry, so this should be tested on a separate PR or the docker issue fixed so it can be re-enabled in the pipeline

@timja I've updated the PR description. an example is also in the code comments.

have you got a link to somewhere you've tested it?

Here is a failed build (because of invalid character use '~')
And the fixed one obviously.
So I assume that the acr build is being tested in this PR's checks.

Ah its being tests on backend but not frontend 👍
thanks


Revert "Move config consts out of src files and into a conf.yaml "

Reverts carrot-ar/carrot#37

Codecov Report

Merging #38 into master will increase coverage by 2.99%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
+ Coverage   48.77%   51.77%   +2.99%
==========================================
  Files          15       14       -1
  Lines         490      479      -11
==========================================
+ Hits          239      248       +9
+ Misses        237      216      -21
- Partials       14       15       +1

Impacted Files
Coverage Δ

router.go
70.27% <ø> (ø)
:arrow_up:

dispatcher.go
66.66% <ø> (+8.33%)
:arrow_up:

session.go
86.36% <ø> (+1.13%)
:arrow_up:

middleware.go
36.66% <ø> (ø)
:arrow_up:

client.go
3.84% <ø> (ø)
:arrow_up:

server.go
0% <ø> (ø)
:arrow_up:

app.go
0% <ø> (ø)
:arrow_up:

broadcaster.go
68.57% <0%> (-5.72%)
:arrow_down:

... and 1 more

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 6fb4f00...de89548. Read the comment docs.


Implement chunking

It is currently very ugly but I don't know how to avoid MaybeUninit. I'm 100% sure theres a way and will figure it out soon. also inlined difference in get_best_char because it was wayy to slow (This is the highest quality github pull request with 50 minutes spent on just the git process alone)

meh PR.
I'll still add it because there's so much to fix I need to do it in my IDE I don't wanna use this github editor anymore


Error - Access denied for user 'root'@'localhost' (using password: NO)

Hi,
When trying to execute this -
Connection connection = DriverManager.getConnection("jdbc:mysql://localhost/myDb", "root", "");
I'm getting error -

Access denied for user 'root'@'localhost' (using password: NO)

Here is my full code
static class MySqlRule extends ExternalResource {
        DB db = null;

        MySqlRule() {
            DBConfigurationBuilder configBuilder = DBConfigurationBuilder.newBuilder();
            configBuilder.setPort(3306); // OR, default: setPort(0); => autom. detect free port
            try {
                db = DB.newEmbeddedDB(configBuilder.build());
                db.start();
                db.source("db/1_create-database.sql");
                db.source("db/2_create-tables.sql", "root", "", "myDb");
                db.source("db/3_seed-data.sql", "root", "", "myDb");
            } catch (ManagedProcessException e) {
                e.printStackTrace();
            }
        }

        @Override
        protected void after() {
            try {
                db.stop();
            } catch (ManagedProcessException e) {
                e.printStackTrace();
            }
        }
    }

DriverManager.getConnection("jdbc:mysql://localhost/myDb", "root", "");
This will try to connect on port 3306. You probably have another mysql or mariaDB running on the system on port 3306, which it then tries to connect to.
Try using DriverManager.getConnection(configBuilder.getURL("myDb"), "root", "")
Or specify a different port, and remember to update the connection URL accordingly, for instance: configBuilder.setPort(33306);
DriverManager.getConnection("jdbc:mysql://localhost:33306/myDb", "root", "");

@vikrampatankar can we close this then? (Without hearing back from you within 1 week, I'll close it.)
@Maldivia thanks for answering this!

I think its time to close this.

Closing as "Answered".


Use latest falafel / acorn version

better ES6 / ES7 support
default es version is 7 (see acorn readme)

For a better support you might want to make parserOptions = {sourceType: 'module'} the default. It seems to be not exclusive and still allow require

Sorry for the delay and thanks for PR :) will merge :+1:


Avoid setting values when equal

In some cases, it’s useful to avoid calling setters when the values are known to be equal. In particular, calling a setter on an NSManagedObject will flag that object as updated in the context, which will trigger a database write, even if [newValue isEqual:oldValue].
This adds an optional -mts_checkValueOfKeyForEqualityBeforeAssignment:.

Hello @samkaufman, thanks for the pull request. I like the idea of what you are doing. I'll check the code and merge the pull request later today (and release a new cocoa pod version).
Cheers,

@vilanovi Hope it helps!

Hello @samkaufman ,
Just published to cocoa pods the new version of Motis 1.1.0 with your changes.
I have, however, updated the name of your method to "mts_checkValueEqualityBeforeAssignmentForKey".
Also, checkout the new feature of value mapping very useful for enums:
https://github.com/mobilejazz/Motis#12-value-mapping
Thanks,

Fantastic. Thanks, @vilanovi.


Modeling Exercises: Implement drag and magnification gestures

⚠ Should be merged after #169

Adds drag and magnification gestures to UML diagrams. Also, it makes the font size adjustable.
Note: The diagrams are not always centered correctly. I'm not sure what's wrong because the code seems to be correct 🤷♂

What's the difference between the two font sizes here? Can we somehow align them?
This might lead to confusions.

What's the difference between the two font sizes here? Can we somehow align them?
This might lead to confusions.

There's no difference. We have a duplicate because the toolbar has access to the AssessmentViewModel but not an ExerciseRendererViewModel. So, the font size changes made from the toolbar are stored separately in the AssessmentViewModel and later used to update the font size of a class conforming to ExerciseRendererViewModel.
A solution to this duplication could be to extract toolbar-related variables (fontSize & pencilModeDisabled) from AssessmentViewModel into a separate ViewModel (e.g. ToolbarViewModel) and pass it to the child views as an environment object (in a separate PR). What do you think?

Is this behavior intended?

Fixed 👍

Do you prefer arguments or multiple trailing closures? :)

Trailing closures 😅  Thanks for the review, @nityanandaz 👍


Delete server-side job on completion

Since we are putting jobs on a more user-friendly folder, should we not delete the engine job when the results are transferred ?

If the job is deleted we can not get the log file anymore.

maybe we should fetch the log file anyway and keep it in the same user-friendly folder as the job results (even if the job failed, the log file can be copied over), then it's easier to collect from users anyway, e.g. if they're filing a bug report, as it would be a standalone file instead of a web view.

It works for me (tried now with DTBook Validator), which script did you run? I will try to reproduce.

Ok now it works, perhaps I was testing the wrong version earlier.

I was wondering: would it also be possible to open the detailed log in the browser, like it used to? For a lot of people the browser is more familiar than the program that has been set as the default for opening .log files. Currently the file opens in Console (macOS) for me. For other people it might be a text editor.


babel-jest always installed by default

When I currently install jest it will automatically also install babel-jest.
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>
According to the docs, to enable babel transpilliation you just have to install babel-jest, but it will always be installed be default, so everyone (using npm >= 3) will always use babel to precompile, even if not necessary.
Is this intended or is there a way to tell jest to not use babel? To me it looks like it might not be needed and this is actually a (potential performance) bug, but it is the first time I look at the jest src.
I can create a PR to remove babel-jest from jest-runtime (The tests work just fine without it and it is not used in the src)
Or I can create a PR for the docs if you tell me how it works :)
I noticed this while trying to move babylon from ava to jest. There we run the tests agains a rollup-bundle that is already transpiled.
By default I get this error, which is babel trying to transpile the same bundle again:
  ● Test suite failed to run

    ReferenceError: babelHelpers is not defined

      at Object.<anonymous> (../lib/index.js:129:73)
      at Object.<anonymous> (index.js:3:15)

If I delete babel-jest from the node-modules folder by hand it works perfectly :
Test Suites: 1 passed, 1 total
Tests:       59 skipped, 2492 passed, 2551 total
Snapshots:   0 total
Time:        3.696s, estimated 5s

You can do "transform: {}" in Jest or customize your transformers.
http://facebook.github.io/jest/docs/configuration.html#content