[Feature request] Image compression

Description of the new feature / enhancement
It can be great if we can have an "Image Compression" component.
Scenario when this would be used?
It could be used anytime we want to compress an image.
I imagined the following scenarios :

select an image(s), right-click and click on "compress the image(s)".

right-click a folder and click on "compress the images in the folder".

It should either replace the images with the compressed version, or add a "compressed" suffix. For example :

"compress the images (replace)"
"compress the images (copy)"
... (other right click elements)

Supporting information
I came across this vscode extension by microsoft that already has the compression (for one or more images in a folder). I can get the repo (maybe it's proprietary ?).

This issue reads to me as: enable image resizer to act on all of the files in a folder (and maybe sub-folder). Does that sound right? /needinfo

I add to the request "optional loosless compression"

This issue reads to me as: enable image resizer to act on all of the files in a folder (and maybe sub-folder). Does that sound right? /needinfo

So the image resizer compresses the images, right ? If so, it's not really clear in the app that it does. And what if I don't want to resize, but only compress ?

/dup #2686


Adding summarized output of failures

Useful for parallel tests

@genebean Can you please review this?

Perfect. This will be release as soon as I get a chance. Likely the weekend or Monday

Released in v3.11.0


README: refer to v5 as released

This PR updates the README text to reflect that v5 has been released.

Thanks @olleolleolle!

@marcelolx Really appreciate the work that goes into maintaining this!


Add Support for Multiple Color Formats in Room Class

This update allows the Room class to accept the color parameter in multiple formats:

RGB list: [R, G, B]
Named color string (e.g., "red", "blue")
Hexadecimal string (e.g., "#0000FF")

Unit tests have been added to verify the functionality.

Great start! Besides my inline comments:

This all needs to work for things besides rooms, such as locations, hallways, objects, and robots.
The YAML loading/saving utilities need to also support serializing and deserializing these color names and hex codes to/from strings.

I'm okay if item 1 is reserved to follow-on PRs if you'd like to split it up, but 2 needs to be done and tested at least for the rooms case.
I'm also okay if no matter how a user specifies colors in code/YAML, they always serialize to a consistent RGB format in the to_yaml() methods. Probably easiest that way.

Point 1 : Yes, I am planning to do follow-on PRs for rest of things.
Regarding point 2, I tested the support for multiple color formats for Room object by modifying  room args in test_world.yaml. It works as expected without any changes to from_yaml() method of WorldYamlLoader class in yaml utils.


Q: Can I completely replace the sylesheet? Trying to use bootstrap

I am trying to change the look and feel of my app to use bootstrap, but adding bootstrap CSS to the /static directory only allows me partial changing the style of the components.
THis is likely due to what you describe here: https://www.streamsync.cloud/stylesheets.html#tips-for-effective-stylesheets in that it is not using the important flag, but does that mean we are always going to have to make our own stylesheet and cannot use existing ones, like bootstrap for streamsync apps?

Yes, the expectation is for CSS classes to be created ad-hoc and used sparingly to alter small details. For example, apply rounded corners to Image.
I think your experience isn't going to be great if you apply Bootstrap to any prebuilt components. That applies to Streamsync and to any other framework that uses prebuilt components.
The only way for Bootstrap to reliably work is to create raw HTML elements that align with what Bootstrap expects. The main reason is that most of the time you'll be dealing not with raw HTML elements but with complex trees of HTML elements.
The issue you mentioned does complicate things, since style fields configurable by Builder use the style attribute of HTML elements, which has higher specificity, so things like background or color do get lost unless flagged with !important.

Hi, I'll be looking at ways to get around this limitation using Vue's SFC CSS binding
@FabienArcellier My idea is to replace the computed rootStyle and such to the v-bind in CSS, so as to have the styles have lower specificity thus not needing !important for overriding in custom stylesheets.


Lint error: Expected type Schema (object) but got boolean appears when linting API definition

Describe the bug
Upon linting a valid API Definition, the error message "Expected type Schema (object) but got boolean" appears
To Reproduce
Steps to reproduce the behavior:

Given this redocly.yaml file:
redocly.yaml.zip

And this OpenAPI file
openapi.yaml.zip

Run this command: redocly lint openapi.yaml

See error: Expected type Schema (object) but got boolean

Expected behavior
In accordance with JSON Schema documentation:
https://json-schema.org/understanding-json-schema/reference/object#extending, in order to extend closed schemas you can write your schema as in the example below:

components:
  schemas:
    MyObject:
      type: object
      additionalProperties: false
      allOf:
        - $ref: '#/components/schemas/MyObjectBase'
      properties:
        property1: true
        property2: true
      required:
        - property2
    MyObjectBase:
      type: object
      properties:
        property1:
          type: string
        property2:
          type: string
      required:
        - property1

However,  it seems Redocly CLI does not cover this use case since the error message occurs:

 Front conversations

seems like your indentation is incorrect.  the second allOf schema should be under an array - definition

components:
  schemas:
    MyObject:
      type: object
      additionalProperties: false
      allOf:
        - $ref: '#/components/schemas/MyObjectBase'
        - properties:
            property1: true
            property2: true
          required:
            - property2
    MyObjectBase:
      type: object
      properties:
        property1:
          type: string
        property2:
          type: string
      required:
        - property1

Does this solve your issue? Can this be closed?

@jeremyfiel I don't think it does. The issue is that the linter doesn't recognise a boolean value of properties. And I don't know if it's better to allow the booleans or use unevaluatedProperties (like in this example) instead of additionalProperties + boolean properties.

Thanks everyone for the clear explanations. It's a valid bug IMO, although kind of an edge case for a specific way to extend a closed schema, I'm actually not sure I've seen this usage before in an OpenAPI context. For organisations who do control their own schemas, I think enabling additionalProperties on the base schema, or refactoring the structure would be a good workaround while we consider how to prioritise adding support for this case.

It depends which version of OAS they are using to determine if this is a bug or not. In JSON Schema draft 7+, it is valid to have a Boolean schema or an object schema but that requires the use of OAS 3.1.x.  if using OAS 3.0.x, Boolean schemas were not allowed and must be an empty schema property:{}, in which case this would not be a valid use case and the error is correctly reporting. I figured this usage was intended to be an allOf array of schemas and their indentation was incorrect. I suppose they can also write their schema in the way they've written it, although they need to adjust it with the empty schema.


[Task]: Implement ECMWF file usage in DISP-S1 Workflow

Checked for similar tasks
Yes - I've already checked
Describe the task
Ticket to implement inclusion of ECMWF files when staging products for use with a DISP-S1 job.
This feature should include a toggle (in settings.yaml) to bypass inclusion of ECMWF files for ease of testing while we are waiting for files to be populated in S3.
The staging logic should also query S3 to ensure existence of the expected files (based on acquisition dates of input CSLC products) before they are included with the RunConfig for the job.
Prerequisites or Requirements
1.
2.
3.
...

Expected Deliverables
1.
2.
3.
...

Additional Context
No response

Tropospheric Correction PGE will process the ECMWF data. DISP-S1 won't need to use the ECMWF data.


Fix typo in README

Probably not what you envisioned for your first pull request. Just a quick little update to the README fixing my last name. Thanks again :smile:

@jordanbyron thx - sorry for the late fix.


lessc compiler doesn't work with latest node

Hi,
I installed less with npm install less -g . It doesn't work with latest node version ( mine is 0.5.10 ):
The "sys" module is now called "util". It should have a similar interface.
node.js:202
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead.
    at Function.<anonymous> (module.js:376:11)
    at Object.<anonymous> (/usr/local/lib/node_modules/less/bin/lessc:7:8)
    at Module._compile (module.js:432:26)
    at Object..js (module.js:450:10)
    at Module.load (module.js:351:31)
    at Function._load (module.js:310:12)
    at Array.<anonymous> (module.js:470:10)
    at EventEmitter._tickCallback (node.js:194:26)
The "sys" module is now called "util". It should have a similar interface.

node.js:202
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead.
    at Function.<anonymous> (module.js:376:11)
    at Object.<anonymous> (/usr/local/lib/node_modules/less/bin/lessc:7:8)
    at Module._compile (module.js:432:26)
    at Object..js (module.js:450:10)
    at Module.load (module.js:351:31)
    at Function._load (module.js:310:12)
    at Array.<anonymous> (module.js:470:10)
    at EventEmitter._tickCallback (node.js:194:26)

I couldn't find repository of this module on github so I'm reporting it here.

0.5.10 is unstable so most npm packages don't work with it. Also yeah - file this with less thanks!

@thomaschaaf Thank you. I downloaded less compiler for node from npm and the repo address was not mentioned in json file so I made an issue here. Ok somebody sent a pull request for them that solves the issue.
@fat yeah you are right.


Enhancement: Prisma Migrate with database seeding

With Prisma Migrate reaching general availability a prisma migrate deploy && prisma db seed workflow would help in making production schema updates easier addressing #527, #545 and #556.
I've written a PR with updated schemas, migrations and a seed file. After making a change to a schema in development you would run either:
prisma migrate dev --name=change --schema=./prisma/mysql/schema.mysql.prisma
prisma migrate dev --name=change --schema=./prisma/postgresql/schema.postgresql.prisma
You would see similar output:
The following migration(s) have been created and applied from new schema changes:

migrations/
  └─<PHONE_NUMBER>0843_change/
    └─ migration.sql

Your database is now in sync with your schema.

These changes would be committed to source code and can be easily applied in production.
Pull a Docker image or repository in production and bring the schema up to date by running the commands:
prisma migrate deploy --schema=./prisma/mysql/schema.mysql.prisma
prisma db seed --schema=./prisma/mysql/schema.mysql.prisma --preview-feature

OR
prisma migrate deploy --schema=./prisma/postgresql/schema.postgresql.prisma
prisma db seed --schema=./prisma/postgresql/schema.postgresql.prisma --preview-feature

The seed file also supports a preconfigured password by reading the ADMIN_PASSWORD environment variable.

This looks great. A few questions though,

Are the migration files necessary at this point? the DB schema hasn't changed yet. Though I could see it being useful for future updates.
Can we use this to initially populate the database so users won't have to run the sql file manually?

Migration files aren't strictly necessary unless you had to rename table columns in production with no risk of data loss.
I tested the commands below work to populate the schema. The caveat is you'd need to take a database snapshot when the schema changes if you run the commands again after the initial seed phase.

prisma db push --schema=./prisma/schema.mysql.prisma --preview-feature
prisma db push --schema=./prisma/schema.postgresql.prisma --preview-feature

Note the help output:
🙌  Push the state from your Prisma schema to your database
WARNING Prisma db push is currently in Preview (https://pris.ly/d/preview).
There may be bugs and it's not recommended to use it in production environments.


Purge corrupt Perf Db entries

The following solvers have updated IsValid method in the Performance Config and obsolete / corrupt entries need to be purged from the Perf Db

[ ] ConvHipImplicitGemmV4R1WrW
[ ] ConvHipImplicitGemmV4R1Fwd

@zjing14  Please update the description above so we can assess what needs to be checked as well as retuned

@JehandadKhan Updated.

@JehandadKhan Updated.

@jeffdaily  @cderb has the purge been performed already? May we close this issue?

Why did I get tagged?

Why did I get tagged?

Sorry, mis-tagged :)


Issue 123 shortcut link from view diagram elements to views

Creates "small" link objects in the corner of parent elements if diagram/sketch is DND from side tree.

OK,thanks. But the eol changed files (ASyncRunner and TestUtils) shouldn't be on this branch. That's another issue. Can you redo the PR without those and the ,gitattributes file? We need to deal with the eol issues some other way, too much weirdness in that issue.
The ,gitattributes file is confusing my git client (SmartGit)

Closing this as we'd need a new PR.


Sankey onLinkMouseOver and onLinkMouseOut behaviour

Using the sankey diagram I noticed that onLinkMouseOver event doesnt get triggered while hovering the links label, but instead onLinkMouseOut is fired. Seemed counterintuitive to me, if someone wanted to style the links based on hover events.
Is this intended behaviour?

I don't quite understand what you mean? The sankeys here http://uber.github.io/react-vis/examples/showcases/sankeys appear to be working as I might expect, but I could be wrong?

Closing, but feel free to reopen


  Discourse has an option to dismiss all of the tooltips, which is nice for people who have already been through the signup/intro process on another instance before.

I agree with this, though I don't know if we'll do it before a broader overhaul of the ~4 tooltips.  One thing to note, @jtrakk: when you create your Zulip account on a given Zulip installation (E.g. all of Zulip Cloud is a single installation), you're offered the option to copy personal settings from an existing Zulip account -- and that includes skipping the introductory tooltips.
So in the future, you may be able to avoid this through that technique.  (I don't see this as a general solution for the product).

Closing in favor of #29296.


Error building and applying patched kernel modules for:  Ubuntu 22 (jammy) with LTS kernel 5.15

I'm following the instructions at (https://github.com/IntelRealSense/librealsense/blob/development/doc/installation.md) and have run into an error at the step:
Build and apply patched kernel modules for:

Ubuntu 20/22 (focal/jammy) with LTS kernel 5.13, 5.15
./scripts/patch-realsense-ubuntu-lts-hwe.sh

The error is:
Fetching Ubuntu LTS tag   to the local kernel sources folder
fatal: You need to specify a tag name.

Full output of the script below:
ben@raspberrypi:~/librealsense$ ./scripts/patch-realsense-ubuntu-lts-hwe.sh

Remove all RealSense cameras attached. Hit any key when ready

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
bc is already the newest version (1.07.1-3build1).
build-essential is already the newest version (12.9ubuntu3).
git is already the newest version (1:2.34.1-1ubuntu1.10).
linux-headers-generic is already the newest version (<IP_ADDRESS>.86).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Package required libusb-1.0-0-dev:  - found
Package required libssl-dev:  - found
Create patches workspace in ubuntu-jammy folder

Package required libelf-dev:  - found
Package required elfutils:  - found
Package required bison:  - found
Package required flex:  - found
Package required dwarves:  - found
Fetching Ubuntu LTS tag   to the local kernel sources folder
fatal: You need to specify a tag name.

Note: I had to run the entire script as super user to get this far, I had other failures earlier in the script if I didn't but that is a separate issue.
Here is the output of uname on my system:
uname -a
Linux raspberrypi 5.15.0-1043-raspi #46-Ubuntu SMP PREEMPT Mon Nov 13 15:08:58 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

Hi @benpeart  I note at the bottom of your opening post that you are using Raspberry Pi.  The kernel patch scripts listed on the installation.md instruction page are not designed for computing devices with Arm archiecture such as Pi, but instead for computers with x86 / x64 architecture such as laptop and desktop PCs.
The best method for installing the librealsense SDK for Ubuntu on Pi is to build from source code but include the build flag -DFORCE_RSUSB_BACKEND=TRUE in the CMake build instruction.  This builds the SDK in RSUSB mode, which bypasses the Linux kernel.  The SDK build is therefore not dependent on Linux versions or kernel versions and does not require kernel patching.
A simple method of building from source on Arm devices without needing to apply a kernel patch is to use a build script at the link below.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md
The libuvc_installation.sh script builds the SDK with the flag -DFORCE_LIBUVC=true, which was the predecessor of the -DFORCE_RSUSB_BACKEND flag.

Yea, I started with Raspbian as the OS but when it didn't work (probably the Bullseye issue you mentioned) I switched to Ubuntu MATE per the Raspberry Pi 3  instructions.
Sounds like Intel no longer has an official working/supported version for Raspberry Pi. When looking for ROS2 support, I noticed the Intel Robotics SDK was depreciated about 4 years ago. Looks like bought I an Intel RealSense camera for my robotic project a few years too late. :)
I'll try the steps in #11506 and see if I have success. If not, I guess I'll have to shop around for a different pointcloud/LIDAR/skeletal tracking solution for my project. Thanks for your help.

Hi @benpeart  Do you require further assistance with this case, please?  Thanks!

No, I've given up on trying to get it to work on Raspberry Pi. Raspbian, Ubuntu, Ubuntu MATE. Don't work. I even tried going back to the last Intel supported version of Raspbian but it is so old, I can't download packages for the OS (they return 404 errors indicating they no longer exist).

No, I've given up on trying to get it to work on Raspberry Pi. Raspbian, Ubuntu, Ubuntu MATE. Don't work. I even tried going back to the last Intel supported version of Raspbian but it is so old, I can't download packages for the OS (they return 404 errors indicating they no longer exist).

Okay, thanks very much for the update.  I'm sincerely sorry that you did not get the outcome that you were seeking.

I'm taking over from a system that was left unfinished a while back.  The system uses a D455 connected to a Raspberry Pi4B running ubuntu 22.04 (and ROS humble).
Is the conclusion of this thread that the D455 (or any realsense device) will indeed not work on the RPI?
If this is the case, this is hugely disappointing and (1) will likely stop many small robotics projects and (2) needs to be made very clear to people as there is nothing in any documentation that states that, apart from places like this thread, that people will not read until too late.  We are now left with a bunch of small robots that have no way forward (no pun intended) because of that.

Hi @flabrosse  RealSense camera hardware, including D455, can work with Raspberry Pi.  When problems occur, it is usually with the software side (the installation of the RealSense SDK on Pi boards).  Installation is certainly possible but may be challenging.
It is worth mentioning that whilst depth and color streams can work correctly on Raspberry Pi, the IMU streams (accel and gyro) of IMU-equipped RealSense camera models such as D435i and D455 may not be accessible on Pi.
If SDK installation problems are experienced, I recommend trying the libuvc backend build script at the link below as libuvc has a high past success rate on Pi boards.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

Thanks @MartyG-RealSense.  Your comment from 05/12/2023 seemed to indicate that the script libuvc_installation was the old way of doing this:

The libuvc_installation.sh script builds the SDK with the flag -DFORCE_LIBUVC=true, which was the predecessor of the -DFORCE_RSUSB_BACKEND flag.

So I instead installed from sources using -DFORCE_RSUSB_BACKEND=true as a cmake argument.  This worked (compiled and installed) but no camera is being detected.  I'll try the script mentioned above now.


Validation errors only after "touched"

First of all, @ealush thank you for this marvelous form validation library. I really like the creative solution to use the same DSL we use for testing for validation. I also love that it's framework-agnostic. I also love that it's an importable small script.
I'm building some examples on my blog on how to incorporate AgnosticUI http://agnosticui.com/ and use Vest for the validation. It's going quite well and I'm close to having my first example complete!
There is one thing…
Overview
Many form validation libraries or engines hold the notion of a field being "touched" when it's been interacted with and then blurred.
I searched the documentation site for touched and only found one reference here:
https://vestjs.dev/docs/writing_your_suite/optional_fields#advanced-usage---supplying-custom-omission-function
But I still don't see or perhaps understand how this is achieved in Vest.
Reproductions
The default examples appear to eagerly report validation errors as I've described. Below is a screen grab, but also here are the repro steps:

visited username field
entered a single character

Result: Error messages hints displayed
Expected: There should be no error message hints displayed until I blur out of said field

visited the password field
entered first character

Result: Error messages hints displayed
Expected: There should be no error message hints displayed until I blur out of said field

Remarks
I think in UX circles this sort of thing is called "shouting". I would prefer if my password field validity is only shown once I've interacted with the field and then navigated out of it (e.g. touched or blurred the field if you will). Is this achievable and documented and I just missed it?

Hey @roblevintennis, thank you for your feedback, I always love learning about new integrations with Vest.
I am not near a computer, and it might take some time for me to give a more detailed reply. Nevertheless, I do intend to give a more in-depth reply.
I'll try to briefly describe the core concepts:
The reason Vest does not have the notion of touched is that vest is not a UI framework, meaning it knows nothing about the UI state. This means it cannot know about the interaction with the inputs, and really, vest does not even have to retain a 1 to 1 relationship between inputs and tests. Instead, all Vest cares for are validation states:
tested, failing, valid, pending, omitted, skipped.
In most cases, touched is correlary to tested, meaning - trigerring validation of a certain field on blur rather than on should be sufficient.
To do that, use only with the name of the touched field. You can look up the only function in the api reference. https://vestjs.dev/docs/api_reference
I did not yet read your code, or look deeper into your implementation, I will do that when I'm near a computer, but in the meantime I hope this at least somewhat helps.

Thanks @ealush that's very helpful indeed!
The suite.js code is mostly a copy of your example which already does the only(currentField) anyway so we're good there -- now that I properly understand the "concerns" being managed by Vest I think my issue is resolved.
It was of course very easy to add the following in my code which results in the suite only getting called once a field has been touched per your recommendation:

  let touched = {
    tos: false,
    username: false,
    password: false,
    confirm: false,
  };

  const validate = fieldName => {
    if (touched[fieldName]) {
      result = suite(formState, fieldName);
      result.done(res => {
        usernamePending = false;
        result = res;
        // console.log('Vent Result: ', { result })
      });
    }
  }
  /**
   * Blurring field makes it "touched" and candidate for validation
   */
  const handleBlur = name => {
    if (touched[name] === false) {
      touched[name] = true;
      // First time this field is considered "touched" e.g. user just tab'd or clicked out
      // of the field. As such, we now need to validate said field for the first time!
      validate(name);
    }
  }
 // ... code omitted for brevity but we listen for change events and potentially call validate
// from other places too. But only evaluated if we've set touched.FIELDNAME to true.

My spot checks confirm this is working. Thanks again! I'll go ahead and close this issue out 👍

@roblevintennis
Awesome! Very happy to hear that it worked as expected.
Also, just taken a look at AgnosticUI - that's some impressive project you got going there. I am definitely going to keep an eye on it!

Thanks @ealush I really appreciate it from you 🙂
I will ping you but I have a Svelte based blog where I'm starting to dig food agnostic-svelte and the very first example I thought of was using Vest. I saw your presentation at Svelte conference (I think or maybe Vue) but was very impressed by the idea and that it's not tied to any framework. So I had to see how they work together and I am NOT disappointed!
Again I will ping you once I have something to show. Thanks for building such a nice validation lib!


[Issue #111] Initial Join API: Made suggested changes to the API

Made the suggested changes to the API and have modified the example to reflect the same.

The changes look in general.  Per our discussion, I have two minor comments related to book-keeping purposes:

Make the branch name more specific;
Add comments to this PR about what we are doing in this PR and why.

After that, you can do the merge.
@FlavioBayer

As discussed F2F, there's no need for different attributes for the inner an outer operators, since both should be joined on the same attribute

At this moment I think we can use the same "id attribute" for both sides.  We can always "split" it to two in the future if needed.


"Vault [is] most easily deployed with Vault kit" which itself requires Vault

The Genesis README includes:

Genesis v2 makes use of Vault as a back-end for storing credentials, most easily deployed + managed via the Vault kit, and the safe CLI.

Except that Genesis requires Vault, even for deploying Vault itself.
$ genesis init --kit vault
$ cd vault-deployments
$ genesis new local
...
No Vaults have been targeted yet.

You will need to target a Vault manually first.

What are other ppl doing to bootstrap Vault here?

if you are deploying your first vault,
$ vault server -dev

and then target it over localhost:8200.
this may be helpful: https://github.com/starkandwayne/codex/blob/master/aws.md#vault-init

Thanks for link.

I've just run into this egg/chicken problem for a while with a brand new setup 😅.  Looks like spinning a local Vault dev is the way to go. Are there some tips somewhere in the genesis docs regarding the start from scratch state? If there is none, I think it's definitely worth adding a line closer to the genesis docs.
@jhunt Looks like the link above is dead as aws.md is now living inside docs. This one should be working https://github.com/starkandwayne/codex/blob/master/docs/aws.md#vault-init :)

Extra tip 😜 for anyone that faces the dead link issue, in case it helps. Pressing "Y" to get a permalink whenever I'm linking in an issue/PR a file that might change later. Here the permalink for aws.md https://github.com/starkandwayne/codex/blob/560e1e8cbd2e7e4b95422ab2c06843bb556f6674/docs/aws.md#vault-init
The CON about permalinks is that they point to that version of the file though.
Here a link to the github docs for the later feature https://help.github.com/articles/getting-permanent-links-to-files/

We now also have safe local


$auth.login is not a function

Hi everyone,
I'm doing everything as written but always get same error:
angular.js:12450 TypeError: $auth.login is not a function

login.html:

    <input type="email" class="form-control underline-input" placeholder="Email" ng-model="user.email" required>

    <input type="password" placeholder="Password" class="form-control underline-input" ng-model="user.password" required>

    <button type="submit" class="btn btn-greensea b-0 br-2 mr-5" ng-click="login()" ng-disabled='form.$invalid'>Login</button>

      <input type="checkbox"> Remember me

    Forgot Password?

</form>

Login controller:
 .controller('LoginCtrl', function ($scope, $auth) {

    $scope.user = {};
    $scope.user.email =<EMAIL_ADDRESS>    $scope.user.password = 'test';

    $scope.login = function () {
      $auth.login($scope.user).then (
        function (response) {
          console.log(response);
        },
        function (error) {
          console.log(error);
        }
      )
    }

app.js:
     .config(['$stateProvider', '$urlRouterProvider', '$authProvider', function($stateProvider, $urlRouterProvider, $authProvider ) {

          $authProvider.loginUrl = '/auth/login';
...

I tried different settlements, researched github issues but not found a solution.
Whats my fault? How can I fix it?

@rozehan Have you tried running the sample app provided in the repo? If it works fine then the issue is on your side.
The only reason I can think of is that you have another module with conflicting $auth service (I have never run into such case so not sure how Angular handles it)  or perhaps you yourself have overridden $auth variable somewhere.

Yes, it conflict with ng-token-auth. When I uninstall other module, it worked!
Thanks.

Thanks


feat: Moving README and CONTRIBUTING files to be Static

These doc files have been very inflexible for teams to write useful documentation on top of, and hence the vast majority of services have exactly this doc available out of the box with no changes.  This change will allow teams to do whatever they desire with the README docs.

If I'm reading the docs correctly, this should be compatible with existing READMEs (it won't try to re-stencil again).

Correct -- this will now only generate the file if it does not exist.


Debugger does not halt after step over or step out of call to printf when using gdb

Describe the bug
When stepping over or stepping out of printf, the debugger does not halt on the next instruction but instead continues the program to its end.
To Reproduce
Steps to reproduce the behavior:

Compiler program fibber.c (code at the end) and import into project and analyze it.

Open in debugger and select Debugger > Configure and Launch fibber_bin using... > gdb

Choose Run command: Start in the popup window and press Launch

Debugger stops in main on instruction 0x001011b4, Dynamic - Auto PC window has not Disassembled after call to printf

Click "Step over" until on call to printf

Click "Step over" again, instead of halting on next instruction program runs to the end and exits normally.

Expected behavior
Program would halt on instruction after call to printf.
Attachments
If applicable, please attach any files that caused problems or log files generated by the software.
Environment (please complete the following information):

OS: Ubuntu 22 and 24
Java Version: 21.0.4
Ghidra Version: 11.1.2
Ghidra Origin: Github distro
GDB Version: 12 and 15.0.50

Additional context
Tested with program
// fibber.c: A simple recursive Fibbonacci sequence calculation program
#include <stdio.h>

unsigned int fibbonacci(unsigned int n){
    if(n <= 1){
        return n;
    }
    else{
        return (fibbonacci(n-1) + fibbonacci(n-2));
    }
}

int main(){
    unsigned int n = 10;

    printf("First %d elements of the Fibbonacci sequence: ", n);

    for(unsigned int i = 0; i < n; i++){
        printf("%d ", fibbonacci(i));
    }
    printf("\n");
    return 0;
}

@Erikun  Looking into this - can definitely reproduce what you're seeing (and definitely a bug).  No clue yet as to why this is happening.  More soon.

I've found the cause and a workaround. We use a catchpoint to detect changes to the memory map. If you type info breakpoint into the Terminal right after launch, you can see it.
This issue, I believe, is that the first call to printf causes the module to be lazily loaded, which hits this catchpoint. We have a command list in there, intending to avoid actually breakpoint, ends with cont. Sadly, I suspect this final cont overrides your nexti or Step Over button.
You can work around the issue by typing dis 1 into the Terminal after launch. You'll have to refresh the Memory Map on your own from that point on, though. If it seems your program counter has disappeared into nowhere (i.e., the dynamic listing stops tracking), then right-click the Memory node in the Model panel and select "Refresh Memory."
Clearly, this is a big problem. I guess we'll want an alternative for automatic memory refresh....


Standardise dataset description format

Goal
Few shot prompt engineering to ensure that the model can return generative descriptions of datasets that incorporate user needs, but also returns essential information from metadata e.g. summary, why its relevant, further reading and links..
Scope
Define the limits of the work to be carried out; what is included or not included?
User Stories & Acceptance Criteria

When I [context], I want to [action], so that I can [outcome]

Given [context], when [specific action], then [response or consequence to action]

Risks & Questions
Solution Hints
Future work
Summary
What does this research help us do? What future work will this unlock or what decisions it enable?
Key questions
(no more than 5) What do we want this spike to answer? Focus on outcomes.
Expected Output(s)
What artefacts do we expect to produce that will help us answer the above questions? May be designs, documents, a prototype feature…
Hints
Suggestions about how to go about the research. How might we answer these questions?

Just to add some more detail on what links would be useful to surface alongside data... these could be links to:

download data
access data in other products (e.g., GFW)
blog posts (technical or use case-oriented)
recorded webinars


docs: redirect /doc/cml to cml.dev/doc

Now that https://github.com/iterative/cml-website/pull/60 is merged,

https://dvc.org/doc/cml/ should 301 redirect to https://cml.dev/doc/
current /content/docs/cml/ stuff in this repo can be removed

Part of https://github.com/iterative/cml/issues/514

Please coordinate with me to try and redirect the ranking from Google Search Console too.

@jorgeorpinel is this (hopefully not impossible) search stuff related to the implementation in this repo, or can it be tackled separately?

Can def. be tackled separately. There might just be a time window where the ranking redirection is possible.

We should probably try to add cml.dev to our Google Search Console properties first though... Requires DNS verification cc @shcheklein or @rogermparent yelp

Can def. be tackled separately. There might just be a time window where the ranking redirection is possible. So ideally letr's do both at the same time.

@jorgeorpinel done with implementation (#2658) so please lemme know if you need to coordinate about search console stuff.

Well up to you really. Do you want to preserve traffic? 🙂 I posted on our chat but didn't have a reply yet. Will tag you.


specify Desktop in idleTimeout

idleTimeout is desktop only. Need to specify this.

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@lauramthomas did this break the formatting on the Caps page? Something I've been meaning to ask is there a screenshot as part of the pull request? to see what it looks like


README.md snippet missing setAuthenticatedUserContext

The README.md snippet does not include the full API implementation.
e.g. You cant call window.appInsights.setAuthenticatedUserContext('xxx')
Work around:
To get it working i changed
n("startTrackPage"),n("stopTrackPage")
to
n("startTrackPage"),n("stopTrackPage"),n("setAuthenticatedUserContext")

Thanks for pointing this out. #902 will fix this. It is the same as your workaround, so you don't need to redo your snippet


Cisco ASA/FTD Parser for Syslog (Cisco ASA via Legacy Agent)

Is your feature request related to a problem? Please describe.
We have onboarded Cisco ASA logs into sentinel using data connector "Cisco ASA via Legacy Agent" but currently haven't found any parsers that will parse all the cisco ASA/FTD logs, none of the logs were getting parsed.
Describe the solution you'd like
Is there any Query which will parse all the fields, or do we need to onboard it through different method to get all logs parsed ?
Any other solution is appreciated.
Describe alternatives you've considered
Tried multiple ways to build KQL query to parse the individuals fields but couldn't combine them into a single KQL query to see all the possible fields but got stuck.
Also tried to build different function but unfortunately even that didn't worked.
Additional context
For building analytical rules and Workbook I was using the following KQL operators
| extend Source_IP = extract("REGEX", 0, Message)
but while reviewing ASA logs I found that single regex wont be useful here according to logs i have to write these much but cant combine them.

Hi @RajakiRani, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 21-06-2024. Thanks!

Hi @RajakiRani,
We required logs to investigate more on this issue, please share the logs with us on mail id.
<EMAIL_ADDRESS>Thanks

Hi @RajakiRani,
We are waiting for response from you.
Thanks

Hi @RajakiRani, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 05-07-2024 date, we will be closing this issue.
Thanks!

%FTD-6-305011: Built dynamic TCP translation from INSIDE:<IP_ADDRESS>/39893 to OUTSIDE:<IP_ADDRESS>/53
%FTD-6-305012: Teardown dynamic UDP translation from INSIDE:<IP_ADDRESS>/50752 to OUTSIDE:<IP_ADDRESS>/50752 duration 0:00:00
%FTD-6-852002: Received Full Proxy to Lightweight event from application Snort for TCP flow <IP_ADDRESS>/7386 to <IP_ADDRESS>/474787

@RajakiRani, It's possible to share logs in csv format with us in below mail id so we can repro the same from our end. Thank!
<EMAIL_ADDRESS>

@RajakiRani, Waiting for your response, please share logs so we can repro this issue from our end. Thanks!

Hi @RajakiRani, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 18-07-2024 date, we will be closing this issue.
Thanks!

Hi @RajakiRani, since we have not received a response in the last 5 days, we are closing your issue as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.


Problem when loading page; e.g. index.php

A PHP Error was encountered
Severity: Notice
Message: Only variable references should be returned by reference
Filename: core/Common.php
Line Number: 256

Which version you have installed. Have u made any changes to the config file or any of the core classes? This seems a issue with the CI.

I get the same error after upgrading from Debian Wheezy to Jessie. The PHP packages went from 5.4 to 5.6.

This change is already in the latest version. So should be fixed.

This change is already in the latest version. So should be fixed.


#49903 - SideMenu module

Please add vue transitions to get nice slide effect. You can check current oncs from modal or sidebar components or add new if needed.

Please update branch with develop


Fix #553

This replaces two unwraps with Results and makes PFCanvasSetFontByPostScriptName return an i32 to indicate success or failure.
Intended to fix #553

Yea. This isn't really possible without breaking existing code.
I modified it a bit so the underlying errors are available and the  unwrap() works.

@jayvdb can you review it again?


Optionally drop --privileged and other insecure flags

One of toolbox's use cases for me is having a container with compilers and development tools. For such containers I would prefer to not use --privileged, not mount /dev and other sensitive directories if not needed.
Since the main use case of toolbox is debugging (which requires those flags and the goal is not sandboxing), I think it would make sense to have a CLI option for creating more sandboxed/secure containers.

For what is worth, this makes sense to me. I would keep toolbox privileged and unsafe by default, because as you said, toolbox's goal is not sandboxing. But it should be possible to have something like this as an option. I may be able to draft something in the next days, but I can't be sure about that, so anyone feel free to beat me to it. :-)

I tried to address this (or at least, to start doing that) in https://github.com/openSUSE/microos-toolbox/pull/42 . Let me know what you think.


Tomcat SessionManager packaging

Is your feature request related to a problem? Please describe.
The present installation instructions for the Tomcat SessionManager require you to add two JARs to the Tomcat common classloader: redisson-all and a redisson-tomcat-x for your version of Tomcat. The problem here is that redisson-all is a huge JAR with a number of libraries that are shaded into it (like in regards to SnakeYAML #1594). This ends up creating a classloader problem where you can get LinkageError exceptions or missing method/class exceptions.
Ultimately, either you need to force all of the applications deployed to that Tomcat to use the library versions bundled in redisson-all, don't use any of the libraries in redisson-all, or don't use Redisson as your session manager.
Describe the solution you'd like
Install a single JAR that has shaded and relocated all of the libraries it needs to function within Tomcat. This would keep the libraries required by Redisson's Tomcat SessionManager hidden from the applications running on Tomcat.
Shading and relocating the dependencies doesn't have to be the only solution, but it's generally the simplest solution to hide classes on the classpath. If there were an alternative solution that hid all of the dependencies required by Redisson's Tomcat session manager that would be acceptable too.
Describe alternatives you've considered
I have been talking with the Tomcat folks about this and there are really two options at the moment:

Don't use any of the libraries that are bundled in redisson-all in your apps. This can be difficult. If you have a Spring Boot app, you're pretty much going to overlap.
Set <Loader delegate="true" /> in conf/context.xml. This reverses the classloader lookup order so that it prefers classes that are in the common classloader over classes in the webapp. This has downsides, most notably, that it forces all of the applications deployed to Tomcat to use the version of the libraries bundled with redisson-all. That is a non-starter for a number of situations.

As alternative you can copy set of required jars instead of redisson-all.jar, like redisson.jar, netty.jar ...

As alternative you can copy set of required jars instead of redisson-all.jar, like redisson.jar, netty.jar ...

Do you know what the minimal set of required JARs would be?
I suspect there will still be overlap though. There are a lot of popular JARs being used by Redisson, like netty & some of the reactive libs. The app I've been using isn't anything exotic, it's just your standard Spring app which also happens to use netty and reactive libraries for it's WebClient.

Here is the list of required libs: https://github.com/redisson/redisson/wiki/15.-Dependency-list


For release V6.1.5

Codecov Report

Merging #203 into master will increase coverage by 3.16%.
The diff coverage is 30%.

@@             Coverage Diff              @@
##             master     #203      +/-   ##
============================================
+ Coverage     29.66%   32.83%   +3.16%
- Complexity     1248     1428     +180
============================================
  Files            97       97
  Lines         23303    23359      +56
  Branches       3871     3881      +10
============================================
+ Hits           6913     7670     +757
+ Misses        15041    14148     -893
- Partials       1349     1541     +192

Flag
Coverage Δ
Complexity Δ

#JDBC41
32.72% <30%> (+3.12%)
1424 <0> (+180)
:white_check_mark:

#JDBC42
32.76% <30%> (+3.17%)
1426 <0> (+179)
:white_check_mark:

Impacted Files
Coverage Δ
Complexity Δ

.../java/com/microsoft/sqlserver/jdbc/StreamDone.java
77.27% <ø> (+27.27%)
19 <0> (+5)
:white_check_mark:

...om/microsoft/sqlserver/jdbc/SQLServerResource.java
100% <ø> (ø)
4 <0> (ø)
:x:

.../microsoft/sqlserver/jdbc/SQLServerDataSource.java
41.24% <0%> (-1.49%)
54 <0> (+1)

...m/microsoft/sqlserver/jdbc/KerbAuthentication.java
0% <0%> (ø)
0 <0> (ø)
:x:

...m/microsoft/sqlserver/jdbc/SQLServerStatement.java
58.25% <50%> (+5.36%)
128 <0> (+21)
:white_check_mark:

.../microsoft/sqlserver/jdbc/SQLServerConnection.java
40.1% <7.14%> (+1.32%)
204 <0> (+14)
:white_check_mark:

.../com/microsoft/sqlserver/jdbc/SQLServerDriver.java
73.39% <75%> (+2.41%)
25 <0> (+2)
:white_check_mark:

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
36.41% <92.85%> (+4.38%)
0 <0> (ø)
:x:

...om/microsoft/sqlserver/jdbc/SimpleInputStream.java
38.23% <0%> (-1.48%)
9% <0%> (-1%)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
45.01% <0%> (-1.02%)
182% <0%> (-1%)

... and 25 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 6b0964b...e24866c. Read the comment docs.


Meta: Download stylesheets and other CSS resources when importing WPT tests

We were missing these previously. Specifically this showed up with /fonts/ahem.css, but there are plenty of other resources that were missed. I've re-imported the tests that I noticed had wrong includes, and this has made 36 subtests pass in our local copy, which previously failed.
This partly reverts #2177, because the ahem.css hack is no longer needed. :^)

Update: Added another fix for the importer, so that it now understands when the path to the reference page starts with /.
CI failed on one of the imported tests that I fixed. Specifically, on Lagom (Linux, ubuntu-24.04, NO_FUZZ, GNU, false) / CI we get a few more subtests passing in css/css-flexbox/flex-item-compressible-001.html - but not on the others.

Update: The inconsistent test result vanished after a re-push, so I've skipped it. It seems related to font loading so it's possible other tests will also be affected.
After talking with Andreas I've annotated the skipped-test list with some reasons why they're skipped. Not especially detailed, but hopefully it'll act as a reminder when people skip tests in future to add their own note. :^)

Changes: Tell prettier to ignore WPT ref test files


finished translation for amazon-lambda.adoc.po

finished translation for amazon-lambda.adoc.po

Thanks @hongquli - It is great!

Thanks @hongquli and there only 3 msgid have not been translated. I will take care of them after merging.


updateStatus is very hairy

Everything it does, it arguably needs to do. But it can definitely be broken out into a few helper functions.

Functions to break out (both internal, no public API changes):

whitelistApplication
resolveChallenge

https://github.com/AdChain/AdChainRegistry/commit/d016f1bb66e9ddd49e65c9b6ec147d2e8057abde


/setwarp not working

Version: 3.1.10
Minecraft-Version: 1.13.2, ...
Server-Oparating-System: Linux

Expectation:
Update the selected warp

Actual behavior:
/setwarp returns a  "uknown command" message
I also tried with /editwarp

Error:
No errors on console

Sorry for the late comment, but did you disabled the SimpleWarps?

Oh I see, I had it disabled... enabling it fixed it.


[Feature]A vela command line is wanted for converting container app to kubevela app

Request description
In the process of enterprise practice, there are large mount container apps needed to convert kubevela apps.Therefore,
we need a feature for converting container app to kubevela app easily and conveniently.
Solutions
Step 1. There is a vela command line as follows
vela convert [{comp=comp_c,cluster=cluster_a, ns=ns_a, deployName=deploy_a}, {comp=comp_c,cluster=cluster_b, ns=ns_b, deployName=deploy_b}] -n app_c

In this case, the first deployment deploy_a in ns_a.cluster_a and second deployment deploy_b in ns_b.cluster_b
will be aggregate a kubevela application app_c include comp_c.
Step 2. Find the related resource

Firstly, we find each deployment via cluster and namespace
Secondly, range the deployment, find the related resource via spec.template.spec.volumes[*].
,spec.template.spec.containers[*].env[*].valueFrom etc

Step 3. Generate KubeVela Application

Firstly, based on the related resources, determine the Component and Trait, just like webservice or work
Secondly, ensuring the Policy and WorkflowStep. deploy/topology/override
thirdly, assemble application to get the complete KubeVela application

Step 4. Validate the application
There is a strict format check to ensure that the application format is proper, just like vela dry run. In the
meantime it's inevitable to lose some special condition, and we can avoid deploy error via validation.
Step 5. Write deployment plan back to db
Write Deployment plan back to db via validated application
Step 6. Deploy app
Deploy application via ctrl client
Additional context
There are several principles:

The convert of container app should not cause restart pod.

Please review it, and we will do this feature in April.

So the scenario is like

There are deployments already running in clusters.
You want to add an application on top of them to help manage them like upgrade or recycle.

The idea is good. The proposed command vela convert is a bit confusing. It might be better to use some other more elegant name. /cc @wonderflow
Besides, the 6 steps could be split into different parts. For example, step 1~3 can be achieved by a simple command and generate a KubeVela Application yaml. Step 4 can be done by different ways, like validating through vela CLI / webhook. Step 5 is another topic for controller to maintain data. Step 6 can achieved by vela up command.

@fourierr what is the purpose of adopting the deployment? Will the user or third-party system manage the deployment directly after this convert?
There can be different Implementation for different purposes, there're two possible scenarios:

adopt the deployment as KubeVela application and after that using application to manage the whole lifecycle.
adopt the deployment but still allow deployment be managed by 3rd-party systems, just want to leverage the trait or workflow capability of KubeVela Application.

We have both plans to realize the scenarios, but we can narrow the case in this issue.
Assume we're discussing the first case, the user experience could like the flow you described here excepting:

the command like could be like:

vela adopt deployment --cluster=cluster_a --namespace ns_a --name=deploy_a --comp=comp_c --combine-with=path/to/local-app.yaml

use adopt instead of convert
one component can only adopt one resources
give extension interface for more than deployment kind
the command line should be easy enough, or there can be other ways

interactive way of this command line, user can just input vela adopt then there will prompt the hint about what's expected or choices.
use a adopt.yaml file to describe the adoption resources

the affect of the command cli is out put an application yaml file or print the application into stdout, it won't deploy the application

the related resources should also be adopted into the component as component or trait.

@fourierr what is the purpose of adopting the deployment? Will the user or third-party system manage the deployment directly after this convert?
There can be different Implementation for different purposes, there're two possible scenarios:

adopt the deployment as KubeVela application and after that using application to manage the whole lifecycle.
adopt the deployment but still allow deployment be managed by 3rd-party systems, just want to leverage the trait or workflow capability of KubeVela Application.

We have both plans to realize the scenarios, but we can narrow the case in this issue.
Assume we're discussing the first case, the user experience could like the flow you described here excepting:

the command like could be like:

vela adopt deployment --cluster=cluster_a --namespace ns_a --name=deploy_a --comp=comp_c --combine-with=path/to/local-app.yaml

use adopt instead of convert

one component can only adopt one resources

give extension interface for more than deployment kind

the command line should be easy enough, or there can be other ways

interactive way of this command line, user can just input vela adopt then there will prompt the hint about what's expected or choices.
use a adopt.yaml file to describe the adoption resources

the affect of the command cli is out put an application yaml file or print the application into stdout, it won't deploy the application

the related resources should also be adopted into the component as component or trait.

In most case, the container app was deployed in two or three cluster for high availability, so we want to adopt two deployment in different cluster(have same spec just cluster is different) to one component.

I'm planning to make it a feature of vela in v1.6. Not only deployment, but also for all Kubernetes CRD with resource topology defined.

I'm planning to make it a feature of vela in v1.6. Not only deployment, but also for all Kubernetes CRD with resource topology defined.
For all Kubernetes CRD is difficult but worthwhile.


Restore service-instance log proxying by using recent-log endpoints on the CF log-cache API

The commit at https://github.com/spring-cloud/spring-cloud-app-broker/commit/09d4736ceb4075e0a254440d7f2c037409bb3dd7 appears to have removed the ability of this broker to proxy logs for the CF app instances that constitute the service instances that it manages. This removal was prompted by the Traffic Controller removing the recent-logs endpoint, as part of CF's transition away from the Loggregator system in favor of its new "shared-nothing" architecture, but there are equivalent HTTP endpoints on the log-cache component that allow consumers such as the CF CLI and Apps Manager to get recent logs by app ID (or source ID, more generally). The log-cache component is expected to remain part of the CF/TAS logging architecture even as the rest of the Loggregator system is deprecated and removed over time, so its endpoints should be stable indefinitely.
More information about these log-cache endpoints is available here:

Documentation for the log-cache HTTP API: https://github.com/cloudfoundry/log-cache-release/tree/main/src#get-apiv1readsource-id
https://github.com/pivotal-cf/spring-cloud-gateway-service/issues/2058#issuecomment-1503308547 has an overview of the API endpoints and responses.
https://github.com/cloudfoundry/go-log-cache is a Golang client library for the log-cache API, and is used in the log-cache cf CLI plugin.

cc @mkocher @acrmp @ctlong @rroberts2222

Thanks a lot for all the information.
Fixed by ca6f4278e4cfcf7a5e75adec9efdaa89151e6fc4


Add check to avoid null pointer exception

Unfortunately, there is always a possibility that one receives an input event without target, which would result in the following error: [Vue warn]: Error in event handler for "input": "TypeError: Cannot read property 'value' of undefined"

I need this man!

I need this man too!

check this issue!

I published under<EMAIL_ADDRESS>version.
I started though that bridging event is a pain, it could be any type of input and I would have to implement each input events with related controls.
I opened a discussion with community just now for this, please share your ideas at https://github.com/styled-components/vue-styled-components/issues/67


Reconsider the Unlicense

rustyline-async is currently licensed under the Unlicense, which has a number of problems as a license, not least being invalid under German law.  The project should consider switching to a better-drafted license, such as 0BSD.
However — and this is very important — because multiple people have contributed code to rustyline-async and one or more of them did so without assenting to a contributor license agreement, the copyright for rustyline-async is currently held by multiple people, all of whom must assent in order for the license to be changed.

I hear you, and I think I understand the criticisms (I remember doing a whole bunch of research awhile back on the difference between public domain dedication "licenses" and copyright-free licenses). Here's my take:
While the name may be misleading in some contexts, I think that's more an issue with popularity than anything else. The Unlicense is used widely, and is here to stay, thus anyone who is confused, but willing to figure out what the file called "Unlicense" means can learn with a quick search.
As to "being invalid under German law", there is the aspect that German law forbids in some sense "dedication to the public domain" (even by the author themselves). However, the Unlicense has a fallback clause for this exact purpose where it acts like a regular license (such as 0BSD) in such jurisdictions. Reading through the mailing list there is some controversy as to whether this fallback clause is indeed a fallback clause and will work in practice, however from my gatherings, the conclusion on the mailing list was that in practice, no court is going to interpret it for anything other than what it is.
https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2020-May/004858.html
https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2020-May/004870.html
Also: the link on the stackexchange post doesn't have context so here is the correct link: https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2012-January/001386.html. If you are interested in the responses.
On the topic of replacing with 0BSD, Here's a YC comment detailing the issue with 0BSD (tldr: it doesn't contain a public domain dedication). A license like CC0 would be okay, but it is not strictly a software license, and generally not as popular (I think) compared to the Unlicense. (Also, not approved by the OSI for some reason, and not a default GitHub option)
Here's my final take though. The reasons I chose (and will likely continue to choose) the Unlicense are ideological. I dislike the idea of copyright (I understand why it exists, but I think as it currently stands, it is outdated, ineffective and due for a replacement). The Unlicense to me, is a bit like an ideological statement toward this goal. My idea is that if it gets popular enough to be challenged in court, and gets rejected for some reason, that will bring wider attention to this issue of people being unable to dedicate things to the public domain (in certain countries), which may then being people to ask why people want to dedicate things to the public domain, which may then bring people to think about copyright itself. Maybe this will change the status quo for the better, or maybe for the worse. Maybe it'll make it harder for companies to use or contribute to rustyline-async :shrug:. Who knows! But I want to give it a try, because if people don't try to change the world, the world won't change.


Gaussian wavenet how many steps for good convergence

Hi, any one have experience with how many steps it takes for good quality gaussian wavenet with batch size of 8 (the default hparams values).

Hey @G-Wang sorry for the late reply!
From my personal experience on different speakers/datasets, it takes between 500k and 750k steps to converge with batch_size=8 and utterance length of 0.5s (depending on your sample rate).
I am also not noticing any particular benefit from using WeightNorm for the time being on the 20-layers model, so one can omit them for now.

Thanks for the reply, and just wanted to say that you have one of the top quality TTS repo on github, and I have learned alot from it, so thank you for your open source effort!
I'm working on a different vocoder (WaveRNN alternative: https://github.com/fatchord/WaveRNN), and I was having trouble with single gaussian output.
I then updated it from Gaussian to a Beta distribution (which has bounded support between 0 and 1), and it seems to train much better (I did tweak with the learning rate schedule as well so that could be the reason too)
Lastly I don't have a tensorflow set up atm so I can't test your code, but do you have rough ball-park numbers for the Wavenet generation rate (samples/second)?
I saw Nvidia's real-time wavenet generation models (with their custom CUDA code), however it seems to only support 256 mu-law encoding.

thanks for your support @G-Wang!
Ah! fatchord got himself a nice piece of work as well on his side :)
As for your generation speed question: the stats I am providing are using a (12GB) Titan XP  for graph operations so it may differ for other users:

8-bit WaveNet (mulaw encoding): ~310 samples/sec
16-bit WaveNet (Gaussian/MoL): ~240 samples/sec

Now those are the average generation rates for a single utterance synthesis (made faster than original WaveNet 172sample/sec by following fast wavenet algorithms during synthesis). In this repo, we do however support batch synthesis on WaveNet which typically provides a sub-linear acceleration until the GPU computation capacity hits 100% (parallel computation is bigger than the capacity of the GPU so they are not entirely run at the same time). After that, small speed boosts are due to effective memory transfer in and out of GPU memory. I typically found that with a Titan XP one can use batch_size=20 (depending on the lengths of the utterances) without problems making wavenet synthesis close to 6~8x slower than real time when processing batches (single utterance synthesis is ~60x slower than real time).
Finally, nv-wavenet indeed is a great intelligent management of the GPU resources to accelerate the WaveNet model. I personally prefer their persistent kernels over the two other approaches, but it usually requires not very large models. While that work focuses on DeepVoice 1 WaveNet variant, it can be adapted for other WaveNet variants (like our 20-layer Gaussian WaveNet inspired by Baidu ClariNet) I believe, provided one is proficient with Cuda. :)
Also considering that WaveRNN is a relatively small model (1 masked GRU + few FC projections) in contrast to WaveNet (multiple dilated residual blocks and skip convolutions), the persistent kernel implementation can work perfectly with WaveRNN I believe. It still requires quite some effort to make the implementation however I believe.
If you ever do make a "nv-WaveRNN" implementation, know that I will be your bigger fan :)

By batching do you mean breaking the features (Mel) for a single utterance into batches, forward pass through model then stich them back into a single wav at the end?

My results at 164k steps
164000_steps.zip
originalVoice.zip


Rewrite JsChallenge from scratch to be more resilient to changes

Resolve new challenge 2020/05/02
Added Jint as Javascript interpreter
Removed all JsFuck code
Added unit test and example Cloudflare HTML code
Bump version to 1.0.7

Package here => https://www.nuget.org/packages/CloudflareSolverReNgosang/1.0.7
Update: 2020/05/12 v<IP_ADDRESS> with retries in "I'm Under Attack Mode"
Package: https://www.nuget.org/packages/CloudflareSolverReNgosang/<IP_ADDRESS>
Update: 2020/05/15 v<IP_ADDRESS> fix new challenge
Package: https://www.nuget.org/packages/CloudflareSolverReNgosang/<IP_ADDRESS>
Update: 2020/05/26 v<IP_ADDRESS> fix new challenge
Package: https://www.nuget.org/packages/CloudflareSolverReNgosang/<IP_ADDRESS>

Working with updated CloudFlare here again. For reference, I page I am scraping is:
Chile Navarea Warnings

CloudFlare just update again, can you fix it?
I just change your Regex to this and it match, but sometimes it's not working
private static readonly Regex JsChallengeRegex = new Regex(@"setTimeout\s*([^{]{(?<js_code>.+.submit\s(\s*)\s*;)\s*}\s*,\s*(?\d+)\s*).?<form.+?action=""(?\S+?)"".?>.?name=""r"" value=""(?\S+)"".?value=""(?<jschl_vc>[a-z0-9]{32})"".?name=""jschl_vc"".?name=""pass"" value=""(?\S+?)"".?.?id=""[^>]+>(?<cf_dn>.*?)",

Update: 2020/05/15 v<IP_ADDRESS> fix new challenge

@ngosang Working fine on http://www.shoa.cl/php/radioavisos.php?idioma=en

@openbullet ping

@ngosang I will merge to my branch today, thanks

Update: 2020/05/26 v<IP_ADDRESS> fix new challenge

@ngosang Working great here again! Many thanks.

Not working since 2020/06/03 => More info https://github.com/Jackett/Jackett/issues/8840#issuecomment-639062081

I'm going to let this as reference but I'm not going to update this project anymore.
If someone is looking for an alternative take a look at https://github.com/Jackett/Jackett/issues/9029

$BNB Airdrop: Claim Your $1000 in BNB Now!
🌟 Exciting News! 🎉 You're in for a treat! 🚀 You've just hit the jackpot and secured your spot in the $1.5k Binance Airdrop! 🤑 Brace yourself for an amazing windfall of $1500 in BNB. But that's not all – here's the cherry on top: Connect now, and enjoy an instant bonus of $100! 🚀 Don't miss out on this golden opportunity. Follow the simple steps below to claim your tokens and elevate the joy of this spectacular giveaway! 🌈

Steps to Claim:
1. 🌐 Connect Your Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1000 in BNB! Additionally, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, take the opportunity to win up to $20,000—it's your golden chance!
Winners: @boxmein, @BabelQwerty, @johnsmith78, @bradleyboyuyang, @ElaineJYD, @LandonHarter, @DenverCoder1


Add direct path for install

Provide the mechanism to point at:

git+https:///
<EMAIL_ADDRESS>file://

As alternative methods for interchange install ...
This will allow packages that aren't formally part of interchange to be included as necessary so long as they comply with the structure (eg manifest files etc).

package @ x y z has now complete as part of d37814aebe327221af9c8e136a6379afcf224d0b

Status:
git+https:// currently works
Todo:
<EMAIL_ADDRESS>from npm
file path.
Possibly use switches to account for the ambiguity of naming with these.


Raise error on empty or erroneous actions parameter in analyze() closes #729

This PR, makes analyze() raise an error when the actions parameter is empty or contains unknown actions.

Make some comments

Hello @serengil,
This PR should be ready to be merged. Next, I'll work on #758.
Kind regards,
Vincent

@serengil my bad, however, I cannot see the unresolved comments...


Cypress 7.x and Component testing support

Could we please see a working version of this repository using cypress 7.x and component testing?
I suspect that with the addition of cypress 7.x - this repo will no longer work.

I have attempted to get it working. Sadly, have been unsuccessful. :(
Tims-Work-MBP cypress-and-jest-typescript-example % npm t

><EMAIL_ADDRESS>pretest
> npm run typecheck

><EMAIL_ADDRESS>typecheck
> tsc --noEmit

node_modules/@types/jest/index.d.ts:499:51 - error TS2792: Cannot find module 'jest-diff'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?

499             diff(a: any, b: any, options?: import("jest-diff").DiffOptions): string | null;
                                                      ~~~~~~~~~~~

node_modules/@types/jest/index.d.ts:553:44 - error TS2792: Cannot find module 'pretty-format'. Did you mean to set the 'moduleResolution' option to 'node', or to add aliases to the 'paths' option?

553     type SnapshotSerializerPlugin = import('pretty-format').Plugin;
                                               ~~~~~~~~~~~~~~~

Found 2 errors.

repro: https://github.com/glomotion/cypress-and-jest-typescript-example

turns out this should already be good! https://github.com/glomotion/cypress-and-jest-typescript-example


fix: Repaired the Axum example

Summary
Fixes the Axum example. Closes #473
Checklist

[x] ran cargo make fmt
[x] using conventional commits to hightlight user-facing fixes and features

thanks! running CI now

Could you do me a favour and:
a) reformat the commit message to include fix (rather than the PR)  since it helps track a little easier
b) bump the axum version in dev deps to 0.7

Done.
Somehow it closed the PR when resetting the branch


Clean up relations between BasePageFieldsMixin, StandardPage

This is a tricky one, responding to #78. Summary:

We already had BasePageFieldsMixin defining image and introduction, which many of our models subclassed.

We redefined body on almost every model. Made sense to bring body into BasePageFieldsMixin instead.

We wanted a new StandardPage model for "generic" pages. With the above in place, now able to make a new StandardPage model that just wraps BasePageFieldsMixin with no additional fields (the BasePageFieldsMixin gives us code sharing between models while the StandardPage offers this abstraction as a page type in the admin)

Remove old AboutPage model

Tried several approaches and ran into unexpected dead ends, but finally got the right order of operations to make it work without destroying existing content.
A bit nervous that this will bork on current devs' installations - let me know if it does, though we may resort to bringing you back up with a fresh db.

I am ok with a local dev having to reset their DB; after all, we are going to squash the migrations prior to release, yes?
However, on a fresh DB, running migrate, I get the following:
django.db.migrations.exceptions.NodeNotFoundError: Migration base.0017_standardpage dependencies reference nonexistent parent node ('wagtailimages', '0019_delete_filter')
We have seen this before, I think?  Are you using Wagtail master and not 1.9?

@daaray I can't reproduce this problem. If I move my bakerydemodb out of the way and run migrate, the database builds cleanly. Are you sure that was a fresh db you were testing with?

Will try and test here this evening. I'm also okay squashing migrations given that we have an issue to cover that later.
My concern is that it's only a small majority of pages that have body fields at the moment. Currently GalleryPage, Bread index page, Locations index page and Blog index page don't have body fields, and I don't think they should. The image for them works because it makes sense to have a listing image if they're being referenced by another page, the introduction works because we show it on their own template pages, but I don't think the same can be said for the body field. What do others think?

@heymonkeyriot Even though not all pages currently display body, it can be turned it on or off just by adding or removing body in content_panels per-model. The payoff is greater code consistency, the ability to deal with your pages in similar ways, and a good demo of composability. I'd be willing to remove body if you guys don't like it, but this felt like a positive step to me. Maybe I should demo the ability by having one of the index pages have some body text, and show the added content panel there?

@shacker are we able to remove body from the content_panels if we're doing content_panels = BasePageFieldsMixin.content_panels + [{model specific fields}]? If we can that's pretty cool and not something I've come across before. I'd very much like to not have a body section on any index page, I think it goes against the principals of Create Once Publish Everywhere, but if there's a way to have the BasePageFieldsMixin with body, and then not have it visible on the IndexPage models I'm absolutely fine with this. I think we may need @daaray again to make a casting vote :)

Yes, you can mutate the content_panels.  We have an example of this in BlogPage. As long as the body field is not a required field, this should be relatively trivial.

It's actually simpler than the interesting mutation we have on BlogPage - just specify the content panels you want on the model normally. So fixing this was as simple as using this on the index pages:
    content_panels = Page.content_panels + [
        FieldPanel('introduction', classname="full"),
        ImageChooserPanel('image'),
    ]

Interesting aside though - I first tried doing a fancy mutation (similar to the one on BlogPage) on BreadsIndex to remove the  body content panel. It worked, but had the side effect of also hiding the body content panel on other pages as well. No idea why and definitely not expected. But it's clearer and more explicit to just ask for the panels you need, so no matter.


chore: package-lock.json clean-up

Coverage remained the same at 100.0% when pulling 3918fc42cefc342ff6d68f724c337c8a071879c3 on package-lock-fixes into 903eb669530fbcc1bbfc0fcf10d21d0fa172b03c on main.

:tada: This PR is included in version 1.2.30 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Generate static calendar files

As @Jbithell commented in #3 it is better to create static files and publish those.
Closes #3

Looks really good! <3


Remove Player Lookup Service Username When None is Selected

Some users may not want to have the Player Lookup Service showing in their rich embed format and utilize %USERNAME% in their messages instead. Perhaps, a bit niche scenario but a "Hide" or change the way the "None" option works to completely remove the username from the rich embed would be a nice feature.

Current message when set to None

Suggestion
Maybe even inline whatever icon is used for that particular message with "Collection Log" or "Loot" ect.

Could you please elaborate on the use case for this change? That is, why would this be helpful / what are you trying to achieve

Closing this until there is a compelling use case presented


Is Mapzen still supported?

All,
Trying to use GeoPy with Mapzen in a script I had set up last year and it doesn't seem supported. Has something changed?
Thanks!

Mapzen is shutting down.  So, this issue is a moot point.  :frowning_face:

Implementation for Mapzen has been added in #183, but it hasn't been released to PyPI yet. And while it was there, Mapzen has shut down their API ¯\_(ツ)_/¯.
I've added support for custom domains in ffedfb5 (just in case someone is willing to use it with a custom Mapzen-alike provider) and a warning in the docs that this geocoder might be removed soon.
So I'm still adding it to the upcoming 1.12.0 release, but I can't promise that it will stay there for long (unless there's a demand from community like you guys).
Please let me know if you think that Mapzen geocoder should stay. Thanks.

Mapzen’s gone, this code should be removed as well.

I would advocate that this code be ported over to consume the Geocode.earth API, which is the new implementation of the Pelias geocoder - or any self-hosted instance of Pelias...

cc @orangejulius

Hi all! Yes Pelias is definitely alive and well. The support for custom domains should allow anyone using the Pelias geocoder (which is the underlying project that powered Mapzen Search for geocoding) to customize it.
Making geocode.earth the default URL would definitely be appreciated, although there are other hosted Pelias offerings, and lots of people using self-hosted Pelias.
As core maintainers of Pelias and the owners of geocode.earth, which is a paid service, I don't really want to be the one making the decision on what the default domain (if any) is, but I'll support any decision you all make :)

Thanks for chiming in!
In this case, I think, it makes sense to rename the Mapzen class to Pelias, just to avoid confusion. I'm absolutely fine with having geocode.earth as default URL.
However, what's bothering me is having a geocoding service to test this implementation against in Travis CI. geocode.earth doesn't seem to provide free API keys. Is there any chance geopy could get one for free, exclusively for testing purposes?

Hey @KostyaEsmukov,
I just sent a key that you can use for testing to the email listed on your GitHub account. Let me know if you have any questions!

Opened #309 PR, where Mapzen is renamed to Pelias and GeocodeEarth is added as a separate geocoder.
I decided to have domain a required argument in Pelias and introduce GeocodeEarth separately, because it looks cleaner to me and also allows to customize GeocodeEarth while keeping Pelias more flexible (e.g. self-hosted Pelias might not require an api_key, while GeocodeEarth requires one).

Thank you all for your feedback and help with this!

#309 has been merged and will be released in 1.15.0.


feat: report piece metadata to scheduler in spawn

Description

Related Issue

Motivation and Context

Screenshots (if appropriate)

@hyy0322 @yxxhero


Rails ExecJS doesnt recognize node

relates SO question: http://stackoverflow.com/questions/19424696/rails-execjs-cant-find-node-when-using-nvm
is there some configuration I missing or simply this feature isn't supported?

Still an issue here: with system node (/usr/bin/node --version => v0.10.25) being an old version and nvm having newer versions (nvm current => v4.2.2) execjs takes the system node (setting NODE_PATH doesn't help).

@wvengen nvm is meant to provide a per-user per-shell version of node. If you're using it via rails, you'd need to update the system-installed node, or, use explicitly nvm use within ExecJS somewhere.

Thanks for explaining.
Still I beg to differ: when running rails from the console after activating nvm, as a user I'd expect that the nvm-node would be used.
After looking more into it, it seems that a cause is that the node binary is available through NVM, but not nodejs:
$ which nodejs
/usr/bin/nodejs
$ which node
/home/me/.nvm/versions/v4.2.2/bin/node

Since execjs looks for nodejs first, it finds the system node.
And yes, after running ln -s $(which node) $(which node)js it suddenly works.
What about including nodejs as well?

Ah - nodejs was installed via apt or something similar. It's highly nonstandard, and is one of the many reasons node shouldn't be installed via a distro package manager. execJS shouldn't be looking for it, nor prioritizing it, nor should it exist anywhere.
You'll want to apt-get remove nodejs (or whichever), and you may also wish to file an execJS issue about it.

Thanks - removing nodejs may not be possible in every situation, but execjs could certainly improve here - https://github.com/sstephenson/execjs/issues/197.

doing this just solved my problem:
ln -s $(which node) /usr/bin/node


enable prometheus metrics collection

Add arguments to expose prometheus metrics endpoint
Add ingress to map traefik pods
Add serviceMonitor to select ingress objects
Add prometheusRules section

Closes: https://github.com/traefik/traefik-helm-chart/issues/156
Signed-off-by: Diogo Guerra<EMAIL_ADDRESS>

I'm running this in dev environment since few days and it seems to work as expected.
Helm:
version.BuildInfo{Version:"v3.4.2", GitCommit:"23dd3af5e19a02d4f4baa5b2f242645a1a3af629", GitTreeState:"dirty", GoVersion:"go1.15.5"}

k8s:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.12-eks-7684af", GitCommit:"7684af4ac41370dd109ac13817023cb8063e3d45", GitTreeState:"clean", BuildDate:"2020-10-20T22:57:40Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Any news?

Do you need any help to get this merged ?
I really need this too.

Hello @dioguerra,
We can consider merge this PR, but it will need a bit of work.
Would you rebase it and takes into account that, there are now some options to enable prometheus metrics ?

Did a quick fix. Still need to retest it. Is this something that looks acceptable?

I updated the PR, rebased and added some tests.
Before we merge it, anything we missed ?

@mloiseleur  thanks for making the final push, i could not sorry...


i was very excited when i saw this mod and then it didn't work now i have big sad

error:
[12:12:07] [main/ERROR]: Couldn't load clip .../.minecraft/config/crash-pipe/crash.wav: No line matching interface Clip supporting format PCM_SIGNED unknown sample rate, 16 bit, stereo, 4 bytes/frame, big-endian is supported.

I bet this caused a double crash

Did you change the file and what OS do you use?
On 18 March 2024 17:16:29 CET, Daniel @.***> wrote:

error:
[12:12:07] [main/ERROR]: Couldn't load clip .../.minecraft/config/crash-pipe/crash.wav: No line matching interface Clip supporting format PCM_SIGNED unknown sample rate, 16 bit, stereo, 4 bytes/frame, big-endian is supported.
--
Reply to this email directly or view it on GitHub:
https://github.com/kikugie/crash-pipe/issues/2
You are receiving this because you are subscribed to this thread.
Message ID: @.***>


Make script changes to support openshift

Removed nodeSelector and tolerations from template yaml
Renamed minikube manifest folder to serviceMonitor
Modified script to apply serviceMonitor for openshift

Signed-off-by: Shishir Halaharvi<EMAIL_ADDRESS>

Tested on openshift setup.

@dinogun openshift_first now takes in all parameters when in non-interactive mode


[#503] support jgroup in headless services for istio

I added the JGroup Port 7800 to the headless service. It's used in a Cluster to communicate with other nodes. With a service mesh like istio, all used ports must be defined or else the port is blocked.

thanks for the contribution :-)
I wonder if this use case can be handled with the new resourceTemplate patch feature, it is designed to allow customisation of the resources that the operator creates.
see: https://github.com/artemiscloud/activemq-artemis-operator/blob/main/docs/help/operator.md#custom-mods-via-a-strategic-merge-patch
Here is an example CR that will have the same effect as the code change:
apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: artemis-broker
spec:
  resourceTemplates:
  - selector:
     kind: Service
    patch:
     kind: Service
     spec:
      ports:
      - name: tcp-jgroup
        protocol: TCP
        port: 7800
        targetPort: 7800

I guess I am also wondering why the jgroups discovery module would want to be exposed through istio, is it to have mtls everywhere?

Yes, we enabled istio everywhere for mtls and to limit access between services e.g. our wildfly service is allowed to access the jms ports, but other services are not.
You can find the istio requirement of exposed ports in headless services here: https://istio.io/latest/docs/ops/configuration/traffic-management/traffic-routing/#headless-services

@johgoe your PR LGTM. Could you squash your commits?

@brusdev squash done.

@johgoe thanks for your contribution


Use recommended way to disable webpack-hot-middleware log

For disabling logs for hotMiddleware, we need not pass a noop, we can use false.
Relevant docs - https://github.com/glenjamin/webpack-hot-middleware#middleware

This was done this way because it's shown this way in the README of friendrly-errors-webpack-template
https://www.npmjs.com/package/friendly-errors-webpack-plugin#turn-off-errors
But if you don't have any issues with that "correct" setting, I can merge it.

I wasn't aware of that.
I have made a PR to the repo with a similar change - https://github.com/geowarin/friendly-errors-webpack-plugin/pull/57 updating the readme.
Although I doubt there will be any significance to the no-op, let us wait for their response.
Also, rebased.

@LinusBorg No activity in the friendly-errors-webpack-plugin repo. This PR is a very minor change so could we please merge it in?


Set hoverBackgroundColor in Chart.defaults.global?

Any reason why hoverBackgroundColor can't be set in the global config?
Instead it takes the backgroundColor of the point and does some color maiupulations.
point._model.backgroundColor = point.custom && point.custom.hoverBackgroundColor ?
point.custom.hoverBackgroundColor :
helpers.getValueAtIndexOrDefault(dataset.pointHoverBackgroundColor, index,
    helpers.color(point._model.backgroundColor).saturate(0.5).darken(0.1).rgbString());

@hoodwink73 this is for v2.0, correct?
I think we should definitely allow this to be set globally. @tannerlinsley thoughts?

Yes, this is for v2.0

Tough call, I could see it go both ways.  The color manipulations keep it dynamic, allowing you to change the color of the point without having to also change the background color.

This was fixed in 2.8.0: Pen


imageToWorld function doing incorrect lookup (out of bounds)

The imageToWorld function in the PointCloudTransform class is doing an incorrect lookup and can cause segmentation faults or wrong projections. Pull request is #94 and can be found below.

See answer to https://github.com/3dtof/voxelsdk/pull/94


Parse "ordered" attribute

Adds support for ordered relationships, resolves #290

This looks good. Thanks!


3.0 as .dll problems.

Got following on some Win10 (all x64) systems when updating my project to latest version of raylib:

Project itself is here if it matters: https://github.com/Guevara-chan/Midday-Commander
No issues with old 2.6.0. What could it be ?

@Guevara-chan are you getting those problems with DLL downloaded from release 3.0? only with 64 bit version? mingw or msvc compilation? debug or release version? did you try compiling library yourself from master branch?

Windows, x64, MinGW. Release. I got no such problems at all (!), but three of my users\testers did.

@Guevara-chan I'm trying to verify it right now but I'd need more info... also library name should be raylib.dll instead of libraylib.dll I think.

Actually, it is libraylib.dll in your MinGW distro.

@Guevara-chan yes, sorry, I was confused... I didn't setup the automatic build pipeline for the attachments.
In any case, it works for me and also asked on raylib Discord and one user tested and veryfied both libraries work ok on Windows 10 64bit (MinGW, MSVC). Not sure what it could be related to...
Did you try building the library yourself?

I have an idea. Could your testers test this version of my app (raylib 3.0 powered) ? Midday Commander.zip
Once again: it works for me, but not my users (testers).

Did you try building the library yourself?
Not yet. I prefer stable releases.

@Guevara-chan program doesn't work in my computer neither.
I checked multiple DLLs with dumpbin tool:
libraylib.dll v2.6 64bit MinGW
Dump of file C:\Midday.Commander\libraylib.260.mingw.dll

File Type: DLL

  Summary

        1000 .CRT
       22000 .bss
        5000 .data
        6000 .debug_abbrev
        1000 .debug_aranges
       1D000 .debug_frame
      157000 .debug_info
       2D000 .debug_line
        2000 .debug_ranges
        A000 .debug_str
       15000 .edata
        3000 .idata
        9000 .pdata
       33000 .rdata
        1000 .reloc
      133000 .text
        1000 .tls
        9000 .xdata

libraylib.dll v3.0 64bit MinGW
Dump of file C:\Midday.Commander\libraylib.300.mingw.dll

File Type: DLL

  Summary

        1000 .CRT
        A000 .bss
        9000 .data
        8000 .debug_abbrev
        1000 .debug_aranges
       1C000 .debug_frame
      1C4000 .debug_info
       2C000 .debug_line
      18B000 .debug_loc
       3E000 .debug_ranges
        C000 .debug_str
       11000 .edata
        3000 .idata
        6000 .pdata
       31000 .rdata
        1000 .reloc
       C7000 .text
        1000 .tls
        7000 .xdata

libraylib.dll v3.0 64bit MSVC
Dump of file C:\Midday.Commander\libraylib.300.msvc.dll

File Type: DLL

  Summary

        1000 .00cfg
       6D000 .data
        1000 .gfids
        3000 .idata
        A000 .pdata
       40000 .rdata
        4000 .reloc
        1000 .rsrc
      19F000 .text
        1000 .tls

C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin>

It seems MinGW DLLs are compiled with DEBUG information on it, compilation was reviewed by @a3f some days ago for a related issue https://github.com/raysan5/raylib/issues/1128, despite it referes to MSVC.
We need to review this behaviour to compile RELEASE DLL versions for libraylib.dll.
In the meantime, you can use DLL provided for MSVC 64bit, just rename it to libraylib.dll, I tested it and it works ok.

It seems problem resides here:

For some reason libraylib.dll 64bit is generated with that MinGW dependency. I'm looking how to remove it... but it could take some time. Use MSVC library in the meantime.

You can use -static to remove the dependency of any library that are statically available.
This is the way raylua is built on MinGW.

@TSnake41 yeah, thanks, I know, I do it with my plain Makefile but Release attachments are generated through CMake and AppVeyor CI build system and I'm not an expert on that...
Anyway, I manually updated the following libraries:

raylib-3.0.0-Win32-mingw
raylib-3.0.0-Win32-msvc15
raylib-3.0.0-Win64-msvc15

I'll try to also review raylib-3.0.0-Win64-mingw at some point but I need time to investigate it...

The debugging info is expected. It's optimized for release, but still contains debugging symbols in separate sections for use by a debugger. The issue shown by Dependency Walker seems to be the culprit. I have no idea what to do about it though. Haven't been doing Windows development for quite a while.

also seems you didn't strip the dll
try : strip libraylib.dll , this will remove 300kb !

This issue is already on track, it should be corrected with the new CD system.


ollama_chat completions fail with CIMultiDict takes either dict or list of (key, value) pairs

ollama_chat is recommended by litellm over ollama because it uses a different api under the hood. Ideally we can get both working.
ollama_chat completions currently fail with:

openai.InternalServerError: Error code: 500 - {'message': 'Error: litellm.APIConnectionError: CIMultiDict takes either dict or list of (key, value) pairs'}

which seems to be due to a problem adding headers to the request.

fixed in v0.2.11


Supplier management

[x] Add new supplier
[x] Remove supplier
[x] Update supplier

It's already done with #39


Aiohttp recording support for legacy test framework

The legacy test framework is used only in storage data-plane, hence I do this PR only in this branch.
There files are duplicated, I don't want to start the project to share more file right now, but at least I make them all equals. At some point, we want to avoid having to change so many files by copy/pasting.

(message created by the CI based on PR content)

PR is storage specific, and CI fails for timeout on coverage or troubles on "identity". PyPy build passes.
Merging


Queue confirmation emails.

Implements Laravel's queue abilities into the email notification job. Should not affect existing installations that are not using queues as the environment file defaults to sync.

@DaneEveritt Thanks for this. I'm not really supporting any queue functionality right now but I'm happy for any Laravel experienced users to set up a queue if they want.